SAP ECC Vendor Master data copy by SAP TDMS 4.0
We can use TDMS Business process Library to copy vendor master data from production to non-production systems based on business requirements,
Business Process Library in SAP TDMS is a collection of specific SAP business processes. That we can use the BPL-based transfer migration solution to copy data relevant to the business processes from the sender system to the receiver system.
For most of the projects UAT and SIT business required live vendor master data for production to the non-production environment, Through TDMS we can copy consistent data into the non-production system.
Please check the below blog for basic functionality and control system setup.
The content of this blog post is provided “AS IS”. This information could contain technical inaccuracies, typographical errors, and out-of-date information. This document may be updated or changed without notice at any time. Use of the information is therefore at your own risk. In no event shall SAP be liable for special, indirect, incidental, or consequential damages resulting from or related to the use of this document.
Now we can copy vendor master data from source to target as per business requirements for SIT & UATs.
SAP TDMS BPL Basic Features
- SAP TDMS transfers the required data of the BPL objects based on the selection criteria.
- Following Objects are a part of the BPL package in our case package will be BC – Vendor
- Root Table
- Transferring BPL objects is necessary to ensure a high level of data consistency in the receiver system.
We can modify default BPL objects based on business requirements, Through the Business Process library modeler, we can create a copy of BPL Objets and can be performed the below task and create customized BPL solution based on the requirement.
- Add tables
- Add subobjects
- Modify foreign key or link mappings
- Delete tables
- Deactivate or activate subobject links
- Set a table as a root table or remove the selection
SAP TDMS Vendor Master Copy Technical Steps:-
· Project Template creation
· Project creation
· System landscape creation
· Package creation
o Technical Settings
o Configuration and Selection
o Data Transfer
Project Template creation
Created project template based on the requirement, in our scenario we have to copy vendor master.
Goto TDMS Tcode will redirect you to the web URL.
Go to the project template and create a new project template.
Add a required portfolio to the template, In our case, we need to copy vendor master and it comes under BPL. Select BPL and choose BC – Vendor master
Add requirement to project template
Green status means all ok and proceed with the next setup project creation
Once you assign a portfolio solution to a project template you can’t add more solutions on the same project template, but you can use the same template for many projects multiple times.
Create a project for vendor master data copy and assign a project template to it.
Goto projects and click on new, Provide relevant project name and description.
Goto next and assign project template to project
Click on finish and it will add BC- vendor into an execution phase
Project creation completed, Same projects can be used multiple times for the same solution.
System landscape creation
We will define the data transfer system landscape in this step and during the process, itself all communication automatically will be created between the control system, source, and target system.
Go to SYSTEM LANDSCAPES and create a new system landscape.
Once you click on create, It will open below the wizard.
Provide central system, control system, receiver and sender system SID, and client numbers.
Your central and control system can be the same.
In the next step provide instance number, language, server name, RFC user id, and password.
Click on Distribute RFC destinations, It will automatically create all RFCs.
Once again go to projects and double click on your project and open.
Click on edit and assign your system landscape to the project.
Create a package by clicking on create package.
Some of the settings are optional and we can ignore them, We can select the row and start execution for mandatory steps.
View vendor master related table
|Table Name||Description||Tab. Cat.||Table Role||Pool/Cluster||No. of Records||Table Size (in KB)||Software Component||Software Comp. Desc.|
Assign all logical system names based on the receiver system.
Need to update “Name in the Receiver System” based on sender system details.
Configuration and Selection
Execute all below mandatory steps
This is one of the most important steps where we have to provide either individual vendor master numbers or a range of vendor masters based on the LFA1 table.
Provide vendor master range based on LFA1 table LIFNR column.
Or provide individual vendor master numbers based on the requirement.
It’s very important to provided vendor master range or individual value in this step, If you leave this step blank then nothing will be copied from source to target.
Run the below step to create filters on source and target for data transfer and deletion.
the scrambling rule is very important if you are coping with business-critical data from production to non-production.
Before executing the activity, you have created the required scrambling rules in the TDMS Scrambling Workbench.
Execute below setup to perform final checks
Lock users on the receiver system are optional, Based on Receiver usages.
This is an optional setup, Execute the below step if you want to clear all data from the receiver system or if you want to merge data with the current receiver system-level below step.
In this step, you start the data selection for all migration objects with reading type Cluster Technique. The data of these migration objects are stored in partitioned and compressed form in a storage table in the sender system (cluster).
If you assigned another cluster technique-related reading type to any objects in the optional step for manual selection of reading types, this step covers those objects as well. (This from tool description)
Start the data transfer from source to target
We can check logs by clicking on the number of executions.
Unlock users in the receiver system if you locked in the above step.
Check number range.
Login into receiver system, Goto Se16 give LFA1 table name.
The next screen provides the same range which we have provided in the “specify migration parameters for data Selection” step.
Then check the number of entries it should be the same as a source after providing the same inputs.
TDMS tools inside details
I hope this document will help you with the vendor master copy.