Apo 31 Release Notes

SAP Advanced Planner and Optimizer (SAP APO) Release 3.
Release Notes
Copyright 2001 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation. ORACLE is a registered trademark of ORACLE Corporation. INFORMIX-OnLine for SAP and Informix Dynamic Server Incorporated.
TM
are registered trademarks of Informix Software
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. Design: SAP Communications Media
SAP AG Table of Contents APO 3.1 ________________________________________________________________
1 1.1 1.2 1.3 1.3.1 1.3.1.1 1.3.1.2 1.3.1.3 1.3.1.4 1.4 1.4.1 1.4.2 1.4.2.1 1.4.3 1.4.3.1 1.4.3.2 1.4.3.3 1.4.4 1.4.4.1 1.4.4.2 1.4.5 1.4.5.1 1.4.5.2 1.4.6 1.4.6.1 1.4.6.2 1.4.7 1.4.7.1
APO Advanced Planner and Optimizer - APO Descriptive Characteristics for Use in Order LiveCache Trader's and Scheduler's Workbench (TSW) APO-CA APO Cross-Application Components APO-CA-CDP Characteristics-Dependent Planning Block Planning (enhanced) Batch selection in the sales order for CDP (new) Maintaining classes and charac. in CDP (changed)) Evaluations in PP/DS (enhanced) APO-MD Master Data Mass Maintenance of SAP APO Master Data (New) APO-MD-MO Model Model Consistency Check (New) APO-MD-LO Location Displaying and Deleting Application Log for Location (New) Calculation of Transportation Zone Coordinates (New) Mass Geocoding of Locations (New) APO-MD-PR Product Display of alerts (enhanced) PP Heuristics for Sales Order Oriented Planning (new) APO-MD-RE Resource Block Planning (enhanced) Detailed Scheduling Strategies (enhanced) APO-MD-PPM Production Process Model Detailed Scheduling Strategies (enhanced) SNP PPM Generation With Lot Size Margins (new) APO-MD-PPE Product and Process Engineering Action Handler (Enhanced)
1 1 2 4 4 4 6 6 6 7 7 8 8 8 8 9 9 9 9 10 10 11 12 13 13 14 15 15
________________________________________________________________
SAP AG iii
APO 3.1 Table of Contents SAP AG ________________________________________________________________
1.4.7.2 1.4.7.3 1.4.7.4 1.4.7.5 1.4.7.6 1.4.7.7 1.4.7.8 1.4.7.9 1.4.7.10 1.5 1.5.1 1.5.2 1.5.2.1 1.5.3 1.5.3.1 1.5.3.2 1.5.4 1.5.4.1 1.5.5 1.5.5.1 1.6 1.6.1 1.6.2 1.7 1.7.1 1.7.2
Introduction of Action Points (Enhanced) Creating Multiple Work Centers (New) Overview of New Functions in Line Design (Enhanced) Creating Line Structures with Alternatives (new) iPPE Production Resource (New) New Functions in the iPPE Process Structure (Enhanced) iPPE Actions for Upgrading to SAP APO 3.1 (New) Shop Floor Production in Integrated Product and Process Engi Enhancements and New Functions in the iPPE Product Structure APO-SNP Supply Network Planning (SNP) Conversion of SNP orders into PP/DS orders (enhanced) APO-SNP-BF Basic Functions SNP PPM Generation With Lot Size Margins (new) APO-SNP-INS Interactive SNP Cross-Period Lot Size Planning (new) New Design of the SNP Optimizer Profile and SNP Optimizer Wi APO-SNP-SCH SNP Scheduling Agreement Processing Scheduling Agreement Processing in Supply Network Planning ( APO-SNP-CTM Capable-To-Match Descriptive Characteristics for Use in Order LiveCache APO-FCS Demand Planning Sales Order Oriented Planning Descriptive Characteristics for Use in Order LiveCache APO-PPS Production Planning and Detailed Sch Recreation of Receipt Elements Sales Order Oriented Planning
17 18 18 20 21 21 24 24 25 26 26 28 28 29 29 30 32 32 33 33 34 34 35 37 37 37
________________________________________________________________
iv SAP AG
1.7.3 1.7.4 1.7.5 1.7.6 1.7.7 1.7.8 1.7.9 1.7.10 1.7.11 1.7.11.1 1.7.12 1.7.12.1 1.7.12.2 1.7.13 1.7.13.1 1.7.13.2 1.7.13.3 1.7.14 1.7.14.1 1.7.15 1.7.15.1 1.7.15.2 1.7.16 1.7.16.1 1.7.17 1.7.17.1 1.7.18
Descriptive Characteristics for Use in Order LiveCache Conversion of ATP tree structures into PP/DS procurement pro ATP check in PP/DS (new) Buffer Process with Container Resources (New) Detailed Scheduling Strategies (enhanced) Extended Order Generation (new) Checks with order opening (advanced) Planning procedure APO-PPS-PPT Product Planning Table Enhancements in the product planning table APO-PPS-DST Detailed Scheduling Planning Board Detailed Scheduling Planning Board (enhanced) Planning of Production Campaigns in PP/DS (Enhanced) APO-PPS-PVW Product View Display of alerts (enhanced) ATP check in PP/DS (new) Display of ATP data in the order view (enhanced) APO-PPS-SCF Scheduling Functions Detailed Scheduling Strategies (enhanced) APO-PPS-POM Planned Order Management Action Handler (Enhanced) Planned Order Management (new) APO-PPS-CDS Collaborative Management of Delivery Collaborative Management of Delivery Schedules (CMDS) (new) APO-PPS-EVA Evaluation Evaluations in PP/DS (enhanced) APO-PPS-SNP SNP to PP/DS
38 40 41 43 50 51 52 53 54 54 55 55 56 56 56 57 58 59 59 60 60 62 65 65 67 67
________________________________________________________________
SAP AG v
1.7.18.1 1.7.18.2 1.7.19 1.7.19.1 1.7.19.2 1.7.19.3 1.7.19.4 1.7.19.5 1.7.19.6 1.7.19.7 1.7.19.8 1.7.19.9 1.7.20 1.7.20.1 1.7.20.2 1.7.20.3 1.7.21 1.7.21.1 1.7.21.2 1.7.22 1.7.22.1 1.7.23
Conversion Conversion of SNP orders into PP/DS orders (enhanced) SNP PPM Generation With Lot Size Margins (new) APO-PPS-PCM Production Campaign Planning of Production Campaigns in PP/DS (Enhanced) Improved Handling of Campaigns in the DS Planning Board (New Introduction of the Campaign Status (New) Introduction of the "Campaign-Relevant" Indicator for Resour Introduction of the "Consider Campaign Requirements" Indicat Handling of Campaigns with Errors (New) Improved "Adjust Setup/Clean-Out Order" Function (Changed) Deleting Empty Campaigns (New) Business Add-Ins for Campaign Planning (New) APO-PPS-MMP Model Mix Planning Model Mix Planning: Planning Line Networks New functions in restrictions maintnenance for Model Mix Pla ATP Check for Planned Orders for RPM Products APO-PPS-RPM Rapid Planning Matrix New Functions in the Rapid Planning Matrix ATP Check for Planned Orders for RPM Products APO-PPS-AHT Action Handler & Tracking Action Handler (Enhanced) APO-PPS-PPC Confirmation
68 68 71 71 71 72 74 75 76 76 77 78 79 80 80 83 83 85 85 87 88 88 90
________________________________________________________________
vi SAP AG
1.7.23.1 1.7.24 1.7.24.1 1.7.24.2 1.8 1.8.1 1.8.2 1.8.3 1.8.4 1.8.5 1.8.5.1 1.8.5.2 1.8.5.3 1.8.5.4 1.8.5.5 1.8.6 1.8.6.1 1.8.7 1.8.7.1 1.9 1.9.1 1.10 1.10.1 1.10.1.1 1.10.1.2 1.11 1.11.1 1.11.2 1.11.2.1
99 99 Changed ATP Tree Structure Data Model (enhanced) Deleting ATP Tree Structures 99 Regenerate temp. quantity assignments from ATP tree 99 APO-ATP-EST Explanation & Simulation Tool 100 Enhancement in the Explanation and Simulation Component 100 APO-ATP-BOP Backorder Processing 100 Enhancements in Backorder Processing 100 APO-AMO Alert Monitor 101 Display of alerts (enhanced) 101 APO-OPT Optimization 102 APO-OPT-SNP Supply Network Planning 102 Cross-Period Lot Size Planning (new) 102 New Design of the SNP Optimizer Profile and SNP Optimizer Wi 103 APO-CPR External Procurement 104 Converting Purchase Requisitions into Purchasing Documents ( 104 APO-CPR-SCH Delivery Planning 105 Dynamic Stopping of Scheduling Agreement Releases (New) 105
Processing of confirmations (changed) APO-PPS-HEU Heuristics Block Planning (enhanced) PP Heuristics for Sales Order Oriented Planning (new) APO-ATP Global Availability Check Recreation of Receipt Elements Multilevel ATP Check Conversion of ATP tree structures into PP/DS procurement pro ATP check in PP/DS (new) APO-ATP-BF Basic Functions Correlation Calculation Enhancement in the ATP Tree Structure Display
90 91 92 93 94 94 94 96 97 98 99
________________________________________________________________
SAP AG vii
1.11.2.2 1.11.2.3 1.11.2.4 1.11.3 1.11.3.1 1.12 1.12.1 1.12.2 1.12.3 1.12.4 1.12.5 1.12.6 1.12.7 1.12.8 1.12.9 1.12.10 1.12.10.1
Several Deliveries for Scheduling Agreement Release (New) New Functions in Scheduling Agreement Release Processing (Ch New Print Form for the Output of Scheduling Agreement Releas APO-CPR-SCT Subcontracting Transfer Subcontracting PPM to Source Location via CIF (New) APO-INT Interfaces Processing of change pointers (enhanced) Deltareport3 (new) Deactivating source of supply determination (new) Selection of source of supply (enhanced) Integration of Configurations for External Proc. Docu. Selection screen for integration model (changed) Configuration of the CIF application log (new) SCM Queue Manager (new) Assigning a queue type APO-INT-EXT Interface for External Systems New and Changed Business Objects and BAPIs (Enhanced)
105 106 106 107 107 107 107 108 108 109 109 109 110 110 111 111
________________________________________________________________
viii SAP AG
APO 3.1 ________________________________________________________________
1 APO Advanced Planner and Optimizer - APO 1.1 Descriptive Characteristics for Use in Order LiveCache
Use
Before Release 3.1 product and location were the only characteristics that could be transferred from Demand Planning to SNP and Production Planning /Detailed Scheduling (PP/DS). As of this release it is possible to define descriptive characteristics for use in applications that use Order LiveCache . These characteristics permit more detailed planning in several applications. The following functions are affected: o Demand Planning Release of Unconstrained Demand from DP to Order LiveCache This process transports the descriptive characteristics with their values from DP to order LiveCache. This enables you to release data at any characteristic level. Note that descriptive characteristics are then only added to the independent requirements that are generated. Release of Constrained Forecast from Order LiveCache back to DP
This process recognizes the characteristics attached to the LiveCache order and transports the constrained forecast back to DP with the same characteristic values.
o -
CTM Demand Prioritization

It is possible to assign prioirities based on descriptive characteristics. For example you can specify that one customer or customer group is given preferential treatment if the demand cannot be completetly satisfied.
Rule Application
Currently rules can be found for a few attributes of the forecast (product, location, category). With descriptive characteristics it is possible to perform the rule finding process on any characteristic level in DP. For example including the customer in the descriptive characteristics enables the identification of customer specific rules for the same location/product forecasts.
Consumption In previous releases forecast consumption was restricted to a few attributes of the forecast (product, location) that could be matched to sales order attributes. With descriptive characteristics it is now possible to perform forecast consumption on any characteristic in DP that can be matched to an R/3 attribute of a sales order. For example including the customer in the descriptive characteristics enables the identification of customer specific forecasts for the same location/product that can be consumed by a sales order for that customer.
________________________________________________________________
SAP AG 1
APO 3.1 ________________________________________________________________
Effects on Customizing To specify that a DP characteristic is to be used as a descriptive characteristic in Order LiveCache, you assign it to a consumption group. In the consumption group you link the DP chararcteristic with a field in the ATP field catalog. You enter the consumption group in various objects or transactions, for example the location product, the release profile, or the demand profile. You maintain consumption groups in Customizing for Demand Planning under SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Demand Planning -> Basic Settings -> Maintain Consumption Group. If you use fields that have been assigned to descriptive characteristics and want to use special sorting in CTM Demand Prioritization, you specify the priorities in Customizing under SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Supply Network Planning (SNP) -> Capable-to-Match (CTM) -> Demand Prioritization -> Maintain Special Sorting or Maintain Special Sorting of Descriptive Characteristics. Read these two IMG topics for information on which activity to use.
1.2 Trader's and Scheduler's Workbench (TSW)

Use The following functions are available for the oil and gas industry: o o o o o additional types of location master data product planning book object hierarchy control for hierarchical selection SD contract numbers as descriptive characteristics in Demand Planning (DP) and Supply Network Planning (SNP) enhanced Transport Planning and Vehicle Scheduling (TPVS) functions
Additional Types of Location Master Data APO TSW provides two new types of location master data, called terminal location and geographic area location. You can use these location types in location hierarchies. The hierarchies are used in SNP, which includes the TSW stock projection worksheet, as well as in TSW enhancements to TPVS. Product Planning Book A new planning book, called 9ATSW_SPW1 with data view TSW_SPW1(1) is available for the TSW stock projection worksheet (SPW). The planning book contains enhancements specific to oil and gas, and it provides a framework for daily and weekly product planning.
________________________________________________________________
2 SAP AG
APO 3.1 ________________________________________________________________
The planning book calculates and displays the value of book stock that is transferred from the R/3 System in the row Book stock. If this figure is negative, it appears in the row Book backlog. To calculate the Stock on hand and Backlog column values, the planning book adds the What if receipt and the Book stock or Book backlog values, and subtracts the critical stock level (such as the unpumpable quantity defined in the location product master data) and the What if demand values from this figure. The planning book contains a function for calculating these values.
Object Hierarchy Control for Hierarchical Selection APO TSW allows you to navigate and select existing and new location types, such as the terminal and geographic area, in the supply chain model hierarchy within the SPW shuffler. You can also navigate and select within product hierarchies.
SD Contract Numbers As Descriptive Characteristics in DP and SNP In past releases, you could only transfer the product and location characteristics from DP to SNP, and from DP to Production Planning (PP) and Detailed Scheduling (PP/DS). The new release allows you to define descriptive characteristics for applications that use Order LiveCache. These characteristics allow more detailed planning in several applications. This new feature applies to the following functions: o o Demand Planning Release of unconstrained demand from DP to Order LiveCache This process transports the descriptive characteristics with their values from DP to Order LiveCache. This enables you to release data at any characteristic level. You should note that descriptive characteristics are then only added to the independent requirements that are generated. Release of constrained forecast from Order LiveCache back to DP This process recognizes the characteristics attached to Order LiveCache and transports the constrained forecast back to DP with the same characteristic values.
Enhanced TPVS Functions o TPVS real and dummy vehicles Within TPVS manual scheduling, you can change vehicles after you have assigned orders to a planned transport. You can define dummy vehicles in the resource master data for initial planning, before you select a real vehicle. When you have selected a real vehicle, you replace the dummy vehicle. Scheduling at terminal level When scheduling orders on a shipment or a nomination, you replace the real locations with the assigned terminals defined in the location hierarchy. These terminals are also shown in TPVS planning tables and they are used to define the shipment route stages. Order grouping to support ticket proration Within TPVS shipment scheduling, you can group orders together to support a combined ticket for several orders in the R/3 System. You will then prorate this ticket according to information maintained in the orders. Order change in R/3 leaves order assigned to shipment Whenever order data, such as quantities or timelines, are changed, the orders stay on the shipment and you invalidate the shipment to inform the scheduler that the shipment has been changed. APO R/3 interface for oil nominations
________________________________________________________________
SAP AG 3
APO 3.1
You can also transfer data out of the TPVS shipment into the TSW nomination to trigger execution processes as the result of actual physical events reported. Within TPVS scheduling, you can maintain additional nomination data.
Note: The navigation, selection, and TPVS functions, mentioned above, are available when you activate the TSW indicator in Customizing. To do this, in Customizing choose SAP Advanced Planner and Optimizer (SAP APO) -> Transportation Planning/Vehicle Scheduling (TP/VS) -> Trader's and Scheduler's Workbench (TSW) -> Activate TSW and Subcomponents.
1.3 APO-CA APO Cross-Application Components

1.3.1 APO-CA-CDP Characteristics- Dependent Planning
1.3.1.1 Block Planning (enhanced)

Use
SAP APO 3.1 has been enhanced with the following block planning functions: o o Block planning with buckets Block planning with the productive time or an equivalent to the productive time
Block planning with buckets
In SAP APO 3.1 you can now also execute block planning on single-mixed resources with bucket capacities. The blocks define the buckets. The bucket capacity of a block is derived from the productive time of the resources, and if necessary is corrected by an overload factor. In block planning with buckets for block-planned single-mixed resources, you can sucessively o Execute a "rough" finite scheduling, in which the system schedules operations finitely in the buckets Here, the time-continuous capacity of a block is not important for the resource availability in a block. Rather, the bucket capacity of the block is important. The system can only schedule an operation in a block if there is sufficent bucket capacity in the block. Execute a detailed finite scheduling, in which the system checks the capacity availability in a block against the time-continuous capacity in the block The system can only schedule an operation in a block if it can find a sufficiently long slot for the operation in the block.
For detailed finite scheduling of blocks on single-mixed resources after bucket-oriented finite scheduling, you can use the following heuristics: o Adjust block limits This heuristic adjusts the block limits within a cycle to the current resource loads of the block in the cycle. Reschedule block This heuristic schedules the operations finitely against the time-continuous capacity of the blocks. This heuristic can be called automatically by the adjust block limits heuristic.
________________________________________________________________
4 SAP AG
APO 3.1 ________________________________________________________________
Resource In the single-mixed resource, you specify the data for the definition of the bucket capacity. The resource maintenance has been enhanced accordingly for SAP APO 3.1. o Standard capacity tab page So that the system can derive the bucket capacity of a single-mixed us resource from the productive time, you must set the new from block planning option in the buckets field. This setting automatically sets the dimension of the bucket capacity to time. You process further data for block planning with buckets (overload factors and cycles) on the block planning tab page under maintain blocks. Planning parameter tab page So that a resources can be scheduled finitely, you must set the finite scheduling indicator, as before. In the new finite capacity field, you specify which capacity you want to schedule finitely - the timecontinuous capacity or the bucket capacity. In the detailed scheduling strategy , you can change between the capacities to be finitely scheduled. Block planning tab page, maintain blocks function If you have selected the from block planning entry under buckets on the standard capacity tab page, two new columns will be displayed in the block maintenance: In the cycle type column, a symbol specifies that a new cycle begins at the beginning of the current block. The cycle ends at the start of the next indicated block, or with the last specified block. In the overload (%) column, the factor by which the bucket capacity of the current block is increased, is displayed as the productive time in the block (see below).
Detailed scheduling strategy For block planning with buckets in SAP APO 3.1, the new scheduling mode find buckets with free capacity has been introduced in the detailed scheduling strategy. You use this mode for finite scheduling of the bucket capacity of block-planned single-mixed resources and infinite scheduling of the time-continuous capacity of all resources. If you want to finitely schedule the time-continuous capacity of a block-planned single-mixed resource (and all other resources), you use the existing find slots scheduling mode. Other finite scheduling modes are not suitable. Reconciliation of production process model and resource A prerequisite for block planning with buckets is the consistent maintenance of the resource capacity data (time-continuous capacity and bucket capacity) and the resource consumption of the activities in the production process model (PPM). In the PPM, the duration of the activity must correspond to the bucket consumption of the activity. Block planning with productive times and equivalents The absolute duration of a block on a resource is determined by the start and end date. For block-planned single resources, the absolute duration corresponds to a productive time and possibly a quantity to be produced within a block. Previously, you could create blocks only with absolute duration. In SAP APO 3.1 you can create new blocks with the productive time in seconds or an equivalent in any unit of measurement. When shifting blocks, the productive time is retained and not the absolute duration of the blocks. For the definition of equivalents to the productive time, you specify a conversion factor and the desired unit in the block maintenance. To do this, select the Conversion of the productive time tab page under Further Settings on the Interval tab page. To display the equivalent in block maintenance, select Further Settings,
________________________________________________________________
SAP AG 5
APO 3.1 ________________________________________________________________
You can no longer use transactions /SAPAPO/MC01MDEF and /SAPAPO/MC01MDEF2 to maintain CDP classes and characteristics in SAP APO. Instead, use the SAP R/3 class system transaction variants. In SAP APO, use transactions /SAPAPO/CT04CDP and /SAPAPO/CL02CDP to access class
and set the Productive time in equivalent indicator on the Display Options tab page.
1.3.1.2 Batch selection in the sales order for CDP (new)

Use
If batch characteristics are maintained for the sales order item, they can be transferred from the R/3 System into SAP APO and be defined there as characteristic requirements or characteristic value assignments. Simple value assignments, either value sets or an interval for numeric characteristics are also supported here. The minimum requirement for the transfer of batch characteristics is the R/3 plug-in 2001.2 for R/3 releases 4.6B and 4.6C. In the integration model, Classes/characteristics must be selected, and in SAP APO, CDP must be set as the characteristics and class system. In the R/3 System, you can use batch characteristics alternatively to the configuration. The configuration from the R/3 System, however, is generally used for characteristic requirements and value assignments for CDP. If you prefer to use batch characteristics instead of the configuration, make this setting in the /sapapo/tmc01xvr table in SAP APO. This setting will be valid client-wide (without specifying a class) or per class (Derive value assignments from requirements indicator). In the latter case, characteristic value assignments are derived from the batch selection, in other words, multiple values/intervals are reduced to a single value. For the Mix value assignments and requirements setting, you must ensure that the characteristic values for the batch selection and the characteristic values for the configuration are contained in the R/3 System. This is not the case in the standard system. You can therefore not use this setting without extending it on a customer-specific basis.
1.3.1.3 Maintaining classes and characteristics in CDP (changed)

Use
In SAP APO 3.1, changes were made in the following areas: o o CDP class and characteristics maintenance Transfer of data changes from SAP R/3 to SAP APO
Classes and Characteristics Maintenance Maintaining classes and characteristics in characteristics- dependent planning (CDP) was changed in SAP APO 3.1 to this: o
________________________________________________________________
6 SAP AG
APO 3.1 ________________________________________________________________
and characteristics maintenance of CDP.
The new class type 400 is available for CDP. It is set as default in CDP class maintenance.
For maintaining CDP classes and characteristics, the following functions and settings were not copied from the SAP R/3 transactions used: Characteristic maintenance o o o o o o o o o Engineering change management Documents, additional data and restrictions Interval values Upper/lower case Exponential display Restrictions Value hierarchy Alternative value check Dependencies
Class maintenance o o o o o o o o o o o Engineering change management Select class type (class 400 is set as default) Valid from, valid to Authorization fields Catalog DIN standard Print-relevant Selection-relevant Display-relevant Index-relevant Overwrite
Transfer of changes from SAP R/3 to SAP APO

It is only now possible to transfer class and characteristic changes automatically from SAP R/3 to SAP APO. You could transfer changes before with an initial transfer.
As of R/3 plug-in 2001.2, changes to classes and characteristics are transferred from SAP R/3 directly to SAP APO.
Effects on Existing Data
If you upgrade to SAP APO 3.1, note the following so that you can continue to work with the existing data: o Use SAP APO in connection with SAP R/3
________________________________________________________________
SAP AG
APO 3.1 ________________________________________________________________
Execute a new initial transfer of class and characteristic master data from SAP R/3 to SAP APO. Finally, execute report /SAPAPO/MC01_CACL_CDP_ADJUST. Use SAP APO as a standalone system
Execute report /SAPAPO/MC01_CACL_CDP_ADJUST.
1.3.1.4 Evaluations in PP/DS (enhanced)

Use
The following enhancements exist for evaluations in SAP APO 3.1: o Order list The system uses the characteristics symbol (green triangle) to show if an order product is a configurable product. To display the characteristics value assignments, click on the characteristics symbol. o Resource load The following display options exist for the evaluation of the load on block-planned resources: Display the block load in any unit of measurement In block planning, you can specify that the productive time of a resource is calculated into an equivalent with any unit of measurement. In this way, you can display the quantity to be produced for a block instead of the productive time. So that the equivalent is displayed in the evaluation of the resource load for a block-planned resource, select the display in block unit indicator under view selection, when calling up the evaluation. Display the block capacity For blocks with block-planned single-mixed resources, you can display the time-continuous capacity and the bucket capacity derived from the time-continuous capacity. A prerequisite is that you have set buckets from block planning for the resource for the standard capacity.
1.4 APO-MD Master Data

1.4.1 Mass Maintenance of SAP APO Master Data (New)
Use As of SAP APO 3.1, a mass maintenance tool is available which can be used to process the following SAP APO master data:
o o o o o o o
External Procurement Relationships Locations Production Process Models (PPMs) Products Quota Arrangements Resources Transportation Lanes
You are only able to make simultaneous mass changes for one of the above master data objects at a time. It is not possible to make mass changes for multiple master data objects at the same time.
Note You can use mass maintenance to change many objects simultaneously. Changes have a direct effect on all the chosen objects. This tool should therefore only be used by experienced persons with the necessary due care and attention.
________________________________________________________________
SAP AG 7
APO 3.1 ________________________________________________________________
This tool for the mass maintenance of master data in SAP APO is the same tool with which mass changes can be made to SAP R/3 master data. In addition to technical enhancements and improvements, above all the user interface has been specially revised for use in SAP APO, the emphasis being on user friendliness. To invoke the mass maintenance function, choose Master Data -> Mass Maintenance (transaction code MASSD) in the SAP APO Easy Access menu. If you prefer to use the same user interface as in R/3 when carrying out mass changes to SAP APO master data, jyou can start the tool with transaction code MASS.
See also For more information on the mass maintenance of SAP APO master data, refer to the documentation User Instructions for Mass Maintenance. To display this documentation, call up the mass maintenance tool in SAP APO Easy Access and choose Goto -> Help. For further general information on the mass maintenance tool, refer to the following Release Notes from SAP R/3: Cross-Application Functions: Mass Maintenance EnjoySAP - Enhancements in Cross-Application Mass Maintenance
The documentation is available in the SAP Library under Cross-Application Components -> General Application Functions -> Cross-Application Mass Maintenance (CA-GTF-MS).
1.4.2 APO-MD-MO Model 1.4.2.1 Model Consistency Check (New)

Use
As of release SAP APO 3.1, you can check whether the master data of a planning version is complete and free from contradictions regarding the use in the SAP APO scheduling functions. After a model was created with the Supply Chain Engineer or constructed via data transfer from an external system (SAP R/3, for example) and a planning version was created, the model consistency check provides the possibility of tracing missing or wrongly maintained master data and removing any inconsistencies. The model consistency check can be called up from the SAP Easy Access Menu (Master Data -> Model Consistency Check) or the SC Engineer
1.4.3 APO-MD-LO Location 1.4.3.1 Displaying and Deleting Application Log for Location (New)
Use
As of Release SAP APO 3.1, it is possible to display and delete an application log for the location. The location application log lists the messages issued by the following programs: o Deletion program for locations (program /SAPAPO/DLOC_DEL_JOB) The application log for this report gives you an overview of where links to the deleted location still exist, thus enabling you to remove them. All programs capable of running in background processing mode
In a later release, it will also be possible to display technical error messages occuring in the location in the application log. This will give the system administrator the opportunity to immediately localize and rectify these errors. You can display logs from SAP APO Easy Access via Master Data -> Location -> Application Log -> Display Application Log. You can delete logs from SAP APO Easy Access via Master Data -> Location -> Application Log ->
________________________________________________________________
8 SAP AG
APO 3.1 ________________________________________________________________
Delete Application Log.
1.4.3.2 Calculation of Transportation Zone Coordinates (New)

Use
As of Release SAP APO 3.1, it is possible to convert the existing SAP R/3 transportation zone data into the geographical coordinates of a geolocation for the location type transportation zone (location type 1005).
For more information, refer to the documentation for the program Calculation of Transportation Zone Coordinates (/SAPAPO/TZ_COORD_CALC).
1.4.3.3 Mass Geocoding of Locations (New)

Use As of Release SAP APO 3.1, a program enabling you to supply all locations with the relevant geocoordinates via background processing is available.
This is important for all locations were not already been supplied with the geocoordinates automatically during the process of creating or changing the associated address data. Whether the geocoordinates for a location were created automatically for a location depends on the geocoding program you selected in the Implementation Guide (IMG) and the SAP Release under which the location was created.
Should you have locations to which no geocoordinates have yet been assigned in your system, you can run this program. It is usually only necessary to start this program once.
To start the program, choose Master Data -> Location -> Mass Geocoding (transaction code /SAPAPO/MASSGEOCODE) in the SAP APO Easy Access Men. For more information, refer to the Report Documentation.
1.4.4 APO-MD-PR Product 1.4.4.1 Display of alerts (enhanced)

Use
The following enhancements exist in SAP APO 3.1 for displaying alerts in the order view: o Alert-relevance of a product In the Requirement tab page of the location product master, in the new product alerts field, you can set If the system determines direct alerts for the product If the product is relevant for network alerts As before, you use the PP/DS alert profile to specify if and which alerts the system should display
________________________________________________________________
SAP AG 9
APO 3.1 ________________________________________________________________
in the planning interface or in the alert monitor. In the standard delivery, the option determine direct alerts, relevant for network alerts is set. o Network alerts for receipts and requirements Previously, you could use the Display network alerts indicator under Set order view/periodic product view in the customizing for Production Planning and Detailed Scheduling to specify if the system should display network alerts; in doing this you could not distinguish between receipts and requirements. In SAP APO 3.1 you can make separate settings for if the system should display network alerts for receipts and requirements. The old Display network alerts indicator is therefore replaced by the following new indicators: Display network alerts for receipts Display network alerts for requirements
Effects on Customizing In the standard delivery, a setting is made so that the system does not display network alerts for receipts and requirements. So that the system displays network alerts, set the corresponding indicator in the customizing under Set order view/periodic product view.
1.4.4.2 PP Heuristics for Sales Order Oriented Planning (new)

Use In SAP APO 3.1 there are three new heuristic algorithms that you can use for sales order oriented planning. With this type of planning, you can convert planned orders or purchase requisitions into production orders or purchase orders only if these orders are used exclusively to cover sales orders. Using the requirements ascertainment algorithm (/SAPAPO/HEU_REQ_ASCERTAIN) you can determine the open planned independent requirements for selected products, that is, the planned independent requirements which are still not matched by any sales orders. Using the requirements ascertainment results you can identify the customers for whom you have planned the planned independent requirements and can ask the customers to issue sales orders by a specific deadline. Using an adjustment algorithm, you can delete the open planned independent requirements and make multi-level reductions to the related planned orders and purchase requisitions, down to the initial product level, after the deadline. As an option, you can make adjustments for selected products (algorithm /SAPAPO/HEU_ORGANIZE_VIA_PEGID) or selected orders (algorithm /SAPAPO/HEU_ORGANIZE). You organize the time flow using the requirements ascertainment horizon and the - shorter - adjustment horizon that you specified location product-specifically in the location product master in SAP APO 3.1. Effects on Customizing SAP delivers standard heuristics on the basis of these algorithms. In the customizing for Production Planning and Detailed Scheduling (PP/DS) under Maintain Heuristics, you can define heuristics with your own settings. If you want to use these heuristics in the order view, you must enter the heuristics in the heuristic profile that you are using for the order view, under Maintain Heuristics Profile.
________________________________________________________________
10 SAP AG
APO 3.1 ________________________________________________________________
1.4.5 APO-MD-RE Resource 1.4.5.1 Block Planning (enhanced)

Use
In SAP APO 3.1 you can now also execute block planning on single-mixed resources with bucket capacities. The blocks define the buckets. The bucket capacity of a block is derived from the productive time of the resources, and if necessary is corrected by an overload factor. In block planning with buckets for block-planned single-mixed resources, you can sucessively o Execute a "rough" finite scheduling, in which the system schedules operations finitely in the buckets Here, the time-continuous capacity of a block is not important for the resource availability in a block. Rather, the bucket capacity of the block is important. The system can only schedule an operation in a block if there is sufficent bucket capacity in the block. Execute a detailed finite scheduling, in which the system checks the capacity availability in a block against the time-continuous capacity in the block The system can only schedule an operation in a block if it can find a sufficiently long slot for the operation in the block.
Resource In the single-mixed resource, you specify the data for the definition of the bucket capacity. The resource maintenance has been enhanced accordingly for SAP APO 3.1. o Standard capacity tab page So that the system can derive the bucket capacity of a single-mixed us resource from the productive time, you must set the new from block planning option in the buckets field. This setting automatically sets the dimension of the bucket capacity to time. You process further data for block planning with buckets (overload factors and cycles) on the block planning tab page under maintain blocks.
Planning parameter tab page So that a resources can be scheduled finitely, you must set the finite scheduling indicator, as before. In the new finite capacity field, you specify which capacity you want to schedule finitely - the
________________________________________________________________
SAP AG 11
APO 3.1 ________________________________________________________________
time-continuous capacity or the bucket capacity. In the detailed scheduling strategy , you can change between the capacities to be finitely scheduled. o Block planning tab page, maintain blocks function If you have selected the from block planning entry under buckets on the standard capacity tab page, two new columns will be displayed in the block maintenance: In the cycle type column, a symbol specifies that a new cycle begins at the beginning of the current block. The cycle ends at the start of the next indicated block, or with the last specified block. In the overload (%) column, the factor by which the bucket capacity of the current block is increased, is displayed as the productive time in the block (see below).
Detailed scheduling strategy For block planning with buckets in SAP APO 3.1, the new scheduling mode find buckets with free capacity has been introduced in the detailed scheduling strategy. You use this mode for finite scheduling of the bucket capacity of block-planned single-mixed resources and infinite scheduling of the time-continuous capacity of all resources. If you want to finitely schedule the time-continuous capacity of a block-planned single-mixed resource (and all other resources), you use the existing find slots scheduling mode. Other finite scheduling modes are not suitable. Reconciliation of production process model and resource A prerequisite for block planning with buckets is the consistent maintenance of the resource capacity data (time-continuous capacity and bucket capacity) and the resource consumption of the activities in the production process model (PPM). In the PPM, the duration of the activity must correspond to the bucket consumption of the activity. Block planning with productive times and equivalents The absolute duration of a block on a resource is determined by the start and end date. For block-planned single resources, the absolute duration corresponds to a productive time and possibly a quantity to be produced within a block. Previously, you could create blocks only with absolute duration. In SAP APO 3.1 you can create new blocks with the productive time in seconds or an equivalent in any unit of measurement. When shifting blocks, the productive time is retained and not the absolute duration of the blocks. For the definition of equivalents to the productive time, you specify a conversion factor and the desired unit in the block maintenance. To do this, select the Conversion of the productive time tab page under Further Settings on the Interval tab page. To display the equivalent in block maintenance, select Further Settings, and set the Productive time in equivalent indicator on the Display Options tab page.
1.4.5.2 Detailed Scheduling Strategies (enhanced)

Use The strategy profile has been enhanced as follows for SAP APO 3.1, to control new and enhanced planning functions in various application areas of Production Planning and Detailed Scheduling (PP/DS): o Infinite scheduling with planning-related minimum intervals Previously, the process-related minimum intervals between activities were considered for scheduling in detailed scheduling, under consideration of time relationships. In SAP APO 3.1, infinite scheduling on
________________________________________________________________
12 SAP AG
APO 3.1 ________________________________________________________________
the basis of - larger - planning-related minimum intervals is possible for order-internal relationships. You can create a plan that allows enough space for later finite detailed scheduling. You maintain planning-related minimum intervals in the plan (production process model or iPPE). For the runtime object, the system can determine planning-related minimum intervals from routing data in SAP R/3. When planning under consideration of order-internal relationships, the system uses the planning-related minimum intervals if you have set the Use planning-related minimum intervals for infinite scheduling indicator in the detailed scheduling strategy. o Considering cross-order relationships Previously only order-internal relationships could be considered in detailed scheduling. In SAP APO 3.1 you can also consider cross-order relationships. Cross-order relationships are relevant for subcontracting, for example. This is mapped by an in-house production order in the subcontractor's plant and a stock transport order between the subcontractor's plant and your own plant. The last activity of the in-house production order and the first activity of the stock transport order are linked by a crossorder relationship. You specify if the system should consider cross-order relationships in detailed scheduling, using the cross-order relationships field in the detailed scheduling strategy. Block planning with buckets In SAP APO 3.1, you can use block planning with buckets. You can choose to finitely schedule the bucket capacity or the time-continuous capcity of single-mixed resources whose bucket capacity is derived from blocks. You specify which capacity should be finitely scheduled using the new finite capacity field in the detailed scheduling strategy. For finite scheduling of the bucket capacity there is a new finite scheduling mode find buckets with free capacity. For more information, see release information on Block Planning. Interuptability of campaigns In SAP APO 3.1 you can use the consider campaign requirements indicator in the detailed scheduling strategy to specify if the system can interupt campaigns on campaign-relevant single resources with operations that do not belong to the campaign. You specify if a single resource is campaign relevant using the campaign relevant indicator in the resource. For more information, see the release information on Campaign Planning. Restructuring of the strategy profile The strategy profile has been restructured for SAP APO 3.1, as follows: The settings that are valid for all the detailed scheduling strategies in the strategy profile are on the Cross-strategy Settings tab page.
Strategy-specific settings that are valid for planning selected objects are on the General Settings tab page. The strategy-specific settings for dependent objects are on the Strategy parameters for dependent objects tab page.
1.4.6 APO-MD-PPM Production Process Model 1.4.6.1 Detailed Scheduling Strategies (enhanced)
Use
The strategy profile has been enhanced as follows for SAP APO 3.1, to control new and enhanced planning
________________________________________________________________
SAP AG 13
APO 3.1 ________________________________________________________________
functions in various application areas of Production Planning and Detailed Scheduling (PP/DS): o Infinite scheduling with planning-related minimum intervals Previously, the process-related minimum intervals between activities were considered for scheduling in detailed scheduling, under consideration of time relationships. In SAP APO 3.1, infinite scheduling on the basis of - larger - planning-related minimum intervals is possible for order-internal relationships. You can create a plan that allows enough space for later finite detailed scheduling. You maintain planning-related minimum intervals in the plan (production process model or iPPE). For the runtime object, the system can determine planning-related minimum intervals from routing data in SAP R/3. When planning under consideration of order-internal relationships, the system uses the planning-related minimum intervals if you have set the Use planning-related minimum intervals for infinite scheduling indicator in the detailed scheduling strategy. Considering cross-order relationships Previously only order-internal relationships could be considered in detailed scheduling. In SAP APO 3.1 you can also consider cross-order relationships. Cross-order relationships are relevant for subcontracting, for example. This is mapped by an in-house production order in the subcontractor's plant and a stock transport order between the subcontractor's plant and your own plant. The last activity of the in-house production order and the first activity of the stock transport order are linked by a crossorder relationship. You specify if the system should consider cross-order relationships in detailed scheduling, using the cross-order relationships field in the detailed scheduling strategy. Block planning with buckets In SAP APO 3.1, you can use block planning with buckets. You can choose to finitely schedule the bucket capacity or the time-continuous capcity of single-mixed resources whose bucket capacity is derived from blocks. You specify which capacity should be finitely scheduled using the new finite capacity field in the detailed scheduling strategy. For finite scheduling of the bucket capacity there is a new finite scheduling mode find buckets with free capacity. For more information, see release information on Block Planning. Interuptability of campaigns In SAP APO 3.1 you can use the consider campaign requirements indicator in the detailed scheduling strategy to specify if the system can interupt campaigns on campaign-relevant single resources with operations that do not belong to the campaign. You specify if a single resource is campaign relevant using the campaign relevant indicator in the resource. For more information, see the release information on Campaign Planning. Restructuring of the strategy profile The strategy profile has been restructured for SAP APO 3.1, as follows: The settings that are valid for all the detailed scheduling strategies in the strategy profile are on the Cross-strategy Settings tab page. Strategy-specific settings that are valid for planning selected objects are on the General Settings tab page. The strategy-specific settings for dependent objects are on the Strategy parameters for dependent objects tab page.
________________________________________________________________
14 SAP AG
APO 3.1 ________________________________________________________________
1.4.6.2 SNP PPM Generation With Lot Size Margins (new)

Use
Until now, you had the option of using a generation report to generate SNP production process models (PPMs) from PP/DS PPMs for an individual lot size and to generate exactly one mode combination of a PP/DS PPM. It was then only possible to generate one SNP PPM for one mode PP/DS PPM combination per run of the generation report.
As of SAP APO 3.1, you now have the option of having the system generate SNP PPMs for lot size margins. You are also able to generate SNP PPMs for multiple mode combinations of a PP/DS PPM. To do this, the system creates one SNP PPM per PP/DS PPM mode combination. As the number of mode combinations and also the number of SNP plans will possibly become very large depending on the number of activities and alternative PP/DS plan modes, you are able to choose specific PP/DS PPM mode combinations for the SNP PPM before the report is run or enter specific parameters, such as the maximum number of mode combinations or the lowest mode priority to be included.
New Entries in the SAP APO Menu There are new entries in the SAP APO 3.1 menu for SNP PPM generation with and without lot size margins: o o o Report for generating SNP PPMs with lot size margins: Master Data -> Production Process Model -> SNP PPM Generation With Lot Size Margin Report for generating SNP PPMs without lot size margins: Master Data -> Production Process Model -> SNP PPM Generation Without Lot Size Margin Transaction for choosing mode combinations and flagging the PP/DS PPM for the next SNP PPM generation run: Master Data -> Production Process Model -> SNP PPM Generation: Define Mode Combinations Transaction for displaying the generation log: Master Data -> Production Process Model -> SNP PPM Generation: Display Log
1.4.7 APO-MD-PPE Product and Process Engineering 1.4.7.1 Action Handler (Enhanced)
Use
In SAP APO 3.0, you could choose Production Planning --> Manufacturing Execution --> Connection of the Production Control System in the SAP menu. The connection of the production control system comprised sequence transfer and the Action Handler. For SAP APO 3.1, the sequence transfer function was moved to model mix planning (APO-PPS-MMP). See the release information Modell Mix Planning: Planning Line Networks for further details. The menu option Connection of the Production Control System was changed to Action Handler, and the Action Handler received its own component APO-PPS-AHT. The following enhancements were made in the Action Handler:
________________________________________________________________
SAP AG 15
APO 3.1 ________________________________________________________________
Customizing and Master Data o New Actions The new actions allow you to carry out the following functions: o reschedule orders on alternative resources/lines within a group of alternative lines (only when iPPE is used) change the status of activities (only when iPPE is used) send SAPOffice notifications in the case of an error assign action networks to orders deallocate orders delete orders manually carry out actions for an action point display the variant configuration in production tracking carry out ATP checks for the components of an order (see also release information ATP Check in PP/DS)
Parameterization of Actions In Customizing, you can define certain parameters for an action. This makes it possible to carry out an action at different points in time with different parameter values. Parameterization, that is, the definition of parameter values, is possible in both automated and manual use of the Action Handler. Example of automatic processing with the Action Handler: You want an internal mail to be sent at two different action points. Both mails are to have different text and different recipients. Action Networks You can use action networks to represent business-related dependencies between actions. For example, you can define that a delivery note is only printed once the order has been picked. You can assign an action network to an order via an action. You use action networks for manual processing with the Action Handler. Action Points in iPPE The action points of the Action Handler have been integrated into integrated Product and Process Engineering (iPPE). In repetitive manufacturing, you can assign them to elements of the line structure, and in shop floor production, you can assign them to the mode of an activity of the process structure. Action points which have been assigned to elements of the line structure can at the same time be used as reporting points for the automatic backflush. Maintenance of Action Points and Assignment of Actions to Action Points Maintaining action points and assigning them to actions is no longer carried out in Customizing but either in iPPE (see above, transaction PPE) or in the master data of the Action Handler (transactions AHTGL01 and AHTGL02).
Automated Processing with the Action Handler In automated processing, the Action Handler automatically carries out certain actions for all planned orders as soon as the planned orders reach a certain action point during production (printing of documents, production tracking, backflush and so on). This functionality already existed in SAP APO 3.0 and has now been enhanced. The following functions are now available:
________________________________________________________________
16 SAP AG
APO 3.1 ________________________________________________________________
Archiving Tracking records, including all additional customer fields, are archived. This reduces the database content in the productive system as far as possible and improves the performance. Production Tracking in Planned Order Management (only available if iPPE is used) In planned order management, a new application in SAP APO 3.1, you can display production tracking information on planned orders (tab page Tracking Info) which you selected in the planned order overview. Improved Error Handling If errors occur during the execution of actions, you can send an express mail to the user responsible in addition to the SAPOffice mail. It is possible to implement this functionality per action point or per combination of action point and action. You can also implement user-defined error handling. In this case, the event ACTIONHANDLER_ERROR_OCCURRED is connected to the SAP Business Workflow. Instead of a mail, the person responsible then receives a work item in his SAPOffice-Mail inbox.
Manual Processing with the Action Handler In manual processing, you manually start actions with individual planned orders in order to prepare production in a controlled manner (carry out ATP check for components first, then release orders and so on). This function is new in SAP APO 3.1. o Action Handler in Planned Order Management (only available if iPPE is used). You can use planned order management, a new application for SAP APO 3.1, in order to do the following, starting from the overview screen for planned orders: view the action network for planned orders you selected and manually carry out actions from there
manually carry out standalone actions without business-related dependencies which can be started at any point of the production process for planned orders you selected (tab page Action Handler). For further details, see the release information Planned Order Management. Effects on Customizing Maintain settings for Action Handler
1.4.7.2 Introduction of Action Points (Enhanced)

Use The reporting points that were previously available in the line structure have been renamed as action points. They now include the functions of the tracking point from the action handler in the APO. You can define action points for the following node types: o o o Line network Line Line segment
You can define action points on the Action Points tab page for the above node types. You allocate functions to an action point by making the relevant entries:
________________________________________________________________
SAP AG 17
APO 3.1 ________________________________________________________________
o o
If you wish to use the action point as a reporting point, you specify a type of reporting point (as previously for reporting points). The type of reporting point controls how the backflush is to take place. If the action point is to trigger actions in the action handler (like the tracking point in the APO previously), you do not need to assign a type of reporting point. You must maintain other data for the action point, such as the actions to be done, in the APO Customizing, after the data has been transferred. If you wish to use the action point for the backflush and for the action handler in the APO, you must specify a type of reporting point and maintain the data for the action point in the APO.
1.4.7.3 Creating Multiple Work Centers (New)

Use Multiple work centers are another form of alternatives in the line structure. When you backflush and register which work center has actually been used, multiple work centers help you to determine the correct supply area from which to withdraw components. You can depict multiple work centers with production lines or line segments, for which you create alternatives. An alternative can consist of several consecutive work centers. Even if the multiple work centers themselves are not planned, the number of takts that you have maintained for the multiple work centers must be considered during scheduling. The planning itself cannot determine any alternatives, so you must specify an alternative to be the standard alternative. The standard lead path is defined over these standard alternatives, which forms the basis for planning. Procedure for Creating Multiple Work Centers The procedure is illustrated using an example with line segments: A production line consists of the line segments 1, 2, and 3. Line segment 2 is a multiple work center. It consists of two alternative work centers at which the order can be produced. 1. 2. First, you create line segment 2, and enter both alternatives in the Alternative Work Center tab. Enter descriptions for the alternatives. Indicate the standard alternative. Save your entries. You must also create both work centers as line segments, for example, line segment 2a and 2b. On the 'Relationships' tab page for each line segment, enter line segment 2 and each alternative. Save your entries. You have created a hierarchy relationship between the multiple work center (line segment 2) and the two alternatives (line segments 2a and 2b). You can maintain a sequence for line segments 1, 2 and 3 only. In this example, line segments 2a and 2b do not have predecessors/successors.
3. See also
Overview of New Functions in Line Design
________________________________________________________________
18 SAP AG
APO 3.1 ________________________________________________________________
1.4.7.4 Overview of New Functions in Line Design (Enhanced)

Use With iPPE Line Design, you can create the structure and characteristics of takt-based production lines in the system. Previously, you could use Line Design to reproduce individual production lines or a linear series of production lines only. As of Release SAP APO 3.10 you can also create complex line networks, consisting of alternatives lines, in the system. This enables you to describe the alternative paths through a line network, through which various products can run. The data is available for other applications, such as model mix planning, material staging, and backflushing. The following new line elements have been introduced to make this possible: o o o Group of alternative lines Alternative line Part of line-network
You can find more information on reproducing complex line networks under Creating Line Structures with Alternatives. You can also use multiple work centers to represent alternative paths through a line network. A multiple work center represents a group of work centers at which exactly the same work is carried out. You include a multiple work center in a line structure if you have alternative work centers on a production line, which receive supplies from different supply areas. An order can be processed at either one of the work centers. You specify which work center has been used when you backflush. You can find more information under Creating Multiple Work Centers. The following new functions and enhancements are also available: o New line elements to improve structuring within a line structure: o o Line area Intermediate buffer
Introduction of action points Connection to control cycle maintenance There is a tab page for maintaining control cycles when you maintain line elements. For more information, see Mass Maintenance of Control Cycles. Discontinuation of line resources in the DI system Previously, you had to create a line resource in the DI system and assign it to the line node. As of this Release, line resources are automatically generated from line nodes when iPPE data is transferred into the APO. Der APO adopts the name, which you specify in the basic data for the production line in the Line Resource , and the plant. You must complete data that is relevant for planning manually in the APO, such as the production rate, shift sequence, and so on.
Effects on Existing Data After upgrading, you can no longer display line resources that you have created in the DI System. However, an XPRA conversion ensures that these resources remain available as line resources in the APO.
________________________________________________________________
SAP AG 19
APO 3.1 ________________________________________________________________
Effects on Customizing The activity Define Line-Specific Relationship Subtypes has been added to iPPE Customizing in the Line Design Area. The Customizing entries for these new types have already been made.
1.4.7.5 Creating Line Structures with Alternatives (new)

Use As of Release SAP APO 3.10, you can create line networks, which consist of several production lines that can be used as alternatives to each other. Various products can run along these production lines. You can depict the possible routes for each product. Two new elements have been added to the line network to make this possible: o Group of alternative lines Sometimes a product can be produced on several production lines that have the same function, and not just on one line. During planning, you must be able to state which alternative lines are to be used to produce a particular product. You can use the new node type, the group of alternative lines, to group together alternative lines. This node type enables you to manually reschedule an order from one line to an alternative line in interactive sequence planning. Part of line network Several products can be produced in a line network. They run partly along the same production lines or groups of alternative lines. You must be able to view the situation on all the production lines to be able to implement a correct model mix planning for all the products that share a line network. The line network is now a cross-product line network. The part of line network has been introduced to help you identify which parts of the line network a product can run along. You create a part of line network as an alternative in the line network and select which production lines are to belong to it.
Example
A line network consists of body shop, paintwork, and final assembly. The body shop consists of two production lines, body shop 1 and body shop 2. These two production lines can be used as alternatives to each other. The final assembly also consists of three final assembly production lines, which can be used alternatively. There is only one production line for the paint work, which receives parts from both of the body shop production lines. All of the production lines are divided into line segments. The procedure for creating this line structure would be as follows: 1. You create the necessary line elements: Group of alternative lines 'body shop' Group of alternative lines 'final assembly' Line 'paintwork' Line 'body shop 1' Line 'body shop 2' Line 'final assembly 1' Line 'final assembly 2'
________________________________________________________________
20 SAP AG
APO 3.1 ________________________________________________________________
2.
Line 'final assembly 3' All the subordinate line segments.
You create the alternatives. On the 'Alternative Lines' tab page for the group of alternative lines 'body shop', enter both the production lines 'body shop 1' and 'body shop 2'. Do the same for the group of alternative lines 'final assembly'. You maintain the hierarchy relationships as follows: Enter the line network on the 'Relationships' tab page for the groups of alternative lines. You assign line segments to the lines in the same way. On the 'Part of Line Network' tab page for the line network, you create the alternatives 1 and 2, with a description of your choice. Save your entries. Double click on the part of line network 1 in the structure tree. A list of the lines and buffers in the line network is displayed. Select a line and a buffer, if applicable. Maintain sequences (predecessor/successor relationships) between elements that are assigned to the same higher-level element.
3.
4.
5.
1.4.7.6 iPPE Production Resource (New)

Use In the iPPE Workbench, specific objects are available in the factory layout for depicting production resources. You can differentiate between operating facilities and workers. Operating facilities are all technical resources that are required for completing set work tasks. Production resources and tools, like those in classical routings, are included in this group. In iPPE, operating materials can be materials or documents. Materials can be tools or larger machines, which are available for producing a product in a specific plant (such as torque wrenches). If there are several of the same tool available in one plant, you only need to create the operating facility once and enter the relevant quantity. You can use documents to depict operational method sheets, for example. Workers are people who are available for a defined period of time to complete work. They are represented by production resources of the type 'workers' in iPPE. You must assign a worker to a specific plant and maintain the relevant data in iPPE. You assign production resources to a mode or the relevant elements in the factory layout. Capacity planning is possible for both resource types.
1.4.7.7 New Functions in the iPPE Process Structure (Enhanced)

Use Within Integrated Product and Process Engineering (iPPE), you can use the process structure to create your routing data in the system. In Release SAP APO 3.10, you can use the process structure to fully reproduce
________________________________________________________________
SAP AG 21
APO 3.1 ________________________________________________________________
your production and assembly processes on takt-based production lines. As of this Release, the process structure is linked to Product Cost Controlling. This enables you to make complete cost estimates for products for which you maintain production master data in iPPE. The following new functions and enhancements are available for the process structure as of Release SAP APO 3.10: o o o o o Improvement of multi-level structuring and multiple use of substructures. Replacement of the APO resource with the iPPE production resource Introduction of the activity type to differentiate between assembly activities and setup activites in the header data of the activities. New detail screens for maintaining modes. Clear application lists for assigning components and line elements quickly.
These developments are described in detail below: Improvement of multi-level structuring and use of substructures. Previously, you could create sequences between activities to define the order of individual activities only. This restricted the multiple use of structures below a grouping activity or below an operation. In the new Release you can also specify the order of grouping activities and operations. This means you can use this node type for representing multi-level structures, and also for multiple use similar to standard routings. The following rules apply when you set sequence relationships: o o Within one hierarchy level in a process structure you can maintain a sequence between nodes of the same type only. This means you cannot maintain a sequence between an activity and an operation. The nodes must be assigned to the same higher-level node. For example, you can maintain a sequence only for activities that are assigned to the same grouping activity.
You can use the following functions and evaluations maintaining sequences: o Predecessor-Successor Maintenance tab page You can maintain a predecessor or successor for each element in a process structure that is assigned to a higher-level object. The predecessor/successor must be assigned to the same higher-level object. Sequences of Subordinate Objects tab page On this tab page you can specify the sequence of all assigned objects in one step. For example, for grouping activities you can specify the sequence of all the assigned activities. This sequence is automatically transferred into all the process structures in which the grouping activity is used. Overview of Relationships tab page On the Overview of Relationships tab page you can call up the Hierarchy Overview and Activity Sequence evaluations. These overviews are particularly useful for routing plan headers or grouping activities on the highest hierarchy level. For multi-level structures, you are shown the sequence of individual objects on each hierarchy level. The activity sequence shows the sequence of all assigned activities. For example, if you call up the activity sequence for a routing plan header, the system explodes the complete process structure and calculates the order of all the activities that are usually on the lowest hierarchy level.
New detail screens for maintaining modes Several detail screens are available for maintaining modes:
________________________________________________________________
22 SAP AG
APO 3.1 ________________________________________________________________
Mode tab page This detail screen contains the most important mode data, such as plant, primary resource, duration, standard value determination type, time analysis data. The Fixed and Variable Duration fields no longer exist. They have been replaced with the Duration field. The system interprets this field as a fixed or variable duration depending on the activity type. You can create a production resource directly from the primary resource field and assign it to the mode. At the same time, you can specify whether the production resource is of type worker or of type operating facility. If you wish to carry out capacity requirements planning in the APO for employees, you must use the type 'worker'. If you wish to plan the use of operating facilities, you must use the type 'operating facilities'. The primary resource also establishes a link to the cost center and activity type, which form the basis for product cost controlling. Secondary Resources tab page On this detail screen you can assign more capacity requirements in the form of production resources to the mode, such as important production resources and tools. Costing Data tab page On this detail screen you can assign costing data that you have already created for production activities, or create new data, such as cost element, costs for a unit of measure, and so on. Line Assignment tab page On this tab you assign a line element to the mode, which shows where this mode is to be carried out. This enables you, at an early stage, to determine a relationship between the mode of an activity and the place it is to be carried out, without having to create a line balance.
Application Lists With the Product-Process Assignment list, you can check whether the component variants (components), which you have created in the product structure, have already been assigned to the corresponding activities. You can assign nodes and variants, which have not yet been assigned, to the relevant activities using drag & drop. With the Line Assignment list, you can check whether you have already assigned the mode of an activity to line elements in a line structure. You can also use this list to assign a line, by loading the process structure into the navigation area and assigning the line segment to the relevant mode using drag & drop. Effects on Existing Data Since the Fixed and Variable Duration fields no longer exist for the mode and have been replaced with the Duration field, you must take note of the following if you have already maintained activities in the previous Release: o Activities for which you have maintained a variable duration are converted into activities of Activity Type Assembly. The variable duration is transferred to the Duration field and handled by the system as such. Activities for which you have maintained a fixed duration in the mode are converted into activities of Activity Type Setup. The fixed duration is transferred to the Duration field and handled by the system as such. If you have maintained both a fixed and variable duration in a mode, the activity is converted into an assembly activity and only the variable duration is transferred. The fixed duration remains available in the the database only. It is not displayed, nor is it used for planning.
________________________________________________________________
SAP AG 23
APO 3.1 ________________________________________________________________
Effects on Customizing The IMG activity Define Standard Value Determination Type has been added to iPPE Customizing.
1.4.7.8 iPPE Actions for Upgrading to SAP APO 3.1 (New)

Use For SAP APO 3.1, changes have been made to the way you maintain data for color nodes and color variants. To ensure that existing data in this area remains available after the upgrade, you must call up and run the report PPEPVCOL2PCOLMR. Effects on Existing Data This report creates a master record in the new table PCOLMR for color keys that have already been maintained in color variants.
1.4.7.9 Shop Floor Production in Integrated Product and Process Engi (iPPE)
Use For Release SAP APO 3.10, new functions for shop floor production have been added to the ones that were already available for manufacturing in a line-based production environment. The objects that already existed for depicting line-based production environments in iPPE are now qualified with the term 'line'. A new type of routing has been added to the process structure for use in shop floor production and has the following 4 objects: o o o o Routing header (technical name: S_PPMHD) Subrouting (technical name: S_PPMVW) Operation (technical name: S_PPMSTO) Activity (technical name: S_PPMACT)
These 4 objects are maintained without being linked to a line structure. In shop floor production, the system determines the sequence in which the individual activities are to take place from the relationships between the activities, which you define in the process structure. The routing header groups together all the objects belonging to a routing. The subrouting groups together operations and activities. All objects of the same type can be linked using sequence relationships, as long as they are all assigned to the same higher-level object. Operations and activities can also be linked to one another. o Assigning Supply Areas You assign supply areas on a new tab page in the data for an activity. You can enter a standard supply area for each activity, which is then valid for all component variants and structure nodes assigned to that activity. You can also enter different supply areas for exceptional combinations of modi and variants from the product structure. Reporting Points
________________________________________________________________
24 SAP AG
APO 3.1 ________________________________________________________________
Reporting points are used for backflushing and are maintained for the mode/modi of each activity. When one mode of an activity has a reporting point, the other modi must also be assigned a reporting point. The reporting point type must be the same for all modi of an activity, which is why you maintain reporting points in the data for the activity. o New Fields for Shop Floor Production Several new fields, such as mode linkage and setup group/key, have been added for activities, to enable you to use the functions for planning and scheduling that are available in the APO. The fields for the setup group and setup key are positioned at the setup activity. You enter setup keys in the DI system and they are transferred as attributes via the CIF.
Effects on Customizing You define node types for shop floor production in the IMG activity, Define Specific Node Types for Process Structure.
1.4.7.10 Enhancements and New Functions in the iPPE Product Structure Workbench (Enhanced)
Use o Copying single objects and structures You can copy existing nodes, variants, alternatives, and relationships. The copying function can be used for single objects and for complete application structures (product structure, process structure, factory layout). The assignment relationships that link the applications together are also copied. The user can decide whether attributes, such as the class assignment, assigned materials, or size data, are to be considered when copying. Linking iPPE to Product Cost Controlling and Cost Object Controlling iPPE is connected to Product Cost Controlling and Cost Object Controlling. This means that you can use the following cost estimates based on iPPE data: Cost estimates without reference to an order (product costing and mixed costing), preliminary costing for product cost collectors Sales order cost estimates
Costing runs can select and cost materials with BOMs, as well as materials that have a product structure in iPPE. You can also plan assembly scrap. The iPPE production resource esablishes the link between iPPE and Overhead Cost Controlling. You can find more information under: Overview of Cost Management in the Automotive System Connection of iPPE to Product Cost Controlling Cost Estimates for Objects with iPPE Master Data Concurrent Costing o Distribution iPPE objects from all applications (product structure, process structure, factory layout, line balance, and iPPE resources) can be distributed to other DI systems through ALE (Application Link Enabling) using an all-inclusive BOR (Business Object Repository) object. Using a BOR object and the corresponding message type avoids serialization problems.
________________________________________________________________
SAP AG 25
APO 3.1 ________________________________________________________________
Accessing the iPPE Workbench You no longer use a dialog box to call up or search for objects from iPPE or from the PLM environment. Instead, you use the loading area in the iPPE Workbench, which is immediately displayed when you call up the Workbench. In addition to the navigation area, there is also the Reports tab page, which contains all the evaluations that exist for the iPPE object. See also: Define Reports for the Report Tree Colors In material master maintenance, you can enter color specifications for a component with reference to the material master for color-neutral components. When you maintain color variants and use color nodes at component variants in the PVS, the system checks whether material masters exist for the colored materials. The system displays a list showing which colored materials exist and which do not. You can maintain color keys from the Workbench via the Environment menu. All color supplement keys and their descriptions can be seen there. Engineering Change Management for Relationships You can now use change numbers for relationships in the product structure. This means you can manage structures from the product structure historically.
1.5 APO-SNP Supply Network Planning (SNP)

1.5.1 Conversion of SNP orders into PP/DS orders (enhanced)
Use
When planning, you can use Supply Network Planning (SNP) together with Production Planning and Detailed Scheduling (PP/DS). You use SNP for medium to long-term aggregated planning. Here, you can determine the sources of supply (external procurement or production) that are optimal from a cost point of view (for example, external procurement costs or storage costs. You use PP/DS for detailed scheduling and optimization of dates, resource assignment and the sequence of in-house production orders, for example. If you want to base the PP/DS planning on SNP planning, you convert the SNP orders into PP/DS orders. To improve integration between SNP and PP/DS, the conversion function has been enhanced for SAP APO 3.1. For example, the enhancements support a scenario in which SNP has the planning control, and can specify the lot sizes, sources of supply and - for in-house production - production alternatives (mode selection) for production planning; PP/DS is only used to create complete PP/DS planned orders from SNP planned orders - in general only the most important components are planned in SNP - and to create a sequence of orders with detailed dates. In such a scenario, requirements planning only a task in SNP, that is, PP/DS orders are created for the products only through the conversion of SNP orders.) Planning horizons and conversion horizons Previously, the areas of responsibility of SNP and PP/DS were only separated by one horizon, the production horizon: Within the production horizon, PP/DS heuristics were used for planning, and outside the production horizon SNP was used. SNP or Capable-To-Match planning (CTM) orders could be converted into PP/DS orders, for which the start date of the first activity was within the production horizon. By specifying an offset, you could extend the conversion horizon and also convert SNP/CTM orders that
________________________________________________________________
26 SAP AG
APO 3.1 ________________________________________________________________
began later. In SAP APO 3.1 a horizon has been introduced that is specific to PP/DS - PP/DS horizon - in which you can plan using PP/DS heuristics. The conversion horizon is now determined by the PP/DS horizon and the offset. The horizon previously called the production horizon is now only relevant for SNP and has thus been renamed the SNP production horizon; SNP can only plan production outside this horizon. If you define overlapping horizons, that is, if the SNP production horizon is shorter than the PP/DS horizon, then SNP and PP/DS will have the same planning area. When using mixed resources, in SNP you can consider the resources loaded by PP/DS orders and adjust the planning in the shared planning area to the current PP/DS planning. If you are using reconciled plans (production process models, iPPE plans and runtime objects) in SNP and PP/DS, with suitable conversion parameters, you can integrate SNP planning seamlessly into PP/DS planning. You specify the PP/DS horizon and the SNP production horizon in the location product master. In the planning version you can specify a default PP/DS horizon that is used by the system if no PP/DS horizon is specified in the location product master. In the event of an upgrade, the system automatically transfers the value of the (SNP) production horizon into the new PP/DS horizon. Adjusting the conversion horizon to the SNP time buckets profile If the end of the conversion horizon is in the middle of an SNP planning period, not all SNP/CTM orders in this period will be converted into PP/DS orders. This may be undesirable. In SAP APO 3.1, the system can automatically extend the conversion horizon to the end of the SNP planning period in which the end of the conversion horizon lies. The system converts all SNP/CTM orders in this period. Order types to be converted In the new order type field, you specify which SNP orders the system should convert into PP/DS orders. This field replaces the ATP category and convert time-continuous CTM orders fields, with which the order types to be converted were previously defined. Lot sizes of PP/DS orders For the conversion of in-house production orders, the system has to determine the lot sizes of the PP/DS orders. Previously, you had the following options: o o The system converts an SNP/CTM order into a PP/DS order with the same quantity. The system determines the lot sizes according to the lot size settings in the location product master and creates corresponding PP/DS orders.
You specified which option the system should use using the lot size determination indicator. In SAP APO 3.1 there is a further option with which the system can determine the lot sizes from the lot size interval in the PP/DS plan (PPM, iPPE Plan or runtime object); in the PP/DS plan, you define the lot size interval by entering a minimum lot size and a maximum lot size. The lot sizes created by the system for PP/DS orders depend on the quantity of the SNP/CTM order, as follows: 1. The quantity of the SNP/CTM order is less than the minimum lot size. Here, the system automatically rounds the minimum lot size up and creates a PP/DS order with this quantity. The quantity of the SNP/CTM order is between the minimum and maximum lot size. Here, the system creates a PP/DS order that has the same quantity as the SNP/CTM order. The quantity of the SNP/CTM order is greater than the maximum lot size. Here, the system splits the quantity of the SNP/CTM order into partial quantities, the same size as the
2. 3.
________________________________________________________________
SAP AG 27
APO 3.1 ________________________________________________________________
maximum lot size, and creates planned orders for these lot sizes. The system determines a lot size for the remaining quantity according to rules 1) and 2) and creates a planned order with this lot size. In the new lot size field, that replaces the old lot size determination indicator, you specify which lot size option the system should use. Note: As of SAP APO 3.1, the system can create an SNP PPM with a lot size interval the same as the lot size interval that you have already defined for the PP/DS PPM. For more information, see the release information on Creating SNP PPMs. Mode selection Previously, you were also able to specify that, for conversion of PP/DS planned orders, the system should use the PP/DS PPM that is entered in the SNP PPM. If different modes were assigned to the operations in the PP/DS PPM and so that different production alternatives could be modelled, the system automatically executed mode selection when creating the PP/DS planning orders. In SAP APO 3.1 SNP can specify not only the PPM for PP/DS, but also the mode selection. A prerequisite is that you have created corresponding SNP PPMs from a PP/DS PPM that allows different mode combinations. You do this using the generation report for the SNP PPM. For more information, see the release information on Generating SNP PPMs from PP/DS PPMs. Order status of the PP/DS orders Previously, you could specify that the PP/DS orders should have the status output fixed. In SAP APO 3.1 you can now also specify that the system should set the conversion indicator for the PP/DS orders, for conversion in the active planning version 000; a planned order or purchase requisition, for which the conversion indicator is set, will be converted into a production order or a purchase order immediately after transfer to the SAP R/3 system. Before setting the conversion indicator, the system can execute a conversion check. For more information, see the release information on Checks with Order Opening. Conversion mode In the conversion mode field you could previously specify if the system should plan components or stock transport requiremenets of the newly created PP/DS orders. In SAP APO 3.1 the conversion mode field has been removed; the system plans the components and stock transport requirements according to the planning procedure specified in the location product master. For more information, see the release information on PP Planning Procedure. Displaying orders to be converted You can now use the display selection indicator to specify that the system should display the SNP/CTM orders to be converted. In the display you can start the conversion specifically for selected orders. See also Release Information o o Creating SNP PPMs from PP/DS PPMs Cross-Period Lot Sizes
________________________________________________________________
28 SAP AG
APO 3.1 ________________________________________________________________
1.5.2 APO-SNP-BF Basic Functions 1.5.2.1 SNP PPM Generation With Lot Size Margins (new)
Use
1.5.3 APO-SNP-INS Interactive SNP 1.5.3.1 Cross-Period Lot Size Planning (new)
Use
As of SAP APO 3.1 you are able to run cross-period lot size planning as part of campaign planning within Supply Network Planning (SNP) as a lower level of actual campaign creation within Production Planning and Detailed Scheduling (PP/DS). In some industry sectors (such as the process industry) setup activities have a great influence on lot size planning. If the setup costs are relatively high in comparison to the storage costs, orders are grouped into large lots, to save on set up costs. Until now, however, the SNP optimizer was only able to plan lot sizes that
________________________________________________________________
SAP AG 29
APO 3.1 ________________________________________________________________
were limited to one bucket. Here, the optimizer would schedule one setup activity in each period and would calculate the specified setup consumption and setup costs in the appropriate production process model (PPM). As of SAP APO 3.1, the SNP optimizer is also able to plan cross-period lot sizes. Here, if the same production process model (PPM) is being used to produce a product in the current period, the optimizer takes into account the setup statuses from the previous period. This means that the optimizer still only schedules one setup operation per lot size. The system then calculates the setup costs and setup consumptions (fixed resource consumption and material consumption) that were defined in the PPM for resources that have been marked with the Cross-Period Lot Size indicator. The optimizer is also able to take into account setup statuses that result from already planned PP/DS orders. Campaign Planning - The Process In campaign planning within Supply Network Planning, you are also able to execute rough-cut planning. For example, you could define a business process for the process industry in such a way that a cross-network planning is only run using the SNP optimizer once the forecast data has been transferred from Demand Planning to SNP. For long setup times, it is a good idea to have a rolling monthly planning. The SNP planned orders created by the SNP optimizer correspond to a campaign that is created at a later point in Production Planning and Detailed Scheduling. The SNP planned orders are then converted into (multiple) PP/DS orders. In PP/DS, you then create the actual campaigns (detailed scheduling) for the individual production levels. Here, in order to produce a consistent plan, it is possible to re-run the SNP optimizer on a production level after each campaign is created. See also release information on planning of production campaigns in PP/DS. Automatic Generation of SNP PPMs from PP/DS PPMs As of SAP APO 3.1 it is also possible for you to have the system generate SNP PPMs for lot size margins, as cross-period lot size planning requirements in SNP are supported. See also release information on SNP PPM generation with lot size margins.
Effects on Customizing In Customizing for Supply Network Planning, which you find by following menu path: SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Supply Network Planning (SNP)-> Profiles -> Define SNP Optimizer Profiles, in addition to the SNP optimization run settings, you must also maintain the field Cross-Period Lot Size Planning and, if required, also activate the Cross-Period Lot Size Planning indicator. You must also choose the discrete optimization method. For more information, see the IMG documentation define SNP optimizer profiles and the appropriate F1 field-level help.
1.5.3.2 New Design of the SNP Optimizer Profile and SNP Optimizer Wi (enhanced)
Use As of SAP APO 3.1, the user interface design of both the SNP optimizer profile and the optimizer window in
________________________________________________________________
30 SAP AG
APO 3.1 ________________________________________________________________
interactive SNP planning is clearer and more user-friendly. There are also new functions and settings available. SNP Optimizer Profile The possible SNP optimizer profile settings have now been divided into several tab pages to provide a clearer layout. This means there is now a clear distinction between linear optimization methods and discrete optimization methods for you to choose between. In the header data of the profile you first choose one of the methods. You are then able to activate the constraints for linear and discrete optimization on two separate tab pages, and on additional tab pages you choose model parameters, solution methods, and so on. Options that are unavailable for the method you have chosen are grayed out. The SNP optimizer profile also has the following new functions and settings: o Safety stock (which until now could only be set in master data): You are able to define whether you want the optimizer to take safety stock into account. If you do want it to, you are then able to specify whether you want the penalty costs calculation to include deviations from the safety stock as an absolute value or as a percentage. Shelf life (which until now could only be set in master data): You are able to define whether you want the optimizer to take into account the shelf life of products, and if so, whether you want to continue using the product after it has expired (has passed its shelf life), or whether you want to dispose of it. If you do want to continue using it, you have the option of specifying whether you want to optimizer to use the procurement costs that have been maintained for the location product as penalty costs, or whether you want it to use penalty costs that are not dependent on the product. Fixed material consumption: If you have chosen discrete optimization methods, you are able to define whether you want the optimizer to take into account fixed material consumption in the production process model (PPM). Stock on hand: You are able to define whether you want the optimizer to calculate the stock on hand on the basis of the average stock on hand or on the basis of the stock that is on hand at the end of the period. Heuristic start solution: If you want to find an initial valid solution quickly, you are able to specify that you want the system to start running a heuristic that does not use linear programming. Lot size planning: You are able to define whether, as part of lot size planning, you want the optimizer to take cross-period lot sizes into account and how you want it to process setup statuses (see also the release information on cross-period lot size planning). Discretization horizon: You are now able to specify whether you want the system to consider discrete constraints for all time buckets (days, weeks, and so on, as defined in the planning buckets profile), or a concrete horizon that you define independently of the planning bucket profile. Optimizer Window in Interactive SNP Planning The window of the SNP Optimizer that you access from interactive SNP Planning, has also been given a more user-friendly design. The following new display options are available: o o New tab page Message log: This tab page displays messages from the previous optimization runs. Before now, this function was only accessible from the Optimizer Log Data transaction. The Optimization tab page now displays information on interim solutions during the optimization run.
o o
________________________________________________________________
SAP AG 31
APO 3.1 ________________________________________________________________
See also
IMG activity documentation define SNP optimizer profiles.
1.5.4 APO-SNP-SCH SNP Scheduling Agreement Processing 1.5.4.1 Scheduling Agreement Processing in Supply Network Planning (
Use
As of SAP APO 3.1, scheduling agreements are also going to be included for product procurement as part of heuristic-based planning in Supply Network Planning. By considering scheduling agreements you will be able to improve collaboration with your vendors. As the vendors will be better informed of demand times and demand quantities, processing time can be reduced. You can also use vendor-confirmed quantities within your planning as maximum vendor capacities. Scheduling Agreement Processing - The Process Scheduling agreements that were created in an OLTP system and transferred to the APO system through a CIF interface are taken into account by the SNP heuristic as possible sources of supply. During the planning run, the system creates schedule lines for the scheduling agreements. You are then able to generate manual or automatic scheduling agreement releases based on these schedule lines and transmit them to the vendor. After the vendor has notified you of his capacity using confirmations (that can also be automatically transferred to the OLTP system as scheduling agreement schedule lines), you can, if required, use these as maximum capacities during rescheduling (especially when the vendor's capacity is below your delivery schedule quantity). By doing this, you are also able to restrict the maximum vendor capacity for specific means of transport within a transportation lane. New Planning Books and Data Views Within interactive planning in Supply Network Planning for heuristic-based planning using scheduling agreements, there is a new planning book (9ASA) and data view (SA(1)) available (APO Easy Access Menu -> Supply Network Planning -> Planning -> Scheduling Agreements (Procurement) -> Scheduling Agreements Interactive). This function has also been enhanced to execute the SNP heuristic in the background with new options for including the maximum vendor capacity. An additional planning book has also been created within collaborative procurement for collaboration with vendors over the internet, (9ASAS; APO Easy Access Menu -> Supply Network Planning -> Planning -> Collaborative Supply Planning). Restrictions The SNP heuristic does not take into account scheduling agreements for the procurement types, subcontracting and stock transfer. Types demand scheduling agreement are not included in SNP planning either.
________________________________________________________________
32 SAP AG
APO 3.1 ________________________________________________________________
In addition to this, scheduling agreements in SNP are only included in active model versions.
1.5.5 APO-SNP-CTM Capable-To-Match 1.5.5.1 Descriptive Characteristics for Use in Order LiveCache
Use Before Release 3.1 product and location were the only characteristics that could be transferred from Demand Planning to SNP and Production Planning /Detailed Scheduling (PP/DS). As of this release it is possible to define descriptive characteristics for use in applications that use Order LiveCache . These characteristics permit more detailed planning in several applications. The following functions are affected:
o -
Demand Planning Release of Unconstrained Demand from DP to Order LiveCache This process transports the descriptive characteristics with their values from DP to order LiveCache. This enables you to release data at any characteristic level. Note that descriptive characteristics are then only added to the independent requirements that are generated. Release of Constrained Forecast from Order LiveCache back to DP
This process recognizes the characteristics attached to the LiveCache order and transports the constrained forecast back to DP with the same characteristic values.
o -
CTM Demand Prioritization

It is possible to assign prioirities based on descriptive characteristics. For example you can specify that one customer or customer group is given preferential treatment if the demand cannot be completetly satisfied.
Rule Application
Currently rules can be found for a few attributes of the forecast (product, location, category). With descriptive characteristics it is possible to perform the rule finding process on any characteristic level in DP. For example including the customer in the descriptive characteristics enables the identification of customer specific rules for the same location/product forecasts.
________________________________________________________________
SAP AG 33
APO 3.1 ________________________________________________________________
Effects on Customizing
To specify that a DP characteristic is to be used as a descriptive characteristic in Order LiveCache, you assign it to a consumption group. In the consumption group you link the DP chararcteristic with a field in the ATP field catalog. You enter the consumption group in various objects or transactions, for example the location product, the release profile, or the demand profile.
You maintain consumption groups in Customizing for Demand Planning under SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Demand Planning -> Basic Settings -> Maintain Consumption Group. If you use fields that have been assigned to descriptive characteristics and want to use special sorting in CTM Demand Prioritization, you specify the priorities in Customizing under SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Supply Network Planning (SNP) -> Capable-to-Match (CTM) -> Demand Prioritization -> Maintain Special Sorting or Maintain Special Sorting of Descriptive Characteristics. Read these two IMG topics for information on which activity to use.
1.6 APO-FCS Demand Planning

1.6.1 Sales Order Oriented Planning
Use
This process combines the advantages of a make-to-stock startegy, that is that you can forecast future demand using various staistical methods, with those of a make-to-order startategy, in that only the quantity that customers actually require is produced.
The consumption of the forecast by orders has been extended in Release 3.1. It i s now possible to consume the forecast demand by sales orders at customer level. This function makes use of descriptive characteristics (described in more detail in release note Descriptive Characteristics).
Demand is planned in Demand Planning, using a characteristic for the customer. This characteristic has previously been assigned to a field from the ATP field catalog in a consumption group. The demand plan is released to order LiveCache.
Only those planned orders for which a sales order exist can be converted to production orders or purchase requisitions. In the requirements ascertainment period, the customer is asked to confirm their requirements in the form of purchase orders, which are entered in R/3 as sales orders. The sales orders are transferred via the core
________________________________________________________________
34 SAP AG
APO 3.1 ________________________________________________________________
interface to the APO system where they consume the forecast. In PP/DS two heuristics can be used: 1. 2. The first heuristic finds planned independent requirements for a customer that have not been consumed or only partially consumed by sales orders for the same customer. After the requirements ascertainment period has expired, the planned independent requirements, planned orders as well as the secondary requirements and planned orders that are not covered by sales orders are removed from the system. There are two variants of this heuristic. The program starts at the product level The program starts at any component level
The planned orders for which sales orders exist can now be converted to production orders/purchase requisitions. Conversion block: To prevent planned orders for which no sales orders exist being converted to production orders or purchase requisitions, you enter a conversion rule in the product master data. You maintain conversion rules in Customizing for PP/DS, see Maintain Conversion Rules. However it is possible to give particular users authorization to overwrite the conversion rule, that is to convert planned orders that do not have a relevant sales order. For more information, see Role-specific overriding of a conversion check in the interactive planning In the role that you assign to a user, you can determine whether the user can execute the set conversion indicator in the interactive planning, or execute the conversion in the interactive order transfer / conversion, even if an error appears in the conversion check. You can define the corresponding authorizations in the role maintenance, using the authorization object for the location product APO: PP/DS, Location product (C_APO_MALO) and the authorization field Functions in PP/DS (APO_PPFUNC). You can issue authorizations for overriding the standard checks by specifying the following values for the functions in PP/DS: ATP Check SAP_CNV_ATP_CHECK Requirements Check Customer-Specific Check SAP_CNV_MAKE_TO_ORDER defined by the customers
As default, SAP delivers the PP/DS roles with authorization for overriding the checks (authorization value *). Note: In the background processing, if an error appears, the system does generally not execute the conversion indicator or the transfer and conversion, independent of the authorization..
1.6.2 Descriptive Characteristics for Use in Order LiveCache

Use Before Release 3.1 product and location were the only characteristics that could be transferred from Demand Planning to SNP and Production Planning /Detailed Scheduling (PP/DS). As of this release it is possible to define descriptive characteristics for use in applications that use Order LiveCache . These characteristics permit more detailed planning in several applications. The following functions are affected: o Demand Planning
________________________________________________________________
SAP AG 35
APO 3.1 ________________________________________________________________
Release of Unconstrained Demand from DP to Order LiveCache This process transports the descriptive characteristics with their values from DP to order LiveCache. This enables you to release data at any characteristic level. Note that descriptive characteristics are then only added to the independent requirements that are generated.
Release of Constrained Forecast from Order LiveCache back to DP This process recognizes the characteristics attached to the LiveCache order and transports the constrained forecast back to DP with the same characteristic values.
o -
CTM Demand Prioritization It is possible to assign prioirities based on descriptive characteristics. For example you can specify that one customer or customer group is given preferential treatment if the demand cannot be completetly satisfied. Rule Application Currently rules can be found for a few attributes of the forecast (product, location, category). With descriptive characteristics it is possible to perform the rule finding process on any characteristic level in DP. For example including the customer in the descriptive characteristics enables the identification of customer specific rules for the same location/product forecasts.
Effects on Customizing To specify that a DP characteristic is to be used as a descriptive characteristic in Order LiveCache, you assign it to a consumption group. In the consumption group you link the DP chararcteristic with a field in the ATP field catalog. You enter the consumption group in various objects or transactions, for example the location product, the release profile, or the demand profile. You maintain consumption groups in Customizing for Demand Planning under SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Demand Planning -> Basic Settings -> Maintain Consumption Group. If you use fields that have been assigned to descriptive characteristics and want to use special sorting in CTM Demand Prioritization, you specify the priorities in Customizing under SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Supply Network Planning (SNP) -> Capable-to-Match
________________________________________________________________
36 SAP AG
APO 3.1 ________________________________________________________________
(CTM) -> Demand Prioritization -> Maintain Special Sorting or Maintain Special Sorting of Descriptive Characteristics. Read these two IMG topics for information on which activity to use.
1.7 APO-PPS Production Planning and Detailed Sch

1.7.1 Recreation of Receipt Elements
Use
As of SAP APO 3.1, you can use this function within Capable-To-Promise (CTP) or a multilevel ATP check. This function enables receipt elements that have been created within CTP or a multilevel ATP check to be deleted before a new ATP check. A possible earlier requested delivery date, for example, can therefore be returned to planning. This function is only supported for make-to-order production.
Customizing has been enhanced for the function. In the work step Maintain Check Instructions, you can set the indicator Re-create receipt elements. In the location-specific product master (ATP tab), you can define a horizon for re-creating receipt elements.
See also
Release information Multilevel ATP check Release information Conversion of ATP tree structures into Procurement Proposals of PP/DS For detailed information see the online documentation.
1.7.2 Sales Order Oriented Planning

Use
This process combines the advantages of a make-to-stock startegy, that is that you can forecast future demand using various staistical methods, with those of a make-to-order startategy, in that only the quantity that customers actually require is produced.
The consumption of the forecast by orders has been extended in Release 3.1. It i s now possible to consume the forecast demand by sales orders at customer level. This function makes use of descriptive characteristics (described in more detail in release note Descriptive Characteristics).
________________________________________________________________
SAP AG 37
APO 3.1 ________________________________________________________________
Demand is planned in Demand Planning, using a characteristic for the customer. This characteristic has previously been assigned to a field from the ATP field catalog in a consumption group. The demand plan is released to order LiveCache. Only those planned orders for which a sales order exist can be converted to production orders or purchase requisitions. In the requirements ascertainment period, the customer is asked to confirm their requirements in the form of purchase orders, which are entered in R/3 as sales orders. The sales orders are transferred via the core interface to the APO system where they consume the forecast. In PP/DS two heuristics can be used: 1. 2. The first heuristic finds planned independent requirements for a customer that have not been consumed or only partially consumed by sales orders for the same customer. After the requirements ascertainment period has expired, the planned independent requirements, planned orders as well as the secondary requirements and planned orders that are not covered by sales orders are removed from the system. There are two variants of this heuristic. The program starts at the product level The program starts at any component level
The planned orders for which sales orders exist can now be converted to production orders/purchase requisitions. Conversion block: To prevent planned orders for which no sales orders exist being converted to production orders or purchase requisitions, you enter a conversion rule in the product master data. You maintain conversion rules in Customizing for PP/DS, see Maintain Conversion Rules. However it is possible to give particular users authorization to overwrite the conversion rule, that is to convert planned orders that do not have a relevant sales order. For more information, see Role-specific overriding of a conversion check in the interactive planning In the role that you assign to a user, you can determine whether the user can execute the set conversion indicator in the interactive planning, or execute the conversion in the interactive order transfer / conversion, even if an error appears in the conversion check. You can define the corresponding authorizations in the role maintenance, using the authorization object for the location product APO: PP/DS, Location product (C_APO_MALO) and the authorization field Functions in PP/DS (APO_PPFUNC). You can issue authorizations for overriding the standard checks by specifying the following values for the functions in PP/DS: ATP Check SAP_CNV_ATP_CHECK Requirements Check Customer-Specific Check SAP_CNV_MAKE_TO_ORDER defined by the customers
As default, SAP delivers the PP/DS roles with authorization for overriding the checks (authorization value *). Note: In the background processing, if an error appears, the system does generally not execute the conversion indicator or the transfer and conversion, independent of the authorization..
________________________________________________________________
38 SAP AG
APO 3.1 ________________________________________________________________
1.7.3 Descriptive Characteristics for Use in Order LiveCache

Use Before Release 3.1 product and location were the only characteristics that could be transferred from Demand Planning to SNP and Production Planning /Detailed Scheduling (PP/DS). As of this release it is possible to define descriptive characteristics for use in applications that use Order LiveCache . These characteristics permit more detailed planning in several applications. The following functions are affected: o Demand Planning Release of Unconstrained Demand from DP to Order LiveCache This process transports the descriptive characteristics with their values from DP to order LiveCache. This enables you to release data at any characteristic level. Note that descriptive characteristics are then only added to the independent requirements that are generated. Release of Constrained Forecast from Order LiveCache back to DP This process recognizes the characteristics attached to the LiveCache order and transports the constrained forecast back to DP with the same characteristic values. o CTM Demand Prioritization It is possible to assign prioirities based on descriptive characteristics. For example you can specify that one customer or customer group is given preferential treatment if the demand cannot be completetly satisfied. Rule Application Currently rules can be found for a few attributes of the forecast (product, location, category). With descriptive characteristics it is possible to perform the rule finding process on any characteristic level in DP. For example including the customer in the descriptive characteristics enables the identification of customer specific rules for the same location/product forecasts. o Consumption In previous releases forecast consumption was restricted to a few attributes of the forecast (product, location) that could be matched to sales order attributes. With descriptive characteristics it is now possible to perform forecast consumption on any characteristic in DP that can be matched to an R/3 attribute of a sales order. For example including the customer in the descriptive characteristics enables the identification of customer specific forecasts for the same location/product that can be consumed by a sales order for that customer.
Effects on Customizing To specify that a DP characteristic is to be used as a descriptive characteristic in Order LiveCache, you
________________________________________________________________
SAP AG 39
APO 3.1 ________________________________________________________________
assign it to a consumption group. In the consumption group you link the DP chararcteristic with a field in the ATP field catalog. You enter the consumption group in various objects or transactions, for example the location product, the release profile, or the demand profile. You maintain consumption groups in Customizing for Demand Planning under SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Demand Planning -> Basic Settings -> Maintain Consumption Group. If you use fields that have been assigned to descriptive characteristics and want to use special sorting in CTM Demand Prioritization, you specify the priorities in Customizing under SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Supply Network Planning (SNP) -> Capable-to-Match (CTM) -> Demand Prioritization -> Maintain Special Sorting or Maintain Special Sorting of Descriptive Characteristics. Read these two IMG topics for information on which activity to use.
1.7.4 Conversion of ATP tree structures into PP/DS procurement pro (new)
Use In a scenario with an OLTP system for sales order processing and an SAP APO system for the Global Availabile-to-Promise Check (Global ATP) and for Production Planning and Detailed Scheduling (PP/DS) you can convert ATP tree structures into PP/DS procurement proposals in SAP APO 3.1. With the corresponding check configuration, a rules-based ATP check or a multi-level ATP check - new in SAP APO 3.1 - executed on a sales order, can determine which and how many of the finished products required by the customer are not available in the check location, but could be procured through stock transfers from other locations (location substitutions with rules-based ATP) or through final assembly of available components in Production Planning and Detailed Scheduling (multi-level ATP); here, components may be replaced by alternative components (product substitution with rules-based ATP). The result of the ATP check in the sales order is ATP tree structures that the system creates in SAP APO when saving the sales order; here, there is one ATP tree structure for each request schedule line in the sales order. An ATP tree structure contains, for example, the requirements data (dates, quantities and sources of supply) for the procurement proposals that PP/DS should create for the sales order (stock transport requisitions, planned orders or product substitution orders). PP/DS creates the procurement proposals by converting the ATP tree structures and schedules the procurement proposals on the resources. Depending on the position of the requirements date of an ATP tree structure, the PP/DS horizon and the scheduling horizon for ATP tree structures , conversion is either automatic immediately after saving the sales order, or the user converts the tree structures at a later time. Previously, if you changed an already existing ATP-checked sales order and executed an ATP check again, the system would check against the available PP/DS procurement proposals (that were created from the original ATP tree structure, for example). This may mean that if you bring a date forward in the sales order, the system cannot move the confirmed date forwards; procurement proposals still exist, even if they are delayed. The order may be split if a quantity in the sales order is increased. You can use the new recreate
________________________________________________________________
40 SAP AG
APO 3.1 ________________________________________________________________
receipt elements indicator in the check instructions to specify if, during a new ATP check, the system should ignore the procurement proposals created from the old ATP tree structure and delete the changed sales order when saving. However, it can only ignore and delete procurement proposals whose availability dates are within the horizon for recreation of receipts specified in the location product master, and whose statuses allow for this. You call up the the user-controlled online or background conversion in the area menu for Production Planning under Environment. Effects on System Administration If you have used Capable-To-Promise Processing (CTP processing) until now, check if you can replace this with a multi-level ATP check. (You set CTP processing if you are planning with Characteristics Dependent Planning (CDP), and if you want to schedule the procurement proposals on the resources of the sales order with a more detailed consideration of the resource availability. You use the multi-level ATP check if you are planning with variant configuration. Here, it is possible to split the order through product and location substitution; the product allocation allows for a rough check of the resource availability.) Effects on Customizing o o You define the scheduling horizon for ATP tree structures in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. When scheduling procurement proposals, the system uses the strategy profile that you have specified in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. For user-controlled conversion you can specify a strategy profile interactively under settings. You define check instructions in the customizing for Global ATP under Maintain Check Instructions.
o See also o
Release information on Multi-level ATP check Recreating receipts
Documentation on Production Planning and Detailed Scheduling
1.7.5 ATP check in PP/DS (new)

Use In SAP APO 3.1 you can execute an ATP check for the following orders in the active planning version 000 in Production Planning and Detailed Scheduling (PP/DS): o In-house production orders For an in-house production order (planned order or production order), the system checks the quantity in which the order components planned in SAP APO are available. The ATP check can derive a confirmed quantity for each order product by using a correlation calculation using the component quantities confirmed at the requirements date, that is, it can derive the quantity of the order product that the component can actually supply on the order availability date.
________________________________________________________________
SAP AG 41
APO 3.1 ________________________________________________________________
Stock transport requisitions For each order item in a stock transport requisition, the system checks the quantity in which the product to be transferred can be confirmed in the source location.
The system checks if it is possible to make a total delivery of the order on the availability date. It is not possible to split the order into available partial quantities. For the ATP check, you can use the product availability check and the check against forecasting. Products that are planning relevant are those for which you have specified a check mode and an ATP group in the location product master. The ATP check is integrated in the following PP/DS applications: o Interactive planning You can call up the ATP check in the product view, in the order processing view, in the receipt view and in Planned Order Management. Order opening In the SAP APO system, you can trigger the opening of production orders and stock transfer orders in the SAP R/3 system. For the conversion of planned orders and stock transport requisitions into production orders or stock transport orders, the system can automatically execute an ATP check on the basis of a conversion rule for the planned orders or for the stock transport requisitions. You can make user-specific settings that the system should only allow the opening if all the components are fully confirmed.
Effects on System Administration Often in SAP APO 3.0A, planned orders and stock transport requisitions are transferred to the SAP R/3 system so that an ATP check can be executed there. If you are using SAP APO 3.1, check if it is now sufficient to transfer only the orders for which the conversion indicator is set, into the SAP R/3 system. You can make the relevant settings in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. Effects on Customizing o Business events You can use various business events to control the ATP check in PP/DS according to which order type is being checked (planned order, production order or stock transport requisitions), and if the ATP check should be executed with or without a conversion check. For example, you make different checks on production orders than on planned orders. You define business events in the customizing for the Global Availability Check (Global ATP Check) under Maintain Business Events and enter them in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. ATP check for order opening You can use a conversion rule to specify that the SAP APO system should execute an ATP check during the conversion of a planned order or a stock transport requisition into a produciton order or a stock transport order. You define conversion rules in the customizing for Production Planning and Detailed Scheduling under Maintain Conversion Rules. You can enter a globally valid conversion rule in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. In the location product master, you specify the conversion rule that is valid for a product. Using the roles that you assign to the user, you specify if the user can also execute conversion if there are missing components.
________________________________________________________________
42 SAP AG
APO 3.1 ________________________________________________________________
Sequence when checking several orders The order confirmation results can depend on the sequence in which the system executes the ATP check. You use a sort profile to specify this sequence. You define sort profiles in the customizing for Production Planning and Detailed Scheduling under Maintain Sort Profile.
See also Release Information Checks with order opening
1.7.6 Buffer Process with Container Resources (New)

Use Inhalt 1. 2. Purpose of the Buffer Process New Buffer Process Functions a) b) c) 3. Displaying the Actual Fill Level through Integration with SAP R/3 Alerts for Container Property Monitoring Improved Handling in the Detailed Scheduling Planning Board
Buffer Process Prerequisites a) b) Planning Situation Master Data Modelling
4.
Buffer Process Planning a) b) Profiles for the Detailed Scheduling Planning Board Interactive Planning Procedure
5.
Restrictions
1. Purpose of the Buffer Process If you plan your products at several manufacturing levels that follow each other, you may need to temporarily buffer the material produced at one level in a container until it is consumed by the subsequent level. The material is therefore filled into a buffer container at the producing level and then discharged from the same container by the subsequent level. This process is referred to as buffer process. It is particularly common in the process industries where mainly liquid materials are processed. The buffer container is modelled as a container resource with storage characteristics in the APO system. As of SAP APO 3.1, the following planning functions supporting the buffer process are available: o o o The planned and the actual fill level of a container resource are visualized in the DS planning board. Warnings that are specific to the buffer process can be displayed in the Alert Monitor. Campaigns that are planned at several manufacturing levels and linked to each other through pegging
________________________________________________________________
SAP AG 43
APO 3.1 ________________________________________________________________
relationships (campaign chains) can be determined automatically in the DS planning board and rescheduled manually in one planning step. 2. New Buffer Process Functions As of SAP APO 3.1, the following new and enhanced functions supporting the buffer process are available: 2.a) Displaying the Actual Fill Level Through Integration with SAP R/3 Up to now, only planned receipts and demand were displayed in the fill level of a container resource. The system now also considers the actual fill level. It is represented by the stock that is relevant to the fill level in the storage locations of the SAP R/3 System. To do so, a storage location is assigned to the resource representing the container in the SAP R/3 System (storage resource). In the SAP APO System, the R/3 storage resource becomes a container resource with storage characteristics, and the relevant storage location is assigned to the container resource as a sublocation. Every goods movement to a storage location in SAP R/3 affects the fill level of the relevant container resource in SAP APO. For this reason, the fill level curve now shows the sum of the planned and actual fill level. To be able to use this function, you must have modelled the resources with storage locations correctly in the SAP R/3 System and transferred them to the SAP APO System. This requires the R/3 plug-in PI2001.2. See : Paragraph 3.b) Master Data Modelling 2.b) Alerts for Container Property Monitoring The buffer process assumes that the material produced at an initial level is filled into a container resource, and the same material is then discharged from the same container by a subsequent manufacturing level. Therefore, the following aspects must be taken into account: o o Product Purity in the Container Resource Products must not be mixed in a container resource. Container-Conforming Pegging Orders that are relevant to the fill level and are linked to each other at different manufacturing levels through pegging relationships: Must be scheduled on the same container resource
Must be modelled in such a way that the filling and discharging activity take place at the same container resource The system does not support the automatic container-conforming rescheduling of orders that are linked to each other through pegging relationships. o Fill Levels Maximum fill levels and minimum quantities in the container resource must be taken into account.
The system supports buffer process monitoring by issuing alerts. These warnings help the production planner to react to problems when manually rescheduling in the DS planning board. The following alerts may be triggered: o Quantity Set to 0 This alert is issued when a product is to be filled into a container resource that still contains another product. The system sets the fill level to zero for the product that is still left in the container. Note, however, that the remaining quantity of this product still remains in the container resource. From the
________________________________________________________________
44 SAP AG
APO 3.1 ________________________________________________________________
point of view of inventory management, however, both the old product and the product that was just filled in are posted to the stock. Depending on the amount of the product quantity remaining in the container, the production planner must therefore decide whether he or she wants to create an order to discharge the remaining quantity. For the system to be able to display this alert, you must have set the Set Remain.Fill Levels to Zero indicator in the resource master of the container resource. If you react to the alerts accordingly, you can ensure that: The fill level for the subsequent product is correct since the system simulates discharging the remaining quantity In this way, the minimum fill level and the maximum fill level are displayed correctly.
Product purity is complied with since mixing of different products is prevented This alert is triggered for receipts only but not for demand. o Invalid Mix This alert is issued if two or more products are contained in the container at the same time. Note: This alert is not displayed if the Set Remain.Fill Levels to Zero indicator has been set in the resource master and discharging of the remaining quantity is simulated. Container-Conforming Pegging Violated This alert occurs when two orders that are relevant to the fill level are linked to each other at different manufacturing levels through pegging but are scheduled on different container resources. Example: Through pegging, an order that fills container A is linked to an order that is to discharge the same product from container B. In this case, the production planner must manually transfer the product from container A to container B. Maximum Quantity Exceeded The quantity in the container resource is bigger than the maximum fill level defined in the resource master. Stock < 0 The quantity in the container resource is less than zero.
2.c) Improved Handling in the Detailed Scheduling Planning Board The following functions supporting the manual planning of the buffer process are available in the DS planning board: o Selecting Networked Campaigns (Campaign Chains) SAP APO 3.1 comprises a function that you can use to select all operations, orders, or campaigns that belong to a networked campaign. By choosing Edit -> Select -> More -> Networked Campaigns for objects you selected (order, operation, or campaign) in the DS planning board, you can automatically select the corresponding campaign chain across several manufacturing levels. In this way, you can reschedule an entire campaign chain using Drag&Drop. Visualizing the Actual Fill Level The maximum fill level and the minimum fill level can be displayed as a red line in the diagram section. Via the context menu, you can hide or show all curves. In the table section, you can display the following additional fields for container resources: - Maximum Stock Level
________________________________________________________________
SAP AG 45
APO 3.1 ________________________________________________________________
- Minimum Production Quantity - Stock Unit This is also the unit of the fill level. If you double-click a horizontal fill level line, a dialog box appears with Information about the Product that is currently on stock. If you double-click a filling or discharging line, a dialog box appears with Information about the Orders that are responsible for fill level changes: - The products that are in the container at the moment. - The relevant filling and discharging orders In addition, you can carry out the following transactions in this dialog box: - Display details about the order and operation along with the relevant network - Select objects belonging to an order
3. Buffer Process Prerequisites For the system to be able to support the buffer process from the planning point of view and create a feasible plan, the planning situation must be as described below and the master data must have been modelled according to the special features of the buffer process. 3.a) Planning Situation o o You have carried out production planning for your products across several manufacturing levels and created demand and receipts for the material components. You have carried out campaign planning for every single manufacturing level. Production campaigns in which the orders for a product are combined have been created. All orders of a campaign produce the same product and require the same material components. The production campaigns of all manufacturing levels that are linked to each other through pegging relationships are called campaign chains. You have scheduled the campaign chains in such a way that the component requirement of all orders in a campaign is usually satisfied by exactly one preceding campaign. This means the network between the manufacturing levels should be as linear as possible.
3b) Master Data Modelling You have created the master data (materials, resources, master recipes) in the SAP R/3 System and transferred them to the SAP APO System by means of an active integration model. You may need to correct the transferred master data there or add further master data. To represent the buffer process, the following settings must have been made for resources and PPMs: Resources o The storage resources from the SAP R/3 System are created as multiactivity resources with storage characteristics (container resource) in the SAP APO System. The storage location assigned to the R/3 storage resource is transferred as the sublocation of the container resource. You cannot assign sublocations to a resource in the SAP APO System. The assignment is only created or changed while transferring resources from the SAP R/3 System. You make sure that the following settings have been made for the container resources. Otherwise, you must make the settings later in SAP APO: Capacity Since a buffer container can be filled and discharged at the same time, you must allow for as much capacity for the resource so that the filling and discharging activities can be scheduled as
________________________________________________________________
46 SAP AG
APO 3.1 ________________________________________________________________
overlapping activities. While an activity, for example, fills the buffer container at one manufacturing level, another activity at the higher manufacturing level may simultaneously discharge material from the buffer container. The amount of capacity is technically restricted (for example, the number of valves at a tank). o Sublocation The storage location of the R/3 resource was transferred correctly. Storage Characteristic The indicator has been set. Dimension You specify a dimension (for example, liter) in which the fill level is to be displayed. Maximum Stock Level The maximum stock level is also the maximum fill level in a buffer container. Set Remain.Fill Levels to Zero The indicator has been set.
The buffer process requires the campaigns on the production resources to be uninterrupted. This means the following campaign requirements must be met: The production campaign running on this resource must be uninterrupted, which means that the orders of a campaign must not be interrupted by an operation that does not belong to this campaign. The setup order must be at the beginning and the clean-out order must be at the end on this resource.
If alternative resources are used, all operations of a campaign should occupy the same alternative resource. Container resources, on the other hand, must not consider the campaign requirements to make sure, for example, that the container resource can be filled by an activity of campaign A while an activity of campaign B discharges material from it. By setting the Campaign-Relevant indicator in the resource master, you can specify the resources for which campaign requirements are to be checked. The following applies to the buffer process: At least one production resource must be campaign-relevant. None of the container resources must be campaign-relevant.
Production Process Model (PPM) o o o One discharging or filling activity that takes place on a container resource is defined in the PPM. The discharging or filling activity has a resource consumption greater than zero. A product flow ID has been assigned to the discharging or filling activity. The product flow describes the timeline of the filling or discharging of the buffer container by the activity. This information is used for the fill level display. We recommend modelling the product flow and consumption type for the discharging and filling activity consistently. The consumption type of the input or output product describes the timeline of the stock increase or decrease in the location by the activity. The stock is relevant for pegging. For an input product, for example, we recommend setting up a removal as the product flow ID, whereas for an output product a filling should be defined. The point of time of the filling or removal (at the start,
________________________________________________________________
SAP AG 47
APO 3.1 ________________________________________________________________
end, or continually) should also be the same. Note: In the master recipe of the SAP R/3 System, you can maintain a product flow ID for material components only. If you also want to transfer a product flow ID for the header material from the SAP R/3 System, you must add the header material to the header material's BOM as an intra material. The intra material is the BOM header material with the negative base quantity. This intra material is then converted into a product flow for the BOM header material by the APO Core Interface (CIF). 4. Buffer Process Planning 4a) Profiles for the DS Planning Board For the DS planning board to support the interactive rescheduling of the buffer graphically and with specific functions, you must have maintained the following profiles: Planning Board Profile We recommend that the planning board profile contains the following charts: o o o Resource chart for campaigns and activities Fill level chart for container resources with stock gradient Product stock chart with order network
Strategy Profile We recommend that the following settings are made in the strategy profile: o o o o o o o Scheduling Mode: Find Slot Planning Direction: Forward Consider Campaign Requirements Always Consider Order-Internal Relationships Consider Maximum Intervals Consider Dynamic Pegging Within the Propagation Range Retain Current Modes
Alert Profile For the Alert Monitor to be able to inform you about requirement violations that occurred during buffer planning, the alerts listed below must be contained in the PP/DS profile. You must assign this alert profile to the relevant overall profile. o o o o o o o Order creates overcoverage Order has undercoverage Maximum quantity exceeded Stock < 0 Invalid mix Quantity set to 0 Container-conforming pegging violated
________________________________________________________________
48 SAP AG
APO 3.1 ________________________________________________________________
4.b) Interactive Planning Procedure The following sections describe how you can proceed to plan the buffer process interactively. The buffer process starts after production planning has been completed. Orders are available in PP/DS. They may have been created: o o o o By transferring them from the SAP R/3 System By generating them during automatic production planning By converting SNP orders By creating them manually
Production campaigns have been created at all manufacturing levels (see section 3a) Planning Situation). However, the fill levels of the container resources have not been taken into account in the planning executed so far. For this reason, problems have occurred by now which are displayed by alerts. You must now correct these errors manually in the DS planning board. You proceed as follows: 1. You check the production plan. Information about planning and planning problems is provided in: 2. The Alert Monitor The fill level chart The product stock chart
You eliminate the problems manually by rescheduling. When solving the planning problems, you always consider the entire campaign chain. After each rescheduling step, you check in the Alert Monitor whether new alerts have been created and take them into account in your next rescheduling step. First, you create available capacity by deallocating campaign chains or moving them to the future. You process the troublesome campaign chains according to their sequence in time from left to right in the DS planning board. You start with the first inconsistent campaign chain and then move on towards the future. You alternate between forward and backward planning direction. This provides a good starting situation for detailed scheduling of the buffer process. Depending on the planning problem, you can proceed as follows: You manually reschedule the operations on a different resource (mode change) to ensure that the filling and discharging campaigns take place on the same container resource. Note: If mode linkage has been specified, note that you must manually change the mode for the subsequent campaign as well. You manually reschedule the orders or operations to another date so that the consuming level is not produced until there is enough material in the buffer container from a planning point of view. You select the entire campaign chain and reschedule it using Drag&Drop. You change the sequence of the filling and discharging operations on the container resource to make sure that the maximum fill level of the container resource is not exceeded. You create orders for remaining quantities in the buffer container to react to the Quantity Set to 0 alert.
________________________________________________________________
SAP AG 49
APO 3.1 ________________________________________________________________
5. Restrictions Note the following restrictions: o o o o o Container resources and fill levels cannot be taken into account in SNP. If the pegging relationships have not been scheduled container-conformingly, the system cannot automatically change campaigns to an alternative resource. There is no planning support for the fill level. It is only visualized in the DS planning board and supported by means of warnings in the Alert Monitor. The maximum fill level and product purity may be violated. If you manually change or add material components in the SAP R/3 System, the product flow information for these components gets lost in the SAP APO System. You cannot manually create this product flow information in the R/3 order and transfer it to SAP APO. If confirmations are made to a different container resource than the one that was planned originally, the goods movement is not automatically posted to the new storage location. In this case, you must manually change the storage location, too.
1.7.7 Detailed Scheduling Strategies (enhanced)

