SAP MRP Made Easy -[1.5]需求类型的决定过程
2009-06-15 02:10
501 查看
Determination of the Requirements Type
需求类型的决定过程
If you have entered a strategy group or an MRP group containing the appropriate strategies in the material master record, you do not have to enter a requirements type in Demand Management. The system determines the valid requirements type with the strategy group from the material master record and proposes this type automatically when creating independent or customer requirements. If the strategy group contains more than one planning strategy, the system proposes the requirements type of the main strategy. If necessary, you can overwrite this proposal using one of the requirements types from the alternative strategies.
如果在物料主数据中你已经输入了一个包含正确策略的策略组或MRP组,你就不需要再在需求管理中输入需求类型了。系统从物料主数据中的策略组中获得有效的需求类型,并在创建独立需求或客户需求时自动建议。如果策略组包含多个计划策略,系统建议使用主策略的需求类型,你也可应使用替代策略来覆盖已建议的策略。
The following strategy groups combine two planning strategies:
以下策略组包含两个计划策略:
Strategy 31 策略 31
Allows you to select the Make-to-Order Production (20) or Production by Lot-size (30) strategies by selecting the KE or KL requirements types [strategy 20 (KE) is the default]
允许你选择按单生产(20)或按批量生产(30)策略,需求类型是KE或KL [策略20(KE)是缺省的]。
Strategy 32 策略 32
Allows you to select the Production by Lot-size (30) or Make-to-Order Production (20) strategies by selecting the KL or KE requirements types [strategy 30 (KL) is the default]
允许你选择按批量生产(30)或按单生产(20)策略,需求类型是KL或KE [策略30(KL)是缺省的]。
Strategy 33 策略 33
Allows you to select the Production by Lot-size (30) or Planning with Final Assembly (40) strategies by selecting the KL or KSV requirements types [strategy 30 (KL) is the default]
允许你选择按批量生产(30)或带最终组装的生产(40)策略,需求类型是KL或KSV [策略30(KL)是缺省的]
Table of Planning Strategy Assignments
计划策略分配表
The following planning strategies are used in the Project System (refer to the Project System documentation for more details):
以下计划策略使用在项目系统中(参考项目系统文档可以获得根多的信息):
Strategy 21 Similar to 20 with project settlement.
策略21 和20相似,使用项目结算。
Strategy 51 Similar to 50 with project settlement.
策略51 和50相似,使用项目结算。
Strategy 61 Similar to 60 with project settlement.
策略61 和60相似,使用项目结算。
Strategy 83 Assembly processing for PS.
策略83 为PS项目系统的组装处理。
Strategy 85 Assembly processing for PS.
策略85 为PS项目系统的组装处理。
The following planning strategy is used in Service Management (refer to the Service Management documentation for more details):
以下计划策略用在服务管理中(参考服务管理文档获得更多的信息):
Strategy 84 Assembly processing for SM
策略84 为SM服务管理的组装处理
The following planning strategy is used in PP-PI [(Production Planning for Process Industy) refer to the PP-PI documentation for more details]:
以下计划策略用在流程行业的生产计划[(Production planning for Process Industy)参考PP-PI文档会获得更多的信息]:
Strategy 86 Assembly processing for PP-PI
策略86 为PP-PI的组装处理
需求类型的决定过程
If you have entered a strategy group or an MRP group containing the appropriate strategies in the material master record, you do not have to enter a requirements type in Demand Management. The system determines the valid requirements type with the strategy group from the material master record and proposes this type automatically when creating independent or customer requirements. If the strategy group contains more than one planning strategy, the system proposes the requirements type of the main strategy. If necessary, you can overwrite this proposal using one of the requirements types from the alternative strategies.
如果在物料主数据中你已经输入了一个包含正确策略的策略组或MRP组,你就不需要再在需求管理中输入需求类型了。系统从物料主数据中的策略组中获得有效的需求类型,并在创建独立需求或客户需求时自动建议。如果策略组包含多个计划策略,系统建议使用主策略的需求类型,你也可应使用替代策略来覆盖已建议的策略。
The following strategy groups combine two planning strategies:
以下策略组包含两个计划策略:
Strategy 31 策略 31
Allows you to select the Make-to-Order Production (20) or Production by Lot-size (30) strategies by selecting the KE or KL requirements types [strategy 20 (KE) is the default]
允许你选择按单生产(20)或按批量生产(30)策略,需求类型是KE或KL [策略20(KE)是缺省的]。
Strategy 32 策略 32
Allows you to select the Production by Lot-size (30) or Make-to-Order Production (20) strategies by selecting the KL or KE requirements types [strategy 30 (KL) is the default]
允许你选择按批量生产(30)或按单生产(20)策略,需求类型是KL或KE [策略30(KL)是缺省的]。
Strategy 33 策略 33
Allows you to select the Production by Lot-size (30) or Planning with Final Assembly (40) strategies by selecting the KL or KSV requirements types [strategy 30 (KL) is the default]
允许你选择按批量生产(30)或带最终组装的生产(40)策略,需求类型是KL或KSV [策略30(KL)是缺省的]
Table of Planning Strategy Assignments
计划策略分配表
Strategy 策略 | Requirements Type for Independent Requirements 独立需求的需求类型 | Requirements Type for Customer Requirements 客户需求的需求类型 | ||
10 (Chapter 2) | LSF | Make-to-stock production 按库存生产 | KSL | Sale from stock without independent requirement reduction 从库存销售,不消耗独立需求 |
11 (Chapter 2) | BSF | Gross planned independent requirements 毛计划独立需求 | KSL | Sale from stock without independent requirement reduction 从库存销售,不消耗独立需求 |
20 (Chapter 4 | | | KE | Individual sales order without consumption 不作消耗的个别销售订单 |
25 (Chapter 5) | | | KEK | Make-to-order with configurable material 使用可配置物料的按单生产 |
26 (Chapter 5) | | | KEL | Make-to-order for material variants 为变式物料作按单生产 |
30 (Chapter 2) | LSF | Make-to-stock production 按库存生产 | KL | Sales order manufactured by lot size 按批量的销售订单制造 |
40 (Chapter 2) | VSF | Planning with final assembly 带最终装配的计划 | KSV | Sales order with consumption 销售订单消耗 |
50 (Chapter 4) | VSE | Planning without final assembly 无最终装配的计划 | KEV | Make-to-order with consumption 带消耗的按单生产 |
52 (Chapter 2) | VSE | Planning without final assembly 无最终装配的计划 | KSVS | Make-to-stock with consumption without final assembly 带消耗的对库存生产无最终装配 |
54 (Chapter 5) | VSE | Planning without final assembly 无最终装配的计划 | KEKT | Make-to-order with consumption of variant 带变式消耗的按单生产 |
55 (Chapter 5) | VSE | Planning without final assembly 无最终装配的计划 | KELV | Make-to-order variant with consumption 带消耗的变式按单生产 |
Strategy 策略 | Requirements Type for Independent Requirements 独立需求的需求类型 | Requirements Type for Customer Requirements 客户需求的需求类型 | ||
56 (Chapter 5) | VSE | Planning without final assembly 无最终装配的计划 | KEKS | Make-to-order with consumption of characteristics planning 带特性计划消耗的按单生产 |
59 (Chapter 3) | VSEB | Planning; phantom assemblies 计划:虚拟组装 | | |
60 (Chapter 4) | VSEV | Planning the planning material 计划计划物料 | KEVV | Individual customer with planning material consumption 带计划物料消耗的个别客户 |
63 (Chapter 2) | VSEV | Planning the planning material 计划计划物料 | KSVV | Make-to-stock with consumption of planning material 带计划物料消耗的按库存生产 |
65 (Chapter 5) | VSEV | Planning the planning material 计划计划物料 | ELVV | Make-to-order variant with planning material 带计划物料的变式按库存生产 |
70 (Chapter 3) | VSFB | Planning for assemblies 为组装计划 | | |
81 (Chapter 6) | | | KMSE | Assembly planned order 计划订单组装 |
82 (Chapter 6) | | | KMFA | Assembly with production order 生产订单组装 |
89 (Chapter 5) | VSE | Planning for assemblies 为组装计划 | KMSE | Assembly planned order 计划订单组装 |
The following planning strategies are used in the Project System (refer to the Project System documentation for more details):
以下计划策略使用在项目系统中(参考项目系统文档可以获得根多的信息):
Strategy 21 Similar to 20 with project settlement.
策略21 和20相似,使用项目结算。
Strategy 51 Similar to 50 with project settlement.
策略51 和50相似,使用项目结算。
Strategy 61 Similar to 60 with project settlement.
策略61 和60相似,使用项目结算。
Strategy 83 Assembly processing for PS.
策略83 为PS项目系统的组装处理。
Strategy 85 Assembly processing for PS.
策略85 为PS项目系统的组装处理。
The following planning strategy is used in Service Management (refer to the Service Management documentation for more details):
以下计划策略用在服务管理中(参考服务管理文档获得更多的信息):
Strategy 84 Assembly processing for SM
策略84 为SM服务管理的组装处理
The following planning strategy is used in PP-PI [(Production Planning for Process Industy) refer to the PP-PI documentation for more details]:
以下计划策略用在流程行业的生产计划[(Production planning for Process Industy)参考PP-PI文档会获得更多的信息]:
Strategy 86 Assembly processing for PP-PI
策略86 为PP-PI的组装处理
相关文章推荐
- SAP MRP Made Easy - [1.3]确定需求类型
- SAP MRP Made Easy - [1.3]确定需求类型
- SAP MRP Made Easy -[1.4]维护和定义策略及策略组
- SAP MRP Made Easy -[1.1]概览[翻译]
- SAP MRP Made Easy - [1.2]消耗的策略及逻辑
- SAP MRP Made Easy -[1.1]概览[翻译]
- SAP中MRP类型 P1,P2,P3,P4,PD的区别
- SAP中MRP类型 P1,P2,P3,P4,PD的区别
- 网络工程项目需求获取过程中的沟通艺术
- 图解:sap中的账户确定(账户决定或者科目确定)如何实现如总账的集成
- 过程类型
- 时间:2014年3月23日 mySQL建表过程与字符类型意义
- SAP顾问,市场的双重需求
- 足迹, 决定把我学习过程中的知识和困惑记录下来
- 让函数根据一个以上的对象类型来决定如何虚化
- [转]Oracle中字符集的类型决定varchar2的字符长度
- SAP销售订单状态修改(审核) 计划行自动产生需求,产生MD04需求
- 物料移动类型和后勤自动科目设置-SAP屠夫
- 【more effective c++读书笔记】【第5章】技术(7)——让函数根据一个以上的对象类型来决定如何虚化(2)
- 业务、架构、技术,我们应该关注什么 Java和.Net的优势劣势简单看法 市场经济决定,商业之道即是软件之道,市场的需求决定着软件技术的发展 利益决定着选择应用新技术