SRM7.

0 UI-Enhancement for Customers

Supplier Master Data
Adding a mainview with table data

1 Introduction..................................................................................................................... 2

2 Data Dictionary Objects ................................................................................................. 3

2.1 Create a structure with your fields........................................................................................................3

2.2 Create an append-structure with your fields........................................................................................3

3 BAdI implementations.................................................................................................... 4
3.1 Create an implementation of BAdI /SAPSRM/BD_FPM_OIF_MAINV_DEF ..........................................4

3.2 Create an implementation of BAdI /SAPSRM/BD_PDO_TE_BPSUPP_SAVE......................................5

3.3 Example data .........................................................................................................................................5

4 Customizing: Metadata maintenance............................................................................ 6

4.1 Maintenance view /SAPSRM/V_WD_TE ................................................................................................6

4.2 Maintenance view /SAPSRM/V_WD_TEC .............................................................................................7

4.3 Maintenance view /SAPSRM/V_MDFSBC: ............................................................................................8

4.4 Maintenance view /SAPSRM/V_MDFSBC_DEFAULT: ..........................................................................9

1 Introduction
Up to SRM5.0 the SAP consulting note 675800 provided customers with an option to do field
enhancements on SAPGUI for transaction BBPMAININT using a BAdI implementation.
This functionality is obsolete as of SRM6.0, since the UI technology has been switched from ITS
screens to Web Dynpro ABAP.

As of SRM7.0 SAP offers customers / industries to enhance the Web Dynpro ABAP-UI of supplier
master data by adding an additional main view and a sub view displaying a table with their own data
SAP notes 1359403 and 1358045 support this functionality.

The enhancement of the external business partner object supplier for customers is described step by
step in the next chapters of this document.

The SAP Web Dynpro ABAP UI of a supplier with an enhancement could look like shown in figure 1:

Figure 1: SAP Web Dynpro ABAP UI of supplier master data enhanced by a main view with table
data.
2 Data Dictionary Objects

Use transaction SE11 in order to perform the following steps:

2.1 Create a structure with your fields

Create a structure in your namespace and add the fields, which you would like to display in the table
on your main view on the Web Dynpro UI of supplier master data.

2.2 Create an append-structure with your fields

Create an append-structure to structure INCL_EEW_CST_BPSUPPLIER. Its component has to be an
include and its component type in your namespace has to be of your DDIC-type mentioned in step 2.1.
3 BAdI implementations
Use transaction SE19 in order to create the following BAdI implementations.

3.1 Create an implementation of BAdI /SAPSRM/BD_FPM_OIF_MAINV_DEF

In order to add a main view with sub view and a table to the UI of the supplier, create an
implementation of BAdI /SAPSRM/BD_FPM_OIF_MAINV_DEF (enhancement spot
/SAPSRM/BD_FPM_IDR_OIF_EXT) in your namespace.

Implementing method DEFINE_MAINVIEW you have to define your main view, data for User Identity
Building Block (UIBB) and your sub view.
Refer to figure 2 how to do the implementation. Enter a description for your main view in field
ls_mainview-name. Enter a description for the name of the sub view too.

No filter values are required.

Figure 2: Example coding of a possible customer implementation of BAdI method

/SAPSRM/BD_FPM_OIF_MAINV_DEF~DEFINE_MAINVIEW.
3.2 Create an implementation of BAdI /SAPSRM/BD_PDO_TE_BPSUPP_SAVE
In order to display/maintain table data on your newly created mainview (refer to step 3.1) , create an
implementation of all methods of BAdI /SAPSRM/BD_PDO_TE_BPSUPP_SAVE (enhancement spot
/SAPSRM/BD_DP_TE_BP_SAVE) in your namespace.

In case you would just like to display your own data, implement source code in method
READ_TAB_EXTN (refer to figure 3).

Figure 3: Example coding of a possible customer implementation of BAdI method

/SAPSRM/BD_PDO_TE_BPSUPP_SAVE~READ_TAB_EXTN.

If in addition you would like to be able to maintain your own data, you have to implement source code
in the methods UPDATE_TAB_EXTN and DELETE_TAB_EXTN too.

Filter values (BO-Type = BBP000; Table Type = TSCUS)

3.3 Example data

For reference purposes, have a look at implementations /SAPPSSRM/BP_SUPPL_EXT_MV and
/SAPPSSRM/BP_SUPPL_TE_SAVE of above mentioned BAdIs using transaction SE18.
4 Customizing: Metadata maintenance

Maintain the following customizing entries using transaction SM30:

>>>Important: Use BO-settype TSCUS.<<<<<

4.1 Maintenance view /SAPSRM/V_WD_TE

Make the following entry. In addition you may disable the ADD- and DELETE-buttons on the UI (refer
to step 3.2):
- Type of object = BBP000
- Level = HEADER
- Table set type = TSCUS
- Web dynpro component = /SAPSRM/WDC_DODC_CT
- Web dynpro view = V_DODC_CT
- Inclusive/exclusive = inclusive
- Hide add = X
- Hide delete = X
- Display empty = X
- Grid mode = Both
- Row count = -1
- Scroll column = -1
- TSMode = Single
- Visible rows = <your option (e.g. minimum = 1)>
- Width = <your option (e.g. 100%)>

Figure 4: Example metadata - view /SAPSRM/V_WD_TE.

4.2 Maintenance view /SAPSRM/V_WD_TEC
In case you would like to overwrite the table column headers with a descriptive description, make an
entry for every table column header (= table field defined in chapter 2.1):
- Object type = BBP000
- Table set type = TSCUS
- Name of table column = <your field name>
- Configuration scope = HEADER
- Web dynpro component = /SAPSRM/WDC_DODC_CT
- Web dynpro view = V_DODC_CT
- Type of label text = customizable
- Customizable column name = <your description>

Figure 5: Example metadata of a possible customer implementation of view /SAPSRM/V_WD_TEC.

4.3 Maintenance view /SAPSRM/V_MDFSBC:
Make one entry for every table field, you have defined in the data dictionary (refer to step 2.1):
- Set type = TSCUS
- Structure field name = <your field name>
- Object type = BBP000
- Level = HEADER
- Field visible = X
- Field enabled = <your option>
- Field required = <your option>

Figure 6: Example metadata of a possible customer implementation of view /SAPSRM/V_MDFSBC.

4.4 Maintenance view /SAPSRM/V_MDFSBC_DEFAULT:
Make one entry for every table field, you have defined in the data dictionary (refer to step 2.1):
- Set type = TSCUS
- Structure field name = <your field name>
- Object type = BBP000
- Level = HEADER
- Field visible = <your option>
- Field enabled = <your option>
- Field required = <your option>

Figure 7: Example metadata of a possible customer implementation of view

/SAPSRM/V_MDFSBC_DEFAULT.