|
|
General Information (In the top section of the screen)
|
Name
|
The name for the activity line manager. This is required and must be unique.
|
Description
|
The activity line manager description.
|
Criteria
|
Line #
|
Auto-generated ID for the view.
|
Name
|
The name of the activity line manager criteria being used to gather the activity lines for the manager.
|
Description
|
The description of the activity line manager criteria.
|
|
Fields available when viewing activity line managers
|
Broker
|
The name of the business affiliate Broker, from the document header.
|
Business Process
|
The overall direction (relative to the warehouse) of the business process in which the activity line is involved.
Inbound lines include purchase orders, receipts, kit order products and by-products, kit products and by-products, adjustments, cycle counts, voided shipment items (if the line was marked Return to Inventory)Outbound lines include sales orders, shipments, pack plans, bills of lading, pick plans, pick tickets, kit order products (if the kit specification is for disassembly) and components, kit products (if the kit specification is for disassembly) and components, adjustments, cycle counts, rejected picks (if the line was marked Remove from Inventory)No effect lines include bin transfers, license edits, storage, edit documents, voided shipment items (if the line was not marked Return to Inventory), rejected picks (if the line was not marked Remove from Inventory).
Known Issue: For adjustments and cycle counts, the Qty on the activity line is not the amount that was brought into inventory or removed from inventory. The Qty is the result of the transaction on the line. For example: for adjustments, the Qty is the New Qty (not the increase or decrease from the Current Qty); for cycle counts, the Qty is the Counted Qty (not the increase or decrease from the Previous Qty).
|
Carrier
|
The name of the business affiliate Carrier, from the document header.
|
Complete date
|
The date the activity was completed in the system. From the document header.
|
Created by
|
The username of the user who created the activity. From the document header.
|
Cube
|
The cube or volume used in this warehouse operation, based on the Qty of the line. From the activity line.
|
Customer
|
The name of the business affiliate Customer, from the document header.
|
Date created
|
The date the system created the activity. From the document header.
|
Description
|
The description of the Item # from the item master. From the activity line.
|
Dim Wt
|
The dimensional weight used in this warehouse operation, based on the Qty of the line. From the activity line.
|
Document #
|
The unique identifier for this document, generated by SmartTurn when the document is created in the system. For example: SI-000001, RCPT-000287, ADJ-000015.
|
Document Type
|
The kind of SmartTurn document this activity line is from: Adjustment, Bill of Lading, Bin Transfer, Cycle Count, Inventory Edit, Kit Order, Kit, License Edit, Pack Plan, Pick Plan, Pick Ticket, Purchase Order, Receipt, Sales Order, Shipment, Storage.
|
Due date
|
The date the activity is due to be completed. From the document header.
|
Item #
|
The item master number. From the activity line.
|
Item Status
|
The status of the activity line: Saved, Approved, Started, In Progress, Ready, Closed, Cancelled, Committed, Consumed.
|
Line #
|
The document line number. From the activity line.
|
Line Type
|
The type of line item. Only applicable:
- when the Document Type is
Kit Order or Kit (used to distinguish products, by-products, and components) - OR
- when the Document Type is
Pick Ticket (used to distinguish pick ticket items and rejected picks) or Shipment (used to distinguish shipment items and voided shipment items). Rejected picks and voided shipment items have a Line Type of Anomaly Item.
|
Lot #
|
The lot number assigned to the item. From the activity line.
|
Owner
|
The name of the business affiliate Owner, from the document header.
|
Pallets
|
The number of pallets used in this warehouse operation, based on the Qty of the line. From the activity line.
|
Priority
|
The priority for the activity. From the document header.
|
Product ID
|
The Item number that the Vendor for this product uses. From the activity line.
|
Qty
|
The amount of goods being processed on the line.
- For adjustments, this is the New Qty.
- For bills of lading, this is
the Qty to Pack before the item has started being picked
the Qty Avail to Pack as the item is being picked and delivered to the packing station
the Qty Packed once the item is Closed and has left the warehouse.
- For bin transfers, this is the Transfer Qty.
- For cycle counts, this is the Counted Qty.
- For inventory edits, this is the Edited Qty.
- For kit orders, this is the Ordered Qty.
- For kits,
for products and by-products, this is the Produced Qty.
for components, this is the Qty Pulled.
- For license edits, this is the Licensed Qty.
- For pack plans, this is the Qty to Pack.
- For pick plans, this is the Qty to Pick.
- For pick tickets, this is the Qty Picked.
- For rejected picks, this is the Qty Rejected.
- For purchase orders, this is the Ordered Qty.
- For receipts, this is the Received Qty.
- For sales orders, this is the Ordered Qty.
- For shipments, this is the Qty Shipped.
- For voided shipment items, this is the Qty Voided.
- For storage, this is the Qty on Hand.
|
Scheduled date
|
The date the activity is scheduled to be completed. From the document header.
|
Serial #
|
The serial number assigned to the item. From the activity line.
|
Total cost
|
The total cost or value of the activity line. Calculated by multiplying the cost of the inventory item associated with this activity by the Qty of the line.
(For outbound processes -- for example, sales orders -- the cost is the purchase cost from the item master.)
|
Total price
|
The total price of the activity line. Calculated by multiplying the price or user-overridden price by the Qty of the line.
(For inbound processes -- for example, purchase orders -- the price is from the sales price from the item master.)
|
Transaction date
|
The actual date that the warehouse operation took place. From the document header.
- On Adjustments, Bin Transfers, Cycle Counts, Edit Documents, License Number Edits, Pick Plans, and Pick Tickets this is called the Transaction date.
- On Purchase Orders, it is called the PO Date.
- On Sales Orders, it is called the SO Date.
- On Receipts, it is called the Receipt Date.
- On Shipments, it is called the Shipment Date.
- On Bills of Lading, it is called the Date.
- On Kit Orders, it is called the Kit Order Date.
- On Kits, it is called the Kit Date.
- On Storage Documents, it is called the Items in Storage As Of date.
|
Vendor
|
The name of the business affiliate Vendor, from the document header.
|
Warehouse
|
The warehouse in which the operation took place. From the document header.
|
Wave #
|
Alphanumeric ID for this set of work, generated for the system when this set of work is initiated. Unique in the tenant. From the document header.
All documents involved in fulfilling this set of work have the same Wave #. For a batch of shipments, this includes: the sales orders and the shipments. or a , this includes: the sales orders, the pick plan, and the pick tickets. For a , this includes: the sales orders, the pack plan, the bills of lading, the pick plan, and the pick tickets.
|