on 09-15-2016 1:13 PM
Hi
I have to do a scenario from ECC -- PI--- SOAP
I have to use two tables in ECC. Those fields put together has six hundred field.
It's a huge effort to create a DT with six undred fields. So I created an RFC at the ECC, with tables A and B. I imported it to PI.
I took the XSD of the imported RFC by creating a dummy mapping.
RFC_AB.xsd I named it
If I edit the namespace and give an existing namespace and a DT_CO_AB and import the news xsd, can I use it to create a proxy.
Also can I use the same xsd to generate a wsdl
is there any other way I can create a proxy structure of six hundred field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manoj
Thanks for your help
I am confused about the namespace. It's pointing to sap. Also the target namespace is specific to to a namespace.
Should I edit them?
More importantly, can I use same XSD for both proxy, Client proxy and server proxy
can I use the same WSDL for sender soap and receive soap
In a different interface I have to do the reverse flow with all fields , soap to ecc
Practically rhe structure i create depends on two interfaces and four message types
Midhun,
if i understand properly your scenario is Proxy--->PI---->SOAP async
where you need to create a data type of around 600 fields , so instead of creating the data type you had a RFC of 600 , so you took the XSD of that RFC and use the same in mapping.
So my suggestion just import the RFC in PI use it as source structure in service interface (outbound).
then in mapping do RFC (source Structure)-->WSDL file (provided by third party)
br,
Manoj
Manoj
I have to pick these six hundred fields from ECC and create a WSDL for those six hundred fields.
Structure is same for both sender and receiver.
If I use RFC as source for Proxy, then I will have to manually create six hundred fields for wsdl..
In receiver side we normally import wsdl but here i have to create wsdl
Midhun,
I sill prefer not to use XSD , just use the RFC in inbound and outbound service interface.
But you providing the WSDL for the third party is not a good idea , because usually the WSDl should contain structure+endpoint URL+operation/soap action which can be only provided by third party.
Better take the XSD of the RFC , and provide the same to third party then and ask them to generate the wsdl using this XSD, this is what i usually do.
Now your doudt that RFC has a sap namespace and you service interface has your custom created namespace ? so you want to modify the rfc xsd and replace sap namespace with custom created namespace ?
No, this isn't required , because i remember i had implemented similar design long back when proxy is triggered you get the namespace of the service interface.
Br,
Manoj
Hello Midhun,
Try using the XSD only,Try importing it in DT.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.