SAP MMRP_PR_DATEVECTOR_GET Function Module for Soft Reading of Time Buckets Prof. GUID (Implicit Maint.)









MMRP_PR_DATEVECTOR_GET is a standard mmrp pr datevector get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Soft Reading of Time Buckets Prof. GUID (Implicit Maint.) 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 mmrp pr datevector get FM, simply by entering the name MMRP_PR_DATEVECTOR_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function MMRP_PR_DATEVECTOR_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 'MMRP_PR_DATEVECTOR_GET'"Soft Reading of Time Buckets Prof. GUID (Implicit Maint.)
  EXPORTING
   IV_SIMID =  "Planversion (operativ oder eine Simulationsversion)
*  IV_RPM_SESSION =  "Kennzeichen für temporäre Planungsdaten
   IV_RESID =  "APO-interne Nummer (UID) für Ressource
   IV_TBID =  "Zeitraster-ID
   IV_TIME_DELTA =  "Zeitdauer, Zeitdifferenz (in sec)
   IV_DIRECTION =  "Vorwärtsterminierung
*  IV_PVGUID =  "Interne Identifikation der PPE-Objekte

 IMPORTING
   EV_DATEVECID =  "GUID eines Datums-Vektors

EXCEPTIONS
   CONNECT_FAILED = 1    ERROR_IN_ANCHOR_TABLE = 2    ERROR_IN_DATEVECTOR = 3    ERROR_IN_LIVECACHE = 4
.



IMPORTING Parameters details for MMRP_PR_DATEVECTOR_GET

IV_SIMID - Planversion (operativ oder eine Simulationsversion)

Data type: /SAPAPO/VRSIOID
Optional: No
Call by Reference: Yes

IV_RPM_SESSION - Kennzeichen für temporäre Planungsdaten

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

IV_RESID - APO-interne Nummer (UID) für Ressource

Data type: /SAPAPO/RESID
Optional: No
Call by Reference: Yes

IV_TBID - Zeitraster-ID

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

IV_TIME_DELTA - Zeitdauer, Zeitdifferenz (in sec)

Data type: /SAPAPO/OM_TIME_DIFF
Optional: No
Call by Reference: Yes

IV_DIRECTION - Vorwärtsterminierung

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

IV_PVGUID - Interne Identifikation der PPE-Objekte

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

EXPORTING Parameters details for MMRP_PR_DATEVECTOR_GET

EV_DATEVECID - GUID eines Datums-Vektors

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

EXCEPTIONS details

CONNECT_FAILED -

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

ERROR_IN_ANCHOR_TABLE -

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

ERROR_IN_DATEVECTOR -

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

ERROR_IN_LIVECACHE -

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

Copy and paste ABAP code example for MMRP_PR_DATEVECTOR_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_iv_simid  TYPE /SAPAPO/VRSIOID, "   
lv_ev_datevecid  TYPE /SAPAPO/OM_DATEVECID, "   
lv_connect_failed  TYPE /SAPAPO/OM_DATEVECID, "   
lv_iv_rpm_session  TYPE RPM_SESSION, "   
lv_error_in_anchor_table  TYPE RPM_SESSION, "   
lv_iv_resid  TYPE /SAPAPO/RESID, "   
lv_error_in_datevector  TYPE /SAPAPO/RESID, "   
lv_iv_tbid  TYPE RPM_TBID, "   
lv_error_in_livecache  TYPE RPM_TBID, "   
lv_iv_time_delta  TYPE /SAPAPO/OM_TIME_DIFF, "   
lv_iv_direction  TYPE MMRP_DIRECTION, "   
lv_iv_pvguid  TYPE PPE_GUID. "   

  CALL FUNCTION 'MMRP_PR_DATEVECTOR_GET'  "Soft Reading of Time Buckets Prof. GUID (Implicit Maint.)
    EXPORTING
         IV_SIMID = lv_iv_simid
         IV_RPM_SESSION = lv_iv_rpm_session
         IV_RESID = lv_iv_resid
         IV_TBID = lv_iv_tbid
         IV_TIME_DELTA = lv_iv_time_delta
         IV_DIRECTION = lv_iv_direction
         IV_PVGUID = lv_iv_pvguid
    IMPORTING
         EV_DATEVECID = lv_ev_datevecid
    EXCEPTIONS
        CONNECT_FAILED = 1
        ERROR_IN_ANCHOR_TABLE = 2
        ERROR_IN_DATEVECTOR = 3
        ERROR_IN_LIVECACHE = 4
. " MMRP_PR_DATEVECTOR_GET




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