PeopleSoft runs finance, HR and supply-chain modules in many large estates. Lima reads its PS_ tables over JDBC in partitions, picks up changes by the last-update fields, and writes back through Integration Broker service operations so PeopleSoft applies its own validation.
Each method has a job. The first load uses the bulk method; the daily run uses the incremental or change-capture method; write-back uses the interface the system itself uses.
| Method | What it does | When it is used |
|---|---|---|
| Partitioned JDBC reads | Reads PS_ record tables in parallel slices. | First loads and history. |
| Incremental reads by last-update fields | Reads changed rows. | Deltas. |
| Integration Broker services | Calls service operations (REST or SOAP) that create or update transactions. | Write-back. |
The objects are the tables, views or records Lima reaches through the methods above. The patterns say how a copy is made and kept current.
| Object | Plain meaning |
|---|---|
| PS_MASTER_ITEM_TBL · PS_BU_ITEMS_INV | items and business-unit items |
| PS_PO_HDR · PS_PO_LINE · PS_PO_LINE_SHIP | purchase orders |
| PS_PHYSICAL_INV · PS_BU_ITEMS_INV | inventory balances |
| PS_VENDOR · PS_CUSTOMER | suppliers and customers |
| PS_LEDGER · PS_JRNL_LN | general ledger |
| Pattern | Supported |
|---|---|
| Full load | Yes |
| Incremental | Yes |
| Change capture | by last-update fields |
| Streaming | — |
| Write-back | Integration Broker; response is the confirmation |
A planning dataset is assembled from these objects. The pair pages show how each planning application shapes them.
| Planning object | Source objects in Oracle PeopleSoft |
|---|---|
| Items | PS_MASTER_ITEM_TBL · PS_BU_ITEMS_INV |
| Bills of material | PS_EN_BOM_COMPS |
| Routings | PS_EN_RTG_OPER |
| Stock | PS_BU_ITEMS_INV · PS_PHYSICAL_INV |
| Open purchase orders | PS_PO_HDR · PS_PO_LINE · PS_PO_LINE_SHIP |
| Open sales orders | PS_ORD_HEADER · PS_ORD_LINE |
| Production | PS_SF_PRDNID_HEADR |
| Forecasts | PS_DP_FCST |
| Customers and suppliers | PS_CUSTOMER · PS_VENDOR |
| Calendars | PS_CAL_DETP_TBL |
The prerequisites are what the team that runs Oracle PeopleSoft grants. The four steps are the same for every connector.
Incoming data = valid records + exception records. A row that fails a check is kept, routed to the person who owns it with a deadline, and replayed once fixed. The load carries on with the valid rows and the report says exactly what was held back. How exceptions work →
Each pair page covers one path end to end: objects out, model in, checks, cadence and the offer.
Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →Landing and history: full history landed with a count check per table, then kept current.
Open the pair page →3 more pair pages for Oracle PeopleSoft are listed in the directory.
Lima connects from outside through the interfaces listed above with credentials your administrators grant. Where a vendor requires its own agent or add-on for a method, the prerequisites say so.
Parallel reads are capped and the cap is agreed with the team that runs the system. Large reads run inside an agreed run window. Change capture keeps the daily volume small.
A report per run: rows in, rows out, control totals and variance per table, the exceptions held back and who owns them, and whether the deadline was met.
Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.
A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.
