SAP BDL_INTERFACE_DIFFS_DATCOL Function Module for evaluate differences between local fuba interface and in our tables descri
BDL_INTERFACE_DIFFS_DATCOL is a standard bdl interface diffs datcol SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for evaluate differences between local fuba interface and in our tables descri 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 bdl interface diffs datcol FM, simply by entering the name BDL_INTERFACE_DIFFS_DATCOL into the relevant SAP transaction such as SE37 or SE38.
Function Group: BDL3
Program Name: SAPLBDL3
Main Program: SAPLBDL3
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BDL_INTERFACE_DIFFS_DATCOL 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 'BDL_INTERFACE_DIFFS_DATCOL'"evaluate differences between local fuba interface and in our tables descri.
EXPORTING
SESSIONNR = "
MANDANT = "
SID = "Name of SAP R/3 System
DATE = "Date and time, current (application server) date
SESSION_TYPE = "Single-character flag
INSTALL_NO = "10 digit number
CUST_NO = "10 digit number
SEQNO = "Sequence number
EXCEPTIONS
FUNCTION_NOT_FOUND = 1 INVALID_NAME = 2 X_ERROR = 3 NAMETAB_ERROR = 4
IMPORTING Parameters details for BDL_INTERFACE_DIFFS_DATCOL
SESSIONNR -
Data type: BDLDATKEY-SESSIONNROptional: No
Call by Reference: No ( called with pass by value option)
MANDANT -
Data type: BDLDATKEY-MANDANTOptional: No
Call by Reference: No ( called with pass by value option)
SID - Name of SAP R/3 System
Data type: BDLDTOC-SIDOptional: No
Call by Reference: No ( called with pass by value option)
DATE - Date and time, current (application server) date
Data type: BDLDTOC-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
SESSION_TYPE - Single-character flag
Data type: BDL_DATKEY-TYPEOptional: No
Call by Reference: No ( called with pass by value option)
INSTALL_NO - 10 digit number
Data type: BDL_DATKEY-INSTALL_NOOptional: No
Call by Reference: No ( called with pass by value option)
CUST_NO - 10 digit number
Data type: BDL_DATKEY-CUST_NOOptional: No
Call by Reference: No ( called with pass by value option)
SEQNO - Sequence number
Data type: BDL_DATKEY-SEQNOOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FUNCTION_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_NAME -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
X_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NAMETAB_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BDL_INTERFACE_DIFFS_DATCOL 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_sessionnr | TYPE BDLDATKEY-SESSIONNR, " | |||
| lv_function_not_found | TYPE BDLDATKEY, " | |||
| lv_mandant | TYPE BDLDATKEY-MANDANT, " | |||
| lv_invalid_name | TYPE BDLDATKEY, " | |||
| lv_sid | TYPE BDLDTOC-SID, " | |||
| lv_x_error | TYPE BDLDTOC, " | |||
| lv_date | TYPE BDLDTOC-DATUM, " | |||
| lv_nametab_error | TYPE BDLDTOC, " | |||
| lv_session_type | TYPE BDL_DATKEY-TYPE, " | |||
| lv_install_no | TYPE BDL_DATKEY-INSTALL_NO, " | |||
| lv_cust_no | TYPE BDL_DATKEY-CUST_NO, " | |||
| lv_seqno | TYPE BDL_DATKEY-SEQNO. " |
|   CALL FUNCTION 'BDL_INTERFACE_DIFFS_DATCOL' "evaluate differences between local fuba interface and in our tables descri |
| EXPORTING | ||
| SESSIONNR | = lv_sessionnr | |
| MANDANT | = lv_mandant | |
| SID | = lv_sid | |
| DATE | = lv_date | |
| SESSION_TYPE | = lv_session_type | |
| INSTALL_NO | = lv_install_no | |
| CUST_NO | = lv_cust_no | |
| SEQNO | = lv_seqno | |
| EXCEPTIONS | ||
| FUNCTION_NOT_FOUND = 1 | ||
| INVALID_NAME = 2 | ||
| X_ERROR = 3 | ||
| NAMETAB_ERROR = 4 | ||
| . " BDL_INTERFACE_DIFFS_DATCOL | ||
ABAP code using 7.40 inline data declarations to call FM BDL_INTERFACE_DIFFS_DATCOL
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 SESSIONNR FROM BDLDATKEY INTO @DATA(ld_sessionnr). | ||||
| "SELECT single MANDANT FROM BDLDATKEY INTO @DATA(ld_mandant). | ||||
| "SELECT single SID FROM BDLDTOC INTO @DATA(ld_sid). | ||||
| "SELECT single DATUM FROM BDLDTOC INTO @DATA(ld_date). | ||||
| "SELECT single TYPE FROM BDL_DATKEY INTO @DATA(ld_session_type). | ||||
| "SELECT single INSTALL_NO FROM BDL_DATKEY INTO @DATA(ld_install_no). | ||||
| "SELECT single CUST_NO FROM BDL_DATKEY INTO @DATA(ld_cust_no). | ||||
| "SELECT single SEQNO FROM BDL_DATKEY INTO @DATA(ld_seqno). | ||||
Search for further information about these or an SAP related objects