IRT360
Headquarters -- Store Connections: POS Interface
IRT360 Headquarters -- Store Connections: POS Interface SAP AG 2001
System R/3 Release 4.6 C May 2001 50047604
C
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Copyright
Copyright 2001 SAP AG. 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 AG. The information contained herein may be changed without prior notice. All rights reserved.
SAP AG 2001
Trademarks: Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. ORACLE® is a registered trademark of ORACLE Corporation. INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.
C
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP Retail LO521
Level 2 IRT100
5 days
SAP Retail Process Overview
Pricing in Purchasing
Level 3 IRT310
3 days
SAP Retail Master Data IRT320 3 days SAP Retail Pricing and Promotions IRT330
3 days
SAP Retail Buying IRT340 3 days SAP Retail Supply Chain Management IRT350
3 days
SAP Retail BW/MAP IRT360 3 days SAP Retail Store Connection IRT370
2 days
SAP Retail Store SAP AG 2001
C
2 days
LO620 3 days Pricing in SD LO525 2 days Consumption-Based Forecast LO520 3 days Purchasing Details/Optimization LO530 5 days Basic Processes in Wareh.Management LO610 2 days Shipping LO611 3 days Transportation LO615 2 days Billing LO605 4 days Sales LO925 2 days Cross-Application Business Processes in SD and MM LO515 3 days Invoice Verification
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Prerequisites:
Recommended: Basic knowledge of Application Link Enabling is useful but not essential Basic knowledge of Electronic Data Interchange is useful Good knowledge of content of IRT310 Retail Master Data Good knowledge of content of IRT320 Pricing and Promotions Good knowledge of content of IRT330 Requirements Planning and Buying Good knowledge of content of IRT340 Supply Chain Management Essential: Good knowledge of content of IRT100 Retail Process Overview
SAP AG 1999
C
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Target Group
Project Team members responsible for setting up Store Communications SAP and partner consultants
SAP AG 1999
C
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Goals
This course will enable you to: Plan and implement communication between your headquarters and stores Set up the POS configuration for comm-unications Set up Sales Audit Reporting
SAP AG 1999
C
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Objectives
At the conclusion of this course, you will be able to: Configure your own inbound, outbound and Assortment List communications Explain how to transfer data to and from store systems, both point-of-sale (POS) and foreign merchandise management systems Monitor transmissions via the POS interface and handle any anomalies Configure the Sales Audit Reporting functionality of the POS interface
SAP AG 1999
C
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Contents
Preface Unit 1
Introduction
Unit 2
Technical Aspects of POS
Unit 3
Mapping Store Systems to SAP Retail
Unit 4
Simple POS Case Study
Unit 5
Merchandise Management System Case Study
Unit 6
Sales Audit Reporting
Unit 7
Performance Issues
Unit 8
Conclusion
Exercises Solutions Appendices
SAP AG 2001
C
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Unit: Introduction
Contents: Main Business Scenario Project Plan Communication Scenarios Overview of Business Information
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
1-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Objectives
At the end of this unit, you will be able to: Identify the areas that must be considered in planning communication between headquarters and stores Describe the transmission options supported by SAP Retail List the business information that can be transmitted via the SAP Retail POS interface
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
1-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Unit 1 Introduction Unit 2 Technical Aspects of POS
Unit 3 Mapping Store Systems to SAP Retail Unit 4 Simple POS System Case Study Unit 5 Merchandise Management System Case Study Unit 6 Sales Audit Reporting Unit 7 Performance Issues
Unit 8 Conclusion SAP AG 2001
© SAP AG
C
IRT360
1-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Main Business Scenario
R300-DC
10
15
13
R301-DC 14 11 20
Smart SmartRetailer, Retailer,Inc. Inc.
12
R316 R317
M
SAP AG 2001
You are a member of your company’s store communication integration team. You must create the appropriate configuration to communicate with your store point-of-sale systems. Other project teams already have configured the core business processes on SAP Retail. You have been requested to determine the optimum configuration to communicate with the stores. Configuration assumptions: Your company is a general merchant with stores in three western US states. There are two different point of sales systems currently operating in those stores. The small stores use a point of sales server to drive their registers, while the large format stores have a merchandise management system. Central replenishment will be run for all stores and it is company policy to run promotions for selected articles on weekends. Although you have a company card, you also have a policy of accepting other major credit cards as well as cash and checks.
© SAP AG
C
IRT360
1-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
• Number of different types of store systems
• Partners for converters
• Number of tax jurisdictions • Usage of current data • Converter/ Communications options
Evaluate
Consider
Project Plan
• Conversion requirements • Assortment List Size • Transmission frequency
• Simulate Outbound POS processes
• EDI • POS
Test
Configure
• ALE
• Data requirements
• Assortment List • Schedules
• Simulate Inbound POS processes • Stress Test
SAP AG 2001
Planning is the key to smooth implementation of your store communication systems. How much, what kind of data, and how often you send it are keys to system performance. How will you enable store integration? SAP does not provide the communication interface. - Will you contract with a certified partner? (SAP recommended solution.) Early contact with converter partners ensures communication availability when you are ready to test. - Will you create your own converter? How many different types of store systems are in use and where are they located? - Each store system type may require an unique POS profile and conversion category. - Each tax jurisdiction will require a unique POS profile. Where does the center of control reside in your company? - Determines the kinds of data located at headquarters and at the stores and consequently, which data you send down to the stores and receive back from the stores. Reporting requirements Your reporting requirements directly influence the message types you use to transport information.
© SAP AG
C
IRT360
1-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Transmission Options (1/2)
SAP Retail POS Interface Intermediate doc. (IDOC) Smart SmartRetailer, Retailer,Inc. Inc.
2
1 Conversion
Communication
Store system POS server
M
Store
SAP Retail remote
M
SAP AG 2001
Most in-store merchandise management systems can be linked to SAP Retail. Examples of systems include: A POS server with merchandise management functions. A store-based merchandise management system. In-store systems must be linked to SAP Retail in one of two ways. - via a certified converter/communication interface using the Retail POS Interface (SAP recommended Solution) - via your own converter/communication interface using EDI and SAP Intermediate Documents (IDocs). Some data can be downloaded to merchandise management systems directly using SAP’s standard ALE technology. (Beyond the scope of this course.) SAP Retail applications are also EDI enabled for standard message transmission. (cf., course CA210 EDI Interface.) The central SAP Retail system also can be accessed remotely via an in-store terminal and via the internet using Retail Store.
© SAP AG
C
IRT360
1-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Transmission Options (2/2)
SAP Retail Smart SmartRetailer, Retailer,Inc. Inc.
ALE/EDI
Intermediate doc. (IDOC)
SAP Retail System Conversion M
Store
M
POS server
SAP AG 2001
SAP Retail also can be set up in distributed mode with multiple application servers in various stores. If using a distributed model, you must resolve the following questions: - In which sites are application servers to be installed? - Which applications are to run on which systems? - Which master data and transaction data is to be interchanged? - Which control data is to be made available to the central SAP Retail system? Standard R/3 Application Link Enabling (ALE) and reference models facilitate creating a distribution model. The standard SAP Application Link Enabling course, CA910 provides information on distribution modeling.
© SAP AG
C
IRT360
1-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Outbound
Exchange rates
Article master data
Article sales prices
Taxes
POS Outbound
Merchandise categories
SAP AG 2001
Customer data
Inventory data
EAN/UPC references
Types of business information that SAP Retail sends through the POS outbound interface to store systems. Article master data Article sales prices EAN/UPC assignments Customer data Exchange rates Products Set Assignments Taxes Merchandise Category Master Label data Physical Inventory Assortment Lists Promotions
© SAP AG
C
IRT360
1-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inbound
Financial Transactions
Article Master Data EAN/UPC References
Sales Data
Inventory
POS Inbound
Tender Type Data
Customer Data
Cashier Data
SAP AG 2001
Types of business information that SAP Retail can receive through the POS inbound interface from store systems. Sales Data (receipt-based and aggregated) Cashier data Payment types Financial Transactions External Messages Inventory (Store Orders, Goods movement and Physical count data) Article data changes Pricing conditions Customer data EAN/UPC assignments
© SAP AG
C
IRT360
1-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Scenarios
Sales Master Data
rice, l e, P C c i t r A /UP EAN
Store M
s$ Sale
M
Article, Price, EAN/UPC, Customer, Taxes
Merchandise Management
Simple POS System Store M
IDES IDESSmart SmartRetailer RetailerInc. Inc.
Human Resources
Sales $ and Q, Articles, Customers
Article, Price, EAN/UPC, Customer, Vendors,...
M
Intelligent POS System Store M
M
Purchasing Finance
Sales $ and Q, Articles, Customers, Inventory count...
Merchandise Management System
SAP AG 2001
How you do business plus store system capabilities determines which: - types of Outbound SAP Retail data you will send - types of Inbound SAP Retail data you will receive
© SAP AG
C
IRT360
1-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Summary
Implementing Headquarter-Store communication is an iterative process with many variables -location of stores, types of store systems, and choice of converter are among those that must be considered early in an implementation. The types and amounts of business information sent to and received from stores depends on the capabilities of the store systems.
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
1-11
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
© SAP AG
C
IRT360
2-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
© SAP AG
C
IRT360
2-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
© SAP AG
C
IRT360
2-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Some definitions: Application Link Enabling (ALE) - is a technology developed by SAP. It performs the distribution services that interact with the SAP applications, processing IDocs and passing them to the communications software. Electronic Data Interchange (EDI) - is an IEEE standard for data transfer between disparate systems. SAP can convert IDocs into an EDI compliant format for data export. Intermediate Document (IDoc) - is the standard SAP structure used to communicate business data between systems. IDocs can be exchanged freely between R/3 systems, but generally must be converted to a standard format (such as EDI) for export to other systems. Point Of Sale (POS) - as a term, is used in two ways: First, it is used as a shorthand reference for the POS Interface, the SAP Retail module that determines the recipient and creates IDocs for outbound POS transmission and creates the inbound IDoc from the communication IDoc delivered by the converter system. Secondly, it is also a generic shorthand reference for all store systems (point-of-sale or merchandise management systems).
© SAP AG
C
IRT360
2-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
ALE technology is used in conjunction with the POS Interface and the EDI Interface to automatically prepare master data changes to be sent to store systems. ALE controls the generation of change pointers which POS Outbound uses to create multiple message types. Outbound data flow is handled in the following manner: 1. Users maintain master data and when they save it, database tables are updated, a change document is created and a change pointer is also created. 2. Nightly, when the outbound and/or Assortment List report is run, the change documents and change pointers are analyzed and changed data from the database tables is used to build master IDocs. Note: The POS interface assigns the site and prepares a site specific IDoc for each site affected by the master IDoc. 3. The IDoc is passed to the EDI interface port designated in the Outbound profile, and when one site IDocs are completed, the trigger file is created and the system prepares the next site’s data. 4. The converter checks the trigger file (status) to identify the location of the IDoc files and the IDoc files are copied to the converter. 5. When the converter has received the file, it sends a status message and it deletes the IDoc file at the EDI interface. 6. The converter handles all communication with the store. If a store cannot be reached, the converter sends an error message back to R/3.
© SAP AG
C
IRT360
2-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP recommends that the inbound message data flow be organized as shown. The POS converter communicates with the POS system(s) via a WAN (Wide Area Network) and with the R/3 system via a LAN (Local Area Network). Inbound data flow should then proceed along the following steps: The POS converter receives data from a store system, converts them to the IDoc format, and stores the resulting IDocs in a file (one per store and IDoc type) on the POS converter server. 1. The IDoc file is then copied, via remote copy, to the R/3 application server. 2. The IDoc file is deleted from the POS converter server. 3. Subsequently, the POS converter performs a remote function call (RFC) of the C-program ‘startrfc’ on the R/3 application server, with the location of the IDoc file on this server passed as one of the parameters. This C-program triggers the concluding processing of the inbound data: 4. The ABAP report edi_data_incoming is started automatically and reads the IDoc file on the R/3 application server. The IDoc data are saved in the R/3 database in tables EDIDC, EDID4 and EDIDS. 5. The IDoc file on the R/3 application server is deleted. 6. Finally, for each newly arrived IDoc, the system determines the corresponding EDI partner profile for the message type to post the information to the appropriate application. This can happen either directly by a function module, or indirectly (via workflow or process technology).
© SAP AG
C
IRT360
2-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The POS Interface provides an inbound data simulation tool to facilitate testing the customizing settings of the inbound messages, as well as underlying functions (e.g. pricing procedures, G/L account determination). Technically, the simulation replaces steps 1 - 5 of the live scenario by generating an inbound IDoc directly on the R/3 database, and then posting the data (step 6). Note: The (data) fields in a given IDoc type used in inbound simulation do not generally match the fields on the corresponding simulation screen 1-to-1. Some IDoc fields cannot be filled through simulation at all (e.g., because they are no longer used), some others are calculated from several fields on the corresponding simulation screen. Conversely, some simulation screens contain fields that may, in some circumstances, be necessary to send, but are currently not contained in the corresponding IDoc type. Warning: The POS simulation tool generates business data (e.g., sales, goods movements, financial transactions, ...) that the system does not distinguish from genuine data. Hence, POS inbound simulation should NOT be used in a productive system for testing!
© SAP AG
C
IRT360
2-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP Retail uses profiles, which are collections of standard information that are needed repeatedly in similar combinations for maintenance of different objects. They act as data entry tools and simplify the management of data. One profile may be used by many sites, but each site will have only one outbound, inbound and assortment list profile. All the profiles associated with store communication are linked through each store’s Site Master record.
© SAP AG
C
IRT360
2-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The Customer number associated with each site links to the partner number in the EDI Partner Profile. The EDI Partner Profile is created to provide message handling information that is required by SAP Retail to send or receive messages. The EDI Partner Profile is unique to each site.
© SAP AG
C
IRT360
2-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Although it is not a profile, ALE Activate Messages function is the location where message types are “turned on.” The ALE function itself must be turned on by activating the “Activate Generally” option in the IMG before the active messages will work. Messages are either on or off. So, if one store requires a particular message type, that message type is created for all stores. The link to the Site Master is through the message types assigned to a partner number in the EDI Partner Profile. If a message type is activated in ALE and not activated in the site’s EDI Partner Profile, the message type will not be transmitted.
© SAP AG
C
IRT360
2-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The POS Outbound profile is the repository of outbound specific information. One POS Outbound profile can be used for many sites. The Outbound Profile is used in conjunction with the EDI Partner Profile and the ALE Activate message types to control the flow of message types to the stores. Once the POS Outbound profile is created, its name is entered into the store Site Master record which creates the link between the store and the outbound processing information.
© SAP AG
C
IRT360
2-11
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The POS Inbound profile is the repository of inbound specific information. One POS Inbound profile can be used for many sites. The Inbound Profile is used in conjunction with the EDI Partner Profile to control the flow of message types to SAP Retail. Once the POS Inbound profile is created, its name is entered into the store Site Master record which creates the link between the store and the inbound processing information. Specific handling of inbound data requires several different types of information, depending upon the particular inbound messages you use. These details are described later in the course.
© SAP AG
C
IRT360
2-12
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The Assortment List profile is a particular POS Outbound IDoc type. It relies on a separate profile for communications to the stores. The Assortment List is covered in more detail in a subsequent unit. The Assortment List profile and EDI Partner Profile are linked through the message type which must be activated in the EDI Partner Profile. The Assortment List profile links to the store though the assortment list profile name and through the listing type that is also recorded in the Site Master record.
© SAP AG
C
IRT360
2-13
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
© SAP AG
C
IRT360
2-14
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
IDocs are an SAP tool for communicating business data between an SAP R/3 system and a partner system. Just as different business documents may have different data structures, there are different IDoc types. SAP R/3 provides in excess of 100 such IDoc types to cover most standard communication needs, and these are processed by the system’s EDI Interface. SAP Retail provides an additional 25 IDoc types used specifically to communicate between an SAP Retail system and a store system through the POS Interface. In addition to the basic IDoc types, the system provides tools to create customer-specific extensions of existing IDoc types. This is done by including additional data fields required for in-/outbound communication in data segments (usually called E1WXX01) that are specifically reserved for customer enhancements. User exits (i.e., ABAP functions of an assigned name and source code to be defined by the customer, that are called at a particular point within an application’s ABAP source code) are provided to fill these additional fields on outbound communication, and to read and process data transmitted via these fields on inbound communication.
© SAP AG
C
IRT360
2-15
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Each IDoc (inbound or outbound) consists of the following three components: - Exactly one control record exists per IDoc containing partner information regarding the sender, the receiver, and the message type. These are stored in database table EDIDC. - One or several data records made up of a hierarchical segment structure containing the actual business data. These data may represent business documents such as store orders, assortment lists, etc., or single line items, as in the case of aggregated sales or stock counts. For inbound IDocs, each group of data segments that is processed together (e.g. all segments representing a particular store order) in the POS Interface, is referred to as an IDoc range. Each such IDoc range has a POS status, that reflects the result of its inbound processing, and determines the further processing to which the IDoc range may be subject. IDoc data records are stored in database table EDID4. - One or several (EDI) status records that document the life cycle of the entire IDoc. These are stored in EDIDS. All control records, data records and status records contain a numerical key (IDoc number) that identifies the IDoc client wide. It is by this key (and the client number) that all records belonging to one IDoc are linked together on the system’s database. Which data can be included in a particular IDoc, possible groupings of such data to segments (e.g. PO header, PO item, ...), and the hierarchical order between these segments, are defined by the IDoc type. The structure of all IDoc types is documented in the system and can be retrieved online, as well as exported, e.g., as a html-file, or as a C-header file.
© SAP AG
C
IRT360
2-16
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Each individual IDoc is characterized by exactly one IDoc type and exactly one (logical) message type, both of which are stored in its control record. While the IDoc type describes the (syntactical) structure and hierarchical order of the data transmitted in an associated IDoc (e.g., which header segments, which subordinate segments, which fields in which segment, length and data type of fields, ...), the message type describes the semantics of the data transmitted in the IDoc, i.e., how the recipient should interpret the IDoc data. Consequently, the message type enables the system to distinguish business documents that, from the data structure point of view, are identical. Example: The (standard) IDoc type ORDERS01 may be used to transmit both purchase orders (message type ORDERS), purchase order confirmations (message type ORDRSP), as well as notifications on change of purchase order (message type ORDCHG). Thus, some IDoc types may be combined with several message types. The converse is also true, hence the relation between IDoc types and message types is many to many.
© SAP AG
C
IRT360
2-17
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Details of the data record structure associated with any particular IDoc type can be displayed in the form of a structural tree. This tree provides a drill-down functionality to look at the definition of segments, and eventually the definition of individual data fields, at any level of dis/aggregation. The example shown represents part of the data record structure of IDoc type WP_PLU02, which is the ‘carrier’ for article master data, both for outbound and inbound. Each IDoc of this type consists, at the top level, of 1 to 9999999 mandatory ID segments E1WPA01. Each of these segments may contain some application data (segment fields), plus further, optional segments E1WPA02, E1WPA03 , E1WPA04, E1WPA07, E1WPA08, E1WPA09, E1WXX01 (for customer enhancements). While the segment E1WPA02 (data) may occur at most once within a particular E1WPA01-segment, the others are allowed up to 99 occurrences. Each of the subsegments of E1WPA01 contains their respective data (texts, material conditions, condition values, ...), with E1WPA04 and E1WPA09 each containing a further subsegment.
© SAP AG
C
IRT360
2-18
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
A drill-down on a folder representing data fields of a particular segment lists all fields assigned to that folder, as well as for each of these fields, a short description, its internal length (in bytes), the corresponding data type, and a brief definition of the field.
© SAP AG
C
IRT360
2-19
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The prior two slides show how the IDoc is described in the system. This slide depicts how the data is structured in an IDoc when it is transferred to or from the converter. How the system structures an IDoc can be seen using IDoc Type (parser).
© SAP AG
C
IRT360
2-20
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The EDI status of an (entire) IDoc (inbound or outbound) primarily documents the passing of the IDoc through ALE/EDI during transmission, but may also be updated by the subsequent inbound processing of the IDoc that reports back to the EDI status. Furthermore, the EDI status of an IDoc may also change as a result of user intervention, e.g., by editing a faulty inbound IDoc in the POS Monitor before resubmitting it for processing. EDI status < 50 apply to outbound messages, those > 50 to inbound messages. In addition to a global EDI status, each range of an inbound IDoc, that has successfully passed through ALE/EDI, is assigned a POS status by the inbound processing of the range in question. The POS status reflects the state reached by an IDoc range during inbound processing, i.e., whether the range has been successfully posted by the corresponding application, or at what stage of the inbound processing which error was encountered. The POS status of an IDoc range may also be changed manually in the POS Monitor.
© SAP AG
C
IRT360
2-21
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
© SAP AG
C
IRT360
2-22
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
EDI Port identifies the address of the port and its type. The name of this port must be SAP. The port type for POS communications is File. Other types provided are: Transactional RFC- for use with distributed ALE. CPI-C - for use in communicating with R/2 systems Internet - for use with internet communications. Your System Administrator should create a main POS directory at the operating system level with three sub directories for outbound, inbound and status to make the management of these files easier. Once your directories are created, you identify them for ALE and EDI when you define the port and type. The directories must be created on all R/3 message servers that are used to communicate with a converter.
© SAP AG
C
IRT360
2-23
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Control file customizing is not required for transmission via POS interface. Suggested values for outbound file: Directory
/enter the directory path for POS outbound/
Outbound file Function module
EDI_PATH_CREATE_POS_UNIX_DOS
The function module address plus the blank outbound file field combine to allow for the IDoc file name to be dynamically created each time an outbound process is run.(SAP recommends that you use this module.) Although, on inbound communication, the location of the IDoc file on the SAP application server is passed by the POS converter to the C-function ‘startrfc’, ALE/-EDI requires that a recipient port (of type ‘File’) be defined in ALE-customizing of the SAP R/3 system. The name of this port must be SAP and is specified in the control record of each inbound POS IDoc. Status file for ease of handling should be a separate subdirectory of the POS directory: Suggested values: Directory
/ enter the directory path /
Status file
STAT
Function module
You enter the EDI Port name in the EDI Partner Profile, Outbound section in the Receiver port field for the system to place outbound and status files in the proper location.
© SAP AG
C
IRT360
2-24
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Each store must have an EDI Partner Profile before data can be transmitted either outbound to the store or inbound from the store. The information on the primary screen carries over to both the inbound and outbound sections of the EDI Partner Profile. You define the following information for each store: Partner number -- Use the Customer number of the store Partner type -- For POS use ‘KU’ which identifies the partner as a customer Partner class -- If you have created a class of stores Partner status -- Must be active Telephony -- Only used in standard EDI with external customers or vendors Receiver of Notifications -- The following fields are filled with default information if Workflow has been established in PD-Org. Typ(e) -- Identifies the kind of name to expect in the ID field. Options include, Workcenter, Job, Organization unit, Person, Position, User Lang(uage) -- In which a message is to be issued ID -- Must correspond with Type field described above. For example, if the type is Work Center the ID must be the name of the work center
© SAP AG
C
IRT360
2-25
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
You must list each message type that you will send to the store in the Outbound section of the EDI Partner Profile. Outbound options - Establishes how you wish communication to take place. - Receiver port -- Enter the name of the port already defined in the EDI Port profile for Outbound IDocs. - Transfer IDoc immed. or Collect IDocs-- Use Collect IDocs for all Outbound message types. - Start subsystem or Do not start subsystem-- Not necessary. IDoc type - Correlates to the function module that is called to process communication. - Basic IDoc type -- Provides necessary information to perform communications with no additional data. - Extension-- Customer enhancement to basic IDocs - Syntax check flag-- If the field is selected, the system stops if a syntax error is encountered. Leave blank to have the IDoc posted with a flag for a syntax error. - Seg. Release in IDoc type-- Optional, release version code. Receiver for notification--specifies the ‘agent’ the system should notify in case of errors during inbound processing. - EDI settings -- Communication settings. - EDI Standard-- SAP supports E, EDIFACT and X, ANSIX12 - Message type-- Optional, the EDIFACT or ANSIX12 message type - Version--Optional, enter the version if you are using the prior field.
© SAP AG
C
IRT360
2-26
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
You must customize the following parameters for each message type that a store is allowed to send to the central SAP Retail system in the inbound section of the store’s EDI partner profile: Test flag -- Must be set to use the simulation tool to send an IDoc. Leave blank for a productive message. Process code -- Only parameter (apart from client number) that determines, via database table TEDE2, which function module is called to process the inbound data. Syntax check flag -- If the field is selected, the system stops when a syntax error is encountered. Leave blank to have the IDoc posted with a flag for a syntax error. Processing mode -- Determines, whether incoming IDocs are to be processed immediately, or later in background. Receiver for notification -- Specifies the ‘agent’ the system should notify in case of errors during inbound processing. Upon receipt of an IDoc from a store, the POS Interface uses the EDI partner profile, along with the POS inbound profile assigned to it, which controls the inbound processing of the IDoc, through the seven keys partner number, partner type, message type, partner function, message code, message function and test, as read off the IDoc’s control record.
© SAP AG
C
IRT360
2-27
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
© SAP AG
C
IRT360
2-28
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The POS Monitor, together with the POS Inbound Processing Unit and POS Outbound Processing Unit, make up the POS Interface. It is through this interface that an SAP Retail system is able to communicate, through a POS Converter, with a store based POS system. The main tasks of the POS Monitor are to document both inbound and outbound communication between the SAP Retail system and partner systems, and to provide tools to view and edit this information. Only POS IDoc types can be displayed in the POS Monitor, because the distinction between POS IDoc types and the remaining ones is hardcoded in the system! The POS Monitor provides functions to obtain either a top-level, or a detailed view of a selected portion of both inbound and outbound communication in the SAP Retail system. It may, for instance, be used to inform the user which assortment lists were downloaded to a store or range of stores during the last two weeks, or which inbound IDocs were rejected by the system. In addition to displaying information on past communication activity in the system, the POS Monitor also allows the user to edit IDocs or to change the POS status of ranges of an inbound IDoc.
© SAP AG
C
IRT360
2-29
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
© SAP AG
C
IRT360
2-30
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
According to the selection criteria specified, the POS Monitor displays the matching communication items, sorted into categories that are arranged hierarchically. At top level, there are four categories: Outbound Processing, Outbound message communication, Partner system messages, Inbound processing. All except the ‘Partner system messages’-category are divided into two subcategories: one for items that were successfully processed, and another one for those not fully processed.
© SAP AG
C
IRT360
2-31
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The main ‘Outbound processing’ features of the POS Monitor are: Starting at any (non-terminal) node of the POS Monitor tree, the user can drill down to display the immediate descendants of that node, down to individual application in the ‘Outbound’ or the ‘Outbound message communication’ part of the POS Monitor tree. Outbound processing contains the result of the system preparing an outbound file. Outbound message communication contains the result of the outbound file being processed by the Converter. For each application, its type (POS = download of POS data, SL = download of assortment lists), the date and time when it was processed by the POS Outbound Processing Unit, and a status text are displayed in the POS Monitor. The user may then display the outbound log for any of the application items (e.g. in case of a problem, color-coded in red) to see the IDoc that were posted, the format and transmission status, as well as detailed messages that were recorded during outbound processing of the item. In case of errors (e.g. missing data needed in an assortment list), correct the problem and then restart outbound processing.
© SAP AG
C
IRT360
2-32
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The main ‘Inbound processing’ features of the POS Monitor are: Starting at any (non-terminal) node of the POS Monitor tree, you can drill down to display the immediate descendants of that node, down to individual IDocs and beyond. For each such IDoc, its unique numeric key, its creation date, and a status are displayed in the POS Monitor. The status displayed is the EDI status of the entire IDoc if a problem was encountered during EDI transmission. If EDI transmission was successful, the status displayed is the POS status of an IDoc range within that IDoc. You may select to edit a single IDoc by double-clicking on the IDoc number, the word IDoc, or the date. If you select “To be processed” and Process you can activate the Sales Audit Editor with a list of IDocs, limited by your original selection, that you may edit individually or in groups. If you select the IDoc status, you may (by a single click on the POS status) change the POS status of that IDoc range, e.g. by rejecting it, resubmitting it for processing, or triggering its immediate processing. A further drill-down on an individual IDoc displays any follow-on documents (e.g. billing documents, article documents) created during inbound processing, if successful, or errors or workitems that were generated as a consequence of problems encountered during inbound processing.
© SAP AG
C
IRT360
2-33
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
The Sales Audit Editor screen provides the facility to edit IDocs in the Monitor and to reprocess them as soon as they are corrected. Individual IDocs can be edited and all IDocs containing a similar error can be processed using the Mass change function.
© SAP AG
C
IRT360
2-34
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Additionally, the POS monitor provides a completeness check for inbound communication. This check compiles: a statistic of the number of IDocs received within each message type , as well as the number of those IDocs that were processed with, or without errors a summary of the total number of IDocs received, the number of message types within which inbound communication has occurred, and the number of stores from which inbound communication was complete (i.e., from which at least one IDoc was received within each message type for which inbound communication is defined according to a store's EDI partner profile).
© SAP AG
C
IRT360
2-35
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
© SAP AG
C
IRT360
2-36
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Unit: Technical Aspects of POS Topic: IDoc Documentation At the conclusion of this exercise, you will be able to: • Retrieve technical information about the structure of basic IDoc types from the system As a member of the implementation team, you must determine which POS IDoc type would be best to use to send the stores article data. You know the large format stores can receive the Assortment List IDoc, but you are not so sure about the point of sale servers in the smaller format stores. To start your investigation, you want to evaluate the Article message and IDoc type. 1-1
Investigate an IDoc structure by using the IDoc documentation in the system. 1-1-1 If you were to use WP_PLU02 for your smaller stores, which segment would carry the internal article number? 1-1-2 In what segment is the main EAN/UPC code carried? Is there a segment for another EAN/UPC in this IDoc.
1-2
Now, check an inbound message type. Select WPUFIB01 to determine if it can carry the type of financial transaction data you want to collect from your stores. 1-2-1 You require a transaction code to identify your financial transactions, is there a segment/field identified for transaction types? If there is, which one and is it a required segment? 1-2-2 Is there any required segment in WPUFIB01? What data fields does that segment carry? 1-2-3 If this message does not carry all that you require, is there a way you can attach additional information? If yes, how.
© SAP AG
C
IRT360
2-37
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Technical Aspects of POS Exercises Unit: Technical Aspects of POS Topic: EDI Ports and Partner Profiles At the conclusion of this exercise, you will be able to: • Create an EDI partner port • Create an EDI partner profile with an outbound and an inbound message. You are ready to begin testing, but before any messages can be sent or received there is some System customizing you must do. The first step to POS testing is customizing the communications area. Important note: The R/3 locking mechanism is switched off for courses doing Customizing therefore, it is necessary for you to check that your settings have been saved. Use DISPLAY after you have saved your changes to confirm that they are recorded. 2-1
The technical members must have already identified your logical system. Before beginning with the communications area, please check that the system is identified. 2-1-1 Where do you check if the logical system is identified? 2-1-2 What is the name of the logical system you are using today?
2-2
Either you or the technical members of your team must define a port for the interface. While you are preparing the communications area, you should check if they have defined one that you can use. 2-2-1 Under which Port type will you find the port definition for the POS interface?
© SAP AG
C
IRT360
2-38
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
2-2-2 Use the copy function to create a new port and name it T8##. Remember ## is the number you are assigned. The name of the directory (created by the system administrator) where your files will reside is: 2-2-3 What is the name of the Port you copied to create your new port?
2-3
Now you want to create an EDI Partner Profile for your test site T8##. Remember ## is the group number you have been assigned. 2-3-1 While you are testing you will probably test one message type at a time, so at this point just add one message type to your outbound Partner Profile. Remember to make the profile active. To send article data to your store, which message type will you use? 2-3-2 Create a record for that message type. What IDoc type will you use with that message type? 2-3-3 What other information must you enter for this message type to work? 2-3-4 If you had completed your testing phase and were going to create Partner Profiles for a lot of stores, how would you go about doing that?
2-4
You probably will want to send article information from the store back to headquarters. So create an inbound partner profile for your article information that you can test with the POS Simulation tool. 2-4-1 What message type will you use for the inbound article data? 2-4-2 Must you set the test box for the message type? 2-4-3 What do you require for inbound message types to handle follow-on functions? 2-4-4 Do you have to assign a Port to the Inbound Profile? Why or why not?
© SAP AG
C
IRT360
2-39
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Unit: Technical Aspects of POS Topic: IDoc Documentation 1-1
To use the IDoc documentation in the system to evaluate IDoc type WP_PLU02. The menu path to display the structure of an IDoc type is: Tools → Business Communication, IDoc → IDoc Basis → Documentation double-click IDoc types enter WP_PLU02 in the field ObjectName and, leaving all other selection criteria as defaulted, press button Display Tree (F8).On the subsequent screen, select E1WPA01 and press Expand Subtree. 1-1-1 The segment that carries the internal article number is field ARTIKELNR in segment E1WPA01. 1-1-2 The main EAN/UPC is also carried in segment E1WPA01. It is carried in field HAUPTEAN. No other segment in this IDoc type carries fields for additional EAN/UPC numbers.
1-2
Back out to the IDoc selection screen. Enter WPUFIB01 in the field ObjectName and, leaving all other selection criteria as defaulted, press button Display Tree (F8) 1-2-1 Expand the structure tree and you find that IDoc type WPUFIB01 is made up of three segments. The first is E1WPF01 with the field VORGANGART that carries the transaction code from the POS system. The segment is optional. 1-2-2 The only required segment is E1WPF02, item segment, and the fields associated with it are: Item number, Assignment, Account assignment obj, Cost center, Amount, and currency code. 1-2-3 E1WXX01, the customer enhancement segment, can be used to carry additional information in the IDoc.
© SAP AG
C
IRT360
2-40
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Technical Aspects of POS
Solutions
Unit: Technical Aspects of POS Topic: EDI Ports and Partner Profiles
2-1
The system must have a logical system name before you can complete any communications. 2-1-1 You can check for the logical system name using the following path: Tools → AcceleratedSAP → Customizing double-click Edit Project → SAP Reference IMG Basis Components →Distribution (ALE) → Sending and Receiving Systems → Logical systems → Define Logical system 2-1-2 You can see that DMRCLNT400 is defined. Now look at the next selection, Assign Client to Logical System. On this screen you can select Client No. xxx and see that the logical system is identified as assigned to our client, which is a copy of the training master.
2-2
To define a port that will define where to send your outbound files so the converter will find them. Take the paths from the SAP standard for Retail tree: Tools → AcceleratedSAP → Customizing double-click Edit Project → SAP Reference IMG Basis Components →Distribution (ALE) → Sending and Receiving Systems→ Systems in Network →Asynchronous Processing →Assigning ports → Define port or Tools → Business communication, IDoc double-click Port Definition You can also use Transaction code WE21. 2-2-1 On the left side of the screen, is a tree with the available port types. Expand the Port type File and see other ports for the POS interface. Your port type is also File. 2-2-2 The process you use to copy a Port is as follows: Select the port name you wish to copy. Press the Copy icon. Enter your Port name in the to port field.
© SAP AG
C
IRT360
2-41
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
2-2-3 If you copied SAPDPR, you only need to check the directory paths. If not, enter the directory paths. They are: Outbound directory: \\iwdf0121\sapmnt\trans\ POS\POSout\ (note there are no spaces and the final back slash is very important) Status directory: \\iwdf0121\sapmnt\trans \ POS\POSstat\ (note there are no spaces and the final back slash is very important) Press Save. 2-3
The path you take to create your EDI Partner Profile for the article data message is: Tools → AcceleratedSAP → Customizing double-click Edit. Project → SAP Reference IMG Basis Components →Distribution (ALE) → Modeling and Implementing Business Processes → Partner Profiles and Time of Processing →Maintain Partner Profile Manually or Tools → Business communication, IDoc double-click Partner Profile You can also use the transaction WE20. On the left side of the screen is a tree with the available Partner Types, expand the Partner Type KU, Customer. You note that other stores are listed here, but not your store. To create an EDI Partner profile for your store TS##, press the create button. You are now able to enter information in the upper third of the work area. Field Name or Data Type
Values
Partn. number
T8##
Partn Type
KU
Typ
US
Agent
IRT360-##
Language
EN for English or DE for German
Press Save. Now the Create Outbound Parameters button is active. 2-3-1 You will use the WP_PLU message type to send article and pricing data. 2-3-2 Press the Create Outbound Parameters button below the Outbound parmtrs. Section on the work area. On the next screen, create your message details.
© SAP AG
C
IRT360
2-42
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Field Name or Data Type
Values
Message type
WP_PLU
Receiver port
T8##
IDoc Basic Type
WP_PLU02
Output mode
Collect IDocs Start subsystem
2-3-4 When you are sure of the message types and IDoc types you are going to uses, both inbound and outbound, create an EDI partner profile with all your correct settings, then copy it to as many stores as necessary. Or, you can copy the partner profile to your reference store and use an extended copy function when creating your other stores. 2-4
Now, create the EDI partner profile for inbound article messages. From the EDI Partner profile screen for your store TS##, you may have to scroll down the work area to display the section for inbound parameters. Press the Create Inbound Parameters button below the Inbound parmtrs. Section on the work area. On the next screen, create your message details.
© SAP AG
C
2-4-1
WP_PLU, message type names with the third character an underscore (_) can be used in both directions.
2-4-2
Yes, you do need to set up WP_PLU in the inbound parameters with the test box selected to use the simulation tool for inbound testing.
2-4-3
Rather than an IDoc type, you must enter the process code (WP_P, Product Master) to handle the follow-on functions.
2-4-4
No, you do not. The converter sends the inbound IDocs to the correct directory and tells the system where the IDocs are located.
IRT360
2-43
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Unit: Mapping Store Systems to SAP Retail
Contents: Transaction Logs Conversion Categories
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
3-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Mapping Store Systems to SAP Retail: Objectives
At the end of this unit, you will be able to: Describe the types of data that might require mapping List and describe the Conversion Category parameters Configure a Conversion Category
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
3-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Unit 1 Introduction Unit 2 Technical Aspects of POS
Unit 3 Mapping Store Systems to SAP Retail Unit 4 Simple POS System Case Study Unit 5 Merchandise Management System Case Study Unit 6 Sales Audit Reporting Unit 7 Performance Issues
Unit 8 Conclusion SAP AG 2001
© SAP AG
C
IRT360
3-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Mapping Store Systems to SAP Retail
SAP Retail Tender Types Cash - PTCS Check -PTCH Voucher - PTVO Invoice - PTBL Transaction Types Sales - PN10 Staff Sales Returns Discount Types Promotion Coupon Payout Reasons Payin Reasons
Stores - System A Tender Cash - 0010 Check, personal -0020 Check, payroll - 0021 Store Card - 0040 Cr. Card, AMEX -0050 Transaction Sales -0001 Staff Sales - 0101 Cashier pickup - 04 Returns - 06 Discount types Promo - 0018 Coupon - 0018
Stores - System B Tender Cash - 100 Check - 102 Store Card -108 Transaction Sales - 100 Staff Sales - 300 Exchange - N/A Discount types Promo - N/A Coupon - N/A Employee - 162
SAP AG 2001
Not all store conditions are pre-configured in SAP Retail. Therefore, as a part of the planning process you should perform a thorough evaluation of the transaction logs from several stores. When you have a clear picture of the transactions, tenders, and other items that the stores currently capture, you can map those items to SAP Retail. In some cases, as with the condition type for Cash, PTCS, the customizing is provided.You can use this as a guide for modeling additional tender types or payment methods. When your map is complete and the customizing completed, you are ready to record the map in the Conversion Categories.
© SAP AG
C
IRT360
3-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Customize Conversion Mapping
EDI Partner Profile R310
POS Outbound Profile
OP00 IP00 AL01
X X X
OP00
OP00 XXXX XXXX
USD
Conversion Parameters
Conversion Category
R310
Site Master
CC00
CC00
CC00 US00
CC00
Conversion Details
POS Inbound Profile
X=Y
IP00 XXXX
SAP AG 2001
Inbound and outbound messages use the same conversion categories. The inbound message process access the conversion categories directly, taking the store POS codes as delivered by the converter and SAP Retail translates them into the corresponding SAP Retail terminology. Outbound messages require an additional Customer Enhancement to prepare the translation from SAP Retail to store POS terminology. A User Exit and sample program are provided for each outbound message type. See Function group XWPD in the Repository Browser for these.
© SAP AG
C
IRT360
3-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Conversion Parameters: Customizing
Conversion parameters IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Key CC00
Conversion category
CC00
Control Con. Unit of measure Con.transaction type-SpR Con. condition type Con. language Con.movement type Con. tax code Con. Transaction type Con. mdse categories Con. Payment methods Curr. Code conversion Tax classification con.
SAP AG 2001
First, a Conversion Category is created. Then, Conversion Parameters must be selected and customized if the POS system in the stores use values different from those of SAP Retail. These flag fields allow you to identify which parameters must be converted from R/3 codes to point of sale system codes. Selecting a parameter in this list requires that the corresponding code pairs be identified in the proper detail parameter screen. No further action is necessary if conversion is not required.
© SAP AG
C
IRT360
3-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Conversion Detail: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Conversion POS condition types CC00
Conversion category CC00 CC00 CC00
Des.
POS code
Condition type
185 187 163
PN10 HB00 STTX
Des.
SAP AG 2001
If a conversion category parameter is selected for conversion, a corresponding detail entry must be maintained. The detail screens are filled in similarly as the example in the slide. This example is for condition types. Condition type parameter is selected for conversion. You must specify the condition types that are uploaded from the stores. These will be the condition types identified in your POS calculation schema. The Condition types displayed in the slide are those that pass the sales value, discount value, and tax value to the pricing function in billing. Generally, you will require at least one condition type group for each country because of the differing tax conditions. You may also require different condition type groups for each POS system. In addition, you must activate the user exit for the message and use or modify SAP default coding.
© SAP AG
C
IRT360
3-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Summary
R/3 and most POS systems use different values to identify similar objects. A mapping project must be undertaken to determine the values necessary to communicate between the systems. Conversion categories provide the facility to translate these values. Inbound messages use the Conversion category tables directly to perform the translation. Outbound messages additionally require a Customer enhancement to perform the translation.
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
3-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Mapping Store Systems to SAP Retail Exercises Unit: Mapping Store Systems to SAP Retail Topic: Customizing Conversion Categories At the conclusion of this exercise, you will be able to: Customize a conversion category.
You have checked the transaction logs from your smaller store system. In the process, you have determined that it uses numerical codes for payment types, transaction types, etc. where SAP Retail uses alpha codes.
3-1
Just to convince yourself that the conversion can be handled correctly by SAP Retail, you are going to create your own Conversion Category. Later, you will map each transaction and condition but to begin testing, you will only convert the payment types. Name your category CC##. 3-1-1 What path do you take to define your Conversion Category? 3-1-2 What must you do first after naming your Conversion Category? 3-1-3 The payment types that will be used later in this course are: PTCS, PTCH, PTVO, PTBL and PTAM. Use 150 through 154 as your store system conditions. Note: Do write down the code relationships you are using. It will be important in a later exercise.
© SAP AG
C
IRT360
3-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Systems to SAP Retail Solutions Unit: Mapping Store Systems to SAP Retail Topic: Customizing Conversion Categories
3-1
You are creating a conversion category. 3-1-1 To define your Conversion Category, take the following path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution → POS Interface → Adjustments → Conversions → Conversion Categories. Select New Entries and enter Conversion Category: CC##. 3-1-2 For your next IMG activity, select Conversion parameters. Press New Entries and enter your conversion category name. Select the field Conv. Payment methods. Press Save and Back. 3-1-3 Now you must identify the payment methods and their POS counterparts. Select POS Payment Method Conversion. Enter the following values:
© SAP AG
C
Conversion Category
Payment Methods
Condition type
CC##
150
PTCS
CC##
151
PTCH
CC##
152
PTVO
CC##
153
PTBL
CC##
154
PTAM
IRT360
3-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS System Case Study
Contents: Outbound IDoc/message types Condition Type Groups POS Outbound profile POS Outbound Reports Bonus Buy Promotions POS Inbound Transactions POS Inbound Customizing Using Retail Store
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
4-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS Scenario : Objectives
At the conclusion of this unit, you will be able to: Describe the business information communicated with simple POS systems Customize POS Condition Type groups Set up and run Alternative Method for Condition Analysis Customize POS Outbound profiles Set up POS Outbound Reports Handle Bonus Buy Situations Customize some Inbound POS profiles Simulate some Inbound POS messages Describe using SAP Retail Store
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
4-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Unit 1 Introduction Unit 2 Technical Aspects of POS
Unit 3 Mapping Store Systems to SAP Retail
Unit 4 Simple POS System Case Study Unit 5 Merchandise Management System Case Study Unit 6 Sales Audit Reporting Unit 7 Performance Issues
Unit 8 Conclusion SAP AG 2001
© SAP AG
C
IRT360
4-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS System Case Study As Required: Logistics Info
Retail Store
ITS Server
POS Server IDES IDESSmart SmartRetailer RetailerInc. Inc.
Nightly: Article + Price EAN
Nightly: Sales Receipts Loss Prevention
Converter
BW Vendors SAP AG 2001
Unit Case Study: - Smart Speciality is installing SAP Retail. The company has many small stores. Their stores have fairly simple POS systems which limits how much data they exchange with headquarters. Smart Speciality expects at some point to replace their POS systems but in the interim will make use of personal computers and SAP Retail Store to handle their logistics information that has been handled manually up to now. - Smart Speciality is evaluating WP_PLU and WP_EAN as outbound message types to supply the store with data to drive their cash registers. - The headquarters merchandise manager wants the team to model Bonus Buy functionality to determine if it will support her plan to aggressively pursue manufacturer discounts that she can pass on to customers. - The merchandise manager has also requested that the stores report sales using Sales as per Receipt which will give her more detail about companion purchases and input into store layout. - The accounting team is also pleased with the Sales as per Receipt plan as it provides them with greater detail and coupled with the Loss prevention message will lead to greater financial control in the stores. - The inventory management folks are very interested in the types of information Retail Store will provide them. Some technical details: - The technical team supporting the business believes that using the Alternative Condition Analysis to prepare the outbound data will improve performance and has asked that we set up and test the functionality. - They have also completed sizing the hardware and suggest that we process POS messages using multiple application servers.
© SAP AG
C
IRT360
4-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Outbound: Topic Objectives
At the conclusion of this topic, you will be able to: Describe the type of business information carried by outbound messages Customize POS Condition Type groups Customize POS Outbound profiles Set up POS Outbound Reports
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
4-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Outbound: Process Steps
SAP Retail
1
IDES IDESSmart SmartRetailer RetailerInc. Inc.
2
Using ALE Technology change pointer analysis, create change document Report: prepare POS master data
Article(s) add new articles new EAN/UPCs change retail price change margin include in a promotion
3 4
Report: create trigger file Download data to store POS systems
Store POS Server
SAP AG 2001
POS Outbound master data message types are handled similarly using standard ALE technology and change pointers for IDoc creation. During initial startup report RWDPOSIN is run to prepare all the necessary data for the first time and transfer it to the POS systems. This Initialization should be scheduled in the background and must complete successfully (status: Preparation OK) before change messages can be created. In cases where all data is at the store POS system, the dummy initialization program (RWDPOSDU) which transfers no data but generates the required entries in the status tables for POS outbound can be run instead of the the initialization report. After either initialization is complete, whenever a user maintains master data, the application creates a change document. If the changed field was transmission-relevant, ALE creates a change pointer that identifies where the data can be found. RWDPOSUP, the change message report, is scheduled to run in the background at regular intervals after close of business. This report: • analyzes the changes that have occurred since the last time the data was successfully prepared • analyzes which sites are affected by the changes • prepares the changed data into site specific IDocs and places them into the outbound directory • creates a trigger file, which contains the paths and names of all the IDoc files to be downloaded, into the status directory which the converter accesses.
© SAP AG
C
IRT360
4-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Types of Outbound Business Data
**
Business Data (Outbound)
IDoc type
Message type
Article and condition EAN/UPC assignments Customer Exchange rates Products (Follow-on items) Material group master Taxes Set assignments Physical inventory Bonus Buys**
WP_PLU02 WP_EAN01 WP_PER01 WPDCUR01 WPDNAC01 WPDWGR01 WPDTAX01 WPDSET01 WVINVE02 WPDBBY01
WP_PLU WP_EAN WP_PER WPDCUR WPDNAC WPDWGR WPDTAX WPDSET WVINVE WPDBBY
Assortment list*
WBBDLD02
WBBDLD
require special handling
SAP AG 2001
Specific master data must be available at the point of sale in a store for any transactions to take place at an electronic cash register. Point of sale systems have a variety of capabilities, many do not have large data bases to contain the same detailed master data that R/3 contains. Therefore, SAP Retail provides several message types to carry critical master data to the stores. The types of outbound master data that can be processed via SAP Retail POS Interface and the corresponding IDoc types and message types that may be used as a ‘carrier’ for each of these data are shown. The Bonus buy message is only sent by direct request. The Assortment list data and message types are described separately as it is a special message type.
© SAP AG
C
IRT360
4-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Customize Automatic Outbound Processing ALE Active Messages
EDI Partner Profile R310
R310
Site Master
POS Outbound Profile
OP00 IP00
OP00 XXXX XXXX
USD AL01
CAL1
Calc Schema
US00 Details Conditions
OP00 CC00 US00
US00 Condition Type Group
SAP AG 2001
The POS outbound profile, the EDI partner profile and ALE work together to capture information to be downloaded to the stores. Condition type group and its detail condition types are linked to the POS outbound profile. The conditions entered in the Condition type group must be the same as those in the Calculation Schema assigned to this store. Conversion parameters provide the preliminary link to the translation of R/3 values to point of sale values. A User Exit is supplied and required to facilitate outbound processing of conversion parameters.
© SAP AG
C
IRT360
4-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Activate Change Pointers: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Activate Change Pointers for message types Log. Message Typ.
Activ
WBBDLD WPDNAC WPDSET WPDWGR WP_EAN WP_PER WP_PLU
SAP AG 2001
First, activate the ALE functionality in customizing by selecting Activate Change Pointers (generally). Then “turn on” the message types for which you desire change pointer monitoring. For POS Outbound, the message analysis uses multiple processing of change pointers for different message types so that separate change pointers do not have to be created for each message type. You must take the following links into account when activating change pointers. Log. msg type
Object Message types to be activated
WPDWGR
Merchandise Categories WPDWGR
WP_PLU
Article Master WP_PLU
WP_EAN EAN/UPC references
WP_EAN and WP_PLU
WPDSET Set Assignments
WPDSET and WP_PLU
WPDNAC
Follow-on items
WPDNAC and WP_PLU
WP_PER
Customer data
WP_PER
WPDTAX
Taxes
No change pointer analysis
WPDCUR
Exchange Rates
No change pointer analysis
© SAP AG
C
IRT360
4-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Condition Type Group: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
POS POS Condition Condition Type Type Group Group US00 Cond. Type Group US00 US00 US00
Des.
Cond. type
Des. Note end period
VKP0 VKA0 UTXJ
SAP AG 2001
You must identify the condition types that you are using in the pricing calculation schema in SAP Retail, that you want to analyze for changes and transfer to stores. You combine all the condition types together that will be used at a location in a Condition type group. Generally, you may require one condition type group for each country because of differing tax condition types. You may need to create different condition type groups for different POS systems. As shown in the example, we are identifying Sales Price (VKP0), Promotion prices (VKA0), and a Tax code (UTXJ) as conditions that are transmission relevant.
© SAP AG
C
IRT360
4-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Outbound Profile: Customizing (1/4)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Maintain Maintain Profile Profile for for POS POS Outbound Outbound OP00
Key POS outbound profile
OP00
Control POS category Conversion category Lead time
....
Exch. rate type
SAP AG 2001
Each store’s POS outbound profile provides a refinement to IDoc processing of all outgoing messages. POS category - You may enter a name in this text field for identification. For example, you might want to identify the stores in one state with the POS system type, IBM-RA, AZRA and later you would know to assign this profile to new sites with a similar location and POS system. Conversion category - Enter the name of the Conversion category that you created for the point of sale system in this store. Lead time - The future period for POS outbound that determines the number of days in the future for which data is prepared and transferred. For example, if you download to a store once a week you would enter 7. Exch. rate type - Key that you use to store exchange rates for currencies in the system.
© SAP AG
C
IRT360
4-11
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Outbound Profile: Customizing (2/4)
C u s t o m i z e
Maintain Maintain Profile Profile for for POS POS Outbound Outbound Control
OP00
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Cond. type group Person master reduc. Reduced art master Status communic. OK Recipient determin. Error mode
SAP AG 2001
Cond. type group - Enter the name of the Condition type group you created so that the conditions are analyzed and downloaded to the store. If you leave this field blank, prices cannot be determined or downloaded. Person master reduc. - Enter the name of the logical message type for reducing the person master IDoc structure that you created in the ALE environment. If you leave the field blank and the WP_PER message type is active the entire person master is downloaded. Performance is improved if a reduced person master is created. Reduced article master - Enter the name of the logical message type for your reduced article master IDoc structure that you created in the ALE environment. If you leave the field blank and the WP_PLU message type is active, the entire article master IDoc is downloaded. Status communic OK - The system places a code in this field after outbound processing is complete indicating that communication was completed successfully. Flag settings: Recipient determin. - This flag is only used when transferring data through direct ALE transfers. Error Mode - Set this flag if you want the outbound program to terminate when an error is encountered. If left blank, the incorrect items are recorded in a log and the outbound program continues with the next item.
© SAP AG
C
IRT360
4-12
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Outbound Profile: Customizing (3/4)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Maintain Profile for POS Outbound OP00
Automatic data interchange Sales permitted for all merch.cats Cross ref. Material/EAN Addit.del. Records for EAN ref Cross ref. follow on item/material Transfer merch. catgry article
SAP AG 2001
Flag settings continued: Automatic data interchange- This flag when set indicates that data is transferred to and from the POS systems in the store. If it is not set, the communication profile is used to control only the assortment list. Sales permitted for all merch.cats - When this flag is set, all merchandise categories are prepared for download to the store. If it is not set, data is prepared for only merchandise categories assigned to the store. Cross ref. Material/EAN - Set to generate an article change when an additional EAN/UPC is changed. This is used for POS systems that cannot manage EAN/UPC references and need a full article master for each EAN/UPC version of the article. Addit.del.Records for EAN ref - Set to prepare an additional deletion record with the deleted EAN as the main EAN when an additional EAN deleted. Cross ref. Follow on item/material - Set if the POS system cannot handle a separate empties message from a change to the follow-on item, but must receive a complete article master. Transfer merch. catgry article - Set to prepare an article master record with merchandise category changes when merchandise category information alone is not sufficient.
© SAP AG
C
IRT360
4-13
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Outbound Profile: Customizing (4/4)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Maintain Profile for POS Outbound OP00 Do not prepare article No POS receipt texts Do not prepare follow-on items Do not prepare sets Do not prepare merch. catgry Do not prepare exchange rates Do not prepare taxes Do not prepare customer No factory calendar
SAP AG 2001
These flag fields allow you to explicitly disallow data preparation for a particular store when the message type is activated for other stores. No action is necessary if the message type is not activated. Do not prepare article - If this flag is set, article data (including EAN/UPC references) is not prepared for outbound processing. No POS receipt texts - If this flag is set, receipt texts are not prepared for download. If receipt text in not required at the stores, set this field to improve performance. Do not prepare follow-on items - Set this flag if you do not want follow-on items prepared for download to the store. Do not prepare sets - Set this flag, if you do not want sales set data prepared for download to the store. Do not prepare merchandise category - Set this flag, if you do not want merchandise category data prepared for download to the store. Do not prepare exchange rates - Set this flag, if you do not want exchange rates prepared for download to the store. Do not prepare taxes - Set this flag, if you do not want tax rates prepared for download to the store. Do not prepare customer - If this flag is set, you do not want customer data prepared for download to the store. No factory calendar - Set this flag, if your stores are open seven days a week. The system does not take a factory calendar into consideration when preparing outbound data.
© SAP AG
C
IRT360
4-14
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Outbound Processes
POS Interface Program
Description of Process
Alt. Condition Analysis
RMEBEIN4
Initialization
RWDPOSIN
Dummy Initialization
RWDPOSDU
Change message
RWDPOSUP
Direct request
RWDPOSAN
Reorganization
RWDPOSRS
Subsequent creation of
RWDPOSTG
trigger files
SAP AG 2001
Alternative Condition Analysis report, if used, should be run before executing the Change message report. The Initialization reports should be run prior to going live. Regardless of which type of article message you use to populate your POS systems, each store must be initialized before Change message outbound processing can be used. Change Message report for POS Outbound can be set to run nightly and the system checks for store open days. If, for example, some stores are open 7 days and others only 6, the report only prepares data for the stores that are open on the following day and not those that are closed. Direct request or manual reports are used for testing, replacing missing store data, or to change a particular price when you do not wish to run the entire change analysis. These reports can still be set to run in the background, saving system resources. Reorganization reports are described in the unit on performance issues. Subsequent Creation of trigger files is a report that is used infrequently to check if there is any prepared data for which a trigger file has not been created. A trigger file might have been not created because reorganization reports were not run and sufficient disk space was not available for the file.
© SAP AG
C
IRT360
4-15
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Alternative Condition Analysis
POS Relevant Condition Changes
Worklist... …. …. Condition Changes
SAP AG 2001
The system generates a change pointer for every condition change that is made in the system. Some of these condition changes are not relevant for the stores. The alternative method of condition analysis provides a method to analyze the changes once for each application and generates a work list for each of these applications. In POS outbound and Assortment List the work list is processed rather than all condition change pointers, resulting in improved system performance. You define the specific conditions and their table names in the Condition document index before you can take advantage of this improvement.
© SAP AG
C
IRT360
4-16
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Alternative Condition Analysis: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Maintain Maintain the the Document Document Index Index
Count.. Cond. type 10 20 30
VKP0 VKA0 UTXJ
Des. No.
Table
71 Article per Plant 73 Art.per SOrg/DCh 2 Domestic Taxes
SAP AG 2001
When Change pointer generation is activated, the system records all changed conditions not just those relevant to POS. By using the Alternative method of Condition analysis, you can strengthen performance by limiting analysis to a worklist of POS relevant conditions. You specify which condition changes are relevant for each application in this table and run the program RMEBEIN4. Ensure that you identify all POS relevant condition types here for their inclusion in the condition worklist.
© SAP AG
C
IRT360
4-17
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Automatic Document Adjustment: Create Worklist
Document categories IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Purchasing documents
D e f I n e
Pricing documents PO-based load building POS outbound
Restrictions Condition change date
to
Control Data Flag processed change pointers for reorganization Flag all change pointers for reorganization Store
Process change pointers flagged for reorganization
M
M
Store System SAP AG 2001
Preparing to run the Alternative Condition Analysis requires that you create a variant for program RMEBEIN4. In the variant you select which document categories you want to process and how you want to mark the documents. Schedule this job to run prior to your change message job.
© SAP AG
C
IRT360
4-18
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Interface Outbound: Change Message
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
D e f I n e
Organizational Levels for Changes Sales organization Distribution channel Store
to
Parameters for parallel processing Parallel processing Server grp. for parallel proc. Store
Reorganize pointers
M
M
Store System SAP AG 2001
Preparing to run Outbound message automatically on a regular basis, requires that you create variants of the report. You define your variants at POS Outbound for the particular message type. You also determine at this time, if the system will process the messages using multiple application servers.
© SAP AG
C
IRT360
4-19
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Bonus Buy: Topic Objectives
At the conclusion of this topic, you will be able to: Customize SAP Retail to include bonus buy functionality. Send a Bonus Buy message to the store.
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
4-20
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Bonus Buy
Sale Take an additional 20% of purchases of $100.00 Peaches, $4.00 basket with Smart card or
$4.50
Boom Box 39.95
Any 4 tapes @ 9.99
Free
SAP AG 2001
Bonus buy conditions can be defined so that specific requirements must be met before a promotional price is offered. Requirements can be a minimum amount, a group of required articles at a certain price, and only when a loyalty card is presented, for example.
© SAP AG
C
IRT360
4-21
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Interface Outbound: Direct Request
Organizational Level
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
D e f I n e
Sales organization Distribution channel Store
to
Data to be transferred
.... Bonus buy data Transfer Bonus buy data Bonus buy
to
...
Store M
M
Store System SAP AG 2001
Bonus buy data can only be sent to the stores by a manual Outbound message. You select transfer Bonus buy data and identify the condition or conditions to transfer.
© SAP AG
C
IRT360
4-22
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inbound Processes: Topic Objectives
At the conclusion of this topic, you will be able to: Define Checking Rules for POS Inbound Customize Inbound Profiles for Sales and Loss Prevention Define a profile for distributing coupon discounts Simulate Inbound Sales as per Receipt and Loss Prevention messages Audit Sales Information
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
4-23
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Define Checking Rules for POS Inbound (1/3)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C Define Checking Rules ... u Store’s POS s Inbound profile Key Key t IP00 POS inbound profile IP00 o m i GAP analysis z e Gap analysis type
Max gap errors
......
Gap percentage rate
SAP AG 2001
The inbound checking rules functions as an IDoc preprocessor. Additional business rules for IDoc posting can still be defined in User exits. Inbound checking rules can be set up to block IDocs from posting, if the threshold level is reached. You can select to check for gaps in the transaction number either in the current IDoc (1) or in the previous IDoc also (2). You determine the acceptable threshold for gaps in numbering either by absolute numbers or a percentage rate.
© SAP AG
C
IRT360
4-24
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Define Checking Rules for POS Inbound (2/3)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C Define Checking Rules ... u Store’s POS s Inbound profile t IP00 o m i Double doc.anal. z Duplicate analysis type e Max error DDA % Error DDAnalysis
......
Days DDA
SAP AG 2001
A second check can be configured in the same customizing table, duplicate document check. There are several options that you can set here. Type of duplicate analysis - 1 check only the selected field - 2 check all fields (performance intensive) You can set either a specific number of duplicates to refuse or a percentage. You can also select to check only the current IDoc (0), all IDocs from the current day (1), and also a number greater than 1 to check historical IDocs. Caution should be used, because the larger the number of IDocs searched for the duplicate document check the greater the performance implications.
© SAP AG
C
IRT360
4-25
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Define Checking Rules for POS Inbound (3/3)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C Define Checking Rules ... u Store’s POS s Inbound profile Double doc.anal. t IP00 o m i Check POS controller z Check POS number e
......
Check transaction date Check transaction time Chck rcpt no Check qualifier Check partner number Check cashier number Check cashier name Check currency
SAP AG 2001
You can select one or several fields upon which to perform duplicate document checks. These fields are then used by the Duplicate Analysis Type (with a selection of check selected fields), to determine if a duplicate document is being sent. If the same receipt number is used at different stores, you might select the POS controller, for example, to ensure that the system only checks for duplicate receipt numbers from a single store.
© SAP AG
C
IRT360
4-26
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Coupon Distribution
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Coupon Distribution Profile Key
Coupon Profile
CP50
Cost Object 1 Coupon Share Condition type Account key
......
Affects margins
SAP AG 2001
The Coupon Distribution Profile provides the system with information to automatically handle accounting for coupons redeemed at the store. The cost of a coupon can be distributed to three shares, the percentage of which must add to 100. The Coupon condition and account key ensure correct General Ledger posting. Whether or not the share of the coupon affects margin, determines how the system handles the value of the coupon share.
© SAP AG
C
IRT360
4-27
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Receipt-Based Sales: Process Steps
SAP Retail IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
4
Forward sales data to inventory management, replenishment, billing, SAP BW
• Master data for store/article(s) • Inventory management for store/article • FI accounts
Store System
1 Gather sales data at point of sale, balance and aggregate (items, quantity, taxes, payment meth., ...) 2 If required, check customer’s credit limit and validity of credit/payment cards 3 Upload data to central SAP Retail system at regular intervals
SAP AG 2001
Sales are those transactions where goods are exchanged for payment and recorded at the cash register. Related to sales are returns where goods are returned to a store for a refund. Technically, returns are treated as negative sales by the SAP Retail system. Sales may feed data to several functions in the SAP system: inventory management, replenishment, billing and SAP Business Information Warehouse(BW). The process steps are as follows: over a set period of time, sales data (articles, quantity, taxes, payment method, date/time, ...) are recorded at the point of sale and uploaded to the central SAP Retail system at regular intervals (e.g., each night at 2 am). Upon receipt of the data, the SAP Retail system forwards the relevant data to inventory management, replenishment, billing and SAP BW for further processing.
© SAP AG
C
IRT360
4-28
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales: Aggregated vs. Sales as per Receipt Sales as per receipt IDoc 9979657 IDoc type WPUBON01
Aggregated sales IDoc 9979345 IDoc type WPUUMS01 Article Qty. Amount Milk, 1qt 5 4.45 Postcard 3 0.75 Coke, 2l 7 13.86 Apples 1 1.99 Eggs, 1dz 1 2.49 Pen-Set 3 8.97 ... Hairbrush 1 2.99
... ... ... ... ... ...
Rec. no. Article Qty. Amount ... 482165 Milk, 1qt 3 2.76 ... Postcard 2 0.50 ... ... ... ... ... 482166 Pen-Set 2 5.98 ... Coke, 1.5 1 1.98 ... ... ... ... ... 482167 Milk, 1qt 2 1.78 ... Pen-Set 1 2.99 ... ... ... ... ...
...
SUN, Russian Hill 18 Jan, 2000 Receipt no. 482165
SUN, Russian Hill SUN, Russian Hill 18 Jan, 2000 18 Jan, 2000 Receipt no. 482167 Receipt no. 482166 3 Milk, 1qt 2.76 2 Postcard 0.50 2 Pen-Set 5.98 2 Milk, 1qt 1.78 1 Pen-Set 2.99 1 Coke, 1.5 1.98 1 Coke, 2l 1.98 5 Coke, 2l 9.90 1 Hairbrush 2.99 1 Apples 1.99 1 Postcard 0.25 1 Eggs, 1dz 2.49
SAP AG 2001
SAP Retail provides two IDoc types, WPUUMS01 (message type WPUUMS) and WPUBON01 (message type WPUBON), for transmission of sales data at two levels of detail: - Sales as per receipt The details of every sales transaction are transferred to SAP R/3 system. The store system itself may assign a unique receipt number to each sales transaction, which may be transmitted to the SAP Retail system (in field BONNUMMER in IDoc type WPUBON01). Via a user exit, the SAP Retail system can be set up to check validity of the receipt numbers received from the stores (no gaps, no duplicates, ...). This user exit may also be used to assign receipt numbers to sales transaction data received from a store if the store does not do so itself. The upload of sales data per receipt is recommended if all sales transactions are to be used for statistical analysis or auditing purposes. - Aggregated sales Sales data are aggregated over all sales transactions occurring at a particular store during a set period of time and then uploaded to the SAP Retail system. Details of individual sales transactions are lost. This option greatly reduces the amount of data to be transferred and is preferred if performance is a critical issue.
© SAP AG
C
IRT360
4-29
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales: Payment Methods Sales as per receipt IDoc 9979657 IDoc type WPUBON01
Aggregated sales IDoc 9979345 Payment list IDoc type WPUUMS01 IDoc 9979576 Article ... IDocQty. typeAmount WPUTAB01
Milk, 1qt P/meth. Postcard cash Coke, 2l c/card Apples invoice Eggs, 1dz e/cash Pen-Set e/purse Hairbrush check d/debit
5 Total 3 983 7 471 185 1... 3... 1... ...
Rec. no. Article Qty. Amount ... 482165 Milk, 1qt 3 2.76 ... Postcard 2 0.50 ... cash ... ... ... ... 482166 Pen-Set 2 5.98 ... Coke, 1.5 1 1.98 ... c/card ... ... ... ... 482167 Milk, 1qt 2 1.78 ... Pen-Set 1 2.99 ... invoice ... ... ... ...
4.45 Card ... no. ... P/card 0.75 ... ... 13.86 ... VISA 1023214 ... 1.99 ... ... 2.49 ... ... 8.97 ... ... 2.99 ... ... ... SUN, Russian Hill 18 Jan, 1998 Receipt no. 482165
SUN, Russian Hill 18 Jan, 1998 Receipt no. 482166
3 Milk, 1qt 2.76 2 Postcard 0.50 1 Coke, 2l
1.98
2 Pen-Set 5.98 1 Coke, 1.5 1.98
1 Apples
1.99
1 Hairbrush 2.99
1 Eggs, 1dz 2.49
SUN, Russian Hill 18 Jan, 1998 Receipt no. 482167 2 Milk, 1qt 1.78 Invoice ... .................2.99 1 Pen-Set ......... 5 Coke, 2l 9.90 1 Postcard
0.25
SAP AG 2001
When sales data are transmitted to SAP Retail in the aggregated form, the associated payment data are transmitted as a payment list in a separate message of message type WPUTAB, using IDoc type WPUTAB01. In Sales as per Receipt, the data transmitted for each receipt includes the payment method(s) and other details used in the individual sales transaction. Combinations of payment methods in a single transaction are also possible, for example, a customer purchases goods for $120, pays $20 in cash and the remaining $100 by credit card.
© SAP AG
C
IRT360
4-30
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Goods Movements: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Movements type-dependent C control of goods movements u Store’s POS s Inbound profile t Key Key POS inbound profile o IP00 IP00 m Movement type 251 i z e Cost center
G/L account Rev. mvmt. type
252
SAP AG 2001
In addition to the necessary settings in the store’s inbound EDI profile for message type WPUWBW, the processing of goods movement IDocs (IDoc type WPUWBW01) must be customized in the store's POS inbound profile goods movement parameters. Goods movement must be identified for the Inbound POS interface so that the system knows how to handle the follow-on documents, even though the standard goods movement governs the internal processing. The processing of a goods movement in SAP Retail can be customized as follows: Cost center - If a goods movement type is relevant for cost accounting, the default cost center to which the associated costs are to be assigned is specified here. Note: If a goods movement is to be assigned to a cost center, the cost element must be defined in CO for the G/L account to which the goods movement is posted. G/L account - If the goods movement type is to be assigned to a specific G/L account, the account number can be maintained here. If no G/L account is entered here, account determination is carried out automatically in inventory management instead. Movement type for reversal of goods movement - If the goods movement is to be reversed, the movement type specified here is used.
© SAP AG
C
IRT360
4-31
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Receipt-Based Sales: Customizing (1/5)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u Store’s POS s Inbound profile t IP00 o m i z e
Control Sales as per Receipt Key POS inbound profile
IP00
Proc. Billing
X
Inventory management Update rep.-based IM
......
Statistic update
SAP AG 2001
In addition to the necessary settings in the store’s inbound EDI profile for message type WPUBON, the processing of aggregated sales data IDocs (IDoc type WPUBON01) must also be customized in the store’s POS inbound profile detailed sales parameters. SAP processes to which sales data should be forwarded Billing (SD-) - if active, sales data are passed to the billing functions that prepares them for further processing in Financial Accounting, Information System, Profit Center Accounting, Profitability Accounting, and Cost Accounting. Billing also automatically handles discounts granted at the point of sale, on which no information was provided with the sales data. Inventory management (MM-) - if active, inventory is updated according to sales data received from a store; Replenishment based inventory management - if replenishment is used in conjunction with the (simplified) replenishment-based inventory management, this indicator must be set for sales data to update replenishment-based inventory. Statistics - if active, sales data update information structures S120, and S122 in the Retail Information System (RIS). It is strongly recommended that SAP BW be used, therefore, do not activate.
© SAP AG
C
IRT360
4-32
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Receipt-Based Sales: Customizing (2/5)
Control Sales as per Receipt
...
C u Store’s POS s Inbound profile t IP00 o m i z e
Organization levels Anon. customer Storage location
0001
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
SAP AG 2001
Organization levels The follow-on processing of sales data in SD and FI require the reference to a customer. If no customer is defined, the system posts sales to the store customer number. It is further possible to specify a storage location to which inventory is updated by sales data. If a storage location is not specified, the system determines a storage location based on the article(s) and promotion number.
© SAP AG
C
IRT360
4-33
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Receipt-Based Sales: Customizing (3/5)
Control Sales as per Receipt
...
C Store’s POS u Inbound profile s t IP00 o m i z e
Process control Explode mat. Mov. type: Sale
251
Mov. type: Return
252
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
(MM-) inventory management
SAP AG 2001
Controls for sales data processing by inventory management and billing: The SAP Retail system can be told to ‘explode’ articles subject to deposits during inbound processing of sales data, if inventory is to be updated on individual article level, i.e., separately for article and associated empty. This option may be chosen if the POS system is unable to do so itself. (Note that articles subject to deposit are the only structured articles, for which this option is customizable in SAP Retail. For all other structured articles, explosion must be done either by the POS system itself, or by a POS inbound user exit in the SAP Retail system.) The movement types to be used for the posting of sales and returns are specified here. Additionally, for each of these two movement types and the POS inbound profile, a corresponding entry must be made in POS inbound customizing under ‘Movement type dependent control of goods movements’.
© SAP AG
C
IRT360
4-34
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Receipt-Based Sales: Customizing (4/5)
Control Sales as per Receipt C Store’s POS u Inbound profile s t IP00 o Process control m i z Sales doc. type OR e
...
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
DLN
Bill. type
FP
Calculation schema
POSUSJ
Number of items
100
• sales price • discounts • taxes
...
Item cat. standard
(SD-) Billing
Invoice ... ................. .........
SAP AG 2001
If billing is active, a sales document type and item category must be specified to serve as source for the copy control (sales documents ® billing documents) as defined in SD-customizing. The item category specified is also used in the billing document to be created, which is of the type chosen here. A calculation schema must be specified. Starting with the sales price that is uploaded from the POS system, the calculation schema derives values, in the form of condition records or subtotals, that are passed on to billing, inventory management, Retail Information System and accounting for further processing. In addition to the sales price, this calculation scheme usually includes various discounts and taxes. The maximum number of items to be included in each billing document may be specified.
© SAP AG
C
IRT360
4-35
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Receipt-Based Sales: Customizing (5/5)
Control Sales as per Receipt
Store’s POS C Inbound profile
u s t o m i z e
IP00
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Condition Condition
PN10
Cond. type SAP val. pr. PBEW Cond. type FI val. pr.
PBFI
SAP AG 2001
The condition types identified must be included in the calculation scheme chosen for billing. The first of these condition types represents the sales price sent by the POS system, minus all discounts calculated (by the calculation schema) or granted (at the point of sale). The second condition type is used to pass the value for sales price valuation of the goods movements to billing. The third condition type is used to pass the valuation of value-only articles in FI to billing.
© SAP AG
C
IRT360
4-36
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Receipt-Based Sales: Transaction Types
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
c u s t o m i z e
Transaction types for sales as per receipt Transaction type
Description
STSA
standard sale
PTVO
voucher sale
SFSA
staff sale
...
...
conversion
store system
transactions standard sale voucher sale staff sale
......
transaction types 100 120 300
...
SAP AG 2001
The inbound processing of receipt-based sales data by the SAP system can be customized in two ways: transaction type independent In this case, the controls of the inbound processing of receipt-based sales data are exactly the ones just discussed, and dependent solely on the (sending store's) POS inbound profile; transaction type dependent If data arising from different types of sales transactions are to be processed differently, it is necessary to define those transaction types (for sales as per receipt) in customizing. It is then possible to override some (not all!) of the transaction type independent controls of the inbound processing of receipt-based sales data for each individual transaction type. These overrides are dependent on both the store’s POS inbound profile and on the transaction type the store uploads with an individual sales transaction. In both cases, however, the necessary settings in the inbound section of the sending store’s EDI profile for message type WPUBON must be maintained. If stores use keys different from the ones used by the SAP Retail system to distinguish their different types of sales transactions at the point of sale, the conversion between the transaction types used at the store(s) and the transaction types (for sales as per receipt) used by SAP Retail must be customized.
© SAP AG
C
IRT360
4-37
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Receipt-Based Sales: Customizing
C u Store’s POS s Inbound profile t o IP00 m i z e
Transaction type-dependent control of sales as per receipt Key POS inbound profile Transaction type
IP00 PTVO
..
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Process control Reversal till recpt
...
Payment method Default values Mdse category Acct. Assignment grp
SAP AG 2001
If the inbound processing of sales data as per receipt is customized for a transaction type, it may override some controls that are maintained at the POS inbound profile only level. Also, some additional fields may be maintained: The Process choices are the same as Sales as per receipt customizing and may be redefined, as may the storage location. Reversal till receipt - If flagged, this transaction reverses the prior transaction in the IDoc and neither transaction is posted. Payment method - If flagged, this transaction is treated as if it were a payment method. Additional default values also may be defined. Merchandise category - Enter a merchandise category in this field to post transactions that do not specifically refer to an article, for example, a gift certificate or service. These items are passed to SAP Retail as text items. Account assignment group - Enter a different Account assignment group in this field to post these transactions to a different account from the one associated with the article master.
© SAP AG
C
IRT360
4-38
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Loss Prevention: Process Steps
SAP Retail
3 Process cashier statistics data
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
• Master data for store
Store System
4
View accumulated cashier statistics data, whenever needed
5
Define appropriate exception handling of cashier statistics data, if required
1
Gather POS data per cashier number (and condition type, if required)
2
Upload data to central SAP Retail system
SAP AG 2001
POS statistics data gathered at a store can be stored, and retrieved, to the central SAP Retail system. Examples of such data, gathered at one or several cash registers, can include - total sales - target till amount - Number of drawer openings - number of cancelled receipts The business scenario is as follows: over a given period of time (e.g., one day), a store gathers POS data recorded at its cash registers. These data may be accumulated for each individual cashier, and, if required, for each condition type. At the end of the set period, the data are uploaded to the central SAP Retail system for processing, i.e., they are fed into one of the Retail Communication structures for extraction into BW.
© SAP AG
C
IRT360
4-39
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Loss Prevention: (LIS-) Customizing
RIS
Activate update
S122
Info structure
Description
D W M
Cashier
X
P
FYV
P
...
C u s t o m i z e
S122
1
......
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
update interval
update mode fiscal year variant
SAP AG 2001
The processing of cashier statistics IDocs (IDoc type WPUKSR01) sent by a store requires the necessary settings in the inbound EDI profile for message type WPUKSR. The store’s POS inbound profile requires no further customizing for the processing of cashier statistics IDocs by SAP Retail system. If you are using RIS during your initial testing, it is necessary to activate the updating of the RIS information structure S122 (Cashier) in customizing. This involves determining the update interval (daily, weekly, monthly, at posting period intervals), possibly a fiscal year variant, as well as the update mode (synchronous, asynchronous, in dialog). Note: When testing is complete and before going live, remember to deactivate the RIS information structures.
© SAP AG
C
IRT360
4-40
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP Retail Store
Retail Store Purchasing activities Inventory management Sales Master data maintenance Evaluating reports
ITS Server IDES Smart Retailer Inc. IDES Smart Retailer Inc.
POS Server Converter Nightly: Article + Price EAN
Nightly: Sales Receipts Loss Prevention
Vendors
SAP AG 2001
SAP Retail Store: Smart Specialty will make use of personal computers and SAP Retail Store to handle their store logistic information that has been handled manually up to now. The stores carry some articles that customers purchase in store but are delivered directly by the vendor to their homes. Sales clerks will use Retail Store to record these transactions online. The merchandise managers will be ordering merchandise and stock clerks recording those receipts using Retail Store.
© SAP AG
C
IRT360
4-41
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS System : Unit Summary
You are now able to: Describe how outbound messages are handled by standard ALE change pointer technology so that little human interaction is required, once it is set up. Customize outbound message requirements for a store. Customize inbound sales as per receipt and loss prevention messages. Test outbound and inbound messages. Describe the uses of the SAP Retail Store.
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
4-42
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS System Case Study – Outbound Documents
Exercises
Unit: Simple POS System Case Study – Outbound Documents Topic: Customizing POS Outbound Profile and Send an Initializing Message to your Store. At the conclusion of this exercise, you will be able to: • Customize an Outbound POS Profile and create test messages to send to the stores. Other implementation team members have completed their configuration, you have set up the communication customizing, there is just one more area to customize and you can test POS Outbound for your simple POS system case study. Important note: The R/3 locking mechanism is switched off for courses doing Customizing, therefore, it is necessary for you to check that your settings have been saved. Use DISPLAY after you have saved your changes to confirm that they are recorded. 4-1
Just to make sure the message type is active, go and check in the IMG that your message type is active. 4-1-1 Was it? How did you find out its status?
4-2
Gather the information needed before you can create a POS Outbound Profile. Remember that you will require a Condition Type Group and a Conversion Category. Please check these before creating your Outbound profile. 4-2-1 What path must you take to access the POS Outbound profile? 4-2-2 Does this also bring you to where you can check the Condition Type group and the Conversion Category? If not, please identify that path.
© SAP AG
C
IRT360
4-43
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
4-2-3 What is the name of the Condition Type Group you will be using in this profile? 4-2-4 What is the name of the Conversion Category you will be using in this profile? Now, you have the information to create your Outbound profile, OP## . 4-3
Create your POS Outbound Profile. Use the name OP##. 4-3-1 What flag do you have to set to indicate that the POS systems in the store receive and supply data? What happens if this indicator is not set?
4-4
Once you are sure that your Outbound profile has been saved. Assign it to your site T8##. 4-4-1 What is the path to the site? 4-4-2 Which tab and field do you access to enter your Outbound Profile? Remember to check that the change was saved.
4-5
Your site belongs to Sales organization R300 and distribution channel R1. Initialize the article data for your site only. 4-5-1 What path did you take to access the Initialization process? 4-5-2 Did the initialization create an IDoc the first time you tried it? Look at the message sent after the initialization report is complete in the POS Monitor. 4-5-3 Did the POS Monitor display any errors? 4-5-4 If yes, what were those errors? 4-5-5 Is there a way you can work around any errors? How? Repeat the initialization process after you make any changes:
4-6
© SAP AG
C
Using the POS Monitor, determine for which articles IDocs were created. What were those articles.
IRT360
4-44
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
4-7
How can you access the IDoc file? 4-7-1 Use the IDoc file that was created to determine the price for some of the articles.
© SAP AG
C
IRT360
4-45
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS System Case Study – Inbound Documents
Exercises
Unit: Simple POS System Case Study – Inbound Documents Topic: Inbound Sales as per Receipts Customizing and Simulation At the conclusion of this exercise, you will be able to: • Customize the EDI inbound partner profile for this message types and customize the parameters for Inbound Sales as per Receipt and use the simulation tool for this message. You are continuing with your small POS system case study. Now that you know how to structure and test your outbound message, you want to configure and test the Sales as per Receipt message and determine if it will provide the information necessary to satisfy your finance department. 5-1
In the EDI partner profile of your store, T8##, maintain EDI controls for inbound processing of sales data as per receipt (message type WPUBON). You will also require inbound message type WPUWBW for goods movement. Don’t forget to set the test flag!.
5-2
Create an inbound profile IP## and assign it to your site, T8##. 5-2-1
5-3
Does the profile provide any default data? What is its purpose?
Configure the inbound processing controls for goods movement data for your POS inbound profile, IP##, to allow goods movements data for sales to be processed by the POS interface (movement types 251 and 252). For movements of either type, do not post to a cost center, and do not override the standard G/L account determination in MM customizing. 5-3-1 How many entries were you required to make?
5-4
Configure the inbound processing controls for sales data as per receipt for your POS inbound profile, IP##, copying the settings maintained by the instructor for inbound profile IP00.
5-5
Create a transaction type ST## for standard sales as per receipt, for which you want billing to be carried out in the R/3 system, but NO billing document to be saved. 5-5-1 What path do you take to create a specific transaction type?
© SAP AG
C
IRT360
4-46
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
5-5-2 Maintain the inbound processing controls for sales data as per receipt for your POS inbound profile, IP##, and this new transaction type, ST##.
Use the same settings as for IP## sales as per receipt except for the field Billing
5-6
Simulate the inbound processing of sales data as per receipt, T8##, with a billing document to be created. Sell 2 pieces of article R100016 for cash (Payment method PTCS) at T8##, at a sales price (value) of 396 USD.
Remember if you have a conversion category payment method active, payment type PTCS = 150.
5-6-1 Verify the result of the simulation. View the article document. Check that a billing document was created. How can you accomplish these checks? 5-6-2 View the G/L accounting documents. Check the open line items in your stores customer account.
5-7
Repeat the above simulation, this time you want no billing document to be saved so enter transaction type ST## in field ShTy on the simulation screen. Use the payment method for a check (PTCH or 151). 5-7-1 Verify the result of the simulation. View the article document. Check that no billing document was saved? How can you accomplish these checks?
© SAP AG
C
IRT360
4-47
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS System Case Study – Inbound Documents
Exercises
Unit: Simple POS System Case Study – Inbound Documents Topic: Inbound Cashier Statistics Simulation At the conclusion of this exercise, you will be able to: Customize the EDI inbound partner profile for this message type and use the simulation tool to test the Loss Prevention message. You are continuing to test each of the inbound message types. For the prior inbound testing you have entered your cashier number. Now you will add a cashier message to complete the posting to the info system.
6-1
In the EDI partner profile of your store, T8##, maintain EDI controls for inbound processing of cashier statistics data (message type WPUKSR). Don’t forget to set the test flag!
6-2
Simulate the inbound processing of cashier statistics data from your store, T8##. Consider entering a composite of the data you have passed in the sales transactions. You might also enter an amount of canceled transactions and their value. 6-2-1 What path do you take to simulate this transaction? 6-2-2 Verify the result of the simulation (standard analysis Cashier). How did you verify the results?
6-3
Which info structure is updated by the upload of cashier statistics by a store?
6-4
What are the characteristics of this info structure?
6-5
What are the key figures of this info structure?
6-6
What information do the Loss Prevention and the POS balancing reports give you?
© SAP AG
C
IRT360
4-48
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS System Case Study – Outbound Documents
Solutions
Unit: Simple POS System Case Study – Outbound Documents Topic: Customizing POS Outbound Profile and Send an Initializing Message to your Store. 4-1
Before you can use change pointer analysis on any message type it must be active. 4-1-1 To ensure that the message type is active, use the following path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) →Modelling and Implementing Business Processes→ Master Data Distribution→ Replication of Modified Data First select Activate Change Pointers (Generally). To ensure that ALE is active in the system. Next select Activate Change Pointers for Message Types, click on Position and enter W* to bring you to the POS message types, to ensure that WP_PLU is set to active (Checked)
4-2
To gather the information needed before you create your POS Outbound profile: 4-2-1 The path to access the POS Outbound profile is: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Outbound → Maintain Profile for POS Outbound 4-2-2 Yes, you can check the Condition type group with the selection above for the outbound profile. It is: Maintain condition type group But to go to the Conversion Category, in the IMG use the path: Also in the POS Interface tree select → Enhancement→ Conversions 4-2-3
Select Condition type group : US00.
4-2-4 Select Conversion Category: CC## 4-3
Now you can use the copy function to create your POS Outbound profile or create it by pressing New entries. To copy, use OP00 as the basis to save data entry. Select OP00 and press Copy. Type over the data displayed with the correct information. In the following fields enter this data.
© SAP AG
C
IRT360
4-49
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Field Name
Values
Conversion Category
CC##
Lead time
5
Exch. Rate type
1012
Condition type group
US00
Select Automatic Data Interchange. Save your data, back out, and return to ensure the customizing was saved. 4-4
Assign Outbound Profile to Site master. 4-4-1 Use the following path to assign your profile OP## to your site T8##. Logistics →Retailing → Master Data → Site Data → Site double-click Change. Enter your site name and select Enter. 4-4-2 Select the POS tab and enter your Outbound profile OP## in the field designated. Press Save.
4-5
Perform an Outbound message Initialization. 4-5-1
Take the following path to initialize: Logistics →Retailing → Distributed. Retailing → POS Interface→ Outbound → POS data double-click Initialization
© SAP AG
C
Field Name
Values
Sales Org
R300
Distr. Chnl
R1
Store
T8##
IRT360
4-50
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Select Execute Review the Processing Status screen and note the number of IDocs created. Back out of the screen and then check the POS monitor to determine if your initialization completed with no errors. 4-5-2 To determine if the initialization created an IDoc the first time: Select POS Monitor, enter your site T8## and press Execute. Expand Outbound, select Processed. If your site is not there, select Not fully processed 4-5-3 Although there is an IDoc, you might have error messages under Not fully processed. 4-5-4 Double-click the line that is displayed. On the next screen, select one of the red high lighted lines, press Display Log to see the error messages. When you click on some categories’ error messages, the Help will lead you to the customizing area that must be corrected. However, in this case, simply, identify those IDoc categories that will continue to stop the processing of the Initialization. 4-5-5 Go to your Outbound profile and select the categories of data that you do not want to prepare. For example Merchandise categories, Customer data, etc. Note: In an implementation, you would contact other project members to warn them of the missing information and have them correct it. Or you would fix it yourself. Now perform the Initialization a second time. This time it should work. 4-6
To determine which articles were prepared, select POS Monitor, enter your site T8## and press Execute. Expand Outbound, select Processed and locate your successful IDoc by date and time. Double-click the IDoc and on the subsequent screen, press Display data. Page through the IDoc to find which articles were prepared for your store.
4-7
The path to view your IDoc file is: enter Transaction code AL11. When the SAP Directories screen displays, page down to DIR_TRANS. Double click to expand the directory. Double-click on POS and then on POSout and then expand your IDoc by double clicking it. 4-7-1 You must scroll to the right to view the article number in segment E2WPA01. The condition type, VKPO, is identified in segment E2WPA04 and the price is in segment E2WPA05001.
© SAP AG
C
IRT360
4-51
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS System Case Study -- Inbound Documents
Solutions
Unit: Simple POS System Case Study -- Inbound Documents Topic: Inbound Sales as per Receipt Customizing and Simulation 5-1
To simulate inbound processing of sales as per receipt data, message type WPUBON must be maintained in the EDI partner profile with the test flag set. Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modeling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc → Partner Profile Expand Partner type KU. Select your site T8##. Scroll down to display Inbound parameters and press Create Inbound parameters. The message type and process codes are:
5-2
Field Name or Data type
Values
Message type
WPUBON (sales per receipts) WPUWBW
Process code
WPUB (sales per receipts) WPUWBW
Test
Check
Trigger Immediately
Check
Create an inbound profile IP## and assign it to your site T8##. Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Maintain profile for POS inbound Assign the profile to your site. Use the path: Logistics →Retailing → Master Data → Site Data → Site double-click Change. Enter your site name T8## and select Enter. Select the POS tab and enter your POS inbound profile in the designated field.
© SAP AG
C
IRT360
4-52
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
5-2-1 The inbound profile provides the name that links your other profiles to the site. 5-3
Configure inbound processing controls for goods movement data for your POS inbound profile, IP## to allow the system to move data between quality inventory and cost of good sold to be processed by the POS interface. Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound click Movement typeDependent Control of Goods Movements 5-3-1 You require 2 entries, each movement type with its reversal. Select New entries and then enter: These are your entries: Field Name or Data Type
Values
POS Inbound Profile
IP##
Movement type
251 252
Rev. mvnt.ty
252 251
For the movement type lines, do not enter a cost center, and do not enter a G/L account. Account determination in MM will default in the correct account number. 5-4
Configure inbound processing of sales data as per receipt. Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Control sales as per receipts Maintain the inbound processing controls for sales data as per receipt for your POS inbound profile, IP##. Copy the settings maintained for inbound profile IP00 or SAPD, if IP00 is not available. Modify your profile to ensure that your Storage Location 0001 is identified, the Calculation schema is POSUSJ.
5-5
Configure inbound processing of sales data as per receipt with a new transaction type as an additional control key. 5-5-1 Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution → POS Interface → Inbound → Transaction types for sales as per receipts First, identify the transaction type by entering ST## and a description.
© SAP AG
C
IRT360
4-53
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
5-5-2 Now, complete the control screen, using the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution → POS Interface → Inbound → Transaction typedependent control of sales as per receipts Select New entries. Enter your POS inbound profile, and the transaction ST##. You want inventory management and replenishment based inventory management so, select both fields and set field ‘Billing’ to 1. Use the Matchcode on the Billing field to determine the meaning of 1 in the field. Enter your storage location, 0001; movement type Sale, 251, the return 252, and item cat. Standard, DLN. 5-6
Simulate the inbound processing of sales data as per receipt from your store, T8##, with a billing document. Use the path: Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Sales Enter your site number and select Sales as per recpts.
Field Name or Data Type
Values
Currency
USD
Qual
artn
Number
R100016
Quantity
2
Sales value
396
ShTy
Blank
Select Payment methods. The sale was for cash so enter 150 for the Payment method and 396 for the final total. Press Save. 5-6-1 Select IDoc status to verify the result of the simulation. With a status of 53, Application document posted, select POS monitor to view the resulting documents. Two documents are created, a Billing document and an Article document. 5-6-2 Double click on the Billing document, select Accounting doc, which displays your document choices. Double clicking on each of the document types, displays the detail information associated with the document type. In addition to accessing these documents through the POS monitor, you also can use the following paths to access them through the modules. To display article documents:
© SAP AG
C
IRT360
4-54
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Logistics →Retailing → Merchandise. logistics → Inventory management → Article document double-click Display To display billing documents: Logistics →Retailing →Sales → Billing → Billing document double-click Display To display G/L account document: Accounting → Financial accounting → General ledger → Document double-click Display/change line items To display open line items in a customer account: Accounting → Financial accounting → Accounts receivable → Account double-click Display line items Enter Customer = T8## Company code = R300, and select field Open items. 5-7
Simulate processing sales data as per receipt, this time referring to transaction type ST##. Create the same item data as above, but enter ST## in ShTy. Select Payment methods and enter 151 for payment type check and the final total, $396. Press Save. 5-7-1 Select IDoc status to verify the result of the simulation. With a status of 53, Application document posted, select POS monitor to view the resulting documents. Only one Article document is created, no billing document, as we specified in configuring.
© SAP AG
C
IRT360
4-55
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Simple POS System Case Study -- Inbound Documents
Solutions
Unit: Simple POS System Case Study -- Inbound Documents Topic: Inbound Cashier Statistics Simulation 6-1
To simulate inbound processing of cashier statistics, message type WPUKSR must be maintained in the EDI partner profile with the test flag set. Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modelling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc → Partner Profile Expand Partner type KU. Select your site T8##. Scroll down to display Inbound parameters and press Create Inbound parameters. The message type and process code are: Field Name or Data type
Values
Message type
WPUKSR
Process code
WPUK
Test
Check
Trigger Immediately
Check
Reminder: No specialized customizing is required for inbound processing of Cashier Statistic. However, the Information Structure must have been maintained.
© SAP AG
C
IRT360
4-56
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
6-2
Simulate the inbound processing of cashier statistics data, uploaded from your store, T8##. 6-2-1 Use the following path: Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Sales Enter your site number and select, Cashier statistics Accept today’s date, leave the update group blank and the system defaults 800. Enter your group number ## in the Cashier field, and USD in Target currency. Some example data: Field Name or Data Type
Values
Cashier
Group ##
Till amount target
792
Actual amount till
780
Neg. till difference
12
Value canceled transactions
200
No. terminations
4
Sales
792
Bus. Vol w/o tax
792
6-2-2 Verify the result of the simulation first by selecting IDoc status to determine if the simulation worked error free. Then, take the following path to Cashier standard analysis: Logistics → Retailing→ Info system/Planning → Retailing → Standard analyses → Special processes → Sales audit double-click Cashier 6-3
To find which info structure is updated by the upload of cashier statistics by a store. On the initial list generated by the Cashier standard analysis, select Goto → Other info struct... Note the structure S122
6-4
To determine the characteristics of this info structure. On the initial list generated by the Cashier standard analysis, select Extras → Disp. std drilldown. You will see the answer: Sales district, Site, Cashier number, Condition type, and Date.
6-5
© SAP AG
C
What are the key figures of this info structure?
IRT360
4-57
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
On the initial list generated by the Cashier standard analysis, select Edit → Choose key figures... 6-6
© SAP AG
C
These two reports capture the data sent by the store that has been captured by the POS system in the store. Depending on the system, every key press at the register is captured by the store system providing the sales auditor with valuable loss prevention information.
IRT360
4-58
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study
Contents: Outbound Assortment List Configuring Inbound Logistics Simulating Inbound Logistics Configuring Aggregated Sales and Payment List Simulating Aggregated Sales and Payment List Configuring FI transactions Simulating FI transactions
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
5-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study : Unit Objectives
At the conclusion of this unit, you will be able to: Describe the business information communicated with merchandise management systems Customize Assortment list types and profiles Describe customizing settings for: Store orders, goods movements, Article changes, Aggregated Sales and Payment lists, and Financial transactions and Physical Inventory Simulate Assortment Lists and Inbound Processes
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
5-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Unit 1 Introduction Unit 2 Technical Aspects of POS
Unit 3 Mapping Store Systems to SAP Retail Unit 4 Simple POS System Case Study
Unit 5 Merchandise Management System Case Study Unit 6 Sales Audit Reporting Unit 7 Performance Issues
Unit 8 Conclusion SAP AG 2001
© SAP AG
C
IRT360
5-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Scenario Vendors DCs
Mer. Mgmt. Sys
IDES IDESSmart SmartRetailer RetailerInc. Inc.
Assortment List
BW
Converter
Nightly: Agg. Sales Payment Types Financial Trans. Loss Prevention Store Orders Goods Receipt As Needed: Article Change EAN Change Physical Inventory
SAP AG 2001
Unit Case Study: Smart’s General Merchandise stores present a different situation from their specialty stores. The stores, in this case, are fairly autonomous, doing their own buying both externally and from the DC. Their accounting books are kept at headquarters and they report all they do via POS interface. The team is evaluating the assortment list message for supplying the stores with article information. Although they are looking into reducing the message to eliminate segments they do not use. The inventory management team would like us to provide logistics information to headquarters through the POS interface, so we are evaluating Store Order and Goods movement messages and also the Article and EAN changes, and Physical Inventory messages. Since each of the stores reconcile their sales at the end of the day before reporting, there is no need to capture the detailed receipt based sales. Consequently, for these stores we will report sales through the Aggregated sales and payment list messages. To reconcile all store cash at headquarters, we will also use the Financial Transactions message. After we complete our testing, we will meet with the Sales Audit group to ensure that our planned message types meet their requirements for reporting.
© SAP AG
C
IRT360
5-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List: Topic Objectives
At the end of this topic, you will be able to: Describe the Assortment List message Evaluate whether to use the Assortment List message Customize the Assortment List profile
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
5-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List Outbound: Process Steps
SAP Retail IDES IDESSmart SmartRetailer RetailerInc. Inc.
Article(s) Article(s) add add new new articles articles new new EAN/UPCs EAN/UPCs change retail change retail price price change change margin margin include include in in aa promotion promotion
1
Using ALE Technology change pointer analysis, create change document
2
Report: prepare POS master data
3
Download data to store POS systems
Store Merchandise Management System
SAP AG 2001
The Assortment List master data message is handled similarly as other outbound messages using standard ALE technology and change pointers for IDoc creation. During initial startup report RWDPOSIN is run to prepare all the necessary data for the first time and transfer it to the POS systems. This Initialization should be scheduled in the background and must complete successfully (status: Preparation OK) before change messages can be created. After initialization is complete, whenever a user maintains master data, the application creates a change document. If the changed field was transmission-relevant, ALE creates a change pointer that identifies where the data can be found. RWDPOSUP, the change message report, is scheduled to run in the background at regular intervals after close of business. This report: analyzes the changes that have occurred since the last time the data was successfully prepared prepares the changed data into IDocs and places them into the outbound directory
© SAP AG
C
IRT360
5-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List Contents
All articles that can be ordered per store within a given time, description of new articles and those to be discontinued
Information about sources of supply (DC or vendor, purchase information, delivery unit, sales unit) Information about important movement data (promotions, allocation tables, last orders) Information about presentations and article sales (labels, sales prices, layout specifications)
SAP AG 2001
The Assortment list contains selected data of the integrated article maintenance that are relevant for the store or customer. A source determination is made for the articles so that the store knows from where to order each article. More than one source can be transmitted. Optionally, transaction data (promotions, allocation tables, orders) are read as well. This data can support the store's merchandise planning functions. Information about the layout of the store provides directions for article placement and planning by visual inspection and also, where necessary, for generating shelf-edge labels.
© SAP AG
C
IRT360
5-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Customize Automatic Assortment List Processing
R310
Site Master
ALE Active Messages
EDI Partner Profile R310
POS Outbound Profile
POS1 POS2
Assort. List Profile
USD AL00
POS1 A
Article Master
AL00 B C
A
AL Type
SAP AG 2001
The Assortment List profile with its assortment type, the POS Outbound profile, the EDI partner profile, and ALE work together to create an outbound assortment list message.
© SAP AG
C
IRT360
5-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List Types: Customizing
IDES IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Assortment list Types Assort Des. Lead time Cycle, No. of list type Assort. change change list versions versions F
2
H A
3 3
5 14 7
3 4 4
SAP AG 2001
The above example has three types of Assortment List which allows for different cycles for the three types of articles in our training company--Food, Hardware, and Apparel articles. Using Assortment list types allows multiple versions to be handled by a single Assortment List profile.
© SAP AG
C
IRT360
5-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Outbound: AL Version Management
Definition of n change versions before the next full version Version 1 (full version) Lead time 2 days
08/10 = 1st generation
... next full version
Version 2 (change version)
Cycle time 5 days
08/15 = Next Generation
08/20
t n+1
SAP AG 2001
Version management is recorded in the Assortment List Type entries in the system. This slide provides a detailed look at how version management works. The cycle time definition provides the data for the system to calculate the validity period and the next generation dates for the assortment list. In addition, you can define how many change versions to send before the system sends a full version.
© SAP AG
C
IRT360
5-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List Profile: Customizing (1/4)
IDES IDESSmart SmartRetailer RetailerInc. Inc.
c u s t o m i z e
Maintain profile for assortment lists AL00
AL profile
AL00
Key Assortment list type
H
Parameters AL applic. mode
3
Cond. Type group
US00
......
Reduction
SAP AG 2001
Like all other profiles in R/3, the Assortment List profile handles data entry in a most efficient fashion. The Parameters are: Application mode: how will the assortment list be used. - 1 Save versions, do not send as message - 2 Send as message, do not save versions - 3 Send as message and save versions - 4 Do not save any version or send any message. Condition Type Group - Group created earlier to handle conditions used to prepare pricing to download. Reduction - If you have created a reduced Assortment List message, enter the name in this field. Otherwise, the system will use the full WBBDLD message.
© SAP AG
C
IRT360
5-11
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List profile: Customizing (2/4)
C u s t o m i z e
Maintain profile for assortment lists AL00
...
IDES IDESSmart SmartRetailer RetailerInc. Inc.
Sorting procedure
1
AL structure
WBBP_LINE
Number of lines Print form
Assortment_List
......
OutputDevice
SAP AG 2001
Sorting Procedure controls how the Assortment List will be structured. The options are by: 1 - Department, layout area 2 - Layout area 3 - Vendor, vendor sub-range, article number 4 - Vendor, merchandise category, article number 5 - Department, merchandise category, article number 6 - Merchandise category, article no. 9 - Other, a user exit. Assortment List data line structure. This field identifies a dictionary structure that is used to create and interpret the assortment list data line. The data for the structure is taken from the WBBP_MAX structure and consequently only fields that are included in that structure should be included. The system is supplied with the following Assortment List structures: WBBP_LINE for the retail sector WBBP_LAB for shelf-edge labeling WBBP_WH_SL for the wholesale sector WBBP_STORE for Retail Store Number of lines is to designate the number of lines that fit on a single page of the assortment list. This allows one to create a table of contents for the assortment list. Format for printing the assortment list. This is used in conjunction with the data line structure. OutputDevice is the name of your printer, if you want a printed assortment list. © SAP AG
C
IRT360
5-12
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List Profile: Customizing (3/4)
c u s t o m i z e
Maintain Maintain profile profile for for assortment assortment lists lists AL00
......
IDES IDESSmart SmartRetailer RetailerInc. Inc.
Print immed. Flag changes Sales usage Recipient determin.
SAP AG 2001
Print immed.(iately). Select this field if you want the system to print the assortment list immediately after creating the assortment list. Flag changes, tells the system to examine the master data changes even when creating a full version. Selecting this field has performance implications. Sales usage, selecting this field allows an article to remain in the assortment list after the end of the ordering period. The article remains until the end of the selling period. Recipient determin., identifies that the system should use the ALE distribution model to determine where to send the list when creating IDocs. This has performance implications and should not be used for POS outbound.
© SAP AG
C
IRT360
5-13
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List Profile: Customizing (4/4)
IDES IDESSmart SmartRetailer RetailerInc. Inc.
c u s t o m i z e
Maintain Maintain profile profile for for assortment assortment lists lists RS00
Other Other functionality functionality Vendor Info. Ext. change info Ext. layout modules Lyt module versions
SAP AG 2001
Vendor Info – If stores perform purchasing locally, select this field to include Vendor information in the assortment list. When this field is not selected, segment W1WBB13 of IDoc WBBDLD03 is not prepared for the store. Ext. change info – If you are including change information from an external source, select this field. Ext. Layout modules – If you are using an external space management system for your store layout, select this field. Lyt module versions – Becomes active when you select external layout modules.
© SAP AG
C
IRT360
5-14
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List Report Processes
Description of Process Alt. Condition Analysis Initialization Change message Direct request Reorganization
Assortment List Report
RMEBEIN4 RWDBBINI RWDBBUPD RWDBBMAN RWDPOSRS
SAP AG 2001 SAP AG
Alternative Condition analysis report, if used, should be run before executing the Change message report. The Initialization report should be run prior to going live. If you are using the Assortment List message to populate your store systems, each store must be initialized before change message download can be used. Change Message report for Assortment List can be set to run synchronous with the assortment list cycle time, if all stores are, for example, on a 5 day cycle. If, however, stores are on different cycles you might set the report to run nightly. Then the report checks the cycle you set in Version Management and prepares Change message only for those stores that have cycles requiring one. Direct request or manual reports are used for testing, replacing missing store data, or to change a particular price when you do not wish to run the entire change analysis. These reports can still be set to run in the background, saving system resources. Reorganization reports are described in the last unit under performance issues.
© SAP AG
C
IRT360
5-15
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Assortment List: Change Message
Assortment user IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
D e f I n e
Sales organization Distribution channel Store
to
Assortment list Assortment list type
to
Control data Do not use cycle Generate merged versions Parallel processing Max. no. processes Store
Logon/server group
M
M
Store System SAP AG 2001
Preparing to run the Assortment List message automatically on a regular basis, requires that you create variants of the report. You define your variants at POS Outbound, Assortment List Change message. You may choose to ignore an assortment list type cycle and include all articles assigned to the defined User selections. You may also choose to merge all other change versions with the last full version after the system generates this change version. You also determine at this time, if the system will process the messages using multiple application servers, if you want to limit the number of processes running in parallel, and the name of a server group to perform the parallel processing.
© SAP AG
C
IRT360
5-16
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inbound - Back Office Transactions: Objectives
At the end of this topic, you will be able to: Customize the inbound profile for back office transaction messages Use the system’s simulation tool for inbound processing of these messages
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
5-17
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Types of Inbound Business Data
Business data (inbound)
IDoc type
Message type
store physical inventory
WVINVE01* WVINVE02 WP_PLU01 WP_PLU02** WP_EAN01 WPUFIB01 WPUKSR01 WGSREQ01* WGSREQ02 ORDERS01 ORDERS02 ORDERS03 WPUWBW01 WPUUMS01 WPUBON01 WPUTAB01
WVINVE WVINVE WP_PLU WP_PLU WP_EAN WPUFIB WPUKSR WGSREQ WGSREQ ORDERS ORDERS ORDERS WPUWBW WPUUMS WPUBON WPUTAB
article master financial transactions cashier statistics store order
goods movements sales (& returns) data payment lists
Simulation x x x x x x x x x x x x x x
* obsolete (only maintained for upward compatibility reasons) ** contains extensions (of WP_PLU01) relevant for outbound communication only SAP AG 2001
The above list summarizes the types of inbound business data that can be processed by the SAP POS interface. In each case, also shown are the corresponding IDoc types and message types that may be used as a carrier for each of these business data. The last column indicates, whether or not the corresponding message can be generated and passed on to the inbound processing unit of the POS Interface, by the POS inbound simulation tool. In addition to the IDoc type/message type combinations shown in this list, the IDoc type WPUERR01 can go with message type WPUERR to send error messages from the converter to the SAP Retail system. These messages, however, are only displayed within the POS Interface Monitor and not passed for further processing by any other application within the SAP system. Finally, IDoc type WP_PER01 and message type WP_PER can be used to communicate person data between store and SAP Retail system. After release 4.0, however, inbound processing of this message is not supported.
© SAP AG
C
IRT360
5-18
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Inbound Back Office Transactions
POS Inbound
Store
SAP Retail
M
M
Store system
SAP AG 2001
Back office transactions are those that are required to run the store itself. Normally, no customers are involved in these transactions. The back office functions supported by the POS interface are inventory management transactions: Physical Inventory Store Master data changes Store Orders Goods movements, for example: - Goods receipts from a DC, other store, or vendor - Floor to damaged goods
© SAP AG
C
IRT360
5-19
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Customize Automatic Inbound Processing TR00
R310
Site Master
TR00
EDI Partner Profile
Conversion Category
R310
POS1
TR00
USD
Details Conversion
AL01
POS Inbound Profile POS2 XXXX
X X X
POS Outbound Profile
POS1 POS2
Conversion Parameters
POS2 POS2 POS2
Details Agg. Sales
POS2
POS2
Details Store Order
Details Gds Mvmt
SAP AG 2001
The processing of inbound data by the POS Interface is controlled by two main factors: - POS Inbound Profile POS inbound profiles are defined in customizing in terms of a key and description, and are assigned to stores in their site master data. The processing, in the SAP system, of each inbound message sent by a store is configured (in customizing) with reference to a particular POS inbound profile. Thus, if the SAP Retail system receives a message from a store, it retrieves the store’s POS inbound profile and processes the message according to the active customizing settings. - Inbound parameters in the EDI Partner Profile For each of the message types that a store sends to SAP Retail, a number of control parameters must be set in customizing. This is done in the inbound section of the store’s EDI profile (with partner type ‘KU’ = customer). If the store system and the central SAP Retail system use different keys for movement types, units of measure, merchandise categories, etc., the conversion between the two systems must be defined in customizing using a conversion category. This conversion category is then assigned to the store’s POS outbound profile and used both for conversion on outbound and on inbound communication.
© SAP AG
C
IRT360
5-20
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Physical Inventory: Process Steps
SAP Retail IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
• Master data for store/article(s) • Inventory management for store/article
4
Process results of store physical inventory (double document check; aggregation; physical inventory document/work item);
5
Recount (if necessary);
1 Decide which articles to count, and when; 2 Organize and carry out physical inventory (staff, count lists, MDE’s); 3 Upload count results to central SAP Retail system;
SAP AG 2001
Two main business scenarios (each of which can be varied in certain ways) are possible: - store physical inventory scheduled, organized and carried out by the store; - store physical inventory scheduled by head office, organized and carried out by store . Under scenario one, the store management decides which articles to count, and when. The store then organizes and carries out the physical inventory (roster staff, provide printed count lists/PDE’s, ...). When the physical inventory at the store is complete, the results are uploaded to, and processed by the central SAP Retail system which generates a physical inventory document automatically. In exceptional cases, a work item could be generated instead. The system also checks, whether an external count document has been posted more than once, and aggregates count items referring to the same article, as well as count items involving articles of a merchandise category, for which inventory is managed at a value-only level in the store. Finally, if count results are not within predefined tolerances, a recount may be initiated. In the second scenario, Headquarters generates an inventory document and sends it to the store. The in-store procedure and headquarters processing would be similar to scenario one.
© SAP AG
C
IRT360
5-21
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Physical Inventory: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Store Store phys. phys. inventory inventory control control C Store’s POS u inbound profile Key s t IP00 POS inbound profile IP00 o m i Store phys. Inventory control z e Creation control inv. docs
2
Grouping type
SAP AG 2001
In addition to the necessary settings in the store’s inbound EDI partner profile for message type WVINVE, the processing of store physical inventory IDocs (IDoc type WVINVE02) must also be customized in the store’s POS inbound profile physical inventory parameters. Physical inventory data in the SAP Retail system can be customized as follows: Creation of physical inventory documents in the SAP Retail system Values ‘1’ through ‘4’ are possible. Depending on whether or not a matching active physical inventory document item already exists in the SAP Retail system, the following reaction results: matching open phys. inv. matching open phys. inv. doc. item exists doc. item does NOT exist value ‘1’ update phys. inv. doc. create work item value ‘2’ update phys. inv. doc. issue message value ‘3’ update phys. inv. doc. issue message; create phys. inv. doc on repeat of IDoc value ‘4’ update phys. inv. doc. create phys. inv. doc. Values ‘2-4’ should be chosen for regular inbound processing of store physical inventory IDocs. Value ‘1’ (work item processing) should be used if physical inventory documents have already been created. That is, work item processing is used as a type of exceptional processing. Grouping type If physical inventory documents are to be created from the store IDocs, identify by which characteristic you want to group the articles counted into fewer documents.
© SAP AG
C
IRT360
5-22
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Article Master Data Changes: Process Steps
SAP Retail 3 Create workitem and forward to staff in charge of article master data maintenance (poss. exception: EAN/UPC changes)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
• Master data for articles
4
Carry out workitem to realize changes in SAP Retail article master
1 Changes to article master in store merchandise management system 2 Upload changes to central SAP Retail system article article R100018 R100018
40...890 Blouse $119,00
40...892 Blouse (linen) $99,00
SAP AG 2001
The management of a store decides to change part of the master data of one or several of the articles sold at the store. Examples: - Change article EAN/UPC In stores where some local purchasing is allowed, if the manufacturer/producer of an article changes the article’s EAN/UPC (e.g., to reflect a slight modification of the article or its packaging) - Change article cash register receipt text To provide the customer with more information on the particular article (e.g., ‘Blouse silk’ instead of ‘Blouse’) - Change article sales price To clear stock. These changes are made in the store’s merchandise management system and then uploaded to the central SAP Retail system. There, one or several workitems are created and forwarded to the staff in charge of article master data maintenance, who decides to either reject the proposed changes, or to accept them in the SAP R/3 system. Possible exception: changes of EAN/UPC can be carried through directly/automatically in the SAP Retail article master without using workflow, if preferred.
© SAP AG
C
IRT360
5-23
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Article Master Data Changes: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u Store’s POS s Inbound profile t o IP00 m i z e
Automatic Automatic EAN/UPC EAN/UPC creation creation control control Key POS inbound profile
Auto. EAN creation
IP00
X
SAP AG 2001
Article master data changes other than EAN/UPC changes: All such changes are uploaded from the store initiating the change to the central SAP Retail system via IDocs of IDoc type WP_PLU01 (or WP_PLU02) with message type WP_PLU, which must be maintained in the store’s inbound EDI profile. Upon receipt of any such IDoc, the SAP Retail system always creates a workitem in the inbox of the person responsible for updating article master data. The workitem lists the proposed changes in article master data, which must be either rejected, or manually entered through Article Master data maintenance. Article EAN/UPC changes: A store initiated change of EAN/UPC for an article is uploaded to the central SAP Retail system via an IDoc of IDoc type WP_EAN01 with message type WP_EAN, which must be maintained in the store’s inbound EDI profile. The store’s POS inbound profile can be customized for EAN/UPC changes to: EITHER use workflow OR lead to an automatic update of the article master If workflow is selected, executing the workitem automatically carries the master data changes over to the SAP Retail article master.
© SAP AG
C
IRT360
5-24
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Order: Process Steps
SAP Retail IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
• Master data for store/article(s) • Master data for DC/vendor
3 Check for, and add, missing data required for further processing (e.g., order unit, source of supply, ...) 4 Optimize order item(s) (min. order qty., rounding to log. units) Create procurement document 5 (PReq, PO or delivery) for exceptions: trigger workflow and send order confirmation to 6 Create store (optional)
PReq PReq PO PO Delivery Delivery
1
Determine short/medium term replenishment need at store (which articles, how much, when by, ...)
2
Upload data to central SAP Retail system
7
Register order confirmation
SAP AG 2001
Store order is the functionality by which store (or customer) replenishment needs are uploaded to SAP Retail, which triggers the actual procurement using the system’s purchasing and shipping functionality. The business scenario: a store determines, using it’s own merchandise management system, its short or medium term replenishment demand. Details of this demand (e.g., articles, amount, preferred delivery date, ...) are then uploaded to the central SAP Retail system, usually in regular intervals. Upon receipt of the store order data, the SAP Retail system checks for missing details that are required for further processing, but were not provided by the store (e.g., order unit, source of supply, ...). It adds these details, using information stored in the system. Further, it optimizes individual order items, adapting order quantities to minimum order quantities, or rounding to logistical units of measure according to a defined rounding profile. If the augmented data is sufficient, they are then used to create a document that triggers the procurement of the articles. Depending on the customizing settings of the SAP Retail system, this document can be: - EITHER a purchase requisition (PReq), - OR a purchase order (PO), - OR a delivery. If the augmented data are still insufficient to create the appropriate document, exception handling is triggered through workflow. Finally, an order confirmation may be sent back to the store and recorded in the store’s own merchandise management system.
© SAP AG
C
IRT360
5-25
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Order: Customizing (1/6)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Store order control C Store’s POS POS u Store’s Inbound profile profile s Inbound Key Key t POS inbound profile IP00 o m (dep. on MC) i Doc. control z Document type default e delivery delivery sales sales order order PO PO PReq PReq
IP00
3
Default del. type
LO
Sales document type
OR
Default order doc. type
UB
SAP AG 2001
In addition to the necessary settings in the store’s inbound EDI profile for message type WGSREQ, the processing of store order IDocs (IDoc type WGSREQ02) must be customized in the POS inbound profile Store Order controls. These can be defined at store level, or at store/merchandise category (MC) level. The processing of store order data in SAP Retail system can be customized as follows: Inbound processing of a store order IDoc by the SAP Retail system creates a particular document type that is determined by means of a ‘next-level logic’, that involves the ‘Document type default’ selected. This Document type default is used only, if document type data is not defined in any of the following fields, or more specific direction described in slide 6 of 6.
© SAP AG
C
IRT360
5-26
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Order: Customizing (2/6)
c Store order control u Store’s POS s Inbound profile t IP00 o Doc. control m (dep. on MC) i z e Substitute doc. type NB
...
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Substitute doc. type UB X
...
Group items
SAP AG 2001
Substitute document types for (standard) NB and UB If the standard document types for purchase orders (i.e., NB and UB) have been renamed in standard customizing of the SAP R/3 system, their new names must be specified here. Note: It is NOT recommended to rename NB and UB! Grouping of order items (flag only used at store level) If activated, store order items containing the same article, receiving store, ... are combined to a single item in the follow-on document created from the store order through inbound processing.
© SAP AG
C
IRT360
5-27
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Order: Customizing (3/6)
C Store order control u Store’s POS s Inbound profile t IP00 o Communication m (dep. on MC) Warning level error mess. i z Reply type e
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
...
2
SAP AG 2001
Scope of message log (flag only used at store level) Depending on the selection made in this field, not only errors, but also warnings or notes are logged during inbound processing of store order IDocs. These messages can then displayed as leaves of the tree generated by the POS Interface Monitor. Scope of store order confirmation (flag only used at store level) This flag is only relevant for confirmation of store order. Depending on its value: EITHER everything, OR changes only, OR all store order items, including variances, are to be confirmed to the sender of the store order.
© SAP AG
C
IRT360
5-28
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Order: Customizing (4/6)
C Store’s POS u Inbound profile s IP00 t o (dep. on MC) m i z e
Store order control
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Control Unit determin. default key Check outline agreements Default doc. cat. ext. replen. Default doc. cat. int. replen. Default doc. cat. ext. store order
...
Default doc. cat. int. store order
3 4
SAP AG 2001
Further processing controls • Settings made in this field group determine: How missing units of measure are handled Whether, or to what extent, the automatic source of supply determination should also check for outline agreements (performance critical!), The selections for ‘Default doc. cat. ... replen.’ are only relevant for store order inbound processing triggered by replenishment, as opposed to POS upload. In this case, they are used to determine the document category of the follow-on document to be generated. The selections for ‘Default document category ... store orders’ are relevant for store order inbound processing triggered by POS upload. Depending on the source of supply (either provided explicitly, or determined automatically), the ‘Default doc. cat. external store ord.’ or the ‘Default doc. cat. internal store ord.’ are used in a ‘next-level logic’ to determine the document category of the follow-on document to be generated.
© SAP AG
C
IRT360
5-29
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Order: Customizing (5/6)
Store order control
...
C Store’s POS u Inbound profile s t IP00 o m (dep. on MC) i z e
Control
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Cheapest source Check double PO Switch off doc. flow Two steps Other planning methods
SAP AG 2001
Finally, five check-boxes are provided to determine: • Whether the automatic source of supply determination, when triggered by store order inbound processing, should try to find the cheapest source of supply (very performance critical !!!). Whether store order inbound processing should check for duplicate external document numbers Whether document flow update is deactivated during inbound processing of store order IDocs; (performance critical! used only at store level) Whether store order data should be posted in one or in two steps; if posting is in two steps, the system imports the original store order data and adds missing data in the first step. In the second step, the system posts the document. Optimizing processing steps can take place on a cross-order basis between steps one and two; (used only at store level) Whether store order items containing an article, that is to be procured via replenishment or allocation, are not to be copied over to the follow-on document created by store order inbound processing.
© SAP AG
C
IRT360
5-30
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Store Order: Customizing (6/6) store order IDoc
document type = ?
PReq PReq PO PO delivery delivery
1 User exit:............................................2 Store order IDoc:...............................3 POS inbound profile a - at store/MC level, depending on source of supply (field ´Default doc. category external/internal store order`):.......b - at store/MC level (field ´Document type default`):....4 c - at store level, depending on supply source (field ´Default doc. category external/internal store order`):...... at store level d (field ´Document type default`):....3 4 Default (if anything else fails):........3
doc. type = 4 (delivery)
SAP AG 2001
... continued As the slide shows, SAP Retail searches the store order IDoc from the most specific to the least specific to determine which type of document to create. The checks are performed in the following order: check if a document type was transferred via a user exit; check if a document type was sent with the store order IDoc; check if a document type was maintained for the POS inbound profile - defined at the store/ MC level, dependent on the source of supply (field ‘Default doc. category external store order’) - defined at the store/ MC, not dependent on the source of supply (field ‘Document type default’) - defined at the store level, dependent on the source of supply (‘Default doc. category external store order’) - defined at the store, not dependent on the source of supply (field ‘Document type default’); document type = 3 (PO), if everything else fails.
© SAP AG
C
IRT360
5-31
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Goods Movements: Process Steps
SAP Retail 3
Forward goods movement to inventory management of MM module (material document)
4
Determine affected FI accounts and post
5
Determine affected cost centers in CO (if any) and post
1
Carry out (physical/logical) goods movement at store and gather related data in store system
2
Upload data to central SAP Retail system at regular intervals
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
• Master data for store/article(s) • Inventory management for store/article • Master data for FI accounts • Master data for cost centers
SAP AG 2001
Goods movements are transactions that involve goods, but not necessarily money. A goods movement can be either physical (e.g., the transfer of stock from storage location x to storage location y), or logical (e.g., the reclassification of stock that was ‘in quality inspection’ to stock that is now ‘available for unrestricted use’). Examples include: - Some stock transfers - Floor to damaged goods - Consignment goods on approval at customer - Consumption posted to a cost center. These can be modeled and documented by the inventory management functionality of the SAP system‘s MM-module. G/L accounts must be defined in the FI module and, if cost accounting is required, cost centers must also be defined in the CO module to which goods movements (e.g., consumption) are posted. The following is a typical business scenario: goods movement data (type of goods movement, items, amount, date/time, ...) are gathered at the store and uploaded to SAP Retail at regular intervals. There, the data are forwarded to inventory management which updates stock quantities accordingly and creates an article document. Further, the associated values are posted to the appropriate G/L accounts in FI and cost centers in CO (if required).
© SAP AG
C
IRT360
5-32
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Goods Movements: Movement Types
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Copy, change movement types MvT Movement type text ...
stat. relevant ...
101
GR goods receipt
...
...
...
102
Reversal of GR
...
...
...
...
...
... ...
...
201
GI for cost center
...
...
...
...
...
... ...
...
posting controls for goods movement (IM, Inv. Contr.,...)
SAP AG 2001
For each type of (physical or logical) goods movement, a (3-digit) movement type, together with a textual description, must be defined in standard SAP R/3 system customizing. For most of the conceivable goods movements, corresponding movement types are already predefined in the SAP R/3 system, for instance: movement type description 101 GR goods receipt 102 Reversal of GR ... ...... 201 GI for cost center ... ...... For each defined movement type, a movement type for its reversal is also defined, with a number equaling the number of the original movement type plus 1, e.g., movement type 102 (Reversal of GR) is the reversal of movement type 101 (GR goods receipt). There is a set of controls associated with each movement type that determine, among other things, the effects of the posting of a related goods movement in inventory management and in statistics (‘Inventory Controlling’).
© SAP AG
C
IRT360
5-33
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Goods Movements: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
POS goods movements control C u Store’s POS s Inbound profile t Key POS inbound profile o IP00 IP00 m i Process control z e Prevent PO gen. PO Search PO not found Eval. final delivery order indic
SAP AG 2001
The defaults for Good Receipts movement types, with which the system is delivered are set up the way the system searched for goods receipts in prior releases; doing a complete search for the article/store combination and if none is found, generating a purchase order. Purchase order search can be customized to limit the length of the search. - Complete search - Terminate after the article/store/Purchase order number combination are not found. - Terminate after the article/store/delivery date and vendor combination are not found. - Terminate after the article/store/vendor combination are not found Specific actions for the system to take can be set in the PO not found field. - Receive the goods and generate a purchase order - Receive the goods, generate a purchase order, but issue a warning notice - Generate a workitem - Display an error message, and do not process the IDoc Stores with this profile can also be prohibited from generating a purchase order by selecting the first field. Evaluate final delivery order indicator when set, tells the system to trigger exception handling if the end delivery indicator has been set. If it is not set, the system will post the goods receipt to a purchase order that is ‘completed’ if the quantity is within tolerance regardless. Only when it is outside the tolerance will it trigger a workflow.
© SAP AG
C
IRT360
5-34
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Goods Movements: Customizing
C u Store’s POS s Inbound profile t o IP00 m i z e
POS goods movements control
Process control
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Selection parameter Sel. param. for GR reversal Using workflows Workflow template
SAP AG 2001
A selection parameter can be identified as a further filter for selecting purchasing documents. This is not taken into consideration when a purchase order number is explicitly stated in the IDoc. The same parameters are available for filtering on the reversal of a Goods Receipt. The control of exception processing is defined in the Using workflows field. This field is delivered with “Activate old workflow for processing exceptions.” You may also select: - Activate new workflow for processing exception - Deactivate workflow for processing exceptions. You may also identify a self-defined workflow template or task. If this field is left blank, the system uses the SAP defined WS20000519 workflow.
© SAP AG
C
IRT360
5-35
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Goods Movements: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Movements type-dependent C control of goods movements u Store’s POS s Inbound profile t Key POS inbound profile o IP00 IP00 m Movement type 201 i z e Cost center
G/L account Rev. mvmt. type
202
SAP AG 2001
In addition to the necessary settings in the store’s inbound EDI profile for message type WPUWBW, the processing of goods movement IDocs (IDoc type WPUWBW01) must be customized in the store's POS inbound profile goods movement parameters. The processing of a goods movement in SAP Retail can be customized as follows: Cost center If a goods movement type is relevant for cost accounting, the default cost center to which the associated costs are to be assigned is specified here. Note: If a goods movement is to be assigned to a cost center, the cost element must be defined in CO for the G/L account to which the goods movement is posted. G/L account If the goods movement type is to be assigned to a specific G/L account, the account number can be maintained here. If no G/L account is entered here, account determination is carried out automatically in inventory management instead. Movement type for reversal of goods movement If the goods movement is to be reversed, the movement type specified here is used.
© SAP AG
C
IRT360
5-36
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Financial Transactions: Process Steps
Acc. No. 714398 dr
Acc. No. 714398 D dr
3
Forward financial transaction data to FI (account determination and posting FI document)
4
Follow-on processing in FI (if necessary)
5
Posting to corresponding cost centers in CO (optional)
1
Gather financial transaction data at merchandise management system (type of transaction, amount, ...)
2
Upload data to central SAP Retail system at regular intervals
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
• Master data for store • Master data for FI accounts • FI posting keys
cr
311.50
SAP Retail
cr 311.50
B
a bank n k
SAP AG 2001
Financial transactions are events that involve cash but no goods or other movement. Common types of financial transactions encountered at the point of sale include, for example: - Petty cash payment, - Cash deposits to bank, - Invoice settlement by customer. The following is a typical business scenario: financial transactions data (type of transaction, amount, date/time, ...) take place in the store and are uploaded to the central SAP Retail system at regular intervals. The SAP Retail system determines the accounts involved and post the amounts accordingly. These can be either G/L accounts, customer accounts, or vendor accounts. Depending on the financial transaction, follow-on processing of the data received in the SAP system’s FI module is required (e.g., invoiced sales: a customer payment on account. In this case, a credit was posted to the customer’s account at the time of the purchase (POS upload of sales data), and a debit at the time of payment (POS upload of financial transaction data). The follow-on processing in FI then consists of clearing the customer's account.) Finally, if Controlling is active, the costs involved are posted to the appropriate cost centers.
© SAP AG
C
IRT360
5-37
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Financial Transactions: Transaction Types
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u s t o m i z e
Transaction types for financial transactions FI transaction type
Description
PECA
petty cash payout
CABA
cash deposit to bank
DEIN
customer payment on acct
...
...
conversion
Store M
M
Store System
financial transactions Cash payout Cash to bank Invoice settlement
......
POS transaction types CAPA BANK CUST
...
SAP AG 2001
For each type of financial transaction recorded in the store, a corresponding FI transaction type must be defined in the SAP Retail system. It is the FI transaction type (together with the store’s POS inbound profile) that determines how data on financial transactions uploaded by a store are posted in the FI module of the SAP system. If a particular store system uses keys (POS transaction types) different from the ones used by the SAP Retail system to distinguish the different types of financial transactions at the point of sale, the conversion between the POS transaction types used by the store system and the FI transaction types used by the SAP Retail system must be customized in SAP Retail.
© SAP AG
C
IRT360
5-38
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Financial Transactions: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u Store’s POS s Inbound profile t o IP00 m i z e
Transaction type-dependent control of financial transactions Key Key POS inbound profile FI transaction type
IP00 PECA
Item no.
1
G/L account
301005
Posting key
40
SAP AG 2001
In addition to the necessary settings in the store’s inbound EDI profile for message type WPUFIB, the processing of financial transactions IDocs (IDoc type WPUFIB01) must also be customized in the store’s POS inbound profile financial transaction parameters. Posting an item of a financial transaction in SAP Retail-FI can be customized as follows: G/L account For each POS inbound profile and FI transaction type, the default G/L account number can be maintained here. Consequently, a store communicating financial transactions to the SAP Retail system does not need to include the FI account number in the IDoc(s), unless it wants to vary from the default, i.e., if either a different G/L account is to be posted to, or if a customer/vendor account is to be posted. Posting key Enter a posting key that determines various details for posting, including: - which side of an FI account is posted (debit, credit) - which type of account is posted (G/L-, customer-, vendor account); - a posting key for the posting reversal. The customizing settings described, minimizes the amount of data to be uploaded to SAP Retail to describe a particular financial transaction. From these data, the SAP system is able to create a complete FI document.
© SAP AG
C
IRT360
5-39
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inbound - Front Office Transactions: Objectives
At the end of this topic, you will be able to: Customize the inbound profile for front office transaction messages - Aggregated Sales - Payment List Describe payment card customizing. Use the system’s simulation tool for inbound processing of these messages
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
5-40
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales: Process Steps
SAP Retail IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
4
Forward sales data to inventory management, replenishment, billing, SAP BW
• Master data for store/article(s) • Inventory management for store/article • FI accounts
Store System
1 Gather sales data at point of sale, balance and aggregate (items, quantity, taxes, payment meth., ...) 2 If required, check customer’s credit limit and validity of credit/payment cards 3 Upload data to central SAP Retail system at regular intervals
SAP AG 2001
Aggregated Sales are handled the same as receipt-based sales in the store. The individual receipts are aggregated in the merchandise management system and uploaded. Sales may feed data to several functions in the SAP system: inventory management, replenishment, billing and BW, the Business Information Warehouse. The business scenario follows: over a set period of time, sales data (articles, quantity, taxes, payment method, date/time, ...) are recorded at the point of sale, aggregated and balanced at the store then uploaded to the central SAP Retail system at regular intervals (e.g., each night at 2 am). Upon receipt of the data, the SAP Retail system forwards the relevant data to inventory management, replenishment, billing and SAP BW for further processing.
© SAP AG
C
IRT360
5-41
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales: Aggregated and Payment Methods Aggregated sales IDoc 9979345 IDoc type WPUUMS01 Article Qty. Amount Milk, 1qt 5 4.45 Postcard 3 0.75 Coke, 2l 7 13.86 Apples 1 1.99 Eggs, 1dz 1 2.49 Pen-Set 3 8.97 Hairbrush 1 2.99
... ... ... ... ... ... ... ...
Payment list IDoc 9979576 IDoc type WPUTAB01 P/meth. cash c/card invoice e/cash e/purse check d/debit
SUN, Russian Hill 18 Jan, 1998 Receipt no. 482165
Total P/card Card no. ... 983 ... 471 VISA 1023214 ... 85 ... ... ... ... ... ... ... ... ...
SUN, Russian Hill 18 Jan, 1998 Receipt no. 482166
3 Milk, 1qt 2.76 2 Postcard 0.50 1 Coke, 2l
1.98
2 Pen-Set 5.98 1 Coke, 1.5 1.98
1 Apples
1.99
1 Hairbrush 2.99
1 Eggs, 1dz 2.49
SUN, Russian Hill 18 Jan, 1998 Receipt no. 482167 2 Milk, 1qt 1.78 Invoice ... .................2.99 1 Pen-Set ......... 5 Coke, 2l 9.90 1 Postcard
0.25
SAP AG 2001
Sales data are aggregated over all sales transactions occurring at a particular store during a set period of time and then uploaded to the SAP Retail system. Details of individual sales transactions are lost. This option greatly reduces the amount of data to be transferred and is preferred if performance is a critical issue. When sales data are transmitted to SAP Retail in the aggregated form, the associated payment data are transmitted as a payment list in a separate message of message type WPUTAB, using IDoc type WPUTAB01.
© SAP AG
C
IRT360
5-42
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Payment Cards: Inbound Message Handling
AMEX Clearing Acct IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Store
MC Clearing Acct
WPUBON or WPUTAB
M
M
Store System SAP AG 2001
The POS system in the store captures the customer name, card type, card number, expiration date and the amount of the sale. If payment card settlement is carried out at each store, the inbound payment type should be defined as a cash like payment, since no subsequent settlement takes place through SAP Retail. For payment card settlement carried out at headquarters, the detailed card information is uploaded as detailed payment information in the Sales as per receipt IDoc. If sales are aggregated at the store and uploaded via Aggregated sales, the payment card detail is uploaded via the Payment list IDoc. Posting to the appropriate General Ledger accounts is handled by account determination and account keys as customized.
© SAP AG
C
IRT360
5-43
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Payment Cards: Settlement Flow
Outbound IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Submit converted structure
Call Back to reconstruct batch
Inbound Merchant Bank
Bank Acct MC Clearing Acct
AMEX Clearing Acct Bank Charges Acct
SAP AG 2001
A payment card interface is required both for authorization and settlement. It is this interface that structures the R/3 data into your bank’s format. When you manually trigger settlement, the R/3 file is sent to the payment card interface and stored. The interface converts a copy of the file and forwards it to your bank. When the bank confirms settlement, it generally advises of the batch number, amount settled and exceptions that could not be settled. SAP Retail requires the detail line items to clear the documents in the Clearing account. So, the payment card interface matches the batch number with the original outbound file and uses that with the inbound data to recreate an inbound file with the settlement detail. With the Financial Accounting area properly customized, only the exceptions require any handling.
© SAP AG
C
IRT360
5-44
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Aggregated Sales: Customizing (1/5)
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
C u Store’s POS s Inbound profile t IP00 o m i z e
Aggregated Sales Control Key POS inbound profile
IP00
Proc. Inventory management
X
Billing
X
Update rep.-based IM
......
Statistic update
SAP AG 2001
In addition to the necessary settings in the store’s inbound EDI profile for message type WPUBON, the processing of aggregated sales data IDocs (IDoc type WPUBON01) must also be customized in the store’s POS inbound profile detailed sales parameters. SAP processes to which sales data should be forwarded Billing - if active, sales data are passed to the billing functions that prepares them for further processing in Financial Accounting, Information System, Profit Center Accounting, Profitability Accounting, and Cost Accounting. Billing also automatically handles discounts granted at the point of sale, on which no information was provided with the sales data. Inventory management - if active, inventory is updated according to sales data received from a store; Replenishment based inventory management - if replenishment is used in conjunction with the (simplified) replenishment-based inventory management, this indicator must be set for sales data to update replenishment-based inventory. Statistics – must be active for sales data to update information structures.
© SAP AG
C
IRT360
5-45
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Aggregated Sales: Customizing (2/5)
C Aggregated Sales Control u Store’s POS s Inbound profile t IP00 o Organization levels m Anon. customer i z Storage location 0001 e
...
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
SAP AG 2001
Organization levels The follow-on processing of sales data in SD and FI require the reference to a customer. Specified here is the number of a defined customer to be used if the POS system does not transfer the number of the actual customer involved in a particular sales transaction (sales to anonymous customers). If no customer is defined, the system posts sales to the store customer number. It is further possible to specify a storage location to which inventory is updated by sales data. If a storage location is not specified, the system determines a storage location based on the article(s) and promotion number.
© SAP AG
C
IRT360
5-46
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Aggregated Sales: Customizing (3/5)
Aggregated Sales Control
...
C Store’s POS u Inbound profile s t IP00 o m i z e
Process control Explode mat. Mov. type: Sale
251
Mov. type: Return
252
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
(MM-) inventory management
SAP AG 2001
Controls for sales data processing by inventory management and billing: The SAP Retail system can be told to ‘explode’ articles subject to deposits during inbound processing of sales data, if inventory is to be updated on individual article level, i.e., separately for article and associated empty. This option may be chosen if the POS system is unable to do so itself. (Note that articles subject to deposit are the only structured articles, for which this option is customizable in SAP Retail. For all other structured articles, explosion must be done either by the POS system itself, or by a POS inbound user exit in the SAP Retail system.) The movement types to be used for the posting of sales and returns are specified here. Additionally, for each of these two movement types and the POS inbound profile, a corresponding entry must be made in POS inbound customizing under ‘Movement type dependent control of goods movements’.
© SAP AG
C
IRT360
5-47
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Aggregated Sales: Customizing (4/5)
Aggregated Sales Control C Store’s POS u Inbound profile s t IP00 o Process control m i z Sales doc. type OR e
...
...
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
DLN
Bill. type
FP
Calculation schema
POSUSJ
Number of items
100
• sales price • discounts • taxes
...
Item cat. standard
(SD-) Billing SAP AG 2001
Invoice ... ................. .........
If billing is active, a sales document type and item category must be specified to serve as source for the copy control (sales documents ® billing documents) as defined in SD-customizing. The item category specified is also used in the billing document to be created, which is of the type chosen here. A calculation schema must be specified. Starting with the sales price that is uploaded from the POS system, the calculation schema derives values, in the form of condition records or subtotals, that are passed on to billing, inventory management, Retail Information System and accounting for further processing. In addition to the sales price, this calculation scheme usually includes various discounts and taxes. The maximum number of items to be included in each billing document may be specified.
© SAP AG
C
IRT360
5-48
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Aggregated Sales: Customizing (5/5)
Aggregated Sales Control
Store’s POS C Inbound profile
u s t o m i z e
IP00
....
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Condition Condition
PN10
Cond. type SAP val. pr. PBEW Cond. type FI val. pr.
PBFI
SAP AG 2001
The condition types identified must be included in the calculation scheme chosen for billing. The first of these condition types represents the sales price sent by the POS system, minus all discounts calculated (by the calculation schema) or granted (at the point of sale). The second condition type is used to pass the value for sales price valuation of the goods movements to billing. The third condition type is used to pass the value for valuation of the goods movements in FI to billing.
© SAP AG
C
IRT360
5-49
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Payment Lists: Customizing
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Payment C Payment list list control control Store’s POS u Inbound profile s Key t POSPOS inbound profile inbound profile IP00 o m i Organization levels z Anon. customer e
IP00
Process control OR
......
Sales doc. type
Item cat. payment list
TATX
Number of items
100
SAP AG 2001
Payment details associated with aggregated sales data are uploaded from a store to the central SAP R/3 system (in the form of a payment list) in a separate message of message type WPUTAB, using IDoc type WPUTAB01. In addition to the necessary settings in the store’s inbound EDI profile for message type WPUTAB, the processing of payment list data IDocs (IDoc type WPUTAB01) must also be customized for the store’s POS inbound profile payment list parameters. These are: Organizational level A defined ‘anonymous’ customer can be defined. However, the system takes the store’s customer number when none is identified in this field. Process control Settings made here are as for aggregated sales. In addition, an item category to be used for payment lists in the billing document to be generated must be specified. Together with the sales document type chosen, this item category is used as a source for the copy control (sales documents - billing documents) as defined in SD-customizing.
© SAP AG
C
IRT360
5-50
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System: Unit Summary
You are now able to: Describe the business information communicated among an SAP Retail system and store merchandise management systems. Customize outbound Assortment List message. Customize inbound back office messages Customize inbound aggregated sales and payment lists. Test outbound and inbound processes in the Merchandise Management system case study.
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
5-51
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Outbound Assortment List
Exercises
Unit: Merchandise Management System Case Study – Outbound Assortment List Topic: Customizing Assortment List Profile and Initializing the Store At the conclusion of this exercise, you will be able to: • Customize an Assortment List Profile and create an Assortment List to send to the stores. You are ready to take your first step in customizing your stores with merchandise management systems. That step involves some additional customizing and then testing the Assortment List message. Important note: The R/3 locking mechanism is switched off for courses doing Customizing therefore, it is necessary for you to check that your settings have been saved. Use DISPLAY after you have saved your changes to confirm that they are recorded. 7-1
You want to review the port you created earlier that defines where to send your outbound files so the converter can find them. 7-1-1 Do you require a different port for your Assortment List? 7-1-2 Do you need a different file directory?
7-2
Create a new EDI Partner Profile for your large format store. Your site is TS##. Where ## is the group number you have been assigned. You want to send your Assortment List message directly to your store. 7-2-1 Which message type and IDoc type will you use? 7-2-2 Explain how you do these processes.
7-3
Just to make sure the message type is active, go and check in the IMG that your message type is active. 7-3-1 Was it? How did you find out its status?
© SAP AG
C
IRT360
5-52
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
7-3-2 Does it matter if WP_PLU is also active in the Change Message pointer file? 7-3-3 Please explain why or why not?
7-4
Prepare to create your Assortment List profile. 7-4-1 Is there any customizing you must do to ensure that the Condition Type group and the Conversion Categories work with your Assortment List?
7-5
Use the copy function to create your Assortment List Profile. Use the name AL##. And only use assortment list types S and H for your site. 7-5-1 What path must you take to access the Assortment List profile? 7-5-2 How did you accomplish this? 7-5-3 Why might a retailer want to use different assortment list types?
7-6
Once you are sure that your Assortment List profile has been saved. Assign it to your site TS##. At this time also assign the outbound profile OP## to this store that you created earlier. 7-6-1 What is the path to the site? 7-6-2 Which tab and field do you access to enter your Assortment List Profile? Remember to check that the change was saved.
7-7
Your site belongs to Sales organization R300 and distribution channel R1. Initialize the Assortment List message type for your site only. 7-7-1 What path did you take to access the Initialization process?
© SAP AG
C
IRT360
5-53
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
7-7-2 Did the initialization create an IDoc the first time you tried it? 7-7-3 Were there errors? If yes, what were those errors? 7-7-4 How many IDocs did the system create and why? 7-7-5 How would you correct any errors or, is there a way you can work around the errors? 7-7-6 Using the POS Monitor, determine for which articles IDocs were created.
7-8
Use the IDoc file that was created to determine what data was sent for the first article. OPTIONAL:
7-9
Create a reduced message type WBBDLD for your assortment list. Assume that you will not be sending empties data and additionals data. 7-9-1 What path do you take to reduce an IDoc type? 7-9-2 What segment or segments will you not select? 7-9-3 Where must you identify the new reduced message for it to carry your assortment list?
© SAP AG
C
IRT360
5-54
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Inbound Logistics Documents
Exercises
Unit: Merchandise Management System Case Study – Inbound Logistics Documents Topic: Inbound POS Profile and Store Physical Inventory Customizing and Simulation At the conclusion of this exercise, you will be able to: • Create an Inbound POS Profile • Customize the EDI inbound partner profile for this message type • Customize the parameters for Inbound Physical Inventory • Use the simulation tool for Inbound Physical Inventory. It is now time to customize and test each of the inbound message types. You are beginning with the back office functions, in this case physical inventory. During normal operation the stores decide when to count inventory, so you are going to test in R/3 that way also, plus you want the system to create the inventory documents for you. Important note: The R/3 locking mechanism is switched off for courses doing Customizing therefore, it is necessary for you to check that your settings have been saved. Use DISPLAY after you have saved your changes to confirm that they are recorded. 8-1
Create an inbound POS profile IM## and assign it to your store, TS##. 8-1-1 What path did you take to create the inbound profile? 8-1-2 What path did you take to assign the inbound profile to your site?
8-2
Maintain EDI partner profile for processing of store physical inventory data for your store, TS##. Remember that the physical inventory message is message type WVINVE. Since we will use the simulation tool to test, don’t forget to set the test flag! 8-2-1 Which process code did you use for this message type? 8-2-2 What purpose does the process code serve?
© SAP AG
C
IRT360
5-55
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
8-3
Configure the inbound processing controls for store physical inventory data for your POS inbound profile, IM##, in such a way, that a physical inventory document is created automatically in the R/3 system (unless already existing). 8-3-1 What field must you set to ensure that the physical inventory document is created directly, and what value did you use?
8-4
Simulate the inbound processing of store physical inventory data from your store, TS##, counting only article R100016. Assume, that the count of R100016 in TS## found 2 pieces more than currently is in stock according to the R/3 inventory (check this first!). (Hint: On the simulation screen, leave the field UNIT blank.) 8-4-1 What path did you take to check the inventory of the article for your site? Record the amount of stock currently available. 8-4-2 What path did you take to simulate the physical inventory inbound message? 8-4-3 Verify the results of the simulation. Was a physical inventory document created? 8-4-4 What was its status? 8-4-5 Check your stock after simulation. Are there any changes?
8-5
Post the difference manually. 8-5-1 Did the stock change after posting the difference to the physical inventory document? How did you check this? 8-5-2 Did the status of the physical inventory document change.
© SAP AG
C
IRT360
5-56
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Inbound Logistics Documents
Exercises
Unit: Merchandise Management System Case Study – Inbound Logistics Documents Topic: Inbound Article Master Data Changes Customizing and Simulation At the conclusion of this exercise, you will be able to: •
Customize the EDI inbound partner profile for this message type
•
Customize the parameters for Inbound Article Master Data changes
•
Use the simulation tool for Inbound Article Master Data changes.
You are know you want to send article changes from time to time, so you will test article master data changes message types.
9-1
In the inbound EDI partner profile of your store, TS##, maintain the controls for inbound processing of article master data changes (message types WP_EAN and WP_PLU). Don’t forget to set the test flag to use the simulation tool! 9-1-1 Which process code did you assign to each message type?
9-2
Configure the inbound processing controls for EAN/UPC changes for your POS inbound profile, IM##, so that such changes are NOT posted to the article master automatically. 9-2-1 How did you accomplish this?
© SAP AG
C
IRT360
5-57
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
9-3
Simulate inbound processing of article master data changes from your store, TS##, and execute the resulting workitem for your store only. (Hint: On the simulation screen, refer to the article R100016 by its article number and and use the EAN/UPC number that your instructor provides.) 9-3-1 What path did you take to find and execute your workitem?
9-4
© SAP AG
C
What would headquarters’ staff have to do, if she or he would like to follow the proposal of the store manager? Where are the required changes made? (Do not make these changes, but consider how and where you would change article master data.)
IRT360
5-58
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study Inbound Logistics Documents
Exercises
Unit: Merchandise Management System Case Study Inbound Logistics Documents Topic: Inbound Store Order Customizing and Simulation At the conclusion of this exercise, you will be able to: • Customize the EDI inbound partner profile for this message type • Customize the parameters for Inbound Store Orders • Use the simulation tool for Inbound Store Orders You are continuing to test each of the inbound message types, in this case store orders.
10-1
In the EDI partner profile of your store, TS##, maintain EDI controls for inbound processing of store order data (message type WGSREQ). Don’t forget to set the test flag!
10-2
Configure the inbound processing controls for store order data for your POS inbound profile, IM##. Copy the settings maintained for inbound profile IM00. Then modify those settings to have store order inbound processing always try to generate a purchase order (both for internal and for external procurement), and to produce an error if unsuccessful. 10-2-1 What settings did you have to change?
© SAP AG
C
IRT360
5-59
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
10-3
Simulate the inbound processing of a store order for10 pieces of article R100016 by your store, TS##.
On the simulation screen, use Identifier 006 to identify the article by its article number, and leave the field Unit blank.
10-4
Verify the result of the simulation. 10-4-1 Was a purchase order created? 10-4-2 What was your source of supply? 10-4-3 What steps did you take to verify the result?
© SAP AG
C
IRT360
5-60
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Inbound Logistics Documents
Exercises
Unit: Merchandise Management System Case Study – Inbound Logistics Documents Topic: Inbound Goods Movement Data Customizing and Simulation At the conclusion of this exercise, you will be able to: •
Customize the EDI inbound partner profile for this message type
•
Customize the parameters for Inbound Goods Movement
•
Use the simulation tool for Inbound Goods Movement.
You are continuing to test each of the inbound message types, in this case goods movement. You also remember that without a goods movement control attached to your inbound profile, sales movements will not be processed by the POS interface.
11-1
In the EDI partner profile of your store, TS##, maintain EDI controls for inbound processing of goods movement data (message type WPUWBW). Don’t forget to set the test flag!
11-2
Configure POS Goods Movement control to allow the system to perform a complete search and if no document is found, to generate a purchase order.
11-3
Configure the inbound processing controls for goods movement data for your POS inbound profile, IM##, to allow goods movements data between quality inspection stock and unrestricted use stock to be processed by the POS interface (movement types 321 and 322). For movements of either type, do not post to a cost center, and do not override the standard G/L account determination in MM customizing. While on the control screen, also make entries for movement types 251 and 252 to be used later with your sales messages. 11-3-1 How many entries were you required to make? 11-3-2 What were they?
11-4
Simulate inbound processing of a movement of half of the quantity of article R100016 in quality inspection stock (check quantity first!) to unrestricted use stock in your store, TS##. 11-4-1 How much R100016 was in quality inspection stock before you started?
© SAP AG
C
IRT360
5-61
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
11-4-2 How did you check for this amount?
11-5
Verify the result of the simulation (quality inspection/unrestricted stock before and after the posting? 11-5-1 Are the results as you expected? 11-5-2 Is there an article document? 11-5-3 Is there an accounting document? Why or why not?
© SAP AG
C
IRT360
5-62
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study –Inbound Documents
Exercises
Unit: Merchandise Management System Case Study –Inbound Documents Topic: Inbound Financial Transactions Customizing and Simulation At the conclusion of this exercise, you will be able to: • Customize the EDI inbound partner profile for this message type • Customize the parameters for Inbound Financial Transactions • Use the simulation tool for Inbound Financial Transactions You know one important balancing transaction is the financial transactions that take place in the stores. So, you will test the Financial Transactions message simulation.
12-1
In the EDI partner profile of your store, TS##, maintain EDI controls for inbound processing of financial data (message type WPUFIB). Don’t forget to set the test flag!
12-2
Configure the financial transactions inbound processing controls for. your POS inbound profile, IM##, so that cash-to-bank deposits of a store (identified by financial transaction type CABA) produce the following two posting items in FI: ITEM G/L ACCOUNT POSTING KEY 1 110000 40 (debit entry) 2 100009 50 (credit entry)
12-3
Simulate the inbound processing of a cash-to-bank deposit of 173712 USD by your store, TS##. 12-3-1 Verify the result of the simulation. Record the path you took to find your results. 12-3-2 What G/L Document was created and what items were posted?
© SAP AG
C
IRT360
5-63
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study –Inbound Documents
Exercises
Unit: Merchandise Management System Case Study –Inbound Documents Topic: Inbound Aggregated Sales and Payment List Customizing and Simulation At the conclusion of this exercise, you will be able to: • Customize the EDI inbound partner profile for these message types • Customize the parameters for Inbound Aggregated Sales and Payment List • Use the simulation tool for Inbound Aggregated Sales and Payment List You are testing the front office inbound message types, in this case you want to know if the Aggregated Sales and Payment Lists IDocs will provide enough information to satisfy your finance department.
13-1
In the EDI partner profile of your store, TS##, maintain inbound processing controls for both aggregated sales data and payment list data (message types WPUUMS and WPUTAB). Don’t forget to set the test flag!
13-2
Configure the inbound processing controls for aggregated sales data for your POS inbound profile, IM##. Copy the settings maintained for inbound profile IM00. Then modify them to not update replenishment based inventory because none of the stores carrying POS inbound profile IM## use replenishment based inventory. 13-2-1 How do you ensure that replenishment based inventory is not updated?
13-3
Configure the inbound processing controls for payment list data for your POS inbound profile, IM##. Copy the settings maintained for inbound profile IM00.
13-4
Simulate the inbound processing of aggregated sales data from your store, TS## for 2 pieces of article R100016 for a total sales value of 392 USD, which included a complaint discount of 6 USD (condition type RB10). 13-4-1 Verify the result of the simulation. What documents are created by inbound processing?
© SAP AG
C
IRT360
5-64
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
13-4-2 What does the article document tell you? How did you access it and what accounts were posted? 13-4-3 How do you access the billing document? What does the billing document tell you? 13-4-4 Can you access G/L accounting documents? How? 13-4-5 View the open line items in your customer account. What additional information does that give you?
13-5
Simulate the inbound processing of the associated payment list data from your store, TS##. You want to record total check sales value of $392. Remember that you have an active Conversion Category! 13-5-1 What document types are created as a result of a payment list simulation?
© SAP AG
C
IRT360
5-65
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Inbound Documents
Exercises
Unit: Merchandise Management System Case Study – Inbound Documents Topic: Inbound Cashier Statistics Simulation At the conclusion of this exercise, you will be able to: • Customize the EDI inbound partner profile for this message types • Use the simulation tool for Cashier Statistics. You are continuing to test each of the inbound message types. For the prior inbound testing you have entered your cashier number. Now you will add a cashier message to complete the posting to the info system
14-1
In the EDI partner profile of your store, TS##, maintain EDI controls for inbound processing of cashier statistics data (message type WPUKSR). Don’t forget to set the test flag!
14-2
Simulate the inbound processing of cashier statistics data from your store, TS##. Use your group number for your cashier number. Consider entering a composite of the data you have passed in the sales transactions. You might also capture the discount (condition type) and amount, and.an amount of canceled transactions and their value. 14-2-1 What path do you take to simulate this transaction? 14-2-2 Verify the result of the simulation. How did you verify the results?
14-3
Which info structure is updated by the upload of cashier statistics by a store?
14-4
What are the characteristics of this info structure?
14-5
What are the key figures of this info structure?
© SAP AG
C
IRT360
5-66
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
14-6
© SAP AG
C
What information do the Loss Prevention and the POS balancing reports give you?
IRT360
5-67
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Outbound Assortment List
Solutions
Unit: Merchandise Management System Case Study – Outbound Assortment List Topic: Customizing Assortment List Profile and Initializing the Store 7-1
You want to review which port will define where to send your outbound Assortment List so the converter will find them. The paths you take to review the port is: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Sending and Receiving Systems → Systems in Network → Asynchronous Processing → Assigning Ports → Define port or Tools → Business communication, IDoc double-click Port Definition You can also use Transaction code WE21. 7-1-1 No, the system will use the same port for the Assortment List. 7-1-2 No, the name of the file directories where all your outbound messages, including the Assortment List, reside is: Outbound: \\app.server\sapmnt\trans\ POS\ POSout\ (note there are no spaces and the last \ is important) Status: \\ app.server \sapmnt\trans \ POS\ POSstat\ You do not have to create a separate directory, because Assortment List is essentially just another outbound message.
7-2
You need to create your EDI Partner Profile for your site TS##. The path you take to do this is: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modeling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc double-click Partner Profile or use transaction code WE20.
© SAP AG
C
IRT360
5-68
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
7-2-1 You will use message type WBBDLD and IDoc type WBBDLD02. 7-2-2 On the left side of the screen is a tree with the available Partner Types, expand the Partner Type KU, Customer. You note that other stores are listed here, but not your store. To create an EDI Partner profile for your store TS##, press the create button. You are now able to enter information in the upper third of the work area. Field Name or Data Type
Values
Partn. number
TS##
Partn Type
KU
Typ
US
Agent
IRT360-##
Language
EN for English or DE for German
Press Save. Now the Create Outbound Parameters button is active. Press the Create Outbound Parameters button below the Outbound parmtrs. Section on the work area. On the next screen, create your message details. Field Name or Data Type
Values
Message type
WBBDLD
Receiver port
T8##
IDoc Basic Type
WBBDLD02
Output mode
Transfer IDocs immed Start subsystem
Press Save. 7-3
To ensure that the message type is active, use the following path. Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) →Modelling and Implementing Business Processes→ Master Data Distribution→ Replication of Modified Data 7-3-1 Select Activate Change Pointers for Message Types, click on Position and enter W* to bring you to the POS message types, to ensure that WBBDLD is set to active. Yes, the message type is active if it is checked. 7-3-2 No, both message types can be active. In a live situation several message types will be active. 7-3-3 This one table is used by the system and one company could be using different message types to supply their stores with information.
© SAP AG
C
IRT360
5-69
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
7-4
Prepare to create the Assortment List profile by checking the Condition Type Group and the Conversion Categories. The path to check these Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Outbound → Maintain POS Condition Type Group Also in the POS Interface tree select → Enhancement→ Conversions 7-4-1 No, as long as they have been created and assigned to my outbound profile and that profile assigned to my site nothing else is necessary. However, if the code partners are different, a new Conversion category would be necessary.
7-5
Use the Copy function to create your Assortment List profile or create it using New entries. Use the following path to access the Assortment List profile: 7-5-1
Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Logistics - General → Assortment → Assortment List → Maintain profile for assortment lists
7-5-2 Copy using AL00 as the basis to save data entry. Select AL00 and press Copy. Enter your Assortment name, AL## and press the check. The system asks you to ‘specify object to be copied’. Select Copy all. After the system displays the number of entries that were copied, select your new Assortment List and double-click Maintain assortment list profile parameters in the Dialog Structure. Select the buttons for Assortment list type 1, R and T and press Delete. Save your data, back out, and return to ensure the customizing was saved. 7-5-3 A retailer might use different assortment lists to maintain different cycle times to handle slow moving goods differently from fast moving goods. 7-6
Assign the Assortment List profile to your site TS##. 7-6-1 Use the following path to assign your profile AL##. Logistics →Retailing → Master Data → Site Data → Site double-click Change. Enter your site name and select Enter. 7-6-2 Select the POS tab and enter your Assortment List profile AL## in the field designated. Enter OP## in the outbound profile field. Press Save.
7-7
Initialization 7-7-1 To perform an Initialization, take the following path:
© SAP AG
C
IRT360
5-70
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Logistics →Retailing → Distributed Retailing → POS Interface→ Outbound → Assortment List double-click Initialization
Note: There is a second path to Assortment List. It is:
Logistics →Retailing → Master Data → Assortment/Listing → Assortment List → Generate double-click Initialization Field Name or Data Type
Values
Sales Organization
R300
Distribution channel
R1
Customer no. - site
TS##
Assortment list type
S H
Select Execute. When the initialization is complete a report screen displays. View that screen and note the information it provides. Back out of the report and check the POS monitor to determine if your initialization completed with no errors. 7-7-2 Select POS Monitor, enter your site TS## and press execute. Expand Outbound, select Processed. If your site is not there, select Not fully processed. The initialization should have been successful. If it was not, double-click the line that is displayed. On the next screen, select one of the red high lighted lines, press Display Log to see the error messages. When you click on some categories’ error messages, the Help will lead you to the customizing area that must be corrected. However, in this case, simply, identify those IDoc categories that will continue to stop the processing of the Initialization. 7-7-3 There were no message stopping errors. 7-7-4 The system creates two IDocs, one for each assortment type. 7-7-5 IDocs were created for several articles. 7-8
Now, go to the IDoc file to view the Assortment List communication IDoc. The path to view your communication IDoc is: Transaction code: AL11 When the SAP Directories screen displays, page down to DIR_TRANS. Double click to expand the directory. Double click on POS and then on POSout and then expand your IDoc by double clicking it.
© SAP AG
C
IRT360
5-71
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
OPTIONAL: 7-9
Create a reduced message type WBBDLD 7-9-1 The menu path to display the structure of an IDoc type is: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components → Distribution (ALE) → Modeling and Implementing Business Processes → Master Data Distribution → Scope of Data for Distribution → Message Reduction → Create Reduced Message Type Enter ZTS## in the Reduced message type field, and press Create. Enter WBBDLD in the Message type reference field, press Check. Enter Reduced Msg WBBDLD for TS## in the Description field. Expand the folder E1WBB01, the major segment. Expand all the folders, including the sub-folders so that all segments of IDoc type WBBDLD03 are exposed. 7-9-2 Select all segments, except: E1WTADAL1 – Additionals E1WTADAL2 – Additionals text E1WBBEM – Empties E1WBB21 – BOM E1WBB22 – Article valuation.
E1WBB22 – Article valuation cannot be selected as it is part of the not yet released WBBDLD03, where the other segments are released inWBBDLD02 for 4.6B. Save your selection. Back out to the main screen. Select Activate change pointers, which inserts your reduced message type in the Activate change pointer table and sets it to active. 7-9-3 You must also identify the reduced message type in your Assortment List profile. Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Logistics - General → Assortment → Assortment List → Maintain profile for assortment lists Select each Assortment List type and enter your reduced message type ZTS## in the Reduction field. Save your changes and if you like reinitialize your store assortment, using the description in step 7-7, above.
© SAP AG
C
IRT360
5-72
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Inbound Logistics Documents
Solutions
Unit: Merchandise Management System Case Study – Inbound Logistics Documents Topic: Inbound POS Profile and Store Physical Inventory Customizing and Simulation 8-1
Create and assign POS inbound profile 8-1-1 The path to create the POS inbound profile, IM## is: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Maintain profile for POS inbound→ Maintain profile for POS inbound Select New entries and enter your profile, IM## and the description group ##. 8-1-2 The path to assign the POS Inbound Profile to your store is: Logistics →Retailing → Master Data → Site Data → Site double-click Change Enter your site name TS## and select Enter. Select the POS tab and enter your POS inbound profile in the designated field.
8-2
Maintain EDI partner profile and controls for processing store physical inventory data The path to maintain EDI partner profiles is: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modelling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc double-click Partner Profile Expand Partner type KU. Select your site TS##. Scroll down to display Inbound parameters and press Create Inbound parameters.
© SAP AG
C
IRT360
5-73
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
8-2-1 The message type and process code are: Field Name or Data type
Values
Message type
WVINVE
Process code
WVIN
Test
Check
Trigger Immediately
Check
8-2-2 The process code determines how the system handles the incoming message type. 8-3
Configure inbound processing of store physical inventory data The path to maintain store physical inventory controls is: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound →Store phys. inventory control Select New entries and enter your inbound profile, IM##. 8-3-1 To ensure that a physical inventory document is created directly, set field ‘Creation control inv. docs’ to 4.
8-4
Simulate store physical inventory to check configuration. 8-4-1 First, for a quantity view of your stock use the path: Logistics →Retailing → , Merchandise. logistics → Inventory management, Environment → Stock double-click Stock overview. Enter your article number, your site number and select Enter. There should be 50 pieces of R100016 in Unrestricted stock for your site. 8-4-2 The path to the simulate screen is: Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Store physical inventory
© SAP AG
C
IRT360
5-74
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Field Name
Values
Store
TS##
Storage location
0001
Fiscal year
current
Qualifier
artn
Identifier
R100016
Quant.
2 + the Stock overview Q
Enter your test data. Press Save. 8-4-3 When the system completes the simulation, press IDoc Status. On the next screen, press POS monitor. Record the Phys. Inventory document number and double click on the IDoc to display physical inventory count. Yes, a document should have been created. 8-4-4 On the physical inventory document screen, select Phys. inv. History to determine that the status is “counted”. 8-4-5 To check if the simulation changed your inventory, use the following path: Logistics →Retailing → Info System/Planning → Retailing → Standard Analyses → Article double-click Article
This is a different path to check your inventory. It is only intended to give you another way to check your article. The earlier inventory check also will accomplish the same goal. Enter your store and article number. Press Process and drill down on the subsequent screen. Page down on the next display to note the Quantity and value associated with this article. It should not have changed. 8-5
To accept the new count, post it using the following path: Logistics →Retailing → Merchandise logistics → Physical inventory→Difference double-click Post 8-5-1 The system defaults your Physical inventory document number, or enter the document number and press Enter. Note the difference quantity and value. Press Save to accept the change. 8-5-2 Review your inventory to note the new quantity and value. Logistics →Retailing → Info System/Planning → Retailing → Standard Analyses → Article double-click Article Once on the screen, you can also check that the system tracks all goods movements, by using the following path: Extras → Goods movements → Article document
© SAP AG
C
IRT360
5-75
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Inbound Logistics Documents
Solutions
Unit: Merchandise Management System Case Study – Inbound Logistics Documents Topic: Inbound Article Master Data Changes Customizing and Simulation 9-1
Maintain EDI controls for processing article master change data in the EDI partner profile of your store, TS##. Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modeling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc → Partner Profile Expand Partner type KU. Select your site TS##. Scroll down to display Inbound parameters and press Create Inbound parameters. 9-1-1 The message type and process code are:
9-2
Field Name or Data Type
Values
Message Type
WP_EAN WP_PLU
Process code
WP_E WP_P
Test
Check
Trigger immediately
check
Configure inbound processing of EAN/UPC change data so that such changes are NOT posted to the article master automatically. Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound →Automatic EAN/UPC Creation Control 9-2-1 Select New Entries to enter your inbound profile, IM##, and leave the field Auto. EAN creation blank. Blank means do not update automatically.
© SAP AG
C
IRT360
5-76
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
9-3
To simulate processing an article master change use the following path: Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Master data Enter your store TS## and today’s date. Then select EAN references. On the detail screen enter the following information associated with article R100016:
Field Name
Values
Change flag
MODI
Dates
accept today’s date
main EAN/UPC
2050000001208
EAN/UPC
Provided by instructor
Press Save. Press IDoc status to determine if your document posted without errors. 9-3-1 Since it was configured to stop rather than to automatically update, there will be a workflow item. To execute your workitem, use the following path: Press POS Monitor, double-click on the message attached to your IDoc. On the resulting help screen double-click on the message Office inbox (highlighted in red). 9-4
© SAP AG
C
The required changes would have to be made in the article master by someone in the organization authorized to accept them.
IRT360
5-77
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study Inbound Logistics Documents
Solutions
Unit: Merchandise Management System Case Study Inbound Logistics Documents Topic: Inbound Store Order Customizing and Simulation 10-1
To simulate inbound processing of store orders, message type WGSREQ must be maintained in the EDI partner profile with the test flag set. Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modeling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc → Partner Profile Expand Partner type KU. Select your site TS##. Scroll down to display Inbound parameters and press Create Inbound parameters. The message type and process code are: Enter WGSREQ in the Message type field. Then select Matchcode (F4) on the Process code field. It is WVFB. Set the test flag and also set the message type to Trigger immediately.
10-2
Maintain the inbound processing controls for store orders for your POS inbound profile, IM##, copy the settings of inbound profile IM00. Use the following path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Store order control To copy profile IM00, select it from the list of inbound profiles, then select the Copy icon. When the copied screen displays, enter your profile, IM## in the key field. 10-2-1 Enter 3 in Document type default, leave blank, or clear, ‘Default doc. category external store order’ and ‘Default doc. category internal store order’ at the bottom of the screen to have a purchase order created.
10-3
Simulate inbound processing of a store order, TS##. Use the path: Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Store order
© SAP AG
C
IRT360
5-78
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Enter your store TS## in Customer and accept today’s date and the Message category, WGSREQ02. Select Order Overview. On the simulation screen, enter: Field Name
Values
Identifier
006
Article/EAN
R100016
Quantity
10
Uni
Leave blank
Press Create icon. 10-4
To verify the result of the simulation: Press IDoc status and POS monitor when the system completes the simulation. 10-4-1 Yes, a purchase order should be created. 10-4-2 Double click on the Purchase order number. The Purchase Order Item Overview screen displays and you will find that the Vendor from whom you purchase the tuner is R3002, Meyer Hardware, and the order type was a standard order, NB. 10-4-3 Select Header →Statistics to view the processing statistics. Select Matchcode (F4) on the status field to determine what the status code signifies. You can also access more data by backing out of the POS monitor and taking the following path: Logistics →Retailing → Purchasing → Purchase order→ Purchase order double-click Display
© SAP AG
C
IRT360
5-79
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Inbound Logistics Documents
Solutions
Unit: Merchandise Management System Case Study – Inbound Logistics Documents Topic: Inbound Goods Movement Data Customizing and Simulation 11-1
To simulate inbound processing of store orders, message type WPUWBW must be maintained in the EDI partner profile with the test flag set. Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modelling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc → Partner Profile Expand Partner type KU. Select your site TS##. Scroll down to display Inbound parameters and press Create Inbound parameters. Enter WPUWBW in the Message type field. Then select Matchcode (F4) on the Process code field. Use process code WPUW.
11-2
Configure inbound processing controls for goods movement data for your POS inbound profile, IM## to allow the system to search all purchasing documents and if no purchase order is found to create one. Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → POS Goods Movement control Select New entries and accept the defaults: Field Name or Data Type
Values
PO search
Perform complete search
PO not found
GR with PO generation
Save and back out.
© SAP AG
C
IRT360
5-80
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
11-3
Configure inbound processing controls for goods movement data for your POS inbound profile, IM## to allow the system to move data between quality inspection stock and unrestricted use stock to be processed by the POS interface. Also create entries for Sales movement types. Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Movement typeDependent Control of Goods Movements 11-3-1 You require 4 entries, each movement type with its reversal. 11-3-2 Select New entries and then enter: These are your entries: Field Name or Data Type
Values
POS Inbound Profile
IM##
Movement type
321 322 251 252
Rev. mvnt.ty
322 321 252 251
For the movement type lines, do not enter a cost center, and do not enter a G/L account. Account determination in MM will default in the correct account number. 11-4
Simulate the inbound processing of a movement of half of the quantity of article R100016 in quality inspection stock to unrestricted use stock in your store, TS##. Check for the inventory level first. 11-4-1 There are 30 pieces in quality inspection. 11-4-2 You can find this information using the path. Logistics → Retailing→ Merchandise logistics → Inventory management → Environment → Stock double-click Stock overview Now simulate the movement. Use the path: Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Goods movements Enter your store number TS## and select Goods Movements. On the simulation screen enter the following:
© SAP AG
C
IRT360
5-81
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Field Name
Values
Reference no.
IRT360-##
The second qualifier
ARTN
Number
R100016
Mtyp
321
Quantity
15
Press Save. 11-5
Press IDoc status to verify the result of the simulation, and then POS monitor to view the document. 11-5-1 Discussion, if you did not expect the result. 11-5-2 Yes, there is an article document. Double click on it and select Accounting docs on the resulting screen. 11-5-3 No accounting document should have been created because there was no change in your inventory value, just the location.
© SAP AG
C
IRT360
5-82
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study –Inbound Documents
Solutions
Unit: Merchandise Management System Case Study –Inbound Documents Topic: Inbound Financial Transactions Customizing and Simulation 12-1
To simulate inbound processing of financial transactions, message type WPUFIB must be maintained in the EDI partner profile with the test flag set, use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modeling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc → Partner Profile Expand Partner type KU. Select your site TS##. Scroll down to display Inbound parameters and press Create Inbound parameters. Enter WPUFIB in the Message type field. Then select Matchcode (F4) on the Process code field. The process code to use is WPUF.
12-2
Configure inbound processing of financial transaction, in this example, cash-tobank deposits for your POS inbound profile, IM##. You were to establish the financial transaction type with the following posting items in FI: ITEM NO. 1 2
G/L ACCOUNT 110000 100009
POSTING KEY 40 (debit entry) 50 (credit entry)
Use the following path to check that the Financial Transaction type, CABA, has been created: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Transaction types for financial transactions If the transaction name is not entered on this screen, please create one for CABA. Only one is necessary, these are SAP Retail specific rather than site or profile specific. © SAP AG
C
IRT360
5-83
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Now, also in the Inbound section of the IMG, select Transaction type-dependent control of financial transactions Select New entries. Enter the following details: Profile /trans
item
G/L Acct
Posting Key
IM## / CABA
1
110000
40
IM## / CABA
2
100009
50
Select Save and back out 12-3
Simulate the inbound processing of a cash-to-bank deposit of 173712 USD by your store, TS## using the path: Logistics → Retailing→ Distributed Retailing → POS interface → Extras → Simulation double-click Financial Transactions Enter the following data in the header area:
Field Name
Values
Customer
TS##
Reference No.
IRT360-##
Transaction type
CABA
On the item level, enter: Field Name
Values
Item
1
Acc. Assgnnt Obj
Blank
Cost center
Blank
Amount
173712
Crcy
USD
Assignment
Line 1
Press Save. 12-3-1 To verify the result of the simulation, select IDoc status. If there were no errors press POS monitor, view your IDoc. 12-3-2 To display G/L account document in the case of FI transactions, use this path: Accounting → Financial accounting → General ledger → Document double-click Display Items as expected. © SAP AG
C
IRT360
5-84
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study –Inbound Documents
Solutions
Unit: Merchandise Management System Case Study –Inbound Documents Topic: Inbound Aggregated Sales and Payment List Customizing and Simulation 13-1
To simulate inbound processing of aggregated sales, message type WPUUMS must be maintained and for payments lists, message type WPUTAB must be maintained in the EDI partner profile with the test flag set. Use the following path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modeling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc → Partner Profile Expand Partner type KU. Select your site TS##. Scroll down to display Inbound parameters and press Create Inbound parameters. The message type and process code are: Field Name or Data Type
Values
Message Type
WPUUMS (aggregated sales) WPUTAB
Process code
WPUU (aggregated sales) WPUT
13-2
Test
Check
Trigger immediately
Check
Configure inbound processing of aggregated sales data Copy the settings maintained for inbound profile IM00 or SAPD, if IM00 is not available. Use the following path to maintain control of Aggregated sales: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Aggregated sales control 13-2-1 To eliminate replenishment based inventory updating, deselect field Update rep.-based IM on the Aggregated sales control-screen.
© SAP AG
C
IRT360
5-85
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
13-3
Use the following path to maintain control of Payment lists: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Payment list control Copy the settings maintained for inbound profile IM00 or SAPD, if IM00 is not available. Modify it so that the Calculation schema is POSUSJ.
13-4
Simulate the inbound processing of aggregated sales data from your store of 2 pieces of article R100016 for a total sales value of $392, which included a complaint discount of $6. Logistics → Retailing→ Distributed retailing → POS interface → Extras → Simulation double-click Sales Enter your store number, TS## and accept today’s date. Select Aggregated sales to access the item level.
Field Name
Values
Wahrung (Currency)
USD
Qual
ARTN
Number
R100016
Sales qty
2
Sales value
392
Select Edit → Item discount Field Name
Values
CTyp
RB10
Sales discount
6
Press Save. 13-4-1 Select IDoc status to verify the result of the simulation. With a status of 53, Application document posted, select POS monitor to view the resulting documents. Two documents are created, a Billing document and an Article document. 13-4-2 Double click the Article document, select Accounting and you will see the inventory postings, to relieve Inventory and increase Cost of goods. 13-4-3 Double click on the Billing document, select Accounting, to display the document choices. 13-4-4 Double clicking on each of the document types, displays the detail information associated with each document type.
© SAP AG
C
IRT360
5-86
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
13-4-5 In addition to accessing these documents through the POS monitor, you also can use the following paths to access them through the components. To display article documents: Logistics → Retailing→ Merchandise logistics → Inventory management → Article document double-click Display To display billing documents: Logistics → Retailing→ Sales → Billing → Billing document double-click Display To display G/L account document: Accounting → Financial accounting → General ledger→Document double-click Display To display open line items in a customer account: Accounting → Financial accounting → Accounts receivable → Account double-click Display/change line items Enter Customer = TS## (the customer associated with your site), Company code = R300, and select field Open items 13-5
Simulate the inbound processing of the associated payment list data from your store, TS##. You want to record total check sales value of $392. Logistics → Retailing→ Distributed retailing → POS interface → Extras → Simulation double-click Sales Enter your store, TS## and select Means of payment. Enter 151 (by check) for payment method and 392 for Final total and USD, the target currency. 13-5-1 Select IDoc status to verify the result of the simulation. With a status of 53, Application document posted, select POS monitor to view the resulting document. Only one document is created, a Billing document.
© SAP AG
C
IRT360
5-87
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Merchandise Management System Case Study – Inbound Documents
Solutions
Unit: Merchandise Management System Case Study – Inbound Documents Topic: Inbound Cashier Statistics Simulation 14-1
To simulate inbound processing of cashier statistics, message type WPUKSR must be maintained in the EDI partner profile with the test flag set. Use the path: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) → Modeling and Implementing Business Processes → Partner Profiles and Time of Processing → Maintain Partner Profile Manually or Tools → Business communication→ IDoc → Partner Profile Expand Partner type KU. Select your site TS##. Scroll down to display Inbound parameters and press Create Inbound parameters. The message type and process code are: Field Name or Data Type
Values
Message Type
WPUKSR
Process code
WPUK
Test
Check
Trigger immediately
Check
Reminder: No specialized customizing is required for inbound processing of Cashier Statistic. However, the Information Structure must be active.
14-2
© SAP AG
C
Simulate the inbound processing of cashier statistics data, uploaded from your store, TS##.
IRT360
5-88
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
14-2-1 Use the following path: Logistics → Retailing→ Distributed retailing → POS interface → Extras → Simulation double-click Sales Enter your store, TS## accept today’s date and press Cashier statistics. On the simulation screen, leave the update group blank and the system defaults 800. Enter USD in Target currency. Field Name or Data Type
Values
Cashier
Group ##
Condition type
RB10
Number of conditions
1
Amount
6
Value canceled transactions
200
No. terminations
4
Sales
392
14-2-2 Verify the result of the simulation first by selecting IDoc status to determine if the simulation worked error free. Then, take the following path to Cashier standard analysis: Logistics → Retailing→ Info system/Planning → Retailing → Standard analyses → Special processes → Sales audit double-click Cashier 14-3
To find which info structure is updated by the upload of cashier statistics by a store. On the initial list generated by the Cashier standard analysis, select Goto → Other info struct... Note the structure S122
14-4
To determine the characteristics of this info structure. On the initial list generated by the Cashier standard analysis, select Extras → Disp. std drilldown. You will see the answer: Sales district, Site, Cashier number, Condition type, and Date.
© SAP AG
C
IRT360
5-89
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
14-5
What are the key figures of this info structure? On the initial list generated by the Cashier standard analysis, select Edit → Choose key figures...
14-6
© SAP AG
C
These two reports capture the data sent by the store that has been captured by the POS system in the store. Depending on the system, every key press at the register is captured by the store system providing the sales auditor with valuable loss prevention information.
IRT360
5-90
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit Reporting
Contents: Sales Audit Process Sales Audit Postings to R/3 Applications A Day in the Life of the Sales Auditor…
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
6-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Objectives
At the conclusion of this unit, you will be able to:
Describe the Sales Audit Processing steps Explain which R/3 applications are affected by Sales Audit Describe the tasks of a sales auditor using SAP Retail
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
6-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Unit 1 Introduction Unit 2 Technical Aspects of POS
Unit 3 Mapping Store Systems to SAP Retail Unit 4 Simple POS System Case Study Unit 5 Merchandise Management System Case Study
Unit 6 Sales Audit Reporting Unit 7 Performance Issues
Unit 8 Conclusion SAP AG 2001
© SAP AG
C
IRT360
6-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Inbound Processing: Data Flow
EDIDC
Database Server
EDIDS EDID4
6
4 5
Application Server LAN
IDoc IDoc file file
> startrfc R/3 Applications
3
1
directory = /.../.../... file name = ...
IDoc 2 file 22
POS-Converter WAN POS data SAP AG 2001
We described the flow of data inbound in the unit, Technical Aspects of POS. At this time, we focus on the movement of data from the original database files to the applications and to the SAP BW Information Structures.
© SAP AG
C
IRT360
6-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit: Process Steps
I n b o u n d
P r o c e s s I n g
POS M o n I t o r
1 4 A
System receives data from POS Converter in IDoc format Store IDoc in R/3 database Process Sales Audit data
Create error messages C for POS Monitor
No
Success? B
Yes
User analyzes and fixes the problems D
J E
Post data to different modules 6
F Initiate reversal of transaction
User can check the posting No
Ok? G
Yes
E H
Repeat processing of unprocessed transactions
SAP AG 2001
Step A - The IDoc interface calls Sales Audit Processing, either directly after the POS converter triggered R/3. Details of this step are explained in the next slide. However, processing means to verify the data in one IDoc, prepare it for posting, and posting it. Step B - the system checks the success of posting and posts the successful transactions of the IDoc (step 6) for those transactions that are in error, the system creates a message in the error log (step C). Step D - You can track the error messages and fix them through the POS monitor. Step 6 - When step B is successful, the document flow is also posted. The document flow reports the documents that are created in SAP Retail by store and transaction. Step G - Although Sales Audit processing should normally detect all possible problems automatically, when you are testing it is a good idea to do some manual checking and when all the IDocs are processed to run RIS and exception reports. Use the display function in the POS monitor to view the follow-on billing and article documents for individual transactions. When ready to test SAP Retail with SAP BW, deactivate RIS and use a similar process reviewing your reports in SAP BW.
© SAP AG
C
IRT360
6-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit Step A in Detail
Preprocessor handling (supplied and customer) A.1 A.2
Prepare documents for posting
Call User-Exit for document modifications A.3 A.4 A.6
Yes Errors? Write log messages A.5 No
Post the different documents
Do for each transaction
Yes Write log messages Errors? A.7 No A.8 A.9
Post the document flow Call Customer postprocessor
A.10 SAP AG 2001
Step A.1 - Customer preprocessing handling is described in detail in the next slide. Step A.2 - When Customer preprocessing is complete, Sales Audit Processing prepares the data for posting to the follow-on functions. Step A.3 - A second user exit is called. If it is active, the data prepared for the follow-on functions is passed to it and the posting controlled by the exit. Step A.4 - Sales Audit checks if the User Exit has created an error or rejected the current transaction. Step A.5 - Log errors to the POS monitor that were identified in step A.4. Step A.6 - Pass error free transactions to follow-on functions that handle posting to the R/3 database. Step A.7 - Sales Audit Processing checks if the follow-on functions created errors for the current transaction. Step A.8 - Log errors to the POS monitor that were identified in step A.7 Step A.9 - Follow-on processing returns the number of the created document to Sales Audit Processing. Sales Audit assigns this number to the current transaction number and posts the information as document flow to the database which can be displayed in the POS monitor. Step A.10 - When the IDoc is completely processed, Sales Audit calls the Post Processor User Exit. If one is available, it can be set up to trigger functions that you would like performed after IDoc processing is complete.
© SAP AG
C
IRT360
6-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit Step A.1 in Detail A.1.1 Call preprocessor
A.1.2
Messages Yes raised?
Create log messages for POS Monitor
A.1.3
No A.1.4
IDoc modified?
A.1.6 Yes
No
Yes Change log required? A.1.5 No Update IDoc database
A.1.8
Reject IDoc? No
Yes
Log rejection for POS Monitor and exit
Log changes for POS Monitor
A.1.7
A.1.9
SAP AG 2001
The customer preprocessor is an optional User Exit that can be maintained to check the contents of IDocs. The contents of the preprocessor are customer specific. However, if the preprocessor determines problems it must be capable of passing error messages back to Sales Audit. Step A.1.2 - Sales Audit checks for error messages and saves them to a database where they can be displayed later in the POS monitor. Step A.1.4 - Sales Audit checks if the IDoc was corrected by the preprocessor and if a change log is required. If a change log is required, it is recorded in step A.1.6. Step A.1.7 - Sales Audit copies any modified IDocs to maintain the original data and posts the changes to the IDoc database. Step A.1.8 - Sales Audit checks if the preprocessor rejected the entire IDoc. If it did, Sales Audit creates a log entry for the POS monitor and stops the processing of that IDoc. When Sales Audit has completed checking the results of the customer preprocessor, it passes the IDoc to step A.2, as shown in the previous slide.
© SAP AG
C
IRT360
6-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit: Data Flow (1/2)
Extraction structures
IDocs
Communication structures
Sales
MCPOSREC
MC44RB0REC
MCPOSCAS
MC43RK0CAS
WPUBON (WPUUMS)
Cashier statistics WPUKSR SAP AG 2001
The Sales Audit process also puts the data from the IDocs into Communication structures. These structures are the gateway between the application that provides the data and SAP BW. The message types that update Sales Audit are: - Sales as per receipt (WPUBON - Compressed Sales (WPUUMS) fields not available in this message type are left blank in the communication structure - Cashier statistics (WPUKSR) These structures have a user include where customer enhancements can be placed. The fields must be filled by user exit data either from the IDoc or added directly to the communication structure. The data is moved to their respective extraction structures before being moved to SAP BW.
© SAP AG
C
IRT360
6-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit: Data Flow (2/2)
InfoSource
Update rules
InfoCubes
SAP BW 0RT_C07 Receipts
2LIS_44_POSREC
0RT_C08 POS Monitoring
2LIS_43_POSCAS 0RT_C06 Cashier
SAP AG 2001
The data is transferred to the InfoSource structures, which are the metadata describing extract structures. Update rules control how the data is stored in the Infocubes. The above noted Infocubes are delivered with the Business Information Warehouse and queries provide access to necessary Sales Audit data. Additional stand-alone InfoObjects can be defined in BW during implementation, if you find them necessary.
© SAP AG
C
IRT360
6-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Market Basket Info: Data Flow
InfoSource
Update rules
InfoCubes 0RT_C30 Receipts
2LIS_44_POSREC
0RT_C31 Receipt /Article
SAP AG 2001
Similarly, the receipt data from the POS interface is delivered to the Market Basket Analysis Infocubes.
© SAP AG
C
IRT360
6-10
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit Postings to R/3 Applications (1/3) Follow-on Functions SD
Billing
Cost Center Acctng
CO
Profitability Analysis Profit Center Acctng Replenishment WPUBON01 WPUUMS01
MM Sales/Returns Goods Receipts Other Gds Mvmnts.
FI Stock Ledger G/L Accounts Accounts receivable Credit Card Proc. Accounts payable
various
BW
0RT_C07 0RT_C30 0RT_C31 SAP AG 2001
An example of Sales Audit posting to R/3 modules is that of Sales, IDoc types, WPUBON01 and WPUUMS01. As shown, the IDoc can update Billing, Replenishment, Inventory Management, and SAP BW. Billing is called for each sales transaction to: - determine additional figures such as prices and discounts - calculate additional figures - prepare posting to financial accounting - calculate sales taxes or process those - manage credit card data and prepare it for further 3,9,that are provided by another system processing in FI and credit card settlement - provide follow-on functions with the necessary figures MM, Inventory Management can be supplied with Sales Audit data and also automatically updates the stock ledger. Also, Cost Center Accounting can be posted automatically. Updates to financial accounting are triggered automatically by inventory management and billing. Inventory management provides the stock ledger with goods movements and billing provides the following account types: General Ledger and Accounts Receivable. The BW structures, 0RT_C07, 0RT_C30, and 0RT_C31 are posted directly by the IDoc whereas other information structures are posted by the individual applications as shown.
© SAP AG
C
IRT360
6-11
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit Postings to R/3 Applications (2/3) Follow-on Functions SD
Billing
CO Cost Center Acctng Profitability Analysis Profit Center Acctng
Replenishment MM
Sales/Returns Goods Receipts
Other Goods Mvmnts.
FI Stock Ledger G/L Accounts Accounts receivable Credit Card Proc. Accounts payable BW various
WPUKSR01
0RT_C06
SAP AG 2001
The Cashier Statistics inbound message, IDoc type WPUKSR01, updates only the BW structure.
© SAP AG
C
IRT360
6-12
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit Postings to R/3 Applications (3/3)
WPUFIB01
SD
Billing
CO Cost Center Acctng Profitability Analysis Profit Center Acctng
Replenishment MM
Sales/Returns Goods Receipts
Other Goods Mvmnts.
FI Stock Ledger G/L Accounts Accounts receivable Credit Card Proc. Accounts payable BW
0FIGL_C01 0FIAR 0FIAP SAP AG 2001
In the case of the Financial Transactions, the posting is directly to the Finance component and no data is recorded directly in the BW. The finance component, however, feeds several Infocubes.
© SAP AG
C
IRT360
6-13
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
A Day in the life…: Topic Objectives
At the conclusion of this topic, you will be able to: Describe the daily tasks of a Sale Auditor in SAP Retail
SAP AG 2001
© SAP AG
C
IRT360
6-14
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
A Day in the Life...
1. POS Monitor Communication Complete? Research Errors Edit Errors 2. Business Information Warehouse Review daily reports
IDES IDESSmart SmartRetailer RetailerInc. Inc.
SAP AG 2001
Course Case Study Wrap-up: - The Smart Retailer project team has installed SAP Retail and SAP BW, their work is completed. - Now, the Sales Audit business group takes ownership to perform the day to day operation of POS.
© SAP AG
C
IRT360
6-15
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
POS Monitor: Communication Completeness
Completeness check on POS inbound
SAP Retail
Partner R310
?
Date 12/31/00-1/5/01 Partner number R317, R316
Store M
M
R317 SAP AG 2001
Store M
M
Message Category
OK
Error
ORDERS 5 WGSREQ 3 R316 ORDERS 5 WPUBON 0 WPUUMS 15 Partners with complete transfer Partners with incomplete transfer Total partners . . .
Sum
1 0 1 0 1
6 3 6 0 16 1 1 2
EDI EDI partner partner profile: profile: inbound inbound Partner number Type Message EDI partner profile: inbound Partner number Type Message Type Type R152 KU ORDERS R152 KU ORDERS Partner number Type Message Type WPUBON WPUBON R316 KU ORDERS WPUUMS WPUUMS R316 KU WPUBON R316 KU WPUUMS
R316
The sales auditor uses the POS monitor to ensure all stores have completed their inbound communication. Report variants limits the display to the messages and/or stores you are over seeing. Using this tool makes it easy to determine if a store’s sales data has been received at headquarters in a timely fashion. Also, an overview of errors directs the sales auditor to the location of IDocs in error so that they can be corrected and posted to the proper accounts.
© SAP AG
C
IRT360
6-16
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Correct and Reprocess Errors
IDES . Inc IDESSmart SmartRetailer RetailerInc. Inc.
Mass change
Change status
Process
Find Term Status
Only display hits Reason
Sto.. S R.. Tra.. Pmet Total
TranType
PMeth
Cashier POS.. Date Time
SAP AG 2001
If on examination, the sales auditor finds errors, she can quickly correct and reprocess them using the SAP Retail sales audit editing tool. When all IDocs are posted, SAP BW can be evaluated for further information.
© SAP AG
C
IRT360
6-17
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Sales Audit Processing: Unit Summary
You are now able to: Describe the Sales Audit Processing steps Explain which R/3 applications are affected by Sales Audit Describe the Communication and Information Structures Perform the tasks of a Sales Auditor
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
6-18
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Unit: Performance Issues
Contents: Archiving POS Documents Reorganizing Status files Reorganizing Change Pointer files
SAP AG 2001 SAP AG
© SAP AG
C
IRT360
7-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Objectives
At the end of this unit, you will be able to: Describe the reason for archiving POS created objects Create a variant and run the archiving programs Describe the reason behind change pointer reorganization Perform change pointer reorganization
SAP AG 1999 SAP AG
© SAP AG
C
IRT360
7-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Unit 1 Introduction Unit 2 Technical Aspects of POS
Unit 3 Mapping Store Systems to SAP Retail Unit 4 Simple POS System Case Study Unit 5 Merchandise Management System Case Study Unit 6 Sales Audit Reporting
Unit 7 Performance Issues Unit 8 Conclusion SAP AG 2001
© SAP AG
C
IRT360
7-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Main Business Scenario
You have gone live on SAP Retail and you have been communicating among headquarters and stores for a week. Now it is time to implement the performance measures that you have been planningsince the beginning of the project.
SAP AG 1999
© SAP AG
C
IRT360
7-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Archiving POS Documents
SAP Retail
Database
Archiving Object
Archive Files
SAP AG 2001
The IDocs in the SAP Retail database are not deleted automatically after data transfer. As noted earlier, the communication IDoc is deleted once it has been transferred to the database. Outbound IDoc files are deleted by the converter, once they are transferred to the converters database; and Inbound IDoc files are deleted by R/3 once they are transferred to the R/3 database. When a report is run that accesses the database, it will go through each IDoc to determine if it requires processing, thus slowing the process. To minimize the time, SAP recommends that database items created as a result of POS transfers be archived on a regular schedule, as noted in the following slide.
© SAP AG
C
IRT360
7-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Objects to Archive
Object and Description
When
IDOC - Fully processed IDocs
Older than 1 week
WORKITEM - Completed workitems
Older than 1 week
SD_VBRK - Billing documents
Older than 1 week
MM_MATBEL - Inventory documents
Older than 1 week
FI_DOCUMNT - Accounting documents
Older than 1 month
SAP AG 1999
In addition to the objects to be archived, the document flow displayed in the POS Monitor must be deleted using report RSWWWIDE. After this report is run, you can not display which applications were created during the POS upload. -
Note: this report also deletes the document flow for standard IDocs as well as for POS IDocs. For this reason, SAP recommends that you only delete document flow for uploads that are older than 3 months.
© SAP AG
C
IRT360
7-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Reorganizing Change Pointers
SAP Retail
Status Docs
Change Pointers
SAP AG 2001
The reorganization function (report RWDPOSSRS) is used to remove all unnecessary POS outbound status records, log records and IDocs from the system. - Note: This report is available through the POS outbound menu. When RWDPOSSRS is run, it also flags unnecessary change pointers for deletion. Once the change pointers are flagged, they can be deleted in the ALE layer by running report RBDCPCLR. Access to this report is through ALE Administration. SAP recommends that you reorganize change pointers weekly.
© SAP AG
C
IRT360
7-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP Performance Map SAPNet Alias: performancemarket and performancemap Released for customers and partners (free of charge) Central point of access for performance-related topics Divided up in line with the mySAP.com components (contains core and industry-specific areas, plus cross-component and technical blocks) Gives recommendations and suggestions, detailed information, documents and links, and a direct link to relevant notes and collective notes in OSS Continually updated and enhanced Available in English (some notes and details are translated into other languages)
SAP AG 2001
© SAP AG
C
IRT360
7-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Summary
SAP Retail provides the transaction SARA, the archiving tool, to make archiving a simple task. Through SARA one can archiveIDocs, Billing documents, Accounting Documents and most other documents created via POS Inbound processing. SAP Retail also provides several reports that delete unnecessary workitems and error messages. The change pointer reorganization report is provided to remove already processed change pointers. All these tools enhance performance.
SAP AG 1999 SAP AG
© SAP AG
C
IRT360
7-9
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Unit: Conclusion
You have heard what must be considered in planning communication between headquarters and stores. You have heard the transmission options supported by SAP Retail. You have heard what business information can be transmitted via the SAP Retail POS interface. You have successfully completed two case studies customizing and testing the POS Interface and related areas. You have reviewed the data that you created in the Information System.
SAP SAP AG AG 2001
© SAP AG
C
IRT360
8-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Course Overview Unit 1 Introduction Unit 2 Technical Aspects of POS
Unit 3 Mapping Store Systems to SAP Retail Unit 4 Simple POS System Case Study Unit 5 Merchandise Management System Case Study Unit 6 Sales Audit Reporting Unit 7 Performance Issues
Unit 8 Conclusion SAP AG 2001
© SAP AG
C
IRT360
8-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Reminder !!
Project Start
C
on s
id e
r
Go Live
on
fig
Ev
C
al ua
te
u at e Eval
Stress Tests
ur e
Test
SAP AG 2001
Planning is the key to smooth implementation of your SAP Retail communication project. First, consider and engage a certified communication interface partner or begin creating your own interface. Evaluate your data requirements, profile requirements, messages to send and receive, and your reporting needs. Then, configure SAP Retail. Test the outbound messages and evaluate the preliminary results. Simulate the inbound messages and evaluate the results. Repeat as necessary, until you have your desired results. Test data transmission through the converter both ways. Test using CATT tool to generate large quantities of data.
© SAP AG
C
IRT360
8-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
What Is YOUR Scenario? ice, e, Pr l c i t Ar /UPC EAN s$ Sale
Sales Master Data
Store M
Article, Price, EAN/UPC, Customer, Taxes
Merchandise Management
M
Simple POS System Store M
Sales $ and Q, Articles, Customers
IDES IDESSmart SmartRetailer RetailerInc. Inc.
Article, Price, EAN/UPC, Customer, Vendors,...
Human Resources
M
Intelligent POS System Store M
M
Purchasing Finance
Sales $ and Q, Articles, Customers, Inventory count...
Merchandise Management System
SAP AG 2001
How do you do business today? How will you do business going forward? It is up to you to decide!
© SAP AG
C
IRT360
8-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP Best Practices for Retail ...
... Offer you "Best Practice" configuration of mySAP.com Retail in a number of versions for the following sectors: • • • •
Fashion (including apparel, textiles, footwear) * Food (discounters, supermarkets, hypermarkets, convinience stores) * Wholesale (technical wholesale, mail order, Internet) ** Hardlines (specialists in building materials, electrical items, toys, and so on) **
... Are an implementation tool combining AcceleratedSAP (ASAP) and Preconfigured Systems (PCS), are free of charge, and can be installed in a day
* already available
** planned
SAP AG 2001
© SAP AG
C
IRT360
8-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
SAP Best Practices for Retail ...
... Provide help in every mySAP.com Retail implementation! ... The preconfigured development client reduces the project runtime. ... SAP Best Practices for Retail allow early prototyping in the implementation, which reduces problems later thanks to a systembased discussion in the Blueprint Workshops. ... They contain detailed documentation of the preconfigured processes including full integration with AcceleratedSAP. ...They enable you to set up a pared-down, functioning system in a short period of time and test live operations.
SAP AG 2001
© SAP AG
C
IRT360
8-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Summary
Implementing Headquarter-Store communication is an iterative process with many variables -- you have been through many iterations in this course. You are ready to begin planning for your POS Interface implementation.
AG 1999 SAP SAP AG
© SAP AG
C
IRT360
8-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Frequently-used Menu Paths Activity
Menu Path
Technical Aspects of POS: View IDoc documentation
Tools → Business Communication, IDoc → IDoc Basis → Documentation doubleclick IDoc types
Check the Logical System name
Tools → AcceleratedSAP → Customizing double-click Edit. Project → SAP Reference IMG Basis Components →Distribution (ALE) → Sending and Receiving Systems → Logical systems → Define Logical system
Check the Logical System client assignment
Tools → AcceleratedSAP → Customizing double-click Edit. Project → SAP Reference IMG Basis Components →Distribution (ALE) → Sending and Receiving Systems → Logical systems→Assign Client to Logical system
Create an EDI port through IMG
Tools → AcceleratedSAP → Customizing double-click Edit. Project → SAP Reference IMG Basis Components →Distribution (ALE) → Sending and Receiving Systems→ Systems in Network →Asynchronous Processing →Assigning ports → Define port
Create an EDI port through SAP Easy Access
Tools → Business communication, IDoc double-click Port Definition
Create an EDI Partner Profile through IMG
Tools → AcceleratedSAP → Customizing double-click Edit. Project → SAP Reference IMG Basis Components →Distribution (ALE) → Modeling and Implementing Business Processes → Partner Profiles and Time
of Processing →Maintain Partner Profile Manually
Create an EDI Partner Profile through SAP Easy Access
© SAP AG
C
Tools → Business communication, IDoc double-click Partner Profile
IRT360
9-1
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Activity
Menu Path
Creating a Conversion Category: Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG
Define the Conversion Category Name
Sales and Distribution → POS Interface → Adjustments → Conversions → Conversion Categories.
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG
Select parameters to convert
Sales and Distribution → POS Interface → Adjustments → Conversions → Conversion parameters.
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG
Define parameter pairs
Sales and Distribution → POS Interface → Adjustments → Conversions → Select each type of conversion necessary
Activity
Menu Path
Simple POS System Case Study: Check if Change Message is active
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) →Modelling and Implementing Business Processes→ Master Data Distribution→ Replication of Modified Data → Activate Change Pointers (Generally)
Check if a particular message type is active
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components →Distribution (ALE) →Modelling and Implementing Business Processes→ Master Data Distribution→ Replication of Modified Data → Activate Change Pointers for Message Types
Maintain a Condition Type Group © SAP AG
C
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG IRT360
9-2
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Activity
Menu Path Sales and Distribution →POS Interface → Outbound → Maintain condition type group
Maintain a POS Outbound Profile
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Outbound → Maintain Profile for POS Outbound
Assign Profile to Site
Logistics →Retailing → Master Data → Site Data → Site double-click Change, select POS tab
Initialize Outbound Messages
Logistics →Retailing → Distributed. Retailing → POS Interface→ Outbound → POS data double-click Initialization
Verify success of initialization
IDoc Status → POS Monitor
View POS Directory
Transaction code AL11
Create an inbound profile
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface
→ Inbound → Maintain profile for POS inbound
Assign profile to site
Logistics →Retailing → Master Data → Site Data → Site double-click Change, select POS tab
Configure Goods Movement Controls
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface
→ Inbound → Movement type-
Dependent Control of Goods Movements
Configure Sales as per Receipt Controls
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface
→ Inbound → Control sales as per receipts
Define Sales as per Receipt transaction type
© SAP AG
C
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG IRT360
9-3
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Activity
Menu Path Sales and Distribution → POS Interface → Inbound → Transaction types for sales as per receipts
Configure specific transaction Sales as per Receipt
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution → POS Interface → Inbound → Transaction type-
dependent control of sales as per receipts
Simulate Sales as per Receipt inbound data
Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Sales, select Sales as per recpts
Verify IDoc through simulation tool
IDoc Status → POS Monitor
POS Monitor through SAP Easy Access
Logistics →Retailing → Distributed. Retailing → POS Interface→Monitor double-click POS interface
Display article documents
Logistics →Retailing → Merchandise. logistics → Inventory management → Article document double-click Display
Display billing documents
Logistics →Retailing →Sales → Billing → Billing document double-click Display
Display G/L account document
Accounting → Financial accounting → General ledger → Document double-click Display/change line items
Display open line items in a customer account
Accounting → Financial accounting → Accounts receivable → Account doubleclick Display line items
Simulate Cashier Statistics
Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Sales
View Sales Audit Reports
Logistics → Retailing→ Info system/Planning → Retailing → Standard analyses → Special processes → Sales audit double-click Cashier/POS Balancing/Sales
View Sales Audit Reports through POS area
Logistics →Retailing → Distributed. Retailing → POS Interface→ Environment →Sales Audit double –click Loss prevention/ POS Balancing / Sales
© SAP AG
C
IRT360
9-4
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Activity
Menu Path
Merchandise Management System Case Study: Check Port definition
Tools → Business communication, IDoc double-click Port Definition
Maintain EDI Partner Profile
Tools → Business communication→ IDoc double-click Partner Profile
Create Assortment List Profile
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Logistics - General → Assortment → Assortment List → Maintain profile for assortment lists
Assign Profile to site
Logistics →Retailing → Master Data → Site Data → Site double-click Change.
Initialize Assortment List
Logistics →Retailing → Master Data → Assortment/Listing → Assortment List → Generate double-click Initialization
Verify success of initialization
Logistics →Retailing → Distributed. Retailing → POS Interface→Monitor double-click POS interface
Create a Reduced Message Type
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Basis Components → Distribution (ALE) → Modeling and Implementing Business Processes → Master Data Distribution → Scope of Data for Distribution → Message Reduction → Create Reduced Message Type
Create an Inbound POS Profile
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Maintain profile for POS inbound→ Maintain profile for POS inbound
Assign POS Profile to Site
Logistics →Retailing → Master Data → Site Data → Site double-click Change, select POS tab
Maintain EDI Partner Profile
Tools → Business communication→ IDoc double-click Partner Profile
Maintain POS Store Physical Inventory controls
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP
© SAP AG
C
IRT360
9-5
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Activity
Menu Path Reference IMG Sales and Distribution →POS Interface
→ Inbound →Store phys. inventory control
View Inventory
Logistics →Retailing → , Merchandise. logistics → Inventory management, Environment → Stock double-click Stock overview
Simulate Store Physical Inventory Count
Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Store physical inventory
View Inventory
Logistics →Retailing → Info System/Planning → Retailing → Standard Analyses → Article double-click Article
Post Inventory differences
Logistics →Retailing → Merchandise logistics → Physical inventory→Difference double-click Post
Maintain POS EAN/UPC change controls
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound →Automatic EAN/UPC Creation Control
Simulate an Article Master change
Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Master data
Maintain POS Store Order controls
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Store order control
Simulate a Store Order
Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Store order
View a Purchase Order
Logistics →Retailing → Purchasing → Purchase order→ Purchase order doubleclick Display
Maintain POS Goods Movement processing control
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface
© SAP AG
C
IRT360
9-6
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Activity
Menu Path → Inbound → POS Goods Movement control
Maintain POS Movement type-dependent Goods Movement control
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Movement typeDependent Control of Goods Movements
Simulate Goods movement data
Logistics →Retailing → Distributed. retailing → POS interface → Extras → Simulation double-click Goods movements
Create Financial Transaction types
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Transaction types for financial transactions
Maintain POS FI Transaction type-dependent controls
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface
→ Inbound → Transaction type-
dependent control of financial transactions
Simulate inbound Financial Transaction data
Logistics → Retailing→ Distributed Retailing → POS interface → Extras → Simulation double-click Financial Transactions
View General Ledger documents
Accounting → Financial accounting → General ledger → Document double-click Display
Maintain POS Aggregated Sales controls
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Aggregated sales control
Maintain POS Payment List controls
Tools → AcceleratedSAP → Customizing double-click Edit Project(SPRO) → SAP Reference IMG Sales and Distribution →POS Interface → Inbound → Payment list control
Simulate Aggregated Sales data © SAP AG
C
Logistics → Retailing→ Distributed retailing → POS interface → Extras → IRT360
9-7
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
Activity
Menu Path Simulation double-click Sales, select Aggregated Sales
Simulate Payment List data
Logistics → Retailing→ Distributed retailing → POS interface → Extras → Simulation double-click Sales, select Means of Payment
View Article Documents
Logistics → Retailing→ Merchandise logistics → Inventory management → Article document double-click Display
View Billing Documents
Logistics → Retailing→ Sales → Billing → Billing document double-click Display
View G/L Documents
Accounting → Financial accounting → General ledger→Document double-click Display
View Customer Account Line Items
Accounting → Financial accounting → Accounts receivable → Account doubleclick Display/change line items
Simulate Loss Prevention data
Logistics → Retailing→ Distributed retailing → POS interface → Extras → Simulation double-click Sales, select Cashier statistics
View Sales Audit Cashier Report
Logistics → Retailing→ Distributed retailing → POS interface → Environment→ Sales audit double-click Loss Prevention
View Sales Audit POS Balancing Report
Logistics → Retailing→ Distributed retailing → POS interface → Environment→ Sales audit double-click POS Balancing
View Sales Audit POS Sales Report
Logistics → Retailing→ Distributed retailing → POS interface → Environment→ Sales audit double-click Sales
View Sales Audit POS – Sales per article Report
Logistics → Retailing→ Distributed retailing → POS interface → Environment→ Sales audit double-click Sales per article
© SAP AG
C
IRT360
9-8
Contact for Buying Any SAP Module Materials:
[email protected] Visit: www.sapfans.co.nr
