Description of Receiving Preferences : Purchase Order Window

Table 1. Receiving Preferences : Purchase Order Window
Field Description
Shipment Entry Allowed Select if shipment entry is to be created when a particular shipment is not available on the system.

Allow Shipment Entry" enables the system to automatically create a shipment entry in the system, if a shipment entry does not exist when a "Start Receipt" operation is performed.

On creation and confirmation of the shipment, the "Include in Receipt" transaction is invoked, to enable the receiving process to be carried out on this receipt.

Stores that receive shipment information via fax or email can manually enter the information into the system. This allows for enhanced tracking and visibility.

Build Pallet
Always Select if building of a pallet is mandatory during the receipt process.
Optional Select if building of a pallet is optional.
If Item Tag or Serial Tracked Select if building of pallet is required for items that are tag or serial tracked.
Build Case
Always Select if building of case is mandatory during the receipt process.
Optional Select if building of case is optional.
If Item Tag or Serial tracked Select if building of case is required for items that are tag or serial tracked.
Disposition Code Details
Disposition Code for Receipt with QC Choose the disposition code to associate with receipts for vendors or shipments that require QC.
Disposition Code for Receipt without QC Choose the disposition code to associate with receipts for vendors or shipment that do not require QC.
Receiving unexpected Items
Allow receiving unexpected Items on Shipment Select to allow receiving of unexpected items on the shipment.
Preference for Receipt Closure by Agent
Unconditionally Select if receipt closure by the agent occurs every time the closure agent is run.

This is typically used where receipts are closed as end-of-day process.

Received quantity at least equal to expected quantity Select if receipt closure by the agent occurs when the received quantity is at least equal to the expected quantity.
After Putaway Completion Select if receipt closure by the agent occurs after putaway is completed.

This applies to stores that indicate availability only when inventory is putaway to their storage locations.

Vendor Preferences Populated automatically from vendor preferences in the Sterling Supply Collaboration.

The preferences are evaluated to determine the best preference. The preference with most matches to the order details is determined as the best preference.

For more information about Defining Customer Classifications, see the Configuring Sterling Supply Collaboration.

Vendor This indicates the vendor.

A vendor is defined as an external company that supplies materials that you order. You receive materials from your vendors. You are, in turn, vendors to your customers.

Vendor Classification This indicates classification of the vendor.
Item ID This indicates item ID.
Receiving Item Classification This indicates the custom defined item storage definition.
Force Case Content entry This indicates whether case content entry during receipt must be forced.
Requires QC This indicates whether QC is required or not.

The closure of a shipment triggers the upload of receipt information to external HOST systems is updated in Sterling Supply Collaboration. For example, inventory availability for the shipment is moved from an in-transit to on-hand.

Vendor-specific preferences, if any, configured as part of the Sterling Supply Collaboration display here. For more information, see the Configuring Sterling Supply Collaboration.

Preferences for receiving a shipment are specified as a receiving preference for the ship node and enterprise level. A supervisor, may choose to override these preferences for a specific vendor. For example, a ship node requiring case content verification for most vendors. For a particular vendor a supervisor can override this requirement while manually creating shipment.

The feature of override is only relevant when the preference has been set forcing a granular activity. For example, override is not relevant for a ship node that does not require pallet content verification at a vendor level.