In some circumstances, you may wish to create a schema that has limited or read-only access to Oracle E-Business Suite data.
Warning: Since the APPS schema has all privileges to all Oracle E-Business Suite objects, you should never give users direct access to this schema.
You will need to grant access on objects to the user schema from the base product schema.
Note: You may need to re-grant access if the underlying object is dropped and recreated.
Consequently, if you connect directly to a schema, the rows returned by the view may be different from those returned when you are running in an Oracle E-Business Suite environment. For example, a view may reference a profile option: when accessed from SQL*Plus, the site value of the profile option will be used, rather than the setting for a particular Oracle E-Business Suite user.
Warning: Since the APPS schema has all privileges to all Oracle E-Business Suite objects, you should never give users direct access to this schema.
You will need to grant access on objects to the user schema from the base product schema.
Note: You may need to re-grant access if the underlying object is dropped and recreated.
Schemas and Data Access
Some views access packages or functions, where the value returned by the package or function may depend on the environment having been set up properly. The environment is initialized automatically when accessing Oracle E-Business Suite through the Sign-On screen, or when using concurrent processing with Oracle Reports or SQL scripts.Consequently, if you connect directly to a schema, the rows returned by the view may be different from those returned when you are running in an Oracle E-Business Suite environment. For example, a view may reference a profile option: when accessed from SQL*Plus, the site value of the profile option will be used, rather than the setting for a particular Oracle E-Business Suite user.
No comments:
Post a Comment