SUBBIS processing: Supplier Invoices
BEFVALBIS: Before validating a supplier invoice
Use this entry point to perform other processings following the validation of a supplier BP invoice.
The validation of a supplier BP invoice is called from a supplier BP invoice (GESBIS function) or the supplier validation (BPSVAL function).
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is no open log file except in supplier validation. The user has the possibility to request a log file.
Different call cases
The entry point is called after the accounting validation standard processing of a supplier BP invoice for additional updates and just before the Commit instruction used to confirm changes. When resuming the execution of the processing, the GPE variable is tested and used to confirm or reject all the performed updates, which will lead to the cancellation of the invoice validation.
Available variables and masks
The [M:BIC0,1,2,3] classes are available when in supplier BP invoice management.
Variable or mask | Definition |
Mask [M:BIC0,1,2,3] | Supplier BP invoices |
NUM variable | Supplier invoice number to validate |
Open tables
Table | Significant content | Table Title |
PINVOICE | Yes | Purchase invoice |
BPSINVLIG | No | Supplier BP invoice lines |
BPSINVLIGA | No | Supplier BP analytical lines |
BPSUPPMVT | No | Supplier transactions |
TABPIVTYP | No | Supplier invoice type table |
FACILITY | No | Sites |
COMPANY | No | Company |
BPARTNER | No | Business partner |
BPCUSTOMER | No | Customers |
BPSUPPLIER | No | Suppliers |
BPADDRESS | No | Addresses |
GACCOUNT | No | General ledger accounts |
GACCCODE | No | Accounting codes |
GDIAACC | No | Account structures |
CACNA | No | Analytical natures |
CADSP | No | Prior allocation keys |
CACCE | No | Analytical dimensions table |
CAAUZ | No | Restrictions table |
TABCUR | No | Currency table |
TABUNIT | No | Unit of measure table |
TABVAT | No | Tax code table |
GTYPACCENT | No | Entry type |
FISCALYEAR | No | Fiscal years |
PERIOD | No | Periods |
ACCES | No | Access by user |
GACCDUDATE | No | Open items |
ATABDIV | No | Miscellaneous tables |
GAUTACE | No | Automatic journals |
GAUTACEF | No | Automatic journal formulas |
TABCOUNTRY | No | Country table |
SET_LETOUTCNO: Check invoice status to leave function even if LETAUTCNO is 2
The entry point SET_LETOUTCNO can be used to avoid unmatching an invoice if the invoice is fully payed and matched.
Context and operating mode
Transaction
There is a transaction opened.
Log file
There is one log file opened.
Call cases
The entry point is called in Subprog LETAVOIR(AVOIR,FACTURE) of process SUBBIS. It is located right after the check of the LETAUTCNO parameter.
Available variables and masks
Variable or mask |
Definition |
Mask [M:BIS0] |
Supplier BP invoice |
Mask [M:BIS1] |
Supplier BP invoice |
Mask [M:BIS3] |
Supplier BP invoice |
Value Char AVOIR |
F:PIH]NUM (Document no.) |
Value Char FACTURE |
[F:PIH]INVNUM (Invoice number) |
Local Char VALPAR(10) |
Value of parameter LETAUTCNO |
Example
When the entry point is called, the value of the LETAUTCNO parameter stored in variable VALPAR is 2. To prevent the process from running through the Subprog LETAVOIR and leaving the function, the variable VALPAR can set back to 1. If so, the function is not processed.
$ACTION
Case ACTION
When "SET_LETAUTCNO" : Gosub LETAUTCNO
When Default
Endcase
Return
$ LETAUTCNO
#check invoice. If Subprog LETAVOIR should be leaved set VALPAR to "1"
VALPAR = "1"
RETURN
Open tables
Table |
Significant content |
Table Title |
COMPANY |
Yes |
Company |
CACCE |
Yes |
|
GACM |
Yes |
Account core model |
GLED |
Yes |
Ledger codes |
GDIE |
Yes |
Fiscal years |
GACCOUNT |
Yes |
Accounts |
BPARTNER |
Yes |
Business partner |
SINVOICE |
Yes |
Customers |
BPCINVLIG |
Yes |
Suppliers |
FACTOR |
Yes |
Addresses |
PINVOICE |
Yes |
Bank ID statement |
BPSINVLIG |
Yes |
Country table |
GACCDUDATE |
Yes |
Accounting entry lines |
GTYPACCENT |
Yes |
Accounting enries |
GCOA |
Yes |
Chart of accounts |