Process FUNAUTINVO: Automatic Billing of the Order
AUTINVOFIL: Add selection criteria to the orders to be invoiced
This entry point is used to insert additional logic during the definition of the selection criteria for the orders to be invoiced.
It is used to add additional filters on these orders.
It is called in the automatic invoicing of orders process FUNAUTINVO.
Context and operating method
Transaction
There is no transaction in process.
Log file
No log file is open at this time because it is the selection phase for the order lines to be invoiced.
Call context
This entry point is called during the selection criteria definition.
Available variables and masks
The order line selection mask [M :DIA] (SAUTINVO) is still available.
The standard criteria are loaded :
In the CRITERE variable for the order header (SORDER file). The FILSUPENT variable has been created to add additional criteria.
In the CRITDET variable for the detail of the order lines (SORDERQ file). The FILSUPDET variable has been created to add additional criteria.
These 2 variables are sized at 250 characters. To aid the functioning during the evaluation, FILSUPENT and FILSUPDET are initialized to the string "1=1" if these variables have not been loaded by the entry point.
It is sufficient to complete them in the entry point.
For instance : Add an additional filter on the product reference that must start with "VEN".
FILSUPDET -= ‘ & ITMREF >= "VEN"’
FILSUPENT is evaluated at the same time as CRITERE during the filter on the SORDER file. The criteria must relate to the fields in the SORDER file.
FILSUPDET is evaluated at the same time as CRITDET, during the filter on the file SORDERQ. The criteria must relate to the fields in the SORDERQ file.
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...). Traditionally, this is the case for the file that contains the header and not the file that contains the lines...
|
Table |
Significant content |
Table Title |
|
SINVOICE |
No |
Invoice headers |
|
SINVOICEV |
No |
Invoice header valuations |
|
SINVOICED |
No |
Invoice lines |
|
SORDER |
No |
Order headers |
|
SORDERQ |
No |
Order line quantities |
|
SORDERP |
No |
Order line prices |
|
BPARTNER |
No |
BP |
|
BPCUSTOMER |
No |
Customers |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
ITMFACILIT |
No |
Product-site, |
|
GTYPACCENT |
No |
Journal types |
|
GACCCODE |
No |
Accounting codes |
|
GACCOUNT |
No |
General ledger accounts |
|
GAUTACE |
No |
Automatic journals |
|
GAUTACEF |
No |
Automatic journal formulas |
|
GJOURNAL |
No |
Journals |
|
ACODNUM |
No |
Document sequence number counter |
|
TABMODELIV |
No |
Shipment method table |
|
TABCOUAFF |
No |
Sequence number counter assignment table |
|
SWRKINV |
No |
Work file |
|
TABSIVTYP |
No |
Customer invoice type table |
AUTINVOMAJ: Updates of the specific/custom files after the creation of an invoi
This entry point is used to insert additional logic before the end of the posting transaction for an invoice in order to update the specific/custom files.
It is called in the automatic invoicing process FUNAUTINVO.
Context and operating method
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file.
Different call cases
This entry point is called:
in the automatic invoicing of orders before the end of each posting transaction of an invoice.
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...). Traditionally, this is the case for the file that contains the header and not the file that contains the lines...
|
Table |
Significant content |
Table Title |
|
SINVOICE |
Yes |
Invoice headers |
|
SINVOICEV |
Yes |
Invoice header valuations |
|
SINVOICED |
No |
Invoice lines |
|
SORDER |
No |
Order headers |
|
SORDERQ |
No |
Order line quantities |
|
SORDERP |
No |
Order line prices |
|
BPARTNER |
Yes (BP invoice) |
BP |
|
BPCUSTOMER |
Yes (Bill to customer ) |
Customers |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
TABSIVTYP |
Yes |
Invoice types |
|
GTYPACCENT |
No |
Journal types |
|
GACCCODE |
No |
Accounting codes |
|
GACCOUNT |
No |
General ledger accounts |
|
GAUTACE |
No |
Automatic journals |
|
GAUTACEF |
No |
Automatic journal formulas |
|
GJOURNAL |
No |
Journals |
|
|
|
|
AUTINVOSEL: Add authorization controls to the order line to be invoiced
This entry point is used to insert additional logic at the end of the authorization controls in the invoicing of an order. It therefore makes it possible to add tests that are used to reject the order line.
It is called in the automatic invoicing process FUNAUTINVO.
Context and operating method
Transaction
There is no transaction in process.
To refuse the order line, it is necessary to set the OK variable to 1.
Log file
There is an open log file.
Different call cases
This entry point is called:
in the automatic invoicing function at the end of the authorization controls on the invoicing of each order line.
Available variables and masks
The order selection mask SAUTINVO is available.
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...). Traditionally, this is the case for the file that contains the header and not the file that contains the lines...
|
Table |
Significant content |
Table Title |
|
SINVOICE |
No |
Invoice headers |
|
SINVOICEV |
No |
Invoice header valuations |
|
SINVOICED |
No |
Invoice lines |
|
SORDER |
Yes |
Order headers |
|
SORDERQ |
Yes |
Order line quantities |
|
SORDERP |
Yes |
Order line prices |
|
BPARTNER |
No |
BP |
|
BPCUSTOMER |
Yes (ordering customer) If [F:SOH]IME=5 |
Customers |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
TABSIVTYP |
No |
Invoice types |
|
GTYPACCENT |
No |
Journal types |
|
GACCCODE |
No |
Accounting codes |
|
GACCOUNT |
No |
General ledger accounts |
|
GAUTACE |
No |
Automatic journals |
|
GAUTACEF |
No |
Automatic journal formulas |
|
GJOURNAL |
No |
Journals |
|
|
|
|
AUTINVOREG: Modification of the sort/shortage criteria of the orders to be invo
This entry point is used to insert additional logic before the write to the work file of each order line to be invoiced entry. Thus it is used to add data that serves as shortage criteria in the data of the work file (SWIDATA field) or to modify the key (SWIKEY and SWIKEY1 fields).
It is called in the automatic invoicing process FUNAUTINVO.
Context and operating method
Transaction
There is no transaction in process.
Log file
There is an open log file.
Different call cases
This entry point is called:
in the automatic invoicing of orders function for each posting of an entry to the work file.
Available variables and masks
The order selection mask SAUTINVO is available.
To add shortage criteria, it is necessary to load the required information in the SWIDATA field.
Ex : [F :SWI]SWIDATA += [F :SOH]xxx
Warning: In the SWIDATA field, there are only 40 characters available.
Any modification involving the key fields SWIKEY and SWIKEY1 can lead to problems involving the generated invoices.
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...). Traditionally, this is the case for the file that contains the header and not the file that contains the lines...
|
Table |
Significant content |
Table Title |
|
SWRKINV |
Yes |
Automatic invoicing work file |
|
SINVOICE |
No |
Invoice headers |
|
SINVOICEV |
No |
Invoice header valuations |
|
SINVOICED |
No |
Invoice lines |
|
SORDER |
Yes |
Order headers |
|
SORDERQ |
Yes |
Order line quantities |
|
SORDERP |
Yes |
Order line prices |
|
BPARTNER |
No |
BP |
|
BPCUSTOMER |
Yes (ordering customer) If [F:SDH]IME=5 |
Customers |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
TABSIVTYP |
No |
Invoice types |
|
GTYPACCENT |
No |
Journal types |
|
GACCCODE |
No |
Accounting codes |
|
GACCOUNT |
No |
General ledger accounts |
|
GAUTACE |
No |
Automatic journals |
|
GAUTACEF |
No |
Automatic journal formulas |
|
GJOURNAL |
No |
Journals |
|
|
|
|
AUTINVOEND: Modification of the invoice or addition of lines before invoice cal
This entry point is used to insert additional logic after the loading of all the lines in class [M] as well as their write to [F:SID] and before the launch of the invoice calculation. It is used to add additional lines or to carryout modifications before the calculation.
It is called in the automatic invoicing process FUNAUTINVO.
Context and operating method
Transaction
There is one transaction in progress.
To cancel the transaction if there is a problem, the GOK variable must be set to 0.
Log file
There is an open log file.
Different call cases
This entry point is called:
in the automatic invoicing of orders before the end of each posting transaction of an invoice.
Available variables and masks
The masks for the invoice management are available : [M:SIH0] (SIH0), [M:SIH1] (SIH1), [M:SIH2] (SIH2), [M:SIH4] (SIH4).
For the addition of a line use the $TRT_DETAIL dimension from the FUNAUTINVO process as the template.
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...). Traditionally, this is the case for the file that contains the header and not the file that contains the lines...
|
Table |
Significant content |
Table Title |
|
SINVOICE |
Yes |
Invoice headers |
|
SINVOICEV |
Yes |
Invoice header valuations |
|
SINVOICED |
No |
Invoice lines |
|
SORDER |
No |
Order headers |
|
SORDERQ |
No |
Order line quantities |
|
SORDERP |
No |
Order line prices |
|
BPARTNER |
Yes (BP invoice) |
BP |
|
BPCUSTOMER |
Yes (Bill to customer ) |
Customers |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
TABSIVTYP |
Yes |
Invoice types |
|
GTYPACCENT |
No |
Journal types |
|
GACCCODE |
No |
Accounting codes |
|
GACCOUNT |
No |
General ledger accounts |
|
GAUTACE |
No |
Automatic journals |
|
GAUTACEF |
No |
Automatic journal formulas |
|
GJOURNAL |
No |
Journals |
|
|
|
|