Receipts

• Receiving site (field PRHFCY)

The site code is mandatory. It is initialized by default by the stock site code associated with your user code. To modify this code, click the Selection icon to display the list of authorized sites.

Sites are not subject to any restriction in order to authorize products that are not managed in stock, to be received on sites with no storage role. This can be the case of miscellaneous supplies.

At this stage, you can choose the orders and deliveries to be processed from the Orders and Deliveries selection lists, available in the selection panel.

In order to limit the proposed selection of orders or deliveries:

• enter additional information in the header,
• click Picking criteria from the Actions panel and enter additional filters.

• Intersites (field BETFCY)

This information cannot be modified and specifies whether the receipt has the type 'inter-site'.

If the entered supplier is of the intersite type, this check box is automatically selected and can no longer be accessed when an intersite or intercompany delivery is selected.

To carry out this type of supplier receipt, you first need to assign roles to the various set up sites:

• The supplier at the origin of the receipt must define a sales site (Management tab in the Supplier record, the inter-site check box must be selected and a sales site must be associated with this supplier. It is advised for readability reasons to associate a supplier code with the site code).
• The receipt site must identify a delivery address (receipt site on a customer delivery address) for a customer identified as a purchase site.

A supplier receipt is automatically considered as being of the type inter-sites or inter-company if the supplier is identified as being a site. The difference between intersites and intercompanies is based on whether or not the supplier site belongs to the same legal company as the receipt site. If the sites belong to different companies, the receipt will be considered as intercompany and intersite, otherwise, it will be considered as intersite only.

An intersite or intercompany receipt is processed through the classic method. The only difference is that an intersite receipt cannot be invoiced.
The creation of such a receipt, in addition to the effective update of the stock (by increasing the physical stock) and the entry of the receipt movement in the stock journal, the update of the stock totals In transfer (for the site that has carried out the expedition) and In transit for the receiving site.
When a receipt of this type in entered, it can be the object of a supplier return at the shipment site at the origin of the receipt.
During the receipt of a sales shipment of this type, the stock information us automatically picked up from the customer shipment (lot, sub-lot, serial number).

Note:
In the case of an inter-site receipt, the calculation of the purchase cost and of the stock cost does not take into account the line amount, the not deductible taxes and the invoicing elements.
For the stock cost calculation, the invoicing elements can be taken into account. To do so, the value 'Yes' must be assigned to the BETFCYCST - Integration of invoicing elements parameter (ACH chapter, COS group).

• Intercompany (field BETCPY)

This information, which cannot be modified, indicates if this is an intercompany receipt.
When the receipt relates to an intercompany supplier (site of a different company), the receipt can be invoiced.

• Receipt (field PTHNUM)

The receipt number is automatically generated after validating the receipt creation, based on the setup of the sequence number associated with the receipt document. If the entry of this sequence number is manual, it can be entered manually.
In the case of an inter-site receipt, you can define another sequence number counter to identify the receipts.

• Supplier (field BPSNUM)

Enter the supplier at the origin of the receipt. The selection lists specific to the intersite and intercompany orders and deliveries available for receipt are filered to those related to the entered supplier.

From the Selection icon, you can:

• select a supplier from the list of active suppliers.
• access, based on your authorizations, the supplier record, and create a new supplier if necessary.

• Receipt date (field RCPDAT)

The receipt date is initialized by default to the current date. It can be modified. You can enter a receipt date earlier than the current date to enter a receipt that could not be entered on the system on the day of the physical receipt. However, you cannot enter a date later than the current date.

This date is then taken as the posting date to generate the stock movements during the creation of the receipt. A check will be carried out with respect to the periods file in order to ensure that the movement can be carried out on this date (Stock closing concept).
Once the receipt has been created and the stock movements carried out, you can modify the receipt date, but the associated stock movements will not be updated. You will receive a warning message.

• Supplier packing slip (field BPSNDE)

Use this field to indicate the number of the supplier delivery note. This field contains free text. It is optional.
A non-blocking check is carried out to verify that the delivery number does not already exist for this supplier on another receipt.

When the receipt comes from an intersite or intercompany delivery, the original delivery number is displayed and the field can no longer be modified.
If two deliveries of this type have been selected, the field then becomes available for modification and is reset to an empty value.

• Packing slip date (field NDEDAT)

The date is initialized by default to the current date. You can modify this date and enter the delivery note date mentioned on the supplier delivery note attached to the goods.

When the receipt comes from an inter-site / inter-company delivery, the delivery note date is initialized by the delivery date of the inter-site / inter-company shipment and the field is no longer accessible. If two deliveries of this type have been selected, the field displays today's date and becomes available for modification.

• Currency (field CUR)

The currency proposed by default is that associated with the supplier entered in the receipt header. It remains modifiable provided no receipt line has been entered. If a document is selected via picking although no receipt line has been entered, the receipt currency is initialized to the currency of the selected document.

From this field, you can directly enter a currency code, subject to an existence check in the table of currencies, or click the Actions icon to:

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

The receipt lines, either direct or coming from another document, inherit from this currency. For the lines coming from another document, the amounts are converted into the receipt currency.

After you have created a subcontract receipt, you can no longer modify the currency.

• Rate type (field CHGTYP)

The exchange rate type proposed by default is the exchange rate type associated with the supplier at the origin of the receipt. An exchange rate type is used to determine a currency rate in the exchange rate table, taking into account the receipt date or the original order date, based on the PTHCURDAT - Date of exch. rate for receipt parameter value (ACH chapter, CUR group).

In a receipt, use this information to:

• Determine the prices and discounts for a direct receipt, based on the price lists authorizing currency conversion
• Value the stock receipt when the valuation method of the Product-site is ‘Order price’.

This information can be modified as long as no receipt line has been entered.

After creating a subcontract receipt, you can no longer modify the rate type.

• Warehouse (field WRHE)

