- MODKBEKBJ-530Getting issue details... STATUS
Goal:
Determine the connection between POL, invoice lines and package/resource via agreements
Connection via agreements app
- Get info about agreement lines that related to package or resource.
- For each agreement line get detail info about agreement.
- Extract order line (POL) ids from agreement.
- Get details about POLs and invoice lines.
Endpoints and responses details:
Call endpoint | GET /erm/sas?filters=items.reference=<packageId/resourceId> | |||
Extract ids from response | ↓ | |||
Call endpoint | GET /erm/entitlements?filters=owner=<agreementId> | |||
Extract poLineIds from response | ↓ | ↓ | ||
Call endpoints | GET /orders/order-lines?query=id==<poLineId1> or or id==<poLineIdN> | GET /invoice/invoice-lines?query=poLineId==<poLineId1> or poLineId==<poLineIdN> |
Questions and answers
Question | Answer |
---|---|
Will the current and future connections provide us the information we need to return cost and budget information? | Current connection provide all needed info but it possible only if there are any agreement attached to package/resource. Future direct connection to the orders app assumps more stable connection. |
Is a direct connection to the Invoice Line needed rather than getting the POL then Invoice line? | Invoice line could be retrieved if POL is known. |
High level observations on performance? | There are at least 4 requests needed to get info about POL and invoice lines. If there will be more than one agreement attached to the package/resource then more requests required. Performance should be analyzied after second investigation. |
What challenges are we facing in getting this information? | |
Via eholdings app should we offer a way to attach package/resource to a POL# or Invoice line number? |
1 Comment
Khalilah Gambrell
Thanks Pavlo Smahin. We should assume that a package / resource will be tied to multiple agreements.