SAP ABAP IMG Activity W_WB2B_BADI_TEW20 (BAdI: Set ALV Variant Key)
Hierarchy
☛ EA-GLTRADE (Software Component) SAP Enterprise Extension Global Trade
   ⤷ LO-GT-TEW (Application Component) Trading Execution Workbench
     ⤷ WB2B_TEW (Package) Trading Execution Workbench
IMG Activity
ID W_WB2B_BADI_TEW20 BAdI: Set ALV Variant Key  
Transaction Code S_PLN_62000075   (empty) 
Created on 20040205    
Customizing Attributes W_WB2B_BADI   BAdI Global Trade Management 
Customizing Activity W_WB2B_BADI_TEW20   BAdI: Set ALV Variant Key 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name WB2_ALV_VARIANT    

Use

Use this Business Add-In (BAdI) to set a separate key for storing variants.

Example

The ALV variants should be dependent on the Trading Execution Workbench (TEW) type, the business process step, mode and previous process step:

The user fills the TEW type in field "handle" for structure "disvariant". Unfortunately, there are not enough fields available to transfer the other fields directly. As a result, you must define mapping of the possible combinations to a key with four characters. Depending on the combination number, you can hadrd-code the mapping in the BAdI or create a separate database mapping table.

Requirements

Standard settings

The BAdI is dependent on filter Trading Execution Workbench Type. This BAdI is not active.

Recommendation

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:

  1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.

    The screen for creating BAdI implementations is now displayed.

  2. Enter a short text for the implementation in the Short text for implementation field.
  3. From the tab index, choose Interface.

    The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.

  4. Save your entries, and assign the implementation to a development class.
  5. Place the cursor on the method, and double-click to enter method processing.
  6. Enter the code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. Return to the Edit Implementation screen.
  8. Save the entries on the Edit Implementation screen.

    Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

  9. Choose Activate

    The code you stored in the method will be run when the application program is executed.

Further notes

Field "report" in structure "disvariant" should not be used to copy keys that have been created generically. If this is done, there is a risk that an existing ALV variant key is selected and additional variants deleted.

For more information, see the documentation for BAdI method: get_variant

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20040205 
SAP Release Created in 500