SAP B1If 2.0 - How to adjust Synchronous Step and Call Scenario Step from SAP B1If 1.x?

[rafael_ogeda]

Hi friends!

We are migrating some API HTTP REST packages from SAP B1If 1.x to SAP B1If 2.0.

In these API HTTP REST packages we have strongly used the strategy of using microservices as scenario step called Synchronous Call. But in the Migration Guide we saw that SAP B1If haven't support for Synchronous Call Steps...

Ouse use cases:

1. HTTP REST API services have a main scenario (eg igt.Sellets = HT (CALL,SYNC), Identification Method=RESTful), which identifies the HTTP method using /vpf:Msg/vpf:Body/vpf:Payload[@Role='T']/vpf:http.method and directs the synchronous flow to a secondary scenario for GET (eg igt.getSellers = IQ (INTQ,ASYN)) or PUT (igt. insSeller = IQ (INTQ,ASYN)). These secondary scenarios process synchronously and return the processing response (GET or PUT) to the main scenario. In this case, the Synchronous Call response is used in the main scenario.
2. All API monitoring is performed by synchronous processes. These secondary scenarios insert or update records in UDT for monitoring API requests and transactions in SAP Business One. In this case, the Synchronous Call response is not used in the main scenario.

We think of these solutions:

1. API Service: Instead of having 3 scenario steps for an API REST HTTP service, we can change to 2 scenario steps (one for GET and one for PUT), thus eliminating the main scenario that performed the synchronous call.
2. Monitoring: we can change all Synchronous Calls to Asynchronous Calls and so we will have queues for Monitoring.

But in both cases we are in doubt which is the best solution to use after the migration performed by SAP B1If 2.0?

Does anyone have any recommendations for these atom Call Scenario Step use cases that are not supported by SAP B1If 2.0?

[rafael_ogeda · Accepted solution]

Hi friends!

We found an alternative to call Synchronous Step in SAP B1If 2.0, as explained below.

In the main step, where the synchronous step is called, we change the "Call Scenario Step" com Mode="#Synchronous Call" to "Include".

In the synchronous step, called by main step, we change Inbound to "ENQI" and Outbound to "ENQO".

In this way, the Synchronous step is called by main step and returns to main step when concluded.

Best regrads!