Browse by Java Class¶

This index maps important ADempiere Core Java classes to the engineering documentation where they are explained.

Use this page when a change starts from a Java class and you need to quickly identify:

What the class does.
Where it is documented.
What depends on it.
Whether the knowledge is already certified.

How to Use This Explorer¶

Identify the Java class involved in the change.
Locate the class in this index.
Open the related Knowledge Base document.
Review the certified behavior.
Follow the corresponding Playbook before modifying or deploying code.

Accounting Engine¶

Class	Area	Purpose	Used By	Documentation	Status
`Doc`	Accounting Engine	Base class for accounting documents.	All accounting document posting classes.	KB-212 Ch4	✅ Certified
`Doc_Invoice`	Accounting Engine	Posting logic for invoices.	Invoice posting, sales invoices, purchase invoices, CFDI analysis.	KB-212 Ch10	✅ Certified
`Doc_Order`	Accounting Engine	Posting logic related to sales and purchase orders.	Sales Order and Purchase Order posting analysis.	KB-212 Ch10	✅ Certified
`DocLine`	Accounting Engine	Base document line abstraction.	Invoice lines, order lines, allocation lines and posting line logic.	KB-212 Ch4 / KB-212 Ch5	✅ Certified
`Fact`	Accounting Engine	Represents accounting facts generated during posting.	Posting Engine, `Doc`, `FactLine`, `Fact_Acct`.	KB-212 Ch5	✅ Certified
`FactLine`	Accounting Engine	Represents individual accounting entry lines.	Posting Engine and final accounting entry generation.	KB-212 Ch5	✅ Certified
`MAccount`	Account Resolution	Resolves valid accounting combinations.	Accounting Engine, `FactLine`, account validation.	KB-212 Ch6	✅ Certified
`MAcctSchema`	Accounting Schema	Represents accounting schema configuration.	Posting Engine, account resolution and schema-specific posting rules.	KB-212 Ch7	✅ Certified

Persistence Framework¶

Class	Area	Purpose	Used By	Documentation	Status
`PO`	Persistence Framework	Base persistence object for ADempiere models.	All generated model classes such as `MInvoice`, `MOrder`, `MProduct`, `MBPartner`.	KB-212 Ch13	✅ Certified
`POInfo`	Metadata Layer	Provides table and column metadata used by persistent objects.	`PO`, generated models, Application Dictionary runtime.	Planned KB-217	📋 Planned
`MTable`	Application Dictionary	Represents ADempiere table metadata.	Application Dictionary, dynamic table access, model generation.	Planned KB-217	📋 Planned
`MColumn`	Application Dictionary	Represents ADempiere column metadata.	Application Dictionary, windows, fields, model generation.	Planned KB-217	📋 Planned
`Query`	Persistence Framework	Query builder used to retrieve model records.	Services, processes, model lookups and custom development.	Planned	📋 Planned

Database and Transactions¶

Class	Area	Purpose	Used By	Documentation	Status
`DB`	Database Layer	Provides database access utilities and SQL execution helpers.	Entire Core, processes, models, posting and custom SQL logic.	KB-212 Ch14	✅ Certified
`Trx`	Transaction Management	Manages database transactions.	`PO`, `DB`, posting, processes and batch operations.	KB-212 Ch14	✅ Certified
`CPreparedStatement`	Database Layer	Prepared statement wrapper used by the ADempiere database layer.	`DB`, SQL execution and low-level database operations.	Planned	📋 Planned

Cache¶

Class	Area	Purpose	Used By	Documentation	Status
`CCache`	Cache Layer	Generic cache used by ADempiere objects and metadata.	Models, metadata, account schema, dictionary objects.	KB-212 Ch15	✅ Certified
`CacheMgt`	Cache Administration	Global cache management and reset coordination.	Cache reset, system reload, dictionary refresh and runtime troubleshooting.	KB-212 Ch16	✅ Certified

Process Framework¶

Class	Area	Purpose	Used By	Documentation	Status
`SvrProcess`	Process Framework	Base class for server-side ADempiere processes.	All Java processes executed from ADempiere.	Planned KB-215	📋 Planned
`ProcessCtl`	Process Framework	Controls execution of ADempiere processes.	Process execution, UI process launcher and background execution.	Planned KB-215	📋 Planned
`ProcessInfo`	Process Framework	Carries process execution context and parameters.	`SvrProcess`, process launcher and process logging.	Planned KB-215	📋 Planned
`MPInstance`	Process Framework	Represents process instance metadata and execution state.	Process execution, parameters and process history.	Planned KB-215	📋 Planned

Validation and Extension Framework¶

Class	Area	Purpose	Used By	Documentation	Status
`ModelValidator`	Model Validation	Defines validation hooks for model events.	Custom validations, extension modules and business rules.	Planned KB-213	📋 Planned
`ModelValidationEngine`	Model Validation	Executes registered model validators.	Model lifecycle events, validation hooks and extension points.	Planned KB-213	📋 Planned
`CalloutEngine`	Callout Framework	Base class for field-level callouts.	Window field events and user interaction logic.	Planned KB-214	📋 Planned
`GridTab`	UI / Application Dictionary	Runtime representation of a window tab.	Windows, tabs, callouts and UI logic.	Planned KB-214 / KB-217	📋 Planned
`GridField`	UI / Application Dictionary	Runtime representation of a window field.	Windows, fields, callouts, display logic and validation rules.	Planned KB-214 / KB-217	📋 Planned

Document and Workflow Framework¶

Class	Area	Purpose	Used By	Documentation	Status
`DocumentEngine`	Document Lifecycle	Controls document status transitions and processing.	Invoices, orders, payments, allocations and other document types.	KB-212 Ch2 / KB-212 Ch3	✅ Certified
`DocAction`	Document Lifecycle	Interface for document actions such as complete, void, reverse and close.	Document models implementing lifecycle actions.	KB-212 Ch2 / KB-212 Ch3	✅ Certified
`MWFProcess`	Workflow Engine	Runtime workflow process.	Workflow execution and approval flows.	Planned KB-216	📋 Planned
`MWFActivity`	Workflow Engine	Runtime workflow activity.	Workflow steps, user actions and approvals.	Planned KB-216	📋 Planned

BLACK ERP Relevance¶

This index should be consulted before modifying Core behavior, extending ADempiere models, adding validations, creating processes or analyzing posting errors.

Typical usage:

Identify the Java class involved in the change.
Open the related Knowledge Base document.
Review the certified behavior.
Apply the corresponding Playbook before modifying or deploying code.