SAP ABAP IMG Activity RMX_QST02_STABILOT (BAdI: Change the QALS Work Area)
Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   PLM-RM (Application Component) Recipe Management
     RMXTQM (Package) Main Package - Trial: QM Aspects
IMG Activity
ID RMX_QST02_STABILOT BAdI: Change the QALS Work Area  
Transaction Code S_XBK_47000041   (empty) 
Created on 20030910    
Customizing Attributes RMX_QST02_STABILOT   BAdI: Change the QALS Work Area 
Customizing Activity RMX_QST02_STABILOT   BAdI: Change the QALS Work Area 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name RMX_QST02_STABILOT    

Use

This Business Add-In (BAdI) is used in trial management.

This BAdI method is run directly before a stability inspection lot is generated and changes the transferred inspection lot work area. For example, you can use this BAdI to provide the inspection lot short text on an individual basis or to provide your customer-specific inspection lot data.

Requirements

The interface for method CHANGE_QALS_WA contains the following parameters:

IMPORTING

I_QALS    Inspection Lot Record

I_MHIS    Table of maintenance calls; contains precisely one entry for the current call for the maintenance item

I_MPOS    Maintenance Item

FLT_VAL    Filter Value (= current inspection type)

EXPORTING

E_QALS    Changed Inspection Lot Record

E_IMP_ACTIV    Indicates that changed data is to be copied

When you implement a method, you have to:

  • Provide data for E_QALS in all cases. Ideally, you provide data for E_QALS at the start of the implementation using I_QALS with the statement move I_QALS to E_QALS.
  • Set the export parameter E_IMP_ACTIV to X, if you want the changed data to be copied when the lot is generated.

The following inspection lot data is provided and must NOT be changed:

  • WARPL
  • ABNUM
  • WAPOS
  • STRAT
  • PLNTY
  • PLNNR
  • PLNAL
  • WERK
  • HERKUNFT
  • ART
  • MATNR
  • CHARG
  • XCHPF
  • STAT32

Changing this data can result in inconsistencies and errors when the lot is generated.

The following inspection lot data is also provided. Be extremely careful if you change this data.

  • KTEXTLOS
  • QMATAUTH
  • KUNNR
  • LIFNR
  • HERSTELLER
  • LOSMENGE
  • MENGENEINH
  • LMENGEIST
  • KTEXTMAT
  • PASTRTERM
  • PASTRTERM
  • ENSTEHDAT
  • GUELTIGAB

Standard settings

The BAdI is active. If there is no active implementation for the filter value used, the default code is executed automatically.

The BAdI is filter dependent. You can define one customer-defined implementation for each inspection type.

An example implementation and a default implementation exist for this BAdI.
In the default implementation, the short text of a stability inspection lot is provided with the package number, the short text for the storage condition, and the key for the stability study.

This BAdI implementation is also used in trial management for automatically generated stability inspection lots to copy the trial number from the relevant study to the inspection lot.

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:

  1. 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.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. 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.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. 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:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

SAP provides an example implementation for the method of BAdI CHANGE_QALS_WA.
For customer-defined implementations, refer to this example implementation or to the default implementation.

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_QST02_STABILOT 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