FIN_FSSC_OPTARCHI_PAYAVIS_2050 SAP Function module - Example for archiving payment avis

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

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

Pattern for FM FIN_FSSC_OPTARCHI_PAYAVIS_2050 - FIN FSSC OPTARCHI PAYAVIS 2050

CALL FUNCTION 'FIN_FSSC_OPTARCHI_PAYAVIS_2050' "Example for archiving payment avis
  EXPORTING
    i_reguh =                   " reguh         Settlement data from payment program
    i_gjahr =                   " regud-gjahr   Fiscal Year
    i_nacha =                   " finaa-nacha   Transmission Medium for Correspondence
    i_aforn =                   " t042b-aforn   Name of the Form for the Payment Advice
  CHANGING
    c_itcpo =                   " itcpo         SAPscript output interface
*   c_archive_index =           " toa_dara      SAP ArchiveLink structure of a DARA line
*   c_archive_params =          " arc_params    ImageLink structure
    .  "  FIN_FSSC_OPTARCHI_PAYAVIS_2050

ABAP code example for Function Module FIN_FSSC_OPTARCHI_PAYAVIS_2050

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

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

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

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


DATA(ld_i_gjahr) = Check type of data required


DATA(ld_i_nacha) = some text here
 

SELECT single AFORN 
  FROM T042B 
  INTO @DATA(ld_i_aforn).

.

CALL FUNCTION 'FIN_FSSC_OPTARCHI_PAYAVIS_2050'
  EXPORTING
    i_reguh =                    ld_i_reguh
    i_gjahr =                    ld_i_gjahr
    i_nacha =                    ld_i_nacha
    i_aforn =                    ld_i_aforn
  CHANGING
    c_itcpo =                    ld_c_itcpo
*   c_archive_index =            ld_c_archive_index
*   c_archive_params =           ld_c_archive_params
    .  "  FIN_FSSC_OPTARCHI_PAYAVIS_2050

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_c_itcpo
 
 TYPE ITCPO ,
ld_i_reguh
 
 TYPE REGUH ,
ld_c_archive_index
 
 TYPE TOA_DARA ,
ld_i_gjahr
 
 TYPE REGUD-GJAHR ,
ld_c_archive_params
 
 TYPE ARC_PARAMS ,
ld_i_nacha
 
 TYPE FINAA-NACHA ,
ld_i_aforn
 
 TYPE T042B-AFORN .


ld_c_itcpo = 'Check type of data required'.
ld_i_reguh = 'Check type of data required'.
ld_c_archive_index = 'Check type of data required'.

ld_i_gjahr = Check type of data required
ld_c_archive_params = 'Check type of data required'.

ld_i_nacha = some text here

SELECT single AFORN 
  FROM T042B 
  INTO ld_i_aforn.