Quotes

• Sales site (field SALFCY)

The sales site is loaded by the default sales site associated to the user’s Function profile. The sales site can be modified (as long as no line has been entered on the document) provided it has been chosen from the list of sales sites authorized to the user.

• Quote type (field SQHTYP)

This field is loaded automatically with the quote type defined in the SQHTYP - Quote type parameter (VEN chapter, QUO group).

Authorized quote types are those corresponding to the site and group legislation defined in the setup function Quote types (GESTSQ).

• Quote no. (field SQHNUM)

The quote number allows the quote to be identified in a unique way. This number is automatically assigned or entered upon each creation of a quote following the counter parameterization defined for the quotes.

If the quote counter is defined with automatic allocation, the quote number field is not accessible and the counter is assigned to the quote creation. Conversely, if the quote 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 a quote number according to the counter.

• Revision (field REVNUM)

This field cannot be entered. It is only loaded when quote revisions are managed (SALREV - Revision management parameter (VEN chapter, QUO group)). It displays the last revision number created for the quote.

When you modify a quote, the original values (before modification) are saved in the history of revisions and the revision number is incremented:

• Automatically when the SALREVQ - Revision management parameter is set to: Managed automatically,
• and you answer Yes to the message asking you to confirm if a revision must be created for this modification. This question is displayed when the SALREVQ - Revision management parameter is set to: Managed on demand.

• Revision management from the Quotes function,
• Quote line revision window from the Actions icon available on the modified quote line.

• Reference (field CUSQUOREF)

This information is used to specify the customer's reference for the quote. It can be used as a search criteria in the selection list and is printed on the quote.

• Date (field QUODAT)

The quotation date is initialized via the date of the current day and can be modified as long as the quotation is not 'ordered'. Upon duplicating a quotation of if the date is modified, a question is displayed and suggests a recalculation of prices and discounts (if the quote is not partially 'ordered').

• Customer (field BPCORD)

This is the customer or prospect code for whom the quote is being drawn up. It is managed in the customer and prospect table.

The customer entered must be active. It can be of normal or miscellaneous type. In case of a miscellaneous customer, an address entry window opens automatically.

You can also enter a prospect. When a quote is turned into an order, the system suggests that the prospect be changed into a customer. As a matter of fact, an order can only concern a customer

Click the Actions icon to:

• select a customer or a prospect,
• create or consult, according to the user's authorizations, a customer or a prospect,
• enter a new address associated with a quote,

• view the notes related to the prospect or customer.

• field BPCNAM

This is the corporate or company name of the customer or prospect. This information is not directly modifiable. It can be modified from the address management screen available from the Customers field or the tool bar. The corporate or company name of the customer is printed on the quote.

• Currency (field CUR)

This is the currency in which the quote is drawn up. By default, it is the customer's or prospect's currency. The currency code mentioned in this screen cannot be modified. It is only mentioned as a reminder. The currency code can be modified in the Management tab of the quote.

• Final number (field SQHNUMEND)

• Delivery address (field BPAADD)

The delivery address is initialized by the default delivery address associated with the customer. For prospects, as they do not have a delivery address, their default address is systematically used.

The delivery address is modifiable. It must be one of the delivery addresses defined for the customer. For the prospects, it must be one of the existing addresses. In this case, if the quote is turned into an order, the prospect's address at use is automatically turned into a delivery address when the prospect becomes a customer.

The delivery address may not be entered on the quote. In that case, from the moment that the quote is considered on an order, the default delivery address will be automatically selected upon order creation.

If you change the delivery address on the quote header, then:

