This entry point is used to take control just before the matching of the prepayment allocation entries.
There is one transaction in progress.
There is an open log file.
This entry point is called just before the declaration of the variable tables in which the entries to be matched together will be loaded.
The NBLET variable contains the number of open items linked to the invoice subject to a prepayment allocation. It is used for the sizing of the variable table that will be loaded with the data corresponding to the different open items that will be matched with the generated prepayment allocation entry.
Table | Significant content | Table Title |
GACCTMPD [DAT4] |
| Accounting documents lines |
GACCDUDATE [DUD] |
| Due dates |
GACCDUDATE [DUD2] |
| Due dates |
This entry point is used to take over in order to reroute the standard matching procedure of prepayment allocation entries with the invoice, when the prepayment allocation is performed via the customer or supplier prepayment allocation function.
There is one transaction in progress.
There is an open log file.
This entry point is called just before the call to the standard subprogram used for matching the prepayment allocation entries with the invoice. If the GPE variable is set to 1, the standard matching processing is not performed.
The NBLET variable contains the number of open items linked to the invoice subject to a prepayment allocation.
The LETNUM , LETLIG and LETIPT variable tables respectively contain the numbers of the entries (ACCNUM), the numbers of the open items and the allocated amounts used for matching the generated prepayment allocation entry with the allocated invoice.
Table | Significant content | Table Title |
GACCTMPD [DAT4] |
| Accounting documents lines |
GACCDUDATE [DUD] |
| Due dates |
GACCDUDATE [DUD2] |
| Due dates |