Skip to main content

Master

1). Operation

  • Here it will show all operations list which are used in production flow.

URL : https://dev.giggleserp.com/public/productionoperationmaster


It’s used to define and manage production operations such as Melting, Chemical Testing, Merging, etc.

Purpose:

To create, approve, and manage different production operations used in manufacturing workflows.

Column & Description

Operation Name : Name of the production process (e.g., Melting, MERGER).

Code : Short code or identifier for the operation (e.g., ML, CHEM1).

Description : Additional details about the operation (optional; only present for MERGER).

In Process QC Required : Indicates if Quality Check (QC) is needed during this operation.

Stock Movement : Shows whether the operation involves stock movement (Yes/No).

Date Added : When the operation was created or entered into the system.

Approval Workflow:

For the first operation (Melting):

  • First Approval: Approved

  • Second Approval: Approved

  • Third Approval: Approved
    This shows that this operation passed through a 3-level approval workflow, ensuring it is verified before being used in production.

Example:

  • Operation: MERGER

    • Code: 100

    • Stock Movement: Yes → This means materials are moved (e.g., from one warehouse to another or from WIP to FG).

1.1). Operation Create

  • Here it will show how to create operations which are used in production.

URL : https://dev.giggleserp.com/public/productionoperationmaster/create

                  This image shows the "Create Operation" screen from the Production Operation Master module of Giggles ERP. It's used to define a new production operation within the manufacturing process.

                 This is a form used to create a new operation in the production workflow. Operations can include steps like Cutting, Melting, Merging, Packing, etc.

Key Fields and Their Meaning:

Code* :  A short unique identifier for the operation (e.g., CUT1, MLT1). Operation* The name of the operation (e.g., "Cutting", "Melting").

Operation Type* :  Select whether it's a Regular operation, or something else (based on your ERP's setup).

Stock Movement* :  Choose Yes or No:

➤ Yes – this operation involves stock transfer (e.g., raw material moving from store to production).

➤ No – used for internal tasks like QC checks where stock is not physically moved. Required field.

Location Details Section 

Location : Physical or logical production location (e.g., PIYUSH TEST – the current factory or plant). Required field.

Stock Location : Specific stock area within that location (e.g., Cutting Operation Location – a defined store/warehouse/bin used in this operation).

Create Button : Once all required fields are filled, clicking “Create” will save this operation to the system and make it available for use in:

  • Bill of Materials (BOMs)

  • Job Cards

  • Production Planning

How It Works:

  1. Admin or planner opens this screen.

  2. Fills in operation name, code, type, and sets if it affects stock.

  3. Chooses production and stock location.

  4. Clicks Create.

  5. The operation now appears in the operation list and can be linked to production processes.

2). Machine/Plant Category

  • Here it will show all Machine/Plant list which are used in production flow.

URL : https://dev.giggleserp.com/public/machinecategory

                 This image shows the "Machine/Plant Category" screen under Production → Master → Machine/Plant Category in the Giggles ERP system.

What This Screen Represents:

                 This screen is used to manage categories or types of machines or production plants within the manufacturing unit.

                 It's like creating tags or classifications for machines so that operations, job assignments, and maintenance can be grouped and organized effectively.

This Works in the ERP:

  1. Admins or production planners define categories for machines (e.g., "CNC Machine", "Drilling Unit", "Vendor Machine", etc.).

  2. These categories are later used in:

  • Machine assignment

  • Reporting by category

  • Maintenance logs by machine type

  • Machines/plants (from the Machine/Plant submenu) are then assigned to these categories.

  • The status (Active/Lock) helps manage lifecycle—only active categories can be assigned to operations.

2.1). Machine/Plant Category Create

  • Here it will show how to create Machine/Plant which are used in production.

URL : https://dev.giggleserp.com/public/machinecategory/create

                 This image displays the create screen for a Machine/Plant Category within the Giggles ERP system at the following page:

This page is used to create a new machine or plant category that can later be assigned to specific machines or production setups in your ERP system.

Field Descriptions:

Field Purpose

Code A short, unique identifier for the category (e.g., CHM01, BUFF01).

Name Full name of the category (e.g., “Chrome Plating”, “Buffing Machine”).

Description Optional field to describe the purpose or nature of this category.

Status Toggles between ACTIVE and INACTIVE. Active categories can be used immediately after creation.

How It Works:

  1. Fill in the form:

  • Enter a Code (e.g., BUFF01)

  • Enter a Name (e.g., Buffing Machine)

  • Optionally describe its use in the Description

  • Ensure Status is set to ACTIVE (unless you want it inactive for now)

  • Click “Create” to save the new category.

  • The system will:

  • Save it into the database

  • Make it available in dropdowns or filters wherever machine categories are used in the ERP

  • Assign it a unique ID (like the /759/edit URL you saw earlier)

Let’s say a factory introduces a new type of machinery called “Ultrasonic Cleaning Machine”.

You would:

  • Code: USCLN01

  • Name: Ultrasonic Cleaning

  • Description: Used for precision cleaning of small parts.

  • Status: Active

  • Click “Create”

This category is now available for linking to machines under the "Machine/Plant" master section.






1.5). Bag Category

  • Here it will show all Bag category list which are used in production flow.

URL : https://dev.giggleserp.com/bagscategory



This screen is designed to manage different types of bags used in the production process. It serves as a master data entry point, allowing users to create, view, and manage bag categories. The page displays a list of bag categories along with their associated details.

Filter Section (Top Filters)

Allows users to search and filter records based on:

  • Name

  • Code

  • Description

  • From Date / To Date – Filters by creation date.

  • Multiple Delete Option – Toggle to enable bulk deletion.


Data Table

Displays a list of bag categories with the following columns:

  • Action: Buttons for edit/view

  • #: Row number.

  • Name: Category name (e.g., COTTON BAG).

  • Code: Unique identifier (e.g., CB002).

  • Description: Details about the bag.

  • Status: Shows if the bag is “Active” or not.

  • Remarks: Notes (if any).

  • Date Added: Date the entry was created.

  • Activity Users: Who created or modified the record.

Inline Filter Toolbar (Bottom of Table)

You can filter each column quickly using this toolbar:

  • Text inputs for Name, Code, etc.

  • Dropdown for Status.

  • Date picker for Date Added.

  • Text input for Activity User.

 Create New

  • Green “Create New” Button: Opens a form to add a new bag category.

Use Case

This screen is typically used by production planners or ERP administrators to:

  • Maintain a list of standard bag types.

  • Ensure traceability and consistency in production records.

  • Simplify selection of bags in downstream processes (e.g., inventory, packaging).







1.6). Bag Category Create

  • Here it will show how to create Bag Category which are used in production flow.

URL : https://dev.giggleserp.com/public/bagscategory/create

This is the data entry form used to create a new bag category in the ERP system. It's a simple form interface that allows users (typically with admin rights) to input and save new records into the Bag Category master.


How It Works – Field by Field Explanation

📝 Form Title: BAG CATEGORY

This form is designed to register new bag types used in production or inventory.

🔢 Fields

  1. Code (Required)

  • A unique alphanumeric identifier for the bag category.

  • Example: CB003, PL001.

  • Name (Required)

  • The name of the bag type.

  • Example: Cotton Bag, Plastic Bag.

  • Description (Optional)

  • Additional info about the bag category.

  • Example: Used for packaging lightweight items.

  • Status

  • Default set to ACTIVE (green button).

  • Can be toggled if the implementation allows

  • INACTIVE (red button).

  • That will be not use if status is inactive.

Use Case

This screen is used during:

  • Initial ERP setup to define standard bag types.

  • Adding new packaging options during operational changes.

  • Maintaining reusable master data across modules like Inventory, Production, and QC.

1.7). Bag

  • Here it will show all Bag list which are used in production flow.

URL : https://dev.giggleserp.com/bags

This image shows the "Bag Master List" screen from the Giggles ERP system, specifically under:

Production > Master > Bag

It displays a list of individual bag records created using predefined Bag Categories like Cotton Bag, Plastic Bag, etc.

🧾 What the Screen Describes

