SAP UMC_CUBE_TIMESTAMP_GET Function Module for









UMC_CUBE_TIMESTAMP_GET is a standard umc cube timestamp 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 umc cube timestamp get FM, simply by entering the name UMC_CUBE_TIMESTAMP_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function UMC_CUBE_TIMESTAMP_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 'UMC_CUBE_TIMESTAMP_GET'"
  EXPORTING
   I_DESTINATION =  "RFC Destination
   I_INFOCUBE =  "InfoCube (BW Internal Identifier)

 IMPORTING
   E_TIMESTMP =  "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

EXCEPTIONS
   RFC_ERROR = 1    CUBE_NOT_FOUND = 2    BWSERVER_NOT_EXIST = 3
.



IMPORTING Parameters details for UMC_CUBE_TIMESTAMP_GET

I_DESTINATION - RFC Destination

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

I_INFOCUBE - InfoCube (BW Internal Identifier)

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

EXPORTING Parameters details for UMC_CUBE_TIMESTAMP_GET

E_TIMESTMP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

EXCEPTIONS details

RFC_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CUBE_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

BWSERVER_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UMC_CUBE_TIMESTAMP_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_rfc_error  TYPE STRING, "   
lv_e_timestmp  TYPE RSTIMESTMP, "   
lv_i_destination  TYPE UMC_Y_RFCDEST, "   
lv_i_infocube  TYPE UMC_Y_ICUBE, "   
lv_cube_not_found  TYPE UMC_Y_ICUBE, "   
lv_bwserver_not_exist  TYPE UMC_Y_ICUBE. "   

  CALL FUNCTION 'UMC_CUBE_TIMESTAMP_GET'  "
    EXPORTING
         I_DESTINATION = lv_i_destination
         I_INFOCUBE = lv_i_infocube
    IMPORTING
         E_TIMESTMP = lv_e_timestmp
    EXCEPTIONS
        RFC_ERROR = 1
        CUBE_NOT_FOUND = 2
        BWSERVER_NOT_EXIST = 3
. " UMC_CUBE_TIMESTAMP_GET




ABAP code using 7.40 inline data declarations to call FM UMC_CUBE_TIMESTAMP_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.

 
 
 
 
 
 


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!