You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Restricting Use of a Transaction Source for Integration-Only in Oracle Fusion Project Costing

Summary:

Hi Everyone,

We have a requirement in Oracle Fusion Project Costing where a specific custom transaction source is intended to be used exclusively by an external integration process.

Current Scenario:

The transaction source is used by an integration to import project costs.
Users also have access to create/upload costs through Manage Unprocessed Costs, ADFDI, and FBDI.
Users are currently able to select the same transaction source that is intended only for integration purposes.

Requirement: We would like to understand whether there is a way to prevent users from manually creating/uploading costs using this transaction source, while still allowing the integration process to use it.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!