Docs
/
Open ERP ↗

Module Builder

Module Detail

Set the business identity and major capabilities of a module before designing its fields.

Jhapu DocumentationUpdated 31 August 2026

Start with the correct context

Select the tenant, module type and company before asking AI to fill the form. This context determines which modules, fields, ledgers, submodules and plan capabilities the builder may safely reference.

  • Tenant: the workspace that will own the generated module.
  • Module Type: Master, Transaction, Report or Submodule.
  • Company: the company scope used for runtime access and related data.
  • Module number series: custom series for tenant modules; the core series is reserved for Jhapu internal and template work.

Choose the right module type

MasterReusable reference data

Use for entities such as projects, service types, departments or employees.

TransactionBusiness events

Use when records may calculate, post vouchers, move stock, report GST or follow approval.

SubmoduleReusable child rows

Use for line items that will be attached to a parent module. Submodules do not appear as standalone menu items.

Report is a separate path

A Report module does not create a normal transaction table. It opens the dedicated Report Configuration tab for filters, datasets, sections and output.

Name and capability switches

Give the module a clear unique name and a short menu label. Menu text is limited to 20 characters so navigation remains readable.

  • Show in menu: makes the completed module discoverable to permitted users.
  • Stock flow: enables Stock / Inventory configuration for a transaction.
  • Account voucher: enables Accounting / Voucher posting groups.
  • Approval workflow: allows a company approval policy to control transaction posting on eligible plans.
  • GST reporting: enables GST Mapping for a transaction.
  • Post stock value to accounts: connects eligible stock valuation with accounting when stock flow is enabled.
Enable only what the business process needs

Each switch adds configuration and testing responsibility. A simple Master normally needs none of the transaction switches.

Using the AI Module Assistant

Describe the business outcome, fields, relationships, calculations, list/search behaviour and posting requirements. AI may ask follow-up questions when verified metadata is not sufficient.

  1. 01
    Write the requirement

    Use business language, but include exact field names or rules when they matter.

  2. 02
    Answer clarifications

    The earlier conversation is retained, so respond only with the missing decision or verified reference.

  3. 03
    Review every tab

    An applied AI proposal is still a draft. Verify its columns, layouts, mappings and posting before saving.

Next guideProperties / DB Columns →