Hi,
I tried the MOM pricing levels today in order to update the price for a particular customer type code. Unfortunately, the update worked for some of the items that had committed inventory but not for the other items on backorder status.
Does anyone have any experience with this>??
Regards,
Videoflicks2004
Adding New Pricing Levels mom 4.3
Started by Videoflicks2004, Jul 13 2005 05:51 PM
3 replies to this topic
#1
Posted 13 July 2005 - 05:51 PM
David Narciso
Ecommerce Operations Manager CVS Inc
[email protected]
mobile: 4168238175
DISCLAIMER: Always backup your MOMWIN folder before attempting to perform any updates, testing, etc. Once you blast the data away it's gone forever.
My advice is based on my 8 years of experience with MOM and Dydacomp. If you are not comfortable with data manipulation then hire someone who is.
Ecommerce Operations Manager CVS Inc
[email protected]
mobile: 4168238175
DISCLAIMER: Always backup your MOMWIN folder before attempting to perform any updates, testing, etc. Once you blast the data away it's gone forever.
My advice is based on my 8 years of experience with MOM and Dydacomp. If you are not comfortable with data manipulation then hire someone who is.
#2
Posted 14 July 2005 - 06:40 AM
When updating a price level using "maintain stock item" you are given a choice when saving whether you want to retain original pricing for committed/back ordered items. In my experience choosing "no" will update both committed and backordered items, whereas choosing "yes" will retain all pricing.
When making changes thru dbuwin you are not given this choice and all pricing is changed.
Using 4.3 I have not had a problem with this. The only reasons I can think of why it would not update is if the price was manually changed within the order, or there is another parameter which is excluding your backorders (i.e. a date range).
When making changes thru dbuwin you are not given this choice and all pricing is changed.
Using 4.3 I have not had a problem with this. The only reasons I can think of why it would not update is if the price was manually changed within the order, or there is another parameter which is excluding your backorders (i.e. a date range).
#3
Posted 22 July 2005 - 10:50 AM
You don't say how you are doing the update. If you're writing to the table and you want those changes to be reflected on BOs you have to write into the items table where item status is BO.
n
n
#4
Posted 24 July 2005 - 03:35 AM
You don't say how you are doing the update. If you're writing to the table and you want those changes to be reflected on BOs you have to write into the items table where item status is BO.
n
Hi Notehead,
The method you describe is only partially accrate. If you use an outside program to update open items with cost you also need to consider the following:
ITEM.ITEM_STATE inlist
"PB" (partial backorder)
"HS" (line item on hold)
"CM" (comitted)
"PI" (Picked)
I was trying to use MOM's pricing update features to do this automatically but I had limited success.
Thanks notehead.
Cheers,
Videoflicks2004
David Narciso
Ecommerce Operations Manager CVS Inc
[email protected]
mobile: 4168238175
DISCLAIMER: Always backup your MOMWIN folder before attempting to perform any updates, testing, etc. Once you blast the data away it's gone forever.
My advice is based on my 8 years of experience with MOM and Dydacomp. If you are not comfortable with data manipulation then hire someone who is.
Ecommerce Operations Manager CVS Inc
[email protected]
mobile: 4168238175
DISCLAIMER: Always backup your MOMWIN folder before attempting to perform any updates, testing, etc. Once you blast the data away it's gone forever.
My advice is based on my 8 years of experience with MOM and Dydacomp. If you are not comfortable with data manipulation then hire someone who is.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users