SAP FI_PSO_DISPLAY Function Module for
FI_PSO_DISPLAY is a standard fi pso display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fi pso display FM, simply by entering the name FI_PSO_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: F0KA
Program Name: SAPLF0KA
Main Program: SAPLF0KA
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FI_PSO_DISPLAY 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 'FI_PSO_DISPLAY'".
EXPORTING
* I_LOTKZ = ' ' "Lot number
* I_COMPY = ' ' "Company Code
* I_PSOTYP = ' ' "Request Category
* I_RECURRING = ' ' "
* I_F_FIKEY = ' ' "
* I_CHAN_HIDE = 'X' "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
EXCEPTIONS
UNKNOWN_TYPE = 1 CANCELLED = 2 EXIT_ALL = 3 DATA_MISSING = 4
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLF0KA_001 IS-PS: Formatting of Customer-Specific Document Header Data
EXIT_SAPLF0KA_002 IS-PS: Additional Checks when Bundling Posted FI Documents
IMPORTING Parameters details for FI_PSO_DISPLAY
I_LOTKZ - Lot number
Data type: BKPF-LOTKZDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_COMPY - Company Code
Data type: BKPF-BUKRSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PSOTYP - Request Category
Data type: PSOTY-PSOTYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RECURRING -
Data type: BOOLE-BOOLEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_F_FIKEY -
Data type: FIPSO_FIKEYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CHAN_HIDE - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UNKNOWN_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANCELLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXIT_ALL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATA_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FI_PSO_DISPLAY 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_lotkz | TYPE BKPF-LOTKZ, " SPACE | |||
| lv_unknown_type | TYPE BKPF, " | |||
| lv_i_compy | TYPE BKPF-BUKRS, " SPACE | |||
| lv_cancelled | TYPE BKPF, " | |||
| lv_exit_all | TYPE BKPF, " | |||
| lv_i_psotyp | TYPE PSOTY-PSOTYP, " SPACE | |||
| lv_i_recurring | TYPE BOOLE-BOOLE, " SPACE | |||
| lv_data_missing | TYPE BOOLE, " | |||
| lv_i_f_fikey | TYPE FIPSO_FIKEY, " SPACE | |||
| lv_i_chan_hide | TYPE BOOLE-BOOLE. " 'X' |
|   CALL FUNCTION 'FI_PSO_DISPLAY' " |
| EXPORTING | ||
| I_LOTKZ | = lv_i_lotkz | |
| I_COMPY | = lv_i_compy | |
| I_PSOTYP | = lv_i_psotyp | |
| I_RECURRING | = lv_i_recurring | |
| I_F_FIKEY | = lv_i_f_fikey | |
| I_CHAN_HIDE | = lv_i_chan_hide | |
| EXCEPTIONS | ||
| UNKNOWN_TYPE = 1 | ||
| CANCELLED = 2 | ||
| EXIT_ALL = 3 | ||
| DATA_MISSING = 4 | ||
| . " FI_PSO_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM FI_PSO_DISPLAY
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 LOTKZ FROM BKPF INTO @DATA(ld_i_lotkz). | ||||
| DATA(ld_i_lotkz) | = ' '. | |||
| "SELECT single BUKRS FROM BKPF INTO @DATA(ld_i_compy). | ||||
| DATA(ld_i_compy) | = ' '. | |||
| "SELECT single PSOTYP FROM PSOTY INTO @DATA(ld_i_psotyp). | ||||
| DATA(ld_i_psotyp) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_recurring). | ||||
| DATA(ld_i_recurring) | = ' '. | |||
| DATA(ld_i_f_fikey) | = ' '. | |||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_chan_hide). | ||||
| DATA(ld_i_chan_hide) | = 'X'. | |||
Search for further information about these or an SAP related objects