SAP FM_ARC_IA_GET_NEXT_RECORD Function Module for

Search SAP Function Modules

FM_ARC_IA_GET_NEXT_RECORD is a standard fm arc ia get next record 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 fm arc ia get next record FM, simply by entering the name FM_ARC_IA_GET_NEXT_RECORD into the relevant SAP transaction such as SE37 or SE38.

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

Function FM_ARC_IA_GET_NEXT_RECORD 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 'FM_ARC_IA_GET_NEXT_RECORD'"
  EXPORTING
   I_AR_HANDLE =  "

 IMPORTING
   E_EOR =  "

TABLES
   T_FMIA =  "
*  T_REFBN =  "
*  T_VRGNG =  "
*  T_ARCH_STAT =  "
*  T_FM01_ARCH =  "
*  T_FIKRS =  "
*  T_FONDS =  "
*  T_FISTL =  "
*  T_FIPEX =  "
*  T_GJAHR =  "
*  T_PERIO =  "

.

IMPORTING Parameters details for FM_ARC_IA_GET_NEXT_RECORD

I_AR_HANDLE -

Data type: SY-TABIX
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FM_ARC_IA_GET_NEXT_RECORD

E_EOR -

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

TABLES Parameters details for FM_ARC_IA_GET_NEXT_RECORD

T_FMIA -

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

T_REFBN -

Data type: RANGE_C10
Optional: Yes
Call by Reference: Yes

T_VRGNG -

Data type: RANGE_C4
Optional: Yes
Call by Reference: Yes

T_ARCH_STAT -

Data type: ARCH_STAT
Optional: Yes
Call by Reference: Yes

T_FM01_ARCH -

Data type: FM01_ARCH
Optional: Yes
Call by Reference: Yes

T_FIKRS -

Data type: RANGE_C4
Optional: Yes
Call by Reference: Yes

T_FONDS -

Data type: RANGE_C10
Optional: Yes
Call by Reference: Yes

T_FISTL -

Data type: RANGE_C16
Optional: Yes
Call by Reference: Yes

T_FIPEX -

Data type: RANGE_C24
Optional: Yes
Call by Reference: Yes

T_GJAHR -

Data type: RANGE_N4
Optional: Yes
Call by Reference: Yes

T_PERIO -

Data type: RANGE_N3
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for FM_ARC_IA_GET_NEXT_RECORD 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.

ABAP code using 7.40 inline data declarations to call FM FM_ARC_IA_GET_NEXT_RECORD

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