[UXPROD-2738] Bulk APIs for Invoice Storage Module Created: 07/Oct/20  Updated: 12/Mar/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Ian Walls Assignee: Ian Walls
Resolution: Unresolved Votes: 0
Labels: bulk-api
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-2818 RMB Work to Support Bulk Delete APIs Closed
Defines
is defined by MODINVOSTO-84 Bulk Create/Update API for invoice lines Open
is defined by MODINVOSTO-85 Bulk DELETE API for invoice lines Open
is defined by MODINVOSTO-86 Bulk Create/Update API for invoices Open
is defined by MODINVOSTO-87 Bulk DELETE API for invoices Open
Development Team: None
PO Rank: 70
PO Ranking Note: Equally necessary as Orders
Rank: Chicago (MVP Sum 2020): R3
Rank: Cornell (Full Sum 2021): R3
Rank: Duke (Full Sum 2021): R3
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R3
Rank: U of AL (MVP Oct 2020): R5

 Description   

Current situation or problem:

In order to facilitate migrations in a timely and efficient manner, the Invoice Storage module needs to have batch APIs. POSTing, PUTting and DELETEing records one HTTP request and database commit at a time is unusably slow for large data sets.

In scope:

  • Bulk Create/Update for Invoice Lines
  • Bulk Delete (with CQL query parameters) for Invoice Lines
  • Bulk Create/Update for Invoices
  • Bulk Delete (with CQL query parameters) for Invoices

Out of scope:

Batch APIs for batch voucher export configuration and documents are not required. The anticipated order of magnitude for these record sets is not sufficient to require batch handling. The individual record APIs are sufficient.

Use case(s):

  • Initial Data Migration, including iterative data load/delete

Comments:

In order for these APIs to be effective, they need to bypass the business logic and go directly to the storage module. This means that bulk creation of invoices will not connect data to the Orders, Receiving or Finance modules. The user of these APIs is responsible for maintaining data integrity; documentation needs to reflect this.

Questions:

Can the Invoice module function properly with just Invoices and Invoice Lines, or do vouchers and voucher lines need to be created as well? If so, then these would probably need bulk APIs, too.


Generated at Fri Feb 09 00:26:26 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.