value category customization - sapnote_0000676123

7/28/2019 Value Category Customization - Sapnote_0000676123

http://slidepdf.com/reader/full/value-category-customization-sapnote0000676123 1/4

14.07.2009 of 4

SAP Note 676123 - Project Information Database / ValueCategory Customizing

Note Language: English Version: 4 Validity: Valid Since 31.10.2003

Summary

Symptom

o You want to know more about the project information database, about

value categories and value category customizing.

o You want to know, why it is inevitable to maintain the value

category customizing correctly and completely.

o You do not know, why the value category customizing is necessary at

all.

o You want to know, what this customizing is for and why a support

consultant or developer has asked you to review/maintain your valuecategory customizing.

o You want to know which are the guiding priciples for value category

customizing.

More Terms

Project Information Database, CJEN, OPI1, OPI4, OPI5, RPSCO, RPSQT

Cause and Prerequisites

Solution

Project Information Database

The project information database - table RPSCO - is the value table

(no quantities!) that serves as common database for:

o Hierarchy Reports

o Structure Overview

o Progress Analysis (earned value)

o Project Planning Board.

It contains values from controlling (costs, revenues, commitment) and PS

cash management (expenses, receipts, cash commitment, planned payments

...).

For earned value analysis table RPSQT contains the necessary quantities.

The values in this table occur from statistical keyfigure records in

controlling.That way you can design hierarchy reports that are able to report on all

these values in one single report.



14.07.2009 of 4


For quantities in earned value analysis please use transaction CNE5 or in

releases 4.6* CNSE5. To enable hierarchy reports to deal with these values,

note 523330 must be implemented.

Not all values are updated to the project information database: Settlement

records to receivers other than WBS element, network, network activity or

project related order (with WBS element assignement) are not updated to the

project information database.

--> see also note 51971.

This is, because the values in the project information database are limited

to project values. Values that have left the project are not in focus

anymore.

Value category customizing

In the project information database the value category plays the role, that

cost elements, commitment items and statistical key figures have in the

controlling tables, report-writer reports / report painter reports and lineitem reports.

The value category customizing controls this re-keying process from the

controlling tables to the project information database. It is essential!

This customizing must be set up correctly and completely. Otherwiseyou will get unpredictably wrong values in the hierarchy reports,the structure overview, earned value analysis and in the project

planning board.

Please check now, if your customizing is complete and correct.

1. Please use transaction CJVC to check your value category customizing.

All red AND yellow lights shown there have to be eliminated by correcting and completing your value category customizing. In order to

do that, please review your customizing following these guidelines:

a) 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.

b) This is nessessary EVEN, IF YOU NEVER WANT TO SEE those values. Inthat case you can block the update to table RPSCO. To block the

update please create an assignment line to a value category and

activate the 'suppress' indicator on the assignment detail screen.

c) Only

- Cost elements of the same cost element type

- Commitment items of the same item category and

- Statistical key figures of the same unit of measure and the same

key figure category

are allowed to be assigned to the same value category. Other and/or

mixed assignments will lead to unpredictable results like mixing



14.07.2009 of 4


costs and revenues in columns or rows!

d) When you create the value categories, that replace the cost

element/commitment item/statistical key figure in the project

information database, check for the correct setting of the radio

button:

COSTS: for value categories meant to be used for cost elements of

type 1 ('costs'); for value categories meant to be used for

commitment items for expenses

REVENUES: for value categories meant to be used for cost elements

of type 11 or 12 ('revenues'); for value categories meant to be

used for commitment items for receipts.

If you want to assign STATISTICAL KEY FIGURES to the value

category, you indicate, whether the value category should contain

key figures with totals values characteristic or fixed values

characteristic.

These settings are valid for all cost elements/commitment

items/statistical key figures you assign to the value category.

2. If all red and yellow lights in transaction CJVC are eliminated,

please rebuild the Project Information Database (table RPSCO) by

transaction CJEN. Without this, changes carried out in your value

category customizing won't have any effect. That is necessary after

all changes in value category customizing, that affect values already

posted. Running CJEN is not dangerous.

3. Please rebuild the assigned values using transaction CJBN afterwards,

if you use budgeting.

4. Performance tip:

You can create more than one assignement line for one value category.

This is possible, because the assignment lines do not only contain the

controlling area and the value category but also a counter (1-999).

If you assign cost elements or cost element intervals to the value

category instead of cost element groups, you save the time, that

otherwise would be consumed for the explosion of the cost elementgroup.

For being able to do that easily, please consider the following:

Please use allways the same number of digits for all cost elements and

revenue elements - to have a reserve eventually 1 or two digits more

than you initially need. The field for cost element is an alphanumeric

field and is lexically sorted. If you do not do it that way, you will

have problems defining intervals. So please use the same number of

digits for all cost elements. The same is for commitment items and

statistical key figures.

This setup should be checked regularly to make sure, that all valuesare updated to the project information database in the correct way!



14.07.2009 of 4


There should be a special focus on newly created cost elements /commitment items / statistical key figures.

Header Data

Release Status: Released for Customer

Released on: 31.10.2003 14:39:00

Original Lang.: English

Priority: Recommendations/additional info

Category: Consulting

Main Component: PS-IS-ACC-HIE Hierarchy Reports

Additional Components:

PS-PRG Progress

PS-PRG-EVA Progress Analysis

CO-OM-OPA-C Budgeting

PS Project SystemPS-IS Information System

PS-IS-ACC Accounting

PS-IS-LOG Logistics

PS-ST-PPB Project Planning Board

PS-IS-LOG-STR Structure overview

The Note is release-independent

Related Notes

Number Short Text

668240 FAQ 2: Hierarchy reports

523330 PS-IS: Quantities in hierarchy reports

51971 Hierarchy reports: Displaying actual costs after settlement

value category customization - sapnote_0000676123

Documents