on 08-30-2011 7:10 AM
Hi experts,
We are planning projects via material components to network activities.
Issue over here is initially few materials were having MAP value as
zero & those materials have been used for project planning.
So plan values were based on those zero values & plan value was not
100% correct.
Now we have updated material master with correct MAP value, but still
on S_ALR_87013533 report shows incorrect plan values for said project.
Is there way to update those projects with correct plan values without
reassigning materials to projects in order to reflect correct plan
values on S_ALR_87013533 report?
Beat regards,
SL
Why dont you re-run the network costing for those projects and check the report
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
please check for your network costing the key you maintained to pick up the material price what option you have selected ? is MAP option is maintained there ?
1 thing i wat to clarify that MAP is maintained at plant level and for project when any material is assigned then that is restricetd for that project........ seniors please update this if i am wrong
regards,
Hi Pradeep,
Coting variant is standard (PS02) for network type parameters. 1st priority is Standard price(we are not defined on MM01)
2nd is Moving Average Price(MAP)
For the initial planning when material is assigned it picks the MAP value for that particulat plant which material component is attached.
In this case how SAP is behave is logical , that means planed value is based on MAP which is available at the point of planning.
Here our requirement is to mechanism to refresh that value with new MAP values as and when required.
Thanks & regards,
SL
Hi SL,
Please adjust your value category customizing according to the following
settings:
1) In transaction CJVC, all yellow and/or red lights have to eliminated
by assigning each cost element/commitment item/statistical key figure
according to the following rules:
1.1) Each cost element/commitment item/statistical key figure should
be assigned to a value category, EVEN if its values should NOT
be updated to table Project Information Database, table RPSCO.
In this case please create an assignment to a value category
and activate its 'suppress' indicator. All values basing on an
assignment to this value category won't be updated to RPSCO.
1.2) Each cost element/commitment item/stat. key figure has to be
assigned exactly once to a value category. Assigning them to
more or less than one value category will lead to unpredictable
results.
1.3) Only
1.3.1) cost elements of the same cost element type,
1.3.2) commitment items of the same item category and
1.3.3) statistical key figures of the same unit of measure
and the same KF category are allowed to be assigned to
one value category. Mixed assignments will lead to
unpredictable results, like mixing costs and revenues in
columns or rows.
2) If all yellow and/or red lights in transaction CJVC are eliminated,
please rebuild the Project Information Database (table RPSCO) by
transaction CJEN. Without this, changes from 1.1)-1.3) won't have
any effect.
3) Please rebuild the assigned values by transaction CJBN.
Could you also review notes 51971, 327081, 676123?
Best regards,
Enrique
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
please remove the materials from network and attach again, i think master data changes not yet influenced the attached materials.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
103 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.