PP:Planning Strategy

PP:Planning Strategy

 (2012-03-28 23:30:35)

转载

标签: 

planning

 

strategy

 

杂谈

分类: SAPPP

Planning Strategy

http://help.sap.com/saphelp_46c/helpdata/EN/cb/7f936943b711d189410000e829fbbd/frameset.htm

Selection priority for planning strategy is:

First material, second MRP group and last plant parameters. E.g. System first checks for material, if strategy is defined there, that is used, if it's not maintained there, then it checks if it's defined in MRP group.

That is the same for all MRP parameters, not only strategy.

If you wanna test how it works, try this:

1. create an mrp group, say 0001, and assign strategy group "40 - planning with final assembly" in the MRP group parameters.

2. create a material, say product1 and define planning strategy as "20 - make to order". And also enter the MRP group 0001 in material master.

3. Create a sales order and create an order item for product1.

4. In the sales order header, go to the Procurement tab. There, you will see the requirement type for product1, which is automatically selected by system according to the planning strategy it uses. That requirement type should be "KE" if strategy 20 is selected, or it should be "KSL" if strategy 40 is selected by system.

5. In my test, system selected KE requirement type, which indicates that system used strategy 20, and which I have entered in the material master. It didn't select KSL, which indicates that system uses strategy 40, which is entered in the mrp group. Finally, this test shows that system takes the planning strategy in material master (if it's entered), not the strategy in MRP group.

I think you can now make another test how system uses MRP group's planning strategy. (hint: Delete planing strategy from the material master and repeat the previous test steps. That would end up using strategy 40, which is selected using the MRP group parameters.)

计划策略(Planning Strategies)是对业务中如何计划产出数量和日期的抽象概括。本文参考LO210 Production Planning,记下对各种计划策略的认识。

面向库存生产(Make-to-Stock)的一个显著特点是,产品跟销售订单无关,同一个产品(物料)可以销售给非特定客户特定订单。因此,产品是先产出入库,销售的是库存里的产品。另一特点与CO模块有关。

MTS策略如下:

  • Make-to-stock production (anonymous),10
  • Make-to-stock production/gross reqmts planning,11
  • Production by lots,30
  • Planning with final assembly,40
  • Planning at assembly level,70
  • Planning at phantom assembly level,59

一、Make-to-stock production,10

  • 行业:重复性生产,如Consumer Packaged Goods(消费性包装产品)。
  • 特点:不考虑销售订单,减少对PIR的影响,使需求过程更为平滑。
  • Consumption:N/A
  • Reduce:Goods issue for delivery
  • 可用性检查:ATP Logic
  • 消耗模式:FIFO
  • 主数据:Availability Check - 02 (w/o RLT)
  • IMG:
    • NO MRP - 1/2
    • PIR reduction - X

二、Make-to-stock production/gross reqmts planning,11

  • 行业:大规模生产,如重工业中的钢铁、水泥制造,生产不能停顿。
  • 特点:既不考虑销售订单,也不考虑库存,只强调生产。
  • Consumption:N/A
  • Reduce:Goods receipt
  • 可用性检查:ATP Logic
  • 消耗模式:FIFO
  • 主数据:
    • Mixed MRP - 2 
    • Availability Check - 02 (w/o RLT)
  • IMG:
    • NO MRP - 1/2 

三、Production by lots,30

  • 行业:Contract-based,为主要客户生产,偶尔也从库存小量销售,如汽车备件供应厂商。
  • 特点:不做PIR,需求由销售订单产生。为此要求预先知道销售订单的情况,考虑RLT(补货提前期)。
  • Consumption:N/A
  • Reduce:Goods issue for delivery reduce open sales order
  • 可用性检查:ATP Logic
  • 消耗模式:FIFO
  • 主数据:
    • Availability Check - 01 (with RLT) 

四、Planning with final assembly,40

  • 行业:最常用
  • 特点:客户需求消耗PIR,能迅速反应客户需求。
  • Consumption:销售订单创建
  • Reduce:Goods issue for delivery
  • 可用性检查:ATP Logic
  • 消耗模式:配置
  • 主数据:
    • 消耗模式和时期 

五、Planning at assembly level,70

  • 行业:装配件(Assembly)的需求预测较方便
  • 特点:计划在装配件上
  • Consumption:成品的计划订单、生产订单所产生的相关需求或预留
  • Reduce:Goods issue for production order
  • 可用性检查:ATP Logic
  • 消耗模式:配置
  • 主数据:
    • Mixed MRP - 1 
    • 消耗模式和时期
    • 独立/集中 - 2

六、Planning at phantom assembly level,59

  • 行业:同上
  • 特点:虚拟件,虚拟件的组件可用反冲
  • Consumption:成品的计划订单、生产订单所产生的相关需求或预留
  • Reduce:虚拟件完全发料
  • 可用性检查:ATP Logic
  • 消耗模式:配置
  • 主数据:
    • Mixed MRP - 1 
    • 消耗模式和时期
    • 独立/集中 - 2

Customizing T-Code:

Path: IMG\Sales and Distribution\Basic Functions\Availability Check and Transfer of Requirements\Transfer of Requirements\Determination of Requirement type using Transaction.

OVZI - Assignment of Requirment ytpes to transcation

OPPS - Define Strategy

OPPU - Strategy Group for MRP Group

POOT - Stategy Groups

分享:

 

  • 0
    点赞
  • 2
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
隐式声明的虚拟函数 "apollo::planning::parkandgoscenario::~parkandgoscenario" 是指在派生类的析构函数中调用基类的析构函数,并且该基类的析构函数是虚函数。 在C++中,当一个类的析构函数被声明为虚函数时,它将变为虚拟析构函数。虚拟析构函数允许通过指向派生类对象的基类指针来正确地删除派生类对象,而不会导致对象只调用基类的析构函数而不调用派生类的析构函数。 在"apollo::planning::parkandgoscenario::~parkandgoscenario"这个函数中,它是一个析构函数,并且被隐式声明为虚函数。这意味着在派生类的析构函数中,应该通过在基类名称前加上"~"来调用基类的虚拟析构函数,以确保正确地释放派生类的资源。 例如,在一个名为"ApolloParkAndGoScenario"的派生类的析构函数中,可以这样调用基类的析构函数: apollo::planning::ApolloParkAndGoScenario::~ApolloParkAndGoScenario() { // perform necessary cleanup in the derived class // ... // call the base class virtual destructor apollo::planning::parkandgoscenario::~parkandgoscenario(); } 通过这样的调用,可以确保在删除派生类对象时,递归地调用每个基类的析构函数,以正确地释放每个类的资源。 总之,隐式声明的虚拟函数 "apollo::planning::parkandgoscenario::~parkandgoscenario" 是一个析构函数,并且通过在派生类的析构函数中调用基类的析构函数来确保正确地释放派生类的资源。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值