Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

ADD-ON 200 SP 2

This functionality requires the newest version of Message Broker and Transporter (delivered in August, 2020).

List of supported objects

SAP FSM should be provided with a list of incoming (from SAP ECC/S4 perspective) objects supported by FSM Cloud Connector. Based on this list, SAP FSM will not send to SAP ECC/S4 objects which cannot be handled (and may cause issues).

The list of supported objects is sent automatically after each Resend process. It can be also sent manually using the sending transaction /PACG/ECM_TRIG_SUPO - Supported object send:

Connector version

SAP FSM should know the version of FSM Cloud Connector installed on SAP ECC/S4, more precisely the version of component S4PACG/PACG (depending on the system). Based on the transferred list, SAP FSM will or will not allow new functionalities.

Connector version is sent automatically after each Resend process. It can be also sent manually, using the sending transaction /PACG/ECM_TRIG_CONV - Connector version send:

Prerequisites

To enable this functionality, it is necessary to do the no-object assignment (i.e. create entries in transaction /PACG/ECM_NOAS - No Object Assignment) for the following two objects:

  • CONNECTOR_VERSION

  • SUPPORTED_OBJECT

  • No labels