AutoCore Data Model — Complete Entity-by-Entity Mapping

Source of truth: Every entity and field below is derived from actual production data files in autocore/data/, entitydef/entitymodel.xml, and entitydef/entitymodel_vcdb.xml.

[!IMPORTANT] Single-Threaded Processing for Member Products While standard OFBiz data imports (like ImportDataFromCSV1) utilize multi-threading, Member Product CSV imports (configId=8005) run via a Single-Threaded route (importMemberProductWrapper) in production. This is because importing a member product orchestrates a complex entity graph (Product → Pricing → Inventory → Features → Category Membership), uses raw JDBC batching for high-frequency ProductFacility changes, and maintains global scorecard state (newPartsAdded, globalLBMMapCount). Multi-threading would cause race conditions and database deadlocks across these interdependent writes.

Part 1 — The PIES Domain (Product Information)​

1.1 Product (Extended OFBiz Entity)​

The hub of the entire data model. Every other entity connects here.

Dual-key identity:

Field Mapping (from production data):

PIES EXPI Status Codes (from AutoCoreTypeData.xml):

1.2 LegacyBrandMapping​

Purpose: Translates legacy ERP line codes into modern AAIA brand IDs. This is the first operation performed by importMemberProductWrapper before any product record can be resolved or upserted.

Import service: configId=8009 → importLegacyBrandMapping

1.3 ProductCategory & ProductCategoryType​

The AutoCore model uses a very specific category type hierarchy (from AutoCoreTypeData.xml):

From AutoCoreCatalogData.xml, the root catalog is AAIA_ROOT_CATALOG with AAIA_PART_SEARCH_CAT as the search category. OE parts use a separate OE_CATALOG → OE_PART_SEARCH_CAT.

1.4 ProductPackage & ProductPackageType​

Maps to PIES Package Segments (physical dimensions, barcodes, weight).

PIES PACK Codes (from AutoCoreTypeData.xml):

• EA = Smallest Pack (Consumer Level)
• PK = Inner Pack (shippable)
• BX = Inner Pack (non-shippable)
• CA = Case
• PL = Pallet

1.5 ProductFacility (Extended — JDBC-Batched)​

Tracks inventory at a specific warehouse. Updated via raw JDBC batching (not OFBiz Entity Engine) during importMemberProduct to avoid performance degradation and locking.

Inventory lookup methods (configured per Facility.inventoryLookupMethod):

1.6 ProductPrice (Extended)​

One product can carry multiple simultaneous price points for different channels, tiers, and agreements.

Key productPriceTypeId values (from AutoCoreTypeData.xml):

1.7 ProductFeature & ProductFeatureType​

The flexible extension layer for PIES/PAdb attributes that don't fit fixed Product columns.

Key productFeatureTypeId values (from AutoCoreTypeData.xml):

Feature Application Types (how features attach to products):

• PADB_ATTRIBUTE — PAdb standard attribute
• SAT_ATTRIBUTE — Supplies Accessories & Tools attribute
• STANDARD_FEATURE — Standard vehicle feature (used in ACES)

1.8 ProductAttribute​

Key-value store for product attributes that are not standard PAdb features.

From AutoCoreCatalogData.xml (OE parts):

<ProductAttribute productId="2088" attrName="oePartCoreFlag" attrValue="N" attrType="OE_PART_CORE_FLAG"/>

Stores dynamic PIES data like isPcdbAttribute, sequenceNum, languageId.

1.9 GoodIdentification​

Cross-reference table mapping product IDs across multiple external systems.

1.10 ProductContent & ProductContentType​

Rich media and text content attached to a product (from AutoCoreTypeData.xml):

Part 2 — The ACES / VCdb Domain (Vehicle Configuration)​

The ACES domain uses the OFBiz Product entity as a polymorphic node to represent Vehicles. This is a critical design decision — vehicles are Products with isVirtual=Y or isVariant=Y, connected via ProductAssoc and ProductFeatureGroupProductAppl.

2.1 Three-Level Vehicle Hierarchy​

BaseVehicle (isVirtual=Y, isVariant=N)
    └── Vehicle [per Region] (isVirtual=Y, isVariant=Y)
            └── VehicleConfig (isVirtual=N, isVariant=Y)

From AutoCoreVCDBData.xml:

<!-- Level 1: Base Vehicle (Year+Make+Model) -->
<Product productId="1010" productName="2009 Chevrolet Suburban 1500" internalName="30025"
         isVirtual="Y" isVariant="N"/>

<!-- Level 2: Vehicle (Submodel + Region) -->
<Product productId="1250" productName="2009 Chevrolet Suburban 1500 LT" internalName="72128"
         isVirtual="Y" isVariant="Y"/>
<ProductGeo productId="1250" geoId="USA" description="1"/>

<!-- Level 3: VehicleConfig (Engine+Transmission+Brake+Body+Drive configs) -->
<Product productId="1100" internalName="VC-1100" isVirtual="N" isVariant="Y"/>

2.2 Vehicle Relationship Chains​

2.3 Vehicle Configuration Feature Groups (from AutoCoreVCDBTypeData.xml)​

Each VehicleConfig product has a set of ProductFeatureGroups attached, one per system:

2.4 Vehicle Category Classification​

The Make/Model/Year classification is done via ProductCategory + ProductCategoryMember:

<ProductCategory productCategoryId="1010" productCategoryTypeId="VEHICLE_MAKE" categoryName="47" description="Chevrolet"/>
<ProductCategory productCategoryId="1011" productCategoryTypeId="VEHICLE_MODEL" categoryName="497" description="Suburban 1500"/>

<!-- Associates BaseVehicle to Make, Model, and Year categories -->
<ProductCategoryMember productCategoryId="1010" productId="1010"/>  <!-- Make -->
<ProductCategoryMember productCategoryId="1011" productId="1010"/>  <!-- Model -->
<ProductCategoryMember productCategoryId="1014" productId="1010"/>  <!-- Year -->

2.5 Region Mapping​

Vehicles are region-scoped via ProductGeo:

Vehicle region group VRG includes USA, CAN, and MEX.

Part 3 — The Organization / Party Domain​

3.1 Party Hierarchy​

From AutoCoreExtData.xml, the core organizational structure:

OE Manufacturers (from AutoCoreCatalogData.xml):

3.2 National Account Programs (NAP)​

The NAP system ties pricing to customer groups via Agreement entities.

Flow: Party (AutoCore) → Agreement (NAP_AGREEMENT) → Party (CustomerGroup) → PartyIdentification (NAP_PRICE_CODE)

Part 4 — Import Configuration Map​

From AutoCoreExtData.xml, all DataManagerConfig entries:

Part 5 — Full Entity Relationship Diagram (ERD)​

Part 6 — ACES Vehicle Hierarchy ERD​

Part 7 — Import Workflow Sequence​

Generated from: autocore/data/*.xml | Last updated: 2026-05-02