Unprocessed Project Cost Exception Control for Predefined Sources

Update or delete unprocessed project cost exceptions from predefined transaction sources, such as Oracle Fusion Payables and Oracle Fusion Time and Labor, directly in the Manage Unprocessed Costs page. Previously, customers had to contact Oracle Support to obtain a hash key and set up a special administrator profile option for each individual exception transaction that required an update or deletion, a time-consuming process that had to be repeated for every new exception.

With this feature, organizations can assign delivered data privileges to select users, empowering them to resolve exception transactions without Oracle Support intervention. Each time an exception is updated or deleted, an audit record of the transaction data is automatically captured for reconciliation and compliance purposes. Access is strictly limited to users with the necessary privileges, ensuring only authorized personnel can perform these actions.

Important: Oracle strongly recommends resolving the root cause of exception transactions whenever possible. Editing or deleting unprocessed project cost exceptions from predefined sources should be considered only as a last resort, as it may lead to reconciliation issues or additional exceptions in the future.

This feature offers the following business benefits:

• Resolve unprocessed cost exceptions from predefined sources efficiently and securely, reducing time spent engaging with Oracle Support and enabling timely project cost processing and period close activities.
• By providing granular privileges, organizations can control who is allowed to perform these exception-handling actions, improving operational flexibility while maintaining oversight and auditability.

Steps to enable and configure

1. Create a new custom data security policy containing either the edit or delete data privilege, or both.
2. Assign the custom data security policy to seeded or custom job roles.
3. Assign your seeded or custom job roles to selected users.

Worked Example

Vision Operations wants to allow selected project accountants in their organization to be able to edit unprocessed project cost exceptions for predefined transaction sources. However, they don't allow these select users to delete any unprocessed cost transactions for predefined sources. Vision Operations secures access to unprocessed project costs based on business unit access granted to project accountants using the Manage Data Access for Users setup and maintenance task. This data security policy will apply to the new "super user" project accountants as well; the only difference for users with the new "super user" project accountant job role will be the ability to edit unprocessed project cost exceptions for predefined transaction sources.

Steps to implement:

1. Create a new Project Accountant Super User job role by copying the seeded Project Accountant job role.
2. Create a new data security policy for the Project Unprocessed Cost Transaction for Table PJC_TXN_XFACE_ALL database object that includes the new Edit Unprocessed Transaction Exceptions Data privilege and assign this policy to the new custom Project Accountant Super User job role.

Data Security Policy with the Edit Unprocessed Costs for Predefined Sources Data Privilege

3. Assign the new custom Project Accountant Super User job role to selected users.
4. Assign Business Unit data access to the users having the new custom Project Accountant Super User job role.

A user having the new custom Project Accountant Super User role that allows updates to unprocessed project cost exceptions for predefined sources will see the following when querying an exception for an Oracle Fusion Payables transaction:

Edit Action Enabled for the Oracle Fusion Payables Transaction Using the Custom Role

Whereas another project accountant with the same business unit data access who doesn't have the "super user" job role would see the following:

Edit and Delete Actions Disabled for the Oracle Fusion Payables Transaction Using the Seeded Role

Tips and considerations

• Only grant the new privileges to experienced users who understand the reconciliation and data integrity implications of editing or deleting a transaction which originated in another Oracle application.
• The new privileges delivered with this feature don't apply to the Oracle Fusion Projects predefined transaction source. The ability to update or delete unprocessed costs for the Oracle Fusion Projects transaction source is controlled by the document entry's Allow Modifications to Unprocessed Transactions option.
• The new privileges are only supported in the Manage Unprocessed Costs page on individual transactions. Even with the new privileges granted, a user can't update or delete an unprocessed cost from a predefined transaction source using the Unprocessed Project Cost REST API or deletion using the Delete Costs button in the Manage Unprocessed Costs page.
• Deleting a transaction, such as a supplier invoice, which has already passed budgetary controls in its source application and has had funds reserved won't result in the release of the reserved funds.
• Before an update or deletion of an unprocessed cost exception from a predefined transaction source is saved, a snapshot of the transaction's current attributes is recorded in the PJC_TXN_XFACE_AUDIT_ALL table for audit purposes.
• Oracle can't recover a deleted or updated unprocessed project cost transaction using the information in the audit table.

Key resources

• Refer to the Securing ERP Help Center document for security topics, including the Security in Oracle Project Management section.

Access requirements

To use this feature, you need these data privileges:

• Edit Unprocessed Transaction Exceptions Data (PJC_EDIT_UNPROCESSED_C0ST_EXCEPTIONS_PRIV)
• Delete Unprocessed Transaction Exceptions Data (PJC_DELETE_UNPROCESSED_C0ST_EXCEPTIONS_PRIV)