Ord Inv Mgmt

Primary key, system generated by a sequence that will uniquely identify a single supplier or supplier/department record.

Indicator used to determine if orders for the supplier or supplier/department should be scaled to meet constraints. This indicator is used for both replenishment and manual orders. Valid values are: Y - Yes. Scale orders to meet constraints. N - No. Do not scale orders to meet constraints.

Determines the scaling constraint level when scaling orders for the supplier or supplier/department. Valid values include: O - Order level. Scaling constraints apply to the entire order. L - Location level. Scaling constraints apply to each location on the order.

Determines if the minimum scaling constraint or the maximum scaling constraint should be used as the objective when scaling the order for the supplier or supplier/department. This applies to both scaling constraints. Valid values include: M - Minimum. Scaling objective is the minimum scaling constraint. For example, if the minimum scaling constraint is 20,000lbs and the maximum scaling constraint is 40,000lbs, orders under 20,000lbs would be scaled to at least 20,000lbs. X - Maximum. Scaling objective is the maximum scaling constraint. For example, if the minimum scaling constraint is 20,000lbs and the maximum scaling constraint is 40,000lbs, orders under 40,000lbs would be scaled to 40,000lbs.

The type of the supplier or supplier/departments primary constraint. Valid values include: A - Amount (ex. $US) M - Mass (ex. kilograms) V - Volume (ex. cubic feet) P - Pallets C - Case E - Each S = Stat Case

The primary constraints unit of measure. For example, if the constraint type is Mass, units of measure may include KG (kilograms), LBS (pounds), etc.

The primary constraints currency if Amount is selected as the constraint type. For example, if the constraint type is Amount, the currency field may contain USD (US dollars). This field will always match the orders currency

The value of the primary minimum scaling constraint.

The value of the primary maximum scaling constraint.

The value of the primary minimum scaling constraints tolerance. Defined as a percentage. For example, if the minimum value was 20,000lbs and the tolerance was 5%, the acceptable minimum value can be down to 19,000lbs.

The value of the suppliers primary maximum scaling constraints tolerance. Defined as a percentage. For example, if the maximum value was 40,000lbs and the tolerance was 5%, the maximum value can be up to 42,000lbs.

The type of the supplier or supplier/departments second constraint. Valid values include: A - Amount (ex. $US) M - Mass (ex. kilograms) V - Volume (ex. cubic feet) P - Pallets C - Case E - Each S = Stat Case

The second constraints unit of measure. For example, if the constraint type is Mass, units of measure may include KG (kilograms), LBS (pounds), etc.

The second constraints currency if Amount is selected as the constraint type. For example, if the constraint type is Amount, the currency field may contain USD (US dollars). This field will always match the orders currency

The value of the second minimum scaling constraint.

The value of the second maximum scaling constraint.

The value of the second minimum scaling constraints tolerance. Defined as a percentage. For example, if the minimum value was 20,000lbs and the tolerance was 5%, the minimum value can be down to 19,000lbs.

The value of the second maximum scaling constraints tolerance. Defined as a percentage. For example, if the maximum value was 40,000lbs and the tolerance was 5%, the minimum value can be up to 42,000lbs.

Indicator to determine if the user has changed any scaling constraint information for the order. This indicator is used to determine if the user should be warned that they should re-scale the order because scaling parameters have changed during the order submittal and approval process. Once the order has been re-scaled, this indicator will be reset to No. Valid values include: Y - Yes. Scaling constraint parameters have been changed. N - No. Scaling constraint parameters have not been changed.

Determines the maximum number of iterations the constraint scaling process should perform when attempting to find a valid solution for the order before the process should stop. This is meant to prevent lengthy or run-away scaling processes.

Determines the level at which the supplier or supplier/departments minimums are applied to an order. Valid values include: O - Order level. Minimum constraints apply to the entire order. L - Location level. Minimum constraints apply to each location on the order.

Min_cnstr_conjAddVC(6)YA, OIf 2 minimum constraints have been specified, determines the relationship between the two. Valid values include: A - And. Both minimum constraints have to be met for the order to be valid. O - Or. Only one of the two constraints has to be met for the order to be valid.

The type of the supplier or supplier/departments primary minimum constraint. Valid values include: A - Amount (ex. $US) M - Mass (ex. kilograms) V - Volume (ex. cubic feet) P - Pallets C - Case E = Each S = Stat Case

The primary minimum constraints unit of measure. For example, if the constraint type is Mass, units of measure may include KG (kilograms), LBS (pounds), etc.

The primary minimum constraints currency if Amount is selected as the constraint type. For example, if the constraint type is Amount, the currency field may contain USD (US dollars). This field will always match the orders currency

The value of the primary minimum constraint.

The type of the supplier or supplier/departments second minimum constraint. Valid values include: A - Amount (ex. $US) M - Mass (ex. kilograms) V - Volume (ex. cubic feet) P - Pallets C - Case E - Each S = Stat Case