Use The strategy profile has been enhanced as follows for SAP APO 3.1, to control new and enhanced planning functions in various application areas of Production Planning and Detailed Scheduling (PP/DS): o Infinite scheduling with planning-related minimum intervals Previously, the process-related minimum intervals between activities were considered for scheduling in detailed scheduling, under consideration of time relationships. In SAP APO 3.1, infinite scheduling on the basis of - larger - planning-related minimum intervals is possible for order-internal relationships. You can create a plan that allows enough space for later finite detailed scheduling. You maintain planning-related minimum intervals in the plan (production process model or iPPE). For the runtime object, the system can determine planning-related minimum intervals from routing data in SAP R/3. When planning under consideration of order-internal relationships, the system uses the planning-related minimum intervals if you have set the Use planning-related minimum intervals for infinite scheduling indicator in the detailed scheduling strategy. Considering cross-order relationships Previously only order-internal relationships could be considered in detailed scheduling. In SAP APO 3.1 you can also consider cross-order relationships. Cross-order relationships are relevant for subcontracting, for example. This is mapped by an in-house production order in the subcontractor's plant and a stock transport order between the subcontractor's plant and your own plant. The last activity of the in-house production order and the first activity of the stock transport order are linked by a crossorder relationship. You specify if the system should consider cross-order relationships in detailed scheduling, using the cross-order relationships field in the detailed scheduling strategy. Block planning with buckets In SAP APO 3.1, you can use block planning with buckets. You can choose to finitely schedule the bucket capacity or the time-continuous capcity of single-mixed resources whose bucket capacity is
________________________________________________________________
50 SAP AG
APO 3.1 ________________________________________________________________
derived from blocks. You specify which capacity should be finitely scheduled using the new finite capacity field in the detailed scheduling strategy. For finite scheduling of the bucket capacity there is a new finite scheduling mode find buckets with free capacity. For more information, see release information on Block Planning. o Interuptability of campaigns In SAP APO 3.1 you can use the consider campaign requirements indicator in the detailed scheduling strategy to specify if the system can interupt campaigns on campaign-relevant single resources with operations that do not belong to the campaign. You specify if a single resource is campaign relevant using the campaign relevant indicator in the resource. For more information, see the release information on Campaign Planning. Restructuring of the strategy profile The strategy profile has been restructured for SAP APO 3.1, as follows: The settings that are valid for all the detailed scheduling strategies in the strategy profile are on the Cross-strategy Settings tab page. Strategy-specific settings that are valid for planning selected objects are on the General Settings tab page. The strategy-specific settings for dependent objects are on the Strategy parameters for dependent objects tab page.
1.7.8 Extended Order Generation (new)

