SAP BDL_GET_MAPPING_INFORMATION Function Module for Is mapping required? If yes, provide mapped sessno, clnt

Search SAP Function Modules

BDL_GET_MAPPING_INFORMATION is a standard bdl get mapping information SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Is mapping required? If yes, provide mapped sessno, clnt 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 get mapping information FM, simply by entering the name BDL_GET_MAPPING_INFORMATION into the relevant SAP transaction such as SE37 or SE38.

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

Function BDL_GET_MAPPING_INFORMATION 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_GET_MAPPING_INFORMATION'"Is mapping required? If yes, provide mapped sessno, clnt
  EXPORTING
*  ORIGINAL_SESSNO =  "Character field length = 10
*  ORIGINAL_CLIENT =  "3-Byte field
*  SOURCE_DEST =  "Logical destination (specified in function call)
*  TARGET_DEST =  "Logical destination (specified in function call)
*  SESSION_TYPE =  "3-Byte field

 IMPORTING
   MAPPED_SESSNO =  "Character field length = 10
   MAPPED_CLIENT =  "3-Byte field

TABLES
*  DEST_DATA =  "Destinations and RFC block sizes for data transfer

EXCEPTIONS
   SESSION_UNKNOWN = 1    SESSION_TYPE_UNKNOWN = 2    MAPPING_NOT_NEEDED = 3    MAPPING_TO_BE_AVOIDED = 4    MAPPED_SESSION_ILLEGAL = 5    NO_MAPPING = 6    SPURIOUS_MAPPING = 7 

.

IMPORTING Parameters details for BDL_GET_MAPPING_INFORMATION

ORIGINAL_SESSNO - Character field length = 10

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

ORIGINAL_CLIENT - 3-Byte field

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

SOURCE_DEST - Logical destination (specified in function call)

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

TARGET_DEST - Logical destination (specified in function call)

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

SESSION_TYPE - 3-Byte field

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

EXPORTING Parameters details for BDL_GET_MAPPING_INFORMATION

MAPPED_SESSNO - Character field length = 10

Data type: BDLDATKEY-SESSIONNR
Optional: No
Call by Reference: Yes

MAPPED_CLIENT - 3-Byte field

Data type: BDLDATKEY-MANDANT
Optional: No
Call by Reference: Yes

TABLES Parameters details for BDL_GET_MAPPING_INFORMATION

DEST_DATA - Destinations and RFC block sizes for data transfer

Data type: BDLSESDEST
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

SESSION_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

SESSION_TYPE_UNKNOWN -

Data type:
Optional: No
Call by Reference: Yes

MAPPING_NOT_NEEDED -

Data type:
Optional: No
Call by Reference: Yes

MAPPING_TO_BE_AVOIDED -

Data type:
Optional: No
Call by Reference: Yes

MAPPED_SESSION_ILLEGAL -

Data type:
Optional: No
Call by Reference: Yes

NO_MAPPING -

Data type:
Optional: No
Call by Reference: Yes

SPURIOUS_MAPPING -

Data type:
Optional: No
Call by Reference: Yes

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

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