Hierarchy

⤷

⤷

IMG Activity
ID | RMSA_VAI_ADD_INF | BAdI: Extension of Table-Based Value Assignment Dialog |
Transaction Code | S_XBI_19000061 | (empty) |
Created on | 20021021 | |
Customizing Attributes | RMSA_VAI_ADD_INF | BAdI: Extension of Table-Based Value Assignment Dialog |
Customizing Activity | RMSA_VAI_ADD_INF | BAdI: Extension of Table-Based Value Assignment Dialog |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | RMSA_VAI_ADD_INF |
Use
This Business Add-In (BAdI) is used in the Recipe Management component (PLM-RM), among others.
You can use this BAdI in Recipe Management to define the behavior of the process parameter dialog. The system is shipped with default coding that you can use as a template for implementing your own functionality.
The BAdI methods are called as soon as you call up the process parameter dialog.
When designing your implementation, remember that the BAdI is not only used in the Recipe Management component (PLM-RM). Make sure that the default code for other components is not changed.
Requirements
Standard settings
- The Business Add-In is active by default. The default code is executed automatically.
- The Business Add-In is dependent on a filter. You can create a separate implementation for each recipe object.
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
See also
Methods
Add Application-Specific Characteristics
Determine the 'ALV Outtab' Table
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | RMSA_VAI_ADD_INF | 0 | ALN0000101 | Recipe Management |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20021022 |
SAP Release Created in | 210 |