A Quick Guide to Migrating Six Procurement Data Objects in Your SAP Project

  • by Yogesh Lohiya, Senior Consultant, Infosys Ltd.
  • June 29, 2012
Learn how to automate the uploading of procurement objects in your SAP project using the SAP Legacy System Migration Workbench. Walk through the steps for uploading data for the Purchase Requisition (PReq) object, including how to prepare the data for uploading. Then learn how to easily apply the process to your other procurement objects: purchase orders, scheduling agreements, contracts, purchasing information records, and source lists.
Key Concept
Purchasing master data and transactional data are two of the most critical objects one to consider when implementing an SAP system, upgrading from an older SAP system to SAP ERP Central Component (ECC), or any other scenario in which you have to upload data into an SAP system. One of the most efficient ways of performing these tasks is by using the SAP Legacy System Migration Workbench (LSMW). SAP LSMW is a free tool that supports data migration from non-SAP legacy systems to SAP systems. It allows you to read, convert, and import data.

Requirements for uploading data of procurement objects are unique based on the specific scenario. For example, your company is moving from a non-SAP system or upgrading from an older version of an SAP system (such as SAP R/3 4.7) to a newer version of SAP ERP Central Component (ECC). Another example would be a company with an SAP system that acquires another company with a non-SAP system and now must face integrating the two systems.

To achieve this, you have to migrate data from that acquired company’s system to your SAP ECC system or merge the other company’s code into your SAP system-based company code. In this scenario, you might also need to change organizational data, such as plants, on existing purchasing master data or re-create purchase orders (POs) in your existing system. In yet another scenario, procurement data may need to be uploaded to your SAP system. When performing these necessary tasks, having a single guide that contains all the details of all the programs that are used for procurement object uploading saves you hours of time and effort.

I show you how to use BAPI and IDoc methods in the data migration of procurement objects via SAP Legacy System Migration Workbench (SAP LSMW). I also provide you with guidelines for uploading data for a purchase requisition (PReq), purchase order (PO), scheduling agreement (SA), contract (MK), purchasing information record (PIR), and source list (SL), including:

  • The complete end-to-end steps involved in migration of a purchase requisition via SAP LSMW
  • Detailed data transfer methods for each object
  • The source structure in SAP LSMW for each object
  • The source fields to be maintained for each object

Note
For information on the SAP LSMW tool and its functionality, read the following articles:

Note
At the end of this article, I provide sample text files for each object that you can use for your company-specific projects.

Yogesh Lohiya

Yogesh Lohiya is a senior SAP MM consultant with Infosys. He is currently working on a large data migration project for a Fortune 500 client. He has more than nine years of consulting experience. He also has worked on various SAP global rollouts and data migration projects in the materials management area.

See more by this author


Comments

3/20/2013 11:21:13 AM
Ivan D. Miranda

Great article.. thanks for sharing.

I have a question though, when I'm trying to create the same for a Source List and use the mentioned Message Type and Basic Type, I get an error saying "Maintain the default values for IDoc inbound processing". How can I address this issue?

Thanks,

Please log in to post a comment.

To learn more about subscription access to premium content, click here.