Results for “xdp_action_codes”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The XDP_ACTION_CODES table resides in the XDP schema, which is associated with the Oracle Provisioning module in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The ETRM product documentation explicitly states that this table is "Not used," indicating that it is a legacy or inactive object retained in the schema for backward compatibility rather than an actively maintained provisioning entity. Despite this designation, the table remains VALID in the data dictionary and carries a complete physical definition, including primary keys, unique constraints, and foreign key relationships, which suggests it may still be referenced by dependent objects or customized extensions.
Functionally, XDP_ACTION_CODES serves as a reference or lookup table for action codes used within provisioning workflows. These codes typically represent discrete actions that can be performed against a service, subscription, or provisioning request. Under a heuristic Data Vault classification mined from its foreign key structure, this table leans toward a hub role: it holds a stable business key (ACTION_CODE) surrounded by descriptive and auditing attributes, which is characteristic of a hub entity anchoring related satellites and links.
Key Information Stored
The table contains nine documented columns. The most significant are:
- ACTION_CODE_ID — The surrogate primary key (XDP_ACTION_CODES_PK) that uniquely identifies each action code record and is the target of foreign keys from dependent tables.
- ACTION_CODE — The business-key candidate, enforced by unique index XDP_ACTION_CODES_U2 (in combination with ZD_EDITION_NAME). This is the human-readable code representing the provisioning action.
- SECURITY_GROUP_ID — A foreign key referencing FND_SECURITY_GROUPS, used to scope record visibility and access control across multiple operating units or security profiles.
- ZD_EDITION_NAME — The editioning column introduced in 12.2.2 for online patching support; it participates in both unique indexes (U1 and U2) and distinguishes editions of the same logical record.
- CREATED_BY, CREATION_DATE — Standard WHO columns capturing the creator and creation timestamp.
- LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the last modification user, timestamp, and login session.
Notably, the table carries no descriptive name or description column of its own; translated or descriptive text is stored in the companion table XDP_ACTION_CODES_TL, which references ACTION_CODE_ID. The two unique indexes (U1 on ACTION_CODE_ID and ZD_EDITION_NAME; U2 on ACTION_CODE and ZD_EDITION_NAME) confirm the surrogate/business-key duality common to EBS reference entities.
Common Use Cases and Queries
Although the table is documented as unused, developers and DBAs may encounter it when tracing provisioning logic, resolving orphaned foreign keys, or auditing legacy reference data. Typical queries include retrieving all action codes for a given security group:
SELECT action_code_id, action_code FROM xdp.xdp_action_codes WHERE security_group_id = :p_security_group_id;- Joining to the translation table for descriptive labels:
SELECT a.action_code, t.description FROM xdp.xdp_action_codes a, xdp.xdp_action_codes_tl t WHERE a.action_code_id = t.action_code_id AND t.language = USERENV('LANG'); - Identifying actions referenced by service validation:
SELECT DISTINCT action_code FROM xdp.xdp_action_codes a, xdp.xdp_service_val_acts v WHERE a.action_code_id = v.action_code_id; - Edition-aware lookups filtering on ZD_EDITION_NAME for 12.2.2 environments with online patching enabled.
Reporting use cases center on inventory of action codes, validation of referential integrity, and impact analysis before deprecating legacy provisioning customizations.
Related Objects
The ETRM metadata identifies several direct relationships anchored on ACTION_CODE_ID:
- XDP_ACTION_CODES_TL — The translation (satellite) table storing language-specific descriptions; joined on ACTION_CODE_ID.
- XDP_SERVICE_VAL_ACTS — Links action codes to service validation rules; joined on ACTION_CODE_ID.
- FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for access control scoping.
- XDP_ACTION_CODES_PK / U1 / U2 — Primary and unique constraints enforcing identity and business-key uniqueness.
Together these objects form the reference backbone for provisioning action metadata, even where the base table is no longer actively maintained.
-
Not used
-
Not used
-
TABLE: XDP.XDP_ACTION_CODES 12.1.1
-
TABLE: XDP.XDP_ACTION_CODES 12.2.2
-
VIEW: XDP.XDP_ACTION_CODES# 12.2.2
-
VIEW: XDP.XDP_ACTION_CODES# 12.2.2
-
12.2.2 DBA Data 12.2.2
-
View: XDP_ACTION_CODES_VL 12.1.1
Not implemented in this database·Explore XDP module →
-
XDP_SERVICE_VAL_ACTS is used to define the valid service actions for a given service
-
XDP_SERVICE_VAL_ACTS is used to define the valid service actions for a given service
-
12.2.2 DBA Data 12.2.2
-
View: XDP_ACTION_CODES_VL 12.2.2
Not implemented in this database·Explore XDP module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
Not used
-
Not used
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - XDP Tables and Views 12.2.2
Fulfillment Worklist Details
-
eTRM - XDP Tables and Views 12.1.1
Fulfillment Worklist Details
-
12.2.2 DBA Data 12.2.2
-
eTRM - XDP Tables and Views 12.2.2
Fulfillment Worklist Details
-
12.2.2 DBA Data 12.2.2
-
eTRM - XDP Tables and Views 12.1.1
Fulfillment Worklist Details
-
12.2.2 DBA Data 12.2.2