The first three tiles account for all — purchase orders — that is the delivery position of the book. The last two cut the same book a different way, by the date the vendor agreed to.
Statuses are positions in the ERP, not judgements. Not dispatched means no row in
podispreg carries this order's number. Part dispatched and
Fully dispatched compare DESC_QTY against
ORD_QTY on each item line. Overdue means the delivery date has passed
and the order is not complete; No delivery date means the ERP holds none that can be read.
The dispatch join. A dispatch register number contains its purchase order number as a prefix —
183/0011/0002/0005/0010/1063/1 is the first dispatch against order
…/1063. All 355 dispatch rows link this way. Going through
pordledg.DESP_REGNO instead links only 103, and would understate delivery badly.
Delivery dates. porderdet.TARGET_DELIDT is populated on only 20 of 114 orders. A further
81 dates were read out of the free-text commitment fields in purcord — the last date in strings
such as WITHIN 30.06.2025 or FROM 17.06.2026 TO 17.12.2026. Both the
parsed date and the original wording are shown on every order. 12 orders carry a commitment that has no date in it at
all, such as WITHIN 7 DAYS AFTER RECEIPT OF PAYMENT, and cannot be aged.
Delivery to site cannot be evidenced here. mreceipt.PONO is empty on all 8,279 material
receipt rows, so no receipt can be tied to a purchase order. This report can show that goods left the vendor. It
cannot show that they arrived.
A known disagreement. porderdet totals ₹227.01 cr across 114 orders;
pordledg totals ₹225.82 cr on its item rows and carries one order numbered
NULL. The ₹1.19 cr difference is not reconciled. This report counts
porderdet.
Read-only. Rebuilt from each weekly export — nothing is entered here and nothing is stored.