Kreher Managed Inventory System Integration
- Jim Brashears
Target release | Connect 1.6.5.X |
|---|---|
Epic |
|
Document status | DRAFT |
Document owner | @Jim Brashears |
Designer | @Derrick Canfield, @Jim Brashears |
Developers | @Derrick Canfield |
QA | @Charles Torres |
Goals
Create Aeros ERP Customer Orders from Kreher Vendor Managed Inventory System.
Background and strategic fit
Kreher is currently integrating their Vendor Managed Inventory System with Aeros Classic and will require the same integration with Aeros ERP since they are upgrading from Classic to ERP.
Assumptions
A PEEPS file will be read into a staging area.
A Map will be able to be maintained and updated by a User via our Connect application.
This process can be ran manually and can be scheduled for automation.
Errors can be reviewed by a user and correction can be made.
Requirements
# | Title | User Story | Importance | Notes |
|---|---|---|---|---|
1 | Import records | The user needs the ability to upload a PEEP file into a staging area for review. | ||
2 | Map Fields | the user needs the ability to map PEEP order elements to ERP order elements. | Must Have |
|
3 | Validation | Staging records will need to be validated before sent to ERP. | Must Have |
|
4 | Customer Orders | Customer orders will use ERP templates to determine pricing. | Must Have |
|
User interaction and design
Aeros Connect will be used to accomplished this integration. Currently Connect has other processes that will read a source and create an ERP Customer Order. I propose we reuse current UI standards in Connect.
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
|---|---|