2 weeks ago
Hi Experts,
We have created ODATA V4 Web API using RAP to create Sales Order using EML on I_SALESORDERTP in a custom Action. Once the action method is executed, adjust numbering of this custom API is triggered and the adjust numbering method of I_SALESORDERTP is triggered after the custom API adjust numbering and due to this we are unable to find the Sales Order number during Custom API adjust numbering method.
Why is SAP RAP triggering I_SALESORDERTP Adjust numbering method after the custom API adjust numbering?
Due to this limitation in RAP framework, we are using BAPI - BAPI_SALESORDER_CREATEDAT2 with Destination None as commit is not supported directly in RAP and multiple commits for multiple sales Order update is also not supported.
Do we have any better straight forward solution to this in RAP??
@Andre_Fischer - Could u pls help on this issue?
Thanks,
Vivek
In SAP RAP (RESTful ABAP Programming Model), there are specific mechanisms for transaction control and numbering based on underlying frameworks, such as EML (Entity Manipulation Language). The situation you're describing seems to be related to the call sequence and numbering rules within the transaction processing framework. Here are a few things to consider:
Suggested Solutions:
If you want to dive deeper into the details of the transaction logic and numbering process, debugging sessions or a detailed analysis of the transaction method sequence could help pinpoint the exact cause.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
69 | |
11 | |
10 | |
10 | |
9 | |
7 | |
7 | |
7 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.