Results for “cs_transaction_types_b”

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

Overview

CS_TRANSACTION_TYPES_B is a Service (CS) module table in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores the seeded and user-defined transaction types that determine the processing rules applied to charges within the Service application. Each row defines a distinct transaction type — for example an installation, a repair, or a return — together with the flags and status mappings that govern what happens to a customer product, whether billing is generated, and whether charges and costs are created when that transaction type is used.

In practice the table functions as a central reference and configuration object for the Service enterprise. Transaction types drive behavior across business processes, billing, and line installation detail records, and the values held here are consumed at runtime by the Service processing engine. ETRM classifies this object as hub-leaning within a heuristic Data Vault model, meaning it is best treated as a hub entity: a stable, uniquely identified business concept (the transaction type) whose descriptive attributes could be separated into an associated satellite. The presence of the multi-tenant column ZD_EDITION_NAME reflects the 12.2.2 editioning mechanism layered on top of the 12.1.1 base schema.

Key Information Stored

The table contains 47 documented columns. The surrogate primary key is TRANSACTION_TYPE_ID, enforced by the CS_TRANSACTION_TYPES_B_PK constraint and also carried in the unique index CS_TRANSACTION_TYPES_B_U1 (TRANSACTION_TYPE_ID, ZD_EDITION_NAME), which combines the surrogate key with the edition name.

• TRANSACTION_TYPE_ID — surrogate primary key uniquely identifying each transaction type.
• SEEDED_FLAG — indicates whether the row is an Oracle-seeded transaction type or a user-defined one.
• REVISION_FLAG — identifies transaction types that represent a revision of an existing configuration.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating that controls when the transaction type is usable.
• INSTALLED_CP_STATUS_ID / INSTALLED_STATUS_CODE — the customer product status applied when a product is installed under this transaction.
• NEW_CP_STATUS_ID / NEW_CP_STATUS_CODE — the resulting customer product status assigned by the transaction.
• INSTALLED_CP_RETURN_REQUIRED / NEW_CP_RETURN_REQUIRED — flags controlling whether a return is required for the installed and new customer products.
• BILLING_FLAG — determines whether the transaction generates billable activity.
• NO_CHARGE_FLAG, CREATE_CHARGE_FLAG, CREATE_COST_FLAG, CALCULATE_PRICE_FLAG — financial processing controls governing charge and cost creation and price calculation.
• TRANSFER_SERVICE, DEPOT_REPAIR_FLAG, TRAVEL_FLAG, MOVE_COUNTERS_FLAG — operational behavior switches for service transfer, depot repair, travel, and counter movement.
• INTERFACE_TO_OE_FLAG, LINE_ORDER_CATEGORY_CODE — control order interface behavior and the line order category.
• ATTRIBUTE1–15, CONTEXT — standard descriptive flexfield columns.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing data security grouping.

Common Use Cases and Queries

Typical usage includes validating the active transaction types available to a Service organization, reporting on charge and billing behavior per type, and tracing which transaction types create costs or transfer service. A common pattern joins the table to its billing and status dependencies.

• Listing active, non-seeded transaction types: SELECT transaction_type_id, billing_flag, no_charge_flag FROM cs_transaction_types_b WHERE seeded_flag = 'N' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1).
• Identifying charge-generating types: filter on CREATE_CHARGE_FLAG = 'Y' or CALCULATE_PRICE_FLAG = 'Y'.
• Resolving customer product statuses: join INSTALLED_CP_STATUS_ID and NEW_CP_STATUS_ID to CS_CUSTOMER_PRODUCT_STATUSES.
• Reporting billing types per transaction: join to CS_TXN_BILLING_TYPES on TRANSACTION_TYPE_ID.
• Auditing configuration changes via CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Related Objects

• CS_BUS_PROCESS_TXNS — references TRANSACTION_TYPE_ID; links transaction types to business processes.
• CS_LINE_INST_DETAILS — references TRANSACTION_TYPE_ID; records transaction types on line installation details.
• CS_TXN_BILLING_TYPES — references TRANSACTION_TYPE_ID; defines billing types associated with each transaction type.
• CS_CUSTOMER_PRODUCT_STATUSES — referenced through INSTALLED_CP_STATUS_ID and NEW_CP_STATUS_ID.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for row-level security.

Together these relationships position CS_TRANSACTION_TYPES_B as the controlling hub for Service transaction processing, billing, and customer product state transitions.