Global Ledger CU73

This section contains enhancements in Infor CloudSuite Financials for 11.0.73.0.

Lazy activation of budget templates

Lazy activation addresses the problem of the inability to activate a budget template if it had a large number of dimensions or dimension elements. The number of budget groups grows exponentially.

There is no lazy ProcessPending at this time, but pending items are displayed. They can be processed by reactivating the template. Before deactivating, any pending items are ignored and any pending remove items continue to be processed.

Program/Business class/Process affected:

  • BudgetTemplate
  • BudgetGroup
  • BudgetTemplateGroupTotal
  • BudgetEditBatch
  • GeneralLedgerTransaction
  • GLCommit
  • BudgetGroupLazyInit
  • BudgetLazyDocument
  • BudgetLazyPrime
  • BudgetLazyObligation

Security changes

  • FINBudgetProcessing_ST
  • FINBudgetEditing_ST
  • IEFINSharedInbasketApproval_ST
  • IEFINCommonViewInformation_ST

UI changes

  • LazyActivation flag on BudgetTemplate
  • LazyInitialized read-only flag on the BudgetGroup form and in the list in a BudgetTemplate Groups tab

Use these steps to test this enhancement:

  1. Set the LazyActivation flag on a Budget Template and run LazyActivate. Note that a FinanceEnterpriseGroup can have a mix of lazily activated and fully activated templates. For performance, we recommend having at most one Ready lazy template. You can expect relatively poor performance for a lazy template until most budget groups are initialized. We recommend not to use a lazy template until required. A template with LazyActivation can only edit at the posting level.
  2. Confirm after Lazy Activation that not all BudgetGroups are created. Only those referenced in released GeneralLedgerTransactions, unreleased GLCommits, released GLCommits with difference amount, unreleased GeneralLedgerTransactions for GL System., and unreleleased change request lines. For the budget groups that are created, the corresponding BudgetGroup obligations should include cube data and amounts for released GeneralLedgerTransactions. And, BudgetTemplateGroupTotals should be populated from the budget groups created.
  3. Confirm that creating a distribution that references a BudgetGroup that has not been created yet creates the distribution but does not initialize it. The reading of the GLTOT cube, GL Transactions, and GLCommits is represented by a BudgetGroupLazyInit. If any BudgetGroup referenced by a document is not ready at release time, the release only occurs after all BudgetGroups are initialized. A BudgetLazyDocument is created for the waiting document. Both BudgetGroupLazyInit and BudgetLazyDocument are deleted once ready. A first-time reference to a BudgetGroup does not create a warning budget error.
  4. Verify that edits are processed as expected for edits and batch edits by a PO interface job. Verify edits are processed as expected for PO documents where lines were prepared and any template is processing.
  5. Verify that once a BudgetGroup is initialized, it is not initialized again. Try to create distributions from different documents that reference the same uninitialized BudgetGroup. Only one should perform the initialization.
  6. Confirm Deactivate and Delete Template works as expected and clean up any BudgetGroupLazyInit and BudgetLazyDocument instances.
  7. Check performance of initializing a BudgetGroup by running LazyPrepareGroup. Check performance on large PO and interface jobs.

JT-1456280

Updated confirmation message when releasing a journal

The confirmation message when releasing a journal has been updated.

Program/Business class/Process affected:

GeneralLedgerJournalControl.busclass

Use these steps to test this enhancement:

  1. Select Application Administrator > Financials > Global Ledger > Processing > Journal > Journals.
  2. The "Pending Budget Edit" message is in red if you have any journals with PendingBudgetEdit set to true.

JT-1421732

Display Transaction on the same page as Beginning and Ending balances

Previously, it was only possible to view transactions for a specific Totals line and not for the selected account in the Account Analysis form. Users can have the transactions be displayed on the form.

This feature requires 4.0 controls.

Program/Business class/Process affected:

  • AccountAnalysisSettings
  • GeneralLedgerChartAccount
  • GeneralLedgerTransaction

Use these steps to test this enhancement:

  1. Click the Analyze Accounts link from both the AccountAnalysisSettings list and form. A form is displayed with a Transactions button.
  2. Click Transactions. Transactions from the selected account should be displayed. The Transactions button should be displayed again when navigating to another account.
  3. Click the Analyze Budget link from both the AccountAnalysisSettings list and form. The Transactions button should not be displayed.

JT-1452008

Fund accounting functionality for XM Interface

Fund accounting functionality has been added for company paid expenses interfaced from Expense Management.

Program/Business class/Process affected:

Processing company paid expenses interfaced from Expense Management

Use these steps to test this enhancement:

  1. Verify that company paid expenses interfaced from Expense Management use fund accounting functionality.

JT-1457829

MobileApp: BudgetApproval Change Request Changes

Updates were made to the BudgetApproval Change Request for the MobileApp.

Program/Business class/Process affected:

  • BudgerChangeOrderComment.busclass
  • BudgetChangeOrderLineComment.busclass

Use these steps to test this enhancement:

  1. Create a BudgetChangeOrderRequest without adding an attachment in the comment. Open My Inbasket and open the approval form. Verify that the Attachment symbol is not displayed.
  2. Create a BudgetChangeOrderRequest with an attachment in the comments section. Open My Inbasket and open the approval form. Verify that the Attachment symbol is displayed.

JT-1464555

Add actions to Budget Template Activation queue action

When batch posting, you can prevent initialization of budget groups in a lazy budget template to avoid counting obligations multiple times.

Program/Business class/Process affected:

  • Posting process

Use these steps to test this enhancement:

  1. Confirm that the BudgetGroup.LazyPrepareGroup action is mapped to the Budget Template Activation queue.
  2. During batch posting, the queue should be suspended. When complete, the queue should be unsuspended.

JT-1468320