The second minimum constraints unit of measure. For example, if the constraint type is Mass, units of measure may include KG (kilograms), LBS (pounds), etc.

The second minimum constraints currency if Amount is selected as the constraint type. For example, if the constraint type is Amount, the currency field may contain USD (US dollars). This field will always match the orders currency

The value of the second minimum constraint.

This column will only apply to replenishment generated orders. It will indicate whether replenishment automatically splits this order. Valid values are Yes and No.

This column will hold the truck splitting method for the order. Valid values include Item Sequence or Balanced Assortment. The Item Sequence truck splitting method simply places items onto trucks in order of the items numbers. The Balanced Assortment truck splitting method attempts to place some of each item ordered onto each truck.

This column will hold the constraint type for the truck constraint 1. Valid values include Mass, Volume, Pallet, Case, Each, and Stat Case.

This column will store a Unit of Measure if truck constraint type 1 is either Mass or Volume - i.e. kg, lbs, FT3, etc.

This column will store the value of truck constraint 1. For example, a constraint type may be mass with a UOM of pounds. The value column could then be 3000 which would mean 3000lbs.

This column will define the absolute maximum value for a truck. For example, if the constraint is 40,000 lbs and the tolerance is 10%, the absolute maximum weight the truck can carry will be 44,000 lbs.

This column will hold the constraint type for the truck constraint 2. Valid values include Mass, Volume, Pallet, Case, Each, and Stat Case.

This column will store a Unit of Measure if truck constraint type 2 is either Mass or Volume - i.e. kg, lbs, FT3, etc.

This column will store the value of truck constraint 2. For example, a constraint type may be mass with a UOM of pounds. The value column could then be 3000 which would mean 3000lbs.

This column will define the absolute maximum value for a truck. For example, if the constraint is 40,000 lbs and the tolerance is 10%, the absolute maximum weight the truck can carry will be 44,000 lbs.

This column will indicate if less-than-truckload (LTL) orders that are created during the truck splitting process will be valid for automatic approval. If set to Yes, LTL orders will be auto-approved, if they meet all other approval criteria, for example, vendor minimums. If set to No, LTL orders will not be auto-approved even if they meet all other approval criteria. This column will only be used for reference purposes by the automatic replenishment approval module to determine if the order can be auto- approved.

This column will indicate if the split order is a less-than-truckload (LTL) order. This column will only be used for reference purposes by the automatic replenishment approval module to determine if the order can be auto-approved.

Indicator used to determine if Due Order Processing will be used when building the order. This indicator will only be used for replenishment orders. Valid values include: Y - Yes. Due order processing will be used. N - No. Due order processing will not be used.

Indicator used to determine if Due Order Processing will be used when creating orders for the supplier or supplier/department. This indicator will only be used for replenishment orders. Valid values include: Y - Yes. Due order processing will be used. N - No. Due order processing will not be used.

Determines the level at which Due purchase orders for the supplier or supplier/department are determined. This field is only used for replenishment orders. Valid values include: I - Item level. If any item/location on the order is Due, the entire order will be considered Due. O - Order level. The entire order is Due only if the summed estimated stock out amount (ESO) across all item/locations on the order is greater than the summed accepted stock out amount (ASO) across all item/locations on the order.

Determines whether the safety stock comparisons for Due order determination should be performed in units (standard unit of measures) or currency (ex. $US). Only be used for replenishment orders when the Due Order Indicator is set to Yes. Valid values include: C - Currency based service levels. Safety stock amounts are calculated as the safety stock in units multiplied by the items cost. U - Unit based service levels. Safety stock amounts calculated in units (standard unit of measures).

Indicator used to determine if an order should be scaled to one or multiple vehicles. This indicator is used for both replenishment and manual orders. Valid values include: Y - Yes. Order will be scaled to multiple vehicles. N - No. Order will be scaled to one vehicle.

Contains the number of vehicles required for the order. This field is used only when order constraint scaling is used.

Indicator used to determines if orders created by replenishment should be limited to one location. This indicator is only used in the replenishment order build process. Valid values include: Y - Yes. Orders should be split by location. N - No. Orders can have multiple locations.

Indicator used to determine if orders not meeting the supplier minimum constraints should be purged or created in worksheet status during the replenishment order build process. This field is on this table due to performance reasons for the rplbld.pc program. Valid values are: Y- Yes. Purge orders not meeting supplier minimum constraints. N- No. Create orders in Worksheet status.

This field is used to determine if the order was created in the replenishment process with the intention of being approved during the order approval validation process. This indicator is also used by the scaling and truck splitting modules to identify the orders to be processed (only orders that are going to be approved are processed).

This field will contain the ID for a pooled supplier if the order was created as a pooled order for logistical purposes.

This field will contain an ID that will be used to link orders together for logistical purposes.

Description of any issues that were encountered during the order scaling process.

This column will be populated by the Truck Splitting process if it encountered any problems while splitting the order.