SAP CBDU_BU05_DGREL_LOAD_BUF_IOT Function Module for NOTRANSL: Daten von der Datenbank bis zur Iotab transportieren

Search SAP Function Modules

CBDU_BU05_DGREL_LOAD_BUF_IOT is a standard cbdu bu05 dgrel load buf iot SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Daten von der Datenbank bis zur Iotab transportieren 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 cbdu bu05 dgrel load buf iot FM, simply by entering the name CBDU_BU05_DGREL_LOAD_BUF_IOT into the relevant SAP transaction such as SE37 or SE38.

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

Function CBDU_BU05_DGREL_LOAD_BUF_IOT 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 'CBDU_BU05_DGREL_LOAD_BUF_IOT'"NOTRANSL: Daten von der Datenbank bis zur Iotab transportieren
  EXPORTING
   I_AENNR =  "Change Number
   I_VALDAT =  "Key Date
*  I_DO_LOCKING = ESP1_TRUE "DE-EN-LANG-SWITCH-NO-TRANSLATION
   I_FURTHER_SETTINGS =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  I_FLG_READ_UNPARKED_ONLY = ESP1_FALSE "DE-EN-LANG-SWITCH-NO-TRANSLATION

 IMPORTING
   E_FLG_LOCKFAIL =  "Indicator: Data record is currently valid
   E_FLG_CHACOLL =  "Indicator: Change number collision

TABLES
   E_IOTAB =  "EHS: IOTAB for Product Release
   I_KEYTAB =  "EHS: Minimum Key for FM Call Interface

EXCEPTIONS
   BUFFER_ERROR = 1    NO_RECORD_FOUND = 2 

.

IMPORTING Parameters details for CBDU_BU05_DGREL_LOAD_BUF_IOT

I_AENNR - Change Number

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

I_VALDAT - Key Date

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

I_DO_LOCKING - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

I_FURTHER_SETTINGS - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

I_FLG_READ_UNPARKED_ONLY - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

EXPORTING Parameters details for CBDU_BU05_DGREL_LOAD_BUF_IOT

E_FLG_LOCKFAIL - Indicator: Data record is currently valid

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

E_FLG_CHACOLL - Indicator: Change number collision

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

TABLES Parameters details for CBDU_BU05_DGREL_LOAD_BUF_IOT

E_IOTAB - EHS: IOTAB for Product Release

Data type: RCBDUDGRELIOT
Optional: No
Call by Reference: Yes

I_KEYTAB - EHS: Minimum Key for FM Call Interface

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

EXCEPTIONS details

BUFFER_ERROR -

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

NO_RECORD_FOUND -

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

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

ABAP code using 7.40 inline data declarations to call FM CBDU_BU05_DGREL_LOAD_BUF_IOT

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.

Search for further information about these or an SAP related objects