Use From SAP APO 3.1, the system is able to use the material components to determine the products that are to be produced (main product, by-products, offcuts), their characteristic value assignments, and the operations (such as cutting operations) needed to manufacturer them, and generate production orders for this. This is needed for processes in which several different products, with different specifications, are manufactured from one material component and the production quantities of these different products do not depend only on the quantity of the (main) production material. This planning function will be available under the name Extended Order Generation (EOG) and contains the following functions: o o o Stock search, taking account of customer-specific criteria. Generation of EOG orders taking account of information relating to stocks and the material components needed to manufacture them, and taking account of characteristics-dependent planning. Bottom-up propagation with integrated calculation of offcuts: Information on the material components is propagated to operations, activities, and to the product to be manufactured. This function also determines additional information relating to the product to be manufactured and calculates the resulting offcuts. Offcut calculation is achieved using a customer-specific macro that is called in the standard APO system. Original batch purity: The requirement from a sales order item must be covered by receipt elements from the same production lot (for example from the same melt within steel production or the same coloring process in textiles). The EOG functionality enables you to determine receipt elements that come from the same batch during the search for material components at the start of order generation.
________________________________________________________________
SAP AG 51
APO 3.1 ________________________________________________________________
Single requirement combination: During an EOG planning run for an individual requirement, an existing EOG order is extended so that it covers the original requirement and the new requirement, or at least a part of it.
Effects on Existing Data If you use single requirement combination, you can reduce the number of orders you have. Effects on Customizing To use Extended Order Generation, you must change the following settings in the implementation guide (IMG): o o Activate Extended Order Generation if you want to be able to use the basic functions such as bottom-up propagation and calculation of offcuts. To be able to use the individual functions single requirement combination, original batch purity, and extended stock search, you must also activate these in the IMG.
1.7.9 Checks with order opening (advanced)

