Configuration Fields for Cartonized ASN

You can choose whether to prompt for multiple batch/expiry/Attribute/serial for a single SKU within an LPN for a cartonized ASN via Shipment type UI

To configure the cartonized receiving for batch, expiry and inventory attribute prompt controls:

1. Go to IbShipmentTypeView screen and click Create button.
2. Enter the shipment details.
3. Populate the desired prompt control.

   Three drop-down fields are available on the create shipment type UI along with their values:

   • Cartonized receiving batch and expiry prompt control: Blank/ Prompt, if not known/Always prompt/ Do not prompt.
   • Cartonized receiving Attribute prompt control: Blank/Prompt, if not known/Always prompt/ Do not prompt.
   • Cartonized receiving Serial prompt control: Blank (Default behavior)/ Prompt, if not known/Always prompt/ Do not prompt.
   If the field is blank, the system honors item level configuration. i.e., Prompt, if not know. However, when Cartonized Receiving for Batch number & Expiry Number /Attribute /Serial prompt control is set to Prompt, if not known or Always prompt or Do not prompt, the system does not honor any of the item property configurations for batch/expiry dates/ inventory attribute/ serial number.

   Note: If you scan a batch number that does not match with the batch number present on the LPN (Other than blank value), then system display the message, "Batch number is not present in the LPN".

   Note: If you scan an Expiry date which is not matching with the Expiry date present on the LPN (Other than blank value) then system displays the message, “Expiry date is not present in the LPN".
4. Click Save.

Example: Cartonized ASN - Screen flow for batch/expiry/inventory attribute/serial tracked SKU

In a cartonized receiving flow, the system will retain the LPN on the anticipated detail after receiving an unanticipated detail for the same SKU. In detail receiving of cartonized shipment, the system will retails the LPN on the anticipated detail when you scan and receive an unanticipated detail (Such as batch/exp/inv attribute) form the same SKU

On receiving a cartonized shipment having multiple batch/expiry/inventory attributes for the same SKU in a single IBLPN, the system loops through each detail individually.

Let’s say, you have the following ASN:

Cartonized ASN - Screen flow

ASN	LPN	SKU	Shipped Qty	Received Qty	Attribute	Batch number	Expiry Date
ASN001	LPN001	SKU01	100	0	IND	BATCH-CY-2020	12122020
ASN001	LPN001	SKU01	100	0	USA	BATCH-CY-2021	09122020

1. The system loops through the first detail by scanning the LPN, the inventory attribute (IND), then batch (BATCH-CY-2020), expiry date (12122020), serial number (if any).
2. The system moves to the second detail (without ending LPN), scans the inventory attribute (USA), then batch (BATCH-CY-2021), expiry date (09122020), serial number (if any).

Example: Cartonized ASN - Screen flow for batch/expiry/inventory attribute/serial tracked SKU = Do Not Prompt (Classical Cartonized)

This is a classical receiving behavior and the flag is available on the Shipment type UI to restrict prompting of batch/expiry/inventory attribute/Serial for a single SKU within an LPN, but the system fetches the batch/expiry/attributes from the ASN detail, and the serial numbers are fetched from the IB shipment serial number table.

Note: When configuring the shipment type to Do Not Prompt, you need to populate the batch, expiry date, inventory attribute, and serial numbers on the respective details. Otherwise, the system will not be able to perform RF Receiving and will prompt you to perform detailed receiving.

Let’s say, you have the following prompt control configured:

When Cartonized ASN - Screen flow for serial tracked SKU = Do Not Prompt:

After scanning the SKU, the system doesn’t prompt for serial number:

You can view the associated serial number from the IB Container UI. Clock on the numbered hyperlink from the view_serial_nbs column.

When Cartonized ASN - Screen flow for batch/expiry and inventory attribute = Do Not Prompt

After receiving, the system updates in the following manner: