Vistex IP Module - manual price conditions get replaced

[Former Member]

Hi all,

We are experiencing strange behavior in Vistex Rebate Claim Requests. While processing claims, occasionally all the item level manual price conditions will get changed and replaced with the condition values from a completely different claim! We have been unable to isolate a set of common factors that causes this so we cannot discover the root cause.

What we find is that after this happens, the Status Manual Price Indicator (field MPROK) changes from A to blank.

We have submitted an OSS message to Vistex Support but they cannot find what the problem is.

Does anyone have any ideas?

Thanks & regards to all

[Jelena]

Go through your VOFM routines (transaction VOFM). Take a look at everything in Pricing. The custom routines have the numbers in 900 series. Also search for any code in the user exits that could have been written by a Vistex consultant (check transports by user ID).

[Former Member]

Thanks Jelena,

I should have mentioned that we have already been through all the VOFM 900 series routines and the user exit coding and we cannot find anything that would be causing this problem. It is so random.....we can go for days without any issues, then suddenly it will happen out of the blue. We cannot recreate the error on demand either. It is a total mystery to both our development team and Vistex Support.

Any further insights would be appreciated.

Thanks & regards

Roy Siggins

[Jelena]

From my experience, when problems like this occur, there is always a pattern, but sometimes it's just difficult to see. Some issues took months to finally catch and explain, but everything has a reason.

You said that conditions are getting replaced with the ones on a different claim. What is that claim? What does it have in common with the other claim? Are their numbers close and are they being processed in the same run?

Also check in all the code that when reading line-level tables (e.g. XVBRP and such) the full key, including document number (VBELN) is being used to pull the data.

Do you create documents in the background? There might be multiple threads/instances of the same program running at the same time and data that's stored in memoty could get mixed-up between them. True story - once I was debugging a sales order creation and in ABAP debugger under user ID (ERNAM) I saw not my name but another user doing testing at the same time. If you have a background run, it sometimes helps if you sort of make it slower, e.g. by running in batches or in a single process.

What else is going on in the system at the same time that could influence the claim creation?

If possible, try setting up some "traps" along the way - add some sort of a log or additional messages to see what exactly is going on at what time. The obvious thing to track would be when Manual Price Indicator is changing the value.

[Former Member]

Jelena,

We will definitely take a look at all the things you mentioned. I agree that there is a pattern but right now we cannot identify it. We have had occurrences of this problem as follows:

(a) where the claim request (whose conditions were taken over to the claim request being changed) was in the work list - i.e. being worked in the same session.

(b) where it was not in the open work list but it had been a claim that the User had processed earlier in the day

(c) where it was not in the work list at any time

We have identified all the things that Users do when it happens so I have tried to recreate the issue in our sandbox client - step by step doing exactly what the Users did and using the exact same data. I have never been able to reproduce the problem. The only difference between our sandbox and live production is that the sandbox is on a single server. Production environment has groups of servers for load-balancing. I am am not even sure this would have an impact.

Thanks & regards

Roy

[former_member182877]

Hi Roy,

Were you able to identify the pattern and resolve the issue?

Cheers,

Kripa Rangachari.

[former_member61234]

Yes SAP/Vistex Support resolved the issue after we discovered how to recreate the issue. Basically it happened when you 'X" out of the Item Details pop-up instead of "Enter". They made a direct fix in our system (no OSS Note).