Results for “remaining_quantity”

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

Overview

CSD_IR_REPAIR_JOBS_V is a PL/SQL view owned by the APPS schema within the CSD (Depot Repair) product of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support the Submit Repair Jobs process when the system profile option "Allow create WIP Job w/o RMA" is set. In that configuration, repair jobs may be created independently of a Return Material Authorization, and this view supplies the concatenated, user-facing data set that the Submit Repair Jobs form and its supporting logic consume. Because it joins repair records with service request (incident) data, item information, party data, and several incident lookup views, it behaves as a reporting and integration surface rather than as a table for direct DML. This makes it valuable both to the standard Depot Repair application flow and to any custom reports or interfaces that need a denormalised view of repair jobs linked to incidents.

Underlying Base Objects

The view is defined over the following documented base objects, all under APPS:

• CSD_REPAIRS (synonym) — the primary repair line source, supplying REPAIR_LINE_ID, quantities, status, and attribute columns.
• CS_INCIDENTS_ALL_B (synonym) — the incident/service request header, providing incident number, caller type, customer, severity, urgency, type, and status identifiers.
• CSI_ITEM_INSTANCES (synonym) — the installed base instance, supplying INSTANCE_NUMBER.
• MTL_SYSTEM_ITEMS_VL (view) — item master, providing CONCATENATED_SEGMENTS, DESCRIPTION, and ORGANIZATION_ID.
• CSD_REPAIR_TYPES_VL (view) — repair type name.
• FND_LOOKUPS (view) — used twice (aliases FND1, FND2) to translate approval status and repair status codes to meanings.
• HZ_PARTIES (synonym) and PER_ALL_PEOPLE_F (synonym) — party and employee name/number resolution.
• CS_INCIDENT_SEVERITIES_VL, CS_INCIDENT_URGENCIES_VL, CS_INCIDENT_TYPES_VL, CS_INCIDENT_STATUSES_VL (views) — incident classification names.
• FND_GLOBAL (package) — referenced for session context (for example, org or user identifiers).

This dependency set explains why the object appears alongside the search term cs_incident_urgencies_vl: the urgency name is exposed here via the URG alias and the CS_INCIDENT_URGENCIES_VL join.

Key Columns

• REPAIR_LINE_ID, REPAIR_NUMBER — primary repair line identity and human-readable repair number.
• INCIDENT_ID, INCIDENT_NUMBER, INCIDENT_DATE, INCIDENT_STATUS, INCIDENT_TYPE — incident linkage and classification.
• SEVERITY, URGENCY — decoded names from CS_INCIDENT_SEVERITIES_VL and CS_INCIDENT_URGENCIES_VL.
• CUSTOMER_ID, CALLER_TYPE, PARTY_NAME, PARTY_NUMBER — caller resolution using DECODE over caller type (organization, person, employee).
• INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, DESCRIPTION, ORGANIZATION_ID, UNIT_OF_MEASURE — repaired item details.
• QUANTITY, QUANTITY_RCVD, QUANTITY_IN_WIP, QUANTITY_SHIPPED, RELEASED_QUANTITY, REMAINING_QUANTITY — quantity tracking, where REMAINING_QUANTITY is computed as QUANTITY minus QUANTITY_IN_WIP.
• INSTANCE_NUMBER, SERIAL_NUMBER, CUSTOMER_PRODUCT_ID, INSTANCE_ID — installed base identification.
• APPROVAL_REQUIRED_FLAG, APPROVAL_STATUS, STATUS — workflow and approval state, with FND_LOOKUPS meanings.
• PROMISE_DATE, DATE_CLOSED, PROJECT_ID, TASK_ID, RESOURCE_ID — scheduling and costing context.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield values inherited from CSD_REPAIRS.

Common Use Cases and Queries

Typical scenarios include listing open repair jobs created without an RMA, monitoring WIP consumption versus received quantity, and reporting incident severity and urgency distributions for depot repairs. A sample query follows.

• SELECT repair_number, incident_number, concatenated_segments, remaining_quantity, urgency, severity, promise_date FROM csd_ir_repair_jobs_v WHERE remaining_quantity > 0 ORDER BY promise_date;
• SELECT incident_type, urgency, COUNT(*) FROM csd_ir_repair_jobs_v GROUP BY incident_type, urgency;
• SELECT party_name, party_number, serial_number, status FROM csd_ir_repair_jobs_v WHERE approval_status = 'PENDING';

Because the view reflects the RMA-free WIP job path, its rows are most meaningful when the profile allowing WIP jobs without RMA is enabled. Custom code should treat it as read-only, as its definition already encapsulates all translation and party-resolution logic.