Report Configuration

Report modules use a dedicated builder

Select Report as the module type. Instead of ordinary DB Columns, forms and transaction posting tabs, Jhapu shows Module Detail and Report Configuration.

• Report key and heading: stable identity and user-facing title.
• Report type: the supported execution/rendering model.
• Menu and access: where the report appears and who may run it.
• Output: supported print/export options.

Variants and filters

Variants provide named ways to run the same report, while filters collect the business parameters used by datasets.

• Use From Date and To Date for period-based reports.
• Use company-scoped lookups for Project, Account, Item, Store or other masters.
• Use fixed choices for status, category or summary/detail mode.
• Give every filter a clear label and default only when the default is safe.

Datasets and joins

A dataset identifies an approved source table, selected fields, aggregates and structured relationships to other verified sources. Use relationships that reflect actual keys; do not invent table or field names.

• Start with the smallest dataset that can answer the report question.
• Select only required columns and aggregations.
• Use verified joins and company scope.
• Map report filters to dataset fields explicitly.
• Test empty results, one row and large result sets.

Sections and presentation

Sections determine how datasets appear—such as a summary, detailed table or grouped output. Choose headings, field order, number/date formats, alignment and totals that match the management question.

1. 01
   Define the question

   Write the decision the report should support before selecting fields.

2. 02
   Configure filters and data

   Keep sources and relationships controlled and auditable.

3. 03
   Design sections

   Put the most important totals first and supporting details afterwards.

4. 04
   Reconcile

   Compare known periods against source data before releasing the report.