The presence of this box is subject to the activity code WRH.
Movement warehouse, suggested by default for all the document lines.
It must be entered if it is defined as mandatory at the level of the entry transaction.
It is loaded in priority with the warehouse defined for the user. If it fails to be set up at user lever, it is initialized with the warehouse defined, by default, at site level for this type of movement.

• Dock location (field SRGLOCDEF)

This field is displayed if the entry transaction authorizes receipts on dock. Use this field to enter the dock type location used by default for the stock receipts to be performed. A selection window is used to select the dock type locations defined in the receipt site. The specified dock location must be associated with the warehouse, when the latter is specified.

A dock location corresponds to a ‘pending put-away’ (storage) location. It is used to receive the goods quickly, and later to more precisely identify and store these goods. This put-away is achieved using the Put-away plan function. The stock detail information, such as the license plate number, lot, sublot and serial number, does not need to be entered right away. However, for products managed in stock, the mandatory information is the receipt unit, the quantity and the stock status.
When a license plate number is entered, all the information related to stock line detail should be entered (lot, sublot, serial number). Thus, even if the location type is ‘dock’, it will not be possible to access the line from the Put-away plan since the line is considered as put away.

• 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.
  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 clear this document, the project code is not deleted.
  If you modify the document header project code, this code is automatically used on all the lines.
  
• When this parameter is set to Yes, the management of multiple projects is authorized.
  In direct creation, the project code you enter 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.
• 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.

When an analytical dimension type is used for the Project management tracking, then any modification of the project code made at header level will be redistributed to the lines; if the modification applies to a document line, then the dimension code of the dimension type will be reset. This reinitialization is compliant with the Default dimensions setup.

Inter-sites and inter-company specificities: for an inter-site receipt, the project code automatically defaults from the purchase delivery and not from the purchase order. However, for an inter-company receipt, the project code defaults from the source purchase order.

• Original doc (field TYPVCR)

• CAI number (field CAI)

• CAI validity date (field DATVLYCAI)

• Order (field POHNUM)

This is the number of the purchase order that originated the receipt line.
If you want to perform a supplier receipt with respect to an original order, without using the order selection window, enter the number of the target order in this field.
Otherwise, click the selection icon to pick an order from a short list filtered on the supplier. You can also click the Actions icon to access the order if necessary.
The order number is not mandatory if the PTHDIR - Direct receipt parameter (ACH chapter, REC group) authorizes the entry of direct supplier receipts.
Depending on the receipt transaction used, you can move the order number and line number to the end of the receipt line. In this case, they will no longer be accessible but will continue to be loaded. The selection of orders can then only be carried out from the selection panel.

• Line (field POPLIN)

This is the number of the purchase order line that originated the receipt line.
A receipt line can involve only one order line, it will therefore be necessary to enter this line number if the order number has been entered. Use the Actions icon to select one of the lines of the relevant order.
Once the order line is entered, certain fields will be automatically initialized as a function of the information entered at the level of the order line. It remains possible to modify certain fields and/or to enter additional information.
The order line number is not mandatory if the PTHDIR - Direct receipt parameter (ACH chapter, REC group) authorizes the entry of direct supplier receipts and if no order number has been entered.

• Product (field ITMREF)

This information is compulsory. This is the product code for the receipt that you are entering. It will be automatically populated if an order line or a delivery line has been selected and can no longer be accessed in this context.

From this field, you can:

• Select an active product
• Access the product record, depending on your authorizations, and, if necessary, create a product.

Once the line is entered, it is no longer possible to access this field.

• Description (field ITMDES)

This is the description translated into the supplier's language. When the receipt originates from an order or a delivery, the translated description will be inherited from the original purchase line.

This description will be transferred with any modifications to the supplier invoice. This description will be printed on the internal delivery note.

From this field, click the Actions icon to access the Products record.

• Standard description (field ITMDES1)

This is the description entered in the supplier's language. When the receipt originates from an order or a delivery, the standard description will be inherited from the line of the original purchase order.

This description will be transferred with any modifications to the supplier invoice.

From this field, click the Actions icon to access the Products record.

• Product type (field ITMKND)

You cannot enter the product type:

• On order picking, the product type is recovered from the Standard, Service or Subcontracting document.
• Upon direct receipt, the product can be a Standard or a Service type product. You cannot select a Subcontracting type product.

A Standard type product is a 'physical' product (managed in stock or not). A Service type product is a product that is not managed in stock, whose category is Service.

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

• Unit (field UOM)

In the event of a receipt originating from an order or a delivery, the default receipt unit will be the unit entered on the original document.
In the event of a direct receipt, the submitted unit is the supplier’s purchase unit or the purchase unit if the Product-supplier record has not been defined.
You can modify the submitted receipt unit. The selection icon displays the lists of units grouping the stock unit, the product packaging units, the product purchase unit and the different units specified for the supplier.
Likewise, you can populate the same receipt line with different units. For that purpose, detail the line in the Enter detailed quantities window. This window opens automatically if stock information is missing from the line entry. Otherwise, open this window using the Actions icon that you can access on the line. If a receipt line is distributed over several different units, the Unit field of the document line is loaded with the stock unit.
Once the receipt has been saved and the stock movements have been carried out, you can no longer directly modify this information. You will need to use the Receipt modification function.

• Quantity (field QTYUOM)

This field displays the received quantity in receipt unit. The quantity suggested by default corresponds to:

• the total quantity ordered or delivered in the case of a receipt created from an order or delivery.
• the shipped quantity in the case of a shipment receipt.

You can change the quantity as long as the receipt has not been created yet.
Once the receipt has been created, you can modify the quantity as well, but only for products which are not managed in stock. For products which are managed in stock, since the stock movements have already been performed, you are not authorized to modify the received quantity in this field: you need to use the Receipt modification function, available from the Actions icon on the receipt line.
Important notes on subcontract receipt lines with or without WO:

• If the received quantity is less than the ordered quantity for the released and received product, or for the consumed materials related to the subcontracted product, you must manually identify the consumed material lines. Click Subcon. order issues from the Actionsicon to display the stock lines. Next, click the Actions icon at receipt line level, then select Enter detailed quantities to specify the quantity actually consumed.
• Once the receipt has been saved, you cannot modify the received quantity or the stock information, irrespective of the released product received or of the materials consumed for the subcontracted product.

When a receipt line is partially invoiced (directly or through an order invoice), or when a line is linked to an additional invoice, you are no longer authorized to modify the quantity because this modification would impact the distribution of the invoicing elements.

When the receipt line originates from an inter-site or inter-company delivery line, you can:

• Receive less than the delivered quantity. A warning message will warn you.
  In this context, two interpretations are possible:
  
  • The delivery occurred only in part because the goods will be entered over several receipts or because the entry of the receipt is not completely finished.
  • The delivery occurred only in part because there is an error in the entry of the original delivery or because the goods were stolen or lost.
  In this case it will be necessary to carry out a corrective action at the shipment site.
• receive more than the expected quantity. A warning message will also signal this. It is probably due to an error on the original delivery. As a consequence it will then be necessary to correct it. The receipt line closing field is never available in this context.

If the receipt comes from a delivery request and only part of the request is received, this request will be automatically split and the new generated request will or will not be closed depending on the closing value calculated for the receipt line.

When the receipt line is created from an order line (receipt of an order or shipment linked to an order line), you can:

• receive less than the ordered quantity. The management of the balance will then depend on the POHCLE - PO line closing method parameter (chapter ACH, group REM) and the product record (for the tolerance). Depending on the value assigned to this parameter and on the transaction used, you can decide to manually close the balance.
  
  When the receipt relates to products which landed costs are managed in a cost structure, the quantity can impact the calculation of costs (based on the defined cost type).
  In this case, if the receipt is a partial one and this concerns:
  
  - an order receipt, the amount of the costs on received lines is determined based on the pro rata of the received quantity if the STCPTH - Cost loading upon order rcpt parameter (chapter ACH, group REC) is set to Pro rata. If it is set to Recalculation, the amount of the costs is recalculated based on the quantity but also on all the criteria that have an impact on the calculation (especially the weight and volume).
  
  - A shipments receipt, the amount of the costs on received lines is determined based on the pro rata of the received quantity. Besides, based on the set of criteria, the recalculation impacts the calculation (e.g. weight and volume) performed during shipment.
  This rule also applies in case of modification of the quantity, regardless of whether the modification is performed before or after the creation of the receipt line.
  
• receive more than the ordered quantity provided that the RCPORD - Allow over receipts parameter (chapter ACH, group REM) authorizes it. You will still be notified by a warning message. When receiving a shipment, no control based on the shipped quantity is performed.

• 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 conversion (field UOMSTUCOE)

This is the conversion coefficient between the receipt unit and the stock unit. This information can be accessed for packing units if the setup authorizes it (refer to the packing unit grid on the Units section of the Products record). This information cannot be accessed for the other units (product purchase unit, supplier purchase unit, supplier packing unit).
If the product has the sub-contract type, the conversion coefficient between the receipt unit and the stock unit can never be modified.

• STK (field STU)

This is the storage unit of the product. This information is not available for modification.

• STK qty. (field QTYSTU)

This quantity corresponds to the quantity in stock unit after conversion of the received quantity into stock unit using the conversion coefficient between the receipt unit and the stock unit.
It is not possible to modify the received quantity in STK except for the units whose coefficient can be modified. In that case, the receipt quantity in receipt units is adjusted.

• Disputed STK qty. (field RRRQTYSTU)

This information can only be accessed for the products that are not managed in stock. It provides, in stock units, the non-complying received quantity.

This information can be used:

• On entering supplier returns Refer to the PRTNQTY -Return from status 'A’ parameter (ACH chapter, RET group).
• On entering the supplier invoice control Refer to the PIHQTYAQR - Billable quantity parameter (ACH chapter, INV group).

• Warehouse (field WRH)

The presence of this field is subject to the activity code WRH.
It is loaded with the warehouse displayed in the document header.

• It can still be changed if this field is set up so as to be entered at entry transaction level.
  When it is entered, the warehouse is automatically loaded on the stock detail lines and cannot be modified.
• It cannot be modified when the entry transaction is set up as single-warehouse managed. The header warehouse is then mandatory and the warehouse cannot be entered either on the document lines or on the stock detail lines.
  
  To manage multiple warehouses and enter the same slip line on various warehouses, you must enable the entry of the warehouse-line at the entry transaction level. To split a line onto several warehouses, click, the Actions icon and select Enter detailed quantities.
  When a receipt line is distributed on various warehouses, this field is loaded on the slip line with character '$'.

The warehouse entered on the line has priority over the warehouse entered in the header.

Direct receipts or receipts originating from an order:

The setup of the miscellaneous receipt transaction determines if the field can be accessed from the receipt note line.
When a warehouse is specified, it can no longer be accessed at the level of the note line detailed entry.
To manage multiple warehouses and enter a same note line in different warehouses, you need to detail the line in the Enter detailed quantities window. This window opens automatically if stock information is missing from the line entry. Otherwise, click the Enter detailed quantities action from the Actions icon available on the note line.

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

• Container (field TCTRNUM)

This field is subject to the LPN - License plate no. management activity code.

Indicate the container used. It is initialized based on the default container defined for the Product-site and can be modified if the entry in this field is enabled at the entry transaction level.
The entered container is used to filter the license plate number selection list.

• License plate number (field LPNNUM)

Help common to stock entry functions (Miscellaneous receipts, Receipts, Customer returns, etc.) and the Invoices function (in this case, the field is only displayed and editable for a credit memo or a direct invoice).
This field is subject to the LPN - License plate no. management activity code.

The management of this field depends on the 'Mandatory' or 'Optional' nature of the license plate number, which is defined for the Product category on the Receipt flow section.

