strategies

来源:互联网 发布:seo上海 编辑:程序博客网 时间:2024/05/17 08:57

Overview 概览

The overall goal of production planning—and the use of planning strategies—is to better serve your customers by reducing:

Storage costs

Replenishment lead times

生产计划以及使用计划策略的总的目的是为了更好地为客户减少库存成本和补货提前期。

To reach that goal you should group your materials according to their individual needs. You should create as few groups as possible (for better transparency on the shop floor) and as many as necessary (for flexibility). The following examples may provide the criteria to group:

为了达到这个目的,你需要根据物料各自的需求来组织你的物料。尽可能的使用少量的组(在生产控制中有更好的透明性)而且有根据需要尽可能的使用组(为了灵活性)。下面的例子可以作为分组的标准:

Cheap materials, which could be planned-consumption based.

廉价物料,可以有作基于消耗计划

It is more important to have these materials permanently available than to run out of them. The effort to plan these materials should be minimal.

保证这些物料不断料是很重要的,不要等到用完它们(再买)。计划这些物料的花费是最小的。

Expensive materials, or those with long replenishment lead times, which need a more sophisticated planning approach.

昂贵的物料或需要比较长的提前期的物料,这些物料需要更完善的计划方法。

Consider the following questions when grouping the materials:

当你分组物料时,需要考虑以下问题:

Who is responsible for the production plan?

由谁来负责作生产计划?

Are the materials produced before or after the arrival of sales orders?

销售订单在物料生产之前还是生产之后到达?

How should the actual stock level affect production?

实际库存怎么影响生产?

Do you need a consumption of planned quantities? When should this consumption take place?

你需要一个计划的消耗数量吗?什么时候应该有消耗数量?

Consumption of planned production quantities (planned independent requirements) allows for a permanent reevaluation of planned quantities based on actual sales orders.

计划生产数量的消耗(计划独立需求)基于实际的销售订单。

On what level in the product structure does your planning take place (finished product vs. subassembly)

你的计划发生在你的产品结构的哪一层?(成品还是组装层)

Production planning usually takes place only on one level of your product structure. For example, you either perform production planning (“forecast” of demand) on the finished product level or on the subassembly level.

生产计划通常发生在你的产品结构中其中一层。例如,要么你在你的成品层制定的生产计划(“预测”的需求),要么在组装层制定计划。

Disclaimer 声明

All scheduling information in the sample scenarios (stock/requirements lists), including the screens, is subject to your scheduling settings. The actual results depend on your configuration and the setup of your master data. The data is intended to give you typical examples.

在例子情形中的所有计划信息(库存/需求清单),包括屏幕,都是和你的计划设置有关的,实际的结果根据你的配置和你的主数据的设置。这里的数据只是一种典型的例子。

Questions 问题

To select the most appropriate planning strategies, answer the questions for each material group (remember to use different strategies for different purposes). To make this guidebook easier to use, we have structured similar strategy groups in such a way as to minimize the time you spend reading the entire document.

为了选择最合适的计划策略,回答每一个物料群组的问题(记住使用不同的策略是为了不同的目的)。为了使本手册更易使用,我们组织了一个比较小的策略组,使用这种方法来加速你阅读本书的速度。

Planning Level 计划层

On which of the following levels do you want to plan component procurement:

在以下层次中你需要计划你的组件获取:

Finished product level 成品层

Subassembly or component level 组装或组件层

Characteristics or characteristics value level 特性或特性值层

Finished Product Level 成品层

Finished product level planning is used when there is a stable and predictable demand pattern at the finished product level (the material sold in sales orders).

当在成品层上有一个稳定的、可预见的需求模式时,使用成品层计划(物料使用销售订单销售)。

Subassembly or Component Level 组装或组件层

Planning on the component level is used when there is a stable and predictable demand pattern at component or subassembly level (the material used in production orders).

当在组件或组装层上有一个稳定的、可预见的需求模式时,就使用组装或组件层(物料使用在生产订单中)。

For the following reasons, it is often more convenient to plan at the component, rather than on the finished product, level:

具有以下原因时,使用组件层比使用成品层计划更加方便:

The demand pattern at finished product may be unstable

在成品层的产品需求模式可能不稳定

Many similar variants of finished products require the same component or subassembly

很少有成品需要用相同的组件或组装

Finished products may be consumption based

成品可能是基于消耗的

Characteristics or Characteristics Value Level 特性或特性值层

