Quotes

Code used to identify the transaction set up.

The setup of the entry transactions enables the user to fully set up the entry screens associated with a document (quote, invoice order, request for quotes etc.) or with a stock transaction type (receipt, issue etc.).

For each document or stock transaction type, it is possible to define as many entry transactions as necessary, each one being identified by a code.

Each transaction is used to define, both for fields located on the document header and fields entered in the lines, whether they must be:

• Entered
• Only displayed
• Or hidden

Upon validation of this setup, dedicated entry screens are created, and then can be used by any user having been granted rights on the access code defined on this setup header.

• If a given user has the right to use several transactions of a given type, the choice is presented to the user when entering the function.
• If the user is only authorized one transaction, this transaction is automatically taken into account when entering the function.

Transaction description.

Use this field to activate or deactivate a transaction.
Inactive transactions are not displayed in the transaction selection window.

This access code is used to restrict access to data by user or group of users.
If this field is entered, only users with this access code in their profile can use this transaction.
If several transactions are available, you can choose the transaction you want to use to open the function. If only one transaction is available, there is no selection to be made: the default entry screen opens directly.

The company or site group entered here is used to filter the entries.
These entries can be accessed during the transaction.

If the associated document check box is selected, enter the report code for the standard printed document.

Select this check box to automatically launch the printing of the document on entry completion.

The automatic printing only takes place in creation mode.

This table contains the document invoicing elements (quote, order, shipment, invoice).

Different statuses in the document.

Quote (Print quote, Quote status)

Order (acknowledgement printed, Status of balance, allocation, delivery, order, invoice, credit).

Shipment ( Picking ticket printed, Del. note printed, Delivery status, Invoice status for the delivery).

Invoice (Invoice status).

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.

If this box is selected, the field Order type is displayed in the function Sales Quote (GESSQH). This field is automatically loaded with the order type entered in the setup function Quote types (GESTSQ).

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.

This field is used to specify the various amounts for the document linked to quotes (Ex-tax quote amount, Tax-incl quote amount, Total margin).

This setup is used to define, for this entry transaction, whether the margin must be displayed or not.

In both cases, a value is assigned to the field. This value is calculated from the product net price and cost price.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Product storage unit.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Net price.
It is the net price for the line. It is calculated from the gross price and the various charges/discounts.
This field cannot be modidfed.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Parameter that is used to define, for this entry transaction, if the ex-tax and tax-incl. amounts on the document lines must be displayed or not.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Field that cannot be entered and that defines the line.
The line can have the following values:

• Normal,
• Kit parent product,
• Kit component,
• Kit option,
• Kit variant,
• BOM parent product,
• BOM component,
• BOM option,
• BOM variant,
• Subcontracted,
• Service,
• Supplied material.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Non-enterable field defining the free item characteristics.
The values can be:
- No: This line mentions a price and has not delivered any free items
- Origin: Line mentioning a price and giving rise to free items
- Free item: Free line.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Order number created from the quote detail line.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

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

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

This field contains the reference of the project for which the information has been entered.
This field is not controlled in a table.

• In a request for quotes, this field is empty by default.
• in a purchase order, this field can be initialized by default using the Project reference of the previous line or that of the request for quotes considered.

It is possible to enter a free code or a project code defined in the Project object in the CRM activities module. In this latter case, the user has two possibilities to enter such a code:

• the first contextual menu, Selection, is used to select a project from a selection list containing all the projects defined in object Projects,
• the second contextual menu Projects is used to directly access the Projects object, according to the user's authorizations, and then to carry out a selection.

If the order arises from a requirement and this requirement has a project code, the project code of the order will be initialized with this project code.

Shipment site By default it is initialized with the shipment site of the ship-to customer. The site must be defined with the Warehouse flag set to the value "YES".

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

This setup is used to define, for this entry transaction, whether the Incoterm code field must be:

• hidden: the field does not appear in the entry screen but a default value is assigned to it.
• displayed: The default value is assigned to the field and displayed but the value cannot be modified.
• entered: the default value can be modified and when it is the case, it will be checked in the currency table no. 5.

The access to the freight terms code and city/town is also carried out via the menu Options / Customs information.

 The assigned default value is the Incoterm code associated with the ship-to customer in its record.

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.

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.

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

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

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

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

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.

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

Payment condition code. This code defines the payment code and the distribution rules of the various pre-payments and open items.
It is initialized by the bill-to BP and is controlled in the payment condition table.
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.

It is possible to simulate a distribution thanks to the "Simulation" button. In order management, creation mode, the pre-payments corresponding to the payment condition are automatically created. The 'payment terms' code can be modified as long as no pre-payment has been made and the order has not been invoiced. Such a modification would then trigger the deletion of the already existing pre-payments followed by the creation of the pre-payments related to the new payment condition.

Parameter used to define, for this entry transaction, if the discount must be:

• Hidden:
  The field does not appear on the entry screen but it is assigned a default value.
• Displayed:
  The default value is assigned to the field and displayed but the value cannot be modified.
