Purpose-built ETL platform for Infor LX (BPCS) to Oracle Fusion migration — Financials, Manufacturing, Inventory, Order Management. IBM i / DB2 for i extractors, EBCDIC translation, RPG / COBOL discovery, FBDI / HDL emitters. 40–60% faster than consultant-led programmes — and no RPG developers required on your side.
Most Infor LX (BPCS) projects don't slip in the SQL extract. They slip in the IBM i skills bottleneck, RPG customisation archaeology, Query/400 report rebuild and AS/400 character-set handling.
Infor LX, formerly BPCS (Business Planning and Control System), was originally built by SSA in the 1980s for the IBM System/38 and later AS/400 platforms, then acquired by Infor through a series of consolidations. The product line is mature and stable, but the underlying architecture — RPG IV programs, COBOL modules, CL command languages, DDS-defined display files, DB2 for i physical files with packed-decimal numerics and EBCDIC character sets — is 1980s-era IBM midrange. The talent pool needed to read, refactor or extract that environment is shrinking fast.
Consultant-led migrations typically lose months in two places: hunting down an RPG developer who can confirm whether a 1995-era custom program is still in use, and translating IBM i character-set quirks (CCSID 037, 285, 1140, 1148) into clean UTF-8 without corrupting decimal precision in COMP-3 packed-decimal fields. Syntra ETL absorbs both problems. The Infor LX (BPCS) to Oracle Fusion migration discovery engine crawls the BPCS libraries (LXFILES, LXMODOBJ and any customer-added libraries) directly, indexes every RPG / COBOL program, every Query/400 report, every DDS display file, and produces a complete customisation inventory in days — no AS/400 expert required.
Whether you are moving Infor LX 8.x Financials and Manufacturing to Oracle Fusion in a big-bang cutover, doing a phased migration (Financials first, Manufacturing next quarter, Order Management after that), or running a hybrid where shop-floor stays on BPCS for 18 months while Financials moves first — the same engine handles every workflow with the same reconciliation rigour and the same audit-trail evidence pack.
And how the Syntra ETL platform addresses each one — before they consume your timeline.
Native JDBC extraction against DB2 for i via the IBM i Access drivers — no proprietary middleware, no RPG code on the source side, no AS/400 expert required from your team. Read-only user profile with library-scoped object authority.
CCSID-aware translation handling 037, 285, 1140, 1148 and the long tail of regional code pages. COMP-3 packed-decimal and zoned-decimal numeric fields preserved with full precision through the round-trip.
BPCS library discovery crawls every RPG IV / III, COBOL, CL and DDS object in LXFILES, LXMODOBJ and custom libraries. Classification report identifies what is in use, what is orphaned, what is critical.
Every Query/400 query and IBM i report inventoried, classified by business value, and rebuilt as Fusion OTBI dashboards, BI Publisher pixel-perfect reports or Smart View Excel templates.
BPCS BOMs (PSM / PSC), routings (RTM / RTO), work orders (MHM / MHD), shop-floor hours (HRM) and MRP (MAD) translated to Fusion Manufacturing's item / structure / routing / work-definition model with full lot and serial traceability.
BPCS multi-currency (MCM), multi-company (CCM) and multi-warehouse (WHM) configurations mapped to Fusion Legal Entities, Ledgers, Inventory Organizations with historical-rate carry-over preserved.
A repeatable, governed workflow built for BPCS's particular complexity. Typical full-scope timeline: 14–20 weeks.
DB2 for i extractor catalogs every BPCS table (GLM, GLT, IIM, IIH, ECH, MHM, etc.), every RPG / COBOL / CL / DDS object in scope libraries, every Query/400 report, every active interface and every IBM i journal in retention. Output: complete customisation inventory, source-volume estimate, hardware-retirement plan, sized assessment with risk register.
BPCS Company → Fusion Legal Entity / Ledger; Warehouse → Inventory Organization; ChartField → COA segment; Item Master → Fusion Item; RPG-bound business rules → Visual Builder / AMX. Reviewed and signed off by finance, manufacturing ops, supply chain and compliance leads.
DB2 for i extractor streams every in-scope BPCS table to Parquet, partitioned by fiscal year and company, with EBCDIC-to-UTF-8 conversion, packed-decimal handling and hash-signed manifests. IBM i journals captured in parallel for SOX audit evidence.
Crosswalks applied, BPCS UDFs collapsed to Fusion DFFs, FBDI / HDL payloads generated, validated against current Fusion 26x release schemas. Errors surfaced locally with row-level diagnostics — never wait for a 4-hour Fusion ESS job to fail on row 47,000.
FBDI ZIPs submitted to Fusion ESS, monitored to completion, reconciled at row, sum and hash level. In parallel, critical Query/400 reports rebuilt as OTBI / BI Publisher and validated against BPCS equivalents. Manufacturing item-structure-routing built in Fusion.
1–2 month-end close cycles in parallel (BPCS + Fusion), deltas captured and replayed, reconciled to the cent, sign-off pack issued. BPCS / AS/400 moves to read-only archive mode; new transactions flow to Fusion only. IBM i hardware can begin licence-and-power-down.
No more bespoke ODBC scaffolding or RPG export programs. Just configure scope, run, reconcile.
GLM master, GLT transactions, GBM budgets, APH/APT/APO Accounts Payable, RAH/RAT/RAO Accounts Receivable, ACL supplier master, CIM customer master, FAM/FAT Fixed Assets — full multi-company, multi-currency context preserved.
PSM/PSC bills of material, RTM/RTO routings, MHM/MHD work orders, HRM shop-floor hours, MOD operations, MAD MRP, plus all the engineering-change history needed for Fusion Manufacturing's work-definition model.
IIM item master, IIH item balance, ITH inventory transactions, LOC location master, WHM warehouse master — multi-warehouse configurations mapped to Fusion Inventory Organizations with lot / serial traceability intact.
ECH order header, ECL order line, PRH/PRL pricing, SHP shipment history, CIM customer master, plus the open-order, backorder and credit-hold context needed for Fusion Order Management cutover.
HPO purchase order header, HPL purchase order line, supplier master from ACL, three-way-match history, plus open receipt and accrual context for Fusion Procurement and Cost Management.
RPG IV / III, COBOL, CL and DDS objects in LXFILES, LXMODOBJ and custom libraries discovered and indexed. Query/400 reports catalogued. Feeds the discovery-classification-rebuild loop without manual AS/400 screenshots.
A typical Infor LX (BPCS) to Oracle Fusion migration covering Financials, Manufacturing, Inventory and Order Management with 10–20+ years of IBM i history and a multi-TB DB2 footprint runs 14–20 weeks with Syntra ETL versus 12–18 months on consultant-led programmes. Single-pillar work (Financials-only or Manufacturing-only) completes in 8–11 weeks. The acceleration comes from pre-built IBM i / DB2 for i extractors that already understand BPCS file naming (SYS770, SYS776, GLM, IIM, MBM, MAD, ECH, ECL etc.), governed RPG / COBOL field-to-Fusion crosswalks, AS/400 character-set translation (EBCDIC → UTF-8 with COMP-3 packed-decimal handling) and FBDI / HDL emitters validated against the current Oracle Fusion 26x release. The Infor LX (BPCS) to Oracle Fusion migration almost always carries an extra 2–3 weeks at the front to deal with the RPG / COBOL skills shortage that customers face when they try to staff the project themselves.
Infor LX (formerly BPCS, originally from SSA before the Infor acquisition) is a 1980s-architected ERP running native on IBM i (AS/400), powered by RPG IV and COBOL with DB2 for i underneath. While Infor still ships LX 8.x updates, the writing is on the wall: an aging IBM i installed base, a critical shortage of RPG developers, escalating IBM hardware-and-licence costs, no realistic AI / mobile / API roadmap, and Infor's own clear strategic push toward CloudSuite Industrial as the modern successor. Customers migrate Infor LX (BPCS) to Oracle Fusion to escape the skills cliff, retire AS/400 hardware, consolidate onto a SaaS ERP with quarterly innovation, gain native AI for forecasting and anomaly detection and unlock a global multi-currency / multi-language footprint that BPCS was never designed for.
Syntra ETL supports the full BPCS footprint. Financials: General Ledger (GLM master, GLT transactions, GBM budgets), Accounts Payable (APH header, APT detail, APO open items, supplier master ACL), Accounts Receivable (RAH header, RAT detail, customer master CIM), Fixed Assets (FAM master, FAT transactions). Manufacturing: BOM (PSM bill master, PSC components), Routings (RTM master, RTO operations), Work Orders (MHM header, MHD detail), Shop Floor Control (HRM hours, MOD operations), MRP (MAD master). Inventory: Item Master (IIM), Item Balance (IIH), Inventory Transactions (ITH), Locations (LOC). Order Management: Sales Orders (ECH header, ECL line), Pricing (PRH header, PRL line), Shipments (SHP). Procurement (HPO header, HPL line). Plus all the Custom Fields and User-Defined Fields (UDFs) added over 20 years of BPCS customisation.
DB2 for i (the database that ships on IBM i) is fully supported via JDBC and the IBM i Access drivers; no proprietary middleware is required. The Syntra ETL Infor LX extractor authenticates via an IBM i user profile with read-only object authority on the BPCS libraries (LXFILES, LXMODOBJ, custom libraries), queries the physical files (PF) directly using SQL through QSYS2/SYSIBM views, handles packed-decimal (COMP-3) and zoned-decimal field translation, deals with EBCDIC-to-UTF-8 character-set conversion (CCSID 037 / 285 / 1140 / 1148 etc.), and streams output to cloud object storage as Parquet plus hash-signed manifests. Multi-environment IBM i shops (separate LPARs for prod, QA, dev) are extracted in parallel. No RPG, CL or COBOL code is needed on the source side.
Yes — BPCS multi-currency (MCM currency master, the in-flight currency translation in GLT and APH/RAH), multi-warehouse (LOC location master and WHM warehouse master), and multi-company (CCM company master) configurations are fully supported. The Syntra ETL crosswalk engine maps BPCS Company codes to Fusion Legal Entities and Ledgers, BPCS Warehouses to Fusion Inventory Organizations, and BPCS Currency codes to Fusion Currencies (with the historical-rate carry-over preserved for retro-reporting). Customers running 30+ warehouses across multiple legal entities in BPCS routinely consolidate to 8–12 Fusion Inventory Organizations during the migration without losing transaction-level traceability.
RPG IV programs, COBOL programs, CL command languages, Query/400 reports and RPG-based custom screens don't translate to Fusion — they are platform-bound to IBM i. The Syntra ETL assessment inventories every custom RPG / COBOL program, CL command, Query/400 report and DDS-defined display file in the BPCS libraries, classifies each by business value (in-use vs orphaned, critical vs nice-to-have), and proposes a Fusion-equivalent disposition: native Fusion functionality, OTBI dashboard, BI Publisher report, Smart View, Visual Builder extension, or retire-as-redundant. Customers typically find 50–70% of legacy BPCS customisations are redundant under Fusion's native breadth. The remaining 30–50% get rebuilt during the Infor LX (BPCS) to Oracle Fusion migration so go-live includes the customisation layer, not just the data.
BPCS retains transaction-level audit trails in dedicated audit files (e.g. GLAT for GL audit, APAT for AP, IIAT for inventory) and IBM i journals at the database layer (QSQJRN, application journals). SOX requires 7-year retention of financial records with auditable trace from GL journal back to originating transaction. Syntra ETL preserves the full chain: every BPCS audit-trail record is extracted, hash-signed, and either migrated to Fusion (where appropriate) or routed to the long-term BPCS archive with a signed evidence pack and read-access logging. The IBM i journal extracts are also captured at the Parquet layer so internal audit can drill from a Fusion GL journal back to the originating RPG program execution timestamp on the AS/400 for the full retention window — even after the IBM i hardware is decommissioned.
No. Syntra ETL's Infor LX extractor runs as a read-only IBM i user profile with object-level authority limited to the BPCS libraries actually in scope. All SQL queries are routed through QZDASOINIT server jobs (the standard IBM i database server jobs) which respect IBM i workload management — heavy extracts are throttled to off-peak windows and run in a dedicated subsystem if needed. No CL commands are submitted, no RPG programs are called, and no BPCS user activity is interrupted. Live order entry, MRP runs, and shop-floor transactions continue uninterrupted on the IBM i. The cutover is a defined moment scheduled for a planned shutdown window (typically a weekend close) so the IBM i can be moved to read-only archive mode cleanly.
Book a 30-minute discovery call. We'll walk through your BPCS modules, IBM i landscape, RPG / COBOL customisation profile, multi-company / multi-warehouse design and reporting estate — and give you a concrete timeline and budget before the call ends. No RPG expert required on your side.