Customers Integrator Limitations

In the absence of a suitable Oracle web service, we’ve implemented a download solution using a BI Report.

The data downloaded through the BI Report leverages some, but not all, of the access controls used in the Oracle Fusion ERP UI. To ensure only authorized users can access information, administrators manage download access through a profile option.

The download is intended for the following types of users: Users that are restricted by Business Units or Users with Implementer roles.

This download is not designed for users with data access restricted by the VIEW access function security.

All fields are supported except the B2B configuration attributes: B2B Trading Partner Code and the four Enable for XML Invoicing checkboxes (Invoice, Debit Memo, Credit Memo and Chargeback).

If this omission is something which impacts you, could you please consider upvoting the Oracle Enhancement Idea for the Enable for XML Invoicing checkboxes so that Oracle prioritizes adding it to the web services. Link:

https://community.oracle.com/customerconnect/discussion/608517/ability-to-manage-with-soap-the-field-b2b-trading-partner-code-in-the-customer-profile

Late Charges configuration fields are also unsupported.

Updates: Oracle SOAP APIs do not support Account/Site Profile corrections; the API will inherently create a new Profile record instead.

Below is the Oracle Customer Connect thread tracking a complaint about this issue. Please consider adding your name to this thread to help bring it to Oracle’s attention. Link:

https://community.oracle.com/customerconnect/discussion/709980/update-customer-profile-with-soap-api-with-correct-record-instead-of-insert-record

Oracle Web services do not currently support any fields within the Late Charges section nor do they support the core Credit Limits fields (Credit Limit, Order Amount Limit, Credit Currency and Include Credit Check) at the Site Profile level.

DFFs for the Account Profile and Site Profile sections are currently not implemented due to web service issues. More4apps has raised a Service Request (SR) with Oracle Support requesting these shortfalls be addressed. We will monitor the progress of the SR and consider future enhancements in this area should the functionality become available."

Due to the inability to run SQL queries dynamically in the Integrator, we are not able to provide searchable LOVs.

The Integrator’s DFF forms support LOVs for both dependent and independent DFF segments. However, table-based LOVs are currently not supported.

Downloading of values entered against the Site Contact Assignments and Site Contact Responsibilities DFFs is not currently supported, as at Oracle release 26A, due to the relevant Oracle Package failing to retrieve the DFF data.

More4apps will monitor this situation in anticipation of a future fix from Oracle.

Meanwhile, data entered against DFFs in other Sections, e.g. Party Persons DFF, Party Organizations DFF, Party Sites DFF, can be downloaded.

While Global DFFs at Account Profile and Site Profile levels appear to be available in the web service, there are limitations in the support of this functionality. Oracle has indicated that a bug number (Bug 35036501) has been raised regarding this functionality. However, a fix is not currently planned.

Details of the bug number are available from the link below:

Discussion on Oracle Community.

The Integrator has only the Create function available in this section. There is no web service enabled for Updates.

Processing of Attachments is not supported in the Customers Integrator.

Since the Oracle web services do not support geographical address validation, creating/updating addresses using the Customers Integrator will not validate address information against the master geography data.

The ESS Job Validate Geographies of Addresses Against Master Geographies can be submitted in Oracle Fusion to validate the geography elements, e.g. state, city, postal code are valid against the master geography data. This process also stores the Geography Name Referencing information for the address.

This field was implemented at the request of a customer who needed to record a value in the hz_locations.description field which is not usually available in the Oracle UI.

In order to use this Integrator field for that specific purpose, you must first create a custom field on the Customer Address UI form and then create a link between that custom field and the hz_locations.description field.

You can then create, update and download data into that customised field via the Integrator’s Address Description field.