T
Sign in

FIELDMAP.md — field inventory extracted from the existing software

All docs GitHub source

FIELDMAP.md — field inventory extracted from the existing software

Caveat (owner, 2026-09-02): the existing system is buggy/haphazard — fields below are indicative, verify before trusting (STATUS.md caveat).

Extracted via OCR from the owner's screenshots (raw OCR text kept at screenshots/ocr/, images at screenshots/). Conventions used by the old system: « = required field, trailing numbers in field names are a quality of OCR, terminology is kept as-is. Everything below feeds BUSINESS.md / ARCHITECTURE.md / BRIDGE.md contract cards.

0. System identity

  • Name: "myTextile Inventory Management System – Unit 4" (per-unit, not multi-plant!), financial-year header "2026-2027", logged-in user shown (UserName: Parag), menus: Master / Transactions / Reports / Utility.
  • Job-work runs as a module of the same system; the Utility page menu exposes the full catalogue: Booking Entries · Sizing Register · Inward Beam · Inward Weft · Production Planning · Beam Card · Total Production Dept. · Inward Dept. · Total Packing Slip · Mending Dept. · Customer Bill · Folding Dept. · Payment Receive By Cheque · Rolling One-To-Many · Rolling Many-To-One · Yarn Return · Beam Return · I-Store · Inward Outward Dept. · Weft Issue · Yarn Stock Transfer · Yarn Hishob Transfer (yarn accounts) · Yarn Physical Stock · Fabric Physical Stock · Cone To Be Issued · Yarn Hishob Difference · Daily Efficiency Register (1st/2nd shift).

1. Masters

Party (Master_Party)

Fields: Party Name · Category (Party / Broker / Sizing / Transport…) · Address (Gate No., Unit No.) · City · Taluka · District · Pin code · State · Mob.No · Phone No. · Email ID · Due Days (credit) · Broker Name · Opening Balance (₹) · PAN No. · GST No (e.g. 27ANXPP9439N1ZM). → Model: party_master with category, credit terms, GST/PAN, opening balance (first accounting hook for Tally integration).

Yarn (Master_yarn)

Fields: Yarn Name (e.g. "10S") · Yarn Count (10) · Yarn Type: Cotton (also seen: OE — open-end, Denier/Polyester, Lycra/LYCRA, 150 DENIER). → Model: yarn_master {count, type} where the count system can be Ne or denier — one numeric + a count_system flag (Ne/denier/tex), because the same unit handles 20S OE cotton and 150-denier polyester.

Quality / Design (Master_Quality, Master_Design)

Quality master: Width (63) · Reed (64/5) · Pick (64) · Warp count (40S) · Weft count (20S) · Reed Space (64) · Quality Name "63° 64/5·64 / 40S·20S" · Weave (SATIN/PLAIN) · Alias. Design master: Design Name (e.g. "48°+48° 55/5·63 / 60S·60S -SATIN") · Quality Name alias · Width · Pick on Loom · UTL (107.5) · Reed Space · "As per checker" (50) · Reed · Warp Shrinkage % · HSN Code (e.g. 89921 — fabric HSN!) · grid of yarn rows with a computed kg/m factor per yarn (e.g. 0.032554 / 0.031314). → Model: ONE construction_master (= their "design") carrying width, reed (EPI basis), picks, warp count/ply, weft count/ply, weave, shrinkage%, HSN, UTL, and the two consumption constants (kg/m warp, kg/m weft) the old system already stores — the empirical base for the conversion engine (BUSINESS.md §3), seeded from this master.

Loom (Master_Loom)

Rows: Loom No · Shift toggle (3rd Shift — runs a 3rd shift?) · capacity-class (250 / 190) · Contract No. column. (The weft-cone grid on the capture belongs to the issue forms, not the loom master.) → Model: loom {no, shifts[], capacityClass, unit}.

Flange (Master_Flange)

