Clubbing of SOA Instances while Invoking a web service using BIP report
SummaryClubbing at SOA instance instead of creating new instance while calling a external web service from SaaS BIP report as a Webservice type of BIP report.
We have created a report using a web service connection in BIP, an ESS job is created for that report.
When we call the ESS job or schedule the report from BIP (Scheduling), same stage flow id is returned in the SOAP response which leads to clubbing the same instance in SOA instead of creating a new instance.
But it is working as expected when we submit at report level or data model level, it is creating a new instance in SOA with different stage flow id in response.