Deliveries

• Shipment site (field STOFCY)

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.

• Type (field SDHTYP)

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.

Loan delivery type

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' tab 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' tab 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' tab of the product record) and be managed by location ('Management' tab 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 can only be carried out using the Invoice button present in the delivery. In this case, only non-returned goods will be invoiced. The physical issue of products will be performed on validating the invoice. A loan shipment can however lead to a Pro forma.

Sub-contract delivery type

A sub-contract delivery is never attached to an order. It is always a direct shipment. It will therefore be appropriate for a shipment of this type to specify that it is a shipment sent to the subcontractor. 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 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.

In order to be able to perform a sub-contracting shipment, it is necessary that the activity code LST has been activated. 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 button is grayed out in this context. A Pro forma can however be created and associated with the goods.

• Delivery no. (field SDHNUM)

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.

• Sales site (field SALFCY)

• Order no. (field SOHNUM)

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.

• Ship-to (field BPCORD)

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.

• Address (field BPAADD)

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

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

• Bill-to customer (field BPCINV)

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.

• field BPINAM

• field WSDHCAT

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

• Shipment (field SHIDAT)

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

• Delivery lead time (field DAYLTI)

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

• Delivery (field DLVDAT)

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.

• Loan return (field LNDRTNDAT)

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

• Currency (field CUR)

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.

• Price type (field PRITYP)

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.

• Warehouse (field WRHE)

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.

• Intersite (field BETFCY)

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.

• Intercompany (field BETCPY)

• Product (field ITMREF)

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.

• Description (field ITMDES)

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.

• Standard description (field ITMDES1)

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.

• Major version (field ECCVALMAJ)

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.

• Minor version (field ECCVALMIN)

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.

• SAL (field SAU)

The sales unit is initialized by the sales unit defined in the Product-customer record, if it exists, otherwise it will be initialized by the sales unit of the product. It is possible to enter another unit using a selection window. The units proposed 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 the user has the appropriate authorizations, it is possible to access the units table.

Once the line is entered, it is no longer possible to modify the sales unit. It is necessary to delete the line and to recreate it to modify the unit.

• Delivered qty. (field QTY)

From the quantity field, the contextual button enables the user to inquire the stock by site.
It is mandatory that the shipped quantity is entered. A warning message is displayed if the quantity entered is less than the minimum quantity defined in the product record. A warning message may also appear if the quantity entered is greater than the maximum quantity entered in the product record. These messages can be blocking according to the value of the SDACLOK - Price, margin, qty non blocking control (VEN chapter, AUZ group) user parameter.

When the shipped quantity is entered a price list search process is automatically carried out. The purpose of this search is to recover:

• the gross price as well as the associated reason,
• the charges and discounts in percentages or in amounts to be applied to the line level as well as the associated reasons,
• any free product(s).

The price list search process can be triggered in different ways depending on the product type entered.

In effect, if the entered product is of the type 'Normal', the search process is automatically triggered.

When the entered product is of the type 'Kit parent product' or 'BOM parent product, an initial price list search is triggered for the parent product ('Normal' type), then before triggering the price list search for the components, a read of the BOM file is carried out in order to identify whether different BOM codes of the 'commercial' type exist, in which case they are displayed in a window. If the product has only a single BOM code, it will be taken into account automatically.

After choosing the BOM code, different cases can occur according to the construction of the product BOM:

• Each component of the 'Normal' type is selected automatically.
   
   It is automatically replaced by the substitute product if the latter has been entered in the Product record and if the document date is superior or equal to the substitution date.
  For the other types of components entered below, when a substitute product is used, the original product description is displayed at the level of the components selection window.
   
• For each component of the 'Normal' (with formula) type, a window opens automatically displaying the set of products coming from the selection formula. If a 'Normal' component has also be recorded in the same sequence, this component is also displayed in the list. By default, it is automatically selected but it is still possible to de-select it.. Its quantity cannot be modified.
  It is possible to select one or several components from the selection. The buttons [Include all] and [Exclude all] are available for this purpose. As soon as no component is selected, the [Criteria] button becomes available so as to narrow the selection down when the number of table lines is too important (the number of lines depends on the number of lines remaining to be inserted in the document).
