Ellipse Gradient for Header

Oracle PeopleSoft Integration Guide

Oracle PeopleSoft integrates with enterprise systems through Integration Broker, REST and SOAP services, asynchronous messages, outbound requests, and configured file exchanges.

Oracle PeopleSoft integration options at a glance

Oracle PeopleSoft integrations are primarily implemented through PeopleTools Integration Broker, which supports REST services, SOAP web services, synchronous and asynchronous service operations, messages, queues, routings, handlers, and gateways. PeopleSoft can also exchange flat files and batch outputs for payroll, finance, procurement, and legacy processes. Outbound notifications are possible for selected configured events, but they are not a universal webhook stream. Martini can consume PeopleSoft REST or SOAP endpoints, orchestrate Integration Broker interactions, receive configured outbound requests, parse XML or JSON, process files, and map effective-dated PeopleSoft data into downstream systems with validation, retries, and reconciliation.

Integration pointSupported by Oracle PeopleSoft?Common use casesHow Martini supports it
REST APIsYesPeopleSoft can expose and consume REST services through Integration Broker, using JSON or XML and HTTP methods according to the configured service definition. REST is suitable for API-led employee, supplier, procurement, and organizational integrations.Martini can consume PeopleSoft REST endpoints, map request and response payloads, apply business rules, and expose a controlled API for downstream consumers.
SOAP APIsYesPeopleSoft Integration Broker supports SOAP and WSDL-based web services, including delivered and custom synchronous or asynchronous service operations. SOAP remains relevant for existing enterprise integrations.Martini can consume PeopleSoft SOAP services, manage configured authentication, transform XML and namespaces, and handle transport or business errors in workflows.
Integration Broker messagingYesIntegration Broker supports inbound and outbound messages, service operations, queues, routings, handlers, transformations, and gateways. This messaging model is central to many PeopleSoft integrations.Martini can orchestrate calls to Integration Broker endpoints, receive configured outbound messages, transform payloads, and coordinate acknowledgements and downstream writes.
Bulk, asynchronous, and batch processingYesPeopleSoft supports asynchronous service operations and message processing, along with application-specific batch processes and extracts for high-volume or scheduled workloads.Martini can schedule bounded retrievals, process asynchronous responses, persist checkpoints, control concurrency, and route failed items for retry or reconciliation.
Webhooks and outbound callbacksLimitedPeopleSoft can send outbound Integration Broker messages or HTTP requests for selected configured service operations, events, or application processes. It does not provide a universal webhook feed for every object or event.Martini can receive configured PeopleSoft outbound requests through an API or webhook workflow, validate the message, retrieve additional data when needed, and apply idempotency controls.
File and batch exchangesLimitedFlat files, XML, CSV, and scheduled batch exchanges are commonly used for payroll, finance, procurement, and legacy PeopleSoft integrations. File behavior depends on the product and implementation.Martini can orchestrate available file exchanges, parse supported formats, validate content, transform structures, and route results to APIs, files, or other systems.
Authentication and authorizationYesPeopleTools security can use users, roles, permission lists, service-operation security, HTTPS/TLS, Basic Authentication, certificates, WS-Security, and configured OAuth or token-based mechanisms where supported.Martini can store credentials and secrets securely, configure supported API authentication, and apply API and workflow security around exposed integration endpoints.
Database accessNot confirmedPeopleSoft runs on supported relational databases, but direct database integration is tightly coupled and can bypass application logic, security, validations, and effective-dating behavior.Martini can connect to databases where appropriately configured, but PeopleSoft REST, SOAP, Integration Broker, or approved file interfaces should generally be evaluated first.

How Oracle PeopleSoft exposes data and business events

Oracle PeopleSoft REST APIs

PeopleSoft can expose and consume REST services through Integration Broker. The available resources, fields, methods, JSON or XML representation, and authorization depend on the PeopleSoft product, PeopleTools release, and configured service definitions.

Martini implementation pattern

