Results for “ap_web_proxy_assignments”

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

Overview

AP_WEB_PROXY_ASSIGNMENTS is a Payables module table owned by the AP schema that stores reporting access rights relationships within Oracle E-Business Suite. Its documented purpose is to record the delegation of reporting or approval authority from one application user to another, scoped to a specific responsibility, application, or security group, and bounded by an effective date range. Although the table resides in the AP schema and is most closely associated with the Payables workbench and expense-reporting approval flows, its design is generic: the foreign keys to FND_USER, FND_APPLICATION, and FND_SECURITY_GROUPS indicate that it functions as a cross-application delegation registry rather than an AP-only construct.

The table is present and marked VALID in both the 12.1.1 and 12.2.2 ETRM documentation. In 12.2.2 the documented physical schema contains 14 columns and two unique indexes. From a heuristic Data Vault modeling perspective, AP_WEB_PROXY_ASSIGNMENTS is best classified as a link table: it resolves many-to-many relationships among users (assignor and assignee), responsibilities, applications, and security groups, with the effective dating and audit attributes behaving as link-level satellite attributes. This classification is a modeling suggestion derived from the FK structure, not an Oracle-certified designation.

Key Information Stored

The table is anchored by a surrogate primary key, ASSIGNMENT_ID, enforced through the AP_WEB_PROXY_ASSIGNMENTS_PK constraint and the AP_WEB_PROXY_ASSIGNMENTS_U1 unique index. The business-key candidate is captured by the AP_WEB_PROXY_ASSIGNMENTS_U2 unique index over ASSIGNOR_ID, ASSIGNEE_ID, RESPONSIBILITY_ID, and ASSIGNMENT_TYPE, which prevents duplicate delegation records for the same user pair and responsibility context.

• ASSIGNMENT_ID — surrogate primary key uniquely identifying each proxy assignment row.
• ASSIGNOR_ID — the FND_USER granting the access; the delegating party.
• ASSIGNEE_ID — the FND_USER receiving the delegated reporting access; the proxy.
• RESPONSIBILITY_ID — the responsibility within which the delegated access applies.
• RESPONSIBILITY_APP_ID — foreign key to FND_APPLICATION, identifying the owning application of the responsibility.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, restricting the delegation to a security group scope.
• ASSIGNMENT_TYPE — classifies the nature of the delegation (for example, reporting versus approval access), and participates in the U2 business key.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — the validity window during which the proxy assignment is active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE — standard EBS audit columns recording creation and last modification of each row.

Common Use Cases and Queries

The principal use case is determining who may act on behalf of another user for reporting or approval purposes, and whether that delegation is currently in force. The effective date columns make "as-of" reporting straightforward. A typical pattern joins both user roles back to FND_USER and filters on the active window:

• Identify active proxies for a given assignor: select ASSIGNEE_ID from AP_WEB_PROXY_ASSIGNMENTS where ASSIGNOR_ID = :user_id and SYSDATE between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
• Resolve the assignee name by joining FND_USER on ASSIGNEE_ID = USER_ID.
• Audit expired or future-dated delegations by comparing EFFECTIVE_END_DATE and EFFECTIVE_START_DATE to SYSDATE.
• Scope delegation reporting by application via RESPONSIBILITY_APP_ID, and by security group via SECURITY_GROUP_ID.
• Detect conflicting or duplicate grants using the U2 key columns (ASSIGNOR_ID, ASSIGNEE_ID, RESPONSIBILITY_ID, ASSIGNMENT_TYPE).
• Feed downstream approval-routing or workload reports that need to know the effective approver for a responsibility.

Related Objects

The FK metadata identifies the core related objects; these are the most significant for joins and dependency analysis.

• FND_USER — referenced twice, via ASSIGNOR_ID and ASSIGNEE_ID; the primary user dimension.
• FND_APPLICATION — referenced via RESPONSIBILITY_APP_ID; supplies the application owning the responsibility.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; scopes the assignment to a security group.
• FND_RESPONSIBILITY — the responsibility identified by RESPONSIBILITY_ID, used to resolve responsibility names and menus.
• AP_WEB_PROXY_ASSIGNMENTS_PK / AP_WEB_PROXY_ASSIGNMENTS_U1 / AP_WEB_PROXY_ASSIGNMENTS_U2 — the constraints and unique indexes that define row identity and the business key.
• AP Web Expenses and Payables workbench components — the functional consumers that read this table when evaluating delegated reporting access.