Global Ledger
Relabel Pending Obligations tab to Unreleased Obligations tab
The "Pending Obligations" label in budgeting was confused with the "Process Pending" action.
Program/business class/process affected:
- BudgetTemplate
- BudgetGroup
- Budgeting menu
Use these steps to test the enhancement:
- Create a distribution or a transaction that matches a Budget Template that is in the Ready state.
- Confirm that the label is "Unreleased Obligations" and that the details of the new
distribution or transaction. Confirm that these areas contain the Unreleased Obligations
label and that they show the details of the new distribution or transaction
- The tab on the template form
- The tab on the corresponding Budget Group
- The Budgeting menu for the allowed roles
JT-1577632
[Mobile] – Add ‘Exporting’ message in Budget Scenario screen when Export to Import is ongoing
An ‘Exporting’ message in the Budget Scenario mobile screen is not available when Export to Import process is ongoing
Program/business class/process affected:
- Scenario.busclass
Use these steps to test the enhancement:
- Sign in as Application Administrator.
- Select GlobalLedger >Budgeting > Budget Scenarios and open the form.
- Verify on the Scenario Main form that a conditional text message (“Exporting”) is displayed if the Exporting (persistent field) is true.
JT-1578536
GLSSJE: Add new billing invoice number element at the userarea in SyncSourceSystemJournalEntry Outbound Bod
GLSSJE: Add new billing invoice number element at the userarea in SyncSourceSystemJournalEntry Outbound BOD
Program/business class/process affected:
- FSM_ION_SyncSourceSystemJournalEntry_Outbound.lpd
New Changes in IPA:
- Added Nodes: Assign1180, billingCompany, Assign6420, and made changes in Assign2700 javascript file.
- Added Transaction Node BillingCompany for Billing company and manualInvoiceNumber.
Use these steps to test the enhancement:
- Open a Finance Enterprise Group. On the Options tab, select the BOD Trigger check box.
- In Channels Administrator, Activate the respective ION Inbox Receivers. When the bod is processed, the Work Unit is triggered.
- Enable the Manual Invoice Numbering in the billing company.
- Create and Release a billing invoice.
- Specify the Manual Invoice number.
- Verify the Manual invoice number in Userarea of the XML.
JT-1562056
Front-End Split Feature
Public Sector entities expressed the need to perform the allocation of expenses and revenues up-front, during the recording of the original transaction. By keying in a Project number on a transaction line, this functionality would split that line to reflect all the funding sources (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:
- FinanceEnterpriseGroup
- RequisitionLineDistribution
- PurchaseOrderLineDistribution
- PayablesInvoiceDistribution
- ProjectContract
- ProjectFundingSource
New business class added: FrontEndSplitDistributions.busclass
Use these steps to test the enhancement:
- Perform the appropriate setup
- Create and release Requisition and verify that the distributions have undergone Front End Split.
- Create and release PO and verify that the distributions have undergone Front End Split.
- Create and release AP Invoice and verify that the distributions have undergone Front End Split.
JT-1573514
Add ability to put a transaction on hold for billing or revenue from the project search lists
From the project searches menu the transaction detail list has two actions Put Billing On Hold and Put Revenue On Hold. From there you can hold transactions for active, billable projects where there status allows billing and or revenue. This will allow you to select transactions for a project that you do not want to bill or recognize revenue on.
Program/business class/process affected:
- Project
- GLTransactionDetail
Use these steps to test the enhancement:
- Select Project Ledger > Searches and view the the transaction detail list.
- The Put Billing On Hold action and the Put Revenue On Hold action are used to hold transactions for active billable projects where the status allows billing and or revenue.
- Select transactions for a project for which you do not want to bill or recognize revenue.
- Run the actions.
JT-1590128