Search Results act_cat_inclusion_from

Overview

OTFV_ACTIVITY_CATEGORIES is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, carrying the FND Design Data reference OTA.OTFV_ACTIVITY_CATEGORIES. It resides in the Oracle Trade Management / Enterprise Territory and Resource Management (ETRM) product family, where the OTA table prefix denotes the Activity and Event Management data model. The view is registered with a status of VALID in both the 12.1.1 and 12.2.2 releases, and it is exposed as a public synonym (PUBLIC.OTFV_ACTIVITY_CATEGORIES), making it addressable from any schema without an APPS qualifier.

The view answers a single, focused business question: which category is associated with a given activity, and during what effective period. The documented intent states that the view "shows the Category type for an Activity." Because the underlying category assignment is date-driven, the view exposes inclusion-from and inclusion-to dates that describe the validity window of each activity-to-category relationship. It serves reporting, Discoverer/BIS publishing, and integration consumers that need a denormalized, human-readable projection of activity categorization without navigating the normalized OTA base tables directly.

Underlying Base Objects

The view is defined over the following APPS synonyms: OTA_ACTIVITY_DEFINITIONS and OTA_ACTIVITY_DEFINITIONS_TL (the activity header and its translatable name/description rows), OTA_ACTIVITY_VERSIONS and OTA_ACTIVITY_VERSIONS_TL (versioned activity content), OTA_ACT_CAT_INCLUSIONS (the intersection that binds an activity version to a category usage over a date range), OTA_CATEGORY_USAGES and OTA_CATEGORY_USAGES_TL (the category definition and its translated name), OTA_EVENTS and OTA_EVENTS_TL (the parent event, supplying the event title), and OTA_OFFERINGS (the offering context). The HR_BIS package also participates in the dependency chain, consistent with the BIS view's reporting role.

OTFV_ACTIVITY_CATEGORIES is referenced by PUBLIC.OTFV_ACTIVITY_CATEGORIES, and the view itself references the objects above. The column _DF (datatype CHAR(34)) is the standard Oracle BIS "descriptive flexfield" context column carried by generated business intelligence views.

Key Columns

• ACT_CAT_INCLUSION_FROM / ACT_CAT_INCLUSION_TO (DATE) — the effective start and end of the activity-to-category inclusion. ACT_CAT_INCLUSION_FROM is the column most frequently used for as-of-date filtering; a NULL inclusion-to date generally indicates an open-ended assignment.
• CATEGORY_NAME (VARCHAR2 240) — the translated category usage name sourced from OTA_CATEGORY_USAGES_TL.
• CATEGORY_TYPE and PRIMARY_FLAG (VARCHAR2 4000) — the category classification and an indicator of whether the assignment is the primary category for the activity.
• ACTIVITY_NAME, ACTIVITY_TYPE, ACTIVITY_DESCRIPTION — activity identifying and descriptive attributes, with the name and description drawn from the translatable activity tables.
• EVENT_TITLE, TIME_ZONE — the parent event and its time zone context.
• CATEGORY_USAGE_ID, ACTIVITY_ID, ACTIVITY_VERSION_ID, EVENT_ID, RCO_ID, OFFERING_ID — foreign keys enabling joins back to base tables and to offering or revenue/commerce objects.

Common Use Cases and Queries

Typical consumers use this view to list active activity categorizations, to audit the history of category inclusions, and to join activity categories to event or offering reporting. A frequent requirement is to return only inclusions effective on a given date:

SELECT ACTIVITY_ID, ACTIVITY_NAME, CATEGORY_NAME,
       ACT_CAT_INCLUSION_FROM, ACT_CAT_INCLUSION_TO
FROM   APPS.OTFV_ACTIVITY_CATEGORIES
WHERE  TRUNC(SYSDATE) BETWEEN ACT_CAT_INCLUSION_FROM
                          AND NVL(ACT_CAT_INCLUSION_TO, TRUNC(SYSDATE));

To identify the primary category per activity, filter on PRIMARY_FLAG. To report categorizations grouped by event, join on EVENT_ID or select EVENT_TITLE directly from the view. Because the inclusion dates are the driving semantic of this object, date-bounded predicates on ACT_CAT_INCLUSION_FROM and ACT_CAT_INCLUSION_TO should always be considered to avoid returning superseded assignments.