SAP MRP4 View

 
SAP MRP 4 View:
 
MRP 4 View contains the following fields:
 
 
SAP MRP4 View
 
 
 
Selection Method:
 
 

This field determines which Alternative Bill of Material the system selects during the MRP run. It is a Standard SAP Pre-configured selection.

 

With Selection by order quantity, the system chooses the alternative BOM into whose lot size range the order quantity falls. The lot size range and area of validity of the BOM apply.

 

With Selection by explosion date, the system chooses the alternative BOM into whose area of validity the date falls according to the setting BOM via dates.

 

With Selection by production version, the system chooses the alternative BOM defined in the valid production version. The lot size range and area of validity of the production version apply.

 

With Selection only by production version, the system chooses the alternative BOM defined in the valid production version. The lot size range and area of validity of the production version apply. If no production version is found, no production orders or process orders can be created.

 

 
 
Individual/Collective Requirements:
 
 

This field controls how the Dependent Requirement are displayed in the Stock/Requirements list – as individual records or collectively (grouped together)

 

Indicator determining whether the following requirements are allowed for the dependent Requirements of the material. You can also define this in the explosion type of the BOM item (in Customizing for Basic Data in Define Explosion Types)

                       

Individual requirements: Requirement quantities of the dependent material are stated individually. This is predominantly done for a Made to order material, where the requirements are stated individually against a sales order and are not collectively planned.

 

Collective requirements: Requirement quantities of the dependent material are grouped together.

 

 
 
Requirements Group:

 

It defines whether the system groups together Dependent requirement for the material on a daily Basis. When analyzing requirements planning. If several requirements exist on a day, the system Groups them together & displays one line item.

 

It is standard SAP pre-configured selection.

 

 

Version Indicator:

 

This field indicates whether a Production Version exists for this material.

 

 

 
Production Version:
 
 
Definition:

 

This tab gives the details about the Production Version/s maintained for the material. Production Version determines the Alternate Bill of Material & the Task List type/group used for Production of this material.

 

Production Version defines for a material, the Bill of Material & Routing {Recipe} combination, for the production of a material, for a given Validity date & a lot size range.

 

It is a key which determines the various production techniques according to which a material can be manufactured.

 

Use of Production Versions:

 

We can have multiple Bill of Material’s and Recipes for a Material, but at a given date or for a given lot size it is mandatory for the system to keep one Bill of Material and one Routing/Recipe. This helps the system, in picking the predefined BOM and Routing/Recipe rather than going mad on which to pick in the automatic MRP run.

 

If the lot size of the product does not govern the selection of a bill of material and routing {recipe}, we can keep it as 0 – 99 units. And if the dates of production do not govern the selection of bill of material and routing, we can keep the validity dates as “today – 12/31/9 {MM/DD/YYYY}”.

 

Question: Can we have many predefined production versions?

 

For a given material we can have many Production Versions for different Bill of material and Routing/Recipe combinations for different Lot sizes and different validity periods, but at a given time, the system considers only one production version according to dates or lot sizes and if dates and lot sizes are not the criteria, the system picks up the first production version maintained for the material.

 

Transaction codes to maintain them is through MM01/MM02/CC23

 

 
 
MRP Dependent Requirements:
 
This field controls the relevance of the Dependent requirements to MRP. It is used to avoid duplication in planning at this material level. It may happen that the material is planned through PIR and its requirement also comes in as a dependant requirement through the planning of its higher level material, therefore to avoid this, we set this indicator as “Materials for dependent requirements are not planned”.
更多相关文章
  • 1.  Material Master > MRP4 --> BOM explosion/dependent requirements - > individual / collective requirements       Individual collective indi ...
  • SAP MRP1 View
     MRP 1 View   The MRP 1 View is a place holder for defining the Planning methods and lot sizing procedures of a give material at a plant/storage locat
  • SAP MRP2 View
     SAP MRP 2 View:         Procurement Type (Plant Specific):     Procurement type indicator defines how the material is procured. The following procure
  • SAP MRP3 View
    MRP 3 View: The following are the fields in MRP 3 View:       Strategy Group: A Strategy Group represents the procedure used for planning a material.
  •   上期我们完成了一个简单的主从页面,但是页面是静态的,不能交互,功能也很简单,只有一个销售订单的列表. 我们今天就一鼓作气把代码全都写完,由于本次的代码量较大,所以只对重点代码部分进行讲解. 具体每个文件和代码就不一一贴出来了,代码都放在github中,需要的自行下载吧. 1 页面导航 可以先把代 ...
  • Dependent requirements ind. for individual and coll. reqmts Indicator determining whether the following requirements are allowed for the dependent req
  • SAP Work Scheduling View
     Work Scheduling View: To produce an assembly or subassembly, you  need to maintain a work scheduling view for the material.         Production Schedu ...
  • OPEN(SAP) UI5 學習入門系列之三:MVC (上)
    这次我们来一起学习MVC,这个专题分为两个小节,本次主要是总览以及模型,下一次着重会介绍视
一周排行