Use

This Business Add-In (BAdI) is used in the Extended Warehouse Management (SCM-EWM) component.

You can use this BAdI to enhance the selection screens with user-defined fields in the transactions for warehouse

requests in deliveries.

The BAdI is called when a query is processed in the following transactions:

o Maintain Expected Goods Receipt (/SCWM/EGR)

o Maintain Inbound Delivery (/SCWM/PRDI)

o Maintain Outbound Delivery Order (/SCWM/PRDO)

o Maintain Outbound Delivery (/SCWM/FD)

o Maintain Posting Change (/SCWM/IM_PC)

o Maintain Internal Stock Transfer (/SCWM/IM_ST)

o Maintain Production Material Request (/SCWM/PMR)

Note that the BAdI is also called when a query is processed in transaction Pickup (/SCWM/SGI), but as you cannot

enhance the selection screens in this transaction, an active implementation of the BAdI should not influence the

behavior of the transaction.

Requirements

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot

Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

o You implement this BAdI to allow the enhancement of the selection screens.

o You must also add the new selection fields you want to be available for the enhancement in an append

structure to the following enhancement structures:

- /SCWM/S_EES_SEARCH_ENH_EGR

Enhancement structure for enhancements in transaction /SCWM/EGR

- /SCWM/S_EES_SEARCH_ENH_PDI

Enhancement structure for enhancements in transaction /SCWM/PRDI

- /SCWM/S_EES_SEARCH_ENH_PDO

Enhancement structure for enhancements in transaction /SCWM/PRDO

- /SCWM/S_EES_SEARCH_ENH_FD

Enhancement structure for enhancements in transaction /SCWM/FD

- /SCWM/S_EES_SEARCH_ENH_PC

Enhancement structure for enhancements in transaction /SCWM/IM_PC

- /SCWM/S_EES_SEARCH_ENH_PWR

Enhancement structure for enhancements in transaction /SCWM/PMR

- /SCWM/S_EES_SEARCH_ENH_ST

Enhancement structure for enhancements in transaction /SCWM/IM_ST

You have the following options for naming the components in the append structures:

- ZZ<logical field name> or YY<logical field name> if the field with the corresponding logical fieldname

should be used 1:1 for the selection of the document

- ZZ<any field name> or YY<any field name>

If your components are named with ZZ<logical field name> or YY<logical field name>, this BAdI needs to be

implemented only if you want to enable wildcard selection for reference documents.

If your components are named ZZ<any field name> or YY<any field name>, you must implement this BAdI to

map the selection table to a selection table using logical fieldnames that can be used for subsequent document

selection. This is especially the case if the logical fieldnames are CHAR30 as you have only CHAR28 for the

definition of the component name due to the leading ZZ and YY.

For more information about Logical Field Names, see Define Logical Field Names.

Note that you can adjust the selection screens according to your needs by using the Hide Field checkbox in Variant

Maintenance. In the Advanced Search screen area, choose the Administer Search Queries button. In the

Administer Search Queries dialog box, choose the Change Search Query button to open the Variant

Maintenance screen.

If you have already enhanced the selection once and you want to add an additional field to the selection, we

recommend that you add the field at the end of the structure, so as not to harm saved user search queries. For the

same reason, we do not recommend that you remove a field from the structure once it has been used productively.

If you need to do one of these changes, we recommend that you delete the saved queries first and re-create them

afterwards. (For the corresponding main program of the transaction, see database table /SCMB/QUERIES.) If you

cannot do this, note that you can also delete dedicated saved search queries within the corresponding transactions,

in the case of any issues due to incompatible data formats. In this case, deletion is required and re-creation is

mandatory based on the single case.

Example

You can find example implementations in the BAdI Builder on the Enhancement Spot Element Definitions tab in the

Implementation Example Classes section.

The following example implementations are available:

o /SCWM/CL_EI_DLV_UI_SELECTION

Contains the following examples for the modification of the selection table:

- Simple mapping of selection-screen fields to delivery fields

- Selection by a non-delivery field (product group)

- Enabling wild-card searches for a customer-specific reference document

See also

BAdI method documentation:

o MODIFY_SELECTIONS

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for SAP

NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release and then Application

Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application Server ->

Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development ->

Enhancement Framework.