Requests and returns history (HLR02701)

Options

Header	Select this option to view request header information.
Line	Select this option to view the request line.
Action	Select this option to view the actions that were executed by the request.

Function keys

Selection fields

Request

Business partner

Requests and returns history, Header (HLR02704)

Related topics

On this panel request header information is provided.

Request

Business partner

Your reference: Displays either your customer’s reference number or the name of the contact person at your business partner’s site.

Telephone number: Displays the telephone number defined for your customer in the Business partner file.

Telefax number: Displays the telefax number defined for your customer in the Business partner file.

Address: Displays the address code (to the left) and your customer’s delivery address (to the right).

User: Displays the ID of the employee that created the record.

Destination

Returns that are to be collected from the customer can be defined as a BPR. The parameters on a BPR that determines whether or not it is to be printed as a return are Customer return date and Goods return status.

This field is only mandatory if the BPR is for a goods return (the Goods return field is defined with status 4 = Goods are to be collected). Enter the destination code (from the Destination table) to indicate to the driver which destination to stop at along the route to pick up the return. This information will be printed on the route delivery list if:

The Customer return date field is equal to or less than the dispatch date on the outbound shipment
The Goods return field = status 4 (Goods are to be collected)
At least one line exists with Goods return = status 4 (Goods are to be collected)

Warehouse: Displays a code from the Warehouse table indicating where the returned goods are located.

Customer return date: Displays the date that the customer returned your goods.

Type of reference

Displays a code to identify the type of reference that is defined in the Your order field.

Permitted values:

Note: These values are defined in the Panel value control file table.

Goods return

This field is used to denote how returned goods are handled using this status code.

Permitted values:

Reference number: Displays the customer reference number of the order.

Your order: This field is used to track a request sales order or invoice. Displays your company’s reference number. Note: This field is not valid for Type of reference value 9 (manufacturing order).

Ext request code: Displays a code from the Request code table indicating the nature of the problem that was reported.

Status and type: Displays a code from the Request status code table indicating the status of the request. The status is always related to the request type. Note: Every time the status code changes, a transaction is recorded in the history for the request.

Resolution code: Displays a code from the Action table indicating the necessary steps to be taken to resolving this request.

Call back date/time: Displays the date and time the follow-up was promised to, or requested, by a business partner.

Hours Total: Displays the number of hours spent working on this request, (at current status) in the first input field. The second field indicates the number of hours that have been spent up until this time, on resolving and registering this request.

Claimed amount: Displays the total amount that is claimed by your business partner.

Requests and returns history, Line (HLR02705)

Related topics

This panel displays request line information at the detail level.

Request

Business partner

Line: Displays the request line number.

User: Displays the ID of the employee that created the record.

Quantity: Depending on what has been activated/defined in the system, and if the unit is equal to the D/E-unit for the item, the quantities will be displayed according to D/E-unit. This quantity will be displayed with two units in the same quantity field. The partial units could be displayed with decimal positions for the Display/Entry unit or by a dual display/entry of both the Display/Entry unit and the Stock unit separated by a user-defined delimiter. See About display/entry unit handling for more information.

Ext request code: Displays a code from the Request code table indicating the nature of the problem that was reported.

Int request code: Displays the internal request code as defaulted from the request header.

Resolution code: Displays a code from the Action table indicating the necessary steps to be taken to resolving this request.

Handl status, item: Displays the handling status of the item as defined in the Item file, indicating if specific restrictions apply for the item, e.g., the item is not allowed to be entered on a sales order.

Handl status, whs: Displays the handling status of the item as defined in the Item file, Warehouses panel, indicating if specific restrictions apply for the item in this warehouse, e.g., the item is not allowed to be entered on a sales order.

Conformity group: Displays the item conformity group code as defined in the Item file.

Goods return

Displays a code identifying the status of the returned goods. Note: These values are defined in the Panel value control file table.

Permitted values:

Cust return location: Displays a code from the Warehouse zone table indicating where the returned goods are stored. Note: This field/section is only displayed if DC1 Warehouse Management is installed and activated in Work with companies.

QC receiving loc

Displays a code from the Warehouse zone table indicating the location where the quality control inspection of the returned goods was made.

Batch number: Displays the batch number that corresponds to the returned goods.

Batch recall number: If an item with a batch number is returned, the system will search through all recall information to see if the returned item is subject to a batch recall. If it is, then in this field the batch recall number will be displayed.

Batch recall loc

Displays a code from the Warehouse zone table indicating the location where the recalled goods are stored.

Refund percentage: Displays the refund percentage.

QC performed: Displays the date when the quality control inspection was performed.

Approved quantity: Displays the result of the quality control inspection. This value indicates the number of returned goods that can be restocked (i.e. goods have passed QC inspection).

Rejected quantity: Displays the result of the quality control inspection. This value indicates the number of returned goods have failed the inspection.

Sales order: Displays the sales order number.

Sales order line: Displays the sales order line number. The item details are included on this order line.

Invoice: Displays the invoice number.

Invoice line: Displays the invoice line number. The item details are printed on this invoice line.

Requests and returns history, Action, Alert (HLR02706)

Related topics

This panel displays the actions that triggered an alert message, executed by the request.

Request

Line: Displays the request line number. The action details are printed on this request line.

Business partner

Sequence: This field is used to identify the sequence in which the resolution is executed. Note: The first action that is executed is determined by the lowest sequence number, the last action is assigned the highest sequence number (i.e. Action 10 is executed before Action 999).

User: Displays the ID of the employee that created the record.

Action: Displays the action code (and description) that was used to resolve the problem/issue presented in the request.

Automatic processing: This field is set to YES if the action was processed automatically. It is set to NO if the action was manually processed.

Started: Indicates if the process of resolving the request has begun.

Start date: Displays the date that the action was initiated.

Start time: Displays the time that the action was initiated.

Line dependent: If this option is selected, then the associating action must be connected to a request line. The action will not be performed unless the request line has been processed. This ensures that the system processes all request lines in the correct sequence before an action is called to resolve them.

Pre-requisite line

This field is used in conjunction with the Line dependent field. This field specifies whether or not a line must first be processed before the system will allow further processing of the action you are defining on this panel.

Displays the order line that was used as a pre-requisite for initiating this action.

Action dependent

If this option is selected, then the associating action must be connected to a request line. The action will not be performed unless the action on the request line has been processed. This ensures that the system processes all request actions in the correct sequence before another action is called to resolve them.

This field is set to YES if a connection between two (or more) request actions has been established. It is set to NO if the connection has not been established.

Pre-requisite action

This field is used in conjunction with the Action dependent field. This field specifies whether or not an action must first be processed before the system will allow further processing of the action you are defining on this panel.

Displays an action that was used as a prerequisite for initiating this action.

Completion status

Displays a value indicating the status of the order.

Permitted values:

Date completed: Displays the date that the action was successfully processed.

Time completed: Displays the time that the action was successfully processed.

Action reference req: This field is used in conjunction with the Action reference field. Indicates if a reference is required before the action can be processed.

Action reference: This field is used in conjunction with the Action reference req field. Displays the reference. This is a manually entered field on the action.

Alert receiver: Displays the ID of the employee that received the alert message.

Message: Displays the message that was sent to the Alert receiver.

Approval required: This field is set to YES if approval was required before the next action was processed. It is set to NO if authorisation was not needed.

Approved: Indicates if approval has been given. If Approval required is set to YES, this authorisation is needed before the next action can be processed. The receiver of the alert approves the message via Work with AMT messages.

Rejected: This field is set to NO if approval has not been received. If Approval required is set to YES, this authorisation is needed before the next action can be processed.

Date approved/rejected: Displays the date that the authorisation was either approved or rejected.

Time approved/rejected: Displays the time that the authorisation was either approved or rejected.

Requests and returns history, Action, Order (HLR02707)

Related topics

This panel displays the order details that were executed by the request and return.

Function keys

Discounts

Work with discounts for the action. The discounts are retrieved to the created order line.

Request

Line: Displays the request line number. The action details are printed on this request line.

Business partner

