cancel
Showing results for 
Search instead for 
Did you mean: 

structure input in application service

Former Member
0 Kudos

Hello,

I have created an application service that encapsulates an RFC (BAPI). As long I am using simple types as input parameters in operation and structure in output, everything works fine. But if I'm using structure as input and output parameter, I can't use these operation (after deployment to J2EE).

Can anybody tell me, what the problem is and how I can fix it?

Thank's in advance.

Stefan

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi, Stefan.

BTW, what is your web service client? You're coding with Java?

WD Java?

This information will give other experts to analyze your problem.

Best Regards.

Sejoon

Former Member
0 Kudos

Hi, Stefan.

Yes, if input parameters only have simple types, we are happy

Anyway, did you check your new service via Web Service Navigator

tool of J2EE? If so, you can get right SOAP message, and please

compare that with your program's SOAP message.

Usually, you have to code something to create complex types tags

in your program. For example, the following is SOAP request message

example for BAPI Return(via perl SOAP::Lite module). Even though

BAPI return value is not needed in input parameters, you have to

create tags for meeting the complex types.

-


<RETURN>

<item>

<TYPE xsi:type="xsd:string"/>

<ID xsi:type="xsd:string"/>

<NUMBER xsi:type="xsd:string"/>

<MESSAGE xsi:type="xsd:string"/>

<LOG_NO xsi:type="xsd:string"/>

<LOG_MSG_NO xsi:type="xsd:string"/>

<MESSAGE_V1 xsi:type="xsd:string"/>

<MESSAGE_V2 xsi:type="xsd:string"/>

<MESSAGE_V3 xsi:type="xsd:string"/>

<MESSAGE_V4 xsi:type="xsd:string"/>

<PARAMETER xsi:type="xsd:string"/>

<ROW xsi:type="xsd:string"/>

<FIELD xsi:type="xsd:string"/>

<SYSTEM xsi:type="xsd:string"/>

</item>

</RETURN>

-


Good Luck.

Sejoon