Orders

• Order site (field POHFCY)

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.

• Intersite (field BETFCY)

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

 Note:
In the case of an inter-site order, the calculation of the purchase cost and of the stock cost does not take into account the line amount, non-deductible taxes and invoicing elements.
For the stock cost calculation, the invoicing elements can be taken into account. To do so, set theBETFCYCST - Integration of invoicing elementsparameter to Yes (ACH chapter, COS group).

• Intercompany (field BETCPY)

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

• field POHNUM

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.

• Revision no. (field REVNUM)

This field cannot be entered. It is only loaded when order revisions are managed (PURREV - Revision management parameter (ACH chapter, ORD group)). It displays the last revision number created for the order.

When you modify a signed and printed order, the original values (before modification) are kept in the history of revisions, and the revision number is incremented:

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

• Order date (field ORDDAT)

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

• Supplier (field BPSNUM)

To enter the supplier, enter the supplier code or click the Actions icon to:

• Select a supplier in the file.
• Select a supplier from the list of suppliers available for the product-site.
• Select a back-to-back supplier from the list of back-to-back suppliers available for the product-site, in the case of a back-to-back product.
• Create, according to the user's access rights, a supplier in the file.
• View the notes linked to the supplier.
• View the list of the last order prices.

This supplier cannot be defined as a ‘Prospect’ and must be ‘Active’.

When the supplier entered is of the Miscellaneous type, a window automatically opens for the address to be entered. When the entered supplier is a Normalsupplier, you can view and potentially modify the address from the Actionsicon, as soon as the supplier code has been entered.

After entering or modifying the supplier, the following messages may display:

• When the supplier is declared to be 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.
• 
  
• When the order for the product is blocked for this supplier, or for this supplier on this particular receiving site. This can be a blocking message or a simple warning according to the value of the blocking code in the Product-Supplier or Product-Site record.
• When the product is not referenced by this supplier. This message can be blocking or a simple warning according to the choice made at the level of the ITMBPS - Supplier referencing (ACH chapter, REF group) general parameter.
• When the receipt product-site is not referenced by this supplier. This can be a blocking message or a simple warning according to the value of the ITMBPSFCY - Supplier site referencing parameter. If this message is blocking, you can still proceed with your entry but the Receiving site field must be set as available for entry for the entry transaction. In this case, the Receiving site field is emptied. You must then enter a site where the product-supplier is referenced, or for which the ITMBPSFCY - Supplier-site referencing parameter is not defined as blocking.
  This control does not apply to inter-site orders.
• When the supplier purchase unit is different from the entered unit, a message is displayed and you can decide whether to perform a conversion.

If the supplier is modified and its units are different from those of the former supplier, the message "Do you want to order in US ?" is displayed. This enables the user to avoid any price setting inconsistency and keep a consistent order unit for the supplier.

• - If the answer is Yes, the order unit is readjusted into stock unit.
• - If the answer is No, the quantities are readjusted keeping the supplier units.

In order duplication, changing suppliers is not authorized.

Inter-company specificities: Within the framework of an inter-site or inter-company 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 source of the order must determine an inter-site customer so as to define the ship-to customer on the corresponding sales order.

When the supplier is identified as being an inter-site supplier, the inter-site flag of the 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 flag 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 displays a blocked status. The inter-site orders are not themselves concerned with this operation. No WIP is managed for internal flows.

• field BPRNAM

• Bill-by supplier (field BPSINV)

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.

• field BPAINV

This field is 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.

• Pay-to (field BPRPAY)

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.

• field BPAPAY

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 pay-to supplier. It is possible to choose another address code for the paid supplier.

• Internal reference (field ORDREF)

This field is used to enter an internal reference for the order that will be shown on the order document sent to the supplier.

From this field, the contextual button gives 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.

• Project (field PJTH)

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.
  In direct creation, the project code you enter on the header is always used on the document lines and cannot be modified.
  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.
  In case of a document transformation, the project code entered on the header is used to filter the documents available for selection and picking. If not project code is entered, it is automatically loaded with the project code of the first selected document.
  If you modify the document header project code, this code is automatically used on all the lines. A message is displayed and suggests to update the prices/discounts on lines. The update only applies to lines which are not received and not closed.
  
• When this parameter is set to Yes, the management of multiple projects is authorized.
  In direct creation, the project code you enter on the document header is used to initialize the project code of the document lines and can be modified.
  In case of document transformation, the project code entered on the header is only used as the default values of lines with no project code.
  
  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 transferred to all lines. A second message is displayed and suggests to update the prices/discounts calculated on the lines. The update only applies to lines which are not received and not closed.
• No: the project code is not transferred to the lines.
• Yes if same value: the project code is only transferred to the lines associated to the former project code.
  The project code used on the lines can be the same as that already used on the other lines. As the system is not able to differentiate these lines, no price/discount update is suggested or performed so not to overwrite the prices that the user may have entered, which do not originate from the price list.

When the order has been generated using a back-to-back order from a sales order, the project code is automatically loaded based on the code of the sales order header.
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.

• Payment term (field PTE)

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.

From this field, it is possible to directly enter a payment code whose existence is controlled in the corresponding table or to use the contextual button to:

• select a payment code from the table,
• create, according to the user's authorizations, a payment code in the table,
• simulate a calculation of the open items,
• Access the supplier's detailed address and select an alternative address for the supplier if necessary. This is the address to which the order document will be sent.

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.

• Settlement discount (field DEP)

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.

• Buyer (field BUY)

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.

• Currency (field CUR)

This field indicates the code of the currency in which the order or receipt prices and amounts are expressed.

This mandatory information is initialized to the currency of the supplier to which the order is addressed. Provided the order is not yet created, it is possible to modify this currency. If order lines have been entered, or during the copy of an order, a question will be posed to the user about whether to re-calculate the prices and discounts depending on the price lists. If the user decides not to apply the price lists, the prices and discounts will be simply converted into the new currency at the rate determined by the exchange rate type and the order date.
The change of currency is forbidden if at least one line with a cost structure has already been entered.

From this field, it is possible to directly enter a currency code whose existence is controlled in the currency table or to use the contextual button to:

• select a currency from the table,
• create, according to the user's authorizations, a currency code in the table.
• Access the supplier's detailed address and select an alternative address for the supplier if necessary. This is the address to which the order document will be sent.

Specificities linked to the inter-company: Within the framework of an inter-company or inter-site order, the currency entered in the sales order generated is initialized to the currency of the customer associated with the purchase site.

• Rate type (field CHGTYP)

This field is controlled by local menu and can take the following values: current exchange rate/monthly exchange rate/average exchange rate.

The exchange rate type proposed by default is the exchange rate type associated with the supplier entered in the order header. As long as the order has not been created, it can be modified except when a line with a cost structure has already been entered.

An exchange rate type is used to determine the currency exchange rate in the exchange rate table taking into account the order date. This information is used to determine the prices and discounts on the basis of the price lists authorizing the conversion between currencies.

If order lines have been entered, or during the copy of an order, a question will be posed to the user about whether to re-calculate the prices and discounts depending on the price lists. If the user decides not to apply the price lists, the prices and discounts will be simply converted into the new currency at the rate determined by the exchange rate type and the order date.

If the currency is equal to the company currency, the exchange rate type will not be accessible since it will have no influence in this context.

• Tax rule (field VACBPR)

This information is mandatory and is initialized to the tax rule associated to 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 BP tax rulemiscellaneous table.

Only a tax rule consistent with the legislation and group of the company associated with the site can be entered.
The general principles linked to the multi-legislation setup aredetailed Here.

From this field, you can:

• select a Tax rule in the table,
• create, according to the authorizations held by the user, a tax rule in the table.

If this information is modified during the creation of the order or on its duplication and if the order lines exist, a question will be posed to the user about whether to re-calculate the prices and discounts for the order lines, namely when the price lists are expressed including taxes. When the order is created, this information is no longer accessible.

Inter-company specificities: In the case of an inter-company or inter-site order, the tax rule entered in the generated sales order is initialized with the tax rule of the customer associated with the purchase site.

• field PRHFCYLIB

• Invoicing site (field INVFCY)

Site for which the invoices of this order are intended, initialized by default by the code of the financial site associated with the order site.
 This invoicing site is necessarily a financial site belonging to the same legal company as the order site.
This field is managed depending on the setup of theentry transaction of the subcontract order.

Inter-company specificities: In the case of an inter-company or inter-site order, the invoicing site is initialized to the site associated with the bill-to customer defined in the customer record for the purchase site. The invoicing site can be modified on the condition that it is associated with a customer. At the time of the sales order generation, the bill-to customer and the pay-by customer will be initialized to the customer associated with the invoicing site entered. In the case of a modification, the sales order will automatically be updated.

• Shipment site (field STOFCY)

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.

• Carrier (field BPTNUM)

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.

Inter-company specificities: In the case of an inter-company or inter-site order, the carrier entered in the generated sales order is initialized to the carrier from the ship-to customer and not by the information entered at this level (except if the carrier has not been entered in the ship-to customer).

