Download Configuring SAP® ERP Financials and Controlling PDF

TitleConfiguring SAP® ERP Financials and Controlling
Tags
LanguageEnglish
File Size24.8 MB
Total Pages948
Document Text Contents
Page 1

Configuring SAP® ERP
Financials and Controlling

Page 2

Configuring SAP®
ERP Financials

and Controlling
Peter Jones
John Burger

Page 474

4 5 8 C H A P T E R 1 0 C O S T C E N T E R A C C O U N T I N G

F I G U R E 10 . 8 The completed change view “EC-PCA: controlling area settings”: overview screen

Profit Center Accounting: Creating the Standard Hierarchy

The method for creating and maintaining the PCA standard hierarchy is identi-

cal to the processes involved in upkeep of the CCA hierarchy. The keystrokes and

movements for adding, moving, and deleting nodes are the same for both hierar-

chies. Just as there is one CCA standard hierarchy, there is only one PCA standard

hierarchy.

Another similarity is that you can create or maintain the PCA hierarchy from either

the IMG or the user menu. The IMG menu path is Enterprise Controlling Profit

Center Accounting Master Data Profit Center Define Standard Hierarchy,

and the transaction code is KCH1. Transaction code KCH2 takes you to the change

screen for the standard hierarchy and also the Profit Center Group hierarchy change

screen.

Please refer to “Changing, Moving, and Deleting Hierarchy Nodes” earlier in this

chapter for tips on how to maintain hierarchy nodes.

Page 475

C O N T R O L L I N G A R E A / P R O F I T C E N T E R A C C O U N T I N G M A I N T E N A N C E 4 5 9

Creating the Dummy Profit Center

You create the dummy profit center by using a special transaction code (KE59).

Although it shares many of the same attributes as a normal profit center, the indi-

cator flag identifying it as the dummy can be activated only by using either this

special transaction code or the menu path Enterprise Controlling Profit Center

Accounting Master Data Profit Center Create Dummy Profit Center.

A window will appear asking whether you want to create the dummy or change a

profit center. Select the Create the Dummy Profit Center option. The initial create

dummy profit center screen appears. Enter the name of the dummy, and press Enter.

The create dummy profit center: basic screen configuration screen appears.

Notice that the Valid From and Valid To dates have defaulted into the master

record. Because there is only one dummy profit center, the valid dates must cover

the entire existence of the active system. Complete the remaining open fields:

Name Enter the name of the dummy profit center.

Description Enter a description of the dummy profit center.

Person Responsible Enter the name of the individual assigned the responsibility

of managing the dummy.

Department Enter the name or a description of the department to which the

person in charge belongs, if desired.

Profit Center Group Enter the node ID on the PCA standard hierarchy where

the dummy is to be assigned.

Segment This is an additional assignment of a value to the attributes of a dummy

profit center if further detailed reporting is required. This field has been added to

the profit center master record to provide financial segment reporting to meet the

new accounting standards. It is used in conjunction with the new general ledger.

When the fields are filled in, save the master record. The dummy is now active, as

shown in Figure 10.9, and postings can begin to occur within PCA.

EXTREME SPORTS PROFIT CENTER ACCOUNTING MAINTENANCE
CONFIGURATION ANALYSIS

Extreme Sports is using Profit Center Accounting to capture and report its profitability

by division. Therefore, because it is active within the controlling area, the profit center

standard hierarchy was developed and a dummy profit center was created.

Page 947

U S E R � E X I T C H A R A C T E R I S T I C D E R I V A T I O N � V O I D R E A S O N C O D E S 9 3 3

user-exit characteristic derivation,
688–689

user-exit program, 81–82
user exits, 27
user IDs

assigning personalized menu to, 5
tolerance group assignment, 156,

158
user menus, 5, 7
User Name field, for budget manager,

602
user profile, parameter ID storage in, 5
user status, defining in general status

management, 616–619
User Status screen, 617–619, 618

V
Val. Fld Var Cst field, for cost center to

CO-PA assessment, 701
ValA field, for detail per business area,

549
Valid From field, for batch input session

to create cost elements, 398
Valid From/To field

