Project Analytics - Task Dimension/Project Cost Fact - Billable Flag Logic
762114Dec 13 2010 — edited Dec 24 2010Hello All ..
I am trying to understand what the reasoning is behind the logic being used on the BILLABLE_FLG field that is populated into Oracle Project Analytics warehouse tables W_TASK_D and W_PROJ_COST_LINE_F.
The logic for both W_TASK_D.BILLABLE_FLG and W_PROJ_COST_LINE_F.BILLABLE_FLG is the following:
IIF(PROJECT_TYPE_CLASS_CODE = 'CAPITAL', 'N', IIF(BILLABLE_FLAG = 'Y', 'Y','N'))
At my current client they view this as being the exact opposite of how they view billable flag. They consider everything that is capitalizeable (PROJECT_TYPE_CLASS_CODE = 'CAPITAL') to be billable and therefore should get a billable flag = 'Y' (whereas here it is defualted to 'N').
Can someone provide me with the functional reasoning for defaulting the Billable Flag to 'N' if the class code = CAPITAL? Why is the billable flag not just passed through as is from the source?
I know that there is also a Capitalizeable Flag with the opposite logic, but does Oracle consider Capitalizeable and Billable to be two separate things?
Thanks in advance.
k
Edited by: user_K on Dec 13, 2010 4:30 PM