Data Migration techniques

Hi Experts,
I want to know about data migration techniques and how we can best use MDM while migrating old version of R/3 to new version of R/3....
I have implemented SAP MDM in cases where we have number of SAP R/3 instances across different region and we were taking data from different R/3 one by one and doing data stan'zation,consolidation, Harmonization and all... I am not talking about all this...
There was a good explanation from Markus Ganser about Duplicate data and identical data... I know all this..but my question is when I have only one SAP R/3 and I still want to implement MDM solution while migrating my old R/3 instance to new one, How can I proceed in this scenario? What is the data migration technique...
I know the common answer will be to use MDM as a middle ware..take Master data from old instance and after consolidation, send it back to new instance and at the same time send tran'data directly to new version... But is this worth doing this? Is there any other approach?
If there is any document on this or any one have idea about data migration techniques while implementing MDM solution than send me documents on [email protected].......
In short, I am looking for below 3 points while doing migration along with SAP MDM
Data Migration techniques
Prerequisites
Methodology in this kind of scenario
Step by step procedure
cheers,
R.n

hi..
here i am sending u the link for complete Data Migration Life Cycle
<a href="http://www.redwoodsystems.co.uk/dataMWhitePaper.html#links">http://www.redwoodsystems.co.uk/dataMWhitePaper.html#links</a>
hope it might be of any use to u
thank you & reward points if useful
Message was edited by:
Dasari Narendra

Similar Messages

Error handling in DATA MIGRATION

hi
i am a beginner in sap abap. i am learning data migration techniques . so i wanted to know that what are the possible error in bdc and lsmw apart from error of data in flat file.And how handle those errors. if anyone can share his/her experience based on real time projects then it will be very helpful.
thanks'
akash

Hi
That depends on how you load the data in the system
It can think there are two ways to upload the data:
- Asynchronous: the data are picked up (from file) and loaded in different sessions (for example: a program read data from file and then prepare a BDC session)
- Synchronous: the data are picked up and loaded in the same session (for example a program read data from file and load them by BAPI)
In the first solution you can't know if a record is ok or not ok you need to elaborate it by BDC session: so here yuo need to decide what to do,
The BDC session keeps the wrong transaction so you can elaborate it manually (anyway it's better to be sure the file is correct before creating a BDC session)
In the second case you can use many soltuon because you can know if a record is ok or not after running BAPI, so (for example) you can generate a new file with the wrong record only, in order to try to elaborate it again.
Max

Data Migration from Legacy System in IS-U

Hi All,
We are going to Implement a new IS-U project, I have a problem with LSMW(Legacy System Migration Workbench ), I have some Conversion Objects of IS-U and I need to know whether Data Migration is possible or not, please tell me how to find these Objects and how to know Data Migration is possible or not.
Objects are like.,
1. Accounts
2. Actuate Reports
3. Business Partner Relationships
4. Active Campaigns/Campaign Content/Dispositions
5. Connection Object
6. Contacts
7. Contracts
8. Opportunities
9. Payment Arrangement History
10. Payments
11. Premises
12. Rate Changes
13. Security Deposits
these are few and there are some more..,
Thanks in Advance,
Sai.

Hi Ram,
Use Transaction Code EMIGALL. It will ask for company code. By default Company Code is SAP. If you entered with the SAP you will get all the objects.Then goto menu IS-U Migration-->User Handbook. It will give you details Idea.
Also Check the following Procedure
You can find detailed documentation of EMIGALL in SAP itself. Use Transaction EQ81 to display it. It provides all the concepts and procedures to work with EMIGALL.
Here are some points about EMIGALL :
1. It Migrates data Business Object wise
2. It uses Direct Input Technique
3. It has more than 100 objects of IS-U
and the steps for implementation goes like this:
1)You have to create a user specially for migration which will have all the authorizations related to migration workbench, BASIS and IS-U
2)You have to create your own company in EMIGALL. There is a default company called SAP.
3)Company SAP contains all the Business Objects
4)You have to figure out what business objects u need and then u have to copy those business objects to ur company from Standard Company SAP
5)Each objects contains more than one structure and each structure can contain more than one fields. The relation goes like this
Object ---> Structure ---> Field
6)You have to define field rules for each required field of the object. You have to mark "Not required" for fields u don't need
7)After field rules for a given object is set u have to generate load report i.e. actual Direct Input Program which will migrate data. This program is generated on basis of field rules set by u.
8)After the load report is generated u have to prepare an input file (import File) for migration. The import file should be according to structure provided by SAP and must be in binary format. SAP Provides the structure of file according to your configurations. You have to write ur own Data conversion program(in any language) for this task.
9)You take import file as input and migrate the data using generated load program
10)Finally u can check the Migration Statistics and Error Log
Thanks and Regards,
Jyotishankar Dutta
Message was edited by:
Jyotishankar Dutta
Message was edited by:
Jyotishankar Dutta

