Push asynchronous RFC execution over Queue (SMQR)
If program takes much time to execute synchronous FM calls, then we can send it to Queue (created in TCode SMQR) which will execute asynchronously. It can be useful when Non SAP calls SAP and that will have some time limitation. While sending to Queue, acknowledgement can be provided to Non SAP and Queue RFC
Key as Segment in V4 oData RAP
In Odata usually the entity can be accessed by providing the KeyValue in canonical form. But now in RAP V4 oData services, the entity can be accessed by appending a segment containing the unquoted keyvalue to the URL. Single Key- /service/Employees(‘A1245’) =>New Way : /service/Employees/A1245 MultiPart Key /service/OrderItems(OrderID=1,ItemNo=2) =>NewWay: /service/OrderItems/1/2 The below is a V4
Converting UUID to hyphened UUID
While working with oData and testing around these, then found that the gateway client receives the UUID in a slightly different format(Hyphened format) than the UUID are stored in the table. UUID Raw format- 0050563C56401D36A348F362444845FC UUID Hyphened format- 0050563c-5640-1d36-a348-f362444845fc The test tool may be gateway client/postman need the Hyphened format. The class- CL_SOAP_WSRBM_HELPER provides utility
SAPCODES 