SAP BM_OBJECT_TRANSPORT Function Module for









BM_OBJECT_TRANSPORT is a standard bm object transport SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 bm object transport FM, simply by entering the name BM_OBJECT_TRANSPORT into the relevant SAP transaction such as SE37 or SE38.

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



Function BM_OBJECT_TRANSPORT 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 'BM_OBJECT_TRANSPORT'"
  EXPORTING
   I_OBJECT_TYPE =  "Object Type
   I_OBJECT_ID =  "
*  I_CORR_INSERT = 'X' "
*  I_TRANSPORT_TYPE = 'K' "
*  I_PARAMS = ' ' "

CHANGING
*  OBJECT_LIST =  "Interface Structures for Objects in CTS
*  KEY_LIST =  "Change & Transport System: Key Entries of Requests/Tasks
*  TRANSPORT_ORDER =  "Request/Task
*  MESSAGES =  "Messages

TABLES
*  I_ADDITIONAL_LANGUAGES =  "Language Key
*  I_DEVCLASSES =  "Range for DEVCLASS
.



IMPORTING Parameters details for BM_OBJECT_TRANSPORT

I_OBJECT_TYPE - Object Type

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

I_OBJECT_ID -

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

I_CORR_INSERT -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_TRANSPORT_TYPE -

Data type: C
Default: 'K'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PARAMS -

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

CHANGING Parameters details for BM_OBJECT_TRANSPORT

OBJECT_LIST - Interface Structures for Objects in CTS

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

KEY_LIST - Change & Transport System: Key Entries of Requests/Tasks

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

TRANSPORT_ORDER - Request/Task

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

MESSAGES - Messages

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

TABLES Parameters details for BM_OBJECT_TRANSPORT

I_ADDITIONAL_LANGUAGES - Language Key

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

I_DEVCLASSES - Range for DEVCLASS

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

Copy and paste ABAP code example for BM_OBJECT_TRANSPORT 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_object_list  TYPE STROBJLIST, "   
lv_i_object_type  TYPE BMOBJECT-TYPE, "   
lt_i_additional_languages  TYPE STANDARD TABLE OF T002, "   
lv_key_list  TYPE STRKEYLIST, "   
lv_i_object_id  TYPE ANY, "   
lt_i_devclasses  TYPE STANDARD TABLE OF BMSELDEVCL, "   
lv_i_corr_insert  TYPE C, "   'X'
lv_transport_order  TYPE TRKORR, "   
lv_messages  TYPE BMMSGTAB, "   
lv_i_transport_type  TYPE C, "   'K'
lv_i_params  TYPE BMTRPARAM. "   SPACE

  CALL FUNCTION 'BM_OBJECT_TRANSPORT'  "
    EXPORTING
         I_OBJECT_TYPE = lv_i_object_type
         I_OBJECT_ID = lv_i_object_id
         I_CORR_INSERT = lv_i_corr_insert
         I_TRANSPORT_TYPE = lv_i_transport_type
         I_PARAMS = lv_i_params
    CHANGING
         OBJECT_LIST = lv_object_list
         KEY_LIST = lv_key_list
         TRANSPORT_ORDER = lv_transport_order
         MESSAGES = lv_messages
    TABLES
         I_ADDITIONAL_LANGUAGES = lt_i_additional_languages
         I_DEVCLASSES = lt_i_devclasses
. " BM_OBJECT_TRANSPORT




ABAP code using 7.40 inline data declarations to call FM BM_OBJECT_TRANSPORT

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 TYPE FROM BMOBJECT INTO @DATA(ld_i_object_type).
 
 
 
 
 
DATA(ld_i_corr_insert) = 'X'.
 
 
 
DATA(ld_i_transport_type) = 'K'.
 
DATA(ld_i_params) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!