Sap Retail

6$35HWDLO

5 6 ,  3 / ( +

5HOHDVH%

®

6$35HWDLO

6$3$*

&RS\ULJKW © Copyright 1998 SAP AG. All rights reserved. No part of this brochure may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. SAP AG further does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within these materials. SAP AG shall not be liable for any special, indirect, incidental, or consequential damages, including without limitation, lost revenues or lost profits, which may result from the use of these materials. The information in this documentation is subject to change without notice and does not represent a commitment on the part of SAP AG for the future. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL® and SQL-Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. OSF/Motif® is a registered trademark of Open Software Foundation. ORACLE® is a registered trademark of ORACLE Corporation, California, USA. INFORMIX®-OnLine IRU6$3 is a registered trademark of Informix Software Incorporated. UNIX® and X/Open® are registered trademarks of SCO Santa Cruz Operation. ADABAS® is a registered trademark of Software AG. SAP®, R/2®, R/3®, RIVA®, ABAP/4®, SAP ArchiveLink®, SAPaccess®, SAPmail®, SAPoffice®, SAP-EDI®, R/3 Retail®, SAP EarlyWatch®, SAP Business Workflow®, ALE/WEB, Team SAP, BAPI, Management Cockpit are registered or unregistered trademarks of SAP AG.

,FRQV ,FRQ

0HDQLQJ Caution Example

Note



-XQH

6$3$*

6$35HWDLO

&RQWHQWV 6$35HWDLO   %DVLF3ULQFLSOHV   6$35HWDLO2YHUYLHZ  Integration of SAP Retail in the R/3 Environment .................................................................... 28 Areas of Application of SAP Retail ........................................................................................... 29 Distributed Retailing ................................................................................................................. 30 7KLV'RFXPHQWDWLRQ   This Documentation: Link to Corresponding General Documentation..................................... 32 2UJDQL]DWLRQDO6WUXFWXUH  Organizational Structure: Example........................................................................................... 35 Organizational Structure: Example Graphic ............................................................................. 36 Organizational Structure: Corporate Group.............................................................................. 37 Organizational Structure: Purchasing Organization ................................................................. 38 Organizational Structure: Purchasing Area .............................................................................. 40 Organizational Structure: Purchasing Group............................................................................ 41 Organizational Structure: Company Code................................................................................ 42 Organizational Structure: Sales Organization .......................................................................... 43 Organizational Structure: Distribution Channel ........................................................................ 44 Organizational Structure: Distribution Chain ............................................................................ 45 Organizational Structure: Division ............................................................................................ 46 Organizational Structure: Sales Area ....................................................................................... 47 Organizational Structure: Sales Office ..................................................................................... 48 Organizational Structure: Sales Group..................................................................................... 49 Organizational Structure: Site .................................................................................................. 50 Organizational Structure: Site Group ....................................................................................... 51 Organizational Structure: Customer ......................................................................................... 52 Organizational Structure: Vendor ............................................................................................. 53 Organizational Structure: Stock Planner Group ....................................................................... 54 Organizational Structure: Storage Location ............................................................................. 55 Organizational Structure: Department, Receiving Point and Unloading Point ......................... 56 Organizational Structure: Sales Department............................................................................ 58 %DFNJURXQG3URFHVVLQJ   Background Processing: Site ................................................................................................... 60 Background Processing: Setting Central Block for Sites .................................................... 61 Background Processing: Conditions ........................................................................................ 62 Background Processing: Generating a Worklist of Changed Conditions............................ 63 Background Processing: Adjusting Documents after Condition Changes .......................... 64 Background Processing: Assortment ....................................................................................... 65 Background Processing: Value-Only Article Listing............................................................ 66 Background Processing: Change Assortment Automatically Following Master Data Changes .............................................................................................................................. 67 Background Processing: Assortment List................................................................................. 68 Background Processing: Initializing Outbound Assortment List.......................................... 69 Background Processing: Outbound Processing for Assortment List .................................. 70 Background Processing: Promotion ......................................................................................... 71

-XQH



6$35HWDLO

6$3$*

Background Processing: Message Bundling....................................................................... 72 Background Processing: Pricing .............................................................................................. 73 Background Processing: Pricing Worklist Based on Changes to Factors Relevant to Pricing.................................................................................................................................. 74 Background Processing: Requirements Planning.................................................................... 75 Background Processing: Forecast per Period Indicator...................................................... 76 Background Processing: Total Planning per Site................................................................ 77 Background Processing: Allocation.......................................................................................... 78 Background Processing: Message Bundling....................................................................... 79 Background Processing: Ordering ........................................................................................... 80 Background Processing: Adjusting Purchasing Documents after Condition Changes ....... 81 Background Processing: Invoice Verification ........................................................................... 82 Background Processing: Immediate Invoice Verification or Periodic Invoice Verification .. 83 Background Processing: Preparing the Advance Return for Tax on Sales/Purchases for Parked Documents.............................................................................................................. 84 Background Processing: Subsequent (End-of-Period) Settlement .......................................... 85 Background Processing: Settling Rebate Arrangements.................................................... 86 Background Processing: Extension of Periodic Rebate Arrangements.............................. 87 Background Processing: Compilation of Statistics and Retroactive Updating of Vendor Business Volume................................................................................................................. 88 Background Processing: Inventory Management .................................................................... 89 Background Processing: Sales Price Revaluation.............................................................. 90 Background Processing: Shipping and Transportation ............................................................ 91 Background Processing: Replenishment for Fixed Bins ..................................................... 92 Background Processing: Replenishment ................................................................................. 93 Background Processing: Forecast Weighting Factors ........................................................ 94 Background Processing: Auto-Replenishment ................................................................... 95 Background Processing: POS Interface................................................................................... 96 Background Processing: Initializing Outbound Processing................................................. 97 Background Processing: Periodic Outbound Processing for Stores................................... 98 Background Processing: Repeating Terminated/Buffered POS Inbound Processing ........ 99 Background Processing: Repeating Unsuccessful POS Inbound Processing.................. 100 Background Processing: Information and Planning System .................................................. 101 %XVLQHVV3URFHVVHV  Processes at Headquarters .................................................................................................... 103 Processes in Distribution Centers .......................................................................................... 106 Processes in Stores................................................................................................................ 108 Processes in Sales Offices..................................................................................................... 110 0DVWHU'DWD   6LWH   Functions ................................................................................................................................ 114 Site: Distribution Chains and Site Categories ................................................................... 115 Site: Number Assignment ................................................................................................. 116 Site: Site Profiles ............................................................................................................... 117 Site: Franchisee ................................................................................................................ 118 Site: Data Sets and Data Maintenance Levels ................................................................. 119 Site: Reference Site .......................................................................................................... 121 Site: Definitions ................................................................................................................. 123



-XQH

6$3$*

6$35HWDLO

Site: Currency Changeover ............................................................................................... 125 Site: Groups ...................................................................................................................... 126 Site: Site Layout ................................................................................................................ 127 Site: Use of Industry Master Data ..................................................................................... 129 Site: Site Discontinuation .................................................................................................. 130 Business Processes ............................................................................................................... 131 Site Processing ................................................................................................................. 132 Site Processing: Procedure ......................................................................................... 134 Customer Processing for Site: Procedure.................................................................... 136 Additional Site Data: Procedure................................................................................... 137 Vendor Processing for Site: Procedure........................................................................ 139 Site Block .......................................................................................................................... 140 Setting a General Site Block: Procedure ..................................................................... 142 Blocking a Site in Its Capacity as a Customer: Procedure .......................................... 143 Blocking a Site in Its Capacity as a Vendor: Procedure .............................................. 145 9HQGRU  Functions ................................................................................................................................ 150 Vendor: Vendor Categories............................................................................................... 151 Vendor: Number Assignment ............................................................................................ 152 Vendor: Account Group..................................................................................................... 153 Vendor: Vendor Sub-Range .............................................................................................. 154 Vendor: Data Retention Levels ......................................................................................... 155 Vendor: Business Partners ............................................................................................... 157 Vendor: Partner Functions in the Standard System.......................................................... 158 Vendor: Relationship Between Account Group and Partner Function.............................. 160 Vendor: Partner Determination Procedures in the Standard System ............................... 162 Vendor: Contact Persons .................................................................................................. 164 Vendor: Vendor Characteristic Values .............................................................................. 165 Vendor: Forwarding Changes ........................................................................................... 167 Vendor: Customizing Settings...................................................................................... 168 Vendor: Data Retention Levels and the Next-Level Principle...................................... 169 Vendor: Data segments ............................................................................................... 171 Vendor: Determining the Relevant Purchasing Info Record ........................................ 173 Vendor: Determining the Relevant Article Master Segments ...................................... 174 Vendor: SAP Blocking Mechanism .............................................................................. 176 Vendor: Planning Changes ............................................................................................... 177 Vendor: Returns with a Delivery........................................................................................ 178 Vendor: Rack Jobber......................................................................................................... 179 Rack Jobber: Master Data ........................................................................................... 180 Rack Jobber: Initial Supply of Goods to the Store ....................................................... 181 Rack Jobber: Selling Merchandise in the Stores ......................................................... 182 Rack Jobber: Subsequent Supply................................................................................ 183 Rack Jobber: Goods Receipt ....................................................................................... 184 Rack Jobber: Settlement with the Rack Jobber........................................................... 185 Rack Jobber: Processing Returns ............................................................................... 186

-XQH



6$35HWDLO

6$3$*

Rack Jobber: Other Goods Movements....................................................................... 187 Rack Jobber: Physical Inventory.................................................................................. 188 Rack Jobber: Transferring Goods to Your Own Stock................................................. 189 Vendor Hierarchy .............................................................................................................. 190 About Vendor Hierarchies ............................................................................................ 191 Using Vendor Hierarchy categories ............................................................................. 193 Building a Vendor Hierarchy ........................................................................................ 194 Creating a Vendor Hierarchy Node: Procedure...................................................... 196 Assigning a Node Within a Vendor Hierarchy: Procedure...................................... 197 Assigning a Vendor to a Node in a Vendor Hierarchy: Procedure ......................... 198 Defining Partners as Nodes in a Vendor Hierarchy................................................ 199 Using Organizational Data in a Vendor Hierarchy.................................................. 200 Using Validity Periods in a Vendor Hierarchy......................................................... 201 Using a Vendor Hierarchy During Purchase Order Processing................................... 202 Partner Determination for Vendor Hierarchy Nodes............................................... 203 Displaying the Vendor Hierarchy Path in Purchasing Documents: Procedure....... 205 Vendor Hierarchies and Price Determination ......................................................... 206 Maintaining a Vendor Hierarchy................................................................................... 207 Adding a New Vendor Hierarchy Node : Procedure ............................................... 208 Changing the Assignment of a Vendor Hierarchy Node: Procedure ...................... 209 Changing Validity Data in a Vendor Hierarchy: Procedure..................................... 211 Deleting the Assignment of a Vendor Hierarchy Node: Procedure ........................ 212 Updating a Vendor Hierarchy: Procedure............................................................... 213 Analyzing Errors During Vendor Hierarchy Maintenance: Procedure .................... 214 Business Processes ............................................................................................................... 215 Vendor Processing ............................................................................................................ 216 Creating a Vendor: Procedure ..................................................................................... 217 Creating Planned Changes in the Vendor Master (General Data and Purchasing Data): Procedure..................................................................................................................... 221 Activating Planned Changes Online in the Vendor Master : Procedure ...................... 222 Displaying Accounts Payable Changes to a Vendor: Procedure................................. 223 Displaying Accounts Payable Changes to Several Vendors: Procedure..................... 224 Displaying Planned Account Changes for a Vendor: Procedure ................................. 225 Vendor Block ..................................................................................................................... 226 Vendor: Setting a Purchasing/Posting Block: Procedure............................................. 228 Vendor: Setting a Purchasing Block for Sites and/or Vendor Sub-Ranges: Procedure229 Vendor: Setting a Payment Block for Specific Company Codes: Procedure............... 230 Vendor: Setting a Block for Quality Reasons in the Vendor Master: Procedure ......... 231 $UWLFOH0DVWHU'DWD   Functions ................................................................................................................................ 234 Articles: Article Master Records ........................................................................................ 235 Articles: Basic Data ...................................................................................................... 237 Articles: Listing Data .................................................................................................... 239 Articles: Purchasing Data............................................................................................. 241 Articles: Sales Data...................................................................................................... 243



-XQH

6$3$*

6$35HWDLO

Articles: Logistics Data for Distribution Centers........................................................... 245 Articles: Warehouse Management Data ................................................................. 246 Articles: Logistics Data for Stores ................................................................................ 247 Articles: When Is Logistics Data Differently Maintained? ............................................ 249 Articles: Default Valuation Types in Accounting .......................................................... 251 Articles: POS Data ....................................................................................................... 252 Articles: Article Numbers ................................................................................................... 253 Articles: Organizational Levels .......................................................................................... 254 Articles: User Department and Organizational Level................................................... 256 Articles: Identically Maintained Organizational Levels................................................. 257 Articles: Differently Maintained Organizational Levels................................................. 260 Articles: Merchandise Categories ..................................................................................... 263 Articles: Article Types........................................................................................................ 264 Articles: Empties .......................................................................................................... 265 Articles: Assigning Empties to a Full Product and Unit........................................... 266 Articles: Article Categories ................................................................................................ 267 Articles: Single Articles................................................................................................. 269 Articles: Generic Articles and Variants......................................................................... 270 Articles: Sets ................................................................................................................ 272 Articles: Displays.......................................................................................................... 273 Articles: Prepacks ........................................................................................................ 274 Articles: Merchandise Category Articles ...................................................................... 275 Articles: Hierarchy Articles ........................................................................................... 276 Articles: Group Articles................................................................................................. 277 Articles: Merchandise Category Reference Articles .................................................... 278 Articles: EAN Management ............................................................................................... 279 Articles: Taxes................................................................................................................... 282 Articles: Reference Data ................................................................................................... 283 Articles: Reference Articles .......................................................................................... 284 Articles: Reference Data from the Generic Article ....................................................... 285 Articles: Reference Sites.............................................................................................. 286 Articles: Reference Data from the Same Article .......................................................... 287 Articles: Reference Data from Customizing ................................................................. 288 Articles: Reference Data from Profiles......................................................................... 289 Articles: Reference Data from a Vendor Master Record ............................................. 290 Articles: Reference Data for Seasonal Articles ............................................................ 291 Articles: Reference Data from Constants..................................................................... 292 Articles: Transfer and Distribution of Article Master Data ................................................. 293 Articles: IDoc Types for Distributing Article Master Data ............................................. 294 Articles: IDoc Type ARTMAS01 for Pure Article Master Data ................................ 296 Articles: Online Functions and Their Support in ALE................................................... 297 Articles: Number Assignment in ALE...................................................................... 298 Articles: User Departments in ALE ......................................................................... 299 Articles: Article Categories in ALE .......................................................................... 300 Articles: Reference Data in ALE ............................................................................. 301

-XQH



6$35HWDLO

6$3$*

Articles: Checks in ALE........................................................................................... 302 Articles: Field Selection in ALE............................................................................... 303 Articles: Error Handling ................................................................................................ 304 Articles: Article Discontinuation......................................................................................... 305 Article Discontinuation: Procedure............................................................................... 307 Business Processes ............................................................................................................... 309 Article Processing.............................................................................................................. 310 Article Processing: Procedure...................................................................................... 311 Article Block....................................................................................................................... 315 Blocking an Article: Procedure..................................................................................... 316 0HUFKDQGLVH&DWHJRU\   Functions ................................................................................................................................ 320 Merchandise Category: Merchandise Category Hierarchy ............................................... 321 Merchandise Category: Value-Only Article Categories..................................................... 323 Merchandise Category: In the Context of the Classification System ................................ 324 Merchandise Category: Fields Relevant to Creating a Merchandise Category ................ 327 Merchandise Category: Possibilities for and Consequences of Changes ........................ 330 Merchandise Category: Reclassification of Articles and Merchandise Categories........... 331 Merchandise Category: Transferring Data From a Non-SAP System or Legacy System 334 Business Processes ............................................................................................................... 335 Characteristics Processing................................................................................................ 336 Creating a Characteristic: Procedure........................................................................... 337 Merchandise Category Processing ................................................................................... 339 Creating a Characteristics Profile: Procedure.............................................................. 341 Assigning Characteristics to Merchandise Category Objects: Procedure ................... 342 Creating a Merchandise Category: Procedure ............................................................ 343 Creating a Merchandise Category Hierarchy Level: Procedure .................................. 345 Creating Assignments to the Merchandise Category: Procedure................................ 346 Assigning a Merchandise Category Hierarchy Level: Procedure ................................ 347 Article and Merchandise Category Reclassification.......................................................... 348 Creating a Reclassification Version for Merchandise Categories/Articles: Procedure 350 Activating a Reclassification Version for Merchandise Categories/Articles: Procedure351 Deleting a Reclassification Version for Merchandise Categories/Articles: Procedure 352 &RQGLWLRQV   Functions ................................................................................................................................ 355 Conditions: Interchanging Conditions Between Different Systems................................... 356 Conditions: Purpose of VAKEY in Condition IDoc Segment E1KOMG ....................... 358 Conditions: Transferring Conditions from Orders ............................................................. 359 Business Processes ............................................................................................................... 361 Condition Processing (Vendor) ......................................................................................... 362 Creating a Condition: Procedure.................................................................................. 363 Creating Conditions With User-Defined Condition Types: Procedure ......................... 364 Defining Vendor Prices: Procedure.............................................................................. 365 Making Global Pricing Changes: Procedure ................................................................ 367 &XVWRPHU   Functions ................................................................................................................................ 370



-XQH

6$3$*

6$35HWDLO

Customer: Customers and Business Partners .................................................................. 371 Customer: Customer Master Records............................................................................... 372 Customer: Partner Functions ............................................................................................ 373 Customer: Account Groups ............................................................................................... 375 Customer: Structure .......................................................................................................... 376 Customer: Data ................................................................................................................. 378 Customer: Number Assignment ........................................................................................ 380 Customer: One-Time Customers ...................................................................................... 381 Customer: Help in Creating a New Master Record........................................................... 383 Customer: Master Data Grouping ..................................................................................... 384 Business Processes ............................................................................................................... 385 Customer Processing ........................................................................................................ 386 Creating a Customer (Sold-To Party): Procedure........................................................ 387 Customer Block ................................................................................................................. 389 Customer: Setting Posting and Sales and Distribution Blocks: Procedure.................. 391 Customer: Setting a Payment Block for a Single Company Code: Procedure ............ 393 &ODVVLILFDWLRQ   Functions ................................................................................................................................ 396 Classification: Class Hierarchies....................................................................................... 397 Business Processes ............................................................................................................... 398 Characteristics Processing................................................................................................ 399 Creating a Characteristic: Procedure........................................................................... 400 Reclassification of Objects in Hierarchical Class Types ................................................... 402 Creating a Reclassification Version for Objects in Hierarchical Class Types: Procedure404 Activating a Reclassification Version for Objects in Hierarchical Class Types: Procedure405 Deleting a Reclassification Version for Objects in Hierarchical Class Types: Procedure406 6WUDWHJLF6DOHV   $VVRUWPHQW   Functions ................................................................................................................................ 411 Assortment: Assortment Management.............................................................................. 412 Assortment: Assortment Modules ..................................................................................... 415 Assortment: Listing Conditions.......................................................................................... 418 Assortment: Listing Windows ............................................................................................ 419 Assortment: Listing Procedures ........................................................................................ 420 Assortment: Subsequent Listing ....................................................................................... 421 Assortment: Removing an Article From Assortments ....................................................... 422 Assortment: Automatic Assortment Correction ................................................................. 424 Assortment: Analytical Reports ......................................................................................... 425 Assortment: Assortment List ............................................................................................. 427 Assortment: Assortment List Message Generation ..................................................... 428 Assortment: Assortment List Version Management..................................................... 433 Business Processes ............................................................................................................... 435 Assortment Module Maintenance...................................................................................... 436 Assortment Module Maintenance: Procedure.............................................................. 437 Assortment Module Assignment Maintenance.................................................................. 438 Assortment Module Assignment Maintenance: Procedure.......................................... 439

-XQH



6$35HWDLO

6$3$*

Assortment Processing ..................................................................................................... 441 Assortment Processing: Procedure ............................................................................. 442 Assortment User Assignment Maintenance ...................................................................... 443 Assortment User Assignment Maintenance: Procedure .............................................. 444 Assortment List Generation............................................................................................... 445 Manually Requesting an Assortment List: Procedure.................................................. 447 Automatically Generating an Assortment List: Procedure ........................................... 448 Assortment List Status Reorganization: Procedure ..................................................... 449 Deleting an Assortment List: Procedure ...................................................................... 450 Displaying the Assortment List Cycle: Procedure........................................................ 451 3URGXFW&DWDORJ   Functions ................................................................................................................................ 455 Product Catalog: Basic Data ............................................................................................. 456 Product Catalog: Layout.................................................................................................... 457 Product Catalog: Generic Articles, Variants, and Sets ..................................................... 458 Product Catalog: Article Selection..................................................................................... 460 Product Catalog: Text........................................................................................................ 461 Product Catalog: Multimedia Objects................................................................................ 462 Product Catalog: Status and Export Information............................................................... 463 Product Catalog: Internet Product Catalog and Internet Online Store.............................. 464 Business Processes ............................................................................................................... 466 Product Catalog Processing.............................................................................................. 467 Product Catalog Processing: Procedure...................................................................... 468 6HDVRQ   Functions ................................................................................................................................ 473 Season: Markdown Planning ............................................................................................ 474 Season: Markdown Rules ............................................................................................ 475 Season: Markdown Types ........................................................................................... 476 Season: Markdown Plans ............................................................................................ 477 Season: Activating Price Phases and Monitoring the Results ..................................... 478 Seasons: Currency Changeover for Markdown Planning............................................ 479 Business Processes ............................................................................................................... 480 Markdown Planning........................................................................................................... 481 Markdown Planning: Procedure................................................................................... 482 Processing Markdown Rules............................................................................................. 484 Markdown Rule Processing: Procedure....................................................................... 485 3URPRWLRQ   Functions ................................................................................................................................ 489 Promotion: Basic Data....................................................................................................... 490 Promotion: Assigning Articles to a Promotion ................................................................... 491 Changing Quantities for Generic Articles and Variants ............................................... 492 Promotion: Assortment Modules and Store Groups ......................................................... 493 Promotion: Conditions and Agreements ........................................................................... 494 Promotion: Validity Periods (Retail and Wholesale) ......................................................... 495 Promotion: Status.............................................................................................................. 498 Promotion: Subsequent Processing.................................................................................. 500



-XQH

6$3$*

6$35HWDLO

Promotion: Supply Source Determination ......................................................................... 501 Promotion: Split Valuation for Promotion Merchandise .................................................... 502 Promotion: How Split Valuation Is Controlled .............................................................. 503 Example Using Valuation Categories and Types ................................................... 504 Promotion: Split Valuation and Inventory Management............................................... 505 Split Valuation Example.......................................................................................... 506 Promotion: Split Valuation and Revenue Posting ........................................................ 507 Promotion: Announcement................................................................................................ 508 Promotion: Replenishment Planning................................................................................. 510 Promotion: Product Catalog Planning ............................................................................... 511 Product Catalog Planning Example ............................................................................. 513 Promotion: Displaying Data for Promotions ...................................................................... 514 Promotions: Currency Changeover................................................................................... 515 Business Processes ............................................................................................................... 516 Promotion Processing ....................................................................................................... 517 Creating a Promotion: Procedure ................................................................................ 519 3ULFLQJ  Functions ................................................................................................................................ 526 Pricing: What Pricing Does................................................................................................ 527 Pricing: Planned Markups ................................................................................................. 529 Pricing: Price Points .......................................................................................................... 530 Pricing: Currency............................................................................................................... 531 Pricing: Conversion to the New European Currency (Euro) ............................................. 532 Pricing: Supply Source Determination .............................................................................. 534 Pricing: Calculation Schema ............................................................................................. 535 Pricing: Calculating Prices ........................................................................................... 537 Retail Price.............................................................................................................. 541 Gross Margin .......................................................................................................... 542 Actual Markup ......................................................................................................... 543 Gross Sales Price ................................................................................................... 544 Pricing: Calculating Prices for Site Groups .................................................................. 545 Pricing: Two-Step Calculation for Stores ..................................................................... 546 Pricing: Sales Price Calculation for Generic Articles and Variants .............................. 548 Pricing: Promotions Involving Variant Pricing .............................................................. 550 Pricing: Pricing Overview Screen................................................................................. 551 Pricing: Pricing Documents .......................................................................................... 552 Pricing: Cancelling Price Changes............................................................................... 554 Pricing: Pricing Worklists ............................................................................................. 555 Pricing: List Groups...................................................................................................... 557 Pricing: Fields and List Variants in the Pricing Calculation Display............................. 558 Business Processes ............................................................................................................... 559 Sales Price Calculation ..................................................................................................... 560 Sales Price Calculation: Procedure ............................................................................. 561 Pricing Worklist Processing............................................................................................... 563 Pricing Worklist Processing: Procedure....................................................................... 564

-XQH



6$35HWDLO

6$3$*

3XUFKDVLQJ   5HTXLUHPHQWV3ODQQLQJ  Functions ................................................................................................................................ 567 Requirements Planning: Supply Source Determination in SAP Retail ............................. 568 Requirements Planning: Structured Articles ..................................................................... 569 Requirements Planning: Calculation of the Quantity Required of Header Article from the Component Quantities ................................................................................................. 570 6WRFN$OORFDWLRQ  Functions ................................................................................................................................ 575 Allocation: Allocation Rule................................................................................................. 576 Allocation: Manually Creating an Allocation Rule ........................................................ 577 Allocation: Allocation Rule Generation......................................................................... 579 Allocation: Example of Allocation rule Generation with Allocation Categories ....... 581 Allocation: Fixing an Allocation Rule............................................................................ 583 Allocation: Allocation Table ............................................................................................... 584 Allocation: Components of an Allocation Table ........................................................... 585 Allocation: Generic articles .......................................................................................... 587 Allocation: Structured Articles ...................................................................................... 588 Allocation: Creating an Allocation Table Referencing a Shipping Notification............. 589 Allocation: Scheduling in the Allocation Table ............................................................. 590 Allocation: Delivery Phases in the Allocation Table..................................................... 591 Allocation: Listing Check in the Allocation Table ......................................................... 592 Allocation: Quantities in the Allocation Table............................................................... 593 Allocation: Example of Order Quantity Optimizing in Allocation Tables ................. 595 Allocation: Supply Source Determination in the Allocation Table................................ 597 Allocation: Logs in the Allocation Table ....................................................................... 598 Allocation: Allocation Table Status............................................................................... 599 Allocation: Creating a Worklist for Follow-On Document Generation.......................... 602 Allocation: Texts in the Allocation Table ...................................................................... 603 Allocation: Site Groups in the Classification System ................................................... 604 Allocation: Allocation Strategy ..................................................................................... 605 Allocation: Notifications ..................................................................................................... 606 Allocation: Allocation Table Notification ....................................................................... 608 Allocation: Request Notification ................................................................................... 609 Allocation: Confirmation Notification ............................................................................ 610 Allocation: Allocation Table Notifications for Distribution Centers ............................... 611 Allocation: Replies from the Sites ................................................................................ 612 Allocation: Urging a Reply............................................................................................ 613 Allocation: How Notifications Interact with Follow-On Documents .............................. 614 Allocation: Follow-On Document Generation .................................................................... 615 Allocation: Business Scenarios in the Allocation Table (Item Category) ..................... 616 Allocation: Worklists ..................................................................................................... 618 Allocation: Example of a Worklist................................................................................. 619 Allocation: Updates ...................................................................................................... 620 Allocation: Aggregating Line Items in a Worklist.......................................................... 621



-XQH

6$3$*

6$35HWDLO

Allocation: Allocation Table Adjustment Following a Goods Receipt................................ 622 Allocation: Adjusting the Allocation Table Online ........................................................ 623 Allocation: Allocation Profile for Controlling Allocation Table Adjustment ................... 624 Business Processes ............................................................................................................... 625 Allocation Table Processing .............................................................................................. 626 Creating an Allocation Table: Procedure ..................................................................... 628 Creating an Allocation Table Referencing a Shipping Notification: Procedure............ 630 Allocation Table with Generic Articles: Procedure....................................................... 631 Requesting an Allocation Instruction for the Distribution Center: Procedure............... 632 Allocation Rule Processing................................................................................................ 633 Creating an Allocation Table: Procedure ..................................................................... 634 Creating Model Allocation Rules: Procedure ............................................................... 635 Displaying Allocation Rule List: Procedure .................................................................. 636 Allocation Rule Generation................................................................................................ 637 Creating an Allocation Table: Procedure ..................................................................... 639 Changing Site Assignments in Allocation Rules Already Generated: Procedure ........ 640 Generation of Documents Following On From the Allocation Table (Follow-On Document Generation) ....................................................................................................................... 641 Generating Follow-On Documents for Allocation Table Items: Procedure .................. 643 Generating Follow-On Documents using a Worklist: Procedure ................................. 644 Allocation Table Notification Processing ........................................................................... 646 Creating Notifications of Stock Allocation (Allocation Table Notifications): Procedure 648 Entering Reply Notifications in Allocation Tables: Procedure...................................... 649 Adjusting the Allocation Table Referencing a Goods Receipt .......................................... 650 Adjusting an Allocation Table Following Goods Receipt Entry: Procedure ................. 652 Closing an Allocation Table for Goods Receipts: Procedure....................................... 654 2UGHULQJ  Functions ................................................................................................................................ 658 Supply Source Determination ........................................................................................... 659 Supply Source Determination: Checking Quota Arrangements .................................. 661 Supply Source Determination: Checking the Source List ............................................ 662 Supply Source Determination: Checking the Supply Source in the Article Master ..... 663 Supply Source Determination: Requests for Quotations (RFQs) and Quotations....... 665 Order Optimizing ............................................................................................................... 667 Order Optimizing: Order Quantity Optimizing .............................................................. 668 Order Optimizing: Master Data ............................................................................... 670 Order Optimizing: Static Rounding Profile .............................................................. 672 Order Optimizing: Dynamic Rounding Profile......................................................... 674 Order Optimizing: Threshold Values....................................................................... 676 Order Optimizing: Quantity Comparison for Schedule Lines in Sales Orders........ 677 Order Optimizing: Investment Buying .......................................................................... 679 Order Optimizing: Requirements Determination Procedure in Investment Buying 680 Order Optimizing: Determining Requirements for Investment Buying in the Background or Online ............................................................................................. 681 Order Optimizing: Control Options for Determining Requirements in Investment Buying ..................................................................................................................... 682

-XQH



6$35HWDLO

6$3$*

Order Optimizing: Analysis Functions in Investment Buying .................................. 683 Order Optimizing: Load Building .................................................................................. 684 Business Processes ............................................................................................................... 687 Contract Processing .......................................................................................................... 688 Creating a Contract: Procedure ................................................................................... 690 Scheduling Agreement Processing ................................................................................... 693 Creating a Scheduling Agreement: Procedure ............................................................ 695 Purchase Requisition Processing ..................................................................................... 698 Creating a Purchase Requisition: Procedure............................................................... 700 Monitoring Purchase Requisitions: Procedure............................................................. 702 Purchase Requisition Assignment .................................................................................... 703 Assigning a Purchase Requisition: Procedure............................................................. 704 ,QYRLFH9HULILFDWLRQ  Business Processes ............................................................................................................... 708 Invoice Entry...................................................................................................................... 709 Invoice Entry: Procedure.............................................................................................. 710 Difference Processing (Invoice Verification) ..................................................................... 711 Searching for Errors: Procedure .................................................................................. 712 Automatic Invoice Verification ........................................................................................... 713 Automatic Invoice Verification: Procedure ................................................................... 715 Blocking Reason Processing (Invoice Verification)........................................................... 716 Deleting a Blocking Reason: Procedure ...................................................................... 717 6XEVHTXHQW(QGRI3HULRG5HEDWH 6HWWOHPHQW   Functions ................................................................................................................................ 720 Rebate Settlement: Full Cycle........................................................................................... 721 Rebate Arrangements ....................................................................................................... 723 Conditions .................................................................................................................... 725 Main Conditions ...................................................................................................... 727 Scaled Conditions ................................................................................................... 728 Period-Specific Conditions...................................................................................... 729 Example of Final Settlement with Respect to Period Conditions ...................... 731 Retrospective Creation of Rebate Arrangements ........................................................ 733 Updating of Cumulative Business Volumes ...................................................................... 735 Purchase Order as Prerequisite for Business Volume Update.................................... 737 Process of Updating Cumulative Business Volume Data ............................................ 739 Example of Business Volume Update for a Condition............................................ 740 Retrospective Updating of Vendor Business Volumes ................................................ 741 Retrospective Compilation of the Document Index ................................................ 745 Recompilation of Information Structures................................................................. 747 Recompilation of Vendor Business Volumes.......................................................... 748 Comparison and Agreement of Business Volumes .......................................................... 749 Settlement Accounting ...................................................................................................... 750 Settlement Type ........................................................................................................... 752 Settlement List ............................................................................................................. 755 Distribution of Rebate Income...................................................................................... 756



-XQH

6$3$*

6$35HWDLO

How SAP Business Workflow Supports the Settlement Accounting Process ............. 757 Broker Processing ............................................................................................................. 758 Interchange of Conditions Between Different Systems..................................................... 759 Transferring Data From Another System .......................................................................... 760 Transferring Data From Another System: Procedure .................................................. 762 Subsequent Settlement: Currency Changeover ............................................................... 764 Business Processes ............................................................................................................... 767 Rebate Arrangement Processing (Vendor) ....................................................................... 768 Creating a Rebate Arrangement: Procedure ............................................................... 770 Creating a Rebate Arrangement Using the Referencing Technique: Procedure......... 772 Processing Period-Specific Conditions: Procedure ..................................................... 773 Extending a Rebate Arrangement Using a Report: Procedure.................................... 774 Manually Extending a Rebate Arrangement: Procedure ............................................. 775 Settlement Accounting: Conditions Requiring Subsequent Settlement (Vendor) ............. 776 Comparison/Agreement of Business Volumes: Procedure.......................................... 778 Settlement Accounting for an Individual Rebate Arrangement: Procedure ................. 780 Settlement Accounting for Volume Rebate Arrangements via a Report: Procedure... 782 Settlement Accounting for Volume Rebate Arrangements via Workflow: Procedure.. 783 Subsequent Compilation of Statistics: Procedure........................................................ 784 Displaying Open Purchasing Documents Relating to Volume Rebate Arrangements: Procedure..................................................................................................................... 786 Displaying Information on Updated Statistical Records: Procedure ............................ 787 0HUFKDQGLVH/RJLVWLFV   *RRGV5HFHLSW   Functions ................................................................................................................................ 792 Goods Receipt: Identification ............................................................................................ 793 Goods Receipt: Rough Goods Receipt ............................................................................. 795 Goods Receipt: Check ...................................................................................................... 797 Goods Receipt: Shelf Life Expiration Date Check ............................................................ 799 Goods Receipt: Document Processing ............................................................................. 801 Goods Receipt: Repercussions......................................................................................... 803 Goods Receipt: Special Functions .................................................................................... 804 Goods Receipt: Special Article Categories ....................................................................... 806 Goods Receipt: Appointments .......................................................................................... 807 Goods Receipt: Example of an Appointment............................................................... 809 Goods Receipt: Editing Appointments Manually.......................................................... 810 Goods Receipt: Analyses for Appointments ................................................................ 811 Goods Receipt: Customer Enhancements for Appointments ...................................... 812 Goods Receipt: Automatic Generation of Appointments ........................................ 813 Goods Receipt: Automatic Determination of the Appointment Length Based on Workload............................................................................................................ 815 Goods Receipt: Entering Appointments Manually Using the Planning Board ............. 817 Goods Receipt: Entering Appointments Manually Using a Worklist ............................ 818 Goods Receipt: Store Goods Receipt ............................................................................... 819 Goods Receipt: Origin of a Store Goods Receipt ........................................................ 820

-XQH



6$35HWDLO

6$3$*

Goods Receipt: Identifying a Store Goods Receipt ..................................................... 821 Goods Receipt: How the Head Office Handles the Store Goods Receipt ................... 822 Goods Receipt: Errors and Exceptions at Store Goods Receipt ................................. 824 Business Processes ............................................................................................................... 826 Goods Receipt Planning.................................................................................................... 827 Goods Receipt Planning: Procedure............................................................................ 828 Rough Goods Receipt Processing .................................................................................... 829 Creating a Rough Goods Receipt: Procedure ............................................................. 830 Goods Receipt Processing with Reference Document ..................................................... 831 Entering a Goods Receipt with Reference Document: Procedure .............................. 833 Goods Receipt Processing................................................................................................ 835 Entering a Goods Receipt: Procedure ......................................................................... 836 Goods Receipt (Store)....................................................................................................... 837 Goods Receipt (Store): Procedure............................................................................... 839 Goods Receipt Processing (Store).................................................................................... 840 Return Delivery.................................................................................................................. 842 Return Delivery from Stock or Consumption: Procedure............................................. 843 Return Delivery from Blocked Stock: Procedure ......................................................... 844 ,QYHQWRU\0DQDJHPHQW  Functions ................................................................................................................................ 847 Inventory Management: Basic Principles .......................................................................... 848 Inventory Management: Stock Types .......................................................................... 849 Inventory Management: Article Type ........................................................................... 850 Inventory Management: Transactions............................................................................... 851 Inventory Management: Analyses..................................................................................... 853 Inventory Management: Stock Overview ..................................................................... 855 Inventory Management: Stock Types Updated ...................................................... 856 Inventory Management: Stock Types Calculated via Open Document Items ........ 858 Inventory Management: Stock Overview Display Levels........................................ 860 Inventory Management: Stock Overview Display Variants..................................... 861 Inventory Management: Stock Overview Display Versions .................................... 863 Inventory Management: Batches ...................................................................................... 864 Inventory Management: Special Stocks............................................................................ 865 Inventory Management: Inventory Management at Value-Only Article Level................... 867 Inventory Management: Controlling Inventory Management on a Value-Only Basis .. 868 Inventory Management on an Article Basis: Example ............................................ 870 Inventory Management on a Value-Only Basis at the Merchandise-Category Article Level: Example ....................................................................................................... 871 Inventory Management on a Value-Only Basis at the Hierarchy Article Level: Example .................................................................................................................. 872 Inventory Management on a Value-Only Basis at the Merchandise Category Article Level with Exceptions: Example ............................................................................. 873 Inventory Management: Stock Overview for Value-Only Articles ................................ 874 Inventory Management: Special Articles Categories ........................................................ 875 Inventory Management: Generic Articles..................................................................... 876 Inventory Management: Structured Articles................................................................. 877



-XQH

6$3$*

6$35HWDLO

Inventory Management: Processing Empties .............................................................. 879 Inventory Management: Managing Empties Components in Bills of Material ........ 880 Inventory Management: Special Stock Type for Tied Empties............................... 881 Inventory Management: Automatic Inclusion of Empties Components in Documents882 Inventory Management: Automatic Posting of Differences for Empties Components in Physical Inventory ............................................................................................... 883 Inventory Management: Stock List of Empties ....................................................... 884 Business Processes ............................................................................................................... 886 Reservation Processing .................................................................................................... 887 Creating a Reservation ................................................................................................ 889 Processing Reservations ........................................................................................ 890 Creating a Reservation Using a Reference Document................................................ 892 Planning Goods Receipts Using Reservations ............................................................ 893 Changing a Reservation............................................................................................... 894 Changing a Reservation ......................................................................................... 895 Changing the Requirement Date ....................................................................... 896 Changing the Requirement Quantity ................................................................. 897 Changing the Movement Allowed Indicator ....................................................... 898 Changing the Final Issue Indicator .................................................................... 899 Checking Availability.......................................................................................... 900 Deleting an Item................................................................................................. 901 Enter New Items ................................................................................................ 902 Displaying a Reservation ............................................................................................. 903 Managing Reservations ............................................................................................... 905 Tasks of the Reservations Management Program ................................................. 906 Functions of the Reservations Management Program ........................................... 907 Running the Reservations Management Program ................................................. 909 Stock Transfer in a Single Step......................................................................................... 910 Using the One-Step Procedure With a Reservation - Storage Location...................... 912 Using the One-Step Procedure With a Reservation - Plant......................................... 913 Using the One-Step Procedure Without a Reservation - Storage Location................. 914 Using the One-Step Procedure Without a Reservation - Plant.................................... 915 Stock Transfer From Company Code to Company Code ............................................ 916 Stock Transfer in Two Steps ............................................................................................. 917 Two-Step Procedure - Storage Location...................................................................... 919 Entering Removal From Storage at Issuing Storage Location ............................... 921 Entering Placement Into Storage at Receiving Storage Location .......................... 922 Two-Step Procedure - Plant......................................................................................... 923 Entering the Removal From Storage At the Issuing Plant ...................................... 925 Entering the Placement Into Storage At the Receiving Plant ................................. 926 Stock Transfer From Company Code to Company Code ............................................ 927 Special Stock Movements (Store)..................................................................................... 928 9DOXDWLRQ  Functions ................................................................................................................................ 931 Valuation: Reasons for Sales Price Valuation (Retail Method)......................................... 932

-XQH



6$35HWDLO

6$3$*

Valuation: Controlling Sales Price Valuation (Retail Method) ........................................... 934 Valuation: Sales Price Valuation and Goods Movements................................................. 936 Valuation: Example of Splitting a Structured Article .................................................... 939 Valuation: Sales Value Updates in the Retail Information System ................................... 940 Valuation: Displaying Stock at Sales Prices...................................................................... 941 Valuation: Reasons for Sales Price Revaluation .............................................................. 943 Valuation: Revaluation Profiles ......................................................................................... 944 Revaluation: Manual Revaluation ..................................................................................... 946 Valuation: Automatic Sales Price Revaluation .................................................................. 947 Valuation: Automatic Revaluation when Price Calculations Change........................... 948 Valuation: Automatic Revaluation for Local Markdowns.............................................. 949 Valuation: Automatic Revaluation for Promotions ....................................................... 950 Valuation: Automatic Revaluation for Stock Transfers ................................................ 951 Valuation: Automatic Revaluation for Postings with the Posting Date in the Past ...... 953 Valuation: Revaluation for Local Markdowns .................................................................... 954 Valuation: Example of Sales Price Valuation with Different Sales Units ..................... 956 Valuation: Revaluation for Promotions.............................................................................. 957 Valuation: Sales Value Change Document ....................................................................... 959 Business Processes ............................................................................................................... 960 Sales Price Revaluation .................................................................................................... 961 Sales Price Revaluation: Procedure ............................................................................ 963 :DUHKRXVH0DQDJHPHQW   Business Processes ............................................................................................................... 966 Stock Placement Processing............................................................................................. 967 Stock Placement Processing: Procedure..................................................................... 969 Stock Placement Strategies .............................................................................................. 971 Stock Removal Processing ............................................................................................... 972 Stock Removal Processing: Procedure ....................................................................... 974 Stock Removal Strategies ................................................................................................. 976 Shipping Unit Storage ....................................................................................................... 977 Storing Shipping Units.................................................................................................. 980 Removing Shipping Units From Stock ......................................................................... 981 Transferring Shipping Units ......................................................................................... 982 Replenishment Planning for Fixed Storage Bins .............................................................. 983 Replenishment Planning for Fixed Storage Bins: Procedure....................................... 985 3K\VLFDO,QYHQWRU\   Functions ................................................................................................................................ 989 Physical Inventory: Methods ............................................................................................. 990 Physical Inventory: Stock for Which Physical Inventory Can Be Carried Out................... 992 Physical Inventory: Store................................................................................................... 994 Physical Inventory: Without Warehouse Management ..................................................... 995 Physical Inventory: With Warehouse Management .......................................................... 996 Physical Inventory: Goods Movement Block..................................................................... 998 Physical Inventory: Differences....................................................................................... 1000 Physical Inventory: Analyses .......................................................................................... 1002



-XQH

6$3$*

6$35HWDLO

Physical Inventory: Value-Only Article Management ...................................................... 1004 Physical Inventory: Support for Carrying Out a Store Physical Inventory....................... 1005 Physical Inventory: Sending Physical Inventory Documents to a Store .................... 1006 Physical Inventory: Structure of Intermediate Documents (IDocs) ............................ 1007 Physical Inventory: Processing the Count Data from a Store.................................... 1009 Business Processes ............................................................................................................. 1012 Physical Inventory Processing ........................................................................................ 1013 Creating a Physical Inventory Document: Procedure ................................................ 1015 Subsequent Blocking of Articles for Postings: Procedure.......................................... 1017 Printing Count Lists: Procedure ................................................................................. 1018 Transferring Physical Inventory IDocs: Procedure .................................................... 1019 Freezing the Book Balance: Procedure ..................................................................... 1020 Entering the Results of a Physical Inventory Count (Online): Procedure .................. 1022 Setting the Zero Count Indicator: Procedure ............................................................. 1023 Triggering a Recount: Procedure............................................................................... 1024 Posting Differences: Procedure ................................................................................. 1025 Physical Inventory (Store) ............................................................................................... 1027 6KLSSLQJDQG7UDQVSRUWDWLRQ  Functions .............................................................................................................................. 1030 Shipping and Transportation: Printing the Retail Price in the Delivery Note................... 1031 Shipping and Transportation: Replenishment for Fixed Bins.......................................... 1032 Business Processes ............................................................................................................. 1033 Route Schedule Processing ............................................................................................ 1034 Creating a Route Schedule: Procedure ..................................................................... 1036 Delivery Processing......................................................................................................... 1037 Displaying the Retail Price in the Delivery: Procedure .............................................. 1040 Creating Single Deliveries.......................................................................................... 1041 Creating Deliveries without Reference....................................................................... 1043 Collective Processing................................................................................................. 1044 Packing Processing......................................................................................................... 1047 Packing Delivery Items .............................................................................................. 1049 Dividing Delivery Items for Packing ........................................................................... 1051 Packing Deliveries in Shipment Documents .............................................................. 1052 Goods Issue Processing ................................................................................................. 1053 Posting Goods Issue for a Delivery............................................................................ 1054 Posting Goods Issue in Collective Processing .......................................................... 1055 )RUHLJQ7UDGH  6DOHV  $GGLWLRQDOV   Functions .............................................................................................................................. 1061 Additionals: Master Data ................................................................................................. 1062 Additionals: Grouping Sites Together ............................................................................. 1063 Additionals: Control ......................................................................................................... 1064 Additionals: Examples of Procedures ............................................................................. 1065 Additionals: Data Transmission via an Additionals IDoc................................................. 1066

-XQH



6$35HWDLO

6$3$*

Additionals: Data Transmission via the Assortment List IDoc......................................... 1068 Business Processes ............................................................................................................. 1069 Additionals ....................................................................................................................... 1070 Generating an Additionals IDoc Manually: Procedure ............................................... 1072 Generating an Additionals IDoc Automatically: Procedure ........................................ 1073 6WRUH2UGHU   Functions .............................................................................................................................. 1076 Store Order: Online Processing ...................................................................................... 1077 Store Order: Generating Store Orders Offline ................................................................ 1078 Store Order: Document Categories in Offline Processing .............................................. 1080 Store Order: Working with the Sourcing Check ......................................................... 1082 Store Order: Rules for the Sourcing Check ............................................................... 1083 Store Order: Offline Processing in the Head Office ........................................................ 1084 Store Order: Checking Offline Processing Data ........................................................ 1085 Store Order: Adding to Offline Processing Data ........................................................ 1086 Store Order: Offline Processing Confirmation ........................................................... 1088 Store Order: Handling Offline Processing Errors....................................................... 1089 Store Order: Alternative Methods of Supplying Stores with Merchandise ...................... 1091 Business Processes ............................................................................................................. 1092 Store Order...................................................................................................................... 1093 Creating a Store Order: Procedure ............................................................................ 1095 Store Order Processing................................................................................................... 1097 5HSOHQLVKPHQW   Functions .............................................................................................................................. 1102 Replenishment: Inventory Management Types .............................................................. 1103 Replenishment: Methods................................................................................................. 1104 Replenishment: Standard Method ............................................................................. 1106 Replenishment: Simplified Method ............................................................................ 1107 Replenishment: Inclusion of Expected Receipts and Issues .......................................... 1109 Replenishment: Example Including Expected Receipts and Issues.......................... 1110 Replenishment: Working with a Reorder Point .......................................................... 1111 Replenishment: Requirement Groups............................................................................. 1112 Replenishment: Example of the Use of Requirement Groups ................................... 1113 Replenishment: Master Data........................................................................................... 1115 Replenishment: Site Master Data .............................................................................. 1116 Replenishment: Article Master Data in Article Maintenance...................................... 1117 Replenishment: Article Master Data in an Auxiliary Transaction in Replenishment.. 1118 Replenishment: Forecast ................................................................................................ 1120 Replenishment: Planning Replenishments ..................................................................... 1121 Business Processes ............................................................................................................. 1123 Replenishment ................................................................................................................ 1124 Creating Replenishment Master Data: Procedure ..................................................... 1125 Changing Weighting Factors for Replenishment: Procedure..................................... 1127 Carrying out the Forecast for Replenishment: Procedure ......................................... 1128 Planning Replenishments: Procedure........................................................................ 1129 6DOHV6XSSRUW 



-XQH

6$3$*

6$35HWDLO

Functions .............................................................................................................................. 1131 Sales Support: Product Catalog...................................................................................... 1132 6DOHV2UGHU3URFHVVLQJ   Functions .............................................................................................................................. 1134 Sales Order Processing: Basic Functions....................................................................... 1135 Sales Order Processing: How Sales Documents Are Structured ................................... 1136 Sales Order Processing: Sales Order Quantity Optimizing ............................................ 1138 Sales Order Processing: Sales Order with Promotion Determination ............................ 1139 Sales Order Processing: Blocking a Sales Order ........................................................... 1140 Sales Order Processing: Different Types of Payment .................................................... 1141 Business Processes ............................................................................................................. 1142 Sales Order Processing .................................................................................................. 1143 Creating a Sales Order: Procedure............................................................................ 1146 Creating a Sales Order with Promotion Determination: Procedure ........................... 1147 Processing Goods Offered to Customers on Approval (Store) ....................................... 1149 %LOOLQJ   Functions .............................................................................................................................. 1152 Business Processes ............................................................................................................. 1153 Billing Document Processing........................................................................................... 1154 Billing Document Processing: Procedure................................................................... 1155 Processing the Billing Due List: Procedure................................................................ 1156 Invoice List Processing.................................................................................................... 1157 Creating Invoice Lists................................................................................................. 1158 Rebate Settlement (Customer) ....................................................................................... 1159 Carrying out Partial Settlement .................................................................................. 1161 Carrying out Final Settlement .................................................................................... 1162 Carrying out Final Settlement as a Background Task ............................................... 1163 &RQVLJQPHQW6WRFN   Functions .............................................................................................................................. 1165 Consignment Stock: Special Stock Partner .................................................................... 1166 Consignment Stock: Sales Order Types ......................................................................... 1167 Consignment Stock: Pricing and Availability Check........................................................ 1168 'LVWULEXWHG5HWDLOLQJ  326,QWHUIDFH   POS Interface - Outbound .................................................................................................... 1171 Functions ......................................................................................................................... 1172 POS Interface - Outbound: Information Flow............................................................. 1173 POS Interface - Outbound: Master Data.................................................................... 1174 POS Interface - Outbound: Which Data is Distributed?............................................. 1175 POS Interface - Outbound: Basic Settings................................................................. 1176 POS Interface - Outbound: How Is Data Distributed Periodically?............................ 1177 Business Processes ........................................................................................................ 1179 POS Interface - Outbound: Master Data Preparation ................................................ 1180 Preparing Master Data: Procedure ....................................................................... 1181 POS Interface - Inbound....................................................................................................... 1182 Functions ......................................................................................................................... 1184

-XQH



6$35HWDLO

6$3$*

POS Interface - Inbound: Sales Data......................................................................... 1185 POS Interface - Inbound: Payment Card Processing ................................................ 1188 POS Interface - Inbound: Financial Transactions ...................................................... 1189 POS Interface - Inbound: Special Goods Movements ............................................... 1190 POS Interface - Inbound: Store Goods Receipt......................................................... 1191 POS Interface - Inbound: Cashier Statistics .............................................................. 1192 POS Interface - Inbound: Store Order ....................................................................... 1193 POS - Interface Inbound: Store Physical Inventory ................................................... 1194 POS Interface - Inbound: Changing Master Data ...................................................... 1195 POS Interface - Inbound: Currency Changeover....................................................... 1196 POS Interface - Inbound: Performance...................................................................... 1198 POS Interface-Inbound: Sales Audit / IDoc Editor ..................................................... 1199 POS Interface - Inbound: Integration in Financial Accounting ................................... 1200 Business Processes ........................................................................................................ 1201 POS Interface - Inbound: Sales/Returns (Store) ....................................................... 1202 POS Interface - Inbound: Non-Cash Payment (Store)............................................... 1203 POS Interface - Inbound: Financial Transactions (Store) .......................................... 1204 POS Interface - Inbound: Master Data Processing (Store)........................................ 1205 POS Interface Monitor .......................................................................................................... 1206 Functions ......................................................................................................................... 1207 POS Interface Monitor: Error/Exception Processing.................................................. 1208 POS Interface Monitor: Exception Processing........................................................... 1209 POS Interface Monitor: How Workflow Interacts with the Applications ..................... 1210 5HPRWH$FFHVV   $SSOLFDWLRQ/LQN(QDEOLQJ$/(   ,QIRUPDWLRQ6\VWHP   &RPSRQHQWVRIWKH/RJLVWLFV,QIRUPDWLRQ6\VWHPDQG6WUXFWXUHRIWKH'RFXPHQWDWLRQ  )OH[LEOH3ODQQLQJ6\VWHP   2SHQWR%X\27%   Functions .............................................................................................................................. 1218 OTB: How It Works.......................................................................................................... 1219 OTB: Three Phases of Operation.................................................................................... 1220 OTB: Example Calculations for a Season....................................................................... 1223 OTB: Planning and Monitoring OTB................................................................................ 1227 OTB: Exception Reporting............................................................................................... 1228 OTB: Planning Hierarchy................................................................................................. 1229 OTB: Planning Method .................................................................................................... 1230 OTB: Ways to Plan.......................................................................................................... 1231 OTB: What to Plan .......................................................................................................... 1232 OTB: Opening Stock ....................................................................................................... 1235 OTB: Average Price Band Prices.................................................................................... 1237 6HDVRQDO0RGHOZLWK:HLJKWLQJ)DFWRUV  Functions .............................................................................................................................. 1240 Seasonal Models with Weighting Factors: Formulae...................................................... 1241 Seasonal Model with Weighting Factors: Example......................................................... 1242



-XQH

6$3$*

6$35HWDLO

&XUUHQF\&KDQJHRYHU(XUR  

-XQH



6$35HWDLO

6$3$*

6$35HWDLO Basic Principles SAP Retail Overview [Page 26] This Documentation [Page 31] Organizational Structure [Page 34] Background Processing [Page 59] Business Processes [Page 102]

Concepts and Processes (Top-Down Navigation) Central Coordination Master Data [Page 112] Strategic Sales [Page 407]

Local Operations Purchasing [Page 565]

Processes (Organizational View) Processes at Headquarters [Page 103] Processes in Distribution Centers [Page 106] Processes in Distribution Centers [Page 108] Processes in Sales Offices [Page 110]

Merchandise Logistics [Page 788] Sales [Page 1057]

Distributed Retailing POS Interface [Page 1170] Remote Access [Page 1211] Application Link Enabling (ALE) [Page 1212]

Information and Planning System Information System [Page 1213] Planning System [Page 1216] Currency Conversion (Euro) [Page 1244]



-XQH

6$3$*

6$35HWDLO %DVLF3ULQFLSOHV

%DVLF3ULQFLSOHV This section describes the structure of the documentation for SAP Retail, an overview of the areas in which the system is used, and information on the underlying organizational structures and processes.

-XQH



6$35HWDLO

6$3$*

6$35HWDLO2YHUYLHZ

6$35HWDLO2YHUYLHZ SAP Retail is a completely integrated retailing system. It maps the complete set of business processes required for competitive assortment strategies, different retail formats, and ECR-driven logistics and distribution. It provides all the functions necessary for modeling business processes in a retail company. With SAP Retail, SAP has endeavored to model the full ´9DOXH&KDLQ´ all the links in the logistics pipeline from consumer to vendor. Retailers can thus optimize the whole array of business processes and control checks in managing the flow of merchandise and information among vendors, retailers and consumers.

The business process area “Retailing” comprises the procurement, storage, distribution, and sale of merchandise. SAP Retail supports both wholesale and retail scenarios. The Retail Information System (RIS) enables goods movements to be planned, monitored and tracked throughout the whole supply chain. The key retailing processes include:



•

Assortment Management

•

Sales Price Calculation

•

Promotion Management

•

Allocation

•

Requirements Planning and Purchasing

•

Goods Receipt

•

Invoice Verification and Subsequent Settlement of End-Of-Period Arrangements

-XQH

6$3$*

6$35HWDLO 6$35HWDLO2YHUYLHZ

•

Warehouse Management

•

Picking and Delivery

•

Billing

•

Store Supply

The retailing processes enable you to control and coordinate the whole value chain, and this react swiftly to changes in consumer behavior. New trends, such as electronic commerce or ECR, flow continually into ongoing development cycles. SAP Retail also allows for changes in legal structures or business practices – franchising, for example. This ensures that retailers not only have a future-proof investment but are able to adapt swiftly to a changing market. The growth of your company is not hampered by system constraints, and you can incorporate changes in the real world smoothly and efficiently into the system. 6HHDOVR This Documentation: Link to Corresponding General Documentation [Page 32] Organizational Structure [Page 34]

-XQH



6$35HWDLO

6$3$*

,QWHJUDWLRQRI6$35HWDLOLQWKH5(QYLURQPHQW

,QWHJUDWLRQRI6$35HWDLOLQWKH5(QYLURQPHQW SAP Retail includes the base R/3 components such as Financial Accounting, Controlling and Human Resources. And at the heart of the system is functionality specially developed for 5HWDLOLQJ,65 

,QIRUPDWLRQ 'DWD :DUHKRXVH

Investment

CO

IM Management

Controlling

FI

Financial Accounting

Information

EC Management

(QWHUSULVH 0DQDJHPHQW Asset FI AA Management

HR

Human Resources

FI

Financial Accounting

Retail

RIS Information

System

%XVLQHVV 6XSSRUW IS-R

Vendor

EDI / Internet

IS-R

Purchasing

IS-R Promotions PS

API Layout planning

IS-R

Assortment

Projects

&RUH %XVLQHVV

Warehouse automation

IS-R

Replenishment Planning

Transport

WF

Workflow

Sales

Customer

EDI / Internet

API POS

SAP Retail is fully integrated in R/3, opening up whole new opportunities in the R/3 environment. Thus retailers and suppliers can work even closer together and become true allies in the value chain, without having to painstakingly build bridges between systems. Joint projects for optimizing business processes can be launched, tests carried out and the results accepted or rejected, without any large investments in uncertain projects being necessary.



-XQH

6$3$*

6$35HWDLO $UHDVRI$SSOLFDWLRQRI6$35HWDLO

$UHDVRI$SSOLFDWLRQRI6$35HWDLO SAP Retail integrates all the key areas of retailing and wholesaling, all the various stages in the logistics chain and takes into account the differing requirements of different types of goods, from food and dairy to fashion and hardlines. It provides you with the tools necessary to model all the business processes in the retail sector. 5HWDLO

Wholesale with consumer goods

Retail sector

Store trading Electronic retailing Mail order Direct selling

-XQH



6$35HWDLO

6$3$*

'LVWULEXWHG5HWDLOLQJ

'LVWULEXWHG5HWDLOLQJ Distributed Retailing enables business processes to be decentralized. The use of distributed retailing systems (DRS) brings the following benefits for retailers: •

Improved performance

•

Greater security

•

They enable decentralized company policies, whereby sites have a high degree of autonomy, to be modeled in the system. This allows whole areas of responsibility to be assigned to those organizational unit at which information - on customers, vendors or goods movements - is usually gathered.

Distributed retailing can take three forms:



•

POS Interface

•

Remote Access to SAP R/3

•

Application Link Enabling (ALE)

-XQH

6$3$*

6$35HWDLO 7KLV'RFXPHQWDWLRQ

7KLV'RFXPHQWDWLRQ This documentation describes the SAP Retail functions and explains how they are used, along with examples from a number of business processes. The documentation is aimed at all users of the system, especially those in the various application areas as well as administrators responsible for configuring and maintaining the system and who require basic practical skills in using the functions. You must have a knowledge of business management and know basically how to navigate in the R/3 system. ´ This documentation describes the standard version of the SAP Retail System. Depending on how your system is configured, individual screens can look different or even be missing. You can see what you should enter in each individual screen by clicking on the field with the mouse and pressing )

´ This documentation is not a guide to Customizing the system. Please use the SAP R/3 Implementation Guide (IMG) 6HHDOVR Getting Started [Ext.]

-XQH



6$35HWDLO

6$3$*

7KLV'RFXPHQWDWLRQ/LQNWR&RUUHVSRQGLQJ*HQHUDO'RFXPHQWDWLRQ

7KLV'RFXPHQWDWLRQ/LQNWR&RUUHVSRQGLQJ*HQHUDO 'RFXPHQWDWLRQ SAP Retail is a full-fledged, closed-loop system containing all the functions you require to model retail business processes. SAP Retail also includes general R/3 components such as Financial Accounting, Controlling and Human Resources. At the heart of the SAP Retail system are functions specially developed for retailing. This is based in part on the R/3 Materials Management (MM), Sales and Distribution (SD), and Warehouse Management (WM) components.

00

6'

5HWDLO ,65

This documentation describes the functions developed specifically for retailing. For many topics, documentation also exists describing the functions in a more general context. If you would like to read about the more general context, please see the documentation referred to under the heading &RUUHVSRQGLQJ*HQHUDO'RFXPHQWDWLRQ. In certain circumstances – for example, if your company also has manufacturing operations – you may use some components that are purely MM, SD or WM. In this case, you can reach the documentation for these areas by choosing +HOS →5OLEUDU\ from the menu. ´ If you branch to the corresponding general documentation, the text that appears has a different structure to this documentation. Also, the terminology used is not specific to the retail sector but is the general terminology used throughout the whole SAP system. The following terms differ, depending on where you are in the documentation: 6$35HWDLO



*HQHUDOGRFXPHQWDWLRQ

-XQH

6$3$*

6$35HWDLO 7KLV'RFXPHQWDWLRQ/LQNWR&RUUHVSRQGLQJ*HQHUDO'RFXPHQWDWLRQ

Article

Material

Site

Plant

Material Requirements Planning (MRP)

Requirements Planning (RP)

Logistics Calendar

Factory calendar

´ In certain situations – such as in the F1 help – the terminology of the general documentation (material, plant, etc.) is used and not the terminology specific to retail (article, site, etc.).

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH

2UJDQL]DWLRQDO6WUXFWXUH Flexible organizational units make it possible to reproduce even the most complex corporate structures in the R/3 system. The large number of organizational units available in the R/3 system enables you to reflect the legal and organizational structure of your company in the system and represent it from different viewpoints. The following is a list of the most important organizational units along with a short explanation of their meaning in SAP Retail. Many organizational units are also data retention levels; this means that if there is more than one of a particular organizational unit, different data can be stored for each one.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH([DPSOH

2UJDQL]DWLRQDO6WUXFWXUH([DPSOH The following example illustrates how the structure of a company could be reproduced in SAP Retail and explains what the various organizational units mean. The fictitious company has several subsidiaries, which themselves comprise several distribution chains. Organizational Structure: Example Graphic [Page 36] The organizational structure of the company in the example graphic would be modeled in SAP Retail as follows: •

&HQWUDOSXUFKDVLQJ The highest element in the whole corporate group hierarchy is the client. All the organizational units in a client are subject to the same control mechanisms. Data valid across the whole corporate group is stored at client level. In the example, the central purchasing department of the company is located in the SAP Retail structure at client level.

•

/RFDOSXUFKDVLQJ Local purchasing departments are assigned to central purchasing. Each local purchasing department is responsible for a different distribution chain. Each local purchasing department corresponds to a company code or a purchasing organization in SAP Retail. Specific purchasing activities are assigned to individual purchasing groups.

•

'LVWULEXWLRQFKDLQ Local purchasing procures merchandise for different distribution chains centrally. Distribution chains in SAP Retail are a combination of sales organization and distribution channel. The sales organizations are assigned to different company codes.

•

'LVWULEXWLRQFHQWHU6WRUH Distribution chains consist of distribution centers (DC) and stores. The generic term for DCs and stores in SAP Retail is “site.” Sites are also managed as customers in the system.

•

6WRUDJHORFDWLRQ6WRUDJHVHFWLRQ'HSDUWPHQW Sites can also be seen as a combination of one or more locations in close proximity to each other where stocks of merchandise can be found (examples are storage locations and storage sections). Stores can also be subdivided into departments, which in turn can be understood as cost centers. Each department can be assigned a receiving point.

•

&XVWRPHU The value chain concludes with the customer or consumer. If the customer is recorded in the system (and is therefore not a non-identifiable customer), natural persons can be defined in the customer master as the contact persons at that customer.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH([DPSOH

2UJDQL]DWLRQDO6WUXFWXUH([DPSOH*UDSKLF The following illustration represents the structure of a typical retail business. Central purchasing

Client Purchasing organization Company code

Local purchasing

Distribution chain

Store

Distribution center

Storage types

Customer

Customer

Distribution center

Storage location

Storage location

Customer

Person



Company code Sales organization Distribution channel

Distribution chain

Department

Customer

Person

Store

Department

Site + Customer (Company code) Storage location Department Cost center Customers Contact person

-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH&RUSRUDWH*URXS

2UJDQL]DWLRQDO6WUXFWXUH&RUSRUDWH*URXS At the top of the hierarchy of all the organizational units is the FRUSRUDWHJURXS. It corresponds to a retailing company with, for example, several subsidiaries which are defined from a Financial Accounting point of view as individual FRPSDQ\FRGHV. Data defined at corporate group level is valid for all purchasing and sales organizations. On the logistics side, the corporate group also divides into sites. A VLWH is a store, a distribution center or a production location. In SAP Retail, the site is the organizational level at which merchandise replenishment is planned and stocks are managed. Sites can be grouped together using the Classification System.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH3XUFKDVLQJ2UJDQL]DWLRQ

2UJDQL]DWLRQDO6WUXFWXUH3XUFKDVLQJ2UJDQL]DWLRQ The purchasing organization is an organizational unit which procures articles and negotiates general purchase price conditions with YHQGRUV. Purchasing organizations are data retention levels for many types of master data. Purchasing organizations are responsible for all purchasing transactions. A purchasing transaction is processed completely by one single purchasing organization. Authorizations to maintain master data and process purchasing transactions are assigned per purchasing organization. Each buyer is assigned to a purchasing organization in his or her user master. A purchasing organization can be assigned to a variety of other organizational units: One (and only one) FRPSDQ\FRGH can be assigned to a purchasing organization. A purchasing organization which has been assigned a company code can only buy for sites that belong to that company code. If the purchasing organization is to be responsible for sites that do not all belong to the same company code, no company code should be assigned to that purchasing organization. This is especially important to bear in mind if the ordering site and the supplying site for a warehouse order or merchandise clearing are assigned the same purchasing organization but these sites belong to different company codes. A VLWH can be assigned to the purchasing organization which orders for it in site maintenance. This standard (default) purchasing organization for a site can be changed both in site maintenance and via Customizing. When the source of supply is determined for the purposes of a stock transfer or consignment, the default purchasing organization is used automatically. Further purchasing organizations can be assigned to the site in addition to the default. A site cannot order if it has not been assigned to a purchasing organization. A VDOHVRUJDQL]DWLRQ can be assigned a purchasing organization for statistical purposes. If this assignment is made and the sales organization is then assigned to a site in site maintenance, the default purchasing organization for the site must be the one that has been assigned to the sales organization. In Customizing it is possible to assign UHIHUHQFHSXUFKDVLQJRUJDQL]DWLRQV to a purchasing organization. This allows the purchasing organization access to the conditions and contracts of these reference purchasing organizations. Purchasing info records are not referenced. The purchasing organization can make use of up to two reference purchasing organizations when the sequence in which it accesses conditions is determined. 9HQGRUV are assigned a purchasing organization in the purchasing-related data in the vendor master (purchasing organization vendor).This enables the purchasing organization to order from this vendor. A vendor can supply more than one purchasing organization. Purchasing organization-specific purchasing info records can only be created if corresponding table entries exist. The system also uses the purchasing organization for vendor analyses and for vendor evaluation. In SXUFKDVHSULFHGHWHUPLQDWLRQ, a purchasing organization can be assigned a schema group. This, together with the schema group of the vendor, determines the calculation schema for Purchasing. A purchasing organization can also be assigned a market price schema, which allows the average market price of an article to be maintained (for the purposes of rating a vendor’s price history). In addition, it is possible to process in the system any delivery costs that may arise in connection with a stock transport order. The calculation schema for this is determined via the schema group for the purchasing organization, the purchasing document type and the supplying site.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH3XUFKDVLQJ2UJDQL]DWLRQ

In addition to the above, some other important applications of the purchasing organization should be mentioned: When a VWRFNWUDQVSRUWRUGHUis created (order type UB), all the sites (stores) ordering together must belong to the same company code. This company code must also be the one defined for the purchasing organization specified. If the purchasing organization has not been assigned a company code, the company code of the ordering sites will be used (or alternatively, a company code can be entered manually in a separate window). The system checks whether the purchasing organization is allowed to order for the sites specified. The system does not use any data from the supplying site in the order, nor does it use any data from the combination of supplying site and receiving site (except to calculate the delivery costs). When a stock transport order is created between two company codes, the purchasing organization cannot be assigned to any fixed company code if it is to order for the supplying site. In VWDQGDUGSXUFKDVHRUGHUV(order type NB) the system also checks whether the ordering purchasing organization is assigned to the vendor. This is important for purchase price determination, for example. Similar checks take place for RXWOLQHDJUHHPHQWV (contracts, scheduling agreements). Because SURPRWLRQVand DOORFDWLRQWDEOHV can be used to generate purchase orders, purchasing organizations play a role in these areas, too. Promotions need purchasing organizations for supply source determination and price maintenance functions; they are used in allocation table functions for scheduling (determining the latest possible purchase order date), for example. An activity preceding the purchase order and which involves the purchasing organization is the UHTXHVWIRUTXRWDWLRQLVVXHGWRWKHYHQGRU, the invitation made by a purchasing organization to a vendor assigned to it to submit a quotation.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH3XUFKDVLQJ$UHD

2UJDQL]DWLRQDO6WUXFWXUH3XUFKDVLQJ$UHD Purchasing areas are assigned to the purchasing organizations responsible for negotiations with vendors and the master data maintenance that results from them. No data or authorizations are stored at purchasing area level. Purchasing areas are only used in the Information System and in master data reporting. A purchasing group can only be assigned to one purchasing area in a purchasing organization.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH3XUFKDVLQJ*URXS

2UJDQL]DWLRQDO6WUXFWXUH3XUFKDVLQJ*URXS Purchasing groups are assigned to the purchasing areas. Purchasing groups are not data retention levels; they are used as a selection criterion, as a level at which analyses can take place in the Information System and at which authorizations can be stored. A purchasing group comprises one or more buyers and thus resembles a purchasing department. The main strategic function of a purchasing group in SAP Retail is to maintain its master data and control data. This includes defining outline agreements and volume rebate arrangements for Purchasing, for example. A further responsibility of the purchasing group is the day-to-day ordering process (requirements planning). This includes creating purchase orders, allocation tables and promotions. It can also send vendors requests for quotation or create purchase requisitions. Every stock planner is assigned to a purchasing group. In the individual purchasing operations you are mostly required to enter a purchasing group and a purchasing organization. It is not possible to define an explicit link in the system between these two organizational units. A buyer is assigned to a purchasing group in the user master. Purchasing groups can function strategically, operationally, or both.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH&RPSDQ\&RGH

2UJDQL]DWLRQDO6WUXFWXUH&RPSDQ\&RGH A company code is an independent accounting unit which represents an independent company in the legal sense. It is the central organizational element in Financial Accounting. In the retail sector, company codes can function at distribution chain level or even at the level of individual stores. For this reason, goods movements (such as stock transfers) between different company codes are common in SAP Retail. There are various assignments between a company code and other organizational units: A SXUFKDVLQJRUJDQL]DWLRQ can be assigned to a company code. In this case, the purchasing organization can only order for sites within this company code. The YDOXDWLRQDUHD is the organizational unit of the R/3 system via which stock is managed on a value basis. The valuation area can be a site but it can also be a company code. In SAP Retail it is always assumed that valuation area and site are identical. A VLWH(or more precisely the valuation area which belongs to a site) is assigned a company code as an attribute in site maintenance or in Customizing. Each VDOHVRUJDQL]DWLRQ must be assigned to a company code in Customizing. This assignment forms the link between Sales and Distribution and Accounts Receivable Accounting.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH6DOHV2UJDQL]DWLRQ

