Non-Standard Scenarios for SAP Supply Network · PDF fileNon-Standard Scenarios for SAP® Supply Network Collaboration ... 2.2 SMI with Demand-Based Replenishment ... 3.1.3 SAP APO

Christian Butzlaff, Thomas Heinzel, Frank Thome

Non-Standard Scenarios for SAP® Supply Network Collaboration

Bonn � Boston

195 Book 1.indb 3 12/1/08 9:36:09 AM

5

Contents

Acknowledgments ................................................................................. 9

1 Introduction .............................................................................. 11

1.1 The Need for Supply Network Collaboration ............................... 121.2 SAP SNC Business Scenarios and Processes ................................. 141.3 SAP SNC Architectural Overview ................................................. 19

1.3.1 SAP SNC Software Components and System Landscape .... 191.3.2 SAP SNC Business Partner Roles ....................................... 211.3.3 Multiple Business Partner Networks ................................. 221.3.4 SAP SNC Integration ......................................................... 231.3.5 Master Data in SAP SNC ................................................... 241.3.6 Components of SAP SNC .................................................. 261.3.7 UI Concepts ..................................................................... 37

2 Supplier Collaboration Scenarios ............................................. 41

2.1 Multitier, and Multipartner Collaboration ................................... 412.1.1 Model 1: Two-Tier Linear Supply Chain ............................. 422.1.2 Model 2: Two-Tier Supply Chain with Two Suppliers ......... 452.1.3 Model 3: Two-Tier Supply Chain with Two Contract

Manufacturers and Two Suppliers ..................................... 472.1.4 Model 4: Enhanced Two-Tier Supply Chain with Two

Contract Manufacturers and Two Suppliers ....................... 492.2 SMI with Demand-Based Replenishment .................................... 52

3 Outsourcing Scenarios .............................................................. 57

3.1 PO Subcontracting Collaboration with SAP APO Supply Network Planning (SNP) Integration .......................................................... 573.1.1 Process Description .......................................................... 583.1.2 Master Data ..................................................................... 613.1.3 SAP APO Planning ........................................................... 633.1.4 SAP SNC Scenario and Process .......................................... 65

3.2 Subcontracting Component Transfer Confirmation ...................... 66

195 Book 1.indb 5 12/1/08 9:36:09 AM

6

Contents

3.2.1 Technical Realization ........................................................ 683.3 Work Order Collaboration with SNI ............................................ 71

4 Customer Collaboration Scenarios ........................................... 81

4.1 Enhanced Consensus Finding in Collaborative Sales Forecasting ... 814.1.1 Maintaining the Collaborative Sales Forecast Profile ......... 834.1.2 Creating and Maintaining a Permissible Class .................... 834.1.3 Maintaining the Consensus Determination Rule ............... 854.1.4 Activating the Consensus Determination Rule for

Collaborative Sales Forecasting ......................................... 874.2 Sales Forecast Collaboration with Store-Level Data ..................... 88

4.2.1 Receiving and Processing Store-Level Data ...................... 884.2.2 Accessing Store-Level Data from SAP SNC Collaborative

Sales Forecasting .............................................................. 894.2.3 Using Store-Level Data to Create a Consensus Forecast ..... 93

4.3 Order Forecast Collaboration ...................................................... 954.3.1 Defining the Planning Book with TSDM Key Figures ......... 974.3.2 Enhancing TSDM Characteristics for Data Storage ............. 984.3.3 Storing the SAP APO Time Series Data in the SAP SNC

Order Forecast Monitor .................................................... 994.4 Pallet Determination ................................................................... 101

5 SAP SNC Selection and Authorization Concepts ..................... 109

5.1 Screens in SAP SNC ..................................................................... 1095.2 Introducing the SAP SNC Selection Component .......................... 111

5.2.1 Example Web Dynpro Component .................................... 1125.2.2 Example Web Dynpro Window ......................................... 1125.2.3 Example Web Dynpro View .............................................. 1145.2.4 Embedding the Web Dynpro View in the Web Dynpro

Window ........................................................................... 1165.2.5 Component Controller Message Handling ......................... 117

5.3 Model Class and Selection Object ............................................... 1185.3.1 Initialize Selection Object ................................................. 1185.3.2 Selection Parameters for UI Selection Component ............ 1205.3.3 Web Dynpro Test Application ........................................... 1245.3.4 Selection Parameters ........................................................ 125

195 Book 1.indb 6 12/1/08 9:36:09 AM

7

Contents

5.4 Result List ................................................................................... 1275.4.1 Selection Component Events ............................................ 133

