TRTACHFAC1 processing: TRTACHFAC1
MAJVALPIH: Additional updates to the validation of a purchase invoice
This entry point is located in the TRTACHFAC1 processing for purchase invoice validation and generates a "MAJVALPIH" action.
The aim of this action is to give the possibility to perform additional updates during the validation of an invoice.
Context and operating mode
Transaction
There is one transaction in progress. Can be aborted by setting GOK to 0.
Log file
There is an open log file.
Different call cases
The call is made for each validated invoiced just before the re-write of the invoice header [F :PIH].
Available variables and masks
The following file class is loaded: [F:PIH]
The [F :PIH] class can be modified without any problem for specific/custom fields, but they should be modified with caution for standard fields. For example, the validated invoice flag [F :PIH]STA must not be modified and must always be equal to 3.
Other updates can be carried out for the[F :PIV] classes invoice header addition and [F :PID] invoice lines. It will be up to the user of the entry point to perform the correct reads and re-writes of these classes.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
|
Table |
Significant content |
Table title |
|
PINVOICE |
Yes |
Purchase invoice header |
|
PINVOICEV |
No |
Purchase invoice header additions |
|
PINVOICED |
No |
Purchase invoice lines |
|
BPARTNER |
No |
BP |
|
BPSUPPLIER |
No |
Suppliers |
|
ITMMASTER |
No |
Products |
GAUVALPIH: Automatic journal to be used on invoice validation
This entry point is located in the TRTACHFAC1 processing for purchase invoice validation and generates a "MAJVALPIH" action.
The purpose of this action is to give the possibility to force a given automatic journal when validating a purchase invoice.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is an open log file.
Different call cases
The call is made for each invoice to validate, just before the validation processing.
Available variables and masks
The following file class is loaded: [F:PIH]
The WTRANSAC variable includes the code of the automatic journal to be used.
This variable must be modified in order to force the use of a specific automatic journal.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
|
Table |
Significant content |
Table title |
|
PINVOICE |
Yes |
Purchase invoice header |
|
PINVOICEV |
No |
Purchase invoice header additions |
|
PINVOICED |
No |
Purchase invoice lines |
|
BPARTNER |
No |
BP |
|
BPSUPPLIER |
No |
Suppliers |
|
ITMMASTER |
No |
Products |
CUSMAJCMM: Deactivation of commitments
This entry point is located in the purchase invoice validation process TRTACHFAC1 and is used to prevent the launch of the commitments update.
Context and operating mode
Transaction
There is one transaction in progress. Can be aborted by setting GOK to 0.
Log file
There is an open log file.
Different call cases
The call is made for each validated invoice line.
Available variables and masks
The following file classes are loaded: [F:PIH] and [F:PID]
The global variable GPE set to 1 before call to the entry point. When the update of commitments is not required, it should be positioned to 0.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
|
Table |
Significant content |
Table title |
|
PINVOICE |
Yes |
Purchase invoice header |
|
PINVOICEV |
Yes |
Purchase invoice header additions |
|
PINVOICED |
Yes |
Purchase invoice lines |
|
BPARTNER |
No |
BP |
|
BPSUPPLIER |
No |
Suppliers |
|
ITMMASTER |
No |
Products |
CHGREGVAL: modification of a valuation amount
This entry point is located in the purchase invoice validation process TRTACHFAC1 and is used to modify the stock adjustment as WMT.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is an open log file.
Different call cases
The call is made for each validated invoice line.
Available variables and masks
The following file classes are loaded: [F:PIH] and [F:PID]
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
|
Table |
Significant content |
Table title |
|
PINVOICE |
Yes |
Purchase invoice header |
|
PINVOICEV |
No |
Purchase invoice header additions |
|
PINVOICED |
Yes |
Purchase invoice lines |
|
BPARTNER |
No |
BP |
|
BPSUPPLIER |
No |
Suppliers |
|
ITMMASTER |
No |
Products |
MAJVALPIHA: Additional updates to the validation of a purchase invoice
This entry point is located in the purchase invoice validation process TRTACHFAC1 and generates a "MAJVALPIHA" action.
The aim of this action is to give the possibility to perform additional updates during the validation of an invoice.
This action is positioned before updating standard tables.
Context and operating mode
Transaction
There is one transaction in progress. Can be aborted by setting GOK to 0.
Log file
There is an open log file.
Different call cases
The call is made for each validated invoiced just before the re-write of the invoice header [F :PIH].
Available variables and masks
The following file class is loaded: [F:PIH]
The [F :PIH] class can be modified without any problem for specific/custom fields, but they should be modified with caution for standard fields. For example, the validated invoice flag must not be modified.
Other updates can be carried out for the[F :PIV] classes invoice header addition and [F :PID] invoice lines. It will be up to the user of the entry point to perform the correct reads and re-writes of these classes.
Open tables
In the table below, the significant content flag indicates that the content is in phase with the context.
|
Table |
Significant content |
Table title |
|
PINVOICE |
Yes |
Purchase invoice header |
|
PINVOICEV |
No |
Purchase invoice header additions |
|
PINVOICED |
No |
Purchase invoice lines |
|
BPARTNER |
No |
BP |
|
BPSUPPLIER |
No |
Suppliers |
|
ITMMASTER |
No |
Products |