Publishing ZBAPI updates to NetWeaver

[agentry_src]

Hi All,

I find myself in a strange position where I am asking about something I knew (sort of) from over a decade ago. It seems to have resurrected itself in the present.

I am working with a client that is customizing Function Modules and BAPIs, but they do not seem to show up in their new versions in MII until at least a day has passed. I, rather vaguely, remember that the updates to such had to be pushed down to the NW platform before MII could recognize the changes. I am limited in my NW knowledge, much less the ABAP end of things. If anyone can explain how this works, I would be very grateful.

I am trying to use the JCo (Java Connector) to exercise the RFC/BAPI within a transaction.

Cheers, Mike

salvatore.castro

Hey Sam,
Any idea who can answer this?

[former_member185280 · Accepted solution]

/XMII/JCOProxy?mode=reset

[agentry_src · Accepted solution]

Hi Christian,

I tried that and it has no effect. My understanding is that cleared the cache locally, but I have not used it very much (never needed to).

Does that force a push of new code to the NW platform? We are seeing an odd error message.

'[ERROR] Unable to make RFC call Exception: [Character reference "" is an invalid XML character.]  '

Maybe I should have asked about that, but we have had other errors where the custom RFC development is concerned. We were seeing changes propagate but only by the next day (maybe sometimes longer, I can't really say when I started noticing the new RFCs changing their behavior).

The underlying function module is PM_HIERARCHY_CALL which was not externally enabled. First a wrapper was tried, but apparently that remote enabled wrapper tries bypass the function module's not being remote enabled. Then the developers tried to clone the FM, all the classes, methods, etc. but we are still getting the error message.

[agentry_src · Accepted solution]

Apparently my assumption that it had to do with NetWeaver was premature. After researching the error message rather than presuming to know more about the problem than I did, I turned up quite a few items on this very topic. Including them here just in case anyone else runs into the problem.

https://archive.sap.com/discussions/thread/3441733
https://archive.sap.com/discussions/thread/2118011
https://archive.sap.com/discussions/thread/3619375
https://archive.sap.com/discussions/thread/3893180
Please read the four SAP Notes in one of the responses.  The solution is
probably outlined there.
https://archive.sap.com/discussions/thread/3836907

[former_member185280 · Accepted solution]

I don't think it pushes the change per se, the JCo connector will see that it doesn't have the function definition in it's cache when you make a call and then go get it it from sap. Sometimes you need to update the xml in the JCo action as well, sometimes you don't. Also if you have a cluster I think you have to clear the cache on every specific server in the cluster. Maybe there is some kind of cluster or caching on the SAP side? Are you running directly in the workbench or another way? Maybe transaction caching is turned on?

I am confused a bit now tho. So your rfc works eventually or doesn't work at all?

That FM has a lot of defaults. Sometimes the defaults don't format right in the JCo action and you have to set them directly. Log the request xml and see if it looks funky.

You could try PM_HIERARCHY_CALL_REMOTE. It may not give you everything you need in one shot but they may have done that for a reason.

[agentry_src · Accepted solution]

Meant to come back sooner and accept the answer you posted. At the core of the issue was a flaw in the custom BAPI. Once that was fixed, the JCo Reset worked as you suggested.

Thanks Christian!