rmjobrec2nddtl

### 1. Overview
 The `rmjobrec2nddtl` table serves as the granular detail level for **Secondary Job Work Receipts (Incoming)**. While the header table (`rmjobrec2nd`) tracks the overall receipt of items from a customer or vendor, this detail table specifically records the manufacturing operations (`oprcode`) performed or intended for that specific Job/MRP number, along with the associated processing rates.
 
 In the production lifecycle, this table is primarily used to:
 * Define the sequence or list of operations (e.g., CNC, VMC, Drilling) applied to a specific MRP batch.
 * Store the financial rates (`rate`) for job work billing.
 * Identify if specific operations are classified as `rework`.
 * Support reporting for job work balances and pending operations via stored procedures like `JobIncRecd_Balance`.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary Key | 0, 1, 2... | Internal Row ID. |
 | **compcode** | string | No | Company Identifier | e.g., "DAS" | Part of composite joins for multi-tenant data isolation. |
 | **mrpno** | integer | No | MRP / Job Number | e.g., 727, 7714 | Links the operation details to a specific Material Requirement/Job batch. |
 | **itemcode** | string | No | Part/Item Code | e.g., "CP-162", "INNERSHAFT" | The specific product receiving the operation. |
 | **oprcode** | string | No | Operation Code | e.g., "CNC", "VMC", "CNC1" | Unique identifier for the manufacturing process step. |
 | **rate** | number | Yes | Processing Rate | e.g., 29.00, 8.21 | The financial value or unit cost for performing this operation. |
 | **woyear** | integer | No | Work Order Year | e.g., 2014, 2019 | Fiscal year associated with the work order. |
 | **rework** | string | Yes | Rework Indicator | " " (Space), "Y" | Identifies if the operation is a corrective rework process. |
 
 ### 3. Relationships & Join Map
 
 Based on the `SCHEMA_MAP` and `REFERENCE_JSON`, the following joins are authoritative:
 
 #### Primary Joins (Header & Master Data)
 * **dbo.rmjobrec2nd** (Header Table): Joined on `compcode`, `mrpno`, `itemcode`, and `woyear`. This provides context on the customer (`custcode`), receipt date, and total quantities.
 * **dbo.oprmas** (Operation Master): Joined on `compcode` and `oprcode`. Used to retrieve the descriptive name of the operation (`oprname`).
 * **dbo.itemmas** (Item Master): Joined on `compcode` and `itemcode`. Used to fetch item descriptions, standard rates, and units of measure.
 
 #### Secondary/Process Joins
 * **dbo.machineitem**: Joined on `compcode`, `itemcode`, and `oprcode`. Likely used to determine the standard production time or specific machine capacity for the item.
 * **dbo.vitemopr** (Vendor Item Operations): Joined on `compcode`, `itemcode`, and `oprcode`. Used to compare vendor-specific operation rates against recorded receipt rates.
 * **dbo.invdespwodetail**: (Inferred) Joined on `compcode`, `mrpno`, `itemcode`, `oprcode`, and `woyear`. Used to track which operations have been dispatched or invoiced against the job work receipt.
 
 #### Functional Logic Join
 * **view_JobworkINC_recd_Opr_sigle_record**: This view utilizes a `UNION ALL` between `rmjobrec1stdtl` and `rmjobrec2nddtl` to provide a unified list of the first operations performed on any given MRP/Item combination.