All learning series · Connector · Part 1
Connector for Oracle Applications
Learn both sides of the Manage and Oracle business-data exchange.
Start here
Confirm this product is ready, then use the lesson. The readiness checks are the gate for configuration, for a first journey and for production.
- Are you ready to use Connector for Oracle Applications? Licensing and AppPoints, the records that must exist, and three checklists.
- Basics
- Configuration
- Practical example
- Practice and verify
- Advanced concepts
Are you ready to use Connector for Oracle Applications?
Connector for Oracle Applications moves agreed documents between Maximo Manage and Oracle E-Business Suite. Both sides need their own licence, a working endpoint, and a decision about which system owns each record.
Before configuration
Have the connector install entitlement, a Oracle E-Business Suite environment you are allowed to use, and a matrix that says who creates each document.
Before the first successful journey
One document type, the keys both systems share, and a person or integration identity that may send it.
Before production use
Owners on both sides, a schedule, and a way to tell a refused document from a down endpoint. A schema loaded in Manage is not a completed transaction.
Licensing, entitlement and AppPoints
Connector for Oracle Applications is a Maximo Manage integration. The MAS 9.2 licensing guidance prices this connector per installation at 80 AppPoints. That quantity is the connector install, reserved for the life of the environment. It is not a per-user charge, and it does not buy the external system. People who create or update a record whose source of truth is Maximo still need a Maximo user entitlement, including when they do it through another application. When Oracle E-Business Suite is the source of truth and it only replicates data into Maximo, the guidance says that replication does not by itself require a Maximo end-user licence. The connector install is still required. Oracle E-Business Suite is licensed by its own agreement.
Keep four facts separate for Connector for Oracle Applications. Entitlement is the proof of entitlement and the License Information for IBM Maximo Application Suite. The MAS 9.2 licensing guidance supplements that agreement. Available AppPoints are the pool shown on the AppPoints Usage dashboard: Suite administration, then Suite, then Administration, then AppPoints Usage. Assigned access is the security group together with the user type on the person: Limited, Base or Premium, and Authorized or Concurrent. Consumption is what that assignment draws. Authorized users and administrators reserve AppPoints continuously. Concurrent users draw AppPoints while they are signed in. Install AppPoints stay reserved for the life of that environment. A non-production install of a component draws no install AppPoints when the same component is already installed in production. Administrators and User Management users open the dashboard. Other people need the LICENSEUSAGE security group. Compliance enforcement and idle timeout sit on the dashboard Configuration tab and are suite-administrator settings.
The same guidance publishes these user conversion ratios: Limited is 5 AppPoints for one concurrent user and 2 for one authorized user; Base is 10 concurrent and 3 authorized; Premium is 15 concurrent and 5 authorized; an administrative Base user is 10 AppPoints and an administrative Premium user is 15, both as authorized users. A Base administrator who already reserves 10 AppPoints can be given Premium application access with no further AppPoints. Those ratios were read from the MAS 9.2 licensing guidance on 18 October 2026. Your agreement sets how many AppPoints you purchased. An application that opens shows that the component is deployed. Read the proof of entitlement and the dashboard as well.
Installed and enabled applications
Confirm the connector component is deployed and its version is recorded. Confirm the external endpoint answers. Installed means the connector is on the Manage workspace. Configured means the endpoint, the credentials and the object mapping exist. Usable means one document leaves one system and is read back in the other.
Foundation configuration
Manage needs the organization, the site and the reference data the document uses: operating unit, vendor, item, unit of measure and currency. Oracle E-Business Suite needs the matching company, site or master record. Currencies, units and statuses have to be mapped before the first document. Work orders, items or people that the document mentions must already exist on the side that does not own them, or the interface must be allowed to create them.
Product configuration
Set the endpoint, the queue or the channel, and the mapping for this flow: One Oracle purchasing or inventory flow from the connector’s documented set, with the owner system named. Decide the direction. Grant the integration identity the object structures it writes, and keep that identity off interactive administrator groups. Review defaults that create records in Maximo when the external system should have been the master.
Infrastructure and integration
The workspace needs a route to Oracle E-Business Suite: DNS, TLS, proxy or firewall, and the authentication that system expects. Queues and scheduled jobs need a window. Capacity is whatever your agreement and the external system’s limits say. Do not copy another connector’s throughput into this one.
Data and operational readiness
The first journey is one document of the agreed type, created in the owning system, delivered once, and read back in the other system with the same key. A second send of the same document should not create a duplicate. A missing master record is data. A refused login is the identity. A timeout is the path. A document that never leaves Manage is configuration or the queue.
Setup order for Connector for Oracle Applications
- 1. Connector install and the external licence 80 install AppPoints, plus the Oracle E-Business Suite agreement.
- 2. Who owns the document Maximo or the external system. The licence for end users follows that choice.
- 3. Keys, currency, units, statuses operating unit, vendor, item, unit of measure and currency
- 4. Endpoint, identity and one document Read it back on the other side. Send it once more and keep a single record.
| Requirement | Why needed | Mandatory/Conditional/Optional | Where to configure or verify | Minimum working example | Verification procedure | Consequence if missing | Remediation | Source |
|---|---|---|---|---|---|---|---|---|
| Connector install at 80 AppPoints | The guidance prices the connector per installation. Users are a separate question. | Mandatory | Suite administration → Suite → Administration → AppPoints Usage, install line. Proof of entitlement. | One install drawing 80 AppPoints. A non-production install draws none when production already has this connector. | Match the dashboard install line to the guidance, then open the external system with its own administrator. | The component is deployed and the install line shows a different product’s quantity. | Apply this connector’s published install quantity. Do not reuse another connector’s number. | Licensing in Maximo Application Suite 9.2 |
| Oracle E-Business Suite licence and a system you may call | The connector does not include the external application. | Mandatory | The Oracle E-Business Suite agreement and a non-production tenant or client. | A training company in Oracle E-Business Suite that your integration identity can update. | Sign in to Oracle E-Business Suite with that identity and open the document type. | Manage is ready and the external side refuses the identity. | Complete the Oracle E-Business Suite access before the first send. | Licensing in Maximo Application Suite 9.2 |
| A written owner for the document | End-user Maximo entitlement follows whether Maximo is the source of truth. | Mandatory | The integration design, and the user tier of anyone who updates Maximo-owned records from outside. | One Oracle purchasing or inventory flow from the connector’s documented set, with the owner system named | For one document, name the owning system. If Maximo owns it, the external user who edits it has a Maximo tier. | External users update Maximo-owned work with no Maximo entitlement. | License those users or move ownership to the external system and only replicate in. | Licensing in Maximo Application Suite 9.2 |
| Shared keys, currency, units and statuses | The document has to land on the same master data. | Mandatory | Manage organization, site and reference data. The matching setup in Oracle E-Business Suite. | operating unit, vendor, item, unit of measure and currency | Create the keys on both sides and compare one code. | The document fails on an unknown vendor, unit or status. | Load the reference data before the transaction. | Modules and applications in Maximo Application Suite 9.2 |
| Endpoint, credentials and object-structure access | The integration identity is not an interactive administrator. | Mandatory | The connector endpoint configuration. Manage → Security → Security Groups. Object-structure authorisation. | One integration user that can write only the objects in this flow. | Send a test document and confirm a person without that access is refused. | The channel runs as a super user, or the send is refused. | Narrow the identity to the object structures. Grant the missing structure if the send is the one you intend. | User access and entitlements in MAS 9.1 and later |
| One document read back on the other side | A loaded schema or a successful login is not a transaction. | Mandatory | The One Oracle purchasing or inventory flow from the connector’s documented set, with the owner system named path, then a query in the receiving system. | One training document, one key, visible in both systems. | Query by that key in the receiver. Send the same document again and confirm you still have one record. | The send reports success and the receiver has no document, or it has two. | Fix delivery before production, and make the second send update the same key. | Modules and applications in Maximo Application Suite 9.2 |
| A path and a window | DNS, TLS and the external system’s maintenance window decide whether the job can run. | Mandatory | The route from the workspace to the external host, and the schedule of the channel. | The host name, port and certificate the connector uses, and a window when both systems are up. | Open the endpoint from the workspace network and complete one send inside the window. | A laptop can reach the host and the workspace cannot, or the job runs during the external outage. | Open the workspace path and move the schedule. | Licensing in Maximo Application Suite 9.2 |
A. Ready to configure
- The 80-AppPoint install is on the proof of entitlement and on the dashboard.
- Oracle E-Business Suite access exists for a training company.
- The document owner is written down.
- The integration identity is created and is not a shared administrator.
B. Ready for the first end-to-end journey
- Reference keys exist on both sides.
- One document is created in the owning system.
- The receiver shows the same key.
- A second send updates that record rather than adding another.
- A user without the object structure is refused.
C. Ready for production operation
- Both systems have an owner and a support path.
- The schedule avoids the external maintenance window.
- Maximo end-user entitlement matches the ownership matrix.
- Failures are split into bad data, a refused identity, and an endpoint that did not answer.
- Production credentials replace the training identity.
Sources for this readiness check
Licence statements come from the IBM topic named on the row. Installation of a component is a separate check from entitlement.
- Licensing in Maximo Application Suite 9.2 — MAS 9.2 licensing guidance, verified 2026-10-18
- User access and entitlements in MAS 9.1 and later — MAS 9.1 and later, verified 2026-10-18
- Accessing the AppPoints Usage Dashboard — MAS 9.2, verified 2026-10-18
- Modules and applications in Maximo Application Suite 9.2 — MAS 9.2, verified 2026-10-18
Before you start
MAS learning path. Match the component documentation to your installed release and maintenance build before configuring it.
- A supported Oracle Applications/Manage combination and training connector deployment.
- Test supplier, item, organization and financial mappings.
IBM sources + Assetize exercise
01 · Basics — Understand the building blocks
IBM documents configuration on both the Manage server and the Oracle Applications server after connector deployment. A working endpoint on one side is therefore only part of the setup.
Reference data, operating organizations and financial context must agree before transaction testing is meaningful.
Topics in this series
- Connector architecture
- Reference data ownership
- Organization mapping
- Transaction processing
- Recovery and reconciliation
02 · Configuration — Work through the setup
Use a training environment and match the actions to the IBM guide for your installed build.
- Select an integration flow from the connector documentation and establish its owner system.
- Inspect its required configuration in both Manage and Oracle Applications.
- Map a small supplier/item population and reconcile external identifiers.
- Execute one supported purchasing or financial training transaction and inspect business acceptance.
- Create an invalid mapping case, correct it through the supported process and retry with the same business identity.
03 · Practical example
Fictional teaching example
A fictional item identifier is valid in one Oracle inventory organization but not another. The training exercise demonstrates why the organization mapping must accompany the item key.
04 · Practice and verify
Document the same transaction in both systems with keys, organization, quantity, amount and acceptance result.
Expected result
The accepted business record matches the source, and the invalid organization case produces a visible, recoverable error.
Common mistakes
- Configuring only the Maximo side.
- Treating a supplier name as a stable integration key.
05 · Advanced concepts
Expand into reference-data changes, reversals and restart/replay. Keep the reconciliation population tied to the selected integration flow.
IBM references
Product explanations link to IBM sources. Scenarios and exercises are original Assetize teaching material. Reviewed 2026-10-01.
Maximo ecosystem overview · Manage learning paths · Practice data in Workbench