on 2020 Apr 22 4:30 AM
Hi community colleagues,
I am building an extension using (or trying to use) In-App extensibility only.
One of the requirements is to Update Purchase Order. To achieve that, I am coding a custom reuse elements to be called later in a custom business object.
The API_PURCHASEORDER_PROCESS_SRV is the one I will use for. I use these tutorials:
https://developers.sap.com/tutorials/abap-extensibility-cbo-execute-outbound-service.html
Here´s what I did already:
1. creation of custom communication scenario
2. creation of custom outbound service for API_PURCHASEORDER_PROCESS_SRV
3. code
3.1. check service availability
3.2. create client
3.3. service request (get)
3.4. send request and read response
By reading the body, I don´t get JSON data, but some HTML codes. I am not able to read the full message as the string message is limited to 255 characters.
The portion of the body as follow:
"<html><head><meta http-equiv="cache-control" content="no-cache" /><meta http-equiv="pragma" content="no-cache" /></head><body onload="javascript:var url=window.location.hash;if(url&&(0!==url.length)){document.cookie="oucfarwteufowwvvoreeaozecdowqczbz"
My bet is the system is being redirected to IdP to validate the user.
At this point, I´d like to ask some guidance:
1) Did I get the right idea on how to update Purchase Order? or is there another recommended way (best practice)?
2) If so, any idea on how to overtake this issue? did I miss any setup in S/4HC?
BR,
Pietro
Request clarification before answering.
I found the root cause of this issue.
Using In-App extensibility, if you need to call a whitelisted API (standard) you´re gonna use two communication scenarios:
1) outbound service point to path /sap/opu/odata/sap (custom communication scenario).
2) inbound service for the standard API (e.g., SAP_COM_0053).
BR,
Pietro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
102 | |
15 | |
9 | |
7 | |
5 | |
4 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.