With ILM Legal Retention Management, you can apply legal retention to data that needs to remain available for regulatory compliance. The traditional legal case is a container for syntactically bound objects. These objects correspond to the current system and client data on which legal suspensions are to be created. SAP NetWeaver ILM provides functions for creating and managing legal cases and legally holding relevant data. With eDiscovery, you can discover relevant documents. By running the appropriate programs, you apply the locks to the data. Data locked for a court case cannot be deleted or destroyed. The e-discovery report is developed by the customer in cooperation with the respective applications according to the requirement. You need the eDiscovery report to discover documents, such as: Documents for which you want to set legal retention periods. The user can delete legal retention periods created in the past if they are no longer relevant for existing legal requirements. After the legal case has been deleted, the statutory retention periods must be removed from the shop.
In such a case, the user must carry out the propagation of the legal case to the data present in the store. We have now configured an ILM object with a BOR object that defines the BOR object instance key. We also learned how to add BOR objects to a legal case and the steps to customize it. Before we get into the details of ILM legal suspensions, it`s important that we know the following terminologies: Once the legal case is created, objects must be added to a legal case. This object, called Legal Retention, corresponds to a specific BOR object and can be added to a legal case using the Determination of Origin feature module or the E-Discovery report. In a live application system, you can apply legal retention periods for the following categories of data: 3. Deletion of legal cases – Remove legal suspensions created in the past if they are no longer relevant to legal requirements. Thank you for this informative blog!! This was very necessary for customers looking for a legal hold feature!! Good!! The entire process of creating and propagating legal holds to ILM stores can be divided into two categories: 1. Create legal holds for data in database tables and archive files. Concept of multiple origin. BOR (auto-hold with BOR objects) attachments This feature is now enabled in ILM legal holds (see note 2901307 for details).
Once the item has been added to the legal case, it cannot be destroyed even after the expiration date. Indeed, the object key is now part of a legal case and therefore cannot be destroyed. Recently, as countries apply GDPR rules and regulations, companies must increasingly comply with the legislation. ILM legal retention is an additional feature of the ILM infrastructure that ensures legal compliance of data. If you have defined a legal lock for a BOR object that has not yet been checked in and you want to check in the BOR at a later date, the system applies the lock to the ILM store when the deletion is performed. Here, the carrier ID QF with login ID 0006 and flight date 03.09.2019 was part of several archive files and was also in the database. After addition, the storage and distribution of the three archive files is subject to legal retention. Legal retention periods can be set in an online application system. Implementation of the function in a retention warehouse system (for data from decommissioned systems) is planned. Use the Report ARC_LHM_PROPAGATE_LEGAL_HOLD to assign legal hold rights to archived BOR objects added to a legal dispute (in an ILM-certified storage system). You can schedule the report as a recurring task in the background. For a legal case, the following required fields and their details are as follows: A legal case is also enabled to support multiple origin scenarios.
The details of this scenario are explained below. The person responsible for the legal case can select one of these statuses based on the business purpose for which the legal case is created. Enter details about other relevant input fields. With the BOR object key, a legal retention obligation is now applied to the archive file. You can view each legal case from the overview, and then edit or view it. To return to the overview of all legal cases (first input screen), choose Go to overview. You can confirm the assignment of the legal obligation to retain the archive file. Execute the SARA transaction. Enter the archive object as a BC_SFLIGHT.
Press the Manage key. Navigate to the appropriate file (here A00C7V-001BC_SFLIGHT) and double-click it. The file must be enabled for legal retention as follows: 4. Legal Case Status: A legal case can have one of the following statuses: If the legal dispute is still open and you want to unlock a specific object, select the corresponding entry in the list of locked data and choose the Delete Selected Rows push button. To create a legal dispute, follow these steps: You manually add BOR objects to a legal case by using the Determination of Origin function module. Functional modules for origin determination are developed and provided by SAP applications to enable ILM Legal Hold for their application data. To assign data that should be legally blocked to a legal case, choose Next. You can use Report ARLNK_LHM_PROPAGATE_LEGAL_HOLD to define a legal retention requirement for ArchiveLink documents and print lists that are implicitly linked to BOR objects (via TOAx links) and contained in a content repository. We will not discuss this because it is beyond the scope of this blog.
In the SM30 transaction, you can check LHM_METHODS whether a specific BOR object is enabled to manually add BOR objects to a legal case. View attachments to BOR objects (attachments associated with BOR objects are automatically included in the legal retention obligation). For example, long-term HR documents have the BOR object as PA_LDOC and the BOR object key as the employee number – PERNR. A single employee number can appear in multiple archive files and database records. The BOR object key definition cannot uniquely identify a single instance of this object, resulting in a multi-origin scenario. Here, legal retention periods must be activated for all records (database entries and archive files) in which this employee number exists. In the following figure, the top section corresponds to a legal case and the lower section with the objects added under the BOR objects corresponds to legal suspensions. To apply locks to archived BOR objects or ArchiveLink references (in the ILM store), periodically schedule the following programs in SAP background processing: To add an object to a legal case, follow these steps: You use the priority and status of a legal case as selection criteria.
Exception: The Closed status is a prerequisite for deleting a legal record. The distribution of legal deductions is a manual activity. This should happen once the legal cases in ILM_LHM transaction have been created/deleted. 1.Legal Case Name: Custom name for a legal matter. The Add Objects in a Legal Case button can be used to add objects to a legal case, as shown in the following figure. If a BOR object that has not yet been checked in is added to a legal file and then checked in, the legal lock for that BOR object is set along with the delete program for archiving that runs in the storage system, so the report is not required in this case. 2.Priority: Select the priority relevant to the legal case in the input help. Legal holds are propagated at the legal case level, which means that the user can find the GUID of the legal query defined for the file in the archive store.