Ansicht
Dokumentation

W_DF_VK_0153 - BAdI: Determination of POS Transactions Outside of ERP System

rdisp/max_wprun_time - Maximum work process run time   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used to process physical inventory during opening hours in SAP Retail. The program Calculate Book Inventory (Transaction WSTI_R_PI_CALC) accesses the BAdI method GET_EVENTS to determine the POS transactions (sales or receipts) that are to be taken into account when calculating the book inventory for the count time from a non-SAP system. This can be necessary if you do not use the POS inbound interface as per receipts or the PIPE.

• If you use the POS inbound interface as per receipts, you do not need to implement this BAdI, since in this case all the required data is already available in the ERP system.

• If you use the PIPE, you also do not need to implement the BAdI, since you can request the POS transactions from the PIPE when performing physical inventory during opening hours.

Wichtige Hinweise:

• You can use the count time and the firming time to select the POS transactions for a material. Both times are specified in the inventory document item. They should only return POS transactions that are already posted in the ERP system.

• If the non-SAP system does not have the exact posting time of the POS transactions in Inventory Management in the ERP system, you can leave the corresponding table fields (CPUDT and CPUTM) blank. In this case, you must ensure that all the POS transactions have been posted after the book inventory is stored in the inventory document. The time at which the book inventory is stored is either the time at which it was explicitly firmed or the time at which the count was entered in the system.

• If you use the Adjust Book Inventory in Physical Inventory Document function when posting goods movements (control with field T159L-XBUIB), the POS transactions must be posted with the same posting date as the transaction date of the POS transaction in Inventory Management in the ERP system. If these POS transactions are not posted in the ERP system, the system is unable to distinguish which POS transaction has already changed the book inventory document. This can result in inaccuracies in calculating the book inventory for the count time.

• If you use sales sets and the POS transactions for these sales sets take place at component level, the BAdI implementation must return the sales for the sales sets correctly when you perform physical inventory for a component of one of these sales sets.

• When performing physical inventory for a value-only article, the BAdI implementation must also return the sales of all single articles that are subject to inventory management on a value basis for this value-only article.

You can implement the method GET_EVENTS to determine the POS sales from a different system. The BAdI is accessed once for each inventory document that is to be processed.

The following parameters are passed on to the method GET_EVENTS:

• PI_IKPF
  This parameter is a structure and contains the header record of the inventory document (table IKPF).

• PI_T_ISEG
  This parameter is a table and contains all the items of the inventory document for which the POS transactions must be determined.

• PI_XBUIB
  This parameter contains the value specified in field T159L-XBUIB for the corresponding store. This is the setting for the function Adjust Book Inventory in Physical Inventory Document.

You can specify the following return parameters in the BAdI implementation:

• PE_T_WSTI_BADI_POS_EVENT
  This parameter is a table and contains the POS transactions that are to be used for further calculation. The following fields are mandatory and must contain an entry: WERKS, MATNR, LGORT, VORGDATUM, VORGZEIT, CNTNR, SIGN, ERFMG, ERFME.

• PE_RESULT_CUMULATED
  Enter an X in this parameter if you summarize the POS transactions for a material and return the summarized sales quantity to the ERP system. In this case, table PE_T_WSTI_BADI_POS_EVENT should only contain one entry per material. enthalten.

• PE_BAPIRET2
  Return structure for an error message. If the system identifies an error processing the BAdI implementations, you can use this parameter to return an error message to the ERP system. In this case, the system cancels book inventory calculation for the corresponding inventory document and displays the message.

RFUMSV00 - Advance Return for Tax on Sales/Purchases   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 4960 Date: 20240523 Time: 220056     sap01-206 ( 92 ms )