2UJDQL]DWLRQDO6WUXFWXUH6DOHV2UJDQL]DWLRQ Each sales organization represents a “selling unit” in the legal sense. Its responsibilities include product liability and any claims to recourse that customers may make. It is also responsible for sales and distribution of merchandise and negotiates sales price conditions. Sales organizations can be used to reflect regional subdivisions of the market, for example by states. A sales transaction is always processed entirely within one sales organization. Each sales organization is assigned one FRPSDQ\FRGH. This company code tracks the business transactions of the sales organization from a mainly financial accounting point of view. When a delivery is made for a sales order, a transfer posting from the company code of the sales organization processing the order to the company code of the supplying site is generated (if two different company codes are involved). In SAP Retail, a sales organization can be assigned a SXUFKDVLQJRUJDQL]DWLRQ. This allows you to create an artificial hierarchy like the one shown in the diagram, giving you access to useful statistical information. In some cases the two terms are identical. (PSOR\HHV can be assigned to a sales organization. If a sales organization is not allowed to use all types of sales and distribution documents, it is possible to assign it a UHIHUHQFHVDOHVRUJDQL]DWLRQ so that only those sales and distribution document types found in the reference are allowed in the assigned sales organization.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH'LVWULEXWLRQ&KDQQHO

2UJDQL]DWLRQDO6WUXFWXUH'LVWULEXWLRQ&KDQQHO In order to supply the market as efficiently as possible, the sales and distribution component defines different distribution channels. Distribution channels include selling to consumers through various types of retail outlet or via mail order. Each distribution channel is assigned to a VDOHVRUJDQL]DWLRQ, forming a distribution chain. Multiple assignments are possible. A distribution channel is not a data retention level until it has been combined with a sales organization (and a division, if required).



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH'LVWULEXWLRQ&KDLQ

