Skip to Content

The wrong price is pulled out of the Info record

Good morning all, I have an issue here.

In my company, Purchase orders are generated from purchase requisitions by a batch. During that process, the priced is pulled out of the info record. There is a scale set up in the info record which says :

From 10: $ 23

From 30: $20

The quantity ordered in the purchase order is 20 pieces but the price pulled is $20 instead of $23.

I first thought that somebody has changed the purchase order after it has been generated by the batch but, no change has been made to the purchase order.

Does anyone has an idea or has already faced this issue?

Thank You all.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

11 Answers

  • Oct 15, 2016 at 10:00 AM

    Hi,

    Please test the scenario with a new direct PO and check how the price is pulled. If the price is pulled wrongly, check the info record validity and whether the scales are maintained correctly for the PO date. If issue is not resolved, revert back with the screenshot from info-record.

    Regards,

    AKPT

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 15, 2016 at 10:27 AM

    can you share you screen of info record. As per system behaviour it will always take the lastest info record price.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 17, 2016 at 12:09 AM

    Dear Prasoon , Dear Bhaskar, thank you for your help.

    I did simulate the PO in quality and it is picking the good price. As you've requested, here are 2 screen shots of the Info record. Thank You.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 17, 2016 at 07:13 AM

    Please check whether you have PIR for specific plant or not.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 17, 2016 at 11:48 AM

    Hi Andy, the PIR is plant specific.

    Thank You.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 17, 2016 at 12:05 PM

    The system behavior seems to be incorrect, please choose update prices in the item conditions and then select redetermine scales (Pricing type 'A'). If it doesn't resolve the issue, then carry out new pricing.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 17, 2016 at 04:29 PM

    Hi,

    Please check the order unit in PO - if its different from the scale unit, check the conversion rate. If the UOM is same in the condition record and PO, please check which access has been pulled in the PO - item level - analysis button - whether any other access has been triggered. Check the condition origin and the access triggered and revert back.

    Regards,

    AKPT

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 18, 2016 at 05:43 AM

    Try to create a fresh PO and check the analysis button in condition tab, Check does these value matched with your info record value?

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 24, 2016 at 11:40 PM

    Thank You all, here is a summary of what I have done so far to solve my issue.

    As suggested by Rosh, I updated the price in the item conditions and then selected redetermine scales (Pricing type 'A'), but it did not solve my issue.

    As suggested by Prasoon, I checked the order unit in the PO and it is the same as the the scale unit in the Info record. The access that is pulled is 025 (PB00) and the system is showing the wrong scale price (23.95 instead of 19.44).

    Now just to let you know, the purchase order is generated in our system by a batch job Me59n (conversion of a purchase requisition which is generated by a sale order) .

    I made a strange observation:

    I created 2 purchase requisitions. I converted the first one by Me59n, there the system is picking the wrong scale price.

    I converted the second purchase requisition manually with me21n (indeed, I adopted the purchase requisition from the document overview) in the PO screen and saved it. There the right price was picked up.

    Please let me know your thoughts

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 25, 2016 at 07:18 AM

    pl see whether KB 1952921 explains why 20 was picked instead of 23

    Add comment
    10|10000 characters needed characters exceeded