Documente Academic
Documente Profesional
Documente Cultură
1 of 6
http://www.itpsap.com/blog/2014/01/19/bte-bdt-enhancements-part-2/
Were back with Tims next installment of this blog to teach us about two little known SAP Enhancement
techniques, BTEs and BDTs Here is a little bit about Tim.
Tim Moore is the president of 4 Ever Moore Enterprises, L.L.C., located outside of Charlotte, North
Carolina. Tim has over 15 years of experience with SAP including ERP, SRM, CRM, SCM, BI and XI. He
has technical middleware experience as well as functional knowledge in many different industry solutions,
such as FI, CO, MM, PP, SD, PS, HCM. He has Solutions Architect experience as well as expertise in SAP
Business Workflow, ABAP and Form development. He made his way into programming as an MM
functional SME who grew tired of laying out technical requirements for developers, so he decided to teach
himself to code ABAP. Since then, he has taken courses in ABAP, expanded to Web programming languages,
and learned XML to help with integration points with SAP. Prior to programming, Tim was a Business
School graduate and served as a manufacturing manager for a company who implemented SAP. He continues
to build his professional skills by expanding his business and technical knowledge in new areas. You can
reach him at sapcodemonkey@gmail.com
The acronym BTE stands for Business Transaction Events. This type of enhancement is typically leveraged
in FI and SD transaction objects for process modification. To get a better understanding of BTEs and how
they work, take a look at last months blog What are BTE and BDT Enhancements Part 1.
10/27/2016 10:22 AM
2 of 6
http://www.itpsap.com/blog/2014/01/19/bte-bdt-enhancements-part-2/
The acronym BTE stands for Business Transaction Events. This type of enhancement is typically leveraged
in FI and SD transaction objects for process modification. To get a better understanding of BTEs and how
they work, take a look at last months blog What are BTE and BDT Enhancements Part 1.
This month we will look at BDTs. So lets get started!
The acronym BDT stands for Business Data Tool-set. This type of enhancement can offer exits in the Master
Data maintenance for certain objects.
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 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-sized 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 were placing
the same technical demands on data maintenance.
The requirements listed above were also applicable to other business objects.
10/27/2016 10:22 AM
3 of 6
http://www.itpsap.com/blog/2014/01/19/bte-bdt-enhancements-part-2/
10/27/2016 10:22 AM
4 of 6
http://www.itpsap.com/blog/2014/01/19/bte-bdt-enhancements-part-2/
transaction in SAP. New custom fields can be created; existing fields can be moved or deleted. For each
BDT enabled transaction a separate area menu will be available.
OK, so I can hear you asking How can I find out if my transaction has above BDT
modification technique available?
Here are a set of steps you can use to try and determine if your object is BDT capable.
1) Once you have identified a candidate for enhancement via BDT (i.e. no SAP-provided dialog/screen
exits), how do you find out what the application object is so that you can determine if it is an object
registered for the BDT?
2) All BDT-enabled applications call function module BDT_TBZ0A_GET to find out specifically what, if
anything, has been enhanced.
3) Put a break-point in the function module.
4) Execute the transaction that you are hoping to enhance.
5) When your break-point is hit, look at the value assigned to variable IV_OBJAP. This is your application
object.
6) If the break-point is not hit, chances are that your application doesnt use the BDT.
Want to find ALL the Tcodes in SAP that use BDTs? OK, to find SAP Transaction that use the BDT
Framework, execute SE93 and search on transactions with the short description of *BDT*
10/27/2016 10:22 AM
5 of 6
http://www.itpsap.com/blog/2014/01/19/bte-bdt-enhancements-part-2/
Framework, execute SE93 and search on transactions with the short description of *BDT*
10/27/2016 10:22 AM
6 of 6
http://www.itpsap.com/blog/2014/01/19/bte-bdt-enhancements-part-2/
existing SAP documentation for a step by step Build and use case.
10/27/2016 10:22 AM