EHP6 for SAP ERP

6.0
April 2012
English

R&D with Project

Controlling (183)
Building Block Configuration Guide

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

Copyright

© 2012 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,
SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business
Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of
Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in
Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of
any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.

© SAP AG Page 3 of 12
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

Icons

Icon Meaning
Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.

Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.

© SAP AG Page 4 of 12
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

Content

1 Purpose................................................................................................................................... 5
2 Preparation.............................................................................................................................. 5
2.1 Prerequisites.................................................................................................................. 5
3 Configuration........................................................................................................................... 5
3.1 Project System.............................................................................................................. 5
3.1.1 Create Settlement Profile..........................................................................................5
3.1.2 Define Strategy for Determination of Settlement Rules.............................................7
3.1.3 Define Results Analysis Key......................................................................................8
3.1.4 Determine Strategy for Settlement Rule....................................................................8
3.1.5 Define Line IDs.......................................................................................................... 9
3.1.6 Define Assignments for Results Analysis................................................................10
3.1.7 Define Update for Results Analysis.........................................................................10
3.1.8 Check BOM Selection............................................................................................. 11

© SAP AG Page 5 of 12
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

R&D with Project Controlling

1 Purpose
This configuration guide provides the information you need to set up the configuration of this
building block manually.
If you do not want to configure manually and prefer an automated installation process using BC
Sets and other tools, refer to the Quick Guide..

2 Preparation
2.1 Prerequisites
Before you start installing this building block, you must install prerequisite building blocks. For
more information, see the Building Block Prerequisite Matrix (Prerequisites_Matrix_[xx]_[yy]_
[zz].xls; the placeholder [xx] depends on the SAP Best Practices version you use, e.g. BL refers
to the SAP Best Practices Baseline Package, [yy] depends on the language version, e.g. EN for
English language, and [zz] depends on the country version, e.g. FR for France:
Prerequisites_Matrix_BL_EN_FR.xls). This document can be found in the SAP Best Practices
documentation package in the folder ..\[xx]_[zz]\Documentation\; ([xx] depends on the SAP Best
Practices version and [zz] depends on the country version).

3 Configuration
3.1 Project System

3.1.1 Create Settlement Profile

Use
The settlement profile controls various parameters related to settlement.

Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Project system  Costs  Automatic and Periodic Allocations
 Settlement  Settlement Profile  Create Settlement Profile
2. Choose New Entries and enter header data. Then for each new entry choose Details and
enter remaining data.
3. Overview of data records:
Profile Text

© SAP AG Page 6 of 12
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

YBMFR0 R&D PS Settlement CO-PA

YBMFR1 R&D PS Settlement Variable

YBMFR0 YBMFR1
Actual Costs/Costs of Sales
To Be Settled in X X
Full
Can Be Settled
Not for Settlement
Default Values
Allocation YH YH
Structure
Source Structure
PA Transfer YH YH
Structure
Default object
Type
Indicators
100% Validation X X
%-Settlement X X
Equivalence No’s X X
Amount
Settlement
Var. to Co. bsd. X
PA
Valid Receivers
G/L Account N N
Cost Center N O
Order N O
WBS Element N O
Fixed Asset O O
Material N O
Network N N
Profit. Segment O O
Sales Order N O
Cost Objects N O
Order Item N O
Business Proc. N N

© SAP AG Page 7 of 12
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

Real Est. Object N N

Other Parameters
Document Type SA SA
Max. No. Dist.rls 3 999
Residence Time 3 3

Result
The settlement profiles are maintained.

3.1.2 Define Strategy for Determination of Settlement Rules

Use

Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Project system  Costs  Automatic and Periodic Allocations
 Settlement  Define Settlement Rule for Network  Define
Strategies for Determining Settlement Rules
2. On the Change View “Strategies for Settlement Rule”: Overview screen make the following
entries:
Field Name Description User Action and Values Comment
Strat. Strategy for determining a YH
settlement rule
Name R&D PS-Settlement
Typ 3
Typ 4
Typ <no entry>
Typ <no entry>
Typ <no entry>

Result
The strategy is maintained.

3.1.3 Define Results Analysis Key

Use

Procedure

© SAP AG Page 8 of 12
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

1. Access the activity using one of the following navigation options:

