Additional tab with custom fields in Business Partner UKM_BP

[former_member223133]

Hi,

We have a requirement to add additional tab/screen with custom fields to Business Partner (BP) transaction UKM_BP.

• BP General Data
• BP Credit Segment Data

We tried to enhance/add additional screens to BP using Easy Enhancement Work Bench (EEWB). But it is adding the custom fields to BP General Data in the table format and not allowing us to add screens to BP Credit Segment Data.

These should be available as separate INDIVIDUAL fields with F4 options, but not in the table format.

Currently we are trying BDT settings to add fields. But changes are not getting reflected in UKM_BP transaction.

Kindly help us on how to add additional tab/screen with custom fields to Business Partner (BP).

Thanks

Gangadhar

[former_member223133]

Hi,

After these BDT Settings, BP Creation (Automatic & Manual) is getting affected.

Kindly help us on how to add additional tab/screen with custom fields to Business Partner (BP) without affecting the process of BP creation.

Help will be highly appreciated.

Thanks

Gangadhar

[hemanth_kumar21]

Hi Gangadhar,

After the BDT settings, did you gone through the Tcode BUS3?

This functionality can be broadly divided into 3 parts.

A.    Creation of the custom fields in the BP transaction screen.

B.     Incorporating a logic flow for the validations etc of those custom fields.

C.     Updating the underlying database tables for the custom fields when the BP transaction is saved.

[hemanth_kumar21]

Adding custom fields to the BP Transaction and maintaining those custom fields.

This functionality can be broadly divided into 3 parts.

A.    Creation of the custom fields in the BP transaction screen.

B.     Incorporating a logic flow for the validations etc of those custom fields.

C.     Updating the underlying database tables for the custom fields when the BP transaction is saved.

A.    Creation of the custom fields in the BP transaction screen.

To create the custom fields in the BP transaction, the BDT tool can be used.  Using this tool, a customized screen section can be created in the BP transaction screens.

The following steps describe in detail the creation of 3 custom fields in the BP transaction screen, for the Role -> Prospect, in the Sales Area Data tab.

The custom fields are namely:

·         Ranking key

·         Rank

·         Overwrite

The creation of Field group, View, Section, Screen and Screen sequence using the transaction BUPT is explained below.

1.      Use transaction BUPT to reach the initial screen for BDT.

2.      Use path SAP MENU -> Business Partner -> Control Data -> Screen Layout .

Under the Screen Layout, there are 4 options. We need to work with these.

3.      Go to Field Groups.

i) Create a Fld Group  (eg, 600: Rank Field Group)  .

ii) In the field groups assign the set of fields that you need in the BP screen.

In this case the fields are RANKING_KEY, RANK and OVERWRITE of the custom table YBUT_VKBUR.

Save the data and go back to the initial transaction BUPT.

4) Now, go to VIEWS (transaction – BUS3).

i)  Create a new View (ZRANK) .

ii) Now select the View (ZRANK) and click on the display button (CTRL + SHFT + F2).

You will be taken to the screen below.

Maintain as follows:

• Application = BUP - Central Business Partner: Data
• Differentiation            = 3 - Sales Area Data      
• Data set = ZDSET (***This needs to be maintained by Config)

Specify the program name (/GLB/CGTDDU_RANKING)  and the screen no as 9000.

[Note:  A custom program (/GLB/CGTDDU_RANKING) with custom screen (9000) has already been created using the SCREEN PAINTER transaction (SE51) or the OBJECT NAVIGATOR (SE80).

Add the fields etc (that you want to use in the BP transaction) to this custom screen Layout.

In the Attribute, the screen Type has been selected as ‘SUBSCREEN’.]

iii) Next assign the Field Group (600) already created in (1) to the View ZRANK.

Save the data and go back to the BUPT transaction.

5) Go to STAGES (BUS4)

i) Create a SECTION (ZSECT) and maintain a Title (Ranking).

ii)Now assign the View (ZRANK) created in Step (4-i) to this Section (ZSECT).

