Versions Compared

Key

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

Following implementation of Retention Policies in the FSM (for more check here) the handling of a new message type got introduced in the Connector. This message <DATADELETEDEVENT> is sent by FSM when objects get removed. Connector by itself does not delete in the backend system any object removed in FSM as a result of implementation of Retention Policy however information about these

...

deletions are stored in the dedicated table

...

- /PACG/ECM_DELEVT

In order to make use of these information one must implement BADI /PACG/ECM_DELETE_RETENTION. This BAdI has only one method DELETE_RETENTION which accepts two parameters:

  • IV_COMPID - connector’s company Id

  • IS_DEL_EVN - a structure that contains information about deleted object.

The structure IS_DEL_EVN, of type /PACG/ECM_IS_DELETE_EVT contains in turn following information (and these information are also stored in /PACG/ECM_DELEVT table.

  • ID - the id of the message itself

  • CREATEDATETIME - time stamp of an sent

  • TRANSACTIONID - id of transaction in FSM

  • OBJECT - the SAP key of the object

  • OBJECTID - the FSM guid of the object

  • DELETIONTYPE - deletion type HARD/SOFT, informs if deletion in FSM is reversible

  • DELETIONREASON - deletion reason RETENTION/MANUAL, informs if deletion was initiated by retention policy or user’s action

  • OBJECTTYPE - type of deleted object

EXAMPLE:

ID F520E3F9535F4D5FA6D29D35A35A358C
CREATEDATETIME 2024-05-13T00:07:32Z
TRANSACTIONID 118885
OBJECT 000000000010014256
OBJECTID 5E00710E4A0E4BA19DD13B2A68DCEBED
DELETIONTYPE HARD
DELETIONREASON RETENTION
OBJECTTYPE EQUIPMENT

Deletion Report

In order to help keeping the size of /PACG/ECM_DELEVT within the limits a dedicated deletion report was implemented /PACG/ECM_DEL_DELEVT - Delete table /PACG/ECM_DELEVT