What is the use of CSA queues in CRM middleware

We sometimes observe a queue starting with a CSA in the transaction code SMQ2 of the middleware, the inbound Queue Viewer:

What are the roles of these queues? Many friends have asked the same questions on SAP community, and experts have answered the following two connections:

http://scn.sap.com/thread/2056716

http://scn.sap.com/thread/2079157

Simply put, each time the object in the CRM system is modified, if the object is set in the background configuration to synchronize its modifications to other receivers, these CSA queues are automatically generated, and the modifications are synchronized to other receivers through these queues.

Before 167 lines are executed, the status of Bdoc is as follows:

After 167 lines have been executed, the Bdoc state has changed.

All listener lists registered with the CRM BDOC Hierarchy_prod change are returned through the function module smw3_flow_getlist.

For Bdoc Hierarchy_prod, there are currently three registered listeners in the system I am using:

When changes occur, these listeners are executed in the Smw3_flow_execute loop.

For more details, see the discussion issue of the two SAP community mentioned at the beginning of the article.

To get more original Jerry's technical articles, please follow the public number "Wang Zixi" or scan the QR code below:

What is the use of CSA queues in CRM middleware