Delivery Requests

The order number allows the order to be identified in a unique way. This number is assigned automatically or entered whenever an order is created based on the parameterization of the counter associated with the order type chosen.

If the order counter is defined with automatic allocation, the order number field is not accessible and the counter is assigned to the order creation. Conversely, if the order counter is defined with manual allocation, it is possible to enter it manually. If it is not entered at the moment of creation, the system will automatically assign an order number according to the counter.

Number used to define in a unique way the product line.
This number is automatically generated upon each product line creation.

This field indicates the customer identifier code. 

This field indicates the code of the address to ship to.
You can view the detailed address information by clicking Address from the Actions icon.

• On creation, this field is no longer accessible when a delivery line is created.
  
• Once the delivery has been created, you can no longer modify this field but you can still display the detailed address information.
  You can modify the address after clicking Address/Delivery from the Actions panel.

It is the product reference for which a document line is recorded. It is possible to:

• directly enter a product reference or a Product/Customer reference. The existence of this reference is controlled in the 'Product/Sales' and 'Product/Customer' records. If a 'Product-customer' reference is entered, the system will return the internal product reference. A blocking message can be returned during a product entry if prohibited price lists have been set up for some customers ( see price list setup).
• use the contextual button to:
• select a product from the file of sold products,
• select a product from the list of customer products,
• select a subcontractor shortage, in case of shortage for a subcontracted product,
• create, according to the user's access rights, a product in the file,
• view the price lists for the product.

The entry of the product is used to initialize the Description and Sales unit fields, which can be modified. The sales unit can be modified on the condition that it is chosen from the suggested list that contains the sales and packing units from the product and product-customer records.

At this stage, a warning message can appear that to inform the user of the replacement of the entered product by the substitute product. This automatic substitution only takes place when the following two conditions are fulfilled:

• The fieldArticle of substitution of the plug article has been entered,
• the document date is greater than or equal to the substitution date.

 Once the lie is populated, the product code can no longer be modified. The line has to be deleted and recreated to modify the code.

The early/late for the delivery requests is only calculated from the firm delivery requests and is expressed by two items information. The following fields are grayed out (for the inter-site delivery requests, there is no early/late management). This early/late quantity is expressed in the sales unit entered in the contract order line. It is incremented in the following cases:

• By the quantity for a delivery call-off when a delivery request is late (Planned delivery date strictly less than the current date).

• When a late planned delivery request is transformed into a firm delivery.

• When the late delivery request quantity is increased.

• When the planned date for the delivery request is modified and this new date is before than the current date.

• When cancelling the closing of a delivery request line and that its planned delivery date is earlier than the current date.

• When the delivery line associated with a late delivery request is deleted.

• When the delivery line associated with a late delivery request is modified by increasing the shipped quantity.

This quantity is decremented in the following cases:

• When a late delivery request is deleted.

• When a late firm delivery request is transformed into a planned delivery request.

• When the late firm delivery request quantity is decreased.

• When the planned date for the delivery request is modified and this new date is greater than or equal to the current date.

• When closing a delivery request line and that its planned delivery date is less than the current date.

• When the delivery line quantity associated with a delivery request is greater than the planned quantity. In this context, two behaviors can occur with respect to the value of the parameter EARMGT - Early / late management (VEN chapter, ORD group).

- If this parameter has for value Early/late totals update then the early/late quantity is decreased by the amount that has been shipped in access.

- If this parameter has for value Next delivery request update then the amount shipped in addition will decrease the ordered quantity in the next delivery requests. In this situation, certain delivery requests can then be closed if the reduction of the quantity is such that the remaining quantity is equal to the quantity currently being shipped. Only the delivery requests where the ordered quantity is greater than the allocated quantity plus the shortage quantity plus the quantity being shipped are processed. The early/late quantity for the contract order line can however be decreased if a processed delivery request was late.

The calculated information is used to verify the consistency of the information supplied by the customer and the current status of the request management linked to the contract order.

The Early / Late date is calculated on each update of the early / late quantity total. This corresponds to the last date for which the totals were updated. It is equal to the current date minus one.

Last early/late quantity expressed in Sale unit and provided by the customer.

Enter the delivery date for each delivery request line. The format is as follows:

• DDMMYY or DDMMYYYY for a daily request

• WWWYY or WWWYYYY for a weekly request

• MMYY or MMYYY for a monthly request

Weekly requests and monthly requests are automatically considered as scheduled (non-modifiable status) though daily requests are suggested by default with a firm status which can be modified depending on the firm horizon defined on the contract order line.

Delivery request lines must be entered in a chronological order. In case of insertion, the inserted line must have a date superior or equal to the previous date and inferior or equal to the next date.

Collision on period.

If a delivery call-off plan contains daily, weekly and monthly requests overlapping may occur.

In any case, if a period is defined as weekly, the next periods must be expressed either weekly or monthly. Similarly, if a period is defined as monthly, only monthly periods can be entered in the next periods. It will be impossible to enter the daily requests beyond a weekly or monthly period.

It is possible to have overlapping if a daily request is entered and if a weekly request contains a daily request. This can also be the case if there is a weekly request and an attempt is made to enter a monthly request overlapping the weekly request (For example, if the weekly period included the 2 for the next month, it will not be possible to enter a monthly delivery request for the next month).

The status of the line can take the Firm or Planned value. Only the delivery requests with the status Closed will be suggested for the delivery (see the Delivery documentation).

However all lines can be viewed, independently of their status, using the delivery request inquiry (see the Delivery request inquiry documentation).

It is possible to enter on the line the quantity to be allocated. The quantity to allocate is always equal to the quantity already allocated on the delivery request line. It is possible to increase or decrease the quantity to be allocated. if the INIALLORD - Initialization of the quantity to allocate in order parameter (VEN chapter, SAL group) is set to Yes, the quantity to allocate is always initialized with the total quantity to be allocated to the delivery request line (if the ordered quantity of the delivery request is modified, the quantity to allocate is automatically re-calculated).

The entered quantity can be superior to the ordered quantity. A warning message reports it. The allocation is performed upon recording the delivery request.

If customer reservations exist for this product and if the USERERBPC - Customer reservation consumption parameter is set to Yes, then the reservations carried out by the user are automatically consumed in the allocation process.

The user will need the Allocation authorization in the delivery request management function in order to access this field.

From this field, various functions can be accessed:

• Stock by site.

  This function is used to access the inquiry of the stock by site.

• Filter allocations.

  This option can be used to specify information that may be applied by the detailed allocation or on shipping the order if the line is set to Global allocation. Two exclusive filters can be entered: a lot and a status combination (the entered status combination must be included in the Issue rule associated with the delivery transaction). A preferential filter can be assigned to a location so as to direct the allocation. Allocation Detail. This function is only accessible when several allocated quantities already exist in the delivery request. This function is used to view the stock lines which have been reserved. See button Allocation detail accessible by right-clicking on the line.

• Available Stock.

The project code in document line is initialized by the one entered in the header or, in the case of a document transformation, by the one of the selected document lines (in picking or in mass processing, if the project code on a document line is inactive, the line cannot be selected).

It can only be modified if one of the two following conditions are met:

• The PJTSNGDOC - one project per document parameter (TC chapter, MIS group) is set to No,

• The entry of this field is authorized by the entry transaction being used.

In modification mode, the project code management depends on the value of the CTLOPPCOD - Mandatory project control parameter:

• When the value is No, it may be a code selected freely.

• When its value is Yes, an existence check is systematically applies to the entered project code.

When the entry is controlled, depending on the context, a project or one of its entities can be picked (a budget batch or task), using its posting code:

The project allocation code is composed of:

• The project sequence number for projects.

• The concatenated project sequence number with the budget batch code for a project budget batch.

• The concatenated project sequence number with the number of tasks for a project task.

You can only select one Active posting code depending on the status of the relevant entity. If it becomes inactive after the creation of the document, the control is performed and blocks the modification of the document.

For non-deliverable Service products, you can select a project set with progress billing if the PJM activity code is active. Once the order has been recorded, you can view it in the Project management (GESPJM) function in the generated billing plan, linked to the selected project.

When the project code of the document header is modified, this project code is automatically transferred to the lines, except when the multi-project management is authorized. In this case, a dialog box would open and suggest to transfer this code to the lines of the document, according to the following options:

• Yes: The project code is applied to all lines, excluding lines linked to a billing plan and lines with an incompatible milestone.

• No: The project code is not transferred to the lines.

• Same value: The project code is only transferred to the lines associated to the previous project code.

Sales documents: Quotes, orders, deliveries and invoices:

- If lines are impacted, a dialog box opens requesting a recalculation of prices and discounts. If you answer 'Yes', the price list search is run based on the new project code for all document lines.

