PP/DS for SAP S/4HANA
Reason and Prerequisites When Production Planning and Detailed Scheduling for SAP S/4HANA 1610 was released, some restrictions still applied to the productive use of certain functions in the area of Production Planning and Detailed Scheduling (PP/DS). SAP wishes to inform customers of these restrictions and provide some recommendations here.
Solution Production Planning and Detailed Scheduling for SAP S/4HANA
Production Planning and Detailed Scheduling (PP/DS) for SAP S/4HANA is not a legal successor of the PP/DS component from the SAP SCM Server. Data migration and customer code migration from PP/DS component from the SAP SCM Server is not supported by the standard solution. Basic manual settings needed to set up PP/DS
Set up integrated liveCache and the relevant operational jobs by following the SAP S/4HANA installation and operations guide. Also refer SAP note 2407589 (Manual installation of liveCache for S/4HANA). Run the mandatory reports SLCA_INIT_FOLLOW_UP, /SAPAPO/OM_CREATE_LC_TABLES. You can now use transaction LCA03 to check the functionality of the system in an SAP-liveCache-relevant business client. Activate Activate the flag for Advanced Advanced Planning Planning in customizing. customizing. To activate activate PP/DS PP/DS for SAP S/4HANA in customizing, select Advanced Planning > Basic Settings > Activate Advanced Planning and Scheduling Set up the Model '000' and Version '000' manually and check whether they exist. The PP/DS Horizon can only be maintained at the level of planning versions in SAP S/4HANA. Set the application indicator for ND-APO (New Dimension Plug-In APO) to active. (Transaction BF11). Verify if ND-APO and NDI (New Dimension Integration) is checked. Set up the CIF customizing in customizing by choosing Basic Settings for Creating the System Landscape, and by including SAP S/4HANA with system type SAP_APO and release 713 so that an Integration model pointing to itself (own system and client) can be created and logical system and queue types could be maintained. Set up CIF user parameters. Register the CIF queue (Transaction SMQR). There is no need for maintaining distribution definition or publication types as the PP/DS is part of SAP S/4HANA. Enable number range in PP/DS for SAP S/4HANA in PP/DS global parameters and values (Transaction /SAPAPO/RRP_CUST1). In addition, maintain number
ranges for production campaigns and interchangeability groups depending on the usage of these functions. Check if pre-delivered ATP categories exist. Refer S/4HANA Administration Guide for Implementation and SAP Note 2272406 for more information.
Setup and activation of Locations
Create the integration model including the locations (Plants, MRP areas, Vendors) in which PP/DS should be used using integration model maintenance and activate it. In case your business processes have same location names for different location types and needs integration with PP/DS for S/4HANA, implement BAdI SMOD_APOCF001.
Setup and activation of Materials
SCM Product Master is integrated into the SAP S/4HANA Product Master with CDS Redirects on material master. For more information, refer SAP note 2342043. The SCM Product master is read-only for active version and can be used for maintaining simulative parameters in simulation versions.
Local material creation in PP/DS is not supported. Activate PP/DS Materials by selecting the “Advanced Planning” checkbox in the "Advanced Planning" tab of the material master. Freely defined attribute of Product Master is not supported. SCM Extensibility Feature for SCM Related Fields in Product Master and data mapping, refer SAP Note 2393581 for further information.
Materials that were created in SAP S/4HANA releases prior to 1610 have to be enabled for usage in PP/DS in SAP S/4HANA. To do so run report PRD_SCM_GUID_CONVERSION. For more information, check the report documentation Setup and activation of Resources
Local resource creation in PP/DS is not supported. Enable Target-System independent Settings in CIF (Transaction CFC9) to enable "APO Resources" in Work Center Capacity: header tab. This is required to send to PP/DS different resource types and resource categories. This would be required to transfer handling unit, calendar resources etc. Change transfer mode “No Change Transfer” is not supported in PP/DS for SAP S/4HANA in Target-System independent Settings in CIF (Transaction CFC9). In case “No Change Transfer” is maintained, the value gets defaulted to ‘N’ (Change Transfer for Pl.-Vers-Independent Resource and PV 000) Setup the Capacity Versions for integrating external capacities from ERP in customizing by selecting Advanced Planning > Master Data > Resource >
Specify Capacity Variants . We recommend that you use external capacities as much as possible. Activate PP/DS work centers by selecting the “Advanced planning” checkbox
Setup and activation of Source of Supply
In-house production:
Use transaction CURTOADV_CREATE (in the SAP Easy Access Menu, select Logistics > Master Data > PDS for Advanced Planning ) to enable PDS transfer to PP/DS For automatic change transfer of PDS on change implement BAdI CUSLNTRTO_ADDIN
External Procurement:
Create the integration model for scheduling agreements, contracts, and purchasing info records which needs to be integrated to PP/DS should be used using integration model maintenance and activate it
Activation of Orders and Batches
By default, all material dependent orders and batches are integrated into liveCache for all PP/DS-relevant materials. The settings are controlled in customizing by selecting Advanced Planning > Basic Settings > Settings for Data Transfer Complete retransfer of material dependent orders can be achieved with the report /SAPAPO/PPDS_DELTA_ORD_TRANS Automatic Creation of Transportation Lanes
Transportation lanes between plant and MRP area, between plants or between plants and distribution centers are not created automatically. If needed, transportation lanes should be maintained manually. Forecast Consumption
Consumption period is calculated in calendar days in PP/DS for SAP S/4HANA and in working days in SAP S/4HANA Maintain the Category Group in customizing by selecting Advanced Planning > Maintain Category Groups Check Mode is not displayed in PP/DS product master and cannot be changed. The corresponding strategy group of the requirement class has to be defined in ERP material master. In PP/DS, the Requirement Class has to be defined as Check Mode (same identifier) (maintenance view /SAPAPO/V_ATP06)
The Assignment mode maintained in Check mode and the allocation indicator maintained in the Requirement Class should be the same for consistency in the system’s behavior Trigger the Forecast consumption using Report /SAPAPO/CSP_CORRECT_FCST in case in the Product view the Elements tab result is different from that of the Forecast tab The following consumption modes are supported by PP/DS for SAP S/4HANA o 1 - Backward Consumption Only o 2 - Backward/Forward Consumption o 3 - Forward Consumption Only
MRP Live
All downstream materials should be Advanced Planning-relevant if planned together with MRP Live. This means the data modelling should be such that once a material at one BOM level is PP/DS-relevant (Advanced Planning-relevant), then the materials above that BOM level should also PP/DS-relevant (Advanced Planning-relevant). This is to ensure that depended demands are also in liveCache or PP/DS. Low-level code calculation happens for all materials, whether those are relevant to Advanced Planning or not, in SAP S/4HANA through MRP Live. Therefore, any specific process that uses a different low-level code calculation needs to be planned independently, such as Planning with Planning Package, Interchangeability, Planning with Co-Products. Production Scheduling Board (Fiori App)
Campaign planning and block planning are not supported. Editing Resource master data together with the same sim-session as that of the Production Scheduling Board is not supported. Creation of Downtimes and Fixing intervals from Production Scheduling Board is not supported. Time Profile setting options ‘Segments’ and ‘Hide Non -WT’ are not supported. The following heuristics are supported while working with Production Scheduling Board
SAP001 - Schedule Sequence SAP002 - Remove Backlog SAP003 - Schedule Sequence Manually (Fiori UI pop-up supported) SAP004 - Minimize Runtime SAP005 - Schedule Operations SAP_DS_01 - Stable Forward Scheduling SAP_DS_02 - Enhanced Backward Scheduling
SAP_DS_03 - Change Fixing/Planning Intervals SAP_DS_04 - Activate Seq.-Dependent Setup Activities
For a list of SAP notes to be implemented, refer corresponding release information note for the app. Deletion of Advanced Planning-relevant Work Centers
Capacity deletion in advanced planning-relevant work centers functions like it does in the conventional integration model, without change transfer being switched on. If you try to create a new Advanced Planning-relevant work center without capacity, you get an error message. Usage with EWM as a part of S/4HANA
If you use EWM and APO in the same client, you have to use system type SAP_APO and release 713 with an Integration model pointing to itself is used for the master data distribution for both EWM and APO. As a consequence, you cannot use batch management on plant level (available with EWM 9.4 and higher). Usage of “Side-by-Side SCM-APO” as a part of S/4HANA
Certain versions (refer SAP Note 2376061) of a “Standalone SCM - APO” system running side-by-side with SAP S/4HANA are supported (including all functions integrating standalone SNP, DP and PP/DS). "Standalone SCM-APO" and PP/DS for SAP S/4HANA can be used together, but the data modelling should ensure that there is no data dependency. Integration of orders generated out of "Standalone SCM-APO" to PP/DS for SAP S/4HANA or vice versa is not supported. Special Procurement Types
The following special procurement types from SAP S/4HANA are supported in PP/DS for SAP S/4HANA:
Subcontracting Stock transfer Phantom assembly Production in alternative plant (called "production in alternative location" in SAP APO)
The following special procurement types from SAP S/4HANA are not supported in PP/DS for SAP S/4HANA:
Withdrawal from alternative plant Direct production/collective order Phantom in planning
Lot-Sizing Procedure Fixing and Splitting
The lot-sizing procedure Fixing and Splitting (FS) is not supported in PP/DS for SAP S/4HANA. Explanation and recommendation: If planning is performed in SAP S/4HANA, all partial lots created when using FS cover exactly one requirement and are scheduled in a sequence (in contrast to FX, where all partial lots are scheduled to start at the same time). Though the planning is executed infinitely, the FS procedure spreads the planned orders. This makes finite planning that might be done later in SAP S/4HANA easier, especially if there are no planned orders of other products using the same resource. In PP/DS for SAP S/4HANA, this lot-sizing procedure is not available because better options are available to create a finite schedule for planned orders. Planning with Validity Recommendations of BOMs and Routings
Regarding planning with limited validities of BOMs and routings, see documentation note 385602. Production Data Structure (PDS)
The supported functionality of PDS differs from that of the production process model (PPM). PPM is not supported in PP/DS for SAP S/4HANA.The differences are described in SAP Note 1079959. The limitations of the PDS functionality are described as follows:
Block Planning:
Classification of operations with class type 018 is not possible for recipes. If recipes are used in SAP S/4HANA and block planning is used in PP/DS for SAP S/4HANA, a BAdI must be implemented for the classification of the activities.
Variant Configuration and Object Dependencies:
To add characteristic requirements to an input node, it is necessary to implement the BAdI method CHANGE_EXPL_RESULT of the BAdI /SAPAPO/CULLRTOEXPL or to use an ABAP class that is maintained at the input node. In case of non-configurable BOM, it is possible to set default requirements by maintaining batch classification in the BOM.
Note: When a Stock Transfer Requisition with characteristic requirement is converted in SAP S/4HANA or changed in SAP S/4HANA after the conversion is triggered from PP/DS for SAP S/4HANA, there might be inconsistencies in characteristic-requirement data of the converted/changed Stock Transfer Orders. It is not recommended to directly convert STR with characteristic-requirement in SAP S/4HANA or change the converted STO afterwards. Subsequent documents like delivery will be created without requirements in PP/DS for SAP S/4HANA which may cause broken pegging relationships.
PP-PI/Recipes:
Relationships between phases of different recipes are not supported.
No material quantity calculation.
No product flow (container resource).
Comparison Report PDS and SAP S/4HANA Explosion:
The comparison report (transaction /SAPAPO/RTO_ORD_COMP) does not compare the following: o o o o o
Sub-operations and secondary resources Setup groups and setup keys Configuration of the input and output products Durations of order internal relationships Continuous input/output must be set using a BAdI.
The PDS is NOT RELEASED for the following functionalities:
Parameter efficiency
Extended order generation (EOG)
Multiple output planning (MOP)
Planning with Phantoms:
When using the PDS, it is not allowed to use the same phantom several times in the BOM of a finished product in case a component of this phantom is assigned to different operations in the routing.
Editing Production Data Structure (PDS)
Engineering Change Management (ECM)-relevant changes for components cannot be simulated using the 'PDS Edit' functionality. However, ECM-relevant PDS, transferred from SAP S/4HANA, can be copied to inactive planning versions. Fixed Pegging
Fixed pegging in PP/DS for SAP S/4HANA is not kept during all document type changes in SAP S/4HANA. SAP Note 698427 lists all supported document type changes. Note the following restrictions:
The stock transfer orders have two nodes. Fixed pegging is applicable for the supply node at the target location, but not for the requirement node at the source location. Not supported at all are forecasts and forecast consumption, scheduling agreements (neither SD nor MM) and REM backflush, since these are not sensible from a process point-of-view. Collective orders are not supported in PP/DS for SAP S/4HANA, and consequently, not supported by fixed pegging either. Assembly processing is not supported (No integration of SAP S/4HANA assembly orders (planned orders)). Document type changes from customer inquiry to customer quotation and from customer quotation to sales order are not supported. Document type change from transport order to delivery is not supported.
The limitations of fixed pegging with respect to other functions and processes are described in SAP Note 704583. Some additional comments:
Shelf Life: Fixed pegging does not take shelf life restrictions into account. Make-to-Order: Though it is technically possible to use fixed pegging in a maketo-order scenario as well, it does not make much sense because the assignment between demand and receipt is already given by the account planning segment. Prioritization: Though fixed pegging does not calculate any priorities by itself, it can propagate the priorities from the requirement. Batch Determination: Batch determination in SAP S/4HANA is not influenced in any way by the fixed pegging in PP/DS for SAP S/4HANA. The batch
determination in SAP S/4HANA does not trigger creation of the corresponding fixed pegging arc in PP/DS for SAP S/4HANA. It is however possible to use the heuristic SAP_PP_019 to create fixed pegging in PP/DS for SAP S/4HANA based on the same batches, even though this is not an online process. A prerequisite for this is that no fixed pegging must have existed before.
Quantity Propagation: Changes in the order quantity of a requirement do not lead to the adjustment of the order quantity of a fixed pegged receipt element and vice versa. Multiple scheduling lines in sales and purchase orders: Considerable information for the integration between SAP S/4HANA and PP/DS for SAP S/4HANA is based on the order item and not on the schedule line item. Therefore, during document type changes, the quantities for the fixed pegging are kept for the order item but not necessarily for the correct schedule line. The heuristic for creating fixed pegging can be called before or after a MRPlevel-based Production Planning Run. During the planning of single products or between MRP levels in a Production Planning Run, it is not possible to include the SAP_PP_019 heuristic because there is no possibility in the Standard Heuristic Framework to integrate other heuristics in addition to the product heuristics. If you want to integrate logic similar to that provided by SAP_PP_019 within a product heuristic (for example, in SAP_PP_002 - Standard Lot Heuristic), the BAdI /SAPAPO/RRP_PLANNING must be used to create fixed pegging before the Net Requirements Calculation (Method PEGID_GET_IO)
Safety Stock in PP/DS
The Virtual Safety Stock Elements option that is used to cover unexpectedly high requirements is the only safety stock method supported in PP/DS for SAP S/4HANA. The option Real Safety Stock Requirements that is needed to resolve delays or problems in production is not supported. To consider dynamic safety stock (for example, safety days supply) in PP/DS for SAP S/4HANA, new alerts 'stock below safety stock,' 'stock below target stock,' and 'stock exceeds target stock' are provided. Characteristics, shelf-life and minimum-maximum pegging intervals are not considered for the new stock alert types. The SAP S/4HANA Customizing value for the percentage of safety stock availability will not be integrated with PP/DS for SAP S/4HANA. Product master data of PP/DS is mapped from the SAP S/4HANA material master to utilize the target stock level method functionality. The mapping is as follows o 'SM' if safety stock & time is maintained
o o
'SB' if only safety stock is maintained 'SZ' if only safety time is maintained
Time-dependent target stock level methods are not supported by PP/DS for SAP S/4HANA. Consequently, target stock alerts are only generated when a static target stock level method is used. The fill level of the container resource is not affected by this development. For planning, PP/DS for SAP S/4HANA does not take into account all possible values that can be maintained on the Lot-Size tab in the APO product master.
PP/DS for SAP S/4HANA supports the following entries:
Reorder point method: 2 (Reorder supply from location product master)
Target stock level method: Target days' supply from product master
Safety stock methods: No Safety Stock SB - Safety Stock from Location Product Master SZ - Safety Days' Supply from Location Product Master SM - Max. of Safety Stock and Safety Days' Supply from Location Product
Master Shelf Life
Create dependencies for characteristic: Implement Note 394229. Run report RVBCOR08. Make sure that the report ends without errors. If an error occurs, see Note 604757. Regarding shelf life functionality, see SAP Notes 751392 and 563863. Reservation Planning
This functionality is not supported. Order Combination for Mill Products
This functionality is not supported. Planning Scenarios within Consideration of Length Allowance
Certain planning scenarios within consideration of length allowance are not supported. From the planning perspective, either the operation duration or the operation capacity requirement may be variable (but not both at the same time). The solution does not support scenarios where the operation duration is fixed and the operation varies according to operation quantity. Also not supported are setup durations that have been modified using an available BAdI. Setup times are fixed in the PDS. Scheduling Mode 'Close Gaps'
Depending on the complexity of the scenario and the planning environment, the system is not always able to schedule the operation and close existing gaps even though the scheduling mode 'Insert and Close Gaps' is used. Compact Planning
Compact scheduling concentrates on reduction of lead time of orders. To achieve this in a meaningful way, orders should contain no fixed activities. If they do, a compact schedule cannot be guaranteed. In such cases where orders do contain fixed activities (for example, partially confirmed orders), other optimization strategies such as Prioritization or partially confirmed orders (PCO) should be used instead. PP/DS Optimizer
PP/DS Optimizer is an optional component in S/4 HANA. For the supported optimizer version, refer Product Availability Matrix (PAM) of relevant version of S/4 HANA. For information regarding installation of SCM Optimizers, refer SAP Note 1686826. See SAP Note 712066 for recommendations and restrictions for the PP/DS Optimizer. Explanation Protocol for PP/DS Optimizer
The Explanation Protocol is to be used like a protocol; it is not a problem-solving tool. Customers are able to see the explanations but will be unable to jump from an explanation to the place where the problems could be fixed. The navigation inside the explanation GUI is restricted to functionality that is offered by the ALV grid. When the Explanation Protocol has to protocol a large amount of data, the lists inside the GUI are very long and the display could be slow. There is no solution as yet for this problem. Transfer Planner from SAP S/4HANA to SAP APO
The planner in SAP APO does not correspond to the MRP controller in SAP S/4HANA and is not transferred to SAP APO. If it is desired to match the MRP controller to the SAP APO planner, it has to be considered that the field planner in SAP APO has three
characters and is independent from a location (in contrast to SAP S/4HANA) .
Capacity Reservation
This feature is not supported. Rapid Planning Matrix (RPM)
The Rapid Planning Matrix can only be used in combination with the iPPE and with production line resources - and not in combination with shop floor resources (single, multi, single-mixed and multi-mixed). The transaction RPMBAL to display capacity utilization (capacities of resources and their utilization by activities coming from RPM LC matrices) is not released. Also see SAP Note 699773. Subcontracting
Subcontracting Without Source Location in PP/DS is the only option supported. Following sub-contracting scenarios are not supported for this release o o o
Subcontracting with Source Location in PP/DS Subcontracting with Scheduling Agreements in PP/DS Subcontracting with Third-Party Provision of Components in PP/DS
Serial Numbers
A material may have a serial number in SAP S/4HANA. However, there is no processing of serial numbers in PP/DS for SAP S/4HANA Planning Without Final Assembly
The system only creates safety stock in the make-to-stock segment. Only demands in the make-to-stock segment can consume stock. Keeping Activity Dates when Transferring Orders to PP/DS for SAP S/4HANA
The functionality to keep activity dates provides the possibility to avoid PP/DS for SAP S/4HANA having to do a rescheduling when orders are transferred from SAP S/4HANA to PP/DS for SAP S/4HANA. The operations of production orders must have the status DSEX in SAP S/4HANA to keep their activity dates in PP/DS for SAP S/4HANA. The activity dates of planned orders are generally retained, as long as the PDS is not reexploded. Limitations:
Goods receipt time processing activities are always scheduled. However, with correct and unchanged settings at the handling resource and with an unchanged goods receipt processing time, this should not have an impact on the dates of the goods receipt time processing activity. Not all finite strategies are supported with this functionality. For some finite strategies, the system switches to infinite scheduling in case the activity dates are kept. However, SAP in any case recommends infinite strategies in the strategy profile for CIF integration. Keeping activity dates overrules the settings for synchronization for a resource. If activity dates are kept in PP/DS for SAP S/4HANA, existing violations of other boundary conditions in PP/DS will not be removed; for example, violations of pegging relationships and relationships between operations.
PP/DS Horizon
The 'PP/DS Horizon' field is only available in Model and Version Management. It is not present in product master for each product. Multiple Partial Confirmations on an Operation of a Manufacturing Order
Multiple partial confirmations on an operation of a manufacturing order do not reduce the remaining duration of the operation. An operation of a manufacturing order in SAP S/4HANA is partially confirmed. The corresponding SAP APO operation also has the remaining duration dates adjusted correctly. If a second partial confirmation is done on the same operation, you observe in PP/DS that the remaining duration and dates of the operation are not getting updated according to the new (just confirmed) values. iPPE Workbench Express
The iPPE Workbench Express is not released at all for SAP S/4HANA integration and CDP. Alternate Sequences of SAP S/4HANA Routing
Alternate sequences functioning as at present in SAP S/4HANA routings are not supported in integrated PP/DS for SAP S/4HANA orders (See SAP Note 437400). Setup Information Integration
Setup information from SAP S/4HANA, if maintained (non-initial), is taken over in PP/DS for SAP S/4HANA. It has to be thus ensured that both systems have maintained consistent data. Prior to this, PP/DS setup information was retained. MRP-based Detailed Scheduling (DS)
MRP-based DS functionality is not supported. Fault-Tolerant Scheduling
Fault-tolerant scheduling is only used for scheduling of orders and cannot be used for their creation.
No backtracking in scheduling: A scheduling action can affect more than operation. However, each operation is scheduled only once, independently of previous operations and in a given sequence. If a scheduling problem consisting of several operations is solved by an allowed violation of a constraint for the first operation, the scheduling action might still terminate without solution. This could happen because the problem only occurs at the second operation. If 'Schedule Infinitely' is chosen as the fault-tolerance option, the scheduling modes 'Insert Operation', 'Insert Operation and Close Gaps' and 'Squeeze In' can cause some operations to be pushed outside the planning horizon (the operation sequence is kept with these scheduling modes). Since infinite scheduling does not allow scheduling outside the planning horizon, the scheduling action can terminate without solution.
Reference Operation Sets
Reference operation sets are only integrated for PDS and for orders. Usage of Long Products Planning (LPP)
For LPP solution to be used, you must consider SAP Note 880091. Model Mix Planning (MMP)
For information on the limitations for Model Mix Planning, see SAP Note 627377. The functionality of the Genetic Algorithm for multilines is limited and should be used only after consultation with SAP. For example, only lines belonging to the planning segment and the restrictions assigned to those lines are taken into account during the optimization run. The Model Mix Planning algorithms do not take the priorities of the customer-independent requirements into account. MMP also does not consider the settings made in 'Model and Version Management'. Multilevel Scheduling Framework
The objective of the Multilevel Scheduling Framework is to provide a basis for heuristics such that they can tackle more complex scheduling problems by processing the activity network instead of single activities. The Multilevel Scheduling Framework is not yet
released for customer developments as SAP might change the interface without compatibility. Order validity is considered such that orders that cannot be scheduled finitely on a resource are scheduled deallocated within the order validity. If it is not possible to schedule the orders deallocated within the validity interval, the orders remain in their original positions. The following conditions/parameters are not supported by this heuristic:
Relationships with maximum length (order internal, or between activities of different orders - that is to say, pegging arcs with maximum length)
Continuous I/O
Shelf life
Characteristics
Container resource
Production campaign constraints
Block planning
Synchronization on multi-resources
Operation Split
The functionality of operation split is not supported in PP/DS for SAP S/4HANA. Also see SAP Note 441777. Classification System (CDP vs VC/iBase)
Usage of VC: When running in the one system, CIF transfer for classification data of class type 300 is not required. PP/DS for SAP S/4HANA directly reads class 300 related data from SAP S/4HANA. This leads to the following system behavior when using VC-planning in the one system approach:
CIF transfer for classification data in class type 300 is not required APO reads from SAP S/4HANA classification which is assigned to MARA
The APO product master data transaction /SAPAPO/MAT1 does not show the VC relevant class assignments, which can be viewed on the SAP S/4HANA material master. (SAP S/4HANA classification data is assigned via MARA whereas the APO product master display shows APO-assignments via /SAPAPO/MATKEY) Reference characteristics: unlike SCM Server, where CIF maps table fields for reference characteristics, PP/DS for SAP S/4HANA requires a mapping of reference characteristics procedure code via BADI /SAPAPO/CURTO_CREATE
Usage of CDP: Prerequisite: To use planning with CDP (and batches) data in the PP/DS for SAP S/4HANA please activate the content of BC-set /SAPAPO/APO_ON_ERP_CDP. This will introduce customizing for APO classes 230 and 400. When running in the one system approach, CIF transfer for classification data in class type 23/300 to type 230/400 is required. Integration models need to be maintained for relevant organization areas for these class types. PP/DS for SAP S/4HANA directly reads related data from the APO-only classes of type 230 and 400. This leads to the following system behavior when using CDP-planning in the PP/DS for SAP S/4HANA deployment:
PP/DS for SAP S/4HANA reads from SAP S/4HANA classification which is assigned to /SAPAPO/MATKEY The product master data /SAPAPO/MAT1 shows the CDP relevant class assignments only, assignments to 23/300 can be viewed on the SAP S/4HANA material master. (SAP S/4HANA classification data is assigned via MARA whereas the APO product master display shows APO-assignments via /SAPAPO/MATKEY)
Additional Info: If the components for subcontracting are planned with characteristic dependent planning (CDP), the characteristic values are not transferred to SAP S/4HANA. Classification is not used for components of in-house production orders. The iPPE side access does not support CDP classification. Reference characteristics: It is necessary to first transfer characteristics and then the BOM and routings. Therefore, it is not possible to read SAP APO master data information in the BAdI implementation. The simultaneous use of different configuration schemes - CDP and variant configuration (VC) - within one client is not supported.
In the delta report, the classification is checked for:
VC regarding the same configuration reference
CDP regarding the existence of characteristics
It is possible to perform an extended configuration check for the classification with the effect that the value of the characteristics is checked as well. Consistency Check in liveCache (Transaction OM17):
Consistency of information for characteristics-based time series is not checked Some checks do not prove full consistency but only carry out important plausibility checks Checks for VC configuration only apply to active planning version (planning version 000) Correction of inconsistencies may require subsequent execution of CIF delta report. There is no link between this functionality and CIF delta report.
Overlap and Continuous Input / Output
Overlap due to continuous production (quantities are continuously handed over to the next processing step instead of only at the end) can be modeled in two ways:
Within an order, by order internal relationships a start-start relationship can be defined Between orders, the functionality of continuous consumption can be used
Other limitations:
Note that continuous consumption is only considered in production planning heuristics and not in scheduling heuristics. Continuous consumption does not work with external procurement and sales orders. The heuristic SAP_PP_C001 must not be called by the heuristic SAP_PP_Q001.
See further explanations in the Customizing where the heuristics are maintained and also SAP Note 448960.
Pegging with Delivery Tolerances and 'Use Total Supply'
This functionality should be used only after consultation with SAP. The functionalities "delivery tolerances", "use entire receipt" and "use total stock" (Under the product master, see 'Demand' tab) only lead to satisfying results in very simple cases. For example, the combination of partial delivery and delivery tolerance leads to incorrect results because the system cannot calculate the delivery tolerance correctly in case of a partial delivery. It is therefore necessary to contact SAP in order to evaluate if the mentioned functionalities can be used in the customer's scenario. Accessibility
The Resource Planning Table is not intended to handle or to be used for such business functions as:
Planning of multiresources
Planning of bucket resources
Displaying network information (pegging, relationships)
The function can be called only from those transactions that call the screen 'Receipts View,' which is screen 1000 from the function group /SAPAPO/RRP_FRAMES. This includes the transactions:
/SAPAPO/RRP4 - Receipts View /SAPAPO/RRP7 - Mass Conversion/Transfer of Planned Receipts in Active Planning Version
/SAPAPO/CDPS0 - DPS Variable View and other related transactions
/SAPAPO/PPT - Product Planning Table
Calculation of Capacity Requirements, Durations and Component Requirements
The calculation of capacity requirements, durations, and component requirements are calculated using the formula X = (Order quantity) * A + B. In contrast to SAP S/4HANA, other formulas are not supported in PP/DS for SAP S/4HANA. Partial Delivery of Output Products
The full quantity of an in-house order is available at one discrete point in time, usually at the end of the order (with the exception of continuous input/output).
A partial delivery of the output product is not supported in PP/DS for SAP S/4HANA. It is not recommended to split in-house orders in order to create a workaround for the partial delivery of the output products because this may lead to performance problems.
CDP and Block Planning
Concerning CDP, there are certain limitations regarding unspecified characteristics in planning and pegging; see SAP Note 526883. Regarding block planning, see SAP Note 528189. PP/DS Optimization
PP/DS Optimizer cannot create orders. Characteristics-based Deployment in PP/DS
This feature is not supported. Stretching and Shrinking of Operations (Process Industry Scenario)
Stretching and shrinking operations, either manual or using heuristic, is only applicable for process industry scenarios. When an operation is stretched or shrunk manually or using heuristic 'Fill gaps by changing operation duration' (SAP_PI_002) in the Detailed Scheduling Planning Board, operations are not scheduled automatically. To schedule the stretched or shrunk operations, the planner must subsequently execute the scheduling function.
Software Components Software Component S4CORE This document is referenced by Number
Title
2456959
S/4HANA 1610 Short dump during planned order retransfer from ECC to embedded PPDS
2434851
How to setup Advanced Planning (PPDS) in S/4 HANA (CIF Basic Setup)
2408419
SAP S/4HANA - Multi-Node Support
2381624
Release Information Note: Production Planning and Detailed Scheduling for SAP S/4HANA 1610
From 101
To 101
