Allow mapping for expense classes through GOBI

Description

Overview: Given a FOLIO tenant is using expense classes in their Fund structure. Third party systems must be able to indicate which Fund and Expense classes should be associated with the order line.

Acceptance criteria:
External systems (eg GOBI) can apply fund and expense class when creating orders

Approach:
Between fund code and expense class code splitter must be ":"

Example : "fundCode1234:electronicPrn"

 

Evaluation https://folio-org.atlassian.net/wiki/display/DD/Apply+expense+classes+to+orders+and+invoices+through+API+integrations

Information:
External systems generally only support Fund codes and the sending of a fund code. For this reason it might make sense to use expense class codes as extensions and maintain a list of all fund code+extentions that can be used to Map Fund codes and expense classes when creating orders.
External systems (eg GOBI) may have customizable fields that could be used to send the additional expense class information separately from Fund code.

Environment

None

Potential Workaround

None

Attachments

4

Checklist

hide

TestRail: Results

Activity

Show:

Dennis BridgesSeptember 2, 2021 at 5:50 PM

Test successful in folio-testing through GOBI 8910-24 account.

Andrei MakarankaSeptember 2, 2021 at 7:56 AM

Now there are to ways how to send expense class from GOBI:
1. Upload custom configuration for support expense class in the LocalData element/field
2. In scope of the support expense class in the

And for this option no need any custom configuration.

Dennis BridgesAugust 31, 2021 at 7:51 PM
Edited

 can you update the configuration file in folio-testing so that I can try creating orders through gobi with this expense class mapping working? Otherwise I'm not sure how to test as it doesn't seem to map any fund information at the moment.

Dennis BridgesAugust 30, 2021 at 8:49 PM

I have requested the GOBI test environment updates required to complete this test but they will not be available today. This story will need to spillover to next sprint in order to be verified in testing.

Andrei MakarankaAugust 30, 2021 at 7:04 AM

Please do final verification.

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Story Points

Sprint

Development Team

Thunderjet

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 25, 2021 at 11:29 PM
Updated May 6, 2022 at 10:47 PM
Resolved September 2, 2021 at 5:50 PM
TestRail: Cases
TestRail: Runs