This screen is a data table view that displays detailed information about bags being used or tracked in the production environment. Each row in the table represents one specific bag entry, with its specifications and properties.

⚙️ How It Works – Field Descriptions

🔢 Table Columns (from left to right):

  1. Action

  • Icons for editing (blue), activating/deactivating (green/red), and viewing record status.

  • #

  • Serial number of the row.

  • Bag No

  • Unique number assigned to the bag (e.g., 0003, 0002, 0001).

  • Bag Types

  • Type of bag selected from Bag Category (e.g., Cotton Bag, Plastic Bag).

  • Bag Color

  • Hex color code representing the bag's color (e.g., #f50000, #312626).

  • Weighing Capacity

  • Maximum weight (in kg/units) the bag can hold. (e.g., 200, 20, 50)

  • Weight Variation

  • Tolerance in weight (e.g., 150, 100, 95).

  • Usability

  • Indicates whether the bag is reusable or single-use (e.g., Reusable, One Time).

  • Cost

  • Monetary value of the bag (e.g., 200, 20, 150).

  • Description

  • Additional notes or remarks (e.g., GOOD).

📅 Other Elements

  • Status: Shows if the selected bag record is currently active.

  • Remarks: Area for admin notes (not filled in this view).

  • Date Added: Creation date of the record (e.g., 17-04-2025).

  • Activity Users: Indicates who created or last updated the record (e.g., Created By: Aakanksh).

✅ Features/Actions Available

  • Search Box: Quickly find bag records by any field.

  • Pagination: Navigate through multiple entries.

  • Export Options: Buttons for CSV, Excel, Print.

  • Filter Options: Advanced filters using the buttons at the top-right.

  • Create New Button: Top-right green button to add a new bag entry.

📌 Use Case

This screen is primarily used for:

  • Tracking different types of bags used in production.

  • Monitoring cost, capacity, and usability.

  • Maintaining standardization and traceability of packaging items.

  • Quickly editing or deactivating bags that are obsolete or defective.

1.8). Job Work Price List

What the Screen Describes:

The screen you provided is a Job Work Price List, likely from a business management or ERP system, which is used to manage pricing and vendor operations related to outsourced tasks. It shows a list of items (products) and the vendors who are responsible for specific operations on those items. Each vendor has an associated rate for each operation, which is tied to a particular price list. The table organizes this data in a structured way, making it easy to view and compare vendors, item codes, and rates for different operations.

Table Breakdown:

  1. Price List Name: This column shows the name of the price list. In the example, all entries are under the same list "august25," which may indicate a specific pricing cycle or period.

  2. Item Code: This is an identifier for the item being worked on or sold, such as "CIT01," which likely refers to a specific product.

  3. Item Name: This column provides the name of the item (e.g., "CIT01"). It matches the item code but in text form.

  4. Vendor Code: This is a unique identifier assigned to each vendor (e.g., "B-13," "A-11," etc.), which helps track which vendor is responsible for the work related to this price list.

  5. Vendor Name: The actual name of the vendor, such as "BHIMA," "ALLEN," and "Aliaze." These are likely businesses or suppliers providing the services listed.

  6. Operation: This shows the type of work or operation that the vendor is performing for the item. For example, "ALL" could mean all types of operations, "Drilling Operation" could refer to a specific manufacturing process, or "PCB Assembly" refers to assembling printed circuit boards.

  7. Rate: This is the price or cost associated with the operation for the item, listed in the last column. For example, the rate for the "ALL" operation by "BHIMA" is 135, meaning for the work done by this vendor, the cost is 135 units (presumably in a currency).

Purpose of the Table:

This table is used to track the pricing and vendor-specific details for the services or operations being performed on particular items. It's a tool for businesses to manage and compare the costs associated with outsourcing work to different vendors.

How It Works:

  • Price Lists are maintained by businesses for specific items or services.

  • Vendors are assigned specific codes and names, and their rate for different operations is recorded.

  • When an item needs a specific operation, such as assembly or drilling, the business looks at this table to determine which vendor offers the best rate or is assigned to the task.

Back to top