• Delivery mode (field MDL)

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.

• Incoterm (field EECICT2)

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 an order, a receipt or an invoice, the Incoterm code is initialized by default with the Incoterm code of the supplier.
For orders, receipts and invoices, the Incoterm code is unique to the specific document.

You can jump to the Incoterm management function. 

When a product using a cost structure is entered on the document, you cannot change the selected Incoterm. This rule applies when creating, modifying or duplicating an order.

 The freight terms code and city/town can also be accessed in the Options / Customs information menu.

• Incoterm town (field ICTCTY2)

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.

• Grouping code (field GPGCOD)

This field, managed with an entry transaction, is used to indicate a freely selected code used to identify and group the documents having the same code. It is used, for instance, when importing goods, to accumulate the various documents corresponding to orders that have been grouped into the same journey for logistics and cost optimization reasons.
The orders that have been grouped can be viewed in the List of orders inquiry function and the PURFCS - Purchase costs report.
In the case of an inter-site order, the receipt of the delivery line automatically recovers the grouping code.

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

• Dimension (field CCE)

These are the analytical dimensions initialized based on the setup of Default dimensions (POH dimension code). These dimension codes can be modified manually if authorized by the transaction.

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

According to the setup of the POP dimension code, the dimensions entered at the header level can be used as the default value for the lines of the purchase order.

• Signed (field APPFLG)

This information is used to identify the order situation from the signature management view point. The possible values are: 'No', 'Partially', 'Totally', 'No management', 'Yes automatic'.
If the signature management is not activated for the company (APPPOH setup), the value will be automatically equal to 'No management'. The order document can then be printed and the order received.
If the order management is activated for the company, the value will depend on the signature rules and the signatures carried out:

• If the value is set to No, it means that no signature has been entered or that the signatures that have already been carried out have been cancelled by a signatory.
• If the value is set to 'Partially', it means that some of the signers defined in the signature circuit have signed the order,
• If the value is set to Totally, it means that all the signers defined in the signature circuit have signed the order. It can be printed and received.
• If the value is set to 'Yes automatic', it means that the management of the signatures is optional ( APPPOH)setup) and that no signature circuit has been determined for this order. It is therefore considered as being signed and can be printed and the receipt can be carried out.

If the type of the purchase order is defined in the setup and is equal to "inter-sites" or "inter-companies", the corresponding sales order will be automatically generated if the value of the signature is: 'No management', 'Totally' or 'Yes automatic'.

• Printed (field PRNFLG)

This information is used to identify if the order document has been printed. The order document can only be printed if the order has been totally signed, or if there is no signature management for this order or if the signature is automatic.

• Closed (field CLEFLG)

This information is used to identify whether the order is totally completed/closed (when all the order lines are closed, the order is automatically closed).
An order can be closed if it is totally delivered or if it has been manually closed. If an order is totally completed, it can no longer be modified.

• Received (field RCPFLG)

This information is used to identify the situation of the order from the point of view of the receipt of goods.
The possible values are: 'No', 'Partially', 'Totally'. When an order is totally delivered, it is automatically closed.

• Invoiced (field INVFLG)

This information is used to identify the situation of the order from an invoicing point of view. The possible values are: 'No', 'Partially', 'Totally'.

• Product (field ITMREF)

Help common to the Order, Invoice and Buyer plan functions.
The entry of a product reference is mandatory. This field offers several possibilities.
You can:

• Directly enter a product reference.
  If the ITMFLG - Product/supplier ref. entry (ACH chapter, REF group) setup is active, you can enter either the internal reference of the product or the reference of the product at the supplier's.
  The existence of this reference is controlled in the Products file.
  The reference displayed is always the internal reference of the product and it must exist in the Product table, be active and of the Purchased product type. If the value of parameter BUYFLT - Filter by buyer (chapter ACH, group AUZ) is set to Yes, the product must be managed by the buyer. This filter is deactivated in invoice control.
  The product code is not mandatory for a line with the type Miscellaneous.
  
• Use the Actions menu to:
• Select a product from the file.
• Select a product from the list of supplier products.
• Select a product from the list of supplier-site products. From this selection window, the cursor is set by default on the first product referenced by the supplier for the chosen receiving site. You can select a different product from any other site, if it belongs to the same legal company.
• Create, according to the user's access rights, the product in the file.
• View and take into account the responses to the existing RFQs if the transaction used allows this.
  Click the Actions after the entry of the product reference to restrict the list to requests for quotes specific to this product. If you choose one of the answers linked to a request for quote, the order line is automatically loaded and the information is initialized with the elements from the original request and the answer made by the supplier.
  The quantity ordered, the unit, the descriptions, the project code and the analytical dimensions are initialized by the request for quotes. The prices and discounts and the planned due date are initialized with the information saved in the answer made to the request for quotes by the supplier.
• View and take into account the requirements related to the product (action not available in the invoice function). These requirements are expressed through purchase requests and suggestions created by the MRP calculation or the reordering schedules.
  In the Buyer plan function, you can display the requirement consideration window, even if the product reference is not entered. In all cases, all requirement types matching the selection are displayed, for all types of products. After selecting the lines and validating, the lines are automatically generated and display the proper product type, based on the origin of the requirement.
  In the Orders and Buyer plan functions, depending on the entry transaction used, the requirement consideration window can also open automatically. This window is displayed after entering the product reference, or if the product is of the Service category, after selecting the Product type (service or subcontract), when modifications are available.

The entry of the product is used to initialize the Description fields that can be modified.
After entering the product, the following messages may display:

• When the product does not exist on the selected receiving site.
  This message allows you to create the site, depending on your user authorizations.
• When the product is not referenced by the supplier.
  This message can be blocking or a simple warning according to the choice made at the level of the ITMBPS - Supplier referencing (ACH chapter, REF group) general parameter.
• When the (receiving) product-site is not referenced by this supplier.
  This message can be blocking or constitute a simple warning according to the choice made at the level of the ITMBPSFCY - Supplier-site referencing (ACH chapter, REF group) general parameter.
  This control does not apply to inter-site orders.
• When the product is blocked for the supplier, or for the supplier on the receiving site.
  This can be a blocking message or a simple warning according to the value of the blocking code in the Product-Supplier or Product-Site record.
• The entered product is already subject to an open order.
  This message is a simple warning.
• The product cannot be directly ordered but must previously have been the object of a purchase request.
  This message is blocking.

For products managed in stock, it is possible to take into account the suggestions coming from the MRP calculation or those from the statistical reordering calculations as well as the purchase requests.

For products not managed in stock, only potential purchase requests can be taken into account.

In the case of subcontract products, the subcontract orders generated by manufacturing releases are the ones to suggest what purchase to perform. To order a subcontract product, requirements must exist. Otherwise, an error message will display upon entering the product reference.

The work order can be accessed from the Actions menu on the product line. This order line must apply to a sub-contract product.

Requirement selection

When entering an order and depending on the entry transaction used, if there are purchase suggestions, subcontract orders or purchase requests for the entered product, a window can automatically open to suggest that requirements be taken into account. This window is displayed after entering the product reference, or if the product is of the 'Service' category, after selecting the Product type (service or subcontract), when modifications are available.

Notes:

• If the selected product type is 'Subcontract', the requirement consideration window opens regardless of the setup used in the entry transaction. In fact, the creation of an order line for a subcontract product can only be made by consuming subcontract requirements.
• If the supplier is blocked at the Product-sitelevel, the receiving site field is emptied and the requirement consideration window still opens.

If you do not want to take into account the requirements, simply cancel this window to return to the line entry (except for sub-contract products where the selection of the requirement is mandatory).

If you want to take requirements into account, select them in the corresponding window. This window shows the supplier code and name and the product code concerned along with its standard description.

To view the requirements on all sites, including the sites where the product-supplier is blocked, select the All sites check box. Otherwise, leave the check box cleared or only the requirements of the receiving site will be displayed. If the receiving site is empty as a consequence of the supplier being blocked on the Product-site record, the requirements of the default receiving site are displayed.

Likewise, you can adjust the display of the requirement lines according to the criterion of back-to-back orders.

A date can also be entered to limit the proposition in time. This date will be applied by default to the requirement end date, but it can be applied to the requirement start date according to the Requirement selection section. If no date is specified, all suggestions, purchase requests or subcontract orders are suggested.

Click Criteria to enter sorting criteria and additional selection criteria, including the entry of ranges related to the project code, the document or the original document, and a filter on the suggestion type.

You must then enter the unit in which the requirements quantities must be expressed. By default, the stock unit is suggested but it can be modified if it was picked in one of the following units: Purchase Unit, Packing unit, Stock unit of the product. Requirement lines are then displayed with, for each one:

• The start and end dates of the requirement, the site and the buyer code.
• The requirement quantity as well as the considered quantity.
• The quantity taken into account. This quantity can be initialized by default in two different ways:

