SCM Basis - help.sap.com

PUBLICDocument Version: 2.0 – 2019-10-09

SCM Basis

© 2

019

SAP

SE o

r an

SAP affi

liate

com

pany

. All

right

s re

serv

ed.

THE BEST RUN

Content

1 SCM Basis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 What's New in SAP SCM Basis 7.0, Enhancement Package 4. . . . . . . . . . . . . . . . . . . . . . . . . . . .82.1 Support Package Stack 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

ILM-Based Deletion of SCM Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82.2 Support Package Stack 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

ILM-Based Deletion of SCM Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Business Functions (SAP Enhancement Package 4 for SAP SCM Basis 7.0). . . . . . . . . . . . . . . .123.1 ILM-Based Deletion of Location Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.2 Enhanced Services for Transportation Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.3 Foundation of External Transportation Management System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.4 EH&S Services in SCM: Dangerous Goods continuous improvement. . . . . . . . . . . . . . . . . . . . . . . . 18

4 Integration via Core Interface (CIF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.1 SAP R/3 Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.2 Core Interface (CIF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

CIF Customizing in the ERP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24CIF Customizing in the SCM System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Setting Up the System Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Troubleshooting Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

5 SCM Basis Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.1 Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Display, Create, and Change Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Delete Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80ILM-related Information for SCM Location (SCMB_LOC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Data Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Application Log of Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Geocoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

5.2 Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Maintaining Global Product Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Maintain Location-Dependent Product Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Mass Maintenance of Penalty Costs for Products/Location Products . . . . . . . . . . . . . . . . . . . . 131Assignment of Planning Version to Location Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Assignment of Supply Chain Model to Location Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

2 P U B L I CSCM Basis

Content

Delete Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Product Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Inheritance of Product Master Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

5.3 Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Hierarchy Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Maintain Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Schema Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Extended Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Maintenance of Time-Dependent Location Product Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . .145

5.4 Transportation Lane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Automatic Creation of Transportation Lanes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Create Transportation Lanes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Transportation Lane Maintenance Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151Defining Product Procurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Defining Means of Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Assign Products to Means of Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Assign External Transportation Service Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Create Multiple Lanes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Validity of Product Procurement and Means of Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163Deleting Product-Specific Transportation Lanes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Distance and Duration Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165Lane, Distance, and Duration Determination (LDDD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

5.5 Trailers and Compartments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Compartment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

5.6 Quota Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Maintain Quota Arrangement Header Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184Maintain Quota Arrangement Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185Validity of Quota Arrangements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

5.7 External Procurement Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Processing External Procurement Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Mass Maintenance of External Procurement Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

5.8 General Master Data Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195Mass Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Master Data Locking Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Master Data Enhancement with EEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Deleting Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206Change Logging for Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211User-Specific Display Profiles for Master Data Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . .212Partner-Dependent Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

5.9 Integration of SCM Basis Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214

SCM BasisContent P U B L I C 3

Integration of Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Integration of Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Integration of External Procurement Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Integration of Classes and Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Integration of Batches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

6 Alert Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2446.1 Alert Monitor Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2456.2 Alert Profile Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Overall Alert Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Application-Specific Alert Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Alert Profile Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Maintaining Selection Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

6.3 Global and User-Specific Alert Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2526.4 Alert Overview by Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2546.5 User-Specific Display Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2546.6 Assigning Favorites and Substitutes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2556.7 Sending Alert Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Automatic Sending from the Alert Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Sending Alert Notifications Using the Alert Notification Engine. . . . . . . . . . . . . . . . . . . . . . . . . 257

6.8 Determining Alerts in the Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259Configuring Overall Profiles for Alert Determination in the Background. . . . . . . . . . . . . . . . . . . 260Determining and Saving Alert Situations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261

6.9 Deleting Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

7 Alert Notification Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2637.1 Alert Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2647.2 Creating Alert Notification Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2667.3 Create Message Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

8 Process Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

9 Configurable Process Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2729.1 Process Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2739.2 Master Data Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2749.3 Definition of Time Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2759.4 Delegation Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

10 Order Document Management (ODM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27810.1 Configuring Order Document Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279

Order Document Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Order Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Order Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282


Content

Order Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28310.2 Check Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28410.3 Activating Order Document Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Generating Settings in Order Document Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28610.4 Defining Value Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

11 Time Series Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28911.1 Configuring Time Series Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29011.2 Activating Time Series Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29211.3 Activate Time Profile (Report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29311.4 Delete Time Profile (Report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29311.5 Activate Time Series Data Type (Report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29311.6 Delete Time Series Data Type (Report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29411.7 Activate Time Series Data Area (Report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29411.8 Delete Time Series Data Area (Report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29411.9 Copy Time Series Data Areas (Report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29411.10 Delete Time Series Data (Report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29511.11 Delete Time Series Change History (Report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29511.12 Reporting for Time Series Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295

12 Cross-System and Cross-Partner Document Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29612.1 Determining Process and Document Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29712.2 Distribution Across Several Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29812.3 Displaying Document Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29912.4 Data Transfer and Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

13 Planning Service Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30213.1 Preparation of the Planning Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30513.2 Storage Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30613.3 Define Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308

14 Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31014.1 Activating and Deactivating Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31114.2 Trigger Group Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

15 Transport Load Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31315.1 Master Data Setup for the Transport Load Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

Use of Transportation Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31915.2 TLB Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Weight/Volume Mix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32115.3 TLB Procedures for Remaining Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32215.4 Monitoring TLB and Deployment Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323

16 Package Building. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

SCM BasisContent P U B L I C 5

16.1 Defining Product-Specific Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328

Stacking Factor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

16.2 Defining Package Type Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .330

Determination of Package Type Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Determination of Normalized Load Consumption Quantities. . . . . . . . . . . . . . . . . . . . . . . . . . 332

16.3 Package Building Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Rule Profile for the Package Building Optimizer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .336

16.4 Detailed Mixed Package Building. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

16.5 Reference Products for Package Building. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

16.6 Test Report for Package Building. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

16.7 Consistency Check of Package Building Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

17 Route Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34417.1 Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Cross-Docking Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

17.2 Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

17.3 Carrier Profile for the Routing Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

17.4 General Transportation Cost Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

17.5 Hierarchical Relationships Between Means of Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

17.6 Static Route Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Route Determination as Part of Cross-Docking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

17.7 Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359

Results of Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

17.8 Calculation of Transportation Costs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

17.9 Simulation of Route Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364

17.10 Distribution of Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

18 EH&S Services in SCM Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37018.1 Phrase Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

18.2 Hazardous Substance Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

18.3 Dangerous Goods Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

19 Roles in SAP SCM Basis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37419.1 Transport Load Builder (TLB) Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374

19.2 Roles for Master Data and Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374

SCM Master Data Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

SCM Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

20 Archiving in SCM Basis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37620.1 Archiving in Execution (SCM-ECT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Archiving in LIME (SCM-ECT-LIME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376


Content

1 SCM Basis

SCM Basis offers you functions that you can use in various applications within SAP Supply Chain Management (SAP SCM).

If you want to use these functions, various system modifications might be necessary. Note the prerequisites in the documentation for the relevant application.

SCM Basis also contains enhanced functions for certain applications within SAP SCM, such as for forecasting. Since these functions are of a purely technical nature and no settings are required in SCM Basis, details are not provided in this documentation. You can view the function descriptions within the relevant application documentation.

SCM BasisSCM Basis P U B L I C 7

2 What's New in SAP SCM Basis 7.0, Enhancement Package 4

2.1 Support Package Stack 2

2.1.1 ILM-Based Deletion of SCM Location

Use

As of enhancement package 4, SP 02 for SCM Basis 7.0, the business function ILM-Based Deletion of Location Master Data ( SCM_SCMB_LOC_ILM_1) is available that simplifies the blocking and deletion of location master data by using SAP Information Lifecycle Management (ILM).

Effects on Existing Data

The function enables you to use the ILM component to support the deletion of location master data. Personal data collected in the master data can be blocked as soon as business activities for which this data is needed are completed and the residence time for this data has elapsed; after this time, only users who are assigned additional authorizations can access this data. After the retention period for data expires, personal data can be deleted completely so that it can no longer be retrieved. Residence and retention periods must be defined in the customer system.

Effects on Data Transfer

An end of purpose check determines whether data is still relevant for business activities based on the residence period defined for the data. The retention period of data consists of the following phases:

● Phase one: The relevant data is actively used.● Phase two: The relevant data is actively available in the system.● Phase three: The relevant data needs to be retained for other reasons.

For example, processing of data is no longer required for the primary business purpose but the data must still be available to comply with legal rules for retention. In phase three, the relevant data is blocked.

Blocking of data prevents the business users from displaying and using data that may include personal data and is no longer relevant for business activities.

Blocking of data can impact system behavior in the following ways:

● Display: The system does not display blocked data.● Change: It is not possible to change a business object that contains blocked data.


What's New in SAP SCM Basis 7.0, Enhancement Package 4

● Create: It is not possible to create a business object that contains blocked data.● Copy/Follow-Up: It is not possible to copy a business object or follow-up a business object that contains

blocked data.● Search: It is not possible to search for blocked data or to search for a business object using blocked data in

the search criteria.

Only users with special authorization can display blocked data; they are not authorized, however, to create, change, or copy business objects with blocked data, or perform follow-on activities with these business objects.

The area menu has been enhanced by the following new entries:

● Block Location Master Data (transaction /SCMB/LOC_PRE_EOP)● Unblock Location Master Data (transaction /SCMB/LOC_UNBLOCK_MD)● Delete Location (ILM enabled) (transaction /SCMB/LOC_DEL)● Display Stored Application Logs for Location (transaction /SCMB/LOC_DISPL_LOG)

Effects on Customizing

To use ILM to simplify the deletion of location master data:

● Activate the business function ILM-Based Deletion of Location Master Data ( SCM_SCMB_LOC_ILM_1)

● Make the necessary Customizing settings related to ILM in Customizing under SAP NetWeaverApplication Server Basis Services Information Lifecycle Management .

● Run transaction IRMPOL and maintain the required residence and retention policies for the ILM objects.● Make the necessary Customizing settings related to blocking and deletion of location master data in

Customizing under SCM Basis Master Data Location Location Master Data Deletion .

More Information

● SAP Library for Data Protection under SAP Supply Chain Management Application Help SCM BasisSCM Basis Master Data Location Data Protection Deletion of Location Master Data .

● SAP Note 2249093SAP Note 1825544

2.2 Support Package Stack 3

SCM BasisWhat's New in SAP SCM Basis 7.0, Enhancement Package 4 P U B L I C 9

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2249093


2.2.1 ILM-Based Deletion of SCM Location

Use

As of enhancement package 4, SP 02 for SCM Basis 7.0, the business function ILM-Based Deletion of Location Master Data ( SCM_SCMB_LOC_ILM_1) is available that simplifies the blocking and deletion of location master data by using SAP Information Lifecycle Management (ILM).

Effects on Existing Data

The function enables you to use the ILM component to support the deletion of location master data. Personal data collected in the master data can be blocked as soon as business activities for which this data is needed are completed and the residence time for this data has elapsed; after this time, only users who are assigned additional authorizations can access this data. After the retention period for data expires, personal data can be deleted completely so that it can no longer be retrieved. Residence and retention periods must be defined in the customer system.

Effects on Data Transfer

An end of purpose check determines whether data is still relevant for business activities based on the residence period defined for the data. The retention period of data consists of the following phases:

● Phase one: The relevant data is actively used.● Phase two: The relevant data is actively available in the system.● Phase three: The relevant data needs to be retained for other reasons.

For example, processing of data is no longer required for the primary business purpose but the data must still be available to comply with legal rules for retention. In phase three, the relevant data is blocked.

Blocking of data prevents the business users from displaying and using data that may include personal data and is no longer relevant for business activities.

Blocking of data can impact system behavior in the following ways:

● Display: The system does not display blocked data.● Change: It is not possible to change a business object that contains blocked data.● Create: It is not possible to create a business object that contains blocked data.● Copy/Follow-Up: It is not possible to copy a business object or follow-up a business object that contains

blocked data.● Search: It is not possible to search for blocked data or to search for a business object using blocked data in

the search criteria.

Only users with special authorization can display blocked data; they are not authorized, however, to create, change, or copy business objects with blocked data, or perform follow-on activities with these business objects.

The area menu has been enhanced by the following new entries:

● Block Location Master Data (transaction /SCMB/LOC_PRE_EOP)● Unblock Location Master Data (transaction /SCMB/LOC_UNBLOCK_MD)● Delete Location (ILM enabled) (transaction /SCMB/LOC_DEL)● Display Stored Application Logs for Location (transaction /SCMB/LOC_DISPL_LOG)

Effects on Customizing


What's New in SAP SCM Basis 7.0, Enhancement Package 4

To use ILM to simplify the deletion of location master data:

● Activate the business function ILM-Based Deletion of Location Master Data ( SCM_SCMB_LOC_ILM_1)


● Run transaction IRMPOL and maintain the required residence and retention policies for the ILM objects.● Make the necessary Customizing settings related to blocking and deletion of location master data in

Customizing under SCM Basis Master Data Location Location Master Data Deletion .

More Information

● SAP Library for Data Protection under SAP Supply Chain Management Application Help SCM BasisSCM Basis Master Data Location Data Protection Deletion of Location Master Data .

● SAP Note 2249093SAP Note 1825544

SCM BasisWhat's New in SAP SCM Basis 7.0, Enhancement Package 4 P U B L I C 11



3 Business Functions (SAP Enhancement Package 4 for SAP SCM Basis 7.0)

3.1 ILM-Based Deletion of Location Master Data

Use

Technical Data

Technical Name of Business Function SCM_SCMB_LOC_ILM1

Type of Business Function Enterprise Business Function

Available From SAP enhancement package 4 for SAP SCM 7.0 SP02

Technical Usage SCM

Application Component Location ( SCM-BAS-MD-LO)

Required Business Function Information Lifecycle Management ( ILM)

Incompatible Business Function None

You can use this business function to control the destruction of SCM Location based on settings made in the SAP Information Lifecycle Management (ILM) framework.

Personal data collected in SCM Location master data is blocked as soon as business activities for which this data is needed are completed and the residence time for this data has elapsed. After this time, only users who are assigned additional authorizations can access the blocked data. After the retention period for data expires, personal data is deleted completely so that it can no longer be retrieved. Residence and retention periods must be defined in the customer system.

Integration

This business function works together with the ILM framework to ensure the proper disposal of SCM Location data. The settings made in ILM determine the duration for which an SCM Location is retained. This business function works with the SCM Location master data.


Business Functions (SAP Enhancement Package 4 for SAP SCM Basis 7.0)

Prerequisites

● You have installed the following components as of the version mentioned:

Type of Component Component Required for the Following Features Only

Software Component SCM_BASIS 714 SP02

SAP NetWeaver SAP NetWeaver 740 SP07

● Verify that release/enhancement package/SP of SCM applications (APO, EWM, etc.) you have installed is enabled for simplified blocking and deletion - see SAP Note 2249093 for details

● Activate the business functions ILM-Based Deletion of Location Master Data ( SCM_SCMB_LOC_ILM_1) and Information Lifecycle Management ( ILM).


● Make the necessary Customizing settings related to deletion of location master data in Customizing under SCM Basis Master Data Location Location Master Data Deletion .

● Maintain the required residence and retention policies for the ILM objects (transaction IRMPOL).

Features

This business function enables the following process for deleting a SCM Location:

1. An end of purpose check determines whether the SCM Location data is still relevant for any business activities. The end of purpose check is based on the residence period you configure for the data in the ILM framework. Data is blocked at the end of this period.

2. During the blocking period, data can only be displayed by a user with the appropriate authorization; regular maintenance, however, is not possible:○ The system does not display the blocked data.○ Business object that contains blocked data cannot be changed.○ Business object that contains blocked data cannot be created.○ Business object that contains blocked data cannot be copied or have follow-up activities.○ You cannot search for blocked data or search for a business object using blocked data in the search

criteria.A user with appropriate authorization can unblock the SCM Location data before it is deleted completely.

3. SCM Location data is deleted completely at the end of the retention period defined in ILM.

SCM BasisBusiness Functions (SAP Enhancement Package 4 for SAP SCM Basis 7.0) P U B L I C 13


3.2 Enhanced Services for Transportation Network

Use

Technical Data

Technical Name of Business Function SCM_SCMB_TR_NETWORK


Available From SAP enhancement package 1 for SAP Supply Chain Management 7.0

Technical Usage SCM

Application Component SCM Basis Master Data (SCM-BAS-MD)

Required Business Function Not relevant

You can use this business function to improve the geographical services used in Transportation Network for SAP Supply Chain Management (SAP SCM). Accurate geographical data can help to improve the quality of many features in SAP SCM applications, such as determining geocoordinates for locations, determining distances and durations between locations, and so on. The following functions have been enhanced and improved:

● Geocoding● Distance and duration determination

Prerequisites



Software Component SCMB 701

SCM_BASIS 701

SCMBPLUS 701

External Product Any geographical information systems.

After the activation of the SCM_SCMB_TR_NETWORK business function, you have made the following settings in Customizing for SCM Basis:

● Geocoding



To help the system improve the performance of the distance and duration determination, you have defined geocoding levels under Master Data Location Geocoding Define Geocoding Levels .

● Distance and duration determination

○ You have defined GIS zones under Master Data Transportation Lane Distance and Duration Determination Define GIS Zone .

○ You have assigned countries to GIS zones under Master Data Transportation Lane Distance and Duration Determination Assign Country to GIS Zone .

○ You have defined strategies for the distance and duration determination under Master DataTransportation Lane Distance and Duration Determination Define Strategy for Distance and Duration Determination .

○ You have maintained global settings for the buffering of the distances and durations under Master Data Transportation Lane Distance and Duration Determination Maintain Global Settings for Buffering of DDD .

○ If you are using external GIS providers, you have made settings in the Customizing activity Set Usage of GIS Tool to ensure that the external GIS providers are available. You make the settings under Master Data Transportation Lane Distance and Duration Determination Set Usage of GIS Tool .

Features

Geocoding

Geocoding is the determination of geographical coordinations for locations. To improve geocoding, the following enhancements are available:

● To ensure a more flexible approach to the determination of geocoordinates, you can use the process controller as a flexible framework to create different geocoding strategies so you can connect to external geographical information systems (GIS) different from the standard geocoding program. This flexibility allows you to use third-party GIS providers if required. For more information about how to configure the process controller for geocoding, see Customizing for SCM Basis under Master Data LocationGeocoding Configure Process Controller for Geocoding .

● You can define geocoding levels to store geocoordinates for the address of a location on different levels of detail, for example by house number, postal code, or region. Having different levels of detail for the geocoordinates of a location allows you to improve the performance of the distance and duration buffering table when determining distances and durations between locations. The additional geocoordinates are displayed in the location master.You can define geocoding levels in Customizing for SCM Basis under Master Data LocationGeocoding Define Geocoding Levels .

For more information, see Geocoding [page 94].

Distance and Duration Determination

To ensure more accurate data for transportation lanes, you can use the distance and duration determination to calculate the distance and duration to travel between the start and the destination locations. However, the calculation is done externally by third-party GIS providers and is performance critical. Therefore the following


features are new and enhanced in the distance and duration determination to ensure a more flexible determination of distances and durations and an improved performance:

● To ensure a more flexible approach to the determination of distances and durations, you can use the process controller as a flexible framework to create different distance and duration determination strategies so you can connect to external geographical information systems (GIS) that offer different calculations than the straight line distance and the calculation offered by the standard geocoding program. For more information about how to configure the process controller for the distance and duration determination, see Customizing for SCM Basis under Master Data Transportation Lane Distance and Duration Determination Configure Process Controller for Distance and Duration Determination .

● To improve the performance of the determination of distances and durations, the distance and duration buffering has been enhanced as follows:○ A new table that uses geocoordinates for the buffering has replaced the existing buffering table. You

can precalculate distances and durations for the buffering table to improve the performance by using the Precalculate Distances and Durations for the DDD Buffer report. For more information, see Precalculation of Distance and Duration Determination [page 169].

○ You can use the Deletion of Buffered Distances and Durations report to delete obsolete entries from the distance and duration determination buffering table. For more information, see Deletion of Buffered Distances and Durations [page 171].

For more information, see Distance and Duration Determination [page 165].

3.3 Foundation of External Transportation Management System

Use

Technical Data

Technical Name of Business Function SCM_SCMB_TM_FND1


Available From SAP enhancement package 1 for SAP SCM 7.0

Technical Usage SCM

Application Component SCM Basis SCM-Basis

Required Business Function SCM, Customer and Vendor Master Data Integration into BP ( LOG_SCM_CUSTVEND_INT)

Previously, you could transfer customer and vendor header level data, for example the address, from an ERP system to the business partner in SCM Basis of a SAP Supply Chain Management (SAP SCM) system by using the core interface (CIF). However, many scenarios, for example those of an external transportation management (TM) system, use organization-specific customer data definitions from the ERP system, such as company- or sales-organization-specific partner settings and priorities, that are not transferred using CIF.



You can use the business function to transfer specific attributes of customer and vendor data from an ERP system to a business partner in SCM Basis using CIF. You can use the customer and vendor data as follows:

● If you have manually created an organizational structure in SCM Basis, you can use the customer and vendor data to maintain a company organization that corresponds to the company code in an ERP system and a corporate organization to group company organizations. The company and corporate organizations can be used by, for example, Transportation Charge Management of an external TM system for invoicing and charge calculation.

● You can maintain specific attributes of the customer and vendor in the business partner master. For more information, see Integration of Customer and Vendor Data into Business Partner [page 220].

Furthermore, the SCM basis location master has been extended to maintain international address versions.

View cluster /SCMB/VC_EQU now also includes container-relevant settings.

Integration

In SAP ERP, the business function SCM, Customer and Vendor Master Data Integration into BP ( LOG_SCM_CUSTVEND_INT) is available to extend the outbound CIF interface so that customers who use both an ERP system and an SAP SCM system can transfer the customer and vendor data from the ERP system to the SAP SCM system.

Prerequisites



Software Component SCM_BASIS 701

SCMBPLUS 701

SAP_ABA 702

SAP_BASIS 702

PI_BASIS 702

SAP_BW 702

SAP_BS_FND 702

SAP NetWeaver SAP NetWeaver 7.02


3.4 EH&S Services in SCM: Dangerous Goods continuous improvement

Use

Technical Data

Technical name of the business function SCM_EHS_DG_CI_1


Available as of SAP enhancement package 1 for SAP SCM 7.0

ECC software component SCM_BASIS

ECC application component EH&S Service (SCM-BAS-EHS)

Business Intelligence content Not relevant

SAP Enterprise Services Not relevant

JAVA software component Not relevant

Portal content Not relevant

Additional content available in other SAP applications Not relevant

Business function requiring activation in addition Not relevant

You use this business function to extend the existing functions in the EH&S Service component.

Integration

The functions of the EH&S Service component can be used in other SCM applications.



Prerequisites

You have installed the following components as of the version mentioned:

Type of Component Component Is Needed Only for the Following Features

Software Component SCM_BASIS 701

SAP_ABA 702

Features

With this business function the dangerous goods checks component has been extended to include the check method mixed loading checks. The mixed loading checks determine whether dangerous goods can be loaded together. This requires checks at different levels and allows regulation-dependent rules and enterprise-specific special cases to be mapped. The dangerous goods master dialogue has been extended to include the Mixed Loading tab page.


4 Integration via Core Interface (CIF)

Purpose

The integration via Core Interface (CIF) enables data to be exchanged between an ERP system, in other words, SAP R/3 , SAP R/3 Enterprise, or SAP ERP Central Component ( SAP ECC ) and a connected SCM system. On the SCM side, CIF is part of SCM Basis and can be used by all systems that contain SCM Basis.

The following sections provide information about the integration from a technical point of view, in other words, information about the CIF functions. For more information about the master data that is integrated via CIF and for details about this integration, see Integration of SCM Basis Master Data [page 214] .

4.1 SAP R/3 Plug-In

SAP R/3 Plug-Ins are interfaces that enable the exchange of data between one or more SAP R/3 systems and other SAP components. The SAP R/3 Plug-Ins supply the SAP components from SAP R/3 3.1I to SAP ECC 5.00 with transaction and master data in real time. They enable you to use SAP application components such as 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 require SAP R/3 Plug-Ins . SAP R/3 Plug-Ins are Add-Ons to SAP R/3 .

SAP ERP Central Component 6.0 ( SAP ECC 6.00 ) and later releases will directly contain all the interfaces necessary for the technical integration with other SAP components. These interfaces were previously part of the SAP R/3 Plug-In .

Availability

SAP R/3 Plug-Ins are shipped with SAP application components (for example, SAP SCM , SAP BW , SAP SRM , or SAP CRM ), as well as with SAP industry-specific components based on SAP R/3 4.6B or higher. Customers can download all available SAP R/3 Plug-In releases free from the SAP Service Marketplace.

SAP R/3 Plug-In 2004.1 is the last SAP-R/3 Plug-In release to be delivered separately.

In the future, new and enhanced interfaces for integrating SAP R/3 , SAP R/3 Enterprise , and SAP ECC will no longer be shipped in the form of a separate Add-On ( SAP R/3 Plug-In ).

This means that:

● SAP ECC 6.00 and later releases will directly contain all the interfaces necessary for the technical integration with other SAP components. These interfaces were previously part of the SAP R/3 Plug-In .

● Customers who use SAP R/3 4.6C , SAP R/3 Enterprise 47x100 or 47x200 , or SAP ECC 5.00 will receive additional integration interfaces via a Support Package for SAP R/3 Plug-In 2004.1 as part of the maintenance package and synchronized with the future SAP Business Suite shipment . The shipment for 2005 is in November 2005 with Support Package 10 of SAP R/3 Plug-In 2004.1.


Integration via Core Interface (CIF)

This applies to customers with SAP R/3 Plug-In 2004.1 only. Customers with SAP R/3 Plug-In 2003.1 or older may need to perform an upgrade to SAP R/3 Plug-In 2004.1 or SAP ECC 6.00 .

● Customers who use SAP R/3 3.1I to 4.6B will not receive any additional interfaces for new SAP component releases.

Versions of the SAP R/3 Plug-In

For SAP R/3 Plug-In releases up to and including 2002.1 , SAP provides two versions of the SAP R/3 Plug-In : a PI version for SAP R/3 3.1I to 4.6C and SAP R/3 Enterprise 47x110 and 47x200 , and a PI-A version for SAP R/3 3.1I to 4.5B .

As of SAP R/3 Plug-In 2002.2 , there is only one PI version for all SAP R/3 releases and SAP R/3 Enterprise .

The PI-A version is a subset of PI and contains interfaces for SAP BW . For SAP R/3 3.1I , the PI-A version also supports SAP BBP , SAP EBP , SAP SRM , and SAP Internet Sales . The PI version supports all SAP components that require an SAP R/3 Plug-In .

For SAP R/3 3.1l , the PI version of the SAP R/3 Plug-In is modifying. For SAP R/3 4.0B to 4.6C , the PI version of the SAP R/3 Plug-In is non-modifying. The PI-A version of the SAP R/3 Plug-In is generally non-modifying.

Overview of PI Versions

SAP R/3 Release SAP R/3 Plug-In Version: PI SAP R/3 Plug-In Version: PI-A

SAP R/3 3.1I Supported; modifying Supported; non-modifying

SAP R/3 4.0B Supported; non-modifying Supported; non-modifying

SAP R/3 4.5B Supported; non-modifying Supported; non-modifying

SAP R/3 4.6B Supported; non-modifying Not supported

SAP R/3 4.6C Supported; non-modifying Not supported

SAP R/3 Enterprise 47x110, 47x200 Supported; non-modifying Not supported

Installation

Depending on the combination of the SAP R/3 Plug-In release and version and the SAP R/3 release, certain SAP R/3 Support Package levels are required to install SAP R/3 Plug-Ins . For SAP R/3 3.1I , the PI version can only be installed at a Support Package level for which a CRT is provided.

Non-modifying SAP R/3 Plug-Ins that are installed at the minimum Support Package level require the installation of additional SAP Notes to guarantee complete functional integration. We therefore recommend that you install the most recent SAP R/3 Support Package before the SAP R/3 Plug-In . This is because the most recent Support Package also contains the most recent SAP Notes.

SCM BasisIntegration via Core Interface (CIF) P U B L I C 21

Upgrade

SAP R/3 Plug-Ins are downward compatible with older SAP R/3 Plug-In releases, as well as with older releases of SAP components, provided these components are still in maintenance.

● When upgrading, no SAP R/3 Plug-In release may be missed out.● It is always possible to change from a PI-A version to a PI version. It is not possible to change from a PI

version to a PI-A version.

After an upgrade of SAP R/3 , you must adapt the SAP R/3 Plug-In too. Import the SAP R/3 Plug-In supplement CD that SAP provides for every SAP R/3 Plug-In release shortly after the software becomes available for initial installation.

When you upgrade to SAP ECC 6.00 or higher, the integration interfaces are already included as part of the shipment. You no longer need an SAP R/3 upgrade supplement when upgrading to SAP ECC 6.0 . The SAP R/3 Plug-In is no longer visible as a separate software component in system table CVERS. The objects shipped up to now with the SAP R/3 Plug-In are assigned to the software components SAP_APPL or SAP_HR.

Maintenance

Since SAP R/3 Plug-In 2004.1 is the last SAP R/3 Plug-In release, the general maintenance strategy has changed, as follows:

● The maintenance of the SAP R/3 Plug-In 2004.1 for SAP R/3 3.I to SAP R/3 4.6B comes to an end, in general, at the end of the extended maintenance of the relevant SAP R/3 release, in other words, on 31.12.2006. Up to this point in time, SAP R/3 Plug-In Support Packages will be made available, but they will contain corrections only and no new integration interfaces.

● The maintenance of the SAP R/3 Plug-In 2004.1 for SAP R/3 4.6C , SAP R/3 Enterprise 47x110 and 47x200 , and SAP ECC 5.00 also comes to an end, in general, at the end of the extended maintenance of the relevant release, in other words, on 31.12.2009 for SAP R/3 4.6C , on 31.03.2012 for SAP R/3 Enterprise 47x110 and 47x200 , and on 31.03.2013 for SAP ECC 5.00 .For this release, the SAP R/3 Plug-In 2004.1 will be maintained with Support Packages that contain corrections to errors. Moreover, additional integration interfaces will be shipped once a year in a Support Package synchronized with the future SAP Business Suite shipment.

● SAP R/3 Plug-In 2003.1 is currently maintained via SAP Notes. The mainstream maintenance comes to an end on 31.01.2006.

More Information

For more information, see the following SAP Notes:

● SAP Note 214503: Release Strategy SAP R/3 Plug-In● SAP Note 181255: Composite SAP Note SAP R/3 Plug-In

For more information about availability, supported SAP component releases, maintenance, upgrades, required Support Package Levels, CRT availability, and so on, see the SAP Service Marketplace at http://service.sap.com/r3-plug-in.



SAP Basis Plug-In

The SAP Basis Plug-In is a software component that provides SAP components with BW service API technology as well as functions from CRM Middleware, Supply Chain Event Management, and Financial Basis to establish a connection to these systems.

The SAP Basis Plug-In is an Add-On that can be installed on an SAP Web Application Server or a product that is based on SAP BASIS 620 and SAP ABA 620 or a higher release of these software components.

Unlike the SAP R/3 Plug-In , the SAP Basis Plug-In will continue to be shipped separately. It is also part of the SAP ECC shipment. The SAP Basis Plug-In 2005.1 has been available since August 2005 and will be included in the SAP ECC 6.00 shipment.

Until now, the SAP R/3 Plug-In always required a certain SAP Basis Plug-In release. Previously, when you upgraded the SAP R/3 Plug-In to SAP R/3 Plug-In 2004.1 , for example, you had to first upgrade the SAP Basis Plug-In to SAP Basis Plug-In 2004.1.

As of SAP Basis Plug-In 2005.1 , the rule regarding a corresponding release name no longer exists. In the future, the Support Package shipped for the SAP R/3 Plug-In 2004.1 that contains new interfaces will require a certain SAP Basis Plug-In . Support Package 10 for SAP R/3 Plug-In 2004.1 requires SAP Basis Plug-In 2005.1 .

For more information, see the SAP Service Marketplace at http://service.sap.com/basis-plug-in.

4.2 Core Interface (CIF)

Use

The Core Interface (CIF) is the interface that enables data to be exchanged between an ERP system, in other words, SAP R/3 , SAP R/3 Enterprise, or SAP ERP Central Component ( SAP ECC ) and a connected SCM system.

Prerequisites

To make the relevant communication layer available in the ERP system, you must import a suitable SAP R/3 Plug-In [page 20] up to and including SAP ECC 5.0 . As of SAP ECC 6.0 , CIF is an integrated part of the ERP system.

Features

CIF provides the following central functions:

● Determine source and target systems within complex system environments● Initial transfer of master data from the ERP system


● If your SCM system is SAP Advanced Planning and Optimization (SAP APO), CIF offers the following additional functions:○ Transfer of planning-relevant transaction data and changes to transaction data○ Return of planning results from SAP APO

● Tools for administering the data transfer

Activities

1. Setting up the system landscape and data transfer. To do this, an Implementation Guide is available in both the ERP and SCM systems. For more information, see:○ CIF Customizing in the ERP System [page 24]○ CIF Customizing in the SCM System [page 26]

2. Triggering the data transfer itself. For more information, see Data Transfer [page 36] .3. Administering the current operation. For more information, see Administration [page 60] .

4.2.1 CIF Customizing in the ERP System

Use

CIF Customizing in the ERP system is used to set up the system infrastructure and to configure the data transfer via Core Interface (CIF). CIF Customizing also covers application-specific settings and enhancements for CIF.

An Implementation Guide (IMG) is available for Customizing. The IMG provides you with a clear overview and explanation of all steps that are necessary for integration via CIF. With the exception of organizational IMG activities that only contain a description, you can go directly to the relevant transaction and execute the action.

Integration

In addition to the Customizing settings in the ERP system, you must also make the necessary Customizing settings in the SCM system. For more information, see CIF Customizing in the SCM System [page 26] .

Prerequisites

You work with SAP R/3 4.0B or higher.

You have imported SAP R/3 Plug-In 2002.2 or higher, as necessary.



Features

The IMG consists of three main areas:

● Basic Settings for Creating the System LandscapeHere you can find all the IMG activities that are necessary for the partner systems to be able to communicate with one another via CIF. This includes naming logical systems, naming an RFC destination, and making qRFC settings.

● Basic Settings for the Data TransferHere you can find all the IMG activities that are necessary for the data transfers, that is, the initial data transfer and change transfers.

● Application-Specific Settings and EnhancementsHere you can find customer exits, Business Add-Ins (BAdIs), and settings for individual applications.

Activities

1. You call 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 find the IMG in the SAP Reference IMG under Integration with Other SAP Components Advanced Planning and Optimization .

2. You make the relevant settings.

Note that some of the basic settings are target-system-dependent or client-specific. These settings 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 may also have to make changes in the productive system for some other settings. The following table contains a list of these settings and information about how you can make these settings in the productive system.

Setting Path in CIF Menu** Transaction Code

Define logical system In the ALE menu* under Sending and

Receiving Systems Logical System

BD54

Assign logical systems to a client In the ALE menu* under Sending and

Receiving Systems Logical System

SCC4

Specify SAP SCM release In the CIF menu** under Settings NDV2

Set RFC destination In the CIF menu** under Settings SM59

Assign RFC destination to various application cases

As of SAP R/3 Plug-In 2002.2 Support Package 1, in the CIF menu** under Settings

CFC7


Set target system and queue type In the CIF menu** under

Environment Current Settings

CFC1

Set user parameters In the CIF menu** under


CFC2

Define filter and selection block size In the CIF menu** under


CFC3

Determine number ranges for parallelization

In the CIF menu** under


CFC8

* You access the ALE menu by using transaction SALE.

** You find the CIF menu in the SAP menu under Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer .

4.2.2 CIF Customizing in the SCM System

Use

CIF Customizing in the SCM system is used to set up the system infrastructure and to configure the data transfer between an SCM system and the ERP system via Core Interface (CIF). CIF Customizing also covers application-specific settings and enhancements.

An Implementation Guide (IMG) is available for CIF Customizing. The IMG provides you with a clear overview and explanation of all steps that are necessary for integration via CIF. With the exception of organizational IMG activities that only contain a description, you can go directly to the relevant transaction and execute the action.

Integration

In addition to the Customizing settings in the SCM system, you must also make the necessary Customizing settings in the ERP system. For more information, see CIF Customizing in the ERP System [page 24] .

Features

The Implementation Guide for CIF consists of three main areas:

● Basic Settings for Creating the System LandscapeHere you can find all the IMG activities that are necessary for the partner systems to be able to communicate with each other via CIF (for example, naming the logical systems, naming RFC destinations, and making qRFC settings).



● Basic Settings for the Data TransferHere you can find the IMG activities for the data transfer.

● Application-Specific Settings and EnhancementsHere you can find Business Add-Ins (BAdIs), customer exits, and settings for individual applications.

Activities

1. If your SCM system is SAP Advanced Planning and Optimization, in the 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.2. You make the relevant settings.

Note that some of the basic settings are target-system-dependent or client-specific. These settings are not transported from the Customizing client to the productive client. This means you also have to make the settings in the productive client.

4.2.3 Setting Up the System Infrastructure

Purpose

Setting up the system infrastructure is a prerequisite for transferring data via Core Interface (CIF).

Since data is distributed between the partner systems, you have to identify each system within the system infrastructure. The logical systemis used for this purpose.

CautionDo not use the same name for more than one logical system.

If data from different logical systems is to reference the same objects in the SCM system (for example, because you work with multiple ERP systems and one SCM system), two prerequisites must be met.

1. Define a business system group (BSG). This step is always necessary. The BSG integrates different physical systems into a superordinate logical unit. To make the settings, in CIF Customizing in the SCM System [page 26] , choose Basic Settings for Creating the System Landscape Maintain Business System Group.

RecommendationIf you create master data in the SCM system, we recommend that you assign this system to the same BSG as that used for the logical systems that contain the master data server. Only then can preliminary maintenance of the master data be carried out in the SCM system.

Once you have transferred data, it can be problematic to subsequently change the BSG assignment.

2. Set up mapping structures, in other words, maintain/activate user enhancements. For more information, see SAP Library on SAP Help Portal at http://help.sap.com SAP Supply Chain Management (SAP SCM)


SAP Advanced Planning and Optimization (SAP APO) Integration via Core Interface (CIF) Technical Integration Core Interface (CIF) Setting Up the System Infrastructure Checklist for Setting Up the System Infrastructure Mapping: Technical Transfer Structures Customer Exits.

To be able to uniquely refer to identical keys from different business system groups in the SCM system, the primary key is supplemented by the business system group key. For more information, see the documentation for the IMG activity mentioned above.

Prerequisites

At least one ERP system and one SCM system must be successfully installed.

NoteIf the ERP system was previously used as a standalone system, it is possible that the system distribution (ALE) is not maintained sufficiently. Check whether ALE is active in your ERP system and maintain the logical system in Customizing in the ERP system, as necessary.

Process

You perform the steps necessary for setting up the system infrastructure. For more information, see Checklist for Setting Up the System Infrastructure [page 28] .

Result

After you have completed the steps required to set up the system infrastructure, you can trigger the actual data transfer [page 36] .

4.2.3.1 Checklist for Setting Up the System Infrastructure

The following table shows the Customizing steps required for the technical integration via Core Interface (CIF).

If you work with SAP R/3 4.0B or higher , an Implementation Guide (IMG) is available for CIF Customizing in the ERP System [page 24] . There is also an IMG for CIF Customizing in the SCM System [page 26] . You find the relevant IMG activities in the corresponding IMG under the structure nodes Basic Settings for Creating the System Landscape and Basic Settings for Data Transfer .



CIF Customizing in the ERP System

Step Transaction Obligatory?

Check ALE settings and activate, as required:

● Define the logical system● Assign logical system to clien t

SALE Obligatory

Define the RFC destination SM59 Obligatory

Set up the target system and assign the queue type [page 34]

Caution

If you set the Inbound Queue queue type in the ERP system, you have to register CIF queues (CF*) in the QIN scheduler in the SCM system.

CFC1 Obligatory

Maintain SCM release NDV2 Obligatory

Set number ranges for parallelization [page 48]

CFC7 If needed

Activate BTEs for integration [page 30]

BF11 If needed

Register CIF queues in the QIN scheduler [page 34] if you have changed to inbound queues in the SCM system

SMQR If needed

CIF Customizing in the SCM System


Check ALE settings

● Define the logical system● Assign logical system to clien t

SALE Obligatory

Define the RFC destination SM59 Obligatory

Maintain business system group /SAPAPO/C1 Obligatory



Assign logical system and queue type [page 31]

If you set the Inbound Queue queue type in the SCM system, you have to register CIF queues (CF*) in the QIN scheduler in the ERP system.

/SAPAPO/C2 Obligatory

Register CIF queues in the QIN scheduler [page 34] if you have changed to inbound queues in the ERP system

SMQR If needed

Register CIF queues in the QOUT scheduler, if you have configured outbound queues in the ERP system

SMQS If needed

Maintain distribution definitions /SAPAPO/CP1 Obligatory

Create customer exits for uniquely identifying master data. For more information, see the Implementation Guide (IMG) for SCM Basis.

CMOD (Customer Exits)

SE19 (Business Add-Ins)

If needed

4.2.3.1.1 Activating BTEs for CIF Integration

Use

The transfer of changes to transaction data is carried out as an online transfer in most cases. In some cases, it may also make sense to carry out the transfer of changes to master data as an online transfer.

To be able to use this online transfer, you need to activate Business Transaction Events (BTEs) for integration via CIF in the ERP system. If you have an integrated system infrastructure with several ERP systems, this step must be made in each ERP system before online transfer can be used.

Procedure

1. In the ERP system, use transaction BF11 to call the Change View "Application Indicator": Overview screen.2. Set the application indicator for ND-APO (New Dimension Plug-In APO) or NDI (New Dimension

Integration) to active.



Result

The online transfer is activated for transaction data.

To activate the online transfer of master data, you need to follow additional steps. For more information, see Initial Creation of Master Data [page 50] in the section Online Transfer Using Business Transfer Events .

4.2.3.1.2 Assigning Logical System and Queue Type

Use

To enable error-free communication with the SCM system, each source system (ERP) must be assigned to a business system group (BSG). A BSG can be composed of one or more source systems.

You assign a logical system and a queue type (outbound or inbound) to the BSG. For more information about assigning the queue type, see Setting Up the Target System and Assigning the Queue Type [page 34] .

For more information, see Setting Up the System Infrastructure [page 27] .

Procedure

As of SAP R/3 Plug-In 2000.1, this setting is made in Customizing and it is documented in the Implementation Guide (IMG) for SCM Basis.

If you work with SAP APO, see also the Implementation Guide (IMG) for SAP Advanced Planning and Optimization (SAP APO) under SAP Advanced Planning and Optimizer (SAP APO) Basis SettingsIntegration Business System Group Assign Logical System and Queue Type .

4.2.3.1.3 Defining the RFC Destination

Use

Before two or more systems can communicate with each other, the technical coupling between them must be set up. The target address for the data transfer is determined during the setup of an RFC destination in the ERP system. The name of the corresponding RFC destination must be identical to the name of the logical target system. One RFC destination is required for each target client (for example, 001).

Prerequisites

System administration needs to have made the necessary system settings in the distribution model (ALE).


See Checklist for Setting Up the System Infrastructure [page 28]

Procedure

Call transaction SM59.

The Configuration of RFC Connections screen appears.

Choose Create .

The RFC Destination screen appears.

Enter the required data as follows:

Field Procedure

RFC Destination <Name of the RFC destination>. Choose any name.

Use a maximum of 10 characters for the name.

Connection Type Use the input help (F4) to select the appropriate connection type. In this case: Type 3 (connection to R/3 system)

Description <Any entry>.

Client 001 on target machine X

Language Not necessary

Trace Not necessary

Setting the indicator gives you access to a diagnosis tool.

Client Use the input help (F4) to select the appropriate client.

The client setting is dependent on the current user's authorization profile (Customizing).



User <Any entry>.

The user specified here must also have the appropriate authorization profile created in the target system. If you want to debug all applications, the appropriate user in the target system must be created as a dialog user with debugging permissions.

Password <Any entry>. Presetting at delivery: initial .

Save your entries.

The Technical Settings group box displays additional entry fields.

Enter the required data as follows:

Field Procedure

Load Distribution Select "No".

Only worthwhile if the SCM instance is implemented in a distributed system environment.

Target Host <X>

To determine the destination of the target machine:

Select Start menu à SAP logon

Select Server...

Copy the description from the entry field Message Server .

System Number Specify the number of your target system.

To determine the system number:

Start your SAP logon

Select your target system

Select Properties.

A dialog box appears that displays the system number.


Choose Destination → TRFC options . In the Connection attempts up to task field, enter a value >10, and in the Time betw. 2 tries (mins) field, enter the value 2. Confirm your entries by choosing Continue .

Choose either classic qRFC or bgRFC [page 35] . In most cases, you choose classic qRFC.

Running a connection test is optional.

Choose Exit.

4.2.3.1.4 Setting Up the Target System and Assigning the Queue Type

Use

To set up successful communication, the relevant target system for this connection must be installed after defining the RFC destination. You install a valid operation mode at the same time.

You assign a queue type to the connection to the selected system. The queue type Outbound Queue is set by default.

Change to Inbound Queues

You should choose Inbound Queues if you are expecting large amounts of data during the transfer from the source system to the target system and you want to ensure that the target system is not overloaded. With this setting, queue processing is controlled by the target system.

If you choose Inbound Queues i n the source system, you have to set up the QIN (queue in) scheduler in the qRFC monitor in the target system. Queues that are to be automatically processed by the target system must be registered in the QIN scheduler.

If you work with outbound queues, you must register the target system in the QOUT (queue out) scheduler.

Procedure

1. After calling the CIF menu in the ERP system (see Calling the CIF Menu [page 36] ), choose SettingsTarget Systems .

2. The screen Change View ' Target Systems , Operation Modes , and Queue Type: Overview appears.3. Choose New Entries.4. Enter the connection as follows:

○ Under LogSystem , enter the same name that you previously used for the RFC destination.○ The system automatically sets the operation mode.

5. Save your entries and quit the screen by choosing Exit .

Registration of CIF Queues in the Target System When Converting to Inbound Queues

1. Call the QIN scheduler in the target system using transaction SMQR.2. To select all CIF queues, enter CF* in the Queue Name field.



3. Choose Register . You see the Queue Registration dialog window. We recommend the following entries:○ Queue Name: CF*○ EXEMODE: D (Dialog processing) or B (Background processing)○ MAXTIME: 10 (maximum processing time)○ NRETRY: 30 (number of repetitions for locked queues)○ TDELAY: 300 (time between two repetitions)

4.2.3.2 Background RFC (bgRFC)

Use

Alongside the classic queued Remote Function Call (qRFC), SAP NetWeaver also offers the background RFC (bgRFC) for improved performance when transferring data. You can also use this RFC for transferring data via Core Interface (CIF).

For more information about the bgRFC, see the documentation for SAP NetWeaver under Components of SAP Communication Technology Classical SAP Technologies (ABAP) RFC Queued Remote Function Call (qRFC) bgRFC (Background RFC).

Depending on the transfer direction for which you want to improve performance, you can use the bgRFC for the transfer from the ERP system to the SCM system and for the transfer from the SCM system to the ERP system. You can also use it for both transfer directions at the same time.

Prerequisites

You have performed the basic settings for setting up the system landscape in Customizing for the relevant system.

Activities

To be able to use the bgRFC, you must activate it for the required transfer direction. By default, CIF uses the classic qRFC.

● Activating the bgRFC in the ERP systemIn the Implementation Guide (IMG) for the ERP system, choose Integration with Other SAP Components

Advanced Planning and Optimization Basic Settings for Setting Up the System Landscape Settings for qRFC Communication Activate/Deactivate Background RFC (bgRFC) and perform the steps described there.

● Activating the bgRFC in the SCM system


In the Implementation Guide (IMG) for the SCM system, choose SCM Basis Integration Basic Settings for Creating the System Landscape Settings for qRFC Communication Activate/Deactivate Background RFC (bgRFC) and perform the steps described there.

4.2.3.3 Mapping: Technical Transfer Structures

Mappingis the assignment or mutual display of data or data types from the sending and target systems.

When an SCM system is connected to an ERP system, we recommended that you assign both systems to the same business system group. If you do not, the master data must be maintained locally for each system.

One mapping table is created for each system. This enables you to publish a different key externally from the internal one used in the system.

The ERP key is mapped to the SCM key and then converted to a GUID.

For more information, see CIF Customizing in the SCM System [page 26] under Basic Settings for Creating the System Landscape Maintain Business System Group.

4.2.4 Data Transfer

Purpose

The following process controls the transfer of data from the systems.

Prerequisites

You must have completed the Customizing steps required for setting up an integrated system infrastructure and for data transfer.

For more information, see CIF Customizing in the ERP System [page 24] and CIF Customizing in the SCM System [page 26] .

4.2.4.1 Calling the CIF Menu

Use

From the CIF menu in the ERP system, you can access individual functions of the Core Interface (CIF).



Procedure

For SAP R/3 3.1I to 4.5B

1. Enter the transaction CIF in the command field in the main screen of SAP R/3.2. Confirm this entry using the return key.

As of SAP R/3 4.6B

As of SAP R/3 4.6B, you call the CIF menu via the SAP Easy Access menu. Choose SAPMenu LogisticsCentralFunctions SupplyChain PlanningInterface Core Interface Advanced Planner and Optimizer .

Note

In SAP R/3 release 4.6A, choose Logistics CentralFunctions SCPInterface SCPInterfaces Core Interface Advanced Planner and Optimizer.

4.2.4.2 Integration Model

Definition

The integration model controls the transfer of master data and transaction data. It is generated in the ERP system and contains all data that is to be transferred to the SCM system. It is uniquely identified by name and application.

Use

Only those data objects are transferred from the ERP system that are needed in the SCM system. These data objects are specified in the integration model.

For more information, see Core Interface (CIF) [page 23] .

See also:

● Generating Integration Models [page 38]● Activation and Deactivation of Integration Models [page 41]● Displaying Integration Models [page 57]● Deleting Integration Models [page 59]● Finding Filter Objects [page 58]


4.2.4.2.1 Generating Integration Models

Use

In most cases, only some of the master data and transaction data available in the ERP system is needed for planning in the SCM system. When you generate an integration model, you specify which data objects are to be selected from the total dataset in the ERP system for the transfer.

To create the integration model, you first select the object types (for example, material masters) to be selected on the Create Integration Model selection screen. Next, you select specific selection criteria (in most cases, a material/plant combination) that further restrict the object types you have already selected. If you have already selected Material Masters , for example, you could now enter an MRP controller. In this way, you define filter objects. Filter objects are used to select which data objects are transferred to a specified SCM system. In the example, all material masters for a particular MRP controller are selected.

For more information, see Select Filter Objects below.

Working with Variants

Since the system does not save the selection options you make when creating an integration model, you have to save the settings as a variant on the selection screen. By working with variants you are able to reuse the settings you have saved whenever you want. If you want to recreate an integration model at a later point in time, you can call up the required variant by choosing the Select Variant symbol in the toolbar at the top of the selection screen.

Integration Model Versions

If you regenerate an integration model, the system automatically generates a new version of this model. Different versions of an integration model are distinguished by their date and time of creation, as well as by the filter objects that they contain. You can create as many versions of an integration model as you want. However, only one version may be active at any time.

Changing an Integration Model

We recommend that you change an existing variant of the integration model, generate a new version using transaction CFM1, and then save the variant. You can also create a runtime version of the active integration models. For more information, see Runtime Version of the Active Integration Model [page 45] .

Structure of an Integration Model (Valid Only for SAP APO)

The structure of an integration model influences performance. When it integrates transaction data, the system checks whether the data concerned is contained in the active integration model. At the same time, the system loads and interprets all active integration models for the object type concerned to determine any target systems that may be affected. The greater the number of integration models per object type, the longer the runtime required for determining the target systems.

NoteFor performance reasons, we recommend that you do not enter both master data and transaction data in one integration model.

You have to activate the integration model to trigger the initial transfer of ERP data to the SCM system. See also Activation and Deactivation of Integration Models [page 41] (report RIMODACT).

You can subsequently deactivate and delete integration models that are no longer needed.



See also Deleting Integration Models [page 59] (report RIMODDEL).

Prerequisites

The Customizing and default settings for integration must be maintained. The relationship between the source and target system must also be maintained in both systems.

For more information, see CIF Customizing in the ERP System [page 24] and CIF Customizing in the SCM System [page 26] .

Activities

For SAP R/3 3.1I - 4.5B, open the CIF area menu (transaction CIF). Choose Integration Model GenerateCreate .

As of SAP R/3 4.6B, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Generate Create. .

The Create Integration Model screen appears.

You can also call this report (RIMODGEN) using transaction CFM1.

Define Integration Model

The three required entry fields in the upper section of the selection screen are used to define the scope of the integration model you want to create.

1. Model name: Enter an alphanumeric description or choose an existing model name using the input help (for example, PUMP).

2. Logical system: Enter the target system (logical system). This name is identical to the RFC destination.3. APO application: Enter another name of your own choosing so that you can differentiate between

integration models with the same model name (for example, MATMASTERS).

Select Filter Objects

For Material-Dependent Objects

1. In the Material Dependent Objects screen section, you select the fields for object types that you want to include in your integration model (for example, material masters). Note the recommendations for the combination and sequence of object types given under Example .

2. In the General Selection Options for Materials screen section, you further restrict the selected object types by entering the selection criteria (value ranges) for materials (for example, all materials with the MRP type 1 to 5). These selection criteria are valid for all object types selected under Material Dependent Objects . If you click the arrow button to the right of a field, the dialog box appears where you can make multiple selections. Here, you can specify more complex selection criteria by further restricting the value ranges or by excluding certain value ranges from the transfer.


CautionIf you make no further restrictions to the selection made in point 1, the system automatically selects all objects for this object type (for example, all material masters). This can lead to significant performance problems.

3. Under General Selection Options for Materials, you can make further restrictions to those you have already made by specifying additional selection criteria. This is done by clicking the arrow button to the right of the field for the relevant object. You can also make multiple selections here. These selections are only valid for the current object type.

NoteEven if you only restrict the selection by material and plant, we recommended that you use the selection options in the General Selection Options for Materials screen section. In this case, the selection shows significantly improved performance compared to entering the values in the selection options for the individual object types.

For Material-Independent Objects

1. In the Material Independent Objects screen section, you select the fields for object types that you want to include in your integration model (for example, customers). Note the recommendations for the combination and sequence of object types given under Example .

2. You can additionally restrict the object types selected for material-independent objects by clicking the arrow button to the right of the relevant field and specifying further selection criteria (value ranges). These selections are only valid for the current object type. You can also make multiple selections here.

Results and Saving

To display the results list, choose Execute . You see a list displaying 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.

1. Select the filter object you want to view.2. Choose the Details pushbutton. You see a list of all data entries that have been found for the selected filter

object.3. You leave the screen by choosing Back .

Generate the integration model. A dialog box confirms that the integration model was generated successfully.

Example

Suggestion for the Structure of the Transaction Data Integration Model

The following objects should each be grouped together in a separate integration model and activated in the sequence given:

1. Stocks (if you hold special stocks at the customer or vendor, the relevant customer or vendor must be contained in the same integration model)

2. Sales orders (includes sales orders, deliveries, scheduling agreements, quotations, and customer independent requirements)



3. Purchase orders and purchase requisitions4. Production/process orders and planned orders (these may need to be separated). These have to be

activated before production campaigns.5. Manual reservations and planned independent requirements6. Production campaigns and process/planned orders7. Shipments

4.2.4.2.2 Activation and Deactivation of Integration Models

Use

The activation of integration models results in an initial transfer. If you work with SAP APO, the online transfer of transaction data is released. As standard, the integration models to be activated are compared with the integration models that are already active. In this way, the transfer restricts itself to differences, in other words, only data for filter objects that are not contained in an active integration model is transferred.

NoteTo retransfer all data records, you have to deactivate and then reactivate all active integration models.

You can generate multiple integration models. However, only one version can be activated for each model. You can activate and deactivate several integration models simultaneously.

Integration models must remain active to enable online transfer.

Prerequisites

To activate an integration model, you first have to generate it using the report Create Integration Model (RIMODGEN).

For more information, see Generating Integration Models .

Activities

For SAP R/3 3.1I - 4.5B, open the CIF area menu (transaction CIF). Choose Integration Model Activate .

As of SAP R/3 4.6B, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Activate .

You can also call this report (RIMODACT) using transaction CFM2.

The Activate or Deactivate Integration Model screen appears.


Use the entry fields listed below to select the integration model to be activated:

● Model● Logical system● APO application

NoteIf you do not make an entry for the model, Logical System, and/or for APO Application and the report is started, the system automatically includes all integration models with the same name in the list of results (version creation).

● For more information about the Log Deactivated Material Masters indicator, see below.● For more information about the Parallelized Transfer screen section, see Parallelized Initial Data Transfer .

Result

The selection screen displays the available integration models for the model name you have specified.

Versions : If several integration models exist with the same name, they are displayed in chronological order (according to date and time). They may also be assigned to different logical systems (target systems) and APO applications.

You can activate the required model by double-clicking it or by using the Active/Inactive pushbutton. An OK icon displayed to the left of the model generation date and time shows that the integration model has been activated.

If you wish to deactivate the integration model, repeat the above procedure and ensure that the OK icon is no longer displayed.

Choose the Start pushbutton to begin the data transfer. The data is now transferred in the background.

You can use the Check pushbutton to perform a consistency check on the resulting status of the integration model. All active models are tested, including those models scheduled for activation, but not including those models scheduled for deactivation (for more information, see Consistency Check ).

Deactivation

Deactivating an integration model does not lead to the deactivation or deletion of the corresponding objects in the SCM system.

An exception to this is the material master: If you set the Log Deactivated Material Masters indicator, the system logs all material masters that you deactivate in the ERP system. For more information, see Logging Deactivated Material Master Data .

CautionSome object types refer to filter objects of a different object type. For example, operations are only transferred to SAP APO if they belong to a routing for which the work center is contained in an active integration model for resources. If you deactivate the integration model for work centers, these work centers will not have any operations once a new transfer of production process models takes place. This is also true for operations of production and process orders.



4.2.4.2.3 Logging Deactivated Material Master Data

Use

If you no longer need a material in an SCM system (because this material is already flagged for deletion in SAP ERP or is no longer to be planned in the SCM system, for example), you can deactivate the integration model containing the material. In this case, the corresponding product in the SCM system is no longer supplied with changes from SAP ERP. However, the product still exists in the SCM system and can also be used by planning.

Using the logging function for deactivated material masters, you can have the system log the materials that are no longer contained in an active integration model but which still exist on the SAP SCM side.

In a second step, you can use program RCIFMTDE to execute a complete data transfer of the deactivated material masters to the SCM system. During this transfer, the procurement type for these products in the SCM system is automatically set to External Procurement Planning . These products are then no longer used by Production Planning and Detailed Scheduling (PP/DS). For more information, see SAP Note 364287.

You can then definitively delete these products that are no longer relevant to planning.

Activities

● In the CIF menu, choose Integration Model Activate. Select the integration model whose materials you no longer need in the SCM system. Set the Log Deactivated Material Masters indicator for this integration model. Deactivate the integration model containing the materials that you no longer need in the SCM system.

● The system logs the deactivated material masters.● Use program RCIFMTDE to completely transfer the deactivated material masters to the SCM system.● The system automatically sets the procurement type for these products to P ( External Procurement

Planning ).PP/DS does not take into account products with this procurement type.● If you want to definitively delete these products in the SCM system, you can set the deletion flag for them

and then delete them.

NoteIf you want to delete a large number of such products at once, you can also set the deletion flag for products with procurement type P via mass maintenance. To do this, in mass maintenance, choose the attribute Procurement (BESKZ) and the value P as the selection criteria for the object type Product . Enter the attribute Deletion Flag (LVORM) for these products.

4.2.4.2.4 Consistency Check

The consistency check can be carried out at two different points in time:

● When an integration model is being generated, the model to be generated is analyzed.


● When integration models are being activated, the check is carried out on active integration models, including integration models that are to be activated, but not including integration models that are to be deactivated.

As a result of the check, a dialog box appears that displays a corresponding message.

ExampleThe consistency check applies if, for example, requirements are to be transferred but you did not consider the appropriate material master when you selected filter objects.

The following list indicates what each filter object is being checked for:

Filter Object Contained in (active) integration model?

Material Plant

Production process model (PPM) Material master, resource

Resource Plant

Plant Is the time zone maintained?

Customer Is the time zone maintained?

Vendor Is the time zone maintained?

Stock Material master

Special stock at customer Customer

Special stocks with vendor Vendor

Planned independent requirement Material master

Purchase order Material master

Planned order Material master

Sales order Material master

Material consumption data Material master

Production campaign Material master, production order

Manual reservations Material master

Manufacturing order Material master

ATP check for materials Material master



4.2.4.2.5 Runtime Version of the Active Integration Model

Definition

Database table (CIF_IMAX) that is fully buffered and formatted in an optimized way. It contains exactly one integration model for each object type and each logical system. The runtime version is formed from all active integration models for a particular object type and target system. It is formatted in an optimized way, compressed, and saved to the database. In addition, the information in the runtime version is buffered to all ERP application servers. The runtime version of the active integration models is also called the maximum integration model.

The user creates the runtime version once by using the RCIFIMAX report and then it is automatically updated by the system every time an integration model is activated. To do this, the system reads from the CIF_IMOD database table all active integration models created by the user for the relevant object type and logical system, and then uses this to generate the runtime version.

Compared to the CIF_IMOD database table, the runtime version offers the following advantages:

● Improved performance because only object data for a specific object type needs to be loaded for an integration model

● As a result, database accesses that reduce performance are not needed for online transfer and the target system can be determined faster. Also, the performance for online transfer is not linked to the number of active integration models when the runtime version is used.

● Improved usability because integration model construction now only has a small influence on performance. The speed at which the runtime version is generated depends on the number of integration models.

Use

The runtime version of the active integration model requires SAP R/3 Plug-In 2002.1 or higher. When you install SAP R/3 Plug-In 2002.1 or higher, we recommend that you generate runtime versions for all available integration models. You do this by calling report RCIFIMAX, specifying the relevant object type and target system, and setting the Generation indicator. Note that the runtime version has to be generated in all ERP systems and clients. If the runtime version is not generated, the system continues to access the CIF_IMOD table to determine target systems.

You can also use the same report and the Consistency Check indicator to check whether runtime versions and integration models are consistent. We recommend that you schedule this report as a regular background job. No integration models may be activated during the consistency check. For more information, see CIF Customizing in the ERP System [page 24] under Basic Settings for the Data Transfer Initial Data TransferSchedule Regular Jobs .

You can rectify inconsistencies by generating the runtime version again. However, if unexpected inconsistencies continue to occur, open a problem message in SAPNet - R/3 Frontend and describe the steps that led to the inconsistency.


4.2.4.3 Initial Data Transfer

Use

You transfer relevant data from the SAP ERP system to the SAP SCM system by means of the initial data transfer.

Prerequisites

You have made the basic settings for the integration:

● For the SCM system, see CIF Customizing in the SCM System [page 26].● For SAP ERP 3.1I, see Checklist for Setting Up the System Infrastructure [page 28]. As of SAP ERP 4.0B,

Customizing is available. For more information, see CIF Customizing in the ERP System [page 24].

Features

In the integration model, you select the data that is required in the SCM system. The integration model has the following tasks:

1. Defining the target system2. Selecting the filter objects to be transferred, that is, compiling a data pool for the initial data transfer3. Triggering the initial data transfer

NoteAs standard (that is, if you have not set parallelized initial data transfer), the initial data transfer always runs using the same queue, irrespective of the object type transferred. In other words, it runs in serial. If you use serialization, you cannot trigger a second initial data transfer to the same SCM system, even if none of the selected object types overlap with the active integration model. During an initial data supply run, all transaction data postings are synchronized with the initial supply that is currently running. That means that the method and time of the transaction data transfer are dependent upon the processing status of the initial data transfer. This ensures that the system always transfers the most recent transaction data and helps to avoid data inconsistencies. However, this can reduce the performance of the transaction data postings. For this reason, we recommend that you carry out the initial data transfer during a time when the number of postings is at a minimum (for example, at night).

You can improve system performance in the following ways:

○ You can parallelize the initial data transfer. For more information, see Parallelized Initial Data Transfer [page 48].

○ You can change to inbound queues if there is a large system load in the target system. For more information, see Queue Type Selection for the Initial Data Transfer [page 47].

○ You can activate incremental data transfer for product master data, location product master data, and production data structure (PDS) (in SAP APO only). To use the incremental data transfer, you have to activate the Enhanced Initial Data Transfer ( CA_CIF_INILOAD_01) business function,



which is available as of SAP ECC 6.0 enhancement package 4. For more information about the incremental data transfer, see Customizing for SAP SCM under SCM Basis Integration Basic Settings for Data Transfer Activate Incremental Data Transfer or Integration with SAP Components Integration via APO Core Interface (CIF) Basic Settings for Data Transfer CIF Error Handling Activate Incremental Data Transfer .

Activities

● You create an integration model. For more information, see Generating Integration Models [page 38].● You execute a consistency check for the integration model, if necessary. For more information, see

Consistency Check [page 43].● You activate the integration model. For more information, see Activation and Deactivation of Integration

Models [page 41].

4.2.4.3.1 Queue Type Selection for the Initial Data Transfer

Data transfers using the Core Interface (CIF) generally take place in serial using queues. For this, there are two queue types available: outbound queues and inbound queues.

You can specify the queue type that should be used for data transfer for a certain target system. You assign a queue type to a target system in the ERP system in CIF Customizing in the ERP System [page 24] . This setting is dependent upon the current system. Since the production system usually has a different target system from the system in which Customizing is carried out, you also have to make this setting in the production system. You can make this setting in the SAP menu under Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Environment Current Settings Set Target System and Queue Type, or by using transaction CFC1.

As standard, the initial data transfer is carried out using outbound queues. If you enter a logical target system in CFC1, the system automatically suggests the Outbound Queues queue type. The Outbound Queues setting means that queue processing is controlled by the sending system.This can lead to problems if the target system does not have sufficient free work processes to process the queues.

If you are expecting a large amount of integration data and insufficient work process resources in the target system, it may be useful to change to inbound queues. The Inbound Queues setting means that queue processing is controlled by the target system.If there are insufficient work processes available here, the data is first saved temporarily in inbound processing in the target system and then processed gradually as resources become available. For more information, see Setting Up the Target System and Assigning the Queue Type [page 34] .


4.2.4.3.2 Parallelized Initial Data Transfer

Use

In most cases, the initial data transfer runs in serial. For a serialized initial data transfer, the system selects all objects sequentially in the SAP ERP system, transfers them to the target system, and then processes them there in the same sequence. The correct sequence of individual objects is guaranteed because existing dependencies between the objects are taken into account. However, it may be useful to change to parallelized data transfer for performance reasons. You can activate several integration models in parallel; that is, at the same time. In the same way as for a serialized data transfer, the Core Interface (CIF) ensures that an object is only transferred once, even if it is contained in several integration models.

For certain object types within an integration model (see below), you can specify that the transfer of objects of this type is to run in parallel. For this, you can decide whether the selection in the ERP system, the subsequent processing in the target system, or both, are to run in parallel. However, parallelization is only possible within each object type; that is, the objects of one object type are transferred in parallel, but the object types themselves are transferred in serial as before. The system only begins to process the next object type once the entire selection for the previous object type has been completed.

Prerequisites

● You have defined a number range in Customizing for CIF in the SAP ERP system for parallelized initial data transfer (see CIF Customizing in the ERP System [page 24]). For more information, see Customizing for SAP ERP under Basic Settings for the Data Transfer Initial Data Transfer Determine Number Ranges for Parallelization. .

● The above setting is dependent upon the current target system. Since in most cases the production system has a different target system from the system in which Customizing is carried out, you have also made this setting on the SAP Easy Access screen of the productive system under Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Environment Current Settings Define Number Ranges for Parallelization .

Features

The parallelized initial data transfer incorporates the following functions:

● Parallelized selection in the ERP systemThe ERP system selects the objects to be transferred in parallel in different work processes. For this, parallelization takes place with reference to the blocks of a filter object type. Each work process processes one filter object block. You define the block size (that is, the maximum number of filter objects processed in each block). For more information, see Customizing for SAP ERP under Integration with Other mySAP.com Components Advanced Planning and Optimization Basic Settings for Data Transfer Initial Data Transfer Set Filter and Selection Block Size .



NoteThe performance of the initial data transfer is determined not only by parallelization, but also by the size of the filter object blocks. If you choose a large block size, it may be that the system forms only a small number of blocks within a filter object type. This means that only a small number of work processes are parallelized. In contrast, a higher degree of parallelization is possible for smaller block sizes, although only a small number of objects are transferred in each block. If you want to optimize the performance of the initial data transfer, you have to take into account both parallelization and the filter block size and adjust these according to the specific requirements of your system.

● Parallelized processing of multiple queues in the target systemThe target system processes several incoming queues in parallel in different work processes. In this case, the system uses a different queue name for each data block that is sent using qRFC. The queue name contains the number of this data block.Parallelized processing can result in a significant improvement in performance. As before, you use transaction CFC3 to specify the block size (that is, the maximum number of filter objects processed in each block).

Parallelized transfer is currently supported for the following object types:

● Material masters (in SAP APO only)● Production process models (in SAP APO only)● Sales orders (in SAP APO only)● All types of stock (in SAP APO only)● Planned orders and manufacturing orders (in SAP APO only)● Networks (in SAP APO only)● Maintenance orders (in SAP APO only)● Purchase orders and purchase requisitions (in SAP APO only)● Sources of supply (contracts, purchasing info records, scheduling agreements)● Batches (in SAP APO only)● Inspection lots (in SAP APO only)● Product data structure (PDS) (in SAP APO only)

To use parallelized data transfer for PDS, you have to activate the Enhanced Initial Data Transfer (CA_CIF_INILOAD_01) business function, which is available as of SAP ECC Enhancement Package 4.

NoteFor a parallelized initial data transfer, the sequence in which the integration models are activated is specified not by CIF, but exclusively by the time at which they are activated. For example, if a parallelized initial transfer of material masters and purchase requisitions is triggered, it may be the case that the material master data that is required for the transfer of purchase requisitions does not yet exist in the target system. It is therefore recommended that you only transfer transaction data once all the required master data has been successfully transferred.

Parallel postings to the same material/plant combination or resource can lead to a liveCache lock in the target system. In particular, this can be the case if two integration models for different object types (purchase requisitions and sales orders, for example) are activated in parallel and are both related to the same material/plant combination. This also applies to object types that contain subobjects, such as planned orders or manufacturing orders. As a result, you should ensure that integration models that are activated in parallel do not access the same material/plant combination at either header or subobject level or with reference to the resource used. Object types to bear in mind here are planned orders,


manufacturing orders, networks, and maintenance orders with the operation and component subobjects, subcontract orders and subcontract purchase requisitions, and stock transport orders and stock transport requisitions.

Activities

As standard, the initial data transfer is strictly serialized. To activate parallelized initial data transfer, do the following.

1. On the SAP Easy Access screen, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Activate or use transaction CFM2.

2. On the Activate or Deactivate Integration Model screen, select the Parallelize Selection in ERP System checkbox.

3. Select the Parallelize Processing in APO checkbox.

4.2.4.4 Change Transfer for Master Data

The change transfer for master data covers:

1. Creating new master data whose selection criteria match those of an active integration model, and then the subsequent transfer (see Initial Creation of Master Data [page 50] )

2. Making changes to master data and transferring them (see Changes to Master Data [page 53] )

For more information about the transfer of master data, see Integration of SCM Basis Master Data [page 214] .

4.2.4.4.1 Initial Creation of Master Data

You create new master data in the ERP system because this is the superordinate master data system. New master data objects with selection criteria that correspond to an integration model that already exists (for example, the same MRP type) are not automatically included in this integration model in the ERP system or transferred. There are two procedures available for making the transfer:

1. Periodic transfer using background processing2. Online transfer using Business Transfer Events (BTEs)

1. Periodic Transfer Using Background Processing

In this procedure, a new version of the corresponding integration model is created and activated for master data that has been created in the ERP system. Although this may be done manually, for performance reasons we recommend that you set up a periodic background job to run at times when the system load is at a low (for



example, at night). In the background job, the reports referred to below should run in sequence. This procedure offers the following advantages:

● Master data that has been created recently and that meets the selection criteria of integration models that already exist is included in these integration models and transferred to the target system.

● Master data that has been changed to such an extent that it no longer meets the selection criteria of the corresponding integration model is excluded from the transfer.

● Master data (material, customer, vendor, and source of supply) that has been changed since the last transfer is retransferred and will now be up-to-date.For more information, see Changes to Master Data [page 53] .

Procedure

1. Optionally, you can delete the old, inactive version of the integration model (report RIMODDEL).2. Create a new version of the corresponding integration model (report RIMODGEN).3. Activate the new version (report RIMODAC2, set the radio button Activate Newest Version ).4. The system automatically sets the old version as inactive.5. The system does not transfer all the data in the new version to the target system. Only the differences

between the old and new version (delta information) are transferred.

2. Online Transfer Using Business Transfer Events (BTEs)

As of SAP R/3 Plug-In 2000.2, you can create info objects in the ERP system that correspond to the selection criteria of an integration model that already exists and then immediately transfer them when they are posted. The system automatically creates a new version of the corresponding integration model and activates this in the background.

CautionThis procedure for the creation of new master data should only be used in exceptional cases. This can, in particular, lead to problems if dependent objects exist. In most cases, it is better to use a periodic transfer with background processing as described above. In particular, in cases where you are transferring large amounts of master data to an ERP system using ALE or batch input, the forwarding should be batch-controlled rather than batch-triggered.

Prerequisites

In the ERP system, business transaction events (BTEs) have been activated for the integration with CIF. For more information, see Activating BTEs for CIF Integration [page 30] .

Procedure

Make the following settings to change to online transfer:

1. Use transaction CFC9 to call the Change Target-System-Independent Settings in CIF screen. Under Change Transfer for Master Data , choose BTE Transfer, Immediately . As of SAP R/3 4.0B, you can make this setting in CIF Customizing in the ERP System [page 24] under Basic Settings for the Data TransferConfigure Change Transfer for Master Data .

2. Use transaction SM30 to call the Maintain Table Views: Initial Screen screen. Call table CIFIMODGEN. The Change View "Customizing Automatic Generation of Integration Models" screen appears. You determine the


procedure for adapting the integration model by making entries in this database table. The table contains the following columns:Connection Point : Contains one of six different possibilities:Creation of new material master data (MAT_INS)Changing of material master data (MAT_UPD)Creation of customer master data (CUS_INS)Changing of customer master data (CUS_UPD)Creation of vendor master data (VEN_INS)Changing of vendor master data (VEN_UPD)Program : Contains the name of an ABAP/4 program. This program is to be executed when one of these events occurs. In most cases, you should specify the standard program RIMODGEN for generating integration models.See below.Variant : Contains the name of a variant. This variant contains the input parameters of the given program.Counter : You can specify several program/variant combinations for the same connection point and determine their sequence using the Counter column.

The program RIMODGEN offers the following enhanced functions.

● An existing integration model can be selected● Filter objects can be inserted or deleted● The result can be saved as a new version of the integration model

In addition, the program evaluates the integration model key, the checkboxes for the filter objects, and the selection options for material, customer, and vendor. If the number of filter objects does not change, a new version is not created. If a new version is created, it is activated. That is, new objects are transferred, and the data flow is stopped for obsolete objects.

In the selection screen of program RIMODGEN, the Model Name , Target System , and Application fields are obligatory.

For materials, the selection options under Relevant Materials are evaluated and compared with the newly created or changed material. Besides the checkbox for material master, the following checkboxes are evaluated:

● Availability check● Sales orders (only SAP APO)● Purchase orders and purchase requisitions (only SAP APO)● Production orders and process orders (only SAP APO)● Planned orders (only SAP APO)● Manual reservations (only SAP APO)● Planned independent requirements (only SAP APO)● All types of stock (only SAP APO)● Consumption data (only SAP APO)

If the checkbox for production process models (PPMs) is marked, the selection options entered are used to carry out the selection in the database. The results are incorporated into the model. In the case of newly created materials, this selection provides no results, since a bill of material, routing, or production version does not yet exist. In the case of material changes, the selection can deliver valid PPMs. For PPMs, however, the current date enters the system in the form of the key date. Therefore, it is possible that a 'new' PPM is selected and transferred, even if nothing has changed in the bills of material, production version, or routing.

All other selection options (including special restrictions for material/plant for the individual documents) are not taken into account here.



In the case of customers, only selection options for customers and the Customer checkbox are taken into account. This is also the case for vendors.

The purpose of the extension CIFIMO01 (CIF-IMO-zero-one) with the module EXIT_RIMODGEN_001 is to influence the number of filter objects. This extension modifies the list of filter objects provided by the standard functions.

The process for automatically generating integration models runs in the background as a queued remote function call (qRFC). This means that you can use the qRFC monitor (transaction SMQ1) to test whether errors occurred. The queue name consists of the prefix CF_IMOD_ and the master data type, that is, T_MAT, T_CUS or T_VEN. Transaction SMQ1 provides the following functions:

● Restart● Debugging● Call deletion

If the CIF application log is activated, entries are written there. These entries are documented under the object CIF and the subobject IMOD. Detailed information about the automatic generation process and the activation of the model is located here.

For more information about the qRFC monitor and the CIF application log, see Monitoring .

4.2.4.4.2 Changes to Master Data In most cases, you make changes to master data in the ERP system because this is the superordinate system for master data. There are two different scenarios for this:

Changes to master data fields that are already contained in an active integration model

The ERP system marks these changes using change pointers (see Transfer of Data Changes Using ALE Change Pointers below).

When the integration model is activated, the system automatically evaluates all change pointers and transfers the corresponding master data records to the target system. Only the master data records that have been changed are transferred, not all of the data records that are contained in the integration model.

Changes to master data fields relevant to filtering

These changes mean that certain master data entries now fulfill the selection criteria of an integration model that already exists. Fields relevant to filtering are those that are given in the General Selection Options for Materials section of the selection screen for the integration model (material type, plant-specific material status, MRP controller, MRP type, and ABC indicator).

When creating a new version of the integration model, CIF transfers the master data record that now meets the selection criteria, including all dependent objects.

ExampleA material that previously had the MRP type PD and that was planned in the ERP system will, in the future, have the MRP type XO and will be planned in SAP APO. This change means that it now fulfils the selection criteria MRP Type XO of an integration model that already exists. The ERP system includes the material in this integration model and generates a new version of the integration model. When the integration model is activated, the material is transferred to SAP APO including all dependent objects such as stocks, orders, and so on.


This operation can influence performance. We therefore recommend that you use a periodic transfer using background processing at a time when the system load is low (for example, at night).

For more information about the periodic transfer using background processing and the online transfer using BTE, see Initial Creation of Master Data [page 50] .

For the transfer of data changes, you must differentiate between changes to:

● Material, customer, vendor, and source of supply● Production process model (only SAP APO)● Planning product and work center (only SAP APO)

Special cases to bear in mind for the transfer of changes to these object types are listed below.

Changes to Material, Customer, Vendor, and Setup Group Master Data and to Sources of Supply

Transfer of Data Changes Using ALE Change Pointers

If you change these master data objects in the ERP system, the system writes a note for ALE change pointers (ALE = Application Link Enabling). Here, message type CIFMAT stands for material, CIFCUS for customer, CIFVEN for vendor, and CIFSRC for source of supply.

As a prerequisite, change pointers must have been activated in CIF Customizing in the ERP System [page 24] . In addition, you must specify for which message types changes pointers should be written. To do this, make the following settings:

● In the CIF IMG, choose Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data Activate ALE Change Pointers Generally , or call transaction BD61. Set the relevant indicator.

● Then, in the IMG for CIF, choose Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data Activate ALE Change Pointers for Message Types , or call transaction BD50. Choose the relevant message types.

RecommendationSchedule background jobs in which the integration model is activated regularly (for example, at night). The change pointers will then be evaluated each time. This ensures that your master data in the target system is always up-to-date.

If you do not regularly activate the integration model and want to evaluate the change pointers, you can use report RCPTRAN4. Create a variant of this report containing the target system and the selection of master data objects. You can access this report using transaction CFP1 or in the SAP Menu by choosing

Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Change Transfer Master Data .

For the material, customer, vendor, and setup group master data (message types CIFMAT, CIFCUS, CIFVEN, and CIFSTG), you can also set the periodic transfer of change transfers by using transaction CFC9. In this case, change pointers must also be activated.



● In the IMG for CIF, choose Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data Configure the Change Transfer for Master Data, or call transaction CFC9.

● For the relevant object type, choose ALE Change Transfer, Periodic .

You can also use transaction BD52 to configure the master data fields with message type CIFMAT for which a change pointer should be set.

RecommendationALE change pointers are not deleted in SAP R/3 after the transfer of data changes. Instead, they are marked as Processed . To prevent a drop in system performance, we recommend that you delete ALE change pointers regularly using the relevant IMG activity in the CIF IMG ( Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data Reorganize ALE Change Pointers ) or by calling transaction BD61.

Online Transfer Using Business Transfer Events (BTEs)

As of SAP R/3 Plug-In 2000.2, you can transfer changes to material, customer, and vendor masters that are already contained in an active integration model to the target system as soon as they have been posted in the ERP system.

● In the IMG for CIF, choose Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data Configure the Change Transfer for Master Data, or call transaction CFC9.

● For the relevant message type, choose BTE Transfer, Immediately . In this case, the SAP R/3 system automatically sets the indicators for message types CIFCUS, CIFMAT, and CIFVEN to active.

For more information about the online transfer using BTE, see Initial Creation of Master Data [page 50] .

Changes to Production Process Models (only SAP APO)

You use transaction CFP3 (report RSPPMCHG) to transfer changes to production process models (PPMs). To find the report, on the SAP Easy Access screen, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Change TransferProduction Process Model .

During the transfer of data changes, the system overwrites the PPM that already exists in SAP APO. However, data that has been manually created in SAP APO and that is not contained in the Core Interface (CIF) is not overwritten.

The system writes a note when changes are made to bills of material (BOMs), routings, receipts, and production versions. Phantom assemblies (logical groupings of components) are an exception.

Changes that are relevant to scheduling (for example, changes to the duration of an operation) are taken into account in the transfer of data changes. The explosion date of the PPM must be set correspondingly. As of SAP R/3 Plug-In 2001.1, you are able not only to explode routings/BOMs according to the selection date entered (as before) but also according to the time of transfer and the start/end date of the production version. The selection date specified in the integration model is set as default. If the selection date lies in the past, any current changes will not be taken into account.

Locked production versions in the ERP system lead to a deactivation of the corresponding PPMs.


The system does not write change pointers if you change referenced objects at the work center (for example, formulas).

Only those operations and BOM components are transferred to SAP APO for which work centers or materials are contained in an active integration model.

For more information, see the SAP Library for SAP APO under Master Data Production Process Model, Production Data Structure, and iPPE.

Changes to PP/DS Production Data Structures (only SAP APO)

For more information, see the SAP Library for SAP APO under Master Data Production Process Model, Production Data Structure, and iPPE.

Changes to Planning Products, SAP R/3 Change Numbers, and Work Centers (only SAP APO)

To transfer changes to planning products or the relationships between a product and a planning product, or changes to ERP change numbers or work centers, we recommend that you create a background job with the following reports that is scheduled to run at night:

1. Optionally, you can delete the old version of the integration model (report RIMODDEL).2. Start the initial data transfer (report RIMODINI, set the Set to Active indicator )3. Generate the (new version of the) integration model (report RIMODGEN)4. Activate integration model (report RIMODAC2, activate the Activate Newest Version radio button)

4.2.4.5 Search Functions

Use

The Core Interface [page 23] is equipped with two search functions and one delete function.

Prerequisites

Generation and activation of the appropriate integration model.



Features

● Display integration models [page 57]● Find filter objects [page 58]● Delete integration models [page 59]

4.2.4.5.1 Displaying Integration Models

Use

You can display the integration models that have already been generated. As the result, a selection table is displayed that contains the following information:

● A list of all existing integration models in alphabetical order● The appropriate logical target system for each model● An indicator displaying whether the integration model is active or inactive.

Prerequisites

The Customizing and default settings for integration must be maintained in both the source system and the target system. The relationship between the source and target system must be maintained in each system application log.

See Checklist for Setting Up the System Infrastructure [page 28]

Procedure

1. For SAP R/3 3.1I - 4.5B, open the CIF area menu. Choose Integration Model Display.As of SAP R/3 4.6B, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Display .You can also call up this report (RIMODOUT) using transaction CFM4.The Display Integration Models screen appears.

2. Selection

Choose the integration model to be displayed according to the following selection criteria:

● Model● Logical system● APO application● Creation date● Creation time


● Created by● Only active models

If this indicator is selected, only active models are displayed in the results list.

NoteThe above selection criteria are optional entries. The report can be started even if only one criterion is defined. You can use the Selection Options pushbutton to further restrict the selection criteria.

The selection screen displays all models that the system found for the specified criteria.

You can use the Details pushbutton to view the material/plant combinations for a selected filter object.

4.2.4.5.2 Finding Filter Objects

Use

You can search for specific filter objects in integration models.

ExampleWhich materials are available in which plant.

Prerequisites

To be able to find relevant filter objects, at least one integration model [page 37] must be generated (RIMODGEN) and activated (RIMODACT) (see Generating Integration Models [page 38] and Activation and Deactivation of Integration Models [page 41] ).

Procedure

1. For SAP R/3 3.1I - 4.5B, open the CIF area menu (transaction CIF). Choose Integration Model Filter Object Search.

As of SAP R/3 4.6B, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Filter Object Search.You can also call report RIMODSRH using transaction CFM5.The Search for Filter Objects in Integration Models screen appears.When selecting the procedure for Generating Integration Models [page 38] , select the types of filter objects and use selection options to restrict the search if necessary.

2. ResultThe system displays a list of all filter objects that correspond to your selection criteria.



You can use the Details pushbutton to navigate to the list of material/plant combinations for the filter object type selected.You can use the Models pushbutton to display the integration model in which the selected material/plant combination already exists, and to see which activity mode is valid.

4.2.4.5.3 Deleting Integration Models

Use

You can delete deactivated integration models. Deactivated integration models are not deleted automatically.

We recommend that you regularly delete inactive integration models for performance reasons.

Prerequisites

The integration model must be deactivated before it is deleted (RIMODACT).

See Activation and Deactivation of Integration Models [page 41]

Procedure

For SAP R/3 3.1I - 4.5B, open the CIF area menu (transaction CIF). Choose Integration Model → Delete.

As of SAP R/3 4.6B, choose Logistics → Central Functions → Supply Chain Planning Interface → Core Interface Advanced Planner and Optimizer → Integration Model →Delete.

You can also call this report (RIMODDEL) using transaction CFM7.

The Delete Integration Model screen appears.

Select an integration model based on the following selection criteria:

Model

Logical system

Application

Creation date

Creation time

Created by


The above selection criteria are optional entries. The report can be started even if only one criterion is defined. You can use the Selection Options pushbutton to further restrict the selection criteria.

The system displays a warning message if you try to include active integration models in your selection. Select again. You can only proceed to the actual deletion stage if your selection includes inactive integration models only.

Choose the Delete pushbutton. A message appears to confirm that the deletion was successful. All integration models shown in the results list are deleted.

4.2.5 Administration

Use

The following tools are available for monitoring the data transfer via Core Interface (CIF):

● Application log [page 63]● qRFC monitor [page 61]

For more information about the effects of the serialized transfer via CIF, see Serialization Effect [page 60] .

4.2.5.1 Serialization Effect

This is a potential consequence of a faulty queue entry during a data transfer using queued remote function calls (qRFC). When using qRFCs for a data transfer, the system adheres strictly to the sequence of objects to be transferred (serialization), in contrast to the transfer using transactional remote function calls (tRFC).

Serialization also applies if queue entries from different logical units of work (LUWs) are being processed in this queue. For example, this could be the case if a number of changes are made for an order in the ERP system at different points in time. The changes are in the same queue due to the queue name and they are therefore subject to serialization. However, since the postings took place at different points in time, the corresponding queue entries are in different LUWs.

If a queue contains a faulty queue entry, the subsequent queue entries are not transferred either. This leads to a queue block. A queue block not only affects the LUW containing the faulty queue entry, but also all LUWs containing subsequent queue entries. This effect is called the serialization effect.

Example

A confirmation is issued for a production order with goods movement. This affects the material ROH1. The action leads to the following entries:

LUW 1

CFPLO 0815 xxxxxx



CFRSV ROH1

CFSTK ROH1

The first entry in LUW 1 is faulty and is not transferred. This also blocks the subsequent entries in this LUW.

Shortly afterwards, a goods issue is posted for delivery that also concerns material ROH1. The action leads to the following entries:

LUW 2

CFSLS 4711

CFSTK ROH1

CFSTK ROH2

CFSTK ROH3

Entries with the same queue names (in this case CFSTK ROH1) may only be transferred in serial. This means that entry CFSTK ROH1 in LUW 2 cannot be transferred if entry CFSTK ROH1 is blocked in LUW1. All entries in LUW 2 are also blocked.

4.2.5.2 qRFC Monitor

Use

Communication between the ERP system and the SCM system is based on the asynchronous transfer technique queued Remote Function Call (qRFC) . This technique is used for both the initial data transfer and the transfer of data changes. If your SCM system is SAP Advanced Planning and Optimization (SAP APO), it is also used to publish planning results from SAP APO to the ERP system.

The data is first buffered by the sending system and then transferred to the target system (outbound queue), or it is transferred from the sending system and then buffered by the target system (inbound queue).

The advantage here is that the sending system does not have to wait for the update to be completed in the target system. However, return parameters cannot be delivered which means that potential error messages cannot be returned directly to the component.

The system differentiates between two types of error when processing qRFC modules:

1. Communication errors. These include:○ Network problems○ Non-existent RFC destination, etc.○ Blocked objects (is dealt with as a communication error)

As soon as the network connection is available again, a periodic repetition of the data transfer should solve communication problems.


2. Application errors. These include:○ Program errors○ Missing posting of data to the target system○ Missing master data for transaction data (only SAP APO)

Application problems cannot be solved by the system itself and must be dealt with by a system administrator.

The qRFC monitor is used to monitor application errors in inbound and outbound queues. It is available in both the ERP system and the SCM system. All transfer channels (queues) are displayed for all target systems.

Integration

The technical name for all transfer channels relevant to the CIF integration starts with CF.

ExampleCF_ADC_LOAD - the name of the transfer channel for the initial data supply.

CFSLS0000010003 - the name of the change transfer for the sales order number 10003

Prerequisites

Generation and activation of at least one integration model.

NoteEnsure that you have maintained the settings for RFC destination (including the settings under TRFC Options ).

For more information, see Defining the RFC Destination [page 31] .

Features

To start the qRFC monitor for outbound queues, call transaction SMQ1 (report RSTRFCM1) or, on the SAP Easy Access screen, choose APO Administration Integration Monitor qRFC Monitor (Outbound Queues) .

To start the qRFC monitor for inbound queues, call transaction SMQ2 or, on the SAP Easy Access screen, choose APO Administration Integration Monitor qRFC Monitor (Inbound Queues) .

Transfer errors in the initial data supply are recognized automatically and a dialog box appears that you can use to access the qRFC monitor.

In the case of the online transfer, this does not happen automatically, which means that if data is not transferred, you must check for entries that are marked red in the qRFC monitor of the sending system. (If you work with SAP APO, this check can be performed automatically by the qRFC alert.)



You can double-click the rows to display all the function calls for the selected transfer channel. The highest function call blocks all other entries if an error occurs.

You can call the current status text via the error short text. A detailed error log is always saved in the application log of the target system.

Automatic navigation is supported from the qRFC monitor to the affected application log. See also SAP Notes 396838 and 396839.

See Displaying Entries in Application Log [page 63] .

If you work with bgRFC, you can use the bgRFC monitor (transaction SBGRFCMON in the ERP system and SBGRFCMON1 in the SCM system).

4.2.5.3 Application Log

The application log records data transfers. This allows you to trace who (user) transferred what (data object and integration model) and when (date/time). The application log provides a detailed error message for queues with errors.

The application log can be called in both the SCM system and the ERP system.

For more information, see:

● Activation of Logging [page 67]● Displaying Entries in the Application Log [page 63]● Deleting Entries in the Application Log [page 64]● Finding Entries in the Application Log [page 65]

4.2.5.3.1 Displaying Entries in the Application Log

Use

You can use the evaluation of the application log to find out who (user) transferred what (data objects and integration models) when (at what time). In the case of errors, the application log also provides a detailed error message.

You call the Evaluate Application Log screen as follows:

1. In the ERP system:For SAP R/3 3.1I - 4.5B in the CIF area menu under Monitoring Application Log Display Entries or using transaction CFG1.As of SAP R/3 4.6B, on the SAP Easy Access screen, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Monitoring Application Log

Display Entries or using transaction CFG1.2. In the SCM system:

On the SAP Easy Access screen for SCM Basis, choose Integration Monitor Application Log Display Entries .


Prerequisites

● Logging is activated (see also Activation of Logging [page 67] )● At least one active integration model exists.

Selection

● ObjectCIF is entered here by default.

● SubobjectHere you can use the input help to select a certain object type such as ORDER (planned order/manufacturing order) for which you want to see the transfer logs.

NoteFor performance reasons, in the case of initial transfer and incremental transfer of master data, the entries are grouped together under the subobject INITIAL.

Result

By double-clicking a subobject, you can navigate to the messages for each transfer log. This enables you to see what data objects were transferred between the systems. This function is particularly useful for determining errors.

The transaction ID of the sending system (field TID in the qRFC row of the qRFC monitor of the sending system) is used as the key for error messages. Using this number, you can display all messages for this qRFC call in the target system.

Enter the number of the transaction ID in the External ID field and choose Execute . This displays all messages for the call.

For more information, see qRFC Monitor [page 61] .

4.2.5.3.2 Deleting Entries in the Application Log

Use

The records in the application log are not automatically deleted by the system. To prevent the database from overflowing, we recommend that you delete the records at regular intervals.

If required, you can also schedule a background job to perform this task.

In the ERP System

In the ERP system, you can use the report RDELALOG to delete records from the application log. As a prerequisite, your release must have a Core Interface.



To delete entries, use transaction CFGD or:

● For SAP R/3 3.1I - 4.5B, in the CIF area menu, choose Monitoring Application Log Delete Entries .

● As of SAP R/3 4.6B, on the SAP Easy Access screen, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Monitoring Application Log

Delete Entries .

In the SCM System

In the SCM system, you can use the report /SAPAPO/RDELALOG to delete records from the application log.

To delete entries, use transaction /SAPAPO/C6 or in the SCM Basis menu, choose Integration MonitorApplication Log Delete Entries.

If you do not make any entries in the date and time fields, all records that are older than one week are automatically deleted.

NoteIn both the SCM system and the ERP system (as of SAP R/3 4.6), you can also use transaction SLG2 to delete the logs.

4.2.5.3.3 Finding Entries in the Application Log

Use

This program allows you to search for any character strings, for example, order numbers, in the transfer logs of the CIF application log. In this way, you can track when an order, for example, was exchanged between the systems and what the status was.

This program lists all the logs in which the character string entered, for example, a certain order number, occurs. The program only displays one message for each log. By double-clicking a log, you get a list of all the messages available for this log, and can analyze the logs further.

Prerequisites

In order for the system to display messages for a transfer log, you must set logging [page 67] to Detailed .


Features

You can use the following selection options to restrict the search in the application log and thereby improve performance:

● ObjectCIF is entered here by default.

● SubobjectIf you search for transfer logs that were generated for a certain object type, for example, ORDER (planned order/production order), you can enter these here. Restricting the search to a subobject improves performance considerably.

● External identificationHere you can enter the key of the transfer log to be found. In the case of logs for initial data transfers, this key can be a number beginning with CIFLOAD. In the case of transfers from SAP APO, for example, this key can be a transaction ID.

● Time restriction○ From date/time

Here you can specify a date and/or time from which the system is to search for transfer logs.○ To date/time

Here you can specify a date and/or time up to which the system is to search for transfer logs.The current date from 00:00 to 23:59 is entered by default. Restricting the search in this way improves performance considerably.

● Restriction to a message of a message class generated for a transfer logHere you can first choose the required message class using the input help. The system then displays all the available messages for this message class in the input help for the message. In this way, you can search for an object in a certain situation.

● Character strings to be found○ Character string 1

If you enter a character string here, the system only displays those transfer logs that correspond to the selection criteria specified above and whose message text contains this character string.

○ and character string 2If you enter a character string here, the system only displays those transfer logs that correspond to the selection criteria specified above and whose message text contains both character strings 1 and 2.The use of placeholders (* or ?) can have a negative effect on performance.

● Display optionsHere you can configure whether messages available for a transfer log are displayed in a dialog box or on the full screen.

Activities

1. In the ERP system, you can find this program in the SAP menu under Logistics Central FunctionsSupply Chain Planning Interface Core Interface Advanced Planner and Optimizer MonitoringApplication Log Find Entries or using transaction CFG3.

2. In the SCM system, you can find this program in the SAP menu under Integration MonitorApplication Log Find Entries or using transaction /SAPAPO/C7.



4.2.5.3.4 Activation of Logging

Purpose

Every transfer can be logged in a user-specific way. You can choose between three different settings for logging:

● No logging● Standard (only the number of transferred data records is logged)● Detailed (number and content of the transferred data records are logged)

NoteFor performance reasons, we recommend that you archive regularly if the detailed logging setting is used.

The entries can be deleted using the report RDELALOG.

For more information, see Displaying Entries in the Application Log [page 63] and Deleting Entries in the Application Log [page 64] .

Process

Settings in the ERP System

1. For SAP R/3 3.1I to 4.5B, choose Settings User Parameters via the CIF area menu.As of SAP R/3 4.6B, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Settings User Parameters .

2. The Change View "Maintenance View for CIFGPARAMS": Overview screen appears.3. Under Logging , make the required settings.

Settings in the SCM System

1. In the SCM Basis menu, choose Integration Monitor Application Log Activate Logging .2. The Change View "Activate/Deactivate Maintenance View for Logging": Overview screen appears.3. Under Logging , make the required settings.

CautionDetailed logging can result in large database tables and a loss in performance in productive operation. You should, therefore, only carry out detailed logging when the data is genuinely required. We recommend that you archive the logs regularly.


4.2.6 Troubleshooting Guide

This document is intended to help you to localize and solve problems that arise during integration via Core Interface (CIF). It covers the following topics:

● Data Transfer Technique [page 68]● Prerequisites for Data Transfer [page 69]● Systematic Problem Analysis [page 70]

The Troubleshooting Guide is a supplement to the documentation for integration via CIF. It is aimed at users who already have a basic knowledge of CIF and who work with systems that have been set up.

4.2.6.1 Data Transfer Technique

Data is transferred in both directions by means of one or more queued Remote Function Calls (qRFC). The names of the function modules to be called and the relevant transfer parameters are first buffered on the database before being executed asynchronously in the sequence that they were called.

There are two types of buffering:

1. Outbound qRFC. The data is saved temporarily on the database of the sending system.2. Inbound qRFC. The data is saved temporarily on the database of the receiving system.

Each function module call must be attributed with one or more queue names. Using the same queue name for different calls means that these calls must be executed in a serialized way. If the queue names are different, no sequence has been defined for relevant calls, and the calls can be executed either independently one after the other, or at the same time. Depending on the application case, serialization may be necessary for consistency reasons.

Multiple qRFCs can be combined into a logical unit of work (LUW), whereby one LUW on the sending side results in one LUW on the receiving side.

Schematic Presentation of LUWs

This means, on the one hand, that each individual function call into a target system is serialized with other calls by means of its queue name. On the other hand, multiple calls in the sending system can be combined into one



LUW independently of the queue names. These calls are also executed in the target system within one LUW. By using the same queue names in calls with different LUWs, these LUWs are serialized among one another. At the end of an LUW in the target system, qRFC management triggers a COMMIT or, in the case of an error, a ROLLBACK. If an error occurs, the LUW gets an error status, but all the call data remains on the database. By using the qRFC technique you can therefore allow the processing of saved function calls to continue after you have corrected a problem without generating data inconsistencies.

Changes to production orders in the ERP system are an example of serialization using queues.Here the use of identical queue names ensures that older data does not overwrite newer data and that the SCM system does not contain obsolete data.

Goods receipt for a purchase order is an example of combining function calls within a process as an LUW. The use of one LUW ensures that stock posting can only be updated when the purchase order is changed in the SCM system. Since in this case more than one queue is used, it must be possible to process all the queues used in the LUW, that is, they must not be blocked, before this LUW can be processed.

When a queue cannot be processed, the problem could be due to technical connection errors (status CPICERR or RETRY) or to errors triggered by the application (status SYSFAIL), for example. Moreover, the user can stop and start specific queues in qRFC transactions, if necessary. In the case of CPICERR/RETRY, the data can, in most cases, be transferred successfully after the connection error has been rectified and the function calls have been executed again. However, in the case of an application error, a more detailed analysis is required. It could be that the function call does not run correctly in the target system with the conditions specified. In rare cases, you may need to manually delete an LUW to allow data that is following it to be processed. This could result in inconsistencies that can be rectified with suitable measures. The measure to be taken depends to a large extent on the problem that has occurred. For this reason standard solutions are not possible. One measure that proves suitable in many cases is the CIF comparison/reconciliation of transaction data (transaction /SAPAPO/CCR). This function is only available if you work with SAP APO.

4.2.6.2 Prerequisites for Data Transfer

Since, in most cases, data is transferred asynchronously and in the background, the system cannot issue error messages directly to the user. For this reason, entries are made in the SAP application log under the object CIF and various subobjects in the systems involved.

To make it easier to search any errors that might have occurred, you should therefore activate the CIF application log on both sides, at least during the setup and test phases.

● Set the Logging parameter to D in transaction CFC2 in the ERP system.● Set the Logging parameter to Detailed in transaction /SAPAPO/C4 in the SCM system.

Note that you can configure the control parameters for writing the application log in a user-specific way. If you enter * as the user name, the entry has an effect on all users whose identification is not entered explicitly in the transaction.

To connect your ERP system to the SCM system, you may need to make additional settings with regard to defining RFC destinations (transaction SM59) in both systems.

● If you want the ATP check to be performed in the SCM system but triggered from the ERP system, make sure when defining the RFC connection for the SCM system in the ERP system that you use a user ID for the SCM system that was created there as a dialog user.

● To be able, in special cases, to execute calls in one of the systems within the debugger, the RFC user used must also have debugging authorization.


● If connection errors or lock problems occur in a target system, use transaction SM59 in the sending system to configure the settings for the target system in such a way that the system automatically repeats unsuccessful calls after a certain period of time. You can do this in the detailed view of an RFC destination under the menu option tRFC Options . It has proven successful to set the Connection Attempts to 10 and the pause between attempts to 2 . These settings mean that calls that could not be processed successfully due to technical connection errors or locks, in SAP liveCache for example, are executed again after 2 minutes. If the errors occur again, up to 10 more attempts are made to execute the call.

● If you want a qRFC to be retained for debugging and not executed immediately by qRFC administration, you can set the parameter Debug to R in transaction CFC2 in the ERP system and to Debugging On/Recording of t/qRFCs (NOSENDS) in transaction /SAPAPO/C4 in the SCM system.

Up to and including SAP APO 3.1, the same RFC destination is used for all calls from SAP R/3 to SAP APO and vice versa. All necessary user authorizations must therefore be effective for this RFC destination. As of SAP APO 4.0, the concept of flexible RFC destinations is in place. This means that special RFC destinations are used for dialog application cases (ATP check, debugging, and so on). This offers a better and more secure way to control the authorizations to be granted. For more information, see the CIF Customizing in the SCM system under Basic Settings for Creating the System Landscape Assign RFC Destinations to Various Application Cases.

4.2.6.3 Systematic Problem Analysis

The following information is only relevant if your SCM system is SAP Advanced Planning and Optimiza tion (SAP APO).

If certain data objects arrived incorrectly in the target system or did not arrive at all, you can perform a systematic analysis of the problem.

The following figures provide an overview of systematic problem analysis:

Problem Analysis for Online Transfer of Transaction Data to SAP APO




Problem Analysis for Initial Data Transfer of Master and Transaction Data to SAP APO




Transfer from SAP R/3 to SAP APO

Is the data saved under a different name in SAP APO?

Note that in the case of master data a distinction is made between external keys, that is, keys in SAP R/3, and SAP APO names. The name in SAP APO does not have to be same as in SAP R/3. Depending on the scenario, you may need to modify the SAP R/3 names so that you can uniquely identify different objects in SAP APO. In most cases, you do this using customer functions in SAP APO inbound. If in doubt, check whether a customer function that uses a modified SAP R/3 key as the SAP APO name is active. If this is the case, you must take it into account when searching for objects. In the case of products, the database table for the assignment between SAP R/3 and SAP APO names is /SAPAPO/MATMAP, for locations it is /SAPAPO/LOCMAP, and for resources it is /SAPAPO/RESKEY.

Is the data in the CIF application log of SAP R/3 (transaction CFG1)?

Check the appropriate application log subobjects for the data object, and the date and time of the transfer. For an initial data transfer, you can restrict the check to subobject INITIAL. The application log is written immediately after the function module responsible for the individual object type has sent its data to SAP APO by means of a qRFC call. The name of the function module used, for example, CIF_STOCK_SEND provides information about the object type.

You can define the fields that are logged in the CIF application log for each of the SEND modules. You do this by using transaction CFC6 and entering the module name. SAP delivers one presetting. In most cases, one line is included with administrative data, for example, the names of the systems involved, the user and transaction names, and so on.The keys, for example, the document numbers as well as the transfer methods, for example, N for Create new, should be included in the application log. You can use this method to quickly check whether a particular SAP R/3 document is relevant to SAP APO and was therefore added to a queue. If this is not the case, it could be that integration models were constructed and activated incorrectly.

You can use the filter object search (transaction CFM5) to determine whether a particular filter object occurs in integration models and whether these integration models are active.

Are there entries in the qRFC monitor (transaction SMQ1 or SMQ2)?

You can set up either outbound queues or inbound queues for using qRFCs. In SAP R/3, you do this in transaction CFC1. If outbound queues are set up, you must use transaction SMQ1 in SAP R/3 as the qRFC monitor. If the queue type is set to inbound queue, in most cases you use transaction SMQ2 in SAP APO as the qRFC monitor.

If problems occur with the network connection, it can be the case that the data cannot be sent to SAP APO. In this case, you can find the data in transaction SMQ1 in the sending SAP R/3 system. The names of the queues used by CIF all begin with CF so that you can restrict your selection to these. In the detailed display of function module calls, you can use the separators to tell which calls belong to the same LUW. You can see a restricted view of the data by double-clicking the function name.

Various statuses are possible for the queues: Recorded means that this call is not yet waiting to be processed. In most cases, this means that processing of a call linked to it by the LUWs and queues has not been completed or ended in an error. An LUW can only be started when all queues contained within it are waiting for processing. An error in one of the queues involved prevents the entire LUW from being started. This can then also block other queues. This means that a few errors can block many queues and thereby restrict data transfer.

In most cases, the status CPICERR means that a technical connection problem has occurred during the transfer. In this case, if the appropriate setting has been made, the qRFC administration attempts to repeat the call after a certain period of time. In the case of outbound queues, you can configure the parameters that do



this in the sending system in transaction SM59 under tRFC Options . In the case of inbound queues, you can make these settings in the receiving system in transaction SMQR.

The status RETRY means that the application has deliberately requested that this LUW is reprocessed at a later time and not that a technical connection problem has occurred. In the majority of cases, this is the result of SAP liveCache locks when a CIF LUW wants to process data that is already locked by another LUW (CIF or not). The system recognizes this. As a result, the system re-executes the function calls for this LUW at a later point in time.

If one of the calls in the target system ends in errors, the entire LUW gets the status SYSFAIL. You can find a one-line error message in the status text in SMQ1 or SMQ2. In most cases, the application log of the SAP APO target system contains more information than the text in the qRFC monitor (see next paragraph).

Are there entries in the SAP APO application log (transaction /SAPAPO/C3)?

The CIF application log in SAP APO shows the result messages for the routines that transfer the data into SAP APO, grouped by object CIF and various subobjects. Even if no errors have occurred, you can tell which data has arrived in which target system. If the document numbers that you are looking for appear here and have not produced any errors, you can assume that CIF has correctly transferred the data to the SAP APO system. In this case, any problems that do occur are most likely to be due to the application.

If the application log is activated but does not contain any entries, it is highly likely that the data was not sent from SAP R/3. Even if faulty entries have been deleted in transaction SMQ1 in SAP R/3, application logs that have already been written are kept and can be used to draw conclusions about the data transfer. You can assign a faulty entry in transaction SMQ1 in SAP R/3 to the appropriate application log by means of the transaction ID. This is displayed in SMQ1 and can be copied to the selection screen of the application log transaction. Unlike in SAP R/3, you cannot configure which particular fields are to be logged in the application log in SAP APO. This selection is predefined.

Transfer from SAP APO to SAP R/3

The procedure for analyzing problems for the transfer from SAP APO to SAP R/3 is more or less the same as that for the transfer from SAP R/3 to SAP APO. You should first check the application log in SAP APO to ensure that SAP APO has triggered a transfer and that the data was placed into one or more queues. If this is not case, the problem could be due to incorrectly maintained distribution criteria (transaction /SAPAPO/CP1 or /SAPAPO/CP2). If the entries exist, you should next use the qRFC monitor (SMQ1 in SAP APO or SMQ2 in SAP R/3) to localize any problems. If you do not find any faulty or unprocessed queue entries in the qRFC monitor, check whether there are any entries for the orders to be checked in the SAP R/3 application log. Here you can also assign faulty queue entries in transaction SMQ1 by means of the transaction ID. The successful transfer of data to SAP R/3 indicates that CIF processing was correct. In this case, the problems were most likely to have been caused by the application and not CIF.


5 SCM Basis Master Data

Purpose

The master data of SCM Basis can be used in all SAP applications containing SCM Basis, such as SAP Supply Network Collaboration (SAP SNC) and Transportation Management (TM) .

Integration

If you are using an ERP system as the master data system, you can transfer the master data to SCM Basis via the Core Interface (CIF). For more information, see Integration of SCM Basis Master Data [page 214] .

Features

The master data of SCM Basis are listed in the following. For more information, see the documentation on the individual types of master data.

You can create, display, change, or delete master data. In the case of certain master data, further general master data functions [page 195] are available.

5.1 Location

Definition

A logical or physical place at which products or resources are managed on a quantity basis.

Locations belong to a certain location type. Examples of location types are production plant, distribution center, supplier, and customer.

Use

For information enabling you to set up the location master data maintenance display on a user-specific basis by suppressing individual tab pages, see User-Specific Display Profiles for Master Data Maintenance [page 212] .

For information on logging changes for location master data, see Change Logging for Master Data [page 211] .


SCM Basis Master Data

For information on the where-used list for location master data, see Where-Used List for Master Data [page 207] .

5.1.1 Display, Create, and Change Location

Use

In location master maintenance, you can display, create, and change the master data for a location.

Procedure

1. From the SCM Basis menu, choose Master Data Location . The Location Master Data: Initial Screen appears

2. Enter a location number and a location type. Location types are predefined.

NoteWhen you first choose a location type, the input help for the Location field shows you all already existing locations of this location type.

Choose:

○ Display, to view an already created location○ Change, to change an already created location○ Create, to create a new location○ Set Planning Version, to set a planning version for a location. The system sets the active planning version

000 by default.○ Assign Model,to assign one or more supply chain models to a location.

3. The screen for the selected location appears.4. Choose a tab page and enter the relevant data in the fields. You can choose from the tab pages listed in the

table for the tab pages of the location master.5. On each tab page, choose Save when you have finished entering your data.

Tab Pages of the Location Master

Tab Page Function What You Should Know

General Maintain general data For more information about maintaining geographical data, see Display and Maintenance of Geographical Data [page 79].

Address Maintain address data

SCM BasisSCM Basis Master Data P U B L I C 77

Tab Page Function What You Should Know

Calendar Maintain calendar data

TP/VS Maintain data for Transportation Planning/Vehicle Scheduling

Resources Maintain resource data

VMI General Maintain general data for Vendor-Managed Inventory

VMI Customer Maintain customer data for Vendor-Managed Inventory

This tab page is displayed for the location type 1010 Customer only.

SNP Maintain customer data for SAP Supply Network Planning

Additional Data Maintain additional fields The fields on the Additional Data tab page are fields that are not available in the standard system and which must first be released in Customizing. To do so, in the Implementation Guide,

choose SCM Basis Master Data

Define Free Attributes.

Storage Locations Maintain data for Storage Location MRP Areas

This tab page is displayed for the location type 1007 Storage Location MRP Area only.

TSP Maintain data for carriers This tab page is displayed for the location type 1020 Transportation Service Provider only.

ATP Maintain data for Available-to-Promise.

F&R Maintain data for SAP Forecasting and Replenishment

SPP Maintain data for Service Parts Planning

More Information

For more information about locations, see Location [page 76].

For information about deleting a location, see Delete Location [page 80].



5.1.1.1 Display and Maintenance of Geographical Data

Use

For information purposes, you can use this function to display and maintain geographical data on the General Data tab page of the location master. The system displays those geocoordinates here that it has calculated using the geocoding framework. You can display additional geocoordinates on the basis of geocoordinate determination strategies, for example if you want to know the geocoordinates of a location on house number level, postal code level, or regional level.

The system displays the geographical data on the basis of the following elements:

● Latitude● Longitude● Altitude● Time Zone● Precision

To use additional geocoordinates and the geocoding framework, you must have activated the business function Enhanced Services for Transportation Network [page 14]( SCM_SCMB_TR_NETWORK).

Prerequisites

To display additional geocoordinates based on DDD strategies, you have defined the following in Customizing for SCM Basis:

● You have defined strategies in the process controller under Process Controller Define Strategy .

● You have defined geocoding levels under Master Data Location Geocoding Define Geocoding Levels .

Features

Maintain Geographical Data

You can modify the geographical data for correction purposes, for example to manually adjust the data and make it more precise. If you modify the geographical data, the system also reflects the changes in the additional geocoordinates.

NoteOnly the additional geocoordinates with the lowest geocoding level reflect the changes.

Maintain Additional Geocoordinates

For the geocoordinates that system has determined on the basis of the geocoordinate strategies, you can recalculate values or clear values. You recalculate values for example, if you have modified the geographical data and want new values for the geocoordinates of a specific geocoordinate strategy.


NoteYou cannot make manual changes to the additional geocoordinates.

Activities

To display and maintain geographical data, on the SAP Easy Access screen, choose SCM Basis Master DataLocation Location .

More Information

For more information about locations, see Location [page 76].

For more information about geocoding, see Geocoding [page 94].

5.1.2 Delete Location

Use

If you wish to delete a location, first set the deletion flag before finally deleting the location in a second step. In this way you can schedule the actual deletion process for a later point in time, not just for a single location but for several. You can carry out the delete operation in the background.

Prerequisites

The general prerequisites for the deletion of master data [page 206] apply.

You have eliminated any still-existent dependencies [page 208] involving this location. Possible dependent objects include ATP assignments or a product, model, or resource assignment, for example.

For more information, refer to SAP Note 572579.

To clarify existing dependencies, you can generate a where-used list [page 207] for the location that is to be deleted.



Procedure

1. On the Location Master: Initialscreen, choose a location and then chooseLocation Deletion Flag .On the following screen, set the deletion flag for the location and choose Save .

NoteYou can remove the deletion flag by unsetting the indicator for the relevant location.

○ Choose Extras Delete Locations, to finally delete one or more locations that have been flagged for deletion. You can either perform the deletion immediately or schedule it for a later point in time.

5.1.3 ILM-related Information for SCM Location (SCMB_LOC)

Use

To create and use policies and rules for the SCM Location in Retention Management, an ILM object SCMB_LOC is available. ILM object SCMB_LOC is based on destruction object /SCMB/LOC.

The data destruction object /SCMB/LOC is assigned to data destruction program /SCMB/RLOC_DEL.

Prerequisites

● You have activated the business function Activating SAP ILM ( ILM)

Features

Tables from which data records are destroyed for destruction object /SCMB/LOC:

Table Table name

/SAPAPO/LOC Locations

/SAPAPO/LOCMAP Mapping Table for Locations

/SAPAPO/LOCT Short Text for Locations

/SCMB/LOCID_MAP LOCID mapping table X16<->C22

/SAPAPO/LOCVER Location: Version-Dependent Fields

/SAPAPO/LOCCOMP Table Obsolete Since SCM Release 4.1

/SAPAPO/LOC_SUB Mapping Table for Sublocations

/SAPAPO/LTTYPE Location Resources

/SAPAPO/LTVER Location Resources: Version-Dependent Fields


Table Table name

/SAPAPO/LOCALID Alternative Identifiers for Locations

/SAPAPO/LOC_EQUI Equipment for Locations

/SAPAPO/LOCGC Location Geo Coordinates per GeoCoding Level

/SAPAPO/LOCSIM Location version dependent fields

/SAPAPO/TRMCARR Transportation Service Provider at Transportation Lanes

/SAPAPO/SUBLOC1 Sublocations in APO

/SAPAPO/SUBLOCT Descriptions of the Storage Locations

Condition Fields and Time References for ILM Object SCMB_LOC

The fields for ILM object SCMB_LOC for defining ILM policies are:

● Available Condition Fields○ APPL_NAME - Application Name○ APPL_RULE_VARIANT - Application Rule Variant○ BUKRS - Company Code○ EOP_LOC_TYPE - Location Type

● Available Time References + Available Time Offsets○ LAST_CHANGE_DATE - Last Changed On

○ END_OF_YEAR - End of Year○ START_RET_DATE - Start of Retention Period

● Available Standard Condition Fields○ SCM_COUNTRY_OF_BUKRS - Standard Field Country from Company Code - SCMB

Available Policy Categories

● RST: Residence Rules● RTP: Retention Rules

The condition fields BUKRS and SCM_COUNTRY_OF_BUKRS apply only for locations of type production plant (1001) that were transferred from ERP, as company code mapping is available in SCM only for this location type.

In the ERP system, SAP Note 2156214 (or the corresponding Support Package) must be implemented.

The residence rules, time reference START_RET_DATE and condition fields APPL_NAME and APPL_RULE_VARIANT are only used in connection with Simplified Blocking and Deletion of SCM Locations - see SAP Note 2249093 for details. Time reference START_RET_DATE applies only to location types that can be used in report /SCMB/RLOC_PREPARE_EOP ( Block Location Master Data). For other location types, START_RET_DATE is not relevant.





Procedure

Finding Data Destruction Objects

To find data destruction object /SCMB/LOC, proceed as follows:

1. Execute transaction DOBJ.2. To search for the data destruction object, choose Position.3. Double-click data destruction object /SCMB/LOC to view more information such as the data destruction

program and the component.4. In the dialog structure, double-click Structure Definition to display the tables from which data is destroyed.

Customizing Settings

To adjust data destruction object /SCMB/LOC and define retention rules, proceed as follows:

1. In transaction ILMARA, define an audit area and assign the ILM object SCMB_LOC.2. In transaction IRMPOL, define ILM rules for ILM object SCMB_LOC.3. In transaction ILMSIM, check (simulate) the retention rules for ILM object SCMB_LOC (Evaluating Retention

Management Definitions).4. In transaction ILM_DESTRUCTION, the ILM rules for ILM object SCMB_LOC (data destruction object /

SCMB/LOC) are applied to data.

For more information about the Customizing settings for data destruction objects, see

● Processing Audit Areas● Editing ILM Policies● Evaluating Retention Management Definitions● Applying ILM Rules to Data

Executing Data Destruction Object /SCMB/LOC

You can destroy data from the database by executing a data destruction run for the data destruction object /SCMB/LOC.

For more information about executing data destruction objects, see Data Destruction with a Data Destruction Object.

Start the data destruction (transaction ILM_DESTRUCTION):

1. Select Data from the Database as the Type of Data to Be Destroyed.2. Enter the ILM object SCMB_LOC.3. Choose Execute. In the destruction of data from the database, the actions to be started ( Destroy and

Administration) are displayed.4. Define variants for the data destruction program.

Define a selection variant for the data destruction.To do so, you can use the following selection criteria to find the relevant SCM locations:○ General selection criteria for finding SCM locations and checking the retention rules:

○ Location○ Location Type

○ Standard ILM test and processing parameters○ Test Mode○ Production Mode


https://help.sap.com/viewer/7ce8e5dc89d7407e8baa9de7b775f31f/750 SP16/en-US/19e0786c9fc347b1bc7d0c0ae03e70d4.html

https://help.sap.com/viewer/7ce8e5dc89d7407e8baa9de7b775f31f/750 SP16/en-US/f4e6642b7f5542d8a7b7c7a037cba46f.html

https://help.sap.com/viewer/7ce8e5dc89d7407e8baa9de7b775f31f/750 SP16/en-US/65a763dde61a4ab3b3420de7bcbb6885.html

https://help.sap.com/viewer/7ce8e5dc89d7407e8baa9de7b775f31f/750 SP16/en-US/cb839233478440f38352cf23c6188a71.html

https://help.sap.com/viewer/7ce8e5dc89d7407e8baa9de7b775f31f/750 SP16/en-US/48360bcd9acd47df92c688fc69e938c2.html

https://help.sap.com/viewer/7ce8e5dc89d7407e8baa9de7b775f31f/750 SP16/en-US/48360bcd9acd47df92c688fc69e938c2.html

○ Detailed Log○ Log Output○ Description of Data Destruction Run

5. Define a start date and the spool parameters for the data destruction run and choose Execute.

Additional Checks by the Data Destruction Program

The data destruction program uses Where-used Functionality (WUF) to identify if the location is referenced by other objects. If so, the location is not destroyed. Therefore, you can destroy only locations that are not being used.

Authorization Objects

You require the following authorizations for data destruction with /SCMB/LOC:

Authorization object Description

S_ARCD_OBJ Execute data destruction run for data from the database

C_APO_LOC APO Authorization Object: Master Data, Locations

5.1.4 Data Protection

Use

Data protection is associated with numerous legal requirements and privacy concerns. In addition to compliance with general data privacy acts, it is necessary to consider compliance with industry-specific legislation in different countries. This documentation describes the specific features and functions that SAP provides to support compliance with the relevant legal requirements and data privacy.

For more information about topics related to data protection, see the Data Protection section in the relevant application-specific security guides

NoteIn the majority of cases, compliance with data privacy laws is not a product feature.

SAP software supports data privacy by providing security features and specific data-protection-relevant functions such as functions for the simplified blocking and deletion of personal data.

SAP does not provide legal advice in any form. The definitions and other terms used in this document are not taken from any given legal source.

More Information

Deletion of Business Partner Data

Deletion of Location Master Data [page 85]



https://help.sap.com/viewer/05a5505cc81943fb9d01e84cb2e135ef/750 SP16/en-US/32b45853b2dc7425e10000000a44176d.html

5.1.4.1 Deletion of Location Master Data

Use

You can use the SAP Information Lifecycle Management (ILM) component to control the blocking and deletion of location master data. Personal data collected in location master data can be blocked as soon as business activities for which this data is needed are completed and the residence time for this data has elapsed. After this time, only users who are assigned additional authorizations can access this data. After the retention period for data expires, personal data can be destroyed completely such that it can no longer be retrieved. Residence and retention periods are defined in the customer system.

NoteThe following information is only relevant for SAP SCM.

Implementation Considerations

● You have installed the following: SAP_BASIS 714 SP02 (or higher) and SAP NetWeaver 740 SP07 (or higher).

● You must configure the required Customizing settings under SCM Basis Master Data LocationLocation Master Data Deletion .

● Necessary authorization for blocking/unblocking○ Authorization object: /SCMB/LOCB○ Activity ( ACTVT) = 05 for blocking; 95 for unblocking

● Necessary authorization for viewing of blocked location master data.○ Authorization object: /SCMB/LOCB○ Activity ( ACTVT) = 03○ Authorization group ( BRGRU) defined in Customizing Define Authorization Group Indicating Blocked

Master Data● You must define the residence period and retention period rules for location master data in ILM

(transaction IRMPOL).

Features

The following functions are available for blocking and deletion of location master data:

● Blocking of location master dataYou can block location master data after the residence period has ended. Only authorized users can access the blocked data. The data cannot be displayed or used by other business users.

● Unblocking of location master dataCustomer master data that has been mistakenly blocked can be manually unblocked by an authorized user.


● Deletion of location master dataAfter the retention period the data manager can delete the location master data in the database.

The blocking function is supported in multi-system landscapes. If customer or vendor data is transferred from the ERP as location to SCM system, the customer/vendor end of purpose (EoP) check triggered in ERP calls also the SCM system and performs the EoP check for the transferred location.

The SCM system does not call any other system during the EoP check.

More Information

Blocking and Unblocking Location Master Data [page 86]

Block Location Master Data [page 88]

Unblock Location Master Data [page 91]

5.1.4.1.1 Blocking and Unblocking Location Master Data

Use

Blocking location master data enables you to block data that is no longer required for any business purposes. The data is blocked and not deleted as it is still in the retention period. The blocked data is no longer available for any business transactions or business use. The data is no longer displayed in existing business objects. You cannot edit, create new business objects or conduct follow-up activities with the blocked data.

Authorized users (authorization object: /SCMB/LOCB, ACTVT: 03) can access the blocked data. Authorized users (authorization object: /SCMB/LOCB, ACTVT: 95) can unblock the data in exceptional cases. Blocked data can be unblocked only within the retention period since data is deleted after the retention period.

Prerequisites

● You have activated the business function Information Lifecycle Management ( ILM).● You have read SAP Note 2249093 before activating the business function ILM-Based Deletion of

Location Master Data ( SCM_SCMB_LOC_ILM_1) to verify that all SCM applications that are used in your environment support blocking and deletion of SCM location data using SAP Information Lifecycle Management.

● You have activated the business function Location Master ILM-Deletion ( SCM_SCMB_LOC_ILM_1).● You have made the settings required for blocking and unblocking location master data in Customizing

under SCM Basis Master Data Location Location Master Data Deletion .● You have the required authorizations (authorization object /SCMB/LOCB)● You have defined the residence period and retention period rules for the location master data (ILM object:

SCMB_LOC) in SAP Information Lifecycle Management (ILM) (transaction IRMPOL).




● For scenarios transferring locations from ERP:○ You have correctly configured blocking and unblocking in the ERP system (see details in Blocking and

Unblocking Customer Master Data and Blocking and Unblocking Vendor Master Data).○ You have transferred plants from ERP to SCM after SAP Note 2156214 (or SP containing the

changes) was implemented in your ERP system.

Process

1. For locations created in the SCM system, you run the Block Location Master Data report (transaction /SCMB/LOC_PRE_EOP). For information about the report, see Block Location Master Data [page 88].For locations transferred from the ERP system, blocking needs to be triggered in the ERP system, see Block Customer and Vendor Master Data.

2. The system performs an end of purpose (EoP) check to determine whether the data related to the location master data is used.An EoP indicates that business is complete and the residence time for the location master data is over.The report considers the residence period and retention period rules maintained in ILM to determine if a location master has reached the EoP with respect to a dependent application. When the EoP is ensured in all the dependent applications only then the data is blocked.In a multi-system landscape, the customer/vendor EoP check run in the ERP system triggers the EoP check of a corresponding location in SCM (see Block Customer and Vendor Master Data for details). The EoP check in the SCM system does not trigger an EoP check in any other system.System blocks data in the following sequence:1. Blocking on company code level (only for transferred locations).2. Location general data

3. If the data is still used and business activities are not completed, the system does not block the data.4. If the data is not used by any applications, the system blocks the data.

Blocking of data can impact system behavior in the following ways:○ Display: The system does not display blocked data.○ Change: It is not possible to change a business object that contains blocked data.○ Create: It is not possible to create a business object that contains blocked data.○ Copy or Follow-Up: It is not possible to copy a business object or perform follow-up activities for a

business object that contains blocked data.○ Search: It is not possible to search for blocked data or to search for a business object using blocked

data in the search criteria.It is possible to display blocked data if a user has special authorization (authorization object: /SCMB/LOCB, ACTVT 03, authorization group specified in Customizing for Location Master Data Deletion); this user is not authorized, however, to create, change, or copy business objects with blocked data, or perform follow-on activities with these business objects.

5. If you need to display blocked data, you can do one of the following:○ Contact a business user who is authorized to display this data○ Contact a business user who is authorized to unblock this data (in case the data should be used

further in business processes)6. The user with authorization to unblock data unblocks the location master data using the report Unblock

Location Master Data (transaction /SCMB/LOC_UNBLOCK_MD). For information about the report, see Unblock Location Master Data [page 91].


https://help.sap.com/viewer/05a5505cc81943fb9d01e84cb2e135ef/750 SP16/en-US/f5c25853b2dc7425e10000000a44176d.html

https://help.sap.com/viewer/05a5505cc81943fb9d01e84cb2e135ef/750 SP16/en-US/f5c25853b2dc7425e10000000a44176d.html

https://help.sap.com/viewer/05a5505cc81943fb9d01e84cb2e135ef/750 SP16/en-US/86c75853b2dc7425e10000000a44176d.html


https://help.sap.com/viewer/05a5505cc81943fb9d01e84cb2e135ef/750 SP16/en-US/fe125953c91eff4fe10000000a44176d.html


For locations that are transferred from the ERP system, unblocking needs to be triggered from the ERP system. See Unblock Customer and Vendor Master Data.

7. System unblocks data in the following sequence:1. Location general data2. Location at company code level (if requested for transferred locations)

Result

The location master data is blocked. After the retention period ends, the system deletes the data.

5.1.4.1.1.1 Block Location Master Data

Use

You can use the Block Location Master Data report (transaction /SCMB/LOC_PRE_EOP) to block data related to locations. The report checks with the dependent applications if business is complete and the residence period is over and then blocks the location master data.

You can no longer display, edit, create business objects or conduct follow-up activities with the blocked data. The blocked data can be displayed only by users having the appropriate permissions.

You can unblock data that you might have blocked inadvertently using the Unblock Location Master Data report (transaction /SCMB/LOC_UNBLOCK_MD). For more information about the report, see Unblock Location Master Data.

For locations transferred from the ERP system, blocking needs to be triggered in the ERP system. See Block Customer and Vendor Master Data.

Prerequisites

● You have maintained the residence period and retention period rules in the SAP Information Lifecycle Management (ILM) portal (transaction IRMPOL).

● You are authorized to block location master data. You can use this report if the authorization object /SCMB/LOCB is set with ACTVT 05.

● You have made the settings in Customizing required for blocking location master data in Customizing under SCM Basis Master Data Location Location Master Data Deletion .

Features

Data to be Processed



https://help.sap.com/viewer/05a5505cc81943fb9d01e84cb2e135ef/750 SP16/en-US/7f175953c91eff4fe10000000a44176d.html



You can select the levels for which you want to trigger the end of purpose check using the following options:

● Check On All Data Levels: EoP check is started on general level, so all the selected locations are checked and can be blocked.

● Check Only at Company Code Level: EoP check is started on company code level. This mode is available just in Test Mode - ERP locations. There is no company code specific location master data in the SCM system. Blocking at company code level in SCM is required for consistent behavior in ERP and SCM.

Selection

You select the Location Type for EoP that you want to process. Further, you can narrow down the selection using the Location name. Choosing Test Mode - ERP locations, you can also specify the Business System Group of the ERP system and a Company Code (if Check Only on Company Code Level is selected).

Options

Skip Subsequent EoP Checks if Ongoing Business Found

If ongoing business is found for a master data in an application, the master data cannot be blocked. The report provides an option to optimize the EoP check; you can choose to skip subsequent EoP checks for the data from being conducted in the other applications.

ExampleThree applications, APPL_1, APPL_2, and APPL_3 are registered for EoP check for master data A, B, and C. If APPL_1 has open business activities for master data A and B, then APPL_2 is called for master data C only. Again, if APPL_2 has open business activities for master data C, then APPL_3 is not called at all.

Consider Next Check Date

For data that has ongoing business activities, applications return a date when the next EoP check can be conducted. You can also set the default next check date period for a data by configuring the activity Define Next Check Date Period under Customizing for Location Master Data Deletion. The report considers the default value if the application has not returned any next check date or if the next check date returned by the application is too far in the future.

If you select the Consider Next Check Date option, the report considers the next check date before triggering an EoP check for the data.

Processing Parameters

Number of Objects per Process

Specify the minimum number of objects per process. All dependent objects are handled in the same process. There is no strict upper limit, since the system ensures that all objects are always processed together.

However, processing runs in packages and the packages are formed internally, using SAP blocking logic. It is therefore a possibility that more objects will need to be processed in a package. When defining the package size, you should start with a value like 25, then measure the runtime and moderately increase or decrease the values as appropriate. Then measure the runtime again. The optimum package size needs to be predetermined for each system.

Parallel Processing

The report enables you to trigger parallel processing, that significantly improves runtime. Similar to synchronous processing, parallel processing also runs in packages. When you select this option, the default values for parallel processing made in Define Parallel Processing Settings under Customizing for Location


Master Data Deletion are used. You can also change these settings as per your requirement when you run this report.

● Maximum Number of Parallel Processes and Maximum Utilization of Server GroupSpecify the maximum number of parallel processes you want to run and the maximum utilization of the server group in percent.The percentage of maximum utilization of the server group that you specify determines or restricts the maximum number of parallel processes, in relation to the work processes of the server group that are available at runtime. Therefore, ensure that you specify at least one of the two values when selecting parallel processing. If you specify one parameter, the number of parallel processes is defined using only this parameter. If you specify both parameters, the number of parallel processes is determined using the parameter that applies first.

ExampleIf you define 10 parallel processes as maximum and 50% maximum utilization, but after seven parallel processes you already reach 50% utilization of the server group, the report will not start another parallel process. Similarly, if you would have only 25% utilization with 10 parallel processes reached, the report will not start more than these 10 parallel processes to get the maximum utilization of 50%.

Server Group

In parallel processing several dialog work processes on one or more application servers are used for the processing, regardless of whether they are called from a dialog program or a background job. The server group specifies which application servers can be used to what extent for parallel processing. You must specify a server group to use parallel processing.

Processing Options

You can run the report in test mode to view the data that meets the end of purpose check criteria and can be blocked. In this mode, data is not blocked. Test Mode - ERP locations is used for locations transferred from ERP. Choosing this option, the report explores whether the SCM system will prevent the blocking of a transferred location when the blocking report for the corresponding customer/vendor is run in the connected ERP system.

Detail Log

Without Success Message

With this option, the log lists summary messages or error messages.

Complete

With this option, the log lists all successful EoP checks for each registered application.

Log Output

The options Application Log and List and Application Log enable you to save the logs so that they can be analyzed using the report Display Stored Application Logs for Location (transaction /SCMB/LOC_DISPL_LOG).

For more information about the report, see Display Stored Application Logs for Location [page 92]



Activities

To access this report from the SAP Easy Access screen, choose Cross-Application Components Data Protection SCM Location Master Data Block Location Master Data (transaction /SCMB/LOC_PRE_EOP)..

Based on the data you choose, and the execution criteria you specify, the report triggers an EoP check and blocks data. It stores the Start of Retention Time (SoRT) in the table SoRT Details of Location for Each Application ( /SCMB/LOC_SORT) and blocks the location master data by setting the blocking indicators in the database tables.

More Information


5.1.4.1.1.2 Unblock Location Master Data

Use

You can unblock location master data that was blocked accidentally. Authorized users can unblock the data using the Unblock Location Master Data report (transaction /SCMB/LOC_UNBLOCK_MD).

For locations transferred from ERP, unblocking needs to be triggered in ERP. See Unblock Customer and Vendor Master Data.

Prerequisites

You are authorized to unblock location master data. You can use this report if the authorization object /SCMB/LOCB is set with ACTVT 95.

Features

Data to be Processed

You can select the level for which you want to unblock location master data using the following options:

● Unblocking on General Level: Location is unblocked on general level.● Unblocking on Company Code Level: This mode is available just in Test Mode - ERP locations. There are no

company code specific location master data in SCM. Unblocking on company code in SCM is required for consistent behavior in ERP and SCM.

Selection




You select what location type you want to process and can further narrow down the selection using location name. In Test Mode - ERP locations you can also specify business system group of the ERP system and a company code (if unblocking on company code level is selected).

Processing Options

You can run the report in test mode to view the data that can be unblocked. In this mode data is not unblocked. Test Mode - ERP locations is used for locations transferred from ERP. Choosing this option, the report explores whether the SCM system will prevent unblocking of a transferred location when the unblocking report for the corresponding customer/vendor is run in the connected ERP system.

Detail Log

Without Success Message

With this option, the log lists summary messages or error messages.

Complete

With this option, the log lists all messages.

Log Output

The options Application Log and List and Application Log enable you to save the logs so that they can be analyzed using the report Display Stored Application Logs for Location (transaction /SCMB/LOC_DISPL_LOG).

For more information about the report, see Display Stored Application Logs for Location [page 92].

Activities

To access this report from the SAP Easy Access screen, choose Cross-Application Components Data Protection SCM Location Master Data Blocking/Unblocking/Deletion of Location Master Data Unblock Location Master Data (transaction /SCMB/LOC_UNBLOCK_MD).

More Information


5.1.4.1.1.3 Display Stored Application Logs for Location

Use

You can use this report (transaction /SCMB/LOC_DISPL_LOG to display the application log of application log object Blocking Process Location ( /SCMB/LOC_LOG). It provides more contextual details at the level of the log items compared to the Analyze Application Log report (transaction SLG1)



This report helps you analyze blocking or unblocking logs of location master data and provides access to specific additional information such as:

● Location type● Location ID● Location name● Company code● Application name● System where the log item has been raised● Status

Prerequisites

● You have activated the business function ILM-Based Deletion of Location Master Data ( SCM_SCMB_LOC_ILM_1).

● You have the authorization object /SCMB/LOCB set with ACTVT 05.● You have the authorization to display application log objects.

Activities

To access this report, on the SAP Easy Access screen, choose Cross-Application Components Data Protection SCM Location Master Data Blocking/Unblocking/Deletion of Location Master Data Display Stored Application Logs for Location (transaction /SCMB/LOC_DISPL_LOG)..

More Information



5.1.5 Application Log of Location

Use

The application log for a location is a tool for collecting messages, exceptions, and errors. After being logged, this information is displayed in list form.


Features

The application log of the location shows you the messages issued by the following programs:

● Deletion program for locations (program /SAPAPO/DLOC_DEL_JOB )The application log for this program informs you where dependencies involving the deleted location still exist. You can then remove these on a targeted basis. For more information, see Delete Location [page 80] .

● All programs capable of running in background mode.

Logs can be displayed, saved in the database, and deleted from the database.

You can obtain the following information:

● Basic information (type of log, date, etc.)● Long text of message● Detailed information● Technical information:

Activities

To display logs, from the SCM Basis menu, choose Master Data Location Application Log Display Application Log.

To delete logs, from the SCM Basis menu, choose Master Data Location Application Log Delete Application Log.

5.1.6 Geocoding

Use

The term geocoding comes from the area of geographical data processing. It describes the process for determining the geographical coordinates (longitude and latitude, altitude) from the address data given. There are various commercial geocoding programs that determine the required data using the address attributes (country, region, postal code, city, street, and so on). It is therefore possible in many ways to enhance the existing data basis of these programs gradually (per country, for example). Within the SAP system, an interface has been created for such geocoding programs that is accessible for applications. Geocoding is a service that is not firmly integrated into the central address management (CAM). Applications that do not use CAM can nevertheless implement geocoding by installing a geocoding program. Specifically in SAP SCM, you have the option of geocoding the locations that have an address, using the PTV eServer geocoding program. For more information, see the PTV eServer for SAP SCM Server 7.0 installation guide on SAP Help Portal at https://help.sap.com

You can use the coordinates that are determined in various applications; for example, in the following applications:

● Display of business objects on a map, for example a location (localization of a business object on a map using address data)



https://help.sap.com

https://help.sap.com

● Determination of the distance (distances can be calculated on the earth's surface from the geocoordinates determined; for example, as a first approximation as the crow flies or with the relevant map material on a street basis)

● Routing (for example, in Transportation Planning, determining a route on a street basis)● Regional evaluation (for example, evaluating all customers within a radius of 50km or determining the

nearest competitor)

The solution chosen by SAP guarantees a problem-free connection to various geocoding programs. A model has been selected that provides a single interface for SAP applications. In Customizing it is possible to pass on these addresses using the SAP geocoding framework, on a country-specific basis, to various geocoding programs. This function allows various geocoding programs (for example, a special geocoding program for North America, another for Europe) to be used in the system. Depending on the country given in the address, the various geocoding programs are used. The geocoding programs are called by means of an interface defined by SAP. Manufacturers of geocoding programs can be validated for use of this interface.

Features

Geocoding Levels

You use geocoding levels to store geocoordinates for the address of a location on different levels of detail, for example by house number, postal code, or region. Having different levels of detail for the geocoordinates of a location allows you to improve the performance of the distance and duration determination between two locations. This is important if, for example, you have a large number of locations geocoded on a high level of detail thereby making the distance and duration determination a performance critical process. The lower the accuracy level the more locations share the same geocoordinates.

You can define the geocoding strategy that a geocoding level uses as well as which geocoding program to use and which address fields to pass. You define geocoding levels in Customizing (see Customizing activity Define Geocoding Levels).

To ensure a more flexible approach to the determination of distances and durations, you can use the process controller as a flexible framework to create different distance and duration determination strategies so you can connect to external geographical information systems (GIS) that offer different calculations than the straight line distance and the calculation offered by the standard geocoding program. You configure the process controller for the distance and duration determination in Customizing (see Customizing activity Configure Process Controller for Distance and Duration Determination).

ExampleYou have two transportation lanes. Transportation lane A contains the start location WALLDORF and the destination location MUNICH. Transportation lane B contains the start location WALLDORF and the destination location REGENSBURG. In the location master, MUNICH and REGENSBURG are part of the same region and geocoded to be part of the same region.

When determining the distances and durations, the system first determines the distance and duration for transportation lane A and saves the data in the buffering table. As transportation lane B ends in the same region, the system can reuse the data in the buffering table instead of running a second determination of distance and duration thereby increasing the performance of the system. The system only needs to call the distance and duration determination program once. You can define the required accuracy level in Customizing (see Customizing activityDefine Strategy for Distance and Duration Determination).


NoteIf you delete geocoding levels in the system, you can delete geocoordinates that have become obsolete as a consequence of this. To delete obsolete geocoordinates, you can use the Delete Obsolete Geocoordinates report. For more information, see Deletion of Obsolete Geocoordinates [page 99].

Mass Geocoding

If you want to maintain geocoding for multiple locations, you can use the Mass Geocoding report. For more information, see Mass Geocoding [page 97].

Process Controller for Geocoding

To ensure a more flexible approach to the determination of geocoordinates, you can use the process controller as a flexible framework to create different geocoding strategies so you can connect to external geographical information systems (GIS) different from the standard geocoding program. This flexibility allows you to use third-party GIS providers if required. You configure the process controller for geocoding in Customizing (see Customizing activity Configure Process Controller for Geocoding).

5.1.6.1 Calculation of Transportation Zone Coordinates

Use

You can use this program to convert the existing ERP data for a transportation zoneinto the geographical coordinates of a geolocation. A geolocation is defined by the following data:

● Latitude● Longitude● Time zone● Precision of the geolocation (for example, continent, country, region, postal code)

The system calculates the transportation zone coordinates by means of a geocoding program. The program determines the geographical latitude and longitude of the transportation zone. You can use this data to calculate the distance between two business partners, for example.

The geocoding is carried out according to the required precision, which may be defined at the level of country, region, postal code, place, street, or house number The SAP geocoding program supplied works at the country and region levels.

Prerequisites

● You have made the basic settings for geocoding in Customizing for SAP Supply Chain Management (SAP SCM) under General Settings Set Up Geocoding .

● You have entered the necessary address data. The system calculates the transportation zone coordinates on the basis of this address data.



Activities

● On the SAP Easy Access Menu mySAP Supply Chain Management screen, choose Advanced Planning and Optimization Master Data Location Calculate Transportation Coordinates .

● On the initial screen, enter a supply chain model and choose Execute .

NoteIf you set the Take Deletion Flag Into Account indicator on the initial screen, the customer and vendor locations that are assigned to the transportation zone and for which the deletion flag has been set are not taken into consideration in the calculation of the transportation zone coordinates.

● Choose the transportation zones for which you wish to calculate the coordinates from the list of results and then choose Calculate Coordinates .

● The system calculates the coordinates of the selected transportation zones. You will find the geographical data of the transportation zones on the General tab page of the location master record.

5.1.6.2 Mass Geocoding

Use

You use this report to calculate geographical coordinates for longitude and latitude for your maintained locations. Geocoordinates are essential for the distance and duration calculation between two or more locations. The system defines the geographical coordinates for a location using the following data:

● Longitude● Latitude● Precision of the location (for example country, region, postal code, street, house number)

The report allows you to display existing geocoordinates from the database, to simulate geocoordinates that the geocoding program provides or to directly overwrite existing geocoordinates for locations. You determine geocoordinates by defining a selection from the following:

● Location● Location type● Transportation zone

Once you have a selection, you define if you want to calculate geocoordinates for all selected locations or only for locations that do not yet have geocoordinates as follows:

● If you want the system to calculate geocoordinates for all of your selected locations, select the All Selected Locations radio button.

NoteIf you have maintained geocoding levels in Customizing, the system calculates the geocoordinates on the basis of the geocoding levels.

● If you want the system to only calculate geocoordinates for those locations that have initial geocoordinates, select the Only Locations Without Existing Geocoordinates radio button. You select the


radio button for locations where no geocoordinates were calculated upon the initial maintenance, or for locations that were transmitted from a back-end system by means of the Core Interface. If you want the system to only calculate geocoordinates for those locations that have initial geocoordinates on that geocoding level, additionally select a specific geocoding level.

● If you want to calculate geocoordinates based on a specific geocoding level, select the Only Specific Geocoding Level radio button.

Furthermore, you can execute geocoding as follows:

● If you want the system to display existing geocoordinates from the database for selected locations, select the Show Existing Geocoordinates radio button.

● If you want the system to simulate the geocoordinate determination, select the Simulate Geocoordinates radio button.

● If you want the system to overwrite any existing geocoordinates with the geocoordinates that result from this calculation, select the Overwrite Geocoordinates radio button.

To use this report, you must have activated the business function Enhanced Services for Transportation Network [page 14]( SCM_SCMB_TR_NETWORK).

Prerequisites

The system calculates initial geocoordinates for a location on the basis of existing address data. You must therefore ensure that you enter all relevant information (at least country) in the address data fields for your locations in the location master. You can find the location master on the SAP Easy Access screen under SCM Basis Master Data Location Location .

You have made settings to define geocoding levels in Customizing for SCM Basis under Master Data Location Geocoding Define Geocoding Levels .

Features

Mass Geocoding in Batch

You can use the Mass Geocoding in Batch report to schedule background processing for mass geocoding.

Activities

To access this report, on the SAP Easy Access screen, choose SCM Basis Master Data LocationGeocoding Mass Geocoding .

To access the Mass Geocoding in Batch report, on the SAP Easy Access screen, choose SCM Basis Master Data Location Geocoding Mass Geocoding in Batch .



5.1.6.3 Deletion of Obsolete Geocoordinates

Use

You use this report to delete obsolete geocoordinates after one or more geocoding levels have been deleted. You can do the following:

● If you want to display, change, or delete existing geocoding levels, select the GC-Levels field.● If you want the system to simulate obsolete geocoordinates, deselect the Delete Obsolete Geocoordinates

checkbox.● If you want the system to delete obsolete geocoordinates, select the Delete Obsolete Geocoordinates

checkbox.


Prerequisites

You have made settings to define geocoding levels in Customizing for SCM Basis under Master DataLocation Geocoding Define Geocoding Levels .

Features

You can use the Delete Geocoordinates in Batch report to schedule background processing for the deletion of obsolete geocoordinates after one or more geocoding levels have been deleted.

Activities

To access this report, on the SAP Easy Access screen, choose SCM Basis Master Data LocationGeocoding Delete Geocoordinates .

To access the Delete Geocoordinates in Batch report, on the SAP Easy Access screen, choose SCM BasisMaster Data Location Geocoding Delete Geocoordinates in Batch .


5.1.6.4 Interface for Third-Party Geo-Coding

Use

SAP provides an interface for third-party vendors of geo-coding programs. This interface describes how a company developing geographical information systems (GIS) can attach its geo-coding program to the SAP system. Thus, third-party vendors can offer a complete geo-coding package with regard to implementation, delivery, and Customizing.

Prerequisites

The geo-coding interface is valid for SAP's basis releases 4.6C, 4.6D, and 6.10.

You are not required to set up a user interface. The dialog box for selecting an address is part of the SAP geo-coding framework.

Features

Internal Structure of Geo-Coding Framework

The SAP system uses a geo-coding framework that provides a dispatcher. The dispatcher enables you to choose between several geocoders for a given address and an interface to ABAP applications. The application calls this dispatcher in order to pass one or more addresses. The dispatcher chooses the correct geocoder (depending on the country where the address is located and on Customizing settings), and then calls it via the geo-coding interface.

The following figure shows the geo-coding framework from the left (application) to the right (geo-coding program). The relevant part for geo-coding program suppliers can be found in the right-hand section of the figure (colored red), including the "Interface to geo-coding programs".



Data Exchange Between the SAP Geo-Coding Framework and the Geo-Coding Program


Attachment of Geo-coding Programs to the SAP System

You can attach your geo-coding program to the SAP system using:

the ABAP IF_GEOCODING_TOOL interface or

the RFC interface.

For more information about the different parameters and data types used, see

Parameter Description [page 106]

Data Types of the ABAP interface [page 111]

Data Types of the RFC interface [page 113]

ABAP IF_GEOCODING_TOOL Interface

To attach a geo-coding program to the SAP system via the IF_GEOCODING_TOOL interface, you must first implement a class in ABAP/OO. This class must then implement the IF_GEOCODING_TOOL interface. This interface defines the GEOCODE method as follows:

methodif_geocoding_tool~geocode

importing addresses type aes_addr_table



methodif_geocoding_tool~geocode

xinfo type geocdxinfo

exporting results type geocd_res_table

choice type geocd_choice_table

relevant_fields type geocd_addr_relfields_sortedtab

changing corrected_addresses type aes_addr_sortedtable

messages type aes_msg_table

containers type aesc_sortedtable.

The interface always works with tables and is able to run mass transactions. Each address carries an identifier (GUID16) for identification purposes. The geo-coding program needs to assign the identifier to all calculated results. Within this documentation, only one address is passed to the method for simplification purposes.

RFC Interface

To attach a geo-coding program to the SAP system via the RFC interface, you must implement an RFC server and use SAP's generic geocoder class to call it via RFC. The RFC destination and geocoder function name can be maintained in the geo-coding customizing settings. The ABAP class (CL_GEOCODER_GENERIC_RFC) simply maps the given parameters to RFC-safe structures and passes them to the RFC server, which you must implement.

We recommend that you use a function name such asRFCGEOCODER_ pv_ c, wherepvis a product identifier and version number, andcyour company identifier. The maximum length of such a function name is restricted to 30 characters. For example, an SAP geocoder could use a name such asRFCGEOCODER_GC10_SAP

This interface is as follows:

RFC_FUNCTION name_is_up_to_you

importing addresses type aes_rfc_addr_table

xinfo type geocdxinfo

time_zone type timezone


choice type geocd_choice_rfc_table

relevant_fields type geocd_addr_relfields_sortedtab

changing messages type aes_msg_table


RFC_FUNCTION name_is_up_to_you

containers type aesc_rfc_sortedtable

container_lines type aesc_cont_sortedtable

Differences Between IF_GEOCODING_TOOL and RFC Interfaces

A few arguments have changed in the RFC interface. These changes come from the fact that the address type has been changed fromADRC_STRUCin the OO interface toGEOCD_ADDRin the RFC interface. Addresses occur in exactly these two arguments.

The argumenttime_zonehas been added. This makes it easier for you to return the required time zone. Note that all addresses passed always come from the same country. Thus we pass only onetzone, which is valid for all the addresses in the respective country. This method works fine for countries with just one time zone and you only need to return this value. If you write a geocoder for a country with multiple time zones, such as the US or Russia, it is your job to determine the correct time zone for a given address.

The argumentcorrected_addresseshas been omitted because the SAP geo-coding framework corrects the addresses on its own.

The argumentschoiceandcontainershave been changed due to restrictions in RFC calls (no tables in tables). Argumentcontainer_lineshas been added and is now used in conjunction withchoiceandcontainers

We recommend the RFC approach for the following reasons:

There is no requirement to write ABAP coding.

Certification and/or validation is easier.

Example for a result in container_lines

The address withID=AF6C32could have been geocoded (which can be seen by the zero in columnCOUNT), while the address withID=FCA753is ambiguous (two entries withCOUNT=1 andCOUNT=2). Thus, addressFCA753has two corresponding entries in tableCHOICE, while addressAF6C32has a corresponding entry in tableCONTAINERS

ID COUNT SERVICE FIELD VALUE

FCA753… 1 GEOCODING LONGITUDE 1.234

FCA753… 1 GEOCODING LATITUDE 34.243

… … … … …

FCA753… 2 GEOCODING LONGITUDE -53.987

FCA753… 2 GEOCODING LATITUDE 12.433

… … … … …



ID COUNT SERVICE FIELD VALUE

AF6C32… 0 GEOCODING LONGITUDE 38.432

AF6C32 0 GEOCODING LATITUDE -84.342

… … … … …

Activities

Customizing Settings

In Customizing for General Settings , register your geo-coding program in the SAP system by selecting Geo-Coding → Register Geo-Coding Program in the System .

Enter the value forSRCIDthat you received from SAP and the name of your class. When using an RFC interface, the third-party vendor can have his ownSRCIDs

Save your entry. From now on, the SAP system only works withSRCID

Set up a country for your geo-coding program in Customizing for General Settings by selecting Geo-Coding → Assigning Geo-Coding Program to Countries .

Create a new line for the desired country, enter the value forSRCIDthat you received from SAP, and enter a value for the sequence. If there already is an existing line entered for this specific country, select a number smaller than this one.

Set the exclusive flag.

Mark all fields of theADRC_STRUCaddress structure that will be used to determine the geographical location in Customizing for General Settings by selecting Geo-Coding → Assign Relevant Address Fields for Geo-Coding for each attribute used in your geo-coding process. First enter the ID of your geo-coding program, then enter a value in the address field (or press F4 for a list of possible attributes).

To test it, run theGEOCODING_FIRSTprogram. It is a very simple program that lets you enter an address and prints out the values returned from the geo-coding program. As this is only a test program, we recommend using it as an entry point for your test program. You can also use this program for testing the SAP geo-coding program SAP0 that works on a country/region basis.

Keep in mind:

You are not required to write a geo-coding program for all countries at once.

It is possible to use more than one geo-coding program.

It is possible to set up the system for using specific geo-coding programs for specific countries.


Example

Fine-Tuning the Customizing Settings

A customer wants to use two different geo-coding programs for the same country (for example, France): a reasonable version that works on a regional basis in France (for example, the SAP0 geo-coding program that is contained in the standard delivery) (Geocoder1), and one that works at street level for Paris as capital of France (Geocoder2) for routing purposes.

You can set up Customizing in two different ways:

Run Geocoder1 to get a valid geographical location somewhere in France, and then improve it by trying Geocoder2, which may improve the location if it is in Paris.

In Customizing for General Settings , select Geo-Coding → Assign Geo-Coding Program to Countries . For France, Geocoder1 needs to get a value for the Sequence column that is smaller than Geocoder2 to make the program run earlier. But although Geocoder1 may succeed, we need to run Geocoder2, which may improve the result of Geocoder1. This requires that you remove the exclusive flag in Customizing.

This solution requires that you ALWAYS run both of the registered geo-coding programs, even for addresses in Paris.

Run Geocoder2. Only if the address is not located in Paris, start Geocoder1.

In Customizing for General Settings , select Geo-Coding → Assign Geo-Coding Program to Countries . For France, Geocoder1 needs to get a value for the Sequence column that is higher than Geocoder2 so that the program runs later. If Geocoder1 succeeds (because it found an address in Paris), Geocoder2 does not need to be run because there is no chance for it to improve the location. For this set, the exclusive flag of Geocoder2, which means "Do only continue if no result (result=6 -> not responsible

) was determined." If this flag is set once for a geo-coding program, all geo-coding programs for the same country with a higher value in the Sequence column are implicitly set as exclusive.

This is the preferable solution because of its higher efficiency, but it requires the geo-coding program with the higher order value to be able to improve on an already existing location.

5.1.6.4.1 Parameter Description

Use

The following table lists the parameters that can be used when attaching your geo-coding program to the SAP system via the ABAP IF_GEOCODING_TOOL interface.

For more information about the differences between the parameters given to the IF_GEOCODING_TOOL interface and those passed via the RFC interface, go to section Differences Between IF_GEOCODING_TOOL and RFC Interfaces in Interface for Third-Party Geo-Coding [page 100] .



addresses The interface passes all addresses in the table to the geo-coding program. Each entry consists of an ID and the address data itself (ADRC_STRUC structure).

When implementing the geo-coding program via the RFC interface, the data type of the address is different. It is GEOCD_ADDR which is a subset of ADRC_STRUC.

xinfo This table is used to pass additional information:

SRCID This attribute ("SourceID") is an identifier for the geo-coding program. This value is set in Customizing and simply needs to be returned in the geo-coding result container.

COUNTRY All addresses passed in addresses are from this country.

LANGUAGE This attribute displays the user language. Language code as defined in ISO 639.

results This table is used to return the status from the geo-coding process. Each entry consists of the ID to identify the corresponding address. For each address you need to return a result value ( RES attribute) with valid values (shown in bold font):

0 Geo-coding was successful. The result is unambiguous. The result has been returned in the containers parameter.

1 No geo-coding was required because of non-relevant address changes.

This value will be returned by the SAP geo-coding framework and is not allowed as a result value by the geo-coding program.

2 The result from geo-coding was ambiguous. The most probable address has been selected.

This value will only be returned in batch processing and is not allowed as a result value by the geo-coding program.

3 The result from geo-coding is ambiguous. Choices are available (see also the CHOICE export parameter).

This value should be returned if the user needs to select one out of a few different addresses.


4 The result from geo-coding is ambiguous. There is no choice available because the address data was not clearly specified.

This value should be returned if the list of choices is too big ("too big" is defined by you) or no match was found. In interactive mode, the user will then be asked to enter more data and geo-coding will be continued.

5 Geo-coding was not successful.

This value should only be returned if serious problems occurred within your program (program errors, illegal states, ...).

6 The program was not responsible.

This value should only be returned if your program was called for an address that cannot be geocoded. Example: Your program is responsible for all addresses in New York but the address given is located in San Francisco. In this case, the SAP geo-coding framework will dispatch the address to the next program.



choice This table is used to return a list of addresses the user can choose from. It will only be used if the return value in the results parameter equals 3.

The structure of the table is as follows:

ID

RANKING

PERCENTAGE

ADDR_SHORT

ADDRESS

COUNT (CONTAINER in the ABAP interface, see argument CONTAINERS for details)

The table starts with the ID attribute.

The following RANKING and PERCENTAGE attributes will be used to put these addresses in order. RANKING is used internally to determine the order. PERCENTAGE is only used for display purposes and does not have an impact on the displayed order.

The addr_short attribute is mandatory and is used for displaying the address in the dialog box.

In the address attribute, you must store the complete modified address as it would be passed from an external source.

The addresses data type is different when using the RFC interface. For more information, see section Differences Between IF_GEOCODING_TOOL and RFC Interfaces in Interface for Third-Party Geo-Coding [page 100] .

RFC interface:

The final count attribute is used in conjunction with the container_lines attribute. container_lines holds all pairs of service/key/value triples with results from geo-coding (for example GEOCODING/LONGITUDE/13.533). To identify such an entry, each such line has ID/COUNT as access key. For more information, see the example in the Example for a result in container_lines section in Interface for Third-Party Geo-Coding [page 100] . (The address with ID FCA753… returns a list of two addresses in choice and corresponding geographical data in container_lines ( count 1 & 2 in the table). Please do only use count values greater than or equal to one. Zero is reserved for the unambiguous result of the geo-coding process (see argument containers ).

ABAP interface:

If you use the ABAP interface, container directly links to a table with corresponding container lines.


relevant_fields Currently SAP displays the short form of the address ( addr_short attribute) in the selection dialog box. This table contains the selection-relevant attributes of the returned addresses in the choice parameter. Only the attributes mentioned in this table are displayed.

For example, if the user wants to geocode Frankfurt in Germany, he will encounter the problem that there are two cities called Frankfurt in Germany (Frankfurt-upon-Oder and Frankfurt-upon-Main). The geo-coding program returns a choice of addresses. Though these addresses also contain attributes like street name and house number, there is no need to display these fields if the user first needs to select the correct town. So you may only return the attribute names COUNTRY , POSTCODE and CITY1 in relevant_fields . A list is now displayed that shows only these three relevant fields.

corrected_addresses Do not change this attribute. Usually this attribute is used for internal purposes only.

messages It is possible to create messages that are displayed to users or written to the application log. There are some predefined messages in the SZGEOCODING development class. Simply append messages to this table. Do not modify or delete a message.



containers This is a table of AES containers. For each imported address, there will be an AES container to be exported. Again, each AES container can be identified via the ID .

Note that for each address passed to the geo-coding program, there will also be an AES container passed with the corresponding ID . So it is not required to create a new AES container entry in the table.

The attributes of each AES container structure are ID , CONTAINER, and CANCELLED in the ABAP interface, and ID and CONTAINER in the RFC interface.

CANCELLED should not be set. This flag is set by the SAP geo-coding framework when users cancel the selection of an address.

More details regarding the container are inside the AES container: One line of such a container consists of a SERVICE field that describes which service created this line. For geo-coding purposes, use constant "GEOCODING" (upper case is mandatory). The possible values for the FIELD attribute are LONGITUDE, LATITUDE, ALTITUDE, SRCID, SRCTSTMP, PRECISID, and TZONE (upper case is mandatory). The VALUE attribute is used to store values for the fields given in the FIELD attribute.

For a description of the container, see the graphic in section Data Exchange Between the SAP Geo-Coding Framework and the Geo-Coding Program in Interface for Third-Party Geo-Coding [page 100] .

For a description about the possible values and their data format, see Data Types of the ABAP interface [page 111] .

RFC Interface:

For technical limitations, a direct link to the container table is not available in the RFC interface. Instead the ID is used as link to the CONTAINER_LINES attribute, where the lines of the container are stored. Store container lines using the address' ID and COUNT =0 as key to table CONTAINER_LINES .

5.1.6.4.2 Data Types of the ABAP interface

Use

The following section describes the data types you can use when attaching your geo-coding program to the SAP system via the ABAP IF_GEOCODING_TOOL interface. For more information about the data types passed via the RFC interface, see Data Types of the RFC interface [page 113] .

Below, you will find the data types for the field values returned in the container (see the Data Exchange Between the SAP Geo-Coding Framework and the Geo-Coding Program section in Interface for Third-Party Geo-Coding [page 100] ).

The data type of the VALUE attribute is char255 . This data type enables you to store any kind of data. For the LONGITUDE, LATITUDE, ALTITUDE, SRCID, SRCTSTMP, PRECISID, and TZONE attributes that are relevant for


geo-coding, you need to convert your data to char255 . Then, the SAP applications need to convert these char255 strings back to real data types. These data types are defined in the GEOCODING structure.

GEOCODING structure Type Domain

GUIDLOC geoguid SYSUUID

LONGITUDE geolon GEOLONLAT

LATITUDE geolat GEOLONLAT

ALTITUDE geoalt GEOALT

SRCID geosrcid CHAR4

SRCTSTMP timestamp TZNTSTMPS

PRECISID geoprecis D_GEOPREC

TZONE timezone TZNZONE

The GUIDLOC attribute is for special use only. Do not create an entry with the GUIDLOC ! field. The meaning of the LONGITUDE, LATITUDE, and ALTITUDE attributes is self-explanatory. Longitude and latitude need to be passed in WGS84 data format. Altitude should be passed in meters above sea level and are set to zero if unknown.

The SRCID attribute is an identifier for the program that determines the geographical data. The SRCID value is passed in the XINFO structure and can simply be copied to your result.

The SRCTSTMP attribute holds a timestamp reflecting the time and date of data determination (this is not the date of geo-coding a specified address). A timestamp always contains the time and date in the UTC time zone. The format of a timestamp is YYYYMMDD HHMMSS:

YYYY Year

MM Month

DD Day

HH Hour

MM Minute

SS Second

An example for a valid timestamp is 20001224 121314, which is December 24 th, 2000, 12:13:14, UTC time zone.

The PRECISID attribute describes how precisely a geographical location has been determined. The following values have been defined in the D_GEOPRECIS domain.

0000 Information not available



0100 World

0200 Continent

0300 Country

0400 Region

0500 Borough

0600 Zip code

0700 Town

0800 District

0900 Center of street

1000 Center of interval of house numbers

1100 House number (interpolated)

1200 House number (exact)

1300 House number + additional information (for example Neurottstr. 7b)

The TZONE attribute describes the time zone in which the geographical location is located. The SAP table TTZZ lists the valid time zones. We need to determine the time zone here because mapping from address to time zone is much easier than mapping a geographical location to time zone. You may use the tzon_location_timezone function to determine the time zone for a given country or country + region. Determining the time zone is only difficult for bigger countries with multiple time zones, like the US or Russia. If you do not use our framework, but start to implement an RFC server (using SAP's CL_GEOCODER_GENERIC_RFC class for calling the geocoder via RFC), we additionally pass the time zone of the country used in the given addresses. This makes it easier to develop geo-coding programs for countries that do not have different time zones. If you develop a geo-coding program for countries with multiple time zones, you should ignore the given time zone.

5.1.6.4.3 Data Types of the RFC interface

Use

The following section describes the data types you can use when attaching your geo-coding program to the SAP system via the RFC interface.


Prerequisites

For more information about the data types passed via the ABAP IF_GEOCODING_TOOL interface, see Data Types of the ABAP interface [page 111] .

Features

The data types of the RFC interface are as follows:

importing addresses type aes_rfc_addr_table

xinfo type xinfo

time_zone type timezone


choice type geocd_choice_rfc_table

relevant_fields type geocd_addr_relfield s_sortedtab

changing messages type aes_msg_table

containers type aesc_sortedtable.

The data types will be defined using pseudo code:

aes_rfc_addr_table type standard table of aesaddrrfc;

aesaddrrfc type structure of {

id type byte [16],

address type geocd_addr

};



geocd_addr type structure of {

name_co type char [40],

city1 type char [40],

city2 type char [40],

city_code type char [12],

cityp_code type char [ 8],

home_city type char [40],

cityh_code type char [12],

regiogroup type char [ 8],

post_code1 type char [10],



pcode1_ext type char [10],



po_box type char [10],

po_box_num type char [ 1],

po_box_loc type char [40],

city_code2 type char [12],

po_box_reg type char [ 3],

po_box_cty type char [ 3],

postalarea type char [15],

transpzone type char [10],

street type char [60],

streetcode type char [12],

streetabbr type char [ 2],

house_num1 type char [10],



str_suppl1 type char [40],



location type char [40],


building type char [20],

floor type char [10],

roomnumber type char [10],

country type char [ 3],

langu type char [ 1],

region type char [ 3],

sort1 type char [20],

sort2 type char [20],

sort_phn type char [20],

addrorigin type char [ 4],

extension1 type char [40],

extension2 type char [40],

time_zone type char [ 6],

taxjurcode type char [15],

address_id type char [10],

remark type char [50],

langu_crea type char [ 1]

};

xinfo type structure of {

srcid type char [ 4],

country type char [ 3],

language type char [ 2]

}

time_zone type char [6];

geocd_res_table type standard table of geocd_ress;

geocd_ress type structure of {

id type byte [16],

res type int4 ,

info type char [128],

addit_info type char [64]

} ;

geocd_choice_rfc_table type standard table of aeschoirfc;



aeschoirfc type structure of {

id type byte [16],

ranking type int4 ,

percentage type numc [ 3],

addr_short type char [100],

address type geocd_addr,

container type aesc

};

geocd_addr_relfields_sortedtab

type sorted table of geocd_rlfl

with unique key id fieldname;

geocd_rlfl type structure of {

id type byte [16],

fieldname type char [30]

};

aes_msg_table type standard table of aes_msg;

aes_msg type structure of {

id type byte [16],

order_no type int4 ,

message type symsg

};

symsg type structure of {

msgty type char ,

msgid type char [20],

msgno type numc [ 3],

msgv1 type char [50],



msgv4 type char [50]

} ;

aesc_sortedtable type sorted table of aesc_tabs;


aesc_tabs type structure of {

id type byte [16],

container type aesc ,

cancelled type char

};

aesc. type standard table of aesc_struc;

aesc_struc type structure of {

service type char [16],

field type char [16],

value type char [255]

};

5.2 Product

Definition

Good that is the subject of business activity. A procuct is used, created, or consumed during the manufacturing process.

Use

The product master data of the SCM system are located in SCM Basis and can be used in all SAP applications containing SCM Basis, such as SAP Advanced Planning and Optimization ( SAP APO ).

You maintain the product master data in the SAP menu under SCM Basis Master Data Product .Here you can create, display, change, or delete products. You can log changes to master data using the functions for change logging for master data [page 211] . The mass maintenance of products is possible using the mass maintenance functionality for master data [page 197] .

Frequently, product master data is used in other master or transaction data (for example, in locations or documents). To find out where a certain product is used, you can perform the where-used function. For more information, see Where-Used List for Master Data [page 207] .

Structure

The master data for a product can be divided into global and location-dependent data. While the global data (such as the product group of a product) is valid everywhere, the location-dependent data for this product



apply only within a certain location. When you enter product data maintenance, you can set the global view or - by entering a certain location - the location-dependent view of the data. The location-dependent view always also displays the global data for a product. For more information, see Maintain Global Product Master Data [page 119] and Maintain Location-Dependent Master Data [page 122] .

The product master data is located on a number of tab pages. Some of the tab pages contain data that you only need in certain applications. For information enabling you to set up the product master data maintenance display on a user-specific basis by suppressing individual tab pages, see User-Specific Display Profiles for Master Data Maintenance [page 212] .

Integration

In an integrated system landscape with SAP Enterprise Resource Planning (SAP ERP) and an SCM system, the ERP system is frequently the leading master data system. In this case, the product master data is maintained in the ERP system, where it is managed as materials, and transferred to the SCM system via the SAP Core Interface (CIF). For more information, see Integration of Products [page 227] .

5.2.1 Maintaining Global Product Master Data

1. From the SAP menu choose SCM Basis Master Data Product . The Product Master: Initial screen appears. You have the following options here:○ View

To maintain global product master data, choose Global Data.If you choose Location and enter a location, the location product master appears. In this view, you can also maintain the global product master data. For more information, see Maintaining Location-Dependent Product Master Data [page 122].

○ Profile definitionOn the initial screen of the product master, you can maintain profiles such as the lot size profile or requirements profile independently of the product. You can assign these profiles to the product. For more information about the individual profiles, see the SAP Supply Chain Planning (SAP SCM) SAP Library for Demand Planning, Supply Network Planning (SNP), and Production Planning and Detailed Scheduling (PP/DS).

2. Enter a product number. The product number can be either alphanumeric or numeric. You can set the representation of the numeric product number in Customizing for SCM Basis under Master DataProduct Set Output Format of Product Number .The Create Product screen appears.

3. Enter the base unit of measure in which stocks of the product/material are to be measured.4. Enter an identifier for the product. In doing so, take care not to use the special characters * (asterisk) and ;

(semi-colon).5. The following tabs are available for global product master data:

○ Properties○ Properties 2

On this tab, you can specify alternative product numbers [page 121] and product groups [page 120] for a product.


○ Properties SPPThis tab is only displayed if you are using spare parts planning (SPP). For more information, see the SAP Supply Chain Management (SAP SCM) SAP library under Advanced Planning and Optimization

Spare Parts Planning (SPP).○ Classification

This data is used primarily in demand planning and in characteristics-based planning. For more information, see the relevant SAP SCM SAP library.

○ Units of measure○ ATP

On this tab, you maintain data that is relevant to the global availability check (ATP) for a product. For more information, see the relevant SAP SCM SAP library for the global availability check.

○ SNP1On this tab, you maintain data that is relevant to planning a product using Supply Network Planning (SNP). For more information, see the SAP SCM SAP library for Supply Network Planning.

○ Packaging DataThis data is used for the packing instructions relevant for a product.

○ StorageThis data is used in Extended Warehouse Management. For more information, see the SAP SCM SAP library under SAP Extended Warehouse Management.

NoteSAP Advanced Planning and Optimization (SAP APO) can be deployed within an SAP SCM Server installation or as an add-on on SAP ERP (as of SAP Enhancement Package 6 for SAP ERP 6.0). Note that the Service Parts Planning component (SCM-APO-SPP) is only supported in an SAP SCM server installation.

5.2.1.1 Product Group

Definition

Grouping of similar products. Product groups are defined for a product group type. The product group type specifies the criterion by which grouping takes place (for example, size ). The product groups represent the instances of this grouping (for example, small , medium , large ). You define the product group type and product groups in Customizing for the product master.

Use

Product groups are used in various processes, such as those in Service Parts Planning (SPP) . When defining product groups, you can also maintain transportation lanes for product groups instead of for individual products, for example.

To assign a product to an existing product group, choose Properties 2 in product master maintenance.



To assign a large number of products to an existing product group at one time, you can use the mass maintenance function. It is necessary to differentiate between the following cases:

● You want to assign products for which an entry for a product group type already exists. To select these products, enter the following values:

Component Attribute Value

Product groups Product group Name of product group

The system selects all products that are assigned to this product group. You can now also assign them to another product group, for example.

● You want to assign products for which no entry for a product group type yet exists. To choose these products, enter the following values:

Component Attribute Value

Product groups Product group Initial

Product groups Product group type Identifier for product group type

The system selects all products for this product group type that have not yet been assigned to a product group. You can now assign them to a product group.

Structure

Product groups consist of a product group type and a value assigned to this product group type.

Example

You want to group products according to size. For this purpose, you have defined a product group type Size . You assign the values small, medium, and large to this product group type.

5.2.1.2 Alternative Product Number

Definition

Number under which a product is managed in the system in addition to the product number defined when it was created. An alternative product number (APN) can be a manufacturer part number or an old material number, for example.


Use

You assign alternative product numbers to a product on the Properties 2 tab page in the product's master record. Alternative product numbers are always assigned to a type(APN type), which is defined in Customizing for the product master under Product Maintain Alternative Product Number Type .

Alternative product numbers facilitate a more flexible search for a product, since you can conduct the search via not just one but several product numbers. To search for an alternative product number, invoke the input help for the Product field on the initial screen of the product master and choose the Search with Alternative Product Numbers tab page .

You can assign multipe alternative product numbers. The system does not perform a check of uniqueness.

Structure

Alternative product numbers comprise an APN type and an assigned value.

Integration

Alternative product numbers are not integrated with the ERP system via the APO Core Interface (CIF).

5.2.2 Maintain Location-Dependent Product Master Data

Prerequisites

Procedure

1. In the SAP menu, choose SCM Basis Master Data Product . The Product Master initial screen appears.

2. Enter a product name.3. Choose the Location view and then choose a location.

If you are working with SAP Advanced Planning and Optimization (SAP APO) , you can use the data from predefined profiles. When you choose a profile, certain fields of the product master are automatically populated with the data defined in the relevant profile. If you change this data in master data maintenance, you can no longer maintain the product master globally via the profiles. You can define profiles in Customizing for SAP APO under Supply Chain Planning in the settings for the relevant application.

4. Choose Create . The Create Product for Location screen appears.In location product master data maintenance, the tab pages for global product master data are available to you in addition to those for the location product master data described in the following. For information on global product master data, see Maintain Global Product Master Data [page 119] .

5. Enter the relevant data on the tab pages. Depending on the application you are working with, the following tab pages are available:○ Administration



On this tab page, you can assign a person responsible (planner) to a location product.You can only assign planners that are defined in Customizing for SCM Basis under Master Data Specify Person Responsible (Planner) .

○ ATPThe fields of this tab page are relevant only if you are working with SAP APO . The tab page also contains global product master data. For more information, see the documentation for the global ATP check.

○ SNP 1The fields of this tab page are relevant only if you are working with SAP APO . The tab page also contains global product master data. For more information, refer to the documentation on Supply Network Planning.

○ SNP 2 [page 128]The fields of this tab page are relevant only if you are working with SAP APO . For more information, refer to the documentation on Supply Network Planning.

○ Requirements [page 124]The fields of this tab page are relevant only if you are working with SAP APO . For more information, refer to the documentation on Production Planning and Detailed Scheduling (PP/DS).

○ Lot Size [page 126]The fields of this tab page are relevant only if you are working with SAP APO . For more information, refer to the documentation on Production Planning and Detailed Scheduling (PP/DS).

○ PP/DSThe fields of this tab page are relevant only if you are working with SAP APO . For more information, refer to the documentation on Production Planning and Detailed Scheduling (PP/DS).

○ Procurement [page 130]This tab page contains data relevant ot external procurement.

○ GR/GI [page 130]This tab page contains data relevant to delivery (goods receipt and goods issue).

○ Additional DataThis tab page is used to display fields that do not exist as standard and which have previously released

in Customizing for SCM Basis under Master Data Define Free Attributes.The following tab pages are relevant only if you are working with Service Parts Planning (SPP). For more information, see the relevant documentation.

○ SPP Inventory Planning○ SPP DRP○ SPP Deployment○ SPP Inventory Balancing/Inventory Surplus

6. Save the entries.

If you are working with SAP APO , you will find more information on the maintenance of application-specific master data in the SAP SCM section of the SAP library under Advanced Planning and Optimization . This applies, in particular, to the following applications:

● Production Planning and Detailed Scheduling (PP/DS)● Demand Planning● Supply Network Planning● Global Available-to-Promise (Global ATP)● Service Parts Planning (SPP)


5.2.2.1 Requirement (Demand) Data

Definition

The fields on the Requirements (Demand) tab page in location product master data maintenance are only relevant if you are working with Production Planning and Detailed Scheduling (PP/DS) in SAP Advanced Planning and Optimization (SAP APO).

Use

Requirement Strategy

Fields/area Use to define...

Default strategy How quantities forecast in APO Demand Planning are generated and sales orders are offset against the sales forecast (demand/requirement forecast).

Dependent requirements

Always collective requirement That a collective dependent requirement is to be generated

Possible individual customer requirement That an individual dependent requirement is generated if possible

Consumption

Consumption mode Whether you want to use backward and/or forward consumption

Consumption period Number of calendar days for forward or backward consumption

Assembly planning Whether the system performs forecast consumption for the product's dependent demand or transportation requirements when the dependent demand or transportation requirements change

Pegging


Dynamic pegging

Pegging strategy How product requirements are covered



Maximum earliness of a receipt The maximum period of time that a requirement element may lie before a receipt element in order for the system to establish a pegging relationship between them by setting a pegging edge.

Maximum lateness of a receipt The maximum period of time that a receipt element may lie before a requirement element in order for the system to just about set a pegging edge between the two elements, thus establishing a pegging relationship.

Date/time alerts

Alert threshold for earliness As of when an alert is issued if a receipt element lies before a requirement element in terms of time and there is a pegging relationship between the two.

NoteYou also use the alert thresholds to specify that premature or delayed receipts are taken into account to cover requirements or in the range-of-coverage (days' supply) calculation.

For more information, refer to the PP/DS documentation on the calculation of the range of coverage (days' supply).

Alert threshold for lateness As of when an alert is issued if a receipt element lies after a requirement element in terms of time and there is a pegging relationship between the two.

Individual product tolerance

Product tolerance minus or plus The maximum allowed under- or overcoverage of the individual product tolerance in the requirement element as a percentage.

Overall delivery tolerance

Underdelivery tolerance The percentage tolerance value that specifies by how much the quantity actually delivered may fall short of an order quantity

Overdelivery tolerance The percentage tolerance value that specifies by how must the quantity actually delivered may exceed an order quantity

Use quantity

Use total order quantity (use total receipts) That the total order quantity must be consumed

Consume quantity from total stock (use total stock) That the total stock must be consumed


Available stocks


Blocked stock, stock in transfer, stock in quality inspection, etc.

Which stocks are regarded as available in Production Planning and Detailed Scheduling and in Capable-To-Match (CTM). This means that the system takes these stocks into account in the net requirement calculation and in dynamic pegging.

5.2.2.2 Data on Lot Size

The fields on the Lot Size tab page in location product master data maintenance are only relevant if you are working with Production Planning and Detailed Scheduling (PP/DS) in SAP Advanced Planning and Optimization ( SAP APO ).

Procedure


Lot sizes/DS profile The lot-sizing procedure that is to be used in production planning calculations

Lot-size unit The valid unit of measure

Procedure

Lot-for-lot order quantity Use of the exact lot size in production planning calculations

Fixed lot size Use of a fixed lot size in production planning calculations. It also specifies the quantity that is to be ordered or produced in the event of undercoverage

Periodic Use of a period lot-sizing procedure and the associated type (day, week, etc.)

Reorder point Use of a reorder point procedure and the type of procedure

Reorder days' supply The number days the stock on hand and planned receipts of a material are to suffice to cover requirements existing at the time of planning

Planning calendar The planning calendar for the period lot-sizing procedure

Number of periods The number of short, medium, and long-term periods

Quantity and Date Determination



Procedure


Quantity Determination

Minimum lot size Minimum quantity for procurement

Maximum lot size Maximum quantity for procurement

Target stock level method The target stock level represents a value for the available warehouse stock/stock on hand that is to be achieved through planning.

Assembly scrap (%) Scrap (as a percentage) incurred during production of the material (if the material is an assembly)

Rounding value The value to the multiple of which the system rounds up the procurement quantity

Rounding profile The key used by the system to adjust the order proposal quantity to deliverable units

Target days' supply The number days stock on hand and planned receipts of a material should suffice to cover requirements existing at the time of planning

Date Determination

Safety days' supply The number of days stock on hand and planned receipts of a material should suffice to cover requirements existing at the time of planning

Use period factor The indicator for determining the availability date. You can choose between requirement date = availability date and the availability date from the period factor

Period factor The point in time in a certain period at which the system is to generate receipt due dates/times. The validity relates to period lot-sizing procedures.

Stock Data

Safety stock The quantity that is to satisfy an unexpectedly high requirement in the coverage period

Reorder point The quantity that is to satisfy an unexpectedly high requirement in the coverage period

Maximum stock level The quantity that is to satisfy an unexpectedly high requirement in the coverage period


Procedure


Stock The quantity of the unrestricted-use stock of this product at this location

Safety stock method The method used to calculate the safety stock

Service level (%) Percentage specifying the proportion of pending requirements that is to be covered by warehouse stock (stock on hand)

Relative forecast error for requirements (%) Percentage describing the ratio of the mean deviation between requirement forecast and actual requirement to the requirement forecast. The lower the percentage, the more accurately the forecast agrees with actual requirements.

Relative forecast error in replenishment lead time (%) Percentage describing the ratio of the mean deviation between the forecast and real replenishment lead time (RLT) to the RLT forecast. The lower the percentage, the smaller the deviation between forecast and actual.

5.2.2.3 Product-Relevant Data for SNP2

The fields on the SNP 2 tab page in location product master data maintenance are only relevant if you are working with Supply Network Planning (SNP) in SAP Advanced Planning and Optimization ( SAP APO ).

SNP2 Use to define...

Demand profile How the system calculates the demand

Forecast horizon A horizon in calendar days in which the forecast is not regarded as part of total demand

Pull deployment horizon The number of days in which the distribution demand is taken into account for calculating deployment

Period split How the planning data is disaggregated by time when you release the demand plan from Demand Planning to Supply Network Planning

VMI promotion lead time Like the target days' supply, which refers to the total demand without VMI promotions and is specified in the lot size profile, this lead time refers to the number of days required to satisfy demand, specifically for VMI customer promotions prior to their due date



SNP2 Use to define...

Supply profile How the system calculates supply (that is, key figures such as production and distribution receipts)

Production horizon Where Supply Network Planning ends and Production Planning & Detailed Scheduling (PP/DS) begins

Stock transfer horizon The number of days, beginning with the start of the heuristic run, during which the system does not plan any stock transfers. The system does not generate planned distribution receipts within this horizon but postpones them until the first day after the stock transfer horizon

Push deployment horizon The quantity available for distribution in the future. Receipts beyond this period are too uncertain to confirm by deployment

Deployment SS push horizon The push horizon for deployment when using the safety stock

Firm production That the production date/time is to lie outside the planning period

Fix transports That the transport is to lie outside the planning period

Deployment profile The logic that the system uses during deployment calculations to generate distribution proposals

Fair share rule If demand exceeds supply, the system can use fair share logic to calculate deployment on the available to deploy (ATD) quantity. These rules allow for alternative methods of allocating a restricted supply of a product to the demand sources

Push distribution Push rules are used in Supply Network Planning to calculate deployment when the available to deploy (ATD) quantity covers demand

Customer product The material number used by the customer for this product

VMI purchasing group The identifier for the buyer or purchasing group responsible for the purchasing tasks associated with the VMI product

Purchasing group The key for a buyer or group of buyers responsible for certain purchasing activities

Priority The priority of the product


5.2.2.4 Procurement Data

The following fields are available to you on the Procurement tab page:

Procurement Use to define...

Procurement type How the product is procured (external procurement, in-house production, external or in-house production, external procurement planning)

Planned delivery time The number of calendar days required to acquire the product or service through external procurement

Cost function Used by the optimizer to calculate the cost of procuring, producing, or transporting fluctuating product quantities defined in intervals via the maintenance function

Procurement costs All costs incurred in the procurement of the product

Product storage costs Used by the heuristic and optimizer to calculate how much it costs to store the product in the associated storage resource (warehouse) per base unit of measure

Safety stock penalty The penalty costs incurred if there is a shortfall below the safety stock

5.2.2.5 Data on Goods Receipt and Goods Issue

The following fields are available to you on the GR/GI tab page in location product master data maintenance:

GR/GI Use to define...

Goods receipt processing time The time between the delivery or production of a product and its availability as stock on hand

Goods issue processing time The time between the withdrawal of a product from warehouse stock on hand and its transportation

Loading group The grouping of products subject to the same requirements with respect to loading

Quantity propagation The quantity propagation through confirmation

Comp.adjust.confirm Component adjustment through confirmation

RemNetDrtnAdjustment The remaining net duration adjustment through confirma-tion



GR/GI Use to define...

Synchronous posting GI Whether the goods issue for this component is posted synchronously or asynchronously in the ERP system

HandlCap consump. GR How much handling resource capacity is used by the product for a particular plan

HandlCap consump. GI The handling capacity consumed in the goods issue

StorageCons per BUn How much storage capacity is consumed by the product for a particular plan

Costs for goods receipt The unit of measure of the product for which a goods receipt can take place

Costs for goods issue The unit of measure of the product for which a goods issue can take place

Delivery time quotas The key for the delivery time quota profile maintained in Customizing

Time in warehouse (days) The average time the location product spends in the warehouse (in days)

5.2.3 Mass Maintenance of Penalty Costs for Products/Location Products

Use

Mass maintenance enables you to maintain the penalty costs for several products or location products in one process and thus save time entering the data.

Features

● Mass maintenance of product penalty costs● Mass maintenance of location product penalty costs


Activities

1. On the Product Master: Initialscreen, chooseExtras Mass Maintenance of Product Penalty Costs or Mass Maintenance of Location Product Penalty Costs.

2. Enter the product number and description. When maintaining the location product penalty costs, among other things, you can select by location or planner.

3. Set the Detail Display indicator to view and further restrict the number of products selected.

5.2.4 Assignment of Planning Version to Location Product

Use

You can assign a planning version to a location product to carry out planning with version-specific data.

NoteIf you do not assign a planning version to a location product, the SCM system uses the version-independent data for the planning.

Prerequisites

You have created a planning version and a location product.

You have assigned the location product to a supply chain model. All the planning versions belonging to a supply chain model are offered for selection via the input help. For more information, refer to the SAP SCM section of the SAP library under Advanced Planning and Optimization Master Data Supply Chain Model, Planning Version and Supply Chain Engineer.

Features

● Assignment of Planning Version to Location Product● Deletion of Assignment to Planning Version

Activities

Assignment of Planning Version to Location Product

1. You are on the Product Master: Initial screen . Enter a product and choose a location for the Location view.



2. Click the Choose Planning Version pushbutton.3. On the Set Planning Version screen, use the input help to choose a planning version.4. Confirm the assignment with Enter. The Set Planning Version screen is closed and the selected planning

version number is displayed in the Planning Version field on the Product Master: Initial screen .5. Choose Create or Change. You branch to the Change Product for Location on Version-Dependent Basis

screen appears, where you will find all tab pages that exist for the maintenance of global and location-dependent product master data. All fields that are ready to accept input are now available to you for the maintenance of version-dependent data.

6. Maintain the relevant data on the tab pages for the set planning version. This data is specific location product data for a planning version.

7. Choose Save.

Deletion of Planning Version Parameters

1. Enter a simulation version profile.2. Choose Delete Planning VersionParameters.3. Select the line with the relevant planning version on the Selection of Location Products with Planning

Version screen.4. Delete the assignment to this planning version data with Enter.

5.2.5 Assignment of Supply Chain Model to Location Product

Use

Assignment to a supply chain model is the prerequisite for a location product being taken into account in the planning.

Prerequisites

You have created a location product and a supply chain model. For more information, refer to the SAP SCM section of the SAP library under Advanced Planning and Optimization Master Data Supply Chain Model, Planning Version and Supply Chain Engineer.

Activities

1. Invoke production master data maintenance.2. Choose a product and a location using the input help and then choose Assign Model .3. Select the appropriate line on the Assignment of Location Product - Model screen and save the assignment.

NoteYou can assign one or more supply chain models to a location product. You can also delete previously made assignments.


5.2.6 Delete Product

Use

To delete a product, you must first set the deletion flag before finally deleting the product in a second step. In this way, you can prepare several products for deletion and perform the actual deletion at a later point in time - perhaps in the background.

For information on how you can deactivate material master records in the Core Interface (CIF) and are then able to delete the relevant products in the SCM system, refer to Logging Deactivated Material Master Records [page 43] .

Prerequisites

The general prerequisites for the deletion of master data apply.

You have eliminated any still-existent dependencies [page 208] involving this product. Dependent objects can be orders for the product or inclusion in production process models (PPMs), for example. To clarify existing dependencies, you can generate a where-used list [page 207] for the product that is to be deleted.

For more information, see SAP Note 571031.

Procedure

1. On the Product Master Data: Initial screen, choose a product, then choose Product Flag for Deletion.2. On the following screen, set the deletion flag for the product and choose Save .

NoteYou can remove the deletion flag by unsetting the indicator for the relevant product.

3. Choose Extras Delete Products, to finally delete one or more products that have been flagged for deletion. You can either perform the deletion immediately or schedule it for a later point in time.

5.2.7 Product Hierarchy

Definition

Products can be part of a hierarchical relationship, such as product families, product groups and products. Hierarchies can be formed for both products and location products.

Product-relevant hierarchies are based on hierarchies (hierarchy, schema hierarchy) defined in Customizing. A distinction is made between planning products, which are based on location product hierarchies, and configurable products, which are based on product hierarchies. Through the assignment, the hierarchies



acquire a special function (this applies exclusively to hierarchies and schema hierarchies, not to generated hierarchies).

For more information, see Hierarchy [page 141] and the Implementation Guide for SCM Basis under Master Data Product Maintain Product-Relevant Hierarchy .

5.2.8 Inheritance of Product Master Attributes

Use

With the inheritance function, you can cause certain product master attributes to assume the same values for all the products of a location and a planning version.

Prerequisites

To set up the inheritance of product master attributes, you must extend the table structures of the attributes supplied by SAP. For more information, see Extend Table Structures for Inheritance [page 136] .

The attributes for which you set up the inheritance facility must be attributes of the location product master.

Features

● Pass on valuesIn the standard system, the values of all attributes that are displayed in the maintenance transaction for inheritance can be passed on.

● Display inherited values● Exclude attributes from inheritance

You can exclude individual attributes from inheritance by deselecting the relevant indicator in the product master menu under Edit Inheritance.

Activities

1. From the SAP menu, choose SCM Basis Master Data Product Maintain Values for Inheritance.2. Enter the location and planning version for whose location products you wish to pass on values.3. Enter the values of the attributes you wish to pass on in the relevant fields.4. Choose Pass on Values .5. The system populates the attributes of the products with the corresponding values provided that you have

not explicitly excluded them from inheritance.


Note

You cannot subsequently change inherited values manually in the product master. To be able to change the values, you must exclude the relevant attributes from inheritance.

5.2.8.1 Extend Table Structures for Inheritance

Use

To set up the inheritance of product master attributes in a system, you must extend includes supplied by SAP in table /SAPAPO/MLREFLOC through append structures in the customer namespace.

Procedures

Determine the location product fields for which you wish to use inheritance.

When choosing the fields, note that any inconsistencies arising through the passing on of the fields will not be picked up by consistency checks. Such inconsistencies are liable to occur when quantity fields are passed on, for example.

Determine which of these fields belong to table /SAPAPO/MATLOC, which to table /SAPAPO/MATLSPP, and which belong to both tables.

Call up the table /SAPAPO/MLREFLOC.

Create append structures in the customer namespace for each of the following includes of this table supplied by SAP:

/SAPAPO/MLREF_I [page 137]

/SAPAPO/MATLOC_R_I [page 138]

/SAPAPO/MATL_SPP1_R_I [page 139]

/SAPAPO/EXT_MATLOCX [page 140]

Extend just the include in each case: not - under any circumstances - the table.



Result

The system extends the selected fields in the tables /SAPAPO/MATLOC and /SAPAPO/MATLSPP by adding the inheritance indicator. Inheritance is now active as standard for these fields. Values for these fields are used by the system as defaults in all products of the location and planning version in question.

5.2.8.1.1 Create Append Structure for Include /SAPAPO/MLREF_I

Use

The append structure for the include /SAPAPO/MLREF_I is necessary to set up the inheritance facility in your system.

Prerequisites

You have determined the fields you wish to use for inheritance.

Procedure

1. Invoke the include /SAPAPO/MLREF_I in table /SAPAPO/MLREFLOC by double-clicking.2. Create an append structure for this include in the customer namespace.

○ Choose a name for the append structure in the customer namespace in which the structures are to be stored.

○ Copy the field names into the append structure under Component . Copy the corresponding data elements into the structure nder Component Type . The system supplies the values for the remaining columns automatically.

3. Save your entries and activate the append structure.

Example

1. You want to set up the inheritance facility for the fields SCOST and MAXEOQ_POD. The field SCOST comes from the table /SAPAPO/MATLOC and the field MAXEOQ_POD from the table /SAPAPO/MATLSPP.

2. You enter ZMLREF_APPEND as the name of the append structure.


3. You copy the fields and data elements into the append structure as follows:

Example of Append Structure

Component Component Type

SCOST /SAPAPO/SCOST

MAXEOQ_POD /SAPAPO/ MAXEOQ_PERIOD

5.2.8.1.2 Create Append Structure for Include /SAPAPO/MATLOC_R_I

Use

In this step, you include the fields originating from table /SAPAPO/MATLOC in an append structure.

Prerequisites

You have selected the fields you wish to use for inheritance.

Procedure

1. Invoke the include /SAPAPO/MATLOC_R_I in table /SAPAPO/MLREFLOC by double-clicking.2. Create an append structure for this include.

○ Choose a unique name for the append structure in the customer namespace in which the structures are to be stored.

○ Copy the field names under Component . Under Component Type , specify the data element /SAPAPO/INH_FLAG for each field.

3. Save your entries and activate the append structure.

Result

The system creates the inheritance indicator for the selected fields in the product master.



Example

1. You have selected the fields SCOST and MAXEQR_POD. The field SCOST comes from the table /SAPAPO/MATLOC.

2. You enter ZMATLOC_R_APPEND as the name the append structure.3. You copy the field name SCOST under Component and the data element /SAPAPO/INH_FLAG under

Component Type as specified below .

Append Structure


SCOST /SAPAPO/INH_FLAG

5.2.8.1.3 Create Append Structure for Include /SAPAPO/MATL_SPP1_R_I

Use

In this step, you include the fields originating from table /SAPAPO/MATLSPP in an append structure.

Prerequisites


Procedure

1. Invoke the include /SAPAPO/MATL_SPP1_R_I in table /SAPAPO/MLREFLOC by double-clicking.2. Create an append structure for this include.


○ Copy the field names under Component . Under Component Type , assign the data element /SAPAPO/INH_FLAG to each field.

3. Save and activate your entries.

Result

The system creates the inheritance indicator for the selected fields in the table /SAPAPO/MATLSPP.


Example

You have selected the fields SCOST and MAXEQR_POD. The field MAXEQR_POD comes from the table /SAPAPO/MATLSPP.

You enter ZMATLOC_R_APPEND as the name of the append structure.

You copy the field name MAXEOQ_POD under Component and the data element /SAPAPO/INH_FLAG under Component Type.

Append Structure


MAXEQR_POD /SAPAPO/INH_FLAG

5.2.8.1.4 Create Append Structure for Include /CI_MATLOCX

Use

In this step, you include the fields originating from tables /SAPAPO/MATLSPP and /SAPAPO/MATLOC in an append structure.

Prerequisites


Procedure

1. Invoke the include /CI_MATLOCX in the structure /SAPAPO/EXT_MATLOCX by double-clicking.2. Create an append structure for this include.


○ Copy the field names under Component . Then append the field name _R . Under Component Type , assign the data element BAPIUPDATE to each field.

3. Save and activate your entries.



Example

You have chosen the field MAXEOQ_POD. The field MAXEOQ_POD comes from the tables /SAPAPO/MATLSPP and /SAPAPO/MATLOC.

You enter ZMATLOC_R_APPEND as the name the append structure.

You copy the field name MAXEOQ_POD under Component , add _R to extend the field name to MAXEOQ_POD_R, and copy the data element BAPIUPDATE under component type.

5.3 Hierarchy

Definition

Hierarchies serve to depict hierarchical relationships between the master data objects of an object type. Hierarchies are based on hierarchy structures and can be created, changed, and deleted in the course of hierarchy maintenance.

Hierarchies can be formed from the following master data object types:

● LocationFor this master data type, you could define a customer hierarchy containing customer groups with different customers for example. This could obviate the need for single-item planning.

● Location productA hierarchy of this master data type consists of location products.

● Time-dependent location productA hierarchy of this master data type consists of time-dependent location products, which are location product extended with a validity. Time-dependent location products are not independent master data objects. They can only be used in time-dependent location product hierarchies. For more information, see Maintenance of Time-Dependent Location Product Hierarchy [page 145].

● ProductA hierarchy of this master data type might consist of product family, product group, and product, for example.

● ResourceSimilar resources can be combined to form a resource group. The resources can be planned individually but can be used as a resource group in the production process model (PPM). This facilitates a rough capacity check in the entire supply chain.

● Production process model (PPM)/production data structure (PDS) (for SAP APO only)A hierarchy for a PPM or a PDS might consist of a PPM for a product group and a PPM for a product, for instance.

● Transportation zoneThe transportation zone hierarchy enables you to map a transportation zone as a set of other transportation zones. A location that is situated in one of the subordinate transportation zones is thus also situated in this superordinate zone.

To use time-dependent location product hierarchies, you must activate the business function SCM-APO, Aggregated Planning in DP, SNP and CTM ( SCM_APO_HIER_AGG_PLAN).


A master data object can occur in different hierarchies.

For more information, see Hierarchy Structure [page 142] and Maintain Hierarchy [page 142].

5.3.1 Hierarchy Structure

Definition

A structure, defined in Customizing, that forms the basis of a hierarchy. The hierarchy structure determines the following properties of each hierarchy whose basis it forms:

● Master data object type from which the hierarchy is built (for example, location)● Maximum number of levels the hierarchy can have

The Levels Excluded option enables you to define hierarchies with any number of levels.

Each hierarchy structure belongs to one of the following hierarchy structure categories:

● Hierarchy● Generated hierarchy● Schema hierarchy [page 144]● Extended hierarchy [page 144]● Adapter hierarchy

Use

Hierarchy structures are necessary prerequisites for the creation of hierarchies. For more information, see Maintain Hierarchy [page 142]. Each hierarchy is based on a hierarchy structure.

You define hierarchy structures in Customizing for SCM Basis under Master Data Hierarchy Define Hierarchy Structure . For more information, see the documentation on this Customizing activity.

5.3.2 Maintain Hierarchy

Use

Hierarchies serve to depict hierarchical relationships between master data objects. Hierarchies are based on hierarchy structures and can be created, changed, and deleted in the course of hierarchy maintenance. Hierarchies can be used in various applications.

For more information about hierarchies, see Hierarchy [page 141].



Prerequisites

You have created a hierarchy structure in Customizing. For more information, see Hierarchy Structure [page 142].

Procedure

Create and Change Hierarchies

1. On the SAP Easy Access screen, choose SCM Basis Master Data Hierarchy Maintain Hierarchy .2. Enter the name of the hierarchy you wish to create or change. You are now in hierarchy maintenance mode.3. Create a new hierarchy by adding additional subnodes (master data objects) to the uppermost node. The

number of hierarchy levels available depends on the hierarchy structure used. You can change already existing hierarchies by adding, changing, or deleting nodes.

NoteYou can also transfer the nodes of a hierarchy in the fast entry facility by double-clicking. Here you can change, insert, or delete the master data objects of the next lower level and adopt these changes in the hierarchy by using the Transfer button.

Copy Hierarchies

You can copy an existing hierarchy. However, the subnodes are not copied at the same time. In hierarchy maintenance mode, choose Change and enter the relevant data in the Copy Hierarchy dialog box.

Delete Hierarchy

To delete an existing hierarchy, on the SAP Easy Access screen, choose SCM Basis Master DataHierarchy Delete Hierarchy .

Filter Hierarchy

If a hierarchy contains too many objects, you can use a filter to display only the objects that you are interested in. You can use a filter only for hierarchies containing one of the following object types:

● Product● Location● Location product● Product data structure (PDS)

To filter objects, choose the Filter pushbutton. The system displays the selection fields for the chosen object type.


5.3.3 Schema Hierarchy

Definition

The schema hierarchy is a hierarchy structure category that differs from the structure category hierarchy in the assignment of the level numbers.

Use

In the case of the structure category hierarchy, the system pulls the levels in numerical order.

In the case of the structure category schema hierarchy, the level number is a designation that does not contain the numerical order of the levels but has significance as a number in itself. The specified value of the level number stands for the number of characters that defines the object of the level:

Level number Number of characters Object

Level 1: 3 3 characters AAA

Level 2: 5 5 characters AAA BB

Level 3: 9 9 characters AAA BB CCCC

Note that the characters of the object at the upper level must be replicated at a subordinate level so that the assignment can be recognized. Level 2 objects with the designation AA1 BB, for example, cannot be assigned here to a higher level.

Unlike hierarchy structures, the digit here has both a classification and semantic significance.

5.3.4 Extended Hierarchy

Definition

Hierarchy structure category with respect to which, in contrast to the hierarchy structure category hierarchy, a child hierarchy node can be assigned to several parent nodes.

Use

You can use an extended hierarchy if a hierarchy node is to be assigned to several parent nodes. However, the node that is assigned multiple times must always be assigned at the same hierarchy level.

An extended hierarchy can make sense in processes of transportation planning/vehicle scheduling (TP/VS), for example, in which a plant delivers materials to a customer and several alternative itineraries involving different



transshipment locations (such as ports) are available. In this case, you can use an extended hierarchy to assign a plant (hierarchy level 2) to several transshipment locations (hierarchy level 1), for example.

5.3.5 Maintenance of Time-Dependent Location Product Hierarchy

Use

Time-dependent location product hierarchies consist of time-dependent location products, which are location products that are extended with a validity period. Time-dependent location products are dependent master data objects. They can only be used in time-dependent location product hierarchies. You can use time-dependent location product hierarchies to model product structures that change over time, for example, in Demand Planning.

ExampleThe following examples illustrate the use of time-dependent location product hierarchies:

● You sell a shirt in two sleeve lengths: short and long. If you plan to sell more short-sleeved shirts in the spring, you can increase its quota for the spring period. When you release the spring forecast for the shirt from Demand Planning to Supply Network Planning, the system takes this quota into account to split the forecasts into short- and long-sleeved shirts.

● You plan to introduce a sleeveless shirt for summer. In this case, you can add the sleeveless shirt to the hierarchy for the summer period.

To use this function, you must activate the business function SCM-APO, Aggregated Planning in DP, SNP and CTM ( SCM_APO_HIER_AGG_PLAN).

Features

You can manually create time-dependent location product hierarchies. To do this, you have to create a validity period and assign it to a location product.

NoteYou can use the Reading of Time-Dependent Location Product Hierarchies Business Add-In (BAdI), if you want to use a logic for time-dependent location product hierarchies that is different from the one used in the standard system.

For more information, see Customizing for SCM Basis under Master Data Hierarchy BAdI: Reading of Time-Dependent Location Product Hierarchies .

NoteIf you assign multiple hierarchies with the same hierarchy structure type to the same model, you have to implement the BAdI: Hierarchy Change to specify which hierarchy you want to use.


For more information, see Customizing for Advanced Planning and Optimization under Supply Chain Planning Demand Planning (DP) Business Add-Ins (BAdIs) Release SNP/DP BAdI: Hierarchy Change

Maintaining Validity Periods

You can create, display, and change validity periods. A validity period can have multiple occurrences. Each occurrence is valid for a date interval. You can also select validity periods for later deletion with the Reorganize Time-Dependent Location Products function.

ExampleIf you want to maintain a validity period such as Easter that occurs every year, you enter the first validity period with occurrence 1. You then enter the following Easter with occurrence 2, and so forth.

Maintaining Time-Dependent Location Products

You can assign a validity period to a location product, display the time-dependent settings of a location product, and change the time-dependent settings of a location product.

Reorganizing Time-Dependent Location Products

You can do the following:

● You can delete validity periods that you have selected for deletion in the Maintain Validity Periods function.● You can delete the assignment between a validity period and a location product if the time-dependent

location product is not used in a time-dependent location product hierarchy.

Activities

To maintain validity periods, on the SAP Easy Access screen, choose SCM Basis Master Data HierarchyMaintain Validity Periods for Time-Dependent Location Products .

To maintain time-dependent location products, on the SAP Easy Access screen, choose SCM Basis Master Data Hierarchy Maintain Time-Dependent Location Products .

To reorganize time-dependent location products, on the SAP Easy Access screen, choose SCM BasisMaster Data Hierarchy Reorganize Time-Dependent Location Products .

5.4 Transportation Lane

Use

You need transportation lanes when planning distribution and procurement between different locations. Products can only be procured if transportation lanes exist between the possible locations.



For information on change logging for transportation lanes, see Change Logging for Master Data [page 211] .

For information on the where-used list for transportation lanes, see Where-Used List for Master Data [page 207] .

Integration

Transferring Stock from one Location to Another

You can use transportation lanes to plan stock transfers between locations. You can:

● Create a transportation lane manually in the SCM system● Store a special procurement type in the material master record in the ERP system

When a material master record is transferred with one of these special procurement types via CIF, the corresponding transportation lane between the supplying plant and the receiving plant can be created the SCM system automatically.

For more information, see Automatic Creation of Transportation Lanes [page 148] .

External Procurement Relationships

In the ERP system, the business relationship between a supplier and a plant (customer) is stored as a purchasing info record or outline agreement (contract or scheduling agreement). When you transfer this purchasing data to the SCM system, the system automatically generates external procurement relationships. At the same time, the system creates a transportation lane from the supplier to the plant. The external procurement relationship and transportation lane are assigned to each other.

For more information, see External Procurement Relationship [page 188] .

You can also assign an external procurement relationship to a transportation lane manually.

Structure

A transportation lane is specified more exactly by the following:

● The products that can be procured via this transportation lane● The means of transport that can be used for transporting the products being procured

You can create a transportation lane as follows:

● For a specific product● For a product group [page 154]

This option is displayed only if you have defined at least one product group in Customizing for the product master.

● For all products● For a specific mass selection

Note that you can only use mass selection for products that exist at both the start and destination locations.

Product Procurement Parameters


The parameters for product procurement enable the system to find the valid sources of supply in the source determination process, for example.

Means of Transport

Means of transport are used to move goods between the locations of a transportation lane. The term covers trucks, ships, aircraft etc. You assign means of transport to a transportation lane and specify the associated parameters such as the transportation duration, transportation distance, and transportation costs. The system can also calculate the straight line distance (as the crow flies) from the geographical coordinates of the location.

Product-Specific Transportation

You can assign a product-specific means of transport to one or more products. You must have already defined this means of transport in the means of transport list.

You can assign the means of transport as follows:

● You can assign a specific means of transport or all available means of transport to a product.To do so, you select a product from the Product Procurement list and choose the Create button in the Product-specific Means of Transport list.

● You can assign one product or all existing products to a means of transport.To do so, you select a means of transport from the Means of Transport list and choose the Create icon in the Product-specific Means of Transport list.

5.4.1 Automatic Creation of Transportation Lanes

Use

Transportation lanes can be created automatically as well as manually.

Transportation lanes are created automatically in the SCM system if you have transferred the following data from the ERP system via Core Interface (CIF):

● Purchasing data, such as purchasing info records, contracts, or scheduling agreements● Sales Scheduling Agreements● Material masters with a special form of procurement consisting of a procurement type F: external

procurement and a special procurement U: stock transfer.

Prerequisites

You have transferred the following data from the ERP system per CIF:

In the case of transportation lanes with reference to ERP purchasing data:

● Purchasing info records● Scheduling agreements● Contracts



To be able to transfer purchasing data, you also have to transfer plants, material master records, and vendor master records.

For more information, see Processing an External Procurement Relationship [page 191].

In the case of transportation lanes with reference to ERP sales scheduling agreements:

● Sales scheduling agreements

To be able to transfer sales scheduling agreements, you also have to transfer plants, material master records, and customer master records.

In the case of transportation lanes with reference to the special procurement type of the ERP material master record:

● Material master records

To be able to transfer material master records, you also have to transfer plants.

Features

Transportation Lanes with Reference to ERP Purchasing Data

If you have transferred purchasing data from the ERP system, the SCM system automatically creates external procurement relationships for the products concerned.

For more information, see Processing an External Procurement Relationship [page 191].

For example, if the external procurement relationship contains an info record that has a vendor as the source location and a plant as the destination location, the system creates a corresponding transportation lane running from the vendor location to the plant location.

The system links the external procurement relationship with the transportation lane. This transportation lane contains the following product procurement data:

● Validity● Form of procurement● Source of supply category● Purchasing document number● Purchasing document item● Purchasing organization● Planned delivery time● Goods receipt processing time

Transportation Lanes with Reference to Sales Scheduling Agreements

If you have transferred sales scheduling agreements from the ERP system, the SCM system automatically creates SCM sales scheduling agreements for the products concerned.

If the SCM sales scheduling agreement contains items that have a plant as a source location and a customer location as a destination location, the system creates a corresponding transportation lane running from the plant location to the customer location.


The system links the SCM sales scheduling agreement with the transportation lane. This transportation lane contains the following external procurement data:

● Sales document number● Sales item● Sales organization

Transportation Lanes with Reference to ERP Material Master Record

Storing a special procurement type with procurement type F: External Procurement and special procurement U: Stock Transfer (in the MRP 2 view of the ERP material master record), means that the material has to be procured externally from another plant (supplying plant) or transferred from another plant.

To also be able to perform stock transfers for this material in the SCM system, there has to be a transportation lane from the supplying plant to the receiving plant. If you have transferred a material with this special procurement type from the ERP system, the SCM system automatically creates a corresponding transportation lane from the supplying plant to the receiving plant for the supplying plant (from the special procurement type) and material/plant combination. The transportation lane is given the creation indicator "S" for special procurement.

CautionWhen the material master record is transferred from the ERP system to the SCM system, if there is already a manually created transportation lane with exactly the same supplying plant and receiving plant combination, this is kept and no new transportation lane is created.

Change of Supplying Plant in the Special Procurement Type

If you have changed the supplying plant in the special procurement type in the ERP system, the SCM system creates a new transportation lane for the new combination of supplying plant (from special procurement type) and material/plant. The already existing transportation lane and the now invalid combination of supplying plant and plant in the ERP system is locked for orders in the SAP APO system. This can be seen from the lock indicator X that is set by the system.

Inclusion in Source Determination

If transportation lanes (that were generated or manually created when purchasing data was transferred from the ERP system) already exist in the SCM system, the SCM system takes these transportation lanes into account when determining sources of supply. In this case, the transportation lanes that were automatically generated from the ERP material master are not taken into account.

Activities

● You can display and process automatically created transportation lanes by choosing Master DataTransportation Lanes from the SCM Basis menu.

● You can go directly from the transportation lane to its associated external procurement relationship by choosing Goto External Procurement Rel.

● You can go directly from the transportation lane to its associated sales scheduling agreement by choosing Goto Sales Scheduling Agreements.



5.4.2 Create Transportation Lanes

Use

A transportation lane represents a direct path between two locations that you can use to transport goods in both directions. Each lane is defined by its source and destination location, depending on the direction of traffic. Products that are transported along the route are assigned to the transportation lane. Furthermore, available means of transport are assigned to each transportation lane.

Prerequisites

You have created locations. If you work with SAP Advanced Planning and Optimization (SAP APO), you must have assigned thise locations to the supply chain model.

Procedure

1. From the SCM Basis menu, choose Master Data Transportation Lanes .2. Enter the model name.3. Enter the source and destination location.4. Choose Create .5. Click the Header Data button. The detail view appears on the right. The source and destination locations

are displayed in the General Data area.6. Enter a description and transportation planner (optional).7. Enter the procurement options and the means of transport for the transportation lane.

5.4.3 Transportation Lane Maintenance Screen

Use

On this screen you can:

● Define product procurement for a transportation lane● Define the means of transport for a transportation lane● Define the product-specific assignment of means of transport● Assign transportation service providers to a means of transport● Launch a queryto view all assignments that are valid for a certain lane


Structure

The maintenance view for transportation lanes consists of a control bar and several tables, plus an optional detail view for maintenance.

Transportation Lane Maintenance Screen

Header controls

● Header data● Product-specific means of transport● External transportation service provider assignment● Lane overview

Tables

Transportation lane maintenance consists of 4 parts. The details are shown in the tables that appear in this view. Each table has its own controls with standard functionality. The tables include:

● Product procurement [page 153]● Means of transport [page 155]● Product-specific means of transport [page 159] OR

assignment of external transportation service provider [page 161]

● To save space, these two tables replace each other. You can toggle back and forth between them using the header icons.

● Lane overview [page 163] (appears only when icon is activated) Total procurement/transportation.

Detail view You can open the detail view of a table in the following ways:

● Click on the Create icon in the table control header● Double-click on a selected row in the table● Select a row and click on the Detail icon in the table con

trol header

Close the detail view using one of the icons at the top of the screen:

● Close (without copying data)● Adopt (the data is copied into the maintenance table on

the left)● Adopt and Close (the data is copied into the left-hand

table and parameter maintenance is closed)



5.4.4 Defining Product Procurement

Use

Use this procedure to define the parameters for the procurement of products. The procurement parameters include:

● Validity period● Minimum and maximum lot sizes● Purchase costs of a unit● Priorities● Cost function● Procurement method

Prerequisites

● You have created transportation lanes.● You have maintained the product master data.● You have assigned the products to the locations.

Procedure

1. From the SCM Basis menu, choose Master Data Transportation Lanes . Enter the model name, the source location, and the destination location of the transportation lane for which you want to maintain product procurement.

2. Choose Edit.The Change Transportation Lane screen appears.

3. Choose Create in the Product Procurement heading line for new product procurements or choose the line containing the product you want to maintain and double-click it.The Product Procurement detail view appears on the right.

4. Maintain the following parameters:

If you choose Create , you have three options on the right-hand side:

● Choose a single product via the standard selection view● Select a product group

This option is displayed only if you have defined at least one product group [page 120] in Customizing for the product master.

● Select all products● Mass selection for multiple entrie s


Validity Enter the start and end date of the period for this product procurement.

Lot sizes Enter the minimum and maximum lot sizes. If no entry is made here, product procurement applies to all lot sizes.

Procurement costs Specify the product procurement costs per base unit at the procurement point.

Priority Define the procurement and distribution priorities.

Cost function Choose a cost function from the input help.

Lock indicator Set this indicator if you want to block the source of supply as a procurement option orders.

Form of procurement Choose the form of procurement:

● Standard● Subcontracting● Consignmen t

Assign a procurement relationship This optional activity is possible only in the active model. It allows you to assign ERP orders toproducts. Procurement relationships are maintained in the procurement master data.

1. Use one of the icons at the top of the detail view to end this transaction:○ Close (without copying data)○ Adopt (the data is copied into the maintenance table on the left)○ Adopt and Close (the data is copied into the left-hand table and parameter maintenance is closed)

2. To delete an entry from the Product Procurement table, select the product and choose Delete .3. To open the detail view, choose Details .

Result

If you chose a copy option in step 7, you can now maintain the product procurement attributes in the Product Procurement table.

5.4.4.1 Transportation Lanes for Product Groups

Use

You can define a transportation lane for one or more product groups of a product group type. This accelerates and simplifies the maintenance of transportation lanes.



Prerequisites

● You have defined at least one product group type in Customizing for the product master under Product Groups Define Product Group Types .

● You have defined at least one product group for this product group type in Customizing for the product master under Product Groups Define Product Groups .

● You have set the Relevant to Transportation Lanes indicator for a product group type in Customizing for the product master under Product Groups Define Product Group Types . This product group type is displayed on the maintenance screen for transportation lanes.If you have not set this indicator, the system does not show the Product Group Type and Product Group fields on the maintenance screen for transportation lanes.

Activities

Maintain a product group for a transportation lane on the maintenance screen for transportation lanes. The transportation lane is automatically valid for all the products of this product group.

5.4.5 Defining Means of Transport

Use

Use this procedure to define the parameters for means of transport.

Prerequisites

You created transportation lanes.

You have maintained the product master data.

You have created a means of transport in Customizing for master data under Transportation Lane Create Means of Transport

Procedure

From the SCM Basis menu, choose Master Data Transportation Lanes

Enter a model name for the source and destination location of the transportation lane for which you want to maintain a means of transport.

Choose Edit. The Change Transportation Lane screen appears.


In the Means of Transport table, choose Create or choose the line containing the means of transport that you want to maintain by double-clicking on it. The means of transport maintenance screen appears.

Maintain the following settings:

ValidityEnter the start and end date of the period to which this parameter relates.

Control indicator Set this indicator ...

All Products If you want this means of transport for which procurement has been defined to apply.If this indicator is not set, the means of transport applies only to those products that have been explicitly assigned to the means of transport.

For more information on the effects of setting this indicator, see also: Validity of Product Procurement and Means of Transport [page 163]

Aggregated Planning If the means of transport is valid for aggregated planning. For example, for Network Design or Supply Network Planning

Detailed Planning For detailed planning in Transportation Planning and Vehicle Scheduling (TP/VS)

Fixed Transportation Duration If you do not want this setting to be overwritten by automatic calculation (when maintaining new transportation lanes, for instance)

Fixed Transportation Distance If you do not want this setting to be overwritten by an automatic calculation of distance factors when maintaining new transportation lanes.

Discrete Means of Transport For means of transport optimization calculated in whole numbers (i.e. no half-loads on a truck). Relevant to SNP only



ValidityEnter the start and end date of the period to which this parameter relates.

Control indicator Set this indicator ...

Parameters Maintain the following parameters:

Transportation calendar (APO Customizing)

Duration of transportation

Additional stop duration

Transportation costs per unit of measure

Cost function

Resource

Means of transport costs

TLB profile

Transportation time rounding

Note

The duration of transportation is specified in hours and minutes (for example: 12:22) and refers to the net duration (i.e. the actual time in motion). Bucket-oriented planning applications such as SNP calculate the gross duration using the following formula:

Net duration divided by average working time, or time in motion, for example the number of hours driven in one day.

Gross duration of transportation refers to the time between arrival and departure.

Description (short text) Text describing the assignment of a means of transport to a transportation lane

Use one of the icons at the top of the maintenance view to exit this transaction:

Close (without copying data)

Adopt (the data is copied into the maintenance table on the left)

Adopt and Close (the data is copied into the left-hand table and parameter maintenance is closed)

To delete an entry from the Means of Transport table, select the means of transport and choose Delete .

Result

If you chose the Adopt option in step 5, you can now maintain the attributes directly in the Means of Transport table.


5.4.5.1 Means-of-Transport Combination

Definition

Grouping of multiple means of transport.

Use

You use means-of-transport combinations to model vehicle combinations. A vehicle combination is a grouping that consists of one vehicle and at least one trailer that move together. You can use one means-of-transport combination to map multiple vehicle combinations (see Example section).

Structure

When you define a means-of-transport combination, you define the following:

● Means of transport that the combination is to consist of, in other words, those means of transport that are permitted for the combination

NoteA means-of-transport combination must consist of one means of transport (vehicle) that can move itself and at least one passive means of transport (trailer).

● Number of individual means of transport within the combination● Total capacity of the means-of-transport combination

NoteThe total capacity is the maximum loading capacity (without the tare weight of the vehicle and trailers).

● AttributesYou use attributes to define compatibilities and incompatibilities.

Integration

● You define means-of-transport combinations in Customizing for SCM Basis.For more information, see the Implementation Guide (IMG) for SCM Basis under Master Data Trailers and Compartments Define Means-of-Transport Combination.



● If the vehicle is not to have its own capacity, you must set the No Capacity indicator for the relevant means of transport. To do so, on the SAP Easy Access screen for SCM Basis, choose Master DataTransportation Lane Maintain Means of Transport.

● You can define compatibilities and incompatibilities for means-of transport combinations.

Example

The following table shows the vehicle resources and means of transport you have defined and the assignments you have made:

Vehicle Resource Means of Transport

TRUCK1 (Vehicle) MTRTRUCK

TRUCK2 (Vehicle) MTRTRUCK

TRAILER1 (Trailer) MTRTRAILER

TRAILER2 (Trailer) MTRTRAILER

You can model the following vehicle combinations with a means-of-transport combination 1TRAIL consisting of both means of transport:

● TRUCK1 + TRAILER1● TRUCK2 + TRAILER2● TRUCK1 + TRAILER2● TRUCK2 + TRAILER1

5.4.6 Assign Products to Means of Transport

Use

In this step you assign one or more products that has/have already been assigned to a transportation lane to a means of transport.

Prerequisites

● You have created a transportation lane.● You have assigned the product to the source or destination location.● You have maintained settings for product procurement.● You have maintained the settings for the means of transport.


Procedure

1. Invoke the maintenance view for transportation lanes in change mode.2. Choose the Product Procurement table. In the Product Procurement table, select the product you want to

assign to a means of transport by clicking in the selection box at the beginning of the line. The entire line is highlighted.

NoteProducts can only be assigned individually or using the mass selection button. It is not possible to assign a means of transport to an All Products entry.

3. From the Product Procurement table header, choose the icon : Assign Means of transport to Product .4. Choose Create . The detail view for assigning products to means of transport appears on the right.5. Enter the necessary data as described in the table below.6. Use one of the icons at the top of the maintenance view to exit this transaction:

○ Close (without copying data)○ Adopt○ Adopt and close (the data is copied and the maintenance view closed)

Maintain the detail view

If you selected Product Use the selection icon in the detail view to choose a valid means of transport.

If you selected Means of Transport Use the selection icon in the detail view to choose a valid transportation procurement

Validity of product-specific means of transport assignment Results of the overlap between the validity dates for the product and the means of transport

Means of Transport Restriction indicator Set this indicator if the means of transport is not defined for this product.

For more information about the effects of setting this indicator, see also: Validity of Product Procurement and Means of Transport [page 163]

Parameters Set the following parameters:

● Transportation costs per base unit of measure● Consumption: to determine which part of a transporta

tion resource is reserved for a certain base unit of measure

● Lot size profile● Stacking factor, which shows how many pallets of this

product can be stacked on top of each other. If you make no entry, the system assumes the product cannot be stacked .

Result



If you chose a copy option in step 6, the product or means of transport assignment appears in the table.

5.4.7 Assign External Transportation Service Provider

Use

In this step, you assign external transportation service providers to the means of transport that are assigned to a transportation lane. For example, you could assign the means of transport Truck to logistics company A and logistics company B.

Prerequisites

You have maintained transportation service providers in the location master.

Procedure

1. Invoke the maintenance view for transportation lanes in change mode.2. Choose a means of transport from the table for means of transport. The entire line is highlighted.3. Choose Assignment of Transportation Service Provider

The External Transportation Service Provider Assignment view appears, which replaces the lower table.4. Choose Create .

The detail view for creating transportation service providers appears on the right.5. Enter the necessary data as described in the table below.6. Use one of the icons at the top of the maintenance view to exit this transaction:

○ Close (without copying data)○ Adopt (copy data into the External Transportation Service Provider Assignment view on the right)○ Adopt and close (the data is copied and the maintenance view closed)

Transportation service provider Choose a transportation service provider from the input help .

Parameters Set the following parameters:

○ Transportation costs per unit of measure○ Costs for transportation service provider○ Priority○ Assignment of business share (for example, 50% )


Result

If you chose a copy option in step 6, the transportation service provider assignment appears in the table.

5.4.8 Create Multiple Lanes

Use

The mass maintenance of several transportation lanes simplifies the maintenance of large volumes of of supply chain transportation data. This function is particularly useful if you want to create transportation lanes between several source and destination locations (for example, between selected plants and customers).

Prerequisites

Transportation lanes have been created.

Procedure

1. From the SCM Basis menu, choose Master Data Mass Creation of Transportation Lanes .2. Enter the source location and destination locations of the transportation lane you want to use as a

template.3. Enter the source and destination locations for the new transportation lanes. You can also enter a range of

locations. See example below.4. Maintain any other applicable selection criteria such as the location type or the maximum and minimum

distances.5. Choose Execute .

Result

The system creates new transportation lanes between the specified locations. Each new lane is an exact copy of the template. Individual maintenance may therefore be required. However, product procurement entries are only copied if the product exists at both locations. For information on maintaining the settings for product procurement and transportation lanes, see Transportation Lane Maintenance [page 146] .

NoteExisting transportation lanes are not overwritten.



Example

Create multiple transportation lanes

Model name Model X

Copy from:

Source location A

Destination location B

Create lanes for:

Source locations All plants

Destination location All DCs

Minimum distance: 100 km

Maximum distance 1000 km

The system creates transportation lanes between all the plants in the specified region and all distribution centers that are more than 100 km and less than 1000 km away. The new transportation lanes are copies of the transportation lane in model X.

5.4.9 Validity of Product Procurement and Means of Transport

Use

The validity of product procurement and means of transport depends on the various settings and assignments you make when you maintain transportation lanes. Use this table to get a general overview of the validity situation for the lanes in your network

Structure

The transportation lane overview is part of Transportation Lane Maintenance , but it is only visible if you activate Total Procurement/Transport in the header line. The lane overview shows the relationship between the product procurement assignments and transportation lane settings that you make in the view for transportation lanes.

Transportation Lane Maintenance screen


Table: Total Procurement and Transportation of Products

If product procurement is product specific, that is, you did NOT select All Products in the Product Procurement table, you will have the following results for the following setting/assignment combinations:

Means of transport Assignment of product-specific means of transport Lane overview result: Is product valid for means of transport?

Validity indicator All Products set.

Defined Yes

Not defined Yes

Defined, means of transport indicator set

No

Validity indicator All Products NOT set

Defined Yes

Not defined No

Defined, means of transport indicator set

No

If product procurement is valid for ALL products:

Means of transport Lane overview result: Is product valid for means of transport?



If product procurement is product specific, that is, you did NOT select All Products in the Product Procurement table, you will have the following results for the following setting/assignment combinations:

Validity indicator All Products set. Yes

Validity indicator All Products NOT set No

For more information on the various settings, see:

Transportation Lane Maintenance [page 146]

5.4.10 Deleting Product-Specific Transportation Lanes

Use

Product-specific transportation lanes for which the deletion flag has been set can be deleted using report /SAPAPO/TR_TRPROD_DELETE. The deletion flag can be set in the following cases:

● The indicator was set manually for the transportation lane.● The transportation lane was transferred from the ERP system using the Core Interface (CIF).

The report automatically deletes only those transportation lanes that do not have any dependencies.

NoteTo see which transportation lanes the report would delete, perform a simulation run before actually deleting. To do so, set the Simulation indicator. Then run the report without this indicator.

Prior to deleting, you can also perform the where-used list [page 207] function.

5.4.11 Distance and Duration Determination

Use

You can use this function to determine the distance of a transportation lane and the duration it takes the means of transport to travel that distance. The system determines the distance and duration in the following ways:

● The system calculates the shortest distance (line of flight) between locations.● The system calculates the precise distance between locations based on the means of transport by using a

third-party geographic information system (GIS).

The distance and duration determination (DDD) uses geocoordinates that are stored in the system for each location. For a more precise determination of distances and durations, you can use geocoding levels and DDD strategies to define on which level of detail you want to determine the distance and duration. For example you can determine the distance and duration based on the house number, the postal code or the region of the location's address. If the distance between a start and a destination location is very large, you may not need to


use the most detailed geocoordinates to determine the distances and durations as it does not affect the business process significantly.

To use this function, you must have activated the business function Enhanced Services for Transportation Network [page 14]( SCM_SCMB_TR_NETWORK).

Prerequisites

For information, see Settings for Distance and Duration Determination [page 167].

Features

Precalculating Distances and Durations for the DDD Buffer

The retrieval of data from a GIS can be time consuming and it can affect the performance of the system. For this reason, you can store retrieved data in the DDD buffering table. You can use the Precalculation of Distance and Duration Determination report to precalculate the distance and duration for a set of start and destination locations and save the result in the distance and duration determination (DDD) buffer. For large volumes of data you can also run background jobs for this function. For more information, see Precalculation of Distance and Duration Determination [page 169].

Deleting Buffered Distances and Durations

You can use the Deletion of Buffered Distances and Durations report to delete obsolete entries from the distance and duration determination (DDD) buffer. For more information, see Deletion of Buffered Distances and Durations [page 171].

Determining the Distance and Duration for a Single Transportation Lane

You can determine distances and durations for a single transportation lane. For more information, see Determining the Distance and Duration for a Single Transportation Lane [page 168].

Determining the Distance and Duration for Multiple Transportation Lanes

You can determine distances and durations for multiple transportation lanes. For more information, see Determining the Distance and Duration for Multiple Transportation Lanes [page 169].

More Information

For more information about geocoding, see Geocoding [page 94].



5.4.11.1 Settings for Distance and Duration Determination

Use

Determining Distance and Duration Based on the Shortest Distance

If you want the system to determine the distance and duration for the shortest distance (line of flight) between two locations, you have done the following:

● In Customizing for SCM Basis under Master Data Transportation Lane Maintain Means of Transport you have made the following settings:○ You have defined means of transport and specified the average speed and the distance factor for them.○ You have deactivated the GIS Qlty (GIS Quality) checkbox.

● You have defined locations in the location master. If you have entered address data for the location, the system calculates the geographical data for the location as well as any additional geocoordinates based on geocoordinate determination strategies you have maintained. The system uses the geographical data of a location as a basis for the DDD.

Determining Distance and Duration by Means of a GIS

If you want the system to determine the distance and the duration by means of a geographic information system (GIS), you have done the following:

● You have installed a third-party GIS and connected it to the internet graphics server (IGS) or you have used the process controller to create your own DDD strategy and method.

● In Customizing for SCM Basis under Master Data Transportation Lane Distance and Duration Determination Set Usage of GIS Tool you have set the usage of the GIS. If you want to use a GIS connected using a IGS, you have to specify the RFC destination as well. If you use a GIS connected with process controller strategy you have defined, no RFC destination is necessary.

● You have maintained means of transport for which you have specified the low, medium, and high speeds, and you have activated the GIS Qlty (GIS Quality) checkbox in Customizing for SCM Basis under Master Data Transportation Lane Maintain Means of Transport .

NoteIf you do not make any entries for the speeds, the system can determine the distance but not the duration. In this case, the system uses a standard value for the duration.

● If you want to determine distances and durations on the basis of specified geocoordinates, you have done the following in Customizing for SCM Basis under Master Data Transportation Lane Distance and Duration Determination :○ You have defined GIS zones for use in the DDD strategies under Define GIS Zone○ You have assigned countries to the GIS zones for use in the DDD strategies under Assign Country to

GIS Zone○ You have defined DDD strategies under Define Strategy for Distance and Duration Determination○ You have maintained global settings for the buffering of DDDs under Maintain Global Settings for

Buffering of DDD


To make settings in Customizing for SCM Basis under Master Data Transportation Lane Distance and Duration Determination , you must have activated the business function Enhanced Services for Transportation Network [page 14]( SCM_SCMB_TR_NETWORK).

More Information

For more information about the process controller, see Process Controller [page 270].

For more information about the IGS, see Internet Graphics Service.

5.4.11.2 Determining the Distance and Duration for a Single Transportation Lane

Procedure

1. Define a transportation lane.2. Display the detail screen for the means of transport and switch to change mode.3. On the detail screen, in the Parameters frame, choose Generate Proposal.

Results

The system determines the distance and duration on the basis of either a geographic information system or the shortest distance (depending on the assigned means of transport) and enters values in the Transptn Distance (Transportation Distance) and Trsp. Duration (Transportation Duration) input fields.

NoteYou can enter values for the distance and duration manually when defining a transportation lane.

Next Steps

For more information about distance and duration determination, see Distance and Duration Determination [page 165].

For more information about creating transportation lanes, see Create Transportation Lanes [page 151].



https://help.sap.com/viewer/3348e831f4024f2db0251e9daa08b783/7.5.16/en-US/4e193ea5b5c617e2e10000000a42189b.html

5.4.11.3 Determining the Distance and Duration for Multiple Transportation Lanes

Procedure

1. Define multiple transportation lanes in the Mass Creation of Transportation Lanes report.2. In the Transport Duration and Distances frame, choose either of the following:

○ Calculate transport durations and distancesThe system redetermines the distances and duration for the transportation lanes created. It determines the values on the basis of either a GIS or the shortest distance and enters values in the Transptn Distance and Trsp. Duration input fields of the means of transport.

○ Adopt Transport. Duration and Distances from TemplateThe system reuses the distances and duration of the transportation lane that is used as a template and enters values in the Transptn Distance and Trsp. Duration input fields of the means of transport.

When you run mass maintenance, you need to run the Precalculate Distances and Durations for the DDD Buffer report. The system determines the distances and durations for all the transportation lanes created.

To run the report, in the Easy Access screen, choose SCM Basis Master Data Transportation LanesDistance and Duration Determination Precalculate Distances and Durations for the DDD Buffer .

More Information

For more information about distance and duration determination, see Distance and Duration Determination [page 165].

For more information about creating transportation lanes, see Create Transportation Lanes [page 151].

For more information about the precalculation of distances and durations, see Precalculation of Distance and Duration Determination [page 169].

5.4.11.4 Precalculation of Distance and Duration Determination

Use

You can use this function to precalculate the distance and duration for a set of start and destination locations and save the result in the distance and duration determination (DDD) buffer. For large volumes of data you can also run background jobs for this function.

The precalculation of distances and durations speeds up the distance and duration determination by storing already calculated results for later reuse. You can either add new entries only to the buffer or you can overwrite already existing buffer entries. You can also simulate the selection. By simulating, the report displays the


selected entries that the system potentially adds to the buffer. The system does not make any changes to the buffer. You set up your selection based on the following data:

● DDD strategyYou select a DDD strategy and a geocoding level that you want to use for the distance and duration determination. If you enter a DDD strategy and leave the Geocoding Level field empty, the system precalculates the distance and duration for all geocoding levels of the locations. If you want the system to set the DDD strategy and the geocoding level dependent on the settings in the DDD strategy Customizing, you can also select the Strategy Determination checkbox.

● Means of transportYou can select one or several means of transport. The system uses the means of transport for the distance and duration calculation. If you leave the Means of Transport field empty, the system uses all means of transports maintained in the system. The system calculates the distance and duration for all selected start and destination location pairs in combination with all selected means of transport.

● Start and destination locationYou can select a set of start and destination locations for the distance and duration calculation.

By selecting the Use Only Existing Transportation Lanes checkbox, the system only selects combinations that have start and destination locations with a corresponding transportation lane maintained. If you do not select the Use Only Existing Transportation Lanes checkbox, the system considers all combinations between the start and destination locations. Combinations with identical start and destination are ignored.


Prerequisites

You have defined strategies for distance and duration determination in the process controller. The strategies provide the connection to your GIS provider. You can define your own strategy or use the standard strategy DDD_STD.

You define strategies in Customizing for SCM Basis under Process Controller Define Strategies . For more information, see Process Controller [page 270].

NoteThe system updates the DDD buffer by means of the DDD strategies, so the strategies you use must contain the standard method for the update of the buffer.

You have determined geocoordinates for all start and destination locations. You maintain geocoordinates with the Mass Geocoding report. To run the Mass Geocoding report, on the SAP Easy Access screen choose

Master Data Location Geocoding Mass Geocoding .



Activities

To precalculate the distances and durations, on the SAP Easy Access screen choose SCM Basis Master Data Transportation Lane Distance and Duration Determination Precalculate Distances and Durations for the DDD Buffer .

To precalculate the distances and durations as a background job, on the SAP Easy Access screen choose SCM Basis Master Data Transportation Lane Distance and Duration Determination Precalculate

Distances and Durations for the DDD Buffer in Batch

5.4.11.5 Deletion of Buffered Distances and Durations

Use

You can use this function to delete obsolete entries from the distance and duration determination (DDD) buffer. For large volumes of data you can also run background jobs for this function.

You delete entries that are no longer needed or entries that are invalid because of a change in the system setup, for example a new GIS Provider has been defined with a new strategy or a geocoding level has been removed. It is also possible to delete old entries dependent on their last change or access date.

You set up your selection based on the following data:

● Strategy selectionYou can set up the strategy selection as follows:○ If you want to delete buffer entries with a specific strategy and a specific geocoding level only, you

select a DDD strategy and a geocoding level.○ If you want to delete all entries with a certain strategy regardless of the geocoding level, you select a

DDD strategy and leave the Geocoding Level field empty.○ To delete all entries with a specific geocoding level, regardless of the strategy, you can leave the

Strategy field empty and select a specific geocoding level.○ If you leave both fields empty, the system deletes all combinations of strategy and geocoding level in

the selection.● Means of transport

You can select one or several means of transport if you want to delete buffer entries with specific means of transport only. If you leave the Means of Transport field empty, the report uses all means of transports maintained in the system.

● Time-dependent selectionYou can select buffer entries for the deletion dependent on the date they were last changed or accessed.

● Start and destination location selectionYou can select a set of start and destination locations to delete only buffer entries with selected locations.

By selecting the Use Only Existing Transportation Lanes checkbox, the system only selects combinations between the start and destination locations that have a corresponding transportation lane maintained. If you do not select the Use Only Existing Transportation Lanes checkbox, the system considers all combinations between the start and destination locations. Combinations with identical start and destination are ignored.



Prerequisites

You specify the interval in which the system updates the last access date for the time-dependent selection in Customizing for SCM Basis under Master Data Transportation Lane Distance and Duration Determination

Maintain Global Settings for Buffering of DDD .

Activities

To delete distances and durations, on the SAP Easy Access screen choose SCM Basis Master DataTransportation Lane Distance and Duration Determination Delete Buffered Distances and Durations .

To delete distances and durations as a background job, on the SAP Easy Access screen choose SCM BasisMaster Data Transportation Lane Distance and Duration Determination Delete Buffered Distances and Durations in Batch .

5.4.11.6 Checking and Repairing the DDD Buffer Table

Use

You use the Check and Repair Buffering Table report to check and repair any inconsistencies that might occur in the distance and duration determination (DDD) buffering table. You can do the following with the report:

● Delete all entries in the buffering table● Check the following for consistency:

○ Means of transport○ DDD strategies○ Locations


Activities

To access this report, on the SAP Easy Access screen, choose SCM Basis Master Data Transportation Lane Distance and Duration Determination .



More Information

For more information about DDD, see Distance and Duration Determination [page 165].

5.4.12 Lane, Distance, and Duration Determination (LDDD)

Use

The system uses this function to determine the most specific transportation lane for your transportation process. The lane, distance, and duration determination (LDDD) considers the hierarchy of the means of transport and the hierarchy of the transportation zone at the source and destination location. In addition to determining the transportation lane, the system determines the distance of the lane and the duration it takes the means of transport to travel that distance. For more information, see Distance and Duration Determination [page 165].

Prerequisites

● In Customizing, you have defined means of transport to which you have assigned superordinate means of transport. For more information, see Customizing for SCM Basis under Master Data Transportation Lane Maintain Means of Transport .

● You have defined hierarchies for the source location or zone and the destination location or zone.● You have defined transportation lanes.

5.5 Trailers and Compartments

Use

You can define compartments [page 175] for your vehicle resources. You can also define trailers [page 174] and combine these with vehicles to create vehicle combinations. To do this, you use means-of-transport combinations [page 158] .

See also:

Examples of Compartments [page 176]


5.5.1 Trailer

Definition

Vehicle resource that cannot move by itself.

Use

You can couple trailers to vehicles. As a result, you create vehicle combinations. For more information, see Means-of-Transport Combination [page 158] .

Integration

● You define trailers by defining a vehicle resource and then setting the Passive indicator for the relevant means of transport in the means of transport definition. To do so, on the SAP Easy Access screen for SCM Basis, choose Master Data Transportation Lane Maintain Means of Transport.

● To be able to work with trailers in the Transportation Planning/Vehicle Scheduling (TP/VS) component, you must set the Activate Trailer indicator in Customizing for TP/VS. For more information, see the Implementation Guide (IMG) for TP/VS under Trailers and Compartments Activate Trailers and Compartments .

● In Customizing for SCM Basis, you can define a coupling duration and an uncoupling duration for your trailers. For more information, see the Implementation Guide (IMG) for SCM Basis under Master DataTrailers and Compartments Define Coupling/Uncoupling Duration.The system creates a coupling activity and an uncoupling activity for each trailer that is assigned to a shipment.The system generates the coupling activity after the loading activities that you use to load freight units onto the trailer, in other words, directly before the transportation activity for the assigned vehicle.The system schedules the uncoupling activity if a trailer is no longer to be moved by the same vehicle in the next stage. If the system has assigned an empty trailer to a stage, it schedules the coupling activity directly before the transportation activity and the uncoupling activity directly after the transportation activity.The compatibilities and incompatibilities as well as the means-of-transport combinations that you have defined determine whether or not a trailer can be coupled to a vehicle. In multilevel planning, you can override these settings manually.You cannot couple trailers to schedule vehicles.

● The system takes into account trailers in VSR optimization and in multilevel planning in TP/VS as well as in VSR optimization and in manual planning in SAP Transportation Management (SAP TM).

● You cannot define schedules for trailers (TP/VS and SAP TM).● Dynamic route determination in TP/VS does not support trailers. For more information, see SAP Library on

SAP Help Portal at http://help.sap.com SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and Optimization (SAP APO) Transportation Management Transportation Planning/Vehicle Scheduling (TP/VS) Dynamic Route Determination .



5.5.2 Compartment

Definition

Part of the loading space of a vehicle resource (vehicle or trailer).

Use

You use compartments for the following, for example:

● You have to separate two freight units on a truck because they contain refrigerated goods and fruit.● You want to transport diesel and super fuel in one tanker.

Structure

You define compartments by using compartment types. You can define a fixed number of compartments per vehicle resource (vehicle or trailer).

For each compartment, you can define a capacity per dimension. The capacity consumption within a compartment is linear. By defining steps, you can model a capacity consumption on the basis of the step. This is recommended if the compartment has a door, or if you want to work with movable partitions, for example.

The relationship between the total capacity of the vehicle resource and the total capacity of all assigned compartments determines whether the individual compartments are fixed or flexible. This is not an attribute of the compartment. A vehicle resource with fixed compartments means that the total capacity of all assigned compartments is the same as the total capacity of the vehicle resource. A vehicle resource with flexible compartments means that the total capacity of all assigned compartments is greater than the total capacity of the vehicle resource. For more information, see Examples of Compartments [page 176] .

The system takes into account compartments in VSR optimization and in manual planning in the Transportation Planning/Vehicle Scheduling(TP/VS) component, as well as in SAP Transportation Management (SAP TM).

Integration

● You define compartment types in Customizing for SCM Basis. You use the compartment type to define the capacity of the compartment, possible steps, and a compartment profile, for example. In the compartment profile, you specify the number and type of compartments that a means of transport is to have. You then assign this compartment profile to the means of transport.For more information, see the Implementation Guide (IMG) for SCM Basis under Master DataTrailers and Compartments Define Compartment Type.

● To be able to work with compartments in TP/VS, you must set the Activate Comps indicator in Customizing for Transportation Planning/Vehicle Scheduling (TP/VS).


For more information, see the IMG for TP/VS under Trailers and Compartments Activate Trailers and Compartments .

● You have defined a number range for the handling unit Compartment Type in TP/VS.For more information, see the IMG for TP/VS under Basic Settings Define Number Range for HU Compartment Type .

● You have assigned packaging materials to means of transport and compartment types in TP/VS.For more information, see the IMG for TP/VS under Interfaces Maintain Mapping Table for Vehicles/Compartment Type .

● You can define compatibilities and incompatibilities for compartments.● Dynamic route determination in TP/VS does not support compartments. For more information, see SAP

Library on SAP Help Portal at http://help.sap.com SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and Optimization (SAP APO) Transportation Management Transportation Planning/Vehicle Scheduling (TP/VS) Dynamic Route Determination .

5.5.2.1 Examples of Compartments

Fixed Compartments

In this example, the vehicle resource comprises three compartments with the compartment type X. Each compartment has a maximum capacity of 5 m 3 . The total capacity of the vehicle resource is 15m 3 .



Flexible Compartments (Without Steps)

In this example, the vehicle resource comprises two compartments with the compartment type X. Each compartment has a maximum capacity of 10m 3 . The total capacity of the vehicle resource is 15m 3 , in other words, you are not allowed to load more than 15m 3 onto the vehicle resource.


Flexible Compartments (with Steps)

In this example, the vehicle resource comprises one compartment with the compartment type X. The compartment has a maximum capacity of 15 m 3 . The total capacity of the vehicle resource is 15m 3 . The compartment has three steps (5 m 3 , 10 m 3 , and 15m 3 ).

This means the following for the compartment:

● Zero consumption is not possible for the compartment. That means if you do not load this compartment, it still consumes a capacity of 5m 3 .

● Each load that is greater than or equal to 0 m 3 but less than or equal to 5m 3 results in a capacity consumption of 5m 3 . That means if you load this compartment with 3m 3 , for example, it still consumes a capacity of 5m 3 .

● Each load that is greater than 5 m 3 but less than or equal to 10m 3 results in a capacity consumption of 10m 3 .




NoteIn a realistic scenario, you would define a second compartment, for example, a flexible compartment without steps.

Flexible Compartments (Zero Consumption Is Not Possible)

In this example, the vehicle resource comprises two compartments. Compartment 1 has compartment type X, compartment 2 has compartment type Y. Each compartment has a maximum capacity of 10m 3 . The total capacity of the vehicle resource is 15m 3 . Compartment 1 has a door and a step (5m 3 ). Compartment 2 does not have any steps.


This means the following for the two compartments:

Compartment 1:

● Zero consumption is not possible for the compartment. That means if you do not load this compartment, it still consumes a capacity of 5m 3 .

● Each load that is greater than or equal to 0 m 3 but less than or equal to 5m 3 results in a capacity consumption of 5m 3 .

● Each load x that is greater than 5 m 3 but less than or equal to 10m 3 results in a capacity consumption of x m 3 .

Compartment 2:

Each load xm 3 results in a capacity consumption of xm 3 (linear capacity consumption).

Flexible Compartments (Zero Consumption Is Possible)

Example 1



In this example, the vehicle resource comprises two compartments. Compartment 1 has compartment type X and a maximum capacity of 10m 3 . Compartment 2 has compartment type Y and a maximum capacity of 15m 3 . The total capacity of the vehicle resource is 15m 3 . Compartment 1 has two steps (0m 3 and 5m 3 ). Compartment 2 does not have any steps.


Compartment 1:

● Zero consumption is possible for the compartment. That means if you leave this compartment empty, it does not consume any capacity.

● Each load that is greater than 0 m 3 but less than or equal to 5m 3 results in a capacity consumption of 5m 3 . This compartment might be a refrigerated part with a door, for example. As soon as you load one frozen pizza, you have to turn on the refrigerated part. The second compartment has to start behind the door.

● Each load x that is greater than 5 m 3 but less than or equal to 10m 3 results in a capacity consumption of x m 3 (due to the maximum capacity).

Compartment 2:

Each load xm 3 results in a capacity consumption of xm 3 (linear capacity consumption).

Example 2


In this example, the vehicle resource comprises two compartments. Compartment 1 has compartment type X and a maximum capacity of 10m 3 . Compartment 2 has compartment type Y and a maximum capacity of 15m 3 . The total capacity of the vehicle resource is 15m 3 . Compartment1 has four steps (0m 3 , 5m 3 , 8m 3 , and 10m 3 ). Compartment2 also has four steps (5m 3 , 7m 3 , 10m 3 , and 15m 3 ). There are two doors.


Compartment 1:

● Zero consumption is possible for the compartment.● Each load that is greater than 0 m 3 but less than or equal to 5m 3 results in a capacity consumption of 5m

3 .● Each load x that is greater than 5 m 3 but less than or equal to 8 m 3 results in a capacity consumption

ofxm 3 (linear capacity consumption since you have set the Linear indicator for this step).● Each load that is greater than 8 m 3 but less than or equal to 10m 3 results in a capacity consumption of

10m 3 .

Compartment 2:

● Each load x that is greater than 0 m 3 but less than or equal to 5 m 3 results in a capacity consumption ofxm 3 (linear capacity consumption since you have set the Linear indicator for this step).


● Each load x that is greater than 7 m 3 but less than or equal to 10 m 3 results in a capacity consumption ofxm 3 (linear capacity consumption since you have set the Linear indicator for this step).


5.6 Quota Arrangement

Use

The quota arrangement is the percentage that specifies which proportion of a required quantity of a product is to be procured from a source of supply (inbound quota arrangement) or supplied to a location (outbound quota arrangement). This percentage defines which part of a product quantity split should be assigned to a transportation lane.

Quota arrangements can be defined as either version-dependent or model-dependent, and as either product-dependent or product-independent. Quota arrangements are defined for a certain area of validity.

Inbound Quota Arrangement

Starting point is the source location of a delivery. For each product, an inbound quota arrangement specifies which part of the quantity should be supplied from which of the possible source locations. Possible source locations are all locations that are listed as source locations of transportation lanes for a specific destination location.

Inbound quota arrangements can be defined for the following source of supply types:

● Locations (transportation lanes)



● External procurement relationships● SAP APO only: In-house production (production process models, iPPE access objects, or production data

structures)

Outbound Quota Arrangements

Starting point is the destination location of a delivery. For each product, an outbound quota arrangement specifies which part of the product quantity should be transported to which of the possible destination locations. Possible destination locations are all the directions or destination locations of transportation lanes starting at the defined source location.

Outbound quota arrangements can only be created for locations.

Prerequisites

You have maintained the product.

You have maintained the locations.

You have maintained the transportation lane.

Activities

1. You call up quota arrangement maintenance in the SCM Basis menu under Master Data Quota Arrangement .

2. You make the required entries.

Quota Arrangement Maintenance

Data Description

Quota arrangement header data [page 184] The quota arrangement header shows a product/location combination.

Quota arrangement items [page 185] for inbound quota arrangements

The quota arrangement item defines the product procurement type; that is, the source of supply for a location.

In this activity, you determine the product percentage you want to procure from a source location.

Quota arrangement items for outgoing transportation lanes Same as above, except there are no procurement types. Outgoing items are sent to partner locations. In this activity, you determine the item percentage you want to deliver to a destination location.

For information about change logging for quota arrangements, see Change Logging for Master Data [page 211].


5.6.1 Maintain Quota Arrangement Header Data

Use

The quota arrangement header identifies a certain product/location combination and contains the definition of the relevant parameters :

● Validity period● Assignment and grouping of requirements● Quantity splits

Procedure

1. Invoke the quota arrangement in the SCM Basis menu under Master Data Quota Arrangements.2. Enter the model and planning version (optional). If you do not specify a planning version, the version-

independent entries apply. For more information, see Validity of Quota Arrangements [page 187] .3. Enter the source location for inbound quota arrangements or the destination location for outbound quota

arrangements.4. Activate the appropriate radio button to display inbound or outbound quota arrangements.5. Choose Create .

The Create Quota Arrangement screen appears. The details you entered on the previous screen have been inserted.

6. Choose Create from the quota arrangement table.The Quota Arrangement Header view appears on the right-hand side. On this screen, you maintain the settings listed below

7. Use the relevant icon at the top of the Quota Arrangement Header maintenance screen to exit this transaction:○ Close (without copying data)○ Adopt (the data is copied into the quota arrangement table on the left)○ Adopt and Close (the data is copied into the table on the left and the maintenance view is closed)

Maintenance of Quota Arrangement Header Data

Field Description

Product Selection Choose one of the following options:

○ An individual product○ All products maintained for this location○ Mass selection using a standard selection view of

multiple products maintained for this locatio n

Validity Period Enter the end date of the period in which this quota arrangement is to be valid.



Field Description

Requirement Splitting Applies only to Production Planning and Detailed Scheduling (PP/DS) in SAP Advanced Planning and Optimization (SAP APO). Set this indicator if procurement for a requirement is allowed to be made from different sources. Enter the minimum quantity in the Quantity requirements split field.

Requirement Grouping Valid only for Production Planning and Detailed Scheduling (PP/DS) in SAP APO. Use the input help to enter an individual, daily, weekly or monthly requirement.

Minimum Quantity in Case of Splitting for Quota Arrangements

Valid only for Production Planning and Detailed Scheduling (PP/DS) in SAP APO. Enter the minimum quantity if splitting is allowed, and the unit of measure.

Result

If you chose the copy option in step 7, the quota arrangement table appears on the left. You can now create and maintain quota arrangement items for the quota arrangement header.

5.6.2 Maintain Quota Arrangement Items

Use

Quota arrangement items for incoming quota arrangements define the product procurement category, the source location of the procurement for a destination location, and which percentage of the quantity of a product is to be procured from which source location.

The products of the incoming quota arrangement can be procured as follows:

● Via a partner location● Via an external supplier● Via in-house production

Quota arrangement items for outgoing quota arrangements are shipped to partner locations only. Therefore, if you are maintaining quota arrangement items for outgoing lanes, in this activity you determine which percentage of an item is to be sent to which destination location.

Prerequisite

You have maintained the quota arrangement header data.


If you are working with SAP Advanced Planning and Optimization (SAP APO), you have entered the quota arrangement heuristic for the product in the product master ( Heuristic field on the PP/DS tab page) for use in PP/DS.

Procedure

1. Create the quota arrangement header data.2. In quota arrangement maintenance, choose the quota arrangement header for which you want to maintain

quota arrangement items. The entire line is highlighted.3. Choose Display Quota Arrangement Items.

The Quota Arrangement Items detail view appears in the bottom left-hand part of the screen.4. Choose Create .

The Quota Arrangement Header maintenance view appears on the right-hand side. Maintain the settings as described in the table below.

5. Use one of the icons at the top of the maintenance view to exit this transaction:○ Close (without copying data)○ Adopt (the data is copied into the quota arrangement table on the left)○ Adopt and Close (the data is copied into the table on the left and the maintenance view is closed)

Maintenance of quota arrangement item

Field Description

Choose the procurement category You have the following options :

○ A partner location○ An external supplier○ In-house production

Use the standard selection view to make your selection.

Quota arrangement Quota arrangement value with which the requirement splitting is weighted. This value has no dimension.

Heuristic Define which heuristic is to be used to plan the quota arrangement item. For example, you could use the heuristic SAP006 to plan the product using a periodic lot-sizing procedure.

Quota base quantity This quantity serves as a basis for adjusting quota arrangement items when a new one is added. See the detailed example in the field help.

Quota-allocated quantity and unit Requirement quantity (with unit of measurement) that has already been allocated for this quota arrangement.



Result

If you chose a copy option in step 5, the quota arrangement item appears in the Quota Arrangement Item table on the left. You can now create and maintain quota arrangement items for the quota arrangement header.

5.6.3 Validity of Quota Arrangements

Use

The total quota arrangement relates to all products assigned to a specific location. Quota arrangements can be maintained on a version-specific or version-independent basis. Furthermore, the following options are available:

● Individual product● All products maintained for this location

The system determines the quota arrangement validity for a given location product or planning version in the following sequence:

● If a quota arrangement has been defined for a certain version, the quota arrangement relates to the location product.

● Ifyou choose All Products when maintaining the quota arrangement header data, this entry applies to all location products, provided that no product specific quota arrangement has been defined in the header line.

● If no quota arrangements have been defined for a planning version, the version-independent quota arrangement relates to the location product.

● If you choose All Products in the header line, the quota arrangement relates to the location product.

Activities

You can display the valid quota arrangements for each location product assigned to a location. Activatethe Total Quota Arrangements button in the toolbar of the Display Quota Arrangement screen. The Total Quota Arrangements table appears in the bottom left-hand part of the screen.

In the table, you see all the products that have been assigned to the location and the valid quota arrangements for each product. The valid quota arrangements contain all data defined in the quota arrangement header plus all assigned quota arrangement items listed in columns.

For more information, see also Quota Arrangement Maintenance [page 182] .


5.7 External Procurement Relationship

Definition

External procurement relationships belong to the master data in the SCM system. They represent purchasing info records contracts, and scheduling agreementsfrom your OLTP system(for example, an ERP system) in your SCM system and provide all the necessary data for the planning of product procurement.

Use

The external procurement relationship enables you to generate delivery schedule lines for an item of a scheduling agreement (APO scheduling agreement) directly in the SCM system.

The external procurement relationship links the transportation lane with information from your OLTP system:

The transportation lane represents the business relationship between a source location (for example, a vendor) and a destination location (for example, a plant). It is created automatically in the SCM system when you have transferred data from the ERP system. For more information see Transportation Lanes [page 146]

The external procurement relationship supplements the information about the transportation lane by creating a link to a specific contract that exists in your OLTP system for the source and destination locations.

External procurement relationships can exist for the following forms of procurement:

Standard

Subcontracting

Consignment

Stock transfer for stock transport scheduling agreements

The product Steel bolt 01 can be procured by your Houston plant from the vendor Armstrong Co. The product is to be procured via a scheduling agreement that already exists in your ERP system.

In your SCM system, the link between the vendor Armstrong Co. (source location) and your Houston plant (destination location) for the product Steel bolt 01 is represented by a transportation lane. Furthermore, an external procurement relationship exists, creating a link between this transportation lane and the scheduling agreement in your ERP system.



Structure

An external procurement relationship contains the following data:

General data

The general data includes information on the purchasing info record, contract, or scheduling agreement (for example, the procurement category, the logical system, the document number, the vendor and so on).

Settings

Under Settings, you can see the planned delivery time of a material and whether the external procurement relationship is active or inactive.

Planned delivery time The planned delivery time is adopted from the ERP outline agreement. However, you can change it. In the source determination process, the system uses the planned delivery time to calculate the scheduling of external procurement orders. If there is no entry in the external procurement relationship, or the entry is zero, the system uses the planned delivery time from the product master. If you want the planned delivery time of zero from the external procurement relationship to be taken into account in source determination, you must also set the Take Into Account indicator. Planned delivery times greater than zero are generally taken into account, even if the Take Into Account indicator has not been set.

Deactivation of external procurement relationship An external procurement relationship is usually deactivated if the purchasing info record, contract, or scheduling agreement is deleted in the ERP system. If the external procurement relationship is inactive, it is no longer taken into account in the source determination process and no new transportation lanes can be created for it.

Data on the transportation lane


On the Assigned Transportation Lanes tab page, you can display data on the transportation lanes and maintain the priority. You can also lock and unlock the assigned transportation lanes on this tab page.

Scheduling agreement data (only in the case of APO scheduling agreements)

You can display, and in some cases maintain, the following data on the Scheduling Agreement tab page:

Settings

Transaction data

Delivery data

Partners (only in the case of APO scheduling agreements)

On the Partners tab page, you can specify:

The address (for example, postal address, e-mail address) to which scheduling agreement releases are to be sent

The medium (for example, fax, e-mail) via which scheduling agreement releases are to be output

Which partner role your vendor assumes (here: source location)

If you have not maintained an address here, the SA release will be sent to the address maintained in the master data for the source location. The medium and the partner role are then determined from the default values maintained in Customizing for Supply Chain Planning under Collaborative Procurement → Set Message Triggers

You can also call up additional information by clicking one of the following buttons:

Costs

This gives you more precise information on the product costs (for example, scale prices and their validity periods).

Release Creation Profile (only in the case of APO scheduling agreements)

This takes you to Customizing, where you can display the release creation profile.

SA Releases (only in the case of APO scheduling agreements)

Here you can display the scheduling agreement releases that have already been generated for a scheduling agreement item.

PO History (only in the case of APO scheduling agreements)

Here you can view all the transactions and events that have been recorded for an item of a scheduling agreement (for example, receipts of goods and invoices).

Display Last Deliveries (only in the case of APO scheduling agreements)

Here you can display an overview of the last inbound deliveries against a scheduling agreement item. The inbound delivery data is transferred from the OLTP system to the APO system.

Accessible Functions

You can also branch to the following functions ( Environment →<...>):

Location



Product

Transportation lane

Quota arrangement

Tolerance profile, checking procedure, and confirmation profile for the receipt of confirmations (only in the case of APO scheduling agreements)

In Customizing, you can display the profiles and procedures for the receipt of confirmations.

Enter confirmations (only in the case of APO scheduling agreements)

You go to the function for entering confirmations.

Integration

The external procurement relationship is directly linked to the relevant transportation lane and provides additional information about it. From the external procurement relationship, you can also branch directly to the transportation lane in order to maintain relevant data.

If your OLTP system is an ERP system, you can transfer purchasing info records, contracts, and scheduling agreements (and changes to these purchasing objects) to your SCM system via the core interface (CIF).

For more information on external procurement relationships see Process External Procurement Relationship [page 191] .

5.7.1 Processing External Procurement Relationships

Use

The External Procurement Relationship function enables you to check (and, if necessary, adjust) data relating to your external procurement relationships.

External procurement relationships are master data in the SCM system that make data from purchasing info records, contracts, and scheduling agreements available to that system for the planning of material procurement. In this way, you can not only reference a vendor from an external procurement order, you can also directly reference a specific item in an existing contract.

The external procurement relationship is directly linked to the relevant transportation lane and provides it with data from the purchasing info record, contract, and scheduling agreement. From the external procurement relationship, you can also branch directly to the transportation lane in order to maintain transportation lane data.


Integration

When you transfer purchasing info records, contracts, or scheduling agreements from your OLTP system via Core Interface (CIF), external procurement relationships and the associated transportation lanes are automatically created in the SCM system. In the process, a separate external procurement relationship is created for each contract item or scheduling agreement item.

For more information, see:

● External Procurement Relationship [page 188]● Transportation Lane [page 146]● Automatic Creation of Transportation Lanes [page 148] .

Prerequisites

Before you can work with external procurement relationships in the SCM system, you must transfer the following data to it from your ERP system via CIF:

● Plants● Material master records● Vendor master records● Purchasing info records● Scheduling agreements● Contracts

For more information, see Integration of External Procurement Relationships [page 231] .

Features

The External Procurement Relationship function enables you to display and change the external procurement relationships that exist in the SCM system and to restrict how they are used (by blocking the transportation lane, for example)-

On the initial screen for this function you define which external procurement relationships are displayed. For example: all external procurement relationships for a destination location (for example, plant 0001), all those for a source location (vendor Meyer Corp.), or all those with a certain external procurement category ("contract").

The external procurement relationships are displayed in an overview tree in the left-hand part of the screen, listed by external procurement category (purchasing info record, contract, OLTP scheduling agreement, APO scheduling agreement) and the logical system from which the data originates.

If you choose an external procurement relationship from the overview tree, the following data will be displayed in the right-hand part of the screen:

● General information on the external procurement relationship (such as the source and target location, the product, and the validity of the external procurement relationship)



● Status of the external procurement relationship(active or inactive)● Associated transportation lanes● Scheduling agreement data, for example, the release creation profile (only in the case of APO scheduling

agreements)

Change External Procurement Relationship

Only certain data in an external procurement relationship can be changed:

● Change planned delivery time● Activate, deactivate, and delete external procurement relationship

● Change transportation lane ( Environment Transportation Lane Maintain )

● Create new transportation lane ( Environment Transportation Lane Create )

NoteYou can change the priority or block the transportation lane for a transportation lane in the external procurement relationship.

If you block an external procurement relationship then it can no longer be selected in the source determination process.

If you are working with SAP Advanced Planning and Optimization (SAP APO) and the external procurement relationship relates to an APO scheduling agreement, you can also maintain the following data:

● Release creation profileThe release creation profile for the scheduling agreement is not transferred from the ERP system. You must create a separate release creation profile in the APO system and assign it to the external procurement relationship. You define the release creation profile in Customizing for Supply Chain Planning under Collaborative Procurement Maintain Release Creation Profile .

● Confirmation profileYou define the confirmation profile in Customizing for Supply Chain Planning under Collaborative Procurement Maintain Release Confirmation Profiles .

● ProcessHere you can specify how confirmations are to be integrated in the scheduling agreement process.

● Update liveCacheWhen an external procurement relationship is created, the field Update liveCache is automatically filled with the value 10 - At time of release creation .

● Scheduling agreement with forecastYou use this indicator to specify whether forecast/planning delivery schedules are to be generated in addition to operative schedules. In the standard system, this indicator is not preset when an external procurement relationship is created.If you want to work principally with forecast/planning delivery schedules, you can specify that the indicator is automatically preset when an external procurement relationship is created using the Business Add-In (BAdI) /SAPAPO/PWB_TPSRC_IN . Using this BAdI you can also influence other data relating to the external procurement relationship or the transportation lane.


NoteYou can also specify in the release creation profile whether forecast/planning delivery schedules are to be generated in addition to operative schedules. For this reason, the settings in the release creation profile and the Scheduling Agreement with Forecast field must be harmonized.

● Internet releaseThis indicator enables you to specify whether or not the scheduling agreement release is an Internet Releaseand whether it has to be acknowledged by the vendor.

● Address dataAddress data is not transferred from the ERP system. If you do not maintain any address data on the Partners tab page, the address data of the source location is used.Use the relevant symbol to maintain your own address data for an external procurement relationship.

You can only influence other data by changing it in the ERP system (for example, a change to the scheduling agreement).

Deactivate External Procurement Relationship

If a purchasing info record, a contract, or a scheduling agreement is deleted in your ERP system, the relevant external procurement relationship is deactivated in the SCM system.

This procurement alternative can no longer be used in the source determination process. The log for the source determination process draws your attention to the fact that the relevant procurement alternative has been deactivated.

Furthermore, no new transportation lanes can be created for deactivated external procurement relationships.

Delete External Procurement Relationship

If you no longer need an external procurement relationship in the SCM system, you can delete it. In order for you to be able to do this, the external procurement relationship must have been deactivated. Furthermore, no external procurement orders or quota arrangements may exist in the SCM system for this external procurement relationship.

You can delete external procurement relationships as follows:

● In the external procurement relationshipDisplay the relevant external procurement relationship ( Master Data Procurement Master DataProcurement Relationships ) and choose Delete .

● Using the report Delete Procurement RelationshipsChoose Master Data Procurement Master Data Delete Procurement Relationships and select the external procurement relationships that you want to delete. Choose Delete . All external procurement relationships marked accordingly with the green symbol are deleted.

Mass Maintenance

You can use mass maintenance to change data that can also be changed in master data maintenance.

For further information see Mass Maintenance of External Procurement Relationships [page 195] .



5.7.2 Mass Maintenance of External Procurement Relationships

Use

You can use mass maintenance to change data relating to external procurement relationships ( scheduling agreement, OLTP scheduling agreement item, contractand info record) that can also be changed in master data maintenance (transaction /SAPAPO/PWBSRC1).

Features

You can activate or deactivate multiple external procurement relationships simultaneously and also change the procurement priority or the planned delivery time, or redefine whether the planned delivery time is to be taken into account.

If you are working with SAP Advanced Planning and Optimization (SAP APO), you can also use the following data from scheduling agreements.

● Release creation profile● Confirmation profile● Update liveCache● Scheduling agreement with forecast/planning delivery schedules● Internet release● Process for scheduling agreement processing

Note that you can only display certain data, not change it. For example, you cannot change the setting specifying whether a scheduling agreement is planned in SAP APO or in the ERP system ( Scheduling Agreement Processing Control (APOMS field)).

Activities

Invoke mass maintenance of master data under General Master Data Functinos , and choose the object type Procurement Relationship .

5.8 General Master Data Functions

In master data maintenance, there are a number of functions that apply to several object types. The following table provides an overview of these functions and the object types to which they apply in each case.

General Functions of Master Data Maintenance


Function Object Type

Mass Maintenance [page 197] Location

Product

Production process model (only SAP APO)

Resource

Transportation lane

Quota arrangement

External procurement relationship

Sales scheduling agreement

Master Data Locking Concept [page 201] Location

Product, location product

Enhancement (see Enhancement with the EEW) Location


Deletion with Deletion Flag (see Deletion of Master Data [page 206])

Location

Product

Transportation lane

Where-Used List (see Where-Used List for Master Data [page 207])

Location


Production process model

Product data structure

Resource

Transportation Lane

Change Logging (see Change Logging for Master Data [page 211])

Location

Product

Location product

Transportation lane

Quota arrangement

Partner product

Partner location

User-Specific Change Profiles (see User-Specific Display Profiles for Master Data Maintenance [page 212])

Location

Product

Location product



5.8.1 Mass Maintenance

Use

It is frequently necessary to revise a large volume of master data using a mass-maintenance function. What is primarily involved here is master data that (a) cannot be transferred (or cannot be transferred completely) from external systems and (b) exists in large quantities. Since selections of several thousand entries are not uncommon in the case of certain master data, a special mass maintenance tool is essential to minimize the amount of time required to process such data.

Mass maintenance involves the mass changing of individual attributes of master data, the creation of new data records, the assignment of existing objects, and mass deletion.

A tool is available for the mass maintenance of master data. This tool can be used in all projects having large volumes of such data. This tool facilitates the efficient changing and supplementation of master data.

Features

You can use the mass maintenance tool to process the following master data:

● External procurement relationships● Sales scheduling agreements● Locations● Production process models (PPMs) (SAP APO only)● Products● Quota arrangements● Resources● Transportation lanes

You can only make simultaneous mass changes for one of the above types of master data in each case. It is not possible to make mass changes for several types at the same time.

CautionThe mass maintenance tool enables you to change a large number of objects simultaneously. The changes directly impact all selected objects. This tool should therefore only be used by experienced users exercising due care.

5.8.1.1 Using the Mass Maintenance Tool

Use

The tool for the mass maintenance of SAP APO master data is basically the same tool with which the mass maintenance of master data can also be carried out in SAP R/3. In addition to technical enhancements and


improvements, the SAP APO version of the tool features a redesigned user interface and greater user-friendliness.

The new design has the following main advantages:

● All activities on a single screenYou perform all necessary activities for mass maintenance on one screen (single-screen transaction). You thus don't have to navigate between different screens or screen sequences. You have a permanent overview of the chosen selection criteria, the change methods, and the selected data.

● Predefinable display restrictionYou can set the maximum number of data records selected and displayed without a warning message. To do so, choose Settings Display Restriction.

● Changing without displaying the data in the case of numerous hitsIn order to be able to change large volumes of data despite given runtime restrictions, you have the option of changing data without displaying it. This allows you do dispense with both the data selection process and the on-screen display of the data.

● Suppression of warning messages after they have been displayed onceYou can permanently deactivate the display of warning messages after they have appeared once. The display of warning messages can later be reactivated for the less-experienced user via Settings Display Warnings Again .

● Hiding of selection areaWhen you have finished selecting the master data to be maintained, you can hide the selection area in order to obtain more space to display and actually maintain the data.

● Cumulative effect of formulasFormulas are always applied to the values that are currently visible in the data table. This results in a cumulative effect if formulas are applied successively.

● Comprehensive online helpChoose Goto Help to access additional information when working with the tool. The information available includes tips on selection, making systematic changes for all objects, table maintenance for individual objects, and how to use variants.

If you want to carry out the mass maintenance of master data in SAP APO using the redesigned tool, use the transaction code MASSD. If you prefer to carry out the mass maintenance of master data in SAP APO using the same interface as in SAP R/3, use transaction code MASS.

Note the functional differences between the two transactions.

Note

For information on the functional differences between the transactions MASS and MASSD, see Functional Differences MASSD <-> MASS [page 200] .

Features

Selection of Data in Selection Area

You choose the data that is to be maintained in the selection area on the left-hand side of the screen. Selection is carried out according to object type, component, and attribute.



When the selection process has been completed, you can hide this area.

Maintenance of Data in Manipulation Area

In upper part of the manipulation area on the right-hand side of the screen, you specify the change methods by which the values of the attributes are to be changed. Below this, the attributes are displayed with their associated values in the data table.

Types of Mass Maintenance

In mass maintenance, you can change data in two different ways:

● Systematic changes● Tabular maintenance

Systematic Changes

In the case of systematic changes, you enter a change method with which the change in an attribute is specified. This change is carried out for all objects. You can choose whether the changes are to be carried out immediately or in the background. It is also possible to save systematic changes as variants.

Tabular Maintenance

In tabular maintenance, you can change individual objects with different values. Once you have activated tabular maintenance, it is not then possible to make changes in the background. Neither is it possible to save a tabular change as a variant.

Activities

Basic Process of Mass Maintenance

In the mass maintenance of master data, you always proceed according to the following schema:

You first choose an object type (such as a location) in the selection area. Using the selection criteria, you then choose the component (header data, for example) containing the attribute to be changed (the location type, for example).

In the next step, you specify the attribute you wish to maintain. The selection made here determines the attribute to which the change methods are to be applied.

The result of the selection appears in a data table in the manipulation area on the right-hand side of the screen. In the process, the attributes for each selected component are listed on a separate tab page. Prior to the mass maintenance operation, the data table shows you the values read by the database. After the first change, you see the changed values that are subsequently affected by all further changes.

Invoking Mass Maintenance Function with New Interactive Design

To call up the redesigned mass maintenance tool, choose Master Data Mass Maintenance (transaction code MASSD) from within SAP APO Easy Access.

Invoking Mass Maintenance Function with Conventional Interactive Design

If you prefer to use the same interface as in SAP R/3 to carry out the mass maintenance of SAP APO master data, you can call up the tool with the transaction code MASS.


5.8.1.2 Functional Differences MASSD <-> MASS

Use

The following table lists the functional differences between the mass maintenance transactions MASSD and MASS.

Function MASSD MASS

Navigation All activities on one screen; there are warnings, e.g. of loss of data.

Several consecutive screens before data maintenance possible; no warnings.

Changes via ABAP-FORMs Function not available. Function available.

Changes via formulas Simplified formula application: only addition to/subtraction from absolute and percentage values possible.

Any formulas possible.

Processing of variants The following restrictions apply to variants saved in the transactions MASSD or MASS:

- No ABAP-FORMs

- Only simplified formulas

All variants possible.

Use of formulas Formulas are always applied to the values that are currently visible in the data table. This results in a cumulative effect if formulas are applied successively.

Formulas are always applied to the values that were originally read from the database, i.e. no successive data changing is possible.

Removal of individual lines from the data table

Individual selected items in the data table can be excluded from the change process. The removal of the item relates only to the display and has no effect on the database.

Function not available.

Table maintenance Display of the data table must be explicitly opened for input.

Data table is continuously ready to accept input.

Selection of fields Multiple selection possible. Just one field at a time is adopted by mouse-click.

Calling up variants Object type can be changed in variant loading dialog.

Not possible to change object type.

Column selection in data tables Function not possible. When the Execute Changes function is performed, the system checks whether a column has been changed; only selected columns are processed.



5.8.2 Master Data Locking Concept

Use

In day-to-day operations, it frequently happens that several users simultaneously access a master data object using different maintenance types - for example, individual and mass maintenance. In parallel to this, it is also possible that data transfers via the Business Application Programming Interface (BAPI) or the Core Interface (CIF) affecting the same master data object are occurring. The master data locking concept covers all maintenance types and ensures mutual locking in the case of the parallel accessing of the same master data objects. The lock time and associated performance loss are minimal. The maintenance types have a predetermined lock prioritythat specifies which maintenance type the system gives precedence in the case of parallel accesses and which maintenance type can override a lock set by another. The locking behavior of the system is also determined by the processing mode (individual or mass processing mode).

Features

The master data locking concept applies to products and location products.

Lock Priority

The maintenance types have the following lock priorities:

● Highest priority: Data transfer via BAPI and CIF● Medium priority: Mass maintenance● Lowest priority: Individual maintenance

Individual Processing Mode and Mass Processing Mode

Individual Processing Mode

In individual processing mode, the system sets the locks during dialog processing and updating individually for master data objects that are just being processed. In individual maintenance, the system always uses the individual processing mode. In mass maintenance, and in data transfer via CIF or BAPI, it uses the individual processing mode only up to a number of lock requests that you define in Customizing.l In individual processing mode, the parallel individual or mass maintenance of other master data objects is possible. In individual processing mode, individual and mass maintenance have the same priority.

When you process a master data object in individual maintenance, the object is locked during the dialog and update time against access by other users. Users accessing the same master data object in parallel cannot save their changes until they have ended their maintenance. In the case of a parallel access by a maintenance type with a higher lock priority, this access can override the lock set by such users. In this case, you get an error message the next time you switch screens and are unable to save your change. You must restart the maintenance transaction and repeat your changes, saving them when the overriding lock has been removed.

Mass Processing Mode

In mass processing mode, the system collects the lock requests up to a block sizes that is predefined in Customizing and then processes them in parallel work processes.

The system uses the mass processing mode in mass maintenance and in the case of data transfers via CIF or BAPI above a certain number of lock requests.


Note

In Customizing for the SCM Basis under Master Data Define Parameters for Master Data Locking Concept, you can specify as of which block size the system switches from individual to mass processing mode.

In the mass processing mode, parallel accesses via mass maintenance and CIF or BAPI transfers result in mutual locking irrespectively of whether or not the master data objects to be maintained overlap each other.

In the process, a distinction is made between a general lock and a limited general lock. In the case of the general lock, you cannot save changes effected using a maintenance type with lower priority, irrespectively of whether or not the maintenance type with higher priority impacts the same master data objects. In the case of the limited general lock, you can, however, still save changes made to different master data objects. However, it is not possible to re-access the objects using this maintenance type for the duration of the lock.

Parallel data transfers via CIF and/or BAPI constitute an exception. Here, parallel maintenance of different master data objects is possible. That is to say, these are not mutually locking maintenance types.

CIF parallelizes the data transfer and ensures that the master data objects are transferred serialized via the queued remote function call (qRFC). In the case of BAPI transfers, this is not automatically the case. Therefore the users must prevent the same master data objects from being processed in parallel by various BAPI accesses.

You will find an overview of the system behavior depending on the maintenance type and processing mode under Lock Priorities in Individual and Mass Processing Modes [page 203] .

Special Aspects

● In mass processing, the system does not transfer the lock set in dialog processing to background processing. If you are performing a mass maintenance and save in the background, the system does not therefore set a lock. On the other hand, if you save during dialog processing, the system sets the lock.

● Due to the serialization of the CIF, it is not possible for two CIF transfers to be carried out for the same master data object. The system does not set a lock (see above).

● Two transfers take place simultaneously for the same master data object via two different BAPIs. The BAPIs do not set mutual locks. You should preclude this case when invoking the BAPIs.

Activities

In the standard system, the master data locking concept is active. However, you can deactivate it individually for mass maintenance, CIF transfer, or BAPI transferin Customizing for the SCM Basis under Master DataDefine Parameters for Master Data Locking Concept.

At the same point in Customizing, you can influence performance by changing the parameters Block Size, Number of Parallel Work Processes and Blocks per Parallel Work Process.



5.8.2.1 Lock Priorities in Individual and Mass Processing Modes

The following tables give you an overview of the locking behavior of each individual maintenance type in relation to the other maintenance types. A distinction is made between the individual and mass processing modes.

Individual Maintenance

Individual maintenance (IM) versus parallel…

Individual maintenance Mass maintenance CIF transfer BAPI transfer

Individual processing mode

IM has same priority and sets individual lock

IM has same priority and sets individual lock

IM has lower priority and runs into lock


Mass processing mode Mass processing mode not possible




Mass Maintenance

Mass maintenance (MM) versus parallel…



MM has same priority and sets individual lock

MM has lower priority and runs into lock (1)

MM has lower priority and runs into lock


Mass-processing mode

MM has higher priority and overrides IM lock

MM has same priority and sets individual lock



CIF Transfer

CIF transfer (CIF) versus parallel...



CIF has higher priority and overrides IM lock

CIF has higher priority and overrides MM lock

CIF does not set a lock against CIF Separation of master data objects through serialization

CIF has same priority and does not set a lock against BAPI

Mass processing mode CIF has higher priority and sets a limited general lock (2)

CIF has higher priority and sets a limited general lock (2)

CIF does not set a lock against CIF Separation of master data objects through serialization

CIF has same priority and does not set a lock against BAPI


BAPI Transfer

BAPI transfer versus parallel...



BAPI has higher priority and overrides IM lock

BAPI has higher priority and overrides MM lock

BAPI has same priority and does not set a lock against CIF

BAPI has same priority and does not set a lock against BAPI

Mass processing mode BAPI has higher priority and sets a limited general lock (2)

BAPI has higher priority and sets a limited general lock (2)

BAPI has same priority and does not set a lock against CIF

BAPI has same priority and does not set a lock against BAPI

(1) This applies only if one mass maintenance is running in individual processing mode and the other in mass processing mode. If both mass maintenances are running in individual processing mode, they have the same priority.

(2) A general lock imposed through CIF or BAPI transfers overrides individual locks set on master data objects that are in the process of being changed through individual or mass maintenance. In the case of the limited general lock, the user can, however, still save the master data object currently being processed if this is not affected by the transfer.

5.8.3 Master Data Enhancement with EEW

Use

The Easy Enhancement Workbench (EEW) is available to assist you in enhancing the master data fields in the customer namespace provided by SAP by adding further fields. You can use the EEW, for example, to enhance the product master record by adding the Additional Costs field or further date fields for specifying validity periods. The business use of the enhancement fields has no influence on the standard. It is not necessary to manually change the source text.

The newly created fields appear on the relevant tab page in the Enhancement Fields group box. This box is visible only if you are using the enhancement. You can process the enhancement fields using individual or mass maintenance.

Integration

Enhancements effected using the EEW do not involve modification of the standard system.

In the event of an upgrade, the enhancement fields are automatically transported to the new system as well.

Enhancement fields are not integrated with the ERP system. That is to say, they are not automatically transferred to the ERP system via the Core Interface (CIF) or Business Application Programming Interface (BAPI).



Prerequisites

You need the appropriate authorization to be able to use the EEW.

Features

In Customizing for the EEW (transaction EEWZ1) the objects and subobjects you can enhance with the EEW are predetermined:

● Location○ Location header

● Product○ Storage data○ Product header○ Location product○ Warehouse product○ Storage type product○ Packing/packaging material

A total of 500 bytes are available for each enhancement, which you can distribute among several fields. You can use a maximum of 60 bytes per field.

You can have a check table generated for each field.

Restrictions

● You can only insert fields (one-to-one relationship) using the EEW - not tables.● The enhancement fields appear at predefined points on the user interface and cannot be moved.● You may not use any floating point numbersin the fields.● Consistency checks and search helps are not enhanced.● The indicator for activating change documents is not set automatically in the generated data elements.

Activities

Invoke the EEW in the SCM Basis menu under Master Data General Master Data FunctionsEnhancements .

For more information, see Documentation on EEW .


https://help.sap.com/viewer/2eb99edb9d99472d9afa587acddd7a7c/750 SP16/en-US/12b98d5377a0ec23e10000000a174cb4.html

5.8.4 Deleting Master Data

Use

You can delete master data that you no longer need in the SCM system. However, you should note that in many cases dependencies exist between the data you are considering deleting and other master data or transaction data. You should therefore give careful thought to any planned deletion activities. You can only delete a location, for example, if there are no dependent products. This means that you may first have to delete the products that are dependent on the location in question. For certain master data, you can generate a where-used list prior to deletion.

For the object types "location", "product" and "transportation lane", you can set a deletion flag prior to actual deletion. This enables you to set the deletion flag for several objects of an object type and schedule the deletion itself as a background job, for instance.

Integration

If you wish to delete integrated locations, products, or location products (plants, materials, or material-plant combinations) in the ERP system, first set the deletion flag in the ERP system. If the master data is contained in an active integration model, the system transfers the deletion flag to the SCM system. Here you can only delete master data for which the deletion flag has been set if no dependent objects exist. You can use master data flagged for deletion without restriction in planning.

To prevent materials flagged for deletion from being used in planning, you must deactivate the integration models that contain these materials and delete the corresponding products in the SCM system as necessary. For more information, see Logging Deactivated Material Master Data [page 43] .

Prerequisites

You have ensured that the master data object you want to delete is no longer used. To do this, you can use the Where-Used List [page 207] .

NoteThe availability of a where-used list for a master data object in an application component depends on the master data object and application component. For more information, see the documentation for the master data object and for the corresponding application component.



Features

For more information on deleting master data objects in SCM Basis, see the following sections:

● Deleting a Location [page 80]● Deleting a Product [page 134]● Deleting Product-Specific Transportation Lanes [page 165]● Processing External Procurement Relationships [page 191]

For more information about deleting application-specific master data objects, see the corresponding application documentation. Documentation for SAP APO contains, for example, information about deleting the following objects:

● Model● Planning version● Production data structure● Resource

5.8.4.1 Where-Used List for Master Data

Use

You can use the where-used list to see where a master data object is used. You can determine, for example, to which locations a product is assigned. The where-used list is of particular importance when you are considering deleting a master data object.

The availability of a where-used list for a master data object in an application component depends on the master data object and application component. For more information, see the documentation for the master data object and for the corresponding application component.

CautionFor example, the where-used list is not available in Logistics Inventory Management Engine (LIME). Therefore, the where-used list cannot determine whether a master data object is used in LIME.

In SAP Supply Network Collaboration (SAP SNC), the where-used list is only available for the product.

Features

Master data objects with where-used list

The where-used list is available for the following master data objects - depending on the application.

● Hierarchy● Location● Location product


● Product● Production process model (only SAP APO)● Production data structure (SAP APO only)● Resource● Transportation lane● Product-specific transportation lane● Vehicle

Background Processing

If a large number of dependent objects are involved, you can perform the where-used function in the background. You can then load the results at a later point in time.

NoteDepending on the scope of selection and the number of usages, the where-used function can have a long runtime. This applies particularly to resources. We recommend performing the where-used function for individual resources only or in the background.

Planning version dependency

The where-used list for a resource is planning-version-dependent. If you perform the where-used function for a resource without a planning version (that is, planning-version-independently), the system will not determine any orders for the resource.

If you perform the where-used function for a resource with a planning version (that is, planning-version-dependently), the system will not determine any optimization profiles, transportation lanes, means of transport, or hierarchies for the resource.

Production process model (PPM), production data structure (PDS), and iPPE are determined planning-version-independently. This also applies if you have specified a planning version.

Activities

To call the where-used list, on the SAP Easy Access screen, choose SCM Basis Master Data General Master Data Functions Where-Used List.

The where-used list for the SAP APO-specific master data objects Productions Data Structure and Production Process Model can only be found in SAP APO under Master Data Production Process Model .or Production Data Structure (PDS).

5.8.4.2 Master Data Dependencies

The following table displays the dependent objects for each master data object. The Delete column also indicates whether you can delete the dependent objects using the where-used list.



Master Data Dependencies

Master Data Dependent Objects Deletion

Supply chain model (SAP APO only)

Planning version (only SAP APO)

Location

Location product

Transportation lane

Production process model

iPPE

Resource

You can delete models or planning versions directly, without first having to delete the dependent objects. This does not apply to the active model or the active planning version.

Location Hierarchy

Model

Matrix

Location product

Resource

Transportation lane


You can manually delete the dependent objects via the where-used list [page 207] .

Product ATP order

Configurable product

liveCache order

Location product

Production process model plan (PPM plan)

Production data structure


Source of supply

SAP SNC-specific objects (see the application documentation for SAP SNC)

Depending on the application component and the type of dependent object, you can delete dependent objects manually via the where-used list [page 207] .



Location product ATP order

Configurable product

Interchangeability object

liveCache order

PPM plan

Quota arrangement

Production data structure


Source of supply


Resource Hierarchy

iPPE

Location

Model

liveCache order

PDS

PPM plan

Resource

Means of transport/transportation lane

Vehicle

TP/VS optimization profile


Transportation lane Shipment

Order number

Quota arrangement

You can manually delete dependent objects via the where-used list [page 207] .

Vehicle Shipment

Order number

Quota arrangement


Product-specific transportation lane Order number

Quota arrangement


Class (SAP APO only) Characteristic Dependent characteristics are deleted automatically as well.




External procurement relationship Transportation lane

Quota arrangement

Order number

Dependent transportation lanes are deleted automatically as well.

If the item of a dependent quota arrangement is a purchasing info record, scheduling agreement, or contract, you must first delete it manually.

Sales scheduling agreement Transportation lane Dependent transportation lanes are deleted automatically as well.

Production process model (only SAP APO)

Model

liveCache order

Quota arrangement


Production data structure (SAP APO only)

Model

liveCache order

Quota arrangement


5.8.5 Change Logging for Master Data

Use

If you activate change logging, the system writes change documents when changes are made to master data. You can display the change documents and thus keep track of how a master data object was changed at certain points in time.

In the standard system, change logging is not active.

NoteChange logging can impair performance. We recommend not activating it if large volumes of data are anticipated. This is particularly so in the case of the initial transfer of data from the ERP system.

Change documents are not deleted automatically even if the relevant master data object (such as a location) is deleted. Report RSCDOK99 is available for the deletion of change documents.

Prerequisites

You have activated change logging for the desired master data object type. Activation takes place in Customizing for the relevant master data object type (location, product, location product, transportation lane, quota arrangement, partner product, or partner location) under Activate Change Documents. You can activate


certain subobject types (such as the header data, mapping information, or location description for the location) separately for each object type.

Features

You can use change logging for the following master data object types:

● Location● Product● Location product● Transportation lane● Quota arrangement● Partner product● Partner location

Activities

Choose Display Change Documents under the relevant master data object in the SAP menu and select the change documents you wish to see.

5.8.6 User-Specific Display Profiles for Master Data Maintenance

Use

In the standard system, all tab pages are displayed in master data maintenance. If you do not need all the tab pages and wish to suppress individual ones, you can create display profiles for the maintenance of the location, product, and location product master. This enables you to better organize master data maintenance and tailor it to suit your own particular requirements.

Features

You can create the following categories of display profile:

● Template profiles● User profiles● Standard template profile and standard user profile



Activities

1. Your system administrator creates template profiles for certain user groups (for example, all users in planning). He or she can designate a template profile as the standard template profile. This template profile is automatically used for all users who do not have their own standard user profile.To create or change a template profile, from the SCM Basis menu, choose Master Data Location (or Product) Manage Display Profiles for Master Data Maintenance.

2. The system administrator assigns a template profile to individual users. As a result, user profiles are automatically created which can be changed at will by their owners (that is, the users). A user can be assigned to several template profiles. He or she can designate one of his or her user profiles as the standard user profile.To create or change a user profile, from the SCM Basis menu, choose Master Data Location (or Product) Manage Display Profiles for Master Data Maintenance.

3. The system uses the template or user profile designated as the standard profile as the standard template profile or standard user profile. There can only ever be one standard template profile or (per user) standard user profile. If a user has been assigned to a standard template profile, the latter is automatically used if no standard user profile of his or her own exists. If a user has created a standard user profile, this is used by default.

4. If neither a standard nor a template profile has been created, the system displays all tab pages in master data maintenance.

5. A display profile can also be changed temporarily from within master data maintenance. To change a user profile for the current display, choose the Display Profile button for Location or Product in master data maintenance. However, when you exit master data maintenance, these changes are lost.

5.8.7 Partner-Dependent Master Data

Use

You maintain partner-dependent master data for the partner, location, product. You can maintain, for example in the case of partner-dependent partner data, the partner-dependent number and description that your partner uses.

Activities

You maintain partner-dependent master data on the SAP Easy Access menu, by choosing Master DataPartner-Dependent Data .

Example

In this example, business partner master data is maintained for both customer and supplier by a maintaining partner. For example, the customer is assigned the number CUST_ABC and the supplier is assigned the


number SUP_ABC. The supplier wants to use the number CUSTOMER_123 for the customer. In order for the supplier to enter not only the number CUST_ABC, but also the number CUSTOMER_123, they must enter the following data:

● Maintaining Partner: SUP_ABC● Partner Number: CUST_ABC● Partner-Dependent Partner Number: CUSTOMER_123

5.9 Integration of SCM Basis Master Data

Certain master data can be transferred from a connected ERP system to the SCM system. Transmission takes place via the Core Interface (CIF) and is controlled via the integration model that is located as part of the CIF on the ERP side. For information on the technical view of the integration, see Integration via Core Interface (CIF) [page 20] .

The following provides you with information regarding which master data can be adopted from the ERP system and further details of this integration.

5.9.1 Integration of Locations

Use

This section provides you with information as to how the Core Interface (CIF) transfers location master data (plant, customer, vendor, etc.) from the ERP system to the SCM system.

Integration

The ERP master data objects plant, customer, vendor, shipping point, etc. are transferred as locations.



They differ from each other through their respective location types. The function of a location is therefore dependent upon the location type.

Note that the location type does not belong to the location table key and that this can lead to naming conflicts.

ExampleIf both the vendor and the customer have the same number in the ERP system (for example, customer and vendor 1000 ), you need to rename one of them when entering them into SCM by using the customer exit for the vendor master record (for example, you can rename the vendor S1000 ). If you do not do this, the system is unable to differentiate between the two locations. This is due to the fact that the location type is a key field in table /SAPAPO/LOCMAP but only an attribute in table /SAPAPO/LOC.

Transfer of ERP Master Data to the SCM Location Master


Question Answer

How is the data transfer from the ERP production plant carried out?

A plant is transferred to the SCM system with the location type 1001 (production plant). For this, all basic settings associated with the plant are transferred: Name, address, time zone, and regional assignment.

When a plant is transferred, the transportation zone assigned to the plant in the ERP system is transferred as a separate location of type 1005 in addition to the actual plant location.

Additional data in the SCM location:You can maintain the short text for SCM locations in several languages (in contrast to the plant in the ERP system), so that when you log on in a certain language the short text appears in that language.SCM locations generally contain a large number of additional planning parameters for which there is no equivalent in the ERP system. You have to maintain these parameters in the SCM system subsequently. You cannot transfer them from the ERP system.

How is the data transfer from the ERP distribution center carried out (as of SAP R/3 4.0)?

As of SAP R/3 4.0, you can define plants as distribution centers within the framework of the DRP functionality. (DRP: Distribution Resource Planning.) For this, you need to maintain the associated entry in the customizing table in the basic settings of DRP customizing (customizing step Node Type Assignment - Maintain Plant ).

If you transfer plants that are defined as distribution centers in the ERP system, these plants are transferred to the SCM system as location type 1002 (distribution center). The transfer of the individual ERP plant settings (in the ERP system, a distribution center is nothing other than a plant) occurs in the same way as for production plants.

How is data transferred from storage location MRP areas of the ERP system (as of SAP R/3 4.5B)?

See Integration of Storage Location MRP Areas [page 222] .



Question Answer

How is the transfer of customer data from the ERP system carried out?

Customer data is transferred from the ERP system as locations with the type 1010 (customer).

When a customer master record is transferred, the transportation zone assigned to a customer in the ERP system is transferred as a separate location of type 1005 in addition to the actual customer location. The missing data that is needed to use the transportation zone for planning in SAP APO has to be entered manually after the transfer.

If you work with SAP Advanced Planning and Optimization (SAP APO), the following applies: sales orders are entered in the ERP system and transferred to SAP APO as transaction data. If the customer to whome an ERP sales order is assigned is also to be displayed in SAP APO, the corresponding location must exist in SAP APO. However, a transfer is not mandatory for the pure production planning process.

How is the transfer of vendor data from the ERP system carried out?

Vendors are transferred from the ERP system as locations of the type 1011 (vendor) or type 1020 (carrier) depending on the account group assignment in ERP. (Account group and SCM location type assignments are defined in table CIFVENTYPE in ERP.) Transportation zones are transferred in the same way as customer data.

How is the transfer of shipping point data from the ERP system carried out?

Shipping points are transferred from the ERP system as locations of the type 1003 (shipping point).

To change the transfer data of the shipping points prior to sending, the Business Add-In (BadI) CIF_ENHANCED is available.


Question Answer

Which customer exits exist? ERP function module:CIF_PLANT_LOCATION_MAPERP customer exit:EXIT_SAPLCLOC_001 (CIFLOC01)

ERP function module:CIF_VENDOR_LOCATION_MAPERP customer exit:EXIT_SAPLCLOC_002 (CIFLOC01)

ERP function module:CIF_CUSTOMER_LOCATION_MAPERP customer exit:EXIT_SAPLCLOC_003 (CIFLOC01)

ERP function module:CIF_MRPAREA_LOCATION_MAPERP customer exit:EXIT_SAPLCDC5_001 (CIFLOC02)

SAP APO function module:/SAPAPO/CIF_LOC_INBOUNDSAP APO customer exit:EXIT_/SAPAPO/SAPLCIF_LOC_001(APOCF001)

SAP APO function module:/SAPAPO/DM_LOCATION_MAINTAINSAP APO customer exit:EXIT_SAPMMDUSER_004 (APOMD004)

You can find usage examples and example coding for the customer exits in the relevant documentation.

What BAPIs are there and what is their operation? Object type: BUS10002BAPI: BAPI_LOCSRVAPS_SAVEMULTI_30ACustomer exit: EXIT_SAPL10002_001 (APOBP003)



Question Answer

How is the transfer of location master data initiated? There are three possibilities:

Initial data transfer

For the integration, you must include the relevant locations in an integration model. When you activate the integration model, the locations are sent to the SCM system and created there.A necessary prerequisite for the change transfer and for a series of processes is that the objects are included in an active integration model.You can also repeat the initial data transfer if the integration model is deactivated in the meantime.

Change transfer using change pointers

You can use ALE change pointers to log changes to customer and vendor master data. They can then be transferred using the program RCPTRAN4 (transaction CFP1) without repeated activation of an integration model.

Online transfer of customer and vendor master data using BTE

You can also transfer customer and location master data using a Business Transaction Event (BTE). You can set the system so that the transfer of changed and newly created customers and vendors is directly initiated when the master data is updated in the ERP system.

When transferring changes, the system always transfers the complete master data record and not just the changed fields. This means that those fields that originate from the ERP system and have been locally changed in the SCM system are overwritten again in the SCM system. You can prevent this information being overwritten in SAP APO by using a customer enhancement.

In this case, the system can only automatically recognize that a location has been changed, and transfer the data to SAP APO if you carry out the change directly in the fields of the material master record. Changes to the customizing or profile tables may also mean that you have to transfer the locations again. Changes that only indirectly influence the master record cannot be automatically recognized by the system.


Question Answer

How is the sublocation converted? There is currently no conversion of the storage location functionality in the SCM system. The Sublocation field exists in the MRP area only.

5.9.1.1 Integration of Customer and Vendor Data into Business Partner

Use

You can transfer vendor and customer data from a SAP ERP system to a SCM Basis system to automatically create a business partner.

Prerequisites

To ensure that SCM Basis only creates a business partner you have to make settings in the SAP ERP system. Depending on the SAP ERP Release you are using, the settings you make differ as follows:

● If you are using SAP ERP 2005 including an enhancement package (EhP) lower than EhP 3, you must first create an integration model using the CFM1 transaction and include the customer or the vendor. When you activate the integration model in the CFM2 transaction, you specify that you only want to create a business partner by entering 1 in the Create Business Partner field.

● If you are using SAP ERP 2005 including an enhancement package (EHP) higher than EHP3, you must first create an integration model using the CFM1 transaction and include the customer or the vendor. For the customer or vendor you specify that you only want to create a business partner by entering 1 in the Create Business Partner field. Once you have specified that you want to only create a business partner, you activate the integration model in the CFM2 transaction.

To ensure that the system can validate a field entry for the following data, you have maintained settings in Customizing for SCM Basis under Business Partner:

● Transportation service level codes● Industry keys● Terms of payment● Customer account groups● Vendor account groups● Business partner functions● Delivery priorities

To maintain settings in Customizing for SCM Basis under Business Partner, you must activate the business function Foundation of External Transportation Management System [page 16] ( SCM_SCMB_TM_FND1).



Features

Integration of Vendor Data

You can transfer the following business partner data for the vendor roles Vendor ( BBP000) and Carrier ( CRM010):

● General header data for the vendor, such as address, account groups, industry key, and tax numbers● Company organization data for the vendor, such as terms of payment and central posting blocks● Organizational data for the vendor, such as customer group, shipping conditions, and incoterms● Partner functions for the vendor, such as partner function for the sales organization and purchasing

organization

To transfer the customer data into the business partner, you must activate the SCM Basis business function Foundation of External Transportation Management System [page 16] ( SCM_SCMB_TM_FND1) and the SAP ERP business function SCM, Customer and Vendor Master Data Integration into BP ( LOG_SCM_CUSTVEND_INT).

Integration of Customer Data

You can transfer the following business partner data for the customer roles Sold-To Party ( CRM000) and Ship-To Party ( CRM002):

● General header data for the customer, such as address, account groups, industry key, and tax numbers● Company organization data for the customer, such as terms of payment and central posting blocks● Organizational data for the customer, such as purchasing group, currency, responsible sales person at the

vendor● Partner functions for the customer, such as partner function for the sales organization and purchasing

organization

To transfer the vendor data into the business partner, you must activate the SCM Basis business function Foundation of External Transportation Management System [page 16] ( SCM_SCMB_TM_FND1) and the SAP ERP business function SCM, Customer and Vendor Master Data Integration into BP ( LOG_SCM_CUSTVEND_INT).

5.9.1.2 Integration of International Address Versions

Use

International address versions are versions of a location address that can be maintained in various character sets, such as Kanji characters and Latin letters. With this function, you can automatically transfer international address versions with customer and vendor data from the SAP ERP system to SCM Basis using CIF.

To integrate international address versions, you must activate the SCM Basis business function Foundation of External Transportation Management System [page 16] ( SCM_SCMB_TM_FND1) and the SAP ERP business function SCM, Customer and Vendor Master Data Integration into BP ( LOG_SCM_CUSTVEND_INT).


Prerequisites

To use international address versions in your SAP Supply Chain Management system, you have done the following:

● You have ensured that international address versions are maintained in SAP ERP.

● In Customizing for SAP NetWeaver under Application Server Basis Services Address ManagementInternational Settings Activate International Address Versions you have activated the international versions of the address that you want to use.

CautionThe system only transfers those international address versions that you have activated.

5.9.1.3 Integration of Storage Location MRP Areas

Use

In the ERP system, an MRP area is an organizational unit within a plant for which you carry out separate material requirements planning and inventory management. An MRP area might consist of one or more storage locations (storage location MRP area) or a subcontractor (subcontractor MRP area). With MRP areas, you can execute material requirements planning specifically for individual areas in a plant. For example, you are able to do this for individual production lines or for a store for spare parts. This enables you to stage materials for the individual areas in accordance with date and quantity. Processing using storage location MRP areas is only possible for make-to-stock production. You only plan make-to-order or engineer-to-order production in the plant location.

You can use an integration model of the Core Interface (CIF) to transfer selected storage location MRP areas to the SCM system, where they are mapped automatically as independent locations. If you integrate not only the plant, but also the storage location MRP areas belonging to the plant with the SCM system, several locations are thus created in the SCM system: one location for the plant and one for each storage location MRP area that is transferred. The following graphic shows the integration of a plant that is subdivided into storage locations and MRP areas.



In the plant, there are the storage locations A to H. The storage locations D, E, and F make up the storage location MRP area 1, the storage locations G and H make up the storage location MRP area 2. The storage locations A, B, and C are not assigned to any MRP area. As a result of integration, there are three locations in the SCM system: the plant location and one location each for the storage location MRP areas 1 and 2.

On the basis of these locations, you can carry out a plant-internal supply chain planning in SAP APO, for example. You can use the products and sources of supply that were automatically distributed to the storage location MRP areas during the transfer of the storage location MRP areas from the ERP system for this purpose.

Prerequisites

In order that you can integrate storage location MRP areas, the systems involved have to fulfill the following prerequisites:

System Release

ERP system ≥ SAP R/3 4.6C *

SAP R/3 Plug-In ≥ PI 2003.1


System Release

SCM system ≥ SAP APO 4.0

The main differences between the various ERP Releases are shown in the following table:

Function/Release 4.6C 4.70 4.70 + Extension 2.0

Mass maintenance for material master

assignments to MRP areas

X X X

Change documents for material master assignments

X X X

System-supported restructuring of MRP areas

X X X

Stock transport orders between MRP areas

X

Features

Integration of Master Data

The following tables contain information on the integration of storage location MRP areas and master data, which is relevant to planning with storage location MRP areas.

Object Integration

Storage location MRP area A storage location MRP area of the ERP system is automatically created in the SCM system as a location of the type storage location MRP area (1007).

The plant to which the storage location MRP area belongs in the ERP system is automatically entered in the location product master of the storage location MRP area in the SCM system. The link between the storage location MRP area and the plant thus also exists in the SCM system.



Object Integration

Storage locations The storage locations of a storage location MRP area are automatically transferred to the location master of the storage location MRP area in the SCM system.

You cannot change the assignment of the storage locations to the storage location MRP area in the SCM system. The receiving storage location of the storage location MRP area in the ERP system is automatically flagged as the leading storage location in the location master in the SCM system. In the graphic (see above), the receiving storage locations in the ERP system and the leading storage locations in the SCM system are marked with an asterisk (*).

Further information is available in the SAP Help Portal under

http://help.sap.com SAP Supply Chain Management

SAP Advanced Planning and Optimization Production

Planning and Detailed Scheduling (PP/DS) Supply Chain

Planning Within a Plant Storage Location MRP Area in SAP

APO.

Address of the storage location MRP area in SAP APO The first address of the receiving storage location of the storage location MRP area in the ERP system is automatically transferred to the SCM system as the address of the storage location MRP area. If the receiving storage location does not have an address, the storage location MRP area in the SCM system acquires the address of the plant to which it belongs.

NoteIn the ERP system, a storage location MRP area cannot apply to all plants, all countries, or all time zones. Therefore, the address of the receiving storage location has to be in the same country and the same time zone as the plant.


Object Integration

Products The materials of a plant in the ERP system that you have selected for transfer are automatically transferred to the plant location. Materials that are also assigned to a storage location MRP area in SAP R/3 are automatically transferred as location products to this storage location MRP area.

NoteIf you have entered the special procurement type stock transfer from own plant to MRP area for a material in the storage location MRP area in the ERP system, a transportation lane between the plant location and the storage location MRP area is automatically created in the SCM system when the material is transferred.

Sources of supply On the basis of storage location information, sources of supply are automatically transferred to the locations (plant location or storage location MRP areas) for which they are relevant (see Distribution of Sources of Supply).

If you are working with SAP Advanced Planning and Optimization (SAP APO), the following applies:

For a production process model or PP/DS runtime object, the issuing storage location for a component or the receiving storage location for a co-product or by-product is determined automatically during the transfer. The storage location is entered in the plan of the source of supply in SAP APO. Further information is available in the SAP Help Portal

under http://help.sap.com SAP Supply Chain

Management SAP Advanced Planning and Optimization

Production Planning and Detailed Scheduling (PP/DS)

Supply Chain Planning Within a Plant Integration of

Storage Location MRP Areas Distribution of Sources of

Supply and under Storage Location Determination in Source Transfer to SAP APO .

Resources You define resources in the ERP system at the plant level. Therefore, they are always transferred to the plant location.

Integration of Transaction Data from SAP R/3 to SAP APO

The following applies only if you are working with SAP APO:

In the ERP system, transaction data is uniquely assigned to a plant and a storage location. In SAP APO, plant and storage location together uniquely define a certain location. The transaction data for a product is automatically transferred to the corresponding location if the following prerequisites are fulfilled:

● The product is created in the location



● If the location is a storage location MRP area, the storage location MRP area must be integrated with SAP APO

If these prerequisites are not fulfilled, the transaction data is automatically transferred to the plant location.

Integration of Transaction Data from SAP APO to SAP R/3

The following applies only if you are working with SAP APO:

In order that you can transfer orders with a receipt in a storage location MRP area from SAP APO to the ERP system, you must have created distribution definitions at plant location level in SAP APO in Customizing for Integration .

Activities

You use the process Initial Transfer of Storage Location MRP Areas to integrate storage location MRP areas and the assigned products and sources of supply with SAP APO. Further information is available in the SAP Help Portal under http://help.sap.com SAP Supply Chain Management SAP Advanced Planning and Optimization Production Planning and Detailed Scheduling (PP/DS) Supply Chain Planning Within a PlantIntegration of Storage Location MRP Areas Initial Transfer of Storage Area MRP Areas.

If you make changes to the MRP areas in the course of time (for example, deletion of the assignment of a material to an MRP area or assignment of the material to a different MRP area), note the following: In the case of all changes that you make to MRP areas in the R/3 or ERP system, the transaction data in the R/3 or ERP system is automatically adjusted to the changed situation. SAP APO does not automatically adjust the transaction data. The user must make the necessary data adjustments manually. Further information is available in the SAP Help Portal under http://help.sap.com SAP Supply Chain Management SAP Advanced Planning and Optimization Production Planning and Detailed Scheduling (PP/DS) Supply Chain Planning Within a Plant Integration of Storage Location MRP Areas Delete Assignment of a Material to an MRP Area.

See also:

http://help.sap.com SAP ERP Central Component Logistics Production Planning and Detailed Scheduling (PP) Material Requirements Planning Special Planning Process MRP Area.

5.9.2 Integration of Products

Use

When materials are transferred to the SCM system via the Core Interface (CIF), they are created there as products. The following provides you with information on the integration of the product master data.


Integration

To enable the planning of a product, the following master data is transferred from the ERP system:

● Basic dataThis is location-independent master data.

● IdentificationA product is identified via the European Article Number (EAN) and the ERP material number. The latter is called the external product number in the SCM system.

● Unit conversion● Classification

This master data from the ERP system involves data for characteristic determination.

Integration of the External Material Group

The external material group is transferred as an attribute to the SCM system together with the material. If you set the External Material Group indicator in Customizing for the product master under Product Groups Define Product Group Types, you specify that the external material group is to be mapped to the SCM system as a product group of this product group type. You can set this indicator for one product group type only.

Constraints

The planner in SAP APO does not correspond to the MRP controller in SAP ERP and is not transferred to SAP APO. If it is required to match the MRP controller to the SAP APO planner, it must be considered that the field planner in SAP APO has three characters and is independent of a location (in contrast to SAP ERP).

5.9.2.1 Integration of Location Products

Use

In the following, the integration of location products is described.

Integration

The location product of the SCM system is supplied with plant material data from the ERP system.

If you are working with SAP Advanced Planning and Optimization (SAP APO), the following also applies:

● RequirementsThe subareas Planning Strategy and Dependent Requirements are supplied from the ERP system; dynamic pegging can only be maintained in SAP APO.

● Lot sizeThe parameters for calculating the lot size and the range-of-coverage (days' supply) determination are adopted from the ERP system (corresponds to the lot size data in the ERP system).

● SNP2You can maintain this data entirely in the SAP APO system (with the exception of the purchasing group, for which the data is taken from the ERP system).



● PP/DSAll fields on this tab page are SAP APO fields and are only maintained in SAP APO.

● GR/GIThe parameters for procurement type, planned delivery time, goods receipt, and goods issue are taken from the ERP system. You can maintain the remaining data in SAP APO.

● ATP○ Product allocation procedure and sequence of product allocation procedures are maintained in SAP

APO Customizing and selected using the input help (F4).○ The check mode (SAP APO) is transferred from the ERP system (requirement type with correct

requirement class) to SAP APO and created in SAP APO Customizing.○ The checking horizon (SAP APO) is transferred from the ERP system if certain data was maintained in

the material master record for material produced in-house. For more information, see the SAP APO documentation under Global Available-to-Promise Check Methods Product Availability CheckProduct Availability Check Using the Checking Horizon .

○ ATP group, checking horizon, and calendar for checking horizon are maintained in SAP APO Customizing and selected using the input help (F4).

○ Display unit of measure: If you want to use the display units of measure created in the ERP system, you must first transport them there. You can also create them directly in SAP APO.

NoteNote that the MRP planner in the ERP system is plant-dependent but the production planner in SAP APO is not. If the ERP MRP controller is transferred as an SAP APO production planner, the ERP MRP controller must be unique across plants.

5.9.2.2 Integration of Batches

Use

You can transfer batches created in SAP ERP to an SCM system.

ExampleFor the following SAP APO processes it is necessary for batches or their characteristics to be transferred to SAP APO:

● Working with classified stocks● Characteristics-dependent planning (CDP)● Characteristics-based product availability check● Planning with shelf life

If you want to work with these processes in SAP APO 4.0, you must explicitly transfer the batches to SAP APO as new objects.

Characteristics-Dependent Planning (CDP) and the characteristics-based product availability check cannot process batch valuations that contain multiple values or intervals.

For more information about characteristics-dependent planning (CDP), see SAP Library on SAP Help Portal at http://help.sap.com SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and


Optimization (SAP APO) Production Planning and Detailed Scheduling (PP/DS) Planning with Characteristics Characteristics-Dependent Planning (CDP) .

For more information about characteristics-based product availability check, see SAP Library on SAP Help Portal at http://help.sap.com SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and Optimization (SAP APO) Global Available-to-Promise (Global ATP) Check Methods Product Availability Check Characteristics-Based Product Availability Check .

Prerequisite

In your SAP ERP system that has been released before ERP 2005, you have implemented SAP ERP Plug-In 2003 1 with SAP ERP Basis Release 4.6 B or higher.

To ensure that the batches retain the characteristic value assignments in the connected SCM system, you have transferred the relevant classes and characteristics by including the classes and characteristic in the same integration model or transferring them beforehand in another integration model.

Features

Batches in the Connected SCM System

In the connected SCM system, batches are called versions and are displayed on the Versions tab page in the product view. In the SCM system, batch properties are stored as classifications.

In the SCM system, batches are classified with class type 230. If SAP Supply Network Collaboration (SAP SNC) is installed in the SCM system, an additional class of class type 232 is created for use in SAP SNC that refers to the class of class type 230.

For more information, see SAP Library on SAP Help Portal at http://help.sap.com SAP Supply Network Collaboration (SAP SNC) Work Order Collaboration Work Order Collaboration with Batch-Managed Products

Master Data for WO Collaboration with Batch-Managed Products Transferring Configurable Materials or Batch-Managed Materials via CIF .

NoteTo transfer the classes to the SCM system, you must create the necessary organizational areas for the class type 230, in Customizing for the SCM system under Cross-Application Components Classification System Classes Maintain Object Types and Class Types.

Preparation of Batches in SAP ERP for Transfer to the Connected SCM System

In SAP ERP you classify batches that you want to use in the SCM system with the class type 023. If the batches are uniquely defined at plant level (class type 022), you must convert the batch level to material or client level (class type 023) before transfer to the SCM system. To do this, choose in Customizing for Batch Management Specify Batch Level and Activate Status Management.

All affected ERP systems must use class type 023 for batch classification. So that batch master data (for example, status of the batch) is transferred to the SCM system, the object characteristic data in SAP ERP must be copied to the classification.



To transfer batches from SAP ERP to the SCM system, assign the batches to the integration model in SAP ERP and execute the initial data transfer. If you use SAP APO 4.0 and still require classified stocks of batch-managed material for your processes, you must include the material for which batches are to be transferred in your existing integration model or in a new integration model. Set the Transfer batches of material indicator in the integration model for the material. This indicator is available as of Plug-In 2003.1 in SAP ERP Basis Releases 4.6.B or higher.

Deactivation of Batches in SAP ERP

In the batch master in SAP ERP, the indicator Batch no longer active was introduced with SAP ERP Basis Release 4.7, Support Package 3 (for earlier SAP ERP releases, see SAP Note 533068). If you set this indicator, the corresponding batch is not transferred to the SCM system. If postings are executed for deactivated batches, the indicator is reset and the batches are transferred to the SCM system again.

You can select the Batch no longer active checkbox in the SAP ERP System with the RVBDEACT report. We recommend that you execute this report before the initial data transfer at regular intervals. In the batch master transaction, the indicator is not visible. Changes to the indicator value are documented with the change documents in the batch master (tab Changes).

Note on Upgrade to SAP APO 4.0

If you have already worked with the processes mentioned above in earlier SAP APO Releases, then, when you upgrade to SAP APO 4.0, you must first retransfer the classes from SAP ERP to SAP APO using an initial data transfer. This is necessary so that the classes are created in the class types 230 (batches) and 400 (CDP) in SAP APO. You then transfer the classified batches from SAP ERP to SAP APO.

5.9.3 Integration of External Procurement Relationships

Use

You can transfer external procurement relationships from the ERP system to the SCM system via the Core Interface (CIF). For more information on integrating the individual external procurement relationships, see:

● Integration of Purchasing Info Records [page 232]● Integration of Contracts [page 234]● Integration of Scheduling Agreements [page 236]

Features

Initial data transfer

For the initial transfer of external procurement relationships from the ERP system to the SCM system, you create an integration model in the ERP system in which you specify which data is to be transferred to the SCM system. You then activate the integration model.

NoteIn the ERP system, you can use contracts (centrally agreed contracts) and purchasing info records on a cross-plant basis simply by not assigning a plant. If you transfer such a centrally agreed contract or cross-


plant purchasing info record to your SCM system, an external procurement relationship will be created for each plant of the relevant purchasing organization that exists in your SCM system.

Change transfer

If purchasing document or master data has changed, you can carry out a transfer of the changed data. To do so, from the menu of the ERP system, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Change Transfer Master Dataand set theSources of Supplyindicator. The system then transfers changes made to purchasing info records, contracts, and scheduling agreements to the SCM system. The transfer of changes may result in data that you have changed in the SCM system being overwritten.

Example

In the SCM system, you have an external procurement relationship for item 10 of scheduling agreement no. 5500000001 from your ERP system. In the SCM system, you change the planned delivery time for this external procurement relationship from 5 days to 3 days .

In the ERP system, the original planned delivery time is then changed from 5 days to 6 days . The changed planned delivery time is now transferred from the ERP system to the SCM system. The planned delivery time amounting to 3 days in the SCM system is overwritten by the planned delivery time that was changed to 6 days in the ERP system.

5.9.3.1 Integration of Purchasing Info Records

Use

This section informs you how purchasing info records are transferred from the ERP system to the SCM system.

Features

To assign several production versions to a subcontracting info record in SAP ERP, starting from the SAP Easy Access screen, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Environment Data Transfer Assign Multiple Production Versions.

To specify that SAP ERP transfers purchasing info records to which several production versions are assigned to SAP SCM, in the Implementation Guide (IMG) choose Integration with Other SAP Components Advanced Planning and Optimization Basic Settings for Data Transfer Change Transfer Change Transfer for Master Data Configure Change Transfer for Master Data.



Furthermore, in the case of purchasing info records with several production versions you can flag individual versions as invalid. In the course of the initial data transfer to SAP SCM, SAP ERP transfers only production versions that are not flagged as invalid. To flag production versions as invalid, you have two options:

● You can do so manually by setting the Production Version Invalid indicator for the relevant production version.From the SAP Easy Access screen, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Environment Data Transfer Assign Multiple Production Versions.

● You can have the check as to whether production versions are valid run by the system in the background via the report SET_PRODVER_VALIDITY. When using the check report, you have two options:○ Select Invalid Entries

If you choose this option, the system merely selects the invalid production versions and does not include them in the initial transfer of data to SAP SCM. This is the standard setting.

○ Delete Invalid EntriesIf you choose this option, the system automatically deletes the invalid production versions.

Question Answer

Are the ERP purchasing info record categories relevant to the transfer?

The purchasing info record category (standard, subcontracting, consignment) on the ERP side determines the form of procurement on the SCM side.

How is the area of validity regulated? If the purchasing info record is assigned to the purchasing organization and the plant on the ERP side, a transportation lane from the vendor (source location) to the relevant plant (destination location) and an external procurement relationship are created on the SCM side.

If the purchasing info record is just assigned to the purchasing organization on the ERP side, a transportation lane from the vendor (source location) to all plants (destination locations) belonging to this purchasing organization plus an external procurement relationship in each case are created on the SCM side.

A prerequisite for the creation of external procurement relationships in the SCM system is that the vendor master record (source location), the plant (destination location), and the material master at plant level (destination location) already exist in the SCM system.

How is the validity period regulated? The validity period of the purchasing info record (LIFAB - available/deliverable from, LIFBI - available/deliverable until) is transferred to the SCM system. If a validity period is not specified on the ERP side, the validity period 01/01/1990 to 12/31/9999 is created on the SCM side.

The validity period of the conditions (prices) is transferred to the SCM system.


Question Answer

Is the planned delivery time taken into account in the purchasing info record?

The planned delivery time is transferred to the SCM system as well.

Is the minimum quantity taken into account in the purchasing info record?

The minimum quantity is not transferred to the SCM system.

Are the prices taken into account in the purchasing info record?

The prices (including the scale prices) are transferred to the SCM system. In addition to the prices from the purchasing info record, conditions are taken from the vendor master to calculate the effective price.

(SAP Note 368887: CIF Change Transfer of External Procurement Relationships describes for which tables a change pointer is written. If a change pointer is written, the purchasing info record is taken into account in the change transfer.)

Which data from the General Data view is taken into account in the purchasing info record?

None.

Which data from the Purchasing Organization Data view is taken into account in the purchasing info record?

Planned delivery time, net price, validity to.

Which data from the Conditions view is taken into account in the purchasing info record?

Scale prices.

Which additional data is taken from the purchasing info record?

Purchasing info record number, vendor, material number, purchasing organization, plant, and purchasing info record category.

Which conditions are taken into account for generating change pointers?

The only conditions taken into account during the generation of change pointers are those that are also used in ALE master data distribution for the COND_A message. You can display or alter the change documents (stored in table TBD62 ) taken into account for distributing external procurement relationships by using transaction BD52 and message type CIFSRC (conditions are stored as entries with the object COND_A ). See also SAP Note 368887, which is mentioned above.

5.9.3.2 Integration of Contracts

Use

This section informs you how contracts are transferred from the ERP system to the SCM system.



Features

Question Answer

Are the ERP item categories relevant to the transfer? The item category (standard, subcontracting, consignment) on the ERP side determines the form of procurement on the SCM side.

Are the contract types Quantity Contract or Value Contract relevant to the transfer?

The contract types are not relevant.

How is the area of validity regulated? The item data is assigned to the plant. As a result of this, for every contract item on the ERP side, both a transportation lane from the vendor (source location) to the plant in question (destination location) and an external procurement relationship are created in the SCM system.

How is the validity period regulated? The validity period of the contracts is transferred from ERP to the SCM system.

The validity period of the conditions (prices) is transferred from ERP to the SCM system.

How are the target quantity and the target value taken into account in the contract?

The target quantity and the target value are not transferred to the SCM system.

Is the planned delivery time taken into account in the contract?

The planned delivery time is transferred to the SCM system.

Is the goods receipt processing time taken into account in the contract?

The goods receipt processing time is not transferred to the SCM system.

Are the prices taken into account in the contract? The prices (including the scale prices) are transferred to the SCM system. In addition to the prices from the contract, conditions from the vendor master are also used to calculate the effective price.

(Note 368887: CIF Change Transfer of External Procurement Relationships describes for which tables a change pointer is written. If a change pointer is written, the contract is taken into account in the change transfer.)

Are the terms of payment taken into account in the contract?

The terms of payment are transferred to the SCM system.

Are the Incoterms taken into account in the contract? The Incoterms are transferred to the SCM system.

Is the document currency taken into account in the contract?

The document currency is transferred to the SCM system.


Question Answer

Which key figures on the Purchasing Organization Data 1 tab page are taken into account in the contract?

The GR-Based Invoice Verification, No ERS, and No Cash Discount indicators are transferred to the SCM system.

Are the price and the price unit taken into account in the contract?

The price and the price unit are transferred to the SCM system.

Are the PO price and the order unit taken into account in the contract?

The PO price and the order unit are transferred to the SCM system.

Is the conversion of the PO price unit into the order unit taken into account in the contract?

The conversion of the PO price unit into the order unit is transferred to the SCM system.

Is the conversion of the order unit into the base unit taken into account in the contract?

The conversion of the order unit into the base unit is transferred to the SCM system.

Is the invoicing party taken into account in the contract? The invoicing party is transferred to the SCM system.

Is the jurisdiction code taken into account in the contract? The jurisdiction code is transferred to the SCM system.

Is the final invoice indicator taken into account in the contract?

Thefinal invoice indicator is transferred to the SCM system.

5.9.3.3 Integration of Scheduling Agreements

Use

This section informs you how scheduling agreements are transferred from the ERP system to the SCM system.

NoteIf you want to include stock transport scheduling agreements in the initial data transfer, you must specify the supplying plants in the selection.

Features

Question Answer



Which agreement types are relevant? If scheduling agreement delivery schedule lines are to be created in the SCM system, the agreement type LP is relevant. If not, LPA should be used. (See also SAP Note 335097: Agreement Type in the Case of SAP APO Scheduling Agreement)

Are the ERP item categories relevant to the transfer? The item category (standard, subcontracting, consignment) on the ERP side determines the form of procurement on the SCM side.

How is the area of validity regulated? The item data is assigned to the plant. As a result, a transportation lane from the vendor (source location) to the relevant plant (destination location) and an external procurement relationship are created in the SCM system for each item of the scheduling agreement on the ERP side.

How is the validity period regulated? The validity period of the scheduling agreements is transferred from the ERP system to the SCM system.

The validity period of the conditions (prices) is transferred from ERP to the SCM system.

How is the target quantity taken into account in the scheduling agreement?

The target quantity is not transferred to the SCM system.

Is the planned delivery time taken into account in the scheduling agreement?

The planned delivery time is transferred to the SCM system.

Is the goods receipt processing time taken into account in the scheduling agreement?

The goods receipt processing time is not transferred to the SCM system.

Are the prices taken into account in the scheduling agreement?

The prices (including the scale prices) are transferred to the SCM system. In addition to the prices from the scheduling agreement, conditions from the vendor master record are also used to calculate the effective price.

The price unit and the order price unit are transferred to the SCM system.

(SAP Note 368887: CIF Change Transfer of External Procurement Relationships describes for which tables a change pointer is written. If a change pointer is written, the scheduling agreement is taken into account in the change transfer.)


What is the significance of the External Scheduling field? If this field is set to 1 (planning and release generation in the SCM system), the requirement coverage elements are created as schedule lines on the SCM side. Release creation and message output is thus mandatory in the SCM system. No more scheduling agreement delivery schedule lines can then be entered in the ERP system. The agreement type should thus be LP .In the SCM system, these external procurement relationships can then be found under scheduling agreement SCM .

If this field is left blank, the requirement coverage elements are created as purchase requisitions on the SCM side. The requisitions can then be assigned to the scheduling agreement on the ERP side. Release creation and message output thus take place in the ERP system. The agreement type should be LPA .This approach should be chosen for subcontracting scheduling agreements because it is not currently possible to plan subcontracting scheduling agreements on the SCM side.It is possible to set a conversion indicator for purchase requisitions referencing a scheduling agreement in the SCM system. In this case, the requisitions are converted into scheduling agreement delivery schedule lines when they are transferred to the SCM system. In the SCM system, these external procurement relationships can then be found under scheduling agreement .

Are the terms of payment taken into account in the scheduling agreement?

The terms of payment are transferred to the SCM system.

Are the Incoterms taken into account in the scheduling agreement?

The Incoterms are transferred to the SCM system.

Is the document currency taken into account in the scheduling agreement?

The document currency is transferred to the SCM system.

Which key figures on the Purchasing Organization Data 1 tab page are taken into account in the scheduling agreement?

The GR-Based Invoice Verification, No ERS, and No Cash Discount indicators are transferred to the SCM system.

Is the order unit taken into account in the scheduling agreement?

The order unit is transferred to the SCM system.

Is the conversion of the order unit into the base unit taken into account in the scheduling agreement?

The conversion of the order unit into the base unit is transferred to the SCM system.

Is the invoicing party taken into account in the scheduling agreement?

The invoicing party is transferred to the SCM system.

Is the jurisdiction code taken into account in the scheduling agreement?

The jurisdiction code is transferred to the SCM system.



Is the final invoice indicator taken into account in the scheduling agreement?

The final invoice indicator is transferred to the SCM system.

5.9.4 Integration of Classes and Characteristics

Use

To transfer classes and characteristics, you create your own integration model in the SAP ERP system. You specify in the integration model which characteristics and class types are to be transferred to the connected SCM system.

The integration models for classes and characteristics should not contain any other objects to keep the integration of classes and characteristics of other master data separate. Any changes made to the integration model that are required because of other objects do not result in the characteristic and class master data being transferred again.

Prerequisites

Determine the scope of the class and characteristic master data to be transferred in the integration model by specifying the organizational area. In the SAP ERP system, assign a special organizational area that you also specify in the integration model to the characteristics to be transferred to the connected SCM system.

The organizational areas must be created before the classes and characteristics are transferred to the SCM system. The characteristics and classes are still transferred to the SCM system, even if the organizational areas are not maintained in the SCM system, but you cannot display input help for the characteristics in the SCM system, for example.

1. In Customizing for the SCM system, choose Cross-Application Components Classification SystemClasses Maintain Object Types and Class Types.

2. Select the table /SAPAPO/MATKEY and choose Organizational Areas.3. Choose New Entries to create new organizational areas.

ExampleTo use characteristic-dependent planning (CDP), the ERP technical names of the batch class and the variant class must be the same (class type 023 and 300 ). In the SCM system, the characteristics of these two classes are merged to create the class type 400 after CIF transfer.

NoteNo changes can be made in a productive ERP system.


Features

APO-Specific Features

In the SAP APO system, inbound processing is then executed depending on Customizing. If the CDP configuration procedure has been configured for the system, a class is automatically created in the SAP APO system for class types 023 and 300. This class has the same name as class type 400.

NoteClass and characteristic master data can only be integrated from a logical system in the SCM system. Errors can occur during the transfer if a characteristic or a class is transferred to the SCM system and a characteristic (or class) with the same name has already been transferred from another source system. This prevents identically named but semantically different objects from mixing.

To influence which classes are to be created in SAP APO for CDP, you can use the BAdI Control Class Assignments for CDP with the method CDP_CLASSES_FILTER in Customizing under Advanced Planning and Optimization Master Data Classification and Configuration Business Add-Ins (BAdIs) for Classification and Configuration.

Additional Characteristics

In the integration model, you can specify characteristics in the Additional Characteristics field that are not assigned to an SCM-system-relevant class. This can be useful for reference characteristics (these can be used in the production data structure for CDP).

If you only want to integrate additional characteristics in the connected SCM system, but no classes, then specify an organizational area not to be used in classes in the integration model.

Object Characteristics/Check Table Characteristics in SAPAPO

These characteristics refer to a table that usually has a different name in SAP ERP from the one in SAP APO. The table reference must therefore be adjusted in a customer enhancement, or subsequently in SAP APO.

Reference characteristics are used in object dependencies and can be evaluated with production data structures (PDS) in SAP APO. For more information, see SAP Library on SAP Help Portal at http://help.sap.com SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and Optimization (SAP APO) Production Planning and Detailed Scheduling (PP/DS) Planning with Characteristics Prerequisites for Planning Production Data Structures (PDS) for CDP and Block Planning.

To adjust the reference characteristics to the APO-specific tables, make the necessary settings in Customizing under Advanced Planning and Optimization Master Data Classification and Configuration Map Object Characteristics .

You can also use the BAdI Map Object Characteristics in SAP APOin Customizing under Advanced Planning and Optimization Master Data Classification and Configuration Business Add-Ins (BAdIs) for Classification and Configuration .

The reference characteristics should not be contained in classes with class type 400 and should only be used in object dependencies. Therefore, integrate reference characteristics as additional characteristics in SAP APO.



Activities

1. In theSAPERP system, choose Logistics Central Functions Supply Chain Planning Interface Core Interface Advanced Planner and Optimizer Integration Model Create .

2. In the Material Independent Objects section, select the Classes/Charact indicator and choose Special Restrictions .

3. Specify the organizational area for the SCM-specific characteristics for Org. area ind .4. Specify the class type 300.5. Save and activate your integration model.

If an active integration model containing other objects in addition to classes and characteristics already exists, proceed as follows to split the integration models:

1. Use the filter object search for the integration model, if required, to determine the use of organizational areas in active integration models.

2. Generate and activate a second integration model that only contains SCM-relevant classes and characteristics (when activating the integration model, the system does not transfer data again to the SCM system because all affected classes and characteristics are already contained in the active integration model).

3. Generate a new version of the first integration model that contains all objects of the active version except for the classes and characteristics.

4. Activate the new version of the integration model. Here, the system does not transfer the data again to the SCM system because all objects are already contained in an active integration model (old version).

See also:

For more information about integration of classes and characteristics in SAP APO, see the following topicson SAP Help Portal at http://help.sap.com SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and Optimization (SAP APO) Production Planning and Detailed Scheduling (PP/DS) Planning with Characteristics Prerequisites for Planning Integration of Classes and Characteristics :

● Class Type 400 in SAP APO● Definition of Classes for CDP● Definition of Characteristics for CDP● Organizational Areas for Characteristics

5.9.5 Integration of Batches

Use

You can transfer batches created in SAP ERP to an SCM system.


ExampleFor the following SAP APO processes it is necessary for batches or their characteristics to be transferred to SAP APO:

● Working with classified stocks● Characteristics-dependent planning (CDP)● Characteristics-based product availability check● Planning with shelf life

If you want to work with these processes in SAP APO 4.0, you must explicitly transfer the batches to SAP APO as new objects.

Characteristics-Dependent Planning (CDP) and the characteristics-based product availability check cannot process batch valuations that contain multiple values or intervals.

For more information about characteristics-dependent planning (CDP), see SAP Library on SAP Help Portal at http://help.sap.com SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and Optimization (SAP APO) Production Planning and Detailed Scheduling (PP/DS) Planning with Characteristics Characteristics-Dependent Planning (CDP) .

For more information about characteristics-based product availability check, see SAP Library on SAP Help Portal at http://help.sap.com SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and Optimization (SAP APO) Global Available-to-Promise (Global ATP) Check Methods Product Availability Check Characteristics-Based Product Availability Check .

Prerequisite

In your SAP ERP system that has been released before ERP 2005, you have implemented SAP ERP Plug-In 2003 1 with SAP ERP Basis Release 4.6 B or higher.

To ensure that the batches retain the characteristic value assignments in the connected SCM system, you have transferred the relevant classes and characteristics by including the classes and characteristic in the same integration model or transferring them beforehand in another integration model.

Features

Batches in the Connected SCM System

In the connected SCM system, batches are called versions and are displayed on the Versions tab page in the product view. In the SCM system, batch properties are stored as classifications.

In the SCM system, batches are classified with class type 230. If SAP Supply Network Collaboration (SAP SNC) is installed in the SCM system, an additional class of class type 232 is created for use in SAP SNC that refers to the class of class type 230.

For more information, see SAP Library on SAP Help Portal at http://help.sap.com SAP Supply Network Collaboration (SAP SNC) Work Order Collaboration Work Order Collaboration with Batch-Managed Products

Master Data for WO Collaboration with Batch-Managed Products Transferring Configurable Materials or Batch-Managed Materials via CIF .



NoteTo transfer the classes to the SCM system, you must create the necessary organizational areas for the class type 230, in Customizing for the SCM system under Cross-Application Components Classification System Classes Maintain Object Types and Class Types.

Preparation of Batches in SAP ERP for Transfer to the Connected SCM System

In SAP ERP you classify batches that you want to use in the SCM system with the class type 023. If the batches are uniquely defined at plant level (class type 022), you must convert the batch level to material or client level (class type 023) before transfer to the SCM system. To do this, choose in Customizing for Batch Management Specify Batch Level and Activate Status Management.

All affected ERP systems must use class type 023 for batch classification. So that batch master data (for example, status of the batch) is transferred to the SCM system, the object characteristic data in SAP ERP must be copied to the classification.

To transfer batches from SAP ERP to the SCM system, assign the batches to the integration model in SAP ERP and execute the initial data transfer. If you use SAP APO 4.0 and still require classified stocks of batch-managed material for your processes, you must include the material for which batches are to be transferred in your existing integration model or in a new integration model. Set the Transfer batches of material indicator in the integration model for the material. This indicator is available as of Plug-In 2003.1 in SAP ERP Basis Releases 4.6.B or higher.

Deactivation of Batches in SAP ERP

In the batch master in SAP ERP, the indicator Batch no longer active was introduced with SAP ERP Basis Release 4.7, Support Package 3 (for earlier SAP ERP releases, see SAP Note 533068). If you set this indicator, the corresponding batch is not transferred to the SCM system. If postings are executed for deactivated batches, the indicator is reset and the batches are transferred to the SCM system again.

You can select the Batch no longer active checkbox in the SAP ERP System with the RVBDEACT report. We recommend that you execute this report before the initial data transfer at regular intervals. In the batch master transaction, the indicator is not visible. Changes to the indicator value are documented with the change documents in the batch master (tab Changes).

Note on Upgrade to SAP APO 4.0

If you have already worked with the processes mentioned above in earlier SAP APO Releases, then, when you upgrade to SAP APO 4.0, you must first retransfer the classes from SAP ERP to SAP APO using an initial data transfer. This is necessary so that the classes are created in the class types 230 (batches) and 400 (CDP) in SAP APO. You then transfer the classified batches from SAP ERP to SAP APO.


6 Alert Monitor

Use

You can use the Alert Monitor to monitor whether your application is running without problems. To do this, for each of the applications you work with, you use alert profiles to specify in what situations the system reports the problem, in other words, generates an alert. In the Alert Monitor window, you can monitor all the alerts that have occurred, and can navigate directly to the relevant application function to resolve the problem. For more information, see Alert Monitor Window [page 245].

NoteThis Alert Monitor is not the same as the Alert Monitor in the Web Application Server. For more information, see SAP Library on SAP Help Portal at http://help.sap.com under SAP NetWeaver Prior to SAP NetWeaver 2004 SAP NetWeaver Components SAP Web Application Server Computing Center Management System (BC-CCM) Monitoring in the CCMS The Alert Monitor .

Integration

You can only use the Alert Monitor with SAP Advanced Planning and Optimization (SAP APO), SAP Forecasting and Replenishment and SAP Extended Warehouse Management (SAP EWM). For more information, see the documentation for the relevant application.

Features

The scope of the alerts displayed depends on how you call the Alert Monitor. You can choose from the following options:

● If you call the Alert Monitor directly, the system displays all the alerts determined according to your selected overall alert profile. For more information, see Overall Alert Profile [page 247]. On the initial screen of the Alert Monitor, you can also call up an alert situation that has been determined in the background and saved. You can then process the alerts. For more information, see Determining Alerts in the Background [page 259].

● If you want to use the Alert Monitor within the Supply Chain Cockpit (SCC) in SAP APO, you must assign application-specific alert profiles to your SCC user profile. In the upper right area of the SCC, you can see the existing alerts for the applications.

● If you call the Alert Monitor from an application, the system only displays alerts for the alert types that exist for the objects that you are processing in the application, and that you have selected in the relevant application-specific alert profile. For more information, see Application-Specific Alert Profile [page 248].


Alert Monitor

● If you want to view all alerts for individual objects, such as for a particular location product, irrespective of which application the alerts were generated, you can use the Alert Overview by Objects function. For more information, see Alert Overview by Objects [page 254].

6.1 Alert Monitor Window

Definition

Displays the alerts depending on the chosen overall alert profile or application-specific alert profile.

Use

You can access Alert Monitor Profile Maintenance from the Alert Monitor window, by choosing the Alert Profile pushbutton. For more information, see Alert Profile Maintenance [page 246].

You can manage your favorites, assign and adopt substitutes, schedule running alerts in the background and change user-specific settings, by choosing the Favorite Management pushbutton. For more information, about favorite management, see Assigning Favorites and Substitutes [page 255]. For more information about user-specific settings, see User-Specific Display Hierarchy [page 254].

Structure

The Alert Monitor window consists of the following screen areas:

Alert Profile Selection

Here you select the overall alert profiles, for which you want the system to display alerts. You can choose overall alert profiles from the following selection options:

● FavoritesHere, you can select the overall alert profiles you previously saved as favorites.

● SubstitutionsHere you can select other users' overall alert profiles, and work with these as a substitute, if they first appoint you as a substitute, and then you accept the appointment by choosing Adopt Substitute.

● Saved Alert SituationsHere you can select overall alert profiles that have been processed in the background.

Alert View Selection

Here, the system displays the number and priority of alerts for each hierarchy node. You can select alerts to be displayed in detail by selecting the Selection checkbox.

You can configure the display hierarchy for the object selection in the User-Specific Display Hierarchy.

SCM BasisAlert Monitor P U B L I C 245

If you click a priority icon, the system only displays alerts of the selected priority for the hierarchy node you choose.

Display Area of the Alerts

Here, the system displays a list of all the selected alerts. For further processing, the following functions are available:

● You can process alerts, for example hide, forward, freeze or delete them, send them as a document, email or SMS, or take note of them.

● Depending on the alert type, you can use the context menu of an alert to go to the corresponding application functions to resolve the planning problems that caused the alert.

● You can, for example, sort, filter, print, export, or change the layout of the list.

● You can change the time zone used in the display in the Alert Monitor window, by choosing Goto Environment Time Zone for Display .

6.2 Alert Profile Maintenance

Use

You can use Alert Profile Maintenance function to create or maintain overall alert profiles and application-specific alert profiles. You can specify and change alert profile settings and attributes, assign application-specific alert profiles to overall alert profiles and display the relationship between application-specific and overall alert profiles. You can transport alert profiles to other systems.

Features

● To access Alert Profile Maintenance, on the SAP Easy Access screen, choose Advanced Planning and Optimization Supply Chain Monitoring Current Settings Set Alert Monitor . You can also access the transaction by choosing the Alert Profile pushbutton on the Alert Monitor window. For more information, see Alert Monitor Window [page 245].

● You can display or change the overall alert profiles and the application-specific alert profiles by navigating the hierarchy under Alert Profile.

● You can manage your favorites, assign and adopt substitutes, set alerts to be determined in the background, and set up user-specific display hierarchies by choosing User Settings.

● You can run the selected alert profile by choosing Determine Alerts. This function calls the Alert Monitor window to display the alerts determined on the basis of the selected alert profile.

More Information

Overall Alert Profile [page 247]


Alert Monitor

Application-Specific Alert Profile [page 248]

6.2.1 Overall Alert Profile

Definition

Collects application-specific alert profiles and defines the time period for which the system determines alerts.

Use

The overall alert profile includes all selection criteria for the following alerts:

● Alerts that the system displays when you call the Alert Monitor directly.For more information, see Alert Monitor [page 244].

● Alerts for which the system sends an automatic notification.For more information, see Sending Alert Notifications [page 255].

NoteIf you call the Alert Monitor window ( Alert Monitor Window [page 245]) from an application, only the settings made in the application-specific alert profiles are relevant.

In the overall alert profile, you make the following settings:

● Period for which the system determines alerts● Planning version● Application-specific alert profiles assigned● Choose Favorite Management to assign all relevant overall alert profiles to your user. For more information,

see Assigning Favorites and Substitutes [page 255].

● Choose Goto Alert Determination in the Background to configure overall alert profiles for alert determination in the background. For more information, see Configuring Overall Alert Profiles for Alert Determination in the Background [page 260].

● Choose Environment User-Specific Display Hierarchies to configure the hierarchical structure of the tree display for the display screen to your own requirements. For more information, see User-Specific Display Hierarchy [page 254].

Structure

Attributes

Here, you can view or modify the attributes of the overall alert profile.

Settings


● Supply Chain Model/Planning Version ( SAP Advanced Planning and Optimization (APO) only)In the overall profile, you must enter a planning version to be evaluated. The following exceptions apply to this:○ If you want to monitor alerts from Demand Planning (DP) and Supply Network Planning (SNP) but do

not enter a planning version, the system determines alerts for all planning versions.○ The Alert Monitor only determines Available-to-Promise (ATP) alerts for the active planning version

000.○ The system determines SAP ERP MRP alerts without reference to planning versions.

● Period○ Here, you specify an absolute time interval, or an interval relative to the time at which the alerts are

determined by the system.

Application-Specific Profiles

For all applications for which you want to monitor planning using the Alert Monitor, you must define an application-specific alert profile. For more information, see Application-Specific Alert Profile [page 248].

NoteIf you want to call the Alert Monitor window within an application, you can define and save an application-specific alert profile without assigning it to an overall profile.

In the standard system, the selection screen displays all applications when you create an overall profile. If you only want to see the applications that are relevant for you, you can show or hide individual applications in Customizing. For more information, see Customizing under SCM Basis Alert Monitor Activate/Deactivate Applications in the Alert Monitor.

6.2.2 Application-Specific Alert Profile

Definition

Defines application-specific selection criteria for alert determination.

Use

If you want to use the Alert Monitor to monitor an application, you must define an application-specific alert profile for the application.

Depending how you want to call the Alert Monitor, you must select this alert profile at the corresponding point. The following options are available to you:

● If you want to call the Alert Monitor directly, select the alert profile in Alert Profile Maintenance. For more information, see Alert Profile Maintenance [page 246].

● If you want to use the Alert Monitor in SAP Advanced Planning and Optimization (SAP APO) in the Supply Chain Cockpit (SCC), assign the alert profile to your SCC user profile sapurl_link_0003_0002_0010.


Alert Monitor

● If you want to call the Alert Monitor from an application, assign the alert profile to the application.

NoteThe following is valid if you are working in SAP Advanced Planning and Optimization (SAP APO):

To be able to use the Alert Monitor in the detailed scheduling planning board, define a Production Planning and Detailed Scheduling (PP/DS) alert profile and assign this profile to the overall profile for the detailed scheduling planning board.

If you are working with SAP APO, the following alert profiles are available to you:

● Available-to-Promise (ATP) Alert Profile● Forecast Alert Profile● Supply and Demand Planning (SDP) Alert Profile● Transport Load Builder (TLB) Alert Profile● Production Planning and Detailed Scheduling (PP/DS) Alert Profile● Vehicle Scheduling (VS) Alert Profile● ERP Alert Profile● Maintenance and Service Planning (MSP) Alert Profile● Vendor-Managed Inventory (VMI) Alert Profile

For more information, see the documentation of the respective SAP APO application.

Structure

Attributes

You can view and modify the attributes of the selected application-specific alert profile here.

Selection

For each application-specific alert profile, you can select the alerts you want to see from a list of predefined alert types.

● Error (priority one, highlighted in red)● Warning (priority two, highlighted in yellow)● Information (priority three, highlighted in white)

ExampleExample for defining threshold values for the capacity overload:

○ Info alert for overload between 100% and 120%○ Warning alert for overload between 120 % and 150%○ Error alert for overload over 150%

Choose Environment Description Texts to enter a descriptive text for each alert type. This text can, for example, suggest a specific reaction to this alert for the planner. In the Alert Monitor window (see Alert Monitor Window [page 245]), the planner can call this descriptive text using the context menu for the alert.

The alert types are collected into alert object types and can be selected together. In Customizing, you can assign a separate alert status to specific alert object types. For more information, see Global and User-Specific


Alert Status [page 252]. For more information about the alert types generated by the Alert Monitor, see SAP Note 500051.

Overall Profile Assignment

You can view the overall alert profiles assigned to the application-specific alert profile here.

6.2.3 Alert Profile Transport

Use

As of SCM 7.0 you can transport alert profiles between SAP systems. You use the Alert Profile Maintenance function to assign one or more alert profile transport entries to a transport request.

Features

● You can transport several alert profiles in one transport request.● Only the settings of the alert profile are transported. Referenced external objects are not transported with

the alert profile.● The alert profiles are transported in the state valid at the time of transport request release.● In addition to the alert profiles, you can also select selection objects for transport used by the selected

alert profiles.

NoteAlthough you can select selection objects on the basis of alert profiles, the transportation of alert profiles and selection objects are independent of each other.

Activities

The alert profile transport function requires activities on both sides of transportation; the source system as well as the destination system.

Source System

In the source system you select and add alert profiles to transport requests.

For more information, see Settings for Alert Profile Transport [page 251].

Destination System

When the transport reaches the destination system, the transported alert profiles are created or overwritten if they already exist. The imported alert profiles get the Unchecked status and remain in that state until they are checked manually.


Alert Monitor

NoteThe manual check is necessary because the alert profile check cannot be performed by the transport system as part of the import process. Checking the alert profile requires calling several application-specific functions that are running in the logon client. Since the import step of alert profile transport runs in a client other than the target client, the alert profile check cannot be performed during the import process.

NoteThe status of alert profile does not affect how the alert monitor uses the alert profile during the alert determination process.

6.2.3.1 Settings for Alert Profile Transport

Use

As of SCM 7.0, you can transport alert profiles between SAP systems.

Process

Source System

1. You open an alert profile from the hierarchy list under Alert Profile.2. You choose from the following options:

○ Choose Transport Profile (F9) from the toolbar

○ Choose Edit Transport Profile○ Select the alert profile from the hierarchy list and click it with your alternate mouse button, and choose

Transport...

NoteIf you select an overall alert profile you can also select the assigned application-specific alert profiles.

3. You check and prepare the list of selected alert profiles.4. You specify if you want to add selection objects used by the selected alert profiles to the same transport

request. To do so, select the Transport Selections with Profiles checkbox.5. To confirm the alert profile selection, choose Transport.6. You enter the transport request.

Destination System

1. You open the imported alert profile in change mode from the hierarchy list under Alert Profile.2. The system highlights the unchecked alert profiles.

3. You choose Edit Check Profile to perform the check on the alert profile.


4. You save the alert profile, by choosing Save.

6.2.4 Maintaining Selection Objects

Use

Selection objects store selection criteria for defining a business area. To define filter criteria the application-specific alert profiles refer to selection objects.

You can maintain selection objects independently of alert profiles. You can perform the following activities:

● Create● Change/Display● Delete● Transport

The system groups selection objects into selection types, based on the master data objects used by the selection object to define the business area. The following are examples of selection types:

● Location● Product● Location Product● Resource● ATP Category● Means of Transport

Process

1. You choose Environment Maintain Selection Objects to call selection object maintenance.2. You choose the selection objects you want to work with.3. You use your alternate mouse button to select the activity you want to perform on the selection object.

Alternatively, you can delete or transport selection objects by choosing the appropriate toolbar button.

6.3 Global and User-Specific Alert Status

Use

The status of an alert shows you the processing status, gives you a better overview in the Alert Monitor, and simplifies cooperation between several processors.


Alert Monitor

The Alert Monitor contains the following fixed pre-defined alert statuses:

● AK - Take Note of Alerts● FW - Alert Forwarded● HD - Alert Hidden

In Customizing, you can define additional alert statuses. You can also restrict these additionally defined alert statuses to specific alert object types in Customizing.

In Customizing, you can also specify whether an alert status is visible for all users (global alert status) or only for a specific user (user-specific alert status).

Activities

Define and reset alert status

Activities Global Alert Status User-Specific Alert Status

Define additional alert statuses In Customizing for SCM Basis, choose

Alert Monitor Define Additional

Status in Alert Monitor

In Customizing for SCM Basis, choose


Status in Alert Monitor

Choose User to specify the alert status as user-specific.

Restrict additionally defined alert statuses to specific alert object types

In Customizing for SCM Basis, choose

Alert Monitor Limit Additionally-Defined Status to Specific Alert Object

Types

Change validity of an alert status until automatic reset

In Customizing for SCM Basis under


Status in Alert Monitor , enter the required number of days (between 1 and 90 days) in the Days column.

The user-specific alert status is automatically reset after 14 days.

To change the validity, from the SAP

Easy Access screen, choose System

User Settings Own Data and choose the Parameters tab page

Enter the parameter /SAPAPO/ASTAT_DAYS and assign the required number of days as a parameter.

System behavior when resetting an alert status

If a global alert status is overwritten by a user-specific alert status and is reset, then the Alert Monitor displays the previous global alert status.

If a user-specific alert status is overwritten by a global alert status and is reset again, then the Alert Monitor displays no alert status at all.


6.4 Alert Overview by Objects

Use

Whereas the Alert Monitor allows you to display alerts for the individual applications or alert types, the Alert Overview by Objects enables you to display alerts for a particular object, such as a location product. The Alert Overview by Objects shows you the alert types that were generated for this object in different applications. This enables you to track alerts for a location product, for example, across different applications.

Activities

To call the Alert Overview by Objects, on the SAP Easy Access screen, choose SCM Basis Alert MonitorAlert Overview by Objects .

In the user-specific display hierarchy, you can configure which information you want to have displayed in the Alert Overview by Objects. The system sets up a standard display. For more information, see User-Specific Display Hierarchy [page 254].

6.5 User-Specific Display Hierarchy

Use

In the user-specific display hierarchy, you can define the views and information (columns) that you want to have displayed for a particular user on the initial screen of the Alert Monitor and the Alert Overview by Objects.

Features

● You can maintain the user-specific display hierarchy by using drag and drop.● When using drag and drop to copy objects from the column Possible Nodes per Alert View, you have to

position the cursor on the user name. You can also move the objects to their respective columns by double-clicking.

● The system automatically positions the objects in the correct hierarchy position, even if you are combining individual objects from different views.


Alert Monitor

Activities

You call the user-specific display hierarchy as follows:

● From the Alert Monitor menu, under Environment● From the Alert Overview by Objects menu, under Alert Monitor

6.6 Assigning Favorites and Substitutes

Use

If you call the Alert Monitor (see Alert Monitor [page 244]) directly, you assign the overall alert profiles (see Overall Alert Profiles [page 247] ) relevant for your area of responsibility to yourself as favorites. On the initial screen, you can then select from these overall alert profiles. If you cannot monitor your favorites yourself for a period of time, for example, because you are on vacation, you can name a different system user as your substitute.

If you are entered as a substitute for favorites from another system user, you can take over the substitution, by choosing Adopt Substitute. For the given period, the initial screen of the Alert Monitor then allows you to select from your own favorites, and the favorites where you have taken over as the substitute.

Prerequisites

You have defined overall alert profiles. For more information, see Overall Alert Profiles [page 247].

NoteIf you want to manage favorites and substitutions for other users, your system user must be assigned the authorization object C_APO_AMON with activity 22, which is contained in the AMON Superuser role.

6.7 Sending Alert Notifications

Use

It is not always possible for all planners involved to actively monitor alerts in the Alert Monitor. You can use the following notification functions to ensure that each planner is informed of alerts in their area of responsibility:

● Interactive sending of documents for alerts from the Alert Monitor window (see Alert Monitor Window [page 245].)


● Automatic messaging when alerts occur, or at regular intervals.

Features

The following options are available for sending notifications:

● Interactive sending of notificationsIn the Alert Monitor window, you can choose the Send Notification function in the context menu of an alert to create a notification, and to send it to a recipient of your choice. The system automatically copies the description and the corresponding alert parameters (such as priority, product, location) into the notification. You can change the data, enter extra notes, or add an attachment.

● Automatic sending of notifications○ From the Alert Monitor

From the Alert Monitor, you can automatically send notifications to system users to an email address, or to the inbox in the SAP Business Workplace. For more information, see Automatic Sending from the Alert Monitor [page 256].

○ Alert notification using the Alert Notification EngineThe system can use the Alert Notification Engine in SCM Basis to automatically send alert notifications, using all message channels supported by Alert Management in the SAP Web Application Server. For more information, see Alert Notification Engine [page 263] and Sending Alert Notifications Using the Alert Notification Engine [page 257].

6.7.1 Automatic Sending from the Alert Monitor

Use

The Alert Monitor can automatically send notifications of alerts that have occurred for an overall alert profile to a system user by email, or to the inbox in the SAP Business Workplace.

Prerequisites

You have defined an overall alert profile. For more information, see Overall Alert Profile [page 247].

Process

1. On the SAP Easy Access screen, you choose Advanced Planning and Optimization Supply Chain Monitoring Current Settings Set Sending of Alerts .

2. You enter the following data:○ The user that you want to notify


Alert Monitor

○ The overall alert profileYou can only assign one overall alert profile to each system user, which is then used to notify the user.

○ The address (email address or inbox in the SAP Business Workplace)3. You activate automatic notification for this system user

NoteIf you are working with SAP Advanced Planning and Optimization (SAP APO), you can also trigger the sending of notifications manually. To do this, on the SAP Easy Access screen, choose Advanced Planning and Optimization Alert Monitor Send Alerts . Select the system user you want to notify. If you want the system to automatically send notifications at regular intervals, define a variant of report /SAPAPO/AMON_MAIL_BROADCAST. In this variant, select the user to notify and schedule the sending as a regular job.

6.7.2 Sending Alert Notifications Using the Alert Notification Engine

Use

Using the Alert Notification Engine in SCM Basis, the system can automatically send notifications at regular intervals for alerts that exist in the Alert Monitor. You make all the required settings in alert notification profiles.

Process

1. You choose an existing alert notification profile, or create a new one. To create a new alert notification profile, choose Generate New Profile.

2. You enter a description for the alert notification profile, and specify the validity period.3. You specify the mechanism you want the system to use to determine the alerts for which to send

notification.For the mechanism, according to which the alert notification should be triggered, choose the pull mechanism and specify the pull intervals. You cannot use the event mechanism or push mechanism for the Alert Monitor.

4. On the Recipient Determ. (Who?) (Recipient Determination (Who?) tab page, you specify the recipient's data.○ Specify the recipient type.

NoteIf you do not have administrator authorization for the alert messaging profile, you can only enter the recipient type User and your own user name as the recipient. For the Alert Monitor, you can choose between the recipient types User and Message Channel. The recipient type Partner is not available.

5. On the Alert Select. (What?) (Alert Selection (What?) tab page, you specify the details of the alerts you want notifications to be sent about.


Select the alerts for which you want to send a notification. To improve performance, and keep the number and range of notifications to manageable levels, reduce the number of selected alerts as much as possible.○ Enter the application Alert Monitor.○ Enter the overall alert profile (see Overall Alert Profile [page 247]) for which you want to generate a

notification.○ Specify whether notification should only occur using alerts that have not already been confirmed in the

application.○ Enter the minimum priority, and the minimum and maximum age of the alerts for which notifications

should be sent.

NoteYou can use these settings to define an alert notification profile for escalating alerts that have not been confirmed within a longer period of time.

6. On the Send Mechanism (How?) tab page, you specify the send mechanism.○ Enter a message profile. Choose Detail View to create new message profiles or change existing ones. In

the message profile, you specify for example, whether the system sends a separate notification for each alert that occurs, lists all alerts in a collective notification, or creates an aggregated notification that collates all alerts by alert type or by object affected.

NoteYou make these settings regardless of the message channel that you selected. For the message channel SMS it is advisable, for example, to only send aggregated messages.

○ Enter the message channel.All message channels supported by Alert Management in the SAP Web Application Server are available for use. The Alert Notification Engine can also send emails directly. You can choose from the following options:○ If you have selected the recipient type Message Channel, you must enter a message channel and a

corresponding destination address, for example, the message channel SMS and the number of a telephone with SMS capability.

○ If you have selected the recipient type User, you can enter a fixed message channel or you can define various message channels for this particular user, which are available at different times. The system takes the destination address from the communication data stored in the user master record.

7. You specify how the notification should be constructed.○ Select the alert category SCM_ANOT, which is predefined for SAP Supply Chain Management (SAP

SCM). This alert category has been defined so that the alert notification is generated dynamically, according to the entries in the message profile.

NoteFor more information about alert categories, see the documentation for Alert Management for SAP NetWeaver 7.0 (2004s) in the SAP Library under SAP NetWeaver by Key CapabilityApplication Platform by Key Capability Business Services Business Communication ServicesAlert Management (BC-SRV-GBT-ALM) .

8. You activate automatic notification for this system user, by selecting the Actve (Active) checkbox.9. You save the notification profile.


Alert Monitor

10. You schedule a variant of report /SCMB/ANOTPULL, in which the alert notification profile is selected, as a regular job at an interval that is shorter than the pull interval.

NoteYou can also use report /SCMB/ANOTPULL to trigger alert notification manually.

More Information

Alert Notification Engine [page 263].

6.8 Determining Alerts in the Background

Use

The run times for determining alerts can vary, depending on the scope of the overall alert profile you are using. Alert determination in the background enables you to use extensive overall profiles without a waiting time when you access a current alert situation. The system automatically starts alert determination at the time you specify. You can select the time in such a way that alert determination runs a half hour before the working day begins, after the system has completed the nightly planning run. This ensures that the results are available immediately when the working day begins.

Prerequisites

You have defined an overall alert profile (see Overall Alert Profile [page 247]).

Process

1. On the SAP Easy Access screen, choose Advanced Planning and Optimization Demand PlanningPlanning Demand Planning in the Background Job Overview of Demand Planning in the Background to schedule program /SAPAPO/READ_ALERTS_BATCH as a periodic background job. This program determines the alerts for the selected overall profiles and saves them, dependent on the alerts' due dates. For more information, see Determining and Saving Alert Situations [page 261].

2. You configure an overall alert profile for alert determination in the background. For more information, see Configuring Overall Alert Profiles for Alert Determination in the Background [page 260]. Make sure that the time interval for the due date is not smaller than the time interval in which the background job is repeated (see the example below).


3. Alert determination is started at the time when program /SAPAPO/READ_ALERTS_BATCH defines the due date of an overall profile. The system saves the alert situation using the name of the overall profile, including the date and time of the determination.

4. On the initial screen of the Alert Monitor, you call up the saved alert situation using the input help.5. You process the alerts. For more information, see the documentation for the relevant application.6. The system repeats the alert determination at the time interval you have specified in the overall profile, and

then saves the new alert situation. The previous alert situation is deleted automatically. This means you can only call up the last saved alert situation for an overall profile.

Example

You configure the overall profile for alert determination in the background in such a way that the alert determination is due on every hour. You enter a start time 00:00:00 and the repeat interval 1.

Schedule program /SAPAPO/READ_ALERTS_BATCH, so that it always runs a minute after the due time for alert determination. This means that the background job starts at 00:01 and is repeated hourly.

6.8.1 Configuring Overall Profiles for Alert Determination in the Background

Use

To determine alerts in the background (see Determining Alerts in the Background [page 259]), you must configure one or more overall profiles for alert determination in the background. Program /SAPAPO/READ_ALERTS_BATCH can only determine and save alert situations that correspond to an overall profile that has been configured for background determination.

Prerequisites

You have scheduled program /SAPAPO/READ_ALERTS_BATCH as a periodic background job. For more information, see Determining and Saving Alert Situations [page 261].

Process

1. You call up overall profile maintenance for alert determination in the background.On the initial screen of the Alert Monitor, choose Alert Profile. The Alert Profile Maintenance screen appears. Choose Goto Alert Determination in the Background , or from Favorite Management, choose the Alerts in Background tab page.


Alert Monitor

2. You assign a user.If you are setting up an overall profile for alert determination in the background for the first time, you are automatically assigned as an administrator. Each overall profile can only be configured once for alert determination in the background.To assign an overall profile to yourself that you have configured for alert determination in the background, proceed as follows:○ From Favorites Management, you assign yourself the overall profile using drag and drop.○ You manually assign yourself the overall profile when you configure it for alert determination in the

background.You can only enter or change settings for background determination if you are assigned as an administrator (with the exception of the email address).All overall profiles that are configured for alert determination in the background, and for which you are assigned as the user, are displayed in the screen area Overall Profiles Available for Background Determination.

3. You make settings.If you are setting up an overall profile for alert determination in the background for the first time, you can now make any required settings and save them. Make sure that the repeat interval is not smaller than the repeat period for the scheduled background job. The alerts are only determined for as long as the background job has been scheduled. If, for example, the background job is scheduled twice a day, entering a repeat interval of one hour when you configure the overall profile is not useful.

6.8.2 Determining and Saving Alert Situations

Use

You can use program /SAPAPO/READ_ALERTS_BATCH to determine and save alert situations, which you can call up and process at a later point. For determining alerts in the background (see Determining Alerts in the Background [page 259]), you must schedule this program as a periodic background job.

Prerequisites

You have selected alerts in an overall alert profile, which you have set up for alert determination in the background. For more information, see Configuring Overall Alert Profiles for Alert Determination in the Background [page 260].

Process

You can specify the overall profiles for which the system should determine and save the alert situation as follows:

● All due overall profilesIf you select this option, the system first checks which overall profiles are due. When you configure an overall profile for alert determination in the background, you can specify when the overall profile is due for


alert determination. The system determines and saves the alerts for all due overall profiles. At the same time, the system updates the next due date/time, according to the repeat interval, for the overall profiles affected.

● Selected overall profilesHere you can select one or more overall profiles for which the system should determine and save alerts. The system first checks whether the selected overall profiles have reached their due dates, before it determines the corresponding alerts.○ Ignore due dates/times

If you also set this indicator, the system determines and saves the alerts for all selected overall profiles, regardless of their due dates/times.

6.9 Deleting Alerts

Use

Alerts determined by the Alert Monitor, which you have processed and whose causes you have removed, are deleted automatically. For performance reasons, you should regularly delete any alerts that you cannot, or do not want to resolve from the database. You can delete individual alerts directly in the Alert Monitor by choosing Delete Alerts or using the context menu. If you want to delete more than one alert at the same time, you can use this function.

NoteIf you are working with SAP Advanced Planning and Optimization (SAP APO), you can only delete alerts that have been saved to the database. Production Planning and Detailed Scheduling (PP/DS) alerts and dynamic macro-dependent alerts are not saved in the database. These are determined from the SAP liveCache at runtime. These alerts are only removed from the Alert Monitor display when the problem has been resolved.

Process

1. You can call up the deletion report in the overall profile for the Alert Monitor by choosing Goto Deletion of Alerts , or using transaction /SAPAPO/AMON_REORG. Alternatively, on the SAP Easy Access screen, choose Advanced Planning and Optimization APO Administration Reorganization Delete Alerts .

2. You select the alerts to be deleted.3. If you set the Simulation indicator and execute the report, the system displays the alerts selected for

deletion. If you do not set this indicator and execute the report, the system deletes the selected alerts from the database.


Alert Monitor

7 Alert Notification Engine

Use

Via the Alert Notification Engine, the system can automatically send out notifications regarding the occurrence of alerts in an application.

Integration

As standard, the SCM Alert Monitor is connected to the Alert Notification Engine .

The Alert Notification Engine uses the Alert Management facility of the S AP Web Application Server to send out notifications . If you use the alert category SCM_ANOT, which is predefined for the SCM system, the Alert Management settings are not relevant. You specify all necessary data in alert notification profiles.

NoteFurther information is available in the documentation for the Alert Management facility of the SAP Web Application Server in the SAP Library under mySAP Technology Components SAP Web Application Server Basis Services/Communication Interfaces Business Workplace and Services (BC-SRV-OFC)Alert Management (BC-SRV-GBT-ALM) .

Prerequisites

If you want to send notifications relating to alerts that occur in a connected application via the Alert Notification Engine , you must note the following:

● You must define an alert notification profile and a message profile for the Alert Notification Engine .● An alert selection must be defined in the connected application.

Features

The Alert Notification Engine does not store alerts itself but accesses the data stored in the connected application and imports it or filters the data transmitted from the application.

Available Message Channels

You can choose whether alert notifications are to be sent via the Alert Notification Engine directly as e-mails or via message channels supported by the Alert Management facility. If you use Alert Management, the notifications can additionally be displayed in the recipient's alert inbox in a portal.

SCM BasisAlert Notification Engine P U B L I C 263

NoteYou specify which message channels are available for the connected applications, users, and partners in Customizing for the Alert Notification Engine under Message Channels for Alert Notification Engine.

Possible Transmission (Send) Mechanisms

● Push mechanism: With this mechanism, the Alert Notification Engine always automatically sends a notification if an alert is stored in the database in the connected application.

● Pull m echanism: With this mechanism, the Alert Notification Engine sends notifications regarding all selected alerts to the relevant recipient at intervals specified in the alert notification profile. For this purpose, in addition, you must regularly schedule the program /SCMB/ANOTPULL to run at an interval that is shorter than the shortest pull interval specified in the selected alert notification profiles.

● Event m echanism: For this mechanism, the connected application must provide an event. As soon as this event is triggered in the application, the Alert Notification Engine reacts accordingly and sends notifications for all the alerts selected in the alert notification profile.

NoteThe Alert Monitor does not make any events available. The event mechanism cannot therefore be used for this application.

Structure of Notification

You specify how the alert notification is to be structured in the message profile. Depending on the message channel you have chosen, you can choose between the following message modes:

● Individual messageAn individual notification is sent for each alert that occurs.

● Collective messageAll alerts that exist at the time of notification are collected and sent in one message.

● Aggregated messageThe notification contains only the number of all alerts that exist at the time of notification. You can have these numbers broken down according to alert parameters. You define these in the message profile.

Activities

1. Create an alert notification profile and a message profile.2. If you use the pull mechanism, schedule program /SCMB/ANOTPULL to run on a regular basis.

7.1 Alert Notification

Definition

Information transmitted via the Alert Notification Engine telling the recipient that alerts have occurred in a connected application.


Alert Notification Engine

The form of the alert notification is defined by the following profiles:

● Alert notification profile In this you specify the message channels via which the notifications can be transmitted.

● Message profile In this you determine the structure and content of the notification.

Structure

You can define the form of the alert notification in different ways depending on the message channel chosen. Generally speaking, the form is determined from the data set out in the following table:

Feature Meaning

Message mode ● Individual messageA separate notification is sent for each alert that occurs.

● Collective message At the time of notification, a message informing the recipient of all existing alerts is sent.You cannot use this message mode for SMS or pagers.

● Aggregated message At the time of notification, statistics on all alerts that have occurred are sent.

Attachment If you use the message channel e-mail direct , you can choose whether the message texts belonging to the alerts are to be integrated in the notification or provided as an attachment.

Text for message header and reason for message You store the text for the message header and the text to be used as the reason for the notification in a message class of the system. You can use up to four message variables.

Statistics For an aggregated message , you can choose whether the number of existing alerts of a certain type is to be quoted as an absolute or relative figure in relation to the total number, or as a percentage thereof.

Message parameters ● In the case of a collective message, you specify via the message parameters which alerts are to be included in the alert notification.

● In the case of an aggregated message , you determine via the message parameters the objects according to which the alert statistics are to be broken down.


7.2 Creating Alert Notification Profiles

Use

If you wish to send out notifications regarding the occurrence of alerts via the Alert Notification Engine , you must create an alert notification profile.

Prerequisites

The application for which the Alert Notification Engine is to transmit alert notifications uses the SCM Basis . As standard, only the Alert Monitor is connected to the Alert Notification Engine .

Depending on which authorization has been assigned to your system user name, you can use the following transactions for the administration of alert notification profiles:

● Administrator transaction:If you have the administrator authorization, you can use this transaction to create new alert notification profiles for all users, partners, or message channels and subsequently change all such profiles.

● User transactionIf you have no administrator authorization, you can use this transaction to define alert notification profiles in which you yourself are specified as the recipient (recipient type User ).

● Partner transactionIf you have no administrator authorization, you can use this transaction to define alert notification profiles in which partners that are assigned to your user name in the system are specified as recipients (recipient type Partner ).

Procedure

1. Enter a description for the alert notification profile, and specify the validity period.2. Specify the recipient type on the Recipient Determination tab page and the message channel on the Send

Mechanism tab page.All message channels supported by Alert Management in the SAP Web Application Server are available for use. The Alert Notification Engine can also send emails directly.○ If you have chosen the recipient type message channel , you must specify a message channel and a

corresponding destination address (e.g. the message channel SMS and the number of an SMS-compatible telephone).

○ If you have chosen the recipient type User or Partner , you can specify a fixed message channel or define different time-dependent message channels that are available at certain times. The system takes the destination address from the communication data stored in the user master record or the partner administration data.

3. On the Alert Selection tab page, you specify the alerts in respect of which a notification is to be sent. To improve performance, and keep the number and range of notifications to manageable levels, reduce the number of selected alerts as much as possible.



○ Specify the application in which the alerts are to be generated.○ -Specify the alert selection defined in this application for which you wish to have the notification

generated.○ Specify whether notification should only occur using alerts that have not already been confirmedin the

application. Enter the minimum priority, and the minimum and maximum age of the alerts for which notifications should be sent.

NoteWith these settings, you can define an alert notification profile for the escalation of alerts that have not been acknowledged for a long period.

4. Specify how the notification should be constructed.○ Select the alert category SCM_ANOT, which is predefined for the SCM system. This alert category

provides that the alert notification is generated dynamically according to the specifications in the Message Profile [page 268] .

NoteFor more information on Alert Categories , see the documentation for Alert Management for the SAP Web Application Server in the SAP Library under mySAP Technology Components Basis Services/Communication Interfaces Business Workplace and Services (BC-SRV-OFC) Alert Management (BC-SRV-GBT-ALM) .

○ Enter a message profile. Choose Detail View to create new message profiles or change existing ones. In the message profile, you specify, for example, whether the system is to send an individual message for each alert that occurs, list all alerts in a collective message, or create an aggregated message that collates all alerts by alert type and - optionally - by objects affected.

NoteYou make these settings regardless of the message channel that you selected. For the message channel SMS it is advisable, for example, to only send aggregated messages.

5. Specify the mechanismby which alert notification is to be triggered.○ If you choose the pull mechanism, the system reads all the alerts that exist for the specified alert

selection in the application at regular intervals and creates a notification. You specify the interval and the first execution date in the alert notification profile.

○ If you choose the push mechanism , the system sends a notification as soon as an alert is written to the database of the application.

○ For the event mechanism , an event that triggers the notification must be generated in the connected application.

6. Activate and save the alert notification profile.

NoteIf you use the pull mechanism , you must schedule a variant of the program /SCMB/ANOTPULL, in which the alert notification profile has been selected, to run at a regular interval that is shorter than the pull interval.

You can also use this program to manually trigger an alert notification for an alert notification profile with the pull mechanism.


https://help.sap.com/viewer/fff5965a513a4c69ae68f8c6cafb5d22/7.5.16/en-US/4947839537042221e10000000a42189d.html

https://help.sap.com/viewer/fff5965a513a4c69ae68f8c6cafb5d22/7.5.16/en-US/494782b737042221e10000000a42189d.html

7.3 Create Message Profile

Use

In the message profile, you specify how the Alert Notification Engine assembles an alert notification from the selected alerts.

Procedure

1. Assign a short description for the message profile and specify the application in which the alerts will be generated.

2. Specify the message mode.3. Specify the attachment type.4. Specify a system message (message class and message number) in which the text for the header and the

reason for notification has been defined. You can use up to four variables ( Message Variable fields 1 to 4). The name of the alert notification profile, the number of alerts, and the time of creation of the notification can be inserted via the parameters &1, &2, and &3.

5. In the message parameters, you specify the message categories and corresponding alert parameters according to which the individual alerts are to be sorted in the alert notification.

6. For an aggregated message, you use the Column indicator to define a matrix in which the statistical figures are set out. You can set this indicator in several alert parameters and specify the order in which the associated columns are to be arranged.

ExampleYou have chosen the message parameter Location Product View and the alert parameter Location Text for the Alert Monitor .

If you do not set the Column indicator, the numbers of alerts that have occurred are set out as shown in the following table:

Location 1 Product 1 10

Product 2 15

Product 3 27


Product 2 12

Product 3 28




Product 2 58

Product 3 1

If you set the Column indicator, the numbers will be arranged in a matrix as in the following table:

Product Location 1 Location 2 Location 3

Product 1 10 15 6

Product 2 15 12 58

Product 3 27 28 1


8 Process Controller

Use

The process controller is a framework with which you can define your own strategies and methods and the way in which the system executes specific processes. It allows you to define adaptive processes that make it possible for a user to exclude delivered functionality or include new functionality.

In the process controller, you model a process as a strategy. A strategy defines how the system executes a specific service, for example the determination of geocoordinates, to suit your business need.

ExampleYou want to determine geocoordinates using a specific geocoding provider. You use the strategy GC_GIS1.

In the standard system, SAP delivers a number of different strategies that you can use for your various services. The strategy itself is made up of a sequence of methods. The methods define the individual process steps of the strategy. You must assign a service to the strategy as well as to the methods. Different strategies can employ the same method. To change the behavior of the methods that the strategies use, you can define parameters for a method and then assign them to it. For example, you can use a parameter to define the number of expected results for a request. You must implement the logic within the method using the parameter.

CautionIf you include a customer-specific method in a strategy, the method must comply with the standard interfaces of the process controller methods.

In SCM Basis, you can use the process controller to define the following strategies:

● Geocoordinate determination strategies● Distance and duration determination strategies● Static route determination strategies

Prerequisites

In Customizing for SCM Basis under Process Controller, you have made the following settings:

● You have defined a service under Define Service.● You have defined a strategy under Define Strategy.● You have defined one or more methods under Define Methods.● You have assigned the methods to a strategy under Assign Methods to a Strategy.


Process Controller

NoteThe sequence in which you assign the methods to the strategy determines the sequence in which the system processes the methods. Strategies and methods must have the same service. You can also assign one method to multiple strategies.

To further adjust your strategy, you can define parameters under:

● Define Parameters● Assign Parameters to a Method● Assign Method Parameters to a Strategy

NoteThe definition and usage of parameters is optional. If you change a standard strategy we recommend you set the value of a delivered standard parameter in Assign Method Parameters to a Strategy. If you define a new parameter, you must implement the usage logic within the using method.

Activities

You set up the process controller in Customizing for SCM Basis under Process Controller.

If you have set up a new strategy, you must define for which process you use the strategy.

SCM BasisProcess Controller P U B L I C 271

9 Configurable Process Scheduling

Purpose

Up to now, different SAP applications have developed their own scheduling function according to related requirements. Configurable process scheduling is a cross-application function, which you can use to schedule several freely definable business processes according to your own rules. You can set up your own date rules in such a way that scheduling adjusts itself to your processes. You can integrate any number of currently existing processes, or model new processes, and convey these to configurable process scheduling. However, note that the particular application must also be capable of processing the dates returned.

Process definition comprises the following areas:

● Definition of process steps (for example, load)● Arrangement of these steps in time per business process● Date types of these steps (load finish, for example)● Time units of the dates (hour, day, for example)● Methodology of master data determination (methodology to determine the duration of loading time, the

working times of loading personnel and the time zone of the loading point, for example)

Process scheduling has an open structure, which compromises application-specific or process-specific Customizing, which you can use to help you define the different implementations for the determination and execution of scheduling subtasks or auxiliary services, at the time of definition.

Features

You can use configurable process scheduling to allocate dates to all known process steps in the process model that are marked as scheduling-relevant. You can specify some of these dates for scheduling (if some of the dates are already known); scheduling determines the remaining dates that have not yet been determined.

Configurable process scheduling comprises the following functions:

● Process Definition [page 273]● Master Data Determination [page 274]● Definition of Time Units [page 275]● Delegation Determination [page 276]

In process definition , you specify actual dates and their relation to another in time. For example, in the outbound delivery process, you would define that the material availability date is before the goods issue date.

In master data determination , you define for a scheduling schema how the desired master data determination for scheduling is to take place.

When defining time units per date, you communicate to scheduling the time unit to which the scheduling result should be rounded. This rounding takes place in the local time zone that was defined for the related activity.

Delegation determination gives you the option of delegating certain tasks within scheduling to other components, which, for example, are capable of managing certain special dates in a more complex way.


Configurable Process Scheduling

Example

Scheduling could notice, for example, that a certain date needs to be postponed due to new circumstances that have arisen. This is communicated to the application, so that a new decision can be met within the application.

For example, a truck might not appear at the loading ramp on the planned date, or, that is, on the date determined by process scheduling, and as such, the goods cannot be posted as a goods issue. The application may now decide that that the goods issue date should take place at a later time, or that the materials should be delivered to another customer. If the goods issue date is to be executed at a later date, you can ensure that process scheduling completely reschedules all new or adjusted dates.

9.1 Process Definition

Use

You can model business processes that you can use as a basis for scheduling within configurable process scheduling. The process definition contains a reference to an existing scheduling schema (see also: Master Data Determination [page 274] ), which contains all activities of the process definition.

In the process definition, you specify the dates and their relationship to another in time. For example, you define that the material availability date is before the goods issue date.

Prerequisites

Make sure that you have already maintained a scheduling schema. You can find further information in the Implementation Guide (IMG) under SCM Basis → Configurable Process Scheduling → Scheduling Schema → Define Schema.

Features

You create one or several steps of the workflow for the process definition (see also: WebFlow Engine ).You can do this either via Simple Process Maintenance or via Maintain Process in Customizing. In simple process maintenance, you maintain the scheduling process model using a simplified SAP workflow editor.

If a step is relevant for scheduling, create a property with the name sap.scm.bas.sch.actitype and assign the property to the key of an activity as a value. This turns the step into an activity of the process model used in scheduling.

Note that you have to define this activity within the schema defined in the basic data. The process definition in the workflow editor that is in the form of a network of steps is converted into a process model within scheduling that only contains the steps (activities) relevant to scheduling.

SCM BasisConfigurable Process Scheduling P U B L I C 273

https://help.sap.com/viewer/a602ff71a47c441bb3000504ec938fea/7.5.16/en-US/4f41e8a0dd89535fe10000000a421937.html

If you include a subworkflow containing steps that are not relevant to scheduling, it may be necessary to explicitly mark up to two steps that are relevant to scheduling as inbound/outbound activities of this subworkflow. You do this by maintaining the inbound/outbound for the activity for the property sap.scm.bas.sch.sactibzw. sap.scm.bas.sch.eacti in the workflow step. These activities are then connected to the inbound and outbound edges that the superordinate step possesses in the superordinate workflow. In simple cases, the system can determine the inbound and outbound activity itself. This is the case for workflows that only consist of a linear sequence of steps. In particular, using complex workflows that also contain steps that are not relevant to scheduling may require the explicit marking of inbound and outbound activities. This particularly applies when the scheduling process model derived from the subworkflow has several activities without an inbound edge (that is, several potential inbound activities).

Applications that make use of process scheduling and that have set up a workflow can impart the workflow ID of the process scheduling interface. Configurable process scheduling then uses the preset parameters for scheduling.

You can add a language-dependent process descriptor for a technical process name. You can show the process descriptor on the user interface, for example, the scheduling log, to display the scheduling process model used.

SAP currently provides the defined process Delivery or Supply Process of Planning , which is defined under the process alias PLANNING .

Activities

1. Maintain a process in Customizing. You can find further information in the Implementation Guide (IMG) under SCM Basis → Configurable Process Scheduling → Process Definition → Simple Process Maintenance.1. a. Maintain the reference to a scheduling schema.2. b. Maintain the reference to a time unit assignment set.3. c. Create one or more workflow steps.

2. Define a process alias in Customizing. You can find further information in the Implementation Guide (IMG) under SCM Basis → Configurable Process Scheduling → Process Definition → Define Process Alias.

9.2 Master Data Determination

Use

A scheduling schema is used within configurable process scheduling to control the behavior of scheduling. For process scheduling to determine the corresponding master data such as calendar (time stream), duration and time zones for the related activities, you first have to maintain the determination methods in Customizing.

Prerequisites

A scheduling schema used activity types, date types, activity type categories and logical classes. Make sure that you have already maintained these elements.



You can find further information in the Implementation Guide (IMG) under SCM Basis → Configurable Process Scheduling → Scheduling Schema → Define Elements of Schema.

Features

You can use master data determination to communicate to process scheduling where the master data for the determination of dates comes from. You have the option of storing a property or a logical class for the determination for a combination of scheduling schema and activity. The program then determines master data according to the access priority that you have set.

Activities

1. Define a schema in Customizing. You can find further information in the Implementation Guide (IMG) under SCM Basis → Configurable Process Scheduling → Scheduling Schema → Define Schema.

2. Maintain the master data for the activities in Customizing. You can find further information in the Implementation Guide (IMG) under SCM Basis → Configurable Process Scheduling → Master Data for Activities.1. a. Assign a calendar2. b. Assign durations and time units to an Activity Type Category and the Activity Type .3. c. Assign time zones to an Activity Type Category and the Activity Type .

9.3 Definition of Time Units

Use

Within configurable process scheduling, you can use time unit assignment sets to assign date types to time units. In this way, the time unit is preset to the results dates of scheduling. A time unit can also be used to define the duration of an activity.

Moreover, you can maintain time unit assignment sets, which consist of a number of date types and the assignment of a time unit to each date type. You can use a time unit assignment set within scheduling, to preset the time unit to the results dates.


Features

According to the time unit of the duration of an activity, the system uses another implementation for basic date calculation. The implementations provided by SAP differ as follows:

● For time units of less than a day , the system calculates the (net) duration of the activity along the time stream of the activity. This time stream allows you to map working time definitions of less than a day (down to the level of seconds).

● For the time unit day , the system calculates the (net) duration along the factory calendar of the activity.● For time units greater than a day , the system does not take working time or a calendar into account.● When assigning date types to time units, you can round the times in the local time unit or the time zone.

If you create and use your own time units, you can influence scheduling in your core functions, particularly if you are also using your own implementations.

Activities

1. Maintain a time unit assignment set. You can find further information in the Implementation Guide (IMG) under SCM Basis → Configurable Process Scheduling → Time Units → Assign Units.

2. Assign the time unit assignment set to a process definition.

9.4 Delegation Determination

Use

You can use delegation determination if you execute scheduling in connection with applications or components, which are capable of determining certain dates, processes, or checks that are more complex than configurable process scheduling.

Prerequisites

Make sure that the necessary activity types for delegation determination in Customizing have already been maintained. You can find further information in the Implementation Guide (IMG) under SCM Basis → Configurable Process Scheduling → Scheduling Schema → Define Elements of Schema.

Features

Delegation determination gives you the option of delegating certain tasks for scheduling to other components or applications. This operation makes particular sense if, for example, the other application is capable of



determining these dates in a more complex way, or according to a special pattern.You can delegate the following tasks to other components:

● Determination of a date (start or finish); for example, validation as to whether dates have a certain validity (timetable, for example)

● Determination of complete subprocesses (of an individual activity also)

You can assign delegation determination to the system statically or set dynamic determination. You define static delegation determination in Customizing, either in the activity, or in the activity in the schema. Furthermore, you must also convey a class for delegation determination that is able to carry out the actual delegation.

In the case of dynamic determination, only convey a class to the system that overrides the static determination in the contained coding, or set the Control of Delegation indicator to dynamic.

NoteIf you maintain delegation determination in the same way as duration determination, note that the system only uses this delegation determination if you have set the control parameter for delegation determination in the activity in such a way that the system uses dynamic determination.

Activities

For the combination of scheduling schema and activity type, maintain a class for delegation determination in Customizing and use the Control of Delegation indicator to communicate to the system what kind of delegation you would like to execute (dynamic or static). You can find further information in the Implementation Guide (IMG) under SCM Basis → Configurable Process Scheduling → Scheduling Schema → Define Schema.


10 Order Document Management (ODM)

Purpose

Order document management (ODM) is a collection of individual functions that can administer documents within logistics. These documents (for example, purchase order, sales order, delivery) are also used within logistics to document individual goods movements.

Within order document management, the structure of a document is split up according to components. You can thus use the components [page 282] for the different documents. In this way, within logistics, you can map the most diverse document types from as few components as possible for order document management.

Implementation Considerations

You have installed the component order document management within SCM Basis and executed all necessary Customizing activities. You can find further information in the Implementation Guide (IMG) under SCM Basis

Order Document Management and under Configuring Order Document Management [page 279] .

Features

Order document management can administer the following document types:

● Documents, which trigger business processes (purchase orders and sales orders, for example)● Documents, which document the transportation of goods (delivery notes, for example)● Documents, which document the end of business processes (goods receipt document, goods issue

document, for example)

Moreover, order document management can administer documents other than the ones listed above, if they meet certain requirements:

● The hierarchy depth of the document may only span three levels (header, item, schedule line, for example)● The structure of the documents can be clearly identified with a document type [page 280] .● The structure of the documents can be split up into components [page 282] .

The structure of order document management enables you to store master data, business partners or locations in order document management, for example.

Order document management supports the following additional functions:

● Any amount of references between the core components of the order documents● Order document management takes care of the hierarchical consistency of the order documents, that is, if

you delete an order header, for example, order document management automatically deletes all items, and so on.


Order Document Management (ODM)

● Methods for the archiving of order documents exist● A history of changes to the document can be carried out

Administration of data on the database is separated from the actual application with the help of order document management. Thus, in a running system, you can swap the tables in which data is stored, without having to adjust the application itself. For example, based on certain criteria, you can distribute the data of the same document type over different table records. In this way, the occupancy of the individual tables is reduced and you thus improve access performance.

10.1 Configuring Order Document Management

Use

You can set up order document management (ODM) using metadata maintenance.

The system uses the metadata to describe the database structure in which the order document data is managed by order document management.

Metadata also determines the structures with which the application can access the order document data. However, the application does not know in which tables the order document data is stored.

Features

To configure order document management, you must set up the following objects:

● Order component [page 282]● Order data type [page 281]● Order data area [page 283]● Order document type [page 280]

In the order component area, you can maintain the following subareas:

● Order components● Parameters for order components● Indices for order components● Display generation data

In the order data type area, you can maintain the following subareas:

● Order data type● Extensions for the order data type● Display generation data

Within the order data area, you can maintain the following subareas:

● Order data area● Tables for the order data area

SCM BasisOrder Document Management (ODM) P U B L I C 279

Within the order document type, you can maintain the following subareas:

● Order document type● Validity of the order data area

In the maintenance dialogs of metadata, you can only change inactive versions. Use the activation options (see also: Activating Order Document Management [page 285] ) to activate inactive versions. Should errors occur during activation, you can first generate order document management (see also: Generating Settings in Order Document Management [page 286] ). You can review the current settings and the generated objects at any time (see also: Check Settings [page 284] ).

Activities

Configure order document management in Customizing. You can find further information in the Implementation Guide (IMG) under SCM Basis Order Document Management Configure Order Document Management.

10.1.1 Order Document Type

Definition

The order document type is a document that is used in a business process and stored, or administered, in order document management.

Use

You must assign an order data type [page 281] to an order document type.

The order document type is used by applications to transfer order documents to order document management (ODM), or to access order documents, whereby the related application determines which order document types are supported.

In addition, you can specify whether ODM sets locks when processing an order document of this kind, and whether the history is updated when changes are made. The aim of the lock is to prevent the same order document (or the same item of an order document) from being processed and changed by two parallel transactions at the same time.

The order data type that is assigned to the order document type describes the structure and the attributes of the order document (that you can store for an order document).



Example

An order document type can be a sales order, a purchase order or a delivery, for example.

10.1.2 Order Data Type

Definition

The order data type describes which data of an order document can be stored in order document management, that is, the order data type describes the actual data structure of an order document type [page 280] . The description consists mainly of the specification of the hierarchy category of the order document, the core components and a list of the extensions, and their assignment to the core components (see also: order component [page 282] )

Use

An order data type can be used by several order document types [page 280] . In this way, you can use the same data type for the customer quotation and the sales order, for example, since you manage the same data for both document types.

Within order document management, an order data type is made up of several order components [page 282] .

The order data type is used to describe the order document type and the order data area. The tables of the order data area are generated from the definition of the order data type. Tables that correspond to the components of the order data type are created in the order data area.

NoteNote that the technical name of the order data type may only contains letters and figures, if you want to use it in table and structure names.

Structure

Currently, only double and triple-level hierarchy categories are supported in order document management (ODM).

● A double-level hierarchy category is made up of header and items.● A triple-level hierarchy category is made up of header, items and schedule lines.

For a double-level logistic order document, you can use the components 1HDR (header) and 2IT2 (item), for example. For a triple-level logistic order document, you can use 1HDR (header), 2IT3 (item) and 4SDL (schedule line), for example.


A 1:N relationship exists between the individual hierarchy levels, that is, more than one item can exist for a header, but only one header can exist for an item. The same applies for the relationship between items and schedule lines.

You must specify the components for header, item, and if necessary, schedule line according to the hierarchy category of the order data type.

● If you want to store external or readable numbers for the order documents, you must enter the related mapping components (double or triple-level).

● If the order data type can reference other order documents (and these references are to be stored in ODM), you must also enter the reference components.

You can use extensions to store further data, which is not contained in the core, for an order document. Extensions group the characteristics or the attributes of an order document according to topic (transportation, for example).You assign extensions in the order document type. The standard extensions of ODM are:

● 7MP2 and 7MP3Used to map double and triple-level document types

● 7REFUsed for references (links between order documents and parts of documents).

● 1PRT and 2PRTUsed to store partners at header and item level.

● 1TST, 2TST, and 4TSTUsed to store dates and time intervals. (This extension is not used in the current version).

10.1.3 Order Component

Definition

Order components are the elements that make up an order data type [page 281] . Components group order data, or the attributes of an order document together under one topic (item, term of delivery, for example).

Use

Order document data is exchanged between the application and order document management (ODM) component for component.

Components must meet certain requirements according to their use and their assigned hierarchy level (header, item, schedule line, and component reference type).

You have to assign an ABAP Dictionary structure to a component. You use the structure to specify which attributes the system stores for the component. The structure serves as the basis for the data exchange between ODM and the application. The structure is used to generate the tables in the order data area type [page 283] , in which the data of the components is stored.



Structure

Each component has a technical and a descriptive name. The technical name is used to identify the component in the order data type and in the application. Order document management distinguishes between core components and extensions.

● Core componentsCore components form the basic framework of an order document. The framework consists of a header, an item and, if necessary, a schedule line.

RecommendationThe following recommendation is relevant for logistic orders, for example, where other orders also use other components:

For a double-level order document, use the components 1HDR (header) and 2IT2 (item). For a triple-level order document, use 1HDR (header), 2IT3 (item) and 4SDL (schedule line).

You can identify core components by setting the ODM: Core Component indicator. You cannot use a core component as an extension. If a corresponding extension is required, you need to create this separately. The extension may however use the same ABAP Dictionary structure as the core component.

● ExtensionsYou can use extensions to store further data, which is not contained in the core, for an order document. Extensions group the characteristics or the attributes of an order document according to topic (transportation, for example).You assign extensions in the order document type.

10.1.4 Order Data Area

Definition

The order data area describes which tables order document data is stored in.

Use

Assign an order data type [page 281] to the order data area. When the order data area is activated, database tables are generated (or, if necessary, adjusted) according the description of the order data type.

Assign an order data area to one or several order document types [page 280] . You can store all order document types that have the same order data structure in one order data area.

For performance reasons, it may be preferable to use different order data areas for each order document type to keep the data quantity in the individual tables to a minimum.

In addition, the assignment of an order document type to an order data area depends on the version of the order document. In this way, you can, for example, store the data of the active versions of the order document types in different order data areas (for performance reasons), and the other versions in an individual order data area.


Example

For example, you can store a customer quotation and a sales order in the same order data area if the customer quotation and the sales order have the same order data structure and the order data area has the same order data type.

10.2 Check Settings

Use

If you would like to check the current active settings and the generated objects, then you can use this check report.

Prerequisites

You have configured at least one active version for order document management. You can find further information in the Implementation Guide (IMG) under SCM Basis Order Document ManagementConfigure Order Document Management.

Features

You can execute a complete check of all settings or select according to the following subareas:

● Order component [page 282]● Order data type [page 281]● Order data area [page 283]

Moreover, you also have the option or explicitly checking an order component, an order data type, or an order data area by explicitly specifying the corresponding name.

You can carry out checks for both active and inactive versions. You can display the output of results as a log or as a list.

Activities

Check the Customizing of order document management. You can find further information in the Implementation Guide (IMG) under SCM Basis Order Document Management Check Settings in Order Document Management .



10.3 Activating Order Document Management

Use

During activation you convert inactive settings into active settings. Order document management (ODM) only uses active settings.

You may need to reactivate order document management after performing an upgrade, after activating a business function, or after implementing a Support Package.

Prerequisites

You have configured at least one inactive version for order document management. You can find further information in the Implementation Guide (IMG) under SCM Basis Order Document ManagementConfigure Order Document Management .

Features

When you activate order document management, you can activate the following individual areas separately:

● Order component [page 282]● Order data area [page 283]● Order data type [page 281]

You can decide for each area, whether, for example, you would like to activate all order components or whether you enter a special component to activate only this, or a certain area of components.

During generation, the system checks the inactive settings and, if necessary, generates ABAP Dictionary objects (structures and tables).

Should errors occur during activation, you can call Generation [page 286]. Once generation has been carried out successfully, you have to call activation again.

Activities

Activate the order components, the order data area and the order data type in Customizing.

When you have to reactivate ODM settings, first execute the Activate Order Document Types and Dependent Objects activity for the order document types that are active in your system. Would you still encounter issues after having executed this activity, execute the Activate Order Component, Activate Order Data Type, and Activate Order Data Area activities.


You can find further information in Customizing for SCM Basis under Order Document ManagementActivate Settings in Order Document Management , and in SAP Note 1896995 .

10.3.1 Generating Settings in Order Document Management

Use

Should errors occur during activation [page 285] , you can call generation. Once generation has been carried out successfully, you need to call activation again.

Prerequisites

You have configured at least one inactive version for order document management. You can find further information in the Implementation Guide (IMG) under SCM Basis Order Document ManagementConfigure Order Document Management.

Features

When you generate order document management, you can generate the following individual areas separately:

● Order component [page 282]● Order data area [page 283]● Order data type [page 281]

You can decide for each area, whether, for example, you would like to generate all order components or whether you enter a special component to generate only this, or a certain area of components.

During generation, the system only takes inactive settings into account. However, this does not affect the ABAP Dictionary objects of the active order components, the active order data area and the active data type. If necessary, the system then generates the corresponding structures and tables.

Activities

Generate the order components, the order data area and the order data type in Customizing. You can find further information in the Implementation Guide (IMG) under SCM Basis Order Document ManagementGenerate Settings in Order Document Management .




10.4 Defining Value Ranges

Use

You have the option of maintaining certain master data and its value range for order document management (ODM). Maintenance is particularly relevant if you want to use uniform cross-application data. Consequently, you can ensure that when data is transferred to order document management, the same names are used as in the calling application.

Prerequisites

You have configured at least one active version for order document management. You can find further information in the Implementation Guide (IMG) under SCM Basis Order Document ManagementConfigure Order Document Management and Activate Settings in Order Document Management.

Features

You can maintain the following master data:

● Item categoryThe item category distinguishes between the handling and the function of an item in the order document. Item categories are specified by applications and interpreted by these.The item category describes the type or use of the item.

● Schedule line categoryYou can use schedule line categories to distinguish between schedule lines or their quantity specifications (requested or confirmed quantity, for example). Schedule line categories are specified by applications and interpreted by these.The schedule line category describes the quality of the type of quantity specification in a schedule line. A schedule line type is only needed in the case of a triple-level hierarchy category (see also: Order component [page 282] ). Possible schedule line categories are, for example, 'request' and 'confirmation'.

● Date typeYou can use a date type to further specify date specifications (for example, goods issue date or loading date).The date type specifies the date or the date interval in the business process in business terms (see also: Master data determination [page 274] in configurable process scheduling). Date types are needed for the selection of order documents via dates: You define, in the order data type [page 281] , where the dates are to be stored depending on their date type.

● Partner roleYou can use the partner role to further specify partner specifications (for example, ship-to-party vendor). Partner roles are specified by applications and interpreted by these.

None of the master data has a direct influence on the behavior of order document management.


Activities

Define the value ranges in Customizing. You can find further information in the Implementation Guide (IMG) under SCM Basis Order Document Management Define Value Range.



11 Time Series Data Management

Purpose

This component is a data management module in SAP Supply Chain Management (SAP SCM) that you can use to create and to call time series data within the logistics. The time series are saved as numerical key figure values in sequential time periods (buckets).

You can use time series data management (TSDM) to configure data storage, group the time series in clusters, and use multiple time series data areas.

By grouping time series in clusters, you reduce the number of table entries that the system can access by a factor proportional to the cluster size. At the same time, the number of key figure values read is proportional to the cluster size. If the grouping in clusters is done well, this results in smaller tables and improved performance.

NoteTo set a suitable cluster size, you bring the cluster size into agreement with a typical read access or a typical write access. In doing so you must always balance between access to too many table entries and reading too large a data volume.

Introductory Notes

SAP delivers TSDM Customizing for the following business scenarios so that you do not have to make any changes in most cases:

● Forecasting & Replenishment (F&R)● Responsive Replenishment (RR)● Supplier-Managed Inventory (SMI)● Supply Network Inventory ( SNI )● Service Parts Planning (SPP)

For more information, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management and under Configuring Time Series Data Management [page 290] .

Integration

TSDM is incorporated in the following applications:

● SAP Forecasting and Replenishment (SAP F&R): SAP Library SAP Supply Chain Management (SAP SCM) SAP Forecasting and Replenishment (SAP F&R)

SCM BasisTime Series Data Management P U B L I C 289

● Service Parts Planning (SPP) :SAP Library SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and Optimization (SAP APO) Service Parts Planning (SPP)

● SAP Supply Network Collaboration (SAP SNC): SAP Library SAP Supply Chain Management (SAP SCM) SAP Supply Network Collaboration (SAP SNC)

● Demand Planning: SAP Library SAP Supply Chain Management (SAP SCM) SAP Advanced Planning and Optimization (SAP APO) Demand Planning

Large amounts of time series data must be managed within these applications. For this, SAP delivers default settings for TSDM. For SAP F&R, you create new time series data areas for the transaction data of each location used and you activate them.

Features

You can use the following functions:

● Configure time profile● Configure time series data type● Configure time series data area● Configure time series type

NoteYou make your settings for TSDM in Customizing. TSDM then runs automatically in the background.

See also:

Configuring Time Series Data Management [page 290]

Activating Time Series Data Management [page 292]

11.1 Configuring Time Series Data Management

Use

You use this function to set the metadata for time series data management (TSDM) and to configure at least one inactive version for the metadata objects Time Profile, Time Series Data Type , and Time Series Data Area .

Features

You use the following metadata objects to configure TSDM:

● Time Series Type


Time Series Data Management

You use the time series type to model a group of time series to a single business object used by external applications. You do this to define specific classes of time series data that you want to access. You use the time series type to determine the time series data type that gives time series data their structure. The time series type is the external name of a quantity of time series data of the same structure that an application uses when calling TSDM.You can also connect the time series data type to a planning object structure.

● Time Series Data TypeYou use the time series data type to model the technical properties and the structure of a set of time series, and to determine characteristics, key figures, and a time profile.

● Time Series Data AreaYou use the time series data area to determine a table set that is used for saving the time series of an individual time series data type.You can use multiple time series data areas to divide large quantities of data into different table sets. You define the division of data on various time series data areas using the Time Series Data Areas for Time Series Type function. For more information about this, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Configure Time Series Data Management . Time series data areas are not visible in the application.

At least one time series data area must exist for a time series data type to use it actively in the application. For more information, see Activating Time Series Data Management [page 292] .

● Time ProfileYou use the time profile to define the consolidation period type and the end of a period sequence, as well as the settings for grouping in clusters (cluster type and cluster multiplier).

● ParametersYou use the parameters to define the name and technical properties of a key figure or a characteristic of TSDM. The parameters are also used in other SCM data management and form a part of the description of corresponding algorithms and user interfaces.

Activities

You configure the metadata for TSDM in Customizing by choosing SCM Basis Time Series Data Management Configure Time Series Data Management .

To be able to use the metadata objects time profile, time series data type , and time series data area, you must activate them .

See also:

Time Series Data Management [page 289]

Activating Time Series Data Management [page 292]


11.2 Activating Time Series Data Management

Use

You can use this function to convert the metadata in time series data management (TSDM) from the inactive version into an active version.

Each of the metadata objects Time Profile, Time Series Data Type and Time Series Data Area exist in an inactive version that describes their definition and in an active version that reflects the current used status of the definition. You can only use the metadata if it exists in an active version.

Prerequisites

You have configured at least one inactive version of the metadata objects Time Profile, Time Series Data Type, and Time Series Data Area for TSDM . For more information, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Configure Time Series Data Management .

Features

You can activate each of the following metadata objects separately:

1. Time ProfileDuring activation of the time profile, the system generates the corresponding time periods and time clusters in the database tables /SCA/TIMEPERIOD and /SCA/TIMECLUSTER. It then copies the table entry relevant for the time profile from the inactive version (definition) into the active version (runtime usage).

2. Time Series Data TypeDuring activation of the time series data type, the system copies the relevant table entries from the inactive version (definition) into the active version (runtime usage).If you have assigned the time series data type to a planning object structure, the planning object structure will be created and activated as well.

3. Time Series Data AreaDuring activation of the time series data area, the system generates the relevant ABAP Dictionary objects (tables) from the inactive version (definition) into the active version (runtime usage).

You must activate new objects in the sequence above because a time series data area is dependent on the time series data type and the time series data type is dependent on the time profile.



Activities

Activate the metadata objects Time Profile, Time Series Data Type, and Time Series Data Area in Customizing by choosing SCM Basis Time Series Data Management Activate Time Profile, Activate Time Series Data Type, or Activate Time Series Data Area.

See also:

Time Series Data Management [page 289]

Configuring Time Series Data Management [page 290]

11.3 Activate Time Profile (Report)

Use

You can use the /SCA/TSDM_TIMEPROFILE_ACTIVATE report to activate an existing time profile to be able to use it in time series data management (TSDM).

For more information about this report, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Activate Time Profile .

11.4 Delete Time Profile (Report)

Use

You use the /SCA/TSDM_TIMEPROFILE_DELETE report to delete the active version, periods, or cluster for a time profile.

For more information about this report, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Delete Time Profile .

11.5 Activate Time Series Data Type (Report)

Use

You can use the /SCA/TSDM_TSDTYPE_ACTIVATE report to activate an existing time series data type to be able to use it in time series data management (TSDM).

For more information about this report, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Activate Time Series Data Type.


11.6 Delete Time Series Data Type (Report)

Use

You can use the /SCA/TSDM_TSDTYPE_DELETE report to delete the active version or dependent objects of a time series data type.

For more information about this report, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Delete Time Series Data Type.

11.7 Activate Time Series Data Area (Report)

Use

You can use the /SCA/TSDM_TSDAREA_ACTIVATE report to activate an existing time series data area so that time series data management (TSDM) assigns table names and creates corresponding tables.

For more information about this report, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Activate Time Series Data Area.

11.8 Delete Time Series Data Area (Report)

Use

You can use the /SCA/TSDM_TSDAREA_DELETE report to delete the active version of the time series data area.

For more information about this report, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Delete Time Series Data Area.

11.9 Copy Time Series Data Areas (Report)

Use

You can use the /SCA/TSDM_TSDAREA_COPY report to copy a time series data area to another time series data area.

For more information about this report, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Copy Time Series Data Areas.



11.10 Delete Time Series Data (Report)

Use

You can use the /SCA/TSDM_TS_DELETE report to delete the exact time series data that you enter on the screen.

For more information about this report, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Delete Time Series Data.

11.11 Delete Time Series Change History (Report)

Use

You can use the /SCA/TSDM_TS_HIST_DELETE report to delete the change history data for a certain period in the past that you no longer need.

For more information about this report, see the Implementation Guide (IMG) under SCM Basis Time Series Data Management Delete Change History Data.

11.12 Reporting for Time Series Data Management

You can extract time series data management (TSDM) data into the SAP Business Warehouse to enable an analysis of the data for reporting purposes.

You can extract the data using the Extractor for TSDM Data ( 0SCM_TSDM_GEN_1), which is a general extractor. To ensure that the required data is extracted, you can specify and extend the range of the data handled by the extractor in Customizing for SCM Basis under Time Series Data Management Reporting for TSDM .


12 Cross-System and Cross-Partner Document Flow

Purpose

The subdivision of different sections of a complete business process demands the coordination of different partners and subprocesses across companies and systems. In doing so, you attain efficient results by meeting customer needs.

To determine the degree of processing of the process, and to measure the fulfillment of contractual conditions between the partners involved, you must monitor and document the actual procedure of a concrete business process. Moreover, with regard to the business documents, the flow of the business process becomes clear. You must also be able to still determine the process flow afterwards. This is valid independently of the direction of the process flow, that is for procurement and production as well as for the fulfillment of sales orders.

The leading partner that receives the sales order must be able to easily gain information about the degree of processing of the sales order and about the partners involved, and their tasks. In this way, you can forward the individual requirements for transportation, production and shipment to both internal and external partners. At the same time, a relationship must be created between the documents and business documents that the system creates during the process so that you can clearly document the process flow.

Cross-system and cross-partner document flow is the application to manage the document flow.

A document flow collects the tasks, responsibilities, and progress of a business transaction using business documents. The objects in the flow are existing documents and the overall status of these. You can use the document flow to document contractual agreements and the fulfillment of these in a concrete business transaction. Once the business transaction is completed, the document flow is definitely finished.

Features

Document flow provides transparency for processes that have several partners in different systems and enables a simple overview of the complete business process. Document flow maps the relationship and course of the complete process, irrespective of the actual execution of the section in the business process.

In the case of central management, several applications, which can also be implemented in different systems, use the document flow. The cross-system and cross-partner flow concentrates all the business transaction information that is relevant for the overall process in one place.

In the case of cross-system and cross-partner document flow, you can enter documents whose data is managed by other systems (that differ to the document flow system).

In any case, you can make minimal data, that is, some of the document data, redundant in cross-system and cross-partner document flow.

Document flow contains the following functions:

● Determining Process and Document Statuses [page 297]


Cross-System and Cross-Partner Document Flow

● Display [page 299]● Data Transfer and Archiving [page 300]

12.1 Determining Process and Document Statuses

Use

When displaying a network of cross-system and cross-partner document flow, you can display the complete status from the point of view of the process tasks. Business process management controls the processes and the individual process tasks. The status of the complete process flow and the degree of processing of the tasks linked to this are known to business process management and managed there. The view of the process is thus task-oriented and does not have to be congruent with the expected events of Supply Chain Event Management (SCEM) .

Prerequisites

You can only check the status of the document flow if you have modeled the document flow in such a way that the status exists as an attribute for the respective document.

Define the document types and assign a structure to each document type. Then use the Object Relationship Service to define role categories and assign the desired document types to the role categories.

For more information, see the Implementation Guide (IMG) Integration with SAP Components Cross-System and Cross-Partner Document Flow.

Features

In the business process, different documents that document the process flow up until now exist. Cross-system and cross-partner document flow relates the documents that have actually arisen in the different applications involved. Document flow creates and manages the network of documents from the applications and provides methods that enable them to be displayed. A network of documents is made up of the objects themselves and their links. The system keeps the objects redundantly to the actual documents of the original systems or applications in the document flow.

For the network of documents to be displayed and documented consistently (for all applications), cross-system and cross-partner document flow merges this information centrally.

Document flow is purely a passive tool that merges the documents that it receives from the applications into a network. Document flow does not actively report to an application.

The documents that document flow combines to form a network can have a status. Cross-system and cross-partner document flow takes this status and displays it, but does not manage it. When the object status of the

SCM BasisCross-System and Cross-Partner Document Flow P U B L I C 297

documents is displayed, it is a case of a static snapshot. The application is responsible for transmitting the current status to cross-system and cross-partner document flow.

Activities

Make the following settings in Customizing:

1. Define document categories.2. Define role categories.3. Assign the document category to the role category.4. Define link categories.5. Define the link category between two role categories.6. If you want to specify data for the related link when updating the document flow, assign activities to the

related link categories.

For more information, see the IMG under Integration with SAP Components Cross-System and Cross-Partner Document Flow Maintain Object Link Model and Define Document Categories for Document Flow .

12.2 Distribution Across Several Systems

Use

A distributed system landscape is characterized by several components (business application components, BAC) that are installed on one or several systems with separate databases and that are combined in a group. The group is formed to process business processes in a cross-component way.

Cross-system and cross-partner document flow is updated in the individual systems from the point of view of the respective components. There must be at least one central system in this group in which you can consolidate and centrally view the separately updated document flows.

Features

Document flow updates links between documents. You can store attributes for the links and the objects (documents). The Object Relationship Service (ORS) describes the possible links (relationships) and their attributes.

Cross-system and cross-partner document flow is not a 'central document flow'. A central system exists, which, ideally, should contain the union of the local document flows of individual BACs. This central system merely contains the replica of the local document flow fragments.

The mechanism described enables locally updated document flows to be replicated in a central system. Nevertheless, this transfer is independent of the use of document flow in the individual systems.



If the logical system and the system name of the sending system are the same, then the sending system is the master for the document.

A system that is not the master of a document or of a link can only update attributes if the master or another system has not already sent this data.

NoteNote that the attributes for objects and links are the same in all the systems.

12.3 Displaying Document Flow

Use

You can use several parameters in the entry screen for the display to determine the document flows to be displayed.You can display one or several document flows. You can either display only the direct predecessors and successors, or the complete network of the flow.

Features

You can display the flow of a document (with its predecessors and successors) within the individual document display of a document. From the flow, you can display the other documents of the network.

The system displays the data that exists in cross-system and cross-partner document flow for a document.

Activities

In cross-system and cross-partner document flow, provision is made for the application itself to develop the dialog for the display of the document flow. The following classes and methods are important to access the data of the document flow:

In the package : /SCMB/FLOW_CUSTOMIZING

Class Method Description

/SCMB/CL_DF_DOCUMENT_TYPE GET Delivers document types

GET_DETAIL Delivers the characteristics of a document type

/SCMB/CL_DF_MAXIMAL_CHAIN GET Delivers maximum chains



/SCMB/CL_DF_RELATION_TYPE GET_ATTRIBUTE Delivers the description of additional data

GET Delivers the description of the link

GET_NET Delivers the links of a document type

GET_ROLE Delivers the role of a document type

In the package : /SCMB/FLOW_NET


/SCMB/CL_DF_DOCFLOW READ_LINK Queries the direct links

CREATE_LINK Creates links

READ_NETWORK Queries a network

DELETE_LINK Deletes links

SEARCH_LINK Evaluates document data; delivers direct links

SEARCH_NETWORK Evaluates document data; delivers networks

12.4 Data Transfer and Archiving

Data Transfer

To enable data transfer after an upgrade, the individual applications must implement a relevant interface. Cross-system and cross-partner document flow determines the interface.

You can set the system in such a way that one or several networks are transferred when the data is transferred. Cross-system and cross-partner document flow requests this data.

You can transfer old document flows and networks to cross-system and cross-partner document flow. This can be done selectively or inclusively. Objects that you can transfer are the SAP R/3 SD document flow, the SAP R/3 MM purchase order history, or the SAP CRM document flow.

The applications provide transfer tools to do this.



Archiving

The respective application itself must implement archiving of the document flow. You can use the functions of the Object Relationship Service (ORS). In doing so, you make sure that, when archiving an object, the system completely archives the object.


13 Planning Service Manager

Purpose

The Planning Service Manager (PSM) is a tool that you use to execute automated planning tasks. You can group various planning tasks, such as forecast, replenishment planning, or Transport Load Builder (TLB), in a planning profile . When you execute a planning profile, all planning tasks within it are executed, and the results are saved.

The PSM carries out planning tasks using planning services . The forecast service, the replenishment service, and the TLB service are all examples of planning services. Using data managers, the planning services access master data, transaction data (such as orders, time series, or stock), alerts, and all other kinds of data. The storage service [page 306] saves new and changed data to the database and clears the data manager buffers.

The PSM and the planning services write an application log. You can call this up from the SAP Easy Access screen under SCM Basis Planning Service Manager Analyze Application Log

The Package Creation and Parallel Processing functions enable the PSM carry out performant processing of data quantities.

Integration

The PSM uses other functions from SCM Basis and from SAP Supply Network Collaboration (SAP SNC) . You must carry out one or more of the following points in the Customizing, depending on the different applications you want to use the Planning Service Manager in.

● Order Document Management (ODM):SCM Basis Order Document Management

● Time Series Data Management (TSDM):SCM Basis Basic Settings Time Series Data Management

● Logistics Inventory Management System (LIME):SCM Basis Logistics Inventory Management System (LIME)

● Transaction Data Layer (TDL):SCM Basis Data Management Layer Transaction Data Layer (TDL)

● Trigger (for planning file entry):SCM Basis Data Management Layer Trigger (for Planning File Entry)

The PSM is an SCM Basis tool that can be used by various applications. Planning services and service profiles for the PSM are prepared by the respective applications. It is possible for every planning service to have a service profilewhere you can set parameters such as model, planning horizon, or time series, that you want the system to take into account during the planning run. The parameter type and the number of parameters can differ a great deal, depending on the service.


Planning Service Manager

Features

Data and Objects in PSM

The following graphic is an example of which data and objects the PSM accesses and how it uses these in the planning profile.

The system calls up the PSM with a planning profile. In the planning profile, you define which planning steps are executed in which process blocks . The PSM calls up the planning services (such as the forecast service, the replenishment service, and the storage service) in sequence, as defined in the planning profile. The storage service [page 306] calls up the data managers that are responsible for reading and buffering time series, orders, and master data for example. In the selection, you define which planning objects you want the system to consider when executing the various planning services.

Structure of the Planning Profile and Process Blocks

SCM BasisPlanning Service Manager P U B L I C 303

The following graphic shows the structure of the planning profile:

A planning profile consists of header data and one or more process blocks. The header data contains administrative information for the planning profile, such as who created or changed the planning profile, and when. The process blocks follow the header data. A selection, a planning version, a process profile, and an optional trigger group are defined in every process block. These setting apply for all planning services that are executed in the attached service list.

Every planning service can have a service profile that is prepared by the respective application. At the end of the service list, the system automatically calls up the storage service with the &SAVE+INIT profile, without executing it in the service list.

The PSM creates packages of planning objects for every process block from the selection and planning version defined. The PSM creates packages using the package creation method defined in the process profile. If a trigger group has been defined, only planning objects for which at least one trigger of the trigger group is set are considered during package creation. The packages can be processed in sequence or in parallel. Parallel processing helps improve performance. Instead of processing packages in sequence, packages can be processed in parallel, which can save time. The PSM executes the planning services from the service list separately for each package .

Examples of package creation methods are: Location Product (by Product), Transportation Lane (Simple Method), and No Package Creation.

Planning Services



In the Responsive Replenishment replenishment scenario, you can plan the following planning services in a planning profile for example:

● Order Forecast Service● Deletion Service (only for TLB shipments and replenishment orders)● Replenishment Service● ProAct Check Service● Forecasting Service● TLB Service

The storage service [page 306] is available for all applications and scenarios.

The planning services are assigned to specify package creation methods.

For more information on setting options in the PSM , see Customizing for SCM Basis under Planning Service Manager.

Restrictions

You can only use the PSM if the application concerned provides the necessary planning services, data managers, and storage profiles as standard.

Parallel processing is not available for all planning services, and is dependent on the assigned package creation method.

13.1 Preparation of the Planning Run

Purpose

The central object in the Planning Service Manager is the planning profile. You use the planning profile to set up a planning run. You carry out a series of Stepps to set up the planning profile. The sequence of steps you must carry out are detailed below.

Prerequisites

The prerequisites for using the Planning Service Managers are detailed under Planning Service Manager [page 302] .


Process

The preparation of the planning run takes place in several steps:

1. Define Selection IMG activity in the SCM Basis Implementation Guide (IMG) under Planning Service Manager .

2. Optional Define Trigger Groups and Attributes IMG activity in the Implementation Guide (IMG) for SCM Basis , under Data Management Layer Triggers (for Planning File Entry) .

3. Define Process Profile IMG activity in the SCM Basis Implementation Guide (IMG) under Planning Service Manager .

4. Optional Define Storage Service Profile IMG activity in the SCM Basis Implementation Guide (IMG) under Planning Service Manager .

5. Define Planning Profile IMG activity in the SCM Basis Implementation Guide (IMG) under Planning Service Manager .

6. Execution of the planning profile. To do this, select SCM Basis Planning Service Manager Run Planning Service Manager from the SAP Easy Access screen.

NoteAlternatively, you can make the settings from the IMG only in the current settings, or change them there. To do this, select SCM Basis Planning Service Manager Current Settings from theSAP Easy Access screen, and then select the activity you require.

13.2 Storage Service

Use

You can use the storage service to save new or modified data to the database, or discard data that is buffered in the data managers.

Integration

The storage service works in conjunction with one or more data managers so that it can access data. The Planning Service Manager contains data managers for master data and transaction data, for example. The following lists contain examples of data managers.

Data Managers for Master Data

● Location● Location Product● Product● Transportation Lane



Data Managers for Transaction Data

● Vendor-Generated ICH Order● Replenishment Order● TLB Order● Stock Transfer Order● Time Series Data Management

Other Data Managers

● Alerts● Stock● Unit Conversion● Product Allocation (only in the Responsive Replenishment scenario)

Features

There are two indicators in the storage service:

● Save Data● Clear Buffer

Both indicators have different effects, depending on whether they are set in the General Storage Service Settings or in the Data Manager-Dependent Storage.

General Storage Service Settings

If you set the Save Data indicator in the General Storage Service Settings , the new and modified data is saved in all data managers and written to the database. If you set the Clear Buffer indicator, all data manager buffers are cleared, that is, all data in the buffer is deleted. If you set both indicators, the system saves first and then clears the buffers.

Data Manager-Dependent Storage

In Data Manager-Dependent Storage , you can set the Save Data and Clear Buffer indicators for individual data managers, so that you can deal with them separately. There may be other data managers in addition to those listed. The system processes the list of data managers by row, according to the sequence number. Here again, the system saves first and then clears the buffers.

Standard Storage Service Profiles

The storage service can have several storage service profiles. The following standard profiles exist:

Profiles Function

&INIT Clears all data manager buffers (deletes all data in the

buffer). New and modified data are not saved to the database.

&SAVE_ALL Saves all new and modified data to the database.


&SAVE+INIT First saves all new and modified data to the database and then clears all data manager buffers.

The standard profiles are sufficient in the General Storage Service Settings because they cover all combinations of the two indicators. If you want to make separate settings for individual data managers in the Data Manager-Dependent Storage , you must define new storage service profiles.

The system automatically calls up the storage service at the end of a process blockin the planning profilewith the &SAVE+INIT profile, even if it does not appear on the service list.

Performance

To improve performance, you can also call up the storage service between two planning services

Simulation

If you want to perform a simulation, you can use the &INIT profile.

Activities

You can also create your own storage service profiles. You can find further information on this in the SCM Basis Implementation Guide (IMG) under Planning Service Manager Define Storage Service Profile.

13.3 Define Selections

Use

You use this procedure to define the selections for the Planning Service Manager. You can define selections for the following planning objects:

● Location Product● Product● Location● Transportation Lane

You need the selections in the planning profile so that the Planning Service Manager knows which selections you want it to consider in the planning runs.

To organize your work, you can assign the selections to specific ICH planners. However, this is only possible in the Responsive Replenishment scenario.



Procedure

To define a selection, proceed as follows:

1. Select SCM Basis Planning Service Manager Define Selections from theSAP Easy Access screen.2. In the Selection Type area , choose whether you want to define a selection for a location product, a product,

a location, or a transportation lane.In the Responsive Replenishment scenario, you can only use the Location Product and Transportation Lane selection types.

3. Enter a new description for the selection in the Selection area.4. Enter at least one value as a selection:

○ If you want to define a selection for a location, a product, or a location product, enter the necessary data in the fields for the Location / Product / Location Product area.

○ If you want to define a selection for a transportation lane, enter the necessary data for the means of transport, start location, destination location, and product in the Transporation Lane area.

5. You can also select one or more ICH planners (in the Responsive Replenishment scenario) in the Additional Selection Parameters area .

6. Save the selection.7. You can then assign the selection to a planning profile. To assign the selection to a planning profile, select

SCM Basis Planning Service Manager Current Settings Define Planning Profile from the SAP Easy Access screen.

You can define the planning profile in the Implementation Guide or in the current settings. You must define selections in the current settings because selections do not have a transport link. For more information, see the documentation for the Define Planning Profile IMG activity.


14 Triggers

Definition

Indicator for a planning file entry. A trigger for a planning file entry is a combination of trigger name, service, and selection type.

Use

You can assign triggers to individual services. The system then sets these triggers for planning objects as a result of certain events. However, you must activate the triggers for the services that are to be triggered by triggers. For more information, see Activating and Deactivating Triggers [page 311] . When executing the services, the system only considers those planning objects for which you or the system set triggers, thus reducing the amount of data to be processed.

Trigger groups

If you want to use trigger groups for the execution of certain services in the Planning Service Manager (PSM), the triggers that you assigned to the services must be included in the corresponding trigger group. You can store trigger groups in the PSM planning profile. For more information, see Trigger Group Creation [page 311] .

Mass Deletion of Triggers

For the mass deletion of triggers you can delete a trigger for all products or for all locations products (according to the selection criteria you chose for this trigger). You can do this on the SAP Easy Access screen under SCM Basis Data Management Layer Mass Deletion of Triggers . You specify a combination of planning version, service, and trigger name, and then choose either the product, the location, or the location product as the criteria for deleting the trigger.

Structure

Triggers consist of the following components:

Trigger Name

The name of the trigger describes the event in which the system sets this trigger. Possible trigger names are, for example, Demand at Non-Stock Location, Manual Trigger, or Replenishment Indicator Changed .

You assign trigger names to triggers in Customizing for SCM Basis by choosing Data Management LayerTrigger for Planning File Entry Configure Trigger Define Trigger Assignment of Services and Attributes to Trigger .

Service


Triggers

The service that you assign to a trigger determines the service for which the trigger is valid, for example, for a planning servicein the Planning Service Manager [page 302] .

You also assign services to a trigger in Customizing for SCM Basis under Assignment of Services and Attributes to Triggers .

Type of Selection

The selection type that you assign to a trigger defines the planning objects, for example the product, location, or location product, for which the system can set a trigger. The system also uses these selection types in the Planning Service Manager (PSM).

You also assign selection types to a trigger in Customizing for SCM Basis under Assignment of Services and Attributes to Triggers .

14.1 Activating and Deactivating Triggers

Use

You must activate triggers [page 310] so that they trigger the execution of certain services. You set global activation of triggers for certain services in Customizing. You can also activate or deactivate triggers for individual combinations of trigger name, service, and selection type.

Features

In Customizing for SCM Basis under Data Management Layer Triggers (for Planning File Entry) Activate Triggers you can activate or deactivate triggers for certain planning services or for the planning services of a planning area.

If you want to activate triggers for specific assignments of services and selection types to triggers, you can also do this in Customizing for SCM Basis under Data Management Layer Triggers (for Planning File Entry)Configure Triggers Define Triggers Assignment of Services and Attributes to Trigger . If you have set the Trigger Active indicator for a certain assignment in this IMG activity, this activation is also visible in the Define Trigger Groups and Attributes IMG activity under Trigger Attributes .

14.2 Trigger Group Creation

Use

You can organize triggers [page 310] into trigger groups to execute planning objects in certain services. The use of trigger groups ensures that the system only processes the planning objects for which a trigger is set and which the system must currently process.

SCM BasisTriggers P U B L I C 311

The system uses trigger groups during planning with the Planning Service Manager (PSM). You can define trigger groups in the PSM in the planning profile process block. To do so, you enter the requested trigger group in Customizing for SCM Basis under Planning Service Manager Define Planning Profile Planning Profile: Process Block in the Trigger Group field.

If you use trigger groups, the system executes planning objects as a result of certain events and reduces the volume of data to be processed.

You have several ways to create trigger groups on the SAP Easy Access screen under SCM Basis Data Management Layer Define Trigger Groups and Attributes:

● You can assign a trigger name to a trigger group.● You can assign services to a trigger group.● You can assign selection types to a trigger group.

You can also use more than one of these options to create a trigger group. However, these options are AND operations. This means that the system calculates all triggers (all combinations of trigger name, service, and selection type) that correspond to the assignment of trigger names, services and selection types. The more criteria that you assign to a trigger group, the less triggers it will contain.

As well as this AND operation, you can also include or exclude individual triggers in a trigger group. However, the inclusion or exclusion of triggers in a trigger group only happens after the system applies the AND operation logic for the combinations check trigger name, service, and selection type. This means that triggers that you include or exclude are not affected by this logic.

You can see all triggers that belong to a certain trigger group on the SAP Easy Access menu under SCM BasisData Management Layer Display Triggers of a Trigger Group .


Triggers

15 Transport Load Builder

Use

You can use the Transport Load Builder (TLB) to group transport loads for certain means of transport whilst ensuring that the capacity of the means of transport is utilized as much as possible. The main aims of TLB planning are:

● Building of transport loads that are within the parameter limits defined by the user (such as weight and volume)

● Straight loading or load balancing of means of transport

You can implement the TLB profile in SAP Supply Network Collaboration (SAP SNC) or in Supply Network Planning (SNP). In SAP SNC, additional functions are available. These are features that are not available in the SNP TLB. For more information, see the documentation for SAP SNC under Replenishment Transport Load Builder Additional TLB Functions in SAP SNC .

The TLB groups deployment stock transfers (SNP) or planned replenishment orders (SAP SNC) that were generated for individual products in the previous planning runs, into TLB shipments for several products.

Prerequisites

● You have set up the master data for the TLB. For more information, see Master Data Setup for the Transport Load Builder [page 316].

● You have defined upper and lower limits for the TLB parameters in a TLB profile, and have assigned this profile to the means of transport in the transportation lane. To create the TLB profile, proceed as follows:

○ SAP SNC: On the SAP Easy Access screen, choose SCM Basis Transport Load Builder Define Transport Load Builder (TLB) Profiles .

○ SNP: On the SAP Easy Access screen, choose Advanced Planning and Optimization Supply Network Planning Environment Current Settings Profiles Define Transport Load Builder (TLB) Profiles .

For more information, see TLB Profile [page 320].● You have defined a profile for the TLB basic settings in Customizing for SAP SNC or SNP. If you do not

define a profile, the TLB uses the default settings. To create the profile, proceed as follows:

○ SAP SNC: In Customizing for SAP SNC, choose Replenishment Transport Load Builder Make TLB Basic Settings .

○ SNP: In the SNP Customizing, choose Basic Settings Make TLB Basic Settings .For more information, see Customizing.

● If you are using SNP, you can make settings for the layout of interactive TLB planning in SNP in the SNP Customizing under Basic Settings Change Display of Parameters in Interactive TLB . For more information, see Customizing.

SCM BasisTransport Load Builder P U B L I C 313

● You can set the TLB: Pallet Loading parameter to Product Mix in Customizing for SNP under Maintain Global SNP Settings (if you want the TLB to be able to load a pallet with several different products). If you do not make this setting, the SNP TLB is permitted to load pallets with products of the same type only.

If you are using SAP SNC, you must make additional settings for the TLB. For more information, see the documentation for SAP SNC under Replenishment Transport Load Builder Additional TLB Functions in SAP SNC .

Features

Building of Transport Loads

The TLB first groups deployment stock transfers or planned replenishment orders from the current period into TLB shipments. In doing so, the TLB tries to load the shipments as far as possible to the upper parameter limits that you defined in the TLB profile for that means of transport.

The TLB also considers the loading method that you defined for the means of transport in the transportation lane. As far as possible, the TLB loads the transport loads with the same products, or products from the same loading group (straight loading), distributes the products evenly amongst all transport loads built (load balancing), or distributes the products so that the load reaches an ideal weight/volume ratio ( product-wise loading - product mix heavy/light). Do note, however, that the TLB does not use optimization methods and can, therefore, not guarantee the optimal solution. The TLB considers the individual loading methods as follows:

● Straight loading: The TLB sorts the loading groups and then the products within the loading group alphabetically. In the second step, the TLB distributes the loading groups and products into shipments, in the sequence in which they were sorted.If a loading group can only be partially loaded onto a shipment, the TLB loads the rest of the loading group onto the next shipment. In this way, it is possible for a loading group to be too large or too small for a shipment.

● Load balancing: The TLB tries to distribute products to shipments in such a way that the product percentages are, as far as possible, the same for every shipment.To do this, each time, the TLB adds a rounding value of that product to a shipment. This is the smallest ratio of the quantity already loaded and the total demand of the product. If the ratios of all products are the same, the TLB adds a rounding value of a product selected at random to the shipment.

● Product-wise loading - product mix heavy/light: The TLB tries to distribute products to shipments in such a way that load reaches an ideal weight/volume ratio, which makes the best use of the capacity of a means of transport.To do this, the TLB uses either a static or a dynamic weight/volume ratio. For more information, see Weight/Volume Mix [page 321].

Once all TLB shipments lie within the valid parameter limits, the TLB ends the planning run.

You can also make detailed settings for transport load building by creating your own profile for the TLB basic settings in Customizing for SAP SNC or SNP (see the Prerequisites section above).

Procedure for Remaining Quantities

The TLB may not be able to load one of the TLB shipments to the defined lower limits with deployment stock transfers or planned replenishment orders from the current period. For more information about how the TLB proceeds in this situation, see TLB Procedures for Remaining Quantities [page 322].


Transport Load Builder

Running the TLB and Checking the Results

You can also start the TLB as a background job or run it directly from interactive TLB planning. In interactive TLB planning, you can display the results after the TLB run and then change the shipments manually. You receive a list of generated TLB shipments and possibly also deployment stock transfers that have not been processed. You can then remove or add deployment stock transfers from or to the TLB shipments.

You can also display the results of the TLB run in the application log that is generated during the run.

Activities

The following table details the activities that you have to carry out in SNP or SAP SNC to run the TLB and check the results:

Activity SNP SAP SNC

Running the TLB as a Background Job On the SAP Easy Access screen, choose

Advanced Planning and Optimization

Supply Network Planning Planning

Supply Network Planning in the

Background Transport Load Builder

(TLB) . The SNP Transport Load Builder screen appears where you can make settings for the background run and for the TLB run.

You can also plan the TLB run as a background job using the Process Chain in SCM function.

You execute the TLB as a background job using the Planning Service Manager [page 302].

Running the TLB from Interactive TLB Planning and Checking the Results

Choose Advanced Planning and

Optimization Supply Network

Planning Planning Transport Load

Builder (TLB) .

Then make a selection. To make settings for the TLB run, choose TLB Parameters. In this dialog box, you can also temporarily change TLB profile settings and transportation lane settings. Then choose TLB.

The results are then displayed in the planning table.

In the SAP SNC Web application menu,

choose Replenishment Transport

Load Builder TLB Shipments .

Make the settings for the TLB run and choose TLB Planning Run.

The results are then displayed in the TLB Shipments section.


Activity SNP SAP SNC

Checking the TLB Results in Application Logs

For more information about application logs in SNP, see the SNP documentation under Application Logs.

On the SAP Easy Access screen, choose

Supply Network Collaboration

Tools Application Logs Display

Application Logs .

15.1 Master Data Setup for the Transport Load Builder

Use

In addition to the general master data settings for planning in Supply Network Planning (SNP)or SAP Supply Network Collaboration (SAP SNC), you can make additional settings for the Transport Load Builder (TLB). The following is intended to provide an overview of the TLB settings. For more information, see the input help for the individual fields.

NoteFor more information about master data settings that you can make for the additional functions of TLB in SAP SNC, see the SAP SNC documentation under Replenishment Transport Load Builder Additional TLB Functions in SAP SNC .

Settings

Product Master Data

You make the following settings in the product or location product master data:

Tab Page Field

Attributes ● Stacking FactorThis field is relevant if you want to use the Pallet Positions TLB parameter in the TLB profile [page 320]The stacking factor indicates how many pallets of a product can be stacked on top of each other. For mixed pallets, the system uses the smallest stacking factor of all products.



Tab Page Field

Units of measure For the Weight, Volume, and Pallet Positions parameters (only SNP TLB) that you use in the TLB profile, you must define the conversion of the parameter unit of measure to the base unit of measure for the product.

SNP 2 ● VMI Purch. GroupThe TLB can divide the TLB shipmentsinto individual orders according to the purchasing group of the VMI customer.

● ATD Receipt and ATD IssueThese fields are only considered by the SNP TLB. You can enter the category groups that you have defined in

the SNP Customizing under Basic Settings

MaintainCategory Groups. Using the category groups, you define which order categories are included in the quantity that is available for transport load building.If you do not enter a value here, the system uses the value from the location master data or the standard category groups ATR and ATI .

Lot Size/Quantity and Date Determination ● Rounding ValueThe TLB uses the rounding value for building transport loads. However, the TLB first uses the value that you have defined in the transportation lane, that is, in the lot size profile (SNP) or transportation guideline set (SAP SNC). If no value is assigned, the TLB uses the value specified here or 1 .So that the SNP TLB can use this rounding value, you must set the relevant indicator in the SNP Customizing

under Basic Settings Maintain Global SNP

Settings. Otherwise, the SNP TLB uses the rounding value from the transportation lane.


Tab Page Field

Goods receipt/goods issue ● Handling unit GThe TLB can only pack products with the same handling unit group together in the same handling unit (HU). In the SNP TLB, which does not use handling units, this field applies to pallets.

● Max. CoverageThe TLB considers the maximum coverage time during shipment upsizing. The system only brings forward as many deployment stock transfersas are necessary to cover demand within this time period.

● Shipment UpsizingFor the location product, you specify whether shipment upsizing is allowed and whether it is permitted beyond the maximum coverage time period.

● Loading grp.The TLB considers the loading group for the straight loadingloading method.

● Not PalletableYou specify whether the location product may be stacked on pallets. If you set this indicator, the TLB does not consider any pallet positions for this product.

Location Master Data

You make the following settings in the location master data:

Screen/Tab Page Field

Initial screen ● Loc. TypeThis field is relevant if you want to use transportation zones. For more information, see Use of Transportation Zones [page 319] .

SNP ● ATD Receipt and ATD IssueIf you have not defined category groups for the location product (see above), the SNP TLB considers the category groups defined here.

Transportation Lane Master Data



You make the following settings for the means of transport in the transportation lane master data:

Stage Field

Means of transport ● TLB profileYou must assign a TLB profile [page 320] that you created previously.

● Loading MethodYou specify whether you want the TLB to consider the straight loadingor load balancingloading method.

● Pull-In HorizonIf the TLB carries out a shipment upsizing, it considers the pull-in horizon.

● Siz.Desn and Shpmt Thr.Val.In the Siz.Decsn field, you determine how the TLB calculates the value it uses to decide about shipment sizing. The system compares the base value calculated with the value that you have entered in the ShpmThrVal field as the threshold value for shipment sizing, and then carries out either shipment upsizingor downsizing.

Product-Specific Transportation ● T. Lot PrflThis field is only considered by the SNP TLB. You can enter a profile here that you created in the SNP Cus

tomizing under Basic Settings Profiles SNP Lot

Size Profiles (Transportation Lanes). The TLB considers the value defined in this profile (see above).

15.1.1 Use of Transportation Zones

Use

In the Transport Load Builder (TLB), you can use transportation zones to group several locations together in one group (that is, one zone) and use one means of transport to ship TLB shipmentsto multiple locations. In this way, the system regards TLB shipments for multiple locations as one shipment for one location.

Activities

If you want to use transportation zones, in the location master data, create a location as location type 1005 ( transportation zone ) or 1006 ( stock transfer point for the Cross-Docking scenario in SAP Supply Network Collaboration (SAP SNC)).


After creating the location (type transportation zone or stock transfer point ), assign the relevant location in the hierarchy master data for transportation zones (select Master Data Hierarchy ). You can display location hierarchies in the shufflerfor interactive TLB planning.

You must also create a transportation lane that contains these transportation zones as destination location or source location and that has the same destination and source location as in the locations in the transportation zone.

In this instance, the TLB only considers the deployment stock transfersor the replenishment orders of locations you have assigned to the transportation zone.

See Also

For more information about using transportation zones in SAP SNC, see the documentation for SAP SNC under Customer Collaboration Responsive Replenishment Responsive Replenishment PlanningTransport Load Builder Additional TLD Functions in SAP SNC Processing of Remaining Quantities .

15.2 TLB Profile

Definition

You use this profile to determine within which parameter limits the Transport Load Builder (TLB) groups shipments for a means of transport.

Structure

Parameter Limit

In the Parameters for TLB Profile: XX section of the TLB profile, you can define upper and lower limits for the following standard parameters:

● Weight● Volume● Pallet Positions

You can define your own parameters in Customizing for SCM Basis under Transport Load Builder (TLB)Define TLB Parameters .

Rule Relationships

In the TLB profile section, you can define very flexible rule relationships for linking upper and lower limits. The following standard connections are available:



● Connect upper limits with 'and', lower limits with 'or' . When building transport loads, the TLB may not exceed any of the upper limits defined. At least one of the lower limits must also be reached or exceeded, depending on how you have defined the rules.

● Connect upper limits with 'and', lower limits with 'and' . The TLB may not exceed any of the upper limits defined. All lower limits must be reached or exceeded.

If you have chosen the '=' operator, the TLB also interprets the lower limits as upper limits.

In addition to the standard connection, you can also define user-specific relationships between the rules. Using the AND and OR operators as well as brackets, you can determine which combinations of rules you want the TLB to use when building transport loads.

When processing the rules, the TLB always considers the AND connection first and then the OR connection. If you want to change this sequence, you can put the OR connection in brackets.

ExampleYou have defined specific upper and lower limits for the parameters: Weight (Rule 1), Volume (Rule 2), and Pallet Positions (Rule 3). You now want to specify that you want either both rules 1 and 2, or rule 3 to be fulfilled. You then enter 1 AND 2 OR 3 in the Rule Details field.

If you want to define a rule connection, such as 1 OR 2 AND 3 and also want the TLB to consider the rules in this sequence, you must define the rules as follows: (1 OR 2) AND 3 .

15.2.1 Weight/Volume Mix

Use

The Transport Load Builder (TLB) loads a means of transport so that the load reaches a target weight/volume ratio. The target weight/volume ratio is the ratio between the total weight and the total volume of the products loaded onto the means of transport, such as a truck. By trying to reach an ideal weight/volume ratio, a proper weight/volume mix can be achieved, which makes the best use of the capacity of a truck and keeps the number of trucks to a minimum.

Features

1. In Customizing for SCM Basis , choose Transport Load Builder MakeTLBBasic Settings .2. In Weight/Volume Ratio , select one of the following options:

○ Static weight/volume ratioThis ratio is the ratio between the upper limit of the weight parameter in TLB profile and the upper limit of volume parameter in TLB profile. The static target weight/volume ratio can be calculated at the beginning of a TLB run.

○ Dynamic weight/volume ratioThis ratio is the total weight/ total volume of demand in planned receipts in the next "n" days. (The default value of "n" is 1 day.) The dynamic target weight/volume ratio is recalculated in every period.


3. In Wt./Vol. Tolerance , enter the weight/volume tolerance as a percent value.The tolerance factor controls the load building process.The load building process builds the load while trying to keep the weight/volume ratio between target weight/volume ratio * (1 - tolerance factor/100) and target weight/volume ratio * (1 + tolerance factor/100).One of the following results occurs:○ Current weight/volume ratio is within the range

The system continues with regular loading.○ Current weight/volume ratio is below the range

The system selects a product with a weight/volume ratio higher than the target weight/volume ratio. If no such product exists, select the one with highest weight/volume ratio.

○ Current weight/volume ratio is above the rangeThe system selects a product with a weight/volume ratio lower than the target weight/volume ratio. If no such product exists, select the one with lowest weight/volume ratio.

4. In Wt./Vol. Horizon , enter a value.In this field, you enter the number of days in the future that the system should consider to evaluate the total weight and volume of the planned receipts. This horizon is considered when the ratio type is dynamic.

Example

You have to transport bottled water (heavy, compact) and cereal (light, voluminous). If you put all the water in one truck, you would reach the weight limit long before you reach the volume limit. You might have a half-empty truck from a volume perspective; in some cases, you cannot even build a truck that satisfies both the weight and volume requirements. On the other hand, if you put all the cereal in one truck, then you hit the volume limit long before you reach the weight limit, which is equally undesirable. By introducing a target weight/volume ratio, and enhancing the load building process to try and achieve a proper weight/volume mix, these situations can be avoided.

15.3 TLB Procedures for Remaining Quantities

Use

If the Transport Load Builder (TLB) has not been able to load one of the TLB shipmentto the upper limits defined with the deployment stock transfersor replenishment orders of the current period, the TLB first redistributes product quantities. The TLB tries to ensure that all shipments lie within the valid upper and lower parameter limits by only loading some shipments to the defined lower limits. To do this, the TLB rebuilds all transport loads, taking the loading method into account.

If the TLB does not produce a valid solution this way either, it uses the following shipment sizing methods.

● Shipment Upsizing● Shipment Downsizing



Features

Shipment Upsizing

The TLB upsizes the product quantities to be transported by including further deployment stock transfers or replenishment orders that lie within the pull-in-horizon . The TLB also sorts the stock transfers within this horizon according to their days' supply.

You can also define a coverage period for a product in the master data for location product. The TLB is then only allowed to bring forward as many products that are necessary to cover demand within this time period. You can also rule our shipment upsizing for a product.

The TLB system upsizes the shipment quantities with individual rounding values of the product until all shipments lie within the valid upper and lower parameter limits.

Shipment Downsizing

Taking days' supply into account, the TLB downsizes the product quantities to be transported by prioritizing and reducing deployment stock transfers or replenishment orders in the current period.

Shipment Upsizing or Downsizing Decision

The TLB decides whether the to upsize or downsize a shipment based on a threshold value and a decision basis for shipment sizing. In SAP Supply Network Collaboration (SAP SNC), the TLB can also make the decision based on costs. You make these settings in the transportation lane for the means of transport. For more information, see Master Data Setup for the Transport Load Builder [page 316] .

Detailed Setting

You can also make detailed settings for shipment sizing by creating your own profile for the TLB basic settings in SAP SNC, or Supply Network Planning (SNP) Customizing (see Prerequisites section under Transport Load Builder [page 313] ). For example, for shipment upsizing, you can specify that you want the shipments to be loaded, as far as possible, to the upper parameter limit.

15.4 Monitoring TLB and Deployment Alerts

Use

You can use the Alert Monitor [page 244] to monitor alerts for the Transport Load Builder [page 313] and for Deployment in Supply Network Planning (SNP). To do this, you define a TLB alert profile containing a user-specific selection of alerts that are relevant for your planning area.

Features

The following table shows you the alert types available, and a brief description of each one.


NoteFor all the alerts except Invalid Delivery Date, you can enter priority variants based on critical values.

TLB/deployment alerts Description

Fair share (general) The fair share percentage is determined according to the rule specified in the deployment heuristic profile ( SNP2 tab in the location product master). The system triggers this alert if the percentages to deploy to meet product demand fall below the percentages specified in the master data.

Fair share (customers only) Same as above, except in this case fair share distribution refers only to customers instead of locations. (for example, VMI customers)

Invalid shipment When the shipment does not fulfill the parameters for the capacity of the means of transport (such as volume, weight, and pallet positions) defined in the TLB profile [page 320], the system generates an alert.

Invalid delivery dates You active this alert using the /SAPAPO/TLB_CHK_DATE BAdI.

Means of transport overload When the shipment exceeds the parameters for the capacity of the means of transport (such as volume, weight, and pallet positions) defined in the TLB profile, the system generates an alert.

Minimum load for transportation capacity not reached When the shipment does not reach the minimum parameters for the capacity of the means of transport (such as volume, weight, and pallet positions) defined in the TLB profile, the system generates an alert.

Activities

1. Select the alert types that are relevant to you, and define threshold values where required.2. Select the objects (products, transportation lanes, means of transport) for which the system should

determine alerts.3. If necessary, assign the TLB alert profile to your overall alert profile (see Overall Alert Profile [page 247]),

your SCC User Profile, or your user in SAP Supply Chain Management (SAP SCM) from the SAP Easy Access screen by selecting Advance Planning and Optimization Supply Network Planning Environment Current Settings Assign Planners to Alert Profiles .

RecommendationFor performance reasons, we recommend restricting the number of alerts to be displayed to a minimum.



More Information

Application-Specific Alert Profiles [page 248]


16 Package Building

You can use this function to create packages out of products.

Use

During package building, the system bundles the products into packages based on specific constraints, while also keeping the total number of packages to a minimum. The system can also specify the exact position and orientation of each product item.

You can define these constraints for different combinations of product, business partner, equipment, and location. If several constraints apply, the system always uses the most specific constraint. For more information, see Determination of Package Type Assignments [page 331].

You can use the constraints that you define within this function to create packages in SAP Transportation Management (SAP TM) and in SAP Extended Warehouse Management (SAP EWM).

For more information about creating packages in SAP TM, see SAP Library for SAP Transportation Management on SAP Help Portal at http://help.sap.com under Planning Package Building .

For more information about creating packages in SAP EWM, see SAP Library for SAP Extended Warehouse Management on SAP Help Portal at http://help.sap.com under Goods Issue Cartonization Planning Configuring Package Building .

Prerequisites

● You have defined product master data. For more information, see Defining Product-Specific Master Data [page 328].

● You have defined package type assignments. For more information see Defining Package Type Assignments [page 330].

● You have defined a package building profile. For more information, see Package Building Profile [page 335].● If you want to use mixed package building, you have optionally defined a product relationship profile in

transaction /SCMB/VC_MAT_PKG_RP. In this profile, you can define incompatibilities and stacking rules. Moreover, you can define the sequence in which the products are to be packaged.

● If you want to use detailed mixed package building, you have done the following:○ You have optionally defined a profile for the package building optimizer. This profile contains technical

settings like runtimes, dump and trace levels. For more information, see Customizing for SCM Basis under Pack Package Building Define Profile for Package Building Optimizer .

○ You have optionally defined a rule profile for the package building optimizer. This profile allows you to select predefined rules and define values and priorities. For more information, see Customizing for SCM Basis under Pack Package Building Define Rule Profile for Package Building Optimizer . For more information, see Rule Profile for the Package Building Optimizer [page 336].


Package Building

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com


○ You have optionally defined a product orientation profile. In this profile, you define how a product can be positioned in a package. For more information, see Customizing for SCM Basis under Master Data Product Define Product Orientation Profile .

Features

When creating packages, the system can split the quantity of a product using the following criteria:

● Quantity per package● Maximum height of the package● Maximum weight of the package

If different products are to be packaged, the system considers the lowest maximum height and the lowest maximum weight for a product or a packaging material. For example, if each product has a different maximum height, the system uses the lowest maximum height.

The system creates mixed packages based on one of the following consolidation types:

● Volume● Layer definitions● Incompatibilities, stacking rules, and product orientations (based on these values, the system determines

the exact positions of each product item in the package (detailed mixed package building))

The result of package building is different types of packages:

● Packages that contain only a single type of product● Mixed packages that contain several different products● Packages that consist of several layers

The layers within a package can also contain different products, which results in mixed layers.● Nested packages, that is a package in another package

For example, you can plan 24 cans in one box and 100 boxes in ten layers on one pallet.● Full packages or incomplete packages

Incomplete packages provide room for further consolidation.● Flat or uneven packages

Flat packages are a prerequisite for stackability.

These package types can be combined. For example, the result of package building can be an incomplete, uneven mixed package with mixed layers.

You can simulate the package building. For more information, see Test Report for Package Building [page 339].

You can check whether you have defined your package building constraints in a consistent way. For more information, see Consistency Check of Package Building Constraints [page 342].

For more information about best practices and the processing logic, see SAP Note 2581421 .

NoteYou can adapt these constraints according to your specific business needs with several Business Add-Ins (BAdIs). For more information, see Customizing for SCM Basis under Pack Package Building .

SCM BasisPackage Building P U B L I C 327


Example

You have 105 laptops and 117 mini hi-fi systems. 90 laptops and 80 mini hi-fi systems form a complete package, while 10 laptops and 16 mini hi-fi systems form one layer. If you allow mixed packages to be created with mixed layers, the system plans to put the remaining 15 laptops and 37 mini hi-fi systems in a mixed package with one layer consisting of 10 laptops, two layers each consisting of 16 mini hi-fi systems, and one mixed layer consisting of 5 laptops and 5 mini hi-fi systems.

Related Information

Detailed Mixed Package Building [page 337]

16.1 Defining Product-Specific Master Data

In the master data of a product, you define product-specific attributes that the system considers when creating packages.

Procedure

● On the SAP Easy Access screen, choose SCM Basis Master Data Product /SAPAPO/MAT1 - Product .

● On the Units of Meas. (Units of Measure) tab page, define the following:

○ Dimensions (length, width, height) of the product○ Weight of the product○ Definitions for full packages, that is, the product quantity that fits into one package as well as the

height and weight of the package○ Definitions for full layers, that is, the product quantity that fits into one layer as well as the height and

weight of the layer○ Maximum stacking factor (see Stacking Factor [page 329])○ Maximum top load, that is, the maximum weight that you can place on top of a full package of this

product○ A conversion factor between the base unit of measure and the unit of measure for normalized quantity

(see Determination of Normalized Load Consumption Quantities [page 332]).

Layer definitions are typically used for mixed packages. If you do not define any layer definition for your product, the system creates packages based on the available volume of the packaging material.

You can define multiple layer and package definitions for a product. To do so, you need to define packaging-specific units of measure in Customizing for SAP NetWeaver under General settings Check Units of Measurement . In the Define Package Type Assignment transaction, you can indicate in which cases these


Package Building

different layer and package definitions are to be used. For example, you can use different layer definitions for different business partners.

● On the Pkg Data (Packaging Data) tab page, define settings for the packaging material. Note that these settings are only relevant if the physical attributes of the packaging material are to be taken into account during package building. In this case, you need to define a product for the packaging material and define the following settings:

○ Maximum height and weightNote that these are global limits that apply for your entire company, for example. You can set lower limits, for example on a product-specific basis, in the Define Package Type Assignment transaction.

○ Closed Packaging (closed packaging material)○ Filling level (for volume-based mixed package building)

● On the Pkg Data (Packaging Data) tab page, define settings for package building:

○ A reference product for package building○ A product orientation profile○ The shape of the product○ Thresholds for overhang, and absolute height

For more information, see the system documentation and SAP Note 2581421 .

Related Information

Defining Package Type Assignments [page 330]Reference Products for Package Building [page 338]

16.1.1 Stacking Factor

The stacking factor defines how products and packages, for example pallets, can be stacked.

On the Units of Meas. (Units of Measure) tab page of the product master data, you can define a maximum stacking factor per alternative unit of measure. If, for example, you define a maximum stacking factor of six for the alternative unit of measure of the product (for example PC (Piece) or EA (Each)), it means that the product can be stacked up to six times on itself. This is taken into account during detailed mixed package building. Detailed mixed package building also takes into account maximum stacking factors that you have defined for reference products.

The maximum stacking factor that you define for the alternative unit of measure of the packaging material (for example PAL (Pallet)) is determined in package building and taken into account during load planning. For example, you can specify a maximum stacking factor of two for pallets. This means, that no more than two pallets can be stacked on top of each other.

For closed packaging, only the stackability of the packaging material is relevant, the stackability of the products within the packaging material does not matter. For example, a pallet cage is considered as the outer packaging and thus the system checks the maximum stacking factor that you defined for the pallet cage and takes it into account during load planning. If a product is packaged in a carton, the stackability of the carton is relevant for detailed mixed package building since the carton will be packaged further.



You can also define a stacking factor on the Properties tab page (that is, on header level). It indicates how often a pallet of this product can be stacked during load planning. Note however, that if you define a stacking factor on header level, the system ignores the maximum stacking factor that you defined on the Units of Meas. (Units of Measure) tab page.

16.2 Defining Package Type Assignments

By defining package attributes, for example the packaging material, you specify what kind of packages the system is to create for your products.

Context

You have the following options:

● You define package attributes for multiple different combinations of product, business partner, location, and equipment.

● You define package attributes for multiple different combinations of business partner, location, and equipment.

● You define an exclusive package for a business partner.● You define normalized load consumption quantities for your products or have the system determine them.

NoteIf you define more specific attributes for a specific product (first option), the system considers these attributes and ignores the more global attributes (second option).

You can define the following package attributes:

● Packaging material and package type● Limits to be applied, for example, the maximum height and weight of the package● Product-specific attributes, for example, a separation material or if mixed packages and mixed layers are to

be created

In the Packaging Material field, you enter the product ID of the packaging material that you defined in the product master data. This packaging material is used for full packages and mixed packages unless you have specified an additional product ID in the Packaging Material (Mixed) field. In this case, all remaining product items are packaged in mixed packages using this additional packaging material.

The package type can be either the packaging material, or the unit of measure, or both. You can enter the packaging material, or the package type, or both:

● If you only enter the packaging material and not the package type, the system uses the base unit of measure that you defined in the product master data.

● If you only enter the package type and not the packaging material, the weight and dimensions that you defined in the product master data are not considered. The system only considers limits that you specify in this transaction.


Package Building

● If you enter both a packaging material and a package type, the system overrides the base unit of measure that you defined in the product master data with the package type that you specify in this transaction.

If you want the system to create layers, you have to indicate a unit of measure for layers. If you do not indicate such a unit of measure, the system creates packages based on your settings in the package building profile (either volume-based package building or detailed mixed package building).

Some of these attributes can also be defined in the package building profile. However, the parameters in the package building profile are global parameters and are taken into account only if you have not defined more specific attributes here.

For more information about the individual attributes, see the system documentation.

For more information about best practices and the processing logic, see SAP Note 2581421 .

To define package attributes, you need to do the following:

Procedure

1. Open the Define Package Type Assignment transaction by entering /SCMB/PB_PKG_ASS in the command field.

2. Define the package attributes.

Note that you have to define attributes on the Product-BP-Location tab page. The other two tab pages are optional.

Related Information

Package Building Profile [page 335]Determination of Package Type Assignments [page 331]Determination of Normalized Load Consumption Quantities [page 332]

16.2.1 Determination of Package Type Assignments

During package building, the system determines package type assignments to decide how to best package a product.

The system always uses the most specific value that it can find for a parameter.

To determine this value, the system does the following:

1. The system checks if you have defined a value for a specific parameter on the Product-BP-Location tab page. On this tab page, you define product-specific package attributes for different combinations of key fields, that is, product, business partner, location, as well as equipment type and group.

2. If the system does not find a value or if you selected Undefined for the parameter on the Product-BP-Location tab page, the system looks for a value on the BP-Location tab page. On this tab page, you define



product-independent package attributes for different combinations of key fields, that is, business partner, location, as well as equipment type and group.

3. If the system does not find a value for the parameter on the BP-Location tab page either, it uses the initial value (0).If you also selected Undefined for the parameter on the BP-Location tab page, the system checks if you made a global setting for the parameter in the package building profile.

4. On the BP tab page, the system checks if you indicated that an exclusive package is to be built for the business partner.

RecommendationPlease use placeholder (*) for the key fields very carefully. For products and locations, we recommend that you use reference products for package building and location hierarchies instead.

● If several products are to be packaged in the same way, we recommend that you define reference products for package building. You define reference products for package building in the product master data.

● If the same attributes apply for a large number of locations, we recommend that you define a location hierarchy in the package building profile.

Note● The key fields Equipment Type and Equipment Group allow you to indicate the resource to which the

product is assigned.You can use these fields if the way a product is packaged depends on the resource with which it is going to be transported. For example, if you need to transport frozen goods, placing them on a pallet would be fine if the resource is a refrigerated truck. If the resource is a regular truck, however, you would need to package the goods into a refrigerated compartment.

Related Information

Defining Package Type Assignments [page 330]Package Building Profile [page 335]Defining Product-Specific Master Data [page 328]

16.2.2 Determination of Normalized Load Consumption Quantities

During package building, the system determines normalized load consumption quantities (normalized quantities, NLQ) to get accurate values regarding the load consumption of products. Based on these values, vehicle scheduling and routing optimization is able to choose the most suitable resources later in the process.

To determine the normalized quantity for each product, the system does the following:


Package Building

1. The system first checks if values are available in the Normalized Quantity field of the package type assignment transaction (on the Normalized Quantity Definition tab page). These values can have the following source:○ You have entered the values manually.○ You have executed the NLQ determination report. The results are copied in this field automatically. For

more information, see NLQ Determination Based on Randomized Data [page 333].○ You have uploaded a Microsoft Excel file that contains the values.

2. If the system finds values in this field, it multiplies for each product the corresponding value with the planned quantity indicated in the freight unit item.The system saves the results in the freight unit items. In addition, it displays the sum of the normalized quantities of all items on header level of the freight unit.

3. If the system does not find values in this field, it checks the product master data. If it finds a conversion factor between the base unit of measure and the unit of measure for normalized quantity for a product, it uses this conversion factor to determine the normalized quantity for this product.

4. If you have not defined conversion factors in the product master data, the system does not determine normalized quantities during package building.

NoteThe system only determines normalized quantities if you have defined a unit of measure for normalized quantity in your package building profile.

Related Information

Use of Normalized Quantities and Capacities

16.2.2.1 NLQ Determination Based on Randomized Data

Use

You can use this report to determine a value for the normalized load consumption quantity (normalized quantity, NLQ) per product and unit of measure (UoM) by using a statistical approach. This value indicates how much space (footprint) a single product consumes in a top-level package (that is, the outer packaging).

The report determines this value in the following way:

1. Based on your selection, the report creates a random number of SPBUs (that is, units created by separate package building) with a random number of product items that contain a random quantity of products. Each SPBU represents a transportation demand, that is, a set of goods that are transported together across the entire transportation chain within a specific period of time (for example, one delivery day).

2. The report creates one CPBU (that is, a unit created by capacity-document-based package building) with an infinite capacity for all product items of these SPBUs. The CPBU represents a transportation order.


https://help.sap.com/viewer/54cf405c9d9e4c96bf091967ea29d6a7/9.6.2/en-US/8766684f1c884168839cd2887fa299d6.html

3. The report performs package building based on this CPBU and builds the best possible packages.4. Based on the package building results, the report calculates a value for the normalized quantity for each

product.5. The report repeats step 1-3 as many times as you have indicated (number of calculation runs).6. By evaluating the values calculated during these calculation runs, the report determines a unique weighted

value for the normalized quantity per product.

Prerequisites

● You have defined dimensions for your products.● We recommend that you check the consistency of your package building constraints before you run this

report. For more information, see Consistency Check of Package Building Constraints [page 342].

For more information about prerequisites for package building, see Package Building [page 326].

Features

Selection

You need to indicate the following:

● A UoM for the normalized quantity● A package building profile● The number of calculation runs● A range for the number of SPBUs, that is, the number of transportation demands● The update mode, that is whether the system is to save the results or run the report in simulation mode

(default setting)● Whether the system is to keep the load consumption quantities in the base UoM of the packaging material

in addition to converting them into the normalized quantities● At least one input option. For each input option, you can indicate the following:

○ A product or reference product○ A range for the number of items to be created per SPBU○ A range for the product quantity per item

By indicating more than one input options, you can influence the weighting of specific products related to one SPBU.

Outputs

The report determines a value for the normalized quantity for each product, which is saved in the Normalized Quantity field on the Normalized Quantity Definition tab page of the package type assignment transaction, if you have made the respective setting (see "Selection"). If the Normalized Quantity Definition tab page already contains entries for combinations of product number and UoM for the normalized quantity, these entries are overwritten.


Package Building

Activities

To start the report /SCMB/PB_FOOTPRINT_DET, enter transaction code /SCMB/PB_NLQ_DET in the command field.

Related Information

Package Building Profile [page 335]Defining Package Type Assignments [page 330]

16.3 Package Building Profile

The package building profile is a collection of parameters with which you control the creation of packages.

For example, you can indicate whether the system is to create mixed packages. If so, you can indicate if they are to be created based on volume or whether the exact positions of the products are to be determined (detailed mixed package building). For detailed mixed package building, you can make further settings. For example, you can indicate how the products will be arranged. Moreover, you can disable stacking, grouping, and overhang. And finally, by indicating a profile and a rule profile for the package building optimizer, you can let the system take into account further technical settings and predefined rules.

In the General Data area, you can define a unit of measure for normalized load consumption quantities. If you define such a unit of measure, the system determines normalized load consumption quantities during package building.

For more information, see the system documentation.

Note● You do not have to define any of these parameters. The package building will then run in standard

mode.● Some of these parameters are also available in the Define Package Type Assignment transaction.

However, the parameters in the package building profile are global settings and are taken into account only if you have not defined more specific values in the Define Package Type Assignment transaction.

You define package building profiles in Customizing for SCM Basis under Pack Package Building Define Package Building Profile .

Related Information

Defining Package Type Assignments [page 330]Rule Profile for the Package Building Optimizer [page 336]


Detailed Mixed Package Building [page 337]Reference Products for Package Building [page 338]Determination of Normalized Load Consumption Quantities [page 332]

16.3.1 Rule Profile for the Package Building Optimizer

SAP offers a number of predefined rules that you can use for detailed mixed package building. For each rule, you can indicate a value and a level. Indicating levels allows you to define a hierarchy between several rules.

Rule Number Rule Description Explanation

1110 Minimize height difference on capacity (in mm)

With this rule, you can minimize the height differences of the surface of the package. This objective is defined as standard deviation of the heights of the different cartonized or non-cartonized products that form the surface of the package, weighted by the sizes of these individual product surfaces.

You can indicate the deviation from the standard deviation that the package building optimizer is to reach. This value is considered as a threshold, that means, all height differences above are penalized. It is always measured in millimeter.

3010 Minimize distance of center of mass from capacity center

With this rule, you can minimize the distance between the center of mass of the load (that is, the products) and the center of a package, for example, a pallet.

You can indicate a threshold value that defines the maximum deviation above which the package building optimizer penalizes distances.


Package Building

Rule Number Rule Description Explanation

3020 Minimize height of center of mass on capacity

With this rule, you can minimize the height distance between the center of mass of the load (that is, the products) and the bottom side of a package, for example a pallet.

You can indicate a threshold value that defines the maximum deviation above which the package building optimizer penalizes height distances.

Note that these rules only apply to top-level packages, that is, to the outer packaging.

16.4 Detailed Mixed Package Building

You can use this function to create mixed packages for products.

Prerequisites

● You have installed the package building optimizer. For more information, see SAP Note 1686826 .● In your package building profile in Customizing, you have selected Detailed Mixed Package Building in the

Mixed Package Building Mode field. By doing so, additional fields are made editable, which allow you to make further settings. For more information, see Customizing for SCM Basis under Pack Package Building Define Package Building Profile .

Use

During package building, the package building optimizer creates mixed packages for products taking into account the constraints you have defined. Moreover, it determines the exact position of each product item and its orientation.

The package building optimizer takes into account the following constraints:

● Package building profile (settings for detailed mixed packaging)● Product package assignments● Product-specific master data (settings for package building)● Product orientation profile● Product relationship profile● Profile for the package building optimizer



● Rule profile for the package building optimizer

Related Information

Package Building [page 326]Defining Product-Specific Master Data [page 328]Defining Package Type Assignments [page 330]Package Building Profile [page 335]Rule Profile for the Package Building Optimizer [page 336]

16.5 Reference Products for Package Building

You can define reference products to simplify the process of defining package building attributes.

If you have a group of products that need the same packaging attributes, you can define the attributes once for a reference product and then assign the reference product to each product of the group. By doing so, all of the products inherit the attributes of the reference product.

The following attributes can be defined for reference products:

● Definitions for full packages● Definitions for full layers● Package type assignments● Incompatibilities● Stacking rules● Consolidation sequence

NoteYou define full packages and full layers in the product master data. You define incompatibilities, stacking rules, and the consolidation sequence in the product relationship profile.

When creating packages, the system first tries to create full packages with one product. If this is not possible, the system adds other products from the group with the same reference product.

You can define reference products on more than one level.

NoteIf you want to change the reference product for multiple products, we recommend to use the test report for package building. For more information, see Test Report for Package Building [page 339].


Package Building

Related Information

Defining Package Type Assignments [page 330]Defining Product-Specific Master Data [page 328]Package Building Profile [page 335]

16.6 Test Report for Package Building

With the test report you can simulate the building of packages and analyze the result. You can also display and analyze the master data for products and display products or reference products in the product hierarchy.

The test report for package building offers several execution modes. You can do the following:

● Simulate the building of packages and analyze the result● Display the package types assigned to a product or reference product● Display a hierarchy for products or reference products

To start the product-based simulation of package building from the SAP Easy Access menu, choose SCM Basis Package Building Test Report for Package Building . Alternatively you can start the test report for package building (/SCMB/TEST_PB) by entering the transaction code /SCMB/TEST_PB in the command field.

Package Building Result (PB Result)

You can simulate the creation of packages out of products and analyze the result. You have the following options to start the simulation:

● Select products by various product-based selection criteria● Select a package building profile (optional). If you do not select a package building profile, the system

builds packages based on the volume of the products.● Start the report with an empty input section and select products later

You can navigate to the product master data and change data, if needed.

Messages from the package building, like error messages, warnings or success messages, are displayed to help you understand and analyze the package building result.

The simulation of package building includes the following functions:

Function Where to Find Further Information

Add products Toolbar of input section Insert rows to add (further) products to the input list, then execute the simulation for package building to analyze the result.



Get Products per Reference Product Toolbar of input section Add all products in one go to the input list that are located below the entered reference product.

Export/Import data Toolbar of input section Download currently displayed input list.

If you plan to upload data, you should first download data, to get the data structure.

Open Product Master Result section Doubleclick the icon to navigate to the product master data. You can change the data, if needed.

Display Product Hierarchy (up) Result section Doubleclick the icon to display all products of the hierarchy that are above the entered product.

Display Package Type Assignments

With this execution mode you can display the package types assigned to a product. Select your products by various product-based selection criteria.

Display Hierarchy for Product or Reference Product

With the product hierarchy, you can display products (or reference products) and their location in the product hierarchy. Data like product master data, package type assignment or the alternative unit of measure is displayed in the hierarchy. You can navigate to the transactions and change the data, if needed.

You have the following options to start the product hierarchy:

● Hierarchy up: Show all (reference) products in a hierarchy tree that are located above the entered product.● Hierarchy down: Show all (reference) products that are located below the entered product. The entered

product serves as top node.

The product hierarchy includes the following functions:


Add products Toolbar of input section Insert rows to add (further) (reference) products to the input list and then display the hierarchy trees of the added (reference) products.

Remove products Toolbar of input section Remove rows to delete (reference) products from the input list and then display the hierarchy trees of the remaining (reference) products.


Package Building


Open Product Master Result section (tree) Doubleclick the icon to navigate to the product master data. You can change data, if needed.

UoM Result section (tree) Doubleclick the icon to display the alternative unit of measure (UoM) of the corresponding (reference) product.

PTA Result section (tree) Doubleclick the icon to display the package type assignment of the corresponding (reference) product.

Show PTA Toolbar of result section Mark one or several nodes to display the package type assignment. The symbol in column PTA shows if a package type is assigned to a (reference) product.

Show Alternative UoM Toolbar of result section Mark one or several nodes to display the alternative unit of measure (UoM) of a product.

PTA Customizing Toolbar of result section Navigate to the transaction where you can define package type assignments for products (/SCMB/PB_PKG_ASS).

Change Reference Product Toolbar of result section Prerequisite: You have authorization to make changes.

Mark one or several nodes, to change the assigned reference product. When the system asks you, confirm switching to change mode. The system will then make the change. Note, you remain in change mode until you leave the report.

Show Alternative UoM Toolbar of package type assignment section

Mark one or several rows to display the alternative unit of measure (UoM) of a packaging material.

Related Information

Defining Product-Specific Master Data [page 328]Defining Package Type Assignments [page 330]Package Building Profile [page 335]Reference Products for Package Building [page 338]


16.7 Consistency Check of Package Building Constraints

With this report, you can check whether you have defined your package building constraints in a consistent way.

Use

Package building takes into account a wide range of constraints, such as master data and various profiles. When package building is complete, you might wonder why the system has built packages in a certain way. This report lets you check your constraints to discover any potential inconsistencies.

A number of individual checks are available. They are grouped in predefined categories, such as:

● Products● Package type assignments● Normalized quantities

Integration

By selecting Open Ref. Mat. Hierarchy (Up) (Open Reference Material Hierarchy (Up)) in the check results area, you can directly open the test report for package building and analyze the product hierarchy. For more information, see Test Report for Package Building [page 339].

Features

SelectionTo run the report, you need to select the following:

● A product, a reference product, or a range of products● One or several check categories

Moreover, you can specify how the output should look. You can indicate whether the report is to focus on products or checks and whether successful check results are to be displayed as well. Note that you can change these output settings on the consistency checks screen after you have executed the checks.

When you execute the report, the consistency checks screen is displayed:

● On the left, you can select the individual checks and execute them.● On the right, the check results are displayed.

OutputThe check results are displayed according to your output settings. A red check result indicates a critical inconsistency that might lead to a package building run failure. A yellow check result indicates that the system might not build the packages as you expect it.


Package Building

From the check results area, you can directly open the following:

● Product master● Test report for package building (see Integration)● Package type assignment transaction

Activities

Enter transaction code /SCMB/CHECK_PB_CONS in the command field to start the report /SCMB/CHECK_PB_DEFINITIONS.

On the selection screen, choose Program Execute in Background to execute the report in batch mode. The system executes all checks of the categories, which you selected.

Related Information

Defining Package Type Assignments [page 330]Defining Product-Specific Master Data [page 328]


17 Route Determination

Use

The aim of route determination is to find the most suitable route from a large number of routes. Route determination is executed in the routing guide. It runs automatically in the background.

A report is available for simulating route determination (see Simulation of Route Determination [page 364]).

Integration

Route determination is integrated with the following components and systems:

Task System

Perform the Global ATP check and backorder processing SAP Advanced Planning and Optimization (SAP APO)

Create sales orders and perform the Global ATP check SAP CRM and SAP APO

Perform the Global ATP check when converting unchecked deliveries into checked deliveries

ERP system and SAP APO

Make route-relevant changes, for example, change delivery date/time or goods recipient

Delivery processing in EWM

If you want to perform dangerous goods checks, you must ensure that route determination is integrated with the ERP component EH&S.

Environment, Health, and Safety (EH&S)

Prerequisites

For route determination, you have made the following settings:

● You have defined the following master data:○ Locations○ Transportation lanes○ Zones (see Zone [page 350])○ Routes (see Route [page 346])○ Carrier profile for the routing guide (see Carrier Profile for the Routing Guide [page 351])○ General transportation cost profile (see General Transportation Cost Profile [page 353])

● You have defined the means of transport and, if necessary, hierarchical relationships between means of transport in the SCM Basis master data.


Route Determination

● You have defined a transportation zone hierarchy in transaction Hierarchy Maintenance ( /SAPAPO/RELHSHOW).

● If you want to perform route determination within a cross-docking context, you must define cross-docking routes. For more information, see Cross-Docking Route [page 349] and Route Determination as Part of Cross-Docking [page 358].

● To enable the integration of route determination with the components and systems listed above, you must select the Activate RG checkbox in Customizing for SCM Basis under Routing Guide General Settings for Route Determination .

● If you want the master data in various systems to always have the same status, you must configure the distribution of master data. For more information, see Distribution of Master Data [page 368].

Features

Route determination comprises the following steps:

● Static Route Determination [page 356]The system determines possible trips from the available routes. When doing this, the system can take into account the assignment of carriers to the geographical data, such as legs.

● Scheduling [page 359]The system calculates the start or end dates/times for the trips found. When doing this, it takes into account calendars and times for the activities departure, transportation, arrival, and transshipment:○ Forward scheduling: the system uses a start date/time (for example, order creation date/time) to

calculate the end date/time (for example, delivery date/time).○ Backward scheduling: the system uses an end date/time (for example, requested delivery date/time)

to calculate the start date/time.● Dangerous goods check

The system first checks if a product is classified as dangerous goods. The system then checks if the product is allowed to be transported within a series of jurisdictions, for example, countries using a certain means of transport. These two checks are performed in EH&S services.If the product is classified as being dangerous goods and is allowed to be transported with the means of transport concerned, the system checks if the assigned carriers can accept dangerous goods. It rejects all carriers that do not offer dangerous goods transportation along the legs used.For more information, see SAP Library for SAP Extended Warehouse Management (SAP EWM) on SAP Help Portal at http://help.sap.com SAP Business Suite SAP Extended Warehouse ManagementEH&S Services Dangerous Goods Management .

● Calculation of Transportation Costs [page 363]The system calculates the transportation costs for all the trips found. When doing this, it takes into consideration fixed transportation costs, distance-dependent costs (based on the transportation distance), time-dependent costs (based on the transportation duration), and weight-dependent costs. It also takes into consideration penalty costs for a premature or delayed delivery and a premature or delayed pickup. The costs that you have defined are evaluated by the system in the following order:1. Costs from the carrier profile2. Costs from the general transportation cost profile or costs that you have defined for transportation

lanesYou can use the Business Add-In (BAdI) /SCTM/EX_RG_COST to determine alternative values or to adjust the values determined by the routing guide.

SCM BasisRoute Determination P U B L I C 345


● Additional filteringIf you want to use your own criteria to perform additional filtering on the trips that have been found up to now, you can implement the BAdI /SCTM/EX_RG_FILTER.

● ValuationYou can set up the route determination to consider different trip attributes for evaluation and sorting of the determined routes. The routing guide can determine the most cost effective or the quickest route. It is also possible to apply rules regarding the location priority.If you request the most cost effective route, the routing guide considers for each request only trips with complete cost information, in other words, trips for which you have defined costs for all the legs. If no such trips exist, the system falls back on trips with incomplete cost information. The system then sorts the trips according to the costs determined. If the system finds multiple trips with identical costs, it sorts the trips by date. In the case of forward scheduling, the system gives preference to the earliest start date. In the case of backward scheduling, it gives preference to the latest end date.If the quickest route is requested, the routing guide sorts the results according to the determined total transportation time.In cases where route determination runs in the background, the system returns the best result only. It rejects the remaining results.

17.1 Route

Definition

Sequence of legs that are connected by transshipment locations.

Use

The route represents a framework or corridor that comprises a multitude of trips, in other words, possible concrete itineraries. The system uses routes to determine trips in route determination (see Route Determination [page 344]).

You can form cross-docking routes from routes (see Cross-Docking Route [page 349]).

You can define routes in transaction /SCTM/ROUTE.

Structure

Leg

A leg is assigned uniquely to a route, in other words, it cannot be part of multiple routes. You define legs as a sequence of stops. Each stop is a supply chain unit (SCU), in other words, a location, or zone (see Zone [page 350]). The stops that connect two consecutive legs must be locations.


Route Determination

By specifying whether the stop-offs are optional or mandatory, you define which locations the carrier is to serve in which order.

You assign exactly one means of transport to each leg. In most cases, adjacent legs of a route have different means of transport. However, it might also be necessary to change legs due to various properties of the legs. Nonetheless, in most cases, the legs of a route represent its unimodal parts.

Stop

At stop level, you can assign a mode of transport for foreign trade to each location. The system then takes into account this mode of transport for outbound shipments in the case of exports. The value that represents this mode of transport is dependent on the country in which the location lies. The system does not check if the mode of transport semantically matches the means of transport used for the leg of this location. Since, in most cases, the system cannot define a unique country for zones, it does not permit you to define a mode of transport for such stops.

In static route determination, the system determines the mode of transport for foreign trade for outbound shipments (trips) in the following sequence:

1. Country of first location2. Part of the location sequence of the trip that runs from the first location within this country3. The first location in this part of the location sequence when going backward that is a stop along the leg and

for which a mode of transport for foreign trade was defined, in other words, the location that lies closest to the border.

Carrier Assignment

You can assign as many different carriers as you want to your means of transport or any of its subordinate means of transport for the leg. You can specify whether dangerous goods can be transported for each such combination of leg, means of transport, and carrier.

In static route determination, the system defines the carrier for a trip as the carrier for the first leg who can transport dangerous goods, if required, and for which you have defined the lowest costs for transportation along this leg in the carrier profile.

Departure Calendar Assignment

You can define a departure calendar for the leg. If the departures for a specific request type do not correspond with the departure calendar for the leg, you can also define a specific departure calendar for this request type.

The system takes into account departure calendars when scheduling a trip for both the start location of the request and for each transshipment location served. For more information, see Scheduling [page 359].

Validity and Restrictions

You can restrict the validity of a route by specifying the following:

● A validity period that the system compares with the cutoff time of a single request.● Permitted shipping conditions that the system compares with the shipping conditions of a single request.● Permitted request types that the system compares with the request type of a single request.

You can specify permitted request types at the header level of the route and for each stop within the leg (customer, for example). The request types at stop level must be part of the request types that you specify at header level. Request types at stop level have a higher priority than those at header level. Accordingly, the request types at header level are valid for those stops for which you have not defined separate request types.


● Permitted transportation groups that the system compares with the transportation groups of the products in a single request.

● Weight limits for single and collective requests that the system compares with the total weight of the products in the single request or in multiple combined requestsYou can also specify weight limits for single and collective requests for each stop within a leg. These limits overwrite the relevant limits that you specify for the route at header level.

● Volume limits for single and collective requests that the system compares with the total volume of the products in the single request or in multiple combined requestsYou can also specify volume limits for single and collective requests for each stop within a leg. These limits overwrite the relevant limits that you specify for the route at header level.

● Dimension limits (length, width, and height)You can specify the maximum dimensions that a product is permitted to have to be valid for a certain route. The system compares these dimensions with those that you defined in the product master.

You can also define various lead times for the different request types. These influence the start time of a trip in scheduling.

Example

The following figure shows a route with three legs that are connected by the transshipment locations P and M. It also shows a (red) trip for the case where all stop-offs in the middle leg are optional and a (blue) trip for the case where these stop-offs are mandatory.

Route


Route Determination

17.1.1 Cross-Docking Route

Definition

One or more inbound routes or one or more outbound routes that are connected by exactly one cross-docking location (warehouse or distribution center relevant to cross-docking).

Use

You use cross-docking routes (CD routes) to link routes to route networks. The system takes into account CD routes when you use route determination as part of cross-docking.

Here you can define per route pair (inbound route and outbound route) whether goods at the cross-docking location (CD location) are to remain on the same vehicle or whether they are be loaded onto a different vehicle.

For more information, see Route Determination as Part of Cross-Docking [page 358] and SAP Library for SAP Extended Warehouse Management (SAP EWM) on SAP Help Portal at http://help.sap.com SAP Business Suite SAP Extended Warehouse Management Cross-Docking (CD) .

Structure

To define a CD route, you must make the following settings:

● You specify a CD location for the route at header level.● You specify one or more inbound routes on the CD Routes tab page. Here the destination location of all

these routes must be identical with the CD location.● You specify one or more outbound routes on the CD Routes tab page. Here the start location of all these

routes must be identical with the CD location. By specifying a different CD route as the inbound or outbound route, you can create a route network with multiple CD locations. Here an outbound CD route from CD location 1 must have at least one inbound route with the start location CD location 1. An inbound CD route to CD location 2 must have at least one outbound route with the destination location CD location 2.

● On the CD Attributes tab page, you define the required attributes, for example, whether transshipment is not required (goods remain on the same vehicle), for the route pairs that consist of inbound and outbound routes.

NoteYou define CD routes in the Maintain Route ( /SCTM/ROUTE) transaction.



Example

The following figure shows a route network consisting of two CD routes:

Cross-Docking Routes

17.2 Zone

Definition

A zone comprises a number of locations. You can define the following types of zone:

● Direct zoneYou define a direct zone by directly assigning locations to this zone.

● Postal code zoneIn the case of postal code zones, you indirectly define the locations contained in the zone. To do this, you assign a number of postal code intervals to a postal code zone. The postal code zone then contains all the locations that lie in at least one of these postal code intervals.

● Region zoneIn the case of region zones, you indirectly define the locations contained in the zone. To do this, you assign countries, and optionally a number of regions, to a region zone. The region zone contains all locations that lie in one of the selected countries and in at least one of the regions, if you have assigned regions.

● Leg zoneIn the case of leg zones, you indirectly define the locations contained in the zone. You define a leg of a route as a sequence of locations and, optionally, zones (direct zones, region zones, or postal code zones). The leg


Route Determination

zone then contains all the locations that are either part of this sequence or that belong to a zone that is part of this sequence.

NoteIn the zone definition, the system does not display the zones assigned to a leg, but instead simply the locations contained in the zones.

● Mixed zoneYou define mixed zones from locations, postal code intervals, and regions.

Use

The properties assigned to a zone can be partly transferred to all its locations. In this way, the zone helps to reduce the volume of master data.

ExampleAll the locations that are supplied by the same warehouse are grouped in a zone.

The main advantage of postal code zones, region zones, and leg zones is that you can take into account one-off locations. One-off locations are locations that are not created as master data in the system. You can therefore map unloading locations, for example, that are important for one request only. One-off locations are described by addresses where you must specify at least a country, a region, and a postal code. The country makes the postal code and region information unique.

You define and maintain direct zones, postal code zones, and region zones in the definition of zones for routes in transaction /SCTM/ROUTE.

You define and maintain leg zones in the definition of routes in transaction /SCTM/ROUTE. You can only display them in the definition of zones.

17.3 Carrier Profile for the Routing Guide

Definition

Profile in which you define data for the carrier (business partner with the role Carrier).

Use

The system takes into account the carrier profile data when determining routes in the routing guide (see Route Determination [page 344]).

You can create only one profile for each carrier.


You define the carrier profile for the routing guide in transaction /SCTM/TSPP.

Structure

Header Data

The carrier profile for the routing guide contains the following header data:

● Carrier address● Communication data● Administrative data

Geographical Data and Means of Transport

You can assign geographical data (locations or zones) and means of transport to the carrier. During route determination, the system only takes into account the assignment of a leg zone and a means of transport that is either the same as the means of transport for the leg or superior to it. For more information, see Hierarchical Relationships Between Means of Transport [page 354]. You can also specify whether the carrier for this assignment can accept dangerous goods.

Transportation Groups and Product Freight Groups

The system considers a carrier's transportation groups and product freight groups as restrictions (whether the carrier can accept the products in a request) when determining routes in the routing guide.

Freight Code Sets

Freight code sets are used to define freight codes. You use freight codes to communicate with freight forwarders and other service providers.

Transportation Costs

During route determination, the system takes into account the transportation costs with a higher priority than the costs in the general transportation cost profile (see General Transportation Cost Profile [page 353]).

● Global transportation costsGlobal transportation costs are fixed transportation costs that you define for a carrier's means of transport.

● Dimension-dependent transportation costsYou define dimension-dependent transportation costs for a carrier's means of transport in a certain dimension and relevant unit. The following dimensions are supported:○ Distance○ Duration (transportation duration)○ Quantity (weight)○ Stop-offs (The system does not currently evaluate them.)

ExampleYou define dimension-dependent costs of 20.00 per kilometer driven for the dimension Distance.


Route Determination

17.4 General Transportation Cost Profile

Definition

Profile that contains costs for transportation planning.

Use

If you specify a general transportation cost profile in Customizing for SCM Basis under Routing GuideGeneral Settings for Route Determination , the system takes into account the relevant costs during static route determination (see Route Determination [page 344]).

NoteThe costs that you define in the general transportation cost profile are not actual costs, but instead they represent a theoretical value.

Structure

You define the following costs in the general transportation cost profile:

● Location-specific costsYou can define the following penalty costs for each priority:○ Earliness costs (per day) for pickup or delivery○ Lateness costs (per day) for pickup or delivery

A trip that has been determined by static route determination only has a premature pickup or delivery, if the request contains a start date/time or an end date/time and the pick-up or delivery date/time that has been determined lies before this requested date/time. Correspondingly, a trip only has a delayed pickup or delivery, if the request contains a start date/time or an end date/time and the pick-up or delivery date/time that has been determined lies after this requested date/time.

● Transportation-specific costsThese are fixed transportation costs that are incurred once for each means of transport used in the route determination run. They are independent of the actual transportation (in other words, distance, and so on).

● Dimension-specific costsThese are variable transportation costs per unit for the following dimensions:○ Time○ Distance○ Transported quantity per distance

These costs refer to the consumption of the dimensions of a vehicle for a request.● Transportation-lane-specific costs

These are variable transportation costs per unit and means of transport.


The values that are displayed on this tab page, for example, locations or zones as the start location or destination location, as well as means of transport costs come from the transportation lane.

Note

To define general transportation cost profiles, on the SAP Easy Access screen, choose SCM BasisRouting Guide Define General Transportation Cost Profile .

17.5 Hierarchical Relationships Between Means of Transport

Use

Route determination takes into account hierarchical relationships between means of transport when determining certain attributes. If the system does not find a certain attribute for a means of transport because you have not defined it, it automatically tries to find the attribute for the means of transport directly superior to the first one. If it does not find the attribute there either, the system tries to find it for the means of transport that is directly superior to this one, and so on.

By defining hierarchical relationships between your means of transport, you can reduce the effort required to enter your attributes. If, for example, you want to use route determination quickly without having to define a large number of attributes, it is sufficient to define the required attributes for the highest means of transport in the hierarchy only. The system then takes these attributes into account for all subordinate means of transport. If you subsequently define attributes for individual subordinate means of transport bit by bit, the system then takes these into account.

Defining hierarchical relationships is optional.

Prerequisites

You have defined means of transport and have specified superordinate means of transport for each of them in Customizing for SCM Basis under Master Data Transportation Lane Maintain Means of Transport . In this way, you have defined hierarchical relationships between your means of transport.

Features

Route determination takes into account hierarchical relationships for the following attributes:

● Attributes that you have defined when defining the means of transport, for example, average speed for scheduling

● Attributes that you have defined when defining transportation lanes for the means of transport, for example, transportation costs, transportation duration, and transportation distance


Route Determination

● Carriers that you have assigned to the means of transport when defining legsYou can assign a carrier not only to the means of transport for a leg but also to each means of transport superordinate to it. This is advantageous if you change the means of transport for the leg by entering a superordinate means of transport after you have assigned the carrier. In this case, the system automatically deletes all carrier assignments that do not refer to the new means of transport for the leg or one of its superordinate means of transport. You have specified means of transport TRUCK_LARGE for leg 1.

ExampleYou have specified CR 1 as the carrier for TRUCK_LARGE and CR 2 as the carrier for TRUCK. If you now change the means of transport for leg 1 from TRUCK_LARGE to TRUCK, the system automatically deletes the assignment of CR 1 to TRUCK_LARGE.

● Costs that you have defined in the carrier profile or in the general transportation cost profileSee Carrier Profile for the Routing Guide [page 351] and General Transportation Cost Profile [page 353].

NoteIf you have assigned a means of transport to a leg, route determination takes into account this exact means of transport and its superordinate means of transport only but not the subordinate means of transport. Otherwise, there would be too many solutions.

Example

The following table shows the hierarchical relationships between different means of transport:

Means of Transport Average Speed Superordinate Means of Transport

TRUCK 80 km/h

TRUCK_LARGE TRUCK

TRUCK_SMALL TRUCK

TRUCK 51' 60 km/h TRUCK_LARGE

TRUCK 48' TRUCK_LARGE

TRUCK 24' TRUCK_SMALL

TRUCK 21' TRUCK_SMALL

This produces the following hierarchical relationships:

TRUCK

TRUCK_SMALL TRUCK_LARGE


TRUCK 21' TRUCK 24' TRUCK 48' TRUCK 51'

When you enter the means of transport TRUCK_LARGE, the system determines an average speed of 80 km/h. Since you have not defined a value for means of transport TRUCK_LARGE, the system takes the value for the superordinate means of transport TRUCK.

When you enter the means of transport TRUCK 51', the system determines an average speed of 60 km/h, in other words, the value that you have defined for the means of transport TRUCK 51'.

When you enter the means of transport TRUCK 24', the system determines an average speed of 80 km/h. Since you have not defined a value for either means of transport TRUCK 24' or means of transport TRUCK_SMALL, the system takes the value for the superordinate means of transport TRUCK.

17.6 Static Route Determination

Use

Static route determination is part of route determination in the routing guide (see Route Determination [page 344]). In static route determination, the system uses the existing routes to determine possible trips, in other words, instances of these routes (see Route [page 346]).

Prerequisites

See the prerequisites under Route Determination [page 344].

Features

Determination of Geographically Possible Routes

The system first determines the number of routes that are geographically possible. Here the route must contain the start location and destination location from the request in the correct order.

A leg of a route and therefore the route itself contains a location if at least one stop in its sequence of stops contains this location. A stop of a leg contains a given location if one of the following conditions is met:

● The stop is a location and is identical to the given location.● The stop is a direct zone (see Zone [page 350]) and includes the given location.● The stop is a postal code zone or a regional zone and includes the postal code or the region of the given

location.


Route Determination

A route contains the start location and destination location from the request in the correct order in one of the following cases:

● At least one leg that contains the start location lies before another leg that contains the destination location in the leg sequence of the route.

● A leg in this route contains both the start location and the destination location, and at least one stop that contains the start location lies before another stop that contains the destination location in the stop sequence of this leg.

Determination of Valid Routes

A route that is possible from a geographical point of view is valid for a request if it meets all the following conditions:

● You have not explicitly excluded this route.● You have not marked the route for deletion.● You have not defined any restrictions for this route that make it invalid for the request (see Route [page

346]).

Creating the Location Sequence of a Trip

In accordance with the division of a route into legs, the location sequence of a trip is also divided into legs.

For each relevant leg of a valid route, the system uses the stop sequence to form a fixed sequence of locations for the relevant leg of the trip. A leg of a route is only relevant to a request in the following cases:

● It is the start leg for the request because it is the closest of all the legs containing the start location in the request to the destination location.

● It is the destination leg for the request because it is the closest of all the legs containing the destination location in the request to the start location.

● It is a leg between the start leg and the destination leg of the request.

Only the following locations are relevant to the system for the location sequence of the trip:

● Start location of the request; the last stop of the start leg that contains it is called the start stop.● Destination location of the request; the first stop of the destination leg that contains it is called the

destination stop.● Each transshipment location that connects two consecutive relevant legs● Each location in a relevant leg that you have marked as mandatory

As a result, the zones that you have defined as (optional) stops along legs are skipped when the location sequence of the trip is created.

To create the location sequence of the trip, the system arranges the relevant locations in accordance with the following rules:

● Two locations of different legsTheir arrangement is given by the leg sequence of the route.

● Two locations of different stops along the same legTheir arrangement is given by the stop sequence of the leg.

● Two locations of the same stop (along the same leg)This case only occurs if both the start location and the destination location from the request lie in the same zone and you have defined this zone as a stop along a leg. In this case, the location sequence of each trip consists of the start location and the destination location only.

Assignments


Among other reasons, a geographical route is not valid for a request if you have excluded the means of transport of a relevant leg as a result of the request. On the other hand, you reduce the assignment to its means of transport by explicitly excluding carriers.

17.6.1 Route Determination as Part of Cross-Docking

Use

When you use route determination as part of cross-docking, the system takes into account cross-docking routes (CD routes). For more information, see Route Determination [page 344] and Cross-Docking Route [page 349].

Prerequisites

The following prerequisites must be met:

● You have defined request types for CD routes in Customizing for SCM Basis under Routing GuideRoute Determination Define Request Types for Routing Guide .

● You have defined CD routes in transaction /SCTM/ROUTE. Here you have made sure that all the routes involved are suitable for cross-docking, in other words, they have one of the request types defined previously.

Features

The system first searches for possible route sequences in the route network that meet the following conditions:

● The start location of the request is contained in the first route of the route sequence.● The destination location of the request is contained in the last route of the route sequence.

Then it checks each possible route sequence to ascertain whether the attributes of the individual routes agree with the requirements in the request, for example, shipping conditions, weight restrictions, and request type. If a route in a route sequence does not meet these requirements, the system rejects the entire route sequence. The result is a number of route sequences that the system represents as a trip, in other words, a sequence of legs. The difference in comparison with route determination without cross-docking is that the trip covers multiple routes in this case. The additional steps in route determination take place in the same way as in the case of route determination without cross-docking (see Route Determination [page 344]).

NoteYou can use the Business Add-In (BAdI) Enhancements for Scheduling in Routing Guide ( /SCTM/EX_RG_PROCESS_SCHED) to determine alternative durations for the transshipment activities.


Route Determination

More Information

For more information, see SAP Library for SAP Extended Warehouse Management (SAP EWM) on SAP Help Portal at http://help.sap.com SAP Business Suite SAP Extended Warehouse Management Cross-Docking (CD) .

17.7 Scheduling

Use

In scheduling, the system calculates start and end dates/times for all valid trips. Here it takes into account calendars and times for the following activities:

● Transshipment● Departure/shipping● Transportation● Arrival/receipt

Scheduling is part of route determination in the routing guide (see Route Determination [page 344]). When you simulate route determination (see Simulation of Route Determination [page 364]), the system displays detailed results of scheduling. The following sections are particularly relevant to this case.

Integration

See Route Determination [page 344].

Prerequisites

For scheduling, the following prerequisites must be met:

● You have defined the following in the master data for route determination:○ Locations with geocoordinates○ Transshipment locations with minimum goods wait time and arrival calendar○ Optionally, transportation lanes with transportation calendars, transportation durations, and distances○ Routes with departure calendars (see Route [page 346])

● You have defined the average speed and the "actual distance versus aerial distance" factor for all relevant means of transport in Customizing for SCM Basis under Master Data Transportation Lane Maintain Means of Transport .

● See also the prerequisites under Route Determination [page 344].



Features

Scheduling is based on the following activities:

● Transshipment● Departure/shipping● Transportation● Arrival/receipt

The system takes into account these activities in this order for each leg of trip, whereby transshipment is not relevant to the first leg of the trip.

The routing guide chooses the relevant locations of the leg before scheduling, and defines a fixed order for them in accordance with the sequence strategy that you have defined for the leg. Here the following applies:

● A location is part of a leg if either itself or one of its zones is a stop along the leg.● A location of a leg is relevant if it does not lie before the start location or after the destination location of the

request, and is either a transshipment location or part of a leg for which you cannot skip stops.

NoteIn scheduling, the routing guide only takes into account transportation lanes between sequential locations in the sequence that the routing guide defined before scheduling.

Scheduling of activities is based on the following data:

● TransshipmentTransshipment duration: minimum duration of the goods wait time at the transshipment location

● Departure/shippingDeparture calendar: departure calendar of the leg, if available, or shipping calendar of the start or transshipment location

● Transportation (for each stage of a trip)○ Transportation calendar: you define the transportation calendar for a stage by defining a

transportation lane.○ Transportation duration: if you have not defined a transportation duration for the transportation lane,

the system checks if a value exists for the transportation distance for the transportation lane. It then multiplies this with the average speed of the means of transport used for the leg. If you have not defined any of these values for the transportation lane or have not defined a transportation lane at all, the system estimates the transportation distance on the basis of the geocoordinates of the two locations. It then multiplies this value with the average speed of the means of transport used for the leg.

● Arrival/receiptArrival calendar: Receiving calendar of the transshipment or destination location

For more information, see Results of Scheduling [page 361].


Route Determination

17.7.1 Results of Scheduling

Use

The results of scheduling that you aim for in route determination are defined as listed in the following tables. Here the following applies:

● If route determination is executed automatically in the background, the system only displays the departure and arrival of the trip at header level.

● When you simulate route determination, the system displays all the dates/times and durations listed below.

Features

Results at header level (that is, for the entire trip)

Forward Scheduling

Date/Time Comment

Trip cutoff time (date/time) The scheduling start is the current time, unless you have specified a different value when simulating route determination. The system then calculates the cutoff time of the trip from the scheduling start and the cutoff time of the route by using the later of the two dates/times. The cutoff time of the route is calculated from the order creation time plus the lead time that you have defined for the route on the basis of the request type. The order creation time is the current time, unless you have specified a different value when simulating route determination.

Trip departure (date/time) The departure of the trip is calculated from the cutoff time of the trip, taking into account the departure calendar of the start location. (This is the departure calendar for the relevant leg dependent on the request type, or the shipping calendar of the location.)

Trip arrival (date/time) The arrival of the trip is calculated from the departure of the trip plus the transportation duration of the trip, taking into account the arrival calendar of the destination location (receiving calendar of the location). The transportation duration of the trip is the total of all transportation and transshipment durations for all legs in the trip.

Backward Scheduling


Date/Time Comment

Trip arrival (date/time) The arrival of the trip is calculated from the end that you specified during the simulation of route determination, taking into account the arrival calendar of the destination location.

Trip departure (date/time) The departure of the trip is calculated from the arrival of the trip minus the transportation duration of the trip, taking into account the departure calendar of the start location. If the time calculated is before the cutoff time, the system puts the time back into the past by the relevant lead time.

Results at item level (that is, for the individual legs of the trip)

Date/Time Comment

Transportation duration for the leg The transportation duration of the leg is calculated from the total of the transportation durations between the relevant locations, taking into account the relevant transportation calendar. In the case of transportation durations, they can be estimates.

Transshipment duration for the leg The transshipment duration of the leg is the period of time of the transshipment, taking into account the minimum goods wait time.

Forward Scheduling

Date/Time Comment

Leg departure (date/time) In the case of the first leg, the departure of the leg is the same as the trip departure. For each additional leg, it is calculated from the transshipment end, taking into account the departure calendar of the transshipment location.

Leg arrival (date/time) The arrival of the leg is the same as the departure of the leg plus the transportation duration of the leg, taking into account the arrival calendar of the transshipment location or destination location.

Backward Scheduling


Route Determination

Date/Time Comment

Leg arrival (date/time) For the last leg of the trip (first leg for scheduling), the arrival of the leg is the same as the trip arrival. For each additional leg, it is the transshipment start, taking into account the arrival calendar of the transshipment location.

Leg departure (date/time) The departure of the leg is the same as the arrival of the leg minus the transportation duration of the leg, taking into account the departure calendar of the start location or transshipment location.

More Information

Simulation of Route Determination [page 364]

17.8 Calculation of Transportation Costs

Use

During route determination, the system calculates the transportation costs for each of the trips that are determined. For more information, see Route Determination [page 344].

Features

The system first adds up the following costs to produce a total cost value:

● The penalty costs for premature or delayed delivery, or for premature or delayed pickup for each trip, dependent on the following values:○ Period of time of the earliness or delay○ Priority of the location where the earliness or delay occurred

● The fixed transportation costs for each leg of a trip, dependent on the following values:○ Carrier for the leg (if you have assigned one)○ Means of transport for the leg

● The following costs for two consecutive locations along a leg:○ Distance-dependent costs, dependent on the following values:

○ Carrier for the leg (if you have assigned one)○ Means of transport for the leg○ Transportation distance between the two locations


○ Time-dependent costs○ Carrier for the leg (if you have assigned one)○ Means of transport for the leg○ Transportation duration between the two locations

○ Weight-dependent costs○ Carrier for the leg (if you have assigned one)○ Means of transport for the leg○ Total weight of the products transported between the two locations○ Transportation distance between the two locations

The system requires a cost value or cost factor to calculate these costs. You define the cost value or cost factor in one of the following places:

● In the carrier profile● In the general transportation cost profile● In the relevant transportation lane

The system searches for a cost value or cost factor in these three places in the sequence specified. As soon as it finds an entry, it terminates the search and performs the cost calculation. When calculating transportation costs, the system takes into account hierarchical relationships between means of transport. For more information, see Hierarchical Relationships Between Means of Transport. [page 354]

ExampleDuring route determination, the system has determined a trip with one leg with means of transport M and carrier F. If you have not defined a cost factor for the means of transport M in the transportation cost profile for carrier F but have defined a cost factor for a means of transport superior to M, the system also takes into account this cost factor for M.

NoteYou can use the Business Add-In (BAdI) Cost Determination in Route Determination ( /SCTM/EX_RG_COST) to determine alternative values or to adjust the values found by the routing guide.

17.9 Simulation of Route Determination

Use

You can use this report ( /SCTM/RGINT) to manually simulate route determination in the routing guide. As a basis for the simulation, you choose a strategy and parameter values. All the output tables for the routing guide such as trips, legs, and dangerous goods information are displayed as the result.


Route Determination

Prerequisites

See Route Determination [page 344].

Features

Selection

Strategies

When you choose the Route Information strategy, the system simply determines a trip for your location data. In the case of the other strategies, the system also performs scheduling, a dangerous goods check, a cost calculation and, on the basis of the strategy chosen, it selects and arranges the trips determined.

Request Data

To simulate route determination, you specify the start location and the destination location. If you have already defined a location with an address, you only have to specify the location name. Otherwise, you specify the location using your address data. Furthermore, specify a shipment direction (selection parameter). You use the shipment direction to specify if it is an outbound delivery process or an inbound delivery process.

Selection Parameters

If the strategy you have chosen includes scheduling (see Scheduling [page 359]), you have specified the following:

● Start date/start time if you have chosen forward scheduling● End date/end time if you have chosen backward scheduling

If in the route definition you have defined the lead time of the routes depending on the request types, you can take into account the lock time. To do this, specify the request type and the request date/time if this differs from the current date/time. For more information about scheduling, see Results of Scheduling [page 361].

You optionally enter the following for calculating penalty costs for premature or delayed pickup or delivery:

● Start date/start time if you have chosen backward scheduling● End date/end time if you have chosen forward scheduling

Restrictions

The following table shows how to influence the determination of trips:

Specify Value Exclude Value

Route The system only returns a trip if it is based on this route.

The system only returns a trip if it is based on a different route.

Shipping condition The system only returns a trip if you have defined this shipping condition for the underlying route (see Route [page 346]).

Not possible


Specify Value Exclude Value

Means of transport The system only returns a trip if you have assigned this means of transport to the leg whose destination location is the customer (outbound delivery process) or whose start location is the supplier (inbound delivery process).

The system only returns a trip if you have not assigned this means of transport to the leg whose destination location is the customer (outbound delivery process) or whose start location is the supplier (inbound delivery process).

Carrier The system only returns a trip if you have assigned this carrier to the leg whose destination location is the customer (outbound delivery process) or whose start location is the supplier (inbound delivery process).

The system only returns a trip if you have not assigned this carrier to the leg whose destination location is the customer (outbound delivery process) or whose start location is the supplier (inbound delivery process).

Products

The system takes into account your input about the products to be transported in the following way:

● If your chosen strategy includes a dangerous goods check, the system only displays a trip as the result if the geographical course of the trip agrees with the dangerous goods relevance of the products.

● If you have defined a weight interval for the single request for a route, the system only returns a trip based on this route if the total weight of the request based on the product master lies in this interval.

● If you have defined a volume interval for the single request for a route, the system only returns a trip based on this route if the total volume of the request that is based on the product master lies in this interval.

● If you have defined maximum vales for length, width, and height for the route, the system only displays a trip based on this route as the result of route determination if the values for length, width, and height defined in the product master do not exceed these maximum values.

Control Parameters

You can use the following control parameters to influence the output of system messages in the results area Log: Max. problem class for messages. The system only displays messages that are assigned either to the problem class you have chosen or to a higher one (filter). If you activate buffering, the system can minimize the response times for multiple requests. As a prerequisite, you must not leave the transaction in between requests.

Results

Results: Trip (Header Level)

Results Comment

Rank The system arranges the trips in accordance with the total costs calculated, whereby the completeness of the costs is the sort criterion.


Route Determination

Results Comment

Route The system specifies the underlying route of the trip that is determined. Within cross-docking, this is the cross-docking route that comprises the entire trip. For more information, see Cross-Docking Route [page 349].

Next cross-docking location Within cross-docking, the system displays the first location where transshipment is to occur according to the cross-docking route definition.

Costs The total costs consist of transportation costs and penalty costs. Transportation costs include fixed costs as well as variable costs that are dependent on distance, duration, and/or weight. Both types of cost can be dependent on the choice of means of transport and carrier. Penalty costs include costs for premature delivery, premature pickup, delayed delivery, and delayed pickup.

Times for lock time, departure, and arrival of the trip See Scheduling [page 359].

GTS geography group The system specifies the GTS geography group of the route upon which the trip that is determined is based.

Results: Legs of a Trip (Item Level)

Results Comment

Leg number The system arranges the legs of a trip in the shipment direction.

Route Within cross-docking, the system specifies the route of the leg on which the leg of the trip is based.

Start location, destination location, and stops The value in the Start Location of Leg field is the start location of the request or the loading location of a subsequent leg. The value in the Destination Location of Leg field is the destination location of the request or the unloading location of a previous leg. Along with the start location and destination location of the leg, the stops also include a list of locations served along the leg that you have selected.

Means of transport, carrier, and assignments The system specifies the means of transport and, optionally, a carrier for the leg of the route upon which the leg in the trip that has been determined is based. If more than one carrier is assigned to this means of transport for the leg, the system displays the relevant combinations as assignments of the leg that you have selected (see Route [page 346]).


Results Comment

Costs The total costs or the penalty costs for the trip are the sum of the total costs or penalty costs for all legs in the trip.

Times for departure and arrival See Scheduling [page 359].

Durations for transshipment and transportation See Scheduling [page 359].

Additional Results

Results Comment

Dangerous goods information The system specifies the result of the dangerous goods check for the products that you have specified.

Transit information The system specifies the regions that the transportation covers for the legs of the trips that have been determined.

Log While taking into account the control parameters that you have chosen, the system specifies the messages that have been collected over time.

17.10 Distribution of Master Data

Use

If you want to perform route determination in a distributed system landscape with multiple SAP Supply Chain Management (SAP SCM) systems, you must ensure that all these systems have the same master data. Otherwise, you might receive different results when you call route determination from the different systems. This is particularly important if your planning system (SAP Advanced Planning and Optimization (SAP APO)) and your execution system (Extended Warehouse Management (EWM)) lie in different SCM systems.

As part of route determination, you need to distribute master data in the following cases:

● Route determination is called in SAP Customer Relationship Management (SAP CRM) during the SAP APO availability check for sales orders.

● Route determination is called from an ERP system during the conversion of unchecked deliveries to checked deliveries. Here the call occurs through the relevant SAP APO system too.

● Route determination is called from various EWM systems for outbound delivery orders.


Route Determination

Prerequisites

For the distribution of master data, the following prerequisites must be met:

● You have selected the Realtime Distrib. checkbox in Customizing for SCM Basis under Routing GuideGeneral Settings for Route Determination . In this case, the master data is distributed automatically when you change or create it in your master system.

● You have created and transferred a distribution model. The following steps are necessary to do this:1. Create a distribution model in the master system. To do this, call transaction BD64. Enter the following

BAPIs:○ Route->SaveReplicaMulti○ TSPProfile->TSPProfileSavereplica○ TransportCostProfil->TransportCostsSaveReplica○ Zone->SavereplicaMulti

2. In the model view, generate the partner profiles that you have created. To do so, choose EnvironmentGenerate Partner Profiles .

3. Transfer the distribution model from the master system to the other systems. To do so, choose EditModel View Distribute in the distribution model.

Activities

Distribution can occur automatically or you can trigger it manually. If you want to trigger the distribution manually, choose the appropriate menu option in the following transactions:

● Maintain Route (transaction /SCTM/ROUTE)● Maintain Zones for Routes (transaction /SCTM/ZONE)● Carrier Profile for the Routing Guide (transaction /SCTM/TSPP)

Alternatively, you can call the distribution program using transaction /SCTM/RG_MD_DISTRI.


18 EH&S Services in SCM Basis

Use

The functions in EH&S Services support you with the safe handling and storage of hazardous substances and with the transport of dangerous goods in accordance with regulations.

Features

The following functions are available in EH&S Services :

● In phrase management [page 370] you can enter texts that have a standard character in the form of phrases with little effort required for entry and translation.

● In the hazardous substance master [page 371] you can enter all important data relating to hazardous substances, for example, data that you require for hazardous substance checks prior to storage.

● In the dangerous goods management [page 371] you can enter all the important data for dangerous goods. With this data, you can run dangerous goods checks, for example, or print dangerous goods data on a delivery note.

18.1 Phrase Management

Use

This function supports the central management and translation of text modules called phrases.

You can use phrases to perform the following language-independent activities:

● Record information about hazardous substances in the hazardous substance master , for example, R and S phrases

● Output dangerous goods texts on dangerous goods documents

Phrases are managed in phrase libraries, from which you select one library for editing data.

Features

For more information about the individual functions of phrase management , see the documentation for mySAP ERP 2005 inSAPHelp Portal under SAPERP Central Component Logistics Environment, Health and Safety (EHS) Basic Data and Tools (EHS-BD) Phrase Management (EHS-BD-PHR) .


EH&S Services in SCM Basis

The following functions are not supported in phrase management in EH&S Services :

● Use of phrases in the value assignment of specifications and in EH&S reports● Import and export of phrases● Phrase merging● Phrase combining● Master data matchup● Data exchange via ALE (sending)

Activities

You can access the phrase management functions on the SAP Easy Access mySAP Supply Chain Management screen in theSAPmenu under SCMBasis EH&S Services Phrase Management .

18.2 Hazardous Substance Master

Use

With this function, you create and edit hazardous substance master records.

Features

For more information about the individual functions of the Hazardous Substance Master , see the documentation for mySAP ERP 2005 inSAPHelp Portal under SAPERP Central Component LogisticsEnvironment, Health and Safety (EHS) Hazardous Substance Management (EHS-HSM) Hazardous Substance Master . The following functions are not supported in the hazardous substance master in EH&S Services :

● Filling of the hazardous substance master from specification management● Distribution of the hazardous substance master via Application Link Enabling ( ALE ) from the system

containing EH&S Services to other systems

An import of data from a central ERP system into the hazardous substance master in EH&S Services via ALE is possible, however. You can also create hazardous substance master data manually in the hazardous substance master in EH&S Services .

SCM BasisEH&S Services in SCM Basis P U B L I C 371

Activities

To edit hazardous substance master data, on the SAP Easy Access mySAP Supply Chain Management screen in theSAPmenu choose SCMBasis EH&S Services Hazardous Substance Management Hazardous Substance Master Edit Hazardous Substance Master .

18.3 Dangerous Goods Management

Use

With this function, you create and edit dangerous goods master records. The system uses the data in the dangerous goods master records, for example, in the dangerous goods checks and for printing dangerous goods documents.

Features

For more information about the individual functions of Dangerous Goods Management , see theSAPHelp Portal under SAPERP SAPERP Central Component Release 6.0 SAP ERP Central Component LogisticsEH&S - Environment, Health and Safety EH&S Dangerous Goods Management .

The following functions are not supported in Dangerous Goods Management in EH&S Services :

● Dangerous goods basic data● Filling● Distribution (sending)● Template and one-time material processing● DG exceptions● Product release and dynamic classifications● Dynamic textpattern handling● Data record split from the dangerous goods master screen● Printing the dangerous goods master● Packaging data

An import of data from other systems into the dangerous goods master in EH&S Services via ALE is possible, however. You can also create dangerous goods data manually in the dangerous goods master in EH&S Services .


EH&S Services in SCM Basis

Activities

You can access the functions in Dangerous Goods Management on the SAP Easy Access screen in theSAPmenu under SCMBasis EH&S Services Dangerous Goods Management .

SCM BasisEH&S Services in SCM Basis P U B L I C 373

19 Roles in SAP SCM Basis

19.1 Transport Load Builder (TLB) Planner

Technical name: SAP_SCM_SNP_TLB_PLN

Tasks

You can use this role to perform all the activities you require for planning with the Transport Load Builder (TLB).

Activities in Supply Network Planning

You can display and edit data in the following screens in Supply Network Planning (SNP):

Screen Mode

Interactive Supply Network Planning (all Books) Edit

Maintain Selection Assignment Edit

Transport Load Builder (TLB) - interactive Edit

Transport Load Builder (TLB) Edit

Define Transport Load Builder (TLB) Profiles Edit

Transportation Lane Edit

Application Logs Edit

19.2 Roles for Master Data and Integration

Purpose

This section contains information about the following cross-application roles:

● SCM Master Data Processing [page 375]● SCM Integration [page 375]


Roles in SAP SCM Basis

19.2.1 SCM Master Data Processing

Technical name: SAP_SCM_MD

Tasks

The role for SCM master data processing contains all authorization objects necessary for the creation, changing, and deletion of master data in the applications of SAP Supply Chain Management ( SAP SCM ). The role is valid for all process roles.

The instance of this role, that is, the assignment of the authorization and menus, depends on the tasks of the relevant role holder. The role holder acquires the role in addition to the process role in each case.

The role is assigned per employee by the person responsible and is valid for all process roles that the employee has.

19.2.2 SCM Integration

Technical name: SAP_SCM_INTEGRATION

Tasks

This role contains authorizations for users who are logged on in the SCM system via an RFCconnection from the ERP system (background users).

The integration of SAP SCM with an ERP system (SAP R/3, SAP ERP Central Component (SAP ECC), or DIMP system) via APO Core Interface (CIF) requires at least one RFC connection. The logon data for the background user in the target system can be entered in the RFC connection. The purpose of this role is to provide the background user in SAP SCM with minimum authorizations to prevent the abuse of access via an RFC connection.

For security reasons, we recommend that the background users for CIF integration have the user type Communication only.

NoteThis role is not sufficient for users who want to perform a global ATP check in SAP SCM. For more information, see the documentation for the global ATP check.

SCM BasisRoles in SAP SCM Basis P U B L I C 375

20 Archiving in SCM Basis

20.1 Archiving in Execution (SCM-ECT)

Purpose

The Execution component contains the Logistics Inventory Management Engine [page 376] (LIME) archiving objects.

20.1.1 Archiving in LIME (SCM-ECT-LIME)

Use

Archiving in Logistics Inventory Management Engine (LIME) is composed of the following objects:

● Prima Nota documents and the New Log Data (LIME_NLOG) [page 378]● LIME Physical Inventory documents (LIME_PI) [page 376]

20.1.1.1 Archiving Physical Inventory Documents (SCM-ECT-LIME-PI)

Definition

You use the archiving object LIME_PI to write the LIME physical inventory tables in archive files.

Use

You can archive physical inventory documents that SAP Extended Warehouse Management (SAP EWM) saved a certain number of days ago. You can also simultaneously archive physical inventory documents for multiple warehouse numbers.

For test purposes, you can display a list of all the physical inventory documents to be archived and deleted before archiving them.


Archiving in SCM Basis

Structure

Tables

SAP EWM uses the archiving object LIME_PI to archive data from the following tables listed in the following table:

Table Table Name

/LIME/PI_DOC_IT Table of Physical Inventory Document Items

/LIME/PI_DOC_SER Serial Numbers for Physical Inventory Document Items

/LIME/PI_DOC_TB Quantities for Physical Inventory Document Items

/LIME/PI_LOGHEAD Log Table for Header Data of a Physical Inventory Document

/LIME/PI_LOGITEM Log Table for Item Data of a Physical Inventory Document

/LIME/PI_PAR_BIZ Physical Inventory Document Business Key Item Object

/LIME/PI_IT_BIZ Physical Inventory Document Business Key Parent Object

Programs

The programs listed in the following table are delivered for the archiving object LIME_PI:

Program Function

/LIME/PI_ARCH_WR Write

/LIME/PI_ARCH_DL Delete

/LIME/PI_ARCH_RL Reload

Variant Settings for Writing

In the variant of the write program, specify the following selection criteria for the physical inventory documents:

● Document YearYou can enter the archiving year of a physical inventory document.

● Generate Archive FileIf you choose this option, the write program of the archiving object runs in production mode.

● Delete Program in Test ModeIf you select this checkbox, the delete program of the archiving object is started with the test mode variant that was specified in the archiving-object-specific Customizing. No data is deleted from the database, because deletion is only simulated. The program generates statistics about the table entries that would be deleted from the database in the production mode.If you do not select this checkbox, the delete program is started with the production mode variant that was specified in the archiving-object-specific Customizing.

SCM BasisArchiving in SCM Basis P U B L I C 377

The checkbox only appears on the selection screen if in archiving-object-specific Customizing under Settings for Delete Program you have checked the option Start Automatically.

● Packet SizeYou can define the maximum number of objects per archive file. The default value is 100.

In the processing options, specify whether SAP EWM is to start the program in test mode or production mode.

For more information about maintaining variants for archiving jobs, see the documentation for archiving with the Archive Development Kit (ADK) in the SAP NetWeaver library.

NoteThe runtime of the write program depends on the number of physical inventory documents to be archived and on the general system performance.

Integration

Display Function for Archived Physical Inventory Documents

You can use the field catalog SAP_LIME_PI and the archive information structure SAP_LIME_PI to access archived physical inventory documents using the archive information system.

For more information, see the documentation for the Archive Information System in the SAP NetWeaver library.

20.1.1.2 Archiving of New Log Data (SCM-ECT-LIME-NLOG)

Definition

The Logistics Inventory Management Engine (LIME) New Log ( LIME_NLOG) archiving object archives the incoming LIME documents with Prima Nota information and LIME NLOG data.

NoteThis archiving object is a combination of the former LIME_PN archiving object and the new LIME_NLOG data.

Use

You can archive new logs that LIME saved a certain number of days in the past.



Structure

Tables

When you use the archiving object LIME_NLOG, the system archives data from the tables listed in the following table:

Table Table Name

/LIME/LOG_HEAD Log table that contains the header data of the Prima Nota document.

/LIME/COLL_PN Table for the connection between collections and the Prima Nota documents.

/LIME/NLOG_QUAN Log table that contains the stock change quantities.

/LIME/NLOG_SERIAL Log table that contains the hierarchy of the serial numbers.

/LIME/NLOG_TREE Log table that contains the LIME hierarchy.

/LIME/PN_ITEM Table that contains each item of the Prima Nota document.

/LIME/PN_ITEM_TB Table that contains a list of parameters, quantities, serial numbers and accounting parameters

/LIME/PN_SERIAL Table that contains the serial numbers of the Prima Nota documents.

/LIME/ARCH_IDX Table for the connection between the log and the archiving key.

Programs

The programs listed in the following table are available for archiving object LIME_NLOG:

Program Function

/LIME/ARCH_WR Write

/LIME/ARCH_DL Delete

/LIME/ARCH_RL Reload

/LIME/QUERY_PN Function module to read log information in the archive

This archiving object does not store the business key of the LIME object (locations, handling units, stock items or serial numbers). They are kept in the corresponding shadow tables and are not deleted from the LIME database even if the LIME object is removed from LIME.

Variant Settings for Writing

SCM BasisArchiving in SCM Basis P U B L I C 379

You can use the following variant settings for the new logs you want to archive:

● Minimum number of days● End date

The following conditions, in addition to the internal timestamp criteria for LIME documents, must be fulfilled before the LIME document can be archived:

● Reload stock quantityAt least one entry with a new log type or a calculated hist_stock value must be available for a combination of each stock item and location or stock item and handling unit in the /LIME/NLOG_QUAN table. This entry is used as a basis to calculate the historical stock level and for the recovery process.

● Reload LIME hierarchyAn entry in the /LIME/NLOG_TREE table must remain for all combinations of GUID and GUID_PARENT.

Integration

Display Function for Archived New Logs

You can use the field catalog SAP_LIME_NLOG and the archive information structure SAP_LIME_NLOG to access archived new logs using the archive information system:

More Information

Archiving documentation in the SAP NetWeaver library



Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up.The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example CodeAny software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

SCM BasisImportant Disclaimers and Legal Information P U B L I C 381

www.sap.com/contactsap

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

Please see https://www.sap.com/about/legal/trademark.html for additional trademark information and notices.

THE BEST RUN

https://www.sap.com/about/legal/trademark.html