Open orders

Code of the site issuing the order (request for quote, purchase request, order, subcontract order etc.).
This field is mandatory. It is initialized by default by the purchase site associated with your function profile.
You can modify this code by selecting a code from the list of authorized sites.

Each order has its own order number. It is used to identify it.

If the order sequence number is to be manually assigned, the user must also enter an order number. Where the order number sequence assignment is automatic, a number will be assigned at the end of the creation.

When you copy a purchase order and its order date is different from the current date, a messages suggests that you recalculate the prices and discounts according to the new order date.

This is the last revision number entered for the open order. When a signed, printed order is modified and the PURREV setup activates the revision management, the user will be asked whether they wish the modification to generate a revision.
If this is the case, the previous values of the modified elements in the order will be added to the history and the revision number will be incremented.

The supplier code entered must meet particular conditions: be active and not of the prospect type. From this field, you can:

• directly enter the supplier code whose existence is checked in the Suppliers file,
• click the quick Supplier selection from the Actions icon to:
• Select a supplier from the file;
• Create a supplier in the file (according to the user's access rights);
• View the notes linked to the supplier.

When the supplier entered is of the type "Miscellaneous", a window automatically opens for the entry of the address. When the entered supplier is of the 'Normal' type, you can view and potentially modify the address from the Actions icon, since the supplier code has been entered.

Following the entry of the supplier, a message is displayed when the supplier is declared "on-hold". This can be a blocking message or a simple warning according to the value given to the dispute code in the supplier record. 

In order duplication, changing suppliers is not authorized.

Case of inter-site reorder contracts: You can create inter-site contracts to manage reorders between sites:
Record the sites as customer BP and/or supplier BP. Requesting sites are referenced as Customers and reordering site as Suppliers.

When you create a purchase contract and enter a supplier of the inter-site type, the contract is considered as an inter-site contract. This means that when creating the purchase contract, the associated sales contract is automatically created. This contract is identical to the purchase contract. The customer for this sales contract will be the Customer associated with the requesting site that has issued the purchase contract.

The master contract is the purchase contract. A delivery call-off entered on the purchase contract automatically creates the delivery request in the sales contract. Any modification carried out on a delivery call-off is automatically duplicated on the delivery request of the sales contract (modification of the quantity, delivery call-off balance, deletion of the delivery call-off). At the level of the delivery request of the sales contract, no modification is possible, everything is managed by the purchase contract.

There is a case where the purchase delivery call-off can be modified by the sales delivery request. If a delivery request is partially delivered, the delivery request of the sales contract is split into two delivery requests. The first part applies to the delivered amount, the second to the remainder. In fact, the purchase delivery call-off will also be split into two delivery call-offs corresponding to the sales delivery requests.

Inter-company specificities: Within the framework of an inter-site or inter-company open order, the supplier needs to be declared as being of the inter-site type and the site associated with this supplier must be a sales site (it defines the sales site in the mirror sales contract). The purchase site at the origin of the open order must be able to identify an inter-site customer that will serve to define the reciprocal customer sales open order.

When the supplier is identified as being an inter-site supplier, the inter-site check box in the open order is automatically selected. If the site associated with the supplier belongs to another company than the purchase site of the order, the inter-company check box is also selected.

A warning message can be displayed in this context, if the customer linked to the purchase site is blocked. The generated sales order will display a blocked status. The inter-site orders are not themselves concerned with this operation. The WIP order book is not managed for the internal flows.

This information cannot be modified and specifies whether the open order has the type inter-company. When the order concerns an inter-company supplier (site in a different company), an invoice can be generated.

This information cannot be modified and specifies whether the open order has the type inter-site. When the order concerns an inter-site supplier (site in the same company) it cannot be invoiced.

It is initialized by default to the current date

This is the sales site associated with the inter-site supplier.

This field is used to enter the invoicing supplier code, initialized by default to the supplier code entered in the header.
The supplier can be another supplier chosen from the supplier table.

This field used to indicate an invoicing address code for the invoicing supplier.
By default, this is the address code defined in the order supplier record for the invoicing supplier. It is possible to choose another address code for the invoicing supplier.

This field is used to enter the paid supplier code, initialized by default to the supplier code entered in the header. The supplier can be another supplier chosen from the supplier table.

This field used to indicate a payment address code for the paid supplier. By default, this is the address code defined in the order supplier record for the paid supplier. It is possible to choose another address code for the paid supplier.

Use this field to enter a project code.
The management of this code depends on the value of the CTLOPPCOD - Mandatory project control parameter (TC chapter - MIS group).

• When the value is No, it may be a code selected freely.
• When its value is Yes, an existence check is systematically applies to the entered project code.
  You can use the Selection icon to display the list of available project codes.

The management rules of this field are based on the PJTSNGDOC - One project by document- parameter (TC chapter, MIS group).

• When this parameter is set to Yes, the management of multiple projects is prohibited.
  The project code is always the same on the document header and on the lines.
  The project code you enter in the header is always used on the document lines and cannot be modified.
  In case of a document transformation, it is loaded with the project code of the lines of the first selected document and cannot be modified.
  Additional lines must have the same project code.
  If you do not enter a project code but the conditions are met for the automatic opening of the requirements window, then this window will display all the requirements that match the entered criteria. The requirements can relate to various project codes. If you click Include all, the project code of the first line is used to load the order project code: only the lines having the same project code as the first line are selected.
  If you modify the document header project code, this code is automatically used on all the lines.
  
• When this parameter is set to Yes, the management of multiple projects is authorized.
  In direct creation, the project code you enter in the document header is used to initialize the project code of the document lines.
  You can only modify the project code of lines when the following conditions are met:
  - the entry of this field is authorized by the entry transaction being used,
  - the product line is not subject to a delivery request.
  
  If you modify the header project code, a dialog box opens and suggests to transfer this code to the lines of the document, according to the following options:
• Yes: the project code is used on all lines, except from the ones that have already been subject to a delivery request.
• No: the project code is not transferred to the lines.
• Yes if same value: the project code is only used on the lines that have already been subject to a delivery request.

When an analytical dimension type is used in the Project management tracking, any modification of the project code on the document header leads to reinitializing the dimension code of this dimension type on the document header and on the invoicing elements, based on the Default dimensions setup. If the project code is used onto the lines, the dimension code of impacted lines is also reset.

Inter-company specificities: for an inter-site open order, the project code is automatically sent to the generated sales order line. However, it is not sent for an inter-company open order.

Start date for the contract validity.

This information is initialized to the supplier entered in the order header. It is used to identify the supplier's payment method as well as the payment scheduling.
This information remains modifiable but is mandatory. When managing this table, it is possible to simulate the calculation rules that will be applied in entry mode.

The discount code is used to identify a series of discount and charge rates to be applied to a payment according to a number of early or late days with respect to the due date.
The discount code is initialized using the discount code of the invoicing supplier. It can still be modified.
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.

Specificities linked to inter-companies: for an intercompany invoice generated from a sales invoices, the payment condition is intialized from the one of the sales invoice.

Code of the currency in which the invoice prices and amounts are expressed. This field is initialized by default with the currency code of the BP record. This field is only modifiable in creation or copy mode.

When the BUYFLT - Filter by buyer parameter (ACH chapter, AUZ group) is set to Yes, the Buyer code is set to the user code and its entry is mandatory.

Depending on the entry transaction used, this field may be hidden. In this case, it is the user code that is used as default value.

From this field, the Actions icon gives you access to the supplier's detailed address and can be used to select an alternative address for the supplier if necessary. This is the address to which the order document will be sent.

This is the storage site code from which the customer is generally delivered. This site, which is controlled in the site table, must be identified as a warehouse.

This information can only be accessed if the order is of the inter-company or inter-site type. It is used to indicated which shipping site will be used by the sales company that the inter-site/inter-company supplier identified. It will then serve to initialize the shipment site for each line of the purchase order. It is mandatory in this context.

The shipment site is initialized by order of priority, as follows:

• usual shipment site defined in the delivery address identified by the receiving site previously calculated is used. It must belong to the supplier's company,
• site identified by the supplier if it is a warehouse site.

If after this search, the site is still not identified, you must then manually enter it. A control is applied to check if the entered site belongs to the same company as the supplier site and if the site is a storing site. The Actions icon is used to view all the sites available for selection.

Specificities linked to automatically-generated purchase orders: if the shipment site is still not identified after the execution of the previous steps, the shipment site is initialized using the first warehouse site found, in alphabetical order, in the list of storage sites for the company identified by the supplier.

When generating the corresponding sales order, the shipping site of the sales order header is equal to the site defined here.

This mandatory information is initialized by default to the supplier entered in the order header. It describes how the goods are transported. This information is used namely in the Exchange of goods declaration (Intrastat).
The transport method determined by the delivery method is shown on the order document.

From this field, you can directly enter a delivery method whose existence is controlled in the delivery method table or you can use the Actions icon to:

• select a shipment method from the table,
• create, according to the user's authorizations, a shipment method in the table.

Inter-company specificities In the case of an inter-company or inter-site order, the delivery method of the generated sales order is initialized to the delivery method entered in the purchase order if the delivery method is not entered in the ship-to customer. The ship-to customer for the sales order is determined by the delivery address identifying the receipt site for the purchase order.

This is the carrier in charge of transporting the goods. It is initialized to the supplier's carrier entered in the order header. A selection window is used to choose another carrier.
It is also possible to access the carrier table if the user's authorizations allow it.

This information is mandatory and is initialized to the tax rule associated with the supplier entered in the order header. It is used to define the tax rule to be applied to the order and is used to determine the tax codes to be used for the product lines. This information is controlled by the miscellaneous table "BP tax rules".

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

This field repeats the title of the dimension type.

The analytical dimensions are initialized in compliance with the Default dimensions setup (POH dimension code). These dimension codes can be modified manually if authorized by the transaction.

When an analytical dimension type is used for the Project management tracking, any modification of the project code leads to the dimension code of this dimension type being reset based on the Default dimensions setup. If the project code is used onto the lines, the dimension code of impacted lines is also reset.

This information is used to identify if the open order has been printed. It cannot be printed until it is totally signed, or if there is no signature management or if the signature is automatic.

This information is not used in the open orders. An open order is due or not (validity date).

This information is used to identify the situation of the open order from the perspective of the receipt of goods. The possible values are: 'No', 'Partially'.

This information is used to identify the situation of the open order from the perspective of the receipt of goods. The possible values are: 'No', 'Partially'.