Hierarchy

⤷

⤷

IMG Activity
ID | RMX_QM00_SUBSCR_5000 | BAdI: Reference Object Screen for Stability Study (QT) |
Transaction Code | S_XBK_47000040 | (empty) |
Created on | 20030910 | |
Customizing Attributes | RMX_QM00_SUBSCR_5000 | BAdI: Reference Object Screen for Stability Study (QT) |
Customizing Activity | RMX_QM00_SUBSCR_5000 | BAdI: Reference Object Screen for Stability Study (QT) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | RMX_QM00_SUBSCR_5000 |
Use
This Business Add-In (BAdI) is used in trial management.
You can use this BAdI to implement the free reference object screen, dependent on a notification type, to meet your requirements.
The BAdI enables you to display data and also to maintain notification data (VIQMEL).
On the subscreen that is called for the BAdI implementation, the following data is available for the notification:
VIQMEL Notification Header
TQ80 Notification Type
MODUS Processing Mode (H = Add, V = Change, A = Display)
You can return the complete VIQMEL object, with changes, to the calling program.
Active BAdI implementations already exist in the PLM add-on for the notification types QS (StabilStudy with Mat) and QR (StabilStudy w/o Mat) provided in standard Customizing for the PLM add-on.
Use this active implementation as a template for your own implementations.
If you do not use the PLM add-on package but want to implement this BAdI, use the example code provided for the method implementations as a template.
Note: For the QT notification type, an active implementation also exists for trial management that displays the trial, the project, and the planning building block.
Requirements
In Customizing for the notification type, you have maintained screen areas for the notification header and selected O550 (Object: Free Reference Object (BAdI)) for the Object subscreen type.
Standard settings
The BAdI is active. The default code is executed automatically.
This BAdI implementation is used in trial management to display trial-specific fields on the reference object screen in the stability study.
The BAdI is filter dependent. The notification type is used as a filter for this method.
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.
Example
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | RMX_QM00_SUBSCR_5000 | 0 | HLA0006251 | Basic Data |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20030917 |
SAP Release Created in | 471 |