SAP RPM_GET_TIME_DETAILS Function Module for Genearate Timeand Rate IDoc for RPM









RPM_GET_TIME_DETAILS is a standard rpm get time details SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Genearate Timeand Rate IDoc for RPM 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 rpm get time details FM, simply by entering the name RPM_GET_TIME_DETAILS into the relevant SAP transaction such as SE37 or SE38.

Function Group: RPM_HR_INTEGRATION
Program Name: SAPLRPM_HR_INTEGRATION
Main Program: SAPLRPM_HR_INTEGRATION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RPM_GET_TIME_DETAILS 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 'RPM_GET_TIME_DETAILS'"Genearate Timeand Rate IDoc for RPM
  EXPORTING
   IV_PLAN_VERSION =  "Plan Version
*  IV_EVAL_BEGDA =  "Date and time, current (application server) date
*  IV_EVAL_ENDDA =  "Date and time, current (application server) date
   IV_RECEIVER_PARTNER =  "Logical destination (specified in function call)
   IV_OTYPE =  "Object Type

 IMPORTING
   EV_SUBRC =  "Return value, return value after ABAP statements

TABLES
*  ET_LOG_TAB =  "Error logging
   ET_PERNR_TAB =  "Pernr table
.



IMPORTING Parameters details for RPM_GET_TIME_DETAILS

IV_PLAN_VERSION - Plan Version

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

IV_EVAL_BEGDA - Date and time, current (application server) date

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

IV_EVAL_ENDDA - Date and time, current (application server) date

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

IV_RECEIVER_PARTNER - Logical destination (specified in function call)

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

IV_OTYPE - Object Type

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

EXPORTING Parameters details for RPM_GET_TIME_DETAILS

EV_SUBRC - Return value, return value after ABAP statements

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

TABLES Parameters details for RPM_GET_TIME_DETAILS

ET_LOG_TAB - Error logging

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

ET_PERNR_TAB - Pernr table

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

Copy and paste ABAP code example for RPM_GET_TIME_DETAILS 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_ev_subrc  TYPE SY-SUBRC, "   
lt_et_log_tab  TYPE STANDARD TABLE OF RPM_TS_ERR, "   
lv_iv_plan_version  TYPE PLVAR, "   
lt_et_pernr_tab  TYPE STANDARD TABLE OF RPM_TS_PERNR, "   
lv_iv_eval_begda  TYPE SY-DATUM, "   
lv_iv_eval_endda  TYPE SY-DATUM, "   
lv_iv_receiver_partner  TYPE TBDLS-LOGSYS, "   
lv_iv_otype  TYPE OTYPE. "   

  CALL FUNCTION 'RPM_GET_TIME_DETAILS'  "Genearate Timeand Rate IDoc for RPM
    EXPORTING
         IV_PLAN_VERSION = lv_iv_plan_version
         IV_EVAL_BEGDA = lv_iv_eval_begda
         IV_EVAL_ENDDA = lv_iv_eval_endda
         IV_RECEIVER_PARTNER = lv_iv_receiver_partner
         IV_OTYPE = lv_iv_otype
    IMPORTING
         EV_SUBRC = lv_ev_subrc
    TABLES
         ET_LOG_TAB = lt_et_log_tab
         ET_PERNR_TAB = lt_et_pernr_tab
. " RPM_GET_TIME_DETAILS




ABAP code using 7.40 inline data declarations to call FM RPM_GET_TIME_DETAILS

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 SUBRC FROM SY INTO @DATA(ld_ev_subrc).
 
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_iv_eval_begda).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_iv_eval_endda).
 
"SELECT single LOGSYS FROM TBDLS INTO @DATA(ld_iv_receiver_partner).
 
 


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!