Additional Settings for Production Environment

3.3.14.1 Conversions

In the Retail system and the POS system used, fields with the same meaning often contain different values. This might mean that a POS system only accepts numeric values as keys for merchandise categories, while SAP Retail uses alphanumeric values, for example.

These types of value must be converted. You can define the conversion rules by manually specifying the corresponding values in the various systems. You can also use user exits, which enable appropriate algorithms to be incorporated.

To call up conversion tables, which you can use to convert R/3 data to POS system data, choose IMG  Sales and Distribution  POS Interface  Adjustments  Conversions.

The data is converted in extension WPDA0001. Reference source code exists for the user exits contained in this extension and can be activated in an enhancement project.

If a converter is used (such as the SAP Business Connector), it converts the data when the POS system is unable to do so.

3.3.14.2 Extensions

The R/3 System provides over 100 IDoc types for standard communication, which are processed by the EDI interface. SAP Retail also provides 25 IDoc types for communication between the store and the central SAP Retail system. These IDoc types are sent via the POS interface.

In addition to the basic types that have already been defined in the SAP system, the system provides tools for creating customer-specific extensions for the existing IDoc types.

Additional data fields are provided for inbound and outbound communication in the data segments. User exits are supplied to enable these additional fields to be transferred when data is sent and received.

3.3.14.3 Reports and Batch Jobs

Definition is possible in the R/3 System of one or more variants for the reports that prepare data. These variants determine which data is to be prepared for which stores.

3.3.14.4 Outbound Processing in Background

In the BEST PRACTICES, “Output immediately” has been set in the partner profile in outbound processing for demonstration purposes. In a production environment, the output mode must be set to “Collect IDocs” and transferred to the port with a report in one step.

Rather than being set to status 03 ‘IDoc written to port’, the IDocs are then set to status 30

‘IDoc ready for dispatch’.

3.3.14.6 Job Scheduling

These types of report are scheduled using jobs. They can be scheduled with a fixed time or as successors of previous jobs. To schedule jobs, choose

System  Services  Jobs  Define Job.

When defining the steps in a job, you have to specify the ABAP program and an existing variant. To display the program name from the relevant online transaction, choose System

 Status. To create a variant, choose Goto  Variants  Save as Variant.

3.3.15 Change Versions

In production operation, manual requests are only used to transfer individual articles or merchandise categories in particular cases.

A store is usually supplied with merchandise for the first time during initialization. From then on, only change versions are generated.

If master data is changed in the system and change pointers have been activated, the system saves change pointers, which the system evaluates when the POS request is made.

Although the system only transfers the articles that have been changed, it transfers the entire data record and not just the fields that have been changed.

3.3.15.1 Initialization

SAP Menu  Logistics  Retailing  Distributed Retailing  POS Interface  Outbound

 POS Data  Initialization

3.3.15.2 Create Change Versions

IMG  Basis  Application Link Enabling (ALE)  Modelling and Implementing Business Processes  Master Data Distribution  Replication of Modified Data  Activate Change Pointers - Generally

IMG  Basis  Application Link Enabling (ALE)  Modelling and Implementing Business Processes  Master Data Distribution  Replication of Modified Data  Activate Change Pointer per Message Type

or transaction BDCP.

Change Version Requirements:

SAP Menu  Logistics  Retailing  Distributed Retailing  POS Interface  Outbound

 POS Data  Change Message

3.3.15.3 Reorganize the Change Pointers

The change pointers are updated to tables BDCP and BDCPS. To avoid these tables becoming too large, the processed or obsolete change pointers have to be deleted. The POS status must be reorganized beforehand.

Reorganize the POS Interface:

3.4 Store Order/Store Order Return

Hierarchy BC Set: /BPR3R/FIL_AUFTRG_RETOURE

Precondition

 POS inbound profile KASI has been defined in the system.

 Distribution center VZ01:

 Distribution chain for site: V001, V2, S1

 EDI partner profiles should already be maintained

 POS outbound and inbound profiles should be maintained as KASI

 Shipping point VS01 should be assigned

 Warehouse number 100

 The site has a Warehouse Management System

 Store M002:

 It should be possible to deliver goods to the store from distribution center VZ01 using distribution chains V001, V2, S1 (customer view)

 The site debitor view should be expanded for distribution chain V001, V1, S1 to be able to use the postings of unknown customer sales to the store debitor concerned.

 EDI partner profiles should be maintained

 POS outbound and inbound profiles should be maintained as KASI

 <ARTICLE1 and <ARTICLE2 should be listed in both sites and the purchasing info record should exist

 Delivery type NLR and default order category DLR must exist (store returns)

Store order

Check the store order settings in the POS inbound profile. Here, you maintain the document types of the follow-on documents generated as a result of the IDoc (type WGSREQ) being processed further.

You need to maintain inbound profile KASI for the goods movements transaction in POS Customizing.

To be able to post goods movements for the store using the POS interface, you need to identify the movement types in POS Customizing and maintain the relevant reversal movement type.

Store order return

Check the store order settings in the POS inbound profile. Here, you maintain the document types of the follow-on documents generated as a result of the IDoc (type WGSREQ) being processed further.

You need to enter the delivery type for store returns to distribution center VZ01. If you do not do this, the system will not find a delivery type and will not be able to generate a delivery of a store return.

To ensure that the return is not posted to the unrestricted-use stock in the distribution center, a returns storage location is created. In this storage location, the goods are checked

posted to the unrestricted-use stock in the distribution center.