Reference for Identity

This section provides information about views within Resource Analytics Identity and their columns, data types, keys, and the referred view and column names. The following views are available:

The suffixes in the view names specify the view type:

• FACT_V: Fact
• DIM_V: Dimension
• HIERARCHY_V: Denormalized hierarchy view

This section provides diagrams that define the logical relationship of different dimension views.

The contents of each view and their relationships are listed in the following file: identity views.

Relationships exist among dimensions. Dimensions can be joined directly to each other. This diagram shows the relationship between dimension views.

COMPARTMENT_DIM_V

These diagrams show the relationship of the fact view with different dimension views.

IDENTITY_DOMAIN_FACT_V

IDENTITY_DYNAMIC_GROUP_FACT_V

IDENTITY_GROUP_FACT_V

IDENTITY_NETWORK_SOURCES_FACT_V

IDENTITY_POLICY_FACT_V

IDENTITY_PROVIDER_FACT_V

IDENTITY_USER_FACT_V

Relationships exist among dimensions. Dimensions can be joined directly to each other. These diagrams show the relationship between dimension views.

IDENTITY_AUTH_TOKEN_DIM_V

IDENTITY_CUSTOMER_SECRET_KEY_SUMMARY_DIM_V

IDENTITY_IDP_GROUP_MAPPING_DIM_V

IDENTITY_MFA_TOTP_DEVICE_DIM_V

IDENTITY_PROVIDER_GROUP_SUMMARY_DIM_V

IDENTITY_SMTP_CREDENTIAL_DIM_V

IDENTITY_TAG_DEFAULT_DIM_V

IDENTITY_TAG_NAMESPACE_DIM_V

IDENTITY_USER_GROUP_MEMBERSHIP_DIM_V

Sample queries for Identity.

SELECT C.ID AS COMPARTMENT_ID, C.NAME AS COMPARTMENT_NAME, T.ID AS TENANCY_ID, T.NAME AS TENANCY_NAME,
 T.DESCRIPTION AS TENANCY_DESCRIPTION, T.TIME_CREATED AS TENANCY_TIME_CREATED
FROM OCIRA.COMPARTMENT_DIM_V C
LEFT JOIN OCIRA.TENANCY_DIM_V T
ON C.OCIRA_ROOT_COMPARTMENT_KEY = T.OCIRA_TENANCY_KEY;

SELECT ID, LVL1_COMPARTMENT_ID, LVL1_COMPARTMENT_NAME
FROM OCIRA.COMPARTMENT_HIERARCHY_V;

SELECT DOMAIN_ID, DISPLAY_NAME, LIFECYCLE_STATE
FROM OCIRA.IDENTITY_DOMAIN_FACT_V F
WHERE LIFECYCLE_STATE = 'ACTIVE';

SELECT DYNAMIC_GROUP_ID, NAME, LIFECYCLE_STATE
FROM OCIRA.IDENTITY_DYNAMIC_GROUP_FACT_V F
WHERE LIFECYCLE_STATE = 'ACTIVE';

SELECT GROUP_ID, NAME, USER_COUNT, LIFECYCLE_STATE
FROM OCIRA.IDENTITY_GROUP_FACT_V F
WHERE LIFECYCLE_STATE = 'ACTIVE';

SELECT NETWORK_SOURCE_ID, NAME, LIFECYCLE_STATE
FROM OCIRA.IDENTITY_NETWORK_SOURCES_FACT_V F
WHERE LIFECYCLE_STATE = 'ACTIVE';

SELECT POLICY_ID, NAME, LIFECYCLE_STATE
FROM OCIRA.IDENTITY_POLICY_FACT_V F
WHERE LIFECYCLE_STATE = 'ACTIVE';

SELECT PROVIDER_ID, NAME, MAPPED_GROUP_COUNT, LIFECYCLE_STATE
FROM OCIRA.IDENTITY_PROVIDER_FACT_V F
WHERE LIFECYCLE_STATE = 'ACTIVE';

SELECT IDENTITY_PROVIDER_ID, COUNT(USER_ID) AS USER_COUNT
FROM OCIRA.IDENTITY_USER_FACT_V F
GROUP BY IDENTITY_PROVIDER_ID;

The Customer Experience Semantic Model Lineage spreadsheet and Metric Calculation Logic spreadsheet for Identity provide an end-to-end data lineage summary report for physical and logical relationships in your data.

For more information, see Data Lineage.

This section provides information on the subject areas with data you maintain in Identity. These subject areas, with their corresponding data, are available for you to use when creating and editing analyses and reports. The information for each subject area includes:

• Description of the subject area.

• Business questions that can be answered by data in the subject area, with a link to more detailed information about each business question.

• Job-specific groups and duty roles that can be used to secure access to the subject area, with a link to more detailed information about each job role and duty role.

• Primary navigation to the work area that's represented by the subject area.

• Time reporting considerations in using the subject area, such as whether the subject area reports historical data or only the current data. Historical reporting refers to reporting on historical transactional data in a subject area. With a few exceptions, all dimensional data are current as of the primary transaction dates or system date.

• The lowest grain of transactional data in a subject area. The lowest transactional data grain decides how data are joined in a report.

• Special considerations, tips, and things to look out for in using the subject area to create analyses and reports.