SAP BDL_CREATE_ADDON_DIRECTORY Function Module for (Re)create the addon directory for an addon type in a SDCC session









BDL_CREATE_ADDON_DIRECTORY is a standard bdl create addon directory SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for (Re)create the addon directory for an addon type in a SDCC session processing and below is the pattern details for this FM, 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 bdl create addon directory FM, simply by entering the name BDL_CREATE_ADDON_DIRECTORY into the relevant SAP transaction such as SE37 or SE38.

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



Function BDL_CREATE_ADDON_DIRECTORY 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 'BDL_CREATE_ADDON_DIRECTORY'"(Re)create the addon directory for an addon type in a SDCC session
EXPORTING
SESSNO = "session number
EXTENSION = "session number extension (client)
CONTRACT = "addon type (e.g. ST14, SQLCACHE, ...)
* DESCRIPTION = ' ' "sub type (usually space)

EXCEPTIONS
NO_DATA_FOUND = 1
.



IMPORTING Parameters details for BDL_CREATE_ADDON_DIRECTORY

SESSNO - session number

Data type: BDLDTOC-SESSIONNR
Optional: No
Call by Reference: Yes

EXTENSION - session number extension (client)

Data type: BDLDTOC-MANDANT
Optional: No
Call by Reference: Yes

CONTRACT - addon type (e.g. ST14, SQLCACHE, ...)

Data type: BDLDTOC-CONTRACT
Optional: No
Call by Reference: Yes

DESCRIPTION - sub type (usually space)

Data type: BDLDTOC-DESCRIPTIO
Default: ' '
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_DATA_FOUND - no data found for given addon type

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BDL_CREATE_ADDON_DIRECTORY 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.

DATA:
lv_sessno  TYPE BDLDTOC-SESSIONNR, "   
lv_no_data_found  TYPE BDLDTOC, "   
lv_extension  TYPE BDLDTOC-MANDANT, "   
lv_contract  TYPE BDLDTOC-CONTRACT, "   
lv_description  TYPE BDLDTOC-DESCRIPTIO. "   ' '

  CALL FUNCTION 'BDL_CREATE_ADDON_DIRECTORY'  "(Re)create the addon directory for an addon type in a SDCC session
    EXPORTING
         SESSNO = lv_sessno
         EXTENSION = lv_extension
         CONTRACT = lv_contract
         DESCRIPTION = lv_description
    EXCEPTIONS
        NO_DATA_FOUND = 1
. " BDL_CREATE_ADDON_DIRECTORY




ABAP code using 7.40 inline data declarations to call FM BDL_CREATE_ADDON_DIRECTORY

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.

"SELECT single SESSIONNR FROM BDLDTOC INTO @DATA(ld_sessno).
 
 
"SELECT single MANDANT FROM BDLDTOC INTO @DATA(ld_extension).
 
"SELECT single CONTRACT FROM BDLDTOC INTO @DATA(ld_contract).
 
"SELECT single DESCRIPTIO FROM BDLDTOC INTO @DATA(ld_description).
DATA(ld_description) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!