SAP Function Modules

BDL_EXPORT_SESSDATA_TO_FILE SAP Function module - Export collected session data via R3trans into a transportable data file







BDL_EXPORT_SESSDATA_TO_FILE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BDL_EXPORT_SESSDATA_TO_FILE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BDL3
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM BDL_EXPORT_SESSDATA_TO_FILE - BDL EXPORT SESSDATA TO FILE





CALL FUNCTION 'BDL_EXPORT_SESSDATA_TO_FILE' "Export collected session data via R3trans into a transportable data file
  EXPORTING
    sessionnr =                 " bdldtoc-sessionnr  Source session number
    mandant =                   " bdldtoc-mandant  Source session extension
*   destsessnr = ' '            " bdldtoc-sessionnr  Destination session number
*   destmand = ' '              " bdldtoc-mandant  Destination session extension
  IMPORTING
    usedfilepath =              "               Generated data file
  EXCEPTIONS
    DEST_SESSION_NONEMPTY = 1   "               Destination session already contains data
    FILE_ERROR = 2              "               Error during file open
    PERMISSION_ERROR = 3        "               Insufficient permissions for file operation
    .  "  BDL_EXPORT_SESSDATA_TO_FILE

ABAP code example for Function Module BDL_EXPORT_SESSDATA_TO_FILE





The ABAP code below is a full code listing to execute function module BDL_EXPORT_SESSDATA_TO_FILE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_usedfilepath  TYPE STRING .


SELECT single SESSIONNR
FROM BDLDTOC
INTO @DATA(ld_sessionnr).


SELECT single MANDANT
FROM BDLDTOC
INTO @DATA(ld_mandant).


SELECT single SESSIONNR
FROM BDLDTOC
INTO @DATA(ld_destsessnr).


SELECT single MANDANT
FROM BDLDTOC
INTO @DATA(ld_destmand).
. CALL FUNCTION 'BDL_EXPORT_SESSDATA_TO_FILE' EXPORTING sessionnr = ld_sessionnr mandant = ld_mandant * destsessnr = ld_destsessnr * destmand = ld_destmand IMPORTING usedfilepath = ld_usedfilepath EXCEPTIONS DEST_SESSION_NONEMPTY = 1 FILE_ERROR = 2 PERMISSION_ERROR = 3 . " BDL_EXPORT_SESSDATA_TO_FILE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_usedfilepath  TYPE STRING ,
ld_sessionnr  TYPE BDLDTOC-SESSIONNR ,
ld_mandant  TYPE BDLDTOC-MANDANT ,
ld_destsessnr  TYPE BDLDTOC-SESSIONNR ,
ld_destmand  TYPE BDLDTOC-MANDANT .


SELECT single SESSIONNR
FROM BDLDTOC
INTO ld_sessionnr.


SELECT single MANDANT
FROM BDLDTOC
INTO ld_mandant.


SELECT single SESSIONNR
FROM BDLDTOC
INTO ld_destsessnr.


SELECT single MANDANT
FROM BDLDTOC
INTO ld_destmand.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BDL_EXPORT_SESSDATA_TO_FILE or its description.