Migration Cockpit Enhancement for Missing Migration Objects using BAPI
Problem Statement: Migration Cockpit is a very user-friendly approach to upload master data, or balances. However, it does not cover all the migration objects so far. For example, migration objects to transfer TRM transactions from legacy system to new system are missing.
And, it takes good amount of time and efforts to develop and test custom migration programs. Moreover, from client perspective, available WRICEF objects get unnecessarily consumed in developing such cut-over programs.
However, with minimal efforts, we can easily enhance Migration Cockpit functionality. This blog details the steps involved with screenshots for easy understanding.
Pre-requisite: Basic understanding of working with Migration Cockpit is expected like creation of Migration Project, download and upload of template, execution of ‘Validation’ to ‘Migrate’ steps.
Step 1: Select BAPI
Identify a BAPI required for the involved transaction. E.g. to create Interest Rate Swap transaction in TRM, we can use this BAPI – “BAPI_FTR_SWAP_CREATE“. So, we will map this BAPI in LTMOM transaction – this is the transaction wherein we can modify migration objects of the Migration Cockpit.
Step 2: Create Migration Project
Execute t-code LTMC. If Migration Project already exists, we can use that also.
Step 3: Create Migration Object
Execute t-code LTMOM.
Select the Migration Project as shown below: –
Create a Migration Object within our Migration Project as shown below: –
Please note that we have mapped the relevant BAPI in the above screenshot.
We can confirm the entered details in the ‘Target Structures’ link, as shown below: –
Step 4: Target Structures – Standard Fields
Double click on tabs available under ‘Target Structures’, as shown below, to display the list of standard fields available for upload.
Using this, we can make a list of relevant fields to be uploaded as per client requirements as all the fields are not required to be uploaded. Say, we have selected the following fields from R_OTCINTERESTSWAP and R_GENERALCONTRACTDAT tabs. (Just copy-paste the required fields in an excel file.)
Step 5: Create Source Structures
Open the Migration Object in edit mode, as shown below: –
Create ‘Source Structure’, as shown below, as per required tabs in the template file. In our case, we will have two tabs in our template – PROD_DET and TRANS_DET.
For each tab, create fields as shown below. Copy-paste from the excel file prepared above.
Note that we are using EXT_UID (it can have any name, data type and description) to establish relationship between different tabs of the template.
Note: Using ‘Foreign Key Relationship’ button, circled above, establish the relationship with parent tab.
Step 6: Structure Mapping
As shown above, drag and drop the tabs under ‘Source Structures’ (in the middle) to tabs under ‘Target Structures’ (on the right side)
- First drag-drop each tab under ‘Source Structures’ onto its corresponding tab under ‘Target Structures’.
- PROD_DET –> R_GENERALCONTRACTDAT
- TRANS_DET –> R_OTCINTERESTSWAP
- Drag-drop header tab (i.e. PROD_DET here) onto each tab under ‘Target Structures’.
- PROD_DET –> HEADER
- PROD_DET –> R_OTCINTERESTSWAP
- PROD_DET –> R_TESTRUN
- PROD_DET –> R_RETURN
Step 7: Field Mapping
As shown above, map each field of our template to the standard field (just drag and drop), so that data is uploaded in the correct fields. System will throw errors if the data types of source and target fields do not match.
Step 8: Generate the Migration Object
Step 9: Upload Legacy Data
Click on the highlighted Migration Object to download the template and upload data from legacy system
After filling legacy data in this template, we can upload it using standard LTMC process.
This blog post will help us to avoid custom developments for missing Migration Objects in the Migration Cockpit saving us time, money and efforts. In the next blog, I will cover enhancement for custom fields.
- TRM – Treasury and Risk Management
- LTMC – Legacy Transfer Migration Cockpit
- LTMOM – Legacy Transfer Migration Object Modeller
Thanks Ravi for sharing this article, saved a lot Custom effort in my current project for uploading the Master data objects.