IRT260 4.0 Instructor's Guide

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

R/3 System Instructor Guide Level 03 Barbara Peatie Horst Gerlach

IRT260- Retail Store Connection

Release 4.0 October 1998

October 1998

Page 1

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

Contents Page: SAP Contact(s)............................................................................................................3 Walldorf – Horst Gerlach.................................................................................................................... 3 Subsidiaries – Barbara Peatie............................................................................................................ 3

Revisions To Previous Instructor Guide..................................................................3 Course Details.............................................................................................................4 Duration............................................................................................................................................. 4 Three Days........................................................................................................................................ 4 Course Materials and other Materials (Training Manual)....................................................................4 Country-Specific Units........................................................................................................................ 4

Course Instructor Profiles.........................................................................................5 Level of Knowledge Required............................................................................................................ 5 Courses Recommended as Preparation............................................................................................ 5 Online Help Recommended as Preparation.......................................................................................5 Hints on Preparing This Course......................................................................................................... 5

Training System IRT client 800.................................................................................6 Data Required- Sites.......................................................................................................................... 6 User ID and Passwords for Course Participants................................................................................6 Preparation in the System.................................................................................................................. 6 Example ABAPs................................................................................................................................. 6 CATTs................................................................................................................................................ 6 Technical Hints................................................................................................................................... 6

Goals and Objectives.................................................................................................7 Course Structure and Flow........................................................................................7 Course Schedule.........................................................................................................8 Course Schedule:............................................................................................................................... 8 Day One............................................................................................................................................. 8

Unit: Introduction......................................................................................................10 Topic: The Relationships.................................................................................................................. 13 Topic: ALE, EDI, and POS..................................................................Error! Bookmark not defined. Topic: Technical Documentation....................................................................................................... 16 Topic: IDoc Monitoring...................................................................................................................... 18

October 1998

Page 2

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

SAP Contact(s) Walldorf – Horst Gerlach Subsidiaries – Barbara Peatie

Revisions To Previous Instructor Guide

October 1998

Page 3

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

Course Details Duration Three Days

Course Materials and other Materials (Training Manual) Country-Specific Units

October 1998

Page 4

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

Course Instructor Profiles Level of Knowledge Required Ideally, the instructor will have experience in the retail industry, good R/3 knowledge, and strong SAP Retail knowledge and POS system understanding. The course covers retail communications but touches on MM/SD, ALE, and EDI communications. Accounting and Calculation schema’s are discussed are is workflow briefly as a function of Inbound POS processing. Courses Recommended as Preparation  IRT110 and IRT120 provide information on the Retail MM/SD functionality. 

IRT250 provides information on the Retail configuration.



CA210 is an excellent source of EDI information.



CA910, although primarily ALE for distributed systems, provides ALE exposure.



BC600 provides an introduction to Workflow.

Online Help Recommended as Preparation IMG documentation for POS, ALE, and EDI. POS system documentation and F1 help. Hints on Preparing This Course Run through the exercises as outlined for the students and also through the demo’s in this guide. Warning: The demonstrations must be performed in order. Each succeeding step is predicated on the prior configuration being completed.

October 1998

Page 5

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

Training System IRT client 800, 801, 802, 803, 804 Data Required-

Company Code

R300

Sales Org

R300

Distribution Chnl

R1

Division

R1

Purchasing Org.

R300

Sites

R316 and TS##

Article

R100016 R100005 R100000

Customers

R3001, R3001

Vendor

R3001, R3002

Controlling Area

R300

Cost Center

R3110_001

Cost Element

410050

User ID and Passwords for Course Participants Use transaction ZUSERS to create users IRT260-01 through IRT260-nn password init. Copy IRT260 to create with the proper authorizations. Save them locked until you are ready for class. Use transaction PPOM and org structure 50012897. Drill down (Zentr. Org., Logistik/EDV) Assign holders (IRT260-01—nn) Preparation in the System Unlock users and run ZENQUEOFF Example ABAPs CATTs Technical Hints

October 1998

Page 6

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

Goals and Objectives Give participants the ability to configure the communications environment to use SAP Retail POS communication functionality.

Course Structure and Flow

October 1998

Page 7

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

Course Schedule Course Schedule: Day One Approximate Times

Content: Units and Topics

Activities: Instructor and Participant

20 minutes

House Keeping and Introductions

Participants describe their experience level and expectations of the course.

20 minutes

Introduction

40,000 foot view into all of POS including

60 minutes

Technical Grounding

Lecture and exercises

15 minutes

Break

6 hours

Headquarters to store (Outbound processes)

Lecture, Demo and Exercises

30 minutes

Review Day 1

Answer any questions and highlight the important points of Day 1

60 minutes

Headquarters to Store (Assortment List)

Lecture, Demo and Exercises

15 minutes

break

30 minutes

Inbound Overview

Lecture and Demo

60 minutes

Store Physical Inventory

Lecture, Demo and Exercises

60 minutes

Lunch

Lecture, Demo and Exercises

60 minutes

Article Master Data Changes

Lecture, Demo and Exercises

60 minutes

Financial Transactions

Lecture, Demo and Exercises

60 minutes

Cashier Statistics

Lecture, Demo and Exercises

60 minutes

Store Orders

Lecture, Demo and Exercises

60 minutes

Goods Movement

Lecture, Demo and Exercises

30 minutes

Review of Day 2

Answer any questions and highlight the important points of Day 2

60 minutes

Sales – Aggregated

Lecture, Demo and Exercises

Day 2

Day 3

Break 60 minutes

Sales – as per receipts

Lecture, Demo and Exercises

60 minutes

Review Cashier Statistics

Review Cashier Statistics now that the participants have generated transactions.

Lunch

October 1998

Page 8

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

30 minutes

Background Processes Overview

Lecture and Demo

30 minutes

Performance Enhancers

Lecture and Demo

15 minutes

Summary

Lecture

Additional notes:

October 1998

Page 9

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

Unit: Introduction 20 minutes

List of Topics in the Unit Main Business Scenario Project Plan Communication Scenarios Overview of Messages Putting the Unit in Context This is a high level overview of a POS implementation project. Discuss the two options for hardware configuration. These do not impact the rest of the class but lay the groundwork for how we structure the flow of information Objectives Identify the areas that must be considered Explain the transmission options Explain the transmission messages

Main Business Scenario Setting up a POS project team. Other teams in the company are working to customize other functional areas. POS crosses functional modules so how the others configure the MM, SD, and FI areas will impact the POS team. Also, testing the POS functions will test the completeness of the configuration and master data in MM, SD, and FI. We will use a general merchant as our example because that provides a view to the breadth of Retail functionality. We have multiple stores in 3 western US states that have two point-of-sale systems operating in the stores. The smaller stores have POS servers and the larger ones have a foreign merchandise management system serving their POS terminals. Replenishment planning is run for all stores and promotions for selected articles are run most weekends. Although you have a company credit card, you also have a policy of accepting other major credit cards as well as cash and checks.

October 1998

Page 10

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

Project Plan There are essentially four phases to a successful implementation: Consider the size of your organization, where your stores are located, and the kind of data headquarters requires from the stores. Discuss with other functional teams the data requirements and their goals. Note that the phases are not necessarily discrete steps that rigidly follow one another, and that during the course, as will be true during an implementation, we will step through all phases in small increments before we have the entire process together. Evaluate which tools you are going to use to achieve the teams goals. Configure the system to reflect the decisions made in phase 1 and phase 2. Test that the configuration performs as they expected. Considerations Discuss in some detail what they must consider at the project outset. The items that we consider up front must be kept in mind as we go through the other three steps. Throughout the course we will be evaluating, customizing, and testing. Transmission Options (1/2) Schematic showing the modes of connection to the store. Emphasize that an external converter is recommended. Two companies have certified interfaces, SiemonsNixdorf and IBM. Transmission Options (2/2) A second option is available. That is using the distributed mode where servers are physically in different locations and some modules run in these locations. Using multiple servers, reduces the number of records processed by any one system at any one time. We are just mentioning this option but will not discussed it in any detail. Although we have listed some items to consider, if you are considering this option. See CA910, the Application Link Enabling course. Outbound The slide shows the types of information that the POS interface handles. The information and message types are discussed in detail in a later unit and are presented as an overview. Inbound The slide shows the type of information that the POS interface can receive. Each type is discussed in detail when we discuss the Inbound processes. and are presented as an overview.

October 1998

Page 11

SAP AG

IRT260 Retail Store Connections SAP Contact(s)

Scenarios As a last consideration, you will want to consider where the center of control lies in your company and the types of POS systems that you have in the stores. As the slide shows in stores where you have very simple POS sytems you might only send an article message with pricing and the main UPC number. This would provide enough information for the POS server to capture sales and send them back to headquarters. As systems become more intelligent and have more memory, messages can become more complex, as the slide shows. Both control and POS systems will impact the types of messages you use and how often data is transferred. For example: If you will be performing auto-replenishment at headquarters, you must receive detailed sales data and the store must have accurate article data to provide the sales at the register. If stores maintain their own inventory, regular sales volume and store orders inbound might fulfill corporate reporting requirements and periodic inventory counts to substantiate the inventory. Summary The slide shows the type of information that the POS interface can receive. Each type is discussed in detail when we discuss the Inbound processes. and are presented as an overview.

October 1998

Page 12

Unit: Technical Grounding 45 minutes

List of Topics in the Unit Profiles Application Link Enabling Electronic Data Interchange Intermediate Documents POS Monitor Putting the Unit in Context We put aside the business aspects of the POS course for a short while and discuss some of the underlying system functionality provided in SAP Retail necessary for using the POS interface. We will be using these parts of the system as we go through the remaining units and will come back to these areas several times throughout the course.

Objectives Describe the use of profiles to populate data Explain the relationship among ALE, EDI, POS, and IDocs Describe the role of the ALE layer Explain the IDoc documentation and structure provided in the system Describe the POS monitor as a tool for interfacing with the IDocs. Topic: The Relationships Putting the Topic in Context No matter where we start there is always some piece of information that you might have had earlier. No matter where we start you might feel, “I wish I knew that sooner.” While I think we have started at the right point, this feeling might hold true throughout today. I will ask you to be patient and write down your questions as they come up, at the end of the day I will ask you for those questions that were not answered and will spend a few minutes discussing them before we leave for the day. This topic covers some of the underlying functionality that you will need to comprehend the later sections. Topic Objectives Identify all the pieces of the configuration puzzle that make up POS communications.

SAP AG

IRT260 Retail Store Connections Unit: Technical Grounding

Where do I start? Just a little swipe at the use of acronyms and at the outset it probably sounds like just a bowl of alphabet soup. The definitions on the notes pages are what is important in this slide. Describe the definitions.

How it all ties together This should be a build slide that begins with just the Site Master. Although we won’t populate these fields until last, it is important to know what we are building up to. You should all be familiar with the Site Master and the Customer number of the site master. Are you? How it all ties together 2 Add EDI Partner Profile that is unique to each site and/or customer. This is the key to moving the IDoc messages in and out of the system. It is linked to the site by way of the site customer number. We are going to discuss this briefly now and again in more detail when we come to the inbound and outbound sections of the course.

How it all ties together 3 Add ALE config. This is the key to moving the data to and from the application areas. We’ll cover this topic next.

How it all ties together 4 Add POS outbound profile. This packages the data appropriately and allows it to be sent to particular stores. The link is through the POS Outbound profile name entered into the site master and the customer number assigned to message types in EDI partner profile. Outbound profiles will be discussed at length later today. How it all ties together 5 Add POS inbound Profile. This is the key to packaging the inbound data and allow it to be handled by the system. The link is through the POS Inbound profile name entered into the site master and the customer number assigned to message types in EDI partner profile. Inbound profiles will be discussed at length beginning tomorrow.

October 1998

Page 14

SAP AG

IRT260 Retail Store Connections Unit: Technical Grounding

How it all ties together 6 Add the POS inbound Detail Profiles. At the detail level, each inbound profile “tells” the system what kind of data to expect and how to deal with it. The inbound profile details will also be discussed at length. How it all ties together 7 Add Calc schema. This is another piece of the link that we touch on but do not discuss in detail. It is a subject of a three day Pricing course and one with which other members of your team will deal. However, I bring it up to remind you that when you get to testing, the calculation schema is critical to getting transactions to post. How it all ties together 8 Add Assortment list profile. The assortment list profile is the way we handle this special message type. This is covered in detail after outbound profiles.

How it all ties together 9 Now we are back where we started with the focus on Sites with all the links to the profiles that will drive the data down and back from the stores with minimal input from an operator. Topic Objective ALE and EDI work together to deliver data out to the POS systems and in to R/3. Explain how the two work together to move data to and from the application to the converter.

Information Flow in POS Outbound The Application Link Enabling function of R/3 moves the data from the application area. The slide shows generally: folks working in the application areas make changes to master data, for example in a live system, a merchandise manager decides to mark-down a group of articles and does so in the system. The ALE layer creates a change pointer and a master IDoc that the POS interface converts to communication IDoc and tags it with the appropriate sites. Then the EDI interface passes the IDocs to the assigned port. After the IDoc is created, ALE places the location of the IDoc file in the status file. When the report is started, a message is sent to the converter/communication interface. The communication interface goes to the status file, finds the location of the files and downloads the data to the store.

October 1998

Page 15

SAP AG

IRT260 Retail Store Connections Unit: Technical Grounding

Information Flow in POS Inbound This will be covered in greater detail in the Inbound section of the class. It is sufficient to say at this point, that the data takes the reverse path into the system.

Topic: Technical Documentation Putting the Topic in Context Discussion of IDocs as the carrier of business data, how they are structured and what data they carry. Where to go to display the technical documentation. Technical Documentation Objectives Explain the concept and structure of IDocs Describe the database tables that store the components of individual IDocs Describe the classification of IDocs in terms of IDoc types Describe and show how to use the online IDoc documentation to determine the contents of an IDoc. IDocs and IDoc Types SAP provides over 100 basic IDoc types or structure into which the system places data. The POS interface uses 25 retail specific IDoc types and provides a facility for attaching customer data to the IDoc types .

IDocs: Components Each IDoc is made up of 1 Control record, at least one, but more likely, many data records. Inbound IDoc segments that are processed together are called a range and each range has a POS status describing the result of inbound processing, and determining if further processing may be required. The POS status is different from the EDI status. The EDI status is assigned to the entire IDoc. It also contains one or more IDoc status records that document the life cycle of the whole IDoc. The components are identified by a numerical key, the IDoc number and the client number through which all the records belonging to one IDoc are linked in the database. IDocs: Control Record See notes.

October 1998

Page 16

SAP AG

IRT260 Retail Store Connections Unit: Technical Grounding

IDocs: IDoc Types vs Message Type See notes. Also, Syntax means the systematic arrangement of the data Semantic means the contextual meaning IDocs: Data Records See notes.

IDocs: Data Record Structure See notes.

IDocs: Data Record Structure – Example (1/2) and (2/2) See notes.

IDocs: EDI Status Record See notes.

IDocs: EDI Status vs. POS Status See notes.

Break 10 minutes

Demonstration of IDoc Documentation 20 minutes Tools  Administration, Administration  Process Technology  IDocs Basis, Documentation  IDoc Types (WE60). Enter WP_PLU02 press Display Tree. Show the structure and the expansion to see segments. Back out

October 1998

Page 17

SAP AG

IRT260 Retail Store Connections Unit: Technical Grounding

