on 03-08-2022 2:29 PM
Hi Experts,
We have a requirement for ECC Proxy -> CPI -> Tax Agency Webservice
Now, the Webservice WSDL has reference to external XSDs
As I understand for the setup to work
1. We need to import the WSDL file in Sender SOAP Channel in CPI and deploy the IFlow
2. Download the deployed IFlow WSDL file on Manage Integration Content (containing CPI details)
3. Create Service Consumer in ECC based on this WSDL file
4. Configure SOAManager with CPI endpoint and credentials
Unfortunately, ECC needs the XSD fields included on the WSDL file when creating the service consumer.
Is #1 a hard-requirement for this setup or can we just skip it and download the generic WSDL file (without any reference to Tax Agency Webservice) created by CPI and import it on ECC? Then ABAP team can create their own input and output structures for the proxy?
hi
I had similar requirement .your abap team need to call abap proxy that's it.
Thanks
Harshalata
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
77 | |
11 | |
10 | |
8 | |
6 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.