PO Based Receiving

You may want the option to receive inventory against Purchase Orders (POs) without the need of an ASN.

The option ‘PO receiving’ allows you to do this. You can enable PO receiving from the mode parameter in the RF Receive IB Shipment screen.

When the ‘PO receiving’ option is enabled, the transaction prompts you to scan a PO Number to initiate receiving.

Once you scan the PO Number:

If the PO is linked to multiple Inbound Shipments, the screen will provide an error message and will not allow you to proceed with receiving.
If the PO is linked to an unverified Inbound Shipment, you can receive against the inventory in that Inbound Shipment, which is equal to the PO’s inventory.
If the PO is not linked to an Inbound Shipment, the system auto-generates an Inbound Shipment in the background for the whole PO and allows you to receive. You should enable the ‘Create ASN for PO Interface’ flag should for the corresponding vendor.
If the PO is linked to a verified Inbound Shipment, the application auto-generates an Inbound Shipment for the quantity pending to be received. You should enable the ‘Create ASN for PO Interface’ flag for the corresponding vendor.
Additionally, you can make appointments for specific PO Numbers so that you can check a PO Number into a Dock.
When the Dock location is scanned during receiving with “mode” set to ‘PO receiving’ the system will auto-populate the PO Number.

Prompt for PO Sequence Number/PO Line Schedule Number

In order to support reconciliation of Purchase Order (PO) lines under receipt, the RF Parameter (prompt_po-seq-line) is available in RF Receive (LPN) Shipment (rf.inbound.cwrfrecvlpnshpmt) and RF Receive Load (rf.inbound.cwrfrecvlpnload) modules which supports prompting for the PO sequence number or the PO line schedule number based on the configuration.

PARAMETER DETAILS

The prompt_po-seq-line parameter has the following options under the drop-down:

PO Sequence
PO line schedule

NOTE: The default value of the prompt_po-seq-line parameter is Blank. When the parameter is set to Blank, the system exhibits the existing behavior and should not prompt for the PO sequence or line schedule number.

Companies using Oracle WMS Cloud together with Oracle SCM Cloud should set the parameter "prompt_po-seq-link" screen parameter to be "PO Line Schedule."

This parameter can be used in the following flows:

PO Based Receiving
RF Receiving Flow
RF Receive by Load

The following table provides details about the parameter behavior for these flows when the prompt_po-seq-line parameter is set to PO Sequence or PO line schedule:

