release notes for sap supply chain management release sap

158
Release Notes for SAP Supply Chain Management Release SAP SCM 7.0

Upload: others

Post on 19-May-2022

13 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Release Notes for SAP Supply Chain Management Release SAP

Release Notes for SAP Supply Chain Management

Release SAP SCM 7.0

Page 2: Release Notes for SAP Supply Chain Management Release SAP

______________________________________________________________

CopyrightCopyright(c) 2009 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.

Page 3: Release Notes for SAP Supply Chain Management Release SAP

1 SCM Supply Chain Management 11.1 SAP SCM Monitoring with CCMS (Enhanced) 11.2 SCM-APO Advanced Planning and Optimization 31.2.1 Structure Changes in the IMG of SAP APO 31.2.2 SCM-APO-CA APO Cross-Application Components 61.2.2.1 Functions for APO Consignment Vendor-Managed Inventory (New) 61.2.2.2 SCM-APO-CA-CDP Characteristics-Dependent Planning 61.2.2.2.1 CDP: Integration of Orders via APO CIF (Enhanced) 61.2.3 SCM-APO-MD Master Data 71.2.3.1 SCM-APO-MD-PR Product 71.2.3.1.1 Requirements Strategy for Configurable Products (New) 71.2.4 SCM-APO-VS Vehicle Scheduling 81.2.4.1 SCM-APO-VS-INS Interactive VS 81.2.4.1.1 Splitting Stock Transport Requisitions (Enhanced) 81.2.5 SCM-APO-SNP Supply Network Planning (SNP) 91.2.5.1 Low-Level Code Determination (Enhanced) 91.2.5.2 Functions for APO Consignment Vendor-Managed Inventory (New) 101.2.5.3 SCM-APO-SNP-BF Basic Functions 101.2.5.3.1 Supply Network Planning (SNP) Queue Processing (Enhanced) 111.2.6 SCM-APO-SDM Multilevel Supply & Demand Matching 121.2.6.1 SCM-APO-SDM-CTM Capable-to-Match 121.2.6.1.1 Capable-to-Match (CTM) (Enhanced) 121.2.7 SCM-APO-FCS Demand Planning 131.2.7.1 Forecast Release and Consumption with Configuration (New) 131.2.7.2 MLR Forecasting Using POS Data (New) 141.2.7.3 Forecasting Enhancements (Enhanced) 141.2.7.4 Definition of Configuration Schema (Enhanced) 151.2.7.5 SCM-APO-FCS-CFM Customer Forecast Management 161.2.7.5.1 Customer Forecast Management (New) 161.2.8 SCM-APO-SPP Service Parts Planning 171.2.8.1 Location Product Master Data for Service Parts Planning (Enhanced) 171.2.8.2 OEM-Managed Inventory (New) 181.2.8.3 Name of the SPP - Customer View (Internal View) Changed 191.2.8.4 User Interfaces for Service Parts Planning (Enhanced) 191.2.8.5 Worklists for Service Parts Planning (New) 201.2.8.6 Creating Users With SAP NetWeaver Identity Management (New) 221.2.8.7 SCM-APO-SPP-CPD Entry and Maintenance of Historical Data 231.2.8.7.1 Creation of the Demand History (Enhanced) 231.2.8.7.2 Simulations in Service Parts Planning (Enhanced) 241.2.8.8 SCM-APO-SPP-SFC Service Parts Forecast 25

______________________________________________________________SAP AG iii

Release-Informationen Inhaltsverzeichnis SAP AG______________________________________________________________

Page 4: Release Notes for SAP Supply Chain Management Release SAP

1.2.8.8.1 Functions in Forecasting (Enhanced) 251.2.8.9 SCM-APO-SPP-SIP Service Parts Inventory Planning 251.2.8.9.1 Functions for Inventory Planning (Enhanced) 251.2.8.9.2 Functions in Surplus and Obsolescence Planning (Enhanced) 271.2.8.10 SCM-APO-SPP-SDR Distribution Requirements Planning for Service Part 281.2.8.10.1 Functions in Distribution Requirements Planning (DRP) (Enhanced) 281.2.8.10.2 Kit to Stock in Distribution Requirements Planning (DRP) (New) 311.2.8.11 SCM-APO-SPP-SDE Service Parts Deployment 311.2.8.11.1 Functions in Inventory Balancing (Enhanced) 321.2.8.11.2 Multi-Level Priority Tier Processing in Deployment (New) 331.2.8.11.3 Functions in Deployment (Enhanced) 341.2.8.12 SCM-APO-SPP-PWL Worklist 351.2.8.12.1 Roles for Service Parts Planning (Enhanced) 351.2.8.13 SCM-APO-SPP-SFA Service Fill Analysis 351.2.8.13.1 Functions in Reporting and Monitoring (Enhanced) 351.2.8.14 SCM-APO-SPP-INB Inbound Delivery Monitor 371.2.8.14.1 Functions in Reporting and Monitoring (Enhanced) 371.2.8.15 SCM-APO-SPP-SHA Shortage Analysis 391.2.8.15.1 Functions in the Alert Monitor (Enhanced) 391.2.8.15.2 Functions in Reporting and Monitoring (Enhanced) 401.2.8.15.3 Functions in Shortage Analysis 411.2.9 SCM-APO-PPS Production Planning and Detailed Scheduling 431.2.9.1 Order Scheduling for Block Changes (Enhanced) 431.2.9.2 PP/DS Enhancements for the Process Industry 441.2.9.3 SCM-APO-PPS-PPT Product Planning Table 481.2.9.3.1 PPT: Cross-location Planning Chart and Other Enhancements (Enhanced) 481.2.9.4 SCM-APO-PPS-HEU Heuristics 521.2.9.4.1 PP/DS Heuristics in Characteristics-based Cross-location Planning 521.2.9.4.2 PP/DS Deployment Heuristic (New) 541.2.10 SCM-APO-ATP Global Available-to-Promise 561.2.10.1 Backward Consumption (Enhanced) 561.2.10.2 ATP Category (Enhanced) 561.2.10.3 Adoption of Scheduling Results (Changed) 571.2.10.4 Subcontracting in MATP (Enhanced) 571.2.11 SCM-APO-OPT Optimization 58

______________________________________________________________SAP AG iv

Release-Informationen Inhaltsverzeichnis SAP AG______________________________________________________________

Page 5: Release Notes for SAP Supply Chain Management Release SAP

1.2.11.1 SCM-APO-OPT-BF Basic Functions 581.2.11.1.1 Remote Control and Communication Framework (Changed) 581.2.12 SCM-APO-INT Interfaces 581.2.12.1 SCM-APO-INT-MD Master Data 581.2.12.1.1 SCM-APO-INT-MD-CLC Classes and Characteristics 581.2.12.1.1.1 Definition of Configuration Schema (Enhanced) 581.3 SCM-BAS SCM Basis 591.3.1 Structure Changes in the IMG of SCM Basis 591.3.2 SCM-BAS-INT Interfaces 601.3.2.1 SCM-BAS-INT-MD CIF Master Data 601.3.2.1.1 Initial Data Transfer via Core Interface (CIF) (Enhanced) 601.3.3 SCM-BAS-AMO Alert Monitor 611.3.3.1 Alert Monitor (Enhanced) 611.3.4 SCM-BAS-PSM Planning Service Manager 621.3.4.1 Functions for Planning Service Manager (PSM) (Enhanced) 621.3.5 SCM-BAS-TDL Transaction Data Layer 631.3.5.1 Triggers for Service Parts Planning (Enhanced) 631.3.6 SCM-BAS-MD Master Data 631.3.6.1 SAP SCM Basis Monitoring with CCMS (New) 631.3.6.2 SCM-BAS-MD-TL Transportation Lanes, TDL Profile and Planning Cost 641.3.6.2.1 Maintaining Means of Transport (Changed) 641.3.7 SCM-BAS-RCC Remote Control and Communication Framework 651.3.7.1 Remote Control and Communication Framework (Deleted) 651.4 SCM-EWM Extended Warehouse Management 651.4.1 Cross-Docking (Enhanced) 651.4.2 SAP Extended Warehouse Management: Create User (new) 661.4.3 Structure changes in the EWM IMG 671.4.4 Material Flow System (MFS) 711.4.5 Graphical Warehouse Layout (New) 721.4.6 Integration of Production Supply of EWM into Production Planning in ERP 731.4.7 Additional Functions in Radio Frequency (RF) 741.4.8 Additional Functions for Warehouse Order Processing 741.4.9 SCM-EWM-MON Monitoring 751.4.9.1 SAP EWM Monitoring with CCMS (New) 761.5 SCM-EM Event Management 761.5.1 Structure Changes in IMG for SAP Event Management 761.5.2 SAP Business Information Warehouse Interface (Changed) 771.5.3 SAP Object Event Repository Complies with EPCIS 1.0 Specification (New) 78

______________________________________________________________SAP AG v

Release-Informationen Inhaltsverzeichnis SAP AG______________________________________________________________

Page 6: Release Notes for SAP Supply Chain Management Release SAP

1.5.4 Other interfaces 781.5.5 EventCaptureNotification Service (Enhanced) 791.5.6 Poll Service (Enhanced) 791.5.7 Roles for SAP Object Event Repository (New) 811.5.8 Subscriptions (New) 811.5.9 Alternative Display Formats for URNs (Enhanced) 821.5.10 SCM-EM-MGR Event Manager 831.5.10.1 SCM-EM-MGR-EVP Event Processing 831.5.10.1.1 Web Interface (Enhanced) 831.6 SCM-ICH Supply Network Collaboration 841.6.1 Structure Changes in the IMG of SAP SNC 841.6.2 Quick View (New) 871.6.3 Selection Using Product Group and Product Group Type (New) 871.6.4 SCM-ICH-MD Master Data 881.6.4.1 Inventory Management (Changed) 881.6.4.2 Creating Users with Identity Management (New) 891.6.4.3 Location Product Status (Enhanced) 901.6.4.4 Roles (Enhanced) 911.6.4.5 User Administration (New) 921.6.5 SCM-ICH-REL Scheduling Agreement Release 931.6.5.1 New-Note Alerts for SA Releases (Changed) 931.6.6 SCM-ICH-PO Purchase Order and Replenishment Order 941.6.6.1 XML Messages for Delivery Collaboration (Enhanced) 941.6.6.2 Control of Actions for Purchase Order and Replenishment Order (Enhanced) 941.6.6.3 Purchase Order XML Messages (Enhanced) 961.6.6.4 Batches and Configuration in Purchase Order Collaboration (Enhanced) 971.6.6.5 Purchase Order Screens and Replenishment Order Screens (Enhanced) 1001.6.6.6 Due Schedule Lines (Enhanced) 1001.6.6.7 Manufacturer Part Number (New) 1021.6.6.8 Price Confirmation (New) 1021.6.6.9 Technical Basis for Web UI Screens (Enhanced) 1031.6.6.10 Purchase Order Worklist (Enhanced) 1041.6.7 SCM-ICH-ASN Advanced Shipping Notification 1051.6.7.1 XML Messages for Delivery Collaboration (Enhanced) 1051.6.7.2 Due Schedule Lines (Enhanced) 1061.6.8 SCM-ICH-WO Work Order 1071.6.8.1 Batches and Configuration in Work Order Collaboration

______________________________________________________________SAP AG vi

Release-Informationen Inhaltsverzeichnis SAP AG______________________________________________________________

Page 7: Release Notes for SAP Supply Chain Management Release SAP

(Enhanced) 1071.6.8.2 Sending Work Orders to Customer Back-End System (Enhanced) 1101.6.8.3 Splitting of Deliveries (Enhanced) 1111.6.8.4 Work Order Worklist (New) 1121.6.9 SCM-ICH-IV Invoice 1121.6.9.1 Invoice Alerts (New) 1121.6.10 SCM-ICH-IMO Inventory Monitor 1131.6.10.1 Inventory in SMI and Outsourced Manufacturing (Enhanced) 1131.6.10.2 Data in the Min/Max Replenishment Monitor (Enhanced) 1151.6.10.3 Data in the RR Monitor (Enhanced) 1161.6.10.4 Functions in the RR Overview (Enhanced) 1171.6.10.5 Configuring the Replenishment Monitor Overview (Enhanced) 1181.6.10.6 Saving Planning Service Results in the Replenishment Monitors (Changed) 1191.6.10.7 Refresh Concept (Enhanced) 1191.6.10.8 Data Matrix (Enhanced) 1201.6.10.9 Visibility of Location Products (Enhanced) 1211.6.11 SCM-ICH-KNB Kanban 1231.6.11.1 New Selection Parameter for the Kanban Web Screen (Enhanced) 1231.6.12 SCM-ICH-SNI Supply Network Inventory 1231.6.12.1 Inventory in SMI and Outsourced Manufacturing (Enhanced) 1231.6.12.2 Inventory Overview (New) 1261.6.12.3 Data Matrix (Enhanced) 1271.6.12.4 Visibility of Location Products (Enhanced) 1281.6.13 SCM-ICH-FCS Forecast 1301.6.13.1 Visibility of Location Products (Enhanced) 1301.6.14 SCM-ICH-NDC Net Requirements Calculation 1321.6.14.1 Product Allocation (Enhanced) 1321.6.14.2 Minimum and Maximum Lot Size (New) 1331.6.14.3 Two-Level Rounding (New) 1331.6.14.4 Safety Stock Planning (Enhanced) 1341.6.15 SCM-ICH-PRO Promotion Planning 1351.6.15.1 Determining the Promotion ID (Enhanced) 1351.6.16 SCM-ICH-TLB Transport Load Builder 1351.6.16.1 Product Allocation (Enhanced) 1351.6.16.2 Minimum and Maximum Lot Size (New) 1361.6.16.3 Transport Load Building (Enhanced) 1371.6.17 SCM-ICH-DIO Inbound/Outbound Data Processing 1381.6.17.1 SAP SNC Monitoring with CCMS (New) 1381.6.17.2 Inventory in SMI and Outsourced Manufacturing (Enhanced) 1381.6.17.3 Location Product Status (Enhanced) 1411.6.18 SCM-ICH-AMO Alert Monitor 142

______________________________________________________________SAP AG vii

Release-Informationen Inhaltsverzeichnis SAP AG______________________________________________________________

Page 8: Release Notes for SAP Supply Chain Management Release SAP

1.6.18.1 Activation of Alert Types (Changed) 1421.6.18.2 SAP SNC Monitoring with CCMS (New) 1421.6.18.3 Control of Actions for Purchase Order and Replenishment Order (Enhanced) 1431.6.19 SCM-ICH-ERP ERP-SNC Integration 1441.6.19.1 Inventory in SMI and Outsourced Manufacturing (Enhanced) 1441.6.19.2 Purchase Order XML Messages (Enhanced) 1471.6.20 SCM-ICH-FTR File Transfer 1481.6.20.1 File Transfer (New) 148

______________________________________________________________SAP AG viii

Release-Informationen Inhaltsverzeichnis SAP AG______________________________________________________________

Page 9: Release Notes for SAP Supply Chain Management Release SAP

1 SCM Supply Chain Management

1.1 SAP SCM Monitoring with CCMS (Enhanced)

Use

As of SAP NetWeaver 7.0 including SAP enhancement package 1 and SAP Supply Chain Management(SAP SCM) 7.0, the predefined monitor set SAP SCM Monitor Templates in the monitoringarchitecture of the Computing Center Management System (CCMS) provides additional monitoringtemplates and monitoring tree elements. The CCMS Monitoring Architecture is a framework available inSAP NetWeaver into which monitoring and administration functions can be added.

The SAP SCM Monitor Templates monitor set includes the following:

- APO Monitor (enhanced)The APO Monitor allows you to check the following:

- SAP Core Interface (CIF)

- qRFC consumption of planned independent requirements (PIR)

- CIF queues with inbound and outbound CIF queues for transactional RFCs and queued RFCs

- SNP Monitor for SNP master data and time series (new)

- EWM Monitor (new)The EWM Monitor allows you to monitor inbound and outbound queues for external and internalmessage processing.

- Event Manager Monitor

- F&R Monitor

- SCM Optimizer Monitor

- SNC Monitor (new)For each SAP SNC client of the system landscape, the SNC Monitor allows you to monitor inboundand outbound message processing of XML messages.

- liveCache Monitor

Effects on System Administration

To use the SCM Monitor Templates monitor set as a template for your own monitor, copy the desiredmonitor and adapt it to your needs. If you run CCMS from a central system to monitor your systemlandscape, set up system connections with your SAP SCM systems. For more information, see the SAPNetWeaver documentation on SAP Help Portal at http://help.sap.com under SAP Library -> SAPNetWeaver Library -> SAP NetWeaver by Key Capability -> Solution Life Cycle Management byKey Capability -> Solution Monitoring -> Monitoring in the CCMS.

______________________________________________________________SAP AG 1

SAP-System______________________________________________________________

Page 10: Release Notes for SAP Supply Chain Management Release SAP

______________________________________________________________SAP AG 2

SAP-System______________________________________________________________

Page 11: Release Notes for SAP Supply Chain Management Release SAP

1.2 SCM-APO Advanced Planning and Optimization

1.2.1 Structure Changes in the IMG of SAP APO

Use

As of SAP SCM 7.0, the structure of the Implementation Guide (IMG) for SAP APO has changed. Youmust regenerate the project IMGs to transfer these changes.

New IMG Structure Nodes and IMG Activities

- IMG for Service Parts Planning (SPP)

- Basic Settings -> Settings for User Interfaces -> Define User-Specific andApplication-Specific Display of the BOD

- Distribution Requirements Planning (DRP) -> Define Reasons for DRP Locks

- Distribution Requirements Planning (DRP) -> Define Profile for Repairable ReturnsForecast Based on Time Series

- Deployment -> Define Reasons for Deployment Locks

- Inventory Balancing -> Define Service Profile for Inventory Balancing of UnserviceableProducts

- Node under Monitoring: Overdue Orders and Schedule Lines

- Monitoring -> Service Fill Monitor -> Select ATP Categories for the Service Fill Monitor

- Monitoring -> Service Loss Analysis -> Define Processing Order for Overdue ServiceLoss Reasons

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdI: Define Filter forBOD Display

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for Forecasting-> BAdI: Change Final Forecast

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for InventoryPlanning -> BAdI: Safety Stock Adjustment at Parent Location for Push Deployment

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for InventoryPlanning -> BAdI: Define Logic for Proposed Surplus Approval

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for InventoryPlanning -> BAdI: Define Sorting for Surplus Disaggregation

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for DistributionRequirements Planning (DRP) -> BAdI: Determine Additonal Quantities forPeriod-Based Planning

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for DistributionRequirements Planning (DRP) -> BAdI: Determination of Preferred Location of aVLCO

______________________________________________________________SAP AG 3

SAP-System______________________________________________________________

Page 12: Release Notes for SAP Supply Chain Management Release SAP

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for DistributionRequirements Planning (DRP) -> BAdI: Definition of the Latest GR Time of ReleasedDelivery Schedule Lines

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for DistributionRequirements Planning (DRP) -> BAdI: Customizing of "External Procurement -Delivery Maintenance" Screen

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for Deployment-> BAdI: Define Limits for Express Shipments

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for Deployment-> BAdI: Determination of Parameters for the Time-Related Supply Limit

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for InventoryBalancing -> BAdI: Define if Pull Deployment is a Valid Alternative to Inv. Balancing

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for InventoryBalancing -> BAdI: Determine Excess and Shortage Quantities for UnserviceableStock

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for InventoryBalancing -> BAdI: Determine STR Quantities for Unserviceable Stock

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for InventoryBalancing -> BAdI: Determine Sublocations and Versions for Unserviceable Stock inSTRs

- Business Add-Ins (BAdIs) for Service Parts Planning (SPP) -> BAdIs for Monitoringand Reporting -> BAdI: Define System Behavior if Orders/Schedule Lines areOverdue

- Node under Business Add-Ins (BAdIs) for Service Parts Planning (SPP): BAdIs forCustomer's Worklist

- IMG for Global Available-to-Promise (Global ATP)

- Node Influence RBA Substitutions for Requirement Groups under Enhancements ->Rules

- Node Confirmations under Enhancements

- Enterprise Services

- Business Add-Ins (BAdIs) for Enterprise Services (APO) -> Service Parts Planning ->Service Part Order History -> BAdI for ProductActivityNotification_In

- Node under Business Add-Ins (BAdIs) for Enterprise Services (APO) -> Service PartsPlanning: BAdIs for Mapping Master Data in XML Messages

- Business Add-Ins (BAdIs) for Enterprise Services (APO) -> Supply and DemandMatching -> Material Supply and Demand View

- IMG for Integration with SAP Components

- Integration via APO Core Interface (CIF) -> Basic Settings for Data Transfer -> CIF ErrorHandling -> Activate CIF Incremental Load

- Integration via APO Core Interface (CIF) -> Application-Specific Settings and

______________________________________________________________SAP AG 4

SAP-System______________________________________________________________

Page 13: Release Notes for SAP Supply Chain Management Release SAP

Enhancements -> Settings for Publication of Characteristics of Transactional Data ->Remove Configuration Before Transfer to ERP

- Integration via APO Core Interface (CIF) -> Application-Specific Settings andEnhancements -> Settings for Publication of Characteristics of Transactional Data ->BAdI: Adding Exception for Removing Configuration

- IMG for Demand Planning

- Customer Forecast Management -> Define Profiles and Settings for Customer ForecastManagement

- Business Add-Ins (BAdIs) -> Customer Forecast Management -> BAdI: Data Release toSpecified Destination

- Business Add-Ins (BAdIs) -> Customer Forecast Management -> BAdI: Processing ofSingle Inbound Bucket

Changed IMG Activities

- IMG for Master Data

- Classification and Configuration -> Define Configuration Schema (CDP orVariant Configuration)

- IMG for Basic Settings

- Define Configuration Schema (CDP or Variant Configuration)

- IMG for Global Available-to-Promise (Global ATP)

- General Settings -> Maintain Category

- Product Allocation -> Maintain Product Allocation Group

- IMG for Supply Network Planning (SNP)

- Basic Settings -> Maintain Global SNP Settings

- IMG for Service Parts Planning (SPP)

- Deployment -> Define Service Profile for Deployment

Transferred IMG Activities

...

Deleted IMG Activities

- IMG for Service Parts Planning (SPP)

- Distribution Requirements Planning (DRP) -> DRP Approval -> Define ManagementApprovalManagement approval can now be defined on the SAP Easy Access screen under AdvancedPlanning and Optimization -> Service Parts Planning (SPP) -> Planning -> DistributionRequirements Planning (DRP) -> DRP Approval.

______________________________________________________________SAP AG 5

SAP-System______________________________________________________________

Page 14: Release Notes for SAP Supply Chain Management Release SAP

1.2.2 SCM-APO-CA APO Cross-Application Components

1.2.2.1 Functions for APO Consignment Vendor-Managed Inventory (New)

Use

As of SAP SCM 7.0, the following new functions exist to support a consigned vendor-managed inventoryscenario:

- Consignment indicator A new indicator is available on the Transport Load Builder user interface, which shows whether aconsignment scenario is used for the procurement of the given TLB shipment items.

- TLB shipment splitIn the case of a parallel consigned and non-consigned scenario or multiple purchasing groups, ashipment split is executed during the TLB run.

- Consignment stock in transitA new key figure, Consignment Stock in Transit has been created and added to the standardplanning book 9AVMI. After posting the goods issue in ERP, the new ATP category EV is assignedto the stock in the SCM inbound process. This enables you to view intransit consignment stock data,and integrate it in the planning process.

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

1.2.2.2.1 CDP: Integration of Orders via APO CIF (Enhanced)

Use

______________________________________________________________SAP AG 6

SAP-System______________________________________________________________

Page 15: Release Notes for SAP Supply Chain Management Release SAP

As of SAP SCM 7.0 you can determine whether the system sends in-house production orders and externalprocurement orders (that belong to the make-to-stock segment) to the ERP system with or withoutconfiguration.

Removing the configuration before the transfer of the orders to the ERP system allows you to plan withcharacteristics in the make-to-stock segment in SAP APO even if you do not use SAP for DiscreteIndustries and Mill Products (DIMP). You can use this function together with a Business Add-In (BAdI)to allow a restriction of orders per location and ATP category before the configuration is removed.

If you do not remove the configuration before the transfer, it is only possible to transfer the orders to theERP system with configuration if you use DIMP.

Effects on Customizing

To remove the configuration before the transfer, use the Customizing activity Remove ConfigurationBefore Tranfer to ERP. For more information, see Customizing for Integration with SAP Componentsunder Integration via APO Core Interface (CIF) -> Application-Specific Settings and Enhancements ->Settings for Publication of Characteristics of Transactional Data -> Remove Configuration BeforeTransfer to ERP.

To allow a restriction of orders per location and ATP category before the configuration is removed, usethe Business Add-In BAdI: Addign Exception for Removing Configuration. For more information, seeCustomizing for Integration with SAP Components under Integration via APO Core Interface (CIF) ->Application-Specific Settings and Enhancements -> Settings for Publication of Characteristics ofTransactional Data ->BAdI: Adding Exception for Removing Configuration.

See also

For more information about the integration of orders via CIF, see SAP Library for SAP Supply ChainManagement on SAP Help Portal at http://help.sap.com -> Overview of SAP Documentation -> SAPBusiness Suite -> SAP Supply Chain Management -> SAP SCM 7.0 -> Application Help EN -> SAPSupply Chain Management (SAP SCM) -> SAP Advanced Planning and Optimization (SAP APO) ->Production Planning and Detailed Scheduling (PP/DS) -> Planning with Characteristics -> Functions forCharacteristics-Based Planning -> Transfer of In-House Orders with CDP Data to SAP ERP andTransfer of External Procurement Orders with CDP Data to SAP ERP.

1.2.3 SCM-APO-MD Master Data

1.2.3.1 SCM-APO-MD-PR Product

1.2.3.1.1 Requirements Strategy for Configurable Products (New)

Use

As of SCM 7.0, you can use a new standard requirements strategy for planning without final assembly for

______________________________________________________________SAP AG 7

SAP-System______________________________________________________________

Page 16: Release Notes for SAP Supply Chain Management Release SAP

configurable products. This requirements strategy 35 is assigned to the new planning segmentCharacteristics-Based Planning without Final Assembly.

Forecast data for variant configuration relevant products can be released to this new planning segment ifthe proposed requirements strategy of the location product is either 35, or it is a user-defined requirementsstrategy which is assigned to the planning segment Characteristics-Based Planning without FinalAssembly.

Effects on Customizing

You can specify your own requirements strategy in Customizing for Master Data under Product ->Specify Requirements Strategies.

See also

Release Note Forecast Release and Consumption with Configuration (New)

1.2.4 SCM-APO-VS Vehicle Scheduling

1.2.4.1 SCM-APO-VS-INS Interactive VS

1.2.4.1.1 Splitting Stock Transport Requisitions (Enhanced)

Use

As of SAP SCM 7.0, you can split stock transport requisitions on the basis of split rules in TransportationPlanning/Vehicle Scheduling (TP/VS).

The result of the split is a set of freight units for which you can then create shipments (either manually orby using VSR optimization).

In this process, you can make use of the TP/VS function for creating shipments for orders that have acommon source location but different destination locations. These orders can be transported sequentiallyby the same resource in one shipment (multi-stop scenario).

After you have created the shipments, you have to convert them into TLB shipments by using the report/SAPAPO/VS_TLB_CONVERT. This report deletes the stock transport requisitions being delivered bythe shipment and replaces them with new TLB shipments. The report creates one TLB shipment perfreight unit and also updates the freight units. The TLB shipments are still linked to the shipments inTP/VS.

To enable you to run this report, a new pushbutton (Convert Shipments) has been added to the selectionbar (shuffler) for shipments in transaction VS01. To ensure that this pushbutton is displayed in transactionVS01, you must activate the default implementation of Business Add-In (BAdI)/SAPAPO/VS_ADD_BUTTONS.

______________________________________________________________SAP AG 8

SAP-System______________________________________________________________

Page 17: Release Notes for SAP Supply Chain Management Release SAP

Alternatively, you can call the report on the SAP Easy Access screen by choosing Advanced Planning andOptimization -> Transportation Planning/Vehicle Scheduling -> Environment -> OLTP Interface ->Convert TP/VS Shipments into TLB Shipments.

The TLB shipments are automatically transferred via Core Interface (CIF) from SAP APO to the ERPsystem and the resulting stock transport orders are automatically returned to SAP APO. The TP/VSinbound controller supports the subsequent update of the TLB shipments with the stock transport orders.

You can continue with the standard transportation planning process in TP/VS (transportation serviceprovider selection, releasing shipments, and so on). When you trigger delivery creation in the ERPsystem, the ERP system automatically creates one delivery for each stock transport order. As the finalstep, you can transfer your shipments to the ERP system.

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

1.2.5.1 Low-Level Code Determination (Enhanced)

Use

As of release SAP SCM 7.0, the low-level code determination process for Supply Network Planning(SNP) is enhanced by the following:

- You can run low-level code determination on a selected set of master data objects in transactionsSupply Network Planning in the Background and Determine Low-Level Code.

- Low-level code determination for SNP is integrated in process chains. If you are working with aprocess chain, you can decide what you want the system to do if low-level code determination wasnot successfully finished.

______________________________________________________________SAP AG 9

SAP-System______________________________________________________________

Page 18: Release Notes for SAP Supply Chain Management Release SAP

- In case the low-level code determination process fails, the system provides more detailedinformation about the reasons for failure, as well as information about the percentage of master dataobjects for which low-level codes have been calculated. Based on this information, you can decidewhether or not to use the incomplete results by implementing BAdI method /SAPAPO/SNP_LLC ->CHECK_RESULTS. You can use incomplete results only in process chains.

- It is possible to navigate from the application log to inconsistent master data object after the systemhas finished low-level code calculation.

1.2.5.2 Functions for APO Consignment Vendor-Managed Inventory (New)

Use

As of SAP SCM 7.0, the following new functions exist to support a consigned vendor-managed inventoryscenario:

- Consignment indicator A new indicator is available on the Transport Load Builder user interface, which shows whether aconsignment scenario is used for the procurement of the given TLB shipment items.

- TLB shipment splitIn the case of a parallel consigned and non-consigned scenario or multiple purchasing groups, ashipment split is executed during the TLB run.

- Consignment stock in transitA new key figure, Consignment Stock in Transit has been created and added to the standardplanning book 9AVMI. After posting the goods issue in ERP, the new ATP category EV is assignedto the stock in the SCM inbound process. This enables you to view intransit consignment stock data,and integrate it in the planning process.

______________________________________________________________SAP AG 10

SAP-System______________________________________________________________

Page 19: Release Notes for SAP Supply Chain Management Release SAP

1.2.5.3 SCM-APO-SNP-BF Basic Functions

1.2.5.3.1 Supply Network Planning (SNP) Queue Processing (Enhanced)

Use

As of release SAP SCM 7.0, master data queue processing in Supply Network Planning (SNP) has beenenhanced by the following:

Performance Improvement and Background Processing

- The performance of SNP master data queue processing has been improved significantly, which leadsto a shorter startup time of interactive Supply Network Planning and a runtime improvement of SNPplanning reports and planning area initialization.

- To further improve the startup time of interactive Supply Network Planning, a new queue updatemethod has been introduced that moves the queue processing into the background.

Monitoring in Computing Center Management System (CCMS)

- The monitoring of SNP master data queues is integrated into CCMS.

- You can monitor the runtime of the queue update process, the number of entries in level 1 and level2 queues, the errors of background update processes. and the latest initialization date of planningareas for each planning version.

- You can specify that CCMS should issue alerts at certain thresholds, and also have the system notifythe administrator of these alerts by email.

- You can navigate from CCMS to the relevant transactions to resolve the alerts.

Effects on Customizing

In customizing activity Maintain Global SNP Settings there are three new parameters that affect theprocessing of SNP master data queues:

- Queue processing method

- Maximum wait time for running queue update processes

- Setting whether the queue update should automatically update the timeseries in liveCache

For more information, see Customizing for Advanced Planning and Optimization under Supply ChainPlanning -> Supply Network Planning (SNP) -> Basic Settings -> Maintain Global SNP Settings.

See also

For more information see SAP Library under SAP Supply Chain Management (SAP SCM) -> SAPAdvanced Planning and Optimization (SAP APO) -> Supply Network Planning -> Master Data for SupplyNetwork Planning -> Processing Master Data Queues in Supply Network Planning (SNP).

______________________________________________________________SAP AG 11

SAP-System______________________________________________________________

Page 20: Release Notes for SAP Supply Chain Management Release SAP

1.2.6 SCM-APO-SDM Multilevel Supply & Demand Matching

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

1.2.6.1.1 Capable-to-Match (CTM) (Enhanced)

Use

Planning with Characteristics

Characteristics-Based Planning

As of SCM 7.0, CTM considers characteristic values of orders during planning and creates orders withcorresponding characteristic values. CTM considers characteristics that are relevant for variantconfiguration or for characteristics-dependent planning (CDP). For this, you must fulfill the followingprerequisites:

- You are planning with configurable products.

- In Customizing for Master Data under Define Configuration Schema (CDP or VariantConfiguration), you set the configuration relevance or the default configuration relevance CDP orVariant Configuration.

- In the CTM profile on the tab page Strategies -> Planning Strategies, you choose the ConsiderCharacteristics checkbox.

CTM considers characteristics with a numeric or alphanumeric data type.

Block Planning

If the products you are planning with are configured for CDP, CTM considers block definitions ofresources and fixed blocks.

Forecast Data with Configuration

If the products you are planning with are configured for variant configuration, CTM considers forecastdata with their configuration and creates orders with the relevant characteristic values accordingly.

Shelf-Life

As of SCM 7.0, CTM takes the following product master settings for shelf life into consideration:

- Shelf Life

- Maturation Time

- Req.Min.Sh.Life

- Req.Max.Sh.Life

PP/DS Production Data Structure (PP/DS PDS) for CTM

Parallel Operations

If you generate a PP/DS PDS for CTM from a production version that contains parallel operations in a

______________________________________________________________SAP AG 12

SAP-System______________________________________________________________

Page 21: Release Notes for SAP Supply Chain Management Release SAP

routing, only the longest of the parallel operations is considered in the PDS. As a result, the PDS containsa chain of linear operations. If more than one of the longest parallel operations have the same duration, thefirst of these operations is considered.

Business Add-In (BAdI) /SAPAPO/CURTO_CREATE

In the Business Add-In (BAdI) /SAPAPO/CURTO_CREATE, the method CREATE_CTM_PDS hasbeen enhanced by the parameter EV_OPER_FINITE_RES. This parameter specifies that only theoperations on finite resources are to be considered when the PP/DS PDS for CTM is generated.

Additionally, the parameter EV_TRUE of the method CREATE_CTM_PDS has been changed. If you usethis parameter, the system now creates a PP/DS PDS for CTM even if the production version containsconfigurable products or object dependencies. In this case, a PP/DS PDS is generated for CTM, however,without the information regarding the configurable products or object dependencies.

Object Dependencies, Variant Tables and Reference Characteristics

CTM considers the following types of object dependencies in the PP/DS PDS for CTM:

- Selection condition

- Procedure

CTM considers the following operators for selection conditions and procedures: =, <>,AND,OR,NOT.For procedures CTM considers also the operator IF.

This is true if you assign a value to a variable in a selection condition or procedure. For example, colour =red, size > 10 AND size < 30. However, this is not true if you assign a value to value. For example, colour= colour2, size > size2 AND size < size3.

CTM also takes into consideration the following in the PP/DS PDS for CTM:

- variant tables

- reference characteristics which reference the QUANT field in the/SAPAPO/CULL_CFG_COMPONENT structure and the DURVAR field in the/SAPAPO/CULL_CFG_MODE_PRODUCE structure.

1.2.7 SCM-APO-FCS Demand Planning

1.2.7.1 Forecast Release and Consumption with Configuration (New)

Use

As of SCM 7.0, you can release forecast data of products with a configuration of their own from DemandPlanning (DP) to Supply Network Planning (SNP). To do this, you must fulfill the following

______________________________________________________________SAP AG 13

SAP-System______________________________________________________________

Page 22: Release Notes for SAP Supply Chain Management Release SAP

prerequisites:

- The corresponding products are relevant for variant configuration.

- In Customizing for Master Data under Define Configuration Schema (CDP or VariantConfiguration), you have set the configuration relevance or the default configuration relevance tovariant configuration (VC) and selected the Release Forecast with Configuration checkbox.

- In the location-specific product master data of the corresponding products, you have specified for theproducts the requirements strategy 35 or a comparable user-defined requirements strategy that isassigned to the planning segment Characteristics-Based Planning without Final Assembly.

- You have assigned the products to a characteristics-based forecasting profile (CBF profile).

- You have assigned the products to a consumption group with CBF characteristics.

- In the location-specific product master data of the corresponding products, you have not selected theAssembly Planning checkbox.

See also

Release Notes Configuration Schema (Enhanced) and Requirements Strategy for Configurable Products(New)

1.2.7.2 MLR Forecasting Using POS Data (New)

Use

As of SCM 7.0, this forecasting method in Demand Planning (DP) enables you to use point of sale data(POS data) to create a short-term statistical forecast. This forecast, in contrast to other statistical forecasts,can achieve more exact results since it also considers, in addition to the deliveries in the past and the POSdata, the customer's inventory fluctuation.

You can make the relevant settings for this forecasting method in the MLR Profile.

______________________________________________________________SAP AG 14

SAP-System______________________________________________________________

Page 23: Release Notes for SAP Supply Chain Management Release SAP

1.2.7.3 Forecasting Enhancements (Enhanced)

Use

As of SCM 7.0, the forecasting methods in Demand Planning (DP) have been enhanced by the followingfunctions:

- Reinitialization of forecast parameters

- Trend dampening

You can make reinitialization and trend damping settings globally for a planning area which will beapplied to every univariate forecast made in this planning area. If you want to use different settings for aspecific univariate forecast, you can change the settings in the corresponding univariate forecast profile.

Reinitialization

Forecasting methods based on the methods of exponential smoothing usually react very slowly to extremestructural changes in historical data. You can use reinitialization to adjust a forecast accordingly if itdetects a structural interruption or a major change in trend in the historical data. For reinitialization, theforecast parameters basic value, trend value and seasonal indices are recalculated.

Trend dampening

Forecast algorithms often identify a strong upward trend and as a consequence create a very optimisticforecast for the future. To dampen the identified trend for long term forecast, you can do the following:

- Use a trend dampening profile

- Set an upper limit for the trend value

- Set an upper limit for the forecast

- Use the trend dampening factor Phi (applicable only for exponential smoothing methods)

1.2.7.4 Definition of Configuration Schema (Enhanced)

Use

As of SCM 7.0, you can define the configuration relevance for Characteristics-Dependent Planning(CDP) or variant configuration (VC) on client level or on product level. If you want to work with bothconfiguration procedures in one client, in the Setting field, choose Configuration on Product Level,and in the Default for Config. field, choose the configuration procedure as a default that is relevant for

______________________________________________________________SAP AG 15

SAP-System______________________________________________________________

Page 24: Release Notes for SAP Supply Chain Management Release SAP

the characteristics you are using for your planning.

You can also define that your forecast data is to be released with a configuration of its own. Select theRelease Forecast with Configuration checkbox, if you want to do the following:

- Release your forecast data from Demand Planning (DP) to Supply Network Planning (SNP) with aconfiguration of its own

- Transfer the orders with a configuration of their own back from SNP to DP.

For more information on the requirements for releasing forecast data with configuration, see the releasenote Forecast Release and Consumption with Configuration.

Effects on Customizing

You can make the settings as described above in Customizing for Master Data under DefineConfiguration Schema (CDP or Variant Configuration)

1.2.7.5 SCM-APO-FCS-CFM Customer Forecast Management

1.2.7.5.1 Customer Forecast Management (New)

Use

In a standard vendor-managed inventory scenario, the customer regularly sends forecast data to thevendor's APO system, and this forecast serves as the basis for replenishment planning. Up to now, theforecast data has been immediately saved into APO Demand Planning, and it was not possible to analyzethe data before making it available for the planning process.

As of SAP SCM 7.0, you can use the new component Customer Forecast Management(SCM-APO-FCS-CFM) to perform an analysis of the data before releasing it to Demand Planning.

- A new program is available for performing a forecast analysis on incoming customer forecast data.The forecast analysis can either be a background run, or can be implemented interactively by apushbutton.

- New alert types are available for the forecast analysis run, and you can define an alert profile for auser specific alert display.

- A new forecast analysis user interface has been created with an authorization object to restrict dataaccess to the relevant planner.

- A program is available to perform the release of customer forecast data based on the customerforecast release profile defined in customizing. You can release the data from the customer forecastmanagement UI interactively, after checking and correcting (adjusting) the original customerforecast data.

______________________________________________________________SAP AG 16

SAP-System______________________________________________________________

Page 25: Release Notes for SAP Supply Chain Management Release SAP

- You can perform a waterfall analysis run on data according to predefined selection criteria, anddownload the results to an Excel file in a structured way.

- A new subtab is available on the Demand tab of the location product master data maintenancetransaction to maintain customer forecast related settings.

Effects on Customizing

To define a forecast analysis profile and a forecast release profile, implement the IMG activity DefineProfiles and Settings for Customer Forecast Management. You can also use this activity to make basicand other settings for customer forecast management, for example, compare key figures and assign thesekey figure comparisons to forecast analysis profiles.

By implementing the BAdI: CFM Data Release to Specified Destination, you can define a target otherthan Demand Planning for saving forecast data.

There is also a BAdI for specifying the conversion procedure for forecast quantities in inbound timebuckets (BAdI: Processing of Single Inbound Bucket)

1.2.8 SCM-APO-SPP Service Parts Planning

1.2.8.1 Location Product Master Data for Service Parts Planning (Enhanced)

Use

Up to now, the following fields have only been available on product level. As of SAP SCM 7.0, thesefields are also available on location product level and you can specify whether you want the system to usethe values you specified on location product level or the values you specified on product level:

- Product for Kit-to-OrderThe system evaluates the value in this field for the KIT approval rule of distribution requirementsplanning (DRP).

- Production Start DateThe system evaluates the value in this field for

- The NEWPARTDUE approval rule of DRP

- The selection of planning-relevant products in surplus and obsolescence planning

- Phase-in planning

- Retention PeriodThe system evaluates this value for the calculation of the surplus quantity with exponentiallysmoothed forecasting.

______________________________________________________________SAP AG 17

SAP-System______________________________________________________________

Page 26: Release Notes for SAP Supply Chain Management Release SAP

- No Inventory BalancingThe system evaluates this value for the inventory balancing service.

- Procure-to-OrderThe system evaluates this value for checking the planning relevance for the destocking service ininventory planning.

1.2.8.2 OEM-Managed Inventory (New)

Use

As of SAP SCM 7.0, Service Parts Planning (SPP) contains a VMI variant, the OEM-managed inventoryprocess.

As of SAP SCM 7.0, you, being an original equipment manufacturer (OEM) and owner of SPP, can planthe inventory of certain products for certain customers or dealers. In doing so, you can support thesecustomers or dealers to optimize their planning and their inventory situation. The customers and dealersthat you include in this process do not actively have to order service parts from you any more, but you asOEM trigger the stock transport to the customer's or dealer's location based on your planning.

The customer or dealer, whom you involve in the OEM-managed inventory process, saves his or her salesdata and his or her stock data either in an SAP system or in an external system. He or she provides youwith information about this data in a business-to-business (B2B) process. This B2B process is anXML-based process between business partners, which allows these business partners (especially smallerbusiness partners, as your customers or dealers might be) to exchange XML documents.

SPP uses the sales data that you receive from your customer or dealer, to create a demand history for hisor her location products. On the basis of this demand history, SPP continues the regular planning(including forecasting, inventory planning, distribution requirements planning, deployment, and so on) forthe products at the customer's or dealer's location.

You can display all the planning results for products at your customer's or dealer's location on the SPPscreens on which you also display the planning results of your OEM-locations.

Your customer or dealer can display the planning results that are relevant to him or her in the customer'sworklist, which he or she can access using a Web browser. Additionally, he or she has the followingopportunities to influence the planning:

- Agree or disagree to a stocking or destocking decision

- Approve and change stock transport orders to his or her location(This is optional. You do not have to allow your customer or dealer to approve and change stocktransport orders, but you can also do this as part of your internal planning process.)

______________________________________________________________SAP AG 18

SAP-System______________________________________________________________

Page 27: Release Notes for SAP Supply Chain Management Release SAP

- Define, together with you, follow-on activities for excess stock at his or her location and executethese follow-on activities(This is optional. You do not have to provide the possibility to process excess stock.)

See also

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Service Parts Planning -> OEM-ManagedInventory.

1.2.8.3 Name of the SPP - Customer View (Internal View) Changed

Use

As of SAP SCM 7.0 the SPP - Customer View (Internal View) is called SPP - Planner View(Internal). The transaction code and the URL stay the same.

1.2.8.4 User Interfaces for Service Parts Planning (Enhanced)

Use

As of SAP SCM 7.0, there will be the following changes for user interfaces in Service Parts Planning(SPP):

- Display of the bill of distribution (BOD)

- Trigger events

Display of the BOD

As of SAP SCM 7.0, you can define a default display of the BOD for every combination of user and thefollowing screens:

- Interactive Forecasting (/SAPAPO/SPPFCST)

______________________________________________________________SAP AG 19

SAP-System______________________________________________________________

Page 28: Release Notes for SAP Supply Chain Management Release SAP

- EOQ/Safety Stock Planning (/SAPAPO/SPPINVP)

- DRP Matrix (/SAPAPO/SPPDRPM)

- Deployment and Inventory Balancing (/SAPAPO/SPPDEPL)

- Product Detail (/SAPAPO/SPP_CUSTOMER)

- SPP Cockpit (/SAPAPO/SPP_CUSTOMER)

You can define that a user either sees a filtered or the complete BOD by default. Nevertheless, the usercan change the display of the BOD individually by using the new Show Filtered BOD or ShowComplete BOD pushbutton. In the BAdI: Define Filter for BOD Display(/SAPAPO/SPP_BOD_DISPLAY) Business Add-In (BAdI) that is available as of SAP SCM 7.0, you candefine how the filter works and what the filtered BOD looks like. In the standard implementation of thisBAdI, a filtered BOD means a BOD without non-OEM locations (that means without customer and dealerlocations).

Trigger events

As of SAP SCM 7.0, the BAdI: Define Modifications and Enhancements for User Interfaces(/SCF/UIMDL_APPCUST) BAdI contains the new method GET_EVENT. In this method, you can defineevents that the system triggers if a user chooses a certain pushbutton.

1.2.8.5 Worklists for Service Parts Planning (New)

Use

As of SAP SCM 7.0, planners and customers (customers can be dealers, for example) can use worklists inService Parts Planning (SPP). Planners and customers can use these worklists as a start page for theirdaily work.

A worklist consists of different queries. These queries either contain the actions required by the planner orcustomer or information that is useful for the planner or the customer. From some of the queries, aplanner can navigate to other transactions of Service Parts Planning to gather additional information or toperform a required action. A customer, however, is not allowed to navigate to the (internal) transactionsof Service Parts Planning. He or she can display the information relevant for him or her only directly inthe worklist.

The worklists are based on the personal object worklist (POWL) technology of SAP NetWeaver.Selection criteria, queries, and layouts of a worklist can be changed and can be defined for each user.

______________________________________________________________SAP AG 20

SAP-System______________________________________________________________

Page 29: Release Notes for SAP Supply Chain Management Release SAP

There is one worklist for planners and one for customers. In the SAP standard, we deliver these worklistswith the following queries:

Note:You can modify, add, and delete queries to model the worklists according to your needs.

Planner's Worklist

- Stocking / Destocking Approval (category Action Required)

- Stocking / Destocking (category Monitoring)

- STO Approval (category Action Required)

- STO (category Monitoring)

- Procurement Approval (category Action Required)

- Procurement (category Monitoring)

- Surplus Approval (category Action Required)

- Forecast Approval (category Action Required)

- Critical Products (category Monitoring)

- Supplier Overview of Critical Products (category Monitoring)

- Critical Sales Orders (category Monitoring)

- Alerts (Category-Based) (category Alerts)

- Alerts (Product-Based) (category Alerts)

- Alerts (Location-Based) (category Alerts)

Customer's Worklist

- Stocking / Destocking Agreement (category Action Required)

- Stocking / Destocking (category Monitoring)

- STO Approval (category Action Required)

- Excess (category Action Required)

- Supersession (category Monitoring)

See also

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Service Parts Planning (SPP) -> Master

______________________________________________________________SAP AG 21

SAP-System______________________________________________________________

Page 30: Release Notes for SAP Supply Chain Management Release SAP

Data and General Functions for SPP -> Worklists for Service Parts Planning.

1.2.8.6 Creating Users With SAP NetWeaver Identity Management (New)

Use

As of SAP NetWeaver 7.0 Enhancement Package 1 and SAP Service Parts Planning (SAP SPP) 7.0, youcan generate users in SAP SPP automatically, using SAP NetWeaver Identity Management. The followinguse cases apply:

- Creation of users and business partners for employeesA user administrator creates new employees in the Human Resources (HR) system. These employeeswork for the business partner running SAP SPP. The user creation in the HR system triggers theautomatic creation of a new internal identity in the Identity Management system. A useradministrator assigns a business role to this new identity. As a result, Identity Management triggersautomatic user and business partner creation in SAP SPP for the employee.

- Creation of users and business partners for external usersA user from an external business partner requests access to the SAP SPP system. The useradministrator creates a new external identity in Identity Management for the external user. With SAPNetWeaver Identity Management, the new user of the external business partner is distributed to SAPSPP.

In all use cases, SAP NetWeaver Identity Management triggers the creation of a new user in SAP SPP asfollows:

- Generation of a user in SAP SPP

- Generation of a business partner of type Person and with Internet User role, which is then assignedto the user

- Assignment of the business partner of type Person to a business partner of type Organization thatrepresents the business partner the user belongs to

In addition, you can also change and delete users centrally with Identity Management.

Prerequisites

You can use this function only when the following applies, in addition to the standard SPP system setup:

- SAP NetWeaver Identity Management (as of release 7.1) is installed and connected to SAP SPP.

- For the uses case Creation of users and business partners for new employees, an EmployeeAdministration component of SAP ERP HCM (as of enhancement package 4 for SAP ERP 6.0)solution is installed.

Effects on System Administration

With the use of Identity Management, automatic creation of new users is triggered by the Identity

______________________________________________________________SAP AG 22

SAP-System______________________________________________________________

Page 31: Release Notes for SAP Supply Chain Management Release SAP

Management system, so there is no need to create users manually in SAP SPP.

To be able to use Identity Management, you must make an initial load of all existing user IDs, roles, andbusiness partner IDs from SAP SPP to the Identity Management system.

Effects on Customizing

To be able to use Identity Management, you must perform the following Customizing activities:

- You have defined which business partner of type Organization represents the leading businesspartner. The leading business partner is the customer in supplier collaboration or the supplier incustomer collaboration. To do this, you use the Define Leading Business Partner for IdentityManagement Customizing activity.

- If there a multiple business partners of type Organization that represent the leading business partnerin the system, you implement the /SCA/IDM_PARTNER_OWN Business Add-In (BAdI) with theBAdI: Determination of Leading Business Partner for Identity Management Customizing activity.

- You have mapped the form of address in Human Resources (HR) to the form of address of thebusiness partner using the Assign HR Form of Address Key to Form of Address Keys of BusinessCustomizing activity.

See also

For more information, see the documentation for SAP NetWeaver Identity Management.

1.2.8.7 SCM-APO-SPP-CPD Entry and Maintenance of Historical Data

1.2.8.7.1 Creation of the Demand History (Enhanced)

Use

As of SAP SCM 7.0, new functions exist for the creation of the demand history in the following areas:

- Simulation

- Realignment of the demand history in the case of calendar changes

Simulation

As of SAP SCM 7.0, you can simulate the planning services for the realignment of the demand history.Thus, you can check the planning results in a non-active version and, as a result, adjust parameters andsettings if necessary.

To enable simulations of the realignment services of the demand history, there is new BI Content in theSAP SCM system.

Realignment of the demand history in the case of calendar changes

As of SAP SCM 7.0, the additional planning service SPP: Calendar Change Realignment(SPP_PDEM_CLD_RLG) for the realignment of the demand history exists. If you change, delete, or addperiods in the calendar master data, this planning service scales the raw demand of the affected locationproducts for the periods that have been changed, anew.

______________________________________________________________SAP AG 23

SAP-System______________________________________________________________

Page 32: Release Notes for SAP Supply Chain Management Release SAP

See also

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Service Parts Planning (SPP) ->Generating the Demand History -> Historical Data Maintenance -> Planning Services forRealignment of Demand History.

1.2.8.7.2 Simulations in Service Parts Planning (Enhanced)

Use

As of SAP SCM 7.0, it is possible to simulate the inventory balancing service and the planning servicesfor the realignment of the demand history.

Simulation of the inventory balancing service

You can create and delete simulation versions for inventory balancing on the SPP Simulation(/SAPAPO/SPPSIM) screen. Additionally, you can simulate the inventory balancing service on thisscreen. You can display the results of the simulation on the Deployment and Inventory Balancing(/SAPAPO/SPPDEPL) screen.

Simulation of the planning services for the realignment of the demand history

You can create and delete simulation versions on the SPP Simulation (/SAPAPO/SPPSIM) screen andyou can specify the InfoProviders that you want to use for the simulation on this screen. To simulate theplanning services for the realignment of the demand history, however, you do not use the SPPSimulation screen, but you schedule the services in the Planning Service Manager (PSM).

For the simulation of the planning services for the realignment of the demand history, new BI Contentexists in the Business Intelligence system of SAP SCM 7.0. The new BI Content objects are very similarto the already existing BI Content for the creation of the demand history. The only difference is that thenew InfoSources and InfoProviders for the simulation contain the characteristic 9AVERSION. Thischaracteristic enables you to capture raw data and to maintain the demand history specific to a version.

See also

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Service Parts Planning -> Simulation inService Parts Planning and under Service Parts Planning -> Generating the Demand History ->

______________________________________________________________SAP AG 24

SAP-System______________________________________________________________

Page 33: Release Notes for SAP Supply Chain Management Release SAP

Historical Data Maintenance -> Planning Services for Realignment of Demand History.

1.2.8.8 SCM-APO-SPP-SFC Service Parts Forecast

1.2.8.8.1 Functions in Forecasting (Enhanced)

Use

As of SAP SCM 7.0, new functions exist for forecasting in the following areas:

- Forecast approval

- TPOP forecast

Forecast approval

Up to now, it was only possible to modify the final forecast for individual periods manually. As of SAPSCM 7.0, you can modify the final forecast for all planning periods on the basis of a formula defined byyou in the Business Add-In (BAdI) BAdI: Change Final Forecast(/SAPAPO/FCST_APPR_CHG_FCST).

TPOP forecast

Up to now, you could specify in the forecasting service profile, whether you want to perform a TPOPforecast or a regular forecast. As of SAP SCM 7.0, there are separate planning services for TPOPforecasting. This means that if you want to create a TPOP forecast for your supplier, you can schedule thefollowing new planning services in Planning Service Manager (PSM):

- SPP: Forecast Service (TPOP Selection) (SPP_FCS_SERVICE_TPOP)

- SPP: Forecast Service (StdDev. for TPOP) (SPP_FCS_SERVICE_MSE_TPOP)

- SPP: Forecast Approval Service (TPOP) (SPP_FCST_RELEASE_TPOP)

- SPP: Recalculation of FCST in Past (TPOP) (SPP_RECALC_HISTFCST_TPOP)

1.2.8.9 SCM-APO-SPP-SIP Service Parts Inventory Planning

1.2.8.9.1 Functions for Inventory Planning (Enhanced)

______________________________________________________________SAP AG 25

SAP-System______________________________________________________________

Page 34: Release Notes for SAP Supply Chain Management Release SAP

Use

As of SAP SCM 7.0, new functions exist for inventory planning in the following areas:

- Stocking / destocking approval

- Historical data for stocking / destocking

- Safety stock at parent location

- EOQ period

- Target service level

- Additional safety stock

Stocking / destocking approval

Up to now, the system automatically changed the replenishment indicator of a location product accordingto the results of the stocking service and the destocking service. As of SAP SCM 7.0, you can decidewhether you want the system to change replenishment indicators automatically or whether you want toapprove replenishment indicators for which the stocking or destocking service has proposed a change. Ifyou decide that you want to approve changes to the replenishment indicator, you can use theStocking/Destocking Approval screen, which is newly available as of SAP SCM 7.0. On this screen,you get a lot of background information, based on which you can decide whether you want to approve thechanged replenishment indicator or whether you want to change it yourself. Only when you haveapproved or when you have changed and approved a replenishment indicator for a location product, doesthe system save the new replenishment indicator and use it for further planning.

Historical data for stocking / destocking

As of SAP SCM 7.0, you can decide how many periods the system considers for the stocking decision andthe destocking decision. Additionally, you can split the historical periods that the system considers in twoparts and define a weighting factor for each of these two parts.

Safety stock at parent location

As of SAP SCM 7.0, the Business Add-In (BAdI) BAdI: Safety Stock Adjustment at Parent Locationfor Push Deployment (/SAPAPO/PINV_ADJUST_PARENT_SFT) is available. Since you do not putaway goods at the parent location at push deployment but forward them straight to the relevant childlocation, the replenishment lead time is shortened. Therefore, you might want to adjust the safety stock,which is calculated depending on the replenishment lead time. If you want to use another logic to adjustthe safety stock as implemented in the standard inventory planning process, you can use this BAdI todefine an own logic or you can implement the logic that we deliver as the default implementation of theBAdI. This default logic takes a minimum and a maximum safety stock into account. The minimum safetystock is based on the lead time from the parent location to the door of the child location (or to the contractpackager if a contract packager is involved). The maximum safety stock is based on the lead time from theparent location to the storage bin of the child location.

EOQ period

Up to now, you could get the EOQ period for a child location from the parent location. As of SAP SCM7.0, the system can also take the minimum and maximum EOQ period of the child location into accountwhen getting the EOQ period from the parent location.

Target service level

______________________________________________________________SAP AG 26

SAP-System______________________________________________________________

Page 35: Release Notes for SAP Supply Chain Management Release SAP

As of SAP SCM 7.0, you can define rules for the determination of the target service level on locationlevel or on location product level in a more detailed way. Up to now, you could only specify rules for acertain location or a certain location product. As of SAP SCM 7.0, you can define rules for a location or alocation product based on which level of the bill of distribution (BOD) the location is. That means youcan define different rules for a location or a location product depending on whether the location is anentry location, an intermediate parent location, or a child location.

Additional safety stock

Up to now, you could specify an additional safety stock in days on location product level in locationproduct master data. As of SAP SCM 7.0, you can also specify an additional safety stock when definingthe target service level. This means that you can also specify an additional safety stock for a locationproduct based on which level of the BOD the location is. This means you can specify the additional safetystock depending on whether the location is an entry location, an intermediate parent location, or a childlocation.

See also

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Service Parts Planning -> InventoryPlanning.

1.2.8.9.2 Functions in Surplus and Obsolescence Planning (Enhanced)

Use

As of SAP SCM 7.0, new functions exist for surplus and obsolescence planning in the following areas:

- Proposal for surplus approval

- Lead times

- Additional sorting for surplus quantity disaggregation

Proposal for surplus approval

As of SAP SCM 7.0, the BAdI: Define Logic for Proposed Surplus Approval(/SAPAPO/SPP_SOR_UI) Business Add-In (BAdI) is available. In this BAdI, you can define logicaccording to which the system either recommends approval of a surplus quantity that needs to bemanually approved or marks a surplus quantity that needs to be manually approved as critical. When yourplanners then access the Surplus and Obsolescence Approval screen and choose the Go pushbuttonfor their product selection, the system not only displays the surplus quantities that need to be manuallyapproved, but it also sets the Approve or the Critical indicator for each surplus quantity.

Lead times

As of SAP SCM 7.0, you can choose which lead time scenario you want to use for surplus and

______________________________________________________________SAP AG 27

SAP-System______________________________________________________________

Page 36: Release Notes for SAP Supply Chain Management Release SAP

obsolescence planning. Additionally, surplus and obsolescence planning takes into account whethercontract packagers are involved in the planning process when determining the lead time.

Additional sorting for surplus quantity disaggregation

As of now, you could only define a disaggregation strategy for surplus. You could define, for example,that the system sorts the locations according to their demand history quantity or their forecast quantity. Asof SAP SCM 7.0, you can refine this disaggregation strategy for the surplus quantity. To refine thedisaggregation strategy, you can either use the sorting methods delivered by us or you can define yourown sorting method in the BAdI: Define Sorting for Surplus Disaggregation(/SAPAPO/SOR_DISAGG_SORT) BAdI that is available as of SAP SCM 7.0.

1.2.8.10 SCM-APO-SPP-SDR Distribution Requirements Planning forService Part

1.2.8.10.1 Functions in Distribution Requirements Planning (DRP) (Enhanced)

Use

As of SAP SCM 7.0, new functions exist for distribution requirements planning (DRP) in the followingareas:

- Repair or buy

- Reorder-point-based planning

- Supplier shutdown

- DRP horizons

- DRP Matrix

- Virtual locations for consolidated ordering

- DRP locks

- Fixed demands and fixed receipts

- Customizing of the External Procurement - Delivery Schedule Maintenance screen

- DRP approval rules

- Management approval

- Define latest goods receipt time of released delivery schedule lines

______________________________________________________________SAP AG 28

SAP-System______________________________________________________________

Page 37: Release Notes for SAP Supply Chain Management Release SAP

Repair or buy

- As of SAP SCM 7.0, you can perform the repairable returns forecast not only based on the demandforecast or on your own forecast, but also based on time series. To do so, you can define a profile forthe repairable returns forecast based on time series in Customizing, in which you specify the timeseries that the system uses.

- Up to now, the repair-or-buy function could only plan with a one-to-one relationship of serviceableand unserviceable products. As of SAP SCM 7.0, it is also possible to specify that more than oneunserviceable product is needed to restore the serviceable product. If you know, for example, thatyou need an average of two broken assemblies to cover the demand of one serviceable assembly, youcan specify this in the bill of material of the assembly and the repair-or-buy function takes thisinformation into account.

Reorder-point-based planning

Up to now, you could define additional demand and receipt quantities for products that you plan in thereorder-point-based planning mode in the BAdI: Determine Additional Quantities forReorder-Point-Based Planning (/SAPAPO/ROP_ADDITIONAL_QTYS) Business Add-In (BAdI). Asof SAP SCM 7.0, in this BAdI, you can distinguish between additional demand and receipt quantities forserviceable and for unserviceable products that you plan in the reorder-point-based planning mode.

Supplier shutdown

Up to now, the system did not take the lead time from the supplier to the entry location into account whenplanning a supplier shutdown that you have defined in the location product master data. As of SAP SCM7.0, you can decide whether you want the system to take this lead time into account and, if yes, you canspecify a profile ID for a supplier shutdown in the product specific transportation lane master data.

DRP horizons

As of SAP SCM 7.0, you can extend the freeze horizon for specific suppliers or specific products ofspecific suppliers. This means that if, over a period of time, you do not want the system to change deliveryschedule lines or create new delivery schedule lines for this product and supplier, you can enter the enddate of this time period as end date for the freeze horizon. If you have entered this end date, the systemcompares it with the date it has calculated as end date of the freeze horizon and chooses the later one asthe actual end date for the freeze horizon.

DRP Matrix

As of SAP SCM 7.0, the DRP Matrix contains the new key figures described below:

- As of SAP SCM 7.0, the BAdI: Determine Additional Quantities for Period-Based Planning(/SAPAPO/PB_ADDITIONAL_QTYS) BAdI is available. In this BAdI, you can define additionalquantities for serviceable and unserviceable products that the system plans period-based and thatDRP is to take into account. If you define additional quantities in this BAdI, the system displaysthese additional quantities in the following new key figures of the DRP matrix:

- Additional Demand (BAdI)

- Additional Receipt (BAdI)

- Additional Unserviceable Demand (BAdI)

- Additional Unserviceable Receipt (BAdI)

______________________________________________________________SAP AG 29

SAP-System______________________________________________________________

Page 38: Release Notes for SAP Supply Chain Management Release SAP

- As of SAP SCM 7.0, you can perform inventory balancing with unserviceable products. The systemdisplays the results of this new process in the following new key figures of the DRP matrix:

- Unserviceable Products Demand (STO)

- Unserviceable Products Receipt (STO)

- Unserviceable in Transit Stock (STO)

- Subst. Dem: Forw.Exc.Unserv.Stk (Inv.Bal.)

- Subst. Rcpt: Forw. Exc. Unserv. Stk (Inv.Bal.)

As of SAP SCM 7.0, the following key figures are re-named:Name up to now Name as of SAP SCM 7.0

Dependent Demand from Repairs Dependent Demands

Serviceable Products Rcpt (Rep., Frozen) Products Rcpt (Kit-to-Stk./Repair, Froz)

Serviceable Products Rcpt (Rep., Not Froz.) Products Rcpt (Kit-to-Stk./Rep, Not Froz)

Virtual locations for consolidated ordering

Up to now, virtual locations for consolidated ordering could only consist of child locations. As of SAPSCM 7.0, you can also define virtual locations for consolidated ordering that consist of entry locations.Additionally, as of SAP SCM 7.0, the BAdI: Determination of Preferred Location of a VLCO(/SAPAPO/SPP_VCOL_LEADING_LOC) BAdI is available. In this BAdI you can define your own logicfor how the system determines the preferred location of virtual locations for consolidated ordering thatconsist of child locations and of virtual locations for consolidated ordering that consist of entry locations.

DRP locks

Up to now, you could only define a lock period during which DRP did not take a certain location productinto account in the planning. As of SAP SCM 7.0, you can also define reasons for DRP locks and assignthese reasons to a lock period.

Fixed demands and fixed receipts

As of SAP SCM 7.0, on the Fixed Demands and Fixed Receipts screen, the system displays the userswho have created and last changed a fixed demand or fixed receipt. Additionally, the system displays thedate and time a fixed demand or a fixed receipt was created and last changed.

Customizing of the External Procurement - Delivery Schedule Maintenance screen

As of SAP SCM 7.0, the BAdI: Customizing of "External Procurement - Delivery Maintenance"Screen (/SAPAPO/SPPDRPSB_CUST) BAdI is available. In this BAdI, you can modify theCustomizing settings for the External Procurement - Delivery Schedule Maintenance screen foreach user.

DRP approval rules

As of SAP SCM 7.0, there is a new DRP approval rule that checks if a purchase order schedule line or ascheduling agreement release that DRP has planned, falls within a supplier shutdown. If this is the case,the system creates an alert of type 7891.

Management approval

As of SAP SCM 7.0, you can change the limit values for the DRP management approval in the productivesystem. Up to now, these limit values could only be defined and modified in Customizing. As of SAP

______________________________________________________________SAP AG 30

SAP-System______________________________________________________________

Page 39: Release Notes for SAP Supply Chain Management Release SAP

SCM 7.0, you can define these limit values in the Define Management Approval screen, which you canaccess on the SAP Easy Access screen.

Define latest goods receipt time of released delivery schedule lines

As of SAP SCM 7.0, the BAdI: Definition of the Latest GR Time of Released Delivery ScheduleLines (/SAPAPO/ORDER_SNAPSHOT) BAdI is available. In this BAdI, you can define the latest goodsreceipt time of released scheduling agreement delivery schedule lines (SASLs). You have to specify thispoint in time, for example, to define the release creation horizon if you do not release every SASLindividually, but aggregate the SASLs that are to be released. Only then, a snapshot of the deliveryschedule can be accurately and correctly created.

1.2.8.10.2 Kit to Stock in Distribution Requirements Planning (DRP) (New)

Use

As of SAP SCM 7.0, the kit-to-stock function is available in distribution requirements planning (DRP).

Up to now, you could only plan the procurement of individual products. As of SAP SCM 7.0, you canalso plan the procurement and creation of kits. A kit is a service part that is created out of several otherservice parts. You define the service parts a kit consists of in a bill of material for the kit in SAP ERP. InSAP SCM, you can decide for each combination of kit and location, whether you want to perform thekitting internally at your BOD location or externally at a subcontractor. When DRP determines demandfor a kit, it reads the bill of material of the kit to determine and cover the dependent demands as well.

DRP also takes periods into account in which kit to stock is not possible for certain kits at certainlocations. You can decide whether you allow external procurement of the kits during these periods.

See also

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Service Parts Planning -> DistributionRequirements Planning (DRP) -> Kit to Stock.

______________________________________________________________SAP AG 31

SAP-System______________________________________________________________

Page 40: Release Notes for SAP Supply Chain Management Release SAP

1.2.8.11 SCM-APO-SPP-SDE Service Parts Deployment

1.2.8.11.1 Functions in Inventory Balancing (Enhanced)

Use

As of SAP SCM 7.0, new functions exist for inventory balancing in the following areas:

- Inventory balancing with unserviceable products

- Simulation of the inventory balancing service

- Stock in stock transport orders and intransit stock

- Manual confirmation of stock transport requisitions

- Use of pull deployment as an alternative to inventory balancing

Inventory balancing with unserviceable products

As of SAP SCM 7.0, there is a new planning service that performs inventory balancing with unserviceableproducts. If you are using the repair or buy function, customers might send unserviceable products todifferent locations of your bill of distribution (BOD) to have them repaired. Therefore, there can be excessstock at some locations (at which you possibly do not even repair products) and shortages at locations atwhich you repair unserviceable products. To balance these excesses and shortages, you can use the newplanning service. You can schedule the planning service regularly in planning service manager (PSM);additionally, the planning service is triggered by distribution requirements planning (DRP) if there are notenough unserviceable products for the repair or buy process at a location.

Simulation of the inventory balancing service

As of SAP SCM 7.0, you can simulate the inventory balancing service to check your planning results andadjust parameters and settings if necessary.

Stock in stock transport orders and intransit stock

Up to now, inventory balancing only took stock in stock transport orders (STOs) and intransit stock intoaccount if the STOs and the intransit stock were inside the shortage horizon. As of SAP SCM 7.0, you canspecify that inventory balancing also takes stock from STOs and intransit stock into account that isoutside the shortage horizon.

This makes sense, for example, if the inventory balancing service has created an STO to cover a shortage,but the STO is not inside the shortage horizon. Up to now, inventory balancing did not consider the stockin this STO in the next planning run and might have created another STO to cover the same shortage.That might lead to an excess at the location that originally had a shortage. As of SAP SCM 7.0, you candefine that inventory balancing takes stock from all STOs and all intransit stock into account. Then,inventory balancing does not create a second STO to cover the same shortage.

Manual confirmation of stock transport requisitions

Up to now, you could either decide to manually confirm all stock transport requisitions that have beencreated by the inventory balancing service or none. As of SAP SCM 7.0, you do not have to globallymake this decision any more but you can specify whether you want to confirm stock transport requisitionsin the inventory balancing service profile. As you can define more than one inventory balancing serviceprofile and include these service profiles in different planning profiles together with different selections,

______________________________________________________________SAP AG 32

SAP-System______________________________________________________________

Page 41: Release Notes for SAP Supply Chain Management Release SAP

you can, for example, decide for each product, whether you want to manually confirm stock transportrequisitions.

Use of pull deployment as an alternative to inventory balancing

As of SAP SCM 7.0, the BAdI: Define if Pull Deployment is a Valid Alternative to Inv. Balancing(/SAPAPO/SPP_REDEPL_CHK_PULLDEP) Business Add-In (BAdI) is available. You can use thisBAdI to check if pull deployment is a valid alternative to inventory balancing. The system calls this BAdIif there is a shortage at a location. Then, it decides if pull deployment from the parent is a valid alternativeto inventory balancing.

See also

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Service Parts Planning (SPP) -> InventoryBalancing and Simulation in Service Parts Planning.

1.2.8.11.2 Multi-Level Priority Tier Processing in Deployment (New)

Use

Up to now, you could only use two-level priority tier processing in deployment. In two-level tierprocessing, deployment only took a location and its direct child locations into account when coveringdemands according to priority tiers. Demands of other locations below the child location were allconsidered to be in the same priority tier.

As of SAP SCM 7.0, you can also use multi-level priority tier processing in deployment. Multi-levelpriority tier processing considers the demands of all locations of the BOD that are in the appropriatepriority tiers. When you use multi-level priority tier processing, deployment rolls up demands of the lowerlevels of the BOD to the second level of the BOD in a recursive algorithm to provide visibility of thedemands that are assigned to a priority tier with high priority of the whole BOD. Thus, multi-level prioritytier processing covers demands to which you have assigned high priority at lower levels of the BODbefore it covers demands to which you have assigned a lower priority at higher levels of the BOD.

See also

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Service Parts Planning (SPP) ->Deployment -> Planning Demand Fulfillment According to Priority Tiers -> Planning DemandFulfillment According to Multi-Level Tier Processing.

______________________________________________________________SAP AG 33

SAP-System______________________________________________________________

Page 42: Release Notes for SAP Supply Chain Management Release SAP

1.2.8.11.3 Functions in Deployment (Enhanced)

Use

As of SAP SCM 7.0, new functions exist for deployment in the following areas:

- Express shipment

- Stock in stock transport orders and intransit stock

- Determination of the time-related supply limit (TSL)

- Deployment locks

Express shipment

As of SAP SCM 7.0, you can define your own logic that the system uses to make an express shipmentdecision. You can define this own logic in the BAdI: Define Limits for Express Shipments(/SAPAPO/DEPL_EXPED_SHIP_LIMITS) Business Add-In (BAdI). The default implementation of thisBAdI contains the logic that has been used up to now and that is still used unless you define another logic.

Stock in stock transport orders and intransit stock

Up to now, deployment only took stock in stock transport orders (STOs) and intransit stock into account ifthe STOs and the intransit stock were inside the lead time. As of SAP SCM 7.0, you can specify thatdeployment also takes stock from STOs and intransit stock into account that is outside the lead time.

This makes sense, for example, if the inventory balancing service has created an STO that is not inside thelead time to cover a shortage at a location. Up to now, deployment did not consider the stock in this STOand might have created another STO to cover the same demand. That might lead to an excess at thelocation in question. As of SAP SCM 7.0, you can define that deployment takes stock from all STOs andall intransit stock into account. Then, deployment also takes the STO created by the inventory balancingservice into account, does not determine a demand, and thus does not create another STO.

Determination of the time-related supply limit (TSL)

As of SAP SCM 7.0, the BAdI: Determination of Parameters for the Time-Related Supply Limit(/SAPAPO/DEPL_TSL_PARAMETERS) BAdI is available. In this BAdI, you can define your own logicfor how the system determines the parameters Maximum Gross Demand for TSL and AdditionalGross Demand for TSL, on the basis of which deployment calculates the TSL.

Deployment locks

Up to now, you could only define a lock period during which you had to confirm stock transport ordersmanually. As of SAP SCM 7.0, you can also define reasons for deployment locks and assign these reasonsto a lock period.

See also

______________________________________________________________SAP AG 34

SAP-System______________________________________________________________

Page 43: Release Notes for SAP Supply Chain Management Release SAP

For more information, see SAP Library of SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Service Parts Planning (SPP) ->Deployment.

1.2.8.12 SCM-APO-SPP-PWL Worklist

1.2.8.12.1 Roles for Service Parts Planning (Enhanced)

Use

As of SAP SCM 7.0, the following new roles are available:

- Service Parts Planner (Worklist) (SAP_SCM_SPP_WORKLIST) With this role, you can access the worklist of a planner for Service Parts Planning (SPP). From thisworklist, a planner can navigate to all transactions that he or she needs to complete his or herworklist.

- Service Parts Customer (Worklist) (SAP_SCM_SPP_WORKLIST)With this role, your customers or dealers can access his or her worklist to display, change andconfirm data that is relevant to him or her.

As of SAP SCM 7.0, the following roles have been renamed:

Old name New name

Service Parts Monitoring (Customer) Service Parts Monitoring (Planner)

Service Parts Monitoring (Customer): Administration and Master Data Service Parts Monitoring(Planner): Administration and Master Data

Service Parts Monitoring (Customer): Expert Service Parts Monitoring (Planner): Expert

See also

For more information, see SAP Library for SAP Supply Chain Management (SAP SCM) under SAPAdvanced Planning and Optimization (SAP APO) -> Roles for SAP APO -> Roles for ServiceParts Planning (SPP).

1.2.8.13 SCM-APO-SPP-SFA Service Fill Analysis

1.2.8.13.1 Functions in Reporting and Monitoring (Enhanced)

______________________________________________________________SAP AG 35

SAP-System______________________________________________________________

Page 44: Release Notes for SAP Supply Chain Management Release SAP

Use

As of SAP SCM 7.0, new functions exist for monitoring Service Parts Planning (SPP) in the followingareas:

- Overdue documents

- ATP categories for the service fill monitor

- Service loss reason

- Supplier delivery performance rating

Overdue documents

As of SAP SCM 7.0, the planning service SPP_REP_DUE7 is available. This planning service determinesif the following document types contain overdue schedule lines:

- Purchase orders

- TPOP purchase orders

- Scheduling agreement releases

- Subcontract orders

- Refurbishment orders

- Production orders

- Stock transport orders

You can specify if you want the system to check all these document types or only some of them.Additionally, you can specify the number of days after which a certain document is considered as overdueand, in the BAdI: Define System Behavior if Orders/Schedule Lines are Overdue(/SCMB/SPLREP_PROCESS_OVERDUE) Business Add-In, you can define the system behavior in caseof overdue documents. In the standard implementation of the BAdI, the system creates an alert andrequests a supplier confirmation if it determines a purchase order (standard purchase order, TPOPpurchase order, or subcontracting purchase order) or a scheduling agreement release as overdue.

ATP categories for the service fill monitor

Up to now, the service fill monitor took only sales orders (ATP category BM) and deliveries (ATPcategory BR) into account. As of SAP SCM 7.0, you can specify which ATP categories meaning whichrequirements (customer orders, for example) and which fulfillment of these requirements (goods receipts,for example) you want the service fill monitor to take into account.

Service loss reasons and service loss categories

As of SAP SCM 7.0, the service loss reason Supplier Overdue is called Overdue Orders andSchedule Lines.

As of SAP SCM 7.0, you can define the order in which the system processes the overdue orders andschedule lines for this service loss reason and you can specify if the system groups these overdue ordersand schedule lines into sub-reasons.

Although the service loss reason is enhanced, the Overview Service Loss due to Supplier Late /Overdue (0SPL_C33_Q0001) query and the Service Loss Due to Supplier Late / Overdue(0SPL_DS39_Q0001) query are still available and show the same results that they have shown up to

______________________________________________________________SAP AG 36

SAP-System______________________________________________________________

Page 45: Release Notes for SAP Supply Chain Management Release SAP

now. However, as of SAP SCM 7.0, the following new queries are available for the enhanced service lossreason:

- Overview Service Loss Due to Overdue Orders or Overdue Schedule Lines(0SPL_C33_Q0002)

- Service Loss Due to Overdue Orders or Overdue Schedule Lines (0SPL_DS39_Q0002)

Supplier delivery performance rating

As of SAP SCM 7.0, supplier delivery performance rating (SDPR) also considers subcontracting purchaseorders when it rates the performance of your suppliers. In the respective objects of the BusinessIntelligence system, the system now differentiates between standard orders, TPOP orders, andsubcontracting purchase orders.

1.2.8.14 SCM-APO-SPP-INB Inbound Delivery Monitor

1.2.8.14.1 Functions in Reporting and Monitoring (Enhanced)

Use

As of SAP SCM 7.0, new functions exist for monitoring Service Parts Planning (SPP) in the followingareas:

- Overdue documents

- ATP categories for the service fill monitor

- Service loss reason

- Supplier delivery performance rating

Overdue documents

As of SAP SCM 7.0, the planning service SPP_REP_DUE7 is available. This planning service determinesif the following document types contain overdue schedule lines:

- Purchase orders

- TPOP purchase orders

______________________________________________________________SAP AG 37

SAP-System______________________________________________________________

Page 46: Release Notes for SAP Supply Chain Management Release SAP

- Scheduling agreement releases

- Subcontract orders

- Refurbishment orders

- Production orders

- Stock transport orders

You can specify if you want the system to check all these document types or only some of them.Additionally, you can specify the number of days after which a certain document is considered as overdueand, in the BAdI: Define System Behavior if Orders/Schedule Lines are Overdue(/SCMB/SPLREP_PROCESS_OVERDUE) Business Add-In, you can define the system behavior in caseof overdue documents. In the standard implementation of the BAdI, the system creates an alert andrequests a supplier confirmation if it determines a purchase order (standard purchase order, TPOPpurchase order, or subcontracting purchase order) or a scheduling agreement release as overdue.

ATP categories for the service fill monitor

Up to now, the service fill monitor took only sales orders (ATP category BM) and deliveries (ATPcategory BR) into account. As of SAP SCM 7.0, you can specify which ATP categories meaning whichrequirements (customer orders, for example) and which fulfillment of these requirements (goods receipts,for example) you want the service fill monitor to take into account.

Service loss reasons and service loss categories

As of SAP SCM 7.0, the service loss reason Supplier Overdue is called Overdue Orders andSchedule Lines.

As of SAP SCM 7.0, you can define the order in which the system processes the overdue orders andschedule lines for this service loss reason and you can specify if the system groups these overdue ordersand schedule lines into sub-reasons.

Although the service loss reason is enhanced, the Overview Service Loss due to Supplier Late /Overdue (0SPL_C33_Q0001) query and the Service Loss Due to Supplier Late / Overdue(0SPL_DS39_Q0001) query are still available and show the same results that they have shown up tonow. However, as of SAP SCM 7.0, the following new queries are available for the enhanced service lossreason:

- Overview Service Loss Due to Overdue Orders or Overdue Schedule Lines(0SPL_C33_Q0002)

- Service Loss Due to Overdue Orders or Overdue Schedule Lines (0SPL_DS39_Q0002)

Supplier delivery performance rating

As of SAP SCM 7.0, supplier delivery performance rating (SDPR) also considers subcontracting purchaseorders when it rates the performance of your suppliers. In the respective objects of the BusinessIntelligence system, the system now differentiates between standard orders, TPOP orders, andsubcontracting purchase orders.

______________________________________________________________SAP AG 38

SAP-System______________________________________________________________

Page 47: Release Notes for SAP Supply Chain Management Release SAP

1.2.8.15 SCM-APO-SPP-SHA Shortage Analysis

1.2.8.15.1 Functions in the Alert Monitor (Enhanced)

Use

As of SAP SCM 7.0, new functions exist for the Alert Monitor in the following areas:

- Statistical view

- Display of tab pages

- Alert types

Statistical view

As of SAP SCM 7.0, the statistical view of the alert monitor will be updated when an alert is deleted orconfirmed and when one or more alert parameters change.

Display of tab pages

As of SAP SCM 7.0, only these tab pages are displayed on the Alert Monitor screen that are relevant forthe selected alerts.

Alert types

As of SAP SCM 7.0, the following new alert types that are relevant for Service Parts Planning (SPP) willbe available:

Alert Type Description Category

7891 Order Created During Supplier Shutdown DRP Approval Rule

7892 Assignment of Calendar for Scaling to Location Changed Hist. DataMaint.

7893 Header Data of Calendar for Scaling ChangedHist. Data Maint.

7894 Calculation Rule of Calendar for Scaling Changed Hist. Data Maint.

7895 Error in XI Message Processing Hist. Data Maint.

7896 Customer Does Not Agree With Stocking / Destocking DecisionInventory Planning

7897 Net Demand During Freeze Horizon for ROB / Kit to Stock DRP

81 PSM Service Failed During Execution Planning Service Manager

82 PSM Finished with Errors Planning Service Manager

______________________________________________________________SAP AG 39

SAP-System______________________________________________________________

Page 48: Release Notes for SAP Supply Chain Management Release SAP

1.2.8.15.2 Functions in Reporting and Monitoring (Enhanced)

Use

As of SAP SCM 7.0, new functions exist for monitoring Service Parts Planning (SPP) in the followingareas:

- Overdue documents

- ATP categories for the service fill monitor

- Service loss reason

- Supplier delivery performance rating

Overdue documents

As of SAP SCM 7.0, the planning service SPP_REP_DUE7 is available. This planning service determinesif the following document types contain overdue schedule lines:

- Purchase orders

- TPOP purchase orders

- Scheduling agreement releases

- Subcontract orders

- Refurbishment orders

- Production orders

- Stock transport orders

You can specify if you want the system to check all these document types or only some of them.Additionally, you can specify the number of days after which a certain document is considered as overdueand, in the BAdI: Define System Behavior if Orders/Schedule Lines are Overdue(/SCMB/SPLREP_PROCESS_OVERDUE) Business Add-In, you can define the system behavior in caseof overdue documents. In the standard implementation of the BAdI, the system creates an alert andrequests a supplier confirmation if it determines a purchase order (standard purchase order, TPOPpurchase order, or subcontracting purchase order) or a scheduling agreement release as overdue.

ATP categories for the service fill monitor

Up to now, the service fill monitor took only sales orders (ATP category BM) and deliveries (ATPcategory BR) into account. As of SAP SCM 7.0, you can specify which ATP categories meaning whichrequirements (customer orders, for example) and which fulfillment of these requirements (goods receipts,

______________________________________________________________SAP AG 40

SAP-System______________________________________________________________

Page 49: Release Notes for SAP Supply Chain Management Release SAP

for example) you want the service fill monitor to take into account.

Service loss reasons and service loss categories

As of SAP SCM 7.0, the service loss reason Supplier Overdue is called Overdue Orders andSchedule Lines.

As of SAP SCM 7.0, you can define the order in which the system processes the overdue orders andschedule lines for this service loss reason and you can specify if the system groups these overdue ordersand schedule lines into sub-reasons.

Although the service loss reason is enhanced, the Overview Service Loss due to Supplier Late /Overdue (0SPL_C33_Q0001) query and the Service Loss Due to Supplier Late / Overdue(0SPL_DS39_Q0001) query are still available and show the same results that they have shown up tonow. However, as of SAP SCM 7.0, the following new queries are available for the enhanced service lossreason:

- Overview Service Loss Due to Overdue Orders or Overdue Schedule Lines(0SPL_C33_Q0002)

- Service Loss Due to Overdue Orders or Overdue Schedule Lines (0SPL_DS39_Q0002)

Supplier delivery performance rating

As of SAP SCM 7.0, supplier delivery performance rating (SDPR) also considers subcontracting purchaseorders when it rates the performance of your suppliers. In the respective objects of the BusinessIntelligence system, the system now differentiates between standard orders, TPOP orders, andsubcontracting purchase orders.

1.2.8.15.3 Functions in Shortage Analysis

Use

As of SAP SCM 7.0, new functions exist for the shortage analysis in the following areas:

- SPP Cockpit

- Product Detail

- Shortage Overview, Shortage Monitor, and Supplier Overview

______________________________________________________________SAP AG 41

SAP-System______________________________________________________________

Page 50: Release Notes for SAP Supply Chain Management Release SAP

- Sales Order View on the Shortage Monitor screen

SPP Cockpit

As of SAP SCM 7.0, the SPP Cockpit displays the following additional information:

- Replenishment indicator of the location product

- Information about the quantities and overdue quantities of unserviceable products, repaired products,and products that are part of the kit to stock process.

Product Detail

As of SAP SCM 7.0, the Product Detail screen contains several new fields and displays additionalinformation, mainly about unserviceable products and kits.

- Overview tab page

- As of SAP SCM 7.0, this tab page is structured into content areas (Product, LocationProduct, and Forecast/Demand, for example).

- As of SAP SCM 7.0, this tab page contains information about forecasted values and demandsas well as information about delivery schedules.

- As of SAP SCM 7.0, this tab page also contains information about unserviceable products.

- Product tab page

- As of SAP SCM 7.0, this tab page is structured into content areas.

- As of SAP SCM 7.0, this tab page contains information about the SPP planners that areassigned to the product.

- As of SAP SCM 7.0, this tab page contains information about alternative product numbers andproduct groups.

- As of SAP SCM 7.0, this tab page contains information about the repair and return time forunserviceable products, for example the initial warehous stock of unserviceable products andthe intransit stock of unserviceable products.

- External Procurement tab pageAs of SAP SCM 7.0, this tab page contains information about whether an external procurementrelationship is a subcontracting relationship.

- EP Schedule tab page

- As of SAP SCM 7.0, this tab page contains information about whether an external procurementrelationship is a subcontracting relationship.

- As of SAP SCM 7.0, this tab page contains information about refurbishment orders andproduction orders.

- Stock Transport Order tab pageAs of SA P SCM 7.0, this tab page contains information about whether a stock transport order hasbeen created for unserviceable products and whether a stock transport order is from an OEMlocation to a non-OEM location.

- Fixed Demand tab pageAs of SAP SCM 7.0, this tab page contains administrative information like who has created orchanged a fixed demand.

______________________________________________________________SAP AG 42

SAP-System______________________________________________________________

Page 51: Release Notes for SAP Supply Chain Management Release SAP

- Forecast and Inv. Planning tab pageAs of SAP SCM 7.0, if you select a virtual child location, this tab contains information about thereorder point and the maximum stock level of the virtual child location.

- Supersession tab pageAs of SAP SCM 7.0, this tab page contains information about serviceable and unserviceable stock aswell as about open quantities.

- Stock tab pageAs of SAP SCM 7.0, this tab page contains information about

- Stock at the contract packager

- Unserviceable and repaired stock

- Kits

- Excess stock

Shortage Overview, Shortage Monitor, and Supplier Overview

As of SAP SCM 7.0, the Shortage Overview screen, the Shortage Monitor screen, and the SupplierOverview screen display information about overdue quantities and order items of products that are part ofthe (internal or external) repair and kit to stock process.

Sales Order View on the Shortage Monitor screen

As of SAP SCM 7.0, you can decide whether you want to display the Location Product View and theSales Order View on the Shortage Monitor screen or whether you want to display only the LocationProduct View. If you decide not to display the Sales Order View, the system does not display theselection criteria that are sales-order-specific either.

Additionally, as of SAP SCM 7.0, the BAdI: Define Logic for Shortage Analysis/SAPAPO/SPP_SHORTAGE_ANALYSIS Business Add-In (BAdI) contains the new methodHIDE_SALES_ORDER_VIEW. In this method, you can define that certain users or business partners(suppliers, for example) cannot display the sales order view of the shortage analysis

1.2.9 SCM-APO-PPS Production Planning and Detailed Scheduling

1.2.9.1 Order Scheduling for Block Changes (Enhanced)

Use

As of SAP Supply Chain Management (SAP SCM) 7.0, you can execute automatic rescheduling of theorders in a block that you modify. Such an automatic rescheduling of orders is necessary to retain the link

______________________________________________________________SAP AG 43

SAP-System______________________________________________________________

Page 52: Release Notes for SAP Supply Chain Management Release SAP

between the block and its orders where possible.

Order rescheduling is available for the Enhanced Block Maintenance heuristic (SAP_CDPBP_03) in caseswhere a block is shortened, lengthened, deleted, or moved.

Lengthened Block

If a block is lengthened using the Enhanced Block Maintenance heuristic, this function automaticallyreschedules its orders. It also reschedules the subsequent blocks and their orders.

The scheduled orders of the subsequent blocks are rescheduled to their original blocks.

Shortened Block

If a block is shortened using the Enhanced Block Maintenance heuristic, the function automaticallyreschedules subsequent blocks and their orders as well. You must choose from one of the following threeoptions:

o Deallocate the non-fitting orders from the block

o Schedule the non-fitting orders infinitely within the block

o Schedule the non-fitting orders into another block according to the settings in the strategy profile

Deleted Block

If a block is deleted using the Enhanced Block Maintenance heuristic, the function reschedules thesubsequent blocks as well.

The scheduled orders of the subsequent blocks are rescheduled to their original blocks. The dates of theorders in relation to the block limits remain the same as before the block deletion.

Moved Block

Moving blocks involves assigning the block a later end date. You cannot change the start date or otherparameters.

In effect, when you move a block using the Enhanced Block Maintenance heuristic, the functionoverwrites any blocks scheduled until and including the new end date.

Effects on Customizing

You must set the Enhanced Block Maintenance heuristic to enable automatic order rescheduling to blockchanges. Choose SAP - Implementation Guide -> Advanced Planning and Optimization -> Supply ChainPlanning -> Production Planning and Detailed Scheduling (PP/DS) -> Heuristics -> Maintain Heuristics-> SAP_CDPBP_03 (Enhanced Block Maintenance) -> Details and select the Enable Reschedulingindicator. Alternately, from the Detailed Scheduling Planning Board, choose Settings -> Heuristics ->SAP_CDPBP_03 Enhanced Block Maintenance, and select the Enable Rescheduling indicator.

______________________________________________________________SAP AG 44

SAP-System______________________________________________________________

Page 53: Release Notes for SAP Supply Chain Management Release SAP

1.2.9.2 PP/DS Enhancements for the Process Industry

Use

As of SAP Supply Chain Management (SAP SCM) 7.0, production planning for the process industryincludes new master data and optimization functions.

You can now precisely model the production restrictions for consecutive operations in a simple manner.With the new resource networks, you define the permitted links between resources in a plant. In doing so,you define the actual production flow between the individual resources. This forms the basis for thecreation of a feasible production plan.

When the material flow is defined in the recipe within the SAP ERP system and transferred to SAP APO,this data is created as a product storage definition in SAP APO. Using these you can assign multiplecontainer resources to a product belonging to a production source of supply, such as PPM or PDS.

In planning with container resources, it is now possible to take the maximum volume of a containerresource into account. The system was previously unable to take account of this restriction in theplanning.

This new container planning is based on optimization. The optimization function has therefore beenenhanced such that it can now process all requirements, sourcing alternatives, resource networks, andproduct storage definitions of the products to be planned. Optimization creates a feasible production planon the basis of this data and creates new orders or changes existing orders for it.

Master Data

The following master data has been enhanced:

- Product Master

In the Product Master, the following new fields are available on the Demand tab screen under Pegging:

Resource Network Name: In this field, you specify the resource network with which the product can bemanufactured.

Resource Network Strategy: In this field, you specify whether pegging must take account of the assignedresource network.

- Resource

Resources have been enhanced so that you can now also maintain storage characteristics forsingle-activity resources. Previously this was only possible for multiactivity resources.

The Allow Multiple Products checkbox has also been added to the tab screen for storage characteristics.

- Resource Network

The master data in PP/DS has been enhanced by the addition of resource networks; you can create,change, display, or delete these. To access resource networks, in the SAP Easy Access menu, chooseAdvanced Planning and Optimization -> Master Data -> Resource -> Resource Network. Alternately, usethe /SAPAPO/RESNET transaction directly.

A new BAdI for resource networks, /SAPAPO/BADI_RESNET, has also been introduced. You can usethis BAdI to implement customer-specific changes for resource networks.

______________________________________________________________SAP AG 45

SAP-System______________________________________________________________

Page 54: Release Notes for SAP Supply Chain Management Release SAP

- Product Storage Definition

With the product storage definition, you can assign the source of supply of a product to components andcontainer resources. It is possible to assign several alternative resources. You can create the productstorage definition manually or have this done automatically at the time of the CIF transfer of the PPM orPDS data.

To access product storage definitions, in the SAP Easy Access menu, choose Advanced Planning andOptimization -> Master Data -> Product Storage Definition -> Product Storage Definition. Alternately,use the transaction /SAPAPO/STORDEF.

You could earlier transfer the data for the product flow created in SAP ERP to SAP APO only if usingPPM. As of SCM 7.0, you can now also transfer the product flow data to SAP APO if you work withPDS.

A new BAdI for product storage definition, /SAPAPO/BADI_PSD_DEFS, has also been introduced. ThisBAdI enables you to change the product storage definition if required.

Optimization

- Optimization Profile

The Resource Processing tab screen has been enhanced by the addition of the following fields:

- Consider Resource Networks

- Lowest Resource Network Priority

- Consider Storage Properties

- Finiteness Level

In addition, the Order Creation tab screen has been added. Here you specify whether optimization mustcreate new orders for certain location products. The following options are available:

- No order creation: Optimization only reschedules existing orders.

- Automatic location product selection: Order creation is active. All location products that can beproduced on the selected resources are selected for order creation.

- Location product selection profile: Order creation is active. The location products for ordercreation are defined by the given selection profile.

- New Optimization FunctionsThe optimization process has been enhanced by the addition of the following new functions:

- Container PlanningYou can now also use optimization to carry out container planning. You set up containerplanning in the Consider Storage Properties field in the optimization profile. Optimization cantake the following settings from the resource into account:Maximum Stock LevelSet Remaining Fill Level to ZeroAllow Multiple ProductsFor more information on restrictions, see SAP Note 1171154.

- Optimization with Resource NetworksResource networks are considered by the optimization process. You can use the Consider

______________________________________________________________SAP AG 46

SAP-System______________________________________________________________

Page 55: Release Notes for SAP Supply Chain Management Release SAP

Resource Networks field in the optimization profile to specify whether resource networks mustbe taken into account within an order or between orders, or in both cases.

Restriction:The Self-Reference indicator in the resource network master data is not considered by theoptimization process. Since this indicator is always set for optimization, the sequence ofoperations on the same resource is always allowed.

- Order CreationOptimization can now create new orders and adjust or delete existing ones. You make thesettings for these functions on the Order Creation tab screen in the optimization profile. Formore information on restrictions, see SAP Note 1155421.

Effects on System Administration

Dependencies and Restrictions in Optimization

- The current functionality is designed for buffer processes between different production stages as wellas simple mixing scenarios. The functionality in the optimizer cannot be used for reactor processesor chemical conversions (reactions) in container resources.

- Master data attributes of container resources, such as minimum fill level or replenishment level, arenot considered.

- Each order should use any container resource only once. Each violation of this rule can result inviolations of the maximum fill level.

- Deallocation of late operations is not compatible with container resource planning as the deallocatedoperations can cause missing amounts in the storage balance. Such a deallocation is automaticallydisabled if you activate the container resource planning. Deallocation on the right horizon and due tovalidity periods is still possible, but with resulting storage violations in the last postprocessing step,when operations are shifted backward and deallocated.

- Dependencies between orders: Any dependencies between orders besides pegging have a big impacton the container planning in performance and quality of the solution. Shelf life and maximumearliness are automatically disabled during the optimization run. You must avoid any externalconstraints, fixing of sequences, or prioritizations in your storage scenarios.

- The decomposition is automatically deactivated if you activate the planning of storages.

- Lot sizes: Lot sizes that are too large cause infeasibilities in the container planning. The optimizertries to reduce such infeasibilities. To achieve good planning quality, the lot sizes should match withthe storage capacities. One possible solution for this is the creation of orders with the optimizer.

- Campaign planning: Container planning cannot be combined with campaign optimization onbottleneck resources. If there are already existing campaigns that should be considered together withstorage constraints, the optimizer tries to achieve the uninterruptedness of campaigns but cannotguarantee it. Interruption of campaigns is not reported during optimization.

______________________________________________________________SAP AG 47

SAP-System______________________________________________________________

Page 56: Release Notes for SAP Supply Chain Management Release SAP

- Selection of resources and horizons: If you plan a container resource, the optimizer must have theorders that produce into storage and orders that consume from storage inside the optimizationproblem. No other valid solution is possible.

- Continuous material flow is not supported in connection with container resource planning. Allcontinuous material flows affecting container resources are handled as discrete for optimization.

- Time-dependent storage definitions or time-dependent storage usage parts of PPMs are notsupported.

- For detailed information and additional restrictions, see SAP Note 1171154.

1.2.9.3 SCM-APO-PPS-PPT Product Planning Table

1.2.9.3.1 PPT: Cross-location Planning Chart and Other Enhancements(Enhanced)

Use

As of SAP Supply Chain Management (SAP SCM) 7.0, the Product Planning Table (PPT) has beenenhanced to include cross-location planning and to improve the capabilities of characteristics handling.Various other enhancements have also been made to improve general usability and functioning in thework area.

Constraints

The following charts cannot be loaded multiple times:

- Product view (Single elements)

- Pegging Overview

- Product view (Quantity Graphic)

When the filter criteria consist of multiple values or ranges, only the output nodes are filtered. Input nodessuch as stock transport orders are not filtered. This limitation is due to the design of the underlyingliveCache function /SAPAPO/OM_PEGID_GET_IO. The same behavior is seen when you use Select viaCharacts in the /SAPAPO/RRP3 transaction.

The above limitation is not applicable to VC orders. In case of VC, only iPPE orders can be filtered. Thisis due to the design of the underlying function module MMRP_ORDER_FILTER.

The following features have not been included in this release:

- A separate transaction to access the Cross-location view: Periodic chart

- Capability to define additional rows using a BAdI (analogous to /SAPAPO/PPT_INFROW)

- Capability to define additional columns using a BAdI.

______________________________________________________________SAP AG 48

SAP-System______________________________________________________________

Page 57: Release Notes for SAP Supply Chain Management Release SAP

- The Product View: Periodic chart's capability to display only orders for selected sales order items incase of MTO.

Features

Cross-location Planning Chart

The PPT now includes a Cross-location view: Periodic chart that has cross-location planning capability.You access this chart using the standard PPT transaction /SAPAPO/PPT1.

This new chart takes the distribution relationships into account and works at a product level, that is,aggregated across all locations. You can drill down on product and location levels. It contains thefollowing key figures:

- Available Quantity

- Days' Supply

- Safety Stock

- Total Requirements

- Total Receipts

- ATD Issues (read-only)

- ATD Receipts (read-only)

The Total Requirements and Total Receipts figures are aggregated from various subordinate requirementor receipt quantities, which are also displayed in the chart.

A new tab screen in the user settings for allows you to define settings for the chart. Choose Settings ->User Settings and enter the required settings in the Cross Location View tab screen. Here you can definewhether:

- Total Requirements values are displayed aggregated or disaggregated

- Distribution Demands values are displayed aggregated or disaggregated

- Total Receipts values are displayed aggregated or disaggregated

- Total Distribution Receipts values are displayed aggregated or disaggregated

- In-house Production values are displayed aggregated or disaggregated

- External Procurement values are displayed aggregated or disaggregated

- Stock Transfer Orders (Demand) values are displayed or not.

- Stock Transfer Orders (Receipt) values are displayed or not.

- Scheduling Agreement Schedule Lines and Releases values are displayed if only orders exist.

- Values for ATD Issues and ATD Receipts are displayed

- Advanced Shipping Notification (ASN) is displayed

You can run PP/DS deployment for a selected product and location from the chart by clicking theDeployment button. You can also define the settings for deployment, for example, the deploymenthorizon, or whether stock transfer requisitions must be reduced.

To run the Demand Propagation heuristic directly, click Variable Heuristic above the chart, make the

______________________________________________________________SAP AG 49

SAP-System______________________________________________________________

Page 58: Release Notes for SAP Supply Chain Management Release SAP

required settings, and choose Heuristics.

Filters for Characteristics

The PPT now includes a filter that displays only those orders that match selected characteristics. Thisfilter is applicable to the following charts:

- Product view: Single elements

- Product View: Periodic

- Pegging Overview

This filter allows you to define ranges and multiple values for the characteristics, as well as to save thecharacteristics and their values as variants if necessary. To use this filter, choose the Filter byCharacteristics button.

You can get a proposal for the characteristics from a sales order by specifying a sales order profile, a salesorder, and an item. The system fills the characteristics from the sales order profile and reads the values forthose characteristics from the sales order item.

The sales order profile must define which characteristics from the sales order must be applied to the filterand which tolerances for the values must be applied (that is, the value of the sales order minus or plus adefined delta).

The following restrictions apply to the filter:

- Since not more than 5 characteristics can be maintained in the sales order profile, the filter alsoconsiders a maximum of 5 characteristics.

- Certain I/O nodes are not filtered by LiveCache.

Production Output

You can display the production output in a separate chart within Resource view: Periodic; this chart isread-only.

You can make the following new settings by choosing Settings -> User Settings -> Resources tab screen:

- Selecting the Display Total Output indicator displays a row for total output in the chart.

- In the Unit of Measurement field, choose the base unit of measurement for the production outputquantities.

Filter for Configurations

The Product View: Periodic chart of the PPT displays characteristic values if the product isconfiguration-relevant and if the requirements strategy is make-to-order. The characteristic values aredisplayed as green triangles with links to the details.

If forecasts with configurations are used, you can apply a filter for the configurations that has thefollowing features:

- You can filter according to the configuration defined in characteristic-based forecasting (CBF) forthe forecasts.

- You can release forecasts with variant configuration (VC) to a planning segment.

- Characteristics are displayed as defined in the consumption group. However, you can sort by orchange the sequence of the characteristics.

______________________________________________________________SAP AG 50

SAP-System______________________________________________________________

Page 59: Release Notes for SAP Supply Chain Management Release SAP

Display of Availability Date of Orders

You can now view the availability date of in-house production orders and external procurement orderseither inclusive or exclusive of the duration for goods receipt. This feature is available for the followingcharts:

- Product view: Periodic

- Product view: Single elements

- Product view: Quantity Graphic

- Cross-location view: Periodic

By default, the availability date is inclusive of the goods receipt duration. Click the AV button in thetoolbar to display the planned orders' availability date exclusive of the goods receipt duration. The systemalso replaces AV with a GR button, which you can click to return to the default setting.

Expanding and Collapsing Period Columns

You can now expand and collapse period columns without selecting the columns themselves. This featureis applicable only when the period category defined in the user settings is either SAP001, SAP002,SAP003, SAP004, or SAP006.

Multiple Loading for Different Location Products

You can now load the same chart multiple times for different location products. If you lock a particularchart using the Fix Chart button and select materials from the navigation tree, the chart is loaded with thesame selected materials every time. A maximum of three charts can be loaded in this manner.

This feature is only available for the following charts:

- Product view: Periodic

- Cross-location view: Periodic

- Resource view: Periodic

- Production view: Periodic

Revoking Status of Processed Products

Using the Processed button, you can manually revoke the Processed status of a product if a new planningfile entry is created.

Display of Sales Order

In the navigation tree to the left, click the Group button and select Sales Order. If you select a sales orderfrom the list, the system displays all orders that have the same account. This function applies only to salesorders with a make-to-order requirements strategy.

Order Display (Make-to-Order)

The Product view: Periodic chart displays only the orders for the selected sales order items in case of themake-to-order requirements strategy. Unlike in the Product view: Single Elements chart, the displayedorders are not restricted to the selected order item.

Restricted Selection of Products with Alerts

You can now make a restricted selection of only products with alerts. The alert profile as maintained inthe PPT settings must be used for this selection. For performance reasons, you must apply the restricted

______________________________________________________________SAP AG 51

SAP-System______________________________________________________________

Page 60: Release Notes for SAP Supply Chain Management Release SAP

selection criteria before selecting all products.

Selection of Components with Requirements

You can now opt to select only the components with requirements and not the output products. In thiscontext, components refer to the input nodes of the operations on the resource.

This option only applies to selection by resources. For performance reasons, you must apply the selectionchange before selecting the output products.

Extended Selection

You can now extend the selection to output products and components with requirements. This option onlyapplies to selection by resources.

Display of Current Stock

The current stock is now displayed in the Group menu in the navigation tree. You can define in the usersettings whether or not the stock should be displayed; choose Settings -> User Settings and enter therequired settings in the Navigation Tree tab screen.

Effects on Customizing

Sales order profiles can be defined and maintained in a new Customizing setting. In Customizing, chooseAdvanced Planning and Optimization -> Supply Chain Planning -> Production Planning and DetailedScheduling (PP/DS) -> Product Planning Table -> Maintain Sales Order Profile.

1.2.9.4 SCM-APO-PPS-HEU Heuristics

1.2.9.4.1 PP/DS Heuristics in Characteristics-based Cross-location Planning(Enhanced)

Use

As of SAP Supply Chain Management (SAP SCM) 7.0, you can carry out characteristics-basedcross-location planning. To enable this, the following new heuristics are available:

Heuristic for Interactive Sourcing Profiles (JJ_INT_SRC)

This heuristic allows you to interactively choose the sources of supply from which to source procurementproposals. You can choose from the displayed key resources and key components for each sourcelocation.

You must maintain interactive sourcing profiles (VC_PROF).

Demand Propagation Heuristic (SAP_PP_022)

This heuristic can be used in external procurement scenarios to derive the dependent demands for a

______________________________________________________________SAP AG 52

SAP-System______________________________________________________________

Page 61: Release Notes for SAP Supply Chain Management Release SAP

product in a source location, by propagating the demands for the product in all target locations in thesupply chain network. It can be executed for one level or across all levels in the supply chain network.

Delete Dependent Orders Heuristic (SAP_PP_026)

You can use this heuristic to delete all pegged dependent orders across BOM levels. This includes allsub-assemblies and purchase requisitions that are pegged to the selected order. The heuristic can beexecuted only at the order level.

Shelf-Life Propagation Heuristic (SAP_PP_025)

This heuristic enables you to propagate the minimum and maximum required shelf life values across thepegging network. This ensures that the required shelf life dates from the independent demands arepropagated to dependent demands throughout the pegging network.

The heuristic propagates the required shelf life values one level downward. To propagate the shelf lifeacross a network that includes in-house production orders or external procurement orders, this heuristicmust be invoked from within the MRP heuristic (SAP_MRP_001).

Propagation of Descriptive Characteristics (SAP_PP_023)

This heuristic allows you to propagate the descriptive characteristic values associated with a demandelement to the dependent demand or stock transfer requirement of the receipt element (planned order orstock transfer order) pegged to it.

Enhanced Heuristics

The following PP heuristics have been enhanced with an option to enable interactive sourcing:

- SAP_PP_001

- SAP_PP_002

- SAP_PP_003

- SAP_PP_004

When executed after enabling interactive sourcing, these heuristics display the interactive sourcing dialog.You can here choose the source of supply for the procurement proposals based on key resource andcomponent availability. The interactive sourcing dialog displays the utilization, capacity, and availablecapacity for resources and the product availability and stock for components.

The following service heuristics have been enhanced to reschedule stock transfer requisitions anddeployment confirmed stock transfer requisitions:

- SAP_PP_008 (Rescheduling: Bottom up for Conti-I/O)

- SAP_PP_009 (Rescheduling: Bottom Up)

- SAP_PP_010 (Rescheduling: Top Down)

Constraints

The capability of branching to the display of batches from the stock display has not been implemented inthis release.

______________________________________________________________SAP AG 53

SAP-System______________________________________________________________

Page 62: Release Notes for SAP Supply Chain Management Release SAP

1.2.9.4.2 PP/DS Deployment Heuristic (New)

Use

As of SAP Supply Chain Management (SAP SCM) 7.0, the new PP/DS Deployment Heuristic,SAP_PP_024, allows you to select the process to be executed for stock transfers during PP/DSdeployment. On deployment, the system reads the orders for the selection from LiveCache and the masterdata.

After production is complete, deployment determines which demands can be fulfilled by the existingsupply. If there are insufficient quantities available to fulfill the demand or if the quantities availableexceed the demand, PP/DS deployment makes adjustments to the plan created by the PP/DS planning run.

The deployment heuristic invokes the PP/DS deployment algorithm, which generates deployment stocktransfers based on the PP/DS stock transfers that were created during the PP/DS planning run. TheTransport Load Builder (TLB) then uses these deployment stock transfers to create transport loads, thusgenerating TLB shipments. The PP/DS deployment also enables characteristic-based deployment.

Distribution Plans

You can use this heuristic to create a distribution plan for one product at one location. Real-timedeployment does not take place. If the available quantities are insufficient to fulfill the demand, thesystem uses fair share rules to determine the distribution plan. Only pull deployment is applicable inPP/DS.

Quantity Confirmation within Order Segments

PP/DS deployment can now confirm quantities in order segments, such that the same document flow asfor (Make-to-stock) MTS orders is followed. The planning runs separately for each order segment.

Processing of Stock Transfers

PP/DS deployment has capabilities similar to Supply Network Planning (SNP) deployment. It confirmsquantities that can be transferred and changes the planned stock transfers accordingly. You can opt foreither of the following procedures on the planned PP/DS stock transfers:

- Delete: Enables the creation of deployment stock transfers and deletes all PP/DS stock transfers thatfall within the planning period, regardless of whether or not they could be confirmed during thedeployment run.

- Change: Enables the creation of deployment stock transfers and reduces the PP/DS stock transfersaccordingly.

- No Processing: Ensures that the system does not create any deployment stock transfers and does notreduce the existing PP/DS stock transfers. This option is for simulation purposes only. You can viewthe results in the log.

ATD quantity is calculated based on the ATI and ATR categories.

Deployment Horizon

______________________________________________________________SAP AG 54

SAP-System______________________________________________________________

Page 63: Release Notes for SAP Supply Chain Management Release SAP

The deployment horizon setting allows you to define the number of days the system must consider duringthe deployment calculation. Unless you process the deployment run in batch mode, using the backgroundjob scheduling function, the current date is taken as the start date for the run. This horizon is shorter thanthe SNP horizon since SNP is the input for deployment planning.

The existing SNP deployment function has been incorporated into a standard PP/DS heuristic,SAP_PP_024. This approach provides the following capabilities for PP/DS deployment:

- The heuristic can be called from the PP/DS Product View or started from the background.

- The heuristic fits into the Process Chain tool just like any other standard heuristic.

PP/DS deployment is different from SNP deployment in the following areas:

- Only pull distribution is allowed

- Fair share situations can only be resolved with Fair Share A and Fair Share X options

- The planning run uses only the new standard Planning Book 9APPDS_DEP which defines:

- A long-term daily bucket structure

- Macros relevant for this scenario only

- Categories of confirmed stock transfers can be seen at PP/DS Global Settings

Master Data Changes

The following new fields have been added to the PP/DS tab screen of the Product Master:

- Depl. Char. Prof.

- Fair Share Rule

- Pull Deployment Horizon

- Push Deployment Horizon

- SNP Checking Horizon

Effects on Customizing

Heuristic

Based on the /SAPAPO/HEU_PPDS_DEPLOYMENT algorithm, a new PP/DS Deployment Heuristic,SAP_PP_024, has been added. You use this heuristic to define the settings for the deployment horizonand the processing of stock transfers, both of which are described above; in Customizing, chooseAdvanced Planning and Optimization -> Supply Chain Planning -> Production Planning and DetailedScheduling (PP/DS) -> Heuristics -> Maintain Heuristics -> SAP_PP_024 to carry out these settings.

Deployment Characteristic Profiles

______________________________________________________________SAP AG 55

SAP-System______________________________________________________________

Page 64: Release Notes for SAP Supply Chain Management Release SAP

You can maintain PP/DS deployment characteristic profiles within the system. In Customizing, chooseAdvanced Planning and Optimization -> Supply Chain Planning -> Production Planning and DetailedScheduling (PP/DS) -> Deployment -> Maintain PP/DS Deployment Characteristics Profile.

1.2.10 SCM-APO-ATP Global Available-to-Promise

1.2.10.1 Backward Consumption (Enhanced)

Use

As of SAP SCM 7.0, you can specify the period consumption strategy. This strategy defines the sequencein which periods are to be consumed by product allocation during backward consumption.

Effects on Customizing

You specify the strategy in Customizing for SAP SCM under Advanced Planning and Optimization ->Global Available-to-Promise (Global ATP) -> Product Allocation -> Maintain Product AllocationGroup.

1.2.10.2 ATP Category (Enhanced)

Use

As of SAP SCM 7.0, you can specify an SAP category as a reference category. The system copiesattributes, such as the following, from the referenced category to a non-SAP category:

- Backorder processing allowed

- OLTP object type

- No ATP check allowed

- ATP check of open or confirmed quantity

This enables you to configure non-SAP categories to act like the referenced SAP categories.

______________________________________________________________SAP AG 56

SAP-System______________________________________________________________

Page 65: Release Notes for SAP Supply Chain Management Release SAP

Effects on Customizing

You can specify a reference category in Customizing for SAP SCM under Advanced Planning andOptimization -> Global Available-to-Promise (Global ATP) -> General Settings -> MaintainCategory.

1.2.10.3 Adoption of Scheduling Results (Changed)

Use

As of SAP SCM 7.0, the system reuses the scheduling results from the ATP check in the batch backorderprocessing and sends them to the OLTP system. This leads to a better system performance.

Effects on Existing Data

If you change the confirmation, you have to delete the scheduling results if you use one of the followinguser exits:

- EXIT_/SAPAPO/SAPLBOP_051

- EXIT_/SAPAPO/SAPLBOP_052

If you do not delete the scheduling results, they differ in the OLTP system from the confirmationsituation.

For more information, see the user exit documentation.

1.2.10.4 Subcontracting in MATP (Enhanced)

Use

As of SAP SCM 7.0, you can activate subcontracting for the multilevel ATP check (MATP) in theintegrated rule maintenance. Subcontracting is a form of procurement, in which the product to beprocured is manufactured by a supplier.

Effects on Existing Data

If you activate subcontracting, the system automatically sets the Stock transfer indicator and sets theStartProduction field to Production Directly.

______________________________________________________________SAP AG 57

SAP-System______________________________________________________________

Page 66: Release Notes for SAP Supply Chain Management Release SAP

1.2.11 SCM-APO-OPT Optimization

1.2.11.1 SCM-APO-OPT-BF Basic Functions

1.2.11.1.1 Remote Control and Communication Framework (Changed)

Use

In SAP SCM 7.0, the Remote Control and Communication Framework (RCCF) in SCM Basis has beenmoved into SAP Business Suite Foundation 7.01 (SAP_BS_FND 701). (RCCF replaces the OptimizerFramework of SAP Advanced Planning and Optimization (SAP APO)). In SAP APO, the previoustransaction codes and IMG activities are still available, but they now refer to the new user interfaces.

For more information, see the corresponding release note in SAP Business Suite Foundation 7.01.

1.2.12 SCM-APO-INT Interfaces

1.2.12.1 SCM-APO-INT-MD Master Data

1.2.12.1.1 SCM-APO-INT-MD-CLC Classes and Characteristics

1.2.12.1.1.1 Definition of Configuration Schema (Enhanced)

Use

As of SCM 7.0, you can define the configuration relevance for Characteristics-Dependent Planning(CDP) or variant configuration (VC) on client level or on product level. If you want to work with bothconfiguration procedures in one client, in the Setting field, choose Configuration on Product Level,and in the Default for Config. field, choose the configuration procedure as a default that is relevant forthe characteristics you are using for your planning.

______________________________________________________________SAP AG 58

SAP-System______________________________________________________________

Page 67: Release Notes for SAP Supply Chain Management Release SAP

You can also define that your forecast data is to be released with a configuration of its own. Select theRelease Forecast with Configuration checkbox, if you want to do the following:

- Release your forecast data from Demand Planning (DP) to Supply Network Planning (SNP) with aconfiguration of its own

- Transfer the orders with a configuration of their own back from SNP to DP.

For more information on the requirements for releasing forecast data with configuration, see the releasenote Forecast Release and Consumption with Configuration.

Effects on Customizing

You can make the settings as described above in Customizing for Master Data under DefineConfiguration Schema (CDP or Variant Configuration)

1.3 SCM-BAS SCM Basis

1.3.1 Structure Changes in the IMG of SCM Basis

Use

As of SAP SCM Basis 7.0, the structure of the Implementation Guide (IMG) has changed. You mustregenerate the project IMGs to transfer these changes.

New IMG Structure Nodes and IMG Activities

- IMG for Planning Service Manager (PSM)

- Assign Selection Types to Application

- IMG for Master Data Layer

- Master Data Layer -> BAdI: Modify Generated Partner ID

- IMG for Integration

- Integration -> Basic Settings for Data Transfer -> Activate CIF Incremental Load

- Integration -> Basic Settings for Creating the System Landscape -> Define SLD Dataof Business Systems

- IMG for Master Data

- Location -> Configuration for Alternative Location Identifiers

- Enterprise Services -> Business Add-Ins (BAdIs) -> Product Data Maintenance ->

______________________________________________________________SAP AG 59

SAP-System______________________________________________________________

Page 68: Release Notes for SAP Supply Chain Management Release SAP

Material -> BAdI for MaterialSCMSimpleByIdentifyingElementsQueryResponse

Changed IMG Activities

...

Transferred IMG Activities

...

Deleted IMG Activities

- In the area of Routing Guide

- Define Transportation Zone Hierarchy

- The whole area Remote Control and Communication Framework has been deleted including thefollowing IMG activities:

- Edit Destinations

- Make Settings for Experts

- Under Enterprise Services, the IMG activity Configure Idempotent Services has been deleted.Instead, this IMG activity and other IMG activities for enterprise services are now available underCross-Application Components -> Processes and Tools for Enterprise Applications ->Enterprise Services.

1.3.2 SCM-BAS-INT Interfaces

1.3.2.1 SCM-BAS-INT-MD CIF Master Data

1.3.2.1.1 Initial Data Transfer via Core Interface (CIF) (Enhanced)

Use

As of release SAP SCM 7.0 you can improve the effectiveness of initial data transfer via Core Interface(CIF) by activating incremental data transfer in Customizing. The incremental data transfer is valid for thefollowing master data objects:

- Product master data

- Location product master data

- Production data structure (PDS) (in SAP APO only)

______________________________________________________________SAP AG 60

SAP-System______________________________________________________________

Page 69: Release Notes for SAP Supply Chain Management Release SAP

If you do not activate the incremental data transfer, the initial data transfer stops in the event of an errorduring the processing of a queue even if the error only affects one of the objects in the queue. If the datatransfer is scheduled in a background job, then the background job is canceled. You must correct the errorand start the transfer of all objects again.

If you activate the incremental data transfer, the system transfers all blocks of correct master data objectsin a CIF queue so that you only have to retransfer blocks with errors. Due to the lower volume of objectsto be processed again, the retransfer becomes more effective.

To be able to use incremental data transfer, you must activate the Enhanced Initial Data Transfer(CA_CIF_INILOAD_01) business function. This business function is available as of EnhancementPackage 4 for SAP ECC 6.0.

Effects on Customizing

To activate the incremental data transfer, use the Customizing activity Activate Incremental DataTransfer. For more information, see Customizing for SCM Basis under Integration -> Basic Settings forData Transfer -> Activate Incremental Data Transfer.

See also

For more information about the initial data transfer via CIF, see SAP Library for SAP Supply ChainManagement on SAP Help Portal at http://help.sap.com -> Overview of SAP Documentation -> SAPBusiness Suite -> SAP Supply Chain Management -> SAP SCM 7.0 -> Application Help EN -> SAPSupply Chain Management (SAP SCM) -> SAP Advanced Planning and Optimization (SAP APO) ->Integration via Core Interface (CIF) -> Technical Integration -> Core Interface (CIF) -> Data Transfer-> Initial Data Transfer.

1.3.3 SCM-BAS-AMO Alert Monitor

1.3.3.1 Alert Monitor (Enhanced)

Use

As of release SAP SCM 7.0, to simplify and improve the usability of alert profile maintenance, the AlertMonitor provides a new user interface that allows you to configure profiles, create new profiles, or selectexisting profiles and modify, delete or transport them.

Application-specific and overall profiles are maintained in separate group boxes, which illustrates therelationships between the two types of profiles.

In order to control access to alert profiles, the Alert Monitor checks authorization before the requestedaction is performed. The user administrator can specify which users are allowed to work with the AlertMonitor, as well as the actions they can perform, and the profiles they are allowed to create, modify,

______________________________________________________________SAP AG 61

SAP-System______________________________________________________________

Page 70: Release Notes for SAP Supply Chain Management Release SAP

delete or transport.

The processing of type Order in Past Production Planning and Detailed Scheduling (PP/DS) alert types ismoved to liveCache in order to improve the performance of the alert determination process.

Effects on System Administration

To maintain the alert profiles the user needs to have adequate authorization. The profile maintenanceauthorization is checked against authorization object C_APO_APRF, which enables the systemadministrator to control maintenance activities on the alert profile level.

1.3.4 SCM-BAS-PSM Planning Service Manager

1.3.4.1 Functions for Planning Service Manager (PSM) (Enhanced)

Use

As of SAP SCM Basis 7.0, the following new functions will exist for the Planning Service Manager(PSM):

- Alerts for the PSM

- Display and selection of planning profiles

Alerts for the PSM

If a planning service failed or has been finished with errors, you could only display information about thefailure and the errors in the PSM application log. As of SAP SCM Basis 7.0, the system creates an alert ifa planning service fails or has been ended with errors so that a planner is immediately informed and cancorrect the errors.

Display and selection of planning profiles

Up to now, you could only display planning profiles on the Define Planning Profile screen by selectingone of the existing planning profiles. As of SAP SCM Basis 7.0, there is a new screen for displayingplanning profiles. On this new Display Planning Profile screen, you can not only enter specific planningprofiles, but you can also search for planning profiles by entering certain selection criteria as a serviceprofile or a trigger group.

______________________________________________________________SAP AG 62

SAP-System______________________________________________________________

Page 71: Release Notes for SAP Supply Chain Management Release SAP

1.3.5 SCM-BAS-TDL Transaction Data Layer

1.3.5.1 Triggers for Service Parts Planning (Enhanced)

Use

As of SAP SCM 7.0, the following new triggers are available for Service Parts Planning (SPP):

- SPP: Calendar Period Change (SPP_CLD_CHG)This trigger triggers the realignment service for calendar changes if the calendar master data hasbeen changed.

- SPP: Anticipated Demand Coverage for Seasonal Product (SPP_SEASONAL_PROD)This trigger triggers the anticipated demand coverage if the forecast of a seasonal product has beenchanged.

- Not Enough Unserviceable Stock (SPP_UNSRV_INSUFF)This trigger triggers inventory balancing with unserviceable products if not enough unserviceableproducts are available to cover the demand for unserviceable products.

- STO with Unserviceable Stock Created (SPP_UNSRV_STO_CRTD)This trigger triggers distribution requirements planning (DRP) if the inventory balancing withunserviceable stock service has created a stock transport order with unserviceable stock.

- STO Creation with Unserviceable Stock Failed (Cap. Constraints)(SPP_UNSRV_STO_NO_CAP)This trigger is set for inventory balancing with unserviceable stock if no stock transport order couldbe created due to capacity constraints.

1.3.6 SCM-BAS-MD Master Data

1.3.6.1 SAP SCM Basis Monitoring with CCMS (New)

Use

As of SAP NetWeaver 7.0 including SAP enhancement package 1 and SAP SCM Basis 7.0, you can usethe predefined monitor set SAP SCM Basis Monitor Templates in the monitoring architecture of theComputing Center Management System (CCMS). The CCMS Monitoring Architecture is a framework

______________________________________________________________SAP AG 63

SAP-System______________________________________________________________

Page 72: Release Notes for SAP Supply Chain Management Release SAP

available in SAP NetWeaver into which monitoring and administration functions can be added.

The SAP SCM Monitor Templates monitor set includes the following:

CIF Master Data Queue MonitorThe CIF Master Data Queue Monitor allows you to monitor inbound and outbound queues for the SAPCore Interface (CIF).

Effects on System Administration

To use the SAP SCM Basis Monitor Templates monitor set as a template for your own monitor, copythe desired monitor and adapt it to your needs. If you run CCMS from a central system to monitor yoursystem landscape, set up system connections with your SAP SCM systems. For more information, see theSAP NetWeaver documentation on SAP Help Portal at http://help.sap.com under SAP Library -> SAPNetWeaver Library -> SAP NetWeaver by Key Capability -> Solution Life Cycle Management byKey Capability -> Solution Monitoring -> Monitoring in the CCMS.

1.3.6.2 SCM-BAS-MD-TL Transportation Lanes, TDL Profile and PlanningCost

1.3.6.2.1 Maintaining Means of Transport (Changed)

Use

In SCM Basis 7.0, the Customizing activity for maintaining means of transport has been changed:

- The field External Means of Transport (/SAPAPO/TR_EXTTTYPE_FLG) has been renamed toMultiresource.

- The field Number of External Vehicle Resources (/SAPAPO/TR_EXTTTYPE_NUM ) has beenrenamed to Number of Individual Resources.

For more information, see the Customizing for SCM Basis under Master Data -> Transportation Lane ->Maintain Means of Transport.

______________________________________________________________SAP AG 64

SAP-System______________________________________________________________

Page 73: Release Notes for SAP Supply Chain Management Release SAP

1.3.7 SCM-BAS-RCC Remote Control and Communication Framework

1.3.7.1 Remote Control and Communication Framework (Deleted)

Use

As of SAP SCM Basis 7.0, the Remote Control and Communication Framework (RCCF) is available inSAP Business Suite Foundation 7.01 (SAP_BS_FND 701). Therefore, this function (including thetransactions in the area menu and the Customizing activities) has been deleted in SAP SCM Basis.

For more information, see the corresponding release note in SAP Business Suite Foundation 7.01.

1.4 SCM-EWM Extended Warehouse Management

1.4.1 Cross-Docking (Enhanced)

Use

As of Release 7.0, you can use new processes in the area of cross-docking to execute a planned oropportunistic cross-docking.

- In the area of planned cross-docking, you can use merchandise distribution alongside the existingtransportation cross-docking. If you want to use merchandise distribution, a prerequisite is that youuse SAP enhancement package 4 for SAP ERP 6.0 with business function Retail, CD/FT_EWMIntegration, and your system is defined as an SAP Retail system.For a planned cross-docking, the decision for whether cross-docking has to be performed is madebefore the goods arrive at the warehouse. You can use merchandise distribution to plan and managethe flow of merchandise from a vendor to a warehouse, and then on to the store or customer.Merchandise distribution supports push and pull processes, and allows you to carry outcross-docking in the warehouse.Various processes are used to distribute the goods to the recipients, for example, merchandisecross-docking, recipient -driven flow-through, or product-driven flow-through.You can manually start a quantity adjustment for the flow-through processing methods. From theSAP Easy Access menu, choose Extended Warehouse Management -> Delivery Processing ->Inbound Delivery -> Merchandise Distribution: Maintain Quantity Adjustment (Flow-Through).In a recipient-driven flow-through process, you can use a business add-in (BAdI) to automatically

______________________________________________________________SAP AG 65

SAP-System______________________________________________________________

Page 74: Release Notes for SAP Supply Chain Management Release SAP

unpack the higher-level handling unit at the pick point work center.

- In the area of opportunistic cross-docking, you can use an opportunistic cross-docking, which istriggered by Extended Warehouse Management (EWM), alongside the existing push-deployment orpick from goods receipt. The decision for whether cross-docking has to be performed is made in thewarehouse during warehouse task creation, that is, after the arrival of the incoming goods or releaseof the outbound delivery order. Opportunistic cross-docking, which is triggered by EWM, supportspush and pull processes, and also allows you to carry out cross-docking in the warehouse.

- You can use work center determination for cross-docking. On the SAP Easy Access screen, chooseExtended Warehouse Management -> Master Data -> Work Center -> Determine Work Center forCross-Docking.

Effects on Customizing

- If you want to use merchandise distiribution, you maintain the required IMG activities inCustomizing for EWM as described under Basic Settings for Merchandise Distribution.

- If you want to modify the quantity calculation for the quantity adjustment in the flow-throughscenario, you use the BAdI: Quantity Adjustment BAdI.

- If you want to automatically unpack the higher-level handling unit at the pick point work center in arecipient-driven flow-through process, you use the BAdI: Unpack Higher-Level Handling Unit atWarehouse Task Confirmation BAdI.

- If you want to use opportunistic cross-docking, which is triggered by EWM, you do the following:

- Maintain the required IMG activities in Customizing for EWM as described under BasicSettings for EWM-Triggered Opportunistic Cross-Docking.

- Activate and adjust the inbound-driven process using the BAdI: Activate and AdjustInbound-Driven Cross-Docking Process BAdI.

- Activate and adjust the outbound-driven process using the BAdI: Activate and AdjustOutbound-Driven Cross-Docking Process BAdI.

See also

For more information, see SAP Library for EWM in SAP Help Portal under http://help.sap.com.

1.4.2 SAP Extended Warehouse Management: Create User (new)

Use

As of enhancement package 1 of SAP NetWeaver 7.0 the system can automatically create a user, create abusiness partner, and assign authorizations (roles) to the user in SAP Extended Warehouse Management(SAP EWM). You can distinguish between the following use cases:

______________________________________________________________SAP AG 66

SAP-System______________________________________________________________

Page 75: Release Notes for SAP Supply Chain Management Release SAP

- SAP ERP Human Capital Management (SAP HCM) is part of your system landscape and you haveactivated labor management in SAP EWM

- SAP HCM is part of your system landscape and you have not activated labor management in SAPEWM

In the first use case, you can transfer the data of your employees from SAP HCM to SAP NetWeaverIdentity Management. Here, the system creates identities for the employees. These identities are thenprovisioned to SAP EWM. Before provisioning them the system administrator must do the following:

- The system administrator must assign SAP EWM roles that are used for labor management to thebusiness roles in SAP NetWeaver Identity Management. The system administrator then assigns theidentities to the business roles and provisions the identities to SAP EWM.

- Note that the SAP EWM roles must have been assigned a warehouse number at anorganizational level that is relevant for labor management for the identities to be used in labormanagement.

When the system administrator provisions the identities to SAP EWM, the system creates a userwith the respective SAP EWM role, a business partner (BP) with a Processor business partner role,and a Central Person that manages the user ID, the personnel number, and the BP data.

In the second use case, the system administrator can assign any SAP EWM role to the business role inSAP NetWeaver Identity Management. When the system administrator provisions the data to SAP EWM,the system only creates a user with the respective SAP EWM role. The system does not create a BP.

Prerequisites

- You are using SAP NetWeaver Identity Management 7.1 under license.

- To allow a background user to access SAP EWM from SAP NetWeaver Identity Management, asystem administrator must assign the /SCWM/IDM_EWM_INTEGRATION role to the backgrounduser. In addition, the system administrator should assign theSAP_BC_SEC_IDM_COMMUNICATION role the background user to allow user management androle assignment through SAP NetWeaver Identity Management.

1.4.3 Structure changes in the EWM IMG

Use

As of SAP EWM 7.0, the structure of the implementation guide (IMG) of SAP EWM has changed. Totransfer these changes to the project IMGs, you must regenerate the project IMGs.

Deleted IMG Activities

- In the area Master Data -> Shipping & Receiving

______________________________________________________________SAP AG 67

SAP-System______________________________________________________________

Page 76: Release Notes for SAP Supply Chain Management Release SAP

- Prerequisites for Using Goods Receipt and Shipping

- In the area Goods Issue Process -> Outbound Delivery

- Define EWM-Specific Settings for Item Types

New IMG Structure Nodes

- In the area Master Data ->

- Production Supply

- In the area Goods Issue Process -> Outbound Delivery ->

- Production Supply

- In the area Cross-Process Settings -> Warehouse Task ->

- Define Storage Groups for Layout-Oriented Storage Control

- In the area Cross-Process Settings -> Cross-Docking (CD) ->

- Planned Cross-Docking with the Merchandise Distribution subnode

- Opportunistic Cross-Docking with the EWM-triggered opportunistic Cross-Docking subnode

- In the area Cross-Process Settings -> Resource Management ->

- Control Data

- In the area Monitoring ->

- Graphical Warehouse Layout

- In the area Business Add-Ins (BAdIs) for Extender Warehouse Management -> Internal WarehouseProcesses -> Resource Management ->

- Resource Execution Constraints (REC) Control

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Cross-ProcessSettings ->

- Cross-Docking (CD) with the Planned Cross-Docking subnode and the OpportunisticCross-Docking subnode

- Under the Planned Cross-Docking subnode the Merchandise Distribution subnode

- Under the Opportunistic Cross-Docking subnode the EWM-triggered opportunisticCross-Docking subnode

- Under the EWM-triggered opportunistic Cross-Docking subnode the EWM-triggeredopportunistic Cross Docking Inbound subnode and the EWM-triggered opportunistic CrossDocking Outbound subnode

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Monitoring ->

- Graphical Warehouse Layout (GWL)

New IMG Activities

- In the area Master Data -> Production Supply ->

- Maintain Product Group Type for PSA Assignment

______________________________________________________________SAP AG 68

SAP-System______________________________________________________________

Page 77: Release Notes for SAP Supply Chain Management Release SAP

- In the area Goods Issue Process -> Outbound Delivery -> Production Supply ->

- Maintain Settings for Aut. Goods Issue for Production Supply

- Post Goods Issue for Consumption Posting

- In the area Cross Process Settings -> Cross-Docking (CD) -> Planned Cross-Docking ->Merchandise Distribution ->

- Basic Settings for Merchandise Distribution

- Define Adjustment Profile

- Define Adjustment Method

- Define Merchandise Distribution Process for Warehouse Process Type

- In the area Cross Process Settings -> Cross-Docking (CD) -> Opportunistic Cross-Docking ->EWM-triggered opportunistic Cross-Docking ->

- Basic Settings for EWM-triggered opportunistic Cross-Docking

- Activate EWM-triggered opportunistic Cross-Docking

- In the area Cross-Process Settings -> Resource Management ->

- Define Queue Types

- In the area Cross-Process Settings -> Resource Management -> Control Data ->

- Define Resource Execution Constraints (REC)

- Assign Resource Execution Constraints to REC Storage Group

- In the area Monitoring -> Graphical Warehouse Layout ->

- Define GWL Object Category

- Define GWL Object

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Master Data ->Product

- BAdI: Search Help for Entitled

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Master Data ->Work Center -> Adjust User Interface for Work Center ->

- BAdI: Method called After Save

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Goods ReceiptProcess -> Putaway Strategies ->

- BAdI: Filter and Sort Possible Storage Bins

- BAdI: Near to Fixed Bin: Determine Fixed Bin

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Internal WarehouseProcesses -> Resource Management -> Resource Executions Constraints (REC) Control ->

- BAdI: Handle Situation if Storage Group in not Accessible for Resource

- BAdI: Calculate Resource Leaving Time from REC Storage Group

______________________________________________________________SAP AG 69

SAP-System______________________________________________________________

Page 78: Release Notes for SAP Supply Chain Management Release SAP

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Internal WarehouseProcesses -> Resource Management -> Processing ->

- BAdI: RF: Resource Management Task Interleaving

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Cross-ProcessSettings -> Warehouse Task -> Confirmation of Warehouse Task ->

- BAdI: Unpack Higher-Level Hansling Unit at Warehouse Task Confirmation

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Cross-ProcessSettings -> Cross-Docking (CD) -> Planned Cross-Docking -> Merchandise Distribution ->

- Notes on Implementation

- BAdI: Quantity Adjustment

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Cross-ProcessSettings -> Cross-Docking (CD) -> Opportunistic Cross-Docking -> EWM-triggered opportunisticCross-Docking -> EWM-triggered opportunistic Cross Docking Inbound ->

- Notes on Implementation

- BAdI: Activate and Adjust Inbound Driven Cross Docking Process

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Cross-ProcessSettings -> Cross-Docking (CD) -> EWM-triggered opportunistic Cross-Docking -> EWM-triggeredopportunistic Cross Docking Outbound ->

- Notes on Implementations

- BAdI: Activate and Adjust Outbound Driven Cross Docking Process

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Monitoring ->Graphical Warehouse Layout (GWL) ->

- Notes on Implementation

- BAdI: Extend Context Menu

- BAdI: Change Display of GWL

- BAdI: Function on Mouse Click

- BAdI: Define Additional Marker

- In the area Cross-Process Settings -> Shipping & Receiving -> General Settings

- Activate Parallel Processing for Unloading WTs

- In the area Cross-Process Settings -> Goods Movement for Delivery ->

- BAdI. Select and Sort Stock for Consumption Posting Delivery

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Interfaces -> ERPIntegration

- BAdI: Generation of PSA Name to be Used in EWM

- In the area Business Add-Ins (BAdIs) for Extended Warehouse Management -> Interfaces -> ERPIntegration -> Goods Movement -> ERP Goods Movement Interface ->

______________________________________________________________SAP AG 70

SAP-System______________________________________________________________

Page 79: Release Notes for SAP Supply Chain Management Release SAP

- BAdI. Enhancement of the ERP Stock ID Mapping

- In the area Master Data -> Shipping & Receiving

- Define Means of Transport

- In the area Material Flow System (MFS) -> BAdIs for the Material Flow System

- BAdI: Accept Wrongly Located HU at Communication Point (CP)

Reassigned IMG Activities

- IMG of Cross-DockingYou can find the following IMG activity in the IMG for EWM under Cross-Docking (CD) ->Planned Cross-Docking ->

- Basic Settings for Transportation Cross-Docking (TCD)This IMG activity was previously located directly under Cross-Docking (CD). This structurenode was enhanced with the Planned Cross-Docking subnode.

You can find the following IMG activity in the IMG for EWM under Cross-Docking (CD) ->Opportunistic Cross-Docking ->

- Basic Settings for PD and Pick From GRThis IMG activity was previously located directly under Cross-Docking (CD). This structurenode was enhanced with the Oppoprtunistic Cross-Docking subnode.

- IMG of Maintain Transportation ModeYou can find the following IMG activities in the IMG for EWM under Master Data -> Shipping &Receiging

- Maintain Transportation ModeThis IMG activity was previously located under SCM Basis -> Master Data -> TransportationLane. This structure node is still available.

1.4.4 Material Flow System (MFS)

Use

As of SCM 7.0, MFS allows you to do the following:

- Specify an MFS server group on which the MFS processes can run

- Track and trace the execution of the MFS action function modules provided by SAP using theapplication log

______________________________________________________________SAP AG 71

SAP-System______________________________________________________________

Page 80: Release Notes for SAP Supply Chain Management Release SAP

- Reuse the example implementations offered by SAP to achieve an equal distribution of products inaisles of an automatic high rack during putway. Additionally, the status of the resources is taken intoaccount during putaway and picking in these example implementations. The BAdIs and exampleimplementation classes are as follows:

- BAdI /SCWM/EX_CORE_PTS_FILT_SORT, method FILT_SORT, example implementationclass /SCWM/CL_EI_CORE_PTS_FILT_SORT

- BAdI /SCWM/EX_MFS_ACT_WT_CONF, method NEW_DEST, example implementationclass /SCWM/CL_EI_MFS_ACT_WT_CONF

- BAdI /SCWM/EX_CORE_RMS_DETERMINE, method DETERMINE, exampleimplementation class /SCWM/CL_EI_CORE_RMS_DETERMINE

1.4.5 Graphical Warehouse Layout (New)

Use

As of Release 7.0, you can use the graphical warehouse layout (GWL) in the warehouse. You can use theGWL to display Customizing and master data of the warehouse and the status of warehouse activities. Italso provides users with intuitive application menus, and allows users to check both the Customizing andthe warehouse activity data, changing it if required. For example, users can check the data consistency ofmaster data.

Effects on System Administration

If you use the GWL standard objects, you must have installed a SAP Graphical User Interface (SAP GUI)7.10 or higher. For more information, see the SAP Service Marketplace underhttp://service.sap.com/patches.

Effects on Customizing

If you want to define own GWL objects and GWL object categories, you make the following settings inCustomizing for EWM under Monitoring -> Graphical Warehouse Layout:

- Define GWL Object Category

- Define GWL Object

See also

______________________________________________________________SAP AG 72

SAP-System______________________________________________________________

Page 81: Release Notes for SAP Supply Chain Management Release SAP

For more information, see the Customizing for EWM under Monitoring -> Graphical Warehouse Layout.

For more information, see SAP Library for Extended Warehouse Management under Monitoring ->Graphical Warehouse Layout.

1.4.6 Integration of Production Supply of EWM into Production Planning in ERP

Use

As of SCM 7.0, you can use SAP Extended Warehouse Management in connection with an ERP systemto store and stage products used for production by transporting them to a production supply area (PSA).The products have to be picked in the warehouse and moved to the PSA. After transporting the productsto the PSA, the stock can be consumed on the basis of a production order.

There are several ways to provide components that are required for a manufacturing order:

- Pick parts/release order parts: The products that are needed as components for an individual order(pick parts) or for multiple orders (release order parts) have to be staged in the PSA in time and inthe required quantity.

- Crate parts/kanban: Products that are often used in the production area are provided independentlyfrom the existing orders. The warehouse is responsible for filling containers when requested by theproduction.

The following functions are available for EWM 7.0 and ERP EHP4:

- Maintaining the new object production supply area (PSA) in EWM to stage products

- Staging of pick parts from EWM for process and production orders in ERP

- Staging of release order parts from EWM for process and production orders in ERP

- Staging of crate parts. This process is initiated in EWM

- Consumption (goods issue) of staged components in EWM

- Canceling goods issue (GI) of staged components from ERP

- Staging with Kanban via stock transfer from EWM

- Staging with Kanban via external procurement and goods receipt (GR) into EWM

- Staging with Kanban via in-house production and GR into EWM

- Staging with Kanban via consumption to cost center from EWM

- GR for repetitive manufacturing from ERP into EWM

- Document-related cancellation for repetitve manufacturing into EWM

- Document-neutral cancellation for repetitive manufacturing into EWM

______________________________________________________________SAP AG 73

SAP-System______________________________________________________________

Page 82: Release Notes for SAP Supply Chain Management Release SAP

See also

- For more information about Extended Warehouse Management, see SAP Library under ExtendedWarehouse Management --> Goods Issue --> Production Supply.

- For more information about the ERP system, see SAP Library under SAP ERP --> SAP ERPEnhancement Packages --> Business Function Sets and Business Functions --> Enterprise BusinessFunctions --> Logistics --> Production Planning and Control --> EWM Integration intoManufacturing.

1.4.7 Additional Functions in Radio Frequency (RF)

Use

As of SCM 7.0, you have the following additional functions in your RF transactions:

- Query for HU Stock Overview: This transaction provides an opportunity to display the content ofthe whole HU at a glance.

- Pick Point Process: The pick point process at a work center is now RF-supported. You can createpick-handling units, send the pick-handling units to the next location, such as the goods issue area,and send the stock HU back to a storage type. To assist you in identifying the correct packagingmaterial, you can have a workload overview of your current distribution group.

- System-guided processing: Within the system-guided processing you now have the followingadditional options:

- Using semi-system-guided processing, the selected warehouse order is not assigned to theresource. The system sends the worker to a bin and allows him or her to select any HU.

- Using task interleaving helps you to increase efficiency by reducing the travel time of theresources in general and the travel time without load.

- Resource Execution Constraints (REC): With this function, you can limit the number of workingresources per resource type. This prevents the collision (disturbing) of different resources in thewarehouse area.

______________________________________________________________SAP AG 74

SAP-System______________________________________________________________

Page 83: Release Notes for SAP Supply Chain Management Release SAP

1.4.8 Additional Functions for Warehouse Order Processing

Use

As of SCM 7.0, you can also do the following in warehouse order processing:

- Use process-oriented storage control for internal movements

- Add a validity time frame and user-specific settings for application logs

- HU Denial:

- Make exceptions for bin denial at HU level, if a source HU has been defined

- Pick from alternative HUs in the same bin

- Change the stock ID in the packing screen of the inbound delivery

- Use the report /SCWM/DLV_CONF_UPG_XPRA to move the document types and item types fromthe old database tables (SAP EWM 2007) to the new database tables (EWM 7.0).

- Use the following monitor enhancements:

- Block storage bins in the warehouse monitor:Block storage bins for putaway and stock removal with a single methodRemove block on storage bins for putaway and stock removal with a single method

- Selection criterion for empty HUs:Within node Stock and Bin -> Storage Bin -> HUs in the monitor, there is an additionalselection criterion "empty", enabling a user to select empty HUs only

- There are three new methods in the monitor node Stock and Bin -> Storage Bin -> HUs:Delete HU: Delete an HU including its sub-HUs; stock will be unpackedCreate warehouse task for HU: Navigate to the transaction /SCWM/ADHUQuit storage control: Only works for storage processes for internal movements

- Use new BAdI methods:

- Extension in Putaway Strategy Near Fixed Bin:New BAdI method to select and sort the fixed bins that are to be takenas reference for the new reserve bin (including an example implementation)

- Extension in Work Center:New BAdI method to change data after saving for HUs

______________________________________________________________SAP AG 75

SAP-System______________________________________________________________

Page 84: Release Notes for SAP Supply Chain Management Release SAP

1.4.9 SCM-EWM-MON Monitoring

1.4.9.1 SAP EWM Monitoring with CCMS (New)

Use

As of SAP NetWeaver 7.0 including SAP enhancement package 1 and SAP Extended WarehouseManagement (SAP EWM) 7.0, the predefined monitor set SAP EWM Monitor Templates in themonitoring architecture of the Computing Center Management System (CCMS) provides additionalmonitoring templates and monitoring tree elements. The CCMS Monitoring Architecture is a frameworkavailable in SAP NetWeaver into which monitoring and administration functions can be added.

The SNC Monitor Templates monitor set includes the following:

- CIF Master Data Queue MonitorThe CIF Master Data Queue Monitor allows you to monitor inbound and outbound queues for theSAP Core Interface (CIF).

- EWM MonitorThe EWM Monitor allows you to monitor inbound and outbound queues for external and internalmessage processing.

Effects on System Administration

To use the EWM Monitor Templates monitor set as a template for your own monitor, copy the desiredmonitor and adapt it to your needs. If you run CCMS from a central system to monitor your systemlandscape, set up system connections with your EWM system. For more information, see the SAPNetWeaver documentation on SAP Help Portal at http://help.sap.com under SAP Library -> SAPNetWeaver Library -> SAP NetWeaver by Key Capability -> Solution Life Cycle Management byKey Capability -> Solution Monitoring -> Monitoring in the CCMS.

1.5 SCM-EM Event Management

1.5.1 Structure Changes in IMG for SAP Event Management

Use

As of SAP Event Management 7.0, the structure of the Implementation Guide (IMG) for SAP EventManagement has changed. To copy these changes to the project IMGs, you must regenerate the projectIMGs.

New IMG Structure Nodes

______________________________________________________________SAP AG 76

SAP-System______________________________________________________________

Page 85: Release Notes for SAP Supply Chain Management Release SAP

- Settings for SAP Object Event Repository

- Business Add-Ins (BAdIs)The two BAdIs BAdI: Pre- or Postprocess EPCIS EPCISDocument Messages and BAdI: Pre-or Postprocess EPCIS Poll Messages have been moved to the new BAdI node.

Renamed IMG Nodes

- The IMG node Settings for SAP Object Event Repository (SAP OER) is now called Settings for SAPObject Event Repository.

New IMG Activities

- Settings for SAP Object Event Repository

- Define EPCIS Extensions

- Define Number of Allowed Subscriptions

- Maintain Allowed Destinations for EPCIS Subscriptions

- Define Number of Tries for Callback

- Business Add-Ins (BAdIs) -> BAdI: Pre- or Postprocess EPCIS Get Query Names Messages

- Business Add-Ins (BAdIs) -> BAdI: Pre- or Postprocess EPCIS Get Standard VersionMessages

- Business Add-Ins (BAdIs) -> BAdI: Pre- or Postprocess EPCIS Get Subscription IDs Messages

- Business Add-Ins (BAdIs) -> BAdI: Pre- or Postprocess EPCIS Get Vendor Version Messages

- Business Add-Ins (BAdIs) -> BAdI: Pre- or Postprocess EPCIS Subscribe Messages

- Business Add-Ins (BAdIs) -> BAdI: Pre- or Postprocess EPCIS Unsubscribe Messages

Renamed IMG Activities

- The IMG activity Settings for SAP Object Event Repository -> Business Add-Ins (BAdIs) -> BAdI:Pre- or Postprocess EventCaptureNotification Messages is now called BAdI: Pre- or PostprocessEPCIS EPCISDocument Messages.

- The IMG activity Settings for SAP Object Event Repository -> Business Add-Ins (BAdIs) -> BAdI:Pre- or Postprocess BAdI: Pre- or Postprocess EventQuery Messages is now called BAdI: Pre- orPostprocess EPCIS Poll Messages.

______________________________________________________________SAP AG 77

SAP-System______________________________________________________________

Page 86: Release Notes for SAP Supply Chain Management Release SAP

1.5.2 SAP Business Information Warehouse Interface (Changed)

Use

As of Release 7.0, you can define an optional external document type for each BI data collection groupavailable for the data in the SAP object event repository. This document type, which corresponds to thebusiness transaction type in the EventCaptureNotification, is then used by the system for each report.

If you do not specify an external document type, the system automatically uses the first businesstransaction type that is sent in an event capture notification for a specific ID as default.

For more information, see Customizing under Event Management -> Setting for SAP Object EventRepository -> SAP Business Information Warehouse Interface -> Make Settings for BI Data CollectionGroups.

1.5.3 SAP Object Event Repository Complies with EPCIS 1.0 Specification(New)

Use

As of Release 7.0, SAP object event repository complies with the "EPC Information Services (EPCIS)Version 1.0 Specification" provided by EPCglobal Inc.

To be compliant with this specification, you must use managed web services through SAP NetWeaverProcess Integration (SAP NetWeaver PI).

1.5.4 Other interfaces

Use

As of Release 7.0, the following EPCIS services are available:

______________________________________________________________SAP AG 78

SAP-System______________________________________________________________

Page 87: Release Notes for SAP Supply Chain Management Release SAP

- GetQueryNames

- GetStandardVersion

- GetVendorVersion

1.5.5 EventCaptureNotification Service (Enhanced)

Use

As of Release 7.0, the EventCaptureNotification Service supports quantity events for SAP object eventrepository in SAP Event Management. Quantity events can be used, for example, to report inventorylevels of a product.

In SAP NetWeaver Process Integration (SAP NetWeaver PI) the quantity events are located in namespacehttp://sap.com/xi/PTA for SAP Event Management, and in namespace http://sap.com/xi/AIN for SAPAuto-ID Infrastructure.

EventCaptureNotification supports UIIs and custom-defined IDs.

You can use a managed web service through SAP NetWeaver PI to execute an EventCaptureNotificationService.

As of Release 7.0, the Capture Interface fully supports the EPCIS extension concept. You have tomaintain Customizing settings for every extension field that is to be supported. For more informationabout EPCIS extensions, see Customizing under Event Management -> Settings for SAP Object EventRepository -> Define EPCIS Extensions.

1.5.6 Poll Service (Enhanced)

Use

EPCIS: SimpleEventQuery (Enhanced)

______________________________________________________________SAP AG 79

SAP-System______________________________________________________________

Page 88: Release Notes for SAP Supply Chain Management Release SAP

As of Release 7.0, the SimpleEventQuery supports the following new parameters:

- WD_readPoint

- WD_bizLocation

- HASATTR_fieldname

- EQATTR_fieldname_attrname

- MATCH_epcClass

- EQ_quantity

- GT_quantity

- GE_quantity

- LT_quantity

- LE_quantity

As of Release 7.0, the SimpleEventQuery supports EPC patterns. The following parameters support notonly pure identity format for the value, but also the pure identity pattern format:

- MATCH_epc

- MATCH_parentID

- MATCH_anyEPC

As of Release 7.0, SimpleEventQuery supports Unique Item Identifiers (UIIs) and custom-defined IDs.

EPCIS: SimpleMasterDataQuery (New)

As of Release 7.0, a new query called SimpleMasterDataQuery is available. It is based on the sameinterface, which is the Poll Interface, as the SimpleEventQuery, and supports the following queryparameters:

- vocabularyName

- includesAttribute

- includeChildren

- attributeNames

- EQ_name

- WD_name

- HASATTR

- EQATTR_attrname

- maxElementCount

Web Service

You can use a managed web service through SAP NetWeaver Process Integration (SAP NetWeaver PI) toexecute a SimpleEventQuery or SimpleMasterDataQuery.

EPCIS: Sending Poll Queries to other systems

______________________________________________________________SAP AG 80

SAP-System______________________________________________________________

Page 89: Release Notes for SAP Supply Chain Management Release SAP

SAP object event repository can execute an on-demand Poll Query to another SAP object event repositorythrough SAP NetWeaver PI. It can also execute a web service-based on-demand Poll Query to an externalEPCIS system through SAP NetWeaver PI.

EPCIS Extensions

As of Release 7.0, the Poll Interface fully supports the EPCIS extension concept. You have to maintainCustomizing settings for every extension field that is to be supported.

Effects on Customizing

You have to define EPCIS extensions in Customizing under Event Management -> Settings for SAPObject Event Repository -> Define EPCIS Extensions.

1.5.7 Roles for SAP Object Event Repository (New)

Use

As of Release 7.0, there are two new roles for SAP object event repository:

- SAP_EM_OER_USER: for unrestricted use of EPCIS services

- SAP_EM_OER_PARTNER: for restricted use of EPCIS services

In the standard, both roles are authorized to call all EPCIS services.

1.5.8 Subscriptions (New)

Use

As of Release 7.0, SAP object event repository supports subscriptions for existing queries. You can nowregister for the Simple Event Query via subscription, and receive periodic results via the EPCIS QueryCallback Interface.

To this effect, the following three methods and synchronous message interfaces have been added to theEPCIS Query Control Interface:

______________________________________________________________SAP AG 81

SAP-System______________________________________________________________

Page 90: Release Notes for SAP Supply Chain Management Release SAP

- subscribe

- unsubscribe

- getSubscriptionIDs

You can define the number of allowed subscriptions and the number of tries for callback.

The Query Callback Interface is the path by which an EPCIS service delivers standing query results to aclient.

SAP object event repository only supports HTTP and HTTPS binding. AS2 binding is not supported.

SAP NetWeaver Process Integration

The Event Capture Interface in SAP NetWeaver Process Integration (SAP NetWeaver PI) can now dealwith subscriptions.

There are separate message interfaces and proxies for each query control method. The message interfacesare based on new external definitions that are available on PI using the original XML schemas providedby EPCIS. The fault message types that are related to the subscription are provided as external definitionsand are used in the appropriate message interfaces.

1.5.9 Alternative Display Formats for URNs (Enhanced)

Use

As of Release 7.0, in the web interface (ABAP WebDynpro) you can display the different components oravailable master data attributes of a URN instead of the URN of the location.

Example: You can display the master data attributes of a business location, for example site sublocation(SSL) or site sublocation type attribute (SLLTA), instead of the URN.

As of Release 7.0, alternative display formats for URNs in the web interface are configured for thefollowing attributes of the PTA visibility process:

- Business location

- Outbound delivery number

- Ship-from location

- Ship-to location

______________________________________________________________SAP AG 82

SAP-System______________________________________________________________

Page 91: Release Notes for SAP Supply Chain Management Release SAP

Effects on Customizing

As of Release 7.0, ID mapping types 07 (Map Internal Format to Descriptive Format ) and 08 (MapInternal Format to Descriptive Format (Description)) are available in Customizing under SAP EventManagement -> Event Messages, Status Queries, and Web Interface -> Web Interface -> ConfigureFields For User Profiles.

1.5.10 SCM-EM-MGR Event Manager

1.5.10.1 SCM-EM-MGR-EVP Event Processing

1.5.10.1.1 Web Interface (Enhanced)

Use

As of SAP Event Management 7.0, several enhancements are available in the Web interface (WebDynpro ABAP). In general, the Web interface (Web Dynpro ABAP) now supports almost all thefunctions that are available for the Web interface (classic). The Web interface (classic) will not bedeveloped further, but is still supported. We recommend that you use the Web interface (Web DynproABAP). In the following, you can find the most important enhancements of the Web interface (WebDynpro ABAP):

- On the SAP Easy Access screen, you can choose a fast entry that displays the available services butdoes not offer an option to query data. For example, a carrier only needs to report back actual eventsand should not be able to query data.

You can generate a URL link and use it for one of the following:

- To log on to the Web interface (Web Dynpro ABAP)

- To display a specific event handler without first logging on to the Web interface (Web DynproABAP).You can use a direct link option to access the details of an event handler without logging on toSAP Event Management. When you send event messages, you sometimes want SAP EventManagement to create an alert that relates to data for a certain event handler. In this case, youcan use a direct link to allow the recipient of the alert to easily access the data for the eventhandler without logging on to SAP Event Management.

- If you assign a selection, a display and, an event message profile to a user profile and have set theDocument Flow indicator, you have to check if you need to maintain different user profiles. Formore information, see Define User Profiles.

- You can define the sequence in which the Web interface is to display the status values of an statusattribute.

______________________________________________________________SAP AG 83

SAP-System______________________________________________________________

Page 92: Release Notes for SAP Supply Chain Management Release SAP

Effects on Customizing

- If you want to use the direct link option, you maintain a hyperlink that appears in the alert inCustomizing for SAP Event Management under Define Alert Framework Integration to SAP EventManagement.

- If necessary, maintain different user profiles in Customizing for SAP Event Management underDefine User Profiles.

- If you want to define the sequence in which the Web interface is to display the status values of astatus attribute, you maintain the sequence in Customizing for SAP Event Management under DefineStatus Attributes.

See also

For more information about the Alert Framework, see Customizing for SAP Event Management underReactions to Event Messages -> Define Alert Framework Connection -> Define Alert FrameworkIntegration to SAP Event Management.

For more information, see SAP Library for SAP Event Management on SAP Help Portal athttp://help.sap.com.

1.6 SCM-ICH Supply Network Collaboration

1.6.1 Structure Changes in the IMG of SAP SNC

Use

As of SAP Supply Network Collaboration 7.0 (SAP SNC 7.0), the structure of the Implementation Guide(IMG) has changed. You must regenerate the project IMGs to transfer these changes.

Reassigned IMG activities

- Purchase OrderThe following IMG activities that were under Purchase Order -> Approval Process -> ApprovalProcess without Tolerances are now part of the Make General Purchase Order Settings IMGactivity under Purchase Order:

- Create Approval Profiles

- Assign Approval ProfilesThe organisational activity Set Up Approval Process under Purchase Order -> ApprovalProcess is now under Purchase Order.

Deleted IMG activities

______________________________________________________________SAP AG 84

SAP-System______________________________________________________________

Page 93: Release Notes for SAP Supply Chain Management Release SAP

- Purchase OrderThe Purchase Order -> Approval Process node has been deleted.The Purchase Order -> Approval Process -> Approval Process without Tolerances node hasbeen deleted.

New IMG activities

- ExceptionsThe IMG activity Activate Alert Types under Exceptions -> Alert Type Activation is new.

- URL DeterminationThe IMG activity Determining URLs under Basic Settings -> URL Determination is new.

- Quick ViewThe IMG activity Configure Quick View under Basic Settings -> User Interfaces is new.

- User AdministrationThe following IMG activities under Master Data -> User Administration are new:

- Configure User Administration

- Maintain Welcome E-Mail Texts

- Maintain E-Mail Texts for Password Re-Set NotificationsThe following IMG activities under Business Add-Ins (BAdIs) for SAP SNC -> Master Data ->User Administration are new:

- BAdI: Enhance Logic After New User Creation

- BAdI: Create User Name for New User

- BAdI: Set Validity for New User

- Identity ManagementThe IMG activities under Master Data -> Integration with Identity Management are new.The IMG activity under Business Add-Ins (BAdIs) for SAP SNC -> Master Data -> BAdI:Determination of Leading Business Partner for Identity Management is new.

- PromotionThe IMG activity Define Expected Promotion IDs under Demand -> Promotion is new.

- File TransferThe following IMG activities under Tools -> File Transfer are new:

- Make Settings for Global Constants

- Define Default User for a Download Profile

- Determine Accepted E-Mail Addresses for File Upload

- Maintain E-Mail Texts

- Determine E-Mail Texts

- Determine Error Control of the File Upload

- Maintain Job SchedulingThe following IMG activities under Business Add-Ins (BAdIs) for SAP SNC -> Tools -> FileTransfer are new:

______________________________________________________________SAP AG 85

SAP-System______________________________________________________________

Page 94: Release Notes for SAP Supply Chain Management Release SAP

- BAdI: Read Inbound E-Mail

- BAdI: Purchase Order Interface

- BAdI: ASN Publish Control

- BAdI: Due List for Purchasing Documents

- BAdI: Due List for Planned Receipts

- BAdI: Order Forecast Collaboration Interface

- BAdI: SMI Planned Receipt

- Processing Inbound and Outbound MessagesThe following IMG activities under Business Add-Ins (BAdIs) for SAP SNC -> Basic Settings-> BAdIs for Message Interfaces (Outbound XML Messages) are new:

- BAdI for ManufacturingWorkOrderOrderProductionProgressNotification_Out

- BAdI for PurchaseOrderERPRequest_V1_OutThe following IMG activity under Business Add-Ins (BAdIs) for SAP SNC -> Basic Settings-> BAdIs for Message Interfaces (Inbound XML Messages) is new: BAdI forPurchaseOrderERPReplenishmentOrderCollaborationNotification_InThe following IMG activity under Business Add-Ins (BAdIs) for SAP SNC -> Basic Settings-> Processing Inbound and Outbound Messages -> BAdI: Validation of the MessageHeader (Inbound).

- VisibilityThe following IMG activity under Basic Settings -> Visibility is new: AssignPartner-Dependent Selection Modes to Applications.

- Purchase OrderThe IMG activity Make General Settings for Purchase Orders under Purchase Order is new.The IMG activity BAdI: Modify Approved Manufacturer Parts List Transfer under BusinessAdd-Ins (BAdIs) for SAP SNC -> Master Data is new.

Renamed and Changed IMG activities

- Projected Stock, SNIThe IMG activity Define Profiles for the Projected Stock has been renamed to Define Profilesfor the Projected Stock and the SNI Demand

- ExceptionsThe IMG activity Update the Quantities and Statuses of ROs and ASNs has been changed andrenamed to Configure Processing of Inbound ProductActivityNotification Data. In addition, theIMG activity has been moved from Exceptions -> Data Import Controller to Supply NetworkCollaboration -> Basic Settings -> Processing Inbound Outbound Messages.

______________________________________________________________SAP AG 86

SAP-System______________________________________________________________

Page 95: Release Notes for SAP Supply Chain Management Release SAP

1.6.2 Quick View (New)

Use

As of Supply Network Collaboration (SAP SNC) 7.0, you can use the quick view as your entry screen tothe SAP SNC Web applications. The quick view displays application-specific key figures. The key figuresindicate tasks you need to complete for various order documents, for example purchase orders that need tobe confirmed. On the quick view, the system groups key figures into building blocks. Each building blockcontains key figures that are relevant to a particular application. The system splits the key figures by aspecific split criterion that breaks the key-figure bars into segments, for example, by age, last change date,and so on. You can personalize the quick view so that it displays the building blocks on a global, businesspartner, or user level.

To complete daily tasks, you can navigate from a key-figure bar on the quick view to the relevant SAPSNC Web application.

In the standard system, we deliver building blocks and key figures for the following supplier collaborationscenario applications:

- Purchase Order

- Advanced Shipping Notification

- Invoice

- Scheduling Agreement Release

- Work Order

To access the quick view, on the SAP SNC Web UI, choose Exceptions -> Quick View.

Effects on Customizing

If you want to configure the quick view in a different way from the default that we deliver, you can assignbuilding blocks at a global, business partner, or user level in Customizing for SAP Supply NetworkCollaboration under Basic Settings -> User Interfaces -> Configure Quick View.

1.6.3 Selection Using Product Group and Product Group Type (New)

Use

______________________________________________________________SAP AG 87

SAP-System______________________________________________________________

Page 96: Release Notes for SAP Supply Chain Management Release SAP

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the Product Group and Product GroupType selection fields were added to the following Web screens:

- Forecast Overview

- Forecast Parameters

- Short-Term Forecasting

- Forecast Details

- Sales Forecast Details - Product View

- Promotion Planning

- Create Promotions

- Replenishment Order Overview

- Replenishment Order History

- ASN Overview

- ASN History

- Product Extension

- Location Product Extension

- Location Product Status

- Assign Rounding Unit to Product

1.6.4 SCM-ICH-MD Master Data

1.6.4.1 Inventory Management (Changed)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, inventory management has been enhanced: Alllocation products are now stored with a new key for the batch number.

In addition, the reports for creating and deleting inventory data ( /SCA/DM_INV_CREATION,/SCA/DM_DELETE_INV) have been enhanced a follows:

- A new field for batch numbers has been added.

______________________________________________________________SAP AG 88

SAP-System______________________________________________________________

Page 97: Release Notes for SAP Supply Chain Management Release SAP

- You can select the new Query (Batch Aggregation) option. In this case, the system displays theinventory data of location products according to your selection criteria. In the display of the resultsscreen, however, it aggregates all the inventory that differs with regard to the batch number, but forwhich all other keys are the same.

1.6.4.2 Creating Users with Identity Management (New)

Use

As of SAP NetWeaver 7.0 Enhancement Package 1 and SAP Supply Network Collaboration (SAP SNC)7.0, you can generate users in SAP SNC automatically using SAP NetWeaver Identity Management. Thefollowing use cases apply:

- Creation of users and business partners for employeesA user administrator creates new employees in the Human Resources (HR) system. These employeeswork for the business partner running SAP SNC or, if SAP SNC is hosted by a third party, theemployees work for the leading business partner in SAP SNC collaboration. The user creation in theHR system triggers the automatic creation of a new internal identity in the SAP NetWeaver IdentityManagement system. A user administrator assigns a business role to this new identity. As a result,SAP NetWeaver Identity Management triggers automatic user and business partner creation in SAPSNC for the employee.

- Creation of users and business partners for external usersA user from an external business partner requests access to the SAP SNC system. The useradministrator creates a new external identity in SAP NetWeaver Identity Management for theexternal user. Using SAP NetWeaver Identity Management, the new user of the external businesspartner is distributed to SAP SNC.

In all use cases, SAP NetWeaver Identity Management triggers the creation of a new user in SAP SNC asfollows:

- Generation of a user in SAP SNC

- Generation of a business partner of type Person and with Internet User role, which is thenassigned to the user

- Assignment of the business partner of type Person to a business partner of type Organization thatrepresents the business partner to whom the user belongs

- Assignment of a visibility profile to the user (optional)

In addition, you can also change and delete users centrally with SAP NetWeaver Identity Management.

______________________________________________________________SAP AG 89

SAP-System______________________________________________________________

Page 98: Release Notes for SAP Supply Chain Management Release SAP

Prerequisite

You are using the SAP NetWeaver Identity Management 7.1 product under license.

Effects on System Administration

With the use of SAP NetWeaver Identity Management, automatic creation of new users is triggered by theSAP NetWeaver Identity Management system, so there is no need to create users manually in SAP SNC.

To be able to use SAP NetWeaver Identity Management, you must make an initial load of all existing userIDs, roles, visibility profiles, and business partner IDs from SAP SNC to the SAP NetWeaver IdentityManagement system.

Effects on Customizing

To be able to use SAP NetWeaver Identity Management, you must make the following settings inCustomizing:

- You have defined which business partner of type Organization represents the leading businesspartner. The leading business partner is the customer in supplier collaboration or the supplier incustomer collaboration. To do this, you use the Customizing activity Define Leading BusinessPartner for Identity Management.

- If there a multiple business partners of type Organization that represent the leading business partnerin the system, you implement the Business Add-In (BAdI) /SCA/IDM_PARTNER_OWN with theCustomizing activity BAdI: Determination of Leading Business Partner for Identity Management.

- You have mapped the form of address in Human Resources (HR) to the form of address of thebusiness partner using the Customizing activity Assign HR Form of Address Key to Form ofAddress Keys of Business Partner.

See also

For more information, see SAP Library for SAP NetWeaver Identity Management on SAP Help Portal athttp://help.sap.com/nw71.

