Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourYellow
titleADD-ON 200 SP 2

Info

This functionality requires the

newest version of

Message Broker 3.1 and higher.

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:

Image Removed

. It contains all inbound message types (other than CONNECTORUNKNOWN) maintained in /PACG/ECM_CLSASSIGIN - FSM Connector's Incoming Messages Configuration.

Supported objects are then visible in SAP FSM Admin module, in the tab ‘ERP Connector’:

image-20240418-064956.pngImage Added

Once a given supported object was sent, it cannot be removed from that list via resending the supported object list with /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:

Image Removed

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

Additionally, the setup program should be executed, with the option below checked: