Search Results po_control_groups_u2

Overview

PO.PO_CONTROL_GROUPS_ALL is a key Purchasing application table that stores the control groups defined within an Oracle E-Business Suite implementation. Control groups represent a specific level of authorization within an organization, and each group defines the restrictions that may be applied to a control function and, by extension, to a Job or Position. The table contains one row per control group defined, making it a foundational reference object for purchasing document security and approval routing.

Control groups are consumed by the Purchasing controls framework, where they are assigned to control functions and mapped to jobs or positions. A single control group may be assigned to many functions, so the table functions as a reusable authorization unit rather than a transactional record.

From a Data Vault modeling perspective, the mined FK structure suggests a hub-leaning classification, since PO_CONTROL_GROUPS_ALL acts as the parent of independent control-related entities keyed by CONTROL_GROUP_ID. In EBS 12.1.1 and 12.2.2 the table is owned by the PO schema and resides in the APPS_TS_TX_DATA tablespace, with unique indexes in APPS_TS_TX_IDX.

Key Information Stored

The primary key of the table is PO_CONTROL_GROUPS_PK, defined on CONTROL_GROUP_ID, which is the surrogate unique identifier for each control group. Two documented unique indexes act as business-key candidates: PO_CONTROL_GROUPS_U1 on CONTROL_GROUP_ID and PO_CONTROL_GROUPS_U2 on (CONTROL_GROUP_NAME, ORG_ID), confirming that a control group name must be unique within an operating unit.

• CONTROL_GROUP_ID — surrogate primary key and unique identifier for the control group.
• CONTROL_GROUP_NAME — the user-facing name of the control group, up to 80 characters.
• ORG_ID — the operating unit that owns the control group; combined with the name it forms the second unique key.
• ENABLED_FLAG — indicates whether the control group is active and available for assignment.
• DESCRIPTION — free-text description of the group's authorization purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns identifying when and by whom the row was created or last changed.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program columns recording the last program that altered the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns for customer-defined extensions.

The documented physical schema lists 30 columns, most of which are the WHO, concurrent, and DFF attributes above.

Common Use Cases and Queries

Typical usage centers on listing active control groups for a given operating unit, resolving a control group name to its ID for downstream joins, and validating the uniqueness of a proposed name. Because PO_CONTROL_GROUPS_ALL is a reference table, it is frequently joined to PO_CONTROL_RULES and PO_POSITION_CONTROLS_ALL to report the security configuration applied to a job or position.

Sample query — active control groups by operating unit:

• SELECT cg.control_group_id, cg.control_group_name, cg.enabled_flag FROM po.po_control_groups_all cg WHERE cg.org_id = :org_id AND cg.enabled_flag = 'Y' ORDER BY cg.control_group_name;

Sample query — control rules assigned to each group:

• SELECT cg.control_group_name, cr.control_group_id FROM po.po_control_groups_all cg, po.po_control_rules cr WHERE cg.control_group_id = cr.control_group_id AND cg.org_id = :org_id;

Reporting scenarios include documenting which jobs and positions carry which authorization restrictions, auditing enabled versus disabled control groups, and reconciling control-group definitions across operating units.

Related Objects

The following objects reference PO_CONTROL_GROUPS_ALL through CONTROL_GROUP_ID and are the most significant dependents for configuration and reporting.

• PO_CONTROL_RULES — joins on PO_CONTROL_RULES.CONTROL_GROUP_ID → PO_CONTROL_GROUPS_ALL. Defines the rules applied within each control group.
• PO_POSITION_CONTROLS_ALL — joins on CONTROL_GROUP_ID. Maps control groups to positions and jobs.
• PO_CONTROL_RULES_EFC — joins on CONTROL_GROUP_ID; the EFC counterpart used for the controls framework.
• FND_USER — via LAST_UPDATED_BY / CREATED_BY foreign keys, resolving the user who maintained the row.
• FND_CONCURRENT_REQUESTS — via REQUEST_ID, identifying the concurrent program that last updated the row.
• FND_APPLICATION — via PROGRAM_APPLICATION_ID, resolving the owning application of the concurrent program.
• FND_LOGINS — via LAST_UPDATE_LOGIN, resolving the operating-system login of the updating user.