SAP UPF_EXIT_INIT_EXAMPLE_01 Function Module for Exit function is called with a specific record determined in the Exit Init
UPF_EXIT_INIT_EXAMPLE_01 is a standard upf exit init example 01 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Exit function is called with a specific record determined in the Exit Init 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 upf exit init example 01 FM, simply by entering the name UPF_EXIT_INIT_EXAMPLE_01 into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPFX
Program Name: SAPLUPFX
Main Program: SAPLUPFX
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPF_EXIT_INIT_EXAMPLE_01 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 'UPF_EXIT_INIT_EXAMPLE_01'"Exit function is called with a specific record determined in the Exit Init.
EXPORTING
I_AREA = "Planning Area
I_PLEVEL = "Planning Level
I_PACKAGE = "Planning Package
I_METHOD = "Planning Function
I_PARAM = "Parameter group
IT_EXITP = "Planning Functions: Exit Function Parameters
ITO_CHASEL = "Characteristic Selection
ITO_CHA = "Characteristics
ITO_KYF = "Key Figures
IMPORTING
ETO_CHAS = "
ET_MESG = "Messages
IMPORTING Parameters details for UPF_EXIT_INIT_EXAMPLE_01
I_AREA - Planning Area
Data type: UPC_Y_AREAOptional: No
Call by Reference: Yes
I_PLEVEL - Planning Level
Data type: UPC_Y_PLEVELOptional: No
Call by Reference: Yes
I_PACKAGE - Planning Package
Data type: UPC_Y_PACKAGEOptional: No
Call by Reference: Yes
I_METHOD - Planning Function
Data type: UPC_Y_METHODOptional: No
Call by Reference: Yes
I_PARAM - Parameter group
Data type: UPC_Y_PARAMOptional: No
Call by Reference: Yes
IT_EXITP - Planning Functions: Exit Function Parameters
Data type: UPF_YT_EXITPOptional: No
Call by Reference: Yes
ITO_CHASEL - Characteristic Selection
Data type: UPC_YTO_CHASELOptional: No
Call by Reference: Yes
ITO_CHA - Characteristics
Data type: UPC_YTO_CHAOptional: No
Call by Reference: Yes
ITO_KYF - Key Figures
Data type: UPC_YTO_KYFOptional: No
Call by Reference: Yes
EXPORTING Parameters details for UPF_EXIT_INIT_EXAMPLE_01
ETO_CHAS -
Data type: ANY TABLEOptional: No
Call by Reference: Yes
ET_MESG - Messages
Data type: UPC_YT_MESGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPF_EXIT_INIT_EXAMPLE_01 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_area | TYPE UPC_Y_AREA, " | |||
| lv_eto_chas | TYPE ANY TABLE, " | |||
| lv_et_mesg | TYPE UPC_YT_MESG, " | |||
| lv_i_plevel | TYPE UPC_Y_PLEVEL, " | |||
| lv_i_package | TYPE UPC_Y_PACKAGE, " | |||
| lv_i_method | TYPE UPC_Y_METHOD, " | |||
| lv_i_param | TYPE UPC_Y_PARAM, " | |||
| lv_it_exitp | TYPE UPF_YT_EXITP, " | |||
| lv_ito_chasel | TYPE UPC_YTO_CHASEL, " | |||
| lv_ito_cha | TYPE UPC_YTO_CHA, " | |||
| lv_ito_kyf | TYPE UPC_YTO_KYF. " |
|   CALL FUNCTION 'UPF_EXIT_INIT_EXAMPLE_01' "Exit function is called with a specific record determined in the Exit Init |
| EXPORTING | ||
| I_AREA | = lv_i_area | |
| I_PLEVEL | = lv_i_plevel | |
| I_PACKAGE | = lv_i_package | |
| I_METHOD | = lv_i_method | |
| I_PARAM | = lv_i_param | |
| IT_EXITP | = lv_it_exitp | |
| ITO_CHASEL | = lv_ito_chasel | |
| ITO_CHA | = lv_ito_cha | |
| ITO_KYF | = lv_ito_kyf | |
| IMPORTING | ||
| ETO_CHAS | = lv_eto_chas | |
| ET_MESG | = lv_et_mesg | |
| . " UPF_EXIT_INIT_EXAMPLE_01 | ||
ABAP code using 7.40 inline data declarations to call FM UPF_EXIT_INIT_EXAMPLE_01
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