Need Help in Data migration from standard 10g to standard to 11g RAC

Hi,
We are running an application in Standard 10g (Not RAC). Our service provider has installed a fresh standard 11g RAC and did not transfer the data from 10g to 11g RAC.
I want to migrate the 10g data to 11g RAC.
I wanted to know the followings
1) Easy data transfer technique (Data Pump or RMAN) & How do I do that (Steps)
2) How to backup the fresh 11g RAC (In case of errors in data transfer process to recover the base) (How to do)
Appreciate your help as I only have average knowledge in DBA.
Thanks.
Jezee
Edited by: 991554 on Mar 3, 2013 11:27 PM

See the 11g Upgrade guide chapter "Moving Data Using Oracle Data Pump" http://docs.oracle.com/cd/E11882_01/server.112/e23633/expimp.htm#i262220
See the 11g RAC Administration and Deployment Guide chapter "Managing Backup and Recovery" http://docs.oracle.com/cd/E11882_01/rac.112/e16795/backup.htm#i443637
Get some training on 11g Grid Infrastructure and RAC
Hemant K Chitale

Legacy Data Migration - question on conversion

Hello All,
We are trying to build a generic tool which could help the conversion process in data migration.
For eg, If the material name in legacy starts with AB (AB6790), the same has to be referred in SAP as SQ6790.
So its replacing initial few characters during the conversion process.
Like this, I am expected to collect possible scenarios and
develop a generic tool, which can cover some possible conversion conditions.
Can you please help me with such scenarios, which you may have come across in project needs.
Thank you.
Meenakshi

Rahul,
I strongly suggest you do a search in the CRM General & Framework Forum on this topic. If you are looking for specific objects to migrate there are several posts on the major data elements in crm (transactions, business partners, products).
In general the technique is to use the LSMW combined with the XIF-IDOC adapter to convert data into the CRM system.
My blog here will explain the general process:
/people/stephen.johannes/blog/2005/08/18/external-data-loads-for-crm-40-using-xif-adapter
Thank you,
Stephen

Data Migration from 4.6C to ECC 6.0

Hi all,
Can you suggest me solution for data migration from 4.6C to ECC6.O which technique to be used!!
if you have the documents regarding the above post it which will be useful!!!
Thanks,
Yogeshwaran K S

Hi Yogesh
OS migrations are more or less painless beside the fact, that most "Unix" operating systems are using a different endianess (aside from Solaris on X86_64). For RFC and other SAP proprietary communication this is done in the kernel but if you use own software to read BINARY data (not talking about textfiles) you need to take care of that in your software.
Hope ths helps
Please reward points
Sunil

Data trasfer techniques

Hi,
We have so may data transfer techniques such as BDC, LSMW, BAPI, IDoc.
What is the each technology for? I mean what is the significance of each technology?

Hi Sandeep,
BDC is the old technic used for DATA transfer. SAP Replaced all BDCs with BAPI function modules in the newer versions. SAP doesn't encourage using BDC. Almost for all transactions we have readily available BAPIs. Both will do the same thing
i.e Updating the data base. BDC and BAPI can be used both from with in SAP or from Non SAP to SAP.
eg: If we are going to change some order information it will be with in SAP. We will get the order details from SAP database and change the details using BDC or BAPI.
If we are going to create new order by uploading the data from Flat files then it will be between Non SAP to SAP.
Another important point is All BAPIs are RFCs. SO u can use
BAPI from another system also(SAP/NonSAP)
LSMW is generally used for initial migration of legacy data from Non SAP system to SAP system.
IDOC is used to send and receive the documents/data From SAP to SAP or Non SAP to SAP or SAP to Non SAP. I heard that it is possible to send the data between 2 Non SAP systems also using IDOCs.
Thanks,
Vinod.

Data Migration examples

can give some examples on data migration?...thanks.

Hi Gow.
Difference Between Batch Input and Call Transaction in BDC
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is
not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program.
Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling. It can also be used for real-time interfaces and custom error handling & logging features. Whereas in
Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are not available for all application areas.
Differences between bdc session method and call transaction method.
The most important aspects of the batch session interface are: - Asynchronous processing - Transfers data for multiple transactions - Synchronous database update During processing, no transaction is started until the previous transaction has been written to the database. - A batch input processing log is generated for each session - Sessions cannot be generated in parallel
The most important aspects of the CALL TRANSACTION USING interface are: - Synchronous processing - Transfers data for a single transaction - Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. - Separate LUW for the transaction The system performs a database commit immediately before and after the CALL TRANSACTION USING statement. - No batch input processing log is generated.
Explain in detail with example what is batch input session?
Batch Input Session:
- It is a sequence of transactions, which is generated when user run a particular program.
- It contains the accounting documents that are to be created. The SAP system stores these transactions until you decide to process them online.
- It does not update transaction figures until the session has been processed. Using this technique, you can transfer large amounts of data to the SAP system in a short time.
Three processing modes of executing Batch Input Session :-
(1) Run Visibly : You can correct faulty transactions online & work step-by-step through the transactions not yet executed.
(2) Display Errors only : You can correct faulty transactions online. Transactions not yet executed, but without error, run in the background.
(3) Run in Background : Recommended by SAP.
Kindly Reward Points If You Found The Reply Usefull,
Cheers,
Chaitanya.

Data Migration- Infotypes BDC Recording

Hi All,
Iam currently working on data migration project.
Before i joined here,they developed the upload programes,by using Function modules.But when we are doing that,we are able to see in Over veiw,But when we go to change mode,nothing is there on screen.Then we tried Using BDC Recording for IT0105.Then working perfectly.
So i need a help,if any one of you any idea on list of the Infotypes which need BDC Recording.
I need the List of infotypes,so that i make sure,we use BDC .
Its on priority,Pls have some inputs.
Thanks,
Anitha

Hey Anitha,
BDC and LSMW are both data loading techniques.
In both cases you will need input files in a specific format so that these are read by your BDC or LSMW program
The main difference is
Using BDC you can validate the data in the system. Suppose you want to check if an employee is active before loading the data then BDC is advisable because you can check the employment status of the employee and then upload data or else give a message that employee is terminated and data loading has been skipped
If there is a straight forward upload without any validation then go for LSMW
Finally it depends on your requirements
Cheers
Ajay
As stated above IT 0008 has to be filled using table control hence BDC is helpful
Edited by: Ajay Hosur on Apr 13, 2010 6:41 AM

HELP ME ON DATA MIGRATION PLEASE

Hi
what is SAP data migration what kind of tools and techniques include in that and also please what are the roles and responsibilities include in that when we are working on project.(RELATED TO ABAP)

Data Migration Current Situation
Data migration or data conversion is a persistent issue facing most organizations who have implemented SAP. Whether it is during the final phases of a new SAP implementation, during SAP upgrades and updates, during corporate restructurings, or during mergers and acquisitions, data migration continues to remain a challenging problem for IT.
Most data migration projects are faced with a time and budget crunch. But, these projects usually require extensive support from programmers and other technical experts and therefore data migration projects tend to get expensive and time-consuming.
The tools for data transfer and data migration provided by SAP are very technical and have a steep learning curve associated with them and they require technical experts to build and implement the data migration scripts.
Data Migration Ideal Scenario
An ideal data migration scenario would let the data migration project be implemented by the end user departments themselves. A few super-users within these end-user departments that supply the data should have the ability to transfer and migrate data themselves without relying on technical experts. Such a scenario would significantly cut the time and effort required in a data migration project.
Reaching such an ideal scenario would require data migration tools that are easy to learn and require no programming. Furthermore, these tools should work across all the different SAP modules and the SAP products, including the different versions of SAP.
Data Migration
Data Migration is the process of moving required (and most often very large) volumes of data from our clients existing systems to new systems. Existing systems can be anything from custom-built IT infrastructures to spreadsheets and standalone databases.
Data Migration encompasses all the necessary steps to cleanse, correct and move the data into the new system *. Technological changes, change in providers, software updates or data warehousing / data mining projects make such delicate and critical operations necessary.
Data Migration can be done using BDC, LSMW, BAPI, Idoc's.
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Differences between bdc session method and call transaction method.
The most important aspects of the batch session interface are: - Asynchronous processing - Transfers data for multiple transactions - Synchronous database update During processing, no transaction is started until the previous transaction has been written to the database. - A batch input processing log is generated for each session - Sessions cannot be generated in parallel
The most important aspects of the CALL TRANSACTION USING interface are: - Synchronous processing - Transfers data for a single transaction - Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. - Separate LUW for the transaction The system performs a database commit immediately before and after the CALL TRANSACTION USING statement. - No batch input processing log is generated.
Refer this
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
http://www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_DATADICTIONARY_FAQ.html
http://www.****************/InterviewQ/interviewQ.htm
http://help.sap.com/saphelp_46c/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Check these step-by-step links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
regards,
srinivas
*reward for useful answers*

