Different Apps Adapters Generate The Same Object Types With Different Bodies
(Doc ID 436703.1)
Last updated on MARCH 30, 2019
Applies to:Oracle(R) BPEL Process Manager 10g - Version 10.1.3.1 and later
Information in this document applies to any platform.
Each Oracle Applications adapter within a BPEL process creates a wrapper PL/SQL package and some
SQL statements. These statements are executed against the Apps schema the adapter connects to. One
of the SQL statements creates a TYPE which is accessed by the PL/SQL package. The TYPE is created
with a specific name. If there are multiple Apps adapters withing a single BPEL process, there are
therefore multiple TYPES created, but these types all have the same name, although they access
different PL/SQL procedures and functions in the database and have different structures. This
leads to a conflict, as the TYPEs overwrite each other when being created. Because the TYPEs are
invalid, the Apps adapters can't be used.
The expected behaviour is that different TYPEs are created with different names to prevent conflict.
Steps To Reproduce
The issue can be reproduced at will with the following steps:
- Create a BPEL process with two or more Oracle Applications adapters
- Using the adapters' wizards, access two separate PL/SQL APIs in the APPS schema
- Complete the wizard steps to produce two .sql files for each adapter
- Compare the .sql files and verify that two separate adapters contain different CREATE OR
REPLACE TYPE statements, but with the same name.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document