Hierarchy
⤷ LO-GT-TEW (Application Component) Trading Execution Workbench
⤷ WB2B_TEW (Package) Trading Execution Workbench
IMG Activity
ID | W_WB2B_BADI_TEW11 | BAdI: Change ALV Data for Agency Documents (Lists) |
Transaction Code | S_PLN_62000036 | (empty) |
Created on | 20040130 | |
Customizing Attributes | W_WB2B_BADI | BAdI Global Trade Management |
Customizing Activity | W_WB2B_BADI_TEW11 | BAdI: Change ALV Data for Agency Documents (Lists) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | WB2_ALV_AGENCY_LST |
Use
Use this method to change how data is displayed in ALV.
Example
You have defined a subtable for "EKPO" in the customer project. This table is to be displayed in ALV. The table contains the key fields "MANDT","EBELN","EBELP" and "NEW_SUB_POS". The new data fields and the new key field can be added as data fields in an append structure for data stucture "wb2_ekpo_dyn" or the ALV display structure "wb2_alv_po_item". The additional lines are structure and added in method "modify". In method "get_ext_key", the value of field "new_sub_pos" is added to key field "ext_key1" for field "e_ext_keys". If five lines are added to item "10", the table contatins "it_heads_and_items" for the item lines "10" and a table "t_ext_key" with five external numbers. By doing so, it is possible to read the additional data from the database as a later data.
Standard settings
The BAdI is dependent on the TEW type filter. The BAdI is not active.
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:
- 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.
- Enter a short text for the implementation in the Short text for implementation field.
- 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.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- 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.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Further notes
The data in the ALV display structure is a copy of the data that are transferred into the action classes. Change values has no influence on data that the action class contains. New lines are not transferred (only the external keys are transferred, as detailed above).
For more information, see the documentation for the following BAdI methods:
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 | 20040130 |
SAP Release Created in | 500 |