All tables
tables · table

mrci2dtl

The mrci2dtl table serves as a transactional detail record for Material Receipt Challenge/Internal (MRCI) processes within the production and supply chain module. It specifically tracks operation-level data for items received from vendors or internal processes, including accepted/rejected quantities, operation rates, and associations with specific Job Cards (jobno) and MRP numbers (mrpno). It is frequently used in financial monitoring, GST reporting (ITC-04), and vendor billing reconciliations.

Row count
315,556
Last entry
2026-01-16
Source
tables

Columns

20
ColumnTypeNullableMeaning
indexintegerNoPrimary key for the record.
compcodestringNoUnique identifier for the company/entity.
mrpnointegerNoMaterial Receipt Plan/Note Number.
mrpdatedatetimeYesThe date the material receipt was recorded.
oprcodestringYesCode representing the specific manufacturing operation.
oprnamestringYesDescriptive name of the operation.
itemcodestringYesUnique identifier for the part or raw material.
acptqtynumberYesThe quantity of items passing inspection.
rejqtynumberYesThe quantity of items failing inspection.
oprratenumberYesThe financial rate applied for the specific operation.
jobnointegerYesReference number linking to the master Job Card.
lotnostringYesBatch or lot identifier for traceability.
wooprqtynumberYesWork Order Operation Quantity; often used as a status flag.
rej_flagstringYesIndicator if the record involves a rejection.
sublotnostringYesSecondary lot identifier for finer traceability.
ponostringYesPurchase Order number associated with the receipt.
podatestringYesDate of the associated Purchase Order.
amendnostringYesAmendment sequence number if the record was modified.
amenddatestringYesDate of the specific amendment.
vendcodestringYesUnique identifier for the vendor providing the operation.

Full documentation

### 1) Overview
 The `mrci2dtl` table serves as a transactional detail record for Material Receipt Challenge/Internal (MRCI) processes within the production and supply chain module. It specifically tracks operation-level data for items received from vendors or internal processes, including accepted/rejected quantities, operation rates, and associations with specific Job Cards (`jobno`) and MRP numbers (`mrpno`). It is frequently used in financial monitoring, GST reporting (ITC-04), and vendor billing reconciliations.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary key for the record. | | PK |
 | **compcode** | string | No | Unique identifier for the company/entity. | e.g., "DAS", "SF1" | Join; Filter |
 | **mrpno** | integer | No | Material Receipt Plan/Note Number. | | Join; Filter |
 | **mrpdate** | datetime | Yes | The date the material receipt was recorded. | | Range Filter |
 | **oprcode** | string | Yes | Code representing the specific manufacturing operation. | e.g., "TPO", "PY" | Join; Filter |
 | **oprname** | string | Yes | Descriptive name of the operation. | e.g., "YELLOW PLATING" | Reporting |
 | **itemcode** | string | Yes | Unique identifier for the part or raw material. | e.g., "CP-153" | Join; Filter |
 | **acptqty** | number | Yes | The quantity of items passing inspection. | | Aggregation |
 | **rejqty** | number | Yes | The quantity of items failing inspection. | | Aggregation |
 | **oprrate** | number | Yes | The financial rate applied for the specific operation. | | Calculation |
 | **jobno** | integer | Yes | Reference number linking to the master Job Card. | | Join |
 | **lotno** | string | Yes | Batch or lot identifier for traceability. | | Filter |
 | **wooprqty** | number | Yes | Work Order Operation Quantity; often used as a status flag. | 0 = Standard, >0 = WO | Filter |
 | **rej_flag** | string | Yes | Indicator if the record involves a rejection. | "N", "Y" | Filter |
 | **sublotno** | string | Yes | Secondary lot identifier for finer traceability. | | Filter |
 | **pono** | string | Yes | Purchase Order number associated with the receipt. | | Join |
 | **podate** | string | Yes | Date of the associated Purchase Order. | | Reporting |
 | **amendno** | string | Yes | Amendment sequence number if the record was modified. | | Filter |
 | **amenddate** | string | Yes | Date of the specific amendment. | | Reporting |
 | **vendcode** | string | Yes | Unique identifier for the vendor providing the operation. | e.g., "AI", "BI" | Join |
 
 ### 3) Relationships & Join Map
 
 #### Real Physical Joins (Based on SCHEMA_MAP)
 
 * **MRP/Receipt Tracking:**
  * `mrci2dtl` joins to `dbo.mrci_rep` via `(mrpno, compcode)`.
  * `mrci2dtl` joins to `dbo.mrcirhdr` via `(mrpno, compcode)`.
  * `mrci2dtl` joins to `dbo.mrcirdtl` via `(mrpno, compcode)`.
 
 * **Production & Jobs:**
  * `mrci2dtl` joins to `dbo.job` via `(jobno [mrci2dtl] = jobno [job])`.
  * `mrci2dtl` joins to `dbo.jobhdr` via `(jobno [mrci2dtl] = jobcardno [jobhdr])`.
  * `mrci2dtl` joins to `dbo.job2dtl` via `(jobno, oprcode, compcode)`.
 
 * **Entity Masters:**
  * `mrci2dtl` joins to `dbo.itemmas` via `(itemcode, compcode)`.
  * `mrci2dtl` joins to `dbo.vendmas` via `(vendcode, compcode)`.
  * `mrci2dtl` joins to `dbo.oprmas` via `(oprcode, compcode)`.
 
 * **Financial & Procurement:**
  * `mrci2dtl` joins to `dbo.itemvendopr` via `(itemcode, vendcode, oprcode, compcode)` to retrieve operation rates for billing.
  * `mrci2dtl` joins to `dbo.jobpodtl` via `(itemcode, oprcode, compcode)` when auditing rates against Purchase Orders.
 
 #### Likely Inference
 * **Inventory History:** Likely joins to `dbo.itemledger` on `itemcode` and `compcode` for stock movement auditing.