5.5 Authorization Concepts in SAP SNC ............................................ 1355.5.1 Screen Action Authorization Object .................................. 1355.5.2 Business–Partner–Based Authorization .............................. 1385.5.3 Master Data Authorization Checks .................................... 139

5.6 Selection Modes and Selection Objects ....................................... 1395.6.1 Selection Mode Configuration .......................................... 1415.6.2 Selection Object Interfaces ............................................... 143

5.7 Application Logic ........................................................................ 1435.7.1 Selection Object Usage Example ....................................... 1445.7.2 Time Series Data Access and Conversion ........................... 149

5.8 Navigation Menu ........................................................................ 1575.9 Selection Object Extensions ........................................................ 158

5.9.1 Customer Selection Object ............................................... 1585.9.2 BAdI Extension for Selection ............................................. 159

5.10 Alert Selection ............................................................................ 160

6 Business Process Enhancements .............................................. 163

6.1 Process Enhancement Description ............................................... 1636.2 Enhancements of Mapping and Message Interface ...................... 164

6.2.1 Enhancing the Interface Object ......................................... 1666.2.2 Enhancing the Mapping Object ........................................ 1676.2.3 Accessing the Enhancement Information during Inbound

Processing ........................................................................ 1696.3 Enhancements of Business Object Layer for Order Documents ... 171

6.3.1 Data Management ............................................................ 1726.3.2 Validation ......................................................................... 178

6.4 Enhancements of PO Details Web Screen .................................... 1796.5 Enhancements of Time Series Data Storage ................................. 180

195 Book 1.indb 7 12/1/08 9:36:09 AM

8

Contents

A Conclusion ................................................................................ 183

B SAP SNC Resources .................................................................. 185

C Appendix ................................................................................... 187

C.1 Example Proact Report ............................................................... 187C.2 Example Proact Mapping ............................................................ 201C.3 Example Method for Consensus Forecast .................................... 203

The Authors ........................................................................................... 209

Index .................................................................................................... 211

195 Book 1.indb 8 12/1/08 9:36:10 AM

41

Supplier Collaboration Scenarios2

SAP SNC provides a variety of supplier collaboration scenarios and processes, many of which are well established in industries such as automotive or high tech. Most of today’s supplier collaboration implementations focus on a single SAP SNC instance installed at the customer’s location. They provide data visibility and collaboration with the first tier of suppliers only. In this chapter we show how SAP SNC can go beyond these implementations and support the whole supply network.

In the first example we expand the visibility concept to second-tier suppliers. We use the Supply Network Inventory (SNI) scenario and provide inventory vis-ibility across an entire supply chain with multiple contract manufacturers and suppliers.

The second example goes one step further and introduces multiple SAP SNC instances into the network.

The third example enhances the traditional Supplier Managed Inventory (SMI) pro-cess, using a minimum-maximum type of replenishment, by introducing a purely demand-driven replenishment algorithm to the process. Although not applicable in all industries, it broadens the scope and applicability of the SMI process.

Multitier, and Multipartner Collaboration2.1

Most of the standard SAP SNC scenarios and processes, such as Supplier Managed Inventory, Purchase Order Collaboration, or Responsive Replenishment contain single-tier collaboration. This is the collaboration between a single customer and his direct suppliers, or a single supplier and all of his customers. The SNI scenario allows for multitier inventory collaboration, sharing of inventory levels, demands, future receipts, and projected stock information across the entire multitier supply chain. This also includes a visibility concept allowing all partners to display the relevant information, thereby securing competitive information.

195 Book 1.indb 41 12/1/08 9:36:15 AM

42


In this chapter we describe multiple two-tier collaboration scenarios. We develop them step by step from a simple linear model to a more complex network of multiple contract manufacturers with multiple suppliers and different relation-ships. The first model contains a brand owner, a contract manufacturer, and a single second-tier supplier. The last model contains two contract manufacturers, two suppliers, and a supplier-customer relationship between the two contract manufacturers.

In all models we refer to the manufacturing of a computer by contract manufac-turers. The memory component is delivered by second-tier suppliers. In the last model we add a display component, which is manufactured by one of the contract manufacturers and is part of the computer. The contract manufacturer delivers the display to a second contract manufacturer.

We do not include any subcontracting components provided by the brand owner. Those could, however, easily be added to the models.

In all of the models we assume that a single SAP SNC installation is available, pro-viding access to all business partners: the brand owner, the contract manufactur-ers, and the suppliers. We describe several visibility models allowing each business partner to see the inventory at his own locations and selected inventory at the other business partner locations.

