SAP BDC_OBJECT_UPDATE Function Module for Batch input object: Save
BDC_OBJECT_UPDATE is a standard bdc object update 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 object: Save 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 object update FM, simply by entering the name BDC_OBJECT_UPDATE 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_OBJECT_UPDATE 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_OBJECT_UPDATE'"Batch input object: Save.
EXPORTING
QUEUE_ID = "Unique database key
IMPORTING
KEY = "Data record: Key and info record
TABLES
DYNPROTAB = "Table for screens of object
EXCEPTIONS
INVALID_QUEUE_ID = 1 SYSTEM_FAILURE = 2
IMPORTING Parameters details for BDC_OBJECT_UPDATE
QUEUE_ID - Unique database key
Data type: APQD-QIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BDC_OBJECT_UPDATE
KEY - Data record: Key and info record
Data type: APQIOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BDC_OBJECT_UPDATE
DYNPROTAB - Table for screens of object
Data type: BDCDATAOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_QUEUE_ID - Invalid database key
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE - System error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BDC_OBJECT_UPDATE 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_queue_id | TYPE APQD-QID, " | |||
| lt_dynprotab | TYPE STANDARD TABLE OF BDCDATA, " | |||
| lv_invalid_queue_id | TYPE BDCDATA, " | |||
| lv_system_failure | TYPE BDCDATA. " |
|   CALL FUNCTION 'BDC_OBJECT_UPDATE' "Batch input object: Save |
| EXPORTING | ||
| QUEUE_ID | = lv_queue_id | |
| IMPORTING | ||
| KEY | = lv_key | |
| TABLES | ||
| DYNPROTAB | = lt_dynprotab | |
| EXCEPTIONS | ||
| INVALID_QUEUE_ID = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| . " BDC_OBJECT_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM BDC_OBJECT_UPDATE
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 QID FROM APQD INTO @DATA(ld_queue_id). | ||||
Search for further information about these or an SAP related objects