I have seen gold contributors like Ajay Maheshwari saying Price Variance should not be a cost
element.
I am new to controlling & trying to clean up after the implementation team, so please
help.
Requirement: Price Variance needs to hit Copa. Not any
other cost object.
Issues with Current config:
- Price Variance is a cost element – hence needs a cost object
- There are OKB9 settings, that default the CC – Client is not
happy with the defaults – they want price variance to act just like GRIR -
determine the CC, PC & segment based on material master.
- Price variance is not configured to flow into COPA at all
I have a chance to redo this & would like to do it right – what are the recomendations.
My questions:
- If Price Variance is not a cost element how does the value flow into COPA?
- Mapping MM pricing condition to copa value field - is that only relevant for IS retail? Can I do
that?
- Should I create a new GL acct? Expiring the existing cost
element – what are the implications
- Why doesn’t the price variance determine the CC, PC & segment based on material master like GRIR?
Why were the OKB9 defaults set?