SAP Fiori LL11 - Consultants Should Know About

7/24/2019 SAP Fiori LL11 - Consultants Should Know About ..

1/8

21/02/2016 SAP Fiori LL11 - Consultants should know about ... | SCN

http://scn.sap.com/community/mobile/blog/2013/11/13/sap-fiori-ll11--consultants-should-know-about-odata-troubleshooting

Getting Started Newsletters Store

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Log On Join UsHi, Guest Search the Community

Activity Communications Actions

Browse

SAP for Mobile

1 Tweet

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 shou ld l earn ab out OData techni cal an d 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

SAP Fiori LL11 - Consultants should know aboutOData troubleshooting

Posted by Masayuki Sekiharain SAP for Mobile on 13-Nov-2013 11:32:03

Share 8 3Like
http://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322841/inspect.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322841/inspect.pnghttp://scn.sap.com/people/masayuki.sekiharahttp://scn.sap.com/community/mobile/bloghttp://scn.sap.com/community/mobile/blog/2013/11/13/sap-fiori-ll11--consultants-should-know-about-odata-troubleshootinghttp://scn.sap.com/people/masayuki.sekiharahttp://scn.sap.com/community/downloadshttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322841/inspect.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322841/inspect.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322841/inspect.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322841/inspect.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322841/inspect.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322841/inspect.pnghttp://scn.sap.com/people/masayuki.sekiharahttp://scn.sap.com/community/mobile/bloghttp://scn.sap.com/people/masayuki.sekiharahttp://scn.sap.com/community/mobile/blog/2013/11/13/sap-fiori-ll11--consultants-should-know-about-odata-troubleshootinghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322841/inspect.pnghttps://twitter.com/intent/tweet?hashtags=scn&original_referer=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Fmobile%2Fblog%2F2013%2F11%2F13%2Fsap-fiori-ll11--consultants-should-know-about-odata-troubleshooting&ref_src=twsrc%5Etfw&text=SAP%20Fiori%20LL11%20-%20Consultants%20should%20know%20about%20OData%20troubleshooting&tw_p=tweetbutton&url=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Fmobile%2Fblog%2F2013%2F11%2F13%2Fsap-fiori-ll11--consultants-should-know-about-odata-troubleshooting&via=SAPCommNethttp://scn.sap.com/community/mobile/blog/2013/11/13/enterprise-mobility-strategy-the-details-a-mobile-enabled-company-needs-to-think-abouthttp://scn.sap.com/community/mobile/blog/2013/11/11/cloud-solution-integrationhttp://scn.sap.com/community/mobile/bloghttp://scn.sap.com/contenthttp://scn.sap.com/actionshttp://scn.sap.com/communicationshttp://scn.sap.com/activityhttp://scn.sap.com/login.jspahttp://scn.sap.com/community/mobile/blog/2013/11/13/login.jspahttp://scn.sap.com/community/uachttp://scn.sap.com/community/developer-centerhttp://scn.sap.com/community/downloadshttp://scn.sap.com/welcomehttps://www.sapstore.com/?url_id=banner-US-2015-SCN-HeadLinkhttp://scn.sap.com/community/newslettershttp://scn.sap.com/community/getting-started


2/8



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://.:

