Results for “ieo_predservices_all”

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

Overview

IEO_PREDSERVICES_ALL is a configuration table in the Oracle E-Business Suite Interaction Center Technology (IEO) product. It stores the setup and operational parameters for Predictive Services — the outbound dialing, predictive call routing, and agent assignment components used in telemarketing, collections, and customer-care contact centers. Each row defines one predictive service registered with the Interaction Center, capturing the name of the service, the service reference type (SREF_TYPE), the hardware image that hosts the predictive dialer, and the timing thresholds that govern dialer behavior and agent RPC communication. The table is significant because it is the central configuration point from which PBX and dialer subsystems derive their runtime behavior; the related IEO_PBX_INFO table carries a composite foreign key into this table on PRED_SRV_NAME and SREF_TYPE.

Because the _ALL suffix is used for multi-org enabled tables, this object is partitioned by operating unit through ORG_ID. The metadata also classifies the object as hub-leaning under a heuristic Data Vault model. This should be read as a modeling suggestion: the row identity defined by the composite unique key (PRED_SRV_NAME, SREF_TYPE) behaves like a business key hub, while the surrounding operational attributes (timeouts, deadlines, flags) are candidate satellite payload.

Key Information Stored

The following columns are the most consequential in the documented 30-column physical schema:

• PREDSERVICE_ID — the surrogate primary key (PREDICTIVE_PK) that uniquely identifies each predictive service configuration row.
• PRED_SRV_NAME — the name of the predictive service; with SREF_TYPE, it forms the unique business key (PSV_UK) on which IEO_PBX_INFO joins.
• SREF_TYPE — the service reference type; together with PRED_SRV_NAME this is the discriminating component of the composite unique key and the join column used by IEO_PBX_INFO.
• ORG_ID — operating unit identifier; confirms multi-org partitioning and conditions all queries.
• HARDWARE_IMAGE — identifies the dialer hardware image associated with the service.
• COUNTRY_CODE and AREA_CODE — telephony numbering context used for dialing.
• RECEIVE_DEADLINE, RESPONSE_DEADLINE — timing thresholds for inbound/outbound response handling.
• AGENT_RPC_TIMEOUT, SERV_RPC_TIMEOUT, VOICE_ASGN_TIMEOUT — timeouts governing agent and service RPC calls and voice assignment.
• RPC_PROTOCOL, REGISTRATION_NAME — transport and registration identity for the service.
• THROTTLE, MIN_CTX_DOWN_TM, RESTART_TIME — dial-rate throttling, minimum context downtime, and restart timing controls.
• IO_LOG_Y_N, EVENT_LOG_Y_N — logging flags for IO and event activity.
• DIALER_CON_SHT, DIALER_TOTAL_ERR — dialer connection shortfall and total error counters.

Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), OBJECT_VERSION_NUMBER, and SECURITY_GROUP_ID are also present. The documented foreign key on SECURITY_GROUP_ID references FND_SECURITY_GROUPS.

Common Use Cases and Queries

Typical uses include auditing which predictive services are active by operating unit, comparing timeout settings across services, and troubleshooting dialer registration or RPC failures. A frequent starting query filters on the composite business key:

• Service lookup by business key: SELECT * FROM ieo_predservices_all WHERE pred_srv_name = :name AND sref_type = :type;
• Multi-org configuration report: SELECT org_id, pred_srv_name, sref_type, rpc_protocol, agent_rpc_timeout FROM ieo_predservices_all WHERE org_id = :org_id ORDER BY pred_srv_name;
• Join to PBX configuration: SELECT p.pred_srv_name, p.sref_type, b.* FROM ieo_predservices_all p JOIN ieo_pbx_info b ON b.pred_srv_name = p.pred_srv_name AND b.sref_type = p.sref_type WHERE p.org_id = :org_id;
• Throttle and timeout analysis: aggregate throttle, serv_rpc_timeout, and voice_asgn_timeout to detect inconsistent service tuning.

Related Objects

The following objects are most significant for joins and impact analysis:

• IEO_PBX_INFO — references this table via the composite foreign key on PRED_SRV_NAME and SREF_TYPE; the primary dependency in the dialer/PBX configuration model.
• FND_SECURITY_GROUPS — parent of the SECURITY_GROUP_ID foreign key, used for row-level access control.
• IEO_PREDSERVICES_TL — the translatable counterpart typically paired with _ALL tables for multi-language service descriptions.
• FND_ORGANIZATION_UNITS — resolves ORG_ID to an operating unit name for reporting.
• IEO Interaction Center concurrent programs and dialer registration APIs that read this configuration at runtime.

Because PREDICTIVE_PK and PSV_UK are the only documented keys, any integration that inserts or updates predictive service configuration must preserve uniqueness of PRED_SRV_NAME plus SREF_TYPE within the tenant to avoid breaking IEO_PBX_INFO referential integrity.