Flow	prompt_po-seq-line set to: Purchase Order (PO) Sequence	prompt_po-seq-line set to: Purchase Order (PO) Line Schedule
PO Based Receiving	If a PO has multiple details with the same SKU, the system prompts for the PO sequence list. If a PO only has a single detail for a SKU, (if there is no conflict), the system will not prompt for the PO sequence number. For an Attribute tracked item, if the item level configuration is set to *Required, validate, Allow user override* the system prompts for the attribute even if the the system can determine the attribute from the PO sequence PO line schedule scan. For an attribute tracked Item, if the Attribute prompt is set to *Required, validate, Allow user override* and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail." In case a user receives more quantity than the order quantity for a PO sequence number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"	If a PO has multiple details with the same SKU, the system prompts for the PO line schedule list. If the line schedule number is not populated on the PO, then the system should prompt for PO sequence number even if the prompt_po-seq-line set to PO line schedule. If a PO only has a single detail for a SKU, (if there is no conflict), the system will not prompt for the PO line schedule number. for an Attribute tracked item, if the item level configuration is set to *Required, validate, Allow user override* the system prompts for the attribute even if the the system can determine the attribute from the PO sequence PO line schedule scan. For an attribute tracked Item if the Attribute prompt is set to *Required, validate, Allow user override* and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail." In case a user receives more quantity than the order quantity for a PO line schedule number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"
RF Receive Shipment	If there is only one detail/SKU for a PO or if the system can determine the PO sequence from the remaining PO details. the Purchase Order sequence list during RF IB shipment receiving does NOT appear. The Purchase Order sequence list during RF IB shipment receiving appears if an IB shipment details has multiple PO numbers or PO -sequence combinations for the same SKU. After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO sequence numbers. After scanning a SKU if multiple purchase orders are found, the system prompts for the purchase order list for the SKU. After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO sequence numbers. For an Attribute tracked item, if the item level configuration is set to *Required, validate, Allow user override* the system prompts for the attribute even if the system can determine the attribute from the PO sequence scan. For an attribute tracked Item, if the Attribute prompt is set to *Required, validate, Allow user override* and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail." This error message should not appear when prompt-po-seq-line is not configured. In that case, users can scan an unanticipated attribute. A new shipment detail will be created with 0 shipped qty without the PO number populated. If a user receives more quantity than the order quantity for a PO sequence number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"	If there is only one detail/SKU for a PO or if the system can determine the PO line schedule from the PO details, the Purchase Order line schedule number list during RF IB shipment receiving does NOT appear. The Purchase Order line schedule number list during RF IB shipment receiving appears if an IB shipment detail has multiple PO numbers or Purchase Order line schedule number combinations for the same SKU. After scanning a SKU if multiple purchase orders are found the system prompts for the purchase order list for the SKU. After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO line schedule numbers. If the line schedule number is not populated on the PO, then the system should prompt for PO sequence number even if the prompt_po-seq-line set to PO line schedule. For an Attribute tracked item, if the item level configuration is set to *Required, validate, Allow user override* the system prompts for the attribute even if the the system can determine the attribute from the PO line schedule scan. For an attribute tracked Item if the Attribute prompt is set to *Required, validate, Allow user override* and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail." This error message should not appear when prompt-po-seq-line is not configured. In that case, users can scan an unanticipated attribute. A new shipment detail will be created with 0 shipped qty without the PO number populated. If a user receives more quantity than the order quantity for a PO line schedule number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"
RF Receive by Load	System prompts for the PO number and the sequence list after scanning the SKU in case the PO has multiple details for the same SKU or the IB Shipment has multiple POs for the same SKU. User is prompted for the PO number as a list right after the SKU scan (showing all the eligible PO number-PO sequence number for the scanned SKU that the user can receive for the IB Shipment) . After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO sequence numbers. In case an IB Shipment has only one detail, or if the IB shipment has multiple details carrying different PO for different SKUs, the system doesn’t prompt for the PO number list because the system can identify the sequence number to be received. For an attribute tracked Item if the Attribute prompt is set to *Required, validate, Allow user override* and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail." This error message should not appear when prompt-po-seq-line is not configured. In that case, users can scan an unanticipated attribute. A new shipment detail will be created with 0 shipped qty without the PO number populated. In case, a user receives more quantity than the order quantity for a PO sequence number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"	System prompts for the PO number and the Line schedule list after scanning the SKU in case the PO has multiple details for the same SKU or the IB Shipment has multiple POs for the same SKU. User is prompted for the PO number as a list right after the SKU scan (showing all the eligible PO number for the scanned SKU that the user can receive for the IB Shipment) . After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO line schedule numbers. In case an IB Shipment has only one detail, or if the IB shipment has multiple details carrying different PO for different SKUs, the system doesn’t prompt for the PO line schedule number list because the system can identify the line schedule number to be received. For an attribute tracked Item if the Attribute prompt is set to Required, validate, allow user override and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail." This error message should not appear when prompt-po-seq-line is not configured. In that case, users can scan an unanticipated attribute. A new shipment detail will be created with 0 shipped qty without the PO number populated. In case, a user receives more quantity than the order quantity for a PO sequence number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?" If any of the PO line schedule number is not populated on the PO details. the system prompts for the PO sequence number. However, the PO sequence number is prompted only if the scanned PO has multiple details with the same SKU on the IB shipment.

Flow