2UJDQL]DWLRQDO6WUXFWXUH'LVWULEXWLRQ&KDLQ A distribution chain is a combination of VDOHVRUJDQL]DWLRQ and GLVWULEXWLRQFKDQQHO. For every distribution chain, you must clearly define whether it is to be used for supplying FRQVXPHUV (from stores) or for supplying VWRUHV (from distribution centers). There are indicators for this purpose. The reason for this distinction is that sales prices are generally defined for a distribution chain and not for individual sites or customers. So if the same distribution chain is used for supplying both stores and consumers, then stores will be charged the same by a distribution center as consumers are charged by a store, using the selling price defined at distribution chain level. The same applies for the determination of the units of measure to be used for each delivery. It would be very unusual for stores and their consumers to pay the same for merchandise. But it is easy to avoid this in the system by using separate distribution chains to supply stores and consumers. In Customizing you define the distribution chains for which a VLWH can deliver merchandise. No site can deliver merchandise until it has been assigned to a distribution chain. For each distribution chain (sales organization and distribution channel) there is a UHIHUHQFH GLVWULEXWLRQFKDQQHO for customer and article master data, and also for condition data and sales document types. The data used for each of these areas is that of the reference distribution channel rather than that of the original distribution channel. You specify various data for the combination of distribution chain and DUWLFOH, including sales unit and delivering site. The distribution chain is used to target a particular group of customers. It attaches a permanent (“static”) description to its sites which associates them with the distinctive form typical of that distribution chain. The distribution chain to site assignment is important for the Retail Information System. This static assignment is made in site maintenance in the general organizational data for the site.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH'LYLVLRQ

2UJDQL]DWLRQDO6WUXFWXUH'LYLVLRQ Articles are assigned uniquely (client-wide) to one division. Divisions have two main applications: They are organizational units for sales and distribution and they are also necessary for EXVLQHVVDUHDDFFRXQWDVVLJQPHQW for logistics transactions in Financial Accounting. Divisions can be used to describe specific product groups and can form the basis for sales statistics, for example. Divisions are assigned to VDOHVRUJDQL]DWLRQV. For each combination of sales organization and division there is a UHIHUHQFHGLYLVLRQ for customer and article master data, and also for condition data and sales document types. This allows the data in the reference division to be used in the original division too. Divisions are not used for any other functions in SAP Retail. Nevertheless, a single dummy division is provided where necessary.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH6DOHV$UHD

2UJDQL]DWLRQDO6WUXFWXUH6DOHV$UHD Another common term in the SAP system is VDOHVDUHD. This is the combination of a GLVWULEXWLRQ FKDLQ (a sales organization and a distribution channel) and a GLYLVLRQ. Since divisions are not actively used in SAP Retail, however, sales areas are of little significance here and can largely be seen as synonymous with distribution chains. Just as the purchasing organization plays an important role in calculation schema determination in Purchasing, the sales area (together with the document schema and the customer schema) is used to determine the VDOHVSULFHFDOFXODWLRQVFKHPD in Sales Price Calculation. Each VLWH is assigned one sales area, and therefore one distribution chain as well, permanently (“statically”) in site maintenance. The sales organization does not necessarily have to belong to the same company code as the site. If a site is to be supplied by other sources, you can define (in site maintenance) the sales areas, and therefore distribution chains, via which the site is allowed to procure merchandise. The “static” sales area determines the sales prices and assortments of a site, and frequently the internal and external presentation, too. Sales areas appear in all the main sales and distribution documents, including customer inquiries, customer quotations, sales orders, customer outline agreements, deliveries and billing documents. Sales areas are used for updates in the Sales Information System.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH6DOHV2IILFH