Model 1: Two-Tier Linear Supply Chain2.1.1

The first model is a simple, linear supply chain: The contract manufacturer builds the computer for the brand owner, and a second-tier supplier provides memory components to the contract manufacturer.

The brand owner can see the computer inventory at his own location and at the contract manufacturer’s location. He can also monitor the memory com-ponent inventory levels at the contract manufacturer’s location. He cannot, however, see the memory inventory at the second-tier supplier’s location. The contract manufacturer can see the computer and the memory inventory at his location only, whereas the supplier can see the memory inventory at his and the contract manufacturer’s locations. For this relationship, an additional SMI scenario could be set up to allow the second-tier supplier to actively manage the memory inventory at the contract manufacturer’s location. Figures 2.1 and 2.2 provide an overview of the product flow and the visibility model used in this example.

195 Book 1.indb 42 12/1/08 9:36:15 AM

43

Multitier, and Multipartner Collaboration 2.1

BO MemoryComputer CM1 SP 1

Material Flow Between Supplier 1 (SP1), Contract Manufacturer 1 (CM1), and Brand Figure2.1Owner (BO)

BO CM1 SP 1

MemoryComputer/Memory

Data Visibility Model for Brand Owner, Contract Manufacturer, and SupplierFigure2.2

To set up this scenario, business partners, locations, and products need to be cre-ated. Table 2.1 defines the basic master data required.

Object Name

Business Partner Brand Owner BO

Brand Owner Location BO_LOC

Finished Product COMPUTER

Business Partner Contract Manufacturer CM1

Contract manufacturer Location CM1_LOC

Supplier 1 SP1

Supplier location SP1_LOC

Product MEMORY

Master Data Required for First ScenarioTable2.1

The SNI visibility is driven by the profiles defined in the SAP SNC settings (Transac-tion /SCF/VISCTRLPROFASSN). For the first scenario, the profiles defined in Table 2.2 need to be created.

Profile Name Assigned to Parameter Name Parameter Value

BO11 Brand Owner BO Location CM1_LOC

Product COMPUTER

Product MEMORY

Profiles Supporting the First ScenarioTable2.2

195 Book 1.indb 43 12/1/08 9:36:15 AM

44


Profi le Name Assigned to Parameter Name Parameter Value

SP11 Supplier 1 SP1 Location CM1_LOC

Product MEMORY

Supplier SP1

Table2.2 Profi les Supporting the First Scenario (Cont.)

The profi les are assigned to the three business partners involved. The brand owner is assigned profi le BO11, and the fl ag Usr/Prtnr’s Own Data Visible is set. Because we do not provide the contract manufacturer with visibility into any other busi-ness partners’ inventory, no profi le is required. Only the fl ag Usr/Prtnr’s Own Data Visible is set. The supplier is assigned profi le SP11, and the fl ag for his own data is set.

The example in Figure 2.3 shows the brand owner ’s user interface. We allowed the brand owner to see his own inventory, as well as the computer and memory inventory at the contract manufacturer’s location.

SNIFigure2.3 Visibility for the Brand Owner into the Contract Manufacturer’s Inventory

195 Book 1.indb 44 12/1/08 9:36:16 AM

45

Multitier, and Multipartner Collaboration 2.1

Model 2: Two-Tier Supply Chain with Two Suppliers2.1.2

For the second example, an additional memory supplier, SP2, is added. Similar to the first supplier, the second supplier has visibility into the memory inventory located at the contract manufacturer’s location. The first supplier can only see the memory inventory he provided to the contract manufacturer (he has no visibility into the memory inventory provided by the second supplier) and vice versa. The separating factor is the supplier ID, which has to be defined in the visibility profiles.

The master data model defined in the first example is enhanced by the data shown in Table 2.3.

Object Name

Business Partner Supplier 2 SP2

Supplier Location SP2_LOC

Additional Master Data Required for the Second SupplierTable2.3

Figures 2.4 and 2.5 show the data flow and visibility concept for this scenario. Both suppliers can see the memory inventory status at the contract manufacturer side, but the contract manufacturer can only see the memory inventory at his loca-tion. The brand owner can see the computer and memory inventory at his own location and at the contract manufacturer’s location

BO

Mem

ory

Mem

ory

Computer CM1

SP 1

SP 2

Supplier 1 (SP1) and Supplier 2 (SP2) Deliver Memory Components to Contract Figure2.4Manufacturer 1 (CM1)

195 Book 1.indb 45 12/1/08 9:36:16 AM

211

A

Advanced List Viewer (ALV), 112, 125, 140, 152, 153Advanced Shipment Notification (ASN), 16, 23, 26, 27, 50, 54

ASN, 30, 31

Alertengine, 29, 33monitor, 158, 182notification, 158, 182ALV component, 112, 125, 126

ApplicationLogic, 141, 168model class, 141, 168model, 141

Authorization profile, 133, 159

B

BAdI, 31, 59, 60, 61/sapapo/curto_snp, 60, 70/SAPAPO/SDP_TSDM_BADI, 96, 121/SCA/BIF_I_REPLORD, 95/SCF/BAdI_SELECTION, 157, 181/SCF/NAV_ABS, 155/SCMB/IF_EX_BOL_VALFRMWRK, 202

BAdI Extension for Selection, 157

BAPI, 26, 63, 75, 199, 200BAPI_GOODSMVT_CREATE, 66, 80BAPI_PBSRVAPS_CHANGEKEYFIGVAL2, 63

Bullwhip, 7, 12Business Interface Layer (BIF), 21, 26Business object layer (BOL), 22, 26, 161, 169, 196Business Scenario, 12, 13

C

Collaborative Sales Forecasting, 99Consensus Baseline Forecast (CSFC), 85, 106Contract Manufacturing Procurement, 10, 14Core interface (CIF), 21, 24, 26, 59, 68

D

Data matrix, 30, 34DDSN, 10, 181Delivery Control Monitor (DCM), 15

DCM, 147Delivery Control Monitor, 11, 15, 172

Demand driven supply network (DDSN), 2, 4, 6, 9, 10, 207Dynamic Replenishment, 11, 15

E

Enterprise Services Repository, 162, 163, 186

F

Firm receipts proposal, 29, 33

I

IMG activityDefine Replenishment Service Profile, 58Maintain Consensus Quantity Profiles, 84, 104Maintain Consensus Rules, 83, 103Maintain Permissible Classes, 83, 102Rounding Values, 99, 125Visibility, 167

Index

195 Book 1.indb 211 12/1/08 9:37:00 AM

212

Index

Invoice, 10, 15, 23, 28self-billing, 11, 15Invoice Processing, 15

K

Kanban, 13, 23, 28

L

Lean Inventory Management Engine (LIME), 29, 33

M

Master data, 146

O

Order Document, 138, 164Order Document Management (ODM), 28, 32, 161, 170, 184Order Forecast, 29, 33Outsource Manufacturing, 55, 63

P

Pallet Type, 79, 98, 99, 100, 102, 103, 105, 125, 127, 128Partner Dependent Network Filter (PDNF), 138, 139, 164, 165Planned Replenishment Order, 23, 28Planning Service Manager, 30, 34Point-of-Sale (POS), 79, 86, 97, 108ProductActivityNotification, 57, 63, 66, 74, 75, 86, 108, 185, 187, 193, 197, 199

service, 25, 30ProductForecastNotification, 80, 109ProductForecastRevisionNotification, 80Promotion, 11, 24, 29

build up, 4

ID, 25, 29planning, 29, 33reactive, 2, 6, 9

Purchase order, 23, 27Collaboration, 39Processing, 9, 13, 34

R

Release, 8, 13, 27Releases for Scheduling Agreements, 23Replenishment

demand driven, 39, 51, 54, 57, 61min/max, 11, 13, 15, 50, 51, 54, 55, 56, 61planning, 29Replenishment Order, 23, 33Replenishment planning, 12, 15, 33, 34responsive, 39safety stock, 52, 55, 57, 63service profile, 52, 58

ReplenishmentOrderNotification, 161, 177, 184, 186Responsive Demand Planning, 12, 16Responsive replenishment, 10, 12, 14, 16, 24, 34, 108, 147, 172Return Instruction, 24, 28

S

Safety Stock, 52Sales Forecast Collaboration (SFC), 85, 106SAP APO, 93, 95SAP Enterprise Services Enhancement Guide, 162, 186SAPGUI, 154, 178SAP NetWeaver Process Integration (PI), 93, 116, 161, 184SAP NetWeaver Exchange Infrastructure (XI), 161, 184SAP Supply Chain Management (SCM)

server, 7, 12, 14SAP Supply Network Collaboration (SNC), 9, 107

195 Book 1.indb 212 12/1/08 9:37:00 AM

213

Index

