Message Flows

From SAP to FSM

Open

• Events are triggered, if relevant, directly from ABAP code – we used enhancements and standard BADIs. The Events used by connector rely on SAP Business workflow – configuration in SWETYPV

• In addition to standard mechanism, Connector implements own solutions that help control events execution like /PACG/ECM_EVTD where events can be disabled and enabled

• All Connector’s events classes implement standard interfaces:

  • BI_EVENT_HANDLER_STATIC

  • BI_OBJECT

  • BI_PERSISTENT

  • IF_WORKFLOW

• Selection class selects (or confirms validity) of object that must be sent to FSM. Selection classes must implement /PACG/ECM_IF_S_DATA_SEND interface.

• Idoc creation class is responsible for selection data that must be sent to FSM. Idoc output classes must implement /PACG/ECM_IF_S_IDOC_OUTPUT interface.

• Class assignment for outbound processing is configured in transaction /PACG/ECM_CLSASSIG

• Then Idoc is forwarded to regular processing queue to be eventually passed to dedicated port function

• Port function /PACG/ECM_S_PORT is part of Connector solution. It handles conversion to XML and sending message to message broker (web service call). It is configured in the standard transaction WE21

• Port definition is one of the prerequisites before Connector’s setup can be run

From FSM to SAP

Open

• Inbound XML message is initially passed to conversion class where XML object is mapped into Idoc based on configured transformation

• Inbound conversion classes must implement /PACG/ECM_IF_S_XMLIDOC interface

• The Idoc is then passed to regular processing queue and eventually is passed to inbound processing class. This class must implement interface /PACG/ECM_IF_S_IDOC_INPUT