Fields: Flange No (e.g. 32-PARIWAR) · Status · Beam Size (250 cm). → Beam width comes from the flange: flange {no, beamSize}, beams reference a flange, beam.width is derived (per the old system's convention).

2. Contracts & orders

Job-work sale contract entry (Form_Job_work_sale_contract_entry)

Header: Contract No · Contract Date · Party · C.No (party's contract ref?) · Type of Loom (190-class) · Broker Name · Brokerage % · Order Status · Remark · Payment Term (Days) · Diff. Mtr. / Diff. Beam. (radio — tolerance basis!). Lines: SrNo · Beam No · QualityName (e.g. "126/2·96 / 60S·60S -PLAIN" construction string) · Meter (per beam, e.g. 24,000) · JobRate (₹/m, e.g. 3) · Rate (₹/m billed, e.g. 8.64). → Model: job_work_contract {contractNo, party, cNo, loomType, broker, brokeragePct, paymentDays, toleranceMode(mtr|beam), status} + lines {beamQty, construction, metersPerBeam, jobRate, rate}. JobRate = ₹/pick; Rate = JobRate × picks (₹/m); market rate, no costing sheet in job-work (owner 2026-09-01). C.No = Party Contract No. Type of Loom = loom class (e.g. Airjet 190/250). Lines grant mtrs or beams (brim-filled beam assumption).

3. Sizing & beams

Beam outward for sizing (Form_beam_outward_for_sizing)

Header: Sizing Date · GP No · Sizing Name (sizer party) · Party Name · Firm Name · Firm Address · Transport · Vehicle No. · Remark. → Model: sizing_job {gpNo, sizingParty, transport, vehicle, date, lines}; GP No = the movement's goods-pass number — the audit spine of every movement.

Beam inward from sizing (Form_Beam_Inward_from_sizing)

Header: G.P.No · S.GP.No (sizer's GP No) · Party Name · Transfer Year · Warp Yarn Count (41) · Cut Mark Meter (110) · Meter · Total Ends (10240) · Contract No. Grid per beam: BeamNo · Meter · kg (38.64 per ~4250 m) · Sizing party · Cuts (sections, e.g. 15) · Quality (63" 64/5·64/40S·2…) · Width (63.5) · Contract · status Pending. Footer: Total Meter 12,720 · Total Cuts 115.64. → Model: beam {no, ends, warpCount, cutMarkMtr, totalMtr, width} — sized beams re-enter with total ends + cut-mark + cuts and computed kgs (ends×Mtr×count-factor); the 38.64 kg rows let us validate the factor.

Beam card (Form_Beam_Card)

Header: Loom No · Beam No · Flange No · Date · Party · Quality · Rolling Length · Beam meter (5945) · Actual meter · Status (Getting Frames in-progress) · Loom set · Frames (6). Rolls: RollNo 452-01…452-11 (beam-scoped piece numbering), selvedge column Kinari. → Model: beams carry a piece/roll register (RollNo = BeamNo + running piece); "frames" = loom sections; Kinari = selvedge tracking.

Beam return to party (Form_Beam_return_to_party)

Header: Party Name · GP No · Date · Firm Name · Set No · Transfer Year · Transport · Vehicle. Grid: BeamNo · Meter (11270) · kg (102.45) · sizer · quality · width. → Return of party-owned beams (job-work outbound leg).

4. Weft

Weft inward from job-work provider (Form_Weft_Inward_from_JHob_work_Provider)

Header: GP No · Transfer Year · Date · PGP.No (provider's GP) · Party Name · Transport · Vehicle No · Contract No. Rows: Yarn Name · R.Count (raw count) · Lot No · Type · Bag/Cone · Ge.Wt · Net Wt · Set No · Cone Per Wt · Cal. e.g. "127333-01, 20S, Cotton NIKIKA OE, 1.875…, 45 cones, 47.25 kg/set, lot 1938". → Model: weft_receipt with per-lot cone/bag detail — lot no (127333-xx) is the physical barcode identity; cone-per-bag and set no are inventory units.

Weft issue types + Weft issued to production dept (screenshot_weft_issue_types, Form_Weft_issued_to_production_dept)

Header: GP No · Date · Type of Issue (dropdown — one value seen: "Weft issue Sold to party") · From/To Party Name · From/To Set No · Loom No · Shift · Payment mode · Reference no · Barcode No. Rows: Yarn Name (RAMAKRISHNA CBDCPT), cones with kgs; footer "Total Cones 16 · Total Net Wt 30.24"; button Print Yarn Sold. → Model: weft_issue {type, from/to set, loom, shift…} — cones to a loom/shift, production-only (PLANNING §201 — the old form's "Sold to party" type removed; sold yarn is a separate form, PLANNING §8).

5. Yarn movements (hishob / accounts)

Yarn return to party (Form_yarn_return_to_party)

Header: Date · GP No · Transfer Year · From Party Name · From Set No · Firm Name · Transport · Vehicle · Barcode No. Rows: barcode → bags × Gross/Net/Cal weight per bag; footer: Total Bag 3 · Total Cone 28 · Total G.Weight 98 · Total Net Weight 98 · Total Cal Weight 98. → Model: yarn_return {party-lot, bags, cones, gross/net/cal} — CAL = calculated weight (tare-adjusted / cone-average — see questions).

Yarn transfer party account → factory account (Form_saved_yarn_transfer_from_party_account_to_factory_account)

Header: Date · GP No · Transfer Year · From Party Name · From Set No · To Party Name (own firm) · To Set No · Firm · Transport · Vehicle · Barcode No. Rows: bag barcodes, Gross/Net/Cal (35.912 / 33.627), set/unit "1784/38 Unit 04". → Model: the ownership flip (party → own) from ARCHITECTURE.md §2; the reverse direction exists too (factory → party = "Weft issue Sold to party").

Yarn transfer from one contract to another (Form_yarn_transfer_from_one_contract_to_another)

Header: Date · GP No · Transfer Year · Party Name · From Set No · Firm · Transport. Rows: 300 DENIER, kg 4142.95, KANDOI (contract/set) 2, 12, 68, 68, 1873; suffix "short yarn transfer". → Model: runtime re-apportionment of yarn across contracts (the "change assignment at runtime" requirement) incl. a shortage (short) transfer type (allowance adjustment).

Yarn physical stock take (Form_yarn_physical_stock_take_difference)

Header: Date · Type: Non-zero Cone / Difference Cone (also zero-cone) · per yarn: count "16/1", type "LYCRA / OE", cones in hand, kgs (45.36 × 24 cones). → Model: cone balance — residual weft on cones (non-zero) vs empty cones (zero-cone) vs variance (difference cone); the floor counts cones.

6. Production & planning

Daily machine production data entry / Daily Efficiency Register (Form_Daily_machine_production_data_entry)

Header: Date · Shift · Session (A/B/C) · Import · Electrical Failure Min. Per loom: Loom No · Beam No · Flange No · Sizing Name · RPM · Total (picks?) · OnLoom · Actual MTR · Eff % · Design · Party Name · CFM? · Status (Getting/Knotting…) · Stop · Warp Br (breaks) · WarpBrTime · Weft Br · WeftBrTime · Start Attempts · Pick/Rate · Set No · Remark. Footers: RPM Average · Reading · Total Pick · Average · Actual MTR · Total Efficiency · AVG Warp/Weft BR · Pick/Rate · Warp/Weft BR Rate/hr/Mech. → Model: per-loom-per-shift register — the IoT screen: every column is a natural machine-sensor event (picks, RPM, warp/weft breakages, stops, efficiency); this is the exact template for the IoT event schema (PLATFORM.md §4).

Beam plan over machines / Production planning (Form_Further_beam_plan_over_machines__production_planning)

Grid per loom: Loom No · Planning (set) · Design · Beam No · Flange · Job Rate · Clear · Total (planned mtrs) · Actual (woven) · Adjust · Remaining · PerDay (mtrs/day) · OnLoom · Beam · Running (days) with projected finish dates ("09 Aug" → "03 Sep", 3.12 days). → Model: the runtime production plan table per loom — planned vs actual vs remaining vs per-day vs projected finish; the planner's board (ROADMAP Phase 2).

7. Checking, rolling, dispatch (finished goods)

Checking & packing dept register — rolls (Form_Checking_and_packing_dept_register_for_rolls)

Header (Rolling One-To-Many): Roll No (433-07) · Beam No · Flange No · Party Name · Design (construction string) · Meter · Rolling Date · TOL / LTOL (107.5 / actal 76.32) · Loom No · Sizing Name · Printer Path. Grid per roll: RollNo (433-009) · Barcode · Meter (431) · Weight kg (67.7) · kg/m (0.157) · tag (98) · grade columns. Footer: Total Meter · Total Weight · AVG Grams. → Model: checking/rolling — production rolls measured (mtrs + kg + grammage), one beam → many rolls; grade + barcode per roll.

Checking & packing dept register — lumps (Form_Checking_and_packing_dept_register_for_lumps)

Same shape for lumps (short/fold pieces): RollNo 436-073…, barcode, meter (100), kg (10.18, 0.102 kg/m), tag, F grade column visible. → Model: lump stock is a separate item class (short pieces, seconds) with its own grade path → bales.

Converting lumps to bales (Form_Converting_lumps_to_bales)

Header: Date · PS No · Party Name (CHARBHUIJA FABRICS — an internal unit!) · Design Name · Transport · Bale Slip. Rows: roll → bale (429-043 → bale), barcode, mtrs, kg, grams, F grade; footer: Total Tags · Total Meter · Total Weight · Total Grams · Cut Piece. → Model: bale = packing unit for lumps/seconds; the "party" here is the owner's own subsidiary unit — another cost centre, confirming ARCHITECTURE.md §1's multi-profit-centre reality.

Dispatch slip (Form_Dispatch_Slip)

Header: Firm Name · PS No · Date · Party Name · To Party Name · Delivery Address · Design · Bill No · Roll No · Barcode · Transport Name · Fold · Status (Non-delivered) · SDate · Job Work (module toggle!) · Remark. Rows: roll 407-005, barcode 6574, …, 53.1 kg, 0.073 kg/m, tag 49, R grade. → Model: dispatch {psNo, party, deliveryAddress, billNo, transport, status, module(jobwork|trading)} — the Job Work toggle is exactly the profit-centre separation the new system computes instead of entering twice.

Rolling One-To-Many / Many-To-One (Form_Different_forms_for_one_to_many_and_many_to_one…)

Design intent from the names: production roll → many FG rolls (splitting) and many production rolls → one FG roll (joining on folding), with mending & folding departments in the menu. → Model: roll split/join operations as typed events with piece-level tracking.

Trading module

Own raw material → fabric flow. Masters are shared with the job-work module (same Party/Yarn/Quality/Design/Loom/Flange masters).

Yarn Booking (= yarn PO) (Trading_module_Form_-_Yarn_Booking)

Fields: Date · Booking No · Delivery Date · Firm Name · Yarn Supplier · Owner · Broker Name · Yarn Count · Mill Name (e.g. SANATHAN) · Bags × WtPerBag × ConePerBag × Cones (168 × 45 × 18 → 3024 cones) · WtPerCone (0.25) · Grwt / Net Wt (7560) · Rate/Kg (Rs) (253) · Basic Amt · Gst Type (IGST) + Per + IGST/SGST/CGST Amt · Total Amt (2,802,114) · Delivery Term · Payment Term · Status · T&C · Remark. → Model: yarn_po {bookingNo, supplier, mill, count, bags/cone math, ratePerKg, gstTaxation, amounts} — full GST breakup → the Tally adapter contract is right here (booking ↔ voucher on receipt).

Yarn Inward (receipt vs booking) (Trading_module_Form_-_Yarn_Inward)

Fields: Inward No · Inward Date · Firm · Party Name · N.PartyName (their own name field?) · Broker Name · Vehicle No; rows per yarn: count · bags · cones · …(supplier brand e.g. SSM GOLD) · qty; footer: Total Bags/Cones/Gr Wt/Net Wt. → Model: yarn_receipt {inwardNo, bookingLink?, supplierBrand, quantities} — receipts close the Booking; partial/full tracked by kgs.

Warp sent to sizing + construction intimation (Trading_module_Form_-_Warp_sent_to_sizing_and_intimation_of_construction_for_sizing)

Fields: Date · Firm · Design (construction!) · Set No (492) · Reed Space · Type Of Sizing; rows per yarn: 60S SANATHAN … kgs (1512). → Model: warp issue-to-sizing with construction intimation (reed space, design) — exactly how the sizer is told the beam setup; feeds the Sizing job (job-work module's outward form is the mirror).

Beams received from sizing + winding yarn received (Trading_module_Form_-_Beams_received_from_sizing_and_widing_yarn_received)

Fields: Firm · Cutmark/lasa (10) · Sizing-Set No (535) · Warping- Set No (535) · Issue Total Bags (42) · Total Cones (756) · Total Net Wt (590) · Design · Sizing Name (CHARBHUIJA SIZERS); yarn rows (60S SANATHAN…); Used kgs (1847.32 — consumed at sizing!); second grid: weaver leg — "MAHESH CHOUDHARI-GROUP | AIRJET | 2 | 13200 | 120 | … | 48" 55/5·66 60S·60S - Satin | 10 | 49.2"; footer Total Beam Meter 13200 · Total Cuts 120. → Model: sizing receipt = beams in (mtrs/cuts) + leftover-yarn/winding return; the weaver leg + AIRJET (loom type) confirms beams go to the weaver with the beam's meter count.

Yarn received from sizing for winding → sent to winder (Trading_module_Form_-_Yarn_received_from_sizing_for_winding_sent_to_winder) and Yarn received from winder (…yarn_received_from_winder)

To-Winding: GP No · Winding Date · Sizing-Set No · Warping-Set No · Winder Name (SHRIDHWALESHWAR…WINDING) · Year · Set No; rows (41S NITIN… kgs). From-winder: Rec No · Date · Firm · Winder Name · Year · Set No · LB sizing set no · Warping Set No; Empty Bags / Empty Cones / Cone Wt / Rec Net Wt / Ring Wt / Empty Cones Per Wt / Total Empty Cones Wt / Diff Net Wt / Diff Gr Wt. → Model: winding leg (outsourced auto-spinner winding) with full empty-cone/bag reconciliation (gross vs net vs ring weight) — the "cal-weight" logic the job-work module also uses; the accounts-only fields (Diff Net/Gr Wt) are exactly the hishob reconciliation.

Yarn sent to weaver (weft out) (Trading_module_Form_-_Yan_sent_to_weaver)

Fields: Yarn Type (Weft) · Outward No · Outward Date · Firm · To Type: Weaver / Other · Weaver Name · Contract No · GP No · Transport Name · Vehicle No · Mobile No; rows: 61S MANCHESTER … bags; "Only For AS print". → Model: weft_outward {contract, weaver, gpNo, transport} — the outsourced-weaver leg of the trading flow.

Yarn returned from weaver / transferred to other contract (Trading_module_Form_-_yarn_returned_from_weaver_or_transferred_to_other_contract)

Fields: Date · GP No · Weaver Inward No · Party Name. → Model: return of unconsumed yarn (or re-routing to another contract) — the runtime re-apportionment again, now across weavers/contracts.

Fabric Inward from weaver (Trading_module_Form_-_Fabric_Inward_from_weaver)

Fields: Inward No · Date · Firm · PartyName (CHARBHUJA UNIT NO.4 — own unit!) · N.PartyName · Slip No (1393) · Contract No; rows: quality (48"+48" 72/2·64/40S·60S-PLAIN) · … · roll … · mtrs (100) · kg (6.5) · kg/m (0.0519) · OFFICE; footer: Total Tags/Roll No (2, 3518) · Total Meter (7815?). → Model: outsourced fabric received against the weaver contract; the "weaver" is the owner's own Unit No.4 — confirming the internal-transfer pattern (ARCHITECTURE.md §2).

Fabric Purchase order / outsourced weaving job-work order (Trading_module_Form_-_Fabric_Purchase_order_and_outsourced_weaving_job_work_order)

ONE form, two faces: Contract No · Contract Date · Party C.No · Type: Jobwork Fabric · Firm · Party Name (CHARBHUJA UNIT NO.4) · Fabric Order No; rows: beams (10) · design (48" 55/5·66/60S·60S-Satin) · meter (60000) · per-day? (600) · job rate (125) · rate (8.25) · BrokerName · Payment Term. → Model: outsourced weaving = fabric purchase order on a unit; the type toggle ("Jobwork Fabric") is the dual-profit-centre flag the new system computes (same physical contract, two views).

Fabric Sale order (SO) (Trading_module_Form_-_Fabric_Sale_order)

Fields: Order No · Date · Party Contract No · Firm · PartyName · Dispatch City · Design · Total Meter (100000) · Total Taga (150 — lumps, ~100 m pieces; delivery form is rolls OR lumps) · Rate (33.36) · CD % (cash discount, tied to payment days/market dhara) · Brokerage Per (2) · Broker Name (DIRECT) · Due Days · Status. Less Meter / Less Taga dropped (owner 2026-09-01). Owner additions: dispatch form (roll/lump) + per-roll/per-lump mtr carried on the order; amendment provision for later reduction/increase in mtrs. → Model: fabric_so {orderNo, party, dispatchCity, design, totalMeter, totalTags, rate, cdPct, brokerage, dueDays, lessMeter, lessTags, status} — the SO carries tolerance/less adjustments (less meter/taga) matching the contract's Diff. Mtr./Beam tolerance.

Fabric Dispatch slip (Trading_module_Form_-_Fabric_Dispatch_slip)

Fields: Packing Slip No · Outward Date · Unit · Party Name · Purchase Party Name · Slip No (1393) · Quality · Order No · Balance Qty · Design + Design Alias · Vehicle No · Tag Nos (7/12 per row) · Transport Name (Mehalaxmi cargo) · LR No (lorry receipt); rows: quality · tag · mtrs (300) · kg (654/653) · kg/m (0.0519) · copy columns (Office/Transport/Customer Copy checkboxes!); "Jobwork Fabric" + "Auto wate" flags; footer: Total Tags (211) · Total Mtr (29518?) · Total Wt (7815). → Model: fabric_dispatch {packingSlipNo, party, order, balanceQty, vehicle, lrNo, tags[]} with role-based print copies and grade/quality per tag — print-first culture confirmed (customer/office/transport copies).

Reports

Owner is uploading the old software's reports (PDFs/screenshots) — each is logged in docs/DASHBOARDS.md's report catalogue (index) + docs/REPORTS.md (full catalogue) as it arrives (exportable report vs live dashboard tile). Field-level reading of each report adds rows to the relevant form deep-dives in docs/PLANNING.md §3.

8. Terminology glossary (first pass)

Term Meaning (as used) Model home
GP No Goods-Pass number — the movement slip/sequence movement header id
PS No Packing Slip number dispatch/packing header id
Set No Tracks beams of one sizing set + yarn/fabric to the end; assigned at sizing-set issue or JW beam inward (NOT at yarn inward) sizing-set/beam link
Tippan Sizing intimation/plan (construction + yarn usage + weaver + beams) tippan doc (system propose → planner confirm)
Krill Winder creel min–max cones per-winder master
Parts Warping beams one finished beam's ends are split into warping detail
Beam No vs Flange No Flange = physical beam id (movements); Beam no = system production id two id fields
Cone measure Yarn mtrs per cone (per-cone wt × count) lot/costing input
Transfer Year FY of the movement (2026-2027) accounting period tag
Hishob Yarn accounts (stock in kgs/values) yarn ledger / value layer
Cone / Bag Weft unit (cone) / warp-cone-bag unit lot units, gross/net/cal weights
Cal Weight / Ge.Wt Calculated weight (tare/avg-based) / gross weight lot weight fields
Barcode No Pre-printed barcode identity per bag/roll/bale physical token id (QR in new system)
Cuts Sizing sections on a beam beam sizing detail
Frames / Loom set Loom harness/sections count loom config
Kinari Selvedge (edge) of the fabric roll/beam edge tracking
LTOL / UTL see open questions roll/length master field
Lumps Delivery form: ~100 m pieces (NOT exclusively seconds; grades still apply) delivery piece class
R, F Grade letters on checking rows checking grade values
Design / Quality Construction string (width·reed·picks·counts·weave) construction_master key/alias
40S / 20S, 150 DENIER Ne counts; denier for polyester yarn count system
KW / CW / CCW / KCW Karded / Combed / Combed-Compact / Karded-Compact (cotton yarn types) yarn_TYPE
Dn Denier marker (polyester) — "150 Dn" yarn count-system flag
"61 CCW Sanathan" count+type+ticket natural identity product selector
Broker / Brokerage % Intermediary on sale contracts contract party role
Diff. Mtr. / Diff. Beam. Tolerance basis on contract (mtr or beam) contract tolerance mode
Booking No Yarn purchase order number (trading module) yarn_po id
Inward No / Outward No Movement document numbers (in/out) movement ids
N.PartyName Second party-name field (own firm?) party role field
Taga Lump — delivery piece, generally 100 m (SO Total Taga 150 = pieces) delivery piece count
Slip No / PS No Packing slip number (weaver's slip) dispatch ref
LR No Lorry receipt (transport doc) dispatch transport ref
Cutmark / lasa Cut-mark length on the beam beam cutMark
Sizing-Set / Warping-Set No The same lot's set no on each side of sizing lot/set ids
LB sizing set no (winding screen) set no on the sizing side lot/set id
Winder Outsourced auto-spinner doing warp winding unit/party role
Used kgs Yarn consumed at sizing (computed on receipt) sizing consumption
Ring Wt Cone ring/tube weight (empty-cone math) lot weight fields
Kharad (winding rows) — party/process? (open q) —
Ticket Local name for the MILL (yarn supplier/mill selection) booking field (suggestion-driven)
Gatepass (GP) Yarn dispatch note — trader→godown, endorsed onward; WhatsApp + physical stamped copy gatepass entity
Inward code System-generated scan code for the transporter at godown gate → prints bag barcodes gatepass/guard scan
Yarn-stock-transfer (JY) Saved weft transferred to weaver's own account (5% allowance − efficiency) weaver account transfer
AIRJET / loom type Loom technology class on weaver contracts loom type
Market Dhara Market customs for CD% vs payment days (by selling city; e.g. Mumbai: 4%/15d, 3%/30d, 2%/60d, full-90d no cd, 4.5%/2d) order payment fields (prefill)
CD % Cash discount % tied to payment days (market dhara) order payment fields
IGST / SGST / CGST GST tax heads on the yarn booking (→ Tally) po taxation
Lasa / L 2 L Warp length allowance pair (costing: warp kg/m factor ≈1.055) construction.costing
Sizing Wajan Vaad Size add-on % on warp weight (10%) construction.costing
ps (paise) Rate unit on some charges (job rate 9 ps) money fields
GLM Grams per linear meter of fabric (costing basis) weight basis
Reed / Pick ends/inch, picks/inch in construction (costing) construction fields
Regular / Second / Super Second Quality classes seen in costing sheet grade/quality classes (grading set!)

9. Dependencies & calculations inferred (to confirm)

  1. Quality name ↔ construction fields are consistent (63° 64/5·64 / 40S·20S = width·reed·picks·warp·weft) → confirms BUSINESS.md §3 recipe structure; Design master already stores precomputed kg/m factors (0.032554 / 0.031314) to seed the conversion engine.
  2. Beam kgs (38.64 kg per 4250 m ≈ 9.09 g/m with 10240 ends) — the count-factor can be reverse-engineered from receipts and reused for planning.
  3. Weft cone arithmetic: bags × net/cone + cone-per-wt → totals; stock take counts non-zero vs zero cones → residual yarn ledgers.
  4. Contracts are beam-quantum: job-work contract grants beams (BeamNo, Meter per beam, JobRate, Rate) — planning counts beams.
  5. Roll numbering is beam-scoped: RollNo 433-07 = beam 433 piece 07; barcode is the physical key everywhere (→ QR in the new system).
  6. Grading letters visible: R and F — full set (A/B/C/R/F?) needed from the checking report screen.
  7. UTL/LTOL repeated across design master (107.5) and rolls register — likely a per-roll length norm; must ask.
  8. GST on yarn booking (IGST 5%, SGST/CGST splits) — the yarn PO is a fully taxed purchase document → the Tally voucher contract is directly visible in this screen.
  9. Internal-unit-as-party: CHARBHUJA UNIT NO.4 appears as party on fabric PO / fabric inward / dispatch ("Jobwork Fabric" type) — the outsourced-weaving leg is a contract on the own unit, validating the internal-transfer computation (ARCHITECTURE.md §2).
  10. Sizing receipt computes "Used kgs" (1847.32) — sizing consumption is derived on receipt; size pickup/loss can be validated against it (BUSINESS.md §3.2).
  11. Winding leg: warp yarn goes through an outsourced auto-spinner winder with full empty-bag/cone reconciliation (ring weight, diff net/ gr wt) — a distinct operation state between yarn and warp beams.
  12. Taga = roll: SO Total Taga 150 for 100000 m → ~666 m/tag; tags are the commercial roll unit and the dispatch line unit.
  13. Per-beam cut accounting: "Total Beam Meter 13200 · Total Cuts 120" on sizing receipts — beams carry meter + cut sections.

10. Open questions for the owner (from this batch)

  1. LTOL/TOL/UTL — what do they stand for and where are they used?

  2. Type of Issue dropdown — ANSWERED (PLANNING §201): production-only; "Sold to party" removed, sold yarn = separate form.

  3. "Short yarn transfer" — exact meaning (shortage adjustment)?

  4. Grade letters — full grading set and their dispatch/pricing meaning?

  5. "Cal Weight" formula — (bag tare? cone-average × count?) so the new system reproduces it exactly.

  6. The "3rd Shift" toggle — is a per-loom shift matrix needed in loom?

  7. Does the old system store kg/m factors per design only, or re-derive them from count/reed? (Seeded either way.)

  8. G.P.No (own) vs S.GP.No / PGP.No (partner's) — confirm pairing logic.

  9. "As per checker 50" on design master — reed space measured by checking department?

  10. N.PartyName — what it means (own firm shown on transactions)?

  11. "lasa" in Cutmark/lasa, and "Kharad" in winding rows — terms?

  12. Loom type list (AIRJET / other) — which values does the old system use (airjet, rapier, dobby…)?

  13. "Used kgs" on the sizing receipt — derived from which inputs, exactly?

  14. GST config per supplier (IGST vs SGST+CGST) and where numbers are taken from for the Tally bridge.

  15. Numbering sequences: are Booking No / Contract No / GP No / PS No shared between the two modules or per-module (matters for tenancy + invoice sequences in the new system)?