Hierarchy
⤷ PLM-RM (Application Component) Recipe Management
⤷ RMXTQM (Package) Main Package - Trial: QM Aspects
IMG Activity
ID | RMX_QPAP_FLEX_PLAN | BAdI: Flexible Specification Selection for Stability Inspection Lots |
Transaction Code | S_XBK_47000039 | (empty) |
Created on | 20030910 | |
Customizing Attributes | RMX_QPAP_FLEX_PLAN | BAdI: Flexible Specification Selection for Stability Inspection Lots |
Customizing Activity | RMX_QPAP_FLEX_PLAN | BAdI: Flexible Specification Selection for Stability Inspection Lots |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | RMX_QPAP_FLEX_PLAN |
Use
This Business Add-In (BAdI) is used in Trial Management to change the characteristics and operations read in the standard system for inspection lots in the stability study before the system writes them to an inspection lot in the database.
For example, you can use method PLMKB_QAPO_MODIFY to control and change specifications such as target values, tolerances, and so on for a particular inspection lot, on the basis of a particular configuration. You use a building block to create stability studies and carry out activities for the study. Since, in Trial Management this building block already contains all the planning data required for the study, such as the inspection plan for the initial test, this function is not necessarily very useful for trial-related studies. For this reason, the function for flexible inspection specifications must be suppressed when an inspection lot is being created for an initial test. This implementation is used for this purpose.
Requirements
Before you activate the implementation RMXT_QPAP_FLEX_PL_16, you have to deactivate the implementation QPAP_FLEX_PLAN_16 provided by SAP.
Standard settings
The BAdI is filter-dependent. The system uses the inspection lot origin as the filter for this method which means you can enable specifications to be changed on the basis of a particular origin.
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
An example of how this Business Add-In can be used is the function for flexible inspection specifications, using method PLMKB_QAPO_MODIFY:
This enables you to change or restrict inspection specifications again.
When the plan has been selected, the system lists all the specified inspection characteristics (table T_PLMK) with the inspection specifications in a dialog box and you can select the characteristics you actually want to be checked and also change certain specifications.
This function is available, for example, in the stability study. You can use this BAdI to change the characteristics and operations read in the standard system before the system writes them to an inspection lot in the database.
For example, you can use method PLMKB_QAPO_MODIFY to control and change specifications such as target values, tolerances, and so on for a particular inspection lot, on the basis of a particular configuration.
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_QPAP_FLEX_PLAN | 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 |