Co-existence of AgileEbiz and MDM PIPs

I would like to put down some findings from R&D on co-existence of Agile-Ebiz and MDM PIP. The environment that we were looking at had an Agile system, an Ebiz R12 with Item and Variant Management modules and Ebiz R11i .

For Agile-Ebiz PIP, Agile will be the source system and Ebiz R12 instance will be the target and for MDM PIP Ebiz R12 will act as the MDM or PIM (source system) and Ebiz R11i the target system.

Task was to see whether the Agile-Ebiz and MDM PIP will co-exist on the same AIA environment. On top of a fresh SOA 10.1.3.4 environment we installed the AIA FP 2.5 and Agile-Ebiz PIP .One round of testing was successful. On this we tried the MDM PIP with Oracle Ebiz R12 and Oracle Ebiz R11i as source and target systems. After that we ran one more round of testing on Agile-Ebiz PIP and some functionality failed. Generate Item number service had failed. So we started analyzing the errors and processes affected due to the co-existence of MDM PIP to zero-in on the affected processes.

In case of Agile for Item sync scenario there is a SyncItemListAgileReqABCSImpl process calling Item EBS and that calls SyncItemListEbizProvABCSImpl which in turn invokes the SyncItemListEbizAdapter and this process will interact with the Ebiz systems. The response is send back by SyncItemListEbizProvABCSImpl through ItemResponseEbiz EBS process where routing will be to SyncItemListAgileReqABCSImpl process.

In case of MDM for Item sync scenario there is a SyncItemListPIMReqABCSImpl process calling SyncItemListEbizProvABCSImpl which in turn invokes the SyncItemListEbizAdapter and this process will interact with the Ebiz systems. The response is send back by SyncItemListEbizProvABCSImpl through ItemResponseEbiz EBS process where routing will be to SyncItemListPIMReqABCSImpl process.

The flows are so similar, but the Requester process differs, so the response will also be routed to the PIP process which was installed later. In our case the since MDM PIP was installed over the Agile-Ebiz PIP, these routing rules are overwritten favoring the PIM systems.

SyncItemListEbizAdapter which interacts with the Ebiz system also was affected since the JNDI name used for Agile-Ebiz PIP was eis/Apps/EbizRA whereas for MDM PIP for Ebiz was eis/Apps/OracleAppsDatasource. Depending on the value it will hit different systems, in our case R12 or R11i.

To conclude it didn’t seem like a recommendable solution to have these 2 PIPs on the same environment. It could be made to work with lot of workarounds but would not make sense as the upgrades to the FP & PIPs will not be clean/easy as you will have to manually upgrade these workarounds.