sap offline word template€¦ · web viewnote for the customer project team: instructions for...

Test ScriptSAP Customer Activity Repository, retail applications bundle 2.0May 2017English

CUSTOMER

POS Data Transfer and AuditID: R72

Table of Contents1 Test Description 3

2 Prerequisites 62.1 System Access and Roles 62.2 Preliminary Steps 7

3 Overview Table 8

4 Test Procedures 94.1 Import POS Data from XML file 94.2 Check POS Transaction Details 114.3 POS Data Processing – One-Step Tasks 144.4 POS Data Processing – Aggregation Tasks 164.5 Check Entries in Table TLOGF 18

5 Appendix 225.1 Process Integration 22

5.1.1 Preceding Processes 225.1.2 Succeeding Processes 22

Document History

Revision Change Date Description

0 October 31, 2016 Published Version

Note for the customer project team: Instructions for the customer project team are highlighted in yellow and should be removed before hand -over to project testers. The appendix is included for internal reference, in particular to support A2O, and should also be deleted before hand-over to the customer, unless deemed helpful to explain the larger context. If there are any special requirements that do not fit into the template, add instructions to the appendix.

POS Data Transfer and AuditTest Procedures

CUSTOMERError: Reference source not found 2

1 Test DescriptionPOS Data Transfer & Audit is the central SAP application for processing and analyzing cash register information as core part of the SAP Customer Activity Repository. It enables you to transfer, enrich, monitor and validate all of your POS data quickly and efficiently.

Business Benefit POS Data Transfer & Audit provides a comprehensive POS tool set for data capturing, sales auditing and distribution of POS data. It's scalable up to the largest, fastest growing retailers. It allows a flexible and central validation and verification of store sales data as well as financial and logistical data generated in the store and

provides store insight related to store processes and employee behavior

POS Data Transfer & Audit collects point-of-sale transaction data from the cash registers of the connected stores. These data are handed over to a defined receipt interface provided by POS data transfer and auditing. This interface can either be a standard (flattened) BAPI interface, a structured RFC interface or an enterprise service interface, providing an interface to cover most needs regarding POS data. The POS transaction data is received by the repository in form of transaction logs (TLOGs), which are processed by the POS Inbound Processing Engine (PIPE), the central component of POS data transfer and auditing.



Once the POS transactions are received, PIPE runs several processing activities, such as master data validation, sales auditing, POS transaction data summaries and sending of POS transaction data to follow-on applications on the necessary level of detail or aggregation. The POS Workbench, the PIPE user interface, enables monitoring, error handling and process control. POS transaction data is made available to consuming applications through virtual data models and individual SAP HANA views.

The major features are:

POS Inbound POS connection, for example via SAP Process Integration (SAP PI) Transfer and mapping of the POS data Data encryption for PCI DSS (Payment Card Industry Data Security Standard) Extensibility of the inbound interface

POS Data Processing Basic data validation, ability to implement own check rules Efficient error handling and intuitive user interface Flexible set-up and control of processing steps Tracking of data changes and access to encrypted data

POS Data Distribution Aggregation/enrichment of data for subsequent processing Intra-day data preparation Easy to implement outbound framework Different outbound options to trigger follow-on

NoteAll references to POS Data Management in this documentation refer to the software component included in the SAP Customer Activity Repository application and not to the SAP POS Data Management application.The SAP HANA Customer Activity Repository rapid-deployment solution delivers automated content to accelerate the implementation of this scope item.1The SAP HANA Customer Activity Repository rapid-deployment solution is offering pre-built content for reports in the area of Multichannel Sales Analytics, Inventory Visibility and Sales Reports.

1 Please note that in case you have a productive SAP POS Data Management in place, you need to do a migration project instead of implementing this scope item.POS Data Transfer and AuditTest Procedures


This business process document helps you to make sure that you have the POS pre-requisites in order to run reports based on POS data.This document provides a detailed procedure for testing the scope item POS Data Transfer and Audit after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in its own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be added.



2 PrerequisitesThis section summarizes all prerequisites to conducting the test in terms of systems and preliminary steps.

2.1 System Access and RolesThe test is conducted in the following systems:

System DetailsSAP Customer Activity Repository (SAP CAR)

<Server>: <Instance>:<System ID>:<Client>:

Use the following standard test users or assign roles to testers, respectively:

Business Role Business Role Description Business Role ID Log OnPOS Inbound Processing Engine (PIPE) Administration

The business role contains administrative activities that should not be carried out by normal users. These include deleting data and explicitly reconstructing index records

/POSDW/ADMINISTRATOR Test user: <userid>Password: <password>

