Páginas filhas
  • Technical Details (FINA310 - SIGAFIN)

The electronic payment in the Financials module is carried out by the integration with the e-banking indicated by Argentinean banks. To do so, in the Banks register, two fields are being made available containing the user function responsible for running the processes of saving and reading the text files. They are:

File Function (A6_FORMARQ) = It indicates the specific user function which generates the file sent to the bank.

Return Function (A6_FORMRET) = It indicates the specific user function which reads the data in the file returned by the bank and feeds the bank return history (FJD)

These functions are called via menu options made available in the Bank Files Management routine and are followed by a series of questions to help filtering data. Parameterization performed in these sets of questions are carried over as parameters when they are run.

Besides carrying over parameters, the default routine requires a structure of the vector type as return, containing the result of the processing, so as to correctly update the records involved.

Thus, consider using:


To generate the (A6_FORMARQ) file


Parameters

Bank (character type)

Branch (character type)

Account (character type)

Date from (date type)

Date to (date type)

Return

Vector containing processed Lots, as follows:

  • Position 1 = Lot number
  • Position 2 = Name of the generated file


The bank, branch and account refer to the bank entity registered in the Banks table (SA6) These data are included in the Financial Lots Header (FJB), in their Lot Details (FJC) and, consequently, in the respective bound Payment Orders (SEK). Thus, these tables contain the base information for generating the files for sending to the banks.

To generate the (A6_FORMRET) file


Parameters

Bank (character type)

Branch (character type)

Account (character type)

Return file name (character type)

Return

Vector containing the processed lots, each position containing the Lot Number returned.


Data processed by the user function must feed the Bank Return History table (FJD) so that it may later be used in the Lot Confirmation. To do so, the following status update rule is to be considered:

  • Lot header status (FJB_STATUS) is automatically updated by the default routine
  • History status (FJD_STATUS) must follow the pattern below:

1

Bank Return

When there is no error in the record return, this status is to be saved.

2

System update

Reserved for default routine – Lot Confirmation

3

Error indicated by the bank

When there is an error of the bank, this status must be used and the complement of the error description saved to FJC_ERRO

4

System update error

Reserved for default routine – Lot Confirmation