Client Settings
Term | Description |
Company | The client. |
Facility | The SEKO warehouse(s) the client is located in. |
Tenant | SEKO |
User Settings
Term | Description |
Department | The user will be assigned to one of the following departments: Corporate/IT, Receiving, Inventory Controls, Outbound, Returns |
Team Member ID | Username used to login to JASCI software, this field should be the SEKO alias ID. |
Profile Assignments | Menu options JASCI users are given access to. |
Authority | |
Authority ID: Analytics | |
Authority ID: Change Status | |
Authority ID: Cycle Count | Level 1: [Update, this is configurable] Level 2: Level 3: |
Authority ID: Inventory | |
Authority ID: KitRequest | |
Authority ID: MUL |
Location Definitions
Term | Description |
AREA | Governs first priority for sequencing, slotting, or allocation based on the work type assignment.
|
Location Types | Governs what type of UOM can be slotted into the location and/or what UOM can be allocated from the location.
|
Receiving
Term | Description |
ASN Receiving | Advance Shipment Notification, gives prior knowledge on product(s) and quantity expected in the inbound shipment. (e.g similar to a packing slip) |
Build Pallet | |
Dock Jockey | |
Domestic Receiving | |
Plotting |
|
QR Receiving | |
Shipment ID | Container number, PO number, etc. |
Work Control Number | |
Work Bench | A virtual “station” that represents a physical station for a specific task. The virtual station will systematically capture all actions/task that were physically preformed. (e.g an inbound staging area, picking station, packing station, outbound staging area) |
Outbound
Term | Description |
CUT | Allows an operator to skip any missing product(s) from a sales order line and will do one of two processes:
|
Cart | A virtual and physical cart used for picking. The cart will be systematically assigned either discrete or singles sales orders. An operator will need to scan (check out) the cart to begin picking the assigned sales orders. |
Cart Slots | A bin within the cart, an LPN will be assigned per bin. (e.g a cart with 20 slots (AKA 20 bins) will have 20 different LPNs) |
Cluster Pick | Picking several different sales orders at a time. (e.g wave picking) |
Discrete Pick | Picking one sales order at a time. |
Product | SKU |
Singles Picking | Sales orders that only contain one order line and one unit can be clustered or discrete pick. |
Slots | Bin Locations, pick phases, etc. |
Suspended Cart | A cart that is currently checked out by a different operator. |
Tote | Similar to a cart slots but instead you of transferring all picked product(s) into different slots the operator will transfer all picked product(s) into one tote. This is usually used for singles picking. |
Work Bench | A virtual “station” that represents a physical station for a specific task. The virtual station will systematically capture all actions/task that were physically preformed. (e.g an inbound staging area, picking station, packing station, outbound staging area) |
Work Zone | A zone of warehouse locations in one area. (e.g Zone A has warehouse locations 00001 - 00020, Zone B has warehouse locations 00021 - 00040) |
Trouble Orders | Orders that were not successfully fulfilled. |
Kitting
Term | Description |
KIT | A KIT is an internal work order(s) that are pick and packed (pre-built) prior to the end consumer's request. Child products will be picked and brought to a common area where they will be packaged to produce the final parent product and putaway. |
Parent Product (KIT) | A parent product requires several different products (i.e child products) to be assembled in order to create a final product. (e.g Product ‘12345’ needs the following SKUS and QTYs: SKU001(QTY:1), SKU002(QTY:1), SKU003(QTY:1). The parent product would be ‘12345'.) |
Child Product (KIT) | Individual component(s) that make up the parent product. (e.g Kit ‘12345’ needs the following SKUS and QTYs: SKU001(QTY:1), SKU002(QTY:1), SKU003(QTY:1). The child product(s) would be the listed SKUs.) |
SET | A SET will auto-generate (explode) upon end consumer's request. If a sales order contains all SKUs and QTYs needed to create a parent product, JASCI will recognize this. This is not pre-built and will require assembly. |
Parent Product (SET) | A parent product requires several different products (i.e child products) to be assembled in order to create a final product. (e.g Product ‘12345’ needs the following SKUS and QTYs: SKU001(QTY:1), SKU002(QTY:1), SKU003(QTY:1). The parent product would be ‘12345'.) |
Child Product (SET) | Individual component(s) that make up the parent product. (e.g Kit ‘12345’ needs the following SKUS and QTYs: SKU001(QTY:1), SKU002(QTY:1), SKU003(QTY:1). The child product(s) would be the listed SKUs.) |
Explode (SET) | JASCI recognizing a parent product based off the requested child products. that were initial requested. |
Inventory Control
Term | Description |
CUT | |
Product Master | Material master, item list, product list, etc. |
Reason Code | Different codes that explain why a unit was adjusted out of actual inventory. |
Material Master
Term | Description |
Data Mapper | A JASCI tool used to set manual clients up or for mass item/order imports. |
Accounting Code | |
Description Short | The product name, 20 characters max. |
Description Long | The product description, 50 characters max. |
Product | The product SKU. |
Quality |