Projects in LOV are Not Restricted to Key Members In Pre-Approved Expenditure Batch Form
Last updated on MARCH 08, 2017
Applies to:Oracle Project Costing - Version 12.2.4 and later
Information in this document applies to any platform.
Requirement: Resources are NOT supposed to charge expenditures/ costs or transfer costs to other projects where the resource is not a Key Member. In other words, Resources are supposed to charge costs/transfer costs only for the projects where the person is a Key Member.
The profile option %PA%Cross%Project%Update/View% is set to 'NO' at the Responsibility level to prevent resources from entering/charging expenditures/costs to other projects when the person is not a key member. At Projects Inquiry and Costs Transfer form, the LOV is listing correctly where the user is a Key Member.
Issue: In the Pre-Approved Expenditure Batches entry form, the LOV is listing all the projects from the Project Org Hierarchy, even if the User is not a Key Member for those projects. This will result in User charging costs to other projects where he is not a Key Member.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms