AAI-479 Destination Bin mapping for Feed Production Repete Process
Target release | 1.6.15.0 |
|---|---|
Document status | In Review |
Document owner | @Jim Brashears |
Story/Problem to Solve
As a feed clerk, I need the ability to map a Repete feed bin to a Aeros Work Order destination bin, so when a work order is created by the Feed Production process it will create inventory in the correct bin.
Background
Currently the Connect Feed Production process for a Repete Batcher does not have a map for destination bin. For our current clients this has not been an issue since they were not requiring a specific bin to be assigned during the Aeros Work Order creation.
Assumptions
A Connect Feed Production Batch has been created.
The Repete batcher data has bin included in its batch.
Requirements
Title | User Story | Notes | |
|---|---|---|---|
| 1 | Configuration to Map Bin for the Feed Production Repete Batcher Process. | As a feed clerk, I need the ability to configure the Feed Production process to require bin mapping, so bin will be mapped if configured to do so. | This configuration is needed for clients that are using the existing Repete Feed Production process and do not want bins to be mapped. |
| 2 | Add a new generic map between Repete Bins and Aeros work order warehouse bins . | As a feed clerk, I need the ability to map a Repete feed bin to a Aeros Work Order destination bin, so when a work order is created by the Feed Production process it will create inventory in the correct bin. | Source Product: Batcher Source Field : Bin Code Target Product: Aeros-Inventory Control Target Field: Destination Bin |
| 3 | Add Destination Bin column to Staging grid. | As a feed clerk, I want to see the mapped destination bin that will be used during the work order creation process, so I can review and make sure I have the correct bin mapped. | There is already a column called Destination Bin on the staging table that is not being populated. |
| 4 | Validate mapped bin. | As a feed clerk, I want to be notified when I am missing a bin map or if the mapped bin does not exist in Aeros, so a work order will not be created for records that do not have a valid bin map. | Please utilize the Connect framework for validation. Validation message : "Mapped Bin (bin code) is not valid, please check Aeros if bin exists or if map is correct". |
User interaction and design
Requirement #1: Configuration to Map Bin for the Feed Production Repete Batcher Process.
Requirement #2: Configuration to Map Bin for the Feed Production Repete Batcher Process.
Add new Map in Generic Mapper.
Source Product: Batcher
Source Field : Bin Code
Target Product: Aeros-Inventory Control
Target Field: Destination Bin
Requirement #3: Add Destination Bin column to Staging grid.
(Already Exists)
Requirement #4: Validate mapped bin.
Add validation message to import messages.
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
|---|---|
None at this time |
|
Acceptance Criteria:
Requirement | Acceptance Criteria |
|---|---|
#1: Configuration to Map Bin for the Feed Production Repete Batcher Process. | The user will be able to navigate to the product configuration form and select and save Map by bin checkbox. |
#2: Add a new generic map between Repete Bins and Aeros work order warehouse bins . | The user will be able to navigate to the Generic Map and create a new Map between Repete bins and Aeros Destination bins. |
#3: Add Destination Bin column to Staging grid. | The user will see a new column on the Feed Production Staging grid called "Destination Bin" which will be populated with mapped Aeros Destination bin. |
#4: Validate mapped bin. | The user will see a new import message on the import tab stating a Bin map is invalid if the a map doesn't exist in the Generic mapper or does not exist in Aeros. |
Client Sign Off
_______________________________________________________________