Martini implementation pattern: a workflow calls the configured PeopleSoft REST endpoint, handles pagination or incremental criteria, validates the response, maps PeopleSoft data into a canonical model, and writes it to one or more target systems. Martini can also expose a controlled API façade for downstream consumers.

Implementation sequence

Authenticate to the configured PeopleSoft REST endpoint
Retrieve the current page or incremental data set
Validate the response and preserve source identifiers
Map PeopleSoft fields to the canonical model
Apply effective-date and business rules
Write the result to the target system and store the synchronization watermark

Oracle PeopleSoft SOAP APIs

PeopleSoft Integration Broker supports SOAP web services and WSDL-driven synchronous or asynchronous integrations. SOAP is particularly relevant for delivered services and established enterprise interfaces.

Martini implementation pattern

Martini implementation pattern: Martini consumes the PeopleSoft WSDL-based service, constructs the required XML request, handles namespaces and service-operation responses, and routes successful or failed outcomes through a workflow.

Implementation sequence

Load the configured PeopleSoft SOAP service definition
Authenticate and submit the XML request
Parse the SOAP response or asynchronous acknowledgement
Map the response into the target data model
Apply validation and business rules
Retry transport failures and reconcile business failures

Integration Broker messages

Integration Broker provides service operations, messages, queues, routings, handlers, transformations, and gateways for inbound and outbound PeopleSoft integrations. Messages can be synchronous or asynchronous.

Martini implementation pattern

Martini implementation pattern: Martini invokes or receives a configured Integration Broker interaction, distinguishes acceptance from final processing, correlates message identifiers, and coordinates downstream processing and reconciliation.

Implementation sequence

Receive or submit the configured service operation message
Capture the PeopleSoft message or correlation identifier
Parse and validate the XML or JSON payload
Transform the message into the target structure
Track queued, processed, and failed outcomes
Retry safe failures and route unresolved items to reconciliation

Configured outbound notifications

PeopleSoft can initiate outbound Integration Broker messages or HTTP requests for selected configured service operations, events, batch processes, or custom application logic. Coverage is partial rather than universal.

Martini implementation pattern

Martini implementation pattern: Martini exposes an authenticated receiving API or webhook workflow, validates the notification, uses the event as a trigger, and retrieves authoritative PeopleSoft data when the notification is not complete.

Implementation sequence

Receive the configured PeopleSoft outbound request
Authenticate and validate the notification
Check the source message or business key for duplicates
Retrieve authoritative PeopleSoft data when required
Map and route the change to downstream systems
Persist processing status and return the appropriate acknowledgement

File and batch exchanges

PeopleSoft environments commonly use scheduled processes, flat files, XML, CSV, and other batch exchanges for payroll, finance, procurement, and legacy integrations. The exact interface is implementation-specific.

Martini implementation pattern

Martini implementation pattern: a scheduled or event-driven workflow obtains the available file, validates its structure and provenance, transforms each business object, and delivers results to APIs, files, or other endpoints.

Implementation sequence

Detect or retrieve the PeopleSoft-generated file
Validate file format, naming, and completeness
Parse XML, JSON, CSV, or another supported structure
Transform and validate each business object
Deliver accepted data to the target system
Archive processing metadata and route rejected rows for review

Common Oracle PeopleSoft integration patterns

Pattern 1: Synchronize PeopleSoft employees to workforce applications

When to use this pattern

Use this pattern when PeopleSoft HCM is the source for employee lifecycle, organizational, or identity-related data and downstream systems need current or effective-dated changes.

Integration direction
Oracle PeopleSoft
Martini
ServiceNow
Example Mapping
Oracle PeopleSoft FieldCanonical FieldTarget Field
EMPLIDemployeeIdemployee_number
EFFDTeffectiveDateeffective_date
DEPTIDdepartmentCodedepartment
EMPL_STATUSemploymentStatusactive
Martini implementation pattern

A scheduler or configured outbound message starts a Martini workflow. Martini retrieves Person, Employee, Job, and Position data, selects the required current or future-dated rows, validates mandatory identifiers, maps the workforce model, and performs idempotent create-or-update operations. Failed records are retried when safe and retained for reconciliation with PeopleSoft message identifiers.

