Interacts with Bankgirot and generates and parses related files.
Processes files without connecting to Bankgirot.
For bankgiro and plusgiro columns, the component will strip the characters '.', '-', and ' '. All other non-numeric characters will result in an error. The resulting number must contain 10 digits or less.
Bank account numbers should start with the clearing number (four digits) followed by the account number. For clearing numbers with five digits (Swedbank), do not include the fifth digit.
SQL with details of supplier payments. Is only used with LBUT.
SQL with details of customer payments. Is only used with BGI.
SQL to save confirmations of automatic transaction admission registration or withdrawal.
Possible value | Description |
---|---|
BANK | |
PAYER | |
RECEIVER | |
SENDER |
SQL to save electronic annoucements of admissions for automatic transactions.
SQL to save reports of success or failure of automatic transactions.
May also include refund information. This only applies to New Autogiro files.
SQL to save reports of success or failure for withdrawal of automatic transaction assignments.
Fakturautställaren kan definiera egna fält för anmälningsärenden. Temptabellen #Fields(Name char(3), Value varchar(max)) innehåller de fält som fyllts i av fakturamottagaren.
Possible value | Description |
---|---|
0 | Production. |
1 | Registrations were sent for testing. |
SQL to report when file has been parsed with correct action.
Starting with version 7.8.001: Both this call and the "Finished" call use the @Finished parameter, but only this call will include @BankFileId.
This call is made after all other calls have been made.
Both this call and the "File successfully parsed" call use the @Finished parameter, but only "File successfully parsed" will include @BankFileId.
Allows you to validate the parameters supplied by the user before any other SQL is run in the component. This call is only made if the component has visible parameters, the SQL is a stored procedure, and 'Validate parameters' is checked.
Use this call to restrict which entries a user is allowed to view and edit, and to log which entries a user views.
Access to a menu item is normally controlled through functions and roles alone but some entities need more fine grained control. For example, a user may have access to the View Member menu item for normal members but not for members with a protected identity.
The menu items a user visits are always logged (in ADMINLogMenuItem) but for sensitive data you may need to log exactly what entries are viewed. Do the logging in this call as the common ways of viewing data (grid and InfoSQL) are not allowed to modify the database.
If you bind a scalar function instead of a stored procedure to this call then its name must end with '_GrantAccess'.