READ_BROUGHT_FORWARD_TABLE SAP Function module - Read Brought Forward Using Original Period

READ_BROUGHT_FORWARD_TABLE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name READ_BROUGHT_FORWARD_TABLE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: HRGG
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM READ_BROUGHT_FORWARD_TABLE - READ BROUGHT FORWARD TABLE

CALL FUNCTION 'READ_BROUGHT_FORWARD_TABLE' "Read Brought Forward Using Original Period
  EXPORTING
    orig_rgdir =                " pc261         Cluster Directory (For Export and Import of Payroll Results)
    persnr =                    " pernr-pernr   Personnel number
  TABLES
    bf_table =                  " pc208         Payroll Results: Cumulated Results Table
  EXCEPTIONS
    RGDIR_ERROR = 1             "               Error raised by RGDIR_READ
    RESULTS_ERROR = 2           "               Error raised by Payroll Results Read
    .  "  READ_BROUGHT_FORWARD_TABLE

ABAP code example for Function Module READ_BROUGHT_FORWARD_TABLE

The ABAP code below is a full code listing to execute function module READ_BROUGHT_FORWARD_TABLE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_bf_table  
 
 TYPE STANDARD TABLE OF PC208,"TABLES PARAM
wa_bf_table
 
 LIKE LINE OF it_bf_table
.


DATA(ld_orig_rgdir) = 'Check type of data required'.


DATA(ld_persnr) = Check type of data required
 

"populate fields of struture and append to itab
append wa_bf_table to it_bf_table.
.

CALL FUNCTION 'READ_BROUGHT_FORWARD_TABLE'
  EXPORTING
    orig_rgdir =                 ld_orig_rgdir
    persnr =                     ld_persnr
  TABLES
    bf_table =                   it_bf_table
  EXCEPTIONS
    RGDIR_ERROR =                1
    RESULTS_ERROR =              2
    .  "  READ_BROUGHT_FORWARD_TABLE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_orig_rgdir
 
 TYPE PC261 ,
it_bf_table
 
 TYPE STANDARD TABLE OF PC208 ,
wa_bf_table
 
 LIKE LINE OF it_bf_table,
ld_persnr
 
 TYPE PERNR-PERNR .


ld_orig_rgdir = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_bf_table to it_bf_table.

ld_persnr = Check type of data required