Project Ledger CU74
Project Ledger security changes
Program/Business class/Process affected:
These are security class changes:
- Project Ledger related business classes in security classes that contain 'Projects' as
part of the name.
ProjectsAdditionalSetupProcessing_ST.secclass, ProjectsBasicSetupAdmin_ST.secclass, ProjectsCreateAssignment_ST.secclass,ProjectsCreateBalanceAdjustment_ST.secclass,
ProjectsManageAssignmentEffort_ST.secclass, ProjectsToCompleteSetup_ST.secclass
- We changed rules for Project Ledger related business classes in security classes that
did not contain 'Projects' as part of the name.
APBasicInvoiceProcessing_ST.secclass, POBasicPurchaseOrderProcessing_ST.secclass, ReconciliationAuditInquiry_ST.secclass
- Changes on IEFINCommonViewInformation_ST, so that all users get this security access. Changes made for all related business classes.
- Replaced unconditional to new condition as below inside the security classes Project.SecurityGroupAllowsAccess
Use these steps to test the enhancement:
Restrict the users to view or access the data for a set of Project's at assigned roles. need to enable Project Security Setup.
Attached a sample detailed test document for one scenario.
JT-1422308
Update IDM Project Invoice formats to current mapping
Sample Templates for Project Contract Invoice using IDM are outdated. We updated the templates to reflect changes in non-IDM templates.
Program/Business class/Process affected:
IDM
Project Contract Invoice
Generate
Sample Document Template
To test this enhancement, generate Project Invoices using the Updated IDM Templates. The BillToAddress is used if available. If not, then the Customer’s Address is used.
JT-1452689
Allow ability to enter a partial code block for the indirect burden offset
You can now specify a partial code block for the indirect burden offset to enable the posting of the offset to either the cost center, fund, or any dimension from the originating expense.
Program/Business class/Process affected:
Add a new fields to the ProjectIndirectBurdenCode business class to designate partial finance structure. This affects the Journalize Indirect Burdens action.
Use this information to test the enhancement:
- Add an indirect burden.
- Define the offset account as a partial finance structure.
- Run the Generate and Journalize actions.
- Verify that the offset entry inherits dimensions that are not defined on the partial offset from the originating expense transactions.
JT-1467577
Added derived fields to ProjectContractInvoiceLine for Indirect and Fringe burden rates
This enhancement satisfies the requirement to report burden rates on invoice detail or supporting invoice reports by adding derived fields to ProjectContractInvoiceLine for Indirect and Fringe burden rates.
Program/Business class/Process affected:
ProjectContractInvoiceLine business class
Use these steps to test the enhancement:
- Generate Invoices containing indirect and fringe burdens.
- Personalize the ProjectContractInvoiceLine business class to include Derived Indirect Burden Rate and Derived Fringe Burden Rate columns to the list.
- Verify that the indirect and fringe rates are displayed for ID and BD event code lines.
JT-1470520
Change SEFA report name to SEFA worksheet
Change the report name for the Schedule of Federal Awards toSchedule of Federal Awards Worksheet
Program/Business class/Process affected:
ProjectFundingSource
To test this enhancement, verify the name change.
JT-1483671
Added labor redistributed field to processed labor lists
Need visibility to which processed labor distributions have been redistributed. Enhancement includes:
- New derived fields and conditions have been added to ProjectAssignmentLabor. Added a new column to the Processed Labor lists that indicates whether redistribution has been done for the specified employee and labor period.
- Added audit log list to the ProjectAssignmentLabor busclass that is available using Drill Around from the Project Assignment Labor record. Shows status, planned percent, actual percent and when and who changed it.
Program/Business class/Process affected:
ProjectAssignmentLabor business class and lists
To test this enhancement, redistribute labor and verify that it is reflected on the projectassignmentlabor list. Verify that you can Dill Around to the audit log.
Dependencies:
Grant Accounting Labor Distribution processing
JT-1485908
Added new Project Reversal Invoices in IDM
Need to produce Project Contract Invoice Reversal Documents using IDM
Program/Business class/Process affected:
- IDM
- IDM Template, Sample Document Template
- Project Contract, Project Contract Invoice, Project Contract Reversal Line, Project Funding Source, Project Structure, Project Documents IDM Template
Use these steps to test then enhancement:
- Generate Project Contract Invoice Reversals using IDM
- Print Project Contract Invoice Reversals using IDM
- Email Project Contract Invoice Reversals using IDM
JT-1429766
Update Project Contract Invoice Document Type Attribute - Remove max length
The InvoiceGroup, InvoiceType, Project, Status, FinanceDimension2 and FinanceEnterpriseGroup attributes of FSM_ProjectContractInvoice, cannot handle values that are higher than 99999999 and length greater than 30, 25, 15, 15, and 4 respectively. User cannot attach document if any attribute’s value exceeds the set Max Length of the attribute.
Program/Business class/Process affected:
- IDM
- Project Contract Invoice
Use this information to test the enhancement:
If a config file is imported to a system with no configuration to FSM, the attributes of FSM_ProjectContractInvoice will have no max length. If it is imported to a system with an existing configuration, the user must manually delete the Max Length values of the attributes of FSM_ProjectContractInvoice.
JT-1482872
Add a new funding source date to Generate Invoices and Recognize Revenue actions
Added a funding source date to Generate Invoices and Recognize Revenue actions. The invoice date parameter on the Generate Invoice action is currently used for these records: Projects, Funding Sources, Milestones/Installments, Advances, Retainers, Tax, Invoice date, Due Date, Receivable Aging, and Journal transaction dates. Using a single invoice date parameter to determine all of the above does not account for lagged invoices.
Program/Business class/Process affected:
Generate Invoices and Recognize Revenue actions
Use these steps to test the enhancement:
- Generate the Invoices action and the Recognize Revenue action. Verify that the project
funding date picks up all valid records as follows:
- Enhancement includes a new required funding source date parameter added to both Generate Invoices and Recognize Revenue actions.
- The new funding source date field will determine valid funding sources, milestones/installments, advances, and retainers in effect.
- Invoice date is still used to determine posting projects that are valid, as the date stamped on the invoice; passed to the tax system to calculate tax; passed to receivables to determine the invoice due date and used for the receivable aging reports; and used as the journal transaction date for entries generated by the journalize invoices and journalize invoices actions.
JT-1471260
Rewrite mass actions for processing large volumes and fpr concurrent processing
Project Invoicing and Revenue Management (Mass Actions Concurrent Processing/Efficiency) – Rewrite mass actions (GenerateContractInvoices, RecognizeContractRevenue, JournalizeContractInvoices, and JournalizeContractRevenue) in such a way as to satisfy these criteria:
- Extremely large invoices (1000+ lines) must be processed without timeouts, while smaller invoices must be run without clogging the queue.
- Multiple invocations of the mass jobs cannot be allowed to run concurrently, but the individually spawned jobs must be allowed to run concurrently.
Program/Business class/Process affected:
GenerateContractInvoices, RecognizeContractRevenue, JournalizeContractInvoices, and JournalizeContractRevenue actions
To test this enhancement, run these actions and confirm improved performance: GenerateContractInvoices, RecognizeContractRevenue, JournalizeContractInvoices, and JournalizeContractRevenue.
JT-1478332
Update Project documents on Sample Document Template
Program/Business class/Process affected:
Project Templates
To test this enhancement, verify that Project Templates have the newest version.
JT-1482252
Change constraint for transfer transactions actions
Currently, there is a constraint that Project Ledger generated transaction with system code = PS cannot be transferred. This constraint is too broad and migrated AC only transactions cannot be transferred. Change the constraint so that event codes = AR, BI, BIR, IB, OS, PE, RB, RE, and RER cannot be transferred. Constraint still does not allow projects with system code = PR and events codes PL, BD, and PJ to be transferred. As part of this enhancement, transfer transaction should no longer be appended to the transaction description.
Program/Business class/Process affected:
Transfer Transactions actions
To test this enhancement, verify that projects' generated transactions cannot be transferred. Verify that the words transfer transaction is no longer appended to the transaction description.
JT-1483689