Snc100 en Col81 Fv Part a4

SNC100Supplier Collaboration with SAP

SNCmySAP Supply Chain Management

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 81Course Duration: 3 Day(s)Material Number: 50089112

An SAP course - use it to learn, reference it for work

Copyright

Copyright © 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

� Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® areregistered trademarks of Microsoft Corporation.

� IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®,S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

� ORACLE® is a registered trademark of ORACLE Corporation.� INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered

trademarks of Informix Software Incorporated.� UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.� Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

� HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, WorldWide Web Consortium, Massachusetts Institute of Technology.

� JAVA® is a registered trademark of Sun Microsystems, Inc.� JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.� SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

g200842853320

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal (in this documentation) and external (inother locations, such as SAPNet).

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2008 © 2008 SAP AG. All rights reserved. iii

About This Handbook SNC100

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

iv © 2008 SAP AG. All rights reserved. 2008

ContentsCourse Overview ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Unit 1: Overview on Supply Network Collaboration ..... . . . . . . . . . . 1Supply Network Collaboration Overview... . . . . . . . . . . . . . . . . . . . . . . . . . .2Data Integration and System Landscape Overview .... . . . . . . . . . . 33

Unit 2: Purchase Order Collaboration with SAP SNC ..... . . . . . . 45Purchase Order Process Overview... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Purchase Order Processing: Process Demo... . . . . . . . . . . . . . . . . . . . 60PO Process � Integration .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Relevant Customizing for Purchase Order Processing in SAPSNC ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Unit 3: Release Process with SAP SNC ...... . . . . . . . . . . . . . . . . . . . . . . 89Scheduling Agreement Release Process - Overview .... . . . . . . . . 90Release Processing: Process Demo.... . . . . . . . . . . . . . . . . . . . . . . . . . .101Relevant Customizing for Release Processing with SAP SNC 110

Unit 4: ASN Processing in SAP SNC ...... . . . . . . . . . . . . . . . . . . . . . . . . . 117ASN Processing Overview... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Packing... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Process Demo: ASN Processing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149Relevant Customizing for ASN Processing in SAP SNC ... . . . .163

Unit 5: Invoice Collaboration in SAP SNC ...... . . . . . . . . . . . . . . . . . . 173Invoice Collaboration Process Overview... . . . . . . . . . . . . . . . . . . . . . . .174Process Demo: Invoice Collaboration... . . . . . . . . . . . . . . . . . . . . . . . . . .189Relevant Customizing for Invoice Collaboration in SAP SNC..203

Unit 6: Master Data ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Master Data... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208Master Data Integration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Visibility Concept . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227

Unit 7: Supplier Managed Inventory Process (SNC)..... . . . . . . . 235Supplier Managed Inventory Process in SAP SNC .... . . . . . . . . .236Process Demo & Exercise: SMI Process.. . . . . . . . . . . . . . . . . . . . . . . .253

2008 © 2008 SAP AG. All rights reserved. v

Contents SNC100

Relevant System Settings and Customizing for SMI in SAPSNC ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Unit 8: Further Processes in SAP SNC ...... . . . . . . . . . . . . . . . . . . . . . . 275Dynamic Replenishment .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276Delivery Control Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283Kanban Process with SAP SNC ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289Work Order Collaboration with SAP SNC.... . . . . . . . . . . . . . . . . . . . . .300SNI and Subcontracting PO ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327

Unit 9: Alert Notification (SNC) ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345Alert Notification in SAP SNC .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346Relevant System Settings and Customizing for AlertNotification .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350

Process Demo & Exercise: Alert Notification .. . . . . . . . . . . . . . . . . . .355Creating own SNC alerts.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366

Unit 10: Authorization ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371Authorization Within SAP SNC... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372Process Demo: Authorization Objects in SAP SNC... . . . . . . . . . .375

Glossary..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

vi © 2008 SAP AG. All rights reserved. 2008

Course OverviewThis course will introduce you to SAP Supply Network Collaboration (SAPSNC). You will get an overview of the capabilities of the solution and hands-onexperience with some of the processes. This course also covers possible systemlandscapes and authorization for SAP SNC.

Target AudienceThis course is intended for the following audiences:

� Consultants� Project team members

Course PrerequisitesRequired Knowledge

� SAP MM� SAP01 (SAP Overview)

Recommended Knowledge

� SAPSCM (SAP SCM Overview)

Course GoalsThis course will prepare you to:

� Understand the benefits of SAP SNC� Understand the system landscape and data integration of SAP SNC� Explain the different SAP SNC business processes� Perform some typical collaboration processes

Course ObjectivesAfter completing this course, you will be able to:

� Explain the different processes for supplier collaboration in SAP SNC� Describe the system landscape used by SAP SNC

2008 © 2008 SAP AG. All rights reserved. vii

Course Overview SNC100

� Discuss process details for:

- Purchase order- Scheduling agreement release- Advance shipping notification- Invoice collaboration- Supplier-managed inventory

� Explain the process flow for the following SAP SNC processes:- Dynamic replenishment- Delivery Control Monitor- Kanban- Work order- Supply Network Inventory and subcontracting purchase order

� Describe the functionality of exception management and alert notification� Discuss authorization within SAP SNC

viii © 2008 SAP AG. All rights reserved. 2008

Unit 1Overview on Supply Network

Collaboration

Unit OverviewThis unit will give you an overview of SAP SNC. You will about the processeswithin SAP SNC and the SAP SNC system landscape.

Unit ObjectivesAfter completing this unit, you will be able to:

� Explain the capabilities of SAP SNC� Discuss the benefits of using SAP SNC� Name the existing SAP SNC processes� Name the two different deployment options for SAP SNC 5.1� Name the involved systems of a simple SNC system landscape

Unit ContentsLesson: Supply Network Collaboration Overview ... . . . . . . . . . . . . . . . . . . . . . . . . . .2Lesson: Data Integration and System Landscape Overview... . . . . . . . . . . . . 33

2008 © 2008 SAP AG. All rights reserved. 1

Unit 1: Overview on Supply Network Collaboration SNC100

Lesson: Supply Network Collaboration Overview

Lesson OverviewThis lesson will give you an overview of SAP Supply Network Collaboration. Youwill learn about existing processes in SAP SNC supplier collaboration.

Lesson ObjectivesAfter completing this lesson, you will be able to:

� Explain the capabilities of SAP SNC� Discuss the benefits of using SAP SNC� Name the existing SAP SNC processes

Business Example

Business Background and Strategy

Figure 1: Driving the Supply Network Collaboration Strategy

Globalization and outsourcingGlobalization and outsourcing have resulted in stretched supply chains andincreased risk. Timely analysis, response, and resolution of supply chainissues is impossible due to lack of control.


SNC100 Lesson: Supply Network Collaboration Overview

Lack of visibility beyond the four wallsAnticipating the next supply chain disruption is not possible due to lackof visibility.

Rising energy and fuel costsRising energy and fuel costs have increased cost and challenges ofcompliance and transportation.

Poor customer servicePoor customer services results in an inability to sense and respond toreal-time demand signals.

Figure 2: SAP Addresses the Challenges Enabling Adaptive Supply ChainNetworks

Enhance visibility and productivity: Real-time visibility of inventory, incomingsupply, component consumption and carrier information

Increase control and flexibility: Change orders based on customer demands, andadjusted supply chain strategies (for example, postponement)

Collaborate successfully: Reduce lead times and cycle times through improvedcollaboration and communication

Increase customer service: Fulfill customer orders on time, with the correct itemsand quantities (perfect order)



Figure 3: A 360-Degree View On Collaboration

Supply Network Collaboration (SNC) is one of the core capabilities of adaptivesupply chain networks, and is a fundamental principle for the networked andoutsourced enterprise of today and tomorrow.

Through SNC, customers and suppliers can eliminate inefficiencies in theirsupply chains by synchronizing the flow of information between them. SNCoffers a 360-degree view on supply chain collaboration, which helps a companyto effectively collaborate with its customers, suppliers, third-party logisticsproviders, and outsourced manufacturing partners.

� On the supplier collaboration side, SNC offers upstream business processeslike supplier-managed inventory, discrete purchase order management,scheduling agreement release handling, and web-based Kanban signals.

� For customer collaboration, SNC offers comprehensive downstreambusiness processes like responsive replenishment, which represents the nextgeneration in demand-driven replenishment and collaboration.

� SNC also offers market-leading capabilities for collaborating and monitoringcontract manufacturing relationships. For outsourced manufacturing, themain capabilities include cross-tier visibility of inventory, supply, anddemand, and a collaborative work order process that tracks work-in-progress,material consumption, and BOM changes at the outsourced manufacturingpartner.



Figure 4: All Suppliers Are Not Equal

In an economic and business environment that challenges your company's profitmargins, you face enormous pressure to reduce costs while increasing innovationand improving customer service and responsiveness. There are several waysto meet these challenges. For example, you could do business in regions andcountries where costs are lower, develop and maintain relationships with globalsuppliers, outsource non-strategic activities to suppliers, and leverage real- timedemand data across your supply chain. All these actions depend on fosteringcollaborative relationships with your suppliers, outsourced contract manufacturers,and customers.

Most enterprises only focus on their top suppliers.

Major investments (such as electronic data interchange) are made to streamlineand optimize these relationships.

Extending such initiatives to the entire supply base is not cost-effective.



Figure 5: SAP SNC: A Multi-Channel Approach

Developing collaborative relationships is not always easy, since each partner hasdifferent technical capabilities. For example, connecting to a supplier with limitedtechnical capabilities can be costly, complicated, and time-consuming.

Telephone, fax, and e-mail remain the most common methods of communication.Even though electronic data interchange (EDI) may be a more reliablecommunication resource, it is cost-effective only in high-volume situations thatinvolve large expenditures.

How, then, can you extend the benefits of streamlined collaboration to your entireecosystem? How can you get all your partners to connect automatically � as wellas efficiently and cost-effectively � to your internal processes?



Figure 6: The Enabler: SAP SNC 5.1

Drive Your Business Vision and Strategy

� The focus of SAP's strategic supply chain efforts� Real-time collaboration with suppliers and customers� Enable adaptive supply chain networks� Out-of-the-box collaborative business processes

Execute Your Collaborative Business Processes

� Automated end-to-end processes� Enable inventory and requirement visibility� Quick and accurate replenishment� Improve data quality and accurancy

Empower Your Employees and Network Partners

� Intuitive, easy to learn, and easy to use� Online and message-based collaboration� Multiple alert and notification methods� Native Web user interface

The answer lies in SAP Supply Network Collaboration (SAP SNC), which ispart of SAP Supply Chain Management (SAP SCM). SAP Supply NetworkCollaboration helps suppliers operating SAP or non-SAP systems to executecollaborative processes through a range of supply, demand, and inventoryreplenishment processes.



SAP SNC helps you connect to and collaborate with your suppliers by providingeasy and seamless access to supply chain information. This application facilitatesyour ability to synchronize supply with demand. Because it offers support forraw-material, component, and contract-manufacturing suppliers, it helps youstrengthen your purchasing operations and your relationships with suppliers ofdirect materials.

With supplier-collaboration processes, you can cooperate with suppliers of allsizes to reduce transactional costs by replacing fax and e-mail as primary modesof communication. Smaller suppliers without specialized EDI infrastructures canintegrate into the supply network by setting up Web access to SAP SNC in theirsoftware landscapes. All they need is Internet access and Web browsers.

You can deploy SAP SNC as a standalone application, or integrate it with SAPor non-SAP back-end solutions on the customer and supplier sides. You can alsooperate SAP SNC in a hosted environment, where it serves as a joint-use platformfor all business supply chain partners involved in the process.

SAP Supply Network Collaboration supports exceptions-based processes that letyour suppliers view the status of materials at customers plants, receive automaticalerts when inventory levels runs low, and respond quickly over the Web. It alsosupports net-demand-release and purchase-order processes, a Kanban process,dynamic replenishment, supplier-managed inventory (the industry-standardreplenishment process), a delivery control monitoring process, a supply networkinventory process, and a contract manufacturing procurement process, as well aspackaging and label-printing functions.



Supply Chain Collaboration with SAP SNC 5.1

Figure 7: SAP SNC Timeline

Major Milestones for SAP SNC:

� First release: SAP Inventory Collaboration Hub (ICH) 4.0 (Ramp-Up Start:June 2003)

� Second release: SAP Inventory Collaboration Hub (ICH) 4.1 (Ramp-UpStart: July 2004)

� Third release: SAP Inventory Collaboration Hub (ICH) 5.0 (Ramp-Up Start:December 2005)

� Fourth release: SAP Supply Network Collaboration (SNC) 5.1 (Ramp-UpStart: July/August 2007)

� Name change: Per the 5.1 release, the application changes names fromICH to SNC to indicate the broader footprint covered and the strategicimportance SAP places on the collaboration space.

� Fifth release: SAP Supply Network Collaboration (SNC) 7.0 (Ramp-UpStart � PLANNED: Q3, 2008)



Figure 8: Functional Growth - SAP SNC Supplier Collaboration



Key functional delta additions per release of SAP ICH/SNC supplier collaboration:

� SAP ICH 4.0:

� Release process� SMI process� ASN

� SAP ICH 4.1:

� PO process� Dynamic Replenishment process (forecast comparison)� Packaging and label printing (with bar codes) added to ASN

� SAP ICH 5.0:

� Kanban process� Contract manufacturing purchasing process (subcontract POs)� Supply Network Inventory process (supply, demand, and inventory

monitoring across plants and business partners)� Delivery Control Monitor process� Goods Receipt user menu (allows for dedicated user menu for

goods recipients, such as third- party logistics providers or contractmanufacturers)

� SAP SNC 5.1:

� Work order collaboration process� Invoicing (to support existing purchasing processes, closing the loop in

the procure-to-pay cycle)� Harmonization, automation, and increased flexibility for SMI

scenarios (more configuration, more algorithms, and more automationcapabilities)

� PO worklist (to enable mass maintenance of PO items)� EM integration� PLM cFolders integration (tighter integration with cFolders)



Figure 9: SAP SNC Supplier Collaboration: Main Value-Adding Capabilities

Main Value-Adding Capabilities of Supplier Collaboration

� Change your communication method:

� Switch from fax, phone calls, and e-mails as the main communicationmethods with your suppliers. SAP SNC gives suppliers a one-stop,web-based tool to access and respond to supply chain, which willreduce human errors and increase the speed and accuracy with whichdata is exchanged between you and your suppliers. In addition,suppliers can respond to data feeds from SAP SNC, which will updateyour ERP system in real time.

� Have suppliers plan and replenish for you:

� SAP SNC has capabilities that allow you to change the businessprocess, allowing the supplier to take responsibility for planning andreplenishment. SAP SNC offers business processes (such as SMI andDCM) that shift the replenishment activities from you to the supplier,still keeping your ERP in sync.

� Enable lean, or pull-based, systems with your suppliers:

� SAP SNC also comes with capabilities that allow you to push throughany lean manufacturing initiatives you may out to your externalsuppliers. Consumption-based replenishment capabilities exist in theshape of Kanban triggers and reorder-point-driven logic.

� Monitor and collaborate with contract manufacturers and other networkpartners:



� Contract manufacturers represent a special type of supplier and, alongwith third-party logistics (3PL) providers, are something SAP SNC hasspecial capabilities to handle. Collaborate on a more granular levelusing BOMs and phases (routing) and find out where a certain productorder is in the process, and when it might be finished. Gain insightsinto the supply-and-demand situation at a contract manufacturers plant,or a 3PL plant participating in the extended supply chain network.

� Complement existing EDI connections with collaborative planning:

� Typically, large manufacturing companies that use SAP ERP (or SAPR/3) have hundreds, if not thousands, of direct material suppliers.A well-know CP industry SAP customer has approximately 5000direct material suppliers in North America, and about 200 of them areconnected via traditional EDI connections (that is, the customer's ERPsystem talks directly to the supplier's ERP system). That means that4800 suppliers are not connected via EDI, and forecasts and ordersare shared via e-mail, Microsoft Excel attachments, phone calls, fax,or simpler supplier portals over the web. However, when looking atthe 200 suppliers that are connected via EDI, most of the data sharedis of short-term, execution character (such as POs, change POs, POconfirmations, or ship notifications) and not much data is shared on along-term horizon. Therefore, SAP SNC can be positioned and usedas a forecast, or mid- to long-term, collaboration platform that canexist in parallel to an existing EDI connection. SAP SNC and EDIconnections can be complementary.

Figure 10: Supplier Collaboration: Business Processes



Purchase Order ProcessIntroduced in SAP ICH 4.1 in 2004; significantly enhanced since then.

Release ProcessIntroduced in SAP ICH 4.0 in 2003. One of the original SAP ICH processes.Enhanced since then.

SMI ProcessIntroduced in SAP ICH 4.0 in 2003. One of the original SAP ICH processes.Significantly enhanced since then.

Dynamic Replenishment ProcessIntroduced in SAP ICH 4.1 in 2004; not enhanced since then.

Figure 11: Supplier Collaboration: Business Processes (2)

Contract manufacturing purchasing process:Introduced in SAP ICH 5.0 in 2005. Somewhat enhanced since then. Thisprocess is called �subcontracting PO� in SAP ERP.

Work order collaboration process:Introduced in SAP SNC 5.1 in 2007

Supply Network Inventory:Introduced in SAP ICH 5.0 in 2005; significantly enhanced since then.

Kanban process:Introduced in SAP ICH 5.0 in 200;, somewhat enhanced since then.



Delivery Control Monitor processIntroduced in SAP ICH 5.0 in 2005; not enhanced since then.

Figure 12: SAP SNC: Purchase Order Process

The purchase order process is a supplier collaboration business process offered aspart of SAP SNC.

The purchase order process allows the customer to send purchase orders to thesupplier using the web-based application SAP SNC. The purchase orders aretypically generated as part of the customer's MRP run, or are manually createdby the customer. The suppliers can view the POs by status, enter free text notes,and print and download. The supplier can enter confirmations or order responsesindicating the date and quantity that can be committed to. At time of shipment, thesupplier can also create ASN messages which, together with the confirmations,update the customer's ERP system.

As of 2007, SAP PLM cFolders can be used together with and integrated toSAP SNC. This allows a supplier to link to cFolders from, for example, thePO in SAP SNC, and access related documents and files such as drawings ortechnical specifications. The supplier can also upload additional, purchase-relateddocuments to cFolders for the customer's benefit.

The main business value is derived from the fact that the customer cancommunicate requirements accurately and in real time, replacing older methodslike phone, fax, and e-mail. The supplier can find his requirements through a webbrowser only, and is proactively alerted to exception situations, like a new PO, onscreen or via e-mails. The supplier can respond to the requirements quickly andaccurately via confirmations and ASNs.



Figure 13: SAP SNC: Scheduling Agreement Release Process

The release process is a supplier collaboration business process offered as partof SAP SNC.

The release process allows for the customer to send out Scheduling AgreementRelease Updates to the supplier using the web-based application SAP SNC. TheSA Releases are typically generated as part of the customer's MRP run. Thesuppliers can view the various �release updates�, compare the differences betweenolder and newer updates and print/download as well. At time of shipment, thesupplier can create ASN messages as well, which updates the customer's ERPsystem.

The main business value is derived from the fact that the customer cancommunicate requirements accurately and in real time, replacing older methodslike phone, fax and e-mail. The supplier can find his requirements thru a webbrowser only, and is proactively alerted to exception situations, like a new updatedrelease, on screen or via e-mails. The supplier can respond to the requirementsquickly and accurately via confirmations and ASNs.



Figure 14: SAP SNC: Supplier-Managed Inventory Process

Supplier-managed inventory is a supplier collaboration business process offeredas part of SAP SNC.

Supplier-managed inventory (SMI) shifts the responsibility for net replenishmentplanning and execution from the customer to the supplier. The supplier uses grossdemand (dependent requirements) and stock balance to calculate a replenishmentplan based on min/max logic, and subsequently converts the plan into purchaseorders and ASNs at time of shipment. The POs and ASNs are sent back to thecustomer's ERP system as indication of commitment from the supplier. POs areoptional in the SMI process; the replenishment plan can be converted directlyinto ASNs if needed.

The main business value is derived from the fact that the customer no longer hasto perform the MRP net planning and replenishment activities, and the suppliercan better utilize his capacity by performing both the planning and execution.



Figure 15: SAP SNC: Dynamic Replenishment

Dynamic replenishment is a supplier collaboration business process offered aspart of SAP SNC.

Dynamic replenishment (DR) allows for a comparison of customer and supplierplanning data in a single-screen environment were deviations between customer'splan and the supplier's plan are shown as absolute numbers and percentages.There are also color-coded thresholds that visualize the deviations on screen. Thecustomer's ERP system is used to extract data such as planned orders and purchaserequisitions which are shown as �customer plan� values in SAP SNC. The sameapplies for previously created POs, which are shown as �customer order� values.The supplier can send in, or enter the corresponding responses via the web, for the�supplier plan� and �supplier order� values.

The main business value is derived from the fact that both supplier and customerhave a mid- to long-term awareness of deviations in supply and demand, and takeappropriate action early to avoid delayed shipments or over production situations.



Figure 16: SAP SNC: Contract Manufacturing Procurement

Contract Manufacturing Procurement is an outsourced manufacturing businessprocess offered as part of SAP SNC.

Contract manufacturing purchasing allows you to send subcontracting purchaseorders to the supplier using SAP SNC. This is an extension of the regular POprocess, and it allows the supplier to view, print, and download the componentlist as part of the PO. The supplier can request changes to the finished goodsquantity and date, as well as the components and quantities. This is part of anapproval process were the customer can approve or reject the request via the web.Components can be added or deleted along with the consumed quantities; allchanges later update the PO in the customer's ERP system.

The main business value is derived from the fact that suppliers and customerscan communicate their respective requirements and responses around acontract manufacturing relationship, accurately and in real time, and their ERPenvironments are kept up to date.



Figure 17: SAP SNC: Work Order Process

The work order process is an outsourced manufacturing business process offeredas part of SAP SNC.

The work order process is a collaborative reflection of the production demandsand the production taking place at the contract manufacturer's location. Thework order tracks high-level production progress through milestones and hascapabilities to project the finished goods date and quantity based on currentproduction progress. It also allows for component changes to the BOM, includinga collaborative approval process. Consumption of components and raw materialsare also tracked, something that is useful in cases when the components are ownedby the customer but are physically available at the contract manufacturer's facility.

The work order exists in SAP SNC and is typically created by sending purchaseorders from the customer's ERP system. SAP SNC would then be configured toautomatically create the work order based on configuration settings. Feedbackfrom the contract manufacturer, captured on the work order, can be fed back intoERP for automatic updates.

The main business value is derived from the fact that the customer has visibilityinto the production activities at the contract manufacturer's location and can seechanges that affect the finished goods shipping date and final quantity early.This helps the customer manage his or her customer's expectations and increasecustomer satisfaction. The customer can also get more up-to-date adjustments toinventory and work-in-progress relating to components being used by the contractmanufacturer.



Figure 18: SAP SNC: Supply Network Inventory

Supply Network Inventory is an outsourced manufacturing business processoffered as part of SAP SNC.

Supply Network Inventory allows for visibility of the inventory, supply anddemand planning situation in a cross-tier environment, including variousindependent business partners such as the customer, component supplier, contractmanufacturer and third-party logistics providers. SNI has a sophisticated visibilityfilter which allows certain partners to only see information for which they havebeen set up. Using SNI capabilities, a customer can view the inventory of acertain product across many locations belonging to different partners in the supplychain network. In all cases the future stock, or projected stock, is calculated anddisplayed along with the planned replenishments (for example, incoming POs)and planned out takes (for example, production orders) with min/max stock limitsand associated alerts. This allows for proactive monitoring of changes in supplyand demand.

The main business value is derived from the fact that the liability on finishedgoods level is managed by monitoring the component inventory situation atcontract manufacturer's locations, allowing for early discovery and action inexception situations.



Figure 19: SAP SNC: Kanban

The Kanban process is a supplier collaboration business process offered as partof SAP SNC.

The Kanban process allows the customer to send out Kanban replenishmentsignals to the supplier using SAP SNC. The Kanban signals are typically generatedas part of the customer's MRP run, or are manually created by the customer. Thesuppliers can view the Kanbans by status, control cycle ID, Kanban ID, or productnumber, and can also print or download. The supplier has access to one screenenvironment for Kanban processing (the dashboard), from which, at time ofshipment, the supplier can create advanced shipping notification (ASN) messagesthat update the customer's ERP system.

The main business value is derived from the fact that the customer cancommunicate Kanban requirements accurately and in real time, replacing oldermethods like phone, fax, and e-mail. The supplier can find his or her requirementsthrough a web browser, and is proactively alerted to exception situations onscreen or via e-mails. The supplier can respond to the requirements quickly andaccurately via ASNs.



Figure 20: SAP SNC: Delivery Control Monitor

The Delivery Control Monitor (DCM) is a supplier collaboration business processoffered as part of SAP SNC.

The DCM enables a shift of net replenishment planning and execution from thecustomer to the supplier. The supplier uses stock balance updates and preset signallevels (reorder points) to understand when replenishment needs to take place. Thereplenishment is based on min/max inventory limits, and the DCM calculates thesuggested replenishment quantities using the maximum level as the upper limit.DCM is a one-screen environment where the supplier user has access to stockon hand, signal levels, min/max limits, and in-transits, as well as the calculatedreplenishment quantities. In addition, alerts are triggered and shown by dedicatedcolors on the screen (representing, for example, a breach of the signal level or theminimum stock level), but the alerts can also be e-mailed to one or many recipients.

From the DCM replenishment screen, the user can select the products thatneed replenishing and, with one click, convert the data into the ASN screenof SAP SNC. The system then pre-fills data such as delivery date and quantity.The ASNs are sent back to the customer's ERP system as an indication of asupplier's commitment to deliver goods. The customer's SAP ERP system sets upa scheduling agreement to act as a blanket order for the ASNs and the physicalgoods receipts.

The main business value is derived from the fact that the customer no longer hasto perform the MRP net planning and replenishment activities for the purchasedcomponents or raw materials, and the supplier can better utilize his or her owncapacity by managing the replenishment process.



Figure 21: SAP Supply Network Collaboration in 2007

SAP SNC 5.1 in 2007

� New name for SAP ICH: SAP Supply Network Collaboration� Part of SAP SCM 5.1 (APO, EM, F&R and SNC) or� SAP SNC 5.1 standalone� Release to customer/ramp-up planned for Q3, 2007� Part of SAP Business Suite

Figure 22: SAP Supply Network Collaboration in 2007



Highlights of additions to SAP SNC 5.1 in 2007

� Invoicing � New Functionality� Replenishment collaboration � Major Enhancements� Work order collaboration � New Business Process� Supply, demand, and inventory monitoring for contract manufacturing �

Major Enhancements� PO worklist for mass maintenance of POs � Major Enhancements� Kanban and release process � Functional Enhancements� SAP Event Manager � Integration scenarios to SAP SNC� PLM cFolders � Contextual integration to SAP SNC

Figure 23: SAP SNC: Work Order Collaboration

SAP SNC: Work order collaboration

� Work order collaboration is a new business process, part of SAP SNC 5.1� Supports key collaboration activities between brand owners and contract

manufacturers� Purchase orders kick off work orders in SNC� Brand owners can track the manufacturing process at the contract

manufacturer� Integration to cost control order in SAP ERP, linked to PO� Changes to components and component use� Production phases/milestones modeled



Figure 24: SAP SNC: Supply Network Inventory

SAP SNC: Supply Network Inventory

� SNI monitor enhanced to support scenarios involving customer, contractmanufacturer, supplier, and 3PL locations/business partners

� Users of different business partners can monitor planning situation at anylocation in the network

� Display of multiple ownership of components at the same location� User-defined alerts based on percentage thresholds of supply and demand

Figure 25: SAP SNC: Replenishment Collaboration

SAP SNC: Replenishment Collaboration

� Technical consolidation of customer (Responsive Replenishment) andsupplier-side replenishment functionality

� Additional replenishment algorithms and automation capabilities� Configurable �Toolbox� monitor� ATP checks added on customer side� Addition of demand forecast collaboration functionality (customer side)� SMI monitor: For simple suppliers without a PO� Min/Max monitor: For sophisticated suppliers with a PO or for customers



Figure 26: SAP SNC: Invoicing

SAP SNC: Invoincing

� Create invoices� Self-billing invoices (evaluated receipt settlement)� Subsequent debit/credit� Payment status� Print and download capabilities� Invoice due list� Complete execution processes, such as PO, release, Kanban, SMI, and DCM� Invoice based on Order or ASN (shipment)

Figure 27: SAP SNC: PO Worklist

SAP SNC: PO worklist

� New screen for PO management� Geared toward use cases with high volume of POs� Created to increase usability and productivity for the supplier� Three main functional lists available (tabs on one screen):

� Confirmation due list (PO items that need to be confirmed)� Publish due list (confirmed PO items that need to be sent back to

customer)� Cancelled POs (PO items that have been deleted or canceled)



SAP SNC: Additional Capabilities

� Change history comparison (on History screens) on order data (PO, release,ASN)

� Notes management improvements (free text) on most objects� Alert monitor and alert notification � Usability enhancements for statistical

view and setup� Archiving for work order object� PLM cFolders integration � Contextual integration SNC to cFolders (for

example, PO item to matching cFolder)� Events Management and SNC integration for initial scenarios on supplier

and customer collaboration sides� Additional alerts out of the box� Additional SAP BI content for work order data

Technology and Implementations

Figure 28: Sample Project Plan



Implementation timelines depend greatly on the scope.

� How many suppliers are part of the go live?� How many processes will be used in SAP SNC?� How many products are part of the go live?� How many of the customer's own plants are part of the go live?� Are there any modifications needed?� Are any supplier back-end system to be integrated?

SAP SNC skills are the most important!

Background skills in Purchasing, and SAP NetWeaver XI are highly recommended.

Supplier training and onboarding must also be planned.

� Online tutorials, documentation, and a call center are typical methods used.

Figure 29: The SAP SCM 5.1 Landscape

SAP SCM 5.1 includes SAP SNC 5.1, SAP EM 5.1, and SAP APO 5.1. SAPERP serves as an execution system by supporting manufacturing, transportation,materials management, and warehouse management.

SAP SNC is included in SAP SCM 5.1 is one system instance.

You can run SAP SNC together with SAP APO and SAP EM as one SAP SCM 5.1system. However, you also have the choice to run it separately or together witheither SAP APO or SAP EM.



Starting with SAP SNC 5.1, SNC is also available as a separate system, alongwith being part of SAP SCM as a whole. The two deployment models are calledthe �standalone� and �server� versions (the latter indicates SNC as part of theoverall SCM system). You can choose how to run your system, depending onorganizational, security, performance, TCO, or administration requirements.

SAP SCM 5.1 is based on SAP NetWeaver technology.

Figure 30: SAP NetWeaver as Technology Base

SAP SNC is based on the SAP NetWeaver technology stack

� User Interface: Web Dynpro web-based UI is new for SAP SNC 5.1 (ABAPversion of Web Dynpro)

� SAP Enterprise Portal is optional with SAP SNC; you can run it by itselfor via SAP EP

� SAP SNC application server: SAP SNC is built into SAP ABAP coding onSAP NetWeaver Application Server

� Message-based integration: SAP SNC relies on SAP NetWeaver XI formessage-based integration using XML messages (SAP B2B certified XMLmessages)

� SAP ERP: Integration provided out-of-the-box via content (mappings) inSAP NetWeaver XI, which translates from ERP IDocs and SAP SNC XMLs.Using of SAP NetWeaver XI also allows for integration to, for example,the supplier's back-end ERP system.

� SAP APO: Integration is provided for certain scenarios (delivery schedulesbased on APO-CMDS), also via SAP NetWeaver XI.



Wrap-Up

Figure 31: Working Together to Achieve Common Goals



Lesson Summary

You should now be able to:� Explain the capabilities of SAP SNC� Discuss the benefits of using SAP SNC� Name the existing SAP SNC processes


SNC100 Lesson: Data Integration and System Landscape Overview

Lesson: Data Integration and System LandscapeOverview

Lesson OverviewIn this lesson, you will learn about data integration in SAP SNC and the requiredsystem landscape.


� Name the two different deployment options for SAP SNC 5.1� Name the involved systems of a simple SNC system landscape

Business Example

TechnologyThere are two deployment options for SAP Supply Network Collaboration (SAPSNC) 5.1:

Within SAP SCM 5.1As part of SAP Supply Chain Management (SAP SCM), together with all theother applications (SAP Advanced Planning & Optimization [SAP APO],SAP EM, and so on)

Standalone as SAP SNC 5.1As a standalone SAP SNC 5.1 option (also including most of the SAP SCMBasis functionality)

The first variant is appropriate when enhanced planning functionality from SAPAPO or other SAP SCM 5.1 capabilities is used � or will be used � on the sameserver. This option should be used if a customer is considering an upgrade fromSAP SCM 5.0 (4.1) to SAP SCM 5.1.

The second variant is interesting for new customers who do not intend to use otherSAP SCM planning capabilities on the same server, but SAP SNC exclusively.They can profit from the lean approach, which has less dependencies on otherrelease cycles and a lower TCO. It is best to install the standalone SAP SNC5.1 system outside the firewall to avoid external access to the internal planningsystem. In addition to SAP SNC 5.1, other add-ons can be installed, such asSAP EM or SAP Extended Warehouse Management (SAP EWM). Currently, anupgrade from SAP SCM 5.0 to SAP SNC 5.1 is not possible, but an upgrade fromSAP SNC 5.1 to SAP SNC 7.0 will later be supported.



A seamless integration with SAP ECC is available for both options.

Caution: You need to consider these deployment options carefully, thereis no way to switch from a standalone option to a full standard SAP SCMserver version. A new implementation would be necessary.

Figure 32: SAP SCM 5.1 Server

Advantages

� It is possible to use other SAP SCM components on the same machine.� Features like production data structures (PDM) and production process

model (PPM) master data can be used for an SNC work order collaborationderived out of SAP APO.

� Upgrade from SAP ICH 5.0 is possible.

Risks

� There is more friction on the system because you need to consider morenotes and support packages.

� A bigger machine might be necessary.� No individual standalone system planning is possible.

Pro and Cons of the SAP SCM 5.1 Server



Business ProcessNaturally, all SNC capabilities in regards to supplier collaboration areincluded in the full SAP SCM server option. In addition, you can leveragesome specific SAP APO capabilities for the work order collaboration processin SAP SNC. There are several ways to set up phases, which are used in thenew work order collaboration process to make production progress visible.Along with maintaining the phases directly in SAP SNC, a customer canchoose to reuse the PDS and PPM structures from SAP APO to representthese phases/components.

SecurityWhen SNC is part of SAP SCM and SAP APO is also used, the SAP SCMsystem is typically installed within the firewall/network of the customer(since APO is mainly a system for internal users). This results in less security,as the SNC system is always accessed by users from an external company.

PerformanceWould require fewer hardware pieces but more hardware capacity becausemore applications (SAP SNC, SAP APO, and SAP EM) are running on onesystem, as opposed to when they run on separate systems.

Implementation Project

� If the implementation of a supplier collaboration process with SAPSNC is an extension of an existing SCM process implemented withSAP APO, the SAP APO implementation must be upgraded to achievethe latest SAP SNC functionality.

� The customer can easily extended the project scope by starting withsupplier collaboration in SAP SCM, and then implementing processesrelated to SAP APO supply chain planning on the same system.

� The customer can decide to leverage things like allocations,deployment, or safety stock planning in supplier collaboration. Thesefunctionalities are currently not included in the standard suppliercollaboration processes, but they could be made available as anextension of supplier-managed inventory (SMI) in a customer project.



Figure 33: Deployment Options for SAP SNC Supplier Collaboration &Outsourced Manufacturing

Figure 34: Standalone Lean

Advantages

� Less support package implication� Lean system� Less hardware requirement� Individual life cycle



Risks

� Cannot switch to a full server deployment� Upgrade from SAP ICH 5.0 to standalone is not possible� Leverage of other SAP SCM components on the same system is not possible� Features such as using PDS and PPM master data for the SAP SNC work

order collaboration process cannot be used

Business ProcessIn general, all business processes and capabilities for supplier collaborationare supported in the SAP SNC standalone option as well. However, thephases used for the work order collaboration process need to be explicitlymaintained within SAP SNC 5.1 .

SecurityThe SNC system can be installed outside the firewall to avoid external accessto internal planning systems. Typically, SAP SNC would be placed in theperimeter network or outside the customer's firewall because outside usersaccess the system, and this adds to the overall IT security.

Performance

� Less master data and fewer transactions may speed up database queriesand performance in general.

� Fewer users may speed up response time.

Implementation Project

� Independent release cycles are possible and no interference withexisting SAP APO implementations.

� The TCO is lower due to less dependence on support packages andhigher system availability, as this application option is smaller andloosely coupled.

� Shorter development cycles are to be expected, which delivers moreavailable functionality in a given time frame.



Figure 35: Supported Deployment Options for SAP SNC 2007 SupplierCollaboration and Outsourced Manufacturing


Note: Collaboration Projects (cProjects) includes cFolders. If you want toleverage the cFolders change management features in combination withSAP SNC, you have to use the Collaboration Projects add-on.




Integration

Figure 38: SAP SNC: Contextual Integration with SAP PLM cFolder



Connects to cFolders from multiple detail views with SAP SNC 5.1:

� Releases/scheduling agreements� Purchase orders� Kanban� Replenishment orders� Advanced shipping notifications� Invoices

Figure 39: PLM cFolders Integration

You can activate a cFolders collaboration in Customizing for Supply NetworkCollaboration by choosing Basic Settings→ cFolders→Activate cFolders andRFC Destination.

You can set up an RFC destination to the cFolders system in Customizing forSupply Network Collaboration by choosing Basic Settings→ cFolders→ SetUp RFC Destination.

You can change the cFolders target URL in Customizing for Supply NetworkCollaboration by choosing Business Add-Ins (BAdIs) for SAP SNC→ BasicSettings→ cFolders→BAdI: Redefine cFolders URL.

You can change the collaboration name used in the cFolders collaboration inCustomizing for Supply Network Collaboration by choosing Business Add-Ins(BAdIs) for SAP SNC→ Basic Settings→ cFolders→ BAdI: Definition of Prefixand Separator for cFolders Used for SAP SNC.



Figure 40: SAP EM and SNC Integration: Architecture

You can use SAP Event Management to monitor processes. This is based onevents that are expected by a specific date/time at the latest in a process. Delaysin the actual events lead to alerts. As of SAP Supply Network Collaboration5.1 and SAP Event Management 5.1, the following new visibility scenarios areavailable for SAP SNC:

� SNC Visibility Process for Incoming Message (Both SC + CC)� SNC Visibility Process for Purchase Order (SC)� SNC Visibility Process for Replenishment Order (CC)

You can connect SAP Event Management to SAP SNC in Customizing for SAPSNC by choosing Integration with SAP Components→ Event ManagementInterface.

You execute the report for determining overdue events in SAP Event Management.The data is copied to SAP SNC. SAP SNC then creates the following new alerttypes for overdue events:

� SNC Visibility Process for Incoming Message

� Overdue incoming message (alert type 7135)� SNC Visibility Process for Purchase Order

� Overdue purchase order confirmation of supplier (alert type 7129)� SNC Visibility Process for Replenishment Order

� Overdue replenishment order confirmation of supplier (alert type 7127)� Overdue replenishment order confirmation of customer (alert type

7128)



Data IntegrationData integration is different for master data and transactional data.

Master data objects are integrated from the ERP system to SAP SNC via theCore Interface (CIF). The Core Interface communicates directly between an SAPERP system and the SAP SNC system.

Transactional data is integrated between the ERP system and SAP SNC by XMLmessages, which are exchanged via SAP NetWeaver Exchange Infrastructure(SAP NetWeaver XI).

Three systems are involved in a simple SNC system landscape:

� ERP system� SAP NetWeaver XI� SAP SNC system



Lesson Summary

You should now be able to:� Name the two different deployment options for SAP SNC 5.1� Name the involved systems of a simple SNC system landscape


Unit Summary SNC100

Unit SummaryYou should now be able to:� Explain the capabilities of SAP SNC� Discuss the benefits of using SAP SNC� Name the existing SAP SNC processes� Name the two different deployment options for SAP SNC 5.1� Name the involved systems of a simple SNC system landscape


Unit 2Purchase Order Collaboration with

SAP SNC

Unit OverviewIn this unit, you will gain deeper insight into the purchase order process withinSAP SNC.


� Explain and understand the purchase order process details in SAP SNC� Differentiate between statuses in the SAP SNC purchase order� Name the purchase order alerts in SAP SNC� Perform your exercise on purchase order processing in SAP SNC� Explain the message flow for the SAP SNC purchase order process� Discuss the monitoring possibilities for the message integration between

the affected systems� Customize the message determination for the SAP SNC purchase order

process� List the Customizing possibilities for the SAP SNC PO process� Discuss the due quantity calculation logic

Unit ContentsLesson: Purchase Order Process Overview ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Lesson: Purchase Order Processing: Process Demo ... . . . . . . . . . . . . . . . . . . . 60Lesson: PO Process � Integration.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Exercise 1: Purchase Order Collaboration with SAP SNC... . . . . . . . . . . 69Exercise 2: PO Worklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Lesson: Relevant Customizing for Purchase Order Processing in SAPSNC.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82


Unit 2: Purchase Order Collaboration with SAP SNC SNC100

Lesson: Purchase Order Process Overview

Lesson OverviewThis lesson will give you an overview of the SAP SNC purchase order process.You will learn about the process steps and the alerts for this process.


� Explain and understand the purchase order process details in SAP SNC� Differentiate between statuses in the SAP SNC purchase order� Name the purchase order alerts in SAP SNC

Business Example

BackgroundYou can use the purchase order collaboration function in SAP Supply NetworkCollaboration (SAP SNC) for the collaborative processing of procurementprocesses with purchase orders. A purchase order is a procurement order that youuse to request that a supplier deliver certain quantities of products at a certain dateand time. The purchase order is, for example, the result of a demand planningprocess that the you perform in your ERP backend system. You send the purchaseorder to SAP SNC to inform the suppliers about demands. In the SAP SNC Webuser interface (UI), the supplier can display the purchase order and react to itaccordingly.

� The supplier can create confirmation schedule lines for a purchase order itemin the purchase order collaboration Web UI to inform the customer aboutthe dates/times on which partial quantities of the product can be delivered.(The request schedule lines remain unchanged). When the supplier publishesa purchase order in SAP SNC, SAP SNC sends the purchase order to thecustomer's backend system. The customer can also see the confirmationschedule lines in the SAP SNC Web UI.

� If the supplier cannot fulfill a purchase order item, he or she can reject theitem. This information is visible to the customer in the Web UI.

� If the supplier sends the delivery to the customer, he or she can create anadvanced shipping notification (ASN) for the purchase order in the Web UI.

The functions in the purchase order collaboration Web UI are especially relevantfor suppliers that do not use a backend system or EDI. Suppliers that use EDI donot have to use the manual functions. Instead, they can send purchase orders with


SNC100 Lesson: Purchase Order Process Overview

confirmation schedule lines and ASNs from their backend system to SAP SNC,which then validates the messages and forwards valid messages to the customer'sbackend system.

Process

Figure 41: PO Process Overview

The Purchase Order Process

1. The customer creates a purchase order in his or her backend system andsends the purchase order as a message to the SAP SNC system.

2. To display the purchase order, the supplier calls purchase order collaborationon the SAP SNC Web UI. The supplier can be informed automatically aboutnewly arrived or changed purchase orders, such as by e-mail or fax, usingpurchase-order-specific alerts and alert notifications. The supplier thereforeonly has to call SAP SNC when he or she needs to respond. The purchaseorder has the distribution status Updated by Customer and the header statusOpen. The item status is also Open.

3. To inform the customer about when the supplier can deliver which quantitiesof the ordered end product, the supplier creates confirmation schedule linesin SAP SNC purchase order collaboration for the items of the purchase order.

The supplier has the following options to create confirmation data in SAPSNC:

� Create the confirmation data manually in the purchase ordercollaboration Web UI.



� Send the confirmation data from the backend system to SAP SNC witha ReplenishmentOrderConfirmation XML message. To generate theReplenishmentOrderConfirmation, the supplier can, for example, createsales order schedule lines in the sales order in his or her backend systemand map this information to a ReplenishmentOrderConfirmation.

Caution: When using Replenishment Order Confirmations,there are no mappings available for the mappingof the supplier's backend system message to theReplenishmentOrderConfirmation XML. You must definethese mappings yourself.

� The supplier cannot change request schedule lines or (for subcontractorders) request component requirements of the purchase order.

� If the supplier cannot fulfill the entire purchase order or an individualpurchase order item, he or she can manually reject the purchase orderor purchase order item in purchase order collaboration. SAP SNCgenerates an alert to inform the customer of the rejection.

4. If the supplier has completed the manual processing of the confirmation datain the purchase order collaboration Web UI and wants to send the purchaseorder with confirmation data to the customer, he or she publishes the purchaseorder. The purchase order acquires the distribution status Published bySupplier. If the supplier generated the confirmation data in his or her backendsystem and sent it to SAP SNC with the ReplenishmentOrderConfirmation,SAP SNC publishes the purchase order automatically.

After publication, the purchase order is no longer changeable in SAP SNC.As a result, the supplier cannot process the purchase order manually inpurchase order collaboration. It is not until after the customer changes thepurchase order in his or her backend system and sends the changed purchaseorder to SAP SNC via ReplenishmentOrderNotification that the purchaseorder can be changed again (distribution status Updated by Customer) andthe supplier can create the relevant confirmation data.

5. SAP SNC sends the published purchase order with the confirmation datato the customer's backend system.

6. If the supplier sends the delivery to the customer, he or she publishes an ASNwith reference to the purchase order items in SAP SNC. The supplier cancreate the ASN manually in SAP SNC or send it from his or her backendsystem to SAP SNC. SAP SNC creates an ASN-confirmed schedule line forthe purchase order and sends the published ASN to the customer's backendsystem.

7. When the customer receives the delivery, he or she sends a goods receiptmessage referring to the ASN from his or her backend system to SAPSNC (ReceivedDeliveryInformation). SAP SNC updates the goods receiptquantity in the ASN and in the ASN-confirmed schedule line of thepurchase order item. SAP SNC updates the goods receipt quantity in the



request schedule line of a purchase order item when the customer sends acorresponding updated purchase order with goods receipt data from his orher backend system to SAP SNC.

Caution: An SAP customer backend system does not send anupdated purchase order to SAP SNC at goods receipt.

SAP SNC also calculates the open quantity of the request schedule linesand of the items. If the backend system has not transferred the DeliveryCompleted indicator for the item and the open quantity of an item is less thanthe underdelivery tolerance, SAP SNC sets the status Delivery Completed forthe purchase order item. Otherwise, it sets the status Partially Delivered.

If all items have the status Delivery Completed, SAP SNC sets the headerstatus of the purchase order to Delivery Completed.

DefinitionA purchase order is a procurement order that a customer uses to request that asupplier deliver certain quantities of products at certain dates and times.

In SAP Supply Network Collaboration (SAP SNC) purchase order collaboration,the customer backend system sends the purchase order to SAP SNC with an XMLmessage.

StructureIn SAP SNC, a purchase order has a three-level structure:

Purchase order headerThe purchase order header contains data that affects the entire purchase order.This includes data about the customer, the supplier, and different purchaseorder statuses. A purchase order includes one or more purchase order items.

Purchase order itemA purchase order item contains the product ordered by the customer. SAPSNC contains various data for the purchase order item. Among it thelocation at which you ant to receive the product. This ship-to location can bedifferent from the customer location that commissioned the purchase order.A purchase order item contains purchase order schedule lines.



Purchase order schedule lineA purchase order schedule line determines the quantities and the dates/timeson which the supplier should or can deliver them. Purchase order schedulelines can of the following types:

� A Request schedule line defines the quantity of the product that isexpected at a certain date and time. For one purchase order item, therecan be several request schedule lines with various dates, times, andquantities. The request schedule lines are defined by the customer.

A request schedule line contains the goods receipt quantity, the openquantity, and the requested quantity. The goods receipt quantity is thequantity that the customer has already received. The customer transfersthe goods receipt in the purchase order schedule line to SAP SNC. Theopen quantity is the quantity that the supplier has not yet delivered;SAP SNC determines this quantity automatically.

� The supplier creates a Confirmed schedule line for an item in SAP SNCpurchase collaboration either manually or by sending a purchase orderwith confirmation data from his or her backend system to SAP SNC.A confirmation schedule line determines the quantity of the productthat the supplier can deliver at certain date and time. The suppliercan create one or more confirmation schedule lines for an item. Theconfirmation schedule lines can differ in terms of number, quantities,and dates/times of the request schedule lines. In standard confirmationprocessing, a confirmation schedule line refers to the item, not to aspecific request schedule line.

The supplier can only create confirmation data for an item ifconfirmation control permits it.

� SAP SNC automatically creates an ASN-confirmed schedule line for apurchase order if the supplier publishes an ASN for the purchase orderitem in SAP SNC. Schedule lines of this type also refer to the item, notto specific request schedule lines.

Note: A product master must be available in SAP SNC for all productsand components in a purchase order.

Purchase Order StatusSAP SNC sets the status of a purchase order or a purchase order item automatically,depending on the function you or SAP SNC performed on the purchase order.

Status at Header Level



At header level, you can see the distribution status and the header status.The distribution status is a message-related status. It provides informationabout which processes have been performed on or are possible for anXML message for a purchase order (ReplenishmentOrderNotification andReplenishmentOrderConfirmation).

Distribution StatusValue DescriptionPublished by Supplier The supplier has closed the purchase order in SAP

SNC.The supplier can no longer change the purchaseorder.

Updated by Customer A purchase order acquires this status in thefollowing cases:

� The customer created a purchase order in his orher backend system and sent it to SAP SNC bymeans of a ReplenishmentOrderNotification.

� The customer changed a purchase order� already sent to SAP SNC � in his orher backend system, and sent the changedpurchase order to SAP SNC using aReplenishmentOrderNotification.

The supplier can process the purchase order.Updated by Supplier The supplier did not create confirmations

manually in SAP SNC, but instead sent themfrom his or her backend system to SAP SNCusing a ReplenishmentOrderConfirmation.However, SAP SNC has not yet forwarded theReplenishmentOrderConfirmation to the customerbackend system and thus receives the Published bySupplier status.

The header status displays which editing processes have been performed onthe purchase order. The header status is an �aggregated� status that SAP SNCdetermines from the status of the purchase order items. For more information,see the section on item status.

Item Status

The item status shows which editing processes have been performed on thepurchase order item. The following table contains the possible values for theitem status.



Item StatusValue DescriptionOpen After the customer sent the purchase order from his or

her backend system to SAP SNC, the purchase itemdid not undergo any further processing steps (such asa goods receipt or a cancellation in purchase ordercollaboration).

Partially Delivered The supplier delivered part of the ordered quantity.Delivery Completed The supplier delivered the ordered quantity as part of

the underdelivery tolerance.Rejected The supplier rejected the purchase order item.Canceled The customer deleted the item from his or her SAP

backend system.Closed The customer has closed the purchase order item in the

SCM system using report /SCA/PO_SET_CLOSED.The item cannot be changed.

Locked The customer locked the item in his or her backendsystem.

Confirmation Status

The confirmation status indicates whether confirmations already exist for an item.The confirmation status is relevant if confirmations are mandatory or optional foran item according to confirmation control.

Confirmation StatusValue DescriptionNot confirmed The supplier has not yet created any confirmations for

the item.Partially Confirmed So far, the supplier has only confirmed a partial quantity

for the item.Confirmed As part of the underdelivery tolerance, the supplier

confirmed the full item quantity.

Change Status

The change status indicates whether an item is new or changed.

Status in the Approval Process



If you use the approval process in purchase order collaboration, the followingadditional statuses are also relevant:

� Approval status� Change distribution status

PO ConfirmationA supplier can manually create, change, or delete confirmation schedule lines withthe Confirmed schedule line type for a purchase order item in the purchase orderdetails in SAP Supply Network Collaboration (SAP SNC).

Confirmation means there is a possibility to change date and/or quantity fields.

To be able to create a Confirmed confirmation schedule line for an item in thestandard system, the item must fulfill the following conditions:

� Confirmation control in SAP SNC permits confirmations for the item.� The item is changeable.

In the standard system, an item is changeable in the SAP SNC Web UI if thepurchase order and item have the following statuses:

� The purchase order has the status Updated by Customer .� The item status is Open or Partially Delivered.� The item does not have the distribution status for changes Published

by Supplier. This status is relevant if the customer uses the approvalprocess.

The settings for status-dependent changeability are defined in Customizingfor Supply Network Collaboration. ChooseBasic Settings→ Changeabilityof Purchase and Replenishment Order Items→ Create Change Profiles forPurchase Order Itms and Replenishment Order Items.

The settings are irrelevant if the supplier sends the confirmations by EDIfrom his or her backend system to SAP SNC. If you want to ensure thatthe supplier does not send confirmations from his or her backend system,deactivate the POCONF_CONF_ALLOWED validation check.

� The item is not a statistical item.

Adding new schedule lines (splitting) is also possible as part of the confirmation.

If the supplier has completed manual processing of the confirmation data in thepurchase order collaboration Web UI and wants to send the purchase order withconfirmation data to the customer, he or she publishes the purchase order. Thepurchase order acquires the distribution status Published by Supplier.

After publication, the purchase order is at first no longer changeable in SAPSNC. As a result, the supplier cannot process the purchase order in purchaseorder collaboration manually. It is not until the customer changes the purchase



order in his or her backend system and sends the changed purchase order to SAPSNC via ReplenishmentOrderNotification that the purchase order can be changedagain (distribution status Updated by Customer) and the supplier can create therelevant confirmation data.

Caution: PO confirmations are only visible in the customer ERP systemafter the supplier has published the purchase order.

Purchase Order AlertsThe following options are available when you generate a purchase order alert,depending on the alert type:

� The Post Processing Framework (PPF) generates the alert. Systemadministration can deactivate alert generation in the PPF.

� System administration executes a report regularly in the SAP SNCsystem. To call the report for online processing, choose Supply NetworkCollaboration→ Exceptions→ Alert Generation→ <Report> from theSAP Easy Access menu.

� SAP SNC generates the alert during validation of the purchase order. Systemadministration can deactivate alert generation in Customizing for Validation.

The following list contains the alert types for purchase order collaboration.

Exception during validation of purchase order (Alert ID 7035)SAP SNC detected a problem during validation. This alert is a generalvalidation alert. Some validations generate more specific alerts (see below).This alert is of special interest for monitoring errors in the XML inboundprocessing for purchase orders and purchase order changes.

New purchase order item (Alert ID 7051)The customer sent a purchase order, containing a new purchase order item,to SAP SNC from his or her backend system. This alert is generated by thePO_NEW_CHG_ALERT_CTRL validation check. The validation check isactive in the standard system.This alert is generated by the Validation Framework.

Changed purchase order item (Alert ID 7052)The customer changed a purchase order item in his or her backend systemand sent the modified purchase order to SAP SNC.The alert text indicates what has changed (for example, the quantity or thedate/time).This alert is generated by the PO_NEW_CHG_ALERT_CTRL validationcheck. The validation check is active in the standard system.



Partially confirmed purchase order item (Alert ID 7053)The entire confirmed quantity of the item is the sum of the confirmedquantities from the confirmation schedule lines of the confirmed scheduleline type. The total request quantity of the item is the sum of the requestquantities from the request schedule lines.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_ORDER, action /SCA/BOL_ORD_INCOMPLCONF_ALERT).

Overdelivery tolerance exceeded (Alert ID 7038)The total confirmed quantity of the purchase order item is greater than thetotal request quantity of the purchase order item, plus the overdeliverytolerance.The entire confirmed quantity of the item is the sum of the confirmedquantities from the confirmation schedule lines of the confirmed scheduleline type. The total request quantity of the item is the sum of the requestquantities from the request schedule lines.This alert is generated by the PO_ITMOVERDELIVERY andPO_ITMOVERDELIVERY_WITHOUTZERO validation checks.In the standard system, SAP SNC does not generate alerts. ThePO_ITMOVERDELIVERY validation check is active, but alert generationhas been deactivated. The PO_ITMOVERDELIVERY_WITHOUTZEROvalidation check is not active in the standard system.If unlimited overdelivery is defined for the purchase order item, the systemdoes not generate this alert.

Underdelivery tolerance not reached (Alert ID 7039)The total confirmed quantity of the purchase order item is less than thetotal request quantity of the purchase order item minus the underdeliverytolerance.The entire confirmed quantity of the item is the sum of the confirmedquantities from the confirmation schedule lines of the Confirmed scheduleline type. The total request quantity of the item is the sum of the requestquantities from the request schedule lines.This alert is generated by the PO_ITMUNDERDELIVERY andPO_ITMUNDERDELIVERY_WITHOUTZERO validation checks.In the standard system, SAP SNC does not generate alerts. ThePO_ITMOVERDELIVERY validation check is active, but alert generationhas been deactivated. The PO_ITMUNDERDELIVERY_WITHOUTZEROvalidation check is not active in the standard system.

Late confirmation of purchase order item (Alert ID 7054)The confirmed delivery date of at least one confirmation schedule lines liesafter the customer's request delivery date.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_ORDER, action /SCA/BOL_ORD_INCOMPLCONF_ALERT).



Manual approval of confirmation required (Alert ID 7055)This alert is relevant for purchase order collaboration with the approvalprocess. The customer must approve the confirmation schedule linemanually on the purchase order collaboration Web UI.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_ORDER, action /SCA/BOL_ORD_APPROVAL_ALERT).

Confirmation rejected (Alert ID 7057)This alert is relevant for purchase order collaboration with the approvalprocess. The customer rejected the confirmation schedule line manually onthe purchase order collaboration Web UI.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_ORDER, action /SCA/BOL_ORD_APPROVALREJ_ALERT).

Purchase order rejected (Alert ID 7036)The supplier manually rejected the purchase order in the purchase ordercollaboration Web UI.This alert is generated by the PPF (action profile /SCA/BOL_ORDER,action /SCA/BOL_ORD_REJECTED_ALERT).

Purchase order item rejected (Alert ID 7037)The supplier manually rejected the purchase order item in the purchase ordercollaboration Web UI.This alert is generated by the PPF (action profile /SCA/BOL_ORDER,action /SCA/BOL_ORD_REJECTED_ALERT).

New note for purchase order (Alert ID 7059)The customer or supplier has created a new note for a purchase order or apurchase order confirmation in purchase order collaboration.This alert is generated by the PPF (application /SCA/ICH_NOTES,action profile /SCA/BOL_ORDER_NOTES, action /SCA/BOL_OR-DER_NEW_NOTES).

Purchase order overdue (Alert ID 7103)The purchase order contains due schedule lines with an ASN-based duequantity in the past. The schedule lines, therefore, are not fully covered byASNs.The system administrator generates these alerts with the GenerateAlerts for Due/Overdue Purchase Orders and SA Releases report(/SCA/DUELISTALERTWRITE).



Purchase order due within lead time (Alert ID 7104)The release/purchase order contains schedule lines in the future that liewithin the lead time and are not fully covered by ASNs.The system administrator generates these alerts with the GenerateAlerts for Due/Overdue Purchase Orders and SA Releases report(/SCA/DUELISTALERTWRITE).

Purchase Order WorklistThe purchase order worklist allows you to process confirmations more quickly.The supplier immediately sees purchase order schedule lines with unconfirmedquantities in the purchase order worklist, and can create and publish confirmations.In the customer view of the purchase order worklist, the customer sees a list ofpurchase order items that the supplier has rejected.

The purchase order worklist includes the following lists (queries), in whichpurchase order data is grouped according to different criteria:

To Be ConfirmedThis list displays request schedule lines whose requested quantity is not yetcompletely covered by confirmation schedule lines. The quantity that is stillto be confirmed is displayed in the Confirmation-Based Due Quantity field.In this list, the supplier can create confirmation schedule lines for severalrequest schedule lines simultaneously. If the supplier wants to confirm adeviating quantity, he or she enters the confirmed quantity directly in therequest schedule line row. If the supplier wants to confirm the requestquantity, he or she sets the Confirm Complete Quantity indicator. If required,the supplier also changes the delivery date/time date or shipment date/timedirectly in the row. The supplier then chooses Confirm. For the requestschedule lines, the system creates confirmation schedule lines in which thesupplier has entered a quantity or has set the Confirm Complete Quantityindicator.

To Be PublishedThis list displays purchase orders with purchase order items for which thesupplier has created new confirmation schedule lines. The supplier has notyet published the purchase orders. The supplier can select one or morepurchase orders and publish them by choosing Publish.

Canceled/Blocked ItemsThis list displays purchase order items that the customer has blocked orcanceled.

Rejected ItemsThis list is only relevant for the customer view. It shows, for example, thepurchase order items that the supplier has rejected.



The lists are based on SAP-defined queries. If required, you can also create yourown queries and, thus, your own lists based on the purchase order data, such as alist containing items that are partially delivered or completely delivered.



Lesson Summary

You should now be able to:� Explain and understand the purchase order process details in SAP SNC� Differentiate between statuses in the SAP SNC purchase order� Name the purchase order alerts in SAP SNC



Lesson: Purchase Order Processing: Process Demo

Lesson OverviewThis is your chance to see what has been discussed and to view a systemdemonstration.


� Perform your exercise on purchase order processing in SAP SNC

Business Example

Figure 42: Demo Purchase Order


SNC100 Lesson: Purchase Order Processing: Process Demo

Lesson Summary

You should now be able to:� Perform your exercise on purchase order processing in SAP SNC



Lesson: PO Process � Integration

Lesson OverviewThis lesson will give you insight into the message integration in the SAP SNCPurchase Order Collaboration Process.


� Explain the message flow for the SAP SNC purchase order process� Discuss the monitoring possibilities for the message integration between


process

Business Example

Message IntegrationMessages are exchanged between an SAP ERP system and SAP SNC via theSAP NetWeaver Exchange Infrastructure (SAP NetWeaver 2004 XI). IDocs areused for data transfer between SAP ERP and SAP NetWeaver XI. Within SAPNetWeaver XI, these IDocs are converted into XML messages. These XMLmessages are then transferred to SAP SNC. The communication of the responsemessage from SAP SNC is vice versa.

IDocs Used in the SAP SNC PO ProcessPO transactional data is transferred to SAP SNC by one of the following IDoctypes:

� ORDERS.ORDERS05� ORDCHG.ORDERS05� PORDCR1.PORDCR102 (only SAP ECC 6.0 or higher)

PO confirmation is received from SNC by one of the following IDoc types:

� ORDCHG.ORDERS05� PORDCH.PORDCH02 (only SAP ECC 6.0 or higher)


SNC100 Lesson: PO Process � Integration

Message Conversion in SAP NetWeaver XISAP SNC uses XML messages for the exchange of transactional data, whilean SAP ERP system uses IDocs. SAP NetWeaver XI is used to convert IDocmessages into XML messages, and vice versa.

Message mapping for the standard SNC scenarios is provided by SAP.

Hint: You can find the XI content for SAP SNC in theIntegration Repository in the SNC software component in the .http://sap.com/xi/SNC/Global namespace.

Figure 43: Example of a PORDCR102 IDoc

Figure 44: Example of an XML Message



Inbound Processing of XML Messages in SAP SNCDetermining the Process Type for the XML Message

For each XML message, SAP SNC determines the corresponding processtype that you defined in Customizing for Supply Network CollaborationBasic Settings→ Processing Inbound and Outbound Message→ ProcessTypes for Inbound Messages. Depending on the process type and the type ofXML message, SAP SNC performs validation checks for an XML message.

Hint: For more information, see the Implementation Guide (IMG)for SAP Supply Network Collaboration.

Checks in Inbound Message Processing and Master Data CompletionSAP SNC checks all inbound XML messages for consistency andcompleteness. These checks run automatically.SAP SNC can fill in some master data if it is missing in inbound XMLmessages. This function allows SAP SAP SNC to automatically completemissing master data in inbound XML messages. You can configure masterdata completion for locations. In Customizing, you specify how SAP SNCdetermines locations from business partner data. To do this, you can createa master data completion profile for every inbound message interfaceand every process type by providing data for the master data completionprocess. You can also maintain the settings for recipient and sender, ona partner-dependent basis.

Validation ChecksWithin validation, SAP SNC performs various validation checks on abusiness object. For example, the validation check checks:

� Does the business object contain all required data?� Is the master data referenced in the business object valid; in other

words, is it created in SAP SNC?� Is the data consistent?If a validation check determines that a business object does not have theproperty that is being checked, SAP SNC can respond with a check-specificalert and an entry in the application log. Depending on the severity of anerror, SAP SNC even terminates validation and rejects the business object (itdoes not save the business object).



Alert GenerationDepending on the results of the validation checks, SAP SNC either savesthe data in application tables or rejects it. If the system generates errormessages of type A (Abort) or E (Error) during the validation checks, thesystem creates error messages or alerts in the application log, dependingon the Customizing settings.

Hint: You can restrict logging in the application log in Customizingby choosing Supply Network Collaboration→ Basic Settings→Processing Inbound and Outbound Messages→ Restrict Log.You can limit alerts in Customizing by choosing Supply NetworkCollaboration→ Basic Settings→ Processing Inbound andOutbound Messages→ Restrict Alerts.

Posting Data on the DatabaseThe system posts data without error messages in the following componentsin the database:

� Time series: Time series data management (TSDM)� Order documents: Order document management (ODM)� Stock data: Logistics Inventory Management Engine (LIME)

Monitoring TransactionsYou can use the following transactions for monitoring:

� WE02 / WE05 (IDoc monitor in SAP ERP)� SM58 (SAP ERP)� SXI_MONITOR (SAP NetWeaver XI and SAP SNC)

Message Determination in SAP ERPIDoc and XML Messages are used for communication between SAP ERP andSAP SNC.

To create an IDoc message from a purchase order, you need to maintain themessage determination. From the SAP Easy Access menu, choose Logistics→Materials Management→ Purchasing→ Master Data→ Messages→ PurchaseOrder→ Create. In this transaction you are asked for an output type. The settingsfor message determination vary from implementation to implementation. For thiscourse we have set up our own output type: BAPI.

Hint: Output types are defined in customizing. Choose IMG→MaterialsManagement→ Purchasing→ Messages→ Output Control→ MessageTypes→ Define Message Types for Purchase Order.



After selecting the output type you are asked for a key combination. For thiscourse, we set up message determination for the key combination Document Typebecause we do have also our own unique document type for SNC purchase orders(PO doc type ZS). The entry we maintained looks like this:

Condition RecordsDoc Name Funct Partner Medium Date /

TimeLanguage

ZS SNC PO LS sidCLNTxxx 8 4 EN

From the table you can see that the system is set to create a message whenever thePO document type is ZS. By selecting an other key combination, you could createa message based on the supplier and or purchase Ooganization.

We have selected logical system as partner. You could also use the vendor aspartner. However you decide the corresponding entry need to exist in the partnerprofiles (Transaction WE20).

�Medium 8� represents a special function, and �Date / Time 4� stands for Sendimmediately (when saving the application). You can also select other options fordate / time based on your business requirements.

Partner ProfilesA partner profile controls which IDocs are created. You maintain partner profilesin transaction WE20; choose Tools→ ALE→ ALE Administration→ RuntimeSettings→ Partner Profiles.

Corresponding to the above entries in Message Determination, entries are requiredfor LS sidCLNTxxx and message type ORDERS and ORDCHG.

Hint: You can check your settings by creating a new PO. Instead of savingthe PO, choose the Message button in the PO Create screen. If all yoursettings were made correctly, you will see an entry for your output type.

OutputType

Medium Function Partner Language

ZSNC 6 EDI LS sidCLNTxxx EN

If you cannot find an entry you might find the reason by evaluating theDetermination Analysis using the button.



Using the XML MonitorTo monitor incoming and outgoing XML messages, you can use transactionSXI_MONITOR (choose Supply Network Collaboration→ Tools→ IntegrationEngine, then choose Monitor for Processed XML Messages).

The monitor for processed XML messages shows following status:

Figure 45: Message Status

In addition, a message shows one of the following acknowledgement statuses.



Figure 46: Acknowledgement Status

You can navigate to the message details by selecting a message and choosingDetails. Here you can review the content of the XML message. Drill down bychoosingInbound Message→ Payload and double-click on MainDocument. Youwill then see the XML message in one of the two windows on the right.

Figure 47: An XML Message in SXI_MONITOR



Exercise 1: Purchase Order Collaborationwith SAP SNC

Exercise ObjectivesAfter completing this exercise, you will be able to:� Run a purchase order collaboration scenario with SAP SNC

Business ExampleYour company collaborates with some suppliers via SAP SNC. You, as apurchaser, issue purchase orders to a supplier who participates in the collaborationwith SAP SNC. You expect the supplier to review and confirm the PO within SAPSNC. The confirmation then is sent back to your SAP ERP system.

Task 1: Create a purchase order in SAP ERPNote: This task is performed in the role of the customer. So you needto logon to the ERP System with the user representing the customer(SNC100-##).

Create a new purchase order to be sent to SAP SNC.

1. Navigate to the Create Purchase Order transaction.

2. Create a purchase order of type SNC PO for vendor SNC100A-##. Theorder is for 100 pc of material T-C100-## and should be delivered in twoweeks to your plant 1000 in storage location 0001.

The tax code for this order is 19% domestic input tax (VA). Purchaseorganization and company code are 1000. Your purchasing group is S##.

3. Save the purchase order.

4. Write down the PO number. _____________

Task 2: Check for purchase order in SAP SNCLog on to the SAP SNC Web UI and review the PO (in the role of the supplier).

1. Log on to the SCM System with user IU-SUPA## and password welcomeand then connect to the SNC Supplier view.

A browser window will open and show the SNC Web UI.

2. Navigate to the new purchase order using the Alert Overview or the PurchaseOrder Overview.

Continued on next page



3. Have a close look on the PO in SAP SNC and check all the informationshown in the PO. Just like in SAP ERP, the SNC PO is a three-levelpurchasing document (Header, Item, Schedule Line).

Task 3: Confirm PO from the PO Details screenNow confirm that you can deliver on time but not the full quantity. You canconfirm at either item or schedule line level.

How does the system react to the underconfirmation?

1. Try confirming a quantity lower than the requested quantity.

2. Save and publish the purchase order.

Hint: If the system does not allow the publication of the crderConfirmation because the underdelivery tolerance is violated, simplychange the quantity, for example, to 99 or 100.

3. Check that the confirmation has been sent back to the ERP system and thepurchase order is updated.

Note: This is again a task that will be performed in the role of thecustomer using the ERP System and the user SNC100-##.

4. OPTIONAL: Check the message flow



Solution 1: Purchase Order Collaborationwith SAP SNCTask 1: Create a purchase order in SAP ERP

Note: This task is performed in the role of the customer. So you needto logon to the ERP System with the user representing the customer(SNC100-##).

Create a new purchase order to be sent to SAP SNC.

1. Navigate to the Create Purchase Order transaction.

a) Use transaction code ME21N or choose Logistics→ MaterialsManagement → Purchasing → Purchase Order → Create →Vendor/Supplying Plant Known.

2. Create a purchase order of type SNC PO for vendor SNC100A-##. Theorder is for 100 pc of material T-C100-## and should be delivered in twoweeks to your plant 1000 in storage location 0001.




The tax code for this order is 19% domestic input tax (VA). Purchaseorganization and company code are 1000. Your purchasing group is S##.

a) Select SNC PO from the document type dropdown list in the headersection.

Hint: It is important to select the correct document type.Otherwise no message will be sent to SAP SNC.

b) Enter SNC100A-## as vendor.

c) Use the afterwards values to create your purchase order.

HeaderOrganizational Data Purch. Org. 1000

Purch. Group S##

Company Code 1000

ItemMaterial T-C100-##

PO Quantity 100

Delivery date today + 2weeks

Plant 1000

Storage Location 0001

Item DataInvoice tab Tax Code VA

3. Save the purchase order.

a) Choose Save to save the new purchase order.


a) Write down the number of the purchase order, which is displayed in thebottom line on the screen.

Task 2: Check for purchase order in SAP SNCLog on to the SAP SNC Web UI and review the PO (in the role of the supplier).

1. Log on to the SCM System with user IU-SUPA## and password welcomeand then connect to the SNC Supplier view.




A browser window will open and show the SNC Web UI.

a) After logging on to the SCM System you will see a user menucontaining only one transaction - SNC Supplier View.

Call transaction SNC Supplier View.

Alternatively you can use transaction /N/SCA/ICH_S or choose SupplyNetwork Collaboration→ Web UIs for SAP SNC→ Special Views→Supplier Collaboration→ SNC - Supplier View.

2. Navigate to the new purchase order using the Alert Overview or the PurchaseOrder Overview.

a) Choose GO in the Alert Monitor.

Hint: For a better overview you might close the selectionelement by choosing Close Selection.

You can now select the alert for your newly created PO by clickingon the number of alerts in the PO New Item line. Afterward, selectthe alert concerning your new PO and choose See Details to navigateto the PO details.

b) Alternately, you can choose Purchase Order→ Purchase OrderOverview from the navigation bar.

After the PO Overview screen has appeared, choose Go, select yourPO, and then choose Details.

3. Have a close look on the PO in SAP SNC and check all the informationshown in the PO. Just like in SAP ERP, the SNC PO is a three-levelpurchasing document (Header, Item, Schedule Line).

a) Check if the data shown in the PO correspond to the data that youentered in the ERP system.




Task 3: Confirm PO from the PO Details screenNow confirm that you can deliver on time but not the full quantity. You canconfirm at either item or schedule line level.

How does the system react to the underconfirmation?

1. Try confirming a quantity lower than the requested quantity.

a) Select the item you want to confirm and choose Confirm Items.

b) Alternately, you could also select the schedule line and press theConfirm Schedule Lines button.

c) You will see that on the schedule line tab a new line is added for theconfirmation. Choose Change Item Area and change the quantity in theconfirmation schedule line to 80.

To complete the confirmation, choose Ok.

d) Press the Check PO button.

The system issues a warning message: Underconfirmation(confirmed quantity too small). The reason for this is anactive validation check that issues a warning message if the confirmedquantity is too small.

Hint: This system behavior can be customized. In the standardsystem, only a warning message is issued upon saving, but anerror message appears when you try to publish the PO.

You can find the Customizing for the validation checks in theImplementation Guide under Supply Network Collaboration→ Basic Settings→ Validation→ SAP Standard Settings/ Own Settings.

The accepted tolerances are maintained in the externalprocurement relationship in SCM, and these are transferredfrom the purchasing info record in ERP.




2. Save and publish the purchase order.

Hint: If the system does not allow the publication of the crderConfirmation because the underdelivery tolerance is violated, simplychange the quantity, for example, to 99 or 100.

a) Use the Publish button to save and publish the purchase orderconfirmation.

Confirm the dialog box.

Hint: If you choose Save ,the purchase order is saved as a draft,but no confirmation is sent to the ERP system. Choose Publishto publish the purchase order (Publish = Save and Publish).

b) If the system does not allow the confirmation of 80 pc you can eitherchange the quantity or add a second confirmation with 20 pc for alater date. Therefore either use the Change Item Area button (changequantity) or the Confirm Items / Confirm Schedule Line button (adda second confirmation).

Hint: Do not forget to publish the PO.

3. Check that the confirmation has been sent back to the ERP system and thepurchase order is updated.

Note: This is again a task that will be performed in the role of thecustomer using the ERP System and the user SNC100-##.

a) Call transaction Display Purchase Order.

Use transaction ME23N or choose Logistics→ Materials Management→ Purchasing→ Purchase Order→ Display.

b) Choose Document Overview On. In the Document Overview area onthe left of the screen, choose My Purchase Orders from the dropdownmenu.

The purchase order you created earlier is listed. Double-click on thepurchase order to display the details. In the item data area, select thetab page Confirmations. You can see a confirmation of the type AB �Order Acknowledgement.




4. OPTIONAL: Check the message flow

a) In the SAP SNC system you can check in transaction SXI_MONITORthat a message of the type ReplenishmentOrderConfirmation_Out issent to the ERP system.

b) In the SAP ERP system, you can check the inbound and outboundIDocs with transaction WE02.



Exercise 2: PO Worklist

Exercise ObjectivesAfter completing this exercise, you will be able to:� Confirm an SAP SNC purchase order using the PO worklist

Business Example

Task 1: Confirm and publish a POInstead of confirming the PO from the PO confirmation screen, you can use the POworklist to identify POs that have to be confirmed and process them more quickly.

1. Create another purchase order in SAP ERP (User SNC100-##).


3. In SAP SNC, navigate to the PO Worklist and execute the to be confirmedquery.

Note: This step is again performed in the role of the supplierIU-SUPA##

4. Confirm your PO and publish the PO confirmation to SAP ERP.

Task 2: Create a new queryYou can also create your own queries based on the purchase order data, such as alist containing items that are partially delivered or completely delivered.

Create your own query to show all confirmed POs.

1. Create your own query for confirmed POs.

2. Set your new query as the default query and change the layout of thePurchase Order Worklist screen so that each query appears on its own tabpage.



Solution 2: PO WorklistTask 1: Confirm and publish a POInstead of confirming the PO from the PO confirmation screen, you can use the POworklist to identify POs that have to be confirmed and process them more quickly.

1. Create another purchase order in SAP ERP (User SNC100-##).

a) Use transaction code ME21N or choose Logistics→ MaterialsManagement→ Purchasing → Purchase Order → Create →Vendor/Supplying Plant Known.

b) Select SNC PO from the document type dropdown list in the headersection.

Hint: It is important to select the correct document type.Otherwise no message will be sent to SAP SNC.

c) Enter SNC100A-## as vendor.

d) Use the values in the table below to create your purchase order.

HeaderOrganizational Data Purch. Org. 1000

Purch. Group S##

Company Code 1000

ItemMaterial T-C100-##

PO Quantity 100

Delivery date today + 2weeks

Plant 1000

Storage Location 0001

Item DataInvoice Tab Tax Code VA

e) Choose Save to save the new purchase order.


a) Write down the number of the purchase order, which is displayed in thebottom line of the screen.




3. In SAP SNC, navigate to the PO Worklist and execute the to be confirmedquery.

Note: This step is again performed in the role of the supplierIU-SUPA##

a) In SNC, choose Purchase Order→ Purchase Order Worklist fromthe menu.

b) You can see there are three active lists, or queries. The standardqueries are To Be Confirmed, To Be Published, and Cancelled/BlockedItems. For this example, choose the query To Be Confirmed and chooseRefresh if required (at the bottom right of the screen).

4. Confirm your PO and publish the PO confirmation to SAP ERP.

a) Your purchase order is displayed. Enter either the quantity to beconfirmed or set the Confirm Complete Quantity (CCQ) indicator andchoose Confirm.

If you confirm a partial quantity, a line is created for the quantity still tobe confirmed.

b) Publish the PO using the To Be Published query.

Choose To Be Published. Select your purchase order and choosePublish.

Task 2: Create a new queryYou can also create your own queries based on the purchase order data, such as alist containing items that are partially delivered or completely delivered.

Create your own query to show all confirmed POs.

1. Create your own query for confirmed POs.

a) On the Purchase Order Worklist screen, choose Define New Query.

b) Select the object type Purchase order items (supplier) and choose Next.

c) Enter the criteria by which you want to select the purchase orders. Forexample, select the confirmation status CF. Chose Next.

d) Enter a query description, for example, Confirmed POs, and ensurethat the Activate Query indicator is set. Choose Finish.




2. Set your new query as the default query and change the layout of thePurchase Order Worklist screen so that each query appears on its own tabpage.

a) On the Purchase Order Worklist screen, choose Personalize. Set thedefault query indicator for your new query. On the Layout tab page,select the Tab Strip indicator and choose Apply.

Your new query now appears as the first query and each query is on aseparate tab page.



Lesson Summary

You should now be able to:� Explain the message flow for the SAP SNC purchase order process� Discuss the monitoring possibilities for the message integration between


process



Lesson: Relevant Customizing for Purchase OrderProcessing in SAP SNC

Lesson OverviewIn this lesson, you will learn about the relevant customizing in SAP SNC and thelogic for due quantity calculation in SAP SNC.


� List the Customizing possibilities for the SAP SNC PO process� Discuss the due quantity calculation logic

Business Example

Changeability of Purchase OrdersYou can control if a supplier is allowed to change a PO item or not. One typeof change is confirming the PO. You define the changeability of a PO basedon the order type and on thestatus on item level (distribution status, changedistribution status, and item status). You then group these settings into a changeprofile. Change profiles are defined and assigned in the IMG by choosing IMG→Supply Network Collaboration→ Basic Settings→ Changeability of Purchaseand Replenishment Order Item.

Say, for example, you do not want your supplier to change POs which he or shehas already confirmed and published. You want to prevent the supplier fromchanging his or her confirmation shortly before the published delivery date.

Approval ProfilesWhen the supplier publishes a purchase order with his or her confirmation datain SAP Supply Network Collaboration (SAP SNC), SAP SNC automaticallydetermines whether there are deviations between the confirmation data and therequest data. There are two different procedures to determine the deviationsand set the approval status. Depending on the procedure, the system approvesdeviating data or sets the status Manual Approval Required.

Approval profiles are defined and assigned in the IMG by choosing IMG→Supply Network Collaboration→ Purchase Order→ Approval Process→ CreateApproval Profiles and IMG→ Supply Network Collaboration→ Purchase Order→ Approval Process→ Assign Approval Profiles.


SNC100 Lesson: Relevant Customizing for Purchase Order Processing in SAP SNC

Approval process without tolerances

You can choose from the following procedures for the automatic approval process:

� Here, the system does not consider any tolerances for quantity or date/timedeviations. If the confirmation data does not deviate from the request data,the system sets the approval status Approved. You can configure how thesystem will react to deviations in data. Depending on these settings, thesystem sets the approval status Approved orManual Approval Required. Youcan make the settings dependent on customer, supplier, and product.

� Approval process with consensus finding

Here, the system uses the deviation analysis of consensus finding and thecondition technique. The system can consider tolerances for quantity anddate/time deviations as follows:

� Quantity tolerances

The system uses the underdelivery tolerance and the overdeliverytolerance from the purchase order item. For items without underdeliveryand overdelivery tolerances, you can maintain a corresponding quantityprofile in consensus finding.

� Date/time tolerances

To define date/time tolerances, you have to maintain a correspondingtime profile in consensus finding.

The system automatically approves deviations within the tolerances andsets the status Approved. For deviations outside of the tolerances, manualapproval is required. The system therefore sets the approval status toManualApproval Required.

Hint: Even if all items of a purchase order do not contain a productfor which you have explicitly set the approval process, all items of thepurchase order are subject to the approval process. If you have notconfigured an approval process for a product, the system sets the approvalstatus Manual Approval Required when there are deviations.

If confirmation data of a purchase order received the approval status ManualApproval Required during the automatic approval process, you, as customer, mustcheck this confirmation data on the purchase order collaboration Web UI in thePurchase Order Details screen, and either approve or reject it manually. If youreject the data, SAP SNC generates an alert. The supplier then has to changethe confirmation data.

You can find the customizing for approval profiled in the



Approval StatusThe approval status of a confirmation schedule line can have the following values:

� New

The supplier has created a new confirmation schedule line or componentrequirement on the Purchase Order Details screen on the Web Web UI, andhas saved the purchase order but not yet published it.

� Approved

The confirmation schedule line has been approved (either automatically bythe system or manually by the customer).

� Manual Approval Required

The automatic approval process has determined that the confirmationschedule line deviates (to an excessive degree) from the request data. Thecustomer has to manually approve the confirmation schedule line.

Hint: When using the approval procedure with tolerances, aconfirmation schedule line or a component requirement is alwaysassigned this status if it deviates to an excessive degree outside ofthe tolerance limits. When using the approval procedure withouttolerances, a confirmation schedule line or a component requirementis only assigned this status if you use an approval profile for theproduct of the purchase order item, according to which the customermust approve deviations manually.

� Rejected

The customer has rejected the confirmation schedule line or the componentrequirement in the manual approval process. The supplier has to changethe confirmation data.

Confirmation ControlIn SAP SAP SNC, you can specify whether a supplier can create supplierconfirmations (purchase order confirmations or scheduling agreementconfirmations) or advanced shipping notifications (ASNs) for purchase orderitems in purchase order collaboration or for scheduling agreement releases.

ASNs or supplier confirmations can be mandatory, optional (default setting), orforbidden for a certain characteristics combination. Depending on your settings inconfirmation control, SAP SNC either permits the creation of ASNs and supplierconfirmations (obligatory or optional) or does not (forbidden).


SNC100 Lesson: Relevant Customizing for Purchase Order Processing in SAP SNC

You can configure confirmation control in Supply Network CollaborationCustomizing by choosing Delivery→ Confirmation Control→ Set ConfirmationControl. You can also access this activity from the SAP Easy Access menu bychoosing Supply Network Collaboration→ Delivery→ Supplier Confirmation→Current Settings.

Hint: Confirmation control also exists for purchase orders in an SAPback-end system. However, IDocs cannot transfer the settings forconfirmation control. You must therefore ensure that you maintain settingsconsistently in the SAP back-end system and in SAP SNC.

Calculation of Due QuantityFor the schedule lines of scheduling agreement releases, purchase orders, andreplenishment orders, SAP SNC automatically calculates the quantities that thesupplier still has to confirm with confirmations or ASNs. The following typesof due quantities exist:

� ASN-based due quantity

The ASN-based due quantity is relevant for scheduling agreement releases,purchase orders, and replenishment orders. The schedule line of a purchasingdocument has an ASN-based due quantity if the schedule line quantity isnot completely covered by ASNs. This means that the supplier has not yetpublished ASNs for the document in SAP SNC, or the published ASNshave quantities that are too small.

� Confirmation-based due quantity

The confirmation-based due quantity is only relevant for purchase orders. Arequest schedule line of a purchasing document has a confirmation-baseddue quantity if the requested quantity of the schedule line is not completelycovered by confirmations. This means that the supplier has not yet publishedconfirmations for the purchase order item in SAP SNC, or the publishedconfirmations have quantities that are too small. To detect request schedulelines with due quantities, the system assigns confirmed quantities to therequest schedule lines from the confirmation schedule lines.

Caution: SAP SNC only calculates the confirmation-based due quantityand the ASN-based due quantity for documents for which you can createconfirmations or ASNs. For purchase orders and scheduling agreementreleases, you therefore must have made a setting in SAP SNC confirmationcontrol to determine if confirmations and ASNs are optional or mandatory.Confirmations and ASNs are optional in the standard configuration.

Note: You can use the /SCF/DUELIST BAdI to implement your ownalgorithm for determining open schedule lines.



Lesson Summary

You should now be able to:� List the Customizing possibilities for the SAP SNC PO process� Discuss the due quantity calculation logic


SNC100 Unit Summary

Unit SummaryYou should now be able to:� Explain and understand the purchase order process details in SAP SNC� Differentiate between statuses in the SAP SNC purchase order� Name the purchase order alerts in SAP SNC� Perform your exercise on purchase order processing in SAP SNC� Explain the message flow for the SAP SNC purchase order process� Discuss the monitoring possibilities for the message integration between


process� List the Customizing possibilities for the SAP SNC PO process� Discuss the due quantity calculation logic


Unit Summary SNC100


Unit 3Release Process with SAP SNC

Unit OverviewIn this unit, you will gain deeper insight into the scheduling agreement releaseprocess within SAP SNC.


� Explain the release process details in SAP SNC� Name the release alerts in SAP SNC� Perform release processing in SAP SNC� Describe the Customizing possibilities for the SAP SNC release process� Explain the due quantity calculation logic

Unit ContentsLesson: Scheduling Agreement Release Process - Overview... . . . . . . . . . . 90Lesson: Release Processing: Process Demo .... . . . . . . . . . . . . . . . . . . . . . . . . . .101

Exercise 3: Release Processing with SAP SNC ... . . . . . . . . . . . . . . . . . . . .103Lesson: Relevant Customizing for Release Processing with SAP SNC.110


Unit 3: Release Process with SAP SNC SNC100

Lesson: Scheduling Agreement Release Process -Overview

Lesson OverviewThis lesson will give you an overview on the SAP SNC scheduling agreementrelease process. You will learn about the process steps and alerts for this process.


� Explain the release process details in SAP SNC� Name the release alerts in SAP SNC

Business Example

BackgroundRelease processing in SAP Supply Network Collaboration (SAP SNC) supportsprocurement processes on the basis of scheduling agreements. A schedulingagreement is an outline agreement between a customer and a supplier. It specifiesthe total quantity of the products that a supplier is to deliver to the customerin a specific time period. The customer performs exact planning at regularintervals and determines what exact demand quantities are to be released from thescheduling agreement on certain dates.

To inform the supplier about the current demands, the customer sends a schedulingagreement release for one or several products to SAP SNC. For each item, thescheduling agreement release contains schedule lines. Each schedule line containsa demand for a product with a quantity and a date/time.

The supplier can display the releases in the SAP SNC Web user interface (WebUI) and supply the customer based on the schedule lines in the up-to-date release.

To inform the customer about probable delivery quantities and dates/times,the supplier (or the customer on behalf of the supplier) can create schedulingagreement confirmations in the SAP SNC Web UI. The customer can see thescheduling agreement confirmations in the SAP SNC Web UI.

To inform the customer about a forthcoming delivery, the supplier sends thecustomer an advanced shipping notification (ASN). The supplier can create theASN manually in SAP SNC or send it from his or her backend system.


SNC100 Lesson: Scheduling Agreement Release Process - Overview

When the customer updates his or her planning, that customer sends a newscheduling agreement release to SAP SNC. This replaces the predecessor release,and the supplier delivers on the basis of the new release. Both the customer andthe supplier can view the delivery progress details in release processing. Thisincludes the cumulative received quantity or data for the deliveries that havealready been made.

Process

Figure 48: Release Process in SAP SNC 5.1

1. Publish a new forecast delivery schedule (customer�s ERP system, SAPR/3 4.6C or higher).

The customer creates a forecast delivery schedule in the ERP system. TheERP system transfers the DELINS.DELFOR01 IDoc to the customer�s SAPNetWeaver system. The SAP NetWeaver system converts the IDoc intoan XML message of type DeliveryScheduleNotification and transfers it toSAP SNC.

Hint: You can distinguish between forecast delivery schedule(LAB) and JIT delivery schedule (FAB) by the value in theE1EDP10-SCREL field; 03 stands for LAB and 02 for FAB.

2. Display the forecast delivery order (SAP SNC).3. OPTIONAL

a) Publish an advanced shipping notification (supplier�s ERP system).



When the material is ready for delivery, the supplier can publish an advancedshipping notification in his or her ERP system. The ERP system transfersan XML message of type DespatchedDeliveryNotification to the customer�sSAP NetWeaver system, which forwards the message to SAP SNC.

Caution: The IDocs, XML messages, and mappings depend onwhich ERP system and releases are being used. Depending onthe supplier�s system, mappings are sometimes required for themessage flow between the supplier�s system and SAP SNC. Sincethe mappings are dependent on the supplier�s system, they cannotbe predefined in the SAP SNC standard delivery; you must createthe mappings as part of a project solution.

b) Receive the advanced shipping notification in SAP SNC.

4. Create an advanced shipping notification in the Web UI (SAP SNC.

If suppliers do not use an ERP system to send advanced shippingnotifications, they can create them in the Web UI. The SAP SNC systemtransfers an XML message of type DespatchedDeliveryNotificationto the SAP NetWeaver system, which converts the message into theDESADV.DELVRY03 IDoc and transfers it to the customer�s ERP system.

5. Receive an advanced shipping notification (customer�s ERP system).6. Post a goods receipt (customer�s ERP system).

When the customer posts the goods receipt, the customer�s ERP systemsends the STPPOD.DELVRY03 IDoc to the SAP NetWeaver system. TheSAP NetWeaver system converts the IDoc into an XML message of typeReceivedDeliveryNotification and transfers it to SAP SNC.

7. Display the goods receipt information (SAP SNC).

DefinitionA scheduling agreement is an outline agreement between a customer and asupplier. It specifies the total quantity of the products that a supplier is to deliverto the customer in a specific time period. The customer performs exact planning atregular intervals and determines what exact demand quantities are to be releasedfrom the scheduling agreement on certain dates. To inform the supplier about thecurrent demands, the customer sends a scheduling agreement release for one orseveral products to SAP SNC. For each item, the scheduling agreement releasecontains schedule lines. Each schedule line contains a demand for a product with aquantity and a date/time.



Release TypesSAP SNC supports forecast delivery schedules and just-in-time (JIT) deliveryschedules. You can use both forecast delivery schedules and JIT deliveryschedules for a scheduling agreement item.

Visible ReleasesA business partner user can see the following releases in release processing in thestandard system (selection mode ODM_REL):

� A supplier user can see releases in the supplier view in which the supplier isentered as the supplier.

� A customer user can see releases in the customer view in which the customeris entered as the customer.

� A goods recipient user can see releases in the goods recipient view in whichthe goods recipient is entered as the goods recipient.

The location and product names of the location products from these releases areavailable in input help (provided that the user authorization allows these locationsand products to be displayed).

NotesYou can create notes in release processing for a release at header and scheduleline level. If you create a note, the system automatically generates an alert (alerttype 7105).

An XML message of type DeliveryScheduleNotification can also transfer notes toSAP SNC, and you can display them in release processing.



XML Messages in Release ProcessingRelease processing uses the following XML messages:

� DeliveryScheduleNotification

The customer generates a release in his or her backend system andsends the release as an electronic message to SAP NetWeaver with theProcess Integration usage type. SAP NetWeaver maps the messageto an XML message DeliveryScheduleNotification and sends theDeliveryScheduleNotification to SAP SNC. You differentiate between aforecast delivery schedule and a JIT delivery schedule on the basis of therelease type in the release header.

If the customer uses an SAP ERP system as the backend system, the ERPsystem sends and receives messages in IDoc format. SAP delivers standardXSLT mappings for the following release IDocs:

� DELINS.DELFOR01 (release generation in an SAP R/3 or SAP ERPsystem)

� DELFOR.DELFOR02 (release generation in an SAP DIMP system):The IDoc is available as of SAP DIMP 4.71.

� DELINS.DELFOR02 (release generation in SAP APO; only relevantfor release processing in the service parts management scenario): TheIDoc is available as of SAP SCM 5.0.

� DespatchedDeliveryNotification

SAP SNC sends an ASN, which the supplier publishes in SAP SNC fora release, to the customer�s backend system using SAP NetWeaver witha DespatchedDeliveryNotification.

� ReceivedDeliveryNotification

On receipt of the delivery, the customer sends the goods receipt informationwith a message from his or her backend system to SAP NetWeaver. SAPNetWeaver maps the message to a ReceivedDeliveryNotification thatit sends to SAP SNC. SAP SNC updates the ASN on the basis of theReceivedDeliveryNotification.

Release StatusSAP SAP SNC sets the status automatically, depending on the function that youpreviously performed on the release. The following table contains an overviewof the release statuses.



Release StatusStatus DescriptionPrinted You have printed the release.Downloaded You have downloaded the release.Acknowledged The supplier has confirmed that he or she has noted the

release.Rejected The supplier has rejected the release.

Level of CommitmentThe level of commitment informs the supplier about the schedule line type andhow binding a schedule line is. The customer transfers the level of commitmentto in the scheduling agreement release to SAP SNC.

The following table contains an overview of the possible values for the levelof commitment in SAP SNC.

Level of CommitmentValue Description Explanation001 Fixed dates and

quantitiesQuantity and date of the schedule line arefixed and will remain unchanged. Theschedule line belongs to a delivery-relevantrelease. The supplier can deliver thequantity without waiting for anotheracknowledgement or the customer�srequest.

002 Production andmaterial go-ahead

The schedule line belongs to a forecastdelivery schedule that is not relevant fordelivery and is in the production go-aheadperiod. The supplier can, therefore, procurethe materials for manufacturing the orderedproducts and start with production. Ifthe customer cancels a schedule line,the supplier can invoice the material andproduction costs.



003 Material go-ahead The schedule line belongs to a forecastdelivery schedule that is not relevant fordelivery and is within the material go-aheadperiod. The supplier can, therefore, procurethe materials that he or she requires forproduction. If the customer cancels aschedule line, the supplier can invoice forthe material costs.

004 Preview The schedule line belongs to a forecastdelivery schedule that is not relevant fordelivery. The schedule line is not bindingand may change. The supplier can use thedata for his or her own planning, however.

005 * Missing quantity /backlog

The schedule line is in the past. Thecustomer has already transferred theschedule line in a release but the supplierhas not yet delivered the schedule line.

010 * Immediaterequirement

The customer has not yet transferred theschedule line in a release, but needs theschedule line quantity immediately.

* These values are relevant if you use a DIMP system as the customer backendsystem.

Release ComparisonThe schedule lines of two releases may differ in terms of quantities and dates.The release comparison allows you to detect these differences. In the releasecomparison, SAP SNC compares the releases at schedule line level and determinesthe differences between the quantities, the cumulative released quantities, andthe delivery dates.

You call the release comparison in the release history. You specify the releasesthat you want to compare as follows:

� If you do not select any releases, SAP SNC compares the current releasewith the predecessor release.

� If you want to compare any release with the current release, select the release.� If you want to compare any two releases, select these releases.



Scheduling Agreement ConfirmationsThe supplier can use scheduling agreement confirmations to inform the customerabout when he or she can deliver which quantities. The customer can usescheduling agreement confirmations to plan in greater detail. In the time intervalbetween the release date and the delivery date indicated by the ASN, the customerreceives additional information about expected deliveries.

The supplier creates scheduling agreement confirmations for schedule lines of thecurrent release on the SAP SNC Web UI. The supplier can create one or morescheduling agreement confirmations for a schedule line. A scheduling agreementconfirmation, therefore, always refers to one specific release schedule line. Thesupplier uses several scheduling agreement confirmations if he or she does notwant to deliver the quantity requested by the customer in the release schedule lineall on one date, but would rather deliver over several dates.

If the supplier wants a scheduling agreement confirmation to be visible tothe customer in SAP SNC, the supplier publishes the scheduling agreementconfirmation. The customer can see the scheduling agreement confirmationin the release details.

If your backend system can handle confirmations for schedulingagreement releases (SA releases) you may send the scheduling agreementconfirmation to your backend. The mapping from the XML messageDeliveryScheduleConfirmation_Out to the required inbound message for yourbackend system needs to be developed on project base.

Note: For an SAP backend, see SAP Note 810340.

Release AlertsRelease processing distinguishes between supplier-specific and customer-specificalert types. In the alert monitor, the alert types can only be seen by the relevantpartner in each case.

The following options are available to generate a release alert, depending on thealert type:


� System administration executes a report regularly in the SAP SNC system.To call the report for online processing, from the SAP Easy Access screen,choose Supply Network Collaboration→ Exceptions→ Alert Generation→<Report>.

� SAP SNC generates the alert during validation of the release. Systemadministration can deactivate alert generation in Customizing for validation.

The following list contains the alert types for release processing in SAP SNC.



Exception during validation of scheduling agreement release (alert ID 7034)Relevant for customer and supplier.The validation has detected invalid, missing, or differing data in the release.This alert might be from special interest for monitoring errors in the XMLInbound processing for Releases.

New scheduling agreement release (alert ID 0023)Relevant for supplier only.A new release has arrived in SAP SNC.This alert is generated by the PPF (application /SCA/ICH, actionprofile /SCA/BOL_RELEASE, action /SCA/BOL_REL_NEWRE-LEASE_CHECK).

Unacknowledged scheduling agreement release (alert ID 0024)Relevant for customer and supplier.The supplier has not yet acknowledged the release after the end of a certainperiod.System administration generates these alerts using report/SCA/RELUNACKNALERTWRITE. The report deletes obsolete alerts.

Unloading point has changed (alert ID 7025)Relevant for supplier only.The unloading point of the current release deviates from the unloading pointof the previous release.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_RELEASE, action /SCA/BOL_REL_UNLD_CHG).

Cumulative received quantity is smaller (alert ID 7026)Relevant for supplier only.The cumulative received quantity of the current release is less than that ofthe previous release.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_RELEASE, action /SCA/BOL_REL_CUM_QUAN_LESS).

Fiscal year has changed (alert ID 7027)Relevant for supplier only.The fiscal year of the current release deviates from the fiscal year of theprevious release.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_RELEASE, action /SCA/BOL_REL_FISCAL_YR_CHG).



Scheduling agreement release with a demand that cannot be covered(supplier) (alert ID 7028)

Relevant for supplier only.The release contains schedule lines that you, as supplier, cannot cover withinthe lead time. To determine whether a release contains uncovered schedulelines, SAP SNC takes account of the deliveries that the supplier has sent tothe customer. Here, SAP SNC evaluates the ASNs that the supplier sentto the customer.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_RELEASE, action /SCA/BOL_REL_UNSATIS_DEMAND).

Scheduling agreement release with a demand that cannot be covered(customer) (alert ID 7029)

Relevant for customer only.This alert corresponds to alert type 7028 for uncovered releases that canonly be seen by suppliers (see above).System administration generates these alerts using report/SCA/REL_DEMAND_ALERT_WRITE. The report deletes obsoletealerts.

Scheduling agreement release overdue (alert ID 7101)Relevant for customer and supplier.The release contains due schedule lines in the past.System administration generates these alerts using report/SCA/DUELISTALERTWRITE.

Scheduling agreement due within lead time (alert ID 7102)Relevant for customer and supplier.The release contains schedule lines in the future that lie within the leadtime and have due quantities.System administration generates these alerts using report/SCA/DUELISTALERTWRITE.

New note for scheduling agreement release (alert ID 7105)Relevant for customer and supplier.The customer or supplier has created a new note for the release in SAP SNCrelease processing or a scheduling agreement confirmation.This alert is generated by the PPF (application /SCA/ICH_NOTES, actionprofile /SCA/BOL_REL_NOTES, action /SCA/BOL_REL_NEW_NOTES).

Scheduling Agreement Release rejected (alert ID 7107)Relevant for customer only.The supplier has rejected the release on the release processing Web UI.This alert is generated automatically by the system.



Lesson Summary

You should now be able to:� Explain the release process details in SAP SNC� Name the release alerts in SAP SNC


SNC100 Lesson: Release Processing: Process Demo

Lesson: Release Processing: Process Demo

Lesson OverviewThis is your chance to see what has been discussed and to view a system demo.


� Perform release processing in SAP SNC

Business Example

Demo

Figure 49: Demo





Exercise 3: Release Processing with SAPSNC

Exercise ObjectivesAfter completing this exercise, you will be able to:� Run a release processing scenario with SAP SNC

Business ExampleRelease processing in SAP Supply Network Collaboration (SAP SNC) supportsprocurement processes on the basis of scheduling agreements. A schedulingagreement is an outline agreement between a customer and a supplier. It specifiesthe total quantity of the products that a supplier is to deliver to the customerin a specific time period. The customer performs exact planning at regularintervals and determines what exact demand quantities are to be released from thescheduling agreement on certain dates. To inform the supplier about the currentdemands, the customer sends a scheduling agreement release for one or severalproducts to SAP SNC. For each item, the scheduling agreement release containsschedule lines. Each schedule line contains a demand for a product with a quantityand a date/time.

The supplier can display the releases in the SAP SNC Web UI and supply thecustomer based on the schedule lines in the up-to-date release. To informthe customer about probable delivery quantities and dates/times, the supplier(or the customer on behalf of the supplier) can create scheduling agreementconfirmations in the SAP SNC Web UI. The customer can see the schedulingagreement confirmations in the SAP SNC Web UI. To inform the customer abouta forthcoming delivery, the supplier sends the customer an advanced shippingnotification (ASN). The supplier can create the ASN manually in SAP SNC orsend it from his or her back-end system.

Task 1: Create Release Delivery Schedule in ERP �Customer

Note: This task is performed in the role of the customer and thus isperformed in the ERP system (User SNC100-##).

Maintain a delivery schedule for your supplier, SNC100B-##, and materialT-A100-##, and send a scheduling agreement release to SAP SNC.

1. Navigate to the Maintain Scheduling Agreement Schedule: Initial Screen.

2. Find the scheduling agreement for your supplier and maintain a deliveryschedule.

Write down the scheduling agreement number.Continued on next page



___________

3. Send the release delivery schedule information to SNC

Task 2: Check the SNC Alert Monitor

Hint: This task is performed in the role of the supplier thus with userIU-SUPB##.

Which alert(s) are in the alert monitor?

1. Log on to SNC as the supplier and check the alert monitor for alerts relatingto the new release.

Task 3: Acknowledge ReleaseAcknowledge the release that has been sent to SAP SNC.

1. In the supplier view in SAP SNC, choose Release→ Release Overviewand acknowledge the release.

Task 4: Release ComparisonCreate a second release for your scheduling agreement. Change some dates andquantities and add/remove some schedule lines in your delivery schedule. Thensend the new release to SAP SNC and use the release comparison function tosee the difference between the releases.

1. In SAP ERP, make some changes to the delivery schedule of your schedulingagreement and send a new release to the supplier.

2. In SAP SNC, review the new release.

3. Use the compare releases function of SAP SNC to see the differencesbetween any two releases of your scheduling agreement.



Solution 3: Release Processing with SAPSNCTask 1: Create Release Delivery Schedule in ERP �Customer

Note: This task is performed in the role of the customer and thus isperformed in the ERP system (User SNC100-##).

Maintain a delivery schedule for your supplier, SNC100B-##, and materialT-A100-##, and send a scheduling agreement release to SAP SNC.

1. Navigate to the Maintain Scheduling Agreement Schedule: Initial Screen.

a) Call Transaction Create Scheduling Agreement.

Use transaction code ME38 or choose Logistics → MaterialsManagement→ Purchasing→ Outline Agreement→ SchedulingAgreement→ Delivery Schedule→ Maintain.

2. Find the scheduling agreement for your supplier and maintain a deliveryschedule.

Write down the scheduling agreement number.




___________

a) On the Maintain Scheduling Agreement Schedule: Initial Screen, callthe input help for the scheduling agreement field and search for thescheduling agreement for your vendor, SNC100B-##.

Press F4 and then select the Purchasing Documents per Vendor tabpage.

Enter your vendor number, purchasing organization 1000, andpurchasing group S##. Choose Enter.

The system finds the corresponding scheduling agreement. ChooseEnter once again.

b) Choose Enter to branch to the Maintain Scheduling AgreementSchedule: Item Overview screen.

c) Select item 10 and, from the menu, choose Item→ Delivery Schedule .

d) Maintain the afterwards values.

Category of Del. Date Date Qty TimeD + 2 weeks 20 12:00D + 2 weeks & 2 days 20 12:00D + 3 weeks 20 12:00D + 3 weeks & 2 days 20 12:00W 1st week of 2nd month 20 12:00W 2nd week of 2nd month 20 12:00W 3rd week of 2nd month 20 12:00W 4th week of 2nd month 20 12:00M 3rd month 80 12:00M 4th month 80 12:00M 5th month 80 12:00M 6th month 80 12:00

3. Send the release delivery schedule information to SNC

a) Choose Edit→ Generate Forc. schd. or press F6.

b) Choose Save to save the delivery schedule and process the messageoutput.




Task 2: Check the SNC Alert Monitor

Hint: This task is performed in the role of the supplier thus with userIU-SUPB##.

Which alert(s) are in the alert monitor?

1. Log on to SNC as the supplier and check the alert monitor for alerts relatingto the new release.

a) Log on to SNC with the supplier user IU-SUPB## and passwordwelcome.

b) In the Alert Monitor screen enter your product, T-A100-##, andchoose Go.

You will see the alerts relating to your supplier location for this product.A new release generates the alert New SA Release.

c) In the Statistical View section, select the value associated with theNew SA Release alert.

The New SA Release alert will be displayed under the Release tabat the bottom.

Select the alerts and press the See Details button. The system takes youimmediately to the Release Details screen.

Task 3: Acknowledge ReleaseAcknowledge the release that has been sent to SAP SNC.

1. In the supplier view in SAP SNC, choose Release→ Release Overviewand acknowledge the release.

a) In SAP SNC, in the Release Overview screen, select your schedulingagreement release and choose Acknowledge.

Hint: You can also acknowledge the release from the ReleaseDetails screen.

Hint: If you log on to SNC customer view with customer userSNC100-## and navigate to the Release Overview screen,you will see the acknowledgement date of the release by thesupplier.




Task 4: Release ComparisonCreate a second release for your scheduling agreement. Change some dates andquantities and add/remove some schedule lines in your delivery schedule. Thensend the new release to SAP SNC and use the release comparison function tosee the difference between the releases.

1. In SAP ERP, make some changes to the delivery schedule of your schedulingagreement and send a new release to the supplier.

a) Navigate to transaction Maintain Scheduling Agreement Schedule:Delivery Schedule.

Use transaction code ME38 or choose Logistics → MaterialsManagement→ Purchasing→ Outline Agreement→ SchedulingAgreement→ Delivery Schedule→ Maintain.

b) Enter the scheduling agreement number that you noted down earlierand choose Enter.

c) Double-click on item 10 to navigate to the delivery schedule of item 10.

d) Change some quantities and dates and add/remove some schedule lines.

e) To issue a new release, press F6 or choose Edit→ Generate Forc.Schd..

The traffic light should switch from yellow to green.

f) Save your changes.

2. In SAP SNC, review the new release.

a) In SAP SNC, navigate to the Release Details screen for your schedulingagreement.

b) Choose Release→ Release Details.

c) Choose Go.

d) Review the new release.

3. Use the compare releases function of SAP SNC to see the differencesbetween any two releases of your scheduling agreement.

a) Choose Compare Releases to compare the latest two releases.

Hint: You can compare any two releases of a schedulingagreement by selecting these two releases in the ReleaseHistory section and choosing Compare Releases.



Lesson Summary

You should now be able to:� Perform release processing in SAP SNC



Lesson: Relevant Customizing for Release Processingwith SAP SNC

Lesson OverviewThis lesson will give you an overview of the relevant customizing activities inSAP SNC and will help you to understand the logic for due quantity calculation.


� Describe the Customizing possibilities for the SAP SNC release process� Explain the due quantity calculation logic

Business Example

Confirmation ControlIn SAP Supply Network Collaboration (SAP SNC), you can specify whethera supplier in SAP SNC can create supplier confirmations (purchase orderconfirmations or scheduling agreement confirmations) or advanced shippingnotifications (ASNs) for purchase order items in purchase order collaborationor for scheduling agreement releases.

ASNs or supplier confirmations can be mandatory, optional (default setting), orforbidden for a certain characteristics combination. Depending on your settings inconfirmation control, SAP SNC either permits the creation of ASNs or supplierconfirmations (obligatory or optional) or does not (forbidden).

You configure confirmation control in Supply Network Collaboration Customizingby choosing Delivery→ Confirmation Control→ Set Confirmation Control. Youcan also access this activity from the SAP Easy Access screen by choosing SupplyNetwork Collaboration→ Delivery→ Supplier Confirmation→ Current Settings.


SNC100 Lesson: Relevant Customizing for Release Processing with SAP SNC

Calculation of Due QuantityFor the schedule lines of scheduling agreement releases, purchase orders, andreplenishment orders, SAP SNC automatically calculates the quantities that thesupplier still has to confirm with confirmations or advanced shipping notifications(ASNs). The following types of due quantities therefore exist:

� ASN-based due quantity

The ASN-based due quantity is relevant for scheduling agreement releases,purchase orders, and replenishment orders. The schedule line of a purchasingdocument has an ASN-based due quantity if the schedule line quantity isnot completely covered by ASNs. This means that the supplier has not yetpublished ASNs for the document in SAP SNC or the published ASNs havequantities that are too small.

� Confirmation-based due quantity

The confirmation-based due quantity is only relevant for purchase orders.

Caution: SAP SNC only calculates the confirmation-based due quantityand the ASN-based due quantity for documents for which you can createconfirmations or ASNs. For purchase orders and scheduling agreementreleases, you must have made a setting in SAP SNC confirmation controlto determine that confirmations and ASNs are optional or mandatory.Confirmations and ASNs are optional in the standard configuration.

Note: You can use the /SCF/DUELIST BAdI to implement your ownalgorithm for determining open schedule lines.

The due quantities are displayed in SAP SNC, for example, in the due list forpurchasing documents (ASN-based due quantity and confirmation-based duequantity). If the supplier creates an ASN in the due list for a purchasing document,SAP SNC automatically proposes the ASN-based due quantity as the ASNquantity. If the due quantity is zero, the supplier cannot create an ASN in theseapplications.

SAP delivers default settings for calculating due schedule lines. If necessary,you can make alternative settings in Supply Network Collaboration Customizingby choosingDelivery→ Due Quantity Calculation→ Determine Due ScheduleLine Quantities.

In this IMG activity, you determine the following:

� Which date/time the system copies to the ASN (shipping date/time ordelivery date/time)

� Which ASNs the system considers for a release (the Relevant ASNs andRelease Reference Time Stamp fields)



The system only considers ASNs that have the status Published, CompleteGoods Receipt, and Partial Goods Receipt. In the Relevant ASNs field, youcan set the method that the system uses to choose release-relevant ASNs.You can choose between the following methods:

� Time stamp

The system uses the following time stamps:

For an ASN, the system uses the ASN change time stamp that wastransferred to SAP SNC with the XML message. If the XML messagedoes not contain a change time stamp, the system uses the ASN changetime stamp from SAP SNC (this time stamp is the point at which theASN was last changed in SAP SNC).

For a release, you set a release reference time stamp in this IMGactivity. (See below.)

You can choose between the following time stamps:

Selection Based on Time Stamps and

Change Time Stamp of ASN in Release

More detailed information about these two time stamps can be foundfurther below.

� Control category for cumulative quantities

The cumulative quantity control category reflects whether the customer,when creating a release in the back-end system, considers only theposted goods receipt quantities or the total quantities confirmed by thesupplier. This depends on whether the customer or the supplier wantsto synchronize their cumulative quantities by means of goods receiptsor inbound deliveries. SAP SNC also considers this when calculatingthe due release schedule lines.

Hint: Depending on the time stamps and on the control category,SAP SNC decides whether an ASN is relevant for a release asfollows:

� If the customer considers goods receipts when creating a releasein the back-end system, ASNs with the status Complete GoodsReceipt or Partial Goods Receipt that exist in the back-endsystem at the release reference time (for example, at the timeof release creation) are considered. The release quantities arereduced accordingly. SAP SNC thus only considers ASNs thathave goods receipt status and that lie after the release referencepoint, when it calculates due quantities. In addition, SAP SNCconsiders all ASNs that have the status Published, regardless ofwhether they lie before or after the release reference time.



� If the customer considers inbound deliveries during releasecreation, all ASNs contained in the release that exist in theback-end system at the release reference time are considered.The release quantities are reduced accordingly. SAP SNC thusonly considers ASNs that occur after the release reference timeand that have the status Published, Goods Receipt, or PartialGoods Receipt when it calculates due quantities.

In the case of the Selection Based on Customer Cumulative Quantitymethod,the system considers the customer cumulative quantity in the ASN, thecustomer cumulative quantity in the release, and also the cumulative controlcategory. The system assigns ASNs to releases as follows:

� If, according to the control category, the customer considers goodsreceipts during release creation in the back-end system, SAP SNCassigns all published ASNs to the release, regardless of the ASNchange time stamp. SAP SNC also assigns ASNs with the statusComplete Goods Receipt or Partial Goods Receipt and that also fulfillthe following conditions:

The change time stamp of the ASN lies after the release creation timestamp of the most up-to-date release that has transferred a reconciliationdate/time.

The customer cumulative quantity of the ASN is greater than thecustomer cumulative quantity of the release.

� If, according to the control category, the customer considers theinbound deliveries that already exist during release creation in theback-end system, SAP SNC assigns to the release those ASNS with thestatusPublished, Complete Goods Receipt, or Partial Goods Receiptthat fulfill the following conditions:

The change time stamp of the ASN lies after the release creation timestamp of the most up-to-date release that has transferred a reconciliationdate/time.

The customer cumulative quantity of the ASN is greater than thecustomer cumulative quantity of the release.

� The release reference time stamp

You can choose between the following time stamps:

� Change Time Stamp of ASN in Release

The release contains the number of the most up-to-date ASN that isknown in the back-end system at the time of release creation. SAP SNCuses the ASN number to determine the change time stamp of this ASN.

� Release Creation Time Stamp



This time stamp is transferred to SAP SNC with the release.

Hint: If the release does not contain the time, SAP SNC setsthe time of the change time stamp to 12:00:00. If you, ascustomer, run an SAP back-end system, implement SAP Note858447 if required.

� How the system calculates the ASN quantities of these ASNs with theschedule lines (Assignment Algorithm field)

In the Assignment Algorithm field, you define how the system distributes theASN quantities that are relevant for the release to the release schedule lines.Assignment occurs based on the date/time that is relevant for calculatingthe ASN-based due quantity (depending on your settings, this is either theshipping date/time or the delivery date/time).

You can choose between the following assignment algorithms:

� Use timely ASNs

In this method, the system only assigns ASNs to a release scheduleline where the delivery or shipping date/time occurs before or on therequested delivery/shipping date. The system processes the releaseschedule lines chronologically, that is, the system first assigns timelyASNs to the schedule line that has the earliest date/time, then the next,and so on.

� Use complete ASN quantity (standard)

This is the method that the system uses by default. In this method, thesystem first adds up the delivery quantities of all ASNs that are assignedto the release. From this total quantity, the system chronologicallyassigns the quantity needed to the release schedule lines, based on thedates/times they contain. Note that the ASN dates/times do not play arole for assignment. The delivery date/time of an ASN can occur afterthe requested delivery date/time of the release schedule line.

Hint: The system uses the following quantity of an ASN dependingon the ASN status:

� ASN quantity, if the ASN has the status Published or PartialGoods Receipt

� Received quantity, if the ASN has the status Complete GoodsReceipt

� Which release schedule lines the system considers (depending on the level ofcommitment of a release schedule line)



Lesson Summary

You should now be able to:� Describe the Customizing possibilities for the SAP SNC release process� Explain the due quantity calculation logic


Unit Summary SNC100

Unit SummaryYou should now be able to:� Explain the release process details in SAP SNC� Name the release alerts in SAP SNC� Perform release processing in SAP SNC� Describe the Customizing possibilities for the SAP SNC release process� Explain the due quantity calculation logic


Unit 4ASN Processing in SAP SNC

Unit OverviewIn this unit, you will gain deeper insight into the ASN processing within SAP SNC.


� Explain ASN processing in SAP SNC� Name the ASN alerts� Discuss the packing functionality in SAP SNC ASNs� Explain the difference between automated and manual packing� Perform ASN processing in SAP SNC� Describe the Customizing possibilities in ASN processing in SAP SNC� Set up message determination for this process

Unit ContentsLesson: ASN Processing Overview ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118Lesson: Packing ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136Lesson: Process Demo: ASN Processing.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Exercise 4: ASN Processing with SAP SNC... . . . . . . . . . . . . . . . . . . . . . . . . .151Lesson: Relevant Customizing for ASN Processing in SAP SNC.... . . . .163


Unit 4: ASN Processing in SAP SNC SNC100

Lesson: ASN Processing Overview

Lesson OverviewThis lesson will give you an overview of the ASN Processing within SAP SNC.You will learn about the process steps and the available alerts.


� Explain ASN processing in SAP SNC� Name the ASN alerts

Business Example

BackgroundAdvanced shipping notifications (ASNs) are key documents in the collaborationbetween suppliers and customers. A supplier uses an ASN to inform a customerthat he or she has sent a delivery. The ASN informs the customer of whichproducts and quantities are in transit and the expected arrival time of the delivery.

The supplier can create ASNs for the following objects:

� Planned receipts (relevant for supplier-managed inventory)� Purchase orders� Scheduling agreement releases� Replenishment orders


SNC100 Lesson: ASN Processing Overview

ASN processing in SAP Supply Network Collaboration (SAP SNC) comprisesvarious functions for processing an ASN (from the supplier and the customerviewpoint) and for depicting the progress of the delivery process:

� The supplier can create ASNs manually in ASN processing and send themto the customer. Due lists are available as a starting point for targetedprocessing of open deliveries. These lists contain the planned receipts orreplenishment orders that a supplier has created (for example, within theSMI process) or the customer�s purchasing documents (purchase ordersand scheduling agreement releases) with due schedule lines. Alternately,suppliers can create ASNs in their backend system and send them to SAPSNC. SAP SNC then forwards ASNs to the customer�s backend system.

Caution: The IDocs, XML messages, and mappings dependon which ERP system and release is being used. Mappings aresometimes required for the message flow between the supplier�ssystem and SAP SNC. Since the mappings are dependent on thesupplier�s system, they cannot be predefined in the SAP SNCstandard delivery.; you must create the mappings as part of a projectsolution.

� In ASN processing, the customer gains an overview of the deliveries thesupplier has planned or already sent and when these deliveries will arrive.The customer can send messages for delivery receipt and for goods receiptsfrom his or her backend system to SAP SNC Alternately, in ASN processing,the customer can manually post a complete goods receipt or manually setASNs to Closed.



Process

Figure 50: Process

1. Call ASN processing. To do so, you can select one of various options:

� Create an ASN for a purchase order or for a scheduling agreementrelease

� Create an ASN for a planned receipt� Copy and change an ASN� Create an ASN directly

2. Enter the required data on the ASN Header tab page. Note the following:

� If you create an ASN for a planned receipt or for an order document, thesystem automatically transfers the data to the ASN. This data includesthe delivery date, the ship-from location, the customer location, andthe ship-to location.

� If you enter either only the delivery date or only the shipping date, SAPSNC uses scheduling to automatically calculate the other date in eachcase when you save the ASN. You can also enter both dates. In thiscase, SAP SNC does not perform scheduling.

� You only have to enter the ASN number if system administrationhas set external number assignment for ASNs. In internal numberassignment, SAP SNC generates an ASN number automatically.

3. Enter the optional data on the remaining tab pages if required. This data is notmandatory, but is important if you want shipping processing to run smoothly.



4. Create the ASN items. To create an ASN item, choose the Add Itemfunction in the ASN Items screen area. In addition to the product and thequantity, enter � for each item � the number and item of the customer�sorder document to which the ASN item refers. This means the customer canlink the ASN with the order document and the item. This is important forposting goods receipts. You can use rounding to round the item quantityto a whole-numbered multiple of the rounding value set for the locationproduct. You can delete an item again, if required, by choosing Delete Item.If required, enter additional, optional item data such as the batch number ordangerous goods data.

5. If required, choose Check to perform an SAP-SNC-internal validation. Inthe validation, SAP SNC checks whether the ASN data at header level andat item level is complete and correct. Fill in the missing data or correctthe incorrect data as required. You can save an ASN that is not correct.In the standard system, incorrect ASN data or an incorrect ASN headeracquire the validation status Invalid in accordance with the standard settingsin Customizing for Validation.

6. If you save the data, but want to continue processing the ASN (possibly at alater time), save the ASN as a draft. The ASN acquires the Draft processstatus. SAP SNC automatically performs an internal validation.

7. If required, pack the ASN items manually or automatically. In other words,create handling units and print labels and the delivery note.

8. If you want to send the ASN to the customer, publish the ASN. SAP SNCperforms a validation automatically in this case. If the ASN does not showany errors, SAP SNC publishes the ASN; the ASN acquires the processstatus Published and SAP SNC sends the ASN to the customer. If the ASNcontains errors, you cannot publish it in the standard system. This is specifiedin Customizing for Validation. The relevant sub-objects (ASN items or ASNheader) acquire the validation status Invalid and the ASN retains the processstatus Draft. To publish the ASN, you must first correct the incorrect data.

9. Receive the advanced shipping notification (customer�s ERP system). Theadvanced shipping notification is stored in ERP as an inbound delivery. Theinbound delivery will update the referred purchasing document.

10. When the customer posts the goods receipt, the customer�s ERP systemsends the STPPOD.DELVRY03 IDoc to the SAP NetWeaver system.The SAP NetWeaver system converts the IDoc into an XML messageReceivedDeliveryNotification and transfers it to SAP SNC.

Note: As an alternative, the PROACT.PROACT01 IDoc can beissued by report RSMIPROACT to carry goods receipt informationto SAP SNC.

11. Display goods receipt information in SAP SNC. Dependent on the goodsreceipt quantity, the ASN will change the item and header status to PartialGoods Receipt or Goods Receipt Complete.



XML Message in ASN ProcessingASN processing uses the following XML messages in the standard system:

� DespatchedDeliveryNotification

If the supplier publishes an ASN in SAP SNC, SAP SNC generates an XMLmessage of type DespatchedDeliveryNotification and sends this to SAPNetWeaver. SAP NetWeaver maps the XML message to the customer'smessage format and sends it to the customer's backend system.

� ReceivedDeliveryNotification

When the customer receives the delivery, he or she sends the goods receiptinformation with a message from his or her backend system to SAPNetWeaver. SAP NetWeaver maps the message to an XML message of typeReceivedDeliveryNotification and sends it to SAP SNC. SAP SNC updatesthe ASNs on the basis of the XML message ReceivedDeliveryNotification.

If the customer uses an SAP system as the backend system, the backend systemsends and receives messages in IDoc format. An ASN is mapped to an inbounddelivery in the SAP backend system. In the standard system, SAP deliver XSLTmappings for the following ASN IDocs:

� SAP ERP 6.0 and higher: DELVRY05� For lower releases: DELVRY03

ASN StatusSAP SNC sets the status of an ASN item or an ASN automatically, depending onthe function you or SAP SNC performed beforehand in relation to the ASN. Thestatuses are of particular relevance to the progress of the delivery. At item level,the statuses show whether a goods receipt has been created for an ASN item orwhether the customer regards an item as closed, even if the supplier has onlydelivered a partial quantity. SAP SNC determines the status of the ASN headerfrom the status of the individual items.

Status of the ASN HeaderStatus Triggering FunctionDraft The supplier has saved the ASN as a draft.

An ASN with this status is not yet binding. It is still inplanning at the supplier. SAP SNC has not yet sent theASN to the customer as an XML message. Customerscan only see the ASN in the ASN overview. The supplieris able to change the draft ASN at any time.

Published The supplier has published the ASN.In the standard delivery, the supplier can notchange a published ASN on the SAP SNC Web UI.



Partial goods receipt The customer has confirmed a partial goods receipt.Therefore, the supplier has not yet delivered all itemsfrom the ASN . With this status, individual (but not all)items can also be delivered in full and thus have thestatus Goods Receipt Complete. The ASN can no longerbe changed.

Closed The customer has confirmed that all ASN items areclosed, even if the supplier has not delivered anythingor has only delivered partial quantities. The ASN canno longer be changed.

Goods receiptcomplete

The customer has confirmed a complete goods receipt.

The supplier has delivered all items from the ASN infull. The ASN can no longer be changed.

Canceled The supplier has canceled the ASN manually in SAPSNC.SAP SNC no longer takes account of an ASN withthis status during planning or in further process steps.However, the ASN is retained in SAP SNC. The ASNcan no longer be changed.

Status of the ASN ItemsStatus Triggering FunctionDraft The supplier has saved the ASN as a draft.Published The supplier has published the ASN.Partial goods receipt The customer has confirmed that the supplier has already

delivered a partial quantity for this item.Goods receiptcomplete

The customer has indicated that he or she has receivedthe entire item quantity.

Closed The customer has indicated that he or she has not yetreceived a delivery for the item or has only received apartial delivery, but he or she accepts this.

Canceled The supplier has canceled the ASN.

RoundingIf you have set up a rounding value for the location product, SAP SNCautomatically rounds up quantities to a whole-numbered multiple of the roundingvalue.



If you want to round the item quantities of a draft ASN in ASN processing,select the ASN items and choose Round. SAP SNC rounds up each item quantityaccording to the rounding value set for each location product.

Draft ASNIf you create and save an ASN in SAP SNC but do not yet want to send it tothe customer, you can save the ASN as a draft. You can continue processing orcancel the ASN at any time.

The consequences of saving the ASN as a draft are as follows:

� If you have only entered either a delivery date or only a shipping date, SAPSNC performs scheduling automatically.

� SAP SNC performs an internal validation.� The ASN acquires the Draft status.� The customer can see the draft ASN in the ASN overview as a draft.

However, SAP SNC does not send the ASN to the customer system.� SAP SNC includes the ASN in the due list for planned receiptsl however,

SAP SNC does not change any quantities. SAP SNC does not reduce thequantity of planned receipts and does not increase the in-transit quantity.

Publishing ASNIf you want to send an ASN that you created or changed in SAP SNC to thecustomer�s backend system, you must publish the ASN in SAP SNC.



The consequences of publishing the ASN are as follows:

� If you have only entered either a delivery date or only a shipping date, SAPSNC performs scheduling automatically.

� SAP SNC performs an internal validation.

If the data for a newly created ASN is complete and correct, the ASNacquires the Published status and SAP SNC sends the ASN to thecustomer. To do so, SAP SNC generates an XML message of typeespatchedDeliveryNotificationD. This goes to the customer�s backendsystem via SAP NetWeaver.

In the standard system, SAP SNC sends the XML message in the backgrounddirectly. However, you can also change the configuration so that SAP SNCuses the Post Processing Framework (PPF) to send the XML message.

� If the data contains errors, the affected, incorrect ASN sub-objects (ASNheader or ASN item) acquire the Invalid validation status in the standardsystem and the ASN acquires (or retains) the Draft status. To be able topublish the ASN, you must first correct the data. For publishing, all ASNsub-objects must have the Valid validation status.

Hint: In Customizing for Validation, the system administrator canspecify which validation status a sub-object acquires on publishing,depending on the validation result.

� SAP SNC automatically updates the In Transit and Planned Receipts keyfigures. For more details please see the SMI Unit of this course.

� In the standard system, the supplier cannot change a published ASN.

Sending ASNs from the Supplier System to SAP SNCThe supplier can create an ASN in his or her backend system and send it withan XML message DespatchedDeliveryNotification directly to SAP SNC. SAPSNC forwards the ASN (XML message DespatchedDeliveryNotification) to thecustomer�s backend system.

Caution: The IDocs, XML messages, and mappings depend on whichERP system and release is being used. Mappings are sometimes requiredfor the message flow between the supplier�s system and SAP SNC,depending on the supplier�s system. Since the mappings are dependent onthe supplier�s system, they cannot be predefined in the SAP SNC standarddelivery. You must create the mappings as part of a project solution.



Canceling ASNsIf you, as supplier, want to revoke a draft ASN or a published ASN, you cancancel the ASN manually in the SAP SNC ASN overview.

You can only cancel the ASN if the ASN does not yet have the status GoodsReceipt, Partial Goods Receipt, or Closed. Therefore, the customer must not yethave posted a goods receipt for the ASN or closed the ASN.

The consequences of canceling the ASN are as follows:

� The ASN acquires the status Canceled.� The ASN still exists in SAP SNC; however, SAP SNC no longer takes

account of the ASN in planning or for other functions.� You cannot change a canceled ASN.

Hint: In the standard system, the cancellation can only be seen in SAPSNC. SAP SNC does not send a message to the customer's backendsystem. If you want to send cancellation ASNs to an SAP backend system,apply SAP Notes 923705 and 924151.

Update ASNsTo make it possible for your supplier to always see current data in SAP SNC, you,as customer, must update the published ASNs regularly in SAP SNC in accordancewith the delivery progress. To do so, you supply SAP SNC with data for thedelivery receipt and for the goods receipt. In doing so, you update the status of theASN items, the status of the ASN, the quantity in transit, and the stock on hand inSAP SNC. You thus allow the supplier to perform planning in accordance with thedemands in the supplier-managed inventory (SMI) scenario, for example.

Confirming Partial Goods ReceiptsYou, can use XML messages to inform SAP SNC that you have received a partialdelivery for an ASN item from your supplier. The ASN item can thereby acquirethe status Partial Goods Receipt in SAP SNC. SAP SNC takes the deliveredpartial quantity from the quantity in transit and puts it into the warehouse stock.If an item in the ASN has the status Partial Goods Receipt, the ASN header alsoacquires the same status.



SAP SNC sets the goods receipt status of an ASN item based on the Customizingsettings, as follows:

� If partial goods receipt is allowed, an ASN item only acquires the statusGoods Receipt Complete if the goods receipt quantity is the same as theitem quantity. If the gods receipt quantity is less, the ASN item acquires thestatus Partial Goods Receipt. If you want to set the Goods Receipt Completestatus in spite of the partial delivery, you have to do so manually on theSAP SNC Web UI.

� If partial goods receipt is not allowed, SAP SNC sets the goods receipt statusGoods Receipt Complete for the item, even if the supplier has only delivereda partial quantity for an item.

Hint: Be careful when using the option for partial goods receipt. Asmentioned above, the only way to set the status of an ASN to GoodsReceipt Complete in case you received 99 out of 100 pc would be tomanually set this status in the SAP SNC Web UI.

Caution: Partial goods receipt means that in your business, you willperform two or more goods receipt postings on one itemwithin onedelivery.

The following cases do normally not require partial goods receiptcustomizing:

� You have inbound deliveries / advanced shipping notifications withmultiple items. The goods receipt postings for the different itemswill happen at different points in time. There is only one goodsreceipt posting per item.

� The requested quantity of a purchasing document (for example, apurchase order item) is delivered with multiple shipments. In thiscase you have multiple deliveries / ASNs.

� Part of a delivery is not accepted and you want your supplier toresend the remaining quantity. In this case, the new shipment will bea new ASN / inbound delivery.

All the above situations are often considered as partial goods receipt .However, only the situation of a partial goods receipt within one item ofan inbound delivery / ASN qualifies.

XML Messages for Updating ASNsAs customer, you can update ASNs in SAP SNC by sending data for goods receiptfrom your backend system to SAP SNC using electronic messages. The messagesgo to SAP NetWeaver first. SAP NetWeaver maps the messages to SAP XMLmessages and sends them to SAP SNC.



You can use the following XML messages (depending on the specific scenario):

� ReceivedDeliveryNotification� ProductActivityNotification� DeliveryScheduleNotification

The following provides an overview of the properties of the XML messages thatare relevant to updating ASNs in SAP SNC.

ReceivedDeliveryNotificationYou can use this message to transfer the ASN number and the ASN itemnumbers. You can transfer the following data for each item:

� Product number� Quantity received� Difference to the notified quantity� Information about whether the delivery is complete as far as the

customer is concerned, even if he or she has received a smaller quantitythan the notified quantity

Since a, XML message ReceivedDeliveryNotification is able to transferdetailed data at item level, you can map partial goods receipts in SAP SNC.An XML message ReceivedDeliveryInformation contains a Completedindicator. If this indicator is set, the item is given the status Goods ReceiptComplete, regardless of the goods receipt quantity in SAP SNC.

Caution: The IDoc technology of an SAP backend system doesnot support this indicator.

ProductActivityNotificationYou can use this message to transfer only the ASN number and the ASNitem numbers as ASN-relevant information. This message cannot transferdetailed data at item level. This means that if you use this message, youcannot map partial goods receipts in SAP SNC.



DeliveryScheduleNotificationUse this message to transfer scheduling agreement releases. SAPrecommends that you use XML message ReceivedDeliveryNotificationsas standard for release processing with SAP SNC to update ASNs in SAPSNC. Alternately, you can also work without ReceivedDeliveryNotificationsand instead transfer cumulative received quantities with XML messageDeliveryScheduleNotifications. In this case, you can specify that SAP SNCsets the goods receipt status of ASN items based on the cumulative receivedquantity.

Note: For more information, see the Implementation Guide (IMG)for ASN Processing: IMG→ Supply Network Collaboration→Delivery→ ASN→ Goods Receipt→ Define Settings for ReleaseProcessing.

Updating ASNs with an SAP backend SystemWhen you use an SAP backend system, you have various possibilities to updateadvanced shipping notifications with goods receipt data in SAP SNC, dependingon the type of delivery processing in the backend system.



Goods Receipt in the SAP backend System for Inbound DeliveryIn this scenario you transfer ASNs from SAP SNC to the SAP backendsystem. There, you create an inbound delivery for an ASN (transactionVL31N) and create the goods receipt reference to the inbound delivery. Youhave the following options when updating ASNs in SAP SNC:

� Transfer proof of delivery in XML message ReceivedDeliveryNo-tification

Here you configure the SAP backend system so that it automaticallycreates a proof of delivery at goods receipt and sends it to SAP SNC asan XML message ReceivedDeliveryNotification via SAP NetWeaver.The ReceivedDeliveryNotification is able to transfer detailed goodsreceipt data at item level. Depending on the goods receipt data, SAPSNC updates the status of the ASN item, the in-transit quantity, andthe stock on hand. You can process partial goods receipts in SAP SNCwith XML message ReceivedDeliveryNotifications.

� Transfer goods receipt data using report RSMIPROACT and XMLmessage ReceivedDeliveryNotification

Here you configure the SAP backend system so that it does notgenerate a proof of delivery at goods receipt. To transfer goods receiptdata to SAP SNC, use report RSMIPROACT. The system transfers thegoods receipt data with an XML message ReceivedDeliveryNotificationto SAP SNC via SAP NetWeaver.

� Transfer goods receipt data using report RSMIPROACT and XMLmessage ProductActivityNotification

Here you do not generate proofs of delivery in the SAP backend system.To transfer goods receipt data to SAP SNC, use report RSMIPROACT.However, you do not transfer the data to SAP SNC in an XMLmessage ReceivedDeliveryNotification, but in an XML messageProductActivityNotification. Since a ProductActivityNotification doesnot transfer any quantities at item level, you can only map completegoods receipts in SAP SNC. SAP SNC therefore sets the status GoodsReceipt Complete for an ASN item, even if the supplier has onlydelivered a partial quantity.



Release Processing Without Inbound DeliveryIn release processing, you procure your products via schedulingagreement releases that you send to SAP SNC as a XML messageDeliveryScheduleNotification. The supplier creates ASNs for schedulingagreement releases in SAP SNC, and you transfer them to the SAP backendsystem. We recommend that you also process goods receipts in the SAPbackend system on the basis of inbound deliveries in release processing.Alternately, you can also work without inbound deliveries; in other words,you do not send back any ReceivedDeliveryNotifications to SAP SNC.If, in this scenario, you also want to update ASN items in SAP SNCautomatically, you have to specify that SAP SNC update ASN items basedon the cumulative received quantities that you transfer to SAP SNC usingscheduling agreement releases.

Note: For more information, see the Implementation Guide forSupply Network Collaboration: Delivery→ ASN→ Goods Receipt→ Define Settings for Release Processing.

Overview of Processing Goods Receipt Data from SAPR/3The following table contains an overview of how SAP SNC processes the goodsreceipt data that you transmit in various processes and with various messages. ThePartial GR column shows whether you can map partial goods receipts in SAP SNC



Trigger IDocType forGoodsReceiptRefer-ence

Transac-tion for GRPosting

Transmit-ted Data forGR Refer-ences

Interpre-tationThroughSAP SNCInboundProcessing

Par-tialGR

ReportRSMIPROACT

PROACT01VL32NwithoutPODprocess inplace

ASN ID,ASN itemID, no GRquantities,no materialnumbers

GoodsReceiptCompletestatus for theASN item

No

ReportRSMIPROACT

PROACT01MIGO.GoodsreceiptwithoutreferencingASN.The deliverynumber forthe ASNID wastaken froma printeddeliverynotification,for example.

ASN ID,ASN itemID, no GRquantities,no materialnumbers

GoodsReceiptCompletestatus for allASN itemscontaininga materialthat is alsopart of thetransmissionof thisPROACTmessage.

No



ReportRSMIPROACT

DELVRY03 VL32NwithoutPODprocess inplace

ASN ID,ASN itemID, GRquantities,deltaquantitiesbetweenGR quantityand ASNquantity,materialnumbers

GoodsReceiptCompleteor PartialGoodsReceiptstatus for theASN items

Yes

ReportRSMIPROACT

DELVRY03 MIGO.GR withoutreference toASN itemsThe deliverynumber forthe ASNID wastaken froma printeddeliverynotification,for example.

ASN ID, noASN itemID, no GRquantities,materialnumbers

GoodsReceiptCompletestatus for theASN itemscontainingthe products

Yes *

POD Process DELVRY03 VL32Nwith PODprocess inplace

ASN ID,ASN itemID, GRquantities,deltaquantitiesbetweenGR quantityand ASNquantity,materialnumbers

GoodsReceiptCompleteor PartialGoodsReceiptstatus for theASN items

No

* Since in this case no ASN item ID is transmitted, SAP SNC searches for thecorresponding ID using the material number. Prerequisite: There is only one ASNitem for the material number in the ASN.



ASN AlertsThe following options are available to generate an ASN alert, depending on thealert type:


� System administration executes a report regularly in the SAP SNC system.To call the report for online processing from the SAP Easy Access screen,choose Supply Network Collaboration→ Exceptions→ Alert Generation→<Report>.

� SAP SNC generates the alert during validation of the purchase order. Systemadministration can deactivate alert generation in Customizing for validation.

The following list contains the alert types for ASN processing in SAP SNC.

Exception during validation of ASN (alert ID 7033)The validation has detected missing or incorrect data in the ASN.This alert might be of special interest for monitoring errors in the XMLinbound processing for ASNs (XML message ReceivedDeliveryNotification).

Overdue ASN (alert ID 0031)SAP SNC system administration generates the ASN alerts with report/SCA/ASN_PASTDUE_ALERTWRITE. For the report, an ASN isregarded as overdue if the ASN fulfills the following conditions:

� The delivery date lies, at latest, on a date defined by the user (specifieddate plus offset in days).

� The supplier has not yet delivered all items in full. However, ASNs orASN items with the status Closed are regarded delivered in full.

Goods receipt quantity differs from ASN quantity (alert ID 0032)The goods receipt quantity for an item in the ASN differs from the requesteditem quantity in the ASN.This alert is generated by PPF (application /SCA/ICH, action profile/SCA/BOL_DELIVERY, action /SCA/BOL_DLV_GRQUAN_CHECK).



Lesson Summary

You should now be able to:� Explain ASN processing in SAP SNC� Name the ASN alerts



Lesson: Packing

Lesson OverviewThis lesson will introduce you to the details of the packing functionality withinSAP SNC ASN processing.


� Discuss the packing functionality in SAP SNC ASNs� Explain the difference between automated and manual packing

Business Example

BackgroundYou can use the packing function to pack the items of an advanced shippingnotification (ASN) into handling units (HU). A handling unit represents a unitconsisting of the products and the packaging materials into which the products arepacked. The result of packing is one or more handling units. You can also packthe handling units into other handling units.

ExampleA wire basket contains two big boxes, and each big box contains four small boxes.Each small box contains four pieces of the product being delivered. As packagingmaterial, you use wire baskets, big boxes, and small boxes, and as auxiliarypackaging materials, you use steel binders and plastic film.

Figure 51: A small box can contain four pieces of the material


SNC100 Lesson: Packing

Figure 52: Small boxes may be packed into large boxes. A large box cancontain four small boxes.

Figure 53: Large boxes may be packed into wire baskets. A wire basketcan carry two large boxes.



Figure 54: A complete packed wire basket contains 32 pieces of the material.

In ASN processing, only the supplier can process ASNs and thus carry out packing.

You cannot pack items from different ASNs together.

Settings for Packaging1. You create a product master for each of the packaging materials and auxiliary

packaging materials that you want to use for single-level or multilevelpacking of a product. You assign the product master to the active model 000.

Note: Packaging materials and auxiliary packaging materials are notlocation-specific. Therefore, you do not have to define any locationproduct masters.

2. You specify the packaging materials in which a product or (in the case ofmultilevel packing) a packaging material can be packed.

3. If you want the system to take into account the packing capacity of apackaging material during packing, you set up the data that is relevant to thepacking capacity in the product masters of the packaging material and theproducts or packaging materials packed therein.

4. If you want to use automatic packing, set up internal number assignmentfor the handling units. You can use both internal and external numberassignment for manual packing.

5. If you want to use automatic packing, set up packaging specifications.

Consideration of the Packing CapacityDuring packing, the system automatically takes account of weight andvolume-related constraints and requirements for filling a handling unit (HU).These result from the attributes of the packaging material assigned to the HU. Thequantity that you can pack in a handling unit depends on the packing capacity of ahandling unit and the attributes of the objects to be packed (products or handlingunits).



You make the following settings in the product masters of the packaging materialsand the products to be packed:

� Settings for a product to be packed

In the product master of the product, enter the properties of the product(weight, dimensions, and volume) on the Units of Measure tab page relatedto a base unit of measure of the product. If required, define conversionsinto other units of measure.

� Settings for a packaging material

1. In the product master of the packaging material, enter the properties ofthe packaging material (weight, dimensions, and volume) on the Unitsof Measure tab page related to a base unit of measure of the packagingmaterial. If required, define conversions into other units of measure.

2. Choose Enter or save the product master. As a result, the system copiesthe gross weight and the volume automatically to the Properties tabpage (you cannot enter this data manually on the Properties tab page.)The system checks the data on the Packing Data tab page against thegross weight and the volume on the Properties tab page.

3. In the Capacities screen area on the Packaging Data tab page, enterthe control data for filling a HU that uses the packaging material. Thisincludes, for example, the maximum weight that can be packed in theHU or the packing volume of the packaging material.

SAP SNC automatically calculates the following weight data of a handling unitusing the weight data and units of measure in the product master of the products tobe packed and the packaging material:

Net weight of HU =product quantity in HU x gross weight of product per unit of measure

Gross weight of HU =gross weight of HU packaging material + net weight of HU

You can change the gross weight and the net weight manually on the Packagingscreen. The system automatically checks the packing capacity of an handlingunit based on the data in the product master of the packaging material. Youcannot pack more products into a handling unit than the packing capacity of thepackaging material allows.



Specification of the Permitted Packaging MaterialsYou use this process to define which packaging materials are permitted for packinga product or � and this is relevant for multilevel packing � a packaging material.This ensures that you or your supplier use the correct packaging materials inmanual packing or when creating a packaging specification. This process preventsincorrect packing.

1. Define the following keys in Customizing for SCM Basis. Choose Pack→ Handling Units.

� Packaging material types

A packaging material type is a key that you use to group alternatepackaging materials.

� Packing groups

In a packing group, you group the packaging material types that youpermit for packing a product in a packaging material or for packing apackaging material into a larger packaging material.

2. Enter the packaging material type in the product masters of the packagingmaterial and � if you want to pack the packaging materials into largerpackaging materials in multilevel packing � the packing group.

3. To specify the packaging material types that are permitted for packing aproduct, you enter the packing group in the location product master of theproduct.



Process for Manual PackingThis process describes, for example, how you pack the items of an ASN (that isnot yet published) on the packing screen, both manually and at multiple levels.

� The settings for packing have been made.� You are in the ASN details screen in create or change mode.

1. Call the packing screen in the ASN details screen by choosing Packing.2. Create your first HU hierarchy as follows:

For each packing level that you require for packing, create one empty HU onpacking level one. You do this in the HU � Hierarchical Viewscreen area. Ifyou have three packing levels, you must create three HUs. On creation, youenter the required auxiliary packaging materials for each HU. In the HU atthe innermost packing level, in addition to the auxiliary packaging materials,you pack the partial quantity of an ASN item that the HU can include.

Hint: Alternately, you can create these first HUs hierarchically (thatis, on the correct packing levels) immediately. In the case of threepackaging levels, therefore, you create the largest HU at packaginglevel one, the next smallest HU at packaging level two, and thesmallest HU at packaging level three.

You can use the cut and paste functions to multiply these first HUs andbuild the complete HU hierarchy successively. In other words, you build upa packaging unit packed on multiple levels that contains the product of anASN item.

3. If the HU hierarchy that you created in the last step is not sufficient forthe complete packing of a product, generate the required number of HUhierarchies for the remaining quantity. You can use cut and paste to dothis, too. You cut the HU hierarchy and paste as often as necessary at thepacking level.

4. If the ASN contains further items that you have to pack in a different way, forexample, using different packaging materials or in different quantities, yougenerate additional relevant HU hierarchies as described in the last steps.

5. In the ASN items screen area, check the packing status of the ASN items.The packing status shows whether you have already packed all items.

6. If you have packed all ASN items, print the HU labels and print the ASN asa delivery note.



Process for Automated PackingThis process describes how you automatically pack the items of an advancedshipping notification (ASN) that has not yet been published on the Packing screen.Automatic packing uses a packaging specification (PS) to pack an item.

1. In the ASN details, choose Packing to call the Packing screen.2. If several packaging specifications are assigned to a product and you do not

want automatic packing to use the packaging specification with the highestpriority, define the required packaging specifications for the ASN item in theASN Items screen area. The highest priority is 1.

3. To start automatic packing, select the ASN items to be packed and chooseAutomatic Packing.

4. The system packs each item using the packaging specification that is definedfor the item. The system creates the required HUs and assigns the HUnumbers. The system displays the packing proposal in the HU � HierarchicalView screen area.

5. Check the packing proposal. In the ASN Items screen area, the packing statusshows you whether the system has completely packed the items.

6. If required, process the packing proposal using the functions for manualpacking. For example, you can unpack HUs again or overwrite the HUnumber that the system has assigned to a handling unit in automatic packing.

If you are satisfied with the packing proposal, save the ASN draft bychoosing Save ASN/Draft.

7. If you have packed all ASN items, print the HU labels and print the ASN asa delivery note.

Packaging SpecificationA packaging specification is a rule that specifies how products are to be packed inhandling units (HUs), for example, for shipment to the customer.

A packaging specification (PS) describes which product quantities should bepacked, and which packaging materials and auxiliary packaging materials shouldbe used for this purpose. You can use a PS to model packing on single or multiplelevels.

The packaging specification forms the basis of automatic packing. In automaticpacking, the system automatically generates a proposal (with a PS) as to howyou pack an item of an advanced shipping notification (ASN) into HUs.Packaging specifications can be set up for a product by the customer and �with the appropriate authorization from the customer � by the supplier. Thecustomer can define which packaging specification a supplier may use. You canuse product-specific packaging specifications for a product or assign packaging



specifications to the product by means of the reference product. It is not possibleto link packaging specifications. A packaging specification cannot, therefore,refer to another packaging specification.

Product-specific packaging specificationA product-specific packaging specification is created specially for a specificproduct. Therefore, you can only use the packaging specification for thisproduct.

PS for a reference productIf you want to pack different product variants in the same way, you do nothave to create a separate PS for each product. Instead, set up a PS for areference product. Assign the reference product (in the product master) andthe packaging specification of the reference product (in the PS assignment)to the product for which you want to use the packaging specification ofthe reference product.

Alternate packaging specificationsYou can assign a product several alternate packaging specifications withdifferent priorities. By default, automatic packing uses the PS with thehighest priority (the highest priority is 1). As a supplier, you can manuallyselect the PS to be used before you call up automatic packing.

PS Status, PS Versions, and PS Change NumberThe status of a newly created PS is New. To be able to use the PS for automaticpacking, you must first activate the PS and then set the PS status to Active. Youcannot change an active PS. You have the following options to change a PS:

� Deactivate a PS and then edit it. The status of a deactivated PS is Inactive,making it unavailable for automatic packing. Automatic packing can onlyuse the PS again only after you have made the changes and reactivated it.

� Generate a second, inactive version of an active PS which you can then edit.The status of the second PS version is Inactive, enabling it to be edited. Theoriginal version remains active and can continue to be used for automaticpacking. When you have finished editing the second version, you canactivate it. Only then will SAP SNC delete the original version.

SAP SNC marks the two versions of a PS that may simultaneously be present inthe system using PS change numbers 1 and 2. The non-editable active versionis always marked as PS number 1. The version that can be edited is marked asPS change number 2.

On the editing screen for packaging specifications, the functions Activate,Deactivate, and Create 2nd Version are available for a PS, depending on the PSchange number. For example, the Activate function is no longer available for adeactivated PS. If you want to activate a PS that you have already deactivated,create a second version of the PS and activate the second version.



PS StructureA packaging specification consists of the following elements:

� The packaging specification levels (PS levels) describe the various packaginglevels.

� You use the PS level elements to describe the packaging materials that youuse for a PS level.

� The PS content describes which products you pack in which quantity ratio inthe smallest packaging unit of the packaging specification.

Packaging Specification LevelThe packaging specification level is part of a packaging specification (PS) thatdescribes a packaging level.

A PS level contains, for example, data for the quantities that SAP SNC is to packin this packaging level in automatic packing.

You can use various PS levels to describe the various packaging levels. Numberthe PS levels in the sequence of the packaging levels. Use the PS level withthe lowest number to describe the smallest packaging unit, in other words, theinnermost packaging level. You only require higher PS levels in multilevel packingif you want to pack the smallest packaging units into larger packaging units.

Note: For example, If you want to pack boxes with indicators into meshbox pallets, you require two PS levels. The first PS level describes thepacking of indicators into the boxes; the second PS level describes thepacking of the filled boxes into mesh box pallets.

PS Level StructureA PS level contains fields for the target quantity, the rounding quantity, and theminimum quantity. You use this data to control which quantities of products orpackaging units SAP SNC packs in a packaging level during automatic packing.The target quantity, rounding quantity, and minimum quantity are numbers withoutdimensions. On the lowest PS level, they represent a number of PS contents. Ona higher PS level, they represent a number of packaging units from the lowerpackaging level. The following table contains a description of the individualquantity fields.



Field DescriptionTarget Quantity Maximum number that SAP SNC can pack in a PS level.

Example: The PS content consists of a right and a leftindicator. On the first packaging level, you want to pack oneright and one left indicator in a box. Therefore, you entertarget quantity 2 for PS level 1. If you want to pack 1000of these boxes on the second packaging level in a mesh boxpallet, enter the target quantity 1000 for PS level 2.

MinimumQuantity

Minimum number that SAP SNC must pack in a PS level.If SAP SNC does not reach the minimumquantity for a PS level during automatic packing,SAP SNC terminates packing for this level.Example: If you have to put at least 200 boxes in the meshbox pallet, you specify the minimum quantity 200 for PSlevel 2.

RoundingQuantity

Number whose multiple SAP SNC must pack.A remaining quantity, which is smaller than the roundingquantity, remains unpacked in automatic packing.Example: You always want to put complete layers in themesh box pallet. A layer holds 100 boxes. In this case, youspecify the rounding quantity 100 for PS level 2. For 370boxes, SAP SNC only packs 300 pieces. The remaining70 are not packed.

Total quantity of a product in a handling unit packed on multiple levelsThe total product quantity that can be packed in a handling unit packed onmultiple levels is the product quantity that you entered in the PS content,multiplied by the target quantities that you entered for the PS levels.If the PS content consists of a right and a left indicator, and target quantitiesof two and 1000 are entered for PS levels 1 and 2 respectively, a fully packedHU contains 2000 right and 2000 left indicators (2000 = 1×2×1000).

Data for the properties of a packaging unitSAP SNC calculates the volume and weight of a packaging unitautomatically, using the data from the product masters of the packagingmaterials, auxiliary packaging materials, and the packed products.You cannot change the data at the PS level.The height, length, and width of a handling unit also come from the productmaster of the main packaging material.You can change this data.



HU creation indicatorSet the HU Creation indicator for a PS level if you want the system toautomatically generate an HU for the PS level during automatic packing. Thesystem generates the HU that is marked as the main packaging material forthe PS level element. If no PS level element is marked as the main packagingmaterial, SAP SNC does not generate an HU for the PS level.

Element groupThe PS level displays the number of the element group. The element groupis automatically generated by the system and contains the PS level elementof the PS level. Element groups simplify assigning PS level elements toa PS level.

Packaging Specification Level ElementThe packaging specification level element is part of a packaging specification (PS)that specifies a packaging material that you require for a PS level.

In addition to the product number, the PS level element for the packaging materialalso contains the necessary packaging material quantity.

You define a PS level element for each packaging material or auxiliary packagingmaterial that you require in a PS level. Number the PS level elements in thesequence in which the employee performing packing has to process the packagingmaterials or auxiliary packaging materials. In addition, specify the relevance forhandling units for each element. The main packaging material of the PS leveldetermines the packing capacity and the properties of a handling unit. Theseinclude the weight, volume, and the dimensions. The system adopts this data inthe handling unit data.

The system automatically generates an element group for the PS level elements ofa PS level. Element groups simplify assigning PS level elements to a PS level.

Example

For the first PS level, one box, one liter of padding, and 20 centimeters of adhesivetape are required. Thus there are three PS level elements for the PS level. Thepacker takes a box, puts the indicators in the box, adds the padding, and then usesthe adhesive tape to seal the box. The PS level elements for the box, padding, andadhesive tape have the numbers 1, 2, and 3, respectively. Using the HU Relevancefield, you classify the box as the main packaging material, the padding as theauxiliary packaging material, and the adhesive tape as Not relevant for HUs.

Packaging Specification ContentThe packaging specification content is part of a packaging specification thatcontains the products to be packed.



The PS content contains the following fields:

� In the Content Sequence field, you specify the sequence in which the packermust pack the products. Assign the lowest number to the product that is tobe packed first.

� In the Quantity and Unit of Measure fields, you specify the base quantitythat you want to pack for a product. The system uses the base quantity andthe target quantity that you have specified for the PS level with the lowestnumber to automatically calculate the maximum product quantity that thesmallest packaging unit must include.

Product Quantities in the Smallest Packaging UnitThe smallest packaging unit of a packaging specification contains the products tobe delivered. You control which and how many products the system packs intothe smallest packaging unit as follows:

� In the PS content, specify the products and the quantity ratio of the products.To do so, enter a base quantity for each product.

� If the PS content only contains one product, it is recommended that youenter 1 as the base quantity. You control the actual quantity in thesmallest packaging unit using the target quantity of the PS level for thesmallest packaging unit.

� In the case of several products, enter small whole numbers that reflectthe quantity ratio of the products in the smallest packaging unit.

� Use thetarget quantity , rounding quantity, and minimum quantity inthe PS level for the innermost packaging level to control which productquantities the system actually packs in the smallest packaging unit. Thesequantities are nondimensional factors with which the system multiplies thebase quantities in the PS content. This results in the actual target quantity,the actual rounding quantity, and the actual minimum quantity.

Examples

Pack indicators with a ratio of 1:1If you want to pack a right indicator and a left indicator in a box, you enterboth the right and the left indicator with quantity 1 in the PS content. Enter 1as the target quantity in the PS level for the innermost packaging level. If youwant to pack 10 right and 10 left indicators in a box, you also enter 1 for thequantities in the PS content. Enter 10 as the target quantity in the PS level.

Pack indicators with another quantity ratioIf you want to pack 10 right and 20 left indicators in a box, enter the quantity1 for the right indicator and the quantity 2 for the left indicator in the PScontent. Enter 10 as the target quantity in the PS level.



Lesson Summary

You should now be able to:� Discuss the packing functionality in SAP SNC ASNs� Explain the difference between automated and manual packing


SNC100 Lesson: Process Demo: ASN Processing

Lesson: Process Demo: ASN Processing



� Perform ASN processing in SAP SNC

Business Example

Figure 55: Demo





Exercise 4: ASN Processing with SAP SNC

Exercise ObjectivesAfter completing this exercise, you will be able to:� Run an ASN processing (with Packaging) scenario with SAP SNC

Business ExampleAs part of delivery processing, your supplier creates an advanced shippingnotification (ASN) in SAP SNC with reference to a purchase order or a schedulingagreement release. The supplier also uses the automatic packaging function topack the shipped goods according to a predefined packaging specification. TheASN is sent to your back-end ERP system. A corresponding inbound delivery iscreated in the ERP system, for which you can post the goods receipt. The goodsreceipt information is posted back to SNC and updates the status of the ASN.

Task 1: Create Packaging Specification in SAP SNC

Hint: You will create the packaging instruction in the role of the customer.In SNC both partners can create the packaging specification but in yourtraining system authorization are setup in that way that only the customeris authorized to create a packaging specification.

Log on to the SNC customer view (user SNC100-##) and define a packagingspecification for your supplier to use for automatic packaging of the goods.

1. Log on to the customer view of SAP SNC and navigate to the PackagingSpecification Details screen.

2. Create a packaging specification for product T-C100-##.

4 pc of the product shall be packed into one unit of packaging materialT-Z100-##.

Task 2: Assign Packaging Specification to ProductPacking specifications must be assigned to any combination of partner (customeror supplier), product, partner product, or applicable PS priority. Assign yourpackaging specification to the product.

1. In the customer view of SNC, assign your newly created packagingspecification to supplier SNC100A-## and product T-C100-##.




Task 3: Create an ASN for a Purchase Order in SAPSNC

Hint: In this step you again jump into the role of the supplier. Thus logonto SAP SNC with user IU-SUPA## and open the supplier view WebUI.

Create an advanced shipping notification in SNC for the purchase order youcreated in the Purchase Order Collaboration with SAP SNC exercise. Publish theASN so that it is sent to the ERP system.

1. Find the purchase order from the Purchase Order Collaboration exercise

2. Create an ASN with reference to this purchase order.

Caution: Do not publish the ASN. You will perform packing beforepublishing.

Task 4: PackingAs part of the ASN creation process, the supplier packs the components into theappropriate packaging material. Use the automatic packing function to pack thematerials according to the assigned packaging specification (PS_SCN##). Oncethe materials are packed, publish the ASN.

1. Use the automated packaging function to pack the ASN.

2. Once the ASN item is packed completely, publish the ASN to the SAP ERPsystem.

Task 5: Check Inbound Delivery in ERP

Hint: This task is performed in the role of the customer. Using the userSNC100-## in the ERP System.

Check the inbound delivery in the ERP system and write down the inbounddelivery number.

1. Log on to ERP as the purchaser and check for the corresponding inbounddelivery for the ASN. Write down the inbound delivery number.

Task 6: Post Goods Receipt for Inbound Delivery inERPNow that you have found the inbound delivery, continue booking a goods receipt.

1. Post a goods receipt to your ASN (inbound delivery)




Task 7: Check Status of ASN in SNCLog on to SNC as the supplier and check the status of the ASN. What is theheader status?

Hint: This task is performed in the role of the supplier thus logon toSAP SNC with user IU-SUPA##.

1. Log on to SNC as the supplier and check the status of the ASN. What isthe header status now?

Task 8: Check Status of the PO in SNCHow is the goods receipt information reflected in the PO?

1. How is the goods receipt information reflected in the PO?

Task 9: Create an ASN for a Scheduling Agreementin SAP SNCCreate an ASN for a scheduling agreement in SAP SNC.

Hint: Remember that the scheduling agreement releases have been placedfor the Supplier SNC100B-##, thus you need to logon to SAP SNC withuser IU-SUPB## for this task.

1. Create an ASN for a scheduling agreement in SAP SNC.

Task 10: Post Goods Receipt for Inbound Delivery inERPBack in ERP find the inbound delivery which corresponds to the ASN you havejust created and book a goods receipt.

Hint: This task is performed in the role of the customer with userSNC100-## in the ERP System.

1. Find the inbound delivery and book the goods receipt like you did in thetasks 5 and 6 before.



Solution 4: ASN Processing with SAP SNCTask 1: Create Packaging Specification in SAP SNC

Hint: You will create the packaging instruction in the role of the customer.In SNC both partners can create the packaging specification but in yourtraining system authorization are setup in that way that only the customeris authorized to create a packaging specification.

Log on to the SNC customer view (user SNC100-##) and define a packagingspecification for your supplier to use for automatic packaging of the goods.

1. Log on to the customer view of SAP SNC and navigate to the PackagingSpecification Details screen.

a) Log on to the SCM System with user SNC100-##.

b) Call the the customer view of SAP SNC. To do so call the transactionSNC Customer View which can be found in the Easy Access menuunder Supply Network Collaboration→ Web UIs for SAP SNC→Special Views→ Supplier Collaboration.

c) In the SAP SNCWeb UI chooseMaster Data→ Packing→ PackagingSpecification Details

2. Create a packaging specification for product T-C100-##.




4 pc of the product shall be packed into one unit of packaging materialT-Z100-##.

a) On the Packaging Specification Details screen, choose Create andenter the following data:

Packaging Specification Group: SNC – Pack. Spec.Group Packaging

Specification Identifier: PSSNC##Packaging Specification Description: Pack. Spec.Group ##

b) On the Content tab page, make the following entries:Cont. Seq. No.: 1Product: T-C100-##Quantity: 1

c) On the Level tab page, make the following entries:Level Sequence No.: 1Target Quantity: 4Minimum Quantity: 1HU: Checked

d) In the Related Elements area, choose Add Element and make thefollowing entries:

Elem. Seq. No.: 1Packaging Material: T-Z100-##HU-Relevance: 1Quantity: 1

e) Choose Check to check the correctness of the packaging specification.

f) Choose Save. The status of the packaging specification is New.

g) Choose Activate. The status is now Active.




Task 2: Assign Packaging Specification to ProductPacking specifications must be assigned to any combination of partner (customeror supplier), product, partner product, or applicable PS priority. Assign yourpackaging specification to the product.

1. In the customer view of SNC, assign your newly created packagingspecification to supplier SNC100A-## and product T-C100-##.

a) In the SNC customer view, choose Master Data→ Packing→ AssignPackaging Specification.

b) ChooseCreate/Change PS Assignments, then choose Insert line. Makethe following entries:

Supplier: SNC100A-##Product: T-C100-##Sequence Number: 0001Packaging Spec: PSSNC##

c) Choose Save all Changes.

Task 3: Create an ASN for a Purchase Order in SAPSNC

Hint: In this step you again jump into the role of the supplier. Thus logonto SAP SNC with user IU-SUPA## and open the supplier view WebUI.

Create an advanced shipping notification in SNC for the purchase order youcreated in the Purchase Order Collaboration with SAP SNC exercise. Publish theASN so that it is sent to the ERP system.

1. Find the purchase order from the Purchase Order Collaboration exercise

a) Log on to SNC as the supplier (IU-SUPA##).

There are several choices of how you can navigate to the ASN creationon the basis of the purchase order:

� In the supplier view, choose Purchase Order→ Purchase OrderDetails. Enter your purchase order number and choose Go.

� In the supplier view, choose Delivery → Receipts andRequirements→ Due List for Purchasing Documents. On theDue List for Purchasing Documents screen, enter the customerlocation 1000 and choose Go. The purchase order you createdappears as due for delivery.

2. Create an ASN with reference to this purchase order.




Caution: Do not publish the ASN. You will perform packing beforepublishing.

a) Once you have found the correct PO, choose Create ASN or CreateASN for Items.

b) On the ASN maintenance � Create ASN screen, check the details ofthe ASN and enter an ASN number (for example, ASN##_01 where## is your group number).

c) Choose Check to validate ASN.

Caution: Do not publish the ASN. You first will do thepacking in the next exercise step before publishing.

Task 4: PackingAs part of the ASN creation process, the supplier packs the components into theappropriate packaging material. Use the automatic packing function to pack thematerials according to the assigned packaging specification (PS_SCN##). Oncethe materials are packed, publish the ASN.

1. Use the automated packaging function to pack the ASN.

a) On the ASN maintenance � Create ASN screen, select the item andchoose Packing.

b) On the ASN Packing screen, make sure that the pack spec identifier isfilled. Select the item and choose Automatic Packing.

You can see that the packed percentage is now 100% and, in the lowerhalf of the screen, you can see the handling units that have been created.

2. Once the ASN item is packed completely, publish the ASN to the SAP ERPsystem.

a) Choose Save ASN/Publish to send the ASN to the ERP system.




Task 5: Check Inbound Delivery in ERP

Hint: This task is performed in the role of the customer. Using the userSNC100-## in the ERP System.

Check the inbound delivery in the ERP system and write down the inbounddelivery number.

1. Log on to ERP as the purchaser and check for the corresponding inbounddelivery for the ASN. Write down the inbound delivery number.

a) From the SAP Easy Access menu, choose Logistics→ LogisticsExecution→ Inbound Process→ Inbound Delivery→ Change→Single Document or use transaction code VL32N.

b) Search for the inbound delivery using the input help (F4) and searchby the External Delivery ID (the ASN number you entered in SNC,for example, ASN##_01).

c) Write down the inbound delivery number. _____________




Task 6: Post Goods Receipt for Inbound Delivery inERPNow that you have found the inbound delivery, continue booking a goods receipt.


a) On the Shipping Notification 18XXXXXXX Change: Overview screenyou can see that the delivery is relevant for putaway, as the warehouseis subject to lean warehouse management. (Indicated by the letter Ain the field WM activities which you can find on header level usingthe button.

Choose Subsequent Functions→ Create Transfer Order. Confirmthe End of Dialog - Do you want to switchsubsequent functions? Dialog with Yes. On the CreateTransfer Order for Delivery Note: Initial Screen, select the processingoption Background for the field Foreground/Background and chooseEnter ( ). The system issues a message: Transfer orderXXXXXXXX created.

b) Return to the Change Inbound Delivery screen (Transaction VL32N).You can see that the putaway status is now Completely put away.

c) Choose the Post Goods Receipt button. The system issues a message:Shipping notification 18XXXXXXX has been saved.

d) If you now display the delivery (VL33N) and choose Extras→Delivery Output, you can see that a message of the type OPOD (VendorProof of Delivery) was issued when the goods receipt was posted.

Task 7: Check Status of ASN in SNCLog on to SNC as the supplier and check the status of the ASN. What is theheader status?

Hint: This task is performed in the role of the supplier thus logon toSAP SNC with user IU-SUPA##.

1. Log on to SNC as the supplier and check the status of the ASN. What isthe header status now?

a) Log on to SNC and choose Delivery→ Advanced Shipping Notification→ ASN Details.

b) Enter your ASN number and choose Go.

You can see the status of the ASN in the header area on the General tabpage. The status should now be GC - Goods Receipt Complete.




Task 8: Check Status of the PO in SNCHow is the goods receipt information reflected in the PO?

1. How is the goods receipt information reflected in the PO?

a) Either branch to the PO from the ASN Details screen (press thePurchasing Document button at item level) or navigate via the menu tothe Purchase Order Details screen.

You can now see that the PO Hdr Status has changed to DeliveryCompleted.

At schedule line level you can see a line ASN Confirmed showing thereceived quantity.

Task 9: Create an ASN for a Scheduling Agreementin SAP SNCCreate an ASN for a scheduling agreement in SAP SNC.

Hint: Remember that the scheduling agreement releases have been placedfor the Supplier SNC100B-##, thus you need to logon to SAP SNC withuser IU-SUPB## for this task.

1. Create an ASN for a scheduling agreement in SAP SNC.

a) Remember to logon as supplier SNC100B-## (user IU-SUPB##).

b) To create the ASN, on the Release Details screen select your scheduleline and choose Create ASN, then proceed in the same manner as forASN creation based on a purchase order.




Task 10: Post Goods Receipt for Inbound Delivery inERPBack in ERP find the inbound delivery which corresponds to the ASN you havejust created and book a goods receipt.

Hint: This task is performed in the role of the customer with userSNC100-## in the ERP System.

1. Find the inbound delivery and book the goods receipt like you did in thetasks 5 and 6 before.

a) From the SAP Easy Access menu, choose Logistics→ LogisticsExecution→ Inbound Process→ Inbound Delivery→ Change→Single Document or use transaction code VL32N.

b) Search for the inbound delivery using the input help (F4) and search bythe External Delivery ID (the ASN number you entered in SNC).

c) Write down the inbound delivery number. _____________

d) On the Shipping Notification 18XXXXXXX Change: Overview screenyou can see that the delivery is relevant for putaway, as the warehouseis subject to lean warehouse management. (Indicated by the letter Ain the field WM activities which you can find on header level usingthe button.

Choose Subsequent Functions→ Create Transfer Order. Confirmthe End of Dialog - Do you want to switchsubsequent functions? Dialog with Yes. On the CreateTransfer Order for Delivery Note: Initial Screen, select the processingoption Background for the field Foreground/Background and chooseEnter ( ). The system issues a message: Transfer orderXXXXXXXX created.

e) Return to the Change Inbound Delivery screen (Transaction VL32N).You can see that the putaway status is now Completely put away.

f) Choose the Post Goods Receipt button. The system issues a message:Shipping notification 18XXXXXXX has been saved.

g) If you now display the delivery (VL33N) and choose Extras→Delivery Output, you can see that a message of the type OPOD (VendorProof of Delivery) was issued when the goods receipt was posted.



Lesson Summary

You should now be able to:� Perform ASN processing in SAP SNC


SNC100 Lesson: Relevant Customizing for ASN Processing in SAP SNC

Lesson: Relevant Customizing for ASN Processing inSAP SNC

Lesson OverviewIn this lesson, you will learn about relevant customizing for ASN processingin SAP SNC.


� Describe the Customizing possibilities in ASN processing in SAP SNC� Set up message determination for this process

Business Example

Internal Number Assignment for ASNIf you set up internal number assignment for ASN, SAP SNC will generate theASN number automatically when saving the ASN in the Web UI.

Make the settings for internal number assignment on the SAP SNC Web UI. You can control internal number assignment, depending on the followingcharacteristics:

� Supplier� Customer� Ship-to location� Ship-from location

This means that you can set up SAP SNC to assign numbers from different numberranges for different suppliers.

Example

You can specify that your ASNs to customer LeClerc acquire a consecutivenumber between 1 and 1000 and that the system automatically prefixes thenumbers with the character string LC. When the number range interval is used up,SAP SNC should reuse the number range interval, starting again with number 1 innumber assignment (rolling number range interval). ASNs to customer Duboisacquire a consecutive number from the interval 1001 to 2000, with the prefix DU.



If you want to set number assignment for an object type (for example, for ASNs),do the following:

1. Define the number range attributes for the object type (for example, forASNs) in the Web application menu by choosing Master Data→ NumberRanges→ Number Range Attributes.

2. Define number range intervals for the object type (for example, for ASNs) inthe Web application menu by choosing Master Data→ Number Ranges→Number Range Intervals for <OBJECT TYPE> .

Note: If you want to modify number assignment, use the BAdI/SAPAPO/VMI_PO_NRGET.

Number Range AttributesNumber range attributes to control how SAP SNC uses the specific numbersand number range intervals in number assignment. You specify the numberrange attributes for each object type and each characteristics combination.The following characteristics are available:

� Supplier� Customer� Ship-to location� Ship-from locationThe number range attributes apply to all objects of an object type where thespecified characteristics match. The more characteristics you specify, themore specifically the defined attributes apply. If you do not specify anycharacteristics, the attributes apply to all number range intervals.The following table provides an overview of the settings that you have tomake in the number range attributes.

Field Manda-tory Set-ting

Description

Interval Type Yes In this field, you specify to which object typeyour settings apply, for example, to ASNs.

Customer No This field defines the customer ID.Supplier No This field defines the supplier ID.CustomerLocation

No This field defines the customer location ID.

Ship-FromLocation

No This field defines the ship-from location ID.



Customer�sPurchasingGroup

No This field defines the purchasing group used bythe customer.

Append/Replace Yes This field is relevant if the system is alreadyusing the interval and you create a new interval.In this field, you specify whether the systemcontinues to use the existing interval(s) or startswith the newly created interval immediately.

� If you choose the Append option, thesystem first uses the numbers in the existinginterval(s) before it starts with the newinterval. If all the numbers in the intervalare used up, the system sets the Usedindicator and starts with the new interval.

� If you choose the Replace option, thesystem no longer uses the existinginterval(s), even if not all the numbersare used up yet. The system sets theObsolete indicator for the interval and startsimmediately with the new interval.

Rolling Yes This field is relevant if you want to reuse anumber range interval.

� If all numbers in a rolling number rangeinterval are used up, the system starts againwith the first number in the number rangeinterval.

� The system only uses the numbers from anon-rolling interval once. After the systemhas assigned all numbers in the interval, itsets the Used indicator.

Prefix No Enter a character string with maximum 10 placesin this field. The system prefixes a number withthis string.

Suffix No Enter a character string with maximum of eightplaces in this field. The system adds this stringto the end of a number.

No overwrite No As standard, when creating an object, the user isable to manually overwrite the number that thesystem has given the object. If you enter X in thisfield, you cannot overwrite manually.



Alternativenumber ranges

No This field is only relevant for customercollaboration.

Max. NumberLength

No This setting defines the maximum displayedlength of the assigned number. The maximumlength includes the length of the prefix and thesuffix. For example, if you set a maximumlength of 10, the prefix XY is followed byeight characters, for example, 12345678. Theresulting number is XY12345678. However, ifthe number contains only four characters, forexample, 1234, zeros are added to completethe maximum length, XY00001234. If you donot set a maximum length, the default for themaximum number length is 35 characters.

Item Increment No The increment value for items in thegiven document can be specified here in apartner-dependent fashion. If not filled, thedefault increment is 1.

Number Range IntervalsNumber ranges or single numbers that are available for numbering objects inthe SAP Supply network collaboration

� Supplier� Customer� Ship-to location� Ship-from locationThe number range attributes apply to all objects of an object type where thespecified characteristics match. The more characteristics you specify, themore specifically the defined attributes apply. If you do not specify anycharacteristics, the attributes apply to all number range intervals.The following table provides an overview of the settings and data for numberrange intervals.

Field Manda-tory Set-ting

Description

Customer No This field defines the customer ID.fSupplier No This field defines the supplier ID.CustomerLocation

No This field defines the customer location ID.



Ship-FromLocation

No This field defines the ship-from location ID.

Customer�sPurchasingGroup

No This field defines the purchasing group used bythe customer.

Promotion ID No This field is only relevant for customercollaboration.

Interval From Yes* In this field, you enter the lower (inclusive) limitof the interval.

Interval To Yes* In this field, you enter the upper (exclusive) limitof the interval. The system does not assign thelast number to a document. The system sets theinterval to Obsolete or restarts the assignment,based on rolling settings, after the number(Interval To -1) has been used.

Single Number Yes* Single numbers are only relevant for customercollaboration. If you want to create a singlenumber, enter an alphanumerical value here.

Obsolete No If the indicator is set, the system can no longeruse the number range interval. In the followingcases, the system sets the indicator automatically:

� If you set the Replace option in the numberrange attributs, the system can no longeruse an existing interval after you create anew interval.

� If you set non-rolling intervals in thenumber range attributes, the system can nolonger use a used interval here.

You can also set the indicator manually, ifrequired, and thus specify that the system shouldno longer use the number range interval.

Last number Noread only

This field displays the number that the systemassigned last.

Date Noread ony

This field shows the date on which you createdthe number range interval.

Time (clock-time)

Noread only

This field shows the time at which you createdthe number range interval.

* Either an interval or a single number must be entered. Do not populate bothfields or none of the fields.



Partial Goods ReceiptYou may allow partial goods receipt in Customizing by choosing Supply NetworkCollaboration→ Delivery→ ASN→ Goods Receipt→ Allow Partial GoodsReceipt for ASN items.

You can control the partial goods receipt function depending on the customerlocation and product.

Confirmation ControlIn SAP SAP SNC, you can specify whether a supplier in SAP SNC can createsupplier confirmations (purchase order confirmations or scheduling agreementconfirmations) or advanced shipping notifications (ASNs) for purchase orderitems in purchase order collaboration or for scheduling agreement releases.

ASNs or supplier confirmations can be mandatory, optional (default setting), orforbidden for a certain characteristics combination. Depending on your settings inconfirmation control, SAP SNC either permits the creation of ASNs or supplierconfirmations (obligatory or optional) or does not (forbidden).

You can configure confirmation control in Supply Network CollaborationCustomizing by choosing Delivery→ Confirmation Control→ Set ConfirmationControl. You can also access this activity from the SAP Easy Access screen bychoosing Supply Network Collaboration→ Delivery→ Supplier Confirmation→Current Settings.

Hint: Confirmation control also exists for purchase orders in an SAPback-end system. However, IDocs cannot transfer the settings forconfirmation control. You must therefore ensure that you consistentlymaintain settings in the SAP back-end system and in SAP SNC.

Message Determination in SAP ERPThere are different ways to update the SAP SNC ASN with the goods receiptinformation. For all of them, you need to set up partner profiles.

The partner profile controls which IDocs are created. You maintain partnerprofiles in transaction WE20 (or chooseTools→ ALE→ ALE Administration→Runtime Settings→ Partner Profiles).

There are two possible XML message types for updating the SNC ASN from theback-end system: ReceivedDeliveryNotification and ProductActivityNotification.

The corresponding IDocs are DELVRY03.STPPOD and PROACT01.PROACT.

Depending on the way you want to update the SAP SNC ASN you need to create acorresponding entry in the Partner Profiles.



If you want to use the proof of delivery from the inbound delivery, you need toset up message determination.

To create an IDoc message from an inbound delivery you need to maintain themessage determination. You can make these entries by choosing Logistic→Materials Management→ Purchasing→ Master Data→ Messages→ InboundDelivery→ Create. In this transaction you are asked for an output type. Thesettings for message determination vary from implementation to implementation.In this course we use the standard output OPOD.

Hint: Output types are defined in customizing. Choose IMG→MaterialsManagement→ Purchasing→ Messages→ Output Control→ MessageTypes→ Define Output Types for Inbound Delivery.

After selecting the output type you are asked for a key combination. As anexample, we have set up message determination for the key combination DeliveryType / Vendor. The entry looks like this:

Condition RecordsDoc Vendor Name Funct Partner M... Dat... Lang...EL SNC100A-## Carl Stahl VN sid-

CLNTxxx6 4 EN

EL SNC100B-## LuckyWheel

VN sid-CLNTxxx

6 4 EN

If you are not using the partial goods receipt option in SAP SNC, you mustmaintain the message scheme assigned to your output type in a way that youonly send an IDoc once per inbound delivery. You can ensure this by assigninga certain requirement to your procedure for your message schema. The possiblerequirements can be found in the IMG: Materials Management→ Purchasing→Messages→ Output Control→ Maintain Requirements for Output Control.

As an example, we use requirements 17. This requirement checks that the inbounddelivery is relevant for POD process and that the goods receipt is complete. It mayhappen that another requirement better fits your business requirements.



Lesson Summary

You should now be able to:� Describe the Customizing possibilities in ASN processing in SAP SNC� Set up message determination for this process


SNC100 Unit Summary

Unit SummaryYou should now be able to:� Explain ASN processing in SAP SNC� Name the ASN alerts� Discuss the packing functionality in SAP SNC ASNs� Explain the difference between automated and manual packing� Perform ASN processing in SAP SNC� Describe the Customizing possibilities in ASN processing in SAP SNC� Set up message determination for this process


Unit Summary SNC100


Unit 5Invoice Collaboration in SAP SNC

Unit OverviewIn this unit, you will gain deeper insight into the invoice collaboration with SAPSNC.


� Explain invoice collaboration within SAP SNC� Perform invoice collaboration in SAP SNC� Customize invoice collaboration in SAP SNC� Set up message determination for invoice collaboration

Unit ContentsLesson: Invoice Collaboration Process Overview ... . . . . . . . . . . . . . . . . . . . . . . .174Lesson: Process Demo: Invoice Collaboration ... . . . . . . . . . . . . . . . . . . . . . . . . . .189

Exercise 5: Invoice Processing with SAP SNC... . . . . . . . . . . . . . . . . . . . . . .191Exercise 6: Self-Billing with SAP SNC.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Lesson: Relevant Customizing for Invoice Collaboration in SAP SNC ..203


Unit 5: Invoice Collaboration in SAP SNC SNC100

Lesson: Invoice Collaboration Process Overview

Lesson OverviewIn this lesson, you will learn about invoice collaboration within SAP SNC.


� Explain invoice collaboration within SAP SNC

Business Example

BackgroundInvoice collaboration enables a supplier or customer to produce invoices for goodsthat have been provided by the supplier to the customer. You can create invoicesfor purchase orders, replenishment orders, or advanced shipping notifications(ASNs).

Note: ASNs are related to a purchasing document, such as a purchaseorder or scheduling agreement.

Invoice collaboration in SAP SNC supports the following processes:

� The supplier manually creates an invoice in SAP SNC for goods that he orshe has provided to the customer.

� The supplier sends an invoice via XML message through SAP NetWeaver toSAP SNC.

Caution: The IDocs, XML messages, and mappings dependon which ERP system and release is being used. Mappings aresometimes required for the message flow between the supplier�ssystem and SAP SNC. Since the mappings are dependent on thesupplier�s system, they cannot be predefined in the SAP SNCstandard delivery. You must create the mappings as part of a projectsolution.

� The supplier manually creates a subsequent debit or credit in SAP SNC.� The supplier sends a subsequent debit or credit via XML message through

SAP NetWeaver to SAP SNC.

Caution: The IDocs, XML messages, and mappings dependon which ERP system and release is being used. Mappings aresometimes required for the message flow between the supplier�s


SNC100 Lesson: Invoice Collaboration Process Overview

system and SAP SNC. Since the mappings are dependent on thesupplier�s system, they cannot be predefined in the SAP SNCstandard delivery. You must create the mappings as part of a projectsolution.

Hint: In all of the above processes, SAP SNC is able to receive aninvoice confirmation from the customer�s back-end system after invoiceverification. However, the use of this function is dependant on thecustomer back-end system being able to send such a confirmation.

� The customer creates a self-billing invoice, which is sent to the SAP SNCsystem.

� The customer creates a self-billing invoice, which is sent to SAP SNC andthe supplier�s ERP system.


� The customer performs a revaluation. The created documents are sent tothe SAP SNC system.

� The customer performs a revaluation. The created documents are sent toSAP SNC and the supplier�s ERP system.


DefinitionsInvoice

An invoice is created by the supplier to charge a customer for goods thathave been provided by the supplier to that customer.An invoice can reference an existing purchase order, replenishment order,or advanced shipping notification (this allows you to invoice a schedulingagreement).



Self-billing invoiceA self-billing invoice is created by a customer. It contains the invoice detailsfor goods provided by the supplier to the customer. A supplier does notcreate an invoice for goods that are invoiced using a self-billing invoice.A self-billing invoice references an existing purchase order, replenishmentorder, or advanced shipping notification (this allows you to invoice ascheduling agreement).

Subsequent debit/creditThis is an additional document that the supplier creates for a transactionthat has already been invoiced. The subsequent debit or credit charges anadditional value for, or reduces the original value of, a quantity of goods thathas already been invoiced.A subsequent debit or credit can reference an existing purchase order,replenishment order, or advanced shipping notification.

RevaluationIf the price of a product changes and is retroactively valid, the customercan create a revaluation. This determines the difference in value for itemsthat have already been invoiced. A revaluation can only be created for apurchasing order or advanced shipping notification that has the Evaluatedreceipt settlement (ERS) indicator set.

Master Data and Settings for InvoicesTo use the invoice collaboration functions in SAP SNC, you must set up therequired master data in SAP SNC. In addition to general master data for suppliercollaboration in SAP SNC, you must also set up invoice-specific master data.



Partner-dependent purchasing document dataYou can transfer partner-dependent purchasing document data from SAPERP to SAP SNC using the Core Interface (CIF). If you do not havethis functionality set up, or you want to change this data, you can enterpurchasing document master data manually in SAP SNC.You can maintain partner-dependent master data using the SAP SNC Web UIby choosing Master Data→ Partner-Dependent Data→ Maintenance ofPartner-Dependent Purchasing Document Data. You can also access it fromthe SAP Easy Access screen by choosing Supply Network Collaboration→Master Data→ Application-Specific Master Data→ Invoice→ MaintainPartner-Dependent Purchasing Document Data. Both the customer andsupplier can maintain purchasing document data in the customer�s SAPSNC system.You must specify the following data:

� Customer number� Purchasing document number� Purchasing document type� Purchasing document itemYou can manually maintain the following data:

� Net price� Price unit� Price unit of measure� Terms of payment key� Incoterm� Incoterm location� Tax code� Jurisdiction code� Currency� Use Data to Create Invoice indicator

If you select the Use Data to Create Invoice indicator, SAP SNC usesthis data to automatically fill out the corresponding fields when thesupplier creates an invoice.



Partner-dependent payment termsYou can maintain partner-dependent payment terms using the SAP SNCWebUI by choosing Master Data→ Partner-Dependent Data→ Assignmentof Payment Terms to Partners. You can also access it from the SAP EasyAccess screen by choosing Supply Network Collaboration→ Master Data→ Application-Specific Master Data→ Invoice→ Assign Payment Termsto Partners.This enables the customer or supplier to maintain the payment terms fora particular supplier-customer pair.You can maintain the following data:

� Terms of payment� Net payment period� Payment period for normal cash discount in days� Normal cash discount percentage� Payment period for maximum cash discount in days� Maximum cash discount percentageSAP SNC uses this data to automatically assign the defined payment termswhen you create an invoice for the specified partner. If you want to usedifferent payment terms for a particular invoice, you can manually overwritethe payment terms in the invoice.

Tax codesTo send calculated tax data between SAP SNC and the customer�s back-endERP system, you must maintain tax codes in both SAP SNC and SAP ERP.This is because SAP ERP uses the tax code to calculate the gross amount.Each tax code can relate to a number of tax rates that you maintain.

Note: For more information about maintaining tax codes, see theImplementation Guide (IMG) for Supply Network Planning bychoosing Invoice→ Maintain Tax Codes for Invoices.



Data transferred via CIFIf you are using an SAP ERP 2005 or higher back-end system, you cantransfer the following data via the Core Interface (CIF) from purchasingdocuments (scheduling agreements and contracts) in SAP ERP to SAP SNC.If you transfer this data using CIF, you do not need to maintain it manually inSAP SNC.

� Payment terms� Document currency� Goods receipt based invoice verification indicator� Evaluated receipt settlement indicator� No cash discount indicator� Price� Price unit� Purchase order price unit� Conversion of order price unit to order unit� Conversion of order unit to base unit� Invoice receipt indicator� Incoterms� Incoterm location� Jurisdiction code� Final invoice indicator� Tax code

Incoterms in SAP SNCWhen an invoice is created, the Incoterm and location that are used in thereference document are transferred from that reference document to theinvoice.The master data for Incoterms in the customer�s back-end system, however, isnot transferred to SAP SNC. Therefore, you must manually maintain masterdata for Incoterms in your SAP SNC system so that it matches the Incotermsin your back-end ERP system. If, in an invoice, you use an Incoterm thatyou have not maintained in the master data, the system generates an errormessage when it performs validation checks for the invoice.Define Incoterms in Customizing for SAP SNC by choosing SCM Basis→Master Data→ Define Incoterms.



Invoice Follow-Up-Requirement CodeWhen a customer sends a purchase order to SAP SNC, the XML message includesa follow-up-requirement code relevant to invoicing. This determines whetherthe supplier needs to create an invoice for the purchase order or not. Thisinvoice-relevant follow-up-requirement code has three possible values that definewhether the creation of an invoice is mandatory, not allowed, or optional.

Hint: If you use a purchase order sent from an SAP ERP back-endsystem as the reference document for your invoice, the purchase ordermust have been sent to SAP NetWeaver XI using an IDoc of typePORDCR1.PORDCR102 in order for the follow-up code to have beensent. IDocs of type ORDERS.ORDER05 do not transfer the invoicefollow-up code.

If you want to create an invoice for a scheduling agreement (using anASN) the invoice follow-up code is transferred via the Core Interface(CIF).



XML Messages for Invoice CollaborationInvoice collaboration in SAP SNC uses the following XML messages:

� InvoiceRequest

� If the customer creates a self-billing invoice or revaluation in his orher back-end system and the customer creates an IDoc message of typeGSVERF.GSVERF03 for customer self-billing or the revaluation of aninvoice in his or her back-end system he or she sends this message toSAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI). SAPNetWeaver XI maps the message to an InvoiceRequest XML messageand sends it to SAP SNC. SAP SNC uses this message to create aself-billing invoice or revaluation.

� When the supplier publishes an invoice in SAP SNC, SAP SNC sendsan invoice request to the customer's back-end ERP system via SAPNetWeaver XI using an XML message of type InvoiceRequest.

� InvoiceConfirmation

If a customer confirms an invoice in his or her back-end system,SAP SNC can receive this confirmation as a XML message of typeInvoiceConfirmation. SAP SNC uses this XML message to update thestatus of the invoice.

Hint: Although SAP SNC supports this function, the ability to makeuse of it is dependent on the customer�s back-end system being ableto create such a confirmation.

� PaymentAdviceNotification

When the customer creates a payment run in his or her back-end system,a remittance advice is sent to SAP NetWeaver XI using an IDoc of typeREMADV.PEXR2002. SAP NetWeaver XI maps this IDoc to an XMLmessage of type PaymentAdviceNotification and sends it to SNC. SAP SNCuses this XML message to update the payment status of the invoice.

Manual Creation of Invoice Using the SAP SNC Web UIThe supplier can create an invoice using the Create Invoice screen.



The supplier can create the following types of invoice:

� Standard invoice� Subsequent debit� Subsequent credit

Note: You can only create subsequent debits and credits for referencedocument items that have already been invoiced. The validation checkINV_ITM_CREDIT_QTY checks that the subsequent debit or creditquantity does not exceed the quantity that was invoiced.

When you create an invoice, you can reference a purchase order item or anadvanced shipping notification (ASN) item. If a purchase order item also hasan associated ASN, you can only reference the purchase order item or the ASNitem, not both.

When the supplier creates an invoice, SAP SNC checks the Invoice CreationType field in the reference document. The following three settings are availablein this field:



Invoice Creation Type DescriptionInvoice Creationwith Purchase OrderReference

The system sets this value as follows:

� In the standard setting, this is the default valuefor a purchase order or replenishment orderthat has been created without the GoodsReceipt-Based Invoice Verification indicatorset.

This setting is controlled by the validationcheck PO_INVOICE_CREATION for pur-chase orders, and RO_INVOICE_CREATIONfor replenishment orders.

� If a purchase order item or replenishment orderitem has already been partially invoiced usingthe purchase order as the reference document.

If this value is the status of the Invoice CreationType field, an invoice can only be created for thisreference document item by using the purchaseorder as the reference document.

Invoice Creation withASN Reference

The system sets this value as follows:

� In the standard setting, this is the default valuefor a purchase order that has been created withthe Goods-Receipt-Based Invoice Verificationindicator set.

This setting is controlled by the validationcheck PO_INVOICE_CREATION for pur-chase orders, and RO_INVOICE_CREATIONfor replenishment orders.

� If a purchase order item has already beenpartially invoiced using the ASN as thereference value

If the Invoice Creation Type field has this value, aninvoice can only be created for this purchase orderitem by using the ASN as the reference document.

Invoice Creation Similarto Predecessor Invoice

If the Invoice Creation Type field has this value,an invoice can be created using either the purchaseorder or the ASN as the reference document. Anysubsequent invoices created for that same item,however, must use the same reference documenttype.For example, if part of purchase order item 10 isinvoiced using an ASN as the reference document,then any subsequent invoices for purchase order item10 must also use ASNs as the reference documenttype.It is possible to configure SAP SNC to make thisthe default value for purchase order items andASN items, regardless of the Goods-Receipt-BasedInvoice Verification indicator. To do this you mustactivate the validation check PO_INVOICE_RE-LATED_TO_PO_OR_ASN for purchase orders andRO INVOICE RELATED TO PO OR ASN for



Invoice with Reference to Purchase Order or Replenishment Order ItemAn invoice can only be created with a purchase order as the referencedocument if the Invoice creation type field in the purchase order item datahas the status Invoice Creation with Purchase Order Reference or InvoiceCreation Similar to Predecessor Invoice.An invoice can be created for a valid purchase order.When the invoice is created, the PO item is updated:

Item Creation TypeThis field is updated with the status Invoice Creation with PurchaseOrder Reference.

Quantity to Be InvoicedThis is the remaining quantity that is to be invoiced.

Invoiced QuantityThis is the total invoiced quantity relating to this purchase order.

Invoice with Reference to Advanced Shipping Notification ItemAn invoice can be created for a valid scheduling agreement or purchase orderby using an associated ASN as a reference document.An invoice can only be created with an ASN as the reference document if theInvoice Creation Type field in the item data has the status Invoice Creationwith ASN Reference or Invoice Creation Similar to Predecessor Invoice.When the invoice is created, the ASN item (and any associated PO item)is updated:

Item Creation TypeThis field is updated with the status Invoice Creation with ASNReference.

Quantity to Be InvoicedThis is the remaining quantity that is to be invoiced.

Invoiced QuantityThis is the total invoiced quantity relating to this purchase order item orscheduling agreement item.

Invoice Creation Using XML Message from SupplierBack-End SystemIf the supplier�s back-end system is connected to the customer�s SAP NetWeaverXI system, it is possible for the supplier to create a new invoice in his or her ownback-end system and send an invoice request to SAP NetWeaver XI using an XMLmessage of type InvoiceRequest or an IDoc of type INVOIC.INVOIC01.



Caution: Note that the IDocs, XML messages, and mappings depend onwhich ERP system and releases are being used. Mappings are sometimesrequired for the message flow between the supplier�s system and SAPSNC, depending on the supplier�s system. Since the mappings aredependent on the supplier�s system, they cannot be predefined in theSAP SNC standard delivery. You must create the mappings as part of aproject solution.

The following processes are then possible:

� The customer�s SAP NetWeaver XI system receives an XML message oftype InvoiceRequest or an IDoc of type INVOIC from the supplier. Fromhere an XML message of type InvoiceRequest is sent to SAP SNC, and anIDoc of type INVOIC is sent to the customer�s ERP system.

� The customer�s SAP NetWeaver XI system receives an XML message oftype InvoiceRequest from the supplier. SAP NetWeaver XI sends an XMLmessage of type InvoiceRequest to SAP SNC, where the invoice is checkedagainst validation checks. If the invoice passes the validation checks, itis automatically published and sent on from SAP SNC to the customer�sSAP ERP system via SAP NetWeaver XI. If the invoice does not pass thevalidation checks, it is given the status Received. In this case, the suppliermust manually change and publish the invoice in SAP SNC in order for itto be sent on to the customer�s SAP ERP system.

Creation of Self-Billing InvoiceThe customer can create a self-billing invoice in his or her ERP back-end systemand send an IDoc of type GSERVF.GSERVF03 to SAP NetWeaver XI. SAPNetWeaver XI maps this to an XML messageof type InvoiceRequest. When theself-billing invoice is received in SAP SNC, SAP SNC performs a series ofvalidation checks to ensure that the correct data is filled out and that the datais consistent.

When a self-billing invoice is created, SAP SNC fills the Invoice Type field withthe value Self-Billing Invoice and assigns the status Published. Self-billinginvoices cannot be changed in SAP SNC.

Creation of RevaluationThe customer can create a revaluation for a self-billing invoice in his or herERP back-end system and send an IDoc of type GSERVF.GSERVF03 to SAPNetWeaver XI. SAP NetWeaver XI maps this to an XML message of typeInvoiceRequest and sends it to SAP SNC. When SAP SNC receives this messageand creates a revaluation, it fills the Invoice Type field with the value Self-Billing



Invoice and assigns the status Published. Depending on the action code in themessage, the Item Type field is either assigned the value Revaluation Creditor Revaluation Debit.

Invoice PublicationTo support invoice processing in the customer back-end system you must sendinvoices created in SAP SNC to the customer back-end system. Do this by sendingan XML message of type InvoiceRequest.

In the standard setting, invoices are automatically sent in the background whenyou call the publish function. This can be carried out in the following ways:

� Validation Check

In the standard setting, SAP SNC sends the XML messages directlyin the background. This is controlled by the validation checkINV_PUBLISH_DIRECT.

If you deactivate this validation check, SAP SNC sends the XML messagesusing the Post Processing Framework (PPF).

� Post Processing Framework (PPF)

If you want SAP SNC to send the XML messages using the PPF, you mustalso activate actions in the /SCA/BOL_INVOICE PPF action profile for the/SCA/ICH application as follows:

� To send XML messages of type InvoiceRequest to thecustomer back-end system when you call the publish functionfrom the Create Invoice screen, you must activate the action/SCA/BOL_INVOICE_XML.

� If you want SAP SNC to automatically send an XML message of typeInvoiceRequest to the customer back-end system for a valid invoicethat was received in SAP SNC from a supplier back-end system, youmust activate the action /SCA/BOL_INVOICE_XML_ROUTING.

Invoice StatusSAP SNC sets the status of an invoice to show which stage of the invoice processthe invoice is currently at.



Invoice StatusStatus Triggering FunctionDraft The supplier saves the invoice as Draft.

SNC does not send out invoices saved with thestatus Draft. Use this status if the invoice is incomplete.

Published The invoice is published. The supplier can no longer makechanges to the invoice.

Received The supplier sent the invoice via XML to SAP SNC. SAPSNC has not published the invoice.

Paid This status is set by the XML message of typePaymentAdviceNotification which is received from thecustomer back-end system when a payment run has beencompleted.

Acceptance Status

If the customer sends an invoice confirmation from his or her back-end systemusing an XML message of type InvoiceConfirmation, this status is set. Thefollowing status values are available:

Status Triggering FunctionPending The customer has not yet confirmed or rejected the

invoice.Accepted The customer back-end system accepted the invoice and

sent an XML message of type InvoiceConfirmation.Rejected The customer back-end system rejected the invoice and

sent an XML message of type InvoiceConfirmation.



Lesson Summary

You should now be able to:� Explain invoice collaboration within SAP SNC


SNC100 Lesson: Process Demo: Invoice Collaboration

Lesson: Process Demo: Invoice Collaboration



� Perform invoice collaboration in SAP SNC

Business Example

Demo

Figure 56: Demo





Exercise 5: Invoice Processing with SAPSNC

Exercise ObjectivesAfter completing this exercise, you will be able to:� Run an invoice processing scenario with SAP SNC

Business ExampleYour supplier creates an invoice in SNC with reference to a purchase order. Onpublication, the invoice is sent to the ERP system, where it is verified and thepayment run carried out. The payment information is sent to SNC and the statusof the invoice is updated accordingly.

Task 1: Create an invoice in SAP SNCLog onto the supplier view with supplier user IU-SUPA## and call up the purchaseorder you created in the Purchase Order Collaboration exercise. If necessary,create a new purchase order in ERP for this exercise. Create an invoice, INV_##,directly from the Purchase Order Details screen.

Note: In a real-world scenario, the supplier might want to create aninvoice for several position. In this case, the Documents RequiringInvoices function provided from the Invoice menu is an efficient way toaccomplish this task. Feel free to explore this as an alternative to creationvia the Purchase Order Details screen.

1. Log onto the supplier view with supplier user IU-SUPA## and call up thepurchase order you created. If necessary, create a new purchase order in ERP.

2. Create an invoice, INV_##, directly from the Purchase Order Details screen.

Task 2: Display the invoice in the ERP systemDisplay the invoice in the ERP system

Hint: This task is performed in the role of the customer thus you need touse user SNC100-## ro log on to the ERP system.

1. Display the invoice in the ERP system.




Task 3: Release the invoiceRelease the invoice

1. Release the invoice in the SAP ERP System

Task 4: Conduct the payment runConduct the payment run

1. Conduct the payment run.

ResultThe payment information has been sent to SNC. You can check in transactionWE05 to ensure that an IDoc of the type REMADV.PEXR2002 has been sent.

Task 5: Check the status of the invoice in SNCWhat is the status of the invoice in SNC following the payment of the invoice?

Hint: This task is again performed in the role of the supplier. (UserIU-SUPA##).

1. Check the status of the invoice in SNC.



Solution 5: Invoice Processing with SAPSNCTask 1: Create an invoice in SAP SNCLog onto the supplier view with supplier user IU-SUPA## and call up the purchaseorder you created in the Purchase Order Collaboration exercise. If necessary,create a new purchase order in ERP for this exercise. Create an invoice, INV_##,directly from the Purchase Order Details screen.

Note: In a real-world scenario, the supplier might want to create aninvoice for several position. In this case, the Documents RequiringInvoices function provided from the Invoice menu is an efficient way toaccomplish this task. Feel free to explore this as an alternative to creationvia the Purchase Order Details screen.

1. Log onto the supplier view with supplier user IU-SUPA## and call up thepurchase order you created. If necessary, create a new purchase order in ERP.

a) Navigate to the Purchase Order Details screen by choosing PurchaseOrder→ Purchase Order Details.

b) Enter your PO number and choose Go, or use the input help to findthe PO.

2. Create an invoice, INV_##, directly from the Purchase Order Details screen.

a) Choose Create Invoice for Items. You branch to the invoice creationscreen.

b) On the Create Invoice screen, enter an invoice number, INV_##, andchoose Check.

c) If the check is okay, choose Publish to send the invoice to the ERPsystem.




Task 2: Display the invoice in the ERP systemDisplay the invoice in the ERP system

Hint: This task is performed in the role of the customer thus you need touse user SNC100-## ro log on to the ERP system.

1. Display the invoice in the ERP system.

a) In the ERP system, choose Logistics→ Materials Management→Logistics Invoice Verification→ Further Processing→ InvoiceOverview or use transaction code MIR6.

b) On the selection screen, enter the following parameters and choose(F8):Company code: 1000Invoicing Party: SNC100A-##Entry type: select EDI

Invoice status: select all checkboxes

Hint: Ensure that the Processor selection field is empty.

The system shows a list of invoice documents. Choose Display Detailsto view the details.

Task 3: Release the invoiceRelease the invoice

1. Release the invoice in the SAP ERP System

a) In the ERP system, choose Logistics→ Materials Management→Logistics Invoice Verification→ Further Processing→ ReleaseBlocked Invoices or user transaction code MRBR.

b) On the selection screen ,enter the following parameters and press(F8):

Company code: 1000Vendor: SNC100A-##

c) The system lists the invoice you created in SNC as the supplier. Selectthe corresponding line and choose Release Invoice .

d) Choose Save . The invoice is now released for payment.






a) In the ERP system, choose Accounting→ Financial Accounting→ Accounts Payable→ Periodic Processing→ Payments or usetransaction code F110.

b) On the selection screen, make the following entries:Run date: Today’s date

Identification: SNC##

c) Go to the Parameters tab page and enter the following:Company code: 1000Pmt mthd: UNext p/date: today + 2 months

Vendor: SNC100A-##

d) On the Additional Log tab page, make the following entries:

Due check date:Pmnt method selection if not successful:Line items of the payment documents:Vendors (from): SCN100A-##Vendors (to): SCN100A-##

e) On the Print/data medium tab page, make the following entries:

Enter the variant for the program RFFOAVIS_FPAYM: SNC100

f) Switch back to the Status tab page and save your entries.

g) Choose Payment run to execute the payment run, and confirm anywarning messages with Yes.

h) In the dialog box to schedule and start the payment run, make thefollowing entries:

Start date: today’s date

Start immediately:

Create pmnt medium:

Choose Enter to start the payment run.

i) Choose Status repeatedly until the status is

Posting orders: 1 generated, 1 completed.




ResultThe payment information has been sent to SNC. You cancheck in transaction WE05 to ensure that an IDoc of the typeREMADV.PEXR2002 has been sent.


Hint: This task is again performed in the role of the supplier. (UserIU-SUPA##).

1. Check the status of the invoice in SNC.

a) Log on to SNC as the supplier (IU-SUPA##) and choose Invoice→Invoice Overview. Choose Go to display your invoices. You invoiceshould now have the status Paid.

b) Click on the invoice number to branch to the Invoice Details screen.On the Payment status tab page, you can see the date and amount of thecustomer payment.



Exercise 6: Self-Billing with SAP SNC

Exercise ObjectivesAfter completing this exercise, you will be able to:� Run a self-billing scenario with SAP SNC

Business ExampleIn this process, the customer creates an invoice for goods that have been purchasedfrom a supplier.

The responsibility for creating an invoice does not lie with the supplier; however,the supplier is able to view invoices once the customer has sent them to SAP SNC.The supplier can also view the status of a payment run for an invoice, that is, oncethe customer has initiated and completed the payment run.

When the customer purchases goods from a supplier, he or she can issue aninvoice, thus shortening the time of document creation. The customer can theninitiate payment for that invoice.

Task 1: Carry out invoice verificationCaution: As a prerequisite to this scenario, you must have completed theexercise on release processing and must have created a correspondingASN for at least one schedule line for which you have posted the goodsreceipt in ERP.

Carry out an invoice verification run in ERP and write down the resulting invoicenumber: ______________________

Hint: This task is performed in the role of the customer (UserSNC100-##) in the ERP system.

1. Carry out an invoice verification run in ERP.

2. Write down the resulting invoice number. ______________________




Task 2: Display the invoice in SNCLog on as the supplier and display the invoice in SNC.

Hint: This task is performed in SNC. Because the invoice is related to theASN for the scheduling agreement release you need to logon as supplierSNC100B-## using the user IU-SUPB##.

1. Log on as the supplier and display the invoice in SNC.


Hint: This is again a task for the customer to be carried out in ERP withuser SNC100-##.


ResultThe payment information has been sent to SNC. You can check in transactionWE05 to ensure that an IDoc of the type REMADV.PEXR2002 has been sent.


Hint: This finally is a task performed by supplier SNC100B-## (UserIU-SUPB##) in SAP SNC.

1. Check the status of the invoice in SNC



Solution 6: Self-Billing with SAP SNCTask 1: Carry out invoice verification

Caution: As a prerequisite to this scenario, you must have completed theexercise on release processing and must have created a correspondingASN for at least one schedule line for which you have posted the goodsreceipt in ERP.

Carry out an invoice verification run in ERP and write down the resulting invoicenumber: ______________________

Hint: This task is performed in the role of the customer (UserSNC100-##) in the ERP system.

1. Carry out an invoice verification run in ERP.

a) In the ERP system, choose Logistics→ Material Management→Logistics Invoice Verification→ Automatic Settlement→ EvaluatedReceipt Settlement or use transaction code MRRL.

b) On the selection screen, enter the following parameters:Company Code: 1000Vendor: SNC100B-##Purchasing document: scheduling agreement number

Test Run: (deselected)

Choose .

A line with ERS-Pstable=X is displayed, referencing the schedulingagreement, the item 10, and the external delivery reference.

2. Write down the resulting invoice number. ______________________

a) Write down the invoice number (in the Document number column)._____________________

You can view the details of the invoice by clicking on the documentnumber.




Task 2: Display the invoice in SNCLog on as the supplier and display the invoice in SNC.

Hint: This task is performed in SNC. Because the invoice is related to theASN for the scheduling agreement release you need to logon as supplierSNC100B-## using the user IU-SUPB##.

1. Log on as the supplier and display the invoice in SNC.

a) In the SNC supplier view, either navigate to the invoice from the ASNdetails screen (Invoices Related to ASN) or choose Invoice→ InvoiceOverview to find and display the invoice created.


Hint: This is again a task for the customer to be carried out in ERP withuser SNC100-##.


a) In the ERP system, choose Accounting→ Financial Accounting→ Accounts Payable→ Periodic Processing→ Payments or usetransaction code F110

b) Make the following entries on the selection screen:Run date: Today’s date

Identification: ERS##

c) Go to the Parameters tab page and enter the following:Company code: 1000Pmt mthd: UNext p/date: today + 2 months

Vendor: SNC100B-##

d) On the Additional Log tab page, make the following entries:

Due check date:Pmnt method selection if not successful:Line items of the payment documents:Vendors (from): SCN100B-##Vendors (to): SCN100B-##




Due check date: selectPmnt method selection if not successful:selectLine items of the payment documents: selectVendors (from):SCN100B-##Vendors (to): SCN100B-##

e) On the Print/data medium tab page, make the following entries:

Enter the variant for the program RFFOAVIS_FPAYM: SNC100

f) Switch back to the Status tab page and save your entries.

g) Choose Payment run to execute the payment run, and confirm anywarning messages with Yes.

h) In the dialog box to schedule and start the payment run, make thefollowing entries:

Start date: today’s date

Start immediately:

Create pmnt medium:

Choose Enter to start the payment run.

i) Choose Refresh repeatedly until the status is Posting orders: 1generated, 1 completed.

ResultThe payment information has been sent to SNC. You cancheck in transaction WE05 to ensure that an IDoc of the typeREMADV.PEXR2002 has been sent.


Hint: This finally is a task performed by supplier SNC100B-## (UserIU-SUPB##) in SAP SNC.

1. Check the status of the invoice in SNC

a) Log on to SNC as the supplier (IU-SUPB##) and choose Invoice→Invoice Overview. Choose Go to display your invoices. You invoiceshould now have the status Paid.

b) Click on the invoice number to branch to the Invoice Details screen.On the Payment status tab page, you can see the date and amount of thecustomer payment.



Lesson Summary

You should now be able to:� Perform invoice collaboration in SAP SNC


SNC100 Lesson: Relevant Customizing for Invoice Collaboration in SAP SNC

Lesson: Relevant Customizing for Invoice Collaborationin SAP SNC

Lesson OverviewIn this lesson, you will learn about relevant customizing for invoice collaborationin SAP SNC.


� Customize invoice collaboration in SAP SNC� Set up message determination for invoice collaboration

Business Example

Maintaining Tax CodesTo send calculated tax data between SAP SNC and the customer�s backend ERPsystem, you must maintain tax codes in both SAP SNC and SAP ERP. This isbecause SAP ERP uses the tax code to calculate the gross amount. Each tax codecan relate to a number of tax rates that you maintain.

Note: For more information about maintaining tax codes, see theImplementation Guide (IMG) for Supply Network Planning by choosingInvoice→ Maintain Tax Codes for Invoices.

Invoice NumberWhen you create an invoice, SAP SNC can automatically assign an invoicenumber.

In order for SAP SNC to assign numbers for invoices, you must have definednumber ranges in the Web UI by choosing Master Data→ Number Ranges→Invoice Number Range Intervals.

Hint: If you use an SAP backend system, the numbers can have amaximum of 10 places. Therefore, limit the length of the order numbersin the number range attributes to 10 places.

To assign invoice attributes from the Web UI, choose Master Data→ NumberRanges→ Number Range Attributes.



Invoice Creation TypeIf you want the supplier to create invoices for purchase orders, you should beaware that there is a dependency between the invoice creation type and the GoodsReceipt-Based Invoice Verification indicator in the SAP ERP purchase order.

In the standard setting, the invoice creation type Invoice Creation with PurchaseOrder Reference is the default value for a purchase order or replenishment orderthat has been created without the Goods Receipt-Based Invoice Verificationindicator set. If the indicator is set, the invoice creation type will be set to InvoiceCreation with ASN Reference.

Message DeterminationMessage determination is relevant for creating IDocs in the ERP system. This isthe case for sending self-billing invoices and revaluation.

In order to send the IDoc for the self-billing invoice to the supplier you needto setup the message determination in transaction NACE for Application MR,condition recordERS6. For this course we set up message determination based onthe Key Combination CoCode, Vendor.

Vendor Funct Partner Medium Date / Time Lan-guage

SNC100* LS sidCLNTxxx 6 4 EN

Partner ProfilesA partner profile controls which IDocs are created. You maintain partner profilesin transaction WE20; choose Tools→ ALE→ ALE Administration→ RuntimeSettings→ Partner Profiles.

Corresponding to the above entries in Message Determination, entries are requiredfor for LS sidCLNTxxx and message type GSVERF (Basic type GSVERF03).


SNC100 Lesson: Relevant Customizing for Invoice Collaboration in SAP SNC

Lesson Summary

You should now be able to:� Customize invoice collaboration in SAP SNC� Set up message determination for invoice collaboration


Unit Summary SNC100

Unit SummaryYou should now be able to:� Explain invoice collaboration within SAP SNC� Perform invoice collaboration in SAP SNC� Customize invoice collaboration in SAP SNC� Set up message determination for invoice collaboration


Unit 6Master Data

Unit OverviewIn this unit, you will gain deeper insight into the master data being used withinSAP SNC.


� Name the relevant master data for supplier collaboration with SAP SNC� Explain which master data objects are integrated from SAP ERP and which

are maintained in SAP SNC� Discuss the business partner concept� Explain how master data is integrated to SAP SNC� Understand how to use the Core Interface� Explain what need to be considered for an automated data transfer� Explain the visibility concept of SAP SNC

Unit ContentsLesson: Master Data ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208Lesson: Master Data Integration.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Lesson: Visibility Concept . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227


Unit 6: Master Data SNC100

Lesson: Master Data

Lesson OverviewThis lesson will give you an overview of the relevant master data in SAP SNC


� Name the relevant master data for supplier collaboration with SAP SNC� Explain which master data objects are integrated from SAP ERP and which

are maintained in SAP SNC� Discuss the business partner concept

Business Example

Master DataFor all collaborative business processes that use SAP Supply NetworkCollaboration (SAP SNC), you need the following basic master data in SAP SNC:

Business partnerThe following types of business partners are relevant for SAP SNC:

� A business partner of type organization represents a company. Foreach company that is involved in a business process, you need abusiness partner of type organization (for example, for the customerand for the supplier).

� A business partner of type person corresponds to a real person withina company. It represents a specific user who works with the SAPSNC Web application. A business partner of type person is connectedto the business partner of type organization, which represents thecompany. Each user is assigned to only one business partner of typeorganization. You link a business partner of type person to an Internetuser and an SAP SNC system user.

Hint: You can assign several persons to each organization, butonly one organization can be assigned to a person.


SNC100 Lesson: Master Data

LocationA location is the place or the organizational unit that provides or receivesgoods, for example, the supplier�s ship-from location or the customerlocation. You assign the location to the organization to which it belongs. Youmake the assignment in the location master.

Note: A location master also contains organizational data, such astime zones or location addresses.

ProductA product is a material that is used or exchanged in a business process.You define a product master for each product that is relevant for a businessprocess.For the product that the supplier delivers to the customer, you create acustomer location product. This means that you assign the product to thecustomer location. Maintain the application-specific settings in the productmaster for the customer location product (for example, planning parametersfor replenishment planning).

Transportation laneA transportation lane connects the ship-from location with the customerlocation. You must assign the product that the supplier delivers to thecustomer to the transportation lane. You must also assign at least one meansof transport to the transportation lane. SAP SNC uses the transportationduration of the means of transport that is assigned to the transportation laneto schedule the delivery date from the shipping date, and vice versa.

Hint: Some processes, such as purchase order processing or releaseprocessing, do not necessarily require transportation lanes. However,it will require some customizing effort to run these processessmoothly without transportation lanes.

Note: Depending on the business process, you need additional master datafrom SCM Basis or SNC-specific master data. For packing in deliveryprocessing, for example, you need packaging specifications.

Model and Version AssignmentYou must assign the following master data objects to the active supply chainmodel 000 and the active version 000:

� Product� Location� Transportation lane



Figure 57: Master Data Concept

Master Data MaintenanceYou can create the basic master data manually in the SAP GUI of SAP SNC.Depending on the application and the business process, you must maintainadditional master data on the SAP SNC Web UI.

If you run SAP SNC together with an SAP ERP back-end system, you can usethe SAP SCM Core Interface to transmit the following master data from theback-end system to SAP SNC:

� Product� Location� Transportation lane

SAP SNC creates a transportation lane from a purchasing info record ora scheduling agreement. You must assign the means of transport and thetransportation duration manually in the transportation lane.

� Business partner of type organization for the supplier

You can also use Business Application Programming Interfaces (BAPIs) totransmit these master data objects (for example, in the case of a non-SAP-ERPback end).



Manual Creation of Master Data for SAP SNCYou create the basic master data objects manually in the SAP GUI of SAP SNC.Maintain the data on the SAP Easy Access screen under Master Data.

1. If supply chain model 000 and the planning version 000 are not yet availablein the SAP SNC system, create these objects in the specified sequence.

To do this, choose Supply Network Collaboration→ Master Data→ Modeland Planning Version→ Create Model 000 and Planning Version 000 fromthe SAP Easy Access screen.

2. Create a business partner of type organization for each business partner whois involved in the business process (for example, customer and supplier).

To do this, on the SAP Easy Access screen, choose Supply NetworkCollaboration→ Master Data→ Business Partner→ Create BusinessPartner.

3. Create a business partner of type person for each employee of theorganization who works with SAP SNC. Assign an SAP SNC and an Internetuser to this person. Link the business partner person to the business partnerorganization to which he or she belongs using a relationship. To do so, usethe relationship category Is SNC User Of or Has SNC User. If you do notcreate relationships for an Internet user using these relationship categories,SAP SNC uses the relationships of category Is Contact Partner Of or HasContact Partner, if they are available.

4. Create a location for each location that belongs to a business partner of typeorganization and assign the location to this business partner. Make thissetting in the Partners area on the General tab page in the location productmaster. Enter the business partner of type organization in the BusPartnerfield. Assign the locations to model 000.

You can also maintain partner-dependent location numbers and locationdescriptions.

5. Create a customer location product for each product that the supplier is todeliver to the customer and assign this customer location product to model000.

You can also maintain partner-dependent product numbers and productdescriptions.

6. Create a transportation lane between the ship-from location and the customerlocation.

7. Assign the product and a means of transport to the transportation lane. Enterthe duration of transportation for the means of transport.



Caution: Before you delete master data, carefully check whether themaster data is still being used in SAP SNC. You must not delete anymaster data that SAP SNC is still using (in other words, for whichtransaction data still exists). For products, you can use the where-used list.

Where-Used List for SAP Supply Network CollaborationYou can use the where-used list to see where a master data object is used. In SAPSNC, you can use the where-used list for the product. You can determine, forexample, to which locations a product is assigned. The objects can be documentsor master data related to SAP SNC. The where-used list is of particular importancewhen you are considering deleting a master data object.

You can search in the following sub-objects:

� SAP SNC alerts� Partner-dependent location product� Partner-dependent product� cFolders for SCM collaboration� SAP SNC content in condition technique� SAP SNC inventory management (LIME)� SAP SNC order documents

� Replenishment order� Purchase order� Work order� Kanban� Return delivery instruction� Invoice� Release� Advanced shipping notification� Supplier confirmation� Promotion� Planned replenishment orders

� SAP SNC settings (Web GUI and SAP GUI)� SAP SNC time series types

The where-used framework only considers the time-series types that areconsidered in release 5.1.

Forward navigation is only possible to the SAP GUI screens, not to the SAP SNCWeb screens.



Deletion of Master DataBefore you delete master data, check thoroughly whether the master data is stillbeing used in SAP SNC.

Note: You can use the where-used list to check if a product is still beingused in SAP SNC.

Caution: Do not delete any master data that SAP SNC is still using (inother words, for which transaction data still exists).

Consider all master data here that is relevant to SAP SNC. This includes thefollowing:

� Planning version 000� Business partners� Product� Location� Location product� Transportation lane� External procurement relationship� Transportation zones� The following specific master data that you create in the Web application

menu in SAP SNC:

� Packing master data (such as packaging specifications)� Partner-specific data (such as partner-specific product numbers)� Number ranges

CustomizingThere are only a few master-data-related Customizing settings in SAP SNC.



Output format of product numberIn this customizing transaction you determine the following:

� Maximum input and output length of the product number: The lengthcan be up to 40 characters.

� Template for displaying the product number (online or print): You musttype an underscore at every place in the product number that shouldnot contain template characters.

� Display with or without leading zeros� Storage type of the product number

Note: By default, SAP SCM stores products with a length of 40places. SAP ERP only stores 18 places. If you connect your SAPERP System to SAP SNC it might be a good idea to change theproduct length in SAP SNC to 18 places if there is no impact onother SAP SCM components, like APO or EM.

You can make these settings in the SAP SNC IMG by choosing SCM Basis→ Master Data→ Product→ Specify Output Format of Product Number.

Number ranges for business partnerWhen transferring master data from a connected back-end system, you mightwant to create business partners automatically. In this case, you require anexternal number range is required for your master data. If, for example,you want to transfer supplier master data from your SAP ERP back end toSAP SNC and you want the SNC system to automatically create businesspartners of type organization for the suppliers, the external number rangefor the business partner must fit to the number range for suppliers in yourback-end system.To access this customizing from the IMG, choose Cross-ApplicationComponents→ SAP Business Partner→ Business Partner→ Basic Settings→ Number Ranges and Grouping→ Define Number Ranges. In thisCustomizing screen, create an entry that fits your requirements, does notoverlap with any other interval, and has the Ext flag set.After defining the number range, you need to assign it to a grouping in theIMG underCross-Application Components→ SAP Business Partner→Business Partner→ Basic Settings→ Number Ranges and Grouping→Define Groupings and Assign Number Ranges.



Lesson Summary

You should now be able to:� Name the relevant master data for supplier collaboration with SAP SNC� Explain which master data objects are integrated from SAP ERP and which

are maintained in SAP SNC� Discuss the business partner concept



Lesson: Master Data Integration

Lesson OverviewIn this lesson you will learn about master data integration in SAP SNC and how toset up an automated master data transfer.


� Explain how master data is integrated to SAP SNC� Understand how to use the Core Interface� Explain what need to be considered for an automated data transfer

Business Example

SAP R/3 Plug-InSAP R/3 plug-ins are interfaces that enable the exchange of data between one ormore SAP R/3 systems and other SAP components. SAP R/3 plug-ins supplythe SAP components from SAP R/3 3.1I to SAP ECC 5.00 with transaction andmaster data in real time. They enable you to use SAP application components suchas SAP SCM or SAP CRM along with certain SAP industry-specific components.All SAP industry-specific components based on SAP R/3 4.6B or higher requireSAP R/3 plug-ins. SAP R/3 plug-ins are add-ons to SAP R/3.

SAP ECC 6.0 and later releases will contain all the interfaces necessary fortechnical integration with other SAP components. These interfaces werepreviously part of the SAP R/3 plug-in.

Integration via the Core InterfaceIntegration via the Core Interface (CIF) enables data to be exchanged betweenan ERP system i (such as SAP R/3, SAP R/3 Enterprise, or SAP ECC) and aconnected SCM system. On the SCM side, CIF is part of SCM Basis and can beused by all systems that contain SCM Basis.

CIF Customizing in the ERP SystemCIF Customizing in the ERP system is used to set up the system infrastructureand to configure the data transfer via CIF. CIF Customizing also coversapplication-specific settings and enhancements for CIF.


SNC100 Lesson: Master Data Integration

An Implementation Guide (IMG) is available for Customizing. The IMG providesyou with a clear overview and explanation of all steps that are necessary forintegration via CIF. With the exception of organizational IMG activities that onlycontain a description, you can go directly to the relevant transaction and executethe action.

The IMG consists of three main areas:

� Basic settings for creating the system landscape

Here you can find all the IMG activities that are necessary for partnersystems to communicate with one another via CIF. This includes naminglogical systems, naming an RFC destination, and making qRFC settings.

� Basic settings for data transfer

Here you can find all the IMG activities that are necessary for data transfers,that is, the initial data transfer and change transfers.

� Application-specific settings and enhancements

Here you can find customer exits, Business Add-Ins (BAdIs), and settingsfor individual applications.

Calling the IMG

� In SAP R/3 4.0B and 4.5B, you call the IMG using transaction PIMG.� As of SAP R/3 4.6B, you can find the IMG in the SAP Reference IMG by

choosing Integration with Other SAP Components→ Advanced Planningand Optimization.

Some of the basic settings are target-system-dependent or client-specific. Thesesettings are not transported from the Customizing client to the productive client.This means you also have to make the settings in the productive client. You mayalso have to make changes in the productive system for some other settings. Thefollowing table contains a list of these settings and information about how you canmake these settings in the productive system.

Setting Path in CIF Menu** TransactionCode

Define logical system In the ALE menu* under Sendingand Receiving Systems→ LogicalSystem

BD54

Assign logical systemsto a client

In the ALE menu* under Sendingand Receiving Systems→ LogicalSystem

SCC4

Specify SAP SCMrelease

In the CIF menu** under Settings NDV2

Set RFC destination In the CIF menu** under Settings SM59



* Access the ALE menu by using transaction SALE.

** Access the CIF menu in the SAP menu by choosing Logistics→ CentralFunctions→ Supply Chain Planning Interface→ Core Interface AdvancedPlanner and Optimizer.

CIF Customizing in the SCM SystemCIF Customizing in the SCM system is used to set up the system infrastructureand to configure the data transfer between an SCM system and the ERP systemvia the Core Interface (CIF). CIF Customizing also covers application-specificsettings and enhancements.

An Implementation Guide (IMG) is available for CIF Customizing. The IMGprovides you with a clear overview and explanation of all steps that are necessaryfor integration via CIF. With the exception of organizational IMG activities thatonly contain a description, you can go directly to the relevant transaction andexecute the action.

The Implementation Guide for CIF consists of three main areas:

� Basic settings for creating the system landscape

Here you can find all the IMG activities that are necessary for the partnersystems to be able to communicate with one another via CIF. This includesnaming logical systems, naming an RFC destination, and making qRFCsettings.

� Basic settings for the data transfer

Here you can find all the IMG activities that are necessary for data transfers,that is, the initial data transfer and change transfers.

� Application-specific settings and enhancements

Here you can find customer exits, BAdIs, and settings for individualapplications.

Calling the IMG

� If your SCM system is SAP Advanced Planning and Optimization, inthe SAP Reference IMG, choose Integration with SAP Components→Integration via Core Interface (CIF) .

� If you work with a different SCM system, in the SAP Reference IMG,choose SCM Basis→ Integration.



Setting Path in CIF Customizing** TransactionCode

Define logical system In the ALE menu* under Sendingand Receiving Systems→ LogicalSystem

BD54

Assign logical systemsto a client

In the ALE menu* under Sendingand Receiving Systems→ LogicalSystem

SCC4

Define the RFCdestination

In the CIF customizing** underSettings

SM59

Maintain businesssystem group


/SAPAPO/C1

Assign logical systemand queue typeIf you set the InboundQueue queue type inthe SCM system, youhave to register CIFqueues (CF*) in the QINscheduler in the ERPsystem.


/SAPAPO/C2

Register CIF queues inthe QIN scheduler ifyou have changed toinbound queues in theERP system

SMQR

* Access the ALE menu by using transaction SALE.

**If your SCM system is SAP Advanced Planning and Optimization, in the SAPReference IMG, choose Integration with SAP Components→ Integration via CoreInterface (CIF). If you work with a different SCM system, in the SAP ReferenceIMG, choose SCM Basis→ Integration.

Data TransferFrom the CIF menu in the SAP ERP system, you can access individual functionsof the Core Interface.

As of SAP R/3 4.6B, you call the CIF menu via the SAP Easy Access menu.Choose SAP Menu→ Logistics→ Central Functions→ Supply Chain PlanningInterface→ Core Interface Advanced Planner and Optimizer.



Integration ModelThe integration model controls the transfer of master data and transaction data. Itis generated in the ERP system and contains all data that is to be transferred to theSCM system. It is uniquely identified by name and application.

Only those data objects are transferred from the ERP system that are needed in theSCM system. These data objects are specified in the integration model.



Generating integration modelsWhen you generate an integration model, you specify which data objects areto be selected from the total dataset in the ERP system for the transfer.To create the integration model, you first select the object types (forexample, material masters) on the Create Integration Model selection screen.Next, you select specific selection criteria (in most cases, a material/plantcombination) that further restrict the object types you have already selected.If you have already selected Material Masters, for example, you couldnow enter an MRP controller. In this way, you define filter objects. Filterobjects are used to select which data objects are transferred to a specifiedSCM system. In the example, all material masters for a particular MRPcontroller are selected.

Working with variantsSince the system does not save your selection options, you have tosave the settings as a variant on the selection screen. Variants allowyou to reuse the settings you saved whenever you want. If you wantto recreate an integration model at a later point in time, you can callup the required variant by choosing Select Variant in the toolbar atthe top of the selection screen.

Integration model versionsIf you regenerate an integration model, the system automaticallygenerates a new version of this model. Different versions of anintegration model are distinguished by their date and time of creation,as well as by the filter objects they contain. You can create as manyversions of an integration model as you want. However, only oneversion may be active at any time.

Results and savingTo display the results list, choose Execute . You will see a listdisplaying the results of the selection, that is, the type and (total)quantity of the selected filter objects.You can navigate to the detailed view for each filter object. Select thefilter object you want to view and choose Details. You will see a list ofall data entries that were found for the selected filter object.Leave the screen by choosing Back.Generate the integration model. A dialog box confirms that theintegration model was generated successfully.



Activation and deactivation of integration modelsThe activation of integration models results in an initial transfer. As standard,the integration models to be activated are compared with the integrationmodels that are already active. In this way, the transfer restricts itself todifferences, in other words, only data for filter objects that are not containedin an active integration model is transferred.

Hint: To retransfer all data records, you have to deactivate and thenreactivate all active integration models.

You can generate multiple integration models. However, only one versioncan be activated for each model. You can activate and deactivate severalintegration models simultaneously.Integration models must remain active to enable change transfer.You can also call this report (RIMODACT) using transaction CFM2.The Activate or Deactivate Integration Model screen appears.The selection screen displays the available integration models for the modelname you specified.You can activate the required model by double-clicking it or by choosingActive/Inactive. A checkmark is displayed to the left of the modelgeneration date and time shows that the integration model has been activated.In newer plug-in / ERP versions, the OK icon is shown to the right of themodel generation date and time in the New Status column.If you wish to deactivate the integration model, repeat the above procedureand ensure that the OK icon is no longer displayed.In newer plug-in / ERP versions, after deactivating the model, the OK iconwill disappear and an X will be shown in the New Status column.Choose Start to begin the data transfer. The data is transferred in thebackground.

Note: Deactivating an integration model does not lead to thedeactivation or deletion of the corresponding objects in the SCMsystem.

Change Transfer for Master DataThe change transfer for master data covers:

� Creating new master data whose selection criteria match those of anactive integration model, and then the subsequent transfer

� Making changes to master data and transferring them

Initial Creation of Master Data



You create new master data in the ERP system because this is thesuperordinate master data system. New master data objects withselection criteria that correspond to an existing integration model (forexample, the same MRP type) are not automatically included in thisintegration model in the ERP system or transferred. There are twoprocedures available for making the transfer:Periodic transfer using background processingIn this procedure, a new version of the corresponding integration modelis created and activated for master data that has been created in theERP system. Although this may be done manually, for performancereasons we recommend that you set up a periodic background job torun at times when the system load is low (for example, at night). In thebackground job, the reports should run in sequence. This procedureoffers the following advantages:

� Master data that has been created recently and that meets theselection criteria of integration models that already exist isincluded in these integration models and transferred to the targetsystem.

� Master data that has been changed to such an extent that it nolonger meets the selection criteria of the corresponding integrationmodel is excluded from the transfer.

� Master data (material, customer, vendor, and source of supply)that has been changed since the last transfer is re-transferred andwill now be up to date.

Online transfer using Business Transaction EventsAs of SAP R/3 plug-in 2000.2, you can create info objects in the ERPsystem that correspond to the selection criteria of an existing integrationmodel, and then immediately transfer them when they are posted.The system automatically creates a new version of the correspondingintegration model and activates it in the background.

Caution: This procedure for the creation of new masterdata should only be used in exceptional cases. This can, inparticular, lead to problems if dependent objects exist. In mostcases, it is better to use a periodic transfer with backgroundprocessing. In particular, in cases where you are transferringlarge amounts of master data to an ERP system using ALEor batch input, forwarding should be batch-controlled ratherthan batch-triggered.

Changes to master dataIn most cases, you make changes to master data in the ERP systembecause this is the superordinate system for master data. There aretwo different scenarios for this:



Changes to master data fields that are already contained in anactive integration modelThe ERP system marks these changes using change pointers.When the integration model is activated, the system automaticallyevaluates all change pointers and transfers the corresponding masterdata records to the target system. Only the master data records thathave been changed are transferred, not all of the data records that arecontained in the integration model.Changes to master data fields relevant to filteringThese changes mean that certain master data entries now fulfill theselection criteria of an existing integration model. Fields relevant tofiltering are those that are given in the General Selection Options forMaterials section of the selection screen for the integration model(material type, plant-specific material status, MRP controller, MRPtype, and ABC indicator).When creating a new version of the integration model, CIF transfers themaster data record that now meets the selection criteria, including alldependent objects.

Example for background jobConsidering all the given information, a suggestion for a jobchain forbackground processing would be:

1. Delete old inactive integration models (report RIMODDEL)2. Process changepointers (report RCPTRAN4)3. Generate new integration model (report RIMODGEN)4. Activate new integration model (report RIMODAC2)

Alternative Method to Transfer Master DataIf you are not using an SAP back-end system, you may transfer the master datathrough BAPIs.

BAPIA standardized programming interface that facilitates external access tobusiness processes and data in the SAP system.You define BAPIs in the Business Object Repository (BOR) as methods ofSAP business objects or SAP interface types.BAPIs offer an object-oriented view of business components in the SAPsystem. They are implemented and stored as RFC-enabled function modulesin the Function Builder of the ABAP Workbench.



SAP SNC provides you with the folllowing BAPIs:

� BAPI_PRDSRVAPS_SAVEMULTI2 (Product)� BAPI_LOCSRVAPS_SAVEMULTI2 (Location)� BAPI_TRLSRVAPS_SAVEMULTI2 (Transportation Lane)



Lesson Summary

You should now be able to:� Explain how master data is integrated to SAP SNC� Understand how to use the Core Interface� Explain what need to be considered for an automated data transfer


SNC100 Lesson: Visibility Concept

Lesson: Visibility Concept

Lesson OverviewThis lesson will explain the visibility concept of SAP SNC.


� Explain the visibility concept of SAP SNC

Business Example

BackgroundData for a location product is only visible to a user on the Web UI for SAP SupplyNetwork Collaboration (SAP SNC) if the user has authorization to display orchange the location product. The user can therefore only display transaction datafor a location product in an application (for example, the stock situation in the SMIMonitor) if he or she has the appropriate authorization; the user can likewise onlysee the product name or location name in the input help for products and locationsif he or she has the appropriate authorization.

In SAP SNC, there are additional filters, known as selection modes. A selectionmode controls which data a business partner user is able to see in an application. Adefault selection mode is assigned in Customizing to each SAP SNC application.For some applications, alternate selection modes are available.

Caution: If a business partner is not assigned to a user, he or she can seeall data for which he or she has authorization according to the user role.

Each selection mode is assigned to one of the following visibility concepts:

User-partner-based visibility conceptThis visibility concept restricts the visibility of a business partner user in anSAP SNC application to the master data and transaction data that is relevantand allowed for the business partner based on his or her role in the supplychain. This is important, for example, if a customer has links to severalsuppliers but the suppliers themselves should not see the other suppliers' data.

Profile-based and parameter-based visibility conceptThis is a special visibility concept for the SNI Monitor; it is based onvisibility control profiles that you can assign to each user or business partner.



Partner-Dependent Network Filter (PDNF)The partner-dependent network filter (PDNF) belongs to the user-partner-basedselection modes.

The user is allowed to see following data:

� All locations of the assigned business partner� All location products in locations of the assigned business partner� All transportation lanes for which a business partner location is either ship-to

location or ship-from location� All location products in other locations for which a transportation lane is

defined with a business partner location� All business partners to who own locations for which a transportation lane is

defined with an assigned business partner location� Alerts for the named objects

The following additional restrictions apply, depending on the selected view:

� The supplier view only displays data for products for which the assignedbusiness partner is supplier.

� The customer view only displays data for products for which the assignedbusiness partner is customer.

Figure 58: Master Data / Model Overview



Selection Modes Based on Order Documents(ODM_xxx)Selection based on order document management (ODM) belongs to theuser-partner-based selection modes.

There are selection modes available for the various applications for processingorder documents (such as purchase orders and scheduling agreement releases) thatdetermine the visible documents and data as follows:

� A user at a supplier can use the supplier view to see documents in which thatsupplier is entered as the supplier.

� A user at a customer can use the customer view to see documents in whichthat customer is entered as the customer.

� A user at a goods recipient can use the goods recipient view to see documentsin which that goods recipient is entered as the goods recipient.

The location names and product names of the location products from thesedocuments are available in the input help (provided that the user authorizationallows these locations and products to be displayed). If purchase orders andscheduling agreement releases do not exist in the system, there are no locations orproducts available in the input help for ASN processing. If the user at a suppliernevertheless wants to create an ASN without a purchasing document, he or shemust manually enter the product and the ship-from location of the supplier.

Master DataMaster-data-based selection belongs to the user-partner-based selection modes.

With this selection mode, the user sees data for location products for which heor she has authorization. The locations and products of these location productsare available in the input help.

Profile-Based and Parameter-Based VisibilityData for a location product is only visible to a user on the SAP SNC Web UI ifthe user has authorization to display or change the location product. You can usethe profile-based and parameter-based visibility concepts to filter master dataand movement data. You filter the data by creating profiles for users or businesspartners that define which data a business partner is allowed to display.

This allows you, for example, to grant the following business partners access onlyto selected data in SAP SNC:

� Suppliers� Suppliers of a supplier� Third-party logistics provider



You can create visibility control profiles and assign users and business partners. Ina profile, you can control the visibility of data in the following ways:

� Restrict visibility to specific master data, such as locations, products, orsuppliers

� Restrict the visibility through the Assigned Partner, Data-Providing Partner,and Owner parameters.

You can use these parameters to restrict the visibility of the data even further.For example, if you enter the parameter Owner and business partner A, youcan ensure that a user with this visibility control profile can only see themaster data and movement data for which business partner A is the owner.

Assignment of visibility control profilesYou can assign one or more visibility control profiles to a user or businesspartner, and delete assignments that are not needed. You can do this byusing the following functions:

� With the Application Data ID field, you restrict the visibility controlprofile to selected Web UIs.

Note: You can only select application data IDs for SNI(technical name: SNI).

� You can restrict the validity of the profile to a time period.� You can use the Execute function to display all visibility control profiles

that are assigned to a user or business partner within a validity period.� You can use the User/Prtnr's Own Data Visible indicator to determine

the following: If a user is assigned to a business partner, he or she isallowed to display all products that lie in locations belonging to his orher assigned business partner. You can set this indicator to allow a userto access his or her own data without first having to define a profile.

Note the following ranking sequence when you create visibility controlprofiles:

� Settings in a visibility control profile for a business partner useroverride the settings in a visibility control profile for a business partner.

� Settings in a visibility control profile for an SNI application overridethe settings in a visibility control profile that is valid for all SNIapplications.

Displaying visible dataYou can use the Visible Data function (transaction /SCF/SNC_VIS_DATA)to obtain an overview of which data is displayed to a user or business partnerwho has the specified profiles.



Configuration OptionsOne selection mode is defined for each application data ID. In the standardsystem, the applications use the selection modes described above by default. Forsome applications, alternative selection modes are available. If required, you canconfigure them in Customizing for Supply Network Collaboration by choosingBasic Settings→ Visibility.

Hint: You can find the link between application data ID and screen ID intable /SCF/APPDATAASS.

If required, you can also create user-defined selection modes inCustomizing for visibility and program the selection logic using the BAdI/SCF/BADI_SELECTION. You can also use the BAdI to modify the selectionlogic for existing selection modes.



Lesson Summary

You should now be able to:� Explain the visibility concept of SAP SNC


SNC100 Unit Summary

Unit SummaryYou should now be able to:� Name the relevant master data for supplier collaboration with SAP SNC� Explain which master data objects are integrated from SAP ERP and which

are maintained in SAP SNC� Discuss the business partner concept� Explain how master data is integrated to SAP SNC� Understand how to use the Core Interface� Explain what need to be considered for an automated data transfer� Explain the visibility concept of SAP SNC


Unit Summary SNC100


Unit 7Supplier Managed Inventory Process

(SNC)

Unit OverviewIn this unit, you will gain deeper insight into the supplier managed inventoryprocess within SAP SNC.


� Explain the SMI process flow� Name the SMI alerts� Explain the difference between SMI and SMI with replenishment order� Use SMI process in SAP SNC� Make the necessary system settings to run an SMI scenario� Explain Customizing for the data matrix

Unit ContentsLesson: Supplier Managed Inventory Process in SAP SNC ... . . . . . . . . . . .236Lesson: Process Demo & Exercise: SMI Process .. . . . . . . . . . . . . . . . . . . . . . . .253

Exercise 7: SMI with SAP SNC.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255Lesson: Relevant System Settings and Customizing for SMI in SAPSNC.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267


Unit 7: Supplier Managed Inventory Process (SNC) SNC100

Lesson: Supplier Managed Inventory Process in SAPSNC

Lesson OverviewThis lesson will introduce you to the supplier-managed inventory (SMI) processin SAP SNC.


� Explain the SMI process flow� Name the SMI alerts� Explain the difference between SMI and SMI with replenishment order

Business Example

BackgroundThe SMI Monitor is found on the SAP Supply Network Collaboration (SAP SNC)Web UI, and it supports the supplier-managed inventory (SMI) business scenario.Customers and suppliers can use the SMI Monitor to monitor the demand andstock situation of selected products at the customer location. The SMI Monitoralso gives a quick overview of critical stock situations. Customers transfer demandand stock data from their backend system to SAP SNC. The SMI Monitor gives aperiod-orientated, time-series-based view of this data.

Suppliers use the SMI Monitor to plan the quantities that they want to supply tothe customer (receipts). The most important key figure for planning with the SMIMonitor is the projected stock, which gives information about the demand/stockbalance of a customer location product in a period. SAP SNC compares theprojected stock with the minimum and maximum stock levels of the customerlocation product agreed upon between the customer and the supplier. If thesestock thresholds are violated, SAP SNC generates alerts. In the SMI scenario, thesupplier must enter the planned receipts so that the projected stock does not exceedor fall below the maximum or minimum stock levels.

The customer can use the Simulation function to enter planned receipts and tocheck the effect they would have on the projected stock. Unlike the supplier, thecustomer cannot manually save the planned receipts.


SNC100 Lesson: Supplier Managed Inventory Process in SAP SNC

If you are using alert notifications, you only have to call the SMI Monitor whenan exceptional situation occurs that requires your intervention. You can specifythat SAP SNC informs a user automatically (for example, by e-mail or fax) if analert has occurred that is relevant for him or her.

Planned receipts are not binding. If the supplier wants to inform the customerabout a delivery so that it is binding, he or she can call SAP SNC ASN processingin the SMI Monitor or in the due list for planned receipts, create a binding ASNfor a planned receipt, and send it to the customer.

Planned receipts are only visible in the SMI Monitor, not in the customer backendsystem. In the business scenario SMI with replenishment order, the supplier cancreate a replenishment order for a planned receipt in the SMI Monitor. Customerscan transfer the replenishment order to their backend system, where it is visible asa firm receipt for requirements planning at the customer.

If you want to rate the supplier on the basis of alerts, you can use alert-based rating.

Figure 59: SMI Process Overview

Data TransferThe customer uses the XML message ProductActivityNotification to transferdemand and stock data to SAP SNC for the SMI Monitor. If customers use an SAPbackend system, they can us report RSMIPROACT to transfer the data.



Multisourcing in the SMI ScenarioThe SMI Monitor supports multisourcing for customer location products.Multisourcing means that customers procure a product for their customer locationfrom different ship-from locations. The ship-from locations can belong to differentsuppliers. For the different suppliers, different planning parameters, such asminimum or maximum stock levels, may be necessary for the customer locationproduct. You can set up the SMI planning parameters on the SAP SNC Web UI,depending on the supplier at supplier-customer location-product level.

Master Data for SMIMaster Data for SNC has been covered already. In addition to these master dataobjects SMI requires the min and max level per product.

In the SMI process, the supplier is responsible for replenishment. He or sheperforms the replenishment based on the customer's inventory and demandsituation. The supplier keeps the inventory levels of a certain product betweenagreed boundaries -- a maximum stock level and a minimum stock level.

This data is stored in the product master and can also be transferred via the SCMCore Interface from an SAP backend system to SAP SNC.

The max stock level is transferred from the MRP1 tab in the similarly namedfield in the SAP ERP material master.

The min stock level is transferred from the Safety Stock field on the MRP2 tab.



ProcessThe process runs as follows:

1. Publish current stock status and gross demand.

The customer publishes the current stock status and the gross demand in hisor her ERP system. The ERP system transfers the PROACT.PROACT01IDoc to the customer�s SAP NetWeaver system. The SAP NetWeaver systemconverts the IDoc into an XML message of type ProductActivityNotificationand transfers it to SAP SNC.

2. Display current stock status in SAP SNC.3. Publish advanced shipping notification (supplier�s ERP system).


Caution: Note that the IDocs, XML messages, and mappingsdepend on which ERP system and releases are being used. Mappingsare sometimes required for the message flow between the supplier�ssystem and SAP SNC. Since the mappings are dependent on thesupplier�s system, they cannot be predefined in the SAP SNCstandard delivery. You must create the mappings as part of a projectsolution.

4. Receive advanced shipping notification, or create shipping notification in theSAP SNC Web UI.

If suppliers do not use an ERP system to send advanced shippingnotifications, they can create them in the Web UI. The SAP SNC systemtransfers an XML message of type DespatchedDeliveryNotificationtothe SAP NetWeaver system, which converts the message into the IDocDESADV.DELVRY03 and transfers it to the customer�s ERP system.

5. Receive advanced shipping notification (customer�s ERP system).6. When the customer posts the goods receipt, the customer�s ERP system

sends the STPPOD.DELVRY03 IDoc to the SAP NetWeaver system. TheSAP NetWeaver system converts the IDoc into an XML message of typeReceivedDeliveryNotification and transfers it to SAP SNC.

7. Display goods receipt information (SAP SNC).

SMI Monitor Details ScreenDemand, receipt, and stock data are displayed in the SMI Monitor � Details screenfor the selected customer location products.



The following provides an overview of the key figures on the Grid tab page.

DemandThis key figure represents the sum of the demands in a period that arerelevant for the scenario in question.

Average DemandThis key figure represents a demand that SAP SNC determines by averagingthe actual demands.The quality of demand data that the customer sends to SAP Supply NetworkCollaboration (SAP SNC) can vary greatly depending on the forecastingtechnique the customer is using. SAP SNC therefore uses averagingmethods to calculate the average of the actual demands for a particularaverage-demand horizon. SAP SNC displays the average demands in theplanning grid in the Average Demand key figure of the SMI Monitor and theMin/Max Replenishment monitor.The following averaging methods are available:

� Moving average calculation method

With this method, SAP SNC calculates the average demand based onmoving averages calculated from three average demand sets.

� Arithmetic mean calculation method

As an alternative to the standard averaging methods, the BAdICalculation of Average Demand (/SCA/SMI_AVG_DEMAND) allowsyou to implement your own average demand calculation.

Raw Net DemandThis quantity is the result of a replenishment run. It indicates how much is tobe shipped (and consequently received by the customer) at what time andfrom which source.

Planned ReceiptThis key figure represents the planned, rounded total quantity that thesupplier wants to send to the customer in a specific period. The PlannedReceipt row is the only row in the planning grid that suppliers can edit.They can enter quantities manually, or the system can automatically proposequantities. The end of the period is the planned time of arrival at thecustomer.Planned receipts are visible to the customer but are not yet firm. As asupplier, you can create deliveries based on the planned receipts and createbinding advanced shipping notifications (ASNs). This reduces the quantitiesof the planned receipts. The ASN quantities are automatically included inthe In-Transit Quantity key figure.



In-Transit QuantityThis key figure represents the total quantity that the customer can expect in aspecific period. The supplier has already sent the deliveries and, and usingASNs, has informed the customer about the expected deliveries.SAP SNC automatically reduces the in-transit quantity when the customersends SAP SNC a goods receipt confirmation or, in SAP SNC, manuallyconfirms the goods receipt in ASN processing. The customer�s warehousestock increases at goods receipt.

Projected StockThis key figure represents the demand and stock balance, which is thestock to be available at the customer at the end of the period. SAP SNCautomatically calculates the projected stock from demand and stock data.SAP SNC adds the anticipated warehouse stock at the start of the period,the planned receipts, and the in-transit quantity in the period, and subtractsthe demands.If the projected stock has a critical value at the end of a period, this period isautomatically highlighted in color in the SMI Monitor.

Days� SupplyThis key figure represents the days� supply of projected stock for a period indays. This value specifies how many days the projected stock of a periodwill last to cover the demands of subsequent periods.

Minimum ProposalThis key figure represents the quantity that the supplier has to deliver tothe customer in this period so that the projected stock reaches the agreedminimum stock level of the location product at the end of the period. SAPSNC automatically determines the minimum proposal.

Maximum ProposalThis key figure represents the quantity that the supplier has to deliver tothe customer in this period so that the projected stock reaches the agreedmaximum stock level of the location product at the end of the period. SAPSNC automatically determines the maximum proposal.

Minimum Stock LevelThis key figure represents the minimum stock level that SAP SNC hascalculated automatically from the safety days� supply of the location product.

Maximum Stock levelThis key figure represents the maximum stock level that SAP SNC hascalculated automatically from the target days� supply of the location product.

The following provides an overview of the data in the Product Data tab page:



SoH (stock on hand)Stock available at the customerThe stock on hand comprises the stock taken into account in the formulafor calculating the projected stock. In the standard system, this is only theunrestricted-use stock.

B/C Stk (blocked/consignment stock)Stock at the customer location that cannot be used.You cannot take account of this stock when calculating the projected stock.

Last Update Inv.Point in time at which inventory last changedThe time entry refers to the time zone of the user who is logged on to thesystem.

Unrestr./Cons. StockStock in the warehouse at the customer location that is freely available atthe time of planning

Min/Max StkMinimum and maximum stock level of a product agreed upon by customerand supplier

LP Sts (Location Product Status)

Last Update DemPoint in time at which demands last changedThe time entry refers to the time zone of the user who is logged on to thesystem.

Q/C StkStock that the customer is putting through a quality inspection at the timeof planning

Last Update ASNPoint in time at which ASNs last changedThe time entry refers to the time zone of the user who is logged on to thesystem.



Lead TimeScheduled time span between sending a delivery from the ship-from locationand the probable arrival at the location receiving the deliverySAP SNC uses lead time as follows:

� For scheduling

If a document contains only the delivery date/time or only the shippingdate/time, SAP SNC calculates the complementary date/time usingscheduling.

� For alerts

As supplier, you cannot cover customer requirements that lie within thelead time in the usual way. SAP SNC generates an alert if the projectedstock within the lead time reaches a critical value.

As the lead time, SAP SNC uses the transportation duration of a meansof transport that you have assigned to the transportation lane between theship-from location and the receiving location. SAP SNC uses the followingtransportation lanes:

� If the customer and the goods recipient are the same, the delivery goesto the customer location. The transportation lane between the ship-fromlocation and the customer location is relevant here.

� If the goods recipient is different from the customer, the delivery goesto the ship-to location. The transportation lane between ship-from andship-to locations is relevant here, if it exists. If this transportation lanedoes not exist, SAP SNC uses the transportation lane between theship-from and the customer locations.

If you have assigned several means of transport to a transportation lane, SAPSNC uses the transportation duration of the slowest means of transport.

Calculating the Projected StockThe projected stock is a key figure in Supply Network Inventory and inreplenishment planning (for example, in the SMI Monitor). The system calculatesthe projected stock from demands, receipts, and stocks. The projected stockprovides information about the demand/stock balance of a location product ina period. The projected stock is the stock of a product that is expected to beavailable at the location at the end of a period. As customer or supplier, you cantell from this key figure how the demand/stock balance develops over time andwhether critical stock situations occur.

In replenishment planning, the system proposes planned receipts (depending onthe replenishment planning method) so that the projected stock reaches a certainvalue. For example, if the projected stock drops to the minimum stock level inthe supplier-managed inventory business scenario, the system generates a plannedreceipt that returns the projected stock to the maximum stock level.



Calculation ProcedureTo calculate projected stocks for a location product, the system starts with thesituation on the current day and first calculates the projected stock for thisday. This is the stock that is expected to be available in the location at the endof this day. Based on this value, the system calculates the projected stock forthe following day by adding the demands and receipts from the current day.Based on this value, the system calculates the projected stock for the day afternext, and so on. The following provides an overview of the calculation steps.

Today's projected stockToday�s projected stock =stock+ all receipts with delivery date up to and including today� all demands with demand date up to and including today

Tomorrow's projected stockTomorrow's projected stock =today�s projected stock+ receipts with delivery date tomorrow� demands with demand date tomorrow

Projected stock on any later dayProjected stock of this day =projected stock of the previous day+ receipts with delivery date on this day− demands with demand date on this day

User-Defined SettingsYou can make the following user-defined settings in Supply NetworkCollaboration Customizing:

� You can define your own formulas for calculating the projectstock, taking other key figures or stock types into account. ChooseReplenishment→ Replenishment Planning→ Projected Stock.

� Choose Replenishment→ Replenishment Planning→ Assign Settingsto configure a different standard formula for the following applications:

� Supply Network Inventory� Replenishment planning with promotions� Replenishment planning without promotions

Hint: If you want to calculate the stock on hand of a location productin a different way, use the /SCA/ICH_STOCKONHAND BAdI.



Critical situations for the projected stockIf the projected stock in a period has a critical value, this period isautomatically highlighted in the SMI Monitor. Critical situations in theSMI Monitor include:

� The projected stock falls to or below zero.� The projected stock falls below the minimum stock level.� The projected stock exceeds the maximum stock level.The system also generates corresponding alerts.

Updating the Planned Receipts key figureWhen ASNs and replenishment orders are published, the system also updatesthe Planned Receipts key figure based on the formula used for the projectedstock:

� If the formula for the projected stock contains the In Transit key figurebut not the Firm Receipts key figure (published replenishment orders),SAP SNC reduces the Planned Receipts key figure by the publishedASN quantity.

� If the formula for the projected stock contains both the In Transit keyfigure and the Firm Receipts key figure, the system reduces the plannedreceipts published replenishment order quantity, rather than by thepublished ASN quantity.

Replenishment Order CollaborationIn SAP SNC, the supplier performs replenishment planning based on the stock anddemand data that the customer has sent to SAP SNC. This planning determineswhich quantities of products the supplier is to deliver to the customer and inwhich periods. After replenishment planning, the supplier creates correspondingreplenishment orders. Replenishment orders only exist in SAP SNC. To supportthe backend processes in the supplier backend system (sales order processing,goods issue) and in the customer backend system (purchase order processing,goods receipt), the supplier sends the replenishment orders to the backend systems.The customer backend system uses the replenishment order to create a purchaseorder. The supplier backend system uses the replenishment order to create a salesorder.



SAP SNC supports replenishment order collaboration in the following scenarios:

� Responsive replenishment

Responsive replenishment is part of customer collaboration and thus notpart of this course.

� Supplier-managed inventory with replenishment orders

In this scenario, the customer has an SAP SNC system connected to his orher backend system. The customer sends data about his or her demand andstocks to SAP SNC. The supplier uses the Min/Max Replenishment monitorto plan which products will be delivered to which customer location onwhat date. In doing so, the supplier creates planned receipts. As part of thisscenario, SAP SNC allows the supplier to create replenishment orders basedon these planned receipts. These replenishment orders are then sent to thecustomer backend system, where they are used to create a purchase order, andto the supplier backend system, where they are used to create sales orders.

Replenishment OrderA replenishment order is an order that a supplier creates in SAP SNC to informabout certain quantities of products that he or she intends to deliver to a customeron a certain date and time.

In SAP SNC, a replenishment order is an order of order document type VGOR.

A replenishment order is transferred to the customer and supplier backend systemsusing XML messages. The customer backend system uses the replenishment orderto create a purchase order. The supplier backend system uses the replenishmentorder to create a sales order.

The supplier can create replenishment orders in the following ways:

� Manually create replenishment orders in the Due List for Planned Receiptsscreen (SMI scenario)

� Manually using the Create RO screen

Publication of Replenishment OrdersA replenishment order is an object that only exists in SAP SNC. To support theprocesses in the customer backend system (purchase order processing, goodsreceipt) and in the supplier backend system (sales order processing, goodsissue), you must send a replenishment order that you created in SAP SNCto the customer and supplier backend systems. This means sending an XMLmessage of type VendorGeneratedOrderNotification to the customer backendsystem, where a purchase order is then created, and an XML message of typeReplenishmentOrderNotification to the supplier backend system, where a salesorder is then created.



Caution: Note that the IDocs, XML messages, and mappings depend onwhich ERP system and releases are being used. Mappings are sometimesrequired for the message flow between the supplier�s system and SAPSNC, depending on the supplier�s system. Since the mappings aredependent on the supplier�s system, they cannot be predefined in theSAP SNC standard delivery. You must create the mappings as part of aproject solution.

Creating ASNs for Replenishment Order ItemsIf the supplier wants to inform the customer about an impending delivery for areplenishment order, he or she can use the SAP SNC Web UI to manually createand publish an advanced shipping notification (ASN) relating to the replenishmentorder. SAP SNC sends this ASN to the customer backend system using an XMLmessage DespatchedDeliveryNotification. Alternately, the supplier can createthe ASN in his or her own backend system and send it to SAP SNC. SAP SNCthen forwards the ASN to the customer.

SMI with Replenishment OrdersThis process describes how you can use replenishment orders in the SupplierManaged inventory business scenario.

Figure 60: SMI with Replenishment Orders



In this business scenario, the customer sends his or her gross demands and stocksto SAP SNC). The supplier uses this data to plan, in the SMI Monitor, whichquantities he or she wants to deliver to the customer location and in which periods.The customer and supplier can see the planned receipts in the SMI Monitor, butthey cannot see them in the customer or supplier backend system. The suppliercan inform the customer about the planned receipts at the start of the outbounddelivery by using SAP SNC to send ASNs to the customer. In this case, thecustomer can only include the receipts in his or her planning at short notice. Toarrange it so that the customer finds out earlier about the planned replenishmentquantities and can therefore include them in planning, the supplier can createpurchase orders for the planned receipts in SAP SNC. The customer can transferthe replenishment orders from SAP SNC to his or her backend system. In thecustomer backend system, a purchase order is created for the replenishment order.

So that the supplier can also include the quantities to be delivered to thecustomer as firm demands in his or her backend system, SAP SNC can send thereplenishment orders to the supplier's backend system when it sends them tothe customer�s backend system. The replenishment orders are mapped to salesorders there.

Only when the supplier sends the delivery does he or she create ASNs forreplenishment orders in SAP SNC and send the ASNs to the customer.

1. The supplier creates planned receipts in the SMI Monitor.2. The supplier creates replenishment orders for the planned receipts.3. The supplier publishes the replenishment order.4. SAP SNC immediately sends the replenishment order to the customer

backend system and supplier backend system.5. When delivery processing begins, the supplier sends the customer an ASN

with reference to the replenishment order.

Inventory Alerts for Replenishment PlanningThe following options are available to generate a release alert, depending on thealert type:


� System administration executes a report regularly in the SAP SNC system.To call the report for online processing from the SAP Easy Access screen,choose Supply Network Collaboration→ Exceptions→ Alert Generation→<Report>.

� SAP SNC generates the alert during validation of the purchase order. Systemadministration can deactivate alert generation in Customizing for validation.

The following list contains the alert types for release processing in SAP SNC.



Below Min. � Projected Stock (alert ID 0011)The projected stock falls below the minimum stock level.This alert is generated by the PPF or with a report from the systemadministrator.

Above Max. � Projected Stock (alert ID 0012)The projected stock exceeds the maximum stock level.This alert is generated by the PPF or with a report from the systemadministrator.

Out of Stock � Projected Stock (alert ID 0013)The projected stock is zero or below zero.This alert is generated by the PPF or with a report from the systemadministrator.

Below Min. � Within Lead Time (alert ID 7021)The projected stock falls below the minimum stock within the lead time. *This alert is generated by the PPF or with a report from the systemadministrator.

Above Max. � Within Lead Time (alert ID 7022)The projected stock exceeds the maximum stock level within the lead time. *This alert is generated by the PPF or with a report from the systemadministrator.

Out of St. � Within Lead Time (alert ID 7023)The projected stock falls to zero or below zero within the lead time. *This alert is generated by the PPF or with a report from the systemadministrator.

Below Min. � Stock on Hand (alert ID 7041)The actual warehouse stock is below the minimum stock.This alert is generated by the PPF or with a report from the systemadministrator.

Above Max. � Stock on Hand (alert ID 7042)The actual stock on hand is above the maximum stock level.This alert is generated by the PPF or with a report from the systemadministrator.

Out of Stock � Stock on Hand (alert ID 7043)The actual warehouse stock is zero.This alert is generated by the PPF or with a report from the systemadministrator.



* If the projected stock violates the minimum or maximum stock level, or fallsto or below zero in the lead time, and you use your usual means of transport, theproduct reaches the customer after the desired delivery date.

Determining the Planning Horizon and Period DivisionTo determine the planning horizon and period division of the planning horizon fora location product in the monitor, you define a time buckets profile and assign itto the location product. You can also assign the time buckets profile to severallocation products. If you display data for multiple location products with varioustime buckets profiles, the monitor uses the most detailed time buckets profile.

Note: You can only assign a time buckets profile to products in yourlocations. The locations must, therefore, be assigned to the businesspartner to which you are assigned.

1. Call time buckets profile editing and assignment under Time BucketsProfiles. To do so, you have the following options:

� In a monitor, on the Product Data tab page of the Details screen or inthe stock information (Details-Product View)

� In the Web UI of the SMI Monitor or the SNI Monitor2. To determine the total duration of the planning horizon, choose a period type

in the Horizon field and enter the desired number of periods.3. Specify the period division of the planning horizon as follows:

� To specify the duration and period division of the short-term horizon,enter the number of weeks for which you want a schedule line in daysin the Number of Weeks field.

� To specify the duration and period division of the subsequentmedium-term horizon, enter the number of months for which youwant a schedule line in weeks in the Number of Months field . Thisschedule line is only available if you have chosen the period typemonth or year for the planning horizon.

� To specify the duration and period division of the subsequent long-termhorizon, enter the number of years for which you want a schedule linein months in the Number of Years field. This schedule line is onlyavailable if you have chosen the period type year for the planninghorizon.

4. You can specify that the planning horizon starts in the future or in the pastand not with the current period. To do so, under Offset, enter a positive ornegative number of days by which you want to shift the start of the planninghorizon.



5. Specify to which location products you want to assign the time bucketsprofile. To specify a product or location, you can use any of the fields for thesystem descriptions or the fields for your own descriptions (My�). You havethe following assignment options:

� Assign time buckets profile to a location product

Enter a location and a product.

Choose the assignment mode Save for This Location Product Only.

� Assign time buckets profile in all your locations to the product

Enter a product.

Choose the assignment mode Save for My Product in All My Locations.

� Assign time buckets profile to all products in your location

Enter a location.

Choose the assignment mode Save for All Products in My Location.

� Assign time buckets profile to all products in all your locations

Do not enter a product or a location.

Choose the assignment mode Save for All My Location Products.

6. Choose Save.



Lesson Summary

You should now be able to:� Explain the SMI process flow� Name the SMI alerts� Explain the difference between SMI and SMI with replenishment order


SNC100 Lesson: Process Demo & Exercise: SMI Process

Lesson: Process Demo & Exercise: SMI Process

Lesson OverviewThis is your chance to see what has been discussed and to view a system demo.


� Use SMI process in SAP SNC

Business Example

Figure 61: Demo





Exercise 7: SMI with SAP SNC

Exercise ObjectivesAfter completing this exercise, you will be able to:� Run a supplier-managed inventory scenario with SAP SNC

Business ExampleYour company collaborates with a number of suppliers using SAP SNC. You,as a purchaser, send information on stock levels and demand to a supplier, whothen takes on the planning of the material and delivers quantities of the materialas required. The supplier creates planned receipts on the basis of the stock anddemand information and then creates ASNs on the basis of these.

Task 1: Check stock levels in ERPCheck the current available stock for material T-B100-## in plant 1000.

Hint: This task is performed in the role of the customer using userSNC100-## in the ERP system.

1. Check stock levels in ERP for material T-B100-## in plant 1000.

ResultThe available stock is 500 PC.

Task 2: Check demand levels in ERPWhat demands exist in ERP for product T-B100-##?

1. What demands exist in ERP for product T-B100-##?

Task 3: Transfer stock levels and demand details tothe SAP SCM systemTransfer stock levels and demand details to the SAP SCM system

1. To transfer the stock and demand details to SNC, run the programRSMIPROACT with variant SNC100 SMI. In the Material field, entermaterial T-B100-##.




Task 4: Check the demands and inventory in the SMIOverview in SNCIn SAP SNC, create a new query in the SMI overview to show the SMI informationfor your product.

Hint: This task is again performed in the role of the supplier. The SMIexercise introduces a new supplier - the supplier SNC100C-## representedby the user IU-SUPC##.

1. Log on to the SNC system with the supplier user IU-SUPC## and passwordwelcome. Create a new query in the SMI overview to show the SMIinformation for your product.

ResultYou have an overview of the status of your SMI material. You can see thestock on hand of 500 pcand the SMI status (red= below minimum) for eachperiod.

Task 5: Check demand and stock information inproduct detailsCheck demand and stock information in the product details.

1. Navigate to the SMI Details screen and check that the demand and stockinformation in the ERP system corresponds to the information in SAP SNC.

2. What are the minimum and maximum stock levels?

Minimum stock level ______________________

Maximum stock level ______________________

3. What is the current stock on hand?

________________

4. What is the lead time and where does this information come from?

__________________

5. Compare the demand information in SAP SNC with the demands you notedin SAP ERP.




Task 6: Enter planned receiptsEnter planned receipts in such a way that the project stock always remains withinthe agreed range.

1. Enter planned receipts in such a way that the project stock always remainswithin the agreed range.

Task 7: Create ASNs from due listCreate ASNs from the due list

1. Navigate to the Due List for Planned Receipts and create an ASN on thebasis of the first planned receipt you created.

2. Publish the ASN.

3. Review the SMI Details screen once more. What has changed?

Task 8: Check Inbound Delivery in ERPLog on to SAP ERP as the purchaser and check the corresponding inbounddelivery for the ASN. Write down the inbound delivery number

Hint: This task is again done by the customer user SNC100-## backin the ERP system.

1. Log on to SAP ERP as the purchaser and check the corresponding inbounddelivery for the ASN.

2. Write down the inbound delivery number.

Task 9: Post goods receipt for inbound delivery in ERPNow that you have found the inbound delivery continue booking a goods receipt.





Task 10: Review SMI details in SAP SNCCheck the effect of the goods receipt posting on the SMI details in SAP SNC.

Hint: This task is again being performed by the supplier in SAP SNCusing the user IU-SUPC##.

1. What happens to the in-transit quantity?What is the stock-on-hand quantity?



Solution 7: SMI with SAP SNCTask 1: Check stock levels in ERPCheck the current available stock for material T-B100-## in plant 1000.

Hint: This task is performed in the role of the customer using userSNC100-## in the ERP system.

1. Check stock levels in ERP for material T-B100-## in plant 1000.

a) In the ERP system, in the SAP Easy Access menu, choose Logistics→Materials Management→ Inventory Management→ Environment→Stock→ Stock Overview or use transaction code MMBE.

b) Enter material T-B100-##, plant 1000, and storage location 0001and choose Execute .

ResultThe available stock is 500 PC.

Task 2: Check demand levels in ERPWhat demands exist in ERP for product T-B100-##?

1. What demands exist in ERP for product T-B100-##?

a) In the ERP system in the SAP Easy Access menu, choose Logistics→ Production→ Production Planning→ Demand Management→Environment→ Stock/Requirements List or user transaction codeMD04.

b) Enter material T-B100-## and plant 1000.

The demands are as follows:

Today + 2 working days 200Today + 4 working days 100Today + 6 working days 200Today + 8 working days 200Today + 11 working days 100




Task 3: Transfer stock levels and demand details tothe SAP SCM systemTransfer stock levels and demand details to the SAP SCM system

1. To transfer the stock and demand details to SNC, run the programRSMIPROACT with variant SNC100 SMI. In the Material field, entermaterial T-B100-##.

a) In the ERP system, go to transaction SE38.

Enter program RSMIPROACT.Choose Execute with variant.In thedialog box, select variant SNC100 SMI and chose Enter.

In the Material field, replace the ## of T-B100-## with your groupnumber (so that you only transfer the details for your own samplematerial).

Note: In a productive system, you can use the MRP type (here,ZI) to restrict the material selection.

Choose Execute .

On the subsequent screen, you can branch to the generated IDoc byclicking on the text List for IDocs. If you then click on the IDoc numberyou can see the details of the IDoc, of type PROACT.




Task 4: Check the demands and inventory in the SMIOverview in SNCIn SAP SNC, create a new query in the SMI overview to show the SMI informationfor your product.

Hint: This task is again performed in the role of the supplier. The SMIexercise introduces a new supplier - the supplier SNC100C-## representedby the user IU-SUPC##.

1. Log on to the SNC system with the supplier user IU-SUPC## and passwordwelcome. Create a new query in the SMI overview to show the SMIinformation for your product.

a) In SNC, choose Replenishment→ SMI Monitor→ SMI Overview.

b) Choose Define New Query.

In the first step, select object type SMI Monitor (Supplier).

Choose Next.

In the second step, enter your selection criteria, for example productT-B100-##.

Choose Next.

In the final step, enter a description for your query, for example, MySMI Query Group ##, and make sure the Activate Query indicatoris set.

Choose Finish.

c) On the SMI Overview screen, select your query and choose Refresh atthe bottom right of the screen, if necessary.

ResultYou have an overview of the status of your SMI material. You can seethe stock on hand of 500 pcand the SMI status (red= below minimum)for each period.




Task 5: Check demand and stock information inproduct detailsCheck demand and stock information in the product details.

1. Navigate to the SMI Details screen and check that the demand and stockinformation in the ERP system corresponds to the information in SAP SNC.

a) In SNC, branch from the SMI Overview screen to the Details screenby selecting the line and pressing Details. Or, from the menu, chooseReplenishment -> SMIMonitor→ SMI Details.

2. What are the minimum and maximum stock levels?

Minimum stock level ______________________

Maximum stock level ______________________

a) On the Product Data tab page you can see the minimum and maximumstock levels in the Min/Max Stk field.

3. What is the current stock on hand?

________________

a) You can see the current stock on hand in the SoH field.

4. What is the lead time and where does this information come from?

__________________

a) The lead time is 1 day. This information comes from the transportationduration maintained for the means of transport in the transportationlane.

Note: You can check this in the SCM system by choosingSupply Network Collaboration → Master Data →Transportation Lane→ Transportation Lane or by usingtransaction /SAPAPO/SCC_TL1.

5. Compare the demand information in SAP SNC with the demands you notedin SAP ERP.

a) In the SMI Overview grid arrangement, you can see the demands in theDemand line.




Task 6: Enter planned receiptsEnter planned receipts in such a way that the project stock always remains withinthe agreed range.

1. Enter planned receipts in such a way that the project stock always remainswithin the agreed range.

a) Switch to the SMI No Ship-From Location grid arrangement. In thePlanned Receipts line, enter the planned receipt quantities.

Choose Enter simulate the projected stock.

b) Alternately, you can have the system propose the planned receiptsrequired to keep the projected stock between the minimum andmaximum levels.ChoosePropose Planned Receipts.You can see theproposals in the Planned Receipts line. When you are happy withthe situation, choose Save.

Task 7: Create ASNs from due listCreate ASNs from the due list

1. Navigate to the Due List for Planned Receipts and create an ASN on thebasis of the first planned receipt you created.

a) In SAP SNC, navigate from the SMI Details screen by choosing DueList, or choose Delivery→ Receipts and Requirements→ Due List forPlanned Receipts.

b) Choose Go. You can now see the planned receipts you created in theprevious step.

Select the first entry and choose Create ASN.

c) You branch to the ASN Maintenance - Create ASN screen. Enter anASN number, for example SMI##_01.

2. Publish the ASN.

a) Choose Check to validate that the ASN is correct. If there are noerrors, publish the ASN.

3. Review the SMI Details screen once more. What has changed?

a) Navigate to the SMI Details screen (choose Replenishment→ SMIMonitor→ SMI Details - Product view) and call up the details foryour product, T-B100-##.

Choose Go.

You can now see the quantity of the ASN in the In Transit row.




Task 8: Check Inbound Delivery in ERPLog on to SAP ERP as the purchaser and check the corresponding inbounddelivery for the ASN. Write down the inbound delivery number

Hint: This task is again done by the customer user SNC100-## backin the ERP system.

1. Log on to SAP ERP as the purchaser and check the corresponding inbounddelivery for the ASN.

a) From the SAP Easy Access menu, choose Logistics→ LogisticsExecution→ Inbound Process→ Inbound Delivery→ Change→Single Document or use transaction transaction VL32N.

b) Search for the inbound delivery using the input help (F4) and searchby the External Delivery ID (the ASN number you entered in SNC,for example, SMI#_01).

2. Write down the inbound delivery number.

a) ___________________

Task 9: Post goods receipt for inbound delivery in ERPNow that you have found the inbound delivery continue booking a goods receipt.


a) On the Shipping Notification 18XXXXXXX Change: Overview screen,you can see that the delivery is relevant for putaway as the warehouseis subject to lean warehouse management.

From the menu, choose Subsequent Functions→ Create TransferOrder. Confirm the dialog box. On the Create Transfer Order forDelivery Note: Initial screen, select the processing option Backgroundand choose Enter. The system issues a message: Transfer orderXXXXXXXX created.

b) Return to the Change Inbound Delivery screen by choosing Back .You can see that the putaway status is now Completely put away.

c) Choose Post Goods Receipt. The system issues a message: Shippingnotification 18XXXXXXX has been saved.

d) If you now display the delivery (VL33N) and choose Extras→Delivery Output, you can see that a message of the type OPOD (VendorProof of Delivery) was issued when the goods receipt was posted.




Task 10: Review SMI details in SAP SNCCheck the effect of the goods receipt posting on the SMI details in SAP SNC.

Hint: This task is again being performed by the supplier in SAP SNCusing the user IU-SUPC##.

1. What happens to the in-transit quantity?

What is the stock-on-hand quantity?

Answer: Navigate to the SMI Details screen.You will see that the in-transitquantity has disappeared.On the Product Data tab page, the stockon hand has increased by the goodsreceipt quantity.



Lesson Summary

You should now be able to:� Use SMI process in SAP SNC


SNC100 Lesson: Relevant System Settings and Customizing for SMI in SAP SNC

Lesson: Relevant System Settings and Customizing forSMI in SAP SNC

Lesson OverviewThis lesson will introduce you to the necessary system settings to run asupplier-managed inventory (SMI) scenario in SAP SNC. We sill also discussthe concept of the data matrix.


� Make the necessary system settings to run an SMI scenario� Explain Customizing for the data matrix

Business Example

Transfer of Demands and Stocks to SAP SNCIn the SMI business scenarios and processes, you transfer your demand andstock data to SAP SNC so that a supplier can see it and plan deliveries to youaccordingly. You can specify whether the report should be used to create demandand stock data, stock data only, demand data only, or goods receipt references only.

There are two versions of the report available:

� Rreport RSMIPROACT uses IDocs. The report creates PROACT01 orDELVRY03 IDocs (type DELVRY03 is for goods receipt references only).

� As of SAP ERP 6.0, enhancement package 02, you can also use theRSMIRPOACT02 report. With this report, you can create PROACT01or DELVRY03 IDocs, and you can also create XML messages of typeProductActivityNotification.



PrerequisitesThe source list contains a valid entry for each selected SMI material.

1. On the SAP Easy Access screen, choose System→ Services→ Reporting.2. Enter RSMIPROACT or RSMIPROACT2 in the Program field and choose

Execute .3. Choose SMI (Single Sourcing).4. To switch off goods receipt references, choose No Goods Receipt References.

Hint: The text displayed on the button represents the actualselection. If the button text displays No Goods Receipt References,the report does not transfer goods receipt information.

5. Enter the required selection criteria.6. In the Send Parameters for IDoc screen area, enter the following data:

Field MeaningTarget System Enter the name of the logical system to which the

generated IDocs are transferred. This is frequentlythe logical name of the EDI subsystem. The partnerprofiles refer to this logical system (see partner typeLS in the partner profile, transaction WE20).

Demand If you set this indicator, the system transfers thedemand information to the IDoc or XML message.

Stock If you set this indicator, the system transfers the stockinformation to the IDoc or XML message.

Choose Execution and then choose Update run. Finally, execute the report.

Zero QuantitiesThink about following demand situation in your back-end system. You set upRSMIPROACT to run on a daily basis and transmit the demand situation for theactual period and the next five periods.

Demand situation at day tDay t t+1 t+2 t+3 t+4 t+5 t+6 t+7 t+8Demand 10 0 15 20 8 3 5 10 7

The data will be extracted by report RSMIPROACT and will be sent to SAPSNC and stored there as time series data.



Result in SNCDay t t+1 t+2 t+3 t+4 t+5 t+6 t+7 t+8Demand 10 0 15 20 8 3 0 0 0

Note: t+6, t+,7 and t+8 are empty because you only selected to transmitdemand for the actual and the next five periods.

One day later, the demand situation looks like this.

Demand situation as of day t+1Day t t+1 t+2 t+3 t+4 t+5 t+6 t+7 t+8Demand 0 0 15 20 8 3 5 10 7

Nothing has changed except that the demand in day t (which is now in the past)has disappeared.

Caution: If you next want to transfer the demand for the actual periodand the next 5 periods, based on the actual date, you will transfer data forthe period t+1 to t+6. Thus the XML message sent to SAP SNC would notcontain any information about periods t, t+7 and t+8. As SAP SNC wouldnot get a update on period t, the result would be this:


Obviously the result is wrong.

In the next situation, the demand in period t+3 will disappear.

Demand situation as of day t+2Day t t+1 t+2 t+3 t+4 t+5 t+6 t+7 t+8Demand 0 0 15 0 8 3 5 10 7

Report RSMIPROACT will only send data were there is a demand. This is tokeep the message traffic low. Imagine a situation were you transmit the demanddata for the next three years and only a few periods show a demand.

Caution: As SAP SNC does not receive any data for period t+3, thedata remains unchanged.




There are two ways to avoid the above situation. You can either use the TransferZero quantities flag in the Execution Parameters section of the report, ormake a Customizing setting in SAP SNC to reset the time series for incomingProductActivityNotification messages.

In the first case there is the risk of getting very large IDocs / XML messages.

To perform the Customizing for the second option, choose Supply NetworkCollaboration→ Basic Settings→ Processing Inbound and Outbound Messages→ Reset Time Series for incoming ProductActivityNotifications in the SAP SNCIMG.

Default Process TypesWithin SAP SNC customer collaboration, supplier collaboration usesProductActivityNotification XML messages. The XML message has differentcontent depending on the scenario. Thus SAP SNC need to know how to processthe incoming message. In SAP SNC Customizing you define the process typeto be used for the incoming message. In the SAP SNC IMG, you maintain theseprocess types by choosing Supply Network Collaboration→ Basic Settings→Processing Inbound and Outbound Messages→ Process Types for InboundMessages→ Assign Inbound XML Messages to Default Process Type. In thestandard delivery the process type for the ProductActivityNotifictation - Inboundmessage is set to VMI Responsive Replenishment. For the SMI process, you needto set this to ICH Supplier Collaboration.

Hint: If you are using customer collaboration and supplier collaboration,you can make a setting based on the sending system in Customizing bychoosing Supply Network Collaboration→ Basic Settings→ ProcessingInbound and Outbound Messages→ Process Types for Inbound Messages→ Assign Sender- and Recipient-Dependent Process Types (Inbound).

MRP Type for SMI MaterialsAs the supplier is responsible for the replenishment of a SMI part, it is no longerrequired that you are plan the replenishment for this part. Thus you can exclude itfrom the MRP planning. Therefore, assign a non-MRP-relevant MRP type to thematerial. For better separation from the other non-MRP-relevant parts, the SMIparts normally get their own MRP type (for example a copy of ND).



Message Determination for the SMI ProcessYou have learned that the IDocs in the SMI Process are generated by theRSMIPROACT report. Therefore, message determination is not required for thisprocess, but you still require a partner profile.

Maintain partner profiles in transaction WE20: Tools → ALE → ALEAdministration→ Runtime Settings→ Partner Profiles.

You require an entry for sidCLNTxxx and message type PROACT. The partnerrole remains empty.

Message Determination for the SMI Process withReplenishment OrderIn contrast to the standard SMI process, the supplier creates an additionaldocument in the SMI process with replenishment order: the replenishment order(RO). This document is sent to the customer's ERP system and will create apurchase order there. For the creation of the purchase order in the customers backend, no settings are required for message determination except a partner profileand some additional customizing.

Partner profileFor the SMI with RO process, you require an inbound partner profile.

Partner Role Message Type Message Variant<EMPTY> ORDRSP SMI

The process code is ORDS.

Order entry by vendorBefore creating the purchase order, the SAP back-end system checks if thevendor is allowed to create an order in the customer's back-end system. Thisinformation is stored in the vendor master. In the Purchasing data, Servicedata section, set the Order Entry by Vendor indicator.



Assignment of PO data to vendorThe SAP SNC replenishment order does not contain all the relevantinformation for creating the purchase order in the SAP back-end system.During the inbound processing, the system needs to assign these values.Maintain these values in transaction Assignment of PO Data to vendorwhich can be found in the SAP Easy Access menu by choosing Logistics→Materials Management→Purchasing→ Environment→ Order Entry byVendor→ Organizational Assignment. Here you define which PurchasingOrganization, Purchasing Group, Plant, and Purchasing Document Type willbe used for order creation.

Hint: The Purchasing document type that you assign here must beset up for external number assignment.

Data MatrixThe data matrix contains the key figures of an application, as well as the variousaggregation levels on which these key figures exist. The data matrix views controlhow the screen looks in the replenishment monitors. In Customizing, you can addnew key figures to the different views or remove existing key figures. ChooseSupply Network Collaboration→ Basic settings→ Data Matrix→ ConfigureData Matrix views.



Lesson Summary

You should now be able to:� Make the necessary system settings to run an SMI scenario� Explain Customizing for the data matrix


Unit Summary SNC100

Unit SummaryYou should now be able to:� Explain the SMI process flow� Name the SMI alerts� Explain the difference between SMI and SMI with replenishment order� Use SMI process in SAP SNC� Make the necessary system settings to run an SMI scenario� Explain Customizing for the data matrix


Unit 8Further Processes in SAP SNC

Unit OverviewIn this unit, you will gain an overview on further processes within SAP SNC.


� Explain the capabilities of SAP SNC dynamic replenishment� Explain the DCM process flow in SAP SNC� Name the DCM alerts in SAP SNC� Explain the Kanban process flow in SAP SNC� Name the Kanban Aalerts in SAP SNC� Explain work order process flow in SAP SNC� Name the work order alerts in SAP SNC� Describe the SNI and subcontracting PO process flow in SAP SNC� Name the alerts for SNI and subcontracting POs in SAP SNC

Unit ContentsLesson: Dynamic Replenishment... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276Lesson: Delivery Control Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283Lesson: Kanban Process with SAP SNC... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289Lesson: Work Order Collaboration with SAP SNC ... . . . . . . . . . . . . . . . . . . . . . .300Lesson: SNI and Subcontracting PO.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327


Unit 8: Further Processes in SAP SNC SNC100

Lesson: Dynamic Replenishment

Lesson OverviewThis lesson will introduce you to the capabilities of SAP SNC dynamicreplenishment.


� Explain the capabilities of SAP SNC dynamic replenishment

Business Example

BackgroundThe purpose of dynamic replenishment is to exchange planning data between thesupplier and the customer. Both the customer and the supplier have the same viewof the planning situation and gain a quick overview of critical situations. This isthe basis for a possible planning adjustment to match supplier capacity as partof a dynamic replenishment scenario.

The main screen for this scenario is the Demand Monitor.

The Demand Monitor displays and compares the customer�s firm or plannednet demands and the supplier�s firm or planned receipts. The Demand Monitorcalculates the absolute and the percentage deviations between customer andsupplier data and, depending on the deviations, highlights periods in color.

The customer uses electronic messages to transfer his or her data from theback-end system to SAP SNC The supplier can also transfer data electronicallyfrom his or her back-end system to SAP SNC. Alternately, the supplier canmanually create planned receipts in the Demand Monitor.


SNC100 Lesson: Dynamic Replenishment

Figure 62: Dynamic Replenishment

Key FiguresThe Demand Monitor differentiates between planned data and firm data. Planneddata is data that could still change, that is, data that is still provisional. Thisincludes, for example, the customer�s forecast demands or the supplier�s plannedreceipts. Firm data includes the customer�s purchase orders or the purchase orderschedule lines that the supplier has confirmed.

The following sections contain information about the relevant key figures andhow to transfer the data for the key figures as standard from the customer�s andsupplier�s back-end systems.



Customer planned demandsThis key figure can contain the following demands:

� Customer�s net demands, for example, from the customer�s net demandplanning

� Dependent demands from the customer's orders that are still at theplanning stage, for example, planned orders, purchase requisitions,and scheduling agreement release schedule lines in the secondfirm/trade-off zone

The customer transfers the data from his or her back-end system to SAP SNC.Depending on the back-end system, the customer has the following options.Time series datamanagement in SAP SNCmaps theOrderForecastTimeSeriesfrom the ProductActivityNotification to the SAP SNC time seriesNETDEMAND (time series data type SMI02).

� If the customer�s back-end system is an SAP system as of SAPR/3 4.6C, the customer can use report RSMIPROACT. Thecustomer uses this report to generate the IDoc PROACT.PROACT01for net demands and demands from purchase requisitions andunfirmed scheduling agreement release schedule lines. The IDocfirst goes to SAP NetWeaver usage type Process Integration. SAPNetWeaver maps the IDoc automatically to an XML message of typeProductActivityNotification. The OrderForecastTimeSeries of theProductActivityNotification contains the sum of the demands (netdemands, demands of the purchase requisitions, and the unfirmedscheduling agreement release schedule lines).

� If the back-end system is not an SAP system, the customer sends datain a ProductForecastNotification to SAP SNC The customer usesthe OrderForecastTimeSeries of the ProductForecastNotification forthe data. No mapping is required in SAP NetWeaver. Time seriesdata management in SAP SNC maps the OrderForecastTimeSeriesfrom the ProductForecastNotification to the SAP SNC time seriesNETDEMAND (time series data type SMI02).



Customer firm demandsThis key figure contains, as standard, open demands from orders in thecustomer system that the customer regards as firm. These include schedulingagreement release schedule lines in the first firm/trade-off zone and purchaseorders.The customer transfers the data from his or her back-end system to SAP SNC.Depending on the back-end system, the customer has the following options:

� If the customer�s back-end system is an SAP system as of releaseSAP R/3 4.6C, the customer can use report RSMIPROACT, asfor the key figure Customer Planned Demands. With this report,the customer can transfer demands of purchase orders and firmscheduling agreement release schedule lines. When mapping theIDoc PROACT.PROACT01 to the ProductActivityNotification, SAPNetWeaver maps the demands of the purchase orders and the firmscheduling agreement release schedule lines to the OnOrderTimeSeriesof the ProductActivityNotification. Time series data management inSAP ICHSNC maps the OnOrderTimeSeries to the SAP SNC timeseries CORDERTS (time series data type SMI02).

� If the customer�s back-end system is not an SAP system, the customercan also transfer purchase orders and scheduling agreement releases asReplenishmentOrderNotifications or as DeliveryScheduleNotificationsto SAP SNC. No mapping is required in SAP NetWeaver.

Supplier planned receiptsThis key figure contains receipts that the supplier has forecast in his or herback-end system for the customer and transferred to SAP SNC.Alternately, the supplier can manually enter planned receipts in the DemandMonitor or in the SAP SNC SMI Monitor.The supplier transfers the data in a ProductForecastRevisionNotificationfrom his or her back-end system to SAP SNC. To do so, he or she uses theOrderForecastTimeSeries of the ProductForecastRevisionNotification.No mapping is required in SAP NetWeaver. Time series datamanagement in SAP SNC maps the OrderForecastTimeSeries fromthe ProductForecastRevisionNotification to the SAP SNC time seriesPLANSHIP (time series data type SMI02).



Supplier firm receiptsAs standard, this key figure contains confirmation schedule lines that thesupplier has created manually in SAP ICH or sent from his or her back-endsystem to SAP SNC.The supplier sends confirmation schedule lines to SAP SNC in aReplenishmentOrderConfirmation. No mapping is required in SAPNetWeaver.To transfer receipts to SAP SNC that the supplier has planned inhis or her back-end system for the customer, the supplier can use aProductForecastNotification. No mapping is required in SAP NetWeaver.In this case, the customer must set in time series data management in SAPSNC such that SAP SNC maps the data to the time series SORDERTS (timeseries data type SMI02).

Key figures for deviationsThe following table contains the key figures for deviations between customerand supplier data. SAP SNC calculates the key figures automatically.

Key figure CalculationPercentage plan deviation 100*(supplier planned receipts - customer planned

demands)/customer planned demands *Absolute plan deviation supplier planned receipts � customer planned

demandsPercentage order deviation 100*(supplier firm receipts � customer firm

demands)/customer firm demandsAbsolute order deviation supplier firm receipts � customer firm demands

* Depending on the percentage variance between the planned supplier receiptsand the planned customer demands, SAP SNC highlights the periods on theoverview and detailed screens of the Demand Monitor in color. The followingtable explains the meaning of the colors:

Deviation Status Percentage Deviation in PercentBelow tolerance < - 2Within tolerance >= -2 and < 0Under threshold value >= 0 and <= 5Over threshold value > 5

Integration with Purchase Order collaborationBesides the intended use for exchanging plan data the Demand Monitor is oftenused as extension of the purchase order collaboration scenario.



In purchase order collaboration, only the purchase orders are shown to thesupplier, not the purchase requisition.

The Demand Monitor, on the other hand, is able to store and show the customer'spurchase requisition as times series data. Thus the Demand monitor is often usedto give the supplier a forecast in the PO process when no dynamic replenishmentscenario is implemented.



Lesson Summary

You should now be able to:� Explain the capabilities of SAP SNC dynamic replenishment


SNC100 Lesson: Delivery Control Monitor

Lesson: Delivery Control Monitor

Lesson OverviewThis lesson will introduce you to the capabilities of the Delivery Control Monitorin SAP SNC.


� Explain the DCM process flow in SAP SNC� Name the DCM alerts in SAP SNC

Business Example

BackgroundThe Delivery Control Monitor (DCM) is a function of supplier cooperation andis available on the SAP SNC Web UI.

Figure 63: DCM Process Overview

In supplier collaboration, a supplier can use the DCM to monitor the customer'scurrent stock on hand on a daily basis, and immediately initiate deliveries, ifrequired. The DCM displays how high the customer's current stock on hand is,and the quantity that is already in transit from the supplier to the customer.



The DCM generates alerts for critical stock situations, including alerts for fallingbelow the minimum stock level or for exceeding the maximum stock level. As inthe SMI scenario, the supplier must adhere to these stock limits. A special alertis generated if the stock falls to or below the signal stock level that lies betweenthe minimum and the maximum stock levels. If this occurs, the supplier shouldimmediately initiate a delivery to refill the stock.

In the DCM, the supplier can call ASN processing and create ASNs to informthe customer of the pending deliveries.

The customer can use the DCM to see, for example, information about thedelivery quantities that will arrive from the supplier on the current day or thosethat will be late.

DCM is intended to be used in the following scenario:

� For a product that the supplier delivers several times a day, the customerwants to keep an amount stock on hand that lies between the minimumand the maximum stock levels agreed on with the supplier. The supplieris responsible for ensuring that the stock on hand does not fall below theminimum stock level nor exceed the maximum stock level.

� The supplier must react to the current status of the customer stock on handat very short notice. The supplier should initiate deliveries as soon as thestock has fallen to or below the signal stock level at the very latest (severaltimes a day if required) so as to refill the stock and to prevent the stock levelfrom falling below the minimum.

Hint: When to Use the SMI Monitor and When to Use the DCM

The DCM enables deliveries to be triggered at short notice for acutedemand, in other words, when the stock on hand sinks to or below thesignal stock level. The important control parameter is the stock on hand,which must not fall below the minimum stock level nor rise above themaximum stock level. The supplier does not use the DCM for planningpurposes. The supplier uses the SMI Monitor to plan in an SMI scenario.The SMI Monitor provides an overview of how the stock situation at thecustomer will develop in the future. The controlling key figure here isthe projected stock. The supplier can use the SMI Monitor to plan whichdeliveries are necessary in the future so that the remaining stock remainsbetween the minimum stock level and the maximum stock level. TheSMI Monitor also frees the customer from planning responsibilities andoptimizes production and transportation on the supplier side.

You can use both monitors at the same time in an SMI scenario. Use theSMI Monitor for the planning side and the DCM for the daily monitoringof the stock on hand and to initiate deliveries at short notice.



The customer uses the XML message of type ProductActivityNotificationtotransfer demand and stock data for the DCM to SAP SNC. If the customer usesan SAP back-end system, he or she can use report RSMIPROACT to transferthe data.

Master Data for the Delivery Control MonitorThe DCM scenario uses the same master data as the SMI process, plus anadditional value: the signal stock.

Master data

� Business partners� Location� Product� Transportation lane� Minimum stock level (from the Safety Stock field in the ERP material master)� Maximum stock level (from the Maximum Stock field in the ERP material

master)� Signal stock level (from the Reorder Point field in the ERP material master)� Rounding value (from the Rounding Value field in the ERP material master)

Calculating Stock on HandIn the standard configuration, the system calculates the stock on hand as the sumtotal of the following types of stock:

� Unrestricted-use stock� Blocked stock� Stock in quality inspection� Unrestricted-use consignment stock� Blocked consignment stock� Consignment stock in quality inspection

If you want to use other formulas to calculate the stock (for example, with otherstock types and based on the characteristics customer, customer location, andproduct), you must define a profile for calculating the projected stock that takesaccount of other stock types in Supply Network Collaboration Customizing.The standard system uses a formula that corresponds to the settings in the ASNstandard profile.

The calculation of the stock on hand is performed by the default implementationof the /SCA/ICH_STOCKONHAND BAdI (CALCULATE_STOCKONHANDmethod). If required, you can use the BAdI to implement your own calculationmethod.



Stock-on-Hand StatusTo calculate the status of the stock on hand, the system compares the stock onhand with the minimum stock level, the maximum stock level, and the signal stocklevel from the location product master. The stock-on-hand status is representedin the DCM by color.

Stock-on-Hand Status ColorStock on hand exceeds the maximum stock level BlueStock on hand lies between the signal stock level and themaximum stock level

Green

Stock on hand lies between the minimum stock level and thesignal stock level

Yellow

Stock on hand lies below the minimum stock level but is notzero

Orange

Stock on hand is zero Red

Calculating Gross and Net Delivery QuantitiesIn the standard system, the system calculates the net delivery quantity and thegross delivery quantity as follows:

Net delivery quantity = maximum stock level - stock in transit - stock on hand

Gross delivery quantity = maximum stock level - stock on hand

If necessary, you can implement your own calculation methods in the/SCF/ICH_DCM_VALUES BAdI. You can use this BAdI to modifyDCM-relevant values, for example, the values that the DCM displays or the valuesthat the DCM uses as the basis for calculating alerts.

Creating ASNs in the DCMYou, as supplier, can directly call ASN processing and create an ASN for a selectedproduct in the Delivery Control Monitor. The system automatically suggests thedelivery quantity that is necessary to refill the stock on hand to the maximum stocklevel, and (if necessary) automatically carries out rounding to adjust the deliveryquantity, for example, to the production, packaging, or transportation conditions.

If you want to create an ASN for the gross delivery quantity, choose CreateASN (Gross). If you want to create an ASN for the net delivery quantity, chooseCreate ASN (Net).



Inventory Alert for the DCMDCM alerts are generated by one of the following methods:

� The Post Processing Framework (PPF) generates an alert when aProductActivityNotification is received. By default, alert generation is notactive. The system administrator must activate alert generation in the PPF(application /SCA/ICH, action profile /SCA/BOL_INVENTORY, action/SCA/BOL_INV_DCM_STOCK_CHECK).

� The system administrator regularly runs report /SCA/DCMALERTSWRITEin the SAP SNC system. To call the report for online processing, chooseSupply Network Collaboration→ Exceptions→ Alert Generation→Generate Inventory Alerts for Delivery Control Monitor on the SAP EasyAccess screen.

Stock Below Minimum (DCM) (alert ID 7081)The stock on hand is less than the minimum stock level.

Stock Above Maximum (DCM) (alert ID 7082)The stock on hand is greater than the maximum stock level.

Stockout (DCM) (alert ID 7083)The stock on hand is zero.

Signal Level Reached (DCM) (alert ID 7084)The stock on hand is less than or equal to the signal stock level.



Lesson Summary

You should now be able to:� Explain the DCM process flow in SAP SNC� Name the DCM alerts in SAP SNC


SNC100 Lesson: Kanban Process with SAP SNC

Lesson: Kanban Process with SAP SNC

Lesson OverviewThis lesson will introduce you to the Kanban process in SAP SNC.


� Explain the Kanban process flow in SAP SNC� Name the Kanban Aalerts in SAP SNC

Business Example

BackgroundAs a customer, you can use SAP Supply Network Collaboration (SAP SNC)for Kanban-driven external procurement. If you want to procure a specificquantity of a product from your supplier with whom you have arranged Kanbanprocessing, send a Kanban request from your back-end system to SAP SNC byXML message. This Kanban request corresponds to the Kanban card of an emptyKanban container.

Figure 64: Generic Kanban Process



Figure 65: Web-Based Kanban with SAP SNC

Figure 66: Kanban Process Overview

On the SAP SNC Web UI, you and your supplier can monitor the Kanbans. TheKanban Web UI provides an overview of all Kanbans of a Kanban control cycleand provides information about the Kanban status and quantities. In particular, thesupplier sees the empty Kanbans and can deliver accordingly.



If the supplier wants to inform you that he or she has sent you the requestedKanban quantity, he or she creates an ASN for the empty Kanban in SAP SNC,publishes it, and sends it to your back-end system. SAP SNC automaticallyupdates the Kanban status based on the ASN. If you have received the goods, yousend the goods receipt information to SAP SNC by XML message. Based on thisgoods receipt information, SAP SNC sets the Kanban status to Full.

If you, the customer, want to inform a supplier of required quantities in advance,you can send a Kanban forecast delivery schedule to SAP SNC from yourback-end system. For suppliers, Kanban forecast delivery schedules are purelyinformative. (The supplier, however, is committed to delivering these quantitiesif you order these quantities with Kanban requests.) In the standard system, thesupplier cannot create ASNs for a Kanban forecast delivery schedule.

There are special Kanban alerts in SAP SNC for Kanban processing. By usingalert notifications, SAP SNC can inform a supplier automatically if a new Kanbanrequest has arrived or if the supplier has not responded to an empty Kanbanwith an ASN within a specific response time. SAP SNC can inform the supplierby e-mail or fax, for example. Therefore, the supplier only has to call Kanbanprocessing if his or her intervention is required.

XML Messages in Kanban ProcessingKanban processing in SAP SNC uses various XML messages to receive Kanbanrequests from the customer back-end system and for delivery processing with thecustomer back-end system. SAP NetWeaver (as of 2004s usage type ProcessIntegration) maps the messages from the customer back-end system to thecorresponding XML messages, and vice versa.

An SAP customer back-end system sends and receives messages in IDoc format.In particular, the customer can use the Kanban functions of the SAP back-endsystem to generate forecast delivery schedules or Kanban requests, and send theseas IDocs. SAP delivers standard XSLT mappings for message integration betweenSAP SNC and an SAP back-end system (SAP ECC 6.0 with industry extensionDIMP or SAP R/3 4.6C without DIMP).

Kanban processing with SAP uses the following XML messages:

DeliveryScheduleNotificationThe customer creates a message for a Kanban forecast delivery schedule inhis or her back-end system. He or she sends this message to SAP NetWeaver(usage type Process Integration). SAP NetWeaver maps the message to aDeliveryScheduleNotification XML message, in which the Kanban indicatoris set at header level, and sends the DeliveryScheduleNotification to SAPSNC.



ReplenishmentOrderNotificationThe customer creates a message for the Kanban request in hisor her back-end system. He or she sends this message to SAPNetWeaver. SAP NetWeaver maps the message to an XMLmessage of type ReplenishmentOrderNotification and sends theReplenishmentOrderNotification to SAP SNC.

DespatchedDeliveryInformationSAP SNC sends an ASN, which the supplier publishes in SAP SNC for aKanban, to the customer back-end system via SAP NetWeaver with an XMLmessage DespatchedDeliveryInformation.

ReceivedDeliveryInformationWhen the customer receives a full Kanban, he or she sends thegoods receipt information with a message from his or her back-endsystem to SAP NetWeaver. SAP NetWeaver maps the message to aReceivedDeliveryInformation that it sends to SAP SNC.

Hint: For more information, see ASN processing.

DeliveryScheduleNotificationThe customer can create a forecast delivery schedule in the customerback-end system and send this to SAP NetWeaver to inform the supplier ofrequired quantities in advance. SAP NetWeaver maps the forecast deliveryschedule to a ReceivedDeliveryInformation that it sends to SAP SNC. ADeliveryScheduleNotification is indicated in the header data as a previewrelease for Kanban processing.

As Kanban-specific information, the XML messages contain the Kanban ID and,depending on the document, the required, delivered, or received Kanban quantity.In addition, the XML messages contain information about the procurementdocument in the customer back-end system to which the Kanban request refers(such as purchase order number, contract, or scheduling agreement).

ASN ProcessingFor an empty Kanban, the supplier can manually create an ASN in SAP SNCor send it from his or her back-end system to SAP SNC. The ASN refers to theKanban request. Based on the ASN, SAP SNC automatically updates the Kanbanstatus. A Kanban acquires the In Work status in SAP SNC if the supplier saves theASN as a draft. It acquires the In Transit status if the supplier publishes the ASNand sends it to the customer.



To set a Kanban to In Transit, the supplier must publish exactly one ASN in therequired quantity for the Kanban. The following are not possible:

� Partial deliveries, that is, delivery in several partial quantities and withseveral ASNs

� Underdelivery, that is, delivery of a quantity that is smaller than the requestedKanban quantity

� Overdelivery, that is, delivery of a quantity that is larger than the requestedKanban quantity

If the customer sends a goods issue message to SAP SNC from his or her back-endsystem, SAP SNC updates the status of the Kanban and the ASN.

Simplified ASN maintenance is available in SAP SNC Kanban processing.However, the supplier can also use the Web UIs for standard ASN processing.This can include, for example, analyzing problems that occurred when creatingthe ASN, or manually or automatically packing ASN items of a draft ASN usingthe standard packing functions.

You can use the /SCA/KANBAN BAdI to modify Kanban data or Kanbanprocessing in SAP SNC specifically to the customer, if required.

Master DataIf you, as customer, want to implement Kanban processing in SAP SNC, you mustset up the required master data in SAP SNC. In addition to the general master datafor supplier collaboration in SAP SNC, Kanban-specific master data (Kanbancontrol cycles and supply areas) is necessary for Kanban processing. You cancreate this master data manually in the SAP SNC system. If you use an SAPsystem as your back-end system (as of SAP R/3 4.6C or as of SAP DI 4.6C2 for anautomotive system) and have already set up control cycles and supply areas , youcan transfer this data to SAP SNC using report KANBAN_MD_TRANSMIT.With regard to this master data, the back-end system is the leading system.If Kanban master data changes in the back-end system, you must update themaster data in SAP SNC using the report. You must either transfer the followingKanban-specific master data from an SAP back-end system to SAP SNC or createit manually in SAP SNC:

Control cycleIf you want to procure a product from a supplier for a specific supply area inthe customer location with Kanban, a control cycle must be available in SAPSNC for this combination of customer, supplier, customer location, supplierlocation, product, and supply area. You can manually create control cycles inSAP SNC under Inventory Collaboration Hub→ Supplier Collaboration→Kanban→ Kanban Master Data→ Maintain Kanban Control Cycles. TheKanban control cycle contains the following data:

� Control cycle category



The following control cycle categories are available:

- Classic Kanban

- Event-driven Kanban

The control cycle category is displayed in the Kanban overview. Thecontrol cycle category does not have a control function in SAP SNC.

� Container quantity

This is the quantity that each container of a Kanban control cycle cancontain.

� Reference document

For a control cycle, you must specify the number of the schedulingagreement or the contract in the back-end system to which theKanban requests for the control cycle refer. SAP SNC can use thereference document to determine the control cycle ID for a Kanbanrequest (ReplenishmentOrderNotification) at receipt. Alternately, theReplenishmentOrderNotification can contain a control cycle ID directly.

� Supply area

You must enter a name in the control cycle for the supply area.

� Response time

The response time is an SAP-SNC-specific parameter that you usein SAP SNC to generate alerts for late supplier responses to emptyKanbans. You cannot transfer this parameter from the SAP back-endsystem. Rather, you must enter the parameter in SAP SNC in the controlcycle. In SAP SNC, the /SCA/DM_KNBN_SETDEF_RESTIMEreport allows you to define a control-cycle-independent defaultresponse time for all control cycles of a customer. For onlineprocessing, call the report by choosing Inventory Collaboration Hub→Supplier Collaboration→ Kanban→ Set Default Response Time.

� Packaging material

Here you specify the product number of the Kanban container material(you must have created a location product master for the packagingmaterial). The product number of the packaging material is displayedin the Kanban processing Web UI. In the packaging function of ASNprocessing, there is no validation check which forces the supplier to usethis packaging material for packing.

� Total number of Kanbans in a Kanban control cycle� Number of active Kanbans



Supply area descriptionsYou can also transfer supply area descriptions from the SAP back-endsystem. If there are no descriptions in the SAP back-end system, you cancreate the descriptions in the SAP SNC system. To do so, on the SAPEasy Access mySAP Supply Chain Management screen, choose InventoryCollaboration Hub→ Supplier Collaboration→ Kanban→ Kanban MasterData→ Maintain Kanban Control Cycles.

Kanban StatusSAP SNC sets the status of a Kanban automatically, depending on the functionthat the supplier or customer performed beforehand on the Kanban.

Status DescriptionEmpty A Kanban can acquire this status as follows:

� The customer has sent a Kanban request to SAPSNC from his or her back-end system.

� A Kanban that has the status In Work or InTransit can obtain the status Empty again if thesupplier manually cancels the related ASN withthe status Draft or Published.

In Work The supplier has created a draft ASN in Kanbanprocessing in SAP SNC for a Kanban with the Emptystatus.



In Transit A Kanban can acquire this status as follows:

� In SAP SNC, the supplier has manually createdand published (that is, sent to the customer) anASN for an empty Kanban.

� The supplier has sent an ASN with Empty statusto SAP SNC from his or her back-end system.

Full A Kanban with the In Transit status can acquire thisstatus as follows:

� The customer has received the requested Kanbanquantity and sent a goods receipt message,which refers to the Kanban, from his or herback-end system to SAP SNC.

� The customer has set the Kanban statusmanually to Full in Kanban processing in SAPSNC.

Closed The customer has set the Kanban sta-tus of a Kanban from Full to Closedin Kanban processing of SAP SNC.The customer can delete closed Kan-bans in the SAP SNC system using report/SCA/DM_KNBN_DEL_CLOSED.

ProcessThe process runs as follows:

1. Create Kanban request.

The customer creates a Kanban request in the ERP system. The ERPsystem transfers the ORDERS.ORDERS03 IDoc to the customer�s SAPNetWeaver System, which converts the IDoc into an XML message of typeReplenishmentOrderNotification and transfers it to SAP SNC.

Hint: You have implemented SAP Note 844679 for this purpose.

2. Display Kanban call (SAP SNC).3. Publish advanced shipping notification (supplier�s ERP system).




Caution: Note that the IDocs, XML messages, and mappingsdepend on which ERP system and releases are being used. Mappingsare sometimes required for the message flow between the supplier�ssystem and SAP SNC, depending on the supplier�s system. Sincethe mappings are dependent on the supplier�s system, they cannotbe predefined in the SAP SNC standard delivery. You must createthe mappings as part of a project solution.

4. Receive advanced shipping notification, or create shipping notification in theWeb UI (SAP SNC).

If suppliers do not use an ERP system to send advanced shippingnotifications, they can create them in the Web UI. The SAP SNC systemtransfers an XML message of type DespatchedDeliveryNotification tothe SAP NetWeaver system, which converts the message into the IDocDESADV.DELVRY03 and transfers it to the customer�s ERP system.

5. Receive advanced shipping notification (customer�s ERP system).6. Receive advanced shipping notification and post goods receipt (customer�s

ERP system).

When the customer posts the goods receipt, the customer�s ERP systemsends the STPPOD.DELVRY03 IDoc to the SAP NetWeaver system. TheSAP NetWeaver system converts the IDoc into an XML message of typeReceivedDeliveryNotification and transfers it to SAP SNC.

7. Display goods receipt information (SAP SNC).

Kanban AlertsException during validation of Kanban object (alert ID 7093)

SAP SNC has detected a problem during validation of an inbound purchaseorder.This alert might be of special interest for monitoring errors in XML inboundprocessing for the Kanban process.

New Kanban request (alert ID 7091)SAP SNC generates this alert automatically when a new Kanban requestarrives.If you modify the alert (for example, the alert priority) or want to suppressgeneration of this alert, you must implement the BEFORE_NEWKNBNUPDmethod of the /SCA/KANBAN BAdI.



Late Kanban response (alert ID 7092)As customer, you expect the supplier to respond to an empty Kanban withina specific time and to create an ASN as a draft or to publish an ASN for theempty Kanban in SAP SNC. You define this response time in SAP SNC foreach Kanban control cycle.To monitor whether the response time has been adhered toand to make the supplier aware of delays, if necessary, run the/SCA/DM_KNBN_ALRT_LATERESP report regularly in the SAP SNCsystem. The report checks whether the response time has been exceeded forempty Kanbans. To determine a delay, the report adds the response timeto the time at which the Kanban request arrived in SAP SNC. If the timecalculated in this way is in the past, and the response time has therefore beenexceeded, the report generates the alert.To call the report for online processing, on the SAP Easy Access screen forSAP Supply Chain Management, choose Inventory Collaboration Hub→Supplier Collaboration→ Alerts→ Generate Alerts for Late Responseto Kanban Requests.If you modify the alert (for example, the alert priority) or want to suppressgeneration of this alert, you must implement the BEFORE_LATERESUPDmethod of the /SCA/Kanban BAdI.



Lesson Summary

You should now be able to:� Explain the Kanban process flow in SAP SNC� Name the Kanban Aalerts in SAP SNC



Lesson: Work Order Collaboration with SAP SNC

Lesson OverviewIn this lesson, you will learn about the work order collaboration process in SAPSNC.


� Explain work order process flow in SAP SNC� Name the work order alerts in SAP SNC

Business Example

BackgroundYou use the work order component to monitor the production progress at a contractmanufacturer. The contract manufacturer (hereafter referred to as �supplier�)regularly sends data about the progress of the production process in the work order(component quantities used, WIP, scrap, completed final product quantities). Asa result, the phase between issuing the purchase order and the goods receipt atthe customer location is more transparent for the customer, who can then reactin sufficient time to potential exception situations (for example, if componentsare missing or a low yield is expected).

The work order supports collaboration between customer and supplier. In thework order, the business partners can negotiate dates/times, quantities, andthe components to be used. The partners can also make documents visible inthe work order, such as documents that contain production instructions (likespecifications and drawings). Work order collaboration is integrated in purchaseorder collaboration in SAP SNC.

The basis for collaboration between the customer and the supplier in contractmanufacturing is the work order order object, which combines the characteristicsof a purchase order and a production order. Along with the delivery dates/timesand quantities for the ordered final product, the work order contains the billsof material and routing information � but only to such detail as required bythe customer to monitor the production progress at the supplier. This includesthe most important input and output components and the relevant work steps(called phases), including quantities, durations, and consumption and availabilitydates/times.


SNC100 Lesson: Work Order Collaboration with SAP SNC

Creation of Work Orders and Master DataSAP SNC creates the work order based on a purchase order or subcontract orderthat the customer has sent from his or her back-end system to SAP SNC using aReplenishmentOrderNotification. A work order can be created either automaticallyupon receipt of the ReplenishmentOrderNotification, or later with a special reportthat the customer executes in the SAP SNC system. SAP SNC can create multiplework orders for a purchase order (one for each purchase order item or one foreach purchase order schedule line). SAP SNC determines the components andphases from the master data. It then uses this data and the purchase order data(requested quantities and requested dates and, in the case of subcontract orders,subcontracting components) to create the work order. A new SNC-specific masterdata object, the phase structure, is available for creating work orders. In an SCMserver installation, however, you can also use special sources of supply forin-house production from SAP Advanced Planning & Optimization (productiondata structures and production process models for Supply Network Planning).

Negotiation PhaseAfter creating the work order, the customer publishes it in SAP SNC with hisor her request data. This opens an (optional) negotiation phase, in which thecustomer and supplier agree on the quantities and dates/times that the supplier isto comply with. This includes the quantities and dates/times for deliveries or theconsumption quantities of the components. The supplier checks the work order,and either confirms the requested data or proposes other dates/times and quantities,for example, in the case of capacity bottlenecks arising from the requested data.The customer checks the supplier confirmations, and approves them or proposesnew requested data. The negotiation phase lasts until the customer and supplierhave reached an agreement and all work order data has a corresponding status.

Execution PhaseWhen the request data and confirmation data match, the execution phase begins,in which the supplier produces the ordered products. During the execution phase,the supplier regularly updates the work order with actual phase data (actual inputand output quantities, actual consumption and availability dates/times, scrap,WIP). Based on the actual data, SAP SNC calculates the delivery quantities anddates/times expected (projected data) and displays these in the work order.

When entering the actual data, the supplier can classify the produced quantities,for example, as yield. If the supplier cannot decide how to handle a certain batch,he or she can set the batch to On Hold. A special alert informs the customer aboutthis, and the customer can decide whether the supplier should continue processingthe batch, rework the batch, or scrap it.



Action-Based and Alert-Based Work Order ProcessingSAP SNC uses required actions and alerts to guide the business partners throughthe negotiation and execution of a work order. SAP SNC creates required actionsautomatically and displays them on the Web UI. Required actions containinformation about which business partner has to do what next. SAP SNC can, forexample, create a required action if the supplier is to react to a new work orderfrom the customer, or if the projection based on actual data determines a latedelivery or an insufficient delivery quantity. In addition, SAP SNC creates alertsfor the required actions. Business partners can use alert notification to receivemessages about the required actions.

Web User InterfaceOn the SAP SNCWeb UI, the customer and the supplier have a joint and consistentview of the data and status of the work order. On the Web UI, the customer andthe supplier display the work order, negotiate it, and update it with actual data. Inthe Work order overview, the partners can select work orders according to variousselection criteria, for example, according to actions required for the work orders.They can navigate from the work order overview to the work order details. TheWork order details contain all data and functions required to process the workorder. The customer can use this to process the request data, for example.

The supplier can create confirmation data in the negotiation phase and actual datain the execution phase. In the Work order details, the customer and the supplieralso see which actions are currently required for a work order. The supplier, forexample, sees that he or she has to react to a new work order. The customer, forexample, sees that he or she has to decide how the supplier is to handle a batchthat was put on hold.

Consensus Finding with Deviation AnalysisSAP SNC supports the negotiation phase with an automatic approval process. Thisoccurs when the supplier publishes confirmation data in SAP SNC. The approvalprocess checks whether the supplier's confirmation data and the customer's requestdata match within customer-defined quantity tolerances and date/time tolerances.If so, SAP SNC accepts the confirmation data.

Deviation analysis is used in the execution phase as well. Here, SAP SNCdetermines critical deviations between the planning data and the actual data, orbetween the planning data and the projected delivery data, and creates actionsand alerts based on the results.



Update of the Purchase Order in SAP SNC and in theCustomer Back-End SystemA special indicator in the purchase order overview and in the SAP SNC purchaseorder details shows whether a work order has already been created for a purchaseorder.

If the customer and supplier for a work order have reached an agreement and thework order is published, SAP SNC also updates the purchase order for which thework order was created. In so doing, SAP SNC copies the confirmation data tothe request schedule lines of the purchase order item. The purchase order nowcontains identical request schedule lines and confirmation schedule lines with thestatus Accepted. SAP SNC then uses a ReplenismentOrderNotification to send thepurchase order schedule line to the customer back-end system, so that the purchaseorder is updated in the customer back-end system as well.

SAP SNC also updates the purchase order during confirmation of current data.When the supplier confirms the actual consumed quantity of the subcontractingcomponents during the completion of a phase, the quantities of the subcontractingcomponents are updated in the confirmation schedule lines as well.

Work Order UpdateThe customer can, at any time, in his or her back-end system, change a purchaseorder for which a work order already exists. He or she can, for example, createnew schedule lines. When the back-end system sends the purchase order to SAPSNC, the work order is automatically adjusted there, and a new negotiation phasebegins for the changed data.

Work Order Configuration1. To call up work order configuration, on the SAP Easy Access screen, choose

Supply Network Collaboration→ Master Data→ Application-SpecificMaster Data→ Work Orders→ Work Order Configuration.

2. Under General Settings for Work Orders, determine the following:

� For which characteristics combination (for example, supplier andproduct) should the configuration settings apply?

If you do not enter any characteristics, the settings apply to all workorders. An entry of this kind determines the standard setting for workorders. You can exclude work orders having a certain characteristicscombination from the standard setting by creating an additional entrywith this characteristics combination and the desired setting.

� Should the system create work orders for a purchase order automaticallyupon receipt of the purchase order from the customer back-end system?

� Should it be possible to create work orders in SAP SNC using thereport for creating work orders?



� How many work orders should the system create for a purchase order:one per item, then with multiple deliveries, or one for each requestschedule line?

� Should a work order be published immediately upon its creation, orafter its update through a changed purchase order?

� Of what type should the work order be?� Should the Instructions tab page display the Bin column?

The Bin column is relevant if you use binning. In the Bin column, you,as customer, specify the bin in which a test program sorts a product.

3. If you want to use a phase structure to create work orders, make thefollowing settings:

� Create a phase structure under Phase Structures.� If you want to use external components for a work order, define

component assignment rules under Component Assignment Rule.Component assignment rules are relevant when the work order is touse external components (components from a subcontract order orcomponents from a PPM/ PDS).

4. Make the following settings under Master Data Assignment:

� Determine which master data the system uses to create work orders.You have the following options:

- Phase structure

- Production process model or production data structure

- Phases from the phase structure, or components from the PPM orfrom the PDS

� If you use a phase structure to create work orders, proceed as follows:

- Specify the name of the phase structure.

- If the work order is to use external components, specify the name ofthe component assignment rule that you want the system to use toassign the external components to the phases.

Hint: Leave the Phase structure field blank if you are usingproduction process models or production data structures forSupply Network Planning to create work orders. The systemdetermines these master data objects automatically using theSAP APO source-of-supply determination.

� Specify the time period the master data assignment is to be valid.� For the system to consider this master data assignment, you have to

set the Active indicator.



Master Data for Phase CreationPhase Structure

The phase structure is an SNC-specific master data object that represents thedifferent phases for the production of a product. In the phase structure, youcan assign input and output components directly to every phase. The inputcomponents of a phase are consumed at the beginning of a phase, and theoutput components are provided at the end of a phase. You can make settingsin the phases of the phase structure as to whether and how a phase uses thecomponents from the subcontract order. The system copies the componentsto the phase when creating a work order.

Production Process Model or Production Data Structure for Supply NetworkPlanning

You can only use this master data if SAP APO is installed in the system(SCM server installation). During work order creation, the system uses thesource of supply determination from SAP APO to determine a productiondata structure (PDS) or a production process model (PPM). The systemcreates a work order phase for every PDS or PPM activity. The systemassigns the input and output components of the activity to the phase (inputcomponents to the phase beginning, output components to the phase end).The phase sequence corresponds to the sequence of activities in the PDS orPPM. The phase IDs are identical to the activity IDs.

Phase DurationsSAP SNC only supports phases that have a quantity-independent (fixed) netphase duration. In the phase structure, therefore, you can only define phaseswith a fixed net duration. In the case of a PPM or PDS, SAP SNC likewiseonly considers the fixed duration of the activities.

Phase StructureThe phase structure is a master data object in SAP SNC that serves as anorder-neutral basis for creating work orders.

The phase structure describes the sequential phases that the supplier executeswhen producing a product. A phase represents a specific stage in the production ofa product, such as assembly or test. The phase duration is independent of quantity.A process-related, quantity-independent break can follow a phase. The successorphase begins at the end of this break.

During work order creation, SAP SNC uses the phase structure to determine thefollowing data for the production phases of the work order:

� When, at the latest, does the supplier have to start each production phase andwith which input component quantities to facilitate on-time delivery?

� When is each production phase completed and when does it provide therequired output component quantities?



SAP SNC determines the consumption and availability dates/times of the inputand output components by using backward scheduling based on the shippingdate/time. In so doing, SAP SNC considers the duration of the phases and breaksfrom the phase structure, as well as the production calendar at the supplier'sship-from location.

StructureDefine the following data in the phase structure for a phase:

� Phase ID and phase description

You can use this data to identify a phase on the Web UI for work ordersand in the XML messages for work orders (ID only).

� Sequence number

You assign a number to every phase of the phase structure. In so doing,you determine the sequence in which the supplier has to execute thephases.

� Phase duration

SAP SNC only supports phases with fixed net phase duration, in otherwords, phases whose duration does not depend on the quantity to beproduced.

� Duration of the break following a phase

The break immediately follows a phase. The next phase can beginafter the break, at the earliest. A break can be process-related, forexample, if paint has to dry. The break duration does not depend on thequantity to be produced.

� Phase type

The phase type is a classification characteristic for phases which youcan use to differentiate between an assembly phase and a test phase,for example. You create codes and descriptions for phase types inCustomizing for the work order.



ComponentsEvery phase of a phase structure must have at least one input component andone output component assigned to it. You have the following options forassigning components to a phase:

� Assign components directly

Here you assign the input and output components directly to the phasein the phase structure.

� Use components from the subcontract order

Here you make settings in the phase structure so that the phase usescomponents from the subcontract order. The system copies thecomponents from the subcontract order to the phase when creatinga work order.

The phase can use components from the subcontract order in additionto the components assigned directly. However, you can also leave thephase empty (do not assign components), and only use componentsfrom the subcontract order for the phase. You determine in the phasewhether and how the phase uses components from the subcontract order.

� Use components from a PPM or PDS

Here you only need an empty phase structure. When creating the workorder, the system determines a PPM or PDS and copies the componentsof the PPM or PDS to the work order. To assign the components to thephases, you need a component assignment rule. You enter this rule inthe master data assignment of the work order configuration.



Components Assigned DirectlyYou can assign the input and output components used or provided by a phasedirectly to that phase in the phase structure. The phase structure differentiatesbetween the following types of output component:

� Primary product

The primary product is the product that is ordered by the customer andwhich is to be produced with the phase structure. You can only definean output product of the phase structure as the primary product. Use thePrimary product indicator to do this.

� Output component that is processed as input component in a nextphase

In this case, the output component of a phase is needed as an inputcomponent by the phase that immediately follows. This is required,for example, if one primary product is processed in several sequentialphases.

� Output component to be delivered together with primary product

Use this option for an output component of a phase that is to bedelivered to the customer together with the primary product withoutfurther processing (co-product). Such an output component cannot bethe input component of the following phase.

To differentiate between input and output components, use the Input/Outputindicator in component maintenance.

Transportation PhaseThe transportation phase is the phase between the shipping of a product at thesupplier's ship-from location and the inbound delivery at the customer location.You do not create the transportation phase in the phase structure; the systemcreates it automatically during the creation of work orders, using data from thepurchase order schedule line.

Consistency Check for Phase StructuresYou can use the consistency check to check whether you have maintained a phasestructure consistently.

From the SAP Easy Access screen, choose Master Data→ Application-SpecificMaster Data→ Work Order→ Perform Consistency Check for Phase Structures.



Statuses of the Work Order ItemContents in Negotiation (CINE)

The work order item contains at least one phase with a planned phaseinput/output (PIO), which the customer and supplier still have to negotiate.Such a PIO has the status In Negotiation (INEG).

Contents Canceled (CCNL)All request PIOs and confirmation PIOs are canceled.

Contents Rejected (CREJ)The supplier has rejected all the customer's request PIOs.

Contents in Agreement (CIAG)All of the PIOs are either in agreement or canceled (at least one PIO mustbe in agreement). The work order therefore no longer contains any PIOswith the status INEG.

Contents in Execution (IEXE)The supplier has started with production and has reported an actual phaseinput (component consumption) for the first phase.

Production Completed (PRCO)The supplier has completed production and has reported the last actual phaseoutput (completed components) for the last production phase.

Shipped (SHIP)The supplier has sent the last delivery to the customer and has reported thelast phase input for the transportation phase.

Execution Completed (EXCO)The customer has received the last delivery and has reported the last phaseoutput for the transportation phase. The work order is complete.

Closed (CLSD)The customer no longer requires the completed work order with statusEXCO, and has closed the work order using the report for closing workorders.

Phase StatusContents in Negotiation (CINE)

The phase contains at least one PIO that the customer and supplier must stillnegotiate. Such a PIO has the status In Negotiation (INEG).

Contents Canceled (CCNL)All request PIOs and confirmation PIOs are canceled.



Contents Rejected (CREJ)The supplier has rejected all request PIOs of the phase.

Contents in Agreement (CIAG)All PIOs of the phase are either in agreement or canceled\ (at least one PIOmust be in agreement). The phase therefore no longer contains any PIOswith the status INEG.

Contents in Execution (IEXE)The supplier has reported the first actual phase input for consumed inputcomponents for the phase.

Execution Completed (EXCO)In a production phase, this status means that the supplier has reported thelast actual phase output and has set the Phase Completed indicator. Thesupplier, therefore, has completed the last output component.In a transportation phase, this status means that the customer has reportedthe last actual phase output and has set the All Delivered indicator. Thecustomer, therefore, has received the last inbound delivery.

Shipped (SHIP)This status is only relevant for transportation phases. The transportationphase obtains this status when the supplier reports the last phase input forthe transportation phase and sets the All Shipped indicator. The supplier,therefore, has sent the last delivery to the customer.

Negotiation-Relevant Statuses of Request PIOs andConfirmation PIOsIn Negotiation (INEG)

The PIO is part of the negotiations between the customer and supplier. Thecustomer and supplier are therefore still negotiating whether to use the PIOas the plan PIO or to cancel it.

In Agreement (IAGR)the customer and supplier have reached an agreement for the PIO. The PIOis therefore a plan PIO that the supplier must comply with.

Rejected (REJE)The customer or supplier has rejected the confirmation PIO or the requestPIO.

Canceled (CNCL)The PIO owner has canceled the PIO.



Draft (DRFT)As long as the customer or supplier has not yet published a work order,a new or changed request PIO or confirmation PIO has the status Draft(DRFT). The change here can also be a status change, for example, throughrejection of a PIO. When the business partner publishes the work order,new or changed PIOs lose their Draft status. The other business partnernow has to react to the proposals.As long as a business partner is processing a PIO and the PIO has the statusDraft, the other business partner cannot process the PIO.

Cancellation Requested (CARE)This status is relevant if customer and supplier have already reachedan agreement for a PIO and the PIO has the status IAGR. To request acancellation, the owner of a PIO having the status IAGR can use the Cancelfunction. A cancellation request can also be made indirectly if the PIO ownercreates a counterproposal for this PIO by changing the quantity or date/timeof the PIO, or by splitting the PIO.SAP SNC creates the Respond to Cancellation Request action for the otherbusiness partner.

Cancellation Rejected (CARJ)A business partner has rejected the cancellation request from the otherbusiness partner with respect to the latter's PIO, which already has the statusIAGR.

Capture of Actual DataAs of the start of production, the supplier reports actual data (actual PIOs) forthe work order. This includes the quantities and dates/times of consumed inputcomponents, the quantities and dates/times of created output components, and thecompletion of a production phase. When the supplier sends a delivery to thecustomer, he or she reports an actual transportation phase input. The customerreports when he or she receives a delivery (actual transportation phase output).The customer and supplier can capture actual data as follows:

� Manually, on the Work Order Details screen on the Production Log tab page� Using XML messages that the business partner sends from his or her

back-end system to SAP SNC

SAP SNC considers the actual data immediately and updates projected deliveries,required actions, and alerts. The business partner that captures actual data does nothave to publish the work order beforehand.



Use of Actual DataThe system uses the actual data as follows:

� The system compares the actual data with the planned data and usesrequired actions and alerts to inform about deviations.

� The system uses the actual data to calculate projected deliveryquantities and dates/times. Every time the supplier captures actual dataand saves the work order, the system uses the actual data to calculatethe primary product quantities that are (theoretically) in every phaseor waiting between two phases for further processing. The customerand supplier can see these partial quantities on the Tracking tab pagein the Production Overview screen section. The system calculates theanticipated completion date/time and the anticipated available yield foreach of the partial quantities. The system displays this data for therespective partial quantities in the production overview. In the case ofcritical deviations between the projected delivery data and the planneddata, the system likewise creates required actions and alerts.

Capture of Actual Data for Production Phases (Supplier)The supplier reports the following data for a production phase:

� Which input component quantities he or she has consumed and when� Which output component quantities he or she has createdWhen the supplier has completed a production phase for the work order andhas reported the last output component quantity for this phase, he or she setsthe status Phase Completed for this partial quantity. At the end of a phase,the system also updates the subcontract order that was created by the workorder: The system copies the actual data for the subcontracting componentsassigned to the phase as component consumptions in the subcontract order.

Classification of Reported QuantityWhen capturing actual data, the customer and supplier classify the reportedquantity using a progress report code. The following table shows theavailable progress report codes.

ProgressReportCode

For Input or Output? Description

Start Input of a productionphase

The supplier uses this code for an inputcomponent quantity of a productionphase.

Scrap Output of a productionphase

The supplier uses this code for an outputcomponent quantity of a productionphase if this quantity is scrap.



Yield Output of a productionphase

The supplier uses this code for an outputcomponent quantity of a productionphase if this quantity meets the qualityrequirements.

On Hold Output of a productionphase

The supplier uses this code for an outputcomponent quantity of a productionphase if he or she wants to let thecustomer decide whether the quantity isa yield or scrap or whether the suppliershould rework this quantity.

Reworked Output of a productionphase

The supplier uses this code for an outputcomponent quantity of a productionphase if he or she has reworked aquantity that was previously on hold, byinstruction of the customer.

Scrapped Output of a productionphase

The supplier uses this code for an outputcomponent quantity of a productionphase if he or she has scrapped aquantity that was previously on hold, byinstruction of the customer.

Shipped Input of thetransportation phase

The supplier uses this code for aquantity that he or she has sent to thecustomer (input component quantity ofthe transportation phase).

Delivered Output of thetransportation phase

The customer uses this code for aquantity that he or she has received fromthe supplier (output component quantityof the transportation phase).

Alerts and Required ActionsThe system monitors the work order in the negotiation phase and executionphase. If a situation arises to which a business partner must react, the systemautomatically creates an alert for the business partner. For example, SAP SNCcreates an alert if the supplier is to respond to a new customer work order, or ifthe system determines a large quantity deviation or date/time deviation betweenactual data and planned data. The alert notification can send the alerts to thecustomer and to the supplier.

If an alert relates to the negotiation or execution of plan PIOs in the work order,the system also creates the required actions for the affected plan PIOs. A requiredaction represents an instruction for a particular business partner. The responsiblebusiness partner must execute this action to resolve the alert situation for theaffected plan PIOs. For example, if the customer publishes a newly-created



work order, the system creates the Respond to Proposal action for the supplier.The supplier is to confirm the work order or make counterproposals. The actionsthat the system creates in the case of deviations between actual data and planneddata, for example, are directed to the customer. The customer is responsible forstarting a new round of negotiations and, for example, negotiating a shift indelivery dates/times. The alert for deviations in actual data is directed to bothbusiness partners.

Publish Changes (alert type 7110)The system displays this alert type when the customer or supplier hasprocessed the PIOs in the work order but has not yet published the changes.The work order therefore contains PIOs with the status Draft. The businesspartner that made the changes must publish the work order so that the otherbusiness partner can react to the proposals.The system also displays this alert if the system does not publish the workorder directly after its creation. The customer has to publish the work ordermanually on the Web UI or use the publication report.

� Addressee: The business partner that made the changes� Required action: Publish Changes

Respond to Proposal (alert type 7112)The system creates this alert type when the customer or supplier publishesthe work order with new or changed request PIOs or confirmation PIOs. Theother business partner has to react to the proposals.

� Addressee: The other business partner� Required action: Respond to Proposal

Respond to Rejection (alert type 7111)The system creates this alert type when the customer or supplierrejects a confirmation PIO or request PIO directly or indirectly (with acounterproposal) in the negotiation phase. As a result, the PIO receivesthe status INEG and REJE

� Addressee: The other business partner� Required action: Respond to Rejection

Provide Actual Data (alert type 7114)The system creates this alert type when the work order receives the statusCIAG. The customer or supplier has thus reached an agreement for a workorder. The supplier must now report actual data for the production phases(when did he or she consume or provide which component quantity inwhich phase?).

� Addressee: Supplier� Required action: Provide Actual Data



Provide Shipping DataThe system creates this alert type when the work order receives the statusPRCO. The supplier has thus completed the last production phase. Thesupplier now has to report transportation phase inputs (when did he or sheship which quantity to the customer?).

� Addressee: Supplier� Required action: Provide Shipping Data

Provide Delivery DataThe system creates this alert type when the work order receives the statusSHIP. The supplier has thus completed the transportation phase, in otherwords, has sent the last partial quantity to the customer. The customer nowhas to report transportation phase outputs (when did he or she receive whichpartial quantity?).

� Addressee: Customer� Action: Provide Delivery Data

Actual Data Outside of Tolerance Range (alert type 7115)The system displays this alert type when it determines a deviation inquantities or dates/times between the planned data and the actual data. Thecustomer and supplier must react to this, and agree to shift the date/time orchange the quantity.

� Addressee: Customer and supplier� Required actions:

Process Low Actual Quantity

Process High Actual Quantity

Process Late Actual Completion

Process Early Actual Completion

Projected Data Outside of Tolerance Range (alert type 7116)The system displays this alert type when it determines a deviation inquantities or dates/times between the planned data and the projected deliverydata that lies outside of the allowed tolerances. The customer and suppliermust react to this, and agree to shift the date/time or change the quantity.

� Addressee: Customer and supplier� Required actions:

Process Low Projected Quantity

Process High Projected Quantity

Process Late Projected Completion

Process Early ProjectedCompletion



Confirm Cancellation (alert type 7113)The system creates this alert type when the customer or supplier wants tocancel a planned request PIO or confirmation PIO in a work order that hadalready been agreed upon (status CIAG). The other business partner mustaccept or reject the cancellation.

� Addressee: The other business partner� Required action: Respond to Rejection Request

Decide Status of On-Hold Components (alert type 7117)The system creates this alert type when the supplier reports an actual PIOand classifies the actual PIO as On Hold. The supplier thus does not knowhow he or she is to proceed with this partial quantity (continue, rework, orscrap). The customer must now decide.

� Addressee: Customer� Required action: Decide Status of On-Hold Components

Process On-Hold Components According to Decision (alert type 7118)The system creates this alert type when the customer has made a decision foran on-hold actual PIO as to how the supplier is to proceed with the partialquantity. The supplier must process the quantity according to the customer'sdecision. There is an action type for every possible decision.

� Addressee: Supplier� Required actions:

Rework

Scrap

Continue

Acknowledge Note (alert type 7119)The system creates this alert type when the customer or supplier has createda note in the work order. The other business partner must acknowledge thathe or she has read the note.

� Addressee: The other business partner� Action: Acknowledge Note

Exception During Validation of Work Order (alert type 7109)The system has determined an exception while validating the work order.There are no required actions.



Process

Figure 67: Generate WO from PO

Figure 68: Finish WO



Figure 69: Publish PO

Figure 70: Negotiate (Supplier)



Figure 71: Negotiate (Customer)

Figure 72: Agreement



Figure 73: Publish changes to Customer Backend

Figure 74: Report Production Progress



Figure 75: Report On-Hold Situation

Figure 76: Decide on On-Hold Situation



Figure 77: Analyze Exception

Figure 78: Change Plan



Figure 79: Negotiate Changes

Figure 80: Continue providing actual data



Figure 81: Complete WO



Figure 82: Report Delivery Receipt

1. Send purchase order to SAP SNC (SAP ERP).

The customer creates a purchase order or a subcontract order in his or her ERPsystem. The ERP system sends the purchase order or subcontract order to thecustomer's SAP NetWeaver system, using the IDoc ORDERS.ORDERS05(purchase order) or PORDCR1.PORDCR102 (subcontract order). TheSAP NetWeaver system converts the IDoc into an XML message of typeReplenishmentOrderNotification and sends it to SAP SNC.

2. Create work order (SAP SNC).

SAP SNC creates a work order for the purchase order.

3. Send purchase order to supplier back-end system (SAP SNC).

To do so, SAP SNC uses a ReplenishmentOrderNotification.

4. Send work order to supplier back-end system (SAP SNC).

To do so, SAP SNC uses a ManufacturingWorkOrderRequest.

5. Send work order confirmation to SAP SNC (supplier back-end system).

To do so, the supplier back-end system uses a ManufacturingWorkOrder-Confirmation.

6. Update work order and purchase order (SAP SNC).

SAP SNC updates the work order based on the work order confirmation.

When the customer and supplier have reached an agreement for the workorder and the customer has published the work order in SAP SNC, SAP SNCupdates the purchase order with the confirmation data from the work order.SAP SNC copies the confirmed data from the work order as identical requestdata and confirmation data to the purchase order. To update the customerback-end system as well, SAP SNC sends the updated purchase order to theSAP Net Weaver system of the customer, using an XML message of typeReplenishmentOrderConfirmation. The SAP NetWeaver system maps theReplenishmentOrderConfirmation to the IDoc ORDERSP.ORDERS05 andsends the IDoc to the customer's ERP system.

7. Send actual data to SAP SNC (supplier back-end system).

As of the start of production, the supplier regularly reports actual data: Whendid he or she start which phase with which component quantity? When did aphase create which component quantity? When did the supplier complete aphase with which component quantity?

To send this data, the supplier uses an XML message of typeManufacturingWorkOrderWorkInProcessNotification.



Lesson Summary

You should now be able to:� Explain work order process flow in SAP SNC� Name the work order alerts in SAP SNC


SNC100 Lesson: SNI and Subcontracting PO

Lesson: SNI and Subcontracting PO

Lesson OverviewThis lesson will introduce you to the capabilities of the SNI Monitor and thesubcontracting purchase order in SAP SNC


� Describe the SNI and subcontracting PO process flow in SAP SNC� Name the alerts for SNI and subcontracting POs in SAP SNC

Business Example



BackgroundSupply Network Inventory

The SNI Monitor is a function on the SAP Supply Network Collaboration(SAP SNC) Web UI that supports the Supply Network Inventory (SNI)business scenario. Using the SNI Monitor, both customers and suppliers canmonitor the stock situation of selected products in customer or supplierlocations as part of a subcontracting scenario. Customers and suppliers havethe same view of the most important components of the end product that thesupplier produces on behalf of the customer, providing a quick overviewof critical stock situations. The SNI Monitor is not limited to one supplyrelationship between a customer and a supplier. On the contrary, it alsosupports more complex supply networks, such as:

� Supply networks with one customer and suppliers of the first level ,second level , third level, and so on (supplier, supplier's supplier)

� Supply networks with customers, suppliers, and third-party logisticsproviders

The SNI Monitor provides a period-oriented, time-series-based view ofthe demands, receipts, and stocks of the components that the customer andsupplier transfer from their back-end systems to SAP SNC for the productsthey manage. Alternately, the supplier can manually enter the demandand receipt data for his or her components in the SNI Monitor. This is ofparticular relevance for suppliers that do not use an ERP back-end systemor an EDI. In addition, you can get an overview of in-transit quantities andsubcontracting reservations.SAP SNC calculates the projected stock from the demand, receipt, and stockdata. The projected stock provides information about the demand/stockbalance of a location product in each period. SAP SNC compares theprojected stock and the actual stock on hand with the minimum andmaximum stock levels of the location product agreed upon between thecustomer and the supplier. If these stock thresholds are violated, SAP SNCgenerates alerts.A simulation function is also available for the customer. Customers can usethis function to determine how changed receipts affect the projected stock ofthe components that they procure for the supplier.



Subcontracting Purchase OrderThe subcontracting PO is similar to the standard purchase order in SAP SNC.In addition to the standard PO, the subcontracting PO has information aboutthe required components for a subcontracting item.

Caution: The subcontracting components are transferred togetherwith the subcontracting PO. There is no master data (BOM) or anyBOM resolution in SAP SNC.

The component consumption for a subcontracting PO is part of theconfirmation function. This means the supplier should confirm date andquantity not only for the subcontracting product, but also for the componentconsumption.

Monitoring Customer, Supplier, and Supplier'sSupplier ProductsOf particular interest in a subcontracting scenario are the components that thesupplier needs to produce the finished product that the customer has requested bymeans of a subcontracting purchase order. This is because critical stock situationswith regard to components jeopardize the timely availability of the finishedproduct. You use the SNI Monitor primarily for monitoring subcontractingcomponents that the customer provides to the supplier. The SNI Monitor alsoenables monitoring of additional, particularly important components that thesupplier needs to manufacture the finished product. Such components areproduced by the supplier itself or procured from other suppliers.

Caution: The SNI Monitor does not support bills of material (BOMs),and it does not map the hierarchical relationships between the componentsof a BOM. A user who wants to work with the SNI Monitor must knowwhat the BOM looks like.

The SNI Monitor does not support supersession/product substitution.

Data TransferSNI

The customer sends data from his or her back-end system to SAP SNC. Thesupplier makes data available for products either by sending the data from aback-end system to SAP SNC or by entering the data manually in the SNIMonitor. In addition, a supplier can transfer data for products belonging tohis or her suppliers. To transfer data to SAP SNC, customer and supplier useProductActivityNotification XML messages, which contain all the relevantdata ("full replacement").



Subcontracting POThe customer sends subcontracting purchase orders to SAP NetWeaver usingthe IDoc PORDCR1.PORDCR102 . SAP NetWeaver maps the IDoc to anXML message of type ReplenishmentOrderNotification, which is sent toSAP SNC.Confirmations for date and quantity, as well as componentconsumption, are send back to the customers back-end system using theReplenishmentOrderNotification message. SAP NetWeaver maps the XMLmessage to the IDoc PORDCH.PORDCH02, which is sent to the customer'sback-end system, where the subcontracting PO is updated.

Master DataThe same master data is required for a subcontracting PO as for a standard PO.

The afterwards master data is meant for the SNI process.

You must create the master data for supplier collaboration in the SAP SNC system.This includes the following master data:

� Business partners for customer and supplier� Internet user for customer and supplier� Customer location and supplier location� Location products:

� Location products at the customer location� Location products at the location of the supplier� Location products at locations of a third-party logistics provider or of a

supplier who you have mapped as an additional plant (3PL location) inyour ERP system

In the product location product master, enter the unit of measure for thequantity specifications in the SNI Monitor in the Base UoM field.

If you, as customer, use SAP ECC or SAP ERP as your back-end system,you can transfer the customer location products to SAP SNC by using theCore Interface (CIF).

Hint: Transportation lanes between customer and ship-fromlocations are not necessary.

The master data maintained in the different location products is the same as that inthe supplier-managed inventory (SMI) process:

� Minimum stock level� Maximum stock level� Rounding value



Visibility Concept in the SNI MonitorA multitude of business partners are involved in the Supply Network Inventory(SNI) scenario, including suppliers of a supplier or third-party logistics providersthat are not necessarily part of a transportation lane.

The profile-based and parameter-based visibility concept is available just forthis reason. It allows you to create visibility profiles for all involved users andbusiness partners in which the visibility of inventory data and key figures in theSNI Monitor is defined.

Data for a location product is only visible to a user on the SAP SNC Web UI ifthe user has authorization to display or change the location product. You can usethe profile-based and parameter-based visibility concept to additionally filtermaster data and movement data in the SNI Monitor. You filter the data by creatingprofiles for users or business partners that define which data a business partneris allowed to display.

This allows you, for example, to grant the following business partners access onlyto selected data in SAP SNC:

� Suppliers� Suppliers of a supplier� Third-party logistics providers

Selection modes for profile-based and parameter-based visibilityIn Customizing for Supply Network Collaboration, you can make settings tofilter the data with selection modes by choosing Basic Settings→ Visibility.Use selection modes to do this. A selection mode controls which data abusiness partner user is able to see. For profile-based and parameter-basedvisibility, the following standard selection mode for SNI is provided: TimeSeries and Inventory (Profile-Based) (TSDM_INV_C). With this selectionmode, the user can only see inventory data and key figures for the locationproducts that are defined in his or her visibility profiles.

Creating and assigning visibility control profilesYou can use the Maintain and Assign Visibility Control Profiles transactionto create visibility control profiles and assign users and business partners.



Figure 83: Visibility in the SNI Monitor

1. User AB of business partner ABC calls the SNI Monitor.2. The system searches the application data ID of the corresponding screen.

In this example, the application data ID is SNI.3. The system reads the visibility settings for application SNI in Customizing.

The system finds the Time Series and Inventory (Profile-Based) selectionmode (TSDM_INV_C). The selection mode is assigned to a profile-basedselection rule type in Customizing for visibility.

4. The system searches for the profiles that are assigned to user AB, businesspartner ABC, and application ID SNI.

5. The system finds a matching profile. In this profile, product A and locationX are predefined as filter criteria.

6. Result: User AB only sees inventory data and key figures for product Aand location X in the SNI Monitor.

Creation and Assignment of Visibility Control ProfilesYou can use this function to create visibility control profiles, with which youcan control the visibility of master data and movement data in the SNI Monitorfor users and business partners. Use this function to assign profiles to users orbusiness partners.



Definition of visibility control profilesYou can create visibility control profiles and assign users and businesspartners. In a profile, you can control the visibility of data in the followingways:

� Restrict visibility to specific master data, such as locations, products,or suppliers

� Restrict the visibility through the parameters Assigned Partner,Data-Providing Partner, and Owner

You can use these parameters to restrict the visibility of the data evenfurther. For example, if you enter the parameter Owner and businesspartner A, you can ensure that a user with this visibility control profilecan only see the master data and movement data for which businesspartner A is the owner.

Assignment of visibility control profilesYou can assign one or more visibility control profiles to a user or businesspartner, and delete assignments that are not needed:

� With the Application Data ID field, you restrict the visibility controlprofile to selected Web UIs.

Note: You can only select application data IDs for SNI(technical name: SNI�).

� You can restrict the validity of the profile to a time period.� You can use the Execute function to display all visibility control profiles

that are assigned to a user or business partner within a validity period.� You can use the User/Prtnr's Own Data Visible indicator to determine

the following: If a user is assigned to a business partner, he or she isallowed to display all products that lie in locations belonging to his orher assigned business partner. You can set this indicator to allow a userto access his or her own data without you first having to define a profile.

Note: Note the following ranking sequence when you createvisibility control profiles:

� Settings in a visibility control profile for a business partneruser override the settings in a visibility control profile for abusiness partner.

� Settings in a visibility control profile for an SNI applicationoverride the settings in a visibility control profile that is validfor all SNI applications.



Displaying visible dataYou can use the Display Visible Data report (transaction/SCF/SNC_VIS_DATA) to obtain an overview of which data is displayed toa user or business partner who has the specified profiles.

SNI AlertsSAP SNC offers two groups of alerts for the SNI process :

� Inventory alerts for SNI� Rule based SNI alerts

Inventory alerts for SNI are SAP predefined alerts, just like those in other SNCapplications.

Rule-based SNI alerts are generated based on customer-defined rules.

Creating and managing SNI alert rulesYou can create and manage rules for SNI alerts. In an SNI alert rule, youdefine conditions that have to be met before the system generates an SNIalert. Use this function if you want to define your own conditions for SNIalerts; these conditions must be met before the system generates alerts forlocation products.

Hint: This function is only available for customers. The customer'ssystem administration uses this function to create the alert rulescentrally. Alerts that are generated by the system based on thesealert rules are visible in the Alert Monitor for all business partnersinvolved (customer, supplier, supplier's supplier, and third-partylogistics provider).

Overview screen of all SNI alert rulesOn the Overview screen, you can search for existing alert rules for locationproducts and create, display, change, copy, or delete new alert rules. On theOverview screen, you can see all existing SNI alert rules for the productsthat you are allowed to display according to the SNI visibility concept. Ifyou choose Display→ Detailed, the system also shows you the location, theplanner, and the product for which the SNI alert rule is relevant.Choose Create Alert to start a background job for SNI alert rules that checksthe conditions in the alert rule and creates alerts.

Note: You can also create alerts using the Generate Inventory Alertsfor SNI transaction (/SCA/SNIALERTSWRITE).



Detail screen for creating and changing SNI alert rulesYou can define the following conditions and criteria for an SNI alert rule:

� Inventory: For example, inventory lies below a fixed value� Time period: For example, May 2008� Demand: For example, demand is larger than stock on hand� Days' supply: For example, days' supply is smaller than three days

� Product� Location� PlannerWith the Inactive status, you can create an alert rule but not yet release itfor the generation of alerts. You can assign a priority to every alert rule.Depending on this priority, the associated alerts for the alert rule have thepriority High, Medium, or Low.When you create an alert condition and then choose an alert condition, thesystem automatically displays further suitable fields for the alert condition.If you want to create multiple alert conditions, first create one alert conditionand choose Plus. The system then displays a further row for an alertcondition. You can choose Minus to delete an alert condition that is nolonger needed.ExampleA customer's planner, Smith, uses this function to monitor inventories thathis company needs for producing computers, which are stored at locationABC. If the demand for the product Hard Disk becomes larger than the stockon hand, the planner wants to be informed of this automatically by an alert.The planner therefore defines the following alert rule:

� Demand: Demand is larger than stock on hand

� Product: Hard Disk A� Location: ABC� Planner: Smith



GenerationSNI Alerts are generated by either PPF or report.

� The Post Processing Framework (PPF) generates inventory alertswhen a ProductActivityNotification arrives. Alert generation is notactive in the standard system; you must activate alert generationin the PPF (action profile /SCA/BOL_INVENTORY, action/SCA/BOL_INV_SNI_STOCK_CHECK).

� System administration has scheduled the /SCA/SNIIN-VALERTSWRITE report as a regular background job in the SAP SNCsystem. To call the report for processing in the dialog, on the SAP EasyAccess screen, choose Supply Network Collaboration→ Exceptions→Alert Generation→ Generate Inventory Alerts for SNI.

Below min. � projected stock (SNI) (alert ID 7061)The projected stock is below the minimum stock level.

Above max. - projected stock (SNI) (alert ID 7062)The projected stock exceeds the maximum stock level.

Out-of-stock - projected stock (SNI) (alert ID 7063)The projected stock is zero or below zero.

Below min. - stock on hand (SNI) (alert ID 7071)The actual stock on hand is below the minimum stock level.

Above max. - stock on hand (SNI) (alert ID 7072)The actual stock on hand is above the maximum stock level.

Out-of-stock - stock on hand (SNI) (alert ID 7073)The actual stock on hand is zero.

SNI alert (alert ID 7060)Alert conditions that can be configured on a customer-specific basis fora location product have been met.

Subcontracting PO AlertsSNC offers the same Alerts for a Subcontracting PO as for a regular PO. Inaddition to these alerts a few more alerts exist for the Subcon PO process in SNC.

Manual approval of component requirement required (alert ID 7056)This alert is relevant for purchase order collaboration with approval process.The customer must accept the component requirement that the supplier hasconfirmed manually on the purchase order collaboration Web UI.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_ORDER, action /SCA/BOL_ORD_APPROVAL_ALERT).



Confirmation rejected (alert ID 7057)This alert is relevant for purchase order collaboration with approval process.The customer has rejected the component requirement that the supplier hasconfirmed manually on the purchase order collaboration Web UI.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_ORDER, action /SCA/BOL_ORD_APPROVALREJ_ALERT).

Component requirement rejected (alert ID 7058)This alert is relevant for purchase order collaboration with approval process.The customer has rejected the confirmation schedule line manually on thepurchase order collaboration Web UI.This alert is generated by the PPF (application /SCA/ICH, action profile/SCA/BOL_ORDER, action /SCA/BOL_ORD_APPROVALREJ_ALERT).

Data Transfer from ERP Systems to SAP SNC for SNIIn business scenarios such as Supply Network Inventory (SNI), customers andsuppliers can use reports in ERP systems to transfer relevant inventory data andkey figures to SAP SNC. This data is then displayed in the SNI Monitor.

There are two versions of the reports:

� Up to SAP ERP 2005, you can use the reports ROEMPROACT andRCMPROACT.

� As of SAP ERP 2005, enhancement package 2, you can use the reportsROEMPROACT2, RCMPROACT2, and RPRTPROACT.

Main differences between old and new reports

The new reports generate XML messages of the type ProductActivityNotification,which are sent from the ERP system to SAP SNC. All the new reports providethe following enhancements:

� They support the extraction of consignment inventory.� They transfer the new key figure In Transit, and the existing key figure

Demand has been split into the key figures Planned Demand, Firm Demand,and Forecast.

� With the new reports, you can also extract and send the supplier IDs forkey figure data.

� The new RPRTPROACT report is only available as of SAP ERP 6.0,enhancement package 2.

Purchase Order Collaboration with Approval1. Create subcontract order (SAP ERP 6.0).



The customer sends IDoc PORDCR1.PORDCR102 to SAP NetWeaver.SAP NetWeaver maps the IDoc to an XML message of typeReplenishmentOrderNotification, which is sent to SAP SNC.

2. Display subcontract order (SAP SNC).3. OPTIONAL: Change subcontract order (SAP ERP 6.0)

The customer sends IDoc PORDCR1.PORDCR102 to SAPNetWeaver, which maps the IDoc to an XML message of typeReplenishmentOrderNotification.

4. OPTIONAL: Display updated subcontract order (SAP SNC).

SAP SNC can now display the updated subcontract order.

5. Confirm sales order and update components (contract manufacturer�s ERPsystem).

The ERP system sends a message of type ReplenishmentOrderConfirmationto an SAP NetWeaver system at the customer site.

Caution: Mappings for the message flow between the supplier�ssystem and SAP SNC are not part of the standard delivery for SAPSNC because the mappings needed depend on the supplier systemused. If necessary, you must create the mappings as part of aproject-specific solution.

6. Receive ReplenishmentOrderConfirmation or confirm on Web UI and updatecomponents (SAP SNC).

SAP SNC receives the XML message from SAP NetWeaver. Ifthe OED keeps track of the components, the OED must update thecomponents manually. SAP SNC sends an XML message of typeReplenishmentOrderConfirmation to SAP NetWeaver, which maps the XMLmessage to the IDoc ORDRSP.ORDERS05.

7. Create confirmation in purchase order (customer�s SAP ERP system).8. Approve confirmation and component consumption (SAP SNC).9. Change schedule lines or components (SAP SNC).

SAP SNC sends a message of type ReplenishmentOrderNotification to SAPNetWeaver, which maps the XML message to IDoc PORDCH.PORCH02.

10. OPTIONAL: Change purchase order (customer�s SAP ERP system).

The customer�s SAP ERP system sends IDoc PORDCR1.PORDCR102to SAP NetWeaver, which maps the IDoc to an XML message of typeReplenishmentOrderNotification.

11. OPTIONAL: Update sales order (contract manufacturer�s ERP system).12. Update components (SAP SNC).



13. Create delivery (contract manufacturer�s ERP system).

The contract manufacturer�s ERP system sends an XML message of typeDespatchedDeliveryNotification to the customer�s SAP NetWeaver system,which in turn sends the message to SAP SNC.

14. Receive ASN or create on Web UI (SAP SNC).

SAP SNC sends a message of type DespatchedDeliveryNotification to SAPNetWeaver, which maps the message to IDoc DESADV.DELVRY03.

15. Receive ASN (customer�s SAP ERP system).16. Receive delivery and post goods receipt (customer�s SAP ERP system).

SAP ERP sends IDoc STPPOD.DELVRY03 to SAP NetWeaver, which mapsthe IDoc to an XML message of type ReceivedDeliveryNotification.

17. Update ASN (SAP SNC).

� The scope of the Contract Manufacturing Procurement business scenariooutlined in this documentation only concerns the customer side (OED). Thisbusiness scenario does not cover how an ERP system on the supplier�s side(that is, the contract manufacturer�s side) receives messages sent by thecustomer, and how it deals with the additional information (for example,components) submitted with these messages.

� Mappings are only provided for A2A communication (between the OED�sERP system and SAP SNC) from IDoc to XM,L and vice versa.

� This business scenario does not cover the tracking of the manufacturingprocess (production phases) that takes place at the contract manufacturer�ssite. It also does not take into account the current production phase at thecontract manufacturer� site. Consequently, the OED planner cannot predictthe supply situation of finished goods.

� The Contract Manufacturing Procurement business scenario has thefollowing limitations:

� Once a schedule line in the ERP purchase order is changed, the dateand quantity data originally requested are lost. Even if the informationis stored in SAP SNC, it is not possible to send this information tothe contract manufacturer.

� The Contract Manufacturing Procurement business scenario is based onfunctions introduced in SAP ERP 6.0. For lower releases, you need todevelop a customer modification.

� No data import control functions are provided for messages sent fromthe contract manufacturer to SAP SNC.

� The bill of material (BOM) is not available in SAP SNC.� New purchase order items cannot be created in SAP SNC.� Product substitution is not supported.� Scheduling agreements for the subcontracted material are not allowed.



� The subcontracting scenario of the RosettaNetWork Order ManagementProgram as described in the Partner Interface Processes 7B5 (Notifyof Manufacturing Work Order), 7B6 (Notify of Manufacturing WorkOrder Reply), and 7B1 (Work In Process Notification) is not includedin the scope of SAP SCM.

Business ExampleYour company procures computers from a subcontracting vendor. This contractmanufactured assembles the finished good - the computer from (simplified) threecomponents: a Harddisk, a Monitor and a Chip-set. The Monitor and the harddiskare subcontracting components which are managed and owned by you. TheChip-set is owned and managed by the supplier. You procure the monitor from athird party which directly delivers to your subcontractor.

Figure 84: Contract Manufacturing Procurement and SNI



Figure 85: Subcontracting with SAP SNC

Figure 86: Third-Party Procurement with SAP SNC



Figure 87: Combinations



Lesson Summary

You should now be able to:� Describe the SNI and subcontracting PO process flow in SAP SNC� Name the alerts for SNI and subcontracting POs in SAP SNC


Unit Summary SNC100

Unit SummaryYou should now be able to:� Explain the capabilities of SAP SNC dynamic replenishment� Explain the DCM process flow in SAP SNC� Name the DCM alerts in SAP SNC� Explain the Kanban process flow in SAP SNC� Name the Kanban Aalerts in SAP SNC� Explain work order process flow in SAP SNC� Name the work order alerts in SAP SNC� Describe the SNI and subcontracting PO process flow in SAP SNC� Name the alerts for SNI and subcontracting POs in SAP SNC


Unit 9Alert Notification (SNC)

Unit OverviewIn this unit, you will gain deeper insight into alert notification within SAP SNC.


� Explain the alert notification function� Discuss the functionality of Alert Notification Administration screen� List the prerequisites for alert notification within SAP SNC� Create your own message profile� Use alert notification in SAP SNC� Create your own SAP SNC alert

Unit ContentsLesson: Alert Notification in SAP SNC... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346Lesson: Relevant System Settings and Customizing for AlertNotification .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350Lesson: Process Demo & Exercise: Alert Notification ... . . . . . . . . . . . . . . . . . .355

Exercise 8: Alert Notification .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357Lesson: Creating own SNC alerts .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366


Unit 9: Alert Notification (SNC) SNC100

Lesson: Alert Notification in SAP SNC

Lesson OverviewThis lesson will explain alert notification in SAP SNC.


� Explain the alert notification function� Discuss the functionality of Alert Notification Administration screen

Business Example

BackgroundIn the SAP Supply Network Collaboration (SAP SNC) Alert Monitor, you can setspecifically to the user that SAP SNC informs you automatically about new alerts.You receive alert notifications by e-mail, SMS, or fax. and only for alert typesand location products that are relevant to you. Depending on your authorization,you can set alert notifications for all users, for all users of a business partner, orjust for yourself.

As you can imagine, a typical user will not be interested in all alerts that the SAPSNC system generates. As a prerequisite for alert notification, therefore, you mustset up a selection that defines which alerts a user should be notified about. Typicalselection criteria are Location, Product, Alert ID, or Planner.

After you have maintained a selection, you can create an alert notification profilethat refers to this selection.

Alert Notification ProfileAn alert notification profile mainly controls to whom and when an alert notificationis to be sent. You specify the following parameters in the alert notification profile.

Valid-from date, valid-to datePeriod in which the alert notification profile is valid


SNC100 Lesson: Alert Notification in SAP SNC

Recipient typeClassification of the user who should receive the alert notificationDepending on the recipient type, you have to specify additional data:

� If you choose Channel, you must enter the desired message channeland the destination address data (e-mail address, fax number, or � forSMS or pager � the telephone number).

� If you choose System User, you have to enter the desired messagechannel. As recipient address, the system uses the communication datafrom the user master that corresponds to the message channel.

Recipient (User)Addressee�s user name

E-mail addressUser�s e-mail address

SMS/Pager numberUser�s telephone number for SMS

Fax country/numberCountry and number of the fax

Sending userUser that the alert notification names as senderAs reply address, the alert notification contains communication data fromthe user master that corresponds to the message channel. If you do not entera sending user, SAP SNC uses the sending user from the alert notificationprofile.

Message channelTechnical medium with which SAP SNC sends an alert notificationIf you have enter Channel or System User as recipient type, you have to entera message channel.SAP provides partner-independent and user-independent standard messagechannels. System administration can set up partner-specific and user-specificmessage channels as required.

Message profileProfile that controls the structure of an alert notificationYou specify here whether you want to receive individual messages, collectivemessages, or aggregated messages for alerts.

AgeMinimum and maximum age (in hours) of the alerts about which SAP SNCshould inform you



Minimum priorityMinimum priority of the alerts about which SAP SNC should inform you

Immediate notificationIf you set this indicator, SAP SNC informs you immediately about alerts(provided the alerts fulfill the requirements with regard to minimum age andminimum priority).

Periodic notificationIf you set this indicator, SAP SNC informs you at regular intervals. With thisform of notification, SAP SNC determines the alerts periodically accordingto the pull mechanism. If you want to use periodic notification, specify thefollowing data:

� In the Start Date/Time field, specify the date and time when SAP SNCis to determine the alerts for the first time.

� In the Period [h] field, specify the time intervals in which SAP SNC isto determine the alerts. Specify the period in the format hhhhhhh:mm.

To send the alerts, use report /SCMB/ANOTPULL. Schedule this report asa background job to be run at regular intervals. The repeat period should besmaller than the time interval between the alert determination dates/timesthat you configured in the Period [h] field.

Note: You must enter ALEN in the Application field in the reportsettings.

Unacknowledged alerts onlyIf you set this indicator, SAP SNC only informs you about alerts that you oranother user have not yet acknowledged in the Alert Monitor.

Alert Notification AdministrationOn the Alert Notification Administration screen, an administrator can display,change, and delete existing notification profiles, as well create new notificationprofiles for other selections. Administrators assign profiles to other users.

You can copy notification profiles to create multiple notifications for a selection.You can also copy both the profile and the selection.

You can display the details and log entries of a specific notification by selecting itin the Profiles area of the screen.

Hint: You can only maintain notification profiles for partner-specificselections in the administration screen.


SNC100 Lesson: Alert Notification in SAP SNC

Lesson Summary

You should now be able to:� Explain the alert notification function� Discuss the functionality of Alert Notification Administration screen



Lesson: Relevant System Settings and Customizing forAlert Notification

Lesson OverviewThis lesson will introduce you to the prerequisites for alert notification withinSAP SNC.


� List the prerequisites for alert notification within SAP SNC� Create your own message profile

Business Example

SAPconnectSAPconnect must be properly configured to allow the SCM system to send outalert notifications via diverse channels like e-mail, SMS, and fax. Please contactyour Basis administrator for further details.

SelectionA valid selection is a mandatory prerequisite for alert notification within SAPSNC.


SNC100 Lesson: Relevant System Settings and Customizing for Alert Notification

You can define which alerts you want to be informed about. Maintain yourselection from the SAP SNC Web UI in the Alert Monitor screen (choose SAPSNC Web UI→ Exceptions→ Alert Monitor).

1. Create selection

Maintain the required selection parameters in the Selection block of theAlert Monitor.

2. Save the selection

To save your selection, open the Reset dropdown menu and select Save as ....

A dialog box appears.

3. Name the selection

In the dialog box, specify the name of the new selection and decide if theselection is partner-specific or user-specific.

User-Specific means that the selection is only visible to the actual user,while a partner-specific selection is visible to all users of a certain businesspartner (for example, supplier).

Use the Default checkbox to make the selection the default for the screen(Alert Monitor).

Message ProfileIn the previous lesson you have learned about the different settings in the AlertNotification profile. One is the Message profile.

In the message profile, you specify how the Alert Notification Engine assemblesan alert notification from the selected alerts.



You create message profiles from the Create / Change Message Profile transactionin the SAP Easy Access menu (choose SCM Basis→ Alert Notification Engine→Settings→ Create / Change Message Profile).

1. Assign a short description for the message profile and specify the applicationin which the alerts will be generated.

SAP SNC uses the ALEN application.

2. Specify the message mode.

� Individual message

A separate notification is sent for each alert that occurs.

� Collective message

At the time of notification, a message is sent to inform the recipient ofall existing alerts.

You cannot use this message mode for SMS or pagers.

� Aggregated message

At the time of notification, statistics on all alerts that have occurredare sent.

3. Specify the attachment type.

If you use the message channel e-mail direct, you can choose whether themessage texts belonging to the alerts are to be integrated in the notificationor provided as an attachment.

4. Specify a system message (message class and message number) in which thetext for the header and the reason for notification are defined. You can useup to four variables (Message Variable fields 1 to 4). The name of the alertnotification profile, the number of alerts, and the time of notification creationcan be inserted via the parameters &1, &2, and &3.

5. In the message parameters, specify the message categories and correspondingalert parameters according to which the individual alerts are to be sorted inthe alert notification.

6. For an aggregated message, use the Column indicator to define a matrix inwhich the statistical figures are set out. You can set this indicator in severalalert parameters and specify the order in which the associated columns areto be arranged.

Message ParametersThe alert parameters entered in the message profile control control whichinformation about an alert will be shown in the notification. The standard profile,SAP_COLL, only contains information about the location and the product.


SNC100 Lesson: Relevant System Settings and Customizing for Alert Notification

Which parameters are available depends on the individual alert. An inventoryalert, for example, will not contain a purchase order number. Which alerts containwhich parameters can be found in Customizing for the Alert Notification Engine.

Periodic NotificationFor alert notification profiles with the periodic notification option, a backgroundjob needs to be scheduled to send out the alert notification.

Your system administrator should schedule report /SCMB/ANOTPULL. Thefrequency of this job is smaller than the smallest value that is maintained in any ofthe alert notification profiles, for example, five minutes.

This job will check if any of the notification profiles need to be processed.

Hint: For immediate notification, no additional job is required to send outthe alerts. Nevertheless, a job might be required to generate the alert itself.



Lesson Summary

You should now be able to:� List the prerequisites for alert notification within SAP SNC� Create your own message profile


SNC100 Lesson: Process Demo & Exercise: Alert Notification

Lesson: Process Demo & Exercise: Alert Notification



� Use alert notification in SAP SNC

Business Example

Demo

Figure 88: Demo





Exercise 8: Alert Notification

Exercise ObjectivesAfter completing this exercise, you will be able to:� Use alert notification in SAP SNC

Business Example

Task 1: Maintain an Alert Notification ProfileMaintain an alert notification profile to inform supplier SNC100A-## when a newpurchase order (PO) is sent to SAP SNC or an existing PO is changed.

1. Log on to SAP SNC in the role of supplier SNC100-A-## (userIU-SUPA##).

2. Create a selection for the New PO and Changed PO alerts.

3. Create an alert notification profile to inform the supplier about new andchanged POs in SAP SNC.

4. Test your profile by sending a new PO to SAP SNC for supplierSNC100-A-##.

Hint: This task is performed in SAP ERP by the user SNC100-##representing the customer.

5. In case the e-Mail service of your training system has not been activated youcan check the result of your notification profile using transaction SOST inthe SAP SNC System.

Task 2: Create a New Message ProfileYou might feel that your alert notification e-mail does not contain a lot ofinformation, so you would like to enrich the content. Create a new message profileand change your alert notification profile to use the new message profile. Performthis task in the role of the customer.

Hint: This task is performed with user SNC100-##

in the SAP SNC system.

1. Make sure that you are logged on to the SAP SNC system as a customer.

2. Use the Create / Change Message Profile transaction to create your ownmessage profile.




3. Change your alert notification profile to use the new message profile.

Hint: This step is again being performed in the role of the supplierwith user IU-SUPA##.

Task 3: Alert Notification AdministrationInstead of creating an alert notification profile from scratch, an administrator canalso create / copy alert notification profiles.

Log on in the role of the customer and copy the alert notification profile fromSupplier A to Supplier B.

1. Log on as customer and call the Alert Notification Administration screen.

2. Select the profile that you created before and choose Copy Selection &Profile.

3. Check the result.



Solution 8: Alert NotificationTask 1: Maintain an Alert Notification ProfileMaintain an alert notification profile to inform supplier SNC100A-## when a newpurchase order (PO) is sent to SAP SNC or an existing PO is changed.

1. Log on to SAP SNC in the role of supplier SNC100-A-## (userIU-SUPA##).

a) Log on to the SNC system with the supplier user IU-SUPA## andpassword welcome.

The Alert Monitor should open automatically. If not, choose Exceptions→ Alert Monitor.

2. Create a selection for the New PO and Changed PO alerts.

a) In the Selection area of the Alert Monitor, scroll down so that you cansee the Alert Type field. Use the input help to select alert type 7051 forNew Purchase Order Item and 7052 for Changed Purchase Order Item.

b) To save the selection use the button to the left of the Go button. Thisbutton most likely is labeled Reset. Next to it click on the small buttonwith the triangle. Select Save as ... from the dropdown menu.

c) In the dialog box, specify a name, for example, New/ChangedPO Alerts Supplier A-##. In the dropdown area, choosePartner-Specific.

If you like you, can make the selection the default selection for theAlert Monitor.

d) Choose OK to save your selection.




3. Create an alert notification profile to inform the supplier about new andchanged POs in SAP SNC.

a) Make sure that the selection you just created is shown in the Showdropdown list.

b) Choose Set Notification to create your alert notification profile.

c) In the Alert Notification Profile screen, enter the following values:

Recipient Type: Channel

E-Mail Address: enter your e-Mail address

Sending User: IU-SUPA##

Message Profile: SAP_COLL

Minimum Priority: Information

Immediate Notification: checked

Profile is Active: checked

d) Choose Save to save your alert notification profile.

4. Test your profile by sending a new PO to SAP SNC for supplierSNC100-A-##.

Hint: This task is performed in SAP ERP by the user SNC100-##representing the customer.

a) Log on to the ERP system and create a new purchase order.

b) After you have saved your PO, check your e-mail account. You shouldhave received an e-mail informing you about the new PO.

5. In case the e-Mail service of your training system has not been activated youcan check the result of your notification profile using transaction SOST inthe SAP SNC System.

a) Logon to SAP SNC and call transaction SOST.




Task 2: Create a New Message ProfileYou might feel that your alert notification e-mail does not contain a lot ofinformation, so you would like to enrich the content. Create a new message profileand change your alert notification profile to use the new message profile. Performthis task in the role of the customer.

Hint: This task is performed with user SNC100-##

in the SAP SNC system.

1. Make sure that you are logged on to the SAP SNC system as a customer.

a) Ensure that you are logged on with user SNC100-##.

2. Use the Create / Change Message Profile transaction to create your ownmessage profile.

a) From the SAP Easy Access menu, choose SCM Basis → AlertNotification Engine→ Settings.

b) In the Create / Change Message Profile transaction, choose New entriesto create a new message profile.

c) Enter the following data:

Message Profile: SNC100-##

Application: ALEN

Message Mode: Collective Message

d) In the dialog structure on the left ,double-click on Message Parameter.

e) Choose New entries and enter the following data:


Sequence Number: 10

Parameter: LOCID

Choose Next entry or press F8.


Sequence Number: 20

Parameter: MATID



Sequence Number: 30




Parameter: ODMORDNO



Sequence Number: 40

Parameter: ITMNO



Sequence Number: 50

Parameter: POITMQUAN

Choose Next entry or or press F8.


Sequence Number: 60

Parameter: UNIT

f) Choose Save to save your new profile.

You will be asked for a Customizing request. Choose Own Requestsor press F7 to select your customizing request. Double-click on thecustomizing task.

Back in the Prompt for Customizing request dialog box, chooseContinue or Enter to continue.

Caution: After saving your new profile, make sure that youleave the Customizing transaction, so as not to block othercourse participants.




3. Change your alert notification profile to use the new message profile.

Hint: This step is again being performed in the role of the supplierwith user IU-SUPA##.

a) Log on with the supplier user, IU-SUPA##, again.

Log on to the Web UI.

b) In the Alert Monitor of the SAP SNC Web UI, choose your selection,NEW / CHANGED PO SNC100-##, from the dropdown menu.

c) Choose Set Notification.

d) In the alert notification profile, change the message profile fromSAP_COLL to SNC100-##.

Save your changes to the profile by choosing Save.

e) Check your changes by creating a new purchase order in the ERPsystem and checking your e-mail account.

Task 3: Alert Notification AdministrationInstead of creating an alert notification profile from scratch, an administrator canalso create / copy alert notification profiles.

Log on in the role of the customer and copy the alert notification profile fromSupplier A to Supplier B.

1. Log on as customer and call the Alert Notification Administration screen.

a) Log on to SAP SNC with the user SNC100-## and call transaction/N/SCA/ICH_C.

b) Choose Exceptions→ Alert Notification Administration.

2. Select the profile that you created before and choose Copy Selection &Profile.

a) Select your profile, NEW / CHANGED PO SNC100-##, and chooseCopy Selection and Profile.

b) In the Required Fields for Copy Selection and Profile dialog box,enter New / Changed PO SNC100-## as Selection Name andIU-SUPB-## as User and take over the other values.

Choose Ok.

c) Change the sending user from IU-SUPA## to IU-SUPB##.




3. Check the result.

a) Log on to SAP SNC with user IU-SUPB## and check the selectionand the notification profile.



Lesson Summary

You should now be able to:� Use alert notification in SAP SNC



Lesson: Creating own SNC alerts

Lesson OverviewIn this lesson, you will learn how to create your own SAP SNC alerts.


� Create your own SAP SNC alert

Business Example

Customizing for SNC AlertsYou can access Customizing for SNC alerts with transaction code/N/SCMB/ALENCFG.

1. First, define which parameters belong to your alert. These could be forexample, Purchase Order Number, Product, Location, Date, or Quantity.

2. Group these parameters into a new alert structure.3. Define a new alert object type that uses your newly created alert structure.4. Create the new alert type with reference to your newly created alert object

type.

The priority and the name of the alert are defined in the alert type.

Alert Category AssignmentAlerts in SAP SNC are grouped into different aalert categories, such as PurchaseOrder Alerts, Inventory alerts, and so on.

You need to assign your newly created alert to one of the existing categories intransaction /N/SCF/ALERTCATCFG.

You can also specify the name of your new alert under Alert type description.

Generation of the Database Tables for Your New AlertDatabase tables are required to store your new alert in the database.These database tables will be generated automatically with report/SCMB/ALEN_DB_GENERATE. Ask your Basis administrator to executethis report. The report need to be run in all systems (development, test, andproduction).


SNC100 Lesson: Creating own SNC alerts

Alert LogicAfter defining a new alert in customizing and generating the correspondingdatabase tables, you still require a logic for generating the alert. This means yourequire some ABAP code to fill the database tables upon an alert situation.

Note: As this is very project-specific, this topic cannot be covered inthis training. If you require support in creating the coding for a newSNC alert, you can engage SAP Consulting. You referent will tell youa contact for this service.



Lesson Summary

You should now be able to:� Create your own SAP SNC alert


SNC100 Unit Summary

Unit SummaryYou should now be able to:� Explain the alert notification function� Discuss the functionality of Alert Notification Administration screen� List the prerequisites for alert notification within SAP SNC� Create your own message profile� Use alert notification in SAP SNC� Create your own SAP SNC alert


Unit Summary SNC100


Unit 10Authorization

Unit OverviewIn this unit, you will get an idea about authorization within SAP SNC.


� Name the relevant authorization objects for SAP SNC� Explain the dependency between SAP SNC authorization objects and the

appearance of the SAP SNC Web UI� Explain how the authorization objects in SAP SNC can be used to control the

appearance of the SAP SNC Web UI

Unit ContentsLesson: Authorization Within SAP SNC ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372Lesson: Process Demo: Authorization Objects in SAP SNC .... . . . . . . . . .375


Unit 10: Authorization SNC100

Lesson: Authorization Within SAP SNC

Lesson OverviewThis lesson will introduce you to the most important SAP SNC authorizationobjects and show you the dependency between the SAP SNC authorization objectsand the SAP SNC Web UI.


� Name the relevant authorization objects for SAP SNC� Explain the dependency between SAP SNC authorization objects and the


Business Example

Authorization ObjectsSAP Supply Network Collaboration (SAP SNC) has its own authorization objects,and also euses existing objects � mainly in the area of master data.

SAP SNC reuses master data objects from SAP Advanced Planning &Optimization (SAP APO), such as plant and product. Therefore the correspondingauthorization objects are checked within SAP SNC as well.

In addition to the existing SAP SCM / SAP APO authorization objects, SAP SNChas its own authorization objects:

C_ICH_USERThis object mainly controls the visibility of certain SNC screens and thevisibility of buttons on the SAP SNC Web UI.This object has five authorization fields; theSMI activity and Screen Name(/SCA/SCRID) fields are the most important.The Screen Name field refers to the different screens in SAP SNC, includingASN Overview, PO Details, ASN History, and SMI Overview.You can grant access to every screen in SAP SNC by using the authorizationobject C_ICH_USER and the SMI activity field.The SMI activity (/SCA/ACTVT) authorization field is also used to show/hidebuttons on the SAP SNC screens. The idea behind this is that if a user doesnot see certain buttons, he or she can not perform certain actions.


SNC100 Lesson: Authorization Within SAP SNC

C_ATIDWith this authorization object you grant visibility to the different alert types.For example, you want a user to see purchase order alerts, but you do notwant him or her to see release alerts.The authorization object C_ATID has only one authorization field,/SCMB/ATID. You maintain the number of the alert types you want to bevisible to the user.

/SCF/PLNRIn SNC supplier collaboration, this authorization object correlates with thePurchasing group field from the product master on the SAP SNC Web UI.As the purchasing group in SAP SNC is linked to the product master, youcan restrict the visibility of products for certain user with this object.

Besides these three SNC authorization objects, some standard SAP SCM / SAPAPO authorization objects are checked at runtime, including C_APO_LOC andC_APO_PROD.



Lesson Summary

You should now be able to:� Name the relevant authorization objects for SAP SNC� Explain the dependency between SAP SNC authorization objects and the



SNC100 Lesson: Process Demo: Authorization Objects in SAP SNC

Lesson: Process Demo: Authorization Objects in SAPSNC



� Explain how the authorization objects in SAP SNC can be used to control theappearance of the SAP SNC Web UI

Business Example

Figure 89: Demo



Lesson Summary

You should now be able to:� Explain how the authorization objects in SAP SNC can be used to control the



SNC100 Unit Summary

Unit SummaryYou should now be able to:� Name the relevant authorization objects for SAP SNC� Explain the dependency between SAP SNC authorization objects and the

appearance of the SAP SNC Web UI� Explain how the authorization objects in SAP SNC can be used to control the



Course Summary SNC100

Course SummaryYou should now be able to:

� Explain the different processes for supplier collaboration in SAP SNC� Describe the system landscape used by SAP SNC� Discuss process details for:- Purchase order - Scheduling agreement release -

Advance shipping notification- Invoice collaboration - Supplier-managedinventory

� Explain the process flow for the following SAP SNC processes:- Dynamicreplenishment- Delivery Control Monitor- Kanban - Work order- SupplyNetwork Inventory and subcontracting purchase order

� Describe the functionality of exception management and alert notification� Discuss authorization within SAP SNC


GlossaryBAPI

A standardized programming interface that facilitates external access tobusiness processes and data in the SAP System.

InvoiceAn invoice is created by the supplier to charge a customer for goods that havebeen provided by the supplier to that customer. An invoice can referencean existing purchase order, replenishment order or advanced shippingnotification (this allows you to invoice a scheduling agreement).

Packaging specificationRule that specifies how products are to be packed in handling units (HUs),for example, for shipment to the customer.A packaging specification (PS)describes which product quantities should be packed, and which packagingmaterials and auxiliary packaging materials should be used for this purpose.You can use a PS to model packing on single or multiple levels.

Packaging specification levelPart of a packaging specification (PS) that describes a packaging level.APS level contains, for example, data for the quantities that the SAP SupplyNetwork Collaboration (SAP SNC) is to pack in this packaging level inautomatic packing.

Packaging specification level elementPart of a packaging specification (PS) that specifies a packaging material thatyou require for a PS level. In addition to the product number, the PS levelelement for the packaging material also contains the necessary packagingmaterial quantity.

Purchase orderA purchase order is a procurement order that a customer uses to request that asupplier delivers certain quantities of products at certain dates/times. In SAPSupply Network Collaboration (SAP SNC) purchase order collaboration, thecustomer backend system sends the purchase order to SAP SNC with anXML message.

Purchase order statusClassification of the status of a purchase order or a purchase order item.

ReleaseA scheduling agreement is an outline agreement between a customer and asupplier. It specifies the total quantity of the products that a supplier is todeliver to the customer in a specific time period. The customer performsexact planning at regular intervals and determines what exact demandquantities are to be released from the scheduling agreement on certain dates.


Glossary SNC100

To inform the supplier about the current demands, the customer sends ascheduling agreement release for one or several products to SAP SNC. Foreach item, the scheduling agreement release contains schedule lines. Eachschedule line contains a demand for a product with a quantity and a date/time.

Replenishment orderA replenishment order is an order that a supplier creates in SAP SNC toinform about certain quantities of products that he or she intends to deliver toa customer on a certain date and time In SAP SNC, a replenishment order isan order of order document type VGOR.

RevaluationIf the price of a product changes and is retroactively valid, the customercan create a revaluation. This determines the difference in value for itemsthat have already been invoiced. A revaluation can only be created for apurchasing order or advanced shipping notification that has the evaluatedreceipt settlement (ERS) indicator set.

Self-Billing InvoiceA self-billing invoice is created by a customer. It contains the invoice detailsfor goods provided by the supplier to the customer. A supplier does notcreate an invoice for goods that are invoiced using a self-billing invoice.Aself-billing invoice references an existing purchase order, replenishment orderor advanced shipping notification (this allows you to invoice a schedulingagreement).

Subsequent Debit/CreditAn additional document that the supplier creates for a transaction that hasalready been invoiced. The subsequent debit or credit charges an additionalvalue for, or reduces the original value of a quantity of goods that havealready been invoiced.A subsequent debit or credit can reference an existingpurchase order, replenishment order or advanced shipping notification.


FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place in thecourse evaluation.
