Deliveries

The 'delivery site' is initialized by default with the normal storage site for the user.
It can be modified provided that the chosen site is defined with an active 'stock' indicator. The chosen site must belong to the same legal company that the sales site.

The delivery type is used to determine, amongst other things, the sequence number counter at use.

Only one delivery type of the same category as the one specified in the entry transaction can be entered. However, when the category has for value All types, the delivery type is free; in this case, it this type that will determine the category.
Besides, the legislation and company group for which it is defined must be consistent with those of the shipping site company.
For further information, click here.

The choice of the delivery type can be modified as long as no delivery line has been created.

When creating a delivery by picking documents (orders, contracts, picking tickets, sub-contract shortages, sub-contract reorders), the documents that are available for selection are filtered with respect to the delivery type: only the ones having the same delivery type or the ones with no delivery type are listed.

On creating a delivery directly from the order, this field is loaded with the deliver type mentioned in the order and taken from the setup of the order type. By default, the delivery type specified for the following parameters is taken into account:

• SDHTYPNOR - Normal delivery type.
• SDHTYPLND - Loan delivery type
• SDHTYPSCO - Sub-contract delivery type

When directly creating a nonbillable delivery, this field is loaded by default with the delivery type specified by the SDHTYPNINV - Nonbillable delivery type parameter.

During the Automatic deliver of orders processing, the delivery type consists in a grouping criteria. When it is not specified in the order, the delivery type entered in the processing launch function is the one that is taken into account.

During the Picking ticket delivery processing, the delivery type consists in a grouping criteria. When it is not specified in the picking ticket, the delivery type entered in the processing launch function is the one that is taken into account. This is the case of picking tickets related to sub-contracting requirements: in this context no delivery type is entered.

Type: import of loan delivery

If the delivery comes from a loan order, the information is automatically displayed. It can also be defined manually that the shipping being entered is a type loan shipping. The validation of a delivery of the loan type simply corresponds to a location change. The stock used in the loan delivery goes from a shipping site location to a Customer location defined for the ship-to customer. Therefore, there is no decrease in the physical stock upon validating a loan delivery. However, the available stock is decremented.

In order to be able to provide a loan to a customer, loans must be authorized for this customer (Commercial section in the customer record). In addition, it is necessary that a location of the Customer Stock type be defined and then associated with the delivery address of the customer (Ship-to customers section of the customer record). It is recommended that a loan location by customer and by delivery address be defined so as to view more clearly the products being loaned. Finally, for each product to be loaned, the product must authorize loans (Sales section of the product record) and be managed by location (Management section of the product site record).
It is important to note that loans are usually not to be invoiced since they are meant to be returned. In some cases, the loaned goods can however be invoiced if the customer has not returned them before the expected return date. The invoicing of a loan is done only from the delivery by clicking on the Invoice action. In this case, only non-returned goods will be invoiced. The physical issue of products will be performed on validating the invoice. A loan delivery can however lead to a Pro forma.

Type: subcontract deliveries

A sub-contract delivery is never attached to an order. It is always a direct delivery. It will therefore be appropriate for a delivery of this type to specify that it is a delivery sent to the subcontractor. The validation of a delivery of the loan type simply corresponds to a location change. The stock used in the subcontracting delivery goes from a shipping site location to a Sub-contractor location defined for the sub-contractor customer. Therefore, there is no decrease in the physical stock upon validating a sub-contracting delivery. However, the available stock is decremented.

The LST activity code must be active to be able to perform a subcontracting delivery. Then, a customer role must be assigned to the supplier as well as a delivery address related to a sub-contracting location. A sub-contracting shipment is used to replenish sub-contractors for whom material shortages have been reported during the operation they were assigned. A sub-contracting shipment is therefore not to be invoiced. The Invoice action is grayed out in this context. A Pro forma can however be created and associated with the goods.

Type: non-billable delivery

Non-billable deliveries include:

• service deliveries
  
• deliveries of items related to a task associated with a project in the context of project management. These can be products managed in stock subjected to a detailed allocation at the task level, or service products that are not managed in stock but delivered.

The category cannot be modified; it is determined by the chosen Delivery type.

The delivery number is used to identify the delivery in a unique fashion. This number is either assigned automatically or entered upon each delivery creation with respect to the setup of the Sequence number(s) associated to the chosen Delivery type.
If the delivery sequence number is set to automatic assignment then this field cannot be accessed and the number is assigned on creating the delivery.
Conversely, if the sequence number is set to manual assignment, the number can be entered manually. If it is not entered by the user, the system automatically assigns a delivery number according to the sequence number.

 Notes:

• If they not entered at the level of the delivery type, the sequence numbers taken into account are the ones specified in the function Sequence number assignment.
• If the company parameter SDHENDNBR - Final delivery sequence no. is set to 'Yes', a new delivery number is assigned upon validating the delivery. The former number is no longer displayed but it is saved in a dedicated field (TMPSDHNUM) in the table of deliveries.

The sales site is initialized by default by the sales site associated with the user.
It can only be accessed upon creating a direct delivery. In this case, the chosen site:

• must have been identified as a sales and storage site,
• must belong to the same legal company as the shipment site.

This number is initialized if the delivery is related to an order (traditional order or contract order). This information is not entered in the case of a multi-order delivery.

Code of the customer requesting the order, the direct delivery or the direct invoice. This code:

• must be managed in the customer table,
• must be of normal, miscellaneous or inter-company type,
• can be modified as long as no line has been entered on the document.

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 code for the bill-to customer, which is initialized by default with the customer code entered in the header.
This customer can be another customer chosen from the customer table.

It is possible to search a customer or several customer grouped under the same criteria by selecting 'Quick customer search'. A list of matching items is generated on tabulating to the next field.
For a more advanced search, all fields present in the block can be entered. The list of matches is narrowed down with each tabulation.

The shipment date is the date used to determine the date of the good issue. 
This is the stock actual posting date: it is used as posting date in the stock journal.

If the delivery comes from an order, the shipment date is initialized according to the value of parameter INISHIDAT - Shipment date initialization (chapter VEN, group SSD). It can be:

• the current date,
• or the planned shipment date of the order, if this date is not earlier than the current date, otherwise it is the current date which is used.

A delivery note cannot be validated with a shipment date greater than the current date.

In the case of an order delivery, if this date is changed, a message is displayed, proposing a new price list search when the user parameter SDHRECPRI - Order delivery price search (chapter VEN, SSD group) is set to 'Yes'. When it is set to ‘No’, the price of the order is kept. 

The delivery lead time is initialized by default:

• according to the ship-to customer record (in the case of a direct shipment)
• or by the lead time entered on the order. The latter can be modified and is used to recalculate the 'delivery date' with respect to the 'shipment date'.

The delivery date corresponds to the date on which the goods will be received by the customer and the ownership transfer will be made. The search of the tax rates to apply is based on this date.
It is calculated from the Shipment date to which the Delivery lead-time has been added. This date can be modified.
In the case of an order delivery, if this date is changed, a message is displayed, proposing a new price list search when the user parameter SDHRECPRI - Order delivery price search (chapter VEN, SSD group) is set to ‘Yes’. When it is set to ‘No’, the price of the order is kept.
If the calculated or entered delivery date corresponds to a non-working day defined in the customer delivery address, the delivery date is then automatically moved to the first working date following the initial delivery date.
If the calculated or entered delivery date corresponds to an unavailability period in the customer delivery address, a warning message signals it.

The 'loan return' date is initialized by the 'loan return' date defined in the order if it is a delivery coming from an order. Otherwise, it is not initialized and must be entered manually. This date is used if required, to invoice a loan delivery from the moment the 'loan date' is exceeded and the loaned goods have still not been returned by the customer. This date must be greater than or equal to the 'delivery date'.

This is corresponds to the currency of the order, delivery or invoice.
It is initialized by default with the bill-to customer currency and can be modified. In this case, it can only be modified in creation and duplication modes and is controlled in the currency table.

It is possible to choose the currency for the delivery transaction as well as to define (depending on the value of the 'Excl. tax and Incl. tax Prices' parameter - TC Chapter / INV/NOTATI group) if the prices are expressed excluding tax or including tax. When the delivery comes from an order, this information is automatically loaded and cannot be modified. When it is a direct delivery, this information is no longer modifiable once at least one delivery line is entered. It is inherited in this case from the invoiced customer information.

The value of this field (Ex-tax or Tax-incl.) is defined by the general parameter SALPRITYP - Price/Amount type (TC chapter, INV group).

When the general parameter NOTATI - Ex-tax and tax-incl. amount/price (TC chapter, INV group) is set to No you cannot modify this information.

The presence of this box is subject to the activity code WRH.
Movement warehouse, suggested by default for all the document lines.
It must be entered if it is defined as mandatory at the level of the entry transaction.
It is loaded in priority with the warehouse defined for the user. If it fails to be set up at user lever, it is initialized with the warehouse defined, by default, at site level for this type of movement.

This information is not accessible and is loaded depending on the context. The lines in the table are used to enter products, quantities, prices, discounts and charges... related to the delivery.

This non modifiable information specifies whether the order is of the inter-site or inter-company type.

• When the delivery concerns an 'inter-site' customer (site of the same company), it cannot be invoiced.
• When the delivery concerns an 'inter-company' customer (site of a different company), an invoice can be generated.

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.

This is the product description translated into the customer language. This description is the one that will be printed on the document. If the translation does not exist in the customer language, the un-translated product description is used. This description is also transferred to the next document.

The product record can be accessed from this field using a tunnel.

This is the description entered on the product record. This description is transferred from the sales invoice to the purchase invoice in case of inter-company invoicing. When the invoice stems from another document, the standard description is inherited from the source line.

This field displays the major version of the product.

The major version number can be accessed if the tracking of major versions is active at the level of the product setup (in the Management tab of the Product function, the Stock version field is set to 'Major').

If the preloading of versions is active at the product/customer level (in the Customers tab of the Product function, the Version preloading box is checked), or by default, at the product/sales level (in the Sales tab of the Product function, the Version preloading box is checked), then the last active major version is preloaded automatically. Otherwise, the last major version with the 'Stopped' status will be preloaded.

The picking of orders, open orders, picking ticket et subcontract shortages will lead to the transfer and control of version numbers on the delivery.

For automatic deliveries of orders and picking tickets, version numbers are transferred and the control on versions is applied to the delivery.

If the version is not correct, a message of information is displayed in the log file.

This field displays the minor version of the product.

The minor version number can only be accessed if the tracking of major and minor versions is active at the level of the product setup (in the Management tab of the Product function, the Stock version field is set to 'Major and minor').

If the preloading of versions is active at the product/customer level (in the Customers tab of the Product function, the Version preloading box is checked), or by default, at the product/sales level (in the Sales tab of the Product function, the Version preloading box is checked), then the last active minor version is preloaded automatically.

The picking of orders, open orders, picking ticket et subcontract shortages will lead to the transfer and control of version numbers on the delivery.

For automatic deliveries of orders and picking tickets, version numbers are transferred and the control on versions is applied to the delivery.

If the version is not correct, a message of information is displayed in the log file.

The sales unit is initialized by the sales unit defined in the Product-customer record, if it exists, if not, it will be initialized by the sales unit of the product. Entry of another unit is possible in a selection window. The suggested units, other than those mentioned previously, are the packing units for the product and the packing units defined in the Product-customer record. When necessary, and if you have been granted the appropriate authorizations, you can access the units table.

Once the line is entered, you can no longer modify the sales unit. You must delete the line and recreate it to be able to modify the unit.

It is the quantity ordered by the customer. It is expressed in sales units.

This is the conversion factor between the sales unit and the stock unit. This coefficient can be modified in certain cases. It can be edited if the sales unit of the product has been specified as 'editable', or if the chosen packing unit has also been specified as 'Editable' (See Product record). It cannot be edited if the unit used is a unit defined for the customer. If units are used where the factor is modifiable, it is necessary to define for the product concerned, only prices expressed in stock unit. In addition, if a basic price list has been defined for the sales unit, the modification of the conversion factor for the sales unit does not trigger a recalculation of the unit gross price.

 Once the line entered, it is no longer possible to modify the conversion factor. The line must be deleted and recreated so as to modify the factor.

This field indicates the product management unit in which are expressed:

• The stock
• The standard price
• The BOM link quantity, etc.

This information is always displayed, regardless of the transaction used. It cannot be modified.

Help common to the Order and Buyer plan functions.

Use this field to determine the gross and excluding tax unit price of the product. This price is expressed in order unit if the Unit field is declared as accessible at the time of entry in the transaction, if not, it is expressed in purchase unit.

When the main information for the line has been given, a price list search process is automatically carried out. The objective of this search is to recover:

• The gross price and the associated reason.
  If the order (or purchase) unit is different from that of the price list line:
  - The price list amount is converted if the value of the Unit conversion is set to 'Yes' at the Pricing parameters level. This conversion is based on the unit conversion coefficient table. If no conversion is set up between these units, the price list amounts are those that are considered by applying a 1 conversion rate.
  - The price list is not used if the value of the Unit conversion is set to 'No' at the Pricing parameters level The value of the gross price is set to '0'.
• The charges and discounts in percentages or in amounts to be applied to the line level as well as the associated reasons.

When the entered price is null, a message appears to request confirmation from the user.

In the Price field, you can use the Actions icon to:

• View and modify the Discount and Cost fields defined using the structure code associated with the supplier. The values contained in these fields come from the price list search and can be modified if the associated reason allows it.
• View the reasons associated with the price as well as the different discounts and charges fields
• View the price lists
• Re-initialize the price, as well as the discounts and costs, by requesting a new price list search.

The entry of other data on the line depends on the selected transaction. This is the case for example for the Site information, Quality control code, etc.

Inter-company specificities: Within the framework of an inter-site or inter-company order, if the inter-company price lists have been set up, they will be used in the same way as normal price lists. When the sales order is generated, the prices and the discounts calculated for the reciprocal sales order will be determined from the inter-company price lists or the normal price lists. In no case will the prices and discounts entered in the purchase order be transferred to the sales order. The prices between the sales and purchasing documents can change independently. The reconciliation is made at the time of invoicing.

Help common to the Sales and Purchase modules.

The displayed discount and cost columns are linked to the setup of the price lists structure code associated with the supplier in said supplier's record.
These columns can be initialized by means of the price lists (see the Sales pricing setup and Price list entry documentations).

Access to these columns can depend on the setup of the reasons associated with the price lists as well as the value of the reason given to the

• UPDPRISAL - Default price reason - base parameter (VEN chapter, PRI group), for sales,
• UPDPRIPUR - Default price reason - base parameter (ACH chapter, PRI group), for purchases.

These discounts or costs are defined in amount or in percentage and they are applied with a totaling or cascading method to the gross price to determine the net price of the document line.

From the Actions icon, you can:

• View the reasons associated with the price as well as the different discounts and costs fields
• Modify, if necessary, the reasons allocated to each column.

This is the unitary net price for the receipt line calculated from the gross price affected by any discounts and charges. This information cannot be accessed.
From this field, use the Actions icon to:

• View the reasons associated with the price as well as the different discounts and charges fields
• View the list of the last 10 order prices
• View the price lists
• Have a detailed explanation available describing how the net price is obtained

If the entered price is null, a message appears to request confirmation. However, this message is not displayed for the components of a BOM, for free items and for deliveries not to be invoiced.

A process for the Free items is triggered at the end of the delivery line. This processing generates all the free product lines (Gross price and discounts set to 0). If the value of the FOCPRI - Free product valuation parameter (VEN chapter, PRI group) is ‘Yes’, a price list search is triggered for the free item to assign it a gross price. The assigned price is compensated for, either by a line discount in percentage or a line discount in amount (according to the order of discounts) to obtain a zero net price.

When you click Create to save the delivery, and based on the value of the GRPPRI - Grouped price lists parameter, a message can be displayed, suggesting that a new price list search is run to determine the specificities globally linked to the delivery. At the end of the processing, the following can be generated on some product lines:

• a new gross price or new discounts or new charges for the line,
• free products that are not associated with a specific line.

The 'cost price' is populated by default with the valuation of the product chosen for the margin calculation (see the valuation methods defined for the Product-Site record) at the time of the creation of the document line and is expressed in sales unit. The various possible choices for the cost price valuation are: Standard price, Revised standard price, Last price, Weighed average price, FIFO price, Lot average price and LIFO price. If the valuation method happened to return a zero value, a default value is used by specifying another valuation method contained in the list previously described. This value is stored in the "document" line.