Sequence: This field is used to identify the sequence in which the resolution is executed. Note: The first action that is executed is determined by the lowest sequence number, the last action is assigned the highest sequence number (i.e. Action 10 is executed before Action 999).

User: Displays the ID of the employee that created the record.

Action: Displays the action code (and description) that was used to resolve the problem/issue presented in the request.

Automatic processing: This field is se to YES if the action was processed automatically. It is set to NO if the action was manually processed.

Started: Indicates if the process of resolving the request has begun.

Start date: Displays the date that the action was initiated.

Start time: Displays the time that the action was initiated.

Line dependent: If this option is selected, then the associating action must be connected to a request line. The action will not be performed unless the request line has been processed. This ensures that the system processes all request lines in the correct sequence before an action is called to resolve them.

Pre-requisite line

Displays the order line that was used as a pre-requisite for initiating this action.

Action dependent: If this option is selected, then the associating action must be connected to a request line. The action will not be performed unless the action on the request line has been processed. This ensures that the system processes all request actions in the correct sequence before another action is called to resolve them. This field is set to YES if a connection between two (or more) request actions has been established. It is set to NO if the connection has not been established.

Pre-requisite action

Displays an action that was used as a pre-requisite for initiating this action.

Completion status

Displays a value indicating the status of the order.

Permitted values:

Date Completed: Displays the date that the action was successfully processed.

Time completed: Displays the time that the action was successfully processed.

Action reference req: This field is used in conjunction with the Action reference field. Indicates if a reference is required before the action can be processed.

Action reference: This field is used in conjunction with the Action reference req field. Displays the reference. This is a manually entered field on the action.

Price: Displays the price.

Order type: This field is used in conjunction with the Type of order field. Displays the order type to be used when this action automatically processes sales, service or purchase orders.

Price unit: Only displayed if the PRCUNIT (Price unit handling) function is activated in the Function control file. Displays the unit in which the price is presented. See About price unit handling for more information.

Refund price: Displays the refund price (a value is only displayed for order related actions).

Refund %

The price on an order line can be affected by a refund percentage.

For example:

Type of order

This field is used in conjunction with the Order type field. Displays the order type that this action automatically processed.

Permitted values:

FOC: Indicates if the goods were given to the customer free of charge.

Pricing

Indicates how the price of your goods has been defined.

Permitted values:

Order: Displays the number of the order that was automatically created by the action.

Order line: Displays the order line number.

Requests and returns history, Action, Restock (HLR02708)

Related topics

This panel displays the restock actions that were executed by the Requests and Returns.

Request

Line: Displays the request line number. The action details are printed on this request line.

Business partner

Sequence: This field is used to identify the sequence in which the resolution is executed. Note: The first action that is executed is determined by the lowest sequence number, the last action is assigned the highest sequence number (i.e. Action 10 is executed before Action 999).

User: This ID identifies the employee that created the record.

Action: Displays the action code (and description) that was used to resolve the problem/issue presented in the Requests and Returns.

Automatic processing: This field is set to YES if the action was processed automatically. It is set to NO if the action was manually processed.

Started: Indicates if the process of resolving the Requests and Returns has begun.

Start date: Displays the date that the action was initiated.

Start time: Displays the time that the action was initiated.

Line dependent: This field is set to YES if a connection between two (or more) request and return lines is established, or NO if the connection has not been established. Line dependency means that the associating action must be connected to a request line. The action will not be performed unless the request line has been processed. This ensures that the system processes all request lines in the correct sequence before an action is called to resolve them. For example: In the case of a wrong item having been delivered to your customer, your customer must have returned the goods to your company before a replacement order is sent FOC. Since the “wrong” item and the replacement are defined on separate request and return lines, a connection between the two lines must be established.

Pre-requisite line

This field is used in conjunction with the Line dependent field and denotes whether or not a line must first be processed before the system will allow further processing of the action you are defining on this panel.

Displays the order line that was used as a prerequisite for initiating this action. For example, goods can only be restocked once they have been returned; a credit note can only be given to a customer once they have returned their goods, and so on.

