Setting
1). Production Setting Screen
-
Here it will show different store level configurable settings which are used in production flow.
URL : https://dev.giggleserp.com/public/productionsetting

Stock Deduction Type (Required Field):.
-
-
“Stock Deduction Type” with options Group-Based and Manual.
This field typically appears in ERP/Inventory or POS (Point of Sale) systems, and its function is to determine how stock (inventory quantities) should be reduced when items are sold, issued, or consumed.
Explanation of Stock Deduction Type
When an item is sold, dispatched, or consumed in production, the ERP needs to know how to deduct that stock from inventory. The Stock Deduction Type defines the rule for this process:
-
Manual
-
The user decides which batch, lot, or location stock should be deducted from.
-
Example: If a company has 50 units in Warehouse A and 30 units in Warehouse B, the system won’t auto-choose. The user must select where the stock will come from.
-
Useful when stock control is strict (e.g., pharmaceuticals, high-value items, compliance industries).
-
-
Group-Based
-
The system automatically deducts stock according to predefined rules (such as FIFO – First In First Out, LIFO – Last In First Out, or location priority).
-
Example: In retail sales, if you sell 5 units, the system will automatically reduce it from the batch/warehouse defined by the group rule without user intervention.
-
Useful in fast-moving environments (e.g., supermarkets, wholesale) where speed matters.
-
Where It Is Used
-
Sales Order Processing / POS: To deduct stock when invoices or sales are made.
-
Production / Manufacturing: To consume raw materials during production.
-
Inventory Adjustments / Transfers: To control from which warehouse, location, or batch the stock is deducted.
How Users Work With It
-
If “Manual” is selected → Every time stock is deducted, the user will pick the specific warehouse, lot, or batch.
-
If “Group-Based” is selected → The ERP automatically deducts based on system-defined logic (faster, less control).
👉 In short:
-
-
-
Stock Deduction Type controls how inventory quantities are reduced. Manual = user-controlled, Group-Based = system-controlled (based on rules).
-
-
-
-
Allow Prod Without Planning (Required Field):
-
“Allow Prod Without Planning” with options Yes / No.
This is a control setting in ERP production or manufacturing modules. It defines whether production can be started directly without creating/approving a production plan (or work order).
Explanation of "Allow Prod Without Planning"
-
No (default, stricter control)
-
Production cannot start unless there is a planned work order or production schedule in the system.
-
Enforces discipline: raw materials, capacity, and routing must be planned before manufacturing begins.
-
Prevents ad-hoc or unauthorized production.
-
Useful for industries where strict resource planning and compliance are required (automotive, pharma, electronics).
-
-
Yes (flexible, less controlled)
-
Allows users to start production immediately, even without a production plan.
-
Useful for urgent, small, or unplanned jobs (e.g., rework, custom orders, prototypes).
-
Risks: raw material shortages, overuse of resources, or misalignment with MRP (Material Requirements Planning).
-
Where It Is Used
-
Manufacturing Module (ERP) → While creating a Production Order or Job Card.
-
Production Execution Stage → Decides if operators can directly start making items without planned schedules.
-
Shop Floor Control → For quick jobs, urgent requirements, or maintenance-related production.
How Users Work With It
-
If set to No →
-
User must create a Production Plan → Generate a Work Order → Then production can be started.
-
-
If set to Yes →
-
User can directly start production (for example, producing 10 units immediately) without going through planning approval.
-
👉 In short:
“Allow Prod Without Planning” controls whether production can bypass the formal planning process.
-
No = strict, planned production only
-
Yes = flexible, ad-hoc production allowed
-
Consumption is Fixed as per BOM (Required Field):
"Consumption is Fixed as per BOM" means that the quantity of raw materials or components consumed during production is strictly based on the quantities defined in the BOM (Bill of Materials), regardless of the actual amount used on the shop floor.
This is typically a setting in an ERP system that tells the system how to handle material consumption during manufacturing.
What is a BOM (Bill of Materials)?
A Bill of Materials (BOM) is a structured list of all the materials, components, and subassemblies needed to manufacture a finished product. It includes:
-
Material name or code
-
Quantity required
-
Unit of measure
-
Other attributes (like wastage, scrap, etc.)
What Does "Consumption is Fixed" Mean?
If "Consumption is Fixed" is set to Yes, then the system will:
-
Automatically consume materials exactly as per the BOM when you confirm production.
-
Even if more or fewer materials were actually used during production, the system does not adjust the consumption.
If it is set to No, then:
-
The user or system can manually enter the actual quantity of material consumed.
-
Useful in cases where consumption varies depending on production conditions (e.g., size, weight, human error, waste).
Where is it Used?
This setting is used in manufacturing modules of ERP systems
You’ll typically find this setting in:
-
Production Order / Work Order creation
-
Item Master
-
PD Setup
How Does It Work?
If “Consumption is Fixed = Yes”:
-
When a production order is processed (or confirmed), the system:
-
Refers to the BOM.
-
Issues material from inventory automatically based on BOM quantity.
-
Does not ask for actual consumption input.
-
Example:
BOM says you need 10 kg of Material A per unit.
You produce 5 units → system consumes exactly 50 kg, regardless of what was really used.
If “Consumption is Fixed = No”:
-
The system allows you to manually enter the actual consumption.
-
Useful when production involves variable inputs.
Example:
BOM says 10 kg of Material A, but due to wastage, you used 12 kg.
You can enter the actual 12 kg into the system for accurate tracking.
Live Production Entry:
“Live Production Entry” refers to the real-time recording of production data as it happens on the shop floor. When this setting is enabled (set to Yes), the production system expects that all production activities (quantities produced, material consumed, machine time, etc.) will be entered and updated live—as and when the production occurs.
What It Means in Practice
-
If Live Production Entry = Yes:
-
Operators or production users must enter production data immediately when production happens.
-
The system may require details like:
-
Quantity produced
-
Material consumed
-
Time taken
-
Machine used
-
Operator involved
-
-
Often integrated with barcode scanners, MES (Manufacturing Execution Systems), or mobile devices.
-
-
If Live Production Entry = No:
-
Production data can be entered later (batch entry or backdated).
-
Suitable for environments where live updates are not possible or practical.
-
How It Works – Workflow
When Set to "Yes" (Live Entry):
-
Operator starts a job on the machine.
-
They scan the job order (barcode or RFID).
-
As production progresses:
-
Every unit produced is logged in real-time.
-
Material consumed is deducted immediately.
-
Any defects or stoppages are reported live.
-
-
System updates inventory and production reports instantly.
When Set to "No" (Non-live or Batch Entry):
-
Production happens on the floor.
-
At the end of the shift/day, the supervisor logs into the system.
-
Manually enters:
-
Total quantity produced
-
Materials used
-
Time taken
-
-
Inventory is updated only after posting.
Frequency (Hours) in Minute
What is "Frequency (ExampleHours) :in 15):Minute"?
The field "Frequency (Hours) in Minute" defines how often a specific task or activity should occur, and the value is given in minutes.
Despite the label being a bit confusing, it really means:
How frequently (in minutes) something should happen within an hour-based process.
For example, if the value is 15, it means:
The task or process should be performed every 15 minutes.
Where Is It Used?
This type of setting is commonly used in manufacturing systems, MES (Manufacturing Execution Systems), or ERP platforms, particularly in areas involving real-time production tracking, monitoring, or quality checks.
Common Use Cases
| Area | Purpose of Frequency |
|---|---|
| Live Production Entry | Defines how often the operator must enter production data. |
| Machine Monitoring | How frequently machine data (like speed, temperature, output) is logged. |
| Quality Checks | Ensures quality inspections happen at regular intervals. |
| Preventive Maintenance | Triggers checks every few minutes/hours. |
| Shift Reporting | Breaks down production data into time blocks for reporting. |
The system will send alerts at the specified time intervals, notifying the designated machine authority to complete the production report accordingly
Determines how often (in minutes) the system checks or records production frequency — here, every 15 minutes.
Dynamic Field in Operation:
What is
"Dynamic Field in Operation"?
The field "Dynamic Field in Operation" controls whether custom, changeable (dynamic) input fields are enabled within production operations or tasks in a manufacturing or ERP system.
Meaning in Simple Terms
-
If set to "Yes" → Users can see or add dynamic fields (custom inputs) while performing an operation.
-
If set to "No" → Only standard fields are shown during operation; no extra/custom inputs are available.
How Users Work With It
When "Dynamic Field in Operation" = Yes
-
While doing an operation (e.g., entering production data):
-
Yes/No:TheEnablesscreen/formormaydisablesshowdynamic/customadditional fieldsduring the production operation process. (like machine settings, operator notes, etc.). -
These
dynamicfieldswillmay bevisiblerequired or optional.
-
-
Users (e.g., operators or supervisors) must fill these based on the
production report screen, where during add/edit production based on setting these dynamic inputs fields are required to be filled along with other inputs data.context.
Example Workflow:
-
User opens the production entry screen.
-
Operation = “Painting”
-
Dynamic Field = "Paint Color Code" appears.
-
User enters the code, submits the form.
When "Dynamic Field in Operation" = No
-
Only the default system fields are visible.
-
No extra inputs are required or expected.
-
Simpler UI for standard processes.
| Setting | Meaning |
|---|---|
| Yes | Show custom fields during production operations |
| No | Show only standard system fields |
Rejection Ratio Display from last no of production (Example : 5)
What is "Rejection Ratio Display"?
Rejection Ratio Display refers to showing the ratio or percentage of rejected products or units in a manufacturing or production process — compared to the total produced.
Definition in Simple Terms:
Rejection Ratio = (Rejected Quantity / Total Produced Quantity) × 100
It helps monitor product quality by showing how many units were rejected during production in relation to the total number of units produced.
Where Is It Used?
The Rejection Ratio Display is commonly used in:
| Area | Purpose |
|---|---|
| Manufacturing Execution Systems (MES) | To track and display rejection in real time |
How Users Work With It
Use Case: Real-Time Production Monitoring
-
-
Operator enters production data:
-
Total quantity produced
-
Rejected quantity (scrap, defects, etc.)
-
-
System calculates and displays the rejection ratio:
-
DisplaysAsthea percentage -
In reports or dashboards
-
-
Supervisor or quality team reviews:
-
If rejection ratio > threshold (
defectivee.g.items)3%),basedinvestigationonisthe last 5 production batches/entries.
triggered.
-
-
Action is taken:
-
Root cause analysis
-
Maintenance
-
Training, etc.
-
Display Records For Item Purchase History (Example : 10)
What is "Display Records For Item Purchase History"?
Display Records For Item Purchase History refers to a system feature or screen that shows a detailed history of purchases made for a specific item or product.
It provides information like:
-
WhenHowviewingmany times the itempurchasewashistory,purchased -
By whom
-
When
-
Quantity and price
-
Purchase source (vendor, supplier, or customer)
Definition in Simple Terms
"Item Purchase History" means looking at all the systemtimes willa showproduct was bought — by a business or customer — and seeing the lastfull 10details recordsof those transactions.
It helps answer:
🗂️ “When did we buy this item, from whom, and at what cost?”
🧾 “How many units of this item did this customer purchase?
How Users Work With It
Use Case: Inventory Reordering or Vendor Audit
Step 1: User Selects an Item
-
The user (procurement officer, store manager, etc.) selects or enters an item code or name.
How2: ItSystem Works
Displays This page controls how raw materials are deducted, how production is recorded, and whether packing is centralized. Based on these settings:History
-
MaterialsThecansystembeshowsauto-deductedall(group-based)pastorpurchasemanuallyrecordstracked.of that item:-
Dates
-
Production can follow a BOM strictly or allow flexibility.Vendors -
Operators may enter production data live, with optional dynamic fields.Quantities -
AllCostsactivities -
location-specificPO
andoraffectinvoiceinventory control.numbers
are -
Step 3: User Reviews Data
-
Determine:
-
📅 How frequently the item is bought
-
📉 Is cost increasing or decreasing?
-
🚚 Which vendor is more reliable?
-
🔁 When to reorder?
-
Step 4: Take Action
-
Create purchase orders
-
Negotiate with vendors
-
Forecast inventory needs
Where It's Displayed
| Interface | Description |
|---|---|
| Item Master Screen | Shows purchase history per item |
| Vendor Performance Report | Links items to vendors |
| Purchase Order Screens | History helps while creating new POs |
| Stock Replenishment Modules | Past purchases used for reorder suggestions |
| Customer Purchase History Screens | In B2B/B2C systems, shows customer-specific item purchases |