• by the requirement quantity when no supplier is assigned to the requirement or when the supplier specified in the requirement line is identical to the supplier in the order,
• to zero when the supplier specified in the requirement line is different from the supplier in the order.

• The 'Blocking' status being mentioned against the product-site-supplier.

• If the line is blocked, the Blocking field is set to 'Yes'. The line cannot be entered and cannot be considered.
• If the line is linked to a warning, the Blocking field is set to 'No'. The quantity is initialized to zero but you can still enter a quantity. You can only select this line manually. You cannot use the Include all action.

• The Exclude all and Include all actions apply to all requirement lines, except from blocked lines and lines with a warning. They make it possible to reset the selected quantity to zero or to preload it. If there is a minimum quantity in the product-supplier record for the considered product, this quantity is suggested for the selected quantity, even if it is greater than the requirement quantity. A blocking message prohibits the entry of a quantity inferior to this minimum quantity.

• Various information such as the weight and volume for the considered quantities, the purchase request line and number (if the requirement is related to a purchase request), the supplier, the order type and number in the WIP and the requirement origin (MRP, MPS, Purchasing or Manufacturing).
• The supplier (or back-to-back supplier) is set to the default supplier (or default back-to-back supplier) defined on the Product-site record or Product-supplier record> (for more information on the supplier initialization rules, please refer to the documentation on the Product record).
• If you modify the receiving site, a message is displayed suggesting that you search for the new default supplier (or default back-to-back supplier) for this product-site.
• If the product is not referenced by the supplier, a blocking or warning message can be displayed based on the value of the ITMBPS - Supplier referencing parameter (ACH chapter, REF group).
• If the (receiving) product-site is not referenced by the supplier, a blocking or warning message can be displayed based on the value of the ITMBPSFCY - Supplier-site referencing general parameter (ACH chapter, REF group). If this message is blocking, you can still proceed with your entry but the Receiving site field must be set as available for entry for the entry transaction. In this case, the Receiving site field is emptied. You must then enter a site where the product-supplier is referenced, or for which the ITMBPSFCY - Supplier-site referencingparameter is not defined as blocking.

After entering the unit, you can automatically enter the quantity to be taken into account, which is the only information that can be entered on this screen. If you want to sort the suggested list by requirement start date (default sort), by requirement end date or by site, you have to exit the entry mode and use the Actions icon to choose the required sort. At this stage, if the requirement line is taken from a purchase request, you can also tunnel access the purchase request for inquiry.

The suggested quantity taken into account can be modified on the condition that the quantity entered is less than or equal to the requirement quantity, which can be the case if, for instance, you wish to take into account only part of the requirement. If you wish to exclude requirement lines, enter a null quantity. Click the Actions icon to select the total requirement quantity.

For subcontract products, always enter the required quantity in the screen dedicated to the taking into account of requirements. In fact, the creation of an order line for a subcontract product can only be made by consuming subcontract requirements. It remains possible to order a quantity greater than the requirement expressed by the manufacturing service. To do so, modify the ordered quantity once the order line has been generated.

For products managed by direct back-to-back order, the quantity cannot be modified.

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:

• the system has not found a purchase price list for the back-to-back order supplier,
• no purchase base price is entered on the product record,
• the product has no standard cost, or the PURPRICE - Price by default standard cost parameter (ACH chapter, PRI group) is set to 'No'.

Once this process is complete, if when entering the product, you have previously selected an invitation to tender response, an additional check is carried out and a warning message appears when the total requirement quantity is less than that mentioned in the response. You can cancel or proceed with your entry. In addition, another message allows you to decide if the order lines must be valued or not at the price entered in the request for quote response.

After validation, requirement lines taken into account are then sorted by product, by site, by supplier, and by project code and then lines are grouped by site, by analytical dimension, by project code and by description for generic products. Subcontract requirements are never grouped.

By using an entry point, it is possible to modify the grouping of the these orders (see the entry point ECLBESOINS).

For order lines generated from a requirement linked to a purchase request, after creating the order line, click the Actions icon to view all purchase request lines that have not be consumed. An inquiry screen appears and by tunnel it is possible to access each of the associated purchase requests.

When the requirements taken into account in an order line concern more than one purchase request, it will not be possible to reduce the order line quantity (however it can be increased). When the requirements concern a single purchase request and the quantity is reduced, this reduction will update the WIP quantity in the purchase request and the order, as well as the consumption information in the purchase request. It will also update the precommitments if necessary.

Inter-company specificities:

Inter-site orders:

You can only enter products of the Received / Deliverable type.

Inter-company orders:

You cannot enter a product of the Received / Not deliverable type.

For the same inter-company purchase order, the product of the first entered line determines the category of the generated sales order. A control is applied to the type of each product that you add so consistency is ensured at the level of the sales order category.

• If the first product is Received / Deliverable or Non received / Non deliverable, the category of the generated sales order is 'Normal'. You can only add products:

• of the Received / Deliverable type. These product lines use the Delivery/Sales invoice flow.
• of the Not received / Not deliverable type. These product lines are invoiced using the invoicing schedule.

• If the first product is Not received / Deliverable, the category of the generated sales order is 'Direct invoicing'. All lines are directly invoiced with no delivery. You can only add products:

• of the Not received / Deliverable type,
• of the Not received / Not deliverable type.

When creating a purchase order, even if you delete the product on the first line, the sales order category defined is kept as long as the table contains at least one line. In order to reinitialize the sales order and its category, you must delete all the entered lines.

When modifying a purchase order, if the sales order has already been generated, its category can never be modified, even if you delete all the purchase order lines. You can only enter products of a type compatible with the initial category. However, if the sales order has not been generated yet (e.g. if the signature management is active and the purchase order has not been signed yet), you can delete all the lines, enter a product line of any other type and finally modify the category of the sales order to generated, if needed.

The subcontract products are not allowed for this type of orders.

• Description (field ITMDES)

This is the description translated into the supplier's language. This description will be transmitted with any modifications on the receipt to stock or on the supplier invoice.

When an order comes from a purchase request or a request for quote, the translated description will be inherited from the original line.

This description will be printed on the order document.

 The product record can be accessed from this field using a tunnel.

• Standard description (field ITMDES1)

This is the description entered in the product record. This description will be transmitted with any modifications on the receipt to stock or on the supplier invoice. In the case of an inter-site or inter-company order, the modified standard description will also be transmitted to the sales order generated.

When an order comes from a purchase request or a request for quote, the standard description will be inherited from the original line.

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

• Product type (field ITMKND)

• Major version (field ECCVALMAJ)

The major version number can only be accessed if the tracking of major versions is activated at product setup level (in the Management section of the Product function, the value of the Stock version field is set to 'Major'). If the versions preloading is activated at the Product-supplier level, or otherwise, at the Product/Order level, the last active major version is preloaded automatically. Otherwise, the last major version with the 'Stopped' status will be preloaded. It can still be modified.

• Minor version (field ECCVALMIN)

The minor version number can only be accessed if the tracking of the major and minor versions is activated at product setup level (in the Management section of the Product function, the Stock version field is set to 'Major and minor'). If the version preloading is activated at Product-supplier level, or at least, at Product-Order level, the last minor version is preloaded automatically. It can still be modified.

• Receiving site (field PRHFCY)

Site where you want the supplier to ship the order, initialized by the purchase site entered in the order header, when the site is also a warehouse site.

This receiving site must belong to the same legal company as the order site.

Concerning an order for a product managed in stock:

• the receipt site must be a warehouse,
• the product reference must be defined for this receiving site.

If the product is managed in stock and the purchase site is not a storage site, then the system will propose the first storage site defined for the product.
If you enter a receipt site for which no Product-site record has been created, the system will offer to create it directly from the Product-site record.
If the product-site is not listed by the supplier, a blocking or warning message can be displayed based on the value of the ITMBPSFCY - Supplier-site referencing general parameter (ACH chapter, REF group). This control does not apply to inter-site orders.

If you change the receiving site, a message suggests that you run the default supplier search again:

• You want to run the search again:
• If a default supplier can be found on the Product-site record, then this supplier is used.
• If there is no supplier listed in the Product-site record, the default supplier listed in the Product-supplier record will be used, except if the ITMBPSFCY - Supplier-site referencing parameter (ACH chapter, REF group) specifies that the product-supplier must be listed at site level.
• If there are suppliers defined on the Product-site record but no default supplier is found because they are all blocked, then the supplier is not loaded. The field remains blank. You need to enter it.
• You do not want to run the search again:
• The source supplier is kept.
  

From this information, you can use the Actions icon to:

• select a purchase site form the site table. The sites proposed will be restricted to the sites of the company defined by the purchase site,
• inquire the stock for the product at the specified site.
• access the Product-site record if your user authorizations allow it.

Inter-company specificities: When the purchase order is of the inter-site or inter-company type, the receipt site is initialized to the receipt site entered in the default delivery address of the customer order associated with the purchase site of the purchase order. If the default delivery address associated with the customer defined by the purchase site does not specify the receiving site, then the first delivery address will be used, in alphabetic order, to identify the receiving site.