- If the project code is modified on the line, the same price list search process applies to the line.

Depending on the processed document, the recalculation is performed only if the following conditions are met:

• For a quote: The item line is not ordered and is not free.

• For an order: The item line is not closed, not delivered, not invoiced nor free.

• For a delivery: The item line is direct and not free.

• For an invoice or a direct credit: the document is not validated, the item line is direct and not free. For direct credits, the quantity is different from 0.

Deliveries linked to a task:

The header project code displays the project code linked to the first selected task.

• If multi-project management of documents is enabled (PJTSNGDOC - One project per document parameter set to No), the delivery can include direct delivery lines and product lines linked to tasks. The header project code is used as the default value on direct delivery lines only. Product lines linked to tasks keep their project code, which cannot be modified. If the header project code is modified, the application of this code to the lines is suggested, as described above. This only applies to direct delivery lines.

• If multi-project management of documents prohibited (PJTSNGDOC - One project per document parameter set to Yes), the delivery cannot include both direct delivery lines and product lines linked to tasks.

• When the delivery is for direct delivery lines, you cannot enter a project code in the header that is already used on tasks.

• When the delivery is for product lines linked to tasks, you can only enter product lines linked to the same task. The header project code can then be used to filter tasks in the selection panel.

Specific case of free items generated by the price list search after updating the header project code: The free item displays the project code of its source product but only if this code is not used on a task.

The carry-forward of the business code is carried out only for unclosed delivery requests. The business code of a delivery request associated with a contract order line cannot be modified

This function is only accessible if the order is of the type planned and if the delivery date is expressed in the form of a period. This option is used to distribute a weekly request over n daily requests and a monthly request over n weekly requests. This type of process on the planned requests must be carried out in chronological order of the requests.

This function is used to close a firm or planned delivery request (except if the delivery date is expressed in the form of a period. In this case this button will not be accessible). It is also used to open a closed delivery request provided it has not be shipped. The user must have the Closing authorization available in the shipment request management function to access this function. It is possible to close a delivery request, even if this possesses the allocated quantities (a warning message will then be displayed that allows a user to continue or to cancel). If the user accepts it, a de-allocation of the line will be carried out on saving the delivery request closure).

The functioning proposed will be the same as for a deletion of a delivery request line. It is impossible to delete a delivery request that has been the object of a delivery or if it is closed.

This function is used to view additional information concerning the contract order line :

Validity date

Planned quantity

Total ordered quantity

Total shipped quantity

Firm horizon

and to modify certain information linked to the delivery of the delivery request :

Shipment site. It will then be possible to modify this information for the delivery requests concerning inter-site or inter-company contract orders to manage the vagaries of the delivery. On the other hand the shipping site will not be updated in the corresponding purchase delivery request.

Consumption location

Carrier

Delivery method

Delivery lead-time

Shipment priority

Packaging code and packaging capacity

This function is used to enter a text on the delivery request line. This text will be initialized in the delivery request by the text entered in the contract order line. This text can then be propagated to the deliveries and invoices as a function of the value of the general setup SALTEXLIN.

This function is only available if the delivery request is allocated. It is then used to consult the stock lines that have been allocated to the delivery request or the allocated total if it is a global allocation.

This function behaves as follows :

In the header the product reference, the product description and the warehouse site for the delivery request line, as well as the stock unit for the product.

A grid then displays the detail of the allocation. The following information is mentioned:

Allocation type: Detailed or Shortage/detail if a shortage exists (the stock information is ten empty except for the quantity in stock unit).

The quantity expressed in stock unit

The lot number if the product is managed by lot

The sub-lot number if the product is managed by sub-lot 

The serial number if the product is managed by serial number

The location if the product is managed by location

The stock line status

The packing unit for the stock line

The quantity expressed in packing unit

The lot expiry date if the product is managed with an expiry date for the lot

Two free stock identifiers

The manual detailed allocation function is available if it is a firm order and this is irrespective of the allocation type for the line. If the allocation type for the line is Global, a warning message informs the user that the allocation that will be carried out will change the allocation type for the line to Detailed. This function is used to manually allocate the stock lines (the products present in certain locations or for specific lots...). This function is only accessible in delivery request modification. It can then be used to allocate more than the ordered quantity such as is allowed for the Quantity to be allocated entry in the shipment request. The user will need to have available the Allocation authorization in the contract order management to access this function.

This function is used to access the Stock by site inquiry for the product present in the delivery request.