/PACG/ECM_CLSASSIG - FSM Connector's Outgoing Messages Configuration

The settings for the outbound messages:

Message Type	This is an IDoc message type used in the SAP ERP for unique identification of objects being processed
Message Code	– not used --
Message Function	– not used --
Channel	This is a name of ABAP class which is responsible for sending data to the external receiver which is Message Broker. The class must implement the interface /PACG/ECM_IF_S_CHANNEL.
IDoc Class	This is ABAP class name, which is used for IDOC generation. It MUST implement the interface /PACG/ECM_IF_S_IDOC_OUTPUT and the method IDOC_OUTPUT. This method must return filled IDOC structure.
Data selection	This is ABAP class, which is responsible for data selection. It MUST implement the interface /PACG/ECM_IF_S_DATA_SEND and the method SEND. For given object keys it calls the IDOC creation process.
Process Code	Code is used to identify function module used for IDoc processing. This is a part of standard ALE mechanism in SAP ERP
Transformation	Name of XSLT transformation used for translating IDoc into XML
Cloud message type	External message type name - used to link SAP ERP message type with its FSM counterpart
Rel. for resend	The E4C Object type is relevant for Resend. The Resend action is triggered by the Cloud (forces resending of the data from SAP to the Cloud).
FullSync relevant	The E4C Object type is relevant for Fullsync (Initial Load). The Fullsync action is triggered by the Cloud (forces initial sending of the data from SAP to the Cloud).
FSync Max Age	When the objects are sent during Fullsync, only the objects not older than the given number of days will be considered.
Use Hash	Once the given object in SAP is changed, it is sent to the Cloud automatically and store in hash DB. The Cloud contains normally the subset of the fields of the SAP objects. Sometimes there are changes in SAP, which are not relevant for the Cloud as they refer to non-relevant fields. Resending of the object in that case will not harm but produces unnecessary data transmission. The comparison if a relevant change happened based on stored hash in DB and the hash generated from actual field contents. Thereby for some objects (e.g. Material) a check is foreseen: if the change is not Cloud-relevant, then the object data does not have to be sent. The usage of this check can be activated / deactivated by this flag per object. Please note that starting from Release 2202, use hash option will be always defaulted to true and hidden from the view.
ADD-ON 200 SP04 Action not needed	For each outgoing object, it is possible to define an action after calling BADI not needed (/PACG/ECM_OBJ_NEEDED) results as true (in parameter cv_not_needed) - meaning the object is not needed in FSM. The possible options include: Set to inactive – send the object as inactive Soft delete – send the object as soft deleted Delete – send the object as hard deleted Do not send to FSM – the object won’t be sent to FSM; because of backwards compatibility, it is the standard value The field is useful if an object used to be relevant for the cloud, but then stopped. Using the BAdI, it can be determined as such and then sent as inactive/deleted to FSM.