for activity type, 486
for cost centers, 465
for costing sheet assignment, 418
for imputed costs, 421
for secondary cost element, 405
for surcharge percentages, 420

Valid To field
for batch input session to create cost

elements, 399
for credit calculation, 422

Validation �® Simulate or Substitution
�® Simulate, 84

Validation Modif. indicator, for posting
procedures rules, 134

Validation Name field, 62
validations, 61–67, 62, 81

activation, 66–67, 67
message classes, 81
testing, 84–86
transporting, 86, 86–87

ValidFrom field, for currency exchange
rates, 289

Validity (Days) field, for credit rating
procedure, 319

Validity in Days field, for credit
segment, 318

validity period, of cost element vs.
activity type, 490

Valuation Class indicator, for posting
procedures rules, 134

Valuation field, for leading ledger, 335

valuation grouping codes, 134
Valuation View field

for controlling area, 755
for profit center, 457

ValuationArea: Table/Fld field, for
organizational level, 845

Value Date field
for fiscal year version, 386
for version parameters, 389

value dates, for payment methods, 207,
207–208, 208

value field catalog, 668
value fields, 575

assigning values to, 689–702
mapping SD condition types to,

690–694
configuration screen for resetting,

693
cost element/cost element group

and, 697
of operating concern, 645

creating, 662–668
Value Fields from Op. (Operating)

Concern option, for value fields,
663

value fields pop-up screen, listing of
elements, 731

Value Fld (Field) field, for value
assignments, 699

Value Origin field, for statistical key
figure, 481

Value: Table/Field field, for
organizational level, 845

value types, for tagging CO transaction,
443

variable portions, for allocation
amount, 504

variables
for layout column, 529
in layouts, 524
local, or global, 736–737
in report forms, 728

defining, 740
using programs in, 737

variance analysis, for activity
allocation, 491

Variance column in report, creating,
734

Variances field, for control indicators,
370

Variances to Costing-Based PA field, for
order settlement, 580

Variant Attributes save screen, 399,
399–400

Variant Attributes screen, 864, 865,
865, 867

Variant field
for flow definition, 871
for posting period variant, 40

Variant for TP field
for planned data transfer, 788
for version parameters, 390

Variant-Variable Parameters field, for
organizational level, 844

Variant-Variable Sel. Opt. field, for
organizational level, 844–845

variants, 4
in FI Closing Cockpit

creating, 862
use, 838–841

Variants: Change Screen Assignment
dialog box, 864, 864

VAT Registration No. field, for company
code, 48

vendor account groups, assigning
number ranges to, 217–219, 218

Vendor field, for customer-group field
status, 269

vendor groups, 211–222
configuration screen for assigning

number ranges, 220
field status, 213–216
initial configuration screen, 212
new entries screen, 212, 213

Vendor indicator, for terms of payment,
228

vendor master data, 211–222
creating, 221–222

version
parameters for fiscal year, 384–387
of postings, in allocation process,

502
version control, 515–518

planning, 588–589
Version field

for copy planning, 517
for imputed costs, 417

version field, for planning external data
transfer, 707

Version for Ind. Act. All. (IAA) field
for fiscal year version, 387
and order planning, 588

Version Locked field
for fiscal year version, 386
for version parameters, 389

version parameters, Profit Center
Accounting, 388–390

view V_GB01C, 84
views of tables, 17
void reason codes, 179–182

configuration screen, 181

Page 948

9 3 4 W / H O L D I N G T A X D A T A W / H T A X 2 F I E L D – Z I P C O D E S

W
W/holding Tax Data w/h Tax2 field, for

customer-group field status, 272
Warning field, for status profile, 623
warning, triggered by budget limits, 600
WBS elements, in Investment

Management, 804, 805, 813
“what-if” analysis, 518
whole table transport, potential

problems, 124

Workflow Variant field, for company
code, 50

working days, vs. non-working days, for
interest run program, 235

worklist, for flow definition, 857

X
XXL (Spreadsheet) option, for report

display, 743

Y
Year-Dependent field, for fiscal year

variant configuration, 38
Year field, for number range

configuration, 161
Year Shift field, for periods screen, 40

Z
zip codes, functionality for selecting

bank from, 209

Similer Documents