Details
-
Story
-
Resolution: Completed
-
Medium
-
None
-
None
-
GxP
-
RP Sprint 89, RP Sprint 90
-
Yes
Description
Problem Statement
In order to exit the Pfish system and get the ANZ markets on the Supply Status tool, some adjustements are going to be needed to ensure there is no loss of capabilites from one system to another.
One of they key difference between Pfish and Supply Status for the ANZ markets is the possibility to report to customers outside of Pfizer on the stock status of every sku. The reporting to end customers takes place through a platform called Hospital Hub, which is fed with raw data from Pfish.
In Pfish, each sku is assigned a status (available, constrained, short dated, out of stock) by the market planners. A complete list of sku's is extracted from Pfish and sent to Hospital Hub on daily basis
Documents enclosed
- example of sku status maintenance in Pfish
- example of stock status picture in Hospital Hub
Acceptance Criteria
- Create a placeholder field for ANZ markets to maintain the SKU status that will be communicated out to customers (in the product page)
- Field is brought into the column selection of the Shortage Risk Details table
- Allowable Status values (Available, Constrained, Constrained - Short Dated, Discontinued, Follow Up, New Product Launch, Out Of Stock, Released, Short Dated)
- Full list of sku's can be extracted from Shortage Risk Details table on daily basis
- Extract can be formatted based on enclosed extract
qTest: Test Execution
Attachments
Issue Links
- is cloned by
-
OS-5210 Supply Status - Create a placeholder field for ANZ markets to maintain the allocation notes communicated to customer through Hopsital Hub
- Closed