Hierarchy
⤷ FI-GL-GL-ACE (Application Component) Accrual Engine
⤷ ACE (Package) Accrual Engine: Other
Basic Data
Data Element | ACE_LEGACY_TO_ACC_TRANSFER |
Short Description | Allow Transfer of Legacy Data to Accounting |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FLAG | |
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 | Trans to A |
Medium | 20 | Allow Trans. to Acc. |
Long | 40 | Allow Transfer to Accounting |
Heading | 1 | A |
Documentation
Definition
If this flag is set, the legacy data that has been transferred to the Accrual Engine (Accrual Engine documents) is also transferred to Accounting.
This transfer to Accounting must be performed separately with report ACEPS_POSTINGS_2_ACC_TRANSFER.
This is problematic, as the legacy data transferred cannot be distinguished from other data in the Accrual Engine, meaning that the legacy data could be accidentally transferred to Accounting at a later stage.
IF this flag is not set, the legacy data that has been transferred to the Accrual Engine is not transferred to Accounting.
If this is the case, it is assumed that the Accounting data is transferred separately from the legacy systems to Accounting.
Technical Background:
Transferring Accrual Engine data to Accounting with report ACEPS_POSTINGS_2_ACC_TRANSFER is only possible with Accrual Engine documents in which the AWKEY field is empty.
If this flag is not set, the AWKEY field in the transferred legacy data will be filled with a dummy value.
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in | 461 |