Results for “svcpln_id”

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

Overview

The IEB_SERVICE_PLANS table is owned by the IEB schema and belongs to the Interaction Blending (IEB) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores summary information describing service plans — the configurable definitions that govern how inbound and outbound interactions are handled and categorized within the Telephony/Interaction Blending subsystem. Each row represents a single service plan header, capturing its name, direction (inbound or outbound), treatment, media type, and descriptive attributes, while the finer-grained coverage rules are held in dependent child tables.

Under a heuristic Data Vault classification derived from its foreign key structure, IEB_SERVICE_PLANS is best modeled as a hub. Most of its foreign keys point outward from the table to reference/lookup objects, and it is itself the target of several foreign keys from dependent detail tables, which is the characteristic profile of a hub surrounded by satellites and links. Modelers building a Data Vault representation should therefore treat SVCPLN_ID as the hub business key anchor.

Key Information Stored

The documented physical schema contains 14 columns. The most significant are:

• SVCPLN_ID — surrogate primary key, constrained by IEB_SERVICE_PLANS_PK. It is the identifier referenced by all dependent coverage and category tables.
• SERVICE_PLAN_NAME — the user-facing name of the service plan; the principal business identifier for reporting and inquiry.
• DIRECTION — indicates whether the plan applies to inbound or outbound interactions, driving which coverage child table is relevant.
• TREATMENT — the handling or treatment classification applied by the plan.
• MEDIA_TYPE_ID — foreign key to IEU_UWQ_MEDIA_TYPES_B, associating the plan with a media/channel type.
• DESCRIPTION — free-text description of the plan.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling row-level access.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the generated Forms/ADF layer to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ZD_EDITION_NAME — editioning column supporting EBR (Edition-Based Redefinition) in 12.2.x.

The unique index IEB_SERVICE_PLANS_PK_U covers (SVCPLN_ID, ZD_EDITION_NAME), confirming that the business key candidate combines the surrogate key with the edition name in the 12.2.2 editioning model.

Common Use Cases and Queries

Typical usage includes administrative inquiry into configured service plans, validation of coverage definitions, and reporting on inbound versus outbound plan distribution. A representative query listing plans by direction:

• SELECT svcpln_id, service_plan_name, direction, treatment, media_type_id FROM ieb.iebservice_plans WHERE direction = 'INBOUND';
• Join to IEU_UWQ_MEDIA_TYPES_B on media_type_id to resolve the media type description for reporting.
• Aggregate counts grouped by DIRECTION and TREATMENT to audit plan coverage.

Because security group enforcement applies, queries run through EBS responsibilities should respect SECURITY_GROUP_ID filtering applied by the application tier.

Related Objects

• IEB_INB_SVC_COVERAGES — child table; joins on SVCPLN_SVCPLN_ID = IEB_SERVICE_PLANS.SVCPLN_ID for inbound coverage rules.
• IEB_OUTB_SVC_COVERAGES — child table; joins on SVCPLN_SVCPLN_ID for outbound coverage rules.
• IEB_SVC_CAT_TEMPS_B — child table referencing the service plan via SVCPLN_SVCPLN_ID for category templates.
• IEB_WB_SVC_CATS — child table referencing the plan via SVCPLN_SVCPLN_ID for service categories.
• IEU_UWQ_MEDIA_TYPES_B — referenced parent; join on MEDIA_TYPE_ID.
• FND_SECURITY_GROUPS — referenced parent; join on SECURITY_GROUP_ID.