Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines (UXPROD-1146)

[MODORDERS-80] Spike: Receiving Schemas Created: 07/Nov/18  Updated: 03/Dec/18  Resolved: 03/Dec/18

Status: Closed
Project: mod-orders
Components: None
Affects versions: None
Fix versions: None
Parent: Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines

Type: Story Priority: P3
Reporter: Craig McNally Assignee: Pavel Korolenok
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File RE Interim Summary on Receiving.msg    
Issue links:
Blocks
blocks MODORDERS-71 Create draft receiving schemas Closed
Sprint: ACQ Sprint 52, ACQ Sprint 51
Story Points: 3
Development Team: Thunderjet
Epic Link: Receiving and Checking-in Materials based on Purchase Orders and Purchase Order Lines

 Description   

Develop high-level design for the receiving schemas. This will likely involve discussions with the PO and Tech Lead.

Time Box: 1 day

Acceptance Criteria:

  • Sufficient documentation exists to point and implement MODORDERS-71 Closed


 Comments   
Comment by Pavel Korolenok [ 03/Dec/18 ]

Below is the current status on the Receiving so far.

What is agreed:

  • mod-orders/mod-orders-storage will be extended to accommodate this functionality
  • Receiving and Checkin Record data entities are not required and will not be introduced
  • Draft definition of endpoints and schemas (see attached)

Blocker:

In order to finalize the endpoints/schema definition and start implementation, the approach needs to be defined.
Since main part of the Receiving business logic is to manipulate Items in Inventory (create/retrieve/update Items), it should be just a matter of following the selected approach to manipulate Instance/Holding when PO Line is created. See attached e-mail thread for more details.

The approach is in progress with Craig McNally. At this point, the spike is considered completed.

Generated at Thu Feb 08 22:32:50 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.