It is possible to preload this information according to the document transaction used. Still, during the following events, the entered value is systematically replaced by the value originating from the setup of the valuation method for the product, except if this setup determines a null value (in which case the change is saved):

• Turning a quote into an order
• Delivering an order 
• Validating a delivery
• Invoicing an order The cost price is fixed when invoicing a delivery

In quote management, the 'lot average price' always returns a null value. A default value is used. During the delivery validation, the 'Lot average price' is used to recalculate the margin and obtain a real margin depending on the shipped lot(s).

This field displays the margin in sales unit, calculated based on the difference between the net price and the cost price.

During the gross margin calculation, a control can be carried out to verify that this margin is not below the minimum threshold defined in the Sales tab in the Product record. This control can be blocked according to the value attributed to the user parameter SDACLOK - Non block. control price, prof, qty (VEN chapter, AUZ group). The calculation carried out to control the margin rate is the following:

(Ex-tax price - Cost price) / Total ex-tax price) *100 >= percentage of the minimum margin.

No control is carried out on nonbillable deliveries.

This field indicates the tax level applied to the selected product.

The tax level, when crossed with the document tax rule, is used to determine the tax rate to be applied on the document line.

There are three tax levels for a document line.

The first level is compulsory and it corresponds to the VAT.

The other two levels concern additional and special taxes that can be submitted to the VAT or not, and be applied to the ex-tax basis or any other evaluated formula.

The tax levels for the document line will be loaded by default with the values associated with the product record (Accounting tab). These values can be modified depending on the transaction. You can also, if the user's authorizations permit it, access the tax level management.

The parameter CTLTAX - Tax codes control (VEN chapter, VAT group) is used to control that the tax codes linked to the tax level are consistent. Using this control, the system checks that the tax level:

• is specified,
• is activated,
• has a legislation and company group consistent with the ones of the document.

Enter the code to use in order to override the default SST tax code from the product or invoice element. This tax code is recognized by Sage Sales Tax and is used to identify line types for tax purposes. This field is available only if the LTA - Local taxing activity code is activated, and the USATAX - Tax system user parameter is set to Yes.

For invoicing elements designated as the SST document discount for a company, you cannot remove the SST tax code value on the document.

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).

• 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:

• 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:

• 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.

• 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 presence of this field is subject to the WRH activity code.
It defaults to the value of the warehouse specified in the header.

• This field can be modified if it is defined as available for entry at the level of the entry transaction.
  When this field is entered, it is used as a filter for stock detail line selection and cannot be modified.
  When this field is not entered, the warehouse defined by default for this type of movement in the product-site record is used as the selection filter.
• It cannot be modified when the entry transaction is set up as single-warehouse managed. The header warehouse is then mandatory and the warehouse cannot be entered either on the document lines or on the stock detail lines.
  To manage multiple warehouses on the lines, the entry must be set up at the entry transaction level. The selection of a single product line distributed over multiple warehouses is available by clicking Enter detailed quantities from the Actions icon.
  If a single product line is distributed over multiple warehouses, the corresponding fields display the '$' character.

The warehouse entered on the line has priority over the warehouse entered in the header.

If the product is managed by lot then, on manual creation of the delivery line or when the stock to be issued has not been determined, it possible to enter a lot existing in the 'shipment site'.
A selection window accessed by right click on the field is used to select a lot number. 
It is also possible to enter a lot number which does not exist in stocks.
A message then informs the user that no lot exists. This alternative is provided so it is possible to record a lot number that has never been entered even though the goods are physically available. This method can only be applied when negative stock is authorized for the product and when the delivery transaction is set up with no stock determination. In the case of a delivery transaction with stock determination, this lot is only considered if the product if in complete shortage (the detailed allocation algorithm will attempt to allocate stock first).

Indicates the sub-lot to be issued.

It is not necessary to enter it in the following cases:

• the issue is a multi-lot one
• all characteristics of the stock to be issued are not entered (lot, sub-lot, serial no., location)

If the product is managed with serial numbers, only this number is necessary to determine the stock to issue.
If this is not the case, the lot, sub-lot and location (depending on the management method for the product) are necessary.
There is no selection window for this field. The selection window is available on the lot field and makes it possible to choose the requested lot and sub-lot. When the lot is selected, the sub-lot it instantly initialized. Otherwise, it is also possible to enter a sub-lot number which does not exist. An information message will report it. Same remarks as for the lot number in this context.

