Considerations while recording scripts in SAP Fiori® Standard mode - Automate_Studio - Latest

Automate Studio with Evolve User Guide

Product type
Software
Portfolio
Integrate
Product family
Automate
Product
Automate > Automate Studio
Version
Latest
ft:locale
en-US
Product name
Automate Studio
ft:title
Automate Studio with Evolve User Guide
Copyright
2025
First publish date
2018
ft:lastEdition
2025-10-30
ft:lastPublication
2025-10-30T16:47:31.176000
When you use the SAP Fiori® Standard Mode to record a script in the apps listed below, consider the following:
  • In Manage Global Hierarchy app:
    • If the recorded script creates a hierarchy using the Import Hierarchy option, the data type of date fields in Hierarchy Valid From and Hierarchy Valid To is displayed as String. In this case, you need to put the values in YYYYMMDD format.
    • The ValidityStartDate and ValidityEndDate fields cannot be skipped by making these fields as fixed value by providing a Skip Field Indicator as fixed value. If the field is marked as upload to SAP and then you provide a Skip Field Indicator, the script will run successfully.
    • If you need to create multiple subnodes, you can enter data row by row instead of using a loop. This helps in getting accurate logs for both valid and invalid data.
    • The NodeParentID field appears blank in the lookup if it does not already have a subnode. To fix this issue, add the key UseNodeIDAsParentIfEmpty in the ShuttleRule.xml file. If the value for this key is true, then the nodeid value gets assigned to NodeParentID.
  • In Manage Journal Entries app, while recording a script, if its line item fields are also recorded, the title in script properties will display as Item instead of the app name.
  • In Reclassify Products - Commodity code app, when you try to Download the fields, the data will not download from SAP.
  • In Reclassify Product Commodity Code and similar apps, lookup functionality is currently unavailable for the fields Validity Start Date and Validity End Date in SAP. However, these values are retrieved via a GET call and must be passed when you run the script.
  • In Post General Journal Entry app, if the recorded script contains ProfitabilitySegments entity, set its Line Item Behavior to None instead of Add or Edit.
  • In Post Goods Receipt for Purchasing Document app, when you enter an incorrect information, the error message shows an incorrect purchase order number. Irrespective of the purchase order number you provide, it always shows Purchase order 0045000001 was already changed in the error message which directly comes from SAP.
  • In Manage Cost Center app:
    • You need to provide the Cost Center name in uppercase to avoid any issues during runtime.
    • You may notice that the value for toggle fields are not updated in SAP as per the provided values in the data file. To fix this, an entry should be created in ShuttleRule.xml. For example:
      <FioriToggleFields>
          <EntityField App="F1443A" field="IsBlkdForPrimaryCostsPosting" />
          <EntityField App="F1443A" field="ConsumptionQtyIsRecorded" />
        </FioriToggleFields>
  • In Create Bill of material app, the Material field should remain empty because it is a query parameter and gets recorded as an empty field.
  • In Manage Sales Quotation (V2) app, the Script run is considered as a success even if in the data file invalid rejection reason is provided.
    Note: In Automate Studio, the warning message is not treated as an error and is displayed as a log message without an error code.
  • In Manage Business Partner Master Data app, while recording the line items if the Standard value is set to Yes, the recorded fields will not appear in the mapper. If you record the line items that has No as standard value, then only the recorded fields will appear in mapper.
  • In Manage Bank Accounts app, if you try to add a language that already exists, the message An exception was raised will appear.
  • In Manage Prices Sales app, the date field cannot have a blank value. You need to provide Skip Field Indicator to run the script successfully. Otherwise, the following error will be logged in the run logs:
    Error Code:/IWCOR/CX_DS_EP_PROPERTY_ERROR/005056A509B11ED1BF822D2D0917DA04
    Message: Property 'FixedValueDate' at offset '2.013' has invalid value ''.
  • In Manage Prices Sales app, while recording, you must select a criteria, such as, condition record that ensures only one row appears in the grid. This allows Automate Studio to accurately capture the intended changes. During execution, you must use an alternative field to get the value for conditionRecordUUID field to avoid the Object does not exist error.
  • For GUI For HTML, warning messages are displayed as Error in the validation log. You can use the Shuttlerule setting GUIForHTML_SuppressAllGUIWarningsOnValidate which is true by default to remove the warning messages.
  • In Goods Receipt app, the lookup column appears blank for the Storage Location field. To fix the issue, add the corresponding entry in the ShuttleRule.xml under FioriLookupMapping. The values will be available once you apply the filter on Material Number and Plant.
  • In Change Material Prices app on Public HANA Cloud sap server, following error might be observed:

                Cannot access child value on Newtonsoft.Json.Linq.JValue..Error
                Code:RAP_RUNTIME/028Message: Read-only fields must not be changed.

    To resolve this error, you can use the Skip Field Indicator as mentioned below:

    Mapper steps for workaround

    1. After recording the script, navigate to the Expert View on the Map tab in Automate Studio.
    2. For the screen to_InventoryPriceChangeItem, create a loop and set its Loop Behavior to None under properties section.
    3. Save the script.
    4. Add one line item to send the Material, and another line item to post the Price and Quantity based on the selected data source.