Cant Use A Synonym As A Table Name In Data Properties When Creating New General Level
Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
Customer is trying to create a new general level called t_ep_pitem_parent
He has created a synonym t_ep_pitem_parent that points to table t_ep_pitem_child
When they try to create the general level in the business modeler, the synonym t_ep_pitem_parent is not visible in the list of values. Initially it was thought that it was a permission issue but they say that the permissions of the synonym should be granted already. The user is the Demantra schema owner DM that is creating the level. The synonym is owned by dm, and so is the target table. All the permissions should be high enough. When they try some simple pl/sql using the synonym instead of the table name they can update, delete, select, and insert into the synonym.
But they do see that configuration for seeded t_ep_cto_parent uses a synonym. It is a synonym for t_ep_cto_parent that points to t_ep_cto child. This is a seeded one
So does that mean that there is the limitation on the level creation tool that it cannot see a synonym that a user has created, and can see and use only the ones that oracle has created like in the case of t_ep_cto_parent ?
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