Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-TRM-TM-AC (Application Component) Transfer to Financial Accounting⤷
FTR_ACCOUNTING_ADAPTOR (Package) CFM TM: Accounting Adaptor
IMG Activity
| ID | BEWERT_SE | Enter Valuation Area Independent Data for Securities |
| Transaction Code | S_PLN_62000779 | (empty) |
| Created on | 20040621 | |
| Customizing Attributes | BEWERT_SE | Enter Valuation-Area-Independent Data for Securities |
| Customizing Activity | BEWERT_SE | Enter Valuation-Area-Independent Data for Securities |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BEWERTUNGSBEREICHSUN |
Use
The data is defined for each key date and position (without the valuation area.) You can specify the purchase value and capitalized costs in addition to the quantity information (units and nominal amounts.)
Five fields are also provided for transferring other components.
The effects on the position are controlled by the update type. Update types are assigned in the IMG activity Assign Update Types for Legacy Data Transfer on the valuation area-independent tab page.
The impact on the position of all the update types used for this table needs to be specified in the IMG activity Set the Effects of the Update Types on Position Components.
Note:
You can use the Customizing settings delivered as a guide.
Lots
If lots are required, you need to make the relevant settings in the IMG activity Define and Assign Differentiations.
In the valuation area-independent table, enter a number in the position number field. This number must also be defined in the corresponding entry in the valuation area-dependent table. Prior to the valuation area-dependent business transaction being distributed, the system determines the LotID of the valuation area-independent business transaction (identified by its number) that has already been distributed. The LotID is then written into the valuation area-independent business transaction.
By entering the number in the position number field, different lots with the same differentiation terms can also be generated for a key date.
The position number can also be used for collective position management to define multiple data records for each key date and position.
Requirements
You need to create the master data required for the positions to be transferred:
- Business partners (issuer, counterparty)
- Classes
- Securities accounts
Activities
You define the position using the fields position value date, company code, general valuation class, ID number, securities account, portfolio, and position number. You then enter the relevant valuation area-independent data in the following fields:
- Position currency
- Local currency
- Assets/liabilities
- Calculation Date
- Units
- Original Nominal Amount in Position Currency
Nominal amount
- Nominal amount currency
- Purchase Value in Position Currency
- Purchase value in local currency
- Purchase value in position currency, index clean
- Costs in Position Currency
- Costs in local currency
- Costs in position currency, index clean
- Cumulative Repayment in Position Currency
- Cumulative repayment in local currency
- Cumulative repayment in position currency, index clean
- Component 1 in position currency
- Component 2 in local currency
- Component 2 in position currency
- Component 2 in local currency
- Component 3 in position currency
- Component 3 in local currency
- Component 4 in position currency
- Component 4 in local currency
- Component 5 in position currency
- Component 5 in local currency
- The last column shows whether the data was already transferred.
- Empty field -> the data has not been transferred yet.
- X -> the data has been transferred.
After you have entered your data, save your entries.
Use the IMG activity Execute Data Transfer to transfer your data.
Business Attributes
| ASAP Roadmap ID | 103 | Set up development systems |
| 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 |
| SNUM | T - Individual transaction object | TPM63A |
History
| Last changed by/on | SAP | 20040621 |
| SAP Release Created in | 500 |
