fbpx

AVC Advanced Variant Configuration

How to find the odata errors in SAP S/4HANA

by

Loading

Check OData Error Logs in /IWFND/ERROR_LOG

The primary location for checking OData service errors is the transaction /IWFND/ERROR_LOG.

  • Steps:
    1. Execute the transaction /IWFND/ERROR_LOG in the SAP GUI.
    2. Use filters such as User, Date/Time, or Service to narrow down the results.
    3. Check the error details for further analysis.
  • Error Analysis:
    • Analyze the error codes and messages.
    • Inspect the stack trace for technical details.
    • Often includes information about missing authorizations, incorrect URIs, or payload issues.

Advanced Variant Configuration screen does not open in classic SAPGUI transactions

by

The Advanced Variant Configuration screen does not open in classic SAPGUI transactions (e.g. Sales Order processing) and shows an error page or an empty screen or an error message that some requests were not successful in case the S/4HANA embedded Fiori deployment option is used, which means S/4HANA backend and Fiori frontend server system are the same.

Another issue is that a logon page comes up in SAPGUI for Windows when opening the Advanced Variant Configuration screen in case the S/4HANA embedded Fiori deployment option is used.

The reason for the issue in the Advanced Variant Configuration screen is that an origin URL parameter is added to the OData requests sent to the SAP Gateway system, which is prohibited by SAP Gateway in the Co-Deployment scenario.

The logon page issue happens because in SAPGUI for Windows, the SSO logon cannot be established the same way as when accessing the system via Fiori Launchpad and embedded SAPGUI for HTML; instead, a ticket-based logon using special capabilities of the SAPGUI HTML Viewer control is used.

Refer the Notes: 2916536-2916536 – SSO and OData Issue Fix for Advanced Variant Configuration