Results for “internal_order_flag”

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

Overview

CSD_REPAIR_TYPES_VL is the translated (VL) view for Depot Repair repair types in Oracle E-Business Suite 12.1.1 and 12.2.2. Repair types define the categories of repair work that a depot repair organization can perform, such as advance exchange, return for repair, or repair-and-return-to-customer models. The view joins the bilingual base table (CSD_REPAIR_TYPES_B) with the translation table (CSD_REPAIR_TYPES_TL), exposing the user-entered name and description in the session language returned by USERENV('LANG'). It also denormalizes several descriptive lookups for convenience, including the workflow item type display name, the start flow status code and meaning, and the workflow display name. In reporting and integration contexts, the view is the standard reference source for repair-type attributes, most notably the transaction billing type identifiers that drive invoicing and cost recovery for repairs.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented objects:

• CSD_REPAIR_TYPES_B — the base table holding repair-type definitions, seeded and user-defined, including billing type IDs, flags, and descriptive attributes.
• CSD_REPAIR_TYPES_TL — the translation table holding NAME and DESCRIPTION per language.
• CSD_FLOW_STATUSES_B — outer-joined to derive the start flow status.
• FND_LOOKUPS — outer-joined on lookup type CSD_REPAIR_FLOW_STATUS to yield the flow status code and meaning.
• WF_ITEM_TYPES_VL — outer-joined on WORKFLOW_ITEM_TYPE to supply the display name.
• FND_GLOBAL — supplies the language environment for the translation join.

The joins are all outer joins except those against the B and TL tables, which are paired on REPAIR_TYPE_ID and filtered by LANGUAGE. Because the TL table is language-filtered, a row is returned only if a translation exists for the current session language; the base-language row typically satisfies this.

Key Columns

• REPAIR_TYPE_ID — primary key of the repair type.
• NAME / DESCRIPTION — translated values from the TL table.
• WORKFLOW_ITEM_TYPE / WORKFLOW_ITEM_TYPE_NAME — the workflow driving the repair process.
• START_FLOW_STATUS_CODE / START_FLOW_STATUS_MEANING — the initial flow status assigned to a repaired unit.
• CPR_TXN_BILLING_TYPE_ID — the transaction billing type used for customer-paid repair (CPR) transactions. This is the column most frequently sought by users searching for this identifier; it links to the service billing type definition that determines how a repair transaction is priced and invoiced.
• CPS_TXN_BILLING_TYPE_ID, LS_TXN_BILLING_TYPE_ID, LR_TXN_BILLING_TYPE_ID, MTL_TXN_BILLING_TYPE_ID, LBR_TXN_BILLING_TYPE_ID, EXP_TXN_BILLING_TYPE_ID — parallel billing type identifiers for the parts, labor, material, labor-rate, and expense components of a repair.
• THIRD_RMA_TXN_BILLING_TYPE_ID / THIRD_SHIP_TXN_BILLING_TYPE_ID — billing types for third-party RMA and shipment transactions, active when THIRD_PARTY_FLAG is set.
• AUTO_PROCESS_RMA, INTERFACE_TO_OM_FLAG, BOOK/RELEASE/SHIP_SALES_ORDER_FLAG, INTERNAL_ORDER_FLAG — integration flags controlling order interface and fulfillment behavior.
• SEEDED_FLAG — distinguishes Oracle-seeded repair types from customer-defined ones.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the repair type.
• ATTRIBUTE1–15 and ATTRIBUTE_CATEGORY — the standard DFF columns.

Common Use Cases and Queries

The most common query resolves the billing type associated with a repair type, for example to audit pricing configuration or to feed a reconciliation report:

• SELECT repair_type_id, name, cpr_txn_billing_type_id, cps_txn_billing_type_id FROM csd_repair_types_vl WHERE cpr_txn_billing_type_id IS NOT NULL;
• SELECT name, start_flow_status_code, workflow_item_type_name FROM csd_repair_types_vl WHERE seeded_flag = 'Y';
• SELECT name, third_party_flag, third_rma_txn_billing_type_id FROM csd_repair_types_vl WHERE third_party_flag = 'Y';

These queries are typically used in Depot Repair reporting, in the Order Management interface setup review, and in billing reconciliation when validating that every active repair type carries a valid CPR billing type identifier.