SAP FI_PSO_READ_DOCUMENT Function Module for









FI_PSO_READ_DOCUMENT is a standard fi pso read document 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 read document FM, simply by entering the name FI_PSO_READ_DOCUMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function FI_PSO_READ_DOCUMENT 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_READ_DOCUMENT'"
EXPORTING
I_COMPY = "
I_ACTIVITY = "

IMPORTING
ET_PSO = "
ET_ITEM = "
ET_PSSEC = "

CHANGING
C_LOTKZ = "
C_PSOTYP = "
C_RECURRING = "
C_BELNR = "
C_GJAHR = "

EXCEPTIONS
NO_KEY_SPECIFIED = 1 EXIT_ALL = 2 ERROR_MESSAGE = 3
.




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_READ_DOCUMENT

I_COMPY -

Data type: BKPF-BUKRS
Optional: No
Call by Reference: Yes

I_ACTIVITY -

Data type: TACT-ACTVT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FI_PSO_READ_DOCUMENT

ET_PSO -

Data type: FM_PSO02
Optional: No
Call by Reference: Yes

ET_ITEM -

Data type: FM_PSO02S
Optional: No
Call by Reference: Yes

ET_PSSEC -

Data type: FIPSO_BSEC_TAB
Optional: No
Call by Reference: Yes

CHANGING Parameters details for FI_PSO_READ_DOCUMENT

C_LOTKZ -

Data type: VBKPF-LOTKZ
Optional: No
Call by Reference: Yes

C_PSOTYP -

Data type: PSOTY-PSOTYP
Optional: No
Call by Reference: Yes

C_RECURRING -

Data type: BOOLE-BOOLE
Optional: No
Call by Reference: Yes

C_BELNR -

Data type: VBKPF-BELNR
Optional: No
Call by Reference: Yes

C_GJAHR -

Data type: VBKPF-GJAHR
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_KEY_SPECIFIED -

Data type:
Optional: No
Call by Reference: Yes

EXIT_ALL -

Data type:
Optional: No
Call by Reference: Yes

ERROR_MESSAGE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FI_PSO_READ_DOCUMENT 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_et_pso  TYPE FM_PSO02, "   
lv_c_lotkz  TYPE VBKPF-LOTKZ, "   
lv_i_compy  TYPE BKPF-BUKRS, "   
lv_no_key_specified  TYPE BKPF, "   
lv_et_item  TYPE FM_PSO02S, "   
lv_c_psotyp  TYPE PSOTY-PSOTYP, "   
lv_exit_all  TYPE PSOTY, "   
lv_i_activity  TYPE TACT-ACTVT, "   
lv_et_pssec  TYPE FIPSO_BSEC_TAB, "   
lv_c_recurring  TYPE BOOLE-BOOLE, "   
lv_error_message  TYPE BOOLE, "   
lv_c_belnr  TYPE VBKPF-BELNR, "   
lv_c_gjahr  TYPE VBKPF-GJAHR. "   

  CALL FUNCTION 'FI_PSO_READ_DOCUMENT'  "
    EXPORTING
         I_COMPY = lv_i_compy
         I_ACTIVITY = lv_i_activity
    IMPORTING
         ET_PSO = lv_et_pso
         ET_ITEM = lv_et_item
         ET_PSSEC = lv_et_pssec
    CHANGING
         C_LOTKZ = lv_c_lotkz
         C_PSOTYP = lv_c_psotyp
         C_RECURRING = lv_c_recurring
         C_BELNR = lv_c_belnr
         C_GJAHR = lv_c_gjahr
    EXCEPTIONS
        NO_KEY_SPECIFIED = 1
        EXIT_ALL = 2
        ERROR_MESSAGE = 3
. " FI_PSO_READ_DOCUMENT




ABAP code using 7.40 inline data declarations to call FM FI_PSO_READ_DOCUMENT

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 VBKPF INTO @DATA(ld_c_lotkz).
 
"SELECT single BUKRS FROM BKPF INTO @DATA(ld_i_compy).
 
 
 
"SELECT single PSOTYP FROM PSOTY INTO @DATA(ld_c_psotyp).
 
 
"SELECT single ACTVT FROM TACT INTO @DATA(ld_i_activity).
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_c_recurring).
 
 
"SELECT single BELNR FROM VBKPF INTO @DATA(ld_c_belnr).
 
"SELECT single GJAHR FROM VBKPF INTO @DATA(ld_c_gjahr).
 


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!