Which direction does data move between Oracle PeopleSoft and Fishbowl?

Data moves one way from Oracle PeopleSoft into Fishbowl. Vendor records, purchase orders, and line items flow from PeopleSoft finance into Fishbowl inventory so the warehouse team sees current procurement information. Changes in Fishbowl do not flow back to PeopleSoft; the two systems remain independent at the finance and inventory level.

How does ml-connector handle Oracle PeopleSoft's self-hosted architecture?

Each Oracle PeopleSoft customer runs their own on-premise installation with a unique hostname, port, and node name. ml-connector stores these connection details per customer and builds the correct REST service URLs for their instance. It also manages separate HTTP Basic Auth or OAuth2 credentials, so no Oracle-managed login is required.

What happens if either system is unavailable during a sync?

ml-connector tracks which records have been processed and retries on the next scheduled poll cycle, so no data is lost. If Oracle PeopleSoft is slow or temporarily down, the connector backs off and tries again at the next interval. Both systems remain independent; Fishbowl continues to work while waiting for PeopleSoft to come back online.

Oracle PeopleSoftFishbowl

Oracle PeopleSoft and Fishbowl integration

Oracle PeopleSoft manages finance and procurement. Fishbowl manages inventory and manufacturing. Connecting them keeps your purchase orders and vendor data in sync so that when procurement updates a PO in Oracle PeopleSoft, it flows into Fishbowl's inventory system without manual re-entry. Vendor master data, purchase order details, and line-item allocations can flow from finance into inventory, eliminating duplicate maintenance and reconciliation work. ml-connector bridges the API and authentication differences between the two platforms and handles the polling schedule you define.

How Oracle PeopleSoft works

Oracle PeopleSoft exposes vendors, purchase orders, invoices, and general ledger accounts through REST and SOAP service operations. Each customer runs their own on-premise installation on their own servers or Oracle Cloud Infrastructure, with a unique hostname, port, and node name. Authentication uses HTTP Basic Auth with operator ID and password, or OAuth2 bearer tokens on PeopleTools 8.58 and later. Webhooks are not available; write operations require SOAP Component Interface calls. Data is read via polling with date-range filters to handle large result sets.

How Fishbowl works

Fishbowl Advanced is an on-premise inventory and procurement system that exposes vendors, purchase orders, parts, and inventory through REST APIs. Customers run Fishbowl on their own server and provide the base URL, typically on port 2456. Authentication is session-based: a login POST call with username and password returns a bearer token for subsequent calls. Fishbowl has no webhooks and no rate limits; polling is the standard integration pattern. GL accounts are not exposed in Fishbowl; accounting integration happens through QuickBooks or Xero.

What moves between them

Vendor master records and purchase order details flow from Oracle PeopleSoft into Fishbowl on a schedule you define, typically daily or weekly. When procurement creates or updates a PO in Oracle PeopleSoft finance, ml-connector reads the PO header, line items, and associated vendor records from PeopleSoft and creates or updates the matching PO in Fishbowl's inventory system. Inventory staff see the PO arrive in Fishbowl with vendor, quantity, and scheduled-delivery dates already filled in, reducing data entry and errors. The sync is one-way from finance into inventory; changes in Fishbowl do not flow back to PeopleSoft.

How ml-connector handles it

ml-connector stores credentials for both systems encrypted and handles their different authentication models: HTTP Basic Auth for Oracle PeopleSoft (or OAuth2 if your PeopleTools version supports it) and session-token login for Fishbowl. Because Oracle PeopleSoft is self-hosted, it accepts the unique hostname, port, and node name for your instance. It polls PeopleSoft vendor and PO records with date-range filters to avoid large result sets that could impact your user performance, then transforms the data to match Fishbowl's REST structure. For Fishbowl, it logs in, exchanges credentials for a bearer token, and writes the PO records to the inventory system. If either platform is temporarily unavailable, ml-connector backs off and retries on the next poll cycle, tracking which records have been processed so no data is lost or duplicated. Every record is audited with timestamps and status.

A real-world example

A mid-sized manufacturer runs Oracle PeopleSoft for finance and procurement, and Fishbowl for inventory and manufacturing planning. Before the integration, the procurement team would enter new vendors and POs into PeopleSoft finance, then re-enter the same data into Fishbowl for inventory and shop-floor planning. This caused data drift between the two systems, and the warehouse often received POs with incorrect quantities or vendor information. With Oracle PeopleSoft and Fishbowl connected, each new PO entered in PeopleSoft finance automatically flows into Fishbowl overnight, pre-populated with vendor, line items, and expected delivery dates. The warehouse team sees accurate data, receiving teams confirm receipt in Fishbowl, and both systems stay aligned without manual re-keying.

What you can do

Sync vendor master data from Oracle PeopleSoft into Fishbowl so inventory staff work from current finance records.
Automatically create and update purchase orders in Fishbowl from Oracle PeopleSoft, eliminating dual data entry.
Handle Oracle PeopleSoft's unique hostname, port, and authentication method for each customer's self-hosted instance.
Poll both systems on a configurable schedule with date-range filters to minimize performance impact on your platforms.
Track every sync with a full audit trail and replay failed records when connectivity is restored.

Questions

Which direction does data move between Oracle PeopleSoft and Fishbowl?: Data moves one way from Oracle PeopleSoft into Fishbowl. Vendor records, purchase orders, and line items flow from PeopleSoft finance into Fishbowl inventory so the warehouse team sees current procurement information. Changes in Fishbowl do not flow back to PeopleSoft; the two systems remain independent at the finance and inventory level.
How does ml-connector handle Oracle PeopleSoft's self-hosted architecture?: Each Oracle PeopleSoft customer runs their own on-premise installation with a unique hostname, port, and node name. ml-connector stores these connection details per customer and builds the correct REST service URLs for their instance. It also manages separate HTTP Basic Auth or OAuth2 credentials, so no Oracle-managed login is required.
What happens if either system is unavailable during a sync?: ml-connector tracks which records have been processed and retries on the next scheduled poll cycle, so no data is lost. If Oracle PeopleSoft is slow or temporarily down, the connector backs off and tries again at the next interval. Both systems remain independent; Fishbowl continues to work while waiting for PeopleSoft to come back online.

Connect Oracle PeopleSoft and Fishbowl

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started