Sub-cont Material Returns
This function is used to record returns of non-consumed material having been subject to a delivery for sub-contracting or to a supplier return. This concerns for instance a return of damaged material or of material sent in excessive quantities as compared to the recorded sub-contracting order.
It is not possible to carry out directly a sub-contracting material return. This return is created:
- either it is a return on delivery from a sub-contracting delivery,
- or (in the case of inter-site management), from a supplier return recorded in the sub-contracting service provider site. It is then a return on supplier return.
Once the return is carried out, the stocks will be transferred and it will be possible to print a return note.
Prerequisite
Refer to documentation Implementation
Screen management
The presentation of the entry screen depends on the setup of the selected transaction.
If only one transaction has been set up, any selection will be suggested when entering the function; otherwise, a window opens and displays the list of transactions that might be used. (The choice can also be restricted by access codes.)
The creation of a sub-contracting material return is performed by picking:
- either a sub-contracting delivery line (in the left list Delivery Selection),
- either a supplier return (in the left list Return Selection).
The picking lists are available as soon as the ship-to customer is entered.
Header
The header is used to enter the ship-to customer and so to initialize the picking lists.
Receiving site (field STOFCY) |
The site in which the return is carried out. It is initialized by default with the user usual storage site. |
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. 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 used to identify the latter in a unique way. |
Return date (field RTNDAT) |
By default the return date is initialized to the current date. |
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.
|
Tab Lines
Each returned product line is loaded from one or several lines selected by picking in the lists of the Selection panel: Delivery selection and Return selection.
It is initialized with the entire delivery or return, except for the returns that have already been carried out for this delivery or return.
Depending on the setup carried out for the Stock information at entry transaction level, the data necessary to the stock movement can be entered on the return line when the stock update is required and when there is only one stock detail line. When this information has not been entered or when there are several stock detail lines, a Detail entry window automatically opens at return line end in order to complete it. See below Entry operation in return creation mode.
In addition to the stock characteristics specific to the product, a certain number of rules affect stock receipts. A general description can be entered for these rules in the Delivery return for sub-contract field, in the Stock management rules setup function. They can also be refined by Product category or site-specific product category. If necessary, a receipt to stock rule on sub-contract material return can also be defined by Product category for a movement typology (see the movement code definition on the Sub-contracting material return transaction setup).
Block number 1
Warehouse (field WRHE) |
The presence of this box is subject to the activity code WRH. |
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. |
Block number 2
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. |
Actual delivered qty. (field DLVQTY) |
The delivered quantity, expressed in the return unit, cannot be entered. |
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:
In modification mode, the project code management depends on the value of the CTLOPPCOD - Mandatory project control parameter.
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:
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. For non-deliverable Service products, you can select a project set with progress billing if the PJM activity code is active. Once the order has been recorded, you can view it in the Project management (GESPJM) function in the generated billing plan, linked to the selected 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:
Sales documents: Quotes, orders, deliveries and invoices: - If lines are impacted, a dialog box opens requesting a recalculation of prices and discounts. If you answer 'Yes', the price list search is run based on the new project code for all document lines. - If the project code is modified on the line, the same price list search process applies to the line. Depending on the processed document, the recalculation is performed only if the following conditions are met:
Deliveries linked to a task: The header project code displays the project code linked to the first selected task.
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. |
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 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 is subject to the activity code WRH.
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). 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.
- The License plate number is set to 'Mandatory' for the Product category.
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 product quality status can on ly be entered if the stock update is demanded. The stock status is used to define if a product is:
A sub-status of two alphanumerical characters is used to further define the status. Example:
The statuses and sub-statuses authorized in a stock transaction can depend on various factors:
The stock totals for a product are updated according to the status entered in the transactions:
|
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. |
Location (field LOC) |
The location can be entered only if the stock update is demanded. 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. |
No. of sublots (field NBSLO) |
Number of sub-lots concerned by the stock transaction. |
Sublot (field SLO) |
Sub-lot concerned by the stock movement. |
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. |
Starting serial number (field SERNUM) |
These fields, which cannot be entered, respectively display the first and last serial numbers, when these are consecutive. |
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. |
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. |
field CCE1 |
Depending on the setup, the analytical dimensions can be modified as they are initialized in compliance with the default dimensions setup. |
Enter Detailed Quantities |
Click this action to open a stock detail window and:
It can be accessed:
A detailed description of this window is available in the Receipts to stock detail documentation. |
Lot info |
This function is only available for the products managed by lot provided the stock receipt has not yet taken place. It is used to identify, when the lot has not been entered, how the lot is to be calculated during the stock receipt. The possible values are: Lot sequence number counter, Document no., Blank lot. |
LOT complement |
This function opens a window and is used to inquire lot characteristics (expiry date etc.). |
Change receipts |
This function opens a window used to modify the stock movements carried out upon record of a return and to delete return lines if necessary. If it is the only return line, the return note itself will be deleted. |
Delivery |
This function is used to access by tunnel to the original delivery based on the user authorizations. |
Stock by Site |
This function is used to access by tunnel to the Stock by site function, based on the user authorizations. |
Supplier return |
This function is used to access by tunnel to the supplier return based on the user authorizations. |
SC situation display |
Tab Controls
This tab is used for the management of analytical postings.
Stock data
Transaction group (field 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. |
Transport
Registration (field LICPLATER) |
License plate of the vehicle carrying goods. |
Trailer license plate (field TRLLICPLAT) |
Enter the trailer license plate. |
Departure date (field DPEDATR) |
Displays the departure date for this delivery or return.
|
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
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 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: The project allocation code is composed of:
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).In modification, the project code modified in the header is recovered automatically in lines, except when the multi-project management is authorized in which case a dialog box will open and requests whether to transfer this code to the document lines with respect to the following options:
Sales documents: Quotes, orders, deliveries and invoices: In case the project code is applied to the lines, a dialog box opens and suggests a recalculation of prices and discounts If you answer 'Yes', the price list search is run based on the new project code for all document lines. Depending on the processed document, the recalculation is performed only if the following conditions are met:
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. Deliveries linked to a task: The header project code displays the project code linked to the first selected task.
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. Intercompany specificities: For an intersite order, the project code automatically displays the project code of the purchase order. For an intercompany open order, the project code is not recovered from the purchase order and remains blank.
|
Grid Analytical
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
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
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.
|
Communication
AT code (field ATDTCODR) |
This field displays the AT code for the Transportation note returned by the tax authority. This field populates automatically when you communicate using the web service.
If you communicated the transport using a manual document, you need to enter the code from the tax authority manually.
|
Reports
By default, the following reports are associated with this function :
BONRETLIV : Customer return notes
SRETURNE : Sales return list
SRETURNL : Detail sales return list
This can be changed using a different setup.
Menu Bar
Picking criteria
This option opens a window that makes it possible to define a pre-loading filter for the picking left list, from: Customs informationTechnical Block number 1
Intrastat information
Physical flow
Adjustment flow
This window contains the customs information and the information necessary to the creation of the Customs Document File. In creation mode, they come from the sub-contract delivery concerned by the return.
The EU Information used only for the Intrastat is liable to the Intrastat activity code (DEB):
Information linked with the Physical flows: EU rule andTransaction nature, subject to activity code DEB, too, come from the setup carried out at Movement rules and natures function level. This information can still be modified. TransactionThis function is used to view the transaction setup used. |
Functions/Customer installed baseThis function is used to tunnel access the management function of the Installed based. |