Planning on the characteristics (value) level is used when, for each configurable product, you have a stable and predictable demand patterns at characteristics (value). The use of characteristics requires the use of the variant configurator (see chapter 5, Characteristics Planning). Characteristics selection is translated into component selection. Therefore, when planning at characteristics (value) level, you are planning, for example, the characteristic “blue” paint. This characteristic results in the selection of the component “blue paint.” A more complex example is to plan the characteristic “stick shift,” which results in the selection of components related to that characteristic’s value.

对于可配置产品,按照特性值具有稳定的、可预测需求模式时,使用特性或特性值计划。特性的使用需要变式配置(见第5章,特性计划)。特性选择被传输到组件选择。因此,当计划在特性(值)层时,你要计划,例如,特性“蓝色”油漆。组件就按照特性的治选择“蓝色”的油漆。更复杂的例子是计划特性“辊轴”,这种情况下组件的选择要依赖特性的值。

Production Level 产品层

Would you like to produce the planned product in stock before a sales order is entered?

销售订单到来之前你的计划产品是否在库存?

If “Yes,” use a make-to-stock strategy (for example, 10, 11, 40).

如果“是”,使用按库存生产策略(MTS: Make-To-Stock)(例如:101140)。

If “No,” use either a make-to-order or a strategy without final assembly (for example, 30, 52, 63, 20, 25,26, 54, 55, 56, 65, 89)