prompt_po-seq-line set to: Purchase Order (PO) Sequence

prompt_po-seq-line set to: Purchase Order (PO) Line Schedule

PO Based Receiving

If a PO has multiple details with the same SKU, the system prompts for the PO sequence list.

If a PO only has a single detail for a SKU, (if there is no conflict), the system will not prompt for the PO sequence number.

For an Attribute tracked item, if the item level configuration is set to Required, validate, Allow user override the system prompts for the attribute even if the the system can determine the attribute from the PO sequence PO line schedule scan.

For an attribute tracked Item, if the Attribute prompt is set to Required, validate, Allow user override and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail."

In case a user receives more quantity than the order quantity for a PO sequence number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"

If a PO has multiple details with the same SKU, the system prompts for the PO line schedule list.

If the line schedule number is not populated on the PO, then the system should prompt for PO sequence number even if the prompt_po-seq-line set to PO line schedule.

If a PO only has a single detail for a SKU, (if there is no conflict), the system will not prompt for the PO line schedule number.

for an Attribute tracked item, if the item level configuration is set to Required, validate, Allow user override the system prompts for the attribute even if the the system can determine the attribute from the PO sequence PO line schedule scan.

For an attribute tracked Item if the Attribute prompt is set to Required, validate, Allow user override and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail."

In case a user receives more quantity than the order quantity for a PO line schedule number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"

RF Receive Shipment

If there is only one detail/SKU for a PO or if the system can determine the PO sequence from the remaining PO details. the Purchase Order sequence list during RF IB shipment receiving does NOT appear.

The Purchase Order sequence list during RF IB shipment receiving appears if an IB shipment details has multiple PO numbers or PO -sequence combinations for the same SKU.

After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO sequence numbers.

After scanning a SKU if multiple purchase orders are found, the system prompts for the purchase order list for the SKU.

After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO sequence numbers.

For an Attribute tracked item, if the item level configuration is set to Required, validate, Allow user override the system prompts for the attribute even if the system can determine the attribute from the PO sequence scan.

For an attribute tracked Item, if the Attribute prompt is set to Required, validate, Allow user override and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail."

This error message should not appear when prompt-po-seq-line is not configured. In that case, users can scan an unanticipated attribute. A new shipment detail will be created with 0 shipped qty without the PO number populated.

If a user receives more quantity than the order quantity for a PO sequence number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"

If there is only one detail/SKU for a PO or if the system can determine the PO line schedule from the PO details, the Purchase Order line schedule number list during RF IB shipment receiving does NOT appear.

The Purchase Order line schedule number list during RF IB shipment receiving appears if an IB shipment detail has multiple PO numbers or Purchase Order line schedule number combinations for the same SKU.

After scanning a SKU if multiple purchase orders are found the system prompts for the purchase order list for the SKU.

After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO line schedule numbers.

If the line schedule number is not populated on the PO, then the system should prompt for PO sequence number even if the prompt_po-seq-line set to PO line schedule.

For an Attribute tracked item, if the item level configuration is set to Required, validate, Allow user override the system prompts for the attribute even if the the system can determine the attribute from the PO line schedule scan.

For an attribute tracked Item if the Attribute prompt is set to Required, validate, Allow user override and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail."

This error message should not appear when prompt-po-seq-line is not configured. In that case, users can scan an unanticipated attribute. A new shipment detail will be created with 0 shipped qty without the PO number populated.

If a user receives more quantity than the order quantity for a PO line schedule number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"

RF Receive by Load

System prompts for the PO number and the sequence list after scanning the SKU in case the PO has multiple details for the same SKU or the IB Shipment has multiple POs for the same SKU.

User is prompted for the PO number as a list right after the SKU scan (showing all the eligible PO number-PO sequence number for the scanned SKU that the user can receive for the IB Shipment) .

After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO sequence numbers.

In case an IB Shipment has only one detail, or if the IB shipment has multiple details carrying different PO for different SKUs, the system doesn’t prompt for the PO number list because the system can identify the sequence number to be received.

