Basic Principles

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_erp60_sp/helpdata/en/88/95c7536e8e2a4be10000000a174cb4/content.htm

Created on April 12, 2016

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Table of content
1 Basic Principles
1.1 This Documentation
1.1.1 Link to Corresponding General Documentation
1.2 SAP Retail Overview
1.2.1 Integration of SAP Retail in the Standard Environment
1.2.2 Areas of Application of SAP Retail
1.2.3 Distributed Data Processing
1.3 Configuration as SAP Retail
1.3.1 Differences Between Articles and Materials
1.3.2 Standard Functions Used in SAP Retail with Articles
1.3.3 Standard Functions Not Supported in SAP Retail
1.3.4 Standard Functions not Tested with Articles in SAP Retail
1.4 Retail Terminology
1.5 Roles
1.6 Initial Menu for SAP Retail
1.7 Organizational Structure
1.7.1 Organizational Structure: Example
1.7.1.1 Organizational Structure: Examples
1.7.2 Organizational Structure: Corporate Group
1.7.3 Organizational Structure: Company Code
1.7.4 Organizational Structure: Site
1.7.5 Organizational Structure: Site Group
1.7.6 Organizational Structure: Vendor
1.7.7 Organizational Structure: Purchasing Organization
1.7.8 Organizational Structure: Purchasing Group
1.7.9 Organizational Structure: Purchasing Area
1.7.10 Organizational Structure: Stock Planner Group
1.7.11 Organizational Structure: Sales Organization
1.7.12 Organizational Structure: Sales Group
1.7.13 Organizational Structure: Sales Department
1.7.14 Organizational Structure: Distribution Channel
1.7.15 Organizational Structure: Distribution Chain
1.7.16 Organizational Structure: Division
1.7.17 Organizational Structure: Sales Area
1.7.18 Organizational Structure: Sales Office
1.7.19 Organizational Structure: Storage Location
1.7.20 Organizational Structure: Department, Receiving and Unloading Po
1.8 Vendor Consignment
1.8.1 Consignment Processing in SAP Retail
1.8.2 Goods Issues for Stock Transfers
1.8.3 Displaying Consignment Stock in Transit
1.8.4 Determining the Stock Situation After Sales
1.8.5 Allocation of Vendor Consignment Goods
1.8.6 Returns of Vendor Consignment Goods
1.9 Background Processing
1.9.1 Parallel Processing of Background Jobs
1.9.1.1 Load Distribution and External Parallel Processing
1.9.2 Background Processing: Retail Terminology
1.9.3 Background Processing: Site
1.9.3.1 Background Processing: Setting Central Block for Sites
1.9.4 Background Processing: Conditions
1.9.4.1 Background Processing: Generating Worklist Entries From Change P
1.9.4.2 Background Processing: Adjusting Documents after Condition Chang
1.9.5 Background Processing: Assortment
1.9.5.1 Background Processing: Value-Only Article Listing
1.9.5.2 Background Processing: Change Assortments Automatically After Ma
1.9.6 Background Processing: Assortment List
1.9.6.1 Background Processing: Automatic Generation of Assortment Lists
1.9.7 Background Processing: Markdown Planning
1.9.7.1 Background Processing: Markdown Price Phase Activation

PUBLIC Page 2 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.9.7.2 Background Processing: Markdown Plan/Actual Comparison
1.9.7.3 Background Processing: Price Calculation Test
1.9.8 Background Processing: Promotion
1.9.8.1 Background Processing: Generating Messages for Promotion Announc
1.9.8.2 Background Processing: Subsequent Processing for Promotions
1.9.8.2.1 Background Processing: Promotion Price Activation
1.9.8.2.2 Background Processing: Promotion Allocation Table Generation
1.9.8.2.3 Background Processing: Promotion Listing
1.9.8.2.4 Background Processing: Promotion Announcement
1.9.8.2.5 Background Processing: Promotion Supply Source Determination
1.9.9 Background Processing: Pricing
1.9.9.1 Background Processing: Pricing Worklist Based on Changes to Fact
1.9.10 Background Processing: Requirements Planning
1.9.10.1 Background Processing: Forecast per Period Indicat
1.9.10.2 Background Processing: Total Planning per Site
1.9.11 Background Processing: Order Cancelation
1.9.11.1 Background Processing: Performing Order Cancelations
1.9.12 Background Processing: Allocation
1.9.12.1 Background Processing: Generating Messages for Notifications
1.9.12.2 Background Processing: Follow-On Documents for Allocation Tables
1.9.13 Background Processing: Ordering
1.9.13.1 Background Processing: Adjusting Purchasing Documents after Cond
1.9.14 Background Processing: Seasonal Procurement
1.9.14.1 Background Processing: Deletion of Completed Worklist Items
1.9.14.2 Background Processing: Remaining Quantities for Order Items
1.9.15 Background Processing: Invoice Verification
1.9.15.1 Background Processing: Immediate Invoice Verificat
1.9.16 Background Processing: Subsequent (End-of-Period) Settlement
1.9.16.1 Background Processing: Settling Rebate Arrangements
1.9.16.2 Background Processing: Extension of Periodic Rebate Arrangements
1.9.16.3 Background Processing: Compilation of Statistics and Retrospecti
1.9.17 Background Processing: Inventory Management
1.9.17.1 Background Processing: Revaluation at Retail
1.9.18 Background Processing: Logistics Execution
1.9.18.1 Replenishment for Fixed Storage Bins
1.9.19 Background Processing: Additionals
1.9.19.1 Background Processing: Generating Additionals Purchase Orders
1.9.19.2 Additionals: Change Analysis
1.9.20 Background Processing: Replenishment
1.9.20.1 Background Processing: Auto-Replenishment
1.9.20.2 Background Processing: Check Consistency of Replenishment Data
1.9.21 Background Processing: Multi-Step Replenishment
1.9.21.1 Background Processing: Automatic Multi-Step Replenishment
1.9.22 Background Processing: POS Interface
1.9.22.1 Background Processing: Initializing Outbound Processing
1.9.22.2 Background Processing: Periodic Outbound Processing for Stores
1.9.22.3 Background Processing: Repeating Terminated/Buffer
1.9.22.4 Background Processing: Repeating Unsuccessful POS
1.9.23 Background Processing: SAP Retail Store
1.9.23.1 Background Processing: Linking to PDC Units SAP Retail Store
1.9.24 Background Processing: Information and Planning Sy

PUBLIC Page 3 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1 Basic Principles
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.

1.1 This Documentation

Einführung in das SAP-System
This documentation describes the SAPRetail 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 ERP system.

Note
This documentation describes the standard version of the SAPRetail 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 F1.

Caution
This documentation is not a guide to Customizing the system. Please use the SAP Implementation Guide (IMG)

See also:
Getting Started
Customizing
Roles
Relevant Cross-Application Documentation
Help on Help

1.1.1 Link to Corresponding General Documentation

SAP Retail is a fully integrated, self-contained system comprising all the functions you require to model retail business processes. SAPRetail also includes
general SAP components such as Financial Accounting, Controlling and Human Resources.
And at the heart of the system is functionality specially developed for retailing (IS-R). The functionality is based on the SAP components Materials
Management (MM), Sales and Distribution (SD), Logistics - General (LO) and Logistics Execution (LE). Links can also be created to new dimension
systems, such as SAPBusiness Information Warehouse (SAP BW) and SAPAPO.

This documentation describes SAP Retail in a retailing context. Many topics do, however, contain references to additional information in other areas of the
SAP Library. These references point you to the relevant part of the documentation.
In certain circumstances – for example, if your company also has manufacturing operations–you may use some components that are purely MM, SD or LE. In
this case, you can reach the documentation for these areas by choosing Help SAP Library .

Caution
If you follow a link to another part of the SAP Library, the text that appears has a different structure to this documentation. Also, the terminology used is
standard SAP terminology which is not specific to your SAP Retail system.

For further information on the different terminology, see Retail Terminology .

PUBLIC Page 4 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 See also:
Relevant Cross-Application Documentation

SAPRetail Overview
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 "Value Chain," 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
Warehouse Management
Picking and Delivery
Billing
Store Supply
The retailing processes enable you to control and coordinate the whole value chain, and thus 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.
See also:
This Documentation: Link to Corresponding General Documentation
Organizational Structure

Integration of SAPRetail in the Standard Environment

SAPRetail includes the base components such as Financial Accounting, Controlling and Human Resources. And at the heart of the system is functionality
specially developed for Retailing (IS-R).
The following illustration shows the areas comprising SAP Retail:

The total integration of SAPRetail opens up new opportunities for increased cooperation between retailers and vendors. This cooperation can take place in the
standard system without complex linking of 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.

Areas of Application of SAPRetail

SAP Retail integrates all the key areas of retailing and wholesaling, all the various stages in the supply 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

PUBLIC Page 5 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 retail sector.

1.2.3 Distributed Data Processing

Use
SAPRetail provides interfaces with which you can achieve distributed data processing (Distributed Data Processing, DDP). Subtasks that logically belong
together are distributed to several computers that are connected together by a network. This results in decentralization for operating tasks that can be
achieved immediately, and better, without the need for central processing. If necessary, the system can also provide other computers with data that is saved
in different places.
The functions in the SAP System are modular. This simplifies any adjustment of the system to different enterprise organizations. You can store individual
areas in the central office for example, by decentralized processing of goods receipts in stores, but carrying out invoice verification in the central system.
Corresponding interfaces and comparison programs consolidate data.
SAPRetail also provides interfaces for communicating with external systems, for example, for electronically sending purchase orders to vendors and sales
data to market research companies, as well as for exchanging data with space management and workforce planning systems.
Distributed data processing has the following advantages:
Improved performance
Greater security
It promotes decentralized company policies, which provides sites with a high degree of autonomy. This allows whole areas of responsibility to be
assigned to those organizational units at which information - on customers, vendors or goods movements - is usually gathered.

Integration
Retail uses distributed data processing principally in the area of stores. The following illustration shows how distributed retailing systems are typically used:

The following areas are important for distributed data processing:

POS Interface
You can use the POS interface functions to link up the POS systems in your stores to the SAP Retail system.
SAP Retail Store
SAP Retail Store is a separate software product that enables you to run SAP Retail functions designed or adapted by SAP for specific use in-store.
Distribution of Applications to Multiple Systems (ALE)
The technology described here allows you to distribute the functions contained in the central SAP Retail system among several SAP systems, and to
connect non-SAP systems.
AFS/SAP Retail interface
Using this interface it is possible to link an AFS system with SAP Retail.
See also:
Remote Access to SAP Retail

1.3 Configuration as SAP Retail

Use
The requirements that retail companies place on software solutions, in particular in the areas of planning and distribution, are different from the requirements of
industrial companies, with their production-oriented objectives. For this reason, SAP developed a special retail solution, which you can use by setting up the

PUBLIC Page 6 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 SAP ECC component as SAP Retail. You do this by activating the SAP Retail business function set.

Integration
Activating the SAP Retail business function set enables you to use functions developed specifically for the retail sector. These functions are described in this
documentation. A significant difference between the retail system and a manufacturing system is the use of the article master as opposed to the material
master. The majority of the retail-specific functions can only be used with articles and not with materials. In all other functions that are also relevant for retail, it
is possible to use articles. However, it is often not possible to use articles in production-oriented functions. Note that most of these functions have not yet
been tested with articles. There are no restrictions for using materials in an ECC system set up as SAP Retail, however, apart from in the Material Ledger
and MRP Area functions.

Note
If you want to use articles in functions with a production focus, make sure that this has been thoroughly tested in your project.

Note
If you activate the SAP Retail business function set, you cannot use any other industry solutions. Once you have configured your system as an SAP
Retail system, it cannot be reversed.

In the case of the terms ‘material’ and ‘article’, we differentiate between the master data and their designation on the system user interface. Whereas either
‘material’ or ‘article’ is used consistently for both master data records in the system (see Retail Terminology ), this part of the documentation uses ‘material’ for
master data records that were created using the maintenance transactions in the standard system (manufacturing system), and ‘article’ for master data
records created using the maintenance transactions in SAP Retail .

Prerequisites
You should only configure SAP ECC as SAP Retail if you are in possession of a valid license for SAP Retail.

Activities
If you activate the business function set SAP Retail, the core functions Material Ledger and MRP Area are no longer available. If you already use these
functions and want to configure your system as an SAP Retail system, you must first deactivate these functions. The applications contain functions for
reorganizing the data associated with this.
Vendor master processing represents another anomaly. If you make the relevant setting in Customizing in SAP Retail, changes made to master data can be
automatically passed on to associated material master data and purchasing info records. While the standard system ignores these settings in Customizing in
the account groups for vendors, any settings that have been made will become active when the SAP Retail business function set is activated, therefore
potentially changing the system behavior. Before you switch on the business function set, you should therefore check the settings for transferring changes to
master data in Customizing for Logistics - General under Business Partner Vendors Control Define Account Groups and Field Selection
(Vendor)and, if necessary, adjust these settings.
Finally, activate the SAP Retail business function set. For more information, see the Implementation Guide under Activating SAP ECC Extensions .

1.3.1 Differences Between Articles and Materials

In the case of the Retail solution, the central object in all logistics processes is the article, whereas in industry it is the material.
Retail and industry have different needs in terms of the corresponding master data and maintenance options. For example, to optimally process all its fashion
processes, retail needs variants (such as color and size). Industry, however, uses bills of material for special requirements in the area of production planning.
Due to the large number of articles in the retail industry, master data maintenance must also be integrated into processing.
To best support the different processes in retail and industry, ECC provides different maintenance transactions for materials and articles. Unlike the material
master, the article master contains the following additional points:
Specific additional data is integrated, for example, purchasing info records, listings and sales price calculations.
Several organizational levels, for example, sites and distribution chains, and for generic articles several articles, can be processed online in one single
maintenance transaction.
In the material master you can process only one material or one plant at a time, but in the article master the system transfers data from higher levels to
the dependent levels, provided you have not maintained these differently. For example, the system transfers data from a generic article to all its
variants. It also transfers data from reference sites to individual sites.

1.3.2 Standard Functions Used in SAP Retail with Articles

The following standard functions can also be used with articles. However, not all functions support retail-specific processing of generic articles (for example,
matrix maintenance).

Caution
We recommend that you do not use materials and articles in SAP Retail at the same time. The functions listed here were tested as part of individual
customer projects, using the existing conditions and system settings.
If there are times when you really cannot keep to this recommendation, ensure that you enlist the help of experienced SAP consultants in your project and
plan and execute comprehensive tests.

Materials Management (MM)

PUBLIC Page 7 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 All functions are available.
In SAP Retail there are two stock overviews for articles and materials.
Standard stock overview (transaction MMBE )
It is also possible to use the batch stock here to make selections.
Retail stock overview (transaction RWBE ) for article selection
It is also possible to use merchandise categories here to make selections.
Batch management can generally be used with single articles. However, some Retail functions (for example, allocation tables, store orders) do not
take batches into consideration.
Sales and Distribution (SD)
All functions are available.
Production Planning (PP)
PP bills of material with individual articles and variants of generic articles.
Product groups
You can assign articles or materials to a product group that you have created with transaction MC84 .
Product cost calculation
The product cost calculation can also be used as the basis for sales price calculations. You can use the special procurement key for the
calculation (for example, for calculation data from another site).
Material requirements planning (MRP)
You can also use the special procurement key for requirements planning, for example, for production in another plant.
Planned orders
Conversion of planned orders into production orders
Production order confirmation
Discreet production of single articles and variants of a generic article
Variant configuration with make-to-order production without variants subject to inventory management
Repetitive manufacturing
Constraint: You must use the standalone transaction C233 to create production versions for articles.
Service Management (SM)
All functions are available.
Quality Management (QM)
All functions are available.
Constraint: You can only access the maintenance screen for QM check data for articles using the standalone transaction QA08 . The display is
integrated into the article master.
Foreign Trade
Intrastat/Extrastat
Preference processing (vendor declaration)
Letter of credit processing for export
Foreign trade forms (T1, T2, export declaration)
Tax handling for Brazil
Additional tax and categorization fields are needed for goods movements in Brazil . These fields cannot be maintained in the article master, but can be
easily integrated into a user-specific article master.

1.3.3 Standard Functions Not Supported in SAP Retail

SAP Retail supports the special function for handling generic articles in Materials Management and Sales and Distribution only, not in any of the other
standard areas.
SAP Retail does not support the following standard functions with articles: You can therefore only use these functions for materials:
Variant configuration with inventory-managed variants
You can only use variants of a generic article in the variant configuration as an item in the super bill of material. You cannot use generic articles in bills
of material.
Long-term planning
You cannot maintain specific data for long-term planning for articles.
Co-product production
You cannot create specific data for co-product production (for example, apportionment structure for costs) for articles. You can map production
transactions with by-products in the bill of material, using articles with a negative quantity.
Foreign Trade
Legal controls
Preference determination
Letter of credit processing for import
Forms: Single registration, collective registration
Production resources/tools
You cannot maintain specific data for production resources/tools for articles. Instead, you should use materials.
Material ledger
SAP Retail does not support the material ledger. This is due to the likely performance problems that would occur when dealing with a large number of
articles in many stores, and compatibility problems between certain retail-specific valuation procedures (value articles, RMA) and the material ledger
(see also customer message 11192/2002). An enhancement would then be needed in the article master and the material ledger (sales values must be
updated in the material ledger and the data structures and the update must be extended).
Valuation levels above the plant (company code).
To do this, extensive enhancements may be required in the article master and in other areas.
Plan article changes (change service)
Revision level for articles
Manufacturer part number management
Proportion unit, active ingredient unit of measure
Creation of articles using the CAD interface
Inflation handling for South America
Special handling tool for South American countries that require a revaluation method once a particular inflation rate has been exceeded. To do this,
article valuation data must be updated in a table for this purpose ( Inflation MBEW , same key as MBEW ). You cannot currently maintain this data in
the article master.

PUBLIC Page 8 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Requirements planning areas
If a system is primarily a retail system you can generally not activate any requirements planning areas, not even for materials. The article master does
not provide any segments for requirements planning parameters.
For information on deactivation within a Retail system, see Note 163001.
Transaction parameters and planning parameters (process manufacturing)

1.3.4 Standard Functions not Tested with Articles in SAP Retail

SAP has not tested the following functions for use with articles:
Plant maintenance (PM)
Recommendation: If possible map this area in SAP Retail with materials.
Subcontracting with generic articles
LIFO and FIFO analysis
Production planning (PP-PI)
Using serial numbers with generic articles
Project System (PS)
If you want to use one of these functions you must make sure that the function works correctly in your project.

1.4 Retail Terminology

SAP ECC is developed and delivered using standard SAP terminology. In the retail industry, however, some languages use terms that differ from these
standard terms. SAP therefore offers customers working in these languages a tool for converting the standard terms on the user interfaces of the entire
standard system to the terms specific to the retail industry. This technique is known as Short Text Replacement .
The documentation for SAP Retail is based on the assumption that you have replaced the short texts in your ECC system. When you follow links from the
Retail documentation to other parts of the SAP documentation, however, note that standard SAP terminology is used.
The following terms differ depending on where you are in the documentation:

SAP Retail Other parts of the documentation

Article Material

Site Plant

Logistics calendar Factory calendar