In both cases, you can select the license plate number to be used. The selection list displays the active license plate numbers (both 'Free' or 'In stock') associated with the entered container. If no container is specified, the selection list displays all active license plate numbers attached to the site and available in stock. These containers are the ones you created previously, either by unit via the License plate number function or by batch via the License plate number creation function. You can also directly access the License plate numbers function in order to create a number and then switch back to entry mode on the document.
If you want to enter multiple license plate numbers on the same document line, leave this field blank and click Enter detailed quantities entry from the Actions icon available on the document line.
When you enter a license plate number, there is no restriction on the line quantity, as compared to the capacity of the container used.

• When the license plate number is 'Mandatory', you can leave this field blank and create the relevant license plate number(s) 'on the fly'. The number of containers is determined automatically based on:
  - The container capacity; This capacity is defined on the Product-site record, Management section, based on the packaging and/or stock unit of the product.
  - The line quantity; When multiple containers are required, the number of containers is displayed on the Enter detailed quantities window. This window opens automatically if stock information is missing from the line entry. Otherwise, click the Actions icon from the document line to open it.
  After the creation process, the '$' symbol is displayed in the License plate number field of the document line if the line has been distributed over different license plate numbers. To view the list of license plate numbers used, click the Actions icon on the document line and open the Receipt modifications window.
  You can only create numbers 'on the fly' when the following conditions are met:

- The License plate number is set to 'Mandatory' for the Product category.
- The entered container and unit must be defined in the containers setup table at the Product-site level.
- The container capacity must be defined in the same unit as the document line.
Once the numbers have successfully been created 'on the fly', the License plate number label printing window is automatically displayed if printing is authorized by the entry transaction.

• When the license plate number is 'Optional', no 'on the fly' creation is performed. If you want to use one or several containers, you need to manually enter their license plate number on the document line, or in detailed line entry mode. You may also use the License plate number assignment function afterwards.

Inter-site / inter-company specificities: for an inter-site or inter-company receipt, the license plate number does not correspond to the one specified on the sales delivery, since the LPN is single-site.

• Status (field STA)

The stock status is used to define if a product is:

Direct receipts or receipts originating from an order:

The status is initialized based on the default status defined by the management rule assigned to the 'Supplier receipt' movement type.
If no status is specified in the rule, no value is suggested.
If the product is managed with quality control (editable or not), the authorized and default statuses also depend on this rule (see Submit to quality control field).

The status is not mandatory on the receipt line. If it is not entered, the Stock detail window automatically opens at the end of a line entry so that a status can be specified.
You can choose not to enter the status on the document line because the goods that are booked in are of a different quality. In this case, a breakdown must be performed: you can enter the breakdown information in the Stock detail window.

When several statuses have been assigned and the stock lines have sub-details, the '$' sign is displayed in these fields at the end of the document line entry.
Depending on the management rule used for the 'Supplier receipt' movement type, you can set up and generate an analysis request during the receipt to stock if the status of the goods is "To be controlled" (status Q*).

Receipt originating from an inter-site delivery:

The status is initialized based on the status of the delivery if the status is authorized by the management rule assigned to the 'Supplier receipt' movement type (see the authorized Statuses and Sub-statuses).

If the delivery status is not authorized by the management rule defined for the receipt or if the quality control is not editable, then the default status of the management rule applies (it also needs to correspond to the quality control rule).

• Loc. type (field LOCTYP)

Location types are used to codify warehouse locations according to storage characteristics such as their dimensions, authorized statuses and technical constraints.

The location type is automatically loaded from the location type associated with:

• the container (if entered); The location type can be modified if the status of the container is ‘Free’, which means it does not contain any stock lines yet.
• the products by warehouse (if warehouses are managed);
• the product-site.

In all cases, the location type can be modified if its entry is enabled at the level of the entry transaction.

You may only enter a ‘dock’ type location if the entry transaction authorizes receipts on dock.

When warehouses are managed, entry of a location type is only permitted if at least one location is linked to the entered type and warehouse.

• Location (field LOC)

Depending on the entry transaction setup, the information related to locations is accessible for entry at receipt note line level.
On the other hand, in all cases, these fields can be accessed from the detailed entry of the receipt note, provided that the product is managed by location. If the product is not location-managed, the detailed entry of the receipt does not display the Location type and Location fields.

The storage location is automatically loaded based on the location type, if it is specified. Otherwise, the location taken into account is the following (in order of priority):

• the location that may be associated to the entered license plate number. It can be modified if the status of the container is ‘Free’ and thus does not contain any stock lines yet.
• the default location defined in the Product-warehouses record, if warehouses are managed.
• the location defined in the Product-site record. This value can later be modified.

When the warehouses are managed, only a location linked to the specified warehouse can be entered.

Additionally, it is possible to enter on the same receipt note line using several different locations. In order to do this, you need to detail the line in the Quantity detail entry window.This window opens automatically if stock information is missing from the line entry. Otherwise, open it by clicking the Actions icon from the note line.
If a receipt line is distributed over several location types and/or different locations, the corresponding fields on the document line display the '$' character.

• Supplier lot (field BPSLOT)

Direct receipts or receipts originating from an order:

If the product is managed by lot, you can enter the original supplier lot (if known) for information purposes (no control applies if it is an internal lot, which can only be linked to a single supplier lot).
It is recorded in the stock file and corresponds to the internal lot number. This ensures that the origin of goods can be tracked.

A selection window is used to choose a supplier lot among known ones (that have the object of a receipt).
To enter several supplier lots, do not enter the information on the receipt line but in the Stock detail window. When exiting this window, a '$' sign is displayed in this field to indicate that the information includes sub-details.

Receipt originating from an inter-site delivery:

This information is not accessible in this context and this is irrespective of the management rule associated with the product category. The supplier lot proposed is the lot coming from the original shipment.

• Lot (field LOT)

Lot concerned by the receipt transaction.

• No. of sublots (field NBSLO)

This field contains the number of sub-lots concerned by the stock transaction.

• Sublot (field SLO)

Sub-lot concerned by the stock transaction.

• Ending sublot (field SLOF)

