release notes for sap supply chain management release sap ... · pdf filesap supply chain...

Release Notes for SAP Supply Chain Management

Release SAP SCM 4.1

______________________________________________________________

CopyrightCopyright(c) 2005 SAP AG. All rights reserved.

Neither this document nor any part of it may be copied or reproduced in any form or by anymeans or translated into another language, without the prior consent of SAP AG. Theinformation contained in this document is subject to change without notice.

SAP is a registered trademark of SAP AG.

All other products which are mentioned in this documentation are registered or not registeredtrademarks of their respective companies.

1 SCM Supply Chain Management 11.1 SCM-APO Advanced Planning and Optimization 11.1.1 IDoc Inbound Processing and Default Profiles Definable in the Application Menu (Changed) 11.1.2 Changes to the IMG Structure for SAP Advanced Planning and Optimization 11.1.3 SCM-APO-CA APO Cross-Application Components 61.1.3.1 Data Reorganization (New) 61.1.3.2 APO Consistency Checks 71.1.3.3 SCM-APO-CA-CDP Characteristics-Dependent Planning 81.1.3.3.1 Consistency Check for Product Variants (New) 81.1.3.3.2 Process Change: Generate Production Data Structures (PDS) from iPPE Data (New/Changed) 91.1.3.3.3 Bucket-Oriented Block Planning (Changed) 101.1.3.3.4 Block Planning Using Variant Configuration (New) 111.1.3.3.5 'Extended Block Maintenance' Heuristic (New) 121.1.3.3.6 Consistency Checks in liveCache - APO DB for CDP and Configuration (New) 131.1.3.3.7 Map Reference Characteristics in SAP APO (New) 131.1.3.3.8 Transfer of Characteristic Requirements to Stock Transfer Doc. (New) 131.1.3.4 SCM-APO-CA-COP Collaborative Planning 141.1.3.4.1 Collaborative Planning using ITS Plug-In and Internet Communication Framework (New) 141.1.3.5 SCM-APO-CA-VC Variant Configuration 151.1.3.5.1 Consistency Check for Product Variants (New) 151.1.3.5.2 Block Planning Using Variant Configuration (New) 151.1.3.5.3 Consistency Checks in liveCache - APO DB for CDP and Configuration (New) 161.1.3.5.4 Map Reference Characteristics in SAP APO (New) 161.1.4 SCM-APO-MD Master Data 171.1.4.1 Logging of Master Data Changes with Change Documents (New) 171.1.4.2 Extended Hierarchy (New) 181.1.4.3 Fast Entry of Hierarchy Nodes (Extended) 181.1.4.4 Display Profiles for Master Data Maintenance (New) 181.1.4.5 Where-Used List for Master Data (New) 191.1.4.6 Mass Maintenance of Sales Scheduling Agreements (New) 201.1.4.7 SCM-APO-MD-LO Location 201.1.4.7.1 Subcontracting for Multiple Plants with Loc. Subcontractor (New) 201.1.4.8 SCM-APO-MD-PR Product 211.1.4.8.1 Assignment of Category Groups for ATD Receipt and ATD Issue

______________________________________________________________SAP AG iii

Release-Notes Table of Contents SAP AG_________________________ _____________________________________

(Enhanced) 211.1.4.9 SCM-APO-MD-INC Product Interchangeability - Master Data 221.1.4.9.1 New Functions in Master Data for Product Interchangeability 221.1.4.10 SCM-APO-MD-RE Resource 241.1.4.10.1 Changes to the Maintenance of Resources 241.1.4.11 SCM-APO-MD-PPE Product and Process Engineering 251.1.4.11.1 Consistency Check for iPPE Data 251.1.4.11.2 Extended Process Integration of iPPE Data 261.1.4.11.3 iPPE Workbench Express and iPPE Workbench Professional (New / Changed) 281.1.4.11.4 Process Change: Generate Production Data Structures (PDS) from iPPE Data (New/Changed) 291.1.4.11.5 Production Data Structure (PDS): Supported Uses in Planning (New) 301.1.4.11.6 Rename Runtime Object (RTO) to Production Data Structure (PDS) 311.1.4.12 SCM-APO-MD-CL Classes and Characteristics 321.1.4.12.1 Block Planning Using Variant Configuration (New) 321.1.4.13 SCM-APO-MD-PDS Production Data Structure 331.1.4.13.1 PP/DS Production Data Structure Comparison (Previously: PP/DS Runtime 331.1.4.13.2 Integration of Order BOMs/WBS BOMs (New) 341.1.4.13.3 Production Data Structure (PDS): Supported Uses in Planning (New) 341.1.4.13.4 Rename Runtime Object (RTO) to Production Data Structure (PDS) 351.1.4.13.5 SCM-APO-MD-PDS-SIM Display and Simulation 361.1.4.13.5.1 Displaying production data structures (PDS) 361.1.5 SCM-APO-VS Vehicle Scheduling 361.1.5.1 BAdIs for Transportation Planning/Vehicle Scheduling (New) 361.1.5.2 Various Functional Enhancements in TP/VS (Enhanced) 371.1.5.3 SCM-APO-VS-OPT Vehicle Scheduling Optimization 381.1.5.3.1 Definition of Compatibilities (Enhanced) 381.1.5.3.2 Optimization Profile (Enhanced) 391.1.5.3.3 Definition of Pickup/Delivery Windows (New) 401.1.5.4 SCM-APO-VS-INS Interactive VS 411.1.5.4.1 Displaying Shipments on Road Maps (New) 411.1.5.4.2 Interactive Combining of Freight Units (New) 421.1.6 SCM-APO-SNP Supply Network Planning (SNP) 421.1.6.1 Automatic Parallel Processing and Scheduling of Jobs 42

______________________________________________________________SAP AG iv

Release-Notes Table of Contents SAP AG______________________________________________________________

1.1.6.2 Process Change: Generate Production Data Structures (PDS) from iPPE Data (New/Changed) 441.1.6.3 Production Data Structure (PDS): Supported Uses in Planning (New) 451.1.6.4 SNP Heuristic (Enhanced) 461.1.6.5 Application Logs for SNP Planning Runs (Enhanced) 461.1.6.6 Periodic Lot Size Grouping (Changed) 471.1.6.7 Generation of Alerts with Exit Macros during a Planning Run (New) 481.1.6.8 Production Data Structure in SNP (New) 491.1.6.9 SCM-APO-SNP-BF Basic Functions 501.1.6.9.1 Global SNP Settings - SNP Planning Profile (Changed) 501.1.6.9.2 Mass Maintenance of Time Series Key Figures (New) 501.1.6.9.3 Diverse SNP-Relevant Master Data Changes 511.1.6.9.4 Transfer of SNP Orders to OLTP Systems (Enhanced) 521.1.6.9.5 SNP Supply, Demand, and Deployment Profile (Changed) 521.1.6.9.6 Sourcing of Forecast (New) 531.1.6.10 SCM-APO-SNP-OPT SNP Plan Optimization 541.1.6.10.1 Decomposition Procedures for the Deployment Optimizer (New) 541.1.6.10.2 Diverse Functions in the SNP and Deployment Optimizer Area (Enhanced) 551.1.6.10.3 SNP Priority Profile (New) 561.1.6.10.4 SNP Optimizer Procedures for Fail-Safe Solution Determination (New) 571.1.6.10.5 Subcontracting (Enhanced) 571.1.6.11 SCM-APO-SNP-INS Interactive SNP 581.1.6.11.1 Changes and Enhancements to the Graphic in Interactive Planning 581.1.6.11.2 Usability Changes in Interactive Planning 581.1.6.11.3 Interactive Planning (Enhanced) 601.1.6.12 SCM-APO-SNP-DPL Deployment 621.1.6.12.1 Assignment of Category Groups for ATD Receipt and ATD Issue (Enhanced) 621.1.6.12.2 Decomposition Procedures for the Deployment Optimizer (New) 621.1.6.12.3 Determination of the Means of Transport in the Deployment Heuristic 631.1.6.12.4 Diverse Functions in the SNP and Deployment Optimizer Area (Enhanced) 641.1.6.12.5 Rounding in Deployment (Changed) 651.1.6.13 SCM-APO-SNP-TLB Transport Load Builder 661.1.6.13.1 Transport Load Builder (Enhanced) 661.1.6.14 SCM-APO-SNP-INC Product Interchangeability in SNP 68

______________________________________________________________SAP AG v


1.1.6.14.1 Product Interchangeability in Supply Network Planning (Changed) 681.1.7 SCM-APO-SDM Multilevel Supply & Demand Matching 691.1.7.1 SCM-APO-SDM-CTM Capable-to-Match 691.1.7.1.1 Enhancements in Capable-to-Match (New) 691.1.7.1.2 Transport CTM Profile (New) 701.1.7.1.3 Automatic Parallel Processing and Scheduling of Jobs 701.1.7.1.4 Production Data Structure (PDS): Supported Uses in Planning (New) 721.1.8 SCM-APO-FCS Demand Planning 721.1.8.1 New and Changed Authorization Objects 731.1.8.2 Function Improvements in Demand Planning (Enhanced) 741.1.8.3 Activities Deleted from Demand Planning IMG (Deleted) 751.1.8.4 Automatic Parallel Processing and Scheduling of Jobs 761.1.8.5 Release of Forecast Data from the InfoProvider 771.1.8.6 Release of Forecast Data from the InfoProvider 771.1.8.7 SCM-APO-FCS-BF Basic Functions 781.1.8.7.1 Changes and Enhancements for Planning Object Structures 781.1.8.8 SCM-APO-FCS-MAC MacroBuilder 801.1.8.8.1 Changes and Enhancements in Macro Processing 801.1.8.9 SCM-APO-FCS-STF Statistical Forecast 801.1.8.9.1 Changes and Enhancements to Forecasting 801.1.8.10 SCM-APO-FCS-INF Interactive Forecasting 821.1.8.10.1 Changes and Enhancements to the Graphic in Interactive Planning 821.1.8.10.2 Usability Changes in Interactive Planning 821.1.8.11 SCM-APO-FCS-PRP Promotion Planning 841.1.8.11.1 Changes and Enhancements to Promotion Planning 841.1.8.12 SCM-APO-FCS-CHS Characteristics-Based Forecasting 851.1.8.12.1 Changes and Enhancements to Characteristics-Based Forecasting 851.1.8.13 SCM-APO-FCS-CSP Forecast Consumption 861.1.8.13.1 Changes and Enhancements toForecast Consumption and Associated Tools 861.1.9 SCM-APO-PPS Production Planning and Detailed Scheduling 871.1.9.1 Consistency Check for Product Variants (New) 871.1.9.2 Configuration Check in the CIF Comparison/Reconciliation (New) 881.1.9.3 Improved Master Data Integration for Subcontracting (Enhanced) 89

______________________________________________________________SAP AG vi


1.1.9.4 Changes to the Maintenance of Resources 901.1.9.5 Stable Forward Scheduling (New) 921.1.9.6 Process Change: Generate Production Data Structures (PDS) from iPPE Data (New/Changed) 921.1.9.7 Bucket-Oriented Block Planning (Changed) 931.1.9.8 Subassembly Planning in the CTP Process 951.1.9.9 Bucket-Oriented Capacity Check in the CTP Process (New) 961.1.9.10 Fixed Pegging (Enhanced) 981.1.9.11 Sequence-Dependent Setup Activities (Changed) 1011.1.9.12 Calculation of the Days' Supply (New) 1031.1.9.13 Inventory Alerts in PP/DS (New) 1041.1.9.14 Target Stock Level in Production Planning and Detailed Scheduling 1041.1.9.15 SCM-APO-PPS-PPT Product Planning Table 1051.1.9.15.1 Alert when Mode Linkage of Activities is Violated in Detailed Scheduli 1051.1.9.15.2 Alert when Non-Interruptible Activities are Interrupted During Detaile 1061.1.9.15.3 Alert when Synchronization is Violated in Detailed Scheduling (New) 1061.1.9.16 SCM-APO-PPS-DST Detailed Scheduling Planning Board 1071.1.9.16.1 Alert when Mode Linkage of Activitiesis Violated in Detailed Scheduli 1071.1.9.16.2 Alert when Non-Interruptible Activities are Interrupted During Detaile 1071.1.9.16.3 Alert when Synchronization is Violated in During Scheduling (New) 1081.1.9.16.4 Sequence-Dependent Setup Activities (Changed) 1081.1.9.16.5 Simulation Versions (Enhanced) 1101.1.9.16.6 Improvements to the Usability of the Detailed Scheduling Planning Board 1111.1.9.17 SCM-APO-PPS-PVW Product View 1121.1.9.17.1 Alert when Mode Linkage of Activities is Violated in Detailed Scheduli 1121.1.9.17.2 Alert when Non-Interruptible Activities are Interrupted During Detaile 1131.1.9.17.3 Alert when Synchronization is Violated in Detailed Scheduling (New) 1131.1.9.17.4 Manual Maintenance of Fixed Pegging Relationships (Enhanced) 1141.1.9.17.5 Product View (Enhanced) 1161.1.9.18 SCM-APO-PPS-SCF Scheduling Functions 1161.1.9.18.1 Stable Forward Scheduling (New) 116

______________________________________________________________SAP AG vii


1.1.9.18.2 Sequence-Dependent Setup Activities (Changed) 1171.1.9.18.3 Error-Tolerant Scheduling (New) 1191.1.9.19 SCM-APO-PPS-FP Fixed Pegging 1201.1.9.19.1 Fixed Pegging (Enhanced) 1201.1.9.19.2 Manual Maintenance of Fixed Pegging Relationships (Enhanced) 1221.1.9.20 SCM-APO-PPS-CDS Sales Scheduling A Processing 1241.1.9.20.1 Overview of New Features in Sales Scheduling Processing 1241.1.9.20.2 Under- and Overconfirmation Alerts (New) 1251.1.9.20.3 IDoc Inbound Processing and Default Profiles Definable in the Application Menu (Changed) 1261.1.9.20.4 Mass Maintenance of Sales Scheduling Agreements (New) 1261.1.9.20.5 Pegging-Relevant Quantity for Sales Scheduling Agreements (Changed) 1271.1.9.20.6 Business Add-In for Determining a Suitable Means of Transport (New) 1291.1.9.20.7 Additional Data in Master Data Maintenance for the Sales Scheduling Agreement (New) 1291.1.9.21 SCM-APO-PPS-MMP Model Mix Planning 1301.1.9.21.1 Model Mix Planning (Changed) 1301.1.9.22 SCM-APO-PPS-RPM Planning Matrix 1311.1.9.22.1 Production Planning Using the Planning Matrix (Changed) 1311.1.9.23 SCM-APO-PPS-PPC Product and Process Confirmation 1321.1.9.23.1 Production Backlfush (Enhanced) 1321.1.9.24 SCM-APO-PPS-HEU Heuristics 1331.1.9.24.1 Pegging-Relevant Quantity for Sales Scheduling Agreements (Changed) 1331.1.9.24.2 'Extended Block Maintenance' Heuristic (New) 1351.1.9.25 SCM-APO-PPS-RSP Reservation Planning 1351.1.9.25.1 Reservation Planning (New) 1351.1.10 SCM-APO-MSP Maintenance Planning 1371.1.10.1 Easy Simulation in Maintenance and Service Processing (Enhanced) 1371.1.10.2 Number Range Maintenance of Maintenance Items (Deleted) 1381.1.10.3 Maintenance and Service Planning Board Enhancements (Enhanced) 1391.1.10.4 Master Data in Maintenance and Service Planning (Enhanced) 1401.1.11 SCM-APO-ATP Global Available-to-Promise 1411.1.11.1 BAPI to Determine the Availability Situation (New) 1411.1.11.2 SCM-APO-ATP-BF Basic Functions 142

______________________________________________________________SAP AG viii


1.1.11.2.1 Distribution Key for Lasting Orders in ATP Time Series (New) 1421.1.11.2.2 Location-Dependent Buckets in the Availability Check (Enhanced) 1431.1.11.3 SCM-APO-ATP-PRD ATP in Conjunction With Production 1431.1.11.3.1 Subassembly Planning in the CTP Process 1431.1.11.3.2 Bucket-Oriented Capacity Check in the CTP Process (New) 1441.1.11.4 SCM-APO-ATP-SCH Time and Scheduling Functions 1471.1.11.4.1 Scheduling Using Configurable Process Scheduling (New) 1471.1.11.5 SCM-APO-ATP-EST Explanation & Simulation Tool 1481.1.11.5.1 Explanation Facility of Global Available-to-Promise (Enhanced) 1481.1.11.6 SCM-APO-ATP-BOP Backorder Processing 1481.1.11.6.1 Results Display of Backorder Processing (Enhanced) 1491.1.12 SCM-APO-AMO Alert Monitor 1491.1.12.1 Alert when Mode Linkage of Activitiesis Violated in Detailed Scheduling 1491.1.12.2 Alert when Non-Interruptible Activities are Interrupted During Detaile 1501.1.12.3 Alert when Synchronization is Violated in Detailed Scheduling (New) 1501.1.12.4 Automatic Parallel Processing and Scheduling of Jobs 1511.1.12.5 Under- and Overconfirmation Alerts (New) 1521.1.12.6 Alert Determination in the Background (New) 1531.1.12.7 Changes in the Alert Monitor (Changed) 1531.1.12.8 Inventory Alerts in PP/DS (New) 1541.1.13 SCM-APO-OPT Optimization 1551.1.13.1 SCM-APO-OPT-SNP Supply Network Planning 1551.1.13.1.1 Decomposition Procedures for the Deployment Optimizer (New) 1551.1.13.1.2 Diverse Functions in the SNP and Deployment Optimizer Area (Enhanced) 1561.1.13.1.3 SNP Priority Profile (New) 1571.1.13.1.4 SNP Optimizer Procedures for Fail-Safe Solution Determination (New) 1581.1.13.1.5 Subcontracting (Enhanced) 1581.1.14 SCM-APO-CPR Collaborative Procurement 1591.1.14.1 Business Add-In for Determining a Suitable Means of Transport (New) 1591.1.14.2 SCM-APO-CPR-SCH Procurement Scheduling Agreement 1591.1.14.2.1 Enter Confirmations Manually (New) 1591.1.14.3 SCM-APO-CPR-TRA Stock Transfer 1601.1.14.3.1 Transfer of Characteristic Requirements to Stock Transfer Doc. (New) 160

______________________________________________________________SAP AG ix


1.1.15 SCM-APO-INT Interfaces 1611.1.15.1 Consistency Check for Product Variants (New) 1611.1.15.2 Implementation Guide for SAP APO Core Interface (New) 1611.1.15.3 CIF Cockpit (New) 1621.1.15.4 SAP APO Monitoring in Computing Center Management System (CCMS) (New) 1641.1.15.5 Configuration Check in the CIF Comparison/Reconciliation (New) 1651.1.15.6 New Options in the CIF Comparison/Reconciliation (Enhanced) 1661.1.15.7 New Interfaces in the CIF Comparison/Reconciliation (Changed) 1661.1.15.8 Integration of SAP R/3 Source List with SAP APO (New) 1671.1.15.9 Subcontracting for Multiple Plants with Loc. Type Subcontractor (New) 1681.1.15.10 SCM-APO-INT-EXT Interface to External Systems 1681.1.15.10.1 Business and Interface Objects and BAPI Methods (Changed) 1681.1.15.10.2 Deletion of Transaction Data Using BAPIs (New) 1711.1.15.10.3 Sending Transaction Data Using BAPIs (New) 1711.1.15.11 SCM-APO-INT-MD Master Data 1721.1.15.11.1 SCM-APO-INT-MD-PDS Production Data Structure 1721.1.15.11.1.1 Enhanced Integration of Reference Operation Sets (Enhanced) 1721.1.15.11.1.2 PP/DS Production Data Structure Comparison Previously: PP/DS Runtime Object (New) 1731.1.15.12 SCM-APO-INT-PPS PP/DS - Production Process Order 1741.1.15.12.1 Enhanced Integration of Reference Operation Sets (Enhanced) 1741.1.15.12.2 CIF Compare/Reconcile Function for Operations and Phases (New) 1751.1.15.12.3 Setup Information in Order Integration (Changed) 1761.1.15.13 SCM-APO-INT-CCR CIF Compare/Reconcile 1781.1.15.13.1 CIF Compare/Reconcile Function for Operations and Phases (New) 1781.1.15.14 SCM-APO-INT-CPP Postprocessing Records of CIF Error Handling 1791.1.15.14.1 Creation of Notes in CIF Error Handling (Enhanced) 1791.1.15.15 SCM-APO-INT-POR Project Order 1791.1.15.15.1 Project Orders (New) 1791.1.15.16 SCM-APO-INT-MOR Maintenance Order 1811.1.15.16.1 Maintenance Orders (New) 1811.2 SCM-BAS SCM Basis 1831.2.1 SCM-BAS-AMO Alert Monitor 1831.2.1.1 Alert Determination in the Background (New) 183

______________________________________________________________SAP AG x


1.2.1.2 Changes in the Alert Monitor (Changed) 1831.2.1.3 Target Stock Level in Production Planning and Detailed Scheduling 1841.2.2 SCM-BAS-PSM Planning Service Manager 1851.2.2.1 Planning Service Manager (New) 1851.2.3 SCM-BAS-BIF Business Interface Layer 1861.2.3.1 Validation (Enhanced) 1861.3 SCM-FRE Forecasting and Replenishment 1861.3.1 SAP Forecasting and Replenishment (New) 1861.3.2 F&R Optimization Process 1871.3.3 SCM-FRE-MD Master Data 1881.3.3.1 F&R Master Data (New) 1881.3.4 SCM-FRE-IF Interfaces 1891.3.4.1 SCM-FRE-IF-FRP Interfaces from and to FRP 1891.3.4.1.1 F&R Interfaces (New) 1891.3.5 SCM-FRE-TSM Time Series Management 1891.3.5.1 F&R Transaction Data (New) 1901.3.6 SCM-FRE-FRP FRP Functions 1901.3.6.1 F&R Processor 1901.3.7 SCM-FRE-OPM Order Proposal Management 1911.3.7.1 Order Proposal Management (New) 1911.3.8 SCM-FRE-DIF Demand Influencing Factor 1921.3.8.1 Demand Influencing Factors (New) 1921.3.9 SCM-FRE-ANA Analyses 1931.3.9.1 Forecasting & Replenishment Analytics 3.52 (New) 1931.3.10 SCM-FRE-RWB Planning Workbench 1941.3.10.1 Replenishment Workbench (New) 1941.3.10.2 Replenishment Workbench for Stores (New) 1951.3.11 SCM-FRE-EXC Exception Handling 1951.3.11.1 Exception Workbench 1951.4 SCM-ICH Inventory Collaboration Hub 1961.4.1 Audit Trail (New) 1961.4.2 Demand Monitor (New) 1961.4.3 Personalization (New) 1971.4.4 Purchase Orders in Supplier Collaboration (New) 1971.4.5 SCM-ICH-REL Scheduling Agreement Release 1981.4.5.1 Release Processing (Enhanced) 1981.4.6 SCM-ICH-ASN Advanced Shipping Notification 1981.4.6.1 ASN Processing (Enhanced) 1981.4.6.2 Notes (New) 1991.4.6.3 Validation (Enhanced) 2001.4.7 SCM-ICH-IMO Inventory Monitor 200

______________________________________________________________SAP AG xi


1.4.7.1 Inventory Monitor (Enhanced) 2001.4.7.2 Notes (New) 2011.4.8 SCM-ICH-REP ICH Reporting 2021.4.8.1 Alert Monitor (Enhanced) 2021.4.9 SCM-ICH-DIO Inbound/Outbound Data Processing 2031.4.9.1 Inbound and Outbound Messages (Enhanced) 2031.4.10 SCM-ICH-AMO Alert Monitor 2031.4.10.1 Changes in the Alert Monitor (Changed) 2031.4.10.2 Alert Monitor (Enhanced) 2041.4.10.3 Notes (New) 205

______________________________________________________________SAP AG xii


1 SCM Supply Chain Management

1.1 SCM-APO Advanced Planning and Optimization

1.1.1 IDoc Inbound Processing and Default Profiles Definable in the ApplicationMenu (Changed)

Use

Until SAP APO 4.0 the activities IDoc Inbound Processing and Default Control Profile were accessedfrom Customizing for Advanced Planning and Optimization under Supply Chain Planning ->Delivery Schedule Processing for Sales Scheduling Agreements.

As of SAP SCM 4.1, these functions are no longer in Customizing, but can be accessed using newtransaction codes from the Easy Access Menu under Supply Chain Collaboration -> SalesScheduling Agreement Processing -> Current Settings:

-> IDoc Inbound Processing-> Define Inbound Release Processing /SAPAPO/CMDS_STPSR

(Previously: Set IDoc Inbound Processing /SAPAPO/CUST14)

-> Define Sold-To Party Determination /SAPAPO/CMDS_STPD

(Previously: Determination of Sold-To Party over EDI/SAPAPO/CUST15)

-> Default Profiles for Initial Data Transfer-> Maintain Default Control Profile /SAPAPO/CMDS_DEFCNTR

(Previously: Define Default Control Profiles/SAPAPO/CUST10)

-> Maintain Default Confirmation Profile /SAPAPO/CMDS_DEFCNF

(Previously: Define Default Confirmation Profiles/SAPAPO/CUST9)

1.1.2 Changes to the IMG Structure for SAP Advanced Planning and

______________________________________________________________SAP AG 1

SAP-System______________________________________________________________

Optimization

Use

In SAP SCM 4.1 the following changes have been made to the IMG structure:

Deleted IMG nodes and IMG activities:

Maintenance and Service Planning (SCM-APO-MSC)

- Define Number Range for Maintenance Items

Alert Monitor (SCM-APO-AMO)

- Alert MonitorThis IMG node and all related activities can now be found under SCM Basis.For more information, see the release note Changes in the Alert Monitor.

Interfaces (SCM-APO-INT)

- IntegrationAll the activities belonging to this IMG node can now be found under Integration with SAPComponents -> Integration of SAP SCM and and SAP R/3.For more information, see the release note Implementation Guide for the SAP APO Core Interface(APO-CIF-IMG).

Product Interchangeability - Master Data (SCM-APO-MD-INC)

- Maintain Application Settings

Vehicle Scheduling Optimization (SCM-APO-VS-OPT)

- Define Additional Fields in the Optimization Profile

Vehicle Scheduling Basic Functions (SCM-APO-VS-BF)

- Maintain Compatibility of Means of Transport/Transportation Group

- Maintain Compatibility of Location/Means of Transport

- Maintain Compatibility of Means of Transport Between Transportation Groups

Supply Network Planning (SCM-APO-SNP)

- Maintain Global Setting for the Optimizer in SNP

New IMG Nodes and IMG Activities:

Advanced Planning and Optimization

______________________________________________________________SAP AG 2

SAP-System______________________________________________________________

Maintenance and Service Planning (SCM-APO-MSP)

- Define Counter Types

Master Data (SCM-APO-MD)

- Version Management (SCM-APO-MD-VM)

- Create Parallel Processing Profile for Planning Version Copy

- Location (SCM-APO-MD-LO)

- Activate Change Documents

- Product (SCM-APO-MD-PR)


- Transportation Lane (SCM-APO-MD-TL)


- Quota Arrangement (SCM-APO-MD)


- Resource (SCM-APO-MD-RE)

- BAdI: Change PP/DS Bucket

- Product Interchangeability (SCM-APO-MD-INC) -> Application Settings

- Maintain Attribute Properties

- Maintain Member Types

- Maintain Replacement Types

- Maintain Interchangeability Types and Assign Replacement Types

- Maintain Default Graphic Profile

- Integrated Product and Process Engineering (SCM-APO-MD-PPE)

- Define Settings for Object Dependencies in the iPPE Process Structure

- Define Settings for Consistency Check

General Settings -> Settings for the Production Data Structure ->

- Define Settings for Generating Production Data Structures (PDS)

- Determine Message Handling for Generating PDS

Production Planning and Detailed Scheduling (SCM-APO-PPS)

- Global Settings

- Transfer Characteristic Requirements to Stock Transfer Doc.

______________________________________________________________SAP AG 3

SAP-System______________________________________________________________

- Heuristics

- Define Sort Profile

- Define Special Sorting

- BAdIs -> Business Add-Ins for R/3 PP/DS Integration

- BAdI: Adjustment of Fixed Pegging for Document Change

Product and Process Confirmation (SCM-APO-PPS-PPC)

- Define Control Parameters

Detailed Scheduling Planning Board (SCM-APO-PPS-DST)

- Business Add-Ins (BAdIs) for PP/DS - > Business Add-Ins for the Detailed SchedulingPlanning Board

- Configure Interface for Error-Tolerant Scheduling

Product View (SCM-APO-PPS-PVW)

- Order View

- Define Selection Rules for Product View

Time and Scheduling Functions (SCM-APO-ATP-SCH)

- Determine Assignment of Item Category to Process Alias

Vehicle Scheduling (SCM-APO-VS)

- BAdI: TP/VS Authorization Checks

- BAdI: TP/VS: Freight Units

- BAdI: TP/VS Optimizer: Preprocessing

Vehicle Scheduling Basic Functions (SCM-APO-VS-BF)

- Maintain Means of Transport

Vehicle Scheduling Optimization (SCM-APO-VS-OPT)

- Define Field Catalog

- Define Compatibility Types

Interactive Vehicle Scheduling (SCM-APO-VS-INS)

- Activate GIS Roadmap

______________________________________________________________SAP AG 4

SAP-System______________________________________________________________

Supply Network Planning (SCM-APO-SNP)

- Basic Settings

- Make TLB Basic Settings

- Change Display of Parameters in Interactive TLB

- Sourcing of Forecast: Connect SNP and DP Planning Area

- Profiles

- Define Parallel Processing Profile

Forecasting and Replenishment (SCM-FRE)

- Master Data

- Demand Influencing Factors

- Connectivity

- Time Series

- Forecasting and Replenishment Processor

- Requirement Quantity Optimization

- Order Proposal Management

- Exceptions

- Replenishment Workbench

- Analytics

Renamed and Restructured IMG Nodes and IMG Activities:

Sales Scheduling Agreement Processing (SCM-APO-PPS-CDS)

- Set IDoc Inbound Processing

- Determination of Sold-To Party Over EDI

- Define Default Control Profiles

- Define Default Confirmation ProfilesSee IDoc Inbound Processing and Default Profiles Definable in the Application Menu

Production Data Structure (PDS) (Previously: Runtime Object (LZO)

- Production Data Structure

- Define Settings for Generating Production Data Structures (PDS)

- Determine Message Handling for Generating PDS

______________________________________________________________SAP AG 5

SAP-System______________________________________________________________

1.1.3 SCM-APO-CA APO Cross-Application Components

1.1.3.1 Data Reorganization (New)

Use

As of SAP SCM 4.1, you can find the following programs for reorganization in the SAP Easy Accessmenu under Advanced Planning and Optimization -> APO Administration -> Reorganization:

General SAP APO

- Delete Alerts

- Reorganize liveCache Objects in the Background

- Check Sales Order and Delivery Demands

- Application Log: Delete Expired Logs

Integration

- Delete Entries in the Application Log

Integration/Master Data

- Reorganize GIS Pre-selection

Demand Planning

- Reorganize Planned Independent Requirements

- Manage Job Logs

- Check liveCache Time Series Data

- Toolbox for Planning Object Structures

Global ATP

- Check Sales Order and Delivery Requirements

- ATP: (SD) - Delete Orders from the Database

- Product Allocation Assignment from Sales Orders

- Product Allocation Assignment: Check

- Product Allocation Assignment: Update

- Delete Application Log

- Delete C-Log Data

______________________________________________________________SAP AG 6

SAP-System______________________________________________________________

Production Planning

- Delete Logs

- Delete Production Data Structures

Transportation Planning/ Vehicle Scheduling

- Delete Completed Deliveries

- Delete Completed Deliveries in the Background

- Delete Completed Shipments

- Delete Completed Shipments in the Background

1.1.3.2 APO Consistency Checks

Use

In Release SCM 4.1 several APO consistency checks are easily available from the Easy Access menu (Advanced Planning and Optimization -> APO Administration - > Consistency Checks) .

The following tests are available:

General APO

- Sales order and delivery requirements checks

- LiveCache checks and tools

- Model and versions consistency checks

- Order Document Management Customizing check

- Order document consistency check

Integration

- CIF postprocessing function

- CIF postprocessing multiple call function

- CIF compare/reconcile function

Demand Planning

- Time series consistency checks

______________________________________________________________SAP AG 7

SAP-System______________________________________________________________

- Planning object structures consistency checks

Supply Network Planning



Capable-to-Match

- Master data consistency check

Production Planning / Detailed Scheduling

- Reorganization of pegging areas and account assignment objects

- PP/DS runtime object check


- Consistency of product variants between APO and R/3

Global ATP


- Product allocation assignment by sales orders

- Control product allocation assignment

- Product allocation assignment update

Transport Planning/Vehicle Scheduling

- Consistency check for vehicle scheduling

1.1.3.3 SCM-APO-CA-CDP Characteristics-Dependent Planning

1.1.3.3.1 Consistency Check for Product Variants (New)

Use

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, you can check in the CIF comparison/reconciliation oftransaction data whether product variants have the same configuration data in both systems. You can alsouse the option Check Details to specify that the characteristic values for the product variants are alsochecked.

______________________________________________________________SAP AG 8

SAP-System______________________________________________________________

You execute the comparison under Advanced Planning and Optimization -> APO Administration ->Integration -> Comparison of Master Data -> Comparison of Product Variants.

1.1.3.3.2 Process Change: Generate Production Data Structures (PDS) fromiPPE Data (New/Changed)

Use

As of SAP SCM 4.1, you must generate a production data structure (PDS) for iPPE data to be able to usethe data for planning. This also applies for already existing data. The production version is used forgenerating a PDS.

- Current Process if Using Connected DIMP System:You have created iPPE data in the DIMP system, and transferred the data using the Core Interface(CIF) to the SAP APO system. The data were active immediately in the SAP APO system, andavailable for planning.

- New Process if Using Connected DIMP System:You create iPPE data in the DIMP system. You transfer the data using the Core Interface (CIF) tothe SAP APO system. The data are inactive here and cannot be used for planning. You generate aproduction data structure (PDS) from the production versions of the relevant master data. Duringgeneration, the system checks if the data are correct. If the data contains errors, no PDS isgenerated; the data retains its previous status and is available for planning. If the system hassuccessfully generated the production data structure, the changed data can be used for planning. Theprevious status of the data is no longer available.

- Process for iPPE as Standalone Scenario in SAP APO:You create iPPE data in the SAP APO system. In the standalone scenario, you have the option ofgenerating production data structures with new or changed data automatically, or using the data,which is at first inactive, at a later point in time. In this case, you also generate a production datastructure from the relevant production version. After the system has generated the production datastructure, the data are available for planning.

Check Production Data Structure (Check PDS)

As of SAP SCM 4.1, you can generate iPPE master data in a check PDS and monitor if the results aresuitable for planning. This check PDS can only be generated for PP/DS and inactive planning versions.Check PDSs cannot be generated in the active planning version 000.

You can create orders for check PDSs and execute all steps of your planning process. If the data arecorrect, you can generate the PDS in the active planning version. The status of the PDS in the activeplanning version is also available in all inactive planning versions assigned to the models that are

______________________________________________________________SAP AG 9

SAP-System______________________________________________________________

assigned to the production version.

Effects on Existing Data

You must generate the production data structures at least once for all existing data.

See also

Release Information for Topic:

Rename Runtime object (RTO) to Production Data Structure (PDS)

There is a check that determines if iPPE data used to generate production data structures are correct andsuitable for planning.

See also the Release Information for Topic:

Consistency Check for iPPE Data

1.1.3.3.3 Bucket-Oriented Block Planning (Changed)

Use

The Block Planning with Buckets has been changed in SCM 4.1. Now, in block planning, you canexecute a bucket-oriented capacity check based on PP/DS buckets.

The advantage of a bucket-oriented capacity check in block planning as opposed to infinite planning isthat an operation can only be scheduled to a particular block if sufficient capacity is available for thisoperation. The advantage over the previous finite planning is that a maximum capacity load is achievedfor the resource by avoiding gaps. In the bucket-oriented capacity check, the system starts from thedesired date and proceeds in the planning direction to see whether sufficient bucket capacity is available.If there is, the system reserves it. An operation cannot be scheduled over several buckets. That is, theoperation must be completed by the end of the bucket at the latest.

Until now, you could only use single mixed resources for bucket-oriented block planning as it was onlypossible to create the buckets on the basis of SNP buckets. Now, using the new PP/DS bucketcapacity, you can also use multimixed resources, single activity- and multiactivity resources forbucket-oriented block planning.

As the buckets for block planning are no longer based on the SNP buckets, a resource used forbucket-oriented block planning can now also be used in SNP at the same time. However, SNP still doesnot observe any block planning.

Prerequisites

- You can only execute the bucket-oriented capacity check for the following resource types:

- Single activity resource

- Single mixed resource

______________________________________________________________SAP AG 10

SAP-System______________________________________________________________

- Multiactivity resource (created dimension-free)

- Multimixed resource (created dimension-free)

- The resource to be checked should have the following settings:

- You have created the blocks in the Block Planning tab page.

- You have set the Finite Planning indicator in the General Data tab page.

- You have maintained the parameters for time-continuous capacity in the Time-Cont.Capacitytab page.

- You have maintained the following parameters for the PP/DS bucket capacity in the PP/DSBucket Cap. tab page:In the Bucket Definition field, you choose the setting From Block Planning.In the Finite Capacity field, you choose the setting Bucket Capacity.

- Using the function key Bucket Capacity, you can display the capacity for each bucket.

- The resource to be checked must be assigned as the primary resource to a PPM or to a PDS in themode of an activity and you must have set the indicator calendar resource.You can use the Check Plans function key in the resource maintenance to check whether thesesettings have been made for the resource in the PPM/PDS. The model consistency check alsocarries out the same check.

- If you use bucket-oreinted block planning along with the CTP check, use the standard strategyprofile SAP_BCTP or your own strategy profile with the same settings.


If you already use bucket-oriented block planning, you have to execute the general upgrade report/SAPAPO/OM_LC_UPGRADE_41 for the liveCache before upgrading to SCM 4.1. A CDPconsistency check has to be carried out for block planning. You do this using the report/SAPAPO/OM_CDP_41_PREP_CHECK. For all block planning resources, this report checks whetherthese resources are used as primary resources in PPMs and that the calendar resource indicator hasbeen set. The system records the PPMs for which a block planning resource is not used as the primaryresource and/or the calendar resource indicator is not set.

When upgrading to SCM 4.1, the XPRA /SAPAPO/XPRA_PPDSBUCKET is carried out. The systemuses this XPRA to convert the bucket definition of block planning resources to the new PP/DS bucketcapacity.

See also

Release Information on Changes in Resource Maintenance

Release Information on the Bucket-oriented Capacity Check in the CTP Process

______________________________________________________________SAP AG 11

SAP-System______________________________________________________________

1.1.3.3.4 Block Planning Using Variant Configuration (New)

Use

As of Release SCM 4.1, you can execute block planning using variant configuration. In previous releases,you could only execute block planning for products using the setting CDP.

In Customizing for SAP APO, you determine the configuration relevance for products. The configurationrelevance determines if a product is planned with variant configuration or CDP (characteristics-dependentplanning).

You have the following options for block planning when using the setting VC:

- Block planning using production data structures (PDS)For configurable products, class and characteristics data are used for block planning.For non-configurable products, the classification of an operation from the routing (class type 018) istransferred.Note

You can also execute block planning in this way using the setting CDP.

- Block planning using the production process model:You have assigned the activities to a class and created a standard valuation in the production processmodel.

Resources must be maintained in SAP APO:

A class with class type 400 must be created in SAP APO and assigned to the products. The characteristicsshould be integrated from the R/3 system (plug-in) to ensure that uniform characteristics are used in theR/3 system and in SAP APO.

1.1.3.3.5 'Extended Block Maintenance' Heuristic (New)

Use

As of SAP SCM 4.1, you can use the Extended Block Maintenance heuristic(SAP_CDPBP_03) to create,delete and move blocks in a resource, or to change the length of these blocks.

______________________________________________________________SAP AG 12

SAP-System______________________________________________________________

1.1.3.3.6 Consistency Checks in liveCache - APO DB for CDP and Configuration(Ne

Use

As of SAP SCM 4.1, the system performs a consistency check on order receipts/requirements inconfiguration and characteristics-dependent planning. You can choose either a general or detailed check.

You can also check the characteristic values for block basis definitions in the liveCache and the database.

1.1.3.3.7 Map Reference Characteristics in SAP APO (New)

Use

As of Release SCM 4.1, you can map reference characteristics from the R/3 system (plug-in) in SAPAPO.

You must specify which tables and fields from the R/3 system (plug-in) correspond to the tables andfields in SAP APO as the structures and fields in the R/3 system differ from those in SAP APO.

Effects on Customizing

You assign the tables and fields in the R/3 system and in SAP APO in Customizing for AdvancedPlanning and Optimization under Map Reference Characteristics.

If you use reference refer to table fields that are not included in the standard delivery, you can use theBusiness Add-In (BAdI) Map Reference Characteristics in SAP APO.

______________________________________________________________SAP AG 13

SAP-System______________________________________________________________

1.1.3.3.8 Transfer of Characteristic Requirements to Stock Transfer Doc. (New)

Use

As of SAP SCM 4.1, you can transfer characteristic requirements of demand to stock transfer documents.

The system copies the characteristic requirements from the pegged requirement to the stock transferdocument, and assigns demand and stock transfer documents to each other by means of automaticallyfixed pegging.

This enables you to use characteristic requirements in planning across plants.


You can activate this function in Customizing for Advanced Planning and Optimization under SupplyChain Planning -> Production Planning and Detailed Scheduling (PP/DS) -> Global Settings ->Transfer Characteristic Requirements to Stock Transfer Doc.

1.1.3.4 SCM-APO-CA-COP Collaborative Planning

1.1.3.4.1 Collaborative Planning using ITS Plug-In and Internet CommunicationFramework (New)

Use

As of SAP Web Application Server 6.40, the SAP Internet Transaction Server (SAP ITS) is integratedinto the kernel as an ICF (Internet Communication Framework) service called "ITS Plugin" and the ITSPlugin will be accessed through the ICMan (Internet Communication Manager) like other ICF services.It is possible to use this new function together with collaborative planning.

A separate server is now no longer required for ITS.

Recommendation

If you are installing a new SAP SCM system and do not want to work with the Collaborative AlertMonitor, we recommend that you make use of this function.

Restriction

It is currently not possible to use the ITS Plugin together with the Collaborative Alert Monitor.

______________________________________________________________SAP AG 14

SAP-System______________________________________________________________

Effects on System Administration

You activate the ITS Plugin for the relevant service in the HTTP Service Hierarchy Maintenancetransaction (SICF). Expand the path default_host/sap/bc/gui/sap/its and select the relevant service.Activate it using the context menu. Irrespective of the services that you want to use, you must activatethe CLPGLOBAL service.

1.1.3.5 SCM-APO-CA-VC Variant Configuration

1.1.3.5.1 Consistency Check for Product Variants (New)

Use




Use




- Block planning using production data structures (PDS)For configurable products, class and characteristics data are used for block planning.For non-configurable products, the classification of an operation from the routing (class type 018) is

______________________________________________________________SAP AG 15

SAP-System______________________________________________________________

transferred.Note





1.1.3.5.3 Consistency Checks in liveCache - APO DB for CDP and Configuration(Ne

Use

As of SAP SCM 4.1, the system performs a consistency check on order receipts/requirements inconfiguration and characteristics-dependent planning. You can choose either a general or detailed check.

You can also check the characteristic values for block basis definitions in the liveCache and the database.

1.1.3.5.4 Map Reference Characteristics in SAP APO (New)

Use

As of Release SCM 4.1, you can map reference characteristics from the R/3 system (plug-in) in SAPAPO.

You must specify which tables and fields from the R/3 system (plug-in) correspond to the tables andfields in SAP APO as the structures and fields in the R/3 system differ from those in SAP APO.

______________________________________________________________SAP AG 16

SAP-System______________________________________________________________


You assign the tables and fields in the R/3 system and in SAP APO in Customizing for AdvancedPlanning and Optimization under Map Reference Characteristics.

If you use reference refer to table fields that are not included in the standard delivery, you can use theBusiness Add-In (BAdI) Map Reference Characteristics in SAP APO.

1.1.4 SCM-APO-MD Master Data

1.1.4.1 Logging of Master Data Changes with Change Documents (New)

Use

As of SAP SCM 4.1, by making the appropriate setting in Customizing for SAP APO, you can havechanges to the following master data objects logged in the system:

- Location

- Product

- Transportation lane

- Quota arrangement

This enables you to keep track of how and when master data is changed.

To activate change logging for one of the aforementioned object types, choose the relevant master dataunder Advanced Planning and Optimization -> Master Data in the SAP SCM Implementation Guide, andthen Activate Change Documents. Here you can define the subobject types belonging to this object typethat are to be subject to change logging.

Change logging is not active in the standard system.

If change logging is active, the system generates change documents if changes are made to the subobjectspreselected in Customizing. To display the change documents, invoke the Display Change Documentsfunction in the SAP APO menu under the relevant master data.

______________________________________________________________SAP AG 17

SAP-System______________________________________________________________

1.1.4.2 Extended Hierarchy (New)

Use

As of SAP SCM 4.1, the hierarchy structure extended hierarchy is available for the creation ofhierarchies. You can use the extended hierarchy if a hierarchy node is to be assigned to several parentnodes. This can make sense, for example, in Transportation Planning/ Vehicle Scheduling (TP/VS),where a plant supplies a customer and several alternative itineraries via different transshipment locations(such as ports) are available. In this case, with the extended hierarchy, you can assign a plant (hierarchylevel 2) to several transshipment locations (hierarchy level 1).

You define the hierarchy structure for the extended hierarchy in Customizing under Define HierarchyStructure. You can create and change the extended hierarchy in the SAP APO menu under Master Data-> Hierarchy -> Maintain Hierarchy.

See also

Various Functional Enhancements in TP/VS

1.1.4.3 Fast Entry of Hierarchy Nodes (Extended)

Use

As of SAP SCM 4.1, a fast-entry screen area is available in the maintenance transaction for hierarchies(in the SAP-APO menu under Master Data -> Hierarchy -> Maintain Hierarchy). This functionenables you to add hierarchy nodes quickly and easily.

1.1.4.4 Display Profiles for Master Data Maintenance (New)

Use

______________________________________________________________SAP AG 18

SAP-System______________________________________________________________

In the standard system, all tab pages are displayed in master data maintenance. As of SAP SCM 4.1, youcan create display profiles for locations, products, and location products, in order to suppress individualtab pages. This enables you to gain a better overview of master data maintenance and tailor the latter tosuit your own particular requirements.

You can create the following display profile categories:

- Template profilesTemplate profiles are created by the system administrator for certain user groups (e.g. for all usersin planning). Template profiles are used by the system for all users who have not created their ownuser profile.

- User profilesUser profiles are created by users on the basis of template profiles and can be changed by themwhenever they wish. A user can have several user profiles for several template profiles.

- Standard template profiles and standard user profilesIf the Standard Profile indicator has been set in a template or user profile, the system uses it as astandard template profile or a standard user profile. There can only ever be one standard template orstandard user profile. If a user has been assigned to a standard template profile, this is automaticallyused if the user has not created his own standard user profile. If a user has created a standard userprofile, this is used by default.If neither a standard nor a template profile has been created, the system displays all tab pages inmaster data maintenance.

1.1.4.5 Where-Used List for Master Data (New)

Use

As of SAP SCM 4.1, a where-used function is available for the following master data object types in SAPAPO:

- Location

- ProductLocation product

- Production process model

- Production data structure

- Resource

______________________________________________________________SAP AG 19

SAP-System______________________________________________________________

- Transportation laneProduct-specific transportation laneMeans of transport

With the where-used list, you can display dependent objects linked to a master data object, such asdependent locations for a product. You obtain an overview of where a master data object is used. This isparticularly important if you are thinking of deleting an object.

For objects with many dependencies, we recommend running the where-used list function in thebackground and loading the results later.

To invoke the where-used list function, choose Advanced Planning and Optimization -> Master Data-> Master Data Object (Location, Product, Production Process Model, Product, Production ProcessModel, Production Data Structure, Resource or Transportation Lane) -> Where-Used List from the SAPEasy Access mySAP Supply Chain Management screen.

1.1.4.6 Mass Maintenance of Sales Scheduling Agreements (New)

Use

As of SAP SCM 4.1 you can change any data relating to sales scheduling agreement items, provided thatit is data that can also be changed in Master Data Maintenance.You can activate or deactivate sales scheduling agreements and change the scheduling agreement profileand the confirmation profile.


Choose Advanced Planning and Optimization -> Master Data -> Mass Maintenance and select the objecttype Sales Scheduling Agreement.

See also

For more information see the release information on Mass Maintenance of Master Data and the SAPLibrary for SAP Advanced Planning and Optimization underSAP APO Master Data -> MassMaintenance.

______________________________________________________________SAP AG 20

SAP-System______________________________________________________________

1.1.4.7 SCM-APO-MD-LO Location

1.1.4.7.1 Subcontracting for Multiple Plants with Loc. Type Subcontractor(New)

Use

Up to now, a subcontractor was mapped in SAP APO as a vendor location (location type Vendor).Subcontracting for multiple plants could not be mapped in SAP APO, since the system could notdistinguish between the plants, and mixed up the receipts and requirements for the plants.

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, the new location type Subcontractor is available. Youcan assign both a plant and a vendor in this subcontractor location. Planning for a plant-vendorcombination now takes place in the subcontractor location. If a subcontractor works for multiple plants,you can map this situation by creating multiple subcontractor locations each with its own plant-vendorcombinations.

You create the subcontractor location manually in the location master data maintenance in SAP APO.The subcontractor location is not integrated with SAP R/3.

1.1.4.8 SCM-APO-MD-PR Product

1.1.4.8.1 Assignment of Category Groups for ATD Receipt and ATD Issue(Enhanced)

Use

Previously, you have been able to specify which order categories contribute to increasing and reducingthe available-to-deploy quantity (ATD quantity). To do this, you defined a category group for both theATD receipt and ATD issue in the location master data.

As of SAP SCM 4.1, you can make this specification not just for location, but also for a product at alocation. This means you can also assign the category groups for the ATD receipt and issue in thelocation product master (on the SNP 2tab page). During deployment execution, the system first checkswhether the category group has been specified for the location product. If not, the system performschecks on the location level. If a category has not been defined for the location either, the system uses thedefault ATR (receipt) or ATI (issue) category group.

______________________________________________________________SAP AG 21

SAP-System______________________________________________________________

1.1.4.9 SCM-APO-MD-INC Product Interchangeability - Master Data

1.1.4.9.1 New Functions in Master Data for Product Interchangeability

Use

As of SAP SCM 4.1 the following new functions in master data for product interchangeability aresupported to provide a more flexible usage of the product interchangeability service. This fulfills thetechnical prerequisites for the use of the new functions in subsequent releases.

- One-to-many substitution (1:n substitution)A product is replaced by a group of individual products (also called product combination).In subsequent releases this function will be supported by the new ATP and SPP processes.

- Many-to-one substitution (n:1 substitution)

- A group of products is replaced by a single assembly

- A number of individual products are replaced by the same productThat means, one supersession chain contains two different discontinuation steps with the samesuccessor product (A --> C and B --> C).

In subsequent releases this function will be supported by the new ATP and SPP processes.

- Many-to-many substitution (n:m substitution)A group of individual products is replaced by another group of individual products.In subsequent releases this function will be supported by the new ATP and SPP processes.

- Multi level replacementA substituted product is again substituted with a new product or a group of products. This could be acombination of one-to-one or one-to-many substitutions or a combination of both.In subsequent releases this function will be supported by the new ATP and SPP processes.

- Application settingsIn order to create various alternatives to a simple product-to-product substitution, for instance, aone-to-many substitution with products only or a one-to-one substitution with assemblies only, thefollowing new attributes are introduced:

- Basic member type

- Member type

- Replacement type

- Product substitution procedure

______________________________________________________________SAP AG 22

SAP-System______________________________________________________________

This is a new interchangeability group type. You can use the product substitution procedure forgrouping a number of interchangeability groups that are used by the ATP application.

- Application relevanceWith this indicator you can specify whether an interchangeability group is relevant for planning,ATP or both.

- Status management for interchangeability groupsThis function is required to control the usage of an interchangeability group by various otherapplications.

- New attributes for superssesion chainIn order to handle special cases of product substitution, the following attributes are introduced forthe interchangeability group type supersession chain:

- Quantity factor

- Priority factor

- Demand percentage

- Successor product planning date

- Stock exhaustion date

- Stock exhaustion warning date

- Additional information

- Location dependency of attributesSome attributes may be different depending on the location. With this function you can control,whether an attribute is specific to a certain location or valid in all locations.

- Usability improvements on the user interface:

- Graphical display areaA new graphical display area is provided in order to represent an interchangeability groupgraphically.

- Collapsible screen areasYou can collapse/expand all areas on the user interface.

- Enhancements in user settings

- You can activate/deactivate predefined replacement types for an interchangeability group

- You can set one replacement type as the default replacement type at user level

- You can activate/deactivate the graphical display area

- You can choose your default search option

- XML upload via background jobA new report is provided in order to transfer interchangeability master data in XML format from thelegacy system to the SAP APO system via background job.

______________________________________________________________SAP AG 23

SAP-System______________________________________________________________

1.1.4.10 SCM-APO-MD-RE Resource

1.1.4.10.1 Changes to the Maintenance of Resources

Use

The maintenance of resources has been changed in SCM 4.1:

Changes to interface

The resources interface has been redesigned in SCM 4.1 to improve usability. Here, the followingmaintenance tab pages were removed:

- Planning parameters

- Standard capacity

The parameters that you previously maintained in these two tab pages were included in a new tab pagedepending on their use.

The following maintenance tab pages were added:

- Time-Cont.CapacityThis tab page contains the planning parameters that only affect the time-continuous capacity of aresource, such as the setup matrix, time buffer, and so on.

- PP/DS Bucket CapacityIn this tab page, you create the parameters for creating PP/DS buckets. (See above.)

- SNP Bucket Capacity (Only available for mixed resourses.)In this tab page, you define the parameters for creating SNP buckets.

The Planning Parameters section was added to the General Data tab page. Here, you create thegeneral planning parameters, such as the Finite Planning or the Finiteness Level.

Introduction of the PP/DS Capacity

The resource maintenance has been enhanced by the tab page PP/DS Bucket Capacity. Using this tabpage, you can define a PP/DS capacity as well as the time-continuous capacity for a resource that you usein PP/DS.

The PP/DS bucket capacity of a resource provides the basis for the bucket-oriented capacity check in theCTP process and in block planning. Until now, in block planning, you could already execute abucket-oriented capacity check using single-mixed resources. This is now possible for several resourcetypes. Moreover, you can now also use a single-mixed resource for SNP and for the bucket-orientedcapacity check at the same time.

You can define PP/DS buckets for the following types of resources:

- Single-activity resource

______________________________________________________________SAP AG 24

SAP-System______________________________________________________________

- Single-mixed resource



A resource with PP/DS bucket capacity must have the following settings:

- You set the indicator Finite Planning in the General Data tab page.

- You maintain the data for the time-continuous available capacity in the Time-Cont.Capacity tabpage.

- You define the following parameters for creating the PP/DS bucket capacity in the PP/DS BucketCap. tab page:

- Bucket Definition

- Bucket Schema

- Bucket Factor

- Finite Capacity

- Using the Bucket Capacity function key, the system displays the capacity profiles for every bucket(for example, capacity in hours).

- Using the Check Plans function key, you can check whether the resource is used as the calendarand primary resource in the PPM or the PDS. This is essential before you can execute abucket-oriented capacity check for the resource. You can also carry out this resource check using themodel consistency check.


If you already use bucket-oriented block planning, you have to execute the XPRA/SAPAPO/XPRA_PPDSBUCKET when upgrading to SCM 4.1. Using this XPRA, the system convertsthe bucket definition of the resources planned in block planning to the new PP/DS bucket capacity.


Note that, as a result of the interface changes in the resource maintenance, existing batch input programsand CATTs may no longer be runable.


Customizing of the master data has been enhanced by the BAdI Change PP/DS Bucket.

See also

Release Information on Bucket-Oriented Capacity Check in the CTP Process

Release Information on Bucket-Oriented Block Planning

______________________________________________________________SAP AG 25

SAP-System______________________________________________________________

1.1.4.11 SCM-APO-MD-PPE Product and Process Engineering

1.1.4.11.1 Consistency Check for iPPE Data

Use

As of SCM 4.1, you can use the iPPE consistency check in SAP APO to check the master data of one ormore products whose master data were maintained in iPPE before using the data in other functions suchas Demand Planning and Production Planning.

The master data required for manufacturing a product are bundled in a production version. Therefore,data in production versions is checked in the consistency check. You can check several productionversions.

You call up the consistency check in the following way:

- As program PPE_CONSISTENCY_CHECK to check mass data

- As report on the Reports tab page in the navigation area of the iPPE Workbench Professional tocheck one or more production versions

- In the context menu of the iPPE Workbench Professional

- As an individual transaction. Choose Integrated Product and Process Engineering (iPPE) ->iPPE Consistency Check in the SAP Easy Access Menu.

The consistency check can be activated for generating production data structures and for preventing thegeneration of production data structures that are not suitable for planning.

You can find Customizing for the consistency check in the IMG under Advanced Planning andOptimization -> Master Data -> Integrated Product and Process Engineering (iPPE) -> Define Settingsfor Consistency Check.

You can find Customizing for message handling and generating production data structures in the IMGunder Advanced Planning and Optimization -> Master Data -> Integrated Product and ProcessEngineering (iPPE) -> General Settings for Production Data Structure.

1.1.4.11.2 Extended Process Integration of iPPE Data

Use

______________________________________________________________SAP AG 26

SAP-System______________________________________________________________

- Fixed Quantity Consumption at Variants:As of SAP SCM 4.1, you can maintain fixed quantity consumptions for input materials(components). You maintain a fixed quantity consumption when the quantity of the material useddoes not depend on the lot size. The fixed quantity consumption can be maintained for each changestatus of the variant. You cannot maintain a variable and a fixed quantity consumption at a variant.The fixed quantity consumption is not evaluated for repetitive manufacturing and for SNP.The fixed quantity consumption can only be used at the assembly item for an assembly.

- Fixed and Variable Duration and Consumption at Activities:As of SAP SCM 4.1, you can maintain fixed and variable durations and consumptions at all setup,teardown, and production activities, except for line routing.

- Cost Fields in the Access:The access contains a field for single-level variable costs that are included in SNP. This fieldcontains the quantity-dependent costs that results from using the production version.You can also specify a cost function in the access that uses the optimizer to calculate the productioncosts for fluctuating product quantities.The access also contains multi-level cost fields (fixed and variable). These contain the costs thatresult from using the production version. In contrast to the single-level costs, the costs for providingthe components are already included here. The variable cost field is quantity-dependent, whereas thefixed cost field is quantity-independent.

- Procurement Priority:You can maintain the procurement priority in the access. In planning, CTM chooses the source ofsupply with the highest priority. If the procurement priority was not maintained, or there are severalsources of supply with the same procurement priority, the multi-level costs are evaluated.

- Aggregate Scrap:You can use the Aggregate Scrap indicator if scrap between the activities that have apredecessor-successor relationship should be cumulated. The system then determines the scrap ofthe connected activities and calculates the required material quantity.

- Usage of Demand Planning in the Access:You can create accesses with the usage 'Demand Planning'. You can execute Demand Planning forthe relevant production version in SAP SCM.

All indicators and fields mentioned above can also be used in the iPPE Workbench Express and theiPPE Workbench Professional.

- Link to Mass Maintenance:As of SAP SCM 4.1., you can edit iPPE data using mass maintenance. Attributes can only bemaintained in a change status of a variant or mode. You cannot create new change statuses.

- Block Planning in iPPE:Block planning involves forecasting and preassigning resource capacities for products with specificproperties.As of SCM APO 4.1, you can define block basis definitions for resources in the routing activities.Activities that are planned for a certain resource in block planning are described using classes andcharacteristics. Only orders for which the characteristic values of the activities correspond to theblock basis definition are scheduled for a block. You can use block planning in iPPE forconfigurable and non-configurable products.

______________________________________________________________SAP AG 27

SAP-System______________________________________________________________

1.1.4.11.3 iPPE Workbench Express and iPPE Workbench Professional (New /Changed)

Use

As of SAP SCM 4.1, the iPPE Workbench is called the iPPE Workbench Professional.

As of SCM 4.1, you can use the iPPE Workbench Express in addition to the iPPE WorkbenchProfessional. The iPPE Workbench Express has no functions in addition to those contained in theiPPE Workbench Professional.

- You can use the iPPE Workbench Express to create, change, and display the following data:

- Production versions

- Single-level product structures with object dependencies in a production version

- SNP routings and routings for a production version

- You can use change numbers with validity periods to maintain data in the iPPE WorkbenchExpress.

- You cannot display, edit, or create the following iPPE objects in the iPPE Workbench Express:

- Line balances

- Line structures

- Color schemes

- Focus objects

- Document assignments

- Joint products

- Alternative decompositions

- Long texts

- Configuration simulation

______________________________________________________________SAP AG 28

SAP-System______________________________________________________________

- Products

- Resources

- Time-dependent planning parameters

- References to phantom assemblies

- Parallel sequences in routings

- You can copy existing production versions with the relevant product and process structure in theiPPE Workbench Express if the production versions correspond to the restrictions listed above.

- You can find the Customizing for the profiles of the iPPE Workbench Express in the iPPECustomizing under Define User Profiles for iPPE Workbench Express.


- Data that were maintained in the iPPE Workbench Professional can be edited in the iPPEWorkbench Express if the data correspond to the restrictions listed above.

- Production versions whose data can be displayed and maintained the iPPE Workbench Expressare marked with the (@08@) icon.

- If you cannot or only partially display the production versions and the relevant data in the iPPEWorkbench Express, you can access, display, and edit the data in the iPPE WorkbenchProfessional.

1.1.4.11.4 Process Change: Generate Production Data Structures (PDS) fromiPPE Data (New/Changed)

Use



- New Process if Using Connected DIMP System:You create iPPE data in the DIMP system. You transfer the data using the Core Interface (CIF) tothe SAP APO system. The data are inactive here and cannot be used for planning. You generate aproduction data structure (PDS) from the production versions of the relevant master data. Duringgeneration, the system checks if the data are correct. If the data contains errors, no PDS is

______________________________________________________________SAP AG 29

SAP-System______________________________________________________________

generated; the data retains its previous status and is available for planning. If the system hassuccessfully generated the production data structure, the changed data can be used for planning. Theprevious status of the data is no longer available.




You can create orders for check PDSs and execute all steps of your planning process. If the data arecorrect, you can generate the PDS in the active planning version. The status of the PDS in the activeplanning version is also available in all inactive planning versions assigned to the models that areassigned to the production version.



See also






1.1.4.11.5 Production Data Structure (PDS): Supported Uses in Planning (New)

Use

The production data structure is a master data in SAP APO that can be used in place of the PPM fordifferent planning applications.

The production data structure is generated from production version data.

The system generates production data structures containing classic BOMs and routings automaticallyafter the data has been transferred using the APO Core Interface.

______________________________________________________________SAP AG 30

SAP-System______________________________________________________________

You must generate production data structures manually or using a report for production versions thatcontain iPPE master data after the data has been transferred.

As of SAP SCM 4.1, you can also use the production data structure in Production Planning and DetailedScheduling (PP/DS) for the following planning applications:

- Production Planning and Detailed Scheduling (PP/DS) with Subcontracting

- Supply Network Planning (SNP)

- Supply Network Planning (SNP)with Subcontracting

- Capable-to-Match Planning (CTM)

- Capable-to-Match Planning (CTM) with Subcontracting

- Block Planning and Characteristics-Dependent Planning (CDP)

- Demand Planning (DP)

See also

Release Information:

Rename Runtime Object (RTO) to Production Data Structure (PDS)

Process Change: Generate Production Data Structures (PDS) from iPPE Data

1.1.4.11.6 Rename Runtime Object (RTO) to Production Data Structure (PDS)(Changed)

Use

As of SAP SCM 4.1, EA-IPPE 3.0, and PI2004.1 (SAP_APPL 3.1 and above), 'runtime object (RTO)'has been renamed to production data structure (PDS). This applies to all compound words using the term'runtime object'.

There are different types of production data structures (PDS) that can be differentiated according towhere the master data originated from and the usage / application in planning.

Master Data Source:

- Production data structure generated from iPPE data

- Production data structure generated from R/3 data, that is, classic master data (BOM, routing,recipe)

Usage / Application in Planning:

______________________________________________________________SAP AG 31

SAP-System______________________________________________________________

- DP production data structure

- SNP production data structure

- CTM production data structure

- PP/DS production data structure

1.1.4.12 SCM-APO-MD-CL Classes and Characteristics


Use




- Block planning using production data structures (PDS)For configurable products, class and characteristics data are used for block planning.For non-configurable products, the classification of an operation from the routing (class type 018) istransferred.Note





______________________________________________________________SAP AG 32

SAP-System______________________________________________________________

1.1.4.13 SCM-APO-MD-PDS Production Data Structure

1.1.4.13.1 PP/DS Production Data Structure Comparison (Previously: PP/DSRuntime Object (New)

Use

As of SAP SCM 4.1 you can compare R/3 master data with the PP/DS production data structure generatedfrom it in SAP APO. This means that you can check whether R/3 data has been transferred to SAP APOcorrectly.This function is made up of two comparisons:

1. Comparison of the Change DateYou can use this simple comparison to check whether R/3 master data or changes to it has alreadybeen transferred to SAP APO, based on the date of the last change to the bill of material, routing,master recipe and production version.

2. Comparison of the Explosion ResultsYou can use this comparison to carry out a detailed check of the master data, based on the explosionresults.During the comparison, the explosion result of the R/3 manufacturing order (production or processorder) is simulated and compared with the simulated explosion result of the PP/DS production datastructure in SAP APO.Within this comparison, the system compares operations, phases, input and output products and theactivity relationships of the manufacturing order.

NoteYou should note that the master data explosion for orders in the comparison is simulated andused as the basis for the comparison. If Business Add-Ins are executed during the comparisonthe result of the comparison may be incorrect.

3. Retransfer of the Master DataFor deviating master data, you can carry out a retransfer of the PP/DS production data structurefrom SAP R/3 to SAP APO.

Choose Advanced Planning and Optimization -> APO Administration -> Integration -> CompareMaster Data -> Compare PP/DS Production Data Structure.

See also

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAP APO) under Integration of SAP APO and SAP R/3 -> Technical Integration -> SAP APO Core

______________________________________________________________SAP AG 33

SAP-System______________________________________________________________

Interface .

For more information about the name change from PP/DS runtime object (PP/DS-LZO) to PP/DSproduction data structure (PP/DS-PDS) see the release notes Renaming: Runtime Object (LZO) -Production Data Structure (PDS).

1.1.4.13.2 Integration of Order BOMs/WBS BOMs (New)

Use

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004, you can generate a production data structure for orderand WBS BOMs, and transfer these to SAP APO. You can also transfer substructures.

You execute the transfer in the R/3 system (plug-in) under Logistics -> Central Functions -> SupplyChain Planning Interface -> Core Interface Advanced Planning and Optimization -> Integration Model-> Change Transfer -> Production Data Structure (PDS) -> Transfer Order BOM/WBS BOM.

You can call the transferred order and WBS BOMs in SAP APO under Advanced Planning andOptimization -> Master Data -> Production Data Structure -> Display Production Data Structures.Order and WBS BOMs have the source of supply type FOCUS.


Use








______________________________________________________________SAP AG 34

SAP-System______________________________________________________________






See also




1.1.4.13.4 Rename Runtime Object (RTO) to Production Data Structure (PDS)(Changed)

Use

As of SAP SCM 4.1, EA-IPPE 3.0, and PI2004.1 (SAP_APPL 3.1 and above), 'runtime object (RTO)'has been renamed to production data structure (PDS). This applies to all compound words using the term'runtime object'.

There are different types of production data structures (PDS) that can be differentiated according towhere the master data originated from and the usage / application in planning.

Master Data Source:

- Production data structure generated from iPPE data

- Production data structure generated from R/3 data, that is, classic master data (BOM, routing,recipe)

Usage / Application in Planning:

- DP production data structure

- SNP production data structure

- CTM production data structure

- PP/DS production data structure

______________________________________________________________SAP AG 35

SAP-System______________________________________________________________

1.1.4.13.5 SCM-APO-MD-PDS-SIM Display and Simulation

1.1.4.13.5.1 Displaying production data structures (PDS)

Use

As of SAP SCM 4.1 there is a new display function for production data structures (PDS). This functionprovides a useful tool for troubleshooting:

- Data transfers that use the SAP APO Core Interface (CIF)

- Planning (PDS displays the data used by the planning function)

With the PDS display function you can:

- Display the complete PDS (for example, with all input and output components) for every validitydate and configuration

- Display old versions of the PDS, if they exist

- Simulate what a PDS would look like if it were generated based on current iPPE data for PP/DS

- Display specific PDS information for a given date and configuration

The transaction displays production data structures regardless of their master data type (iPPE, R/3 BOMsand routings and order BOMs).

Limitations

- The function is a display transaction only; it is not possible to save a simulated PDS

- The function is only accessed from SAP APO; it cannot be accessed from SAP R/3

______________________________________________________________SAP AG 36

SAP-System______________________________________________________________

1.1.5 SCM-APO-VS Vehicle Scheduling

1.1.5.1 BAdIs for Transportation Planning/Vehicle Scheduling (New)

Use

As of SAP SCM 4.1, you can use the following Business Add-Ins (BAdIs) in the componentTransportation Planning/Vehicle Scheduling (TP/VS):

- TP/VS: Freight Units(/SAPAPO/VS_FUNIT)

- TP/VS Authorization Checks(/SAPAPO/VS_AUTHORITY)

- TP/VS Optimizer: Preprocessing(/SAPAPO/VS_OPT_PREP)

You can find the BAdIs in the Implementation Guide (IMG) under Advanced Planning and Optimization-> Transportation Planning and Vehicle Scheduling (TP/VS) -> Business Add-Ins (BAdIs) forTP/VS.

1.1.5.2 Various Functional Enhancements in TP/VS (Enhanced)

Use

As of SAP SCM 4.1, the following functional enhancements are available:

- Assigning Locations to Multiple Transshipment LocationsWhen you define hierarchies in master data, you can now assign a location, for example, a plant tomultiple transshipment locations (only for hierarchy structure type Extended Hierarchy). In thisway, you can map several alternative itineraries with different transshipment locations.TP/VS optimization still cannot take this into account, however. Therefore you must definecompatibilities for transshipment locations, for example, between order characteristics andtransshipment location or means of transport and transshipment location. You must define thesecompatibilities in such a way that a unique relationship between the transshipment location and thesource/destination location is passed on to the optimizer.

- Minimal Duration of Goods Wait Time at Transshipment LocationsIn addition to the maximum duration of the goods wait time, you can now also define the minimumduration of the goods wait time at the transshipment location in the location master. These durationsare considered as hard constraints during optimization.

______________________________________________________________SAP AG 37

SAP-System______________________________________________________________

- New Fields in Interactive PlanningThe following new fields are available for freight units in interactive planning:

- Source transportation zone

- Destination transportation zone

- Incoterms

- Weight group and volume groupe (as defined in ATP Customizing)

- Transferring Shipping DataAs of SAP SCM 4.1, shipping data in SAP R/3 (Incoterms, shipping conditions, shipping point,delivery priority, delivery block, route) is transferred to SAP APO. Shipping data for sales orders isupdated in SAP APO if the corresponding sales orders have been changed in SAP R/3.

- Authorization ChecksYou can now perform authorization checks in the component Transportation Planning/VehicleScheduling (TP/VS). To do this, you can use authorization object C_APO_TPVS. You can restrictaccess to certain functions and areas, for example, by using the optimization profile. You can alsouse a Business Add-In (BAdI) (TP/VS Authorization Checks (/SAPAPO/VS_AUTHORITY)) foruser-specific changes.

1.1.5.3 SCM-APO-VS-OPT Vehicle Scheduling Optimization

1.1.5.3.1 Definition of Compatibilities (Enhanced)

Use

As of SAP SCM 4.1, there is a new concept for defining compatibilities and incompatibilities. It offerscomprehensive options that enable you to define compatibilities and incompatibilities between any orderfields, order characteristics, means of transport, and transshipment locations.

You can map the following requirements using compatibilities and incompatibilities:

- Certain orders must not be delivered together, for example, orders with certain Incoterms.

- Certain orders must be delivered together, for example, orders with certain shipping conditions mustbe transported using a certain means of transport.

- Customers, plants, vendors, or distribution centers are to have goods delivered to them via differenttransshipment locations (several different itineraries).

- Orders with a certain weight group or volume group are to be transported using a certain means oftransport.

______________________________________________________________SAP AG 38

SAP-System______________________________________________________________

- You want to combine deliveries, for example, by transportation zone or route.

- Cross-docking is to be executed for orders with a certain weight group or volume group.

An individual transaction is now available for defining compatibilities and incompatibilities ((DefineCompatibilities (/SAPAPO/VS12)). The following fields and IMG activities were deleted as a result ofthis:

- The field Incompatible/Compatible Means of Transport in the location master

- The field Comp. in the transaction Maintain Means of Transport

- The IMG activities Maintain Compatibility of Means of Transport/Transportation Group,Maintain Compatibility of Location/Means of Transport, Maintain Compatibility BetweenTransportation Groups

You can restrict the validity of compatibilities or incompatibilities to certain orders or restrict planning ina certain optimization profile. A new concept is available for filtering orders - the definition ofconditions. Conditions are defined by their period of validity and a maximum of four filter criteria. Thisconcept is also available for defining windows and optimization profiles.

Compatibilities and incompatibilities are taken into account during optimization, in manual planning(tabular and multilevel planning), and during the automatic generation of shipments.


To be able to use compatibilities and incompatibilities from previous releases, you must convert themusing the upgrade report.


The definition of compatibilities and incompatibilities is based on fields. For this reason you must firstdefine a TP/VS field catalog. There are two ways to do this:

- Manually using IMG activity Define Field Catalog

- Automatically using the upgrade report

You must also define compatibility types in Customizing for the component TransportationPlanning/Vehicle Scheduling (TP/VS).

See also

For more information, see the SAP Library under SAP Advanced Planning and Optimization (SAP APO)-> Transportation Management -> Transportation Planning/Vehicle Scheduling (TP/VS) -> Definition ofCompatibilities.

1.1.5.3.2 Optimization Profile (Enhanced)

Use

The following functional changes were made in the optimization profile:

- User-defined filtering options

______________________________________________________________SAP AG 39

SAP-System______________________________________________________________

The field Additional Fields was deleted. As of SAP SCM 4.1, a new concept is available forfiltering orders - the definition of conditions. Conditions are defined by their validity period and amaximum of four filter criteria. This concept is also available for defining compatibilities andwindows.

- Factory calendarYou can now specify a factory calendar for the relative planning horizon and the relative demandhorizon. This means that non-workdays are not taken into account when horizons are calculated.

- The field Consider Requested Delivery Time was deleted. It has been integrated in a newfunction for defining windows.


The definition of conditions is based on fields. For this reason you must first define a TP/VS field catalogin Customizing for Transportation Planning/Vehicle Scheduling (TP/VS).

See also

For more information, see the SAP Library under SAP Advanced Planning and Optimization (SAP APO)-> Transportation Management -> Transportation Planning/Vehicle Scheduling (TP/VS) -> Optimization.

1.1.5.3.3 Definition of Pickup/Delivery Windows (New)

Use

As of SAP SCM 4.1, you can define windows for picking up and delivering orders.

You can map the following requirements using windows:

- Certain dates/times are to be considered during optimization as hard constraints, for example,material availability date.

- Different delivery windows are to be taken into account during optimization for different customers,shipping conditions, and so on.

- The time during which a product is stored after production is to be shortened.

The system considers these windows as constraints during optimization. The active windows as well asthe dates/times determined in interactive planning (transaction /SAPAPO/VS01) are displayed in a newdialog box and on the Details tab page.

You can define windows at order level by restricting their validity to certain orders or by restrictingplanning using a certain optimization profile.

As of SAP SCM 4.1 , a new concept is available for filtering - the definition of conditions. Conditions aredefined by their period of validity and a maximum of four filter criteria. This concept is also available fordefining compatibilities and optimization profiles.

You define the costs that the system takes into account for the windows during optimization in the cost

______________________________________________________________SAP AG 40

SAP-System______________________________________________________________

profile. You can use a Business Add-In (BAdI) to overwrite these costs for certain orders. (TP/VS FreightUnits (/SAPAPO/VS_FUNIT)).

A new transaction is available for defining windows (Define Pickup/Delivery Windows(/SAPAPO/VS11)).


You can use the upgrade report to create soft constraints for delivery windows (standard in previousreleases) and hard constraints for premature pickup (taking the material availability date into account).


The definition of windows and conditions is based on fields. For this reason you must first define aTP/VS field catalog. There are two ways to do this:

- Manually using the IMG activity Define Field Catalog

- Automatically using the upgrade report

See also

For more information, see the SAP Library under SAP Advanced Planning and Optimization (SAP APO)-> Transportation Management -> Transportation Planning/Vehicle Scheduling(TP/VS) -> Optimization-> Definition of Windows.

1.1.5.4 SCM-APO-VS-INS Interactive VS

1.1.5.4.1 Displaying Shipments on Road Maps (New)

Use

As of SAP SCM 4.1, you can display shipments on a road map in interactive planning of the componentTransportation Planning/ Vehicle Scheduling (TP/VS). A route can be displayed either as a road route,that is, the exact route to be followed, or as a symbolic route, that is, a direct connection between theindividual locations. You can also display route descriptions with the travel time and distance of thejourney based on the road network.


You must install a GIS server (GIS = Geographical Information System) and an IGS (Internet GraphicsServer) and connect these to SAP APO. The GIS server is made available by an external provider and isnot part of the standard SAP SCM 4.1 delivery.


To be able to display shipments on road maps, you must first activate the road map in a user-specific way

______________________________________________________________SAP AG 41

SAP-System______________________________________________________________

in Customizing for the component Transportation Planning/Vehicle Scheduling (TP/VS). To do this, usethe activity Activate GIS Road Map.

See also

For more information, see the SAP Library under SAP Advanced Planning and Optimization (SAP APO)-> Transportation Management -> Transportation Planning/Vehicle Scheduling (TP/VS) -> InteractivePlanning -> Planning View -> Displaying Routes for Shipments.

1.1.5.4.2 Interactive Combining of Freight Units (New)

Use

As of SAP SCM 4.1, you can interactively specify that several different freight units are to be deliveredtogether. By combining the required freight units manually, you ensure that they are assigned to the sameshipment during optimization.

See also

Fore more information, see the SAP Library under SAP Advanced Planning and Optimization (SAP APO)-> Transportation Management -> Transportation Planning/Vehicle Scheduling (TP/VS) -> InteractivePlanning -> Manual Order Combining.

1.1.6 SCM-APO-SNP Supply Network Planning (SNP)

1.1.6.1 Automatic Parallel Processing and Scheduling of Jobs

Use

Parallel processing of background jobs

There are several processes in Demand Planning and other applications that often run as background jobs.This can be due to the size of the jobs and the time they take or the routine nature of the task. In order toimprove the performance of such background jobs it is often advisable to run these jobs in several parallelprocesses.

In Release SCM 4.1 parallel processing has been extended to several applications. Making the relevantsettings is simplified by the use of parallel processing profiles that you define in Customizing or theapplication. This profile defines the maximum number of parallel processes, the block size, and as anoption a server group. You assign it to the variant in the application.

______________________________________________________________SAP AG 42

SAP-System______________________________________________________________

The following applications support parallel processing profiles:

- Copy Planning Version (DP)

- Load Planning Area Data from InfoCube

- Create Time Series Objects

- Extraction from Planning Area

- Proportional Factor Calculation

- DP Background Processing

- SNP Heuristic

- SNP Optimizer

Process Chains in SCM

In Release SCM 4.1 this Business Information Warehouse (BW) function has been extended to includeseveral SCM applications. It allows you to set up chains of background jobs. For instance in DemandPlanning you could program a chain that uploads data from a data source to an InfoCube, generate anynew characteristic value combinations, upload the data from the InfoCube to a planning area, carry out aforecast, and release the data to SNP. As well as process types from the listed components, it is possibleto include report programs and several BW functions in process chains.

The SCM components that currently use process chains are:

- SCM Alert Monitor

- SCM Version Copy

- SCM-APO Demand Planning

- SCM-APO Supply Network Planning

- SCM-APO Capable-to-Match Planning


You define parallel processing profiles in general in Customizing under Advanced Planning andOptimization -> Supply Chain Planning -> Demand Planning or Supply Network Planning ->Profiles -> Maintain Parallel Processing Profile.

See also

For more information on parallel processing profiles, see the F1 help for the individual fields and the SAPLibrary documentation under Demand Planning -> Technical Aspects of Demand Planning ->Parallel Processing of Background Jobs.

______________________________________________________________SAP AG 43

SAP-System______________________________________________________________

1.1.6.2 Process Change: Generate Production Data Structures (PDS) from iPPEData (New/Changed)

Use



- New Process if Using Connected DIMP System:You create iPPE data in the DIMP system. You transfer the data using the Core Interface (CIF) tothe SAP APO system. The data are inactive here and cannot be used for planning. You generate aproduction data structure (PDS) from the production versions of the relevant master data. Duringgeneration, the system checks if the data are correct. If the data contains errors, no PDS isgenerated; the data retains its previous status and is available for planning. If the system hassuccessfully generated the production data structure, the changed data can be used for planning. Theprevious status of the data is no longer available.







See also

______________________________________________________________SAP AG 44

SAP-System______________________________________________________________






1.1.6.3 Production Data Structure (PDS): Supported Uses in Planning (New)

Use













See also




______________________________________________________________SAP AG 45

SAP-System______________________________________________________________

1.1.6.4 SNP Heuristic (Enhanced)

Use

In SAP SCM 4.1, the following changes and enhancements have been made to heuristic-based planningin Supply Network Planning (SNP):

Rounding of product quantities

Previously, for heuristic-based planning, product quantities were rounded down based on the base unit ofquantity. This applied for both heuristic-based capacity leveling and manual order changes in interactiveSNP planning. However, dependent demand for components and quantities for co-products were notpreviously rounded.

As of SAP SCM 4.1, dependent demand for components is rounded to the base unit of quantity.Quantities for co-products are rounded down. This means that the planning result is consistent with thebase unit of quantity defined.

Net change planning

Previously, in SNP planning (with the exception of optimization), the system set planning jobs forlocation products, if a planning-relevant change had been made since the previous planning run, such as achange to the demand situation, for instance. The planning jobs were considered by the SNP heuristic, ifyou selected net change planning.

As of SAP SCM 4.1, the system also sets planning jobs for components and co-products, which are thenconsidered by the SNP heuristic during the net change planning.

The system sets planning jobs for distribution demands as well as for distribution receipts.

1.1.6.5 Application Logs for SNP Planning Runs (Enhanced)

Use

Previously, various result and error logs were generated for planning runs in Supply Network Planning(SNP) when you executed planning in the background. While planning results were mainly issued in

______________________________________________________________SAP AG 46

SAP-System______________________________________________________________

spool lists, as of SAP SCM 4.0, error messages were sometimes displayed in application logs based onthe Business Application Log (BAL).

As of SAP SCM 4.1, uniform application logs based on BAL are available for SNP planning runs. Abreakdown of planning results and messages is displayed in this log. There are also filter and sortingoptions. When required, the log also provides detailed information on planning results, such as data forplanned orders and stock transfers.

You can access the logs from the SAP Easy Access screen using a new function under AdvancedPlanning and Optimization -> Supply Network Planning -> Reporting -> Application Logs . Youcan also access the appropriate log from the individual screens for execution of planning in thebackground.

The following enhancements have been made to planning functions:

- SNP heuristic, deployment heuristic and Transport Load Builder (TLB) Previously, planning results were issued in a spool list, and error messages in a detailed error logbased on BAL. As of SAP SCM 4.1, an application log with both planning results and errormessages is available. You can set an indicator to determine whether detailed planning results (datafor planned orders, stock transfers, or TLB shipments) are saved and displayed in the log.For the deployment heuristic and the TLB, you can specify that you also want a spool list to begenerated.

- Enhanced safety stock planningPreviously, both planning results and error messages were issued in a spool list. As of SAP SCM4.1, an application log with planning results and error messages is available. You can set anindicator to determine whether detailed planning results and information about master data isdisplayed.

- Optimization-based planning runs in SNPFor optimization runs in SNP, the previous Optimizer Log Data function, which was already usedto display logs, has been revised and enhanced. The function now contains a list of optimizationruns with relevant data from which you can select a run and display all available logs for this run(such as entry log, results log, message log and costs). The Resulting Costs of Optimizationfunction has been integrated into the new function. A further log containing information on solutionquality has been added. This shows the development of the total costs of the best solution over theruntime of the optimization run.


The Maintain Global Settings for the Optimizer in SNP IMG activity, which enabled you to specifythe the number of log entries, has been removed from the SNP Customizing. You no longer need tospecify the number of log entries, since, as of SAP SCM 4.1, you can enter the availability of logs in daysfor an optimization run.

See also

For more information, see the Supply Network Planning component in the SAP Library.

______________________________________________________________SAP AG 47

SAP-System______________________________________________________________

1.1.6.6 Periodic Lot Size Grouping (Changed)

Use

Previous Situation

Previously, you were able to define a periodic lot size procedure in the location product master forheuristic-based planning in Supply Network Planning (SNP). For this procedure, the system groups thedemand quantities of several consecutive periods and creates the orders to cover demand according to thiscombined demand.

You entered the type and number of periods in the appropriate fields, period type and number of periods.The start of the lot size grouping was in the first period of the time buckets profile defined in the planningbook (generally today's date).

The period in which the combined demand and the order to cover demand were created in, depended onthe settings in the Period Factor field in the location product master. Since the period factor is mainlyused by the system to calculate the availability date of a receipt element within a period, this solution didnot make sense.

New situation

As of SAP SCM 4.1, you can use an indicator in the location product master to determine whether thestart of the lot size grouping is in the first period of the planning buckets profile, as before, or in the firstperiod where there is a shortage of supply. The period in which the combined demand is set and the orderto cover demand is created, is based on the settings you made in the new Strategy Lot Size field.

1.1.6.7 Generation of Alerts with Exit Macros during a Planning Run (New)

Use

Previously, you were able to generate Supply Network Planning (SNP) alerts by defining thecorresponding macros and then executing them in a separate background job after a planning run. Sinceonly start macros and standard macros were executed before the actual planning during SNP planningruns, alerts could be generated directly during the planning run.

As of SAP SCM 4.1, exit macros are automatically executed in some SNP planning runs. If you definethe alert macros as exit macros, the alerts are generated automatically during the planning run. In thisway, you can specify, for instance, that you want the system to issue system alerts for supply shortages.

Exit macros are executed in the following SNP planning runs:

______________________________________________________________SAP AG 48

SAP-System______________________________________________________________

- SNP heuristic run

- SNP optimization run

- SNP deployment optimization run

- Capacity leveling

Exit macros are executed per location product or resource (capacity leveling). However, values that arechanged by the macros are not saved. Only alerts that are generated by an exit macro are saved to thedatabase.

1.1.6.8 Production Data Structure in SNP (New)

Use

As of SAP SCM 4.1, for planning in Supply Network Planning (SNP), you can use a production datastructure (PDS) as an alternative to the production process model (PPM). Similar to the PPM, the PDS isa combination of data from the work list and the bill of materials. The PDS has more flexible options forcombining and reusing data from work lists and bills of materials.

The SNP production data structure is supported by all planning processes, one exception being demandand stock propagation. In addition, you cannot select or delete the objects according to specific PDS inthe Deletion of Transaction Data.

Two options are available for creating a production data structure:

- Generation of an SNP production data structure from iPPE dataYou can either create the iPPE data in a connected DIMP system and transfer it to an SAP SCMsystem using the APO Core Interface (CIF), or you create the data directly in the SAP SCM system.Note that you must use an SNP work list for SNP in the iPPE data. You then create a productionversion for the iPPE data and generate an SNP production data structure from it.

- Generation of an SNP production data structure from SAP R/3 dataYou can generate the SNP PDS directly from the work list, bill of materials, and production versiondata in SAP R/3. To do this, you must select an SNP or SNP subcontracting CIF integrationmodel. The corresponding SAP R/3 data is then transferred to the SAP SCM system and an SNPPDS is then generated automatically in the SAP SCM system.If you select SNP subcontracting, the product master data at the subcontractor location is createdautomatically (as are the components). In addition, the transportation lane between plant andsubcontractor is generated automatically (this is not possible if you use an SNP PPM).

As with the PPM, the PDS is used as a basis for planning in SNP. Note that the execution proceduresdescribed in the documentation also apply for the PDS. This is often not explicitly stated in

______________________________________________________________SAP AG 49

SAP-System______________________________________________________________

documentation.

The SNP PDS can also be used in Capable-to-Match planning (CTM) .

See also

For more information, see the following release notes:

- Production Data Structure (PDS): Supported Planning Types/Applications

- Process Change: Generation of Production Data Structures (PDS)

1.1.6.9 SCM-APO-SNP-BF Basic Functions

1.1.6.9.1 Global SNP Settings - SNP Planning Profile (Changed)

Use

Previously, you were able to make some settings for the Supply Network Planning (SNP) planningprocedures globally in SNP Customizing under Maintain SNP Settings.

As of SAP SCM 4.1, you can save these settings as a profile. You then activate one of the defined SNPplanning profiles that then applies globally for all SNP planning procedures.

For some planning procedures, you can overwrite the settings by entering another SNP planning profile(SNP heuristic, SNP optimizer, deployment heuristic, deployment optimizer, and Transport LoadBuilder) for execution of planning in the background. However, if you execute the SNP planningprocedures using interactive SNP planning, the activated profile applies, since you cannot create a specialSNP planning profile in interactive planning.


SAP delivers a default SNP planning profile that is activated automatically. If you upgrade SAP SCM 4.0to SAP SCM 4.1, the system generates a profile from your settings. This profile is automatically activatedinstead of the default profile.

______________________________________________________________SAP AG 50

SAP-System______________________________________________________________

1.1.6.9.2 Mass Maintenance of Time Series Key Figures (New)

Use

Planning in Supply Network Planning (SNP) is generally based on order key figures. However, insome areas time series key figures can be used (when defining time-dependent restrictions foroptimization-based planning, for instance). Previously, you were only able to edit time series key figuresmanually in interactive SNP planning.

As of SAP SCM 4.1, one function is available for mass maintenance of time series key figures. You canselect time series for a specific planning area and planning time period as well as for specific planningobjects and then define the key figure values. You can either define and change the key figure values forindividual periods or for all periods.

In principle, you can also use this function to process Demand Planning, DP key figures.

See also

For more information, see Supply Network Planning -> Administration of Planning Area -> MassMaintenance of Time Series in the SAP Library.

1.1.6.9.3 Diverse SNP-Relevant Master Data Changes

Use

In SAP SCM 4.1, several small changes have been made to master data that are relevant for SupplyNetwork Planning (SNP). These changes are detailed below.

Quota arrangements for means of transport

Previously, you were only able to define quota arrangements for locations. As of SAP SCM 4.1, you candefine detailed quota arrangements for a target location and a specific means of transport. If you do notenter a means of transport, SNP distributes the quantity evenly over the means of transport that areavailable and, thus, splits the order.

Time-dependent maintenance of penalty costs

Previously, you were able to define penalty costs for late delivery and non-delivery separately for certaintypes of demand. As of SAP SCM 4.1, you can also define time-dependent penalty costs and in doing soassign a time-priority to demands.

Penalty costs are considered during optiomization-based planning.

______________________________________________________________SAP AG 51

SAP-System______________________________________________________________

Adjusting resource consumption according to scrap

Previously, you were able to define a scrap for an activity in the production process model (PPM), whichthen lead to adjustment of the quantity entered for a product. As of SAP SCM 4.1, scrap also leads toadjustment of the resource consumption, if you have set the appropriate indicator in the SNP Customizing(see below).


If you want the system to adjust resource consumptions according to the scrap defined for an activity, youmust set the appropriate indicator in the SNP Customizing under Maintain Global SNP Settings (not setas default).

1.1.6.9.4 Transfer of SNP Orders to OLTP Systems (Enhanced)

Use

In the Set Up Transfer to OLTP Systems IMG activity, you can determine how orders created,changed, or deleted by the system during SNP planning are transferred to OLTP systems. Previously,when you configured a transfer, all generated SNP planned orders and stock transfers were transferred tothe OLTP system.

As of SAP SCM 4.1, you can exclude specific order types from transfers (SNP planned orders, SNP stocktransfers, and SNP stock transfers without source location).


The new indicators in the Set Up Transfer to OLTP Systems IMG activity are set as default so that allgenerated planned orders and stock transfers are transferred.

1.1.6.9.5 SNP Supply, Demand, and Deployment Profile (Changed)

Use

Previously, you were able define the SNP supply profile, the SNP demand profile, and the SNP

______________________________________________________________SAP AG 52

SAP-System______________________________________________________________

deployment profile in the location product master, as well as in the Customizing and the current settingsof the Supply Network Planning (SNP).

As of SAP SCM 4.1, you can only define these profiles in the location product master (from the initialscreen).


The corresponding transactions have been deleted from the SNP Customizing and current settings.

1.1.6.9.6 Sourcing of Forecast (New)

Use

As of SCM 4.1, there is a new IMG activity (Advanced Planning and Optimization --> Supply ChainPlanning --> Suppy Network Planning (SNP) --> Basic Settings --> Sourcing of Forecast: Connect SNPand DP Planning Area) that you can use to source demand planning (DP) forecasts at customer locationsto the various production locations modeled in the supply chain.

The result of the sourcing of forecast updates the global available-to-promise (GATP) product allocationsituation that enables the sourcing of subsequent incoming sales orders to the appropriate productionlocations. Therefore, the sourcing process allows you to realize location-independent consumption byeffecting the consumption of DP forecasts at the customer location by sales orders at the productionlocation.

GATP product allocation and the SNP optimizer should be in active use to realize the sourcing processbecause the SNP optimizer is the "sourcing tool".


Sourcing of Forecast is integrated with SAP APO and the SAP R/3 System. The sourcing processintroduces a new link between the DP and the SNP planning area. This process can be invoked through anSNP planning area because it uses the SNP optimizer as the sourcing tool. The link specifies the DPplanning area (and a key figure in the DP planning area) from which the forecast data will be read.

In addition, there is a standard link between a GATP product allocation group and a DP planning area.The sourcing process uses this link with standard features and without any modification. The sourcingprocess, therefore, creates a three-way link between an SNP planning area, a DP planning area, and aGATP product allocation group.

______________________________________________________________SAP AG 53

SAP-System______________________________________________________________

See also

SAP Library:

SAP Advanced Planning and Optimization (SAP APO) --> Global Available-to-Promise (GATP) -->Product Allocation Settings

SAP Advanced Planning and Optimizer (SAP APO) --> Global Availabile-to-Promise (GATP) -->Availability Check Tools --> Product Allocation Tools

SAP Advanced Planning and Optimizer (SAP APO) --> Supply Chain Processes with SAP APO -->SalesOrder Oriented Planning

1.1.6.10 SCM-APO-SNP-OPT SNP Plan Optimization

1.1.6.10.1 Decomposition Procedures for the Deployment Optimizer (New)

Use

Previously, the decomposition procedures, which can speed up the solution process during theoptimization run, were only available for the SNP optimizer, and not for the deployment optimizer.

As of SAP SCM 4.1, you can also define various decomposition procedures for the deploymentoptimizer. The following procedures are available (as for the SNP optimizer):

- Time decomposition: Speeds up the solution process by dividing the optimization problem into achronological sequence of partial problems that are then solved sequentially.

- Product decomposition: Speeds up the solution process by creating product groups and thensolving the optimization problem for each individual product group.

- Resource decomposition: Speeds up the solution process by producing a sequence of resourcesafter analysing material flow and fundamental optimizer decisions regarding transportation andstorage. Partial problems are then created for the individual resources, and the parts are then solvedsequentially.

In addition. a further method has been added especially for the deployment optimizer:

- Internal deployment decomposition: Can speed up the solution process by dividing theoptimization problem into partial problems that are as small as possible, and then solving themsequentially. This decomposition method is particularly useful if the supply chain model has aparticular problem structure. If the model does not contain capacity restrictions, the products can bedistributed independently of each other in deployment, which can help reduce runtime.

You can also use the SNP priority profile for the deployment optimizer decomposition procedures thatare new to SAP SCM 4.1 . For more information, see release SNP priority profile release information.

______________________________________________________________SAP AG 54

SAP-System______________________________________________________________


You can define the decomposition procedures in the SNP deployment optimizer profile. To do this, selectDefine SNP Deployment Optimizer Profile in the Supply Network Planning Customizing.

1.1.6.10.2 Diverse Functions in the SNP and Deployment Optimizer Area(Enhanced)

Use

Several minor enhancements have been made in the SNP and deployment optimizer area. These aredescribed briefly below.

Forecast horizon

Until now, the forecast horizon that you define in the location product master data was not considered bythe SNP and deployment optimizers. As of SAP SCM 4.1, the SNP and deployment optimizers considerthe forecast horizon if you have set the Forecast Horizon indicator on the Integration tab page of theSNP otimizer profile or the SNP deployment optimizer profile.

Pull and push deployment horizon and SNP checking horizon

Until now, the deployment optimizer only considered the pull or push deployment horizon and the SNPchecking horizon that you define in the SNP deployment optimizer profile, and not in the correspondingsettings in the location product master.

As of SAP SCM 4.1, you can define the pull or push horizon and the SNP checking horizon in thelocation product master as well as in the SNP deployment optimizer profile (on the DeploymentParameters tab page). If you want the deployment optimizer to consider the value defined in thelocation product master, you must enter a value of > 0 and set the Use horizon from productmaster/profile indicator. Otherwise, the sytem uses the value you defined in the deployment optimizerprofile.

Safety stock methods SZ, MZ, and SM

Until now, when using the SZ, MZ and SM safety stock methods that you define in the location productmaster, the SNP optimizer only considered independent demands as well as dependent demands anddistribution demands caused by fixed orders. As of SAP SCM 4.1, this restriction no longer applies (andnow only applies for the MM safety stock method).

Determination of transportation lot size

Until now, you would use the Maintain Global SNP Settings activity of Supply Network PlanningCustomizing to define whether the SNP and deployment optimizers use the rounding value from thetransportation lane lot size profile or from the destination location location product master.

______________________________________________________________SAP AG 55

SAP-System______________________________________________________________

As of SAP SCM 4.1, you can define whether the system takes the values for determination oftransportation lot size soley from the transportation lane lot size profile (maximum and minimum lot sizeand rounding value) or from either the transportation lane lot size profile or the location product master ofthe product at destination location. With the second option, the values from the lot size profile still applyif that profile has been defined and stored in the transportation lane. Otherwise, the values from thelocation product master apply (maximum lot size, rounding value and fixed lot size). The minimum lotsize is an exception: here, it is always the maximum value from the lot size profile and the locationproduct master that applies.

1.1.6.10.3 SNP Priority Profile (New)

Use

Previously, the product and resource decomposition solution methods were available for optimization inSupply Network Planning (SNP). Decomposition methods enable you to reduce runtime and memoryrequirements.

For product and resource decomposition, the system combines both products and resources in partialproblems. These are then solved sequentially. Previously, the order in which the objects are combinedand planned was determined automatically by the system.

As of SAP SCM 4.1, you can determine this order yourself by assigning priorities to the products andresources in an SNP priority profile. In this way, you can specify that important products and resourcesare planned first, for instance.


You create the SNP priority profile in the current settings in SNP under Profiles -> Define PriorityProfiles and assign it to an SNP or deployment optimizer profile in Customizing or in the current settingsof SNP under Profiles -> Defined SNP Optimizer Profile or Define Deployment Optimizer Profile(on the Solution Methods tab page). If you do not define an SNP priority profile, the optimizerdetermines the sequence of objects as before.

______________________________________________________________SAP AG 56

SAP-System______________________________________________________________

1.1.6.10.4 SNP Optimizer Procedures for Fail-Safe Solution Determination (New)

Use

Previously, you have been able to specify a maximum runtime for the SNP optimzer. If the system couldnot find a solution for an optimization problem within this time, the optimization run was terminatedwithout result.

As of SAP SCM 4.1, you can chose how you want the SNP optimizer to proceed if it cannot find asolution within the specified runtime. First, you can enter a runtime extension. If the optimizer does notfind a solution at the end of the extended runtime, you have further options to chose from (such as,simplifying the problem internally in the system or ignoring a partial problem).


You can make these settings in the SNP optimizer profile on the Advanced Settings tab page. To dothis, select Define SNP Optimizer Profile in the Supply Network Planning Customizing.

1.1.6.10.5 Subcontracting (Enhanced)

Use

Previously, in Supply Network Planning (SNP), subcontracting processes were only supported by theSNP heuristic. As of SAP SCM 4.1, both processes, subcontracting with source location andsubcontracting with third-party provision of components are possible within optimization-basedplanning. The SNP optimizer supports the processes to the same extent as the SNP heuristic. Onerestriction to note is that either the transportation capacity or the production capacity should be used as aconstraint for planning, not both.

In SAP SCM 4.1, improvements have also been made to the integration of master data using the APOCore Interface (CIF) with R/3. If you use the new production data structure (PDS) in SNP and select theSNP Subcontracting option in the integration model, the transportation lane from the plant to thesubcontractor location is automatically created in the SAP SCM system for all components, not just forthe end product. The product master data is also automatically transferred to the subcontractor location.

______________________________________________________________SAP AG 57

SAP-System______________________________________________________________

See also

For more information, see the SNP documentation entitled Subcontracting with Source Location inSNP and Subcontracting with Third-Party Provision of Components in SNP and the ProductionData Structure in SNP release information.

1.1.6.11 SCM-APO-SNP-INS Interactive SNP

1.1.6.11.1 Changes and Enhancements to the Graphic in Interactive Planning

Use

The following functions have been added to the graphic view in interactive planning:

- Hide an individual curveYou can remove single curves from the display for more clarity. You can then select the curves thatyou wish to display again.

- Connect two points on a curveYou can select two points on a curve that are not adjacent and join them with a straight line. Thesystem overwrites any points with the interpolated values.

- Draw a trend line between two points on a curveYou can select any two points on a curve and draw a trend line between them. The system takes thevalues of these points and all points between into account and calculates the trend line using linearregression. Seasonal effects are not taken into account. If you wish you can replace the curve withthe trend line.

- Smooth the effects of changing a point in the graphicIf you activate this function and enter a factor larger than 0, when you change a point in the graphic(by using drag & drop), the system automatically corrects the neighboring points so that the changesin the curve are less acute. The system uses an exponential smoothing as in forecasting, whereby thefactor corresponds to the alpha factor.

In all cases the system will not make any changes if the key figure involved has been defined asread-only.

______________________________________________________________SAP AG 58

SAP-System______________________________________________________________

1.1.6.11.2 Usability Changes in Interactive Planning

Use

In Release SCM 4.1 several changes have been made that improve user productivity:

User Settings

It is now possible to save a wide variety of settings user-specifically at planning book/data view level oradditionally at selection level.

For more details, see User Settings in Interactive Planning

Header Information

It is now possible to customize the header information (characteristic buttons for drill-down purposes).You can

- Specify the position of the header

- above the grid

- below it

- to the left

- to the right

- Specify the width of the header if it is positioned to the left or to the right of the grid

- Hide the Previous value/Next value buttons (arrow up/arrow down)

Drill-down

As of Release SCM 4.1 it is possible to select several characteristic values for a drill-down. This issimilar to the Multiple Key Figure function for key figure selection. It appears in the pull-down menu asDetails (Filter).

Navigation path

You can save the drill-down/show-dependent path user-specifically. These settings are then automaticallytransferred to the user-setings.

Fixing

It is now possible to fix several cells at once.

Sum/Mean Function

It is now possible to calculate the sum or mean of any number of selected cells using the context menu.

Performance

In Release SCM 4.1 the performance has been noticeably improved in the following areas:

- Reading time series data from liveCache

- Changing values

Further improvements have been made by enabling users to deactivate notes (see also user settings) and

______________________________________________________________SAP AG 59

SAP-System______________________________________________________________

when satrting interactive planning.

1.1.6.11.3 Interactive Planning (Enhanced)

Use

In SAP SCM 4.1, a number of changes have been made to interactive planning in Supply NetworkPlanning (SNP). The individual changes are detailed below.

New design of detail view

Previously, you were able to display, and sometimes change, order details, such as quantity, source ofsupply, and availability/demand date, in the detail view of interactive SNP planning. As of SAP SCM 4.1,this view has a new design. The standard arrangement of fields now changes for each different type oforder, that is, according to whether it is a planned order, a stock transfer, or a planned independentrequirement. You can also design the layout of the display yourself and hide or show certain fields. Inaddition, the detail view now has sorting, filter, and search options for your orders.

As of SAP SCM 4.1, you can also change the time and date of orders.

Saving a navigation path

Previously, you were not able to save navigations that you made in interactive planning using the DrillDown or Show Dependent Objects functions. Navigations were only temporary and expired once youexited interactive planning.

As of SAP SCM 4.1, you can save, delete, or temporarily deactivate a navigation for a specific selection.To do this, right-click Deactivate/Save/Delete Navigation Path in the top left cell of the planningtable.

The navigation saved for a selection is automatically executed when you make the selection. You canalso transport a navigation path with the corresponding selection to another system.

Data view selection check

Previously, the system did not check whether the selections you made in interactive planning producedsuitable results for the key figures defined in the data view. As of SAP SCM 4.1, the system produces anerror message if a selection does not fit the selected data view.

New option the shuffler for displaying output products

Previously, if you wanted the output products of a resource to be displayed in the capacity view, you had

______________________________________________________________SAP AG 60

SAP-System______________________________________________________________

to select Display Dependent Objects -> APO - PPM Name -> APO - Usage in the shuffler. As ofSAP SCM 4.1, the interim step has been removed and you can now select Display Dependent Objects-> APO - Usage directly.

Fixing of manually created orders

Previously, orders created manually in interactive SNP planning were fixed automatically. A fixed orderis an order that cannot be deleted or changed in the next SNP planning run (heuristic, optimization, orCapable-to-Match).

As of SAP SCM 4.1, you can specify that you do not want manually created orders to be fixedautomatically in the master data of a location product. To do this, set the No Fixing indicator on theSNP2 tab page (not set as default).

Changing orders for products with multiple sources of supply

Previously, you were able to create and change planned orders and stock transfers in the planneddistribution receipt, confirmed distribution demand, and planned production key figures of theplanning table. If several sources of supply were available for a location product in a period, you wereable to select them for creating and changing orders. However, you were not able to see which sources ofsupply were being used for the existing orders in that period. In addition, you were able to edit the ordersin the detail view, but only for the sources of supply with existing orders in that period.

As of SAP SCM 4.1, improvements have been made to the transparency of order processing. Existingorders can be displayed in the detail view with their sources of supply. You can now also create neworders for the various sources of supply by creating a new row in the detail view, entering the quantity,and selecting the source of supply. You can create multiple orders per source of supply.

This enhanced functionality applies for planned orders and for stock transfers.

You can also use a macro to specify that, when there are multiple sources of supply per location product,the corresponding row in the planning table is not ready for input. This is indicated by a green marker inthe row. You can then only edit the orders in the detail view. For more information, see SAP note704651.

Changing planned orders in the capacity view in conjunction with the "Display DependentObjects" function.

Previously, you were able to change planned orders in the Production Planned key figure if you hadselected a resource and chosen Display Dependent Objects -> PPM in the capacity view. As of SAPSCM 4.1, you can also change planned orders if you selected Display Dependent Objects -> Products.The functionality described above (under the heading, Changing orders for products with multiplesources of supply) also applies in this case.

Changing subcontracting SNP stock transfers

Previously, subcontracting SNP stock transfers could only be changed or deleted by the system in aplanning run. As of SAP SCM 4.1, you can also change these SNP stock transfers manually in interactiveSNP planning. Subcontracting SNP planned orders cannot be changed manually. Since they are alwaysconnected to an SNP stock transfer, the corresponding planned orders adjust automatically.

______________________________________________________________SAP AG 61

SAP-System______________________________________________________________

Distribution function in drill down view

As of SAP SCM 4.1, you can use the distribution function if you have executed a drill down. This wasnot possible before.

Pivot sorting of key figures

AS of SAP SCM 4.1, a second pivot sorting option is available in which the key figures are not displayedin the rows, but in the period columns.

1.1.6.12 SCM-APO-SNP-DPL Deployment

1.1.6.12.1 Assignment of Category Groups for ATD Receipt and ATD Issue(Enhanced)

Use

Previously, you have been able to specify which order categories contribute to increasing and reducingthe available-to-deploy quantity (ATD quantity). To do this, you defined a category group for both theATD receipt and ATD issue in the location master data.

As of SAP SCM 4.1, you can make this specification not just for location, but also for a product at alocation. This means you can also assign the category groups for the ATD receipt and issue in thelocation product master (on the SNP 2tab page). During deployment execution, the system first checkswhether the category group has been specified for the location product. If not, the system performschecks on the location level. If a category has not been defined for the location either, the system uses thedefault ATR (receipt) or ATI (issue) category group.

______________________________________________________________SAP AG 62

SAP-System______________________________________________________________


Use











1.1.6.12.3 Determination of the Means of Transport in the Deployment Heuristic(Changed)

Use

Previously, when creating deployment stock transfers during a deployment run in Supply NetworkPlanning (SNP), the system only checked the validity of the transportation lane and one of the means of

______________________________________________________________SAP AG 63

SAP-System______________________________________________________________

transport assigned to it on today's date. However, the system did not check whether the transportationlane and means of transport were valid in all other periods of the planning period. Neither did the systemtry to ensure that the means of transport for the SNP stock transfers created in the SNP run were also usedin deployment.

As of SAP SCM 4.1, the system checks the validity of transportation lanes and means of transport for theentire planning period. The system first determines all valid means of transport for each individual periodand target location. The system then decides which means of transport it will use to create the deploymentstock transfers. Generally, the system tries to use the SNP run as a basis and adopt the means of transportcreated there for the SNP stock transfers. If several means of transport are considered or no SNP stocktransfers are available in a period, the system selects the means of transport with the shortest move timefrom all valid means of transport. If no valid transportation lanes or means of transport are available, thesystem cannot create any deployment stock transfers.


Use


Forecast horizon





______________________________________________________________SAP AG 64

SAP-System______________________________________________________________






1.1.6.12.5 Rounding in Deployment (Changed)

Use

Previous situation

Previously, during the deployment run in Supply Network Planning(SNP), the system only performedrounding once it had created deployment stock transfers in a fair share situation. The system either getsthe rounding value from the lot size profile that you entered in the transportation lane, or from the settingsin the target location product master data. The system did not consider the maximum lot size.

Generally, it was assumed that rounding had already been executed in the previous SNP run. This,however, was not always the case. It also lead to errors, if another means of transport to the SNP runmeans of transport was used in the deployment run, since different lot sizes may be assigned to differentmeans of transport.

______________________________________________________________SAP AG 65

SAP-System______________________________________________________________

New situation

As of SAP SCM 4.1, you can define how you want rounding to be executed in the SNP planning profile(see Release Information). By default, deployment considers the rounding value and the maximum lotsize when creating deployment stock transfers. The system either gets these values from the lot sizeprofile that you entered in the transportation lane, or from the settings in the target location productmaster data. The target location product settings are considered by the system, if no lot size profile hasbeen specified in the transportation lane, or if the values are 0.

You can also specify that you only want the system to get the values from either the transportation lanelot size profile, or the target location product master data. You can also specify that you do not want thesystem to execute rounding in the deployment run at all.


As of SAP SCM 4.1, you can save the rounding options for deployment in an SNP planning profile underMaintain Global SNP Settings in SNP Customizing.

1.1.6.13 SCM-APO-SNP-TLB Transport Load Builder

1.1.6.13.1 Transport Load Builder (Enhanced)

Use

In SAP SCM 4.1, the Transport Load Builder (TLB) has been revised and enhanced in the SupplyNetwork Planning (SNP) area. The individual enhancements are detailed below.

Flexible definition of upper and lower parameter limits

Previously, you were able to define upper and lower limits for the standard parameters weight, volume,and pallet positions in the TLB profile. The lower limits were linked by an AND condition, and theupper limits by an OR condition.

As of SAP SCM 4.1, definition of upper and lower limits for the standard parameters is more flexible inthe TLB. You can assign relational operators (such as <, =, and >) and define more flexible links betweenparameter limits. You can also define customer-specific parameters using BAdIs.

Different loading methods

Previously, when building transport loads, the TLB tried to assign quantities of the same product to the

______________________________________________________________SAP AG 66

SAP-System______________________________________________________________

same shipment.

As of SAP SCM 4.1, you can choose between two different loading methods, which you define in thetransportation lane. For straight loading, the system groups together same products, or products in thesame loading group (set in the location product master). For load balancing, the system tries todistribute products evenly over all shipments (that is, all shipments should roughly be the same).

Shipment upsizing and downsizing

In TLB planning, there may be remaining quantities that are not within the valid parameter limits for ashipment. Previously, the system could move deployment stock transfers that are in the pull-in horizonforward to the current calculation date to avoid these remaining quantities.

As of SAP SCM 4.1, you can define other methods that the system can use to avoid remaining quantitiesin the SNP Customizing. In this way, you can also define shipment downsizing, whereby, taking days'supply into account, the system downsizes the quantity to be transported by prioritizing and reducingdemand in the current period. You can also specify, that you want the system to try and build validshipments without remaining quantities by only filling some shipments to the lower parameter limit.

Further changes

As of SAP SCM 4.1, TLB is no longer executed on the basis of days, and execution is based on theperiods defined in the planning buckets profile.

In addition, in planning, the TLB no longer uses shipment priorities that you assigned to deploymentstock transfers using the Prioritization of Deployment Stock Transfers function. However, you canstill use these transport priorities for manual transport load building in interactive TLB planning.


For customers who have not previously been using an SAP SCM system and are installing one for thefirst time, only the new TLB planning is available. If you are upgrading from a previous SAP SCMrelease, the previous TLB is activated, since the earlier BAdIs and user exists are no longer available dueto revision of the TLB.

A client-specific change from old to new TLB planning can be made at any time, even if you havealready started productive operation. To do this, execute the /SAPAPO/TLBPRF_TRANS report. Thesystem then converts the existing orders in the TLB profile to new TLB profile orders and assigns the linkrules between the parameters to the old rules accordingly. The system also assigns the new TLB profile tothe means of transport that were also assigned to the old profile. The pull-in horizon is no longer part ofthe new profile but is assigned to the means of transport in the transportation lane.

Note that, as of release SAP SCM 5.0, the old TLB planning will no longer be available.

For more information, see SAP note 707828.


You can define the new methods for managing TLB planning, such as shipment upsizing and downsizing,in the SNP Customizing under Basic Settings -> Make TLB Basic Settings. You define these settingsas a profile and activate one of the profiles, which then applies for all TLB planning runs. You can,

______________________________________________________________SAP AG 67

SAP-System______________________________________________________________

however, also overwrite the global profile by entering another profile in the planning run settings beforeexecution of TLB planning.

If you do not define and activate a profile in Customizing, one of the standard profiles provided by SAPis activated (DEFAULT profile).

You can also determine whether certain parameter fields are displayed in interactive TLB planning underBasic Settings -> Change Display of Parameters in Interactive TLB Planning.

See also

For more information, see Supply Network Planning -> Transport Load Building in the SAP Library.

1.1.6.14 SCM-APO-SNP-INC Product Interchangeability in SNP

1.1.6.14.1 Product Interchangeability in Supply Network Planning (Changed)

Use

In SAP SCM 4.1, some small changes have been made to product interchangeability in Supply NetworkPlanning (SNP).

Planning of all products of a supersession chain

Previously, for execution of the SNP heuristic and the SNP optimizer in the background, you could set anindicator to determine that you wanted the system to plan all products of a supersession chain. However,if you executed the SNP heuristic in interactive SNP planning, you were not able to set this indicator.

As of SAP SCM 4.1, if you execute the SNP heuristic or the SNP optimizer interactively, the systemautomatically plans all products in a supersession chain in the correct order. This ensures that theplanning results are consistent within the supply chain.

Display of invalid stock on hand in interactive planning

As of SAP SCM 4.1, in interactive SNP planning, the Stock on Hand key figure is highlighted in colorfor the time period in which the stock of a product is invalid and can, therefore, no longer be used.

Display of predecessor and successor products in the detail view

As of SAP SCM 4.1, the predecessor and successor products are displayed in the detail view forinteractive SNP planning. The product you selected for planning or displaying data in the selection ishighlighted in color.

______________________________________________________________SAP AG 68

SAP-System______________________________________________________________

1.1.7 SCM-APO-SDM Multilevel Supply & Demand Matching

1.1.7.1 SCM-APO-SDM-CTM Capable-to-Match

1.1.7.1.1 Enhancements in Capable-to-Match (New)

Use

In SCM 4.1, the following enhancements for Capable-to-Match (CTM) have been made:

Settings in the Master Data for CTM

CTM now considers the following settings in the master data for in-house production:

- Infinite planning

- Assembly scrap

- Goods receipt processing time (GR processing time)Note: So that CTM considers the GR processing time, all the output products of a plan must use thesame receiving calendar and the same GR processing time.

Planning Area in CTM Profile

You can now specify a planning area for determining the SNP key figures in the CTM profile. CTMplanning then uses the planning area specified here instead of the planning area that you have specified inCTM Customizing.

Note: The system does not use the planning area for the determination of the ATP categories for ordersof type SNP.

Transport CTM Profile

You can now transport CTM profiles within an SCM release, for example, from a test system to aproduction system. For more information, see Transport CTM Profile.

New Business Add-Ins (BAdIs)

You can now use the following BAdIs:

- /SAPAPO/CTM_SOSINT Change In-House Production Sources of Supply

- /SAPAPO/CTM_SOSEXT Change External Procurement Sources of Supply

- /SAPAPO/CTM_RESOURCE Change Resources and Capacities

With these BAdIs, you can change the individual attributes of the corresponding objects that CTMrequires for planning. However, the changes are only valid temporarily for the current CTM planning run.

______________________________________________________________SAP AG 69

SAP-System______________________________________________________________

1.1.7.1.2 Transport CTM Profile (New)

Use

As of SCM 4.1, you can transport Capable-to-Match profiles (CTM profiles) within an SCM release, forexample, from a test system to a production system. You transport the CTM profiles manually using theTransport Organizer.

If you wanto to specify CTM profiles that should be transported, choose the Multilevel Supply andDemand Matching component, then Environment -> Transport CTM Profile.


The system transports the following data from the CTM profile:

- Settings in the CTM profile

- Variable planning parameter

- ATP categories for aggregation

- Criteria for demand prioritization

Effects on Data Transfer

CTM references other objects in the CTM profile, such as master data order selection, CTM time streamand categorization profile. The system simply transports the references to these objects and not theobjects themselves. Ensure, therefore, that the objects also exist in the target system.

The transport log will tell you which objects do not exist in the target system. You must create theseobjects manually in the target system.

1.1.7.1.3 Automatic Parallel Processing and Scheduling of Jobs

Use



______________________________________________________________SAP AG 70

SAP-System______________________________________________________________









- SNP Heuristic

- SNP Optimizer




- SCM Alert Monitor

- SCM Version Copy






See also

For more information on parallel processing profiles, see the F1 help for the individual fields and the SAP

______________________________________________________________SAP AG 71

SAP-System______________________________________________________________

Library documentation under Demand Planning -> Technical Aspects of Demand Planning ->Parallel Processing of Background Jobs.


Use













See also




______________________________________________________________SAP AG 72

SAP-System______________________________________________________________

1.1.8 SCM-APO-FCS Demand Planning

1.1.8.1 New and Changed Authorization Objects

Use

New authorization objects

The following authorization objects have been introduced:

- Forecast

- C_APO_PRPF- Forecast ProfilesWith this authorization object you can restrict access to forecast profiles. You can specifywhich profiles a user can change, display or use (execute).

- C_APO_TSID - Time SeriesWith this authorization object you can restrict access to time series (for example weightingprofiles, phase in/out profiles, trend dampening profiles, and distribution functions. You canspecify which time series a user can change or assign.

- Lifecycle Planning

- C_APO_LIKE - Like Profile With this authorization object you can restrict access to like profiles. You can specify whichlike profiles in which planning area a user can change, display, or assign.

- Promotion Planning

- C_APO_PROM - PromotionsWith this authorization object you can restrict access to promotions. You can specify whichpromotions a user can change or display.

- Master Data

- C_APO_DPPR - Product in Demand PlanningAs opposed to C_APO_PROD, which checks the authorization for the master data objectproduct, C_APO_DPPR checks against the values of the characteristic that you have defined asthe product in the master planning object structure. The location is not required in theauthorization check, which means that the same user can work independently of a location inDP and restricted to a location in SNP.In Release SCM 4.1 the authorization checks for C_APO_PROD have been replaced by checksfor C_APO_DPPR.You can thus specify which products in DP a user can change or display.

Business Information Warehouse (BW) Authorization Concept

As of SCM Release 4.1 it is possible to use the BW authorization concept together with characteristics.Note that this function is not available for CBF and DP-BOM planning areas. It also cannot be used inrealignment transaction.

In the standard system for performance reasons it cannot be used in the Maintain Characteristic ValueCombinations transaction. However a BAdI (/SAPAPO/SDP_AUTH_CHK) is available with which you

______________________________________________________________SAP AG 73

SAP-System______________________________________________________________

activate this function. For more details, see BAdI documentation .

Authorization Checks for Product and Location Splits

Authorization checks are now carried out when maintaining the corresponding settings in the transactionsProduct Split (/SAPAPO/MC7B) and Location Split (/SAPAPO/MC7A). The system uses theauthorization objects C_APO_DPPR, and C_APO_LOC to check authorization on the Demand Planningside. In product splits it also checks C_APO_PROD for authorization to change the product on the SNPside


If you have restricted access to data on a product basis by using authorization object C_APO_PROD, youmust maintain similar authorizations for authorization object C_APO_DPPR.

1.1.8.2 Function Improvements in Demand Planning (Enhanced)

Use

This release note describes small changes in the Demand Planning area that are not the subject of otherrelease notes.

Calculation of Proportional Factors

As of Release SCM 4.1 when calculating proportional factors you can

- Restrict the data processed by using a pre-defined selection

- Use parallel processing by assigning a parallel processing profile (see Automatic Parallel Processingand Scheduling of Jobs)

- Use the business add-in (BAdI) /SAPAPO/SDP_CALC_PRP to implement your own logic

Data Extraction to InfoCubes

In Release SCM4.1 you can create multiple data sources for one planning area.

If you are working with the Business Information Warehouse in the same system as your SCMinstallation, you can replicate the data source in the data extraction tool in planning area maintenance.

You can maintain the properties of data sources separately in the same transaction. Here you can assign aparallel processing profile (see Automatic Parallel Processing and Scheduling of Jobs) or the block sizefor the transfer of the data to BW.

DP-BOM with Product Data Structures

______________________________________________________________SAP AG 74

SAP-System______________________________________________________________

As of Release SCM 4.1 it is possible to use product data structures (PDS) instead of production processmodels . For more information, see Renaming: Runtime Object to Production Data Structure.

Distribution Function in Drill-Down View

As of Release SCM 4.1 it is possible to use the distribution function after a drill-down. This was notpossible in previous releases.

Manual Transport Connection

As of Release SCM 4.1 it is possible to transport background jobs independently or for a particularplanning area.

Key Figure Pivot Sorting

As of Release SCM 4.1 a second pivot sort option is available in which the key figures are displayed notin the rows but in columns under the period.

1.1.8.3 Activities Deleted from Demand Planning IMG (Deleted)

Use

Since they are concerned with master data maintenance on a regular basis, and as such are accessibleusing the SAP Easy Access menu, the following activities have been deleted from the ImplementationGuide (IMG) for Demand Planning:

Maintain Forecast Profile

Maintain Release Profile

Maintain Transfer Profile

The activitity Maintain Settings for IDOC Messages has also been deleted since this activity is notrequired in Demand Planning.

______________________________________________________________SAP AG 75

SAP-System______________________________________________________________


Use











- SNP Heuristic

- SNP Optimizer




- SCM Alert Monitor

- SCM Version Copy




______________________________________________________________SAP AG 76

SAP-System______________________________________________________________



See also


1.1.8.5 Release of Forecast Data from the InfoProvider

Use

As of Support Package 4 in SCM 4.1, you can release forecast data from an InfoProvider to SupplyNetwork Planning (SNP) or to an ERP system. The release is made directly to SNP or the ERP system; inother words, you do not have to load the data first into a planning area in Demand Planning and thus inthe time series liveCache.

You can release the forecast data from the following objects of the SAP Business Information Warehouse(BW):

- InfoCube

- RemoteProvider

- DataStore object

- MultiProvider

______________________________________________________________SAP AG 77

SAP-System______________________________________________________________

1.1.8.6 Release of Forecast Data from the InfoProvider

Use

As of Support Package 4 in SCM 4.1, you can release forecast data from an InfoProvider to SupplyNetwork Planning (SNP) or to an ERP system. The release is made directly to SNP or the ERP system; inother words, you do not have to load the data first into a planning area in Demand Planning and thus inthe time series liveCache.

You can release the forecast data from the following objects of the SAP Business Information Warehouse(BW):

- InfoCube

- RemoteProvider

- DataStore object

- MultiProvider

1.1.8.7 SCM-APO-FCS-BF Basic Functions

1.1.8.7.1 Changes and Enhancements for Planning Object Structures

Use

Creating Characteristic Value Combinations

This function has been changed in Release SCM 4.1. It is now possible to create several combinations atonce.

There are the following options:

- Create manuallyYou create new characteristic value combinations manually. You do this in a table. You can copyindividual entries as the basis for further entries.

- Load to worklistYou can load characteristic value combinations from various sources into the worklist. You can thenedit the data and generate new characteristic value combinations. The sources are:

- A master planning object structure

______________________________________________________________SAP AG 78

SAP-System______________________________________________________________

- An InfoProvider (for example, InfoCube, ODS object or InfoSet)

- FilesYou can upload characteristic value combinations from files on your PC or the applicationserver.

- Business add-in

- Generate directlyWith this option the characteristic value combinations are generated directly from the source (asabove).

- Generate in backgroundAs in Generate Directly, but as a background job.

Consistency Checks for Planning Object Structures

You can run consistency checks for

- · Master planning object structures

- · Aggregates

- · Characteristics

The checks that you can select are dependent on which type of object you select.

There are two modes

- AnalyzeThe selected check(s) are carried out. A results screen appears from which you can go to a moredetailed log.

- RepairIf the selected check permits (see online help for check), the system automatically tries to correctany errors it finds. As above a results screen appears from which you can go to a more detailed log.

See also

For more information on creating characteristic value combinations, see the F1 help and the SAP Libraryfor Demand Planning under Demand Planning Process -> Planning Area Administration ->Planning Object Structures -> Master Planning Object Structure -> Creation of CharacteristicValue Combinations.

For more information on consistency checks for planning object structure, see the context-sensitive help

______________________________________________________________SAP AG 79

SAP-System______________________________________________________________

in the transaction and AP Library for Demand Planning under Demand Planning Process -> PlanningArea Administration -> Planning Object Structures -> Consistency Checks for Planning ObjectStructures

1.1.8.8 SCM-APO-FCS-MAC MacroBuilder

1.1.8.8.1 Changes and Enhancements in Macro Processing

Use

The following small changes to macro processing have been made in Release SCM 4.1:

Search and Replace Function in MacroBuilder

In the MacroBuilder you can now search for a key figure or a formula (string) in an Operator/function.You can then replace it with a new entry.

Behavior of Macros after Change to Planning Area

- If the order of key figures in a planning book are changed, any macros remain active. The oneexception to this rule are macros that contain areas. In this case the relevant macros are deactivated.

- After deleting a key figure, which is used in at least one macro, the macros using that key figure, isdeactivated, the step containing the key figure is deleted, and an informative message is displayed.

- If a key figure is deleted that is not used in macros, the macros are completely unaffected.

- The behavior in respect to user exit macros remains unchanged as such macros are not activated andare always executed. The implementation of the user exit APODM005 controls the furtherprocessing. The user must check these macros manually when changing key figures.

1.1.8.9 SCM-APO-FCS-STF Statistical Forecast

1.1.8.9.1 Changes and Enhancements to Forecasting

Use

New Forecast Strategy - Median Method

This empirical method, which is used in strategy 36, determines the median of the basic and trendparameters, as well as the seasonal index if applicable. The system determines the difference between the

______________________________________________________________SAP AG 80

SAP-System______________________________________________________________

first and second values in the historical data, the second and third, and so on to the end of the data. It thensorts the values in ascending order and chooses the value that is exactly in the middle of the list, themedian value.

For more information see the SAP Library under Demand Planning Processs ->Definition/Redefinition of Forecast Models -> Creating a Master Forecast Profile -> UnivariateForecasting - > Forecast Strategies -> Median Method.

Outlier Correction

As of Release SCM 4.1 the outlier correction has been modified extensively. There are now two methodsof outlier correction:

- Ex-Post MethodIn this method the system uses the ex-post forecast to determine a tolerance lane. If a historicalvalue lies outside this tolerance lane, the system views it as an outlier and corrects it. As opposed toearlier releases, after the system has replaced a value it recalculates the ex-post forecast and theMAD measure of error. It then uses the new values for the succeeding historical values. InCustomizing you can decide whether the system corrects erroneous values to the ex-post value orthe nearest value of the tolerance lane.

- Median MethodIn this method the system uses the median forecast model to determine the ex-post forecast valuesfor the basic value, trend value, and the seasonal index. It can thus calculate an expected value foreach historical period. With the factor Sigma it then calculates a tolerance lane. Any values outsidethe tolerance lane are deemed to be outliers and are corrected. In Customizing you can decidewhether the system corrects erroneous values to the ex-post value or the nearest value of thetolerance lane.

Adaptive Forecasting

With this function the system attempts to find automatically the best forecast settings (model andparameters) for selections in background processing. For each selection in the job it determines the bestprofile and assigns it to the selection. In future jobs the forecast is carried out using this profile.Optionally you can set up the system so that if an error threshold is exceeded for a selection, the systemagain starts automatic model selection and finds the new optimal forecast settings for the selection.

This function is only available in background planning.


A Customizing activity is available for outlier correction. As well as specifying how the system correctsoutliers (see above) you can enter:

- How often the system recalculates the ex-post forecast and MAD. Per default the system does this ifthe two values after a corrected value are not corrected.

______________________________________________________________SAP AG 81

SAP-System______________________________________________________________

- How long the initial phase is. In this period the ex-post forecast and MAD are calculated for allvalues. The values form the basis for the outlier correction of the remaining values.

1.1.8.10 SCM-APO-FCS-INF Interactive Forecasting

1.1.8.10.1 Changes and Enhancements to the Graphic in Interactive Planning

Use

The following functions have been added to the graphic view in interactive planning:

- Hide an individual curveYou can remove single curves from the display for more clarity. You can then select the curves thatyou wish to display again.

- Connect two points on a curveYou can select two points on a curve that are not adjacent and join them with a straight line. Thesystem overwrites any points with the interpolated values.

- Draw a trend line between two points on a curveYou can select any two points on a curve and draw a trend line between them. The system takes thevalues of these points and all points between into account and calculates the trend line using linearregression. Seasonal effects are not taken into account. If you wish you can replace the curve withthe trend line.

- Smooth the effects of changing a point in the graphicIf you activate this function and enter a factor larger than 0, when you change a point in the graphic(by using drag & drop), the system automatically corrects the neighboring points so that the changesin the curve are less acute. The system uses an exponential smoothing as in forecasting, whereby thefactor corresponds to the alpha factor.

In all cases the system will not make any changes if the key figure involved has been defined asread-only.

______________________________________________________________SAP AG 82

SAP-System______________________________________________________________

1.1.8.10.2 Usability Changes in Interactive Planning

Use

In Release SCM 4.1 several changes have been made that improve user productivity:

User Settings

It is now possible to save a wide variety of settings user-specifically at planning book/data view level oradditionally at selection level.

For more details, see User Settings in Interactive Planning

Header Information

It is now possible to customize the header information (characteristic buttons for drill-down purposes).You can

- Specify the position of the header

- above the grid

- below it

- to the left

- to the right

- Specify the width of the header if it is positioned to the left or to the right of the grid

- Hide the Previous value/Next value buttons (arrow up/arrow down)

Drill-down

As of Release SCM 4.1 it is possible to select several characteristic values for a drill-down. This issimilar to the Multiple Key Figure function for key figure selection. It appears in the pull-down menu asDetails (Filter).

Navigation path

You can save the drill-down/show-dependent path user-specifically. These settings are then automaticallytransferred to the user-setings.

Fixing

It is now possible to fix several cells at once.

Sum/Mean Function

It is now possible to calculate the sum or mean of any number of selected cells using the context menu.

Performance

In Release SCM 4.1 the performance has been noticeably improved in the following areas:

- Reading time series data from liveCache

- Changing values

Further improvements have been made by enabling users to deactivate notes (see also user settings) and

______________________________________________________________SAP AG 83

SAP-System______________________________________________________________

when satrting interactive planning.

1.1.8.11 SCM-APO-FCS-PRP Promotion Planning

1.1.8.11.1 Changes and Enhancements to Promotion Planning

Use

Usability Changes

The user interaction in promotion planning has been adapted to be the same as that in interactive planningas far as possible. It particular this means:

- You can display or hide the sum column for all rows in the table.

- You can display or hide the unit of measure column or all rows in the table. You can also change theunit of measure if this is possible for the product involved.

- You can change the description of the periods, for instance between M01.2005, 01/01/2005 or01/31/2005.

- You can calculate the sum or average of a series of selected adjacent cells.

- You can switch rows and columns.

- You can use pivot sorting. (Pivot sorting for key figures is not available for promotion planning.)

- The export function is identical to that in interactive planning.

- You can specify how characteristic values are displayed: the technical name or the description.

- When selecting promotions in either interactive planning or batch processing, you can use thefollowing as selection criteria:

- Author

- Promotion base

- Promotion key figure

- Periodicity

- Promotion status

- Promotion type

- Promotion attributes

Where a user changes these settings the changes are saved user-specifically.

______________________________________________________________SAP AG 84

SAP-System______________________________________________________________

Assignment of Characteristic Values to Promotions

In one operation you can assign all characteristic values to a promotion.

You first decide which characteristics are to be used in the promotion; the promotion level characteristicis assigned automatically. If you are using a promotion base, all of the characteristics must exist in thepromotion base.

You then assign characteristic values either by using an existing selection or by defining a selectionmanually.

It is also possible to specify whether the data from the baseline planning key figure is copied to thepromotion key figure when creating a newpromotion.

Copying Promotions

This function has been enhanced so that you can create several copies of one promotion in one action. Foreach new promotion you can define a different start date and change the attributes.

Promotion Management

This transaction is new in Release SCM 4.1. It offers you a wide range of functions for administratingpromotions. Many of these functions let you change or check several promotions at once. You can

- Activate or deactivate promotions

- Check the consistency of promotions and if necessary update the data

- Copy promotions without entering promotion planning

- Change the characteristic values that have been assigned to a promotion without entering promotionplanning

- Delete promotions without entering promotion planning

- Display overlapping promotions

A log is kept for some of these functions.

1.1.8.12 SCM-APO-FCS-CHS Characteristics-Based Forecasting

1.1.8.12.1 Changes and Enhancements to Characteristics-Based Forecasting

Use

Master Data Maintenance

______________________________________________________________SAP AG 85

SAP-System______________________________________________________________

In Release SCM 4.1 the maintenance of the CBF master data has been combined in one transaction. Inthis integrated profile management you can

- Create and edit CBF tables

- Create and edit CBF profiles

- Assign CBF profiles to products and planning areas

- Make the setting for the new component-oriented logic

Component-Oriented Logic

This new development in Release SCM 4.1 implements a special disaggregation/aggregation logic inCBF. After an initial disaggregation to CBF characteristics it is possible to make changes at detail levelwithout these changes being added to the total on the aggregate level. However to ensure consistency thisdifference can be displayed in the planning table in a separate row.

This function is intended for use in over-planning scenarios. For instance in the computer industry eachPC normally has one hard disk drive. However in some circumstances it is possible to buy a PC withtwo. The number of PCs and the other components that are produced remain constant, but you want toensure that the correct number of hard disks are procured. This function enables this kind of planning.


Existing data is unaffected by these changes.

1.1.8.13 SCM-APO-FCS-CSP Forecast Consumption

1.1.8.13.1 Changes and Enhancements to Forecast Consumption andAssociated Tools

Use

QRFC/Background Consumption

In previous releases consumption of planned independent requirements by sales orders occursimmediately when the orders are transferred using the CIF from the OLTP system. However in a highvolume environment the processing time can be significant. This can lead to locking problems if severalusers or sales order items try to access the same location product simultaneously.

In SCM 4.1 there are two new methods of solving the problem:

Queued Remote Function Call (QRFC)

The system generates consumption tasks in queues for the incoming sales orders. Each pegging area has

______________________________________________________________SAP AG 86

SAP-System______________________________________________________________

its own queue. The system monitors the tasks, giving each task a status.

Background Processing

The consumption process is separated from the processing of the sales order. The consumption process isthen executed in a background job which you schedule to run regularly. This of course has thedisadvantage that the consumption data is not always up to date.

Improvements to Auxiliary Transactions

In the Generation of Forecast transaction the selections options have been enhanced. It is now possibleto use selection profiles from the SNP planning book to select the liveCache orders from which theforecast orders should be generated. Similarly you can restrict the period of time over which ordersshould be selected. You can now specify whether the open quantity or the original planned quantity is tobe copied to the forecast.

The selection options for the Adjustment of Requirements transaction have been enhanced similarly.

Time Series for Consumption Quantities from Sales Orders

As of Release SCM 4.1 it is possible to use (ATP-)time series in liveCache to store the data from salesorders that is relevant for consumption. In scenarios where there is a large amount of sales order data thiscan lead to a significant improvement in performance.


To use time series for storing the quantity data from sales orders for consumption purposes, you shouldstart report program /SAPAPO/ATP_PLANVERSION_UPD (in the upgrade guide activity C5 -Customizing for Clients with Active TS) before liveCache is restarted. You should then check in versionmanagement (Advanced Planning and Optimization -> Master Data -> Planning VersionManagement -> Model and Version Management) that the two indicators Forecast Time SeriesUpdate and Update from ATP Time Series have been set. You can use transaction /SAPAPO/AC05 todisplay the time series for individual location products.


There is a new Customizing activity to set up QRFC/background consumption. (Advanced Planning andOptimization -> Demand Planning -> Basic Settings -> Consumption -> Set Consumption Type ). Hereyou decide which type of consumption you want to use.

______________________________________________________________SAP AG 87

SAP-System______________________________________________________________

1.1.9 SCM-APO-PPS Production Planning and Detailed Scheduling

1.1.9.1 Consistency Check for Product Variants (New)

Use



1.1.9.2 Configuration Check in the CIF Comparison/Reconciliation (New)

Use

Until now, the CIF comparison/reconciliation of transaction data (delta report) did not check theconfiguration data for orders.

Simple configuration check

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, the CIF comparison/reconciliation of transaction dataalso checks by default if an order refers to the same configuration data (simple configuration check). Thesystem does not, however, check if the contents of the configuration data agree. In the case ofcharacteristics-dependent planning (CDP), the simple configuration check merely checks whether aconfiguration exists for the order.

Extended configuration check

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, the selection screen for the CIFcomparison/reconciliation also offers the additional option Extended Configuration Check. If you setthis indicator, the delta report checks whether the contents of the configuration data (characteristic valueassignments) agree in SAP APO and SAP R/3. The extended configuration check can have a negativeeffect on performance. If you do not set the indicator Extended Configuration Check, the simpleconfiguration check is performed.

The simple and extended configuration checks apply to the following object types:

- Manufacturing orders

- Planned orders

______________________________________________________________SAP AG 88

SAP-System______________________________________________________________

- Purchase orders

- Purchase requisitions

- Sales orders

- Deliveries

- Sales scheduling agreements

1.1.9.3 Improved Master Data Integration for Subcontracting (Enhanced)

Use

If you work with subcontracting in SAP APO, planning for subcontracting occurs in both the destinationlocation (location type production plant) and in the source location (location type vendor orsubcontractor). The following master data must be available in the source location:

- Production process model (PPM) or production data structure (PDS)

- Master data for the finished product and all components

- Transportation lanes between source and destination location for the finished product and allcomponents

Until now, PPMs or PDS were only transferred to SAP APO using APO Core Interface (CIF) for thedestination location. Only PPMs were transferred for the source location, assuming that the relevantsetting had been made in the integration model. You had to create master data and transportation lanesmanually in SAP APO for the source location.

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, you can specify in the integration model that CIF alsotransfers PDS for the source location to SAP APO. SAP APO automatically creates the relevant productmaster data and transportation lanes between source and destination location in the source location, ifthese are not there.

The in-house production order created in SAP APO in the source location automatically receives theplanned delivery time from the R/3 vendor purchasing info record as the duration. If you change theplanned delivery time in the purchasing info record, CIF transfers the changed PDS to SAP APO with thenext change transfer.

To ensure that the PDS for source locations is transferred to SAP APO, create an integration model forPDS and in the additional selection screen choose Subcontracting as the PDS type.

You can use Business Add-In /SAPAPO/DM_SUBCO_MD to create master data that is required in SAPAPO in the source location but which is not available in SAP R/3 during the inbound processing of PDS.You can find this BAdI in the Implementation Guide under Integration of SAP APO and SAP R/3 ->

______________________________________________________________SAP AG 89

SAP-System______________________________________________________________

Application-Specific Settings and Enhancements -> Enhancements for Production DataStructures.

1.1.9.4 Changes to the Maintenance of Resources

Use

The maintenance of resources has been changed in SCM 4.1:

Changes to interface

The resources interface has been redesigned in SCM 4.1 to improve usability. Here, the followingmaintenance tab pages were removed:

- Planning parameters

- Standard capacity

The parameters that you previously maintained in these two tab pages were included in a new tab pagedepending on their use.

The following maintenance tab pages were added:

- Time-Cont.CapacityThis tab page contains the planning parameters that only affect the time-continuous capacity of aresource, such as the setup matrix, time buffer, and so on.

- PP/DS Bucket CapacityIn this tab page, you create the parameters for creating PP/DS buckets. (See above.)

- SNP Bucket Capacity (Only available for mixed resourses.)In this tab page, you define the parameters for creating SNP buckets.

The Planning Parameters section was added to the General Data tab page. Here, you create thegeneral planning parameters, such as the Finite Planning or the Finiteness Level.

Introduction of the PP/DS Capacity

The resource maintenance has been enhanced by the tab page PP/DS Bucket Capacity. Using this tabpage, you can define a PP/DS capacity as well as the time-continuous capacity for a resource that you usein PP/DS.

The PP/DS bucket capacity of a resource provides the basis for the bucket-oriented capacity check in theCTP process and in block planning. Until now, in block planning, you could already execute abucket-oriented capacity check using single-mixed resources. This is now possible for several resourcetypes. Moreover, you can now also use a single-mixed resource for SNP and for the bucket-oriented

______________________________________________________________SAP AG 90

SAP-System______________________________________________________________

capacity check at the same time.

You can define PP/DS buckets for the following types of resources:





A resource with PP/DS bucket capacity must have the following settings:

- You set the indicator Finite Planning in the General Data tab page.

- You maintain the data for the time-continuous available capacity in the Time-Cont.Capacity tabpage.

- You define the following parameters for creating the PP/DS bucket capacity in the PP/DS BucketCap. tab page:

- Bucket Definition

- Bucket Schema

- Bucket Factor

- Finite Capacity

- Using the Bucket Capacity function key, the system displays the capacity profiles for every bucket(for example, capacity in hours).

- Using the Check Plans function key, you can check whether the resource is used as the calendarand primary resource in the PPM or the PDS. This is essential before you can execute abucket-oriented capacity check for the resource. You can also carry out this resource check using themodel consistency check.


If you already use bucket-oriented block planning, you have to execute the XPRA/SAPAPO/XPRA_PPDSBUCKET when upgrading to SCM 4.1. Using this XPRA, the system convertsthe bucket definition of the resources planned in block planning to the new PP/DS bucket capacity.


Note that, as a result of the interface changes in the resource maintenance, existing batch input programsand CATTs may no longer be runable.


Customizing of the master data has been enhanced by the BAdI Change PP/DS Bucket.

See also

Release Information on Bucket-Oriented Capacity Check in the CTP Process

Release Information on Bucket-Oriented Block Planning

______________________________________________________________SAP AG 91

SAP-System______________________________________________________________

1.1.9.5 Stable Forward Scheduling (New)

Use

The PP/DS heuristic Stable Forward Scheduling can be used, in the short-term horizon, for explodingbacklogs, for correcting capacity overloads or for adjusting the production plan to a changed capacitysituation for the resources, as a result of resource downtimes, for example.

If you execute detailed scheduling in the medium-term horizon on a weekly basis using the PP/DSoptimizer, for example, you can use the stable forward scheduling heuristic to adjust the production plandaily in the short-term horizon.

By rescheduling the orders, the heuristic stable forward scheduling adjusts a given production planover several levels of production and on several finite resources to suit the new planning situation. In theprocess, the system tries to retain the sequence of the operations on the resources. The assignment of theoperations to the resources also remains unchanged. That is, changing to alternative resources is avoided.

You can use the heuristic interactively in the detailed scheduling planning board and in the background inthe production planning run. The heuristic is also suitable for processing a large volume of data in theproduction planning run.

1.1.9.6 Process Change: Generate Production Data Structures (PDS) from iPPEData (New/Changed)

Use



- New Process if Using Connected DIMP System:You create iPPE data in the DIMP system. You transfer the data using the Core Interface (CIF) tothe SAP APO system. The data are inactive here and cannot be used for planning. You generate aproduction data structure (PDS) from the production versions of the relevant master data. Duringgeneration, the system checks if the data are correct. If the data contains errors, no PDS isgenerated; the data retains its previous status and is available for planning. If the system has

______________________________________________________________SAP AG 92

SAP-System______________________________________________________________

successfully generated the production data structure, the changed data can be used for planning. Theprevious status of the data is no longer available.







See also






1.1.9.7 Bucket-Oriented Block Planning (Changed)

Use

The Block Planning with Buckets has been changed in SCM 4.1. Now, in block planning, you canexecute a bucket-oriented capacity check based on PP/DS buckets.

The advantage of a bucket-oriented capacity check in block planning as opposed to infinite planning isthat an operation can only be scheduled to a particular block if sufficient capacity is available for thisoperation. The advantage over the previous finite planning is that a maximum capacity load is achievedfor the resource by avoiding gaps. In the bucket-oriented capacity check, the system starts from the

______________________________________________________________SAP AG 93

SAP-System______________________________________________________________

desired date and proceeds in the planning direction to see whether sufficient bucket capacity is available.If there is, the system reserves it. An operation cannot be scheduled over several buckets. That is, theoperation must be completed by the end of the bucket at the latest.

Until now, you could only use single mixed resources for bucket-oriented block planning as it was onlypossible to create the buckets on the basis of SNP buckets. Now, using the new PP/DS bucketcapacity, you can also use multimixed resources, single activity- and multiactivity resources forbucket-oriented block planning.

As the buckets for block planning are no longer based on the SNP buckets, a resource used forbucket-oriented block planning can now also be used in SNP at the same time. However, SNP still doesnot observe any block planning.

Prerequisites


- Single activity resource

- Single mixed resource



- The resource to be checked should have the following settings:

- You have created the blocks in the Block Planning tab page.

- You have set the Finite Planning indicator in the General Data tab page.

- You have maintained the parameters for time-continuous capacity in the Time-Cont.Capacitytab page.

- You have maintained the following parameters for the PP/DS bucket capacity in the PP/DSBucket Cap. tab page:In the Bucket Definition field, you choose the setting From Block Planning.In the Finite Capacity field, you choose the setting Bucket Capacity.

- Using the function key Bucket Capacity, you can display the capacity for each bucket.

- The resource to be checked must be assigned as the primary resource to a PPM or to a PDS in themode of an activity and you must have set the indicator calendar resource.You can use the Check Plans function key in the resource maintenance to check whether thesesettings have been made for the resource in the PPM/PDS. The model consistency check alsocarries out the same check.

- If you use bucket-oreinted block planning along with the CTP check, use the standard strategyprofile SAP_BCTP or your own strategy profile with the same settings.


If you already use bucket-oriented block planning, you have to execute the general upgrade report/SAPAPO/OM_LC_UPGRADE_41 for the liveCache before upgrading to SCM 4.1. A CDPconsistency check has to be carried out for block planning. You do this using the report/SAPAPO/OM_CDP_41_PREP_CHECK. For all block planning resources, this report checks whetherthese resources are used as primary resources in PPMs and that the calendar resource indicator hasbeen set. The system records the PPMs for which a block planning resource is not used as the primary

______________________________________________________________SAP AG 94

SAP-System______________________________________________________________

resource and/or the calendar resource indicator is not set.

When upgrading to SCM 4.1, the XPRA /SAPAPO/XPRA_PPDSBUCKET is carried out. The systemuses this XPRA to convert the bucket definition of block planning resources to the new PP/DS bucketcapacity.

See also

Release Information on Changes in Resource Maintenance

Release Information on the Bucket-oriented Capacity Check in the CTP Process

1.1.9.8 Subassembly Planning in the CTP Process

Use

Until now, it was not technically possible to use the the planning strategy subassembly planning in theCTP process. From SCM 4.1, you can now also use this planning strategy in the CTP process to planimportant assembies.

In subassembly planning, you create planned independent requirements for important assemblies toexecute a planning run for these assemblies before any sales orders are received. Production is triggeredfor these planned independent requirements. On receipt of the sales orders for the finished product whichrequire these assemblies, the dependent requirements of the assembly consume the previously createdplanned independent requirements and use the receipt elements already created for the assembly by thesystem. If the dependent requirement quantity exceeds the planned independent requirement quantity, thesystem creates a new receipt element for the planning procedure Cover dependent requirementsimmediately or the system schedules the dependent requirement as far in the future as is necessary tofind a suitable receipt element for the planning procedure Manual with check.

The implementation of the ATP category ID (Temporary Reqmt Subassembly Planning) now ensuresthat dependent requirements created in a CTP check for the assembly do not immediately consume theplanned independent requirements. In the net requirements calculation executed in the CTP check on thebasis of the planning procedure Cover dependent requirements immediately or Manual with check,the unconsumed planned independent requirements are not taken into account. This guarantees a correctforward scheduling. This avoids inconsistencies if you terminate the CTP check before saving.

If you save the CTP check, the system converts the temporary ATP category ID to the permanentcategory of the dependent requirements AY. Then the system triggers the consumption of the plannedindependent requirements by the dependent requirements. In principle, the same procedure is executedfor a stock transfer. The "actual" catogory of the stock transfer requirement is BH. In this case, thecategory ID is also used temporarily for the stock transfer requirement during the CTP check. Whensaving this category is replaced by the category BH.

For a component/assembly that is planned using the planning procedure Manual with check or Coverdependent reqmts immediately, you should set the Consumption mode backward/forwardconsumption and you should enter 999 days backwards and 999 days forwards as the Consumptionperiod. This ensures that every dependent requirement can be consumed later.

______________________________________________________________SAP AG 95

SAP-System______________________________________________________________

1.1.9.9 Bucket-Oriented Capacity Check in the CTP Process (New)

Use

In SAP SCM 4.1, the CTP process has been enhanced by the bucket-oriented capacity check. This check,based on the PP/DS bucket capacity, is now the standard procedure in the CTP process from SCM 4.1which the system uses to execute the capacity availability check and the capacity reservation forimportant resources (bottleneck resources).

Up until SAP SCM 4.0, you could only execute a time-exact scheduling for the sales orders on the basisof the time-continuous capacity of a resource using the strategy Find gap. This process has thefollowing disadvantages:

- When scheduling on the basis of the time-continuous capacity of a resource, gaps of various sizesarise that cannot be used by other orders.

- When using sequence-dependent setup activities, the orders may be scheduled in an unsuitablesequence due to the random receipt of the orders. This means that too much capacity is wasted onsetup activities and the result is a poor utilization of capacity.

- Using the time-exact CTP check over several production levels is also problematic. The fragmentedloads of the resources increase with each level checked and cause an increase in the lead time of theorders. The delivery date calculated by the CTP check may lie so far in the future that it is no longerrealistic.

To avoid these disadvantages, in SAP SCM 4.1 the bucket-oriented capacity check has beenimplemented in PP/DS. The main aim of the bucket-oriented capacity check is the improvement of thecapacity load by avoiding a fragmented capacity load utilization. The system achieves this by checkingand reserving the available capacity per period (Bucket). A bucket can be one day or a week, forexample. Due to the period-oriented capacity check, the system can schedule many more orders as it triesto use up the capacity of a bucket completely (for example, one day of 8 hours).

Advantages of the Bucket-Oriented Capacity Check in the CTP Process

- The system calculates feasible delivery dates and creates the planned orders with a relatively highcapacity load utilization.

- Due to the simplified capacity check and scheduling process, the system can create the plannedorders very quickly in the CTP process. The sales employee can give binding confirmationsindependently of the production planner.

- Several resources can be scheduled finitely in a CTP check without the lead time increasingunnecessarily.

______________________________________________________________SAP AG 96

SAP-System______________________________________________________________

Prerequisites






- The resource to be checked must have the following settings:

- You have set the indicator Finite Scheduling in the tab page General Data.

- You have defined the parameters for the time-continuous capacity.

- In the tab page PP/DS Bucket Cap., you have maintained the parameters for the PP/DSbucket capacity:Bucket DefinitionBucket SchemaBucket FactorFinite Capacity

- Using the function key Bucket Capacity, you can display the capacity profiles, for example,capacity per bucket in hours.

- The resource to be checked must be assigned as the primary resource in a PPM or in a PDS andthe Calendar Resource indicator must be set.Using the Check Plans function key in the resource maintenance, you can check whether you havemade these settings for a certain resource. You can also carry out the same check using the modelconsistency check.

- For the CTP check, you use the Standard strategy profile SAP_BCTP or your own strategyprofile with the same settings.

Procedure of the Bucket-Oriented Capacity Check in the CTP Process

1. Create sales orderIn the CTP process, you execute an ATP check in SAP APO for the newly received sales order. Ifthe requested quantity of the product cannot be confirmed for the desired date, the system accessesproduction planning and detailed scheduling. The requirement is trasferred to PP/DS.

2. Create temporary planned ordersIn PP/DS, the system executes a source of supply determination, a planned order explosion andscheduling. When scheduling the planned order, the system starts from the desired date andschedules in a backwards direction. Depending on the lot size, the system creates temporaryplanned orders.

3. Execute bucket-oriented capacity checkThe system starts from the desired date of the order and checks in a backwards direction to seewhether sufficient bucket capacity is available for the operation. In this process, the system takesaccount of the constraints, such as, the relationships or desired date of the order, for example. Ifsufficient capacity is available in the required bucket, it is reserved for the operation. At the sametime, the operation is scheduled infinitely on the time-continuous capacity. Then the system cancalculate the availability date of the planned order and calculate a confirmation date.

______________________________________________________________SAP AG 97

SAP-System______________________________________________________________

If not enough bucket capacity is available for the desired date, the system searches in a backwardscheduling direction for free capacity. If this is not successful, the system switchs to a forwardscheduling direction to search for free capacity.

4. Save sales orderYou save the sales order. In SAP APO, the temporary planned order is replaced by a plannedorder that is assigned to the account of the sales order.

5. Execute detailed schedulingNo time-exact production plan is created in the bucket-oriented capacity check in the CTP process.That is, the operations of the orders may overlap on the resources.If you require a time-continuous production plan (with exact production dates), you then have toexecute detailed scheduling.

Limitations

- The bucket-finite capacity check is a rough capacity check. The resulting requirements andavailability dates are therefore only exact per bucket. The bucket-oriented capacity check does notcreate a finite production plan. If you want a finite production plan, you have to execute DetailedScheduling later.

- The sequence-dependent setup activities are only considered in the capacity check in the formof average setup times or capacity reductions. If the average setup duration lies below the setupduration calculated in the setup optimization, it is possible that the dates cannot be respected.

- You should not use the bucket-oriented capacity check in CTP if the capacity requirements of thesetup activities represent a high proportion of the total capacity requirements. In this case, blockplanning may provide the better alternative.


To execute the bucket-oriented capacity check, the standard strategy profile SAP_BCTP has beenadded in SCM 4.1. Check the strategy profile in the IMG activity Maintaining Strategy Profiles andcreate your own strategy profile with the same settings.

See also

Release Information: Enhancements to Resource Maintenance

Release Information: Bucket-Oriented Block Planning (Changed)

Consultant Note: xxxxxx

1.1.9.10 Fixed Pegging (Enhanced)

Use

The fixed pegging functions have been enhanced for release SAP SCM 4.1:

______________________________________________________________SAP AG 98

SAP-System______________________________________________________________

Until now, the system was not able to retain fixed pegging relationships after a document change in R/3.If, for example, you created fixed pegging relationships between a sales order and a planned order thisfixed pegging relationhip disappeared after converting the planned order into a production order.

In SAP SCM 4.1, the system now transfers the existing fixed pegging relationships from a precedingdocument (for example, a planned order) to the successor document (for example, a production order).This ensures that the fixed pegging relationships between the receipt and requirement elements remainintact in production planning and during production execution. Refer to note 698427 to see exactly whichdocument changes are supported.

These enhancements to fixed pegging provide the following advantages:

- Stable confirmationsUsing fixed pegging, the assignment of a sales order item to a receipt element remains stable.Moreover, the component assignments over multi-levels can be kept stable. That is, components thatare assigned to an order via fixed pegging cannot be consumed by other, competing orders. Thismeans that the confirmation date you gave your customer can be retained more easily.Note that you can take account of the scope of check and the checking horizon in the ATP/CTPcheck based on the fixed pegging relationships.

- Fixing the material flow for production planningUntil now, dynamic pegging caused unexpected results during detailed scheduling as theassignments between the receipt and requirement elements were recalculated in every process step.Using fixed pegging, the material flow remains more stable. This increases transparency and thequality of the planning result.

- Heuristics

- You can create fixed pegging relationships using the heuristic SAP_PP_019 for a single levelor for multi-levels starting from the finished product. You define the parameters that controlhow the system is to proceed when creating the fixed pegging relationships in the heuristicsettings in Customizing for PP/DS.

- You can delete fixed pegging relationships using the heuristic SAP_PP_011. You can useparameters to define exactly which fixed pegging relationships are to be deleted.

- Improved maintenance functions

- You can also create or delete fixed pegging relationships manually. For this purpose, theProduct View has been extended to include the Pegging Overview tab page. In this tab page,you can check already existing fixed pegging relationships or you can also create fixedpegging relationships manually. Here, it is also possible to assign partial quantities and tocreated fixed pegging relationships for these partial quantities.

- The Context of an Order has been enhanced by functions for manually maintaining fixedpegging. Now, you can manually fix dynamic pegging relationships that were created by thesystem at either single or multi-level or you can delete already fixed pegging relationships. Seealso: Manual Maintenance of Fixed Pegging Relationships in the Product View

Integration with R/3

You can use fixed pegging with retention of the fixed pegging relationships after document changesif you use SAP APO along with an R/3 System Release 4.6C or 4.70 and a PlugIn 2114.1.

Business process with fixed pegging

______________________________________________________________SAP AG 99

SAP-System______________________________________________________________

How the various functions of fixed pegging interact is explained using the following example processes:

Order Receipt with ATP Check (ATP Online)

Order Confirmation Without Online Confirmation (MRP Process)

Fixed Pegging as Basis for Detailed Scheduling

Fixed Pegging in the CPT Process

Integration-Based Limitations to Fixed Pegging

- Fixed pegging is not integrated in R/3. This means that assignments between requirement andreceipt elements made in R/3 are not created as fixed pegging relationships in SAP APO.

Example:You execute a batch determinination in R/3. This assignment does not automatically trigger a fixedpegging relationship in SAP APO.

There is no integration of R/3 order networks for the same reasons.

- On the other hand, a fixed pegging relationship you created in SAP APO between a requirement anda receipt element also does not trigger an assignment in R/3.

Example:You create a fixed pegging relationship between an order reservation and a batch stock in SAPAPO. This does not automatically lead to a batch assignment to the order reservation in R/3.

Process-Based Limitations to Fixed Pegging

- The shelf life process is not supported as the fixed pegging heuristics do not take account of anyshelf life data.

- The fixed pegging heuristics do not take account of the limited capacity of a container resource.

- The APO production backflush is not supported.

- The fixed pegging relationship between a planned independent requirement and a receipt element isnot transferred to the sales order during the consumption with sales orders.

- You can find more limitations including functional limitations in the note 704583.


All document types supported, with the exception of stocks and inspection lots, transport the informationon the preceding document during the data transfer from R/3 to SAP APO without you having to makeany extra settings in Customizing. For stocks and inspection lots, you have to make the following settingsin the R/3 System:

______________________________________________________________SAP AG 100

SAP-System______________________________________________________________

- In order for the preceding document information for stocks to be transferred along with the datatransfer from R/3 to SAP APO, you have to execute the IMG activity Activate Fixed Pegging forStocks in Customizing for R/3 by choosing the menu path Integration with Other mySAP.comComponents --> Advanced Planning and Optimization --> Application-Specific Settings andEnhancements --> Settings and Enhancements for Stocks.

- If you use inspection lots and you also want to transfer the preceding document information to SAPAPO, you have to execute the IMG activity Activate Fixed Pegging for Inspection Lots inCustomizing for R/3 by choosing the menu path Integration with Other mySAP.comComponents --> Advanced Planning and Optimization --> Application-Specific Settings andEnhancements for inspection lots.

The following IMG activities have been changed or are new in SAP APO:

- Maintain Global Parameters and DefaultsThe field Activate Fixed Pegging has been added to this IMG activity. Using the setting FixedPegging is Active, you ensure that the fixed pegging remains intact also after document changes.

- Maintain HeuristicsThe heuristic SAP_PP_019 for creating fixed pegging relationships and SAP_PP_011 for deletingfixed pegging relationships have been enhanced.

- Define Sort Profile and Define Special Sorting

- The following BAdIs have been added:

- Enhance Heuristics for Fixed Pegging

- Adjusting Fixed Pegging at Document Change

See also

Release Information for Manual Maintenance of Fixed Pegging Relationships in the Product View

1.1.9.11 Sequence-Dependent Setup Activities (Changed)

Use

For release SCM 4.0 (support paclage 04) the setup logic, that is, the procedure used by the system tocalculate the sequence-dependent setup activities was changed. The dispay of the sequence-dependentsetup activities in the detailed scheduling planning board was adjusted accordingly.

This new setup logic is delivered as standard from release SCM 4.1.

As opposed to the previous setup logic that was based on the start dates/times of the setup activities, thesequence of the operations on a resource is now determined by the start dates/times of the processingactivities. Using this sequence, the system uses the setup matrix to calculate the necessary setup activitieswith the corresponding duration. The system creates the setup activities with the calculated duration. Theadvantage of this procedure over the previous procedure is that the sequence of the operations no longerchanges - even if an operation received an earlier start date/time as a result of the setup. This is because itis the start date/time of the processing activities that is significant for the sequence of the operations. Thismeans that the planing situation remains stable.

The new setup logic is based on two principles:

______________________________________________________________SAP AG 101

SAP-System______________________________________________________________

The sequence of the operations is based on the start dates/times of the processing activities. The setupactivities only have an insignificant role in planning.

When rescheduling, the planning situation should be changed as little as possible. If, for example, thepredecessor of an operation is changed, if possible, the operation itself should not be rescheduled - onlythe setup time should be recalculated.

The display of the sequence-dependent setup activities in the detailed scheduling planning board hasbeen changed as follows:

- The sequence-dependent setup activities are displayed using a narrow bar.

- When moving an operation with a sequence-dependent setup activity, the phantom object is onlydetermined by the activity types, processing, teardown, and queue. The setup activity is nolonger taken into account.

- The display of the non-sequence-dependent setup activities remains unchanged.


The new setup logic is deliverd as standard with SCM 4.1. The previous setup logic has been deactivated.All new resources are created with the new setup logic. In the upgrade to SCM 4.1, all currectly existingresources are automatically converted to the new setup logic. Here, you have to pay attention to thefollowing:

- You have to adjust your already existing planning board profile in Customizing for PP/DS. See alsoNote 644295 .

- If you use customer-specific planning functions, such as customer heuristics, for example, youhave to adjust these to suit the new setup logic. The procedure is described in the note 690692.Using the changes described in the note, you can make sure that the sequence-dependent setupactivities no longer represents a date/time specification for detailed scheduling but only containsduration and dates/times from the processing activity. See also note 645719.


In Customizing for PP/DS, the following planning board profiles were changed to adjust the display ofthe setup activities to the new setup logic.

- SAP001

- SAP003

- SAP006

- SAP_PCM1

- SAP_REM

In these planning board profiles, the graphic objects for the standard settings of the operations, fordeallocated operations and for fixed operations were copied and changed as follows:

In the graphic element setup, the hight was increased from 300 to 200 to be able to display thesequence-dependent setup activities in the DS planning board using a small bar.

______________________________________________________________SAP AG 102

SAP-System______________________________________________________________

In the graphic element setup, the Fixing indicator was set so that the setup activity is no longer a partof the phantom object when moving an operation in the detailed scheduling planning board.

In the charts that display operations in the diagram section resource chart, operation chart, operationsnetwork display), the decision tables for graphic objects were changed so that the changed graphicobjects are used for an operation with a sequence-dependent setup activity.

Your existing planning board profiles have to be adjusted accordingly. For more information on theprocedure, refer to note 644295.

See also

- You can find detailed information on the new setup logic in the note 645719.

- For more information on determining setup times, refer to the SAP Library under SAP AdvancedPlanner and Optimizer (SAP APO)--> PP/DS Process --> Basic Functions --> DetailedScheduling --> Determine Sequence-Dependent Setup Activities.

1.1.9.12 Calculation of the Days' Supply (New)

Use

Until SAP APO 4.0 the days' supply was calculated taking into account the Maximum AllowedEarliness or Lateness for a Receipt Element from the location-dependent product master.To calculate the days' supply, the system determined the first requirement that could no longer becompletely covered, taking into account maximum allowed earliness or lateness. Requirements were alsoregarded as covered in the days' supply calculation if the receipt was too late and lay outside of the alertthreshold.

As of SAP SCM 4.1 the system uses the alert threshold for early receipts and the alert threshold fordelayed receipts from the location-dependent product master to calculate the days' supply.When calculating the days' supply the system now determines the first requirement whose receiptviolates the alert threshold for too early or too late receipts.Requirements are then only regarded as covered in the days' supply calculation if the receipt lies withinthe alert threshold. The result is that only early or late receipts that are not problematic from the planner'spoint of view are used to calculate the days' supply.


You can use the Business Add-In /SAPAPO/RRP_COVPARAM Time Parameters for Receipts in theDays' Supply Calculation to influence the way the system determines the days' supply.An example implementation, which can be used to recreate the previous system behavior (up to andincluding SAP APO 4.0), exists for this BAdI.

See also

______________________________________________________________SAP AG 103

SAP-System______________________________________________________________

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAPAPO) under Production Planning and Detailed Scheduling (PP/DS) -> PP/DS Process -> BasicFunctions -> Calculation of Days' Supply.

1.1.9.13 Inventory Alerts in PP/DS (New)

Use

As of SAP SCM 4.1 you can choose to be informed when the stock level exceeds or falls below thesafety or target stock levels by means of an alert.

You activate the following alerts in the Alert Monitor on the PP/DS tab page, under Inventory Alerts:

- Stock Fallen Below Safety Stock Level

- Stock Fallen Below Target Stock Level

- Stock Exceeds Target Stock Level

See also

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAPAPO) under Supply Chain Monitoring -> Alert Monitor -> Monitoring and Solving PlanningProblems Using the Alert Monitor -> Monitoring PP/DS Alerts and under Production Planning andDetailed Scheduling (PP/DS) -> PP/DS Process -> Basic Functions -> Safety and Target StockLevel Planning in PP/DS.

1.1.9.14 Target Stock Level in Production Planning and Detailed Scheduling(PP/DS) (New)

Use

As of SAP SCM 4.1 you can also use target stock level methods in PP/DS.

In heuristic-based procurement planning with the standard heuristic SAP_PP_002 (Planning StandardLots) the following statistical target stock level methods, which you set in the location-dependent productmaster, are observed:

- Target Days' Supply from Product Master ' '

- Target Stock Level Equals Maximum Stock Level + safety stock (4)

- Maximum of Maximum Stock Level/Target Days' Supply (5)

- Sum of Maximum Stock Level/Target Days' Supply (6)

______________________________________________________________SAP AG 104

SAP-System______________________________________________________________

- No Target Stock Level (7)

You can be informed by means of an alert when stock falls below or exceeds the target stock level.

See also

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAPAPO) under Production Planning and Detailed Scheduling (PP/DS) -> PP/DS Process -> BasicFunctions -> Safety and Target Stock Level Planning in PP/DS and the Release Note InventoryAlerts in PP/DS.

1.1.9.15 SCM-APO-PPS-PPT Product Planning Table

1.1.9.15.1 Alert when Mode Linkage of Activities is Violated in DetailedScheduli (New)

Use

As a rule, the mode linkage for activities, which is defined, for example, in the production process model(PPM), cannot be violated during the scheduling and rescheduling of activities. In other words, activitieswith a mode linkage, between which time relationships exist, cannot be scheduled to other modesindependently of one another.When the mode has been defined for an activity it is also defined for the linked activity to which a timerelationship exists.As a exception, mode linkage may nevertheless occur for activities that belong to different operations.

As of SAP SCM 4.1 you can be informed by means of a dynamic alert in the Alert Monitor if the modelinkage has been violated during planning.To enable this, you must select the following alerts in the alert profile on the PP/DS tab page:

- Mode linkage violated within an order (under Constraint Alerts Within Order)

- Mode linkage violated between orders (under Constraint Alerts - Cross-Order)

______________________________________________________________SAP AG 105

SAP-System______________________________________________________________

1.1.9.15.2 Alert when Non-Interruptible Activities are Interrupted During DetaileScheduling (New)

Use

During scheduling and rescheduling, activities are not, as a rule, interrupted, if this has been defined, forexample in the production process model (PPM) (Break not Allowed indicator).However, in exceptional cases, non-interruptible activities may still be interrupted during scheduling andrescheduling.

As of SAP SCM 4.1 you can be informed of this situation by means of a dynamic alert in the AlertMonitor.You must first select the alert Non-interruptible activity is interrupted by a break in the Alert Profileon the PP/DS tab page under Alerts for Activities of a Resource.

1.1.9.15.3 Alert when Synchronization is Violated in Detailed Scheduling (New)

Use

As a rule, the synchronization of activities, which is defined in the resource master data of multimixedresources and multiactivity resources, cannot be violated during the scheduling and rescheduling ofactivities. This means that the scheduled activities must match in terms of start date, duration and onefurther characteristic.Under certain circumstances this situation may nevertheles arise, for example, when changes are made inparallel modes.

As of SAP SCM 4.1 you can choose to be informed of this situation in the Alert Monitor by means of adynamic alert. You can also choose to be informed of start and end dates of time periods in whichactivities are not synchronized.To activate these alerts you must select the alert Activity violates synchronization for the resource inthe alert profile, on the PP/DS tab page, under Alerts for activities of a resource.

______________________________________________________________SAP AG 106

SAP-System______________________________________________________________

1.1.9.16 SCM-APO-PPS-DST Detailed Scheduling Planning Board


Use






Use



______________________________________________________________SAP AG 107

SAP-System______________________________________________________________


Use



1.1.9.16.4 Sequence-Dependent Setup Activities (Changed)

Use



As opposed to the previous setup logic that was based on the start dates/times of the setup activities, thesequence of the operations on a resource is now determined by the start dates/times of the processingactivities. Using this sequence, the system uses the setup matrix to calculate the necessary setup activitieswith the corresponding duration. The system creates the setup activities with the calculated duration. Theadvantage of this procedure over the previous procedure is that the sequence of the operations no longerchanges - even if an operation received an earlier start date/time as a result of the setup. This is because it

______________________________________________________________SAP AG 108

SAP-System______________________________________________________________

is the start date/time of the processing activities that is significant for the sequence of the operations. Thismeans that the planing situation remains stable.














- SAP001

- SAP003

- SAP006

- SAP_PCM1

- SAP_REM


______________________________________________________________SAP AG 109

SAP-System______________________________________________________________





See also



1.1.9.16.5 Simulation Versions (Enhanced)

Use

From SAP SCM 4.1, two new functions are available for processing the simulation version:

- Save asWhen planning in the DS planning board, it was possible to save changes to the simulation version.However, it was not possible to save this simulation version under a new name. It was only possibleto save the already existing simulation version under the same name.With the enhancements for SCM 4.1, you can now use the Save as function to save a simulationversion using a different name. You can also save a simulation version with an already existingname. The system then overwrites the old simulation version.

Note that this function is only possible if you work with the same planning version. Only then canyou overwrite an already existing simulation version.

- CopyIn the simulation version menu (transaction /sapapo/cdpss0), you can select and copy simulationversions and you can also save an existing simulation version under a different name. The systemchecks whether the name you proposed already exists and then saves the simulation version underthe new name.

Note:

If you have already copied a version of a simulation version to the planning version, the other simulationversions for the planning version are usually no longer suitable to be copied again to the planning version.

______________________________________________________________SAP AG 110

SAP-System______________________________________________________________

1.1.9.16.6 Improvements to the Usability of the Detailed Scheduling PlanningBoard (Enhanced)

Use

From SAP SCM 4.1, the following functions are available improving the usability of the detailedscheduling planning board:

Setup and production times of process orders in one row

In the resource views of the DS planning board, setup and production times are now displayed in one rowfor process orders. Setup and production times have been realized as one graphical element and are nowvisible in one row.

Enhanced search function

Unitl now, in the DS planning board, you could only search by order number. The search function hasbeen enhanced so that you can now also search using the product identifier, the product description (shorttext), setup group and setup key. In a dialog box you can choose a search criteria for the search and youcan also define a value area.

If several results were found for a particular search, the system first selects the object that lies closest inthe displayed horizon. Using the function Continue Search, the system selects the next object thatcorresponds to your search criteria.

New graphic display

In the graphic DS planning board, it is now also possible to display the PP/DS horizon and the PP/DSplanning time fence in graphic form. Here, the PP/DS horizon is displayed by a dark green line and thePP/DS planning time fince by an orange line.

Create orders using template

Using this new function, you can create planned orders using a template in the DS planning board. Youcan use planned orders and production orders as templates. Here, data such as the product, location,receipt and requirements quantity, start date/time, availability date/time, source of supply as well as thecharacteristics of the characteristics-dependent planning, and class and characteristics from R/3 fromconfigured products can be directly copied from the template. You can create up to 99 orders in one step.These orders are then created and scheduled by the system according to the strategy profile you selected.If necessary, dependent requirements are covered.

Note the following limitations:

- You cannot use this function for make-to-order production orders.

______________________________________________________________SAP AG 111

SAP-System______________________________________________________________

- If any activity has been deallocated for an original order, then all the activities of the new order arealso deallocated.

- If you use campaign planning, the campaign characteristics of the original order are not copied tothe newly created orders.

- You can only create orders if the production process model (PPM) of the template is valid. If, forexample, a date or a quantity is invalid, it is not possible to create a copy.

- If you have defined that the dependent requirements for a product are to be covered and then use thisorder to create a new order, then the dependent requirements of the new orders are also covered.

1.1.9.17 SCM-APO-PPS-PVW Product View


Use





______________________________________________________________SAP AG 112

SAP-System______________________________________________________________


Use




Use



______________________________________________________________SAP AG 113

SAP-System______________________________________________________________

1.1.9.17.4 Manual Maintenance of Fixed Pegging Relationships (Enhanced)

Use

The product view has been enhanced for SCM 4.1 to create or delete manual fixed pegging relationships.Until now, you could only create and delete pegging relationships in the order processing view in thePegging tab page. Now, you can maintain pegging relationships directly in the product view - either inthe new Pegging Overview tab page or in the Context of an Order.

Pegging Overview

In the pegging overview you can check already existing fixed pegging relationships or you can also createfixed pegging relationships manually. Here, it is also possible to assign partial quantities and to createfixed pegging relationships for these partial quantities.

The pegging overview is provided as a tab page in the product view. However, you can also access itdirectly via the SAP APO menu by choosing Production Planning --> Interactive ProductionPlanning --> Pegging Overview. The pegging overview provides the following functions:

- Displaying Pegging RelationshipsThe pegging overview provides the planner with an overview of all pegging relationships that existfor a location product. The receipt and the requirement assigned to each other via pegging aredisplayed in one row. In the Pegging Type field, the system shows the type of the peggingrelationship.

- Creating Single-Level, Fixed Pegging RelationshipsIn the change mode, the fixed pegging quantity field is ready-for-input. By entering a quantity, youcan create the fixed pegging relationships manually. It is also possible to assign partial quantities.Using the icon @06@ Fix Complete Quantity, you can assign the actual pegging quantity in onestep by selecting a row. In this case, any existing dynamic pegging relationships are replaced byfixed pegging relationships. However, you can also select several rows therefore creating severalfixed pegging relationships.Note that the creation of fixed pegging relationships for a virtual safety stock is not possible. If youalso want to create fixed pegging relationships for safety stock elements, you have to go to theplanning version management and select the option 3 Consider safety stock requirements inthe liveCache in the Consider safety stock field.

- Deleting Fixed Pegging Relationships

- You can delete a fixed pegging relationship by deleting the quantity in the Fixed PeggingQuantity field.

- You can also delete a fixed pegging relationship between a receipt element and a requirementby selecting the appropriate row and choosing the icon @07@.

- Displaying Planning SegmentsAs opposed to the Elements tab page, in which all existing planning segments of a location productare displayed, the system can only display one planning segment in the pegging overview. If amake-to-stock segment exists, the system displays it. The other planning segments can only beselected in the overview tree.

______________________________________________________________SAP AG 114

SAP-System______________________________________________________________

- Selecting LayoutsTwo standard layouts are provided:

- SAP standard variant for receipts (elements sorted according to receipt elements)

- SAP standard variant for requirements (elements sorted according to requirements)

- Show additional columnsYou can show two additional columns by selecting Layout --> Change Layout:Autom.Fixed Pegging QtyMissing Qty for Reqmts(Variant Receipts)/ Excess for Receipts (Variant Reqmts)

- Alternative Reqmts/ReceiptsYou can use this function key to show all the alternatives that have not yet been assigned via fixedpegging. However, this is only possible for make-to-stock production.

Context of an Order

The Context of an Order has also been enhanced with functions for manually maintaining fixedpegging. Until now, you could only display the pegging structure for an order using the context.

You can access the context for an order by selecting a row in the Elements tab page and choosing theicon @3A@, for example.

The context has been enhanced by the requirement element column. For every receipt element of thepegging structure, the system displays the requirement element that was assigned via pegging.

Now, you can create or delete single or multilevel pegging relationships directly for an order. Theprerequisite for creating a fixed pegging relationship between a receipt and a requirement element is thata dynamic pegging relationship already exists between the two elements. In this case, the D indicator isdisplayed in the Pegging Type column.

- Creating Fixed Pegging RelationshipsYou can create fixed pegging relationships either using the icon @06@ or via the context menu(right-hand mouse key). You can also create multilevel fixed pegging relationships for a completepegging structure. Note here, that when creating the pegging relationships on the lower BOM levels,the system checks to see whether the authorization object C_APO_MALO is assigned to theactivities Display and Change. The system executes this check based on product and location. Thesystem also checks that the pegging relationship to be created also belongs to the selectedpropagation range.

- Deleting Fixed Pegging RelationshipsYou can either delete fixed pegging relationships using the icon @07@ or via the conext menu. Youcan also delete the fixed pegging relationships on multilevels for a complete pegging structure. Notehere that you require an appropriate authorization for deleting pegging relationships on the lowerBOM levels. The system also makes sure that the pegging relationship to be deleted belongs to theselected propagation range.

See also

______________________________________________________________SAP AG 115

SAP-System______________________________________________________________

Release Info for Fixed Pegging

1.1.9.17.5 Product View (Enhanced)

Use

From SAP SCM 4.1, the following functions are available in the product view:

Selection Rules

Selection rules are now available for the product view. You can use these selection rules to improve thetransparency of the product view by only displaying the elements you currently require, for example. Youcan hide certain ATP categories from the product view entirely.

In the selection rule, you define which ATP categories are to be displayed and you define settings for theselection interval. For the selection interval, you can define whether;

- you want an interval without limits

- the used can define the selection interval in the product view, or

- whether the interval can be defined in Customizing

You define the selection rules for the product view in Customizing for the order view under DefineSelection Rules for the Product View.

New tab page Pegging Overview

A new tab page, the Pegging Overview is available in the product view. For more information on thepegging overview, refer to the Release Information on Maintaining Fixed Pegging Manually in theProduct View.

1.1.9.18 SCM-APO-PPS-SCF Scheduling Functions

1.1.9.18.1 Stable Forward Scheduling (New)

Use

The PP/DS heuristic Stable Forward Scheduling can be used, in the short-term horizon, for explodingbacklogs, for correcting capacity overloads or for adjusting the production plan to a changed capacity

______________________________________________________________SAP AG 116

SAP-System______________________________________________________________

situation for the resources, as a result of resource downtimes, for example.

If you execute detailed scheduling in the medium-term horizon on a weekly basis using the PP/DSoptimizer, for example, you can use the stable forward scheduling heuristic to adjust the production plandaily in the short-term horizon.

By rescheduling the orders, the heuristic stable forward scheduling adjusts a given production planover several levels of production and on several finite resources to suit the new planning situation. In theprocess, the system tries to retain the sequence of the operations on the resources. The assignment of theoperations to the resources also remains unchanged. That is, changing to alternative resources is avoided.

You can use the heuristic interactively in the detailed scheduling planning board and in the background inthe production planning run. The heuristic is also suitable for processing a large volume of data in theproduction planning run.

1.1.9.18.2 Sequence-Dependent Setup Activities (Changed)

Use



As opposed to the previous setup logic that was based on the start dates/times of the setup activities, thesequence of the operations on a resource is now determined by the start dates/times of the processingactivities. Using this sequence, the system uses the setup matrix to calculate the necessary setup activitieswith the corresponding duration. The system creates the setup activities with the calculated duration. Theadvantage of this procedure over the previous procedure is that the sequence of the operations no longerchanges - even if an operation received an earlier start date/time as a result of the setup. This is because itis the start date/time of the processing activities that is significant for the sequence of the operations. Thismeans that the planing situation remains stable.





______________________________________________________________SAP AG 117

SAP-System______________________________________________________________










- SAP001

- SAP003

- SAP006

- SAP_PCM1

- SAP_REM






______________________________________________________________SAP AG 118

SAP-System______________________________________________________________

See also



1.1.9.18.3 Error-Tolerant Scheduling (New)

Use

When you are working in the detailed scheduling planning board, or with detailed scheduling heuristics,it is sometimes not possible to schedule all operations. Detailed scheduling is usually terminated whenthe system encounters an operation than cannot be scheduled. All the dates found by the system arediscarded and the operations are again scheduled to where they originally were. Therefore, either alloperations were scheduled or none were.

As of SAP SCM 4.1 you can also use error-tolerant scheduling in the detailed scheduling planningboard and when you use detailed scheduling heuristics. When you use error-tolerant scheduling, thesystem ignores constraints one at a time. The scheduling plans as many operations as possible and ignorespossible errors that occur during scheduling. Operations for which errors occur are scheduled withouttaking the constraints into account.

The scheduling tries to ignore the constraints in the following order:

- Infinite scheduling or deallocate

- Violate dynamic pegging relationships

- Violate fixed pegging relationships

- Violate external relationships

- Violate internal relationships

You should note the following constraint: If you want to use error-tolerant scheduling for detailedscheduling heuristics, it is not possible to carry out infinite scheduling. You can only do so if you useerror-tolerant scheduling in your strategy profile in the detailed scheduling planning board.

______________________________________________________________SAP AG 119

SAP-System______________________________________________________________

1.1.9.19 SCM-APO-PPS-FP Fixed Pegging

1.1.9.19.1 Fixed Pegging (Enhanced)

Use

The fixed pegging functions have been enhanced for release SAP SCM 4.1:

Until now, the system was not able to retain fixed pegging relationships after a document change in R/3.If, for example, you created fixed pegging relationships between a sales order and a planned order thisfixed pegging relationhip disappeared after converting the planned order into a production order.

In SAP SCM 4.1, the system now transfers the existing fixed pegging relationships from a precedingdocument (for example, a planned order) to the successor document (for example, a production order).This ensures that the fixed pegging relationships between the receipt and requirement elements remainintact in production planning and during production execution. Refer to note 698427 to see exactly whichdocument changes are supported.

These enhancements to fixed pegging provide the following advantages:

- Stable confirmationsUsing fixed pegging, the assignment of a sales order item to a receipt element remains stable.Moreover, the component assignments over multi-levels can be kept stable. That is, components thatare assigned to an order via fixed pegging cannot be consumed by other, competing orders. Thismeans that the confirmation date you gave your customer can be retained more easily.Note that you can take account of the scope of check and the checking horizon in the ATP/CTPcheck based on the fixed pegging relationships.

- Fixing the material flow for production planningUntil now, dynamic pegging caused unexpected results during detailed scheduling as theassignments between the receipt and requirement elements were recalculated in every process step.Using fixed pegging, the material flow remains more stable. This increases transparency and thequality of the planning result.

- Heuristics

- You can create fixed pegging relationships using the heuristic SAP_PP_019 for a single levelor for multi-levels starting from the finished product. You define the parameters that controlhow the system is to proceed when creating the fixed pegging relationships in the heuristicsettings in Customizing for PP/DS.

- You can delete fixed pegging relationships using the heuristic SAP_PP_011. You can useparameters to define exactly which fixed pegging relationships are to be deleted.

- Improved maintenance functions

- You can also create or delete fixed pegging relationships manually. For this purpose, theProduct View has been extended to include the Pegging Overview tab page. In this tab page,you can check already existing fixed pegging relationships or you can also create fixedpegging relationships manually. Here, it is also possible to assign partial quantities and tocreated fixed pegging relationships for these partial quantities.

- The Context of an Order has been enhanced by functions for manually maintaining fixed

______________________________________________________________SAP AG 120

SAP-System______________________________________________________________

pegging. Now, you can manually fix dynamic pegging relationships that were created by thesystem at either single or multi-level or you can delete already fixed pegging relationships. Seealso: Manual Maintenance of Fixed Pegging Relationships in the Product View

Integration with R/3

You can use fixed pegging with retention of the fixed pegging relationships after document changesif you use SAP APO along with an R/3 System Release 4.6C or 4.70 and a PlugIn 2114.1.

Business process with fixed pegging

How the various functions of fixed pegging interact is explained using the following example processes:

Order Receipt with ATP Check (ATP Online)

Order Confirmation Without Online Confirmation (MRP Process)

Fixed Pegging as Basis for Detailed Scheduling

Fixed Pegging in the CPT Process

Integration-Based Limitations to Fixed Pegging

- Fixed pegging is not integrated in R/3. This means that assignments between requirement andreceipt elements made in R/3 are not created as fixed pegging relationships in SAP APO.

Example:You execute a batch determinination in R/3. This assignment does not automatically trigger a fixedpegging relationship in SAP APO.

There is no integration of R/3 order networks for the same reasons.

- On the other hand, a fixed pegging relationship you created in SAP APO between a requirement anda receipt element also does not trigger an assignment in R/3.

Example:You create a fixed pegging relationship between an order reservation and a batch stock in SAPAPO. This does not automatically lead to a batch assignment to the order reservation in R/3.

Process-Based Limitations to Fixed Pegging

- The shelf life process is not supported as the fixed pegging heuristics do not take account of anyshelf life data.

- The fixed pegging heuristics do not take account of the limited capacity of a container resource.

- The APO production backflush is not supported.

- The fixed pegging relationship between a planned independent requirement and a receipt element isnot transferred to the sales order during the consumption with sales orders.

- You can find more limitations including functional limitations in the note 704583.


______________________________________________________________SAP AG 121

SAP-System______________________________________________________________

All document types supported, with the exception of stocks and inspection lots, transport the informationon the preceding document during the data transfer from R/3 to SAP APO without you having to makeany extra settings in Customizing. For stocks and inspection lots, you have to make the following settingsin the R/3 System:

- In order for the preceding document information for stocks to be transferred along with the datatransfer from R/3 to SAP APO, you have to execute the IMG activity Activate Fixed Pegging forStocks in Customizing for R/3 by choosing the menu path Integration with Other mySAP.comComponents --> Advanced Planning and Optimization --> Application-Specific Settings andEnhancements --> Settings and Enhancements for Stocks.

- If you use inspection lots and you also want to transfer the preceding document information to SAPAPO, you have to execute the IMG activity Activate Fixed Pegging for Inspection Lots inCustomizing for R/3 by choosing the menu path Integration with Other mySAP.comComponents --> Advanced Planning and Optimization --> Application-Specific Settings andEnhancements for inspection lots.

The following IMG activities have been changed or are new in SAP APO:

- Maintain Global Parameters and DefaultsThe field Activate Fixed Pegging has been added to this IMG activity. Using the setting FixedPegging is Active, you ensure that the fixed pegging remains intact also after document changes.

- Maintain HeuristicsThe heuristic SAP_PP_019 for creating fixed pegging relationships and SAP_PP_011 for deletingfixed pegging relationships have been enhanced.

- Define Sort Profile and Define Special Sorting

- The following BAdIs have been added:

- Enhance Heuristics for Fixed Pegging

- Adjusting Fixed Pegging at Document Change

See also

Release Information for Manual Maintenance of Fixed Pegging Relationships in the Product View

1.1.9.19.2 Manual Maintenance of Fixed Pegging Relationships (Enhanced)

Use

The product view has been enhanced for SCM 4.1 to create or delete manual fixed pegging relationships.Until now, you could only create and delete pegging relationships in the order processing view in thePegging tab page. Now, you can maintain pegging relationships directly in the product view - either inthe new Pegging Overview tab page or in the Context of an Order.

Pegging Overview

In the pegging overview you can check already existing fixed pegging relationships or you can also createfixed pegging relationships manually. Here, it is also possible to assign partial quantities and to createfixed pegging relationships for these partial quantities.

______________________________________________________________SAP AG 122

SAP-System______________________________________________________________

The pegging overview is provided as a tab page in the product view. However, you can also access itdirectly via the SAP APO menu by choosing Production Planning --> Interactive ProductionPlanning --> Pegging Overview. The pegging overview provides the following functions:

- Displaying Pegging RelationshipsThe pegging overview provides the planner with an overview of all pegging relationships that existfor a location product. The receipt and the requirement assigned to each other via pegging aredisplayed in one row. In the Pegging Type field, the system shows the type of the peggingrelationship.

- Creating Single-Level, Fixed Pegging RelationshipsIn the change mode, the fixed pegging quantity field is ready-for-input. By entering a quantity, youcan create the fixed pegging relationships manually. It is also possible to assign partial quantities.Using the icon @06@ Fix Complete Quantity, you can assign the actual pegging quantity in onestep by selecting a row. In this case, any existing dynamic pegging relationships are replaced byfixed pegging relationships. However, you can also select several rows therefore creating severalfixed pegging relationships.Note that the creation of fixed pegging relationships for a virtual safety stock is not possible. If youalso want to create fixed pegging relationships for safety stock elements, you have to go to theplanning version management and select the option 3 Consider safety stock requirements inthe liveCache in the Consider safety stock field.

- Deleting Fixed Pegging Relationships

- You can delete a fixed pegging relationship by deleting the quantity in the Fixed PeggingQuantity field.

- You can also delete a fixed pegging relationship between a receipt element and a requirementby selecting the appropriate row and choosing the icon @07@.

- Displaying Planning SegmentsAs opposed to the Elements tab page, in which all existing planning segments of a location productare displayed, the system can only display one planning segment in the pegging overview. If amake-to-stock segment exists, the system displays it. The other planning segments can only beselected in the overview tree.

- Selecting LayoutsTwo standard layouts are provided:

- SAP standard variant for receipts (elements sorted according to receipt elements)

- SAP standard variant for requirements (elements sorted according to requirements)

- Show additional columnsYou can show two additional columns by selecting Layout --> Change Layout:Autom.Fixed Pegging QtyMissing Qty for Reqmts(Variant Receipts)/ Excess for Receipts (Variant Reqmts)

- Alternative Reqmts/ReceiptsYou can use this function key to show all the alternatives that have not yet been assigned via fixedpegging. However, this is only possible for make-to-stock production.

Context of an Order

The Context of an Order has also been enhanced with functions for manually maintaining fixedpegging. Until now, you could only display the pegging structure for an order using the context.

______________________________________________________________SAP AG 123

SAP-System______________________________________________________________

You can access the context for an order by selecting a row in the Elements tab page and choosing theicon @3A@, for example.

The context has been enhanced by the requirement element column. For every receipt element of thepegging structure, the system displays the requirement element that was assigned via pegging.

Now, you can create or delete single or multilevel pegging relationships directly for an order. Theprerequisite for creating a fixed pegging relationship between a receipt and a requirement element is thata dynamic pegging relationship already exists between the two elements. In this case, the D indicator isdisplayed in the Pegging Type column.

- Creating Fixed Pegging RelationshipsYou can create fixed pegging relationships either using the icon @06@ or via the context menu(right-hand mouse key). You can also create multilevel fixed pegging relationships for a completepegging structure. Note here, that when creating the pegging relationships on the lower BOM levels,the system checks to see whether the authorization object C_APO_MALO is assigned to theactivities Display and Change. The system executes this check based on product and location. Thesystem also checks that the pegging relationship to be created also belongs to the selectedpropagation range.

- Deleting Fixed Pegging RelationshipsYou can either delete fixed pegging relationships using the icon @07@ or via the conext menu. Youcan also delete the fixed pegging relationships on multilevels for a complete pegging structure. Notehere that you require an appropriate authorization for deleting pegging relationships on the lowerBOM levels. The system also makes sure that the pegging relationship to be deleted belongs to theselected propagation range.

See also

Release Info for Fixed Pegging

1.1.9.20 SCM-APO-PPS-CDS Sales Scheduling Agreement Processing

1.1.9.20.1 Overview of New Features in Sales Scheduling AgreementProcessing

Use

As of SAP SCM 4.1 the following new features are available:

General

- Pegging-Relevant Quantity for Sales Scheduling Agreements (Changed)

______________________________________________________________SAP AG 124

SAP-System______________________________________________________________

- IDoc Inbound Processing and Default Profile Definable in the Application Menu (Changed)

Sales Scheduling Agreement

- Display of Additional Data in Master Data Maintenance for the Sales Scheduling Agreement (New)

- Mass Maintenance of Sales Scheduling Agreements (New)

Confirmation

- Under and Overconfirmation Alerts (New)

Business Add-In

- Business Add-In for Determining a Suitable Means of Transport (New)

1.1.9.20.2 Under- and Overconfirmation Alerts (New)

Use

As of SAP SCM 4.1 you can choose to be informed of under- and overconfirmation situations by meansof an alert.An underconfirmation situation occurs if the confirmed quantity of a customer requirement is less thanthe requested quantity.An overconfirmation situation occurs if the confirmed quantity of a customer requirement exceeds therequested quantity.


You can use the Business Add-In (BAdIs) Over/Underconfirmation Alerts/SAPAPO/AM_CNF_ALERT to influence how under- and overconfirmation alerts are determined.

See also

______________________________________________________________SAP AG 125

SAP-System______________________________________________________________

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAPAPO) under Supply Chain Monitoring -> Alert Monitor and Production Planning and DetailedScheduling (PP/DS) -> Collaborative Management of Delivery Schedules.

1.1.9.20.3 IDoc Inbound Processing and Default Profiles Definable in theApplication Menu (Changed)

Use

Until SAP APO 4.0 the activities IDoc Inbound Processing and Default Control Profile were accessedfrom Customizing for Advanced Planning and Optimization under Supply Chain Planning ->Delivery Schedule Processing for Sales Scheduling Agreements.

As of SAP SCM 4.1, these functions are no longer in Customizing, but can be accessed using newtransaction codes from the Easy Access Menu under Supply Chain Collaboration -> SalesScheduling Agreement Processing -> Current Settings:

-> IDoc Inbound Processing-> Define Inbound Release Processing /SAPAPO/CMDS_STPSR

(Previously: Set IDoc Inbound Processing /SAPAPO/CUST14)

-> Define Sold-To Party Determination /SAPAPO/CMDS_STPD

(Previously: Determination of Sold-To Party over EDI/SAPAPO/CUST15)

-> Default Profiles for Initial Data Transfer-> Maintain Default Control Profile /SAPAPO/CMDS_DEFCNTR

(Previously: Define Default Control Profiles/SAPAPO/CUST10)

-> Maintain Default Confirmation Profile /SAPAPO/CMDS_DEFCNF

(Previously: Define Default Confirmation Profiles/SAPAPO/CUST9)

1.1.9.20.4 Mass Maintenance of Sales Scheduling Agreements (New)

Use

As of SAP SCM 4.1 you can change any data relating to sales scheduling agreement items, provided that

______________________________________________________________SAP AG 126

SAP-System______________________________________________________________

it is data that can also be changed in Master Data Maintenance.You can activate or deactivate sales scheduling agreements and change the scheduling agreement profileand the confirmation profile.


Choose Advanced Planning and Optimization -> Master Data -> Mass Maintenance and select the objecttype Sales Scheduling Agreement.

See also

For more information see the release information on Mass Maintenance of Master Data and the SAPLibrary for SAP Advanced Planning and Optimization underSAP APO Master Data -> MassMaintenance.

1.1.9.20.5 Pegging-Relevant Quantity for Sales Scheduling Agreements(Changed)

Use

Until now, as a default, the confirmed quantity was pegging-relevant in Production Planning andDetailed Scheduling (PP/DS). In other words, it was relevant for the net requirements calculation and fordynamic pegging. As a result, both procurement proposals and under- or overcoverage alerts weregenerated on the basis of the confirmed quantity and not the requested quantity.

As of SAP APO 4.0 you were able to use the PP planning procedure for each location product to definefor sales orders whether the requested quantity or the confirmed quantity was pegging-relevant.

As of SAP SCM 4.1 you can use the PP planning procedure for each location product to define for salesscheduling agreements whether the requested quantity or the confirmed quantity of schedulingagreement items is pegging-relevant. If no planning procedure is defined in the location-dependentproduct master then the requested quantity is pegging-relevant as a default.


From a technical point of view, the change means that the system fills the pegging-relevant quantity field(REAL_QUANTITY) according to the planning procedure that you have defined for the location productin the location product master. Until now, this field was always filled with the confirmed quantity (minusthe quantity already delivered, if applicable).This change has the following consequences:

- As of SAP SCM 4.1 the REAL_QUANTITY field contains the confirmed or the requested quantityfor requirements relating to sales scheduling agreements, depending on the planning procedure.Therefore, all planning applications that use this field automatically now use either the confirmedquantity or the requested quantity.

______________________________________________________________SAP AG 127

SAP-System______________________________________________________________

- In the heuristics Days' Supply Check (SAP_CDS_F02) and Product Heuristic with Days' SupplyCheck (SAP_CDS_F03), in the feasibility check, you were, until now, able to define that the systemchecked the feasibility of the confirmed quantity instead of the requested quantity.In SAP SCM 4.1, the field Use Confirmed Quantity has been removed.The feasibility check is now always carried out on the basis of the requirement quantity.

- Until now, the standard heuristics based on the algorithm/SAPAPO/HEU_PLAN_STANDARDLOTS have always planned requirements relating to salesscheduling agreements on the basis of the requested quantity. Now, these requirements are eitherplanned on the basis of the requested quantity or the confirmed quantity, depending on the planningprocedure.The standard heuristic Planning Standard Lots Confirmed Qty SAP_CDS_F04 and the algorithm/SAPAPO/CDMS_PLAN_STANDARDLOTS for sales scheduling agreements, with which youwere able to carry out planning of standard lots on the basis of the confirmed quantity, are thereforeno longer required and have been deleted in SAP SCM 4.1.

During the upgrade to SAP SCM 4.1, requirements relating to sales scheduling agreements items areautomatically converted as part of the liveCache upgrade report. The requested quantity is then, as a rule,pegging relevant (exception, CTP). This corresponds to the system behavior that has been in place untilnow, because the heuristic for planning standard lots for sales scheduling agreements always carried outplanning on the basis of the requested quantities.For more information about the conversion rules see the documentation on the XPRA/SAPAPO/XPRA_REAL_QUANTITY.

After the upgrade, check whether you want to use the requested quantity or the confirmed quantity as thepegging-relevant quantity in the planning procedure, for any products which are procured usingscheduling agreements.If necessary, change the planning procedure or assign a planning procedure with a different definition ofthe pegging-relevant quantity to these location products.

- To change the pegging-relevant quantity for a planning procedure, use the function ConvertPegging-Relevant Quantity of Customer Requirements. You call this function via the transaction/SAPAPO/RRP_CONF_QTY. (The transaction is not in the SAP APO Menu). This function carriesout the conversion in the planning procedure. You cannot change the setting of the pegging-relevantquantity directly in Customizing for the planning procedure.

- To assign a different planning procedure, in which the pegging-relevant quantity is defineddifferently, to a location product, you must use the function Change Planning Procedure andConvert Customer Requirements. You call this function via the transaction/SAPAPO/RRP_SET_RRPT. (The transaction is not in the SAP APO Menu). You cannot assign aplanning procedure that has a definition of the pegging-relevant quantity that is different from thecurrent planning procedure to a location product directly in the location product master or in massmaintenance.

The system carries out the function and then converts the pegging-relevant quantity of the existingcustomer requirements according to the new setting.

See also

For more information, see the release notes Pegging-Relevant Quantity for Sales Orders and in the SAPLibrary under SAP Advanced Planner and Optimizer (SAP APO) -> Production Planning and Detailed

______________________________________________________________SAP AG 128

SAP-System______________________________________________________________

Scheduling (PP/DS) -> PP/DS Process, in the sections PP Planning Procedure and Pegging-RelevantQuantity.

1.1.9.20.6 Business Add-In for Determining a Suitable Means of Transport(New)

Use

As of SAP SCM 4.1 you can use the Business Add-In (BAdI)Prioritization of Sources of Supply andMeans of Transport (/SAPAPO/SOS_COST) to influence the way the means of transport for salesscheduling agreements is selected, so that the system determines a suitable means of transport.As a default, transport costs are given priority. If two means of transport carry the same transport costs,the means of transport that is fastest is given priority.


In Customizing for Advanced Planning and Optimization, choose Supply Chain Planning ->Delivery Schedule Processing for the Sales Scheduling Agreement ->Business Add-Ins(BAdIs)-> Means of Transport.

1.1.9.20.7 Additional Data in Master Data Maintenance for the Sales SchedulingAgreement (New)

Use

As of SAP SCM 4.1 you can see additional data about the sales scheduling agreement on the new tabpage Additional Data in Master Data Maintenance for the Sales Scheduling Agreement.

Additional data, such as sold-to party, customer material, partner description and unloading point, andcustomer-specific fields (/SAPAPO/CMDS_USR01-/SAPAPO/CMDS_USR05) are displayed on this tabpage.

______________________________________________________________SAP AG 129

SAP-System______________________________________________________________

1.1.9.21 SCM-APO-PPS-MMP Model Mix Planning

1.1.9.21.1 Model Mix Planning (Changed)

Use

For Release SCM 4.1, the usability of the restriction processing function has been improved by theaddition of new function keys for maintaining the restriction groups. A new function for copyingrestriction groups is now also available.

Note that you have to execute an XPRA if you already use the restriction maintenance functions withmodel mix planning/sequencing and you are ugrading to APO 4.1:

- XPRAFor the upgrade to SCM 4.1, you have to execute the XPRA /SAPAPO/RET_FILL_LOG_KEY.The database table /SAPAPO/RET_HEAD was expanded by the fields; planning version, locationand line. You use the XPRA to adjust the already existing restrictions in the system. Using theXPRA fills these fields with values.

- Interface changesNew function keys have been added to improve usability:Using the icon @3I@ you can switch back and forth between the display and change modes. In thechange mode, the following function keys are shown for maintaining the restriction groups:

- Create restriction group

- Change restriction group

- Copy restriction group

- Delete restriction group

- New functions for copying restriction groupsUsing this function, you can copy a restriction group and assign it to the same line. The restrictionsthat are assigned to the restriction group are also copied automatically.However, with this function, you can also leave name of the restriction group unchanged and assignthe restriction group to another line. Here, the restrictions assigned to the restriction gorup are againcopied automatically. You can achieve the same result if you use Drag & Drop to copy a restrictiongroup to another line. The system then copies the restriction group along with the restrictionsassigned to the restriction group.

If a restriction with the same name is already assigned to the line to which you want to copy therestriction group, it is not possible to copy the restriction group.Example:The restriction group RG1, that is assigned to Line1, has been assigned the restrictions R1 and R2.You want to copy the restriction group by assigning it to Line2. However, restriction R2 is alreadyassigned to Line2. For this reason, the system cannot copy the restriction group to Line2.

______________________________________________________________SAP AG 130

SAP-System______________________________________________________________

See also

Dokumentation zum XPRA /SAPAPO/RET_FILL_LOG_KEY

- Note that the format of the iPPE data has also changed for planning in SCM 4.1. Until now, youwere able to use the iPPE data in planning immediately after transferring it from the DIMP System.Now, after the data transfer, you have to generate a production data structure (PDS) from thetransferred iPPE data. You cannot execute model mix planning/sequencing until you havesuccessfully created a production data structure. For more information on generating productiondata structures, refer to the release information Process Change: Generating Production DataStructures (PDS) from iPPE Data and Production Planning with the Planning Matrix.

1.1.9.22 SCM-APO-PPS-RPM Planning Matrix

1.1.9.22.1 Production Planning Using the Planning Matrix (Changed)

Use

Due to the implementation of the Production Data Structure (PDS) the procedure for preparing the iPPEdata for planning with the planning matrix has changed. Until now, the planning matrix worked directlywith the data saved in the iPPE structures and that you transferred to SAP APO from the connected DIMPSystem. From SCM 4.1, the production data structure is now the basis for planning with the planningmatrix. Therefore, you have to generate a production data structure for every RPM product before youcan use the planning matrix.

The procedure for preparing the iPPE master data is as follows for the upgrade to SCM 4.1:

1. You maintain the iPPE data in the DIMP system, as before.

2. You transfer the iPPE data to SAP APO using the CIF, as before.

3. In SAP APO, you now have to create a production data structure (PDS) for the RPM product fromthe iPPE data. To do so, goto the SAP APO menu and choose Master Data --> Production DataStructure (PDS) --> Generate Production Data Structure from iPPE Data.The system displays the screen for creating the production data structure from the iPPE data.

4. Enter the data for the RPM product and choose the setting P for Production Planning andDetailed Scheduling (PP/DS) in the PDS Usage field.

5. Select the option Also regenerate current production data structures.You use this setting to define that SAP APO is to generate all production data structures for theselected planning versions.

6. Choose Execute.The system generates the production data structures.

7. Check the generation log. By double-clicking the error messages that are highlighted in red, you canaccess the message long texts. If necessary, correct the iPPE data in the DI System and transfer thechanges to SAP APO. Then you have to regenerate a production data structure for the RPM product.

______________________________________________________________SAP AG 131

SAP-System______________________________________________________________

8. After creating the PDS successfully, you can display it by choosing Master Data --> ProductionData Structure --> Display Production Data Structures.

When working, you execute a change transfer for changed iPPE data. After every change transfer youhave to regenerate the production data structure for the RPM product. Here, you choose the option, Onlygenerate changed production versions. This means you can ensure that the changes you made to youriPPE master data is also transferred to the production data structure. This is a prerequisite that has to befulfilled so that the planning version can use the current iPPE data for planning.


Check the following IMG activities in Customizing for APO under Master data --> Production DataStructure:

- Settings for Generating Production Data Structures (PDS)

- Message Control for Generating Production Data StructuresIn this IMG activity, you define the most important iPPE messages. You should first check the iPPEmessages and define which of the situations described in the message texts should lead to atermination of the generation of a PDS. You control this by defining the corresponding messagetype. For example:

- ErrorIn the case of an error, the error described in the message is so serious that the system is toterminate the generation of the PDS.

- WarningIn this instance the error described in the message should only trigger a warning message. Thegeneration of the PDS should continue in spite of the error.

See also

Release Information Generating Production Data Structures from iPPE Data

1.1.9.23 SCM-APO-PPS-PPC Product and Process Confirmation

1.1.9.23.1 Production Backlfush (Enhanced)

Use

From SAP SCM 4.1, the production backflush has been enhanced with the following functions:

______________________________________________________________SAP AG 132

SAP-System______________________________________________________________

- Archiving versions of the reporting point structuresTo improve performance, it makes sense to keep the database tables with the versions of thereporting point structures as small as possible. Therefore, you can now archive these versions of thereporting point structures to improve performance. Report /sapapo/ppc0_ord_rpv_delydetermines whether orders still exist for a reporting point structure. If this is not the case, you candelete the versions of the reporting point structures. A test mode is available for this report. Notethat to be able to use this report, the same functionality must also exist in the connected DI System.

- Improved background processing: New Acivity in the Implementation GuideUntil now, it was not possible to select a server group for the background process of the productionbackflush nor could you define that parallel background processing was to be used. From SAP SCM4.1, you can define the background processing more exactly and you can define the necessarycontrol parameters. A new IMG activity exists in the implementation guide of the productionbackflush for this which you can use to define the control parameters.

1.1.9.24 SCM-APO-PPS-HEU Heuristics

1.1.9.24.1 Pegging-Relevant Quantity for Sales Scheduling Agreements(Changed)

Use

Until now, as a default, the confirmed quantity was pegging-relevant in Production Planning andDetailed Scheduling (PP/DS). In other words, it was relevant for the net requirements calculation and fordynamic pegging. As a result, both procurement proposals and under- or overcoverage alerts weregenerated on the basis of the confirmed quantity and not the requested quantity.

As of SAP APO 4.0 you were able to use the PP planning procedure for each location product to definefor sales orders whether the requested quantity or the confirmed quantity was pegging-relevant.

As of SAP SCM 4.1 you can use the PP planning procedure for each location product to define for salesscheduling agreements whether the requested quantity or the confirmed quantity of schedulingagreement items is pegging-relevant. If no planning procedure is defined in the location-dependentproduct master then the requested quantity is pegging-relevant as a default.


From a technical point of view, the change means that the system fills the pegging-relevant quantity field(REAL_QUANTITY) according to the planning procedure that you have defined for the location product

______________________________________________________________SAP AG 133

SAP-System______________________________________________________________

in the location product master. Until now, this field was always filled with the confirmed quantity (minusthe quantity already delivered, if applicable).This change has the following consequences:

- As of SAP SCM 4.1 the REAL_QUANTITY field contains the confirmed or the requested quantityfor requirements relating to sales scheduling agreements, depending on the planning procedure.Therefore, all planning applications that use this field automatically now use either the confirmedquantity or the requested quantity.

- In the heuristics Days' Supply Check (SAP_CDS_F02) and Product Heuristic with Days' SupplyCheck (SAP_CDS_F03), in the feasibility check, you were, until now, able to define that the systemchecked the feasibility of the confirmed quantity instead of the requested quantity.In SAP SCM 4.1, the field Use Confirmed Quantity has been removed.The feasibility check is now always carried out on the basis of the requirement quantity.

- Until now, the standard heuristics based on the algorithm/SAPAPO/HEU_PLAN_STANDARDLOTS have always planned requirements relating to salesscheduling agreements on the basis of the requested quantity. Now, these requirements are eitherplanned on the basis of the requested quantity or the confirmed quantity, depending on the planningprocedure.The standard heuristic Planning Standard Lots Confirmed Qty SAP_CDS_F04 and the algorithm/SAPAPO/CDMS_PLAN_STANDARDLOTS for sales scheduling agreements, with which youwere able to carry out planning of standard lots on the basis of the confirmed quantity, are thereforeno longer required and have been deleted in SAP SCM 4.1.

During the upgrade to SAP SCM 4.1, requirements relating to sales scheduling agreements items areautomatically converted as part of the liveCache upgrade report. The requested quantity is then, as a rule,pegging relevant (exception, CTP). This corresponds to the system behavior that has been in place untilnow, because the heuristic for planning standard lots for sales scheduling agreements always carried outplanning on the basis of the requested quantities.For more information about the conversion rules see the documentation on the XPRA/SAPAPO/XPRA_REAL_QUANTITY.

After the upgrade, check whether you want to use the requested quantity or the confirmed quantity as thepegging-relevant quantity in the planning procedure, for any products which are procured usingscheduling agreements.If necessary, change the planning procedure or assign a planning procedure with a different definition ofthe pegging-relevant quantity to these location products.

- To change the pegging-relevant quantity for a planning procedure, use the function ConvertPegging-Relevant Quantity of Customer Requirements. You call this function via the transaction/SAPAPO/RRP_CONF_QTY. (The transaction is not in the SAP APO Menu). This function carriesout the conversion in the planning procedure. You cannot change the setting of the pegging-relevantquantity directly in Customizing for the planning procedure.

- To assign a different planning procedure, in which the pegging-relevant quantity is defineddifferently, to a location product, you must use the function Change Planning Procedure andConvert Customer Requirements. You call this function via the transaction/SAPAPO/RRP_SET_RRPT. (The transaction is not in the SAP APO Menu). You cannot assign aplanning procedure that has a definition of the pegging-relevant quantity that is different from thecurrent planning procedure to a location product directly in the location product master or in massmaintenance.

The system carries out the function and then converts the pegging-relevant quantity of the existing

______________________________________________________________SAP AG 134

SAP-System______________________________________________________________

customer requirements according to the new setting.

See also

For more information, see the release notes Pegging-Relevant Quantity for Sales Orders and in the SAPLibrary under SAP Advanced Planner and Optimizer (SAP APO) -> Production Planning and DetailedScheduling (PP/DS) -> PP/DS Process, in the sections PP Planning Procedure and Pegging-RelevantQuantity.

1.1.9.24.2 'Extended Block Maintenance' Heuristic (New)

Use

As of SAP SCM 4.1, you can use the Extended Block Maintenance heuristic(SAP_CDPBP_03) to create,delete and move blocks in a resource, or to change the length of these blocks.

1.1.9.25 SCM-APO-PPS-RSP Reservation Planning

1.1.9.25.1 Reservation Planning (New)

Use

From SAP SCM 4.1, a new procedure is available called Reservation Planning. Using ReservationPlanning, the system schedules sales orders for configurable products in production and calculates andconfirms the delivery dates at the same time.

Warning: The transactions of Reservation Planning and Customizing are not freely accessible. Thisapplication may only be implemented in customer projects with SAP participation that have SAP'sconsent. Before commencing the project, an evaluation of the project scope and the processes to becovered must be completed together with SAP. The reason for this is that extra integrationalprogramming is always required per customer in order to implement Reservation Planning. For moreinformation, refer to the note on the release limitations for SCM 4.1.

When calculating the confirmed delivery dates in Reservation Planning, the system takes account of anypreviously defined restrictions. A restriction is a quantity-oriented representation of productioncapacities based on the characteristics of the class system. Example: An automobile manufacturer canproduce a maximum of 60 vehicles per day with a sunroof as the supplier can only provide this number of

______________________________________________________________SAP AG 135

SAP-System______________________________________________________________

sunroofs per day. This situation can be represented as a restriction with the daily quantity 60 and thecharacteristic value assignment, Extras = "Sunroof".

This means that Reservation Planning is a planning procedure that simultaneously checks the availabilityof restriction capacities. The restriction capacities required by a sales order are "reserved".

Reservation Planning has the following objectives:

- In the short-term horizon: Fast and binding determination of delivery dates and an optimumproduction load.

- In the medium to long-term horizon: Production planned according to demand.

The following processes are available:

- Real-time positioningProcedure that can calculate the delivery date on creation of a sales order for a configurable product.Example: A customer orders a car at the car dealer. The dealer creates the sales order directly in themanufacturer's system which calculates the confirmed delivery date at the same time.

- RechedulingProcedure that can be used in the short and medium-term horizon to reschedule a large number ofsales orders for configurable products. Such a rescheduling may be necessary, for example, if in theabove-mentioned example, the supplier of sunroofs can increase his delivery quantity of sunroofsfrom 60 to 90 per day meaning that sales orders can be produced earlier.

- Daily package creationProcedure that can be used in the short-term horizon to calculate a daily order volume that can bereleased for production. The aim of this procedure is to load production to the maximum. Ifproduction is not loaded to full capacity with the already existing sales orders, you can use proposedorders to increase the production quantity. A proposed order is a planned sales order that iscompletely configured but which is produced to stock and not for a particular customer until acustomer can be assigned. The proposed orders must be created in a customer-specificimplementation or are loaded from an external source.

- Medium-term planningSimulative planning in the medium-term horizon with the aim of foreseeing the load of theproduction plants, checking the effects of changes to master data and delivering the basis forcalculating the component requirements.

Various functions are available for monitoring the processes, for evaluation purposes or for correcting theplanning results.

The following application limitations exist:

- The sales order items must always have the quantity 1.

- In real-time scheduling in Reservation Planning, the check of restriction capacities is an alternativeto the basic methods of the global ATP. Within one check instruction, it cannot be combined withthese basic methods.

- Technically speaking, it is possible to use Reservation Planning and Model Mix Planning for thesame scenario. However, the restrictions can be used either by Reservation Planning or by ModelMix Planning but not by both simultaneously. However, a complete process integration has to beevaluated before starting the project.

- Integration within SAP APO:

______________________________________________________________SAP AG 136

SAP-System______________________________________________________________

- The integration of the processes, daily package creation and medium-term planning with theother SAP APO functions in production planning and detailed scheduling must be evaluatedfor particular cases before the project start.

- No integration exists with Demand Planning in SAP APO.

- No integration exists with the Alert Monitor in SAP APO. However, alerts can be displayedusing evaluation tools in Reservation Planning.

- During rescheduling, the newly confirmed delivery dates are saved direclty in SAP APO in the salesorders although the orders themselves are not created in SAP APO but are transferred from an ordercreation system. This order creation system may be an SAP R/3 System or another system.Therefore, any changes to the sales orders must be transferred back to the order creation system. Todo this, the order creation system has to read change pointers in the SAP APO system. Here, extracustomer-specific programming is required.

1.1.10 SCM-APO-MSP Maintenance Planning

1.1.10.1 Easy Simulation in Maintenance and Service Processing (Enhanced)

Use

As of SAP SCM 4.1, the Easy Simulation tool in the Maintenance and Service Planning componentcan help you set up data for simulative planning in the planning board. This tool enables you to examineall aspects and options of a situation, and simulate the effect of a number of parameters before you run anew maintenance plan, or view the effects of changes to an existing plan.

In Easy Simulation, you can

- Create maintenance objects that are used only in simulative planning versions.This process allows you to simulate the effects on your capacity if additional maintenance objectsrequire maintenance work.The created maintenance objects are copies of existing maintenance objects. You can also usemaintenance objects without external reference that you created in the Maintenance Objecttransaction.

- Add existing service areas by:

- Selecting task lists on themaintenance object group level, check type level, or slot task listlevel.

- Adding modes to the used service area. You can branch to the Maintenance Task Listtransaction to add mode details; add mode details in Easy Simulation; or add no mode details.

______________________________________________________________SAP AG 137

SAP-System______________________________________________________________

If you do not add any mode details, SAP APO uses the existing mode with the highest priority.

After setting up the data in the Easy Simulation tool, you can view the simulative plan in themaintenance and service planning board. All of the functions in the maintenance and service planningboard can be used for your simulative plan. This means that you can perform automated planning orinteractive planning, but you cannot transfer the planning data to SAP R/3 DIMP.


You cannot transfer maintenance objects that have been created for simulative planning to SAP R/3DIMP. To use these maintenance objects in an active planning version, you have to do the following:

- In SAP APO, delete the copied maintenance objects and any modes created especially for thoseobjects.

- In SAP R/3, create the relevant functional locations and equipment.

- In SAP R/3, transfer these functional locations and equipment to SAP APO.

- In SAP APO, define the transferred objects in the Maintenance Object transaction in SAP APO


If you use maintenance objects without external reference in a simulative plan, you have to add thecounter data from SAP APO to a maintenance object. To do this, you have to set up the counter types thatcan be used in a performance profile in the activity Define Counter Types.

See also

Release Notes:

Maintenance and Service Planning

Maintenance and Service Planning Board Enhancements

Maintenance and Service Planning Master Data Enhancements

SAP Library:

SAP Advanced Planning and Optimization (SAP APO) -> Industry-Specific Enhancements ->SAP for Aerospace & Defense -> Maintenance and Service Planning (MSP).

1.1.10.2 Number Range Maintenance of Maintenance Items (Deleted)

Use

As of SCM 4.1, you cannot define external number ranges for maintenance items. The number ranges aredefined internally by the system. Therefore, the activity Define Number Ranges of MaintenanceItems has been deleted from the IMG.

______________________________________________________________SAP AG 138

SAP-System______________________________________________________________

1.1.10.3 Maintenance and Service Planning Board Enhancements (Enhanced)

Use

As of SAP SCM 4.1, the following enhancements have been made in the maintenance and serviceplanning board of the Maintenance and Service Planning component:

- One-time demandsYou can now create one-time demands in the planning board for additional maintenance work thatresult from modifications, Airworthiness Directives, service bulletins, engineering orders, and so on.You can also change or delete one-time demands from the planning board.Once created, a one-time demand is no different from other demand in the planning board.However, during planning, the one-time demand has low priority and is planned only after othermaintenance cycles are planned.You cannot transfer one-time demands to an external system.

- Order changesYou can now change the order duration and capacity requirements of the primary resources in slotsand check orders, and the capacity requirements of secondary resources in the planning board.

- Manual adjustment of slot durationYou can now adjust the duration of a slot in the planning board by drag and drop. This step enablesyou to free a service area to accommodate other checks or enlarge the slot used to accommodate apackaging check.

- Transfer of an active planning version to an external systemYou can now transfer an active planning version from within the planning board. The systembranches directly to the Process Change Pointers transaction.

- NavigatorYou can now sort the data in the navigator using a variety of criteria. The navigator can now bedisplayed in a separate window or completely hidden (this provides a larger chart area).

- User-defined functionsYou can now define and add your own functions to the planning board by using Business Add-In(BAdI) /SAPAPO/MSPUI_VIEW. Then, BAdI /SAPAPO/MSP_DMND_SRV processes thefunctions for work packages, and BAdI /SAPAPO/MSP_SLOT_SRV processes the functions forslots.


You cannot transfer one-time demands from SAP APO to an external system.

______________________________________________________________SAP AG 139

SAP-System______________________________________________________________


If you use maintenance objects without external reference in a plan, you have to add counter data fromSAP APO to a maintenance object. To do this, you have to define the counter types that can be used in aperformance profile in the activity Define Counter Types.

See also

Release Notes:


Easy Simulation in Maintenance and Service Planning

Maintenance and Service Planning Master Data Enhancements

SAP Library:

SAP Advanced Planning and Optimization (SAP APO) -> Industry-Specific Enhancements ->SAP for Aerospace & Defense -> Maintenance and Service Planning (MSP).

1.1.10.4 Master Data in Maintenance and Service Planning (Enhanced)

Use

As of SAP SCM 4.1, the following enhancements have been made to the master data transactions forMaintenance and Service Planning (MSP):

- Maintenance Task List (MTL)To facilitate processing, the following enhancements have been made to the user interface:

- Menu bar has been renamed Task List

- Task list header screen now contains only the Activities, Relationships, and Extras tabs. TheExtras tab is a combination of the previous Basic Data and Text tabs.

- On the task list header screen, headers and activities now have quick info

- Task list creation is now a three-step process for Header, Activity, and Mode.

- The Mode screen now contains an Extras tab, which is a combination of the former BasicData and Text tabs.

- On the Mode screen, modes, resources, and relationships now have quick info

- The activity type has been removed from the screens

- Maintenance ObjectThe following enhancements have been made to the maintenance object function:

- Maintenance objects without external referenceYou can now create maintenance objects that have no reference to a functional location orequipment in SAP R/3. This process allows you to create objects for use in simulativeplanning, but you cannot transfer these objects to SAP R/3.

______________________________________________________________SAP AG 140

SAP-System______________________________________________________________

- External reference indicatorThis indicator shows whether an existing maintenance object has been created with or withoutexternal reference.

- Average performance dataYou can now select a performance profile and counter types that are defined in SAP APO,either instead of using the data in SAP R/3, or for a maintenance object without externalreference.

- Cycle seriesYou can now create cycles series that are external cycle series with reference to an SAP R/3maintenance plan, or local cycle series without reference to an SAP R/3 maintenance plan.You can create only local cycle series for a maintenance object without reference.A new check interval indicator enables you to determine whether the maintenance object readsthe check interval data from SAP R/3 or from SAP APO. This is useful, for example, if a newcheck interval is not yet available in SAP R/3.

- Maintenance ProfileA check interval definition has been added to the maintenance profile to enable the scheduling ofmaintenance objects without reference.


You cannot transfer maintenance objects without external reference from SAP APO to SAP R/3.


If you use maintenance objects without external reference in a plan, you have to add counter data fromSAP APO to a maintenance object. To do this, you have to set up the counter types that can be used in aperformance profile in the activity Define Counter Types.

See also

Release Notes:


Maintenance and Service Planning Board Enhancements

Easy Simulation in Maintenance and Service Planning

SAP Library:

SAP Advanced Planning and Optimization (SAP APO) -> Industry-Specific Enhancements -> SAP forAerospace & Defense -> Maintenance and Service Planning (MSP).

______________________________________________________________SAP AG 141

SAP-System______________________________________________________________

1.1.11 SCM-APO-ATP Global Available-to-Promise

1.1.11.1 BAPI to Determine the Availability Situation (New)

Use

Up until now, a released BAPI (Business Application Programming Interface) did not exist forcustomer-specific applications or systems to execute an availability check in SAP APO.

As of SAP SCM 4.1 a new BAPI (function module: BAPI_APO_AVAILABILITY_CHECK) exists foryou to execute an availability check.


If you would like to use the new BAPI, you must maintain a requirements profile in the Customizing ofGlobal Available-to-Promise. The requirements profile contains the most important SAP-APO-internalcontrol parameters for the availability check.

See also

For more information, see the documentation of the BAPI.

1.1.11.2 SCM-APO-ATP-BF Basic Functions

1.1.11.2.1 Distribution Key for Lasting Orders in ATP Time Series (New)

Use

Up until now, orders that lasted a long time were booked into ATP time series at order start in the case ofissues, and at order finish in the case of receipts.

As of SAP SCM 4.1 each newly-produced quantity is directly booked into the ATP bucket in which,according to planning, the stock posting is expected. This enables to-the-minute confirmation, that is,sales orders can thus, in contrast to process orders that run for a long time, be confirmed at the point intime at which a sufficient receipt is expected.


The new function requires the system to determine which orders are directly or indirectly affected everytime a change is made to planning-relevant data. The new function leads to deteriorations in performanceand you should only activate it if you really need it. You can only activate or deactivate the functionglobally.

______________________________________________________________SAP AG 142

SAP-System______________________________________________________________


If you make the Customizing changes within an upgrade before you upgrade the SAP liveCache, adhereto the notes in the Component Upgrade Guide.

See also

For more information about activating bucket parameters, see SAP Advanced Planning and Optimization(SAP APO) -> Global Available-to-Promise (Global ATP) -> Settings for Global ATP -> General Settingsfor Global ATP -> Definition of Buckets for ATP Time Series -> Activation of Bucket Parameters forATP Time Series in the SAP Library.

1.1.11.2.2 Location-Dependent Buckets in the Availability Check (Enhanced)

Use

Up until now, you could only set bucket limits for ATP time series globally for all locations.

As of SAP SCM 4.1 you have the option of interpreting the limits in the time zone of the respectivelocation. In addition, it is possible to use several buckets per day.

This enhancement makes sense if you manage several plants in different time zones in SAP APO.


If you execute the Customizing changes within an upgrade before the upgrade of the SAP liveCache,adhere to the notes in the Component Upgrade Guide.

See also

For more information about activating ATP bucket parameters, see SAP Advanced Planning andOptimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Settings for Global ATP ->General Settings for Global ATP -> Definition of Buckets for ATP Time Series -> Activation of BucketParameters for ATP Time Series in the SAP Library.

1.1.11.3 SCM-APO-ATP-PRD ATP in Conjunction With Production

1.1.11.3.1 Subassembly Planning in the CTP Process

Use

Until now, it was not technically possible to use the the planning strategy subassembly planning in theCTP process. From SCM 4.1, you can now also use this planning strategy in the CTP process to planimportant assembies.

______________________________________________________________SAP AG 143

SAP-System______________________________________________________________

In subassembly planning, you create planned independent requirements for important assemblies toexecute a planning run for these assemblies before any sales orders are received. Production is triggeredfor these planned independent requirements. On receipt of the sales orders for the finished product whichrequire these assemblies, the dependent requirements of the assembly consume the previously createdplanned independent requirements and use the receipt elements already created for the assembly by thesystem. If the dependent requirement quantity exceeds the planned independent requirement quantity, thesystem creates a new receipt element for the planning procedure Cover dependent requirementsimmediately or the system schedules the dependent requirement as far in the future as is necessary tofind a suitable receipt element for the planning procedure Manual with check.

The implementation of the ATP category ID (Temporary Reqmt Subassembly Planning) now ensuresthat dependent requirements created in a CTP check for the assembly do not immediately consume theplanned independent requirements. In the net requirements calculation executed in the CTP check on thebasis of the planning procedure Cover dependent requirements immediately or Manual with check,the unconsumed planned independent requirements are not taken into account. This guarantees a correctforward scheduling. This avoids inconsistencies if you terminate the CTP check before saving.

If you save the CTP check, the system converts the temporary ATP category ID to the permanentcategory of the dependent requirements AY. Then the system triggers the consumption of the plannedindependent requirements by the dependent requirements. In principle, the same procedure is executedfor a stock transfer. The "actual" catogory of the stock transfer requirement is BH. In this case, thecategory ID is also used temporarily for the stock transfer requirement during the CTP check. Whensaving this category is replaced by the category BH.

For a component/assembly that is planned using the planning procedure Manual with check or Coverdependent reqmts immediately, you should set the Consumption mode backward/forwardconsumption and you should enter 999 days backwards and 999 days forwards as the Consumptionperiod. This ensures that every dependent requirement can be consumed later.

1.1.11.3.2 Bucket-Oriented Capacity Check in the CTP Process (New)

Use

In SAP SCM 4.1, the CTP process has been enhanced by the bucket-oriented capacity check. This check,based on the PP/DS bucket capacity, is now the standard procedure in the CTP process from SCM 4.1which the system uses to execute the capacity availability check and the capacity reservation forimportant resources (bottleneck resources).

Up until SAP SCM 4.0, you could only execute a time-exact scheduling for the sales orders on the basisof the time-continuous capacity of a resource using the strategy Find gap. This process has thefollowing disadvantages:

______________________________________________________________SAP AG 144

SAP-System______________________________________________________________

- When scheduling on the basis of the time-continuous capacity of a resource, gaps of various sizesarise that cannot be used by other orders.

- When using sequence-dependent setup activities, the orders may be scheduled in an unsuitablesequence due to the random receipt of the orders. This means that too much capacity is wasted onsetup activities and the result is a poor utilization of capacity.

- Using the time-exact CTP check over several production levels is also problematic. The fragmentedloads of the resources increase with each level checked and cause an increase in the lead time of theorders. The delivery date calculated by the CTP check may lie so far in the future that it is no longerrealistic.

To avoid these disadvantages, in SAP SCM 4.1 the bucket-oriented capacity check has beenimplemented in PP/DS. The main aim of the bucket-oriented capacity check is the improvement of thecapacity load by avoiding a fragmented capacity load utilization. The system achieves this by checkingand reserving the available capacity per period (Bucket). A bucket can be one day or a week, forexample. Due to the period-oriented capacity check, the system can schedule many more orders as it triesto use up the capacity of a bucket completely (for example, one day of 8 hours).

Advantages of the Bucket-Oriented Capacity Check in the CTP Process

- The system calculates feasible delivery dates and creates the planned orders with a relatively highcapacity load utilization.

- Due to the simplified capacity check and scheduling process, the system can create the plannedorders very quickly in the CTP process. The sales employee can give binding confirmationsindependently of the production planner.

- Several resources can be scheduled finitely in a CTP check without the lead time increasingunnecessarily.

Prerequisites






- The resource to be checked must have the following settings:

- You have set the indicator Finite Scheduling in the tab page General Data.

- You have defined the parameters for the time-continuous capacity.

- In the tab page PP/DS Bucket Cap., you have maintained the parameters for the PP/DSbucket capacity:Bucket DefinitionBucket SchemaBucket FactorFinite Capacity

- Using the function key Bucket Capacity, you can display the capacity profiles, for example,capacity per bucket in hours.

______________________________________________________________SAP AG 145

SAP-System______________________________________________________________

- The resource to be checked must be assigned as the primary resource in a PPM or in a PDS andthe Calendar Resource indicator must be set.Using the Check Plans function key in the resource maintenance, you can check whether you havemade these settings for a certain resource. You can also carry out the same check using the modelconsistency check.

- For the CTP check, you use the Standard strategy profile SAP_BCTP or your own strategyprofile with the same settings.

Procedure of the Bucket-Oriented Capacity Check in the CTP Process

1. Create sales orderIn the CTP process, you execute an ATP check in SAP APO for the newly received sales order. Ifthe requested quantity of the product cannot be confirmed for the desired date, the system accessesproduction planning and detailed scheduling. The requirement is trasferred to PP/DS.

2. Create temporary planned ordersIn PP/DS, the system executes a source of supply determination, a planned order explosion andscheduling. When scheduling the planned order, the system starts from the desired date andschedules in a backwards direction. Depending on the lot size, the system creates temporaryplanned orders.

3. Execute bucket-oriented capacity checkThe system starts from the desired date of the order and checks in a backwards direction to seewhether sufficient bucket capacity is available for the operation. In this process, the system takesaccount of the constraints, such as, the relationships or desired date of the order, for example. Ifsufficient capacity is available in the required bucket, it is reserved for the operation. At the sametime, the operation is scheduled infinitely on the time-continuous capacity. Then the system cancalculate the availability date of the planned order and calculate a confirmation date.If not enough bucket capacity is available for the desired date, the system searches in a backwardscheduling direction for free capacity. If this is not successful, the system switchs to a forwardscheduling direction to search for free capacity.

4. Save sales orderYou save the sales order. In SAP APO, the temporary planned order is replaced by a plannedorder that is assigned to the account of the sales order.

5. Execute detailed schedulingNo time-exact production plan is created in the bucket-oriented capacity check in the CTP process.That is, the operations of the orders may overlap on the resources.If you require a time-continuous production plan (with exact production dates), you then have toexecute detailed scheduling.

Limitations

- The bucket-finite capacity check is a rough capacity check. The resulting requirements andavailability dates are therefore only exact per bucket. The bucket-oriented capacity check does notcreate a finite production plan. If you want a finite production plan, you have to execute DetailedScheduling later.

- The sequence-dependent setup activities are only considered in the capacity check in the formof average setup times or capacity reductions. If the average setup duration lies below the setupduration calculated in the setup optimization, it is possible that the dates cannot be respected.

______________________________________________________________SAP AG 146

SAP-System______________________________________________________________

- You should not use the bucket-oriented capacity check in CTP if the capacity requirements of thesetup activities represent a high proportion of the total capacity requirements. In this case, blockplanning may provide the better alternative.


To execute the bucket-oriented capacity check, the standard strategy profile SAP_BCTP has beenadded in SCM 4.1. Check the strategy profile in the IMG activity Maintaining Strategy Profiles andcreate your own strategy profile with the same settings.

See also

Release Information: Enhancements to Resource Maintenance

Release Information: Bucket-Oriented Block Planning (Changed)

Consultant Note: xxxxxx

1.1.11.4 SCM-APO-ATP-SCH Time and Scheduling Functions

1.1.11.4.1 Scheduling Using Configurable Process Scheduling (New)

Use

Up until now, the scheduling schema within transportation and shipment scheduling was fixed, that is, thesystem specified which dates were calculated, how durations and working times were determined andhow the dates were connected with one another.

As of SAP SCM 4.1 you can use configurable process scheduling and thus your own scheduling schemaswithin transportation and shipment scheduling.


To use configurable process scheduling within transportation and shipment scheduling, you must, in theCustomizing of Global Available-to-Promise (Global ATP), assign a process alias to the item categoryused.

To do this, you must have defined a process alias in the Customizing of configurable process scheduling.

Moreover, an item category, for which a process alias can be found, must be transferred in the processthat uses configurable process scheduling. This is the case for sales order in SAP R/3, for example.

See also

______________________________________________________________SAP AG 147

SAP-System______________________________________________________________

For more information about creating an own scheduling schema, see SCM Basis -> Configurable ProcessScheduling -> Process Definition in the SAP Library.

Fore more information about using configurable process scheduling within transportation and shipmentscheduling, see SAP Advanced Planning and Optimization (SAP APO) -> Global Available-to-Promise(Global ATP) -> Transportation and Shipment Scheduling -> Scheduling Using Configurable ProcessScheduling in the SAP Library.

1.1.11.5 SCM-APO-ATP-EST Explanation & Simulation Tool

1.1.11.5.1 Explanation Facility of Global Available-to-Promise (Enhanced)

Use

Up until now, you had to first evaluate several subscreens before you received important informationabout the result of an advanced availability check in SAP APO (rules-based ATP check, for example). Itwas thus easy to overlook critical information. You identified the causes of missing availability orundesired substitutions of products/locations (due to missing stock, incomplete planning) when it was toolate, or not at all.

As of SAP SCM 4.1, the following enhancements exist:

- From the results overview, you can read the contribution of each basic method and advancedmethod to the overall result. In this way, you can immediately recognize the limiting method. In thecase of the multilevel ATP check (MATP) or Capable-to-Promise (CTP), the contributions ofproduct availability and production are explicitly shown by means of detailed functions withsymbols and confirmed quantities.

- As long as these basic methods were executed, you can call the product allocation display and theconsumption situation directly from the results overview.

- In the results overview, individual lines are available within the rules-based characteristicsubstitution to provide a better overview.

- The user-specific settings options in the results overview have been enhanced with the followingfunctions:

- Optional display of product/location or product and location names

- Suppression of substitutions that do not contribute to the result

______________________________________________________________SAP AG 148

SAP-System______________________________________________________________

1.1.11.6 SCM-APO-ATP-BOP Backorder Processing

1.1.11.6.1 Results Display of Backorder Processing (Enhanced)

Use

The results display of backorder processing (transaction /SAPAPO/BOP_RESULT) has been revised. Asof SAP SCM 4.1 , the following functions are available:

- In backorder processing, large data quantities, which take a long time to load and which are difficultto analyze in the results display, are processed.As of SAP SCM 4.1, you can speed up the display by filtering the data that you want to analyze. Todo so, a new pushbutton is available on the selection screen.

- It is often necessary that you know the product availability and product allocation situation forcertain order items that were processed in the backorder processing run. To display this information,additional menu options are now available in the results display.

- New status icons for limiting basic methods exist in the results display. They show which basicmethods (product availability check, product allocation, or forecast) have influenced the results ofthe availability check during backorder processing.

See also

For more information, see Global Available-to-Promise (Global ATP) -> Backorder Processing -> BatchBackorder Processing in the SAP Library.

1.1.12 SCM-APO-AMO Alert Monitor

1.1.12.1 Alert when Mode Linkage of Activities is Violated in Detailed Scheduli(New)

Use


______________________________________________________________SAP AG 149

SAP-System______________________________________________________________




1.1.12.2 Alert when Non-Interruptible Activities are Interrupted During DetaileScheduling (New)

Use



1.1.12.3 Alert when Synchronization is Violated in Detailed Scheduling (New)

Use

As a rule, the synchronization of activities, which is defined in the resource master data of multimixedresources and multiactivity resources, cannot be violated during the scheduling and rescheduling ofactivities. This means that the scheduled activities must match in terms of start date, duration and onefurther characteristic.Under certain circumstances this situation may nevertheles arise, for example, when changes are made in

______________________________________________________________SAP AG 150

SAP-System______________________________________________________________

parallel modes.



Use











- SNP Heuristic

- SNP Optimizer


In Release SCM 4.1 this Business Information Warehouse (BW) function has been extended to includeseveral SCM applications. It allows you to set up chains of background jobs. For instance in DemandPlanning you could program a chain that uploads data from a data source to an InfoCube, generate any

______________________________________________________________SAP AG 151

SAP-System______________________________________________________________

new characteristic value combinations, upload the data from the InfoCube to a planning area, carry out aforecast, and release the data to SNP. As well as process types from the listed components, it is possibleto include report programs and several BW functions in process chains.


- SCM Alert Monitor

- SCM Version Copy






See also


1.1.12.5 Under- and Overconfirmation Alerts (New)

Use

As of SAP SCM 4.1 you can choose to be informed of under- and overconfirmation situations by meansof an alert.An underconfirmation situation occurs if the confirmed quantity of a customer requirement is less thanthe requested quantity.An overconfirmation situation occurs if the confirmed quantity of a customer requirement exceeds therequested quantity.

______________________________________________________________SAP AG 152

SAP-System______________________________________________________________


You can use the Business Add-In (BAdIs) Over/Underconfirmation Alerts/SAPAPO/AM_CNF_ALERT to influence how under- and overconfirmation alerts are determined.

See also

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAPAPO) under Supply Chain Monitoring -> Alert Monitor and Production Planning and DetailedScheduling (PP/DS) -> Collaborative Management of Delivery Schedules.

1.1.12.6 Alert Determination in the Background (New)

Use

As of SAP SCM 4.1 you can perform alert determination in the background. This enables you to schedulealert determination by the system according to the selected overall alert profile at a specific point in time(for example, in the morning before the working day begins). This means that you gain a rapid overviewof the alert situation, without any waiting time or losses in performance.

To configure alert determination in the background, the following steps are necessary:

- You schedule report /SAPAPO/READ_ALERTS_BATCH as a background job.

- You adapt one of your assigned overall alert profiles (from your favorites) for alert determination inthe background. On the selection screen for the Alert Monitor, choose Goto -> AlertDetermination in the Background.

See also

For more information, see the SAP Library under SCM Basis -> Alert Monitor -> Alert Determination inthe Background.

For information on other changes in the Alert Monitor, see Changes in the Alert Monitor.

1.1.12.7 Changes in the Alert Monitor (Changed)

Use

Changes in the SAP Area Menu

The Alert Monitor is available in SAP Advanced Planning and Optimization (SAP APO), and also in

______________________________________________________________SAP AG 153

SAP-System______________________________________________________________

other components, such as in Inventory Collaboration Hub (ICH). As of SAP SCM 4.1, you can accessthe Alert Monitor in the SAP area menu under SCM Basis.

Changes in the SCM Implementation Guide

As of SAP SCM 4.1, you can make the Customizing settings for the Alert Monitor in the SCMImplementation Guide under SCM Basis.

Changes to the Selection Screen for the Alert Monitor

- Until now, the selection screen always contained the tab pages for all applications for which thesystem determined alerts. As of SAP SCM 4.1, you can use Activate/Deactivate Applications in theAlert Monitor to configure which applications are shown on the selection screen. This allows you toset up the selection screen to give you the best possible overview for your requirements.

- Until now, when you created an overall alert profile, you could only select individual alert types. Asof SAP SCM 4.1, the alert types are summarized under alert object types, and can be selected as agroup.

Changes to the Display Screen for the Alert Monitor

- The alerts determined are displayed in a tree structure. The highest hierarchy levels show the alertviews, the lower-levels show, for example, the alert object types and alert types that belong to thatspecific view. You can configure the hierarchical sequence of the tree according to yourrequirements. You do this on the User-Specific Display Hierarchies in the Alert Monitor screen.You can call this screen from the selection screen or the display screen by choosing Environment->User-Specific Display Hierarchies.

- To gain a rapid overview of the alert situation, you can choose to display the number of alerts with aspecific priority at each hierarchy level in the tree structure.

Adjusting an Overall Alert Profile for Alert Determination in the Background

For more information, see Alert Determination in the Background


The following new IMG activites are available:

- Acitvate/Deactivate Applications in Alert Monitor

- Define Additional Status in Alert Monitor

- Limit Additionally Defined Status to Specific Alert Object Types

1.1.12.8 Inventory Alerts in PP/DS (New)

Use

______________________________________________________________SAP AG 154

SAP-System______________________________________________________________

As of SAP SCM 4.1 you can choose to be informed when the stock level exceeds or falls below thesafety or target stock levels by means of an alert.

You activate the following alerts in the Alert Monitor on the PP/DS tab page, under Inventory Alerts:

- Stock Fallen Below Safety Stock Level

- Stock Fallen Below Target Stock Level

- Stock Exceeds Target Stock Level

See also

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAPAPO) under Supply Chain Monitoring -> Alert Monitor -> Monitoring and Solving PlanningProblems Using the Alert Monitor -> Monitoring PP/DS Alerts and under Production Planning andDetailed Scheduling (PP/DS) -> PP/DS Process -> Basic Functions -> Safety and Target StockLevel Planning in PP/DS.

1.1.13 SCM-APO-OPT Optimization

1.1.13.1 SCM-APO-OPT-SNP Supply Network Planning


Use







______________________________________________________________SAP AG 155

SAP-System______________________________________________________________






Use


Forecast horizon





______________________________________________________________SAP AG 156

SAP-System______________________________________________________________






1.1.13.1.3 SNP Priority Profile (New)

Use

Previously, the product and resource decomposition solution methods were available for optimization inSupply Network Planning (SNP). Decomposition methods enable you to reduce runtime and memoryrequirements.

For product and resource decomposition, the system combines both products and resources in partialproblems. These are then solved sequentially. Previously, the order in which the objects are combinedand planned was determined automatically by the system.

As of SAP SCM 4.1, you can determine this order yourself by assigning priorities to the products andresources in an SNP priority profile. In this way, you can specify that important products and resourcesare planned first, for instance.

______________________________________________________________SAP AG 157

SAP-System______________________________________________________________


You create the SNP priority profile in the current settings in SNP under Profiles -> Define PriorityProfiles and assign it to an SNP or deployment optimizer profile in Customizing or in the current settingsof SNP under Profiles -> Defined SNP Optimizer Profile or Define Deployment Optimizer Profile(on the Solution Methods tab page). If you do not define an SNP priority profile, the optimizerdetermines the sequence of objects as before.

1.1.13.1.4 SNP Optimizer Procedures for Fail-Safe Solution Determination (New)

Use

Previously, you have been able to specify a maximum runtime for the SNP optimzer. If the system couldnot find a solution for an optimization problem within this time, the optimization run was terminatedwithout result.

As of SAP SCM 4.1, you can chose how you want the SNP optimizer to proceed if it cannot find asolution within the specified runtime. First, you can enter a runtime extension. If the optimizer does notfind a solution at the end of the extended runtime, you have further options to chose from (such as,simplifying the problem internally in the system or ignoring a partial problem).


You can make these settings in the SNP optimizer profile on the Advanced Settings tab page. To dothis, select Define SNP Optimizer Profile in the Supply Network Planning Customizing.

1.1.13.1.5 Subcontracting (Enhanced)

Use

Previously, in Supply Network Planning (SNP), subcontracting processes were only supported by theSNP heuristic. As of SAP SCM 4.1, both processes, subcontracting with source location andsubcontracting with third-party provision of components are possible within optimization-basedplanning. The SNP optimizer supports the processes to the same extent as the SNP heuristic. One

______________________________________________________________SAP AG 158

SAP-System______________________________________________________________

restriction to note is that either the transportation capacity or the production capacity should be used as aconstraint for planning, not both.

In SAP SCM 4.1, improvements have also been made to the integration of master data using the APOCore Interface (CIF) with R/3. If you use the new production data structure (PDS) in SNP and select theSNP Subcontracting option in the integration model, the transportation lane from the plant to thesubcontractor location is automatically created in the SAP SCM system for all components, not just forthe end product. The product master data is also automatically transferred to the subcontractor location.

See also

For more information, see the SNP documentation entitled Subcontracting with Source Location inSNP and Subcontracting with Third-Party Provision of Components in SNP and the ProductionData Structure in SNP release information.

1.1.14 SCM-APO-CPR Collaborative Procurement

1.1.14.1 Business Add-In for Determining a Suitable Means of Transport (New)

Use

As of SAP SCM 4.1 you can use the Business Add-In (BAdI)Prioritization of Sources of Supply andMeans of Transport (/SAPAPO/SOS_COST) to influence the way the means of transport for salesscheduling agreements is selected, so that the system determines a suitable means of transport.As a default, transport costs are given priority. If two means of transport carry the same transport costs,the means of transport that is fastest is given priority.


In Customizing for Advanced Planning and Optimization, choose Supply Chain Planning ->Delivery Schedule Processing for the Sales Scheduling Agreement ->Business Add-Ins(BAdIs)-> Means of Transport.

______________________________________________________________SAP AG 159

SAP-System______________________________________________________________

1.1.14.2 SCM-APO-CPR-SCH Procurement Scheduling Agreement

1.1.14.2.1 Enter Confirmations Manually (New)

Use

As of SAP SCM 4.1 there is a dedicated function for manually entering and changing confirmations thatyou have received from your vendor by fax or post.You can access this function from the menu by choosing Supply Chain Collaboration -> CollaborativeProcurement -> Scheduling Agreement Releases -> Enter Confirmations.

As of SAP SCM 4.1 it is no longer possible to change confirmed quantities in the interactive planningfunctions (Product View and Product Planning Table).


In the authorization object C_APO_EXPR you can define whether a user has permission to display orenter confirmations.

See also

For more information, see the SAP Library: SAP Advanced Planning and Optimization (SAP APO)-> Production Planning and Detailed Scheduling PP/DS -> Collaborative Management ofDelivery Schedules.

1.1.14.3 SCM-APO-CPR-TRA Stock Transfer

1.1.14.3.1 Transfer of Characteristic Requirements to Stock Transfer Doc. (New)

Use

As of SAP SCM 4.1, you can transfer characteristic requirements of demand to stock transfer documents.

The system copies the characteristic requirements from the pegged requirement to the stock transferdocument, and assigns demand and stock transfer documents to each other by means of automaticallyfixed pegging.

This enables you to use characteristic requirements in planning across plants.

______________________________________________________________SAP AG 160

SAP-System______________________________________________________________


You can activate this function in Customizing for Advanced Planning and Optimization under SupplyChain Planning -> Production Planning and Detailed Scheduling (PP/DS) -> Global Settings ->Transfer Characteristic Requirements to Stock Transfer Doc.

1.1.15 SCM-APO-INT Interfaces

1.1.15.1 Consistency Check for Product Variants (New)

Use



1.1.15.2 Implementation Guide for SAP APO Core Interface (New)

Use

Until now, you maintained the Customizing settings for integrating SAP APO and SAP R/3 in theImplementation Guide (IMG) for SAP Advanced Planning and Optimization under Basis Settings ->Integration.

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, you can find these IMG activities in theImplementation Guide for SAP APO Core Interface under Integration with SAP Components ->Integration of SAP SCM and SAP R/3 -> Basic Settings for Data Transfer. In this ImplementationGuide you can also find all the other IMG activities that you need to create the system landscape and toconfigure and influence the data transfer between SAP APO and SAP R/3 using CIF. The IMG nodeIntegration named above has been deleted.

The Implementation Guide is divided into three main parts:

- Basic Settings for Creating the System Landscape

______________________________________________________________SAP AG 161

SAP-System______________________________________________________________

Here you can find all the IMG activities that you need to execute to enable SAP APO and SAP R/3to communicate with one another, for example, name the logical systems, name the RFCdestinations, or execute qRFC settings.

- Basic Settings for Data TransferHere you can find all the IMG activities that are necessary for transferring data, for example,publishing events from SAP APO.

- Application-Specific Settings and EnhancementsHere you can find customer exits, Business Add-Ins (BAdIs), and settings for individualapplications, for example, for stocks or in-house production.

1.1.15.3 CIF Cockpit (New)

Use

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, you can use the CIF cockpit to centrally monitor thedata transfer between your SAP APO system and all connected SAP R/3 systems using SAP APO CoreInterface (CIF). You can use the CIF cockpit to gain a quick overview of the transfer load of the currentoperation (Monitoring) and an overview of the Customizing settings (Settings) in all systems and clientsthat are relevant to the transfer.

To call the CIF cockpit, choose from the SAP Easy Access screen for mySAP Supply ChainManagement: Advanced Planning and Optimization -> APO Administration -> Integration ->Monitor -> CIF Cockpit.

The CIF cockpit allows you to configure in a user-specific way how information about background jobs,entries in the application log, and the CIF comparison/reconciliation of transaction data is displayed. Todo this, choose Settings -> User Profile.

From the CIF cockpit you can go to the relevant transaction to find detailed information.

You can find the following information under Monitoring:

- SAP APO system

- General information, for example, release

- CIF background jobs

- Entries in the application log

- Routing information

- SAP R/3 system

- General information

______________________________________________________________SAP AG 162

SAP-System______________________________________________________________

- CIF background jobs

- Entries in the application log

- Superfluous filter objects

- Inconsistent APO indicators

- Transfer from SAP APO system to SAP R/3 system

- CIF transfer

- qRFC

- Postprocessing records

- CIF comparison/reconciliation of transaction data

- Comparison of routing information

- Transfer from SAP R/3 system to SAP APO system

- CIF transfer

- qRFC

- Postprocessing records

- Integration model consistency

- Performance of each application

You can find the following information under Settings:

- SAP APO system

- General information

- Distribution settings

- Enhancement projects

- Additional settings: user parameters, strategy profiles, and SNP settings

- SAP R/3 system

- Block sizes for initial data transfer

- Enhancement projects

- Additional CIF-relevant settings, for example, settings for the change transfer

- Transfer from SAP APO system to SAP R/3 system

- Integration models

- qRFC

- Inspection lots

- Transfer from SAP R/3 system to SAP APO system

- Distribution criteria

- qRFC

______________________________________________________________SAP AG 163

SAP-System______________________________________________________________

- Error handling

1.1.15.4 SAP APO Monitoring in Computing Center Management System(CCMS) (New)

Use

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, you can monitor the transfer of data between all SAPAPO systems/clients and connected SAP R/3 systems/clients via SAP APO Core Interface (CIF). In theCCMS you can configure the situations for which the system generates alerts. You can also use alerts tohave the system inform you of certain situations by e-mail, SMS, or WAP.

In this way, you gain a central overview of where problems have occurred during the transfer. You canthen directly rectify the problems by going to the relevant transaction from the CCMS. You can also usethe CIF cockpit or another suitable transaction to rectify errors.

You can monitor the following situations:

- CIF monitorYou can configure whether SAP APO clients are to be excluded from monitoring.

- CIF postprocessingThe CCMS displays the number of unprocessed postprocessing records and the number ofobsolete and processed postprocessing records. You can go directly to CIF postprocessing(transaction /SAPAPO/CPP) to analyze the records.

- CIF comparison/reconciliation of transaction dataThe CCMS displays the number of unloaded comparison results and the number of comparisonresults that are older than a certain number of days (configurable). You can go directly to theCIF comparison/reconciliation of transaction data (transaction /SAPAPO/CCR) to analyzethese results.

- qRFC consumption of planned independent requirements

- Status of the consumption of sales orders using qRFCThe CCMS displays faulty queue entries in the inbound queues for Fulfillment Coordination(FC* queues). You can go directly to the qRFC monitor for inbound queues (transactionSMQ2) to analyze these entries.

- CIF queues

- Monitoring the inbound and outbound queues in CIF (CF* queues)The CCMS displays the faulty queue entries in the inbound and outbound queues in CIF.In the case of outbound queues, the CCMS shows the age in days of the oldest queues. You can

______________________________________________________________SAP AG 164

SAP-System______________________________________________________________

configure the age, for example, older than 10 days. 7 days is set as the default value.You can go directly to the qRFC monitor for inbound or outbound queues (transaction SMQ2or SMQ1).

To call the CCMS, choose from the SAP Easy Access screen for mySAP Supply ChainManagement: Advanced Planning and Optimization -> APO Administration -> Integration ->Monitor -> CCMS Monitor Sets. Then choose the node APO Monitor.

This function is available in the SAP APO system. The monitor also exists on the SAP R/3 side.However, in SAP R/3 you can only monitor the entry CIF Queues. See also SAP Note 708361, if youuse an SAP R/3 release from 4.5B to 4.6C.

1.1.15.5 Configuration Check in the CIF Comparison/Reconciliation (New)

Use

Until now, the CIF comparison/reconciliation of transaction data (delta report) did not check theconfiguration data for orders.

Simple configuration check

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, the CIF comparison/reconciliation of transaction dataalso checks by default if an order refers to the same configuration data (simple configuration check). Thesystem does not, however, check if the contents of the configuration data agree. In the case ofcharacteristics-dependent planning (CDP), the simple configuration check merely checks whether aconfiguration exists for the order.

Extended configuration check

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, the selection screen for the CIFcomparison/reconciliation also offers the additional option Extended Configuration Check. If you setthis indicator, the delta report checks whether the contents of the configuration data (characteristic valueassignments) agree in SAP APO and SAP R/3. The extended configuration check can have a negativeeffect on performance. If you do not set the indicator Extended Configuration Check, the simpleconfiguration check is performed.

The simple and extended configuration checks apply to the following object types:

- Manufacturing orders

- Planned orders

- Purchase orders

- Purchase requisitions

______________________________________________________________SAP AG 165

SAP-System______________________________________________________________

- Sales orders

- Deliveries

- Sales scheduling agreements

1.1.15.6 New Options in the CIF Comparison/Reconciliation (Enhanced)

Use

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, the following options are available in the CIFcomparison/reconciliation of transaction data (delta report).

- You can also execute the comparison/reconciliation for the object types Project Orders andMaintenance Orders.

- In the case of manufacturing orders, project orders, and maintenance orders, you can also specifythat the program checks for both inconsistencies for requirements/receipts and for operations. Youcan also have the system check maintenance orders for downtimes.

- You can also use the additional option Extended Configuration Check. For more information, seeExtended Configuration Check in the CIF Comparison/Reconciliation of Transaction Data.

See also

For information about the new interface of the program, see New Interfaces for the Program CIFComparison/Reconciliation of Transaction Data.

1.1.15.7 New Interfaces in the CIF Comparison/Reconciliation (Changed)

Use

Until now, the program displayed the comparison results on tab pages that were each relevant to an objecttype. To ensure that the display remains clear and easy-to-use in view of the new object types that havebeen included, the results screen has the following structure as of SAP SCM 4.1.:

______________________________________________________________SAP AG 166

SAP-System______________________________________________________________

- On the left-hand side of the screen, you find the selected object types, for example, planned orders,as the nodes of a tree structure. Each node contains lower-level nodes with the error categories thatoccurred for each object type, for example, Missing in APO. Only those object types whereinconsistencies were found are displayed as nodes. When you select an error category, you get a liston the right-hand side of the screen containing the inconsistencies with this error category that werefound for the relevant object type.The highest node in the tree structure (Results) offers you a quick overview of the number and typeof inconsistencies that occurred, separated according to documents and stocks.

- On the right-hand side of the screen, you find the list of inconsistencies with the selected errorcategory that were found for the relevant object type. For more information about the error, click theerror code. You can also reconcile individual inconsistent objects from within this list.

- In the top row you find pushbuttons with which you can execute iteration, see the selection criteria,or save or load comparison results.

- If errors occur in liveCache during data selection, they appear in their own node in the navigationtree on the results screen.

See also

For information about additional options in the program, see New Options in the CIF Comparison/Reconciliation of Transaction Data.

1.1.15.8 Integration of SAP R/3 Source List with SAP APO (New)

Use

In SAP R/3 you can define validities for external procurement relationships (contracts, schedulingagreements, and purchasing info records) in the source list. Up to now, the information from the sourcelist records was not transferred to SAP APO. SAP APO created a transportation lane for each externalprocurement relationship, without taking into account the validities entered in the source list.

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, you can set up the integration of SAP R/3 source listrecords with SAP APO in the Implementation Guide in SAP R/3. Then SAP R/3 transfers the informationfrom source list records that is marked as being MRP-relevant to SAP APO. Source list records forvendor's plants are not transferred. For each source list record transferred, SAP APO creates atransportation lane. The source list integration is not activated by default.

To activate the source list integration, choose in SAP R/3 in the Implementation Guide for the APO CoreInterface Application-Specific Settings and Enhancements -> Settings and Enhancements forExternal Procurement -> Inbound Processing of Purchasing Data -> Activate/Deactivate SourceDetermination/Source List Integration and set the relevant indicator.

______________________________________________________________SAP AG 167

SAP-System______________________________________________________________

1.1.15.9 Subcontracting for Multiple Plants with Loc. Type Subcontractor (New)

Use

Up to now, a subcontractor was mapped in SAP APO as a vendor location (location type Vendor).Subcontracting for multiple plants could not be mapped in SAP APO, since the system could notdistinguish between the plants, and mixed up the receipts and requirements for the plants.

As of SAP SCM 4.1 and SAP R/3 Plug-In 2004.1, the new location type Subcontractor is available. Youcan assign both a plant and a vendor in this subcontractor location. Planning for a plant-vendorcombination now takes place in the subcontractor location. If a subcontractor works for multiple plants,you can map this situation by creating multiple subcontractor locations each with its own plant-vendorcombinations.

You create the subcontractor location manually in the location master data maintenance in SAP APO.The subcontractor location is not integrated with SAP R/3.

1.1.15.10 SCM-APO-INT-EXT Interface to External Systems

1.1.15.10.1 Business and Interface Objects and BAPI Methods (Changed)

Use

The following information describes changes that have been made in SAP SCM 4.1 to business objectsand interface objects and the Business Application Programming Interfaces (BAPIs) or ALE interfaces(message types) contained within them from the following components:

- SCM-APO-MD Master Data

- SCM-APO-PPS Production Planning and Detailed Scheduling

- SCM-APO-VS Vehicle Scheduling

- SCM-APO-FCS Demand Planning

______________________________________________________________SAP AG 168

SAP-System______________________________________________________________

- SCM-APO-ATP Global Availability Check

The technical names of the relevant objects in the Business Object Repository (BOR) are:

- BUS10001 - BUS10004

- BUS10008 - BUS10009

- BUS10020, BUS10030

- BUS10300

- BUS10400

- BUS10500 - BUS10505

- BUS10510

- BUS11201

- BUS11102

- BUS11411 - BUS11415

The corresponding interface objects, if they exist, have the same numbers. The interface object forBUS10501 is therefore IF10501.

Note in particular that some interfaces have been set to obsolete. Some incompatible changes have alsobeen made, that is, conversions may be required.

Use of the IDocs/ALE interfaces and the function modules for BAPI methods

Changes to the BAPI methods also have an effect on each of the corresponding ALE interfaces ormessage types. If you use IDoc message types that call the corresponding BAPI methods of thesebusiness objects, read the release information for the relevant BAPI methods.

Changes that affect the majority of business objects/interface objects of these components ortheir methods and ALE message types

Compatible changes have been made to some of the methods or structures, that is, fields or parametershave been inserted. The system group of the relevant master data record, for example, is now alsoreturned in many read methods that contain master data information, for example, the product number.

Changes that only affect methods of certain business objects/interface objects of thesecomponents or their methods and ALE message types

The following is a list of the new or changed business objects and BAPIs. For more detailed information,see the documentation for the individual BAPIs.

Note that some BAPIs listed have not been released yet. You can use these BAPIs already, butincompatible changes are still possible since the BAPIs have not been released yet.

If you use the corresponding function modules of the BAPIs instead of the BAPIs, the changes also applyto these function modules.

Sending transaction data using BAPIs

For more information, see Sending Transaction Data Using BAPIs.

Deleting transaction data using BAPIs

______________________________________________________________SAP AG 169

SAP-System______________________________________________________________

For more information, see Deleting Transaction Data Using BAPIs.

Function BAPI_ORSRVAPS_GETLIST

This function has been set to obsolete. The new method PPDSServiceAPS.GetReqsReceipts has a similarpurpose.

BUS10500 (PPDSServiceAPS)

GetReqsReceipts

New methods for general reading of requirements and receipt elements

BUS10030 (Vehicle Scheduling Planning Services)

GetOptimizerProfile

Incompatible change: The field OPT_RESPECT_TIME is no longer used in parameterPROFILE_HEAD. This field is also no longer used in the application.

BUS10503 (Production Order APS)

Some of the methods now also support orders from the Rapid Planning Matrix. For more information, seethe documentation for business object BUS10503.

Interfaces BUS10500, BUS10501, BUS10502, BUS10503, BUS10504, BUS10001, BUS10002,BUS10003, BUS10004, BUS10009, BUS11411, BUS11412, BUS11413, BUS11414,BUS11415, BUS11201, BUS11102

New BAdIs have been added to some of the receive methods (definition name APO_BAPI_BUS*, forexample, APO_BAPI_BUS10503).

BUS10001 (ProductAPS)

The methods SaveMultiple2, GetList2, RemoveItems, DeleteMultiple, RequestList2, and ReceiveList2have been enhanced.

BUS10002 (LocationAPS)

The methods SaveMultiple2, GetList2, DeleteMultiple, RequestList2, and ReceiveList2 have beenenhanced.

BUS10003 (ProdProcessModelAPS)

The methods SaveMultiple, GetList, DeletePlan, DeletePpm, RequestList, and ReceiveList have beenenhanced.

BUS10004 (ResourceAPS)

The methods SaveMultiple, ChangeMultiple, GetList, RequestList, ReceiveList, and RemoveSubobjectshave been enhanced.

BUS10009 (QuotaAPS)

The methods SaveMultiple2, GetList2, RequestList2, ReceiveList2, and DeleteMultiple have beencreated. The methods SaveMultiple, GetList, RequestList, and ReceiveList have been set to obsolete.

BUS11411 (LocSubProcAPS)

The methods SaveMultiple, GetList, RequestList, ReceiveList, and DeleteMultiple have been enhanced.

BUS11412 (PrdSubProcAPS)

______________________________________________________________SAP AG 170

SAP-System______________________________________________________________


BUS11413 (SubstitutionRuleAPS)


BUS11414 (LocPrdSubProcAPS)


BUS11415 (PpmSubProcAPS)


BUS10030 (PlanningBookAPS)

The methods GetDetail2, ChangeKeyfigureValue2, RequestDetail2, and ReceiveDetail2 have beencreated. The methods GetDetail and ChangeKeyfigureValue have been set to obsolete.

1.1.15.10.2 Deletion of Transaction Data Using BAPIs (New)

Use

As of SAP SCM 4.1, you can use transaction /SAPAPO/BP2 to delete transaction data that was createdusing Business Application Programming Interfaces (BAPIs). You can delete this data using the reportonline or in the background without any programming effort.

You can find this function in the SAP APO menu under APO Administration -> Integration ->Integration with Non-SAP Systems -> Delete Transaction Data Using BAPI.

See also

For more information about BAPIs, see Business and Interface Objects and BAPI Methods.

1.1.15.10.3 Sending Transaction Data Using BAPIs (New)

Use

______________________________________________________________SAP AG 171

SAP-System______________________________________________________________

As of SAP SCM 4.1, you can use transaction /SAPAPO/BP1 to send transaction data that was createdusing Business Application Programming Interfaces (BAPIs) to an external system. You can send thisdata using the report online or in the background without any programming effort.

You can find this function in the SAP APO menu under APO Administration -> Integration ->Integration with Non-SAP Systems -> Send Transaction Data Using BAPI.

See also

For more information about BAPIs, see Business and Interface Objects and BAPI Methods.

1.1.15.11 SCM-APO-INT-MD Master Data

1.1.15.11.1 SCM-APO-INT-MD-PDS Production Data Structure

1.1.15.11.1.1 Enhanced Integration of Reference Operation Sets (Enhanced)

Use

In a routing used in SAP R/3, operations can also be used as references via a reference operation set. Theadvantage of this is that you can use the same sequence of operations in routings as many times as youwant.If you use a routing when you create an R/3 production order the operations from the reference operationset are taken into account, in addition to the operations defined manually in the routing.

Until SAP APO 4.0, manufacturing orders with operations from referenced reference operation sets fromR/3 could only be correctly integrated into SAP APO if only one operation was added as a reference tothe order for each referenced routing. The simultaneous inclusion of multiple operations using a referenceoperation set referenced in a routing lead to incorrect results in order integration or comparison ofoperation data in SAP APO.

As of SAP SCM 4.1 with Plug-In 2004.1 you can also use routings in which multiple operations from astandard routing are referenced.

With the new enhanced operation mapping, within the framework of order integration, an unlimitednumber of referenced operations from a standard routing can be compared with the operation data in SAPAPO and correctly integrated. The enhanced operation mapping is only supported if you work withPP/DS production data structures (PP/DS PDS).The enhanced operation mapping uses an additional criterion to merge operation data in SAP APO. Thisallows you to identify all referenced operations in the APO manufacturing order. As a result, thecomponent assignments of all referenced operations can be transferred correctly to SAP APO. This isindicated in the APO manufacturing order.

______________________________________________________________SAP AG 172

SAP-System______________________________________________________________

Constraints

The enhanced mapping of operations is only supported if you work with PP/DS production datastructures and not if you use the production process model (PPM).Suboperations from referenced operations are not taken into account in integration and therefore are notrelevant for enhanced mapping of operations.


The PP/DS production data structures must be regenerated after an upgrade, if you already worked withreference operation sets in a lower release. The PP/DS production data structure only offers the explosionresult in the new format.

The existing mapping of operations is retained for combinations with another Plug-In release.

For the PP/DS production data structure the following applies: On upgrade, existing operation mapping isvalid for old data; for new data enhanced operation mapping is used.

See also

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAP APO)under Integration of SAP APO and SAP R/3 -> Integration of Master Data and Transaction Data ->Integration of Transaction Data.

1.1.15.11.1.2 PP/DS Production Data Structure Comparison (Previously: PP/DSRuntime Object (New)

Use

As of SAP SCM 4.1 you can compare R/3 master data with the PP/DS production data structure generatedfrom it in SAP APO. This means that you can check whether R/3 data has been transferred to SAP APOcorrectly.This function is made up of two comparisons:

1. Comparison of the Change DateYou can use this simple comparison to check whether R/3 master data or changes to it has alreadybeen transferred to SAP APO, based on the date of the last change to the bill of material, routing,master recipe and production version.

2. Comparison of the Explosion ResultsYou can use this comparison to carry out a detailed check of the master data, based on the explosionresults.During the comparison, the explosion result of the R/3 manufacturing order (production or processorder) is simulated and compared with the simulated explosion result of the PP/DS production datastructure in SAP APO.

______________________________________________________________SAP AG 173

SAP-System______________________________________________________________

Within this comparison, the system compares operations, phases, input and output products and theactivity relationships of the manufacturing order.

NoteYou should note that the master data explosion for orders in the comparison is simulated andused as the basis for the comparison. If Business Add-Ins are executed during the comparisonthe result of the comparison may be incorrect.

3. Retransfer of the Master DataFor deviating master data, you can carry out a retransfer of the PP/DS production data structurefrom SAP R/3 to SAP APO.

Choose Advanced Planning and Optimization -> APO Administration -> Integration -> CompareMaster Data -> Compare PP/DS Production Data Structure.

See also

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAP APO) under Integration of SAP APO and SAP R/3 -> Technical Integration -> SAP APO CoreInterface.

For more information about the name change from PP/DS runtime object (PP/DS-LZO) to PP/DSproduction data structure (PP/DS-PDS) see the release notes Renaming: Runtime Object (LZO) -Production Data Structure (PDS).

1.1.15.12 SCM-APO-INT-PPS PP/DS - Production Process Order

1.1.15.12.1 Enhanced Integration of Reference Operation Sets (Enhanced)

Use

In a routing used in SAP R/3, operations can also be used as references via a reference operation set. Theadvantage of this is that you can use the same sequence of operations in routings as many times as youwant.If you use a routing when you create an R/3 production order the operations from the reference operationset are taken into account, in addition to the operations defined manually in the routing.

Until SAP APO 4.0, manufacturing orders with operations from referenced reference operation sets fromR/3 could only be correctly integrated into SAP APO if only one operation was added as a reference tothe order for each referenced routing. The simultaneous inclusion of multiple operations using a referenceoperation set referenced in a routing lead to incorrect results in order integration or comparison ofoperation data in SAP APO.

As of SAP SCM 4.1 with Plug-In 2004.1 you can also use routings in which multiple operations from astandard routing are referenced.

With the new enhanced operation mapping, within the framework of order integration, an unlimited

______________________________________________________________SAP AG 174

SAP-System______________________________________________________________

number of referenced operations from a standard routing can be compared with the operation data in SAPAPO and correctly integrated. The enhanced operation mapping is only supported if you work withPP/DS production data structures (PP/DS PDS).The enhanced operation mapping uses an additional criterion to merge operation data in SAP APO. Thisallows you to identify all referenced operations in the APO manufacturing order. As a result, thecomponent assignments of all referenced operations can be transferred correctly to SAP APO. This isindicated in the APO manufacturing order.

Constraints

The enhanced mapping of operations is only supported if you work with PP/DS production datastructures and not if you use the production process model (PPM).Suboperations from referenced operations are not taken into account in integration and therefore are notrelevant for enhanced mapping of operations.


The PP/DS production data structures must be regenerated after an upgrade, if you already worked withreference operation sets in a lower release. The PP/DS production data structure only offers the explosionresult in the new format.

The existing mapping of operations is retained for combinations with another Plug-In release.

For the PP/DS production data structure the following applies: On upgrade, existing operation mapping isvalid for old data; for new data enhanced operation mapping is used.

See also

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAP APO)under Integration of SAP APO and SAP R/3 -> Integration of Master Data and Transaction Data ->Integration of Transaction Data.

1.1.15.12.2 CIF Compare/Reconcile Function for Operations and Phases (New)

Use

As of SAP SCM 4.1, you can now also compare operations and phases in the CIF Compare/ReconcileFunction (Delta Report).You can check operations and phases as part of the comparison of production or process orders.The system displays whether operations, phases, suboperations or secondary resources are missing inSAP R/3 or SAP APO.The system also checks whether the contents of operations and phases are in any way inconsistent.Together with the comparison of operations and phases, the assignment of receipts and requirements toAPO-relevant operations and phases can also be checked.

Choose Advanced Planning and Optimization -> APO Administration Integration -> CIF

______________________________________________________________SAP AG 175

SAP-System______________________________________________________________

Compare/Reconcile Function.Any variances found are displayed under Production/Process Orders -> Operations.


You can use the Business Add-In (BAdI) /SAPAPO/CIF_DELTA3 Compare/Reconcile Function todeactivate individual comparisons, for example, of quantities, dates/times or work centers.

See also

For more information, see the SAP Library for SAP Advanced Planning and Optimization (SAP APO) under Integration of SAP APO and SAP R/3 -> Technical Integration -> SAP APO Core Interface-> Administration -> The Compare/Reconcile Function (Delta Report).

For more information on the new appearance of the CIF Compare/Reconcile Function (Delta Report) seethe Release Information New Interface for the Results Screen of the Delta Report (Enhanced).

1.1.15.12.3 Setup Information in Order Integration (Changed)

Use

Up to and including SAP APO 4.0, only the setup information (APO setup group and setup key) fromthe master data (and not the setup information from the order in R/3 (R/3 setup group family and setupgroup key)) was taken into account during the integration of process and production orders.When orders were created or changed, the setup information was determined from the APO master data,in other words, from the production process model (PPM), runtime object or production data structure(PDS).

As of SAP SCM 4.1 with Plug-In PI 2004.1 both the R/3 setup information of the order and the APOsetup information from the PPM or PDS is taken into account during integration of production andprocess orders.These changes can have different effects when you upgrade:

- If, until now, you have maintained setup information in SAP APO only, in the PPM or PDS, thenthe upgrade does not cause any changes.

- If you have maintained setup information only in SAP R/3 until now, and do not use a PPM or PDSin SAP APO then the setup information is copied from the R/3 order to SAP APO once the upgradehas taken place.

- If an order in SAP R/3 contains setup information and you have maintained a PPM or PDS in SAPAPO then the R/3 setup information from the order is used in SAP APO and not the APO masterdata (as was the case previously).This means that the R/3 setup information is given priority over the setup information from the APOmaster data (PPM and PDS).You should note that adding or deleting data in SAP R/3 has the following effects:

- If you add an operation with setup information to the order in SAP R/3 then this operation andits setup information is copied to the order in SAP APO even if you use a PDS or PPM in SAP

______________________________________________________________SAP AG 176

SAP-System______________________________________________________________

APO and a master data explosion has already been carried out for this order in SAP APO.

- If you delete setup information in SAP R/3 in a production or process order, setup informationis retained in the order in SAP APO.

NoteYou should note that there are certain prerequisites for the integration of process orders:You must have maintained the same setup information in SAP R/3:

- For the first operation and the first phase

- Or for the first phase only

- Or for the operation only (in this case, no sequence-dependent setup activity is created during orderintegration in SAP APO).

Inconsistent setup information in SAP R/3 leads to errors in order integration. Therefore, you must not:

- Assign different setup information to an operation and its phases

- Assign different setup information to the different phases of an operation

The compare/reconcile function checks whether the operations of production and process orders match.For more information, see the SAP Library for SAP Advanced Planner and Optimizer (SAP APO) underIntegration of SAP APO and SAP R/3 -> Technical Integration -> APO Core Interface -> Administration-> CIF Compare/Reconcile Function -> Inconsistencies Recognized by the Compare/Reconcile Function-> Comparison of In-House Production Orders -> Comparison of Operations and Phases.

The integration of the setup information of production orders differs from that of process orders in thefollowing aspects:

Integration of Production Orders from SAP R/3

The operations may contain setup information.

- Production order without setup informationIf the order from SAP R/3 does not contain any setup information but setup information has beenmaintained in the PPM or PDS in SAP APO, the APO setup information is used in SAP APO.

- Production order with setup informationWhen setup information from production orders is copied from SAP R/3 to SAP APO the setupinformation for an operation in SAP APO is forwarded to all activities/phases.If an activity setup exists for the operation then this activity becomes a sequence-dependent setupactivity in SAP APO.

Integration of Process Orders from SAP R/3

Operations and phases of a process order may contain setup information.

- Process order without setup informationIf the order from SAP R/3 does not contain any setup information but setup information has beenmaintained in SAP APO in the PPM or PDS then this setup information is used in SAP APO.

______________________________________________________________SAP AG 177

SAP-System______________________________________________________________

- Setup information for the operationWhen setup information from process orders is copied, the setup information for an operation inSAP APO is forwarded to all activities/phases.

- Setup information for the operation and the first phaseIf the setup information for the operation and the first phase is maintained in SAP R/3, the firstphase becomes a sequence-dependent setup activity in SAP APO. In addition, in SAP APO, thesetup information is forwarded to all activities/phases of the operation (and for display, to theoperation itself).

- Setup information at the first phase onlyIf the first phase contains the setup information in SAP R/3 then this phase becomes thesequence-dependent setup activity in SAP APO. In addition, the setup information is forwarded toall activities/phases of the operation in SAP APO (although not for display to the operation itself).

1.1.15.13 SCM-APO-INT-CCR CIF Compare/Reconcile

1.1.15.13.1 CIF Compare/Reconcile Function for Operations and Phases (New)

Use

As of SAP SCM 4.1, you can now also compare operations and phases in the CIF Compare/ReconcileFunction (Delta Report).You can check operations and phases as part of the comparison of production or process orders.The system displays whether operations, phases, suboperations or secondary resources are missing inSAP R/3 or SAP APO.The system also checks whether the contents of operations and phases are in any way inconsistent.Together with the comparison of operations and phases, the assignment of receipts and requirements toAPO-relevant operations and phases can also be checked.

Choose Advanced Planning and Optimization -> APO Administration Integration -> CIFCompare/Reconcile Function.Any variances found are displayed under Production/Process Orders -> Operations.


You can use the Business Add-In (BAdI) /SAPAPO/CIF_DELTA3 Compare/Reconcile Function todeactivate individual comparisons, for example, of quantities, dates/times or work centers.

______________________________________________________________SAP AG 178

SAP-System______________________________________________________________

See also

For more information, see the SAP Library for SAP Advanced Planning and Optimization (SAP APO) under Integration of SAP APO and SAP R/3 -> Technical Integration -> SAP APO Core Interface-> Administration -> The Compare/Reconcile Function (Delta Report).

For more information on the new appearance of the CIF Compare/Reconcile Function (Delta Report) seethe Release Information New Interface for the Results Screen of the Delta Report (Enhanced).

1.1.15.14 SCM-APO-INT-CPP Postprocessing Records of CIF ErrorHandling

1.1.15.14.1 Creation of Notes in CIF Error Handling (Enhanced)

Use

As of SAP SCM 4.1 you can create, change, and delete notes for postprocessing records in CIF errorhandling. This makes it easier when processing postprocessing records in multiple steps or when severalprocessors are involved.

To create a note, select the relevant row in CIF error handling and choose Edit Note in the menu bar.You can also change or delete existing notes.

Notes are language-dependent. Only notes that were created in the logon language are displayed.

1.1.15.15 SCM-APO-INT-POR Project Order

1.1.15.15.1 Project Orders (New)

Use

As of SAP SCM 4.1, SAP R/3 networks with component requirements and capacity requirements areintegrated with Production Planning and Detailed Scheduling (PP/DS) functions in SAP SCM. Thisenables component requirements and capacity requirements from these networks to be planned in SAPSCM.

The following functions have been added:

- New order type 'project order' in SAP SCM to represent an SAP R/3 network

______________________________________________________________SAP AG 179

SAP-System______________________________________________________________

- Transfer of:

- Created or changed networks from SAP R/3 and receipt of project order in SAP SCM

- Preliminary purchase requisitions and purchase orders from SAP R/3 to SAP SCM

- Planned independent requirements from SAP R/3 to SAP SCM

- Enhancements to the order processing transaction in SAP SCM for project orders

- Scheduling and planning of component requirements in SAP SCM

- ATP check for project orders in SAP SCM

- Interchangeability for project orders in SAP SCM

- Optimization for project orders in SAP SCM

- Inclusion of project order in planning version management in SAP SCM

- Transfer of project order from SAP SCM to SAP R/3

- Transfer of current data from SAP R/3 to SAP SCM

- Enhancements to standard core interface (CIF) comparison/reconciliation report in SAP SCM forproject orders

Some restrictions apply to the integration and are listed in SAP Note 708517. The most importantrestrictions are:

- External relations between networks are not transferred. Overall network scheduling should not beexecuted in SAP SCM.

- The complexity of transferred networks may have a serious impact on performance, and on theexecution and results of finite scheduling and optimizing in SAP APO Detailed Scheduling (DS).Therefore, we recommend that you especially test and design the size of networks at an early stagewithin the implementation phase.


The integration of SAP R/3 networks with project orders in SAP SCM is possible as of Plug-In Release2004.1 for R/3 4.6C and Plug-In Release 2004.1 for R/3 4.70.

See also

SAP Notes

In the Service Marketplace at service.sap.com/notes, see Note Number 708517.

SAP Library

SAP Supply Chain Management -> SAP Advanced Planner and Optimization (SAP APO) under:

______________________________________________________________SAP AG 180

SAP-System______________________________________________________________

- Integration of SAP SCM and SAP R/3 -> Integration of Master Data and Transaction Data->Integration of Orders -> Integration of Project Orders/Networks

- Integration of SAP SCM and SAP R/3 -> Integration of Master Data and Transaction Data ->Integration of Transaction Data -> Integration of Orders -> Integration of Project Orders

- Production Planning and Detailed Scheduling (PP/DS) -> Order -> Project Order

- Cross-Application Topics -> Product Interchangeability -> Product Interchangeability in PP/DS ->Adoption of Substitute Components in the Project Order

1.1.15.16 SCM-APO-INT-MOR Maintenance Order

1.1.15.16.1 Maintenance Orders (New)

Use

As of SAP SCM 4.1, SAP R/3 plant maintenance (PM) orders and refurbishment orders can betransferred to maintenance orders in SAP SCM. To enable this, the order type 'maintenance order' hasbeen created.

Maintenance Planning

As previously, the creation, scheduling, and capacity planning of PM orders and refurbishment orderstakes place in SAP R/3. However, as soon as a PM order or refurbishment order is saved, the SAPSCM-relevant part of that order (that is, operations with scheduled start dates and end dates, componentrequirements, and the downtime of the technical asset) is transferred to a maintenance order in SAP SCM.A new type of downtime is available in SAP SCM for maintenance.

A maintenance order in SAP SCM is fixed and cannot be changed. Its only purpose is to completeplanning by providing maintenance-triggered component requirements and resource downtimes.

The component requirements are visible as reservations and can be planned like reservations ofproduction orders using the standard SAP SCM planning functions. The resulting planned orders,purchase requisitions, production orders, and purchase orders can be transferred back to SAP R/3 usingthe standard core interface (CIF) functions.

In addition to the integration of PM orders and refurbishment orders as maintenance orders, the followingfunctions have been enhanced in SAP SCM:

- Order processing in Interactive Production Planning now includes order type 'maintenance order'.

- The CIF comparison and reconciliation of transaction data now includes maintenance orders. Thisallows you to:

- Compare the existence of PM orders and refurbishment orders with maintenance orders.

- Compare the data in PM orders and refurbishment orders with maintenance orders.

- Resolve any deltas, such as missing maintenance orders, missing PM orders, deltas in orderstructures or actual data, and missing downtimes in SAP SCM.

Maintenance Execution

______________________________________________________________SAP AG 181

SAP-System______________________________________________________________

The complete execution process is handled in SAP R/3. The statuses are set and changed, and the goodsissues and confirmations are posted to the PM order.

To complete planning, SAP R/3 transfers the current data for order confirmations and reversals, andgoods issues and reversals to SAP SCM, which enables you to replan the component requirements.

The technical completion or deletion of a PM order in SAP R/3 triggers the deletion of the correspondingmaintenance order in SAP SCM.


You cannot convert maintenance orders into Supply Network Planning (SNP) orders.

An incoming maintenance order that creates a downtime on a resource does not adjust any blockdefinitions on that resource, because downtimes are not synchronized with defined blocks for blockplanning.

Discontinuation in SAP R/3 is not integrated with SAP SCM.


You can transfer only component requirements in plant, project, and sales order stock, and vendorconsignment. You cannot transfer relationships across PM orders, capacity requirements, or configurationdata of component requirements.

For the transfer of PM orders and refurbishment orders, SAP R/3 has been enhanced to provide:

- Transfer of PM orders and refurbishment orders in the initial CIF run and when saving those orders.The integration model contains selection criteria for PM order type and plant.

- Determination of downtime capacities

For the receipt of maintenance orders, SAP SCM has been enhanced to provide:

- CIF error handling for maintenance orders

- Creation of operations and consumption of existing planned independent requirements

- Creation of or changes to resource downtimes


The integration of PM orders and refurbishment orders with maintenance orders in SAP SCM is possibleas of Plug-In Release 2004.1 for R/3 4.6C, and Plug-In Release 2004.1 for R/3 4.70.

See also

SAP Library:

SAP Supply Chain Management -> SAP Advanced Planner and Optimization (SAP APO):

- Integration of SAP SCM and SAP R/3 -> Integration of Master Data and Transaction Data ->Integration of Transaction Data -> Integration of Orders -> Integration of Maintenance Orders

______________________________________________________________SAP AG 182

SAP-System______________________________________________________________

- Industry-Specific Enhancements -> SAP for Industrial Machinery & Components -> MaintenanceOrders in SAP APO

1.2 SCM-BAS SCM Basis

1.2.1 SCM-BAS-AMO Alert Monitor

1.2.1.1 Alert Determination in the Background (New)

Use

As of SAP SCM 4.1 you can perform alert determination in the background. This enables you to schedulealert determination by the system according to the selected overall alert profile at a specific point in time(for example, in the morning before the working day begins). This means that you gain a rapid overviewof the alert situation, without any waiting time or losses in performance.

To configure alert determination in the background, the following steps are necessary:

- You schedule report /SAPAPO/READ_ALERTS_BATCH as a background job.

- You adapt one of your assigned overall alert profiles (from your favorites) for alert determination inthe background. On the selection screen for the Alert Monitor, choose Goto -> AlertDetermination in the Background.

See also

For more information, see the SAP Library under SCM Basis -> Alert Monitor -> Alert Determination inthe Background.

For information on other changes in the Alert Monitor, see Changes in the Alert Monitor.


Use


The Alert Monitor is available in SAP Advanced Planning and Optimization (SAP APO), and also inother components, such as in Inventory Collaboration Hub (ICH). As of SAP SCM 4.1, you can accessthe Alert Monitor in the SAP area menu under SCM Basis.

______________________________________________________________SAP AG 183

SAP-System______________________________________________________________
















1.2.1.3 Target Stock Level in Production Planning and Detailed Scheduling(PP/DS) (New)

Use

As of SAP SCM 4.1 you can also use target stock level methods in PP/DS.

______________________________________________________________SAP AG 184

SAP-System______________________________________________________________

In heuristic-based procurement planning with the standard heuristic SAP_PP_002 (Planning StandardLots) the following statistical target stock level methods, which you set in the location-dependent productmaster, are observed:

- Target Days' Supply from Product Master ' '

- Target Stock Level Equals Maximum Stock Level + safety stock (4)

- Maximum of Maximum Stock Level/Target Days' Supply (5)

- Sum of Maximum Stock Level/Target Days' Supply (6)

- No Target Stock Level (7)

You can be informed by means of an alert when stock falls below or exceeds the target stock level.

See also

For more information see the SAP Library for SAP Advanced Planning and Optimization (SAPAPO) under Production Planning and Detailed Scheduling (PP/DS) -> PP/DS Process -> BasicFunctions -> Safety and Target Stock Level Planning in PP/DS and the Release Note InventoryAlerts in PP/DS.

1.2.2 SCM-BAS-PSM Planning Service Manager

1.2.2.1 Planning Service Manager (New)

Use

The Planning Service Manager (PSM) is a tool that you can use to carry out automated planning tasks.You can group various planning tasks, such as forecasting, replenishment planning, and the TransportLoad Builder (TLB) in one planning profile. When you execute a planning profile, all planning tasks inthe profile are executed and the results are saved.

The PSM carries out planning tasks using planning services. Examples of planning services are: Forecast,replenishment, and TLB services. The planning services use data managers to access master data,transaction data, (such as orders, time series, or stock), alerts and all other data. The storage service savesnew and modified data to the database and clears the data manager buffers. The PSM and planningservices write application logs.

The Parallel Processing and Package Creation functions enable the PSM to carry out performantprocessing of large data quantities. You can set this function in process profiles, which you can assign toprocess blocks of a planning profile. You can define selections and planning versions in the processblocks. The list of planning services to be executed is assigned to the process block.

______________________________________________________________SAP AG 185

SAP-System______________________________________________________________

The PSM is an SCM Basis tool that can be used by various applications. The relevant applicationprovides planning services and service profiles for the PSM. Every planning service can have a serviceprofile where you can specify parameters (such as model, planning version, and time series) that youwant the system to consider during the planning run.


There are three IMG activities for the PSM:

- Define Process Profile

- Define Storage Service Profile

- Define Planning Profile

See also

For more information, see Planning Service Manager in the SCM Basis area of the SAP Help Portal.

1.2.3 SCM-BAS-BIF Business Interface Layer

1.2.3.1 Validation (Enhanced)

Use

SAP ICH performs a technical and a business validation on XML messages as standard. The technicalvalidation investigates the structural consistency of the messages. The business validation checks whethera document contains all data required for a specific business process in SAP ICH. As of SAP ICH 4.1,you can specify which business validation checks SAP ICH performs on a document and how SAP ICHhandles documents that contain errors. For more information, see the Implementation Guide (IMG) forValidation.

______________________________________________________________SAP AG 186

SAP-System______________________________________________________________

1.3 SCM-FRE Forecasting and Replenishment

1.3.1 SAP Forecasting and Replenishment (New)

Use

As of SAP SCM 4.1 you can use SAP Forecasting and Replenishment (SAP F&R). The aim of SAP F&Ris to optimize the internal logistics of retail companies by making the replenishment process significantlymore efficient.

In particular, SAP F&R supports you in achieving the following goals:

- Reduce surplus stock in distribution centers and stores

- Reduce stockouts in distribution centers and stores

- Reduce the large amount of manual work that is currently required through highly automatedreplenishment planning in stores and distribution centers

- Increase the transparency of the supply chain through effective analyses

SAP F&R provides the following processes to enable you to achieve these goals:

- The automatic replenishment process includes the manual creation, checking and modification ofautomatically created order proposals.

- The analysis process is used to check the results of the automatic replenishment process on the basisof historical data for a certain period. The results of this process are key figures that indicate thequality of the replenishment calculation.

- The connection process provides a link to adjoining systems inside and outside the company. Youimport external data that SAP F&R uses for automatic replenishment calculation.

Note:

- You can only export order proposals. You can convert exported order proposals into purchase ordersin follow-up systems.

See also

For more information, see the SAP Library under SAP Forecasting and Replenishment.

1.3.2 F&R Optimization Process

Use

As of SAP SCM 4.1 you can optimize net requirement quantities in SAP F&R. Using requirementsquantity optimization, you can optimize your net requirements to cover logistic requirements or to reducecosts. Optimization comprises:

______________________________________________________________SAP AG 187

SAP-System______________________________________________________________

- Calculation of article-specific minimum order quantities

- Determination of the units of measure to be used for rounding and ordering. You can definerounding profiles and unit of measure groups for source and target locations. In addition, you canenter a fixed order unit for each location product and source location and choose whether this unit ofmeasure alone is used for optimization and ordering or whether all the units defined by the unit ofmeasure groups are used.

- Rounding of quantities to multiple logistical units. Using the rounding type you can choose whetherthe analysis of the rounding rule relates to individual logistical units or to the total requirementsquantity.

- Parameters to define capital lockup costs (for example, storage costs and interest charges) andpurchase order costs. These are compared during capital lockup optimization.

- A minimum restriction check and an additional restriction check. In the minimum restriction check,the system checks whether an order proposal fulfills vendor-specific minimum order quantities for acertain restriction category, such as, unit of measure, weight or price. In the additional restrictioncheck, the system can check another restriction category, guarantee multiples or take account ofdiscount scales.


In Customizing you define the profile for capital lockup optimization. You can also make specificsettings for location-wide optimization in the requirements quantity optimization profile.

1.3.3 SCM-FRE-MD Master Data

1.3.3.1 F&R Master Data (New)

Use

As of SAP SCM 4.1 you can edit the following master data in SAP Forecasting and Replenishment (SAPF&R):

- Product

- Location product

- Product hierarchy

- Location

- Location group

- Supply network

______________________________________________________________SAP AG 188

SAP-System______________________________________________________________

- Calender

- Procurement cycle (profile)

SAP F&R uses master data in all functions.

See also

For more information, see the SAP Library under Forecasting and Replenishment -> Master Data.

1.3.4 SCM-FRE-IF Interfaces

1.3.4.1 SCM-FRE-IF-FRP Interfaces from and to FRP

1.3.4.1.1 F&R Interfaces (New)

Use

As of SAP SCM 4.1 you can use interfaces in SAP Forecasting and Replenishment (SAP F&R). Theinterfaces are used to link to other systems. SAP F&R uses the connection to exchange data. You have toorganize and control the import of data on the sending side (for example, using background jobs). SAPF&R cannot request the data.

SAP F&R supports connection to the following systems:

- SAP Master Data Management (MDM)

- Point of Sale (POS)

- Logistics Execution (LE)

- Inventory Management

- Merchandise and Assortment

- Purchasing

- Store retailing system

- Space management: Receives shelf data from a space management solution

- Promotion Planning: Receives planned promotions (demand influencing factors)


- An initial data transfer is provided for master data, historical sales or consumption data, demandinfluencing factors and stock data.

- Master data that is created or changed in SAP F&R is not transported to follow-up systems.

See also

For more information, see the SAP Library under SAP Forecasting and Replenishment -> Interfaces.

______________________________________________________________SAP AG 189

SAP-System______________________________________________________________

1.3.5 SCM-FRE-TSM Time Series Management

1.3.5.1 F&R Transaction Data (New)

Use

As of SAP SCM 4.1 you can use transaction data. Transaction data is part of the master data which itdescribes in more detail. For example, transaction data can be sales histories or forecasts for certainproducts.

Transaction data includes:

- Order proposals

- Time series (such as sales histories, forecasts)

SAP F&R requires transaction data as the basis for calculating the following processes:

- Forecast

- Automatic replenishment

- Analyses

Furthermore, SAP Forecasting and Replenishment (SAP F&R) uses transaction data to visualize processdevelopments in the Replenishment Workbench.


SAP F&R needs transaction data to calculate replenishment. You can only import time series using therelevant interfaces; you cannot create time series manually in SAP F&R. SAP F&R creates orderproposals in the forecasting and replenishment calculation. You can export these to follow-up systemsusing the interface.

To use transaction data in SAP F&R, you need TSDM (Time Series Data Management) and ODM (OrderData Management) from SAP SCM 4.1.


To use time series data in SAP F&R, you need to make the settings in Customizing for the time seriesprofile. SAP F&R provides predefined time series profiles that you can use, enhance or modify.

See also

For more information, see the SAP Library under:

- Forecasting and Replenishment -> Transaction Data.

- Forecasting and Replenishment -> Interfaces-> Interface Processing-> Incoming Transaction Data.

- Forecasting and Replenishment -> Interfaces-> Interface Processing-> Outgoing Transaction Data.

______________________________________________________________SAP AG 190

SAP-System______________________________________________________________

1.3.6 SCM-FRE-FRP FRP Functions

1.3.6.1 F&R Processor

Use

As of SAP SCM 4.1 you can calculate automatic replenishment in SAP Forecasting and Replenishment(SAP F&R). Automatic replenishment is a background process in which future demand for a product iscalculated using statistical methods. The F&R Processor anaylzes the time series required for statisticalmethods. You can adjust unusually high values (outliers) and replace stockouts with mean values. SAPF&R does not save the corrections you make to time series. SAP F&R saves the calculated replenishmentquantities in order proposals in order proposal management.

Replenishment quantities can be calculated automatically at product/store level or at product/distributioncenter level. Displaying exceptions ensures greater transparency in automatic replenishment.


To execute the F&R Processor you have to schedule a daily background job. You must reserve sufficienthard disk space for each location. You assign the hard disk space using defined server groups.


In Customizing you define:

- The criteria for how the system calculates order proposals and settings for the recognition ofexceptions

- The technical settings for the processing of locations by the F&R Processor (for example, theassignment of reserved hard disk space and parallel processing)

See also

For more information, see the SAP Library under SAP Forecasting and Replenishment -> F&RProcessor.

1.3.7 SCM-FRE-OPM Order Proposal Management

1.3.7.1 Order Proposal Management (New)

Use

As of SAP SCM 4.1 you can use order proposal management in SAP F&R. Order proposal managementincorporates the management of the results from the replenishment calculation and the release process forthe order proposals created in the requirement quantity optimization.

Order proposal management cannot perform the following functions:

- An open-to-buy function

______________________________________________________________SAP AG 191

SAP-System______________________________________________________________

- A release strategy (such as in purchasing in SAP R/3)

- A workflow for order proposals that are not released

- A random bundling or splitting of existing order proposals (this can only be performed on the basisof the optimization criteria).

See also

For more information, see the SAP Library under SAP Forecasting and Replenishment -> OrderProposal Management.

1.3.8 SCM-FRE-DIF Demand Influencing Factor

1.3.8.1 Demand Influencing Factors (New)

Use

As of SAP SCM 4.1, SAP Forecasting and Replenishment (SAP F&R) provides a Demand InfluencingFactors (DIF) module allows you to take special situations and external events into account whenforecasting product demand. Such situations are user-defined, and could include promotions, holidays,summer vacation time, sports events, and weather-related incidents (for example, snow storms or heatwaves). Each DIF can have one or more DIF occurrences (specific instances when the event occurs).Most DIF occurrences have a valid-from and valid-to date; for example, DIF "Christmas Holiday" canhave a DIF occurrence "Christmas Holiday 2004" that is valid from 11/26/2004 to 12/24/2004. However,other occurrences may have only a valid-from date (for example, inventory clearance prices).

The DIF module includes the following features:

- The DIF Workbench provides all the features and functions for managing DIFs. A navigation treedisplays all DIF objects on the left side of the screen. When you select a DIF (for example, SuperBowl), the right side of the screen displays a list showing all occurrences for that DIF. Below that,the system shows any exceptions that may require user intervention. An example might be afirst-time occurrence of a DIF: since it has not previously occurred, there is no history on which thesystem can predict future impact. Errors in inbound data transmission also cause exceptions toappear.

- You can use sales price information or time series data stored in SAP F&R as DIFs.

- You can apply correction factors to the demand forecast results. These can only be multiplicativefactors; absolute values are not supported.

- The forecast calculation can automatically correct outliers (exceptionally high or low values). Insome cases, a DIF occurrence could cause a spike in demand that appears to be an outlier. You cansuppress outlier correction for time periods that contain a DIF occurrence.

- DIF occurrences can be active or inactive. Inactive DIF occurrences are ignored by the forecastcalculation. If you are not certain whether an event will occur, you can make the DIF inactive, thenreactivate it when the situation is resolved.

- You can define rules for handling overlapping DIF occurrences.

______________________________________________________________SAP AG 192

SAP-System______________________________________________________________

- You can add a memo to a DIF occurrence to provide additional detail about an incident (forexample, a temporary store closing due to storm damage).

- For new store openings, where no historical data exists for predicting a trend, you can define areference store. The system can use the historical data from the reference store to forecast demandfor the new store. You can also define reference products.

- An inbound interface allows you to transfer data from an external source (such as promotionmanagement systems, planning systems, or other DIF provider) to the SAP F&R engine. You canmodify this data as necessary, such as applying a scaling factor to the incoming data. You can alsoopt to prohibit changes to incoming data or selectively authorize who can and cannot make changes.

- Different types of DIFs are supported, such as Boolean DIFs that have discrete occurrences overtime (for example, promotions or holidays) and metric DIFs that have a specific value over time (forexample, sales prices).

- DIF data that is no longer needed can be reorganized (deleted from the database).

1.3.9 SCM-FRE-ANA Analyses

1.3.9.1 Forecasting & Replenishment Analytics 3.52 (New)

Use

As of SAP SCM 410, for Forecasting & Replenishment, you can perform analytics using the followingqueries in SAP BW:

- Stock Development Report. This query is used to analyze the development of the stock value for aproduct location combination or hierarchical level for a given period of time. You can drill down toinclude additional information as well as filter the information in the query by the followingcharacteristics: location type , merchandise category, replenishment planner, ABC indicator, andselling class.

- Gross Margin Return on Investment Report. This query is used to analyze the development of thestock value for a product location combination or hierarchical level, for a given period of time andother important key performance indicators (KPIs) like the gross margin return on investment,inventory turns, and the gross margin percentage. You can drill-down to include additionalinformation, as well as filter the information in the query by the following characteristics:merchandise category (material group), replenishment planner, ABC indicator, and selling class.

______________________________________________________________SAP AG 193

SAP-System______________________________________________________________

- Replenishment Exceptions. This report provides an overview of the quantity, frequency, and typesof the different exceptions reported by the replenishment and forecasting processes. The informationin the report is available at the lowest level of detail by exception message class, exception number,and the date of creation.

- Dead Stock Report. Provides a list of location/product combinations where the stock is greater thanzero and no goods issues exist for several months in the past. The stock information in this reportrepresents obsolete or "dead" stock, which impacts the company's cash flow and profitability in anegative way. A replenishment manager can use the report to decide if the product should bediscontinued, marked down, or removed from the location.

- Variances Dynamic versus Static Minimum Stock. This report provides a list of instances in whichthe static and the dynamic minimum stock for a product/location differ from one another.

- Order Proposal Level of Automation Report. This report shows the number of generated orderproposals (OPs) per day, and the proportion of these OP line items that could be releasedautomatically (level of automation).

These queries are available as of SAP BW 3.52.

See also

For more information please see the content documentation of SAP BW.

1.3.10 SCM-FRE-RWB Planning Workbench

1.3.10.1 Replenishment Workbench (New)

Use

The results of the automatic replenishment processes for stores and distribution centers are checked,controlled and adjusted in the Replenishment Workbench. These results include exceptions and orderproposals that SAP F&R was not able to release automatically during the automatic replenishmentprocess. You can also create manual order proposals and adjust master data that is relevant for planning.

You have already defined the release conditions (exceptions) in order proposal management.

Exceptions could occur due to errors in the following processes:

- Interface processing

- Automatic replenishment

- Analyses in SAP BW

- Requirement quantity optimization

______________________________________________________________SAP AG 194

SAP-System______________________________________________________________

- Order proposal release management

See also

For more information, see the SAP Library under SAP Forecasting and Replenishment -> ReplenishmentWorkbench.

1.3.10.2 Replenishment Workbench for Stores (New)

Use

As of SAP SCM 4.1, store managers and replenishment planners can use the Replenishment Workbenchfor Stores to replenish their stores decentrally. As it is a Web-based component, it is possible to accessthe workbench over the Internet.

See also

For more information, see the SAP Library under SAP Forecasting and Replenishment -> ReplenishmentWorkbench.

1.3.11 SCM-FRE-EXC Exception Handling

1.3.11.1 Exception Workbench

Use

As of SAP SCM Release 4.1, you can use the Exception Workbench in Forecasting andReplenishment. The Exception Workbench is a tool that grants different roles or users (for example, areplenishment specialist or a system administrator) access to the F&R exceptions that the system hasautomatically generated in various F&R business processes. When the system creates an F&R exception,it assigns the exception to the objects (for example, locations products, order requests) and the businessareas (for example, forecasting, replenishment) to which it belongs. Different roles and users may beinterested in different exceptions. It is therefore possible to assign exceptions from different businessareas to different roles/users. Unlike in the subscription dialog, it is possible to select exceptionsaccording to business criteria (for example, business objects and business areas) and technical criteria (forexample, priority, creation date) in the selection screen for the Exception Workbench.

The system structures the business objects from the selection results, which are linked to the exceptions,in groups in a navigation tree. Users can adjust the navigation tree to suit their particular needs. When anexception is selected, by double-clicking in the navigation tree, the system displays it in the SAP ListViewer. The user can easily distinguish between important exceptions and those that are less importantand can choose to hide exceptions with a low priority. The status of an exception can be changed in theException Workbench. If users are not interested in certain exceptions for a brief time, they cantemporarily hide the exceptions until a resubmission date that they define themselves. If F&R exceptionsare relevant for third parties (for example, users who do not use Forecasting and Replenishment), theuser can forward exceptions by email.

______________________________________________________________SAP AG 195

SAP-System______________________________________________________________


A data transfer is not required.


We recommend scheduling a reorganization report that the system runs daily. The reorganization reportdeletes exception objects that have status Processed or whose validity period has expired. You can set thevalidity period of F&R exception objects for each customer in Customizing.

1.4 SCM-ICH Inventory Collaboration Hub

1.4.1 Audit Trail (New)

Use

SAP ICH 4.1 can log all changes for orders, key figures, and stock automatically. Audit trail enters thetime a change was made, who made the change, and the value. For audit trail, you need to have set theTracking indicator for the time series type in Customizing under Configure Time Series DataManagement.

1.4.2 Demand Monitor (New)

Use

As of SAP ICH 4.1, the Demand Monitor is available for supplier collaboration. The Demand Monitor isa function on the Web UI of SAP ICH that displays and compares the customer's firm or planned netdemands and the supplier's firm or planned receipts. The Demand Monitor calculates the absolute and thepercentage deviations between the customer and the supplier data and highlights periods - depending onthe deviations - in color. Both the customer and the supplier have a common view of the planningsituation and gain a quick overview of critical situations. This is the basis for any adjustment to theplanning of the supplier capacity within a dynamic replenishment scenario. For more information, see theSAP Inventory Collaboration Hub (SAP ICH) component.

______________________________________________________________SAP AG 196

SAP-System______________________________________________________________

1.4.3 Personalization (New)

Use

As of SAP ICH 4.1, you can define user-specific settings for the table display on the Web user interfaceunder Personalization.

1.4.4 Purchase Orders in Supplier Collaboration (New)

Use

As of SAP ICH 4.1, functions are available for processing purchase orders that support the followingscenarios in supplier collaboration:

- Purchase order collaborationOn the Web UI of SAP ICH, the supplier can confirm a purchase order that the customer has sentwith an electronic message from his or her backend system to SAP ICH. The supplier can also sendpurchase order confirmations from his or her backend system to SAP ICH.

- Supplier-managed inventory with purchase ordersOn the Web UI of SAP ICH, the supplier can create purchase orders for the receipts that he or shehas planned for the customer within an SMI scenario in SAP ICH. The customer transfers thepurchase orders from SAP ICH to his or her backend system. These purchase orders are used thereas firm receipts in the customer's planning. In order that the purchase orders are also available asfirm demands in the supplier's backend system, the customer can also send purchase orders fromSAP ICH to the supplier's backend system.

SAP ICH sends and receives purchase order data - depending on the scenario - via SAP XI using variousXML messages. For more information, see the SAP Inventory Collaboration Hub component underPurchase Orders in Supplier Collaboration.

______________________________________________________________SAP AG 197

SAP-System______________________________________________________________

1.4.5 SCM-ICH-REL Scheduling Agreement Release

1.4.5.1 Release Processing (Enhanced)

Use

As of SAP ICH 4.1, the following enhancements are available for release processing:

- Comparison of scheduling agreement releasesAs supplier, you are able to compare any two scheduling agreement releases; for example, thecurrent scheduling agreement release with an old scheduling agreement release. You can use thisfunction to quickly identify changes to your customer's demand. The comparison is performed atschedule line level and determines date and quantity changes.

- Navigation to the inventory monitorYou can navigate from release processing to the inventory monitor.

1.4.6 SCM-ICH-ASN Advanced Shipping Notification

1.4.6.1 ASN Processing (Enhanced)

Use

As of SAP ICH 4.1, the following enhancements are available in ASN processing:

- Additional fieldsThere are fields for additional data in the ASN header and in the ASN items. The ASN header nowcontains the full ship-from and ship-to addresses or the unloading point, for example. In the ASNitems, you see the change number, the batch number, shelf life data, or dangerous goods data, forexample.

- PackingAs supplier, you are able to pack the products of an ASN on single or multiple levels. Packingmeans creating handling units (HUs). You specify which product quantities are packed using whichauxiliary packaging materials and into which packaging materials. In addition, you can print labelsfor the handling units. In manual packing, you form the HUs manually. Automatic packing is basedon predefined packaging specifications that you (or your customer) have created in master data

______________________________________________________________SAP AG 198

SAP-System______________________________________________________________

maintenance on the Web user interface of SAP ICH. For more information, see the ImplementationGuide (IMG) for ASN Processing under Packing.

- Due list with purchase orders and scheduling agreement releasesUntil now, a due list has been available for ASNs that contains planned receipts and draft ASNs.You use this due list in the supplier-managed inventory scenario. You generate ASNs based onplanned receipts in the due list. As of SAP ICH 4.1, another due list is available that contains thecustomer's purchase orders and scheduling agreement releases with open demands. You use this duelist to create ASNs based on purchase orders and scheduling agreement releases. For moreinformation, see the Implementation Guide (IMG) for ASN Processing under Determine DueScheduling Agreement Releases.

- Allow partial goods receipt for ASN itemsIn SAP ICH 4.0, if you, as customer, transferred a partial goods receipt for an ASN item to SAPICH, SAP ICH closed the ASN item automatically. In SAP ICH 4.1, you can specify whether ornot SAP ICH closes the ASN item in the case of a partial goods receipt. For more information, seethe Implementation Guide (IMG) for ASN Processing under Allow Partial Goods Receipt for ASNItems.

- Close ASN items based on cumulative received quantitiesFor release processing, you can specify that SAP ICH closes ASN items based on the cumulativereceived quantity that you transfer to SAP ICH in the scheduling agreement release(DeliveryScheduleNotification). This is an alternative to the standard process that we recommend.In the standard process, SAP ICH closes ASNs based on ReceivedDeliveryNotifications that yougenerate in SAP R/3 on goods receipt based on the inbound delivery and transfer to SAP ICH. Formore information, see the Implementation Guide (IMG) for ASN Processing under Close ASNItems Based on the Cumulative Received Quantity.

- NotesYou can create notes at header level. For more information, see the release note for Notes.

- ValidationYou can specify how SAP ICH validates ASNs and how it handles ASNs that contain errors. Formore information, see the release note for Validation.

1.4.6.2 Notes (New)

Use

As of SAP ICH 4.1, you can create notes for the following objects on the Web user interface:

- Advanced shipping notifications (ASNs)

- Alerts

______________________________________________________________SAP AG 199

SAP-System______________________________________________________________

- Selected key figures in the planning grid of the inventory monitor (for example, demands)

You can create a user-defined text for a note. Other users are able to see this text. You can classify notesusing predefined reason codes. For more information, see the Implementation Guide (IMG) for Notesunder Define Reason Codes for Notes.

1.4.6.3 Validation (Enhanced)

Use

SAP ICH performs a technical and a business validation on XML messages as standard. The technicalvalidation investigates the structural consistency of the messages. The business validation checks whethera document contains all data required for a specific business process in SAP ICH. As of SAP ICH 4.1,you can specify which business validation checks SAP ICH performs on a document and how SAP ICHhandles documents that contain errors. For more information, see the Implementation Guide (IMG) forValidation.

1.4.7 SCM-ICH-IMO Inventory Monitor

1.4.7.1 Inventory Monitor (Enhanced)

Use

As of SAP ICH 4.1, the following enhancements are available in the inventory monitor:

- New inventory alertsUntil now, only alerts for critical situations for the projected stock were available (falling below theminimum stock, exceeding the maximum stock, and stockout). As of SAP ICH 4.1, there are also

______________________________________________________________SAP AG 200

SAP-System______________________________________________________________

corresponding alert types for the warehouse stock. In addition, there are more alert types for theprojected stock. They provide information that the critical situation for the projected stock arisesduring the lead time of a product. Therefore, the supplier is no longer able to remove the criticalsituation using the means of transport that is normally used.

- Projected stockUntil now, only one default formula was available for calculating the projected stock. It applied toall business partners and location products. As of SAP ICH 4.1, you can also define your ownformulas in which you can take account of other stock types and key figures. You can also usedifferent formulas for different business partners and location products. For more information, seethe Implementation Guide (IMG) for Projected Stock.

- Average demandA function is available in the planning grid for averaging demands. As supplier, you can use thisfunction to average demands and to perform planning based on the average demand. You use thisfunction if the customer's demand data varies greatly or is incorrect.

- Propose planned receiptsUntil now, you, as supplier, were only able to enter planned receipts manually in the planning grid.SAP ICH 4.1 can also propose planned receipts. SAP ICH determines the planned receiptsaccording to a reorder point method. If the projected stock in a period falls below the minimumstock, SAP ICH proposes a planned receipt with which the projected stock of the period reaches themaximum stock.

- MultisourcingTo support suppliers during planning who are able to deliver a product to the customer from severalship-from locations, the following enhancements are available:

- You are able to assign a supplier several ship-from locations. Until now, only one ship-fromlocation was possible in the inventory monitor.

- You are able to call the inventory details for several products in the inventory overview andgroup the data in the planning grid according to various predefined criteria.

- Audit trailSAP ICH is able to record all changes to the key figures and stock in the planning gridautomatically. For more information, see the release note for Audit Trail.

- NotesYou can create notes for the fields in the planning grid. For more information, see the release notefor Notes.

______________________________________________________________SAP AG 201

SAP-System______________________________________________________________

1.4.7.2 Notes (New)

Use



- Alerts



1.4.8 SCM-ICH-REP ICH Reporting

1.4.8.1 Alert Monitor (Enhanced)

Use

As of SAP ICH 4.1, the following enhancements are available in the Alert Monitor:

- Alert statisticsIn the Alert Monitor, a statistical view is available that groups the alerts according to locationproduct, alert type, and alert priority. The statistics support specific processing of alerts when alertsoccur frequently.

- Alert-based ratingAlert-based rating is a function you can use to evaluate business partners, locations, or productsbased on alerts. You can perform supplier evaluation, for example. Depending on your evaluationcriteria, you can use alert-based rating to specifically evaluate the history of specific alert types. Youcan weight the alerts with different scores depending on the alert type, the alert priority, and the alerttime. For more information, see the Implementation Guide (IMG) for Alert-Based Rating.

- NotesYou can create notes for alerts. For more information, see the release note for Notes.

______________________________________________________________SAP AG 202

SAP-System______________________________________________________________

1.4.9 SCM-ICH-DIO Inbound/Outbound Data Processing

1.4.9.1 Inbound and Outbound Messages (Enhanced)

Use

As of SAP ICH 4.1, the following enhancements are available for inbound and outbound XMLmessages:

- Restrict log and alertsIf SAP ICH was able to process an inbound or outbound XML message successfully or with errors,SAP ICH generates an alert and an entry in the application log as standard. As of SAP ICH 4.1,you can specify, depending on the message type, that SAP ICH only logs alerts and log entries inthe case of errors or does not log them at all. A restricted log is recommendable for performancereasons, for example. For more information, see the Implementation Guide (IMG) for SAP ICHunder Restrict Log and Restrict Alerts.

- Reset time series for inbound ProductActivityNotificationsYou can specify whether SAP ICH sets all data in a time series to zero and then writes the timeseries values transferred from an inbound ProductActivityNotification to the time series. For moreinformation, see the Implementation Guide (IMG) for SAP ICH under Reset Time Series forInbound ProductActivityNotifications.

- ValidationYou can specify how SAP ICH validates inbound XML messages and how it handles messages thatcontain errors. For more information, see the release note for Validation.

1.4.10 SCM-ICH-AMO Alert Monitor


Use

______________________________________________________________SAP AG 203

SAP-System______________________________________________________________


The Alert Monitor is available in SAP Advanced Planning and Optimization (SAP APO), and also inother components, such as in Inventory Collaboration Hub (ICH). As of SAP SCM 4.1, you can accessthe Alert Monitor in the SAP area menu under SCM Basis.
















______________________________________________________________SAP AG 204

SAP-System______________________________________________________________

1.4.10.2 Alert Monitor (Enhanced)

Use

As of SAP ICH 4.1, the following enhancements are available in the Alert Monitor:

- Alert statisticsIn the Alert Monitor, a statistical view is available that groups the alerts according to locationproduct, alert type, and alert priority. The statistics support specific processing of alerts when alertsoccur frequently.

- Alert-based ratingAlert-based rating is a function you can use to evaluate business partners, locations, or productsbased on alerts. You can perform supplier evaluation, for example. Depending on your evaluationcriteria, you can use alert-based rating to specifically evaluate the history of specific alert types. Youcan weight the alerts with different scores depending on the alert type, the alert priority, and the alerttime. For more information, see the Implementation Guide (IMG) for Alert-Based Rating.

- NotesYou can create notes for alerts. For more information, see the release note for Notes.

1.4.10.3 Notes (New)

Use



- Alerts



______________________________________________________________SAP AG 205

SAP-System______________________________________________________________

______________________________________________________________SAP AG 206

SAP-System______________________________________________________________