2UJDQL]DWLRQDO6WUXFWXUH6DOHV2IILFH A sales office is an organizational unit in sales and distribution which is responsible for sales within a specific geographical area. Sales offices are optional. A sales office can be assigned to one or several GLVWULEXWLRQFKDLQV. Sales offices are used in sales transactions in the Sales and Distribution component. They can be used for reporting purposes. A store, in its role as the customer of a sales area, can be assigned a sales office which is responsible for internal sales to this store. Regional sales managers are common in the retail sector. They can be represented in the system by sales offices with the appropriate employees assigned. This UHJLRQDOVDOHVPDQDJHU is then responsible for supplying the stores assigned to him with merchandise. You can also treat each VWRUH as a sales office. This enables you to obtain statistics on the sales volume and revenue that a store achieves through SD sales orders. (PSOR\HHV can be assigned to a sales office.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH6DOHV*URXS

2UJDQL]DWLRQDO6WUXFWXUH6DOHV*URXS Distribution chains can be subdivided into sales groups (with a sales manager for each, for example). Sales groups can be used for reporting purposes. A store, in its role as customer, can be assigned a sales group which is responsible for sales to this store. You can also base sales groups in a VWRUH. These sales groups are then responsible for SD sales orders in that store. (PSOR\HHV can be assigned to a sales group.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH6LWH

2UJDQL]DWLRQDO6WUXFWXUH6LWH A site is a store, a distribution center or a production location. In SAP Retail, the site is the organizational level at which merchandise replenishment is planned and stocks are managed. A store is assigned one SXUFKDVLQJRUJDQL]DWLRQ and one VDOHVDUHD (sales organization, distribution channel and division) and thereby also a GLVWULEXWLRQFKDLQ to which the store belongs and which is used primarily for intercompany billing purposes. The store must be authorized to receive goods from the sales area to which the supplying distribution center belongs. If it is to be possible for merchandise to be transferred from one store to another, then the same applies: the recipient store must be authorized to receive goods from the sales area to which the supplying store belongs. Each distribution center is assigned a purchasing organization (and, if required, a sales area) for determining warehouse transfer prices and units of measure. A distribution center can also be assigned to a VLWH (normally to itself) and a GLVWULEXWLRQFKDLQ (for determining sales prices). These assignments enable merchandise in the distribution center to be valuated at retail prices. This sort of valuation is most common in the apparel industry. Each site belongs to exactly one FRPSDQ\FRGH.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH6LWH*URXS

2UJDQL]DWLRQDO6WUXFWXUH6LWH*URXS 6LWHV can be grouped together using the Classification System. For this to be possible, at least one FODVVW\SH has to be defined in the Classification System. $SSOLFDWLRQJURXSV are defined in Customizing and are assigned the class type required for creating the relevant site groups. This class type uses the customer number of the site as the key. The application groups Allocation Table, Promotions, Season and Labeling are predefined to allow these applications to work with the intended site groups. Site groups operate entirely independently of company codes, distribution chains and other fixed organizational structures.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH&XVWRPHU

2UJDQL]DWLRQDO6WUXFWXUH&XVWRPHU Customers are the organizational units that buy merchandise from your retailing system. The two main types of customer are the non-identifiable customer (consumer), generally used to represent customers who buy merchandise from stores, and the named customer, for whom a customer master record exists in R/3. Customer records can be created in a simple form (for natural persons) or in a more complex form which allows the use of sales and distribution functionality (external customers, for example). The latter type of customer master record can be created not only for external customers but also for the sites in your own company that procure merchandise from a distribution center. If returns from a site to a vendor are to be processed with the aid of sales and distribution documents, the vendor must also be created as a customer in the system. Every VLWH always also exists as a customer in the system. The corresponding customer master record is created automatically in site maintenance.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH9HQGRU

2UJDQL]DWLRQDO6WUXFWXUH9HQGRU Vendors are the organizational units that deliver merchandise to sites or customers (the latter is possible in wholesale, for example, when a third-party arrangement exists). These vendors are normally external suppliers. Whether VLWHV exist as vendors in the system depends on the site category: stores are not defined as vendors but distribution centers usually are, because a DC has a vendor function from the point of view of stores. If returns from a site to a vendor are to be processed with the aid of sales and distribution documents, the vendor must also be created as a FXVWRPHU in the system. This will apply if delivery documents are to be generated and billed in the system for returns from a distribution center to a vendor, for instance.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH6WRFN3ODQQHU*URXS

2UJDQL]DWLRQDO6WUXFWXUH6WRFN3ODQQHU*URXS Sites are assigned stock planner groups, which are responsible for requirements planning. The assignment of a stock planner group to a site is dependent on the article involved. If a stock planner in a stock planner group has ordering autonomy, then the purchasing group that has been assigned to the stock planner in the user master will automatically be copied to purchase orders.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH6WRUDJH/RFDWLRQ

2UJDQL]DWLRQDO6WUXFWXUH6WRUDJH/RFDWLRQ Stocks of an article can be managed within a VLWH in different storage locations to differentiate, for example, between the stock stored for returns, promotions and cross-docking. To structure the complex warehouses that are typical in retailing, each VWRUDJHORFDWLRQ can be divided into warehouse numbers, storage types and storage bins using the Warehouse Management System. Storage locations are intended to represent areas in a warehouse. This differentiation between stocks is therefore of most relevance to distribution centers. If stock is to be managed on an article basis, storage locations must also be managed.

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH'HSDUWPHQW5HFHLYLQJ3RLQWDQG8QORDGLQJ3RLQW

2UJDQL]DWLRQDO6WUXFWXUH'HSDUWPHQW5HFHLYLQJ3RLQW DQG8QORDGLQJ3RLQW 'HILQLWLRQ Departments are subdivisions of a ship-to party. These might be, for example, different departments in a store, doors in a distribution center, or areas in a manufacturing plant. Departments are assigned to receiving points, which in turn are assigned to unloading points. One receiving point may have several departments assigned to it, but each department is assigned to only one receiving point. By knowing a department, you can therefore also determine the receiving point and the unloading point. Using departments and receiving points enables you to more finely specify the final destination for a shipment or portions of a shipment, thus reducing the time it takes for the goods to become available for the recipient’s use or sale. ´ A pallet load of merchandise is delivered to Door 1 at a department store (unloading point). The shipment is broken down and delivered to one or more floors (internal receiving points). From there the packages are delivered to one or more departments, such as Housewares, Home Entertainment, Health & Beauty Aids, or Women’s Fashion.

8VH •

Sales orders The receiving point and department are located on the Business Data Detail Shipment screen, either at the header or item level. If the header contains this information, this becomes the default for all items, but you can override it for individual items if you wish. Items in a sales order may have different receiving points and/or departments.

•

Picking lists and delivery notes You can print the receiving point and department on picking lists and delivery notes. If this information was included in the sales order, then it will automatically be inserted in these other documents; otherwise, you can enter it manually. (However, picking lists and delivery notes are not split by receiving point or department.)

•

Billing documents You can specify that the department and receiving point are to be printed on billing documents. You can also specify that invoices are to be split by receiving point and department.

In Customizing for Sales (3URFHVVLQJVDOHVRUGHUV→0DLQWDLQSURPRWLRQUHFHLYLQJSRLQW GHWHUPLQDWLRQSHUVDOHVRUGHUGRFXPHQWW\SH) you can specify for each type of document whether or not automatic department and receiving point determination is to be done.

6WUXFWXUH The department and receiving points are fields in sales orders and delivery notes.



-XQH

6$3$*

6$35HWDLO 2UJDQL]DWLRQDO6WUXFWXUH'HSDUWPHQW5HFHLYLQJ3RLQWDQG8QORDGLQJ3RLQW

,QWHJUDWLRQ The system can automatically determine the appropriate department and receiving point for an article. To enable this: •

For external customers, you assign merchandise categories in Customer Master Data.

•

For internal sites (for example, stores or distribution centers), you assign merchandise categories in Site Master Data.

In either case, you then assign valid departments and receiving points to the customer or site, and a department to each merchandise category. A merchandise category can only have one department. When you enter an article on a sales order, for example, the system checks the merchandise category to which the article belongs, then checks the merchandise category information for that site or customer and locates the corresponding department and receiving point for the article. 6HHDOVR Site: Definitions [Page 123]

-XQH



6$35HWDLO

6$3$*

2UJDQL]DWLRQDO6WUXFWXUH6DOHV'HSDUWPHQW

2UJDQL]DWLRQDO6WUXFWXUH6DOHV'HSDUWPHQW Stores can be divided into GHSDUWPHQWV. Sales departments bundle together the merchandise categories in a store and determine procurement activities in the store. Please note: if an article in a store is also sold in departments other than the one assigned via the merchandise category, department-based sales statistics can only be generated accurately if the relevant department can be determined from the sales transaction (if, for example, the department is included in the information provided by the POS system). The same applies for layout-based statistics, such as sales area profitability, for example. This is not contained in the standard information structures. Each department can be assigned a UHFHLYLQJSRLQW. 6HHDOVR Site: Definitions [Page 123]



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ

%DFNJURXQG3URFHVVLQJ This section lists all the key retail-specific reports in SAP Retail that are run in the background. The following questions are addressed: •

What are the reports used for? The reports are used for a number of different tasks, such as making mass changes or creating worklists.

•

Are there any prerequisites? The prerequisites for running the report are described. In some cases you have to run the reports in a certain order.

•

What is the recommended procedure for running the report? This information tells you whether a report should be run periodically (for example, daily or monthly) or only in certain circumstances.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ6LWH

%DFNJURXQG3URFHVVLQJ6LWH This section lists and briefly describes all of the important retail-specific reports in the Site environment.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ6HWWLQJ&HQWUDO%ORFNIRU6LWHV

%DFNJURXQG3URFHVVLQJ6HWWLQJ&HQWUDO%ORFNIRU6LWHV 8VH Report 5::/2&.'sets central blocks (delivery blocks, invoicing blocks and order blocks) in line with the blocking profile if the sites are blocked on the current date.

$FWLYLWLHV We recommend you run the report daily.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ&RQGLWLRQV

%DFNJURXQG3URFHVVLQJ&RQGLWLRQV This section lists and briefly describes all of the important retail-specific reports in the environment of Conditions.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ*HQHUDWLQJD:RUNOLVWRI&KDQJHG&RQGLWLRQV