WARNING: The following is only possible if you are able to save files locally on the trainer’s PC and to retrieve them, e.g. through the Windows NT Explorer using a (basic) text editor! Show the html documentation. Press Html, enter c:\ in Local directory and some other name in Basis name for HTML files with no extension. Go to Windows NT Explorer then double click on the _F.htm file and the browser will start. Show the three views. Now show the C header info. Press C header, enter c:\ in Local directory and a name in the local file w/o extension field. Go to Windows NT Explorer and double click on that file. Associate it with Notepad and display the “Automatic Data Declaration” which is the C format of the IDoc. Demonstration of the Database Files 15 minutes Tools  ABAP Workbench  Dictionary (SE11) In the Object field, Enter: EDIDC and press Display to access the Control record table. EDID4 and press Display to access the Data table EDIDS and press Display to access the Status record table Back out. Go to Overview  Data Browser (SE16) Enter EDID4 in the table name to view the data within the table. Exercise: IDoc Types 15 minutes 1-1, 1-2 Topic: IDoc Monitoring Putting the Topic in Context Introducing the POS Monitor. It documents the communication between the system and the converter at a finer level than does the EDI or ALE monitors. IDoc Monitoring: Objectives Explain how the POS Monitor documents communication between SAP Retail and point of sale systems. Show how to use the POS Monitor tools.

October 1998

Page 18

SAP AG

IRT260 Retail Store Connections Unit: Technical Grounding

POS Monitor: Embedding into POS interface The POS interface is made up of an Inbound processing unit, an outbound processing unit, and the POS monitor.

POS Monitor: Functional Scope See notes.

POS Monitor: Selection Criteria See notes.

POS Monitor: Tree Structure See notes.

POS Monitor: Functions Relating to Outbound See notes.

POS Monitor: Functions Relating to Inbound See notes.

POS Monitor: Communication Completeness See notes.

Demonstration of POS Monitor 15 minutes Follow Distr. Retailing  POS Interface, select ‘Monitor POS interf.’, blank out Creation time (from), and enter Customer = R311. Select Execute. On the next screen select ‘Expand subtree’, to expand POS Monitor tree. You will note that there are (store order) IDocs found. One successful and one unsuccessful.

October 1998

Page 19

SAP AG

IRT260 Retail Store Connections Unit: Technical Grounding

Display this IDoc (double-click) with its three components, as well as the follow-on document (= purchase order; double-click). Select ‘Complete area’ to call upon inbound completeness check, using Partner number = R311; select ‘Execute’ and explain/interpret result of completeness check. Exercise: POS Monitor 15 minutes 2-1, 2-2

October 1998

Page 20

Unit : Headquarters to Store (Outbound Processes) 360 minutes

List of Topics in the Unit Outbound IDoc/message types EDI partner profile for outbound processing Condition type groups Conversion categories POS outbound profile POS outbound reports Putting the Unit in Context Master data is required at the electronic cash register if sales data is to be recorded accurately and with detail. Outbound POS transmission of master data is the efficient way to get master data to the stores. For the process to work “automatically” and smoothly, several profiles must be created first for Outbound messages to be transferred seamlessly.

Objectives Describe the type of business information carried by outbound messages Deliver information that allows the students to understand and: Customize EDI Ports Customize EDI Outbound partner profiles Customize Condition Type groups for an implementation Customize Conversion category for an implementation Customize Conversion parameters for an implementation Customize POS Outbound profile for an implementation Topic: Outbound Messages Putting the Topic in Context First we will discuss the types of messages to carry the data out to the stores and go through each of the outbound IDoc message types. Then we will step through all the areas of configuration and set up my demo store to carry outbound messages. We will test sending a message, then you will get to do the same process for your own site.

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Topic Objectives Describe the Outbound messages to understand which one (s) you might want to use and why you might want to use them. Also, which ones you might want to combine for different stores.

POS Outbound: Business scenario The flow of data was discussed in the Technical Grounding unit. On a more general level, this slide depicts how the system handles the entire process of capturing master data changes and downloading them to the stores. In this unit we are concerned with the business uses of outbound data. 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, (such as changing a price, adding a new article) 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 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. As we discuss the message types, you will want to keep in mind our business scenario, as the message types we use will impact how we proceed: We are a general merchant with stores in 3 western US states using 2 different POS systems. Automatic replenishment planning is in place for all stores and we run promotions for selected articles on weekends. We do have an in-store credit card and also accept other major credit cards as well as cash and checks. Types of outbound business data Each of the message types is discussed in this unit as is the customizing that is necessary to ensure the smooth flow of information to the stores. List of the business data, IDoc type and Message type. We will look at the IDoc types one at a time.

October 1998

Page 22

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Outbound Processing: Data Flow The slide shows that the user intervenes in only two operations, the rest the system handles automatically. See notes for the process.

Inbound and Outbound Material and Condition IDoc WP_PLU02, WP_PLU The basic article data can be carried to the stores using message type WP_PLU. WP_PLU02 IDoc type is shown with all its segments. As was explained each segment has a number of fields. WP_PLU01 is still available in the system but it is supported only for the simplest of POS systems that were supported for release 1.2. Critical piece of information: The only message that carries Rebate in kind data is WP-PLU02, so if you do this kind of promotion you must use this IDoc and message type.

View the WP_PLU02 IDoc on line Rather than look at this IDoc on slides, lets look at it on-line. Tools  Administration  Administration  Process Technology  IDoc  IDoc Basis  Documentation IDoc Types. Enter WP_PLU02, press Display Tree E1WPA01, The Inbound and Outbound Identification segment is the only mandatory segment. An IDoc can contain 1 up to 9,999,999 ID segments. It contains the following fields: Site Change indicator Change category Activation date Date changed Employee number of the person who changed the article master record Main EAN/UPC number Internal article number Unit of measure E1WPA02, the Inbound and Outbound article master data is optional and only 1 record. It contains the following fields: Merchandise category Packaging weight Scales group Flag: Quantity entry prohibited

October 1998

Page 23

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Flag: Price must be entered Flag: Sales block Flag: Discounts allowed Flag: Article for weighing Flag: Price includes sales tax Flag: Price autonomy of store Flag: Print price Flag: Display article Minimum remaining shelf life Total shelf life in days POS interface: count request for articles. E1WPA03, the Inbound and Outbound article master text data is optional and an IDoc can contain 1 to 99 segments. It contains the following fields: Qualifier text Language code Text field E1WPA04, the Outbound Article conditions data is optional and can contain 1 to 99 segments. It contains the following fields: Type of condition/discount Promotion number Condition valid from Time of price activation (not active as yet) End of price validity Time of price deactivation Free for use (customer enhancement field) E1WPA05, Outbound article condition values data is optional can contain 1-99 segments. It contains the following fields: +/- sign of condition Condition rate, percentage conditions Amount Quantity Currency key E1WPA11, Outbound Condition scales data is optional and can contain 1-99 segments. It contains the following fields: Scale basis indicator +/- sign of condition Condition rate, percentage conditions Amount Quantity Amount The only message that carries Rebate in kind data is WP-PLU02, so if you do this kind of promotions you must use this IDoc and message type. E1WPA09, the Outbound free goods data is optional and can contain 1-99 segments. It contains the following fields: Type of condition/discount Condition valid from End of price validity Promotion

October 1998

Page 24

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Free goods: Indicator for on-top / inclusive E1WPA10, Outbound article free goods scale data is optional can contain 1-99 segments. It contains the following fields: Minimum free goods quantity Free Goods quantity Internal number of the discounted article Main EAN/UPC discounted article Additional quantity for free goods Unit of measure Calculation type for determining free goods quantity E1WPA07, the Inbound and Outbound article master tax data is optional and can contain 1-99 segments. It contains the following fields: Tax code E1WPA08, the Inbound and Outbound additional article number data is optional and can contain 1-99 segments. It contains the following fields: Qualifier article number Article E1WXX01, a customer enhancement segment that can contain 1 to 999 segments. Inbound and Outbound EAN/UPC Assignments WP_EAN01

WP_EAN

If you had articles that were sold under more than one UPC code, you would activate the WP_EAN message type as well as the Article master message. For example, if you sold apparel and changed UPC codes for store brand t-shirts from different manufacturers you might want to use this IDoc type You must activate both WP_EAN and WP_PLU message types and configure the store profile for both message types as well. Outbound Exchange Rates WPDCUR01 WPDCUR You would use this IDoc if you had international stores that do business in different local currencies from the company code currency and you require translation at the store level. Change pointer analysis is not performed so there is no need to activate the message type but you must configure the store EDI Partner profile. No change pointer analysis This message must be scheduled or activated manually Outbound Follow-on items WPDNAC01

WPDNAC

You would use this message type if you carry returnable beverage bottles or other returnable items attached to an article. If you are using this message type you must activate both WP_PLU, which activates change pointer analysis, and WPDNAC to send the IDoc.

October 1998

Page 25

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Outbound Merchandise Categories WPDWGR01 WPDWGR This might be used by a company that maintained their inventory on a value only basis and therefore did not require article data at the store with the detail of WP_PLU. Also some older POS systems can not handle recording on the article level and must use the Merchandise Category message type Outbound Taxes WPDTAX01 WPDTAX This is another message that must be set up and sent because it is assumed to be something that changes only periodically. No change pointer analysis This message must be scheduled or activated manually Outbound Set Assignments WPDSET WPDSET Use this IDoc if you sell individual items together as a set also.

Outbound Additionals WTADDI01

WTADDI

Additionals are labels, hangers and the like that are attached to an article.

Outbound Person Data IDoc WP_PER01 WP_PER WP_PER is being handled as a special case as we can reduce the IDoc in the ALE layer. We will discuss it in detail because it does have performance implications. This shows the major IDoc segments. Our scenario is that we have-store cards and we want to supply the POS with customer data. Demonstration of Reducing the WP_PER01 IDoc Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO)

October 1998

Page 26

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Activate Change Pointers: Customizing We begin by activating change pointers generally. That is what turns on the ALE functionality. Then we go to the screen similar to this for activating the message types. There is not a one-for-one relationship between the message types and change pointer analysis for system performance reasons. Multiple processing of the same change pointer for different message types means that separate change pointers do not have to be created for each message type. 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 WP_PLU

WPDSET

Set Assignments

WPDSET WP_PLU

WPDNAC

Follow-on items

WPDSET WP_PLU

WP_PER

Customer data

WP_PER

WPDTAX

Taxes

No change pointer analysis

WPDCUR

Exchange Rates

No change pointer analysis

Demonstration of Customizing Change Pointers Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO) Cross-Application Components Distribution (ALE) Master Data Distribution  Activate change pointers Activate change pointers (generally). Either select or note that this has been selected and so the ALE functionality is turned on. Back out. Select the next option  Activate change pointers for message types. Note that all message types are already displayed in this screen. These are all the message types supported by SAP. Our interest is in the POS message types so either page down several times to show the depth of support, or use position to W* to move directly to our message types.

October 1998

Page 27

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

POS Outbound: Change Analysis This slide takes us through the process the system goes through to determine which IDocs must be created. 1. Someone in merchandising changes the Selling Price (VKP0) of Generic Article R322228 at the Sales Organization level. The article is a rugby shirt that is a good back to school seller so the price is being increased to $35.00. 2. At the end of the day Report RWDPOSUP, Change message is started. (We will talk more about the reports at the end of this unit.) 3. The system checks for the stores that carry this article, it notes that R316 and R317 carry the shirt in variants 001 and 005. 4. Both stores have a two day lead time which falls within the preparation period. 5. The systems checks for other condition records that might have been created earlier during this run (access sequence). It finds that store R316 was treated differently because it is located in an upscale neighborhood and another price change to $37.50 was already prepared at the store level. Store R316 is ignored for this price change. 6. Now the system checks and finds that article R322228005 is active in store R317 from 8/16 through the end of the year and creates an IDoc with the price change for transmission. Break 10 minutes

How it all ties together: customizing The way we get the system to handle the change analysis is done during customizing. So lets look again at the links that tie the POS outbound profile to the site and to the other definitions that make communications possible. Discuss the slide. EDI Port (17 and 18) EDI provides the main connection with the translator/converter. The Port customizing identifies the path to the IDocs and status files. It also identifies the movement as an EDI transfer. The Status directory identifies the location of the trigger pointer files. Describe the addressing structure that is configured in the EDI Port. The files must be setup by a system admin prior to use. It is important that the directory is the one that the converter expects for outbound. Inbound must be what R/3 expects

October 1998

Page 28

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Ports and Profiles (19) A quick view of the link between port definition and EDI Partner Profile. Although we are not yet discussing Inbound messages at this point, I want you to note that the only location of the inbound Port for simulation is through the Outbound profile. The converter provides the Port during actual inbound transmissions. Demonstration of EDI Port 3 minutes Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO) Cross-Application Components  Distribution (ALE)  Communication  Manual Maintenance of Partner Profiles  Define Port Expand File and select POS_TEST. Edit  Copy Enter SAPIRT for the new name. Click continue. Select SAPIRT and press Change. *****WARNING**** Use the pswdf05 address ONLY during classes. DO NOT USE it for testing before the class. Clearing this file presents some problems. For testing purposes, USE \\pswdf052\pos\posout\ etc. and attach to this directory using Windows explorer to check your data. Select Outbound and change the port Directory to: \\pswdf050\sapmnt\trans\POS\POSout\ Press continue. Select Status and change the port Directory to: \\ pswdf050\sapmnt\trans\POS\POSstat\ Press continue Press Save and Back out. EDI Partner Profile – Initial Screen Partner number use the store Customer number R316. Partner type ‘KU’ for customer Partner class If you have created a grouping of stores you can enter the code in this field. Archv. Std. EDI, identifies that contracts and other documents exist. Partner status Must be active. However, you can create reference profiles and it that case you would use the status T. Telephony Only used in standard EDI with external customers or vendors. Receiver of Notifications Defaults from predefined PD-Org structure or from the user if no PD-org is defined for that user. All the information is used by the system for Workflow error handling. Typ(e) Identifies the kind of name to expect in the ID field. Options include,

October 1998

Page 29

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Workcenter, Job, Organization unit, Person, Position, User. Lang(uage) In which a message is to be issued. receiver for notification specifies whom the system should notify – a particular workcenter, a particular job (defined in PD-Org) etc.

EDI Partner Profile – Outbound Profile • Message type Corresponds to UN/EDIFACT business structure standards, except for POS message types and they are as close as possible. • Message code Not used in Retail, is a further separation of message types and is optional. • Message function Not used in Retail. Has to do with std transmission. • Outbound options Establishes how you wish communication to take place. Receiver port Enter the port filename you defined for POS communications. Transfer IDoc immed. or Collect IDocs Use Collect IDocs for Outbound messages. Start subsystem or Do not start subsystem Neither one of these is necessary. It was planned to be used but ALE handles it.  Basic IDoc type The SAP parameter that determines, via database table TEDE2, which function module is called to process the data communication. Can be used without additional coding for communication functions that are completed by data from the application.  Extension Customer enhancements to basic IDocs.  syntax check flag determines whether the syntax of the IDocs is checked. If checked, system stops processing if syntax error is incurred. If not, the IDoc is posted but it is flagged as having a syntax error. (You might want to check it while testing in a live system to have the IDoc stopped to determine any error locations, but once errors are corrected, leave this field blank during live processing so that you only deal with problem IDocs.)  Seg. Release in IDoc type is looking for a release version code. The current segment definition is used when this is blank. If the segment definition changes with a new release, the IDoc would also change. With a release number in this field, if a segment definition changes with a new release, the system will use the release definition defined by this release code.  receiver for notification same as prior screen. If you want a different agent for a particular message type, enter that information on the particular message screen.  EDI settings Communication settings.  EDI Standard SAP supports E, EDIFACT and X, ANSIX12, use the one that your converter accepts  Message type Optional, you can enter the EDIFACT or ANSIX12 message type that corresponds to the IDoc type you are using.  Version Optional, you can also enter the version is you are using the prior field.

Demonstration of EDI Partner profile 5 minutes Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO)

October 1998

Page 30

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Cross-Application Components  Distribution (ALE)  Communication  Manual Maintenance of Partner Profiles  Maintain partner profile Enter R316, and KU as partner type. Select Outbound parameters Message type : WP_PLU

IDoc type WP_PLU02

Receiver Port SAPIRT.

