Hierarchy
SAP_AP (Software Component) SAP Application Platform⤷
AP-PRC-CON (Application Component) Condition Technique⤷
/SAPCND/ARCHIVING_C (Package) Archiving for Condition Technique for mySAP
IMG Activity
| ID | /SAPCND/ARCH_CHECK | Enhanced Checks for Archiving of Condition Records |
| Transaction Code | /SAPCND/89000018 | BAdI for /SAPCND/ARC_CHECK |
| Created on | 20040608 | |
| Customizing Attributes | /SAPCND/ARCH_CHECK | Enhanced Checks for Archiving of Condition Records |
| Customizing Activity | /SAPCND/ARCH_CHECK | Enhanced Checks for Archiving of Condition Records |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPCND/ARCH_CHECK |
Use
This Business Add-In (BAdI) is used for archiving condition records and is to be used for the enhanced checks to determine whether or not a condition record should be archived. Implementations for this BAdI are prerequisites for setting up archiving for certain appications and usages.
Requirements
You can find general information on the archiving procedure in the information area of transaction SARA for the archiving object CND_RECORD, or directly in the Documentation of the write program for archiving condition records.
Explanation
The two methods GET_ARCHIVE_PERMISSION and GET_ARCH_PERM_BY_VARNUMH are both provided. These methods differ in terms of interface and the way they are called.
Method GET_ARCHIVE_PERMISSION does not allow single record checking and the method callup is buffered (i.e. only when one of the import parameters is changed).
Method GET_ARCH_PERM_BY_VARNUMH allows single record checking and the interface also contains import parameters VARNUMH and OBJECT_ID. It is therefore not possible to buffer the calls. When implementing, you should also consider performance. This BAdI method is only called if the OBJECT_ID is not initial (otherwise, the first method is called).
Standard settings
Every implemented method must comply with the "veto concept". Because you are only allowed to set parameter C_IS_ARCHIVING_ALLOWED to 'false' (therefore: Space), every method should start with
check c_is_archiving_allowed = ctcus_true.
The filter value FLT_VAL is made up of the application and the usage. During implementation, the individual components (KAPPL and KVEWE) can be coded.
This BAdI is not SAP internal and is not multiple usage-enabled. SAP provides the following implementations:
Where required, you can create your own BAdI implementations.
Note
You can find general information on archiving in transaction SARA for the archiving object CND_RECORD.
Activities
Example
Business Attributes
| ASAP Roadmap ID | 208 | Establish Archiving Management |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | /SAPCND/ARCH_CHECK | 0 | PFC0000016 | Condition Technique |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20041102 |
| SAP Release Created in | 4X1 |