If no receiving site is defined for any of the delivery addresses for the customer associated with the purchase site, a blocking message is returned: Inter-sites: Delivery address not found for customer BP xxxx. In the same way, a blocking message is returned if the site identified does not belong to the same company as the purchase site (inconsistency in the database).

When the order is saved, the receiving site displayed in the order header will be same as the receiving site that has been chosen in the first line of the purchase order.

During the generation of the sales order, the delivery address used in the order line will be the delivery address identified by the receiving site entered on the purchase order line.

The system may prohibit the entry of different receipt sites on the purchase order lines in this context. This depends on the parameters linked to sales:

If the LINBPD - Ship-to clients on detail parameter (chapter VEN, group MIS) for the site defined by the supplier does not allow different addresses on the lines of a single sales order, then the receipt site is the same for all the lines in the purchase order. The receiving site entered on the first line of the purchase order will be automatically picked up by the next line without the possibility of modification.

If the customer related to the purchase site only authorizes completed orders, you can only enter one receipt site and one shipping site on the purchase order, for all the lines of the purchase order. The receiving site and the shipment site entered first in the purchase order will be systematically used in the next lines entered without the option of modification.

• Address (field FCYADD)

This is the default address code for the receiving site chosen. This address will be printed on the order document sent to the supplier.
From this field, you can select another receiving site address if several exist.

• Location reference (field USEPLC)

Use this field to specify the consumption place for the carrier or to define an address complement.

Examples: Dock xx or Hall yy.

The place of consumption is written on the order document.

Inter-company specificities: for inter-company or inter-site orders, the consumption location is transferred to the generated sales order line.

• Ship site (field LINSTOFCY)

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.

• Subcon. address (field SCOADD)

This is the sub-contractor address code where the materials linked to a sub-contractor operation must be consumed. By default, this is the default supplier address that is used. This information is only accessible if the product entered on the order line is a sub-contractor product and if the sub-contractor supplier has also been defined as a customer.

This address code corresponds to a shipment address code associated with a customer defined for the supplier. It is possible in this way to define a Sub-contractor location by address code. If a customer has not been defined for the sub-contractor supplier, the sub-contractor location defined in the supplier record will be taken.

The sub-contractor address code will be initialized to the address code entered in the sub-contract operation. If it is not entered in the operation, the system will initialize this information with the default delivery address for the customer associated with the sub-contract supplier.

It is possible to modify this sub-contractor address. The modification of this address will then be transferred to the sub-contracting operation.

From this information, a contextual button can be used to:

• Select a delivery address from amongst the delivery addresses associated with the customer record of the sub-contract supplier.
• Access by tunnel the delivery address management, if the user's authorizations allow this.

• Unit (field UOM)

Order or invoicing unit.
The product can have five packaging units available:

• Four packaging units entered in the grid of the product-units record.
  
• One packing unit linked to the supplier (product-supplier record) and two purchase units:
  
• One purchase unit linked to the master product.
• One purchase unit linked to the product-supplier. In order entry, this unit is suggested by default if a product-supplier record exists. Otherwise, the purchase unit of the product record is suggested by default.

Only the packing or purchase units previously mentioned can be selected.

Depending on the purchase order transaction used, you can access (or not) the order unit. If the transaction does not authorize the entry of the order unit, it is initialized to the purchase unit defined for the supplier or to the purchase unit of the product if this does not exist.

In the case of an order arising from a requirement, the unit suggested by default is the purchase unit of the supplier for the product or the purchase unit of the product.

It is possible to modify the order unit proposed. From the Actions icon, you can view the list of units including: the stock unit, the product packing units, the product purchase unit and the different units suggested for the supplier.

When the order line originates from a direct order, the order unit is determined based on the value of the POHCTMPUU - Direct order in purchase unit parameter (ACH chapter, ORD group).

In the buyer plan, if the supplier is modified and its units are different from those of the former supplier, a message is displayed suggesting to order in stock unit in order to avoid any price list inconsistency and keep a coherent order unit for the supplier. If you answer Yes, the order unit is readjusted into stock unit. If you answer No, the quantities are readjusted keeping the supplier's units.

Inter-company specificities: In the case of an inter-company or inter-site order, the unit is checked to ensure that a correspondence exists in the Sales module. Otherwise, a blocking control prohibits the entry of this unit.

• Ordered qty. (field QTYUOM)

It is mandatory to mention the quantity of product to be ordered in order units. The order unit can be a purchase unit or a packaging unit to be found in the product-supplier or master product.
By default the minimum purchase quantity or the quantity of considered requirements is suggested. After entry, the quantities in purchase units or stock units are recalculated.

An error message immediately appears if the order quantity is null.

The user will also obtain an error message when:

• The user modifies the suggested quantity after taking into account requirements including more than one purchase request and the quantity entered is less than the quantity taken into account. If the requests taken into account only contain one purchase request (POP) or suggested orders (POS), it is possible to reduce the quantity,
• The quantity entered is less than the minimum quantity required by the supplier mentioned in theProduct-supplier record. The level of control is defined by the POHMINQTY - Minimum order qty control parameter (ACH chapter, AUZ group).
• You are changing the quantity in an order line concerning a product managed in direct back-to-back order.
• You modify the calculated quantity while your order is in packing unit and the entered quantity is not a multiple of the packing.

From the quantity field, use the Actions icon to access the stock inquiry for the receipt site previously entered.

Inter-company specificities: For inter-company or inter-site orders, in addition to a control carried out in connection with the minimum purchase quantity, another control is to be performed in connection with the minimum and maximum sales quantities. This control can be blocked according to the value attributed to the user parameter SDACLOK - Ctr. non blocking price, margin, qt (VEN chapter, AUZ group).

For intercompany orders related to a non-deliverable Service product in a progress billing project, you cannot enter a quantity below the total quantity including the already billed quantity and validated quantity on the billing plan.

• Coefficient (field UOMPUUCOE)

This is the conversion factor expressed between the order unit and the purchase unit (supplier or product).

This coefficient is used to calculate the quantity in PU from an order unit entered in OU:
Qty in PU = Qty in OU * factor
This factor can also be used for the price list conversion into the order unit.
This factor can be accessed if an order unit has been entered with a value different from that of the purchase units contained in the product-supplier or product-master. It is initialized to one of the factors to be found in one of these two files or to the conversion factor table if the combination exists.

You can modify this conversion coefficient if the order unit is a product packing unit, whose coefficient can be modified (see Packing unit table on the Units section of the Product record) but cannot be used with the other units (product purchase unit, supplier purchase unit, supplier packing unit, stock unit).

Inter-company specificities: In the case of an inter-company or inter-site order, the factor used in the generated sales order is always the one entered on the purchase order.

• PUR (field PUU)

This is the purchase unit defined for the product-supplier combination, or for products that do not exist in the product-supplier record.
This product has two purchase units:

• Purchase unit defined on the product record.
• Purchase unit linked to the supplier.

This purchase unit cannot be modified. It is used as the default value when entering an order, subcontract order or receipt. The supplier purchase unit is suggested by default when the product-supplier record exists.

The purchase units are accessible depending on the type of category assigned.

 Upon invoicing a product, the product purchase unit is used.

• STK (field STU)

This field indicates the product management unit in which are expressed:

• The stock
• The standard price
• The BOM link quantity, etc.

This information is always displayed, regardless of the transaction used. It cannot be modified.

• STK qty. (field QTYSTU)

Quantity in stock unit calculated from the ordered quantity in order unit.

If the entered quantity is not a multiple of the order unit, a warning message is displayed. By default the minimum purchase quantity or the quantity of considered requirements is suggested. Under no circumstances the quantity entered is lower than these quantities.

You can modify this quantity if the order unit is a product packing unit, whose coefficient can be modified (see Packing unit table on the Units section of the Product record) but cannot be used with the other units (product purchase unit, supplier purchase unit, supplier packing unit, stock unit).

If you modify the quantity in stock unit, the factor expressed between the order unit and the purchase unit is adjusted.

• Project (field PJT)

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.
  In direct creation, the project code you enter on the header is always used on the document lines and cannot be modified.
  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.
  In case of a document transformation, the project code entered on the header is used to filter the documents available for selection and picking. If not project code is entered, it is automatically loaded with the project code of the first selected document.
  If you modify the document header project code, this code is automatically used on all the lines. A message is displayed and suggests to update the prices/discounts on lines. The update only applies to lines which are not received and not closed.
  
• When this parameter is set to Yes, the management of multiple projects is authorized.
  In direct creation, the project code you enter on the document header is used to initialize the project code of the document lines and can be modified.
  In case of document transformation, the project code entered on the header is only used as the default values of lines with no project code.
  
  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 transferred to all lines. A second message is displayed and suggests to update the prices/discounts calculated on the lines. The update only applies to lines which are not received and not closed.
