SAP BDT_INSTANCE_CREATE Function Module for

Search SAP Function Modules

BDT_INSTANCE_CREATE is a standard bdt instance create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for bdt instance create FM, simply by entering the name BDT_INSTANCE_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: BUSS
Program Name: SAPLBUSS
Main Program: SAPLBUSS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BDT_INSTANCE_CREATE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'BDT_INSTANCE_CREATE'"
  EXPORTING
*  IV_OBJAP =  "BDT: Application Object
*  IV_HANDLE_PRIM =  "
*  IV_HANDLE_SUPER =  "
*  IV_MESSAGE_MODE = '1' "Collective Status for Message Handler
*  IV_SIZE_CAT =  "Size category for BDT instances

 IMPORTING
   EV_HANDLE =  "
   EV_MESSAGE_SEVERITY =  "

TABLES
*  ET_MESSAGE =  "Messages

EXCEPTIONS
   PRIMARY_INSTANCE_NOT_FOUND = 1    SUPER_INSTANCE_NOT_FOUND = 2    NO_OBJAP_EXPECTED = 3    WRONG_ASSIGNMENT = 4    DYNPRO_GENERATOR_LOCKED = 5 

.

IMPORTING Parameters details for BDT_INSTANCE_CREATE

IV_OBJAP - BDT: Application Object

Data type: BU_OBJAP
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_HANDLE_PRIM -

Data type: BDT_INSTANCE_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_HANDLE_SUPER -

Data type: BDT_INSTANCE_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_MESSAGE_MODE - Collective Status for Message Handler

Data type: BU_COLSTAT
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SIZE_CAT - Size category for BDT instances

Data type: BDT_SIZE_CAT
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BDT_INSTANCE_CREATE

EV_HANDLE -

Data type: BDT_INSTANCE_ID
Optional: No
Call by Reference: No ( called with pass by value option)

EV_MESSAGE_SEVERITY -

Data type: SYSUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BDT_INSTANCE_CREATE

ET_MESSAGE - Messages

Data type: BUS0MSG1
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

PRIMARY_INSTANCE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

SUPER_INSTANCE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NO_OBJAP_EXPECTED -

Data type:
Optional: No
Call by Reference: Yes

WRONG_ASSIGNMENT -

Data type:
Optional: No
Call by Reference: Yes

DYNPRO_GENERATOR_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BDT_INSTANCE_CREATE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM BDT_INSTANCE_CREATE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects