Sub-cont Material Returns

• Receiving site (field 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.

• Type (field 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.

• Return no. (field 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.

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

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

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

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

• field WSRHCAT

The category cannot be modified; it is determined by the chosen Return 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)

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 function Put-away plan.

• Intersite (field 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.

• Intercompany (field BETCPY)

• Product (field ITMREF)

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

• Description (field 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.

• Standard description (field 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.

• SAL (field 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.

• Delivered qty. (field 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.

• Net price (field NETPRI)

Net price of the line. Non modifiable information.

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

• Currency (field CUR)

• SAL-STK conv. (field 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.

• Return reason (field RTNREN)

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

• STK (field 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.

• Project (field 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).
It can only be modified if one of the two following conditions are met:

• the PJTSNGDOC - one project per document parameter (chapter TC - group MIS) 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:

• The project allocation code is composed of:
  - for projects, the project counter number,
  - the concatenated project sequence number with the budget batch code, in the case of a project budget batch,
  - the concatenated project sequence number with the number of tasks, in the case of a project task.
  
• 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 selection, there are two possibilities:

• The Selection contextual menus (CRM projects, Projects, Budget batch or projects only linked to the BP) are used to select a project in a selection list.
• The CRM projects and Projects contextual menus are used to directly access the chosen management function and then carry out a selection or create a project.

When the project code of the document header is modified, this project code is automatically transferred to the lines, except when the multi-project management is authorized. In this case, a dialog box would open and suggest 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.
• Same value: the project code is only transferred to the lines associated to the previous project code.

Sales documents: quotes, orders, deliveries and invoices:
- In case lines were impacted, a dialog box opens and suggests to recalculate the prices and discounts. The answer Yes causes a price list search, based on the new project code, for all the lines of the document.
- In the event the project code were modified in the line, this same price list searching system is applied to the line.
Depending on the processed document, the recalculation is performed only if the following conditions are met:

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

• Update stock (field 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.

• Warehouse (field WRH)

The presence of this field depends on the activity code WRH.
It is initialized with the warehouse present in the document header.

• It can be modified if it is defined as enterable in the entry transaction.
  If it is entered, the warehouse will be automatically entered on the stock detail lines and can not 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 multi-warehouses on the lines, it is necessary, at entry transaction level, to set up the warehouse-line so that it can be entered. The split of a same line on several warehouses is carried out in the window Quantity detailed entry available by right-click.
  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.

• Status (field 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:

• A: Accepted
• Q: Pending Quality Control
• R: Rejected
  A sub-status of two alphanumerical characters is used to further define the status.
  Example:
• RD: Rejected products to be destroyed
• SR: Supplier return

The statuses and sub-statuses authorized in a stock transaction can depend on various factors:
- the "subject to control" code of the product,
- the "subject to control" code of the received order,
- a list of configurable values associated with the stock transaction.

The stock totals for the product are updated according to the status entered in the movements:
- Physical stock: total of stocks with status "A"
- Stock under quality control: total of stocks with status "Q"
- Rejected stock: total of stocks with status "R"

• Loc. type (field 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.

• Location (field 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.

• Lot (field 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).

• No. of sublots (field NBSLO)

Number of sub-lots concerned by the stock transaction.

• Sublot (field 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).

• 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 cannot be entered; it is displayed for information purposes.

• Serial no. (field 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. 

• Ending serial number (field SERNUMF)

• Identifier 1 (field PALNUM)

Use this field to enter additional information, if necessary.

• Identifier 2 (field CTRNUM)

• Movement description (field 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.

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

• Supplier return no. (field 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.

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

• Registration (field LICPLATER)

• Trailer license plate (field TRLLICPLAT)

• Departure date (field DPEDATR)

• Departure time (field ETDR)

• Arrival date (field ARVDATR)

• Arrival time (field ETAR)

• Project (field PJT)

• Dimension type (field 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.

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

• Global document type (field GLBDOCTYPR)

• Global document no. (field GLBDOCNUMR)

• Global document date (field GLBDOCDATR)

• Manual document (field MANDOCR)

• AT code (field ATDTCODR)

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