Last updated on JANUARY 31, 2017
Applies to:Business Intelligence Applications Consumer - Version 18.104.22.168 and later
Information in this document applies to any platform.
We are running Bi Apps 7964 version and facing issues with BUYER_WID in W_PURCH_COST_F. It is populating correctly except in the scenario below.
o PO# 920003589 created on “04-MAY-13” , agent_id =”669”
o User updated the Buyer in the PO on “02-MAY-14” and agent_id =”9795”.
o The effective start date for the new buyer is “27-MAR-14”
In the above scenario the PO creation date is earlier than the buyer (employee) effective start date, because of this, even though we have buyer in w_employee_d dim, buyer_wid is populating as 0 in w_purch_cost_f.
We believe functionally this is valid scenario in Sourcing. Could please let us know how can we fix buyer_wid so that it doesn't populate with a 0?
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