Exercise: Create Port and Outbound EDI Partner Profile for their site TS##. 15 minutes 3-1, 3-2 Maintain POS Condition Type group We must identify to the system the conditions that must be analyzed to download pricing info. The ones we have added to the slide are VKP0, the sales price, VKA0, a promotion price, and UTXJ, the tax condition types. These are outbound conditions. Demonstration of POS Condition Type group 5 minutes Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO) Sales and Distribution POS Interface  Outbound message processing  Maintain condition type group. Select New Entries. Type the name US01, and a description. Select Maintain POS cond. type group. Enter the following Condition types: VKP0, sales price VKA0, a promotion price UTXJ, the tax condition. These are standard SAP supplied condition types and are the ones that will take prices , promotion prices and taxes down to the stores. These are in the Calculation schema and will be analyzed for changes and downloaded by the outbound messages or the assortment list. Maintain Conversion Parameters: Customizing Before we get to this point, we should have a solid understanding of the codes necessary at the point of sale system and how they relate to R/3 codes. What message types we are downloading and uploading. Then we can create one (or

October 1998

Page 31

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

several) Conversion Category(s) and then go to this customizing screen to identify which parameters we will be converting. Suggest that for your implementation that you create a matrix for all transaction types, tender types, etc. to link SAP Codes with POS codes. Detail Conversion : Customizing For each conversion parameter we selected in the prior step, we must create a set of code pairs to facilitate the conversion. In actuality, the converter does the conversion, this set of screens allows us to maintain the link in one location, the R/3 system. The Condition type codes in the slide are for inbound processing. These are the condition types that pass the sales value of a receipt line to the pricing function in Billing. Demonstration of POS Conversion Categories group 5 minutes Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO) Sales and Distribution POS Interface  Standardized Data  Conversions  Conversion Categories. Select New Entries. Type in the name TR00 and a description. Press Save. Back Out. Select Conversion Parameters. SAPD comes up. Back out and select New Entries. Enter TR00 and select Convert Conditions and Payment methods. Press Save. Back Out. Now select Conversion POS condition types. As the slide showed we are going to map our R/3 POS condition types to the numerical code for our store system. Enter TR00 184 TR00 185 TR00 186 TR00 187 TR00 162 TR00 163

VKP0 PN10 VKA0 HB00 UTXJ STTX

What is not on the slide are the codes for the downloaded condition types which we will put in the system. . Maintain profile for POS outbound (1/3) Describe the fields as they are shown on the slide.

October 1998

Page 32

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Maintain profile for POS outbound (2/3) Describe the fields as they are shown on the slide.

Maintain profile for POS outbound (3/3) Describe the fields as they are shown on the slide. Note that these fields override the Activate message, and the EDI Partner profile. Remember that when you activate a message type for one store it is active for all stores. Therefore, if you do not want a particular message type to be prepared for a particular store or group of stores, checking these boxes takes precedence over the activate change message and EDI partner profile. Demonstration of POS Outbound Profile Configuration 5 minutes Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO) Sales and Distribution  POS Interface  Outbound message processing  Maintain profile for POS outbound. SAPD is the only Outbound profile, so it displays. Back out. Select New Entries. Enter OP00 and a description; Tr’s Outbound Profil. POS Category – We have not created any so we’ll leave it blank. Conversion Category – We will use the category we just created – TR00 Lead Time – Outbound must be at least 2 days. Exchange Rate type – enter Condition Type group – Use the category we just created – US00 Person Mastr Reduc. – We have not reduced our person master so we will leave this blank Status communic. OK – the system places a code in this field when communications is complete Flag Settings: These provide the tool to limit the work of the system. Since change pointers are either on or off, if one store uses a message the data would be prepared if you set the message in the EDI partner profile and left these settings blank. However, you can improve system efficiency by setting these flags to reflect the data you do want. Recipient determin – Leave blank this is only used when using direct ALE transfers. Error mode – Leave blank, this will stop outbound processing when the first error is encountered (You might want it set for testing, however.) If blank it will flag any errors and put them into the error log and complete the outbound process. EDI – Set this one to indicate that data is to be transferred by outbound messages. Sales allowed for all MC (merchandise categories) – Blank for the demo. If set you

October 1998

Page 33

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

can send all merchandise categories regardless of whether they are listed at a store or not. Do not prepare art. – Leave blank, if set article data is not prepared for download. No follow-on items – Leave blank, if you do not identify empties or other follow-on set it. Do not prepare sets – Leave blank, set if you do not want set data downloaded. No mer. catgy (merchandise category) data – Leave blank, set it if you do not want merch. Catgy data downloaded. (We will use this later when it is clear that the merchandise categories are set up wrong in our data.) No Exchange rates—leave blank Do not prepare taxes – leave blank No customer data – Leave blank

Demonstrate Assign POS Outbound Partner Profile to site R316 5 minutes Once created, the outbound profile must be assigned to the site. Use the path: Retail  Master data  Site, Site  Change. Enter R316 and press Enter. Select the move right arrow and select POS tab. Enter OP00 in POS outbound profile. Exercise: Check Message Types are Active and create POS Outbound Profile for their site TS##. 20 minutes 3-3, 3-4 Break 10 minutes

Background Processes: Topic Objectives We have completed all the set up for our outbound message WP_PLU. Now we can talk about how the system takes the information from the profiles and sets it up for the converter. Much of the Retail system processes can be handled automatically with little or no user intervention. Simply setting up background processes allows the system to handle the routine tasks. Outbound Report Processes These are the reports that the system uses to prepare Outbound message data. We can access these reports in two ways, through the function and also by setting up Background jobs.

October 1998

Page 34

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

How many of you know how to set up background jobs? unnecessary to go through the process.

If most do then it is

The first thing you must do for Change Pointer analysis to work is to initialize the data. That means you are going to send all data to your stores. Demonstration of Initialization 10 minutes Retail  Distr. Retailing  POS Interface Outbound  POS data  Initialization Enter Sales Org – R300 Distr. Chnl – R1 Store

- R316

At this point we can do a number of tasks: If we go to GoTo  Variant  Save as a variant. Do Save it for the next demo! We can save this to use later to set up our process in the background. We could kick it off as a background job from this screen, by accessing Program  Execute in background. We could also select Execute. Or we can start it by pressing execute. Which I am going to do given a single store with only 2 articles listed. When the process is complete Back out to where you can select the POS Monitor. The first time you execute an outbound assortment list, there are many errors and the message is stopped. Use the POS Monitor Demo below, to deal with the problems… present this in a positive light… this is what they will run into in an implementation and this is why it is a great tool begin using early on in an implementation process. Display the site once again in the POS Monitor. This time the IDoc should be in Processed. Double click on the POS line and the IDoc types display. Select WP_PLU02 and press Display data. Double click on segment E1WPA01 and the data displays. You can page through each segment, note the header info and the data. With the data displaying on one screen, go to your second screen and view the communication IDoc. Use transaction code AL11, page down, select DIR_TRANS, then select POS note your three subdirectories. View the POSout file and note the differences between looking at the file through the POS interface and through the communication IDoc. Show POSstat for the .trg file. It is simply the address of the IDoc file and it is placed there when the system has completed creating the IDoc file so that there is no chance for the converter to start transmitting an incomplete IDoc file.

Demo, POS Monitor POS Outbound – Not fully processed < 5 minutes>

October 1998

Page 35

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Retailing  Distr. Retailing  POS Interface  Monitor POS interface. Enter R316 in Customer and press process. Select Outbound processing, Processed. The first time there will be none. Select Not fully Processed. Expand the Site number and double click on POS line with the error message. Select the line with red highlights (as of 11/98 there are two, the Merchandise category IDoc and the Person data IDoc). Red indicates the most important errors. Select WPDWGR01 and press Display Log. Select the resulting line item and press Display message. A list of all the merchandise categories that are not properly maintained is displayed. Clearly, we should ask someone to correct the problems with these merchandise categories, and we would if we were in a different situation but I like to show how the system highlights the problems and so we leave this one in. If we now press Long text, detail about possible solutions display. Scroll down and display the link to material maintenance, which takes us directly to the Article master data selection screen. How will we proceed? Now that we know where the problems are we will by-pass them. Go to the Outbound profile, OP00 and select No follow-on item through No customer data, save your change and back out. Go to your second screen where the IDoc is displayed and back out. Resend the outbound message as above and follow through with that demo.

Scheduling Outbound Change Messages to Run in the Background System  Services  Jobs  Define Job Entry screen Job Name - enter a name you will understand and remember “Download Outbound Changes” Job Class - A for the highest priority it will run before all other lower priority jobs. In a live system, only an administrator may assign A or B priorities. Status – As we prepare the job it will be scheduled, as shown on the screen. It must however, be released by the background controller, before it will be run. Target Host – leave blank and the system will run the report on the server that has the lowest background workload at the starting time of the request. You can designate a specific host upon which to run the background jobs, if you wish. Select Start date : Note the options that one can use for the timing of a report. For example, if

October 1998

Page 36

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

you wanted to make sure that the Outbound processing only took place after some Mass merchandise background job, like massive price changes (Do we do that? Can someone give me an example???) For our demo we will use today’s date and set the time for the end of the day. We are also going to make this a periodic job. At home probably after close of business but for now daily at lunchtime. So select Periodic values and you can see that we could schedule any period from hourly to monthly. Save. Now press Steps to create the process to run. Press ABAP Program, enter RWDPOSUP for the name and variant that you created in the step above. . If you don’t put in a variant, the system makes you. Save and point out “Job POS Outbound changes has been created.” Now lets go to see if the job is released and set it so if it is not. System Services  Jobs  Job Overview Demo, Running an Outbound Change message in Background < minutes> Retail  Dist. Retailing  POS interface  Outbound Note at this point that we can run both Outbound and Assortment List from this menu  POS data  Change message We have the same menu picks for both Outbound and Assortment List. For this demo we will use the Outbound change message. Enter Sales Org – R300 Dist channel - R1 Store

- R316

Go to Program  Execute in Background Note the system message at the bottom of the screen: Background job was scheduled for program RWDPOSUP.

Outbound Change Message in Background This slide is a little misleading. Generally, I make a transparency and use the overhead to explain that on day 1the first price change goes down. Then I draw a similar bar from day 2-7 and point out that no message will go out because there are no changes. Now draw from day 3 to 8 , again no changes. On day 4-9 bar, no change. On day 5 the system will pick up the date change that takes effect day 8 and send it that night. Then on day 6, it will send no message to stores 1 and 2 because it knows that the change is already gone.

October 1998

Page 37

SAP AG

IRT260 Retail Store Connections Unit : Headquarters to Store (Outbound Processes)

Exercise to Initialize Message to store TS## 10 minutes 3-6, 3-7

5 minutes Just wrap-up the outbound

October 1998

Page 38

Unit 4: Headquarters to Store (Assortment List) 90 minutes

List of Topics in the Unit Assortment List message type Assortment List Profile Review as they relate to Assortment List

Activate Message Customize EDI Partner profile Customize Conversion category Customize Conversion parameters Customize Condition Type groups Customize Conversion parameters Putting the Unit in Context Using a single message to send data to a foreign merchandise management system allows the store to be the center of control. The Assortment List sent down from headquarters can contain as much or as little data as necessary to support store operation. Outbound POS transmission of the assortment list is the efficient way to get the assortment list to the stores, change pointer analysis provides the process to accomplish this. For the process to work “automatically” and smoothly, the assortment list profile must be created first for the Assortment List messages to be transferred seamlessly.

The assortment list message is simply a comprehensive Outbound IDoc type and message type. It should be used to send data to a foreign merchandise management system and POS servers that are large enough to handle the capacity of data that is sent. Objectives Describe the type of business information carried by the assortment list Deliver information that allows the students to understand and: Customize EDI Outbound partner profiles Customize Assortment List profile for an implementation

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

POS Outbound: Assortment List Business scenario The flow of data was discussed in the Technical Grounding unit. On a more general level, this slide depicts how the system handles the entire process of capturing master data changes and downloading them to the stores. In this unit we are concerned with the business uses of assortment list data. During initial startup report RWDBBINI is run to prepare all the necessary data for the first time and transfer it to the foreign merchandise management systems. This Initialization should be scheduled in the background and must complete successfully (status: Preparation OK) before change messages can be created. After initialization (a full version) is complete, whenever a user maintains master data, (such as a buyer changing an article, or a price, …) 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. RWDBBUPD, 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 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. Please also note that you can manually create an assortment list using RWDBBMAN. Path: RetailMaster DataAssortmentAssortment list Generate  Manual selection. As we discuss the message type, you will want to keep in mind our business scenario: We still are a general merchant with stores in 3 western US states using 2 different POS systems. Our larger stores have a foreign merchandise management system and are semi-autonomous, i.e. they order selected articles from local vendors. Automatic replenishment planning is in place for all stores and we run promotions for selected articles on weekends. We do have a company credit card and also accept other major credit cards as well as cash and checks. Assortment List You have all taken IRT110 and IRT120 where the Assortment List and the concept behind it were described in detail. At this point, you should know that an assortment list exists for each store regardless of whether you use the POS interface to communicate to the stores. If the store system is not large enough to handle the Assortment List data there are

October 1998

Page 40

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

ways to create the list without downloading it using POS. We will discuss that as we get into customizing. Assortment List Contents Discuss the contents of the slide, which shows the types of information that the assortment list contains.

POS Outbound : Assortment List This is just a visual representation of the slide before and contents discussion can be continued.. What is shows is that with the information sent down by headquarters, the store merchandise management system can function autonomously. Assortment List IDoc (7 and 8) WBBDLD02 This is a visual representation of what you will see in the IDoc documentation. Remember you go there through transaction code WEDI. Select Documentation and select IDoc types. We will alternate between this slide and the actual data from an initialization of a site. Activate Change Pointers: Customizing As with other Outbound message types, we will activate change pointers for our Assortment List message type, WBBDLD. Activate generally was already “turned On” for the previous outbound messages. Stay on this slide until demo is completed. Demo, Activate the message type 2 minutes Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO) Cross-Application Components Distribution (ALE) Master Data Distribution  Activate change pointers Activate change pointers (generally). Note that this has been selected and so the ALE functionality is turned on. Back out. Select the next option  Activate change pointers for message types. Note that all message types are already displayed in this screen. These are all the message types supported by SAP. Our interest is in the Assortment List message type so either page down several times to show the depth of support, or use position to W* to move directly to our message types.

October 1998

Page 41

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

Deselect the messages previously selected and select WBBDLD. POS Outbound: Creating an Assortment List This slide shows the process the system goes through to determine which Assortment lists to create.

Break 10 minutes This break depends upon lunch-time. If you have a longish review and an early lunch, this is a good time to break. If review went quickly, and you have a later lunch slot, wait until the exercise to take a break. How it all ties together: customizing Now lets look at the links that tie the Assortment List profile to the site and to the other definitions that make communications between disparate systems possible.

EDI Partner Profile This is a reminder slide. Like all other outbound messages, the Assortment List message type must be defined in the Site’s Outbound Partner Profile.

Demo, Add to the EDI Partner Profile Cross-Application Components  Distribution (ALE)  Communication  Manual Maintenance of Partner Profiles  Maintain partner profile Enter R316, and KU as partner type. Select Outbound parameters Message type : WBBDLD

IDoc type WBBDLD02

Receiver Port SAPIRT

Assortment List Type: Customizing We probably want to create different types of assortment lists following different rules. As the slide shows we have three different types of assortment lists. Our food type (F) has a shorter cycle, shorter lead time, and fewer change versions before a full version is generated. Lead time assort list, the time in days between creation of Assortment list message

October 1998

Page 42

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

and start date of validity. Cycle, change versions, the number of days between last message creation and a new assortment list change version. No. of Change versions, the number of change versions that are generated before a new full version is run. I shortened the food version because I believe that food is more volatile than the hardware or apparel industries. Is that true? POS Outbound: Assortment List Version Management How lead time and cycle time and versions work together making version management. We were creating our version rules when we created assortment types with their cycles. Now we can see the effect of what that means. When we talk about the reports we will go into this process again more deeply. Maintain profile for Assortment List (1/3) Assortment list type 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 – If you had Remote access in the stores, they could access and print at their store. You can view this on line using the path: Retail  Master data  Assortment, Assortment list  Display. after you have created an assortment list. 2 Send as message, do not save versions -- Once you’ve been live for a while and you have had consistent successful transmission this would save space. 3 Send as message and save versions 4 Do not save any version or send any message. .( use for printing or to generate status log) Condition Type Group We also need to tell the Assortment list which conditions must be prepared to send out to the stores. 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.

