Results for “quantity_submitted”

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

Overview

CSD_GROUP_JOB_PARAM_TEMP is a transient staging and resolving table in the CSD (Depot Repair) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented purpose is to hold parameters used when creating discrete WIP jobs for mass repair orders. In the depot repair flow, a repair line or a set of repair lines is associated with a repair order group; when the group is released to manufacturing, the application must translate each eligible repair line into a WIP job, deriving the item, organization, routing, and quantity attributes required by the Work in Process module. CSD_GROUP_JOB_PARAM_TEMP serves as the working set that the mass-job creation program reads and resolves before the corresponding WIP jobs are instantiated. Because it is a temporary resolving structure, rows are populated during processing and are intended to be consumed or purged rather than retained as a system of record.

From a Data Vault modeling perspective, the mined foreign-key structure suggests classifying this object as a link. It maps associations between a repair group, an inventory item, an incident, and a security group, and it carries no independent descriptive identity of its own beyond the GROUP_JOB_ID surrogate.

Key Information Stored

The table is defined in the CSD schema with 23 documented columns. Its surrogate primary key is GROUP_JOB_ID, enforced by the CSD_GROUP_JOB_PARAM_TEMP_PK1 constraint. The most significant columns are:

• GROUP_JOB_ID — surrogate primary key uniquely identifying each parameter row within the mass job creation run.
• REPAIR_GROUP_ID — foreign key to CSD_REPAIR_ORDER_GROUPS; identifies the repair order group driving the job creation request.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — together form the composite reference to MTL_SYSTEM_ITEMS_B, identifying the item to be built and the inventory organization in which the WIP job is created.
• INCIDENT_ID — foreign key to CS_INCIDENTS_ALL_B, linking the job parameters to the originating service incident.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data separation.
• JOB_TYPE, JOB_STATUS_TYPE, and ACCOUNTING_CLASS — control the type of WIP job produced, its initial status, and its accounting class.
• ROUTING_REFERENCE_ID and ALTERNATE_DESIGNATOR_CODE — specify the routing and alternate bill of material / designator used for the job.
• START_DATE and COMPLETION_DATE — scheduled dates for the resulting WIP job.
• QUANTITY_SUBMITTED and QUANTITY_RECEIVED — quantities to be submitted to and received from the job.
• ITEM_REVISION — the item revision to be manufactured.
• PROCESS_ID — the concurrent or batch process instance that populated the row.
• Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) support concurrency control and traceability.

Common Use Cases and Queries

Typical use is to inspect pending mass repair jobs before or after the creation program runs, or to troubleshoot why a WIP job failed to be created for a given repair line. A representative query joins the staging table to its item and group references:

• SELECT g.GROUP_JOB_ID, g.REPAIR_GROUP_ID, g.INVENTORY_ITEM_ID, g.ORGANIZATION_ID, g.QUANTITY_SUBMITTED FROM CSD.CSD_GROUP_JOB_PARAM_TEMP g WHERE g.PROCESS_ID = :p_process_id;
• Joining to MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID and ORGANIZATION_ID to resolve the item segment and description for reporting.
• Joining to CSD_REPAIR_ORDER_GROUPS on REPAIR_GROUP_ID to reconcile the number of parameter rows against the released repair lines.
• Auditing rows by SECURITY_GROUP_ID when troubleshooting cross-operating-unit visibility.

Because it is a temporary resolving table, queries should be scoped by PROCESS_ID or run window to isolate a specific batch, and results should not be treated as historical.

Related Objects

• CSD_REPAIR_ORDER_GROUPS — referenced via REPAIR_GROUP_ID; the repair order group whose lines are being converted to jobs.
• MTL_SYSTEM_ITEMS_B — referenced via INVENTORY_ITEM_ID and ORGANIZATION_ID; the item and organization master for the job.
• CS_INCIDENTS_ALL_B — referenced via INCIDENT_ID; the service incident that originated the repair.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; the security group governing row-level access.
• WIP_DISCRETE_JOBS — the downstream target where instantiated WIP jobs are recorded once the parameters are resolved.
• WIP_ENTITIES and WIP_OPERATIONS — dependent WIP tables populated as each job is created from these parameters.