Hierarchy
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
LO-MD-MM (Application Component) Material Master⤷
WRF_DEPARTMENT_STORE (Package) Department Store / Shops
IMG Activity
| ID | WRF_DEP_STORE_BA_007 | BAdI: Customer Maintenance Screens (Maintain Shop) |
| Transaction Code | S_XB4_60000153 | (empty) |
| Created on | 20040514 | |
| Customizing Attributes | WRF_DEP_STORE_BADI | BAdIs for Department Store/Shops |
| Customizing Activity | WRF_DEP_STORE_BA_007 | BAdI: Customer Maintenance Screens (Maintain Shop) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SHOPADDSCREEN_E |
Use
You can use this Business Add-In to save customer-specific fields for each shop during mass maintenance of shops via a department store or a category.
You can position these customer-specific fields in three different tab pages:
- Tab page for title element "General Shop Data" (screen 3100)
- Tab page for title element "Shop Data for Distribution Chain" (screen 3200)
- Tab page in a separate, customer-specific title element within detailed shop maintenance (screen 4000).
You can only activate or deactivate a BAdI implementation for all three tab pages. To achieve detailed control at the tab page level, do not enter a customer program for the implementation for the tab page (deactivate).
While all the shop data can be maintained for tab page "General Shop Data" and the tab page under a customer-specific title element, you can only maintain distribution chain-specific shop data (database table KNVV) in tab page "Shop Data for Distribution Chain".
You should avoid having the "General Shop Data" tab page together with the customer-specific title element in the same implementation. When both tab pages are activated, database tables T001W, WRF1, and KNA1 are read from the "General Shop Data" tab page - even if fields from these tables have been maintained customer-specifically in the separate, customer-specific title element.
Set and get methods exist for each tab page. These methods are used to exchange data between screens in the standard program (3100, 3200, and 4000) and the customer program. The get methods have to be called in your customer program at the PBO (process before output) event; the set methods have to be called at the PAI (process after input) event. The get and set methods have a sample implementation in which this data transport is already realized. You generally only have to copy the sample implementation to your implementation of the set and get methods.
You can use method SET_TABSTRIPNAME to assign a customer-specific name for the title element (under which you can maintain the customer-specific data).
Requirements
Standard settings
The Business Add-In is not active in the standard system.
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 | 20040514 |
| SAP Release Created in | 111 |