Sales Auditor/POS Monitoring The business role of the Sales Auditor includes tasks for the daily monitoring of the POS inbound including analyses and evaluations.

/POSDW/SALES_AUDIT Test user: <userid>Password: <password>



2.2 Preliminary Steps In order to implement the pre-requisites, you can refer to the quick guide of SAP HANA Customer Activity Repository rapid-deployment solution and the configuration guide R70. The rapid-deployment solution is offering automated content delivered as a Best Practices Add-On, including e.g. a BCset, eCATT. This automated content takes care of the configuration of the solution. Before you start with the steps described in the test script, make sure that the Best Practices Add-On is installed in your system and the activation was done.



3 Overview TableThe scope item POS Data Transfer and Audit consists of the following process step.

Process Step, Report or Item Business Role Transaction Expected ResultsImport POS Data from XML file System Administrator /n/POSDW/XMLI POS data imported successfullyCheck POS Transaction Details System Administrator /n/POSDW/MON0 POS transaction in verified successfullyPOS Data Processing – One-Step Tasks System Administrator /n/POSDW/PDIS Tasks in completed statusPOS Data Processing – Aggregation Tasks

System Administrator /n/POSDW/PDIS Tasks in completed status

Check Entries in Table TLOGF System Administrator Tools ABAP Workbench Overview Data BrowserTransaction code: SE16

All tables are filled with data



4 Test ProceduresThis section describes test procedures for each process step that belongs to this scope item.The test should take around 60 minutes.

4.1 Import POS Data from XML file

Test AdministrationCustomer project: Fill in the project-specific parts (highlighted).Test Case ID <X.XX> Tester Name Testing Date Click here to enter a

date.Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration 10 Minutes

PurposeIn order to test the POS Data Transfer and Audit, you need to generate POS Data first.POS Data can be generated by inbound IDoc, RFC call, and XML file. In this process step you use an XML file to generate POS test data. It contains POS transactions with Sales Movement, Total Records, Financial Transitions and Control Transitions.

Procedure

Test Step #

Test Step Name Instruction Expected Result Pass / Fail / Comment

1. Put XML file containing POS data on local PC location

Copy Sample POS Data XML file to local folder XML file is prepared for import



Test Step #


XML file contains sample POS transactions. To use it, you need to modify the master data in this xml file based on your data.POS_DTA_Sample_Data.xml is used for SAP ERP as source system.POS_DTA_Sample_Data_S4H.xml is used for SAP S4/HANA as source system

2. Log on Log on the SAP Customer Activity Repository system

3. Import XML file containing POS data

Run tcode /n/POSDW/XMLI- Store: <your store number> for

example: M002- Posting Date: <current date>- Cashier or Name: <your name>- Current Time Stamp: X- File Name: <your local folder>\

POS_DTA_Sample_Data.xmlOr <your local folder>\POS_DTA_Sample_Data_S4H.xml

- Processing log:- Issue log: X- Choose Execute to import data

POS data is imported successfully

4.2 Check POS Transaction Details

Test AdministrationCustomer project: Fill in the project-specific parts (highlighted).POS Data Transfer and AuditTest Procedures


Test Case ID <X.XX> Tester Name Testing Date Click here to enter a date.

Responsibility <State Service Provider, Customer or Joint Service Provider and Customer> Duration 20 Minutes

PurposeIn this process step you check the details about the imported POS transactions using the POS workbench.

Procedure

Test Step #



2. Switch to User MenuClick User Menu

3. Check transactions in the POS workbench

User Menu > PIPE Workbench > POS WB: Selection and Overview (transaction /n/POSDW/MON0)General Settings:

- Store: <your store number> for example: M002

POS Transactions:Day/Status/Type tab

- Posting Date: <current date>Header tab

- Cashier or Name: <your name>For all other criteria use the default settings.

- Choose Execute to access the data.

Transaction details are available in POS Workbench

4. Check the Transaction Summary

Expand All Nodes to see POS transaction Summary

- Transition Status

Transaction summary verified successfully



Test Step #


- Transaction Number- Total Volume- …

5. Check the Sales Movement Overview

Double click on Sales Movement to check overview:

- Status- Sales Total- Transaction Type- POS Number- …

Click to check the task status overview

Sales movement overview verified successfully Tasks CT01 (Check for Duplicate

Transaction Numbers), CT02 (Check if Data in Retention

Period) CT03 (Check for master data and

transaction balancing) CT04 (Check and Enrich the

master data) PT99 (Validation and Status

Tracking Task) TA93 (Determine Status of

Transaction Data) TA96 (Determine Seasons in

Transactions)are in status completed.

TA96 (Determine Seasons in Transactions) is only available when FMS (SAP Fashion Management) is used as source system