Use In SAP APO 3.0A you can only execute a customer specific conversion check when converting planned orders or purchase requisitions into production orders or purchase orders. You implement the check in BADI /SAPAPO/RRP_ORD_CONV. The system executes the conversion check automatically if the conversion indicator is set for a procurement proposal or if you transfer a procurement proposal with the conversion indicator set into the SAP R/3 system. Until now it has only be possible to set the conversion indicator and to transfer and convert a procurement proposal into a production order or a purchase order if the procurement proposal passed the check without errors. The following new and changed functions exist in SAP APO 3.1: o Standard conversion checks You can execute the following new standard checks when setting the conversion indicator and during conversion: ATP check The ATP check checks the availability of components for a planned order and the availability of the product to be transferred in the source location for a stock transport requisition. If the ATP check determines a missing part, the user can only convert the procurement proposal in the interactive planning if he or she has the authorization to do this. Requirements check The requirements check checks which sales orders or planned independent requirements are covered directly or indirectly by a procurement proposal. The system executes a multi-level check using the pegging structure, in which the procurement proposal is contained. Conversion into a production order or a purchase order is then generally only possible if the order is used exclusively to cover sales orders. With the corresponding authorization, a user can also convert an order in the interactive planning, if the order is used to cover other requirements (for example, planned independent requirements) or if the order does not cover any requirements, that is, it is a surplus.
You can use a conversion rule to specify, either globally or location-product specifically, which
________________________________________________________________
52 SAP AG
APO 3.1 ________________________________________________________________
conversion checks the system should execute. o Role-specific overriding of the conversion checks You can specify in role if the user can set the conversion indicator in the interactive planning or if he or she can execute the conversion, even if a conversion check has resulted in an error. SAP delivers the PP/DS roles with the authorization to override the conversion check, as standard. Definition of customer-specific conversion checks You can now call up the maintenance for the BADI /SAPAPO/RRP_ORD_CONV in the customizing for Production Planning and Detailed Scheduling under Business Add-In -> Checks for the conversion of orders. You define authorization values for overriding the customer-specific checks in the customizing for Production Planning and Detailed Scheduling under Define authorizations for customer-specific PP/DS functions. Integration of the conversion checks During the conversion of ATP tree structures, Supply Network Planning orders and Capable-ToMatch Planning orders into PP/DS procurement proposals, you can specify that the system creates PP/DS procurement proposals with the conversion indicator set. The system then automatically executes the checks defined in the conversion rule; the system only sets the conversion indicator if the checks have not resulted in any errors.
Effects on System Administration Check if you still require the customer-specific check that you may have implemented in SAP APO 3.0A using the BADI. If you want to continue to use this conversion check, you must set the BAdI check indicator in the conversion rule. Effects on Customizing You maintain conversion rules in the customizing for Production Planning and Detailed Scheduling under the new activity Maintain Conversion Rules. See also Release information ATP check in PP/DS.
1.7.10 Planning procedure

Use Until now, you could control the planning of a product in Production Planning and Detailed Scheduling (PP/DS) by selecting one of the following planning procedures, specified by SAP, in the location product master: o o o o Automatic planning immediately Automatic planning in the planning run Manual planning with availability check Manual planning without availability check
In SAP APO 3.1 you can define PP planning procedures more flexibly in the customizing for Production Planning and Detailed Scheduling (PP/DS), and in the location product master you can specify which
________________________________________________________________
SAP AG 53
APO 3.1 ________________________________________________________________
planning procedure should be used to plan a product. In a planning procedure you specify which action the system should execute for each planning-relevant event when the event occurs. A planning-relevant event is, for example, a goods movement for a product or a change to the product master. For example, possible actions by the system are immediately calling up the product heuristic or creating a planning file entry; the system can then use net change planning to plan the product later in the production run. SAP delivers a selection of events and actions that can occur in production planning. You can use the reuse mode in the planning procedure to define how the system should handle the existing receipt elements for the product when planning with the product heuristic (immediately or in the production planning run). For example, the system can use receipt elements to cover product requirements or it can delete existing receipt elements and create new ones. In the scheduling status field you specify with which scheduling status the system should create a planned order, and if the system should change the scheduling status of an in-house production order after the quantity has been changed. In SAP APO 3.1 the four option fields for the planning procedure in the location product master are replaced by the new planning procedure field. SAP delivers default planning procedures that correspond to the old planning procedures (see table below). With an upgrade to SAP APO 3.1, the new planning procedure that corresponds to the old planning procedure is set automatically in the location product master. You can define user-specific planning procedures using keys A to Z. (Customer namespace.) Previous planning procedures Manual planning with availability check Manual planning without availability check Automatic planning immediately Automatic planning in the planning run
See also
New default planning procedures 1 2 2 4
For more information, see the Implementation Guide (IMG) for Production Planning and Detailed Scheduling (PP/DS) under Maintain Planning Procedure.
1.7.11 APO-PPS-PPT Product Planning Table 1.7.11.1 Enhancements in the product planning table
Use
In SAP APO 3.10, the following enhancements were made in the product planning table: o Flexible period split: Until now, the periods shifts, days, weeks, months and user-defined combinations of these periods could be displayed in the product planning table. Now you can incorporate your own periods, that you define in Customizing and have determined period profiles for, in the product planning table. A BADI transfers these user-defined periods to the product planning table. Enhancements in the periodic resource view: The periodic resource view of the product planning table has until now consisted of three lines of information: the percentage load, the resource requirements and the resource quotation, each in a user- defined time unit. You can now change the
________________________________________________________________
54 SAP AG
APO 3.1 ________________________________________________________________
resource capacity directly; the system transfers the changes to the master data. The rate of resource utilization line of information has been added to the chart. You can define in the user settings, whether to show or hide this line. If line resources are concerned, the unit of measure of the base rate can be displayed instead of a time unit. You can now also show the resource load of deallocated orders and secondary resources. o Extended selection: You can define selection rules for displaying the product planning table. You maintain the rules in Customizing and implement a BADI, that selects the data accordingly. Three selection rules are already set as default: o only products with receipts, only products with requirements, and only products with MRP types.
Layout: Individual cells in the product planning board can be displayed in color if particular business events, such as exceptional situations, exist. Assign the colors to the events in Customizing.
You can determine in a button profile, which buttons are to be displayed in which sequence for the charts in the product planning table.
You can now change the height of the individual charts.
1.7.12 APO-PPS-DST Detailed Scheduling Planning Board 1.7.12.1 Detailed Scheduling Planning Board (enhanced)
Use
The following enhancements have been made to the detailed scheduling planning board (DS planning board) in SAP APO 3.1: o Configuration Under Settings -> Profile, you can change the planning board profile during a planning board session, without ending and restarting the DS planning board. Previously, a chart for a network view or for a curve view could be a static or a dynamic chart. You specified if a network or curve view chart was a static or a dynamic chart using the dynamic chart indicator in the planning board profile. In SAP APO 3.1, network or curve view charts are dynamic charts that you can hide or display in the planning board, as required. Charts for activities, operations or orders are, as before, static charts. The dynamic chart indicator now only has the function of specifying if a chart is displayed when the planning board is called up. It has therefore been renamed do not display chart when calling up the planning board.
Selecting objects Under Edit -> Select -> More you can select networked operations, order and campaigns for the selected objects call up a customer-specific selection function under user
________________________________________________________________
SAP AG 55
APO 3.1 ________________________________________________________________
You implement the selection logic in the new customer exit APOCDPS8. To implement the customer exit, call up the Select Objects in the DS Planning Board activity under Enhancements in the customizing for Production Planning and Detailed Scheduling (PP/DS).
Planning information Under Extras -> Logs you can access the planning log. Previously, you could only call up this log in the order view and in the area menu for Production Planning. In the planning log, lists the messages that have occured during planning using a heuristic. In SAP APO 3.1, cross-order relationships can be considered during detailed scheduling. These relationships are displayed in the DS planning board by yellow lines. For more information, see the release information for Detailed Scheduling Strategies.
Enhancements for campaign planning and buffer planning In SAP APO 3.1, there are new and changed planning functions, planning information and display options in the DS planning board, that are specific to campaign planning. For more information, see the release information for Campaign Planning and for Buffer Planning.
1.7.12.2 Planning of Production Campaigns in PP/DS (Enhanced)

