SAP MPP_GET_MPP_PROFILE Function Module for NOTRANSL: Reads the profile for manpower planning









MPP_GET_MPP_PROFILE is a standard mpp get mpp profile SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Reads the profile for manpower planning 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 mpp get mpp profile FM, simply by entering the name MPP_GET_MPP_PROFILE into the relevant SAP transaction such as SE37 or SE38.

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



Function MPP_GET_MPP_PROFILE 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 'MPP_GET_MPP_PROFILE'"NOTRANSL: Reads the profile for manpower planning
EXPORTING
* PROFILE_ID = ' ' "Profile for work force planning
* RESET_BUFFER_IMP = ' ' "Generic Type

IMPORTING
PROFILE_ID = "Profile for work force planning
MPPPRO = "Customizing fields for Workforce Planning
PROFILE_TEXT = "Profile for work force planning
DATE_FROM = "ABAP System Field: Current Date of Application Server
DATE_TO = "ABAP System Field: Current Date of Application Server

TABLES
* T_PERIODS_EXP = "

EXCEPTIONS
NO_CURRENT_PROFILE = 1 PROFILE_NOT_FOUND = 2 INTERVAL_ERROR = 3
.



IMPORTING Parameters details for MPP_GET_MPP_PROFILE

PROFILE_ID - Profile for work force planning

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

RESET_BUFFER_IMP - Generic Type

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

EXPORTING Parameters details for MPP_GET_MPP_PROFILE

PROFILE_ID - Profile for work force planning

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

MPPPRO - Customizing fields for Workforce Planning

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

PROFILE_TEXT - Profile for work force planning

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

DATE_FROM - ABAP System Field: Current Date of Application Server

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

DATE_TO - ABAP System Field: Current Date of Application Server

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

TABLES Parameters details for MPP_GET_MPP_PROFILE

T_PERIODS_EXP -

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

EXCEPTIONS details

NO_CURRENT_PROFILE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

PROFILE_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

INTERVAL_ERROR -

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

Copy and paste ABAP code example for MPP_GET_MPP_PROFILE 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_profile_id  TYPE TCYMPP-MPPPRO_ID, "   
lv_profile_id  TYPE TCYMPP-MPPPRO_ID, "   SPACE
lt_t_periods_exp  TYPE STANDARD TABLE OF MPPP_PERIODS_TYPE, "   
lv_no_current_profile  TYPE MPPP_PERIODS_TYPE, "   
lv_mpppro  TYPE CYMPPPRO, "   
lv_reset_buffer_imp  TYPE C, "   SPACE
lv_profile_not_found  TYPE C, "   
lv_profile_text  TYPE TCYMPPT-MPPPROTXT, "   
lv_interval_error  TYPE TCYMPPT, "   
lv_date_from  TYPE SY-DATUM, "   
lv_date_to  TYPE SY-DATUM. "   

  CALL FUNCTION 'MPP_GET_MPP_PROFILE'  "NOTRANSL: Reads the profile for manpower planning
    EXPORTING
         PROFILE_ID = lv_profile_id
         RESET_BUFFER_IMP = lv_reset_buffer_imp
    IMPORTING
         PROFILE_ID = lv_profile_id
         MPPPRO = lv_mpppro
         PROFILE_TEXT = lv_profile_text
         DATE_FROM = lv_date_from
         DATE_TO = lv_date_to
    TABLES
         T_PERIODS_EXP = lt_t_periods_exp
    EXCEPTIONS
        NO_CURRENT_PROFILE = 1
        PROFILE_NOT_FOUND = 2
        INTERVAL_ERROR = 3
. " MPP_GET_MPP_PROFILE




ABAP code using 7.40 inline data declarations to call FM MPP_GET_MPP_PROFILE

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 MPPPRO_ID FROM TCYMPP INTO @DATA(ld_profile_id).
 
"SELECT single MPPPRO_ID FROM TCYMPP INTO @DATA(ld_profile_id).
DATA(ld_profile_id) = ' '.
 
 
 
 
DATA(ld_reset_buffer_imp) = ' '.
 
 
"SELECT single MPPPROTXT FROM TCYMPPT INTO @DATA(ld_profile_text).
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_date_from).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_date_to).
 


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!