To configure the finance lock settings:
Important!
Oracle recommends not changing the enforcement mode on a live production system. When the mode is changed, it takes effect only for new projects created from that point of time. Old projects continue in the previous enforcement mode and cannot be changed.
Notes:
The following table lists the supported options for both the Strict and Limited modes.
Supported Options | Strict | Limited |
---|---|---|
Enforcement | Always Guaranteed | Not Guaranteed. Guaranteed only when used with AET set to Effort from Finances, finances are edited in the monthly mode, and resource rates are explicitly overridden at the project level. Enforcement is through manual process. |
Resource labor rate, role, labor rate changes | Not allowed if it can affect a finance lock/close period in any project. | System does not check for violation and finance lock/close period integrity is not protected. |
Currency conversion rate (exchange rate) changes | Not allowed if it can affect a finance lock/close period in any project. | System does not check for violation and finance lock/close period integrity is not protected. |
Supported AETs | Effort at Resource Level (Detail), Effort from Timesheet, and Effort from Finances | All AET options |
Unsupported AETs | Duration& Resource % availability, Effort at Activity Level- Equal % Distribution, Effort at Activity Level- Unequal % Distribution, and Effort at Resource Level (Summary) | None |
Editing finances in yearly or aggregate (annualized) mode | Not allowed | Allowed. Finance lock may not be protected. |
Managing Finance Approval Templates
Managing Finance Element Types
Managing Activity Labor Cost Capitalization Settings
Updating Global Finance Constants
Legal Notices
Copyright © 2000, 2016,
Oracle and/or its affiliates. All rights reserved.
Last Published Thursday, December 01, 2016