1.6.4.3 Location Product Status (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, functions for the location product status havebeen enhanced as follows:

- Automatic changes to the location product status can be customized.

- Maintenance of the location product status has been enhanced.

Automatic Change of the Location Product Status

In previous releases, SAP SNC automatically set the location product status from Active to Inactive or

______________________________________________________________SAP AG 90

SAP-System______________________________________________________________

Page 99: Release Notes for SAP Supply Chain Management Release SAP

from Inactive to Discontinued when the following conditions were met during inbound processing:

- The 2_MISSING_EAN/UPC validation check is active.

- The ProductActivityNotification message does not contain any data for this location product.

As of SAP SNC 7.0, you can determine in Customizing whether SAP SNC automatically sets the status toInactive or Discontinued when the above conditions are met.

Maintenance of the Location Product Status

In previous releases, you could only maintain the status of single location products one at a time on theLocation Product Status Web screen. As of SAP SNC 7.0, you can create, change, or delete the statusof multiple location products in a mass maintenance. Moreover, on the Location Product Status Webscreen, you can now search for location products by product group and by product group type.

Effects on Customizing

To prevent SAP SNC from automatically setting the location product status to Inactive or Discontinued,in Customizing, select the No Inactive Status checkbox . For more information, see Customizing forSupply Network Collaboration under Basic Settings -> Processing Inbound and OutboundMessages -> Configure Processing of Inbound ProductActivityNotification Data. In the standardsystem, the No Inactive Status checkbox is not selected, that is, inbound processing behaves as inprevious releases.

1.6.4.4 Roles (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, you can use the following new roles:

- Purchase Order Processing (Supplier)

- Dynamic Replenishment (Supplier)

- ASN Maintenance (Supplier)

- Invoice Maintenance (Supplier)

- Replenishment Processing (Supplier)

- Release and Kanban Processing (Supplier)

- Outsourced Manufacturing: Planning (Supplier)

- Outsourced Manufacturing: Planning (Customer)

- Outsourced Manufacturing: Order Processing (Supplier)

- Outsourced Manufacturing: Order Processing (Customer)

______________________________________________________________SAP AG 91

SAP-System______________________________________________________________

Page 100: Release Notes for SAP Supply Chain Management Release SAP

- Supplier Collaboration: Superuser and Administrator (Supplier)

- Supplier Collaboration: Superuser (Customer)

- Supplier Collaboration: Administrator (Customer)

- Forecast Collaboration (Customer)

- Forecast Collaboration (Supplier)

In addition, the Responsive Replenishment: Planner role has been enhanced to incorporate all newResponsive Replenishment Web screens.

1.6.4.5 User Administration (New)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, you can use the application useradministration on the SAP SNC Web UI to maintain users in the supplier and customer collaborationscenarios of SAP SNC. User administration facilitates the maintenance of users in the SAP SNC system,and offers a better overview of existing users and the roles they have been assigned.

You can create, change, delete, and assign roles to users on the following SAP SNC Web screens:

- User Administration (Power Administrator)The User Administration (Power Administrator) Web screen allows a power administrator tomaintain users for the business partner to whom he or she is assigned, as well as for the businesspartner with whom he or she is working.

- User Administration (External Administrator)The User Administration (External Administrator) Web screen allows an external administrator tomaintain users only for the business partner to whom he or she is assigned.

User administration sends automatically generated e-mails to communicate user-specific information,such as logon details and passwords. We deliver default e-mail texts for the e-mails. If you do not want touse the default e-mail texts, you can create e-mail texts with special reports.

Effects on System Administration

To run user administration, you must create and assign a power administrator to the business partner thatruns the SAP SNC system. The power administrator is responsible for the user administration of the

______________________________________________________________SAP AG 92

SAP-System______________________________________________________________

Page 101: Release Notes for SAP Supply Chain Management Release SAP

business partner who runs SAP SNC, as well as for creating external administrators, who maintain usersfor other business partners. You must also determine a mail administrator, for example the poweradministrator, who administrates all automatically generated outbound e-mails, as well as inbound e-mailsthat relate to error messages from unsent e-mails.

You can use the following reports to create e-mail texts for the automatically generated e-mails:

- Welcome e-mail: Create Welcome E-Mails /SCA/PUM_WELCOME

- Password re-set e-mail: Create Password Re-Set E-Mails /SCA/PUM_PSWRESET

Effects on Customizing

To run user administration, you must first make the following settings in Customizing for SAP SupplyNetwork Collaboration under Master Data -> User Administration.

In the Customizing activity Configure User Administration, you make the following settings:

- Assign roles at a global, business partner, or user level

- Determine a mail administrator

- Determine the e-mail texts of the automatically generated e-mails

In Customizing for SAP Supply Network Collaboration under Basic Settings -> URL Determination-> Determine URLs, you determine the URLs for user administration.

The following Business Add-Ins (BAdIs) are available in Customizing for SAP Supply NetworkCollaboration under Business Add-Ins (BAdIs) for SAP SNC -> Master Data -> UserAdministration:

- Enhancing the Logic After New User Creation

- Creating a User Name for a New User

- Setting the Validity for a New User

See also

User Administration in SAP Library for SAP Supply Network Collaboration under Master Data.

1.6.5 SCM-ICH-REL Scheduling Agreement Release

1.6.5.1 New-Note Alerts for SA Releases (Changed)

Use

When you create a note for a scheduling agreement release or for a scheduling agreement confirmation,SAP Supply Network Collaboration (SAP SNC) can create an alert (alert type 7059). Previously,new-note alerts were generated by the Post Processing Framework (PPF), using the/SCA/BOL_REL_NEW_NOTES PPF action (/SCA/ICH_NOTES application,/SCA/BOL_REL_NOTES action profile).

______________________________________________________________SAP AG 93

SAP-System______________________________________________________________

Page 102: Release Notes for SAP Supply Chain Management Release SAP

As of SAP SNC 7.0, the standard system creates new-note alerts directly in the background (that is,without using PPF). The SCONF_NEW_NOTE_DIRECT validation check , which is active in thestandard delivery, controls whether new-note alerts are created directly or by the PPF.

Effects on Customizing

If you want to continue using the previous method (alert generation by PPF), you must deactivate thevalidation check in Customizing for Validation.

1.6.6 SCM-ICH-PO Purchase Order and Replenishment Order

1.6.6.1 XML Messages for Delivery Collaboration (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the DespatchDeliveryNotificationXML message type has been enhanced with the following fields:

- ManufacturerParty

- ManufacturerID

This enhancement allows manufacturer part number data to be transferred as part of an advanced shippingnotification.

1.6.6.2 Control of Actions for Purchase Order and Replenishment Order(Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, validation checks can trigger the generation ofthe following alerts in the background.

______________________________________________________________SAP AG 94

SAP-System______________________________________________________________

Page 103: Release Notes for SAP Supply Chain Management Release SAP

Purchase Order Alerts

Alert Type Alert ID

Purchase Order Rejected 7036

Purchase Order Item rejected 7037

Partially Confirmed Purchase Order Item 7053

Late Confirmation of Purchase Order Item 7054

Manual Approval of Confirmation Required 7055

Manual Approval of Component Requirement required 7056

Confirmation Rejected 7057

Component Requirement Rejected 7058

New Note for Purchase Order 7059

Replenishment Order Alerts

Alert Type Alert ID

Confirmation of Replenishment Order Item Was Rejected 7126

Partially Confirmed Replenishment Order Item 7124

Too-Late Confirmation of Replenishment Order Item 7125

The system can also connect to the supplier delivery performance rating (SDPR) in the background basedon the PPF configuration.

To generate these alerts and to connect to SDPR in the background, you must deactivate the followingvalidation checks:

- For purchase orders: PO_PPF_EXEC

- For replenishment orders: RO_PPF_EXEC.

If you have specified that the system generates these alerts in the background, you can still deactivate eachalert individually or deactivate the SDPR connection by selecting the Inactive checkbox in the PPF forthe relevant PPF action.

Effects on Customizing

You activate and deactivate these validation checks in Customizing for Supply Network Collaborationby choosing Basic Settings -> Validation -> Own Settings -> Maintain Settings in Validation Profiles.

You can make PPF settings in Customizing for Supply Network Collaboration by choosing Tools ->Actions (Post Processing Framework) -> Define Action Profiles and Definitions and editing the

______________________________________________________________SAP AG 95

SAP-System______________________________________________________________

Page 104: Release Notes for SAP Supply Chain Management Release SAP

/SCA/BOL_ORDER action profile within the /SCA/ICH application.

1.6.6.3 Purchase Order XML Messages (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, new XML messages are available for sendingand receiving purchase order data. In addition, the existing XML messages include new fields that supportthe new processes in purchase order collaboration.

New XML Messages

Previously, SAP SNC could only use the following XML messages for the processes in purchase ordercollaboration:

- ReplenishmentOrderNotification for receiving a new or changed purchase order fromthe customer back-end system

- ReplenishmentOrderConfirmation for sending a purchase order confirmation to thecustomer back-end system

- ReplenishmentOrderNotification for sending a changed purchase order to the customerback-end system

As of SAP SNC 7.0, you can send and receive the following XML message types for purchase ordercollaboration instead:

- PurchaseOrderERPReplenishmentOrderCollaborationNotification forreceiving a new or changed purchase order from the customer back-end system

- PurchaseOrderERPRequest_V1 for sending a changed purchase order to the customerback-end system

The new XML messages provide integration with a customer's SAP ERP back-end system that isenhancment package 4 for SAP ERP. If you want to use the new XML messages, you must deactivate thePO_PURORDERPREQ_SEND validation check. Note, that theReplenishmentOrderConfirmation XML message is still used for receiving and sendingpurchase order confirmations.

New Fields in the existing XML Messages

As of SAP SNC 7.0, the following existing XML message types have been enhanced with the followingfields:

- ReplenishmentOrderNotification

- ManufacturerParty

- ManufacturerID

- ConfigurationPropertyValuation

______________________________________________________________SAP AG 96

SAP-System______________________________________________________________

Page 105: Release Notes for SAP Supply Chain Management Release SAP

- ProductManufacturerID

- ClassificationPropertyValuation

- ReplenishmentOrderConfirmation

- ManufacturerParty

- ManufacturerID

- ProductManufacturerID

1.6.6.4 Batches and Configuration in Purchase Order Collaboration (Enhanced)

Use

The customer batch number was already available previously in purchase orders, as follows:

- For the product at item level

- For the subcontracting components at component level

The customer creates a customer batch in his or her back-end system and sends the customer batchnumber in the purchase order to SAP Supply Network Collaboration (SAP SNC). On the Web screens forthe purchase order, the customer batch number was previously called "batch number". When the suppliercreates a purchase order confirmation in SAP SNC, he or she can specify a different customer batchnumber for a subcontracting component. (The batch number of a subcontracting component is, however,not subject to an approval by the customer. In purchase order collaboration with approval process, if thesystem copies the confirmation data of the supplier to the request schedule lines, it also copies thecustomer batch number.)

As of SAP SNC 7.0, the following enhancements exist for purchase orders:

- The customer can transfer characteristic values in the purchase order for a customer batch or for aconfigurable product.You can display the characteristic values on the Purchase Order Details Web screen on the newBatches and Characteristics tab page.

- In the purchase orders, the supplier batch number now exists as well. The customer can transmit thesupplier batch number in the purchase order to SAP SNC. (In SAP ERP, the corresponding batchnumber at PO item level is called "vendor batch number".)

- To differentiate easily between the supplier batch number and the customer batch number previouslycalled "batch number", the term "batch number" was changed to "customer batch number".

______________________________________________________________SAP AG 97

SAP-System______________________________________________________________

Page 106: Release Notes for SAP Supply Chain Management Release SAP

Note that the purchase order in SAP ERP can only save the batch number and the characteristic values forthe product configuration at item level. The characteristic values for the batch classification are not savedin the purchase order. Further restrictions for the data that an SAP ERP system can send to SAP SNC arethe result of certain IDocs (see the IDocs section). If you want to send characteristic values for batchclassification from an SAP ERP back-end system to SAP SNC, you have to use the new XML messagePurchaseOrderERPReplenishmentOrderCollaborationNotification (see below).

IDocs

In the standard SAP ERP system, the following IDocs (which are mapped in the standard to theReplenishmentOrderNotification XML message) can send characteristic values for productconfiguration at item level (but no batch and no characteristic values for the batch classification):

- ORDERS.ORDERS05 (IDoc for a new purchase order)

- ORDCHG.ORDERS05 (IDoc for a changed purchase order)

Note that these IDocs cannot transmit the format of a characteristic (such as numeric format or dateformat). They transmit a characteristic value as character string. Therefore, also theReplenishmentOrderNotification XML message to which these IDocs are mapped onlycontains the character string for a characteristic. (The ReplenishmentOrderNotification itself,however, can transmit the format.) Upon receipt of the ReplenishmentOrderNotification, SAPSNC determines the format information from the characteristic master data.

The following IDocs, which you use for purchase order collaboration with approval process, can sendbatches but no characteristic values:

- PORDCH.PORDCH02

- PORDCR1.PORDCR102

These IDocs can send the customer batch and supplier batch at item level, and the customer batch atcomponent level.

XML Message ReplenishmentOrderNotification

The XML message ReplenishmentOrderNotification (RON), which you could previously useto send purchase orders to SAP SNC, was enhanced accordingly: As of SAP SNC 7.0, the RON containsnew fields with which you can use to send characteristic values for the customer batch or productconfiguration to SAP SNC for a product at item level or for a subcontracting component. In the standardsystem, SAP SNC interprets the characteristic values for an item or subcontracting component in aReplenishmentOrderNotification as follows:

- If a batch is specified for a product, SAP SNC interprets the characteristic value as batchclassification.

- If no batch is specified, SAP SNC interprets the product as configurable product and thecharacteristic values as product configuration data.

XML Message PurchaseOrderERPReplenishmentOrderCollaborationNotification

As of enhancement package 4 for SAP ERP, an SAP ERP back-end system can create the XML messagePurchaseOrderERPReplenishmentOrderCollaborationNotification (POERPROCN)for a purchase order and send it directly to SAP SNC via XI (in other words, without IDoc or mapping).

The new XML message contains fields at item level for a batch and for characteristic values. It cantherefore send characteristic values at item level for the product configuration or for the batch

______________________________________________________________SAP AG 98

SAP-System______________________________________________________________

Page 107: Release Notes for SAP Supply Chain Management Release SAP

classification. In SAP ERP, the purchase order does not contain any characteristic values for batchclassification, therefore the new service writes characteristic values for batch classification directly intothe XML message.

In the standard system, SAP SNC interprets the characteristic values in an item of the POERPROCN asfollows:

- If a batch is specified, SAP SNC interprets the product as a product subject to a batch managementrequirement, and the characteristic values as batch classification.

- If no batch is specified, SAP SNC interprets the product as configurable product and thecharacteristic values as product configuration data.

On component level, the XML message can transmit the batch and the batch classification for asubcontracting component (but no characteristic values for the product configuration).

SAP-SNC-Internal Management of Batches and Characteristics

The XML messages send the data at item level, and SAP SNC displays the data on item level. Internally,however, SAP SNC manages the data at schedule line level.

Master Data

For SAP SNC to be able to process the characteristics of a classified batch-managed product or of aconfigurable product (for example, display the characteristics description dependent on language), thecharacteristics and classes to which the characteristics belong must exist in the SAP SNC system (classtype 300 for a configurable product, class type 232 for a batch-classified product). In addition, you mustassign the class to the product. You can create classes and characteristics manually in SAP SNC in theclassification system.

Integration of Classes and Characteristics with SAP ERP

If you are using an SAP ERP system as your back-end system, you can transfer ERP master data, inparticular, materials, classes and characteristics, to SAP SNC via Core Interface. (For configurablematerials in SAP ERP, you use classes of class type 300. For classified batch-managed materials, you useclasses of class type 023.)

Up to now, batch classes and classified batch-managed materials were integrated as follows:

- When you transfer a class of class type 023 and its characteristics to an SCM system, the class isautomatically created in the SCM system with the class type 230.

- When you transfer a batch-classified material (a class of batch class type 023 is entered in thematerial master) to an SCM system, the material is created in the SCM system as a non-classifiedproduct. In other words, the class type 230 is not entered in the product master.

As of SAP SNC 7.0, batch classes and classified batch-managed materials are integrated as follows, ifSAP SNC is installed in the system instance:

- When you cif a class of class type 023 and the assigned characteristics to the SCM system, a class ofclass type 230 is created in the SCM system with the characteristics assigned to it. (A class of classtype 230 is needed by SAP APO only). In addition, a class of class type 232 is created for use inSAP SNC. The class type 232 is assigned the class type 230 as reference class type. Using the classtype 230 as reference class type, a relationship is established between the SAP SNC class type 232and the SAP ERP class type 023.

- When you cif a batch-managed classified material to the SCM system, a classified product is createdwhich is assigned the class with the class type 232.

______________________________________________________________SAP AG 99

SAP-System______________________________________________________________

Page 108: Release Notes for SAP Supply Chain Management Release SAP

1.6.6.5 Purchase Order Screens and Replenishment Order Screens (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the layouts of the following purchase orderscreens and replenishment order screens have been enhanced:

- Purchase Order Details

- Create Replenishment Order

- Replenishment Order History

- Purchase Order History

The screens are divided into areas that correspond to the structure of a purchase order.

1.6.6.6 Due Schedule Lines (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the system can calculate an ASN-based duequantity for the confirmation schedule lines (type Confirmed) of a purchase order item. This enables thecustomer and supplier to see the quantity of the purchase order that has been confirmed by the supplierbut has not yet been covered by advanced shipping notifications. The ASN-based due quantity for theconfirmation schedule lines can be displayed in the due list for purchasing documents. The system cancopy the ASN-based due quantity from either the request schedule line, the confirmed schedule line, orfrom the due list for purchasing documents.

______________________________________________________________SAP AG 100

SAP-System______________________________________________________________

Page 109: Release Notes for SAP Supply Chain Management Release SAP

Enhancements to the Due List for Purchasing Documents

Previously, the Due List for Purchasing Documents screen showed the ASN-based due quantity for therequest schedule lines. As of SAP SNC 7.0, you can specify in Customizing whether the Due List forPurchasing Documents screen shows the ASN-based due quantity from the request schedule lines orfrom the Confirmed schedule lines. In addition, you can also decide whether request or confirmedschedule lines are the source of the displayed manufacturer part number data and batch information. Thedefault setting is that data from the request schedule lines is displayed.

Enhancements to ASN Creation

When the supplier creates an advanced shipping notification (ASN) for a purchase order item, the systemfills the data in the ASN, such as due quantity, manufacturer part number data, and batch information,considering the relevant schedule line type set in Customizing. When you specify in Customizing that therelevant schedule line type is the Confirmed schedule line type, the system fills the data in the ASN asfollows:

- Creating an ASN for a purchase order item on the PO Details screenThe system copies the ASN-based due quantity, manufacturer part number data, and batchinformation from the due confirmation schedule line to the ASN if the ASN-based due quantity isstored in the confirmation schedule line. If no ASN-based due quantity is available in theconfirmation schedule line, the data from the due request schedule line is used. If no confirmationschedule line of type Confirmed exists, then the ASN uses the data from the due request scheduleline.

- Creating an ASN for a purchase order schedule line on the PO Details screenThe system copies the ASN-based due quantity, manufacturer part number data, and batchinformation from the selected schedule line to the ASN. The system does this regardless of theCustomizing setting for relevant schedule line types.

- Creating an ASN for a purchase order item on the Due List for Purchasing Documents screenThe system copies the ASN-based due quantity, manufacturer part number data, and batchinformation that is displayed on the Due List for Purchasing Documents screen to the ASN.

Effects on Existing Data

If you have existing purchase orders that are open or partially delivered, you can update the ASN-baseddue quantity for the confirmation schedule lines by running the Calculate ASN-Based Due Quantity inConfirmed Schedule Lines of PO (/SCA/PO_ASNDUEQTY_CONF_CALC)report.

Effects on Customizing

You specify whether the due list for purchasing documents and the creation of ASNs triggered from thisscreen should use data from the confirmation schedule line or from the request schedule line, in theCustomizing activity Determine Due Schedule Line Quantities.

______________________________________________________________SAP AG 101

SAP-System______________________________________________________________

Page 110: Release Notes for SAP Supply Chain Management Release SAP

1.6.6.7 Manufacturer Part Number (New)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, a customer can request a specific manufacturerpart number (MPN) and manufacturer in a purchase order to procure a particular product. This means thatif the supplier procures a product from various manufacturers, the customer can specify the preferredmanufacturer and manufacturer part number for the product in a purchase order. A supplier can confirmmanufacturer part data in a purchase order confirmation and advanced shipping notification (ASN) as isor by using a different approved manufacturer and manufacturer part number.

To ensure that only manufacturer part data approved by the customer is used for the product, a customercan maintain an approved manufacturer parts list (AMPL) on the SAP SNC Web UI or on the SAP EasyAccess screen. This list specifies which manufacturers and manufacturer part numbers are acceptable fora given period and for a combination of customer location, supplier, ship-from location, and product.

When a supplier confirms purchase order items or schedule lines, and when he or she creates advancedshipping notifications, he or she can only use manufacturer part data that is entered in the AMPL and thatis valid for the purchase order being confirmed.

Integration with an SAP ERP Back-End System

You can transfer data from an AMPL in SAP ERP to SAP SNC using the Core Interface (CIF). AMPLintegration is available when using enhancement package 4 for SAP ERP, with the OutsourcedManufacturing business function activated.

Effects on Customizing

To use manufacturer part number confirmations, you must make settings for purchase orders and/or ASNsdepending on your requirements. You make these settings in Customizing for Supply NetworkCollaboration under Purchase Order -> Make General Settings for Purchase Orders by creating andassigning an approval profile that contains your MPN confirmation settings.

1.6.6.8 Price Confirmation (New)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, a supplier can confirm a price that differs fromthe requested price in a purchase order item. A customer can specify tolerances within which theconfirmed price can lie, and the system uses deviation analysis to check that these tolerances are not

______________________________________________________________SAP AG 102

SAP-System______________________________________________________________

Page 111: Release Notes for SAP Supply Chain Management Release SAP

breached. The system can call deviation analysis to check the confirmed price by using a validation check.For this purpose, a consensus profile, rule, and permissible class are available in the standard system. InContract Manufacturing scenarios, SAP SNC can copy the confirmed price to the requested price of apurchase order item and send a purchase order update to the back-end system.

Effects on Customizing

To use price confirmations, you must activate price confirmations in Customizing for Supply NetworkCollaboration under Purchase Order -> Make General Settings for Purchase Orders by creating andassigning an approval profile that contains an active price confirmation setting.

To use deviation analysis, you must create a price profile in Customizing for Supply NetworkCollaboration under Basic Settings -> Consensus Finding -> Consensus Profiles -> MaintainConsensus Price Profiles, and assign this to a consensus rule in Customizing for Supply NetworkCollaboration under Basic Settings -> Consensus Finding -> Maintain Consensus Rules.

1.6.6.9 Technical Basis for Web UI Screens (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0 the following screens on the Web userinterface (Web UI) have been converted to Web Dynpro technology:

- Create Replenishment Order

- Purchase Order - Details (Supplier View)

- Purchase Order - Details (Customer View)

- Purchase Order - Details (Goods Recipient)

- Purchase Order - Details History (Supplier View)

- Purchase Order - Details History (Customer View)

- Replenishment Order - Details (Supplier View)

- Replenishment Order - Details (Customer View)

- Replenishment Order - Details History (Supplier View)

- Replenishment Order - Details History (Customer View)

- Purchase Order - Details (Supplier View)

- Purchase Order - Details (Customer View)

- Replenishment Order -Details History (Supplier View)

______________________________________________________________SAP AG 103

SAP-System______________________________________________________________

Page 112: Release Notes for SAP Supply Chain Management Release SAP

- Replenishment Order - Details History (Customer View)

- Replenishment Order - Details (Supplier View)

- Replenishment Order - Details History (Supplier View)

- Due List for Purchasing Documents (Customer View)

- Due List for Purchasing Documents (Supplier View)

- Receipts and Requirements List (Customer View)

- Receipts and Requirements List (Supplier View)

- Receipts and Requirements List (Goods Recipient View)

The following screens display data based on personal object worklists (POWL):

- Due List for Purchasing Documents

- Receipts and Requirements List

Pre-configured queries are delivered with these new POWL screens. Both the due list for purchasingdocuments and the receipts and requirements list have a default query for the initial overview, in additionto a query as a default navigation target when the user navigates from the Quick View screen to the list.

1.6.6.10 Purchase Order Worklist (Enhanced)

Use

In the previous release, the supplier created confirmation schedule lines (type Confirmed) in the To BeConfirmed query. The supplier then published confirmation schedule lines in the To Be Publishedquery. The supplier was able to confirm the complete quantity and date as requested in a schedule line byselecting the CCQ (Confirm Complete Quantity) checkbox for a schedule line.

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the following features are available:

- The supplier can use the Confirmation Due List query to create and publish purchase orderconfirmations for purchase order items with a confirmation-based due quantity greater than 0 asfollows:

- If a purchase order item only contains a maximum of one request schedule line and oneconfirmation schedule line (type Confirmed), the supplier can edit purchase order confirmationdata at item level.

______________________________________________________________SAP AG 104

SAP-System______________________________________________________________

Page 113: Release Notes for SAP Supply Chain Management Release SAP

- If a purchase order item contains multiple schedule lines, the supplier can edit confirmationdata at schedule line level by calling up a pop-up window.

- The supplier can choose to confirm all confirmable data (such as price, date, MPN, andquantity) as requested for an item or schedule line by selecting the Confirm As Requestedcheckbox before saving.

- The supplier can reject items by selecting the Reject checkbox for an item before saving.

- The supplier can use the Change Confirmation List query to change and publish purchase orderconfirmations that have already been published. The options available in this query are the same asfor the Confirmation Due List query.

- The supplier saves and publishes purchase order confirmation data at item level in one step using theSave & Publish pushbutton in the Confirmation Due List query and Change Confirmation Listquery.

Effects on Customizing

If you want to continue using a two-step method for saving and publishing purchase order confirmationdata (as in SAP SNC 5.1), you must make this setting in Customizing for Supply NetworkCollaboration under Purchase Order -> Make General Settings for Purchase Orders. Furthermore, onthe SAP SNC Web UI, you must define a new query for publishing saved purchase order confirmations.For more information see the documentation for this Customizing activity and the application help forPurchase Order Worklist.

1.6.7 SCM-ICH-ASN Advanced Shipping Notification

1.6.7.1 XML Messages for Delivery Collaboration (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the DespatchDeliveryNotificationXML message type has been enhanced with the following fields:

- ManufacturerParty

- ManufacturerID

This enhancement allows manufacturer part number data to be transferred as part of an advanced shippingnotification.

______________________________________________________________SAP AG 105

SAP-System______________________________________________________________

Page 114: Release Notes for SAP Supply Chain Management Release SAP

1.6.7.2 Due Schedule Lines (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the system can calculate an ASN-based duequantity for the confirmation schedule lines (type Confirmed) of a purchase order item. This enables thecustomer and supplier to see the quantity of the purchase order that has been confirmed by the supplierbut has not yet been covered by advanced shipping notifications. The ASN-based due quantity for theconfirmation schedule lines can be displayed in the due list for purchasing documents. The system cancopy the ASN-based due quantity from either the request schedule line, the confirmed schedule line, orfrom the due list for purchasing documents.

Enhancements to the Due List for Purchasing Documents

Previously, the Due List for Purchasing Documents screen showed the ASN-based due quantity for therequest schedule lines. As of SAP SNC 7.0, you can specify in Customizing whether the Due List forPurchasing Documents screen shows the ASN-based due quantity from the request schedule lines orfrom the Confirmed schedule lines. In addition, you can also decide whether request or confirmedschedule lines are the source of the displayed manufacturer part number data and batch information. Thedefault setting is that data from the request schedule lines is displayed.

Enhancements to ASN Creation

When the supplier creates an advanced shipping notification (ASN) for a purchase order item, the systemfills the data in the ASN, such as due quantity, manufacturer part number data, and batch information,considering the relevant schedule line type set in Customizing. When you specify in Customizing that therelevant schedule line type is the Confirmed schedule line type, the system fills the data in the ASN asfollows:

- Creating an ASN for a purchase order item on the PO Details screenThe system copies the ASN-based due quantity, manufacturer part number data, and batchinformation from the due confirmation schedule line to the ASN if the ASN-based due quantity isstored in the confirmation schedule line. If no ASN-based due quantity is available in theconfirmation schedule line, the data from the due request schedule line is used. If no confirmationschedule line of type Confirmed exists, then the ASN uses the data from the due request scheduleline.

- Creating an ASN for a purchase order schedule line on the PO Details screenThe system copies the ASN-based due quantity, manufacturer part number data, and batchinformation from the selected schedule line to the ASN. The system does this regardless of theCustomizing setting for relevant schedule line types.

- Creating an ASN for a purchase order item on the Due List for Purchasing Documents screenThe system copies the ASN-based due quantity, manufacturer part number data, and batch

______________________________________________________________SAP AG 106

SAP-System______________________________________________________________

Page 115: Release Notes for SAP Supply Chain Management Release SAP

information that is displayed on the Due List for Purchasing Documents screen to the ASN.

Effects on Existing Data

If you have existing purchase orders that are open or partially delivered, you can update the ASN-baseddue quantity for the confirmation schedule lines by running the Calculate ASN-Based Due Quantity inConfirmed Schedule Lines of PO (/SCA/PO_ASNDUEQTY_CONF_CALC)report.

Effects on Customizing

You specify whether the due list for purchasing documents and the creation of ASNs triggered from thisscreen should use data from the confirmation schedule line or from the request schedule line, in theCustomizing activity Determine Due Schedule Line Quantities.

1.6.8 SCM-ICH-WO Work Order

1.6.8.1 Batches and Configuration in Work Order Collaboration (Enhanced)

Use

Previously, the following batch numbers were available in the work order:

- Customer batch numberThis batch number is relevant for the primary product of the work order. The work order copies thecustomer batch number from the purchase order item for which the work order was created. Youcannot change the customer batch number in SAP Supply Network Collaboration (SAP SNC).

- Component batch numberThis batch number is relevant for input components. Using the component batch number, thecustomer can propose in a planned phase input which component batch the supplier is to use toproduce the finished product. When the supplier reports actual data for an input component, he orshe can enter the component batch number that he or she actually used.The work order can copy the component batch from the subcontract order for which the work orderwas created (provided the subcontract order transmits the batch number for the component, whichwas not possible previously with an SAP ERP back-end system). In SAP SNC, the customer canenter the component batch number manually in the work order.

Batch usage data, batch characteristic values, or characteristic values for a configurable product were notavailable in the work order. As of SAP Supply Network Collaboration (SAP SNC) 7.0, the work orderwas enhanced as described in the following sections.

Batch Numbers

The batch numbers were enhanced as follows:

- Customer batch number and component batch number

______________________________________________________________SAP AG 107

SAP-System______________________________________________________________

Page 116: Release Notes for SAP Supply Chain Management Release SAP

The component batch number is now called "customer batch number". As of SAP SNC 7.0,"customer batch number" is the general term for a batch number that the customer uses to identify aparticular batch of a subcontracting component, a primary product, or a co-product.

- Supplier batch numberIn addition to the customer batch number, a Supplier Batch Number field is now available for afinished product (primary product or co-product). In this field, the supplier can enter the batchnumber that he or she uses for a particular finished-product batch.

Previously, the Component Batch Number field was ready for input and the customer or supplier couldenter any batch number for a component. As of SAP SNC 7.0, the field for the customer batch number fora component is only ready for input if the component is batch-managed. (A product is batch-managed ifthe customer has selected the Batch Mgmt Reqt (Batch Management Requirement) checkbox in theproduct master of SAP SNC.) The same applies to the fields for the supplier batch number for finishedproducts: Only if a finished product is batch-managed and the customer has selected the Batch MgmtReqt (Batch Management Requirement) checkbox in the product master of SAP SNC, are the fields forthe supplier batch number ready for input. Note that the customer batch number for a co-product orprimary product is never ready for input.

Mandatory Batch Numbers

As of SAP SNC 7.0, the customer can determine whether the supplier must specify batches whenreporting actual data for a batch-managed product. To do so, the customer uses the following checkboxesin work order configuration:

- Supplier Batch for Primary Product

- Supplier Batch for Co-Product

- Customer Batch for Component

When the customer selects a checkbox, the corresponding batch number field is mandatory for thesupplier when reporting actual data. Otherwise, the corresponding batch number is optional. Note that thecheckboxes do not impact work order confirmations or the customer's planned work order data. For workorder confirmations or planned work order data, batch numbers are always optional.

Customer Batches Available for Components

As of SAP SNC 7.0, the customer must determine in the work order configuration which componentbatches are available for use in the work order. The batches can come from the following sources:

- Subcontract order

- Work order

- Inventory data that the customer or the supplier sent from their back-end system to SAP SNC

The SAP ERP back-end reports for outsourced manufacturing were enhanced accordingly.

The customer and the supplier are only allowed to use these batches for the work order components. If thecustomer does not make settings in the work order configuration, the customer and the supplier can notenter customer batches for components in the work order.

Batch Numbers in XML Messages

A supplier can also provide work order confirmations or actual data by sending an XML message fromthe supplier back-end system to SAP SNC. To make sure that the supplier provides the mandatory batchnumbers and that he or she only uses allowed component batches, the customer must activate the

______________________________________________________________SAP AG 108

SAP-System______________________________________________________________

Page 117: Release Notes for SAP Supply Chain Management Release SAP

corresponding validation checks. For more information, see the Effects on Customizing section.

Characteristic Values for Batch Classification and Product Configuration

The work order can now handle the characteristic values for a configurable primary product, abatch-classified primary product, or a batch-classified component. The customer transmits thecharacteristic values in the purchase order to SAP SNC. During work order creation, the work orderadopts the characteristic values from the purchase order.

In SAP SNC, you cannot change the characteristic values of a configurable primary product or abatch-classified component. However, when reporting actual data for a batch-classified finished product(primary product), the supplier can provide characteristic values for the supplier batch. To handlecharacteristics, the relevant classes and characteristics must be available in SAP SNC. For moreinformation about master data, see the Release Note Batches and Configuration in Purchase OrderCollaboration (Enhanced).

Note that for a historic version of the work order the work order history only displays the characteristicvalues that currently exist in SAP SNC for a particular batch or for a configurable product. SAP SNClikewise does not archive the batch classification or the configuration.

Batch Usage

When reporting actual data for a component batch, the supplier can specify the finished-product batchesthat use that component batch.

XML Message Enhancements

The XML messages for work order collaboration were enhanced by the fields that are required for the newfeatures described above. For an input component, the XML messages include fields for the followingdata:

- Batch usage

- Batch characteristic values

For an output component, the XML messages include fields for the following data:

- Batch characteristic values

- Configuration characteristic values

Note: The data that the customer back-end system can actually send to SAP SNC depends on the customerback-end system, the messages used, and the mapping.

Effects on System Administration

If you have previously used batches for a product, do the following after the upgrade:

- If the product was not batch-managed before, select the Batch Mgmt Reqt (Batch ManagementRequirement) checkbox in the product master. Otherwise the batch fields are not ready for input inthe work order after the upgrade.

- In the work order configuration, determine which component batches are allowed for the work order.

Note for work orders that you created before the upgrade: When determining the batches available for awork order after the upgrade, the system does not consider the batch numbers that were entered in thework order before the upgrade.

Effects on Customizing

______________________________________________________________SAP AG 109

SAP-System______________________________________________________________

Page 118: Release Notes for SAP Supply Chain Management Release SAP

As of SAP SNC 7.0, the following validation checks are available for XML messages that the supplieruses to send work order confirmations or actual data to SAP SNC:

- Batch Number Is Valid (WO_BATCH_ID_INVALID)This validation check checks if the batch number for a batch-managed component is valid. A batchnumber is valid if it is included in the list of component batches that are available for use in the workorder.

- Batch Number Is Specified (WO_BATCH_ID_MISSING)This validation check checks if the work order confirmation provided a batch number for abatch-managed product for which the batch number is mandatory according to the work orderconfiguration.

The validation checks are active in the standard system. You can check the settings for validation inCustomizing for Supply Network Collaboration by choosing Validation.

Note that the validation checks are not relevant for batch numbers that the supplier enters on the workorder Web screens: On the Web screens, the supplier can only ever enter a valid batch for abatch-managed subcontracting component. Additionally, the supplier is always requested to enter a batchnumber if work order configuration requires a batch number.

See also

Release Note Batches and Configuration in Purchase Order Collaboration (Enhanced)

Release Note Sending Work Orders to Customer Back-End System (Enhanced)

Release Note Inventory in SMI and Outsourced Manufacturing (Enhanced)

1.6.8.2 Sending Work Orders to Customer Back-End System (Enhanced)

Use

When the customer publishes a work order in SAP Supply Network Collaboration (SAP SNC), SAP SNCcan automatically send the work order to the customer back-end system and to the supplier back-endsystem. To send the work order to a customer back-end system, SAP SNC previously used the work orderinformation, which was transmitted using a ManufacturingWorkOrderInformation XMLmessage type. An SAP ERP system could not receive that message.

As of SAP SNC 7.0, an additional message is available to update the customer back-end system: theproduction progress notification (PPN). In contrast to a work order information a production progressnotification only transmits delta quantities for the actual phase inputs or phase outputs (actual PIOs) of thework order. The delta quantity for an actual PIO is the quantity by which the actual PIO quantity haschanged since the last PPN was sent. The customer back-end system can use the data to track theproduction progress. SAP SNC transmits the message using the new XML message typeManufacturingWorkOrderProductionProgressNotification.

Integration with an SAP ERP System

As of enhancement package 4 for SAP ERP 6.0, an SAP ERP system can receive PPNs (provided that youhave activated the Outsourced Manufacturing (LOG_MM_OM_01) business function in the SAP ERP

______________________________________________________________SAP AG 110

SAP-System______________________________________________________________

Page 119: Release Notes for SAP Supply Chain Management Release SAP

system).

Sending Options

In the work order configuration of SAP SNC, you can determine whether and when the systemautomatically creates and sends a PPN to the customer back-end system. The following options areavailable to you:

- The PPN can never be created or sent, neither automatically nor manually.

- The system creates the PPN when the supplier or the customer reports that a phase has beencompleted.

- The system creates the message each time the supplier or customer creates or changes an actualphase input or phase output and saves the work order.

To improve the performance and save database space, in SAP SNC 7.0 the same configuration optionswere made available for work order information messages in the work order configuration.

Phase Completion

The ManufacturingWorkOrderInformation XML message can now transmit the informationthat a phase was completed (CompletedIndicator field). The newManufacturingWorkOrderProductionProgressNotification XML message includes aCompletedIndicator field at header level that indicates that the work order is completed.

Effects on Customizing

For the message interfaceManufacturingWorkOrderProductionProgressNotification_Out, the Business Add-In(BAdI)/SCA/BIF_O_WORKORD_P is available. You can use this BAdI to change or extend datatransferred via the message interface in outbound message processing. You can call up the BAdI inCustomizing for Supply Network Collaboration under Business Add-Ins (BAdIs) for SAP SNC ->Basic Settings -> Processing Inbound and Outbound Messages -> BAdIs for MessageInterfaces (Outbound XML Messages) -> BAdI forManufacturingWorkOrderProductionProgressNotification_Out.

1.6.8.3 Splitting of Deliveries (Enhanced)

Use

Using the Split Delivery negotiation function in the delivery overview, you could previously split adelivery into two deliveries (depending on the business partner role in two request deliveries or twoconfirmation deliveries). As of SAP Supply Network Collaboration (SAP SNC 7.0), you can split adelivery into multiple deliveries.

______________________________________________________________SAP AG 111

SAP-System______________________________________________________________

Page 120: Release Notes for SAP Supply Chain Management Release SAP

1.6.8.4 Work Order Worklist (New)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, you can use the new work order worklist ifyou want to report actual data for multiple work orders and phases simultaneously. You call up the workorder worklist in the Web application menu for SAP SNC under Work Order.

1.6.9 SCM-ICH-IV Invoice

1.6.9.1 Invoice Alerts (New)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the following alert types are available:

- Exception in Invoice Validation (7130)This alert indicates an exception in the validation of an invoice.

- Payment Past Due (7131)This alert indicates that the due date for payment of an unpaid published invoice has passed.This alert is generated by the Generate Alerts for Invoices (/SCA/INVOICE_ALERT) report.When a payment notification is received in SAP SNC, the system deletes any Payment Past Duealert that exists for the corresponding invoice.

You view invoice-relevant alerts in the new Invoice alert category of the Alert Monitor.

______________________________________________________________SAP AG 112

SAP-System______________________________________________________________

Page 121: Release Notes for SAP Supply Chain Management Release SAP

Effects on System Administration

To generate alerts for payments past due, the system administrator must regularly run the GenerateAlerts for Invoices (/SCA/INVOICE_ALERT) report.

1.6.10 SCM-ICH-IMO Inventory Monitor

1.6.10.1 Inventory in SMI and Outsourced Manufacturing (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0 and enhancement package 4 for SAP ERP 6.0,the following enhancements are available:

- You can transmit stock in transfer from SAP ERP to SAP SNC and consider it in Supply NetworkInventory (SNI) and Supplier Managed Inventory (SMI). In SAP ERP, you create stock in transfer ifyou post a stock transfer between two plants or two storage locations using a two-step postingprocedure. In addition, you can now transmit the subcontracting stock in transfer, which is relevantfor SNI only. Subcontracting stock in transfer is created when you move subcontracting componentsfrom your own stock to the subcontracting stock using a two-step posting procedure. To supportthese stock types in SAP SNC, the relevant functions and objects were enhanced as described below.

- You can transmit individual batch inventories for batch-managed inventories including batchclassification.

ProductActivityNotification (PROACT)

The following new fields were added to the ProductActivityNotification XML message type,which is used to transmit inventory data from SAP ERP to SAP SNC:

- StockInTransferQuantityThis field is used to transmit the total of stock in transfer between plants and stock in transferbetween storage locations.

- SubcontractingStockInTransferQuantityThis field is used to transmit subcontracting stock in transfer.

For batch-managed products, batch IDs were added (internal batch ID, supplier batch ID, and customerbatch ID). In addition, the message now can transmit characteristic values for a batch.

Reports for Data Transfer from SAP ERP to SAP SNC

The reports for transferring data from SAP ERP to SMI or SNI were enhanced as follows:

- Report for data transfer to SMIThe Data Transfer from ERP to SNC for SMI, RP, DR (RSMIPROACT2) report includesselection parameters for stock in transfer between plants and stock in transfer between storagelocations. (Note that the ProductActivityNotification XML message only transmits thetotal stock in transfer.)

______________________________________________________________SAP AG 113

SAP-System______________________________________________________________

Page 122: Release Notes for SAP Supply Chain Management Release SAP

- Reports for data transfer to SNIThe following reports include selection parameters for stock in transfer between plants, stock intransfer between storage locations, and for subcontracting stock in transfer.

- Data Transfer for Contract Manufacturing (Own Data) (ROEMPROACT2)

- Data Transfer for Contract Manufacturing (Partner Plant) (RPRTPROACT)

Note that you can select stock in transfer between plants or between storage locations individually.However, the ProductActivityNotification XML message transmits the total of thesestock types. )

The report Data Transfer for Contract Manufacturing (Partner Data) (RCMPROACT2) reportcontains a selection parameter for subcontracting stock in transfer.If you want to use these report enhancements, you must activate the SAP ERP business functionOutsourced Manufacturing (LOG_MM_OM_1).

Transfer of Individual Batches

The following reports for data transfer to SNI now include an Individual Batches checkbox:

- Data Transfer for Contract Manufacturing (Own Data) (ROEMPROACT2)

- Data Transfer for Contract Manufacturing (Partner Data) (RCMPROACT2)

If you select the checkbox, the reports transmit the individual batches including batch number and batchclassification values for a batch-managed material. Previously, you could only transmit the aggregatedbatch quantity for a selected batch-managed material (without batch numbers or classification values).

If you want to use these report enhancements, you must activate the SAP ERP business functionOutsourced Manufacturing (LOG_MM_OM_1).

Note: If you have transmitted inventory previously and you now want to use the new option and transmitindividual batches, you must first reset the inventory in SAP SNC, using the Reset Inventory to Zeroreport (/SCA/DM_RESETINV) report. This is to prevent stock values for a batch-managed materialfrom existing twice in SAP SNC (aggregated value and values for the individual batches).

Changes on the Web Screens of the SMI Monitor and SNI Monitor

In the SMI Monitor, the following stock types are displayed:

- Stock in transfer

- Consignment stock in transfer

In the SNI Monitor, the following stock types are displayed:

- Stock in transfer

- Consignment stock in transfer

- Subcontracting stock in transfer

- Consignment subcontracting stock in transfer

Stock in transfer and subcontracting stock in transfer are included on the new Inventory Overviewscreen for SNI, for example.

______________________________________________________________SAP AG 114

SAP-System______________________________________________________________

Page 123: Release Notes for SAP Supply Chain Management Release SAP

Stock on Hand and Projected Stock

As of SAP SNC 7.0, the following enhancements are available:

- Calculating the stock on handThe stock on hand is part of the default formula for calculating the projected stock. The default stockon hand in the projected stock formula for SMI, Responsive Replenishment, and Delivery ControlMonitor now also includes the stock in transfer and the consignment stock in transfer. The defaultcoding for the Business Add-In (BAdI) Calculation of Stock on Hand(/SCA/ICH_STOCKONHAND) was enhanced accordingly.

- Defining own profiles for projected stockYou can add the new stock types to your projected stock profiles in Customizing for ProjectedStock if needed.

- Standard profiles for the projected stockThe following SAP standard profiles for calculating the projected stock (listed in the Customizingactivity Display Standard Profiles for Projected Stock) now also include the stock in transferand the subcontracting stock in transfer:

- ASN

- RODP

- RODP_ASN

- ROP

- ROP_ASN

1.6.10.2 Data in the Min/Max Replenishment Monitor (Enhanced)

Use

Previously, the Details screens of the Min/Max Replenishment Monitor displayed the Firm Receipts(Published - Due) key figure. This key figure indicates the total due quantity (quantity not covered byASNs) from published replenishment orders. As of SAP Supply Network Collaboration (SAP SNC) 7.0,the Details screen shows an additional key figure: The Firm Receipts (Unpublished - Due) key figureis related to unpublished replenishment orders that have a due quantity.

______________________________________________________________SAP AG 115

SAP-System______________________________________________________________

Page 124: Release Notes for SAP Supply Chain Management Release SAP

1.6.10.3 Data in the RR Monitor (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the Responsive Replenishment Monitor (RRMonitor) displays new data.

New Key Figures on the RR Details Screen

Previously, the Firm Receipts (Due) key figure was available on the Details screen. The Firm Receipts(Due) key figure indicates the due quantity (quantity not covered by ASNs) of unpublished and publishedreplenishment orders. In SAP SNC 7.0, this key figure was replaced by the following new key figures thatare related to unpublished and published replenishment orders:

- Firm Receipts (Unpublished - Due)

- Firm Receipts (Published - Due)

In addition, the following new key figures are available to you:

- Projected Stock (Firm)This key figure represents a projected stock that only considers firm receipts, that is, publishedreplenishment orders. The firm projected stock does not take into account unpublishedreplenishment orders or planned replenishment orders (planned receipts).

- Days' Supply (Firm)This key figure indicates how many days the firm projected stock (Projected Stock (Firm) keyfigure) suffices to cover the demand of the subsequent periods (Demand key figure).

New Data on the RR Overview Screen

As of SAP SNC 7.0, new columns are available on the RR Overview screen. They are related to the firmdays' supply and to TLB-related quantities, as follows:

- Firm days' supplyTwo new columns are available that indicate the firm days' supply at the end of the aggregationhorizon and at the end of the lead time.

- Aggregated replenishment demand and shipment sizing quantityReplenishment demand and shipment sizing quantity are TLB-related quantities. During the TLBrun, the system determines the replenishment demand and the shipment sizing quantity at the levelof a single TLB shipment and saves it in the TLB shipment.The replenishment demand of a TLB shipment is the quantity that served as the initial input for theTLB shipment (before the TLB performsed upsizing or downsizing). The shipment sizing quantity isthe quantity by which the TLB increased (+) or decreased (-) the replenishment demand for the TLBshipment during shipment sizing.The RR Overview screen displays the total replenishment demand and the total shipment sizingquantity for particular horizons. Nine columns are available for both the replenishment demand andthe shipment sizing quantity, as well as for other quantities on the RR Overview screen that were

______________________________________________________________SAP AG 116

SAP-System______________________________________________________________

Page 125: Release Notes for SAP Supply Chain Management Release SAP

available previously. Each column represents the aggregation with respect to a particular horizon(display horizon, lead time, and aggregation horizon) and replenishment order date (order processingdate, shipping date, and availability date in the customer location).

In the standard system , the RR Overview screen does not display these fields. If you want to displaythese fields, you must use a Business Add-In (BAdI). For more information, see the Release NoteConfiguring the Replenishment Overview (Enhanced).

1.6.10.4 Functions in the RR Overview (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, new navigation functions and configurationoptions are available for the Overview screen of the Responsive Replenishment Monitor.

Call Up the Receipts and Requirements List

Using the Receipts/Requirements List pushbutton, you can call up the receipts and requirements list forselected location products. This list shows replenishment orders.

Display the Planned Replenishment Orders for the PR AD AH Column

The PR AD AH column (Planned Receipts Based on Availability Date (Aggregation Horizon)),which was already available previously, displays the total quantity of all planned replenishment orderswhose availability date lies in the aggregation horizon. The quantity is displayed as a link. Previously, byusing the link you left the RR Overview screen and called up the Replenishment Objects screen. As ofSAP SNC 7.0, the link opens a dialog box but keeps the RR Overview screen in the background. Thedialog box displays the planned replenishment orders that contribute to the quantity value. In the dialogbox, you can create, change, or delete planned receipts for the product under consideration or for anotherproduct. When you save the changed data in the dialog box and close it, you return to the RR Overviewscreen that displays the updated data. You can return to the previous display mode for the replenishmentobjects (leaving the RR Overview screen and opening a new screen) by using a BAdI. For moreinformation, see the Customizing section.

Call Up the TLB Screen

In the RR Overview screen, nine columns for the unpublished replenishment quantity were alreadyavailable previously, which display the total quantity of all unpublished replenishment orders whose keydate is within a particular horizon. (For example, the UnpubRQ AD AH column (UnpublishedReplenishment Quantity Based on Availability Date (Aggregation Horizon)) displays the totalquantity of all unpublished replenishment orders whose availability date is within the aggregationhorizon.) As of SAP SNC 7.0, a link is available for the quantity value in each of these columns.

In the standard system, the link opens a dialog box while keeping the RR Overview screen in the

______________________________________________________________SAP AG 117

SAP-System______________________________________________________________

Page 126: Release Notes for SAP Supply Chain Management Release SAP

background. The dialog box displays unpublished replenishment orders and TLB shipments thatcontribute to the quantity. The dialog box offers the same functions as the regular TLB Shipments screen(for example, for creating or changing planned receipts or TLB shipments). When you save the changeddata and close the window, you return to the RR Overview screen that displays the updated data. Using aBusiness Add-In (BAdI), you can determine that the link leads to the regular TLB Shipments full screeninstead. For more information, see the Customizing section.

Effects on Customizing

If you want the quantity links on the RR Overview screen to lead to the regular Replenishment Objectsor TLB Shipments screen, you must use the BAdI Modification of Replenishment Monitor Overview(/SCF/REPL_OVW). You find the BAdI in Customizing for Supply Network Collaboration underBusiness Add-Ins (BAdIs) for Supply Network Collaboration -> Replenishment ->Replenishment Monitor.

See also

Release note Configuring the Replenishment Monitor Overview (Enhanced)

1.6.10.5 Configuring the Replenishment Monitor Overview (Enhanced)

Use

Previously, you could already use the Business Add-In (BAdI) Modification of ReplenishmentOverview (/SCF/REPL_OVW) to change certain properties of the Overview screen for a replenishmentmonitor. You can, for example, display columns in the replenishment monitor that are hidden in thestandard delivery. In SAP Supply Network Collaboration (SAP SNC) 7.0, the default implementation wasenhanced. Based on the default implementation, you can create your own implementations to do thefollowing:

- Hide servicesYou can, for example, hide the following:

- Buttons that you use to navigate to a related screen, such as the ASN screen

- Planning services in the value help for the Services field, such as the Run TLB service

- Set the display mode for the target window of the quantity links on the RR Overview screen (dialogbox or screen)

You can change the properties depending on the view type (customer view or supplier view) and on thetype of replenishment monitor (SMI Monitor, Min/Max Replenishment Monitor, or ResponsiveReplenishment Monitor).

For more information about hidden columns and display modes, see the following Release Notes:

- Data in the RR Overview (Enhanced)

______________________________________________________________SAP AG 118

SAP-System______________________________________________________________

Page 127: Release Notes for SAP Supply Chain Management Release SAP

- Functions in the RR Overview (Enhanced)

Effects on Customizing

As of SAP SNC 7.0, you can call up the BAdI in Customizing for Supply Network Collaboration underBusiness Add-Ins (BAdIs) for Supply Network Collaboration -> Replenishment ->Replenishment Monitor.

1.6.10.6 Saving Planning Service Results in the Replenishment Monitors(Changed)

Use

Various planning services are available on the overview screen and on the detail screens of thereplenishment monitors. In SAP Supply Network Collaboration (SAP SNC) 5.1, the system automaticallysaves the results of a planning service run. As of SAP SNC 7.0, the results are saved as follows in thereplenishment monitors:

- Detail screenIn the supplier view of the detail screens, the supplier must choose the Save pushbutton to save theresults of a planning service run. In the customer view, the customer cannot save the results of aplanning service run. (Note: In the replenishment monitors, the customer is only allowed to performsimulative planning. Therefore, the Save pushbutton is not available in the customer view.)

- Overview screenIn the supplier view of the overview screen, the system automatically saves the results of a planningservice run. In the customer view, the system does not save the results of a planning service run.(Note that the Save pushbutton is not available in either view on the overview screen.)

1.6.10.7 Refresh Concept (Enhanced)

Use

______________________________________________________________SAP AG 119

SAP-System______________________________________________________________

Page 128: Release Notes for SAP Supply Chain Management Release SAP

As of SAP Supply Network Collaboration (SAP SNC) 7.0, SAP SNC automatically refreshes thetransactional data in the overview screens of the replenishment monitors when you save data on theircorresponding details screens and navigate to the overview screen via the SAP SNC menu or by using thebackwards navigation pushbutton.

1.6.10.8 Data Matrix (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, data matrix configuration has been changed asfollows:

- Disabling of key figures, services, and dependenciesIn SAP SNC 5.1, you could select key figures, services, or dependencies and decide not to take theminto account for data matrix configuration by selecting the Delete from Standard checkbox inCustomizing. As of SAP SNC 7.0, the Delete from Standard checkbox has been renamed toDisabled. In addition, as of SAP SNC 7.0, key figures for the SNI Monitor that are not needed aredisabled by default. You can adopt the standard Customizing with disabled key figures. You can alsoenable key figures again by deselecting the Disabled checkbox for those key figures. For moreinformation about disabled key figures in the standard system, see the Effects on Customizingsection.

- Deselecting time aggregation for key figuresKey figures on the user interface (UI) of SAP SNC can appear with different time periods than intime series data management (TSDM). For example, the data matrix might return key figure valuesin weekly or monthly time periods, whereas in time series data management, the key figures mightbe stored in daily periods. Therefore, the system maps TSDM periods to UI periods. This kind ofmapping is called time aggregation. As of SAP SNC 7.0, you can de-select time aggregation for keyfigures if you do not need it.

These changes to the data matrix help you to improve system performance for data-matrix-basedapplications in SAP SNC, such as the SMI Monitor or the SNI Monitor.

Effects on Existing Data

For the SNI Monitor, standard Customizing of the data matrix has been changed: Per default, key figuresthat are based on Order Document Management (ODM) are disabled as dependencies of key figures FirmDemand (ALLFIRMDEMAND), In-Transit Quantity (INTRANSIT) and Firm Receipts (ORDER) at theAll Keys (LOCPRODSRC) aggregate level. Affected ODM-based key figures include the following:

- ALLORDER

- FIRMDEMANDWO

______________________________________________________________SAP AG 120

SAP-System______________________________________________________________

Page 129: Release Notes for SAP Supply Chain Management Release SAP

- INTRANSITOR

- VGORDER2

- WOORDER

These ODM-based key figures are now excluded from the dependency chain of key figures. On the Webscreens, this has the following consequences: In SAP SNC 5.1, the ODM-based key figures did not counttowards the displayed key figures of editable grid arrangements. As of SAP SNC 7.0, ODM-based keyfigures do not count towards the displayed key figure values on all SNI Monitor screens, includingnon-editable grid arrangements.

Effects on Customizing

To change the standard data matrix configuration, use the Customizing activity Configure Data Matrix.

1.6.10.9 Visibility of Location Products (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the visibility concept of location products onWeb screens for SAP SNC has been enhanced. This includes the following new features:

- New and enhanced selection modes for the SNI Monitor

- New selection mode for the Partner-Dependent Network Filter

- User- and partner-dependent assignment of selection modes to applications

- Deletion report for buffered user data for visibility profiles

New and Enhanced Selection Modes for the SNI Monitor

The TSDM_INV_C selection mode has been enhanced with the following new features:

- Retrieval of specified key figures onlyThe system only retrieves and evaluates data for the key figures that you have specified in theCustomizing activity Create Selection Modes. Default key figures are specified.

- Retrieval of data for specified time periods onlyThe system only retrieves data if the key figure quantities have changed within a time period that youcan specify. If no time period is specified, the system uses default values. For more information, seethe Customizing documentation for Create Selection Modes.

As of SAP SNC 7.0, you can also use the following new selection modes for SNI:

- TSDM_CThis selection mode works like TSDM_INV_C, but it only reads data from TSDM.

- INV_CThis selection mode works like TSDM_INV_C, but it only reads inventory data.

______________________________________________________________SAP AG 121

SAP-System______________________________________________________________

Page 130: Release Notes for SAP Supply Chain Management Release SAP

New Selection Mode for the Partner-Dependent Network Filter

The new PDNF_NEW selection mode works like the existing PDNF selection mode, but with improvedperformance. The selection mode controls data visibility on the basis of the user's business partner, thelocation of this business partner, and the transportation lanes to locations of a different business partner.

User- and Partner-Dependent Assignment of Selection Modes to Application IDs

In previous releases, you could assign selection modes to application IDs. These assignments were validirrespective of business partners or users. As of SAP SNC 7.0, you can assign selection modes toapplication IDs for each business partner or user.

Effects on Existing Data

The standard selection mode PDNF has been changed to PDNF_NEW for the following applications:

- Collaborative Sales Forecasting

- Order Forecast Monitor

- TPOP Forecast

- SMI Monitor

- Delivery Control Monitor

- Min/Max Replenishment Monitor

- Responsive Replenishment Monitor

- Replenishment Order

- Transport Load Builder

- Template Monitor

- History Comparison

- Audit Trail

- Master Data, such as:

- Location

- Product

- Partner-Dependent Data

- Packaging

- Number Ranges

Note that the following applications still use PDNF:

- Statistical Forecasting

- Short-Term Forecasting

- Promotions

______________________________________________________________SAP AG 122

SAP-System______________________________________________________________

Page 131: Release Notes for SAP Supply Chain Management Release SAP

Effects on System Administration

The system saves the relevant location products for a visibility profile in a buffer table for each user. As ofSAP SNC 7.0, you can use the Delete Buffered User Data (Visibility Profile)(/SCF/TSDM_INV_C_SHMA_RESET) report to delete such data from the buffer table. This is necessary,for example, in the following cases:

- New location products have been created.

- Existing location products have been changed or deleted.

- A user has been reassigned to another business partner.

The report is run automatically in the background when you change a visibility profile. Note that thereport is only relevant if you use the SNI Monitor with the TSDM_INV_C or the INV_C selection modes.

Effects on Customizing

The Customizing view /SCF/SELOBJ has been replaced by the new /SCF/SELOBJ_CFG view cluster.

Use the Customizing activity Create Selection Modes if you want to do the following:

- Replace standard selection modes with one of the new selection modes

- Display and change the default time periods for retrieving data for TSDM_C and TSDM_INV_C

- Display and change the default key figure assignment to TSDM_C and TSDM_INV_C

Use the Customizing activity Assign Partner-Dependent Selection Modes to Applications if you want toassign selection modes to application IDs depending on individual business partners or users.

1.6.11 SCM-ICH-KNB Kanban

1.6.11.1 New Selection Parameter for the Kanban Web Screen (Enhanced)

Use

As of Supply Network Collaboration (SAP SNC) 7.0, you can use the Supplier field in the selection areaof the Kanban (Customer View) Web screen to filter by supplier when you search for kanbans.

______________________________________________________________SAP AG 123

SAP-System______________________________________________________________

Page 132: Release Notes for SAP Supply Chain Management Release SAP

1.6.12 SCM-ICH-SNI Supply Network Inventory

1.6.12.1 Inventory in SMI and Outsourced Manufacturing (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0 and enhancement package 4 for SAP ERP 6.0,the following enhancements are available:

- You can transmit stock in transfer from SAP ERP to SAP SNC and consider it in Supply NetworkInventory (SNI) and Supplier Managed Inventory (SMI). In SAP ERP, you create stock in transfer ifyou post a stock transfer between two plants or two storage locations using a two-step postingprocedure. In addition, you can now transmit the subcontracting stock in transfer, which is relevantfor SNI only. Subcontracting stock in transfer is created when you move subcontracting componentsfrom your own stock to the subcontracting stock using a two-step posting procedure. To supportthese stock types in SAP SNC, the relevant functions and objects were enhanced as described below.

- You can transmit individual batch inventories for batch-managed inventories including batchclassification.

ProductActivityNotification (PROACT)

The following new fields were added to the ProductActivityNotification XML message type,which is used to transmit inventory data from SAP ERP to SAP SNC:

- StockInTransferQuantityThis field is used to transmit the total of stock in transfer between plants and stock in transferbetween storage locations.

- SubcontractingStockInTransferQuantityThis field is used to transmit subcontracting stock in transfer.

For batch-managed products, batch IDs were added (internal batch ID, supplier batch ID, and customerbatch ID). In addition, the message now can transmit characteristic values for a batch.

Reports for Data Transfer from SAP ERP to SAP SNC

The reports for transferring data from SAP ERP to SMI or SNI were enhanced as follows:

- Report for data transfer to SMIThe Data Transfer from ERP to SNC for SMI, RP, DR (RSMIPROACT2) report includesselection parameters for stock in transfer between plants and stock in transfer between storagelocations. (Note that the ProductActivityNotification XML message only transmits thetotal stock in transfer.)

- Reports for data transfer to SNIThe following reports include selection parameters for stock in transfer between plants, stock intransfer between storage locations, and for subcontracting stock in transfer.

- Data Transfer for Contract Manufacturing (Own Data) (ROEMPROACT2)

- Data Transfer for Contract Manufacturing (Partner Plant) (RPRTPROACT)

Note that you can select stock in transfer between plants or between storage locations individually.

______________________________________________________________SAP AG 124

SAP-System______________________________________________________________

Page 133: Release Notes for SAP Supply Chain Management Release SAP

However, the ProductActivityNotification XML message transmits the total of thesestock types. )

The report Data Transfer for Contract Manufacturing (Partner Data) (RCMPROACT2) reportcontains a selection parameter for subcontracting stock in transfer.If you want to use these report enhancements, you must activate the SAP ERP business functionOutsourced Manufacturing (LOG_MM_OM_1).

Transfer of Individual Batches

The following reports for data transfer to SNI now include an Individual Batches checkbox:

- Data Transfer for Contract Manufacturing (Own Data) (ROEMPROACT2)

- Data Transfer for Contract Manufacturing (Partner Data) (RCMPROACT2)

If you select the checkbox, the reports transmit the individual batches including batch number and batchclassification values for a batch-managed material. Previously, you could only transmit the aggregatedbatch quantity for a selected batch-managed material (without batch numbers or classification values).

If you want to use these report enhancements, you must activate the SAP ERP business functionOutsourced Manufacturing (LOG_MM_OM_1).

Note: If you have transmitted inventory previously and you now want to use the new option and transmitindividual batches, you must first reset the inventory in SAP SNC, using the Reset Inventory to Zeroreport (/SCA/DM_RESETINV) report. This is to prevent stock values for a batch-managed materialfrom existing twice in SAP SNC (aggregated value and values for the individual batches).

Changes on the Web Screens of the SMI Monitor and SNI Monitor

In the SMI Monitor, the following stock types are displayed:

- Stock in transfer

- Consignment stock in transfer

In the SNI Monitor, the following stock types are displayed:

- Stock in transfer

- Consignment stock in transfer

- Subcontracting stock in transfer

- Consignment subcontracting stock in transfer

Stock in transfer and subcontracting stock in transfer are included on the new Inventory Overviewscreen for SNI, for example.

Stock on Hand and Projected Stock

As of SAP SNC 7.0, the following enhancements are available:

- Calculating the stock on handThe stock on hand is part of the default formula for calculating the projected stock. The default stockon hand in the projected stock formula for SMI, Responsive Replenishment, and Delivery ControlMonitor now also includes the stock in transfer and the consignment stock in transfer. The defaultcoding for the Business Add-In (BAdI) Calculation of Stock on Hand

______________________________________________________________SAP AG 125

SAP-System______________________________________________________________

Page 134: Release Notes for SAP Supply Chain Management Release SAP

(/SCA/ICH_STOCKONHAND) was enhanced accordingly.

- Defining own profiles for projected stockYou can add the new stock types to your projected stock profiles in Customizing for ProjectedStock if needed.

- Standard profiles for the projected stockThe following SAP standard profiles for calculating the projected stock (listed in the Customizingactivity Display Standard Profiles for Projected Stock) now also include the stock in transferand the subcontracting stock in transfer:

- ASN

- RODP

- RODP_ASN

- ROP

- ROP_ASN

1.6.12.2 Inventory Overview (New)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, an inventory overview is available for SupplyNetwork Inventory (SNI). On the Inventory Overview Web screen, you can see detailed inventory datafor different stock types. This includes the following data:

- Batch inventory on batch level

- Stock in transfer

- Subcontracting stock in transfer

For configurable products and batch-managed, classified products you can drill down to the associatedcharacteristics.

The inventory overview displays inventory data that the customer and the supplier have transmitted fromtheir back-end systems to SAP SNC using ProductActivityNotification XML messages. Aspecial view is available that shows inventory data at the level of the individual business partners whoprovided the data (data-providing partners). This way, the inventory overview provides a snapshot of theinventory situation in the back-end systems of different business partners and enables you to compare thedata down to the batch level.

______________________________________________________________SAP AG 126

SAP-System______________________________________________________________

Page 135: Release Notes for SAP Supply Chain Management Release SAP

1.6.12.3 Data Matrix (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, data matrix configuration has been changed asfollows:

- Disabling of key figures, services, and dependenciesIn SAP SNC 5.1, you could select key figures, services, or dependencies and decide not to take theminto account for data matrix configuration by selecting the Delete from Standard checkbox inCustomizing. As of SAP SNC 7.0, the Delete from Standard checkbox has been renamed toDisabled. In addition, as of SAP SNC 7.0, key figures for the SNI Monitor that are not needed aredisabled by default. You can adopt the standard Customizing with disabled key figures. You can alsoenable key figures again by deselecting the Disabled checkbox for those key figures. For moreinformation about disabled key figures in the standard system, see the Effects on Customizingsection.

- Deselecting time aggregation for key figuresKey figures on the user interface (UI) of SAP SNC can appear with different time periods than intime series data management (TSDM). For example, the data matrix might return key figure valuesin weekly or monthly time periods, whereas in time series data management, the key figures mightbe stored in daily periods. Therefore, the system maps TSDM periods to UI periods. This kind ofmapping is called time aggregation. As of SAP SNC 7.0, you can de-select time aggregation for keyfigures if you do not need it.

These changes to the data matrix help you to improve system performance for data-matrix-basedapplications in SAP SNC, such as the SMI Monitor or the SNI Monitor.

Effects on Existing Data

For the SNI Monitor, standard Customizing of the data matrix has been changed: Per default, key figuresthat are based on Order Document Management (ODM) are disabled as dependencies of key figures FirmDemand (ALLFIRMDEMAND), In-Transit Quantity (INTRANSIT) and Firm Receipts (ORDER) at theAll Keys (LOCPRODSRC) aggregate level. Affected ODM-based key figures include the following:

- ALLORDER

- FIRMDEMANDWO

- INTRANSITOR

- VGORDER2

- WOORDER

These ODM-based key figures are now excluded from the dependency chain of key figures. On the Web

______________________________________________________________SAP AG 127

SAP-System______________________________________________________________

Page 136: Release Notes for SAP Supply Chain Management Release SAP

screens, this has the following consequences: In SAP SNC 5.1, the ODM-based key figures did not counttowards the displayed key figures of editable grid arrangements. As of SAP SNC 7.0, ODM-based keyfigures do not count towards the displayed key figure values on all SNI Monitor screens, includingnon-editable grid arrangements.

Effects on Customizing

To change the standard data matrix configuration, use the Customizing activity Configure Data Matrix.

1.6.12.4 Visibility of Location Products (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the visibility concept of location products onWeb screens for SAP SNC has been enhanced. This includes the following new features:

- New and enhanced selection modes for the SNI Monitor

- New selection mode for the Partner-Dependent Network Filter

- User- and partner-dependent assignment of selection modes to applications

- Deletion report for buffered user data for visibility profiles

New and Enhanced Selection Modes for the SNI Monitor

The TSDM_INV_C selection mode has been enhanced with the following new features:

- Retrieval of specified key figures onlyThe system only retrieves and evaluates data for the key figures that you have specified in theCustomizing activity Create Selection Modes. Default key figures are specified.

- Retrieval of data for specified time periods onlyThe system only retrieves data if the key figure quantities have changed within a time period that youcan specify. If no time period is specified, the system uses default values. For more information, seethe Customizing documentation for Create Selection Modes.

As of SAP SNC 7.0, you can also use the following new selection modes for SNI:

- TSDM_CThis selection mode works like TSDM_INV_C, but it only reads data from TSDM.

- INV_CThis selection mode works like TSDM_INV_C, but it only reads inventory data.

New Selection Mode for the Partner-Dependent Network Filter

The new PDNF_NEW selection mode works like the existing PDNF selection mode, but with improvedperformance. The selection mode controls data visibility on the basis of the user's business partner, thelocation of this business partner, and the transportation lanes to locations of a different business partner.

______________________________________________________________SAP AG 128

SAP-System______________________________________________________________

Page 137: Release Notes for SAP Supply Chain Management Release SAP

User- and Partner-Dependent Assignment of Selection Modes to Application IDs

In previous releases, you could assign selection modes to application IDs. These assignments were validirrespective of business partners or users. As of SAP SNC 7.0, you can assign selection modes toapplication IDs for each business partner or user.

Effects on Existing Data

The standard selection mode PDNF has been changed to PDNF_NEW for the following applications:

- Collaborative Sales Forecasting

- Order Forecast Monitor

- TPOP Forecast

- SMI Monitor

- Delivery Control Monitor

- Min/Max Replenishment Monitor

- Responsive Replenishment Monitor

- Replenishment Order

- Transport Load Builder

- Template Monitor

- History Comparison

- Audit Trail

- Master Data, such as:

- Location

- Product

- Partner-Dependent Data

- Packaging

- Number Ranges

Note that the following applications still use PDNF:

- Statistical Forecasting

- Short-Term Forecasting

- Promotions

Effects on System Administration

The system saves the relevant location products for a visibility profile in a buffer table for each user. As ofSAP SNC 7.0, you can use the Delete Buffered User Data (Visibility Profile)(/SCF/TSDM_INV_C_SHMA_RESET) report to delete such data from the buffer table. This is necessary,

______________________________________________________________SAP AG 129

SAP-System______________________________________________________________

Page 138: Release Notes for SAP Supply Chain Management Release SAP

for example, in the following cases:

- New location products have been created.

- Existing location products have been changed or deleted.

- A user has been reassigned to another business partner.

The report is run automatically in the background when you change a visibility profile. Note that thereport is only relevant if you use the SNI Monitor with the TSDM_INV_C or the INV_C selection modes.

Effects on Customizing

The Customizing view /SCF/SELOBJ has been replaced by the new /SCF/SELOBJ_CFG view cluster.

Use the Customizing activity Create Selection Modes if you want to do the following:

- Replace standard selection modes with one of the new selection modes

- Display and change the default time periods for retrieving data for TSDM_C and TSDM_INV_C

- Display and change the default key figure assignment to TSDM_C and TSDM_INV_C

Use the Customizing activity Assign Partner-Dependent Selection Modes to Applications if you want toassign selection modes to application IDs depending on individual business partners or users.

1.6.13 SCM-ICH-FCS Forecast

1.6.13.1 Visibility of Location Products (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the visibility concept of location products onWeb screens for SAP SNC has been enhanced. This includes the following new features:

- New and enhanced selection modes for the SNI Monitor

- New selection mode for the Partner-Dependent Network Filter

- User- and partner-dependent assignment of selection modes to applications

- Deletion report for buffered user data for visibility profiles

New and Enhanced Selection Modes for the SNI Monitor

The TSDM_INV_C selection mode has been enhanced with the following new features:

- Retrieval of specified key figures onlyThe system only retrieves and evaluates data for the key figures that you have specified in theCustomizing activity Create Selection Modes. Default key figures are specified.

- Retrieval of data for specified time periods onlyThe system only retrieves data if the key figure quantities have changed within a time period that youcan specify. If no time period is specified, the system uses default values. For more information, seethe Customizing documentation for Create Selection Modes.

______________________________________________________________SAP AG 130

SAP-System______________________________________________________________

Page 139: Release Notes for SAP Supply Chain Management Release SAP

As of SAP SNC 7.0, you can also use the following new selection modes for SNI:

- TSDM_CThis selection mode works like TSDM_INV_C, but it only reads data from TSDM.

- INV_CThis selection mode works like TSDM_INV_C, but it only reads inventory data.

New Selection Mode for the Partner-Dependent Network Filter

The new PDNF_NEW selection mode works like the existing PDNF selection mode, but with improvedperformance. The selection mode controls data visibility on the basis of the user's business partner, thelocation of this business partner, and the transportation lanes to locations of a different business partner.

User- and Partner-Dependent Assignment of Selection Modes to Application IDs

In previous releases, you could assign selection modes to application IDs. These assignments were validirrespective of business partners or users. As of SAP SNC 7.0, you can assign selection modes toapplication IDs for each business partner or user.

Effects on Existing Data

The standard selection mode PDNF has been changed to PDNF_NEW for the following applications:

- Collaborative Sales Forecasting

- Order Forecast Monitor

- TPOP Forecast

- SMI Monitor

- Delivery Control Monitor

- Min/Max Replenishment Monitor

- Responsive Replenishment Monitor

- Replenishment Order

- Transport Load Builder

- Template Monitor

- History Comparison

- Audit Trail

- Master Data, such as:

- Location

- Product

- Partner-Dependent Data

- Packaging

- Number Ranges

Note that the following applications still use PDNF:

- Statistical Forecasting

______________________________________________________________SAP AG 131

SAP-System______________________________________________________________

Page 140: Release Notes for SAP Supply Chain Management Release SAP

- Short-Term Forecasting

- Promotions

Effects on System Administration

The system saves the relevant location products for a visibility profile in a buffer table for each user. As ofSAP SNC 7.0, you can use the Delete Buffered User Data (Visibility Profile)(/SCF/TSDM_INV_C_SHMA_RESET) report to delete such data from the buffer table. This is necessary,for example, in the following cases:

- New location products have been created.

- Existing location products have been changed or deleted.

- A user has been reassigned to another business partner.

The report is run automatically in the background when you change a visibility profile. Note that thereport is only relevant if you use the SNI Monitor with the TSDM_INV_C or the INV_C selection modes.

Effects on Customizing

The Customizing view /SCF/SELOBJ has been replaced by the new /SCF/SELOBJ_CFG view cluster.

Use the Customizing activity Create Selection Modes if you want to do the following:

- Replace standard selection modes with one of the new selection modes

- Display and change the default time periods for retrieving data for TSDM_C and TSDM_INV_C

- Display and change the default key figure assignment to TSDM_C and TSDM_INV_C

Use the Customizing activity Assign Partner-Dependent Selection Modes to Applications if you want toassign selection modes to application IDs depending on individual business partners or users.

1.6.14 SCM-ICH-NDC Net Requirements Calculation

1.6.14.1 Product Allocation (Enhanced)

Use

In SAP Supply Network Collaboration (SAP SNC), you can use the product allocation check from GlobalAvailable-to-Promise (Global ATP) in SAP Advanced Planning and Optimization (SAP APO). Using theproduct allocation check, you can make sure that the replenishment quantities for a product that areprovided by a particular ship-from location do not exceed product allocations and are restrictedcorrespondingly.

As of SAP SNC 7.0, you can extend the field catalog for VMI product allocation with customer-specificfields. The additional fields are available for the product allocation group. (This means that you can

______________________________________________________________SAP AG 132

SAP-System______________________________________________________________

Page 141: Release Notes for SAP Supply Chain Management Release SAP

choose the fields from the value help for the Characteristics field in the Customizing activity MaintainProduct Allocation Group.)

The field catalog is contained in the /SAPAPO/VMIALLOC structure. If you want to addcustomer-specific fields to the field catalog, create a structure that contains these fields. Using the SE11transaction, you add the structure to the /SAPAPO/VMIALLOC structure.

Using the BAdI VMI Product Allocation: Values for Field Catalog (/SAPAPO/VMIALLOCVALS),which was already available previously, you can determine the values for the customer-specific fields.

Note that you can only use product allocation in an SCM server installation. In the SAP SCM system, youdefine product allocation groups in Customizing for Advanced Planning and Optimization underGlobal Available-to-Promise (Global ATP) -> Product Allocation -> Maintain Product AllocationGroup.

1.6.14.2 Minimum and Maximum Lot Size (New)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the replenishment service and the TLB servicecan consider the minimum and the maximum lot size from the location product master for a customerlocation product. The minimum lot size and the maximum lot size are product parameters that restrict thequantity of a planned receipt for the customer location product (time-series-based planned receipt or aplanned replenishment order). The replenishment service only generates planned receipts whose quantitiesare between the minimum lot size and the maximum lot size.

A subsequent TLB run creates TLB shipments based on the planned receipts. During shipment upsizingand downsizing, the TLB respects the minimum lot size and the maximum lot size as well. The productquantity of all TLB shipments in one period must not violate the minimum lot size and maximum lot size.

______________________________________________________________SAP AG 133

SAP-System______________________________________________________________

Page 142: Release Notes for SAP Supply Chain Management Release SAP

1.6.14.3 Two-Level Rounding (New)

Use

As of SAP Supply Network Collaboration (SAP SNC 7.0), two-level rounding is available forreplenishment planning. Two-level rounding is a rounding method that considers two different roundingvalues and a threshold value. It chooses the rounding value to be applied depending on the quantity to berounded and the threshold value. The system first divides the quantity by the large rounding value. Theremaining quantity is handled in a special way: It is first rounded up with respect to the small roundingunit. The replenishment service only rounds up the rounded remaining quantity to the large roundingvalue as well if the rounded remaining quantity exceeds the threshold.

Effects on Customizing

If you want the replenishment service to use two-level rounding for a customer location product instead ofnormal one-value rounding, you must assign the location product a rounding profile with two levels. Youdefine rounding profiles in Customizing for SCM Basis under Master Data -> Product -> MaintainRounding Profiles.

See also

SAP Library for SAP Supply Chain Management (SAP SCM) on SAP Help Portal athttp://help.sap.com -> SAP Supply Network Collaboration -> Replenishment -> ReplenishmentPlanning -> Replenishment Service -> Rounding -> Two-Level Rounding.

1.6.14.4 Safety Stock Planning (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, you can use the safety stock planning methodSM to build up safety stock. The safety stock method SM, considers safety stock derived using the existingsafety stock methods SZ and SB. As a final safety stock, it takes the maximum derived from methods SZand SB as the safety stock. In addition, the system takes the minimum safety stock into considerationwhen planning safety stock.

______________________________________________________________SAP AG 134

SAP-System______________________________________________________________

Page 143: Release Notes for SAP Supply Chain Management Release SAP

1.6.15 SCM-ICH-PRO Promotion Planning

1.6.15.1 Determining the Promotion ID (Enhanced)

Use

Previously, in the promotion planning process of a Responsive Replenishment scenario, SAP SupplyNetwork Collaboration (SAP SNC) determined the promotion ID as follows:

- Using the external promotion ID that was transmitted as the promotion ID in theDemandInfluencingEventNotification XML message.

- Creating a promotion ID by combining the three letter string XML and the creation time stamp of theDemandInfluencingEventNotification XML message.

The system did not consider the internal promotion ID of the XML message.

As of SAP SNC 7.0, the following enhancements are available:

- SAP SNC can also consider the internal promotion ID transmitted in theDemandInfluencingEventNotification XML message when it determines a promotionID.

- The following Web screens now display the Internal Promotion ID field:

- Promotions - XML Draft Promotion

- Promotions - Promotion Planning

Effects on Customizing

To determine a promotion ID using the internal promotion ID and, or, the external promotion ID, youmust make settings in Customizing for SAP Supply Network Collaboration in the Customizing activityDefine Expected Promotion IDs.

1.6.16 SCM-ICH-TLB Transport Load Builder

1.6.16.1 Product Allocation (Enhanced)

Use

In SAP Supply Network Collaboration (SAP SNC), you can use the product allocation check from Global

______________________________________________________________SAP AG 135

SAP-System______________________________________________________________

Page 144: Release Notes for SAP Supply Chain Management Release SAP

Available-to-Promise (Global ATP) in SAP Advanced Planning and Optimization (SAP APO). Using theproduct allocation check, you can make sure that the replenishment quantities for a product that areprovided by a particular ship-from location do not exceed product allocations and are restrictedcorrespondingly.

As of SAP SNC 7.0, you can extend the field catalog for VMI product allocation with customer-specificfields. The additional fields are available for the product allocation group. (This means that you canchoose the fields from the value help for the Characteristics field in the Customizing activity MaintainProduct Allocation Group.)

The field catalog is contained in the /SAPAPO/VMIALLOC structure. If you want to addcustomer-specific fields to the field catalog, create a structure that contains these fields. Using the SE11transaction, you add the structure to the /SAPAPO/VMIALLOC structure.

Using the BAdI VMI Product Allocation: Values for Field Catalog (/SAPAPO/VMIALLOCVALS),which was already available previously, you can determine the values for the customer-specific fields.

Note that you can only use product allocation in an SCM server installation. In the SAP SCM system, youdefine product allocation groups in Customizing for Advanced Planning and Optimization underGlobal Available-to-Promise (Global ATP) -> Product Allocation -> Maintain Product AllocationGroup.

1.6.16.2 Minimum and Maximum Lot Size (New)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the replenishment service and the TLB servicecan consider the minimum and the maximum lot size from the location product master for a customerlocation product. The minimum lot size and the maximum lot size are product parameters that restrict thequantity of a planned receipt for the customer location product (time-series-based planned receipt or aplanned replenishment order). The replenishment service only generates planned receipts whose quantitiesare between the minimum lot size and the maximum lot size.

A subsequent TLB run creates TLB shipments based on the planned receipts. During shipment upsizingand downsizing, the TLB respects the minimum lot size and the maximum lot size as well. The productquantity of all TLB shipments in one period must not violate the minimum lot size and maximum lot size.

______________________________________________________________SAP AG 136

SAP-System______________________________________________________________

Page 145: Release Notes for SAP Supply Chain Management Release SAP

1.6.16.3 Transport Load Building (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, the following enhancements are available:

- New fields on the TLB Shipments screenThe following columns have been added to the TLB Shipments Details area of the TLBShipments screen:

- Replenishment DemandThe replenishment demand is the quantity that served as the initial input for the TLB shipment(before the TLB performed upsizing or downsizing).

- Shipment Sizing QuantityThe shipment sizing quantity is the quantity by which the TLB increased (+) or decreased (-)the replenishment demand for the TLB shipment during shipment sizing.

- Consideration of minimum and maximum lot sizeDuring shipment upsizing and downsizing, the TLB respects the minimum lot size and themaximum lot size from the location product master of the customer location product. The productquantity of all TLB shipments in one period must not violate the minimum lot size or maximum lotsize.

- New BAdI for integrating an external load builderUsing the new Business Add-In (BAdI) External Transport Load Building(/SCA/EXT_LOAD_BUILD), you can integrate an external load builder. With an active BAdIimplementation, the TLB service calls up the external load builder instead of the Transport LoadBuilder of SAP SNC. The TLB service only provides the TLB settings and the demands to the BAdI.Based on this data, the external load builder can build loads and return them to the TLB service. Forthese loads, the TLB service creates the TLB shipments and the replenishment orders.

Effects on Customizing

You can call up the BAdI in Customizing for Supply Network Collaboration, by choosing BusinessAdd-Ins (BAdIs) for SAP SNC -> Replenishment -> Transport Load Builder -> BAdI: ExternalTransport Load Building.

See also

Release Note Minimum and Maximum Lot Size (New)

______________________________________________________________SAP AG 137

SAP-System______________________________________________________________

Page 146: Release Notes for SAP Supply Chain Management Release SAP

1.6.17 SCM-ICH-DIO Inbound/Outbound Data Processing

1.6.17.1 SAP SNC Monitoring with CCMS (New)

Use

As of SAP NetWeaver 7.0 Enhancement Package 01 and SAP Supply Network Collaboration (SAP SNC)7.0, you can use the predefined monitor set SNC Monitor Templates in the monitoring architecture ofthe Computing Center Management System (CCMS). The CCMS Monitoring Architecture is aframework available in SAP NetWeaver into which monitoring and administration functions can beadded.

The SNC Monitor Templates monitor set includes the following:

- CIF Master Data Queue MonitorThe CIF Master Data Queue Monitor allows you to monitor inbound and outbound queues for theSAP Core Interface (CIF).

- SNC MonitorFor each SAP SNC client of the system landscape, the SNC Monitor allows you to monitor inboundand outbound message processing of XML messages.

Effects on System Administration

To use the SNC Monitor Templates monitor set as a template for your own monitor, copy the desiredmonitor and adapt it to your needs. If you run CCMS from a central system to monitor your systemlandscape, set up system connections with your SAP SNC systems. For more information, see the SAPSNC documentation on SAP Help Portal at http://help.sap.com under SAP SNC Monitoring withCCMS.

Effects on Customizing

Check the settings in the Customizing activity Restrict Alerts in Customizing for Supply NetworkCollaboration under Basic Settings -> Processing Inbound and Outbound Messages. You need tomake sure that the alerts for the message types that you want to monitor are not deactivated.

1.6.17.2 Inventory in SMI and Outsourced Manufacturing (Enhanced)

Use

______________________________________________________________SAP AG 138

SAP-System______________________________________________________________

Page 147: Release Notes for SAP Supply Chain Management Release SAP

As of SAP Supply Network Collaboration (SAP SNC) 7.0 and enhancement package 4 for SAP ERP 6.0,the following enhancements are available:

- You can transmit stock in transfer from SAP ERP to SAP SNC and consider it in Supply NetworkInventory (SNI) and Supplier Managed Inventory (SMI). In SAP ERP, you create stock in transfer ifyou post a stock transfer between two plants or two storage locations using a two-step postingprocedure. In addition, you can now transmit the subcontracting stock in transfer, which is relevantfor SNI only. Subcontracting stock in transfer is created when you move subcontracting componentsfrom your own stock to the subcontracting stock using a two-step posting procedure. To supportthese stock types in SAP SNC, the relevant functions and objects were enhanced as described below.

- You can transmit individual batch inventories for batch-managed inventories including batchclassification.

ProductActivityNotification (PROACT)

The following new fields were added to the ProductActivityNotification XML message type,which is used to transmit inventory data from SAP ERP to SAP SNC:

- StockInTransferQuantityThis field is used to transmit the total of stock in transfer between plants and stock in transferbetween storage locations.

- SubcontractingStockInTransferQuantityThis field is used to transmit subcontracting stock in transfer.

For batch-managed products, batch IDs were added (internal batch ID, supplier batch ID, and customerbatch ID). In addition, the message now can transmit characteristic values for a batch.

Reports for Data Transfer from SAP ERP to SAP SNC

The reports for transferring data from SAP ERP to SMI or SNI were enhanced as follows:

- Report for data transfer to SMIThe Data Transfer from ERP to SNC for SMI, RP, DR (RSMIPROACT2) report includesselection parameters for stock in transfer between plants and stock in transfer between storagelocations. (Note that the ProductActivityNotification XML message only transmits thetotal stock in transfer.)

- Reports for data transfer to SNIThe following reports include selection parameters for stock in transfer between plants, stock intransfer between storage locations, and for subcontracting stock in transfer.

- Data Transfer for Contract Manufacturing (Own Data) (ROEMPROACT2)

- Data Transfer for Contract Manufacturing (Partner Plant) (RPRTPROACT)

Note that you can select stock in transfer between plants or between storage locations individually.However, the ProductActivityNotification XML message transmits the total of thesestock types. )

The report Data Transfer for Contract Manufacturing (Partner Data) (RCMPROACT2) reportcontains a selection parameter for subcontracting stock in transfer.If you want to use these report enhancements, you must activate the SAP ERP business functionOutsourced Manufacturing (LOG_MM_OM_1).

______________________________________________________________SAP AG 139

SAP-System______________________________________________________________

Page 148: Release Notes for SAP Supply Chain Management Release SAP

Transfer of Individual Batches

The following reports for data transfer to SNI now include an Individual Batches checkbox:

- Data Transfer for Contract Manufacturing (Own Data) (ROEMPROACT2)

- Data Transfer for Contract Manufacturing (Partner Data) (RCMPROACT2)

If you select the checkbox, the reports transmit the individual batches including batch number and batchclassification values for a batch-managed material. Previously, you could only transmit the aggregatedbatch quantity for a selected batch-managed material (without batch numbers or classification values).

If you want to use these report enhancements, you must activate the SAP ERP business functionOutsourced Manufacturing (LOG_MM_OM_1).

Note: If you have transmitted inventory previously and you now want to use the new option and transmitindividual batches, you must first reset the inventory in SAP SNC, using the Reset Inventory to Zeroreport (/SCA/DM_RESETINV) report. This is to prevent stock values for a batch-managed materialfrom existing twice in SAP SNC (aggregated value and values for the individual batches).

Changes on the Web Screens of the SMI Monitor and SNI Monitor

In the SMI Monitor, the following stock types are displayed:

- Stock in transfer

- Consignment stock in transfer

In the SNI Monitor, the following stock types are displayed:

- Stock in transfer

- Consignment stock in transfer

- Subcontracting stock in transfer

- Consignment subcontracting stock in transfer

Stock in transfer and subcontracting stock in transfer are included on the new Inventory Overviewscreen for SNI, for example.

Stock on Hand and Projected Stock

As of SAP SNC 7.0, the following enhancements are available:

- Calculating the stock on handThe stock on hand is part of the default formula for calculating the projected stock. The default stockon hand in the projected stock formula for SMI, Responsive Replenishment, and Delivery ControlMonitor now also includes the stock in transfer and the consignment stock in transfer. The defaultcoding for the Business Add-In (BAdI) Calculation of Stock on Hand(/SCA/ICH_STOCKONHAND) was enhanced accordingly.

- Defining own profiles for projected stockYou can add the new stock types to your projected stock profiles in Customizing for ProjectedStock if needed.

- Standard profiles for the projected stockThe following SAP standard profiles for calculating the projected stock (listed in the Customizing

______________________________________________________________SAP AG 140

SAP-System______________________________________________________________

Page 149: Release Notes for SAP Supply Chain Management Release SAP

activity Display Standard Profiles for Projected Stock) now also include the stock in transferand the subcontracting stock in transfer:

- ASN

- RODP

- RODP_ASN

- ROP

- ROP_ASN

1.6.17.3 Location Product Status (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, functions for the location product status havebeen enhanced as follows:

- Automatic changes to the location product status can be customized.

- Maintenance of the location product status has been enhanced.

Automatic Change of the Location Product Status

In previous releases, SAP SNC automatically set the location product status from Active to Inactive orfrom Inactive to Discontinued when the following conditions were met during inbound processing:

- The 2_MISSING_EAN/UPC validation check is active.

- The ProductActivityNotification message does not contain any data for this location product.

As of SAP SNC 7.0, you can determine in Customizing whether SAP SNC automatically sets the status toInactive or Discontinued when the above conditions are met.

Maintenance of the Location Product Status

In previous releases, you could only maintain the status of single location products one at a time on theLocation Product Status Web screen. As of SAP SNC 7.0, you can create, change, or delete the statusof multiple location products in a mass maintenance. Moreover, on the Location Product Status Webscreen, you can now search for location products by product group and by product group type.

______________________________________________________________SAP AG 141

SAP-System______________________________________________________________

Page 150: Release Notes for SAP Supply Chain Management Release SAP

Effects on Customizing

To prevent SAP SNC from automatically setting the location product status to Inactive or Discontinued,in Customizing, select the No Inactive Status checkbox . For more information, see Customizing forSupply Network Collaboration under Basic Settings -> Processing Inbound and OutboundMessages -> Configure Processing of Inbound ProductActivityNotification Data. In the standardsystem, the No Inactive Status checkbox is not selected, that is, inbound processing behaves as inprevious releases.

1.6.18 SCM-ICH-AMO Alert Monitor

1.6.18.1 Activation of Alert Types (Changed)

Use

Previously, all alert types relevant to SAP Supply Network Collaboration (SAP SNC) were active in thestandard system. As of SAP SNC 7.0, all SAP SNC alert types in the standard system are not active. Youmust activate the alert types relevant to the SAP SNC applications you want to run. In addition, you candetermine whether you want alert types to be archived into the alert history tables. You do this to increasethe performance speed of the following processes:

- Alert creation

- Reading of alerts

- Deletion and subsequent archiving of alerts into the alert history tables

Effects on Customizing

You activate alert types in Customizing for SAP Supply Network Collaboration under Exceptions ->Alert Type Activation -> Activate Alert Types.

1.6.18.2 SAP SNC Monitoring with CCMS (New)

Use

As of SAP NetWeaver 7.0 Enhancement Package 01 and SAP Supply Network Collaboration (SAP SNC)7.0, you can use the predefined monitor set SNC Monitor Templates in the monitoring architecture of

______________________________________________________________SAP AG 142

SAP-System______________________________________________________________

Page 151: Release Notes for SAP Supply Chain Management Release SAP

the Computing Center Management System (CCMS). The CCMS Monitoring Architecture is aframework available in SAP NetWeaver into which monitoring and administration functions can beadded.

The SNC Monitor Templates monitor set includes the following:

- CIF Master Data Queue MonitorThe CIF Master Data Queue Monitor allows you to monitor inbound and outbound queues for theSAP Core Interface (CIF).

- SNC MonitorFor each SAP SNC client of the system landscape, the SNC Monitor allows you to monitor inboundand outbound message processing of XML messages.

Effects on System Administration

To use the SNC Monitor Templates monitor set as a template for your own monitor, copy the desiredmonitor and adapt it to your needs. If you run CCMS from a central system to monitor your systemlandscape, set up system connections with your SAP SNC systems. For more information, see the SAPSNC documentation on SAP Help Portal at http://help.sap.com under SAP SNC Monitoring withCCMS.

Effects on Customizing

Check the settings in the Customizing activity Restrict Alerts in Customizing for Supply NetworkCollaboration under Basic Settings -> Processing Inbound and Outbound Messages. You need tomake sure that the alerts for the message types that you want to monitor are not deactivated.

1.6.18.3 Control of Actions for Purchase Order and Replenishment Order(Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, validation checks can trigger the generation ofthe following alerts in the background.

Purchase Order Alerts

Alert Type Alert ID

Purchase Order Rejected 7036

Purchase Order Item rejected 7037

Partially Confirmed Purchase Order Item 7053

Late Confirmation of Purchase Order Item 7054

______________________________________________________________SAP AG 143

SAP-System______________________________________________________________

Page 152: Release Notes for SAP Supply Chain Management Release SAP

Manual Approval of Confirmation Required 7055

Manual Approval of Component Requirement required 7056

Confirmation Rejected 7057

Component Requirement Rejected 7058

New Note for Purchase Order 7059

Replenishment Order Alerts

Alert Type Alert ID

Confirmation of Replenishment Order Item Was Rejected 7126

Partially Confirmed Replenishment Order Item 7124

Too-Late Confirmation of Replenishment Order Item 7125

The system can also connect to the supplier delivery performance rating (SDPR) in the background basedon the PPF configuration.

To generate these alerts and to connect to SDPR in the background, you must deactivate the followingvalidation checks:

- For purchase orders: PO_PPF_EXEC

- For replenishment orders: RO_PPF_EXEC.

If you have specified that the system generates these alerts in the background, you can still deactivate eachalert individually or deactivate the SDPR connection by selecting the Inactive checkbox in the PPF forthe relevant PPF action.

Effects on Customizing

You activate and deactivate these validation checks in Customizing for Supply Network Collaborationby choosing Basic Settings -> Validation -> Own Settings -> Maintain Settings in Validation Profiles.

You can make PPF settings in Customizing for Supply Network Collaboration by choosing Tools ->Actions (Post Processing Framework) -> Define Action Profiles and Definitions and editing the/SCA/BOL_ORDER action profile within the /SCA/ICH application.

1.6.19 SCM-ICH-ERP ERP-SNC Integration

1.6.19.1 Inventory in SMI and Outsourced Manufacturing (Enhanced)

______________________________________________________________SAP AG 144

SAP-System______________________________________________________________

Page 153: Release Notes for SAP Supply Chain Management Release SAP

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0 and enhancement package 4 for SAP ERP 6.0,the following enhancements are available:

- You can transmit stock in transfer from SAP ERP to SAP SNC and consider it in Supply NetworkInventory (SNI) and Supplier Managed Inventory (SMI). In SAP ERP, you create stock in transfer ifyou post a stock transfer between two plants or two storage locations using a two-step postingprocedure. In addition, you can now transmit the subcontracting stock in transfer, which is relevantfor SNI only. Subcontracting stock in transfer is created when you move subcontracting componentsfrom your own stock to the subcontracting stock using a two-step posting procedure. To supportthese stock types in SAP SNC, the relevant functions and objects were enhanced as described below.

- You can transmit individual batch inventories for batch-managed inventories including batchclassification.

ProductActivityNotification (PROACT)

The following new fields were added to the ProductActivityNotification XML message type,which is used to transmit inventory data from SAP ERP to SAP SNC:

- StockInTransferQuantityThis field is used to transmit the total of stock in transfer between plants and stock in transferbetween storage locations.

- SubcontractingStockInTransferQuantityThis field is used to transmit subcontracting stock in transfer.

For batch-managed products, batch IDs were added (internal batch ID, supplier batch ID, and customerbatch ID). In addition, the message now can transmit characteristic values for a batch.

Reports for Data Transfer from SAP ERP to SAP SNC

The reports for transferring data from SAP ERP to SMI or SNI were enhanced as follows:

- Report for data transfer to SMIThe Data Transfer from ERP to SNC for SMI, RP, DR (RSMIPROACT2) report includesselection parameters for stock in transfer between plants and stock in transfer between storagelocations. (Note that the ProductActivityNotification XML message only transmits thetotal stock in transfer.)

- Reports for data transfer to SNIThe following reports include selection parameters for stock in transfer between plants, stock intransfer between storage locations, and for subcontracting stock in transfer.

- Data Transfer for Contract Manufacturing (Own Data) (ROEMPROACT2)

- Data Transfer for Contract Manufacturing (Partner Plant) (RPRTPROACT)

Note that you can select stock in transfer between plants or between storage locations individually.However, the ProductActivityNotification XML message transmits the total of thesestock types. )

The report Data Transfer for Contract Manufacturing (Partner Data) (RCMPROACT2) reportcontains a selection parameter for subcontracting stock in transfer.If you want to use these report enhancements, you must activate the SAP ERP business function

______________________________________________________________SAP AG 145

SAP-System______________________________________________________________

Page 154: Release Notes for SAP Supply Chain Management Release SAP

Outsourced Manufacturing (LOG_MM_OM_1).

Transfer of Individual Batches

The following reports for data transfer to SNI now include an Individual Batches checkbox:

- Data Transfer for Contract Manufacturing (Own Data) (ROEMPROACT2)

- Data Transfer for Contract Manufacturing (Partner Data) (RCMPROACT2)

If you select the checkbox, the reports transmit the individual batches including batch number and batchclassification values for a batch-managed material. Previously, you could only transmit the aggregatedbatch quantity for a selected batch-managed material (without batch numbers or classification values).

If you want to use these report enhancements, you must activate the SAP ERP business functionOutsourced Manufacturing (LOG_MM_OM_1).

Note: If you have transmitted inventory previously and you now want to use the new option and transmitindividual batches, you must first reset the inventory in SAP SNC, using the Reset Inventory to Zeroreport (/SCA/DM_RESETINV) report. This is to prevent stock values for a batch-managed materialfrom existing twice in SAP SNC (aggregated value and values for the individual batches).

Changes on the Web Screens of the SMI Monitor and SNI Monitor

In the SMI Monitor, the following stock types are displayed:

- Stock in transfer

- Consignment stock in transfer

In the SNI Monitor, the following stock types are displayed:

- Stock in transfer

- Consignment stock in transfer

- Subcontracting stock in transfer

- Consignment subcontracting stock in transfer

Stock in transfer and subcontracting stock in transfer are included on the new Inventory Overviewscreen for SNI, for example.

Stock on Hand and Projected Stock

As of SAP SNC 7.0, the following enhancements are available:

- Calculating the stock on handThe stock on hand is part of the default formula for calculating the projected stock. The default stockon hand in the projected stock formula for SMI, Responsive Replenishment, and Delivery ControlMonitor now also includes the stock in transfer and the consignment stock in transfer. The defaultcoding for the Business Add-In (BAdI) Calculation of Stock on Hand(/SCA/ICH_STOCKONHAND) was enhanced accordingly.

- Defining own profiles for projected stockYou can add the new stock types to your projected stock profiles in Customizing for ProjectedStock if needed.

- Standard profiles for the projected stock

______________________________________________________________SAP AG 146

SAP-System______________________________________________________________

Page 155: Release Notes for SAP Supply Chain Management Release SAP

The following SAP standard profiles for calculating the projected stock (listed in the Customizingactivity Display Standard Profiles for Projected Stock) now also include the stock in transferand the subcontracting stock in transfer:

- ASN

- RODP

- RODP_ASN

- ROP

- ROP_ASN

1.6.19.2 Purchase Order XML Messages (Enhanced)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, new XML messages are available for sendingand receiving purchase order data. In addition, the existing XML messages include new fields that supportthe new processes in purchase order collaboration.

New XML Messages

Previously, SAP SNC could only use the following XML messages for the processes in purchase ordercollaboration:

- ReplenishmentOrderNotification for receiving a new or changed purchase order fromthe customer back-end system

- ReplenishmentOrderConfirmation for sending a purchase order confirmation to thecustomer back-end system

- ReplenishmentOrderNotification for sending a changed purchase order to the customerback-end system

As of SAP SNC 7.0, you can send and receive the following XML message types for purchase ordercollaboration instead:

- PurchaseOrderERPReplenishmentOrderCollaborationNotification forreceiving a new or changed purchase order from the customer back-end system

- PurchaseOrderERPRequest_V1 for sending a changed purchase order to the customerback-end system

The new XML messages provide integration with a customer's SAP ERP back-end system that is

______________________________________________________________SAP AG 147

SAP-System______________________________________________________________

Page 156: Release Notes for SAP Supply Chain Management Release SAP

enhancment package 4 for SAP ERP. If you want to use the new XML messages, you must deactivate thePO_PURORDERPREQ_SEND validation check. Note, that theReplenishmentOrderConfirmation XML message is still used for receiving and sendingpurchase order confirmations.

New Fields in the existing XML Messages

As of SAP SNC 7.0, the following existing XML message types have been enhanced with the followingfields:

- ReplenishmentOrderNotification

- ManufacturerParty

- ManufacturerID

- ConfigurationPropertyValuation

- ProductManufacturerID

- ClassificationPropertyValuation

- ReplenishmentOrderConfirmation

- ManufacturerParty

- ManufacturerID

- ProductManufacturerID

1.6.20 SCM-ICH-FTR File Transfer

1.6.20.1 File Transfer (New)

Use

As of SAP Supply Network Collaboration (SAP SNC) 7.0, you can use the file transfer application on theSAP SNC Web UI to download and upload files from SAP SNC, to process their data offline. Filetransfer converts data from SAP SNC applications into Comma Separated Values (CSV) files. In thestandard system, we deliver files for the following supplier collaboration applications:

- Purchase orders

- Download purchase orders requiring confirmation

______________________________________________________________SAP AG 148

SAP-System______________________________________________________________

Page 157: Release Notes for SAP Supply Chain Management Release SAP

- Upload purchase order confirmations

- Due list and advanced shipping notifications for purchasing documents

- Download due list for purchasing documents

- Upload advanced shipping notifications for purchasing documents

- Due list and advanced shipping notifications for planned receipts

- Download due list for planned receipts

- Upload advanced shipping notifications for planned receipts

- Order forecast monitor

- Download forecast

- Upload supplier firm receipts

- Supplier managed inventory

- Download demand

- Upload planned receipts

Web Screens

The following Web screens are available for file transfer on the SAP SNC Web UI:

- Download Center

- Download History

- Upload Center

- Upload History

For every file transfer Web screen, there is a Power User view and an External User view, as follows:

- The Power User view is designed for a user who creates download and upload profiles for theexternal business partners of the business partner that is leading a collaboration process of SAPSNC. The Web screens display all file that are being or have been downloaded or uploaded by theexternal business partners of the leading business partner.

- The External User view of the file transfer Web screens is designed for a user who is assigned toan external business partner. The Web screens display files that belong to the business partner of thelogged-on user.

You can download files from the Download Center Web screen. You can pick up downloaded files fromthe Download Center Web screen, or file transfer can deliver files that you download by means of ane-mail. In the standard system, we deliver templates for the e-mail text that notify the user that a file isready for download. You can also create your own e-mail texts. After processing a file offline, you canupload it back into the SAP SNC system. You can do that as follows:

- You can send an e-mail containing the file to the system.

- You can upload the file manually on the Upload Center Web screen.

Archiving

You can archive a download or upload profile if it is no longer active. We deliver the following archiving

______________________________________________________________SAP AG 149

SAP-System______________________________________________________________

Page 158: Release Notes for SAP Supply Chain Management Release SAP

objects for file transfer:

- ICH_FTRD

- ICH_FTRU

Effects on Data Transfer

The standard e-mail texts we deliver for the notification e-mails are SAPscript objects. To be able to usethe e-mail texts, you need to transport them from client 000. For more information, see SAP Note 3355.

Effects on System Administration

For each file download or upload you need download and upload profiles. Run the Delete File TransferProfiles (/SCA/FTR_DELETE) report if you want to delete the profiles without archiving them. Tocreate a standard e-mail text, run the Create E-Mail Texts for File Download Notifications(/SCF/FTR_CREATE_MT) report . You must set up number ranges for the upload profile numbers andthe download profile numbers. To set up number ranges, you use the Number Ranges (SRNO)transaction.

Effects on Customizing

To use file transfer, you must make the necessary settings in Customizing for SAP Supply NetworkCollaboration under Tools -> File Transfer.

For file transfer the following Business Add-Ins (BAdIs) are available in Customizing for SAP SupplyNetwork Collaboration under Business Add-Ins (BAdIs) for SAP SNC -> Tools -> File Transfer:

- BAdI: Read Inbound E-Mail

- BAdI: Purchase Order Interface

- BAdI: ASN Publish Control

- BAdI: Due List for Purchasing Documents

- BAdI: Due List for Planned Receipts

- BAdI: Order Forecast Collaboration Interface

- BAdI: SMI Planned Receipt

See also

File Transfer in SAP Library for SAP Supply Network Collaboration under Cross-ApplicationsFunctions -> File Transfer.

______________________________________________________________SAP AG 150

SAP-System______________________________________________________________