Hierarchy
⤷ CA-GTF-TS-GMA (Application Component) Generating, Monitoring for Mass Data Archiving Solutions
⤷ BCA_ARCHIVING_CORE (Package) Archiving Objects: Interface Problems
Basic Data
Data Element | BCA_AR_FLUD |
Short Description | Resubmission Date |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DATS | |
Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Resub. |
Medium | 18 | Resubmission Date |
Long | 20 | Resubmission Date |
Heading | 18 | Resubmission Date |
Documentation
Definition
When this date elapses, the system checks the data records again to see if they can be archived.
Use
This archiving object attribute is provided for new creations, deletions, when a final status is set and by the analysis program. The resubmission date is used to prevent the analysis program from continually checking data records that cannot be archived.
For a new creation, a deletion and when an end status is set, the system sets the resubmission date to the earliest date on which the archiving object can be archived. For this it uses the residence time of the archiving object.
If the analysis program detects that the data record can currently not be archived, the resubmission date is updated. The value entered is the current system date plus the period of time stored in the archiving object-specific Customizing settings or the global Customizing settings for the archiving objects. The data record is not processed again in the analysis program until the resubmission date has been reached.
Dependencies
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 20 |