Use As of SAP APO 3.1, the following new and enhanced functions are available in the campaign planning environment:
o o o o o o o o
Improved Handling of Campaigns in the DS Planning Board (New) Introduction of the Campaign Status (New) Introduction of the "Campaign-Relevant" Indicator for Resources (Changed) Introduction of the "Consider Campaign Requirements" Indicator in the Strategy Profile (New) Handling of Campaigns with Errors (New) Improved "Adjust Setup/Clean-Out Orders" Function (Changed) Deleting Empty Production Campaigns (New) Business Add-Ins for Campaign Planning (New)
1.7.13 APO-PPS-PVW Product View 1.7.13.1 Display of alerts (enhanced)

Use
The following enhancements exist in SAP APO 3.1 for displaying alerts in the order view: o Alert-relevance of a product
________________________________________________________________
56 SAP AG
APO 3.1 ________________________________________________________________
In the Requirement tab page of the location product master, in the new product alerts field, you can set If the system determines direct alerts for the product
If the product is relevant for network alerts As before, you use the PP/DS alert profile to specify if and which alerts the system should display in the planning interface or in the alert monitor. In the standard delivery, the option determine direct alerts, relevant for network alerts is set.
Network alerts for receipts and requirements Previously, you could use the Display network alerts indicator under Set order view/periodic product view in the customizing for Production Planning and Detailed Scheduling to specify if the system should display network alerts; in doing this you could not distinguish between receipts and requirements. In SAP APO 3.1 you can make separate settings for if the system should display network alerts for receipts and requirements. The old Display network alerts indicator is therefore replaced by the following new indicators: Display network alerts for receipts Display network alerts for requirements
Effects on Customizing In the standard delivery, a setting is made so that the system does not display network alerts for receipts and requirements. So that the system displays network alerts, set the corresponding indicator in the customizing under Set order view/periodic product view.
1.7.13.2 ATP check in PP/DS (new)

Use In SAP APO 3.1 you can execute an ATP check for the following orders in the active planning version 000 in Production Planning and Detailed Scheduling (PP/DS): o In-house production orders For an in-house production order (planned order or production order), the system checks the quantity in which the order components planned in SAP APO are available. The ATP check can derive a confirmed quantity for each order product by using a correlation calculation using the component quantities confirmed at the requirements date, that is, it can derive the quantity of the order product that the component can actually supply on the order availability date. Stock transport requisitions For each order item in a stock transport requisition, the system checks the quantity in which the product to be transferred can be confirmed in the source location.
The system checks if it is possible to make a total delivery of the order on the availability date. It is not possible to split the order into available partial quantities. For the ATP check, you can use the product availability check and the check against forecasting. Products that are planning relevant are those for which you have specified a check mode and an ATP group in the location product master. The ATP check is integrated in the following PP/DS applications:
________________________________________________________________
SAP AG 57
APO 3.1 ________________________________________________________________
Interactive planning You can call up the ATP check in the product view, in the order processing view, in the receipt view and in Planned Order Management. Order opening In the SAP APO system, you can trigger the opening of production orders and stock transfer orders in the SAP R/3 system. For the conversion of planned orders and stock transport requisitions into production orders or stock transport orders, the system can automatically execute an ATP check on the basis of a conversion rule for the planned orders or for the stock transport requisitions. You can make user-specific settings that the system should only allow the opening if all the components are fully confirmed.
Effects on System Administration Often in SAP APO 3.0A, planned orders and stock transport requisitions are transferred to the SAP R/3 system so that an ATP check can be executed there. If you are using SAP APO 3.1, check if it is now sufficient to transfer only the orders for which the conversion indicator is set, into the SAP R/3 system. You can make the relevant settings in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. Effects on Customizing o Business events You can use various business events to control the ATP check in PP/DS according to which order type is being checked (planned order, production order or stock transport requisitions), and if the ATP check should be executed with or without a conversion check. For example, you make different checks on production orders than on planned orders. You define business events in the customizing for the Global Availability Check (Global ATP Check) under Maintain Business Events and enter them in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. ATP check for order opening You can use a conversion rule to specify that the SAP APO system should execute an ATP check during the conversion of a planned order or a stock transport requisition into a produciton order or a stock transport order. You define conversion rules in the customizing for Production Planning and Detailed Scheduling under Maintain Conversion Rules. You can enter a globally valid conversion rule in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. In the location product master, you specify the conversion rule that is valid for a product. Using the roles that you assign to the user, you specify if the user can also execute conversion if there are missing components. Sequence when checking several orders The order confirmation results can depend on the sequence in which the system executes the ATP check. You use a sort profile to specify this sequence. You define sort profiles in the customizing for Production Planning and Detailed Scheduling under Maintain Sort Profile.
________________________________________________________________
58 SAP AG
APO 3.1 ________________________________________________________________
1.7.13.3 Display of ATP data in the order view (enhanced)

Use
In SAP APO 3.10 the system displays the following ATP data in the order view for orders: o o o Confirmed quantity ATP status Missing parts indicator
1.7.14 APO-PPS-SCF Scheduling Functions 1.7.14.1 Detailed Scheduling Strategies (enhanced)

Use The strategy profile has been enhanced as follows for SAP APO 3.1, to control new and enhanced planning functions in various application areas of Production Planning and Detailed Scheduling (PP/DS):
Infinite scheduling with planning-related minimum intervals Previously, the process-related minimum intervals between activities were considered for scheduling in detailed scheduling, under consideration of time relationships. In SAP APO 3.1, infinite scheduling on the basis of - larger - planning-related minimum intervals is possible for order-internal relationships. You can create a plan that allows enough space for later finite detailed scheduling. You maintain planning-related minimum intervals in the plan (production process model or iPPE). For the runtime object, the system can determine planning-related minimum intervals from routing data in SAP R/3. When planning under consideration of order-internal relationships, the system uses the planning-related minimum intervals if you have set the Use planning-related minimum intervals for infinite scheduling indicator in the detailed scheduling strategy. Considering cross-order relationships Previously only order-internal relationships could be considered in detailed scheduling. In SAP APO 3.1 you can also consider cross-order relationships. Cross-order relationships are relevant for subcontracting, for example. This is mapped by an in-house production order in the subcontractor's plant and a stock transport order between the subcontractor's plant and your own plant. The last activity of the in-house production order and the first activity of the stock transport order are linked by a crossorder relationship. You specify if the system should consider cross-order relationships in detailed scheduling, using the cross-order relationships field in the detailed scheduling strategy. Block planning with buckets In SAP APO 3.1, you can use block planning with buckets. You can choose to finitely schedule the bucket capacity or the time-continuous capcity of single-mixed resources whose bucket capacity is derived from blocks. You specify which capacity should be finitely scheduled using the new finite capacity field in the detailed scheduling strategy. For finite scheduling of the bucket capacity there is a new finite scheduling mode find buckets with free capacity. For more information, see release information on Block Planning. Interuptability of campaigns
________________________________________________________________
SAP AG 59
APO 3.1 ________________________________________________________________
In SAP APO 3.1 you can use the consider campaign requirements indicator in the detailed scheduling strategy to specify if the system can interupt campaigns on campaign-relevant single resources with operations that do not belong to the campaign. You specify if a single resource is campaign relevant using the campaign relevant indicator in the resource. For more information, see the release information on Campaign Planning. o Restructuring of the strategy profile The strategy profile has been restructured for SAP APO 3.1, as follows: The settings that are valid for all the detailed scheduling strategies in the strategy profile are on the Cross-strategy Settings tab page.
Strategy-specific settings that are valid for planning selected objects are on the General Settings tab page. The strategy-specific settings for dependent objects are on the Strategy parameters for dependent objects tab page.
1.7.15 APO-PPS-POM Planned Order Management 1.7.15.1 Action Handler (Enhanced)

Use
In SAP APO 3.0, you could choose Production Planning --> Manufacturing Execution --> Connection of the Production Control System in the SAP menu. The connection of the production control system comprised sequence transfer and the Action Handler. For SAP APO 3.1, the sequence transfer function was moved to model mix planning (APO-PPS-MMP). See the release information Modell Mix Planning: Planning Line Networks for further details. The menu option Connection of the Production Control System was changed to Action Handler, and the Action Handler received its own component APO-PPS-AHT. The following enhancements were made in the Action Handler:
Customizing and Master Data
New Actions The new actions allow you to carry out the following functions: reschedule orders on alternative resources/lines within a group of alternative lines (only when iPPE is used) change the status of activities (only when iPPE is used) send SAPOffice notifications in the case of an error assign action networks to orders deallocate orders delete orders manually carry out actions for an action point
________________________________________________________________
60 SAP AG
APO 3.1 ________________________________________________________________
display the variant configuration in production tracking carry out ATP checks for the components of an order (see also release information ATP Check in PP/DS)
Automated Processing with the Action Handler In automated processing, the Action Handler automatically carries out certain actions for all planned orders as soon as the planned orders reach a certain action point during production (printing of documents, production tracking, backflush and so on). This functionality already existed in SAP APO 3.0 and has now been enhanced. The following functions are now available: o Archiving Tracking records, including all additional customer fields, are archived. This reduces the database content in the productive system as far as possible and improves the performance. Production Tracking in Planned Order Management (only available if iPPE is used) In planned order management, a new application in SAP APO 3.1, you can display production tracking information on planned orders (tab page Tracking Info) which you selected in the planned order overview. Improved Error Handling If errors occur during the execution of actions, you can send an express mail to the user responsible in addition to the SAPOffice mail. It is possible to implement this functionality per action point or per combination of action point and action. You can also implement user-defined error handling. In this case, the event ACTIONHANDLER_ERROR_OCCURRED is connected to the SAP Business Workflow. Instead of a mail, the person responsible then receives a work item in his SAPOffice-Mail inbox.
________________________________________________________________
SAP AG 61
APO 3.1 ________________________________________________________________
Manual Processing with the Action Handler In manual processing, you manually start actions with individual planned orders in order to prepare production in a controlled manner (carry out ATP check for components first, then release orders and so on). This function is new in SAP APO 3.1. o Action Handler in Planned Order Management (only available if iPPE is used). You can use planned order management, a new application for SAP APO 3.1, in order to do the following, starting from the overview screen for planned orders: view the action network for planned orders you selected and manually carry out actions from there
manually carry out standalone actions without business-related dependencies which can be started at any point of the production process for planned orders you selected (tab page Action Handler). For further details, see the release information Planned Order Management. Effects on Customizing Maintain settings for Action Handler
1.7.15.2 Planned Order Management (new)

Use As of SAP APO release 3.1, all necessary information and processing functions for planned orders are integrated into an application contained within the environment, based upon the integrated Product- and Process-Engineering (iPPE) manufacturing process. o You can display the corresponding planning information. The components and activities can either be planned using the single explosion in the Production Planning and Detailed Scheduling (PP/DS) or the Planning Matrix (RPM). In the Planned Order Management (POM) you are however unable to carry out any planning functions. Existing editing functions for planned orders are summarized, such as backflush, the firming of components or changing to alternative lines for example.
Specifically, the Planned Order Management offers the following functions: o You can select planned orders for the planned version 000 according to different criteria, such as horizon, location, product, components, planner, iPPE-line element, resource, order number or some alternative order identification. You can store frequently used criteria as selection variants. After selection you are taken to a screen, which is divided into two different areas: Order Overview The selected orders are listed in the order overview. Using this list you can execute several functions which allow the planned orders to be displayed, printed and exported, and which also permit the display of the orders in the detailed area, as well as the mass processing of orders based on heuristics. You also have the possibility to move out of the order overview, directly to another order within a different transaction: to process the order, to display the product master, and to display and change iPPE.
________________________________________________________________
62 SAP AG
APO 3.1 ________________________________________________________________
Detailed Area On the tab pages, the details for each particular planned order are displayed. You can scroll through the planned orders selected in the order overview. Using the detailed area you can also carry out several different editing functions.
In the user settings assign the various profiles (detail profile, heuristic profile, alert-profile) and define the size ratio of the screen areas. You can change the screen areas dynamically. For example, you can display the detailed area as full screen. In detail profile define which detail screens are to be displayed in the detailed area, and in which sequence these should appear on the tab pages. The maximum number of tab pages available to you is 15. SAP delivers standard detail profile and standard detail screens. If the delivered detailed screens do not meet your requirements, you can create user specific detailed screens and then assign a detail profile. Detailed information concerning the creation of user specific detailed screens can be found under: define detail profile.
o o
The following standard detail screen makes it possible for you to call up different information and functions for other components from the Planned Order Management o Order Details Details relevant to the selected planned order are displayed, such as dates, quantities, information on the order status and on the ATP check, and also master data and characteristic valuations for configurable products. Backflush By means of an overview, all reporting pointsare listed along with the quantities reported back up to that point. You can backflush manually at those points, where a backflush has not taken place or has not been completed. Tracking Information The display of the production tracking within the Planned Order Management is used for this, and allows the production progress of the selected orders to be monitored in a comfortable working environment, and errors in the production process to be tracked down. In the display you can see which action points the order has passed through, and at which time this has taken place. Should an action point be passed through more than once, for example, an action point in the paint shop in the automobile industry, a note is given of a failure in the production process. See also: Release-information action control (extended) Action Control From this detailed screen, you can view and carry out the actions which are assigned to the selected orders. There are two types of actions, which can be carried out manually: Standalone-actions without business dependencies, which can be carried out at every point along the production process (send notifications, print documents). These actions are displayed on the right-hand side of the detailed screen. Actions, which are linked to each other to an action net according to business criteria (firstly carry out the ATP check for components, then release order). This guarantees the definition of the action net in the Customizing, so that you can only execute the actions in a logical business sequence.
________________________________________________________________
SAP AG 63
APO 3.1 ________________________________________________________________
The actions for this action net are displayed along with their position in the net on the left-hand side of the detailed screen. See also: Release-information Action control (extended) o Alerts In this detail screen the alerts for the selected planned order are displayed. Different functions for the alert monitors are available, such as to note the alert, cancel it, to forward it, or to freeze it. See also: Release-information display of alerts (extended) Components You can fix component requirements, to protect them against changes which may arise due to a renewed planning run. If you work with the Planning Matrix (RPM), the indicator fixing allowed in Customizing for the Planning Matrix (RPM) must be set. If you work with the single explosion, you do not have to set an indicator. You can only fix component requirements, or cancel the fixing, if you have not entered a confirmation for the planned order. ATP Check Using this detail screen you can start the ATP Check interactively. The system checks, what quantities of the components for the planned order scheduled in the SAP-APO-System are available. The results of the check are displayed immediately. Using this method, you can instantly identify whether certain components are missing. If you wish to carry out an ATP Check for the components of RPM materials, you must set the indicator fixing allowed in Customizing for the Planning Matrix(RPM) in the same way. If you work with the single explosion, you do not have to set an indicator. The scope of the check, such as for example, a check for the stock level or for planned entries, is determined with the assistance of the ATP group, which you have entered in the location product master for the components. The available quantity of a component is displayed on the screen as a confirmed quantity. Missing components are displayed with the assistance of the missing parts indicator. The planned order is only then completely confirmed, if all of the ATP relevant components are available. After a ATP Check every checked quantity is fixed, to protect the components from any further changes which may arise through a renewed planning run. See also: Release-information ATP Check in the PP/DS (new) Release-information ATP Check for planned orders from RPM products Activities The activities relevant for planning are displayed with the resources, the locations and the status for the selected orders. The resources create the base for the production planning. The activities are determined from the integrated Product- and Process-Engineering (iPPE) from the single explosion of the Production Planning- and Detailed Scheduling (PP/DS) . In this detail screen you can see a change of mode (change from alternative lines) available. Matrix Activities In contrast to the previous detail screen, here the activities from the activities matrix and the line segments are displayed, upon which the activities should be carried out. A prerequisite is, that you use the Planning Matrix (RPM) for the planning of the component requirements, and have also generated a activities matrix.
________________________________________________________________
64 SAP AG
APO 3.1 ________________________________________________________________
See also: Release-information new functions in the Planning Matrix

Settings for the detail profile are available in Customizing for the Advanced Planner and Optimizer (APO) under Supply-Chain-Planning -> Production planning- and detailed scheduling (PP/DS) -> Planned Order Management -> Define detail profile .
1.7.16 APO-PPS-CDS Collaborative Management of Delivery 1.7.16.1 Collaborative Management of Delivery Schedules (CMDS) (new)
Use General Information
The term Collaborative Management of Delivery Schedules (CMDS) incorporates the management of delivery schedule releases, both for procurement delivery schedules as well as sales and distribution delivery schedules. Management of procurement delivery schedules was previously realized in SAP APO 3.0 as part of "Collaborative Procurement" and has now been enhanced, and rounded down in Release 3.1 at the interface for procurement delivery schedules and sales and distribution delivery schedules. A new feature of the current release is the function for managing delivery schedules for SD scheduling agreements. Management of delivery schedules for SD scheduling agreements
The business advantage of using this function to process delivery schedules from SD scheduling agreements is the simultaneous display of customer requirements and the internal flow of stock for a product. When doing this, the system takes into account capacities and other restrictions over several levels in order to achieve the optimum utilization of the machines.
Target groups are those who are responsible for planning at a vendor and who work at the interface between processing sales orders and planning production. These could be product planners who plan a certain number of sales products and have direct contact with the corresponding customer. The work of these planners controls the production plan for the corresponding finished product and the confirmations to the customer. Such a planner faces the following situation in a day's work: The customers send many delivery schedules. Each delivery schedule contains schedule lines whereby each line contains a delivery date and a requested quantity to be delivered. The schedule lines normally represent days for several months, and then they represent weeks and months. Each new delivery schedule replaces the previous one. Many manufacturers send new delivery schedules on a daily basis, and even inside a day in the short-term horizon. Many schedule lines do not change between each delivery schedule, but they can change. If individual schedule lines change, this can have enormous effects on availability and production planning. For this reason and others, the planner has to check the confirmed quantities in short-term and mid-term schedule lines every day. The aim of this new function is to improve significantly the quality and efficiency of the processing of delivery schedules and to increase the stability of the internal production planning and of the communication with the customers. To achieve this, the system first runs a series of checks automatically. These checks generate confirmations for uncritical delivery schedules and, if required, these confirmations are sent to the
________________________________________________________________
SAP AG 65
APO 3.1 ________________________________________________________________
customers. The planner can view schedule lines with conflicts in an alert monitor. These schedule lines can then be processed in a comfortable working environment and are then confirmed as matching or deviating. The planner is thus freed from the simple routine work and kept informed of the current status in the relevant planning area by filtered information. The requirements are only relevant to planning after they have been confirmed manually or automatically. This ensures that only checked requirements flow into the internal production planning and, if necessary, are transferred to the customers. Management of delivery schedules for procurement scheduling agreements The functions for managing delivery schedules for procurement scheduling agreements have been enhanced with a function for processing confirmations. If the vendor sends confirmations to the customer, the customer can process these confirmations further in an APO System using the delivery schedule management functions for procurement scheduling agreements. The customer thus has reliable, always up-to-date data that can be used as a basis for the ATP check, range of coverage alerts and goods receipt proposals. Function Description o EDI inbound processing: The delivery schedules for the SD scheduling agreement are sent to the vendor's APO System by EDI/Internet. The master data for the delivery schedule is known in the R/3 System and the APO System. The EDI inbound function determines the corresponding scheduling agreement, uses the splitting function (days on which inbound deliveries are possible) to create month or week schedule lines, calculates the forecast delivery schedules and operative delivery schedules (for example, a forecast delivery schedule has month schedule lines for the next 12 week period, but an operative delivery schedule has day schedule lines for the next 6 week period), and saves the delivery schedules in the delivery schedule history. Eligibility check: This check refers to the individual delivery schedule and checks whether this is eligible from a business point of view, that is, does not violate quantity tolerances that have been set in Customizing. To do this, the system compares the new delivery schedule with the old one. Feasibility check: This check refers to a product and checks the days' supply (number of days before the stock of a product falls below the minimum days' supply) for a valid delivery schedule. If the days' supply is below the defined minimum day's supply, the planner must reprocess the delivery schedule manually. This is a single-level check, that means, the availability of components for existing procurement proposals for the product are not checked. You can set on a user-specific basis how the days' supply is calculated and which stocks, receipts and requirements are used for the calculation. Confirmations: If the result of the feasibility check is OK, the system generates a confirmation. The requirements from the delivery schedule only become planning-relevant after this confirmation is generated. If required, you can send the confirmation to the customer by EDI/Internet. At the same time, a mini delivery schedule with the currently valid data that is delivery relevant is created in the R/3 System over the Core Interface (CIF). This delivery schedule ensures that all necessary data for the shipping and for the business processing of the scheduling agreements is transferred to the R/3 System. The confirmation is a new object and is therefore an enhancement of the scheduling agreement process both for SD scheduling agreements and procurement scheduling agreements. In contrast to the shipping notification in the R/3 System, the confirmation does not confirm an exact delivery schedule line but a whole series and this does not take place in the R/3 System but directly in the APO System. When using delivery schedule management for procurement delivery schedules, the customer can choose to work without cofirmations, with confirmations always or with confirmation only in exceptional cases. In addition, the customer can choose for each process whether either the delivery schedules or the confirmations are to be ATP-relevant and whether the shipping notifications or the goods receipt are to be settled with scheduling agreement lines, delivery schedules or confirmations.
________________________________________________________________
66 SAP AG
APO 3.1 ________________________________________________________________
Scheduling agreements can be included not only in the feasilibility check but also in the ATP-Check, Product Availability Check. In the product availability check you can use an enhanced confirmation logic. The enhanced confirmation logic represents a enhancement of the product availability check. One aspect of the enhancement is that the quantities which have been confirmed remain assigned to the individual orders (Minimum Confirmation). This is also the case if the product availability of these minimum confirmation quantities is not given. If a customer reduces required quantities which have already been confirmed, the system first tries to assign the corresponding confirmed quantities to other required quantities within the same order item. Confirmed quantities which cannot be assigned within the order item are subsequently available for coverage of other requirements. The enhancement also means that the distribution of the available ATP quantities is carried out per schedule line and not per item. o Alert Monitor: In the alert monitor, the system displays all delivery schedules that cannot be confirmed automatically and that are therefore not yet planning-relevant. These alerts provide the planner with an overview of the current situation and the scope of the manual reprocessing. Manual delivery schedule processing: In the product view or in the product planning table of the APO System, the planner can create a worklist and then work through this successively. In both of these applications, the system displays all requirements (sales orders/scheduling agreement releases) for the product, and also displays each new delivery schedule compared with the old planning-relevant delivery schedule. The planner has the options of dispatching production orders manually, correcting confirmations for the delivery schedules and triggering again the eligibility check, feasibility check and planning heuristics for individual delivery schedules. The end of the manual processing is the MRPrelevant transfer of the planning result in the dialog and, if necessary, the sending of the confirmation to the customer. Customer-specific adaptions: There are numerous BAdIs for adapting the functions to customer-specific needs. In addition, you can use your own function modules for the checking of scheduling agreement releases.
Application area CMDS has been developed to meet the needs of the automotive industry, but it can also be used in other industries. Restrictions Only certain types of SD scheduling agreements are supported. For Release SAP APO 3.1 you can only use CMDS in conjunction with an R/3 System (Release DI 4.6C2) and CRT4. You cannot use other releases or other OLTP systems. The necessary integration is to be developed in future releases. Effects on Customizing You find Customizing for CMDS under Advanced Planner and Optimizer (APO) --> Supply Chain Planning --> Collaborative Procurement or Delivery Schedule Processing for SD Scheduling Agreement.
________________________________________________________________
SAP AG 67
APO 3.1 ________________________________________________________________
1.7.17 APO-PPS-EVA Evaluation 1.7.17.1 Evaluations in PP/DS (enhanced)

Use
The following enhancements exist for evaluations in SAP APO 3.1: o Order list The system uses the characteristics symbol (green triangle) to show if an order product is a configurable product. To display the characteristics value assignments, click on the characteristics symbol. Resource load The following display options exist for the evaluation of the load on block-planned resources: Display the block load in any unit of measurement In block planning, you can specify that the productive time of a resource is calculated into an equivalent with any unit of measurement. In this way, you can display the quantity to be produced for a block instead of the productive time. So that the equivalent is displayed in the evaluation of the resource load for a block-planned resource, select the display in block unit indicator under view selection, when calling up the evaluation. Display the block capacity For blocks with block-planned single-mixed resources, you can display the time-continuous capacity and the bucket capacity derived from the time-continuous capacity. A prerequisite is that you have set buckets from block planning for the resource for the standard capacity.
1.7.18 APO-PPS-SNP SNP to PP/DS Conversion 1.7.18.1 Conversion of SNP orders into PP/DS orders (enhanced)
Use
When planning, you can use Supply Network Planning (SNP) together with Production Planning and Detailed Scheduling (PP/DS). You use SNP for medium to long-term aggregated planning. Here, you can determine the sources of supply (external procurement or production) that are optimal from a cost point of view (for example, external procurement costs or storage costs. You use PP/DS for detailed scheduling and optimization of dates, resource assignment and the sequence of in-house production orders, for example. If you want to base the PP/DS planning on SNP planning, you convert the SNP orders into PP/DS orders. To improve integration between SNP and PP/DS, the conversion function has been enhanced for SAP APO 3.1. For example, the enhancements support a scenario in which SNP has the planning control, and can specify the lot sizes, sources of supply and - for in-house production - production alternatives (mode selection) for production planning; PP/DS is only used to create complete PP/DS planned orders from SNP planned orders - in general only the most important components are planned in SNP - and to create a sequence of orders with detailed dates. In such a scenario, requirements planning only a task in SNP, that is, PP/DS orders are created for the products only through the conversion of SNP orders.)
________________________________________________________________
68 SAP AG
APO 3.1 ________________________________________________________________
Planning horizons and conversion horizons Previously, the areas of responsibility of SNP and PP/DS were only separated by one horizon, the production horizon: Within the production horizon, PP/DS heuristics were used for planning, and outside the production horizon SNP was used. SNP or Capable-To-Match planning (CTM) orders could be converted into PP/DS orders, for which the start date of the first activity was within the production horizon. By specifying an offset, you could extend the conversion horizon and also convert SNP/CTM orders that began later. In SAP APO 3.1 a horizon has been introduced that is specific to PP/DS - PP/DS horizon - in which you can plan using PP/DS heuristics. The conversion horizon is now determined by the PP/DS horizon and the offset. The horizon previously called the production horizon is now only relevant for SNP and has thus been renamed the SNP production horizon; SNP can only plan production outside this horizon. If you define overlapping horizons, that is, if the SNP production horizon is shorter than the PP/DS horizon, then SNP and PP/DS will have the same planning area. When using mixed resources, in SNP you can consider the resources loaded by PP/DS orders and adjust the planning in the shared planning area to the current PP/DS planning. If you are using reconciled plans (production process models, iPPE plans and runtime objects) in SNP and PP/DS, with suitable conversion parameters, you can integrate SNP planning seamlessly into PP/DS planning. You specify the PP/DS horizon and the SNP production horizon in the location product master. In the planning version you can specify a default PP/DS horizon that is used by the system if no PP/DS horizon is specified in the location product master. In the event of an upgrade, the system automatically transfers the value of the (SNP) production horizon into the new PP/DS horizon. Adjusting the conversion horizon to the SNP time buckets profile If the end of the conversion horizon is in the middle of an SNP planning period, not all SNP/CTM orders in this period will be converted into PP/DS orders. This may be undesirable. In SAP APO 3.1, the system can automatically extend the conversion horizon to the end of the SNP planning period in which the end of the conversion horizon lies. The system converts all SNP/CTM orders in this period. Order types to be converted In the new order type field, you specify which SNP orders the system should convert into PP/DS orders. This field replaces the ATP category and convert time-continuous CTM orders fields, with which the order types to be converted were previously defined. Lot sizes of PP/DS orders For the conversion of in-house production orders, the system has to determine the lot sizes of the PP/DS orders. Previously, you had the following options: o o The system converts an SNP/CTM order into a PP/DS order with the same quantity. The system determines the lot sizes according to the lot size settings in the location product master and creates corresponding PP/DS orders.
You specified which option the system should use using the lot size determination indicator. In SAP APO 3.1 there is a further option with which the system can determine the lot sizes from the lot size interval in the PP/DS plan (PPM, iPPE Plan or runtime object); in the PP/DS plan, you define the lot size interval by entering a minimum lot size and a maximum lot size. The lot sizes created by the system for PP/DS orders depend on the quantity of the SNP/CTM order, as follows: 1. The quantity of the SNP/CTM order is less than the minimum lot size.
________________________________________________________________
SAP AG 69
APO 3.1 ________________________________________________________________
Here, the system automatically rounds the minimum lot size up and creates a PP/DS order with this quantity. 2. 3. The quantity of the SNP/CTM order is between the minimum and maximum lot size. Here, the system creates a PP/DS order that has the same quantity as the SNP/CTM order. The quantity of the SNP/CTM order is greater than the maximum lot size. Here, the system splits the quantity of the SNP/CTM order into partial quantities, the same size as the maximum lot size, and creates planned orders for these lot sizes. The system determines a lot size for the remaining quantity according to rules 1) and 2) and creates a planned order with this lot size.
In the new lot size field, that replaces the old lot size determination indicator, you specify which lot size option the system should use. Note: As of SAP APO 3.1, the system can create an SNP PPM with a lot size interval the same as the lot size interval that you have already defined for the PP/DS PPM. For more information, see the release information on Creating SNP PPMs. Mode selection Previously, you were also able to specify that, for conversion of PP/DS planned orders, the system should use the PP/DS PPM that is entered in the SNP PPM. If different modes were assigned to the operations in the PP/DS PPM and so that different production alternatives could be modelled, the system automatically executed mode selection when creating the PP/DS planning orders. In SAP APO 3.1 SNP can specify not only the PPM for PP/DS, but also the mode selection. A prerequisite is that you have created corresponding SNP PPMs from a PP/DS PPM that allows different mode combinations. You do this using the generation report for the SNP PPM. For more information, see the release information on Generating SNP PPMs from PP/DS PPMs. Order status of the PP/DS orders Previously, you could specify that the PP/DS orders should have the status output fixed. In SAP APO 3.1 you can now also specify that the system should set the conversion indicator for the PP/DS orders, for conversion in the active planning version 000; a planned order or purchase requisition, for which the conversion indicator is set, will be converted into a production order or a purchase order immediately after transfer to the SAP R/3 system. Before setting the conversion indicator, the system can execute a conversion check. For more information, see the release information on Checks with Order Opening. Conversion mode In the conversion mode field you could previously specify if the system should plan components or stock transport requiremenets of the newly created PP/DS orders. In SAP APO 3.1 the conversion mode field has been removed; the system plans the components and stock transport requirements according to the planning procedure specified in the location product master. For more information, see the release information on PP Planning Procedure. Displaying orders to be converted You can now use the display selection indicator to specify that the system should display the SNP/CTM orders to be converted. In the display you can start the conversion specifically for selected orders. See also Release Information o Creating SNP PPMs from PP/DS PPMs
________________________________________________________________
70 SAP AG
APO 3.1 ________________________________________________________________
Cross-Period Lot Sizes
1.7.18.2 SNP PPM Generation With Lot Size Margins (new)

