Skip to Content
0

Net price must be greater than 0 is coming via PO change Idoc

Jan 23 at 03:29 PM

74

avatar image
Former Member

Hi All,

The following error message "Net price must be greater than 0" is coming via PO change Idoc(STO). The Idoc flow is one SAP System to another SAP System. In our SAP System, There is no Pur.Info record Concept and we have Condition Record to update the price in STO (Here we have routine to maintain the Condition if the Vendor schema Grp is IV then the Price should be updated from VK11 instead of MEK1). In Inbound Idoc, we are receiving the Condition Price 9417 JPY as same as Condition Price in our System.

Other Details:

1) The Condition Record has been changed on 27.12.2017 (Periods 01.01.2018 to 31.12.9999).

2) PO creation date is 07.11.2017 and PO change date is 16.01.2018

3) Condition Type is PI01 and there is no Statistical Indicator set and no requirements are available in the Calculation Schema.

So please share me the details as what could be the reason of this error messahe in Idoc.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Kunal Ingale Jan 23 at 06:19 PM
0

Hello ,

was this functionality working before , if yes then you need to see form when and due to what it stooped working.

as per your description it seems you have changed the condition records , So it seems to be the one of the reason.

now as this is a custom program/Logic , you need to take help from your ABAPer which may provide you faster solution.

I think you should check what logic is applied in the routine , whether it compare the PO creation date or the change date with the validity period.

try making condition record start date as 061117 , if this resolves the issue then your logic must be comparing the creation date rather than the chnage date.

Thanks

kUnal

Share
10 |10000 characters needed characters left characters exceeded
Pramila Toom Jan 23 at 08:27 PM
0

Hi Suresh,

The condition record was updated on 12/27/2017 with the future date and hence you are seeing the issue with the net price as zero.

When the PO has the effective date as future date, the pricing record will be created with the start date as system date, as with future date the net price is zero for the current date and it fails creation/update of the document. Try changing the validity period and that should resolve the issue.

Thanks

Pramila

Show 2 Share
10 |10000 characters needed characters left characters exceeded

Really...? I need to test it ..need to see if system makes my validity start date as todays date..

My understanding si system chek for po creation date to comapre validity of conditions to fetch value.

0
Former Member

Hi Pramila/Kunal,

Thanks for your reply !

I have tested many cases in the lower environment by changing the Condition Record Validity start date and it is working fine, If my PO creation date in current date. But in my case, The PO creation date is 11/06/2017 and new price was updated on 12/27/2017 and PO Change Idoc was received on 01/03/2018 & 01/16/2018. Based on the validity date, it should update the new price via PO change Idoc but it is not update here.

@kunal : I will check with our ABAPer for pricing date logic and get back you further !

0