| Jira Legacy |
|---|
| server | jira.agrisoftcmc.com JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 9d395f28-7110-3e09-a064-46c1f4565f20 |
|---|
| key | AAI-79 |
|---|
|
Notes: From Keith Email: . We should be getting the ERP Order # back.
In the LOAD OUT ORDERS to WEM specification, we will be supplying the ERP Order # into the “Order Number” field.
Then, in the LOAD OUT TRANS from WEM specification, one of the columns there is also “Order Number”. As long as WEM populates this with the same value (which would make sense), then we would be fine. - The Order Sequence # and Order Line Sequence # appear to be the only 2 fields that we will need to lookup before populating the table. In the LOAD OUT TRANS from WEM spec, there are fields for Lot Code and Source. I’m hoping that the files WEM creates, these are the same Lot #’s that are assigned when created; which they should be because of our other custom programming we did for them to use the WEM # as the Lot #.
- For “During the Process Allocation a receiver must exist for the order to be allocated.” … It actually looks at the Receiver table? If it is allocating a specific line of inventory, a receiver already had to be there at some point, but then, the inventory could have come from a Work Order. So we will need to look at that logic.
From Jim Email: 
|