For an attribute tracked Item if the Attribute prompt is set to Required, validate, Allow user override and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail."

This error message should not appear when prompt-po-seq-line is not configured. In that case, users can scan an unanticipated attribute. A new shipment detail will be created with 0 shipped qty without the PO number populated.

In case, a user receives more quantity than the order quantity for a PO sequence number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"

System prompts for the PO number and the Line schedule list after scanning the SKU in case the PO has multiple details for the same SKU or the IB Shipment has multiple POs for the same SKU.

User is prompted for the PO number as a list right after the SKU scan (showing all the eligible PO number for the scanned SKU that the user can receive for the IB Shipment) .

After selecting the PO number, if the selected PO has multiple lines for the same SKU, the system prompts for another pop up displaying the PO line schedule numbers.

In case an IB Shipment has only one detail, or if the IB shipment has multiple details carrying different PO for different SKUs, the system doesn’t prompt for the PO line schedule number list because the system can identify the line schedule number to be received.

For an attribute tracked Item if the Attribute prompt is set to Required, validate, allow user override and the PO detail is already populated with an Attribute value, the system throws the following error message upon overriding the defaulted attribute during PO based receiving: "Scanned Attribute is not valid for the PO detail."

This error message should not appear when prompt-po-seq-line is not configured. In that case, users can scan an unanticipated attribute. A new shipment detail will be created with 0 shipped qty without the PO number populated.

In case, a user receives more quantity than the order quantity for a PO sequence number, the system prompts for the following warning message: "QTY received is more the anticipated PO detail qty, proceed?"

If any of the PO line schedule number is not populated on the PO details. the system prompts for the PO sequence number. However, the PO sequence number is prompted only if the scanned PO has multiple details with the same SKU on the IB shipment.

QUANTITY DISTRIBUTION FOR PO AND SHIPMENT BASED RECIPT

Oracle WMS Cloud has been updated so that when the prompt_po-seq-line screen parameter is set to blank, the system evenly distributes the received SKU quantity across multiple Purchase Orders or purchase order lines, which resolves purchase order line reconciliation issues. Quantity distribution is only supported for IB shipments details carrying multiple purchase orders for the same SKU or a purchase order with multiple lines for the same SKU.

The following table provides details about the system behavior for these flows when the prompt_po-seq-line parameter is set to blank:

Flow	Behavior
PO Based Receiving	When set to blank and the Purchase Order has a tolerance, the excess quantity is latched to the first detail after the quantity distribution happens evenly across the PO line numbers. If the PO does NOT have tolerance defined, the system should evenly distribute the quantity across the IB shipment details for the respective PO and PO line numbers. If a PO has multiple lines with an attribute tracking SKU, the system will not distribute the qty across the PO line evenly if the PO lines are populated with different Attributes.
RF Receive Shipment (Shipment is carrying multiple PO numbers or PO details of the same SKU)	When set to blank and the Shipment has a tolerance, the excess quantity is latched to the first detail after the quantity distribution happens evenly across the IB shipment details for the respective PO and PO line numbers. If a shipment is carrying multiple Purchase Orders of the same SKU and the tolerance percentage is at the PO or both at shipment and PO, the system evenly distributes the quantity across the POs and the excess qty for the tolerance percentage will be carried forward to the next eligible PO after the tolerance limit of the first PO is exhausted. If the shipment does NOT have tolerance defined, the system should evenly distribute the quantity across the IB shipment details for the respective PO and PO line numbers for the same SKU.
RF Receive Load (Shipment is carrying multiple PO numbers or PO details of the same SKU)	When set to blank, and users try to receive an IB shipment with multiple details for the same SKU converted from a PO, the system should evenly distribute the SKU quantity across the IB shipment details for the respective PO and PO line numbers. If the PO/IB shipment does NOT have tolerance defined for the SKU, the system evenly distributes the quantity across the details carrying multiple PO numbers or PO details for the same SKU. If a shipment is carrying multiple POs of the same SKU and the tolerance percentage is at the PO or both at shipment and PO, the system evenly distributes the quantity across the POs and the excess qty for the tolerance percentage will be carried forward to the next eligible PO after the tolerance limit of the first PO is exhausted.

