JRA "Execute Function" Option in MII 12.1.8.24

[Former Member]

We recently upgraded our MII instance from 12.1.4 to 12.1.8.24. MII is running on NetWeaver 7.01 sp08.

We have noticed a drastic change in the way that "SAP JRA Function" Action block works after the upgrade. The "Execute Function" Check Box appears to be the culprit. Prior to the upgrade, selecting the indicator for "Execute Function" resulted in the RFC being executed and returning results. Not checking the box would simply result in the XML Structure being available. This lined up with the SAP Help definition for JCO which can be found here: http://help.sap.com/saphelp_mii122/helpdata/en/45/a3da12c3b50cefe10000000a114a6b/content.htm

Now that we have upgraded the "Execute Function" results in the following:

- When selected the RFC is not called and no results are returned.

- When NOT selected the RFC is called and the results are returned.

I am hoping someone else has already encountered this or can tell me I am doing something wrong.

Thanks

[agentry_src · Accepted solution]

Are you really running MII 12.1.8 on NW 7.01 SP8? If you have a typo with either the MII version or the NW version, please correct and repost.

Thanks,

Mike

FYI, MII 12.1.8 should be running on NW CE 7.11 SP5

[Former Member · Accepted solution]

I will do this today as soon as I figure out how to do it. It has been at least 5 years since I've had to put in a ticket with SAP.

Thanks

[Former Member · Accepted solution]

I see you changed your original posting. There is no typo. So this means my basis folks installed the wrong version of NetWeaver with the most current version of MII?

UPDATE: I am making sure they gave me the NetWeaver Version from our Java installation and not our ABAP installation. I will re-post when I have a good sense they've provided the correct version info.

Edited by: mubgt38 on Mar 10, 2011 12:18 PM

[agentry_src · Accepted solution]

Sorry about the first post. I missed the potential version conflict the first time I read your thread.

Regards,

Mike

[Former Member · Accepted solution]

No problem, Michael.

My Basis team did initially give me the wrong NetWeaver version information. They are now telling me MII was installed on NetWeaver CE 7.1106.

Thanks

[agentry_src · Accepted solution]

If I interpret that correctly, it would be NW CE 7.11 SP6. I was not aware that SP6 had been released yet, but I am pretty sure that the installation instructions for MII 12.1.8 will specify SP5 as the version to use. MII and NW versions really do need to align correctly. This may be the cause of the JRA problems you are experiencing.

I would suggest you verify the NW version and Service Pack with the Basis folks (and reread the installation instructions for 12.1.8 build 24) and make sure the two versions are correctly matched.

Good luck!

Mike

Edited by: Michael Appleby on Mar 10, 2011 8:26 PM

[Former Member · Accepted solution]

Thank you, Michael. Based on your suggestion we found OSS Note 1537813. Is this note telling us that MII 12.1 SP08 requires only NW CE Version 7.11 SP05 and no version above this?

[agentry_src · Accepted solution]

That is what I remembered for 12.1.8. Glad you could find the note and post it for others to review.

Regards,

Mike

[Former Member · Accepted solution]

Thanks for your help, Michael. We are restoring the system to its state prior to our upgrade and installing Mii 12.1.8 on NetWeaver CE 7.11 SP5. Hopefully, this fixes our problem. If not, I'll post some more info.

[Former Member · Accepted solution]

We have now installed Mii 12.1.8 (Build 24) on NetWeaver CE 7.11 SP05. We are still seeing the same issue with JRA.

The SAP JRA Function Action Block "Execute Function" parameter is working the exact opposite of how it worked prior to the upgrade. When it is selected the Action Block only builds the necessary XML Structure. When it is not selected it executes and returns values.

Any advice?

[agentry_src · Accepted solution]

I think at this point, you need to open a ticket and we can see what the development team comes up with. For the time being, I would put in a global property for the Execute Function boolean. Do all your development with Reversed logic, but tied to the global property. Then when a fix is accomplished, change the value of the global property. That will minimize changes afterwards. Not the best approach, but probably good for the time being.

Or you could go with the JCo based action blocks.

Regards,

Mike

[Former Member · Accepted solution]

We have entered a ticket.

[Former Member · Accepted solution]

This is a bug that I've been told will be resolved in EP 09.