In the SAP Service Marketplace, you can find out the languages and components for which short text replacement is available and how to activate it (
http://service.sap.com/retailhttp://service.sap.com/retail ) under Expert Knowledge Corner → Across Components → Short Text Replacement in
http://service.sap.com/~sapidb/011000358700007294492001E/ShortTextReplacement.pdfRetail Short Text Replacement .

Terminology is only replaced on the user interface (short texts). In certain situations, for example, in the F1 help, terms such as Material instead of Article
and Plant instead of Site appear in this version of the SAP system. Standard SAP terminology is used, in particular, in the Implementation Guide (IMG).
Short text replacement is client-independent.

See also:
Background Processing: Retail Terminology

1.5 Roles
SAPRetail is an integrated part of mySAP ERP. Using a Web Browser, the workplace in mySAP ERP provides the user with a role-based portal for improving
the level of efficiency when carrying out tasks. The screen here is tailor-made for the specific roles of the user in the firm and at their desk.The user registers
once (single sign-on) and in doing so gains access to all relevant functions, services and information for example, to:
classic and new web-based transactions (for example, SAP ECC, SAP BW and business solutions)
Internet Application Components (IACs)
self-service scenarios
reports (for example, SAP BW reports)
non-SAP systems
any internet and intranet pages
You will find a summary of the roles specially developed for SAP Retail under Single Roles SAP Retail . Roles from the following areas are also particularly
important for users of SAPRetail:
Single Roles Logistics General
Single Roles Materials Management
Single Roles Logistics Execution
Single Roles Sales and Distribution
Single Roles Basis
See also:
BC – Users and Roles

1.6 Initial Menu for SAP Retail

From the SAP Retail main menu, choose

PUBLIC Page 9 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Logistics Retailing

Note
This menu path is only available if you set up your start menu as SAP Retail.
To set up your default start transaction, choose System User profile Own data. On the Defaults tab page, enter W10Tin the Start menu field
and choose Save .
You can only use the full set of functions for SAP Retail if you have configured your system as an SAP Retail system (see Configuration as SAP Retail ).

1.7 Organizational Structure

Flexible organizational units make it possible to reproduce even the most complex corporate structures in the standard system. The large number of
organizational units available in the system enables you to reflect the legal and organizational structure of your company in the system and represent it from
different viewpoints.
The most important organizational units are listed below. Their meaning in SAPRetail is described briefly. 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.

1.7.1 Organizational Structure: Example

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
The organizational structure of the company in the example graphic would be modeled in SAP Retail as follows:
Central purchasing
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.
Local purchasing
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.
Distribution chains
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.
Distribution center, Store
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.
Storage location, Storage section, Department
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.
Customer
The value chain concludes with the customer or consumer. If the customer is recorded in the system (and is therefore an identifiable customer), natural
persons can be defined in the customer master as the contact persons at that customer.

1.7.1.1 Organizational Structure: Examples

The following figures are typical examples of how a retailing company is organized and how this organization can be mapped to SAP Retail.

1.7.2 Organizational Structure: Corporate Group

Definition
A corporate group is the affiliation of legally independent companies under the common management of a controlling company. It is the highest of all
organizational units in the hierarchy, and corresponds to a retailing company with several subsidiaries (for example), which are defined from a Financial
Accounting point of view as individual company codes .
Use
Data defined at corporate group level is valid for all purchasing and sales organizations.
Integration
On the logistics side, the corporate group divides into sites. 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. Sites can be grouped together using the Classification System.

1.7.3 Organizational Structure: Company Code

PUBLIC Page 10 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Definition
A company code is an independent accounting unit that represents an independent company in the legal sense. It is the central organizational element in
Financial Accounting.

Use
In the retail sector, company codes can be used 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 SAPRetail.

Integration
Various assignments between a company code and other organizational units are possible:
A purchasing organization can be assigned to a company code. In this case, the purchasing organization can only order for sites within this company code.
A valuation area is the organizational unit subject to inventory management on a value basis in the SAP system. In SAP Retail, the valuation area must
always correspond to a site.
You assign a company code as an attribute to the valuation area that is already allocated to a site either in the site maintenance or in Customizing.
Each sales organization must be assigned to a company code in Customizing. This assignment forms the link between Sales and Distribution and Accounts
Receivable Accounting.

1.7.4 Organizational Structure: Site

Definition
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.

Integration
A store is assigned one purchasing organization and one sales area (sales organization, distribution channel and division) and thereby also a distribution
chain, 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 recipient
store must also 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 site (normally to itself) and a distribution chain (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 company code .
See also:
Sites

1.7.5 Organizational Structure: Site Group

Definition
A site group is a number of sites that have been grouped together using the Classification System.

Use
You can use the Classification System to group together sites that have similar characteristics or are located close to each other, for example. This simplifies
data maintenance, and can also be of use for reporting purposes.

Integration
To create site groups, at least one class type has to be defined in the Classification System.
Application groups 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 independently of company codes, distribution chains and other fixed organizational structures.

1.7.6 Organizational Structure: Vendor

PUBLIC Page 11 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Definition
Vendors are the organizational units that deliver merchandise to sites or customers (the latter is possible in wholesale, for example, if a third-party
arrangement exists). These vendors are normally external suppliers.

Integration
Whether sites 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 customer 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.
See also:
Business Partner

1.7.7 Organizational Structure: Purchasing Organization

Definition
The purchasing organization is an organizational unit which procures articles and negotiates general purchase price conditions with vendors . It is responsible
for all purchasing transactions in the company.
Use
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.
The purchasing organization is used in the following areas:
When a stock transport order (order type UB) is created, 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 no company code is assigned to the purchasing organization, SAP Retail uses the company code assigned to the ordering sites. Alternatively, you can enter
a company code manually. 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 standard purchase orders (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 outline agreements (contracts, scheduling agreements).
Because promotions and allocation tables 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.
In a request for quotation issued to the vendor , the purchasing organization invites a vendor assigned to it to submit a quotation.
Integration
Purchasing organizations are data retention levels for many types of master data.
One (and only one) company code can be assigned to a purchasing organization. A purchasing organization that 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 return delivery are assigned the same purchasing organization but these sites belong to different company codes.
A site can be assigned to the purchasing organization that 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 sales organization 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 reference purchasing organizations to a purchasing organization. This allows the purchasing organization access to
the conditions and contracts of these reference purchasing organizations. The purchasing organization can make use of up to two reference purchasing
organizations when the sequence in which it accesses conditions is determined.
Vendors 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 purchase price determination , 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.
Each buyer is assigned to a purchasing organization in his or her user master.

1.7.8 Organizational Structure: Purchasing Group

Definition
A purchasing group corresponds to a buyer or group of buyers who perform the following purchasing activities:
Procuring certain articles or merchandise categories

PUBLIC Page 12 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Acting as the contact for vendors
Use
Purchasing groups can function strategically, operationally, or both.
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.
The purchasing group is also responsible for the day-to-day planning of requirements and ordering of merchandise.This includes creating purchase orders,
allocation tables and promotions. It can also send vendors requests for quotation or create purchase requisitions.
Integration
Purchasing groups are assigned to the purchasing areas. They 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.
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.
Every stock planner is assigned to a purchasing group. You make the assignment in the user master.

1.7.9 Organizational Structure: Purchasing Area

Definition
A purchasing area is an organizational unit that is assigned to the purchasing organizations responsible for negotiations with vendors and the master data
maintenance that results from them.

Use
Purchasing areas are only used in the Information System and in standard reporting. No data or authorizations are stored at purchasing area level.

Integration
A purchasing group can only be assigned to one purchasing area in a purchasing organization.

1.7.10 Organizational Structure: Stock Planner Group

Definition
A stock planner group is a stock planner or group of stock planners responsible for requirements planning.

Integration
A site is subdivided into stock planner groups. 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.

1.7.11 Organizational Structure: Sales Organization

Definition
A sales organization is an organizational unit in Logistics that structures the company according to its sales requirements.

Use
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 the sale 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.

Integration
Each sales organization is assigned one company code . This company code tracks the business transactions of the sales organization from a mainly
financial accounting point of view.

Note
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).

PUBLIC Page 13 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 In SAP Retail, a sales organization can be assigned a purchasing organization . 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.
Employees 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 reference sales organization so that
only those sales and distribution document types found in the reference are allowed in the assigned sales organization.

1.7.12 Organizational Structure: Sales Group

Definition
Sales groups (for example, each with a sales manager) are subdivisions of a distribution chain.

Use
Sales groups can be used for reporting purposes.

Integration
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 store. These sales groups are then responsible for SD sales orders in that store.
You can assign employees to a sales group.

1.7.13 Organizational Structure: Sales Department

Definition
Sales departments are subdivisions of stores.

Use
Sales departments are used to group together merchandise categories in a store and determine procurement activities in the store.

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.

Integration
Each department can be assigned a receiving point .
See also:
Sites: Definitions

1.7.14 Organizational Structure: Distribution Channel

Definition
The distribution channel is the channel through which saleable materials or services reach the customer. Distribution channels include selling to consumers
through various types of retail outlet or via mail order.
Use
Each distribution channel is assigned to a sales organization , and these two units together form a distribution chain. Multiple assignments are possible.
Integration
Data is not retained at distribution channel level. A distribution channel level is not a data retention level until it has been combined with a sales organization or
(later) a division as well.

1.7.15 Organizational Structure: Distribution Chain

Definition
The purpose of a distribution chain is to structure sales within a retail company. A distribution chain is made up of a sales organization and a distribution

PUBLIC Page 14 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 channel .

Use
Many retail companies use a variety of different sales channels to sell to their customers. These include store-based retailing, wholesale and Internet selling.
In the case of store-based retailing, stores can belong to different chains, which have a common look and feel, a common assortment and common goods
presentation but which target different groups of customers. SAP Retail reflects these different sales channels by means of distribution chains.
In addition to the marketing aspect, distribution chains are used in conjunction with sales area data to control logistics processes.
Distribution chains are also important for sales pricing. It is not only possible to determine sales prices for an individual site or customer but also for an entire
distribution chain.
Distribution chains also have an important role as structuring characteristics for reporting on sales.

Integration
There are three types of distribution chains in SAP Retail:
Store distribution chains
Distribution center distribution chains
Wholesale distribution chains
You assign the distribution chain type in Customizing under Distribution chain control. Among other things, the distribution chain type controls different
logistics processes. In sales price calculation, it controls whether the sales price includes taxes or not.
Customer relationships are important for controlling logistics processes. You maintain these according to sales area. A sales area is a combination of a sales
organization , distribution channel and division . Unlike in industrial companies, there is generally no differentiation made in SAP Retail between product-related
divisions, therefore the distribution chain is definitive for the customer relationship.
You determine which distribution chains each site is going to use to deliver its merchandise. For a store that sells to consumers, the only available option is
generally a store distribution chain, which represents a suitable chain of stores. Sometimes, however, you may need to differentiate between anonymous
consumers and your known major customers, to whom you offer special prices. In this case you can set up a major customers distribution chain for your major
customers. For distribution centers you can set up different distribution center distribution chains to supply the stores in the different chains, which have
different transfer prices. For stores that are supplied by a distribution center, you maintain customer relationships for these distribution chains.
The significance of the distribution chain for logistics and price determination is also manifest in integrated article maintenance. In the distribution chain-related
sales view you maintain data that is relevant for delivery, for example, the sales unit. For price determination, you maintain the actual sales price and other
condition parameters but you also need to enter certain control data, such as the price fixing flag or the competition characterization of the article.
If there are lots of distribution chains, you can set up reference distribution chains to reduce the amount of work needed to maintain customer and article
master data and conditions. To do this, enter suitable reference distribution channels for a distribution chain in Customizing under Distribution chain control.

1.7.16 Organizational Structure: Division

Definition
A division is an organizational unit based on responsibility for sales or profits from saleable materials or services.

Use
Divisions have two main applications: They are organizational units for Sales and Distribution, and they are necessary for business area account assignment
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 not used for any functions developed specifically for SAP Retail. However, a single dummy division is provided where necessary.

Integration
Articles are assigned uniquely (client-wide) to one division.
Divisions are assigned to sales organizations .
For each combination of sales organization and division there is a reference division 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.

1.7.17 Organizational Structure: Sales Area

Definition
The sales area is the combination of a distribution chain (a sales organization and a distribution channel) and a division . 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.

Use

PUBLIC Page 15 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 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 sales price calculation schema in Sales Pricing.

Integration
Each site 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.

1.7.18 Organizational Structure: Sales Office

Definition
A sales office is an organizational unit in sales and distribution which is responsible for sales within a specific geographical area.

Use
Sales offices are used in sales transactions in the Sales and Distribution component. They can be used for reporting purposes. Sales offices are optional.

Integration
A sales office can be assigned to one or more distribution chains .
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 regional sales manager is then responsible for supplying the stores assigned to him with merchandise.
You can also treat each store as a sales office. This enables you to obtain statistics on the sales volume and revenue that a store achieves through SD sales
orders.
Employees can be assigned to a sales office.

1.7.19 Organizational Structure: Storage Location

Definition
A storage location is an organizational unit that allows you to differentiate between various types of stock in a site.

Use
Stocks of an article can be managed within a site in different storage locations to differentiate, for example, between the stock stored for returns, promotions
and cross-docking. Storage locations are intended to represent warehouses or areas in a warehouse.
To reflect the complex warehouses that are typical in retailing, each storage location can be divided into warehouse numbers, storage types and storage bins
using the Warehouse Management System. Storage locations are then used 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 be used.

1.7.20 Organizational Structure: Department, Receiving and

Unloading Point

Definition
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 site.
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. If you know a department, you can therefore also determine the receiving point and the
unloading point.
Using departments and receiving points enables you to more precisely 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 rec ipient ’s use or sale.

PUBLIC Page 16 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Example
A pallet load of merchandise is delivered to door 1 at a department store (unloading point) . The shipment is divided up and delivered to one or more floors
(internal receiving points). From there, the packages are delivered to one or more departments, such as Housewares, Consumer Electronics, Health &
Beauty Aids, or Ladies’ Apparel.

Use
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 ( Sales Order Processing Maintain Promotion/Receiving Point Determination per Sales Document Type ) you can specify for
each type of document whether or not automatic department and receiving point determination is to be possible.

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

Integration
The system can automatically determine the appropriate department and receiving point for an article. For this to occur for internal sites (for example, stores or
distribution centers), you have to assign merchandise categories in the site master record.
You then assign valid departments and receiving points to the 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.
See also:
Site: Definitions

1.8 Vendor Consignment

Use
You can order goods from external vendors as vendor consignment goods. You carry the goods in the vendor consignment stock in your site and therefore
they remain the property of the external vendor (special stock manager) and do not belong to your valuated stock.

Features
You can use either of the following to process vendor consignment goods:
Consignment processing in a manufacturing system
Consignment processing in SAP Retail

Consignment processing in a manufacturing system

This contains the following main functions:
You can order goods from an external vendor as consignment goods by setting the Consignment item category manually in the purchase order.
You can transfer goods in the consignment stock of your site to other sites. To do this, you post goods manually from the consignment stock to your
own stock. This creates a legally binding contract with the external vendor.
For more information, see the Special Stock and Special Procurement Forms (MM-IM) component under Consignment .

Consignment processing in SAP Retail

In contrast to processing in a manufacturing system, this covers the following functions:
In the article master data, you can specify that you specifically want to procure the goods in one site as consignment goods. You can define the
consignment control for an article for each site (for example, distribution center, store) independently of one another.
The system automatically converts goods that are to be transferred from a site’s consignment stock to a site's own stock.
You can transfer goods from your consignment stock to other sites and retain the consignment stock category. Goods in consignment stock can be
transferred across sites and company codes as often as necessary. The goods remain the property of the external vendor until they are sold. Only once

PUBLIC Page 17 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 transferred across sites and company codes as often as necessary. The goods remain the property of the external vendor until they are sold. Only once
they are sold does a legally-binding contract exist.
For more information, see Consignment Processing in SAP Retail .

Note
Consignment processing in SAP Retail supports the following processes:

External procurement
Internal procurement using stock transfer with delivery
Sales at POS terminals
Consignment processing in SAP Retail

1.8.1 Consignment Processing in SAP Retail

Use
Consignment processing in SAP Retail gives you flexibility when dealing with vendor consignment goods. If you transfer vendor consignment goods using
stock transfers and delivery, you can keep the same stock category, or the system can convert the goods to your own stock, depending on the requirement of
the receiving site and the result of stock determination. If you transfer vendor consignment goods and keep the consignment stock category, the goods remain
the property of the external vendor until they are sold.

Note
The following process describes how goods are processed, with the focus on vendor consignment goods. However, it is also possible to process goods in
consignment stock and goods in your own stock at the same time.

Prerequisites
You have activated consignment processing in SAP Retail.
For more information, see the Implementation Guide (IMG) for Logistics – General under Retail Consignment Processing Activate Retail
Consignment Processing .
You have defined strategies for stock determination for goods issues (delivery) for your own stock and for consignment stock.
For more information, see the Implementation Guide (IMG) for Logistics - General under Retail Consignment Processing Define Strategies for
Stock Determination and Define Alternate Stock Determination Rules for Consignment Processing .
You have created purchasing info records for consignment. For stock transfers, the price test must define the same price for the issuing and the
receiving site.
For more information, see the Purchasing (MM-PUR) component under Purchasing Info Record .
For preferential procurement of articles for consignment stock, you have set the Consignment Control flag.
To enable the pricing purchasing info records for consignment to be taken into account, you have defined the Source of Supply appropriately in the
article master data.

Caution

PUBLIC Page 18 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 The settings for the source of supply and consignment control must be consistent.

Procedure
1. You order goods as vendor consignment goods from an external vendor. You carry the goods in Consignment special stock in your site.
2. You can transfer vendor consignment goods as often as necessary across sites. Depending on the stock situation and the settings for consignment
control, the system specifies whether the stock category is to be changed or remain the same.

Note
You cannot transfer vendor consignment goods that the system has converted to your own stock back to the consignment stock, as the transfer of
title has already taken place.

For more information about stock determination, see Goods Issues for Stock Transfers .
3. You can transfer vendor consignment goods across company codes.
If the consignment stock category is retained, no clearing is performed between the company codes because the goods remain the property of whoever
is managing the special stock.
For more information, see the Special Stock and Special Procurement Forms (MM-IM) component under Cross-Company Stock Transfer .
4. You can use an allocation table to control the purchase order and the stock transfer of vendor consignment goods.
For more information, see Allocation of Vendor Consignment Goods .
5. In consignment processing, you can display the stock currently being transferred.
For more information, see Displaying Consignment Stock in Transit .
6. You can delete all documents that the system creates in consignment processing.
7. You can return vendor consignment goods to the external or internal vendors.
For more information, see Returns of Vendor Consignment Goods .
8. You can perform a physical inventory for vendor consignment goods.
For more information, see the Inventory Management (MM-IM) component under Physical Inventory of Consignment Material .
9. You use POS systems to process the sale of vendor consignment goods. The report checks whether the stock is unique or whether stock determination
is required.
For more information, see Determining the Stock Situation After Sales .
10. A sale creates a legally binding contract with the external vendor.
For more information about settlement, see the Special Stock and Special Procurement Forms (MM-IM) component under Setting Consignment
Liabilities .

1.8.2 Goods Issues for Stock Transfers

Use
In SAP Retail consignment processing, when you post goods issues for stock transfers the system always performs stock determination and a price test.

Prerequisites
You have activated consignment processing in SAP Retail.
For more information, see the Implementation Guide (IMG) for Logistics – General under Retail Consignment Processing → Activate Retail Consignment
Processing
You have defined stock determination strategies for goods issues (delivery) and stock transfers for your own stock, and for consignment stock.
For more information, see the Implementation Guide for Logistics - General under Retail Consignment Processing → Define Strategies for Stock
Determination and Define Alternate Stock Determination Rules for Consignment Processing
You have set the Consignment Control indicator for preferential procurement of articles for consignment stock.

Features
When you post goods issues, the system performs stock determination. This identifies whether the system is posting goods from your own stock or from
vendor consignment stock.

You must ensure that the settings for stock determination rules and for the availability check are consistent. If the goods quantity determined by stock
determination and the availability check differs, this can create a great deal of unnecessary work in subsequent processes.
For more information about the availability check, see the Inventory Management and Physical Inventory (MM-IM) component under Availability Check .
The system performs a price test when a goods issue is made. This checks that the same price applies to the goods in both the supplying and the receiving
site. You can only perform a stock transfer if the price is the same.

Activities
When the system posts a goods receipt, it uses the information about the original vendor from the goods issue document. You must therefore always post the

PUBLIC Page 19 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 goods issue before the goods receipt in the receiving site.

Note the following general points:

You can transfer goods from consignment stock to a site's own stock at any time. However, you cannot transfer goods from your company’s own stock to
consignment stock.
It is not possible to make a partial delivery of a delivery item from both consignment stock and a company’s own stock. Nor can you deliver an item from the
consignment stock of several special stock managers.
You cannot make partial deliveries to different stock categories for one delivery. If the system has posted a goods issue from the consignment stock for a
delivery, it must also post the subsequent goods issue for this delivery from the consignment stock. This also applies if you have cancelled the first goods
issue.
See also:
Stock Determination

1.8.3 Displaying Consignment Stock in Transit

Use
You can use this function to display the valuated and the non-valuated stock (consignment stock in transit) that has been removed from the issuing site
because of a stock transport order but has not yet arrived in the receiving site.

Features

Selection
You can restrict the scope of the selection with settings for articles, the receiving site and the issuing site.
You can specify that only articles that go into the consignment stock of the receiving site are displayed.
The system displays all the purchase orders whose goods issue quantity is greater than the goods receipt quantity and that are neither flagged as
Delivery Completed nor Deleted .

Note
Set at least one of the indicators Stock Transport Order and Cross-Company Code Purchase Order , otherwise the system will not select any
purchase order document and will issue an error message.

You can also display deleted purchase orders or ones for which delivery has been completed.

Output
When you run a report, the system displays the purchase orders that correspond to your selection criteria in a list. You can display the following additional
information for the items in the list:
Warehouse stock of the article
Article data
Site master data for the receiving site

Activities
On the SAP Easy Access screen, choose Logistics Retailing Merchandise Logistics Inventory Management Environment Stock Stock in
Transit (Consignment) .

Note
You can use a Business Add-In (BAdI) to adapt the report functions to meet your requirements.
For more information, see the Implementation Guide (IMG) for Logistics - General under Retail Consignment Processing Enhancements Using
Business Add-Ins BAdI: Extension: Output Stock in Transit.

1.8.4 Determining the Stock Situation After Sales

Use
The stock situation changes with each goods movement. However, it would be impractical to update the stock situation for every goods movement as this
would reduce system performance considerably. As a result, in addition to the functions for standard processing, when sales are made at POS terminals, a
report for determining the stock situation is available as part of consignment processing.

Prerequisites

PUBLIC Page 20 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 You have activated consignment processing in SAP Retail.
For more information, see the Implementation Guide (IMG) for Logistics – General under Retail Consignment Processing Activate Retail
Consignment Processing .
You have defined strategies for stock determination for goods issues (sales) for your own stock and for consignment stock.
For more information, see the Implementation Guide (IMG) for Logistics - General under Retail Consignment Processing Define Strategies for
Stock Determination and Define Alternate Stock Determination Rules for Consignment Processing.
You have made general settings for the POS interface - inbound and have also set the consignment flag to control either receipt-specific or aggregated
sales.
For more information, see the Implementation Guide (IMG) for Logistics - General under Retail Consignment Processing POS Inbound Interface
.

Features
Before the report processes sales made at POS terminals, it checks whether the stock situation is ambiguous or unique.

Note
The report only takes into account the unrestricted-use stock for the articles in a site.

If the stock situation is unique , the system can post the goods without stock determination. If, for example, only consignment stock for a vendor
or only your own stock is present, the situation is unique.
If the stock situation is ambiguous , the system performs stock determination before posting the goods. If, for example, consignment stock
exists for several vendors, the stock situation is ambiguous .
To combine the components of structured articlesin the consignment stock that the system expanded during the goods receipt, the stock situation must
be unique.

Note
You can use a Business Add-In (BAdI) to adapt the report functions to your requirements.
For more information, see the Implementation Guide (IMG) for Logistics - General under Retail Consignment Processing Enhancements Using
Business Add-Ins BAdI: Extensions for Consignment Processing.

Activities
On the SAP Easy Access screen, choose Logistics Retailing Distributed Retailing POS Interface Environment Consignment Processing
Stock Situation.

Caution
Do not post any goods movements that take place after determination of the stock situation and before posting at the POS terminal. Otherwise the result
of the report will not reflect the current stock situation and errors could occur.

Selection
Select the sites for which you would like to run the report.
If you set the Include Previous Period indicator, the report determines the current stock situation and the stock situation for the previous period.

Note
The report only updates the stock situation of the previous period for articles whose stock in the current period is ambiguous.

To determine and update data you can use parallel processing, in other words, you can start separate processes for a number of sites.
To perform processes from other jobs on the server group as well, you can restrict the maximum number of parallel processes for the current
processing run.
Enter a server group for parallel processing.
Under Logging , make settings for the application log.

Output
The system issues the result of the report in the application log.
See also:
POS Interface Inbound

1.8.5 Allocation of Vendor Consignment Goods

Use
When you create purchase orders in consignment processing using an allocation table (externally/internally), you specify the stock category for which or to
which you would like to procure or transfer goods for a site, in addition to the usual settings.

Prerequisites

PUBLIC Page 21 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 You have activated consignment processing in SAP Retail.
For more information, see Customizing for Logistics – General under Retail Consignment Processing Activate Retail Consignment Processing .
In the item category enhancements for the allocation table, you have entered defaults for consignment processing.
For more information, see Customizing for Logistics - General under Retail Consignment Processing Allocation Table .
You have defined the stock transport order follow-on document for the item categories of the allocation table that you are using in consignment
processing.
For more information, see Customizing for Logistics - General under Merchandise Distribution Allocation Allocation Table Item Categories of
Allocation Table .
For preferential procurement of articles for consignment stock, you have set the Consignment Control flag.

Features
When using an allocation table to create purchase orders for each site, you can control consignment processing as follows:
Perform procurement according to the consignment control defined in the master data for the article
Procure goods for the consignment stock
Procure goods for your own stock
In two-level allocation tables, you can define separate procurement for each site. For example, the distribution center can order an article as a
consignment good, but when stock is transferred this article might be transferred to the consignment stock of one store but to another store’s own stock.
Procurement combinations that make good business sense from a distribution center and a store point of view

Distribution Center Procurement Store Procurement

Define in master data Define in master data

Define in master data Own stock

Own stock Own stock

Consignment stock Define in master data

Consignment stock Consignment stock

Consignment stock Own stock

Activities
When you create an allocation table, you can change the default settings for Item Categories that you have defined in Customizing:
In the detail view of the allocation item, choose the Control tab page and define the required procurement under Consignment Processing .

Note
Provided that the system has not generated any follow-on documents for external procurement, you can change consignment processing for items in the
allocation table.

See also:
Allocation

1.8.6 Returns of Vendor Consignment Goods

Use
You can return goods in consignment stock to both internal and external vendors. You can choose from one of the following options:
Return vendor consignment goods with direct reference to the purchase order
For more information, see the Inventory Management and Physical Inventory (MM-IM) component under Return Delivery .
Store return of consignment goods (to internal vendors)
You create a purchase order and set the returns indicator for the required item. For more information about consignment processing in SAP Retail, see
Vendor Consignment .
Vendor return of consignment goods (to internal vendors)
You create a purchase order with the item type Consignment and set the returns indicator for the required item.
You have the following options for further processing:
You create a delivery with reference to the purchase order and post a goods receipt for the item required. You can use all the functions in shipping
processing.
You post a goods receipt with reference to the purchase order.

Integration

Store returns
For returns, you can use a Business Add-In to adjust stock determination to meet your requirements.
For more information, see the Implementation Guide (IMG) for Logistics – General under Retail Consignment Processing Enhancements Using
Business Add-Ins BAdI: Enhancements for Consignment Processing .

PUBLIC Page 22 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Returns to vendor
The system takes account of returns items of consignment goods in the transactions for creating outbound deliveries (for example, VL10B ). The items
contain the special stock indicator Consignment and the Special Stock Partner (key of the vendor for whom the special stock is being carried). If you use
Warehouse Management, it takes account of this data when creating a transport order for picking.
Deliveries generated from returns items of consignment goods are assigned the delivery type Vendor Returns .
When creating a goods issue, the system copies the special stock type and the vendor from the delivery. The stock is booked out of the consignment stock
for the selected vendor.

Prerequisites
You can only use returns of consignment goods with shipment processing if you have configured your system as an SAP Retail system.

Store returns
You have set the Returns with Shipping Processing indicator in the purchasing data for the delivery site. The prerequisites under Consignment Processing in
SAP Retail also apply.

Returns to vendor
You have set the Returns with Shipping Processing indicator in the purchasing data for the delivery site.
You have activated the shipping connection for vendor returns of consignment goods in SAP ECC in Customizing for Logistics – General under
Retail Consignment Processing Activate Consignment Returns with Shipping Processing .

Features
Store returns
The following special features apply to the Return of Vendor Consignment Goods function in SAP Retail:
In the returns purchase order, you do not set the consignment indicator. Instead, stock determination determines the stock category from which the
system posts the goods:
You cannot return goods that the system transferred from the consignment stock to your own stock back to the consignment stock.
No stock split is allowed at purchase order item level: You cannot combine an item from consignment stock with your own stock. Nor can you
combine an item from consignment stock with different special stock partners.
You cannot make partial deliveries for returns to different stock categories. If the system has posted a goods issue for a return from consignment stock,
it must also post the subsequent goods issue for this return from the consignment stock. This also applies if you have cancelled the first goods issue.
You post the (negative) goods receipt before the (negative) goods issue. If the goods issue posting involves unique stock, the system determines the
vendor using stock determination.
Returns to vendor
You can process items from returns orders for consignment stock using shipping processing.
For more information, see Goods Movements Using Shipping .
See also:
Returns

1.9 Background Processing

This section lists all the key retail-specific reports in SAPRetail that are run in the background. The following questions are addressed:
What are the programs used for?
The programs 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 programs in a specific sequence.
What is the recommended procedure for running the programs?
This information tells you whether a report should be run periodically (for example, daily or monthly) or only in certain circumstances.
See also:
Introduction to the standard system : Reports
Computing Center Management System (BC-CCM): Background Processing
Parallel Processing of Background Jobs

1.9.1 Parallel Processing of Background Jobs

Use
For the SAP system to execute a program in the background, the program must be scheduled as a background job. For information on scheduling background
jobs, see Computing Center Management System (BC-CCM): Background Processing .
Many programs can also be divided up and run parallel in several jobs. This is an option particularly if several application servers are available. In many cases,
however, a program requires the results of the previous program or the programs try to access the same data and lock problems occur.
In order to avoid these programs, you can assign part of the data to each server. The data is then processed by programs running in parallel. The data is
processed more quickly and the subsequent program can start earlier.

PUBLIC Page 23 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Normally, data has to be distributed between the individual servers manually by creating variants for each program and each server. This is a laborious
process and is prone to errors. The distribution of data also soon becomes obsolete and needs to be updated regularly. An optimum runtime is only achieved if
the distribution is even so that each individual job has as an equal as possible runtime.
You can have the system distribute the data to the available servers using load distribution and external parallel processing. Parallel processing is set up
within process planning and replaces the time consuming parallel job scheduling using variants.
Subsequent process control is made considerably more simple and transparent by the removal of lots of scheduled jobs which need to be sychronized:
The manual scheduling of parallel jobs, which is prone to errors and the maintenance of lots of variants to distribute the worklist amongst the parallel
jobs is no longer required.
Changes to the worklist no longer lead to unequal runtimes for the individual jobs.
It is no longer necessary to check and update the distribution of data regularly.
From the outside, only one main process is visible. If necessary, a follow-on job starts when the main process has finished.

Prerequisites
In order to make the Customizing settings for these functions, it is important to have knowledge of the way in which the programs to be processed in parallel
work.
The timeout for the server group of the online processes must be set so that the jobs are not terminated if they exceed the time limits for the processes.

Procedure
1. For each relevant program, you generate a help program using transaction WLCPAR , which controls the parallel processing of this program externally
(see Load Distribution and External Parallel Processing ).
1. You schedule the program generated to be executed in parallel.
1. The system starts the programs to be processed in parallel externally using an asynchronous RFC in a separate parallel process. This process is an
online process on a server in a server group that can be set in advance.
1. Once all partial processes have finished, the main process also finishes, which then triggers the execution of any follow-on jobs that may be scheduled.

Result
Parallel processing reduces the time that the program takes to run. The shortest achievable runtime is roughly equal to the runtime on one server divided by
the number of servers available.
If not all the jobs have finished, the system triggers an optimum follow-on event, for which a follow-on job can wait before it starts.
Follow on jobs also always start if a job is terminated.

1.9.1.1 Load Distribution and External Parallel Processing

Use
External parallel processing guarantees the distribution of loads is always up-to-date and well-balanced.
Initial selection of the worklist
Estimation of the current workload
Uniform distribution amongst the required number of parallel jobs
This ensures the optimum use of the available computing capacity.

Integration
Each relevant program can be brought into operation step by step.
You can also use this function to run the programs that were developed in your customer project in parallel.

Prerequisites
The way in which the initial selection is carried out needs to be set in Customizing. It is not always possible to estimate the workload accurately. You can,
however, preselect data using a specific, self-developed function module.

Features
A help program, generated by the actual program, is scheduled to start the parallel jobs. You do not need to change or extend existing programs.
For each program to be run in parallel, the system creates a program, which determines the volume of data to be processed, distributes the data between
several jobs and starts parallel processing.
The generated program can be scheduled as a normal job with variants. The system generates a selection screen on which you can select the name of the
selection option via which the parallel processing is to be carried out (visible selection options only). There are also some other fields for the parallel
processing of jobs (number of parallel jobs, terminating event, tolerance limit for packet creation). In addition, all the variants of the basic program are also
copied invisibly so that the values are available for processing. These variants are defined as normal.

PUBLIC Page 24 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 There are two ways of selecting data:
Static data selection
In the program generated, a function module containing the values from the variant is called to select the data to be processed. This data is then distributed
among the parallel jobs of the program in a later step.
The function module and programs are assigned using a Customizing table so that for each new program, you just need to create the function module and
maintain an entry in this table.
The function modules have a standard interface. The crucial thing is the output table in which all the data to be processed is described with suitable keys and
values.
The disadvantage of the static method is that a new function module has to be adapted for each program to be processed in parallel. However, it is the only
way of parallel processing programs for which the dynamic method cannot be used.
Dynamic data selection
For dynamic creation, it has to be possible to determine the following values:
Tables to process
Result values, the number of which determines the volume of the workload
Key values, used for the initial selection
The result values do not necessarily have to match the key values.
The selection must be possible if the volume of data can only be determined using dependent tables.
The key values that resulted in the initial selection are then summarized in order to prevent a value waiting to be processed being named more than once in
multi-level selections. The number of duplicate names is, however, a measure of the workload to be processed for a value. A value could, for example, stand
for a document, for which the workload is determined by the number of document items.
The values are sorted according to their workload and assigned to the planned parallel jobs in descending order. This ensures an more even distribution
between the parallel processes.
For each parallel run the system sorts the key values in ascending order to fill the corresponding selection options.

Activities
Schedule background jobs for parallel processing using transaction WLCPAR .
For more information and examples, see the program documentation, which you can access from this transaction by pressing the i-button or Shift+F1 .

1.9.2 Background Processing: Retail Terminology

Use
Using short text replacement, you switch the user interface of your entire system to retail-specific terminology.

Activities
If you import corrections, for example, using support packages, the texts contained in these may overwrite retail-specific texts that have already been
converted.
Make sure that program RSBRAN03 is executed after each import of transports that contain texts. We recommend you run the report monthly.
To do so, start the program and enter the following data in the fields:
BRANCHE: ISR
LANG: <Your language>
NO_PROT: selected
DEL_OLD: selected
Leave all other fields blank.
Schedule the program to be executed in the background.
See also:
Retail Terminology

1.9.3 Background Processing: Site

This section contains information about key SAP Retail programs for sites.

1.9.3.1 Background Processing: Setting Central Block for Sites

Use
Program RWWLOCKD 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.

Activities

PUBLIC Page 25 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 We recommend you run the report daily.

1.9.4 Background Processing: Conditions

This section contains information about important Retail-specific programs in the area of conditions.

1.9.4.1 Background Processing: Generating Worklist Entries From

Change Pointers

Use
Program RMEBEIN4 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 program RMEBEIN1 . This determines all documents containing changed conditions. These documents are then
updated.
Worklist for Pricing
The worklist can be processed further by program RWVKP008 . 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 program RMEBEIN2.

Prerequisites
Program RMEBEIN4 does not need to be run if the system concerned has been configured to enable the Direct Generation of Worklist Entries for the
appropriate document categories.

Activities
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.

1.9.4.2 Background Processing: Adjusting Documents after

Condition Changes

Use
Worklists for purchasing documents and for Pricing created by program RMEBEIN4 can be processed together by program RMEBEIN2.

Prerequisites
Program RMEBEIN4 must be run before starting. This is not necessary if your system has been configured so that worklist entries are generated directly. This
program defines and collects conditions with all relevant changes.

Activities
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.

1.9.5 Background Processing: Assortment

This section contains information about key SAP Retail programs for assortments.

1.9.5.1 Background Processing: Value-Only Article Listing

Use
Program RWSORT17 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.

PUBLIC Page 26 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 If you wish, you can use this program to list all value-only articles in all assortment owners. This enables articles from any merchandise category to be sold at
the POS.

Activities
We recommend you run the report daily.
Program RWSORT17 is a prerequisite for POS outbound. For reasons of system performance, it should be scheduled to run before program RWSORT07 ("
Changes after Corrections ").

1.9.5.2 Background Processing: Change Assortments

Automatically After Master Data Change

Use
The following programs use change documents to identify changes to master data and then adjusts the assortment accordingly:
RWSORT07A changes listing conditions when assortment master data has been changed
RWSORT07B changes listing conditions when site master data has been changed
These reports can identify changes to the following types of master data:
Site/merchandise category
Sources of supply for articles
Site layout
Site classification
Supplying site

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

1.9.6 Background Processing: Assortment List

This section contains information about key SAP Retail programs for assortment lists.

1.9.6.1 Background Processing: Automatic Generation of

Assortment Lists

Use
If you choose to generate assortment lists automatically, you can have the system generate either a full version or a change version at set periods (in cycles).

Prerequisites
Before change versions and full versions of the assortment list can be generated in cycles, a site has to be initialized.
Programs relevant to background processing are:
RWDBBINI for initializing sites
Program RWDBBINI 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.

The program is only run when this data is transported to the stores for the first time.
If the data is transported again, use report RWDBBUPD.
RWDBBUPD for generating change and full versions of assortment lists regularly
Program RWDBBUPD sends the relevant data to the stores.

Assortment program RWSORT07 must run beforehand.

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

Activities
Select parallel processing in the Control check box. This is recommended if a large number of recipients (for example, stores) receive assortment lists. You
can enter the maximum number of parallel processes and a server group to be used.
Generate mixed versions means that you combine the last assortment list with assortment list changes. SAP recommends you generate mixed versions to

PUBLIC Page 27 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 improve performance.

Note
The cycle and the number of change versions which have to be created before creating full versions is defined in the assortment list type.

1.9.7 Background Processing: Markdown Planning

This section lists and briefly describes the important retail-specific programs in the Markdown Planning environment.

1.9.7.1 Background Processing: Markdown Price Phase Activation

Use
You can use report RWMFA200 to activate markdown price phases in the background. This is necessary if you have a large volume of data, due to
potentially long run times for price calculations and generation of conditions.
You can restrict which price phases are to be activated by selecting the sales organization, distribution channel, article, and/or starting date for the price
phases.

Integration
If you restrict the number of articles by entering selection parameters, then only these articles will be locked (that is, other users will not be able to access
them). This allows several users to activate pricing for different articles at the same time (parallel processing). Conversely, if you do not limit the number of
articles on the report's selection screen, then all articles will undergo price activation. The entire markdown plan all the articles in it will be locked for other
users.

1.9.7.2 Background Processing: Markdown Plan/Actual

Comparison

Use
Report RWMFA300 compares the planned and actual statistics for either an entire markdown plan or for specified articles within a markdown plan. Selection
criteria include: distribution chain, merchandise category, article and vendor for selection of the articles.
The report shows the current actual data of all stores within a given distribution chain. If no stores are assigned to the markdown plan (price activation at
distribution chain level), the system uses the actual data of all stores for the comparison. If there are price lists assigned to the distribution chain, the system
determines the appropriate sites for each article.
You can sort the list (for example, by sell-out rate). You can also mark certain articles and price phases within the report, then either start the price activation
report RWMFA200 or go from here directly to the Maintain Markdown Plan transaction for the marked articles and dates.

1.9.7.3 Background Processing: Price Calculation Test

Use
Report RWMFA210 allows you to test price calculations for markdown plans before activating them.

1.9.8 Background Processing: Promotion

This section contains information about key SAP Retail programs for promotions.

1.9.8.1 Background Processing: Generating Messages for

Promotion Announcements

Use
Use program RWNASTVP to generate messages for promotion announcements. This enables you to output messages in, for example, print form. The
program groups individual messages (according to articles and site) at site level.
For more information, see Promotion Announcements

Activities
We recommend you run the report on a daily basis.

1.9.8.2 Background Processing: Subsequent Processing for

PUBLIC Page 28 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.9.8.2 Background Processing: Subsequent Processing for
Promotions

Use
If you have large volumes of data, it is recommended that you do subsequent processing in the background. The following reports can be run in the
background:

For this function Use this report Which is equivalent to transaction

Promotion price activation RWAKT200 WAK16

Allocation RWAKT210 WAK17

Listing RWAKT220 WAK18

Announcements RWAKT230 WAK19

Supply source determination RWAKT240 WAK20

These reports works the same way online subsequent processing They use existing settings within the promotion (for example, prices, price activation types,
purchase price determination sequence, controls for generation of price conditions, allocation rules, announcement categories, and so on).

Activities
If you restrict the number of articles by entering selection parameters, then only these articles will be locked (that is, other users will not be able to access
them). This allows several users to do subsequent processing for different articles in the same promotion at the same time (parallel processing). Conversely, if
you do not limit the number of articles on the report's selection screen, then all articles will undergo subsequent processing. The entire promotion all the
articles in it will be locked for other users.

Note
You cannot run two different programs at the same time for the same article. However, you can set the programs up to run one after the other for an article.

1.9.8.2.1 Background Processing: Promotion Price Activation

Use
Program RWAKT200 is used to activate or deactivate promotion prices in background processing.

Note
The functions in program RWAKT200 are the same as transaction WAK5 .

Integration
In order to increase the speed of processing you can run the price activation or deactivation in several parallel processes.

Prerequisites
The promotion must have been created.
The promotion period must not yet have expired.

Features
You can run a price activation or deactivation for a chosen promotion.
Selection
You can limit the articles in a promotion for which you want to activate or deactivate prices.

Note
If you do not select any articles, all articles in the promotion are activated or deactivated.

You determine whether prices are activated or deactivated.

Output
The log from the sales price calculation is displayed or in the case of background processing it is printed.

PUBLIC Page 29 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 The calculation table produced can be printed in the case of non-parallel background calculation.
See also:
Subsequent Processing for Promotions

1.9.8.2.2 Background Processing: Promotion Allocation Table

Generation

Use
You can use program RWAKT210 to generate a promotion allocation table in background processing.

Note
The functions in program RWAKT210 are the same as transaction WAK5 .

Prerequisites
The promotion period must not yet have expired.
The promotion must have at least one site group assigned to it.

Features
You can generate an allocation table for a chosen promotion.
You can limit the articles in a promotion for which an allocation table is generated.

Note
If you do not select any articles an allocation table is generated for all articles in the promotion.

You can choose whether

the allocation table is generated with allocation rules,
the allocation table is generated with entered site quantities,
or a simulation of an allocation table is performed with the help of an allocation rule.
See also:
Subsequent Processing for Promotions

1.9.8.2.3 Background Processing: Promotion Listing

Use
You can use program RWAKT220 to list promotional articles in background processing.

Note
The functions in program RWAKT220 are the same as transaction WAK5 .

Prerequisites
The promotion period must not have expired and the promotion must be assigned to at least one site group.

Features
You can run a listing for a chosen promotion.
If you have assigned manual modules to the promotion you can limit the listing to individual modules.

Note
If you do not select any modules, the listing will run for all the modules in the promotion.

If you do not assign any manual modules to the promotion, you generate modules for the listing automatically. You can limit the promotional articles according
to article number, promotional theme or merchandise category. If you do not select any promotional articles, the listing will run for all items that have not yet
been listed.
See also:

PUBLIC Page 30 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Subsequent Processing for Promotions

1.9.8.2.4 Background Processing: Promotion Announcement

Use
You can use program RWAKT230 to generate a promotion announcement in background processing.

Note
The functions in program RWAKT230 are the same as transaction WAK5 .

Prerequisites
The promotion period must not yet have expired.
The promotion must have at least one site group assigned to it.

Features
You can generate an announcement for a chosen promotion.
You can limit the articles and/or sites in a promotion for which an announcement is created.

Note
If you do not enter any restrictions an announcement is made for the whole promotion.

You can choose what is run:

Message
Reminder
Completion of the notification
Confirmation
See also:
Subsequent Processing for Promotions

1.9.8.2.5 Background Processing: Promotion Supply Source

Determination

Use
You can use program RWAKT240 to generate a supply source determination for a promotion in background processing.

Note
The functions in program RWAKT240 are the same as transaction WAK5 .

Integration
Program RWAKT240 can be run in parallel externally if locks are set at article level.

Prerequisites
The promotion period must not yet have expired.
The promotion must have at least one site group assigned to it.

Features
You can run a supply source determination for a chosen promotion.
You can limit the articles in a promotion for which a supply source determination is run. If you do not select any articles, the supply source determination
will run for all the articles in the promotion.

Activities

PUBLIC Page 31 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 The program can only be run once for each promotion.
See also:
Subsequent Processing for Promotions

1.9.9 Background Processing: Pricing

This section contains information about key SAP Retail programs for pricing.

1.9.9.1 Background Processing: Pricing Worklist Based on

Changes to Factors Relevant to Pricing

Use
Report RWVKP008 determines all those price calculations that are based on changed conditions. 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 program RMEBEIN2 instead of generating a pricing worklist.

Prerequisites
Before you generate the pricing worklist, you must run program RMEBEIN4 . This finds and groups the changed conditions for further processing. This is not
necessary if the system concerned has been configured to enable the Direct Generation of Worklist Entries for document category 10 (pricing document).

Activities
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.

1.9.10 Background Processing: Requirements Planning

This section contains information about key SAP Retail programs for requirements planning.

1.9.10.1 Background Processing: Forecast per Period Indicator

Use
Program RMPROG00 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.

1.9.10.2 Background Processing: Total Planning per Site

Use
Program RMMRP000 provides 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.

Prerequisites
Program RMPROG00 must run prior to requirements planning.

Activities
We recommend you run the program daily.

1.9.11 Background Processing: Order Cancelation

This section lists and briefly describes all of the important retail-specific programs in the Order Cancelation application within the planning workbench.

1.9.11.1 Background Processing: Performing Order Cancelations

PUBLIC Page 32 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.9.11.1 Background Processing: Performing Order Cancelations

Use
Program RWPOB001 performs order cancelations. Due to the current delivery situation, the program processes purchase orders for which the delivery date
has passed but which have not yet been delivered or have only been partially delivered.

Activities
Execute as required.

1.9.12 Background Processing: Allocation

This section contains information about key SAP Retail programs for allocation.

1.9.12.1 Background Processing: Generating Messages for

Notifications

Use
Use program RWNASTV to generate messages for stock allocation notifications. This enables you to output messages in, for example, print form. The
program groups individual messages (according to articles and site) at site level.
For more information, see Creating Stock Allocation Notifications

Activities
We recommend you run this program or a daily basis.

1.9.12.2 Background Processing: Follow-On Documents for

Allocation Tables

Use
Use program RWWGENFB (Transaktion WA08 ) to generate follow-on documents for an allocation table. You can create all types of follow-on document
with this program (for example, purchase orders, deliveries or sales orders). For a description of how the process of follow-on document generation works, see
Allocation Table – Follow-On Document Generation .You have the following alternatives:
You can schedule follow-on document generation as a regular job. For more information, see Generating Follow-On Documents for Allocation Tables .
You can trigger follow-on document generation online. For more information, see Generating Follow-On Documents for Allocation Tables Online .

Prerequisites
Follow-on documents can only be generated if the allocation table data is complete.

Activities
If you schedule follow-on document generation as a regular job, it is recommendable to run it daily.

1.9.13 Background Processing: Ordering

This section contains information about important Retail-specific programs in the area of ordering.

1.9.13.1 Background Processing: Adjusting Purchasing

Documents after Condition Changes

Use
Program RMEBEIN1 determines purchasing documents (purchase orders and delivery schedules) containing changed conditions and updates these
documents.

PUBLIC Page 33 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Prerequisites
You must run program RMEBEIN4 beforehand. This determines and collects the conditions with the relevant changes.

Activities
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.
If you also want to update all price calculations in which changed conditions appear and put them in the pricing worklist, use program RMEBEIN2 to generate
the pricing worklist.

1.9.14 Background Processing: Seasonal Procurement

Use
This section contains information about the important retail-specific programs in the area of Seasonal Procurement.

1.9.14.1 Background Processing: Deletion of Completed Worklist

Items

Use
Program RWRF_PCTR_RCT_WL_DELETE determines the items that have been completed by a certain date or within a certain period and removes them
from the worklist for reactive order monitoring .

Recommendation
We recommend you schedule this report daily to keep the worklist clear and manageable.

Example
You want to delete all items completed between January 01 and June 30 from the worklist.

1.9.14.2 Background Processing: Remaining Quantities for Order

Items

Use
In order items, program RWRF_PCTR_REM_QTY checks whether the expected date has expired and which remaining quantities are still open.
The report processes the remaining quantity with the activity intended for the article, for example, it cancels or insists upon delivery of the remaining quantity
(see Activities Profile).

Recommendation
We recommend that you schedule this report to run each day, to keep the number of items in the system with unprocessed remaining quantities to a
minimum.

Integration
As long as the expected date (goods receipt: availability in distribution center) of an item has not been reached, the system writes the open quantities to the
remaining quantity table WRF_PRCT_REM_OTY .

Activities
Enter the parallelization parameters that the system should use for parallel processing. For example, under Package Size , enter a value if the system is to
process a specific number of items at once.

Example
The planned goods receipt date for an order item with a quantity of 100 is 07.01 (availability date in distribution center). On 06.28 you post the goods receipt
with a quantity of 80 and with an open remaining quantity of 20, whose delivery you insist upon. After the availability date has expired, the system informs the
vendor that you insist upon delivery of the remaining quantity.

1.9.15 Background Processing: Invoice Verification

PUBLIC Page 34 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.9.15 Background Processing: Invoice Verification
This section contains information about important Retail-specific programs in the area of invoice verification.

1.9.15.1 Background Processing: Immediate Invoice Verification

or Periodic Invoice Verification

Use
Program RMBABG00 executes invoice verification for invoices which have Immediate invoice verification or Periodic invoice verification set as the invoice
verification category.

Activities
If Immediate invoice verification is set, the program is started during opening hours (for example, 8:00 - 17:00).
If Periodic invoice verification is set, the program 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.

1.9.16 Background Processing: Subsequent (End-of-Period)

Settlement
This section contains information about key SAP Retail programs for subsequent settlement.

1.9.16.1 Background Processing: Settling Rebate Arrangements

Use
Use program RWMBON01 (vendor rebate arrangements) and RWMBON31 (customer rebate arrangements) to settle arrangements.

Prerequisites
Settlement periods (end of validity of condition records) must be defined in Customizing. The runtime depends on the volume of vendor business volume data,
purchase organization, purchasing groups, merchandise categories, tax code and settlement type.

Activities
You execute this report as and when required.

1.9.16.2 Background Processing: Extension of Periodic Rebate

Arrangements

Use
Programs RWMBON05 (vendor rebate arrangements) and RWMBON35 (customer rebate arrangements) extend the time period applicable for rebate
arrangements.

Activities
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.

1.9.16.3 Background Processing: Compilation of Statistics and

Retrospective Updating of Vendor Business Volume

Use
Programs RWMBON08 (vendor rebate arrangement) and RWMBON38 (customer rebate arrangement) can be used for the following:
Compilation of statistics

PUBLIC Page 35 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 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.
Retrospective Updating of Business Volume
You can retrospectively 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.

Activities
The programs should only be used in specific circumstances because they require considerable time and system resources. SAP recommends that you use
program RWMBO12 via function Process Worklist . When this is selected, a vendor and customer rebate arrangements are processed in the same way or,
if necessary, in parallel including the recompilation of amounts in a single operation.
You execute this report as and when required.
See also:
Retrospective Updating of Business Volume Data

1.9.17 Background Processing: Inventory Management

This section contains information about key SAP Retail programs for inventory management.

1.9.17.1 Background Processing: Revaluation at Retail

Use
Program RWVKU001 executes or prepares revaluation at retail for articles whose price at retail is changed during the selected time period.The following
cases can exist:
Inventory Management on a quantity and value basis
The program executes revaluation. Sales value change documents are generated with item status C (repriced). Retail revaluation documents are
generated with item status C (revaluated).
Inventory Management on a value-only basis
The program generates retail revaluation documents with item status A (to be counted). After documents are generated, you should generate a count
list, enter your count results in the central ERP system, and trigger the reevaluation. For more information, see Valuation: Automatic Revaluation When
Calculating New Sales Prices .

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

1.9.18 Background Processing: Logistics Execution

This section contains information about key SAP Retail programs for Logistics Execution.

1.9.18.1 Replenishment for Fixed Storage Bins

Use
There are two reports in the Warehouse Management System (WMS) that support picking:
Warehouse replenishment for fixed storage bins in WMS (RLLNACH1): This report shows which fixed storage bins in the warehouse currently have
insufficient stock. (The system does not do any planning based on the results.)
Replenishment planning for fixed storage bins (RLLNACH2): This report displays which fixed storage bins do not have enough stock to cover deliveries
planned for a specific period and for a specific shipping point. Planning is carried out especially for this.
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 second 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 create the appropriate transfer orders based on this transfer requirement, move
the stocks physically and confirm the transfer orders in the system. If you confirm the transfer orders, 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 (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).

1.9.19 Background Processing: Additionals

This section contains information about key SAP Retail programs for additionals.

1.9.19.1 Background Processing: Generating Additionals

PUBLIC Page 36 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.9.19.1 Background Processing: Generating Additionals
Purchase Orders

Use
When an event occurs and the Customizing settings specify that an additionals purchase order should be created for that event, the order data is entered in a
table. The program ADDI_ORDERS_CREATE generates purchase orders using the order data.
See also: Additionals: Generating Additionals Purchase Orders Automatically

Activities
We recommend you run the report on a daily basis.

1.9.19.2 Additionals: Change Analysis

Use
Changes to master data or movement data (for example, articles or purchase orders) lead to change pointers being updated. You can use change analysis to
analyze change pointers and if necessary, generate additionals IDocs at your head office.

Note
If additionals are to be generated in your store, information on the relevant changes is passed to the assortment list. In this case, you have to analyze
change pointers for the assortment list IDoc.

Features
Use program ADDI_ANALYSIS_OF_CHANGES (transaction WTCA ) to start change analysis. You can limit analysis to, for example, a particular time
period and selected sales price conditions.
In change analysis, change pointer analysis or a reduction derived from this is executed for logical message category WTADDI . Then, the changed sales
price conditions for the time period that you stated are found and analyzed.
For relevant changes, additionals IDocs are generated and transferred to the logical system TICKETS . You can incorporate individual fields to change
pointer analysis (see also: Distributing Master Data Using the Shared Master Data Tool (SMD) ).

Example
When you process a promotion, promotion sales prices are activated. Promotion sales prices are recognized in change analysis. An entry exists in the
additionals IDoc for each promotion sales price that is valid in the analyzed time period, if an additional with a suitable procedure for additionals is assigned to
the article in question.

1.9.20 Background Processing: Replenishment

This section contains information about key SAP Retail programs for replenishment.

1.9.20.1 Background Processing: Auto-Replenishment

Use
Program RWRPLPRO carries out replenishment planning. 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.

Prerequisites
Replenishment master data must be maintained for the required articles.

Activities
Execute as required.

1.9.20.2 Background Processing: Check Consistency of

PUBLIC Page 37 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.9.20.2 Background Processing: Check Consistency of
Replenishment Data

Use
Program RWRPLCHK checks the consistency of the replenishment data. The system checks for possible inconsistencies in the data and eliminates any that
it finds. It can also delete any replenishment data and requirement groups that are no longer required.

Activities
Execute as required.

1.9.21 Background Processing: Multi-Step Replenishment

This section lists and briefly describes all of the important retail-specific programs in the field of Replenishment Control with multi-step replenishment.

1.9.21.1 Background Processing: Automatic Multi-Step

Replenishment

Use
The programs
RWRPLPFE
RWRPLSRP
RWRPLVFB
perform replenishment planning. On the basis of the current stock situation, the system calculates the requirements of the sites and creates purchase
requisitions, purchase orders, sales orders or delivery schedules.

Prerequisites
Replenishment master data must be maintained for the required articles.

Activities
Perform this function as needed.

1.9.22 Background Processing: POS Interface

This section contains information about key SAP Retail programs for POS Interface.

1.9.22.1 Background Processing: Initializing Outbound Processing

Use
Program RWDPOSIN is used for the initial transport of master data to all stores using sales organization, distribution chain and site selection data.

Activities
The program is only run when this data is transported to the stores for the first time.
If the data is transported again, you use program RWDPOSUP.

1.9.22.2 Background Processing: Periodic Outbound Processing

for Stores

Use
Program RWDPOSUP executes POS outbound processing.
The quantity of data depends largely on the number of relevant master data changes.

PUBLIC Page 38 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Prerequisites
Assortment program RWSORT07 must be executed beforehand.

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

1.9.22.3 Background Processing: Repeating Terminated/Buffered

POS Inbound Processing

Use
You use program RWDAPP01 to restart processing of IDocs that have been buffered or for which inbound processing was terminated.

Activities
Terminated inbound processing
You can start processing IDocs at any time online or via job planning.
Buffered IDocs
If you decide to buffer IDocs, you must schedule program RWDAPP01 for the time when you want to process the data.
For further information see the program documentation.

1.9.22.4 Background Processing: Repeating Unsuccessful POS

Inbound Processing

Use
You use program RBDMANIN to reprocess specific IDoc data that was not processed in a previous attempt.

Activities
If overnight inbound processing was unsuccessful, and the fault has been repaired (for example, missing master data has been entered), you can plan program
RBDMANIN as a regular job or start it online.
For further information see the program documentation.

1.9.23 Background Processing: SAP Retail Store

This section contains information about key retail-specific programs for SAP Retail Store.

1.9.23.1 Background Processing: Linking to PDC Units SAP Retail

Store

Use
The following programs ensure a perfect connection of the PDC units in the stores for the RFC procedure:
Goods movement
General
R_SRS_PDC_GM_DATA_OUT (outbound processing of vendors and sites), scheduled daily
R_SRS_PDC_ASSORT_STRUCT_OUT (outbound processing of structure data for the assortment list. The outbound data is provided by the RFC
module SRS_PDC_GM_STRUCTURE) , scheduled initial and when changes are made to the assortment list profile
R_SRS_PDC_MDATA_OUT (outbound processing of the article data), scheduling depends on frequency of the article changes, if necessary, daily
Goods receipt
R_SRS_PDC_GR_CUSTOMIZING_OUT (output processing of Customizing data), scheduled daily
R_SRS_PDC_GR_DOCUMENT_OUT (output processing of reference documents), scheduled daily
R_SRS_PDC_GR_CREATE (automatic posting of partial goods receipts), scheduled daily
Goods movement
R_SRS_PDC_GM_CUST_OUT (outbound processing of business transactions), scheduled daily

PUBLIC Page 39 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Store Order
R_SRS_PDC_ASSORT_STRUCT_OUT (output procssing of structure data for the assortment list, the outbound data is provided by the RFC module
SRS_PDC_GM_STRUCTURE) , scheduled initial and when changes are made to the assortment list profile
R_SRS_PDC_SO_DISP_DATA_OUT (output processing of planning data. The outbound data is provided by the RFC module
SRS_PDC_SO_OUTBOUND), scheduled daily
Store physical inventory
R_SRS_PDC_PI_DELETE_EVENTS (reorganization of the PDC processes), scheduled monthly

Prerequisites
The prerequisites for using store order processing via PDC units are the same as those for using the store order in SAP Retail Store. In particular, in order to
be able to use programs R_SRS_PDC_ASSORT_STRUCT_OUT , R_SRS_PDC_SO_DISP_DATA_OUT and R_SRS_PDC_MDATA_OUT a complete or
merged version of the assortment list must exist.

Activities
The programs named can all be found in the menu under Logistics Retailing Distributed retailing SAP Retail Store – Administration SAP Retail
Store – PDC-Processing . SAP recommends that you schedule the programs as stated above

1.9.24 Background Processing: Information and Planning System

Program processing is not essential in the Information System. If certain functions (for example, periodic exception analysis) are used, or large quantities of
data are processed (for example, creation of new statistics), reports are used.
Requirements can be classified as follows:
Standard analyses
All standard analyses can be run as programs, for example as selection versions, in the case of evaluations that affect performance.
Periodic or event-oriented evaluations in the Early Warning System
These evaluations must be run as programs.
Flexible analyses
These evaluations can be run as programs. This must be defined first. The evaluation can be started online or planned as a job.
Compilation of statistics
You must create new statistics using a program.
Administrative activities
Tasks in this area, such as copying information structures, should be run as programs wherever possible.

PUBLIC Page 40 of 40
© 2014 SAP SE or an SAP affiliate company. All rights reserved.