Stage Master

Stage Master - User Guide

1. Introduction 📝

The Stage Master defines the lifecycle states through which items and materials pass during their time in the facility. It acts as a universal classification system that tells the ERP whether an item is currently “Raw Material,” “Work-in-Progress (WIP),” or “Finished Product.”

â„šī¸

Strategic Role of Stages:

  1. Material Flow Visibility: Tracks the transformation of goods from purchase to sale.
  2. Stock Partitioning: Allows the system to separate different categories of stock even if they sit in the same physical store.
  3. Operational Clarity: Provides a common language for Production, Quality, and Sales departments to identify the state of a product.

2. Getting Started 🚀

Accessing the Module

The Stage Master is typically found under Supply Chain Setup or Manufacturing Configuration.

Standard Stage Examples

While stages are configurable, they often follow a standardized progression:

  • 01 - Raw Material: Items as they are received from vendors.
  • 02 - WIP: Components currently undergoing production.
  • 08 - Finished Goods: Completed products ready for shipment.
  • QC Stages (IQC/PQC/FQC): Specialized stages used specifically for Quality Control checkpoints.

3. Key Features ✨

đŸˇī¸ Simplified Coding

Stages use short 2-character codes (e.g., ‘01’, ‘08’) for high-speed data entry and compact representation in grid views and reports.

đŸ›Ąī¸ System Consistency

Because stages are deeply embedded in the logic of stock valuation and MRP (Material Requirements Planning), they serve as a “fixed reference” for calculating the current value and readiness of your inventory.


4. Usage Across Modules & Transactions 🔄

The Stage column is a mandatory field in almost all material-related transactions:

🛒 Procurement (Indent & GRN)

  • Indent: Requests specify which stage of material is required.
  • GRN: Items are initially received into a specific stage (usually “Incoming” or “Raw Material”).

🔨 Manufacturing (BOM & Job Work)

  • BOM (Bill of Materials): Defines that “Stage 01” materials are consumed to produce “Stage 02” WIP items.
  • Job Work: Tracks the transition of items between stages as different processes (like machining or assembly) are completed.

✅ Quality Control

  • Test Plans: Specifically linked to stages like IQC (Incoming Quality Control) or FQC (Final Quality Control) to trigger the correct inspection protocols.

5. Related Reports 📊

📈 Stock by Stage

A critical executive report that shows the total quantity of inventory grouped by its current lifecycle state. This helps managers see how much capital is tied up in “Raw Materials” versus “WIP.”

📉 QR & Aging Reports

Used to track how long items have been sitting in a particular stage. For example, it can highlight WIP items that haven’t moved in over 30 days, indicating a bottleneck in production.

📋 Sales Analysis

Allows the sales team to filter results by the stage of the product, providing insights into whether “Seconds” or “Scrap” stages are being sold frequently.


6. Guidelines and Logic âš ī¸

Entry Standards

  • Stage Name: Should be concise and descriptive.
  • Unique Codes: No two stages can share the same code.

7. Deletion & Modification Preventions đŸ›Ąī¸

The Stage Master is protected by high-level data integrity rules:

đŸšĢ Deletion Preventions

You cannot delete a Stage once it has been used in any transaction.

  • If a stage is used in even a single Indent, Invoice, or Stock record, the system will block its deletion.
  • Deleting a core stage like “Finished Goods” would orphan thousands of records, making historical reports inaccurate.

âœī¸ Modification Rules

  • Code Immutability: The 2-character Stage Code is a permanent identifier and cannot be updated after the stage is saved.
  • Name Updates: The name can be refined (e.g., Changing “WIP” to “Work in Progress”), and the change will instantly propagate across all related reports.

8. Best Practices / Tips 💡

  • Align with Production: Ensure your stages match the actual physical flow of your factory floor.
  • Avoid Duplication: Do not create multiple stages for the same logical state (e.g., having both “RAW” and “MATERIAL”).
  • Use for Segregation: Stages are a great way to separate “Service Parts” from “Production Parts” in the same warehouse.