SAP BDC_RECORD_TRANSACTION Function Module for









BDC_RECORD_TRANSACTION is a standard bdc record transaction 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 bdc record transaction FM, simply by entering the name BDC_RECORD_TRANSACTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: SBDR
Program Name: SAPLSBDR
Main Program: SAPLSBDR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BDC_RECORD_TRANSACTION 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 'BDC_RECORD_TRANSACTION'"
  EXPORTING
   TCODE =  "Transaction Code
*  AUTHORITY_CHECK = 'X' "
*  OPTIONS = ' ' "
*  MODE = 'A' "
*  UPDATE = 'A' "

TABLES
   DYNPROTAB =  "
*  MESSTAB =  "

EXCEPTIONS
   SYSTEM_FAILURE = 1    INVALID_TRANSACTION = 2    INVALID_MODE = 3    INVALID_UPDATE = 4
.



IMPORTING Parameters details for BDC_RECORD_TRANSACTION

TCODE - Transaction Code

Data type: SHDFV-TCODE
Optional: No
Call by Reference: No ( called with pass by value option)

AUTHORITY_CHECK -

Data type: APQI-PUTACTIVE
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

OPTIONS -

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

MODE -

Data type: APQI-PUTACTIVE
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

UPDATE -

Data type: APQI-PUTACTIVE
Default: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BDC_RECORD_TRANSACTION

DYNPROTAB -

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

MESSTAB -

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

EXCEPTIONS details

SYSTEM_FAILURE - System Error

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

INVALID_TRANSACTION -

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

INVALID_MODE -

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

INVALID_UPDATE -

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

Copy and paste ABAP code example for BDC_RECORD_TRANSACTION 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_tcode  TYPE SHDFV-TCODE, "   
lt_dynprotab  TYPE STANDARD TABLE OF BDCDATA, "   
lv_system_failure  TYPE BDCDATA, "   
lt_messtab  TYPE STANDARD TABLE OF BDCMSGCOLL, "   
lv_authority_check  TYPE APQI-PUTACTIVE, "   'X'
lv_invalid_transaction  TYPE APQI, "   
lv_options  TYPE CTU_PARAMS, "   SPACE
lv_invalid_mode  TYPE CTU_PARAMS, "   
lv_mode  TYPE APQI-PUTACTIVE, "   'A'
lv_invalid_update  TYPE APQI, "   
lv_update  TYPE APQI-PUTACTIVE. "   'A'

  CALL FUNCTION 'BDC_RECORD_TRANSACTION'  "
    EXPORTING
         TCODE = lv_tcode
         AUTHORITY_CHECK = lv_authority_check
         OPTIONS = lv_options
         MODE = lv_mode
         UPDATE = lv_update
    TABLES
         DYNPROTAB = lt_dynprotab
         MESSTAB = lt_messtab
    EXCEPTIONS
        SYSTEM_FAILURE = 1
        INVALID_TRANSACTION = 2
        INVALID_MODE = 3
        INVALID_UPDATE = 4
. " BDC_RECORD_TRANSACTION




ABAP code using 7.40 inline data declarations to call FM BDC_RECORD_TRANSACTION

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 TCODE FROM SHDFV INTO @DATA(ld_tcode).
 
 
 
 
"SELECT single PUTACTIVE FROM APQI INTO @DATA(ld_authority_check).
DATA(ld_authority_check) = 'X'.
 
 
DATA(ld_options) = ' '.
 
 
"SELECT single PUTACTIVE FROM APQI INTO @DATA(ld_mode).
DATA(ld_mode) = 'A'.
 
 
"SELECT single PUTACTIVE FROM APQI INTO @DATA(ld_update).
DATA(ld_update) = 'A'.
 


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!