Receiving of QC Rejected LPNs and Returning to Vendor

Allowing QC Rejected Inventory into the Warehouse

You can receive the QC rejected inventory into the warehouse. To differentiate the QC rejected inventories you got a provision to update an un-allocatable lock code to the QC rejected inventories. On applying the lock code, the QC rejected status remains in Rejected status and the LPN status moves to Received. So, the system allows the rejected inventories to be brought inside the warehouse.

Applying Un-Allocatable Lock Code via RF QC Complete transaction

The lock code prompt for RF QC Complete works based on the parameter configuration for the QC Rejected inventories.

To configure the parameters in the RF QC Complete transaction, do the following:

Go to RF QC Complete (rf.inbound.cwrfqccomplete) module.
Configure the “rejected-inventory-handling” parameter to “Lock rejected inventory”.
This enables the system to prompt for lock code while performing the RF QC Complete transaction to apply an un-allocatable lock code for the rejected LPNs.
Note: By default, the “rejected-inventory-handling” is set as a blank. If the “rejected-inventory-handling” is set as a blank, the system will not prompt for a lock code and does not track any QC Rejected inventories.
To auto populate an un-allocatable lock code for QC Rejected inventories, set the “rejected-lock-code” parameter with a valid lock code value.
Note:
- If the configured lock code is invalid, then the system displays an error message “Invalid lock code for facility or company" (Message code 2013). On accepting the message, the un-allocatable lock codes are displayed to select.
- By default, the “rejected-lock-code” is set as a blank. If“rejected-lock-code” parameter is not configured, then the system prompts for the un-allocatable lock code (if the QC Rejected inventory handling is set to Lock rejected inventory).

The following table details the behavior of the parameters:

QC Status	rejected-inventory-handling	rejected-lock-code	LPN Status	Behavior
QC Rejected	Blank	Blank	Canceled	The system does not prompt for lock code and does not track QC Rejected inventories.
QC Rejected	Lock rejected inventory	Blank	Received	You need to provide an un-allocatable lock code when prompted.
QC Rejected	Blank	Lock code provided	Canceled	The lock code is not honored.
QC Rejected	Lock rejected inventory	Lock code provided	Received	The system defaults the configured lock code and does not prompt for the lock code.

Note:

If the LPN is QC accepted, the system doesn’t prompt for a lock code.
If you apply an allocatable lock code on the QC Rejected LPN or configured an allocatable lock code in the “rejected-lock-code” parameter, the system displays error message "Cannot QC reject with an allocatable lock code".
Applied lock code is recorded under the “Lock Code” column in the Verification History view UI screen.
On completion of RF QC Complete transaction, the system considers the QC Rejected inventories and updates the shipment and associated PO quantity (if any).

Once you configure the parameters for RF QC Complete module, you can proceed for quality check. For more details on QC process, refer to Receiving/QC Process.

Applying Lock Code via IB Container and IB Shipment UI

You can apply un-allocatable lock code for LPNs in the IB Container (IbContainerView) and IB Shipment (IBShipmentView) UI.

To apply an un-allocatable lock code for LPNs, do the following:

Go to IB Container or IB Shipment screen.
Select the records and click “Reject” action button.
In the Reject pop-up, select an un-allocatable lock code from the Lock Code drop-down list.
Note:
- The applied lock code will be applicable to all the selected LPNs subjected to QC.
- Applying a lock code upon rejecting an LPN is not mandatory. If you are not selecting a lock code, on performing QC Reject, the LPN status moves to Cancelled.
Click Submit.
On applying the lock code, the QC Rejected LPN status moves to Received and brings the LPN within the four walls.
Note: If some of the selected LPNs already has the same lock code, the system displays an error message “Successfully completed:<LPN> Some of the LPNs are not rejected with lock code as the same lock is already applied to them <LPN>” and retains the same LPN status and do not get QC rejected.

Creating an Order for QC Rejected LPNs

Once you apply an un-allocatable lock code to an QC Rejected LPN, you can create an order to ship the rejected inventories from designated locations.

Primarily, you need to configure the un-allocatable lock code, to do so follow the below steps:

Go to Order Type screen.
Select an order type record and click edit (pencil) icon.
OR
To create a new order type, click create (plus) icon.
In the edit pane, enter the lock code in the “Eligible Lock code for Allocation” field.
The system compares the lock code on the IBLPN with the defined lock codes. If the lock codes are matched, then the system allocates the QC Rejected IBLPN.
Note:
- You can define both allocatable and un-allocatable lock codes that allow IBLPNs to be allocated and shipped to the vendors via RF Direct Allocation and RF Pick and Allocate transactions.
- You can use comma to separate and enter multiple valid lock codes.
Click Save.

Once you configure the order type, you can create order to send the QC rejected inventories to vendors. For more details on creating orders, refer to Creating Orders in WMS .

Allocating for QC Rejected LPNs

Once you configure the lock codes on the Order Type UI and create an order, you can allocate the QC Rejected LPNs to vendors via the RF Pick and Allocate and RF Direct Allocation transactions.

