Inventory and Call Off
From UG
(Difference between revisions)
(→ASN) |
(→SOW 4 Purchase Order upload) |
||
Line 150: | Line 150: | ||
'''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4437 '''4437'''] | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4437 '''4437'''] | ||
- | * This feature provides | + | * This feature provides an uploading of PO information into the ASN Portal. |
* Information comes via e-mail. New accounts for incoming email were created: | * Information comes via e-mail. New accounts for incoming email were created: | ||
:* Production environment: upload@jaguarfreight.com | :* Production environment: upload@jaguarfreight.com |
Revision as of 14:11, 9 June 2014
About
Mantis:
- Parent: 0004392
- Category: ASN: Inventory and Call Off
Business Info
Definitions
- Inventory - Supplier's information about items ready to ship.
- Per Marc, Inventory is a quantity of items related to a purchase order that are "manufactured" and "ready" at a supplier's warehouse.
- This is Portal-specific data
- 1 "Inventory Record" = unique PO / SKU combination
- Inventory can be "replenished". This means the supplier can add more quantities at any point in time.
- Call Off - Action of a Planner with "Call Off" rights to request/reserve some quantity of the PO from Inventory.
- Per Marc, Planner users can select a quantity from "Inventory" and ask the supplier to create an ASN for that "Quantity".
- Pending Call Off
- Inventory Shipper
- Call Off Planner
Business Needs
- The simple way of auto-update a list of open POs
- Notify/filtering a due date status of PO (e-mail, DB reports)
- Provide visibility of Supplier inventory levels
- Create "Call Off" based on Inventory record
- Log call off request in inventory
- Create ASN from "Call Off"
- Analytics in Flashlight
Solution
Solution Summary
System should provide the following steps/processes:
- Open POs - Purchase Order upload per "PO Issued by"
- Inventory - Creating Inventory record by Supplier
- Call Off - Requesting quantity of PO by Planner
- Notifications and reports
Admin
- Add Inventory Shipper Role
- Add "Call Off" rights as option of Planner User
- Ability to enable/disable "Inventory and Call Off" feature in Portal
- Per Portal, manage a table of allowed Inventory Shippers by "PO issued by"
ASN
- ASN Inventory record contains the following fields:
- PO Issued By
- Release Number
- PO Number
- SKU
- Total PO Qty
- Shipper
- Item Description
- Ship To Location
- Origin Due Date
- Destination Due Date
- Mode Of Transport
- Piece Price
- Total Value
- Inventory tab
- Fields.
- Supplier
- Pick up Location
- PO #
- Item code
- Description
- Price
- PO Issued By
- Packaging?
- Ship to?
- Filters
- Controls
- Functions
- Call Off tab
- Fields
- Filters
- Controls
- Functions
Dashboard Reports
SOWs
SOW 1 Add Inventory Shipper Role
mantis: 4457
- This is a new kind of Shipper User Role and designed to let the Shipper to work in ASN Inventory.
- Inventory Shipper Role is implemented as an option of CT2 Generic Shipper User (managed in User Profile admin)).
- This user should be linked to one or more ASN Portals.
- It allows Shipper to work in Inventory with all or some "PO issued by" (managed in ASN Portal admin) - ???
- Inventory Shipper functions are:
- create Inventory record from open PO
- confirm cargo ready (available) date (?) and enter other fields (pallets, packaging, gross weight, dims, ship to)
- replenish Inventory record (add more quantities at any point in time)
- proceed "Call Off":
- open "Call Off" record
- confirm Cargo Ready Date
- updates all fields required (need validations)
- create ASN from "Call Off"
- NOTE: Allow item QTY changes! (???)
- close Inventory record (moving to another tab) - ???
SOW 2 Add "Call Off" rights as option of Planner User
mantis: 4458
- This is new option for CT2 Generic Planner user
- ...
SOW 3 Inventory and Call Off panel
mantis: 4459
- 2 new tabs in ASN2 shipment list are "Inventory" and "Call Off".
- They should to provide:
- Uploading the list of open POs by PO issued By Company (POIB)
- Showing Inventory information on Supplier's level. One PO per line.
- Call Off functionality on Planner's level
- Ability to create ASN from "Call Off" record
- "Inventory" and "Call Off" tabs should be managed to enable for Inventory Users from User Profile.
SOW 4 Purchase Order upload
mantis: 4437
- This feature provides an uploading of PO information into the ASN Portal.
- Information comes via e-mail. New accounts for incoming email were created:
- Production environment: upload@jaguarfreight.com
- All Dev environments: po.upload@gmail.com
- To upload Inventory PO list user have to send email to the given email address with following parameters:
- Subject must contain key phrase "PO Upload" and name of PO Issued By Company, separated by colon ":"
- e.g "PO Upload: CEI Roanoke"
- Excel file (Excel v 97-2003 xls only currently supported) should be attached to this email.
- The following columns in this XLS document (Gemline example) should be handled (others should be missed):
Name (mapping link) | XLS Column | XLS Name | Note/Example |
---|---|---|---|
PO Number (a.k.a Commodity PO) | A | Order No | Alphanumeric. Gemline example: 20296. |
PO Line | B | Line No | Gemline example: 2. |
Release # | C | Release No | Alphanumeric. Makes unique pair with PO Number. Multiple PO Numbers are allowed with different Release Number. Gemline example: 7. |
D (no mapped yet) | E | Supplier Name | Code. Gemline example: TCD. |
POIB | F | Buyer ID | Gemline example: GEM. |
PO Issue Date. NEW field | I | Created | Need to be added. Gemline example: 04/14/2014. |
SKU (a.k.a Commodity SKU) | J | Part No | Alphanumeric. Gemline example: 90301R1B. |
Description (a.k.a Commodity Item Description) | K | Part Description | Gemline example: ISAAC MIZRAHI AVA WRISTLET-NAVY. |
SKU QTY (a.k.a Commodity Item Qty) | M | Quantity | Numeric. Gemline example: 1500. |
Destination Due Date | N | Planned Receipt Date | Gemline example: 06/03/2014. |
Origin / Supplier Due Date | T | Wanted Delivery Date | Gemline example: 04/30/2014. |
MOT (a.k.a Transport Mode) | BR | Ship Via Code | ASN Portal Transport Mode. Gemline examples: OCN, AIR. |
Incoterms (FOB - location) | BU | Delivery Terms | Incoterms is FOB. See list of overseas ports (Location) under the table. Gemline example: SHA. |
HTS | CC | Tech Coordinator | Harmonized Tariff Schedule (of the United States). Gemline example: 4202.32.2000. |
- Location (a list of the overseas ports that Gemline is using, or sometimes/potentially could use):
- Code - Terms - Port
- CHG - FOB - Chittagong
- CLO - FOB - Colombo
- DJI - FOB - Djibouti
- FUZ - FOB - Fuzhou
- GUA - FOB - Guangzhou
- HCM - FOB - Ho Chi Minh City
- HK - FOB - Hong Kong
- KEE - FOB - Keelung
- NED - FOB - New Delhi
- NGB - FOB - NINGBO
- QIN - FOB - Qingdao
- SHA - FOB - Shanghai
- SHE - FOB - Shekou
- SHZ - FOB - Shenzhen
- SIH - FOB - Sihanoukville
- SRI - FOB - Sri Lanka
- THA - FOB - Thailand
- TPS - FOB - Tanjung Perak
- XIA - FOB - Xiamen
- YAN - FOB - Yantian
- System is handling receiving emails every 3 minutes. After successful uploading file, system will reply to the sender with report email. In case of any error, the system will also reply to sender the information of error cause. This reply will be sent also to the Jaguarfreight users that are in the BCC list of Client Application notifications.
- Once POs uploaded they should be displayed on Open POs tab
- Visibility rules - TBD.
- Validations - TBD.
SOW 5 Supplier Due Date: indicate, filter, notify
mantis: 4460
- Supplier Due Date
- = when does this need to be ready at the supplier
- = date by which an INVENTORY record needs to be created.
- Add "Due date" group indicator as column in the table of Open POs:
- Green. Due date is in XXX weeks
- Yellow. Due date is in YYY weeks
- Orange. Due date is in ZZZ days
- Red. Due is "past due"
- Add ability to filter by group of due date
- Add ability to send "Due date" e-mail notifications
- Green/Yellow "due date": no need to notify.
- Orange "due date": "PO / Item is due in xx days and no inventory record was created. Please provide a status update urgently."
- Red "due date". "PO / Item is due tomorrow and no inventory record was created. This order is late. Please update."
- Add "Due date" dashboard report
- ...
SOW 6 Inventory tab
mantis: ???
- Inventory
- ...
- closed Inventory
- ...
SOW 7 Call Off tab
mantis: ???
- Call Off
- ...
SOW 8 Logging and show history
mantis: ???
- Logging
- ...
SOW 9 Flagging and Watchlist
mantis: ???
- Flagging
- Watchlist
- ...
SOW 10 Supplier Event Validation
mantis: 4586
- Object of handling: Purchase Order (PO) on ASN Inventory tab
- Object of validation: Current Date vs Supplier Due Date of validated PO
- Provide configurable Time Frames of Validation (days before Supplier Due Date):
- XX days - start of "Impending" PO Status
- ZZ days - start of "At Risk" PO Status
- ZZ shouldn't be more than XX
- PO Statuses:
- PENDING - more than XX days before Supplier Due Date
- IMPENDING - equal or less than XX days and more than ZZ days before Supplier Due Date
- AT RISK - equal or less than ZZ days before Supplier Due Date
- PAST DUE - Supplier Due Date is today or in the past
- Validation logic
- System should validate Current Date vs PO Supplier Due Date daily (or every N days) starting from the day when PO has been uploaded to Inventory
- As soon as Current Date comply with condition of some PO Status, assign(?) the Status to validated PO and send notification e-mail to the supplier
- E-mail notifications
- Text of message: “is PO # etc etc (contents details) still going to be available on “Supplier Due Date”
- if Supplier replies Yes = no further action (log the yes, display in comments)
- if Supplier replies No = supplier can revise date + Cyberchain sends e-mail notification to planner group
- Watchlist notifications
- Changes or updates to the Supplier Due Date
- Inventory created
- Call Off created
- ASN created
- Log / display the validation info
SOW 11 Dashboards for PO Statuses
mantis: 4587
- Impending Supplier Due Date. PO’s with a supplier due date in “xx” days.
- At Risk Supplier Due Dates. Impending PO’s with a due date in “xx days” for which NO ASN was created.
- Past Due Supplier Due Dates.
- PO’s for which the supplier did not reply to the “Supplier Due Date validation e-mail” (after 2 week days from when the e-mail was sent).
- For example: E-mail sent on Monday … put on Dashboard by Wednesday, e-mail sent on Thursday, put on Dashboard on Monday etc.