Devol. materiais sub-contratação

• Estabelecimento receção (campo STOFCY)

The site in which the return is carried out. It is initialized by default with the user usual storage site.
It is used to filter returns (the filter is carried out on the delivery shipment site). A control is performed on the chosen site to check that it is a storage site.
Once a return line has been selected, it is no longer possible to modify this information.

• Tipo (campo SRHTYP)

Only one type of return of the 'For sub-contract' 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.

• campo WSRHCAT

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

• Nr. devol. (campo SRHNUM)

Return number used to identify the latter in a unique way.
This number is automatically generated or entered upon each return creation depending on the counter setup defined for sub-contract material returns.

• Data devol. (campo 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.

• Assinado (campo SRHCFMFLG)

• Cliente exped. (campo BPCORD)

The delivered customer code is mandatory. It remains modifiable provided no return line has been entered.

• Endereço (campo 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.

• Armazém (campo 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.

• Localização Cais (campo 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.

• Inter-estab. (campo BETFCY)

This non modifiable information specifies whether the return is of type inter-site and/or inter-company. The display of thes fields depends on the Sub-contract material return entry transaction setup.

• Inter-sociedade (campo BETCPY)

• Artigo (campo ITMREF)

The product code cannot be entered; it is initialized from the selected delivery or return line.

• Designação (campo ITMDES)

This is the product description translated into the business partner language. This description comes from the description entered on the material delivery for sub-contract.

This field is managed depending on the Sub-contract material return entry transaction setup.

• Designação standard (campo ITMDES1)

This is the description entered on the delivery of material for sub-contracting.

This field is managed depending on the Sub-contract material return entry transaction setup.

• UV (campo SAU)

Unit in which the product is being sold. It is the order and delivery entry unit, to which the product sales price is associated. This field comes from the product screen and is not entered.

• Qtd expedida efetiva (campo DLVQTY)

The delivered quantity, expressed in the return unit, cannot be entered.
It is initialized by the total quantity of the delivery line minus the sum of the quantities already returned.
This field is managed depending on the Sub-contract material return transaction setup.

• Prç. liq. (campo NETPRI)

Net price of the line. Non modifiable information.

• Qtd.devol. (campo 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.

• Divisa (campo CUR)

• Coef. UV-US (campo SAUSTUCOE)

Coefficient used to calculate the quantity in stock unit, from a quantity entered in sales unit. Qty in STK = Qty in SAL * coeff . This coefficient cannot be modified.

• Motivo devol. (campo RTNREN)

The reason of the return cannot be entered; it is loaded from the supplier return.

• US (campo STU)

The product storage units used to carry out the stock movement are, depending on the situation, either those of the delivery, or those of the return on receipt. They cannot be modified.

• Projecto (campo DPJT)

The project code in document line is initialized by the one entered in the header or, in the case of a document transformation, by the one of the selected document lines (in picking or in mass processing, if the project code on a document line is inactive, the line cannot be selected).

• The PJTSNGDOC - one project per document parameter (TC chapter, MIS group) is set to No,
• The entry of this field is authorized by the entry transaction being used.

In modification mode, the project code management depends on the value of the CTLOPPCOD - Mandatory project control 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.

When the entry is controlled, depending on the context, a project or one of its entities can be picked (a budget batch or task), using its posting code:

• 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: The item line is not ordered and is not free.
• For an order: The item line is not closed, not delivered, not invoiced nor free.
• For a delivery: The item line is direct and not free.
• For an invoice or a direct credit: the document is not validated, the item line is direct and not free. For direct credits, the quantity is different from 0.

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

• Act.stock (campo RTNSTOUPD)

This flag is selected by default. It is used to specify if the stock information update has to be performed.

• If the transaction setup allows it, and if there is only one stock detail line, it is possible to enter on the return line, all the information required for the stock movement: the status, the location type and the location if the product is managed on location (if not, the information linked to the management by lot, and the movement description). At return line end, a window for the Stock detail entry may open automatically if part of this information has not been entered.
• In the following cases, some of the information related to the lot have to be entered in the Stock detail window, which opens automatically:
  - several stock detail lines are generated,
  - several stock detail lines exist and the return line quantity is modified: it is then necessary to select the line(s) impacted by this modification,
  - only one stock detail line exists and the return line quantity is increased: it is then necessary to specify whether the additional quantity concerns the same detail line or another one.

If the stock update is not demanded, all the stock information from the delivery is erased, the stock movement is not created and the stocks are not updated. This can happen again when, for instance, the returned material is damaged and it is not to be entered to stock.

• Armazém (campo 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.

• Conteúdo (campo TCTRNUM)

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

Select the container you want to use.

• Número conteúdo (campo 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 (campo STA)

The product quality status can on ly be entered if the stock update is demanded.
It is initialized with the delivery status if the latter is authorized by the Stock management rules, for field Delivery return for sub-contract. If this status is not authorized, it is the field default status that is used.
However, it is not mandatory to enter it on the return line; the returned material may be of different quality and a split may in the end be necessary. If it is not entered; the Stock detail window will automatically open at line end for the status to be specified or the split carried out. When different statuses have been assigned and when there exist a sub-detail for stock lines, the $ symbol appears in this field at entry end on the document line.
When the product status is To check (status Q*), an analysis request can be generated upon receipt to stock of a product if the Management rule for field Delivery return for sub-contract has been set up so.

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

• Tipo localiz. (campo LOCTYP)

The location types are used to codify the warehouse locations according to their storage characteristics: dimensions, authorized statuses, technical constraints etc.
They are associated with the products by site (or the products by warehouse when warehouses are managed), thus making it possible to geographically group the products having similar characteristics. 
The location type of the product suggested by default is the one recorded during the delivery.

• Localização (campo LOC)

The location can be entered only if the stock update is demanded.
It is automatically initialized based on the location type if it is specified, if it is not the first free location specified in the product-site record is proposed. The location type and the location defined in this record 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). In some location types, the allocation will also depend on their availability or capacity (replenishment management).
If a location of type Quay has been entered in the return header, it is this location that systematically is proposed by default. Locations of type Quay are proposed for selection only if the entry transaction setup allows Receipts on quay.

A location type and / or a location are not necessarily to be entered on the return line; it can happen that the returned material is distributed over several storage locations. If they are not entered, the Stock detail window opens automatically at line end for the distribution to be entered. When several location types and / or locations have been allocated and when there is a sub-detail for stock lines, the $ symbol appears in these fields at entry end on the document line.

• Lote (campo LOT)

Lot concerned by the input movement.
The $ symbol is displayed when the return concerns a delivery or a return on receipt with references to several lot numbers. In case the return only concerns some of the lots, the choice of the lots is carried out via window Stock detail (by deleting the useless lines).

• Nr. S/lote (campo NBSLO)

Number of sub-lots concerned by the stock transaction.

• S/lot (campo SLO)

Sub-lot concerned by the stock movement.
The $ symbol is displayed when the return concerns a delivery or a return on receipt with references to several sub-lot numbers. In case the return only concerns some of the sub-lots, the choice of the sub-lots is carried out via window Stock detail (by deleting the useless lines).

• S/lote fim (campo SLOF)

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

• Lote fornec. (campo BPSLOT)

The supplier lot number cannot be entered; it is displayed for information purposes.

• Série inicio (campo SERNUM)

These fields, which cannot be entered, respectively display the first and last serial numbers, when these are consecutive.
When they are not, the $ symbol is displayed in both fields.
If the return only concerns some of the serial numbers, the choice of returned numbers is carried out via window Stock detail.

• Série fim (campo SERNUMF)

• Identific. 1 (campo PALNUM)

Use this field to enter additional information, if necessary.

• Identific. 2 (campo CTRNUM)

• Designação do movimento (campo MVTDES)

Free text that will be written in the stock journal for each movement of the return line. This information can also be modified in the Stock detail window.

• Nº Expedição (campo 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.

• Nr. dev. forn. (campo PNHNUM)

This field is loaded only in the case of a return on a supplier return. If your user authorizations allow it, you can access the source return using the Actions icon.
This field is managed based on the Subcontract material return transaction setup.

• campo CCE1

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

• Familia de movimentos (campo TRSFAM)

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.

This statistical information will be recorded in the stock journal upon record of the return to stock.
The management of this field depends on the setup of the Sub-contract material return transaction.

• Matrícula (campo LICPLATER)

License plate of the vehicle carrying goods.

• Matricula reboque (campo TRLLICPLAT)

Enter the trailer license plate.

• Data partida (campo DPEDATR)

• Hora saída (campo ETDR)

Delivery departure time.

• Data chegada (campo ARVDATR)

Displays the arrival date for this delivery or return.

• Hora chegada (campo ETAR)

Delivery arrival time.

• Projecto (campo 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.

• Eixo (campo DIE)

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

• Descr. (campo NAMDIE)

This field repeats the title of the dimension type.

• Secção (campo CCE)

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

• Documento Global (campo 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.

• Tipo documento global (campo 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.

• Nº documento global (campo GLBDOCNUMR)

• Data documento global (campo GLBDOCDATR)

This field displays the date for Global document.

• Documento manual (campo 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.

• Código AT (campo ATDTCODR)

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

• Incoterm (campo XEECICT)

• Local Incoterm (campo XICTCTY)

• Despachante (campo XFFWNUM)

• Endereço despachante (campo XFFWADD)

• N° IVA intracomunitário (campo XEECNUM)

• Local transporte DEB (campo XEECLOC)

• Modo transporte DEB (campo XEECTRN)

• Natureza da transação (campo XEECNAT)

• Regime estatístico (campo XEECSCH)

• Natureza da transação (campo XEECNATR)

• Regime estatístico (campo XEECSCHR)