SAP TEM_MAINTAIN_PROFILE_UI Function Module for Read Plan Profile and Transfer Flat to UI
TEM_MAINTAIN_PROFILE_UI is a standard tem maintain profile ui SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Plan Profile and Transfer Flat to UI 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 tem maintain profile ui FM, simply by entering the name TEM_MAINTAIN_PROFILE_UI into the relevant SAP transaction such as SE37 or SE38.
Function Group: TEM_PROFILE_AL
Program Name: SAPLTEM_PROFILE_AL
Main Program: SAPLTEM_PROFILE_AL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TEM_MAINTAIN_PROFILE_UI 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 'TEM_MAINTAIN_PROFILE_UI'"Read Plan Profile and Transfer Flat to UI.
EXPORTING
IM_PROFILE_ID = "Planning Profile
IM_MODE = "Mode (Display, Change, Create, Delete)
* IM_FLG_INIT = ' ' "'X' = Erster Aufruf (= interne Objektinstanziierung)
* IM_FLG_SAVE = ' ' "'X' = Sichern
* IM_FLG_EXIT = ' ' "'X' = Exit
CHANGING
C_STR_PROFILE_MAIN_UI = "Screen-UI-Elements for Master Data Exp. Plng Profile MAIN
C_TAB_POLICY = "Table Type for Policy
C_TAB_FILTER = "Table Type for Exposure Management Filter
EXCEPTIONS
PROFILE_NOT_FOUND = 1 VIOLATE_SINGLETON = 2 PROFILE_LOCKED = 3 NO_AUTHORITY = 4 ERROR = 5
IMPORTING Parameters details for TEM_MAINTAIN_PROFILE_UI
IM_PROFILE_ID - Planning Profile
Data type: TEM_PLANNING_PROFILEOptional: No
Call by Reference: Yes
IM_MODE - Mode (Display, Change, Create, Delete)
Data type: TPM_TRG_MODEOptional: No
Call by Reference: Yes
IM_FLG_INIT - 'X' = Erster Aufruf (= interne Objektinstanziierung)
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: Yes
IM_FLG_SAVE - 'X' = Sichern
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: Yes
IM_FLG_EXIT - 'X' = Exit
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for TEM_MAINTAIN_PROFILE_UI
C_STR_PROFILE_MAIN_UI - Screen-UI-Elements for Master Data Exp. Plng Profile MAIN
Data type: TEMS_PROFILE_MAIN_UIOptional: No
Call by Reference: Yes
C_TAB_POLICY - Table Type for Policy
Data type: TEMY_POLICYOptional: No
Call by Reference: Yes
C_TAB_FILTER - Table Type for Exposure Management Filter
Data type: TEMY_FILTEROptional: No
Call by Reference: Yes
EXCEPTIONS details
PROFILE_NOT_FOUND - Profile Does Not Exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
VIOLATE_SINGLETON - Profile-objekt ist schon instanziiert
Data type:Optional: No
Call by Reference: Yes
PROFILE_LOCKED - Profile is Locked
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY - No Authorization
Data type:Optional: No
Call by Reference: Yes
ERROR - Other Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TEM_MAINTAIN_PROFILE_UI 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_im_profile_id | TYPE TEM_PLANNING_PROFILE, " | |||
| lv_profile_not_found | TYPE TEM_PLANNING_PROFILE, " | |||
| lv_c_str_profile_main_ui | TYPE TEMS_PROFILE_MAIN_UI, " | |||
| lv_im_mode | TYPE TPM_TRG_MODE, " | |||
| lv_c_tab_policy | TYPE TEMY_POLICY, " | |||
| lv_violate_singleton | TYPE TEMY_POLICY, " | |||
| lv_im_flg_init | TYPE CHAR1, " SPACE | |||
| lv_c_tab_filter | TYPE TEMY_FILTER, " | |||
| lv_profile_locked | TYPE TEMY_FILTER, " | |||
| lv_im_flg_save | TYPE CHAR1, " SPACE | |||
| lv_no_authority | TYPE CHAR1, " | |||
| lv_error | TYPE CHAR1, " | |||
| lv_im_flg_exit | TYPE CHAR1. " SPACE |
|   CALL FUNCTION 'TEM_MAINTAIN_PROFILE_UI' "Read Plan Profile and Transfer Flat to UI |
| EXPORTING | ||
| IM_PROFILE_ID | = lv_im_profile_id | |
| IM_MODE | = lv_im_mode | |
| IM_FLG_INIT | = lv_im_flg_init | |
| IM_FLG_SAVE | = lv_im_flg_save | |
| IM_FLG_EXIT | = lv_im_flg_exit | |
| CHANGING | ||
| C_STR_PROFILE_MAIN_UI | = lv_c_str_profile_main_ui | |
| C_TAB_POLICY | = lv_c_tab_policy | |
| C_TAB_FILTER | = lv_c_tab_filter | |
| EXCEPTIONS | ||
| PROFILE_NOT_FOUND = 1 | ||
| VIOLATE_SINGLETON = 2 | ||
| PROFILE_LOCKED = 3 | ||
| NO_AUTHORITY = 4 | ||
| ERROR = 5 | ||
| . " TEM_MAINTAIN_PROFILE_UI | ||
ABAP code using 7.40 inline data declarations to call FM TEM_MAINTAIN_PROFILE_UI
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_im_flg_init) | = ' '. | |||
| DATA(ld_im_flg_save) | = ' '. | |||
| DATA(ld_im_flg_exit) | = ' '. | |||
Search for further information about these or an SAP related objects