This field indicates the last sub-lot on which the stock movement is applied.

• Starting serial number (field SERNUM)

• Enter the first serial number concerned by the movement.
  When the issue applies to the stock line of a product managed in Issue/receipt and including discontinuous serial numbers or differentiators such as the lot, status or location, the serial number selection is performed in the stock issue Detailed entry window. This window opens automatically at the end of a line entry or from the Actions icon.
  If an issue line is distributed over several serial numbers, the Serial number and Ending serial number fields of the document line are loaded with the $ character.
• When the issue applies to the stock line of a product managed in Global issue/receipt, you can enter the first serial number. If the system automatically determines a stock line including the quantity to be issued, the ending serial number is automatically loaded. Otherwise, this first serial number is deleted automatically and the Detailed entry window of the stock issue opens automatically at the end of the line entry so you can select the serial number sequences to be issued.
  The issue table will then be loaded with as many issue lines as sequences of issued serial numbers.
  

• Ending serial number (field SERNUMF)

This is the serial number of the product.

• Identifier 1 (field PALNUM)

Use this field to enter additional information, if necessary.

• Identifier 2 (field CTRNUM)

This field indicates the first recorded identifier.

• Close (field WSOLDE)

Indicates if the receipt line closes the order line.
This indicator defaults to ‘Yes’ or ‘No’ based on the received quantity and on the value of the POHCLE - PO line closing method parameter (ACH chapter, REM group).
When additional invoices on order have been recorded, if the order line is closed then all the additional invoices recorded on this order line are taken into account. In addition, even if the order line has been received (all at once or not) and has been the object of one or several additional invoices, it is only upon closing the order line that these invoices will be taken into account and that stock adjustment movements will be applied. The additional invoices are then distributed with respect to the received quantities of each receipt of the order line.

• Ship. closed (field WSHDSOLDE)

Indicates if the receipt line closes the shipment line.
This flag is initialized to 'Yes' or 'No' depending on the received quantity:

• When the receipt line closes the shipment line, this flag is automatically set to 'Yes' and cannot be modified.
• When the receipt line does not close the shipment line, this flag is set to 'No' but can be manually set to 'Yes'.
  

• Project (field PJT)

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 of the document line is never available for entry. In direct creation, it is loaded automatically with the code entered in the header and cannot be modified. In case of a document conversion, it is loaded with the project code of the lines of the selected document and cannot be modified.
  Additional lines must have the same project code. In case of line addition, the picking lists are automatically filtered so that only the documents with the same project code are displayed.
  If you modify the document header project code, this code is automatically used on the lines.
  
• When this parameter is set to Yes, the management of multiple projects is authorized.
  The project code of the document line is initialized with the header code and in case of document transformation, with the code of the selected document lines. The following lines can have a different project code.
  You can only modify the project code of lines if entering this field is authorized by the chosen entry transaction.
  
  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.
  • 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.
  
  In modification mode, the project code management depends on the value of the CTLOPPCOD - Mandatory projectcontrol parameter.
• 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.

When an analytical dimension type is used for the Project management tracking, then any modification of the project code made at header level will be redistributed to the lines; if the modification applies to a document line, then the dimension code of the dimension type will be reset. This reinitialization is compliant with the Default dimensions setup.

• Gross price (field GROPRI)

This field is used to determine the Stock cost per unit of the product. This price is expressed in the receipt unit. When the principal information for the line necessary for the determination of a price list is entered, a price list search process is automatically carried out. The objective of this search is to recover:

• the gross price as well as the associated reason,
• The charges and discounts in percentages or in amounts to be applied to the line level as well as the associated reasons.

If the price list search is unsuccessful, then a search is launched on the base price of the purchase product. As a last resort, if the search on the base price does not return any result and if the PURPRICE - Price by default standard cost parameter (ACH chapter, PRI group) is set to Yes for the company of the receipt site, the standard cost is used to value the gross price (if it has been defined for the product).
When the entered price is null, a message is displayed requesting your confirmation. From this field, click the Actions icon to:

• View the price lists
• View the reasons associated with the gross price and the discount and charge fields
• View the list of the last 10 order prices
• Re-initialize the price by requesting a new price list search to update the prices and discounts
• Have the detailed explanation of how the net price is obtained from the gross price and the various discounts and charges.

In the event of an inter-site/inter-company receipt, or in the case of a purchase order receipt, the gross price and the discounts are initialized with those of the source document and cannot be modified.
Prices and discounts can never be accessed if there is a source document. They can be entered/modified only in case of direct creation of a receipt. During a direct inter-site receipt, if the original delivery prices are tax inc., they are converted into ex tax. on the receipt line.

This information will be used during the creation of a supplier invoice or an invoice to be received to value the invoice.

• field DISCRGVAL1

The different discount and charge fields that appear at the level of each return line are determined via the structure code associated with the supplier in their record.
The values contained in these fields come from the price list search and can be modified if the associated reason allows it (or if the reason value given to the UPDPRIPUR parameter allows it).
The Actions icon is used to view all the reasons associated with the price and discounts and to modify, if necessary, the reasons assigned to each of the columns.

• Net price (field NETPRI)

This is the unitary net price for the receipt line calculated from the gross price affected by any discounts and charges. This information cannot be accessed.
From this field, use the Actions icon to:

• View the reasons associated with the price as well as the different discounts and charges fields
• View the list of the last 10 order prices
• View the price lists
• Have a detailed explanation available describing how the net price is obtained

If the entered price is null, a message appears to request confirmation. However, this message is not displayed for the components of a BOM, for free items and for deliveries not to be invoiced.

A process for the Free items is triggered at the end of the delivery line. This processing generates all the free product lines (Gross price and discounts set to 0). If the value of the FOCPRI - Free product valuation parameter (VEN chapter, PRI group) is ‘Yes’, a price list search is triggered for the free item to assign it a gross price. The assigned price is compensated for, either by a line discount in percentage or a line discount in amount (according to the order of discounts) to obtain a zero net price.