• No: the project code is not transferred to the lines.
• Yes if same value: the project code is only transferred to the lines associated to the former project code.
  The project code used on the lines can be the same as that already used on the other lines. As the system is not able to differentiate these lines, no price/discount update is suggested or performed so not to overwrite the prices that the user may have entered, which do not originate from the price list.

When the order has been generated using a back-to-back order from a sales order, the project code is automatically loaded based on the code of the sales order header.
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.

• Expected rcpt. date (field EXTRCPDAT)

Help common to the Orders, and Buyer plan functions.

The expected receipt date must be entered. A date is automatically suggested by default. It can have various origins, including (in the following order):

• The date of the requirement when the requirement has been considered. When the line comes from a group of requirements, the closest requirement date is used. If you modify the suggested date and enter a later date, a warning message is displayed.
• The order date increased by the supplier lead-time included in the price list if it exists.
• The order date increased by the reorder lead-time from the product-site record if the product is in stock.
• The order date increased by the reorder lead-time from the product record if the product is not in stock.

This date is controlled with respect to the receiving site's calendar. If the site is unavailable on this date, a blocking message is displayed and you need to enter another date. You can also be returned a warning message when the entered date is prior to the calculated date. Once the order line has been validated, this date will not be modified by a price list re-initialization.

The planned due date can also be automatically recalculated when the date entered corresponds to a non-working day for the site. It is then automatically proposed as the first working day.

In any case, the minimum planned due date will be equal to the order date increased in the order by the lead-time from the price list, the Product-site or Product record.

From this field, click the Actions icon to view the stock forecast.

Inter-company specificities: Within the framework of an inter-site or inter-company order, the delivery date requested in the generated sales order header is initialized to the nearest expected receipt date from the purchase order lines. The expected receipt date for each sales order line is initialized to the expected receipt date from the corresponding purchase order line.

• Gross price (field GROPRI)

Help common to the Order and Buyer plan functions.

Use this field to determine the gross and excluding tax unit price of the product. This price is expressed in order unit if the Unit field is declared as accessible at the time of entry in the transaction, if not, it is expressed in purchase unit.

When the main information for the line has been given, a price list search process is automatically carried out. The objective of this search is to recover:

• The gross price and the associated reason.
  If the order (or purchase) unit is different from that of the price list line:
  - The price list amount is converted if the value of the Unit conversion is set to 'Yes' at the Pricing parameters level. This conversion is based on the unit conversion coefficient table. If no conversion is set up between these units, the price list amounts are those that are considered by applying a 1 conversion rate.
  - The price list is not used if the value of the Unit conversion is set to 'No' at the Pricing parameters level The value of the gross price is set to '0'.
• The charges and discounts in percentages or in amounts to be applied to the line level as well as the associated reasons.

When the entered price is null, a message appears to request confirmation from the user.

In the Price field, you can use the Actions icon to:

• View and modify the Discount and Cost fields defined using the structure code associated with the supplier. The values contained in these fields come from the price list search and can be modified if the associated reason allows it.
• View the reasons associated with the price as well as the different discounts and charges fields
• View the price lists
• Re-initialize the price, as well as the discounts and costs, by requesting a new price list search.

The entry of other data on the line depends on the selected transaction. This is the case for example for the Site information, Quality control code, etc.

Inter-company specificities: Within the framework of an inter-site or inter-company order, if the inter-company price lists have been set up, they will be used in the same way as normal price lists. When the sales order is generated, the prices and the discounts calculated for the reciprocal sales order will be determined from the inter-company price lists or the normal price lists. In no case will the prices and discounts entered in the purchase order be transferred to the sales order. The prices between the sales and purchasing documents can change independently. The reconciliation is made at the time of invoicing.

• field DISCRGVAL1

Help common to the Sales and Purchase modules.

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

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

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

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

From the Actions icon, you can:

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

• Net price (field NETPRI)

This is the unit net price for the order line calculated from the gross price affected by any discounts and charges.
 This information cannot be accessed.

• Line amount - tax (field LINAMT)

This is the unit net ex-tax price multiplied by the ordered quantity.
 This information cannot be accessed.

• Currency (field NETCUR)

This is the currency of the document, in which the amounts displayed in the previous columns are expressed.
This currency, which cannot be modified, displays the currency entered on the Management section.

• Landed cost coef. (field CPRCOE)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

• global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
• method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

The management of this field depends on the method used to determine the landed costs and on the entry transaction used. When it can be entered, the landed cost coefficient must be greater than or equal to 1. It is used to impact the purchase and stock costs by adding to the net price costs that have been previously estimated.
It is initialized based on the landed cost coefficient entered for the storage site of the product-supplier in the Landed costs - Site function.

If no record exists for the storage site of the product-supplier, the coefficient displayed on the Product-supplier record is used.
If the coefficient is not entered on this record, the value 1 is applied.
If there is no product-supplier, the coefficient entered on the Purchase section of the Product record is taken into account instead.

In order to display the calculated landed cost amount, click Line cost from the Actions icon (this amount is displayed on the Cost detail section - Undetailed costs table).

• Fixed cost per unit (field CPRAMT)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

• global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
• method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

The management of this field depends on the method used to determine the landed costs and on the entry transaction used. When it can be entered, this value, which must be a positive value, is expressed in the company currency.

It is initialized with the fixed cost per unit entered for the storage site of the product-supplier in the Landed costs - Site function.

If no record exists for the storage site of the product-supplier, the fixed cost per unit displayed on the Product-supplier record is used. If the fixed cost per unit is not registered on this record, the value 0 is applied.
If the product-supplier does not exist, the fixed cost per unit entered on the Purchase section of the Product record is considered instead.

In order to display the calculated landed cost amount, click Line cost from the Actions icon (this amount is displayed on the Cost detail tab - Undetailed costs table).

• Cost structure (field STCNUM)

The management of landed costs makes it possible to quantify the routing costs of the goods ordered from a supplier and to allocate them to the products upon order, receipt or invoice. These costs are used for the calculation of the purchase cost and stock cost.
The evaluation of these costs can be performed according to one of the two following methods:

• global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account,
• method in which a set of costs detailed in a cost structure is taken into account.

Only one method can be used, the choice of this method is performed at the level of the product management.

A cost structure details all the costs that are considered as fixed costs and can be identified at the time of the purchase. These costs are expressed in the currency of the company.
The presence of this field depends on the entry transaction used.

When managed, this information is initialized based on the cost structure entered for the storage site of the product-supplier, in the Landed costs - Site function.
If no record exists for the storage site of the product-supplier, the cost structure displayed on the Product-supplier record is used. If the cost structure is not specified for this record, no cost structure is considered for the product-supplier.
If the product-supplier does not exist, the cost structure entered on the Purchase section of the Product record is taken into account instead. It can never be modified.
If the cost structure is not specified on a record, the system will not suggest the cost structure of the next-level record.

In order to display the detail of costs included in the cost structure, click Cost structure detail from the Actions icon. It remains possible to adjust the calculated amounts.
These costs are also displayed in a window when clicking Line cost from the Actions icon (this amount is displayed on the Cost detail section - Direct costs table).

• Purchase cost per unit (field CSTPUR)

This information, which cannot be modified, is displayed if the transaction authorizes it.

The purchase cost per unit, which cannot be modified, is expressed in the company currency. It is equal to the result of the following calculation:

Line purchase cost / Quantity (in STK)

 This amount is never calculated during the entry process but only when saving the document.

• Purchase cost (field LINCSTPUR)

The purchase cost corresponds to the total amount that the buyer has to pay: the amount of the line, all the costs and invoicing elements (valued or not), as well as the non-deductible taxes.
This field cannot be modified. It is only displayed when the transaction authorizes it. It is expressed in the currency of the company.
Notes:

The calculation method varies depending on the landed costs valuation method:

• Global method where a Landed cost coefficient is applied and/or a method where a Fixed cost per unit is applied:
  
  Total of the line net price (line amount -tax) * Landed cost coefficient
  + total of the line fixed cost (fixed cost per unit * quantity in PUR)
  + total of the line invoicing elements
  + total of the line non-deductible taxes
  
  Note: To view the the non-deductible tax amount, click the Actions icon on the line to open the Line cost window.
  
  Example of line purchase cost calculation (without invoicing elements):
  
  - Hypothesis: the company currency and the document currency are identical (€).
  
  - Net price: €10/box
  - Landed cost coefficient: *1.3
  - Fixed cost per unit: €20
  - 1 box = 15 STK
  - Non-deductible tax: 16.9 %
  
  --> For an order of 1 box:
  Purchase cost = (10 * 1.3 ) + 20 + (10 * 16.9 %)  = €34.69
  The purchase cost per unit is the following: €34.69 / 15 STK = €2.31
  
  --> For an order of 5 boxes:
  Purchase cost = [(10 * 5) * 1.3 ] + (20 * 5) + (50 * 16.9 %)  = €173,45
  The purchase cost per unit is the following: €173.45 / 75 STK = €3.31
  
  
  Example of line purchase cost calculation (with invoicing elements):
  
  - Hypothesis: the company currency and the document currency are identical (€).
  
  - Net price: €10/box
  - Landed cost coefficient: *1.3
  - Fixed cost per unit: €20
  - 1 box = 15 STK
  - Valued invoicing element (transportation): €10
  - Non-valued invoicing element (unloading): €7
  - Non-deductible tax: 16.9 %
  
  --> For an order of 5 boxes:
  Purchase cost = [(10 * 5) * 1.3 ] + (20 * 5) + (50 * 16.9 %) + 10 +7 = €190.45
  The purchase cost per unit is the following: €190.45 / 75 USD = €2.539
  
  
