Skip to main content

Master Type

Module Guide: Master Type

Module Location

Settings > Reports > Master Type (or Settings > Menu/General > Master Type)

Module Purpose

The Master Type module is a developer or super-administrator level configuration module that defines and manages the various types of master data used throughout the system. This module controls the options that appear in various dropdowns or fields across the application, as well as their labels and multilingual behavior. It is the "master of all master data."

1. Main View (Master Type List)

The main page displays a complete list of all master types that exist in the system, from various different modules.

View Explanation

  • Search Filter: Allows searching by Type Code or Table Name.

  • List Table:

    • No.: Serial number.

    • Type Code: The internal unique code used by the system to identify a master value (e.g., CRYtype2SOPO).

    • Type Name (English/Indonesian): The label or description of the master value in various languages. This supports multilingual functionality in the interface.

    • Table Name: Indicates which database table or master group this value belongs to (e.g., CylinderRequestTypeYesNoApprovalBothVesReffDocType).

    • Sequence Number: Determines the display order of this value within a dropdown.

  • Action Buttons:

    • Add New: Opens the form to add a new master type entry.

2. Add/Edit Master Type Page

This form is used to create or edit a master type entry.

View Explanation

  • Type Code: Field for the internal unique code.

  • Type Name: Fields to enter the label in various languages (English, Indonesian, etc.). The Apply to All button likely copies text from one language field to the others.

  • Table Name: A dropdown to select the master group or database table this value will be associated with.

  • Number: Field to determine the display order.

  • Enabled: A checkbox to enable or disable this master value, preventing it from appearing in dropdown choices without deleting the data.

  • Buttons:

    • Save: To save the master type data.

    • Reset: Reverts the values to their initial state.

    • Cancel: Cancels the process.

3. Steps to Add a New Master Type

  1. From the main page, click the Add New button.

  2. Select the relevant Table Name from the dropdown.

  3. Fill in the Type Code with a unique code.

  4. Enter the Type Name in the available languages.

  5. Set its sequence Number.

  6. Ensure the Enabled checkbox is checked.

  7. Click the Save button.

4. Workflow & System Impact

  • Populating Dropdowns System-Wide: This module is the primary data source for almost all dropdowns in the application. For example, all options in a "Payment Type" dropdown (like CashBank Transfer) are defined here under the corresponding Table Name.

  • Advanced System Configuration: Allows administrators to add or change the options available to users without needing to alter program code. For example, if the company wants to add a new payment method, they can simply add it through this module.

  • Multilingual Functionality: By providing labels in various languages, the system can dynamically display the correct text according to the language preference of the currently logged-in user.

  • Application Behavior Control: By enabling or disabling entries, administrators can control which options are available to users at any given time.

5. Tips & Important Notes

  • High Risk: This module is extremely fundamental and critical. Configuration errors, such as incorrectly mapping a Table Name or changing an existing Type Code, can cause serious functional errors throughout the entire application.

  • Super Admin Access: Access to this module should be strictly limited to the most senior and well-trained personnel in the architecture of this ERP system.

  • Do Not Change Existing Type Codes: Changing a Type Code that is already in use by transactional data can corrupt the integrity of historical data. If a change is needed, it is better to disable the old one and create a new one.

  • This module is the "engine room" of the application. Changes must be made with a full understanding of their impact on the other modules that depend on it.