We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-log-mm] Manual Purchase Price Condition

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from Logistiker on Mar 11 at 11:38 AM
Hi Ha Tran,

I have done that as well unfortunately and it just says it has been manually entered. Interestingly enough if I recalculate the pricing the Z Condition type disappears. For some reason it pulls this condition every time when a new PO line for this material/vendor is created.

Regards
Logisitiker

---------------Original Message---------------
From: Logistiker
Sent: Friday, March 07, 2014 12:12 AM
Subject: Manual Purchase Price Condition

Hi MM Guys,

I have a weird issue with one material and vendor. We have a manual Z Price condition which acts as a surcharge at either header or item level. This condition is being pulled into every PO that is created for that vendor with that material. Looking at the price history of Purchase Info record and contract, this condition has never been maintained!

I have checked with MEK3 the PB00 condition with all possible available combinations and this price has not been maintained. I have checked all the other pricing transactions like MEKJ and MEKG, etc. but this price is not there.

I have checked MEPA to simulate the PO price and this condition is being shown after a certain date in 2012. I want to get rid of the condition as it is not required. Has anyone any idea where / how to find it?

Thanks,
Logisitker

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2014 Ziff Davis, Inc. and message author.
Ziff Davis, Inc. 28 E 28th Street New York, NY 10016
Logistiker  

achievements
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Have a technical question? Need to find IT solutions? Ask your peers in the Toolbox for IT community.

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language