• Method in which a set of costs detailed in a Cost structure is taken into account:
  
  Total of the line net price (line amount -tax)
  + total of the line product costs (originating from the cost structure)
  + total of the line invoicing elements
  + total of the line non-deductible taxes.
  
  Example of line purchase cost calculation:
  
  - Hypothesis:
  - the company currency and the document currency are identical (€)
  - Incoterm Ex-Works (all the costs are paid by the buyer)
  
  - Net price: €10/box
  - Valued product costs: 20 % of the net price
  - Non-valued product costs (calculation mode: unit price per box): €20 per box
  - 1 box = 15 STK
  - Valued invoicing element (transportation): €10
  - Non-valued invoicing element (unloading): €7
  - Non-deductible tax: 16.9 %
  
  --> For an order of 5 boxes:
  Line amount -tax: 5 boxes * €10 = €50
  + Costs of the cost structure: (€50 * 20%) + (€20 * 5) = €110
  + Total of the line invoicing elements: 10 + 7 = €17
  + Total of the line non-deductible taxes: 50 * 16.9 % = €8,45
  
  Purchase cost = 50 + 110 + 17 + 8.45 = €185.45
  The purchase cost per unit is the following: €185.45 / 75 STK = €2.472
  

• Actual purchase cost (field REACSTPUR)

The actual purchase cost corresponds to the total amount of the invoices/credit memos allocated to the line. These are the supplier invoices/credit memos, as well as the additional invoices and the credit memos on additional invoices, as long as they are validated.

• The additional invoices/credit memos on additional invoices with the New cost flag set to Yes are taken into account directly upon validation.
• The additional invoices/credit memos on additional invoices with the New cost flag set to No correspond to an update of the cost amount. This update is performed, depending on the situation, as follows:
• If the order is closed and already invoiced (partially or completely), the update is performed by launching the STCREG - Cost matching query.
• If the order is closed but not yet invoiced, the update is performed at the time of invoicing, as follows:
  - When the invoice is an invoice on receipt, the considered amount is the amount of receipt costs, impacted by additional invoices.
  - When the invoice is an invoice on order, the additional invoice amount is distributed with respect to the received quantities of each order line receipt.
  

The actual purchase cost is not available for modification. It is only displayed if the entry transaction authorizes it. It is expressed in the currency of the company.

This information is never calculated during the creation process, but only when saving the order.

• Stock cost per unit (field CPR)

This is the stock cost per unit of the product, expressed in the currency of the company.
It is equal to the result of the following calculation:

This field cannot be modified. It is displayed if authorized by the transaction you selected.
The stock cost can also be viewed in the stock detail window.

This cost is calculated when you save this order. It is not calculated whilst you are entering this order line.

• Stock cost (field LINAMTCPR)

This field, which cannot be modified, is displayed if the transaction authorizes it.
It displays the amount of the costs used for stock valuation, expressed in the company currency.

Notes :

Its calculation mode varies according to the method used to value the landed costs:

• Global method where a Landed cost coefficient is applied and/or a method where a Fixed cost per unit is applied:
  
  Line amount -tax * Landed cost coefficient
  + fixed cost per unit (expressed in PUR and converted into STK) * quantity in PUR
  + total of the valued invoicing elements of the line (the elements taken into account are only the ones with the Stock valuation flag set to: 'Yes')
  + total of the non-deductible taxes of the line (if parameter NODVATSTO - Non-deductible taxes in stock is set to ‘Yes’).
  
  This result is converted into the currency of the company using the exchange rate type specified the Management section.
  
  Example for the calculation of the Stock cost of the line (without invoicing elements):
  
  - Hypothesis: the company currency and the document currency are identical (€).
  
  - Net price: €10/box
  - Landed cost coefficient: 1.3
  - Fixed cost per unit: €20
  - 1 box = 15 STK
  - Non-deductible tax: 16.9 % but the NODVATSTO parameter - Non-deductible taxes in stock is set to "No".
  
  --> For an order of 1 box:
  Stock cost = (10 * 1.3 ) + 20  = €33
  The stock cost per unit is the following: €33 /15 STK = €2.20
  
  --> For an order of 5 boxes:
  Stock cost = [(10 * 5) * 1.3 ] + (20 * 5)  = €165
  The stock cost per unit is the following: €165 / 75 STK = €2.20
  
  
  Example for the calculation of the stock cost of the line (with invoicing elements):
  
  - Hypothesis: the company currency and the document currency are identical (€).
  
  - Net price: €10/box
  - Landed cost coefficient: 1.3
  - Fixed cost per unit: €20
  - 1 box = 15 STK
  - Valued invoicing element (transportation): €10
  - Non-valued invoicing element (unloading): €7
  - Non-deductible tax: 16.9 % but the NODVATSTO parameter - Non-deductible taxes in stock is set to "No".
  
  --> For an order of 5 boxes:
  Stock cost = [(10 * 5) * 1.3 ] + (20 * 5) + 10 = €175
  The stock cost per unit is €70 / 75 STK = €2.33
  
  
  Example for the calculation of the stock cost of the line (with invoicing elements):
  
  - Hypothesis: the company currency and the document currency are different.
  
  Company currency: $
  Document currency: €    - Conversion: €1 = $1.40
  
  - Net price (in document currency): €10/box, converted into company currency --> $14/box
  - Landed cost coefficient: 1.3
  - Fixed cost per unit (in the currency specified in the Product record): $30
  - 1 box = 15 STK
  - Valued invoicing elements (transportation) (in document currency): €15, converted into company currency --> $21
  - Non-deductible tax: 16.9 % but the NODVATSTO parameter - Non-deductible taxes in stock is set to "No".
  
  --> For an order of 1 box:
  Stock cost = (14 * 1.3) + 30 + 21 = $69.20
  The stock cost per unit is the following: $69.20 / 15 STK = $4.61
  
  
• Method in which a set of costs detailed in a cost structure is taken into account:
  
  Line amount -tax
  + costs of the cost structure
  + total of the valued invoicing elements of the line (the elements considered are only the ones with the "Stock valuation" flag set to: "Yes").
  + total of the non-deductible taxes (if the NODVATSTO parameter - Non-deductible taxes in stock is set to ‘Yes’)
  
  Example for the calculation of the stock cost of the line:
  
  - Hypothesis:
  - the company currency and the document currency are identical (€)
  - Incoterm Ex-Works (all the costs are paid by the buyer)
  
  - Net price: €10/box
  - Valued direct costs: 20 % of the net price
  - Non-valued direct costs (calculation mode: unit price per box): €20 per box
  - 1 box = 15 STK
  - Valued invoicing element (transportation): €10
  - Non-valued invoicing element (unloading): €7
  - Non-deductible tax: 16.9 % but the NODVATSTO parameter - Non-deductible taxes in stock is set to "No".
  
  --> For an order of 5 boxes:
  Line amount -tax: 5 boxes * €10 = €50
  + Valued costs of the cost structure: €50 * 20 % = €10
  + Total of the valued invoicing elements: €10
  
  Stock cost = 50 + 10 + 10 = €70
  The stock cost per unit is the following: €70 / 75 STK = €0.933
  

• Currency (field CPRCUR)

This is the currency in which the stock is valued (accounting currency of the company). The stock cost per unit and the order unit price are expressed in this currency.
This information cannot be modified.

• field LINACC1

These fields indicate the purchase accounting accounts. The charts of accounts that can be accessed depend on the account core model associated to the company of the movement.
If these fields are not entered the account will be automatically determined by the accounting code for the product as a function of the parameters for the automatic journal.
 The presence of this field depends on the entry transaction used.

• Purchase type (field LINPURTYP)

The presence of this information depends on the transaction setup.

The different purchase types are: Purchases, Fixed assets and Services. The purchase type is initialized on the basis of the tax posting type associated to the GL account previously entered.

The purchase type will be transmitted to the receipt or to the purchase invoice control.

• Matching tolerance (field MATTOL)

This field displays the tolerance code of the order line. This field is loaded in the following way:

• the program searches if a tolerance code is specified in the product/supplier record,
• if no value is found by the program, a search is performed at the level of the product record,
• finally, the control is carried out at the level of the supplier record,
• if no code has been specified: no tolerance code is applied to the line.

Field management (depends on the entry transaction setup)

