SUBFRM processing: Remittances

PYH: Payment entry

Use this entry point to load specific fields or to modify the value of certain fields when recording a remittance.

Context and operating mode

Transaction

There is one transaction in progress.

Log file

There is an open log file.

Different call cases

The entry point is called when creating and modifying the remittance, at each re-entry of the PYH table.

Available variables and masks

The PAYMENTH table is online, this is the only one with significant content.

The FRM0 [FRM0] and FRM1 [FRM1] remittance entry screens are online.

BOUTON: Bank file button management

Use this entry point to intervene on the specific buttons at the bottom of the screen and particulary, the Bank file generation button.

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

The entry point is called at each button or menu event generated by the user (First, Next, Create, Save, Load a new remittance record, and so on), through the SETBOUT action.

Available variables and masks

In this entry point, the [L]GENFIC variable, of Integer type, is used to manage the Bank file button. If it is set to 0, the button will be deactivated. Otherwise, it is activated. By default, the GENFIC variable is set to 1.

The TABPAYTYP table is online, it is the only one with significant content.

The FRM0 [FRM0] and FRM1 [FRM1] remittance entry screens are online.

FICBAN: Personalization of the directory for the bank file generation

Use this entry point to personalize the Bank file generation directory (GDIRBQE variable).

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

The entry point is called when generating the Bank file.

Available variables and masks

The GDIRBQE variable can be modified.

Note - warningIt contains the relative path, in other words a sub-directory of the folder (for example: GDIRBQE contains BQE for a file generated under /adonix/v120/DEMO/BQE).

This variable is saved before the entry point is called. It is restored when generating the file.

The TABPAYTYP table is online, its content is significant.

The FRM0 [FRM0] and FRM1 [FRM1] remittance entry screens are online.

BUTTONCTL: Manual remittance button management

Use this entry point to ensure the proper button and menu item management from specific and vertical layers in the Manual remittances function. This applies specifically to the Payment and Approve buttons.

Context and operating mode

Conditions for button and menu item management placed in this entry point should align with the ones in the SPE and SPV scripts of the SETBOUT action.

After this is called from a subprogram context, buttons and menu items are not recognized with their letter code, such as V for the Post button, but with their numerical values, such as 1801 for the Post button. You need to manage these directly with the Enable/Disable command. There are 4 global variables already assigned to buttons and menu items that can be used:

  • [V]POST_BUTTON

  • [V]BANK_FILE_BUTTON

  • [V]APPROVE_ALL_BUTTON

  • [V]REMOVE_UNAPPROVED_BUTTON

All the others must be managed by their number code or assigned variables and must be declared in the script called by the entry point.

For example, if you want to disable the Post button, do not use the standard command:

Call VIREBOUT(CHAINE,"V") From GOBJET

Use this command:

Disable [V]POST_BUTTON

BEFUPDPYHDEL: When deleting payment before rewriting the PYH table

Context and operating mode

Transaction

There is no transaction in progress.

Log file

There is no open log file.

Different call cases

When deleting a payment from the remittance, use this entry point to modify the value of certain fields before recording the PYH table.

Available variables and masks

The FRM0 [FRM0] and FRM1 [FRM1] remittance entry screens are online.

Open tables

Table Significant content Table title
PAYMENTH Yes Payment header
PAYACCNUM No Accounting payment entry
TABPAYTYP Yes Payment transactions