Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.CFG_ADDL_GRANTS
Table FPSINPUT.CFG_ADDL_GRANTS"
All grants in the FPS DWH are set automatically based on the logic in BLD_PRIVILEGES but occasionally a site will need to add grants, particularly to select from FPSAPP objects in FPSRPT. This is generic so we can add any site specific privilege.
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
-
Primary key: OBJECT_NAME, GRANTEE, PRIVILEGE
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
OBJECT_NAME |
VARCHAR2(30) |
N |
This could be an object name (we will disable loading of that object in the scheduled jobs), a load job (we will disable loading of all objects in that scheduled job), an FPSAPP prefix (we will disable loading of all objects with that prefix), a constraint (we can explain why it is permanently disabled), or a trigger (technically an object so we can get away with omitting this from the column name and also to explain why it is permanently disabled). (* from FPSADMIN.CFG_DISABLED) |
|
GRANTEE |
VARCHAR2(30) |
N |
User to whom the privilege needs to be granted |
|
PRIVILEGE |
VARCHAR2(40) |
N |
Privilege needed to be granted in caps like SELECT. |