Hierarchy
⤷ LO-MDS-AL (Application Component) Allocation
⤷ WRF_AT_DDIC (Package) RTFASH: Dictionary Objects for Allocation Table Enhancements
IMG Activity
ID | WRF_AT_BADI_0005 | BAdI: Adjust Messages from Follow-On Document Generation-Fashion |
Transaction Code | S_XB4_60000182 | (empty) |
Created on | 20040701 | |
Customizing Attributes | WRF_AT_BADI | BAdI in Allocation Table |
Customizing Activity | WRF_AT_BADI_0005 | BAdI: Adjust Messages from Follow-On Document Generation-Fashion |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | WRF_X_AT_FDG_E |
Use
You can use this Business Add-In (BAd) for generating follow-up documents in Fashion. It controls which messages from purchase order generation for Fashion Purchasing are passed on to the generation log for follow-up document generation when a purchase order is created.
Requirements
You use follow-up document generation for the Fashion allocation table.
Standard settings
This BAdI is active in standard. The existing default coding deletes all messages that come from Fashion purchase order generation. Only the messages for the OTB budget are retained (message ID WRF_BUDGET). You can read the amount of the deducted OTB budget here.
The BAdI does not support multiple use and is not filter-dependent.
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
- In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
- Enter a short text for the implementation in the Short text for implementation field.
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Also see:
Method
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 | 20040914 |
SAP Release Created in | 111 |