[MODFISTO-461] FYRO fails on Second Journal Created: 02/Feb/24  Updated: 08/Feb/24

Status: Open
Project: mod-finance-storage
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P2
Reporter: Thomas Trutt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Microsoft Word CUL - Endowed-rollover-errors-FY2025 (1).xlsx     Microsoft Word CUL - Endowed-rollover-errors-FY2025.xlsx     Microsoft Word DRY-run FY Rollover test updated.docx     Microsoft Word DRY-run FY Rollover test.docx    
Sprint: ACQ Sprint 185
Development Team: Thunderjet
Release: Not Scheduled
Potential Workaround: Run fix ecnumbrances script: https://github.com/folio-org/mod-finance-storage/tree/master/scripts/fix_encumbrances
RCA Group: TBD

 Description   

Overview:

While testing FYRO on Cornell's Poppy dry-run they ran into an error when trying to roll over the second Ledger.

The first ledger: Contract Colleges. That ledger rolled over as expected

The Second Ledger:  Endowed said it completed but an error message was received after. 

 

Contract has a planned budged, Endowed does not

 

Error message and screen shots attached.

Investigation result:

There were two similar encumbrance transactions which violate unique index:

        {
          "fieldName": "encumbrance",
          "multiFieldNames": "amount, fromFundId, encumbrance.sourcePurchaseOrderId, encumbrance.sourcePoLineId, encumbrance.initialAmountEncumbered, encumbrance.status, expenseClassId, fiscalYearId",
          "tOps": "ADD",
          "whereClause": "WHERE (jsonb->>'transactionType')::text = 'Encumbrance'"
        }

Approach:

Need to skip unique index for 'transaction' table while running rollover. The similar approach you can see here.

Interested parties:

Cornell

Dennis Bridges , Joseph Reimers 



 Comments   
Comment by Thomas Trutt [ 02/Feb/24 ]

I am contacting FSE to see if logs can be pulled and attached to this Bug report. from the message it looks like it was a duplicate key error.

Comment by Khalilah Gambrell [ 07/Feb/24 ]

Hey Mikita Siadykh Joseph Reimers Dennis Bridges - assigning this issue to Thunderjet.

Comment by Mikita Siadykh [ 07/Feb/24 ]

Serhii_NoskoKhamidulla Abdulkhakimov could you please work with FSE as it should be fixed in scope of https://folio-org.atlassian.net/browse/MODFISTO-441

Comment by Thomas Trutt [ 07/Feb/24 ]

The encumbrance script was ran on our dry-run env and the second ledger was rolled over. Errors where generated but the budgets where created for the ledger. From what i can see all the errors are because there are orders that crossed ledgers (attached). There where no other errors when the other ledgers where rolled over.

DRY-run FY Rollover test updated.docx
CUL - Endowed-rollover-errors-FY2025 (1).xlsx

Comment by Mikita Siadykh [ 07/Feb/24 ]

Thomas Trutt yep, it’s connected to duplicate encumbrances that script fixed, in scope of this issue we are going to ignore them to avoid rollover stop in the middle

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