LC - Liquor Control
LC applications are used in the Warehouse Management System for monitoring and performing tasks related to the receiving, storage and distribution of (government-regulated) alcohol inventory.
3PL warehouse operations that receive and ship alcohol products are required by the government to report on the status of these products. Government agencies involved with liquor control will usually need to ensure that, when a warehouse ships these products, the tax has either been paid or will be paid based on what has been shipped.
The level of detail required for government reporting can vary, but it will usually include the following: client, tax status, alcohol content, product code, ship-to name, and quantities. For auditing purposes, warehouses should be able to show (at the transaction level) what tax status inventory has been received or shipped out, and what inventory is on hand.
On handling liquor at the warehouse:
- It is possible for a warehouse to co-mingle tax paid and non-tax paid liquor at their site; however, each stock location should be restricted to a single tax status (either all paid or all unpaid, but not both). For example, location 001 can have tax paid inventory, location 002 tax unpaid, location 003 tax paid etc.
- Orders are not placed based on tax status. The tax status would be invisible on the Bill of Lading and to the ShipTo / Consignee.
- Inventory can change occasionally from tax unpaid to tax paid, while still in the warehouse.
|
|
|
.png)
.png){kind=small}
To walk through a series of integrated workflows relating to Liquor Control setups and processes , click Liquor Control Applications
LC applications allow additional information to be tracked relating to the requirements of these types of goods (described above). Beginning with the receipt of inbound inventory, information such as the tax status, generic code (to identify alcohol content), and the total quantity (equivalent gallons, barrels, liters, etc.) is recorded at the receipt line level. These essential elements of information continue to be tracked as activities are performed on the inventory.
LC05- Transaction Maintenance
The Liquor Control - Transaction Maintenance application provides access to the information relating to each Liquor Control transaction in the WMS. This information can also be accessed via the Liquor Control Action Grid (below).
LC30 - Alcohol Categories
The Alcohol Categories - Maintenance application is used to add and change the Generic Codes and Categories associated with the various alcohol types and alcohol content of the inventory being tracked.
Liquor Control Action Grid
The transaction information for Liquor Control inventory can be accessed and acted upon via the Liquor Control action grid in the WMS WiP HighView:
ž
Each row (record) in this action grid represents a unique Liquor Control transaction. For information on data elements provided in this action grid, see Liquor Control Action Grid. To view and/or change the details of a Liquor Control transaction, select the associated record/row in the action grid, then click the .png){kind=small}
button. This opens the Liquor Control Maintenance job.
How-To ...
The following sections outline what is involved in setting up the LC applications, processing transactions, and generating related documentation.
Setups
The Liquor Control Subsystem activation (LC.99) includes the following actions:
- Use System? (Y/N)
Alcohol Categories (LC.30) - Revise Field # 1 so the Category Code MUST be a valid/existing Generic Code (i.e., in CR.32)
Client (CR.06) - Record transaction quantities for Liquor Control Reporting? (Y/N)
Customer (CR.26) - Record transaction quantities for Liquor Control Reporting? (Y/N)
- Do we need this configuration?
Product (CR.62) - Record transaction quantities (i.e. Receipts/Orders) for this Product in the Liquor Control System (Y/N)
- Alternate SKU for Liquor Control Reporting
Select the Measuring Unit Code (i.e. from CR.10 – e.g. “GAL” = Gallons, or “BRL” = Barrels) for Liquor Control Reporting
Enter the Conversion Quantity (e.g., 1.118095 – six decimal places) used to calculate the Liquor Control Reporting Measuring Unit (e.g. a Gallon) from the Product’s Standard SKU (i.e., Field # 10 – e.g. a Case of 6-750 ml Bottles)
Lot Component (WP.43) - New System defined Lot Component to determine whether the Excise Tax has been paid for the Lot of Liquor
- The System defined Lot Component will be *LTP* Liquor Tax Paid and will have either a “Y” or “N” value
Lotting Assignments (WP.46) - Warn the Operator if they attempt to attach a Lot Set to a Client or Product that has been configured to use Liquor Control Reporting BUT the Lot Set does NOT contain the Liquor Control Tax Paid Lot Component (i.e. *LTP*)
Inbounds/Order Entry
Whether a Client will be “Bond” or “Tax Paid” is defined in various inbound/receiving implementations including:
- In-Transit Receipts (RE.11)
- Receipts (RE.21)
- Receipt Invoices (RE.31)
- RF Stock Handling (RF.01)
Outbounds /Bill of Lading
Inventory that is flagged with Generic Code and Alcohol Category information may need to have this summarized to be included on a Bill of Lading:
- Enter Orders - Shipping (OE.01)
- Print Shipping Documents (OE.03)
- Confirm or Modify Shipments (OE.20)
Was this article helpful?
Give feedback about this article