TRTVENFAC processing: TRTVENFAC
ALISIH: Load the fields in the SINVOICE file during the creation of an invoice
Use this entry point to take over when loading the fields in the "Invoice header" record.
With this entry point, it is possible to load specific/custom fields in the SINVOICE table.
It is called in the automatic invoicing processes:
- for deliveries FUNAUTINVD
- for orders FUNAUTINVO.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is an open log file.
Call context
This entry point is called during the creation of the invoice header.
Available variables and masks
The INVORI local variable is used to identify the document type that is at the origin of the invoice:
- 1 = Quote
- 2 = Order
- 3 = Delivery
The GINVTYP global variable contains the invoice type. The possible values (in this context) are:
- 1 = Invoice
- 5 = Proforma
The GFONCTION global variable contains the function currently being executed:
- FUNAUTINVD Automatic invoicing of deliveries
- FUNAUTINVO Automatic invoicing of orders
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 that contains the header but not for the file that contain the lines…
Table |
Significant content |
Table title |
||
|
Quote source |
Order source |
Delivery source |
|
SINVOICE |
Yes |
Yes |
Yes |
Invoice headers |
SINVOICEV |
Yes |
Yes |
Yes |
Invoice header valuations |
SINVOICED |
No |
No |
No |
Invoice lines |
SQUOTE |
Yes |
No |
No |
Quote header |
SORDERQ |
Yes |
No |
No |
Quote line |
SORDER |
No |
Yes |
No |
Order headers |
SORDERQ |
No |
Yes |
No |
Order line quantities |
SORDERP |
No |
Yes |
No |
Order line prices |
SDELIVERY |
No |
No |
Yes |
Delivery header |
SDELIVERYD |
No |
No |
Yes |
Delivery line |
BPARTNER |
Yes |
Yes |
Yes |
A/P - A/R Accounting |
BPCUSTOMER |
Yes |
Yes |
Yes |
Customers |
BPDLVCUST |
No |
No |
No |
Ship-to customers |
BPCUSTMVT |
No |
No |
No |
Customer transactions |
ITMMASTER |
No |
No |
No |
Products |
TABSIVTYP |
Yes |
Yes |
Yes |
Invoice types |
|
|
|
|
|
ALISIV: Load the fields in the SINVOICEV file during the creation of an invoice
Use this entry point to take over when loading the fields in the "Invoice header" record.
With this entry point, it is possible to load specific/custom fields in the SINVOICEV table.
It is called in the automatic invoicing processes:
- for deliveries FUNAUTINVD
- for orders FUNAUTINVO.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is an open log file.
Call context
This entry point is called during the creation of the invoice header.
Available variables and masks
The INVORI local variable is used to identify the document type that is at the origin of the invoice:
- 1 = Quote
- 2 = Order
- 3 = Delivery
The GINVTYP global variable contains the invoice type. The possible values (in this context) are:
- 1 = Invoice
- 5 = Proforma
The GFONCTION global variable contains the function currently being executed:
- FUNAUTINVD Automatic invoicing of deliveries
- FUNAUTINVO Automatic invoicing of orders
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 |
||
|
Quote source |
Order source |
Delivery source |
|
SINVOICE |
Yes |
Yes |
Yes |
Invoice headers |
SINVOICEV |
Yes |
Yes |
Yes |
Invoice header valuations |
SINVOICED |
No |
No |
No |
Invoice lines |
SQUOTE |
Yes |
No |
No |
Quote header |
SORDERQ |
Yes |
No |
No |
Quote line |
SORDER |
No |
Yes |
No |
Order headers |
SORDERQ |
No |
Yes |
No |
Order line quantities |
SORDERP |
No |
Yes |
No |
Order line prices |
SDELIVERY |
No |
No |
Yes |
Delivery header |
SDELIVERYD |
No |
No |
Yes |
Delivery line |
BPARTNER |
Yes |
Yes |
Yes |
A/P - A/R Accounting |
BPCUSTOMER |
Yes |
Yes |
Yes |
Customers |
BPDLVCUST |
No |
No |
No |
Ship-to customers |
BPCUSTMVT |
No |
No |
No |
Customer transactions |
ITMMASTER |
No |
No |
No |
Products |
TABSIVTYP |
Yes |
Yes |
Yes |
Invoice types |
|
|
|
|
|
ALISID Load the fields in the SINVOICED file during the creation of an invoice
Use this entry point to take over when loading the fields in an "Invoice line" record.
With this entry point, it is possible to load specific/custom fields in the SINVOICED table.
It can also be used to update specific/custom tables linked to the invoice lines.
It is called in the automatic invoicing processes:
- for deliveries FUNAUTINVD
- for orders FUNAUTINVO.
Context and operating mode
Transaction
There is one transaction in progress.
Log file
There is a open log file.
Call context
This entry point is called during the loading of each invoice line.
Available variables and masks
The INVORI local variable is used to identify the document type that is at the origin of the invoice:
- 1 = Quote
- 2 = Order
- 3 = Delivery
The GINVTYP global variable contains the invoice type. The possible values (in this context) are:
- 1 = Invoice
- 5 = Proforma
The GFONCTION global variable contains the function currently being executed:
- FUNAUTINVD Automatic invoicing of deliveries
- FUNAUTINVO Automatic invoicing of orders
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 |
||
|
Quote source |
Order source |
Delivery source |
|
SINVOICE |
Yes |
Yes |
Yes |
Invoice headers |
SINVOICEV |
Yes |
Yes |
Yes |
Invoice header valuations |
SINVOICED |
No |
No |
No |
Invoice lines |
SQUOTE |
Yes |
No |
No |
Quote header |
SORDERQ |
Yes |
No |
No |
Quote line |
SORDER |
No |
Yes |
No |
Order headers |
SORDERQ |
No |
Yes |
No |
Order line quantities |
SORDERP |
No |
Yes |
No |
Order line prices |
SDELIVERY |
No |
No |
Yes |
Delivery header |
SDELIVERYD |
No |
No |
Yes |
Delivery line |
BPARTNER |
Yes |
Yes |
Yes |
A/P - A/R Accounting |
BPCUSTOMER |
Yes |
Yes |
Yes |
Customers |
BPDLVCUST |
No |
No |
No |
Ship-to customers |
BPCUSTMVT |
No |
No |
No |
Customer transactions |
ITMMASTER |
No |
No |
No |
Products |
TABSIVTYP |
Yes |
Yes |
Yes |
Invoice types |
|
|
|
|
|
ALISDDSIH: Load the invoice detail screen in invoice delivery
Use this entry point to take over when loading the invoice detail screen from a delivery detail record. With this entry point, is it possible to intervene in the quantity to be invoiced.
It can be therefore used to load the specific/custom fields in this SIH4 screen.
It is called for each line in the picking of the deliveries from the invoice management.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no open log file when executing the buttons.
Call context
This entry point is called during the loading of each invoice line in the SIH4 screen following the picking of a delivery.
Available variables and masks
The NOL variable contains the number for the screen line.
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 that contains the header but not for the file that contain the lines…
Table |
Significant content |
Table title |
SINVOICE |
No |
Invoice headers |
SINVOICEV |
No |
Invoice header valuations |
SINVOICE |
No |
Invoice lines |
SDELIVERY |
Yes |
Delivery header |
SDELIVERYD |
Yes |
Delivery line |
|
|
|
|
|
|
ALISIDSIH: Load the credit note detail screen from an invoice detail or delivery
Use this entry point to take over during the loading of the credit note detail screen from an invoice detail or delivery return record.
It is therefore possible, using this entry point, to load specific/custom fields in the screen SIH4 and in the table SINVOICED, or to modify the value of already existing fields.
It is called from the credit memo management (creation or modification), for each line, during the picking of invoices or delivery returns.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no open log.
Call context
This entry point is called after each credit memo line is loaded.
Available variables and masks
In the case of a credit note on an invoice, [F :SID] is loaded with the invoice line, [F:SIH] and [F:SIV] are loaded with the invoice header.
In the case of a credit note on delivery return, [F :SRD] is loaded with the return line, [F:SRH] is loaded with the return header, [F :SID] is loaded with the invoice line, [F:SIH] and [F:SIV] are loaded with the invoice header. This invoice corresponds to the invoice for the delivery
The masks of the SIH object are loaded with the credit memo being processed. The detail line is loaded with the invoice or return line being picked.
The WINVORI local variable is used to identify the document type at the origin of the credit memo:
- 4 = Invoice
- 6 = Return
The NOL local variable is the index of the line in [M :SIH4].
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 that contains the header but not for the file that contain the lines…
Table |
Significant content |
Significant content |
Table title |
|
Invoice source |
Return source |
|
SINVOICE |
Yes |
Yes |
Invoice headers |
SINVOICEV |
Yes |
Yes |
Invoice header valuations |
SINVOICED |
Yes |
Yes |
Invoice lines |
SRETURND |
No |
Yes |
Return line |
SDELIVERY |
No |
Yes |
Delivery header |
SDELIVERYD |
No |
Yes |
Delivery line |
ITMMASTER |
Yes |
Yes |
Products |
ITMSALES |
Yes |
Yes |
Product-sales |
ITMBPC |
Yes |
Yes |
Product-customer |
TABSIVTYP |
No |
No |
Invoice type |
SORDER |
No |
No |
Order headers |
SORDERP |
No |
No |
Order line prices |
SORDERQ |
No |
No |
Order line quantities |
BPARTNER |
No |
No |
BP |
BPCUSTOMER |
No |
No |
Customers |
BPCUSTMVT |
No |
No |
Customer transactions |
BPDLVCUST |
No |
No |
Ship-to customers |
FACILITY |
No |
No |
Sites |
ITMMVT |
No |
No |
Product movements |
ITMFACILITY |
No |
No |
Products-sites |
TABCUR |
No |
No |
Currency table |
SALESREP |
No |
No |
Sales reps |
PRICSTRUCT |
No |
No |
Price list structures |
SPRICLINK |
No |
No |
Sales price list search |
GTYPACCENT |
No |
No |
Entry types |
GACCCODE |
No |
No |
Accounting codes |
GACCCOUNT |
No |
No |
General ledger accounts |
CONTSERV |
No |
No |
Service contracts |
GAUTACE |
No |
No |
Automatic journals |
ACODNUM |
No |
No |
Document sequence numbers |
ACTIV |
No |
No |
Activity codes |
TABALLRUL |
No |
No |
Allocation rules |
TABSTORUL |
No |
No |
Stock management rules |
STOWIPW |
No |
No |
Stock currently being processed |
ITMCATEG |
No |
No |
Product category |
SERREQUEST |
No |
No |
Service requests |
HDKTASKINV |
No |
No |
Consumptions to be invoiced |
TABUNIT |
No |
No |
Unit table |
STOJOU |
No |
No |
Stock journal |
STOCK |
No |
No |
Stock |
STOLOT |
No |
No |
Lot number |
SPRICLIST |
No |
No |
Price lists |
ALISRDSIH: Load the credit note detail screen from a direct return detail record
Use this entry point to take over during the loading of the credit note detail screen from a direct return detail record.
It is therefore possible, using this entry point, to load specific/custom fields in the screen SIH4 and in the table SINVOICED, or to modify the value of already existing fields.
It is called from the credit memo management (creation or modification), for each line, during the picking of returns.
Context and operating mode
Transaction
There is no transaction in progress.
Log file
There is no open log.
Call context
This entry point is called after each credit memo line is loaded.
Available variables and masks
[F :SRD] is loaded with the return line, [F:SRH] is loaded with the return header.
The masks of the SIH object are loaded with the credit memo being processed. The detail line is loaded with the return line being picked.
The NOL local variable is the index of the line in [M :SIH4].
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 |
Significant content |
Table title |
|
Invoice source |
Return source |
|
SINVOICE |
Yes |
Yes |
Invoice headers |
SINVOICEV |
Yes |
Yes |
Invoice header valuations |
SINVOICED |
Yes |
Yes |
Invoice lines |
SRETURND |
No |
Yes |
Return line |
SDELIVERY |
No |
Yes |
Delivery header |
SDELIVERYD |
No |
Yes |
Delivery line |
ITMMASTER |
Yes |
Yes |
Products |
ITMSALES |
Yes |
Yes |
Product-sales |
ITMBPC |
Yes |
Yes |
Product-customer |
TABSIVTYP |
No |
No |
Invoice type |
SORDER |
No |
No |
Order headers |
SORDERP |
No |
No |
Order line prices |
SORDERQ |
No |
No |
Order line quantities |
BPARTNER |
No |
No |
BP |
BPCUSTOMER |
No |
No |
Customers |
BPCUSTMVT |
No |
No |
Customer transactions |
BPDLVCUST |
No |
No |
Ship-to customers |
FACILITY |
No |
No |
Sites |
ITMMVT |
No |
No |
Product movements |
ITMFACILITY |
No |
No |
Products-sites |
TABCUR |
No |
No |
Currency table |
SALESREP |
No |
No |
Sales reps |
PRICSTRUCT |
No |
No |
Price list structures |
SPRICLINK |
No |
No |
Sales price list search |
GTYPACCENT |
No |
No |
Entry types |
GACCCODE |
No |
No |
Accounting codes |
GACCCOUNT |
No |
No |
General ledger accounts |
CONTSERV |
No |
No |
Service contracts |
GAUTACE |
No |
No |
Automatic journals |
ACODNUM |
No |
No |
Document sequence numbers |
ACTIV |
No |
No |
Activity codes |
TABALLRUL |
No |
No |
Allocation rules |
TABSTORUL |
No |
No |
Stock management rules |
STOWIPW |
No |
No |
Stock currently being processed |
ITMCATEG |
No |
No |
Product category |
SERREQUEST |
No |
No |
Service requests |
HDKTASKINV |
No |
No |
Consumptions to be invoiced |
TABUNIT |
No |
No |
Unit table |
STOJOU |
No |
No |
Stock journal |
STOCK |
No |
No |
Stock |
STOLOT |
No |
No |
Lot number |
SPRICLIST |
No |
No |
Price lists |
ALISQHSIH: Loading invoice header screens during proforma creation.
Use this entry point to take over during the loading of the invoice detail screen from a quote header record.
It is therefore possible, using this entry point, to load fields that are specific these screens or to modify the value of standard fields.
It is called in quote management, during the creation of a proforma via the proforma button.
Context and operating mode
Transaction
There is one transaction in progress. This transaction is the transaction for the creation of a proforma invoice.
Log file
There is an open log file.
Call context
This entry point is called when loading invoice header screens from the quote header record.
Available variables and masks
[F:SQH] is loaded with the quote header.
The screens of the SIH object, [M:SIH0] [M:SIH1] [M:SIH2], are on line and loaded with the data of the proforma header (data initialized with the quote header).
The address screens ADB2, ADB3 and ADB4 are also on line and loaded. ADB2 is loaded with the address of the ship-to customer from the quote. ADB3 is loaded with the address of the bill-to customer from the customer record. ADB4 is loaded with the address of the pay-by customer from the customer record.
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 |
No |
Invoice headers |
SINVOICEV |
No |
Invoice header valuations |
SINVOICED |
No |
Invoice lines |
SQUOTE |
Yes |
Quote header |
SQUOTED |
No |
Quote line |
BPCUSTOMER |
Yes Customer |
Customers |
BPDLVCUST |
Yes Ship-to customer |
Ship-to customer |
BPARTNER |
Yes Pay-by BP |
BP |
BPADDRESS |
Yes Pay-by BP address |
Addresses |