Buyer plan

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

• Order date (field ORDDAT)

Order date

It is initialized to the current date and it can be modified. If it is actually modified (after entering lines in modification or copy mode), the user is asked whether they would like to carry out a new price list search on all the lines of their document.

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

• Buyer (field BUY)

The buyer code is initialized by the user code and must be entered if the BUYFLT Filter by buyer parameter (chapter ACH, group AUZ) is set to Yes.

According to the transaction entry used, this field may be hidden. In this case, the user code is used as the default value.

From this field, the Actions icon 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.

• Grouped prices (field TARGRP)

Specify if you want to use the grouped price lists.

• Supplier (field HBPSNUM)

• Project (field PJTH)

The project code entered on the header is used to initialize by default the project code on each line of the buyer plan.
This field is managed depending on the setup of the entry transaction of the subcontract order. The management of this code also depends on the value of the CTLOPPCOD - Mandatory project control parameter (TC chapter - MIS group).

• When it is set to No, the code can be selected freely.
• When it is set to Yes, an existence check is systematically applied to the entered project code.
  You can use the Selection icon to display the list of available projects.

This project code can still be modified in the lines.
If the loading of lines is done with the action Requirement selection, all the lines with the entered selection criteria are selected regardless of the project code entered on the header. This is not an implicit selection criteria, even in a single project context (the parameter PJTSNGDOC - One project per document - chapter TC- group MIS - is set to Yes).

This parameter has an influence on the generated orders:

• When it is set to Yes, the multi-project management is prohibited.
  The project code is mandatory the same on the header and on the order lines.
  
• If the value of this parameter is No, multi-project management is authorized.
  You can modify the project code on each order line.
  

• Dimension type (field DIE)

• Description (field NAMDIE)

• Dimension (field CCE)

The setup determines whether the analytical dimensions can be modified. These are initialized in compliance with the default dimension setup.

In creation mode, if no order line has been entered and the project code is modified, analytical dimensions are reset based on the setup of the default dimensions.

In creation mode, as in modification mode, if an order line has been entered and the project code is modified, analytical dimensions are not reset.

• Print orders (field PRTFLG)

• Document (field DOCNAM)

Code of the standard document printed during an automatic printing at the end of entry.

• Destination (field PRTCOD)

This field defines the destination of the calculated report. The destination types are the following:

Preview

The flow generated in a format compatible with a display (text, PDF, RTF, Word...) is displayed in a window that opens on the user workstation. This print is formatted by Crystal Reports either on the user workstation, or via a print server.

Printer

In that case, Crystal Reports uses either a local printer, or a printer that can be accessed from a print server.

Message

Crystal Reports creates a file containing the message in a format such as PDF, text, RTF, Word. This message is used as the attachment of an email sent via the Workflow engine.

File

Crystal Reports creates a file containing the message in a format such as PDF, text, RTF, Word, which is stored on the disk.

ZPL printer

The flow is controlled by a specific formatting program associated with the report and defined by a dedicated setup. This flow can be sent directly on a local printer, on a printer accessible from the print server, or stored in a file.

Archiving

Crystal Reports creates a file containing the message in a format such as PDF, text, RTF, Word. This file is addressed to a EDM system for archiving, via the EDM standard connector.

• Server (field PRTSRV)

• Printer (field PRTNAM)

• Freight container (field TCTRNUM)

Select the Freight container you wish to use. The choice of the container determines the maximum weight and volume you can carry.

• Weight (field WEICAP)

This field displays the total weight capacity for the selected container or containers. 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 for the selected container or containers. 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

• 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.
Update 8.0.0 and higher:
The Control field displays the POHMINAMT - Order min amount parameter (ACH chapter, AUZ group) value. You can set the Order min amount control level parameter value to 'Block', 'Warning', or 'No Control'.

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

• Cost (field TOTCOST)

This field represents the cost multiplied by the ordered quantity.

• field TOTCUR

• No. (field NOLIG)

• 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,
• create, according to your access rights, the product in the file,
• view and take into account the responses to the existing RFQs if the transaction used allows this.
  The activation of the contextual button after the entry of the product reference is used to restrict the list to requests for quotes specifically for 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.
Following the entry of the product, different messages can be displayed in the following cases:

• The product is not referenced at the supplier's.
  This message can be blocking or constitute a simple warning according to the choice made at the level of the ITMBPS - Supplier referencing (ACH chapter, REF group) general setup.
• The product is blocked for this supplier.
  This message can be blocking or constitute a simple warning according to the value given to the blocking code in the Product-supplier record.
• The product entered is already the object of a contract order, a warning message is displayed.
• The product cannot be directly ordered but must previously have been the object of a purchase request. This message is blocking.
• The product entered does not exist at the receiving site chosen, a warning message informs you and gives you the possibility to create it if you have the authorization to do so.

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

You can decide whether to view the requirements of all the sites, or not (in which case, only the requirements of the order 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 quantity taken into account;
  This quantity taken into account 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 Exclude all and Include all actions make it possible, for all the requirement lines, to set the selected quantity to zero or, to the contrary, 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 less than 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 PO followed by a ~ corresponds to an inter-company order.

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 wish 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 contextual button 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. In this field, use the right-button 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 not 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 (chapter ACH, group PRI) 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, 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).

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

• Description (field ITMDES)

Main description of the product coming from the product record and that can be modified during entry.
In the case of a call for tenders, if the product does not exist in the product table, the description must be entered directly.

• Standard description (field ITMDES1)

This is the description entered on the product record. This description is transferred from the sales invoice to the purchase invoice in case of inter-company invoicing. When the invoice stems from another document, the standard description is inherited from the source line.

• Site (field PRHFCY)

It is the site where the supplier will ship the order, initialized by the order site in case the latter is also a warehouse.

Warning:

This 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 receipt site.

By default, it is the purchase site entered in the order header. 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 a receiving site is entered for which the Product-site record has not been created, the system will then propose to create this record by accessing the Product-site record.

From this information, a contextual button can be used 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 the user's authorization allow this.

Specificities linked to the inter-company: When the purchase order is of the inter-site or inter-company type, the receiving site is initialized to the receiving 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 will be returned: Inter-sites: Delivery address not found for customer BP xxxx.  In the same way, a blocking message will be returned by the system 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 receiving sites on the purchase order lines in this context. This depends on the setups linked to sales:

If the LINBPD setup for the site defined by the supplier does not allow different addresses in the lines of a single sales order, then the receiving site will be 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 associated with the purchase site only authorizes complete orders, it will not then be possible to enter more than a single receiving site in the purchase order, and only a single delivery site for all the purchase order lines. 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 chosen receiving site. This address will be printed on the order document sent to the supplier.
From this field, you can select another address for the receipt site if multiple sites are defined.

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

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

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

This conversion factor can be modified if the order unit entered is a packing unit for the product where the factor can be modified (see the packing unit grid in the Units tab in the Product record), but it is not accessible for the other units (Purchase unit of the product, Purchase unit defined for the supplier, Packing unit for the supplier, Stock unit).

Specificities linked to the inter-company: In the case of an inter-company or inter-site order, the factor that will be used in the sales order generated will always be the one entered in the purchase order.

• PUR (field PUU)

• STK (field STU)

• STK quantity (field QTYSTU)

This is the 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 will be 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.

This quantity can be modified if the order unit entered is a packing unit for the product where the factor can be modified (see the packing unit grid in the Units tab in the Product record), but it is not accessible for the other units (Purchase unit of the product, Purchase unit defined for the supplier, Packing unit for the supplier, Stock unit).

If the quantity in stock unit is modified, the factor expressed between the order unit and the purchase unit will be adjusted.

• Weight (field LINWEI)

• Weight unit (field LINWEU)

• Volume (field LINVOL)

• Volume unit (field LINVOU)

• Project (field PJT)

The project code entered on the header is used to initialize by default the project code on each line of the buyer plan.
This field is managed depending on the setup of the entry transaction of the subcontract order. The management of this code also depends on the value of the CTLOPPCOD - Mandatory project control parameter (TC chapter - MIS group).

• When it is set to No, the code can be selected freely.
• When it is set to Yes, an existence check is systematically applied to the entered project code.
  You can use the Selection icon to display the list of available projects.

This project code can still be modified in the lines.
If the loading of lines is done with the action Requirement selection, all the lines with the entered selection criteria are selected regardless of the project code entered on the header. This is not an implicit selection criteria, even in a single project context (the parameter PJTSNGDOC - One project per document - chapter TC- group MIS - is set to Yes).

This parameter has an influence on the generated orders:

• When it is set to Yes, the multi-project management is prohibited.
  The project code is mandatory the same on the header and on the order lines.
  
• If the value of this parameter is No, multi-project management is authorized.
  You can modify the project code on each order line.
  

• Supplier (field BPSNUM)

The supplier is initialized by default to the first supplier in the list of suppliers available for the product but it remains available for entry. The supplier code entered must fulfill certain conditions: be active and not of prospect type.

This field offers several possibilities. The user can:

• directly enter the supplier code whose existence is checked in the Suppliers file,
• click the quick Supplier selection from the Actionsicon to do the following:
• select a supplier from the file,
• 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.

