...
Apart from the Company ID and Cloud message type (e.g. Region) - SAP Key or GUID value is needed:
...
| Note | ||||
|---|---|---|---|---|
Deletion by FSM GUID is supported with Message Broker version 4.6 (9.2.1.0) and newer.
|
when the SAP object has a corresponding FSM object in the cloud - the SAP key can be used. The value can be found in the ‘ID’ field of an outbound idoc which transferred a given object to the cloud,
...
To prepare a list of object key SAP Key values, a few steps must be taken.
1. Create a query in FSM to get a list of desired object codes. An example query for region objects - Select r.code from Region r (where r.createDateTime < '2020-03-17T11:47:49Z'). Then copy the codes into a spreadsheet.
...
2. Find out how the key SAP Key (ID) is constructed for a given object by examining idocs which sent an object of this type to the cloud. Copy into another column of the spreadsheet a part of an ID which doesn’t contain a specific code but is a template for all ID’s sent for this type of objects. In the example below this would be ‘/PACG/ECM_REGION_’.
...
After executing, idocs of basic type /PACG/ECM_ITYPE_OPERATION and message type /PACG/ECM_OBJDELREQ are sent to the cloud. They contain the keys SAP Keys of deleted objects.
...
Successful execution, apart from confirmation logs, can be checked by creating a query in FSM.
...