Missing Price Rate...in the past

[SimoneMilesi]

Hi all!

i've a weird situation where i created a sales order (dates from 10 to 30 sept. 2018, speaking about creation, delivery, price and so on) and all works fine, price is calculated (in AUD while the company currency is EUR but we mantained OB08 since 1st of July, 2018).
Then i update one item's Account Assignement and i insert a WBS as account assignement.
And here i got message SG105

Enter rate AUD / EUR rate type M for 01.01.2015 in the system settings
Message no. SG105
Diagnosis
For the conversion of an amount into another currency, an entry is missing in the currency conversion table.
Procedure
Add the missing entry in the currency conversion table.

i can understand the system needs the exchange rate, but i cannot understand why for 01.01.2015!
i have no date previous half july 2018 in both Sales Order and WBS.
i checked a lot of similar questions and i see in OB08 the rates are ok.

To make a test, i insert the row in OB08 at 01.01.2015 and it works.

The question is.. why?

[Lakshmipathi]

While I don't have an answer to your question "Why", you can have a look at OSS note 2428955

[SimoneMilesi]

Thanks for the note!
i installed it since we need it and i'll keep the situation monitored: we maintained the rate at 1/1/2015 to be able to process the SO and the following documents, so i have way to check if the note solves the issue.

[sez41]

Hi Simone,

Exchange rates are calculated on the pricing date. Since you say that after you update one item's Account Assignement and insert a WBS as account assignment everything is broken, the only logical explanation is that pricing date has changed. I could recommend debugging by setting a watchpoint for the pricing date to explore which functionality has been changing this.

[pjcools]

Hi Simone

I would say that the date is somewhere in either the document or the WBS to be then looking at this currency conversion date. There may also be a userexit involved here as well depending on the circumstances (e.g. if a WBS is entered then..... etc). Try removing the WBS and see if it works as before and then I would re-enter the WBS and see if the same error applies.

I would check userexits as well, there could be a rule to take the date from the WBS create date or something weird like that.

This would be my first starting point in trying to work out where this date is coming from.

Thanks & Kind Regards

Phil Cooley

[SimoneMilesi]

Hi Phil!

It's surely related the WBS, but it's a basic project with 6 tasks and, believe me, i checked all the dates there without finding a date previous past july (2018).

Thanks for your interest

[pjcools]

Hi Simone

Did you check user exits? If something weird is happening this is the first step I would take. I've seen some weird stuff over the years included dodgy key numbers in tables that are read incorrectly to provide different results. Only debugging assists in finding out what is going on.

Assuming you have done this already. If not, debugging is the key.

Good Luck!

THanks

Phil