Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-TRM-TM-TR (Application Component) Transaction Management⤷
FTTR (Package) Treasury: Financial Transaction
IMG Activity
| ID | SIMG ABWEICHFORT | Alternative Update Types for Position Outflows |
| Transaction Code | S_KFM_86000293 | (empty) |
| Created on | 20010508 | |
| Customizing Attributes | SIMG_ABWEICHFORT | Alternative Update Types for Position Outflows |
| Customizing Activity | ABWEICHFORT | Alternative Update Types for Position Outflows |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ABWEICHENDE FORTSCHR |
Use
In this IMG activity you can replace the update types for derived business transactions with alternative update types, based on certain conditions. The new update type is automatically assigned the position change category of the old update type.
You make these settings for a given position management procedure.
Alternative update types can be used to avoid P/L inflation. The P/L account is inflated when the system generates income-related derived business transactions that offset each other (such as a realized price loss and a positive OCI translation). By using alternative update types, you can group these flows and post them to the same P/L account.
Conditions
The following conditions are currently supported:
- Total amount realized for security >= 0
- Total amount realized for security < 0
- Total amount realized for foreign currency >= 0
- Total amount realized for foreign currency < 0
Total amount realized for security = Security price gain - Security price loss + Translation of security write-up (not posted to P/L) - Translation of security write-down (not posted to P/L) + [Translation of discount - Translation of premium]
Total amount realized for foreign currency = Exchange rate gain - Exchange rate loss + Translation of FX write-up (not posted to P/L) - Translation of FX write-down (not posted to P/L)
[...] only relevant for gross procedure
Example
During key date valuation, write-ups and write-downs are generated for a position, but not posted to P/L. These write-ups and write-downs are cleared by "translations" when positions are sold.
Position 01/01/XX:
Nominal value: 200,000 EUR
Amortized acquisition value: 200,000 EUR
Security write-up (not affecting P/L): 20,000 EUR
Book value: 220,000 EUR
Position outflow 01/02/XX: 100,000 EUR nominal at a price of 105%
The following derived business transactions would be generated:
- DBT_B003 (security price loss): 5,000 EUR [Posting: Realized price losses to balance sheet position]
- DBT_E025 (Translation of security write-up (not posted to P/L): 10,000 EUR [Posting: OCI to Realized price gains]
In this case, the position outflow results in inflated P/L figures if the price losses and price gains are not posted to the same account. You can avoid this by defining the following alternative update type:
- Position management procedure: 4711
- Old update type: DBT_B003 (security price loss)
- Condition: Total amount realized for security >= 0
- New update type: DBT_BA03 (security price loss -> security price gain)
The position outflow would then generate the following flows, as opposed to those above:
- DBT_BA03 (security price loss - alternative): 5,000 EUR [Posting: Realized price gains to balance sheet position]
- DBT_E025 (Translation of security price valuation not posted to P/L): 10,000 EUR [Posting: OCI to realized price gains]
If the total realization amount (DBT_B001) is positive and exceeds the translation for the security write-down not posted to P/L (DBT_E026), these flows could be grouped by the following entry:
- Position management procedure: 4711
- Old update type: DBT_E026 (translation of security write-down not posted to P/L)
- Condition: Total amount realized for security >= 0
- New update type: DBT_EA26 (Translation of security write-down not posted to P/L -> Gain)
You also have to make corresponding settings for the other conditions.
Requirements
- First define all the necessary update types in the IMG activity Define Update Types.
- Assign the update types to the usage "Derived Business Transactions" in the IMG activity Assign Update Types to Usages.
- Enter the relevant account determination settings for the alternative update types in the IMG activity Define Account Determination.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| TRL_C_FT_REPLACE | S - Table (with text table) | SM30 |
History
| Last changed by/on | SAP | 20030515 |
| SAP Release Created in | 463_20 |