6. Check the Sales Movement Details

Double click a transaction line in sales movement overview to check the sales movement details:

- Sales Item Data- Means of Payment

Sales movement details verified successfully

7. Check the Total Records Overview Choose to go back to the POS

Workbench and double click Totals Records:- Status- Transaction Index- Transaction Type- POS Number- …

Total records overview verified successfully CT01 (Check for Duplicate


Period) CT04 (Check and Enrich the

master data) CT30 (Check Balancing for Total



Test Step #


Click to check the task status overview Transactions) PT99 (Validation and Status


Transaction Data)are in status completed.

8. Check the Balancing Details

Click in the Total Records Overview and check balancing details:

- Variance- Value in TotRec- Total Value- …

Balancing verified successfully

9. Check the Financial Transactions Overview Choose to go back to the POS

Workbench and double click on Financial Transactions to check overview:

- Status- Transaction Index- Transaction Type- POS Number- …

Click to check task status overview

Financial transactions overview verified successfully CT01 (Check for Duplicate


Period) CT04 (Check and Enrich the

master data) PT99 (Validation and Status


Transaction Data)are in status completed.

10. Check the Financial Transactions Details

Double click a transaction line in Financial Transactions Overview to check financial transactions details:

- Financial Transaction

Financial transactions details verified successfully

11. Check the Control Transactions Overview Choose to go back to the POS

workbench and double click on Control Transactions to check the overview:

- Status

Control transactions overview verified successfully CT01 (Check for Duplicate


Period)POS Data Transfer and AuditTest Procedures


Test Step #


- Transaction Index- Transaction Type- POS Number- …

Click to check the task status overview

CT04 (Check and Enrich the master data)

PT99 (Validation and Status Tracking Task)

TA93 (Determine Status of Transaction Data)

are in status completed.12. Check the Control

Transactions DetailsDouble click a transaction line in the Control Transactions Overview to check control transactions details

Control transactions details verified successfully

4.3 POS Data Processing – One-Step Tasks



PurposeTasks are operations on the POS transaction data.The following types of tasks exist:

- Supplying follow-up systems such as SAP BW or SAP ERP with POS data.- Tasks carried out externally or manually that can be recorded in the PIPE.

An example of this would be the sales audit, which can be mapped as a task. The sales auditor can then record the task in the PIPE.- Performance-intensive checks that are too performance-intensive for rules. For such checks it makes sense to store the result as the status of the

task.The tasks have a status that indicates whether they are completed, incorrect, cancelled or refused, and so on.



Procedure

Test Step #




3. Run POS Data Parallel Processing

User Menu > POS Processing > POS Data Parallel Processing (transaction /n/POSDW/PDIS)

- Task Code: enter CT10 (Check for Receipt Numbers Without Gaps),

choose to select further tasks: PT09 (Create IDOC WPUBON), PT12 Generate IDOC WPUFIB), choose Execute.


- Posting Date: <current date>

Choose Other selections:- Cashier or Name: <your name>

Choose Execute

POS Data Parallel Processing completed successfully







Transaction details are available in the POS Workbench



Test Step #


Choose Execute to access the data.5. Check the Task CT10

StatusChoose Expand All Nodes and double click on Sales Movement and Click to check the task status overview

Tasks CT10 are in status completed.There is no gap in Transaction numbers

6. Check the Task PT09 Status

Double click on Sales Movement and click to check the task status overview

Tasks PT09 are in status completed.


Double click on Financial Transactions and click to check the task status overview


8. Check the Outbound IDoc WPUFIB ‘FI Documents’generated by Task PT12

Double click on Financial TransactionsClick Expand notes and find Outbox: IDocDouble Click IDoc.

IDoc WPUFIB ‘FI Documents’ was generated successfully

4.4 POS Data Processing – Aggregation Tasks



PurposeThe aggregation task controls how POS transactions are updated in a POS aggregate.



Procedure

Test Step #




3. Run POS Data Parallel Processing

User Menu > POS Processing > POS Data Parallel Processing (transaction /n/POSDW/PDIS)

- Task Code: enter PT20 (Material/Stock with Taxes and

Discounts), choose to select further tasks: PT21 (Means of Payment) and choose Execute


- Posting Date: <current date>

Choose Other selections:- Cashier or Name: <your name>- Choose Execute

POS Data parallel processing completed successfully







Choose Execute to access the data.

Transaction details are available in the POS Workbench



Test Step #



Choose Expand All Nodes and double click on Sales Movement and click to check the task status overview

Tasks PT20 are in status completed

6. Check the Material/Stock with Taxes and Discounts Aggregation Records generated by Task PT20

