Show TOC

Process documentationCreating Worklists for POS Transactions

 

In this process, you create a list of POS transactions, referred to as a worklist, on which you can perform a logical unit of work.

A worklist is updated, which means that POS transactions are added to it, based on the specified process step, such as the initial saving of the POS transactions to the /POSDW/TLOGF table or the processing of a particular task.

Similarly, POS transactions are deleted from a worklist based on a specified process step, such as the execution of an outbound task.

To perform a logical unit of work on a worklist, provide custom implementations for BAdI: Implementation of Index/Worklist, found in Customizing under Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP Customer Activity Repository Next navigation step POS Data Management Next navigation step POS Inbound Processing Next navigation step Tasks Next navigation step BAdI Implementations End of the navigation path.

Caution Caution

You must associate at least one worklist to each of your store profiles, as described in the Example section below, to ensure proper POS transaction data input for the SAP HANA Content for SAP Customer Activity Repository.

End of the caution.
Worklists Delivered in the SAP Standard Profile

There are three worklists included in the SAP Standard Profile:

  • 0001 Index for Unprocessed Sales Transactions: This worklist is used by the /POSDW/SALES_QUERY_RFC remote function call. You use this RFC from an SAP ERP system to perform inventory lookup functionality.

  • 0003 and 0004 Unprocessed Sales for Inventory Visibility: This worklist pair is used to collect unprocessed POS sales transactions /POSDW/TLOGUS table. The /POSDW/TLOGUS table is used by views of the Inventory Visibility Analysis virtual data model to provide near real-time inventory counts based on combination of SAP ERP inventory counts with the current unprocessed sales data stored in the SAP Customer Activity Repository.

    The unprocessed POS sales transactions are added to the /POSDW/TLOGUS table as soon as they are initially saved to the /POSDW/TLOGF table by worklist 0003.

    The list of unprocessed POS sales transactions is updated by worklist 0004 when task 2001 Material/Stock (SAP Standard Profile) is executed. This is necessary to remove any transactions that are subsequently reversed by post-void transactions from the /POSDW/TLOGUS table.

    Finally, the unprocessed POS transactions are deleted from the /POSDW/TLOGUS table by worklist 0003 when the outbound task 3001 (SAP Standard Profile) is executed on the corresponding transactions in the /POSDW/TLOGF table.

    Note Note

    The Index Active option for task 2002 must be enabled to use the 0003 Index for Unprocd Sales Trans for Invtry Visiblity worklist.

    Task 3001 (SAP Standard Profile) assumes the completion of the 2002 Material/Stock with Taxes and Discounts aggregation task (SAP Standard Profile). During aggregation, the individual transaction indices are not preserved. Therefore, to know which transactions to delete from the /POSDW/TLOGUS table once task 3001 is executed, you must maintain a list of all the transactions included in the aggregate by task 2002. This list is maintained by enabling the Index Active option for task 2002 in the Start of the navigation path POS Data Management Next navigation step POS Inbound Processing Next navigation step Tasks Next navigation step Two-Step Processing Next navigation step Define Aggregation Task End of the navigation path Customizing activity.

    End of the note.

    For more information about worklists 0003 and 0004, refer to the documentation accompanying the /POSDW/CAR_WORKLIST_US implementation of BAdI: Implementation of Index/Worklist and SAP Note 1912467Information published on SAP site.

Process

  1. Open the Define Index/Worklist for POS Transactions Customizing activity, found under Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP Customer Activity Repository Next navigation step POS Data Management Next navigation step POS Inbound Processing Next navigation step Tasks End of the navigation path.

  2. Select New Entries.

  3. Specify which profile for which you are creating the worklist.

  4. Provide an identifier and a description for your worklist.

  5. Optionally, specify a filter value of BAdI: Implementation of Index/Worklist to modify the standard SAP worklist implementation and/or to assign a logical unit of work to perform on your worklist.

    The standard worklists have the following standard BAdI implementations associated to them by default:

    • 0001: /POSDW/WORKLIST_MATERIAL_INDEX

    • 0003 and 0004: /POSDW/CAR_WORKLIST_US

    Note Note

    If no explicit BAdI filter value is specified, then the worklist identifier, specified in step 4, is assumed to represent the BAdI filter value that should be called.

    End of the note.

  6. Optionally, specify a worklist type. The type Unprocessed Sales Items (Standard) is used by the /POSDW/SALES_QUERY_RFC remote function call. Only worklists used to perform inventory lookup functionality from an SAP ERP system using the /POSDW/SALES_QUERY_RFC remote function call should have this type.

    For reasons of compatibility with previous releases, the standard worklist 0001, having no worklist type specified, is an Unprocessed Sales Items worklist.

  7. Specify the update type, that is, when to add a POS transaction to a worklist.

    • When available, specify whether to perform master data enrichment on a POS transactions when it is added to the worklist.

    • When available, specify whether to perform duplicate checking.

      The logic used to check for duplicates is contained in the /POSDW/FILTER_TRANSACTIONS implementation of BAdI /POSDW/BADI_FILTER_TRANSACTION. If you want to change the logic for duplicate checking, create a custom implementation for BAdI /POSDW/BADI_FILTER_TRANSACTION.

    • If you selected a task-related update type, specify the identifier of the task. If more than a single task is needed (for example, task 2001 and 2002), then a separate worklist should be created for each task.

  8. Specify the delete type, that is, when to remove a POS transaction from a worklist.

    If you selected a task-related delete type, specify the identifier of the task.

Example

One reason to maintain a worklist for each of your store profiles is master data enrichment. Normally, when PIPE receives POS transactions from a connected store, it does not preform any master data enrichment on the transactions until the transactions are either:

  • Loaded in the POS Workbench, or

  • Processed using one of the tasks defined for your store profile

During master data enrichment, transactions are enhanced with data such as article EAN numbers or base units of measure.

When transactions are received by PIPE, their data can be queried by SAP Customer Activity Repository virtual data models (VDMs) prior to any further transaction processing using POS Workench or tasks. In such an event, the data added by the master data enrichment would be missing.

Therefore, for each of your profiles, you must define at least one worklist, the definition of which has the Save POS Transactions option selected and the Master Data checkbox enabled. This ensures that the master data enrichment is performed as soon as transactions are saved by PIPE, regardless of any subsequent task or POS Workbench processing of these transactions.

More Information

Master Data Checks

SAP HANA Content for SAP Customer Activity Repository

Providing POS Transactions for Online Stock Queries and Inventor