Loan Returns

• Receiving site (field STOFCY)

The site in which the return is carried out. It is:

• Initialized by default with the normal storage site for the user.
• Used to filter the shipments to be returned (the filter is carried out on the shipment site for the delivery).
• no longer modifiable from the moment there are return detail lines. The site must be defined with the 'Warehouse' flag set to the value "YES".

• Type (field SRHTYP)

Only one return type of the "Loan" category can be entered.  Besides, the legislation and company group for which it is defined must be consistent with those of the receipt site.
For further information, click here.

The return type is used to determine, amongst other things, the sequence number counter at use.

• field WSRHCAT

The category cannot be modified; it is determined by the chosen Invoice type.

• Return no. (field SRHNUM)

Return number that allows the return to be identified in a unique way.
This number is generated automatically or entered whenever a return is created based on the setup of the possible counter(s) associated with the chosen Return type.
If the assignment of the return sequence number has been defined as automatic, this field cannot be accessed and the code is assigned upon return creation.
Conversely, if the counter is defined with manual allocation, it is possible to enter the number manually. If it is not entered by the user, the system will automatically assign a return number according to the sequence number.

• Return date (field RTNDAT)

By default the return date is initialized to the current date.
It corresponds to the actual date of the product return (or material return in case of sub-contracting) to the company. It is used as a receipt to stock date for the returned product (or material) if the stocks are updated.

• Signed (field SRHCFMFLG)

• Ship-to (field BPCORD)

Code of the customer requesting the order, the direct delivery or the direct invoice. This code:

• must be managed in the customer table,
• must be of normal, miscellaneous or inter-company type,
• can be modified as long as no line has been entered on the document.

• Address (field BPAADD)

This field indicates the code of the address to ship to.
You can view the detailed address information by clicking Address from the Actions icon.

• On creation, this field is no longer accessible when a delivery line is created.
  
• Once the delivery has been created, you can no longer modify this field but you can still display the detailed address information.
  You can modify the address after clicking Address/Delivery from the Actions panel.

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

In the case where the receipt transaction authorizes a dock receipt (parameter active in the transaction setup), a dock location field appears in the receipt note header. This makes it possible to enter a location of the 'dock' type which will then be transferred by default as the return location for all receipt note lines. The specified dock location must be associated with the warehouse, when the latter is specified.

A dock location corresponds to a location of the type "pending storage". This authorizes the entry of stocks whose characteristics of lot, sub-lot, and serial number are not necessarily immediately identified. This type of receipt is used to rapidly book the goods and to then later to more precisely identify them and put them away. This put-away process is performed in the functionPut-away plan.

• Intersites (field BETFCY)

This non modifiable information specifies whether the return is of type inter-site.
When the return concerns an inter-site customer (site of the same company), the latter cannot be subject to a credit memo.

• Intercompany (field BETCPY)

This non modifiable informations specifies whether the return is of type inter-company.
When the return concerns an inter-company customer (site of a different company), an invoice credit memo may be created.

• Product (field ITMREF)

This field indicates the product reference code. It is generated by a sequence number counter (set up in function Sequence number counters) in the case when the product category has a sequence number counter code.

The reference cannot be modified. It is automaticaly assigned and displayed at product creation end.

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

• SAL (field SAU)

The unit in which this product is sold. The sales price is attributed to this unit.

This sales unit is also displayed by default in the Sales and Customer sections.

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

• Actual loan qty. (field DLVQTY)

From the quantity field, the contextual button enables the user to inquire the stock by site.
It is mandatory that the shipped quantity is entered. A warning message is displayed if the quantity entered is less than the minimum quantity defined in the product record. A warning message may also appear if the quantity entered is greater than the maximum quantity entered in the product record. These messages can be blocking according to the value of the SDACLOK - Price, margin, qty non blocking control (VEN chapter, AUZ group) user parameter.

When the shipped quantity is entered a price list search process is automatically carried out. The purpose 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,
• any free product(s).