Transaction Code OKG1
IMG Menu Project system  Revenues and Earnings  Automatic and
Periodic Allocations  Results Analysis  Edit Results
Analysis Keys and Version  Maintain results analysis keys

2. On the Change View “Results Analysis Keys”: Overview screen select New Entries.
3. On the New Entries: Overview of Added Entries screen make the following entries:
Field Name Description User Action and Values Comment
RA key Results analysis key YBMFR1
Text R&D PS Settlement

Result
The results analysis key is added.

3.1.4 Determine Strategy for Settlement Rule

Use

Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Project system  Costs  Automatic and Periodic Allocations
 Settlement  Settlement Rule for Work Breakdown
Structure Element  Determine Strategy for Settlement Rule
2. On the Change View “Strategy”:Overview screen select New Entries.
3. On the New Entries: Overview of Added Entries screen make the following entries:
Field Name Description User Action and Values Comment
Strategy YH
Description Settlement Rule R&D WBS
4. Choose Save.
5. Select the line with strategy added and choose Settings.
6. On the Change View “Settings”: Overview screen select “New Entries.
7. On the New Entries:Overview of Added Entries screen make the following entries:
Field Name Line 1 Line 2
Billing no entry Select
AA ele Select no entry

© SAP AG Page 9 of 12
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

Field Name Line 1 Line 2

No ac No entry No entry
Settl.Proffil. YBMFR1 YBMFR1
AcctAssCat 1 1
N:1 SD-PS No entry No entry

8. Save your entries.

3.1.5 Define Line IDs

Use

Procedure
1. Access the activity using one of the following navigation options:
Transaction Code SPRO
IMG Menu Project system  Revenues and Earnings  Automatic and
Periodic Allocations  Results Analysis  Edit Results
Analysis Keys and Version  Define line IDs
2. On the Change View “Line IDs for Results Analysis or WIP Calculation”: Overview screen,
check or add following entries:
Field Name Entry 1 Entry 2 Entry 3
CO Area 1000 1000 1000
Line ID COP COS REV
Name Primary Secondary Revenues
Costs Costs

Result
The line IDs are maintained.

3.1.6 Define Assignments for Results Analysis

Use

Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OKG5
IMG Menu Project system  Revenues and Earnings  Automatic and
Periodic Allocations  Results Analysis  Edit Results

© SAP AG Page 10 of 12
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

Analysis Keys and Version  Define assignments for results

analysis
2. Choose New Entries and provide the following data:

Overview of data records:

CoArea 1000 1000 1000 1000

RA Version 0 0 0
0
RA Key YBMFR1 YBMFR1 YBMFR1 YBMFR1
Masked CoEl 000050++++ 0000521000 000060++++ 00009+++++
Origin ++++ ++++ ++++ ++++
Masked CC
Masked AT
Bus Proc.
D/C Ind. + + + +
Vble/Fix Ind. + + + +
App. Reason
Acc Ind. ++ ++ ++ ++
Val-from Per. 001.2007 001.2007 001.2007 001.2007
Rec. To Cap. REV COP COS REV

3.1.7 Define Update for Results Analysis

Use
For each line ID a cost element, under which RA is performed, is assigned.

Prerequisites
RA Versions, Cost Elements, Line IDs

Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OKG4
IMG Menu Project system  Revenues and Earnings  Automatic and
Periodic Allocations  Results Analysis  Edit Results
Analysis Keys and Version  Define Update for Results
Analysis

© SAP AG Page 11 of 12
SAP Best Practices R&D with Project Controlling (183): Configuration Guide

2. Choose New Entries and enter data.

3. Overview of data records:
Creation
Co Area Vers. RA Key LID Cat UM
WIP Reserves
1000 0 YBMFR1 COS K 931130 931140

1000 0 YBMFR1 COP K 931110 931120

3.1.8 Check BOM Selection

Use
For each line ID a cost element, under which RA is performed, is assigned.

Prerequisites
RA Versions, Cost Elements, Line IDs

Procedure
1. Access the activity using one of the following navigation options:
Transaction Code OPJI
IMG Menu Controlling  Product Cost Controlling  Product Cost
Planning  Material Cost Estimate with Quantity Structure
Settings for Quantity Structure ControlBOM Selection 
Check BOM selection
2. Check following entries:

SellD SelPr BOM Usage

05 4 2

© SAP AG Page 12 of 12