%DFNJURXQG3URFHVVLQJ*HQHUDWLQJD:RUNOLVWRI &KDQJHG&RQGLWLRQV 8VH Report 50(%(,1 finds all the changed conditions for a specific period for the selected document categories. It generates a separate worklist for each document category selected. You can define which condition changes are relevant for each document category in Customizing. The worklists have various functions, including: •

Worklists for purchasing documents (purchase orders and scheduling agreements) The worklist can be processed further by report 50(%(,1. This determines all documents containing changed conditions. These documents are then updated.

•

Worklist for Pricing The worklist can be processed further by report 5:9.3. This determines all price calculations based on changed conditions. The price calculations are updated, with the period of validity being taken into account, and put into the pricing worklist.

•

Worklist for load building

Worklists for purchasing documents and for Pricing can be processed together by report 50(%(,1

$FWLYLWLHV We recommend you run the report periodically. The time between running the report depends on the number of condition changes that are made each day.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ$GMXVWLQJ'RFXPHQWVDIWHU&RQGLWLRQ&KDQJHV

%DFNJURXQG3URFHVVLQJ$GMXVWLQJ'RFXPHQWVDIWHU &RQGLWLRQ&KDQJHV 8VH Worklists for purchasing documents and for Pricing created by report 50(%(,1 can be processed together by report 50(%(,1

3UHUHTXLVLWHV You must run report 50(%(,1 beforehand. This determines and collects the conditions with the relevant changes.

$FWLYLWLHV We recommend you run the report periodically. The time between running the report depends on the number of condition changes that are made each day.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ$VVRUWPHQW

%DFNJURXQG3URFHVVLQJ$VVRUWPHQW This section lists and briefly describes all of the important retail-specific reports in the environment of Assortments. In the 0DVVPDLQWHQDQFH screen of assortment processing, you can choose the -RERYHUYLHZ menu option to have the system analyze how the report is running.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ9DOXH2QO\$UWLFOH/LVWLQJ

%DFNJURXQG3URFHVVLQJ9DOXH2QO\$UWLFOH/LVWLQJ 8VH Report program 5:6257 generates listing conditions and article master data for value-only articles on the basis of the following changes: •

The first time the articles in a merchandise category are listed in an assortment owner.

This is the only way to list hierarchy articles and other types of value-only article. If you wish, you can use this report program to list all value-only articles in all assortment owners. This enables articles from any merchandise category to be sold at the POS.

$FWLYLWLHV We recommend you run the report daily. Report program 5:6257 is a prerequisite for POS outbound. For reasons of system performance, it should be scheduled to run before report program 5:6257 ("&KDQJHVDIWHU &RUUHFWLRQV").



-XQH

6$3$*

6$35HWDLO

%DFNJURXQG3URFHVVLQJ&KDQJH$VVRUWPHQW$XWRPDWLFDOO\)ROORZLQJ0DVWHU'DWD&KDQJHV

%DFNJURXQG3URFHVVLQJ&KDQJH$VVRUWPHQW $XWRPDWLFDOO\)ROORZLQJ0DVWHU'DWD&KDQJHV 8VH Report program 5:627 uses change documents to identify changes to master data and then adjusts the assortment accordingly. It can identify changes to the following types of master data: •

Site/merchandise category

•

Sources of supply for articles

•

Site layout

•

Site classification

•

Supplying site

$FWLYLWLHV We recommend you run the report daily. It is a prerequisite for POS outbound processing.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ$VVRUWPHQW/LVW

%DFNJURXQG3URFHVVLQJ$VVRUWPHQW/LVW This section lists and briefly describes all of the important retail-specific reports in the assortment list environment.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ,QLWLDOL]LQJ2XWERXQG$VVRUWPHQW/LVW

%DFNJURXQG3URFHVVLQJ,QLWLDOL]LQJ2XWERXQG $VVRUWPHQW/LVW 8VH Report 5:'%%,1,is used for the initial transport of the assortment list/shelf-edge labeling data to stores with the appropriate sales organization, distribution chain and site, using selectable assortment list categories.

$FWLYLWLHV The report is only run when this data is transported to the stores for the first time. If the data is transported again, you use report 5:'%%83'

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ2XWERXQG3URFHVVLQJIRU$VVRUWPHQW/LVW

%DFNJURXQG3URFHVVLQJ2XWERXQG3URFHVVLQJIRU $VVRUWPHQW/LVW 8VH Report 5:'%%83' sends the relevant data to the stores.

3UHUHTXLVLWHV Assortment report 5:6257 must run beforehand.

$FWLYLWLHV It is not necessary to run the report daily. We recommend that you run the report weekly.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ3URPRWLRQ

%DFNJURXQG3URFHVVLQJ3URPRWLRQ This section lists and briefly describes all of the important retail-specific reports in the Promotion environment.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ0HVVDJH%XQGOLQJ

%DFNJURXQG3URFHVVLQJ0HVVDJH%XQGOLQJ 8VH Report 5:1$6793 generates group NAST records from the individual NAST records created using output determination. This sorts article-related data at site level. When creating a promotion, start report 5:1$6793. The group NAST records generated like this are processed by the output processing program 561$67. A paper printout is then made.

3UHUHTXLVLWHV You should run report 5:1$6793 immediately before report 561$67.

$FWLYLWLHV We recommend you run the report daily.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ3ULFLQJ

%DFNJURXQG3URFHVVLQJ3ULFLQJ This section lists and briefly describes all of the important retail-specific reports in the environment of Pricing.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ3ULFLQJ:RUNOLVW%DVHGRQ&KDQJHVWR)DFWRUV5HOHYDQWWR 3ULFLQJ

%DFNJURXQG3URFHVVLQJ3ULFLQJ:RUNOLVW%DVHGRQ &KDQJHVWR)DFWRUV5HOHYDQWWR3ULFLQJ 8VH Report 5:9.3 determines all those price calculations that are based on conditions that have changed. The price calculations are updated, with the period of validity being taken into account, and put into the pricing worklist. If you also want to automatically adjust purchasing documents, you can run report 50(%(,1 instead of generating a pricing worklist.

3UHUHTXLVLWHV Before you generate the pricing worklist, you must run the report 50(%(,1. This finds and assembles the changed conditions for further processing.

$FWLYLWLHV We recommend you run the report periodically. The time between running the report depends on the number of condition changes that are made each day.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ5HTXLUHPHQWV3ODQQLQJ

%DFNJURXQG3URFHVVLQJ5HTXLUHPHQWV3ODQQLQJ This section lists and briefly describes all of the important retail-specific reports in the environment of Requirements Planning.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ)RUHFDVWSHU3HULRG,QGLFDWRU

%DFNJURXQG3URFHVVLQJ)RUHFDVWSHU3HULRG,QGLFDWRU 8VH Report 50352* for the forecast run is scheduled depending on the period lengths that are used. All articles for a site are always processed with a specified period indicator.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ7RWDO3ODQQLQJSHU6LWH

%DFNJURXQG3URFHVVLQJ7RWDO3ODQQLQJSHU6LWH 8VH Report 50053provides a purchase order proposal for all articles for a site with changes relevant to requirements planning (reorder point/ordering day reached) In reorder point planning, the period depends on how many articles reach the reorder point at the same time. In time-phased planning, the period depends on how the articles are distributed over the ordering days. Usually, not all the articles in a site are planned automatically, i.e. with a purchase order proposal. Total planning can be processed in parallel.

3UHUHTXLVLWHV Report 50352*must run prior to requirements planning.

$FWLYLWLHV We recommend you run the report daily.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ$OORFDWLRQ

%DFNJURXQG3URFHVVLQJ$OORFDWLRQ This section lists and briefly describes all of the important retail-specific reports in the environment of Stock Allocation.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ0HVVDJH%XQGOLQJ

%DFNJURXQG3URFHVVLQJ0HVVDJH%XQGOLQJ 8VH Report 5:1$6793 generates group NAST records from the individual NAST records created using output determination. This sorts article-related data at site level. When creating a promotion, start report 5:1$6793. The group NAST records generated like this are processed by the output processing program 561$67. A paper printout is then made.

3UHUHTXLVLWHV You should run report 5:1$6793 immediately before report 561$67.

$FWLYLWLHV We recommend you run the report daily.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ2UGHULQJ

%DFNJURXQG3URFHVVLQJ2UGHULQJ This section lists and briefly describes all of the important retail-specific reports in the environment of Ordering.



-XQH

6$3$*

6$35HWDLO

%DFNJURXQG3URFHVVLQJ$GMXVWLQJ3XUFKDVLQJ'RFXPHQWVDIWHU&RQGLWLRQ&KDQJHV

%DFNJURXQG3URFHVVLQJ$GMXVWLQJ3XUFKDVLQJ 'RFXPHQWVDIWHU&RQGLWLRQ&KDQJHV 8VH Report RMEBEIN determines purchasing documents (purchase orders and delivery schedules) containing changed conditions. These documents are then updated. If you also want to update all price calculations in which changed conditions appear and put them in the pricing worklist, use report 50(%(,1 to generate the pricing worklist.

3UHUHTXLVLWHV You must run report 50(%(,1 beforehand. This determines and collects the changed conditions.

$FWLYLWLHV We recommend you run the report periodically. The time between running the report depends on the number of condition changes that are made each day.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ,QYRLFH9HULILFDWLRQ

%DFNJURXQG3URFHVVLQJ,QYRLFH9HULILFDWLRQ This section lists and briefly describes all of the important retail-specific reports in the environment of Invoice Verification.



-XQH

6$3$*

6$35HWDLO

%DFNJURXQG3URFHVVLQJ,PPHGLDWH,QYRLFH9HULILFDWLRQRU3HULRGLF,QYRLFH9HULILFDWLRQ

%DFNJURXQG3URFHVVLQJ,PPHGLDWH,QYRLFH9HULILFDWLRQ RU3HULRGLF,QYRLFH9HULILFDWLRQ 8VH Report 50%$%*executes invoice verification for invoices which have ,PPHGLDWHLQYRLFH YHULILFDWLRQor 3HULRGLFLQYRLFHYHULILFDWLRQset as the invoice verification category.

$FWLYLWLHV If ,PPHGLDWHLQYRLFHYHULILFDWLRQis set, the report is started during opening hours (8:00 - 17:00). If 3HULRGLFLQYRLFHYHULILFDWLRQis set, the report is started once or twice during the day, at times when the system load is low. This should be clarified with Financial Accounting. It is possible to restrict the report to specific vendors. This allows you to divide processing up into a number of jobs.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ3UHSDULQJWKH$GYDQFH5HWXUQIRU7D[RQ6DOHV3XUFKDVHVIRU 3DUNHG'RFXPHQWV

%DFNJURXQG3URFHVVLQJ3UHSDULQJWKH$GYDQFH5HWXUQ IRU7D[RQ6DOHV3XUFKDVHVIRU3DUNHG'RFXPHQWV 8VH Report 50%$%*formats parked vendor invoices, and vendor invoices that have not yet been correctly checked, for Financial Accounting report 5)8069(advance return for tax on sales/purchases).

$FWLYLWLHV This report is executed as and when required before Financial Accounting report 5)8069is executed.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ6XEVHTXHQW(QGRI3HULRG 6HWWOHPHQW

%DFNJURXQG3URFHVVLQJ6XEVHTXHQW(QGRI3HULRG 6HWWOHPHQW This section lists and briefly describes all of the important retail-specific reports in the environment of Subsequent (End-of-Period) Settlement.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ6HWWOLQJ5HEDWH$UUDQJHPHQWV

%DFNJURXQG3URFHVVLQJ6HWWOLQJ5HEDWH$UUDQJHPHQWV 8VH Report 5:0%21executes settlement of rebate arrangements.

3UHUHTXLVLWHV It is dependent on the planned settlement dates (that is the end of the validity period for the condition records) entered in Customizing. The runtime depends on the volume of vendor business volume data, purchase organization, purchasing groups, merchandise categories, tax code and settlement type.

$FWLYLWLHV You execute this report as and when required.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ([WHQVLRQRI3HULRGLF5HEDWH$UUDQJHPHQWV

%DFNJURXQG3URFHVVLQJ([WHQVLRQRI3HULRGLF5HEDWH $UUDQJHPHQWV 8VH Report 5:0%21extends periodic rebate arrangements.

$FWLYLWLHV You should schedule the report in good time before the dates entered in Customizing, that is, before the first purchase order is created. You execute this report as and when required.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ&RPSLODWLRQRI6WDWLVWLFVDQG5HWURDFWLYH8SGDWLQJRI9HQGRU %XVLQHVV9ROXPH

%DFNJURXQG3URFHVVLQJ&RPSLODWLRQRI6WDWLVWLFVDQG 5HWURDFWLYH8SGDWLQJRI9HQGRU%XVLQHVV9ROXPH 8VH You can use report 5:0%21for the following activities: •

&RPSLODWLRQRIVWDWLVWLFV You can recompile vendor business volume statistics if the statistical data is incorrect. This may be necessary if the update of statistical data contained errors, for example.

•

5HWURDFWLYH8SGDWLQJRI%XVLQHVV9ROXPH You can retroactively compile vendor business volume statistics for a past period. This may be necessary if you agree a retroactive arrangement that is to be taken into account for business volume that has already recorded.

$FWLYLWLHV The report should only be run for individual cases because it takes considerable time and resources. You execute this report as and when required. 6HHDOVR Subsequent (End-of-Period) Settlement: Retroactive Updating of Vendor Business Volumes [Page 741]



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ,QYHQWRU\0DQDJHPHQW

%DFNJURXQG3URFHVVLQJ,QYHQWRU\0DQDJHPHQW This section lists and briefly describes all of the important retail-specific reports in the environment of Inventory Management.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ6DOHV3ULFH5HYDOXDWLRQ

%DFNJURXQG3URFHVVLQJ6DOHV3ULFH5HYDOXDWLRQ 8VH Report 5:9.8 generates lists of articles whose sales prices have changed in the selected period. This list has to be created for articles to be revaluated that are managed on a value-only basis and can be used as: a list for counting the stock •

an entry help for manually re-valuating stock online

$FWLYLWLHV Depending on the number of sites selected and the length of the period under review, the runtime of the report can be very long. You should therefore only run the report when necessary and when the load on the system is low.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ6KLSSLQJDQG7UDQVSRUWDWLRQ

%DFNJURXQG3URFHVVLQJ6KLSSLQJDQG7UDQVSRUWDWLRQ This section lists and briefly describes all of the important retail-specific reports in the Shipping and Transportation environment.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ5HSOHQLVKPHQWIRU)L[HG%LQV

%DFNJURXQG3URFHVVLQJ5HSOHQLVKPHQWIRU)L[HG%LQV 8VH There are two reports within the Warehouse Management System that pertain to picking: •

:DUHKRXVH5HSOHQLVKPHQWIRU)L[HG6WRUDJH%LQV (RLLNACH1): This report shows which fixed storage bins in the warehouse currently have insufficient picking stock. The system does not do any planning based on the results.

•

3ODQQLQJ5HSOHQLVKPHQWIRU)L[HG6WRUDJH%LQV(RLLNACH2): This report shows which fixed storage bins have insufficient picking stock to fill deliveries scheduled for a specified time frame and shipping point and also carries out the planning to remedy the situation.

In both cases, the system generates transfer requirements to refill the fixed storage bins with sufficient replenishment stock for picking. It takes into account existing transfer requirements and transfer orders. The report (RLLNACH2) can be run at the end of the day so that you can see which fixed storage bins need to be refilled for the following day’s picking. The system will generate transfer requirements for that day. You can then create transfer orders from the transfer requirements, physically move the stock, and then confirm the transfer orders in the system, at which point the system posts the movement. The system views this kind of replenishment as a movement of stock from one storage type to another. Therefore, the selection screen for the report requires you to enter the storage type of the fixed storage bins in question (i.e., the destination storage type of the transfer requirements). You must also enter the site and warehouse number. You can further restrict the relevant deliveries by specifying the shipping point, multiple processing number, picking date, and goods issue date (usually the following day).



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ5HSOHQLVKPHQW

%DFNJURXQG3URFHVVLQJ5HSOHQLVKPHQW This section lists and briefly describes all of the important retail-specific reports in the environment of Replenishment Control.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ)RUHFDVW:HLJKWLQJ)DFWRUV

%DFNJURXQG3URFHVVLQJ)RUHFDVW:HLJKWLQJ)DFWRUV 8VH Report 5:53/ recalculates the forecast weighting factors for a year. Note: The report overwrites the old forecast weighting factors without any warning!

3UHUHTXLVLWHV Replenishment master data must be maintained for the required articles.

$FWLYLWLHV We recommend you run the report once a year.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ$XWR5HSOHQLVKPHQW

%DFNJURXQG3URFHVVLQJ$XWR5HSOHQLVKPHQW 8VH Report RWRPL001 executes automatic replenishment. On the basis of the current stock situation, the system calculates the requirements for the customer or the plant and creates purchase requisitions, purchase orders, sales orders or delivery schedules.

3UHUHTXLVLWHV Replenishment master data must be maintained for the required materials.

$FWLYLWLHV Execute as required.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ326,QWHUIDFH

%DFNJURXQG3URFHVVLQJ326,QWHUIDFH This section lists and briefly describes all of the important retail-specific reports in the POS Interface environment. POS inbound processing usually takes place overnight and is triggered by the POS converter (SCS) via RFC. RFC calls POS inbound function modules, which process the incoming data.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ,QLWLDOL]LQJ2XWERXQG3URFHVVLQJ

%DFNJURXQG3URFHVVLQJ,QLWLDOL]LQJ2XWERXQG 3URFHVVLQJ 8VH Report 5:'326,1 is used for the initial transport of master data to all stores using sales organization, distribution chain and site selection data.

$FWLYLWLHV The report is only run when this data is transported to the stores for the first time. If the data is transported again, you use report 5:'32683

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ3HULRGLF2XWERXQG3URFHVVLQJIRU6WRUHV

%DFNJURXQG3URFHVVLQJ3HULRGLF2XWERXQG3URFHVVLQJ IRU6WRUHV 8VH Report 5:53/ executes POS outbound processing. The quantity of data depends largely on the number of relevant master data changes.

3UHUHTXLVLWHV Assortment report 5:6257 must be executed beforehand.

$FWLYLWLHV We recommended you run this report daily after the store has closed. This requires a large amount of resources, but parallel processing is possible as the report can run simultaneously on all application servers. For further information see the report program documentation.



-XQH

6$3$*

6$35HWDLO

%DFNJURXQG3URFHVVLQJ5HSHDWLQJ7HUPLQDWHG%XIIHUHG326,QERXQG3URFHVVLQJ

%DFNJURXQG3URFHVVLQJ5HSHDWLQJ 7HUPLQDWHG%XIIHUHG326,QERXQG3URFHVVLQJ 8VH You use report 5:'$33to restart processing of IDocs that have been buffered or for which inbound processing was terminated.

$FWLYLWLHV •

7HUPLQDWHGLQERXQGSURFHVVLQJ You can start processing IDocs at any time online or via job planning.

•

%XIIHUHG,'RFV If you decide to buffer IDocs, you must schedule report 5:'$33for the time when you want to process the data.

For further information see the report documentation.

-XQH



6$35HWDLO

6$3$*

%DFNJURXQG3URFHVVLQJ5HSHDWLQJ8QVXFFHVVIXO326,QERXQG3URFHVVLQJ

%DFNJURXQG3URFHVVLQJ5HSHDWLQJ8QVXFFHVVIXO326 ,QERXQG3URFHVVLQJ 8VH You use report 5%'0$1,1to reprocess specific IDoc data that was not processed in a previous attempt.

$FWLYLWLHV If overnight inbound processing was unsuccessful, and the fault has been repaired (for example, missing master data has been entered), you can plan report 5%'0$1,1as a regular job or start it online. For further information see the report documentation.



-XQH

6$3$*

6$35HWDLO %DFNJURXQG3URFHVVLQJ,QIRUPDWLRQDQG3ODQQLQJ6\VWHP

%DFNJURXQG3URFHVVLQJ,QIRUPDWLRQDQG3ODQQLQJ 6\VWHP Report processing is not essential in the Information System. If certain functions (e.g. periodic exception analysis) are used, or large quantities of data are processed (e.g. creation of new statistics), reports are used. Requirements can be classified as follows: •

6WDQGDUGDQDO\VHV All standard analyses can be run as reports, e.g. as selection versions, in the case of evaluations that affect performance.

•

3HULRGLFRUHYHQWRULHQWHGHYDOXDWLRQVLQWKH(DUO\:DUQLQJ6\VWHP These evaluations must be run as reports.

•

)OH[LEOHDQDO\VHV These evaluations can be run as reports. This must be defined first. The evaluation can be started online or planned as a job.

•

&UHDWLRQRIQHZVWDWLVWLFV You must create new statistics using a report.

•

$GPLQLVWUDWLYHDFWLYLWLHV Tasks in this area, such as copying information structures, should be run as reports wherever possible.

-XQH



6$35HWDLO

6$3$*

%XVLQHVV3URFHVVHV

%XVLQHVV3URFHVVHV 8VH The following describes which business processes in SAP Retail are assigned to which organizational areas. The organizational areas are: •

Headquarters

•

Distribution center

•

Store

•

Sales office

The business processes are listed for each organizational area by subject area (such as Purchasing or Merchandise Logistics). By navigating in this way, you obtain an overview of the business processes, as it allows you to view the processes independently of the function documentation. Only certain processes are relevant for each individual organizational area. This narrows down the view on the documentation to one specific area, showing all the processes that are used in that area (for example, in the store).



-XQH

6$3$*

6$35HWDLO 3URFHVVHVDW+HDGTXDUWHUV

3URFHVVHVDW+HDGTXDUWHUV Usually members of this organizational area perform the following business functions:

0DVWHU'DWD 6LWH0DVWHU Site Processing [Page 132] Site Block [Page 140]

9HQGRU0DVWHU Vendor Processing [Page 216] Vendor Block [Page 226]

$UWLFOH0DVWHU Article Processing [Page 310] Article Block [Page 315]

0HUFKDQGLVH&DWHJRULHV Characteristics Processing [Page 399] Merchandise Category Processing [Page 339] Article and Merchandise Category Reclassification [Page 348]

&RQGLWLRQV0DVWHU Condition Processing (Vendor) [Page 362]

&XVWRPHU0DVWHU Customer Processing [Page 386] Customer Block [Page 389]

&ODVVLILFDWLRQ Characteristics Processing [Page 399] Reclassification of Objects in Hierarchical Class Types [Page 402]

6WUDWHJLF6DOHV $VVRUWPHQW3ODQQLQJ Assortment Module Maintenance [Page 436] Assortment Assignment Maintenance [Page 438] Assortment Processing [Page 441] Assortment User Assignment Maintenance [Page 443] Assortment List Generation [Page 445]

-XQH



6$35HWDLO

6$3$*

3URFHVVHVDW+HDGTXDUWHUV

3URGXFW&DWDORJ Product Catalog Processing [Page 467]

3URPRWLRQV Promotion Processing [Page 517]

3ULFLQJ Sales Price Calculation [Page 560] Pricing Work List Processing [Page 563]

3XUFKDVLQJ $OORFDWLRQ Allocation Table Processing [Page 626] Allocation Rule Processing [Page 633] Allocation Rule Generation [Page 637] Generation of Documents Following On From the Allocation Table (Follow-On Document Generation) [Page 641] Allocation Table Notification Processing [Page 646] Adjusting the Allocation Table Referencing a Goods Receipt [Page 650]

2UGHULQJ Contract Processing [Page 688] Scheduling Agreement Processing [Page 693] Purchase Requisition Processing [Page 698] Purchase Requisition Assignment [Page 703]

,QYRLFH9HULILFDWLRQ Invoice Entry [Page 709] Difference Processing (Invoice Verification) [Page 711] Automatic Invoice Verification [Page 713] Blocking Reason Processing (Invoice Verification) [Page 716]

6XEVHTXHQW6HWWOHPHQW Volume Rebate Arrangement Processing (Vendor) [Page 768] Settlement Accounting: Conditions Requiring Subsequent Settlement (Vendor) [Page 776]

0HUFKDQGLVH/RJLVWLFV *RRGV5HFHLSW



-XQH

6$3$*

6$35HWDLO 3URFHVVHVDW+HDGTXDUWHUV

Goods Receipt Processing (Store) [Page 840]

,QYHQWRU\0DQDJHPHQW Reservation Processing [Page 887] Stock Transfer in a Single Step [Page 910] Stock Transfer in Two Steps [Page 917] Special Stock Movements (Store) [Page 928]

9DOXDWLRQ Sales Price Revaluation [Page 961]

,QYHQWRU\ Physical Inventory Processing [Page 1013] Physical Inventory (Store) [Page 1027]

6DOHV 6WRUH2UGHU Store Order Processing [Page 1097]

5HSOHQLVKPHQW Replenishment [Page 1124]

6DOHV2UGHU3URFHVVLQJ Sales Order Processing [Page 1143]

%LOOLQJ Billing Document Processing [Page 1154] Invoice List Processing [Page 1157] Rebate Settlement (Customer) [Page 1159]

'LVWULEXWHG5HWDLOLQJ 326,QWHUIDFH2XWERXQG POS Outbound: Master Data Preparation [Page 1180]

326,QWHUIDFH,QERXQG Sales/Returns (Store) [Page 1202] Financial Transactions (Store) [Page 1204] Master Data Processing (Store) [Page 1205]

-XQH



6$35HWDLO

6$3$*

3URFHVVHVLQ'LVWULEXWLRQ&HQWHUV

3URFHVVHVLQ'LVWULEXWLRQ&HQWHUV Usually members of these organizational areas perform the following business functions:

6WUDWHJLF6DOHV $VVRUWPHQW3ODQQLQJ Assortment Module Maintenance [Page 436] Assortment Assignment Maintenance [Page 438] Assortment Processing [Page 441] Assortment User Assignment Maintenance [Page 443] Assortment List Generation [Page 445]

3XUFKDVLQJ $OORFDWLRQ Allocation Table Processing [Page 626] Allocation Rule Processing [Page 633] Allocation Rule Generation [Page 637] Generation of Documents Following On From the Allocation Table (Follow-On Document Generation) [Page 641] Allocation Table Notification Processing [Page 646] Adjusting the Allocation Table Referencing a Goods Receipt [Page 650]

2UGHULQJ Purchase Requisition Processing [Page 698]

0HUFKDQGLVH/RJLVWLFV *RRGV5HFHLSW Goods Receipt Planning [Page 827] Rough Goods Receipt Processing [Page 829] Goods Receipt Processing with Reference Document [Page 831] Goods Receipt Processing Without Reference Document [Page 835] Return Delivery [Page 842]

,QYHQWRU\0DQDJHPHQW Stock Transfer in a Single Step [Page 910] Stock Transfer in Two Steps [Page 917] Sales Price Revaluation [Page 961]



-XQH

6$3$*

6$35HWDLO 3URFHVVHVLQ'LVWULEXWLRQ&HQWHUV

:DUHKRXVH0DQDJHPHQW Stock Placement Processing [Page 967] Stock Placement Strategies [Page 971] Stock Removal Processing [Page 972] Stock Removal Strategies [Page 976] Shipping Unit Storage [Page 977] Replenishments to Be Planned for Fixed Storage Bins [Page 983]

,QYHQWRU\ Physical Inventory Processing [Page 1013]

6KLSSLQJ Route Schedule Processing [Page 1034] Delivery Processing [Page 1037] Packing Processing [Page 1047] Goods Issue Processing [Page 1053]

6DOHV 5HSOHQLVKPHQW Replenishment [Page 1124]

-XQH



6$35HWDLO

6$3$*

3URFHVVHVLQ6WRUHV

3URFHVVHVLQ6WRUHV Usually members of these organizational areas perform the following business functions:

6WUDWHJLF6DOHV $VVRUWPHQW3ODQQLQJ Assortment Module Maintenance [Page 436] Assortment Assignment Maintenance [Page 438] Assortment Processing [Page 441] Assortment User Assignment Maintenance [Page 443] Assortment List Generation [Page 445]

3XUFKDVLQJ $OORFDWLRQ Allocation Table Notification Processing [Page 646]

2UGHULQJ Purchase Requisition Processing [Page 698]

0HUFKDQGLVH/RJLVWLFV *RRGV5HFHLSW Goods Receipt Planning [Page 827] Rough Goods Receipt Processing [Page 829] Goods Receipt Processing with Reference Document [Page 831] Goods Receipt Processing Without Reference Document [Page 835] Goods Receipt (Store) [Page 837] Return Delivery [Page 842]

,QYHQWRU\0DQDJHPHQW Stock Transfer in a Single Step [Page 910] Stock Transfer in Two Steps [Page 917] Special Stock Movements (Store) [Page 928] Sales Price Revaluation [Page 961]

3K\VLFDO,QYHQWRU\ Physical Inventory Processing [Page 1013] Physical Inventory (Store) [Page 1027]

6DOHV



-XQH

6$3$*

6$35HWDLO 3URFHVVHVLQ6WRUHV

6WRUH2UGHU Store Order [Page 1093]

5HSOHQLVKPHQW Replenishment [Page 1124]

'LVWULEXWHG5HWDLOLQJ 326,QWHUIDFH,QERXQG Sales/Returns (Store) [Page 1202] Non-Cash Payment (Store) [Page 1203] Financial Transactions (Store) [Page 1204] Master Data Processing (Store) [Page 1205]

-XQH



6$35HWDLO

6$3$*

3URFHVVHVLQ6DOHV2IILFHV

3URFHVVHVLQ6DOHV2IILFHV Usually members of these organizational areas perform the following business functions:

0DVWHU'DWD &XVWRPHU0DVWHU Customer Processing [Page 386] Customer Block [Page 389]

6WUDWHJLF6DOHV $VVRUWPHQW3ODQQLQJ Assortment Module Maintenance [Page 436] Assortment Assignment Maintenance [Page 438] Assortment Processing [Page 441] Assortment User Assignment Maintenance [Page 443] Assortment List Generation [Page 445]

3URGXFW&DWDORJ Product Catalog Processing [Page 467]

3URPRWLRQV Promotion Processing [Page 517]

3ULFLQJ Sales Price Calculation [Page 560]

3XUFKDVLQJ 2UGHULQJ Purchase Requisition Processing [Page 698]

0HUFKDQGLVH/RJLVWLFV ,QYHQWRU\0DQDJHPHQW Reservation Processing [Page 887]

6DOHV 6DOHV2UGHU3URFHVVLQJ Sales Order Processing [Page 1143]

%LOOLQJ



-XQH

6$3$*

6$35HWDLO 3URFHVVHVLQ6DOHV2IILFHV

Billing Document Processing [Page 1154] Invoice List Processing [Page 1157] Rebate Settlement (Customer) [Page 1159]

-XQH



6$35HWDLO

6$3$*

0DVWHU'DWD

0DVWHU'DWD Master data contains all the most important information on sites, vendors, and customers as well as on all the articles involved. This information also includes pricing and cycle control data and is stored in the system for retrieval when the user processes business transactions. When master data is maintained in full and correctly, the time required to process transactions can be drastically reduced, as the system automatically copies the master data you have already maintained to the relevant fields. All types of master data can be grouped together in the Classification System and analyzed. This section describes the various types of master data and how you can work with them. The following types of master data exist in SAP Retail: •

Site [Page 113] The site master contains data on sites such as the address, assignment to other organizational units, size, opening hours, control information, classification information, departments, merchandise categories, and receiving points

•

Vendor [Page 148] The vendor master contains information on vendors such as name and address, the currency in which the vendor works, and the vendor number (used in SAP Retail as the account number).

•

Article [Page 232] The article master contains data on all the individual articles that a company purchases, sells or produces. An article master record includes information such as the unit of measure and the description of the article. Other SAP components access the data contained in the article master.

•

Merchandise category [Page 318] Articles can be grouped together into merchandise categories. These groups can serve as a basis for Inventory Management, analyses, and other logistics functions.

•

Conditions [Page 353] Conditions contain information on arrangements used for pricing in purchasing and sales. These can be freely defined and stored at a number of levels with relevant periods of validity.

•

Customer [Page 369] Master data can be stored for each individual customer. This includes general data such as the address, sales data (contact person, departments, merchandise categories and unloading points, for example) and accounting data (such as bank details).

6HHDOVR Organizational structure [Page 34] Classification [Page 394] Season [Page 471] POS interface - outbound [Page 1171]



-XQH

6$3$*

6$35HWDLO 6LWH

6LWH 3XUSRVH A site is an organizational unit used in SAP Retail to document goods stored in distribution centers and stores for the purposes of inventory management, and to model the associated business processes, such as goods receipt, physical inventory and goods issue. The site master contains information on all the sites, that is all distribution centers and stores, in your company. This information is stored in master records for each individual site. The data contained in a site’s master record then appears as default values for a wide variety of business processes.

,PSOHPHQWDWLRQ&RQVLGHUDWLRQV Storing the master records centrally and sharing them between applications means that you only have to enter data once. If a site has a change of address, for example, the new address only ever has to be entered once.

,QWHJUDWLRQ A site is an independent unit that has its own Inventory Management and orders its own stock. A site can, however, be considered as a customer, since sales functions, such as delivering and billing, are carried out by head office for the site. This is why a site is always maintained in SAP Retail in its capacity as a customer. A distribution center is also a vendor (creditor), as it supplies merchandise to other sites. %XVLQHVVSURFHVVHVDQG SURFHGXUHV

Organizational areas Headquarters [Page 103]

Site processing [Page 132]

•

Site block [Page 140]

•

Distribu tion Center [Page 106]

Store [Page 108]

Sales Office [Page 110]

6HHDOVR Organizational structure [Page 34] Vendor [Page 148] Customer [Page 369] Assortment: subsequent listing [Page 421]

-XQH



6$35HWDLO

6$3$*

)XQFWLRQV

)XQFWLRQV In this section the functions available for the current topic are described. Procedures that are not assigned to any specific business process are also documented here. Procedures assigned to a specific business process are found in the business process section of the current topic in the description of the steps in the process.



-XQH

6$3$*

6$35HWDLO 6LWH'LVWULEXWLRQ&KDLQVDQG6LWH&DWHJRULHV

6LWH'LVWULEXWLRQ&KDLQVDQG6LWH&DWHJRULHV Sites are grouped together in GLVWULEXWLRQFKDLQVfor marketing purposes. For example: •

Chain of supermarkets with the same logo

•

Home improvement centers in a company

•

Wholesale chains of a company

In SAP Retail, a distribution chain consists of a sales organization and a distribution channel. You can maintain data relevant to sales, such as conditions or assortments, for each distribution chain. For organizational reasons (compilation of statistics, for example), a site is assigned to only one distribution chain. However, deliveries can still be made to a distribution chain from a number of distribution centers. In the same way, one distribution center can supply goods to a number of distribution chains. Each site is part of a company code. It is an independent unit that has its own Inventory Management and orders its own stock. Goods are procured referencing one or more purchasing organizations and are sold referencing one or more distribution chains. In retailing, one distribution chain is defined as the default for store trading. There are two types of site in SAP Retail: •

'LVWULEXWLRQ&HQWHU Enables other sites and/or customers to be supplied quickly with goods A distribution center is assigned to a purchasing organization, and may also be assigned to a distribution chain for the purposes of sales price valuation, stock transfers and statistics. A distribution center can also supply a number of distribution chains. In the same way, a site can also be supplied with goods from different distribution chains.

•

6WRUH Location in which goods are put on sale to the consumer A store is assigned to one purchasing organization and one distribution chain.

-XQH



6$35HWDLO

6$3$*

6LWH1XPEHU$VVLJQPHQW

6LWH1XPEHU$VVLJQPHQW Every site master record is assigned a unique number for identification purposes. The number given to the customer and vendor master records assigned to the site is usually the same number as the site, but it can differ. You require this number to call the master record or enter purchase orders. ´ Wherever possible, customer and vendor master records should have the same number. This makes it easier for you to use the functions which are based on this data. The Classification System, for example, uses the customer number. Numerical site numbers are extended to ten-digit numbers in the vendor and customer data (e.g. site 2500, customer 0000002500). However, they can be used in the same way. When you create a site master record, you have to enter the number manually (referred to as external number assignment). The system makes sure that the number you enter has not been assigned to any other object. How numbers are assigned, and which number range is used, for vendors and customers is determined by the account group of the site profile you have to enter when you create a site master record.



-XQH

6$3$*

6$35HWDLO 6LWH6LWH3URILOHV

6LWH6LWH3URILOHV When you create a site master record, you have to specify a site profile. Site profiles are used to differentiate site categories (distribution center or store) and control maintenance functions. The following site profiles are available: •

Distribution center

•

Store without internal settlement All the transactions in the supply chain in this case take place within the same company code. From the point of view of the distribution center, no sales transaction takes place. The system therefore switches off the sales and billing screens in this case.

•

Store with internal settlement From the point of view of the distribution center, sales transactions involve different company codes. The sales and billing screens are available.

•

Store with external settlement Stores that do not belong to the company are supplied by the distribution center.

•

Wholesale customer This is a normal customer that is created as a site so that you can use site functions (such as the allocation tables, promotion, receiving points).

•

Franchisee A franchisee is a merchant who operates as an independent company funded by equity capital and offers goods or services using a standardized marketing strategy in stores owned by a franchiser.

Site profiles are assigned accounts groups (customer/vendor) and site categories (distribution center or store). The account groups mainly control number assignment and screen modification. You define the available site profiles in Customizing. ´ Once you have created a site you cannot change the site profile or the site category. Changes to the screen modification group in the site profile apply for all sites. However, changes to the site category only apply to sites created after you made the changes.

-XQH



6$35HWDLO

6$3$*

6LWH)UDQFKLVHH

6LWH)UDQFKLVHH A franchisee is a merchant who operates as an independent company funded by equity capital and offers goods or services using a standardized marketing strategy in stores owned by a franchiser. In the SAP system, a franchisee is modeled as a site in the site master. You must assign this site to a company code. There are two ways of doing this: •

If Financial Accounting is not active for the franchisee, it can be assigned to a company code which is used for all franchisees without Financial Accounting. This company code can be considered a “dummy” company code.

•

If Financial Accounting is active for the franchisee, it must be assigned to its own company code. All the stores of a franchisee are assigned to the appropriate company code. In this case, the company code is an additional grouping characteristic.

You can activate Inventory Management for a franchisee, regardless of whether it has its own company code or is assigned to a dummy company code. You must make the relevant Customizing settings for updating quantities and values for each material type. If Inventory Management is not active for a franchisee, the appropriate settings must be made for this in Customizing (updating quantities/values for each material type). The fact that there may not be a setting for a material type does not mean that quantities and values will automatically not be updated for the material type. If the settings are made for each material type, and updating quantities and values is not specified, the system does not create the required data retention levels in the article master. This avoids unnecessary data. If a franchisee has been assigned to a dummy company code, and Financial Accounting is subsequently activated, the franchisee can be assigned to its own company code in the site master. Special tools are available for copying franchisee data to the new company code.



-XQH

6$3$*

6$35HWDLO 6LWH'DWD6HWVDQG'DWD0DLQWHQDQFH/HYHOV

6LWH'DWD6HWVDQG'DWD0DLQWHQDQFH/HYHOV A site master record comprises the following data sets: •

General data

•

Customer Data

•

Vendor Data

*HQHUDOGDWD This contains information on the site that is valid for the whole client. This includes: •

Name and address of the site.

•

Organizational data on how the site is assigned to other organizational structures.

•

Opening times

•

Information on sales price valuation and the profiles assigned for value-based Inventory Management

•

Listing information

•

Purchasing data on replenishment planning, automatic purchase order creation, regular vendors, source list requirements and the region of supply

•

Information on interfaces for communicating with subsystems.

•

Layout data with information on total sales area, layout and area schemas.

•

Blocking information

•

Tax information for US sites (e.g. jurisdiction code)

The following data can also be stored in the site master record: •

Departments (per site)

•

Merchandise categories (per site)

•

Receiving points (per site)

•

Supplying sites (per merchandise category and site)

•

Merchant ID

&XVWRPHU'DWD Since a site performs the functions of a customer in certain cases, this set of data is the same as that in the customer master.

9HQGRU'DWD Since a site performs the functions of a vendor in certain cases, this set of data is the same as that in the vendor master. 6HHDOVR Vendor [Page 148]

-XQH



6$35HWDLO

6$3$*

6LWH'DWD6HWVDQG'DWD0DLQWHQDQFH/HYHOV Customer [Page 369]



-XQH

6$3$*

6$35HWDLO 6LWH5HIHUHQFH6LWH

6LWH5HIHUHQFH6LWH You can enter a reference site when you create a new site. The following data is copied from the reference site: *HQHUDOSODQWGDWD 2UJDQL]DWLRQDOGDWD •

Company code (table 002K, field BUKRS)

•

Purchasing organization (table 001W, field EKORG)

•

Sales organization (table 001W, field VKORG)

•

Distribution channel (table 001W, field VTWEG)

•

Division (table 001W, field SPART)

•

Sales district (table 001W, field BZIRK)

•

Sales office (table RF1, fields VKBUR and WRK)

&DOHQGDU •

Calendar (table 001W, field FABKL)

9DOXDWLRQ,QYHQWRU\0DQDJHPHQW •

Valuation area (table 001K, field BWKEY)

•

Valuation grouping code (table 001K, field BWMOD)

•

Profile for inventory management on value basis (table 001K, field WBPRO)

•

Indicator for sales price valuation (table 001K, field XVKBW)

•

Revaluation profile (table 001K, field UPROF)

•

Sales organization retail price reduction (table RF1, field BWVKO)

•

Distribution channel retail price reduction (table RF1, field BWVTW)

•

Negative stocks permitted (table 001K, field XBKNG)

•

Batch status management (table 001W, field CHAZV)

•

Stock correction tolerance (table 001K, field BDIFP)

•

Sales area determination (table 001W, field VTBFI)

/LVWLQJ •

Indicator for listing conditions (table RF1, field KZLIK)

•

Indicator for subsequent listing (table RF1, field NLMATFB)

•

Listing procedure for store types (table RF1, field LSTFL)

•

Basic listing rules (table RF1, field LIGRD)

5HSOHQLVKPHQWSODQQLQJ •

Requirements planning (table 001W, field BEDPL)

-XQH



6$35HWDLO

6$3$*

6LWH5HIHUHQFH6LWH •

SOP plant (table 001W, field WKSOP)

3XUFKDVLQJ •

Regular vendor (table 001W, field BZQHL)

•

Automatic purchase order conversion (table RF1, field AUTOB)

•

Source list requirement (table 001W, field KORDB)

•

Conditions at plant level (table 001W, field KKOWK)

•

Supply region (table 001W, field ZONE1)

'LVWULEXWLRQ •

Distribution profile (table 001W, field FPRFW) (up to now without function)

326,QWHUIDFH •

POS outbound profile (table RF1, field KOPRO)

•

POS inbound profile (table RF1, field INPRO)

•

Assortment list profile (table RF1, field BBPRO)

/D\RXW •

Layout ( table RF1, field LAYVR)

•

Area schema (table RF1, field FLVAR)

•

Sales area (table RF1, field VERFL)

•

Sales area unit (table RF1, field VERFE)

$GPLQLVWUDWLYHGDWD •

Node type supply chain network (table 001W, field NODETYPE)

5HIHUHQFH



•

Departments (table RF4)

•

Merchandise categories (table RF6)

-XQH

6$3$*

6$35HWDLO 6LWH'HILQLWLRQV

6LWH'HILQLWLRQV This section describes the relationship between merchandise categories, departments, receiving points and goods recipients. •

'HSDUWPHQWV A store can be divided into GHSDUWPHQWV and UHFHLYLQJSRLQWV. Stores are divided into departments for the purposes of retail management. Departments play an important role in store-internal logistics. A department can be assigned to one receiving point.

•

0HUFKDQGLVH&DWHJRULHV Information can be stored at VLWHPHUFKDQGLVHFDWHJRU\ level. This is important for the listing of articles and Inventory Management on a merchandise category level. A merchandise category can be assigned to a department at site level. Depending on the profile for value-based inventory management, you can define how inventory management is to be carried out per merchandise category. The merchandise category to which an article belongs allows the following information to be determined for the supply of a store with merchandise:

•

–

The department to which an article usually belongs. Example: Article 4711 belongs to merchandise category XY

–

The receiving point to which a department is assigned. Example: Department G is assigned receiving point 3rd floor

–

The unloading point to which the receiving point is assigned. Example: Receiving point 3rd floor is assigned unloading point DOCK1 and goods recipient 1023

5HFHLYLQJ3RLQWV A store can have more than one XQORDGLQJ point. The carrier delivers goods to these unloading points. A store has several GHSDUWPHQWV. Departments can be determined for every store and merchandise category. When goods are received in a store, the system can automatically determine the department for every item in the delivery. A store also has several UHFHLYLQJ points. Every receiving point can be assigned one of the unloading points. Every department can be assigned a receiving point (in the case of department stores, for example). The receiving point is located close to the goods recipient. The receiving point can be determined automatically via the merchandise category and the store concerned. This can be changed by the user, however. The receiving point can be printed on delivery documents. Only items destined for the same receiving point can be contained in the one package.

•

6XSSO\LQJ6LWHV Supplying (delivering) sites can be entered at merchandise category level to facilitate supply source determination. You can define a supplying site at site level as a default value. They can be maintained for different periods of validity.

•

0HUFKDQW,'

-XQH



6$35HWDLO

6$3$*

6LWH'HILQLWLRQV The merchant ID is used for the settlement of payments made with payment cards (credit cards, procurement cards etc.) with the clearing house. The merchant ID is issued to retailers by the clearing house. If a site communicates with different clearing houses, different merchant IDs are possible. 6HHDOVR Organizational structure [Page 34] SD - Sales and Distribution Processing: Payment card processing [Ext.] FI - Accounts Receivable and Accounts Payable Accounting Payment cards [Ext.]



-XQH

6$3$*

6$35HWDLO 6LWH&XUUHQF\&KDQJHRYHU

6LWH&XUUHQF\&KDQJHRYHU 8VH The 326FXUUHQF\ field in the POS data of the site master prevents you from having to convert the currency for all the sites in a company code at the same time as you convert the currency for the company code. In this field, you define the currency in which a site is managed in R/3.

)HDWXUHV When you install R/3 or when you upgrade to R/3 Release 4.0, this field is automatically filled with the currency of the appropriate company code. This store currency applied until you enter a new currency in the field - even if you change the company code currency. The POS currency makes use of change documents and thus allows a history to be managed. This enables you to determine the currency valid at the time a sale was transacted even after conversion has taken place.

$FWLYLWLHV Maintain the new currency in the 326FXUUHQF\field of the site in question. After you change the currency, make sure that the new prices are transferred to the POS systems involved. You can execute the functions required directly using reports, using SAP Business Workflow or via the currency changeover interface in SAP Retail. 5HIHUWR Currency Changeover in Retail (euro) [Page 1244] POS Interface - Inbound: Currency Changeover (Euro) [Page 1196] Currency Changeover Interface for Retail [Ext.] BC - Workflow Scenarios in the Applications: Currency Changeover in Retail (LO-MD) [Ext.]

-XQH



6$35HWDLO

6$3$*

6LWH*URXSV

6LWH*URXSV Sites can be grouped together. One site can be assigned to several groups. A site group does not have any master data or movement data. It is used simply as a method of ensuring that data is maintained for all the individual objects assigned to it (for example, in making mass article changes). Grouping sites together has the following advantages: •

It simplifies the maintenance process For example, you can change a large number of articles for a large number of stores without having to make the changes in all the stores individually.

•

It allows best possible use of store characteristics For example, a promotion can be carried out in all the stores of the same size in a particular region.

•

It allows you to maintain data in sites for information only For example, you can enter the number of employees in a certain group of stores.

Site groups are used mainly in the following functions: •

Allocation table

•

Promotion

•

Listing

•

Supply source determination

•

Mass article maintenance

•

Information System

Site groups are created as classes in the Classification system. The groups can be valid for different periods of time, depending on the class type. The class type also determines whether a site can be assigned to one or more groups. Site group applications are used to determine how classes are used. The following views are available in the standard system: •

Allocation table

•

Promotions

The class type used to create the site groups is stored for every application. The standard system contains class type 30 (sites, not strictly hierarchical) and 35 (sites, strictly hierarchical). 6HHDOVR Classification [Page 394]



-XQH

6$3$*

6$35HWDLO 6LWH6LWH/D\RXW

6LWH6LWH/D\RXW 8VH It is often desirable for stores belonging to the same distribution chain, or departments in a store, to have the same system of merchandise presentation and shelving structure, regardless of their size. This allows customers to find their way better round a store, no matter whether it is their home store or a store in a different town, and therefore provides greater customer satisfaction. To achieve this, you can define site layouts in SAP Retail. You assign these layouts to sites or individual departments. A site layout is divided into layout areas. Layout areas in turn are divided into layout modules, which articles are assigned to.

$UWLNHO

/D\RXWEDXVWHLQH

%HWULHEVOD\RXW

The structure of a layout is described below: •

/D\RXWEHUHLFK The OD\RXWPRGXOH is a group of articles put on sale in the same place in a store or /D\RXWEDXVWHLQ 2EVWUHJDO 2EVW department. It can correspond to one or more shelves. You can define the fixed position of the articles within a layout module.

•

The VLWHOD\RXWconsists of a number of layout areas. Layout areas are used to divide /D\RXWEHUHLFK up the space in a site or department. 6‰ZDUHQUHJDO

•

The OD\RXWDUHD reflects how6‰ZDUHQ the layout modules in the site layout are arranged in the space available. A layout module can occur in several layout areas in a site layout.

/D\RXWEDXVWHLQ

Articles can be located in one or more places in a store. In/D\RXWEHUHLFK the basic data of the article master for 5HLQLJHUUHJDO each article, you can define a main layout module and a number of additional layout modules that are to contain the article. You can /D\RXWEDXVWHLQ enter a sort sequence to define the precise placement of articles within a layout module. The sequence of articles you determine is then reflected in the 5HLQLJXQJVPLWWHO assortment list, which is sorted in the same way for printing/D\RXWEHUHLFK purposes.

.DVVHQUHJDO

You can also specify that the assortments to be assigned to a site layout may only consist of the articles included in the site layout. A store or department can also be assigned an area schema that provides you with a basic profitability analysis for the area. You give an area weighting to the layout area by defining area portions that indicate the relative area portion of the layout area within the site layout. ´ •

Total area points: 10,000

•

Total sales area of store: 1,000 shelf meters

•

Area portion of layout module ELECTRONICS in store: 200 area points

•

Sales volume in layout module ELECTRONICS: $1,000

•

Sales volume of the store $500.000

These details provide the following profitability analysis for layout module ELECTRONICS: •

Share of sales volume / area: 0.1

•

(2% of area and 0.2% of sales volume)

6HHDOVR

-XQH



6$35HWDLO

6$3$*

6LWH6LWH/D\RXW Assortment: assortment list [Page 427] Product catalog [Page 452]



-XQH

6$3$*

6$35HWDLO 6LWH8VHRI,QGXVWU\0DVWHU'DWD

6LWH8VHRI,QGXVWU\0DVWHU'DWD &RQYHUWLQJ,QGXVWU\3ODQWVWR5HWDLO6LWHV So that you can use Retail functions for sites created in the industry environment (industry plants), you must convert these to retail sites. You can then assign retail-specific information to them. You can convert an existing industry plant to a retail site by creating a new site. The system recognizes that the industry site exists and adds the retail-specific data and customer information. As when you create a new retail site, you can use a reference site. The system then copies data and Customizing settings.

&RQYHUWLQJ&XVWRPHUVWR5HWDLO6LWHV You can also convert existing customers to retail sites. You do this by creating a new retail site. When assigning this customer to a site, you can use an existing industry plant or enter the new site which is to be created. If the site already exists, then the retail-specific data is added to it. In the initial screen for the customer, the system suggests a customer number which is the same as the site number. You can overwrite this with the existing customer number. The system recognizes that this customer exists and displays a dialog box. Here, you can assign the existing customer to a site or enter a different customer. When you create the new site, you can change an existing customer or add sales or company code data. You can also assign existing vendors when you create a site, and change or add data relating to these.

-XQH



6$35HWDLO

6$3$*

6LWH6LWH'LVFRQWLQXDWLRQ

6LWH6LWH'LVFRQWLQXDWLRQ If you no longer require sites that are created in the system, you can discontinue them. The related master data is normally archived first. There are two steps in this process: 1. The system checks whether it is able to delete the data, and if so records this in archive files. If a data record is still used in other functions, the system does not store this in the archive file. 2. A deletion program reads the archive file for the data record and deletes the data that is flagged for deletion from the database. Data is archived using the Archive Development Kit (ADK). The ADK contains an archiving object for every object that can be archived. You may need to transfer archived and deleted master data back to the system. For this reason there is a reloading program for most master data. A site always contains customer data, and may also contain vendor data. A site is archived in three steps to take account of this: 1. Customer data is archived (archiving object FI_ACCRECV) 2. Vendor data is archived (archiving object FI_ACCPAYB) 3. General site data is archived (archiving object WS_ACSITE) This process ensures that the customer and vendor data for a site is archived in the appropriate customer and vendor archive files. The advantage of this is that customer or vendor data which is needed at a later date can be accessed directly from the appropriate archive files. See CA - Archiving and deleting application data: Archiving general site data (LO-MD-PL) [Ext.] 6HHDOVR CA - Archiving and deleting application data: Overview [Ext.]



-XQH

6$3$*

6$35HWDLO %XVLQHVV3URFHVVHV

%XVLQHVV3URFHVVHV In this section the business processes available for the current topic are described. Procedures assigned to a specific business process are found in the description of the steps in the process. Procedures that are not assigned to any specific business process are found in the function section of the current topic.

-XQH



6$35HWDLO

6$3$*

6LWH3URFHVVLQJ

6LWH3URFHVVLQJ 3XUSRVH This business process allows you to create sites. Sites can carry out the functions of a YHQGRU as well as those of a FXVWRPHU. When sites carry out vendor functions, they provide goods for other customers or sites. When sites carry out customer functions, they receive goods or services from external vendors or other sites. When a site is created in the system, you not only create a set of general data (such as the address and inventory management information) on the site, you also create data on the customer functions of the site. If the site profile requires you to create the site as a customer, you must enter the customer data in the system. By maintaining additional data, you can, for example, assign merchandise categories to the sites and define supplying sites which can be later included in supply source determination. You can use a reference site and a copying rule to reduce the amount of data you have to enter. This enables you to copy the Customizing settings from one site to another. SAP Retail enables you to maintain all the necessary data for a site in a single transaction. This transaction can be divided into the following areas (views): •

General site data

•

Customer data (site in its capacity as a customer)

•

Vendor data (site in its capacity as a vendor)

•

Additional site data

•

Copying Customizing settings using a reference site

6WHSVLQWKH3URFHVV 1. You assign the site a number and a site profile (which you use to define the site category and the type of settlement).You can also enter a reference site. 2. You assign the site organizational units. 3. You maintain the general site data. 4. You maintain the customer data for the site, such as general customer data, company code data for the customer (optional), and sales area data for the customer (optional). 5. Depending on your requirements, you maintain additional data, such as the supplying sites, the departments and the merchandise categories. 6. You maintain vendor data for the site if the profile allows this. This includes general vendor data, company code data for the vendor (optional), and purchasing organization data for the vendor (optional). 7. If required, you evaluate the characteristics of the site (such as the store manager and number of employees). 8. If required, you copy the Customizing settings from the reference site. 9. The site is now created. The system has also created an assortment that the merchandise categories of the site are assigned to. The assortment has the same



-XQH

6$3$*

6$35HWDLO 6LWH3URFHVVLQJ

number as the site master, providing this has not already been assigned. If it has, an internal number is determined.

5HPDUNV •

If you want to create departments for sites, you have to define these first in Customizing .

6HHDOVR Customer processing [Page 386] Vendor processing [Page 216]

-XQH



6$35HWDLO

6$3$*

6LWH3URFHVVLQJ3URFHGXUH

6LWH3URFHVVLQJ3URFHGXUH To create a site master record, proceed as follows: 1. On the Site Create: Initial Screen [Ext.] enter the site number, a site profile, and the reference site number if you are using one. Choose ENTER. The screen for entering general site data appears. ´ •

The VLWHSURILOH determines the category of site involved (store or distribution center) and how merchandise is to be settled up between the sites (with internal settlement, without internal settlement, external settlement). The site profile can also contain a reference site and a copy rule for the Customizing settings that are to be copied from the reference site to the new site. The site profile also determines which fields are displayed on subsequent screens and whether the fields are optional or compulsory. If you only enter a reference site, the system will always use the site profile defined for that reference site. You can display the site profile on the subsequent screen by choosing menu path &XVWRPL]LQJ → &RQWURO → 6LWHSURILOHVFXUUHQW.

•

If you enter a reference site on the initial screen, the system proposes general site master data (merchandise category, organizational data, departments, etc.) from the reference site.

2. Maintain the JHQHUDOGDWD for the site. •

2UJDQL]DWLRQ&DOHQGDU –