The price list search process can be triggered in different ways depending on the product type entered.

In effect, if the entered product is of the type 'Normal', the search process is automatically triggered.

When the entered product is of the type 'Kit parent product' or 'BOM parent product, an initial price list search is triggered for the parent product ('Normal' type), then before triggering the price list search for the components, a read of the BOM file is carried out in order to identify whether different BOM codes of the 'commercial' type exist, in which case they are displayed in a window. If the product has only a single BOM code, it will be taken into account automatically.

After choosing the BOM code, different cases can occur according to the construction of the product BOM:

• Each component of the 'Normal' type is selected automatically.
   
   It is automatically replaced by the substitute product if the latter has been entered in the Product record and if the document date is superior or equal to the substitution date.
  For the other types of components entered below, when a substitute product is used, the original product description is displayed at the level of the components selection window.
   
• For each component of the 'Normal' (with formula) type, a window opens automatically displaying the set of products coming from the selection formula. If a 'Normal' component has also be recorded in the same sequence, this component is also displayed in the list. By default, it is automatically selected but it is still possible to de-select it.. Its quantity cannot be modified.
  It is possible to select one or several components from the selection. The buttons [Include all] and [Exclude all] are available for this purpose. As soon as no component is selected, the [Criteria] button becomes available so as to narrow the selection down when the number of table lines is too important (the number of lines depends on the number of lines remaining to be inserted in the document).
• For each component of the type 'Variant', a window opens presenting the set of variants listed at the BOM level or coming from a selection. The user must choose one.
• For each component of the type 'Option', the option is suggested and the user must accept it or refuse it. When several options are possible for a same BOM level, a window opens for the user to select one or more options or to refuse all of them.
• For each component of the type 'Multiple Option', a window opens presenting the set of components listed at the BOM level or coming from a selection formula. You can select several ones or refuse all. The buttons [Include all] and [Exclude all] are available for this purpose. As soon as no component is selected, the [Criteria] button becomes available so as to narrow the selection down when the number of table lines is too important.

The lines corresponding to the different BOM components are then generated:

• If the product is of the type 'Kit parent product', all the component lines are automatically generated. These lines become completely dependent on the parent component. They appear on the screen but are not accessible. The component quantity is automatically calculated from that of the parent product. If the parent product quantity is modified, the quantities of all the components are automatically recalculated. If the parent product is deleted, all the components are automatically deleted.
• If the product is of the 'BOM parent product' type, all the component lines are proposed and they are modifiable (except the sales unit). They are independent with respect to the parent product. If the parent product is modified or deleted, a question is posed over whether or not to transfer the modification or deletion to the components.

In both cases, a price list search for the component type is then automatically triggered and for each delivery line generated, a value is assigned to the type of line:

• 'Kit option' or 'BOM option' for a component of type 'Option',
• 'Kit Variant' or 'BOM Variant' for a 'Variant' type component,
• 'Kit component' or 'BOM component' for a component of 'Normal' type.

Certain price list controls are carried out on exiting this price list process:

• if the price is defined tax included, the tax-ex price is calculated.
• control on the calculated net price: if the calculated net price is less than the threshold price stored in the product a warning message is displayed.
• control on the profit margin: if the percentage margin is less than the minimum margin percentage stored in the product record, a warning message appears.

These different messages can be blocking according to the value given to the SDACLOK - Price, margin, qty non blocking control user parameter.

If the shipment comes from an order and an allocated quantity remains and a shortage on the order, the fact of increasing the shipped quantity will consume the allocations then the shortages still present in the order.

When the delivery line is created and the shipped quantity is then modified, the 'stock' detail window then automatically opens at the line end to give the user the choice of stock lines to be modified. The stock detail window does not open in only one case. If the delivery line is only associated with one stock line and the shipped quantity is decremented, the system automatically reduces the recorded quantity on the stock line, no intervention from the user required.

• Returned qty. (field QTY)

This field contains the quantity ordered by the customer and expressed in sales unit. It is initialized by default with the quantity left to return and remains modifiable. A quantity comprised between 0 and the quantity that left to return may be entered.

• SAL-STK conv. (field SAUSTUCOE)

Conversion factor used to calculate the quantity in stock units from a quantity entered in sales units: Quantity in STK = Qty in SAL * conversion factor.

This conversion factor can be accessed if the Sales unit field (SAU) has been entered, and has a value different from the stock unit. It can be initialized using the conversion factor table if the combination exists.

• STK (field STU)

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

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

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

• Planned return date (field DEXTRTNDAT)

This is the loan return date identified in the selected delivery. This information cannot be modified.

• Project (field DPJT)

• Update stock (field RTNSTOUPD)

This information is, by default, initialized to 'Yes' (except if the user parameter RETININULL - Non init. returned quantities is set to 'Yes' in which case the indicator is positioned to 'Yes' provided that the user has entered the returned quantity).
When this zone is set to 'Yes', provided the transaction permits it, it is possible to enter the information required for the stock movement in the return line. Otherwise, no stock receipt is entered for the returned goods because they are damaged and so no stock receipt is requested, or because the entered return is an expected return and thus the stock receipt is to be performed on receiving the goods.

According to the product configuration, some stock characteristics should be mentioned. These characteristics are:

• The "status". This is the product quality status.
• The "location type" and "location" if the product is managed on locations.
• The "internal lot".
• The number of "sub-lots" and the "sub-lot" number. The end "sub-lot" is calculated if several sub-lots are entered and if they are in a row (this information cannot be modified).
• The "supplier lot".
• The "serial number" if the product runs in series. The "end serial number" if several serial numbers are returned and are in a row (this information cannot be modified).
• The "movement description". This description is specified in the stock journal.

At return line end, a window for the Stock detail entry may open automatically if part of this information has not been entered or initialized. They should then be entered in this detail screen.

Besides the stock characteristics of the product, some rules control the stock receipts. For a loan return these rules can be described in a general fashion, see Stock management rules, in the section 'Loan return'. These rules can also be refined by Product category or by product category narrowed down by site. A stock receipt rule for a loan can also be defined by 'Product category' for a particular movement typology (see definition of the movement code in the setup of transactions related to Loan returns).

In the case of a loan return, since registering the delivery is mandatory, almost all the information is initialized automatically based on the stock information of the original document line. Some information must be entered manually or can be initialized according to the setup linked to this 'loan return' receipt movement.

• The Status: it is initialized based on the delivery status if it is authorized by the management rule assigned to the 'Loan return' movement type (see 'Status', and 'Authorized sub-status'). If the delivery status is not authorized for the management rule defined in the return, then the default status of the management rule is used.

The status is not mandatory in the return line but if it is not entered, the 'stock' detail window automatically opens at the line end so the status can be specified. In some cases, it is possible not to enter this status intentionally on the document line as the quality of the goods to be returned is different and because a split is required. This split will then be entered in the 'Stock' detail window. If the sign '$' is displayed in this zone at the end of the document line entry, it is because different status have been assigned and that a sub-detail exists for stock lines.

According to the management rule used for 'Loan return' movement typology, it is possible to set up the generation of an analysis request upon receiving the goods in stock if the status of goods is set to status to be controlled (Q * ).

• The location type and the location: if the product is managed on locations a default location can be initialized with respect to the management rule assigned to the 'Loan Return' movement type and to the locations set up in the 'Product/Site' record. The semantics identifying a location category make it possible to associate to this category a type of location and a potential location in the 'Product/site' record. The location type and the location defined in the 'Product/Site' can refer to a group of location types and/or locations if wildcards ( ?,*) are used in their definition (See Location Types and Product/Site). For some location typologies, their assignment will depend on their availability and on their capacity (capacity management). This information can be modified is necessary.

If the return transaction allows it, a location of the "dock" type can be entered in the return header. If this is the case, this location is systematically suggested by default. Dock-type locations are not suggested upon selection if dock receipts are not specified in the return transaction.

In some cases, it is possible not to enter a location and/or location type intentionally as the goods to be returned are distributed on different storage locations. This distribution is thus entered in the stock detail window. On terminating the entry, if the sign '$' is displayed in these zones, it is because different location types and/or locations have been assigned and that a sub-detail exists for stock lines.

From the 'Location Type' field, the contextual button can be used to:

• Select a location type.
• Tunnel access the table of location types, granted the user has authorization.

From the 'Location' field, the contextual button can be used to:

• Select a location.
• Tunnel access the table of locations, granted the user has authorization.
• Tunnel access the inquiry of 'Occupied locations', granted the user has authorization.
• Tunnel access the inquiry of 'Dedicated locations' for the product being entered, granted the user has authorization.
• The Internal lot: this information cannot be accessed on the return line. If the return is related to a delivery which only registers one lot number then this number is displayed on the line. If the original document, registers several lot numbers, the $ sign is displayed in the lot zone. If the delivery is a multi-lot delivery and the return only applies to part of the delivery, then the choice of sub-lot is carried out using the stock detail screen (by deleting unecessary lines). Same goes for the management of sub-lot numbers.
• The lot supplier: this information cannot be accessed in this context regardless of the management rule associated with the product category. The suggested lot is the taken from the original delivery.
• The Serial number: this information cannot be accessed on the return line in this context. If the serial numbers of the delivery line are in a row, then they are displayed on the return line. Otherwise, the $ sign is displayed in both fields so as to indicate the returned number are not ordered. If the original document contains several serial numbers and the return only applies to part of these numbers, then it is necessary to enter the stock detail window in order to choose the appropriate numbers. Only the serial numbers of the original delivery line can be selected. The selection window of serial numbers only suggests the serial numbers of the original document line.

Note regarding the entry kinematics upon creating a return:

When creating a return line by selecting a delivery line and several stock detail line are generated, the stock information can only be modified using the window Stock Detail. Only the following can still be accessed: 'Quantity' and 'Description' of the movement.

When only one stock detail line exists, the information related to the 'Status', 'Location type', 'Location' and 'Movement description' can be modified.

If the quantity is modified on the return line and several stock detail lines exist, then the detail window opens automatically so as to choose which line(s) is impacted by this modification.

If the quantity is increased on the return line and only one stock detail line exists, then the detail window opens automatically so as to specify whether the additional quantity applies to the same detail line or to another detail line.

If the quantity is decreased on the return line and only one detail line exists, then the stock window does not open.

Note related to the management of coefficients and return units:

When the return originates from the delivery, the units used to perform the stock movement are the ones of the delivery. This way, if a shipment has a box for sales unit, but the associated stock is calculated by the unit, then the unit used by default to carry out the receipt is the stock unit.

It is not possible to modify the conversion factor between the return unit and the stock unit. In the stock detail window, if other units are used or if lines with different coefficients are entered, then the unit of the return line is replaced by the stock unit so as to ensure that the conversion is performed with the units used upon stock receipt.

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

• Container (field TCTRNUM)

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

Select the container you want to use.

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

• Loc. type (field LOCTYP)

The location types are used to codify the warehouse locations according to their storage characteristics: size, authorized statuses, technical constraints etc.
They are associated with the products by site, and are used in this way to geographically group the products with similar characteristics.
According to the stock transaction parameterization, the location type for the product is proposed by default and can be modified in the transaction entries.

• Location (field LOC)

If the product is managed by license plate number, the location associated to the LPN is displayed. It is not editable.
If the product is managed by location and no container is entered, a default location can be initialized based on the management rule assigned to the ‘Delivery return’ movement type and on the locations set up in the 'Product/warehouses' record if the warehouses are managed. If it is not the case, the product is based on the locations set up in the ‘Product/site’ record.
The semantic identifying a location category is used to associate in the 'Product/site' record (or 'Product/warehouse' if warehouses are managed) a location type and a potential location.
The location type and the location defined in the 'Product/site' record (or 'Product/warehouses') can refer to a group of location types and/or locations if the wildcards (?, *) are used in their definition (see the Location types and Product-site documentations).
You can view documentations about Location types and the Product/site for more details.

In the case of some location types, the assignment will also depend on their availability or their capacity (replenishment management). This information can be modified if necessary.

If the return transaction allows it, a dock type location can be entered in the return header. If this is the case, it will be this location that will be systematically suggested by default. The locations of the type dock are not suggested in the selection if the return transaction does not specify receipts to dock.

In some cases, you may intentionally choose not to enter the location type and/or location because the goods to be returned will be distributed across different storage locations. You will then enter the distribution in the Stock detail window. If a “$” symbol is displayed in these fields after entry, it means that different location types and/or locations have been assigned and that a stock line has subdetails.

From the Location type field, click the Actions icon to:

• select a location type,
• access by tunnel the location types table if the user's authorizations allow it.

From the Location field, click the Actions icon to:

• select a location,
• jump to the location table if your user authorizations allow it,
• jump to the Location occupation inquiry if your user authorizations allow it.
• jump to the Dedicated locations inquiry for the product being entered if your user authorizations allow it.

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

• Supplier lot (field BPSLOT)

The supplier lot number can be entered for information purposes in the receipt transactions, and displayed in the stock issue transactions.

It is recorded in the stock file and corresponds to the internal lot number. This ensures that the origin of goods can be tracked.

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

• Movement description (field MVTDES)

Enter a free description that will be registered in all the stock transactions associated with the delivery line.
This description is also accessible from the stock issue detail window. If it has been modified by this function, it will be automatically recovered and registered on the shipment line in this field.

• Delivery no. (field DETSDHNUM)

This field is always loaded. If your user authorizations allow it, you can access the source delivery using the Actions icon.
This field is managed based on the Subcontract material return transaction setup.

• field CCE1

Depending on the setup, the analytical dimensions can be modified as they are initialized in compliance with the default dimensions setup.

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

• Registration (field LICPLATER)

License plate of the vehicle carrying goods.

• Trailer license plate (field TRLLICPLAT)

Enter the trailer license plate.

• Departure date (field DPEDATR)

• Departure time (field ETDR)

Delivery departure time.

• Arrival date (field ARVDATR)

Displays the arrival date for this delivery or return.

• Arrival time (field ETAR)

Delivery arrival time.

• Project (field PJT)

The management of the project code depends on the value of the CTLOPPCOD - Mandatory project control parameter (TC chapter, MIS group).

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

When the entry is controlled, depending on the context, you can choose a project or one of the entities to be allocated to the project (budget lot, task) using the allocation code:

You can only select one active posting code, depending on the status of the relevant entity. If it becomes inactive after the creation of the document, the control is performed and blocks the modification of the document.

In creation mode, the project code is systematically transferred to the document lines where it can only be modified if the multi-project management of documents is authorized (the PJTSNGDOC - One project per document parameter is set to No).

During the transformation of a document, the project code of the header is initialized by the first selected document (if the project code of the original document header has become inactive, the one of the destination document is not loaded).

• Yes: The project code is applied to all lines, excluding lines linked to a billing plan and lines with an incompatible milestone.
• No: the project code is not transferred to the lines.
• Same value: The project code is only transferred to the lines associated to the previous project code.

Sales documents: Quotes, orders, deliveries and invoices:

• For a quote: It is not ordered.
• For an order: It is not delivered (for standard orders) or not invoiced (for direct invoicing) and no line is closed.
• For a delivery: it is not validated and the delivery is direct.
• For an invoice or a credit memo: it is not validated and the invoice/credit memo is not direct.

