SAP BSP_DLLC_TRANS_TRANSP_2_TRANSL Function Module for Get Translation object from a Transport object (Customer)
BSP_DLLC_TRANS_TRANSP_2_TRANSL is a standard bsp dllc trans transp 2 transl SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Translation object from a Transport object (Customer) 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 bsp dllc trans transp 2 transl FM, simply by entering the name BSP_DLLC_TRANS_TRANSP_2_TRANSL into the relevant SAP transaction such as SE37 or SE38.
Function Group: BSP_DYN_DESIGN_TRANSLATION
Program Name: SAPLBSP_DYN_DESIGN_TRANSLATION
Main Program: SAPLBSP_DYN_DESIGN_TRANSLATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BSP_DLLC_TRANS_TRANSP_2_TRANSL 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 'BSP_DLLC_TRANS_TRANSP_2_TRANSL'"Get Translation object from a Transport object (Customer).
TABLES
IT_OBJECTS = "Change & Transport System: Object Entries of Requests/Tasks
IT_KEYS = "Change & Transport System: Key Entries of Requests/Tasks
ET_OBJECTS = "Object List Structure
TABLES Parameters details for BSP_DLLC_TRANS_TRANSP_2_TRANSL
IT_OBJECTS - Change & Transport System: Object Entries of Requests/Tasks
Data type: E071Optional: No
Call by Reference: No ( called with pass by value option)
IT_KEYS - Change & Transport System: Key Entries of Requests/Tasks
Data type: E071KOptional: No
Call by Reference: No ( called with pass by value option)
ET_OBJECTS - Object List Structure
Data type: LXE_COLOBXOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BSP_DLLC_TRANS_TRANSP_2_TRANSL 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: | ||||
| lt_it_objects | TYPE STANDARD TABLE OF E071, " | |||
| lt_it_keys | TYPE STANDARD TABLE OF E071K, " | |||
| lt_et_objects | TYPE STANDARD TABLE OF LXE_COLOBX. " |
|   CALL FUNCTION 'BSP_DLLC_TRANS_TRANSP_2_TRANSL' "Get Translation object from a Transport object (Customer) |
| TABLES | ||
| IT_OBJECTS | = lt_it_objects | |
| IT_KEYS | = lt_it_keys | |
| ET_OBJECTS | = lt_et_objects | |
| . " BSP_DLLC_TRANS_TRANSP_2_TRANSL | ||
ABAP code using 7.40 inline data declarations to call FM BSP_DLLC_TRANS_TRANSP_2_TRANSL
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