Hi
Uploading data fom lagecy system we use tools like LSMW,BDC
Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.
Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.
as example , in simple words for MDM(master data maintenance) it means that after cutover - all data will be used of MDM and not legacy systems . for central master data scnerio ; Data before cutover date will be maintained in all systems and after cutover date , it will be maintained in MDM only .
Data can be uploaded using BDC programs, LSMW for master data and CATT is also being used.
Call transaction Method
A data transfer technology similar to batch input that allows large amounts of data to be transferred to a SAP System using the online transaction.
No batch input folder is generated. Instead, the data is posted directly using the online transaction.
Other transfer methods:
Batch Input
Direct Input
EDI
BAPIs
REFER LINK BELOW
http://www.akaas.net/faq/sap/bdc-questions.htm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.