QC Rejected Inventory allocation is possible only through user directed mode in the RF Pick and Allocate transaction and LPNs should be in Reserve locations.

If the scanned LPN has multiple un-allocatable lock codes, but only one of them matches with the Eligible Lock code for Allocation in the Order Type, then the lock code with higher priority will take precedence.

If you scan an active location the system displays an error message “Order Type has lock code for QC Reject. <%> location is not supported for allocation.”.

The following table details the allocation of IBLPNs via RF Direct Allocation and RF Pick and Allocate:

IBLPN	Lock Code on the IBLPN	Lock Code Type	Lock Code for Order type	Behavior
LPN01	LC01	Allocatable		Not required. Do not provide any lock code.
LPN01	LC01	Allocatable	LC02 (un-allocatable)	IBLPN doesn’t gets allocated and the system displays an error message "Lock code mismatch".
LPN01			LC02 (un-allocatable)	IBLPN doesn’t gets allocated and the system displays an error message "Lock code mismatch".
LPN01	LC01	Un-allocatable		IBLPN doesn’t gets allocated and the system displays an error message “IBLPN has unlocatable lock”.
LPN01	LC02	Un-allocatable	LC02, LC03 (both un-allocatable)	IBLPN gets allocated. (If lock code priority is not set or both LC02 and LC03 has same lock code priority).
LPN01	LC03	Un-allocatable	LC02, LC03 (both un-allocatable)	IBLPN gets allocated. (If you are using lock code priority, then LC02 should have lesser priority than LC03).
LPN01	LC03	Un-allocatable	LC02, LC03 (both un-allocatable)	IBLPN doesn’t gets allocated and the system displays anerror message “Scanned LPN has another un-allocatable lock code with a higher priority". (If you are using lock code priority and LC02 have greater priority than LC03).

Restricting QC Rejected inventory to Mix with Other Inventories

The system avoids mixing of QC Rejected Inventory with the good inventory. You can refer the following transactions and cases where the system restricts the mixing of inventories.

Restricting RF Split IBLPN and RF IB Sort During QC Complete Transaction

You can split and sort similar QC Rejected inventory via the RF Split IBLPN (rf.inbound.cwrfsplitcntr) transaction and thus restricting splitting of QC Rejected inventory into non-rejected LPN when performing the split transaction.

When performing RF Split IBLPN (rf.inbound.cwrfsplitcntr) or RF IB Sort (rf.inbound.cwrfibsortlpn) transaction, the system behaves in the following manner:

Source LPN	Destination LPN	Behavior
QC rejected inventory	With New LPN	Inventory splits or merges from the source LPN and moved to the destination LPN. So, the lock code and QC status will be transferred to the destination LPN.
QC rejected inventory	An existing QC rejected LPN	Inventory splits or merges from the source and moved to the destination LPN having the same or different lock code. Note: When the Required Validation parameter is set to All, and if the source LPN has an un-allocatable lock code present, the same lock code should be matched with the destination LPN as well. Otherwise, the system displays an error message “Lock code mismatch”. You can perform RF split transactions when the source and destination IBLPN has different lock codes and the Required Validation parameter is set to None.
QC rejected inventory	Existing LPN without any reject inventory	The system displays an error message “QC Reject inventory cannot be mixed with non-reject inventory' should be displayed”.
Existing LPN without any reject inventory	QC Reject LPN	The system displays an error message “QC Reject inventory cannot be mixed with non-reject inventory' should be displayed”.

Note: It is recommended to use Container QC status as the sort criteria to sort the QC rejected IBLPNs. Otherwise, you are required to scan a different Sort Zone to sort the QC rejected LPNs if the sorting zone already has mainstream inventories.

Restricting Create LPNs from Active Location

The system allows you to scan an existing IBLPN (if the shipment associated with the IBLPN is verified), when you create LPNs from an active location using RF Create LPN.

If you scan an existing IBLPN that is QC Rejected and in Received status, the system displays an error message “Invalid LPN status, LPN is QC rejected”.

This applies when,

LPNs are created with Inventories out of active location.
LPNs are associated with a verified shipment.

Restricting QC Rejected LPNs During Palletization

The system prevents combining of QC Rejected inventory with regular inventory on the pallet. The system displays an error message “Pallet cannot have a mix of QC rejected and non-rejected inventory” in the following conditions on the mentioned transactions:

RF Palletization (rf.inbound.cwrfpalletizeplt) transaction:

When you scan an existing pallet during palletization containing QC rejected LPNs, and you scan a regular LPN.

RF putaway (rf.inbound.cwrfputaway) transaction:

When prompt-dest-pallet parameter is configured to yes and

You scan a QC rejected LPN for putaway and pallet contains good LPN.
You scan a regular LPN for putaway and pallet contains QC rejected LPN.

RF Locate LPN/pallet (rf.inbound.cwrflocatelpnpallet) transaction:

When prompt-dest-pallet parameter is configured to yes and

You scan a QC rejected LPN to locate and pallet contains good LPN.
You scan a regular LPN to locate and pallet contains QC rejected LPN.