• If the entry transaction authorizes the entry of the tolerance code, the code can be modified as long as the order has not been closed.
• If the entry transaction authorizes the display of the tolerance code, a default code is assigned and cannot be modified.
• If the entry transaction does not authorize the display of the column, the default code is invisible.

 A tolerance code can be assigned by default whatever the purchase order type (back-to-back, manual or planning workbench).

• field CCE1

During the entry of an order line, the analytical dimension types are initialized according to the POP Default dimensions code.

If the order line originates from a document line, the analytical dimension types are loaded by the analytical dimensions on the source document line. If analytical dimension types are not specified on the source document, an attempt to initialize these analytical dimension types is made according to the Default dimensions code.
When an analytical dimension is used for project management tracking, any modification of the project code on the document line leads to the dimension code being reset based on the Default dimensions setup.
According to the setup of the transaction, the analytical dimensions can be modified.The different analytical dimensions entered in the order line will be transferred to the receipt or to the purchase invoice control. STOP

• QC (field QUAFLG)

This code is used to define whether this product must be controlled on receipt into stock.
The assigned product Category determines the initial control value for the product-site record and the supplier-stock record. The supplier-stock record value provides the default value for purchase orders.

• No control. The control is based on the management rules. It can be modified manually.
• Non-changeable control. Quality control is mandatory for stock receipts. Q is the only valid status.
• Changeable control. For a miscellaneous receipt into stock, the quality status is initialized to the value Q. This status can be changed to A or R.
  The quality control code can also be defined at the purchase order level.
  • If in the order quality control is set to "Yes", quality control is mandatory and the receipt has one of the sub-statuses Q* defined in the product management rule for receipt movements.
    If no sub-status is defined, the status cannot be entered at the time of receipt.
  • If in the order quality control is set to "No", quality control is not mandatory.
    At the time of receipt, A is suggested as the default status. This can be changed to one of the statuses defined in the receipt movement rule for this product.
• Periodic control. This control is automated according to the number of receipts for this supplier and this product. The stock status can still be modified during entry.
  
  

When the quality control code associated with the product or with the product-supplier combination has the Non-changeable control value, the field that corresponds to the order line cannot be accessed in entry mode, irrespective of the transactions setup.

This information will then be used at the receipt and cross-checked with the management rule defined for the product category and associated with the movement type Supplier receipt to determine the product status and to generate, if necessary, an analysis request.

• Intras. incr. (field EECINCRAT)

This is the increase coefficient used in the INTRASTAT file (Exchange of goods declaration).
This coefficient, applied to the fiscal value of the product line is used to obtain the statistical value. The presence of this field depends on the activation of the management of the INTRASTAT file (Exchange of Goods Declaration) (DEB activity code).
 This information is initialized by the increase coefficient in the Product-Supplier record if it is entered, by the increase coefficient in the Supplier record if not.

• Country (field ORICRY)

This is the country of origin where the goods have been manufactured.
This information is initialized with the country of the supplier's shipment address. It is used for the Intrastat declaration (ISO code of the country table). The country of origin of the goods, as it is used in the context of Intrastat declarations, is retrieved from the shipment address of the supplier.

• Ack. date (field LINOCNDAT)

This information is not accessible on the order line. When the date and number of the last acknowledgment of receipt sent by the supplier are entered on the Total section of the order, the order lines that do not have an acknowledgment date and number yet are automatically updated with the values entered.
When a line is modified or added, the acknowledgment date and last number (Total section) known are reproduced on these lines
Inter-company specificities
In the case of an inter-company or inter-site order, the date and number of the acknowledgment of receipt of each line are initialized, once the sales order has been generated, with the date and number of the sales order.

• Ack. ID (field LINOCNNUM)

• Closed (field LINCLEFLG)

This information is used to indicate the order line situation. If the line is complete, it will not be accessible.
If necessary, it is possible to reactivate it, provided that the user's authorizations allow it and if the order has not been totally closed.
An order line can be closed manually or automatically by the receipt of goods.

• Revision no. (field LINREVNUM)

If revision management is activated (PURREV setup), the revision number is displayed on the line specifying that the order line has been modified under revision number x.

• Sales order no. (field SOHNUM)

This information specifies the original sales order number when the purchase order has been generated by a direct order.
 This information cannot be accessed.

• Request source (field ORI)

This non accessible information reminds the origin of the purchase order line.
The possible values are: 'Purchasing', 'PO direct to customer', 'PO received and shipped', 'Production', 'Subcontracting'.

• Weight (field QTYWEU)

This field, subject to an entry transaction, contains the weight of the ordered product.

• Weight unit (field LINWEU)

The weight unit is the reference weight of the document. It is defined by parameter SALDSPWEU - Weight units to affect (chapter TC, group INV) for all the documents.

• Volume (field QTYVOU)

This field, subject to an entry transaction, contains the volume of the ordered product.

• Volume unit (field LINVOU)

The volume unit is the reference volume of the document. It is defined by parameter SALDSPVOU - Volume unit to affect (chapter TC, group INV) for all the documents.

• Tax 1 (field VAT1)

This field is used to enter a first tax code to apply to the ordered product.
The tax codes (VAT, additional taxes, special taxes and/or provincial taxes) can be modified on the order line if the transaction authorizes it. They are initialized according to the tax determination rules that most often are coming from crossing the supplier tax rule with the tax levels of the entered product.
If activity code PTX - Regional taxes is activated, it is also possible to access at line level four additional taxes that are used to manage regional taxes. When converting an order line into a receipt or invoice line, the tax codes entered in the order line are transferred to these documents.
The right click is used to select a tax code for each tax level.

• Tax 2 (field VAT2)

This field is used to enter a second tax code to apply to the line. This concerns additional or special taxes.

• Tax 3 (field VAT3)

This field is used to enter a third tax code to apply to the line.
This concerns additional or special taxes.

• Receipt tax (field TAXRCP)

This field is used to indicate the receipt tax to apply to the product.
This tax stems from the tax determination parameters or is entered manually.
 Theactivity code linked to the provincial taxes must be activated beforehand.

• Issue tax (field TAXISS)

This field is used to indicate the issue tax to apply to the product.
This tax stems from the tax determination parameters or is entered manually.
 Theactivity code linked to the provincial taxes must be activated beforehand.

• Other tax 1 (field TAXOTH1)

This field is used to indicate an additional tax to apply to the product.
This tax stems from the tax determination parameters or is entered manually.
 Theactivity code linked to the provincial taxes must be activated beforehand.

• Other tax 2 (field TAXOTH2)

This field is used to indicate an additional tax to apply to the product.
This tax stems from the tax determination parameters or is entered manually.
 Theactivity code linked to the provincial taxes must be activated beforehand.

• Line type (field LINTYP)

This information characterizes the line type by distinguishing a standard product from a subcontract BOM product.
It can take the following values:

• Minimum order (field ORDMINAMT)

This amount, which cannot be accessed, is a reminder of the minimum order amount defined for the Supplier.
It is expressed in the order currency.
At the end of the order entry, the order can be subject to a control if the ex-tax amount is lower than this threshold.
The Control field displays the level of control (Block, Warning, No control) as set by the POHMINAMT - Order min amount parameter (ACH chapter, AUZ group).

• Maximum order (field ORDMAXAMT)

This field displays the maximum order amount defined for the supplier in the folder currency. This amount is not stored and does not prevent you from saving.

The field identifies the total purchase order amount needed to receive free freight. It is a display-only field and does not restrict POS creation.

• Free freight threshold (field ORDFREFRT)

The field identifies the total purchase order amount needed to receive free freight. It is a display-only field and does not restrict POS creation.

• Control (field POHMINAMT)

This field, which cannot be accessed, describes the type of control carried out with respect to the minimum order amount. The type of control (blocking, warning, no control) is defined by the parameter POHMINAMT - Order min amount control (ACH chapter, AUZ group).

• Invoice lines excluding tax (field WTOTLINAMT)

This is the total ex-tax amount for the order expressed in the order currency.

• Container (field TCTRNUM)

Select the container that you want to use. It can simply be a "freight container" type.
The choice of the container determines the maximum weight and volume you can ship.

• Weight (field WEICAP)

This field displays the total weight capacity of the selected freight container(s). If a container is not selected, you can enter a weight without having to manage containers.

• No. of containers (field TCTRQTY)

• Volume (field VOLCAP)

This field displays the total volume capacity of the selected freight container(s). If a container is not selected, you can enter a volume without having to manage containers.

• Weight (field WEITOT)

This field represents the total weight multiplied by the quantity ordered.

• Volume (field VOLTOT)

This field represents the total quantity ordered multiplied by the total volume.

• Weight (field WEIAVL)

This is field displays the available weight for a container when the total weight of selected lines in the workbench do not equal zero.

• field TCTRWEU

• Volume (field VOLAVL)

This is field displays the available volume for a container when the total volume of selected lines in the workbench do not equal zero.

• field TCTRVOU

• No. (field INVDTA)

