BP

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

Applies to:CRM 6.0 and above. For more information, visit the Customer Relationship Management homepage

SummaryThrough this document the reader will be able to get a detailed idea about the Business data tool set and its application in CRM Author: G.V.Niranjan Raj

Company: IBM Created on: 24 May 2010

Author BioG.V.Niranjan Raj , currently working as an SAP ABAP / Workflow Consultant having 3 years experience in all stages project like implementation, Support & Maintenance, Enhancement. In addition having techno-functional exposure in SAP ICM module.

SAP COMMUNITY NETWORK 2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1


Table of ContentsScope ......................................................................................................................................................... 3 Target Audience............................................................................................................................................ 3 What is BDT?................................................................................................................................................ 3 Various Parts of BDT .................................................................................................................................... 4 Field groups .............................................................................................................................................. 4 Views ........................................................................................................................................................ 4 Sections .................................................................................................................................................... 5 Screens ..................................................................................................................................................... 5 Customizing Screen Layout/Screen Sequence with Drag&Drop ................................................................. 5 Requirement ................................................................................................................................................. 5 Methods to Achieve other than BDT .............................................................................................................. 5 Creation of BDT Environment........................................................................................................................ 6 BDT Elements : ............................................................................................................................................. 7 Section : .................................................................................................................................................... 7 View : ........................................................................................................................................................ 7 Field Group: .............................................................................................................................................. 7 Important transactions for BDT ...................................................................................................................... 7 Steps To Achieve in BDT .............................................................................................................................. 8 Make sure that in the right overview, you are on the TabKonfiguration, which Shows you the current values. ........ 18 Screen Developed ...................................................................................................................................... 21 Related Content .......................................................................................................................................... 22 Disclaimer and Liability Notice ..................................................................................................................... 23




ScopeThis document introduces Business Data Tool Set (BDT) to the beginners and enthusiasts wishing to explore the 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 and tricks which were discovered while working.

Target AudienceThe document is intended for ABAP and CRM Consultants at all levels trying to learn BDT. Prior Knowledge of 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 transaction data. In addition to dialog maintenance, it also supports maintenance with direct input and/or function modules. The BDT also provides generic services for consistently recurring requirements such as occur in change document lists, field groupings and the deletion program. It takes control over these objects as well as generic parts and calls the applications using predefined interfaces (control tables and events). The applications 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 and customers can also extend these application objects via the BDT interfaces. However, objects belonging to the development partners and customers may not be mapped using the BDT, as the required control has not yet been released. The Business Data Toolset originated in the Central Business Partner project. The following demands on the technical aspect of data entry played an important role in the development of the BDT:

ExtensibilityAlthough 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 in many of the remaining applications. Development partners and customers needed a facility for incorporating their own attributes into maintenance. In master data for accounts receivable and accounts 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.




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 which only 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 entry screens 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 each type of maintenance, the maintenance itself must be divisible into parts wherein only those attributes are visible which are relevant in the current business context. These parts are called roles in Business Partner.

The necessary technology was first developed in a common program with application data for Business Partner. However, it soon became apparent that the second part of this project - i.e., the business partner relationships - was placing the same technical demands on data maintenance. The requirements listed above 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 enhance application objects from the standard system. As a consequence, the Business Partner project group decided to separate the technical part from the application data and then make this technology available to other 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 are grouped in one view. The fields of a view cannot be separated in screen layout since they are located on the same 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. The same applies to customers as extending a view amounts to a modification.




Sections One or more views are grouped together as a section. The BDT automatically puts a frame around each section. 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 the description, you also define a language-dependent title for the section, which is displayed in a dialog in the upper left-hand corner of the frame. Screens The screen represents the largest unit in screen layout. One or more sections are grouped together as a screen. In addition to screens created with BDT, you can integrate screens that were not created with BDT by 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 the main screen sequence as well as the sequence itself in Customizing by drag&drop. These changes, like all other 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..,




Creation of BDT Environment Go to transaction BUPT to view the BDT menu.

Screen Shot Describing BDT elements :




BDT Elements :Section :

View :

Field Group:

Important transactions for BDT 1. 2. 3. 4. 5. 6. BUS2 FIELD GROUP BUS3 VIEWS BUS4 SECTIONS BUS5 SCREENS BUS7 EVENT HANDLINGS BUCO ROLE HANDLINGS AND VCT




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 :




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. In PBO 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 PBO and PAI modules. Data extraction, field checks should be carried out in a separate function modules.




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




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 strict separation 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 is significant 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.




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

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




Create own function module :

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




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




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




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




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.




Make sure that in the right overview, you are on the TabKonfiguration, which Shows you the current 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.




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. On the right side, toggle to 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.




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.




Screen Developed




Related Content http://help.sap.com/saphelp_47x200/helpdata/en/2f/696d360856e808e10000009b38f839/content.ht mFor more information, visit the Customer Relationship Management homepage




Disclaimer and Liability NoticeThis document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported 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 do cument, 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 or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.



BP

Documents

Transcript of BP