Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-FS-ARE (Application Component) Archiving Engine⤷
ARFA_ARCHIVING_FACTORY (Package) Archiving Factory
Basic Data
| Data Element | TYP_CONDITIONAL_DELETING |
| Short Description | Conditional Deletion |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Condit. |
| Medium | 17 | Conditional Deletion |
| Long | 20 | Conditional Deletion |
| Heading | 17 | Conditional Deletion |
Documentation
Definition
Conditional deletion: Yes/No
Use
You can use this function when deleting data from the database to decide whether certain data for an object needs to remain in the system, or whether it can be deleted. An example is multiple use of data for different business objects that can be assigned to an object uniquely, but is also required by other objects.
If the "Conditional Deletion" view has been activated, a check module for conditional deletion can be stored on the "Table" detail screen ("Archive and Delete" node for an archiving object).
Dependencies
Example
Object A references data from object B. Object B needs to be archived first. In the conditional deletion function, you need to ensure that the data that is required by both object A and object B is archived (= copied) for both objects, and that the data is only deleted from the database if it is no longer required by object A or object B.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 40 |
