Skip to Content
author's profile photo Former Member
Former Member

BDT??Business data toolset for Dialog Programs

Hi All,

what exactly is BDT?

what I know is that BDT is a enhancement toolset provided by SAP like user exits, BAPI and all. In case you want to make some changes to standard SAP program.

BDT is GUI based, specifically focusing Grants Management Module.

I am not sure whether we can use this toolset for all transactions and make changes accordingly…..

CAN SOMEONE PLEASE GIVE ME A CLEAR PICTURE ON WHAT IS BDT?IS IT USED FOR ALL ENHANCEMENTS TO STANDARD PROGRAMS.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 01, 2005 at 11:14 AM

    Hi,

    The Business data toolset (BDT) is a central control tool for maintaining SAP programs. It supports

    maintenance via the use of dialog techniques, direct input and/or function modules.

    The BDT is basically the tool SAP use when they want to add new fields, change field names, change/add

    field groups etc for specific customers, but they are now starting to allow there customers access to these

    maintenance transactions (i think mainly ramp-up customers at the moment).

    please gothrough this link for Example

    http://www.sapdevelopment.co.uk/enhance/bdt/bdt_gmcustom.htm

    _EVENT_DSAVE

    (Customer: Function module name also has the prefix Y_ or Z_)

    Example: BUP_BUPA_EVENT_DSAVE

    Action required:

    ¡ Write new data from the global memory to database. The BDT will state, using a parameter of the function module BUS_PARAMETERS_ISSTA_GET, whether this is to be done with or without an update task.

    ¡ Write change documents using the old and the new status from the global memory.

    ¡ Issue success message (only application which owns application object).

    · DLVE1 (initializing the current memory)

    The current memory is initialized. When returning to the initial screen there is no ⚠️ LEAVE TO TRANSACTION with the result that the current memory must be initialized at this point so that the next data maintenance will start correctly. The application which owns the application object will remove the lock.

    Runtime: When leaving data maintenance.

    Application area: All applications.

    Naming convention: _EVENT_DLVE2.

    (Customer: Function module name has the prefix Y_ or Z_).

    Example: BUP_BUPA_EVENT_DLVE2

    Action required:

    ¡ Initialize global memory.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 01, 2005 at 10:34 AM

    Hi,

    Pl. find some documentation.

    Adding Customer Attributes to Core Object Entity

    Prerequisites

    You have decided to enhance the core entity using the criteria mentioned in Selecting and Implementing Customer Enhancement Types .

    Procedure

    1 If necessary, familiarize yourself with the contents of the BDT developers' handbook. Pay particular attention to the following points:

    • Function overview

    • Basic settings

    • Applications

    • Function overview

    • Dialog

    • Program logic

    • Implementation schedule

    • New table fields and new tables

    • New table field through participating application

    • Implementation schedule

    • New object part

    • Implementation schedule

    • Enhancing screen layout and sequence

    2 Create a function group for processing the enhancement fields and define the screen fields in the global memory.

    3 Create the APPEND structure for the table CACS_CTRTBU in the DDIC. A prerequisite here is that all other necessary data dictionary objects have already been created (data elements in the customer name range, value tables, and so on).

    4 Write the coding for the PAI and PBO routines necessary for each view and define the screens.

    Entries in the screen fields are checked in the PAI routines, values are converted to the internal format, depending on their type, and transferred to the internal tables. PBO routines transfer any converted values from the internal table to the screen fields.

    • You must always work with the current version.

    • If you want to carry out checks on standard fields (in addition to the standard checks or in combination with enhancement fields), you can do this using functions that must first be defined in the BDT under Further checks. The PAI routines for standard views cannot be replaced with customer routines.

    Further information:

    • Sample coding for standard PAI and PBO routines.

    5 Using the area menu CACSBDT, create the BDT entries required for screen layout (field groups, views, sections, screens) for the new fields.

    6 In the area menu CACSBDT, make the necessary assignments using AssgnScrnField  DBField.

    7 Create the necessary function modules at the following events for processing the enhancement fields for this enhancement type.

    8 In the area menu CACSBDT, define the function modules for the program logic using the path Events  Assign Event  Function Module.

    Other information:

    • You can find a general description of events in the BDT developers' handbook.

    • More detailed information on events in the commission contract (customer attributes)

    • Sample coding for events ISSTA, ISDST, XCHNG, DSAVB, DLVE1 and FCODE

    9 Create a routine that corresponds to the form "get_val_dyn" in the sample coding (you can give it any name). This calls function CACS_CSC_GETACTVERS, which determines the version to be displayed. The current screen values are determined from the internal table, which contains the current data for the commission contract (in conjunction with the version currently valid), and then they are transferred to the BDT work structure with the screen output fields (fields of the same name - the rest must be transferred explicitly, for example in the ISDST module).

    You will find program examples here that you can use to program event modules for this change type.

    Result

    You have carried out all the necessary activities, and you can now begin testing the commission contract and its enhancements.

    Pl. reward the points.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 01, 2005 at 10:02 AM

    Hi Welcome to SDN.

    you may want to check out the following artcile.

    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6173fb9e-0701-0010-6083-a0001827a6ff

    Regards

    Raja

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 01, 2005 at 10:04 AM
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.