Accelerator · Integration package
Plex ODBC Master Config Package
Fuuz accelerator: Plex ERP ODBC master configuration — 40+ numbered integration flows for master data sync
Version: 1.0.1 Platform: Fuuz (any)
Overview
The Plex ODBC Master Data Configuration package installs the complete set of Fuuz master data import flows for Plex ERP customers using ODBC connectivity. It registers 40+ numbered integration flows — each responsible for importing a specific Plex data entity into Fuuz — as MasterDataFlowConfiguration records managed by the package-master-data-flow-config-accelerator orchestration layer.
Plex ODBC flows extract data directly from Plex stored procedure endpoints (via ODBC connection) and upsert records into Fuuz data models covering the full manufacturing and logistics data model: facilities, locations, customers, suppliers, products, workcenters, modes, events, BOM structures, inventory, and more.
This is an installer package (no interactive screens or custom models) — it creates flow configuration records and verifies uniqueness constraints before installing. It requires an active Plex ODBC Connection in the Fuuz platform.
Package Contents
plex-odbc-master-config/
├── manifest.json
├── package-data.json
├── install/ 5 install steps
└── preinstall/ 3 preinstall validation steps
Registered Import Flows (40+)
Each flow is sequentially numbered in its description for ordered execution. The full set covers:
Site & Location Hierarchy
| # | Flow Name | Source |
|---|---|---|
| 01 | Facilities from Plex ODBC Buildings | Plex Buildings |
| 02 | Location Type from Plex ODBC | Plex Location Types |
| 03 | Location Status from Plex ODBC | Plex Location Statuses |
| 04 | Locations from Plex ODBC | Plex Locations |
| 05 | Customer Stage from Plex ODBC | Plex Customer Stages |
Customers & Suppliers
| # | Flow Name | Source |
|---|---|---|
| 06 | Customers from Plex ODBC | Plex Customers |
| 07 | Customer Addresses from Plex ODBC | Plex Customer Addresses |
| 10 | Contacts from Plex ODBC | Plex Contacts (Supplier/Customer) |
| 24 | Approved Suppliers from Plex ODBC | Plex Approved Suppliers |
Products & BOM
| # | Flow Name | Source |
|---|---|---|
| 11 | Product Stages from Plex ODBC | Plex Product Stages |
| 12 | Product Types from Plex ODBC | Plex Product Types |
| 13 | Products from Plex ODBC Parts | Plex Parts |
| 14 | Product Strategies from Plex ODBC | Plex Product Strategies |
| 15 | Processes from Plex ODBC | Plex Processes |
| 16 | Product Strategy Process Type from Plex ODBC | Plex Part Operations Type |
| 17 | Product Strategy Processes from Plex ODBC | Plex Part Operations |
| 18 | Customer Products from Plex ODBC | Plex Customer Parts |
| 26 | Product Strategy Process BOM from Plex ODBC | Plex BOM |
| 39 | Product Custom Data from Plex ODBC | Plex Part Attributes |
Logistics & Inventory
| # | Flow Name | Source |
|---|---|---|
| 22 | Logistical Units from Plex ODBC Container Types | Plex Container Types |
| 23 | Approved Logistical Units from Plex ODBC | Plex Part Operation Approved Container |
| 38 | Adjustment Codes from Plex ODBC | Plex Adjustment Codes |
| 40 | Inventory Status from Plex ODBC | Plex Container Statuses |
Production & Workcenters
| # | Flow Name | Source |
|---|---|---|
| 25 | Approved Workcenters from Plex ODBC | Plex Approved Workcenters |
| 27 | Events from Plex ODBC | Plex Workcenter Events |
| 28 | Modes from Plex ODBC | Plex Workcenter Statuses |
| 29 | ModeEvent from Plex ODBC | Plex Workcenter Event Statuses |
Additional flows (30–37, and others) cover shipment statuses, work orders, scheduling data, and supplementary reference tables.
Install Process
Preinstall (3 steps): Validates uniqueness constraints for all flow IDs and names before installation begins. Throws an error if any flow already exists with a conflicting ID or name, preventing duplicate registration.
Install (5 steps):
1. Creates all MasterDataFlowConfiguration header records (one per import flow) with the flow ID, name, description, and Integration type
2. Registers each flow's connection configuration — links the configuration record to the Plex ODBC connection
3. Sets initial schedule definitions for each flow (e.g., nightly, hourly)
4. Sets active status based on recommended defaults (most flows active, some requiring manual activation)
5. Deploys the flow definitions to the application as runnable integration flows
Installation
- Ensure
package-master-data-flow-config-acceleratoris installed first - Ensure a Plex ODBC
Connectionis configured in Fuuz Connections settings and its connector is active - Import this package via Fuuz Package Manager
- Review installed
MasterDataFlowConfigurationrecords and adjust schedules as needed - Enable desired flows by setting
active = true - Trigger initial full sync by running all active flows manually from the Master Data Import dashboard
Dependencies
- Fuuz Platform — any version
package-master-data-flow-config-accelerator— required; provides theMasterDataFlowConfigurationmodel and scheduling infrastructure- Plex ERP with ODBC access enabled
- A configured Plex ODBC
Connectionin the Fuuz platform - Target data models must exist (provided by
application-mes-accelerator,application-wms-accelerator, orapplication-machine-monitoring-accelerator)
Built on the Fuuz Industrial Operations Platform
Before you install
A Jump Start, Not A Finished Answer
An accelerator is a pre-built, configurable starting point that addresses the bulk of the common challenges in its domain. It is not intended to solve every possible variation off the shelf — requirements that fall outside it are expected and normal for the model, not a shortcoming of this one.
Standard
Delivered and working as-is. No configuration needed.
Configurable
A base capability you adapt with the platform's own no-code and low-code tools — screen builder, transforms, workflow rules, flow parameters — without professional services.
Custom development
Feasible on the platform but outside this accelerator's current scope. A scoped change through Fuuz or a certified partner.
Once installed, it is yours
Installation forks the flows, models and screens into your environment as your own copies. Later versions published against this accelerator do not propagate to you automatically — picking up a change means deliberately re-applying it.