Open a new session and run transaction SE16Enter the table name /POSDW/AGGR01 and choose enter and Execute

Aggregation records generated successfully


Go to the session with the POS Workbench and double click on Sales Movement and click to check the task status overview


8. Check the Means of Payment Aggregation Records generated by Task PT21

Run transaction SE16Enter the table name /POSDW/AGGR03 and choose enter and Execute

Aggregation records generated successfully

4.5 Check Entries in Table TLOGF



PurposeTo ensure that the analytics reports delivered with the SAP HANA Customer Activity Repository rapid-deployment solution can work smoothly, you should check if the entries in the TLOG table are filled correctly.



Procedure

Test Step #



2. Switch to SAP MenuClick SAP Menu

3. Access the TLOGF table SAP Menu >Tools > ABAP Workbench > Overview > Data Browser (transaction SE16)Enter the table name /POSDW/TLOGF and

choose Table Contents F7You can restrict the datae.g. by store or date

4. Select the POS data created by XML file

Click Settings and > Fields for Selection, make sure following fields are selected.

- RETAILSTOREID- BUSINESSDAYDATE- OPERATORID- RECORDQUALIFIER

and click Execute EnterInput following values

- RETAILSTOREID: <your store number> for example: M002

- BUSINESSDAYDATE: <current date>

- OPERATORID: <your name>and click Execute

The TLOGF table is shown

5. Check the entries in the TLOGF table

Compare with transactions show in POS workbench. Check entries in the fields, listed in the table below

Data value in TLOGF is same as the imported POS transitions from XML file

You are able to run the reports

6. Check Season information in POS Transaction Click Back F3

When task TA96 (Determine Seasons in Transactions) is completed successfully, the season information

only available when FMS (SAP Fashion Management) is used



Test Step #


Input following values- RETAILSTOREID: <your store

number> for example: M002- BUSINESSDAYDATE: <current

date>- RECORDQUALIFIER: 5- OPERATORID: <your name>

and click ExecuteCheck following fields for Season Data from FMSMATERIALNUMBERFSH_SEASON_YEARFSH_SEASONFSH_COLLECTIONFSH_THEME

(such as the season year, season, fashion collection, or fashion theme) can be determined successfully in POS transaction line items.

as source system

MANDT System ClientRETAILSTOREID StoreBUSINESSDAYDATE Posting DateTRANSINDEX Transaction IndexROWKEY 2 byte integer (signed)BEGINTIMESTAMP Start of TransactionENDTIMESTAMP End of TransactionCALYEAR YearCALMONTH MonthsCALDAY DayCALHOUR HourCALWEEK WeekSTORECURRENCY Local CurrencyITEMID Article Identifier



UNITS Sales QuantitySALESUOM Sales UnitSALESAMOUNT RetailNORMALSALESAMT Norm. Sales ValueCOST CostsMATERIALNUMBER Material NumberMERCHANDISECAT Material GroupBASEQUANTITY Quantity in Base UNBASEUOM Base Unit of MeasureORDER_CHANNEL Order Channel IDCUSTCARDNUMBER Card Number (CARDNUMBER)CUSTOMERQUALIFIER Qualifier for Customer NumberOFFERID Offer IDPROMOTIONID Promotion NumberFSH_SEASON_YEAR Card Number (CARDNUMBER)FSH_SEASON Qualifier for Customer NumberFSH_COLLECTION Offer IDFSH_THEME Promotion Number



5 Appendix

5.1 Process IntegrationThe process to be tested in this test script is part of a chain of integrated processes.

5.1.1 Preceding ProcessesYou may first have completed the following processes and conditions before you start with the test steps:

Process Business ConditionImplementation of POS Data Transfer and Audit

All POS data are available to run the reports

5.1.2 Succeeding ProcessesAfter completing the activities in this test script, you can continue testing the following business processes:

Process Business ConditionSAP Smart Business for Multichannel Sales Analytics

The SAP HANA Customer Activity Repository rapid-deployment solution enables you to quickly leverage the SAP Smart Business Multichannel Sales Cockpit providing category managers with real-time insight into sales activities across multiple sales channels.

SAP Lumira for Inventory Visibility and Sales Reports

SAP HANA Customer Activity Repository rapid-deployment solution supports real time visibility into store-level current inventory to improve stock performance and real-time insight into POS sales performance with pre-built analytics leveraging SAP Lumira.



Typographic Conventions

Type Style

Description

Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.Textual cross-references to other documents.

Example Emphasized words or expressions.EXAMPLE Technical names of system objects. These include report names, program names, transaction

codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example>

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .



www.sap.com/contactsap

© 2017 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark