Product-Specific Planning Time Fence in Workdays

Source: SCM Server Help

Use
The system cannot create or delete any receipt elements using the procurement planning functions given above within the PP/DS planning time fence. If the system creates a new receipt for the product, it has to schedule the procurement proposal so that the availability date/time of the receipt is outside the planning time fence. Since existing receipts, whose availability date/time is in the PP/DS horizon, are firmed, the system may, at most, only re-explode the PPM plan, the iPPE process structure or the production data structure (PDS) for these receipts. Note that in the case of a procurement proposal with several output products, the system only takes into account the planning time fence of the product for which the system executes planning; the system does not consider the planning time fences of the other output products.


You use the PP/DS planning time fence if you have completed short and medium-term procurement planning for the product and want to prevent changes being made by automatic procurement planning. In the PP/DS planning time fence, you only want to execute sequence optimization on the resources for the existing in-house production orders. You can, however, manually create, change or delete receipts at any time in the PP/DS planning time fence.

No PP/DS functions and heuristics, other than the ones mentioned here, consider the PP/DS planning time fence:

* Action Cover dependent and stock transport requirements immediately if possible
* Action Cover dependent and stock transport requirements immediately
* Heuristics that execute procurement planning and can create or delete procurement proposals
* These heuristics include, for example, the standard heuristic SAP_PP_002 for planning standard lots.
* The standard heuristic SAP_PCM_DIS for dissolving production campaigns

The PP/DS planning time fence begins at the current time and continues for the given number of workdays into the future.

DependenciesThe system determines the workdays from the production calendar for the location. If you have not maintained any data in the production calendar, all days are workdays.

NoteYou can specify a time fence interactively in the product view. It may override the planning time fence in the following way:

* If the time fence is after the end of the PP/DS planning time fence, planning is fixed until the time fence.

* If the time fence is before the end of the PP/DS planning time fence, planning is fixed until the end of the planning time fence.

SNP and PPDS difference

Source: http://help.sap.com/saphelp_scm70/helpdata/EN/c1/147a375f0dbc7fe10000009b38f8cf/frameset.htm

 

You use Supply Network Planning (SNP) to create a feasible, medium to long-term production and distribution plan for critical products (products with long replenishment lead times or products that are produced on bottleneck resources). This plan should ensure that the required product quantities in your supply chain are available at the right place, at the right time, without overloading bottleneck resources for production and transportation. A key task of SNP involves determining the optimum sources of supply. Based on cost aspects, SNP decides where, when, and in which quantities products should be procured, produced, or transported in the supply chain. SNP plans according to periods and quantity. Order dates are exact to the day and detailed order sequences are not considered.

You use Production Planning and Detailed Scheduling (PP/DS) for detailed production planning; that is, for planning the lot sizes to be procured, for planning order dates to the second, and for planning order sequences on the production resources. Accordingly, in PP/DS you plan in-house production based on detailed, complete BOM (production process model plans, iPPE process structures, or PP/DS runtime objects) and on resources with a time-continuous capacity. 

For SNP planning, on the other hand, you use rough production process model plans (PPM plans). These contain only a section of the BOM with the critical components. You use resources with a period-related capacity, where the smallest period is a day. 

You separate the responsibilities for planning using the PP/DS horizon and the SNP production horizon. Planning within the PP/DS horizon is part of PP/DS planning and planning outside of the SNP production horizon is part of SNP planning, although the planning areas may also overlap. If, within short-term planning, you want to execute more detailed planning on receipts created by SNP, meaning that you want to plan them with detailed dates and a complete BOM, you must convert the SNP receipts into PP/DS receipts.  If the SNP receipts reach the PP/DS horizon, you convert the SNP receipts into PP/DS receipts.

SNP planning results primarily in stock transport orders. These orders are relevant to PP/DS if the stock transfer requirements concern production plants. 

SNP alone plans receipts and determines cost-effective sources of supply and lot sizes. You only use PP/DS to plan the receipts created by SNP in detail (that is, to complete the BOM) and to execute sequencing (for example, with setup time optimization). PP/DS copies the SNP source of supply decisions during conversion.

Horizon

If you want the PP/DS horizon and the SNP planning period to always follow each other without a gap, you only enter the SNP production horizon in the location product master, and no PP/DS horizon. The system automatically uses the SNP production horizon as the PP/DS horizon. This is required in particular if you define the SNP production horizon in calendar weeks or calendar months. 

Resource

If you want to consider the resource loads caused by PP/DS orders in SNP planning, and adjust the SNP planning accordingly, you must use mixed resources (single-mixed resources or multimixed resources) 

Source of Supply

Use a PP/DS PPM, for which you have defined a lot size interval, to create a corresponding SNP PPM with the same lot-size interval.

 Use a PP/DS PPM, which allows operations to be processed in different modes, to create an SNP PPM for each possible mode combination.

If you want SNP to specify the sources of supply during conversion, and you are planning with an automatically generated SNP PPM, the system automatically uses the basic PP/DS PPM.

Define the lot-size interval of a PP/DS PPM, for example, based on the process-related or technical creation restrictions. Use the PP/DS minimum lot size as the SNP minimum lot size. As maximum lot size, specify in the SNP PPM the total quantity that can be produced in one day. 

 

Find CTM Profiles from a particular Process Chain

Copy process chain technical name: BRAZIL_HYB_NET_UNC_SUM



Go to table: RSPCCHAIN, give process chain technical name, then copy all the Process Variants.

Then go to table: RSPCVARIANT, paste all the process variants, then use the "SCM_CTM01" as the Type, execute to get all CTM profiles

Planning Area Initialization Error

Symptom
You are executing the initialization of a planning area and you get the
error message "Invalid selection condition for selection of planning object".
 

Other terms
/SAPAPO/TS_PAREA_INITIALIZE, MATRES, Material, Resource, Planning area,
Planning version, /SAPAPO/TS103

Reason and Prerequisites
It is a side effect of note 1276922(which is a performance enhancement note.
 

Solution:

Implement the correction Note: 1280841

Restrictions of the Production Planning and Detailed Scheduling (PP/DS) optimizer

Source:https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=1155421

Summary

Symptom
Restrictions of the Production Planning and Detailed Scheduling (PP/DS) optimizer
Other terms
Optimizer, buckets, containers, block tolerances, order creation, warehouse
Reason and Prerequisites
You are using the Production Planning and Detailed Scheduling (PP/DS) optimizer.
Solution

• The PP/DS optimizer tries to improve the solution gradually but there is no guarantee that it will find the optimum solution. In addition, the gap in relation to the optimum is not definite.

• For releases earlier than SCM 7.0, the following applies: The optimizer does not create any new orders and does not delete any existing orders. It does not create new orders and does not change the production process model (PPM) or lot sizes. Only the dates of the operations are changed. Note 1155421 contains restrictions regarding the creation of orders as of Release SCM 7.00.

• For releases earlier than SCM 7.0, the following applies: A finite container planning is not supported. Note 1171154 contains restrictions regarding finite container resource planning as of Release SCM 7.00.

• The deactivation of the "Self Reference" indicator from resource networks is ignored by the optimization.  Linking a resource to itself is always allowed for the optimization.

• During block planning, the blocks are taken into account but the block tolerances are not used.

• The optimizer starts with the pegging of the liveCache. Without this pegging, material bases and delays cannot be calculated. Therefore, scenarios without pegging; for example, when you use the rapid prototype matrix, are not supported without the optimizer creating the pegging.

• No bucket resources are supported. Operations that use a bucket resource are fixed for the optimizer.

• For releases earlier than SCM 5.1, the following applies: Bi-finite planning is not supported. However, it is useful to use the PP/DS optimizer for a finite planning after a bi-finite forecast.

• On infinite single-activity resources with setup matrix, the optimization cannot plan the setup activities as sequence-dependent activities. Instead, the average setup times are used for planning.

• For releases earlier than SCM 7.02, the following applies: With conti-IO nodes, the material is always allocated to all recipients in parallel. Acceptance with sequencing so that first order A1 and then order A2 continuously accepts from a chronologically overlapping manufacturing order A (that is, A does not end before A2), is not supported. In this case, a finite capacity modeling with discrete IO nodes is to be avoided. Note 1533835 contains information about the functions in relation to conti-IO nodes as of Release SCM 7.02.

• The optimization of the order lead time is not part of the optimization goal. Using compact scheduling (available as of Release SCM 5.0) reduces the order lead time in the postprocessing step.

• The planned delivery time is only taken into account for purchase requisitions.  If a component is missing and if no receipt is planned as yet, the planned delivery time from the product master is not used.

• Scheduling agreements are not rescheduled; instead, they are treated as fixed (see Note 666725).

• Fixed operations retain their planning/deallocation status.

• The optimizer does not support days' supplies. Safety stocks are supported only if they are available as additional requirements.

• The "Deallocation with delay" function and the function for deallocation in case of validity violations cannot be linked with campaign planning.

• The "Deallocation with delay" function cannot be linked with container resources planning.

• The function for taking into account the exact continuous material flow can be linked with campaign planning or time decomposition.

• During the campaign optimization with maximum campaign length, the processed campaigns must be completely visible for the optimizer to be able to determine the length. The first orders processed must not be deleted from the system; if they are, the maximum length for the campaign in question may be exceeded.

• The campaign optimization is based on the bottleneck resources. There must be no direct or indirect time link (in the form of constraints or material dependencies) between the operations or orders that are planned on the bottleneck resources. In particular, bottleneck resources may be used only once in the production flow.

• The explanation log cannot provide the best explanation for all modellings (see Note 840883).

• Note 765320 describes compatibility restrictions regarding previous versions.

Header Data

Release Status:	Released for Customer
Released on:	23.12.2010  15:57:59
Master Language:	German
Priority:	Recommendations/additional info
Category:	Consulting
Primary Component:	SCM-APO-OPT-PPS Production Planning and Detailed Scheduling

Affected Releases

Software Component Release From Release To Release And subsequent SCM 400 400 400   SCM 410 410 410   SCM 415 415 415   SCM 500 500 500   SCM 510 510 510   SCM 700 700 700   SCM 701 701 701   SCM 702 702 702 X

Related Notes

	1533835 - Continuous material flow in PP/DS optimization
	1406424 - Implementation recommendations for APO 7.0 PP/DS
	1171154 - Planning of container resources with the PP/DS Optimizer
	1155421 - Restrictions for order creation
	840883 - Restrictions of the explanation log

A framework for the development of IT for effective SCM

Source: An Information System Architectural Framework for Enterprise Application Integration for Enterprise Application Integration. By André Vasconcelos and etc