/
REF1 displays the previous BUA's REF1 data

REF1 displays the previous BUA's REF1 data





Description of Issue

REF1 displays the previous BUA's REF1 data when selecting define in the ribbon



Context

Budget Transfers and Amendments



Cause

After updating the REF1 on a BUA, if you use the Define option to pull up the next BUA the REF1 from the prior BUA will display



Resolution

Work ticket MUN-420853 is open with development to address the issue

As a work around you can use the Browse option when searching for the next BUA and the REF1 will display as expected for each journal



Additional Information

This is a display issue when using the Define option after updating the Ref1 data on the first BUA

The BUA's will post with the expected REF1 data for each journal 











Related content

The Reference1 field did not update when saved - Budget Transfers and Amendments or Accounting Entries
The Reference1 field did not update when saved - Budget Transfers and Amendments or Accounting Entries
More like this
What does the A in the Ref3 field mean for budget amendments
What does the A in the Ref3 field mean for budget amendments
More like this
No original budget has been set for project string message when posting a carry forward BUA
No original budget has been set for project string message when posting a carry forward BUA
More like this
Project Budget Package Posting - Ref1 displays calendar year instead of project year
Project Budget Package Posting - Ref1 displays calendar year instead of project year
More like this
Update to REF1 field does not save - Accounting Entries
Update to REF1 field does not save - Accounting Entries
More like this
Budget amendment BUA displays as a budget completion journal BUC after posting
Budget amendment BUA displays as a budget completion journal BUC after posting
More like this