Issue: If you are using the multipart/mixed option with XML Schema or XML Sample as your payload format in the REST Adapter and view the Request/Response pages in the Adapter Endpoint Configuration Wizard in edit or view mode, JSON Sample is shown as selected. Re-upload your sample payload.

Workaround: None. Despite JSON Sample appearing, this doesn't affect runtime and your XML payload is parsed correctly for mapping.

Issue: When a private endpoint is enabled for an Oracle ERP Cloud Adapter, Oracle HCM Cloud Adapter, or Oracle CX Sales and B2B Service Adapter connection, creation of the endpoint during design time may fail for certain SOAP business objects.

Workaround: None.

Note the following issues when using the Oracle HCM Cloud Adapter ZIP file feature:

Workaround: None.

When using the Oracle E-Business Suite Adapter in an integration, you may encounter the following issues:

• Issue: Trading partner setup form does not accept a password with special characters

  The Trading Partner Setup form does not accept a password with special characters. Therefore, the Oracle Integration password should be a combination of text and numbers.

  Workaround: To resolve this issue, apply the following patches to enable Oracle XML Gateway to accept passwords with special characters:

  • For Oracle E-Business Suite Release 12.2, apply Patch 27752692:R12.ECX.C.
  • For Oracle E-Business Suite Release 12.1.3, apply Patch 28310667:R12.ECX.B.

• Issue: Service invocation fails for certain PL/SQL APIs with table type input parameters

  When invoking certain PL/SQL APIs having table type input parameters, the following exception may occur:

  java.sql.SQLException: ORA-06531: Reference to uninitialized collection ORA-06512 

  Workaround: To resolve the exception, pass an empty element in the request corresponding to the table type in the API. For example, when invoking the PROCESS_BOM API with table type parameters P_BOM_REVISION_TBL, P_BOM_REF_DESIGNATOR_TBL, and P_BOM_SUB_COMPONENT_TBL, pass the empty tags as a workaround:

  1. Export the integration with the mappings for the Oracle E-Business Suite request.

  2. Locate the corresponding .xsl file to change the mapping entries for P_BOM_REVISION_TBL, P_BOM_REF_DESIGNATOR_TBL, and P_BOM_SUB_COMPONENT_TBL as follows:

     <P_BOM_REVISION_TBL/>
     <P_BOM_REF_DESIGNATOR_TBL/> 
     <P_BOM_SUB_COMPONENT_TBL/>

  3. Import this modified mapping for the request mapping.

  4. Activate the integration and the API should be invoked successfully.

If your Oracle Integration instance tenancy was migrated from Oracle Identity Cloud Service to an identity domain, you can receive errors when using the OCI Object storage and OCI Function actions or using a terraform script-generated service instance. These issues don’t impact tenancies that were always enabled for identity domains.

Issue: If you attempt to drag a connection into an integration when using the Chrome browser on Windows 10, the connection is not added. If you use Internet Explorer, a forbidden icon is displayed.

Workaround: If you disable support for the touch screen and restart the browser, this issue goes away.

Issue: After phased upgrade of Process from Oracle Integration Generation 2 to Oracle Integration 3, dynamic process calls using the integrations activity will not work. Oracle Integration Generation 2 Process does not show any error and erroneously indicates that the integration call is successful although it is not successful.

Workaround: You can reconfigure these calls to use the Service Task (calling the REST trigger on Oracle Integration 3).

Issue: If there are any dynamic processes calling integrations using Generic Credentials as security, it will result in failures at runtime.

Workaround: None.