Results for “eff_to”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The table CZ_DEVL_PRJ_USER_GROUPS is a legacy Configurator (CZ) object that resides in the CZ schema within Oracle EBS 12.1.1 and 12.2.2. Per the documented metadata, the object is marked OBSOLETE and its stated purpose was to assign development projects to MDApp (Models/Configurator application) users. It therefore functions as an intersection or association table that links two principal entities: development projects (CZ_DEVL_PROJECTS) and user groups (CZ_USER_GROUPS).

Although the object remains VALID in the data dictionary, its obsolete status means that it is retained primarily for backward compatibility, historical data retention, and referential integrity purposes rather than for active application logic. In practice, this table is the kind of artifact discovered during EBS upgrades, data migrations, or schema audits, where a consultant or DBA must confirm whether it still participates in any live Configurator workflow.

Regarding Data Vault modeling, the heuristic classification supplied with the metadata is link. This is a modeling suggestion only: the table's composite primary key of two foreign keys (DEVL_PROJECT_ID and USER_GROUP_ID) is characteristic of a link table that resolves a many-to-many relationship between two hubs.

Key Information Stored

The table contains 13 documented columns. The most significant are summarized below.

• DEVL_PROJECT_ID — Foreign key to CZ_DEVL_PROJECTS; identifies the development project being assigned. Part of the composite primary key.
• USER_GROUP_ID — Foreign key to CZ_USER_GROUPS; identifies the user group receiving project access. Part of the composite primary key and the column most commonly referenced in searches for user_group_id.
• DELETED_FLAG — Indicates soft-deletion status, allowing rows to be logically retired without physical removal.
• EFF_FROM / EFF_TO — Effective date range for the assignment, supporting date-tracked security or access windows.
• EFF_MASK — Bitmask or indicator controlling effective-date behavior.
• SECURITY_MASK — Security-related mask governing visibility or access propagation.
• CHECKOUT_USER — Identifies the user who checked out the record, relevant to Configurator's model checkout semantics.
• CREATION_DATE / CREATED_BY — Standard audit columns recording row creation.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification.

The unique index CZ_DEVL_PRJ_USR_GRP_PK on (DEVL_PROJECT_ID, USER_GROUP_ID) is the business-key candidate, enforcing one assignment per project/group pair. No separate surrogate key column is documented.

Common Use Cases and Queries

Because the table is obsolete, the primary use cases are investigative rather than operational.

• Impact analysis before upgrade or decommissioning: determine whether any project/group assignments remain and whether dependent objects still reference them.
• Security audits: reconstruct which user groups were historically granted access to which development projects.
• Data migration: extract legacy assignments to map into current security constructs.

A representative query joining both parent tables:

• SELECT p.DEVL_PROJECT_ID, g.USER_GROUP_ID, a.EFF_FROM, a.EFF_TO, a.SECURITY_MASK
• FROM CZ.CZ_DEVL_PRJ_USER_GROUPS a, CZ.CZ_DEVL_PROJECTS p, CZ.CZ_USER_GROUPS g
• WHERE a.DEVL_PROJECT_ID = p.DEVL_PROJECT_ID AND a.USER_GROUP_ID = g.USER_GROUP_ID AND a.DELETED_FLAG = 'N';

Filtering on EFF_FROM/EFF_TO yields point-in-time assignment reporting, and counting distinct USER_GROUP_ID values per project provides a distribution view.

Related Objects

• CZ_DEVL_PROJECTS — Parent hub for development projects; joined via DEVL_PROJECT_ID.
• CZ_USER_GROUPS — Parent hub for user groups; joined via USER_GROUP_ID.
• CZ_DEVL_PRJ_USR_GRP_PK — The unique index enforcing the composite business key on (DEVL_PROJECT_ID, USER_GROUP_ID).
• Configurator (CZ) MDApp security objects — Legacy user-assignment and model-access constructs that historically consumed this mapping.

Because the table is obsolete, no public APIs are documented as depending on it; any remaining dependencies should be confirmed through the EBS dependency and AOL validation reports during upgrade planning.