Customer Returns
Use this function to record customer returns following a delivery or supplier returns for inter-site or inter-company transfers.
When the return is completed, the stocks are moved if necessary. You can print a return note or you can record a credit memo.
This function is directly linked with the Non-conformance management functionality. If the 'return' warrants notification to your Quality management team of a potential non-conformity you can raise a non-conformance incidence directly from this function. For example, if the product does not comply with specifications or the customer has returned the goods because they are defective.
Timely notification of a non-conformity can be critical for compliance management.
Prerequisite
Refer to documentation Implementation
Screen management
This function is customized to the needs of your organization and your processes. The transaction you select determines the way in which you enter information, and information is displayed and printed.
If only one transaction has been set up you are not offered a choice, the default entry screen is displayed.
The choice can also be restricted by using access codes.
Header
Receiving site (field STOFCY) |
This is the site to which the material is returned. A product can be returned to another site in the company to the one which carried out the shipment. A control is performed on the chosen site so as to check that it is a Stock type site. When a return is recorded, it is longer possible to modify this information. Based on this information, it is possible to select a site in the list of authorized sites which have a storage function. |
Type (field SRHTYP) |
Only one return type of the 'Normal' 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 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. Notes:
|
Return date (field ENTRTNDAT) |
This date is initialized to the current date. It corresponds to the actual date of the product return to the company. It will be used as a receipt to stock date for the returned product if the stocks are updated. |
Signed (field SRHCFMFLG) |
Ship-to (field BPCORD) |
A return is relative to:
They must be specified in the return header. A customer can only be selected if he is active. Based on this information, it is possible to:
|
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.
|
Entry screen
Return lines can be initialized automatically by picking from the selection panel. For the same return, you can thus select:
- one or several standard or nonbillable deliveries,
- specific standard or nonbillable delivery lines.
Each line is initialized for all of the delivery, minus any returns already carried out on this delivery.
For the management of inter-company flows, you can also generate the return lines from the selection of:
- supplier returns,
- supplier return lines.
Entry operation for a return creation
When you create a return line by selecting a delivery line or a supplier return line and several stock detail lines are generated, the stock information can only be modified by using the Stock detail window. The same is true for the modification of a line in a direct return (provided the return is not created).
Only the following information remains accessible: Unit, Quantity, Coefficient, Order price (only for the direct returns) and the Movement description.
For a direct return, when a single stock detail line exists, the information remains modifiable on the return line for a direct return.
For a return with a delivery or a supplier return as origin, only the following information can be modified: Status, the Location type, the Location and the Movement description.
If you modify the quantity on the return line and several lines exist in the stock detail, then the detail window automatically opens: it allows you to chose the line(s) impacted by this modification.
If you increase the quantity on the return line and only one stock detail line exists, the detail window automatically opens: it allows you to specify that the additional quantity concerns the same detail line or another detail line.
If you decrease the quantity in the return line and only one detail line exists, the stock window does not open.
Return coming from a delivery or an inter-site supplier return:
In the case of a return coming from a delivery or an inter-site supplier return, most of the information will be automatically initialized from the stock information in the original document line, other information must be entered manually or will be initialized as a function of the setup associated with a receipt movement of the Customer return type.
- Status: It will be initialized with the status of the delivery if the status is authorized by the management rule assigned to the movement type Delivery return (see the authorized Statuses and Sub-statuses). If the delivery status is not authorized for the management rule defined in the return, then the default status for the management rule is used.
- Location type and Location: the operation is identical to the direct return operation.
- Internal lot: this information in not accessible in this context on the return line. If the return concerns a delivery (or an inter-site supplier return) referencing only one lot, the latter will be displayed on the line. If the original document references several lot numbers, this is indicated by the presence of the $ symbol in the lot field. If the delivery is multi-lots and the return only concerns part of the delivery, the choice of the lot will be made via the stock detail screen (by deleting the lines that are not required). Same remarks as those concerning the management of sub-lot numbers.
- Supplier lot: this information is not accessible in this context and this is irrespective of the management rule associated with the product category. The lot proposed is the one coming from the original delivery.
- Serial number: this information is not accessible in this context in the return line. If the serial numbers in the delivery line or the supplier return are consecutive they will be displayed on the return line. If not, the '$' symbol is displayed in the two fields to indicate that the numbers displayed are not consecutive. If the original document contains several serial numbers and the return only concerns some of these numbers, you must access the stock detail window to choose the required numbers. Only the serial number from the original delivery lines or the original supplier return can be chosen. The serial number selection window only suggests the serial numbers from the original document line.
Return on deliveries with shortages
A return for a delivery line containing only missing items is not allowed. A blocking message is displayed. You must have entered the stock information beforehand in the original delivery.
If the return concerns a delivery line containing shortages and identified stock lines, only the quantities corresponding to the identified stock lines are proposed on the return lines. It is impossible to modify the return quantity beyond the quantities identified during the original issue.
If the return concerns a delivery with packaging that is not decimalized, the unit proposed will then be the stock unit.
Return of non-billable deliveries of product lines associated with tasks attached to a project.
- If the task is not closed, the Delivered quantity and Delivery status are updated on the product line at the task level. If you want to update the stock with the returned quantity, select the Update stock check box . However, this quantity is not reallocated on the product line associated with the task. The remaining quantity to be delivered is updated at the Enterprise planning level on the WIP order associated with the product line of the task.
- If the task is closed, a warning message will appear when you select the delivery line. The project code is reseted on the line. The task on the project is not updated and is therefore not reopened.
If multi-project document management of documents is prohibited (the PJTSNGDOC - One project per document parameter is set to Yes), all selected lines must be on the same project code. The project code of the first selected line is used to filter the pick list of non-billable deliveries.
Return detail
Bill-to customer (field BPCINV) |
This field is initialized by the bill-to customer for the ship-to customer. It can be modified because in certain cases the bill-to customer can be different from the usual bill-to customer. It can also be used to filter deliveries that can be subject to a return. It is used to:
|
Expected return date (field EXTRTNDAT) |
This date is used to initialize the return date on each line. |
Block number 2
Intersite (field BETFCY) |
This information which cannot be modified specifies if the return type is 'inter-site'. A return is automatically considered as being of the 'inter-site' type if the site linked to the delivery address legally belongs to the same legal company as the return site company. It is also mandatory that the site type be 'Stock'. If it is an inter-company return, this indicator will also be activated. |
Intercompany (field BETCPY) |
This information which cannot be modified specifies if the return type is 'inter-company'. When the return concerns an 'inter-company' customer, a credit memo of the invoice can be created. |
Stock
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. |
Grid
Product (field ITMREF) | |||||||||||||
This field is only accessible when the return entry makes no reference to any delivery or to no supplier return. It is used to:
The entry of the product is used to initialize the ‘Description’ and ‘Sales unit’ fields that are modifiable. The sales unit can be modified on the condition of being chosen from the list proposed that contains the sales and packaging units from the product record and the units from the product-customer record. |
|||||||||||||
Description (field ITMDES) | |||||||||||||
This is the product description translated into the customer language. If the translation does not exist in the customer language, the un-translated product description is used. This description is also transferred from one document to another. When the return comes from a delivery, the translated description is inherited from the document line concerned. When the return comes from a direct supplier return (inter-site), the translated description is inherited from the product record. If the supplier has for origin a delivery, the translated description of the delivery is used. It is possible to access the product record by tunnel from this field. |
|||||||||||||
Standard description (field ITMDES1) | |||||||||||||
The standard description for the product is initialized by the product description if it is a direct return (making no reference to any shipment). If it is a return linked to a shipment the product description will be the product description entered in the delivery. When the return comes from a direct supplier return (inter-site), the standard description will be inherited from the supplier return. If the supplier has as origin a delivery, the standard description from the delivery will be reused. The product record can be accessed by ‘Jump to’ from this field. |
|||||||||||||
SAL (field SAU) | |||||||||||||
This is the unit in which the return is expressed. This information remains modifiable provided there have been no stock movements for the return line or provided the return line has not been the object of a credit memo. During a direct return, the sales unit is initialized by the sales unit defined in the Product-customer record, if it exists. Otherwise, it is initialized with the sale unit of the product. Entry of another unit is possible in a selection window. The units proposed are the sales units for the product previously mentioned, the packing units for the product and the packing units defined in the Product-customer record. If the sales unit is modified, the Expected return quantity, the Return quantity and the conversion coefficient between the return unit and the stock unit are automatically recalculated in the new unit. From this field it is possible to use the contextual button to:
|
|||||||||||||
Expected ret. qty. (field EXTQTY) | |||||||||||||
The 'Expected return quantity' field , expressed in the unit for the return, is initialized by the maximum quantity that can be returned with respect to the original delivery or the supplier return in the case of an inter-site or inter-company supplier return. When the customer return makes reference to a delivery or a supplier return, it is not be possible to enter a quantity that is greater than the shipped (or returned) quantity less the quantity already returned.
If it is a direct return line (not associated with a delivery), this field is initialized to zero. This quantity is no longer modifiable if the return line has been subject to a stock receipt. |
|||||||||||||
Returned qty. (field QTY) | |||||||||||||
The Return quantity field is expressed in the return unit. By default, the returned quantity is equal to the Expected return quantity. It can still be modified. It corresponds to the actual quantity returned for the selected delivery, or the chosen supplier return. A control is applied against the Expected return quantity. It will not be possible to return a quantity that is greater than the expected quantity. Provided that the Expected return quantity is not null, it is possible to enter a null Return quantity. This would mean recording an expected customer return event. No stock receipt will be possible as long as the returned quantity has not been entered. |
|||||||||||||
SAL-STK conv. (field SAUSTUCOE) | |||||||||||||
The coefficient between the return unit and the stock unit is only accessible if the return unit has been set up as being modifiable in the product record. If this coefficient is modifiable, it will remain accessible as long as no stock movement has taken place for the return line or provided the return line has not been subject to a credit memo. If the coefficient is modified, then the unitary net price for the return line will be re-calculated. The operation is the same if the coefficient is modified using the stock detail window if the return sales unit is a packaging unit. Management of the coefficients and the return units:When the return has a delivery as origin, the units used to carry out the default stock movement are those of the delivery. Thus if a delivery had as sales unit a Carton, but the associated stock movement in made by individual unit, the unit used by default to carry out the receipt to stock will be the unit. It is possible to modify the conversion coefficient between the return unit and the stock unit. If this change occurs not on the return line, but in the inventory detail window, the change in the coefficient is reflected on the return line, except in the following case: in the inventory detail window, other units are used or lines with different coefficients are entered and the quantity entered does not match the quantity of the return line. In this case the return line unit is replaced by the stock unit to ensure a conversion with the units used to carry out the receipt to stock. |
|||||||||||||
STK (field STU) | |||||||||||||
This is the stock unit for the product. This information cannot be accessed. |
|||||||||||||
Actual delivered qty. (field DLVQTY) | |||||||||||||
This is the delivered quantity on the original packing slip minus any quantity already returned. For supplier returns, the delivered quantity is also the original delivery quantity minus the quantity already returned. If it is a direct return, the delivery quantity is blank. The shipped quantity is decreased by the returned quantity on the line when the return is saved. It is expressed in the return unit (SAL). This field is not editable. |
|||||||||||||
Net price (field NETPRI) | |||||||||||||
The information indicated in this field comes from the delivery and displays the net unitary price of the delivery line for a return unit. For a direct return the price is null. If it is a direct supplier return, the net price will be equal to the net price entered in the supplier return. |
|||||||||||||
Curr. (field CUR) | |||||||||||||
The information specified in this field comes from the delivery showing the currency of the net price in the delivery line. It is in fact possible to carry out a return for delivery lines that have different currencies. If it is a direct return, the net price being blank, the currency does not have any significance and is not entered. When the return has as its origin a direct supplier return, the currency of the return line is the currency of the supplier return. |
|||||||||||||
Return reason (field RTNREN) | |||||||||||||
This field is used to define the customer return reason using the different reasons defined in miscellaneous table number 7. |
|||||||||||||
Return date (field DETRTNDAT) | |||||||||||||
This date is initialized by the return date entered in the header. If this date is inferior to the current date, the current date will be proposed by default. The date specified in this field corresponds to the actual date of the product return to the company. It is used as a receipt to stock date for the returned product if the stocks are updated. |
|||||||||||||
Update order (field ORDUPD) | |||||||||||||
When the return is a delivery for an order that has not yet been invoiced, you can request to update the order. The order and the order line are updated to process a new delivery based on the returned quantity. The order is then pending delivery. Note: When a customer returns a sales kit, you cannot update the sales order. This ensures that quantities for the parent product and the associated components remain consistent. The parent product and the associated components are no longer linked in the returns, but they are still linked in the sales order. The re-activation is not possible for an intercompany return. The Intercompany check box is inactive. |
|||||||||||||
Project (field DPJT) | |||||||||||||
This field displays the project code of the task to which the selected non-billable delivery is associated, only when the task is not closed. If the task is closed, the project code is reseted. The task is not updated. If multi-project document management of documents is prohibited (the PJTSNGDOC - One project per document parameter is set to Yes), all selected lines must be on the same project code. The project code of the first selected line is used to filter the contents of the selection list. |
|||||||||||||
Update stock (field RTNSTOUPD) | |||||||||||||
This flag is always selected by default. When it is selected, and if the transaction allows it, you can enter the information required for the stock movement on the return line. Otherwise, you will not enter a stock receipt for these returned goods because the goods are damaged and you do not want to record a stock receipt; or because you are entering a provisional return and the stock receipt will only be recorded once the goods are actually received. Depending on the product configuration, the following stock characteristics need to be specified:
At the end of the receipt line, a window for the entry of the stock detail may open automatically if all the stock information has not been entered or initialized. This information must then be entered in this detail screen. In addition to the stock characteristics specific to the product, a certain number of rules affect stock receipts. For a customer return these rules may be described in a general manner. These rules can also be refined by Product category or by site-specific product Category. If necessary, a stock entry rule on return may also be defined by product Category for a transaction typology. Different cases can be considered based on whether it is a direct return, a return with a delivery line as origin or a return with a supplier return as origin in an inter-site case.
|
|||||||||||||
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.
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.
- 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. |
|||||||||||||
Loc. type (field LOCTYP) | |||||||||||||
Location types are used to codify warehouse locations according to storage characteristics such as their dimensions, authorized statuses and technical constraints. The location type is automatically loaded from the location type associated with:
In all cases, the location type can be modified if its entry is enabled at the level of the entry transaction. You may only enter a ‘dock’ type location if the entry transaction authorizes receipts on dock. When warehouses are managed, entry of a location type is only permitted if at least one location is linked to the entered type and warehouse. |
|||||||||||||
Status (field STA) | |||||||||||||
This field is initialized with the default status defined by the management rule assigned to the transaction type Delivery return. If no status has been specified in the rule, no value will be proposed. The status is not mandatory in the return line, but if it is not entered, the stock detail window will open automatically at the end of the line so that a status can be specified. In certain cases, the user may intentionally choose not to enter the status in the document line, because the goods that are returned are of a different quality and a split is necessary. It will then be necessary to enter this split of the statuses in the stock detail window. If a $ symbol appears in this field at the end of the entry of this field in the document line, it means that different statuses have been assigned and that a sub-detail on the stock lines exists. According to the management rule used for the transaction type Delivery return, it is possible to generate an analysis request during the receipt to stock of the goods if the goods have the status to be controlled (Q*). |
|||||||||||||
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). 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:
From the Location field, click the Actions icon to:
|
|||||||||||||
Lot (field LOT) | |||||||||||||
If the product is managed by lot, different cases are possible based on the lot management rule associated with the Shipment return transaction type and based on the product lot management rule. If a product is managed with mandatory or optional lots, the access to the lot field depends on one hand on the setup of the return transaction used and on the other hand on the management rule Delivery return defined in the product category or in the stock management rules. At the level, you can indeed specify whether the lot is not to be entered, free of entry, or if only new lots can be entered. In addition, it will be possible to allocate a default value to a lot. In this case, several choices are also offered. Never initialize the lot or initialize the lot with a document number (the initialization with the document number is not visible during the entry if the return number is automatically allocated at the creation, it is given a blank value). If you do not enter the lot number in the lot field, the document number is written in the lot field upon posting the note. The choice of initializing the internal lot with the supplier lot is not active in a delivery return context. When the entry is completed, if no lot number has been entered, several cases can arise:
Specific case of the products managed as optional lotThis product type allows the entry of a blank lot field. In this case, this must be indicated by entering the lot field and clicking Blank lot from the Actions menu. Then, when saving the document, the sequence numbers or the document number will not be used. This management method is thus incompatible with a management rule that does not allow the entry of an internal lot number. The grid given below summarizes the impact of the setup of the management rule for the movement type Shipment return with mandatory lot management during the entry of a direct return. For optional lots, click Blank lot from the Actions icon to indicate that you are recording a blank (empty) lot.
From this field, use the Actions icon to:
|
|||||||||||||
No. of sublots (field NBSLO) | |||||||||||||
This field contains the number of sub-lots concerned by the stock transaction. |
|||||||||||||
Sublot (field SLO) | |||||||||||||
If the product is managed by lot and sub-lot, it is mandatory upon return to specify the sub-lot number associated with the internal lot. This entry is not mandatory at the level of the return line because it can be necessary to distribute it on the stock detail lines or to have several sub-lots to enter. By default, the system proposes the sub-lot number 00001 if no sub-lot number has yet been assigned to a lot in the entry. If this is not the case, the next sub-lot number is suggested as an increment of the last sub-lot. In some cases, the next sublot is not displayed because the last sublot corresponds to a character chain that cannot be incremented (e.g. 'AAAAA'). At the level of the return line, it is possible to enter a number of sub-lots corresponding to the number of sales units. If a number superior to 'one' is entered, the system calculates automatically the sub-lots to be assigned based on the entered sub-lot number (validate the calculated distribution in the stock detail window which opens automatically in this context). The number of the end sub-lot is displayed. If a '$' symbol is to be found in the two sub-lot columns, it means that the stock detail for the Sub-lots entered is not consecutive. At the level of the detail line, it is possible to define as many sub-lots as there are stock units. If a single sub-lot is required, the end sub-lot number is identical to the starting sub-lot number. From this field, click New from the Actions icon to calculate the next sub-lot number by incrementing the last known sub-lot. |
|||||||||||||
Ending sublot (field SLOF) | |||||||||||||
This field indicates the last sub-lot on which the stock movement is applied. |
|||||||||||||
Supplier lot (field BPSLOT) | |||||||||||||
If the product is managed by lot and this is a new lot manually entered, it is possible upon return to assign the original supplier lot if it is known (no specific control is carried out on this information). When this is not the case, this information is not be accessible and it is initialized by the supplier lot associated with the internal lot if it exists (only a supplier lot can correspond to an internal lot). A selection window is used to choose a supplier lot among known ones (that have the object of a receipt). If several supplier lots are entered, data must not be entered in the return line but in the 'stock' detail window. |
|||||||||||||
Starting serial number (field SERNUM) | |||||||||||||
If the product is managed by serial numbers at the receipt/issue or only at issue, it is mandatory to enter, before saving the return, one or more serial numbers depending on the quantity returned (this entry is made in the stock detail window). A control is carried out to verify that the number entered is not already in stock (a serial number being considered as unitary and not divisible). Upon direct return, it is possible to enter a serial number not known by the system (this corresponds to an old serial number that was not referenced in Sage X3). An information message will report it. Upon saving the return, the serial number is automatically created. If several serial numbers are returned, the end number contains the last serial number, provided the numbers are consecutive. Otherwise, a '$' symbol will be displayed in the two fields to specify that the numbers returned are not consecutive. It is recommended to access the stock detail window in order to view all 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. |
|||||||||||||
Order price (field PRIORD) | |||||||||||||
This is the unitary amount by stock unit that can be used to value the stock (if the valuation method for a customer return is Order price). The order price is initialized as follows:
In both these cases, the order price cannot be modified. If it is a direct return, the order price is not initialized but it is modifiable. |
|||||||||||||
Movement description (field MVTDES) | |||||||||||||
This is a free text written in the stock journal for each return line movement. This field can also be modified in the stock detail window. |
|||||||||||||
Deduct from invoice (field RTNINVUPD) | |||||||||||||
This field is not editable.
|
|||||||||||||
Credit memo (field RTNCNOFLG) | |||||||||||||
This field does not require any specific process. You use it to specify if a credit memo must be carried out. A credit memo can be manually created in the invoice management function by selecting the return that should be subject to a credit memo. A return line which has been subjected to a credit memo can no longer be modified even if the stock update has not been carried out. This field cannot be accessed:
|
|||||||||||||
Credit memo no. (field SIHNUM) | |||||||||||||
This field indicates the credit memo number that has been created from this return line. |
|||||||||||||
Delivery no. (field DETSDHNUM) | |||||||||||||
This field corresponds to the delivery number at the origin of the return. The original delivery can be accessed by tunnel granted the user has authorization. |
|||||||||||||
Supplier return no. (field PNHNUM) | |||||||||||||
This is the number of the inter-site supplier return at the origin of the return. This return can be accessed by tunnel, granted the user has authorization. |
|||||||||||||
field CCE1 | |||||||||||||
Depending on the setup, the analytical dimensions can be modified as they are initialized in compliance with the default dimensions setup. |
Line text entry | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
This function is used to enter a free text on the return line to be printed on the return note. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Enter Detailed Quantities | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
This function is used to access the Stock detail window that makes it possible to specify the stock information that has not been entered on the return line or to proceed with the necessary splits (Returns with different statuses, on different locations...). This function is accessible for a return line only if the stock transactions have not been recorded yet. If the stock transactions have been recorded, it is necessary to use the Receipt Modification function described later in this document. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 / Document no. / Blank lot. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Lot complement | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
This function is only accessible on the return line for products managed by lot where the stock receipt has not yet taken place (it is always accessible using the stock detail windows in creation or modification mode).
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Change receipts | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use this function to modify the stock movements that have been carried out when saving a return. This function is very similar to the Entry of quantity details function available at the time of the entry of the stock transaction on the return line. This function is only available from a stable situation. This means that it is not possible to modify the receipt note (the action Save must be deactivated). On saving a modification, reversals will be carried out on the original transactions in the stock journal and new stock transactions will be carried out on the original transaction dates. A modification on a receipt will only be possible if the stock line linked to the credit memo still exists or if the quantity to be processed for this line is sufficient. Use this function to modify all the stock information entered and to delete return lines if necessary. Indeed, if all the stock information is deleted, the return line will be deleted. If it is the only return line, the return note itself will be deleted. A return line that has been taken into account by a credit memo cannot be deleted. For more information on this function refer to Change receipts. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Delivery | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
If you have the required authorizations, click this action to access the source of the delivery. This function is not available in the case of a direct return. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Credit Memo | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use this function to access the credit memo through the Jump to in the action menu while taking into account the return line depending on the user authorizations. This function is not available if no credit memo has been created. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Supplier return | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Use this function to access the source supplier return through the Jump to in the action menu depending on the user authorizations. This function is not available if the line origin is not an inter-site or inter-company supplier return. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Stock by site | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Click this action to access the Stock by site function. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sales journal traceability | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
This function is used to access the Traceability of purchase documents function. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
Ret line situation display | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Field descriptions
Block number 1
Grid Deliveries
Grid Credit memos
|
Create non-conformance |
Click Create non-conformance from the Actions icon to raise (or report) an incidence of non-conformance against this specific return line. Generally speaking, you should report an incidence of non-conformance if you have observed or been informed that a product does not comply with specifications. The reported non-conformance provides the details of the non-conformance; it becomes the source of the information to support investigations into the root cause, or failure. If a single Description field is displayed, your organization only requires you to provide minimal details. Leave the default Description or amend as appropriate, then click Create to create the non-conformance. If the Non-conformance function is displayed, you are authorized to raise a detailed non-conformance incident. This means that your NCSDOCCRE - Non-conformance creation mode user parameter (TC chapter, NCS group) is set to 'Full'. Leave the default values from this return displayed or type in or select different values as appropriate. In the Identification section. add your detailed observations on the specification deviations or failures or potential failures of the product. You are returned to this function when you close the non-conformance. |
Description (field TITLE) |
Leave the default description displayed or type in a short description of this incidence of non-conformance. The default description is one of the following:
This field is mandatory. |
Tab Controls
Authorizations
Expiration date (field EXYDAT) |
This is the date beyond which it is normally no longer possible to register returns. |
Authorized user (field AUZUSR) |
This field is used to limit the acceptance rights for a return requested by a user. This limitation depends on the assignment of the SAUZRET user parameter which determines whether users can modify a return for which they are not the authorized operator. By default the user code proposed is the code of the current user performing the entry. If no user is specified, all operators can modify the return. |
Stock data
Transaction group (field TRSFAM) |
This is statistical information that will be recorded in the stock journal at the moment of saving the return to stock. This transaction group comes from the miscellaneous table number 9. This information can be initialized by the value given in the corresponding transaction setup. |
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, the user can choose a project, or one of the entities that can be allocated to the project (a budget lot or a task) using its allocation code:
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).
Inter-company and inter-site specificities: for an inter-site supplier return, the project code is automatically set to the one of the purchase return. For an inter-company supplier return, the project code is not recovered from the purchase return and remains blank. |
Grid Analytical
Dimension type (field DIE) |
This grid is used to enter or display the dimension types based on the customer 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
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.
|
Other conditions
If a return has generated stock movements, it is not possible to delete the return by clicking Delete. You first need to delete the lines that have generated a stock movement: on the concerned return lines, click Receipt modifs from the Actions icon.
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.
Specific Buttons
Post |
Menu Bar
Header TextClick this action to enter a return header free text. This text will be printed on the return note. During the transformation of a document, this text is never propagated to the other documents. Footer textClick this action to enter a return footer free text. This text will be printed on the return note. During the transformation of a document, this text is never propagated to the other documents. |
Delivery addressClick this action to access the customer delivery address and modify it if necessary. |
Picking criteriaClick this action to enter criteria that will be used to filter the pick lists. Customs informationTechnical Block number 1
Intrastat information
Physical flow
Adjustment flow
This window contains customs information and the information necessary to the creation of the Intrastat. On creation, they stem from the delivery or are initialized from those entered in the Ship-to section of the Customer record when it concerns a direct customer 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 and Transaction nature, subject to activity code DEB, too, come from the setup carried out at Movement rules and natures function level. This information can be modified up as long as the return note is not validated. Options / TransactionClick the Transaction action to view the format of this entry transaction. Journal trackingThis option gives access, via tunnel, to the inquiry function Entry traceability that makes it possible to visualize and browse into the hierarchy of original entries or coming from the document. |
Functions \ Installed base |
Click this action to access the installed base. When a product is managed in the base, the customer base will automatically be updated upon entry of the return with stock transaction (only for products with serial numbers). The status of the installed base record will be:
An archive identifying the previous (customer) status of the base record will be created. In certain cases, the automatic update cannot be made notably in the case of non-serialized products or because the installed base has never been created. This function therefore makes it possible (where the user authorizations enable it) to create an installed base record or to manually update the customer installed base. |
Any modification carried out on the return after a stock receipt will no longer update the installed base automatically. The installed base has to be updated manually. |
Functions \ Credit card processing |
Click this action to send the individual transport note. Use the Transport doc communication function to mass communicate transport notes. Additional info
Manual document
Communication
|
Non-conformance / Create
Click the Create action to raise (or report) an incidence of non-conformance against this return. Generally speaking, you should report an incidence of non-conformance if you have observed or been informed that a product does not comply with specifications. The reported non-conformance provides the details of the non-conformance; it becomes the source of the information to support investigations into the root cause, or failure. If a single Description field is displayed, your organization only requires you to provide minimal details. Leave the default Description or amend as appropriate, then click Create to create the non-conformance. If the Non-conformance function is displayed, you are authorized to raise a detailed non-conformance incident. This means that your NCSDOCCRE - Non-conformance creation mode user parameter (TC chapter, NCS group) is set to 'Full'. Leave the default values from this return displayed or type in or select different values as appropriate. In the Identification section. add your detailed observations on the specification deviations or failures or potential failures of the product. You are returned to this function when you close the non-conformance.
|
Non-conformance / List
Click the List action to view the list of non-conformance incidents that have been raised (reported) against this returns number.
The information displayed includes any amendments made to the original incident such as a change to the defective quantity (field NC quantity) and whether the return line is considered active and relevant to the incident (field Line status). The default description displays the applicable line number from this return if the non-conformance was created from the document line, for example, 'Customer return SRTPT0310002 1000'.
The list of non-conformances is displayed in ascending order with the most recent non-conformance on the first line. Click Non-conformance from the Actions icon to view or edit the con-conformance details.
|
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
Function not authorized
The user profile has no rights for this function, regardless of the site.
You do not have the rights for this return
You are not the authorized user for this return.
This document does not exist !
This message appears if the operator entered a non-existent return in a context of change.
No sequence number is assigned to this document
This message appears upon creating a return if no return number has been entered and the sequence number is assigned manually.
Problem when the sequence number counter is recovered
This message appears if it has not been possible to assign a delivery number.
$DELIVERY xxx or $PRETURN Modification on another workstation
This message appears if the delivery or the supplier return to which the return is associated is being modified on another workstation.
Problem on the table $DELIVERY or $PRETURN.
This message appears if there is a technical error on the table of the delivery headers or of the supplier returns.
Expected return quantity > Delivered quantity or Expected return quantity > Supplier return quantity.
This message appears when it is attempted to enter an expected return quantity superior to the delivered quantity (or the return quantity entered on the supplier return) that remains to be returned.
Return quantity > Delivered quantity
This message appears when it is attempted to enter a return quantity superior to the delivered quantity that remain to be returned or superior to the quantity of the supplier return.
Modification in process on another workstation
This message appears when trying to modify a return currently being modified on another workstation.
Processing not possible: This line has been subject to a credit memo
This message appears when an attempt is made to modify a return line that has been subjected to a credit memo.
The deletion of a validated line must be made using the modification window.
This message appears when an attempt is made to modify a line that has already been received in stock.
The original order has been updated. It will not be automatically updated by this entry! Continue?
This message appears when an attempt is made to modify or delete a line even though the delivered quantity of the order has already been reduced.
Indefinite period or processing prohibited at this date
This message is displayed if the return date is later than the current date or if the period status corresponding to this return date is different from 'direct'.
XXX: Product not managed in stock for the site: YYY
This message is displayed when a return is done for a site and that product is not defined on the site concerned.
The site is not in the same legal company
This message is displayed when it is attempted to return a delivery to a site that does not belong to the same company as the shipment site.
Delivery XXX: Product YYY Movements pending on this line !
This message is displayed during a picking of delivery to inform you pending movements still exist on this delivery line. Only the identified stock quantity will be suggested on the return line.
Delivery XXX: Product YYY The line movements are pending. Please adjust.
This message appears upon the picking of a delivery that contains only pending movements. The delivery must be adjusted before entering the return.
Installed base update: The installed base record is no longer defined in the installed base.
This message appears when a customer return is carried out on a serialized product that is tracked in the installed base for a customer (whose category is either Direct customer, Reseller, Wholesaler or End user) but that the installed base record does not exist. Either because it has been modified manually (allocated to another client ... ), deleted or because it is a direct return on a serial number that has not been previously identified.
Tables used
Refer to documentation Implementation