CFMINVMAJ: Update of the specific/custom files after the validation of an invoic

Use this entry point to take control before the end of an invoice validation transaction in order to update specific/custom files.

It is called during the TRTVENFACV validation processing for invoices.

Context and operating mode

Transaction

There is one transaction in progress

To refuse the confirmation of the invoice, it is necessary to set the GOK variable to 0.

Log file

There is an open log file when the entry point is called from the invoice automatic validation function.

There is no open log file when the entry point is called from the validation button of the invoice function.

Different call cases

This entry point is called from each processing that is used for the validation of an invoice:

·               Validation button in the invoice function

·               Invoice validation function

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…). It is usually the case for the file that contains the header but not for the file that contain the lines…

Table

Significant content

Table Title

SINVOICE

Yes

Invoice headers

SINVOICEV

Yes

Invoice header valuations

SINVOICED

No

Invoice lines

BPCUSTOMER

No

Customers

BPCUSTMVT

No

Customer transactions

TABSIVTYP

No

Invoice types

GAUTACE

No

Automatic journals

GACCDUDATE

No

Open items

PAYORDER

No

Pre-payments

 

LETACOMPTE: Specific/custom process for the matching of pre-payments

This entry point is used to take control, when validating an invoice, during the matching of the pre-payments with the invoice to be validated.

It is used to perform a particular matching process for the pre-payments that will replace the standard processing.

It is called during the TRTVENFACV validation processing for invoices.

Context and operating mode

Transaction

There is one transaction in progress

To refuse the confirmation of the invoice, it is necessary to set the GOK variable to 0.

Log file

There is an open log file when the entry point is called from the invoice automatic validation function.

There is no open log file when the entry point is called from the validation button of the invoice function.

Different call cases

This entry point is called from each processing that is used for the validation of an invoice:

·               Validation button in the invoice function

·               Invoice validation function

Available variables and masks

The WPOINT_ENTREE variable (local integer) has been created. It is used to not execute the standard process for the matching of the pre-payments. It is initialized to 0 before the call to the entry point. It must be set to 1 in the entry point in order not to execute the standard processing.

Open tables

In the table below, the significant content flag indicates that the content matches the context (the current customer is loaded…). It is usually the case for the file containing the header, but not for the file containing the lines…

Table

Significant content

Table Title

SINVOICE

Yes

Invoice headers

SINVOICEV

Yes

Invoice header valuations

SINVOICED

No

Invoice lines

ACTIV

No

Activity code

BPARTNER

No

BP

BPCUSTOMER

Yes

Customers

BPCUSTMVT

No

Customer transactions

FACILITY

No

Sites

GTYPACCENT

No

Entry types

TABSIVTYP

No

Invoice types

GACCCODE

No

Accounting codes

GACCOUNT

No

General ledger accounts

GAUTACE

No

Automatic journals

GACCDUDATE

No

Open items

PAYORDER

No

Pre-payments

 

CREPIH: Automatic generation of inter-site purchase invoice

Use this entry point to take control during the validation of a sales invoice in order to automatically generate an inter-site or inter-company purchase invoice.

It is called at the end of the invoice validation, upon determining the generation or not of the purchase invoice.

Context and operating method

Transaction

There is no transaction in process. The validation transaction of the sales invoice ended correctly. The invoice has been validated.

Log file

There is an open log file when the entry point is called from the invoice automatic validation function.

There is no open log file when the entry point is called from the validation button of the invoice function.

Different call cases

This entry point is called from each processing that is used for the validation of an invoice:

·               Validation button in the invoice function

·               Invoice validation function

Available variables and masks

The EP is located just before the determination or not of the purchase invoice generation.

The [F:SIV] class is on line and loaded.

The WPE_CREPIH variable (local integer) has been created. It is initialized to 0 before the call to the entry point. It must be set to 1 in the entry point to force the generation of the purchase invoice.

Open tables

When the EP is called from the invoice button of the invoice management, the tables of the invoice object are opened.

In the table below, the significant content flag indicates that the content is in phase with the context (the current customer is loaded…). It is usually the case for the file that contains the header and not the file that contain the lines…

Table

Significant content

Table Title

SINVOICE

Yes

Invoice headers

SINVOICEV

Yes

Invoice header valuations

SINVOICED

No

Invoice lines

GACCOUNT

No

Accounts

SVCRFOOT

No

Sales document - Footer item

SVCRVAT 

No 

Sales document - Taxes

FACILITY

No 

Sites 

COMPANY

No 

Companies 

BPCUSTOMER

No

Customers

BPARTNER

No

BP

GACCCODE

No

Invoice types

CADSP

No

Prior allocation keys 

CACCE 

No

Analytical 

CAAUZ

No

Restrictions table 

TABCUR 

No

Currencies 

TABCHANGE 

No

Currency exchange rate 

TABUNIT

No

Units 

GTYPACCENT

No

Document types 

FISCALYEAR

No

Fiscal years 

PERIOD 

No 

Periods 

GAUTACE

No

Automatic journals

GACCDUDATE

No

Open items

GJOURNAL

No

Journals 

ITMMASTER

No

Products 

SDELIVERY

No

Delivery header 

STOJOU

No

Stock journal 

ABATRQT

No

Batch server (requests) 

TABPAM

No 

Payment method table 

GAJOUSTA

No

Journals - reports by period