on 08-13-2010 12:54 PM
Hi Guys,
When fix the cell in the planning book, getting "One or more cells could not be completely fixed" message.
1. If a material having only one CVC in the MPOS those quantity can be fixed correctly without any issues.
2. If a material having more than 1 CVC combination and try to fix one of the CVC combination quantity, it is fixing partially and getting the above message.
3. Even, it is not allowing to fix the quantity in aggregate level also.
We are in SCM 7.0.
Is there precondition that need to fix the material having only one CVC combination.
Even a material having multiple CVC combination why it is not allowing to fix one CVC combination in detail level.
Is aggregate level key figure fixing is not allowed ?
Please clarify.
Thanks
Saravanan V
and when zero value fixed option is not selected, there also partially fixing occurred.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This may help, got below details through raised OSS message,
IS_FIXED Function needs to be used to validate the cell value in macro when copying values from other keyfigure to fixed values having key figure.
When fixing for example if a material having 10 CVC and fixed at material level, given values should not be less than number of CVC of material, otherwise ti will lock partially.
During fixing first the given value disaggregated base on time bucket in Storage bucket profile lowest level and the spilit to CVC level.
Regards,
Saravanan V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mani Suresh,
Thanks a lot for your reply. And finally one more. We are fixing cells of a key figure A and then run a copy job to copy key figure B value to A. After the copy job all fixing locks removed and values also overwritten with new value.
Do we need to use the IS_FIXED function validation in the copy macro.
Will the fixing stable if we use the /TSCOPY transaction copy.
Hope will get the reply soon.
Thanks,
Saravanan V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mani Suresh,
Thanks for your clear and useful reply.
One more clarification. Where we can see the custom info object is BW KF or APO key figure.
Thanks,
Saravanan V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
While creating an infoobject, it asks if you want it to be a APO or BW infoobject. However after creating it doesnt show up explicitly as APO or BW.
However if you go to txn RSA1, Navigate to your infoobject Key Figure. double click on that. There will be 3 tabs. In the tab "Type/Unit" if you see a section Fixed Key Figure at the bottom, then it is a APO KF if not it is a BW KF.
Hope this helps.
Thanks
Mani Suresh
Hi,
One more clarification, currently the fixable key figure and key figure assigned to the fixable both are custom info objects.
Not APO Key figure. Is it must to assign the APO key figure for fixing and wouldn't work for customer key figures.
Thanks in advance.
Regards,
Saravanan V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
It is not mandatory to assign Standard KF to be able to fix. However your custom infoobject that you created must be of type APO KF and not BW KF.
That said, Let us try and address your first problem.
You can fix at an aggregate level. However there a few points to remember.
Let us consider a couple of scenarios.
1) In your selection id, it is showing a number of products. You are selecting all the products at one go and load the data and try to fix at this level. This is not possible.
2) In your selection id, you have selected a product division. For a single product division you are loading data and try to fix at this level. This is the true aggregate level and it should be possible at this level.
Hope this helps.
Thanks
Mani Suresh
User | Count |
---|---|
11 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.