Default settings generated by the setup program provided by proaxia (transaction /PACG/ECM_SETUP).
Info |
---|
When installing a few service packs one by one, make sure that each service pack’s post-installation steps have been performed. Pay special attention to updating processing classes and transformations. The list of the most up-to-date classes/transformations can be found on the following page: Outbound/inbound message configuration |
Message Type | This is an IDoc message type used in the SAP ERP for unique identification of objects being processed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Inb.Data Creat. | Name of an ABAP class which should be used for processing of an IDOC created in the preceding step. This class must implement interface /PACG/ECM_IF_S_IDOC_INPUT. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Check GUID on input |
If the checkbox ‘Check GUID on input’ is set, the GUID of an incoming object will be checked. If a received message has already been processed, an idoc will be created but its status will be immediately set to 56. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Save XML | With this option enabled original XML received from FSM is stored as an attachment linked to an IDoc created based on this XML document | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| When 'Send Generic' option gets enabled then as a confirmation message /PACG/ECM_GENERIC is sent. This means that Connector sends to the FSM original XML objects which was received from FSM | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Dummy booking |
'Dummy booking' for inbound messages means that a confirmation will be sent to SAP FSM to unblock an object, but no additional processing (saving this object in SAP ECC/S4, creating an SAP document/object) will take place. This functionality works for the following objects:
Available since
Available since
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Error conf | Error messages generated in SAP ECC/S4 for objects modified in SAP FSM will be communicated to the cloud and result in unblocking the objects. Learn more: Error message for blocked objects |
Unknown object handling
Message type /PACG/ECM_CONNECTORUNKNOWN is used for unknown object handling:
This incoming message will be used if any other message cannot be found in the configuration. An idoc of type /PACG/ECM_ITYPE_UNKNOWN_IN will be generated:
The message is confirmed with message confirmation like other messages. Finally, an object error idoc will be sent to SAP FSM:
This message sends error code ‘E/PACG/ECM_MAIN 990’ and error text ‘Unknown message’.