0% found this document useful (0 votes)
809 views6 pages

LSMW Documentation

The document outlines the LSMW objects used in an MRP Bottling Project. It describes 14 objects that perform various material and MRP related processes like closing POs, changing material types and prices, creating BOMs, and updating MRP settings. The objects take different files as input and use transactions like BAPI, MM01, MM02 and MR21 to make the required changes in SAP.

Uploaded by

Mel Starkie
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
809 views6 pages

LSMW Documentation

The document outlines the LSMW objects used in an MRP Bottling Project. It describes 14 objects that perform various material and MRP related processes like closing POs, changing material types and prices, creating BOMs, and updating MRP settings. The objects take different files as input and use transactions like BAPI, MM01, MM02 and MR21 to make the required changes in SAP.

Uploaded by

Mel Starkie
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 6

MRP Project – LSMW Documentation

Changes History
Issue No Date Change

1.0 06/02/2008 Initial Draft


2.0 14/02/2008 MAT09 and PIR
3.0 16/04/2008 Following Go-Live

Introduction
This document outlines the various LSMW objects being used in the MRP Bottling
Project. They are all in project ZMRP1 as this allows fixed values and user routines
to be shared across different objects.
The subproject ID is used to group the objects in logical groups
LSMW Object List
Object Name Purpose Dependencies Process Outline
COMP01 Close down component The input is a file of PO/Items – this can be generated by
PO’s ZMMR0040
This is fed into the BAPI that changes PO’s
If the PO item is still open, then it is changed by setting the
order quantity to the delivered quantity, the final delivery
indicator and the deletion flag.
Note: The IDoc will fail if the PO item is not completely
invoiced. This process must be do manually (e.g. via
transaction MIRO)
MAT03 Change Material Type COMP01 The input is a list of materials and their current and proposed
material types which provides a feed to a recording of
transaction MMAM.
The material is validated and also checked that it has not
already been changed.
A further check is performed that there are no open purchase
order lines as such materials cannot be converted
This check is done for plant SHOB only
MAT08 Set up materials for The input is a file of material types
Accounting The program generates a table of all materials for the type
that have not been set up for accounting (status ‘B’) for plant
SHOB.
This is fed into RMDATIND where the price per is set to
1000.
If there is a set price control indicator for the material type,
then the material set up for this.
Object Name Purpose Dependencies Process Outline
MAT07 Correct Price Type and The input is a file of material types
Unit The program generates a table of all materials for the type
that do not have a price per of 1000. This is fed into
RMDATIND where the price per is set to 1000.
If there is a set price control indicator for the material type,
then the material is changed if required.
MAT1FG Update MRP settings MAT02, MAT04 Provides feed to Direct Input program RMDATIND
for Finished Goods Check that the material exists.
If it is not already set up for MRP (Material Status) ‘D’, then
an MM01 transaction is performed, otherwise MM02
Some differences in settings are made depending on
whether the material type is ‘ZUNB’ (Contract) or ‘HAWA’
(Own)
MAT1COMPA Update MRP settings MAT02 This is similar to the above, but has been split off because
for Components the data is set up separately and some the MRP settings are
different from FG.
At the moment there is no difference in settings between the
two material types (ZOCP and ZZCP).
MAT02 Create Storage The input is a list of material / plants
Locations Provides feed to Direct Input program RMDATIND
Check that the material exists.
Check that the material does not exist in any of the storage
locations PCKG and QUAL – create it where required.
RMDATIND requires that at least one field be filled in for the
store – the bin location is set to blank.
MAT04 Create Work Scheduling The input is a list of material / plants
View Provides feed to Direct Input program RMDATIND
Check that the material exists and is of type HAWA or ZUNB
If the material status is not A, then create the view with
certain default values
Object Name Purpose Dependencies Process Outline
BOM1 Load the bottling BoM’s Materials and Creates Batch Input for RCSBI010
Components must exist Check that the material exists and there is not already a BoM
and set up with the Check that the component exists and that the unit of
correct base UoM measure is valid.
Report the counts of invalid data found.
MAT09 Change Material MAT08 The input is a list of material / valuation classes
Valuation Class Provides feed to Direct Input program RMDATIND
The materials to be changed cannot have any open PO’s or
Prod Orders, nor any stock
No validation is in place
MAT05 Update Material Price MAT03 Provides feed to a recording of MR21
MAT07 Check that the material exists and has been set up for
Accounting
MAT06 Stock Takeon MAT03 Provides feed to a recording of MB1C – MVT 561
MAT07 Check that the material exists and has been set up for
Accounting
Check that the input UoM exists for the material
A message is issued if the material already has stock
MAT10 Create Free Issue Creates materials as type ZCCP in SHOB
Materials Provides feed to Direct Input program RMDATIND
This did not create Purchasing or Accounting views which
were later found to be needed.
MAT11 Change Profit Centre Change profit centre
Provides feed to Direct Input program RMDATIND
No validation is in place
MAT12 Change Unit of Measure Changes unit of measure to THS for a list of products
Provides feed to a recording of MM02
No validation is in place
MAT13 Change Unit of Issue Reads all components in the input plant and selects those
where the base unit of measure is not ECH. Set the issue
unit to ECH or G depending on the base unit.
Provides feed to Direct Input program RMDATIND
Object Name Purpose Dependencies Process Outline
MAT14 Add Pallets and From a list of material, set up the alternate units of measure
Trunkers for Glasses for Pallets and Trunkers.
Provides feed to a recording of MM02
MAT15 Add Customer(External From a list of materials, update the external material group.
Material Group) Provides feed to Direct Input program RMDATIND
As developed the validation rejected materials of type ZUNB
and HAWA- this may not be correct.

ROUT01 Routings Load MAT04 Creates Batch Input for RCPTRA01


ROUT02 Routings Load MAT04 This is a simpler file layout, where only bottling times are
input. The setup time is defaulted in.

FOR01 Load Independent MAT01FG The input is a reformatted file from ZMMR0060 with one
Requirements entry per material/month. This program does the checking
that the material exists and has been defined with a Strategy
Planning Group.
Input is in to a recording of MD61 – which also allows
existing data to be changed.
PIR01 Loads Purchase Info MAT08 IN DEVELOPMENT
Records Creates a batch input for RM06IBI0
Performs either ME11 or ME12 depending on if a PIR
already exists

User Defined Routines


Routine Purpose
CHECK_MATTYPE Retrieves the material type – if the material does not exist an error flag is returned
CHECK_PO_DOCS Retrieves a table of open PO orders for a given material in SHOB. This uses the SAP
Function Module ME_CHECK_DOCUMENT_FOR_MATERIAL
CHECK_STOCK Retrieves the current available stock and UoM for a material/plant/store
CHECK_UOM Retrieves the base UoM and whether the supplied UoM exists as the base or an
alternative for the base UoM
GET_PO_ITEM_DETAILS Retrieves details of the ordered and delivered quantity of a PO item. If the PO item has
been flagged for deletion, then an error flag is set.
IS_THERE_A_BOM Checks if a production BoM exists at a plant and sets an error flag if it does not.
VALIDATE_MATERIAL Checks that a material exists in an active state at a plant. If it does, the material status is
retrieved, if it does not, then an error flag is set.
VALIDATE_VENDOR Checks that a Vendor number is valid and that the vendor is active for purchasing

You might also like