Results for “oe_pc_resps_v”

34 results




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

Overview

OE_PC_RESPS_V is a view owned by the APPS schema in Oracle E-Business Suite, defined within the Order Management (ONT) product. Its documented purpose is to store and present the responsibilities associated with processing constraints. Processing constraints are the configurable rules in Order Management that control whether a user, or a group of users, may change specific order or line attributes after certain workflow states are reached. Because those constraints are enforced by responsibility, the relationship between a constraint and the responsibilities it applies to is a central configuration artifact, and OE_PC_RESPS_V exposes that relationship in a query-friendly form.

The view is read-only and does not itself store data; it consolidates records from the constraint assignment and exclusion tables and joins them to responsibility definitions. From a reporting and integration standpoint it is the natural entry point for administrators and technical consultants who need to audit, document, or migrate processing-constraint security setups. It is also relevant to the commonly searched object FND_RESPONSIBILITY_VL, since the responsibilities shown here are resolved through that view.

Underlying Base Objects

The documented base objects referenced by the view are OE_PC_ASSIGNMENTS (a synonym in APPS), OE_PC_EXCLUSIONS (a synonym in APPS), and FND_RESPONSIBILITY_VL (a view). OE_PC_ASSIGNMENTS holds the responsibilities to which a processing constraint is assigned. OE_PC_EXCLUSIONS holds responsibility-level exclusions that override or remove an assignment. FND_RESPONSIBILITY_VL supplies the translated responsibility name, keyed by RESPONSIBILITY_ID and APPLICATION_ID.

Internally the view is the UNION of two branches. The first branch selects from OE_PC_ASSIGNMENTS, filters out any assignment that has a matching row in OE_PC_EXCLUSIONS via a NOT EXISTS clause, and stamps the literal flag 'A' for assigned. The second branch selects from OE_PC_EXCLUSIONS joined back to OE_PC_ASSIGNMENTS, and stamps the flag 'E' for excluded. Both branches outer-join to FND_RESPONSIBILITY_VL on RESPONSIBILITY_ID and APPLICATION_ID, so a responsibility name is returned when a matching definition exists. The union removes duplicates and presents a single consolidated result set with a uniform column list.

Key Columns

  • ASSIGNMENT_ID — Identifier of the constraint-to-responsibility assignment record; links back to OE_PC_ASSIGNMENTS.
  • CONSTRAINT_ID — The processing constraint to which the assignment or exclusion applies.
  • ASSIGNED_OR_EXCLUDED_FLAG — Literal 'A' when the row originates from the assignment branch, 'E' when it originates from the exclusion branch. This is the discriminator between the two UNION members.
  • RESPONSIBILITY_ID — Foreign key to the responsibility; used in the join to FND_RESPONSIBILITY_VL.
  • RESPONSIBILITY_NAME — Translated responsibility name obtained from FND_RESPONSIBILITY_VL; may be null if no matching responsibility definition is found.
  • APPLICATION_ID — Application owning the responsibility, also part of the join key to FND_RESPONSIBILITY_VL.
  • ROW_ID — The ROWID of the source row (from OE_PC_ASSIGNMENTS or OE_PC_EXCLUSIONS).
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns carried from the source rows.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns available on the underlying assignment and exclusion records.

Common Use Cases and Queries

Typical uses include auditing which responsibilities a given constraint is assigned to, identifying explicitly excluded responsibilities, and producing configuration documentation for a security or Order Management implementation. The following query lists all responsibilities associated with a specific constraint:

SELECT constraint_id, responsibility_name, assigned_or_excluded_flag
FROM apps.oe_pc_resps_v
WHERE constraint_id = :constraint_id
ORDER BY assigned_or_excluded_flag, responsibility_name;

To separate effective assignments from exclusions, filter on the flag. The next query returns only active assignments, which is the set that actually enforces the constraint:

SELECT constraint_id, responsibility_id, responsibility_name
FROM apps.oe_pc_resps_v
WHERE assigned_or_excluded_flag = 'A';

Because the view joins to FND_RESPONSIBILITY_VL, it can also be used to find responsibilities with no resolvable name, indicating orphaned or stale configuration:

SELECT assignment_id, constraint_id, responsibility_id
FROM apps.oe_pc_resps_v
WHERE responsibility_name IS NULL;

When reporting responsibility-level information, recall that the search term fnd_responsibility_vl refers to the definition source this view depends on; it supplies the RESPONSIBILITY_NAME column and is the appropriate object for responsibility attributes not exposed here.