All tables
tables · table

cjobpohdramnd

The cjobpohdramnd table serves as the historical repository for amendments made to Consumable Job Purchase Order (PO) Headers. It tracks changes to the primary contract terms, vendor assignments, and quotation references for consumable items. Every time a PO is modified, a snapshot of the header is stored here with an incremented amendno.

Row count
54
Last entry
2025-12-30
Source
tables

Columns

25
ColumnTypeNullableMeaning
indexintegerNOInternal primary key.
compcodestringYESUnique identifier for the company.
ponointegerYESPurchase Order number.
amendnointegerYESThe version/amendment number of the PO.
podatedatetimeYESOriginal date the PO was created.
quotnostringYESReference number of the vendor's quotation.
quotdatedatetimeYESDate of the vendor's quotation.
vendcodestringYESPhysical vendor code associated with the PO.
amenddatedatetimeYESDate when this specific amendment was saved.
term_1stringYESPayment terms/delivery conditions line 1.
term_2stringYESTerms and conditions line 2.
term_3stringYESTerms and conditions line 3 (often GST/Tax info).
term_4stringYESTerms and conditions line 4.
term_5stringYESTerms and conditions line 5.
term_6stringYESTerms and conditions line 6.
term_7stringYESTerms and conditions line 7.
authflagintegerYESAuthorization status.
wefdatedatetimeYES"With Effect From" date for this amendment.
reasonstringYESJustification/explanation for the PO amendment.
povaluestringYESTotal financial value of the PO (Header level).
povaluewordstringYESPO value written out in words.
invyearintegerYESFinancial/Inventory year for PO tracking.
vendcodeCstringYESLikely Consignee or Alternative Vendor Code.
PODocstringYESFormatted Document String for the PO.
ValidUpTodatetimeYESExpiry or validity date of the PO terms.

Full documentation

### 1) Overview
 The `cjobpohdramnd` table serves as the historical repository for amendments made to **Consumable Job Purchase Order (PO) Headers**. It tracks changes to the primary contract terms, vendor assignments, and quotation references for consumable items. Every time a PO is modified, a snapshot of the header is stored here with an incremented `amendno`.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | NO | Internal primary key. | | PK |
 | **compcode** | string | YES | Unique identifier for the company. | e.g., "DAS" | FK / Join |
 | **pono** | integer | YES | Purchase Order number. | | FK / Join |
 | **amendno** | integer | YES | The version/amendment number of the PO. | 0 = Original, 1+ = Amendments | FK / Join |
 | **podate** | datetime | YES | Original date the PO was created. | | Filter |
 | **quotno** | string | YES | Reference number of the vendor's quotation. | | Information |
 | **quotdate** | datetime | YES | Date of the vendor's quotation. | | Information |
 | **vendcode** | string | YES | Physical vendor code associated with the PO. | e.g., "LAKSHMITRD" | FK / Join |
 | **amenddate** | datetime | YES | Date when this specific amendment was saved. | | Filter / Audit |
 | **term_1** | string | YES | Payment terms/delivery conditions line 1. | | Information |
 | **term_2** | string | YES | Terms and conditions line 2. | | Information |
 | **term_3** | string | YES | Terms and conditions line 3 (often GST/Tax info). | e.g., "EXTRA@18%" | Information |
 | **term_4** | string | YES | Terms and conditions line 4. | | Information |
 | **term_5** | string | YES | Terms and conditions line 5. | | Information |
 | **term_6** | string | YES | Terms and conditions line 6. | | Information |
 | **term_7** | string | YES | Terms and conditions line 7. | | Information |
 | **authflag** | integer | YES | Authorization status. | 0 = Pending, 1 = Authorized | Filter |
 | **wefdate** | datetime | YES | "With Effect From" date for this amendment. | | Filter |
 | **reason** | string | YES | Justification/explanation for the PO amendment. | | Audit |
 | **povalue** | string | YES | Total financial value of the PO (Header level). | | Aggregate |
 | **povalueword** | string | YES | PO value written out in words. | | Information |
 | **invyear** | integer | YES | Financial/Inventory year for PO tracking. | e.g., 2023 | Join |
 | **vendcodeC** | string | YES | Likely Consignee or Alternative Vendor Code. | | Join |
 | **PODoc** | string | YES | Formatted Document String for the PO. | e.g., "CJOB/2023-24/0142" | Information |
 | **ValidUpTo** | datetime | YES | Expiry or validity date of the PO terms. | | Filter |
 
 ---
 
 ### 3) Relationships & Join Map
 
 #### Logical Primary Key
 The table is logically unique on `compcode`, `pono`, `invyear`, and `amendno`.
 
 #### Key Joins (Strictly per SCHEMA_MAP)
 1. **cjobpodtlamnd (Amendment Details):**
  * Join `cjobpohdramnd.compcode` to `cjobpodtlamnd.compcode`
  * Join `cjobpohdramnd.pono` to `cjobpodtlamnd.pono`
  * Join `cjobpohdramnd.amendno` to `cjobpodtlamnd.amendno`
  * Join `cjobpohdramnd.invyear` to `cjobpodtlamnd.invyear`
  * *Usage:* Retrieve the specific item lines and rates for a particular PO version.
 
 2. **vendmas (Vendor Master):**
  * Join `cjobpohdramnd.compcode` to `vendmas.compcode`
  * Join `cjobpohdramnd.vendcode` to `vendmas.vendcode`
  * *Usage:* Get full vendor name and address details for the PO header.
 
 3. **cjobpohdr (Current PO):**
  * Join `cjobpohdramnd.compcode` to `cjobpohdr.compcode`
  * Join `cjobpohdramnd.pono` to `cjobpohdr.pono`
  * Join `cjobpohdramnd.invyear` to `cjobpohdr.invyear`
  * *Usage:* Compare historical amendment data against the current active PO.