• If you are in creation mode and no line has been entered, the data linked to the new delivery address code is reinitialized (Shipment site, Delivery lead time, Incoterm code and Incoterm city, Freight agentand freight agent address code, EU VAT numberand Intrastat transport location, delivery Contactand Sales reps, if the same as the ship-to customer’s.
• If you are creating or modifying the quote and quote lines exist, the system suggests to reload the header fields linked to the address code with the values attached to the new address. The data are the following: Delivery lead time, Incoterm code and Incoterm city, Freight agentand related address code, EU VAT number and Intrastat transportlocation (and in some cases the Sales reps).

This rule does not apply to the shipment site which remains unchanged.
A message opens to suggest that you transfer the modification to the quote lines.

• If you answer Yes, the quote line information related to deliverable products is modified against the delivery information of the quote header (delivery Address code , Delivery lead time, Delivery contact , and Sales reps, if the same as the ship-to customer’s).
  If one or several products are prohibited for this new address, their list is displayed on the screen in a log file. If you are not subject to any blocking control on prices (SDACLOK - Non block ctrl price, profit,qt user parameter), then you may ignore the warning message and resume.
  A dialog box opens and suggests that prices and discounts be re-calculated. The answer Yestriggers a price list search for all document lines. If the price list is defined with respect to the country code and/or new code of the geographic subdivision, prices and discounts may then be re-assigned according to these criteria.
  
• If you answer Noor Endto this question, the quote line information will not be modified.
  
• If you answer Yes if same valueto this question, only the quote line referring to the initial delivery address will be modified.
  If one or several products are prohibited for this new address, their list is displayed on the screen in a log file. If you are not subject to any blocking control on prices (SDACLOK - Non block ctrl price, profit,qt user parameter), then you may ignore the warning message and resume.
  A dialog box opens and suggests that prices and discounts be re-calculated. The answer Yestriggers a price list search for lines with a modified delivery address.
  If the price list is defined with respect to the country code and/or new code of the geographic subdivision, prices and discounts may then be re-assigned to these lines according to these criteria.
  
  The price list re-calculation is only performed on lines if the quote is not ordered.

Special feature: if the LINBPD - Different ship-to customers on order lines parameter (VEN chapter, MIS group) is set to No, the address code is used on each quote line and cannot be modified at line level. In case modification, all the quote lines are automatically modified and you are advised to run a new price list search.

From this field, you can:

• select an address code for prospects and a delivery address code for customers,
• jump to the delivery address in the case of a customer,
• view and modify the delivery address detail related to this quote.

• field BPDNAM

Il s'agit de la raison sociale de l'adresse de livraison.

• Project (field PJT)

The management of the project code depends on the value of the CTLOPPCOD - Mandatory project control parameter (TC chapter, MIS group).

• 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, you can choose a project or one of the entities to be allocated to the project (budget lot, task) using the allocation code:

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 creation mode, the project code is systematically transferred to the document lines where it can only be modified if the multi-project management of documents is authorized (the PJTSNGDOC - One project per document parameter is set to No).

During the transformation of a document, the project code of the header is initialized by the first selected document (if the project code of the original document header has become inactive, the one of the destination document is not loaded).

• 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: It is not ordered.
• For an order: It is not delivered (for standard orders) or not invoiced (for direct invoicing) and no line is closed.
• For a delivery: it is not validated and the delivery is direct.
• For an invoice or a credit memo: it is not validated and the invoice/credit memo is not direct.

The grouping of two or more documents with different project codes in the header is only authorized if the parameter PJTSNGDOC - One project per document is set to No. In this case, two orders with a distinct project code can be grouped on the same delivery note.

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

• Order type (field SOHTYP)

This field is automatically loaded with the order type defined in the setup function Quote types (GESTSQ).

In the case of an order creation using the Order button from a quote

If no order type is defined in the quote, the general parameter QUOORDCAT - Order category (VEN chapter, ORD group) will be used to define the order category to apply ('Normal' or 'Direct invoicing').

• If the category defined in this parameter is 'Normal', then the order type defined in the SOHTYPNOR - Normal order type parameter (VEN chapter, ORD group) will be used.
• If the category defined in this parameter is 'Direct invoicing', then the order type defined in the SOHTYPINV - Direct invoicing order type (VEN chapter, ORD group) will be used.

If no value is defined in the QUOORDCAT - Order category from button parameter, the system takes into account the first order type in alphabetical order.

• Shipment site (field STOFCY)

The shipping site is the storage site from where the products will be shipped when the quote will have been ordered.

The shipping site is initialized to the shipping site entered on the ship-to-customer (it corresponds to the usual shipping site for this delivery address) or, if nothing has been specified, to the user's default storage site. In both cases, the shipping site must belong to the same company as the sales site, otherwise it will not be submitted and it will have to be necessarily entered.

The shipping site is modifiable under certain conditions:

• the entered site must be declared as the storage site,
• It must belong to the same legal company as the sales site.

The shipping site entered in the header is used as the default value for the quote lines. If it is modified and the quote lines are present, the system suggests to the user to modify the shipping site on all quote line. The header shipping site is taken as default value for new lines.

• Delivery lead time (field DAYLTI)

This is the necessary lead-time in number of days to deliver this ship-to customer. It is initialized by the lead-time entered on the customer delivery address. This lead-time will then be used to calculate the shipping date and the planned delivery date during the conversion of the quote into an order.

This information is used to initialize the delivery lead-time in the quote lines. If the quote involves a prospect, the delivery lead-time will not be initialized.

• 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 menuOptions / Informations douanières.

• Incoterm town (field ICTCTY)

It is the city associated to some types of incoterm. For example: 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.

• field REP

The sales representatives are initialized by the representatives of the customer and then by the ones of the ship-to customer when no sales rep. exists in the customer record. In the case of a prospect, only the representatives of the prospect are taken into account. These sales rep codes are used in the quote lines. If a sales representative is modified in the quote header (on creation or when quote lines exist), the system suggests that the modification be applied to all existing lines or on the lines related to the previous sales representative (choice Yes if same value).

• Tax rule (field VACBPR)

A tax rule represents the tax territoriality principle, in other words, the calculation rules necessary to determine the amount of taxes that can be applied to the quote.

As a general rule, by crossing a tax rule linked to the BP with a Tax level, you can determine the tax code to be applied to the document line and so, to the entry line.

The tax rule is based on the tax rule of (in order of priority):

• the ship-to customer,
• the BP/Company,
• the customer.

If the customer is a prospect, the default tax rule defined in the tax rule table is used.

Only a tax rule with a legislation and group that are consistent with those of the document can be entered.
See the documentation on general principles linked to the mutli-legislation setup.

Once the quote is created, this information can no longer be modified. If however, you modify the tax rule after entering quote lines but before creating the quote, then taxes are re-calculated on all entered lines.

The parameter CTLTAX - Tax codes control (VEN chapter, VAT group) is used to control that the BP tax rule:

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

• Entity/Use (field SSTENTCOD)

Enter the Entity/use code to calculate the precise tax amount for the customer. This tax code is compatible with the Avalara system and makes it possible to determine the customer type for fiscal purposes.

This field is available for all countries. The Entity/Use code can be entered for any delivery address when a document is being processed for a country that is tax-exempt. When the Calculate alldocuments connection with SST is set to No andan Entity/use code is entered, the document is exempt from tax and not subject to processing costs.

• Currency (field CUR)

The quote currency is initialised by the customer or prospect currency. Once the quote is created, this information is no longer modifiable. If however the currency is modified after having entered the quote lines, but before having created the quote, then a price and discount conversion will be carried out. it is however possible to carryout a new price list search as function of the new currency by responding Yesto the question "Do you want to recalculate the prices and discounts ?".

• Price - / +tax (field PRITYP)

This indicator is used to determine if the product prices are expressed excluding taxes or including taxes. This indicator influences the price list search. Only price lists defined in a mode or those to which a price conversion can be applied to are taken into account.

The price type of the quote is "excluding taxes" or "including taxes" depending on the price type defined for the customer. For a prospect, the suggested price type is always "excluding taxes".

If the Sales general parameter "Excluding or including taxes (TC chapter, INV/NOTATI group) is set to "No", this information cannot be modified and the value of the field is then defined by the Sales general parameter "Price type" (TC chapter, INV/SALPRITYP group). The price type of the customer is then of no importance.

• Validity date (field VLYDAT)

This is the date up to which the commercial proposition is effective. Beyond this date, it will not be possible to convert the quote into an order.

• Probability rate (field PBYPRC)

This is the estimated percentage that identifies the possibility to transfer the commercial proposition to a firm order.

• Signed (field APPFLG)

This information is used to identify the document situation from the signature management point of view. The possible values are: 'No', 'Partially', 'Totally', 'No management', 'Yes automatic'.

- If the approval management is not active for the company (APPSQH setup for the quotes, APPSOH for the orders or APPSOC for the contract orders), the value will systematically be equal to "No management". It is possible to edit and change the document (change the quote into an order, deliver the order or the delivery request).
 
- If the signatures management is activated for the company, the value will depend on the signature rules and the signatures carried out:

• If the value is set to No, it means that no signature has been entered or that the signatures that have already been carried out have been cancelled by a signer.
• If the value is set to 'Partially', it means that some of the signers defined in the approval circuit have signed the document.
•  If the value is set to Totally, it means that all the signers defined in the signature circuit have signed the order. It can be edited and ordered (for the quotes) or delivered (for the orders and delivery requests).
   In the last two cases, modifying some document fields (see the list of the Approval rules documentation (SQHSIGfor the quotes, SOHSIG for the orders and SOCSIG for the contract orders) can reinitialize the approval circuit and have an impact on the situation of the document with regard to the approvals.
  In the particular case of a contract order, the approval circuit is not modified as soon as at least one delivery request has been associated to it.
• If the value is set to 'Yes automatic', it means that the management of the signatures is optional (APPSQH, APPSOH or APPSOCsetups) and that no signature circuit has been determined for this contract. It is considered as approved and can be edited and ordered (for the quotes) or delivered (for the orders and delivery requests).

• Quote status (field QUOSTA)

This information, not modifiable, is used to identify the quote status. A quote can be Not ordered, Partially ordered or Totally ordered.

• Printed quote (field QUOPRN)

This information is used to identify whether the quote has already been printed.

• Electronic signature (field SQHCFMFLG)

• Validation date (field SQHVALDATC)

• Payment term (field PTE)

The payment condition is used to identify the customer's payment method as well as the scheduling of payments. Prepayment open items can be included in this distribution.

This information is initialized by the bill-to customer or on the paying BP linked to the customer on the quote, based on the setup of the PAYTERMVAL - Init payment conditions parameter (TC chapter, RSK group).

The intialization is carried out according to the following order of priority:

• BP/Company record (BP function)
• Customer record.

If the quote involves a prospect, no initialization is performed. You need to enter the information.

• Settlement discount (field DEP)

This information determines 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. It is initialized by the bill-to customer discount code.

The intialization is carried out according to the following order of priority:

• BP/Company record (BP function)
• Customer record.

If the quote involves a prospect, no initialization is performed. You need to enter the information.

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.

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

• Last order no. (field SOHNUM)

This is the number and date of the last order associated with the quote. A tunnel is used to access this order from the last order number field.

• Last order date (field ORDDAT)

The order date is initialized to the current date and can be modified (only in creation mode). The modification of this date during the creation leads to the display of a message offering the possibility to update the prices and potential discounts calculated for the order lines already entered. This modification also leads to the update of the expected receipt date of the order lines for which no requirement has been consumed.

• Dimension type (field DIE)

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

• Description (field NAMDIE)

This field repeats the title of the dimension type.

• Dimension (field CCE)

The analytical dimensions are initialized according to the Default dimensions setup, associated with the management of quote headers. 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 header leads to the dimension code being reset based on the Default dimensions setup. If the project code is used on the lines, the dimension code of the impacted lines is also reset.

• Short description (field SHO)

This field displays the title of the invoicing element.

• % or amount (field INVDTAAMT)

The values relate to the invoicing footer. This information can directly come from the setups of the invoice footer elements or from the customer record concerned by the selected quote.
See the Invoicing elements documentation for further information.
The footer values can be modified. If the quote involves a prospect, only the invoicing elements coming directly from the footer elements setup are picked up.
The ex-tax and tax-incl. amounts of the document are directly impacted by these values.

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

• Product (field ITMREF)

Product reference for which you are recording a document line.

You can 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 you enter a Product-customer reference, the system returns the internal product reference.
A blocking message is displayed when entering a product:

• if price lists of the prohibited type have been set up for some customers (see Price list setup),
• if this product if of the Kit parent producttype and cannot be delivered.

You can also use the Actions icon to do the following:

• Select a product from the file of sold products.
• Select a product from the list of customer products.
• 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 Descriptionand Sales unit fields, which can be modified. The sales unit can be modified on the condition that it is chosen from the list proposed 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 met:

• the Substitute product field of the product record has been entered,
• the document date is greater than or equal to the substitution date.

Once the line has been entered, you can modify the product code. It is necessary to delete the line and recreate it to modify the code.

• Description (field ITMDES)

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

• There is the possibility to access the product record using a tunnel from this field.

• Standard description (field ITMDES1)

This is the description entered in the product record. There is the possibility to access the product record using a tunnel from this field. If this description is modified, the modification will be transferred to the child document.

• Major version (field ECCVALMAJ)

This field displays the major version of the product.

The major version number can only be accessed if the tracking of major versions is active at the level of the product setup (in the Managementtab of the Product function, the Stock versionfield 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.

When the line is partially ordered, you can no longer change the version number.

When you click Order, the system transfers and controls version numbers on the order.

Version numbers are not transfered to a proforma invoice.

The Major version field display depends on the setup of the entry transaction (hidden, displayed, entered).

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

When the line is partially ordered, you can no longer change the version number.

When you click Order, the system transfers and controls version numbers on the order.

The Minor version field display depends on the setup of the entry transaction (hidden, displayed, entered).

• SAL (field SAU)

The sales unit is initialized by the sales unit defined in the Product-customer record, or by the sales unit of the product. It is possible to enter another unit using a selection window. The suggested units are the packing units of the product and the packing units defined in the Product-customer record. If the user has the appropriate authorizations, it is possible to access the unit 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.

Inter-company specificities upon sales order entry: if the order has been generated from inter-company or inter-site purchase order, this information will be initialized with the unit entered in the purchase order and will be inaccessible. Only by modifying the original purchase contract order is it possible to modify this information.

• Quantity (field QTY)

It is the quantity ordered by the customer. It is expressed in a sales unit.

From the quantity field, the contextual button is used to consult the stock by site. The quantity MUST be 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 file. These messages can be blocking ones according to the value of the user parameter SDACLOCK-Price,margin,qty non-blocking ctrl (Ven chapter, AUZ group).

When the two principal items of information (Product and Quantity) have been given, a price list search process is automatically carried out. The objective 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 fact, if the product entered is of the type Normal,the search process is automatically triggered.
When the entered product is of type Kit parent product or BOM parent product, an initial price list search is triggered for the parent product, 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 alternatives of the type Commercial 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 type Normal is automatically selected.
   
   It is automatically replaced by the substitute product if it was entered at the level of the Product record if the document date is greater than or equal to the substitution date.
  For the other types of components mentioned 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 type Normal (with formula), a window opens displaying all the products from the selection formula (or if the conditions are met, their substitute products along with, in this case, the description of original products). If a component of the type Normal has also been recorded in the same sequence, this component also appears in the list. By default, it is automatically selected but it is possible to de-select it. Its quantity cannot be modified. 
  It is possible to select one or several other components of the selection. The buttons [Include all] and [Exclude all] are available for this purpose. Therefore, if no component is selected, the button [Criteria] becomes available so as to narrow the selection when the number of lines in the table is too large (the number of lines presented depends on the number of lines that still can be inserted in the document).
• For each component of type Variant, a window opens displaying the set of variants listed at the same BOM level or coming from a selection. It is mandatory to 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 or when a selection formula is defined, a window opens for the user to select one or more options or to refuse all of them.
• For each component of type Multiple option, a window opens displaying the set of components listed at the same BOM level or coming from a selection formula. You can select several components or refuse all. The buttons [Include all] and [Exclude all] are available for this purpose. If no component is selected, the button [Criteria] becomes available in order to narrow the selection 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 become independent with respect to the parent product. If the parent product is modified or deleted, the user is asked 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 order 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 Varianttype component,
• Kit component or BOM component for a component of Normal type.

Some price list controls are carried out on exiting this price list processing:

• If the price is defined tax included, the tax-ex price is calculated.
• Price control: 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 (or margin rate) stored in the product record, a warning message appears.

These various messages can be blocking ones according to the value of the user parameter SDACLOCK-Price,margin,qty non-blocking ctrl.

On exiting the entry, all the totals are calculated.

• SAL-STK conv. (field SAUSTUCOE)

This is the conversion factor between the sales unit and the stock unit. This coefficient can be modified. It will be modifiable if the sales unit of the product or the packing unit have been checked as 'modifiable' (see the Product record). It cannot be modified if the unit used is a unit defined for the customer. If for the units used, the factor is modifiable, it is necessary to define only prices expressed in stock unit.

Once the line entered, it is no longer possible to modify the conversion factor. It is necessary to delete the line and recreate it to modify this factor.

Specificities linked to the inter-company: if the order has been generated from inter-company or inter-site sales order, this information is initialized with the factor calculated between the purchase quantity and the stock unit and it cannot be accessed. Only a modification of the original purchase order can modify this information.

• STK (field STU)

This is the stock unit for the product. This unit cannot be modified.

• Gross price (field GROPRI)

This is the unit gross price (in sales unit) of the product expressed tax-excluding or tax-including (depending on the price type). It comes from a price list search, or from the base price of the sales product if the price list search did not return any result.

If the sales unit is different to that of the price list line:

- The price list amount is converted if the Unit conversion is set to Yes in the Price list setup. This conversion is based on the table of unit conversion factors. If no conversion is set up for these units, the price list amounts are considered by applying a conversion rate of 1.

- The price list is not used if the Unit conversion is set to No in the Price list setup. The gross price is set to 0.

Click 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;
• Get an explanation on how the net price was obtained from the gross price and the different discounts.

If the entered price is null, a message is displayed to request confirmation.

This message is displayed neither for the components of a BOM nor for free items.

A processing for Free items is triggered at the end of the document line. This processing generates all the free product lines (Gross price and discounts set to 0). If the parameter FOCPRI - Free product valuation (chapter VEN, group PRI) has the value Yes, a price list search is triggered for the free item so as 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.

The original line number of the free item is mentioned in each free item line generated in the quote line file (information not displayed on the screen). The Origin information is displayed on the line that created the free items in the Free field. For the free item line, this information is set to Yes. All free item lines are accessible in modification mode (except the price and discounts fields). It should be noted that the management of free items is not taken into account for components.

When creating the document, if the setup manages grouped price lists (GRPPRI - Management of grouped price lists), a question is asked about whether to carry out a new price list search (for the grouped type) that is used to determine the specific conditions linked to the whole quote. At the end of this process, you may get the following, 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.

• field DISCRGVAL1

Discounts and charges columns are displayed. They depend on the setup of the Price list structure code (see the Price list structure documentation). They can be initialized by the use of the price lists (see the Price list parameters and Price list entry documentations). Access to these columns can depend on the parameters of the reasons associated with the price lists as well as the value of the reason given to the UPDPRISAL parameter for Sales and to the UPDPRIPUR parameter for Purchase.

These discounts or charges are defined in amount or in percentage and they are applied in total or as a cascade to the gross price to determine le net price of the document line.

From this information using the contextual button there is the possibility to view the reasons associated with the price as well as the different discounts and charges field.

• Net price (field NETPRI)

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.

• Cost price (field CPRPRI)

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

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

• Tax level 2 (field VACITM2)

• Tax level 3 (field VACITM3)

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

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

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

• Sales rep 1 (field REP1)

The sales reps on the document line are initialized by the sales reps entered in the document header. If the latter are not entered, the sales reps in the line are initialized by the sales reps for the customer, by those for the ship-to customer if there are no sales reps in the customer record.

If the parameter LINREP - Sales rep on detail allows it (chapter VEN, group MIS), the sales reps can be modified on the document line. It is possible, based on the user's authorizations, to access the sales representative record.

• Commission rate 1 (field REPRAT1)

The commission rate for the sales representative is initialized on the line based on the commission category for the customer and the commission rate for the sales representative by category. This commission rate can be weighted by a modifiable weighting factor that can be initialized by the price list setup. This information comes from the invoice header in the case of a direct invoice or the original document.

• Sales rep 2 (field REP2)

• Commission rate 2 (field REPRAT2)

• Comm. factor (field REPCOE)

This coefficient is used to weight the commissioning rate of the sales representatives for this document line upon commision calculation.
This information is initialized using the price list search: some price lists are used to define a weighing coefficient for the commissioning rate of the sales representatives.

• Address (field DBPAADD)

The delivery address is initialized to the delivery address entered in the quote header. It can be personalized on each quote line related to deliverable products, if the general parameter LINBPD - Ship-to customer on detail (VEN chapter, MIS group) allows it.
The modification of the delivery address of a quote line has the following consequences:

• the delivery lead-time of the line and the delivery contact will be re-initialized,
• if necessary, a message indicating that the product is prohibited for this new address, is displayed. If you are not subject to any blocking control on prices (SDACLOK - Non blocking ctrl price, margin,qty user parameter), then you may ignore the warning message and resume,
• a dialog box opens and suggests that prices and discounts be re-calculated. The answer Yestriggers a price list search according to the new delivery address.

The delivery address can be entered on a quote line. In that case, from the moment that the quote is considered on an order, the default delivery address will be automatically selected upon order creation.

From the Actionsicon, you can select a delivery address for the customer and jump to this delivery address. If the business partner for the quote is a prospect, only selection is available to pick an address for the prospect. When the quote line is taken into account for an order, the prospect's address is automatically transformed into a delivery address when the prospect becomes a customer.

• Delivery contact (field CNDNAM)

This is the name of the contact associated with the delivery address. If the delivery address corresponds to the delivery address in the document header, the contact suggested by default on the line is the contact entered for the delivery address displayed on the header.
If the delivery address does not match the delivery address mentioned on the document header, then the contact suggested by default is the business partner default contact if it corresponds to this delivery address. Otherwise, the system suggests the first contact of this address by alphabetical order on the contact code.

The quote lines applying to non-deliverable products are not impacted by this information.

• Lead time (field DDAYLTI)

Lead-time in number of days required to deliver the goods to the ship-to customer. The lead-time is initialized by the lead-time entered in the quote header if the address on the line corresponds the address in the header. If it is not the same delivery address, the lead-time is initialized by the lead-time of the entered delivery address. This lead-time will then be used to calculate the shipment date and the planned delivery date during the conversion of the quote into an order.
It the quote is about a prospect, the delivery lead-time is systematically recovered from the header.
The quote lines applying to non-deliverable products are not impacted by this information.

• Ship site (field DSTOFCY)

This is the storage site from where the goods will be shipped to deliver the quote line. The shipping site is initialized to the shipping site in the document header but it remains modifiable. This information can be used on the order and the delivery to manage the shipping of the goods.
If your authorizations allow it, you can select a warehouse site for the company of the sales site and jump to the site record.

The quote lines applying to non-deliverable products are not impacted by this information.

• field CCE1

The analytical dimensions are initialized according to the setup of Default dimensions, associated with the management of quote 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.

• Line amount - tax (field LINQUONOT)

This is the unitary net ex-tax price for the line multiplied by the document quantity.

• Line amount + tax (field LINQUOATI)

This is the unitary ex-tax price for the line to which the different taxes entered have been applied, multiplied by the quantity of the document line.

• Line margin (field LINPFM)

This is the unitary margin multiplied by the quantity on the document line.

• Line type (field LINTYP)

This information characterizes the line type by distinguishing a classic product from a kit or a BOM product.
It can take the following values:

• Normal,
• Fixed kit,
• Kit Component,
• Kit Option, Kit Variant,
• Flex kit,
• BOM component,
• BOM Option,
• BOM Variant.

• Free (field FOCFLG)

This information specifies whether the line concerns a free item or if the line is the origin of the generation of one or more free items.

• Order no. (field DSOHNUM)

This information shows the last order passed on this line of the quote.

• Margin (field PFMTOT)

This is the total margin of the document calculated from the margins on the document lines.

• Lines excluding tax (field QUONOT)

This is the aggregated tax excl. total for the lines. It is calculated by adding the quote lines. If the report DEVICLIENT is printed (Quote printed Ex-tax), the Ex-tax amount printed corresponds to the total Ex-tax amount.

• Excluding tax (field QUOINVNOT)

This field specifies the tax excl. result that integrates the various invoicing elements on the quote.
This information appears when printing the DEVTTC2report.
 The detail of the calculation is stored in tables SVCRVAT and SVCRFOOT.

• Including tax (field QUOINVATI)

This field indicates the tax-including total, which includes:

• the various invoicing elements entered in the quote,
• the tax calculation by tax basis.

This information appear when printing of the DEVTTC2 report.
To display the tax-including calculation details, click the Actionsicon, on Valuation + tax.

The detail of the calculation is stored in the SVCRVAT and SVCRFOOT tables.

• Company name (field BPRNAM)

Business Partner company 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 that identifies a company or an activity (site tax ID number, NAF in France), and whether its entry is mandatory or not,
• 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 those 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 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 loads automatically after the postal code and town/city have been entered and is based on the Postal codes setup.
If the field is controlled, the control is carried out with respect 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 toSage Sales Tax

• Incoterm (field XEECICT)

• Incoterm town (field XICTCTY)

• Freight agent (field XFFWNUM)

• Forwarding agent address (field XFFWADD)

• EU VAT no. (field XEECNUM)

• Intrastat transp. location (field XEECLOC)

• Intrastat transport mode (field XEECTRN)

• Transaction nature (field XEECNAT)

• Statistical rule (field XEECSCH)

• Transaction nature (field XEECNATR)

• Statistical rule (field XEECSCHR)