Restricting dropdown data for BP Grouping field

[Former Member]

Hi all,

I am having a problem with restricting what data is displayed in the Business Partner Grouping dropdown. We are currently on MDG7.0 SP03.

My first thought was to assign my own SH (and SH exit) to the field/data element to restrict the data.

I assigned a Search Help to the BU_GROUP attribute on the BP model, but this did not work.

My Search Help:

In the the Web Dynpro UIBB BS_BP_DETAILS, for field GROUPING I changed the display type to "Input Field". But there was no Search Help property within the Display Type Dependent Properties area.

For some fields with display type "Input Field" you can enter a Search Help.

Does anyone know what drives whether the "Search Help" property is displayed?

I noticed the Data Element BU_GROUP does not have a Search Help assigned, but this requires an access key which I do not have.

I looked at the BADI: Adjust User Interface for Single Processing (USMD_UI_EVENT2). Can this BAdI still be used? I thought the USMD_ENTITY_VALUE2 screens are not used except for Finance.

I feel that I am missing a simple step. Any suggestions on how I can restrict the displayed data in the GROUPING dropdown (whether it is via a BAdI, search help with SH exit or another method) would be appreciated.

Thank you,

Peter

[michael_theis · Accepted solution]

Hi Peter,

in the MDG-BP UIs, the easiest way is using a custom feeder class that inherits from the SAP feeder. Then you can use redefinitions of different methods to adjust the field accordingly:

- If you want to filter out undesired values only and keep the dropdown, it'd be sufficient to redefined method GET_ATTR_VALUE_SET for the specific field (others should do a parent call!).

- If you want to change the dropdown to an input field and offer a more complex search help, you could use GET_DEFINITION to add an "OVS" or "DDIC" search help to the field. In case of "OVS" further methods need to be implemented for providing the search logic.

http://scn.sap.com/docs/DOC-7858 provides a couple of how-to's you might find helpful:

- Custom Feeder Class: http://scn.sap.com/docs/DOC-31882

- Filter Input Helps: http://scn.sap.com/docs/DOC-31886

Best regards

Michael

[Former Member · Accepted solution]

Thanks for the quick reply Michael.

As per your suggestion, I'll redefine the method GET_ATTR_VALUE_SET and will mark this thread as answered once tested.

Regards,

Peter

[Former Member · Accepted solution]

Hi Michael,

Using a custom feeder class that inhertis from the SAP feeder and redefining the method GET_ATTR_VALUE_SET worked perfectly.

Thanks you,

Peter