/sap/opu/odata/sap/GBAPP_POAPPROVALmo/WorkflowTaskCollectio n(SAP__Origin='ONE_800',WorkitemID='

$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 applica tion 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.
http://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322895/data.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322879/gw_client.pnghttp://anvm100.sapcoe.sap.com:8080/sap/opu/odata/sap/GBAPP_POAPPROVAL;mo/WorkflowTaskCollection(SAP__Origin='ONE_800',WorkitemID='000001104681')/HeaderDetails?$expand=ItemDetails,Notes,Attachments,ItemDetails/Limitshttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322877/odata.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322851/refresh.png


3/8



If tttp response is 200 but OData service does not return applica tion 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
http://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322920/stack.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322919/call_stack.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322917/error_log.png


4/8



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.
http://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322938/class.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322937/maint_service.pnghttp://scn.sap.com/community/gateway/blog/2013/08/09/frequent-problems-encountered-in-netweaver-gateway-service-developmenthttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322921/app_log.png


5/8



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
http://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322951/debug2.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322950/map2.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322949/class2.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322942/package.png


6/8



Average User Rating

(20 ratings)

1 Tweet

Make sure the user is applicatio n 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.

Regards,

Masa

SAP Rapid Innovation Group - RIG

30847 Views Tags: fiori

Share 8 3Like

15Comments

Like (0)

Syam Babu13-Nov-2013 14:28

Excellent Stuff and it's covered GW Debugging alsoThanks,Syam

Like (0)

Hemendra Sabharwal29-Dec-2013 13:09

Great stuff, thanks for sharing.

Pradyp Parakala29-Dec-2013 13:15

Excellent stuff MasaKeep posting more
http://scn.sap.com/people/pradyphttp://scn.sap.com/people/hemendra.sabharwalhttp://scn.sap.com/people/syambabu.alluhttp://scn.sap.com/community/mobile/blog/tags#/?tags=fiorihttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322965/method.pnghttp://scn.sap.com/servlet/JiveServlet/showImage/38-96859-322964/debug_user.pnghttps://twitter.com/intent/tweet?hashtags=scn&original_referer=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Fmobile%2Fblog%2F2013%2F11%2F13%2Fsap-fiori-ll11--consultants-should-know-about-odata-troubleshooting&ref_src=twsrc%5Etfw&text=SAP%20Fiori%20LL11%20-%20Consultants%20should%20know%20about%20OData%20troubleshooting&tw_p=tweetbutton&url=http%3A%2F%2Fscn.sap.com%2Fcommunity%2Fmobile%2Fblog%2F2013%2F11%2F13%2Fsap-fiori-ll11--consultants-should-know-about-odata-troubleshooting&via=SAPCommNet


7/8



Like (0)

CheersPradyp

Like (0)

Johan Schtt26-Jun-2014 09:54

Super stuff. The most useful stuff I come a cross for a long time.Johan

Like (0)

Tauhid Hasan Shaikh14-Dec-2014 07:50very nice. very userfull suff.............tTauhid

Like (0)

Valmiki Jansi22-Jan-2015 12:27

What does it mean if the status code returns 500 when I execute my oData URI in Transaction:/IWFND/GW_CLIENT instead of 200

Like (2)

Masayuki Sekihara 23-Jan-2015 04:27 (in response to Valmiki Jansi)

500 means internal server error. List of HTTP status codes - Wikipedia, the freeencyclopedia. Most of cases, system connection has not been setup or there was shortdump in he backend. Please create new discussion if you need further support. Start adiscussion .

Like (0)

Toni Freytag18-Feb-2015 10:18

Hello Masu,thanks a lot - great stuff. Helps me a lot for understanding.Regards Toni

Like (0)

Mr Eli02-Mar-2015 15:49

Hi

Excellent blogI can see the tiles in Chrome and not in IE. I also can see the OData URI in Chrome and not in IE. Anyidea of what might be the cause?Kind regards

Like (0)

Veronika Bakhtalovskaya26-Apr-2015 12:01

thank you! very helpful doc!

Like (0)

Venkata Anjaneya Karthick Kolisetty13-May-2015 17:16

Thank you. This helped me to resolve an issue.

Like (0)

Deborshi De Sarkar18-May-2015 16:45

Thanks you...very use full document.

Like (0)

Liang Hu22-Sep-2015 06:09

Thank you! It is a great document.BTW, is there any list for all LL documents for Fiori?

Michael Appleby22-Sep-2015 14:40 (in response to Liang Hu)
http://scn.sap.com/people/michael.applebyhttp://scn.sap.com/people/leon.huhttp://scn.sap.com/people/deborshi.desarkarhttp://scn.sap.com/people/venkataanjaneyakarthick.kolisettyhttp://scn.sap.com/people/veronika.bakhtalovskaya2http://scn.sap.com/people/willard.chingarande4http://scn.sap.com/people/freytag.tonihttp://scn.sap.com/community/mobile/post!input.jspa?containerType=14&container=2056&tags=fiorihttp://en.wikipedia.org/wiki/List_of_HTTP_status_codeshttp://scn.sap.com/people/masayuki.sekiharahttp://scn.sap.com/people/valmiki.jansihttp://scn.sap.com/people/mr.tauhidhttp://scn.sap.com/people/johan.schtt2


8/8



Follow SCNSite Index Contact Us SAP Help Portal

Privacy Terms of Use Legal Disclosur e Copyr ight

Like (0)

SAP Fioriwill take you to the Fiori community Overview page. Check out the All Things SAP Fiori rightin the middle. It is where all thing s Fiori are organized for easy access.Cheers, MikeSAP Technology RIG

Like (0)

Jeremy Good22-Sep-2015 15:28 (in response to Liang Hu)

As Mike men tioned the more recent "SAP Fiori LL" blo gs are located in the SAP Fiori space,and as you've seen with this one, the older blogs are located in the SAP for Mobile space.There is no master list, but you will find them linked on their correlated topic pages in the All

Things SAP Fiori document. The title format is consistent, and Masa is the author, so acreative searchmight help you.
http://scn.sap.com/people/masayuki.sekihara/content?query=SAP%20Fiori%20LL&sortKey=contentstatus[published]~subjectAsc&sortOrder=1&filterID=contentstatus[published]~objecttype~showallhttp://scn.sap.com/people/jeremy.goodhttp://scn.sap.com/community/fiorihttp://www.sap.com/corporate-en/our-company/legal/copyright/index.epxhttp://www.sap.com/corporate-en/our-company/legal/impressum.epxhttps://accounts.sap.com/ui/public/viewTextResource?scenario=SCN&spId=504efd8ee4b0555c3c17b94e&resourceType=RESOURCE_TERMS_OF_USE&version=1&spDisplayName=SAP%20Community%20Network&locale=enhttps://accounts.sap.com/ui/public/viewTextResource?scenario=SCN&spId=504efd8ee4b0555c3c17b94e&resourceType=RESOURCE_PRIVACYPOLICY&version=1&spDisplayName=SAP%20Community%20Networkhttp://help.sap.com/http://scn.sap.com/docs/DOC-18476http://scn.sap.com/docs/DOC-19361http://spr.ly/SCNgoogleplushttp://bit.ly/SCNyouThttp://bit.ly/SCNFBhttp://bit.ly/SCNTwR

Documents

SAP Fiori LL11 - Consultants Should Know About