Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
QI (Package) QM IMG and area menu
IMG Activity
| ID | OLQU_BADI_VE | Business Add-In for Display of Data for Usage Decision on Subscreen |
| Transaction Code | S_AL0_96000508 | (empty) |
| Created on | 20011206 | |
| Customizing Attributes | OLQU_BADI_VE | Business Add-In for Display of Data for Usage Decision on Subscreen |
| Customizing Activity | OLQU_BADI_VE | Business Add-In for Display of Data for Usage Decision on Subscreen |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | QEVA_SUBSCREEN_1101 |
Use
This Business Add-In allows you to display additional data in a subscreen of the header data (screen 1101 in program SAPMQEVA) in the transactions for the usage decision (Create, Change, Display). You can also call up an additional function by choosing a pushbutton on this screen.
Data cannot be changed here.
The relevant entries in table QALS and in structure RQEVA 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 the usage decision using this Business Add-In, the FCODE used must begin with the following characters:
+BADI1101
Example: +BADI1101_1
Standard settings
Activities
Example
You can use this Business Add-In, for example, to supplement the header area of the usage decision 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 1101 for program SAQMQEVA (usage decision).
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_1101 in screen 1101 and contained a pushbutton. This pushbutton is linked to the FCODE '+BADI1101_1'.
In the PBO of the new screen, the adapter class of the instance for BADI QEVA_SUBSCREEN_1101 is read, and the data in QALS and RQEVA is transferred (method GET_DATA).
In the implementation of the method PROCESS_OK_CODE, the value '+BADI1101_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 | 20011206 |
| SAP Release Created in | 470 |
