SAP UPB_CMI_SEN_VERSIONS_GET Function Module for









UPB_CMI_SEN_VERSIONS_GET is a standard upb cmi sen versions get 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 upb cmi sen versions get FM, simply by entering the name UPB_CMI_SEN_VERSIONS_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function UPB_CMI_SEN_VERSIONS_GET 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 'UPB_CMI_SEN_VERSIONS_GET'"
EXPORTING
I_CMI = "
* I_GET_BWTEXTS = ' ' "
IS_DATASOURCE = "
I_CHANM = "

IMPORTING
ET_CMI_SEN_VERSIONS_ALV = "

EXCEPTIONS
NOTHING_FOUND = 1
.



IMPORTING Parameters details for UPB_CMI_SEN_VERSIONS_GET

I_CMI -

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

I_GET_BWTEXTS -

Data type: AS4FLAG
Default: ' '
Optional: Yes
Call by Reference: Yes

IS_DATASOURCE -

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

I_CHANM -

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

EXPORTING Parameters details for UPB_CMI_SEN_VERSIONS_GET

ET_CMI_SEN_VERSIONS_ALV -

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

EXCEPTIONS details

NOTHING_FOUND -

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

Copy and paste ABAP code example for UPB_CMI_SEN_VERSIONS_GET 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_i_cmi  TYPE UPB_Y_CMI, "   
lv_nothing_found  TYPE UPB_Y_CMI, "   
lv_et_cmi_sen_versions_alv  TYPE UPB_YT_CMI_VERS_ALV, "   
lv_i_get_bwtexts  TYPE AS4FLAG, "   ' '
lv_is_datasource  TYPE UPB_YS_CMI_DATASOURCE, "   
lv_i_chanm  TYPE UPC_Y_CHANM. "   

  CALL FUNCTION 'UPB_CMI_SEN_VERSIONS_GET'  "
    EXPORTING
         I_CMI = lv_i_cmi
         I_GET_BWTEXTS = lv_i_get_bwtexts
         IS_DATASOURCE = lv_is_datasource
         I_CHANM = lv_i_chanm
    IMPORTING
         ET_CMI_SEN_VERSIONS_ALV = lv_et_cmi_sen_versions_alv
    EXCEPTIONS
        NOTHING_FOUND = 1
. " UPB_CMI_SEN_VERSIONS_GET




ABAP code using 7.40 inline data declarations to call FM UPB_CMI_SEN_VERSIONS_GET

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.

 
 
 
DATA(ld_i_get_bwtexts) = ' '.
 
 
 


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!