Troubleshooting

General troubleshooting recommendations

The following triage steps build good troubleshooting habits generally and can help to establish whether an issue is caused by PreBilt or another factor.

When testing PreBilt, use a private browser session with mobile device emulation (if no mobile device is available) and enable the /SCWM/RF_TECH_TITLE parameter. Check the console and network tabs in developer tools for errors during testing.

• To enable developer tools and device emulation in either Edge or Chrome:

  • Press Ctrl+Shift+i to enable to developer tools

  • Press Ctrl+Shift+m to toggle mobile device emulation

• To enable the /SCWM/RF_TECH_TITLE user parameter:

  • Open the relevant SAP GUI client and go to transaction SU3.

  • Select the Parameters tab.

  • Add /SCWM/RF_TECH_TITLE as a parameter name.

  • Set its value to X and save your changes.

Diagnosing an issue with PreBilt

1

Replicate the issue

• Try to replicate the issue in ITS (if available) or RFUI.

  • If the issue can also be reproduced in a different frontend (such as SAP GUI), the problem is likely not with PreBilt but with another system.

• Simulate how the end user is processing the task.

  • For scanned inputs, press Enter after input to mimic the scanner’s carriage return.

  • For push buttons, click the on-screen button rather than using function keys on a keyboard.

  • Use the same or similar data as the original process.

2

Review errors

Analyse any resulting error messages, process data (particularly RF logs, if available), application logs (SLG1), runtime error logs (ST22), and relevant third-party interface data (such as non-SAP Printing or ShipERP).

3

Consider recent changes

Check for recent changes (such as workbench, customization, or infrastructure). If a recent change is thought to have caused the issue, try clearing the cache. Clear browser history for web applications or the app cache for full applications.

Next steps when troubleshooting a potential PreBilt issue

1

Capture key information

Note

(This step is only available if the /SCWM/RF_TECH_TITLE parameter is active.)

Click the “i” icon in the top-right of the screen and:

• Copy the Last Response details at the point of the issue.

• Note the Screen Program, Screen Number, and For Configuration logical transaction details from the technical information window.

For newer versions of PreBilt:

• Perform a triple tap on the app header to view the app version and active plugins.

• If this information is available, capture it.

2

Seek additional support

Contact the Software Team if you identify a potential PreBilt issue and require help with testing or troubleshooting.

Checking service status

In transaction SICF, Execute the selection screen with the default values.

Check relevant TCTM services for the TCTM_EWM deployment are active. If the following services are present they should be activated:

• sap/bc/apc/tctm (and sub nodes)

• sap/bc/bsp/sap/ztctm_fiori

• sap/bc/ui5_ui5/sap/ztctm_fiori

• sap/opu/odata/tctm

• tctm_ewm (and sub nodes)

• tctm_ewm_ui

Check services relevant to your platform, such as PSE or Movilizer.

Inactive services can be activated by right clicking them, then clicking Activate Service, followed by the Yes (with subnodes) button.

Specific issue resolution

Unable to log in or PreBilt crashes when entering a transaction

If the user is not assigned to a Presentation Profile, where the ITS screens have not been converted for PreBilt, the user may not be able to login or may experience a crash trying to access some transactions. An issue here will result in a dump visible in ST22 with the runtime error “ITS_TEMPLATE_NOT_FOUND”.

Check that the user and presentation device setup has been completed correctly.

"Error received from SAP.()Template interpretation terminated, template not found"

If the error message and short dump "Error received from SAP.()Template interpretation terminated, template not found" is displayed, login has likely been attempted with a Presentation Device with a non-PreBilt display profile assigned.

If multiple presentation devices are available to select at login, choose a Presentation Device where the corresponding Display Profile has had the ITS screens converted for PreBilt:

This error message may also be caused by an issue with HTML templates.

Wrong menu displayed or short dump occurs during auto login

Incorrect assignments of presentation/personalisation profile can result in an incorrect menu displaying. Where Auto Logon is selected, short dumps can result if the determination is attempting to login to a presentation device (display profile) where there are no PreBilt HTML templates.

Check whether the user has an entry in /SCWM/USER with Presentation/Personalisation profile assignments that correspond with the correct assignments for that warehouse/role.

Error: Backend Installation Error. Please ensure the ITS service (/tctm_ewm/its) returns a valid JSON structure

The message "Error: Backend Installation Error. Please ensure the ITS service (/tctm_ewm/its) returns a valid JSON structure" or "Error received from SAP.()Template interpretation terminated, template not found" can indicate a need to generate (or regenerate) HTML templates for PreBilt.

Go to transaction /TCTM/EWMITSTEMPGEN to check the HTML Template Status for PreBilt.

• Service should be populated with ZTCTM_EWM

• IAC theme should be 99

• Generating Style should be set to TCT Mobility Templates for EWM

• The Publish? checkbox should be set to checked.

In the results, the icon colour indicates the status of the template. An amber icon means the template does not yet exist, while a green icon indicates the template already exists. For templates with a green icon, the page's publication date and status can be verified.

If a transaction or screen has been modified, the HTML template may need to be regenerated, often indicated by an amber status. If backend changes have been made and the screen works in SAP GUI, but not in PreBilt, regenerate the HTML template.

Consult the Software Team if you still experience issues after regenerating templates.

Non-functional message handling across /SCWM/RFUI

Message handling differs between internet services and when an RF transaction is executed in SAP GUI. If a custom or enhanced transaction works in SAP GUI but not in PreBilt, the step function modules likely have an underlying issue. Refer to the relevant technical team and seek internal support if required.

Some S4 2022 releases without this SAP Note applied will experience non-functional message handling across /SCWM/RFUI.

When importing this note, certain technical changes are required for PreBilt. Please note that RFUI will short dump with any front end until making these changes.

Unexpected verification errors when using PreBilt for EWM

It is advisable not to hide any verification fields using the PreBilt screen configuration. The RF Framework already manages verification control and field display in RFUI. If unexpected verification errors occur, check for hidden verification fields in PreBilt screen customisation. Test the same transaction step and process in SAP GUI using transaction /SCWM/RFUI.

No function key is displayed or the function key does not work as expected

Even though all function codes can be presented in a single list with PreBilt, they will not process as expected if a unique function key per function code group is not preserved. Function Code Profiles still require configuring as if a normal ITS service was in use.

If the expected response is not resulting from executing a function code, check the Function Code profile for the corresponding Logical Transaction.

Back navigation is missing

PreBilt recognises standard "Back" navigation function codes (e.g., BACK, BACKF) and displays a "Back" arrow in the top-left corner of the screen. However, custom transaction steps and some standard steps without these function codes will not show a back arrow by default in PreBilt.

If standard back function codes are not used, a "Back" navigation override is available in the PreBilt configuration (transaction /TCTM/EWM_CFG). Refer to the configuration guide for details on enabling this override, which will ensure the "Back" arrow appears in PreBilt.

(Please note that PreBilt is only warranted when SAP RFUI design guidelines are followed.)

"Data corruption or parsing errors"

1. Inspect the