SAP FIPOS_READ_FROM_ACCOUNT Function Module for









FIPOS_READ_FROM_ACCOUNT is a standard fipos read from account 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 fipos read from account FM, simply by entering the name FIPOS_READ_FROM_ACCOUNT into the relevant SAP transaction such as SE37 or SE38.

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



Function FIPOS_READ_FROM_ACCOUNT 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 'FIPOS_READ_FROM_ACCOUNT'"
EXPORTING
* I_GJAHR = '0000' "

TABLES
* T_BUKRS = "
* T_FIPOS = "
* T_FIVOR = "
* T_POTYP = "
* T_KATEG = "
T_ENTRY_TAB = "
* T_SAKNR = "
* T_BEGRU = "
* T_BUSAB = "
* T_FSTAG = "
* T_RECID = "
* T_STEXT = "
* T_FIKRS = "
* T_FIPEX = "
.



IMPORTING Parameters details for FIPOS_READ_FROM_ACCOUNT

I_GJAHR -

Data type: FMPG-GJAHR
Default: '0000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FIPOS_READ_FROM_ACCOUNT

T_BUKRS -

Data type: RANGE_C4
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_FIPOS -

Data type: RANGE_C14
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_FIVOR -

Data type: RSN2RANGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_POTYP -

Data type: RANGE_C1
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_KATEG -

Data type: RANGE_C1
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_ENTRY_TAB -

Data type: IFMSAKFIPO
Optional: No
Call by Reference: No ( called with pass by value option)

T_SAKNR -

Data type: RANGE_C10
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_BEGRU -

Data type: RANGE_C4
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_BUSAB -

Data type: RANGE_C2
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_FSTAG -

Data type: RANGE_C4
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_RECID -

Data type: RANGE_C2
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_STEXT -

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_FIKRS -

Data type: RANGE_C4
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_FIPEX -

Data type: RANGE_C24
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FIPOS_READ_FROM_ACCOUNT 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_gjahr  TYPE FMPG-GJAHR, "   '0000'
lt_t_bukrs  TYPE STANDARD TABLE OF RANGE_C4, "   
lt_t_fipos  TYPE STANDARD TABLE OF RANGE_C14, "   
lt_t_fivor  TYPE STANDARD TABLE OF RSN2RANGE, "   
lt_t_potyp  TYPE STANDARD TABLE OF RANGE_C1, "   
lt_t_kateg  TYPE STANDARD TABLE OF RANGE_C1, "   
lt_t_entry_tab  TYPE STANDARD TABLE OF IFMSAKFIPO, "   
lt_t_saknr  TYPE STANDARD TABLE OF RANGE_C10, "   
lt_t_begru  TYPE STANDARD TABLE OF RANGE_C4, "   
lt_t_busab  TYPE STANDARD TABLE OF RANGE_C2, "   
lt_t_fstag  TYPE STANDARD TABLE OF RANGE_C4, "   
lt_t_recid  TYPE STANDARD TABLE OF RANGE_C2, "   
lt_t_stext  TYPE STANDARD TABLE OF RANGE_C2, "   
lt_t_fikrs  TYPE STANDARD TABLE OF RANGE_C4, "   
lt_t_fipex  TYPE STANDARD TABLE OF RANGE_C24. "   

  CALL FUNCTION 'FIPOS_READ_FROM_ACCOUNT'  "
    EXPORTING
         I_GJAHR = lv_i_gjahr
    TABLES
         T_BUKRS = lt_t_bukrs
         T_FIPOS = lt_t_fipos
         T_FIVOR = lt_t_fivor
         T_POTYP = lt_t_potyp
         T_KATEG = lt_t_kateg
         T_ENTRY_TAB = lt_t_entry_tab
         T_SAKNR = lt_t_saknr
         T_BEGRU = lt_t_begru
         T_BUSAB = lt_t_busab
         T_FSTAG = lt_t_fstag
         T_RECID = lt_t_recid
         T_STEXT = lt_t_stext
         T_FIKRS = lt_t_fikrs
         T_FIPEX = lt_t_fipex
. " FIPOS_READ_FROM_ACCOUNT




ABAP code using 7.40 inline data declarations to call FM FIPOS_READ_FROM_ACCOUNT

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 GJAHR FROM FMPG INTO @DATA(ld_i_gjahr).
DATA(ld_i_gjahr) = '0000'.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!