Maintain profile for Assortment List (2/3) 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

October 1998

Page 43

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

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. 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 Maintain profile for Assortment List (3/3) The last group of parameters are: 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. Demonstration of POS Condition Type group 5 minutes Review of Outbound, see notes there. Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO) Sales and Distribution POS Interface  Outbound message processing  Maintain condition type group. We’ll be using the same condition types so just view. Discussion of Conversion Parameters: Customizing 5 minutes Review of Outbound, see notes. Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO)

October 1998

Page 44

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

Sales and Distribution POS Interface  Standardized Data  Conversions  Conversion parameters Then view the conditions parameter screen reminding the students that the translation is created in the converter but we enter them here also.

Demonstration of Assortment List Type Configuration 5 minutes Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO) Logistics General  Assortment  Assortment List  Number ranges, status tracking First, view the number ranges. These are provided as you see them. If for some reason you wish to, you can change them. Logistics General  Assortment  Assortment List  Assortment List types Create a new AL type by copying one of the existing ones. Or, select New Entries and enter a type using: P as the list type for perishables; Training AL type; 2, lead time; 3 days for the cycle; and 10 no of change versions. Remind the students that the AL type is attached to the articles. Demonstration of Assortment List Profile Configuration Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG (SPRO) Logistics General  Assortment  Assortment List  Maintain profile for Assortment List Copy profile 0001 and name the new one AL00, When the system asks you whether to copy all the dependent entries or just the entry itself, copy all. Then select AL00 and Maintain assortment list profile parameters Select Assortment list type 1 and press the mag. Glass to view the contents. Back out and press Trash to delete AL type 1. Also trash AL type T for apparel. You might note that one AL profile, because of the different AL types, can handle several different groups of articles differently without creating many profiles.

October 1998

Page 45

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

Demonstrate Assign POS Assortment List Profile to site R316 5 minutes Once created, the outbound profile must be assigned to the site. Use the path: Retail  Master data  Site, Site  Change. Enter R316 and press Enter. Select the move right arrow and select POS tab. Enter AL00 in Assort. list profile. Exercise: Create and review all the necessary profiles and Assortment List Profile for their site TS##. 20 minutes 4-1, 4-2, 4-3, 4-4, 4-5 Break 10 minutes You only need this break if you didn’t take the earlier one. Demonstration of Assortment List Initialization 10 minutes Initialize the Assortment List for R316: Make sure that WBBDLD message type is active. RetailMaster dataAssortment  Assortment List Generate Initialization Sales organization – R300 Distribution channel R1 Customer

R316

Assortment list type F – H Before running this, go to Goto  Variant  Save as variant. Enter a name, description and Save. Execute You might want to talk a bit about the report that displays before you back out to view the POS monitor. Note there are two IDocs because there are two assortment list types. Each has an Outbound log, notes for customer the IDoc number with the number of segments and at the bottom there is a general log with the number of entries. Now back out to access the POS monitor.

October 1998

Page 46

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

Demo, POS Monitor Assortment List 3 minutes Retailing  Master data  Assortment  Environment  Assortment list  Monitor POS interface. Enter the site number in Customer and press process. Select Outbound processing, Processed. Expand the Site number and double click on the SL with the date you want. Select the line with the Assortment list, note the IDoc number and select Display Data. Explain here is an IDoc structure with multiple segments. Showing here is the structure now we will go into the structure and view the data that is going to be passed. Select E1WBB01. Discuss the screen. Note the header data Press the forward arrow to advance to the next segment. Go back to the first screen where the IDoc and all its segments is displayed. On the second session, use transaction AL11, page down, double click on DIR_TRANS, and double click on POS. Show the communication IDoc that you are already displaying and point out that this is ready to be picked up by the converter, if we had one. Back out to the POS monitor screen. Note the line for outbound messages communication and that the outbound messages we downloaded and the Assortment List doc we prepared are under Communication Incorrect that is because the converter has not picked them up. Background Processes: Topic Objectives We have completed all the set up for our outbound message WBBDLD. Now we can talk about how the system takes the information from the profiles and sets it up for the converter in a little more detail. Outbound Report Processes These are the reports that the system uses to prepare Outbound message data. We can access these reports in two ways, through the function and also by setting up Background jobs. How many of you know how to set up background jobs? unnecessary to go through this process.

If most do, then it is

The first thing you must do for Change Pointer analysis to work is to initialize the data. That means you are going to send all data to your stores. Scheduling the Assortment List to Run in the Background 5 minutes System  Services  Jobs  Define Job

October 1998

Page 47

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

Entry screen Job Name - enter a name you will understand and remember “Download Assortment Changes” Job Class - A for the highest priority it will run before all other lower priority jobs. In a live system, only an administrator may assign A or B priorities. Status – As we prepare the job it will be scheduled, as shown on the screen. It must however, be released by the background controller, before it will be run. Target Host – leave blank and the system will run the report on the server that has the lowest background workload at the starting time of the request. You can designate a specific host upon which to run the background jobs, if you wish. Select Start date : Note the options that one can use for the timing of a report. For example, if you wanted to make sure that the Outbound processing only took place after some Mass merchandise background job, you could set it up to run after that process is complete. For our demo we will use todays date and set the time for the end of day. We are also going to make this a periodic job. At home probably after close of business but for now just today for the end of day. So select Periodic values and you can see that we could schedule any period from hourly to monthly. Save. Now press Steps to create the process to run. Press ABAP Program, enter RWDBBUPD for the program name and in variant enter the one we created for the manual initialization above. Save and point out “Job Download Assortment changes has been created.” Now lets go to see if the job is released and set it so if it is not. System Services  Jobs  Job Overview Assortment List Messages in the Background Lead-time in the assortment list has a different meaning than it does in the outbound messages. As we talked about during version management, cycle is more like leadtime in outbound messages and lead-time is really just that. Looking at Store 5 on the slide. Day one, an assortment list is sent down to the store it contains a price change for day 4 and a promotion that begins on day 6. Both events take place during the cycle time. On day 6, you are preparing another assortment list, for store 5 the only change is the promotion that was sent out on the 1st. It is not necessary to send it again, the system knows that, so no AL is sent to store 5 on this date. On the 12th another message is created and downloaded. But on the 16th a full version is created because it has received 2 change versions now.

October 1998

Page 48

SAP AG

IRT260 Retail Store Connections Unit 4: Headquarters to Store (Assortment List)

Exercise: Initialize their Store TS## for Assortment List. 15 minutes 4-6, 4-7

5 minutes The Assortment List is simply another IDoc type and message type to supply master data to a store or customer. The Assortment List message carries just about all the information relevant to an article. Version management controls the schedule of creating the Assortment list. Reports control the sending of Assortment Lists, both full and change versions.

October 1998

Page 49

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Unit: Store to Headquarter (Inbound Documents) 8 hours (plus breaks)

List of Topics in the Unit  Data flow on inbound communication 

POS and EDI profiles for inbound communication



Customizing of inbound processing of store physical inventory data



Customizing of inbound processing of article master data changes



Customizing of inbound processing of financial transaction data



Customizing of inbound processing of cashier statistics data



Customizing of inbound processing of store order data



Customizing of inbound processing of goods movement data



Customizing of inbound processing of sales data

Putting the Unit in Context How the POS Interface handles the general data flow on inbound message processing is important for the student to understand to know how to research problems in a live situation. How to customize each of the POS inbound messages currently supported by SAP Retail is covered in detail.

Objectives Deliver information that will allow the participants to:  List the inbound POS messages (currently handled by SAP Retail) 

Describe the data flow on POS inbound communication on a technical level



Customize store EDI partner profiles for inbound POS messages



Define and assign POS inbound profiles, and customize the detailed processing of inbound POS messages for those POS inbound profiles.

Topic: Data flow on Inbound Communication Putting the Topic in Context Give an overview of the POS inbound messages and the data flow (SAP recommendation) as a warm-up to the unit.

October 1998

Page 50

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Topic Objectives Describe the overview of POS inbound so that participants can:  Name the inbound POS messages that are handled by the POS interface 

Explain the stages of data flow on inbound communication, as recommended by SAP



Explain the steps carried out by the system’s built-in simulation tools for inbound communication and how it differs from live data flow.

Types of Inbound Business Data See notes.

