| Quotation No | Customer | Item | Value | Status |
|---|
Quotation Creation
| SO Number | Item | Customer | Value | Status | Approval |
|---|
Order Creation (Legacy)
Connected to the live ERP database (y2_sale_order_hd / y2_sale_order_dt).
| Order No | Customer | Order Date | Delivery Date | Priority | Status | Total Value |
|---|
Sales Order Creation
| Reference | Item | Status |
|---|
Production Entry Creation
Roll/Bale Barcode scan karke uski poori history dekhein — Production Order, Operations, Material Batches, QC, Warehouse tak.
Roll/Bale
Packing / QC / Warehouse
Production Order / Sales Order
Operations (Machine / Operator / Shift)
| Op | Machine | Operator | Shift | Status |
|---|
Material Batches Consumed (Supplier trace via Lot)
| Material | Lot/Batch | Qty | Godown | Expiry |
|---|
| Supplier | Item | Value |
|---|
Purchase Quotation Creation
| Item | Supplier | Value | Status |
|---|
Purchase Order Creation (Legacy)
| Customer | Item / Tracking | Feedback |
|---|
Sample Creation
My Approvals — Indent / Sales Order / PPC
Sirf wahi transactions dikhte hain jinke current Level/Division ke liye aapka Role authorize hai, ya jinhe aap bypass kar sakte hain. Jab tak koi transaction type yahan configure nahi hota (Permissions > Approval Chain Setup), uska approval yahan bilkul nahi aayega.
| Type | Doc No | Summary | Requested | Level |
|---|
Pending Quotations
| Quotation | Item / Value |
|---|
Pending Orders
| Order | Item / Value |
|---|
Connected to the live ERP database (y2_prdmst) — changes here are real and shared with other systems.
| Item Code | Description | UOM | Product Category |
|---|
| Vehicle No | Type | Driver | Transporter | Capacity |
|---|
Connected to the live ERP database (y2_QCParameters) — department-wise checklist items used by QC Check.
| Code | Department | Parameter Name | Expected Value | Active |
|---|
Machine-wise weighbridge auto-capture rules for Production Packing — min/max weight range, how long the weight must stay stable, whether it locks after auto-capture, and a fixed Series Prefix for that machine.
| Machine | Min – Max Weight | Stable (sec) | Editable After Capture | Series Prefix | Active |
|---|
App ki apni number series (crm_number_series) — prefix, width, year aur last no. Naye forms (jaise BPO) yahin se number lete hain; real ERP ke PO/GRN numbers apni real series se hi bante hain.
| Division | Series Key | Description | Prefix | Width | Year | Last No | Next Number | Active |
|---|
Blanket Purchase Order — vendor ke saath bulk contract (rate + total qty + validity). Release PO isi BPO se banta hai aur seedha real PO table me jaata hai.
| BPO No | Date | Vendor | Inv | Validity | Contract Qty | Released | Status |
|---|
New BPO
Real Purchase Orders (y2_po_ordh) — is division ke. Naya PO BPO ke Release se banta hai; Windows ERP ke PO bhi yahan dikhte hain.
| PO No | Date | Vendor | Inv | Value | BPO | Status |
|---|
Connected to the live ERP database (y2_bom_header / y2_bom_detail) — Bill of Material per product, with revision history.
| BOM No | Product | Type | Revision | Std Qty / Unit | Status |
|---|
BOM Creation
Connected to the live ERP database (y2_ppc_header / y2_ppc_detail) — Sales Order ko Production Qty me convert karne ka planning step, sirf "PPC Required" products ke liye zaroori.
| Plan No | Plan Date | Planner | Plant | From - To | Status |
|---|
Production Plan Creation
Connected to the live ERP database (y2_prodorder_header / material / operation) — Shop Floor Execution document, BOM/Routing yahi se Auto-Load hote hain.
| PO No | Product | Qty | Type | Status | Produced/Rejected | QC |
|---|
Ye Production Order Release ho chuka hai — document ab edit nahi ho sakta. Status upar diye workflow actions (Start/Close/etc.) se hi aage badhega.
Connected to the live ERP database (y2_packing_header / y2_packing_detail) — Roll/Bale/Bag/Box level packing entry with auto-numbering.
| Packing No | Production Order | Product | Type | Packed / Required | Status | MRN No |
|---|
Production Packing
Is packing ka MRN ban chuka hai — stock already credited ho chuka hai, document ab edit nahi ho sakta.
Connected to the live ERP database (y2_QCRESULT_HD / y2_QCRESULT_DT) — document-level QC Check against a Production Packing document, using the checklist defined in QC Parameters.
| QC Check No | Date | Packing No | Department | Result |
|---|
New QC Check
Factory me jitni bhi weighbridges lagi hain (10-12 jagah), har ek ko yahan alag naam se save karein. Jis bhi module me weighing hoti hai (jaise Production Packing), wahan dropdown se choose kar sakte ho konsi weighbridge use karni hai. Har weighbridge us computer/browser se connect karni hogi jahan wo physically judi hai. Sirf Chrome ya Edge browser me kaam karta hai, aur sirf HTTPS link (https://milleerp.tailfb7479.ts.net) se — plain LAN IP link se tabhi kaam karega jab Chrome me security flag set ho.
Saved Weighbridges
| Name | Status | Live Weight |
|---|
Abhi koi weighbridge save nahi hai — "+ Add Weighbridge" se shuru karein.
Nayi Weighbridge
Barcode sticker print karne ke liye is computer me jo bhi printer Windows me already install hai (jaise "TSC TL240"), wahi seedha browser ke Print dialog me dikhega — koi port/baud rate setup nahi karna. Yahan sirf sticker ka size set karna hai, taaki print sahi size me fit ho.
Har production machine ke liye alag sticker design bana sakte hain — Production Packing me print karte waqt jo machine select hogi, uska design automatically use hoga. Machine par koi design saved nahi hai to default layout use hota hai.
Connected to the live ERP database (y2_issuehd / y2_issuedt) — Production Issue (against Production Order) aur General Issue (Department/Machine ke liye), dono isi screen se.
| Issue No | Date | Type | Department | Production Order | Total Qty | Total Value |
|---|
Material Issue Creation
Connected to the live ERP database (y2_iss_requisition_hd / y2_iss_requisition_dt) — Department material requisition, store/warehouse team review karke issue karega.
| Requisition No | Date | Department | Request Name | Lines | Status |
|---|
Connected to the live ERP database (y2_indenthd / y2_indentdt) — Material Purchase Requisition, purchase team ke liye indent raise karne ka form.
| Indent No | Date | Department | Reference | Lines | Status |
|---|
New Material Purchase Requisition
HOD yahan se requisitions review karke approve karta hai — requested qty se kam approve kar sakte hain, zyada nahi. Ye sirf approval hai, stock yahan kam nahi hota — final issue Store/Warehouse Material Issue se karega.
| Requisition No | Date | Department | Lines | Status |
|---|
HOD Approval
Line Review
| Material | UOM | Requested | Available Stock | Lot No | Qty to Issue | Status |
|---|
Ek division se dusri division material bhejne ke liye — Approve karte hi source ka stock kam aur destination ka stock badh jata hai; Gate Out/Gate In sirf vehicle tracking ke liye hai.
| Transfer No | Date | Direction | From | To | Lines | Status |
|---|
Transfer Order Creation
Connected to the live ERP database (y2_gateouthd / y2_gateoutdt) — material gate se bahar jaate waqt entry.
| Gate Out No | Date | Type | Vehicle | Duty Person | Lines |
|---|
Material gate se bahar jaate waqt entry — Trans Type select karke uska pending record chuniye, detail auto-fill ho jayegi.
Ye Trans Type abhi available nahi hai, jald hi add hoga.
| Material | UOM | Qty |
|---|
Items (not linked to Item Master)
| Item Name | Qty | Remarks |
|---|
Connected to the live ERP database (y2_gateentryhd / y2_gateentrydt) — material gate se andar aate waqt entry (stock isi step me add nahi hota, Material Receipt se hota hai).
| Gate Entry No | Date | Type | Supplier / Source | Bill No | Vehicle | Lines |
|---|
Material gate se andar aate waqt entry — stock isi division me add hoga. Trans Type select karke uska pending record chuniye.
Ye Trans Type abhi available nahi hai, jald hi add hoga.
Materials Received
| Material | UOM | Bill Qty | Qty Recvd | Rate |
|---|
Connected to the live ERP database (y2_mrnhd / y2_mrndt) — yahan se stock IN hota hai, bina kisi source document ke Material Receipt nahi ban sakti.
| MRN No | Date | Type | Supplier / Source | Bill No | Lines |
|---|
Yahan se stock IN hota hai (y2_mrnhd + y2_mrndt) — bina kisi source document ke Material Receipt nahi ban sakti.
GRN — Purchase Order receipt
Received = physically utra hua maal. Rejected maal stock me nahi jaata (sirf Accepted = Received − Rejected). Rejection par reason zaroori hai. Short/Excess = Received − Challan. PO qty se over-receipt sirf tolerance tak allowed.
| Material | UOM | PO Qty | Challan | Gate Recvd | Received | Rejected | Accepted | Short/Excess | Reject Reason | Lot No | Godown | Bin |
|---|
Materials Received
| Material | UOM | Qty | Rate | Bill Rate | Tax Code | Godown | Bin |
|---|
Connected to the live ERP database (y2_sub_cost_centre) — read-only reference list, used by Material Issue for cost posting.
| Code | Description |
|---|
Connected to the live ERP database (y2_comp_mst) — logo yahan se upload karein, wahi login screen par us Company ke liye dikhega.
| Logo | Company | Code | Upload |
|---|
Connected to the live ERP database (y2_workcenter).
| Code | Name | Department | Capacity | Supervisor | Status |
|---|
Work Center Creation
Connected to the live ERP database (y2_routing_header / y2_routing_operation) — manufacturing routing per product, with revision history.
| Routing No | Product | Plant | Revision | Approval Stage | Status |
|---|
Routing Creation
| Fabric Type | GSM | Width | Composition |
|---|
Top Customers (by Order Value)
Top Salesperson (by Order Value)
Top Products (by Order Count)
Monthly / Yearly Sales
| Category | Value |
|---|
Connected to the live ERP database (y2_usersX) — changes here control real login access.
| Username | Name | Company | Division | Inventory | Group | Active |
|---|
User Creation
Har Role ke liye define karein konsa menu/screen dikhega, aur us screen me kya kar sakte hain (Entry/Edit/Approve/Delete). Jis Role ke liye yahan kuch bhi define nahi kiya gaya, uska access pehle jaisa hi (full) rahega — sirf jinke liye aap yahan explicitly restrict karein, unhi par ye lagu hoga. Ye roles is app ke apne hain, real ERP ke Group se alag.
| Screen | View | Entry (Add) | Edit | Approve | Delete |
|---|
User-Specific Overrides
Kisi ek specific user ke liye uske Role ke default se alag (zyada ya kam) access set karein — ye Role ki setting se upar priority leta hai, Admin role ho tab bhi. Jis user ke liye yahan kuch define nahi hai, uska access sirf uske Role se hi decide hoga.
| Screen | View | Entry (Add) | Edit | Approve | Delete |
|---|
Approval Chain Setup
Har transaction type ke liye multi-level approval chain define karein — kis Level par kaunsa Role approve karega, aur kis Division ke liye (khaali chhodo = sabhi Division). Jab tak kisi type ke liye yahan kuch bhi define nahi hota, uska approval abhi jaisa hi (bina kisi approval step ke) chalta rahega.
| Level | Role | Division |
|---|
Bypass Roles
In roles ko is transaction type ka koi bhi pending approval seedha (kisi bhi Level se) Approve karne ki chhoot hai.
Save ho gaya ✓