Open orders

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.

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

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

This is the last revision number established for this contract. It is automatically incremented upon each modification of the contract if the SALREV parameter (Revision management) is set to Yes) and if the user confirms that the modification that they are carrying out is the subject of a revision.

This information is used to specify the customer order reference. In the case of an inter-company or inter-site order, generated from a purchase order of the same type, the purchase order number will be entered in this field and a tunnel can be used to access the purchase order at the customer site.

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.

This field indicates the customer identifier code. 

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.

This field is used to enter the pay-by customer code, initialized by default to the customer code entered in the header. The invoice payment schedule will be allocated to this BP.
This customer can be another customer chosen from the customer table.

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.

This non-modifiable information specifies if the contract is of the type inter-site or inter-company.
When the contract concerns an inter-site customer (site of the same company), it will not be possible to invoice said contract.
When the contract concerns an inter-company customer (site of a different company), it will be possible to generate an invoice from the deliveries coming from this order.

This flag is designed to indicate if this is an inter-site BP:

• The inter-site customer/supplier BPs are used for multi-site exchanges.
• A customer BP is a purchase site or a financial site,
• a supplier BP is a sales site or a financial site.

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.

Deliveries linked to a task:

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

• If multi-project management of documents is enabled (PJTSNGDOC - One project per document parameter set to No), the delivery can include direct delivery lines and product lines linked to tasks. The header project code is used as the default value on direct delivery lines only. Product lines linked to tasks keep their project code, which cannot be modified. If the header project code is modified, the application of this code to the lines is suggested, as described above. This only applies to direct delivery lines.
• If multi-project management of documents prohibited (PJTSNGDOC - One project per document parameter set to Yes), the delivery cannot include both direct delivery lines and product lines linked to tasks.
• When the delivery is for direct delivery lines, you cannot enter a project code in the header that is already used on tasks.
• When the delivery is for product lines linked to tasks, you can only enter product lines linked to the same task. The header project code can then be used to filter tasks in the selection panel.

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

End date for the contract validity.

Code associated by default with the current BP, used to define the payment conditions.
This code defines the payment method, open item type, as well as the payment schedule (one or several open items cash, 30 days, end of month etc.).
When managing this table, it is possible to simulate the calculation rules that will be applied in entry mode.

Code associated by default with the current BP, used to define the payment conditions.

This code defines the payment mode, open item type, as well as the payment schedule (one or several open items cash, 30 days, end of month etc.).
When managing this table, it is possible to simulate the calculation rules that will be applied in entry mode.

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.

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.

This field, that can not be modified, displays the Delivery type associated with the chosen Order type.

If this has not been specified:

• During an order delivery using the [Delivery] button:
  The delivery type indicated by the parameter SDHTYPNOR - Normal delivery type or SDHTYPLND - Loan delivery type (chapter VEN, group SSD) is the one that is taken into account.
• During the Automatic order delivery and Picking ticket delivery processings:
  The delivery type entered in the processing launch function is the one that is taken into account.

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.

This field is initialized by the customer invoice exchange rate type.
It is controlled by a modifiable local menu and can take, amongst others, the following values:

• exchange rate of the current day,
• exchange rate of the current month,
• average exchange rate.

This field is used to indicate the tax rule.

The tax rule represents the tax territoriality principle, in other words, the calculation rules that need to be applied to determine the tax amount.

Rules are sorted according to rule type (in the BP tax rule, GESTVB function) in order to identify the various operating modes.

The tax rule is set up at BP level. The rule set up on the customer record or supplier record is suggested by default for all the transactions involving this BP.

As a general rule, crossing a tax rule with a tax level makes it possible to determine the tax code to be applied on the document line and as a consequence on the entry line.

In the tab BP/Company of this BP, it is possible to define different default tax rules according to the company. When a value does exist for a company, this value is suggested first.

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.

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.
  

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 (SQHSIG for 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 APPSOC setups) 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).

Among the suggested selections:

• 'Blocked': The customer credit status is Blocked, when the customer record shows that the credit status is blocked.
• 'Credit level exceeded': The customer credit status is in 'Credit level exceeded' when the Credit level total of the customer is higher than its Authorized credit level.

Concerning the allocation of the shipment requests associated to the contract order, if a shipment request is allocated where the calculated customer credit level is greater than the authorized credit level, the user will get a message requesting confirmation (if the user setup SCDTUNL authorizes it).
If not it will not be possible to allocate the shipment request and a blocking message will be displayed.
If the customer credit level is blocked, the delivery requests associated to the contract order cannot be allocated and new open orders for this customer cannot be created.

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

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

The allocation type (global/detailed) is initialized to the value of general parameter ALLTYP - Allocation type (VEN chapter, SAL group). It can be modified depending on the entry transaction used. The allocation type specified in this tab serves as the default value for the order lines created later.

This information can no longer be modified once the order has allocations.

The global allocation reserves the goods without distinction by applying a global total, whilst the detailed allocation reserves specific stock objects (lot, serial number...). An order can be allocated from the order (entry of the quantity to be allocated or using the Actions icon of the line to select stock lines in detailed allocation or using the allocation button) or from the Automatic allocation or Allocation by product functions.

This grid is used to enter or view the dimension type, based on the setup of the entry transaction of the contracts.

This field repeats the title of the dimension type.

Based on the setup, the dimensions care be modified since they are initialized according to the setup of the default dimensions.

Enter the short description.

By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
You can add your translation in another language using the Translation function:

• Click Translation from the Actions icon in the corresponding field.
• In the Translation window, add a new language code with the translation in this language.

A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language.

The connection language must be defined as a default language for the folder.

The values relate to the invoicing footer. This information can directly come from the parameters of the invoice footer or from the customer record.
 Refer to the Invoicing elements documentation for more information.
The values of the footer elements can be modified. The ex-tax and tax-incl. amounts of the document are directly impacted by these values.
Intercompany specificities
If the order has been generated from an inter-company or inter-site purchase order, and the inter-company setup stipulates that the invoicing elements come from the Purchase module, these will be initialized with the values entered in the original purchase order.

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

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.