Error during GR: Transaction cannot be posted due to errors in price determination

[Former Member]

Hi All,

Facing an error with below scenario:

• During GR of Inbound delivery i am facing error mentioned in subject(screenshot below)
• This delivery document was created on 17th Oct, 2014
• We faced this error on Oct 25th, 2014 (well before expiry of item condition)
• Item condition for this Scheduling agreement was valid till Oct 30,2014 and user added another item condition line item from Oct 31, 2014 to 2099 so that we don't face any issues on this front.

We have already tried the following:

• Implemented note 447374. It does not work for us
• Notes 113856 and 1059878 are not applicable for our release of SAP

Recently we have started facing errors with below details too:

• GR fails for deliveries created in November
• Item condition for predecessor POs were valid till Oct 30, 2014.
• User added new line item with new item condition

Please advise what could be causing this issue

Thanks

Akash

[Prasoon · Accepted solution]

Hi,

   Seems the note:  447374 - ME573"Transctn cannt be postd due to errrs in prce detrmntn"  exactly deals with your situation. If its not solved even after applying the note, you may raise an OSS ticket to SAP.

Regards,

AKPT

[Former Member · Accepted solution]

Hi All,

I finally got the right answer from SAP Global support.

Needed to run price simulation at item level for the SA.

That led me to the problem condition GRWR -- incoterms EXW.

The value for this condition was maintained as 100,000.

The maximum allowable value for this condition is 100.

Hence the error.

Went to transaction MEK2 and reduced this to 100.

Thanks

Akash

[JL23]

Your screen shot does not show the full error text and you did not explain to which of the listed errors the X is set like this [X]

[Former Member]

Hi Jurgen,

The screenshot includes the long text below Diagnosis : "The error marked with X occurred......".

My ABAP colleague was unable to find out which of these conditions is set as X .

Thanks

Akash

[JL23]

Your screenshot shows 6 reasons, the original message has 11.

the last 5 reasons are not shown

[Former Member]

Hi Jurgen,

Sure.

Please find below all the 11 reasons for the error:

Thanks

Akash

[JL23]

I think it is not good practice to issue an error message with 11 reasons and then not showing which of those reasons is valid.

If this is not influence by own programming (exits, modifications, BADIs ...) then you should take it to SAP Support