3XUFKDVLQJRUJDQL]DWLRQ If you do not enter a purchasing organization, all purchasing organizations the site is assigned to in Customizing will be responsible for the site.

–

'LVWULEXWLRQFKDLQVDOHVRUJDQL]DWLRQDQGGLVWULEXWLRQFKDQQHO Enter the distribution chain to which the site belongs. A site is assigned to exactly one distribution chain. On the basis of this assignment, the site can use this distribution chain as a means of supply. In the customer data, you maintain sales segments which the site is allowed to procure merchandise from.

´ You can only assign a number of distribution chains (which the site can procure merchandise from) and different purchasing organizations once you have created a site and subsequently changed it via 6LWH→&KDQJH On the change general site data screen choose the option for distribution chains for site or for purchasing organization. A new window appears. You can maintain further assignments here. •



*HQHUDOVLWHGDWD relating to the address, valuation and inventory management, assortment listing, replenishment planning, purchasing, POS (e.g. assortment list), and layout.

-XQH

6$3$*

6$35HWDLO 6LWH3URFHVVLQJ3URFHGXUH

´ •

You can either maintain layout data in the general data for the whole site or at departmental level.

•

When you create a site, you can set a client-wide block for specific customer activities for a specific period. To do so, maintain the data in the %ORFN field group. The block is only activated by a batch run.

3. Maintain the customer data for the site (Customer Processing for Site: Procedure [Page 136]). 4.

In the steps that follow, maintain the additional data for the site (Additional Site Data: Procedure [Page 137]).

5. Maintain the vendor data for the site (Vendor Processing for Site: Procedure [Page 139]). 6. From the menu, choose &XVWRPL]LQJ → &RS\IRUVLWH. If you have entered a reference site, the system will display the Customizing settings that will be copied that will be copied when you save. If you have not yet assigned a reference site to a site or if you wish to assign a different one, enter the site number and choose /LVW→1HZVHOHFWLRQ. The system will then display the relevant tables. You can also use a different copy rule to enable you to copy fewer Customizing settings, for example. The different colors are used to show which tables contain entries for the reference site and which do not. By double-clicking on a line, you can change the entries for the reference site in the relevant Customizing tables. ´ If you make changes to Customizing settings for a reference site, these changes are not updated in sites which the settings have already been copied to. Choose /LVW→&RQILUP to copy the table entries and their contents. 7. Save your entries.

1RWHVDQG5HPDUNV •

Changes you subsequently make to the site profile only affect the field status and the account group of the vendor (providing vendor data has not yet been created).

•

The fact that the site number is entered in the customer and vendor masters and the customer and vendor numbers are entered in the site master means that there is a link between the different functions carried out by a site (site, vendor, customer).

-XQH



6$35HWDLO

6$3$*

&XVWRPHU3URFHVVLQJIRU6LWH3URFHGXUH

&XVWRPHU3URFHVVLQJIRU6LWH3URFHGXUH You start in the screen for general site data in the transaction for creating a site. To maintain the YHQGRUmaster record for a site (in its capacity as a customer), proceed as follows: 1. Choose *RWR → &XVWRPHU. The initial screen for creating a customer appears. 2. This screen contains default organizational data proposed from the site profile. ´ If, in addition to general customer data, you wish to create data that only applies to a particular company code and distribution chain, you must also enter the relevant company code and distribution chain. You can only enter sales transactions (such as sales orders) for a customer if you have entered distribution chain-specific data for that customer. Furthermore, you can only bill for a transaction if the payer has been maintained from a Financial Accounting view (data specific to the company code). Creating Customer Data For Other Organizational Units: Using the &KDQJHVLWH transaction, you can create customer data for other company codes/distribution chains. To do so, choose &XVWRPHU from the change screen for general data. The customer selection list appears. Choose &XVWRPHU→ ([WHQG By pressing ENTER you proceed to all the subsequent data screens in the customer master record. 3. On these screens you can maintain the customer data relevant to the site: –

General data (e.g. marketing, payment transactions, unloading points)

–

Company code data (e.g. account management, correspondence, insurance)

–

Sales area data (e.g. sales, distribution, billing)

´ Some of the screens require you to enter specific data or are logically linked to other screens, which you branch to via pushbuttons. 4. Once you have gone through all screens, the general site data screen reappears. 6HHDOVR Creating a Customer (Sold-To Party): Procedure [Page 387]



-XQH

6$3$*

6$35HWDLO $GGLWLRQDO6LWH'DWD3URFHGXUH

$GGLWLRQDO6LWH'DWD3URFHGXUH You start in the screen for general site data in the transaction for creating a site. To maintain additional data for the site, proceed as follows: 1. 6XSSO\LQJ6LWHV On the general site data screen choose *RWR → 6XSSO\LQJVLWHV. A new window appears. Assign the site one or more supplying sites. ´ When you leave the customer data the system checks whether the periods of validity overlap and supports changes to the periods. If the periods of validity overlap completely, delete one or more entries so that there is no overlap. If the periods of validity only overlap partially, change the periods of validity so that there is no overlap. 2. 5HFHLYLQJ3RLQWV On the general site data screen choose *RWR → 5HFHLYLQJSRLQWV. A new window appears. Create receiving points. A receiving point can be assigned to only one unloading point; an unloading point, on the other hand, can be assigned several different receiving points. The unloading points must have already been assigned in the customer view of the site. 3. 'HSDUWPHQWV On the general site data screen choose *RWR → 'HSDUWPHQWV. A new window appears. If you have already created departments for the site in Customizing, you can now enter the departments. A department can be assigned only one receiving point; a receiving point, on the other hand, can be assigned several different departments. 4. 0HUFKDQGLVH&DWHJRULHV On the general site data screen choose *RWR → 0HUFKDQGLVHFDWHJRULHV. A new window appears. Maintain the merchandise category data for the site (for example, assign the merchandise categories to the site, assign departments, define value-only articles, define Inventory Management exceptions, define supplying sites for the merchandise categories). The data that you have to maintain depends on the profile for value-based inventory management. ´ Merchandise categories must already exist in the system. A merchandise category can be assigned only one department; a department, on the other hand, can be assigned several different merchandise categories. 5. 0HUFKDQW,' On the general site data screen choose *RWR → 0HUFKDQW,'. A new window appears. Enter the merchant ID of the clearing house (such as NaBANCO). This ID enables sales transactions paid with payment cards to be settled with the clearing house. 6. 2SHQLQJ7LPHV

-XQH



6$35HWDLO

6$3$*

$GGLWLRQDO6LWH'DWD3URFHGXUH On the general site data screen choose ([WUDV → 2SHQLQJWLPHV to enter the opening times, opening date or closing date. A new window appears. So that you do not have to enter as much data, you can use an opening times key. 7. 6LWH&ODVVLILFDWLRQ On the general site data screen choose (QYLURQPHQW → &ODVVLILFDWLRQVLWH A new window appears (providing you have created the customer part). You can now assign the site further attributes (such as number of employees). ´ The class 6WRUHFODVV has the characteristics 5HJLRQ and 6DOHVDUHDLQP. If you assign a store this class the store inherits the characteristics. You can then evaluate the stores using the characteristics. This classification allows you to find, for example, all the stores in the southern region that have a sales area of over 200 2 m. Depending on your settings, click a class type and then a class. Enter values for the characteristics in the class. 8. Return to the general site data screen.



-XQH

6$3$*

6$35HWDLO 9HQGRU3URFHVVLQJIRU6LWH3URFHGXUH

9HQGRU3URFHVVLQJIRU6LWH3URFHGXUH To create a YHQGRU master record for a site (in its capacity as a YHQGRU), proceed as follows: 1. Choose *RWR → 9HQGRU. The &UHDWHYHQGRU initial screen appears. 2. This screen contains default organizational data proposed from the site profile. ´ If, in addition to general vendor data, you wish to create data that is only to apply to a particular company code and purchasing organization, you must also enter the relevant company code and purchasing organization. Creating Vendors for Other Organizational Units Using the &KDQJHVLWH transaction, you can create vendor data for other company codes/ purchasing organizations. To do so, choose 9HQGRU from the change screen of the general data. The vendor selection list appears. Choose 9HQGRU→([WHQG By pressing ENTER, you proceed to the other screens in the vendor master record. 3. On these screens you can maintain the vendor data relevant to the site: –

General data (e.g. payment transactions)

–

Company code data (e.g. accounting data, correspondence, payment transactions)

–

Purchasing organization data (e.g. purchasing data, partner functions, conditions)

´ Some of the screens require you to enter specific data or are logically linked to other screens, which you branch to via pushbuttons. 4. Once you have gone through all screens, the general site data screen reappears. 6HHDOVR Creating a Vendor: Procedure [Page 217]

-XQH



6$35HWDLO

6$3$*

6LWH%ORFN

6LWH%ORFN 3XUSRVH This business process allows you to block a site for certain activities in its capacity as a FXVWRPHU or YHQGRU. You may have to block a site for a number of reasons, for example: •

The site is being renovated

•

The site is changing its location

A block can apply to a specific period of time (due to renovation, for example) or to specific functions. A site block can be set at a number of levels. This is particularly useful, as often a site block does not have apply to the whole company but to only certain areas of the company. This business process covers the individual types of blocks that can be set for a site: •

%ORFNLQJWKH6LWHLQLWV&DSDFLW\DVD&XVWRPHU –

–

•

For a VSHFLILFSHULRGRIWLPH: –

For specific activities (such as delivery, billing, or orders)

–

For the whole client

–

Activated by a batch run

'LUHFW blocks: –

Sales block for some or all sales areas

–

Posting block or payment block for some or all company codes

%ORFNLQJWKH6LWHLQLWV&DSDFLW\DVD9HQGRU –

Posting block or payment block for some or all clients

–

Purchasing block for some or all purchasing organizations

–

Purchasing block for certain sites (for example, the purchasing block set for stores A and B only applies to one distribution center and not to the whole purchasing organization)

–

Block for quality reasons

–

All blocks apply directly

6WHSVLQWKH3URFHVV 1. You decide which type of block is to be set: a) *HQHUDOVLWHEORFN b) %ORFNRQVLWHLQLWVFDSDFLW\DVDFXVWRPHU c) %ORFNRQVLWHLQLWVFDSDFLW\DVDYHQGRU 2a) If you wish to set a general site block, you enter the number of the site, the period during which the block is to apply, and the reason for blocking (such as renovation).



-XQH

6$3$*

6$35HWDLO 6LWH%ORFN

The system can tell from the type of blocking reason which blocks are to be set for the site: order block, delivery block and/or billing document block. 2b) If you wish to block a site in its capacity as a customer, you enter the functions and the organizational units for which the site is to be blocked in its capacity as a customer. 2c) If you wish to block a site in its capacity as a vendor, you enter the functions and the organizational units for which the site is to be blocked in its capacity as a vendor.

5HPDUNV •

You can define keys in the blocking reasons, for example for a sales block (order, delivery and billing blocks), in the customer master data of the site. These allow you to differentiate the reasons for the blocks and the way and which the system reacts to them. A delivery block, for example, might result in no deliveries being made to a customer, whereas an order block might only apply to free-of-charge deliveries and credit memos.

6HHDOVR Vendor block [Page 226] Customer block [Page 389]

-XQH



6$35HWDLO

6$3$*

6HWWLQJD*HQHUDO6LWH%ORFN3URFHGXUH

6HWWLQJD*HQHUDO6LWH%ORFN3URFHGXUH To set a general site block (for the ZKROHFOLHQW for a particular SHULRG), proceed as follows: 1. On the Site Change: Initial Screen [Ext.] enter the site to be blocked and press ENTER. The screen for entering general site data appears. 2. In the %ORFN section enter the blocking reason and the period during which the block is to apply. ´ The blocking reason controls the blocks that are set for the whole client and how the system reacts to the different blocks (order, billing, and/or delivery block). Via &XVWRPL]LQJ → &RQWURO → %ORFNLQJUHDVRQV, you can display the blocking reasons already defined and maintain new ones. 3. Save your entries. ´ A batch program that runs every night (for example) analyzes the blocking reasons for the general site block using the validity period of the block. As required, the system sets or deletes the blocking indicator for the sites concerned. This is valid for the ZKROHFOLHQW. If the period during which a site is blocked starts today and the batch program only runs tonight, the site will not be blocked until tomorrow.



-XQH

6$3$*

6$35HWDLO %ORFNLQJD6LWHLQ,WV&DSDFLW\DVD&XVWRPHU3URFHGXUH

