In this article, we provide a summary of common integration and extensibility questions collected on SAP S/4HANA Cloud Public Edition to reflect the latest developments and changes to frequently asked questions on SAP S/4HANA Cloud Public Edition. In this way, we would like to provide you with a comprehensive and timely resource to help you better understand and take advantage of the functionality of your SAP products.
Common Errors
Problem 1: "TOO_LARGE_BODY" error returned during API call.
Answer: The error "TOO_LARGE_BODY" is returned because the HTTP response is too large, the relevant parameter is (icm/HTTP/max_request size MB), it is recommended to add a parameter $top to limit the number returned, for example, A_PurchaseRequisitionItem? $format=json&$top=100. You can find this in note https://me.sap.com/notes/0003366726 .
Question 2: You cannot create a custom field with the same ID, even if the previous field has been deleted
Answer: This is a known limitation that even if a previously created duplicate custom field has been deleted, you cannot create a new custom field with the same ID as the previously transferred field. It is recommended that customers create new fields with new identifiers and then only use the same description. Details can be found at KBA: https://me.sap.com/notes/3073680 .
Question 3: Postman tests SOAP API reports 500 errors
Answer: The following blog can be referenced: https://blogs.sap.com/2019/09/10/guidelines-for-testing-journal-entry-api-with-soapui-and-checking-r... Part 3, how to test asynchronous APIs.
Question 4: Error "Project of type Custom CDS view must not be edited in this tenant"
Answer: Custom CDS views are part of key user extensions and are therefore only allowed to be changed in the quality/development system, not in the production/test system. Key user extension changes need to be transported together with the Export Soft Collection app and the Import Software Collection app.
Question 5: Change of requested delivery date via Odata API API_SALES_ORDER_SRV but update failed
Answer: This is a known issue, Deep insert of schedule lines is not supported in the sales order creation through the OData API Sales Order (A2X), specifically you can view the KBA https://launchpad.support.sap.com/#/notes/3036121 .
Question 6: Call the OData API of sales order to get all the data, there are about 30000 pieces of data in the system. The return error message is "Error: Maximum response size reached"
Answer: The solution is to change the "Max response size in MB" setting in Postman's settings from 50 to 5000, and then get all the data successfully. The KBA documentation can be found in detail: https://itsm.services.sap/now/nav/ui/classic/params/target/kb_view.do%3Fsysparm_article%3DKB0546967
Question 7: An error is raised when a one-time customer calls the sales order Odata API
Answer: If the customer is a one-time customer, the necessary address information needs to be provided in the payload request, otherwise an error will be reported. You can refer to SAP Note https://me.sap.com/notes/3085492 .
Question 8: Checking CDS for errors: "Data type CURR is not supported at this position"
Answer: To be able to use these fields, one of the following functions needs to be applied to convert the value of the CURR element:
CURR_TO_DECFLOAT_AMOUNT (converts CURR fields to DECFLOAT34 fields,)
GET_NUMERIC_VALUE (Remove the reference information from the DDIC metadata, including the shift of the CURR element.)
Guide Relevant
Question 1: How do I add and subtract dates?
Answer: the function DATS_ADD_DAYS adds days to a specified date.
If the number of days is positive, add the number of days to the date. In other cases, the number of days is subtracted. If the calculation produces an invalid date, the error is handled as specified in on_error.
Question 2: Cannot use APPCustom CDS Views in Starter system
Answer: In the SAP S/4HANA Cloud system (Starter or partner demo system), extensibility for key users is not activated by default. Extensibility for key users can be activated. You can activate extensibility yourself. Open the Fiori app Extensibility Settings and follow the activation process. For more information, see 2283716 - Key User Apps Not Configured https://launchpad.support.sap.com/#/notes/2283716 .
Question 3: Add a new custom field to the app “Post General Journal Entries” which business context should be selected
Answer: You can refer to the SAP Help documentation: https://help.sap.com/docs/SAP_S4HANA_CLOUD/0fa84c9d9c634132b7c4abb9ffdd8f06/e5defe0a850948d1bd7a2834...
Consulting-Relevant
Question 1: What is the effective time for CSRF Token?
Answer: The default CSRF token is 24 hours (86400 seconds), but this validity period is related to security session and depends on the value of system parameter http/security_session_timeout. Inside S4HC, the value of http/security_session_timeout is 30 minutes, so CSRF token is valid for 30 minutes in S4HC.
Question 2: Want to read fixed asset master data via API, but found that CDS View I_FixedAsset cannot be used as a data source for custom cds view
Answer: I_FixedAsset can be used by in-app extensions, except that the data sources in the custom cds view are automatically filtered. If you want to see other data sources, on the select primary data source page, select show filter and set recommended data source to No. Details can be found in the KBA https://me.sap.com/notes/3148426 .
Question 3: Whether the SAP interface has a limit on the amount of data and the number of times it has been acquired, the data is not returned, and no error is reported. There is no return of interface data in successive attempts
Answer: The External API scenario is not available for one-time mass data extraction. For optimal performance, the client needs to use appropriate filters and/or paging to limit the requested data. For more information, check out the following link:
https://launchpad.support.sap.com/#/notes/2692128
Question 4: I want to read the field "RequirementTracking" on the API API_PURCHASEORDER_PROCESS_SRV for purchase orders and found that it is not possible to find it
Answer: There is no such field on the OData V2 API. However, the field is available on the API CE_PURCHASEORDER_0001 for OData V4. If the customer needs to read the field, they can consider using the API of V4.
Question 5: Using the OData API (SAP_COM_0057) to create supplier invoices, but found that there is no duplicate check in the API
Answer: To do the duplicate check in the API, you need to specifically activate it in the configuration of invoice verification. Message class M8 message 804,805 needs to be set to error, see Note https://me.sap.com/notes/2721713 .
Question 6: Create sales order from a third-party system by calling the Sales order Odata API, and find that the performance is not good. It takes 60-70 seconds to create a data
Answer: The user gets the full amount of data when taking the token, but in order to get the token only need to take a piece of data, I suggest adding it at the end of the URL? $top=1&$inlinecount=non.
