bdt_bp

8/3/2019 BDT_BP

1/23

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG

Enhancing Business PartnerTransaction with New fields andScreen using Business Data ToolSet

Applies to:

CRM 6.0 and above. For more information, visit theCustomer Relationship Management homepage

Summary

Through this document the reader will be able to get a detailed idea about the Business data tool set and itsapplication in CRM

Author: G.V.Niranjan Raj

Company: IBM

Created on: 24 May 2010

Author Bio

G.V.Niranjan Raj , currently working as an SAP ABAP / Workflow Consultant having 3years experience in all stages project like implementation, Support & Maintenance,Enhancement. In addition having techno-functional exposure in SAP ICM module.
https://www.sdn.sap.com/irj/sdn/bpx-crmhttps://www.sdn.sap.com/irj/sdn/bpx-crmhttps://www.sdn.sap.com/irj/sdn/bpx-crmhttps://www.sdn.sap.com/irj/sdn/bpx-crm

8/3/2019 BDT_BP

2/23

Enhancing Business Partner Transaction with New fields and Screen using Business Data Tool Set


2010 SAP AG

Table of Contents

Scope ......................................................................................................................................................... 3Target Audience............................................................................................................................................ 3What is BDT? ................................................................................................................................................ 3Various Parts of BDT .................................................................................................................................... 4

Field groups .............................................................................................................................................. 4

Views ........................................................................................................................................................ 4Sections .................................................................................................................................................... 5Screens ..................................................................................................................................................... 5Customizing Screen Layout/Screen Sequence with Drag&Drop ................................................................. 5

Requirement ................................................................................................................................................. 5Methods to Achieve other than BDT .............................................................................................................. 5Creation of BDT Environment ........................................................................................................................ 6BDT Elements : ............................................................................................................................................. 7

Section : .................................................................................................................................................... 7View : ........................................................................................................................................................ 7Field Group: .............................................................................................................................................. 7

Important transactions for BDT ...................................................................................................................... 7Steps To Achieve in BDT .............................................................................................................................. 8Make sure that in the right overview, you are on the TabKonfiguration, which Shows you the current values. ........ 18Screen Developed ...................................................................................................................................... 21Related Content .......................................................................................................................................... 22Disclaimer and Liability Notice ..................................................................................................................... 23

8/3/2019 BDT_BP

3/23



2010 SAP AG

Scope

This document introduces Business Data Tool Set (BDT) to the beginners and enthusiasts wishing to explorethe features of BDT. It also tries to give an in-depth knowledge to developers already working on it.Examples outlining different transformations are also provided.

A Step-by-step introduction Business Data Tool Set is the main feature of this guide. It incorporates tips andtricks which were discovered while working.

Target Audience

The document is intended for ABAP and CRM Consultants at all levels trying to learn BDT. Prior Knowledgeof ABAP development and CRM development environment is recommended.

What is BDT?

The BDT (Business Data Toolset) is a central control tool for maintaining master data and simple transactiondata. In addition to dialog maintenance, it also supports maintenance with direct input and/or functionmodules.

The BDT also provides generic services for consistently recurring requirements such as occur in changedocument lists, field groupings and the deletion program. It takes control over these objects as well asgeneric parts and calls the applications using predefined interfaces (control tables and events). Theapplications themselves introduce application-specific enhancements, such as writing and reading

application tables.

Note: The BDT is used at SAP for maintaining several application objects. Development partners andcustomers can also extend these application objects via the BDT interfaces. However, objects belonging tothe development partners and customers may not be mapped using the BDT, as the required control has notyet been released.

The Business Data Toolset originated in the Central Business Partner project. The following demands on thetechnical aspect of data entry played an important role in the development of the BDT:

Extensibility

Although the Business Partner project group had realized the central attributes of a business partner,(such as name components, addresses and bank details) there were other specific attributes inmany of the remaining applications. Development partners and customers needed a facility forincorporating their own attributes into maintenance. In master data for accounts receivable andaccounts payable, you had to make modifications to do this.Because it is impossible to collect and implement all these different attributes in one project group,maintenance for downstream enhancements had to be extensible without the need for modifications.

8/3/2019 BDT_BP

4/23



2010 SAP AG

Configurability

Because mid-size customers in particular tend to suppress most of the standard SAP data fields,dialog maintenance becomes tedious when you still have to go through screen after screen on whichonly one or two fields are relevant. Switching screens often slows down data entry considerably.As a result, it was decided to make screens configurable in order for customers to both tailor entryscreens to their individual needs and keep the number of screens to a minimum.

Divisibility