Martini capabilities used
  • workflows
  • API consumption
  • scheduling
  • data mapping
  • business rules
  • error handling

Pattern 2: Synchronize PeopleSoft suppliers and purchase orders

When to use this pattern

Use this pattern when PeopleSoft Financials or Supply Chain exchanges procurement data with a finance or enterprise resource planning application.

Integration direction
Oracle PeopleSoft
Martini
NetSuite
Example Mapping
Oracle PeopleSoft FieldCanonical FieldTarget Field
VENDOR_IDsupplierIdvendorId
PO_IDpurchaseOrderIdtranId
BUSINESS_UNITbusinessUnitsubsidiary
PO_LINElineNumberitemLine
Martini implementation pattern

Martini consumes PeopleSoft REST, SOAP, Integration Broker, or file-based data, validates supplier and organizational references, transforms purchase-order headers and lines, and sends the target request. A stable supplier or purchase-order key prevents duplicates, while asynchronous acknowledgements and business errors are tracked separately from transport failures.

Martini capabilities used
  • workflows
  • API consumption
  • XML and JSON transformation
  • data mapping
  • validation
  • retry and reconciliation

Pattern 3: Process configured PeopleSoft employee change notifications

When to use this pattern

Use this pattern when the PeopleSoft implementation has configured outbound messages or HTTP requests for selected employee, job, position, or organizational events.

Integration direction
Oracle PeopleSoft
Martini
Salesforce
Example Mapping
Oracle PeopleSoft FieldCanonical FieldTarget Field
EMPLIDsourcePersonIdExternal_Employee_ID__c
NAMEdisplayNameName
JOB_CODEjobCodeTitle
DEPTIDdepartmentCodeDepartment_Code__c
Martini implementation pattern

Martini exposes an authenticated receiving API, validates the PeopleSoft notification, checks its message or business key for duplicate delivery, and retrieves authoritative details if the notification is only a trigger. Business rules determine whether to create, update, or ignore the target record. Failed downstream calls are retried with controlled backoff.

Martini capabilities used
  • API exposure
  • webhook consumption
  • workflows
  • data mapping
  • business rules
  • idempotency
  • error handling

Pattern 4: Exchange PeopleSoft financial files

When to use this pattern

Use this pattern when a PeopleSoft batch process produces General Ledger Journal, payroll, or other finance files instead of exposing the required data through a real-time API.

Integration direction
Oracle PeopleSoft
Martini
SAP S/4HANA
Example Mapping
Oracle PeopleSoft FieldCanonical FieldTarget Field
JOURNAL_IDjournalIdDocumentReference
BUSINESS_UNITbusinessUnitCompanyCode
ACCOUNTaccountCodeGLAccount
MONETARY_AMOUNTamountAmount
Martini implementation pattern

A scheduled Martini workflow retrieves the file through the available exchange endpoint, validates completeness and control totals, parses the supported format, maps journal headers and lines, and submits accepted data to the target. Processing metadata, source identifiers, rejected rows, and delivery status are retained for reconciliation.

Martini capabilities used
  • scheduling
  • file processing
  • XML and JSON handling
  • data mapping
  • validation
  • workflows
  • monitoring

Applications commonly integrated with Oracle PeopleSoft

Oracle PeopleSoft commonly participates in multi-application enterprise landscapes. The exact objects, direction, and interface method depend on the PeopleSoft product family, PeopleTools release, delivered service definitions, and customer configuration.

Application Scenario Direction Martini Pattern
Salesforce Synchronize PeopleSoft-managed person, employee, account, or organizational information with customer and business-process data in Salesforce. Oracle PeopleSoft → Martini → Salesforce Martini retrieves or receives selected Person, Employee, and organizational changes, normalizes effective-dated fields, applies routing rules, and performs Salesforce create-or-update operations with source-key-based reconciliation.
ServiceNow Create or update users, departments, onboarding tasks, and offboarding tasks from PeopleSoft HCM changes. Oracle PeopleSoft → Martini → ServiceNow A scheduled query or configured PeopleSoft outbound message starts a Martini workflow that validates Employee, Job, and Department data before calling ServiceNow APIs and recording target identifiers and processing status.
Workday Exchange workforce, organization, payroll, or historical HR information when PeopleSoft and Workday coexist or support a phased migration. Oracle PeopleSoft → Martini → Workday Martini orchestrates scheduled extracts or API calls in either direction, maps the two HR models, handles effective dates, and routes exceptions to reconciliation workflows.
SAP S/4HANA Exchange suppliers, purchase orders, financial data, and organizational information between PeopleSoft and SAP environments. Oracle PeopleSoft → Martini → SAP S/4HANA Martini consumes PeopleSoft REST, SOAP, or Integration Broker messages, transforms procurement and finance structures, invokes SAP interfaces, and uses business keys to make retries idempotent.
NetSuite Synchronize suppliers, purchase orders, invoices, journals, and financial reference data across enterprise finance processes. Oracle PeopleSoft → Martini → NetSuite A Martini workflow validates Supplier, Purchase Order, and General Ledger Journal data, maps line-level structures, applies accounting rules, and sends status or error outcomes back to the source process.
Oracle HCM Cloud Exchange workforce or organizational data during coexistence, phased migration, or hybrid Oracle application deployments. Oracle PeopleSoft → Martini → Oracle HCM Cloud Martini coordinates incremental PeopleSoft extracts and Oracle HCM Cloud API calls, applies effective-dated mapping rules, and preserves source identifiers for migration or ongoing synchronization.
Oracle E-Business Suite Coordinate finance, procurement, supplier, and HR-related information between PeopleSoft and another Oracle enterprise application. Oracle PeopleSoft → Martini → Oracle E-Business Suite Martini mediates REST, SOAP, file, or configured messaging interfaces, transforms application-specific payloads into canonical structures, and manages asynchronous acknowledgements and reconciliation.
ADP Exchange employee, payroll, benefits, or workforce data where PeopleSoft HCM and ADP both participate in HR or payroll operations. Oracle PeopleSoft → Martini → ADP Martini processes scheduled files, API responses, or configured outbound messages, validates employee identifiers and effective dates, and routes payroll or workforce exceptions for review.

How to build a Oracle PeopleSoft integration in Martini

Objective

Establish the PeopleSoft interface and authentication model using the actual REST resource, WSDL, Integration Broker service operation, outbound endpoint, or file exchange provisioned by the PeopleSoft administrator.

Instructions in Martini

  • Confirm the PeopleTools and application release and obtain the interface definition
  • Configure the PeopleSoft user, role, permission list, service-operation access, gateway, and endpoint security
  • Store credentials, tokens, or certificates in Martini secrets and configure HTTPS/TLS

Objective

Select a trigger that matches the PeopleSoft integration design and the required freshness of the data.

Instructions in Martini

  • Use a REST or SOAP request for API-led processing
  • Use a configured outbound PeopleSoft message or HTTP request for selected events
  • Use a scheduler for incremental queries, batch processes, or file exchanges

Objective

Obtain the authoritative PeopleSoft payload while accounting for asynchronous processing, pagination, effective dates, and configured message semantics.

Instructions in Martini

  • Receive and authenticate outbound notifications
  • Call the PeopleSoft endpoint with bounded pages or incremental criteria
  • Capture source business keys, message identifiers, timestamps, and watermarks

Objective

Coordinate PeopleSoft calls, enrichment, validation, target operations, acknowledgements, and exception paths in a maintainable Martini workflow.

Instructions in Martini

  • Separate transport acceptance from asynchronous business completion
  • Use conditional routing for HCM, procurement, finance, and file-based flows
  • Persist checkpoints and correlation identifiers for safe resumption

Objective

Convert PeopleSoft XML, JSON, file, and effective-dated structures into a canonical model or target-specific payload.

Instructions in Martini

  • Map repeating groups, namespaces, line items, identifiers, and effective dates explicitly
  • Validate required fields and reference data before target writes
  • Preserve PeopleSoft source identifiers for reconciliation

Objective

Apply implementation-specific rules for current, historical, and future-dated records, population routing, duplicate handling, and transaction status.

Instructions in Martini

  • Choose whether the workflow processes current rows, all changes, or future-dated changes
  • Use stable business keys or message identifiers for idempotency
  • Distinguish accepted, queued, processed, committed, and business-error outcomes

Common Oracle PeopleSoft data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
PersonIdentity and workforce or student-related information, depending on the PeopleSoft product.Salesforce, ServiceNow, Workday, Oracle HCM Cloud, ADPMartini maps identifiers and personal attributes, applies privacy and validation rules, and preserves effective-date and source-key information.
EmployeeEmployee profile, employment status, onboarding, leave, termination, payroll, and workforce synchronization.ServiceNow, Workday, Oracle HCM Cloud, ADPMartini retrieves or receives changes through REST, SOAP, Integration Broker, or files and applies create-or-update and lifecycle routing rules.
JobEmployment status, organizational assignment, compensation-related fields, and effective-dated job changes.ServiceNow, Salesforce, Workday, Oracle HCM CloudMartini explicitly handles current, historical, and future-dated rows and maps job changes to downstream lifecycle actions.
PositionPosition descriptions, reporting relationships, and organizational assignments.ServiceNow, Workday, Oracle HCM Cloud, SalesforceMartini transforms hierarchical and effective-dated structures and validates organizational references before delivery.
DepartmentOrganizational departments and associated business-unit structures.ServiceNow, Salesforce, Workday, SAP S/4HANAMartini synchronizes department keys and descriptions, applies reference-data rules, and records target identifiers for reconciliation.
Purchase OrderPurchasing documents and line-level procurement information in PeopleSoft Financials and Supply Chain.SAP S/4HANA, NetSuite, Coupa, data warehousesMartini maps headers, lines, suppliers, amounts, and statuses, validates required fields, and handles asynchronous acknowledgements.

Authentication and security considerations

PeopleTools security and endpoint authentication

PeopleSoft access is controlled through user profiles, roles, permission lists, service-operation security, routing and node permissions, and gateway configuration. Martini should use the least-privileged PeopleSoft account required for the integration.

Transport and message protection

REST, SOAP, and Integration Broker traffic should use HTTPS/TLS. Depending on the release and configuration, authentication may include Basic Authentication, OAuth or tokens, client certificates, mutual TLS, and WS-Security for applicable SOAP services.

Martini security controls

  • Store credentials, tokens, and certificates as environment-managed secrets.
  • Restrict exposed Martini APIs with appropriate authentication and authorization.
  • Confirm PeopleSoft permissions separately from successful network authentication.
  • Protect logs and payloads containing employee, payroll, supplier, or financial information.

Operational considerations for Oracle PeopleSoft integrations

Effective dating and pagination

PeopleSoft frequently uses effective-dated records. Define whether the workflow processes current, historical, or future-dated rows, and persist a stable synchronization watermark when retrieving incremental data.

Throughput and asynchronous processing

Use bounded page sizes, controlled concurrency, scheduled windows, and asynchronous service operations where appropriate. Distinguish an accepted or queued message from a completed business transaction.

Idempotency and retries

Use Person, Employee, Supplier, Purchase Order, Journal, or Integration Broker message identifiers as business keys where appropriate. Retry transient failures with controlled backoff and send unresolved items to reconciliation rather than repeatedly polling PeopleSoft.

Schema and customization changes

PeopleTools releases, delivered services, custom fields, application classes, namespaces, permissions, and service definitions can change interface behavior. Capture WSDLs, REST definitions, and message structures under change control and test in a non-production environment.

Monitoring and reconciliation

  • Record source keys, message identifiers, request timestamps, HTTP status, response payloads, retry counts, and target identifiers.
  • Monitor both Martini workflow outcomes and PeopleSoft Integration Broker processing status.
  • Use reconciliation workflows for asynchronous business errors, rejected rows, and partial file processing.

Why use Martini instead of scripts or point-to-point integrations?

Orchestration across PeopleSoft interfaces

PeopleSoft landscapes often combine REST, SOAP, Integration Broker messages, outbound requests, batch processes, and files. Martini provides a workflow layer that coordinates these mechanisms without forcing every downstream application to understand PeopleSoft-specific protocols.

Reusable transformation and business logic

Martini centralizes mappings for effective-dated records, XML namespaces, repeating groups, procurement lines, and financial structures. Reusable workflows and APIs reduce duplicated logic across point-to-point integrations.

Operational resilience

Martini can apply validation, controlled retries, idempotency, checkpointing, asynchronous routing, monitoring, and reconciliation. This is more maintainable than isolated scripts that handle transport, transformation, and error recovery inconsistently.

Controlled API access

Martini can expose a governed API façade around selected PeopleSoft services, allowing downstream systems to consume canonical responses while PeopleSoft-specific authentication, mappings, and business rules remain centrally managed.

Frequently asked questions

How can Oracle PeopleSoft be integrated with enterprise systems?

Oracle PeopleSoft can integrate through PeopleTools Integration Broker, REST services, SOAP and WSDL-based services, synchronous or asynchronous messages, configured outbound requests, and file or batch exchanges. The appropriate interface depends on the PeopleSoft product, PeopleTools release, delivered services, and customer configuration.

Can Martini integrate with Oracle PeopleSoft?

Yes. Martini can integrate with Oracle PeopleSoft by consuming configured REST or SOAP services, orchestrating Integration Broker interactions, receiving configured outbound HTTP requests, and processing supported file exchanges. A dedicated PeopleSoft-specific Martini connector is not required for these standards-based patterns.

Do I need a connector to integrate Oracle PeopleSoft with Martini?

No. A dedicated Oracle PeopleSoft connector is not required. Martini can use PeopleSoft's confirmed native integration mechanisms, including REST, SOAP, Integration Broker messages, configured outbound requests, authentication methods, and supported file exchanges.

Is there any extra Lonti cost to integrate Oracle PeopleSoft with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Oracle PeopleSoft. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Oracle, infrastructure, database hosting, or other third-party systems depending on subscriptions, usage, and deployment choices.

Which Oracle PeopleSoft integration methods should be used?

REST is generally suitable when an appropriate configured resource is available for a modern API-led integration. SOAP remains relevant for delivered or existing WSDL-based services, while Integration Broker messaging is central to many PeopleSoft enterprise interfaces. Batch and file exchanges remain useful for high-volume payroll, finance, procurement, and legacy processes.

Can Oracle PeopleSoft send events or webhooks to Martini?

PeopleSoft can send configured outbound Integration Broker messages or HTTP requests for selected service operations, events, batch processes, or custom application logic. This is partial and configuration-dependent, not a universal webhook stream for every Person, Employee, Job, Purchase Order, or Journal change.

How does synchronization with Oracle PeopleSoft handle effective dates and duplicates?

A synchronization design should define whether it processes current, historical, or future-dated rows and should use a stable watermark such as a last-update timestamp, effective date, sequence, message identifier, or approved extract marker. Business keys or source message identifiers should support idempotent create-or-update behavior and safe retries.

Can Martini expose an API façade for Oracle PeopleSoft data?

Yes. Martini can expose a controlled REST API that retrieves, transforms, validates, and presents selected PeopleSoft data to downstream consumers. The façade can centralize authentication, canonical mapping, business rules, error handling, and access to PeopleSoft REST, SOAP, or Integration Broker services.

Related Martini documentation

APIs

Workflows

Data

Security

Operations

Connect Oracle PeopleSoft with the systems that depend on it

Use Martini to orchestrate Oracle PeopleSoft APIs, Integration Broker messages, outbound notifications, and file exchanges through maintainable workflows with secure configuration, reusable mappings, validation, and operational monitoring.

EXPLORE MARTINI
BOOK A DEMO