All tables
tables · table

jobpodtlamnd

The jobpodtlamnd table serves as the Job Purchase Order Amendment Detail ledger. It stores specific line-item revisions for job work (subcontracting) orders. Unlike standard PO tables, this table captures the breakdown of individual manufacturing operations (e.g., grinding, threading, punching) associated with an item within a specific amendment version of a Purchase Order.

Row count
17,855
Last entry
—
Source
tables

Columns

11
ColumnTypeNullableMeaning
indexintegerNOPrimary Key (Internal record identifier)
compcodestringNOCompany identifier
ponointegerNOPurchase Order Number
amendnointegerNOAmendment sequence number (0 = Original)
itemcodestringNOUnique code for the part/product
operationstringYESLong-form description of the manufacturing task
poqtystringYESQuantity allocated for this specific operation
uomstringYESUnit of Measure
ratenumberYESUnit rate/cost for the operation
oprcodestringYESStandardized Operation Code
invyearintegerNOFinancial/Inventory Year of the PO

Full documentation

### 1. Overview
 The `jobpodtlamnd` table serves as the **Job Purchase Order Amendment Detail** ledger. It stores specific line-item revisions for job work (subcontracting) orders. Unlike standard PO tables, this table captures the breakdown of individual manufacturing operations (e.g., grinding, threading, punching) associated with an item within a specific amendment version of a Purchase Order.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | NO | Primary Key (Internal record identifier) | 0, 1, 2... | PK |
 | **compcode** | string | NO | Company identifier | "DAS" | Join Key |
 | **pono** | integer | NO | Purchase Order Number | 42, 12, 22 | Join Key |
 | **amendno** | integer | NO | Amendment sequence number (0 = Original) | 0, 1, 2 | Join Key |
 | **itemcode** | string | NO | Unique code for the part/product | "BS", "CP-133" | Join Key |
 | **operation** | string | YES | Long-form description of the manufacturing task | "THREAD ROLLING" | Display |
 | **poqty** | string | YES | Quantity allocated for this specific operation | "0", "1" | Aggregate |
 | **uom** | string | YES | Unit of Measure | "PCS", "KGS" | Metric |
 | **rate** | number | YES | Unit rate/cost for the operation | 0.2, 35.0 | Financial |
 | **oprcode** | string | YES | Standardized Operation Code | "THREAD", "CNC" | Join Key |
 | **invyear** | integer | NO | Financial/Inventory Year of the PO | 2013, 2016 | Filter |
 
 ### 3. Relationships & Join Map
 
 Based on the `SCHEMA_MAP` and `REFERENCE_JSON` provided, the following physical relationships are established:
 
 #### Primary Header Relationship
 * **jobpohdramnd**: Joins to the amendment header to get amendment dates and vendor details.
  * `jobpodtlamnd.compcode = jobpohdramnd.compcode`
  * `jobpodtlamnd.pono = jobpohdramnd.pono`
  * `jobpodtlamnd.amendno = jobpohdramnd.amendno`
 
 #### Master Data Relationships
 * **itemmas**: To retrieve part names, HSN codes, and drawing details.
  * `jobpodtlamnd.compcode = itemmas.compcode`
  * `jobpodtlamnd.itemcode = itemmas.itemcode`
 * **oprmas**: To validate or expand on operation definitions.
  * `jobpodtlamnd.compcode = oprmas.compcode`
  * `jobpodtlamnd.oprcode = oprmas.oprcode`
 
 #### Likely Transactional Relationships
 * **jobpodtl**: Likely contains the base (non-amended) details of the same POs.
  * `jobpodtlamnd.pono = jobpodtl.pono` (Join on `pono` and `itemcode`).
 
 ---