Tutorial 5 of 6 · ERP Ingestion
ERP Ingestion Pipeline
Simple / Ontology / bCLEARer pipelines, removal of meta_sector, and universal full-ERP bCLEARer pipeline (Tier 4).
Pipeline Overview
| Pipeline | Tier | Entry Point | Use Case |
|---|---|---|---|
| Simple | Tier 0–1 | POST /api/v1/ingest/client_id/component | Direct product/BOM ingestion, no ontology matching |
| Ontology | Tier 2–3 | POST /api/v1/ingest/client_id/component | Semantic matching, Exiobase graph, CPA/HS taxonomy |
| bCLEARer | Tier 4 Enterprise | POST /api/v1/ingest/client_id/component | Full ERP reconstruction — invoices, payroll, CRM, subscriptions, e-commerce, shipments |
The meta_sector URL parameter has been removed from all ingestion routes. The universal route isPOST /api/v1/ingest/client_id/component(and POST /api/v1/ingest/client_id). Pipelines Simple and Ontology are invariant in logic — only the URL changed.
Pipeline 2 — Ontology (Tier 2–3)
- ERP webhook → lca-daemon → tier check (Tier 2/3)
- Forward to lca-erp-connector → POST /api/v1/ingest/client_id/component
- universal_normalizer.py → key_ontology.py (26 languages) → GLiNER + SemanticMapper
- RDF loaded into Oxigraph: urn:ontology:source:tenant_id → urn:ontology:mapped:tenant_id
- Mapping rules applied → sku_mappings + bom_components + auto_lca impact calculation
Pipeline 3 — bCLEARer (Tier 4 Enterprise)
Full ERP reconstruction — any domain, any table, 26 languages. A Tier 4 Enterprise user can ingest their entire ERP without domain restriction.
16 canonical ERP entities across 6 macro-domains
Party master
Party — Organization, Supplier, Customer, Partner, Carrier
Invoicing
Invoice — Active, Passive, Credit Note, Proforma
Invoice lines
InvoiceLine — Tuple whole → Invoice, billsItem → ProductOrService
HR employees
EmployeeParty — PhysicalObject
Payroll
Payslip — Activity — hasEmployer, hasEmployee, hasCurrency
Timesheet/expense
TimesheetOrExpense — Activity
CRM leads
CRMLead — StateOfParticular
Subscriptions
Subscription — StateOfParticular
E-commerce orders
CommercialOrder — Activity
Order lines
OrderLine — Tuple
Shipments
Shipment — Activity
Products/services
ProductOrService — PhysicalObject
BOM links
ERPBomLink — Tuple whole → parent, part → component
Production/projects
ProductionOrProject — Activity
Facilities/utilities
UtilityReading & Facility — Activity / PhysicalObject
Customs/CBAM
TaxCustomsDeclaration — Activity
Strict Superset Property
bCLEARer is a strict superset of Simple and Ontology:
- Scenario A — Same minimal payload as Simple/Ontology: produces identical results in sku_mappings and bom_components — all existing tests pass unchanged.
- Scenario B — Full ERP with invoices, payroll, shipments: activates all 16 entity classes and rules P3–P6, reconstructing BOMs from production orders, supplier invoices, e-commerce shipments, utilities, and payroll allocations.