This is the number of the invoicing element identifying the associated amount (charges, freight, packing, discount, etc.).
The list of invoicing elements is made up by concatenating the lists of the order and invoicing supplier according to the origin defined in the invoicing element itself.
If an invoicing element is present on the order and invoicing supplier, the value of the supplier record is selected according to the origin of the invoicing element. This list is completed with the invoicing elements of line type present in the price list structure of the order supplier.
 Other elements can be added to this list. Only those elements added to the initial list can be deleted.

• Description (field INVDTALIB)

This field indicates the short title of the invoicing element.

• % or amount (field INVDTAAMT)

Information related to the invoice footer. This information comes directly from the invoicing elements present in the supplier record concerned by the order for those that are declared as present in the order footer.
 See the Invoicing elements documentation for further information.
It is possible to modify the values of the various invoicing elements already present and to add new ones. These invoicing elements are immediately taken into account on the order and have an impact on the ex. tax and tax inc. amount.
Inter-company specificities
In the case of an inter-company or inter-site receipt, the invoicing elements are recovered in the purchase order if the received delivery is coming from a purchase order.
In the case of a direct delivery, the invoicing elements are directly taken from the delivery.

• field AMTCODLIB

The system specifies whether the invoicing element is a percentage or an amount.
If it is an amount, the document currency is displayed.

• Order footer amount (field INVORDAMT)

This field indicates the amount of the invoicing element.

• Amount lines (field INVLINAMT)

This field indicates the amount of the invoicing element when the invoicing element is calculated using the document lines.
 In the case of such an invoicing element, the '% or amount' and 'Order footer amount' fields cannot be accessed.

• Invoiced amt. (field INVCPLAMT)

This field specifies the amount taken into account on the invoices linked with the order.

• DR/CR (field DEBCDT)

This field indicates the sign of the invoicing element.

• credit in the case of a discount,
• debit in the case of a charge.

• Tax (field INVDTAVAT)

This field indicates the tax code of the invoicing element.
Only one tax code consistent with the legislation and the group of the site company can be entered.
The general principles linked to the multi-legislation setup are detailed here.

An invoicing element with 'product rate' or 'line amounts' as tax calculation rule does not display a tax code and unauthorizes the modification of this tax code.

• field ACC1

These fields indicate the purchase accounting accounts for the invoicing elements. The charts of accounts that can be accessed depend on the account core model associated to the company of the movement. If these fields are not entered, the accounts are automatically determined using the accounting code of the invoicing element (according to the setup of the automatic journal).
 The display of these fields depends on theentry transaction used.

• Distribution (field DSP)

This is the analytical distribution key for the invoicing element.
It can be directly entered on the line.

• field PFICCE1

Analytical dimensions of the invoicing element.

The analytical dimensions are initialized according to the setup of Default dimensions (POV dimension code), associated with the management of invoicing elements. These dimension codes can be modified manually if authorized by the transaction. Use the Actions icon to change the dimension codes of the dimension types.

When an analytical dimension type is used for the Project management tracking, any modification of the project code on the document header leads to the dimension code being reset for this dimension type, except if a distribution key has been entered.

• No. (field NOTAX)

• Code (field TAX)

This field indicates the tax code present on the lines of the document or in the invoicing element table.

• Description (field LIBTAX)

This field contains the title of the tax code present on the lines of the document or in the invoicing element table.

• Tax basis (field BASTAX)

This field indicates the basis liable to tax. It is comprised of the ex-tax amount of the invoice lines and/or the amount of the invoicing elements.

• Tax amount (field AMTTAX)

This is the tax amount calculated from the lines and/or invoicing elements.

• Type (field PURTYP)

When the tax is related to:

• the document line, the tax type recovers the purchase type of the document line: Purchase, Fixed assets or Service.
• an invoicing element, the tax type always takes the value: Purchase.

• Currency (field WCUR)

This field specifies the currency of the document.

• Minimum order (field ORDMINAMT)

This amount, which cannot be accessed, is a reminder of the minimum order amount defined for the Supplier.
It is expressed in the order currency.
At the end of the order entry, the order can be subject to a control if the ex-tax amount is lower than this threshold.
The Control field displays the level of control (Block, Warning, No control) as set by the POHMINAMT - Order min amount parameter (ACH chapter, AUZ group).

• Blocking (field POHMINAMT)

This field, which cannot be accessed, describes the type of control carried out with respect to the minimum order amount. The type of control (blocking, warning, no control) is defined by the parameter POHMINAMT - Order min amount control (ACH chapter, AUZ group).

• Lines excluding tax (field TOTLINAMT)

This is the total ex-tax amount for the order expressed in the order currency.

• Total excluding tax (field TOTORD)

This is the total ex-tax amount of the order integrating the various invoicing elements expressed in the order currency.

• Tax total (field TOTTAXAMT)

This is the total amount of taxes for the order.
This amount is expressed in order currency.

• Total including tax (field TTVORD)

This is the Tax incl total amount of the invoice calculated by integrating the different invoicing elements and the different taxes. This amount is expressed in order currency.

• Ack. date (field OCNDAT)

• Ack. ID (field OCNNUM)

Once the supplier has received the order, enter the acknowledgement ID provided by the supplier.
After entering this information, the contract lines which have not been assigned an acknowledgement ID are automatically updated with this number.

Inter-company specificities: For inter-company or inter-site contracts, the Order acknowledgement ID and date cannot be accessed and are initialized, when the sales contract has been generated, with the date and the number of the sales order. You can use the Actions icon available on the Ack. ID field to jump to the generated sales contract, provided you are granted the proper authorizations.

• Ack. notes (field OCNREM)

You can add two lines of comments on the acknowledgment of receipt.

• Description (field LIB)

• field TOTDOC

• field TOTSOC

• Total by cost nature (field STCD)

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

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

• Freight agent (field FFWNUM)

The forwarding agent field is used to identify a BP appointed by the sender or the recipient to ensure transport continuity when the goods need to undergo several successive transports. The forwarding agent is controlled in the Carriers table.

The forwarding agent and their address are used in the Intrastat file to declare the flows of goods between the forwarding agent’s address and the sender’s address, or between the forwarding agent’s address and the recipient’s address.

For example, this situation applies to the shipment of goods abroad, since customs formalities are performed by a forwarding agent in another EU country. An Intrastat declaration needs to be submitted for the transfer of goods to this other EU country.

• Forwarding agent address (field FFWADD)

This is the address code of the forwarding agent. It is initialized with the default address of the BP corresponding to the forwarding agent. This address is used to determine whether submitting an Intrastat document is necessary for this flow.

• EU VAT no. (field EECNUM)

This is the VAT identification number of the BP. 

This European VAT number must be entered on all the invoices destined to or coming from the European Union. This number starts with two letters identifying the business partner country followed by a number depending on the country.

In France the number is comprised of FR, then 2 numbers identifying the tax office of the place where the company conducts its activities, followed by the Company tax ID no.(SIREN) of the company.

This information must necessarily be entered if the Company Registration number is set up as being mandatory for the country of the company.

• Intrastat transp. location (field EECLOC)

A transport location must be specified in the EU exchange declaration. It is combined with the Incoterm code in order to determine the delivery conditions referring to the sales contract terms that specify the respective obligations of the buyer and seller.

This information is not used in the French declaration.

• Intrastat transport mode (field EECTRN)

The transport method by which the goods are presumed to leave their national territory on shipment (export) or to have arrived in on receipt (import). This information is used in the Customs document file.

• Transaction nature (field EECNAT)

This is the economic information on the performed transaction. The nature of the transaction is used in the Intrastat.
This information is initialized using the physical flows where it can be modified. This information can also be accessed from some financial flows (sales invoices and credit memos).
The transaction nature is initialized according to the setup of the correspondence table for the Movement rules and natures. This table is used to associate an EU rule and an EU transaction nature to each flow type. This setup can be adjusted by rule, country and group of companies.

• Statistical rule (field EECSCH)

The EU or statistical rules are used to specify the nature of the EU transaction from a tax or statistical point of view. The EU rule is used in the Intrastat.
This information is initialized using the physical flows where it can be modified. This information can also be accessed from some financial flows (sales invoices and credit memos).
The initialization of the nature of the transaction is carried out according to the parameters of the comparison table for the Movement rules and natures, which is used to associate an EU rule and an EEU transaction nature to each type of flow. This setup can be adjusted by rule, country and group of companies.

• Number of lines (field LINNBR)

• No. of fully received lines (field RCPLINNBR)

• No. closed lines (field CLELINNBR)

• No. lines totally invoiced (field INVLINNBR)

• Total no. of receipt lines (field RCPNBR)

• Signed (field APPFLG)

• Total no. of invoice lines (field INVNBR)

• Printed (field PRNFLG)

• No. (field NOLIG)

• Product (field ITMREF)

• Ordered qty. (field QTYPUU)

• Total inv. qty. (field INVQTY)

• Unit (field PUU)

• Receipt no. (field PTHNUM)

• Received (field RCPDAT)

• Receipt qty. (field RCPQTYPUU)

• Qty. inv./recd. (field INVQTYPUU)

• Invoice number (field INVNUM)