cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

problem converting from JCo to JRA connector

Former Member
0 Kudos
164

I have an MII transaction that was set up to use a JCo connection to execute BAPI_ALM_ORDEROPER_GET_LIST. It is using the version of the JCo connector without session management. I am doing some work with the transaction and decided to convert it to a JRA connector with session management as this appears to be the most current method.

When I send the same request document to the BAPI via JRA that I used to send via JCo, the response XML I am getting back indicates an error "Enter at least one selection criteria". When I execute the same BAPI with the same request XML using JCo, I get a response document that returns the result set I am expecting.

Any thoughts on what could cause this behavior?

Here is the requestXML file I am sending to both connectors.

<?xml version="1.0" encoding="UTF-8" ?>

- <BAPI_ALM_ORDEROPER_GET_LIST>

- <INPUT>

- <DISPLAY_PARAMETERS>

<PAGELENGTH>1000</PAGELENGTH>

<SHOW_PAGE_NUMBER />

<FORCE_REFRESH />

</DISPLAY_PARAMETERS>

</INPUT>

- <TABLES>

- <IT_RANGES>

- <item>

<FIELD_NAME>OPTIONS_FOR_PLANPLANT</FIELD_NAME>

<SIGN>I</SIGN>

<OPTION>EQ</OPTION>

<LOW_VALUE>1043</LOW_VALUE>

<HIGH_VALUE />

</item>

- <item>

<FIELD_NAME>OPTIONS_FOR_EARL_SCHED_STA_DAT</FIELD_NAME>

<SIGN>I</SIGN>

<OPTION />

<LOW_VALUE>20000101</LOW_VALUE>

<HIGH_VALUE>20010101</HIGH_VALUE>

</item>

</IT_RANGES>

</TABLES>

</BAPI_ALM_ORDEROPER_GET_LIST>

Edited by: jlwilloz on Oct 4, 2010 4:43 PM

Accepted Solutions (1)

Accepted Solutions (1)

jamie_cawley
Product and Topic Expert
Product and Topic Expert
0 Kudos

Try using the "Remove XML" link type on the portions of the tables section that you are not using. Sometimes jra pulls down default fields that need to be cleared out.

Jamie

Former Member
0 Kudos

Had already tried that with no success. Since I started this thread I did figure out the problem though. The XML that you feed to a JRA connector is slightly different than what is fed to the JCo connector, and I didn't notice it originally. For the JRA connector, the "TABLES" element comes first where in the JRA connector, it is last. Also, some of the elemets for the JRA connector contain attributes where the same elements in the JCo connector do not.

I switched to using the JRA version of "RequestXML", and all is working fine now. I guess I was just surprised that the two are not compatible,

Former Member
0 Kudos

Had already tried that with no success. Since I started this thread I did figure out the problem though. The XML that you feed to a JRA connector is slightly different than what is fed to the JCo connector, and I didn't notice it originally. For the JRA connector, the "TABLES" element comes first where in the JRA connector, it is last. Also, some of the elemets for the JRA connector contain attributes where the same elements in the JCo connector do not.

I switched to using the JRA version of "RequestXML", and all is working fine now. I guess I was just surprised that the two are not compatible,

Answers (0)