If you were to count up all the attributes in the SAP system that are relevant for a business partner,you would have several hundred fields. Since it is impossible to include all these attributes in eachtype of maintenance, the maintenance itself must be divisible into parts wherein only those attributesare visible which are relevant in the current business context. These parts are called roles inBusiness Partner.

The necessary technology was first developed in a common program with application data for BusinessPartner. However, it soon became apparent that the second part of this project - i.e., the business partnerrelationships - was placing the same technical demands on data maintenance. The requirements listedabove were also applicable to other business objects. As SAP restructured with a new industry orientation,extensibility assumed a greater importance for development. Many of the IBUs wanted to extend or enhanceapplication objects from the standard system. As a consequence, the Business Partner project groupdecided to separate the technical part from the application data and then make this technology available toother application objects. This technical part, which was called BP control or master data control for a long

time, is now known as the Business Data Toolset, or BDT.

Various Parts of BDT

Screen layout is defined in control tables. Applications from downstream development stages can

extend and reconfigure existing screens. The BDT supports the following entities in screen layout

Field group

View

Section

Screen

Field groups

Fields whose readiness for input was defined collectively are collected in a single field group. You

create settings for each field group with in the Field Grouping.

A field group may only contain fields from one application. Customers should neither change nor

extend the definition of standard SAP field groups, as this would amount to a program modification.

As an alternative, customers can define their own field groups to which they also assign their own

views.

Views

One or more field groups constitute a view. All attributes that are displayed and checked together aregrouped in one view. The fields of a view cannot be separated in screen layout since they are located on thesame sub screen.

A view may only contain fields from one application. A downstream application may not extend a view;instead, it should create its own views for its attributes and assign its own sub screens to these views. Thesame applies to customers as extending a view amounts to a modification.

8/3/2019 BDT_BP

5/23



2010 SAP AG

Sections

One or more views are grouped together as a section. The BDT automatically puts a frame around eachsection. The only exception to this rule is the first section of a screen in which the header data appears.According to SAP ergonomic guidelines, a frame should not be put around this data. In addition to thedescription, you also define a language-dependent title for the section, which is displayed in a dialog in theupper left-hand corner of the frame.

Screens

The screen represents the largest unit in screen layout. One or more sections are grouped together as ascreen. In addition to screens created with BDT, you can integrate screens that were not created with BDTby using the External screens selection.

Customizing Screen Layout/Screen Sequence with Drag&Drop

Description: Using the Visual Configuration Tool (VCT), customers can change standard SAP screens in themain screen sequence as well as the sequence itself in Customizing by drag&drop. These changes, like allother Customizing activities, connected to transports. Changes made by customers are fully maintained -that is, they are not overwritten by SAP in an upgrade.

Requirement

1. New fields to be added in BUT000 table through a standard customer include.2. These new fields need to be added into BP transaction for the user interaction.

3. These fields should be relevant for business partners (roles ZVP and ZVKO).

Methods to Achieve other than BDT

Easy Enhancement Work Bench Screen Exit etc..,

8/3/2019 BDT_BP

6/23



2010 SAP AG

Creation of BDT Environment

Go to transaction BUPT to view the BDT menu.

Screen Shot Describing BDT elements :

8/3/2019 BDT_BP

7/23



2010 SAP AG

BDT Elements :

Section :

View :

Field Group:

Important transactions for BDT

1. BUS2FIELD GROUP2. BUS3VIEWS3. BUS4SECTIONS4. BUS5SCREENS5. BUS7EVENT HANDLINGS

6. BUCOROLE HANDLINGS AND VCT

8/3/2019 BDT_BP

8/23



2010 SAP AG

Steps To Achieve in BDT

Step 1 : In BUS2 transaction assign the new fields as shown in the below figure.

Step 2 : In BUS3 transaction group the fields to a view as shown below.

Generate the sub screen as shown below :

8/3/2019 BDT_BP

9/23



2010 SAP AG

Sub screen Development :

A function Group is to be developed .

In the FG sub screens need to be developed . In PBO and PAI of the screen BDT related Function modules must be called.

Save the Screen. Return back to the flow logic section. Create one PBO module and one PAI module. InPBO module, call function module BUS_PBO and in PAI module call function module BUS_PAI.

Other than calls to Function Modules BUS_PBO and BUS_PAI, no other logic should be placed in the PBOand PAI modules. Data extraction, field checks should be carried out in a separate function modules.

8/3/2019 BDT_BP

10/23



2010 SAP AG

Now get back to the view creation screen and enter the screen number we have created now.

8/3/2019 BDT_BP

11/23



2010 SAP AG

Next section of information to be entered is Function Modules. There are 3 function modules,

one for Before screen call up, second one for Before output and third one for After Entry. Any

PBO and PAI logic that usually placed in the Flow logic section of Screen is to be placed in

