On the other hand, the manual shipment or the manual invoicing functions (for orders with direct invoicing) can be used without allocation being carried out beforehand.
An allocation can be:
The allocation can be carried out at different stages:
Refer to documentation Implementation
A single screen is necessary to carryout this allocation type. STOP Use it to enter the different information necessary for the selection of orders to be allocated.
Presentation
1/ Enter the selection criteria and the processing parameters.
You can save these selection criteria under a Memo code and recall them later on.
Click OK to launch the automatic allocation processing.
The order lines eligible are then made based on the delivery date and by shipment priority.
If no order line matches the carried out selection, a warning message will be displayed.
A log file will summarize the list of processed order lines processed as well as the result of each allocation.
Close
Fields
The following fields are present on this tab :
Selection criteria
|   |
| Enter a shipment site code that corresponds to a storage site. The shipment site is loaded by default with the your storage site. |
| The shipment date entered is used to filter the orders to be taken into account in the process. Only orders for which the shipment date is less than or equal to the entered date are taken into account. By default, the current date is proposed. |
Parameters
| Partial allocation |
| Imputation réservations client. Indicateur OUI/NON . Permet d'utiliser ou pas les allocations existantes pour le client de la commande. |
| Select this check box if you want to generate shortages when there is no available quantity to allocate.
This check box is initialized according to the value of the GENSHT -Generate shortages parameter (STO chapter, MIS group). |
| If this flag is activated, all the quantities in shortage are reallocated first. Then, the remainder to allocate will be allocated. |
|
|
Start - end range
| Used to carry out a selection on the delivery priority. Aselection start and end range must be entered. |
| Used to carry out a selection on the delivery priority. Aselection start and end range must be entered. |
| Enter a start and an end range to select order numbers: only the orders whose reference is within the entered range are selected. The selection window only displays orders of the Normal category, not totally invoiced and attached to the selected site. |
| Enter a start and an end range to select order numbers: only the orders whose reference is within the entered range are selected. The selection window only displays orders of the Normal category, not totally invoiced and attached to the selected site. |
| Enter a start and end range to apply a filter to the customer codes selection. |
| This field is used to select one of the delivery addresses of the selected customer. When two fields are available (Start/End), it is possible to select a range of several delivery addresses for the same customer.
|
| Enter a start and end range to apply a filter to the customer codes selection. |
| This field is used to select one of the delivery addresses of the selected customer. When two fields are available (Start/End), it is possible to select a range of several delivery addresses for the same customer.
|
| This field is used to select the product. Selection start and end ranges must be entered for the product reference. |
| This field is used to select the product. Selection start and end ranges must be entered for the product reference. |
Extra criteria
| This criteria is used to carry out additional filters on the orders to be allocated. |
| Criteria used to carry out additional filters on the order lines to be allocated. |
| This field is used to select a route code. |
|   |
Close
The allocation of selected order lines or delivery requests depends on the allocation type specified in the order line or delivery request.
If the allocation is of the global type, a reservation will be carried out according to the available stock for the product and to the global allocation rule for the product category. This rule is used to determine by a large status group those that are authorized for the allocation.
If the allocation is of the detailed type, a reservation will be carried out on the stock objects (Lot, Sub-lot, Serial number, Status, Location, Packing unit) following the detailed allocation rule for the category to which the product belongs. Those filters that have been entered on the order lines or delivery requests will also impact the result of the detailed allocations. Two exclusive filters can be entered. These are a filter on the lot number and the status (see the Orders or Delivery requests documentations). In the allocation algorithm, if no stock object corresponds to these exclusive filters, a shortage will be generated. A preferential filter can be entered. This is for the preferential location (see the Orders or Delivery requests documentations). It is used to steer the allocation by specifying that the stock objects must be taken as a priority from this location. If there is no corresponding stock object in this location, the system will then continue its search to allocate the stock objects according to the allocation rule.
This first allocation phase is carried out when the Priority to shortage quantities flag has been selected. In this case, the program carries out an initial allocation of all the order lines corresponding to the selection and having a shortage quantity not equal to zero. The allocation attempt only concerns the shortage quantity. However, if the order line to be processed must be shipped as a single drop and the Partial allocation flag has not been selected, the allocation attempt will concern the total order quantity. This allocation is then carried out under the condition that there is sufficient available stock and that if this is not the case, no quantity is allocated.
This second phase is used to process all the order lines corresponding to the selection and that have not been completely allocated. Equally in this phase, if the order line to be processed must be shipped as a single drop and the Partial allocation flag has not been selected, the allocation attempt will concern the total order quantity. This allocation is then carried out under the condition that there is sufficient available stock and that if this is not the case, no quantity is allocated.
In addition a specific process is carried out for the commercial Kit type products. In fact, the Kit parent product and its components are not disassociated and the allocation is carried out for the parent product (if it is managed in stock) and for the components. The GENSHT - Shortage generation parameter (STO chapter, MIS group) is not applied to the kit components. Whatever the value of this setup, the shortages are always generated for the components of the kit if their stock is insufficient. This is in order to maintain the proportionality between the parent product and its components.
A summary is displayed at the end of the processing. In this report, the following data is displayed for each processed order line: the order number, the customer code and the product reference. When an allocation has been correctly carried out, the allocated quantity is also shown as well as any shortage quantities. Conversely, an error message is displayed under the references of the orders concerned. This report can be printed or deleted.
When the following requirements are met:
- the approval circuit is managed,
- the value of the SOHAPPALL - Allocation on unsigned order parameter is No,
- the order is approved and allocated,
any line addition/deletion or any modification of a field having an impact on the approval status (canceled approval), will generate an automatic de-allocation of the order (a list of these fields is provided in the documentation relating to the Order approvals management rule: SOHSIG).
This function can be run in batch mode. The standard task FUNAUTALL is provided for that purpose.
In addition to the generic error messages, the following messages can appear during the entry :
This message appears when the entered shipment site is not a stock site. Note that only the products managed in stock can be allocated.
In the processing report, for each processing line dealt with (the following references are systematically specified): Order no., Customer no. and Product reference), the following messages can be displayed:
This message appears when another user is already in the process of modifying the order being processed.
This message appears when the Credit status flag in the order has the value Authorized credit exceeded. In this case the allocation is not carried out.
This message appears when the Credit status flag in the order has its value set to Blocked. In this case, the allocation is not carried out.
This message appears when the requested prepayments for this order have not been received. In this case the allocation is not carried out.
This message appears when the order line concerned for a product that should be shipped in a single drop for a quantity is unavailable in stock and the Partial allocation flag has not been selected. In this case the allocation is not carried out.
This message appears when the order line concerns a purchased product and the shipment date for the line is greater than the (processing date + purchasing lead-time + preparation lead-time). In this case the line is not considered in the processing.
This message appears when the order line concerns a manufactured product and the shipment date for the line is greater than the (processing date + production lead-time + preparation lead-time). In this case the line is not considered in the processing.