Last updated on MARCH 08, 2017
Applies to:Oracle Project Costing - Version 12.1.3 and later
Information in this document applies to any platform.
Users set profile options PA: Cross Project User -- Update and PA: Cross Project User -- View in order to allow GL Users to view project data but not make updates to it.
They also set the following profile options in the Chewy Test instance for OTP GL USER
PA: Cross Project User -- Update = No
PA: Cross Project User -- View = Yes
and set the following profile options in the Chewy Test instance for OTP GL Super User
Since the menu they are using for each responsibility uses the Expenditure Inquiry -All feature they are expecting the data that is queried to be the same but it is proving to differ. The data that is returned when the PA: Cross Project User -- Update is set to No does not pull amounts for Labor when querying by project.
However if they query by project and category labor it pulls and displays the Labor costs.
The OTP GL Super user pulls the correct data either by project or by project and category labor.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms