General process overview

The diagram below demonstrates generalized inbound idoc processing (SAP FSM → SAP ECC/S4).

Detailed process example

Detailed description of the inbound idoc processing. In this scenario an activity is modified in SAP FSM and transferred to SAP ECC.

Initial message input handling

When an inbound message comes from the Message Broker, the following web service is executed:

The web service’s function /PACG/ECM_S_WSINPUT calls method /PACG/ECM_CL_S_INPUT=>INPUT.

Then within this method, the function /PACG/ECM_S_INPUT is called.

The process continues in the method /PACG/ECM_CL_S_INPUT=>INPUT_ONLINE. The IT_INPUT table contains the XML.

XML to idoc conversion

XML to idoc conversion takes place in the method PROCESS_INPUT of class /PACG/ECM_CL_S_COM_FACADE.

Based on the inbound class assignment configuration, the conversion class is determined.

The data is then converted to the idoc stucture.

Post-conversion processes

After successful conversion the idoc is stored.

Relevant confirmations are sent back to SAP FSM.

Idoc input class

In the function module /PACG/ECM_S_IDOC_INPUT, the idoc input class is determined based on the inbound class assignment configuration. The interface method /PACG/ECM_IF_S_IDOC_INPUT~IDOC_INPUT of the activity idoc input class is then called.

In the Idoc input class the idoc data is distributed to internal tables, separate for each segment.

Object-specific logic determines what should be done with the received data (e.g. how idoc field values should be mapped with SAP tables in order to correctly modify/create objects in SAP). For activities the most significant actions take place in method /PACG/ECM_IF_I_ACTIVITY~PROCESS_SALES_ACTIVITY.

After the idoc input class processing (back in function /PACG/ECM_S_IDOC_INPUT) the document status is set.