Displays the allocated quantity to be added to the Available balance for an Inventory Lot or Item. This is a calculated field and not stored in the database.

The Allocated (+) balance is the quantity, that has been allocated, on an open transaction containing incoming product. The Allocated (+) balance increases the Available balance. Unlike Committed (+) which represents "requested" balances, Allocated (+) represents "assigned" balances. For example, a Customer may order 15 Cases and only be shipped 10. The 10 Cases would signify what was actually shipped. The Allocated (+) balance is comprised of:

• Inventory transactions where the quantity of a Lot Tracked line item where the item has been saved with a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on a Receipt line item and either the Production Batch or Warehouse Lot was assigned, the Allocated (+) balance for that transaction would be 10.
• Production Orders where the quantity of an Output line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on the transaction and either the Production Batch or Warehouse Lot was unassigned, the Allocated (+) balance for that transaction would be 10.
• Sales Returns where the line item has an allocated quantity.

Note: each of the Inventory Transactions can be conditionally included/excluded from the Allocated balances based on the "Include open ### transactions in Available balances" Inventory Preference. If the preference are set to "Yes", they will be included in Allocated balances and used to update the Available balances, if they are set to "No", they will not be included in Allocated so they will not update Available balances.

Additionally, for Production Order Outputs, these can be conditionally included/excluded from the Allocated balances based on the "First status to include Production Order Outputs in Available balances" Inventory Preference. If the transaction is set to a status equal to or greater than the Preference value, and is not in a status of Closed and not set to "Do Not Include", it will be included in Allocated balances and used to update the Available balances, otherwise if the status is set to a value less than the Preference value, it will not be included in Allocated so they will not update Available balances. 

Displays the allocated quantity to be subtracted from the Available balance for an Inventory Lot or Item. This is a calculated field and not stored in the database.

The Allocated (-) balance is the quantity, that has been allocated, on an open transaction containing outgoing product. The Allocated (-) balance reduces the Available balance. Unlike Committed (-) which represents "requested" demand on product, Allocated (-) represents the quantity that has been "assigned" and has/will ship. For example, if a Customer orders 15 cases and only 10 are allocated, the Available balance will be reduced by 15 made up of Allocated (-) of 10 cases and Committed (-) of 5 cases.  The Allocated (-) balance is comprised of:

• Inventory transactions where the quantity of a Lot Tracked line item where the item has been saved with a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on a Production Input line item and either the Production Batch or Warehouse Lot was assigned, the Allocated (-) balance for that transaction would be 10.
• Production Orders where the quantity of an Input line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on the transaction and either the Production Batch or Warehouse Lot was unassigned, the Allocated (-) balance for that transaction would be 10.
• Sales Transactions where a line item has been allocated. 

Note: Each of the Inventory Transactions can be conditionally included/excluded from the Allocated balances based on the "Include open ### transactions in Available balances" Inventory Preference. If the preference are set to "Yes", they will be included in Allocated balances and used to update the Available balances, if they are set to "No", they will not be included in Allocated so they will not update Available balances.

Additionally, for Production Order Inputs, these can be conditionally included/excluded from the Allocated balances based on the "First status to include Production Order Inputs in Available balances" Inventory Preference. If the transaction is set to a status equal to or greater than the Preference value, and is not in a status of Closed and not set to "Do Not Include", it will be included in Allocated balances and used to update the Available balances, otherwise if the status is set to a value less than the Preference value, it will not be included in Allocated so they will not update Available balances. 

Displays the batch comment assigned to the corresponding Production Batch. This field defaults as blank. This can be edited from the 'Batch Comment' field on the Properties tab of the Production Batch record view.

Database Field: ERPx_IMProductionLot.LotComment

Identifies the Site where the Production Batch was born, created, or initially received. This value defaults from the 'Site' selected on the Inventory transaction that created the Production Batch. This can be edited from the 'Production Batch Site' field on the Properties tab of the Production Batch record view.

Database Field: ERPx_IMProductionLot.ManufactureSiteSK

Identifies the name of user that closed the Lot. It is formatted to be the "logged-in" users [User First Name] + [User Last Name]. This is a system assigned value and is never editable by a user.

Database Field: ERPx_IMLotBalance.ClosedBy

Identifies the date that lot was closed, formatted from the users 'Date Format' preference. This is a system assigned value and is never editable by a user.

Database Field: ERPx_IMLotBalance.ClosedDateTime

Displays the requested quantity to be added to the Available balance for an Inventory Lot or Item. This is a calculated field and not stored in the database.

The Committed (+) balance is the ordered (requested) quantity, that has not yet been allocated, on an open transaction containing incoming product. The Committed (+) balance increases the Available balance. The Committed (+) balance is comprised of:

• Inventory transactions where the quantity of a line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on a Receipt line item and either the Production Batch or Warehouse Lot was unassigned, the Committed (+) balance for that transaction would be 10.
• Open Production Orders where the quantity of an Output line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on the transaction and either the Production Batch or Warehouse Lot was unassigned, the Committed (+) balance for that transaction would be 10.
• Open Purchase Orders where the quantity of an inventory item has been saved and not yet received (on a Posted Receipt transaction). For example, if the inventory item on the Purchase Order is for 100lbs and has not yet been received, the Committed (+) balance for that item would be 100lbs.  If a Receipt is then Posted with 60lbs of that item, the Committed (+) balance would be 40lbs. 
• Sales Returns: Items on Sales Order Shipments, where the Requested Returned quantity is greater than the Allocated quantity. When this occurs, it is calculated as [Requested] - [Allocated]. For example, if 15 Cases were being returned and 3 have been allocated, the Committed (+) balance would be 12. Note, this amount cannot be negative. For example, if there were 5 Cases requested for return and 7 Allocated, the Committed (+) balance would be 0 not -2.

Note: Each of the Inventory Transactions can be conditionally included/excluded from the Committed balances based on the "Include open ### transactions in Available balances" Inventory Preference. If the preference are set to "Yes", they will be included in Committed balances and used to update the Available balances, if they are set to "No", they will not be included in Committed so they will not update Available balances.

Additionally, for Production Order Outputs and unreceived Purchase Order quantities, these can be conditionally included/excluded from the Committed balances based on the "First status to include ##### in Available balances" Inventory Preferences. If the transaction is set to a status equal to or greater than the Preference value, and is not in a status of Closed and not set to "Do Not Include", they will be included in Committed balances and used to update the Available balances, otherwise if the status is set to a value less than the Preference value, they will not be included in Committed so they will not update Available balances. 

Displays the requested quantity to be subtracted from the Available balance for an Inventory Lot or Item. This is a calculated field and not stored in the database.

The Committed (-) balance is the ordered (requested) quantity, that has not yet been allocated, on an open transaction containing outgoing product. The Committed (-) balance reduces the Available balance. The Committed (-) balance is comprised of:

• Inventory transactions: where the quantity of a Lot Tracked line item where the item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on a Production Input line item and either the Production Batch or Warehouse Lot was unassigned, the Committed (-) balance for that transaction would be 10.
• Open Production Orders where the quantity of an Input line item has been saved without a Production Batch and/or Warehouse Lot (if the Site is Warehouse Lot tracked). For example, if 10 Cases were entered on the transaction and either the Production Batch or Warehouse Lot was unassigned, the Committed (-) balance for that transaction would be 10.
• Open Purchase Orders where a negative quantity of an inventory item has been saved and not yet received (on a Posted Receipt transaction). For example, if the inventory item on the Purchase Order is for -100lbs and has not yet been received, the Committed (-) balance for that item would be -100lbs.  If a Receipt is then Posted with -60lbs of that item, the Committed (-) balance would be -40lbs.
• Sales Transactions: Items on Sales Order Shipments, where the Shipment has not been Shipped, where the Ordered quantity is greater than the Allocated quantity. When this occurs, it is calculated as [Ordered] - [Allocated]. For example, if 15 Cases were ordered and 3 have been allocated, the Committed (-) balance would be 12. Note, this amount cannot be negative. For example, if there were 5 Cases ordered and 7 Allocated, the Committed (-) balance would be 0 not -2.