application view, 108, 136,Collaborative Sales Forecasting, 79, 81, 85extensions, 116, 144IMG menu, 140Order Forecast Monitor, 93, 94, 95, 117, 119screen, 107, 109, 123, 127, 135, 137, 138, 150, 154, 161selection component, 109, 157selection mode, 163selection object, 137, 163, 180selection range, 171stand alone, 7, 12, 14, 18style screen, 136style selection, 109UI applications, 109, 137UI framework, 107, 112, 116, 123, 134, 135, 140, 144, 150, 159Web Dynpro, 107Web UI, 99, 109, 133, 135, 137, 154, 158, 179

Selectioncomponent, 109, 112, 131mode, 120, 137object, 137Object Extensions, 156range, 109, 146

Service Partsexecution, 13, 16planning, 12, 16

Service profile, 52SMI, 27, 29, 30, 31, 34, 40, 48Statistical forecasting, 29, 31, 33Supplier confirmations, 23, 27Supplier Kanban, 9, 13Supplier Managed Inventory (SMI), 8, 11, 13, 15, 23, 26, 30, 34, 35, 39, 50, 52, 54, 147, 172Supply Network Inventory (SNI), 9, 14, 34, 39, 55, 57, 63, 64, 69, 74, 75, 76, 84, 167, 172

details screen, 49, 52profiles, 31, 49

scenario, 138, 141, 147visibility profile, 39, 41, 42, 43, 44, 46, 48, 49, 52

T

Time Series Data Management (TSDM), 27, 28, 31, 88, 111, 142, 147, 168, 173Transport Load Builder (TLB), 23, 29, 33, 88, 125, 196

Shipments, 33

U

UI Framework, 31, 35

V

Validation Framework, 26, 30

W

Web Dynpro, 135application, 122, 149, 154component, 110, 125, 138, 142, 168screen, 107, 109, 137, 141, 167selection component, 118, 145UI component, 125, 152Window, 110

Work order, 23, 24Collaboration, 9, 14, 69, 83

X

XSLT, 161, 165, 185

195 Book 1.indb 213 12/1/08 9:37:00 AM

Stefan Glatzmaier, Michael Sokollek

Project Portfolio Management withSAP RPM and cProjectsSAP PRESS Essentials 49

This essentials guide introduces and teaches users how to integrate anduse project portfolio management with SAP to support their business processes. The book focuses on cProjects and SAP RPM, as well as the integration with SAP Project System. With real-life examples, this book uses examples to illustrate specific solution options and projects. The main chapters are based on the actual business processes in an enterpriseand contain industry-specific recommendations. The book is based on the latest releases, and is a must-have addition to any SAP library.

approx. 356 pp., 68,– Euro / US$ 85

ISBN 978-1-59229-224-0

>> www.sap-press.de/1838

Teaches how to integrate cProjects and RPMto provide a high-level visibility over the entireproject portfolio

Provides functionality and integration details for cProjects and RPM with SAP Project System

Includes real-world customer examples throughout

Up-to-date for cProjects 4.5 and RPM 4.5

www.sap-press.com

195 Book 1.indb 214 12/1/08 9:37:01 AM

Stefan Glatzmaier, Michael Sokollek

Project Portfolio Management withSAP RPM and cProjectsSAP PRESS Essentials 49

This essentials guide introduces and teaches users how to integrate anduse project portfolio management with SAP to support their business processes. The book focuses on cProjects and SAP RPM, as well as the integration with SAP Project System. With real-life examples, this book uses examples to illustrate specific solution options and projects. The main chapters are based on the actual business processes in an enterpriseand contain industry-specific recommendations. The book is based on the latest releases, and is a must-have addition to any SAP library.


ISBN 978-1-59229-224-0


Teaches how to integrate cProjects and RPMto provide a high-level visibility over the entireproject portfolio

Provides functionality and integration details for cProjects and RPM with SAP Project System

Includes real-world customer examples throughout

Up-to-date for cProjects 4.5 and RPM 4.5

www.sap-press.com

195 Book 1.indb 215 12/1/08 9:37:01 AM

Eric Stajda

Effective Document Managementwith SAP DMS

This essentials guide is a complete and practical resource toSAP Document Management System. It teaches project managers,functional users, and consultants everything they need to know tounderstand, configure, and use SAP DMS, and provides step-by-stepinstructions and real-world scenarios. This is a must-have book foranyone interested in learning about and creating an efficient, effectivedocument management system using SAP.


ISBN 978-1-59229-240-0


Introduces readers to the ins-and-outsof SAP DMS

Addresses all uses and details of Document Management

Provides real-world examples and practical

Up-to-date for ERP 6.0

www.sap-press.com

195 Book 1.indb 216 12/1/08 9:37:01 AM