2960901 - [Best Practice] How to capture the OData query when using import data connection to acquire data from S/4HANA On-Premise system in SAP Analytics Cloud (SAC)

• Unexpected problems occur when using import data connection to acquire data from S/4HANA On-Premise system in SAP Analytics Cloud (SAC) 
• What trace can be used to capture the OData query (call)?
• How to verify or test the same OData call inside S/4HANA On-Premise system?

• SAP Analytics Cloud (Enterprise) 
• SAP Cloud Connector
• SAP S/4HANA On-Premise

Method 1: Leverage the SAP Gateway Tracing Tool (Recommended)

1. Log into your S/4HANA system.
2. Run transaction code: /n/iwfnd/traces.
3. Add the connection user used in S/4HANA connection for the data import.
4. Change the Error Log Level from Secure to Full.
5. Enable (check) the Payload Trace option.
6. Go to SAC, and import the data from the specific OData service in the SAP S/4HANA system.
7. After the import is executed, check the collected trace in Payload Trace table.
   
8. Double click the OData call having the issue where you can see both Request & Response.
   
   

• Using this way, you do not need to run the OData call using transaction: /IWFND/GW_CLIENT as the response shown here could help decide on next actions.
• See Configuring Tracing Tools and Payload Trace for further information.

Method 2: Leverage the Traffic Trace of SAP Cloud Connector

Note: this trace can be used for the whole workflow of importing data from SAP S/4HANA, from creating connection to loading data from specific OData service.

1. In the SAP Cloud Connector (SCC), in the "Log And Trace Files" section, tick option "Payload Trace" per KBA 2452568 - Log and Trace files for SAP Cloud Connector.
   
   
2. Go to SAC to try creating a new model or refreshing import job in existing model based on the import data connection to SAP S/4HANA.
3. Go back to SAP Cloud Connector, in the "Log And Trace Files" section, find the "traffic_trace_<account id>_on_<landscapehost>.trc" with the most recent Timestamp displayed. Click the download button under "Actions" on the right side. 
4. In the downloaded trace, find the latest Request like "GET https://<Host:port>/sap/opu/odata/sap/...$format=json HTTP/1.1..Authorization: Basic".
   => It may be shown in multiple lines at the right side so you may need to copy each line till the space before  "HTTP/1.1" (like bolded text above).
   => If you have trouble to copy the full OData call out from the trace file, you can provide the downloaded trace file to SAP Support.
   

Method 3: Leverage the RSTT trace in the S/4HANA system

1. Collect the RSTT trace according to SAP KBA 2834064.
   => Not all OData call sent to CDS View in S/4HANA On-premise system can generate RSTT trace, which depends on type of CDS View.
   => If RSTT is not generated, please leverage Traffic Trace of SAP Cloud Connector to capture OData call, which should always work.
2. In transaction RSTT, go to Trace collection to find the latest generated trace records by the Trace User.
3. Double click the last record (sometimes, there will be multiple records generated for one workflow performed in SAC).
4. Display Parameters.
   
5. Search with keywords 'uri' and then you can find the OData call sent from SAC (starting with /sap/opu/odata/sap).
   
   

Verify / Test the same OData call in the S/4HANA On-premise system (for Method 2 and Method 3 only)

1. Log into your S/4HANA On-premise system.
2. Start transaction: /IWFND/GW_CLIENT.
3. Put the copied OData call into Request URI and click the Execute button.

• If you capture the OData call from traffic trace of SAP Cloud Connector, you need to remove "https://<Host:port>" and just use "/sap/opu/odata/sap/...$format=json".
• If the issue is reproducible and is independent of SAP Analytics Cloud, the source system issue will require assistance from the source system component support team.
• For example, component BW-BEX-OT-BICS-EQ for custom CDS View or the relevant component delivering the standard CDS View, from which the OData service is exposed.

• SAP Gateway Tracing and Error Checking
• 3138542 - How to Consume an OData Service from an SAP Analytics Cloud Analytic Application?
• 2628688 - OData service connection in SAP Analytics Cloud ***Collective KBA***
• 2739706 - Error message "The user does not have permission to access the requested resource." appears when creating Import Data Connection to OData Services from SAP S/4HANA in SAP Analytics Cloud (SAC)
• 2569847 - Where can you find SAC user assistance (help) to use, configure, and operate it more effectively?
• Have a question? Ask it here and let our amazing SAP community help! Or reply and share your knowledge!
• 2487011 - What information do I need to provide when opening an case for SAP Analytics Cloud?
• 2511489 - Troubleshooting performance issues in SAP Analytics Cloud
• Search for SAP Analytics Cloud content using Google or Bing:
• https://www.google.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
• https://www.bing.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
• Note: Add relevant text or warning/error messages to the text search field to filter results.
• SAP Analytics Cloud Connection Guide
• Getting Started with SAP Analytics Cloud Expert Community page
• SAP Analytics Cloud Get More Help and SAP Support
• Need More Help? Contact Support or visit the solution finder today!

Your feedback is important to help us improve our knowledge base.

SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped, OData, Call, S/4HANA, S4, import, acquire, test, validate, GW_CLIENT, collect, capture, RSTT,