Results for “cs_business_processes”

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

Overview

CS_BUSINESS_PROCESSES is a Service (CS) module reference table that defines the business processes used in Service Billing within Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a discrete service business process — for example field service, depot repair, or contract-based service — and acts as the classification anchor that determines how service transactions are priced, billed, and routed. Because the table is referenced widely by incident types, repair types, labor schedules, coverage transaction groups, and estimate details, it functions as a central master or lookup entity rather than a transactional table.

The documented primary key is CS_BUSINESS_PROCESSES_PK, defined on BUSINESS_PROCESS_ID, and the physical schema contains 35 columns. Under the heuristic Data Vault classification derived from the foreign key structure, this object is hub-leaning: the surrogate identifier BUSINESS_PROCESS_ID behaves as a durable hub key, while descriptive and flag columns behave as satellite attributes. The presence of a ZD_EDITION_NAME column and edition-aware unique indexes indicates the table participates in the Oracle 12.2.2 editioning model, so queries should account for edition context.

Key Information Stored

The surrogate primary key is BUSINESS_PROCESS_ID (number), which is the value propagated to all dependent tables and to which the ORDER_TYPE_ID and SECURITY_GROUP_ID foreign keys are attached. Two unique indexes document the business-key candidates: CS_BUSINESS_PROCESSES_U1 on (BUSINESS_PROCESS_ID, ZD_EDITION_NAME) and CS_BUSINESS_PROCESS_U2 on (NAME, ZD_EDITION_NAME). NAME is therefore the human-readable business key, subject to edition scoping.

• BUSINESS_PROCESS_ID — surrogate primary key and the join column used by all child tables.
• NAME — business-key candidate; the user-visible process name.
• DESCRIPTION — free-text explanation of the process.
• ORDER_TYPE_ID — foreign key to SO_ORDER_TYPES_115_ALL, tying the process to an order type used in service order entry.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating that controls whether the process is selectable in service billing.
• SERVICE_REQUEST_FLAG, DEPOT_REPAIR_FLAG, FIELD_SERVICE_FLAG, CONTRACTS_FLAG, STAND_ALONE_FLAG — process-type indicators that drive how the process is applied to service requests, depot repairs, field service, contracts, and stand-alone transactions.
• TM_SCHED_COMPLETE_FLAG — indicates whether the process requires labor schedule completion in the Time and Labor context.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting data-level security.
• ZD_EDITION_NAME — edition identifier governing visibility of the row in 12.2.2.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — the standard Oracle flexfield (descriptive) columns for extensibility.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns for concurrency and tracking.

Common Use Cases and Queries

The most common requirement is resolving a BUSINESS_PROCESS_ID back to its NAME for reporting on service incidents, repair orders, or labor schedules. A typical lookup joins the child table to this master on the shared key:

• Reporting: SELECT bp.NAME, bp.DESCRIPTION FROM CS.CS_BUSINESS_PROCESSES bp WHERE bp.BUSINESS_PROCESS_ID = :id;
• Active process list, respecting edition and effective dates: SELECT BUSINESS_PROCESS_ID, NAME, START_DATE_ACTIVE, END_DATE_ACTIVE FROM CS.CS_BUSINESS_PROCESSES WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE+1);
• Cross-module join: SELECT it.NAME incident_type, bp.NAME process FROM CS.CS_INCIDENT_TYPES_B it, CS.CS_BUSINESS_PROCESSES bp WHERE it.BUSINESS_PROCESS_ID = bp.BUSINESS_PROCESS_ID;
• Filtering by process category: constrain on FIELD_SERVICE_FLAG = 'Y' or DEPOT_REPAIR_FLAG = 'Y' to isolate processes eligible for a given service channel.

These patterns support setup validation, migration verification, and operational dashboards that track service volume by business process across the 12.1.1 and 12.2.2 releases.

Related Objects

The table is a referenced parent for numerous Service tables. The most significant relationships documented are the following, each joining on BUSINESS_PROCESS_ID:

• CS_INCIDENT_TYPES_B — links incident types to the process governing their billing.
• CSD_REPAIR_TYPES_B — associates depot and repair types with a business process.
• CS_TM_LABOR_SCHEDULES — ties labor schedules to a process, governed by TM_SCHED_COMPLETE_FLAG.
• CS_BUS_PROCESS_TXNS — the transaction grouping table for the process.
• CS_ESTIMATE_DETAILS — references the process on service estimate lines.
• CSF_DEBRIEF_LINES — field service debrief lines reference the process.
• OKS_COV_TXN_GROUPS_INT_ALL — coverage transaction groups interface references the process.
• WMS_API_HOOKED_ENTITIES — warehouse management integration entities reference the process.

On the parent side, CS_BUSINESS_PROCESSES itself references SO_ORDER_TYPES_115_ALL via ORDER_TYPE_ID and FND_SECURITY_GROUPS via SECURITY_GROUP_ID. Together these relationships position CS_BUSINESS_PROCESSES as a shared master or hub within Oracle Service.