FEB_IMP_AUTOMATIC_PROCESSING SAP Function module

FEB_IMP_AUTOMATIC_PROCESSING 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 FEB_IMP_AUTOMATIC_PROCESSING into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM FEB_IMP_AUTOMATIC_PROCESSING - FEB IMP AUTOMATIC PROCESSING

CALL FUNCTION 'FEB_IMP_AUTOMATIC_PROCESSING' "
  EXPORTING
    it_range_kukey =            " feby_range_kukey
    iv_vgext_ok =               " char1
    it_mansp =                  " feby_mansp
    it_nott028g =               " feby_nott028g
    is_statement_key =          " febs_statement_key
    .  "  FEB_IMP_AUTOMATIC_PROCESSING

ABAP code example for Function Module FEB_IMP_AUTOMATIC_PROCESSING

The ABAP code below is a full code listing to execute function module FEB_IMP_AUTOMATIC_PROCESSING 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(ld_it_range_kukey) = 'Check type of data required'.

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

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

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

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

CALL FUNCTION 'FEB_IMP_AUTOMATIC_PROCESSING'
  EXPORTING
    it_range_kukey =             ld_it_range_kukey
    iv_vgext_ok =                ld_iv_vgext_ok
    it_mansp =                   ld_it_mansp
    it_nott028g =                ld_it_nott028g
    is_statement_key =           ld_is_statement_key
    .  "  FEB_IMP_AUTOMATIC_PROCESSING

IF SY-SUBRC EQ 0.
  "All OK
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_it_range_kukey
 
 TYPE FEBY_RANGE_KUKEY ,
ld_iv_vgext_ok
 
 TYPE CHAR1 ,
ld_it_mansp
 
 TYPE FEBY_MANSP ,
ld_it_nott028g
 
 TYPE FEBY_NOTT028G ,
ld_is_statement_key
 
 TYPE FEBS_STATEMENT_KEY .


ld_it_range_kukey = 'Check type of data required'.
ld_iv_vgext_ok = 'Check type of data required'.
ld_it_mansp = 'Check type of data required'.
ld_it_nott028g = 'Check type of data required'.
ld_is_statement_key = 'Check type of data required'.