When you click Create to save the delivery, and based on the value of the GRPPRI - Grouped price lists parameter, a message can be displayed, suggesting that a new price list search is run to determine the specificities globally linked to the delivery. At the end of the processing, the following can be generated on some product lines:

• a new gross price or new discounts or new charges for the line,
• free products that are not associated with a specific line.

• Line amount - tax (field LINAMT)

This is the unitary Net ex-tax price multiplied by the receipt quantity.
 This information cannot be accessed.

The tax inc. amounts are converted into ex tax amounts on the receipt if the original delivery has a tax inc. price.

• Currency (field NETCUR)

This is the currency in which the amounts displayed in the previous columns are expressed. The prices for the receipt line are expressed in this currency. This information cannot be accessed.

• When the receipt comes from an order line or a delivery line, the currency code inherits the currency code from the original document.
• For a direct receipt line, the currency is loaded based on the currency of the receipt header and corresponds to the currency of the supplier.

• 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 order price of the receipt by including costs that have been previously estimated.
Upon receipt of the supplier invoice, the landed costs impacted on the stock can be adjusted with the actual costs identified in the supplier invoice if the valuation method of the product authorizes adjustments and if parameter PIHCPR - Invoice price adjustment also authorizes it.

• Upon direct receipt, this information is initialized with the landed cost coefficient entered for the storage site of the product-supplier or, if this is not possible, with the one entered in the Product-supplier record.
  If there is no product-supplier record, the coefficient entered in in the "Supply" section of the Product record is considered instead.
   
• Upon order receipt, this information is initialized with the landed cost coefficient of the order.

The landed cost amount calculated is displayed from the Actions menu, by right-clicking "Line cost" (in the "Cost detail" section, "Undetailed costs” grid).

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

• Upon direct receipt, it is initialized with the fixed cost per unit entered for the storage site of the product-supplier or, if this is not possible, with the one entered in the Product-supplier record.
  If there is no product-supplier record, the fixed cost per unit entered in tab "Supply" of the Product record is taken into account instead.
  
• Upon order receipt, it is initialized with the fixed cost per unit of the order.

The landed cost amount calculated is displayed from the Actions menu, by right-clicking "Line cost" (in the "Cost detail" section, "Undetailed costs” grid).

• 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 company currency and document currency.
The presence of this field depends on the entry transaction used.
When it is managed, this information is initialized: 

• Upon direct receipt, with the cost structure entered for the storage site of the product-supplier or, if this is not possible, with the one entered in the Product-supplier record or, as a last resort, with the cost structure entered in the ‘Supply’ section of the ‘Product’ record. 
• Upon order receipt, with the cost structure of the order.

This information can never be modified.

The costs taken into account in the cost structure are displayed in the window that can be accessed via the "Cost structure detail". It remains possible to adjust the calculated amounts.
The costs are also displayed in the ‘Direct costs’ grid in the window that can be accessed via right-click option "Line cost" (in the ‘Cost detail’ section).

• 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 line purchase cost corresponds to the amount totaling the stock cost and the costs that remain payable by the buyer and are not used for stock valuation (transportation cost, non-deductible taxes, etc.).
It cannot be modified and is displayed only if the transaction authorizes it. It is expressed in the currency of the company.

• Upon direct receipt, its calculation mode varies according to the method used to evaluate the landed costs. The calculation mode is the following:
  • Global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account:
    Purchase cost =
    [ 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.
     
  • Method in which a set of costs detailed in a Cost structure is taken into account:
    
    Purchase cost =
    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.

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

• Upon order receipt, it is loaded with the purchase cost of the order.

Note: the non-deductible tax amount is displayed in the 'Line cost’ window, accessed by right-click on the line.

• Stock cost per unit (field CPR)

This is the unit amount by stock unit that can be used to value the stock (if the valuation method for a supplier receipt is Order price). The valuation method for the stock is defined by product category or by product category as a function of the storage site. It can also be set up by movement type.

It can be manually modified as needed, if the transaction authorizes it.
It can also be viewed on the Line cost window.

1/ Upon direct receipt:

• If the receipt line is not related to an inter-site delivery (this exception does not apply to inter-company deliveries), then the order price is equal to the result of the following calculation:

Line stock cost / Quantity (in STK)

• If the receipt line originates from an inter-site delivery line, then the order price is initialized by the stock issue price of the original delivery.

2/ Upon order receipt, the stock cost per unit is populated based on the value of the PRIFLG - Full stock valuation parameter (ACH chapter, REC group), as follows:

• If this parameter is set to Yes, the stock cost per unit is determined based on the order price. The stock value and the stock movement amount linked to the receipt are then recalculated with all the invoices, credit memos, additional invoices linked to documents, regardless of the order in which the documents were received. If these documents are already available and validated at the time of receipt, they are immediately taken into account through stock adjustments.
  Specific behavior of the additional invoices with the value of the New cost set to No and a given cost code: The amount of the adjusted cost is directly integrated into the stock cost per unit of the receipt line.
• If the parameter is set to No, the determination of the stock cost per unit depends on the context:
• When the receipt is created before invoice validation, the stock cost per unit is equal to the order price. The stock value and the stock movement amount linked to the receipt are then recalculated each time an invoice, an additional invoice or a credit memo is validated, through stock adjustments.
• When the receipt is created before the invoices are validated (invoices on orders), the stock cost per unit is determined only from the stock cost per unit of the first invoice and the related additional invoices. It does not take the order price into account although it can be different on the following invoices, credit memos or additional invoices.

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

• 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 currency of the company.

Upon direct receipt, its calculation mode varies according to the method used to evaluate the landed costs.

• Global method in which a Landed cost coefficient is applied and/or a Fixed cost per unit is taken into account:
  
  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 date defined by parameter PTHCURDAT - Date of exch. rate for receipt as the exchange rate date and the exchange rate type specified in the header of the receipt as the exchange rate type.
  
  
• 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 taken into account are only the ones with the Stock valuation flag set to: 'Yes')
  + total of the non-deductible taxes (if parameter NODVATSTO - Non-deductible taxes in stock is set to ‘Yes’)
  
  Calculation examples are to be found here.
  This amount is never calculated during the entry process but only when saving the document.

2/ On order receipt, the stock cost is loaded based on the value of the PRIFLG - Full stock valuation parameter (ACH chapter, REC group) as follows:

• If this parameter is set to Yes, the stock cost per unit is determined based on the cost price. The stock value and the stock movement amount linked to the receipt are then recalculated with all the invoices, credit memos, additional invoices linked to documents, regardless of the order in which the documents were received. If these documents are already available and validated at the time of receipt, they are immediately taken into account through stock adjustments.
  Specific behavior of the additional invoices with the value of the New cost set to No and a given cost code: The amount of the adjusted cost is directly integrated into the stock cost per unit of the receipt line.
• If the parameter is set to No, the determination of the stock cost per unit depends on the context:
• When the receipt is created before invoice validation, the stock cost per unit is equal to the order price. The stock value and the stock movement amount linked to the receipt are then recalculated each time an invoice, an additional invoice or a credit memo is validated, through stock adjustments.
• When the receipt is created before the invoices are validated (invoices on orders), the stock cost per unit is determined only from the stock cost per unit of the first invoice and the related additional invoices. It does not take the order price into account although it can be different on the following invoices, credit memos or additional invoices.

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

• Movement description (field MVTDES)

The description of the transaction is a comment that can be freely specified.

This comment will be written in the stock journal for each movement on the receipt line. You can modify it from the Stock detail window.

• Stock movement group (field TRSFAM)

Movement group, initialized by the movement group of the transaction being used.
This statistical information is recorded in the stock journal when saving the receipt/disposal movements. This movement group comes from the miscellaneous table number 9. The value given in the transaction setup corresponds to a default value that can/cannot be visualized and/or modified according to the transaction setup (entered, displayed, hidden field).

Statistical information used in the stock transactions associated with the shipment. This value is fixed if the original document does not reference a movement group. Otherwise, the movement group of the document at the origin of the quality control is suggested in priority.

• 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 PORD automatic journal.
 The presence of this field depends on the entry transaction used.
These accounts are loaded by default according to the accounts present in the order line that originated the receipt line.

• Type (field LINPURTYP)

The presence of this information depends on the transaction setup. The different product types are: Purchases, Fixed assets and Services.
When the receipt line arises from an order line, the purchase type will come from the order line.
In the case of a direct receipt or where it is linked to an inter-site or inter-company, the purchase type will be initialized as a function of the tax posting associated with the GL account entered previously.
If the receipt line is the object of purchase invoice control, the purchase type will be transferred to the invoice line.

• field CCE1

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

If the receipt line arises from an order line, the analytical dimension types are then loaded by the analytical dimensions present in the order 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 type is used for the Project management tracking, then any modification of the project code made at header level will be redistributed to the lines; if the modification applies to a document line, then the dimension code of the dimension type will be reset. This reinitialization is compliant with the Default dimensions setup.

In the case of a receipt for an inter-site or inter-company delivery, analytical dimensions inherit from the delivery dimensions, based on the default dimension code set up for the PTD receipt line.
During the purchase invoice control, arising from the receipt line, the analytical dimensions entered on the receipt line are transferred to the invoice line.

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

• Match status (field TWMSTA)

The Three-way match status field has the following values:

• Unblocked: a user with unblock access can override the blocking.
• Blocked: one or several lines are blocked (a warning may also be displayed).
• Warning: one or several warnings, but no line is blocked.
• Successful: matching is successful.
• Not applicable: no matching is carried out.

• 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 entered in the source order line in the case of a receipt arising from an order. In the other cases, it is initialized by the increase coefficient in the Product-Supplier record if it is entered, otherwise by the increase coefficient in the Supplier record.

• Country of origin (field ORICRY)

This is the country of origin of the manufactured products. This information is initialized with the country of the supplier's shipment address in the case of a direct receipt or a receipt coming from an inter-site or inter-company delivery. If the receipt originates from an order, the country of origin will be initialized with the code of the original country entered on the order line.
This information is used namely in the INTRASTAT file (Exchange of goods declaration). The ISO code of the country table is used.

• Tax 1 (field VAT1)

This field is used to enter a first tax code to apply to the received product.
The tax codes (VAT, additional levy and/or special tax, regional tax) can be modified in the receipt line if the transaction authorizes it.
They are normally initialized according to the tax determination rules that most often stem from crossing the supplier tax rule with the tax levels of the entered product.

• If the receipt line has as its origin an order line, the tax code will be inherited from the order line.
• If the receipt line originates from a direct inter-site or inter-company shipment, the tax codes are determined based on the tax rule and tax levels entered for the delivery.
• When converting a receipt line into an invoice or return line, the tax codes entered in the receipt line are transferred to these documents.

Click the Actions icon to select a tax code for each tax level.
Only one tax code consistent with the legislation and group of the company on the site can be entered.

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

• Closed (field LININVFLG)

This check box is selected if the receipt line is closed for invoicing. It is updated by the invoice control, but you can also update it by clicking the Close receipt action or the Close option available from the receipt line. Using these actions, you can also close a receipt linked to a remainder amount that will never be invoiced.

• Weight (field QTYWEU)

When receiving products for which landed costs are managed with a cost structure, the weight can have an impact on the costs calculation (according to the cost type defined).
In this context:

• For partial order receipts, the weight is only considered in the costs amount determination if the STCPTH - Cost loading upon order rcpt(chapter ACH, group REC) parameter is set to 'Recalculation'.
  If it is set to "Pro rata", the weight is ignored, since the amount of the costs is determined based only on the pro rata of the quantity actually received.
   
• For partial shipment receipts, the weight has no impact on the costs calculation. The amount of costs is only determined on the pro rata of the actually received quantity; costs are recalculated based on the weight during the shipment process. 
   
• For direct receipts, the amount of costs is recalculated on each weight modification, whether the modification is performed before or after the creation of the receipt line.

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

When receiving products for which landed costs are managed with a cost structure, the volume can have an impact on the costs calculation (according to the cost type defined).
In this context:

• For partial order receipts, the volume is only considered in the costs amount determination if the STCPTH - Cost loading upon order rcpt (chapter ACH, group REC) parameter is set to 'Recalculation'.
  If the parameter is set to 'Pro rata' the volume is not considered since the amount of costs is determined based only on the pro rata of the actually received quantity.
   
• For partial shipment receipts, the volume has no impact on the costs calculation. The amount of costs is only determined on the pro rata of the actually received quantity; costs are recalculated based on the volume during the shipment process. 
   
• For direct receipts, the amount of costs is recalculated on each volume modification, whether the modification is performed before or after the creation of the receipt line.

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

• Mfg./subcon. order no. (field VCRNUMORI)

For a subcontract receipt, the original WO number will be specified on the receipt line. Click the Actions icon to access the source document.

• 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: 'Standard', 'Subcontracted', 'Service' and 'Supplied material'.

• Category (field LINCAT)

This information is used to categorize the line: 'Normal' or 'For sub-contract'

• Invoiced (status) (field INVFLG)

• Invoiced (quantity) (field WINVFLG)

This field indicates if the quantities on receipt lines have been invoiced. This information can take three values:

• No,
• Partially,
• Totally.

• Closed (field WCLEFLG)

This information specifies if the receipt has been closed from the point of view of the invoicing. No invoice is pending for the receipt. The goods without invoices are considered as free and not valued.

For an intercompany receipt linked to a nonbillable sales delivery, the receipt is automatically considered as Closed.
As there can be multiple and legitimate overcharges, some lines cannot be invoiced and are considered as completed from an invoicing point of view. In this case, click Completion from the Actions icon available on the line to close or reopen receipt lines not linked to an invoice, but completed from an invoicing point of view. These lines may therefore be overpriced if required.

• Posted (field PSTFLG)

This information is used to identify if an Invoice to be received (IR) has been generated for this receipt (from the Invoices to receive generation function).

• Printed (field PRNFLG)

The receipt is considered as printed once the internal receipt note has been printed.

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

• Description (field TITLE)

Leave the default description displayed or type in a short description of this incidence of non-conformance. The default description is one of the following:

• The transaction type plus transaction number, for example, 'Purchase receipt RECFR0110038', 'Customer return SRTPT0310002', 'Production tracking WOTFR0110011' if you have clicked the Create action.
• The transaction type plus transaction number plus line number, for example, 'Purchase receipt RECFR0110038 4000', 'Customer return SRTPT0310002 1000' if you have clicked Create Non-conformance from the Actions icon on a transaction line.

This field is mandatory.

• field NBLIG

This field displays a line number in this particular table/grid/block.

• Non-conformance (field NCSID)

This field displays the unique identifier for this incidence of non-conformance.

Implementation > Sequence numbers

• Description (field TITLE)

This field displays the default description from the associated transaction or a manually entered description of this incidence of non-conformance. The default description is one of the following:

• The transaction type plus transaction number, for example, 'Purchase receipt RECFR0110038', 'Customer return SRTPT0310002', 'Production tracking WOTFR0110011'.
• The transaction type plus transaction number plus line number, for example, 'Purchase receipt RECFR0110038 4000', 'Customer return SRTPT0310002 1000' if the non-conformance was created from a specific transaction line.
  
  

• Document type (field DOCTYP)

This field identifies the type of transaction the observed problem, or failure or potential failure in a design or in production, or in a service, or in a process, or in the system has been reported against. If this non-conformance was raised directly from a transaction, this field will display the linked transaction type.

• Document number (field VCRNUM)

This field identifies the number of the source document or order.

• Line number (field VCRLIN)

This field identifies the associated line on the source document or order. If set to zero, this non-conformance was raised against the document as a whole rather than a specific line.

• Document date (field DOCDAT)

This field displays the key date from the Home section of the original document or order. For example, this can be the actual receipt date (Purchase Receipt), the return date (Customer Return), or the follow-up date (Production/Operation Tracking).

• NC quantity (field NCSQTY)

This field displays the actual quantity from the source document or order line that relate to this incident. It will either reflect the original (full) quantity from the source document or order line, or a manually entered (partial quantity) figure. For an incident resulting from the manufacturing process, for example, this will be the actual rejected quantity. The quantity is expressed in the stock unit.

• Original quantity (field DOCQTY)

This field displays the quantity from the source document or order line. The quantity is expressed in the stock unit.

• Supplier (field BPSNUM)

This field displays the code of the supplier for which the source document or order was raised. It is only displayed if the source Document type (field DOCTYP) is a Purchasing document.

• Customer (field BPCNUM)

This field displays the code of the customer for which the source document or order was raised. It is only displayed if the source Document type (field DOCTYP) is a Sales document.

• Project (field PJT)

This field displays the associated project code. The content can be one of the following:

• A project code
• A project code and a project budget code
• A project code and a project task code, that is a material task code, a labor task code (sales only), or a combined (mixed) labor and material task code.

If the content of this field includes a character such as an exclamation mark "!" this field links to the structure of the project. The character is the separator between a project code and the structure, either the project cost structure or the project operational structure. For example, if a material task code is 'USA-P3' and a project code is 'USA12345678', this field displays a link to the project operational structure as 'USA12345678!USA-P3'.

To provide a quick and easy visual reference the link to the project or project structure is distinguishable by the number of separator characters used. If there is no separator, the link is made to the project. A single separator character such as an exclamation mark after the project code (the first code) indicates the link type is a task (the link is to the project operational structure). Two separators placed after the project code mean that the link corresponds to a budget code (link to the project budget structure).

• Line status (field LINSTA)

This field indicates if this particular line is considered active and relevant to this non-conformance incident.