Entering content frameFunction documentation Deleting Bonus Buys Locate the document in its SAP Library structure

Use

Bonus buys are limited by their validity period, however once created they remain available in the system. Using this function you can select and delete bonus buys according to certain criteria.

Integration

The bonus buys are deleted from all systems. They cannot be archived.

Prerequisites

When deleting bonus buys you need to keep the data basis of the SAP System consistent with the connected POS system and avoid data inconsistencies.

Features

  1. First the system shows you the available bonus buys using certain criteria.
  2. You can, for example, select the bonus buys using a promotion in which they are used, a discount type, a bonus buy category, a bonus buy type or the condition target type. You can also limit the selection using the validity period.You can choose which bonus buys you want to delete.
  3. The bonus buys are displayed in a tree, which you can sort according to various criteria (for example, creator, discount type, promotion and bonus buy).

    If you flag the Validity period completely in this time interval indicator on the selection screen, the validity period of the current condition record must not be longer than the time period indicated but must fall fully within this interval. If the indicator is not set, both time intervals can overlap.

  4. The system forwards the deletion request to the connected POS systems.

The system deletes the bonus buy entries in all the relevant tables (KONBBYH, KONBBYPRQ, KONBBYT, KONDN, KONDNS, KOTN*, STXH and STXL).

You can also delete bonus buys from Promotion Maintenance. When you do this, the system enters the bonus buy numbers and the relevant promotion number in the selection screen of the deletion program. If you select bonus buys to be deleted in the promotion, the system skips the selection screen of the deletion program.

When you create or change bonus buys, you are given the option of starting POS outbound manually. Because the bonus buys to be deleted have generally already been sent to the stores, the POS systems also need to be informed when bonus buys are deleted. The system therefore logs which bonus buys have been sent to which stores in table BBY_USED. When you delete a bonus buy, the deletion indicator is set for all the entries belonging to it. Using the entries marked, the relevant deletion information can then be sent to all the stores concerned. The table has the following format:

Field name

Data type

Check table

Description

MANDT

Clnt(3)

T000

Client

WERKS

Char(4)

T001W

POS interface: stores

BBYNR

Char(12)

 

Bonus Buy

LOEKZ

Char(1)

 

Deletion indicator for bonus buys

The following procedure guarantees the necessary information for the POS system for deletion:

  1. The system updates the entries in the table above as follows:
    1. Manual dispatch of bonus buys using program RWDPOSAN:
    2. Updates or creates entries for all stores and bonus buys for which data is available and correct at the respective port (status 3)

    3. Manual dispatch for deletion of bonus buys using program RWDPOSAN:
    4. The relevant entries are deleted in the history table, as long as the deletion information for the POS system has successfully arrived at the port

      The history table is updated in both these cases each time bonus buy data is sent successfully using the manual request of POS outbound. When using report RWDPOSAN (transaction WPMA), the system checks for each store and each bonus buy whether the bonus buy data has been sent correctly and logged in the history table. A dispatch counts as correct if EDI status 03 (Data transfer to port ok) has been achieved. If this is the case, an entry to this effect is written in the history table.

      In order to enable a successful dispatch, the relevant Customizing settings for partner profile and port must be correctly maintained.

    5. Deletion of bonus buys using program BBY_POS_DELETE

Entries in the history table marked with a deletion indicator are deleted.

The history table is updated at this point by deleting the entries that have been flagged by the actual deletion program BBY_DELETE for the bonus buy data in the OLTP system.

In all three cases the history table is updated in the background, which means that the user cannot maintain the data in the table directly.

  1. The deletion indicator is set for all the entries in table BBY_USED for the bonus buys selected for deletion by the BBY_DELETE program (transaction VBK6).
  2. The program BBY_POS_DELETE evaluates this deletion indicator and for all combinations of store and bonus buy, it informs the store that the bonus buy is being deleted The IDoc is prepared in the background by implicitly calling program RWDPOSAN, which activates the input parameter Delete selected data.

    All combinations of store and bonus buy for which the deletion processing has been sent are issued in a list.

    Finally program BBY_POS_DELETE removes all entries that had the deletion flag set from history table BBY_USED .

    SAP recommends that you schedule the program daily in the background. If the data volume expected is not too great, it can be called directly from the BBY_DELETE program.

  3. If the entries in table BBY_USED are not up to date (for example, after upgrading a system in which bonus buys have already been used but for which the deletion functionality was previously not available), the table needs to be initialized using report BBY_USED_FILL. This program recreates the history table for all clients by writing an entry for all combinations with existing bonus buys and all POS relevant stores. It is implicitly assumed that all bonus buys have already been sent to all stores.

Activities

You can start deletion program BBY_DELETE directly from the bonus buy area menu VBK0 or using transaction VBK6.

You can start the deletion of bonus buys for Promotion maintenance (transactions WAK1 and WAK2) by going to the Bonus buy tab page.

 

 

Leaving content frame