Results for “app_id”

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

Overview

The view APPS.ICX_ADMIN_USER_RESP_V belongs to the ICX product family, Oracle iProcurement, and is registered in the ETRM repository with a status of VALID in the APPS schema. Its documented description is unambiguous: the object is Obsolete. It is retained in the E-Business Suite 12.1.1 and 12.2.2 data dictionary purely for backward compatibility, so that legacy code, concurrent programs, or custom extensions that reference the view by name continue to compile and execute without raising ORA-00942 errors. It is not part of any supported functional flow in either release.

The view does not encapsulate any iProcurement administration or user–responsibility data despite the suggestive name. Its definition is a synthetic placeholder built exclusively on SYS.DUAL. Consequently, it has no role in EBS reporting, no role in integration, and cannot be meaningfully joined to other ICX or FND objects. Any report or interface that depends on it for real data will produce only the literal placeholder values described below.

Underlying Base Objects

The ETRM metadata documents exactly one referenced base object: the table DUAL. DUAL is the standard Oracle one-row, one-column pseudo-table owned by SYS, used to satisfy the FROM clause when a query needs to return computed expressions without touching a real entity. Because the view's SQL reduces to a selection over DUAL, it returns at most a single row, and in practice—given the constant expression list—returns precisely one row.

There is no dependency on FND_USER, FND_RESPONSIBILITY, FND_USER_RESP_GROUPS, ICX_ tables, or any other application object. The absence of such dependencies explains the "Obsolete" designation: the view was likely used as a stub or placeholder during development and was never replaced with a functional implementation, or it was formally retired and left behind to avoid breaking dependent objects.

Key Columns

The view exposes two columns, both defined as constant string expressions rather than as selections from real data. The documented view text is:

• RESP_ID — defined as DUMMY||'1'. This is a literal expression concatenating the character DUMMY from DUAL with the string '1', yielding the constant value DUMMY1.
• APP_ID — defined as DUMMY||'2', likewise yielding the constant value DUMMY2.

Neither column carries a real identifier. RESP_ID does not correspond to an FND_RESPONSIBILITY.RESPONSIBILITY_ID, and APP_ID does not correspond to an FND_APPLICATION.APPLICATION_ID. The columns are reserved placeholders matching the naming conventions of responsibility/application identifier pairs, but they contain no reference data and should never be used in joins, lookups, or LOV definitions.

Common Use Cases and Queries

There is no supported business use case for this view. Its only practical purpose is compatibility: validating that a legacy object referencing it still resolves, or confirming the view's retention in the dictionary after upgrade. A diagnostic query such as the following will always return a single row consisting of the two constant values:

• SELECT resp_id, app_id FROM apps.icx_admin_user_resp_v; — returns DUMMY1 and DUMMY2.
• SELECT COUNT(*) FROM apps.icx_admin_user_resp_v; — returns 1 in all environments.
• Querying DBA_VIEWS or ALL_VIEWS for text matching DUMMY confirms the placeholder definition and provides a reliable way to identify other obsolete stub views in the schema.

For genuine iProcurement administration or user–responsibility reporting, the supported replacement approach is to query FND_USER, FND_RESPONSIBILITY, and FND_USER_RESP_GROUPS_DIRECT directly. Since the object is non-functional in both 12.1.1 and 12.2.2, no upgrade path or data migration applies; existing references should be removed and replaced with the appropriate FND base tables.