• For each component of the type 'Variant', a window opens presenting the set of variants listed at the BOM level or coming from a selection. The user must choose one.
• For each component of the type 'Option', the option is suggested and the user must accept it or refuse it. When several options are possible for a same BOM level, a window opens for the user to select one or more options or to refuse all of them.
• For each component of the type 'Multiple Option', a window opens presenting the set of components listed at the BOM level or coming from a selection formula. You can select several ones or refuse all. The buttons [Include all] and [Exclude all] are available for this purpose. As soon as no component is selected, the [Criteria] button becomes available so as to narrow the selection down when the number of table lines is too important.

The lines corresponding to the different BOM components are then generated:

• If the product is of the type 'Kit parent product', all the component lines are automatically generated. These lines become completely dependent on the parent component. They appear on the screen but are not accessible. The component quantity is automatically calculated from that of the parent product. If the parent product quantity is modified, the quantities of all the components are automatically recalculated. If the parent product is deleted, all the components are automatically deleted.
• If the product is of the 'BOM parent product' type, all the component lines are proposed and they are modifiable (except the sales unit). They are independent with respect to the parent product. If the parent product is modified or deleted, a question is posed over whether or not to transfer the modification or deletion to the components.

In both cases, a price list search for the component type is then automatically triggered and for each delivery line generated, a value is assigned to the type of line:

• 'Kit option' or 'BOM option' for a component of type 'Option',
• 'Kit Variant' or 'BOM Variant' for a 'Variant' type component,
• 'Kit component' or 'BOM component' for a component of 'Normal' type.

Certain price list controls are carried out on exiting this price list process:

• if the price is defined tax included, the tax-ex price is calculated.
• control on the calculated net price: if the calculated net price is less than the threshold price stored in the product a warning message is displayed.
• control on the profit margin: if the percentage margin is less than the minimum margin percentage stored in the product record, a warning message appears.

These different messages can be blocking according to the value given to the SDACLOK - Price, margin, qty non blocking control user parameter.

If the shipment comes from an order and an allocated quantity remains and a shortage on the order, the fact of increasing the shipped quantity will consume the allocations then the shortages still present in the order.

When the delivery line is created and the shipped quantity is then modified, the 'stock' detail window then automatically opens at the line end to give the user the choice of stock lines to be modified. The stock detail window does not open in only one case. If the delivery line is only associated with one stock line and the shipped quantity is decremented, the system automatically reduces the recorded quantity on the stock line, no intervention from the user required.

• SAL-STK conv. (field SAUSTUCOE)

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.

• STK (field STU)

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.

• Gross price (field GROPRI)

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.

• field DISCRGVAL1

Discounts and charges columns are displayed.
They depend on the setup of the Price list structure code associated with the supplier in the supplier record (see documentation Price list structure).

They can be initialized by the use of the price lists (see the Price list setups and Price list entry documentations). Access to these columns can depend on the setups of the reasons associated with the price lists as well as the value of the reason given to the UPDPRISAL setup for Sales and to the UPDPRIPUR setup for Purchase.

These discounts or charges 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.

The contextual button is used to:

• view the reasons associated with the price as well as the different discounts and charges fields,
• modify, if necessary, the reasons allocated to each column.

• Net price (field NETPRI)

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.

When the entered price is null, a message is displayed asking for confirmation. This message is not displayed for the components of a BOM, for free items and for nonbillable deliveries.

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 set to 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 record 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.

• Cost price (field CPRPRI)

The 'cost price' is loaded by default by 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 pre-load this information as a function of the document transaction used. Still, during the following events, the entered value is systematically replaced by the value that comes 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).

• Margin (field PFM)

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.

• Tax level 1 (field VACITM1)

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.

• SST tax code (field SSTCOD)

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

• Project (field DPJT)

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 (chapter TC - group MIS) 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:
  - for projects, the project counter number,
  - the concatenated project sequence number with the budget batch code, in the case of a project budget batch,
  - the concatenated project sequence number with the number of tasks, in the case of 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.

In selection, there are two possibilities:

• The Selection contextual menus (CRM projects, Projects, Budget batch or projects only linked to the BP) are used to select a project in a selection list.
• The CRM projects and Projects contextual menus are used to directly access the chosen management function and then carry out a selection or create a 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 transferred to all lines.
• 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:
- In case lines were impacted, a dialog box opens and suggests to recalculate the prices and discounts. The answer Yes causes a price list search, based on the new project code, for all the lines of the document.
- In the event the project code were modified in the line, this same price list searching system is applied 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.

• Warehouse (field WRH)

The presence of this field is subject to the activity code WRH.
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 quantites 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.