This field is used to enter the first serial number (Start) to issue. The last serial number (End) will be automatically calculated.

• It is not necessary to enter the start serial number when the serial numbers to issue are not in a row.
• If the product is managed with serial numbers, only this number is necessary to determine the stock to issue.
• If this is not the case, the lot, sub-lot and location (depending on the management method for the product) are necessary.

This is the serial number of the product.

If the product is managed by location at the 'shipment site' then, on manual creation of the delivery line or when the stock to be issued has not been determined, it possible to enter a location existing in the 'shipment site'. A selection window accessed by right click on the field is used to select a location.

This field is subject to the LPN - License plate no. management activity code.
It refers to the license plate number of the container impacted by the issue.

Irrespective of the product used, there is the possibility, during manual creation of the delivery line or when the stock to be issued has not been determined, to enter a status for the stock to be issued.
A selection window accessed by right click on the field is used to select any status that has been defined.

Enter a free description that will be registered in all the stock transactions associated with the delivery line.
This description is also accessible from the stock issue detail window. If it has been modified by this function, it will be automatically recovered and registered on the shipment line in this field.

It is the number of products, expressed in sales unit, that the packaging can contain.
This value is initialized by default with the quantity entered in the product-site record.

The weight unit.

The weight is calculated by conversion of the sales unit into stock unit and considering the conversion coefficient between these two units if this has been modified. It is loaded from the product.

Use this field to specify the consumption place for the carrier or to define an address complement.

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line.

The analytical dimensions are initialized according to the setup of Default dimensions, associated with the management of delivery lines. Depending on the setup, they remain available for modification.
When an analytical dimension is used for project management tracking, any modification of the project code on the document line leads to the dimension code being reset based on the Default dimensions setup.

This field contains the quantity ordered by the customer and expressed in sales unit. It is initialized by default with the quantity left to return and remains modifiable. A quantity comprised between 0 and the quantity that left to return may be entered.

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.

This is the journal number at the origin of the requirement.

This column is only displayed if the POS - Delivery validation by line activity code is set to 'Yes' and if the entry transaction authorizes the display of the delivery status. When this activity code is set to 'Yes', the stock update applies to the delivery line when the line is validated. During the validation processing, some lines may not be validated due to errors or conflicts when accessing the updated tables, for example.

This check box indicates if the line is validated or not.

This field specifies the tax excl. result that integrates the various elements of the selected products.
This information appears when printing report BONLIV.
 The detail of the calculation is stored in tables SVCRVAT andSVCRFOOT.

This field indicates the tax incl. total, which includes:

• the various invoicing elements of the selected products,
• the tax calculation by tax basis.

This information appear upon printing of the BONLIV report.
The detail of the tax incl. calculation is obtained by right click on the total amount.
 The detail of the calculation is stored in the SVCRVAT and SVCRFOOT tables.

In order to access the 'Incl. tax Valuation' screen, click on the incl. tax field.

This field cannot be entered. It is used to inquire whether pick tickets have been printed.

This field cannot be entered. It is used to inquire whether packing slips have been printed.

This check box only displays when the PDV - Delivery validation by line activity code is set to 'Yes' and when the entry transaction authorizes the display of the delivery status.

This check box cannot be accessed. It is automatically selected when the delivery is partially validated, that is to say when one or multiple delivery lines could not be validated. You can identify the relevant lines by referring to:

• The log file that displays at the end of the validation processing;
• The Validated column of each line.

This flag cannot be accessed. It is automatically selected upon validation of the delivery.

This field indicates the delivery status in case of delivery return. The values of this field are as follows:

Not returned

This value indicates that no product has been returned.

Returned

This value indicates that the products of the delivery have all been returned.

Partially returned

This value indicates that some products of the delivery have been returned.

This status is updated automatically when creating a delivery return.

This field indicates if the delivery has been invoiced.
If the delivery has been invoiced, the invoice number is specified next to this check box. Based on your user authorizations, you may directly jump to the invoice (only one invoice can be used for invoicing a delivery).

Invoice number linked to the delivery.