- SAP Managed Tags:
Introduction
When an application data reaches end-of-purpose and is no longer required for the ongoing business, the data in the database system is moved to an external storage file system via archiving. SAP recommends this process of data archiving for improved system's performance and reduced maintenance cost.
In SAP Commercial Project Management (CPM), every business object has its own archiving object. There may be dependencies between them. For this reason, some objects can be archived only when you have completely archived the dependent data. For more details, refer the section 'Validation during Archiving Process'. Below is the list of archiving objects in CPM.
Archiving Object
| Archiving Object | Description |
| /CPD/PWS_M | Master Projects |
| /CPD/PFP_P | Plan Header |
| /CPD/MC_H | Milestone Checklist Header |
| /CPD/MC_I | Milestone Checklist Items |
| /CPD/RM_I | Risk Management Archiving Object |
| /CPD/RM_A | Risk Action Items |
| /PICM/BO_I | Issue and Change Request |
| /PICM/BO_A | Activities |
The archiving process is mainly divided into three parts:
- Preprocessing
- Writing
- Deleting
Preprocess: This step applies the check program that selects the data to be archived. If the selected data of the business object pass all the checks, the status is set to 'Archiving in Process'.
Write: This step consists of the actual archiving session. The data of the objects with the status 'Archiving in Process' is written sequentially to the archive files.
Delete: This step removes the newly archived data from the database. The system reads the archive files created during the write process, and if this is successful, the system removes the data from the database. The system also generates an archive index during this process to allow faster read access.
When the Infostructure is activated in CPM, a transparent table with prefix ‘ZARIXCA*’ is generated. In CPM, the Field catalogs and Infostructures exists with the same name as archiving objects. For example, the archiving object '/CPD/PWS_M' has an infostructure '/CPD/PWS_M' and the field catalog '/CPD/PWS_M'.
Validation during Archiving Process
To archive a business object, all the dependent objects should be archived. Below table shows the dependency relation of the business objects:
| Business Object | Dependent Business Object |
| Commercial Project | PS Project, Financial Plan, Milestone Checklist, Issue & Change Request, Risk |
| Milestone Checklist | Milestone Checklist Activity |
| Issue & Change Request | Issue & Change Request Activity |
| Risk | Risk Activity |
Additionally there are validation checks for Status and End date as well.
Residence Period
The residence period is the minimum span of time that data must spend in the database before it meets the archivability criteria. You may configure the residence period for relevant business objects in CPM in the following path in SPRO. In the given example the residence period is '0' which indicates that the data can be archived immediately provided it fulfills the criteria. This period can be configured based on the business requirement.
Cross-Application Components → Processes and Tools for Enterprise Applications → Reusable Objects and Functions for BOPF Environment → Archiving Adapter → Maintain BO-Specific Residence Periods
Persistence of Project Hierarchy
For an ongoing operative commercial project, The Project Hierarchy is not stored in CPM rather it is fetched at runtime from Project Systems or Portfolio and Project Management. During archiving, it is crucial to store the hierarchy otherwise hierarchy may change and some information might get lost. To prevent that CPM implements an additional logic.
During execution of preprocessing program of Financial Plan archiving, the hierarchy is fetched at the runtime and is pushed to a temporary table '/CPD/D_ARCH_HIER'. When the delete program is executed, the same hierarchy is pushed to archive file and is deleted from the temporary table.
For Commercial Project, since there is a validation that the PS project should be archived first. During the execution of PS Project archive deletion program, a CPM API '/CPD/ARCH_HIERARCHY_SET' is called which sets hierarchy in the temporary table. The data in the table later gets pushed to the archived files during commercial project archive.
The feature mentioned is part of S/4 HANA 2023 FPS02, 2023 FPS02, 2022 FPS04, 2021 FPS07, and 2020 FPS09.
Conclusion
With the new development for persisting project hierarchy, the complete information will be available in the archive file which can be referred at any point of time. The new development also enables multiple validation and streamlines the entire archiving process in CPM.
1 Comment
