Show TOC

Function documentationJournal Viewer Locate this document in the navigation structure

 

The Journal Viewer (JV) is an enhancement for the transaction viewer function of Loss Prevention Analytics (LPA). In LPA, you create customer-specific identification patterns, using which the system identifies critical POS transactions, and updates these transactions. In the Transaction Viewer (TAV), you can display additional and more detailed information for one of these critical POS transactions.

To display all previous and subsequent transactions for the critical POS transaction, call up the Journal Viewer.

Integration

The Journal Viewer is integrated into LPA.

Prerequisites

A prerequisite for the use of the Journal Viewer is the usage of LPA. To use LPA, you also need to use SAP POS Data Management (SAP POS DM).

As a user, you need the portal role Loss Prevention Officer. For more information, see   https://help.sap.com/bicontent   BI Content Version   Application Help   Industry Solutions   Trading Industries   Retail Trade   Store Analytics   Loss Prevention Analytics   Roles  .

Features

The Journal Viewer is divided into three areas: TAV Reference Transaction, Current Selection, and Journal. The following information is available in the individual areas:

TAV reference transaction

  • The data for the reference transaction (including the posting date and cashier)

  • A pushbutton to display the original transaction, on the far right at the same level

Current selection

  • The current criteria for selection (Selection Criteria), Store, Cashier, or POS Number, Date

  • The patterns that ranked this transaction as critical (Active Pattern), on the far right at the same level

Journal

  • The critical transactions (selection in the column Act. Pattern) and their predecessors and successors, with details

  • Information in additional columns, including discounts, cancellations, loyalty rewards, and so on

  • The reference transaction with which the journal viewer was started - it is initially selected after calling up the display, and displayed in the middle of the listed transactions

Using modification-free enhancements (BAdI implementation), your system administrators can enhance the available SAP List Viewer tables with other customer-specific information, or change the way they are displayed. This BAdI is also available for modification-free enhancements to the Web Dynpro itself.

For more information, see Extensibility of Transaction Viewer.

Activities

The Journal Viewer function is called from the transaction viewer.

  • Setting filters: To restrict the display, you can set filters in the Journal area. To do so, you click the link Filter (far right) and then see an entry line, in which you can enter the required filter values. You can use Delete Filter to see the original display again.

  • Jump to the Transaction Viewer: You can display the details for a critical transaction by clicking the corresponding link for the receipt number . The setting you made for whether the transactions are selected for the same cashier or the same POS is transferred.

  • New selection: To select other transactions for display, you can enter different selection criteria (for example, a different POS number, cashier, date, or time interval). You do this in the Selection Criteria area (top left). To start the new selection, select the Display pushbutton.

  • TAV reference: If you switch from cashier to POS number or change the date in the selection criteria, you change the display, and you no longer see the the reference transaction in the middle of the listed transactions. Using the Back to Original Transaction pushbutton, you restore the original selection criteria and the original list (with the reference transaction in the middle).

  • Printing: In the Settings for SAP List Viewer (tab page Display), you can increase the number of displayed table rows. This enables you to see more/all transactions from the respective table, in the printout from your browser's print function.

Example

In the Transaction Viewer, a critical transaction is displayed that was updated using the "discount too high“ pattern. The Loss Prevention Officer wants to view all transactions that were carried out before and after the questionable transaction. The officer wants more information to decide whether this is simply due to an operator's error or whether a manipulation is involved. The officer switches to the Journal Viewer and sees that the transaction immediately afterwards is a cancellation of the critical transaction - this means that a one-time operator's error was involved, and it was corrected immediately.

The officer can then call up the Transaction Viewer again, and investigate other critical transactions.