The connector. Hidden licence exposure.

The custom application connector to Oracle E-Business Suite is one of the most misunderstood sources of EBS licensing exposure. The connection between a custom application and the EBS technology stack can trigger a licence requirement the buyer never anticipated.

EBS custom application connector pricing concerns the licensing exposure created when a custom application connects to Oracle E-Business Suite or the underlying technology stack. The connection through the Application Object Library, the database, or the application server can trigger a full use licence requirement, with the custom application exposing the organisation to a licence cost that was never anticipated when the connector was built. Understanding the connector exposure is central to the EBS negotiating position.

This article walks through the EBS connector framework. The connector exposure and how the custom application triggers the licence requirement. The Application Object Library licensing and the technology stack dependency. The full use versus the restricted use distinction. The deployment analysis that establishes the genuine exposure. The negotiation approach that resolves the exposure on the buyer side terms. The framework applies to organisations running custom applications against the EBS environment.

The connector exposure.

The connector exposure arises when a custom application connects to the EBS environment or the underlying technology stack. The connection accesses the EBS data, the Application Object Library, or the embedded database, with the access potentially triggering a licence requirement for the technology stack components. The connector exposure is often invisible until the audit, when Oracle identifies the custom application and asserts the licence requirement.

The connector exposure depends on the nature of the connection. The read only connection through a supported interface carries a different exposure than the direct database access through a custom integration. The exposure assessment depends on the specific connection method, the components accessed, and the licensing terms that govern the access. The accurate assessment of the connection is the foundation for the buyer side position on the genuine exposure.

The structural response is the careful assessment of the connector exposure. The connection method and the accessed components should be mapped against the licensing terms, with the assessment establishing the genuine exposure rather than the over stated exposure Oracle would assert. See the EBS negotiation pillar and the Oracle Database product page.

The Application Object Library licensing.

The Application Object Library is the technology foundation of the EBS environment, providing the security, the workflow, and the data access services. The custom application that uses the Application Object Library services accesses the EBS technology stack, with the access potentially triggering a licence requirement. The Application Object Library licensing is central to the connector exposure assessment.

The Application Object Library dependency creates the licensing question. The custom application that relies on the Application Object Library for the authentication, the data access, or the workflow accesses the EBS technology, with Oracle asserting that the access requires the EBS application user licence. The assessment depends on the specific Application Object Library services used and the licensing terms that govern the access.

The structural response is the assessment of the Application Object Library dependency. The custom application use of the Application Object Library services should be mapped against the licensing terms, with the assessment establishing the genuine requirement. See the EBS renewal negotiation article and our contract review service.

The full use versus restricted use.

The full use and the restricted use licences carry different rights and different prices. The full use licence permits the unrestricted use of the EBS application, while the restricted use licence permits only the specific use defined in the licensing terms. The custom application connector may require the full use licence or the restricted use licence, depending on the nature of the access and the licensing terms.

The distinction shapes the connector exposure cost. The full use licence requirement carries a materially higher cost than the restricted use licence requirement, with the assessment of the appropriate licence type central to the exposure cost. Oracle tends to assert the full use requirement, with the buyer side analysis establishing whether the restricted use licence is the appropriate fit for the connector use.

The structural response is the assessment of the appropriate licence type for the connector. The connector use should be mapped against the full use and restricted use definitions, with the assessment establishing the appropriate licence type and the genuine cost. See the Apps Unlimited deal type page.

The deployment analysis.

The deployment analysis establishes the genuine connector exposure against the actual deployment. The analysis maps the custom applications, the connection methods, the accessed components, and the user populations, with the measured reality providing the foundation for the buyer side position on the genuine exposure. The deployment analysis distinguishes the genuine exposure from the over stated exposure.

The deployment analysis identifies the connections that genuinely trigger the licence requirement and the connections that do not. The supported interfaces, the read only access, and the restricted use connections may carry a lower exposure than Oracle would assert, with the deployment analysis establishing the genuine requirement against the actual connection methods. The accurate map of the connections is the foundation for the buyer side position.

The structural response is the completion of the deployment analysis before the negotiation. The analysis should map the connections against the licensing terms, with the genuine exposure established before the negotiation reaches the table. See the EBS manufacturing module pricing article and the Oracle Negotiation Playbook white paper.

The negotiation approach.

The negotiation approach resolves the connector exposure on the buyer side terms. The approach establishes the genuine exposure against the deployment analysis, presents the buyer side position on the appropriate licence type, and negotiates the resolution at the appropriate price. The negotiation approach resists the Oracle tendency to assert the maximum exposure and the full use licence requirement.

The negotiation approach draws its leverage from the deployment analysis and the alternative options. The buyer side that can demonstrate the genuine connection methods, the restricted use fit, and the option to re architect the connector holds the leverage to negotiate the resolution at the appropriate price. The well prepared buyer side resolves the connector exposure without accepting the over stated requirement.

The structural response is the prepared negotiation of the connector exposure. The buyer side should present the deployment analysis, the appropriate licence type, and the alternative options, with the resolution negotiated at the appropriate price. See our audit defense service.

Putting it together.

The EBS custom application connector is a hidden source of licensing exposure that often surfaces only in the audit. The connector exposure, the Application Object Library licensing, the full use versus restricted use distinction, the deployment analysis, and the negotiation approach each shape the exposure cost. Buyer side teams that assess the genuine connector exposure before the negotiation resolve the exposure at the appropriate price, while the teams that accept the Oracle assertion pay for the over stated requirement.

For the broader framework see the EBS negotiation pillar.