%ORFNLQJD6LWHLQ,WV&DSDFLW\DVD&XVWRPHU 3URFHGXUH This procedure allows you to block a VLWH in its capacity as a FXVWRPHU. This block can be valid for the whole client or only for certain company codes or distribution chains. The block becomes valid immediately after you have saved. To set a customer block, proceed as follows: 1. On the Site Change: Initial Screen [Ext.] enter the site number and press ENTER. The screen for entering general site data appears. 2. Go to &XVWRPHU. The customer selection list appears. In this, you see the company codes and sales areas for which data has been maintained for the site. 3. Depending on the type of block you wish to set, proceed in one of the following ways. Since you proceed in most cases to the &KDQJHFXVWRPHU%ORFNLQJGDWDscreen, you can set a number of blocks in the one step: a) &OLHQW:LGH3RVWLQJ%ORFN6DOHVDQG'LVWULEXWLRQ%ORFN 1. From the customer list, select any company code or sales area and views. The system requires this data to proceed to the screen with the blocking data. 2. Choose &KDQJH. A new window appears. 3. Choose([WUDV → %ORFNLQJGDWD.The screen &KDQJHFXVWRPHU%ORFNLQJGDWD appears 4. In the 3RVWLQJEORFN field group, select the $OOFRPSDQ\FRGHV field to set a SRVWLQJEORFNIRUWKHZKROHFOLHQW. In the 6DOHVEORFN field group, enter a key in the $OOVDOHVDUHDV field to set a VDOHVDQGGLVWULEXWLRQEORFNRUGHUGHOLYHU\DQGRUELOOLQJEORFN DW FOLHQWOHYHO. b) 6DOHVDQG'LVWULEXWLRQ%ORFN 2UGHU'HOLYHU\DQGRU%LOOLQJ%ORFN IRUD 3DUWLFXODU6DOHV$UHD 1. From the customer list, select a sales area and a sales area data view. 2. Choose &KDQJH. A new window appears. 3. Choose([WUDV → %ORFNLQJGDWD.The screen &KDQJHFXVWRPHU%ORFNLQJGDWD appears 4. Enter a key for the required block in the 6HOHFWHGVDOHVDUHDVfield. c) Posting Block for a Particular Company Code 1. From the customer list, select the company code and any company code data view. 2. Choose &KDQJH. A new window appears. 3. Choose([WUDV → %ORFNLQJGDWD. The screen &KDQJHFXVWRPHU%ORFNLQJGDWD appears. 4. In the field group 3RVWLQJEORFNselect the 6HOHFWHGFRPSDQ\FRGH field. d) 3D\PHQWEORFN You can set a block for automatic payment at company code level:

-XQH



6$35HWDLO

6$3$*

%ORFNLQJD6LWHLQ,WV&DSDFLW\DVD&XVWRPHU3URFHGXUH 1. In the customer list, select the 3D\PHQWWUDQVDFWLRQVview for the company code data and the required company code. 2. Choose &KDQJH. A new window appears. 3. On the&KDQJH&XVWRPHU3D\PHQW7UDQVDFWLRQV$FFRXQWLQJ screen, enter the required key in the 3D\PHQWEORFNfield. 4. Save your entries. The site is now blocked in its capacity as a customer for the activities you indicated. ´ Repeat the steps as required if you wish to set a sales and distribution block, a posting block or a payment block for more than one organizational unit. 6HHDOVR Customer: Setting Posting and Sales and Distribution Blocks: Procedure [Page 391] Customer: Setting a Payment Block for a Single Company Code: Procedure [Page 393]



-XQH

6$3$*

6$35HWDLO %ORFNLQJD6LWHLQ,WV&DSDFLW\DVD9HQGRU3URFHGXUH

%ORFNLQJD6LWHLQ,WV&DSDFLW\DVD9HQGRU3URFHGXUH This procedure allows you to block a VLWH in its capacity as a vendor. This block can be valid for the whole client or only for certain company codes, purchasing organizations and other levels on which data is maintained. You can also set a block in the vendor master of a site for quality reasons. When you set these blocks, the block becomes valid immediately after you save. To set a block, proceed as follows: 1. On the Site Change: Initial Screen [Ext.] enter the site number and press ENTER. The screen for entering general site data appears. 2. Choose 9HQGRU The vendor selection list appears. In this, you see the company codes and purchasing organizations for which data has been maintained for the site 3. Depending on the type of block you wish to set, proceed in one of the following ways. Since you proceed in most cases to the &KDQJHYHQGRU%ORFNLQJGDWDyou can set a number of blocks in the one step: a) &OLHQWZLGH3RVWLQJ%ORFN3XUFKDVLQJ%ORFN 1. From the vendor list, select any company code or purchasing organization and data areas. The system requires this information to proceed to the screen with the blocking data. 2. Choose &KDQJH. A new window appears. 3. Choose([WUDV → %ORFNLQJGDWD.The screen &KDQJHYHQGRU%ORFNLQJGDWD appears. 4. In the 3RVWLQJEORFN field group, select the $OOFRPSDQ\FRGHV field to set a SRVWLQJEORFNIRUWKHZKROHFOLHQW. In the 3XUFKDVLQJEORFN field group, enter a key in the $OOSXUFKDVLQJ RUJDQL]DWLRQVfield to set a SXUFKDVLQJEORFNDWFOLHQWOHYHO. b) 3XUFKDVLQJ%ORFNIRUD3DUWLFXODU3XUFKDVLQJ2UJDQL]DWLRQ 1. From the vendor list select a purchasing organization and the 3XUFKDVLQJ GDWD view for the purchasing organization data. 2. Choose &KDQJH. A new window appears. 3. Choose([WUDV → %ORFNLQJGDWD.The screen &KDQJHYHQGRU%ORFNLQJGDWD appears. 4. In the 3XUFKDVLQJEORFN field group select the 6HOHFWHGSXUFKDVLQJ RUJDQL]DWLRQ field. c) Posting Block for a Particular Company Code 1. From the vendor list select a company code and any company code data view. 2. Choose &KDQJH. A new window appears. 3. Choose([WUDV → %ORFNLQJGDWD. The screen &KDQJHYHQGRU%ORFNLQJGDWD appears. 4. In the 3RVWLQJEORFNfield group select the 6HOHFWHGFRPSDQ\FRGH field. d) 3XUFKDVLQJ%ORFNIRU'LIIHUHQW'DWD

-XQH



6$35HWDLO

6$3$*

%ORFNLQJD6LWHLQ,WV&DSDFLW\DVD9HQGRU3URFHGXUH If you have maintained different data for the purchasing organization at vendor sub-range level and/or site level, you can set a purchasing block for the level at which the different data is maintained to set a purchasing block in a distribution center for certain stores only. 1. From the vendor list select the 3XUFKDVLQJGDWD view for the purchasing organization data and a purchasing organization. 2. Choose &KDQJH. A new window appears. 3. On the screen &KDQJHYHQGRU3XUFKDVLQJGDWDchoose menu path ([WUDV→ 'LIIHUHQWGDWD. A new window appears. 4. Select the level (on which the different data is maintained) which you wish to block for purchasing activities. 5. Choose 3XUFKDVLQJGHWDLOV A new window appears. 6. Choose ([WUDV→3XUFKDVLQJEORFN. A window appears. 7. Select the 3XUFKDVLQJEORFN field and press ENTER. e) 3D\PHQWEORFN You can set a block for automatic payment at company code level: 1. In the site list, select the 3D\PHQWWUDQVDFWLRQVview for the company code data and the required company code. 2. Choose &KDQJH. A new window appears. 3. On the screen &KDQJH9HQGRU3D\PHQW7UDQVDFWLRQV$FFRXQWLQJ enter the required key in the 3D\PHQWEORFN field. f)

%ORFNIRUTXDOLW\UHDVRQV 1. From the vendor list, select any company code or purchasing organization and data areas. The system requires this information to proceed to the screen with the blocking data. 2. Choose &KDQJH. A new window appears. 3. Choose([WUDV → %ORFNLQJGDWD.The screen &KDQJHYHQGRU%ORFNLQJGDWD appears. 4. In the %ORFNIRUTXDOLW\UHDVRQV field enter a key which defines the procurement functions to be blocked (ordering, goods receipt, etc.). This block does not take account of the organizational levels you previously selected.

´ The %ORFNIRUTXDOLW\UHDVRQVfield in the vendor master record is only of significance in connection with the QM system. You must set the QM procurement key and maintain the control key in the article master. 4. Save your entries. The site is now blocked in its capacity as a vendor for the activities you indicated. ´ Repeat the steps as required if you wish to set a purchasing block, a posting block or a payment block for more than one organizational unit.



-XQH

6$3$*

6$35HWDLO %ORFNLQJD6LWHLQ,WV&DSDFLW\DVD9HQGRU3URFHGXUH

6HHDOVR Vendor: Setting a Purchasing/Posting Block: Procedure [Page 228] Vendor: Setting a Purchasing Block for Sites and/or Vendor Sub-Ranges: Procedure [Page 229] Vendor Setting a Payment Block for Specific Company Codes: Procedure [Page 230] Vendor: Setting a Block for Quality Reasons in the Vendor Master [Page 231]

-XQH



6$35HWDLO

6$3$*

9HQGRU

9HQGRU 3XUSRVH A vendor is an organizational unit that supplies goods to a site or a customer. The vendor master contains information on all vendors. This information is stored in master records for each individual vendor. The data contained in a vendor master record then appears as default values in the appropriate fields, for example in purchase orders.

,PSOHPHQWDWLRQ&RQVLGHUDWLRQV The advantage of storing master data centrally, making it the single source of information for all system functions, is that data only ever has to be entered once. If a vendor has a change of address, for example, the new address only ever has to be entered once.

,QWHJUDWLRQ A vendor master contains information from both purchasing and financial accounting, as vendors are also business partners from the credit side in financial accounting. %XVLQHVVSURFHVVHVDQG SURFHGXUHV

Organizational areas Headquarters [Page 103]

D i s t r i b u ti o n

S t o r e

C e n t e r [ P a g e

1 0 8 ]

[ P a g e

Sal es Offi ce [Pa ge 11 0]

1 0 6 ]



-XQH

6$3$*

6$35HWDLO 9HQGRU

Vendor processing [Page 216]

•

Vendor block [Page 226]

•

6HHDOVR Customer [Page 369] Vendor hierarchy [Page 190] FI - Accounts Receivable and Accounts Payable Accounting [Ext.] BC – Workflow scenarios in applications: Releasing blocked vendor data (LO-MD-BP) [Ext.]

-XQH



6$35HWDLO

6$3$*

)XQFWLRQV

)XQFWLRQV In this section the functions available for the current topic are described. Procedures that are not assigned to any specific business process are also documented here. Procedures assigned to a specific business process are found in the business process section of the current topic in the description of the steps in the process.



-XQH

6$3$*

6$35HWDLO 9HQGRU9HQGRU&DWHJRULHV

9HQGRU9HQGRU&DWHJRULHV There are two different vendor categories: •

,QWHUQDOYHQGRU A vendor is classed as internal if the goods being delivered were already entered in Inventory Management beforehand (that is, if the vendor supplying the goods is a site). The goods movement is handled in the system in the form of a stock transport order or a delivery.

•

([WHUQDOYHQGRU The more common scenario is that of an external vendor who has a particular assortment of goods on offer at set conditions. Where parts of the assortment are offered at different conditions, the assortment can be divided up into sub-ranges. Goods from a external supplier are ordered by a site using a purchase order.

Every vendor can carry out a number of different functions in SAP Retail such as delivering goods, issuing invoices or granting conditions. Normally a site is only maintained as a vendor in the system if it is a distribution center.

-XQH



6$35HWDLO

6$3$*

9HQGRU1XPEHU$VVLJQPHQW

9HQGRU1XPEHU$VVLJQPHQW Every vendor master record is given a unique number for identification within your company. Financial Accounting refers to this number as the DFFRXQWQXPEHU. You require this number to process the master record or enter purchase orders for a vendor. The numbers can be assigned externally by you, or internally by the system. If you assign the number externally, you can also make an alphanumeric entry. The system ensures that the numbers issued are always unique. If the system assigns the number, it issues numbers from a predefined number range. If you enter the number externally, the system makes sure that the number you enter has not been assigned to any other vendor. How numbers are assigned (externally by you or internally by the system) is determined by the account group you enter when creating a site master record. ´ A vendor has the same number in all purchasing organizations and company codes.



-XQH

6$3$*

6$35HWDLO 9HQGRU$FFRXQW*URXS

9HQGRU$FFRXQW*URXS When you create a vendor master record, you are required to enter an account group. The account group determines: •

How numbers are assigned (externally by you or internally by the system) and the number range from which they are assigned

•

Whether the vendor is a one-time vendor

•

Which fields appear on the screen and whether the user can or must make an entry

•

Whether there are any other levels on which data can be retained below the purchasing organization level (site and/or vendor sub-range), and if so, what these are

•

Which partner procedures are valid

•

Whether article default data is to be passed on to article master records and/or purchasing information records;

In Customizing, you define the account groups that are to be available.

2QH7LPH9HQGRUV You can create special one-time master records for vendors from which you only order goods once or very rarely. ´ For example, you order merchandise from a different vendor, because your preferred vendor cannot deliver. In this case, you store the information on the vendor in a one-time vendor master record. When you create a one-time vendor master record, you have to enter a one-time account group. The vendor-specific fields are then switched off. Information that the system usually provides as default data when you create documents does not appear and has to be entered manually. Unlike other master records, one-time master records are used for a number of different vendors so that you do not have to create an unnecessarily large number of master records. This is why no vendor-specific data is stored in the master record. When you create a purchasing document using a one-time vendor, the system automatically branches to a master data screen for you to enter vendor-specific data such as name, address, or bank details. This information is then stored in the document. Like other master records, one-time vendor master records can be displayed, blocked or deleted.

-XQH



6$35HWDLO

6$3$*

9HQGRU9HQGRU6XE5DQJH

9HQGRU9HQGRU6XE5DQJH The complete assortment of merchandise offered by a particular vendor can be divided up into different sub-ranges. These vendor sub-ranges and are useful when different conditions apply to different articles.

If you define vendor sub-ranges for an article, every article supplied by the vendor can be assigned to one vendor sub-range. Vendor sub-ranges must be defined in the same way for all sites. The texts for the vendor sub-ranges can be entered in a number of languages.



-XQH

6$3$*

6$35HWDLO 9HQGRU'DWD5HWHQWLRQ/HYHOV

9HQGRU'DWD5HWHQWLRQ/HYHOV A vendor master record comprises the following data levels: •

General data

•

Company Code Data

•

Purchasing Organization Data

Data can also be retained at other levels within the purchasing organization.

*HQHUDOGDWD This information on the vendor is valid for all company codes and all purchasing organizations within the client. This includes: •

Address data for unique identification of the vendor, and communication purposes

•

Control data for finance purposes

•

Payment transaction data such as bank details and terms of payment.

•

Contact person data, such as the name and address of the director of the vendor company

&RPSDQ\&RGH'DWD This information on the vendor can be maintained separately for every company code in the client. This data is required by the payment and reminder program and for reporting to the tax authorities. This includes: •

Account management data (Financial Accounting)

•

Payment transaction data (Financial Accounting)

•

Data required for correspondence (Financial Accounting)

´ Company code data must have been entered in the system for a vendor before you can enter in the system invoices issued to you by the vendor.

3XUFKDVLQJ2UJDQL]DWLRQ'DWD This information on the vendor can be maintained separately for every purchasing organization in the client. This data is of relevance to Purchasing and includes: This includes: •

Purchasing Data

•

Partner Functions

2WKHU'DWD5HWHQWLRQ/HYHOV:LWKLQWKH3XUFKDVLQJ2UJDQL]DWLRQ In addition to data that is valid for the whole purchasing organization, you can enter information on the 3XUFKDVLQJGDWD and 3DUWQHUIXQFWLRQV screens that is only valid for a particular site and/or vendor sub-range. This includes terms of payment or incoterms that differ from those valid for the purchasing organization. The data differing for the vendor only can be retained for: •

A vendor sub-range (VSR)

-XQH



6$35HWDLO

6$3$*

9HQGRU'DWD5HWHQWLRQ/HYHOV •

Site

•

A particular combination of vendor sub-range and site

´ You managed to negotiate better prices and conditions for a particular vendor subrange that those valid for the purchasing organization. You create a vendor subrange and maintain the different terms of payment, for example, for that sub-range. The system finds the data retention level containing the vendor data (for a purchase order, for example), as follows: 1. If it finds data valid for the specific purchasing organization, vendor sub-range and site, it uses this data. 2. If the system finds no data at this level, it checks whether any data has been maintained for the specific purchasing organization and vendor sub-range. If so, it uses this data. 3. If the system finds no data at this level either, it checks whether any data has been maintained for the combination of purchasing organization and site. If so, it uses this data. 4. Finally if no data can be found at this level either, the system uses the data maintained at purchasing organization level. In Customizing, you can define whether additional levels for data maintenance within a purchasing organization are allowed, and what these levels are, for each account group. These settings can, however, be changed in the vendor master record you are creating. This allows you to control the levels at which different data can be entered for each vendor (see ([WUDV→ $GGLWLRQDOGDWD3XUFKDVLQJ . ´ If you switch off the additional data retention levels within the purchasing organization in the Customizing system, you may first have to delete any different data that exists for a vendor. Choose 3XUFK2YHUYLHZ in the 'LIIHUHQWGDWD screen to obtain an overview of the data retained at the different levels.



-XQH

6$3$*

6$35HWDLO 9HQGRU%XVLQHVV3DUWQHUV

9HQGRU%XVLQHVV3DUWQHUV The business partner “vendor” can assume a number of different functions in connection with your company. When you order goods from a vendor company, the company first has the function of the RUGHUUHFLSLHQW, then the JRRGVVXSSOLHU, theLVVXHURIDQLQYRLFH and then the SD\PHQWUHFLSLHQW. These different functions are described as partner functions. One or more of these functions may be carried out by different vendors. For this reason you can assign business partners a number of partner functions. The data is then used in the associated functions in Logistics and Accounting. The partner functions stored in a vendor master record can appear as default data in purchase orders and contracts, for example. Every partner function is assigned to a SDUWQHUW\SH. You can define whether each partner function is to be unique in the vendor master. If it is, it can occur only once within a data retention level (e.g. function VN). The following partner types are supported in Purchasing: •

LI

Vendor master records

•

CP

Contact Persons

•

PE

HR master records

A SDUWQHUGHWHUPLQDWLRQSURFHGXUH is used to find the partner functions that are to be allowed or mandatory for a particular vendor master record or a purchasing document. When you create a vendor master record, the partner functions that are flagged as being mandatory in the partner determination procedure valid for the account group appear as default values. Mandatory partner functions are defined in the Customizing system. If no other functions have been maintained, the vendor data applies. Any different payment recipient will be displayed if this has been maintained in the payment transaction data.

-XQH



6$35HWDLO

6$3$*

9HQGRU3DUWQHU)XQFWLRQVLQWKH6WDQGDUG6\VWHP

9HQGRU3DUWQHU)XQFWLRQVLQWKH6WDQGDUG6\VWHP Partner determination procedures are determined in the vendor master via the account group and the data retention level (purchasing organization, vendor sub-range and site). In the partner determination procedure you can define whether the business partner number used as the default value by the system in the vendor master number can be changed and whether the function is a mandatory function. The following partner functions exist in the standard system: 3DUWQHUIXQFWLRQVRISDUWQHUW\SH/,YHQGRU AZ

Alternative payment recipient

OA

Ordering address

VN

Vendor

CR

Carrier

PI

Invoice presented by

CA

Contract address

GS

Goods supplier

DP

Delivering site

9HQGRUKLHUDUFK\ 2A

Vendor hierarchy 1

Higher-level function: 2B

2B

Vendor hierarchy 2

Higher-level function: 2C

2C

Vendor hierarchy 3

Higher-level function: 2D

2D

Vendor hierarchy 4

3DUWQHUIXQFWLRQVRISDUWQHUW\SH&3FRQWDFW SHUVRQ CP

Contact person

3DUWQHUIXQFWLRQVRISDUWQHUW\SH3(+5 PDVWHUUHFRUGV ER



Employee responsible

-XQH

6$3$*

6$35HWDLO 9HQGRU3DUWQHU)XQFWLRQVLQWKH6WDQGDUG6\VWHP

Partner functions 2A, 2B, 2C and 2D are defined exclusively for the vendor hierarchy and should not be used in a partner determination procedures used in vendor master schema. Partner function ER (employee responsible) is not used in operative applications and is for information only. The employee responsible could be someone within your company who is responsible for purchasing from the vendor, for example. You can assign this type of buyer to the vendor using partner function ER. If the person in your system has a personnel master record, you can use the %X\HUsubmenu in the 9HQGRUmenu to process the buyer (create, change, display).

-XQH



6$35HWDLO

6$3$*

9HQGRU5HODWLRQVKLS%HWZHHQ$FFRXQW*URXSDQG3DUWQHU)XQFWLRQ

9HQGRU5HODWLRQVKLS%HWZHHQ$FFRXQW*URXSDQG 3DUWQHU)XQFWLRQ For partner functions of the partner type LI, you have to define in Customizing which account group can be used for which partner function. The following combinations exist in the standard system: 3DUWQHUIXQFWLRQ $FFRXQWJURXS AZ

Alternative payment recipient

0001

Vendor

0003

Alternative payment recipient

0100

Vendor distribution center

KRED Vendor (int. number assignment)

OA

Ordering address

LIEF

Vendor (ext. number assignment)

0001

Vendor

0006

Ordering address

0100

Vendor distribution center

KRED Vendor (int. number assignment)

VN

Vendor

LIEF

Vendor (ext. number assignment)

0001

Vendor

0005

Carrier

0100

Vendor distribution center

KRED Vendor (int. number assignment) LIEF

Vendor (ext. number assignment)

CR

Carrier

0005

Carrier

PI

Invoice presented by

0001

Vendor

0004

Invoice presented by

0100

Vendor distribution center

KRED Vendor (int. number assignment)

CA



Contract address

LIEF

Vendor (ext. number assignment)

0001

Vendor

-XQH

6$3$*

6$35HWDLO 9HQGRU5HODWLRQVKLS%HWZHHQ$FFRXQW*URXSDQG3DUWQHU)XQFWLRQ

GS

Goods supplier

0001

Vendor

0002

Goods supplier

0005

Carrier

0100

Vendor distribution center

0110

Delivering site

KRED Vendor (int. number assignment)

2A

2B

2C

2D

-XQH

Vendor hierarchy 1

Vendor hierarchy 2

Vendor hierarchy 3

Vendor hierarchy 4

LIEF

Vendor (ext. number assignment)

0001

Vendor

0012

Hierarchy nodes

0001

Vendor

0012

Hierarchy nodes

0001

Vendor

0012

Hierarchy nodes

0001

Vendor

0012

Hierarchy nodes



6$35HWDLO

6$3$*

9HQGRU3DUWQHU'HWHUPLQDWLRQ3URFHGXUHVLQWKH6WDQGDUG6\VWHP

9HQGRU3DUWQHU'HWHUPLQDWLRQ3URFHGXUHVLQWKH 6WDQGDUG6\VWHP 3DUWQHU'HWHUPLQDWLRQ3URFHGXUHVLQWKH9HQGRU0DVWHU The following partner determination procedures exist in the standard system: 3DUWQHUGHWHUPLQDWLRQ SURFHGXUH

3DUWQHU)XQFWLRQV

L1

Vendor (purchasing organization)

CP Contact persons AZ Alternative payment recipient OA Ordering address (mandatory) VN Vendor (mandatory function, cannot be changed) PI

Invoice presented by (mandatory)

CA Contract address CF Contact person, perishables ER Employee responsible GS Goods supplier (mandatory) 3DUWQHUGHWHUPLQDWLRQ SURFHGXUH

3DUWQHU)XQFWLRQV

L2

Vendor (sub-range area)

OA Ordering address (mandatory) GS Goods supplier CP Contact persons ER Employee responsible CA Contract address PI

Invoice presented by

ER Employee responsible 3DUWQHUGHWHUPLQDWLRQSURFHGXUH 3DUWQHU)XQFWLRQV L3

Vendor (site level)

OA Ordering address GS Goods supplier CP Contact persons ER Employee responsible



-XQH

6$3$*

6$35HWDLO 9HQGRU3DUWQHU'HWHUPLQDWLRQ3URFHGXUHVLQWKH6WDQGDUG6\VWHP

CA Contract address PI

-XQH

Invoice presented by



6$35HWDLO

6$3$*

9HQGRU&RQWDFW3HUVRQV

9HQGRU&RQWDFW3HUVRQV You have contact - either on the telephone, by letter or in person - with a number of different people at a vendor company. Often, you need detailed information about contact persons such as their full name, telephone number and jobs within the company as well as their department. Since the contact person is directly linked to the vendor, there is a transaction for entering this data in the vendor master record. You can enter as many contact persons as desired for every vendor. Contact persons can then be used in their partner role (partner function CP) on various retention levels, with the data available for associated functions in Logistics and Accounting.



-XQH

6$3$*

6$35HWDLO 9HQGRU9HQGRU&KDUDFWHULVWLF9DOXHV

9HQGRU9HQGRU&KDUDFWHULVWLF9DOXHV Articles can have different characteristics such as color or size. Often characteristics are given different names by different vendors. ´ &RPSDQ\RZQYDOXH red

9HQGRUYDOXH 5001

fire engine red

4717

All the characteristic values used in your company can be stored in the system along with the corresponding values given to them by every vendor. This is done by assigning vendor characteristic values to your internal characteristic values. If no vendor characteristic value has been maintained for one of your company-internal characteristic values, the system uses your internal value. This function is only available in a retail system for generic articles. 3XUFKDVHRUGHUZLWKRXWYHQGRUFKDUDFWHULVWLFVYDOXHV 

UHG \HOORZ



EOXH

" " "



6WRUDJHORFDWLRQ 3XUFKDVH RUGHU













%X\HU

9HQGRU

3XUFKDVHRUGHUZLWKYHQGRUFKDUDFWHULVWLFVYDOXHV



9HQGRU 











3XUFKDVH RUGHU %X\HU

-XQH

6WRUDJHORFDWLRQ  





  9HQGRU



6$35HWDLO

6$3$*