• Entered:
  The default value is assigned to the field and displayed. It can be modified.

The first N columns specified in this field remain visible on the screen when scrolling.

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.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

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.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Use this field to control entry or modification of the Major version number for a product. You can set this field to one of the following values:

• Hidden:
  The Major version field is not displayed on the entry screen
• Displayed
  The version number is loaded automatically if a product is version managed. It cannot be modified.
• Entered
  The version number can be entered. The version number is loaded automatically if a product is version managed but can be modified.
  
  

Use this field to control entry or modification of the Minor version number for a product. You can set this field to one of the following values:

• Hidden
  The Minor version field is not displayed on the entry screen.
  The minor version is always hidden if the major version is hidden.
• Displayed
  The version number is loaded automatically if a product is version managed. It cannot be modified.
• Entered
  The version number can be entered. The version number is loaded automatically when a product is version managed but it can be modified.
  You can only select this value if the Major version is set to 'Entered'.
  
  

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

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

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

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.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

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.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

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

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

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 several tax levels for a document line:

• The first level is mandatory. It corresponds to the VAT,
• The two other levels correspond to additional or special taxes which may:
• be liable to VAT,
• be applied on ex-tax basis or other valuated 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.
Provided the user has the corresponding authorizations, he can access the tax level management.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

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.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Delivery date. This is the delivery lead-time in number of days associated with the ship-to customer. It is initialized by the lead-time entered in the header. It is modifiable and it is used to calculate the shipment date and/or the planned delivery date.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Delivery address
It is initialized to the delivery address contained in the order header.
It is modifiable if the address management site parameter for the line is set to 'yes' and if partial deliveries are authorized for the order. In this case, the address is controlled in the ship-to customer table.
Its modification causes the realignment of the lead-time, priority, delivery method and carrier. If the lead-time is modified, the dates are recalculated.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Shipment site. It is initialized with the shipment site of the document header. The shipment site is modifiable. In the orders, this information is modifiable as long as there is no allocation on the line. Moreover it is only modifiable if partial shipment is authorized. The product reference associated with this site must exist in the product-site table if the product is managed in stock. The site must be defined with the Warehouse flag set to the value "YES".

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

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 contract proposed by default in the line will be the contact entered in the delivery address in the header. If the delivery address does not match the delivery address mentioned in the document header, then the contact proposed by default will be the business partner default contact if it corresponds to this delivery address, otherwise the system will propose the first contact of this address by alphabetical order on the contact code.

The contextual button is used to select another contact if required.

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

This parameter is used to define, for this particular entry transaction, if the Project field must be:

• Hidden:
  The field is not displayed on the entry screen.
• Displayed:
  The field is displayed and cannot be modified.
• Entered:
  The field is displayed but can be modified.
  The control applied to the entered value is based on the CTLOPPCOD - Mandatory project control parameter (TC chapter, MIS group).

Even if the project code can be entered using this setup, its entry is still prohibited if the document management is single-project (the PJTSNGDOC - Single-project documentparameter is set to Yes): in that case, the project code of the line automatically uses the value of the project code in the header.

Help common to the Sales and Purchase modules.

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

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

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

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

From the Actions icon, you can:

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

Specify, for this entry transaction, if the field must be present in:

• Form and table mode
• Form mode
• Table mode.

Parameter used to define if, for this transaction, the analytical dimensions fields of the document header must be:

• Hidden: The options/analytical dimensions menu of the main window will be hidden.
• Displayed: It will be possible to access the options/analytical dimensions menu of the main window, the fields will appear but it will not be possible to access them.
• Entered: It will be possible to access the options/analytical dimensions menu of the main window, the fields will appear and it will be possible to access them.

This setup is used to define, for this entry transaction, if the analytical distribution key at line and invoicing element level must be:

• Hidden: the field does not appear on the entry screen but the default value is attributed to it,
• Displayed: The default value is assigned to the field and displayed but it cannot be modified.
• Entered: The default value is assigned to the field and displayed. It can be modified.

Parameter used to define, for this entry transaction, if the field must be present in:

• Record + Table modes,
• Form mode,
• Table mode.

Specify for this transaction if the analytical dimension fields related to stock movements must be:

• Hidden
• Displayed: The menu Analytical sections, accessible from the menu in the movement detail window, will be available. The fields are displayed but cannot be accessed.
• Entered: The menu Analytical sections, accessible from the menu in the movement detail window, will be available. The fields are displayed and can be accessed.

You can enter an analytical dimension type code on each table line.
You can access a function from the Actions icon to pre-load all the dimension types defined on the sites of a given group of sites.

Parameter used to define, for this entry transaction, if the analytical dimension must be:

• Hidden: The field is not displayed on the entry screen. However, it is possible to initialize this field with a default section code.
  
• Displayed: The default value is allocated to the field and displayed but the value cannot be modified.
  
• Entered: The default value is assigned to the field and displayed. It can be modified, and, in that case, the entered value is checked in the analytical dimension table.
  The default value assigned to the analytical dimension is dependent on the dimension setup performed.