• Lot (field LOT)

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

• Sublot (field SLO)

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.

• Starting serial number (field SERNUM)

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.

• Ending serial number (field SERNUMF)

This field contains the end serial number.

• Identifier 2 (field CTRNUM)

• Identifier 1 (field PALNUM)

• Location (field LOC)

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.

• Status (field STA)

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.

• Movement description (field MVTDES)

A free description is entered in this field that will be registered in all the stock transactions associated with the shipment 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.

• Packaging (field PCK)

This code is controlled in the packaging table and initialized by default by the corresponding code from the product-site record. 
It indicates the number of products, expressed in sales units, that the package can contain. The packaging code comes from the Product-Site record depending on the sales unit chosen. In the case of a line creation, if the unit chosen does not correspond to the sales unit of the product or to the customer sales unit, the packaging code and the capacity are not initialized. In this case, it is then necessary to manually enter them. This information remains modifiable and is used upon preparation or shipment of the product to carry out the packaging.
Upon declared packing, this code is specified only if it is present in the original document Deliveries or Picking tickets.
If granted the proper authorizations, the user can access the packaging record.

• Packaging capacity (field PCKCAP)

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

• WGT (field XWEU)

The weight unit.

• Unit weight (field UNTWEI)

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.

• Location reference (field USEPLC)

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.

• field CCE1

Based on the setup, the analytical dimensions can be modified since they are initialized in accordance with the setup of the default dimensions.

• Return quantity (field RTNQTY)

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.

• Order no. (field XSOHNUM)

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.

• Original document (field VCRNUMORI)

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

• Excluding tax (field DLVNOT)

• Excluding tax (field DLVINVNOT)

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.

• Including tax (field DLVINVATI)

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 is displayed when printing the report BONLIV.
The detail of the tax incl. calculation is obtained by right-click on the total amount.
 The calculation detail is stored in the tables SVCRVAT and SVCRFOOT.

To access the screen 'Incl. tax Valuation', click on the link of field Including Tax.

• Printed (field PRNNPR)

• Printed (field PRNNDE)

• Posted (field CFMFLG)

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

• Return status (field RTNSTA)

As of update 8.0.0:

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.

• Invoiced (field INVFLG)

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 no. (field SIHNUM)

Invoice number linked to the delivery.

• Pay-by (field BPCPYR)

The Pay-by BP is initialized by default by the pay-by BP associated with the sold-to customer in the latter's record in the case of a direct delivery. Otherwise, the pay-by BP of the original order is used.

It is possible to:   

• modify the pay-by BP if necessary,
• select a BP or access BP management by tunnel if user authorizations allow it.

 Special features linked to the inter-company: in the case of an inter-company order automatically generated from a purchase order, the pay-by BP corresponds to the customer associated with the invoicing site entered in the purchase order. It cannot be modified in this context.

• Group customer (field BPCGRU)

The group customer is initialized by the group customer code associated to the sold-to customer in the latter's record. This information is used for the generation of statistics. It is also involved in the grouping of invoices during the automatic generation of invoices. There is the possibility to modify the group customer if necessary.
From this field, it is possible to select a customer or access customer management by tunnel if the user's authorizations allow it.

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.

• Route no. (field DRN)

This code, which is controlled by a local menu, is used to generate the delivery notes according to the route code defining for example, a geographic zone. This information is defined by the customer delivery address.

• Delivery mode (field MDL)

This code is used to define the information related to the transport and delivery. It is managed in the Delivery Method table. It is initialized from the ship-to customer.

• Carrier (field BPTNUM)

This field indicates the code that identifies the Carrier liable for the transportation of the goods.

This information comes from the order or from the customer delivery address. The carrier, the weight and the volume as well as the delivery address are used to determine, when managed, the carrier price list whether or not it is invoiced to the customer. The invoice footer, specified in general parameter FRENUM - Carrier invoice elements (chapter VEN, group INV) contains the invoiced delivery charge. Invoicing the delivery charge depends on the delivery charge invoicing method associated to the customer and, regarding the freight application threshold method, from the thresholds specified on the carrier record. When the carrier, weight or volume data are changed, a message suggests to search for the carrier pricelist.

• When the carrier, weight or volume data are changed, a message suggests to search for the carrier pricelist.
  - If the answer is 'No', the amount of the freight remains the amount entered on the order.
  - If the answer is 'Yes' and the new carrier is not subject to pricelist management, then the freight amount entered on the order is maintained.
  - If the answer is 'Yes' and the new carrier is subject to pricelist management, then the freight amount is recalculated according to the carrier pricelist.
