Delivery Note PDF/PLAN remains the shipment canon. N-SRM invoice is a witness source used for existence, quantity, and amount checks.
Status
Invoice No
Week
RD Date
DN Qty
Invoice Qty
Qty Diff
DN Amount
Invoice Amount
Amount Diff
Invoice Status
Delivery Source
Invoice Source
Week
Customer
Code
Description
Specification
Trolley
DO Date
DO Time
GR Date
Qty
Unit Price
Amt
DO No
Invoice No
Source
Invoice No
Code
RD Date
RD Time
GR Date
Buyer Plant
Currency
Ship
Purchaser
Total Qty
Total Amt
Avg Price
Pkg Qty
Tax Amt
Tax Incl Amt
Week
PDF
Code
Description
Specification
Trolley
Evap/Trolley
Source Invoice
Updated
Week
DO Date
DO Time
Code
Description
Qty
Evap/T
Trolley
Door Date
Door Time
Transit (h)
Real Arrived
Delivery Note Guide
Overview β SEHC (Samsung HCMC) delivery plan. Tracks weekly DO (Delivery Order) schedule
with time-slot granularity per component code.
Source: DELIVERY PLAN Excel files (one per month, named like 1. JAN-2026.xlsx ~ 5. MAY-2026.xlsx), each containing weekly sheets.
Path: /mnt/nas133/00.HANYUNG VINA_2026/PURCHASE AND SALE - UYEN*/SALE/SALE/{YEAR}/[N. ]DELIVERY PLAN/ (p340 only)
Delivery Note PDFs: .../SALE/SALE/{YEAR}/2.PRINT BARCODE & DELIVERY CODE/DELIVERY NOTE/ (sibling)
GR Date & GR Week filter β GR = Samsung goods receipt confirmation.
Source: tb_sehc_invoice_header.gr_date (N-SRM invoice witness), joined on invoice_no.
The Delivery Note tables have no GR column of their own β GR is displayed, never written into the DO canon.
- GR Date column: Headers tab (after RD Time) and Note-line tab (after DO Time). Blank means one of three
different things β not received yet, or the invoice was pulled from the Invoice List by PO & DO screen (which does not supply GR at all),
or the row is a plan row with no PDF. Do not read blank as "not received".
- GR Week filter (top bar, next to Week): ISO week of gr_date
(to_char(gr_date,'"W"IW'), server-side). It is a separate axis from Week (= DO week), so the two combine with AND β
e.g. Week W30 + GR Week W31 lists shipments delivered in W30 but receipted in W31.
Applies to Headers, Note-line and Arrival Grid; Dashboard and Door tabs stay on the DO week.
Items: 13 ASSY component codes (DA96-01209A etc.) Schedule: 70+ time slots per week, DO date + time per truck.
Tabs & Sources:
- Dashboard β KPIs + charts from tb_delivery_note_header (PDF invoices)
- Invoice Verify β N-SRM invoice witness (tb_sehc_invoice_header, tb_sehc_invoice_line) checked against Delivery Note PDF headers/lines
- Plan β Result (past, blue, from v_vina_export_canon) + Plan (future, yellow, from tb_delivery_note)
- Arrival Grid β Code Γ (date+time) pivot from Note-line PDF data (tb_delivery_note where source=pdf)
- Note-line β PDF line items from tb_delivery_note (source: Delivery Note PDFs)
- Headers β PDF invoice headers from tb_delivery_note_header. Source: Delivery Note PDF files (e.g. 000126-HV21E-001.pdf)
- Code Desc β Code β description/specification lookup from tb_code_description (extracted from PDFs)
- Door Time β Departure β arrival mapping from tb_door_time
- Door Grid β Truck/trolley calculation per departure time
Tables:
- tb_delivery_note β 15K+ plan rows from monthly DELIVERY PLAN Excel files (e.g. 1. JAN-2026.xlsx, 5. MAY-2026.xlsx, ...). Path: /mnt/nas133/00.HANYUNG VINA_2026/PURCHASE AND SALE - UYEN*/SALE/SALE/{YEAR}/[N. ]DELIVERY PLAN/ Β· loaded via POST /api/core/delivery-note/scan-plan?year=YYYY
- tb_delivery_note_header β PDF invoice headers. Source: NNNNNN-HV21E-NNN.pdf (e.g. 000126-HV21E-001.pdf). Server-side scan path: /mnt/nas133/00.HANYUNG VINA_2026/PURCHASE AND SALE - UYEN*/SALE/SALE/{YEAR}/PRINT BARCODE & DELIVERY CODE/DELIVERY NOTE/ (2026), β¦/{YEAR}/DELIVERY NOTE/ (2024β2025), β¦/2023/DELIVERY NOTE SCAN/ (2023)
- tb_sehc_invoice_header / tb_sehc_invoice_line β N-SRM invoice source. Source screens: ESCMDL02010 and ESCMDL02020. Used only as validation witness; it does not overwrite Delivery Note data.
- v_vina_export_canon β actual export results (canonical: ECUS customs export declaration, XUAT)
- tb_code_description β code β description, specification, trolley (FK lookup from PDFs)
- tb_door_time β Door Time (departure) β DO Time (arrival) per slot
Door Time Logic
Door Time = departure from HYVINA gate. DO Time = arrival at SEHC.
One Door Time covers a truck-load batch of multiple DO slots.
Decision logic (3 departures/day):
β 10:00 departure β DO 14:00~16:00 (daytime batch, ~4h transit)
β‘ 13:00 departure β DO 16:00~20:00 (afternoon batch, ~3-7h)
β’ 16:00 departure β DO 20:00~next day 14:00 (overnight batch, queued delivery)
Caution: This is an observed pattern from past data, not a guaranteed schedule.
Departure times, batch grouping, and transit duration vary by week.
Always use the actual DELIVERY PLAN Excel as the source of truth.
Truck Calculation (Door Grid)
1. TROLLEY per DO slot = ceil(qty / evap_per_trolley) per code, summed across codes
2. TRUCK per departure = bin-pack DO slots into trucks of max 10 trolleys
- Each DO time slot stays on one truck (no splitting a delivery note across trucks)
- Greedy first-fit: largest DO slots packed first for optimal usage
- Example: departure has DO slots with 6, 5, 3, 2 trolleys β Truck 1: 6+3=9, Truck 2: 5+2=7 β 2 trucks