[
https://issues.apache.org/jira/browse/FINERACT-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Saghy resolved FINERACT-2347.
----------------------------------
Resolution: Fixed
> Introduce `classification` code value field for Capitalized Income and
> Buydown Fee loan transactions
> ----------------------------------------------------------------------------------------------------
>
> Key: FINERACT-2347
> URL: https://issues.apache.org/jira/browse/FINERACT-2347
> Project: Apache Fineract
> Issue Type: New Feature
> Affects Versions: 1.12.1
> Reporter: Adam Saghy
> Priority: Major
> Fix For: 1.13.0
>
>
> Introduce new field on loan transaction entity:
> Field name: classification
> Field data type: Long
> Field java type: CodeValue
>
> Introduce 2 new codes:
> *For Capitalized Income transaction type:*
> Code name: capitalized_income_transaction_classification
> *For Buydown Fee transaction type:*
> Code name: buydown_fee_transaction_type
>
> Amend the template API to retrieve the available classification values for
> these two transaction type (only for these two for now!):
> classificationOptions: List of code values (if there were set any, by default
> there will be none) based on the transaction type.
>
> When Capitalized Income / Buydown Fee transaction got created, user should be
> able to provide classification (optional field!), and Fineract store it on
> the transaction level!
> If classification was not set, it remains null.
> Fineract should check whether valid classification was provided:
> * Exists based on the related codes (see above)
> In case adjustment transaction got created for existing Capitalized Income /
> Buydown fee transaction, the adjustment transaction automatically inherit
> from the target transaction the classification, user cannot set different
> classification for this transaction.
> This rule does not apply to Amortization transactions as those contain
> aggregated amounts, there could be multiple Capitalized Income transaction
> amortization amounts with different classifications.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
