tables · table
poduty
The poduty table serves as a detailed breakdown of taxes, levies, and duties applied to Purchase Orders (POs). In the SQL Server environment, this table functions as a child table to PO headers, allowing for multiple duty components (such as CGST, SGST, or Freight) to be associated with a single Purchase Order number. It stores the calculated monetary values, percentage rates, and identifies the specific types of duties applied.
Row count
96
Last entry
—
Source
tables
Columns
7| Column | Type | Nullable | Meaning |
|---|---|---|---|
index | integer | NO | Primary key for the record. |
compcode | string | NO | Unique identifier for the company/branch. |
pono | integer | NO | The Purchase Order number associated with the duties. |
duty_code | integer | NO | Reference code for the specific tax or duty type. |
amount | number | YES | The calculated monetary value of the duty for the PO. |
duty_per | number | YES | The percentage rate applied for this duty code. |
sno | integer | YES | Serial number indicating the sequence of duty application. |
Full documentation
### 1) Overview The `poduty` table serves as a detailed breakdown of taxes, levies, and duties applied to Purchase Orders (POs). In the SQL Server environment, this table functions as a child table to PO headers, allowing for multiple duty components (such as CGST, SGST, or Freight) to be associated with a single Purchase Order number. It stores the calculated monetary values, percentage rates, and identifies the specific types of duties applied. ### 2) Column Dictionary | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage | | :--- | :--- | :--- | :--- | :--- | :--- | | **index** | integer | NO | Primary key for the record. | e.g., 0, 1, 2... | PK | | **compcode** | string | NO | Unique identifier for the company/branch. | e.g., "DAS" | FK/Partition Key | | **pono** | integer | NO | The Purchase Order number associated with the duties. | e.g., 103, 27 | FK to `pohdr` | | **duty_code** | integer | NO | Reference code for the specific tax or duty type. | e.g., 1, 2, 53 | FK to `dutymas` | | **amount** | number | YES | The calculated monetary value of the duty for the PO. | e.g., 141.75 | Measure | | **duty_per** | number | YES | The percentage rate applied for this duty code. | e.g., 12.5, 18.0 | Rate | | **sno** | integer | YES | Serial number indicating the sequence of duty application. | e.g., 2, 3, 4 | Order/Sequence | ### 3) Relationships & Join Map #### Parent Tables * **dbo.pohdr**: Joined on `compcode` and `pono` (referenced as `PONO` in the header). This link provides the general order context (date, vendor, etc.). * **dbo.dutymas**: Joined on `compcode` and `duty_code`. This link provides the descriptive name and ledger mapping for the tax code. #### Related Tables (Sibling/Transaction) * **dbo.podtl**: Joined on `compcode` and `pono`. Links duty breakdowns to the specific line items of the Purchase Order. * **dbo.pdiinspectionhdr**: Joined on `compcode` and `pono` (referenced as `PONO`). Likely used to verify tax implications during quality inspection. #### Join Examples * `poduty.pono` -> `pohdr.PONO` (Primary Header Join) * `poduty.duty_code` -> `dutymas.duty_code` (Tax Master Join) * `poduty.compcode` -> `company.compcode` (Likely Scope Join) ---