Process TRTVENFACP: Enter Sales Invoice Payment
ALIPYH: Load the [F] PAYMENTH class on the creation of a payment of an invoice
This entry point is used to insert additional logic in the loading of the fields in the "Payment header" record.
It makes it possible to load specific/custom fields in the PAYMENTH table.
It is called in the process to create the payment for a sales invoice.
Context and operating method
Transaction
There is one transaction in progress.
Log file
There is no open log file.
Call context
This entry point is called after the payment window entry, after having validated it using the OK button.
It is located at the start of the payment creation transaction, in order to load the PAYMENTH file.
Available variables and masks
The payment entry mask [M :IVPY] is on-line with all the entered information. The payment header files [F :PYH] is on-line and is loaded with [M :IVPY].
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...). Traditionally, this is the case for the file that contains the header and not the file that contains the lines...
Table |
Significant content |
Table Title |
GACCDUDATE |
Yes |
Open items |
TABPAYTYP |
Yes |
Payment transactions |
TABPAYTERM |
Yes |
Payment conditions table |
BPCUSTOMER |
Yes |
Customers |
PAYMENTH |
Yes |
Payment header |
PAYMENTD |
No |
Payment lines |
PAYMENTA |
No |
Payment analytical lines |
TABCUR |
No |
Currency table |
FACILITY |
No |
Site |
GACCOUNT |
Yes |
General ledger accounts |
BANK |
No |
Bank account |
COMPANY |
Yes |
Company |
GACCDENCOD |
No |
Accounting destination |
GACCCODE |
Yes |
Accounting codes |
ACCESS |
No |
Access code |
CREREGSIH: To intervene after the creation of a payment for an invoice
This entry point is used to intervene after the creation of a payment for an invoice.
It is called in the process to create the payment for a sales invoice.
Context and operating method
Transaction
There is one transaction in progress.
Log file
There is no open log file.
Call context
This entry point is called after the payment window entry, after having validated it using the OK button.
It is located at the end of the payment creation transaction, just before the transaction is carried out.
Available variables and masks
The payment entry mask [M :IVPY] is on-line with all the entered information.
The payment line file record [F :PYD] has been created. Another record [F :PYD] will also have been created in the case where there is a discount/charge. It is the last record created that is on-line.
The payment header file record [F :PYH] has been created. It is on-line.
The due date item file record [F :DUD] corresponding to the due date item line that is the object of the payment is on-line and has been updated (provisional update of payment amount).
If the cash account field or the bank field is assigned in the entry screen, the bank account file record [F :BAN] is on-line and has been updated (provisional update of payment amount).
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded...). Traditionally, this is the case for the file that contains the header and not the file that contains the lines...
Table |
Significant content |
Table Title |
GACCDUDATE |
Yes |
Open items |
TABPAYTYP |
Yes |
Payment transactions |
TABPAYTERM |
Yes |
Payment conditions table |
BPCUSTOMER |
Yes |
Customers |
PAYMENTH |
Yes |
Payment header |
PAYMENTD |
Yes |
Payment lines |
PAYMENTA |
No |
Payment analytical lines |
TABCUR |
Yes |
Currency table |
FACILITY |
No |
Site |
GACCOUNT |
Yes |
General ledger accounts |
BANK |
Yes |
Bank account |
COMPANY |
Yes |
Company |
GACCDENCOD |
Yes |
Accounting destination |
GACCCODE |
Yes |
Accounting codes |
ACCESS |
No |
Access code |
TABCOUAFF |
Yes |
Sequence number counters |