如果“不是”,要么是用按单生产(MTO: Make-To-Order)策略或无最终组装的策略(例如:3052632025265455566589

Procuring Components 获取组件

Would you like to procure the components before the entry of sales orders?

在创建销售订单之前你已经获取组件了吗?

PS. MMMRP中,procure/procuring/procurement均是不同词性的“获取”,即物料的取得方式,可以是外部采购,也可以是内部生产得到。

To procure or produce the entire product (the part that you sell) in stock before sales orders can be placed, you should use a make-to-stock planning strategy (40, 10, 11). The components are automatically procured before the sales order entry.

在销售订单创建以前,为了把完整的产品获取或生产在库存中(你也出售部件),你应该使用对库存生产(make-to-stock)的计划策略(401011)。这样组件在销售订单创建以前就自动获取了。

To procure or produce only subassemblies—essentially planning on a finished product level—you will most likely use strategies without final assembly (for example, 50, 52, 55, 60, 63 or 65).

获取或生产仅在组装层——实际的计划在成品层——你最可能使用的策略是“无最终组装”的策略(例如:5052556063、或65

To procure or produce subassemblies based on plans, which are independent of finished products, you will most likely use strategies for the planning of components (70 or 59).

获取或生产在组装层基于成品的独立计划执行,最可能的策略是组件计划的策略(70/59)。

Responsibility for Production 生产职责

Who is responsible for the production quantities?

谁来负责产品数量?

If your production department is responsible for production quantities and the resulting stock levels (and they do not want to rely on sales forecast for the finished products), you can use strategies for planning components and de-couple the two departments.

如果你的生产部门负责产品数量和库存水平(他们不依赖成品的销售预测),你可以使用计划策略来分散到两个部门中。

Influence of Stock 库存影响

Should the stock level influence the production quantities?

库存水平影响生产数量吗?

Strategy 11 allows for production that relies only on the planned quantities from Demand Management (without netting stock quantities). This strategy is particularly useful if you want to have a determined production plan (for example, if you have to deal with a seasonal demand pattern but want to have constant production).

策略11(Make-to-stock production/gross requirements planning)依赖需求管理中的计划数量来生产(没有净库存数量)。如果你需要一个确定的生产计划时,这个策略是比较有用的(例如:如果你需要处理季节性需求模式但又需要一个恒定的产量时)。

Consumption Strategies and Logic

消耗的策略及逻辑

Purpose 目的

In the consumption process, the system compares planned independent requirement quantities and dates with actual customer requirements. The consumption process is defined for every planning strategy in Customizing for Demand Management by combining a requirements type from Demand Management and a requirements type from sales order management. This step means that the requirements type entered when maintaining planned independent requirements is compared to the customer requirements type specified in Customizing.

在消耗处理中,系统用计划独立需求的数量及日期与实际的客户需求作比较。在后台定制作业中的每一个计划策略中定义了消耗策略的处理流程,需求管理中的需求类型和销售订单中的需求类型一起决定消耗策略。维护在计划独立需求中的需求类型和在定制作业中为客户指定的客户需求类型要做比较。

Prerequisites 准备

You must maintain the consumption mode in the Material Master Record (MRP) screen or in Customizing for Demand Management. The consumption mode determines whether consumption is to be carried out as backward or forward consumption, or whether both consumption types are allowed. In backward consumption, the system looks for the planned independent requirement quantity that exists directly before the sales order.In forward consumption, the system looks for the planned independent requirement quantity that exists directly after the sales order. You also need to maintain the consumption period in the MRP screen or in Customizing for Demand Management. The consumption period (forward or backward) is specified in workdays and is valid from the current date. Sales orders, material reservations, and dependent requirements then consume the planned independent requirement quantities that lie within the consumption period and after (for forward consumption) or before (for backward consumption) the requirements date.

你需要在物料主记录的MRP视图中维护物料的消耗模式,或在需求管理的后台定制中维护。消耗模式决定消耗是向后消耗还是向前消耗,还是向后向前都允许。在向后消耗中,系统寻找在销售订单以前存在的计划独立需求数量进行消耗。在向前消耗中,系统寻找在销售订单之后存在的计划独立需求数量进行消耗。你还需要在物料主数据中的MRP视图,或需求管理的后台定制作业中维护消耗的期间。消耗期间(向前或向后)指定从当前日期起的有效工作天数。销售订单、物料预留和相关需求都会消耗在需求日期之后(向前消耗)或在需求日期之前(向后消耗)的位于消耗期间内的计划独立需求。Process Flow

处理流程

The customer requirement consumes the planned independent requirement quantity that either directly precedes or follows it. If the planned independent requirement quantity directly preceding the customer requirements does not cover the customer’s requirement, then the system looks for the next closest planned independent requirements in the future or past.

客户需求消耗计划独立需求的数量。如果计划独立需求的数量向前消耗时不能满足客户的需求,系统会寻找最近的一个计划独立需求去消耗。

During this process, the system refers to the consumption periods maintained in the material master or in Customizing for Demand Management (see above). The consumption periods determine the intervals (for backward or forward consumption) within which customer requirements consume planned independent requirements. Customer requirements that lie outside the consumption period are not consumed.

在这个处理过程中,系统会参考维护在物料主数据,或在需求管理的定制作业中的消耗期间。消耗期间决定客户需求消耗计划独立需求的范围。位于消耗期间之外的客户需求不被消耗。

If no consumption periods have been maintained, you can only consume requirements that are planned on the same day. The allocation of customer requirements to planned independent requirements is carried out dynamic. This step means that if sales orders or planning is rescheduled, the allocation is deleted and redefined.

如果没有维护消耗期间,你只能消耗那些计划在同一天的需求。客户需求到计划独立需求的分配是动态的。这就意味着如果销售订单或计划被重新计划了,分配会被删除并重新分配。

Determining the Requirements Type

确定需求类型

A requirements type contains the control parameters to plan and consume planned independent requirements and customer requirements. Different requirements types or combinations of requirements types from planned independent requirements and customer requirements are defined for each planning strategy.

需求类型包含计划和消耗计划独立需求和客户需求的控制参数。计划独立需求和客户需求中的不同的需求类型或需求类型组合被定一在每一个计划策略中。

You do not have to define any new strategies. SAP’s standard delivery provides you with all strategies described in this document. There are only a few cases where you should define your own planning strategies.

你不需要定义任何新的策略,SAP的标准版本提供了所有在本书中描述的策略。只有在极少的情况下,你可能需要定义你自己的计划策略。

Activities 作业

If you want the system to determine the requirements type when automatically creating the planned independent requirements, enter strategy groups for the corresponding materials in the material master record. If the strategy group allows a number of planning strategies, the system proposes the requirements type from the main strategy. You can overwrite this strategy in the sales order using one of the alternative requirements types in the Overview ->Procurement screen.

在你自动创建计划独立需求,在物料主数据中输入相关物料的策略组时,如果你要求系统去决定需求类型。如果策略组允许几种计划策略,系统会建议主策略中的需求类型。你可以在销售订单中使用替代需求类型去覆盖这个策略,替代需求类型在Overview ->Procurement页中。

Assigning a Planning Strategy via the MRP Group

通过MRP组分配计划策略

You can also assign the planning strategy with the MRP group.

你也可以通过MRP组来分配计划策略。。

1. Assign the strategy group to the MRP group (in Customizing for Demand Management, choose Planned Independent Requirements ->Planning Strategy ->Assign strategy group to MRP group).

分配策略组到MRP (TCODE: OPPU)

The MRP group is assigned to the material in the material master record.

在物料主数据中分配MRP组到物料。

2. 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.

如果你的物料主数据中的策略组或MRP组中包含了正确的策略,在需求管理中你就不需要再输入需求类型了。

The system determines the valid requirements type with the strategy group from the material master record and automatically proposes this type when creating independent requirements (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.

系统使用物料主数据中的策略组来确定有效的需求类型,并且在你创建独立需求(或客户需求)自动建议这个需求类型。如果策略组包含多个策略组,系统使用主策略的需求类型。如果需要你可应从替代策略中使用需求类型来覆盖建议的需求类型。

In order to find the correct requirements type in demand management and in sales order management, you have to:

为了使需求管理和销售订单能正确地找到需求类型,你必须:

Assign the strategy groups to the MRP groups, and

MRP组分配一个策略组,并且

Assign the MRP groups to every material to be planned in the material master record.

在物料主数据中,把这个MRP组分配给每一个要计划的物料。

PS. 这个过程是在作需求管理或销售订单中,策略组由关联的MRP组带出来,需求类型则由策略组带出来Or 或者

Enter the strategy group directly in the material master record of the material to be planned

在要计划的物料的物料主数据中,直接一个策略组。

PS. 即策略组乃是必须的。

Maintaining and Defining Strategies and Strategy Groups

维护和定义策略及策略组

The planning strategies represent the business procedures to plan and produce a material. In the system, the planning strategies are recorded in Customizing by a combination of requirements types from Demands and Sales Order Management. This combination determines either the consumption of planned independent requirements by customer requirements or how the availability check is to be carried out.

计划策略表示了计划和生产物料的业务处理过程。在系统中,计划策略由需求和销售订单管理联合在后台作业中定义。这种联合决定了由客户需求消耗的计划独立需求或有效性检查是怎么执行的。

The planning strategies are maintained in Customizing for Demand Management. Here, the requirements types are combined for the planning strategy. Technically speaking, the requirements types are texts that represent the planning strategy in the application (Demand Management, Sales and Distribution). The requirements type is controlled by another key—the requirements class. The requirements class contains all the control parameters required for Demand Management and Sales and Distribution. To maintain the planning strategy, you only have to combine the necessary requirements types. The corresponding requirements class is automatically assigned with all the accompanying control parameters.

计划策略维护在需求管理的后台定制作业中。在这里,需求类型被包含在计划策略中。从技术上讲,需求类型就是表示计划策略在(需求管理、销售与分销)应用中的一种文本。需求类型由另外一个关键字控制 需求类(Requuirements class)。需求类包含所有的为需求管理和销售与分销所需的控制参数。要维护计划策略,你只需要包含所需要的需求类型即可。相关的需求类会自动分配它所包含的控制参数。

By assigning a planning strategy to a particular material, the system determines the correct requirements type (and all the control parameters of the requirements class) when creating planned independent requirements or sales orders. To set up this mechanism, certain objects and assignments must be set up in the system. The standard system is set up so that you can perform all standard processes described in this guidebook.

通过分配计划策略到特定的物料,当创建计划独立需求或销售订单时,系统决定正确的需求类型(和所有需求类的控制参数)。为了配置这种机制,特定对象和分配必须在系统中设置。在本书中介绍了所有的标准处理流程。

The primary object for setup is the planning strategy (in Customizing for Demand Management). This strategy is defined by a requirements type from Demand Management, Sales Order Management or a logical combination of both requirements types. These requirements types determine, for example, how the consumption of planned independent requirements by customer requirements is carried out and whether the availability check according to the ATP logic also occurs.

配置的主对象是(在需求管理的后台定制中的)计划策略。策略由需求管理、销售订单管理或两者的逻辑组合的需求类型定义。需求类型决定客户需求怎么消耗计划独立需求和是否根据ATP逻辑的有效性检查。

The following assignments have to exist to assign the requirements classes to planned independent requirements and sales orders:

以下分配对计划独立需求和销售订单一定存在已分配的需求类:

Planning strategy to a strategy group (in Customizing for Demand Management) so that a material can be planned with various planning strategies.

You can maintain one main strategy and up to six alternative strategies.

(在需求管理的后台定制中)分配计划策略到策略组,以便物料能够有几个计划策略。你可以维护一个主策略和六个替代策略。

Strategy group to the material (in the material master record), so that the system can automatically determine the correct requirements type.

(在物料主数据中)分配策略组到物料,以便系统可以自动决定正确的需求类型。

A planning strategy can also be assigned with the MRP group. Assign the strategy group in Customizing for Demand Management to the MRP group. In this case, the MRP group is assigned to the material in the material master record.

一个计划策略也可以分配给一个MRP组。在需求管理的后台定制中分配策略组到MRP组。在这种情况下MRP组在物料主数据中被分配给物料。

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)策略,需求类型是KEKL  [策略20KE)是缺省的]

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)策略,需求类型是KLKE  [策略30KL)是缺省的]

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)策略,需求类型是KLKSV [策略30KL)是缺省的]

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的组装处理