Hierarchy
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
LO-SRS (Application Component) SAP Retail Store⤷
WOST_CUST (Package) Retail Store: Customizing
IMG Activity
| ID | W_DF_VK_0153 | BAdI: Determination of POS Transactions Outside of ERP System |
| Transaction Code | S_PLN_06000368 | (empty) |
| Created on | 20030704 | |
| Customizing Attributes | W_DF_VK_BADI | Attributes Enhancements Using BAdIs |
| Customizing Activity | W_DF_VK_0153 | BAdI: Determination of POS Transactions Outside of SAP R/3 |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | WSTI_BADI_POS_EVENTS |
Use
This BAdI belongs to physical inventory processing in an open store in SAP Retail. The BAdI method "GET_EVENTS" is called by the program "Calculate Book Inventory" (transaction WSTI_R_PI_CALC) to determine the POS transactions (sales or receipts) that are to be included at count time from a third-party from a third-party system. This may be necessary if you do not use the POS interface - inbound based on sales by receipt. If you do use POS interface - inbound based on sales by receipt, it is not necessary to implement this BAdI, as all the necessary data is already available in the ERP system.
Important Note:
You can use the count time and the firming time to select the POS transactions for a material. Both times are entered in the physical inventory document item. They should only return POS transactions that have already been posted in the ERP system.
Functionality
You can implement the GET_EVENTS method to determine the POS sales from another system. The BAdI us called once for every physical inventory document that is to be processed.
Parameters
The following parameters are transferred to the method GET_EVENTS:
- PI_IKPF
This parameter is a structure and contains the header record of the physical inventory document (table IKPF). - PI_T_ISEG
This parameter is a table and contains all the items from the physical inventory document for which the POS transactions are to be determined. - PI_XBUIB
This parameter contains the value that is set in field T159L -XBUIB for the store concerned. This is a setting for the function "Adjust Book Inventory in the Physical Inventory Document".
You can fill 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 should be used in further calculations. The following fields are obligatory fields and must be filled: WERKS, MATNR, LGORT, VORGDATUM, VORGZEIT, CNTNR, SIGN, ERFMG, ERFME. - PE_RESULT_CUMULATED
Write the value "X" in this parameter if you are already aggregating POS transactions for a material and sending the aggregated sales quantity to SAP R/3. In this case, the table PE_T_WSTI_BADI_POS_EVENT can only contain exactly one entry for each material. - PE_BAPIRET2
Return structure for an error message. If an error occurs during the BAdI implementation process, you can return an error message to the ERP system in this parameter. In this case, the calculation of the book inventory for the physical inventory document is terminated and the message is output.
Requirements
Standard settings
Activities
Example
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20050221 |
| SAP Release Created in | 200 |
