Hierarchy
⤷ FI-GL-GL-ACE (Application Component) Accrual Engine
⤷ ACE (Package) Accrual Engine: Other
Basic Data
Data Element | ACE_FLAG_ORG_PERIOD |
Short Description | Flag: Reversal Posting in Original Period |
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 | FLAG | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Org.Period |
Medium | 20 | Period-Spec. Revrsal |
Long | 40 | Period-Specific Reversal |
Heading | 55 | Orig. Period |
Documentation
Definition
Note:
In the Accrual Engine, accruals postings are always reversed at the key date for which they were originally posted.
The 'Periodic Reversal' flag is relevant for the (automatic) transfer of reversal postings to Accounting.
If the flag is selected, documents are posted in Accounting in the period from the accrual posting key date.
If the 'Find Next Open Period' flag is set in activity 'Define Customer Settings for Components' in Accrual Engine Customizing, the posting can also be made to a different period if the relevant period is locked..
Supplementary Documentation - ACE_FLAG_ORG_PERIOD0001
Definition
In the standard, only amounts in controlling area currency are taken account of in assessment/distribution. You can select individual field groups to decide whether or not you want them to participate. Depending on the field group, this has various consequences.
- Object Currency
The sender values in object currency are found separately in distributed to special fields of their own. This means, for example, that is it is not possible to distribute a sender to a receiver with a different object currency. If an error of this kind occurs during processing, the system posts a warning, and the object currency is treated as though you had not selected the flag.
If the flag is not set, the object currency to be posted is determined by conversion to the object currency of the sender/receiver when the sender credit and the receiver debit are updated from the controlling area currency. - Transaction Currency
The sender values posted in transaction currency are determined separately, processed internally and updated in the posted transaction currency with the receiver.
If the flag is not set, all sender values are summarized in different transaction currencies, as only the controlling area currency is stored and carried forward. The debits/credits from the distribution are posted in transaction currency = controlling area currency.
If you need to have a separate record of the amounts originally posted at the sender for the receiver, you should select this field group. You should be aware, however, that this could lead to the creation of many more totals records and line items.
Example: The controlling area currency is USD. Sender A distributes to 50 % each to receivers B and C. Values are posted to sender A with transaction currencies DEM and CHF, DEM = 1000 and CHF = 2000. If the transaction currency field group is selected, B and C are both debited with transaction currency DEM 500 and CHF 1000. At the same time, sender A is credited with the posted transaction currencies. A total of 6 line items are posted for distribution. If, on the other hand, the field group is not selected, the two sender values are summarized, resulting in this example in a value of USD 2200. This leads to B and C being debited 1100 USD each. This amount is debited under transaction currency USD. At the same time, the sender is credited USD 2200. A total of three line items are posted. - Consumption
If this field group is selected, the posted consumption amounts are also distributed. A prerequisite for this is that all amounts have been entered fully for all senders. If this prerequisite is not met for the sender, the system will post a message warning you that the amount will not be distributed.
Note
The field groups object currency and transaction currency will only be updated separately if the 'All Currencies' flag is set for the controlling area. If this flag is not set, the two field groups will not be offered at all here, as internal processing in distribution would not make sense.
Supplementary Documentation - ACE_FLAG_ORG_PERIOD0002
Definition
In the standard, only amounts in controlling area currency are taken account of in assessment/distribution. You can select individual field groups to decide whether or not you want them to participate. Depending on the field group, this has various consequences.
- Object Currency
The sender values in object currency are found separately in distributed to special fields of their own. This can only work if the object currency of all participating objects (cost centers, orders and so on) is the same, as no conversion is made between object currencies during processing. This means, for example, that is it is not possible to allocate a sender to a receiver with a different object currency. If an error of this kind occurs during processing, the system posts a warning, and the object currency is treated as though you had not selected the flag.
If the flag is not set, the object currency to be posted is determined by conversion to the object currency of the sender/receiver when the sender credit and the receiver debit are updated from the controlling area currency. - Transaction Currency
The sender values posted in transaction currency are determined separately, processed internally and updated in the posted transaction currency with the receiver.
If the flag is not set, all sender values are summarized in different transaction currencies, as only the controlling area currency is stored and carried forward. The debits/credits from the assessment are posted in transaction currency = controlling area currency.
If you need to have a separate record of the amounts originally posted at the sender for the receiver, you should select this field group. You should be aware, however, that this could lead to the creation of many more totals records and line items.
Example: The controlling area currency is USD. Sender A distributes to 50 % each to receivers B and C. Values are posted to sender A with transaction currencies DEM and CHF, DEM = 1000 and CHF = 2000. If the transaction currency field group is selected, B and C are both debited with transaction currency DEM 500 and CHF 1000. At the same time, sender A is credited with the posted transaction currencies. A total of 6 line items are posted for the assessment. If, on the other hand, the field group is not selected, the two sender values are summarized, resulting in this example in a value of USD 2200. This leads to B and C being debited 1100 USD each. This amount is debited under transaction currency USD. At the same time, the sender is credited USD 2200. A total of three line items are posted.
Note
The field groups object currency and transaction currency will only be updated separately if the 'All Currencies' flag is set for the controlling area. If this flag is not set, the two field groups will not be offered at all here, as internal processing in distribution would not make sense.
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in | 110 |