Results for “seeded_flag”

50+ results




Overview
Explore in AI Chat

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

Overview

The CS_BILLING_TYPE_CATEGORIES table resides in the CS (Service) schema and serves as the definitive mapping construct between billing types and billing categories within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its documented purpose is to define how individual billing types are grouped into higher-level billing categories, providing the classification framework that drives service billing, contract invoicing, and revenue recognition processing across the Service module. Because billing categories aggregate billing types, this table is central to how Oracle Service organizes and reports on billable activity.

Under a heuristic Data Vault classification mined from the foreign key structure, this table is categorized as standalone, meaning it does not exhibit the classic hub-and-satellite dependency pattern typical of transactional service entities. In modeling terms, this classification suggests the table behaves as a reference or lookup construct rather than a transactional fact or a dependent link, which is consistent with its role as a static mapping definition.

Key Information Stored

The table contains 13 documented columns. The most significant are outlined below.

The surrogate primary key is BILLING_TYPE, while the documented business-key candidate is the composite unique index (BILLING_TYPE, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical scenarios include resolving the category for a given billing type during invoice generation, validating active mappings within a date window, and reporting billing activity aggregated by category. A representative query returning active mappings follows:

  • SELECT billing_type, billing_category FROM cs_billing_type_categories WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) AND security_group_id = :sgid;
  • Reporting joins to billing and contract lines aggregate amounts by BILLING_CATEGORY.
  • Setup validation queries identify billing types lacking an active category mapping, which can cause downstream billing failures.

Related Objects

The documented relationship data identifies the following significant references and dependencies:

  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID to enforce access control.
  • CS_BILLING_TYPE_CATEGORIES_PK — the primary key constraint on BILLING_TYPE.
  • CS_BILLING_TYPE_CATEGORIES_U1 — the unique business-key index on BILLING_TYPE and ZD_EDITION_NAME.
  • Service billing and contract tables that consume BILLING_TYPE and BILLING_CATEGORY for invoicing and revenue classification.
  • The Billing Type and Billing Category setup entities that reference these lookup values.

Administrators should treat this table as a configuration-driven mapping whose seeded rows should not be altered directly outside supported setup paths.