Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
QM-IM (Application Component) Quality Inspection⤷
QSTABI (Package) Stability Study
IMG Activity
| ID | OLQU_BADI_EE_16 | Business Add-In for Display of Data for Results Recording on Subscreen |
| Transaction Code | S_PLN_16000193 | (empty) |
| Created on | 20020418 | |
| Customizing Attributes | OLQU_BADI_EE_16 | BAdI for Display of Data for Results Recording on Subscreen (Stabi. Study) |
| Customizing Activity | OLQU_BADI_EE_16 | BAdI for Display of Data for Results Recording on Subscreen (Stabi. Study) |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | QEEM_SUBSCREEN_5000 |
Use
This Business Add-In allows you to display additional data in a subscreen of the header data (screen 5000 in function group QEEM) in the transactions for results recording (Create, Change, Display). You can also call up another function by choosing a pushbutton on this screen.
Data cannot be changed here.
The relevant entries in the tables QALS, QALT, QAPO, and QAPP for the existing inspection lot are available in the Business Add-In.
The inspection lot origin is used as the filter for this method, so that the content of the subscreen can be implemented based on a particular origin.
Requirements
If a customer-specific pushbutton is to be implemented on the subscreen for the header data in results recording using this Business Add-In, the FCODE used must begin with the following characters:
+BADI5000
Example: +BADI5000_1
Standard settings
Activities
Example
You can use this Business Add-In, for example, to supplement the header area of the results recording screen by adding a new pushbutton. This can be implemented using the method PROCESS_OK_CODE.
In this case, you can execute an additional function (for example, you can display additional data) by activating a specific OK code.
This function is, for example, available in the mySAP PLM Addon in the stability study.
The stability study contains an implementation of this BADI, which adds a supplementary pushbutton to call the stability history in the header data of screen 5000 for function group QEEM (results recording).
This implementation was performed by defining a new screen as the subscreen in a separate function group. This new screen was exactly the same size as the subscreen area BADI_SUBSRC_5000 in screen 5000 and contained a pushbutton. This pushbutton is linked to the FCODE '+BADI5000_1'.
In the PBO of the new screen, the adapter class of the instance for BADI QEEM_SUBSCREEN_5000 is read, and the data in QALS, QALT, QAPO, and QAPP is transferred (method GET_DATA).
In the implementation of the method PROCESS_OK_CODE, the value '+BADI5000_1' of the OK code calls a function module in the function group of the subscreen. This function module then calls a module for the display of the stability history using the global QALS data.
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 |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020418 |
| SAP Release Created in | 110 |