Inbound Processing: Data Flow (SAP Recommendation) See notes. Which EDI partner profile the system uses to control the processing of a newly arrived IDoc, is determined by seven fields in the IDoc’s control record (see slide “EDI Partner Profiles: Inbound Controls (1/2)”. The processing of the IDoc is done through a function module. The name of this function module is determined from the field ‘Process code’ maintained for the message type in the EDI partner profile and is found, via database table TEDE2. Inbound Processing: Simulation Tool See notes.

Demonstration of Data flow on Inbound Communication 5 minutes To show menu path to inbound simulation tool: From SAP Retail start menu (TA W10T), select Retail Distr. Retailing POS interface, Extras  Simulation. Relate menu options to messages listed on slide “Types of Inbound Business Data”. Topic: POS and EDI Profiles for Inbound Communication Putting the Topic in Context EDI and POS profiles are described as the two most important items by which the inbound processing of messages received from a store is controlled.

October 1998

Page 51

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Participants should be able to:  Define a POS inbound profile in customizing and assign it to a store 

Create an EDI partner profile for a store and maintain its inbound section for any inbound message



Maintain and use EDI partner profile defaults.

Customizing Inbound Processing: Overview (1/3) through EDI Partner Profiles: Inbound Controls (2/2) See notes.

Demonstration of POS and EDI Profiles for Inbound Communication < 20 minutes> Demonstrate how to define an Inbound Profile for IP00 (IRT260 inb. profile) and assign it to store R316 To Define a POS inbound profile: from standard customizing (TA SPRO):, Select Sales and Distribution  POS interface Inbound Maintain profile for POS inbound Select New Entries, enter IP00 and describe it as Trainer’s Inbound. Press Save and Back out. To Assign the profile, use the path: Retail  Master data  Site, Site  Change. Enter R316. In the store master, select tab ‘POS’. Enter IP00 in field ‘POS inbound profile’. Show definition of a recipient ‘File’-port for POS inbound. To review recipient ‘File’-port SAPIRT for inbound communication In standard customizing (TA SPRO), select Cross-Application components Distribution (ALE) Communication Manual Maintenance of Partner Profiles Define port Expand File, double click port SAPIRT. Show the parameters for the inbound file. These are ignored, the converter passes the file location with the inbound files. See notes in the slide, “Customizing Inbound Processing: Overview (3/3)”. Demonstrate creating an EDI partner profile and maintaining controls for an inbound message, not using EDI partner profile defaults. Create EDI partner profile for store R316 (if not done yet in course) and maintain inbound controls for message type WVINVE. To create: in standard customizing (TA SPRO), select Cross-Application components Distribution (ALE) Communication Manual Maintenance of Partner Profiles Maintain partner profile. October 1998

Page 52

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Enter Partn.number.......................................R316 Partn.type............................................KU (customer) Press enter and on main screen ensure: Partn.status..........................................A (active) To maintain inbound parameters, Select Inbound parameters, select New Entries and enter the following information: Message type.......................................WVINVE Test...................................................... Process code........................................WVIN Synatx check.......................................blank Immediate processing.......................... Typ......................................................(as defaulted) Lang....................................................(as defaulted) ID........................................................(as defaulted).

Demonstration Creating EDI Partner Profile defaults 30 minutes The purpose of this method of creating EDI Partner Profiles is to make the process efficient when you are getting ready to bring many stores online.

To define EDI partner profile defaults: In standard customizing (TA SPRO), select Cross-Application components IDoc interface / Electronic Data Interchang IDoc Interface – Basis Set proposal values for partner profiles (at least one default should exist) select ‘Proposal values for inbound partner profiles’. Direction 2 (inbound) defaults, enter KU for partner type. To use EDI partner profile defaults: In standard customizing (TA SPRO), select Cross-Application components Distribution (ALE)  Communication Manual Maintenance of Partner Profiles Maintain partner profile. Enter: Partn.number R316 Partn.type KU (customer) then, chose menu path Partner > Fast entry. Select the direction and then select the message types you want for the profile.

Exercise for POS and EDI Profiles for Inbound Communication 30 minutes

October 1998

Page 53

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

5-1, 5-2, 5-3 Topic: Customizing of Inbound Processing of Store Physical Inventory Putting the Topic in Context This topic discusses customizing inbound processing of store physical inventory data by the POS interface, for a given POS inbound profile. Participants should be able to:  Describe two business scenarios for handling store physical inventory 

Customize store physical inventory inbound processing and simulate inbound data processing by the POS interface



Describe the effects of simulation.

Store physical inventory: Business scenario 1 See notes. Stress that the upload of physical inventory transaction type from a store to the central SAP Retail system is only required for store/article combinations, for which inventory management is active in the SAP Retail system (regardless of whether it is also active in the store’s merchandise management system). This implies in particular, that the store and articles in question are defined in the SAP Retail system in terms of corresponding sets of master data. Store Physical Inventory: Business Scenario 2 through Store Physical Inventory: Customizing See notes.

Demonstrate Customizing Inbound Processing of Store Physical Inventory Orchestrated by the Store 12 minutes (Refer to slide Store physical inventory: business scenario 1). Prerequisite: POS inbound profile IP00 must be defined and assigned to store R316. EDI partner profile must be defined for store R316 and maintained for inbound message type WVINVE. Customize store physical inventory for POS inbound profile IP00 and simulate upload of store physical inventory data for store R316 and article R100016. To Customize: In standard customizing (TA SPRO), select  Sales and Distribution POS interface Inbound Store phys. Inventory control; Select New entry and enter profile IP00 and October 1998

Page 54

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

creation control inv. docs................4 (create phys. inv. doc. Directly). In a second session check stock using the path: Retail  Master data  Article, Other  Stock Overview. Enter Article R100016 and site R316. Displays the quantity of stock. To simulate physical inventory, use the path: Retail  Distr. Retailing  POS Interface  Extras Simulation  Store phy. Inv. Enter, on store physical inventory simulation screen: Store................................R316 Storage loc......................0001 Fiscal year.......................(current year) (rest as defaulted) at item level Item.................................0001 Qual................................ARTN Identifier.........................R100016 Qty..................................(current stock+2). Press Save. When the system displays the message that the IDoc is created, Press IDoc status and then POS Monitor to display the IDoc created and physical inventory document in POS Monitor Double click the Physical Inventory d area to bring up the inventory document. Select Physical Inv. History point out fields ‘Phys.inv.status’ (= Counted), ‘Quantity’ and ‘Book quantity’ and difference quantity. Post difference in inventory document just created, using the path: Retail  Distr. Retailing  Merchand. logistics Physical inventory, Difference Post The Physical Inventory doc number defaults, press Enter, and then press Save on the subsequent screen. In the second session recheck stock using the path: Retail  Master data  Article, Other  Stock Overview. Enter Article R100016 and site R316. Display the quantity of stock to verify posting of physical inventory difference.

Demonstrate Customizing Settings of Store Physical Inventory Orchestrated by Head Office < 12 minutes> (Refer to slide Store physical inventory: business scenario 2). Customize store physical inventory for. POS inbound profile IP00 and simulate upload of store physical inventory data for store R316 and article R100016. To customize: In standard customizing (TA SPRO): select Sales and Distribution POS interface  Inbound  Store phys. Inventory control. Change entry for POS inbound profile IP00 as follows: October 1998

Page 55

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

creation control inv. docs................2 (do not create phys. inv. Doc To simulate, Create a physical inventory document for store R316 and article R100016. Use the following path: Retail  Distr. Retailing Merchand. logistics Physical inventory, Phys. Inventory doc. Create. Enter Site........................................R316 Storage location..............0001 (rest as defaulted), press Enter. Article (for item 1)..........R100016. Press Save. Display physical inventory document, following Retail  Merchand. logistics Physical inventory, Phys. Inventory doc. Display The article and site default. Press enter, and double click on the article. Point out field ‘Phys.inv.status’ (= Not yet counted) on item details screen. On simulation screen for store physical inventory, enter at header level Store................................R316 Storage loc......................0001 Fiscal year.......................(current year) (rest as defaulted) at item level Item.................................0001 Qual................................ARTN Identifier.........................R100016 Qty..................................(current stock+5). Press Save. Press IDoc status to display IDoc created and physical inventory document (modified) in POS Monitor. Double-click on physical inventory d point out again Phys.inv.stat. (= Counted), Quantity and Book quantity on item details screen. OPTIONAL (this is a repetition): In a second session check stock using the path: Retail  Master data  Article, Other  Stock Overview. Enter Article R100016 and site R316. Displays the quantity of stock. post difference in inventory document, using Merchand. logistics Physical inventory, Difference Post Check quantity of R100016 in store R316 again to verify posting of physical inventory difference.

Exercise for Customizing Inbound Processing of Store Physical Inventory < 25 minutes> 5-4, 5-5 October 1998

Page 56

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Topic: Customizing of Inbound Processing Article Master Data Changes Putting the Topic in Context This topic discusses customizing inbound processing for master data changes uploaded by a store, with a particular POS inbound profile. Participants should be able to ...  Describe main business process for handling master data changes proposed by a store 

Explain, which master data changes the POS interface can handle, and how;



Customize (and simulate) the inbound processing of master data changes by the POS interface;



Describe the effects of the latter;



Access their workflow inbox and execute workitems.

Article Master Data Changes: Business Scenario See notes. Stress that the upload of article master data changes from a store to the central SAP Retail system is only required for articles, that are maintained in the SAP Retail system (regardless of whether a set of article master data is also defined in the store‘s merchandise management system). Article Master Data Changes: Customizing See notes. Stress that the EAN/UPC changes and the other article master data changes are handled differently. For EAN/UPC changes, one has the option (by way of the customizing described on this slide) between workflow and automatic posting to the SAP Retail system. For all other master data changes, there is no option; they always generate a workitem to be executed! Demonstration of Customizing Inbound Processing of Article Master Data Changes 20 minutes Prerequisite: EDI partner profile must be defined for store R316 and maintained for an inbound message type. To maintain EDI Partner Profile for additional inbound POS messages in standard customizing use the following path: Tools  Business Engineer Customizing  Implementation Projects  SAP reference IMG  Cross-Application components October 1998

Page 57

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Distribution (ALE) Communication Manual Maintenance of Partner Profiles Maintain partner profile Enter R316 partner no and KU for type. Select inbound parameters. Select a message type and press copy. Make the following changes: Message type.......................................WP_EAN Process code........................................WP_E, Repeat a second time with these changes: Message type.......................................WP_PLU Process code........................................WP_P; There is no POS customizing necessary for article master data changes. To simulate upload of article master data changes for article R100016 in store R316: Retail  Distr. Retailing  POS Interface  Extras Simulation Master data on the simulation screen for article master data changes other than EAN/UPC changes, enter Customer.............................................R316 Select Article Change flg...........................................MODI Date.....................................................(today’s date) Main EAN/UPC..................................2050000001208 Print price............................................ Select IDoc status to display IDoc status and double-click on message ‘Workitems (tasks) were created for this IDoc’ and select the link to go directly to your office inbox and select Workflow. Execute the IDoc and point out ‘Proposal’ vs. ‘to date’ values; mention again, that the proposed values now must either be rejected, or maintained manually. Note: the ‘print price’ flag is a download-flag (field PRDU in table T134) that determines whether the price is indicated on the display and printed on the sales receipt; it is not maintained at the actual article level, but at the article type level (!); hence, in the above example, the person in charge of processing the workitem would have to (manually). Set the ‘print price’ flag in customizing (TA SPRO), following: Implement. projects SAP Reference IMG  Logistics GeneralLogistics Basic Data: Material Master Material Control Data Define attributes of material types

Demonstrate Customizing inbound processing of article master data changes – EAN/UPC changes only Prerequisite: POS inbound profile IP00 must be defined and assigned to store R316. EDI partner profile must be defined for store R316 and maintained for inbound message type WP_EAN. To customize EAN/UPC changes in standard customizing (TA SPRO), following: Implement. projects SAP Reference IMG  Sales and Distribution POS October 1998

Page 58

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

interface Inbound Automatic EAN/UPC creation control; create entry Inbound Profile.......................IP00 Auto. EAN creation control....(blank); To simulate EAN/UPC changes on simulation screen for article master data: Retail  Distr. Retailing  POS Interface  Extras Simulation Master data enter Customer................................R316 Date........................................(today’s date) Select EAN references Change flg..............................MODI Main EAN/UPC......................2050000001208 EAN/UPC...............................2000000000000 Select IDoc status to display IDoc and double-click on message ‘Workitems (tasks) were created for this IDoc’ select the link to go directly to your inbox. Select the workitem. Execute the IDoc; mention again, that the proposed EAN/UPC (2000000000000) has to be either rejected, or maintained manually for article R10016. (simulation with Autom. EAN creation activated still leads to errors (10/98) Exercise to Customize and Simulate Inbound Processing of Article Master Data Changes 30 minutes 5-6, 5-7, 5-8 Topic: Customize Inbound Processing of Financial Transaction Data Putting the Topic in Context This topic discusses the customizing of the inbound processing of financial transaction data, for a particular POS inbound profile. Participants should be able to:  Describe main business process of handling financial transactions encountered at, and uploaded from a store;

October 1998



Know the type of FI accounts, to which financial transactions can be posted;



Explain, what financial transaction type are designed to be used for;



Customize (and simulate) the inbound processing of financial transaction data



Describe the effects of the latter;



Set up conversion between POS transaction types and FI transaction types.

Page 59

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Financial transactions: business scenario See notes. Stress, in order to model and document financial transactions incurred at a store in the SAP system’s FI module, it is necessary that 1. The stores are defined there in terms of a set of master data in the SAP Retail system, 2. Appropriate FI accounts (G/L accounts, vendor accounts, customer accounts), to which the financial transactions are posted, are defined (also in terms of a set of master data) in the SAP system’s FI module, 3. And suitable (FI-) posting keys are also defined. Financial Transactions: Transaction Types (1/2) through Financial Transactions: Transaction Types (2/2) See notes.

Demonstrate Customizing Inbound Processing of Financial Transaction Data 10 minutes Define FI transaction types PECA (petty cash payments), CABA (cash deposit to bank), DEIN (customer invoice settlement) and CRIN (vendor invoice settlement). Use the following path in standard customizing (TA SPRO): Implement. projects SAP Reference IMG Sales and Distribution POS interface InboundTransaction types for financial transactions; create the following entries: FI trans. Description PECA Petty cash payment CABA Cash dep. into bank DEIN Customer inv. settl. CRIN Vendor inv. Settl. Point out, for example, that PECA is used for one-of cash expenditures of small amounts. CABA is used when depositing cash (taken from cash registers at the end of the day) into a bank account. DEIN is used when a customer comes to a store and settles an invoice. CRIN is used if some local goods or service provider (e.g., a window dresser, office furniture provider,) is paid at the store.

Financial Transactions: Customizing See notes. Remind participants that any posting in the FI module requires at least one debit and the balancing credit. Given the correct customizing settings, the SAP Retail system allows a store to only upload one item (credit or debit) per financial transaction. The second item (debit or credit) is then generated automatically during inbound processing by the SAP Retail system. This further reduces the amount of (financial transaction) data a store needs to upload to the SAP Retail system. Stress that the account default specified per financial transaction type only applies to G/L-accounts. If a financial transaction involves a particular customer or a particular October 1998

Page 60

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

vendor sub-ledger, the number of the corresponding account must be transmitted with each such transaction. Note: Use only one of the following demonstrations and point out that if the set up were for a G/L to G/L transaction, the set up requires the two G/L account numbers rather than one blank.

Demonstration of Customizing Inbound Processing for Financial Transactions -- Customer Payment of an Invoice 20 minutes Prerequisite: EDI partner profile must be defined for store R316 and maintained for an inbound message type. POS inbound profile IP00 must be defined and assigned to store R316. Financial transaction type DEIN must be defined. To maintain EDI Partner Profile for additional inbound POS message types in standard customizing (TA SPRO) use the following path: Implement. projects SAP Reference IMG Cross-Application components Distribution (ALE) Communication  Manual Maintenance of Partner Profiles Maintain partner profile Enter store R316, partner type KU and select inbound parameters. Select a message type and press copy. Make the following changes: Message type.......................................WPUFIB Process code........................................WPUF. Show customizing settings to control inbound processing of financial transaction data involving a G/L account and a sub-ledger account. In this case a customer account, e.g., a customer has bought an article at a store, has received an invoice in the mail and returns to the store to pay it. To customize financial transactions for a G/L and sub-ledger account in standard customizing (TA SPRO), use the following path: Implement. projects SAP Reference IMG Sales and Distribution POS interface Inbound Transaction type-dependent control of financial transactions; Select New entries: Inb. prof....................................IP00 FI transaction............................DEIN Item no......................................1 G/L account...............................(leave blank ) ..................................................because a customer account ..................................................is posted to, no G/L account; Posting key................................11 (credit memo) and Inb. prof....................................IP00 FI transaction............................DEIN Item no......................................2 G/L account...............................163000 (accounts receivable) October 1998

Page 61

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Posting key................................40 (debit entry) To simulate creating an invoice for customer R3000 by following, from SAP Retail start menu (TA W10T): Accounting  Financial accounting Accounts receivable, Postings Invoice and entering, at header level, Document date..........................(today’s date) Doc. type...................................DR Company code..........................R300 Posting date...............................(today’s date) Currency/rate.............................USD, and for the first line item, PstKy.........................................01 (invoice) Account.....................................R3000 (after pressing RETURN) Amount.....................................100 Allocation..................................LINE 1 (rest as defaulted), and for the next line item, PstKy.........................................50 (credit entry) Account.....................................800000 (after pressing RETURN) Amount.....................................100 Allocation..................................LINE 2 (rest as defaulted (press ENTER to get past tax warning;) note number if accounting document created, and display open line items in customer account R3000 by following, from SAP Retail start menu (TA W10T): Accounting Financial accounting Accounts receivable, Account  Display line items Enter: Customer...................................R3000 Company code..........................R300; point out that ‘Allocation’ = Line 1 in that list for the FI document just created To simulate inbound customer payment transaction, use the path from the Retail start menu (TA W10T) Retail  Distr. Retailing  POS interface  Extras  Simulation  Finan. Transaction Enter at header level Customer...................................R316 Reference no.............................00 (group number) Transaction type........................DEIN (rest as defaulted) at item level Item...........................................1 Acc.assgnt. obj..........................R3000 (a customer) Amount.....................................97 October 1998

Page 62

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

..................................................(3 USD cash discount granted ..................................................due to payment conditions of ..................................................R3000) Curr...........................................USD Assignment...............................LINE 1 Press IDoc status to view the IDoc and FI documents numbers in POS Monitor Display customer account R3000 open line items, by following the path from SAP Retail start menu (TA W10T): Accounting Financial accounting Accounts receivable, Account Display line items Enter: Customer...................................R3000 Company code..........................R300 point out that ‘Allocation’ = Line 1 in that list also for the FI document just created; To clear the invoice line item against the payment line item in R3000’s account, follow, from SAP Retail start menu (TA W10T): Accounting Financial accounting Accounts receivable, Account Clear Enter: Account.....................................R3000 Company code..........................R300 Select

.................................................Others (rest as defaulted)

Press ‘ENTER, then ‘Cancel’, and select Allocation Press ‘ENTER’ again and restrict ‘Allocation’ to LINE 1 Press ‘Process open items’ to display the the two line items that were matched and are to be cleared against each other; point out that there is no posting difference (‘Not assigned’ = 0); press button ‘Post’ Display R3000’s open line items again by following the path from SAP Retail start menu (TA W10T): Accounting Financial accounting Accounts receivable, Account Display line items Enter Customer...................................R3000 Company code..........................R300 Point out that the two line items with ‘Allocation’ = LINE 1 have now disappeared, i.e., that the invoice has been cleared by the payment. .

October 1998

Page 63

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Demonstration: Customizing inbound processing of financial transactions -- a G/L account and a vendor account Prerequisite: POS inbound profile IP00 must be defined and assigned to store R316. Financial transaction type CRIN must be defined. EDI partner profile must be maintained for inbound message type WPUFIB. To Customize, in standard customizing (TA SPRO), select: Sales and Distribution POS interface Inbound  Transaction type-dependent control of financial transactions Select New entries Inb. prof. IP00 FI transaction CRIN Item no. 1 G/L account (blank !!!) because creditor or vendor account is posted to, no G/L account; Posting key 25 (outgoing payment) and Inb. prof. FI transaction Item no. G/L account Posting key

IP00 CRIN 2 160010 (trade payables) 91 (costs)

First, create invoice entry from vendor R3001 by following, from SAP Retail start menu (TA W10T): Accounting Financial accounting Accounts payable, Postings Invoice Enter, at header level, Document date........................(today’s date) Doc. type................................KR Company code........................R300 Posting date............................(today’s date) Currency/rate..........................USD For the first line item enter: PstKy......................................31 (invoice) Account..................................R3001 Press RETURN, and enter: Amount...................................100 Allocation...............................LINE 1 (rest as defaulted), For the next line item enter: PstKy......................................86 (GR/IR debit) Account..................................191099 Press RETURN, and enter: Amount...................................100 Allocation...............................LINE 2 (rest as defaulted); October 1998

Page 64

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Note number of accounting document created, and display vendor account R3001 open line items in by following, from SAP Retail start Menu (TA W10T), Accounting Financial accounting Accounts payable, Account Display line items Enter Vendor....................................R3001 Company code........................R300; Point out that ‘Allocation’ = Line 1 in that list for the FI document just created; To simulate inbound payment transaction (to creditor R3001) data, Retail  Distr. Retailing  POS interface  Extras  Simulation  Finan. Transaction Enter at header level Customer................................R316 Reference no...........................00 (group number) Transaction type.....................CRIN (rest as defaulted) at item level Item........................................1 Acc.assgnt. obj........................R3001 (a vendor) Amount...................................100 Curr.........................................USD Assignment.............................LINE 1 Press IDoc status to view the IDoc and FI document number in POS Monitor Display open line items in vendor account R3001 again by following, from SAP Retail start menu (TA W10T), Accounting Financial accounting Accounts payable,Account Display line items Enter Vendor....................................R3001 Company code........................R300; Point out that ‘Allocation’ = Line 1 in that list also for the FI document just created To clear the vendor invoice line item against the payment line item in account R3001, follow, from SAP Retail start menu (TA W10T), Accounting Financial accounting Accounts payable, Account Clear Enter Account..................................R3001 Company code........................R300 Others..................................... (rest as defaulted); Press ‘ENTER, then button ‘Cancel’, and set Allocation...............................; Press ‘ENTER’ again and restrict ‘Allocation’ to LINE 1. October 1998

Page 65

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Press button ‘Process open items’ to display the two line items that were matched and are to be cleared against each other. Point out that there is no posting difference (‘Not assigned’ = 0); Press button ‘Post’ to complete the clearing. To review the success of the clearing, display open line items in vendor account R3001 one more time by following, from SAP Retail start menu (TA W10T), Accounting Financial accounting Accounts payable, Account Display line items Enter Vendor....................................R3001 Company code........................R300; Point out that the two line items with ‘Allocation’ = LINE 1 have now disappeared, i.e., that the invoice has been cleared by the payment

Exercise for Customizing Inbound Processing of Financial Transactions 30 minutes 5-9, 5-10, 5-11 Topic: Customizing Inbound Processing for Cashier Statistics Data Putting the Topic in Context Cashier statistics combine with sales data to provide the Sales Audit information. This topic (briefly) discusses the (LIS-) customizing necessary to ensure that cashier statistics uploaded from a store update info structure S122 (Cashier). Participants should be able to:  Give examples of statistics data that can be uploaded with IDoc type WPUKSR01 

Verify, in LIS customizing, that updating of info structure S122 is active, and be able to activate it if necessary



Use standard analysis ‘Cashier’ in RIS to verify updating of info structure S122.

Cashier Statistics: Business Scenario through Cashier Statistics: (LIS-) Customizing See notes.

October 1998

Page 66

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Demonstrate Customizing Inbound Processing of Cashier Statistics Data 15 minutes Investigate info structure S122 (Cashier), as well as update controls (refer again to course IRT230 Assortment Controlling using the Information System (RIS) for details) Prerequisite: EDI partner profile must be defined for store R316 and maintained for an inbound message type. To maintain EDI partner profile for an additional inbound POS message type, in standard customizing use the following path: In standard customizing (TA SPRO), select Cross-Application components Distribution (ALE) Communication  Manual Maintenance of Partner Profiles Maintain partner profile; Enter R316 partner no and partner type KU Select inbound parameters. Select a message type and press copy and make the following changes: Message type.......................................WPUKSR Process code........................................WPUK. To display characteristics as well as key figures, and update control for info structure S122 in LIS-customizing.: in standard customizing (TA SPRO), select Logistics – General Logistics Information System (LIS) Logistics Data Warehouse Updating Updating Control Activate update Select Retail (RIS) Select info structure S122, Cashier and then, Environment  Info structure def. …, Point out update interval is set for Daily and Updating mode is 2 asynchronous (fiscal year variant should be blank); Note the various characteristics and key figures on the subsequent screen. Select Environment  UpdDf for InfoStr…, double-click on info structure S122 and update group 800 to show details of updating. Ev column means which event updates a key figure: RE Retail External POS data RC Retail External cashier data RP Retail Sales price change T column identifies the type of updating A is Cumulative B is data transfer only C is a counter. Rules for characteristics on this screen identify which table and field is used for each characteristic. Rules for key figures also identify which table and field is used for each key value, also where to look for the date and if a formula or calculation is involved what it is. October 1998

Page 67

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

For an example, page down and show ‘Value terminations’ is updated upon event ‘RC’, updates are A-cumulated, at document currency). To Simulate upload of cashier statistics data (value and number of terminations and scanned articles for a particular cashier) for store R316 and verify, using standard analysis Cashier in RIS. Use the following path: Retail Distr. Retailing POS interfaceExtras  Simulation  Sales Select Cashier statistics Enter Customer..................................................R316 (rest as defaulted) Update group............................................(blank) ..................................................800 is used as default; ..................................................if you want to explicitly ..................................................specify an update group, ..................................................enter it with leading zeroes, ..................................................i.e., 000800; Cashier 00 (group number) Target currency.........................................USD Value terminations....................................(integer - 545) No. terminations.......................................(integer - 5) Value of art. Scnnd...................................(integer > 10365) ..................................................!!! this key figure is NOT ..................................................included in info structure ..................................................S122, hence this value ..................................................will not show in the standard ..................................................analysis ‘Cashier’; No. art. Scnnd...........................................(integer > 235); Press Save. (Note; you can use any integer greater than zero that you wish, I just added these to make it simple.) Select IDoc Status to display the IDoc in POS Monitor. To verify that the structure was updated, Start at the Retail start menu (TA W10T), follow the path: Info system/Planning Retailing, Standard analyses Special processes POS statistics Cashier Enter the following: Site............................................R316 Day (from)................................(blank) Day (to).....................................(today’s date); If necessary, add key figures to list (use button ‘Choose key figures…’); show updated key figures No. terminations No. articles scanned Value terminations Explain, that the value of articles scanned does not appear since this figure, although on the simulation screen, is not included as a key figure in info structure S122. Mention also (… as mentioned in the notes to slide Cashier statistics: October 1998

Page 68

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

(LIS) customizing) that the key figure ‘invoiced sales’ is not updated during upload of cashier statistics data, but during upload of sales data. Exercise for Customizing Inbound Processing of Cashier Statistics Data 30 minutes 5-12, 5-13, 5-14, 5-15, 5-16,

Topic: Customizing Inbound Processing of Store Order Data Putting the Topic in Context This topic describes many factors impacting the inbound processing of store orders, and how to customize, and at what levels they can be customized. Participants should be able to:  Describe main business process involving store orders 

Name the levels at which customizing controls for store order inbound processing can be maintained



Name the types of follow-on documents that can result from store order inbound processing



Explain the ‘next-level’-logic by means of which the type of follow-on document is determined



Name those controls in store order customizing that are performance critical.

Store Order: Business Scenario See notes. Emphasize: to use store order functionality to record and process procurement demands from a store, it is necessary for the store, as well as the articles to be procured, to be defined in the SAP Retail system (as master data. So are distribution centers (DCs) and/or external vendors that are to deliver the articles. Store Order: Customizing (1/6) See notes. Note that store order customizing is also done via a POS inbound profile, BUT, UNLIKE OTHER INBOUND MESSAGES, a POS inbound profile controlling the inbound processing of store orders can also be maintained at the level store/MC (MC = merchandise category)! BUT some store order controls are only read at store level, even if another POS inbound profile is defined at store/MC level (see notes on following slides)!

October 1998

Page 69

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Demonstrate Master Data Set Up for Store Order data) 5 minutes To show assignment of a POS inbound profile for store order control at store/MC level RetailingMaster dataSite, SiteChange Site R316, remind them where the POS inbound profile is assigned at store-level. Then, select Merchandise Categories point at column SPPr, which for this store is blank, and bring up F1-help on this column. Store Order: Customizing (2/6) through Store Order: Customizing (6/6) See notes. Demonstrate Customizing Inbound Processing of Store Order Data 15 minutes Prerequisite: EDI partner profile must be defined for store R316 and maintained for an inbound message type. To Maintain EDI partner profile for an additional inbound POS message in standard customizing (TA SPRO), select Cross-Application components Distribution (ALE) Communication  Manual Maintenance of Partner Profiles Maintain partner profile Enter R316 partner number and KU for type. Select inbound parameters. Select a message type, press Copy and make the following changes: Message type.......................................WGSREQ Process code........................................WVFB. To present test scenario for store orders, first, verify system settings to ensure that article R100000 is procured internally for store R316, and article R100005 is procured externally for store R316. To verify: (a) ‘Supply source’-key and source of supply for R100000 in R316 Retail  Master data Article, Article change Enter article R100000 store R316 Select Logistics: Store Point that ‘Supply source’ = 4 (Stock transfer before standard) DC out R300 Vendor R3001 Explain: ‘before’ means that the automatic source of supply determination first looks for an internal source of supply (i.e., a DC), and then for an external source of supply (i.e., a vendor) Article R100000

Article R100005

October 1998

Page 70

Store R316

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

In site master of store R316 show, on ‘Supplying sites’-screen, that store R316 actually has an internal source of supply defined, namely DC R300 Check whether DC R300 has sufficient stock of article R100000; if ‘not’ post ‘other’ goods receipt for article R100000 at store R316 and storage location 0001, using movement type 501 (not generating a PO in the background) (b) ‘Supply source’-key and source of supply for R100005 in R316 Perform the same check of article R100005 to show that ‘Supply source’ = 3 (Standard before stock transfer on ‘Logistics screen’ for article R100005 and store R316; In this case, explain that ‘before’ means that the automatic source of supply determination first looks for an external source of supply (i.e., a vendor), and then for an internal source of supply (i.e., a DC) Show, that article R100005 actually has an external source, namely vendor R3001, by displaying all (only one exists) purchasing info records involving article R100005. Use the path: Purchasing Purchase order, Master data Purchasing info record List displays By article Select purchasing info record (5300001747) and display it (button ‘Display info record’); Show general data of purchasing info record (button ‘General data’) and point out, that R3001 is also flagged as ‘regular vendor’ for article R100005. (c) Listing of articles R100000 and R100005 for storeR316: Show, that articles R100000 and R100005 are both listed for store R316 and the current date, by following: Master data Assortment,Analyses for article Listing conditions Select: Article:................................................R100000 and R100005 Assortment..........................................R316 Valid on...............................................(today’s date) Valid to................................................(blank); FINALLY, draw a picture similar to the one below on a board:

October 1998

Page 71

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

At this point, interrupt the demo and raise the following question: How can we customize store order inbound processing in such a way, that article R100000 is procured through a delivery, while article R100005 is procured through a PO? As a 1st clue, add MCs to the above picture (R1111 for article R100000, R1114 for article R100005). As a 2nd clue, refer back to the ‘next level’-logic on slide Store order: customizing (6/6). Discuss the following two answers: A1: Maintain a single POS inbound profile at store level (R316) and customize store order for this POS inbound profile, choosing ‘delivery’ (= 4) as follow-on document type for internal store orders, and ‘PO’ (= 3) as follow-on document type for external store orders. (We will do this in the following demonstration.) A2: (Notice that R100000 and R100005 belong to different MCs, R1111 and R1114) Maintain two POS inbound profiles at store/MC level (R316/R1111 and R316/R114). For the one at level R316/R1111, define ‘delivery’ (= 4) as follow-on document type (independent of supply source), and for the one at level R316/R1114, define ‘PO (= 3) as follow-on document type (independent of supply source). Demonstrate Customizing Inbound Processing for Store Order Data continued 25 minutes Prerequisite: POS inbound profile IP00 must be defined and assigned to store R316. EDI partner profile must be defined for store R316 and maintained for inbound message type WGSREQ. To customize store order for POS inbound profile IP00 to create deliveries or POs, depending on the source of supply, in standard customizing (TA SPRO), select Sales and Distribution POS interface Inbound  Store order control Enter: POS inbound profile..................IP00 Default del. type........................LO Default order doc. type..............UB Warning level error mess...........2 (log all errors) Default doc. category external store order....................3 (create PO, otherwise error) Default doc. category internal store order....................4 (delivery)

October 1998

Page 72

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Demonstrate Simulating Inbound Store Order Processing 15 minutes There are 3 separate store order scenarios. 1st scenario: Create delivery and PO in one order and simulate upload of store order data for store R316 and articles R100000 and R100005. To simulate, start at the Retail start menu (TA W10T) Retail Distr. Retailing POS interfaceExtras  Simulation  Store order Enter at header level: Customer...................................R316 (rest as defaulted) Press Order overview. Enter at item level: Identifier....................................003 (EAN) Article/EAN..............................2050000000966 ..................................................(article R100000, in PC) Quantity....................................(integer > 0, not exceeding ..................................................stock of article R100000 at ..................................................DC R300) Ext. Requirement......................A-00 and Identifier....................................006 (article number) Article/EAN..............................R100005 Quantity....................................(integer > 0) Ext. Requirement......................B-00 (Hint: keep these entries for later by selecting System  User profile  Hold data;) Select IDoc status to display IDoc in POS Monitor Display delivery generated (double-click on delivery number in POS Monitor), and: Select Header  General header data and note the fields ‘Deliv.type’ and ‘Ext.delivery’. Return to Overview screen and select Item  Item details. Point out field ‘Site/Sloc’ (Refer to previous discussion of where R300 was found as supplying site;) Stress that data entered in the store order simulation was enhanced, during inbound processing, by adding header details (such as, shipping point, route, ...) and item details (such as, loading group, transportation group, ....) Display the PO generated (double-click on PO number in POS Monitor) and point out on PO overview screen, the ‘Vendor’ field. Select Header  Statistics  General and note ‘Status’ field, use F4 to show definition of code Go back to the overview screen and select Item  Details. Note the October 1998

Page 73

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

‘TrackingNo’ field (Refer to previous discussion and why R3001 was found as vendor;) stress that data entered in the store order simulation was enhanced, during inbound processing, by adding header details (such as company code, purchasing organization, purchasing group, ...) and item details (such as MC, confirmation control key, ...) Simulate: (2nd scenario; display warnings and notes) For your POS inbound profile IP00, modify the Store order control as follows. Change Warning level error mess...........4 (log all errors, warnings .................................................. and notes) Repeat scenario 1, but when you select IDoc status, point out additional information (warnings, notes) that are now displayed in POS Monitor after generation of store order IDoc Simulate: 3rd scenario; produce and execute workflow item Repeat the above simulation, but on the simulation screen for store orders, enter ‘xyz’ in column ‘Unit’ for the second item (article R100005); Because ‘xyz’ is not a defined unit for article R100005, a workitem is generated. In a second session, access your workflow inbox by following, from the SAP Retail start menu (TA W10T), Office Inbox; Double-click on workitem called ‘Store order rework: ...’ and execute it (button ‘Execute’), thereby correcting the PO to be created by overwriting the order unit ‘***’ by ‘PC’ and saving. (Hint: the purchase order just created by processing the workitem is currently not picked up in the POS Monitor;)

Demonstrate strategy A in store order Prerequisite: POS inbound profile IP00 must be defined and assigned to store R316. EDI partner profile must be defined for store R316 and maintained for inbound message type WGSREQ. Store order inbound processing must be customized for POS inbound profile IP00. Simulate upload of store order data for store R316 and article R100000 two times, first for a quantity of 1 CAR (resulting in a PO from a DC), and then for a quantity of 1000000 CAR (resulting in a PO from an external vendor). Show necessary settings in customizing of availability check for stock transport order. Simulate inbound store order for 1 CAR Retail Distr. Retailing POS interfaceExtras  Simulation  Store order Enter at header level: Customer...................................R316 (rest as defaulted) Select Order overview and enter at item level October 1998

Page 74

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Identifier....................................006 (Pricing reference article) Article/EAN..............................R100000 Quantity....................................1 Unit...........................................CAR ..................................................(KAR in German) Default document type..............A. Press Save Select IDoc status to display IDoc in POS Monitor; Display PO generated (double-click on PO number in POS Monitor) and point out: field ‘Supplying site’ in PO header, and stress that procurement is through a DC Simulate: (quantity of 1000000 CAR) Repeat above simulation, but with Quantity....................................1000000; Display IDoc in POS Monitor; Display PO generated (double-click on PO number in POS Monitor) and point out: field ‘Vendor’ in PO header, and stress that procurement is through an external vendor (since PO quantity exceeds stock available at R300, which is the delivering DC for store R316 Show what was done in customizing for strategy A to work: (a) An availability checking rule for stock transport order must be assigned through standard customizing (TA SPRO) Materials Management Purchasing Purchase Order Set up stock transport order  Assign delivery type/checking’ to key combination Document type = (blank), Supplying site = R300 (b) CSS-note 106792 (created by Ralf Wingenter) must be maintained in the system.

Exercise for Customizing of Inbound Processing of Store Order data) 25 minutes 5-17, 5-18, 5-19 Topic: Customizing Inbound Processing of Goods Movement Data Putting the Topic in Context This topic discusses customizing the inbound processing of goods movement data, for a particular POS inbound profile.

October 1998

Page 75

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Participants should be able to ...  Describe the main business process for handling goods movements encountered at store; 

Tell where goods movements are defined and customized in the SAP R/3 system



Customize inbound processing of goods movement data



Simulate inbound processing of goods movement and describe the effects



Set up conversion between POS movement types and movement types, as defined in the SAP R/3 system.

Goods Movements: Business Scenario See notes. Emphasize that, in order to model and document goods movements in the SAP System, it is necessary that 1. The stores and articles are defined in the SAP Retail system in terms of master data, and that inventory management is active for both. 2. Moreover, as goods movements may also affect the valuation of stock at the store where the movement took place, suitable G/L accounts must be defined in the SAP R/3 system‘s FI module. 3. If cost accounting is also required, cost centers must be defined in the SAP R/3 system‘s CO module to which various goods movements (e.g., consumption) are to be posted. Goods Movements: Movement types (1/2) through Goods Movement: Movement types (2/2) See notes.

Demonstrate Customizing Movement Types in (MM-) in relation to Goods Movement Data Inbound Processing 10 minutes Show, where movement types are defined/customized in SAP R/3, and point out some of the customizing controls for movement types relevant for automatic G/L account determination. In standard customizing (TA SPRO), select Materials Management Inventory Management Movement Types Copy, change movement types. Select Movement type and enter 101. Select movement type 101 (GR Goods receipt) and point out, that customizing control of this (and other) movement types is divided into 11 levels, accessed through through the four page-buttons in field group ‘Navigation’. Using these buttons, display details of level Account grouping for the movement type selected, and point out columns Val.strng and TEKey that are used in automatic account determination. October 1998

Page 76

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Goods Movements: Customizing See notes.

Demo Preparations -- Goods Movements Prerequisite: EDI partner profile must be defined for store R316 and maintained for an inbound message type. POS inbound profile IP00 must be defined and assigned to store R316 Simulation preparation: First, check whether store R316 has sufficient stock of article R100016. if ‘not’ post ‘other’ goods receipt for article R100016 at store R316 and storage location 0001, using movement type 501 (not generating a PO in the background). Also, make sure that R100016 has a positive moving average price in store R316, because otherwise, no cost/accounting documents will be created – see field ‘Mov. avg. price’ on logistics screen of article R100016 for store R316, button ‘Accounting’

Demonstrate Customizing Goods Movement Data Inbound Processing 20 minutes To maintain EDI partner profile for an additional message type, in standard customizing (TA SPRO), select Cross-Application components  Distribution (ALE) Communication Manual Maintenance of Partner Profiles Maintain partner profile Enter R316 partner no. and KU for type. Select inbound parameters. Select a message type and press copy. Make the following changes: Message type..........................WPUWBW Process code...........................WPUW. To customize goods movement inbound processing for movement type 201 (Goods Issue for cost center) for POS inbound profile IP00, in standard customizing (TA SPRO), select Sales and Distribution POS interface Inbound Movement typedependent control of goods movements Create entry: POS inbound profile..................IP00 Movement type.........................201 (GI for cost center) Cost center................................R3110_001 (own consumpt.) Rev.mvnt. type..........................202 (RE for cost center To simulate upload of goods movement data, use the path from the Retail start menu (TA W10T) Retail  Distr. Retailing  POS interface Extras  Simulation  Goods movement October 1998

Page 77

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Enter at header level Customer...................................R316 Transact. date............................(today’s date) and press Goods movement. Enter at item level Reference no.............................00 (group number) Qual (in column 4)....................ARTN Number.....................................R100016 MTyp.........................................201 (GI for cost center) Quantity....................................1 Press Save. Press IDoc status and press POS monitor. Double-click on the article document to display it and point out field ‘Art. Slip’ (= Reference no. entered above) in header, field ‘MvT’ in item 1, field ‘Cost center’ in item details, accounting documents created. Double-click on the accounting document, point out field ‘Reference’ (= reference no. entered above) and that they were determined automatically (through movement type 201); (*) Double-click and expand the cost accounting document, point out cost center (R3110_001) and cost element (410050) posted to. Note: You can also display the posting to the cost center by starting at the SAP Retail start menu (TA W10T), and then following: Accounting Controlling Cost centers, Information system Report selection Select the report found by following Line items Actual Cost centers: Actual Line Items If prompted for a controlling area, enter R300. On the following selection screen, enter Cost center................................R3110_001 Posting date (from)....................(start of current month) Posting date (to)........................(end of current month) Display variant..........................1SAP) Check again stock numbers of article R100016 at store R316.

Optional Demo of Customizing for Account Determination 10 minutes If you’re interested in showing the customizing to set up the G/L accounts were determined, go to standard customizing (TA SPRO) and follow: Materials management Valuation and Account Assignment Account Determination Account Determination Without Wizard Create automatic posting October 1998

Page 78

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

(TA OMWB) and press buttons ‘Cancel’ and ‘Account assignment’. For the 1st line item in the accounting document (posting to inventory account), select transaction BSX and display details (chart of accounts = CAUS). Look up under ‘Valuation group code’ = USRE (determined from store, company code and chart of accounts) and ‘Valuation class’ = 3100 (determined from article type), to find account 310050. For the 2nd line item in the accounting document (posting to consumption account), select transaction GBB and display details (chart of accounts = CAUS). Look up under ‘Valuation group code’ = USRE (determined from store, company code and chart of accounts), ‘Account modification’ = VBR and ‘Valuation class’ = 3100 (determined from article type), to find account 410050.

Demonstrate Customizing of Inbound Processing of Goods Movement Data Following a Store Order with NO cost center posting (see Note 0105505 in CSS) 10 minutes Prerequisite: POS inbound profile IP00 must be defined and assigned to store R316. EDI partner profile must be defined for store R316 and maintained for inbound message types WGSREQ and WPUFIB. for POS inbound profile IP00. Store order inbound processing must be customized to create a PO for (external) store orders, by adhering to the store order customizing settings created in an earlier demo. To customize, in standard customizing (TA SPRO), select Sales and Distribution POS interface Inbound Movement typedependent control of goods movements Create entry POS inbound profile..................IP00 Movement type.........................101 Rev.mvnt. type..........................102 To simulate, create a PO via store order upload: use the path from the Retail start menu (TA W10T) Retail  Distr. Retailing  POS interface Extras  Simulation  Store order Enter at header level Customer...................................R316 (rest as defaulted) at item level Identifier....................................006 (article number) Article/EAN..............................R100000 Quantity....................................2 (a number > 0 ) Default document type..............3 (create PO, otherwise error) October 1998

Page 79

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Ext. Requirement......................D-00 Press IDoc status and press POS monitor. To display the IDoc and PO-number, and note PO-number. Double-click on PO-number to display PO and point out that it is an internal PO, to be delivered from DC R300, and that no purchase order history record exist for item 1. Carry out shipping for the PO generated (create delivery, create TA, confirm picking on TA, post goods issue; cf. IRT120 Now simulate the goods movements, use the path: (TA W10T) Retail  Distr. Retailing  POS interface Extras  Simulation  Goods movement Enter at header level Customer...................................R316 (rest as defaulted). Press Goods movement. At item level, enter Qual (in column 4)....................ARTN Number.....................................R10000 MTyp.........................................101 (GR goods receipt) Quantity....................................2 (same as store order) Press IDoc status and press POS monitor. To display the IDoc and workitem created (because a production date was required with movement type 101). Execute workitem (enter yesterday’s date as production date) and redisplay IDoc in POS Monitor. Point out, that, as a result of executing the workitem, this has disappeared, and an article document (for the posted goods receipt) has been created. Display the original PO again and show, that a purchase order history record for item 1 now exist of category WE (= goods receipt).

Exercise Customizing Goods Movement Inbound Processing 25 minutes 5-20, 5-21, 5-22 Topic: Customizing Sales Data Inbound Processing Putting the Topic in Context This topic discusses the customizing of the inbound processing of sales data, both aggregated and per receipt, including payment lists, for a particular POS inbound profile.

October 1998

Page 80

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Participants should be able to:  Describe the main business process of handling sales data captured at a store, and uploaded from a store 

Explain the differences between aggregated sales and sales as per receipt



Customize (and simulate) the inbound processing of aggregated sales data



Customize (and simulate) the inbound processing of payment list data



Define transaction types (for sales as per receipt) in POS customizing



Customize (and simulate) inbound processing of sales data as per receipt



Describe the effects of the various customizing settings;



Set up conversion between SAP Retail transaction types (for sales as per receipt) and the ones used at a store.

Sales (& returns): Business Scenario See notes. Emphasize that the inbound processing of sales data requires, that the stores and articles are defined in the central SAP Retail system in terms of corresponding sets of master data, and that inventory management is active for these store/article combinations. For billing purposes, it is also required that at least one set of customer master data (anonymous or identified customer) exist in the SAP Retail system, and so are appropriate FI accounts. Note: the handling of an ‘anonymous’ customer record is both country- and Releasedependent (see remark given for slide Sales (aggregated): customizing (2/5)). Sales (& returns): Business Scenario through Sales (aggregated): Customizing (1/5) See notes.

Sales (Aggregated): Customizing (2/5) See notes. Regarding the field ‘Anon.customer’, explain: in a German tax environment (where there is only one type of tax on consumer products, corresponding to condition MWST in calculation scheme POS000), you would assign a (dummy) SD-customer defined in the system. In an American tax environment, where there are several types of tax on consumer products (corresponding to condition types STTX, CTTX, ... in calculation scheme POSUSJ) and jurisdiction codes. In Release 4.0B, you would have one POS inbound profile per jurisdiction code and assign one (dummy) customer (here: R320) to this POS inbound profile. In the master data of this customer, the jurisdiction code must be referenced (view ‘Control data’). In releases > 4.0B, the entry for ‘Anon. Customer’ can be left blank, and the system automatically takes the customer segment of the sending store, for which the jurisdiction code was maintained (view ‘Control data’).

October 1998

Page 81

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Sales (Aggregated): Customizing (3/5) through Sales (Aggregated): Customizing (5/5) See notes.

Sales Demo Preparation Check to ensure that store R316 has sufficient stock of article R100016. If ‘not’ post ‘other’ goods receipt for article R100016 at store R316 and storage location 0001, using movement type 501 (not generating a PO in the background). Record the current quantity of article R100016 at store R316. Also, make sure that R100016 has a positive moving average price in store R316, because otherwise, no accounting document will be created – see field ‘Mov. avg. price’ on logistics screen of article R100016 for store R316, button ‘Accounting’;);

Demonstrate Customizing of Sales Data Inbound Processing -- Aggregated 25 minutes Prerequisite: EDI partner profile must be defined for store R316 and maintained for an inbound message type. To maintain EDI partner profile for an additional message type, in standard customizing (TA SPRO), select Cross-Application components Distribution (ALE) Communication Manual Maintenance of Partner Profiles Maintain partner profile Enter R316 partner no. and KU for type. Select inbound parameters. Select a message type and press copy. Make the following changes: Message type.......................................WPUUMS Process code........................................WPUU. To customize aggregated sales inbound processing for POS inbound profile IP00 in standard customizing (TA SPRO), select Sales and Distribution POS interface Inbound Aggregated sales control Create entry POS inbound profile............................IP00 Inv. Management.................................X (invent. management ............................................................ without aggregation) Billing.................................................X Update rep.-based IM.......................... Statistic update.................................... Anon. customer...................................R320 ............................................................(see remark given for ............................................................ slide Sales (aggre............................................................ gated): customizing ............................................................ (2/5)) StorageLocation..................................0001 October 1998

Page 82

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Mov. type: Sale....................................251 (GI for sales) Mov. type: return.................................252 (RE for sales) Sales doc. type:...................................OR ............................................................(TA in German) Item cat. standard................................DLN Bill. type..............................................FP Calculation scheme.............................POSUSJ ............................................................(POS000 in German) Number of items..................................100 Condition type.....................................PN10 Cond.type SAP valuation price............PBEW Condition type FI valuation price........PBFI In a second session, display calculation scheme POSUSJ and draw attention to condition type RB11, by following the, in standard customizing, Sales and Distribution Basic functions Pricing Pricing control Define and assign pricing procedures Select ‘Maintain pricing procedure’. Point out the condition types for rebates (RB11), taxes, and prices (PN10, PBEW and PBFI, as assigned above). Point out significance of column ‘ActKy’ for automatic account determination. Return to the first session and remind participants, that an entry is also required for movement types 251 and 252 (as used above) in standard customizing (TA SPRO) under Sales and Distribution POS interface Inbound Movement typedependent control of goods movements Create entries POS inbound profile............................IP00 Movement type...................................251 (GI for sales) Rev.mvnt. type....................................252 (RE for sales) and POS inbound profile............................IP00 Movement type...................................252 (RE for sales) Rev.mvnt. type....................................251 (GI for sales) To simulate aggregated sales, use the following path from the Retail start menu (TA W10T) Retail Distr. Retailing  POS interface Extras Simulation  Sales. Select Aggregated sales Enter at header level Customer.............................................R316 Transact. date......................................(today’s date) At item level, enter Qual.....................................................ARTN Number...............................................R100016 Sales qty..............................................10 Sales value..........................................1978 (then, after pressing button ‘Item discount’) CTyp....................................................RB11 (Cash and carry; October 1998

Page 83

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

............................................................ ............................................................ Sales discount......................................2 Press Save.

discount for item 1)

Note: in this simulation, no tax applies (as is the case for some articles in the US). Press IDoc status and press POS monitor. Double-click on the material document associated with the IDoc and point out: field ‘SLoc’ in item, field ‘MvT in item, various details of the accounting/cost accounting documents (via button ‘Accounting docs...’).; Double-click on the billing document in the POS Monitor, and point out field ‘Payer’ in header, field ‘Billing type’ in Header  Details, condition value for RB11 and calculation scheme behind button ‘Pricing’ and ‘Analysis’, various details of 2nd accounting document through Overview Accounting Show updating of info structures S121 and S122 in RIS, using standard analyses ‘Article aggr. – POS’ and ‘Cashier’ Check again stock numbers of article R100016 at store R316. Sales (aggregated): payment lists See notes.

Demonstrate Customizing of inbound Payment type processing 10 mins Prerequisite: EDI partner profile must be defined for store R316 and maintained for an inbound message type. To maintain EDI partner profile for an additional message type, in standard customizing (TA SPRO), select Cross-Application components Distribution (ALE) Communication  Manual Maintenance of Partner Profiles Maintain partner profile Enter R316 partner no. and KU for type. Select inbound parameters. Select a message type and press copy. Make the following changes: Message type.......................................WPUTAB Process code........................................WPUT. To customize payment list data inbound processing for POS inbound profile IP00, in standard customizing (TA SPRO), select Sales and Distribution POS interface Inbound Payment list control October 1998

Page 84

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Create entry: POS inbound profile..................IP00 Anon. customer.........................R320 ..................................................(see remark given for .................................................. slide Sales (aggre.................................................. gated): customizing .................................................. (2/5)) Sales doc. type..........................OR ..................................................(TA in Germany) Bill. type....................................FP Calculation schema..................POSUSJ ..................................................(POS000 in Germany) Condition type...........................PN10 Itm cat. payment list..................TATX Number of items........................100 To simulate a payment list, use the following path from the Retail start menu (TA W10T) Retail Distr. Retailing  POS interface Extras Simulation  Sales. Select Means of Payment Enter at header level Customer...................................R316 Transact. date............................(today’s date) at item level Payment method........................PTCS (for cash payment) Final total..................................(positive integer) Press Save. Press IDoc status and press POS monitor. Point out the IDoc that was generated and the follow-on documents that were created. In a 2nd session, display the G/L account document, by following from the SAP Retail start menu (TA W10T) Accounting Financial accounting General ledger, Document Display Enter the number of the G/L account document displayed in the POS Monitor. Also use ‘Company code’ = R300 and ‘Fiscal year’ = actual year). Point out field ‘Reference’ (= number of the billing document generated), as well as account debited (= anonymous customer defined in payment list customizing for POS inbound profile IP00, i.e., R320), as well as the account credited (= checking account 110000). Exercise for customizing of payment list inbound processing 30 mins 5-23, 5-24, 5-25

October 1998

Page 85

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Sales (per receipt): transaction types (1/2) through Sales (per receipt): customizing See notes.

Sales Demo Preparation – Sales as per Receipts Check to ensure that store R316 has sufficient stock of article R100016. If ‘not’ post ‘other’ goods receipt for article R100016 at store R316 and storage location 0001, using movement type 501 (not generating a PO in the background). Record the current quantity of article R100016 at store R316. Also, make sure that R100016 has a positive moving average price in store R316, because otherwise, no accounting document will be created – see field ‘Mov. avg. price’ on logistics screen of article R100016 for store R316, button ‘Accounting’;);

Demonstrate Customizing Sales Data Inbound Processing – Sales as per Receipts, with no reference to a particular transaction type 25 minutes Prerequisite: EDI partner profile must be defined for store R316 and maintained for an inbound message type. Movement type-dependent control of goods movements must be maintained for movement type 251. To maintain EDI partner profile for an additional message type, in standard customizing (TA SPRO), select Cross-Application components Distribution (ALE) Communication Manual Maintenance of Partner Profiles Maintain partner profile Enter R316 partner number and KU for type. Select inbound parameters. Select a message type and press copy. Make the following changes: Message type..........................WPUBON Process code...........................WPUB. To customize sales as per receipt inbound processing for POS inbound profile IP00, without reference to a transaction type for sales as per receipt in standard customizing (TA SPRO), select: Sales and Distribution POS interface Inbound Control sales as per receipt; Create entry POS inbound profile............................IP00 Billing.................................................X Inv. Management................................. Update rep.-based IM.......................... Statistic update.................................... Anon. customer...................................R320 ............................................................(see remark given for ............................................................ slide Sales (aggre............................................................ gated): customizing October 1998

Page 86

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

............................................................ (2/5)) StorageLocation..................................0001 Explode art.......................................... Mov. type: Sale....................................251 Mov. type: return.................................252 Sales doc. type:...................................OR ............................................................(TA in Germany) Item cat. standard................................DLN Bill. type..............................................FP Calculation scheme.............................POSUSJ ............................................................(POS000 in Germany) Number of items..................................100 Condition type.....................................PN10 Cond.type SAP valuation price............PBEW Condition type FI valuation price........PBFI To simulate sales as per receipt, use the following path from the Retail start menu (TA W10T)

RetailDistr. Retailing  POS interfaceExtrasSimulation Sales. Select Sales as per receipt Enter at header level Customer.............................................R316 Transact. date......................................(today’s date) at item level Qual.....................................................ARTN Number...............................................R100016 Quantity...............................................2 Sales value..........................................300 and after pressing button ‘Payment methods’ Payment method..................................AMEX Final total............................................330 Card number........................................3750577301101 Validity date (to)..................................(end of current year) Authorization no.................................(positive integer) Transaction time..................................(actual time, ............................................................e.g. 1345 for 13:45) and after pressing buttons ‘Items’ and ‘Item discount’ CTyp....................................................STTX (State Tax) (**) Amount...............................................30 Press Save. Mention that ‘Sales value’ + ‘Amount’ must equal ‘Final total’. (**)Note: in Europe, final sales prices (including VAT) are uploaded to the SAP R/3 system and the tax is calculated by the system (condition type MWST in calculation scheme POS000) and posted (billing document). In the US, both the net sales price and the various taxes that apply (condition types STTX, CNTX, CITX; if any) are recorded as a separate line item, uploaded to the SAP R/3 system and then posted (billing document).

Press IDoc status and press POS monitor. October 1998

Page 87

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

This displays the IDoc generated. Point out the follow-on documents: Double click on the billing document and branch to associated accounting documents (Overview  Accounting). Double-click on the accounting document displayed on the subsequent screen and point out accounts posted, especially, the $30 tax). Verify updating of info structure S122. Use the following path from the Retail start menu (TA W10M): Info system/Planning Retailing,Standard analyses Special processes POS statistics Basket analysis. Enter the following: Site......................................................R316 Day (from)..........................................(blank) Day (to)...............................................(today’s date). If necessary, add key figure ‘Invoiced sales’ and verify that it has been updated by previous upload of sales data.

Demonstrate the Customizing for Credit Card Payment Processing 35 mins Display the existing customizing settings that led to the posting of the above credit card sale, payment type AMEX, to the corresponding G/L account. To show the definition of payment card types, in standard customizing (TA SPRO), follow: Sales and Distribution Billing Payment cards Maintain card types Point out entry for ‘AMEX’ To show the necessary settings to determine the G/L account to which credit card payments are posted, in standard customizing, first follow Sales and Distribution Billing Payment cards Authorization and settlement Maintain clearing house Account determination Step through: Maintain account determination procedures Show that account determination procedure A00001 is defined, using condition type A001 only, and assigned to billing type FP. Maintain condition type Show that condition type A001 uses access sequence A001 Maintain access sequence Show that access sequence A001 comprises tables 6 and 4, which means it first searches for an A001 record at level sales organization/payment card type, and then at level sales organization only) Assign accounts Show that no match is found in table 6 of access sequence (point out that in most live systems it would be done here because all companies want to keep a close eye on the card October 1998

Page 88

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

clearing accts by card type) A001, The access sequence A001 does find one in table 4. resulting in the posting of all credit card receivables to account 112050 in chart of account CAUS); (hint: doing the above for the first time after a system copy onto IRT may produce a short dump; simply repeat To show the necessary settings to determine the G/L account to which postings are made when clearing payment card receivables, in standard customizing, follow: Sales and Distribution Billing Payment cards Authorization and settlement Maintain clearing house Set authorization / Settlement control per account Point that receivables posted to account 112050 are cleared in account 144250 for chart of accounts CAUS.

Exercise for Customizing Sales Inbound Processing 35 minutes 5-26, 5-27, 5-28, 5-29, 5-30

October 1998

Page 89

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Unit: Monitoring tools 2 hours (plus breaks)

List of Topics in the Unit  IDoc lists and IDoc statistics 

POS statistics

Putting the Unit in Context This unit addresses how to access information about existing inbound and outbound IDocs in an operative system.

Participants should be able to:  Call up IDoc lists and IDoc statistics 

Call up the various standard analysees on POS

to retrieve information on IDocs sent and received from the system. Topic: IDoc lists and IDoc statistics Putting the Topic in Context Selection and display features of IDoc lists and IDoc statistics are discussed in order to be able to decide which to use in which situation. Participants should be able to:  Name the selection criteria for IDoc lists and IDoc statistics, 

Describe functionalities applicable to IDoc lists and IDoc statistics.

IDoc Lists/Statistics See notes.

IDoc Lists: by Generation Date/Time See notes. IDoc Lists: By Status See notes.

October 1998

Page 90

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

IDoc Statistics See notes.

Demonstrate IDoc Lists and IDoc Statistics 15 mins To show menu path to “IDoc Lists by generation date/time” and generate an IDoc list, use the path: From SAP Retail start menu (TA W10T), select Retail  Distr. Retailing POS interface, Monitor Display IDoc Chronological Choose appropriate selection (allow for a wide range for ‘Creation date’). Describe the fact that you can focus your list by any of the selection fields or leave it wide open as we are doing in the demo. Then show on the resulting IDoc list, how to narrow the focus-- click on ‘Directn’ column and then select Edit  Set filter to Directn = 2 to reduce list to inbound IDocs only. Double-click on one of the IDoc number to display its component. To show menu path to “IDoc lists by (IDoc) status” and generate an IDoc list, use the path: From SAP Retail start menu (TA W10T), select Retail Distr. Retailing POS interface, Monitor Display IDoc By status Choose appropriate selection (allow for a wide range for ‘Creation date’). On the resulting IDoc list, select a line and press button ‘Time distribution’, and keep drilling down to eventually reveil the components of one particular IDoc; To show menu path to IDoc statistics (by status groups) and generate a corresponding statistic. First, point out that IDoc status can be grouped together in status groups under starting from SAP Retail start menu (TA W10T) Tools Administration, Administration Process technology, IDoc  IDoc Basis, Control Status maintenance You can also use TA WEDI to reach the IDoc screen. On the detail-screen of each (IDoc) status, the field ‘Qualification’ determines the status group it is asssigned to. Next, call up an IDoc statistic by following, from SAP Retail start menu (TA W10t) Tools Administration, Administration Process technology, IDoc IDoc Basis, IDoc IDoc statistics; choose appropriate selection (allow for a wide range for ‘Last changed October 1998

Page 91

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

on’ and ‘Changed at’). Select Standard Evaluation. On the resulting screen, point out the various status groups in subscreens ‘Inbound’ and ‘Outbound’. Call up graphics display of statistics (button ‘Graphic Compl’). Topic: POS statistics Putting the Topic in Context The main characteristics and key figures of the three standard analyses for POS Statistics are discussed, and some basic features and functionalities available for (all) standard analyses are demonstrated. Participants should be able to:  Name the three standard analyses, and their underlying info structures 

Use the basic functionalities of standard analyses to retrieve statistical POS data, consolidated at the appropriate (characteristics) level.

POS Statistics: The Retail Information System See notes.

POS Statistics: POS Statistics See notes.

POS Statistics: Information Structures See notes.

POS Statistics: info structures S120, S121, S122 See notes.

Demonstration of (POS statistics) 20 mins To show menu path for POS statitics (within RIS) and call up one/several of the three standard analyses for POS statistics. From SAP Retail start menu (TA W10M), select Info System/Planning Retailing, Standard analyses Special processes POS statistics October 1998

Page 92

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Select the report you wish to show Article aggr. - POS Cashier Basket analyses Choose appropriate selection (allow for a wide range for ‘Day’). on the resulting Initial List, Some of the things you might show and discuss -Display standard drill-down sequence, using path: Extras  Dsp. stand drilldown -Change selection of key figures button ‘Choose key figures...’ -Drill down several times double-click on one characteristic value –Display all key figure values for one particular characteristics value double-click on one particular key figure value - etc.

October 1998

Page 93

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Unit: Background Processes Overview 30 minutes

List of Topics in the Unit Customer Enhancement Overview Workflow Overview Putting the Unit in Context This is only an overview to touch on two processes that have impact on the use of the POS interface but are entire courses by themselves. Objectives Deliver information and demonstations that allow the student to: Become familiar with Enhancements as they play a part in inbound and outbound processing. Touch upon the components necessary to set up workflow to handle inbound and outbound messages. IDoc Enhancements The slide shows how most of the POS IDocs are structured to enable customer enhancements. On the outbound these enhancements are used to carry specific data down to the stores that is not already defined in the IDoc types. On inbound, enhancements can be used to preprocess the incoming data. Since these are company specific, they are not something that we can provide. However, we do provide some partial code for customers to use, which we will look at during the demo. Also refer to notes. IDocs: Enhancements User Exits And we come back and view our IDoc structure as discussed in unit 2. We pay particular attention to the user exits that the developers put in place to allow for particular customer data. This is true of the outbound. Structure of the User Exit Fields Each of the Customer Enhancements segments contain three fields. The developers have also provided some code that can expidite creating your own Enhancement and we can see that by looking at the system.

October 1998

Page 94

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Demo, Viewing the Enhancements that are availiable in the System < 15 minutes> First we go and look at the partial code the developers have provided for POS transfers. Tools  ABAP Workbench  Repository Browser Enter XWPD in the Function group field and select Function group for the download enhancements. Press Display. Now, expand Function Modules. Note the eight exits that point to the IDoc types of the names. View EXIT_SAPLWPDA_001 Note that it tells you the program that it becomes a part of and also the include that contains the program code. Now we can look at the include LXWPDU01. Enter XWPU to view the inbound enhancements You will note that there are many many more for inbound. These contain sample code that a user can include for their pre-processing and conversions. Go back and select Utilities  Enhancements  Project Management Use F4 help and search on W* to display active projects. Or select SAP enhancements, enter WPDA0001, the active enhancement and press Display. Select WPDA001 from the subsequent list and select display components. The components are the enhancements for the convertersions that we saw in the Function group area. We are looking at this because after you create your user exit, you must create and activate a project so that it will be included in the download and upload. Back out again. . Example: Reebok wanted to send down Characteristics data as well as other article data so they used the WP_PLU user exit to get the style, color and size for each article. Thus, they could have for example 25 variations attached to a single IDoc.

Topic Summary User exits are in place so that companies can further customize the data they send to and receive from their stores. Partial code is already in place to make it easier for an ABAP programmer to tailor the exit for a customer.

Workflow Overview We touch on workflow because in Retail where we are dealing with such large amounts of data, we must have a process for only dealing with exceptions. We October 1998

Page 95

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

expect that Outbound messages will be downloaded regularly with no problems and Inbound messages will be received regularly with no problems. However, we know that from time to time problems will occur and so we use Workflow to capture the exceptions. Organizational Structure and Workflow Organizational assignment of employees is the more efficient method of assigning tasks, as is stated in the slide.

Objects of Organization Management All of these objects are linked together in PD-Org. Beginning with our Organizational Unit. In the workflow created for this course and IRT120, we will see that we have an overall Retail organization, under which there are two other organizations, the Central org and the decentralized org. Under those two groups are further division to the departments that make up the central org. and the decentral origanization.

Demo, Viewing the PD-Org created for Retail < minutes> Tools  SAP Business Workflow  Organizational plan Simple maintenance  Basic Org plan.  Display Press the Matchcode button on Org unit. Enter Retail* The system returns 50012897, press display. Note the retail company has two organizations – Central and decentral. Expand object 50012898 and note the departments. HR, Finance/controlling, Marketing, Logistics and Assortment Planning. Double click on Logistics Now we can see the staff who are assigned to logistics. Select one of the staff, for example IRT120-00, and the system displays the workcenter. When you expand the workcenter, it shows the tasks that are assigned to the workcenter.

October 1998

Page 96

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Unit : Performance Enhancers 30 minutes

List of Topics in the Unit Archiving POS Documents Reorganizing Trigger Files Reorganizing Status Files Putting the Unit in Context The IDocs that are passed to files for outbound are deleted by the receiver. On outbound that is the converter and on inbound it is R/3. However, these IDocs also reside in the R/3 database and are not deleted, so they must be archived. Likewise Change pointers and Status pointers reside in the system and the Reports must read through them all when preparing a download to determine if they should be prepared. Consequently, these should be reorganized on a reqular basis to prevent performance degredation. Objectives Discribe and display methods of archiving files and reorganizing pointer files.

Archiving POS Documents Archiving POS documents entails moving completely processed IDocs to an archive outside of the system, as this slide shows.

Demo, Archiving POS Documents < 15 minutes> Can use transaction SARA. Or the path: Tools  CCMS – Computing Center Management System DB Administration Data Archiving. Press Archive management (TA SARA). Enter IDoc into Object type. Press Customizing  Technical settings, the logical file name: ARCHIVE_DATA_FILE_WITH_ARCHIVE_LINK displays On a second session use transaction code /nFILE to determine if a path exists.

October 1998

Page 97

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

If not create the path to the archive machine. Use transaction /nWE47 Details for status. You can see in the detail screen that most of these IDoc status are blocked from archiving. So we can go not further with this demonstration. Archiving POS Documents What particularly do we archive? Technical objects – IDocs

Completely processed older than 1 week

WORKITEM

status completed, older than 1 week

Application documents – Billing SD_VBRK

older than 1 week

Inventory Mgmt MM_MATBEL

older than 1 week

Accounting Documents FI_DOCUMNT

older than 1

month Logistics Docu – PO, PReq, DEl, Sales Orders. What particularly do we have to delete? Document Flow reports use report RSWWWIDE, C type of work item and clear fields of ‘ID of work item’ and ‘Status of work item’ – older than 3 months Demo, Deleting Document Flow reports < 5 minutes> Cannot use the transaction SARA. Must use SE38: Tools  ABAP Workbench  ABAP Editor Enter RRSWWWIDE in the Program field. Press Execute, if you were going to do it. Don’t go any farther:

Reorganizing Change pointers Tools  Business Framework ALE  Administration, Periodic processing  Reorganization  Change pointers If you leave the test box checked all processed change pointers and status pointers will not be deleted. Running the process takes a bit of time, so depending on how much time you have, run it or don’t run it. Once you have consistent good transmissions, you can create a variant to run automatically through the application.

October 1998

Page 98

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Retail  Distributed Retailing  POS Interface  Outbound  Change messages On the selection screen is a field to mark for Reorganization pointers. Retail  Distributed Retailing  POS Interface  Outbound  Reorg Status Choice is for either POS interface or Assortment List.

October 1998

Page 99

SAP AG

IRT260 Retail Store Connections Unit: Store to Headquarter (Inbound Documents)

Unit : Conclusion 10 minutes

Putting the Unit in Context Revisit what has been discussed and demonstrated over the past 3 days. Remind and reinforce that Planning is key to an effective implementation and that planning entails: Considering, Evaluating, Configuring and Testing all pieces of the POS interface. The scenario slide to remind them to think about how they do business today and how they want to do business in the future. This business scenario should remind them of many of the things they must consider as they go forward. Summary is another reminder that the process is iterative and that they do have enough information to start their implementation. Open the floor for any last questions they might have.

October 1998

Page 100