Hierarchy
⤷ BC-BMT-OM (Application Component) Organizational Management
⤷ SP0A (Package) HR-OM: General Attribute Maintenance in Org. Management
Basic Data
Data Element | OM_ATTRPST |
Short Description | Search by Sub-String |
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 | Sub-String |
Medium | 15 | Sub-String |
Long | 20 | Sub-String |
Heading | 1 | S |
Documentation
Definition
Supplementary Documentation - OM_ATTRPST0001
Definition
As standard, in assessment/distribution the system only takes into account the amounts in the controlling area currency. By selecting field groups you can specify that they should be processed too.
Depending on the field group, this can have various consequences.
- Object currency
The system determines the sender values separately, and distributes them separately in their own fields. This can only work if the object currency is the same for all participating objects (cost centers, requests...), since there is no conversion between object currencies during processing. For example, it is not possible for a sender to distribute to a receiver with a different object currency. If such an error occurs during processing, the system outputs a warning, and the object currency is treated as if you had not set the indicator.
If the indicator is not set, when the transfer from sender to receiver is posted, the system determines the object currency to be posted by taking the controlling area currency and converting it to the object currency of the sender or of the receiver. - Transaction currency
The system determines the posted sender values in the transaction currency separately, processes them internally, and posts them with the transaction currency in the receiver system.
If the indicator is not set, all sender values with different transaction currencies are grouped together, as the system only uses the controlling area currency.The credit and debit following distribution are posted with transaction currency = controlling area currency.
If you credit the receiver with the amounts originally posted in the sender system using a separate return, you should select this field group. However, you should be aware that this may lead to considerably more totals records and line items.
Example: the controlling area currency is USD. Sender A distributes 50% each to recievers B and C. In sender A are posted values with the transaction currencies DEM and CHF. DEM = 1000.- and CHF = 2000.-. If the Transaction Currency field group is selected, B and C now each recieve postings with transaction currency DEM 500.- and CHF 1000.-. The posted transaction currencies are debited from sender A For the distribution, a total of 6 line items are posted. However, if the field group is not selected, the two sender values are put together, giving, for example, a total of USD 2200.-. This leads to a credit of USD 1100.- in each of B and C. This amount is credited in the transaction currency USD. A total of 3 line items are posted. - Consumption
If this field group is selected, the posted consumption amounts are also distributed. The prerequisite for this is that all amounts have been entered in all senders. If this is not the case for a sender, the system outputs a warning, and the amount is not distributed.
Note
The field groups Object Currency and Transaction Currency are only updated if the 'All Currencies' indicator is set for the controlling area. If it is not set, the system does not even offer the two field groups at this point, as internal processing in distribution would not be meaningful.
Supplementary Documentation - OM_ATTRPST0002
Definition
As standard, in assessment/distribution the system only takes into account the amounts in the controlling area currency. By selecting field groups you can specify that they should be processed too.
Depending on the field group, this can have various consequences.
- Object currency
The system determines the sender values separately, and distributes them separately in their own fields. This can only work if the object currency is the same for all participating objects (cost centers, requests...), since there is no conversion between object currencies during processing. For example, it is not possible for a sender to distribute to a receiver with a different object currency. If such an error occurs during processing, the system outputs a warning, and the object currency is treated as if you had not set the indicator.
If the indicator is not set, when the transfer from sender to receiver is posted, the system determines the object currency to be posted by taking the controlling area currency and converting it to the object currency of the sender or of the receiver. - Transaction currency
The system determines the posted sender values in the transaction currency separately, processes them internally, and posts them with the transaction currency in the receiver system.
If the indicator is not set, all sender values with different transaction currencies are grouped together, as the system only uses the controlling area currency.The credit and debit following distribution are posted with transaction currency = controlling area currency.
If you credit the receiver with the amounts originally posted in the sender system using a separate return, you should select this field group. However, you should be aware that this may lead to considerably more totals records and line items.
Example: the controlling area currency is USD. Sender A distributes 50% each to recievers B and C. In sender A are posted values with the transaction currencies DEM and CHF. DEM = 1000.- and CHF = 2000.-. If the Transaction Currency field group is selected, B and C now each recieve postings with transaction currency DEM 500.- and CHF 1000.-. The posted transaction currencies are debited from sender A For the distribution, a total of 6 line items are posted. However, if the field group is not selected, the two sender values are put together, giving, for example, a total of USD 2200.-. This leads to a credit of USD 1100.- in each of B and C. This amount is credited in the transaction currency USD. A total of 3 line items are posted.
Note
The field groups Object Currency and Transaction Currency are only updated if the 'All Currencies' indicator is set for the controlling area. If it is not set, the system does not even offer the two field groups at this point, as internal processing in distribution would not be meaningful.
Supplementary Documentation - OM_ATTRPST0004
Use
Indicates whether the terminology concept has at least one glossary definition in any language.
Example
Values:
- 'X' The indicator is set. The terminology concept has at least one glossary definition in one language.
- ' ' The indicator is not set. The terminology concept has no glossary definition.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 620 |