The grouping of two or more documents with different project codes in the header is only authorized if the parameter PJTSNGDOC - One project per document is set to No. In this case, two orders with a distinct project code can be grouped on the same delivery note.

• If multi-project management of documents is enabled (PJTSNGDOC - One project per document parameter set to No), the delivery can include direct delivery lines and product lines linked to tasks. The header project code is used as the default value on direct delivery lines only. Product lines linked to tasks keep their project code, which cannot be modified. If the header project code is modified, the application of this code to the lines is suggested, as described above. This only applies to direct delivery lines.
• If multi-project management of documents prohibited (PJTSNGDOC - One project per document parameter set to Yes), the delivery cannot include both direct delivery lines and product lines linked to tasks.
• When the delivery is for direct delivery lines, you cannot enter a project code in the header that is already used on tasks.
• When the delivery is for product lines linked to tasks, you can only enter product lines linked to the same task. The header project code can then be used to filter tasks in the selection panel.

Specific case of free items generated by the price list search after updating the header project code: The free item displays the project code of its source product but only if this code is not used on a task.

• Dimension type (field DIE)

This grid is used to enter or display the dimension types based on the loan return entry transaction setup.

• Description (field NAMDIE)

This field repeats the title of the dimension type.

• Dimension (field CCE)

Depending on the setup, the analytical dimensions can be modified as they are initialized in compliance with the default dimensions setup.

• Global document (field GLBDOCR)

A global document refers to a shipment where the final delivery details (customer sites and quantities) are not known at departure time.

Example: A company sells baked goods and delivers them to several customers' sites. The truck leaves with 1,000 units of baked goods, but it is not know how many will be delivered to each customer site. When all the deliveries are complete, the detail / normal shipping note is created and linked to the global document.

If the current record ponds to the example above, you must select the Global document check box for the record to be associated with the final transport and to disable the fields relating to the global transportation.

Otherwise, do not select Global document to link the record to a global document.

• Global document type (field GLBDOCTYPR)

If the current record is linked to a global document, you need to enter the global document type (origin) and the global document number to associate these two documents and to export this association properly in SAF-T.

• Global document no. (field GLBDOCNUMR)

• Global document date (field GLBDOCDATR)

This field displays the date for Global document.

• Manual document (field MANDOCR)

If the web service is down, the transportation note must be communicated using a paper document including the paper document number and the internal system number. This communication must be done directly in the AT portal.

This field must contain a slash character (/) separating the sequential number specific to the series (on the left) and the sequential number itself (on the right). This is needed for all transportation notes for manual documents.

• AT code (field ATDTCODR)

This field displays the AT code for the Transportation note returned by the tax authority.

• Incoterm (field XEECICT)

• Incoterm town (field XICTCTY)

• Freight agent (field XFFWNUM)

• Forwarding agent address (field XFFWADD)

• EU VAT no. (field XEECNUM)

• Intrastat transp. location (field XEECLOC)

• Intrastat transport mode (field XEECTRN)

• Transaction nature (field XEECNAT)

• Statistical rule (field XEECSCH)

• Transaction nature (field XEECNATR)

• Statistical rule (field XEECSCHR)

• Departure date (field DPEDAT)

• Departure time (field ETD)

Displays the arrival date for this delivery or return.

• Arrival date (field ARVDAT)

Delivery departure time.

• Arrival time (field ETA)

Delivery arrival time.

• Registration (field LICPLATE)

License plate of the vehicle carrying goods.

• Trailer license plate (field TRLLICPLAT)

Enter the trailer license plate.

• Manual document (field MANDOC)

If the web service is down, the transportation note must be communicated using a paper document including the paper document number and the internal system number. This communication must be done directly in the AT portal.

This field must contain a slash character (/) separating the sequential number specific to the series (on the left) and the sequential number itself (on the right). This is needed for all transportation notes for manual documents.

• AT code (field ATDTCOD)

This field displays the AT code for the Transportation note returned by the tax authority.