Table

1. Overview

The Table module in Sumo Ledger provides a general-purpose data storage and lookup facility. Tables act as reference data stores that processes can read from and write to during transaction processing. Common use cases include storing KYC data, loan records, pricing information, credit scorecards, and other structured data that processes need to access.

Unlike accounts and transactions (which follow strict double-entry accounting rules), tables are flexible key-value or record-based stores that support any schema.

Navigation: Table (main sidebar menu)

URL: https://las.ledger.raralabs.dev/table

---

2. Table List View

The list view displays all configured tables with the following columns:

Column	Description
Checkbox	Select one or more tables for bulk actions.
ID	The unique system identifier for the table (e.g., kyc, dpd, loan_accounts).
Name	The display name of the table (typically matches the ID).
Description	A human-readable description of the table's purpose (e.g., Customer's KYC, Days Past Due Table, Scrip Prices).

The list shows pagination at the bottom (e.g., 1-12 / 12) with configurable items per page.

List View Actions

• Import Table Data (.json): Allows you to upload a JSON file to bulk-import table data.

---

3. Table Detail View

Clicking on a table name opens its data view.

3.1 Page Header

Breadcrumb: Table > [table_name] (e.g., Table > kyc).

3.2 Actions

Element	Description
+ New Data	Opens a form to add a new record to the table.

3.3 Data Table

The detail view displays all records stored in the table. The columns are dynamic and depend on the schema of the specific table. For example, a kyc table might show:

• id, Value Date, cif_id, sol_id, name, gender, dob, mobile_number, email, father_name, grand_father_name, id_num

Each table has its own unique set of columns based on the data it stores.

3.4 Pagination

Records are paginated (e.g., 1-4 / 4) with configurable items per page.

---

4. Adding Data to a Table

Click "+ New Data" on the table detail page to add a new record. The form fields are dynamically generated based on the table's schema.

---

5. Importing Table Data

Click "Import Table Data (.json)" on the table list page to bulk-import data. The JSON file should match the table's expected schema.

---

6. How Tables Work in Practice

Integration with Processes

Tables are referenced by process stages that need to look up or store data. For example:

• A KYC check stage might read from the kyc table to verify customer identity.
• A loan disbursement stage might write to the loan_accounts table to record the disbursement.
• A pricing stage might read from scrip_prices to get current market prices.

Common Table Types

Table	Purpose
kyc	Customer Know-Your-Customer data
dpd	Days Past Due tracking for loans
loan_accounts	Loan account records
scrip_prices / scrip_price	Market price data for securities
payday_scorecard	Credit scoring results
payday_loans	Loan disbursement records
user_holdings	User portfolio/holdings data
cic_info	Credit information center data
pledged_scrips	Pledged securities records
cheque_dishonor_registration	Dishonored cheque records

---

7. Best Practices

1. Use descriptive table names and descriptions. This helps other administrators understand the purpose of each table at a glance.
2. Import data in bulk using JSON. For initial setup or migration, JSON import is faster than manual entry.
3. Keep table schemas consistent. All records in a table should follow the same field structure to avoid processing errors.
4. Review table data periodically. Stale or incorrect reference data can cause process failures.
5. Note the distinction between Table (main menu) and Table (configuration). The main menu Table module is for viewing and managing data records. The Configurations > Table section is for defining the table schemas themselves.