The system uses a predefined search strategy to determine the requirements type:
1. First, an attempt is made to find a requirements type using the strategy group in the material master.
2. If the strategy group has not been maintained, the system will determine it using the MRP group.
3. If MRP group has not been defined, the system uses the material type, instead of the MRP group, when accessing the corresponding control tables.
4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.
5. If this is not possible, a last attempt is made to find a requirements type with the item category only.
6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or Transfer of requirements.
需求类型确定优先顺序
1.定义策略(分配需求类型),定义策略组,为物料设置策略组;
2.为MRP组分配策略组,并为物料分配MRP组;
SPRO路径:生产——生产计划——需求管理——已计划的独立需求——计划策略——定义策略组(将策略分配给策略组)
物料主数据MRP组 MRP1 视图1
3.为物料类型分配MRP组,为MRP组分配策略组,物料新建时选的物料类型;
SPRO路径:生产——物料需求计划——MRP组——为每一个物料类型定义MRP组
物料创建时选定物料类型
4.为SO项目类别与MRP组分配需求类型;
SPRO路径:销售与分销——基本功能——可用性检查和传输需求——传输需求
定义需求类/为需求类型分配需求类/按项目类别和MRP类型分配需求类(MRP类型可为空)
5.为SO项目类别(MRP组为空)分配需求类型;
同4。