Results for “ast_switch_data”

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

Overview

The AST.AST_SWITCH_DATA table is a TeleSales (AST) module object that stores configuration metadata describing how customer data is presented on a Computer Telephony Integration (CTI) screen-pop driven by a CGI switch. In Oracle E-Business Suite 12.1.1 and 12.2.2, the table acts as the display-mapping definition layer that binds an agent's inbound or outbound call event to a set of field-level presentation rules, controlling which contact attributes are surfaced to the telesales agent when a call is delivered.

From a Data Vault modeling perspective, the metadata's heuristic classification places AST_SWITCH_DATA as standalone. This suggests that the table functions as a self-contained reference or configuration entity rather than participating in a hub-and-link structure; it holds descriptive rules keyed by its own surrogate identifier and does not appear to serve as a transaction hub or a many-to-many resolution link. The classification should be treated as a modeling suggestion, not a documented architectural assertion.

Key Information Stored

The table is documented with 35 physical columns. The most significant are:

• SWITCH_DATA_ID — surrogate primary key, enforced by the AST_SWITCH_DATA_PK constraint. This is the technical identifier and the join anchor for downstream references.
• CGI_SWITCH_ID — foreign key to AST_CGI_SWITCHES, identifying the specific CGI switch configuration this metadata row belongs to. This is the primary business-key candidate, since the display rules are meaningful only in the context of a given switch.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing which operating unit or security group may see the mapped data, consistent with multi-org–aware configuration tables.
• ENABLED_FLAG — controls whether the metadata row is active and therefore applied at screen-pop time.
• SORT_ORDER — determines display sequence of the mapped fields.
• FIRST_NAME_YN, LAST_NAME_YN, ADDRESS_YN, CITY_YN, STATE_YN, COUNTRY_YN, ZIP_YN — boolean toggle columns that define which contact and address attributes are rendered for the switch.
• PROGRAM_ID — standard concurrent-program or source-program identifier.

Standard EBS audit columns are present: OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Fifteen descriptive ATTRIBUTE columns (ATTRIBUTE_CATEGORY through ATTRIBUTE14, plus ATTRIBUTE15 via the extensibility pattern) provide a DFF-style overflow mechanism for customer-specific extensions.

Common Use Cases and Queries

Typical usage centers on retrieving the active field-presentation rules for a given switch prior to screen-pop rendering. A representative query joins the metadata to its switch parent:

• Determine which fields display for an inbound call: SELECT sd.switch_data_id, sd.sort_order, sd.first_name_yn, sd.last_name_yn, sd.address_yn, sd.city_yn, sd.state_yn, sd.country_yn, sd.zip_yn FROM ast.ast_switch_data sd, ast.ast_cgi_switches cs WHERE sd.cgi_switch_id = cs.cgi_switch_id AND sd.enabled_flag = 'Y' AND sd.security_group_id = :security_group_id ORDER BY sd.sort_order;
• Audit configuration changes by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY within a date window.
• Report on disabled or orphaned metadata rows where ENABLED_FLAG = 'N' to clean up unused screen-pop definitions.

These patterns are common in support diagnostics when agents report missing or incorrectly ordered contact fields during call handling.

Related Objects

The documented foreign keys and primary key relationships identify the following as the most significant related objects:

• AST_CGI_SWITCHES — joined via AST_SWITCH_DATA.CGI_SWITCH_ID = AST_CGI_SWITCHES.CGI_SWITCH_ID. This is the primary parent, defining the switch whose display metadata is being configured.
• FND_SECURITY_GROUPS — joined via AST_SWITCH_DATA.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID. Enforces multi-org security scoping.
• AST_SWITCH_DATA_PK — the primary key constraint on SWITCH_DATA_ID, which any child or referencing object must respect.

Because the metadata classifies the table as standalone, no child tables were documented as referencing it directly; dependent behavior is driven through the switch parent rather than through this table as a hub. Application logic in the TeleSales agent UI consumes these rows at call-delivery time to construct the screen-pop layout.