these function modules instead. BDT wants the interface and the Program Logic to be different

is to enable DIRECT INPUT. One of the goals for development with the BDT is a strictseparation between interface and program logic. This ensures that all checks can be carried out

even if you are using direct input and an external interface.

Before Output Function module can be used to put the PBO logic and After Entry function module

can be used to put in the PAI checks. Before screen callup is useful mostly when the view

contains table controls or step loops and not needed for this example.

In BUS4 transaction one can create section as shown below :

Once section is saved, hit the Section->Views button in the left frame. Data entry screen opens up in

the right frame. Enter the view ZG1901 in there along with Item number as 999991. This number issignificant if there is more than one view in the section. If more than one view exists in the section,

then the views are displayed as per the item number.

8/3/2019 BDT_BP

12/23



2010 SAP AG

Next step is to create a screen. Create screen named ZG1901(this name can be any thing) using thetransaction BUS5. Enter Additional data as description and Title. Value entered in title here will be used asthe tab heading in the final transaction display.

Events for the corresponding fields can be triggered through BUS7 transaction :

8/3/2019 BDT_BP

13/23



2010 SAP AG

Create own function module :

Add the function module to the corresponding triggering event in BUS7 transaction. When the event triggerthe corresponding function module will be triggered:

8/3/2019 BDT_BP

14/23



2010 SAP AG

Assign the screens to the particular role in BUCO transaction as shown in the below screen shot EntryScreen of Transaction BUCO.Choose the Screen Sequence Area to modifiy, most likely Allgemeine Daten(General Data).

8/3/2019 BDT_BP

15/23



2010 SAP AG

BUCO Entry Screen, continued. Choose the role, for which you want to modify the screen sequence, forInstance Vertragskonto(VO)

8/3/2019 BDT_BP

16/23



2010 SAP AG

BUCO Entry Screen, continued.Choose the role, for which you want to modify the screen sequence, forInstance Vertragskonto(VO).

8/3/2019 BDT_BP

17/23



2010 SAP AG

A new window should appear, add the overview to the right screen part, via the button marked

above.

This Button toggles between the screen sequence Bildfolge(allowing you to add /drop a screen)

and the maintenance of screens Bildaufbau.For now stay on Bildaufbau.

The current screens are given as buttons at the buttom of the screen, Choose the one to work on,

for example Stammdaten.

8/3/2019 BDT_BP

18/23



2010 SAP AG

Make sure that in the right overview, you are on the TabKonfiguration, which Shows you thecurrent values.

You can create a new section on the screen by dragging from the Button Neuer Abschnitt on the

right to an area on the layout.

Double clicking the new section on the layout screen allows you to Change the title.

8/3/2019 BDT_BP

19/23



2010 SAP AG

You can create a new section on the screen by dragging from the Button Neuer Abschnitt on the right to anarea on the layout.

Double clicking the new section on the layout screen allows you to Change the title. On the right side, toggleto the tab Sichten (Views)

You should see all standard views and The ones you have defined in the BDT Before.

You can add the views / fields to the new section by dragging them on to

The layout screen.

8/3/2019 BDT_BP

20/23



2010 SAP AG

The cut, copy, paste, delete buttons work on the field section on the Layout screen you have marked

(single click).

These buttons confirm or discard your changes.

Finally run the BUPT transaction to get assigned.

8/3/2019 BDT_BP

21/23



2010 SAP AG

Screen Developed

8/3/2019 BDT_BP

22/23



2010 SAP AG

Related Content

http://help.sap.com/saphelp_47x200/helpdata/en/2f/696d360856e808e10000009b38f839/content.ht

m

For more information, visit theCustomer Relationship Management homepage
http://help.sap.com/saphelp_47x200/helpdata/en/2f/696d360856e808e10000009b38f839/content.htmhttp://help.sap.com/saphelp_47x200/helpdata/en/2f/696d360856e808e10000009b38f839/content.htmhttp://help.sap.com/saphelp_47x200/helpdata/en/2f/696d360856e808e10000009b38f839/content.htmhttps://www.sdn.sap.com/irj/sdn/bpx-crmhttps://www.sdn.sap.com/irj/sdn/bpx-crmhttps://www.sdn.sap.com/irj/sdn/bpx-crmhttps://www.sdn.sap.com/irj/sdn/bpx-crmhttp://help.sap.com/saphelp_47x200/helpdata/en/2f/696d360856e808e10000009b38f839/content.htmhttp://help.sap.com/saphelp_47x200/helpdata/en/2f/696d360856e808e10000009b38f839/content.htm

8/3/2019 BDT_BP

23/23


Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.

bdt_bp

Documents