Hierarchy

⤷

⤷

IMG Activity
ID | WRF_DEP_STORE_BA_009 | BAdI: Additional Checks for Archiving |
Transaction Code | S_XB4_60000155 | (empty) |
Created on | 20040514 | |
Customizing Attributes | WRF_DEP_STORE_BADI | BAdIs for Department Store/Shops |
Customizing Activity | WRF_DEP_STORE_BA_009 | BAdI: Additional Checks for Archiving |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ARCHIEV_CHECK_E |
Use
You can use this Business Add-In (BAdI) to perform customer checks prior to archiving a department store or shop.
Once the BAdI is activated, method CHECK_DATA has to return an exception (if the object cannot be archived) or a reason why it cannot be archived.
The following two methods are available:
- CHECK_DATA
- CODE_TO_TEXT
The objects to be archived are checked in the archiving transaction (SARA) for object WS_ACSITE.
Requirements
To use this BAdI, your SAP R/3 System has to be configured as an SAP Retail system.
Standard settings
This BAdI is not active in the standard system. No default or example coding is provided or executed if the customer does not create an active implementation.
The BAdI is not filter-dependent.
The BAdI does not support multiple use.
Activities
When you start the IMG activity, you initially see a dialog window, in which you can enter the name for the implementation
If implementations already exist for this BAdI, a dialog box containing the names of the existing implementations appears. Click Create in this dialog box and continue as follows:
- Enter a name for the implementation of the BAdI in the Implementation field and then click Create
The initial screen for creating BAdI implementations appears.
- Enter a short text for the implementation in the initial screen, in field Short Text for Implementation
- Select the Interface tab page.
The Name of the Implementing Class is already filled in the tab page, because the system assigns a class name based on the name of your implementation.
- Save your entries and assign to a package.
- Position the cursor on each method and double-click to process the method.
- Enter the desired coding for your implementation between the statements method <Interface-Name>~ <name of method> and endmethod.
- Save and activate your coding, and go back to the Change Implementation screen.
- Save in the Change Implementation screen.
Note: You can also create a BAdI for the implementation and activate it later. In this case, end processing now.
- Choose Activate.
Now, when the application program runs, the coding you defined in the method also runs.
Example
Also see:
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 |