on 12-11-2009 10:28 AM
Hi all, for one particular project,there is an error in the s_alr_87013558 report.The actual costs for the Sub-level WBS is coming correctly.But for the first level WBS element,the actual cost is less than the sum of the lower level WBS.I checked in CJI3 reports the,costs for the 1st level WBS is coming correctly.What could be the possible reason behind this error?What are the PS tables from where we can get the costs for the WBS elements? Can you name some so that i can check.Or the steps for rectification of the reports.
Hello ChiraId,
You are comparing data using two different types of reports u2013 CJI3 is a line item report (table COVJ) while S_ALR_87013558 is based on table RPSCO. Data from line item tables 'rolls up' into RPSCO.
If the outputs from S_ALR_87013558 are incorrect, then you should run transaction CJEN, as advised by other contributors.
In addition, report RKACSHOW will check the contents of CO tables, including RPSCO (note 28145). You could also use transaction BEBD to carry out an analysis of temporary RPSCO changes within the report (note 83191).
Regards,
Damien.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chirald,
Normally this inconsistency happens in table RPSCO. There are a few
suggestions I can provide to you:
(A) 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.
(B) Please review also notes 51971, 327081, 676123.
(C) You can run transaction RKACSHOW for the affected WBS and check
the tables there.
Thanks a lot and kind regards,
Enrique Sosa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
PROJ ( Project master data) and PRPS ( WBS eleement master data).
the transaction get stored in the below tables :
COSP Cost totals for external postings
COSS Cost totals for internal postings
COSB Total variances/result analysis
COEP Line items, actuals
COOI Line items, commitments
COEJ Line items, planned orders
COEPD - budget for the project
hope this helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This report is a combination of multiple tables and data is pulled from multiple from different tables. hence it is difficult to tell that one single table is the source of the entire data pulled by the report.
I would suggest you to try running CJEN - which will actual reconstruct the project data and CJBN - reconstruct availability control.
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.