Summary
This note provides advice about customizing planning processes. The note attempts, in particular, to provide answers to the following questions:
- Which planning processes correspond to the old options 'Immediate automatic planning' and 'Automatic planning in the planning run'.
- When must events be taken into account from the CIF and when must they not be taken into account.
- How does the action 'Cover Dep./Stk Tr. Requirement immediately' differ from the action 'Start Product Heuristic Immediately'.
- What do I need to take into account when customizing the planning process 'Cover dependent requirements immediately'.
- Why is there a difference between creating and changing planned orders, but not between creating and changing purchase requisitions, for example.
- How is the reuse mode determined.
Planning process, Customizing, Documentation
Immediate automatic planning and automatic planning in the planning run
The 'immediate automatic planning' was replaced by the planning process 'Cover dependent requirements immediately'.The 'automatic planning in the planning run' was replaced by the planning process 'Planning in the planning run'.
With the Customizing for planning processes, two types of immediate planning are now possible.The system can either execute a heuristic directly after saving or the algorithm in Release 3.0 known as 'Immediate automatic planning' can be executed.We have therefore decided to rename the planning processes.
Details on the planning process 'Cover dependent requirements immediately' are provided later on in this note.
Customizing of the planning processes allows it to respond to changes transferred via the CIF interface to the APO system differently to changes originally made by the user or the system (for instance in the form of a heuristic) in APO.In each case, there is an event for a change in APO and one for a change transferred to the APO system via the CIF interface.
Certain objects are therefore usually changed in exactly one system, either in the APO system or in a R/3 System (or a CRM system or another OLTP System).Despite this, these objects are frequently replicated in other systems.The APO system therefore requires complete information on the development of requirements a product.The APO system needs the data for this from the sales orders.The sales orders themselves are managed in an R/3 or CRM system.However, they need to be replicated in the APO system.
Conversely, planned orders are only changed in the APO system, for example (this depends on which processes you want to support with APO).The change sent to the APO system as part of key completion of R/3 is exactly the same as the change that was already executed in APO itself.The change which is sent to the APO system by R/3 within the framework of the key completion is exactly the same change which was carried out before in the APO itself.This change does not need to be taken into account in the planning again. Set the events 'Create or Change Planned Order in OLTP System' and 'Create or Change a Dependent Requirement in OLTP System' in such a way that no action is to be carried out.
Your process may make provision for changing production orders in the OLTP system (in a R/3 system, for example). These changes can cause changed reservations. The planning in APO must react to this. The resources there must be adjusted accordingly. Set an action (for example, 'Create Planning File Entries') for the events 'Create or Change Production Order in OLTP System' and 'Create or Change a Dependent Reservation in OLTP'.
Try to avoid making simultaneous changes to the same objects in different systems.
The planning process 'Cover Dependent Requirements Immediately' ensures that the system reacts to the event 'Create or Change Dependent/Stock Transfer Reqmt in PP/DS' with the action 'Cover Dep./Stk. Tr. Requirement Immediately'.
If a planned order P changes (planned order is recreated or the quantity is changed or there is a new explosion for the planned order), the dependent requirements A for the planned order P are also changed, of course.The system then creates one or more receipt elements B1, B2, ... to cover the dependent requirement A. The action 'Cover dependent requirements immediately' has the following individual features:
The action 'Cover Dep./Stk. Tr. Requirement Immediately' has the following features:
- When calculating the quantities for the receipt elements the system takes into account the receipt elements Bn maximum and maximum lot size, fixed order quantity and rounding quantities.Other lot size parameters are ignored.
- If the receipt element Bn cannot be provided in time and the scheduling strategy allows forward scheduling, the planned order P can be shifted to the future in order to create a feasible production plan.This can also occur in several stages. In addition, you can only shift the user P to the future in the case of an overdue component if you use the action 'Cover Dep./Stk. Tr. Requirement Immediately'.
- The planning process 'Cover Dependent Requirements Immediately' also works for stock transfers if the stock transfer is scheduled via resources (Handling resource and/or transport resource).
- If, for example, a planned order P is changed interactively in the product view or product planning table, the system implements the required planning steps for the components immediately online so that the results are immediately visible from the component planning.
- The planning process 'Cover Dependent Requirements Immediately' is a precondition for the CTP check.All products that are supposed to participate in a CTP check must have the planning process 'Cover dependent requirements immediately'.
- You cannot call a heuristic to cover the dependent requirement.
- A planning process with the action 'Cover Dep./Stk. Tr. Requirement Immediately' can only react to a limited number of events. For details, see the next section.
A planning process that carries out the action 'Start Product Heuristic Immediately' has the following features:
- Using the heuristic, you can implement any lot size procedures.
- In the event of non-availability or late availability of a component, there is no change in the higher-level production level.The planned order with dependent requirements that can only be covered late cannot be automatically postponed.Where necessary this can be achieved by an additional call of one the heuristics SAP_PP_008 or SAP_PP_009.
- The heuristic is only started after the last change is saved.If changes are made online, the results of the heuristic are not immediately visible.
- The heuristic can react to any events, so it is not limited to changes of dependent requirements.
The action 'Cover Dep./Stk. Tr. Requirement Immediately' needs the connection between the planned order P and the resources Bn that resolve a dependent demand A of the planned order P. This connection is only known in the case of changes of P in APO. If one of the resources Bn is changed independently of P, the connection is not known. P cannot be changed.This applies to the change in resources Bn in APO and particularly to changes in the resources Bn that are transferred to APO by R/3 via CIF. If you call a heuristic when you make the changes to Bn (or set a planning file entry so that the heuristic is called later), this heuristic can destroy the planning result from the action 'Cover Dep./Stk. Tr. Requirement Immediately'. We therefore recommend that you only respond to the following events as part of the planning process 'Cover Dependent Requirements Immediately':
- Creation/change of dependent requirements or stock transfer requirements in the APO
- Change of a plan.Here we can re-explode the existing planned orders for the product.
- Changes of sales orders.Sales orders cannot be shifted to the future in any case.You should respond to a change in sales orders by immediately executing a heuristic.This heuristic is only executed when the sales order is saved, not during the ATP check.To adjust the resource elements of the sales order when the quantity of the sales order is reduced or when the sales order is postponed.When sales orders are created, or the number of sales orders increases or sales orders are shifted towards the present, the ATP check takes over the task of generating resources.The heuristic is therefore not suited for lot sizing.It should be based on the algorithm /SAPAPO/HEU_PLAN_DEFICITS, particularly in 'Reduce surpluses' (the corresponding check box is set in the heuristic Customizing).The heuristic SAP_PP_003 is set like this in the standard system.
- If there is a subassembly planning for the product of the dependent requirement A then you should also react to the event 'Create or change a planned independent requirement' by immediately calling a heuristic.
- If there is subassembly planning for the product of the dependent requirement A and if the consumption mode in the product master only allows backward consumption, then the system may react to the event 'Reduction of Planned Independent Requirement w. Consumption' by calling a heuristic immediately, however, this does not have to happen. If the SAP_PP_002 standard lot size heuristic reacts to the result, then the replenishment elements originally intended for covering the planned independent requirement are adjusted to the new dependent requirements.If there is no reaction to the event, the original replenishment elements remain.Since in the case of backward consumption the original replenishment element always appears before the new dependent requirement, this does not cause any constraint violation.If there is a reaction to the event, the plan is adapted better to the requirements.However, this has the disadvantage that the receipt elements are changed more frequently.If the receipt elements should not be changed if possible, use the SAP_PP_003 heuristic.
- If there is a subassembly planning for the product of the dependent requirement A, and if the consumption mode in the product master also allows forward consumption, a planned independent requirement that is behind the dependent requirement can be reduced through the consumption.An access element for this planned independent requirement may represent an excess coverage after the consumption.In this case, we would advise you to respond to the 'Reduction of planned independent requirement through allocation' event by immediately calling the SAP_PP_002 standard lot size heuristic.
In addition to defining the activity on an event, the Customizing of the planning processes also allows you to define the desired planning status.A popular scenario creates new planned orders so that they are always deallocated. Scheduling then occurs manually in the planning table.Once a planned order has been scheduled, it should either retain its planning status or be deallocated again if there are changes in the quantity. You can adjust this using the scheduling status settings for the event 'Change an In-House Production Order in PP/DS'. In exactly the same way, you can set planned orders to be created as soon as they are scheduled.
Purchase requisitions do not have a planning status.You therefore do not have to distinguish between creation and changing.
For every event, you can specify exactly which reuse mode is required.For changes to the quantities or dates of product requirements or product receipts, you can always obtain existing non-fixed product receipts (planned orders, purchase requisitions) as long as the quantity and date for the particular planned order still correspond to the requirement situation.
In the case of changes to plans (PPM, LZO), all planned orders must be exploded again unless the explosion of the planned order is frozen.The planned order is then re-exploded if the output of the planned order is fixed (and of course properly when the planned order is not fixed).If there is a change in the goods receipt processing time in the product master, the planned orders of the product must also be exploded again.
The maintenance dialog for the Customizing of the planning processes is generated.The generating tool only allows certain changes to the maintenance dialog.It was therefore not possible to fill the reuse mode automatically, even if only one entry was always allowed for each event.Use the permitted entry.
Find the Customizing for planning processes as follows:
Call transaction SPRO in your APO system.
Click on the SAP Reference IMG pushbutton
Open the following menu path:
SAP APO Implementation Guide
SAP Advanced Planner and Optimizer
Supply Chain Planning
Production Planning and Detailed Scheduling
Maintain Planning Processes
Header Data
| Release Status: | Released for Customer |
| Released on: | 07.05.2003 10:28:24 |
| Master Language: | German |
| Priority: | Recommendations/additional info |
| Category: | Consulting |
| Primary Component: | SCM-APO-PPS Production Planning and Detailed Scheduling |
| Secondary Components: | SCM-APO-PPS-SCF Scheduling Functions |
Affected Releases
|
Related Notes
| 557731 - Planning file entry + reuse mode (documentation) | |||
| 480292 - Multilevel ATP (documentation) | |||
| 441102 - Consulting notes in PP/DS | |||
| 426563 - CTP: Settings, system behavior and performance (docu) |
No comments:
Post a Comment