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_STW_WE_B006N | BAdI for Interface Control in Correction and Release Monitor |
| Transaction Code | S_ALN_01002272 | (empty) |
| Created on | 20030415 | |
| Customizing Attributes | W_STW_BADI | Attribute BAdIs in SAP Retail Store |
| Customizing Activity | W_STW_WE_B006N | BAdI for Interface Control in Correction and Release Monitor |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SRS_PDC_FIELD |
Use
Note the Enhancement Concept for SAP Retail Store Dialogs.
This BAdI is used in SAP Retail Store in the correction and release monitor of the PDC goods receipt function.
Using the methods contained in this BAdI, you can change the interface in the application mentioned above and intervene in processing.
You can save attributes for various defined fields using the FIELD_ATTR_SET_... methods (set field attributes). These control whether a field is hidden, displayed, or ready for input. The attributes are transferred to the templates and can be evaluated there so you can make changes to the interface without having to make modifications in the ERP system. You can only do this for fields that are not mandatory fields for further processing. These methods are called before the application screens are created (PBO time).
You can define as many new fields as you like and transfer them to the ITS context using the NEW_FIELD_... methods (define new fields). These methods are called before the application screens are created(PBO time).
With the READ_INPUT_.. methods (receipt of entry for goods receipt/ movement), additional fields from the ITS context can be received. These methods are not processed in the correction and release monitor but instead at PAI time after the input data is written to the SRS data object before the standard validation. Formatting can also be done here if necessary.
In the CHECK_INPUT_... methods (validation of entries) validations can be made for entries in the application. These methods are processed at PAI time after the standard validation of the input data.
In the CHECK_START_... methods (validation of the loaded reference documents), validations can be made for header and item data before the main dialog is processed.
Before calling the update function module for material documents, method PROCESSING_BEFORE_POSTING is called, with which the new fields can be attached to the input structures of the BAPI and transferred to the material document. You can also carry out your own processing in this method.
In addition, method PROCESS_BEFORE_CREATE_GM is called immediately before the BAPI BAPI_GOODSMVT_CREATE is called in the SAP Retail Store goods receipt. Here, you can save the data in separate function groups for use in the user exits or BAdIs in Inventory Management.
These methods are used to make customer-specific changes to the application and to carry out customer validations and processing. For more information, see the documentation for the individual methods.
Requirements
Standard settings
In the outbound delivery status the Business Add-In is activated. The default coding is executed automatically.
Activities
Example
See also
Methods:
Set fieldattributes for header data in release monitor
Define new fields for header data in release monitor
Validation of entries for header data in release monitor
Enrichment of material document data before posting
Set fieldattributes for item data in release monitor
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20030415 |
| SAP Release Created in | 200 |