Flow

Behavior

PO Based Receiving

When set to blank and the Purchase Order has a tolerance, the excess quantity is latched to the first detail after the quantity distribution happens evenly across the PO line numbers.

If the PO does NOT have tolerance defined, the system should evenly distribute the quantity across the IB shipment details for the respective PO and PO line numbers.

If a PO has multiple lines with an attribute tracking SKU, the system will not distribute the qty across the PO line evenly if the PO lines are populated with different Attributes.

RF Receive Shipment

(Shipment is carrying multiple PO numbers or PO details of the same SKU)

When set to blank and the Shipment has a tolerance, the excess quantity is latched to the first detail after the quantity distribution happens evenly across the IB shipment details for the respective PO and PO line numbers.

If a shipment is carrying multiple Purchase Orders of the same SKU and the tolerance percentage is at the PO or both at shipment and PO, the system evenly distributes the quantity across the POs and the excess qty for the tolerance percentage will be carried forward to the next eligible PO after the tolerance limit of the first PO is exhausted.

If the shipment does NOT have tolerance defined, the system should evenly distribute the quantity across the IB shipment details for the respective PO and PO line numbers for the same SKU.

RF Receive Load

(Shipment is carrying multiple PO numbers or PO details of the same SKU)

When set to blank, and users try to receive an IB shipment with multiple details for the same SKU converted from a PO, the system should evenly distribute the SKU quantity across the IB shipment details for the respective PO and PO line numbers.

If the PO/IB shipment does NOT have tolerance defined for the SKU, the system evenly distributes the quantity across the details carrying multiple PO numbers or PO details for the same SKU.

If a shipment is carrying multiple POs of the same SKU and the tolerance percentage is at the PO or both at shipment and PO, the system evenly distributes the quantity across the POs and the excess qty for the tolerance percentage will be carried forward to the next eligible PO after the tolerance limit of the first PO is exhausted.

PREVENT CONSUMING ENTIRE PURCHASE ORDER DURING PO-BASED RECEIVING

A new screen parameter ‘prevent-entire-po-to-asn-conversion-flg’ has been introduced in the RF Receive Shipment (rf.inbound.cwrfrecvlpnshpmt) module which allows you to restrict the system from converting the entire PO to a shipment right after the PO scan during PO based receiving. The screen parameter receiving mode should be set to PO based receiving.

PARAMETER DETAILS

The prevent-entire-po-to-asn-conversion-flg parameter has the following options under the drop-down:

No (default behavior)
Yes

When the prevent-entire-po-to-asn-conversion-flg is set to Blank or No,

The system converts the entire PO to an ASN during PO based receiving. However, the system converts the entire PO to an ASN only after you scan or skip the trailer scan during PO based receiving.

In case multiple shipments are created prior to PO based receiving, the system will display the following error message right after the PO scan.

“Cannot receive PO linked to Multiple ASNs”

Vendor QC will be supported for this mode and the quality check will happen based on the shipped quantity and the vendor QC configuration.
Users will not be able to reduce the purchase order quantity once the entire PO is converted to a shipment during PO based receiving.

When the prevent-entire-po-to-asn-conversion-flg is set to Yes:

During PO Based Receiving, the system can create the ASN details based on the PO quantity a user is receiving from PO-based receiving mode, so that the whole PO does not get converted to an ASN and its respective details. This allows purchase orders that have been partially received to be updated. For example, supply chain planning may send a recommended change for a purchase order when the supplier was not able to ship the full expected quantity.

NOTE: The purchase order quantity can’t be updated for less than the received quantity.

