Cash Management
Custodial Account Management (CAM) feature
Added feature to fully support management of Custodial and other Trusts.
Program/Business class/Process affected:
These are the added business classes:
- CamCategory.busclass
- CamClassification.busclass
- CamContacts.busclass
- CamCustodian.busclass
- CamFundingCharacteristics.busclass
- CamFundingCharSubType.busclass
- CamSite.busclass
- CamSourceOfFunds.busclass
- CustodialAccountEdit.busclass
- CustodialAccountManagement.busclass
- CustodialActivity.busclass
- CustodialAttachment.busclass
- CustodialComment.busclass
- CustodialContact.busclass
- CustodialDeliverable.busclass
- CustodialDetailAmount.busclass
- CustodialDetailTransfer.busclass
- CustodialFundChar.busclass
- CustodialSourceOfFunds.busclass
These are the modified business classes:
- AllocationControl.busclass
- AllocationTransactionDetail.busclass
- CashLedgerCashReceiptDetail.busclass
- CashLedgerGLDistribution.busclass
- CashLedgerPayment.busclass
- CashLedgerTransaction.busclass
- FinanceDimension10.busclass
- FinanceDimension10Structure.busclass
- FinanceEnterpriseGroup.busclass
- GeneralLedgerJournalControl.busclass
- GeneralLedgerTransaction.busclass
- PayablesInvoice.busclass
- PayablesInvoiceDistribution.busclass
- PayablesInvoiceError.busclass
- PayablesInvoicePayment.busclass
- ReceivableGLDistribution.busclass
To test the enhancement:
Verify successful setup and process for Custodial Account Management.
JT-1576628
Removed the LineMatchField value in Bank Statement Reconciliation
When determining the LineMatchField value during the cash reconciliation process, the modification options were being applied to the entire LineMatchField, compared to only the variable portion. This caused issues when the LineMatchField definition contained both text variables and hard-coded values. The Remove Alpha Characters option was removing not only the text variables alpha characters, but any hard-coded values.
Program/Business class/Process affected:
- BankReconciliationMatchRule (bl/ui)
- BankStatementReconciliation (bl/ui)
- BankReconciliationMatchRuleGroupDetail (ui)
- LineMatchFieldArray.field (new)
- LineMatchFieldSegment.field (new)
To test the enhancement:
Verify that the modification options defined for a Bank Reconciliation Match Rule are only applied to the variable portions of the LineMatchField.
Due to a slight change in how the Modification Options are processed for the LineMatchFields, a configuration parameter is created so this feature can be turned off and processed using the existing functionality. To do this, a ConfigurationParameter must be defined with these values:
Component = config
Key = DisableApplyingModificationOptionsToVariablesOnly
Type = Boolean
Value = trueJT-1554367
Front-End Split feature for Cash Management Cash Receipts
There is a Public Sector requirement to perform the allocation revenues up-front, during the recording of the original transaction. By keying in a Project number on a distribution, this functionality would split that line to reflect all the funding sources, both internal and external, funding this Project and the Fund associated with each Funding Source. This feature is known as Front-End Split (FES).
Program/Business class/Process affected:
- modules/cb/bl/CashLedgerCashReceiptDetail.busclass
- modules/cb/bl/CashLedgerCashReceiptHeader.busclass
- modules/cb/bl/CashLedgerGLDistribution.busclass
- modules/cb/ui/CashLedgerCashReceiptDetail.busclass
- modules/cb/ui/CashLedgerGLDistribution.busclass
To test the enhancement:
- Perform the appropriate setup.
- Create a Cash Management Cash Receipt with a distribution. Distribution must contain a Project that has been setup for FES. Distribution must NOT contain FinanceDimension2. Invoke the action: Front End Split Cash Receipt Details.
- Ensure that the original distribution has been replaced by the split disributions.
- Create and release a Cash Management Cash Receipt and verify that the details have undergone Front End Split.
JT-1623072