All tables
tables · table

Item_ParentToChild

The Item_ParentToChild table serves as a mapping repository for hierarchical relationships between items within a manufacturing or assembly context (likely a Bill of Materials or a process sequence). It defines which "Child" items are associated with a "Parent" item and specifies the specific manufacturing operation (Applicable_OprCode) where this relationship or transformation occurs.

Row count
72
Last entry
—
Source
tables

Columns

5
ColumnTypeNullableMeaning
indexintegerNoPrimary Key / Row identifier.
compcodestringNoCompany code identifying the specific business entity.
ItemCode_ParentstringYesThe code for the assembled or higher-level item.
ItemCode_ChildstringYesThe code for the component or sub-assembly item.
Applicable_OprCodestringYesThe specific operation or production stage where the parent-child linkage is relevant.

Full documentation

### 1. Overview
 The `Item_ParentToChild` table serves as a mapping repository for hierarchical relationships between items within a manufacturing or assembly context (likely a Bill of Materials or a process sequence). It defines which "Child" items are associated with a "Parent" item and specifies the specific manufacturing operation (`Applicable_OprCode`) where this relationship or transformation occurs.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary Key / Row identifier. | | `PRIMARY KEY` |
 | **compcode** | string | No | Company code identifying the specific business entity. | e.g., "DAS" | `JOIN`, `WHERE` |
 | **ItemCode_Parent** | string | Yes | The code for the assembled or higher-level item. | e.g., "HOUSING0474" | `JOIN` (to `itemmas.itemcode`) |
 | **ItemCode_Child** | string | Yes | The code for the component or sub-assembly item. | e.g., "0474076000X" | `JOIN` (to `itemmas.itemcode`) |
 | **Applicable_OprCode** | string | Yes | The specific operation or production stage where the parent-child linkage is relevant. | e.g., "CNC1", "FETTLING" | `JOIN` (to `oprmas.oprcode`) |
 
 ### 3. Relationships & Join Map
 
 #### Real Physical Joins (Strictly based on SCHEMA_MAP)
 
 * **Item Master (Item Metadata):**
  * `Item_ParentToChild.ItemCode_Parent` → `dbo.itemmas.itemcode` (Join to get details of the parent item)
  * `Item_ParentToChild.ItemCode_Child` → `dbo.itemmas.itemcode` (Join to get details of the child component)
 * **Operations & Stations:**
  * `Item_ParentToChild.Applicable_OprCode` → `dbo.oprmas.oprcode` (To identify the operation name/station)
  * `Item_ParentToChild.Applicable_OprCode` → `dbo.MachineOperation.oprcode` (To link to machines capable of this operation)
 * **Process Definitions:**
  * `Item_ParentToChild` (`ItemCode_Parent`, `Applicable_OprCode`) → `dbo.itemopr.itemcode`, `dbo.itemopr.oprcode` (To link the parent item's specific operation parameters)
 * **Production Tracking:**
  * `Item_ParentToChild` (`ItemCode_Child`, `compcode`) → `dbo.RMproduct1.itemcode`, `dbo.RMproduct1.compcode` (To track production history of the child component)
 
 #### Likely Joins (Inferred)
 * `Item_ParentToChild.ItemCode_Parent` → `dbo.saleitemmas.itemcode` (If the parent is a finished good for sale)
 * `Item_ParentToChild.ItemCode_Child` → `dbo.citemmas.citmcode` (If the child is a consumable or store item)