Orders
Use this function to manage the orders placed by customers.
You can thus modify, delete, duplicate, view and print sales orders.
The managed orders can be of different types:
- normal orders that are delivered and invoiced,
- normal order applying to sold and non-deliverable products of the Generic or Service category,
- loan orders, that only concern certain customers and products for which loans are authorized. These orders are delivered and not invoiced as they are subject to a loan return. Otherwise, they can be invoiced,
- direct invoicing orders, or not delivered but invoiced.
This function can also be accessed by clicking Order in Quote entry.
When the signature management is activated (APPSOH parameter), an order cannot be turned into a picking ticket, and delivered or invoiced, as long as the order has not been signed (See below the Workflow rules on orders).
If parameter SOHAPPORD - Product WIP unsigned order specifies it, the order must also be signed for the product WIP managed in stock to be generated and for the order to be allocated (refer to Allocation).
Prerequisites
Refer to documentation Implementation
Screen management
The display of the entry screen depends on the setup of the selected transaction.
If a single transaction has been set up, no choice is suggested. Otherwise, a window opens to present the list of available transactions (the selection can also be restricted using access codes).
Header
Enter the general information related to the invoice such as the invoice type, sales site, customer code, date, etc.
Block number 1
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. |
Type (field SOHTYP) |
The order type is used to determine the order category (Normal (basic), Loan or Direct invoicing) as well as the sequence number used (if the sequence number is a manual counter, the order number can be entered). Contracts are not managed in this function. Only an order type with a legislation and company group consistent with those of the company linked to the sales site can be entered. Case of an order creation using the Order button from a quote If the order is created using the Order button from a quote, the field is loaded with the order type entered in the Order type field of the quote.
If no value is defined in the QUOORDCAT - Order category from button parameter, the first order type in alphabetical order is used. |
Number (field SOHNUM) |
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. |
Revision (field REVNUM) |
This field cannot be entered. It is only loaded when order revisions are managed (SALREV - Revision management parameter (VEN chapter, ORD group)). It displays the last revision number created for the order. When you modify an order, the original values (before modification) are saved in the history of revisions and the revision number is incremented:
To view the history of revisions and detailed modifications, click:
|
Reference (field CUSORDREF) |
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. |
Final number (field SOHNUMEND) |
Date (field ORDDAT) |
This is the customer date. It is initialized to the current date and it can be modified. If it is modified, after at least one line has been entered or saved, a message suggests that you recalculate prices and discounts on all document lines. When an order line managed with price lists relates to a non-deliverable Service product with a billing plan number and a scheduled invoice with a validated progress status, prices and discounts are not recalculated on this line. When an order contains several non-deliverable Service product lines with a billing plan number and a scheduled invoice with a validated progress status, the price list search will no longer be run for all remaining products managed with price lists. However, you can run a recalculation of prices and discounts manually from the corresponding order line. |
Sold-to (field BPCORD) |
The Sold-to customer is the order-giver for the order. This customer must be activated to be assigned to an order. You can also enter a prospect. In this case, a message suggests that the prospect be changed into a customer; otherwise the order cannot be created. Click the Actions icon to:
Click Quick customer search to search for a customer, or several customers grouped under the same criteria. A list of matching items is generated on tabulating to the next field. Inter-company specificities: In the case of an inter-company order automatically generated from a purchase order, the Sold-to customer corresponds to the customer associated with the purchase site entered in the purchase order. |
field BPCNAM |
This is the customer's corporate or company name. This information is not directly modifiable. It can be modified from the address management screen available from the Sold-to customer field or the tool bar. The corporate or company name of the customer is printed on the order acknowledgement or receipt. |
Currency (field CUR) |
This is the currency in which the order is drawn up. By default, it is the Bill-to-customer'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 order. |
field WSOHCAT |
The category cannot be modified; it is determined by the chosen Order type. Intercompany specificities: For intersite orders automatically generated from a purchase order, products are always Received / Deliverablefields. In this case, the order category is always: Normalfields. For intercompany products automatically generated from a purchase order, the sales order category is defined by the product of the first line entered on this purchase order:
|
Management tab
Use this section to specify:
- The sales information from the order header such as:
- The invoiced customer code
- The pay-by customer code
- The group customer code
- etc.
- The order status information such as:
- The allocation status
- The delivery status
- The invoice status
- The customer credit status
- The hold status
- etc.
Most information is initialized by default and can be modified.
BP
Bill-to customer (field BPCINV) |
The bill-to customer code must be active. In all cases, it is initialized by the bill-to customer code associated with the sold-to customer in the latter's record. These is the possibility to modify the bill-to 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. Once the order is partly delivered, this information will no longer be accessible. Special features linked to the inter-company option: In the case of an inter-company order automatically generated from a purchase order, the bill-to customer corresponds to the customer associated with the invoicing entered in the purchase order. This information is not modifiable in this context. |
field BPINAM |
This is the bill-to customer's corporate or company name. This information is not modifiable. |
Pay-by (field BPCPYR) |
The Pay-by BP is initialized by default by the pay-by BP associated with the sold-to customer in the latter's record. It is possible to modify the pay-by BP if necessary. From this field, it is possible to select a BP or access BP management by tunnel if the user's authorizations allow it. Special features linked to the inter-company option: In the case of an inter-company order automatically generated from a purchase order, the pay-by BP corresponds to the customer associated with the invoicing site entered in the purchase order. This information is not modifiable in this context. |
Group customer (field BPCGRU) |
The group customer is initialized by the group customer code associated to the sold-to customer in the latter's record. This information is used for the generation of statistics. It is also involved in the grouping of invoices during the automatic generation of invoices. There is the possibility to modify the group customer if necessary. From this field, it is possible to select a customer or access customer management by tunnel if the user's authorizations allow it. It is possible to search a customer or several customer grouped under the same criteria by selecting "Quick customer search". A list of matching items is generated on tabulating to the next field. For a more advanced search, all fields present in the block can be entered. The list of matches is narrowed down with each tabulation. |
Delivery address (field BPAADD) |
The combination of the sold-to customer and this address code identifies the ship-to customer. The delivery address is initialized with the default delivery address associated with the sold-to customer in the latter's record or with the first delivery address code in the absence of any default delivery address. From this field, click the Actions icon to select a delivery address. If the delivery address is not managed on the line (LINBPD - Ship-to customer on detail parameter), this address code will be picked up by each line in the order and cannot be modified. When this not the case, this address code will be picked up on each line, but it cannot be modified. If you modify the delivery address on the order header while in creation progress and no line has been entered, a message will ask you if you want to update the requested delivery date based on the shipping date and new delivery lead time linked to the new address. In all cases, the information linked to the new address code is reinitialized (Shipping site, Delivery priority, Route code, Delivery method, Carrier, Delivery lead time, Incoterm, Incoterm town, Forwarding agent and address code, EU VAT number, Intrastat transport location, Delivery contact, Sales representatives if they are related to the ship-to customer). If you modify the delivery address and order lines exist (in order creation), a message warns you that the delivery date will be recalculated with respect to the requested delivery date. In all cases the information related to the new delivery address is reinitialized in the order header (Delivery priority, Route code, Delivery method, Carrier, Delivery lead time, Delivery contact and Sales representatives if these come from the ship-to customer). This rule does not apply to the shipping site which remains unchanged. A message then asks if you also want to apply the modification to the order lines. Depending on your answer:
Notes:
Specificity: If the LINBPD -Ship-to Customer on Detail (VEN chapter, MIS group) parameter is set to No, the address code is applied to each order line and cannot be modified at line level. If a modification is applied, all order lines are automatically impacted and a new price list search is suggested. Intercompany specificities: If an intercompany order is generated automatically from a purchase order, the delivery address corresponds to the ship-to customer associated with the receiving site entered on the purchase order. |
field BPDNAM |
Il s'agit de la raison sociale de l'adresse de livraison. |
Projects
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 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: The project allocation code is composed of:
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).In modification, the project code modified in the header is recovered automatically in lines, except when the multi-project management is authorized in which case a dialog box will open and requests whether to transfer this code to the document lines with respect to the following options:
Sales documents: Quotes, orders, deliveries and invoices: In case the project code is applied to the lines, a dialog box opens and suggests a recalculation of prices and discounts If you answer 'Yes', the price list search is run based on the new project code for all document lines. Depending on the processed document, the recalculation is performed only if the following conditions are met:
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.
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. Intercompany specificities: For an intersite order, the project code automatically displays the project code of the purchase order. For an intercompany open order, the project code is not recovered from the purchase order and remains blank.
|
Sales reps
field REP |
The sales reps are initialized by the customer sales reps, then by those of the ship-to customer, if no sales rep exists in the customer record. If one of the two sales representatives is modified and if there are lines in the order, the system will ask the user whether to copy the modifications to the order lines and to recalculate the commission rate. The user will also have the possibility to only modify the order lines referring to the previous sales rep code (choice Yes if same Value). |
Management and taxes
Loan return date (field LNDRTNDAT) |
The planned loan return date is accessible if it is a loan order. It is initialized with the order date plus a month. This date cannot be prior to the order date. |
Closing reason (field CCLREN) |
This is the closing reason for the order line when this has been closed manually. The closing reason is loaded if the CCLRENORD closing reason parameter is active. This reason can correspond to the order closure reason (if the order has been globally closed) or corresponds to the closing reason assigned during the closing of this reason. During the order closing this information can be entered in a list of predetermined values (see miscellaneous table Closing reason). |
field CCLDAT |
Tax rule (field VACBPR) |
A tax rule represents the tax territoriality principle, in other words, the calculation rules to be applied to determine the tax amount. 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):
Once the order is created, this information is no longer modifiable. If you modify the tax rule after entering order lines but before creating the order, then taxes are re-calculated on all entered lines. Only one tax rule with a legislation and group that are consistent with those of the document can be entered. The parameter CTLTAX - Tax codes control (VEN chapter, VAT group) is used to control that the BP tax rule:
|
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 all
documents connection with SST is set to No and
an Entity/use code is entered, the document is exempt from tax and not subject to processing costs. |
Currency (field CUR) |
The order currency is initialized with the customer currency. Once the order is created, this information is no longer modifiable. If however the currency is modified after having entered the order lines, but before creating the invoice, then a conversion of the prices and discounts will be carried out. it is however possible to carryout a new price list search as function of the new currency by responding Yes to the question "Do you want to recalculate the prices and discounts ?". |
Price - / +tax (field PRITYP) |
The value of this field (Ex-tax or Tax-incl.) is defined by the general parameter SALPRITYP - Price/Amount type (TC chapter, INV group). When the general parameter NOTATI - Ex-tax and tax-incl. amount/price (TC chapter, INV group) is set to No you cannot modify this information. |
Status
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).
|
Order state (field ORDSTA) |
This information is used to identify the order status at any time. The possible values are: Not closed, Closed. Provided the order is not closed/completed it is possible to modify it. Otherwise the order can no longer be modified An order is considered as closed if it has been totally shipped (totally invoiced for the direct invoicing orders) or if it has been manually closed. |
Allocation (field ALLSTA) |
The possible values are: Not allocated, Partially allocated, Allocated. |
Delivery (field DLVSTA) |
The possible values are: Not shipped, Partially shipped, Shipped. |
Invoice (field INVSTA) |
The possible values are: Not invoiced, Partially invoiced, Invoiced. |
Credit (field CDTSTA) |
The possible values are: OK, Blocked, Credit level exceeded, Prepayment not made. Blocked
Credit level exceeded
Prepayment not made
In the case of an allocation, if you decide to allocate one or more order lines and the credit level calculated for the customer is greater than the authorized credit level, you will get a message to confirm the action if the SCDTUNL - Order unblocking authorization user parameter (VEN chapter, AUZ group) authorizes it; if not, you cannot allocate the order and a blocking message will be displayed.
|
field CDTBTN |
Hold (field HLDSTA) |
This field is only displayed when the Hold code option is activated at the level of the entry transaction. OK
Held
|
field HLDBTN |
Click this lock icon to hold/release an order. To put an order on hold :
When an order is placed on hold, activity cannot be processed against this order until the order is released from hold. Delivery, invoices, or preparation are systematically held. The allocation and back-to-back order creation depends on the manual order hold reason code settings. When an order is released but the customer remains held, the delivery import of the order cannot be performed. However, the interactive delivery of the order can still be performed. To release an order :
This icon is not available when you do not have sufficient user rights to release the order. This is true when one or all conditions below are met:
The user who created the hold can always unlock that hold even if they do not have security for the access code for the hold. If the hold code does not have an associated access code, there is no restriction on who can release the hold. |
field HLDCOD |
This field displays the manual order hold reason, entered to hold the order. To enter this code, open the Order hold/release screen by clicking the lock icon Hold status lock.
|
Block number 6
Acknowledgment printed (field OCNPRN) |
This information makes it possible to see if the order acknowledgement has been printed. |
Intersite (field BETFCY) |
This non modifiable information specifying that the order is of the type inter-site or inter-company. When the order concerns an inter-site customer (site in the same company) it cannot be invoiced. When the order concerns an inter-company customer (site in a different company), an invoice can be generated. |
Intercompany (field BETCPY) |
Electronic signature (field SOHCFMFLG) |
Validation date (field SOHVALDATC) |
Delivery tab
Use this section to identify the delivery conditions for the order such as the delivery site, the delivery method, the carrier, etc.
Shipment
Shipment site (field STOFCY) |
The shipment site is the storage site from where the products will be shipped when the order is delivered. The shipment site is initialized to the shipment site entered on the ship-to-customer (it corresponds to the usual shipment site for this delivery address) or, if nothing has been specified, to the user's default storage site. In both cases, the shipment 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 shipment site can be modified under certain conditions :
The shipment site entered in the header is used as the default value for the order lines. In the case of orders with Complete shipment, the shipment site is not modifiable in the order lines. If the shipment site can be modified and the order lines exist, the system will propose to the user to modify the shipment site for all the lines in the order (only not allocated or not shipped order lines can be modified). Inter-company specificities In the case of an inter-company or inter-site order generated from a purchase order, the shipment site will be initialized by the shipment site entered in the purchase order. It can be modified to manage any changes in the shipments. However the source purchase order is not updated by this modification. |
Delivery priority (field DLVPIO) |
In this field, specify the delivery priority (Normal, Urgent, Very urgent). The priority is used to classify orders during the delivery preparations. The order lines applying to non-deliverable products are not impacted by this information. |
Dates
Required delivery (field DEMDLVDAT) |
The requested delivery date corresponds to the date requested by the customer. It is initialized by the shipment date (itself initialized by the order date) increased by the delivery lead time associated with the delivery address. This date is recovered by default on the order lines when products are deliverable products. If this date is modified, it will be used to recalculate the shipment date. If the order contains lines, a message suggests that you update the requested delivery date and the maximum delivery date (if the entered date is greater) and the new shipment date on the order lines. A control is applied to this date based on the ship-to customer's working days and their unavailability calendar. If the requested delivery date corresponds to a non-working day for the customer, the date will be automatically moved to a date that is later than the initial date. If the requested delivery date corresponds to a day that falls into the unavailability calendar of the customer, then a warning message is displayed suggesting that you modify the date or continue. Inter-company specificities: In the case of an inter-company or inter-site order generated from a purchase order, the requested delivery date will be initialized to the earliest date in the planned receipt dates entered on the purchase order lines. |
Delivery lead time (field DAYLTI) |
Lead-time in number of days required to deliver the goods to the ship-to customer. This field is initialized by the lead-time entered on the customer delivery address. This lead-time is suggested by default on the order lines corresponding to the delivery address of the order header when products are deliverable ones. It is used to initialize the shipment date based on the requested delivery date. The modification of this lead-time triggers the recalculation of the shipment date based on the requested delivery date. |
Shipment (field SHIDAT) |
The shipment date is initialized to the order date or the current date (if the order date is earlier than the current date). This date is controlled with respect the working days at the shipment site and with respect to the unavailability calendar for this site. If the calculated shipment date corresponds to a non-working day at the site, the system moves the shipment date (earlier) to the first working day. If the date corresponds to an unavailable day at the site, a blocking control is used to make you enter a new shipment date. This shipment date will be used by default on the order lines when the products are deliverable products. A warning message can also be returned when the entered shipment date is greater than the requested delivery date. Modifying the shipment date never updates the requested delivery date. |
Exp. delivery time (field DEMDLVHOU) |
This field is subject to the EDIX3 activity code. |
Transport
Route no. (field DRN) |
This code, which is controlled by a local menu, is used to generate the delivery notes according to the route code defining for example, a geographic zone. This information is defined by the customer delivery address. |
Delivery mode (field MDL) |
Use this code to define the information related to the transport and delivery. The code is managed in the Delivery methods table. It is initialized from the ship-to customer. The information describes how the goods will be sent to the customer (e.g. this information is used in the Intrastat exchange of goods declaration). The information is also used on the order lines, when the products are deliverable products. You can modify information on these lines if the delivery mode of the order is not Completeorder. If you modify this information when order lines already exist, a message displays and suggests that you copy this modification to the order lines. Inter-company specificities icon: In the case of an inter-company or inter-site order generated from a purchase order, the delivery method is initialized by the delivery method entered on the purchase order if the delivery method is not entered for the ship-to customer. |
Carrier (field BPTNUM) |
This is the carrier normally used to transport the goods to the customer delivery address. It will be used at the time of the shipment to establish the delivery cost calculation. The carrier is also indicated on the order line, when the products are deliverable products. You (or carriers themselves) can modify this information on order lines if the delivery mode of the order is not Complete. If you modify this information when order lines already exist, a message displays and suggests that you copy this modification to the order lines. Inter-company specificities icon: In the case of an inter-company or inter-site order generated from a purchase order, the carrier is initialized by the carrier entered on the purchase order if the carrier is not entered for the ship-to customer. |
Incoterm (field EECICT) |
The Incoterm codes, set by the International Chamber of Commerce, seek to standardize the terms the most used in the international commerce by defining the respective responsibilities of the seller and the buyer agreed upon on establishement of the sales contract by a unique word similarly understood throughout the world. The Incoterm code, controlled in Incoterm table is used in the INTRASTAT file (Exchange of goods declaration). It can also be used to define the price lists. When creating a quote, an order, a delivery or an invoice, the Incoterm code is initialized to the Incoterm code defined by default for the ship-to customer. This Incoterm code can be modified. Concerning the quotes and orders, the Incoterm code is unique for the document as a whole. When transforming a document, the Incoterm code is passed on to the child document. The code and the Incoterm city can also be accessed via the menu Options / Custom information. |
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. |
Last documents
Last delivery no. (field LASDLVNUM) |
This is the number and date of the last delivery carried out for the order. A tunnel can be used to access this delivery. |
Last delivery date (field LASDLVDAT) |
Rules
Delivery type (field SDHTYP) |
This field, that can not be modified, displays the Delivery type associated with the chosen Order type. If this has not been specified:
|
Close unfilled lines (field ORDCLE) |
This information, initialized by the sold-to customer, is used to authorize or not the closing of a line or the order. This information is modifiable on order entry if the transaction allows this. |
One order per delivery (field ODL) |
This information, initialized by the sold-to customer, is used to prohibit the grouping of several orders in the same shipment. This information is modifiable on order entry if the transaction allows this. |
Partial delivery
Partial delivery (field DME) |
This information, initialized by the sold-to customer, is used to specify how the order is delivered. There are three possible values:
This also means that a partial allocation cannot be performed on an order line or order if the stock is insufficient to cover the full line or order: the Partial Allocations option must be displayed on the order or in the mass allocation options.When entering the quantity to be allocated to the line or when performing a Manual allocation on the line, a warning message displays if the delivery is partial. Note: When you select Complete line or Complete order, you can ignore this warning message and force the partial delivery. |
Allocation
Allocation type (field ALLTYP) |
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. |
Invoicing tab
Use this section to identify the invoicing information.
Invoicing mode
Invoicing mode (field IME) |
This information is initialized by the sold-to customer and is used to define the customer's invoicing mode. This invoicing mode is used subsequently to invoice the delivery notes or the direct invoicing orders by regrouping or splitting them. This information is used in the automatic invoicing processes and in the manual invoicing function (where a control is performed with respect to this information). The available invoicing modes and their impact on the delivery invoicing are as follows:
Impact of the invoicing mode on delivery generation: orders with an invoicing mode 1 invoice/order or 1 invoice/completed order will never be grouped on a same delivery. Beside these invoicing modes, there are pieces of information that, if varying from one delivery to the next, prohibit the grouping together of two deliveries. Please refer to the automatic delivery invoicing documentation. The impact of the invoicing modes on the direct invoicing orders is as follows:
Beside these invoicing modes, there are pieces of information that, if varying from one order to the next, prohibit the grouping together of two deliveries. Please refer to the automatic order invoicing documentation. |
Payment/Last documents
Payment term (field PTE) |
The payment condition is used to identify the customer's payment method(s) as well as the scheduling of payments upon order invoicing. To simulate how expected payments will be staggered, go to the payment conditions management and click Simulation. Prepayment open items can be included in this distribution. In that case, prepayment requests will be automatically generated upon order creation depending on the order lines. These prepayment requests may be modified subsequently. This information is initialized by the payment condition of 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:
The payment condition can be modified as long as no prepayment request has been made and the order has not been invoiced. Modifying the payment condition leads to the deletion of the already existing prepayment requests and the creation of new prepayment requests linked to the new payment condition. Only a discount code consistent with the legislation and company group of the document site can be entered. |
Settlement discount (field DEP) |
This information determines early discount or late charge rates depending on whether the payment is early or late with respect to the due date. For further information, see the documentation on Discounts. The discount code is specified on the order. This code is initialized by the bill-to customer code of one of the following records, by order of priority:
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. |
Quote no. (field SQHNUM) |
This is the quote number at the origin of the order. A tunnel is used to access the quote. If there are several quotes, no quote number will be displayed at this level. They will be displayed at line level. |
Proforma no. (field PRFNUM) |
This is the number of the pro forma invoice associated with the document. The generated pro forma number is displayed if a pro forma invoice is created from this document. A tunnel then makes is possible to access the invoice. |
Last invoice no. (field LASINVNUM) |
This is the number and the date of the last invoice associated with the order. A tunnel is used to access this invoice. |
Last invoice date (field LASINVDAT) |
Block number 2
Invoicing term (field INVCND) |
This information is only managed with orders of the Normal category. It is not mandatory.
Only the lines that have not been closed or subject to invoicing are concerned. You can access the Invoicing terms management function from the Actions icon. In this function, use the Simulation action to simulate the scheduling of expected invoicing open items. |
Beginning due date (field VCRINVCNDD) |
This is the calculation start date for the planned invoices. |
Grid Analytical
Dimension type (field DIE) |
This table is used to enter or view the dimension types, depending on the parameters of the delivery entry transaction. |
Description (field NAMDIE) |
This field repeats the title of the dimension type. |
Analytical dimension (field CCE) |
The analytical dimensions are initialized according to the setup of Default dimensions, associated with the management of order headers. Depending on the setup, they remain available for modification. Inter-company specificities |
Grid Invoicing elements
Short description (field SHO) |
Enter a short description for the invoicing element. |
% or amount (field INVDTAAMT) |
The values relate to the invoicing footer. This information can stem directly from the parameters of the invoice footer elements or from the record of the concerned customer or the selected quote. The invoicing elements with a grouping rule based on the pro rata of weights or volumes are not taken into account in the flow for non-deliverable products. In the case of the modification of an invoice by deleting either a quote, or one or several lines from a quote, the amounts of the invoice elements are not recalculated by taking into account the deleted lines or quotes: the share of the invoicing elements relating to these lines or quotes is not subtracted from the modified order. Special features linked to the inter-company option |
field INVDTATYP |
The system specifies whether the invoicing element is a percentage or a tax excl. or tax incl. amount. |
SST tax code (field SFISSTCOD) |
Enter the code to use in order to override the default SST tax code from the product or invoice element. This tax code is recognized by Sage Sales Tax and is used to identify line types for tax purposes. This field is available only if the LTA - Local taxing activity code is activated, and the USATAX - Tax system 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. |
Return to calculated value |
Lines tab
Use this section to define the ordered product(s). The minimum information to be entered are the product and the quantity.
You cannot delete an order line linked to a billing plan. In that case, the product relates to a project set up with progress billing.
Product (field ITMREF) |
It is the product reference for which a document line is recorded. 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/Customerreference, the system returns the internal product reference. A blocking message is displayed when entering a product:
You can also use the Actions icon to do the following:
The entry of the product is used to initialize the Description and Sales unit fields, which can be modified. The sales unit can be modified on the condition that it is chosen from the 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:
Once the line is entered, it is no longer be possible to 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.
Inter-company specificities: In the event of an inter-company or inter-site order generated from a purchase order, the translated description will be initialized by the standard description of the purchase order (description translated into the connexion language, in other words, the language of the user who has created the purchase order.) |
Standard description (field ITMDES1) |
This is the description entered in the product record. This description is transferred to the deliveries or invoices (case of direct invoicing orders) along with any modification made in the order. When the order comes from a quote, the standard description is inherited from the quote line. It is possible to access the product record by tunnel. Special features linked to the inter-company option: In the case of an inter-company or inter-site order generated from a purchase order, the standard description is initialized by the translated description of the purchase order, and so, the translated description in the supplier's language (sales site). Enable the predictive or automatic entry by setting the AUTOSEL – Automatic selection parameter (SUP chapter, INT group) to Yes. AUTOSEL – Automatic selection parameter (SUP chapter, INT group) for the conditions for implementing the automatic search. |
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 Management tab of the Product function, the Stock version field is set to 'Major'). If the preloading of versions is active at the product/customer level (in the Customers tab of the Product function, the Version preloading box is checked), or by default, at the product/sales level (in the Sales tab of the Product function, the Version preloading box is checked), then the last active major version is preloaded automatically. Otherwise, the last major version with the 'Stopped' status will be preloaded. When the line is partially allocated, prepared, delivered or invoiced, you can no longer change the version number. When the order is converted into another document, the following actions are carried out:
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 allocated, prepared, delivered or invoiced, you can no longer change the version number. When the order is converted into another document, the following actions are carried out:
The Minor version field display depends on the setup of the entry transaction (hidden, displayed, entered). |
Ship site (field DSTOFCY) |
It is the storage site from where the goods are shipped to deliver the order line. The shipping site is initialized by the shipping site entered in the order header. It can be modified provided that the selected shipping site belongs to the same legal company as the sales site and the order line has not been allocated. In the case of orders with Complete delivery, the shipping site is neither modifiable on the order lines. It is possible to:
Special features linked to the inter-company option: In the case of an inter-company or inter-site order generated from a purchase order, the shipment site is initialized by the shipment site entered in the purchase order line. It can be modified to manage any changes in the shipments. This modification does not lead to the update of the original purchase order. |
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. |
Ordered qty. (field QTY) |
Quantity ordered by the customer. It is expressed in a sales unit. Click the Actions icon to:
The ordered quantity must be entered. A warning message is displayed if:
The product availability is displayed in the Available stock section under the table, if the option Product availability is selected in the Order entry transaction. Specificities linked to the inter-company: if the order has been generated from inter-company or inter-site purchase order, this information is initialized with the unit entered in the purchase order and cannot be accessed. Only a modification of the original purchase order can modify this information.
When the ordered quantity is entered a price list search process is automatically carried out. The objective of this search is to recover:
The price list search process can be triggered in different ways depending on the product type entered:
After choosing the BOM code, different cases can occur according to the construction of the product BOM:
The lines corresponding to the different BOM components are generated:
In both cases, a price list search for the component type is automatically triggered and for each order line generated, a value is assigned to the type of line:
Some price list controls are carried out on exiting this price list processing:
These various messages can be blocking ones according to the value of the user parameter SDACLOCK - Price, margin, qty non-blocking ctrl.(VEN chapter, AUZ group). Order lines applying to sold and non-deliverable products of the Generic or Service category:These products are subject to invoicing using an invoicing schedule. As long as the order line has not been invoiced completely, you can modify the quantity of the line. In that case, only the open items that are not invoiced yet and that are associated with the line can be modified. The percentage is recalculated for all the lines. The total amount of the order line can be different from the schedule total. When products are linked to a progress billing project:
|
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. |
Allocated qty. (field ALLQTY) |
This is the quantity, expressed in sales unit, already allocated in the order. This allocation can be global or detailed. |
Shortage (field SHTQTY) |
This is the shortage quantity in the order expressed in the sales unit. During the last allocation made in the order line, if part of the stock is unavailable then it is expressed in this column (if the GENSHT - Generation of the shortage quantities parameter (STO chapter/MIS group) is set to Yes). |
Qty to allocate (field WALLQTY) |
This is the quantity allocated to the order line. When the transaction authorizes it, it is possible to enter the quantity that is to be allocated on the order line. The quantity entered can be greater than the ordered quantity. A warning message will signal this. The allocation is carried out on saving of the order. If customer reservations exist for this product and if the USERERBPC - Consumption of customer reservations parameter is set to the value 'Yes', the reservations carried out by the customer are consumed during the allocation. If the customer credit is blocked, this field cannot be accessed. If the order status is Prepayment not settled, a warning message asks for the entry confirmation. When entering the quantity to be allocated:
In the specific case of order lines generated by back-to-back order on receipt or back-to-back production order.When the order line is associated with this type of back-to-back order, the automatic allocation processes do not allow the allocation of this type of line. The order line is allocated at the time of the associated purchase order receipt or at the moment of the production reporting for the associated production order. It is not possible to allocate an order line managed with direct orders. The available actions are:
|
Allocation type (field DALLTYP) |
The allocation type for an order line has as its default value the allocation type defined in the order header. It is possible to modify the allocation type (Global/Detailed) on a line, provided that the selected order transaction allows it. A global allocation is carried out depending on the available stock total. A detailed allocation reserved the stock objects (Lot - Serial number - Status - Location). When the order line is allocated, this information is no longer accessible. |
Quantity to deliver (field TDLQTY) |
When the ordered product is not managed in stock, you can specify the quantity to be shipped or invoiced (for direct invoicing orders) for this product. If nothing is specified, the whole line is shipped. When the product is not deliverable for a normal order, this field is not available: the quantity to invoice is defined on the invoicing schedule. |
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:
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. Free item processingA 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. 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:
Order lines applying to sold and non-deliverable products of the generic or service category.These products are subject to invoicing using an invoicing schedule. As long as the order line has not been invoiced in full, you can modify the price of the line. In that case, only open items not yet invoiced and linked to the line can be modified. The quantity and percentage of open items are not impacted. The total amount of the order line can be different from the schedule total. For products linked to a project with progress billing, you cannot update the price if the progress status linked to a scheduled invoice is validated. The price becomes available for modification again once the scheduled invoice is billed and the other scheduled invoices have not yet been linked to a validated progress status. |
field DISCRGVAL1 |
Discounts and charges columns are displayed. They depend on the setup of the Price list structure code. They can be initialized by the use of the price lists (see the Price list parameters and Price list entry documentation). 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.
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:
|
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):
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:
|
Invoicing term (field DINVCND) |
The presence of this field depends on the entry transaction used. In the case of Free items, the invoicing term is initialized by order of priority, as follows:
In the case of BOM parent products, which are not deliverable, the invoicing term is initialized based on the invoicing term entered on the order header, at the Invoicing tab level. By default, the term is initialized on each line (component and parent) based on the invoicing term specified on the line product. It can be accessed and modified on each line separately. If the invoicing term is not specified, the scheduled invoices are not generated. If the invoicing term is modified on the header, a dialog box opens suggesting to transfer the modification to the document lines, as for normal products (see the notes below about products). Notes applying to all products: When the invoicing term is modified on the document header, a dialog box opens and proposes to apply the modification to all document lines, based on the following options:
Only the lines that have not been closed or subject to invoicing are concerned. The selected invoicing term can only be modified once the order line is invoiced partially or totally. On order creation, when this choice is modified on an order line, the schedule is immediately revaluated based on this new invoicing term. On order modification, a message is displayed when modifying the selected schedule to inform you that the schedule of the relevant lines is to be modified. You can access the invoicing terms management in view mode from the Actions icon. In this function, use the Simulation action to simulate the scheduling of expected invoicing open items. To display the invoicing schedule of an order line, click Schedule form the Actions icon displayed at the beginning of a line. |
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). It can only be modified if one of the two following conditions are met:
In modification mode, the project code management depends on the value of the CTLOPPCOD - Mandatory project control parameter.
When the entry is controlled, depending on the context, a project or one of its entities can be picked (a budget batch or task), using its posting code: The project allocation code is composed of:
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. For non-deliverable Service products, you can select a project set with progress billing if the PJM activity code is active. Once the order has been recorded, you can view it in the Project management (GESPJM) function in the generated billing plan, linked to the selected project. When the project code of the document header is modified, this project code is automatically transferred to the lines, except when the multi-project management is authorized. In this case, a dialog box would open and suggest to transfer this code to the lines of the document, according to the following options:
Sales documents: Quotes, orders, deliveries and invoices: - If lines are impacted, a dialog box opens requesting a recalculation of prices and discounts. If you answer 'Yes', the price list search is run based on the new project code for all document lines. - If the project code is modified on the line, the same price list search process applies to the line. Depending on the processed document, the recalculation is performed only if the following conditions are met:
Deliveries linked to a task: The header project code displays the project code linked to the first selected task.
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. |
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. |
Requested delivery date (field DDEMDLVDAT) |
This is the delivery date requested by the customer. This date is initially by the requested delivery date entered in the order header. The modification of this date will trigger the recalculation of the shipment date (Shipment date = Requested delivery date - Delivery lead-time) and will recalculate the planned delivery date (Planned delivery date = Shipment date + Delivery lead-time). During the modification of this date, the system controls that this date does not correspond to a non-working day or an unavailable day for the delivery date. If this is a non-working day, the date is postponed, otherwise a warning message is displayed. Inter-company specificities: In the case of an inter-company or inter-site order generated from a purchase order, the requested delivery date will be initialized by the planned receipt date entered in the purchase order line. |
Lead time (field DDAYLTI) |
This is the delivery lead-time in number of days for the ship-to customer. This lead-time is initialized by the lead-time determined in the order header. It is used to calculate the planned delivery date from the shipment date. If the delivery address is modified on the order line, the delivery lead-time will be re-initialized with the lead-time entered in the new delivery address which will also lead to the recalculation of the planned delivery date. |
Ship date (field DSHIDAT) |
The shipment date is initialized by the shipment date entered in the order header. It is used to calculate the planned delivery date. It is calculated from the requested delivery date to the delivery lead-time is attached. If the shipment date is modified, the planned delivery date will then be recalculated by adding the lead-time to the shipment date entered. During the modification of the shipment date, the system controls that:
|
Expected delivery date (field EXTDLVDAT) |
This is the delivery date calculated by the system taking into account the shipment date and delivery lead-time. If the planned delivery date is modified, the system will suggest that the user modifies the shipment date as a function of the delivery lead-time. During the modification of this date, the system controls that this date does not correspond to a non-working day or an unavailable day for the shipment date. If this is a non-working day, the date is postponed, otherwise a warning message is displayed. |
Address (field DBPAADD) |
The delivery address can be personalized in each order line if the general parameter (LINBPD - Ship-to Customer on Detail) allows it and if the shipment method for the order is not Complete order, in which case this information will not be modifiable on the order line. The modification of the delivery address of an order line has the following consequences: Special features linked to the inter-company option: IIn the case of an inter-company order generated automatically from a purchase order, the delivery address corresponds to the ship-to customer associated with the receiving site entered in the purchase order. This information cannot be modified in the sales order. Only a modification of the original purchase order can update this information provided the order line is neither allocated nor shipped. |
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. |
Location reference (field USEPLC) |
This information is used to indicate the place of consumption or to define an addition to the address. For example: Dock x. Special features linked to the inter-company option: In the case of an inter-company or inter-site order generated from a purchase order, the place of consumption will be initialized by the place of consumption entered in the purchase order line. |
Delivery priority (field DDLVPIO) |
This information (initialized by the delivery priorities in the Delivery tab) is used to specify the priority of each line. This information is used to prioritize the preparation of certain order lines. It is used in the automatic allocation processing of orders. It is possible to allocate orders by priority level (e.g. to supply all orders when the stock is insufficient). If the delivery method for the order is Complete order, this information is not accessible at the order line level. |
Route no. (field DDRN) |
This code, which is controlled by a local menu, is used to generate the delivery notes according to the route code defining for example, a geographic zone. This information is defined by the customer delivery address. |
Delivery mode (field DMDL) |
This delivery method is used to define the information related to the transport and delivery. It describes the manner in which the goods will be sent to the customer (this information is used notably in the Intrastat exchange of goods declaration). It is managed in the Delivery methods table. This information is initialized with the delivery method entered in the order header but it can be modified on the line if the order delivery method is not set to the value Ship order complete. If the delivery address is modified on the order line, the delivery method will then be reassigned by the value mentioned on the delivery address. |
Carrier (field DBPTNUM) |
This is the carrier used to transport the goods to the customer delivery address. It is managed in the Carriers table. This information is initialized with the carried entered in the order header but it can be modified on the line if the order delivery mode is not set to the value Ship order complete. If the delivery address is modified on the order line, the carrier is reassigned by the value mentioned on the delivery address. The carrier is used later on the delivery note in order to calculate freight in accordance with the delivery weight and volume. |
Preparation code (field PRECOD) |
This field includes the preparation code. You can select this code from the Actions icon or enter it if it has not been set up. |
Packaging (field PCK) |
This code is controlled in the packaging table. It specifies the number of products, expressed in sales units, that the packaging can contain. It is initialized once the product has been entered, based on the sales unit used and the shipping site:
This information can be modified. This information and the packaging capacity are used upon preparation or shipment to carry out the packaging. If you are granted the proper authorizations, you can access the packaging record. |
Packaging capacity (field PCKCAP) |
Consumer sales price (field BPCSALPRI) |
This field is subject to the EDIX3 activity code.
In the case of orders received by EDI, the BOM and free item lines are not generated automatically. The final price of the product may be provided by the sender on each line. The lines are therefore imported one by one, based on the provided values.
|
Exp. delivery time (field DEMDLVHOU) |
The two fields Exp. delivery time and Max delivery time are initialized to the Exp. delivery time entered in the header.
|
Max delivery date (field MAXDLVDAT) |
This field is subject to the EDIX3 activity code.
|
Max delivery time (field MAXDLVHOU) |
The two fields Exp. delivery time and Max delivery time are initialized to the Exp. delivery time entered in the header.
|
Use-by date (field USELIMDAT) |
This field is subject to the EDIX3 activity code. |
field CCE1 |
The analytical dimensions are initialized according to the setup of Default dimensions, associated with the management of order lines. Depending on the setup, they remain available for modification. |
Order status (field DEMSTA) |
This flag is used to define the status of the order line which can be Firm or Planned. The Planned status is used to anticipate the firm orders to come because this information is used for requirement purposes in the MRP calculation. This flag is no longer modifiable if the order line has been allocated, delivered or invoiced. It cannot be modified if the line is managed with direct orders.
|
Product source (field FMI) |
Use this field to choose how to cover the requirement expressed by the order line: in a normal way, using a receipt back-to-back order, a direct back-to-back order or a production back-to-back order. Based on the product category and the setup of the product record (Sales tab), this field is initialized in the following way:
|
Back-to-back order no. (field FMINUM) |
This is the purchase order number or the works order number when a back-to-back has been generated for an order line. This document is accessible from the Position function. |
Line amt. - tax (field LINORDNOT) |
This is the unitary net ex-tax price for the line multiplied by the document quantity. |
Line amt. + tax (field LINORDATI) |
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. |
Quote no. (field DETSQHNUM) |
This is the quote number at the origin of the order line. To access the quote, click Quote from the Actions icon available on the order line. |
Billing plan number (field PRGBILNUM) |
This field cannot be entered. It only applies to non-deliverable Service products linked to a project with progress billing. This field displays the number of the billing plan linked to the project, which you generate from the Project management (GESPJM) function after entering the project code on the order line. For more information on how to manage progress billing, refer to the Project management (PJM) how to guide. |
Line type (field LINTYP) |
This information characterizes the line type by distinguishing a classic product from a kit or a BOM product.
|
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. |
Closed (field SOQSTA) |
This information specifies whether the order line is closed or still active. A line can be closed if it has been totally delivered (or totally invoiced in the case of direct invoicing orders or scheduled invoices) or if it has been manually closed. A closed line is no longer available for modification. If the order is not completely closed, an order line can be un-closed if associated with a service contract. |
Closing reason (field DCCLREN) |
This is the closing reason for the order line when this has been closed manually. The closing reason is loaded if the CCLRENORD - Enter order closing reason parameter is active. This reason can correspond to the order closure reason (if the order has been globally closed) or corresponds to the closing reason assigned during the closing of this reason. During the order closing this information can be entered in a list of predetermined values (see miscellaneous table Closing reason) |
Date closed (field DCCLDAT) |
This is the date on which the closing of the order was manually carried out. |
Prepayment contract no. (field PCNTNUM) |
Prepayment status (field PREPSTA) |
Available stock
field WSTKTXT |
The display of information related to stock availability depends on the setup of the Order entry transaction. If the product is not available, the message: ’XXX: Not available in stock' is displayed, followed by the possible first date of availability and quantity in stock unit and sales unit. |
field WALLTXT |
The display of information related to stock availability depends on the setup of the Order entry transaction. As for the document valuation, the display of the product availability is conditioned by the value of parameter SOHVALLIG - Order valuation on line (VEN chapter, MIS group). When the total quantity to be allocated is not available, the quantity remaining to be allocated is mentioned. It is expressed in stock unit and sales unit. |
Margin/Total
To deliver excluding tax (field DLRNOT) |
This field displays the ex-tax amount remaining to be delivered, calculated from the order lines which are either not delivered or only partially delivered. On standard orders, this amount is only calculated from lines that relate to deliverable products. On direct invoicing orders, this amount is loaded based on all the lines. It always corresponds to the ex-tax amount to be invoiced. |
To invoice excluding tax (field INRNOT) |
Specificities linked to the inter-site:
In the case of an inter-site order, this field is not loaded. |
Margin (field PFMTOT) |
Indicates the total margin of the order calculated based on the margin of the order lines. |
Block number 4
Lines excluding tax (field ORDNOT) |
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. |
Valuation
Excluding tax (field ORDINVNOT) |
This field indicates the ex-tax result including the various invoicing elements entered in the order. This information is displayed when printing the report ARCTTC2. The calculation detail is stored in tables SVCRVAT and SVCRFOOT. |
Including tax (field ORDINVATI) |
This field indicates the tax incl. total, which includes:
This information appears when the ARCTTC2 report is printed. The detail of the tax incl. calculation is obtained by right click on the total amount. The detail of the calculation is stored in the SVCRVAT and SVCRFOOT tables. In order to access the Incl. tax Valuation screen, click on the incl. tax field. |
Close | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to close the order line. You can close an order line, even if it contains allocated quantities (a warning message is then displayed allowing you to continue or cancel; if you accept, a deallocation of the line is carried out on saving the order line closing). The customer record or order must authorize order closing (Order closing authorization, Management section of the customer record and Closing authorization, Delivery section of the order initialized with the information from the customer record). You must be authorized for Closing authorization in the order management function. If the CCLRENORD - Order closing reason entry parameter (VEN chapter, ORD group) is activated, a closing reason can be entered to specify the reason for closing the line (the reasons can be set up in miscellaneous table 201). This information and the closing date are stored in the order line and viewed depending on the entry transaction used. This function makes it possible to reactivate a closed order line provided that the order is not fully closed and the order line does not refer to a service contract. Intercompany specificitiesIn the case of an order line generated from a purchase order, the manual closing of an order line is prohibited. Only the purchase order at the origin of this line can be manually closed (by closing the purchase order line). It is not possible to close an order line that is in the process of being delivered or invoiced. If the delivery has been validated or the invoice has been validated, the balance can be closed. This implies that it is possible to carry out a receipt or an invoice control on a closed order line. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Price calculation | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to run a new price search, in particular if the price is blank. This will refresh the prices and discounts on the selected order line. If the order line is linked to products from a progress billing project, the price search no longer updates the prices for the whole order if an order line has a scheduled invoice with a validated progress status. However, you can click the Price calculation action to recalculate the prices and discounts of the other order products that are not assigned to a scheduled invoice with a validated progress status. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Line status | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to view the status of the order line in terms of quantity totals.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Allocation detail | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This action is available if the order line is allocated. You use it to inquire the stock lines allocated to the order line or the allocated total if it is a global allocation. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Scheduled invoice | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This action displays the invoicing schedule for the order line. It is only available:
Two fields are available for scheduled invoices at To be invoiced status for you to enter any information that you find useful. Use the Category field on the payment schedule line (free value entered in miscellaneous table 205) and the Reason field (translatable text limited to 80 characters) for this. Scheduled invoices linked to a project can be managed directly from Project management. You might, therefore, notice an inconsistency in the apportioned dates, quantity, and amount of a scheduled invoice. If an adjustment has been made to a quantity or to an amount of a scheduled invoice, the adjustment is rolled onto the next scheduled invoice, whether the adjustment is an increase or a decrease in the invoice value. Adjustments made using Project management cannot be reapportioned over all remaining scheduled invoices at the time the adjustment is made. You must use this function to reapportion the remaining scheduled invoices, if required. Non-deliverable products: In creation mode, the schedule starts at the start date specified on the Invoicing section. It is based on the criteria entered for the invoicing condition on the line.
The created schedule is a suggestion. You can modify open items that have not been subject to invoicing yet. As long as the order line has not been invoiced completely, you can add or delete open items. You can also modify information related to each item such as period start and end dates, next invoice date, quantities, amounts. You can use the following actions after applying modifications to the schedule:
Non-deliverable Service products without milestone billing:: The schedule is based on the criteria entered for the Invoicing term on the line. The order line can optionally be linked to a project. All scheduled invoices have the To be invoiced status and the Billable field is set to Yes. The scheduled invoiced can be billed when the following conditions are met:
When the scheduled invoice is effectively billable, its Status becomes To be invoiced and the Billable field is set to Yes. You can trigger the invoicing process by clicking the Invoice action in the Orders function. You can also trigger it from the Invoices management function by picking scheduled invoices from orders, or using the Schedule invoice generation automatic processing. Notes:
Non-deliverable Service products with milestone billing: The schedule is based on the criteria entered for the Invoicing term on the line. If the order line is linked to a project, you can assign each scheduled invoice with the To be invoiced status to a milestone, which can be a task or a budget from a project. If the order line is not linked to a project, the milestone can be chosen freely. If you choose a budget, it must not be closed or delivered. If you choose a task, it must not be closed. The scheduled invoiced can be billed when the following conditions are met:
When the scheduled invoice is effectively billable, its Status becomes To be invoiced and the Billable field is set to Yes. You can trigger the invoicing process by clicking the Invoice action in the Orders function. You can also trigger it from the Invoices management function by picking scheduled invoices from orders, or using the Schedule invoice generation automatic processing. Notes:
Non-deliverable Service products linked to a progress billing project: The schedule is based on the criteria entered for the Invoicing term on the line. It is updated based on the progress status of the project, which is entered on the billing plan. A scheduled invoice becomes billable when you validate the corresponding progress status in the billing plan, and provided that the project is set to Launched. The Status field on the scheduled invoice line displays the reference of the budget, task or project selected by default. You can trigger the invoicing process by clicking the Invoice action in the Orders function. You can also trigger it from the Invoices management function by picking scheduled invoices from orders, or using the Schedule invoice generation automatic processing. The invoicing information such as the scheduled invoice status compared to the billing status, as well as the invoice reference is displayed on the schedule and on the billing plan. The schedule is created and saved automatically when you display it, or when the order has been created. Therefore, if you apply a change to the invoicing term after displaying the schedule or after creating the order, this change will not be applied to the schedule. For more information, refer to the Project management (PJM) guide. Click the link that applies to your Sage X3 solution:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Stock by site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to view the stock status of the product at the shipment site of the document line, or for all the sites. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Line text entry | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This function is used to enter a text on the order line which is printed on the order acknowledgment. This text can be initialized on the order line by the product text and propagated to the deliveries and invoices depending on the value of the SALTEXLIN - Product text tracking (VEN chapter, TEX group) general parameter. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Revision management | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This action is only available when an existing revision can be found for the order line. Click on this action to visualize the revision history as table. The lines are displayed by revision number in descending order. On each revision line, most of the information on the order line is displayed and the modified information is in red. The management of revisions is linked to the SALREV - Revision management parameter (VEN chapter, ORD group). When printing the order acknowledgment, you can print a revision number (the last revision number is suggested by default). The information related to a revision are printed. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Price explanation | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to display the details of how the net price of the document line is obtained by application of the different discounts on the gross price of the product. The reasons displayed are used to know any applied price lists. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Quotes | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to open the quote at the origin of the order line. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Service contracts | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This action, only available for a product of the service contract type, is used to view all the contracts generated for the order line. For each contract, the contract number, the contract start date, the contract end date, the contract amount and the contract currency can be inquired. You can access the full description of the service contract:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Configurator | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to access the configurator:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Manual allocation | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
To access this detailed manual allocation action, you must have the Allocation authorization in the orders management function. This function is available regardless of the line allocation type. If the allocation type for the line is Global, a warning message warns the user that the allocation that will be carried out will change the allocation type of the line to Detailed. This action can only be accessed in order modification. You can manually allocate the stock lines (the products present in certain locations or for specific lots, versions...). You can also allocate more than the ordered quantity in the same way as it is used for the entry of the Quantity to be allocated on the order line. The selection list of stock lines is filtered based on picking criteria among which some are defined by default. For versions for example, all the stock lines are displayed by default during the allocation creation - lines are not filtered based on the management rules applying to version statuses (Prototypes, Held, Stopped, etc.). You can modify the filters by clicking the Picking criteria action. This information cannot be accessed when:
If the customer has exceeded its authorized credit level, a message will be displayed requesting confirmation if the user parameter SCDTUNL-Authorization to unblock order (VEN chapter, AUZ group) permits it. If not, it is not be possible to access this function and a blocking message is displayed. If the prepayment has not been made, a message requesting confirmation will be displayed before accessing this function. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Detail valuation | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Work orders | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Order | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Latest products ordered | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use this action to access the last products ordered by the customer. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sales journal traceability | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to access the Sales documents traceability function and view or browse through the hierarchy of documents at the origin of, or issued from, the relevant document. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Assignments | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Multi-level planning | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to access the Multi-level planning function for the product. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product notes | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action in order to open a window displaying the note(s) associated with this product. This information can relate to product availability, additional or substitute products, or a promotional message. This window could open automatically depending on the setup defined when creating the notes. Notes are limited to a screen inquiry and cannot be printed. For further information, see the documentation on Notes. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Valorisation TTC
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use this option to display the detail by fiscal jurisdiction for the selected product. Field descriptions
Block number 1
Grid Taxes
Grid Invoicing elements
Totals
Field descriptions
Grid Invoice elements
Valuation
Click this action to display the detailed fiscal statistics, based on the Sage Sales Tax (SST) tax code. This option is available if the document is imposed using the SST tax code. The calculation detail is stored in the LTAVCR table associated with the document, to fiscal administrations and to the rates imposed by the SST tax code. |
Other information
Quote picking
Use the Quote selection selection panel to convert quotes into orders. The suggested quotes are filtered with respect to the information already entered in the order (site, customer etc.)
One to N quotes can be selected and all or any line of each quote. The quotes that can be selected are the ones which have not been ordered and those with a validity date that has not been exceeded.
When a quote line is selected in an order line, the quote number is displayed on the order line and each quote can be accessed individually from the Actions icon.
In order creation or modification, when the order type is specified on the order header, only the following can be selected by picking:
- quotes sharing the same order type,
- quotes with no order type specified.
Particular case of the payment terms
On a quote, the payment terms may not be entered (a prospect does not have this information which cannot be defined if its entry is not mandatory in the entry transaction). If whilst picking a quote, this does not have a payment condition, the payment condition used is the default payment condition that has been initialized by the system at the time of choosing the sold-to customer or that entered manually. If no payment term had to be entered when creating or modifying the order, an error message is displayed and no order is created as long as this information is not entered.
Order modification
You can modify an order as long as it is not fully closed. Similarly, you can modify each order line as long as the line is not closed. As soon as the order is fully or party delivered, the invoiced customer can no longer be modified. The ordered quantity of each line can be modified provided that the new quantity is not inferior to the previously allocated or delivered quantity.
If you modify an order whose revisions are managed automatically (SALREV - Revision management parameter (VEN chapter, ORD group)), the revision number of the order header is incremented as soon as you save the order. If revisions are managed manually (PURREV - Revision management parameter (VEN chapter, QUO group)), a message asks you if you want to create a revision for this modification. If you answer ‘Yes’, the revision number in the order header is incremented like in an automatic revision generation.
Different warning messages can appear depending on the fields that have been modified:
- When modifying the delivery address in the order header, a message appears suggesting to pass this change on to all the order header fields associated with this ship-to customer, that is to say, the delivery deadline, the delivery priority, the round number, the delivery mode, the contact, the carrier code and the sales representatives. If this change is accepted and thus, the delivery lead time is changed, a message is displayed to indicate that the shipment date has been modified. If parameter LINBPD - Ship-to customer on detail is set to No, the line information linked to the delivery address is also updated. If the parameter LINBPD - Ship-to customer on detail is set to Yes and you answered Yes to the question related to the header field update, a second message is displayed to specify:
- if you want to apply the information of the new delivery address to all the lines (answer Yes),
- if you do not want to apply the information of the new delivery address to all the lines (answer No),
- if you only want to apply the information on the lines with an address code different from the new address code (answer Value).
Particular case:
- If the answer to the first question (Reloading header sections) is No, and the answer to the question Repercussion on the lines is Value, then only the address code and the contact will be loaded on the lines that have an address code different from the new one.
- If the answer to the question Repercussion on the lines is Yes, only the address code and contact will be loaded on all the lines.
- When modifying other fields in the order header, a question will be asked in order to choose whether to apply the modification to all the lines or only to those having the same value as the ones entered in the header. This is true when you modify the fields: Shipment site (for not allocated or not delivered lines), Delivery priority, Requested delivery, Delivery lead time, Shipment date, Delivery mode, Sales rep., Carrier...
- When modifying the order date or quantity of one of the order lines, a message is displayed suggesting the recalculation of the price and any discounts entered or calculated on creation. This message is also displayed when copying the order.
- When modifying the quantity of a line at the origin of a free item, a warning message is displayed.
- When modifying the allocated quantity to enter a quantity superior to the ordered quantity, a warning message is displayed.
- When closing an already closed order line (provided that the order itself is not totally closed), a message appears to suggest canceling the closing of this order line.
- When modifying or deleting an order line linked to a BOM component, a warning message is displayed.
- The modification or closing of an order line related to a BOM parent product triggers a message asking you to decide if the components must also be modified or closed.
- The deletion of the line of an invoice concerning a BOM parent product leads to the display of a message asking whether the components must also be deleted.
Intercompany specificities
In the case of an order generated from a purchase order, the addition of a product line to the is prohibited. Only the addition of a line to the original purchase order can be used to add an order line.
When updating the price, quantity or unit on the purchase order line, the price of the sales order line is updated with respect to the setup of the Price transfer in the Inter-company setup function:
- either by transferring the price from the purchase order,
- or by performing a new price list search.
Order deletion
An order can be deleted even when allocations are linked to the order. A message is displayed to inform you. If you want to proceed with the deletion, the order will be deallocated before it can be deleted. Similarly, for each order line, the deletion can be performed even when the line has been allocated.
You cannot delete an order if at least one line is linked to a billing plan. In that case, the product relates to a project set up with progress billing.
Intercompany specificities: If an order generated from a purchase order, the deletion of the order (or order line) is prohibited. When deleting the purchase order, only the purchase order that the line originated from can be used to delete the order (or the order line).
Order copy
When duplicating an order and modifying the customer code, it may be necessary to reinitialize:
- line texts,
- header and footer texts,
- sales units and sales unit coefficients - stock unit (SAL-STK) of the revaluated product lines, especially when line units apply to customer-specific units. In this case, all other line data is also recalculated.
Line text reinitialization
- If the duplication involves a single customer, the text of the duplicated line remains the same.
- If the duplication involves another customer, the text is reloaded with the sales text of the customer-product, or with the sales text of the product when no customer-product sales text exists.
Header and footer texts reinitialization
- If the duplication involves a single customer, the text remains the same.
- If the duplication involves another customer, the text is reloaded with the acknowledgment text of the customer.
Reinitialization of sales units and coefficients of product lines
SAL-STK coefficients and units of product lines are reinitialized when the original sales unit is not appropriate for the new customer. The processing is as follows:
The system checks if the unit of the line corresponds:
- to the sales unit of the new customer,
- or to the packaging unit (1 or 2) of the new customer,
- or to one of the product units (sales unit, stock unit, packing units).
If the unit present on the line does not correspond to one of the new customer sales units, the system attempts to replace the line unit with one of the following units, successively:
- The sales unit of the customer-product
- The sales unit of the product
- The stock count unit (last resort).
When the system finds an equivalent unit, that unit is taken into account. The system then controls that the SAL-STK conversion factor is the same as the original SAL-STK conversion factor. If the SAL-STK coefficient differs from the original coefficient, the system recalculates the quantity in sales unit so that the quantity in stock unit meets the original one.
If after this calculation, the stock unit quantity is the same as the original one, the system reinitializes:
- The sales unit
- The quantity in sales unit
- The new conversion factor.
Otherwise, the system searches for a new sales unit and recalculates the quantity in sales unit until the quantity in stock unit matches the original one.
Other data recalculation
Changing the sales unit or the quantity in sales unit, or both, leads to the following:
- If the original order has been allocated, the quantity to allocate in sales unit is reinitialized.
- The original quantity in sales unit is reinitialized.
- If the new unit is a customer-product unit and the product-customer record has the same packing code as the line, the reinitialization of the packaging or packaging capacity is not performed.
Otherwise, the packaging or packaging capacity are reinitialized. - If the conversion factor has changed, you need to recalculate:
- At the line level:
- The gross price, net price, net ex-tax price and net tax incl price
- The tax calculation base amounts
- The margin
- The weight and volume
- The amounts.
- At the document level:
- The amounts.
Prices are expressed in sales unit and not in stock unit.
Specific aspects of the 'service contract’ type
It is prohibited to duplicate a sales order for 'service contract’ type products. Lines relating to this type of products are automatically deleted. You need to enter them again.
Kit specificities
For a kit, the sales unit can be the unit of the customer-product or a packaging unit of the customer-product. Duplication can lead to a unit change and to a recalculation of the ordered quantity.
For components, the sales unit is always initialized with the product sales unit. The sales unit and quantity are never modified for this line type.
Reports
By default, the following reports are associated with this function :
ARCCLIENT : Customer order acknowledgement
ARCCLIENT2 : Fixed footer cust order ackn
ARCCLIENT2PI : Preprint cust order acknow
ARCTTC : Cust order acknow - tax inc
ARCTTC2 : Tx-inc fixd footer cst ord ack
ARCTTC2PI : Prepr c. order ackno - tax inc
SCARNETCDE : Valued customer order book
SCARNETQTY : Customer order book
SOHOSTCTL : Sales orders blocked
SORDERE : Sales order list
SORDERL : Detail sales order list
SPROALIV : Products to deliver
This can be changed using a different setup.
This setup is performed at the Customization level of the current object, by associating a report code or a print code to it.
It is possible to further specify this setup:
- By specifying a given report at transaction entry level. If this report matches a print code, the list of reports associated with this print code is also submitted.
The report entered at transaction entry level and the reports associated with the print code are automatically submitted in creation mode only. - At a more detailed level, by associating a print template with the BP. This template mentions the report to be used in priority for the printing of each document, as well as the expected number of copies.
If the number of copies is not specified, or if there is no print template associated with the BP, the number of copies defined for the Destination printer is chosen. If the number of copies is not specified for the destination printer, then a single copy is printed by default.
Specific actions
Click this action to directly allocate all the order lines: the ordered quantity is considered as quantity to allocate. The allocation of order lines depends on the allocation type specified in the order line. This action is active if you have the Allocation authorization available in the order management function. If the allocation has the global type, a reservation is made based on the available stock for the product and the allocation rule for the category to which the product belongs. This rule is used to determine by large status group those that are authorized for the allocation. If the allocation is of the detailed type, a reservation is carried out on the stock objects (Lot, Serial number, Status, Location, Packing unit) based on the allocation rule for the category to which the product belongs. Filters that may have been entered in the order lines also affect the result of the detailed allocation. Two exclusive filters can be entered. This is a filter on the lot number and on the status. In the allocation algorithm, if no stock object corresponds to these exclusive additional filters, a shortage will be generated. In the case of shortage, only the available quantity is directly allocated, the balance is stored in the shortage quantity counter and can be allocated (as priority) once the quantity in the stock is sufficient. The shortage lines can also be processed as a priority by the automatic allocation function. When the signature circuit is managed (APPSOH - Order signature management parameter), the allocation of the sales orders that are not Totally signed can be prohibited via the setup (parameter SOHAPPALL - Unsigned order allocation).
Any addition/deletion of line or any modification of field having an impact on the approval status (canceled approval), will generate an automatic deallocation of the order (a list of these fields is provided in the Order approvals management rule: SOHSIG). Specificities linked to sales kitsAllocations on the parent product and on components cannot be distinguished. This means that if you allocate the parent product, the components are allocated up to the level of the quantity to be allocated on the parent product. If the stock is insufficient for certain components or for the parent product, shortages will automatically be generated irrespective of the value of the GENSHT - Shortage generation parameter (STO chapter/ MIS group). For components: the total Allocated quantity + Shortage quantity divided by the Link quantity is always equal to the sum Allocated quantity + Shortage quantity of the component. Rule concerning the allocation and the decimalization of the unitWhen an allocation is carried out on a non-decimalized unit, for example a container of 10 units, if you cannot fully allocate the unit, the system generates a complete shortage. Sales units are always allocated as a whole. This function cannot be accessed if the customer is blocked, except if the order has been unblocked. If the customer has exceeded its authorized credit level, a message is displayed requesting confirmation if the user parameter SCDTUNL-Authorization to unblock order (VEN chapter/AUZ group) permits it. Otherwise, this function cannot be accessed and a blocking message is displayed. If the prepayment is not made, a message requesting confirmation is displayed before accessing this function.
This function displays the allocation status of the order:
This function also provides allocation options. You can:
Click Detail to view the details of already allocated quantity for each line. If the order has the detailed allocation type, it is also possible to see the lots, sub-lots, serial numbers, locations, stock status, lot expiration date and free identifiers for each line of allocated stock. |
Click this action to link the preparation from the order management when the order is of the Normal or Loan category.
If delivery methods and carriers are different, a warning message allows you to decide whether you want to carry out only one single preparation. The information from the first line to prepare is considered. Otherwise, you need to use the preparation list generation function. |
Use this action to link the delivery from the order management. This action cannot be accessed:
If delivery methods and carriers are different, a warning message allows you to decide whether you want to carry out only one single delivery. The information from the first line to deliver is considered. Otherwise, you need to use the automatic shipment generation function or pick the orders in delivery management. For sales kits, if one component is unavailable, the kit can only be delivered in full if:
When signatures are managed (parameter APPSOH - Order signature management) and the order meets the set signature rule, this action is not available and the order cannot be turned into a delivery as long as the order is not Totally signed. |
Use this action to directly link the invoicing from the order management.
When signatures are managed (parameter APPSOH - Order signature management) and the order meets the set signature rule, this action is not available and the order cannot be turned into an invoice as long as the invoice is not Totally signed or automatically signed. |
Click this action to directly run the calculation and issue of an invoice of the Pro forma type for this order. When order lines apply to a service or generic non-deliverable product whose invoicing is done through an invoicing schedule, the pro forma invoice is generated following the same process as the direct invoicing of orders. The scheduled invoices are not updated. This action can only be accessed when the order is neither signed nor invoiced, even partly. |
Use this action to completely close an order (if the order has allocated lines, a warning message is displayed; if you say yes, the lines will be deallocated in the process). This functionality is similar to the order line closing. When the CCLRENORD - Order closing reason entry parameter (VEN chapter, ORD group) is enabled, you can enter the reason for closing the order. The reasons can be set up in miscellaneous table number 201. A closing date will also be assigned (this is the system date at the time of order closing). This reason and the closing date appear in the order header (Management section) and is copied to all the open lines. The lines that are already closed keep their reason and closing date. When signatures are managed (parameter APPSOH - Order signature management) and the order complies with the set signature rule, the order is automatically closed if it has been rejected from a signer in the workflow and the SOHAPPCLE - Order closing if signature rejection parameter authorizes it. Intercompany specificitiesIn the case of an order generated from a purchase order, the manual closing of the order is prohibited. Only the purchase order at the origin of this order can be manually closed (by the closing of the purchase order). |
This action is only available when revisions are managed (SALREV - Revision management parameter (VEN chapter, ORD group)). Click this action in order to open a window displaying the revisions applied to the order. The revision list is displayed in the selection panel, sorted by descending revision number. Click on a revision to display all the order’s information. Modified information are displayed in red. When an order with a revision is modified is modified, the following tables are updated to archive the information modified in revisions:
Click Resynchronization to resynchronize the display in this window with the information from the history tables. |
Action menu
Click this action to display the hold status:
|
Use this action to enter an order header text. This text is printed on the order acknowledgment. Based on the SALTEXORD - Order text tracking parameter (VEN chapter, TEX group), the header text can be initialized by the acknowledgment text entered on the customer record.
During the transformation of a document, this text is never propagated to the other documents.
|
Use this action to enter an order footer text. This text is printed on the order acknowledgment. Based on the SALTEXORD - Order text tracking parameter (VEN chapter, TEX group), the footer text can be initialized by the acknowledgment text entered on the customer record. During the transformation of a document, this text is never propagated to the other documents. |
Order addressClick this action to view or modify the address of the ship-to customer. This address is used when printing the invoice. Invoicing addressClick this action to access the invoicing address of the customer and to modify it when needed. Upon the transformation from a quote into an order, the content of this address is populated with:
Delivery address
Click this action to:
If the price list is defined with respect to the country code and/or the geographical subdivision code and that the information is modified, a dialog box opens suggesting a recalculation of the discounts and prices. Answer Yes to trigger a price list search and a new assignment of prices and discounts. |
This action is subject to the EDIX3 - Dematerialization activity code. |
This action is subject to the EDIX3 - Dematerialization activity code. It can only be accessed when the document has been validated and if you are granted the proper functional authorizations. You use it to generate the corresponding EDI document. |
Use this option to generate a custom purchase back-to-back order, without using the automatic generation function of Purchase back-to-back orders. As a general rule, the back-to-back supplier is initialized with the default back-to-back supplier defined in the Product-Site record. Purchase back-to-back orders are prohibited when the PURCTLPRI0 - Purchase price existence control parameter (ACH chapter, PRI group) is set to Control and the product has no price:
Technical Block number 1
Intrastat information
Physical flow
Adjustment flow
|
Use this option to generate a custom purchase back-to-back order, without using the automatic generation function of Purchase back-to-back orders. As a general rule, the back-to-back supplier is initialized with the default back-to-back supplier defined in the Product-Site record. Purchase back-to-back orders are prohibited when the PURCTLPRI0 - Purchase price existence control parameter (ACH chapter, PRI group) is set to Control and the product has no price:
|
Click this option to generate a back-to-back work order individually, without using the automatic generation function of Manufacturing automatic POs. If the product (BOM) is version-managed, the system suggests the BOM version and routing to be used systematically when a work order is generated. If the version of the product was not specified on the Sales order line the system selects the BOM version. The version valid on the calculated (scheduled) work order start date is used. If the suggested routing is version-managed the system also selects the routing version valid on the scheduled start date. If the suggested BOM or routing version is not consistent with the calculated work order start date, the work order is generated, but not scheduled. This is because there is an inconsistency between the work order start date and the selected BOM or route version. |
Click this action to view the prepayments to be made (initialized by the payment condition) and to modify or even create the prepayment due dates for this order. In this grid, it is possible to modify the payment method, due date, tax code, planned issue date and prepayment to be deducted fields. The issue of the prepayment is carried out by clicking the Issue action from the Actions icon, or using the dedicated function Issue prepayments. The To be issued field is set to Yes. When the signature circuit is managed (parameter APPSOH - Management of order signatures), the prepayments present on a purchase order cannot be issued as long as the order has not been Totally signed. If, following a modification, a Totally signed order moves back to the Not signed or Partially signed status, the prepayments that may have been issued and posted are not modified. Note: the addition or modification of a prepayment are not considered as modifications that can cancel a signature.The automatic printing and document sections are loaded with the transaction. They cannot be modified. The prepayment requests will be printed after the validation of the window if the prepayments have been issued and if the document is entered. After printing, the field To be issued has for value No and the field Issued has for value Yes. It is no longer possible to modify the prepayment outside of the amount to be deducted. Emitting a prepayment again can be done by right-clicking re-print. The To be issued field is set to Yes. The prepayment is reprinted at the validation of the window (for more details on the re-printing of prepayment request, read the documentation of the FACACC9 and FACACC92 reports). When creating prepayment open items, the payment approval level is automatically set at maximum level. It needed, it is possible to modify the payment approval at Open item management level. |
Click this action to display a window detailing, by order line, the quantitative information and the different documents generated from this order line. Generated back-to-back orders (Jump to action available to the purchase order or work order), completed deliveries (Jump to action available on each invoice). |
Click this action to view the order entry transaction used. |
This option is inactive. This is only used in a Web-specific context. |
This option gives access, via tunnel, to the inquiry function Entry traceability that makes it possible to visualize and browse into the hierarchy of original entries or coming from the document. |
Click this action to access the View routes function, that can be used to:
|
Use this action to select and process transactions. This window opens when the payment method tied to the payment entry transaction is set up for credit card processing. This option is available only if the SEPP activity code - Credit card integration is activated and if the payment method associated with the payment terms for the entry transaction has the Credit card processing check box selected. The document's bank/currency must be the same as the payment card's processing code bank/currency. This screens displays information for payments methods for a sales order or shipment including:
In this screen:
Changes that increase document totals:
|
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Inactive customerThis message is displayed in the following contexts:
- When entering the sold-to customer but the customer is declared as Non active in the customer record.
- When entering the bill-to customer but the customer is declared as Non active in the customer record.
This message is displayed when entering an ‘Loan’ order in the following contexts:
- When the customer loan authorization is set to No on their sold-to customer record.
- When the product loan authorization is set to No in the product record (Product-sales section).
This message is displayed when the shipment date entered is less than the order date. An identical control is performed on the requested delivery line. These dates must be greater than or equal to the order date.
Unavailable period from ../../.. to ../../..This message is displayed in the following contexts:
- The calculated shipping date falls within an unavailability period of the shipment site.
- The planned delivery date falls within one of the unavailability periods of the ship-to customer.
This message is displayed when the shipment site does not belong to the same legal company as the sales site. To correct this problem, select a site from the list.
Product does not exist for this siteThis message is displayed when the product is managed in stock and has not been declared for the shipment site (Product-site record missing).
Prohibited productThis message is displayed when the product entered is a product declared as 'Prohibited' for this customer via the price list management. To correct this problem, enter another product reference.
Sale unit unknown for this productThis message is displayed when the entered sales unit does not match any sales unit or packing unit defined in the Product or Customer-product records. To correct this problem, select a unit from those suggested.
999.99 Net price < minimum price 999.99This message appears when the calculated net price is lower than the lower limit price defined in the Product record. The threshold price is displayed in the order currency to facilitate the comparison. This message can be a simple warning message or a blocking message depending on the value given to the user parameter SDACLOK - Non-blocking control, price, margin, qty (VEN Chapter/ AUZ group). It can be displayed on entry or modification of several fields (site, price, discounts, charges, etc.).
99.99 Margin less than minimum margin of 99.99%This message is displayed when the calculated margin is less than the brand rate defined in the Product record. This message can be a simple warning message or a blocking message depending on the value given to the user parameter SDACLOK - Non-blocking control, price, margin, qty (VEN chapter, AUZ group). It can be displayed during the entry or modification of several fields (price, discounts, charge....).
Quantity lower than the delivered/allocated quantityThis message is displayed when the quantity is modified if the new quantity entered is less than the quantity already allocated (Allocated Qty + Shortage Qty) or delivered (Shipped Qty + Qty in delivery).
This is not a purchased product: Direct order impossibleThis message is displayed when an order line is opened by a back-to-back purchase order (Delivery method field) and the entered product is not a purchase product.
Authorized credit level reached 999.99 EURThis message is displayed after line entry when the authorized credit level for the bill-to customer has been reached. The authorized credit is displayed in the invoice currency. This message can be a simple warning message or a blocking message depending on the value given to the user parameter SCDTUNL - Authorization to unblock order (VEN chapter, AUZ group).
For intersite orders, the message display control for exceeded customer credit can be deactivated through the parameter CTLBETFCY - Credit&price intersite ctrl.
Kit not generated for product XXXThis message is displayed after order line entry for a Kit parent product or BOM parent product product type when a problem prevents the generation of the order lines for this parent product components.
The possible reasons are:
- There is no code for this parent product.
- There is no valid code for this parent product.
- None of the suggested codes has been selected.
The order line could not be generated because the component is an unsold product (does not exist in the Product-sales) or because it is prohibited. In these cases, the following warning messages can be displayed and you can:
- Continue: the order line is not generated for this component and the BOM continues to be processed,
- Cancel: a new message is displayed, the order lines are not generated for the various components and the parent product is considered as a normal product for this order.
This message is displayed after order line entry when the maximum number of order lines has been reached in the following contexts:
- When generating order lines for the components of a BOM or Kit parent product.
- In automatic generation of a free item line.
- When picking quote lines.
This message is displayed during the creation or modification of the order when the total amount of the order is less than the minimum amount defined at the level of the sold-to customer record. This message can be a simple warning message or a blocking message depending on the value given to the user parameter SDACLOK - Non-blocking control, price, margin, qty (VEN chapter, AUZ group).
No line entered. Update impossible.This message is displayed when saving the order and no line has been entered. The order is not created.
Processing not possible: Closing not authorizedThis message is displayed if you try to close an order line but the closing is not authorized (Closing authorization check box cleared in the customer record and/or in the order header, Delivery section).
Processing not possible: This order is closedThis message is displayed when an order line is modified but the order is already fully closed.
Processing not possible: this line is closedThis message is displayed when a line already closed is modified.
Processing not possible: Component of a kitThis message is displayed when you try to modify or delete an order line of the component type from a kit.
Order no. product XXX. The line is managed with direct orders and the purchase order is not generated: Line creation impossible.This message is displayed when you click the Delivery action and one of the lines is managed by back-to-back order and the associated purchase order has not been generated.
There are some non-allocated direct order lines. Do you want to process these lines?This message is displayed when you click the Delivery action and one of the lines is managed by back-to-back order and it has not been received.
Order XXX: Order delivery complete. Product YYY Delivery date ../../.. : This line is not delivered. Continue?This warning message is displayed on delivery when the order lines are not fully allocated but the delivery method for the order is Complete order. Not delivered lines are displayed.
Order XXX: Line delivery complete. Product YYY Delivery date ../../.. : This line is partially delivered. Do you want to continue?This warning message is displayed at the time of delivery for those lines in the order that have not been totally allocated or where the available stock is insufficient whilst the delivery mode for the order is Complete order line.
Site XXX Product YYY Location ZZZ: Stock pending put-away. Stock line incomplete: Lot, sublot. Order no. Product YYY The quantity allocated cannot be shipped.This message is displayed when you attempt to create a delivery from an order by clicking Delivery. It is not possible to create a shipment from an allocated order if the stock lines allocated to the order are pending storage and if the stock has not been identified yet (lot, sub-lot, serial number). If the stock is identified but is still pending storage, the delivery can be created.
Setup of the signature rules does not exist for the companyThis message appears during the entry of the order site, when the signature management is active and no setup exists for the signature rule for the legal company to which the order site is attached.
Order signed. Modification?This message is displayed when fields have been modified but the document has already been signed, in part or in full. The posting of the modification does not trigger the update of the signature circuit. The existing signatures are kept.
Cancellation of the existing signaturesThis message is displayed when adding/deleting a line, modifying fields, or manually closing the order, but the order has already been signed, in part or in full. The validation of the modification triggers the cancellation of the existing signatures and the reinitialization of the signature management.
Oder allocated and no allocation of unsigned orders: the order is to be deallocated automatically.This message is displayed after the cancellation of the signature circuit has been accepted (see message above) if one of the following conditions is met:
- The allocation of an unsigned order is prohibited: the SOHAPPALL- Allocation of unsigned order parameter is set to No.
- The allocation of an unsigned order is authorized but the product WIP management is not authorized for unsigned orders: the SOHAPPORD parameter is set to No.
This warning or blocking message is displayed when inconsistencies are reported on:
- The tax codes of the document lines
- The tax codes of the document invoicing elements.
The consistency check on tax codes is performed based on the value of the CTLTAX - Tax codes control parameter (VEN chapter, VAT group) (no control, non blocking control, blocking control).
After the message is displayed, a log file details the errors that occurred during the consistency check.
Tables used
Refer to documentation Implementation