Infor Lawson Oracle Fusion Integration — Real-Time + Batch

Infor lawson oracle fusion integration is the design pattern that connects a running Infor Lawson S3 estate to a running Oracle Fusion estate during co-existence — either temporarily during migration parallel-run, or permanently as a hybrid architecture where some functions stay on Lawson (typically payroll for a specific population or supply chain for a specific facility) while others move to Fusion. The integration uses Oracle Integration Cloud (OIC) as the orchestration layer, with adapters built for Lawson S3 (database CDC or IPA-fronted REST), and connects to Fusion's REST APIs, SOAP services, and FBDI / HDL bulk-load interfaces. Common patterns: Lawson payroll → Fusion GL daily, Lawson supply chain receipts → Fusion AP, Fusion HCM worker master → Lawson payroll worker master. Real-time vs batch decision per integration based on business latency requirements.

Real-time integration uses Oracle Integration Cloud (OIC) event-driven flows: a transaction posted in Lawson immediately fires an event that OIC consumes, transforms and posts to Fusion via REST API. Latency: seconds to minutes. Use case: AP invoice approval workflow where a Lawson-source invoice needs to appear in Fusion AP within minutes. Batch integration uses scheduled extract-transform-load cycles: typically nightly, hourly or per-period. Latency: hours to days. Use case: GL journal posting from Lawson Payroll to Fusion GL where end-of-period batching aligns with close cycles. The infor lawson oracle fusion integration design picks the appropriate pattern per business flow — real-time isn't always better, because batching often aligns with how finance and HR already work.

IPA (Infor Process Automation) flows in Lawson typically handle AP approval, PO approval, expense report workflows, employee onboarding, position management, and dozens of vertical-specific automations. During migration, these flows get re-platformed to Oracle Integration Cloud (OIC) orchestrations. Each IPA flow is inventoried, its inputs/outputs catalogued, its business logic documented (including any embedded JavaScript), and an equivalent OIC orchestration is built. The new OIC flow reads from Fusion (the new source-of-truth) and writes to Fusion (the new target), with the same approval routing rules, same notifications and same audit trail. During parallel-run, both IPA-in-Lawson and OIC-around-Fusion run; at cutover, IPA is decommissioned and OIC takes over fully.

Smart Notifications in Lawson are event-driven alerts that subscribe materials managers, AP clerks, payroll supervisors, HR business partners and finance leads to specific transaction events (PO created, invoice received, payroll cycle completed, employee terminated, inventory reorder point crossed). During infor lawson oracle fusion integration, every Smart Notification subscription is inventoried with subscriber list, trigger condition and notification template. An equivalent Fusion Workflow / BIP burst is built that fires on the corresponding Fusion event. Subscriber list migrated (HR records map workers to Fusion users), trigger conditions translated to Fusion event predicates, notification template re-rendered in Fusion's notification format. End-users see the transition transparently: same alerts, same routing, same content — just sourced from Fusion.

Healthcare integration is where most hospital Lawson-Fusion integration projects spend the most engineering effort. GHX (Global Healthcare Exchange) supplier exchange integration is repointed at the gateway level: GHX continues posting standard 850/855/856/810 EDI documents, but the receiving endpoint moves from Lawson Supply Chain to Fusion Procurement via OIC adapter. Patient accounting interfaces (Epic / Cerner / MEDITECH → Lawson AR for charge posting, → Lawson Materials for charge-master sync) similarly repoint from Lawson to Fusion. The encounter-level interface contract is preserved (same field semantics, same posting cadence) — only the receiving system changes. Hospital revenue cycle teams see transparent transition; same charges post to the same patient encounters, just into Fusion AR rather than Lawson AR.

Payroll integrations are typically the highest-volume and most time-sensitive integration in the estate. ADP, Kronos, SilkRoad and similar systems feed timekeeping data into Lawson Payroll for gross calculation, then receive net pay file outputs for direct deposit and tax remittance. During migration, OIC adapters are built for ADP, Kronos and SilkRoad that feed the same timekeeping into Fusion HCM Payroll instead of Lawson Payroll, and produce the same net pay file format outputs. Adapter contracts mirror existing field semantics exactly so downstream tax remittance and direct deposit don't need changes. Bi-weekly or semi-monthly payroll cycles cut over together (Lawson cycle 12 is the last in Lawson, cycle 13 is the first in Fusion) for clean break with no overlap risk.

Yes. Some organisations choose permanent hybrid: Lawson Payroll continues running for a specific worker population (e.g., union employees with bespoke pay rules that haven't yet been built in Fusion HCM Payroll), or Lawson Supply Chain continues for a specific facility (e.g., a rural hospital not yet ready for Fusion SCM cutover). The same infor lawson oracle fusion integration pattern that runs during temporary parallel-run runs permanently: OIC flows bridge the two systems, Lawson productlines stay live, and the bidirectional integration keeps both estates synchronised. Customers commonly use hybrid as a 12–24 month bridge before completing full Fusion cutover, or indefinitely for specific edge populations.

Mongoose-built shadow systems (custom screens, custom DB tables, custom workflows built on the Mongoose framework) require explicit integration design during co-existence. If the Mongoose system is migrated to VBCS extensions on Fusion, the data behind it is migrated and the new VBCS UI replaces the Mongoose screen. If the Mongoose system is retained on Lawson temporarily, OIC integration keeps its data synchronised with Fusion (e.g., a Mongoose-built nursing certification tracker continues running on Lawson, but new certifications post via OIC to Fusion HCM Talent Management for unified reporting). The integration design ensures no Mongoose-resident data becomes an orphan during co-existence; every Mongoose record is either migrated or actively synchronised.