Process FUNAUTDLV: Automatic Shipment
AUTDLVFIL: Addition of selection criteria for the orders to be shipped
This entry point is used to insert additional logic during the definition of the selection criteria for the orders to be shipped.
It is used to add additional filters on these orders.
It is also used to force the shipment of non allocated orders as well as the shipment of shortage quantities.
It is called in the automatic shipment of orders process FUNAUTDLV.
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 shipped.
Call context
This entry point is called during the selection criteria definition.
Available variables and masks
The order line selection mask [M :DIA] (SAD1) 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.
Special feature:
To force the shipment of non allocated orders as well as shipment of quantities with shortages (if the ‘SHTDLV’ setup authorizes it and if negative stocks are authorized), it is necessary to set the global variable GLIVSPE to 1.
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 |
|
SORDER |
Yes |
Order headers |
|
SORDERQ |
Yes |
Order line quantities |
|
SORDERP |
Yes (if standard order) |
Order line prices |
|
SORDERC |
Yes (if contract order) |
Product / customer orders (contract orders) |
|
SDELIVERY |
No |
Shipment header |
|
SDELIVERYD |
No |
Shipment line |
|
SWRKDLV |
No |
Work file |
|
BPARTNER |
No |
BP |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
BPCUSTOMER |
No |
Customers |
|
SALESREP |
No |
Sales representatives |
|
BPCARRIER |
No |
Carriers |
|
TABMODELIV |
No |
Shipment methods |
|
SPRICLINK |
No |
Search sales prices (link) |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
ITMBPC |
No |
Products - Customers |
|
ITMFACILIT |
No |
Products - Sites |
|
ITMMVT |
No |
Product - Movements |
|
FACILITY |
No |
Sites |
AUTDLVMAJ: Update of the specific/custom files after creation of a shipment
This entry point is used to insert additional logic before the end of the posting transaction for a shipment in order to update the specific/custom files.
It is called in the automatic shipment process FUNAUTDLV
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 shipment function before the end of each transaction for posting a shipment.
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 |
|
SDELIVERY |
Yes |
Shipment header |
|
SDELIVERYD |
No |
Shipment line |
|
SORDER |
No |
Order headers |
|
SORDERQ |
No |
Order line quantities |
|
SORDERP |
No |
Order line prices |
|
SORDERC |
No |
Product / customer orders (contract orders) |
|
BPARTNER |
Yes (BP invoice) |
BP |
|
BPCUSTOMER |
Yes (Bill to customer ) |
Customers |
|
BPDLVCUST |
Yes |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
SALESREP |
No |
Sales representatives |
|
BPCARRIER |
Yes |
Carriers |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
ITMBPC |
No |
Products - Customers |
|
ITMFACILIT |
No |
Products - Sites |
|
TABMODELIV |
Yes |
Shipment methods |
|
FACILITY |
No |
Sites |
|
|
|
|
AUTDLVSEL: Addition of authorization controls for the orders to be shipped
This entry point is used to insert additional logic at the end of the authorization controls for the shipment of an order line. It therefore makes it possible to add tests that are used to reject the order line.
It is called in the automatic shipment process FUNAUTDLV
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 shipment function at the end of the authorization controls on the shipment of each order line.
Available variables and masks
The order selection mask SAD1 is available.
To refuse the order line, it is necessary to set the OK variable to 1.
To force the shipment of non allocated orders as well as shipment of quantities with shortages (if the ‘SHTDLV’ setup authorizes it and if negative stocks are authorized), it is necessary to set the global variable GLIVSPE to 1.
To force the generation of a break corresponding to the allocated non-deliverable quantity (count under progress, analysis request etc.), the local variable WRUP must be set to 1.
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 |
|
SDELIVERY |
No |
Shipment header |
|
SDELIVERYD |
No |
Shipment line |
|
SORDER |
Yes |
Order headers |
|
SORDERQ |
Yes |
Order line quantities |
|
SORDERP |
Yes (if standard order) |
Order line prices |
|
SORDERC |
No |
Product / customer orders (contract orders) |
|
BPARTNER |
No |
BP |
|
BPCUSTOMER |
No |
Customers |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
SALESREP |
No |
Sales representatives |
|
BPCARRIER |
No |
Carriers |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
ITMBPC |
No |
Products - Customers |
|
ITMFACILIT |
No |
Products - Sites |
|
TABMODELIV |
No |
Shipment methods |
|
FACILITY |
No |
Sites |
AUTDLVREG: Addition of the conditions for the grouping of orders on a shipment
This entry point is used to insert additional logic before the write to the work file of each order line to be shipped entry. Thus it is used to add data that serves as shortage criteria in the data of the work file (SWDDATA field) or to modify the key (SWDKEY field).
It is called in the automatic shipment process FUNAUTDLV.
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 shipment function for each posting of an entry to the work file.
Available variables and masks
The order selection mask SAD1 is available.
To add shortage criteria, it is necessary to load the required information in the SWDDATA field.
Eg.: [F :SWD]SWDDATA += [F :SOH]xxx
Warning: In the SWDDATA field, there are only 19 characters available.
Any modification involving the key field SWDKEY can become problematic concerning the generated shipments.
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 |
|
SWRKDLV |
Yes |
Automatic shipment work file |
|
SORDER |
Yes |
Order headers |
|
SORDERQ |
Yes |
Order line quantities |
|
SORDERP |
Yes if [F :SOH]SOHCAT<>4 |
Order line prices |
|
SORDERC |
No |
Product open order |
|
SDELIVERY |
No |
Shipment header |
|
SDELIVERYD |
No |
Shipment line |
|
BPARTNER |
No |
BP |
|
BPCUSTOMER |
No |
Customers |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
|
|
|
AUTDLVWRK: Modification of the work file before use
This entry point is used to insert additional logic after the write to the work file of each order line to be shipped entry. It is also used to insert logic before the shipment creation process by identifying the lines to be processed. It will for example be possible to launch an urgent reorder process for the picking fields concerned in order to avoid shortages during the shipment.
It is called in the automatic shipment process FUNAUTDLV.
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 shipment function after the write to the work file.
Available variables and masks
The order selection mask SAD1 is available.
The work table SWRKDLV contains the identification of all the order lines that are to be shipped.
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 |
|
SWRKDLV |
No |
Automatic shipment work file |
|
SORDER |
No |
Order headers |
|
SORDERQ |
No |
Order line quantities |
|
SORDERP |
No |
Order line prices |
|
SORDERC |
No |
Product open order |
|
SDELIVERY |
No |
Shipment header |
|
SDELIVERYD |
No |
Shipment line |
|
BPARTNER |
No |
BP |
|
BPCUSTOMER |
No |
Customers |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
|
|
|
AUTDLVDET: Intervene at the end of the processing of a shipment line detail
This entry point is used to insert additional logic at the end of the shipment line detail process.
It is called in the automatic shipment process FUNAUTDLV
Context and operating method
Transaction
There is one transaction in progress. It is the shipment creation transaction.
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.
Call context
This is the shipment creation transaction. The shipment header has been loaded, it has not yet been created.
We find ourselves not at the level of a line detail process at the end of the process. The detail line has been created, the updates related this line have been carried out (Order update, Credit management and the allocations).
Available variables and masks
The order selection mask SAD1 is available.
The order header record to be shipped is loaded in [F:SOH].
The shipment header record to be created is loaded in [F:SDH] but it is not yet created.
The entries for the line detail of the order to be shipped are loaded in [F:SOP] and [F:SOQ].
The entry of the shipment detail is loaded in [F:SDD] and it has been created.
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 |
|
SWRKDLV |
No |
Work file |
|
SDELIVERY |
Yes |
Shipment header |
|
SDELIVERYD |
Yes |
Shipment line |
|
SORDER |
Yes |
Order headers |
|
SORDERQ |
Yes |
Order line quantities |
|
SORDERP |
Yes |
Order line prices |
|
SORDERC |
Yes |
Product / customer orders (contract orders) |
|
BPARTNER |
Yes (BP invoice) |
BP |
|
BPCUSTOMER |
Yes (Bill to customer ) |
Customers |
|
BPDLVCUST |
Yes |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
SALESREP |
No |
Sales representatives |
|
BPCARRIER |
Yes |
Carriers |
|
ITMMASTER |
Yes |
Products |
|
ITMSALES |
Yes |
Products - Sales |
|
ITMBPC |
Yes |
Products - Customers |
|
ITMFACILIT |
No |
Products - Sites |
|
TABMODELIV |
Yes |
Shipment methods |
|
FACILITY |
No |
Sites |
|
SPRICLINK |
No |
Search sales prices (link) |
|
ACTIV |
No |
Activity codes |
AUTTRSVEN: Intervene to modify the transaction to be used
This entry point is used to take over when the transaction was determined in standard mode in order to modify it in contextual mode.
It is called in the automatic shipment process FUNAUTDLV
Context and operating method
Transaction
There is no transaction in progress.
To cancel the transaction if there is a problem, the OK variable must be set to 1.
Log file
There is an open log file.
Call context
This entry point is called:
in the automatic delivery function, after determining the default delivery transaction.
Available variables and masks
The order selection mask SAD1 is available.
Variable WFLGLIG has value 1 if this is a normal delivery.
Variable WFLGLND has value 1 if this is a loan delivery.
The default transaction is stored in WTRS variable. This value can be modified to adapt the specific context.
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 |
|
SWRKDLV |
No |
Automatic shipment work file |
|
SORDER |
No |
Order headers |
|
SORDERQ |
No |
Order line quantities |
|
SORDERP |
No |
Order line prices |
|
SORDERC |
No |
Product open order |
|
SDELIVERY |
No |
Shipment header |
|
SDELIVERYD |
No |
Shipment line |
|
BPARTNER |
No |
BP |
|
BPCUSTOMER |
No |
Customers |
|
BPDLVCUST |
No |
Ship-to customers |
|
BPCUSTMVT |
No |
Customer transactions |
|
ITMMASTER |
No |
Products |
|
ITMSALES |
No |
Products - Sales |
|
|
|
|