SAP UPB_PM_GET_PROFILE Function Module for Profile or main planning area
UPB_PM_GET_PROFILE is a standard upb pm get 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 Profile or main planning area 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 upb pm get profile FM, simply by entering the name UPB_PM_GET_PROFILE into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPB_PM
Program Name: SAPLUPB_PM
Main Program: SAPLUPB_PM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPB_PM_GET_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 'UPB_PM_GET_PROFILE'"Profile or main planning area.
EXPORTING
I_APPLC = "Planning Application
* I_SUBCL = "Subgrouping within a grouping
* I_NO_POPUP = 'X' "Single-Character Flag
IMPORTING
E_PROFILE = "Planning Profile
E_MAIN_AREA = "Planning Area
E_USES_PROFILE = "Single-Character Flag
E_USES_AREA = "Single-Character Flag
EXCEPTIONS
NO_AREA_SET = 1
IMPORTING Parameters details for UPB_PM_GET_PROFILE
I_APPLC - Planning Application
Data type: UPB_Y_APPLCOptional: No
Call by Reference: Yes
I_SUBCL - Subgrouping within a grouping
Data type: UPC_Y_SUBCLASSOptional: Yes
Call by Reference: Yes
I_NO_POPUP - Single-Character Flag
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for UPB_PM_GET_PROFILE
E_PROFILE - Planning Profile
Data type: UPC_Y_PROFILEOptional: No
Call by Reference: Yes
E_MAIN_AREA - Planning Area
Data type: UPC_Y_AREAOptional: No
Call by Reference: Yes
E_USES_PROFILE - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
E_USES_AREA - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: Yes
EXCEPTIONS details
NO_AREA_SET -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPB_PM_GET_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_i_applc | TYPE UPB_Y_APPLC, " | |||
| lv_e_profile | TYPE UPC_Y_PROFILE, " | |||
| lv_no_area_set | TYPE UPC_Y_PROFILE, " | |||
| lv_i_subcl | TYPE UPC_Y_SUBCLASS, " | |||
| lv_e_main_area | TYPE UPC_Y_AREA, " | |||
| lv_i_no_popup | TYPE CHAR1, " 'X' | |||
| lv_e_uses_profile | TYPE CHAR1, " | |||
| lv_e_uses_area | TYPE CHAR1. " |
|   CALL FUNCTION 'UPB_PM_GET_PROFILE' "Profile or main planning area |
| EXPORTING | ||
| I_APPLC | = lv_i_applc | |
| I_SUBCL | = lv_i_subcl | |
| I_NO_POPUP | = lv_i_no_popup | |
| IMPORTING | ||
| E_PROFILE | = lv_e_profile | |
| E_MAIN_AREA | = lv_e_main_area | |
| E_USES_PROFILE | = lv_e_uses_profile | |
| E_USES_AREA | = lv_e_uses_area | |
| EXCEPTIONS | ||
| NO_AREA_SET = 1 | ||
| . " UPB_PM_GET_PROFILE | ||
ABAP code using 7.40 inline data declarations to call FM UPB_PM_GET_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.| DATA(ld_i_no_popup) | = 'X'. | |||
Search for further information about these or an SAP related objects