Search Results source_id1

Overview

CSD_REPAIR_JOB_XREF_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the CSD – Depot Repair product family. Its purpose is to expose the linkage between depot repair order lines and their associated Work in Process (WIP) discrete jobs. The underlying transactional table, CSD_REPAIR_JOB_XREF, stores the cross-reference between a repair line (REPAIR_LINE_ID) and a manufacturing job (WIP_ENTITY_ID), together with allocation quantities and source attribution fields. The view enriches this raw cross-reference with descriptive attributes drawn from WIP, inventory organizations, item definitions, lookups, and service codes, producing a denormalized, query-ready result set suitable for reports, concurrent programs, and integrations.

The view is documented as VALID in both EBS 12.1.1 and 12.2.2 environments, and is the standard access point for retrieving repair-job relationships without requiring the consumer to reconstruct the multi-table join logic independently.

Underlying Base Objects

Per the ETRM documentation, the view is defined over the following objects:

• CSD_REPAIR_JOB_XREF (synonym) — the driving table holding REPAIR_LINE_ID, WIP_ENTITY_ID, GROUP_ID, quantities, source fields, and DFF attributes.
• WIP_DISCRETE_JOBS (synonym) — supplies job status, start/completed quantities, routing reference, alternate routing designator, and organization.
• WIP_ENTITIES (synonym) — provides WIP_ENTITY_NAME.
• HR_ORGANIZATION_UNITS (view) — provides the organization NAME.
• MFG_LOOKUPS (view) — resolves WIP_JOB_STATUS lookup codes to meanings.
• FND_LOOKUPS (view) — resolves SOURCE_TYPE_CODE to a user-facing meaning.
• MTL_SYSTEM_ITEMS_KFV (synonym) — provides concatenated item segments for both the routing reference and the repair product.
• CSD_SERVICE_CODES_VL (view) — supplies the service code NAME via RO_SERVICE_CODE_ID.
• FND_GLOBAL, HR_GENERAL, HR_SECURITY (packages) — support MOAC and organizational security enforcement.

Key Columns

• REPAIR_JOB_XREF_ID, REPAIR_LINE_ID, GROUP_ID — primary key and repair-line grouping identifiers.
• WIP_ENTITY_ID, WIP_ENTITY_NAME — the discrete job identity and its name.
• ORGANIZATION_ID, ORGANIZATION_NAME — the manufacturing organization and its descriptive name.
• ALLOCATED_CREATED_QUANTITY, ALLOCATED_COMPLETED_QUANTITY — quantities allocated to the repair line, nulled when the allocation equals the full job start quantity.
• CREATED_QUANTITY, COMPLETED_QUANTITY — the job's START_QUANTITY and QUANTITY_COMPLETED, along with STATUS_TYPE and STATUS_MEANING.
• ROUTING_REFERENCE_ID, ROUTING_REFERENCE, ALTERNATE_ROUTING_DESIGNATOR — routing context for the job.
• INVENTORY_ITEM_ID, PRODUCT — the repaired item and its concatenated segment description.
• SOURCE_TYPE_CODE, SOURCE_TYPE, SOURCE_ID1, SOURCE_NAME — attribution of the job to an originating source; SOURCE_ID1 holds the source identifier of interest, and SOURCE_NAME resolves it through CSD_SERVICE_CODES_VL.
• RO_SERVICE_CODE_ID — the associated service code for the repair order.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield context and segments.
• OBJECT_VERSION_NUMBER — optimistic locking column.

Common Use Cases and Queries

The view supports repair-to-manufacturing traceability, job status dashboards, allocation reconciliation, and source attribution reporting. A typical query retrieving jobs for a given source identifier is:

• SELECT wip_entity_name, organization_name, product, status_meaning, source_type, source_id1, source_name, created_quantity, completed_quantity FROM csd_repair_job_xref_v WHERE source_id1 = :p_source_id;
• SELECT repair_line_id, wip_entity_name, allocated_created_quantity FROM csd_repair_job_xref_v WHERE repair_line_id = :p_repair_line_id;
• SELECT source_type, source_id1, COUNT(*) FROM csd_repair_job_xref_v GROUP BY source_type, source_id1;

Because the view enforces organization security through HR_SECURITY and FND_GLOBAL, results are automatically restricted to the operating unit context of the session. Access is therefore typically granted to APPS and read-only reporting responsibilities.