Problem with user exit code and refresh to query

[Former Member]

We have a problem that when we make changes to the user exit ZXRSRU01, activate, and then refresh the queries, the changes to the code from the user exit will not take into effect when we refresh the query. We often have to logout the system completely and rerun the query.

We are working on 3.5 SP11. Had one had this problem and had applied any SP other than 11?

It's terrible to do some development work and have to log off anf back again to make sure the query took the code changes. Absolute unfortunate when you're trying to do the work for them and no one is making it easy.

I am not sure why would anyone refuse to apply the system to SP 18 when nothing has gone live yet.

[Former Member]

actually, its quite easy. i do it all the time with exit variables; just run the query via RSRT with a temporary break point in your variable (i always want to check if its working anyway). that will force it to use the new code (i always regen the query after each change in the exit, but i am not sure that is necessary); this way you only need to exit and re-start BEx once - after everything checks out.

sorry, you don't like the system

[Former Member]

No No No No...

There is no need to go round about way of using RSRT and using the debugger; I don't have time, but thanks anyways.

The point here is working with 3.5 SP 11, and there is a chance that you would run into problem and not knowing whether if it could be your approach or the system itself.

Here are other points:

1. They want the reports done quickly and yesterday.

2. When you ask them a question nicely about the system, they accuse you of this and that. Plain vicious...

3. They provide you the system that is acient and archaic to work on.

4. They quickly speak before they think of the consequences.

I could go on and on but then why waste my time...

[Former Member]

Hi,

Unfortunately this is how SAP coding works... normally for a query to take in the new code it will require a logoff or something.

From what I recalled, at the point of executing a query, an ABAP program is created on the fly, and it will point to the version of the coding that it was using (there's version management in programs and functions). Hence no matter how you're refreshing the query, this ad-hoc program will still point to the same version of the user exit. Until you completely log off the query and re-logon, the ad-hoc program will not be refreshed.

Not too sure if this is overcome in the later release. You might have to raise an OSS to SAP to get an answer.

Hope this helps.

Cheers,

Gimmo

[Former Member]

Hi,

Thanks for the detail explaination.

You know, tell me if there is anyone out there is still developing on 3.5 SP11 and planning to go live with this version. It's backward; it's obsolete; it's ancient; it's archaic; it's awkward; it's behind - behind the competitors who are running on the most robust systems provided by SAP and recommended by SAP.

BTW, I'll be so glad to finish the development and can't wait to get it over with and be gone on the go live and let someone else deal with the production go live. They don't think about applying the SP now and doing the testing at the same time. It's rather to find the problem at this phase than at the go live date.

Ha Ha Ha Ha...