• When the entered carrier data is subject to pricelist management and a transport amount is entered on the order, a message suggests to replace the transport amount by the search result on the carrier pricelist.
  - If the answer is 'No', the transport amount on the order is recovered on the delivery.
  - If the answer is 'Yes', the transport amount is recalculated according to the pricelist.

• Proforma no. (field PRFNUM)

This is the number of the pro forma invoice associated with the document. The generated pro forma number is displayed if a pro forma invoice is created from this document. A tunnel then makes is possible to access the invoice.

• Incoterm (field EECICT)

The Incoterm codes, set by the International Chamber of Commerce, seek to standardize the terms the most used in the international commerce by defining the respective responsibilities of the seller and the buyer agreed upon on establishement of the sales contract by a unique word similarly understood throughout the world.

The Incoterm code, controlled in Incoterm table is used in the INTRASTAT file (Exchange of goods declaration). It can also be used to define the price lists.

When creating a quote, an order, a delivery or an invoice, the Incoterm code is initialized to the Incoterm code defined by default for the ship-to customer.

This Incoterm code can be modified. Concerning the quotes and orders, the Incoterm code is unique for the document as a whole. When transforming a document, the Incoterm code is passed on to the child document.

 The code and the Incoterm city can also be accessed via the menu Options / Informations douanières.

• Incoterm town (field ICTCTY)

It is the city associated to some types of incoterm. For instance: FOB Le Havre. A selection window is used to choose a city listed in the system. It is however possible to enter a city that is not listed.

• BOL number (field BOLNUM)

As of update 8.0.0:

This field displays the bill of lading number for this delivery.

• Trailer/Seal number (field TRAILER)

As of update 8.0.0:

This field displays the trailer or seal number from the bill of lading.

• SCAC code (field SCAC)

Update 8.0.0 and higher:

This field displays the SCAC code (Standard Carrier Alpha Code) from the bill of lading. This field is only available if the KUS - Localization USA activity code and the USABOL - Bill of Lading parameter (LOC chapter, USA group) are set to "Yes".

The SCAC code is a unique code used to identify transportation companies.

• PRO number (field PRONUM)

Update 8.0.0 and higher:

This field displays the PRO number from the bill of lading. This field is only available if the KUS - Localization USA activity code and the USABOL - Bill of Lading parameter (LOC chapter, USA group) are set to "Yes".

The PRO number is a tracking number. It is used by some carriers to track the progress of each shipment.

• Payment term (field PTE)

Code of the payment condition. This code defined the payment code as well as the distribution rules of the various prepayments and open items.
It is initialized by the bill-to BP and controlled in the table of payment conditions.
Only a payment method consistent with the legislation and company group of the document site can be entered.
The general principles linked to the multi-legislation setup are detailed here.

It is possible to simulate a distribution using the button [Simul]. As far as order management goes, in creation mode the prepayments corresponding to the payment condition are automatically created. The 'payment condition' code can be modified as long as no prepayment request has been made and the order has not been invoiced. The modification leads to the deletion of existing prepayments and then to the creation of prepayments linked to the new payment condition.

• Settlement discount (field DEP)

This information is entered in the quote and it is initialized by the discount code in the bill-to customer. It makes it possible to determine a series of early discount rates or late charges to be applied depending on whether the payment is early or late with respect to the due date.
Only a discount code consistent with the legislation and company group of the document site can be entered.
The general principles linked to the multi-legislation setup are detailed here.

If the quote involves a prospect, this information is not initialized.

• Tax rule (field VACBPR)

This information is used to indicate the tax rule for the document. This code is controlled in the tax rule table and is initialized by the corresponding code in the BP record. It can be modified.
This information is mandatory and remains accessible provided the delivery has not been confirmed.
Only a tax rule with a legislation and group that are consistent with those of the document can be entered.
The general principles linked to the multi-legislation setup are detailed here.

• Entity/Use (field SSTENTCOD)

• Sales rep (field REP)

The sales reps are initialized by the customer sales reps, then by those of the ship-to customer, if no sales rep exists in the customer record. In the case of a prospect, the representatives of the prospect are not considered. These sales rep codes are copied to the document lines. If a representative is modified in the document header upon creation or when lines exist in the document, the system suggests to copy the modification to all the lines that already exist.

