cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with PR to PO conversion with t-code: ME59N but same PR is converted to PO with t-code: ME59

Former Member
0 Kudos

Hi Experts,

We are getting the error "Net price must be greater than 0" Error message: 06 218 while converting PR to PO using t-code: ME59N. The same PR is getting successfully converted to PO via t-code: ME59.

All master data settings are maintained

1. Vendor Master & Material master- Auto PO tick OK

2. Source List maintained OK

3. Info-record for material-vendor combination maintained OK

4. Condition maintained OK

Also, I have tried creating the PO using the same PR via ME21N and did not get any error. PO was created successfully.

I have checked SCN and could not get requisite link which answer my query. Any inputs/pointers will be helpful.

Thanks,
Sandeep

Accepted Solutions (0)

Answers (6)

Answers (6)

former_member201529
Active Contributor
0 Kudos

This message was moderated.

Prasoon
Active Contributor
0 Kudos

Hi,

   Please check whether the following note is valid in your scenario and SAP release:

895449 - ME59N: No prices with central purchasing

Regards,

AKPT

Former Member
0 Kudos

use standed purchas organization

JL23
Active Contributor
0 Kudos

kalyan vogat, Please use a spell checker.

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

Hi

Please check your Purchase Requisition-->Item detail-->Valuation price. This might be zero.

This is might be due to material price not maintain in material master record.

Regards,

Ashishkumar Banker

JL23
Active Contributor
0 Kudos

ME59N replaced ME59 because of new functionalit, ME59 is out of support for almost 2 years now.

So I would not compare the result of both transactions, instead I would just focus on analyzing why ME59N was not able to catch the price.

As a first check you could try it with ME21N to see if SAP could find the price itself, if not then you can use the analyze button in the condition view to see where the problem is originating.

Such infos like ". Condition maintained OK"  does not tell anything, especially the info if the conditions are valid today or at delivery date is not given. You should try to explain or use screenshots.

If you say everything is okay, then the only answer could be "program bug"

Likely since there are different programs behind the 2 transactions. As well possible that a BADI with your own coding  is considered in ME59N but not in the old unsupported ME59.

Former Member
0 Kudos

Hi Jurgen,

Yes, on trying PO creating manually via ME21N, it is picking the price condition itself and the condition  validity is within the delivery date.

Thanks,
Sandeep Sahota

former_member183424
Active Contributor
0 Kudos

Can you post screen shot of ME59N and Info record and also PR details.

Also please have a look into the wiki content for a reference ME59N trouble-shooting guide - ERP SCM - SCN Wiki