ReasonMappedWithOperation

### 1) Overview
 The `ReasonMappedWithOperation` table serves as a configuration/bridge entity within the manufacturing execution system. It defines valid mappings between **Rejection Reason Codes** and **Operation Codes**. 
 
 In a production environment, this table is typically used to filter the list of available rejection reasons presented to an operator based on the specific manufacturing stage (Operation) they are performing. For example, a "Final" inspection might have different valid rejection reasons compared to a "Pressing" or "Forging" operation.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary key identifier for the mapping record. | | PK |
 | **CompCode** | string | No | Company code identifier used for multi-tenant isolation. | e.g., "DAS" | FK (Join to `company.compcode`) |
 | **Rejcode** | integer | No | The unique code for a specific rejection reason. | e.g., 144, 209 | FK (Join to `rejectionmas.rejcode`) |
 | **OprCode** | string | No | The code representing the manufacturing operation/process step. | e.g., "FINAL", "CF", "PRESS" | FK (Join to `oprmas.oprcode`) |
 
 ### 3) Relationships & Join Map
 
 Based on the `SCHEMA_MAP`, the following relationships are established:
 
 #### Primary Lookups
 * **Rejection Details:** Join to `dbo.rejectionmas` on `CompCode` and `Rejcode` to retrieve the descriptive reason for the rejection (`rejreason`).
 * **Operation Details:** Join to `dbo.oprmas` or `dbo.MachineOperation` on `CompCode` and `OprCode` to retrieve metadata about the manufacturing step.
 
 #### Transactional Integration (Validation)
 * **Production Rejections:** Join to `dbo.product2` or `dbo.prodfhdr` on `Rejcode` and `OprCode`. This is **Likely** used to validate that the rejection logged during a production shift is authorized for that specific operation.
 * **Online Rejections:** Join to `dbo.onlinerej_dtl` on `Rejcode` and `OprCode`.
 
 #### Strict Join Paths:
 1. **Rejection Master:** `ReasonMappedWithOperation.Rejcode` $\rightarrow$ `rejectionmas.rejcode` (and `CompCode`)
 2. **Operation Master:** `ReasonMappedWithOperation.OprCode` $\rightarrow$ `oprmas.oprcode` (and `CompCode`)
 3. **Machine-specific Operations:** `ReasonMappedWithOperation.OprCode` $\rightarrow$ `MachineOperation.oprcode` (and `CompCode`)
 4. **Production Logging:** `ReasonMappedWithOperation.Rejcode` $\rightarrow$ `product2.rejcode` (Likely for data integrity)