Use
1.7.19 APO-PPS-PCM Production Campaign 1.7.19.1 Planning of Production Campaigns in PP/DS (Enhanced)
Use As of SAP APO 3.1, the following new and enhanced functions are available in the campaign planning environment:
Improved Handling of Campaigns in the DS Planning Board (New)
________________________________________________________________
SAP AG 71
APO 3.1 ________________________________________________________________
o o o o o o o
Introduction of the Campaign Status (New) Introduction of the "Campaign-Relevant" Indicator for Resources (Changed) Introduction of the "Consider Campaign Requirements" Indicator in the Strategy Profile (New) Handling of Campaigns with Errors (New) Improved "Adjust Setup/Clean-Out Orders" Function (Changed) Deleting Empty Production Campaigns (New) Business Add-Ins for Campaign Planning (New)
1.7.19.2 Improved Handling of Campaigns in the DS Planning Board (New

Use As of SAP APO 3.1, the following new functions for the processing of production campaigns are availabe in the detailed scheduling planning board: o New Pushbuttons for the following functions: o Display header data for campaign Select objects for campaign Create campaign Add orders to campaign Remove orders from campaign
New Shortcuts You can now also use shortcuts in the DS planning board menu under Functions -> Production Campaign for the following menu options: Menu Option Select Add Selected Items Remove Selected Items Header Data Create Adjust Setup/Clean-Out Orders Shortcut Ctrl+Shift+F6 Ctrl+Shift+F7 Ctrl+Shft+F8 Ctrl+Shift+F9 Ctrl+Shift+F10 Ctrl+Shift+F11
Legend for Campaign Display In the planning board legend, the following information is provided in the diagram section of the resource chart: Which colors are available for campaign bars How the campaigns are displayed depending on the status they have (see section Campaign Status Display).
________________________________________________________________
72 SAP AG
APO 3.1 ________________________________________________________________
Campaign Status Display How campaigns are displayed depends on the campaign status. Campaigns of the same setup group have the same basic color, but different hatches depending on the status. Status Created Released Campaign Bar Display Colored, no hatch Colored, diagonal stripe
Started Colored, diagonal crosshatch For more information on the campaign status, seeIntroduction of the Campaign Status. o Campaign Rescheduling You can reschedule a campaign to a different date by moving the campaign bar or bars in the resource chart of the DS planning board with Drag&Drop. Based on the detailed planning strategy defined, the system then tries to schedule the campaign along with its orders as closely to the desired date as possible. Campaign Bar Labelling In the standard system, the campaign bars in the resource chart are labelled with the following information: The APO number of the campaign The short text of the campaign
The status of the campaign In addition to this, you can use the /SAPAPO/PCM04_PT_PRS Business Add-In to define other labels. See also: Business Add-In for Campaign Planning o Color Assignment for Campaign Bars In the DS planning board, the system displays a campaign by showing a colored campaign bar in the background of the orders belonging to a campaign. Up to now, the system only used one color that had been defined in the system for the campaign bar. From now on, you can individually assign a color for the campaign bar from a predefined color palette. In the DS planning board, the campaign bars are then displayed in the color you selected. For manually created campaigns, you can select the color in the campaign transaction and the DS planning board.
For campaigns created by optimization, you can select a color in the campaign profile. The color is specific to the setup group, which means that campaigns with the same setup group are displayed in the same color. In addition, you can use the /SAPAPO/PCM04_PT_PRS Business Add-In to select other colors, too. See also: Business Add-In for Campaign Planning o Selection Function A new function is now available in the DS planning board that allows you to automatically select all operations and orders belonging to a campaign. You first need to select an operation, order, or campaign bar, and then choose Edit -> Select -> For the Same Campaign.
Effects on Customizing To display the campaign bars and pushbuttons for campaign processing in the DS planning board, you need
________________________________________________________________
SAP AG 73
APO 3.1 ________________________________________________________________
to set the Campaign indicator for the resource chart in the planning board profile. To do so, go to Customizing for SAP Advanced Planner and Optimizer and choose Supply Chain Planning -> Production Planning and Detailed Scheduling -> Detailed Scheduling Planning Board -> Maintain DS Planning Board Profiles . See also For more information on new and enhanced functions in campaign planning, see Planning of Production Campaigns in PP/DS.
1.7.19.3 Introduction of the Campaign Status (New)

Use As of SAP APO 3.1, there is not only an order status but a campaign status, too. It is derived from the statuses of the orders contained in the production campaign. The following statuses have been defined: o Created The production campaign contains: o o Only orders that have not yet been released or started No orders
Released The production campaign contains at least one released order but no order that has been started. Started The production campaign contains at least one order that has been started.
In Customizing for Production Planning and Detailed Scheduling under Global Settings -> Maintain Global Parameters and Defaults, you can specify the following depending on the campaign status: o o Whether or not orders may be removed from the campaign Whether or not a campaign may be dissolved
By making the following settings, you can control that orders must not be removed from a campaign and that campaigns must not be dissolved: o o o o No Restriction - this means the campaign status is not taken into account No Released Orders - this means if the campaign contains one released order No Orders that Were Started - this means if the campaign contains one order that has been started No Released Orders or Orders that Were Started - this means if the campaign contains one released order or one order that has been started
These Customizing settings are taken into account in the following planning transactions: o When rescheduling manually In the detailed scheduling planning board In the campaign transaction
________________________________________________________________
74 SAP AG
APO 3.1 ________________________________________________________________
In automatic campaign optimization in the detailed scheduling planning board
Effects on Customizing To make these settings, go to Customizing for SAP Advanced Planner and Optimizer and choose Supply Chain Planning -> Production Planning and Detailed Scheduling -> Global Settings -> Maintain Global Parameters and Defaults. Select the setting you want to use in the Remove Orders from ProdCampaign field.
See also For more information on new and enhanced functions in campaign planning, see Planning of Production Campaigns in PP/DS (New).
1.7.19.4 Introduction of the "Campaign-Relevant" Indicator for Resour (Changed)

Use Up to now, all resources were campaign-relevant by default. As of SAP APO 3.1, you can explicitly define for each resource whether it is to be campaign-relevant or not. If the Campaign-Relevant indicator has been set for a resource, the following requirements are checked: o o The campaign running on this resource must be uninterrupted, this means the orders of a campaign must not be interrupted by an order that does not belong to this campaign. At this resource, the setup order must be at the beginning and the clean-out order must be at the end.
Note the following dependencies: o o Campaign-relevant resources must not be used as secondary resources in a production process model (PPM). The system only checks the above campaign requirements for resources if both the CampaignRelevant indicator has been set in the resource master and the Consider Campaign Requirements indicator has been set in the strategy profile. You can override the Campaign-Relevant indicator in the resource master by setting the Consider Campaign Requirements indicator. If you define a resource as Campaign-Relevant but have NOT set the Consider Campaign Requirements indicator in the strategy profile, the campaign requirements are not checked.
Effects on Data Transfer To make sure that the resources remain consistent when upgrading from Release 3.0 to 3.1, you must convert them in a mass maintenance transaction. For more information, see Mass Maintenance of SAP APO Master Data. See also
________________________________________________________________
SAP AG 75
APO 3.1 ________________________________________________________________
For more information, see: o o Introduction of the "Consider Campaign Requirements" Indicator (New). Planning of Production Campaigns in PP/DS (New).
1.7.19.5 Introduction of the "Consider Campaign Requirements" Indicat Strategy Profile (New)
Use As of SAP APO 3.1, you can set the Consider Campaign Requirements indicator in the strategy profile on the General Strategy Parameter tab. By doing so, you specify that the following campaign requirements are taken into account when scheduling orders and operations: o o The campaign that is dispatched at the same resource must be uninterrupted, this means that the orders of a campaign must not be interrupted by orders that do not belong to this campaign. The setup order must be at the beginning of the campaign and the clean-out order must be at the end.
The system only checks the above campaign requirements for resources if the following indicators are set at the same time: o o The Campaign-Relevant indicator in the resource master The Consider Campaign Requirements indicator in the strategy profile
Effects on Customizing To set the Consider Campaign Requirements indicator, go to Customizing for SAP Advanced Planner and Optimizer and choose Supply Chain Planning -> Production Planning and Detailed Scheduling -> Detailed Scheduling Planning Board -> Maintain Strategy Profiles. See also For more information, see: o o Introduction of the "Campaign-Relevant" Indicator for Resources (Changed). Planning of Production Campaigns in PP/DS (New)
1.7.19.6 Handling of Campaigns with Errors (New)

Use As of SAP APO 3.1, you can choose from the following functions to correct producion campaigns that have errors: o o Campaign alerts Correction heuristic for eliminating campaign alerts
________________________________________________________________
76 SAP AG
APO 3.1 ________________________________________________________________
A production campaign does not have any errors if the following requirements are met: o o Orders in a campaign that are dispatched at the same resource are not interrupted by orders that do not belong to this campaign. The setup order is at the beginning and the clean-out order is at the end of the campaign.
The system checks these requirements when creating campaigns manually and automatically (campaign optimization). If the campaign is not consistent, the system issues campaign alerts as follows: o o In the campaign transaction and the Alert Monitor, the alerts are displayed in the form of messages. In the DS planning board, the alerts are shown by means of flashing operation bars.
To eliminate the alerts, choose the Eliminate Campaign Alerts function in the DS planning board or in the campaign transaction. The system uses the correction heuristic to deallocate the orders that caused the alerts. It tries to reschedule them, according to the settings in the strategy profile. If the orders cannot be rescheduled, the orders remain deallocated. Effects on Customizing To be able to see the campaign alerts in the DS planning board and in the campaign transaction, you must create a PP/DS alert profile in your planning board profile. This PP/DS alert profile must contain all the alerts relevant for campaign planning. To do so, go to Customizing for SAP Advanced Planner and Optimizer and choose Supply Chain Planning -> Production Planning and Detailed Scheduling ->Detailed Scheduling Planning Board -> Maintain DS Planning Board Profiles . See also By using the /SAPAPO/PCM02_ALERTS Business Add-In, you can implement your own logic to eliminate campaign alerts. For more information, see Business Add-In for Campaign Planning (New) For more information on new and enhanced functions for campaign planning, see Planning of Production Campaigns in PP/DS (New).
1.7.19.7 Improved "Adjust Setup/Clean-Out Order" Function (Changed)

Use You can automatically adjust setup/clean-out orders in the detailed scheduling planning board. This means that existing setup/clean-out orders are deleted and new ones are created. One setup order or one clean-out order is created per campaign. A setup order is always positioned at the beginning of the campaign and a clean-out order at the end. This function is always peformed when you carry out the following transactions in the detailed scheduling board: o o PP/DS optimization with campaign optimization The Adjust Setup/Clean-Out Orders function
________________________________________________________________
SAP AG 77
APO 3.1 ________________________________________________________________
Up to now, all setup/clean-out orders existing in the planning period of the detailed scheduling planning board were automatically adjusted when you carried out the Adjust Setup/Clean-Out Order function. As of SAP APO 3.1, you can carry out this function specifically for selected campaigns. To do so, select the relevant campaigns in the detailed scheduling planning board. If you do not select campaigns, the system issues a message telling you that all setup/clean-out orders in the planning period will be adjusted. If you do not want this, you can cancel the functions. Effects on Customizing For the system to be able to create setup/clean-out orders for a campaign automatically, you must have set up the campaign profile accordingly. To do so, go to Customizing for SAP Advanced Planner and Optimizer and choose Supply Chain Planning -> Production Planning and Detailed Scheduling -> Maintain Campaign Profile. See also To make automatic adjustment of setup/clean-out orders more flexible, you can use the /SAPAPO/PCM03_SETUP Business Add-In. For more information, see Business Add-In for Campaign Planning (New). For more information on new and enhanced functions in campaign planning, see Planning of Production Campaigns in PP/DS (New).
1.7.19.8 Deleting Empty Campaigns (New)

Use As of SAP APO 3.1, you can delete production campaigns that do not contain any orders. You can specify that the system deletes only those campaigns that: o o Belong to certain planning versions Are being processed by certain production planners
In addition, you can specify whether or not intergration to the SAP R/3 System is to be triggered for the deleted production campaigns in the deletion report. You can choose from the following functions to delete empty campaigns: o The Delete Empty Campaigns transaction You access the transaction from the SAP Easy Access screen of the SAP APO System by choosing Production Planning -> Interactive Planning -> Production Campaign. On the initial production campaign screen, choose Goto -> Delete Empty Campaigns. The background job with the /SAPAPO/PCM_DELETE_EMPTY program To create the background job, go to Customizing for SAP Advanced Planner and Optimizer and choose Supply Chain Planning -> Production Planning and Detailed Scheduling -> Production Campaign Planning -> Define Background Job for Deleting Empty Campaigns.
See also
________________________________________________________________
78 SAP AG
APO 3.1 ________________________________________________________________
For more information on new and enhanced functions in campaign planning, see Planning of Production Campaigns in PP/DS (New).
1.7.19.9 Business Add-Ins for Campaign Planning (New)

Use The following Business Add-Ins are available for campaign planning as of SAP APO 3.1: o /SAPAPO/PCM01_TXTOPT Business Add-In: Assign Campaign Description after Optimization In the standard system, a description is automatically assigned to production campaigns that were created after the PP/DS optimization run. This description is the same as that of the first output product of any of the orders in the production campaign. You can use the /SAPAPO/PCM01_TXTOPT Business Add-In to override the standard setting and assign descriptions to production campaigns according to your own criteria. /SAPAPO/PCM02_ALERTS Business Add-In: Eliminate Campaign Alerts You can use this Business Add-In to override the standard logic for eliminating campaign alerts and implement your own logic. Business Add-In /SAPAPO/PCM03_SETUP: Create Setup/Clean-Out Orders You can use this Business Add-In to override the standard behavior when generating setup/clean-out orders and implement your own logic. You may, for example, define your own criteria according to which both a setup and a clean-out order are to be created for a campaign. /SAPAPO/PCM04_PT_PRS Business Add-In: Change Representation of Campaign Bars You can use this Business Add-In to tailor the campaign bar label or color according to your own criteria. /SAPAPO/PCM05_ADDPOS Business Add-In: Control Addition of Orders to Production Campaigns This function used to be available as a customer exit. From now on, you can implement the function as a Business Add-In only. You can use this BAdI to carry out user-specific checks and decide whether or not a manufacturing order or planned order may be added to a production campaign in the SAP APO System. Business Add-In /SAPAPO/PCM06_DELSET: Control Removal of Orders from Production Campaigns This function used to be available as a customer exit. From now on, you can implement the function as a Business Add-In only. You can use this BAdI to carry out user-specific checks and decide whether or not an order that has been defined as a setup/clean-out order may be removed from a production campaign and deleted in the SAP APO System.
Effects on Customizing To implement the Business Add-Ins, go to Customizing for SAP Advanced Planner and Optimizer and choose Supply Chain Planning -> Production Planning and Detailed Scheduling -> Business Add-In. See also
________________________________________________________________
SAP AG 79
APO 3.1 ________________________________________________________________
For more information on new and enhanced functions in campaign planning, see Planning of Production Campaigns in PP/DS (New).
1.7.20 APO-PPS-MMP Model Mix Planning 1.7.20.1 Model Mix Planning: Planning Line Networks
Use
In the automotive industry, vehicles with many variants and assemblies with a high order volume are usually manufactured on the same takt-based production lines, which are linked in a line network. You can use Model Mix Planning to plan production for this form of manufacturing. The aim of Model Mix Planning is to create a production plan in the mid-term to long-term planning horizon. When doing this, the system must take into account the delivery dates, the available capacities and, if necessary, any existing restrictions. The system generates period packages (these are planned orders for a product that are grouped together and for which the start and finish dates lie in the same period (day or shift)) that are already assigned to the lines used for processing them. In the short-term planning horizon, the system uses the period packages to determine a sequence of orders with exact start and finish dates. The system takes into account delivery dates, available capacities, and restrictions. Up to now, you could use model mix planning only to plan individual lines. For SAP APO 3.1, it is now possible to use it to plan a whole line network. The line network can consist of many lines that run sequentially or parallel to each other and that can be used as alternatives to each other. To generate a production plan for all products that are manufactured on the same line network, model mix planning is executed as a multiline planning. That means, the system takes into account all lines in a line network and all products that are used or produced on the various parts of the line network. You can use interactive sequencing, as before, to process the planning results in the short-term horizon. You can change the sequence of orders on a line manually by using interactive sequencing or by accessing the corresponding procedure. In the new release, interactive sequencing has been enhanced with the following functions: o o o Manual rescheduling of orders to an alternative line Display tracking information for an order Starting actions for a particular order
In the following paragraphs, details are given about the prerequisites for planning line networks with groups of alternative lines and about the planning run:
Prerequisites for Multiple Line Planning To plan multiple lines, that is, to plan for a whole line network that can consist of alternative lines, you must use both the APO System and a DI System with Release DI 4.6C2. You use the DI System to maintain the iPPE data that consists of the product structure, process structure and the line design.
________________________________________________________________
80 SAP AG
APO 3.1 ________________________________________________________________
In the following segment, details are given only with regard to the data in the line design. You enter the following elements in the line design and maintain both the corresponding hierarchy relationships and the sequence of the individual elements: o o o o o Line network with parts of the line network Alternative line groups for the lines that can be used as alternatives for each other Lines Line segments, if necessary You must set an element from the line network as a Planning segment. You set the corresponding indicator either for a group of alternative lines or a line if this line does not belong to a group of alternative lines. You use the planning segment to determine the start of your planning. The system plans for this line and determines the start and end times for the orders by using the scheduling data for this line. You use forward scheduling or backward scheduling to calculate the start and end times on the lines that are before or after this line.
You create a line balance for the line network and enter a line balance rate, which is used to determine the takt time. Then you assign the activities of the process structure to the line segments so that the activities can be executed in the predefined takt time. For the products to be planned, you create the iPPE access object in the production version and enter the line network and part of the line network there. If a product can follow several alternative paths through a line network, then you represent this by using various parts of the line network. For each part of the line network, you must maintain an iPPE access object and a production version. You transfer the iPPE data to the APO . When you do this, the system automatically generates line resources in APO by using the data from the line nodes. You must then maintain the planning-relevant master data, such as the base rate and shift programs, manually in the APO System. This is necessary because the line resource forms the basis of the planning. The system uses this rate to determine the takt time that is used for scheduling in model mix planning. In the APO System, you must take note of the following new or changed IMG activities for model mix planning for multiline planning: o In the IMG activity Define LP Procedure, you check the settings for the linear program optimization procedure. This is a new optimization procedure for the planning of line networks with alternative line groups in the mid-term to long-term planning horizon.
In the IMG activity Define Procedure Packages, you define a procedure package for the multiline planning and assign a reference calendar to it. For the long-term horizon, you choose between the Materials planning procedure and the LP procedure. For the medium-term horizon, you must enter the LP procedure in the procedure package. For the short-term horizon, you choose between the genetic algorithm and prioritized equal distribution.
Process for multiline planning In the model mix planning run, the system examines the whole environment for the line/line network entered in the access screen. This environment is based on the relationships of the iPPE nodes and the production versions. In this way, the sytem determines all products that are affected and the possible paths through the line network.
________________________________________________________________
SAP AG 81
APO 3.1 ________________________________________________________________
In the next step, the system reads the Customizing settings and calculates the planning horizon. The system determines the available capacities of the line resources for each day of this horizon. The system uses the LP procedure to assign the existing requirements for each day to the lines taking available capacities and any predefined restrictions into account. The system generates period packages for these requirements. The system uses the start and end time of the period (shift or day) in which the planned of order is is scheduled as the start and end date of the planned order. Period packages that lie in the short-term horizon are split into planned orders with a lot size of 1 using the defined procedure, for example, the genetic algorithm. The system uses the procedure that is defined in Customizing to determine the sequence of orders with the exact start and end dates for these planned orders. Transferring the order sequences to production: If you link a production control system to APO, you can execute a data transfer between the APO System (as the planning system) and the external system (which is responsible for production or assembly control). After sequencing, you transfer the order sequences. This means that, at the request of the production control system, APO transfers sequence-optimized APO planned orders to the production control system in blocks for further processing. The following new functions are available: o Determining the parameters for transferring the planned orders You define how the transfer of the orders is to be carried out in the IMG activity Transferring Order Sequences to Production. You define, for example, that an ATP check is to be carried out for the orders before the transfer to determine whether all the necessary components are available. See also: ATP Check in the PP/DS. Synchronization with orders already received from the production control system When transferring the sequence-optimized APO planned orders from the APO system to the production control system, it is now possible to retransfer orders to the production lines which have already been transferred (and therefore released), but which have not yet been processed. New sysnchronous RFC interface This synchronous interface takes over from the previous asynchronous interface. Compared to the asynchronous interface, it is more simple to realize from a technical point of view. This is because the callback procedure is no longer necessary.
Effects on Customizing Customizing for Model Mix Planning was enhanced with the following IMG activities: o o o Define Procentage Smoothing Define LP Procedure Define the Transfer of Order Sequences to Production
The IMG activity Define Procedure Packageswas enhanced with the following individual procedures: o o LP Procedure Genetic algorithm (multilines) This algorithm can be used to optimize a group of alternative lines. This procedure can also be used to monitor and optimize several, independent individual lines that are
________________________________________________________________
82 SAP AG
APO 3.1 ________________________________________________________________
linked via a common product (a product with various production versions, the individual lines are entered in the iPPE access objects). o Percentage smoothing (mixing/date) For this form of percentage smoothing, you define whether you want to prioritize the date desired by the
customer or the even mixing of products when dispatching the orders to a line. You do this in a profile, which you define in the IMG activity Define percentage smoothing. Note also the rules for combining the individual procedures with the suitable planning basis. These are described in the IMG document Define procedure packages See also Release Information for iPPE Line Design
1.7.20.2 New functions in restrictions maintnenance for Model Mix Pla

Use New maintenance transaction the same as restriction maintenance for resource planning Before the new transaction can be used, you must execute the report /SAPAPO/ADD_SAP_ORIGINAL_LINES.
1.7.20.3 ATP Check for Planned Orders for RPM Products

Use In SAP APO 3.1 you can now use the ATP check for planned orders that you have planned with the Rapid Planning Matrix. It enables you to determine whether the required components, calculated by the matrix for the individual planned orders, are available for the planned requirements date. You can also use the ATP check for planned orders for products that you do not plan with the matrix, but explode in iPPE. The only methods you can use for the ATP check for planned orders are the product availability check and the check against forecast. You cannot use the other methods from the global ATP check, such as the rulesbased availability check. You can find more information on the ATP check for orders in the following Release Note: ATP Check in PP/DS. Prerequisites o o To be able to use the availability check for components in planned orders from the matrix, you must set the Fixing Allowed indicator in the IMG activity Maintain Global Settings. In Customizing for Production Planning and Detailed Scheduling, under Maintain Global Parameters and Defaults on the Execute tab page, you must enter PP as the business event in the Result of Planned Order Check field. The business event PP is provided as standard for checking planned orders.
________________________________________________________________
SAP AG 83
APO 3.1 ________________________________________________________________
You must create a check mode for the availabilty check for components. You do so in Customizing for the Global Available-to-Promise (Global ATP Check), in the IMG activity Maintain Check Mode. In the Assignment field, you can select any entry for the check mode. Select Standard in the Prod.Type field. You must define check instructions for the planned orders. You do so in the IMG activity Maintain Check Instructions by creating an entry for your check mode and assigning the business event PP. You must also make the following settings: ProdCheck Field: First step Prod.Alloc Field: No check Forecast Field: No check Rem Reqmt Field: Do not create remaining requirement StartProd Field: Availability check only, no production You can select any setting for the remaining fields because production is not to be triggered and a multi-level ATP check is not run.
You must define which components are to be checked in the ATP check in the APO. You do so by entering an ATP group, a check horizon and the check mode, which you defined for these components in Customizing, in the location product master of these components. If you wish to run the ATP check automatically when the order sequences are transferred, you must specify whether an ATP check is to be run and how the system is to react if all the ATP-relevant components are not available. You do so in Customizing for Model Mix Planning in the IMG activity Define Transfer of Order Sequence to Production in the ATP Mode field.
Running the ATP Check You can run the ATP check automatically when you transfer order sequences to a production control system. In this way, you can ensure that planned orders are only sent to production if their components are actually available. You can start the ATP check manually in planned order management on the ATP Check tab page. The check results are displayed immediately on this tab page. In this way, you can see at a glance whether certain components are still missing. In the ATP check, the system determines whether the components, determined by the RPM for the order and for which you have set the ATP check, are available for each planned order selected in planned order management, for example. The ATP group, which you have entered in the location product master for the components, determines the scope of the check, such as whether warehouse stock and planned receipts are checked. The available quantity of a component is displayed in planned order management as the confirmed quantity on the ATP Check tab page. The Pre-Allocated Stock indicator shows which components are missing. A planned order for an RPM product is not confirmed until all the ATP-relevant components are available. In the planned order for an RPM product, the APO fixes the confirmed components to protect them from any changes that arise in the next planning run. See also Release Information for the Rapid Planning Matrix
________________________________________________________________
84 SAP AG
APO 3.1 ________________________________________________________________
Release Information for Model Mix Planning
1.7.21 APO-PPS-RPM Rapid Planning Matrix 1.7.21.1 New Functions in the Rapid Planning Matrix
Use
In SAP APO 3.1, there is now an activity matrix for use in production planning using the Rapid Planing Matrix. The activity matrix is the basis for determining production activities for the production backflush in the APO. Previously you could use the production backflush to post the necessary components only. The system can now use the matrix to determine all the activities required for an order. The activity matrix can also be used to calculate the capacity requirements for the current demand program, to determine how many workers are needed, for example. With line balances in previous releases, you could only calculate capacity requirements for a theoretical model mix. As of this release, the capacity can be leveled exactly for each line segment for orders that have already been scheduled using various line balances. This allows you to compare different line balances to see which provides the best utilization of the capacity. The new functions are described in detail below: Introduction of the Activity Matrix
For each product you are planning you can specify whether an activity matrix is to be created during the planning run. You do so in transaction Maintain Additional Data for RPM Materials, using the Create Activity Matrix indicator.
The activity matrix is setup in the same way as the component variant matrix. The orders are in the columns and the activities are in the rows. The following data is contained in the matrix as attributes of the activity: o o o o o
Number of the activity
Line segment Costing data from the mode Production resource Duration from the mode
Displaying the Activity Matrix You can check the activity matrix using the transaction Display Matrix. On the Matrix Activities tab page in planned order management, you can display the activities that the matrix has determined for each planned order. The following information is displayed: o o o o Activity name and description Line segment where the activity takes place Start and end date of the activity Duration from the mode of the activity
Backflushing Production Activities
________________________________________________________________
SAP AG 85
APO 3.1 ________________________________________________________________
You can use the activity matrix during planning and backflushing in the same way as the component variant matrix to determine which activities are required. The modi of the selected activities contain the duration of the activity and the production resource that is used. The duration is used for scheduling, backflushing and calculating product costs. Refer to: Release Information for Production Backflushing: Backflushing Production Activities Displaying the Capacity Utilization The capacity utilization can be displayed as a graphic (bar chart) or a table. This function shows the capacity utilization of the production resource, which is assigned to the line segment and to the activity that takes place there, for each line segment on a given line. Only scheduled orders are referred to when calculating capacity requirements. This means you have to execute a model mix planning run before looking at the capacity utilization. Initial screen for the capacity utilization You must make the following entries on the initial screen: o o o Planning Version Production Line Line Balancing For the line balance, you can choose between the one that is valid for the selected period (standard line balance) and any other line balance. Production Period You must specify a period in which there are already orders that are scheduled on the line. The production interval, in hours, is used to determine the available capacity. For example, if you enter 1 hour, the system calculates the available capacity per line segment as follows: Number of production resources assigned to the line segment x 60 min. When two production resources are assigned, the available capacity is 120 min. within one interval. You can select one of the following settings for displaying the capacity requirements: Absolute The sum of times from all the activities that are to take place at a line segment is displayed for all the orders for the required time interval. Relative to the Available Capacity The absolute sum of the times from the activities is divided by the available capacity of the production resource.
Grafic Display of capacity utilization The graphic shows you the production resource assigned to each station (line segment). This can be a worker or an operating facility. The available capacity and the capacity requirements for the production resource are displayed as bars in the selected interval. You can see at a glance how the production resource is utilized. Tabular Display of capacity utilization The table shows you the values that are used to prepare the bar chart. ATP check for planned orders for RPM products In SAP APO 3.1 you can now run an ATP check for planned orders that you have planned with the Rapid Planning Matrix. The ATP check enables you to determine whether the required components, calculated by
________________________________________________________________
86 SAP AG
APO 3.1 ________________________________________________________________
the matrix for the individual planned orders, are available for the requirements date. Refer to: Release Information for the ATP Check for RPM Planned Orders
1.7.21.2 ATP Check for Planned Orders for RPM Products

Use In SAP APO 3.1 you can now use the ATP check for planned orders that you have planned with the Rapid Planning Matrix. It enables you to determine whether the required components, calculated by the matrix for the individual planned orders, are available for the planned requirements date. You can also use the ATP check for planned orders for products that you do not plan with the matrix, but explode in iPPE. The only methods you can use for the ATP check for planned orders are the product availability check and the check against forecast. You cannot use the other methods from the global ATP check, such as the rulesbased availability check. You can find more information on the ATP check for orders in the following Release Note: ATP Check in PP/DS. Prerequisites o o To be able to use the availability check for components in planned orders from the matrix, you must set the Fixing Allowed indicator in the IMG activity Maintain Global Settings. In Customizing for Production Planning and Detailed Scheduling, under Maintain Global Parameters and Defaults on the Execute tab page, you must enter PP as the business event in the Result of Planned Order Check field. The business event PP is provided as standard for checking planned orders. You must create a check mode for the availabilty check for components. You do so in Customizing for the Global Available-to-Promise (Global ATP Check), in the IMG activity Maintain Check Mode. In the Assignment field, you can select any entry for the check mode. Select Standard in the Prod.Type field. You must define check instructions for the planned orders. You do so in the IMG activity Maintain Check Instructions by creating an entry for your check mode and assigning the business event PP. You must also make the following settings: ProdCheck Field: First step Prod.Alloc Field: No check Forecast Field: No check Rem Reqmt Field: Do not create remaining requirement StartProd Field: Availability check only, no production
________________________________________________________________
SAP AG 87
APO 3.1 ________________________________________________________________
You can select any setting for the remaining fields because production is not to be triggered and a multi-level ATP check is not run.
You must define which components are to be checked in the ATP check in the APO. You do so by entering an ATP group, a check horizon and the check mode, which you defined for these components in Customizing, in the location product master of these components. If you wish to run the ATP check automatically when the order sequences are transferred, you must specify whether an ATP check is to be run and how the system is to react if all the ATP-relevant components are not available. You do so in Customizing for Model Mix Planning in the IMG activity Define Transfer of Order Sequence to Production in the ATP Mode field.
Running the ATP Check

You can run the ATP check automatically when you transfer order sequences to a production control system. In this way, you can ensure that planned orders are only sent to production if their components are actually available.
You can start the ATP check manually in planned order management on the ATP Check tab page. The check results are displayed immediately on this tab page. In this way, you can see at a glance whether certain components are still missing. In the ATP check, the system determines whether the components, determined by the RPM for the order and for which you have set the ATP check, are available for each planned order selected in planned order management, for example. The ATP group, which you have entered in the location product master for the components, determines the scope of the check, such as whether warehouse stock and planned receipts are checked.
The available quantity of a component is displayed in planned order management as the confirmed quantity on the ATP Check tab page. The Pre-Allocated Stock indicator shows which components are missing. A planned order for an RPM product is not confirmed until all the ATP-relevant components are available.
In the planned order for an RPM product, the APO fixes the confirmed components to protect them from any changes that arise in the next planning run.
See also
Release Information for the Rapid Planning Matrix Release Information for Model Mix Planning
1.7.22 APO-PPS-AHT Action Handler & Tracking 1.7.22.1 Action Handler (Enhanced)
Use
In SAP APO 3.0, you could choose Production Planning --> Manufacturing Execution --> Connection of the Production Control System in the SAP menu. The connection of the production control system comprised sequence transfer and the Action Handler. For SAP APO 3.1, the sequence transfer function was moved to model mix planning (APO-PPS-MMP). See
________________________________________________________________
88 SAP AG
APO 3.1 ________________________________________________________________
the release information Modell Mix Planning: Planning Line Networks for further details. The menu option Connection of the Production Control System was changed to Action Handler, and the Action Handler received its own component APO-PPS-AHT. The following enhancements were made in the Action Handler: Customizing and Master Data o New Actions The new actions allow you to carry out the following functions: o reschedule orders on alternative resources/lines within a group of alternative lines (only when iPPE is used) change the status of activities (only when iPPE is used) send SAPOffice notifications in the case of an error assign action networks to orders deallocate orders delete orders manually carry out actions for an action point display the variant configuration in production tracking carry out ATP checks for the components of an order (see also release information ATP Check in PP/DS)
Automated Processing with the Action Handler
________________________________________________________________
SAP AG 89
APO 3.1 ________________________________________________________________
In automated processing, the Action Handler automatically carries out certain actions for all planned orders as soon as the planned orders reach a certain action point during production (printing of documents, production tracking, backflush and so on). This functionality already existed in SAP APO 3.0 and has now been enhanced. The following functions are now available:
Archiving Tracking records, including all additional customer fields, are archived. This reduces the database content in the productive system as far as possible and improves the performance. Production Tracking in Planned Order Management (only available if iPPE is used) In planned order management, a new application in SAP APO 3.1, you can display production tracking information on planned orders (tab page Tracking Info) which you selected in the planned order overview. Improved Error Handling If errors occur during the execution of actions, you can send an express mail to the user responsible in addition to the SAPOffice mail. It is possible to implement this functionality per action point or per combination of action point and action. You can also implement user-defined error handling. In this case, the event ACTIONHANDLER_ERROR_OCCURRED is connected to the SAP Business Workflow. Instead of a mail, the person responsible then receives a work item in his SAPOffice-Mail inbox.
Manual Processing with the Action Handler
In manual processing, you manually start actions with individual planned orders in order to prepare production in a controlled manner (carry out ATP check for components first, then release orders and so on). This function is new in SAP APO 3.1. o Action Handler in Planned Order Management (only available if iPPE is used). You can use planned order management, a new application for SAP APO 3.1, in order to do the following, starting from the overview screen for planned orders: view the action network for planned orders you selected and manually carry out actions from there
manually carry out standalone actions without business-related dependencies which can be started at any point of the production process for planned orders you selected (tab page Action Handler). For further details, see the release information Planned Order Management.
Maintain settings for Action Handler
1.7.23 APO-PPS-PPC Confirmation 1.7.23.1 Processing of confirmations (changed)

Use Previously, confirmations were processed from SAP R/3 via its own CIF interface. The necessary settings for quantity propagation were made in SAP APO Customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults and in the location product master.
________________________________________________________________
90 SAP AG
APO 3.1 ________________________________________________________________
As of SAP APO 3.1 and R/3 Plug-In 2001.2, quantity propagation takes place in SAP R/3, which makes the confirmation process simpler and less open to errors. This eliminates the problem of there not being a return integration of quantity propagation to SAP R/3. In Customizing for SAP APO the fields of the corresponding IMG activity (Quantity Propagation, Component Adjustment and Remaining Duration Adjustment) are no longer needed and were therefore deleted. For the same reason, the corresponding confirmation fields were also deleted from the location product master in SAP APO. Effects on Data Transfer The confirmation in SAP R/3 is transferred to SAP APO as an order change. SAP APO adjusts capacity requirements and operation durations according to PPM entries or the current R/3 operation durations (if you are working without a PPM). Since SAP APO has scheduling autonomy, planned changes to dates are not transferred from SAP R/3. Dates are redetermined by SAP APO and, if necessary, transferred back to SAP R/3 (transaction /SAPAPO/CP3). Effects on System Administration In the application log in SAP APO you will no longer find the log for confirmations under subobject CONF: These are now under ORDER (order change method B). Effects on Customizing For the new processing of confirmations in R/3, certain settings have to be made in the production scheduling profile in the R/3 system that is connected to SAP APO. o Via the transaction CFO1 you see the screen Change View "Enhancements for Production Scheduling Profile in APO CIF". Place the cursor on the necessary production scheduling profile and choose Detail. o In screen section Confirmation the field Adjustment of Quantities after Confirmation corresponds to the deleted field Quantity Propagation. Via the field Rescheduling After Quantity Adjustment you can control whether the order should be rescheduled in SAP R/3 after quantity adjustment.
You can reach the function that used to be contained in the deleted SAP APO field Component Adjustment via customer exit PPAPO010. The relevant example coding is defined there.
A prerequisite for the new processing of confirmations in R/3 is the SAP note 429441. Note As of SAP R/3 4.6C you can start the quantity propagation in standard R/3 via the field Adjust Quantities in Orders to Actual Values on the screen Change View "Production Scheduling Profile: Details (transaction OPKP). If you set this indicator, the corresponding Plug-In functions are ignored. If you want to use these additional functions of the Plug-In you should leave this indicator blank and make the necessary settings in the screen Change View "Enhancements for Production Scheduling Profile in APO CIF" (see above).
________________________________________________________________
SAP AG 91
APO 3.1 ________________________________________________________________
1.7.24 APO-PPS-HEU Heuristics 1.7.24.1 Block Planning (enhanced)

Use
In SAP APO 3.1 you can now also execute block planning on single-mixed resources with bucket capacities. The blocks define the buckets. The bucket capacity of a block is derived from the productive time of the resources, and if necessary is corrected by an overload factor. In block planning with buckets for block-planned single-mixed resources, you can sucessively o Execute a "rough" finite scheduling, in which the system schedules operations finitely in the buckets Here, the time-continuous capacity of a block is not important for the resource availability in a block. Rather, the bucket capacity of the block is important. The system can only schedule an operation in a block if there is sufficent bucket capacity in the block.
Execute a detailed finite scheduling, in which the system checks the capacity availability in a block against the time-continuous capacity in the block The system can only schedule an operation in a block if it can find a sufficiently long slot for the operation in the block.
Resource In the single-mixed resource, you specify the data for the definition of the bucket capacity. The resource maintenance has been enhanced accordingly for SAP APO 3.1. o Standard capacity tab page So that the system can derive the bucket capacity of a single-mixed us resource from the productive time, you must set the new from block planning option in the buckets field. This setting automatically sets the dimension of the bucket capacity to time. You process further data for block planning with buckets (overload factors and cycles) on the block planning tab page under maintain blocks.
Planning parameter tab page So that a resources can be scheduled finitely, you must set the finite scheduling indicator, as before. In the new finite capacity field, you specify which capacity you want to schedule finitely - the
________________________________________________________________
92 SAP AG
APO 3.1 ________________________________________________________________
time-continuous capacity or the bucket capacity. In the detailed scheduling strategy , you can change between the capacities to be finitely scheduled. o Block planning tab page, maintain blocks function If you have selected the from block planning entry under buckets on the standard capacity tab page, two new columns will be displayed in the block maintenance: In the cycle type column, a symbol specifies that a new cycle begins at the beginning of the current block. The cycle ends at the start of the next indicated block, or with the last specified block. In the overload (%) column, the factor by which the bucket capacity of the current block is increased, is displayed as the productive time in the block (see below).
Detailed scheduling strategy For block planning with buckets in SAP APO 3.1, the new scheduling mode find buckets with free capacity has been introduced in the detailed scheduling strategy. You use this mode for finite scheduling of the bucket capacity of block-planned single-mixed resources and infinite scheduling of the time-continuous capacity of all resources. If you want to finitely schedule the time-continuous capacity of a block-planned single-mixed resource (and all other resources), you use the existing find slots scheduling mode. Other finite scheduling modes are not suitable. Reconciliation of production process model and resource A prerequisite for block planning with buckets is the consistent maintenance of the resource capacity data (time-continuous capacity and bucket capacity) and the resource consumption of the activities in the production process model (PPM). In the PPM, the duration of the activity must correspond to the bucket consumption of the activity. Block planning with productive times and equivalents The absolute duration of a block on a resource is determined by the start and end date. For block-planned single resources, the absolute duration corresponds to a productive time and possibly a quantity to be produced within a block. Previously, you could create blocks only with absolute duration. In SAP APO 3.1 you can create new blocks with the productive time in seconds or an equivalent in any unit of measurement. When shifting blocks, the productive time is retained and not the absolute duration of the blocks. For the definition of equivalents to the productive time, you specify a conversion factor and the desired unit in the block maintenance. To do this, select the Conversion of the productive time tab page under Further Settings on the Interval tab page. To display the equivalent in block maintenance, select Further Settings, and set the Productive time in equivalent indicator on the Display Options tab page.
1.7.24.2 PP Heuristics for Sales Order Oriented Planning (new)

Use In SAP APO 3.1 there are three new heuristic algorithms that you can use for sales order oriented planning. With this type of planning, you can convert planned orders or purchase requisitions into production orders or purchase orders only if these orders are used exclusively to cover sales orders. Using the requirements ascertainment algorithm (/SAPAPO/HEU_REQ_ASCERTAIN) you can determine the open planned independent requirements for selected products, that is, the planned independent
________________________________________________________________
SAP AG 93
APO 3.1 ________________________________________________________________
requirements which are still not matched by any sales orders. Using the requirements ascertainment results you can identify the customers for whom you have planned the planned independent requirements and can ask the customers to issue sales orders by a specific deadline. Using an adjustment algorithm, you can delete the open planned independent requirements and make multi-level reductions to the related planned orders and purchase requisitions, down to the initial product level, after the deadline. As an option, you can make adjustments for selected products (algorithm /SAPAPO/HEU_ORGANIZE_VIA_PEGID) or selected orders (algorithm /SAPAPO/HEU_ORGANIZE). You organize the time flow using the requirements ascertainment horizon and the - shorter - adjustment horizon that you specified location product-specifically in the location product master in SAP APO 3.1.
SAP delivers standard heuristics on the basis of these algorithms. In the customizing for Production Planning and Detailed Scheduling (PP/DS) under Maintain Heuristics, you can define heuristics with your own settings. If you want to use these heuristics in the order view, you must enter the heuristics in the heuristic profile that you are using for the order view, under Maintain Heuristics Profile.
1.8 APO-ATP Global Availability Check

1.8.1 Recreation of Receipt Elements
Use
As of SAP APO 3.1, you can use this function within Capable-To-Promise (CTP) or a multilevel ATP check.
This function enables receipt elements that have been created within CTP or a multilevel ATP check to be deleted before a new ATP check. A possible earlier requested delivery date, for example, can therefore be returned to planning.
This function is only supported for make-to-order production.

Customizing has been enhanced for the function. In the work step Maintain Check Instructions, you can set the indicator Re-create receipt elements. In the location-specific product master (ATP tab), you can define a horizon for re-creating receipt elements.
See also
Release information Multilevel ATP check Release information Conversion of ATP tree structures into Procurement Proposals of PP/DS For detailed information see the online documentation.
1.8.2 Multilevel ATP Check

Use
________________________________________________________________
94 SAP AG
APO 3.1 ________________________________________________________________
As of SAP APO 3.1, you can use the multilevel ATP check. There are industry areas (for example, PC assembly) in which a large part of the value-added activity arises at final assembly. The assemblies on the lower production levels have already been produced or procured before the sales order comes in, but final assembly is only initiated when the sales order arrives. The multilevel ATP check is usually used in these areas, since the components that are required to produce an end product are checked when a sales order is created. A particularly suitable use of the multilevel ATP check is sales order entry for configured products. A sales order can only be accepted when all required components are available. Which components are needed specifically, however, depends on the configuration requested by the customer and can only be checked at the time of sales order entry. Further uses are order entry via the internet as well as within heterogeneous system landscapes. In contrast to Capable-To-Promise (CTP), no receipt elements are created during the multilevel ATP check in the order network of SAP APO. Instead, the check results are stored in the ATP tree structure. Receipt elements are only generated later when the ATP tree structure is converted in PP/DS. This allows improved performance during the check. However, statements on capacity availability can only be rough (on a daily basis) and not as detailed as in CTP (in seconds). As long as no receipt elements exist, the ATP tree structure exists in the SAP APO database. Requirements at component level are represented as aggregated quantity assignments. The ATP tree structure and the aggregated quantity assignments are deleted and/or reduced directly after the ATP tree structure is converted into receipt elements. The multilevel ATP check supports the following functions: o o o o o o o o Scope of check in the product availability check for components Product allocation at finished product level Check against the forecast at component level Mapping of capacities using product allocations Exclusion of specific components from the check (that is, complete confirmation of the components without check) Return of data via the components/characteristics that have lead to a delay and/or reduction of the confirmation (see missing parts list) Rules-based ATP check at component level, whereby a location determination generates a stock transport requisition, a product substitution, a product substitution order in PP/DS Cross-system third-party order processing at finished product level, together with multilevel ATP check
Effects on Customizing The following enhancements have been made in Customizing so that a multilevel ATP check can be carried out. For detailed information on the settings for the multilevel ATP check, see the online documentation. o o In the check step Maintain Check Mode, you can now select the value multilevel ATP check in the production type field. In the work step Maintain Check Instructions, you define the Generation of a remaining requirement for the components as well as a conversion mode. You can also define a business event for the multilevel ATP check in the check instructions.
________________________________________________________________
SAP AG 95
APO 3.1 ________________________________________________________________
If you would like to define another determination of the rule strategy for the rules-based ATP check at component level, you can define a separate business transaction in the work step Create business transaction for the multilevel ATP check.
See also Release information Conversion of ATP tree Structures into Procurement Proposals of PP/DS Release information Recreation of receipt elements For detailed information on the multilevel ATP check and its constraints see the online documentation.
1.8.3 Conversion of ATP tree structures into PP/DS procurement pro (new)
Use In a scenario with an OLTP system for sales order processing and an SAP APO system for the Global Availabile-to-Promise Check (Global ATP) and for Production Planning and Detailed Scheduling (PP/DS) you can convert ATP tree structures into PP/DS procurement proposals in SAP APO 3.1. With the corresponding check configuration, a rules-based ATP check or a multi-level ATP check - new in SAP APO 3.1 - executed on a sales order, can determine which and how many of the finished products required by the customer are not available in the check location, but could be procured through stock transfers from other locations (location substitutions with rules-based ATP) or through final assembly of available components in Production Planning and Detailed Scheduling (multi-level ATP); here, components may be replaced by alternative components (product substitution with rules-based ATP). The result of the ATP check in the sales order is ATP tree structures that the system creates in SAP APO when saving the sales order; here, there is one ATP tree structure for each request schedule line in the sales order. An ATP tree structure contains, for example, the requirements data (dates, quantities and sources of supply) for the procurement proposals that PP/DS should create for the sales order (stock transport requisitions, planned orders or product substitution orders). PP/DS creates the procurement proposals by converting the ATP tree structures and schedules the procurement proposals on the resources. Depending on the position of the requirements date of an ATP tree structure, the PP/DS horizon and the scheduling horizon for ATP tree structures , conversion is either automatic immediately after saving the sales order, or the user converts the tree structures at a later time. Previously, if you changed an already existing ATP-checked sales order and executed an ATP check again, the system would check against the available PP/DS procurement proposals (that were created from the original ATP tree structure, for example). This may mean that if you bring a date forward in the sales order, the system cannot move the confirmed date forwards; procurement proposals still exist, even if they are delayed. The order may be split if a quantity in the sales order is increased. You can use the new recreate receipt elements indicator in the check instructions to specify if, during a new ATP check, the system should ignore the procurement proposals created from the old ATP tree structure and delete the changed sales order when saving. However, it can only ignore and delete procurement proposals whose availability dates are within the horizon for recreation of receipts specified in the location product master, and whose statuses allow for this. You call up the the user-controlled online or background conversion in the area menu for Production Planning under Environment.
________________________________________________________________
96 SAP AG
APO 3.1 ________________________________________________________________
Effects on System Administration If you have used Capable-To-Promise Processing (CTP processing) until now, check if you can replace this with a multi-level ATP check. (You set CTP processing if you are planning with Characteristics Dependent Planning (CDP), and if you want to schedule the procurement proposals on the resources of the sales order with a more detailed consideration of the resource availability. You use the multi-level ATP check if you are planning with variant configuration. Here, it is possible to split the order through product and location substitution; the product allocation allows for a rough check of the resource availability.) Effects on Customizing o o You define the scheduling horizon for ATP tree structures in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. When scheduling procurement proposals, the system uses the strategy profile that you have specified in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. For user-controlled conversion you can specify a strategy profile interactively under settings. You define check instructions in the customizing for Global ATP under Maintain Check Instructions.
o See also o
Release information on Multi-level ATP check Recreating receipts
Documentation on Production Planning and Detailed Scheduling
1.8.4 ATP check in PP/DS (new)

Use In SAP APO 3.1 you can execute an ATP check for the following orders in the active planning version 000 in Production Planning and Detailed Scheduling (PP/DS): o In-house production orders For an in-house production order (planned order or production order), the system checks the quantity in which the order components planned in SAP APO are available. The ATP check can derive a confirmed quantity for each order product by using a correlation calculation using the component quantities confirmed at the requirements date, that is, it can derive the quantity of the order product that the component can actually supply on the order availability date. Stock transport requisitions For each order item in a stock transport requisition, the system checks the quantity in which the product to be transferred can be confirmed in the source location.
The system checks if it is possible to make a total delivery of the order on the availability date. It is not possible to split the order into available partial quantities. For the ATP check, you can use the product availability check and the check against forecasting. Products that are planning relevant are those for which you have specified a check mode and an ATP group in the
________________________________________________________________
SAP AG 97
APO 3.1 ________________________________________________________________
location product master. The ATP check is integrated in the following PP/DS applications: o Interactive planning You can call up the ATP check in the product view, in the order processing view, in the receipt view and in Planned Order Management. Order opening In the SAP APO system, you can trigger the opening of production orders and stock transfer orders in the SAP R/3 system. For the conversion of planned orders and stock transport requisitions into production orders or stock transport orders, the system can automatically execute an ATP check on the basis of a conversion rule for the planned orders or for the stock transport requisitions. You can make user-specific settings that the system should only allow the opening if all the components are fully confirmed.
Effects on System Administration Often in SAP APO 3.0A, planned orders and stock transport requisitions are transferred to the SAP R/3 system so that an ATP check can be executed there. If you are using SAP APO 3.1, check if it is now sufficient to transfer only the orders for which the conversion indicator is set, into the SAP R/3 system. You can make the relevant settings in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. Effects on Customizing o Business events You can use various business events to control the ATP check in PP/DS according to which order type is being checked (planned order, production order or stock transport requisitions), and if the ATP check should be executed with or without a conversion check. For example, you make different checks on production orders than on planned orders. You define business events in the customizing for the Global Availability Check (Global ATP Check) under Maintain Business Events and enter them in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. ATP check for order opening You can use a conversion rule to specify that the SAP APO system should execute an ATP check during the conversion of a planned order or a stock transport requisition into a produciton order or a stock transport order. You define conversion rules in the customizing for Production Planning and Detailed Scheduling under Maintain Conversion Rules. You can enter a globally valid conversion rule in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. In the location product master, you specify the conversion rule that is valid for a product. Using the roles that you assign to the user, you specify if the user can also execute conversion if there are missing components. Sequence when checking several orders The order confirmation results can depend on the sequence in which the system executes the ATP check. You use a sort profile to specify this sequence. You define sort profiles in the customizing for Production Planning and Detailed Scheduling under Maintain Sort Profile.
________________________________________________________________
98 SAP AG
APO 3.1 ________________________________________________________________
1.8.5 APO-ATP-BF Basic Functions 1.8.5.1 Correlation Calculation

Use
As of SAP APO 3.1, a correlation calculation takes place for those correlation groups for which an ATP check is also carried out in SAP APO. If the calling system is an SAP R/3, the correlation calculation corresponds to the correlation of delivery groups for sales document items and order BOMs. The correlation calculation has been enhanced considerably in comparison to the delivery group correlation. You can influence the delivery group correlation in SAP R/3 or leave it as it is. The correlation calculation has been enhanced in SAP APO by the following functions: o o o o A quantity correlation can also be carried out for the delivery group You can define how the system should behave for partial quantity confirmations You can define a correlation type You can activate/deactivate the correlation calculation in backorder processing You have the option of simulating the correlation calculation via the execution mode You can carry out the ATP check for the entire delivery group.
In the work step Maintain Correlation Profile you can change the correlation profiles provided by SAP or create new ones. Note that you change your previous delivery group correlation when you change the standard profiles. For more information see the documentation for this work step.
1.8.5.2 Enhancement in the ATP Tree Structure Display

Use As of SAP APO 3.1 entry into the display and output of the ATP tree structure has been enhanced considerably.
You can call the ATP tree structure display from the SAP Easy Access Screen via Global ATP -> Environment -> Technical Monitors -> ATP Tree Structures.
See also
For more information see the documentation for the ATP tree structure display.
________________________________________________________________
SAP AG 99
APO 3.1
________________________________________________________________ 1.8.5.3 Changed ATP Tree Structure Data Model (enhanced)

Use The data model of the ATP tree structure has been fundamentally enhanced for 3.1. Therefore ATP tree structures that possibly exist can not be transferred after a release upgrade from SAP APO 3.0 to SAP APO 3.1. This release information describes the prerequisites and actions to be carried out with regard to the component Global ATP for a release upgrade from SAP APO 3.0 to SAP APO 3.1, if you are using ATP tree structures in one of the following scenarios:
o o o
Backorder processing Cross-system third-party order processing (ALE) using persistent temporary quantity assignments (see also persistency indicator)
ATP check from a connected SAP CRM system (up to and including SAP CRM 3.0) using persistent temporary quantity assignments
Effects on Existing Data
Depending on the scenario, you carry out the following actions: Backorder processing o No open backorder processing (that is, backorder processing that is not yet updated) can be transferred and updated later in release 3.1. For that reason, all existing backorder processings should be deleted. From the SAP Easy Access screen select Global ATP -> Backorder Processing -> Delete Backorder Processing. Leave all selection fields initial and deselect the Test indicator. Cross-system third-party order processing (ALE) o All ALE third-party processes must be completed. The sales order in the sales system must be saved and created completely in the delivery system and updated. In this regard, order IDocs that are not yet transferred or are stopped must be sent before the release upgrade. Otherwise, the order loses its ATP confirmation in the delivery system. o CRM scenario All orders in SAP CRM for which an ATP check has been carried out in SAP APO must be saved and transferred to the connected system and updated there. In this regard, orders that have not yet been transferred must be sent before the release upgrade. Otherwise the order acquires no ATP confirmation in the OLTP system. All ATP tree structures that still possibly exist must then be deleted. Select transaction SE38 and enter the program name /sapapo/dm_atree_remove_trees. Leave all selection fields initial and execute the report. The preparations for the release upgrade with regard to the ATP tree structures are thereby completed.
1.8.5.4 Deleting ATP Tree Structures

Use
As of SAP APO 3.1 it is possible to delete ATP tree structures that are in the database. Using the report /SAPAPO/DM_ATREE_REMOVE_TREES all selected ATP tree structures and their associated temporary quantity assignments will be irrevocably deleted. For this reason, you must make sure that that ATP tree structures that you want to delete are no longer being used. You should only use this report in exceptional cases. See also Changed ATP Tree Structure Data Model (enhanced) Enhancement in the ATP Tree Structure Display
1.8.5.5 Regenerate temporary quantity assignments from the ATP tree

Use As of SAP APO 3.1, using the report /SAPAPO/GENERATE_TMP_ASSIGN, you can regenerate temporary quantity assignments that are specific to an order from the ATP tree structure. Using this report you can restore temporary quantity assignments for dependent requirements that were deleted by mistake (through the initialization of a liveCache, for example.) You should only use this report in exceptional cases.
________________________________________________________________
SAP AG
APO 3.1 ________________________________________________________________
1.8.6 APO-ATP-EST Explanation & Simulation Tool 1.8.6.1 Enhancement in the Explanation and Simulation Component
Use
As of SAP APO 3.1, a results overview is shown as a reaction to a rules-based ATP check and/or to a multilevel ATP check. This results overview replaces the APO Rules-Based Availability Check screen. Depending on the progress of the ATP check, you can branch from the results overview to the following new detail views: o o o Correlation groups Missing parts list Undeleted orders
As of SAP APO 3.1 you can branch from the delivery proposal screen and/or from the confirmation, to the following new detail views (depending on the progress of the ATP check):
o o o o o
See also
Scheduling log Missing parts list Undeleted orders Planning log Results details for the multilevel ATP check
For more information see the online documentation.
1.8.7 APO-ATP-BOP Backorder Processing 1.8.7.1 Enhancements in Backorder Processing

Use
In the following areas of backorder processing, enhanced functions are available as of SAP APO 3.1: o Worklist You can include the correlation calculation and the ATP check of a correlation group in the backorder processing worklist. You thereby have the option of simulating the correlation calculation (depending on the execution mode). An ATP check can be carried out as well for the entire correlation group. If the calling system is an SAP R/3, the correlation group is a delivery group. Filter
________________________________________________________________
100 SAP AG
APO 3.1 ________________________________________________________________
By entering a component and the indicator multilevel ATP, you can define that sales orders that contain components that have been checked within a multilevel ATP check should be included in the backorder processing. You can define with regard to the confirmation situation that the confirmation lock is taken into account in backorder processing. o o Sort profile You can include the correlation group as a sort criterion in the sort profile. Order items lock You can use the cross-system lock (CSL) to lock the order items while they are being processed in backorder processing. The lock is only restricted to SAP APO. In other words, the order items can still be changed in the OLTP system (without lock problems). The order items can not be included in further backorder processing until the update of the first backorder processing is completed. The lock is released per token manager. Using transaction SM30, generate a new entry with the token manager (logical system) and token manager number '01', in the table CSL_M. The indicator 'Lock and Monitoring Activation' specifies if the token manager is active. If the order items are locked, it must be set to LCT (meaning: 'CSL locks active, with reference tracing)'). Alternatively, the lock can be activated via the table CSL_EOAC per lock object. The lock object used in backorder processing is 'ATP_ITEM'. Results list You can, among other things, branch from the output to the display of the Transportation and Shipment Scheduling results. The delivery date is now displayed. For more information see the documentation for the results list. Reports A monitor is now available. You can use this to check the status of backorder processing. From the SAP Easy Access screen select Globale ATP -> Backorder Processing -> Backorder Processing Monitor. Furthermore, you can now compare the first confirmation with the current confirmation. From the SAP Easy Access screen select Global ATP -> Backorder Processing -> Backorder Processing Comparison.
1.9 APO-AMO Alert Monitor

1.9.1 Display of alerts (enhanced)
Use
The following enhancements exist in SAP APO 3.1 for displaying alerts in the order view: o Alert-relevance of a product In the Requirement tab page of the location product master, in the new product alerts field, you can set If the system determines direct alerts for the product If the product is relevant for network alerts As before, you use the PP/DS alert profile to specify if and which alerts the system should display in the planning interface or in the alert monitor.
________________________________________________________________
SAP AG 101
APO 3.1 ________________________________________________________________
In the standard delivery, the option determine direct alerts, relevant for network alerts is set. o Network alerts for receipts and requirements Previously, you could use the Display network alerts indicator under Set order view/periodic product view in the customizing for Production Planning and Detailed Scheduling to specify if the system should display network alerts; in doing this you could not distinguish between receipts and requirements. In SAP APO 3.1 you can make separate settings for if the system should display network alerts for receipts and requirements. The old Display network alerts indicator is therefore replaced by the following new indicators: Display network alerts for receipts Display network alerts for requirements
In the standard delivery, a setting is made so that the system does not display network alerts for receipts and requirements. So that the system displays network alerts, set the corresponding indicator in the customizing under Set order view/periodic product view.
1.10 APO-OPT Optimization

1.10.1 APO-OPT-SNP Supply Network Planning 1.10.1.1 Cross-Period Lot Size Planning (new)
Use
As of SAP APO 3.1 you are able to run cross-period lot size planning as part of campaign planning within Supply Network Planning (SNP) as a lower level of actual campaign creation within Production Planning and Detailed Scheduling (PP/DS). In some industry sectors (such as the process industry) setup activities have a great influence on lot size planning. If the setup costs are relatively high in comparison to the storage costs, orders are grouped into large lots, to save on set up costs. Until now, however, the SNP optimizer was only able to plan lot sizes that were limited to one bucket. Here, the optimizer would schedule one setup activity in each period and would calculate the specified setup consumption and setup costs in the appropriate production process model (PPM). As of SAP APO 3.1, the SNP optimizer is also able to plan cross-period lot sizes. Here, if the same production process model (PPM) is being used to produce a product in the current period, the optimizer takes into account the setup statuses from the previous period. This means that the optimizer still only schedules one setup operation per lot size. The system then calculates the setup costs and setup consumptions (fixed resource consumption and material consumption) that were defined in the PPM for resources that have been marked with the Cross-Period Lot Size indicator. The optimizer is also able to take into account setup statuses that result from already planned PP/DS orders.
________________________________________________________________
102 SAP AG
APO 3.1 ________________________________________________________________
Campaign Planning - The Process In campaign planning within Supply Network Planning, you are also able to execute rough-cut planning. For example, you could define a business process for the process industry in such a way that a cross-network planning is only run using the SNP optimizer once the forecast data has been transferred from Demand Planning to SNP. For long setup times, it is a good idea to have a rolling monthly planning. The SNP planned orders created by the SNP optimizer correspond to a campaign that is created at a later point in Production Planning and Detailed Scheduling. The SNP planned orders are then converted into (multiple) PP/DS orders. In PP/DS, you then create the actual campaigns (detailed scheduling) for the individual production levels. Here, in order to produce a consistent plan, it is possible to re-run the SNP optimizer on a production level after each campaign is created. See also release information on planning of production campaigns in PP/DS. Automatic Generation of SNP PPMs from PP/DS PPMs As of SAP APO 3.1 it is also possible for you to have the system generate SNP PPMs for lot size margins, as cross-period lot size planning requirements in SNP are supported. See also release information on SNP PPM generation with lot size margins.
In Customizing for Supply Network Planning, which you find by following menu path: SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Supply Network Planning (SNP)-> Profiles -> Define SNP Optimizer Profiles, in addition to the SNP optimization run settings, you must also maintain the field Cross-Period Lot Size Planning and, if required, also activate the Cross-Period Lot Size Planning indicator. You must also choose the discrete optimization method. For more information, see the IMG documentation define SNP optimizer profiles and the appropriate F1 field-level help.
1.10.1.2 New Design of the SNP Optimizer Profile and SNP Optimizer Window (enhanced)
Use
As of SAP APO 3.1, the user interface design of both the SNP optimizer profile and the optimizer window in interactive SNP planning is clearer and more user-friendly. There are also new functions and settings available. SNP Optimizer Profile The possible SNP optimizer profile settings have now been divided into several tab pages to provide a clearer layout. This means there is now a clear distinction between linear optimization methods and discrete optimization methods for you to choose between. In the header data of the profile you first choose one of the methods. You are then able to activate the constraints for linear and discrete optimization on two separate tab pages, and on additional tab pages you choose model parameters, solution methods, and so on. Options that are unavailable for the method you have chosen are grayed out.
________________________________________________________________
SAP AG 103
APO 3.1 ________________________________________________________________
The SNP optimizer profile also has the following new functions and settings: o Safety stock (which until now could only be set in master data): You are able to define whether you want the optimizer to take safety stock into account. If you do want it to, you are then able to specify whether you want the penalty costs calculation to include deviations from the safety stock as an absolute value or as a percentage. Shelf life (which until now could only be set in master data): You are able to define whether you want the optimizer to take into account the shelf life of products, and if so, whether you want to continue using the product after it has expired (has passed its shelf life), or whether you want to dispose of it. If you do want to continue using it, you have the option of specifying whether you want to optimizer to use the procurement costs that have been maintained for the location product as penalty costs, or whether you want it to use penalty costs that are not dependent on the product. Fixed material consumption: If you have chosen discrete optimization methods, you are able to define whether you want the optimizer to take into account fixed material consumption in the production process model (PPM). Stock on hand: You are able to define whether you want the optimizer to calculate the stock on hand on the basis of the average stock on hand or on the basis of the stock that is on hand at the end of the period. Heuristic start solution: If you want to find an initial valid solution quickly, you are able to specify that you want the system to start running a heuristic that does not use linear programming. Lot size planning: You are able to define whether, as part of lot size planning, you want the optimizer to take cross-period lot sizes into account and how you want it to process setup statuses (see also the release information on cross-period lot size planning). Discretization horizon: You are now able to specify whether you want the system to consider discrete constraints for all time buckets (days, weeks, and so on, as defined in the planning buckets profile), or a concrete horizon that you define independently of the planning bucket profile. Optimizer Window in Interactive SNP Planning The window of the SNP Optimizer that you access from interactive SNP Planning, has also been given a more user-friendly design. The following new display options are available: o o New tab page Message log: This tab page displays messages from the previous optimization runs. Before now, this function was only accessible from the Optimizer Log Data transaction. The Optimization tab page now displays information on interim solutions during the optimization run.
o o
See also IMG activity documentation define SNP optimizer profiles.
________________________________________________________________
104 SAP AG
APO 3.1 ________________________________________________________________
1.11 APO-CPR External Procurement

1.11.1 Converting Purchase Requisitions into Purchasing Documents
Use
As of SAP APO 3.1: o o o Subcontracting purchase requisitions can be automatically converted into subcontract orders
Purchase requisitions referencing an OLTP scheduling agreement can automatically be converted into scheduling agreement delivery schedule lines
Subcontracting purchase requisitions referencing an OLTP scheduling agreement can automatically be converted into subcontracting scheduling agreement delivery schedule lines
1.11.2 APO-CPR-SCH Delivery Planning 1.11.2.1 Dynamic Stopping of Scheduling Agreement Releases (New)
Use With SAP APO 3.1, you can stop scheduling agreement releases dynamically. (Dynamic stopping means that an SA release is stopped because it varies so greatly from the last SA release transmitted that the tolerance check identifies a change in the delivery schedule situation beyond the tolerance limits set.) With this function, the relevant SA release is created but initially held back from the message output process (XML, printing, etc.) (i.e. stopped).
Stopped SA releases can then be released (cleared, given the green light) by the responsible materials planner with the Process SA Releases function.
Effects on Customizing If you wish to use this function, you must make the appropriate settings in the SA release creation profile on the new Dynamic Stopping tab page.
1.11.2.2 Several Deliveries for Scheduling Agreement Release (New)

Use You use this function to specify whether any of the last deliveries are to be notified to the vendor in the SA release and, if so, how many.
You can notify your vendor of not more than the last nine deliveries.
________________________________________________________________
SAP AG 105
APO 3.1 ________________________________________________________________
If you wish to use this function, you must make the necessary settings on the Last Deliveries tab page in the release creation profile.
1.11.2.3 New Functions in Scheduling Agreement Release Processing (changed)

Use
As of SAP APO 3.1, the functionality of Display SA Releases (transaction /SAPAPO/PWBSCH3) has been extended. For this reason, the transaction has also been renamed as Process SA Releases. Process SA Releases includes the following new functions: o o @A6@ Last Deliveries You can display the last deliveries for a scheduling agreement release. @3R@ Action Log for an SA Release You can invoke a display of the processing steps that have been carried out to date (e.g. stopped, released). @57@ Display Product Planning Table You can branch directly to the product planning table. @48@ Display Source of Supply You can display the external procurement relationship for a scheduling agreement release. @B1@ Release Stopped SA Releases You can release (clear, give the green light to) a stopped SA release. For more information on stopped SA releases, refer to the SAP Release Note Dynamic Stopping of Scheduling Agreement Releases (New). @15@ Output SA Releases You can output a scheduling agreement release directly.
o o o
1.11.2.4 New Print Form for the Output of Scheduling Agreement Release
Use As of SAP APO 3.1, a new layout is available for scheduling agreement releases. The new layout reflects the automobile industry standard and allows further information such as packing information or follow-up material to be included on the printout. The form used (/SAPAPO/SF_SARELEASE_TEMPLATE) is based primarily on the German VDA recommendation 4904 and employs a landscape format. The form can be used for outputting delivery schedules in hardcopy form or as fax or e-mail messages. It is also used for displaying and printing scheduling agreement releases via the Supplier Workplace.
The previous print form (/SAPAPO/SF_SARELEASE_LANDSCAPE) can still be used.

Depending on which of the two print forms you wish to use, you must use the relevant processing method for
________________________________________________________________
106 SAP AG
APO 3.1 ________________________________________________________________
the messaging action in question. Proceed as follows: 1. 2. Choose the Settings for Processing button in Customizing for Collaborative Procurement under Define Actions for Messages -> Application -> Action Profile -> Action Definition -> Processing. Here choose: Processing method EXEC_SMART_FORM_SAR for the form /SAPAPO/SF_SARELEASE_TEMPLATE
Processing method EXEC_SMART_FORM_SAR_QUER for the form /SAPAPO/SF_SARELEASE_LANDSCAPE
1.11.3 APO-CPR-SCT Subcontracting 1.11.3.1 Transfer Subcontracting PPM to Source Location via CIF (New)
Use If you use a planning approach with a source location, up to now you had to create the relevant PPMs in the APO system of the source location manually.
As of SAP APO 3.1, you can transfer subcontracting PPMs to the source location via CIF. To do so, you must assign the production version to an info record in your OLTP system and transfer the object Subcontracting PPM to the APO system of the source location with the aid of the integration model.
1.12 APO-INT Interfaces

1.12.1 Processing of change pointers (enhanced)
Use
By making entries in the selection screen Selection and Transfer of Orders you can control how SAP APO processes change pointers. In SAP APO 3.1 this selection screen has a new design including some new functions: o o In the screen section Products you can filter the selected change pointers according to product/planner. In the screen section Flow Control you can determine in the field Block Size how many change pointers are to be processed per block. The system processes the change pointers selected for transfer on a block basis, depending on the figure entered here. As standard, the block size is set to 1000. As the block size increases, so does the amount of memory needed. For every block processed an application log is written. Under Processing Direction you can also choose between two processing directions: from the product: using the product/planner entered as a basis the system determines the
________________________________________________________________
SAP AG 107
APO 3.1 ________________________________________________________________
associated change pointers. from the change pointer: using the selected change pointers as a basis, the system filters out those change pointers that meet the filter criteria. The system only evaluates these fields if you enter filter criteria under Products. Both processing directions have an effect on performance. It is recommended to use tests to determine which processing direction allows higher performance in your system. o In screen section Background Processing you can use the indicator Detailed Job Log to gain detailed information from the job log. Processing of change pointers for campaigns For changes to campaigns the system also writes change pointers for associated orders (planned/production orders). This is also true if you add an order to or remove an order from a campaign. Always transfer the change pointers for campaigns and associated orders together. The system searches for change pointers with the publishing type In-House Production that do not meet the selection criteria entered but that are, however, components of the selected campaigns. These change pointers are displayed at the end of the list of change pointers and can be selected for transmission. -
1.12.2 Deltareport3 (new)

Use As of SAP APO 3.1 and R/3 Plug-In 2001.2 the compare/reconcile of data between SAP APO and SAP R/3 takes place via a new report (transaction /SAPAPO/CCR, report /SAPAPO/CIF_DELTAREPORT3). As well as improved performance in comparison to the previous report (/SAPAPO/CIF_DELTAREPORT2), this report offers three additional fields in the screen section Objects for Check: o o o Confirmations Shipments Note, that a comparison of shipments in R/3 requires SAP R/3 4.6B or higher. Use Table VBBE for Sales Order Comparison under the field Sales Orders This field controls whether the system uses the current entries in the table VBBE (Single Records for Sales Requirements) to determine requirements for the comparison of sales orders or whether it determines the requirements from the document flow. If this indicator is set, the current entries in the table VBBE are used. That is, the table is not regenerated. Note, that in this case you should carry out the report SDRQCR21 in R/3 at as close to the same time as possible. If you do not, this can lead to faulty results in the comparison. If this indicator is not set the table VBBE is regenerated before the comparison. This corresponds to the report SDRQCR21 in R/3 and can lead to a long runtime.
________________________________________________________________
108 SAP AG
APO 3.1 ________________________________________________________________
1.12.3 Deactivating source of supply determination (new)

Use Previously, source determination was automatically executed when transferring a purchase requisition from SAP APO to SAP R/3 if the purchase requisition was not yet assigned to a source of supply. If a unique source of supply could be determined, this was assigned to the purchase requisition.
In the APO CIF for R/3 Plug-In 2001.2, you can deactivate this automatic source determination by using the transaction CIFPUCUST01. If you set the indicator Deactivate Source Determination the purchase requisition transferred from SAP APO is not assigned a source of supply and you can, for example, enter a source of supply manually in SAP R/3.
1.12.4 Selection of source of supply (enhanced)

Use
In the APO CIF for R/3 Plug-In 2001.2, the screen section Selection of Source of Supply has the additional indicators Material Dependent Source of Supply Selection and Include Dependent Vendors and Delivering Plants. These offer you enhanced means of selection. If you set the indicator Material Dependent Source of Supply Selection, all sources of supply are selected for the data entered in the screen section General Selection Options for Materials. If you set the indicator Include Dependent Vendors and Delivering Plants, all vendors and delivering plants relevant to the source of supply will also be selected. For example, if you enter the MRP controller in the screen section General Selection Options for Materials and set the indicator Material Dependent Source of Supply Selection, the system will select all sources of supply for this MRP controller.
1.12.5 Integration of Configurations for External Procurement Docu.

Use Previously, configurations for external procurement documents (purchase orders, purchase requisitions, stock transfer orders and stock transfer requisisitons) that you entered in SAP R/3 were not transferred to SAP APO.
As of SAP R/3 Plug-In 2001.2 and SAP APO 3.1, you can transfer these configurations to SAP APO in an initial data supply. Online transfer is also possible, but only for configurations that have been created directly in an external procurement document. It is not possible for configurations that come from a predecessor document in SAP R/3 and are only contained in the document for reference purposes. Online transfer requires SAP R/3 4.6B or higher.
________________________________________________________________
SAP AG 109
APO 3.1 ________________________________________________________________
1.12.6 Selection screen for integration model (changed)

Use For R/3 Plug-In 2001.2 the selection screens for the creation of an integration model (transaction CFM1) and for the search for filter objects (transaction CFM5) have been revised. They now show a new, compact interface as well as some new objects. In addition, F1 help is available for all fields. The new selection screen is divided into the following screen sections: o o o Material dependent objects Material independent objects General selection options for materials (previously: Relevant materials)
In the screen sections Material Dependent Objects and Material Independent Objects you can determine which objects are to be included in integration (that is, transferred to SAP APO) by marking the corrsponding field. The transfer can be restricted by making entries in various value ranges in the screen section General Selection Options for Materials. The arrow keys to the right of the value ranges take you to dialog windows where you can make multiple selections. Here, you can determine more complex selection criteria by making additional restrictions for these value ranges, or by excluding certain value ranges from the transfer. In the screen sections Material Dependent Objects and Material Independent Objects you can also find arrow keys to the right of many fields. If you mark a field and select the corresponding arrow key an additional screen section appears on the right hand side of the screen area. Here, you can restrict the selection made under General Selection Options for Materials specifically for this field. As in the screen section General Selection Options for Materials you can use the arrow key to open a dialog window where multiple selection is possible.
1.12.7 Configuration of the CIF application log (new)

Use Transfer logs are evaluated in the CIF application log in R/3 via transaction CFG1. As of R/3 Plug-In 2001.2 you can configure the CIF application log according to your specific needs. As standard, the most commonly used interface parameters are set as default in the CIF application log. To include additional interface parameters in the application log, or to delete them, use the transaction CFC6 to call up the program for configuring the CIF application log. Via input help you can select the function modules that you need. Choose Execute. o Under the node Interface [Name of Function Module] you will find all the interface parameters that can be selected. Under the node Selected Fields for Log you will find both the default interface parameters and those that you have selected yourself. The sequence of the interface parameters corresponds to the sequence in which they were included in the application log. Note, that this program is not yet connected to the transport system. The settings must therefore be made manually in each R/3 system.
Note
1.12.8 SCM Queue Manager (new)

Use As of R/3 Plug-In 2001.2 and SAP APO Support Package 14, you can use the SCM Queue Manager in SAP APO as a central monitoring instrument. The SCM Queue Manager is called up in SAP APO via transaction /SAPAPO/CQ. In the SAP Easy Access Menu it can be accessed via Tools - APO Administration - Integration - Monitor - SCM Queue Manager.
________________________________________________________________
110 SAP AG
APO 3.1 ________________________________________________________________
The SCM Queue Manager allows the central monitoring of queues both in the sending and receiving systems. You can navigate to the qRFC monitor and the application log both in SAP APO and SAP R/3. In comparison to the qRFC Monitor, the SCM Queue Manager has a significantly clearer and more user friendly display of results.
1.12.9 Assigning a queue type

Use
As of R/3 Plug-In 2001.2 and SAP APO Support Package 14 you can assign a queue type (inbound or outbound queues) to a logical system in the SAP APO Implementation Guide (IMG). This is done via SAP Advanced Planner and Optimizer - Basis Settings - Integration - Business System Group - Assign Logical System and Queue Type.
If there is a large amount of data to be transferred from SAP APO to SAP R/3 and an even utilization of the R/3 system is to be ensured, choose Inbound Queues.
If you choose Inbound Queues in SAP APO you must make the corresponding settings in the qRFC monitor of the QIN Scheduler (Queue-In Scheduler) in SAP R/3. Queues that the SAP R/3 system should automatically process must be registered in the QIN scheduler. You can find additional information in the documentation for the SAP APO IMG activity.
1.12.10 APO-INT-EXT Interface for External Systems 1.12.10.1 New and Changed Business Objects and BAPIs (Enhanced)
Use This information refers to business objects, as well as interface objects and the BAPIs/ALE interfaces (message types) they contain for the following components: Production Planning and Detailed Scheduling APO-PPS
APO-MD APO-VS
Master Data Vehicle Scheduling
Note, that some of the BAPIs referred to have not yet been released. You may already use these BAPIs. However, since they have not been released later changes may be made that will render them incompatible. If you use the associated function modules of BAPIs instead of the BAPIs themselves the changes are also valid for these function modules. The new/changed business objects and BAPIs are given below. You can find detailed information in the documentation for the individual BAPIs. BUS10009 Quota Arrangement APS
The business object is new for SAP APO 3.1. It contains BAPIs for quota arrangements
New BAPI methods:
________________________________________________________________
SAP AG 111
APO 3.1 ________________________________________________________________
SaveMultiple GetList
Create or change quota arrangements Read quota arrangements for selection criteria
BUS10300 Vehicle Scheduling Planning Services The business object is new for SAP APO 3.1. It contains BAPIs for Vehicle Scheduling. New BAPI methods: GetOptimizerProfile GetOrderSets UnplanOrders UpdateShipments BUS11201 Transportation lane The business object is new for SAP APO 3.1. It contains BAPIs for transportation lanes. New BAPI methods: SaveMultiple GetList DeleteMultiple BUS10503 (Manufacturing Order APS) New BAPI method: ModifyNodes Changed BAPI methods: o SaveMultiple The field ORDER_START_DATE in parameter ORDER_HEAD for forwards scheduling is supported as of now. The parameter EVENT_CONTROL was included. This is used to control whether events for this order should be transferred to CIF. CreateFromTemplate The field SCHED_LINE was removed from parameters COMPONENTS and CHARACTERISTICS_VAL_IO. The field IS_INPUT_NODE was removed from parameter CHARACTERISTICS_VAL_ACT. The parameter EVENT_CONTROL was included. This is used to control whether events for this order should be transferred to CIF. ChangeActivities The parameter EVENT_CONTROL was included. This is used to control whether events for this order should be transferred to CIF. DeleteMultiple The parameter EVENT_CONTROL was included. This is used to control whether events for this order should be transferred to CIF. Change components of a manufacturing order Create or change transportation lanes Read transportation lanes for selection criteria Delete transportation lanes Read TP/VS optimizer profile Read from transport units and shipments Deallocate transport units from shipments Combine shipments
BUS10004 (Resource APS) New BAPI methods: GetDefinitions Read definitions
________________________________________________________________
112 SAP AG
APO 3.1 ________________________________________________________________
RequestDefinitions ReceiveDefinitions Changed BAPI methods: o
Asynchronous call from GetDefinitions Asynchronous call from GetDefinitions
SaveMultiple Optional table parameter ResourceRatemodel added (allocation of resource to a rate model). Additional fields included in ResourceHead table. ChangeMultiple Optional table parameter ResourceRatemodel added (allocation of resource to a rate model). Additional fields included in ResourceHead table. GetList Additional fields included in ResourceHead table. Optional table parameters added for reading definition assignment (ResourceQuanmodel, ResourceRatemodel, ResourceShiftseq, ResourceDowntime). ReceiveList Additional fields included in ResourceHead table. Optional table parameters added for reading definition assignment (ResourceQuanmodel, ResourceRatemodel, ResourceShiftseq, ResourceDowntime). RemoveSubobjects Optional table parameter added for removing rate model assignment (ResourceRatemodel). SaveDefinitions Optional table parameter added for creation of rate models (Ratemodel, RatemodelText). DeleteDefinitions Key table added for deletion of rate model. BlockSetStatus Method is obsolete since the BlockSaveMultliple method was enhanced. This should no longer be used. BlockSaveMultiple New optional table parameter included for setting block attributes (BlockAttributes). This method replaces the BlockSetStatus method. GetBlocks Additional fields included in table BlockDefinition.
o o o o o
BUS10002 (Location APS) o SaveMutliple Optional table parameters added for the communication types (LocationUri, LocationFax, LocationTel, LocationSmtp). LocationHead table enhanced through additional fields. GetList Optional table parameters added for the communication types (LocationUri, LocationFax, LocationTel, LocationSmtp). LocationHead table enhanced through additional fields. ReceiveList Optional table parameters included for communication types (LocationUri, LocationFax, LocationTel,
________________________________________________________________
SAP AG 113
APO 3.1 ________________________________________________________________
LocationSmtp). LocationHead table enhanced through additional fields. BUS10001 (Product APS) o SaveMultiple Additional fields included in ProductHead table. Additional fields included in ProductLocation table. GetList Additional fields included in ProductHead table. Additional fields included in ProductLocation table. ReceiveList Additional fields included in ProductHead table. Additional fields included in ProductLocation table.
BUS10003 (Production Process Model APS) o SaveMultiple Optional table parameter Prodflow included. Optional import parameter included for executing enhanced checks. GetList Optional table parameter Prodflow included. ReceiveList Optional table parameter Prodflow included.
o o
BUS10030 Planning Book APS New BAPI method: SaveCharacteristicsCombination Changed BAPI methods o GetDetail Additional import parameter included for selection of data view. Method was released. ChangeKeyfigureValue Additional import parameter included for selection of data view. Method was released. RequestDetail Additional import parameter included for selection of data views (SourceDataView, TargetDataView). Method was released. ReceiveDetail Method was released. Create DP characteristics combinations
Change for APX (APO Optimization Extension Workbench) o o o Revision of APX Customizing. Instead of OCX, other external programs may now be started via RFC. Additional data may also be transferred and the optimizer extension can be displayed only for certain
________________________________________________________________
114 SAP AG
APO 3.1 ________________________________________________________________
users. o o Report /SAPAPO/APX_OPTSTART can be used to start an optimizer extension. The previous APX customer exits have been replaced by BADIs.
Detailed information can be found in the documentation for Customizing or for the report.
________________________________________________________________
SAP AG 115

Apo 31 Release Notes

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Apo 31 Release Notes

Загружено:

Авторское право:

Доступные форматы

SAP Advanced Planner and Optimizer (SAP APO) Release 3.

are registered trademarks of Informix Software

SAP AG Table of Contents APO 3.1 ________________________________________________________________

APO 3.1 Table of Contents SAP AG ________________________________________________________________

SAP AG Table of Contents APO 3.1 ________________________________________________________________

APO 3.1 Table of Contents SAP AG ________________________________________________________________

SAP AG Table of Contents APO 3.1 ________________________________________________________________

APO 3.1 Table of Contents SAP AG ________________________________________________________________

APO 3.1 ________________________________________________________________

CTM Demand Prioritization

APO 3.1 ________________________________________________________________

1.2 Trader's and Scheduler's Workbench (TSW)

APO 3.1 ________________________________________________________________

1.3 APO-CA APO Cross-Application Components

1.3.1.1 Block Planning (enhanced)

Block planning with buckets

APO 3.1 ________________________________________________________________

APO 3.1 ________________________________________________________________

1.3.1.2 Batch selection in the sales order for CDP (new)

1.3.1.3 Maintaining classes and characteristics in CDP (changed)

APO 3.1 ________________________________________________________________

and characteristics maintenance of CDP.

Transfer of changes from SAP R/3 to SAP APO

APO 3.1 ________________________________________________________________

Execute report /SAPAPO/MC01_CACL_CDP_ADJUST.

1.3.1.4 Evaluations in PP/DS (enhanced)

1.4 APO-MD Master Data

APO 3.1 ________________________________________________________________

1.4.2 APO-MD-MO Model 1.4.2.1 Model Consistency Check (New)

APO 3.1 ________________________________________________________________

Delete Application Log.

1.4.3.2 Calculation of Transportation Zone Coordinates (New)

1.4.3.3 Mass Geocoding of Locations (New)

1.4.4 APO-MD-PR Product 1.4.4.1 Display of alerts (enhanced)

APO 3.1 ________________________________________________________________

1.4.4.2 PP Heuristics for Sales Order Oriented Planning (new)

APO 3.1 ________________________________________________________________

1.4.5 APO-MD-RE Resource 1.4.5.1 Block Planning (enhanced)

Block planning with buckets

APO 3.1 ________________________________________________________________

1.4.5.2 Detailed Scheduling Strategies (enhanced)

APO 3.1 ________________________________________________________________

APO 3.1 ________________________________________________________________

APO 3.1 ________________________________________________________________

1.4.6.2 SNP PPM Generation With Lot Size Margins (new)

APO 3.1 ________________________________________________________________

APO 3.1 ________________________________________________________________

1.4.7.2 Introduction of Action Points (Enhanced)

APO 3.1 ________________________________________________________________

1.4.7.3 Creating Multiple Work Centers (New)

Overview of New Functions in Line Design

APO 3.1 ________________________________________________________________

1.4.7.4 Overview of New Functions in Line Design (Enhanced)

APO 3.1 ________________________________________________________________

1.4.7.5 Creating Line Structures with Alternatives (new)

APO 3.1 ________________________________________________________________

Line 'final assembly 3' All the subordinate line segments.

1.4.7.6 iPPE Production Resource (New)

1.4.7.7 New Functions in the iPPE Process Structure (Enhanced)

APO 3.1 ________________________________________________________________

APO 3.1 ________________________________________________________________

APO 3.1 ________________________________________________________________

1.4.7.8 iPPE Actions for Upgrading to SAP APO 3.1 (New)

APO 3.1 ________________________________________________________________