clmates
Reputable Poster
Hi
I want to know if any of you is using configurated items and advanced pricing in XE.
We are using this since 2003 and had a few annoying SR opened since 2007 that Oracle are unwilling to solve, to be more precise they have tried to solve and get from SR to SR again and again fixing one thing and breaking another due to their incompetency at development and testing, because they don't make coherent functional testing, but only the exact thing reported, so they don't notice that by fixing that they broke another piece related to this process.
If you are using this, how you resolve changes in promised dates of SO when WO has passed cut off status?
ie: think in this situation.
1. you place a new Sales Order for a customer with a configurated item and a promised date, also you make some manual adjustments to the price like a special discount.
2. you begin production and manufacturing notices he will have a delay and could not be on time, so inform you the new date he will be able to finish. (and adjust this in their WO)
3. You inform the customer, he agree in the new date and then you go to the SO to adjust promised date to the new one so your system is informed and other affected departments like shipping is informed.
What we used to do here (since 2003) is edit SO details, change line dates => the configurator Screen pop ups. As we dont want to change configuration nor price,n nor anything related to product only want to change dates, then we Cancel the configuration. So the system returns to the detail line dates are changed but any other information like price, manual adjustments, attachments, is kept. then we save the SO pressing OK. Also the WO is not affected because it has passed cut off status. (we don't use change status in P48013)
Now the Oracle guys tell us that this is not an accepted operation, that we need to always recalculate the product and accept the configuration screen, but this is erasing price history, attachments, and in some cases changing the configuration of the product due to this new date being for example on different year or due to a change in manufacturing specifications. And we should not change the product or the price as this is already and accepted SO for our customer.
So in conclusion, how you handle date changes in configured sales orders?
Sorry for the long post, but I'm a bit annoyed with this.
Thanks in advance
I want to know if any of you is using configurated items and advanced pricing in XE.
We are using this since 2003 and had a few annoying SR opened since 2007 that Oracle are unwilling to solve, to be more precise they have tried to solve and get from SR to SR again and again fixing one thing and breaking another due to their incompetency at development and testing, because they don't make coherent functional testing, but only the exact thing reported, so they don't notice that by fixing that they broke another piece related to this process.
If you are using this, how you resolve changes in promised dates of SO when WO has passed cut off status?
ie: think in this situation.
1. you place a new Sales Order for a customer with a configurated item and a promised date, also you make some manual adjustments to the price like a special discount.
2. you begin production and manufacturing notices he will have a delay and could not be on time, so inform you the new date he will be able to finish. (and adjust this in their WO)
3. You inform the customer, he agree in the new date and then you go to the SO to adjust promised date to the new one so your system is informed and other affected departments like shipping is informed.
What we used to do here (since 2003) is edit SO details, change line dates => the configurator Screen pop ups. As we dont want to change configuration nor price,n nor anything related to product only want to change dates, then we Cancel the configuration. So the system returns to the detail line dates are changed but any other information like price, manual adjustments, attachments, is kept. then we save the SO pressing OK. Also the WO is not affected because it has passed cut off status. (we don't use change status in P48013)
Now the Oracle guys tell us that this is not an accepted operation, that we need to always recalculate the product and accept the configuration screen, but this is erasing price history, attachments, and in some cases changing the configuration of the product due to this new date being for example on different year or due to a change in manufacturing specifications. And we should not change the product or the price as this is already and accepted SO for our customer.
So in conclusion, how you handle date changes in configured sales orders?
Sorry for the long post, but I'm a bit annoyed with this.
Thanks in advance
