Process BSILIBPAY: BSI payment generation
BSIPAYCRE: Modifying the created payments of a transaction
Use this entry point to add data to the payments created for the BSI transaction.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is an open log file.
Call context
This entry point is called directly after the silent import of the payment.
Available variables and masks
The following tables are available:
- BSIIMP [BSIIMP]: Bank statement import
- BSIIMPD [BSIIMPD]: Bank statement import detail
Miscellaneous remarks
The payments created by the silent import can be filtered:
If !clalev([ZPYH]): Local File PAYMENTH [ZPYH]: Endif
Filter [F:ZPYH] Where [F:ZPYH]BSITRS = [F:BSIIMPD]STMCOD + "/" + num$([F:BSIIMPD]LIN)
BSIPAYCREFILSUP: Adding selection criteria during statement payment generation
Context and operating method
Transaction
There is no transaction in progress.
Log file
There is an open log file.
Code context
This entry point is called when payments are generated for a whole statement.
It is called immediately after the reconciliation header and footer for a statement are created, and before entering the loop that selects BSIIMPD records during the payment creation process.
You can use this entry point to populate the local variable FILSUP with additional criteria for selection.
Available variables and masks
- PSTMCOD: Primary key used to read a record in the BSIIMP table
- PSTA: Status returned by BSI_PAYMENT_CREATION (0 = OK, other values are defined in the BSI_PAYMENT_CREATION processing)
- PMSG: Message corresponding to the status
- FILSUP: Additional condition to be set via the entry point
Open tables
| Table | Significant content | Table title |
| BSIIMP | No | Bank statement import |