Please contact support before using.
Starting from service pack 7 for add-on version 200, access to this transaction is controlled by authorization object /PACG/E010, activity 06. Learn more: FSM Cloud Connector Authorizations Objects and Roles
With this transaction objects sent to the cloud can be deleted from there.
Apart from the Company ID and Cloud message type (e.g. Region) - SAP Key or GUID value is needed:
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,
S4 PACG 200 SP15 In exceptions, when an SAP object has not been created for an FSM object, deletion can be done by providing the GUID. The GUID value can be found via FSM Query API in ID column.
In case of attempting to delete many objects of the same message type at the same time, navigate to multiple selection.
Values can be pasted from the clipboard using the selected icon.
To prepare a list of object 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 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_’.
3. Concatenate the values of the first and second column. The final result should mirror the ID value in the example above.
4. Copy and paste the values from column C into the multiple selection window of the deletion program.
After executing, idocs of basic type /PACG/ECM_ITYPE_OPERATION and message type /PACG/ECM_OBJDELREQ are sent to the cloud. They contain the SAP Keys of deleted objects.
Successful execution, apart from confirmation logs, can be checked by creating a query in FSM.