When the entered supplier is a Miscellaneouscustomer, a window automatically opens for the entry of the address. 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.

Following the entry of the supplier, different messages can be displayed in the following cases:

• When the supplier is declared to be on hold. This message can be blocking or a simple warning according to the value given to the dispute code in the supplier record.
• When the product is not referenced at this supplier. This message can be blocking or constitute a simple warning according to the choice made at the level of the ITMBPS - Supplier referencing (ACH chapter, REF group) parameter.
• When the order for the product is blocked for this supplier. This message can be blocking or a simple warning according to the value given to the blocking code in the product record.
• When the supplier's purchase unit is different from the entered unit, a message is displayed and so 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 coherent 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's 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.

• Major version (field ECCVALMAJ)

• Minor version (field ECCVALMIN)

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

• Expected rcpt. date (field EXTRCPDAT)

This is the desired receipt date. It must always be entered. A date is automatically proposed and can come from different origins in the following order:

• It is the requirement date when it comes from a requirement that has been taken into account. When the line comes from a group of requirements, it is the date of the requirement that is nearest that is retained. If the date proposed is modified in this way to enter a later date, the user will automatically get a warning message.
• It is the order date increased by the supplier lead-time contained in the price list if it exists.
• It is the order date increased by the reorder lead-time from the product-site record if the product is stocked.
• It is the order date increased by the reorder lead-time from the product record if the product is not stocked.

This date is controlled with respect to the receiving site calendar. In the case of the site being unavailable on this date, a blocking message appears and another date must be entered. Furthemore, if the date entered is earlier than the calculated date, a warning message can be displayed with the possibility to proceed or to refuse.
Once the order line has been validated, this date will not be modified by a price list reinitialization. Upon order validation, this date is used to generate the product provisional stock.

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, the contextual button allows the user to view the planned changes to stock.

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

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

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

• Net price (field NETPRI)

• Line amount - tax (field LINAMT)

• field LINACC1

It is the purchasing account. If this field is not entered, the account will be automatically determined by the accounting code for the product depending on the setup of the PORD automatic journal.

The presence of this field depends on the entry transaction used.

• Purchase type (field LINPURTYP)

It is the purchase type (purchase of goods or purchase of fixed assets) used to determine the tax account to use. The presence of this field depends on the entry transaction used. By default the type is "Purchase of goods".

• field CCE1

The setup determines whether the analytical dimensions can be modified. These are initialized in compliance with the default dimension setup.

In creation mode, if no order line has been entered and the project code is modified, analytical dimensions are reset based on the setup of the default dimensions.

In creation mode, as in modification mode, if an order line has been entered and the project code is modified, analytical dimensions are not reset.

• QC (field QUAFLG)

This code is used to define whether the product must be controlled on stock receipt.
The setup defined in the Product category is used to initialize the level of control of the Product-site record and Supplier-product record.The level of stock control on the Supplier-product record represents the finest level of setup and is used to initialize the level of control by purchase order. 

• No control
  The control is defined according to the management rules. It can be modified manually.
• Non modifiable control
  The quality control is mandatory in stock receipt: only a 'Q' status can be entered.
• Modifiable control
  In a miscellaneous receipt into stock, the quality status is initialized to the value 'Q', modifiable by 'A' or 'R'.
  The quality control code can also be defined at the purchase order level.
  • If in the order the quality control is set to 'Yes', the quality control is mandatory and the receipt is made with one of the sub-statuses Q* defined in the product management rule for movements of receipt type.
    If no sub-status is defined, the status cannot be entered upon receipt.
  • If in the order the quality control is set to NO, the quality control is not mandatory.
    At the time of receipt, the default value of the suggested status is 'A' and it is possible to enter or select all the statuses defined in the rule for the management of the receipt type movement for the product.
• Periodic control 
  The control is automated according to the number of receipts for this supplier and this product. In that case, the stock status can still be modified upon receipt.

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 field is subject to the Exchange of goods declaration (Intrastat).

This increase coefficient is used in the Intrastat declaration for the exchange of goods. It is used in supplier invoices and applied to the fiscal value of the product line to obtain the statistical value.
It is initialized by the increase coefficient entered on the Product-supplier record; otherwise, by the one of the Supplier record.

• Country (field ORICRY)

The country code for the origin of the goods, initialized to the country code associated with the order supplier.
This field is used to indicate the country where the goods originated in the sense of EU customs rules on the origin.
For the INTRASTAT exchange of goods declaration, the EU country code field associated with this code in the country table is used.
For supplier returns this will be the destination country.

• Line type (field LINTYP)