• Project (field PJT)

• Net weight (field NETWEI)

Net weight of the delivery. This is the sum of the unit weights of the products (of the sales unit) multiplied by the quantities in SAL of the various lines constituting the delivery. This weight is automatically calculated but it can be modified.

The weight unit is defined by the weight unit of the first product in the delivery. If other products in the delivery do not have the same weight unit, the weight of these products will then be converted to the weight unit from the first line in the delivery note. The conversion between these units is applied as defined in the table Unit conversion. The weight unit does however remain modifiable.

• field WEU

The weight unit.

• Gross weight (field GROWEI)

Indicates the net weight of the delivery (total weight of the different delivery lines) added to the weight of the various types of packaging used. This weight is initialized by the net weight, but it can be modified. The load preparation function impacts on the gross weight with the weight of the packaging because the parcels used can be assigned by this function.

• Volume (field VOL)

This is the total volume of the packages of the document. The volume is automatically calculated by the load preparation function, but it can be modified.

The volume unit is defined by the volume unit of the first packaging from the delivery lines. If other products in the delivery do not have the same volume unit, the volume of the packaging for these products is converted to the volume unit for the first packaging in the delivery note. The conversion between these units is applied as defined in the table Unit conversion. The volume unit does however remain modifiable.

• field VOU

Code of the unit in which the package volume is given.
This unit has already been defined in the Units table.

• No. of packages (field PACNBR)

This concerns the total number of packages in the delivery. This information is automatically calculated by the packaging function, but can still be modified.

• Description (field SHO)

This is the title of the invoicing element.

• % or amount (field INVDTAAMT)

The values relate to the invoicing footer. This information can directly come from the setup of invoicing footer elements, from the record of the given customer or from the selected order.
  See documentation of Invoicing elements for further information.
The footer values can be modified. The ex-tax and tax-incl. amounts of the document are directly impacted by these values.

 If a delivery is modified by deleting an order or one or several lines from an order, the amounts of the invoicing elements are not re-calculated and so deleted lines or orders are not taken into account: the invoicing elements related to these orders or lines are not taken from this modified delivery.

• field INVDTATYP

The system specifies whether the invoicing element is a percentage or a tax excl. or tax incl. amount.

• SST tax code (field SFISSTCOD)

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

• Registration (field LICPLATE)

License plate of the vehicle carrying goods.

• Trailer license plate (field TRLLICPLAT)

Enter the trailer license plate.

• Departure date (field DPEDAT)

• Departure time (field ETD)

Delivery departure time.

• Arrival date (field ARVDAT)

Displays the arrival date for this delivery or return.

• Arrival time (field ETA)

Delivery arrival time.

• Location (field BPCLOC)

This information can only be entered in case of a shipment of sub-contractor type and, in this case, it is mandatory. It corresponds to the sub-contractor location that must be reordered in case of sub-contractor shortages. This location is initialized by default by the sub-contractor location defined in the ship-to customer record, then by the location defined in the supplier record if the location is not entered in the shipment address (on the condition that the location specified in the supplier exists in the shipment site). This location can however be modified from the moment the chosen location is of the sub-contractor type and belongs to the shipment site.

• Transaction group (field TRSFAM)

Movement group, initialized by the movement group of the transaction being used.

• Dimension type (field DIE)

This table is used to enter or view the dimension types, depending on the setups of the delivery entry transaction.

• Description (field NAMDIE)

This field repeats the title of the dimension type.

• Dimension (field CCE)

Based on the setup, the analytical dimensions can be modified since they are initialized in accordance with the setup of the default dimensions.

• Global document (field GLBDOC)

A global document refers to a shipment where the final delivery details (customer sites and quantities) are not known at departure time.

For instance: A company sells baked goods and delivers them to several customers' sites. The truck leaves with 1,000 units of baked goods, but it is not know how many will be delivered to each customer site. When all the deliveries are complete, the detail/normal shipping note is created and linked to the global document.

If the current record corresponds to the example below, you must select the Global document check box to link the record to the final transport and deactivate those fields that are linked to the global transport.

Otherwise, do not select the Global document check box, to link the record to the global document.

• Global document type (field GLBDOCTYP)

• Global document no. (field GLBDOCNUM)

• Global document date (field GLBDOCDAT)

This field displays the date for Global document.

• Manual document (field MANDOC)

If the web service is down, the transportation note must be communicated using a paper document including the paper document number and the internal system number. This communication must be done directly in the AT portal.

