Hierarchy
EA-FIN (Software Component) EA-FIN⤷
FI-GL-GL-ACE (Application Component) Accrual Engine⤷
ACE (Package) Accrual Engine: Other
IMG Activity
| ID | FIGL_ACE_ARCHPREP | Correct Archiving Status |
| Transaction Code | S_PLN_16000086 | (empty) |
| Created on | 20020320 | |
| Customizing Attributes | ACC_GL_ACE_K_U_A_204 | Accrual Engine: Optional Activity, Uncritical, 204 |
| Customizing Activity | FIGL_ACE_ARCHPREP | Correct Archiving Status after Test Run |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ACE_ARCHIVING_PREP |
Use
This Business Add-In (BAdI) is called during the preparation run for archiving Accrual Engine data.
During the preparation run for archiving, Accrual Engine data is selected.
On the basis of predefined rules, the system decides how the data for an accrual object is to be archived. The system sets the
CD_ARCHIVE_OBJ indicator. This flag can have the following values:
- X
This accrual object is to be archived. This means that you want the system to change the status of this accrual object to To be archived. - <initial>
This accrual object is not to be archived. This status of this accrual object should not be changed to To be archived.
The rules (conditions) which your system uses to decide whether the accrual object is to be archived or not are defined in function module ACE_ARCHPREP_DECIDE. This function module is called up in the default implementation of this BADI.
By creating your own BAdI implementation for this BAdI, you can replace the standard logic with your own logic.
Description of the parameters in the method:
- IS_ACEOBJ
Accrual object. Entry from database table ACEOBJ - IT_ACEDSOH
Table with header data for subobjects of the accrual object. This table contains, for example, the validity periods of the accrual subobjects.
These are entries from database table ACEDSOH. - IT_ACEPSOI
Table with item data for the accrual subobjects. This table contains, for example, the data of the most recent periodic accrual posting. It also contains the accrual amounts posted grouped by year.
These are entries from database table ACEPSOI. - ID_KEYDATE
Key data on which the archiving preparation run is executed.
Using the parameters described, in the BAdI you can decide whether an accrual object is to be archived or not.
Allgemeine Informationen zur Definition von BAdIs finden Sie in der SAP-Bibliothek unter Basis -> ABAP Workbench (BC-DWB) -> Änderungen des SAP-Standards (BC) -> Business Add-Ins -> Definition eines Business Add-Ins.
Example
The preparation run is executed for the key date December 31, 2005. A number of accrual subobjects have a runtime from January 1, 2000 to November 30, 2010
The system therefore sets the CD_ARCHIVE_OBJ indicator to <initial>, meaning that the system would not archive this accrual object, as some accrual subobjects are still valid and it is therefore expected that accrual postings might still be made to these in future.
You know, however, that no more accrual postings will be made to these accrual objects, and they can therefore be archived.
You therefore create your own BAdI implementation where the indicator CD_ARCHIVE_OBJ is set to X for these accrual objects.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20040218 |
| SAP Release Created in | 110 |
