Cash Management

This section contains enhancements in Financials and Supply Management.

Require calculation of Total Amount based on Pay Bank Amount on Payment Output Detail file

Add a new amount field to PaymentOutputFileHeader (TotalPayBankAmount) to capture the total of the PayBankAmount in the related PaymentOutputFileDetail records.

Added TotalPayBankAmount field in PaymentOuputFileHeader business class and updated it while running ElectronicPaymentCreation job. Added the same in UI.

  1. Create Payables Invoices with different possible Bank Transaction Code and CashCode combinations.
  2. Select and Schedule CashRequirements.
  3. Run the ElectronicPaymentCreation job with all possible combinations.
    • PaymentCode and CashCode
    • PaymentCode and CashCodeGroup
    • CombineOutputByAccount
  4. Verify that all scenarios generate a Payment Output File with the TotalPayBankAmount.

JR-3280224

Extend Front End Split functionality to Cash Ledger Payment and Cash Ledger Payment Import business classes

This list shows the business classes that changed:

  • modules/cb/bl/CashLedgerGLDistribution.busclass
  • modules/cb/ui/CashLedgerGLDistribution.busclass
  • modules/cb/bl/CashLedgerPayment.busclass

Use these steps to test the enhancement:

  1. Prerequisite: Set up Front End Split.
  2. Sign in as Application Administrator and select Financials > Cash Management > Cash Ledger Processing > Process Cash Ledger > Payment Entry.
  3. Create a Cash Ledger Payment.
  4. For Cash Ledger Payment, create a distribution line with a posting project that is subject to Front End Split. Distribution must not contain a FinanceDimension2.
  5. Run the Front End Split Distributions action and verify that the original distribution is replaced by the split distributions.
  6. Create a Cash Ledger Payment with distribution, which is having Front End Splits project and Release it.
  7. Verify that the distributions have undergone Front End Split.
  8. Create Cash Ledger Payment with distribution, which is having Front End Splits project and Submit For Approval.
  9. Verify that each Distribution has undergone Front End Split.
  10. Create multiple Cash Ledger Payments with distributions having Front End Splits project and perform Mass Release.
  11. Verify that each Cash Ledger Transaction has undergone Front End Split.
  12. Select Financials > Cash Management > Cash Ledger Processing > Process Cash Ledger > Interface Cash Ledger Transactions.> Payment Interface Maintenance.
  13. Create Cash Ledger Payment Interface records in Released status with distributions having Front End Splits project and click Interface Cash Payments.
  14. Verify that interfaced Cash Ledger Payments distributions have undergone Front End Split.

JR-3457434

Allow the user to process a payment rejection by the bank when payments are sent to the bank in detail

A new Allow Detail Payment Reject field is available on the Bank Transaction Code. You can perform a Reject action on the payment record in the same manner as if the Bank Transaction Code was set to Payment Summarization.

Modified all edits that reference PaymentSummarization to also include BankTransactionCode.AllowDetailPaymentReject. This will expose the reject functionality to detail records with the AllowDetailPaymentReject set.

  1. Set a BankTransactionCode to Allow Detail Payment Reject.
  2. Create an invoice and run it through the payment cycle.
  3. On the created cash ledger transaction, on the Payment Records tab, select the Payment Reject action.
  4. Run Payment Void Stop Pay Update.
  5. Verify that the deposit cash ledger transaction is created and the invoice is reinstated just like a summarized payment record reject.

JR-3263573

Enhance Migrate Commitments actions to capture errors and proceed to next record

All Migrate Commitments actions were changed to log errors and list them on the new Migration Results business class. Successful commitments are also logged on the Migration Result. This allows for errors to be resolved and run the corresponding Migrate Commitment action again.

  1. Select Global Ledger > Utilities > Migrate Commitments.
  2. Verify that a Migration Result record is created each time the action is run.
  3. On the Migration Result are lists of Errors and Completed records. These actions should no longer fail in Async if there is an error with creating the GLCommit. Instead, the error is logged and the action continues.

JR-3387205