Results for “start_quantity”

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

Overview

CSD_RO_GROUP_JOBS_V is an APPS-owned database view in the Oracle E-Business Suite Depot Repair (CSD) module. It presents the details of the Work in Process (WIP) jobs that are submitted against a repair order group, joining repair-side data to the manufacturing execution data that tracks shop-floor progress. The view is a reporting and integration aid: it exposes discrete job header attributes, status, quantities, and organization context in a single flattened result set, sparing callers from reconstructing the multi-table join between the repair and WIP schemas themselves.

Because Oracle EBS stores repair orders in CSD tables while discrete manufacturing jobs live in WIP and MTL tables, a repair order group and its associated job are only linked through the CSD_REPAIR_JOB_XREF cross-reference table. CSD_RO_GROUP_JOBS_V materializes that linkage and augments it with human-readable lookups and names, making it suitable for concurrent programs, OAF pages, BI Publisher reports, and custom SQL that needs job status in repair group terms. The view is documented as VALID in the ETRM metadata for 12.1.1 and 12.2.2.

Underlying Base Objects

The documented reference list includes the repair-side synonyms CSD_REPAIR_ORDER_GROUPS, CSD_REPAIRS, and CSD_REPAIR_JOB_XREF, along with the WIP and inventory synonyms WIP_ENTITIES, WIP_DISCRETE_JOBS, and MTL_SYSTEM_ITEMS_KFV. Supporting objects are MFG_LOOKUPS (a view used for the WIP_JOB_STATUS lookup), HR_ORGANIZATION_UNITS, plus the HR_GENERAL and HR_SECURITY packages that participate in the organization security model.

The join path is driven from CSD_REPAIR_ORDER_GROUPS to CSD_REPAIRS on REPAIR_GROUP_ID, then to CSD_REPAIR_JOB_XREF on REPAIR_LINE_ID. The cross-reference supplies WIP_ENTITY_ID and ORGANIZATION_ID, which connect to WIP_ENTITIES and then to WIP_DISCRETE_JOBS. The routing reference is resolved through a left outer join to MTL_SYSTEM_ITEMS_KFV on ROUTING_REFERENCE_ID and ORGANIZATION_ID, so jobs without a routing item still appear. Status is decoded from MFG_LOOKUPS where LOOKUP_TYPE equals WIP_JOB_STATUS, and the organization name comes from HR_ORGANIZATION_UNITS.

Key Columns

• REPAIR_GROUP_ID – Identifier of the repair order group the job belongs to; the primary grouping key.
• WIP_ENTITY_NAME – The discrete job number as known to shop-floor users.
• GROUP_ID – Cross-reference group identifier carried on CSD_REPAIR_JOB_XREF.
• ORGANIZATION_ID / ORGANIZATION_NAME – The manufacturing organization that owns the job and its display name.
• QUANTITY / QUANTITY_COMPLETED / START_QUANTITY – Job quantities from the cross-reference and WIP_DISCRETE_JOBS, enabling completion percentage calculations.
• STATUS – Decoded WIP job status (for example Released, Complete, Closed) derived from the WIP_JOB_STATUS lookup.
• ROUTER – Concatenated inventory segment string of the routing reference item.
• ROW_ID – The row identifier from CSD_REPAIR_JOB_XREF, useful for locking or update-through-view scenarios.

Common Use Cases and Queries

A frequent requirement is to list all WIP jobs for a repair group with their current status and progress. For example:

SELECT wip_entity_name, status, quantity, quantity_completed, router, organization_name FROM csd_ro_group_jobs_v WHERE repair_group_id = :p_group_id ORDER BY wip_entity_name;

Reports that must show only open work use the decoded status as a filter, e.g. WHERE status NOT IN ('Closed','Cancelled'). Cross-organization dashboards aggregate by ORGANIZATION_NAME to show jobs in flight per plant. Because the view already resolves the WIP_JOB_STATUS lookup, custom code should not re-join MFG_LOOKUPS for status; doing so risks mismatch with the view's decoded MEANING values. For integration, the view is a convenient source when an external system needs job number, repair group, and quantity data together, though consumers should apply organization security through HR_SECURITY or the standard EBS access controls since the view itself does not enforce them.