SAP BDC_RECORD_EDIT Function Module for Batch input record entry: Editing
BDC_RECORD_EDIT is a standard bdc record edit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Batch input record entry: Editing 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 bdc record edit FM, simply by entering the name BDC_RECORD_EDIT 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): Normal Function Module
Update:

Function BDC_RECORD_EDIT 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_EDIT'"Batch input record entry: Editing.
EXPORTING
* DISPLAY = ' ' "
IMPORTING
KEY = "
TABLES
* TRANSACTIONS = "
EXCEPTIONS
SYSTEM_FAILURE = 1
IMPORTING Parameters details for BDC_RECORD_EDIT
DISPLAY -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BDC_RECORD_EDIT
KEY -
Data type: APQIOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BDC_RECORD_EDIT
TRANSACTIONS -
Data type: BDCTHOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
SYSTEM_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BDC_RECORD_EDIT 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_key | TYPE APQI, " | |||
| lv_display | TYPE APQI, " SPACE | |||
| lt_transactions | TYPE STANDARD TABLE OF BDCTH, " | |||
| lv_system_failure | TYPE BDCTH. " |
|   CALL FUNCTION 'BDC_RECORD_EDIT' "Batch input record entry: Editing |
| EXPORTING | ||
| DISPLAY | = lv_display | |
| IMPORTING | ||
| KEY | = lv_key | |
| TABLES | ||
| TRANSACTIONS | = lt_transactions | |
| EXCEPTIONS | ||
| SYSTEM_FAILURE = 1 | ||
| . " BDC_RECORD_EDIT | ||
ABAP code using 7.40 inline data declarations to call FM BDC_RECORD_EDIT
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.| DATA(ld_display) | = ' '. | |||
Search for further information about these or an SAP related objects