XR1 - XR6 are displayed multiple times

[Kaitlin]

Hello.

In a pricing procedure for US Vertex controls the values passed on to XR1 - XR6 and in the corresponding pricing procedure each condition is entered once.

I noticed that in the commercial documents, in conditions for item tab each of the condition is displayed twice, once with value 0 and the second time with the expected value according to location provided by Vertex . To make things more confusing in the pricing analysis each is displayed 3 times:

- XR1 008 Condition record exists (removed manually) - that's a nonsense since this condition type can't be manually maintained

- XR1 207 Condition has been found (without condition record)

- XR1 208 Condition record has been found

...and the same can be viewed for all the rest starting with XR2 thru XR6.

On the SAP platform there are several US pricing procedures but only one displays XRx conditions more than once in the conditions tab but in Analysis Pricing same condition may be displayed 2 or 3 times

Any explanation for this behavior?

Thank you.

Kat

[Kaitlin]

Hello.

I checked the differences and found none and yes, I was referring to F2 invoice types.

So far the only thing that I found were 2 UXTJ condition types:

- one valid till 9999 marked as deleted

- the second being the active/used one.

It seems ridiculous but after reducing the validity of the deleted one - and that was in itself quite a jurney - to some date from the past to my utmost surprise it worked, ...for a while on one company code only, meaning the number of XRx lines reduced with 1 unit.

Now the solution that seemed to have worked for a while is not producing any effects, much as it always happened of the second company code so we'll open an incident with SAP and see what happens from there.

Thank you.

[VeselinaPeykova]

I cannot comment on the Vertex part of the question, but did you try comparing the settings between the problematic procedure and the ones that work correctly, also copy control settings(I assume that by commercial documents you meant invoices like F2? Normally this is what I would do in such situation - checking what is different and then try to eliminate the differences in a sandbox until the root cause is found.

As to the seemingly confusing messages in pricing analysis - I suggest that you read SAP note 363212 - "Pricing analysis" mode of operation, which lists the messages that you mentioned and some possible causes. For 008 it may be useful to read also note 859876 - Condition is missing: Message VE 108 or VE 008, which is mentioned in the first note as a special case for VE008.

For some of the analysis you may need to ask the assistance of a local developer if you do not feel confident in reading code or debugging.