Save the data and go back to BUPT.

6) Now go to SCREENS (BUS5).

i) An entry needs to be created/maintained here.

In this case, it is Screen (ZRANK) with Screen Title Ranking.

ii) Assign the Sections:

CRM101:         CRM sales area   (SAP Standard)

EMPTY:           Empty (SAP Standard)

ZSECT:            Rank Section

Save the data before going back.

7) In the transaction BUPT, follow the path

SAP Menu -> Customizing -> Basic settings -> Field Grouping -> BP Roles.

Some Config is required here for the Role Prospect.

·         The data set ‘ZDSET’ that has already been created needs to be attached to the Prospect.

·         This data set has the field group ‘600’ attached to it.

😎 The BP transaction for the BP Role ‘Prospect’ in the ‘SALES AREA DATA’ tab now has the 3 new fields

• Ranking Key

• Rank
• Overwrite

in the tab ‘Ranking’.

B.     Incorporating a logic flow for the validations etc of those custom fields.

To incorporate the logic for the validations of the custom fields, the PAI and the PBO of the custom program that is attached to the View can be used.

In the e.g., given above the PAI and PBO modules of the screen 9000 of the custom program /GLB/CGTDDU_RANKING was used.

C.    Updating the underlying database tables for the custom fields when the BP transaction is saved.

We will need to create FMs and configure the FMs to trigger under specific SAP events.

The list of the events can be found from the transaction BUPT using the path:

SAP Menu -> Business Partner -> Control Data -> Events -> Business Data Toolset (BUS7)

In the e.g. described above, 2 FMs were created under the Function Group ‘/GLB/CGTDD_RANKING’.

These FMs were:

1) FM  ‘/GLB/CGT_GET_STATUS_XCHNG’:

The custom FM ‘/GLB/CGT_GET_STATUS_XCHNG’ was attached to the event the event ‘XCHNG’ (which is triggered to check whether Data Has Been Changed).

     The application name used was ‘BUP’.

2) FM  ‘/GLB/CGT_SAVE_RANK_DSAVE’:

The custom FM ‘/GLB/CGT_SAVE_RANK_DSAVE’ was attached to the event 

‘DSAVE’ (which is triggered to Save Data in Database (from Local Memory)).

            The application name used was ‘BUP’.

(The custom program /GLB/CGTDDU_RANKING used another FM that were created under the same function group ‘/GLB/CGTDD_RANKING’. This was done to link the data flow in the custom program to the FM that were attached to the Standard Events).

[former_member223133]

Hi Hemanth,

Thanks for the reply.

Yes, we have defined views and the below mentioned BDT Settings have been done.

1.       Create the function group and the Sub screen for application

2.       Create New Application for screen

3.       Create New Dataset for the application

4.       Create field groups as required

5.       Create a view & Assign the field groups to the views

6.       Create section & Assign View to the section

7.       Create Screen & Assign the section to the screen

8.       Create the screen sequence & Assign the Screen

9.       Create a screen sequence category & assign the screen sequence to it

10.   Add screen with the standard screen sequence so that it would appear with the standard TABS (Added screen to the standard BUP001 Screen Sequence)

11.   Create BP Views & Add datasets (standard & custom) to the selected BP VIEW

12.   Add the calling application to selected BP VIEW

Since we have enabled the automatic creation of BP's whenever customer master is created, these BDT settings are affecting the BP Master Creation (both automatic & maual).

Please let us know if we missed any other steps.

Thanks

Gangadhar

[former_member223133]

Hi Members,

Any suggestions on the solution?

Thanks

Gangadhar

[former_member223133]

Hi Members,

I have solved the problem myself with below steps.

Define the dataset to standard BP role, If particular dataset should be displayed in particular role and also the custom calling application needs to be added to standard BP View (UKM000 - BP Credit Management).

Thanks

Gangadhar

[hemanth_kumar21]

Thanks Gangadhar for sharing the Solution.