In the previous post about stock transfer between plants, I have explained that we can transfer stock between two plants in SAP ERP with:
In this post I will explain stock transport order without Sales & Distribution (SD) delivery function. Continue reading
An SAP MM user can create a Purchase Requisition (PR) with ME51N transaction code (t-code). In SAP, the PR can be processed automatically into a Purchase Order (PO) with less effort by buyer/purchaser (which often the different party than the PR creator). But, to make this run well, there are some prerequisites that must be fulfilled before, which are:
On previous post, I have explained how to create SAP LSMW program with Standard batch/direct input method to create Purchase Requisition (PR) document with multiple items. In this post, I will show you how to create LSMW program with recording method in videos training. You can see the videos and the explanation of step by step guide how to create LSMW program with recording method for creating vendor master data (XK01) as follow: Continue reading
(Legacy System Migration Workbench), from its name, is a tool in SAP ERP that allows us to do the migration data from Non-SAP system to SAP system. It’s usually used in the Go-live preparation phase of SAP implementation project to create multiple records of SAP master data or transaction data (such as material master, vendor master , customer master, purchasing document, etc), without entering them one by one.
With LSMW, SAP can read an input file, for example a .txt file, which contains multiple records with some columns, and then convert them into SAP data. Of course, we had to define the format of the input file and the conversion rule first before we run the LSMW tool. The contents of the input file can be the master or transaction data form legacy system that needs to be migrated to SAP system.
LSMW can be used not only for data migration, but it also can be used in the production phase of SAP implementation for various needs, such as to create or update master data or transaction data which are not efficient if we do it one by one. Although SAP has provided “mass change” functionalities such as MM17
tcodes, with LSMW, we have more flexibility in terms of fields that can be changed.
Purchase Requisition (PR) is an internal purchasing document in SAP R/3. It is used to give notification to responsible department (purchasing/procurement) of requirements of materials and/or external services and keep track of such requirements. PR must contain information about quantity of a material or a service and the required date.
It can be created directly (manually, through ME51N T-code) by a person or indirectly by another SAP component (such as material requirement planning/MRP, maintenance order of Plan Maintenance/PM module, production order of Production Planning/PP module).
PR then can be processed to be an external purchasing document (such as Purchase Order/PO) or internal purchasing document (such as Stock Transport Order/STO).
In SAP R/3, PR can be processed directly to be PO/STO or must be approved/released before it can be processed to be PO/STO.