MiniPOEM
From UG
(Difference between revisions)
(Created page with 'Category:POEM == Info == == Core Requirements == == SOWs == === SOW 1 === === SOW 2 === === SOW 3 ===') |
(→Core Requirements) |
||
| Line 3: | Line 3: | ||
== Info == | == Info == | ||
| - | == Core Requirements == | + | |
| + | |||
| + | - PO Issued On (date) | ||
| + | ??? filled by shipper on Create ASN? | ||
| + | |||
| + | - Supplier Due Date (the “theoretical “ready to ship” date) | ||
| + | |||
| + | ??? but we have already: | ||
| + | Cargo Available | ||
| + | |||
| + | a.k.a. CT#Cargo_available | ||
| + | |||
| + | Meaning: This is the date that the goods are available for pick up (from Origin Door). | ||
| + | |||
| + | - 1 additional TAB .. “pending PO’s” | ||
| + | ??? where? what would go in there? | ||
| + | |||
| + | - Create ASN’s from PO’s (partial qty) | ||
| + | |||
| + | |||
| + | - Create automated alerts / dashboards for “impending supplier due date” and “past due supplier due date” with e-mail notification alerts to designated supplier and planners | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | <hr>== Core Requirements == | ||
== SOWs == | == SOWs == | ||
Revision as of 20:47, 23 May 2013
Contents |
Info
- PO Issued On (date) ??? filled by shipper on Create ASN?
- Supplier Due Date (the “theoretical “ready to ship” date)
??? but we have already: Cargo Available
a.k.a. CT#Cargo_available
Meaning: This is the date that the goods are available for pick up (from Origin Door).
- 1 additional TAB .. “pending PO’s” ??? where? what would go in there?
- Create ASN’s from PO’s (partial qty)
- Create automated alerts / dashboards for “impending supplier due date” and “past due supplier due date” with e-mail notification alerts to designated supplier and planners
== Core Requirements ==