Fixed Asset Data Migration Wizard

Hi All,
I tried to use Fixed Asset Data Migration Wizard to migration my fixed asset data from 8.82 to 9 in the development server. The server only accessible by myself.
When I start the migration run, system prompt me " To Continue with the fixed asset data migration, you must be the only user logged on to this company data".
In fact I'm the only user in the company data and system not allow me to execute the migration.
What are the causes that system recognise there is another user in the system?
Please advise.
Thanks in advance.
Best Regards,
Foong Yee

Hi,
If you're using SQL Server, try Detach (close existing connections) and re-Attach the database again then re-login and try executing again the wizard.
Regards,
Donald

Data Migration for Open Purchase Order

Hi, All,
Is there anyone know how to Count the volume for Open Purchase Order. What's the normal strategy for the Data Migration and Cut-over stage?
My client want to know how many Open Purchase Order in the legacy system and then determine manual or automatic data migration. If manual, how to do? If automatic, how to do? Because all materials and vendors, plants are different number. How to track? How to find out to match between new and old?
Thank you very much

JC,
Sounds a bit early to be making decisions about the realization phase. It doesn't sound like you have finished the Blueprinting phase yet, much less the testing phase.
Anyhow, in my experience I typically use LSMW (Legacy system migration workbench) to load MM master data (material masters), Inventory (WIP, RM, FG, etc) Purchasing Master data (Vendors, Purchase Info Records, Source Lists, Quota Arrangements), and Purchasing transactional documents (POs, PurReqs, Scheduling Agreements, etc). Depending on the complexity and volume of data, it may be necessary to write custom programs to load the data. You will find this out during your requirements gathering.
It is uncommon but possible to load all of these data manually. I have never run across a client that wants to pay a consultant's hourly rate to sit at a terminal to peck away loading master data, so if the client intends to have his own users enter the data manually, the project manager should make provision that there will be qualified TRAINED client employees available for this data entry. I did help with a portion of a conversion once manually; of Sales Credits, but there were only about 30 SD docs to load. I did this the evening before go-live day, while I was waiting for some of my LSMW projects to complete in the background.
A good opportunity to 'practice' your data loads is right after you have completed your development and customization, and you have gotten the approval from the client to proceed from the pilot build to the full test environment. Once you have moved your workbench and customization into the client's test environment, but before integration testing, you can mass load all, or a substantial portion of your conversion data into the qual system. You can treat it like a dry run for go-live, and fine tune your processes, as well as your LSMW projects.
Yes, it is good practice to generate comparisons between legacy and SAP even if the client doesn't ask for it. For Purchase orders on the SAP side, you could use any of the standard SAP Purchasing reports, such as ME2W, ME2M, ME2C, ME2L, ME2N. If these reports do not meet the requirements of the client, you could write a query to display the loaded data, or have an ABAPer write a custom report.
You didn't ask, but you should also do comparisons of ALL loaded data - including master data.
It sounds like you are implying that the client wants YOU to extract the legacy data. For an SAP consultant, this is not very realistic (unless the legacy system is another SAP system). Most of us do not understand the workings of the myriad legacy systems. The client is usually expected to produce one or more legacy system technical experts for you to liase with. You normally negotiate with the technical expert about every facet of of the data migration. In addition, you will liase with business users, who will help you and the implementation team to logically validate that the final solution (turnkey SAP production system, fully loaded with data) will meet the client's business needs.
Finally, you mentioned how do you track the mapping of master data between legacy and SAP. There are many ways to do this. I normally try to get the legacy person do the conversion on his end, eg, when he gives you the load file, you would like to have already translated the master data and inserted the SAP relevant values into the file. If this is not possible, I usually use MS Access databases to maintain a master map, and I perform the mapping on a PC. If your data package is small, you can probably get by using MS Excel or similar.
Good Luck,
DB49

Data migration of open production order

Hello SAP gurus,
Please advise me about the steps that should be followed for data migration of open production order from legacy to SAP.
Regards,
Anand

Hello SAP gurus,
Please advise me about the steps that should be followed for data migration of open production order from legacy to SAP.
Regards,
Anand

Data migration

Dear all my friends,
please help to share me about data migration before go-live FI system.
i plan to migrate GL acct balance, AP/AR open item and last 3 months historical data.
please help to show me : how should i do ?
thanks !

1. Normal GL Accounts: In this case line items are not required and totals are to be updated in SAP. This can be done using GL fast entry if the number is not too high.
2. Open Item Managed GL Accounts: All the open line items are required to be uploaded in SAP from Legacy in order to clear them. Hence, a LSMW / BDC program has to be developed to upload the line items.
BAPI_ACC_DOCUMENT_POST - for GL/AP/AR
BAPI_ACC_INVOICE_RECEIPT_POST - for AP
BAPI_ACC_GL_POSTING_POST - for GL
GL Balance
F-02 or RFBIBL00 or BAPI
Dr GL a/c Credit Data migration Account or Clearing Account
3. Customer & Vendor Open Items: All open line items in Customer and Vendor Accounts have to be brought in into SAP. For this also a LSMW / BDC program needs to be developed and upload the line items.
Vendor Balances
F-02 or RFBIBL00 or BAPI
Credit Vendor a/c (individually) and Dr Data migration Account or Clearing Account
Customer balances
F-02 or RFBIBL00 or BAPI
Dr Customers a/c (individually) and Dr Data migration Account or Clearing Account
4. Asset Accounting: In case asset accounting is implemented the individual balances of each asset (Gross Value and Accumulated Depreciation) have to be uploaded using transaction AS91. For this also you need to develop a LSMW / BDC program. Further, you also need to update the GL Accounts related to Asset Accounts with totals for each asset class T.Code OASV.
For uploading the Assets
AS91 -> for uploading assets in AA
OSAV --> for uploading assets in GL entry Dr Asset (individually) Cr Data migration Account or Clearing Account
You can use LSMW for uploading all these things
After uploading all, your data migration account will become zero

Confuse on PR & PO data migration approach new to MM module

Hi All,
I'm pretty confuse with the PO data migration approach when it comes to PO is GR or partial GR or GR&IR. I'm hoping that someone can enlighten me. i understand that we typically don't migrate PO when it is GR & IR, FI team usually will bring over to the new system as an vendor open item in AP. How about the PR or PO which have gone through or half release strategy? What is the follow up process? I have created a criteria table below. How Could someone point me in the right direction? Thanks in advance.
PR
Criteria
Data migration required
Notes
Open and Released
Y
Open and not Released
Y
Flag for Deletion
N
Flag for Block
Y
PO
Criteria
Data migration required
Notes
Open and Released
Y
Open and not Released
Y
GR but no IR
GR & IR
N
AP will bring over as open item
Flag for Deletion
N
Flag for Block
Y
Partial
Y
For partial GR to recreate PO only with missing GR quantity
Regards,
John

Hi John,
The approach that i have followed recently is that we have considered PO as the base document and converted other documents based on the PO condition. This means you first need to see if the PO is to be converted or not. Then you can proceed to convert the related documents like PR, Agreement, Info record, Source list, etc.
Also open qty for PO should be considered for Material and Service line items both.
Once a GR/SES is created, it gets updated in the PO history table EKBE with its related transaction/event type.i.e. EKBE-VGABE = 1 for GR and 9 for SES. Quantity and value also gets updated in case of material and services. You can compare this consumed quantities with PO quantity.
Please see below from SCN and let me know if you need more info on PR or PO conversion.
Purchase Requisition Conversion Strategy
Thanks,
Akash

Data Migration techniques

Similar Messages

Maybe you are looking for