Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FIN-FSCM-TRM-TM (Application Component) Transaction Manager⤷
FTR_GENERAL (Package) CFM TM: Application Basis / Global Objects
IMG Activity
| ID | TPM_MIGRATION | Conversion Programs |
| Transaction Code | S_PL7_36000006 | (empty) |
| Created on | 20001123 | |
| Customizing Attributes | TPM_MIGRATION | Conversion Programs for Release CFM 1.0 |
| Customizing Activity | TPM_MIGRATION | Conversion Programs for Release CFM 1.0 |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | TPM_MIGRATION |
In this IMG activity you access the conversion programs.
For Release R/3 Enterprise 2.00 the operative valuation area for the securities and OTC transactions product groups has been integrated into parallel position management.
Several conversion steps must be carried out to complete conversion. Transaction TPM_MIGRATION will help you to complete these conversion steps.
Conversion Customizing
The following settings must be made in Customizing for the conversion:
- Previous release (entry mandatory)
- Customizing request (all Customizing entries generated by the conversion are transferred to this request. An entry is not mandatory but recommended).
- Customizing client (this entry is required if the Customizing steps are carried out in the Customizing client, see below for more information).
- Production system (this entry is required if the Customizing steps are carried out in the Customizing client, see below for more information).
- Reason for reversal (this entry is not mandatory)
- Prefix for the batch job (you can generate jobs for the conversion step from the menu: Extras -> Generate job.) Jobs and variants are generated for report RTPM_TRG_MIGR_BATCH. You can run the conversion steps in a batch run using these jobs.
Conversion Customizing can be called with transaction TPM_MIGRATION_CAT.
Process flow
The conversion steps are divided up as follows:
- Customizing conversion steps (prefix A or E)
- Master/flow data conversion steps (prefix B or F)
Both Customizing and the master/flow data conversion steps are further split into:
- Company code independent conversion steps
- Company code dependent conversion steps
Customizing Conversion Steps
As a rule, all Customizing conversion steps should be carried out in Customizing clients. However, it is also possible to carry out steps directly in the production system/client. In this case, Customizing tables are filled directly by the conversion steps.
If a Customizing request is defined in Customizing conversion, all entries generated in Customizing tables by these steps are transferred to this request. This is in order to simplify the transport of the relevant Customizing settings.
Some Customizing conversion steps must access master and flow data in the production system via RFC. This is why you give the name of the production system in order to carry out the Customizing steps in the Customizing client.
The Customizing steps must be carried out in the correct sequence.
Master and Flow Data Conversion Steps
All Customizing conversion steps must be carried out first.
Notes:
- We differentiate between conversion steps for the product group securities (with the prefix WP) and the product group OTC transactions (prefix OTC). Of course, these steps need only be carried out if you are using these product groups. If there is no prefix this means that the conversion step is for all product groups and must be carried out.
- Conversion steps should be carried out in sequence. Caution: If a company code independent step follows a company code dependent step, you must first carry out the company code dependent step for all company codes.
- If a situation occurs in the middle of a conversion step which triggers an error message, the conversion step is terminated. If the step stumbles on a situation which triggers a warning message, the program is halted and the warning message is output in a dialog box. You can then decide to cancel the step or carry it out despite the warning message.
- Some conversion steps are split into several packages in order to improve performance. To avoid having to deal with this warning message each time you process a package you can set the Convert despite warnings switch. The warning messages are then output only after all packages have been completed. However, only a reversal can reset the conversion step in this case.
- You should carry out all the steps for which there is a test run in test run mode before running the report. This lets you solve any problems that may occur before you carry out the step.
- You can get help for each of the conversion steps by selecting one of the steps and clicking on Help.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | TPM_MIGRATION | 0 | KFM0000007 | Transaction Manager |
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 |
| IMGDUMMY | D - Dummy object | TPM_MIGRATION |
History
| Last changed by/on | SAP | 20010531 |
| SAP Release Created in | 462_10 |