Note: Each Inventory Transaction can be conditionally included/excluded from the Committed balances based on the "Include open ### transactions in Available balances" Inventory Preference. If the preference are set to "Yes", they will be included in Committed balances and used to update the Available balances, if they are set to "No", they will not be included in Committed so they will not update Available balances.

Additionally, for Production Order Inputs, these can be conditionally included/excluded from the Committed balances based on the "First status to include Production Order Inputs in Available balances" Inventory Preference. If the transaction is set to a status equal to or greater than the Preference value, and is not in a status of Closed and not set to "Do Not Include", it will be included in Committed balances and used to update the Available balances, otherwise if the status is set to a value less than the Preference value, it will not be included in Committed so they will not update Available balances. 

Identifies the unit of measure the item's cost is stated in terms of. This is the value assigned in the "Cost UOM" property on the Item Record View.

Database Field: ERPx_IMItem.CostUOMSK

Displays the calculated age (in days) of the Production Batch. It is calculated as the (Current Date) - [Batch Date]. This can be edited by changing the 'Batch Date' field on the Properties tab of the Production Batch record view. This is not stored in the database.

Displays the name of the Hold Code placed on the lot. This defaults as blank and can be edited by setting the 'Hold Code' field on the Mass Update dialog box launched from the Lot Balances Inquiry list view.

Hold Codes are used to prevent a process from being performed or a transaction from being posted.

Database Field: ERPx_IMLotBalanceHold.HoldCodeSK where ERPx_IMLotBalance.LotSK = ERPx_IMLotBalanceHold.LotSK

Identifies if a Lot is expired.

• This will display as "Yes" For Lots with a 'Batch Expiration Date' that is <= the current date.
• This will display as blank for Lots without a 'Batch Expiration Date' or for Lots with a 'Batch Expiration Date' that is >= the current date. 

Displays whether the Inventory Lot is Open or Closed. Displays "Closed" if the Lot has been closed or blank if the Lot is open. When created, inventory lots default as open. This can be edited by setting the 'Lot Status' field on the Mass Update dialog box launched from the Lot Balances Inquiry list view.

Database Field: ERPx_IMLotBalance.StatusSK

Displays the Market Cost assigned to the item or lot. This is the Market base cost when the the Source is Base and Market layer cost when the source is Layer.

The Market Cost reflects the estimated "market" value for the inventory. Market Costs are typically set by taking Actual costs and adding additional components such as delivered freight, brokerage/rebate amounts, and desired profit margin. For each individual LotSK, this is calculated as the [Market Base Cost Rate] + sum of all the [Market Cost Layer Rates]. 

Market Costs are typically maintained in companies where costs and/or margin needs to be shown/used in Sales Order based on the current market value of the item, not the Actual costs.

Database Field: ERPx_IMItem.MarketCost

Displays the On Hold balance of an item or Inventory Lot, stated in terms of the Item's "Reporting UOM". If the Item' Reporting UOM is "Lbs" then this would represent the On Hold Lbs. If the Item' Reporting UOM is "Case" then this would represent the On Hold Cases. When a lot is placed On Hold, the On Hold balance is taken from the Available balance. The On Hold balance is increased by the entire lot's On Hand balance (not the item's On Hand balance). The On Hold balance is decreased when the lot is removed from on hold and the amount is added back to the Available balance. This is a calculated field and not stored in the database.

The On Hold balance reflects the On Hand balance of an Inventory Lot with a Hold Code assigned, provided the 'On Hand' balance is > 0.00. For example, if the 'On Hand' balance of an Inventory Lot is 10.00 Lbs and the Lot is put on Hold, then the 'On Hold' balance will be 10 Lbs. If the 'On Hand' balance of an Inventory Lot is -30.00 Lbs and the Lot is put on Hold, then the 'On Hold' balance would be 0.00 Lbs (because the Lot balance was <= 0.00). On Hold balances are updated when a Hold Code is assigned or removed from an Inventory Lot. Hold Codes can be assigned to any Inventory Lot and the On Hold balances always reduce the Available balance.

Inventory Lots that are On Hold cannot be allocated to a sales transaction, unless done so by a user that is assigned in the 'Can Override' property on the Hold Code, and they cannot be allocated to any inventory transaction. An Inventory Lot can only have a single Hold Code applied at any given time.

Displays the allocate