Low level code is widely used in MRP run.It comes from BOM.We can check it in MM03 MRP3 tab page.
Low-level code is used in MRP to determine which material run at first.The lowest level materail runs at last.
Material status is widely used in SAP.In material master data,we can check material status in MRP1 ,Basic data1 and Sales:sales org.1 .
Material status in Basic data1 is cross plant.
The option of the data in MRP 1 and Sales:sales org.1 is different.
In sales tab,the material status controls if the material can appears in sales related document,such as sales order,delivery and son.
We can use material status here to block material for sale.This is very important to SD module.Sometimes when you want to block material for sales temporaryly,you can set this field in material master data.
![OA2ANES6XPNDFF]Z_63KYMD](http://www.sapgeek.net/wp-content/uploads/2011/10/OA2ANES6XPNDFFZ_63KYMD.jpg "OA2ANES6XPNDFF]Z_63KYMD")
The configuation for the sales related is in the path
SPRO->Logistics – General –>Material Master->
Settings for Key Fields->Data Revelant to Sales and Distribution->Define sales status.
Similarly,the settings under the path
SPRO->Logistics – General –>Material Master->
Settings for Key Fields->Define material statues
controls the material status related with MRP , purchase ,BOM and so on.
If you want the detail,please refer the settings according to the path above.
Shop floor paper print is requried in some scenario.
SAP provides some interface for us to print shop floor paper.
CO04N and CO02 can be used to print shop floor paper.
CO04N is for mass processing while CO02 is for individual process.
In OPK8 we can configure the print.
(SPRO->Production->Shop Floor Control->Operations->Define Print Control)
![44Q[)%V{]D6VBVL91Z{MM7J](http://www.sapgeek.net/wp-content/uploads/2011/10/44QVD6VBVL91ZMM7J1.jpg "44Q[)%V{]D6VBVL91Z{MM7J")
Individual and collective requirements are very important in MRP running.The settings related with these two kind of requirements
are in MM03,materail master record->MRP 4 view
There are three options for this field.
This indictor influence how mrp consider about dependent requirements.
Dependent requirements are the requirements that come from BOM explosion.
For example,there is an order for material A 1000.
COGI is a powerful tool that help us detect the mistake happens in goods movement.
The user can delete the log of COGI as he like.Sometimes,the customer will require us to retrive the deletion log of COGI,and display it in ALV.
We can achieve this as below instruction.
System save the log in the table AFFWPRO.But the save function is closed in default settings.
For activing this function,we should adjust the standard function module
CO_FW_AFFW_POST,
Search “ CLEAR prot_del_is_active. “ in SE37.Comment the line contains “CLEAR prot_del_is_active.”,and then,we can get the deletion log in the table AFFWPRO.Next job is to display it in ALV.
Some material is the component of the BOM and some material is the final product and is linked to a BOM. Below is logic to check whether a material is a component or is linked to a BOM.
First, check table STPO (BOM item). If the material name is in field STPO-IDNRK(BOM component), it means the material is part of the BOM.
Second, check table MAST(Material to BOM Link). If the material is in MAST table, it means this material is linked to a BOM.
Tables:
MARA – General Material Data
MAST – Material to BOM Link
STKO – BOM Header
STPO – BOM item
