savithk
Member
Hello,
During OD receipt , in SD/OD process, we over received secondary quantity in P4312 and system updated SD secondary quantity correctly but it didn't recalculate the extended price. Our pricing UOM = Secondary UOM.
Steps to reproduce:
1) Create a item with Dual UOM turned ON and update Primary UOM= LB and Secondary UOM=LF and Pricing UOM=LF
2) setup Item conversion 1LB= 2 LF in P41002
3) Create SD/OD Primary(Transaction) Quantity = 100 LB and system bring Secondary quantity = 200 (automatically) and update unit price = 10 and system calculates extended price = 2000
4) P4312 , receive OD with Primary unchanged(100LB) and secondary 201 LF
5) System updates SD secondary = 201 LF correctly and It DIDN'T recalculate Extended price. Extended price still showing 2000 and expected Extended price = 2010.
And Yes we did apply JM16709 last October.
If above issue is an expected system behavior or a system limitation , does any one know how to use "secondary quantity" to drive extended price in P4210? Basically we need to Bill customer based on Secondary and Receive(purchase & Pay) based on Primary.We don't have base price concept so we can't use advanced pricing we always override unit price.
Any suggestions much appreciated.
During OD receipt , in SD/OD process, we over received secondary quantity in P4312 and system updated SD secondary quantity correctly but it didn't recalculate the extended price. Our pricing UOM = Secondary UOM.
Steps to reproduce:
1) Create a item with Dual UOM turned ON and update Primary UOM= LB and Secondary UOM=LF and Pricing UOM=LF
2) setup Item conversion 1LB= 2 LF in P41002
3) Create SD/OD Primary(Transaction) Quantity = 100 LB and system bring Secondary quantity = 200 (automatically) and update unit price = 10 and system calculates extended price = 2000
4) P4312 , receive OD with Primary unchanged(100LB) and secondary 201 LF
5) System updates SD secondary = 201 LF correctly and It DIDN'T recalculate Extended price. Extended price still showing 2000 and expected Extended price = 2010.
And Yes we did apply JM16709 last October.
If above issue is an expected system behavior or a system limitation , does any one know how to use "secondary quantity" to drive extended price in P4210? Basically we need to Bill customer based on Secondary and Receive(purchase & Pay) based on Primary.We don't have base price concept so we can't use advanced pricing we always override unit price.
Any suggestions much appreciated.