Action dependent: If this option is selected, then the associating action must be connected to a request line. The action will not be performed unless the action on the request line has been processed. This ensures that the system processes all request actions in the correct sequence before another action is called to resolve them. This field is set to YES if a connection between two (or more) request actions has been established. It is set to NO if the connection has not been established.

Pre-requisite action

Displays an action that was used as a prerequisite for initiating this action.

Completion status

Indicates the status of the order.

Permitted values:

Date completed: Displays the date that the action was successfully processed.

Time completed: Displays the time that the action was successfully processed.

Action reference req: This field is used in conjunction with the Action reference field. Indicates if a reference is required before the action can be processed.

Action reference: This field is used in conjunction with the Action reference req field. Displays the reference. For example, the reference might be a document that has caused a credit note to be created. This is a manually entered field on the action.

Warehouse: This code from the Warehouse table indicates where the returned goods are located.

QC line entry: This field is set to YES if a quality control inspection of the goods was made at the time that the request line was entered (the system automatically brought up the QC program once the action was processed by the system). It is set to NO if the QC was performed upon reception of the goods.

QC using QC notes: Quality Control inspections can be made in two different ways: The first is to specify that a quality control inspection of the returned goods must be made when the request line is entered (in the QC line entry field). The second way would be to run the QC routine once the goods have been returned. Indicates if a quality control note has been printed.

Cust return location

This code from the Warehouse zone table indicates where the returned goods are stored.

QC receiving loc

This code from the Warehouse zone table indicates the location where the quality control inspection of the returned goods was made.

Requests and returns history, Action, Return documents (HLR02709)

Related topics

This panel displays the return actions that were executed by the Requests and Returns.

Request

Line: Displays the request line number. The action details are printed on this request line.

Business partner

Sequence: This field is used to identify the sequence in which the resolution is executed. Note: The first action that is executed is determined by the lowest sequence number, the last action is assigned the highest sequence number (i.e. Action 10 is executed before Action 999).

User: This ID identifies the employee that created the record.

Action: Displays the action code (and description) that was used to resolve the problem/issue presented in the Requests and Returns.

Automatic processing: This field is set to YES if the action was processed automatically. It is set to NO if the action was manually processed.

Started: Indicates if the process of resolving the Requests and Returns has begun.

Start date: Displays the date that the action was initiated.

Start time: Displays the time that the action was initiated.

Line dependent: This field is set to YES if a connection between two (or more) request and return lines is established, or NO if the connection has not been established. Line dependency means that the associating action must be connected to a request line. The action will not be performed unless the request line has been processed. This ensures that the system processes all request lines in the correct sequence before an action is called to resolve them. For example: In the case of a wrong item having been delivered to your customer, your customer must have returned the goods to your company before a replacement order is sent FOC. Since the "wrong" item and the replacement are defined on separate request and return lines, a connection between the two lines must be established.

Pre-requisite line

Action dependent: If this option is selected, then the associating action must be connected to a request line. The action will not be performed unless the action on the request line has been processed. This ensures that the system processes all request actions in the correct sequence before another action is called to resolve them. This field is set to YES if a connection between two (or more) request actions has been established. It is set to NO if the connection has not been established.

Pre-requisite action

Displays an action that was used as a prerequisite for initiating this action.

Completion status

Indicates the status of the order.

Permitted values:

Date completed: Displays the date that the action was successfully processed.

Time completed: Displays the time that the action was successfully processed.

Action reference req: This field is used in conjunction with the Action reference field. Indicates if a reference is required before the action can be processed.

Action reference: This field is used in conjunction with the Action reference req field. Displays the reference. For example, the reference might be a document that has caused a return note to be created. This is a manually entered field on the action.

Return note: This field is set to YES if a return note has been printed.

Transport note: This field is set to YES if a transport note was printed if a quality control inspection of the goods was made at the time that the request line was entered (the system automatically brought up the QC program once the action was processed by the system). It is set to NO if the QC was performed upon reception of the goods.

Investigation note: This field is set to YES if an investigation of the return goods was made when the request line was entered.

Labels: This code is set to YES if labels for the returned goods have been printed.