Results for “use_project_rate_flag”

5 results




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

Overview

CS_TXN_BILLING_TYPES is a Service (CS) module configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the mapping between billing types and transaction types, defining which billing types are valid for a given service transaction type. This mapping is fundamental to the Service-to-Order and Service-to-Project billing flows, where the billing type determines how a service transaction is priced, charged, and subsequently invoiced. Because Oracle Service frequently initiates billing for depot repair, field service, and estimate-based transactions, this table acts as a validation and lookup source during transaction entry, debrief, and billing generation.

The ETRM relationship data classifies this object as hub-leaning. From a Data Vault modeling perspective, CS_TXN_BILLING_TYPES behaves like a hub: it is identified by a single surrogate primary key (TXN_BILLING_TYPE_ID) and is referenced by multiple downstream tables that carry the transactional and contextual detail. The surrounding objects such as CS_COST_DETAILS, CSF_DEBRIEF_LINES, and CS_TXN_BILLING_OETXN_ALL function as satellites or link structures that point back into this hub.

Key Information Stored

The table contains 35 documented columns. The surrogate primary key is TXN_BILLING_TYPE_ID, enforced by the CS_TXN_BILLING_TYPES_PK constraint. A unique index, CS_TXN_BILLING_TYPES_U1, covers TXN_BILLING_TYPE_ID together with ZD_EDITION_NAME, reflecting the multi-edition (ZD) architecture used in 12.2.2.

Common Use Cases and Queries

Typical usage includes validating a billing type during service transaction entry, retrieving billing defaults for a transaction type, and reporting which billing types are active for a given transaction type. A common query joins to CS_TRANSACTION_TYPES_B to resolve the transaction type name:

  • List active mappings: SELECT TXN_BILLING_TYPE_ID, BILLING_TYPE, TRANSACTION_TYPE_ID FROM CS_TXN_BILLING_TYPES WHERE START_DATE_ACTIVE <= SYSDATE AND (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE >= SYSDATE);
  • Resolve transaction type descriptions: join CS_TRANSACTION_TYPES_B on TRANSACTION_TYPE_ID.
  • Identify project-interfacing mappings: filter on INTERFACE_TO_PA_FLAG = 'Y'.
  • Reconcile billing detail: join CS_ESTIMATE_DETAILS, CS_COST_DETAILS, or CSF_DEBRIEF_LINES on TXN_BILLING_TYPE_ID.

Related Objects

  • CS_TRANSACTION_TYPES_B — parent table; join on TRANSACTION_TYPE_ID.
  • FND_SECURITY_GROUPS — security group reference via SECURITY_GROUP_ID.
  • CS_ESTIMATE_DETAILS — references TXN_BILLING_TYPE_ID for estimate billing.
  • CS_COST_DETAILS — references TXN_BILLING_TYPE_ID for cost billing.
  • CSD_REPAIR_TYPES_B and CSD_REPAIR_TYPES_SAR — depot repair type references.
  • CS_TXN_BILLING_OETXN_ALL — order transaction billing detail.
  • CSF_DEBRIEF_LINES — field service debrief references.