This field must contain a slash character (/) separating the sequential number specific to the series (on the left) and the sequential number itself (on the right). This is needed for all transportation notes for manual documents.

• AT code (field ATDTCOD)

This field displays the AT code for the Transportation note returned by the tax authority.

• Company name (field BPRNAM)

Business partner name.

• Address (field BPAADD)

• Country (field CRY)

This code is used to identify amongst other things, the Country of a BP.
This is important information, associated with a number of characteristics useful for performing controls on other linked information, in particular:

• the telephone number format,
• the format of the number used to identify a company or activity (SIRET, SIC) and whether the entry is mandatory,
• the postal code format of the town and also the code of the geographic subdivision, and whether their entry is mandatory,
• whether the VAT number of this community is mandatory,
• the Bank ID code format.

• field CRYNAM

Name of the country used in the addresses and in all the documents where the country code is entered.

• field BPAADDLIG

This table lists the various address lines. The formats of the title and of the entry are defined in the country table.

• Postal code (field POSCOD)

The postal code, whose entry format is defined in the Country table, is used to define the town/city and the geographical subdivision if it is defined for the country.
When the postal code is changed the city/town corresponding to the new code is automatically displayed. The principle is the same for the geographical subdivision if it is present for the country. 
It is also possible to manually enter the town/city name. If the town/city is already defined, the associated postal code is automatically displayed.

The control of this information and its mandatory nature depend on the setup performed in the country management. In order for the control to be applied, the POSCOD - Nonexistent postal code alert parameter (SUP chapter, INT group) must also be set to "Yes".

Specific cases:

- for ANDORRA, indicate 99130
- for MONACO, indicate 99138
- for the other overseas countries, indicate the INSEE code of the country or 99999 if not known.

• City (field CTY)

The city automatically proposed is the one associated with the postal code previously indicated. It is also possible to manually enter the name of a town/city:

• if the town/city is already defined, the associated postal code is automatically displayed, 
•  if the city does not exist and the postal code control has been set up in the Country record, a warning message is displayed but the continuation of the entry is authorized. In addition, the CTY - Nonexistent city alert parameter (SUP chapter, INT group) needs to have the value "Yes" for this control to apply.
• if the city does not exist and the postal code is not entered, a blocking message is displayed when the postal code is set up as mandatory for the country.

Notes:

• Its format is defined in the Country record setup.
• Depending on this setup, the entered town/city can automatically be converted into uppercase after it has been entered.
• In order to make selections easier without taking into account the format (accented characters/uppercase letters/lowercase letters), the selection window available on this field proposes a column dedicated to the search, where the names of the towns/cities are displayed in uppercase. The control which is carried out is case-insensitive since it is carried out with respect to the town/city name stored in uppercase.

• field ITINERAIRE

Click this icon to open a mapping site and locate the entered address.

• field SAT

This field contains the geographical SDL TEST subdivision corresponding to definition of the postal address. For example, a 'department' for France, and a state for the United-States.

The description of the geographic subdivision, as well as the control on the information entry, are defined in theCountries setup.

This field is automatically loaded after the postal code and town/city have been entered, based on the Postal codes setup.
If the field is controlled, the control is carried out according to the Geographical subdivision table.

• Site tax ID no. (field CRN)

The SIRET number of the site associated with the invoice customer is displayed if it has been entered on the BP record.
You can only modify this number when the invoice customer is a Miscellaneous one. The entered number must be compliant with the format defined on the Country record.

• Person to contact (field CNTNAM)

Contact number.

• EU VAT no. (field EECNUMX)

• Address validation (field VALADR)

Click on this button to send the entered address to the Sage Sales Tax (SST) address validation service. It is also possible to send the entered address by clicking on the [OK] button.

• If the address is found, the "Validated" checkbox is automatically checked.
• If the address is not found, the "Validated" checkbox is unchecked and cannot be accessed.

• This field is only available when the activity code Local tax (LTA) is active.
• The validation service of SST addresses is defined in the parameters related to Sage Sales Tax.

• Validated (field ADRVAL)

This box is checked automatically if the address is processed by the validation service of Sage Sales Tax (SST) addresses when the "Address validation" box is checked. The box is not checked and cannot be accessed if the address is not found.

• This field is only available when the activity code Local tax (LTA) is active.
• The validation service of SST addresses is defined in the parameters related to Sage Sales Tax