Sap fiori ll11 – consultants should know about o data troubleshooting sap blogs

3/13/2017 SAP Fiori LL11 – Consultants should know about OData troubleshooting | SAP Blogs
https://blogs.sap.com/2013/11/13/sapfiorill11consultantsshouldknowaboutodatatroubleshooting/ 1/13
Community / Blogs
Get Started

Solutions  Support Training Community  Developer  Partner 
About 
Masayuki Sekihara
more by this author
Follow
SAP Fiori LL11 – Consultants
should know about OData
troubleshooting
November 13, 2013 | 4,566 Views |
SAP Fiori
fiori
share

0 share

0 tweet

share

13
SAP Fiori Lessons Learned 11
Consultants should know about OData troubleshooting

Background:

SAP Fiori apps are out of the solution but you face several issues
because main functions are in backend ERP and each customer has
different backend setup/configuration. OData is the communication
channel to the backend servers via get/post/put method.

Lessons Learned:
Understanding OData and backend function are must requirements for
consultants.
Application consultants should learn about OData technical and
runtime behavior
Technical consultants should learn about ERP application
functions
Both application consultants and technical consultants should
work together

Consultants should know following steps.

Step 1. Identity the OData service call
1.1 Run the app
1.2 Inspect element
Right click > Inspect element (Chrome), F12 (IE), then go to Network
tab

Ignore the warning or error message in the Console tab at this point in
time. Focus on OData troubleshooting.

1.3 Refresh the app or browser
1.4 Find the last called OData URI
Scroll down to the bottom of inspect element and find the OData
/sap/opu/odata/sap/.. from bottom.

http://<host>.<domain>:
<port>/sap/opu/odata/sap/GBAPP_POAPPROVAL;mo/WorkflowTaskColl
ection(SAP__Origin=’ONE_800′,WorkitemID=’000001104681′)/HeaderD
etails?$expand=ItemDetails,Notes,Attachments,ItemDetails/Limits

Step 2. Test OData in the Gateway client
2.1 Copy & Paste the OData URI
Transaction: /IWFND/GW_CLIENT. You should logon with the application
user same as Fiori app logon.
2.1 Check the OData response
If http response is not 200, you may have some connection setting
issue.
If tttp response is 200 but OData service does not return application
data, you should go Step.5 debug section.

Step 3. Check error log
3.1 Transaction /IWFND/ERROR_LOG
Select the “Error Context”
Call Stack helps you to set external break points.
3.2 Transaction /IWFND/APPS_LOG

Reference: Troubleshooting a SAP Netweaver Gateway Service

Step 4. Find the Runtime Data Provider class
4.1 Transaction /IWFND/MAINT_SERVICE
4.2 Transaction SE24
Open the Data Provider Class. Go to Property tab.

4.3 Transaction SE80
Open the package.
Class > Runtime Data Provider Class > Method > Redefinitions
The example OData URI has &expand oprion, so you should look at the
method GET_EXPANDED_ENTITY.

Step 5. Set External break points and debug
5.1 Check the user
Go to Utilities > Settings
Make sure the user is application user.
5.2 Set external break points
5.3 Debug
Test the OData URI from Gateway Client. You can now debug the code.
Most of case, issue is related with ERP customizing or master data.
Each customer has different customizing setting and master data.

Sap fiori ll11 – consultants should know about o data troubleshooting sap blogs

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Sap fiori ll11 – consultants should know about o data troubleshooting sap blogs (6)

More from Nagendra Babu (8)

Recently uploaded (20)

Sap fiori ll11 – consultants should know about o data troubleshooting sap blogs