This entry point located in the TRTACHFAC2 purchase invoice generation processing, generates a "ALIMSKPIH" action.
The aim of this action is to provide the possibility to load specific screen fields for the generation of a purchase invoice.
There is no transaction in progress.
A log file is open if local variable WTRA has a value superior to 2
The call is made for each purchase invoice to generate just before the creation transaction.
The following screen classes are loaded: [M:PIH0], [M:PIH1], [M:PIH3] and [M:PIH4]
The [M:PIHx] classes can be modified without problem for the specific/custom files but with great care with respect to the standard fields.
It is also possible to load other screen classes added in specific/custom.
In order to abort the current invoice generation, set global variable GPIH_WRET to value 1.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
PINVOICE | No | Purchase invoice headers |
PINVOICEV | No | Purchase invoice header additions |
PINVOICED | No | Purchase invoice lines |
BPARTNER | No | BP |
BPSUPPLIER | No | Suppliers |
ITMMASTER | No | Products |
This entry point located in the TRTACHFAC2 purchase invoice generation processing, generates a "ALISIHICO" action.
The goal of this action is to give the possibility to load specific fields in the file classes of a sales invoice to generate an inter-company purchase invoice.
There is no transaction in progress.
A log file is open if local variable WTRA has a value superior to 2
The call is made for each purchase invoice to generate just before loading the screen classes but after reading the sales invoice.
The following file classes are loaded: [F:SIH] and [F:SIV]
The [F:SIH] and [F:SIV] classes can be modified without problem for the specific/custom files but with great care with respect to the standard fields.
These modifications are not recorded in the sales invoice. They are only taken into account for the purchase invoice generation.
In the table below, the significant content flag indicates that the content is in phase with the context.
Table | Significant content | Table Title |
SINVOICE | Yes | Sales invoice headers |
SINVOICEV | Yes | Sales invoice header additions |
PINVOICE | No | Purchase invoice headers |
PINVOICEV | No | Purchase invoice header additions |
PINVOICED | No | Purchase invoice lines |
BPARTNER | No | BP |
BPSUPPLIER | No | Suppliers |
ITMMASTER | No | Products |