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

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).

The E4C Object type is relevant for Fullsynch (Initial Load). The Fullsync action is triggered by the Cloud (forces initial sending of the data from SAP to the Cloud).

When the objects are sent during Fullsynch, only the objects not older than the given number of days will be considered.

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.

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.