Unprocessed Project Cost Exception Update and Deletion for Predefined Sources

Update or delete unprocessed project cost exceptions from predefined transaction sources on the Manage Unprocessed Costs page. Resolve exceptions from sources such as Oracle Fusion Payables and Oracle Fusion Time and Labor without Oracle Support intervention.

Use this capability to:

• Resolve unprocessed cost exceptions efficiently without engaging Oracle Support
• Enable timely project cost processing and support period close activities
• Control access using granular data privileges while maintaining auditability
• Improve operational flexibility by empowering selected users to handle exceptions

Note: Resolve the root cause of exception transactions whenever possible. Editing or deleting unprocessed project cost exceptions from predefined sources should be used only as a last resort, as it may result in reconciliation issues or additional exceptions.

Access Requirements

To use this feature, assign the following data privileges to users through job roles:

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

Grant these privileges through custom data security policies assigned to seeded or custom job roles.

How to Control and Manage Unprocessed Cost ExceptionsSet Up Access

1. Create a data security policy

   Create a new policy that includes either or both:

   • Edit Unprocessed Transaction Exceptions Data
   • Delete Unprocessed Transaction Exceptions Data

2. Assign the policy to job roles

   Attach the policy to seeded or custom job roles.

3. Assign roles to users

   Grant the updated roles to selected users who should manage exception transactions.

4. Assign business unit access

   Ensure users have appropriate business unit access using the Manage Data Access for Users setup.

Perform Exception Updates or Deletions

1. Navigate to the Manage Unprocessed Costs page.
2. Query the unprocessed cost exception transaction from a predefined source.
3. Based on assigned privileges:
   • Update the transaction details, or
   • Delete the transaction
4. Save the changes.

A snapshot of the transaction is automatically recorded for audit purposes before the update or deletion is saved.

Example

Vision Operations wants to allow selected project accountants to update unprocessed project cost exceptions from predefined sources but not delete them.

To achieve this:

1. Create a custom job role, Project Accountant Super User, by copying the seeded Project Accountant role.
2. Create a data security policy that includes the Edit Unprocessed Transaction Exceptions Data privilege.
3. Assign the policy to the new custom role.
4. Assign the role to selected users.
5. Provide business unit data access to these users.

Users with this custom role can update exception transactions on the Manage Unprocessed Costs page. Other project accountants with the same business unit access but without the custom role can view transactions but cannot edit or delete them.

Tips and Considerations

• Restrict access to qualified users

  Grant edit or delete privileges only to experienced users who understand reconciliation and data integrity implications.

• Understand scope limitations

  These privileges don’t apply to the Oracle Fusion Projects predefined transaction source. For that source, control updates using the Allow Modifications to Unprocessed Transactions option on the document entry.

• Use only supported interfaces

  You can update or delete transactions only from the Manage Unprocessed Costs page and at the individual transaction level.

  These actions aren’t supported through:

  • REST APIs
  • The Delete Costs button

• Consider budgetary control impact

  Deleting a transaction that has already passed budgetary controls and reserved funds in the source application doesn’t release those funds.

• Review audit behavior

  Before saving changes, the application records a snapshot of the transaction in the PJC_TXN_XFACE_AUDIT_ALL table.

• Be aware of data recovery limitations

  Deleted or updated transactions can’t be recovered using audit table data.

Assign data privileges to selected users to allow them to manage exception transactions. Each update or deletion automatically records an audit snapshot of the transaction for reconciliation and compliance purposes. Access is restricted to authorized users through role-based security.