Results for “active_y_n”

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

Overview

APPS.IEB_SVC_CAT_TEMPLATES is a reporting and integration view owned by the APPS schema within the Interaction Blending (IEB) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata describes it simply as "a view of service category templates." Functionally, the view exposes the master definition of service category templates — the reusable, hierarchical structures that describe the organization of service categories applied within an interaction blending implementation.

In EBS, Interaction Blending governs how customer interactions are routed, filtered, and prioritized across channels. Service category templates provide the structural blueprint against which individual service plans are configured. Because the underlying storage is split between a transactional base table and a translation table, the view exists to present a single, language-aware, denormalized result set that developers and reporting tools can query directly without writing joins against the base tables. The presence of a SVCPLN_SVCPLN_ID column makes the view particularly relevant to users searching on svcpln_svcpln_id, since it links each template row to its associated service plan.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms from the APPS schema:

• IEB_SVC_CAT_TEMPS_B — the transactional base table holding the non-translatable attributes of each service category template, keyed by WBSC_ID.
• IEB_SVC_CAT_TEMPS_TL — the translation table holding language-specific descriptive text, joined on WBSC_ID and filtered to the session language.

The view join condition is SCTEMPB.WBSC_ID = SCTEMPTL.WBSC_ID, combined with the predicate SCTEMPTL.LANGUAGE = USERENV('LANG'). This language predicate means the view returns only the rows matching the current session language, so results are automatically localized without additional filtering by the caller. Because the view is a simple two-table join, it does not itself own any data and carries no DML capability.

Key Columns

• WBSC_ID — the primary identifier for the service category template, originating from the base table.
• SVCPLN_SVCPLN_ID — the identifier of the associated service plan, linking the template to its owning plan. This is the column most often searched under the term svcpln_svcpln_id.
• MEDIA_TYPE — the interaction channel or media type to which the template applies.
• DEPTH — the level of the template node within the hierarchy, supporting parent/child traversal.
• PARENT_ID — the reference to the parent template row, enabling reconstruction of the category tree.
• ORIGINAL_NAME — the untranslated internal name of the template.
• ACTIVE_Y_N — the active/inactive status flag controlling whether the template is currently in use.
• SERVICE_CATEGORY_NAME — the translated display name of the service category.
• DESCRIPTION — the translated descriptive text for the template.

Common Use Cases and Queries

The view is typically used to report the template hierarchy for a given service plan, to validate template configuration during implementation, and to drive downstream integrations that need translated category names. A representative query retrieves all templates for a specific service plan:

• SELECT wbsc_id, svcpln_svcpln_id, media_type, depth, parent_id, service_category_name, active_y_n FROM apps.ieb_svc_cat_templates WHERE svcpln_svcpln_id = :p_svcpln_id AND active_y_n = 'Y' ORDER BY depth, service_category_name;

To reconstruct the hierarchy for display or integration payloads, developers join the view back to itself using PARENT_ID and WBSC_ID. Because the language filter is embedded in the view definition, no explicit language predicate is required, though callers running in multi-language environments should confirm that USERENV('LANG') resolves as expected for their session.