Middleware flow analysis

This diagram can be useful for middleware understanding:

Journey from ECC to CRM.

1. Data is written in to the BAPI structure in the R/3 system  > written to the outbound queue

2. Data is processed automatically and than written to the  inbound queue in the CRM

3.  R/3 adapter is processing data. Mapping function is done BAPI is converted into mBDOC.

4. mBDoc is saved in the CRM system.

5. Bdoc validation is done by validation service. During validation CSA* queues are triggered, Replication service is linked in the MO* flow

6. If no errors detected, data is saved to the Online DB and now it is available for the CRM users. If there are errors (Validation error) data is not written to the online DB and is not available for the CRM users

Journey from CRM to ECC.

1. Data was changed in the CRM online DB by the CRM user

2. Validation of the data is done directly in the dialog

3. Changes are written to the CSA* queues

4. Replication service is called it determines the system to which data need to be send

5. R/3 outbound adapter is processing data (converting mBDoc to other format XML or BAPI)

Tables that are used during communication:

If we want to analyse time that was spent in the middleware part, we can use the following trx. SMWMFLOW > message flow statistics. 

No let have a look on the time distribution: 

Inbound time: 

Outbound time: