ST22 giving wrong message?

[Former Member]

Hi,

I am having a production dump where i see the following message in the "Source code extract" page:

Caution: Program has changed

Caution: At time of termination, Active source code no longer available

The funny part is that we are in a quarter end freeze and there is no chance for the code to be changed in production when it was executing. Have anyone encountered this kind of a situation before? Any idea why this message appears?

Regards,

Hari.

[Former Member]

I'm not sure exactly what is happening. Is the dump saying that the source shown in the dump is not the same as the current source? Or is it saying that the program dumped because the program changed while it was executing? I've seen both cases.

Rob

[Former Member]

Hi Rob,

The program has dumped due to other reasons. But just above the source code extract SAP has displayed this message:

Caution: Program has changed

Caution: At time of termination, Active source code no longer available

But as i said there is no chance that the source code has been changed.

Regards,

Hari.

[Former Member]

Well, it's saying that the code <b>has</b> changed. Is it your own source or SAP's? In any event, go to version management and see what happened.

Rob

[manuel_bassani]

Hi harikrishnan,

i don't exactly understand that's happening, but consider that some standard programs are automatically generated (like function group of mantain. views)

Regards, Manuel

[Former Member]

Hi,

This is happens in an user exit that is called while a quoatation is saved.

Regards,

Hari.

[Former Member]

As I said, look at version management for the source.

Have any notes or support packs been applied?

Rob

[Former Member]

Hi Rob,

I had checked this first. The last change was in 2004. And as mentioned we are in a freeze and no code changes are being transpored to production.

Regards,

Hari.

[Former Member]

Did you check all the programs in the stack - not just the one that dumped? If it said that something changed, I'd bet that something did.

As Manuel said, SAP sometimes generates code on the fly. Maybe this is what happened.

Rob

[Former Member]

Yes , i did check all the programs. I did also check if there are some STD modules that are being generated at run time, but could not find any. Also this is not the first time i am seeing this. We faced a similar issue about a week back.

[Former Member]

Well, I'm stumped. If it's important from an audit standpoint to find out what changed, you can try debugging ST22 to see why it's giving that message.

Rob

[Former Member]

Did you try the things I requested? Check the most recent config changes that are transported to production. How often is this happening and any pattern in that behaviour?

[Former Member]

Hi Srini,

Thanks for the response. I did check, and as i said we are in a freeze and there were only 2-3 transports that moved, none of them were related. This is the second time it happened, and both for the same object. The program dumped due to a different reason, a quantity issue.

Regards,

Hari.

[Former Member]

Can you go ahead and regenerate the main program of this transaction? Just make sure no one is in it while you do this.

You said 'quantity issue'. Can you expand on that please? You still didn't give us which transaction it is.

Is this happening in your user exit code?

Srinivas

[Former Member]

Hi,

Sorry for the late reply, but too manu PRD issues! We have users creating Quotes through WEB and this creates a quaote in SAP through VA41. We have an exit in VA41 that stores data to a Z table. Some times the users enter special characters in a quantity field that goes into the Z table and we get the dump at the insert statement.All this is fine, but ST22 also gives me that spooky message which i am not able to comprehend. We do have other quotes going through and getting created in SAP.So the code is active. An there were no changes to code, i am so sure because any code changes during the freeze period requires a long approval chain and we would be aware of that.

Regards,

Hari.

[Former Member]

Hari,

The reason why I am so hung up on the changes is that, you are getting this message for a reason. There must be something that SAP is trying to compile of regenerate code or something. Now that you mentioned that these are created from web, that opens another aspect of it. How are your users connecting to SAP from the web? Are they calling some RFC which in turn calls VA41? Have you checked if that RFC has changed recently? How often do you refresh this connection? RFC connections are usually buffered, which means your RFC connection may have an older version of the code, while it has been changed in SAP. You need to bring down the connector and bring it back up. That way the connection will be refreshed.

Config changes, particularly those of pricing procedures, VOFM routines and condition types, will result in automatic generation of code. That is why I was asking if there was a config change.

When was the last note or support pack applied? You can verify this in the menu, SYSTEM-->STATUS under "SAP system data". Press that little display icon, there you should see some dates.

Coming to your root of the problem, can you have the web frontend take care of removing all those special characters.

Other than these thoughts, I don't know what else to think.

Good luck.

Srinivas

[Former Member]

Hi Hari,

Please give us some information. Which transaction is this and which main program is it?

Is there a support pack or a note or even some config change that has been applied to the production system?

You should be able to simply go to SE38, enter the main program of this transaction and activate/generate it one more time. That should take care of it. You should do it only when no one is using it.

Also let us know if this is happening every time or just once or twice?

Srinivas

Message was edited by: Srinivas Adavi