The system prevents consuming the entire PO to the respective IB shipment details when you scan a PO in PO-based receiving mode. After scanning the PO number, the system creates only the IB shipment header based on the PO and the trailer number combination (if no IB shipment with status less than Verification in progress is found for the same PO and trailer number combination.)

After you scan the trailer number, if no open ASN is found, then the system creates a new ASN associating the trailer number to proceed with PO based receiving. The ASN header won't be created until you scan or skip the trailer number.

You can press the Ctrl-E hot key to end receiving on the PO based receiving transaction and the shipment details created will have 0 as the shipped quantity if no prior shipment is created for the PO from the UI or the interface.

Vendor QC is not supported in this mode of PO based receiving as the shipped quantity for the shipments created during this mode of PO based receiving will be 0.

The shipment verification files generated upon ASN verification of the ASNs created during PO-based receiving will also have a shipped quantity as 0.

The system will create a new trailer number record if you scan a trailer number which is not present in the system and the system latches the trailer number to a Shipment with ‘In transit’ status and which does not have a trailer number populated. If no eligible shipment is found for the PO trailer combination, the system then creates a new Shipment with the PO trailer combination.

Users can receive the remaining PO order in different trailers. The system creates a new Shipment with 0 as shipped quantity with the PO and trailer combination and allow users to receive the outstanding PO quantity against the shipment.

In case the system finds multiple shipments created prior to PO based receiving, and if it cannot identify the shipment even after you scan the trailer number, the system will throw the following error message: “PO linked to Multiple ASNs created prior to receipt, cannot perform PO based receipt”

However, the system will allow you to proceed with PO based receiving if multiple shipments are created with 0 as shipped quantity in this mode of PO based receiving. The shipments will be identified and picked based on the PO trailer combination.

BEHAVIOR FOR PO BASED RECEIVING BASED ON FLAG

Transaction	prevent-entire-po-to-asn-conversion-flg = Blank /NO	prevent-entire-po-to-asn-conversion-flg = Yes
Entire PO gets converted to shipment	YES	NO
Shipped qty is more than zero	YES	NO
PO order qty can be reduced after users starts receiving partially	NO	YES
PO Seq /Line prompt is supported	YES	YES
Attribute Prompt is based on shipment dtl	YES	NO
Vendor QC is supported	YES	NO (based on PO details -if PO has Attribute)
Shipment is created/Identified After trailer scan	YES	YES (Only if shipment is created Prior to PO receiving)
verification file has 0 as Shipped qty	NO	YES
Allow PO recv when Multiple Shipments are found	NO	YES (If system can identify shipments after trailer scan)
Additional PO qty or PO details gets latched to the same ASN	YES	NO

INTRODUCTION OF NEW MESSAGES

Parameter status	Use case	Error message
prevent-entire-po-to-asn-conversion-flg= Yes	Multiple IB shipments are found with more than 0 as shipped qty in less than verification in progress	PO linked to Multiple ASNs created prior to receipt, cannot perform PO based receipt
prevent-entire-po-to-asn-conversion-flg= Yes	Shipment is attached to an appointment and the scanned trailer does not match with the shipment	Trailer and shipment do not match

Marking the Reference Purchase Order column as '*' when an LPN is Received With Multiple POs

The system marks the REF PO number column on the IB container UI as "*" for the IBLPNs received with multiple purchase orders. This will indicate that the LPN is carrying multiple purchase orders.

NOTE: The IHT-1 LPN received inventory history will continue to get split based on the PO numbers getting received in the IBLPN. Additionally, The REF PO number column on the IB container UI will show the PO number if the IBLPN is being received with only a single purchase order.

STEPS TO ENABLE

To prompt for PO-sequence number or the PO-line schedule number during Inbound Receiving, in Modules, search for the Recv {lpn} Shipment module.
Then from Screens - Screen Parameters, , select the PO Sequence or PO line schedule option from the prompt_po-seq-line parameter drop-down.