9HQGRU9HQGRU&KDUDFWHULVWLF9DOXHV The assignment of vendor characteristic values to internal characteristic values is dependent solely on the vendor and not on the individual articles. Vendor characteristic values cannot be maintained unless you assign them to an internal characteristic value. If an external characteristic value exists for an internal characteristic value, this assignment is unique. Conversely, for each vendor, one internal characteristic value exists for every vendor characteristic value maintained. All internal characteristic values are maintained in the Classification System and cannot be maintained at the same time as you maintain vendor characteristic values. You can also maintain a language-independent description for every vendor characteristic value. Vendor characteristic values can be entered from vendor or article maintenance. From the purchasing screen of the vendor master, choose ([WUDV → 9HQGRUFKDUDFWHULVWLFYDOXHV. You can only maintain a vendor characteristic value if it is assigned to an internal characteristic value. This assignment must be unique. In addition to using standard functions such as Select, Delete, etc., you can display all internal values for a characteristic and select a vendor to fit the characteristic. The sequence of characteristic values presented to you by the system corresponds to the sequence of values in the Classification system. ´ The sequence of values for a characteristic describing sizes is XS, S, M, L, XL. This is the sequence that was maintained in the Classification system.



-XQH

6$3$*

6$35HWDLO 9HQGRU)RUZDUGLQJ&KDQJHV

9HQGRU)RUZDUGLQJ&KDQJHV A large amount of information is stored in the vendor master and the system accesses this information when creating articles in the article master and in the relevant information records. When changes are made to this information, and if certain conditions are met, the system automatically changes the related information in the article master and in the relevant information records. The following factors determine whether a field in the article master and/or purchasing info record is affected by a change in the vendor master, i.e. whether the change is forwarded to the appropriate segment: •

The Customizing setting in the vendor master See Vendor: Customizing Settings [Page 168]

•

The data retention level at which the change was made in the vendor master, taking account of the “next-level principle” See Vendor: Data Retention Levels and the Next-Level Principle [Page 169]

•

The segments in which the fields changed in the vendor master appear (in the article master only, in the purchasing info record only, or in both) See Vendor: Data Segments [Page 168]

•

Special features when determining the relevant purchasing info records See Vendor: Determining the Relevant Purchasing Info Records [Page 173]

•

Special features when determining the relevant segment of the article master See Vendor: Determining the Relevant Article Master Segments [Page 174]

•

Current blocks See Vendor: Blocking Mechanism [Page 176]

Because the automatic update of all changes can involve a very large amount of data, the process may take some time.

-XQH



6$35HWDLO

6$3$*

9HQGRU&XVWRPL]LQJ6HWWLQJV

9HQGRU&XVWRPL]LQJ6HWWLQJV In Customizing for the vendor master, you can specify whether the changes to certain fields in the vendor master •

are not to be forwarded (standard setting)

•

are only to be forwarded to the article master records

•

are only to be forwarded to the purchasing info records

•

are to be forwarded to the article master records and purchasing info records

Please note that, if you choose the 2QO\IRUZDUGWRDUWLFOHPDVWHUUHFRUGVsetting, only those article master fields for which there is no equivalent field in the purchasing info record are forwarded (see Vendor: Determining the relevant purchasing info records [Page 173] ).



-XQH

6$3$*

6$35HWDLO 9HQGRU'DWD5HWHQWLRQ/HYHOVDQGWKH1H[W/HYHO3ULQFLSOH

9HQGRU'DWD5HWHQWLRQ/HYHOVDQGWKH1H[W/HYHO 3ULQFLSOH All article master records and purchasing info records which are retained in a particular data retention level in the vendor master can be affected by a change to the purchasing data at this data retention level. A data retention level is characterized by the vendor, a purchasing organization, a vendor sub-range (can be empty) and/or a site (can be empty). As a result, there are four possible data retention levels for a combination of vendor/purchasing organization: •

Purchasing organization / sub-range / site

•

Purchasing organization / sub-range / —

•

Purchasing organization / — / site

•

Purchasing organization / — / —

Each article master and each purchasing info record is retained at one of these data retention levels. The initial values (purchasing organization, sub-range, site) which are used to determine the relevant data retention level are obtained from the article master records and/or purchasing info records which are to be analyzed. Starting from the specific level, the system tries to find a data retention level containing appropriate data. If it does not succeed, it moves to the next level (“next-level principle”). It continues to do this until it has either found a data retention level or it reaches the purchasing organization level. The search sequence is therefore as follows: 1. Purchasing organization / sub-range / site 2. Purchasing organization / sub-range / — 3. Purchasing organization / — / site 4. Purchasing organization / — / — As the system must contain a data retention level which is not characterized by the purchasing organization alone, the next-level principle means that a concrete data retention level is always determined. ´ The vendor master contains the following data retention levels: 3XUFKDVLQJRUJDQL]DWLRQ 9HQGRUVXEUDQJH 6LWH

'DWDUHWHQWLRQOHYHO

0001

111111

BED1 Ä DR1

0001

111111

—

Ä DR2

0001

—

—

Ä DR3

An article master segment for site BED1 that contains an article that is assigned to sub-range 111111 is retained at level DR1. Because there is no data retention level which is specified by site BED1 alone, the article master segment for site BED1 which contains an article that is assigned to another sub-range is retained at level DR3.

-XQH



6$35HWDLO

6$3$*

9HQGRU'DWD5HWHQWLRQ/HYHOVDQGWKH1H[W/HYHO3ULQFLSOH An article master segment for site XYZ which contains an article that is assigned to sub-range 111111 is retained at level DR2.



-XQH

6$3$*

6$35HWDLO 9HQGRU'DWDVHJPHQWV

9HQGRU'DWDVHJPHQWV In the $UWLFOHGHIDXOWGDWDarea of the vendor master, the fields can be forwarded as follows: •

to the purchasing info records only

•

to the article master records only

•

to both

These fields are forwarded differently. Where they are forwarded to depends on the default values that are determined when an article is created in Article Maintenance.

)LHOGVLQERWKWKHDUWLFOHPDVWHUDQGSXUFKDVLQJLQIRUHFRUG VHJPHQWV When a purchasing info record is created, the initial values of the fields are determined from the data retention level (in the vendor master) at which the EIN segment is retained. When an article master is created, the initial values of the fields are determined as follows: •

from the site-dependent purchasing info record (if one exists)

•

from the site-independent purchasing info record (if one exists, and no site-dependent purchasing info record exists)

•

from the data retention level (in the vendor master) at which the segment is retained (if neither site-dependent nor site-independent purchasing info records exist).

The reason for this procedure is that the default values are embedded in the operative environment. When you create a purchase order, the default values are taken from the purchasing info record, not the vendor master. It makes no sense to adjust the fields in the article master records so that they contain values which are taken direct from the vendor master but which are not used in operative business. The following fields appear in both the article master and the purchasing info record: •

Purchasing group

•

Planned delivery time

•

Unit of measure groups

•

Rounding profile

If these fields are changed in the vendor master, the changes are forwarded to both segments.

)LHOGVLQRQO\WKHSXUFKDVLQJLQIRUHFRUGRULQDUWLFOHPDVWHU VHJPHQWV The initial values are determined from the data retention level (in the vendor master) at which the segment is retained. The following fields appear in the article master only: •

Stock planner

•

Delivery cycle

•

Planning cycle

-XQH



6$35HWDLO

6$3$*

9HQGRU'DWDVHJPHQWV If these fields are changed in the vendor master, the changes are forwarded to the article master only. The following field appears in the purchasing info record only: •

Confirmation control

If this field is changed in the vendor master, the changes are forwarded to the purchasing info record only.



-XQH

6$3$*

6$35HWDLO 9HQGRU'HWHUPLQLQJWKH5HOHYDQW3XUFKDVLQJ,QIR5HFRUG

9HQGRU'HWHUPLQLQJWKH5HOHYDQW3XUFKDVLQJ,QIR 5HFRUG Starting from the vendor and purchasing organization which characterize the changed data retention level, the system determines all purchasing info records which are not flagged for deletion and for which articles can still be delivered. The vendor data retention level at which the segment is retained is determined for all of the purchasing info record segments determined in this initial selection. If a change is made at this data retention level (this can be a deletion - not just at the level characterized by the purchasing organization - or an addition in the level), the system checks whether the current value in the purchasing info record is the same as the value in the data retention level at which the purchasing info record segment would have been retained if the change had not been made. Only if these two values are identical does the system forward to the purchasing info record the value from the data retention level at which it is now retained. This prevents manual changes to the purchasing info record being automatically overwritten.

-XQH



6$35HWDLO

6$3$*

9HQGRU'HWHUPLQLQJWKH5HOHYDQW$UWLFOH0DVWHU6HJPHQWV

9HQGRU'HWHUPLQLQJWKH5HOHYDQW$UWLFOH0DVWHU 6HJPHQWV The initial selection of the article master segments concerned depends on whether the vendor is an external vendor or a distribution center. •

Initial selection with external vendor The connection between vendor and article is created via the purchasing info record. Starting from the vendor and the purchasing organization which characterize the changed data retention level, the system determines all purchasing info records which are not flagged for deletion and for which articles can still be delivered. The vendor must be the only supplier of these goods, or must be the regular vendor.

•

Initial selection with distribution center As there may not necessarily be purchasing info records for the particular distribution center and site when goods are supplied to the site, the purchasing records cannot be used as they can for an external vendor. Instead, the system considers all articles that the distribution center itself can process (i.e. those for which article master segments exist for the distribution center).

The following checks are carried out for all the article master segments found in the initial selection: •

Check that the segment has planning status.

•

Check that only one purchasing organization is responsible for the site for which the article master segment exists. This must be the same purchasing organization which characterizes the changed data retention level.

•

Check determination of data retention level at which the article master segment is retained (see section below).

•

Check on the supplying site if the vendor is a distribution center. This determines whether the site for which the article master segment exists is actually supplied by the distribution center.

•

Check on the source of supply key. The system will only consider an article master record if the first entry for the source of supply key is a procurement type which matches the vendor in question. For example, if the vendor in question is an external vendor, and the source of supply key for the article master segment specifies that stock transfer is to be carried out prior to external procurement, the system will not consider this article master segment.

•

Check on the procurement code for external vendors. The system will only consider the article master segment if the procurement code indicates external procurement.

'HWHUPLQLQJWKHGDWDUHWHQWLRQOHYHOIRUWKHDUWLFOHPDVWHU VHJPHQW When the system processes an article master segment it determines whether the field affected by the change occurs in the article master segment only, or in the purchasing info record as well. If the latter is the case, the article master and purchasing info record (if one exists, which is not necessarily the case for a distribution center) are seen as a single unit. This means that the value in the field in the article master segment only changes if the value in the field in the purchasing



-XQH

6$3$*

6$35HWDLO 9HQGRU'HWHUPLQLQJWKH5HOHYDQW$UWLFOH0DVWHU6HJPHQWV

info record changes Note that if the purchasing info record segment is site-independent only, this may be retained at a different data retention level to the actual article master segment. ´ The vendor master contains the following data retention levels: 3XUFKDVLQJRUJDQL]DWLRQ 9HQGRUVXEUDQJH 6LWH

'DWDUHWHQWLRQOHYHO

0001

111111

BED1 Ä DR1

0001

111111

—

Ä DR2

0001

—

—

Ä DR3

An article master segment for site BED1 that contains an article that is assigned to sub-range 111111 is retained at level DR1. If the purchasing info record for this article master segment is site-independent only, then this is retained at level DR2. This means that changes at level DR2 are of interest for the fields in the article master segment which also exist in the purchasing info record, while changes at level DR1 are of interest for the other fields. If a change is made at one of the data retention levels (this can be a deletion - not just at the level characterized by the purchasing organization - or an addition in the level), the system checks whether the current value in the article master is the same as the value in the data retention level at which the article master segment would have been retained if the change had not been made. Only if these two values are identical does the system forward to the article master segment the value from the data retention level at which it is now retained (if this relates to changes to fields which also exist in the purchasing info records, the changes are only forwarded if they have also been made in the purchasing info record). This means that manual changes to the article master are not overwritten automatically. ´ MARC segments do not contain any information on a sub-range. An article, and therefore the associated MARC segments, are assigned to a sub-range if a subrange is entered in the purchasing info header record (EINA segment).

-XQH



6$35HWDLO

6$3$*

9HQGRU6$3%ORFNLQJ0HFKDQLVP

9HQGRU6$3%ORFNLQJ0HFKDQLVP Changes to fields which occur in both the purchasing info record and the article master are considered as a unit if a setting is made in Customizing which indicates that changes in the vendor master are to be forwarded to the purchasing info record and article master. They are therefore changed in both segments or not at all. This means in particular that an unsuccessful block on a purchasing info record prevents a change being made to an article master record which has been successfully blocked, if the field in which the change is made occurs in both segments. This applies likewise to an unsuccessful block in the article master.



-XQH

6$3$*

6$35HWDLO 9HQGRU3ODQQLQJ&KDQJHV

9HQGRU3ODQQLQJ&KDQJHV You can enter and later activate changes which you plan to make at a later date to general data (but not the contact person data) and purchasing data. Data for which you can plan changes includes: •

The address

•

Terms of payment

You can enter planned changes for a particular date and vendor. When you save the data a change document is created. If you display planned changes for a particular date, the system displays all planned changes up to and including that date. With the exception of check boxes, fields which have been changed are highlighted in a different color. If you add or delete purchasing data at site and/or sub-range level, the system indicates this on the screen by highlighting the key fields (sub-range, site) which characterize the level. You have to activate planned changes before they can become valid. When you activate a change it takes effect immediately, even if it was planned for a later date. When you activate a change all changes planned but not yet activated up to and including the date entered become valid. If you plan changes for a large number of vendors, activation may take some time. You can therefore activate the changes in the background using a batch input file. Any activation errors which occur are listed in a log.

-XQH



6$35HWDLO

6$3$*

9HQGRU5HWXUQVZLWKD'HOLYHU\

9HQGRU5HWXUQVZLWKD'HOLYHU\ If the 5HWXUQVZLWKGHOLYHULHV indicator is set in the 3XUFKDVLQJGDWD screen, returns items are returned to the vendor using SD deliveries. The goods recipient is determined in the delivery from the customer master assigned to the vendor (general data, control data). The sales area for the delivery is determined from the site master. If this indicator is set in the vendor master but no customer master record has been assigned to the vendor, the system tries to create a customer master record and assign it to the vendor. The default account group of the customer can be assigned to a vendor account group in Customizing. The sales areas used for the creation of the customer master are determined as follows: •

The possible sites are found from the purchasing organization assigned to the site.

•

The possible sales areas are found from the sites.

6HHDOVR Purchase order processing: Returns [Ext.]



-XQH

6$3$*

6$35HWDLO 9HQGRU5DFN-REEHU

9HQGRU5DFN-REEHU 8VH Rack jobbers are wholesalers or manufacturers who are granted sales space (usually shelf space) in retail outlets and who offer goods there which are not covered by the existing assortment. The goods are the property of the rack jobber, but they are sold via the retail site’s POS system. SAP Retail supports the management of rack jobber goods in your stores by separating the stocks and sales revenue of these external goods from the goods that are your property. Rack jobbers are treated as vendors in SAP Retail.

,QWHJUDWLRQ You can use rack jobber features with or without Inventory Management. If Inventory Management is active for the rack jobber merchandise, you can include the rack jobber merchandise in most logistics functions. However, this may cost you more time, e.g. in master data maintenance. A decision to use Inventory Management depends largely on the role your company plays in managing rack jobber merchandise. •

If, for example, you carry out replenishment of rack jobber merchandise independently, you should use Inventory Management so that you can make use of procurement functions.

•

If, on the other hand, the rack jobber provides the goods for the sales area, and your company is only responsible for selling it, you do not need Inventory Management. You are still able to display sales revenue for rack jobber merchandise separately.

3UHUHTXLVLWHV To manage rack jobbers, you must make the following settings in Customizing: •

The 9HQGRUQXPEHU field must be added to the field catalog for account determination in SD.

•

The 9HQGRUQXPEHU field must be added to the field catalog for price determination in SD.

•

If you want separate accounting for the sales revenue for the external goods and your own goods in Financial Accounting, a condition table must be added to SD account determination in the correct access sequence. Because rack jobbers are modeled as vendors, the condition table must contain the vendor number.

•

You can manually charge the fee that you want to receive from the sales revenue of the rack jobber goods at the end of the settlement period. Alternatively, you can have the system charge this fee every time sales data is posted. However, this may reduce performance. If you do this, you must create a discount condition type. The access sequence of this condition type must use a condition table that contains the vendor number. You can update the fee in the Information System or assign an account for this in Financial Accounting. The condition type for this must be configured accordingly in the relevant POS calculation schema (326in the standard system).

-XQH



6$35HWDLO

6$3$*

5DFN-REEHU0DVWHU'DWD

5DFN-REEHU0DVWHU'DWD 3UHUHTXLVLWHV You sign an agreement with a new rack jobber, and want to reproduce the process in the system.

3URFHGXUH 1. Create the rack jobber in the system if it does not already exist as a known vendor in the system. The same vendor can be used for both normal and rack jobber processing. 2. Enter the basic data and sales data for the articles that you want to manage as rack jobber goods if the articles do not already exist in the system. You can use the same article for both normal and rack jobber processing. For each store, you decide how the article is to be managed (this step takes place later). You must enter the sales data for the articles EHIRUHthe next step, as otherwise you may have problems determining the rack jobber in the operative processes. 3. Create an assortment module using the category 5DFNMREEHUPRGXOH Enter the vendor number that you created for the rack jobber in the 5DFNMREEHUfield. You can use the ,QYPDQDJHPHQWfield to control whether Inventory Management is to be active. You can use the $VVLJQUHYHQXHDFFRXQWfunction to enter a Financial Accounting revenue account that the rack jobber revenue is posted to. The revenue account must first have been created in Financial Accounting. From table list, select an entry that contains the vendor number. In the next list, assign the appropriate G/L account to the vendor. Use application 9, account assignment type .2)5, the chart of accounts used in the store concerned, and account key (5/ You can also define account determination for the account that is to contain the rack jobber fees. To do this, you use the account key that is entered in the calculation schema for the item in which the fee is charged. However, if fees are assigned to an account directly when every individual transaction is posted, performance is affected. It is better to assign the fees to an account at the end of a settlement period. Save the data and return to assortment module maintenance. 4. You can now enter the articles that are to belong to the rack jobber assortment module. 5. Assign the rack jobber assortment module to all the required assortments or retail sites. In doing this, you define that the articles listed in the rack jobber assortment module are managed as rack jobber goods in those assortments or retail sites. 6. If Inventory Management is to be active, create purchasing info records with info category &RQVLJQPHQWfor the rack jobber articles. 7. Use the Retail Pricing to define the sales prices for the rack jobber articles. Note: For rack jobber articles, you cannot calculate the sales prices on the basis of the purchase prices.

5HVXOW The master data needed for rack jobber processing is created in the system.



-XQH

6$3$*

6$35HWDLO 5DFN-REEHU,QLWLDO6XSSO\RI*RRGVWRWKH6WRUH

5DFN-REEHU,QLWLDO6XSSO\RI*RRGVWRWKH6WRUH 8VH The rack jobber delivers the goods to the store and thereby provides goods for the first time for the intended sales area.

3UHUHTXLVLWHV •

The settings in Customizing correspond to the listing in Vendor: Rack jobber [Page 179].

•

Master data is maintained as described in Rack jobber: Master data [Page 180].

$FWLYLWLHV •

If Inventory Management is active, you post the goods receipt (movement type . – 5HFHLSWZRSXUFKDVHRUGHULQWRFRQVLJQPHQWVWRUHV)

•

If Inventory Management is not active, you cannot enter a goods receipt.

-XQH



6$35HWDLO

6$3$*

5DFN-REEHU6HOOLQJ0HUFKDQGLVHLQWKH6WRUHV

5DFN-REEHU6HOOLQJ0HUFKDQGLVHLQWKH6WRUHV 8VH When merchandise is sold, you must differentiate between the merchandise that is the property of the rack jobber and the merchandise that is your property and treat these differently in followon functions.

3UHUHTXLVLWHV •

The settings in Customizing correspond to the listing in Vendor: Rack jobber [Page 179]

•

Master data is maintained as described in Rack jobber: Master data [Page 180].

)HDWXUHV If you want to carry out inventory management for the merchandise, you must scan the goods at the POS. You cannot sell goods at merchandise category or value-only article level if you want to carry out inventory management for the rack jobber merchandise. If you do not want to carry out inventory management, you can either scan the goods or sell them at merchandise category or value-only article level.



-XQH

6$3$*

6$35HWDLO 5DFN-REEHU6XEVHTXHQW6XSSO\

5DFN-REEHU6XEVHTXHQW6XSSO\ 8VH You can create purchase orders for rack jobber goods if the rack jobber is not responsible for replenishing sold articles.

3UHUHTXLVLWHV •

The settings in Customizing correspond to the listing in Vendor: Rack jobber [Page 179].

•

Master data is maintained as described in Rack jobber: Master data [Page 180].

•

To work with purchase orders, you must have selected the variant with Inventory Management.

)HDWXUHV You can create purchase orders in the following ways: •

Manually, using the Purchasing dialog transaction. If you use this option, enter item category .for the rack jobber goods.

•

Using the purchase order IDoc in the POS interface If you use this option, the store transfers the purchase orders electronically to the R/3 system. The purchase orders are then generated automatically. Item category .is assigned automatically.

•

Using replenishment On the basis of the sales data posted via the POS interface, purchase orders are created for the rack jobber automatically when required. In this case, too, item category .is assigned automatically.

-XQH



6$35HWDLO

6$3$*

5DFN-REEHU*RRGV5HFHLSW

5DFN-REEHU*RRGV5HFHLSW 8VH The rack jobber delivers the goods to the store and thereby provides goods for the intended sales area.

3UHUHTXLVLWHV •

The settings in Customizing correspond to the listing in Vendor: Rack jobber [Page 179]

•

Master data is maintained as described in Rack jobber: Master data [Page 180].

•

If Inventory Management is active, the goods receipt must be posted to the consignment stock. If a purchase order exists, you generally use movement type .. If no purchase order exists, you use movement type .5HFHLSWZRSXUFKDVHRUGHULQWR FRQVLJQPHQWVWRUHV 

)HDWXUHV You have the following options for posting goods receipts: •

Manually: You post the goods receipt using the dialog transaction. You must enter the movement type and vendor number. You enter item category .for the rack jobber goods.

•

Using the goods receipt/goods movement IDoc in the POS interface. If you use this option, the goods receipt data is transferred from the store electronically to the R/3 system. Item category .is assigned automatically.



-XQH

6$3$*

6$35HWDLO 5DFN-REEHU6HWWOHPHQWZLWKWKH5DFN-REEHU

5DFN-REEHU6HWWOHPHQWZLWKWKH5DFN-REEHU 8VH After a certain period, you must make a settlement with the rack jobber.

3UHUHTXLVLWHV •

The settings in Customizing correspond to the listing in Vendor: Rack jobber [Page 179].

•

Master data is maintained as described in Rack jobber: Master data [Page 180].

)HDWXUHV You have the following options for making a settlement with the rack jobber for goods sold: •

Your company issues a credit memo to the rack jobber at the end of the agreed settlement period. If Inventory Management is active, you can have the settlement program for consignment withdrawals (standard menu ,QYHQWRU\PDQDJHPHQW(QYLURQPHQW &RQVLJQPHQW&RQVJQPWIURPYHQGRU/LDELOLW\) create a credit memo for the rack jobber. If Inventory Management is not active for the rack jobber goods, you can create a credit memo manually. In this case, the amount for settlement is based on the value accumulated in the revenue account for the rack jobber.

•

The rack jobber issues an invoice to your company based on goods receipts. Invoice verification for rack jobber goods is currently not supported. If Inventory Management is active, you can run the consignment settlement program and compare the result with the rack jobber invoice. In addition, the GR document and sales statistics can be used for comparison purposes. Differences must be posted manually. If Inventory Management is not active, you can compare the total value of the invoice with the value of the revenue account for the rack jobber.

-XQH



6$35HWDLO

6$3$*

5DFN-REEHU3URFHVVLQJ5HWXUQV

5DFN-REEHU3URFHVVLQJ5HWXUQV 8VH When goods are returned, you differentiate between your own goods and rack jobber goods.

3UHUHTXLVLWHV •

The settings in Customizing correspond to the listing in Vendor: Rack jobber [Page 179].

•

Master data is maintained as described in Rack jobber: Master data [Page 180].

)HDWXUHV Like sales of rack jobber goods, returns from consumers are processed with using a minus sign or the ‘Reversal’ goods movement type (.). This posting is made automatically when POS sales are processed.

$FWLYLWLHV Returns of rack jobber goods to the vendor only need to be posted in the R/3 system if Inventory Management is active. If you post the goods, use movement type ..



-XQH

6$3$*

6$35HWDLO 5DFN-REEHU2WKHU*RRGV0RYHPHQWV

5DFN-REEHU2WKHU*RRGV0RYHPHQWV 8VH In addition to returns there are other goods movements, for example, transfer of stock to another store. These can be made in the following ways: •

Manually

•

Using the goods receipt/goods movement IDoc in the POS interface.

3UHUHTXLVLWHV •

The settings in Customizing correspond to the listing in Vendor: Rack jobber [Page 179]. •

Master data is maintained as described in Rack jobber: Master data [Page 180].

$FWLYLWLHV •

Manually You post the goods movement using the dialog transaction. You must enter the movement type and vendor number. You enter item category .for the rack jobber goods. You transfer goods to other stores in two steps. If the articles are managed by the same rack jobber in the receiving store, you post a goods receipt reversal (movement type . or .) in the supplying store. This prevents a liability being created for the rack jobber (the goods have not yet been sold). You then post a goods receipt in the receiving store (.). If the articles are managed by you in the receiving store, you post a goods issue for sales (.) in the supplying store. This creates a liability for the rack jobber (the goods become your property). In the receiving store, you post a goods receipt to your stock (e.g. using movement type ).

•

Using the goods receipt/goods movement IDoc in the POS interface. If you use this option, the posting is made automatically. In this case, too, the transfer posting is made in two steps. A stock transfer for consignment goods cannot be made in a single step.

-XQH



6$35HWDLO

6$3$*

5DFN-REEHU3K\VLFDO,QYHQWRU\

5DFN-REEHU3K\VLFDO,QYHQWRU\ 8VH If Inventory Management is active, physical inventory can be carried out for the rack jobber.

3UHUHTXLVLWHV •

The settings in Customizing correspond to the listing in Vendor: Rack jobber [Page 179].

•

Master data is maintained as described in Rack jobber: Master data [Page 180].

$FWLYLWLHV Enter value . in the 6SHFLDOVWRFN field for the rack jobber articles.



-XQH

6$3$*

6$35HWDLO 5DFN-REEHU7UDQVIHUULQJ*RRGVWR