Info Cubes

Business Content
Documentation of
InfoCubes and
Queries
Business Information
Warehouse 1.2B
July 1999
InfoObjects, InfoSources, InfoCubes, and Queries are subject to
change without prior notice.
SAP AG
Neurottstr. 16
D-69190 Walldorf
July 1999 Documentation of InfoCubes and Queries BW 1.2B
Page 2
Copyright 1999 by SAP AG. All rights reserved.
This document may not be distributed or reproduced in whole or in part for any purpose or in any form what-
soever without the express written permission of SAP AG.
SAP AG reserves the right to amend or supplement any or all of the information in this document without
prior notice.
Page 3
Content
1 Accounting................................................................................................................... 12
1.1 FI FinanciaI Accounting .......................................................................................................................... 12
1.1.1 FI-AR Accounts Receivable................................................................................................................... 12
1.1.1.1 InfoCube: 0FIAR_C01 - FIAR: Line items ..................................................................................... 12
1.1.1.2 InfoCube: 0FIAR_C02 FIAR: Summary Values ............................................................................ 14
1.1.1.2.1 Query: 0FIAR_C02_Q0001 Accounts Receivable: DSO Analysis, current period..................... 15
1.1.2 FI-AP Accounts Payable........................................................................................................................ 15
1.1.2.1 InfoCube: 0FIAP_C01 - FIAP: Line items...................................................................................... 15
1.1.2.2 InfoCube: 0FIAP_C02 - FIAP: Summary Values........................................................................... 17
1.1.2.2.1 Query: 0FIAP_C02_Q0001 Accounts Payable: Overview (Summary Values) .......................... 18
1.1.3 FI-AA Asset Accounting......................................................................................................................... 19
1.1.3.1 InfoCube: 0FIAA_C01: Annual Values .......................................................................................... 19
1.1.3.1.1 Query: 0FIAA_C01_Q001 Asset List............................................................................................. 21
1.1.3.1.2 Query: 0FIAA_C01_Q002 Value Comparison Between Depreciation Areas................................ 22
1.1.3.2 InfoCube: 0FIAA_C02: Period Values........................................................................................... 23
1.1.3.3 InfoCube: 0FIAA_C03: Transactions............................................................................................. 24
1.1.3.3.1 Query: 0FIAA_C03_Q001 Asset Acquisitions............................................................................... 26
1.1.3.3.2 Query: 0FIAA_C03_Q002 Asset Acquisitions on Quarterly Basis ................................................ 27
1.1.3.4 InfoCube: 0FIAA_C04: Annual Values and Transactions ............................................................. 28
1.1.3.4.1 Query: 0FIAA_C04_Q001 Asset History Sheet (for APC) ............................................................ 31
1.1.3.4.2 Query: 0FIAA_C04_Q002 Asset History Sheet (for Depreciation)................................................ 31
1.2 TR Treasury .............................................................................................................................................. 33
1.2.1 TR-CM Cash Management.................................................................................................................... 33
1.2.1.1 InfoCube: 0TR_CM_C01: Planned Amounts ................................................................................ 33
1.2.1.1.1 Query: 0TR-CM-TFS-1 Cash Position by Day / Currency............................................................. 34
1.2.1.1.2 Query: 0TR-CM-TFS-2 Cash Position by Currency / Day............................................................. 34
1.2.1.1.3 Query: 0TR-CM-LIQ-1 Liquidity Forecast by Day / Currency........................................................ 35
1.2.1.1.4 Query: 0TR-CM-LIQ-2 Liquidity Forecast by Currency / Day........................................................ 35
1.2.1.1.5 Query: 0TR-CM-1 Planned Amount by Day / Currency ................................................................ 36
1.2.1.1.6 Query: 0TR-CM-2 Planned Amount by Currency / Day ................................................................ 36
1.3 CO ControIIing.......................................................................................................................................... 38
1.3.1 CO-OM Overhead Cost Controlling....................................................................................................... 38
1.3.1.1 Infocube: 0COOM_C01: Costs and Allocations ............................................................................ 38
1.3.1.1.1 Query: 0COOM_C01_Q0001: Cost Center: Orders Plan/Actual/Variance................................... 39
1.3.2 CO-OM-CCA Cost Center Accounting................................................................................................... 40
1.3.2.1 Infocube: 0CCA_C01: Costs and Allocations (Full Costs) ............................................................ 40
1.3.2.1.1 Query: 0CCA_C01_Q0005: Cost center: Plan/Actual/Variance.................................................... 42
1.3.2.1.2 Query: 0CCA_C01_Q0001: Cost center: Plan/Actual/Variance current/cumulated Period.......... 42
1.3.2.2 Infocube: 0CCA_C02: Costs and Allocations (Marginal Costs) .................................................... 43
1.3.2.2.1 Query: 0CCA_C02_Q0003: Cost center: Target/Actual/Variance ................................................ 45
1.3.2.3 Infocube: 0CCA_C03: Statistical Key figures................................................................................ 46
1.3.2.3.1 Query: 0CCA_C03_Q0001: Cost center: Statistical Key figures Plan/Actual/ Variance............... 47
1.3.3 CO-OM-ABC Activity-Based Costing..................................................................................................... 48
1.3.3.1 InfoCube: 0ABC_C01, Activity-Based Costing (Costs and Quantities)......................................... 48
1.3.3.1.1 Query: 0ABC_C01_Q0001: Processes: Target Costs, Actual Costs, Cost Differences ............... 50
1.3.3.1.2 Query: 0ABC_C01_Q0002: Process Efficiency ............................................................................ 50
1.3.3.2 InfoCube: 0ABC_C02, Activity-Based Costing (Statistical Key Figures) ...................................... 51
Page 4
1.3.3.2.1 Query: 0ABC_C02_Q0001: Processes: Statistical Key Figures ................................................... 52
1.3.3.3 InfoCube: 0ABC_C03, Activity-Based Costing (Primary Cost Component Split).......................... 53
1.3.3.3.1 Query: 0ABC_C03_Q0001: Primary Cost Component Split ......................................................... 54
1.3.3.4 InfoCube: 0ABC_C04, Activity-Based Costing (Variances) .......................................................... 55
1.3.3.4.1 Query: 0ABC_C04_Q0001: Process Variances............................................................................ 57
1.3.3.5 InfoCube: 0ABC_C13, Activity Allocation (Primary Cost Component Split).................................. 58
1.3.3.5.1 Query: 0ABC_C13_Q0001: Primary Cost Component Split ......................................................... 59
1.3.3.6 InfoCube: 0ABC_C14, Activity Allocation (Variances) .................................................................. 60
1.3.3.6.1 Query: 0ABC_C14_Q001: Cost Center Variances........................................................................ 61
1.3.3.7 InfoCube: 0ABC_C15, Activity Allocation (Costs and Quantities)................................................. 62
1.3.3.7.1 Query: 0ABC_C05_Q0001: Cost Centers/Activity Types: Target Costs, Actual Costs, Cost
Differences................................................................................................................................... 64
1.3.3.7.2 Query: 0ABC_C05_Q0002: Cost Center Efficiency...................................................................... 64
1.3.4 CO-OM-OPA Overhead Cost Orders .................................................................................................... 65
1.3.4.1 Infocube: 0OPA_C01: Costs and Allocations................................................................................ 65
1.3.4.1.1 Query: 0OPA_C01_Q0005: Orders: Budget/Commitment/Actual/Allotted ................................... 67
1.3.4.1.2 Query: 0OPA_C01_Q0006: Orders: Plan/Actual/Variance........................................................... 67
1.3.4.1.3 Query: 0OPA_C01_Q0022: Orders: Overall Plan/Commitment/Actual/Allotted ........................... 68
1.3.4.2 Infocube: 0OPA_C02: Statistical Key Figures............................................................................... 69
1.3.4.2.1 Query: 0OPA_C02_Q0001: Orders: Statistical Key figures Plan/Actual/Variance ....................... 70
1.3.5 CO-OM-PRO Overhead Cost Projects .................................................................................................. 71
1.3.5.1 Infocube: 0WBS_C01: Costs and Allocations ............................................................................... 71
1.3.5.1.1 Query: 0WBS_C01_Q0002: WBS Element: Budget/Commitment/Actual/Available..................... 72
1.3.5.1.2 Query: 0WBS_C01_Q0001: WBS Element: Plan/Actual/Variance............................................... 73
1.3.5.2 Infocube: 0WBS_C02: Statistical Key Figures .............................................................................. 74
1.3.5.2.1 Query: 0WBS_C02_Q0001: WBS Element: Statistical Key Figures, Plan/Actual/ Variance........ 75
1.3.6 CO-PC Product Cost Controlling ........................................................................................................... 76
1.3.6.1 InfoCube: 0PC_01: Transaction data............................................................................................ 76
1.3.6.1.1 Query: 0PC_C01_Q0001: Target Costs, Actual Costs, Cost Differences .................................... 78
1.3.6.1.2 Query: 0PC_C01_Q0002: Costs for Output Quantities................................................................. 79
1.3.6.1.3 Query: 0PC_C01_Q0003: Production Variance............................................................................ 79
1.3.6.2 InfoCube: 0COPC_02: Actual Costing/Material Ledger ................................................................ 80
1.4 IM Investment Management .................................................................................................................... 83
1.4.1 IM-FA Capital Investments .................................................................................................................... 83
1.4.1.1 InfoCube: 0IMFA_1: Assigned Plan Budget.................................................................................. 83
1.4.1.1.1 Query: 0IMFA_C01_Q001: Plan for investment program and measures ..................................... 87
1.4.1.1.2 Query: 0IMFA_C01_Q002: Budget for investment program and measures................................. 88
1.4.1.1.3 Query: 0IMFA_C01_Q003: Available plan .................................................................................... 89
1.4.1.1.4 Query: 0IMFA_C01_Q004: Available budget ................................................................................ 89
1.5 EC Enterprise ControIIing....................................................................................................................... 91
1.5.1 EC-PCA Profit Center Accounting ......................................................................................................... 91
1.5.1.1 InfoCube: 0PCA_C01: PCA Transaction data............................................................................... 91
1.5.1.1.1 Query: 0PCA_C01_Q0004: Plan/actual variance - profit and loss accounts................................ 92
1.5.1.1.2 Query: 0PCA_C01_Q0008: Plan/actual profit center comparison - result .................................... 93
1.5.1.1.3 Query: 0PCA_C01_Q0001: Plan version comparison - result ...................................................... 94
1.5.1.1.4 Query: 0PCA_C01_Q0003: Plan/actual period comparison - result ............................................. 95
1.5.1.1.5 Query: 0PCA_C01_Q0007: Current period/YTD/complete year - result....................................... 95
1.5.1.1.6 Query: 0PCA_C01_Q0005: Time comparison actual result.......................................................... 96
1.5.1.1.7 Query: 0PCA_C01_Q0006: Time comparison plan result ............................................................ 97
1.5.1.1.8 Query: 0PCA_C01_Q0012: Plan/actual/variance - balance sheet accounts................................ 98
Page 5
1.5.1.1.9 Query: 0PCA_C01_Q0009: Profit after capital costs .................................................................... 98
1.5.1.1.10 Query: 0PCA_C01_Q0010: Return on Investment...................................................................... 99
1.5.1.2 InfoCube: 0PCA_C02 PCA: Statistical key figures...................................................................... 100
1.5.1.2.1 Query: 0PCA_C02_Q0001: Statistical key figures...................................................................... 101
1.5.2 EC- CS Legal Consolidation................................................................................................................ 102
1.5.2.1 InfoCube: 0ECCS_C01: Transaction data .................................................................................. 102
1.5.2.1.1 Query: 0ECCS_C01_Q001: Current year with structure -% Balance sheet ............................... 104
1.5.2.1.2 Query: 0ECCS_C01_Q002: Previous year comparison with variance ....................................... 104
1.5.2.1.3 Query: 0ECCS_C01_Q003: Multi-year comparison.................................................................... 105
1.5.2.1.4 Query: 0ECCS_C01_Q004: Quarter comparison ....................................................................... 105
1.5.2.1.5 Query: 0ECCS_C01_Q005: Month comparison.......................................................................... 106
1.5.2.1.6 Query: 0ECCS_C01_Q006: Comparison local/group currency .................................................. 107
1.5.2.1.7 Query: 0ECCS_C01_Q007: Version comparison ....................................................................... 107
1.5.2.1.8 Query: 0ECCS_C01_Q008: Consolidation unit comparison....................................................... 108
1.5.2.1.9 Query: 0ECCS_C01_Q009: Consolidation group comparison ................................................... 108
1.5.2.1.10 Query: 0ECCS_C01_Q010: Consolidation unit/Consolidation group comparison.................... 109
1.5.2.1.11 Query: 0ECCS_C01_Q011: Development of Consolidated value (local valuation) .................. 109
1.5.2.1.12 Query: 0ECCS_C01_Q012: Sales by region............................................................................. 110
1.5.2.1.13 Query: 0ECCS_C01_Q013: I/S by functional area.................................................................... 110
1.5.2.1.14 Query: 0ECCS_C01_Q014: Asset history sheet ....................................................................... 111
2 Human Resources ..................................................................................................... 112
2.1 PA-PA PersonneI Administration......................................................................................................... 112
2.1.1 InfoCube: 0PA_C01: Headcount and Personnel Actions .................................................................... 112
2.1.1.1 Headcount/Personnel Structure .................................................................................................. 122
2.1.1.1.1 Query: 0PA_C01_Q001: Headcount/Change in Staffing Level................................................... 122
2.1.1.1.2 Query: 0PA_C01_Q012: Average Headcount............................................................................. 123
2.1.1.1.3 Query: 0PA_C01_Q021: Average Headcount (12 Months) ........................................................ 124
2.1.1.1.4 Query: 0PA_C01_Q011: Percentage Breakdown of Employees................................................ 125
2.1.1.1.5 Query: 0PA_C01_Q006: Employees Average Age.................................................................... 126
2.1.1.1.6 Query: 0PA_C01_Q020: Headcount: Part-Time/Full-Time Workers .......................................... 127
2.1.1.1.7 Query: 0PA_C01_Q019: Headcount According to Capacity Utilization Level ............................ 128
2.1.1.2 Headcount/Personnel Structure FTE .......................................................................................... 129
2.1.1.2.1 Query: 0PA_C01_Q013: Headcount FTE................................................................................... 129
2.1.1.2.2 Query: 0PA_C01_Q015: Percentage Breakdown of Headcount FTE ........................................ 130
2.1.1.2.3 Query: 0PA_C01_Q014: Average Headcount FTE..................................................................... 131
2.1.1.2.4 Query: 0PA_C01_Q016: Headcount/Headcount FTE Current Year ........................................... 132
2.1.1.3 Personnel Flow............................................................................................................................ 133
2.1.1.3.1 Query: 0PA_C01_Q002: Number of Personnel Actions ............................................................. 133
2.1.1.4 Entries.......................................................................................................................................... 134
2.1.1.4.1 Query: 0PA_C01_Q003: Number of Entries ............................................................................... 134
2.1.1.4.2 Query: 0PA_C01_Q010: Percentage Breakdown of Entries....................................................... 135
2.1.1.4.3 Query: 0PA_C01_Q022: Entry Rate ........................................................................................... 136
2.1.1.4.4 Query: 0PA_C01_Q005: Net Entry Rate..................................................................................... 137
2.1.1.4.5 Query: 0PA_C01_Q017: Number of Entries FTE........................................................................ 138
2.1.1.5 Leavers........................................................................................................................................ 139
2.1.1.5.1 Query: 0PA_C01_Q007: Number of Leavers.............................................................................. 139
2.1.1.5.2 Query: 0PA_C01_Q009: Percentage Breakdown of Leavers..................................................... 140
2.1.1.5.3 Query: 0PA_C01_Q023: Leaving Rate ....................................................................................... 141
2.1.1.5.4 Query: 0PA_C01_Q018: Number of Leavers FTE...................................................................... 142
Page 6
2.2 PA-RC Recruitment................................................................................................................................ 144
2.2.1 InfoCube: 0PARC_C01 Applications and Applicant Actions ............................................................... 144
2.2.1.1 Applications ................................................................................................................................. 150
2.2.1.1.1 Query: 0PARC_C01_Q002: Number of Applications with Master Data...................................... 150
2.2.1.1.2 Query: 0PARC_C01_Q008: Percentage Breakdown of Applications with Master Data............ 151
2.2.1.1.3 Query: 0PARC_C01_Q016: Average Number of Applications .................................................. 152
2.2.1.1.4 Query: 0PARC_C01_Q006 Ratio Applications to Applicants..................................................... 153
2.2.1.2 Applicants .................................................................................................................................... 154
2.2.1.2.1 Query: 0PARC_C01_Q003 Number of Applicants with Master Data.......................................... 154
2.2.1.2.2 Query: 0PARC_C01_Q015: Applicants Average Age................................................................ 155
2.2.1.2.3 Query: 0PARC_C01_Q007: Percentage Breakdown of Applicants with Master Data................ 156
2.2.1.2.4 Query: 0PARC_C01_Q017: Average Number of Applicants ...................................................... 157
2.2.1.3 Advertising................................................................................................................................... 158
2.2.1.3.1 Query: 0PARC_C01_Q004: Number of Applications in Response to Advertising...................... 158
2.2.1.3.2 Query: 0PARC_C01_Q005: Applications per Advertisement Showing Costs ............................ 159
2.2.1.3.3 Query: 0PARC_C01_Q009: Percentage Breakdown of Applications ......................................... 160
2.2.1.3.4 Query: 0PARC_C01_Q001: Unsolicited Applications and Applications in Response to
Advertisements .......................................................................................................................... 161
2.2.1.3.5 Query: 0PARC_C01_Q010: Unsolicited Applications Rate ........................................................ 162
2.2.1.4 Hires/Contracts Offered............................................................................................................... 163
2.2.1.4.1 Query: 0PARC_C01_Q011: Hires/Offers/Rejected Contracts .................................................... 163
2.2.1.4.2 Query: 0PARC_C01_Q012: Annual Comparison of Hires/Offers/Rejected Contracts ............... 164
2.2.1.4.3 Query: 0PARC_C01_Q013: Applicant Hiring Rate ..................................................................... 165
2.2.1.4.4 Query: 0PARC_C01_Q014: Take Up Rate for Job Offers.......................................................... 166
2.3 PT Time Management ............................................................................................................................ 169
2.3.1 InfoCube: 0PT_C01: Employee Times................................................................................................ 169
2.3.1.1 Employee Times.......................................................................................................................... 174
2.3.1.1.1 Query: 0PT_C01_Q001: Productivity Rate ................................................................................. 174
2.3.1.1.2 Query: 0PT_C01_Q002: Illness Rate.......................................................................................... 175
2.3.1.1.3 Query: 0PT_C01_Q003: Leave Per Planned.............................................................................. 176
2.3.1.1.4 Query: 0PT_C01_Q004: Overtime Rate ..................................................................................... 177
2.3.1.1.5 Query: 0PT_C01_Q005 Leave Taken for Effective Full-Time Employees.................................. 178
2.3.1.2 Employee Times Overview.......................................................................................................... 179
2.3.1.2.1 Query: 0PT_C01_Q011: Comparing Overview of Employee Times to Previous Year ............... 179
2.3.1.2.2 Query: 0PT_C01_Q012: Comparing Selected Employee Times and Debited Cost Centers to
Previous Year (Annual Comparison) ......................................................................................... 180
2.3.1.2.3 Query: 0PT_C01_Q013: Monthly View of Selected Employee Times ........................................ 181
2.3.1.2.4 Query: 0PT_C01_Q021 Employee Times Represented in Full-Time Employee Units............... 182
2.4 PY PayroII Accounting .......................................................................................................................... 184
2.4.1 InfoCube: 0PY_C02 Payroll Data ........................................................................................................ 184
2.4.1.1 Query: 0PY_ C02_Q001: Quarterly Wage Types Overview....................................................... 187
2.4.1.2 Query: 0PY_ C02_Q002: Annual Wage Types Overview........................................................... 188
2.4.1.3 Query: 0PY_ C02_Q003: Wage Types Overview for Germany.................................................. 189
2.4.1.4 Query: 0PY_ C02_Q004: Wage Types Overview USA............................................................... 191
2.4.1.5 Query: 0PY_ C02_Q005: Wage Types Comparison for Personnel Areas.................................. 192
2.5 PE Training and Event Management.................................................................................................... 194
2.5.1 InfoCube: 0PE_C01: Training and Event Management ...................................................................... 194
2.5.1.1 Attendance and Cancellation Evaluations................................................................................... 199
2.5.1.1.1 Query: 0PE_C01_Q001: Number of Attendances and Cancellations......................................... 199
2.5.1.1.2 Query: 0PE_C01_Q002: Annual Comparison of Bookings......................................................... 200
Page 7
2.5.1.1.3 Query: 0PE_C01_Q003: Attendance and Cancellation Rate...................................................... 201
2.5.1.1.4 Query: 0PE_C01_Q004: Business Event Duration..................................................................... 202
2.5.1.2 Evaluations of Business Event Fees ........................................................................................... 203
2.5.1.2.1 Query: 0PE_C01_Q005: Attendance and Cancellation Fees ..................................................... 203
2.5.1.2.2 Query: 0PE_C01_Q006: Fee Distribution by Internal and External Bookings............................ 204
2.5.1.2.3 Query: 0PE_C01_Q007: Fee Rates............................................................................................ 206
2.5.1.3 Evaluations of Organizers Sales and Costs ............................................................................... 207
2.5.1.3.1 Query: 0PE_C01_Q008: Annual Comparison of Revenues ....................................................... 207
2.5.1.3.2 Query: 0PE_C01_Q009: Annual Comparison of Business Event Costs .................................... 209
2.5.1.4 Evaluations of Employees ........................................................................................................... 210
2.5.1.4.1 Query: 0PE_C01_Q010: Training and Education Based on Organizational Assignment........... 210
2.5.1.4.2 Query: 0PE_C01_Q011: Training and Education Fees Based on Organizational Assignment.. 211
2.5.1.4.3 Query: 0PE_C01_Q012: Training and Education by Target Audience....................................... 213
2.5.1.4.4 Query: 0PE_C01_Q013: Training and Education Fees by Target Audience.............................. 215
2.5.2 Key figures........................................................................................................................................... 216
3 Logistics..................................................................................................................... 219
3.1 SD SaIes and Distribution..................................................................................................................... 219
3.1.1 InfoCube: 0SD_C01: Customer ........................................................................................................... 219
3.1.1.1 Query: 0SD_C01_Q010 Returns................................................................................................. 220
3.1.1.2 Query: 0SD_C01_Q011 Incoming Orders................................................................................... 221
3.1.1.3 Query: 0SD_C01_Q012 Credit Memos....................................................................................... 222
3.1.1.4 Query: 0SD_C01_Q013 Sales Volume....................................................................................... 223
3.1.1.5 Query: 0SD_C01_Q0001 Sales: Plan/actual/variance current year/previous year.................. 223
3.1.1.6 Query: 0SD_C01_Q0002 SD: Incoming orders/revenue: Months of current year ................... 224
3.1.1.7 Query: 0SD_C01_Q0003 SD: Returns: Quantities + values.................................................... 225
3.1.1.8 Query: 0SD_C01_Q021 Product Analysis .................................................................................. 225
3.1.1.9 0SD_C01_Q022 Analyses Product Profitability .......................................................................... 226
3.1.1.10 Query: 0SD_C01_Q023 Top Customer ...................................................................................... 227
3.1.1.11 Query: 0SD_C01_Q024 Analysis Incoming Orders .................................................................... 227
3.1.1.12 Query: 0SD_C01_Q025 Analysis Sales/Cost ............................................................................. 228
3.1.1.13 Query: 0SD_C01_Q026 Analysis Distribution Channel .............................................................. 228
3.1.2 InfoCube: 0SD_C02 - Deliveries.......................................................................................................... 229
3.1.2.1 Query: 0SD_C02_Q0001 Sales: weekly deliveries.................................................................. 230
3.1.3 InfoCube: 0SD_C03 Sales Overview................................................................................................... 231
3.1.3.1 Query: 0SD_C03_Q003 Returns................................................................................................. 235
3.1.3.2 Query: 0SD_C03_Q004 Incoming Orders................................................................................... 236
3.1.3.3 Query: 0SD_C03_Q005 Credit memos....................................................................................... 236
3.1.3.4 Query: 0SD_C03_Q006 Deliveries ............................................................................................. 237
3.1.3.5 Query: 0SD_C03_Q007 Billing Documents ................................................................................ 238
3.1.3.6 Query: 0SD_C03_Q008 Fulfillment Rates .................................................................................. 238
3.1.3.7 Query: 0SD_C03_Q009 Sales Values ........................................................................................ 239
3.1.3.8 Query: 0SD_C03_Q010 Order, Delivery and Sales Quantities................................................... 240
3.1.3.9 Query: 0SD_C03_Q011 Faultless Sales Order Processing........................................................ 240
3.2 MateriaIs Management .......................................................................................................................... 242
3.2.1 MM-IC Inventory Management ............................................................................................................ 242
3.2.1.1 Remarks on Filling Non-Cumulative InfoCubes .......................................................................... 242
3.2.1.1.1 Reference Day for Non-Cumulative Values in the OLTP and in the BW System....................... 242
3.2.1.1.2 Connecting Plant Non-Cumulatives to BW (InfoCube 0IC_C01) ................................................ 242
3.2.1.1.3 Connecting Warehouse Non-Cumulatives to BW (InfoCube 0IC_C02) ...................................... 244
Page 8
3.2.1.2 InfoCube: 0IC_C01 Goods Movements: Plant and Stocks ......................................................... 244
3.2.1.2.1 Query: 0IC_C01_Q0001 Warehouse Inventory Turnover........................................................... 246
3.2.1.2.2 Query: 0IC_C01_Q0002 Inventory Days of Supply - Quantity.................................................... 247
3.2.1.2.3 Query: 0IC_C01_Q0003 Inventory Days of Supply - Value........................................................ 248
3.2.1.2.4 Query: 0IC_C01_Q0004 Finished Goods Inventory Days of Supply - Quantity ......................... 248
3.2.1.2.5 Query: 0IC_C01_Q0005 Finished Goods Inventory Days of Supply - Value.............................. 249
3.2.1.2.6 Query: 0IC_C01_Q0006 Raw Material Days of Supply - Quantity.............................................. 249
3.2.1.2.7 Query: 0IC_C01_Q0007 Raw Material Days of Supply - Value.................................................. 250
3.2.1.2.8 Query: 0IC_C01_Q0008 Inventory Obsolete .............................................................................. 250
3.2.1.2.9 Query: 0IC_C01_Q0009 Inventory Aging.................................................................................... 251
3.2.1.2.10 Query: 0IC_C01_Q0010 Stock Values ...................................................................................... 251
3.2.1.2.11 Query: 0IC_C01_Q0011 Stock Quantity.................................................................................... 252
3.2.1.2.12 Query: 0IC_C01_Q0012 Material Consumption........................................................................ 253
3.2.1.2.13 Query: 0IC_C01_Q0013 Process Performance Measure ......................................................... 254
3.2.1.2.14 Query: 0IC_C01_Q0014 Consignment Stock Receipts vs Issues............................................. 255
3.2.1.2.15 Query: 0IC_C01_Q0015 Valuated Stock Receipts vs Issues.................................................... 255
3.2.1.3 InfoCube: 0IC_C02 Warehouse and Stocks ............................................................................... 256
3.2.2 MM-PUR Purchasing........................................................................................................................... 258
3.2.2.1 InfoCube: 0PUR_C01 Purchasing Data...................................................................................... 258
3.2.2.1.1 Query: 0PUR_C01_Q0001 Average Delivery Time -Vendor ...................................................... 261
3.2.2.1.2 Query: 0PUR_C01_Q0002 Service Level Vendor ...................................................................... 261
3.2.2.1.3 Query: 0PUR_C01_Q0003 - Fulfilment rate - Deliveries ........................................................... 262
3.2.2.1.4 Query: 0PUR_C01_Q0005 Average Delivery Time - Material .................................................... 263
3.2.2.1.5 Query: 0PUR_C01_Q0006 Purchasing values according to purchasing org. ............................ 263
3.2.2.1.6 Query: 0PUR_C01_Q0008 Delivery Quantity Variance.............................................................. 263
3.2.2.1.7 Query: 0PUR_C01_Q0009 Delivery Date Variance.................................................................... 265
3.2.2.1.8 Query: 0PUR_C01_Q0011 Order Quantities .............................................................................. 266
3.2.2.1.9 Query: 0PUR_C01_Q0012 Order Activities ................................................................................ 266
3.2.2.1.10 Query: 0PUR_C01_Q0013 Vendor Comparison re: Purchasing Values................................... 267
3.2.2.1.11 Query: 0PUR_C01_Q0014 Country Comparison Raw Materials Goods Receipt .................. 268
3.2.2.2 InfoCube: 0PUR_C02 Vendor Evaluation ................................................................................... 268
3.2.2.2.1 Query: 0PUR_C02_Q0022 Vendor Comparison with the Vendor Evaluation ............................ 270
3.2.2.3 InfoCube: 0PUR_C03 Subsequent Settlement Evaluation ...................................................... 271
3.2.2.4 InfoCube: 0PUR_C04 Purchasing Groups.................................................................................. 273
3.2.2.4.1 Query: 0MMPUR_C04_Q01 Purchasing Group Analysis ........................................................... 275
3.3 QM QuaIity Management ....................................................................................................................... 276
3.3.1 Quality Inspection ................................................................................................................................ 276
3.3.1.1 InfoCube: 0QM_C01 Inspection lot and usage decision............................................................. 276
3.3.1.1.1 Query: 0QM_C01/0QM_C01_Q001 Material analysis - Inspection lots...................................... 277
3.3.1.1.2 Query: 0QM_C01/0QM_C01_Q003 Vendor analysis - Inspection lots....................................... 278
3.3.2 Notifications ......................................................................................................................................... 279
3.3.2.1 InfoCube: 0QM_C02 Notifications............................................................................................... 279
3.3.2.1.1 Query: 0QM_C02/0QM_C02_Q001 Analysis of notifications - Quality Management................. 281
3.3.2.2 InfoCube: 0QM_C03 Notification items....................................................................................... 282
3.3.2.2.1 Query: 0QM_C03/0QM_C03_Q002 Analysis of nonconformities Notifications ....................... 285
3.4 PM PIant Maintenance and Service...................................................................................................... 286
3.4.1 Notifications ......................................................................................................................................... 286
3.4.1.1 InfoCube: 0QM_C02 Notifications............................................................................................... 286
3.4.1.1.1 Query: 0QM_C02/0QM_C02_Q002 Analysis of notifications Technical Objects..................... 288
3.4.1.2 InfoCube: 0QM_C03 Notification items....................................................................................... 289
Page 9
3.4.1.2.1 Query: 0QM_C03/0QM_C03_Q001 Analysis of damage codes Notifications......................... 291
3.5 Production PIanning and ControII........................................................................................................ 292
3.5.1 Process and Production Orders........................................................................................................... 292
3.5.1.1 InfoCube: 0PP_C01 Plan/Actual Comparison Order/ Material View........................................... 292
3.5.1.1.1 Query: 0PP_C01_Q001 Schedule and Scrap Deviation Order View.......................................... 296
3.5.1.1.2 Query: 0PP_C01_Q002 Schedule/Scrap Deviation Order View................................................. 297
3.5.1.1.3 Query: 0PP_C01_Q003 Total Schedule Deviation Order View.................................................. 297
3.5.1.1.4 Query: 0PP_C01_Q004 Detailed Order Release Deviations...................................................... 297
3.5.1.1.5 Query: 0PP_C01_Q005 Detailed Order Start Date Deviations................................................... 298
3.5.1.1.6 Query: 0PP_C01_Q006 Detailed Order Delivery Date Deviations ............................................. 299
3.5.1.1.7 Query: 0PP_C01_Q007 Total Schedule/Lead time Deviation Order View................................. 299
3.5.1.1.8 Query: 0PP_C01_Q008 Quantity/Scrap/Lead time Deviation Order View ................................. 300
3.5.1.1.9 Query: 0PP_C01_Q009 Negative/Positive Schedule Deviation Order View.............................. 300
3.5.1.1.10 Query: 0PP_C01_Q010 Order Quantity .................................................................................... 301
3.5.1.1.11 Query: 0PP_C01_Q020 Production Lead Time......................................................................... 301
3.5.1.1.12 Query: 0PP_C01_Q021 Scheduled Achievement ..................................................................... 301
3.5.1.2 InfoCube: 0PP_C02 To-the-period order / material view............................................................ 302
3.5.1.2.1 Query: 0PP_C02_Q001 Quantity of Goods Received and Scrap............................................... 303
3.5.1.3 InfoCube: 0PP_C03 Plan / actual comparison procedure / work center ..................................... 304
3.5.1.3.1 Query: 0PP_C03_Q001 Execution time and scrap variance: Work center view ........................ 307
3.5.1.3.2 Query: 0PP_C03_Q002 Lead time and relative schedule deviation: Work center ..................... 308
3.5.1.3.3 Query: 0PP_C03_Q003 Operation times detailed ...................................................................... 308
3.5.1.3.4 Query: 0PP_C03_Q004 Operation times.................................................................................... 309
3.5.1.3.5 Query: 0PP_C03_Q005 Schedule deviations Work center view ................................................ 309
3.5.1.3.6 Query: 0PP_C03_Q006 Schedule and quantity deviations Work center view............................ 310
3.5.1.3.7 Query: 0PP_C03_Q007 Capacity load utilization........................................................................ 310
3.5.1.3.8 Query: 0PP_C03_Q008 Operation quantities ............................................................................. 311
3.5.1.4 InfoCube: 0PP_C04 To-the-period operation / work center view................................................ 311
3.5.1.4.1 Query: 0PP_C04_Q001 Capacity load utilization........................................................................ 313
3.5.2 Actual quantities in the work center ..................................................................................................... 314
3.5.2.1.1 Query: 0PP_C04_Q002 Actual quantities in the work center ..................................................... 314
3.5.2.2 InfoCube: 0PP_C05 Plan / actual comparison material consumption......................................... 315
3.5.2.2.1 Query: 0PP_C05_Q001 Material consumption target / actual .................................................... 316
3.5.2.3 InfoCube: 0PP_C06 To-the-Period Material Consumption ......................................................... 317
3.5.2.3.1 Query: 0PP_C06_Q001 Material consumption ........................................................................... 318
3.5.3 Repetitive manufacturing..................................................................................................................... 319
3.5.3.1 InfoCube: 0PP_C07 Repetitive manufacturing Goods receipts .................................................. 319
3.5.4 Goods receipts Repetitive manufacturing............................................................................................ 320
3.5.4.1.1 Query: 0PP_C07_Q001 Goods receipts Repetitive manufacturing ............................................ 320
3.5.4.2 InfoCube: 0PP_C08 Repetitive manufacturing Material consumption........................................ 321
3.5.4.2.1 Query: 0PP_C08_Q001 Material consumption Repetitive production........................................ 322
4 Customer ReIationship Management....................................................................... 323
4.1 MobiIe SaIes ........................................................................................................................................... 323
4.1.1 Important Note ..................................................................................................................................... 323
4.1.2 Activities............................................................................................................................................... 323
4.1.2.1 InfoCube: 0MSA_C01 Activities (Customer/Product).................................................................. 323
4.1.2.1.1 Query: 0MSA_C01_Q0001 - Samples according products......................................................... 325
4.1.2.1.2 Query: 0MSA_C01_Q0002 - Sample reporting in detail ............................................................. 326
4.1.2.1.3 Query: 0MSA_C01_Q0003 - Samples reporting according region ............................................. 326
Page 10
4.1.2.1.4 Query: 0MSA_C01_Q0004 - Order quantity for material per month........................................... 327
4.1.2.1.5 Query: 0MSA_C01_Q0005 - Customer order quantity per month .............................................. 327
4.1.2.1.6 Query: 0MSA_C01_Q0006 - Action selling prices ...................................................................... 327
4.1.2.1.7 Query: 0MSA_C01_Q0007 - Overview of orders per division..................................................... 328
4.1.2.1.8 Query: 0MSA_C01_Q0008 - Orders per sales office.................................................................. 328
4.1.2.2 InfoCube: 0MSA_C02 Activities (Customers) ............................................................................. 329
4.1.2.2.1 Query: 0MSA_C02_Q0001 - Regional Analysis.......................................................................... 330
4.1.2.2.2 Query: 0MSA_C02_Q0002 - Customer-specific analysis ........................................................... 331
4.1.2.2.3 Query: 0MSA_C02_Q0003 - Activities of Key Accounts............................................................. 332
4.1.2.2.4 Query: 0MSA_C02_Q0004 - Activities according industries....................................................... 332
4.1.2.2.5 Query: 0MSA_C02_Q0005 - Activities according customer classes .......................................... 333
4.1.2.2.6 Query: 0MSA_C02_Q0006 - Activities according Nielsen-indicators.......................................... 333
4.1.2.2.7 Query: 0MSA_C02_Q0007 Activities according outlet type........................................................ 334
4.1.2.2.8 Query: 0MSA_C02_Q0008 - Visit rhythm - analysis ................................................................... 334
4.1.2.3 InfoCube: 0MSA_C03 Revenues ................................................................................................ 335
4.1.2.3.1 Query: 0MSA_C03_Q0001 - Order quantity ............................................................................... 337
4.1.2.3.2 Query: 0MSA_C03_Q0002 - Net value....................................................................................... 338
4.1.2.3.3 Query: 0MSA_C03_Q0003 - Invoice value ................................................................................. 338
4.1.2.3.4 Query: 0MSA_C03_Q0004 - Coverage....................................................................................... 339
4.1.2.3.5 Query: 0MSA_C03_Q0005 - Opportunity / Revenue.................................................................. 339
4.1.2.3.6 Query: 0MSA_C03_Q0006 - Promotion / Revenue .................................................................... 339
4.1.2.3.7 Query: 0MSA_C03_Q0007 - Revenues according Opportunity-Classification........................... 340
4.1.2.3.8 Query: 0MSA_C03_Q0008 - Revenues according Opportunity-Result Reason......................... 340
4.1.2.3.9 Query: 0MSA_C03_Q0009 - Revenues according kind of opportunity....................................... 341
4.1.2.3.10 Query: 0MSA_C03_Q0010 - Revenues according Opportunity type ........................................ 341
4.1.2.3.11 Query: 0MSA_C03_Q0011 - Order development...................................................................... 341
4.1.2.3.12 Query: 0MSA_C03_Q0012 - Promotion / Volume..................................................................... 342
4.1.2.4 InfoCube: 0MSA_C04 Activities .................................................................................................. 342
4.1.2.4.1 Query: 0MSA_C04_Q0001 Activities (Number of activities per prospect)............................... 344
4.1.2.4.2 Query: 0MSA_C04_Q0002 Activity status ............................................................................... 344
4.1.2.4.3 Query: 0MSA_C04_Q0003 Activities (Number of facings) ...................................................... 345
4.1.2.4.4 Query: 0MSA_C04_Q0004 Regional Analysis......................................................................... 345
4.1.2.4.5 Query: 0MSA_C04_Q0005 Activities Key Account .................................................................. 346
4.1.2.4.6 Query: 0MSA_C04_Q0006 Activity-types ................................................................................ 346
4.1.3 Opportunity .......................................................................................................................................... 347
4.1.3.1 InfoCube: 0HTMSAC01 Opportunities (with reference to material) ............................................ 347
4.1.3.1.1 Query: 0HTMSAC01_Q0001 Product Analysis........................................................................ 349
4.1.3.1.2 Query: 0HTMSAC01_Q0002 Material-Group Analysis ............................................................ 349
4.1.3.2 InfoCube: 0HTMSAC02 Opportunities (Pipeline Analysis) ......................................................... 350
4.1.3.2.1 Query: 0HTMSAC02_Q0001 Regional expected value........................................................... 352
4.1.3.2.2 Query: 0HTMSAC02_Q0002 Pipeline Customers ................................................................... 352
4.1.3.2.3 Query: 0HTMSAC02_Q0003 Pipeline Potential customers..................................................... 353
4.1.3.2.4 Query: 0HTMSAC02_Q0004 Pipeline Customers (according phases) ................................... 353
4.1.3.2.5 Query: 0HTMSAC02_Q0005 Pipeline classification ................................................................ 354
4.1.3.2.6 Query: 0HTMSAC02_Q0006 Kind of pipeline.......................................................................... 354
4.1.3.2.7 Query: 0HTMSAC02_Q0007 Pipeline Result reason (Lost Order Analysis) ........................... 355
5 ExternaI Data.............................................................................................................. 356
5.1 IS-RetaiI................................................................................................................................................... 356
5.1.1 SAP Campbell Integration ................................................................................................................... 356
Page 11
5.1.1.1 Important Note............................................................................................................................. 356
5.1.1.2 InfoCube: 0RC_C01 Labor Data .............................................................................................. 356
5.1.1.2.1 Query: 0RC_C01_Q0003 Actual vs. Scheduled Overtime....................................................... 362
5.1.1.2.2 Query: 0RC_C01_Q0005 Customer Service ........................................................................... 362
5.1.1.2.3 Query: 0RC_C01_Q0007 Department Productivity - DEMO ................................................... 363
5.1.1.2.4 Query: 0RC_C01_ Q0008 Job Productivity - DEMO ............................................................... 364
5.1.1.2.5 Query: 0RC_C01_Q0004 Labor Hour Distribution................................................................... 365
5.1.1.2.6 Query: 0RC_C01_Q0001 Actual Labor vs. Schedule.............................................................. 366
5.1.1.2.7 Query: 0RC_C01_Q0002 Managers Forecasted Labor .......................................................... 368
5.1.1.2.8 Query: 0RC_C01_Q0006 Schedule Quality............................................................................. 369
5.1.1.3 InfoCube: 0RT_C02 Sales Data............................................................................................... 371
5.1.1.3.1 Query: 0RC_C02_Q0002 Key Business Driver........................................................................ 374
5.1.1.3.2 Query: 0RC_C02_Q0004 Managers Forecasted Sales .......................................................... 375
5.1.1.3.3 Query: 0RC_C02_Q0005 Productivity Data Source ................................................................ 376
5.1.1.3.4 Query: 0RC_C02_Q0003 Sales vs. Last Year ......................................................................... 377
5.1.1.3.5 Query: 0RC_C02_Q0001 Sales vs. Plan ................................................................................. 378
5.1.1.4 InfoCube: 0RC_C03 Operational InfoCube.............................................................................. 379
5.1.1.4.1 Query: 0RC_C03_Q0005 Reporting Stores............................................................................. 384
5.1.1.4.2 Query: 0RC_C03_Q0001 Store Operations Summary ............................................................ 385
5.1.1.4.3 Query: 0RC_C03_Q0002 Store Operations Summary vs. Plan .............................................. 387
5.1.1.4.4 Query: 0RC_C03_Q0003 Store Operations Summary, Future Week ..................................... 388
5.1.1.4.5 Query: 0RC_C03_Q0004 Store Productivity............................................................................ 389
5.2 ACNieIsen USA....................................................................................................................................... 391
5.2.1 InfoCube: 0DSLC_C1, Special Laundry Care (SLC) Market Data...................................................... 391
5.2.1.1 Query: 0DSLC_C1_Q01: Market Performance........................................................................... 392
5.2.1.2 Query: 0DSLC_C1_Q02: Category Performance ....................................................................... 393
5.2.1.3 Query: 0DSLC_C1_Q04: Promotional Performance................................................................... 394
5.2.1.4 Query: 0DSLC_C1_Q05: Competitive Fact-Sheet ...................................................................... 394
Page 12
1 Accounting
1.1 FI FinanciaI Accounting
1.1.1 FI-AR Accounts ReceivabIe
1.1.1.1 InfoCube: 0FIAR_C01 - FIAR: Line items
Content:
This InfoCube contains all accounts receivable data (line items) that was downloaded from the connected source
system(s).
InfoSource:
0FI_AR_2: Accounts Receivable: Line Items
Characteristics:
InfoObject Description Navigation
attribute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0ACCT_TYPE Account type No No
0BLINE_DATE
Baseline date for due date calculation
No No
0BUS_AREA Business area No No
0CHRT_ACCTS Chart of accounts No No
0CLEAR_DATE Clearing date No No
0COMP_CODE Company code No No
0COUNTRY Country key No No
0DSCT_DATE1 Due date for cash discount 1 No No
0DUNN_AREA Dunning area No No
0DUNN_KEY Dunning key No No
0DUNN_LEVEL Dunning level No No
0GL_ACCOUNT Account number No No
0NETDUEDATE Due date for payment No No
0PMNTTRMS Terms of payment key No No
0PSTNG_DATE Posting date No No
Page 13
0SP_GL_IND Special G/L indicator No No
0LAST_DUNN Last dunning date No No
0DEBITOR Customer number Yes Yes
0C_CTR_AREA Credit control area No No
Time characteristics:
InfoObject Description
0FISCPER
Fiscal year / period
0FISCVARNT Fiscal year variant
0FISCYEAR Fiscal year
0FISCPER3 Posting period
Key figures:
InfoObject Description Unit InfoObject Aggregation
behavior
0CREDIT_DC Credit amount in foreign currency 0DOC_CURRCY additive
0CREDIT_LC Credit amount in local currency 0LOC_CURRCY additive
0DEBIT_DC
Debit amount in foreign currency
0DOC_CURRCY additive
0DEBIT_LC Debit amount in local currency 0LOC_CURRCY additive
0DEB_CRE_DC Foreign currency amount (+/-) 0DOC_CURRCY additive
0DEB_CRE_LC Local currency amount (+/-) 0LOC_CURRCY additive
0DISC_BASE Amount eligible for cash discount in
document currency
0DSC_AMT_DC Cash discount amount in document cur-
rency
0DSC_AMT_LC Cash discount amount in local currency 0LOC_CURRCY additive
Units:
InfoObject Description Type
0DOC_CURRCY SD document currency Currency
0LOC_CURRCY Local currency Currency
Page 14
1.1.1.2 InfoCube: 0FIAR_C02 FIAR: Summary VaIues
Content:
This InfoCube contains all accounts receivable data (transaction figures) that was downloaded from the connected
source system(s).
InfoSource:
0FI_AR_1: Accounts receivable: Transaction Figures
Characteristics:
InfoObject Description Navigation attribute
avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0DEBITOR Customer number Yes Yes
0DEBITOR_0INDUSTRY Industry key No No
0DEBITOR_0COUNTRY Country key No No
0CURTYPE Currency type No No
0FISCPER
Key figures:
behavior
0SALES Sales of the period
0CURRENCY
additive
0DEBIT Total debit postings 0CURRENCY additive
0BALANCE Accumulated balance 0CURRENCY semi-additive
0CREDIT Total credit postings 0CURRENCY additive
Units:
0CURRENCY Currency Currency
Page 15
1.1.1.2.1 Query: 0FIAR_C02_Q0001 - Accounts ReceivabIe: DSO AnaIysis, current
period
Use:
The day sales outstanding (DSO) analysis is concerned with the customer payment history. This analysis is always
made within a specific period. The DSO analysis provides general information on the number of days (DSO days) a
customer takes to pay an invoice. Or, in other words: The customer owes the value of DSO days day-sales. For
calculating the DSO days, the balances (= average debts outstanding (open customer items) at the end of the pe-
riod you select) are set against the sales (= average sales per period you select) according to the following formula:
DSO = balance/sales per period * 30
Balance = average debts outstanding (open customer items) at the end of the period you select.
Sales per period = average sales per period you select
Structure(s):
Key figure Remarks
Current balance
Accumulated balance of current period
Sales previous period Sales of the previous period
DSO
Accumulated balance of current period / sales of previous period * 30
See also remarks on use
Free characteristics:
InfoObject Description:
0DEBITOR Customer number
0COMP_CODE Company code
0DEBITOR_0INDUSTRY Industry key
0DEBITOR_0COUNTRY Country key
1.1.2 FI-AP Accounts PayabIe
1.1.2.1 InfoCube: 0FIAP_C01 - FIAP: Line items
Content:
This InfoCube contains all transaction data from accounts payable (line items) loaded from the connected source
system(s).
InfoSource(s):
0FI_AP_2: Accounts payable: Line Items
Page 16
Characteristics:
ExternaI hierarchy
avaiIabIe?
0ACCT_TYPE Account type No No
0BLINE_DATE
Baseline date for due date calculation
No No
0CLEAR_DATE Clearing date No No
0DUNN_AREA Dunning area No No
0DUNN_KEY Dunning key No No
0DUNN_LEVEL Dunning level No No
0GL_ACCOUNT Account number No No
0NETDUEDATE Due date for payment No No
0PMNTTRMS Terms of payment key No No
0PSTNG_DATE Posting date No No
0SP_GL_IND Special G/L indicator No No
0LAST_DUNN Last dunning date No No
0CREDITOR Account number of the vendor or creditor No Yes
0FISCPER
Page 17
Key figures:
behavior
0CREDIT_DC Credit amount in foreign currency 0DOC_CURRCY additive
0CREDIT_LC Credit amount in local currency 0LOC_CURRCY additive
0DEBIT_DC
Debit amount in foreign currency
0DEBIT_LC Debit amount in local currency 0LOC_CURRCY additive
0DEB_CRE_DC Foreign currency amount (+/-) 0DOC_CURRCY additive
0DEB_CRE_LC Local currency amount (+/-) 0LOC_CURRCY additive
0DISC_BASE Amount eligible for cash discount in document
currency
0DSC_AMT_DC Cash discount amount in document currency 0DOC_CURRCY additive
0DSC_AMT_LC Cash discount amount in local currency 0LOC_CURRCY additive
Units:
0DOC_CURRCY SD document currency Currency
1.1.2.2 InfoCube: 0FIAP_C02 - FIAP: Summary VaIues
Content:
This InfoCube contains all accounts payable data (transaction figures) that was downloaded from the connected
source system(s).
InfoSource(s):
0FI_AP_1: Accounts payable: Transaction Figures
Characteristics:
ExternaI hierarchy
avaiIabIe?
0CREDITOR Account number of the vendor or creditor No Yes
Page 18
0FISCPER
Key figures:
behavior
0SALES Sales for the period 0CURRENCY additive
0DEBIT Total debit postings 0CURRENCY additive
0BALANCE Accumulated balance 0CURRENCY semi-additive
0CREDIT Total credit postings 0CURRENCY additive
Units:
0CURRENCY Currency Currency
1.1.2.2.1 Query: 0FIAP_C02_Q0001 - Accounts PayabIe: Overview (Summary VaIues)
Use:
This query shows the total debit postings, the total credit postings, the accumulated balance and the sales of the
period by account number of the creditor, company code and currency type.
Structure(s):
Key figure Remarks
Debit Total debit postings
Credit Total credit postings
Balance Debit Credit
Accumulated balance Accumulated balance
Sales Sales for the period
Page 19
0CREDITOR Account number of the vendor or creditor
0FISCPER
1.1.3 FI-AA Asset Accounting
1.1.3.1 InfoCube: 0FIAA_C01: AnnuaI VaIues
Content:
This InfoCube contains all of the annual values uploaded from the source system(s) for Asset Accounting on the
basis of planned depreciation.
InfoSource(s):
0FI_AA_003: Revaluation/Year
0FI_AA_004: Investment Support
0FI_AA_001: Annual Values
Characteristics:
InfoObject Description Navigation-
ExternaI hierarchy
avaiIabIe?
0ASSET Asset sub-number Yes No
0ASSET_MAIN Asset main number No No
0DEPRAREA Depreciation area real or derived No No
0ASSET_AFAB Depreciation area of asset Yes No
Page 20
Key figures:
behavior
0CACQ_VL_YR Cumulative acquisition value at fis-
cal year start (w/o inv. support)
0CURRENCY Time: first value
0COR_DEP_YR Accumulated ordinary depreciation 0CURRENCY Time: first value
0CRES_TR_YR Cumulative transfer of reserves 0CURRENCY Time: first value
0CSP_DEP_YR Cumulative special depreciation 0CURRENCY Time: first value
0CUP_DEP_YR Cumulative unplanned depreciation 0CURRENCY Time: first value
0PLN_AVR_YR Planned transfer of reserves for year 0CURRENCY Additive
0PLO_DEP_YR Planned ordinary depreciation for
year
0CURRENCY Additive
0PLS_DEP_YR Planned special depreciation for
year
0CURRENCY Additive
0TACQ_VL_YR Transactions affecting acquis. value
(w/o inv. support)
0CURRENCY Additive
0UPL_DEP_YR Scheduled unplanned depreciation
for year
0CURRENCY Additive
0VAW_AVR_YR Value adjustment and write-up on
cumul. transfer of reserves
0CURRENCY Additive
0VAW_ODP_YR Value adjustment and write-up on
ordinary depreciation
0CURRENCY Additive
0VAW_SDP_YR Value adjustment and write-up on
special depreciation
0CURRENCY Additive
0VAW_UDP_YR Value adjustment and write-up on
unplanned depreciation
0CURRENCY Additive
0CREV_OD_YR Cumulative revaluation of ordinary
depreciation
0CREV_RV_YR Cumulative revaluation of replace-
ment value
0PREV_AODYR Planned revaluation of cumulative
0CURRENCY Additive
0PREV_RV_YR Planned revaluation of replacement
value
0CURRENCY Additive
0VA_RAPC_YR Value adjustment on revaluation of
APC
0CURRENCY Additive
0VA_RODP_YR Value adjustment on revaluation of
0CURRENCY Additive
Page 21
0CINV_GR_YR Cumulative investment grants 0CURRENCY Time: first value
0INV_GR_YR Investment grants for year 0CURRENCY Additive
0VA_INVS_YR Value adjustment on investment
support
0CURRENCY Additive
Units:
0CURRENCY Currency key Currency
Comments on the InfoCube:
Note:
If you try to total across a number different depreciation areas, this could lead to incorrect results in the query.
Check if a report that totals the values of several depreciation areas is really necessary.
Each time you upload data, the new data is added to the existing data. Therefore, delete existing data before
uploading.
Comments on the update ruIes:
The Fiscal year field is filled from the fiscal year period field of the InfoSource.
The 0ASSET_AFAB field is filled from the 0DEPRAREA field.
1.1.3.1.1 Query: 0FIAA_C01_Q001 Asset List
Purpose:
This query shows the current asset values in a depreciation area.
Structure:
Key figure Comments
Acquisition value Calculated key figure
Value adjustments Calculated key figure
Net book value Calculated key figure
Percent depreciated Percentage of depreciation in relation to acquisition value
Page 22
0ASSET_MAIN Asset main number
0ASSET Asset sub-number
0ASSET_AFAB__0BALSHA
_APC
APC balance sheet account
1.1.3.1.2 Query: 0FIAA_C01_Q002 VaIue Comparison Between Depreciation Areas
Purpose:
This query provides a comparison of two depreciation areas. It selects and compares the value adjustments (de-
preciation) and net book values of the depreciation areas you select.
Structure:
Key figure Comments
Acquisition value Calculated key figure: The acquisition value is determined for the deprecia-
tion area specified in the selection screen.
Value adjustments Calculated key figure: Value adjustments of the depreciation area
Net book value Calculated key figure: Net book value of the depreciation area
Value adjustments Calculated key figure: Value adjustments of the comparison depreciation
area
Net book value Calculated key figure: Net book value of the comparison depreciation area
Difference in val. adj. Value adjustments of the depreciation area minus Value adjustments of the
comparison depreciation area
Difference in NBV Net book value of the depreciation area minus Net book value of the com-
parison depreciation area
Comment:
When you use a breakdown showing the asset sub-number, the capitalization date of the asset is also displayed.
Page 23
1.1.3.2 InfoCube: 0FIAA_C02: Period VaIues
Content:
This InfoCube contains all of the period values uploaded from the source system(s) for Asset Accounting on the
basis of posted depreciation.
InfoSource(s):
0FI_AA_002: Posted Depreciation
Characteristics:
ExternaI hierarchy
avaiIabIe?
0FISCPER Fiscal year / Period
Key figures:
InfoObject Description Unit InfoObject Aggregation be-
havior
0ASS_APC_PE Acquisition value of asset at period
start
0CURRENCY Additive
0ASS_VAL_PE Value of asset at period start 0CURRENCY Time: first value
0AVR_PDP_PE Period: Posted transferred reserves 0CURRENCY Additive
0COR_DEP_PE Period start: Accumulated ordinary
depreciation
0CRES_TR_PE Period start: Cumulative transferred
reserves
Page 24
0CSP_DEP_PE Period start: Cumulative special
depreciation
0CUP_DEP_PE Period start: Cumulative unplanned
depreciation
0PST_ODP_PE Period: Posted ordinary depreciation 0CURRENCY Additive
0PST_SDP_PE Period: Posted special depreciation 0CURRENCY Additive
0PUP_DEP_PE Period: Posted unplanned deprecia-
tion
0CURRENCY Additive
0VAW_AVR_PE Value adjustment/write-up of trans-
ferred reserves
0CURRENCY Additive
0VAW_ODP_PE Value adjustment/write-up of ordi-
nary depreciation
0CURRENCY Additive
0VAW_SDP_PE Value adjustment/write-up of special
depreciation
0CURRENCY Additive
0VAW_UDP_PE Value adjustment/write-up of un-
planned depreciation
0CURRENCY Additive
Units:
Note:
uploading.
1.1.3.3 InfoCube: 0FIAA_C03: Transactions
Content:
This InfoCube contains all line items uploaded from the source system(s) from Asset Accounting.
InfoSource(s):
0FI_AA_006: Trans. w/ Val. Adjustmts
Page 25
0FI_AA_005: FI-AA: Acquisitions
Characteristics:
ExternaI hierarchy
avaiIabIe?
0SEQ_NUMBER Sequential number of asset line item
in fiscal year
No No
0TRANSTYPE Asset transaction type No No
0FISCPER Fiscal year / Period
Key figures:
havior
0ACQ_VAL_TR Acquisition value for transactions 0CURRENCY Additive
0INTERST_TR Interest on transaction 0CURRENCY Additive
0INV_SUP_TR Investment support on transaction 0CURRENCY Additive
0ORD_DEP_TR Ordinary depreciation on transaction 0CURRENCY Additive
0RES_TRF_TR Transferred reserves on transaction 0CURRENCY Additive
0REVAL_TR Revaluation on transaction 0CURRENCY Additive
0REV_ODP_TR Revaluation of ordinary depreciation
on transaction
0CURRENCY Additive
0SPC_DEP_TR Special depreciation on transaction 0CURRENCY Additive
0UPL_DEP_TR Unplanned depreciation on transac-
tion
0CURRENCY Additive
Page 26
0VAW_AVR_TR Transaction: Value adjustment/write-
up on transferred reserves
0CURRENCY Additive
0VAW_ODP_TR Transaction: Value adjustment/write-
up on ordinary depreciation
0CURRENCY Additive
0VAW_SDP_TR Transaction: Value adjustment/write-
up on special depreciation
0CURRENCY Additive
0VAW_UDP_TR Transaction: Value adjustment/write-
up on unplanned depreciation
0CURRENCY Additive
0VA_INVS_TR Value adjustment on investment
support
0CURRENCY Additive
0VA_RAPC_TR Value adjustment on revaluation of
APC
0CURRENCY Additive
0VA_RODP_TR Value adjustment on revaluation of
0CURRENCY Additive
Units:
Note:
uploading.
1.1.3.3.1 Query: 0FIAA_C03_Q001 Asset Acquisitions
Purpose:
This query lists asset acquisitions.
Structure:
Key figure Comments
Acquisitions Corresponds to the basic key figure: Acquisition value for transactions that
are filtered using history sheet groups in the filter
Page 27
0ASSET_0COSTCENTER Cost center
Comments:
The system determines the cost center in the asset valid on the current date, unless a key date is entered in the
properties of the query.
1.1.3.3.2 Query: 0FIAA_C03_Q002 Asset Acquisitions on QuarterIy Basis
Purpose:
This query displays all asset acquisitions in a given fiscal year and provides quarterly summarizations of the values.
Structure:
Key figure Comments
Quarter I Corresponds to the basic key figure: Acquisition value for transactions
limited to periods 001-003
Quarter II Corresponds to the basic key figure: Acquisition value for transactions
Quarter III Corresponds to the basic key figure: Acquisition value for transactions
Quarter IV Corresponds to the basic key figure: Acquisition value for transactions
Total Totals of quarters I to IV
Comments:
Page 28
1.1.3.4 InfoCube: 0FIAA_C04: AnnuaI VaIues and Transactions
Content:
This InfoCube contains all of the annual values uploaded from the source system(s) on the basis of planned depre-
ciation and line items.
InfoSource(s):
0FI_AA_006: Trans. w/ Val. Adjustmts
0FI_AA_005: FI-AA: Acquisitions
0FI_AA_001: Annual values
Characteristics:
ExternaI hierarchy
avaiIabIe?
0TRANSTYPE Asset transaction type No No
0SEQ_NUMBER Sequential number of asset line
item in fiscal year
No No
Key figures:
havior
0CACQ_VL_YR Acquisition value at fiscal year start
(w/o inv. support)
0COR_DEP_YR Accumulated ordinary depreciation 0CURRENCY Time: first value
0CRES_TR_YR Cumulative transferred reserves 0CURRENCY Time: first value
Page 29
0CSP_DEP_YR Cumulative special depreciation 0CURRENCY Time: first value
0CUP_DEP_YR Cumulative unplanned depreciation 0CURRENCY Time: first value
0PLN_AVR_YR Planned annual transfer of reserves 0CURRENCY Additive
0PLO_DEP_YR Planned annual ordinary deprecia-
tion
0CURRENCY Additive
0PLS_DEP_YR Planned annual special deprecia-
tion
0CURRENCY Additive
0TACQ_VL_YR Transactions affecting acquisition
value (w/o inv. support)
0CURRENCY Additive
0UPL_DEP_YR Unplanned depreciation for year 0CURRENCY Additive
0VAW_AVR_YR Value adjustment/write-up of
transferred reserves for year
0CURRENCY Additive
0VAW_ODP_YR Value adjustment and write-up on
0CURRENCY Additive
0VAW_SDP_YR Value adjustment and write-up on
special depreciation
0CURRENCY Additive
0VAW_UDP_YR Value adjustment and write-up on
unplanned depreciation
0CURRENCY Additive
0CREV_OD_YR Cumulative revaluation on ordinary
depreciation
0CREV_RV_YR Cumulative revaluation on replace-
ment value
0PREV_AODYR Planned revaluation of cumulative
0CURRENCY Additive
0PREV_RV_YR Planned revaluation of replacement
value
0CURRENCY Additive
0VA_RAPC_YR Value adjustment on revaluation of
APC
0CURRENCY Additive
0VA_RODP_YR Value adjustment on revaluation of
0CURRENCY Additive
0CINV_GR_YR Cumulative investment grants 0CURRENCY Additive
0INV_GR_YR Investment grants for year 0CURRENCY Additive
0VA_INVS_YR Value adjustment on investment
support
0CURRENCY Additive
0ACQ_VAL_TR Acquisition value for transactions 0CURRENCY Additive
0INTERST_TR Interest on transaction 0CURRENCY Additive
0INV_SUP_TR Investment support on transaction 0CURRENCY Additive
Page 30
0ORD_DEP_TR Ordinary depreciation on transac-
tion
0CURRENCY Additive
0RES_TRF_TR Transferred reserves on transaction 0CURRENCY Additive
0REVAL_TR Revaluation on transaction 0CURRENCY Additive
0REV_ODP_TR Revaluation of ordinary deprecia-
tion on transaction
0CURRENCY Additive
0SPC_DEP_TR Special depreciation on transaction 0CURRENCY Additive
0UPL_DEP_TR Unplanned depreciation on trans-
action
0CURRENCY Additive
0VAW_AVR_TR Transaction: Value adjust-
ment/write-up on transferred re-
serves
0CURRENCY Additive
0VAW_ODP_TR Transaction: Value adjust-
ment/write-up on ordinary deprecia-
tion
0CURRENCY Additive
0VAW_SDP_TR Transaction: Value adjust-
ment/write-up on special deprecia-
tion
0CURRENCY Additive
0VAW_UDP_TR Transaction: Value adjust-
ment/write-up on unplanned depre-
ciation
0CURRENCY Additive
0VA_INVS_TR Value adjustment on investment
support
0CURRENCY Additive
0VA_RAPC_TR Value adjustment on revaluation of
APC
0CURRENCY Additive
0VA_RODP_TR Value adjustment on revaluation of
0CURRENCY Additive
Units:
This InfoCube is designed for the asset history sheet. It includes the planned depreciation from InfoCube
0FIAA_C01 and the line items from InfoCube 0FIAA_C03.
Note:
uploading.
Page 31
1.1.3.4.1 Query: 0FIAA_C04_Q001 Asset History Sheet (for APC)
Purpose:
This query serves to create an asset history sheet that displays the evolution of acquisition and production costs for
fixed assets.
Structure:
Key figure Comments
APC at FY start Corresponds to the calculated key figure Acquisition value for the fiscal
year and depreciation area chosen in the selection screen (valid for all key
figures used)
Acquisition Basic key figure: Acquisition value for transactions limited to the history
sheet group for acquisitions
Retirement Basic key figure: Acquisition value for transactions limited to the history
sheet group for retirements
Transfer Basic key figure: Acquisition value for transactions limited to the history
sheet group for transfers
Current APC APC at FY start + Acquisition + Retirement + Transfer
Comments:
1.1.3.4.2 Query: 0FIAA_C04_Q002 Asset History Sheet (for Depreciation)
Purpose:
This query serves to create an asset history sheet that displays the evolution of value adjustments (depreciation)
for fixed assets.
Page 32
Structure:
Key figure Comments
Depreciation at FY start Calculated key figure
Acquisition depreciation Value adjustments on acquisitions + Planned annual depreciation
Value adjustments on acqui-
sitions
Value adjustments on transactions limited to transactions in acquisition
history sheet groups/hidden
Planned annual depreciation Calculated key figure /hidden
Retirement depreciation Value adjustments on transactions limited to transactions in retirement
history sheet groups
Transfer depreciation Value adjustments on transactions limited to transactions in transfer history
sheet groups
Final depreciation Depreciation FY start + Acquisition depreciation + Retirement depreciation
+ Transfer depreciation
Comments:
Page 33
1.2 TR Treasury
1.2.1 TR-CM Cash Management
1.2.1.1 InfoCube: 0TR_CM_C01: PIanned Amounts
Content:
This InfoCube contains all the Cash Management data loaded from the connected source systems.
InfoSource
0TR_CM_1 Cash Management
Characteristics:
characteristics
avaiIabIe?
Hierarchy avaiI-
abIe?
0COMP_CODE Company code Yes No
0P_DATA_OF Cash Management data from No No
0P_DATA_SRC Data origin for Cash Management No No
0P_ACCOUNT Cash Management account name No No
0P_LEVEL Planning level Yes No
0GROUPING Grouping for cash position, liquidity
forecast
No No
0P_GROUP Planning group Yes No
0BUS_AREA Business area Yes No
Time Characteristics:
0CALDAY Calendar day
0CALWEEK Calendar year/week
0CALMONTH Calendar year/month
0CALYEAR Calendar year
Page 34
Key Figures:
InfoObject Description InfoObject
units
Aggregation
behavior
0P_AMOUNT Planned amount in planned currency 0P_CURRENCY Additive
Units:
InfoObject Description Condition
0P_CURRENCY Planned currency Currency
Remarks on the InfoCube:
If you want to save the status of your Cash Management data, you should export the data to the Business Informa-
tion Warehouse on a daily basis.
1.2.1.1.1 Query: 0TR-CM-TFS-1 Cash Position by Day / Currency
Purpose:
This query allows you to display the bank account activity for the next few days.
Structure:
Key figure Remarks
0P_AMOUNT Planned amount in planned currency
Free Characteristics:
0BUS_AREA Business area
0P_LEVEL Planning level
0P_ACCOUNT Cash Management account name
1.2.1.1.2 Query: 0TR-CM-TFS-2 Cash Position by Currency / Day
Purpose:
This query allows you to display the bank account activity for the next few days.
Structure:
Key figure Remarks
Page 35
1.2.1.1.3 Query: 0TR-CM-LIQ-1 Liquidity Forecast by Day / Currency
Purpose:
This query allows you to display developments in the liquidity situation of the subledger accounts.
Structure:
Key figure Remarks
1.2.1.1.4 Query: 0TR-CM-LIQ-2 Liquidity Forecast by Currency / Day
Purpose:
This query allows you to display developments in the liquidity situation of the subledger accounts.
Structures:
Key figure Remarks
Page 36
1.2.1.1.5 Query: 0TR-CM-1 PIanned Amount by Day / Currency
Purpose:
This query allows you to look at the cash position and liquidity forecast together. In other words, this report gives
you the activity of the bank accounts for the next few days as well as the liquidity situation of the subledger ac-
counts.
Structure:
Key figure Remarks
0P_GROUP Planning group
1.2.1.1.6 Query: 0TR-CM-2 PIanned Amount by Currency / Day
Purpose:
This query allows you to view the cash position and liquidity forecast together.
Structure:
Key figure Remarks
Page 37
0P_GROUP Planning group
Page 38
1.3 CO ControIIing
1.3.1 CO-OM Overhead Cost ControIIing
1.3.1.1 Infocube: 0COOM_C01: Costs and AIIocations
Content:
This infocube contains all the costs on cost centers, overhead cost orders and work breakdown structure elements
retrieved from the linked source systems. The infocube also contains the partner information for the allocation rela-
tionships.
Info Source(s):
0CO_OM_CCA_1: Cost Centers: Costs and Allocations
0CO_OM_OPA_1: Orders: Costs and Allocations
0CO_OM_WBS_1: WBS Elem.: Costs
Characteristics:
Info Object Description Navigation
ExternaI hierarchy
avaiIabIe?
0COSTCENTER Cost center No Yes
0COORDER Order number No Yes
0WBS_ELEMT Work breakdown structure ele-
ment
No Yes
0COSTELMNT Cost element No Yes
0CO_AREA Controlling area No No
0PIOBJSV Partner object type No No
0PIOVALUE Partner object No No
0METYPE Key figure type No No
0VERSION Version No No
0VTDETAIL Detail of value type No No
0VTYPE Value type for reporting No No
0VTSTAT Statistics indicator for value type No No
0DB_CR_IND Sender/Receiver indicator No No
0VALUATION Valuation view No No
Page 39
Info Object Description
0FISCPER Fiscal year/period
Key figures:
Info Object Description Units-Info Ob-
ject
Aggregation
behavior
0AMOUNT Amount 0CURRENCY additive
Units:
Info Object Description Type
0CURRENCY Currency key Amount
Comments on the Infocube:
Note:
It is first necessary to load the WBS- and order masta data before you fill this InfoCube. Otherwise the cost
center responsible can not be determined and entered in 0COSTCENTER (please also see comments on the
update rules).
If you use different valuation views and currency types when totaling, you obtain incorrect results in the query.
Totaling using different values from the valuation views and currency types is, therefore, not advisable.
Every time you upload data, the system adds it to the existing values. You should, therefore delete existing
values where necessary, before repeating uploading.
In data records for orders or work breakdown structure (WBS) elements, the system fills the 0COSTCENTER (cost
center) info object with the responsible cost center for the order or WBS element. During the subroutine for the
update rules, the system determines the responsible cost center using the master data (for the order or WBS ele-
ment). Data records are not filled with the 0COORDER (order) or the 0WBS_ELEMT (WBS element) info objects.
1.3.1.1.1 Query: 0COOM_C01_Q0001: Cost Center: Orders PIan/ActuaI/Variance
Use:
This query provides you (the cost center manager) with an overview of costs incurred on a cost center, or cost
center hierarchy and corresponding orders, during the reporting timeframe. It enables you to make an actual and
plan cost analysis, taking cost elements and debits/credits into account.
Page 40
Structure(s):
Key figure Comments
Plan Planned costs within the reporting timeframe
Actual Actual costs within the reporting timeframe
Variance Variance between planned and actual costs within the reporting timeframe
Var. (%) Plan percentage variance, within the reporting timeframe
Info Object Description:
0COSTELMNT Cost element
0DB_CR_IND Sender/Receiver indicator
0COORDER Order number
0COSTCENTER Cost center
1.3.2 CO-OM-CCA Cost Center Accounting
1.3.2.1 Infocube: 0CCA_C01: Costs and AIIocations (FuII Costs)
Content:
This infocube contains all costs and consumption quantities from absorption costing retrieved from linked source
system(s). The infocube also contains the partner information from allocation relationships.
Info Source(s):
0CO_OM_CCA_1: Cost Centers: Costs and Allocations
Characteristics:
ExternaI hierarchy
avaiIabIe?
Page 41
Key figures:
Info Object Description Units - Info Ob-
ject
Aggregation
behavior
0QUANTITY Consumption quantity 0UNIT additive
Units:
0UNIT Unit of measure Quantity
Note:
The fiscal year (0FISCYEAR) and posting period (0FISCPER3) characteristics are filled from the fiscal year period
(0FISCPER) field in the info source.
Page 42
1.3.2.1.1 Query: 0CCA_C01_Q0005: Cost center: PIan/ActuaI/Variance
Use:
This query provides you (the cost center manager) with an overview of the costs and consumption quantities in-
curred on a cost center, or cost center hierarchy within the reporting timeframe. It enables you to make an actual
and plan analysis of these costs with regard to cost elements and debits/credits, as well as the corresponding allo-
cation partners.
Structure(s):
Key figure Comments
Costs: Plan Planned costs within the reporting timeframe
Costs: Actual Actual costs within the reporting timeframe
Costs: Variance Variance between plan and actual costs within the reporting timeframe
Costs: Var. (%) Plan percentage variance, within the reporting timeframe
Quantities: Plan Plan quantity within the reporting timeframe
Quantities: Actual Actual quantity within the reporting timeframe
Quantities: Variance Variance between plan and actual quantities within the reporting timeframe
Quantities: Var. (%) Plan percentage variance, within the reporting timeframe
0PIOBJSV Partner object type
0PIOVALUE Partner object
1.3.2.1.2 Query: 0CCA_C01_Q0001: Cost center: PIan/ActuaI/Variance current/cumu-
Iated Period
Use:
This query provides you (the cost center managers) with an overview of the costs incurred on a cost center, or cost
center hierarchy in the current period and during the entire fiscal year. It enables you to make an actual and plan
analysis of the costs with regard to cost elements and debits/credits, as well as the corresponding allocation part-
ners.
Page 43
Structure(s):
Key figure Comments
Plan current period Planned costs in the current posting period
Act. current period Actual costs in the current posting period
Variance Variance between plan and actual costs in the current period
Var. (%) Plan percentage variance in the current period
Plan cum. FY Planned costs cumulated during the entire fiscal year
Act. cum. FY Actual costs cumulated during the entire fiscal year
Variance Variance between planned and actual costs in the fiscal year
Var. (%) Plan percentage variance in the fiscal year
1.3.2.2 Infocube: 0CCA_C02: Costs and AIIocations (MarginaI
Costs)
Content:
This infocube contains all the costs and quantities from marginal costing, retrieved from the linked source sys-
tem(s). It also includes costs and quantities distributed by splitting to activity types.
Info Source(s):
0CO_OM_CCA_2: Cost Centers: Split Costs
Characteristics:
ExternaI hierarchy
avaiIabIe?
Page 44
0ACTTYPE Activity type No Yes
Key figures:
ject
Aggregation
behavior
0AMOUNTFX Fixed amount 0CURRENCY additive
0AMOUNTVR Variable amount 0CURRENCY additive
0QUANTITYFX Fixed consumption quantity 0UNIT additive
0QUANTITYVR Variable consumption quantity 0UNIT additive
Units:
Note:
Page 45
The fiscal year (0FISCYEAR) and posting period (0FISCPER3) characteristics are filled by the fiscal year period
field (0FISCPER) in the info source.
1.3.2.2.1 Query: 0CCA_C02_Q0003: Cost center: Target/ActuaI/Variance
Use:
This query provides you (the cost center manager) with an overview of the costs and consumption quantities that
are incurred on a cost center or cost center hierarchy within the reporting timeframe. It enables you to analyze the
target and actual values with regards to cost elements, as well as debits/credits. It displays the fixed portion of
these values.
Structure(s):
Key figure Comments
Costs: Target Target costs within the reporting timeframe
Costs: Fixed target (%) Percentage of total target costs which is fixed target costs
Costs: Fixed actual (%) Percentage the total actual costs which is fixed actual costs
Costs: Variance Variance between target and actual costs within the reporting timeframe
Costs: Var. (%) Target percentage variance within the reporting timeframe
Quantities: Plan Plan quantities within the reporting timeframe
Quantities: Fixed plan (%) Percentage of total plan quantities which is the fixed plan quantities
Quantities: Actual Actual quantities within the reporting timeframe
Quantities: Fixed actual (%) Percentage of total actual quantities which is the fixed actual quantities
Quantities: Var. (%) Plan percentage variance, within the reporting timeframe
0FISCPER Posting period/Fiscal year
Page 46
1.3.2.3 Infocube: 0CCA_C03: StatisticaI Key figures
Content:
This infocube contains all the quantities you posted to statistical key figures for cost center accounting retrieved
from the linked source system(s).
Info Source(s):
0CO_OM_CCA_4: Cost Centers: Statistical Key Figures
Characteristics:
ExternaI hierarchy
avaiIabIe?
0STKEYFIG Statistical key figure No Yes
Key figures:
ject
Aggregation
behavior
0QUANTITY Quantity 0UNIT additive
0QUANT_AVRG Inventory quantity 0UNIT
Units:
Page 47
Note:
Each statistical key figure category determines whether the system updates quantities or inventory quantities
on the statistical key figure. The system fills the 0QUANT_AVRG info object for non-cumulative values, such as
"Number of Employees". However, for cumulative values such as "Telephone Units", the system fills the
0QUANTITY info object.
1.3.2.3.1 Query: 0CCA_C03_Q0001: Cost center: StatisticaI Key figures PIan/ActuaI/
Variance
Use:
This query provides you (the cost center manager) with an overview of the statistical key figures that were posted
to on a cost center or cost center hierarchy within the reporting timeframe.
Structure(s):
Key figure Comments
Plan Statistical plan quantities within the reporting timeframe
Actual Statistical actual quantities within the reporting timeframe
Variance Variance between plan and actual quantities within the reporting timeframe
Var. (%) Plan percentage variance within the reporting timeframe
0STKEYFIG Statistical key figure
Page 48
1.3.3 CO-OM-ABC Activity-Based Costing
1.3.3.1 InfoCube: 0ABC_C01, Activity-Based Costing (Costs and
Quantities)
Contents:
This InfoCube contains the costs and allocations for the business process. It also contains the resource quantities
consumed and the allocated process quantity (activity quantity).
InfoSource(s):
0CO_OM_ABC_1: Processes: costs
0CO_OM_ABC_2: Processes: activity quantities
Characteristics:
ExternaI hierarchy
avaiIabIe?
0PROC_TYPE Category No No
0VALADD_EXT Value added ext. No No
0VALADD_INT Value added int. No No
0PERF_TYPE Cost behavior No No
0ABCPROCESS Business process No Yes
0DB_CR_IND Sender/receiver No No
0METYPE Key figure category No No
0VALUATION Valuation No No
0VTSTAT Statistics indicator No No
0VTYPE Reporting value type No No
Page 49
Key figures:
behavior
0QUANTITYFX Consumption quantity fixed 0UNIT Additive
0QUANTITY Consumption quantity 0UNIT Additive
0QUANTITYVR Consumption quantity var. 0UNIT Additive
0ACT_QUANTY Activity quantity 0ACT_UNIT Additive
0AMOUNTFX Amount fix 0CURRENCY Additive
0AMOUNT Amount 0CURRENCY Additive
0AMOUNTVR Amount variable 0CURRENCY Additive
Units:
0CURRENCY Currency Amount
0ACT_UNIT Activity unit Quantity
Note the following:
If you sum across different valuation views and currency types, the results in the query will be incorrect. Sum-
ming across different characteristic values is not appropriate.
Each time data is uploaded, it is added to the existing values. If you dont want this to happen, delete the ex-
isting data before uploading.
The characteristics fiscal year (0FISCYEAR) and posting period (0FISCPER3) are filled by the field fiscal year pe-
riod (0FISCPER) of the InfoSource.
Page 50
1.3.3.1.1 Query: 0ABC_C01_Q0001: Processes: Target Costs, ActuaI Costs, Cost Dif-
ferences
Use:
This query compares the target costs and actual costs of a business process and the target and actual quantities
for the resources consumed.
Structure(s):
Key figure Remarks
Target costs For selected target cost version (entered in selection screen)
Actual costs For version 0
Cost difference Actual costs target costs
Target input quantity For selected target cost version
Actual input quantity For version 0
Quantity difference Actual input quantity target input quantity
0VALADD_EXT Value added, external
0VALADD_INT Value added, internal
0ABCPROCESS Business process
0PIOBJSV Partner type
Remarks:
1.3.3.1.2 Query: 0ABC_C01_Q0002: Process Efficiency
Use:
This query compares the target and actual costs of a business process and the target and actual costs per process
quantity (activity quantity).
Structure(s):
Key figure Remarks
Actual costs For Version 0
Page 51
Activity quantity For version 0
Actual costs/unit Actual costs/activity quantity
Target costs/unit Target costs/activity quantity
Remarks:
1.3.3.2 InfoCube: 0ABC_C02, Activity-Based Costing (StatisticaI
Key Figures)
Contents:
This InfoCube contains the quantities loaded from the linked source system(s) that were posted to statistical key
figures for the process.
InfoSource(s):
0CO_OM_ABC_3: Processes: statistical key figures
Characteristics:
ExternaI hierarchy
avaiIabIe?
Page 52
Key figures:
behavior
0QUANT_AVRG Inventory quantity 0UNIT Additive
Units:
Remarks on InfoCube:
Note the following:
The category of the statistical key figure determines whether quantities or inventory quantities are posted to it.
For inventory values such as number of employees, the InfoObject 0QUANT_AVRG is filled. For cumulative
figures such as telephone units, the InfoObject 0QUANTITY is filled.
Remarks on the update ruIes:
1.3.3.2.1 Query: 0ABC_C02_Q0001: Processes: StatisticaI Key Figures
Use:
This query offers provides the employee responsible for the process with an overview of the statistical key figures
posted to the business process or process hierarchy during the reporting time frame.
Page 53
Structure(s):
Key figure Remarks
Planned quantity Statistical planned quantities within the reporting time frame
Confirmed quantity Statistical actual quantities within the reporting time frame
Variance Actual quantity - planned quantity
Var. % Percentage variance based on plan within reporting time frame
Remarks:
1.3.3.3 InfoCube: 0ABC_C03, Activity-Based Costing (Primary
Cost Component SpIit)
Contents:
This InfoCube contains the process costs broken down into cost components. Process costs are allocated to cost
objects under allocation cost elements which results in the loss of information on the original cost elements. The
cost component split, which is generated in the process of activity price calculation for the business process, can
summarize the information of multiple source cost elements onto one cost component.
InfoSource(s):
0CO_OM_ABC_5: Processes: cost split
Characteristics:
ExternaI hierarchy
avaiIabIe?
Page 54
0CSTCOMP Cost component No No
0CURTYP Currency type No No
Key figures:
behavior
0AMOUNTFX Amount fixed 0CURRENCY Additive
Units:
Note the following:
If you sum across different currency types, the results in the query will be incorrect. Summing across different
characteristic values of these characteristics is not appropriate.
1.3.3.3.1 Query: 0ABC_C03_Q0001: Primary Cost Component SpIit
Use:
This query displays the planned and actual activity price for each business process broken down into cost compo-
nents, and shows the differences between the plan activity prices and the actual activity prices.
Page 55
Structure(s):
Key figure Remarks
Planned costs For selected version (entered in the selection screen)
Cost difference Actual costs planned costs
Planned costs, fixed For selected version (entered in selection screen)
Actual costs, fixed For version 0
Cost difference, fixed Actual costs fixed planned costs fixed
Planned costs, variable For selected version (entered in selection screen)
Actual costs, variable For version 0
Cost difference, variable Actual costs variable planned costs variable
0CSTCOMP Cost component
Remarks:
1.3.3.4 InfoCube: 0ABC_C04, Activity-Based Costing (Variances)
Contents:
This InfoCube contains the variances between target costs and actual costs, broken down into variance categories.
InfoSource(s):
0CO_OM_ABC_6: Processes: variances
Characteristics:
ExternaI hierarchy
avaiIabIe?
Page 56
0VTDETAIL Detail of value No No
Key figures:
behavior
0VAR_FX Amount, fixed 0CURRENCY Additive
0VARIATION Amount 0CURRENCY Additive
0VAR_VR Amount, variable 0CURRENCY Additive
Units:
Note the following:
characteristic values of these characteristics is not appropriate.
Page 57
1.3.3.4.1 Query: 0ABC_C04_Q0001: Process Variances
Use:
This query analyzes the variances of a business process.
Structure(s):
Key figure Remarks
Input price variance For selected target cost version
Input quantity variance For selected target cost version
Resource-usage variance For selected target cost version
Remaining input variance For selected target cost version
TotaI input variance Input price variance + input quantity variance + resource-usage variance +
remaining input variance
Output price variance For selected target cost version
Output quantity variance For selected target cost version
Remaining variance Target cost version
TotaI output variance Output price variance + output quantity variance + remaining variance
TotaI variance Total input variance + Total output variance
0VALADD_EXT Value added external
0VALADD_INT Value added internal
0ABCPROCESS Business process number
Remarks:
Page 58
1.3.3.5 InfoCube: 0ABC_C13, Activity AIIocation (Primary Cost
Component SpIit)
Contents:
This InfoCube contains the activity costs broken down into cost components. Internal activities are allocated under
allocation cost elements which results in the loss of information on the original cost elements. The cost compo-
nent split, which is generated activity price calculation for each activity type of the cost center, can summarize the
information of multiple source cost elements onto one cost component.
InfoSource(s):
0CO_OM_CCA_6: Cost centers: cost split
Characteristics:
ExternaI hierarchy
avaiIabIe?
0CSTCOMP Component No No
0ACTTYPE Activity type No No
Key figures:
InfoObject Description Unit InfoObject Aggregations
behavior
Page 59
Units:
Note the following:
values of these characteristics is not appropriate.
1.3.3.5.1 Query: 0ABC_C13_Q0001: Primary Cost Component SpIit
Use:
This query displays the plan activity price and actual activity price for each activity type of a cost center broken
down into cost components, and shows differences between the plan activity price and actual activity price.
Structure(s):
Key figure Remarks
Planned costs For selected version (entered in selection screen)
Cost difference Actual costs planned costs
Planned costs, fixed For selected version (entered in selection screen)
Actual costs, fixed For version 0
Cost difference, fixed Actual costs fixed planned costs fixed
Planned costs, variable For selected version (entered in selection screen)
Actual costs, variable For Version 0
Cost difference, variable Actual costs variable planned costs variable
Page 60
0ACTTYPE Activity type
0CSTCOMP Cost component
Remarks:
1.3.3.6 InfoCube: 0ABC_C14, Activity AIIocation (Variances)
Contents:
This InfoCube contains the variances between target costs and actual costs, broken down into variance categories.
InfoSource(s):
0CO_OM_CCA_5: Cost centers: variances
Characteristics:
ExternaI hierarchy
avaiIabIe?
0VTDETAIL Detail of value No No
Page 61
Key figures:
InfoObject Description Unit InfoObject Aggregations
behavior
0VAR_FX Amount fixed 0CURRENCY Additive
0VARIATION Amount 0CURRENCY Additive
0VAR_VR Amount variable 0CURRENCY Additive
Units:
Note the following:
values of these characteristics is not appropriate.
1.3.3.6.1 Query: 0ABC_C14_Q001: Cost Center Variances
Use:
This query analyzes the variances for each activity type of a cost center.
Structure(s):
Key figure Remarks
Input price variance For selected target cost version
Input quantity variance For selected target cost version
Resource-usage variance For selected target cost version
Remaining input variance For selected target cost version
TotaI input variance Input price variance + input quantity variance + resource-usage variance +
remaining input variance
Output price variance For selected target cost version
Output quantity variance For selected target cost version
Page 62
Remaining variance Target cost version
TotaI output variance Output price variance + output quantity variance + remaining variance
TotaI variance Total input variance + Total output variance
Remarks:
1.3.3.7 InfoCube: 0ABC_C15, Activity AIIocation (Costs and
Quantities)
Contents:
This InfoCube contains the costs and allocations for each activity type of a cost center. It also contains the re-
source quantity consumed, and the allocated activity quantity.
InfoSource(s):
0CO_OM_CCA_2: Cost centers: split costs
0CO_OM_CCA_3: Cost centers/activity types: activities
Characteristics:
ExternaI hierarchy
avaiIabIe?
0CO_AREA Controlling area No Nein
0CURTYP Currency type No No
Page 63
0COSTELEMNT Cost element No Yes
Key figures:
behavior
0ACT_OUTPUT Output 0OUTP_UNIT Additive
0ACT_SCHEDL Planned activity 0ACT_UNIT Additive
0ACT_CAPACT Capacity 0ACT_UNIT Additive
0ACT_QUANTY Activity quantity 0ACT_UNIT Additive
0QUANTITYFX Consumption quantity fixed 0UNIT Additive
0QUANTITYVR Consumption quantity variable 0UNIT Additive
Units:
0OUTP_UNIT Output unit Quantity
0ACT_UNIT Activity unit Quantity
Page 64
1.3.3.7.1 Query: 0ABC_C05_Q0001: Cost Centers/Activity Types: Target Costs, ActuaI
Costs, Cost Differences
Use:
This query compares the target costs and actual costs for each activity type of a cost center, and the target quanti-
ties and actual quantities of the resource consumed.
Structure(s):
Key figure Remarks
Target input quantity For selected target cost version
Actual input quantity For version 0
Quantity difference Actual input quantity target input quantity
Remarks:
1.3.3.7.2 Query: 0ABC_C05_Q0002: Cost Center Efficiency
Use:
This query compares the target costs and actual costs for each activity type of a cost center, and determines the
target costs and actual costs per activity quantity.
Page 65
Structure(s):
Key figure Remarks
Activity quantity For version 0
Actual costs/unit Actual costs/activity quantity
Target costs/unit Target costs/activity quantity
1.3.4 CO-OM-OPA Overhead Cost Orders
1.3.4.1 Infocube: 0OPA_C01: Costs and AIIocations
Content:
This info cube contains all the costs, quantities and budgets on overhead cost orders retrieved from the linked
source system(s).
Info Source(s):
0CO_OM_OPA_2: Orders: Budget
0CO_OM_OPA_3: Orders: Total/Yearly Plan Values
Characteristics:
ExternaI hierarchy
avaiIabIe?
Page 66
Key figures:
ject
Aggregation
behavior
Units:
Note:
The system does not fill the time characteristics or the cost element for overall budgets and overall planning
values. Nor does it fill the posting period and the cost element characteristic for annual budgets and annual
Page 67
planning values. This creates values with the 000.YYYY (Y = Fiscal Year) format, particularly for the
0FISCPER characteristic.
1.3.4.1.1 Query: 0OPA_C01_Q0005: Orders: Budget/Commitment/ActuaI/AIIotted
Use:
This query provides you (the orders manager) with an overview of the set budgets for an order or an order hierar-
chy, as well as for the incurred commitments and costs. It enables you to analyze these values taking the fiscal
year and the posting periods into account. The system calculates the remaining available budget using these val-
ues.
Structure(s):
Key figure Comments
Budget Budget within the reporting timeframe
Commitment Commitment within the reporting timeframe
Allotted Total of commitment and actual costs
Available Budget within the reporting timeframe minus allotted amounts
1.3.4.1.2 Query: 0OPA_C01_Q0006: Orders: PIan/ActuaI/Variance
Use:
This query provides you (the orders manager) with an overview of the costs and consumption quantities incurred
on an order or an order hierarchy within the reporting timeframe. It enables you to make an actual and plan analy-
sis taking cost elements, debits/credits and the corresponding allocation partners into account.
Page 68
Structure(s):
Key figure Comments
Costs: Plan Plan costs within the reporting timeframe
Costs: Var. (%) Plan percentage variance, within the reporting timeframe
Quantities: Var. (%) Plan percentage variance within the reporting timeframe
1.3.4.1.3 Query: 0OPA_C01_Q0022: Orders: OveraII PIan/Commitment/ActuaI/AIIotted
Use:
This query provides you (the orders manager) with an overview of the set overall plan values for an order or an
order hierarchy, as well as for the incurred commitments and costs. It enables you to analyze these values taking
the fiscal year and the posting periods into account. The system calculates the remaining available overall plan
value using these values.
Structure(s):
Key figure Comments
Overall Plan Overall plan value within the reporting timeframe
Commitment Commitment within the reporting timeframe
Allotted Total of commitment and actual costs
Page 69
1.3.4.2 Infocube: 0OPA_C02: StatisticaI Key Figures
Content:
This infocube contains all the statistical key figures posted to overhead cost orders, that were retrieved from the
linked source system(s).
Info Source(s):
0CO_OM_OPA_4: Orders: Statistical Key Figures
Characteristics:
ExternaI hierarchy
avaiIabIe?
Page 70
Key figures:
ject
Aggregation
behavior
Units:
Each statistical key figure category determines whether the system updates quantities or inventory quantities
on the statistical key figure. The system fills the 0QUANT_AVRG info object for non-cumulative values, such as
"Number of Employees". However, for cumulative values such as "Telephone Units", the system fills the
0QUANTITY info object.
1.3.4.2.1 Query: 0OPA_C02_Q0001: Orders: StatisticaI Key figures PIan/ActuaI/Varian-
ce
Use:
This query provides you (the orders manager) with an overview of the statistical key figures posted to on an order
or an order hierarchy within the reporting timeframe.
Structure(s):
Key figure Comments
Page 71
1.3.5 CO-OM-PRO Overhead Cost Projects
1.3.5.1 Infocube: 0WBS_C01: Costs and AIIocations
Content:
This infocube contains all costs, quantities and budgets on WBS elements that were retrieved from the linked
source system(s).
Info Source(s):
0CO_OM_WBS_1: WBS Elem.: Costs
0CO_OM_WBS_2: WBS Elem.: Budget
0CO_OM_WBS_3: WBS Elem.: Overall/Annual Planning Values
Characteristics:
ExternaI hierarchy
avaiIabIe?
ment
No Yes
Page 72
Key figures:
ject
Aggregation
behavior
Units:
Note:
1.3.5.1.1 Query: 0WBS_C01_Q0002: WBS EIement: Budget/Commitment/ActuaI/Avai-
IabIe
Use:
This query provides you (the project manager) with an overview of the budgets set for a WBS element or a WBS
element hierarchy, as well as the commitments and costs incurred. It enables you to analyze these values taking
Page 73
the fiscal years and posting periods into account. The system calculates the remaining available budget using
these values.
Structure(s):
Key figure Comments
Budget Budget within the reporting timeframe
Commitment Commitments within the reporting timeframe
Allotted Total of commitments and actual costs
0WBS_ELEMT Work breakdown structure element
1.3.5.1.2 Query: 0WBS_C01_Q0001: WBS EIement: PIan/ActuaI/Variance
Use:
This query provides you (the project manager) with an overview of incurred costs and consumption quantities on a
WBS element or WBS element hierarchy within the reporting timeframe. It enables you to make a plan or actual
analysis of these costs taking cost elements, debits/credits and corresponding allocation partners into account.
Structure(s):
Key figure Comments
Costs: Plan Plan costs within the reporting timeframe
Costs: Var. (%) Plan percentage variance within the reporting timeframe
Quantities: Var. (%) Plan percentage variance within the reporting timeframe
Page 74
1.3.5.2 Infocube: 0WBS_C02: StatisticaI Key Figures
Content:
This infocube contains all the statistical key figures posted to WBS elements that were retrieved from the linked
source system(s).
Info Source(s):
0CO_OM_WBS_4: WBS Elem.: Statistical Key Figures
Characteristics:
ExternaI hierarchy
avaiIabIe?
ment
No Yes
Page 75
Key figures:
ject
Aggregation
behavior
Units:
Note:
1.3.5.2.1 Query: 0WBS_C02_Q0001: WBS EIement: StatisticaI Key Figures, PIan/Ac-
tuaI/ Variance
Use:
This query provides you (the project manager) with an overview of the statistical key figures posted to on a WBS
element or a WBS element hierarchy within the reporting timeframe.
Structure(s):
Key figure Comments
Page 76
1.3.6 CO-PC Product Cost ControIIing
1.3.6.1 InfoCube: 0PC_01: Transaction data
Content:
This InfoCube contains all of the transaction data uploaded from the source system. The data reflects all product
cost collectors and all orders in Cost Object Controlling.
InfoSource(s):
0CO_PC_01 Product Cost by Order or Period: Plan/actual costs
0CO_PC_02 Product Cost by Order or Period: Period-end closing
Characteristics:
ExternaI hierarchy
avaiIabIe?
0CURTYPE Currency type no no
0VALUATION Valuation no no
0CO_AREA Controlling area no no
0PLANT Plant no no
0MATERIAL Material number yes no
0MATL_GROUP Material group no no
0MATL_TYPE Material type no no
0MATL_HIER Product hierarchy no no
0ORDERITEM Number of order item no no
0PRODORDER Order number (Production order) no no
0PRODPROCNR Production process
no
no
0PRODVRSN Production version no no
0COSTELMNT Cost element no no
Page 77
0DB_CR_IND Sender-receiver indicator no no
0PIOBJSV Partner object type no no
0PIOVALUE Partner object no no
0VERSION Version no no
0VTYPE Value type for reporting no no
0METYPE Key figure category no no
0VTDETAIL Detail of the value type no no
Key Figures:
InfoObject Description InfoObject units Aggregation
0AMOUNT Amount 0CURRENCY SUM
0AMOUNTFX Fixed amount 0CURRENCY SUM
0AMOUNTVR Variable amount 0CURRENCY SUM
0QUANTITY Quantity 0CURRENCY SUM
0QUANTITYFX Fixed quantity consumed 0CURRENCY SUM
0QUANTITYVR Variable quantity consumed 0CURRENCY SUM
0QUANTOUT Activity quantity 0UNIT SUM
0CONTCOST Control costs 0CURRENCY SUM
Units:
InfoObject Description Typ
0UNIT Unit of measure Unit of measure
0ACT_UNIT Service unit Unit of measure
Page 78
Notes on the InfoCube:
Never calculate a sum using different currency keys or valuations, as it can lead to incorrect results in the query.
Always use a filter for the currency key and valuation key.
The following characteristics determine the content of InfoObject 0Amount: version, value type for reporting, key
figure category, and detail of value type. (i.e. target costs have value type 30; scrap has value type 70 key figure
category 1300 and detail 41.)
Notes on the update ruIes:
The fiscal year and period are taken from the fiscal year period field.
1.3.6.1.1 Query: 0PC_C01_Q0001: Target Costs, ActuaI Costs, Cost Differences
Purpose:
This query compares an orders target and actual costs as well as comparing the target input quantity with the ac-
tual input quantity.
Structure:
Indicator Comment
Target costs For selected target versions (entered in the selection screen)
Cost difference Actual costs - target costs
Actual input quantity
Target input quantity For selected target versions
Quantity difference Actual input quantity - target input quantity
User-defined characteristics:
0PLANT Plant
0MATL_HIER Product hierarchy
0MATERIAL Material number
0PRODORDER Order number (Production order)
Page 79
1.3.6.1.2 Query: 0PC_C01_Q0002: Costs for Output Quantities
Purpose:
This query compares the target costs and the actual costs from an order and determines the target and actual
costs for each output quantity.
Structure:
Indicator Comment
Target costs For selected target version (entered in the selection screen)
Cost difference Actual costs - target costs
Production quantity
Actual costs/unit Actual costs / production quantity
Target costs / unit Target costs / production quantity
0PLANT Plant
0MATERIAL_0PROD_HIE Product hierarchy
0PRODORDER Order number (production order)
0PRODVRSN Production version
0FISCPER Fiscal year / period
1.3.6.1.3 Query: 0PC_C01_Q0003: Production Variance
Purpose:
This query compares the target costs with the actual costs from an order or a product cost collector and displays
the resulting variances according to variance category. In addition, the query displays the value of the work in pro-
cess and the value of the unplanned scrap for the order or product cost collector.
Structure:
Indicator Comment
Work in process For selected results analysis versions
Scrap For selected target versions
Page 80
Control costs For selected target versions
Target costs For selected target version (entered in the selection screen)
Total Variances Control costs - target costs
Input price variance For selected target versions
Input quantity variance For selected target versions
Resource-usage variance For selected target versions
Remaining input variance For selected target versions
Total Input Variance Input price variance + Input quantity variance + Resource-usage vari-
ance
+ Remaining input variance
Mixed-price variance For selected target versions
Output price variance For selected target versions
Lot size variance For selected target versions
Remaining variance For selected target versions
Total Output Variance Mixed-price variance + Output price variance
+ Lot size variance + Remaining variance
0PLANT Plant
0MATERIAL_0PROD_HIE Product hierarchy
0MATERIAL Material
0PROD_VRSN Production version
0PRODORDER Production order number
1.3.6.2 InfoCube: 0COPC_02: ActuaI Costing/MateriaI Ledger
Content:
This InfoCube contains all of the transaction data for the Material Ledger uploaded from the source system. This
transaction data is in all currencies and valuations, and covers all periods, materials, and valuation types (or for
each sales order or project stock).
Page 81
InfoSource(s):
0CO_PC_ACT_1: Actual Costing/Material Ledger
Characteristics:
ExternaI hierarchy
avaiIabIe?
0CURTYPE Currency type no no
0VALUATION Valuation no no
0COMP_CODE Company code no no
0CO_AREA Controlling area no no
0PLANT_P Plant no no
0STLMT_CTRL Settlement control no no
0VAL_CLASS Valuation class no no
0VAL_TYPE Valuation type no no
0MATERIAL Material number yes no
0DIVISION Division no no
0MATL_GROUP Material group no no
0MATL_TYPE Material type no no
0PROD_HIER Product hierarchy no no
0CATEG Category in the Material Ledger
data display
no no
0PROCCATEG Process category no no
0DOC_NUMBER Sales document no no
0S_ORD_ITEM Sales document item no no
ment (WBS element)
no no
Key Figures:
InfoObject Description InfoObject unit Aggregation
0AMOUNT Amount 0CURRENCY SUM
0EXRTDIFF_M Multi-level exchange rate differences 0CURRENCY SUM
Page 82
0EXRTDIFF_S Single-level exchange rate differ-
ences
0CURRENCY SUM
0PRICDIFF_M Multi-level price differences 0CURRENCY SUM
0PRICDIFF_S Single-level price differences 0CURRENCY SUM
0QUANTITY Quantity 0UNIT SUM
Units:
InfoObject Description Category
Notes on the InfoCube:
Never calculate a sum using different currency keys or valuations, as it can lead to incorrect results in the query.
Always use a filter for the currency key and valuation key.
Notes on update ruIes:
The fiscal year and period are taken from the fiscal year period field.
Page 83
1.4 IM Investment Management
1.4.1 IM-FA CapitaI Investments
1.4.1.1 InfoCube: 0IMFA_1: Assigned PIan Budget
Content:
This InfoCube contains the plan, budget and assigned values of investment programs and their assigned measures
(orders and projects).
InfoSource(s):
0IM_FA_IP_1: Program Position: Plan
0IM_FA_IP_2: Program Position: Budget
0IM_FA_IP_8: Assignment of Orders
0IM_FA_IP_9: Assignment of Projects
0CO_OM_OPA_2: Orders: Budget
0CO_OM_OPA_3: Orders: Overall/Annual Plan Values
0CO_OM_WBS_1: WBS Element: Costs
0CO_OM_WBS_2: WBS Element: Budget
0CO_OM_WBS_3: WBS Element: Plan
0CO_OM_NTW_1: Network: Costs
0CO_OM_NWA_1: Network activity: Costs
Characteristics:
ExternaI hierarchy
avaiIabIe?
0APPR_YEAR Approval year No No
0PROG_DEF Program definition (name in
OLTP)
No No
0PROG_DEF_S Program definition No No
0PROG_POS Program position Yes Yes
Page 84
0COORDER Order number (CO order) Yes No
0WBS_AS_ELE WBS element Yes No
0IM_OBJ Object type (IM) No No
0NEW_OLD Indicator
balance forward/current/forecast
No No
0DB_CR_IND Sender/receiver indicator No No
Key figures:
behavior
Units:
When you have investment programs whose description in the OLTP system is more than four characters, you
have to rename them in the Implementation Guide for the Business Information Warehouse. For more information,
refer to the BW Implementation Guide.
Interpretation of measure assignments when loading data
When loading measure values, a maximum of two programs can be updated using the assignments available in the
ODS.
As a rule, the most current requests for a program are used to update the data, as well as the two programs with
the most recent approval years.
Example:
The following requests for InfoSource 0IM_FA_IP_8, order assignment, are available in the ODS for the logical
system APT/100:
Page 85
Program Date Time Most recent re-
quests
Most recent ap-
provaI year
INVEST/1998 01/11/1999 17:11:41 +++ +++
INVEST/1998 01/11/1999 12:11:12
INVEST/1997 01/11/1999 14:41:17 +++ +++
INVEST/1997 01/10/1999 07:14:51
INVEST/1996 01/23/1999 07:43:59 +++
INVEST/1995 01/20/1999 06:32:54 +++
Result: The most recent requests of the most recent approval years (1997 or 1998) dated 01/11/1999 at 17:11
hours and 14:41 hours are in the ODS.
The monitor of the InfoPackage log specifies which requests of the ODS were used for measure assignment when
loading the data (log subsection Data-IDoc / Package update).
CAUTION: The percentage assignment of investment measures to program positions, which has been available
since release 4.0, is currently not represented in the BW. The system assigns a measure to the pro-
gram position for which it has the highest percentage program assignment, and the measure is then
assigned at 100%. The multiple assignment by percentage is noted in the monitor in the log of the In-
foPackage.
1. Changes to data structures supplied by the InfoSource
When updating the data of the InfoSource in the InfoCube, the structure of the data is adapted to the particular
requirements of program reporting because of the update rules. The main changes are explained below:
1.1. Reading program assignments for measures
The possible assignment of measures to an investment program is read in the ODS for all InfoSources. Only data
records for those measures that have a program assignment are adopted.
1.2. Aggregation of the assigned objects to projects
For investment projects, the values are aggregated in the InfoCube on the WBS element that is assigned directly to
the investment program. This applies for all values that were posted on lower level WBS elements or objects as-
signed to these WBS elements (orders, networks and network activities).
It is therefore not possible to expand the structure according to these objects.
1.3. Correction records for budget values and planned values for measures
Adding the budget and planned values for measures and program positions is not allowed, as this would result in
an incorrect overall budget value. The system distinguishes the values using the object type (IM), InfoObject
0IM_OBJ. Negative reversal records are also written, as documented in the following example.
Example:
Order 600517 is assigned to program position LAPTOPS with a budget value of 500. The program position has a
budget value of 1000.
The following records are updated in the InfoCube:
Page 86
0PROG_POS 0COORDER 0IM_OBJ 0AMOUNT
LAPTOPS IP 1000
LAPTOPS - 300
LAPTOPS 600517 ME 300
Using the query, you see the following when you drill down the program position according to orders:
Budget program
(0IM_OBJ = IP)
Budget measure
(0IM_OBJ = ME)
Budget
(0IM_OBJ any)
LAPTOPS 1000 700
600517 300 300
Total 1000 300 1000
All key figures displayed can therefore by aggregated hierarchically without any restrictions.
2. Short description of the update rules applied
2.1 Key figure calculation
NEGATIVE
The negative value is adopted.
The rule is used to generate the reversal records mentioned above.
NEGATIVE_PLAN
The negative value is used for planned values.
The rule is used to generate the reversal records mentioned above for the InfoSources that contain assigned val-
ues as well as planned values.
2.2 Characteristic calculation
INITIAL
The initial value of the InfoObjects is adopted.
OBJECT_MEASURE
The object type (IM), 0IM_OBJ, is identified with the value ME for measure.
OBJECT_PROGRAM
The object type (IM), 0IM_OBJ, is identified with the value IP for investment program position.
ASS_<InfoObject>_1
Page 87
The value of the InfoObjects <InfoObject>_1 is adopted for the corresponding measure for the assignment to the
first updated program from the ODS. If no such assignment exists, no update is made. The values for orders are
taken from the ODS data for InfoSource 0IM_FA_IP_8, and the values for projects from InfoSource 0IM_FA_IP_9.
ASS_<InfoObject>_2
Updating occurs as for ASS_<InfoObject>_2, however for the second program updated.
Comments on the queries
Note: Activating the presentation hierarchy in a query:
The following reports require a presentation hierarchy (program hierarchy) for the characteristic 0PROG_POS in
order to display the data in a meaningful way.
Currently you cannot freely specify the presentation hierarchy of a query at runtime. You have to define it in the
query definition. However, this can only be done in the customer system since the hierarchy name is not known
beforehand.
Carry out the following procedure:
1. Call the query in the Business Explorer Analyzer.
2. Choose the Change query icon.
3. Choose the Extended change icon.
4. Press the right mouse button on Program position.
5. Choose the Attributes function.
6. Choose the required presentation hierarchy using the entry help (the hierarchy must already have been loaded
from the OLTP and activated).
7. Set the presentation hierarchy to active.
8. Save the changed query as a new query using Save as.
Note:
Replace the SAP exit variables for program names and authorization year in the filter with fixed values for the pro-
gram, and replace the hierarchy variable 0H_PROG in the selections for the program position by the name of the
program hierarchy.
1.4.1.1.1 Query: 0IMFA_C01_Q001: PIan for investment program and measures
Purpose:
This query displays the planned values for the investment program and measures (for controlling the plan distribu-
tion in the program hierarchy), from the program to the measures as well as within the yearly cycle.
Structure:
Key figure Comments
Plan for program item Planned values of the investment program positions
Plan for measures Planned values of the measures
Time structure Comments
Overalll Overall value
Page 88
Reference year Value in reference year
Reference year + 1
Reference year + 2
All following Total of the values in all the following years
Any reference year can be entered in the selection screen.
0WBS_AS_ELE WBS element
1.4.1.1.2 Query: 0IMFA_C01_Q002: Budget for investment program and measures
Purpose:
This query displays the budget values on the investment program and on the measures (for controlling budget dis-
tribution in the program hierarchy), from the program to the measures as well as within the yearly segments.
Structure:
Key figure Comments
Budget for program item Budget values of the investment program positions
Budget for measures Budget values of the measures
Time structure Comments
Overall Overall value
Reference year Value in reference year
Reference year + 1
Reference year + 2
All following Total of the values in all the following years
Any reference year can be entered in the selection screen.
Page 89
0VTDETAIL Details of value type
Comments:
The budget can be expanded to show the original budget and the updated budget by displaying the details of the
value type.
1.4.1.1.3 Query: 0IMFA_C01_Q003: AvaiIabIe pIan
Purpose:
This query shows the availability in relationship to the plan values.
Structure:
Key figure Comments
Plan Plan values of the program positions and measures
Assigned Actual + commitment
Available Plan - assigned
Actual Actual values on the measures
Commitment Commitments on the measures
0FISCYEAR Business year
1.4.1.1.4 Query: 0IMFA_C01_Q004: AvaiIabIe budget
Purpose:
This query shows the availability in relationship to the budget values.
Structure:
Key figure Comments
Budget Budget values of the program positions and measures
Page 90
Assigned Actual + commitment
Available Budget assigned
Actual Actual values on the measures
Commitment Commitments on the measures
0VTDETAIL Details of value
Comments:
The budget can be expanded to show the original budget and the updated budget by displaying the details of the
value type.
Page 91
1.5 EC Enterprise ControIIing
1.5.1 EC-PCA Profit Center Accounting
1.5.1.1 InfoCube: 0PCA_C01: PCA Transaction data
Content:
This InfoCube contains all of the period totals for profit and loss accounts and balance sheet accounts from Profit
Center Accounting (PCA), which were loaded from the affiliated source system(s).
InfoSource(s):
0EC_PCA_1 Profit Center: Transaction data
Characteristics:
ExternaI hierarchy
avaiIabIe?
0ACCOUNT Account number Yes Yes
0FUNC_AREA Functional area No No
0PART_PRCTR Partner profit center No Yes
0PROFIT_CTR Profit center No Yes
0VTYPE Value type for Reporting No No
0ORIG_PCA Type of origin object in PCA No No
0PCOMPANY Partner company number No No
0PFUNC_AREA Partner functional area No No
0PLANT Plant Yes No
0PORIG_PCA Partner origin object in PCA No No
0REP_MATL Representative material for PCA No No
Page 92
0SCOPE Object class No No
0VERSION_RA Results analysis version No No
Key figures:
behavior
0BALANCE Accumulated balance 0CURRENCY Semi-additive
0CREDIT Total credit postings 0CURRENCY Additive
0DEBIT Total debit postings 0CURRENCY Additive
0QUANTITY Quantity 0UNIT Additive
Units:
To analyze the period totals for profit and loss accounts, use key figure 0DEBIT for debit postings and 0CREDIT for
credit postings. The balance is the total of 0CREDIT and 0DEBIT.
For the balance in balance sheet accounts, use key figure 0BALANCE.
Comments on the update ruIes: ----
1.5.1.1.1 Query: 0PCA_C01_Q0004: PIan/actuaI variance - profit and Ioss accounts
Purpose:
With this query, you can analyze plan and actual values for all profit and loss accounts, as well as their abso-
lute/percentage variance.
Page 93
Structure(s):
Key figure Comments
Plan Total plan postings
Actual Total actual postings
Variance Actual Plan
Variance (%) Variance / Plan
0FUNC_AREA Functional area
0PROFIT_CTR Profit center
0PART_PRCTR Partner profit center
0ACCOUNT Account number
1.5.1.1.2 Query: 0PCA_C01_Q0008: PIan/actuaI profit center comparison - resuIt
Purpose:
With this query, you can compare plan and actual postings to the profit and loss accounts of two profit centers.
Absolute and percentage variances are displayed.
Structure(s):
Key figure Comments
Profit center 1
Plan Total plan postings to profit center 1
Actual Total actual postings to profit center 1
Profit center 2
Plan Total plan postings to profit center 2
Actual Total actual postings to profit center 2
Variance Profit Center 1 - Profit center 2
Plan
Actual
Variance (%) Variance / Profit center 1
Page 94
Plan
Actual
1.5.1.1.3 Query: 0PCA_C01_Q0001: PIan version comparison - resuIt
Purpose:
With this query, you can compare planning in the profit and loss accounts of two plan versions. Absolute and per-
centage variances are displayed.
Structure(s):
Key figure Comments
Plan version 1 Total plan postings for plan version 1
Plan version 2 Total plan postings for plan version 2
Variance Plan version 1 Plan version 2
Variance (%) Variance / Plan version 1
0PROFIT_CTR Profit Center
Page 95
1.5.1.1.4 Query: 0PCA_C01_Q0003: PIan/actuaI period comparison - resuIt
Purpose:
With this query, you can compare plan and actual values in the profit and loss accounts of two periods. Absolute
and percentage variances are displayed.
Structure(s):
Key figure Comments
Period 1
Plan Total plan postings in period 2
Actual Total actual postings in period 1
Period 2
Plan Total plan postings in period 2
Actual Total actual postings in period 2
Variance Period 1 - Period 2
Plan
Actual
Variance (%) Variance / period 1
Plan
Actual
1.5.1.1.5 Query: 0PCA_C01_Q0007: Current period/YTD/compIete year - resuIt
Purpose:
With this query, you can display the following profit-related values: plan and actual postings for the current period,
accumulated plan and actual values for the year to date, plan values for the complete year and the difference be-
tween these and actual postings to date.
Page 96
Structure(s):
Key figure Comments
Plan current period Plan postings for the current period
Actual current period Actual postings for the current period
Plan YTD Accumulated plan values for all periods for the year to date
Actual YTD Accumulated actual postings to date
Plan complete year Plan postings for the complete year
Available Plan complete year - Actual YTD
1.5.1.1.6 Query: 0PCA_C01_Q0005: Time comparison actuaI resuIt
Purpose:
With this query, you can compare actual postings to profit and loss accounts for all eight quarters of two fiscal
years, together with the two fiscal year totals.
Structure(s):
Key figure Comments
Fiscal year 1
Actual complete year
Actual 1
st
quarter
Actual 2
nd
quarter
Actual 3
rd
quarter
Actual 4
th
quarter
Fiscal year 2
Actual complete year
Page 97
Actual 1
st
quarter
Actual 2
nd
quarter
Actual 3
rd
quarter
Actual 4
th
quarter
1.5.1.1.7 Query: 0PCA_C01_Q0006: Time comparison pIan resuIt
Purpose:
With this query, you can compare plan postings to profit and loss accounts for all eight quarters of two fiscal years,
together with the two fiscal year totals.
Structure(s):
Key figure Comments
Fiscal year 1
Plan complete year
Plan 1
st
quarter
Plan 2
nd
quarter
Plan 3
rd
quarter
Plan 4
th
quarter
Fiscal year 2
Plan complete year
Plan 1
st
quarter
Plan 2
nd
quarter
Plan 3
rd
quarter
Plan 4
th
quarter
Page 98
1.5.1.1.8 Query: 0PCA_C01_Q0012: PIan/actuaI/variance - baIance sheet accounts
Purpose:
With this query, you can analyze plan and actual values of balance sheet accounts and their absolute/percentage
variance.
Structure(s):
Key figure Comments
Plan Plan balance of balance sheet accounts
Actual Actual balance of balance sheet accounts
Variance Actual Plan
1.5.1.1.9 Query: 0PCA_C01_Q0009: Profit after capitaI costs
Purpose:
This query calculates the key figure "Profit after capital costs" on the basis of the profit and loss accounts and bal-
ance sheet accounts. It provides a comparison of the plan and actual value of Profit after captial costs.
A market interest rate must be set for the calculation. The capital costs are then subtracted from the operating
profit. These capital costs represent interest on fixed capital raised at the market interest rate.
Page 99
Structure(s):
Key figure Comments
Result Alternatively, define an account group in R/3 or in BW.
Plan
Actual
Fixed capital Alternatively, define an account group in R/3 or in BW.
Plan
Actual
Capital costs Market interest in percent * fixed capital / 100
Plan
Actual
Profit after capital costs Result - Capital costs
Plan
Actual
1.5.1.1.10 Query: 0PCA_C01_Q0010: Return on Investment
Purpose:
This query calculates the key figure "Return on Investment" (ROI) on the basis of the profit and loss accounts and
balance sheet accounts. It provides a comparison of the plan and actual value of the Return on Investment.
Structure(s):
Key figure Comments
Result Alternatively, define an account group in R/3 or in BW.
Plan
Actual
Page 100
Fixed capital Alternatively, define an account group in R/3 or in BW.
Plan
Actual
ROI Result / Fixed capital
Plan
Actual
1.5.1.2 InfoCube: 0PCA_C02 PCA: StatisticaI key figures
Content:
This InfoCube contains all statistical key figures from Profit Center Accounting (PCA), which are loaded from the
affiliated source system(s).
InfoSource(s):
0EC_PCA_2 Profit Center: Statistical key figures
Characteristics:
ExternaI hierarchy
avaiIabIe?
0PROFIT_CTR Profit Center No Yes
0VTYPE Value type for Reporting No No
0ORIG_PCA Type of origin object in PCA No No
Page 101
Key figures:
havior
0QUANTITY Quantity 0UNIT Additive
0QUANT_AVRG Stock quantity 0UNIT Non-additive
Units:
For statistical key figures of fixed value type (employees, for example) use key figure 0QUANT_AVRG.
For statistical key figures of total value type (telephone units for example) use key figure 0QUANTITY.
Comments on the update ruIes: ---
1.5.1.2.1 Query: 0PCA_C02_Q0001: StatisticaI key figures
Purpose:
With this query, you can compare plan and actual values for all statistical key figures (both fixed value type and
total value type).
Structure(s):
Key figure Comments
Plan Planned values of statistical key figures
Actual Actual values of statistical key figures
Variance Plan - Actual
Page 102
1.5.2 EC- CS LegaI ConsoIidation
1.5.2.1 InfoCube: 0ECCS_C01: Transaction data
Content:
This InfoCube contains all the transaction data uploaded from the source system(s) for consolidation. The data is
present both in the form of period balances and non-cumulative values.
InfoSource(s):
0EC_CS_1
Characteristics:
InfoObject Description Navigation attrib-
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0CS_DIMEN Dimension No No
0CS_VERSION Version No No
0CS_HDATFR Hierarchy from No No
0CS_HDATTO Hierarchy to No No
0CS_CHART Consolidation chart of accounts No No
0CS_ITEM Item No Yes
0CS_GROUP Consolidation group No Yes
0CS_UNIT Consolidation unit No No
0CS_SITEMCT Subitem category No No
0CS_SITEM Subitem No No
0ACQ_YEAR Acquisition year No No
0ACQ_PER Period 1. acquisition No No
Page 103
0CS_PARTNER Partner unit No No
0CS_INVESTE Investee No No
0CS_PLEVEL Posting level No No
0CS_DOCTYPE Document type No No
Key figures:
InfoObject Description Units
InfoObject
Aggregation
behavior
0CS_TRN_LC Sum of transactions LC 0CURKEY_LC Additive
0CS_TRN_GC Sum of transactions GC 0CURKEY_GC Additive
0CS_TRN_TC Sum of transactions TC 0CURKEY_TC Additive
0CS_TRN_QTY Sum of transactions 0UNIT Additive
0CS_YTD_LC YTD in local currency 0CURKEY_LC Additive
0CS_YTD_GC YTD in group currency 0CURKEY_GC Additive
0CS_YTD_TC YTD in transaction currency 0CURKEY_TC Additive
0CS_YTD_QTY YTD quantity 0UNIT Additive
Units:
0CURKEY_LC Local currency Currency
0CURKEY_GC Group currency Currency
0CURKEY_TC Transaction currency Currency
The transaction data in the application EC-CS is dependent on a consolidation group hierarchy. Since this itself is
time-dependent, the characteristics 0CS_HDATFR and 0CS_HDATTO must be transferred to the filter together
with the variables 0P_CSHF (Hierarchy from (SAP Exit)) or 0P_CSHT (Hierarchy to (SAP Exit)). These variables
are derived from the query key date and replaced using a SAP Exit. Only this way can you guarantee that the cor-
rect data is displayed.
Furthermore, a variable 0P_CSDAT is defined for the query key date. If this variable is not used, the current date is
automatically used as the query key date. Both the validity interval for a consolidation group hierarchy (that may be
used) and the two variables mentioned above are derived from the query key date.
Page 104
To use a restricting consolidation group hierarchy, you should use the variables 0H_CG or
0N_CG/0N_CG1/0N_CG2 for the hierarchy name or hierarchy node. The hierarchys validity date remains free and
is automatically replaced by the query key date.
When using cumulative key figures, you should ensure that the fiscal year/period is defined exactly. This is be-
cause of the aggregation behavior. You therefore eliminate any implicit cumulation with regard to time. This would
lead to incorrect results.
The cumulative key figures are not automatically available for all periods. If, in OLTP EC-CS, consolidation fre-
quencies are defined for all consolidation groups in all versions and dimensions, then the cumulative results are
available for the most detailed closing periods. Otherwise the cumulative values for all periods are transferred into
the Cube.
1.5.2.1.1 Query: 0ECCS_C01_Q001: Current year with structure -% BaIance sheet
Purpose:
This query serves to display the cumulative transaction data from a fiscal year for the balance sheet, and to show
the percentage share of the total assets/liabilities in each case.
Structure:
Key figure Comments
YTD quantity in GC For selected fiscal year/period (to be entered on selection screen)
% share % share of total assets/liabilities
0CS_UNIT Consolidation unit
0CS_SITEM Subitem
0CS_ITEM Item (vertical breakdown)
1.5.2.1.2 Query: 0ECCS_C01_Q002: Previous year comparison with variance
Purpose:
This query serves to display the cumulative transaction data from a fiscal year and the previous year, and also to
show the absolute and percentage variances.
Structure:
Key figure Comments
YTD quantity in GC FY For selected fiscal year/period (to be entered on selection screen)
YTD quantity in GC Prev. Yr For the previous year (determined from the fiscal year entered)
Page 105
Absolute variance Previous year - Fiscal year
Relative variance (Previous year - Fiscal year) / Fiscal year * 100
0CS_SITEM Subitem
1.5.2.1.3 Query: 0ECCS_C01_Q003: MuIti-year comparison
Purpose:
This query serves to display the cumulative transaction data in a five-year comparison.
Structure:
Key figure Comments
YTD quantity in GC FY For selected fiscal year/period (to be entered on selection screen)
YTD quantity in GC FY -1 For the fiscal year entered 1 (determined automatically)
0CS_SITEM Subitem
1.5.2.1.4 Query: 0ECCS_C01_Q004: Quarter comparison
Purpose:
This query serves to display the transaction data from a quarter and another comparison quarter, and also to show
the absolute and percentage variances.
Page 106
Structure:
Key figure Comments
Quarter Period balances in GC for the selected Quarter (last period of quarter to be
entered on selection screen)
Comparison quarter Period balances in GC for the selected comparison quarter (last period of
comparison quarter to be entered on selection screen)
Absolute variance Comparison quarter - Quarter
Relative variance (Comparison quarter - Quarter) / Quarter * 100
0CS_SITEM Subitem
1.5.2.1.5 Query: 0ECCS_C01_Q005: Month comparison
Purpose:
This query serves to display the period values for any two months, and also to show the absolute and percentage
variances.
Structure:
Key figure Comments
Period Period balances for the selected period (to be entered on selection screen)
Comparison period Period balances for the selected period (to be entered on selection screen)
Absolute variance Comparison period - Period
Relative variance (Comparison period - Period) / Period * 100
0CS_SITEM Subitem
Page 107
1.5.2.1.6 Query: 0ECCS_C01_Q006: Comparison IocaI/group currency
Purpose:
This query serves to display the cumulative transaction data for a consolidation unit in local and group currencies
for the aggregated balance sheet, and shows the resulting exchange rate.
Structure:
Key figure Comments
YTD quantity in LC For the selected fiscal year (to be entered on selection screen)
YTD quantity in GC For the selected fiscal year (without eliminating entries)
Exchange rate Group currency / local currency
0CS_SITEM Subitem
1.5.2.1.7 Query: 0ECCS_C01_Q007: Version comparison
Purpose:
This query serves to display the cumulative transaction data from two versions, and also to show the absolute and
percentage variances.
Structure:
Key figure Comments
Version YTD quantity in GC for the selected fiscal year and version (to be entered
on selection screen)
Comparison version YTD quantity in GC for the selected fiscal year and comparison version (to
be entered on selection screen)
Absolute variance Comparison version - Version
Relative variance (Comparison version - Version) / Version * 100
0CS_SITEM Subitem
Page 108
1.5.2.1.8 Query: 0ECCS_C01_Q008: ConsoIidation unit comparison
Purpose:
This query serves to display the cumulative transaction data column by column from all consolidation units of a
consolidation group.
Structure:
Key figure Comments
YTD quantity in GC For the selected fiscal year (to be entered on selection screen)
0CS_SITEM Subitem
0CS_UNIT Consolidation unit (horizontal breakdown)
1.5.2.1.9 Query: 0ECCS_C01_Q009: ConsoIidation group comparison
Purpose:
This query serves to compare the cumulative transaction data for two consolidation groups, and to display the ab-
solute and percentage variances.
Structure:
Key figure Comments
Consolidation group 1 YTD quantity in GC for the selected fiscal year and the selected consolida-
tion group 1 (to be entered on selection screen)
Consolidation group 2 YTD quantity in GC for the selected fiscal year and the selected consolida-
tion group 2 (to be entered on selection screen)
Absolute variance Consolidation group 2 Consolidation group 1
Relative variance (Consolidation group 2 Consolidation group 1) / Consolidation group 1 *
100
0CS_SITEM Subitem
Page 109
1.5.2.1.10 Query: 0ECCS_C01_Q010: ConsoIidation unit/ConsoIidation group compari-
son
Purpose:
This query serves to compare the cumulative transaction data for a consolidation unit and a consolidation group, to
display the absolute variance, and also to show the consolidation units share of the consolidation group.
Structure:
Key figure Comments
Consolidation unit YTD quantity in GC for the selected fiscal year and the selected consolida-
tion unit (to be entered on selection screen)
Consolidation group YTD quantity in GC for the selected fiscal year and the selected consolida-
tion group (to be entered on selection screen)
Absolute variance Consolidation group Consolidation unit
CU share of CG in % Consolidation unit / Consolidation group * 100
0CS_SITEM Subitem
1.5.2.1.11 Query: 0ECCS_C01_Q011: DeveIopment of ConsoIidated vaIue (IocaI vaIua-
tion)
Purpose:
This query serves to display the cumulative transaction data in the historical development of the reported financial
data through standardizing entries, eliminating entries for IU payables and receivables, eliminating entries for in-
vestment income, and consolidation of investment postings right up to the consolidated value.
Structure:
Key figure Comments
Reported financial data YTD quantity in GC for the selected fiscal year (to be entered on selection
screen) for the posting levels Space and 00
Standardizing entries YTD quantity in GC for the selected fiscal year (to be entered on selection
screen) for document type 15
Eliminating entries for IU
payables and receivables
YTD quantity in GC for the selected fiscal year (to be entered on selection
Elimination of investment
income
YTD quantity in GC for the selected fiscal year (to be entered on selection
Page 110
Consolidation of investments YTD quantity in GC for the selected fiscal year (to be entered on selection
Consolidated value Reported financial data + Standardizing entries + Eliminating entries for IU
payables and receivables + Elimination of investment income + Consolida-
tion of investments
0CS_GROUP Consolidation group
0CS_PARTNER Partner unit
1.5.2.1.12 Query: 0ECCS_C01_Q012: SaIes by region
Purpose:
This query serves to list in the columns the cumulative transaction for the sales items by region.
Structure:
Key figure Comments
Cum. value in GC For the selected fiscal year (to be entered on selection screen)
0CS_SITEM Subitem (horizontal breakdown by region compound characteristic Su-
bitem type 0CS_SITEMCT value 4 (= region) saved permanently)
1.5.2.1.13 Query: 0ECCS_C01_Q013: I/S by functionaI area
Purpose:
This query serves to list the cumulative transaction data for income statement items in the columns by functional
area.
Structure:
Key figure Comments
Cum. value in GC For the selected fiscal year (to be entered on selection screen)
Page 111
0CS_SITEM Subitem (horizontal breakdown by region compound characteristic Su-
bitem type 0CS_SITEMCT value 2 (= functional area) saved permanently)
1.5.2.1.14 Query: 0ECCS_C01_Q014: Asset history sheet
Purpose:
This query serves to display the cumulative transaction data for the fixed asset items in their horizontal develop-
ment (from opening inventory to closing inventory) for one consolidation unit.
Structure:
Key figure Comments
Opening inventory YTD quantity in GC for the selected fiscal year (to be entered on selection
screen) and subitems 100 and 200 of subitem type 1 (= fixed asset trans-
action types)
Acquisitions YTD quantity in GC for the selected fiscal year (to be entered on selection
action types)
Divestitures YTD quantity in GC for the selected fiscal year (to be entered on selection
action types)
Transfers YTD quantity in GC for the selected fiscal year (to be entered on selection
action types)
Closing inventory Opening inventory + Acquisitions + Divestitures + Transfers
Page 112
2 Human Resources
2.1 PA-PA PersonneI Administration
2.1.1 InfoCube: 0PA_C01: Headcount and PersonneI Actions
Content:
The InfoCube Headcount and Personnel Actions (0PA_C01) contains all transaction data based on headcount and
personnel actions. The data in this InfoCube is extracted from the InfoSources Employee (0HR_PA_0) and Per-
sonnel Actions (0HR_PA_1).
The InfoCube contains, among other things, the general key figures Number of Employees (0HDCNT_LAST),
Number of Personnel Actions (0ACTION_CNT), and Headcount FTE (0HDCNT_FTE). Restricted key figures that
take certain personnel action types into account (e.g.Hiring, Leaving) or show the Entries or Leavers FTE, or those
that show the Number of Full or Part-Time Workers are also contained in the standard R/3 System. The following
time dimensions are available for evaluation purposes (as well as others): "Calendar day", "Calendar year/month",
"Calendar year/quarter", and "Calendar year".
You can evaluate these key figures according to various criteria:
Personal data (e.g. nationality, gender, language)
Organizational data (e.g. personnel area, employee group, organizational unit)
Additional templates/structures containing key figures or certain calculation rules for the InfoCube are contained in
the standard R/3 System. These templates enable you to quickly and easily carry out frequently-required evalua-
tions, such as those used to determine the leaving rate or to compare the headcount of the current and previous
years (with absolute and percentage differences).
For more information on the technical elements (characteristics, time characteristics, etc) of the InfoCubes, refer to
Remarks on the InfoCube.
InfoSource(s):
0HR_PA_0: Employee
0HR_PA_1: Personnel Actions
Characteristics:
InfoObject Description Navigation charac-
teristics avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0EMPLOYEE Employee No No
0PERSON Person No No
0ACTIONTYPE Action type No No
0ACTIONREAS Reason for action No No
0PERS_AREA Personnel area No No
0PERS_SAREA Personnel subarea No No
0AGE_RANGE Age range No No
0COUNTY_CDE County code No No
Page 113
0GENDER Gender No No
0AGE Age No Yes - using CSV file
0NATION Nationality No No
0POSTAL_CD Postal code No No
0REGION Region (state, province, county) No No
0PERSLANGU Language No No
0CO_MST_AR Master cost center controlling
area
No No
0MAST_CCTR Master cost center No Yes
0ORGUNIT Organizational unit No Yes
0HRPOSITION Position No No
0JOB Job No No
0PAYPCT_CHA Capacity utilization level No Yes - using CSV file
0EMPLSTATUS Employment status No No
0EMPLGROUP Employee group No No
0EMPLSGROUP Employee subgroup No No
0PAYRL_AREA Payroll accounting area No No
0COUNTRY_ID Country grouping No No
0ESGFORCAP Employee subgroup grouping for
payscale provision
No No
0PAYSCALETY Pay scale type No No
0PAYSCALEAR Pay scale area No No
0PAYSCALEGR Pay scale group No No
0PAYSCALELV Pay scale level No No
0CALMONTH Calendar day/month
0CALQUARTER Calendar day/quarter
0CALMONTH2 Calendar month
0CALQUART1 Quarter
Key Figures:
InfoObject Description InfoObject units Aggregation be-
havior
0ACTION_CNT Number of personnel actions Additive
0HDCNT_LAST Number of employees Last
Page 114
0AGE_KYF Age in years Last
0PAYPCT Capacity utilization level in per-
cent
Last
0HDCNT_FTE Headcount FTE Last
Restricted Key Figures:
0R_PA_003 Entries FTE Headcount FTE
restricted to person-
nel action type En-
tries
0R_PA_001 Number of Entries Number of person-
nel actions restricted
to personnel action
type Hiring
0R_PA_006 Number of Part-Time Workers Number of workers
with a capacity utili-
zation level <99%
0R_PA_005 Number of Full-Time Workers Number of workers
with a capacity utili-
zation level that =
100%
0R_PA_002 Number of Leavers Number of person-
nel actions restricted
to personnel action
type Leaving
0R_PA_004 Leavers FTE Headcount FTE
restricted to the
personnel action
type Leaving
TempIates/Structures:
TechnicaI Name Description EIement FormuIa
Previous year
(&0T_CYEAR&)
Previous year = current calendar
year - 1
(&0CYEAR&-1)
Current calendar year
(&0T_CYEAR&)
Current calendar year = variable
calendar year
(&0CYEAR&)
Difference Difference = current calendar year
- previous year
0QT_PA_001 Compare previ-
ous year and
current year
Difference in % Difference in % = (current calen-
dar year - previous year) / previ-
ous year * 100
0QT_PA_009 Last 4 quarter
comparison
Current quarter - 4
(&0T_CQUAT&-4)
Current quarter - 4
(&0CQUART&-4)
Page 115
Current quarter - 3
(&0T_CQUAT&-3)
Current quarter - 3
(&0CQUART&-3)
Current quarter - 2
(&0T_CQUAT&-2)
Current quarter - 2
(&0CQUART&-2)
Current quarter - 1
(&0T_CQUAT&-1)
Current quarter - 1
(&0CQUART&-1)
Current quarter - 4
(&0T_CQUAT&-4)
Current quarter - 4
(&0CQUART&-4)
Current quarter - 3
(&0T_CQUAT&-3)
Current quarter - 3
(&0CQUART&-3)
Current quarter - 2
(&0T_CQUAT&-2)
Current quarter - 2
(&0CQUART&-2)
Current quarter - 1
(&0T_CQUAT&-1)
Current quarter - 1
(&0CQUART&-1)
0QT_PA_010 Average last 4
quarters
Average 4 quarters of the quarterly value / 4
Headcount FTE 0QT_PA_011 Percentage
Breakdown of
Headcount FTE
Percentage distribution
of headcount FTE
Percentage distribution of
headcount FTE = headcount FTE
per feature value / total headcount
FTE * 100
1
st
quarter of previous year
Quarter (0CALQUART1) re-
stricted to 1 and &0CYEAR&-1
2
nd
3
rd
4
th
0QT_PA_012 Average 4 quar-
ters - previous
year
Average 4 quarters -
previous year
of the quarterly values (previous
year) / 4
0QT_PA_013 Comparison of 4
quarters - previ-
ous year
1
st
Page 116
2
nd
3
rd
4
th
January previous year
Month (0CALMONTH2) restricted
to 1 and &0CYEAR&-1
February previous year
to 2 and &0CYEAR&-1
December previous year

to 12 and &0CYEAR&-1
0QT_PA_014 Average 12
months previous
year
Average 12 months
previous year
of the monthly values (previous
year) / 12
to 1 and &0CYEAR&-1
to 2 and &0CYEAR&-1
0QT_PA_015 Comparison 12
months previous
year
Number of employees
Total age in years
0QT_PA_006 Employees' Av-
erage Age
Employees' average
age
Employees' average age = total
age in years / number of employ-
ees
Page 117
Number of employees 1
st
quarter
previous year
Number of employees, quarter
(0CALQUART1) restricted to 1
and &0CYEAR&-1
nd
quarter
previous year
and &0CYEAR&-1
rd
quarter
previous year
and &0CYEAR&-1
th
quarter
previous year
and &0CYEAR&-1
(Average headcount
previous year)
year) / 4
Number of Entries
(previous year)
Number of entries (previous year)
(&0CYEAR&-1)
0QT_PA_017 Entry Rate
Entry rate
Entry rate = number of entries
(previous year) / average
headcount (previous year) * 100
Number of Entries
Number of Leavers
0QT_PA_003 Net Entry Rate
Net Entry Rate
Net entry rate = number of entries
/ number of leavers
st
quarter
previous year
and &0CYEAR&-1
0QT_PA_016 Leaving Rate
nd
quarter
previous year
and &0CYEAR&-1
Page 118
rd
quarter
previous year
and &0CYEAR&-1
th
quarter
previous year
and &0CYEAR&-1
Average Headcount
(previous year)
year) / 4
Number of Leavers
(previous year)
Number of leavers (previous year)
(&0CYEAR&-1)
Leaving Rate
Leaving rate = number of leavers
Number of Employees 0QT_PA_005 Percentage
Breakdown of
Employees Percentage Breakdown
of Employees
Percentage breakdown of em-
ployees = number of employees
per characteristic value / total
number of employees * 100
Number of Entries 0QT_PA_008 Percentage
Breakdown of
Entries
Percentage Breakdown
of Entries
Percentage breakdown of entries
= number of entries per charac-
teristic value / total number of
entries * 100
Number of Leavers 0QT_PA_007 Percentage
breakdown of
Leavers Percentage Breakdown
of Leavers
Percentage breakdown of leavers
= number of leavers per charac-
leavers* 100
Page 119
Characteristics
Age Range (0AGE_RANGE) and Age in Years (0AGE) are calculated characteristics.
The Age Range characteristic contains an employees age, which is calculated from the date of birth and the
period in the relevant InfoSource. The ranges are specified by the update rules.
Note that you must manually maintain the master data for this characteristic as follows:
0 not available
1 < 20
2 20 - 29
3 30 - 39
4 40 - 49
5 50 - 59
6 60 - 69
7 70
The Age in Years characteristic contains an employees age at the end of the period. You can (depending on
your individual enterprise requirements) define a hierarchy for age and thereby depict the age profile in your
enterprise. You can use this characteristic (0AGE_KYF) to make calculations based on employees age in
years.
The age characteristics are calculated at the end of the period using the update rules. The period is dependent on
the InfoSource used**. For example, the period end can fall either at the end of a calendar day or a calendar
month, depending on which InfoSource you are using.
A person can have multiple assignments within an enterprise. To be able to distinguish between employee rela-
tionships (Employees = 0EMPLOYEE) and real people (0PERSON), the person is deemed an attribute of the em-
ployee.
Hierarchies
If hierarchies exist for the InfoObjects Organizational Unit (0ORGUNIT) and Master Cost Center (0MAST_CCTR),
you can activate them using the Attributes function. This allows you to depict hierarchical, multi-level aggregations.
Hierarchies are defined for the Age (0AGE) and Capacity Utilization Level (0PAYPCT_CHA) features. You can
define these hierarchies manually yourself or by using a CSV file.
You can define your own hierarchies. This gives you flexibility when defining the ranges within the structure
e.g. in five year intervals (25 - 29 years, 30 - 34 years). Defining the age structure yourself has several advan-
tages over using the pre-defined age structure in the Age Range characteristic (0AGE_RANGE).
You can represent your enterprises age structure using hierarchies in the following manner:
< 20 [ ] x < 20
20 - 24 [ ] 20 x 24
Page 120
25 - 29 [ ] 25 x 29
30 - 34 [ ] 30 x 34
35 - 39 [ ] 35 x 39
On the other hand, you can upload the hierarchy from the CSV file delivered by SAP.
To do so, proceed as follows:
1. Select the tab page Source systems in the Administrator Workbench.
2. Position the cursor on the top node Source system and select Create source system using the right mouse
button.
3. Select the radio button File system, manual meta data, data using file interface on the Select source sys-
tem type dialog box.
4. Enter AGE_FiIe in the Source system field and Age in years in the Source system name field on the dia-
log box Create source system. Confirm your entries.
5. Select the InfoSources tab page.
6. Position the cursor on the superior node Master data Personnel Administration and select Create
InfoSource using the right mouse button.
7. Select the Master data / texts / hierarchies radio button on the Create InfoSource: Select type dialog box.
8. Enter 0AGE in the InfoObject field on the Create InfoSource (master data) dialog box. Confirm your entries.
9. Position the cursor on the subordinate node Age in years and select Assign source system using the right
mouse button.
10. Enter AGE_FiIe in the Source system field on the dialog box Master data InfoSource: Assign source sys-
tem. Confirm your entries.
11. Then select the Create hier. (create hierarchy) pushbutton on the Maintain meta data screen.
12. Enter AGE in the field Hierarchy name, Age in years (hierarchy) in the field Long description, and an X in
the Sorted hierarchy, and Interval fields on the Create hierarchy - Name dialog box.
13. Select the Save hier. pushbutton (save hierarchy) and then the Save and Close pushbuttons.
14. Position the cursor again on the subordinate node Age in years (hierarchy) and select Create InfoPack-
age using the right mouse button.
15. Enter a user-defined description in the Long description field on the Create InfoPackage dialog window.
Confirm your entries.
16. Select the ExternData tab page on the Scheduler (maintain InfoPackage) screen.
17. Select the Application server radio button in the Load external data from group box and the CSV file radio
button in the File type (if control switched off) group box.
18. Enter AGE_D.CSV for the German node text and AGE_E.CSV for the English node text in the field File
name. Save you entries.
Hierarchy for the Capacity utilization level feature.
Page 121
You can also define your own hierarchies.
You can also up load the hierarchy from the CSV file delivered by SAP.
Proceed in exactly the same way as described above for the Age in years feature. When doing so, use the fol-
lowing information:
Source system: PAYPCT_FiIe
Name of source system: Capacity utiIization IeveI in %
InfoObject: 0PAYPCT_CHA
Hierarchy name: CAPACITY UTILIZATION LEVEL
Long description (of the hierarchy name): Capacity utiIization IeveI in % (hierarchy)
File name: PAYPCT_D.CSV (for the German node text), PAYPCT_E.CSV (for English node text).
Restricted Key Figures
The restricted key figures are derived from an InfoCubes key figures and are reduced to one or more InfoCube
characteristics. For example, the restricted key figures Number of Entries (0R_PA_001) and Number of Leavers
(0R_PA_002) are derived in this way.
Update Rules
In** the update rules, numerous fields are read from the master data tables to the period end (usually the last day
of the month) and are written to the InfoCube as characteristics. For this reason, it is necessary that the master
data is loaded and activated before the InfoSources.
Structures
In templates/structures in which time periods are taken into account, the periods are represented by text variables
(&0T_CYEAR&, &0T_CQUAT&), and the relevant values (calendar years, calendar quarters) are automatically
generated when the queries are executed.
Example:
In the "Compare previous year with current year" structure, the text variable &0T_CYEAR& is used for "previous
year" and "current year". When the query is executed, the text variable is replaced by the relevant calendar year
i.e. "previous year" is replaced by "1998" and "current year" by "1999".
In the Compare Last Four Quarters (0QT_PA_009) and Average Last 4 Quarters (0QT_PA_010) structures, calcu-
lations begin with the last quarter for which you have complete figures. For example, if a query compares 4 quar-
ters and begins in the second quarter of 1999, the following 4 quarters are compared: 1/99, 4/98, 3/98 and 2/98.
Page 122
2.1.1.1 Headcount/PersonneI Structure
2.1.1.1.1 Query: 0PA_C01_Q001: Headcount/Change in Staffing LeveI
Purpose:
This query displays the headcount as well as changes to the staffing level as an annual comparison (compare cur-
rent year/previous year; with absolute and percentage differences). Personal as well as organizational data is used
for the evaluation.
TechnicaI name Description EIement FormuIa
Previous year
(&0T_CYEAR&)
year 1
(&0CYEAR&-1)
(&0T_CYEAR&)
current calendar year
(&0CYEAR&)
previous year
ous year with
current year
ous year * 100
Key Figures:
TechnicaI name Description Remark
0HDCNT_LAST Number of employees
0EMPLOYEE Employee
0EMPLSTATUS Employment status
0GENDER Gender
0NATION Nationality
0AGE Age in years
0PERS_AREA Personnel area
0PERS_SAREA Personnel subarea
0EMPLGROUP Employee group
0EMPLSGROUP Employee subgroup
0MAST_CCTR Master cost center
Line Characteristics:
0ORGUNIT Organizational unit
Page 123
2.1.1.1.2 Query: 0PA_C01_Q012: Average Headcount
Purpose:
This query displays the headcount for the four quarters of the previous year and calculates an average. Personal
as well as organizational data is used in the evaluation.
1
st
2
nd
3
rd
4
th
ters - previous
year
previous year
year) / 4
Key Figures:
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 124
2.1.1.1.3 Query: 0PA_C01_Q021: Average Headcount (12 Months)
Purpose:
This query displays the various headcounts for the 12 months of the previous year and calculates an average. Per-
sonal as well as organizational data is used in the evaluation.
to 1 and &0CYEAR&-1
to 2 and &0CYEAR&-1

0QT_PA_014 Average 12
months previous
year
Average 12 months
previous year
of the monthly values (previous
year) / 12
Key Figures:
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 125
2.1.1.1.4 Query: 0PA_C01_Q011: Percentage Breakdown of EmpIoyees
Purpose:
This query displays the percentage of total employees for the evaluation characteristic chosen for the current cal-
endar year. Personal as well as organizational data is used for the evaluation.
You can use this query to evaluate the percentage of employees according to gender as well as nationality.
Number of Employees 0QT_PA_005 Percentage
Breakdown of
Employees Ac-
cording to Char-
acteristics
of Employees Accord-
ing to Characteristics
Percentage breakdown of em-
ployees according to characteris-
tics = number of employees per
characteristic value / entire num-
ber of employees * 100
Key Figures:
Percentage Breakdown of Employees Key figure is calculated in
structure 0QT_PA_005.
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 126
CoIumn Characteristics:
&0CYEAR& Current calendar year
2.1.1.1.5 Query: 0PA_C01_Q006: EmpIoyees' Average Age
Purpose:
This query displays the employees average age for the current calendar year. Personal as well as organizational
data is used for the evaluation.
Number of Employees
Total age in years
0QT_PA_006 Employees Av-
erage Age
Employees Average
Age
Employees average age = total
age in years / number of employ-
ees
Key Figures:
0AGE_KYF Total age in years
Employees average age Key figure is calculated in
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 127
2.1.1.1.6 Query: 0PA_C01_Q020: Headcount: Part-Time/FuII-Time Workers
Purpose:
This query shows the number of part-time and full-time employees for the current calendar year. Personal as well
as organizational data is used for the evaluation.
Key Figures:
0R_PA_006 Number of Part-Time Workers
0R_PA_005 Number of Full-Time Workers
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 128
2.1.1.1.7 Query: 0PA_C01_Q019: Headcount According to Capacity UtiIization LeveI
Purpose:
This query shows the number of employees according to the capacity utilization level as an annual comparison
(compare current year/previous year; with absolute and percentage differences). Personal as well as organizational
data is used in the evaluation.
Previous year
(&0T_CYEAR&)
year - 1
(&0CYEAR&-1)
(&0T_CYEAR&)
calendar year
(&0CYEAR&)
- previous year
ous year and
current year
ous year * 100
Key Figures:
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
0PAYPCT_CHA Capacity utilization level
Page 129
2.1.1.2 Headcount/PersonneI Structure FTE
2.1.1.2.1 Query: 0PA_C01_Q013: Headcount FTE
Purpose:
This query shows the headcount as a full-time equivalent, as well as the changes to the headcount FTE as an an-
nual comparison (compare current year/previous year; with absolute and percentage differences). Personal as well
as organizational data is used for the evaluation.
For further information about headcount FTE (full-time equivalent), see the key figure documentation of the same
name.
Previous year
(&0T_CYEAR&)
year - 1
(&0CYEAR&-1)
(&0T_CYEAR&)
calendar year
(&0CYEAR&)
- previous year
ous year and
current year
ous year * 100
Key Figures:
0HDCNT_FTE Headcount FTE
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 130
2.1.1.2.2 Query: 0PA_C01_Q015: Percentage Breakdown of Headcount FTE
Purpose:
This query shows the percentage breakdown of the headcount FTE in relation to the total headcount FTE based on
the evaluation criteria used for the current calendar year. Personal as well as organizational data is used for the
evaluation.
Headcount FTE 0QT_PA_011 Percentage
Breakdown of
Headcount FTE
Percentage distribution
of headcount FTE
Percentage distribution of
headcount FTE = headcount FTE
per feature value / total headcount
FTE * 100
Key Figures:
Percentage Breakdown According to
Headcount FTE
Key figure is calculated in
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 131
2.1.1.2.3 Query: 0PA_C01_Q014: Average Headcount FTE
Purpose:
This query shows the headcount FTE for the previous years four quarters and calculates the average. Personal as
well as organizational data is used for the evaluation.
For further information about the headcount FTE, see the key figure documentation of the same name.
1
st
2
nd
3
rd
4
th
ters - previous
year
previous year
year) / 4
Key Figures:
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 132
2.1.1.2.4 Query: 0PA_C01_Q016: Headcount/Headcount FTE Current Year
Purpose:
This query shows the headcount as well as the headcount FTE for the current calendar year. Personal as well as
organizational data is used for the evaluation.
For further information about headcount FTE, see the key figure documentation of the same name.
Key Figures:
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 133
2.1.1.3 PersonneI FIow
2.1.1.3.1 Query: 0PA_C01_Q002: Number of PersonneI Actions
Purpose:
This query displays the number of personnel actions as an annual comparison (compare current year/previous
year; with absolute and percentage differences): this is restricted to the personnel action types Early Retire-
ment/Retirement, Leaving, Organizational Reassignment and Hiring. Personal as well as organizational data is
used for the evaluation.
Previous year
(&0T_CYEAR&)
year - 1
(&0CYEAR&-1)
(&0T_CYEAR&)
(&0CYEAR&)
Difference Difference = current calendar -
previous year
ous year/current
year
ous year * 100
Key Figures:
0ACTION_CNT Number of personnel actions
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 134
0ACTIONTYPE Personnel action type
2.1.1.4 Entries
2.1.1.4.1 Query: 0PA_C01_Q003: Number of Entries
Purpose:
This query displays the number of people who have entered the enterprise as an annual comparison (compare
current year/previous year; with absolute and percentage differences). Personal as well as organizational data is
Previous year
(&0T_CYEAR&)
year - 1
(&0CYEAR&-1)
(&0T_CYEAR&)
(&0CYEAR&)
- previous year
ous year/current
year
ous year * 100
Key Figures:
0R_PA_001 Number of entries
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 135
2.1.1.4.2 Query: 0PA_C01_Q010: Percentage Breakdown of Entries
Purpose:
This query displays a percentage of the total number of people who have entered enterprise according to the cho-
sen evaluation characteristic; this is valid for the current calendar year. Personal as well as organizational data is
Number of Entries 0QT_PA_008 Percentage
Breakdown of
Entries
of Entries
Percentage breakdown of entries
= number of entries per charac-
teristic / total number of entries *
100
Key Figures:
Percentage breakdown of entries Key figure is calculated in
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 136
2.1.1.4.3 Query: 0PA_C01_Q022: Entry Rate
Purpose:
This query shows the number of entries in relation to the average headcount for the previous year (i.e. last com-
plete year). Personal as well as organizational data is used for the evaluation.
st
quarter
previous year
and &0CYEAR&-1
nd
quarter
previous year
and &0CYEAR&-1
rd
quarter,
previous year
and &0CYEAR&-1
th
quarter
previous year
and &0CYEAR&-1
Average Headcount
(previous year)
year) / 4
0QT_PA_017 Entry Rate
Number of Entries
(previous year)
Number of entries (previous year)
(&0CYEAR&-1)
Page 137
Entry Rate Entry rate = number of entries
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
2.1.1.4.4 Query: 0PA_C01_Q005: Net Entry Rate
Purpose:
This query displays the number of people who have entered the enterprise in relation to the number people who
have left the enterprise for the current calendar year. Personal as well as organizational data is used for the
evaluation.
Number of Entries
Number of Leavers
0QT_PA_003 Net Entry Rate
Net Entry Rate Net entry rate = number of entries
/ number of leavers
Key Figures:
0R_PA_002 Number of leavers
Net entry rate Key figure is calculated in
Page 138
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
2.1.1.4.5 Query: 0PA_C01_Q017: Number of Entries FTE
Purpose:
This query shows the number of people who have entered the enterprise as a full-time equivalent for the current
calendar year. Personal as well as organizational data is used for the evaluation.
Key Figures:
0R_PA_001 Number of Entries
0R_PA_003 Entries FTE
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 139
2.1.1.5 Leavers
2.1.1.5.1 Query: 0PA_C01_Q007: Number of Leavers
Purpose:
This query displays the Number of people who have left enterprise as an annual comparison (compare current
year/previous year; with absolute and percentage differences). Personal as well as organizational data is used for
the evaluation.
Previous year
(&0T_CYEAR&)
year - 1
(&0CYEAR&-1)
(&0T_CYEAR&)
(&0CYEAR&)
- previous year
ous year/current
year
ous year * 100
Key Figures:
0EMPLOYEE Employee
Page 140
0GENDER Gender
0NATION Nationality
0AGE Age in years
2.1.1.5.2 Query: 0PA_C01_Q009: Percentage Breakdown of Leavers
Purpose:
This query displays the number of people who have left enterprise according to a chosen evaluation characteristic
as a percentage of the total number of people who have left enterprise for the current calendar year. Personal as
well as organizational data is used for the evaluation.
Number of Leavers 0QT_PA_007 Percentage
Breakdown of
Leavers
of Leavers
Percentage breakdown of leavers
= number of leavers per charac-
leavers * 100
Key Figures:
Percentage breakdown of leavers Key figure is calculated in
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 141
2.1.1.5.3 Query: 0PA_C01_Q023: Leaving Rate
Purpose:
This query shows the number of people who have left the enterprise in relation to the average headcount for the
previous year (the last complete year). Personal as well as organizational data is used for the evaluation.
st
quarter
previous year
and &0CYEAR&-1
nd
quarter
previous year
(0CALQUART1) restricted to2
and &0CYEAR&-1
rd
quarter
previous year
and &0CYEAR&-1
th
quarter
previous year
and &0CYEAR&-1
0QT_PA_016 Leaving Rate
Average Headcount
(previous year)
of the quarterly value (previous
year) / 4
Page 142
Number of Leavers
(previous year)
Number of leavers (previous year)
(&0CYEAR&-1)
Leaving Rate
Leaving rate = number of leavers
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
2.1.1.5.4 Query: 0PA_C01_Q018: Number of Leavers FTE
Purpose:
This query shows the numbers of leavers FTE (full-time equivalent) as an annual comparison for the current year.
Personal as well as organizational data is used for the evaluation.
Key Figures:
0R_PA_002 Number of Leavers
0R_PA_004 Leavers FTE
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0AGE Age in years
Page 143
Page 144
2.2 PA-RC Recruitment
2.2.1 InfoCube: 0PARC_C01 AppIications and AppIicant Actions
Content:
The Applications and Applicant Actions InfoCube (0PARC_C01) contains all transaction data on job applications
and applicant actions, uploaded from one or more source systems. The data in this InfoCube is extracted from the
InfoSources Applicants (0HR_PA_RC_0), Applications (0HR_PA_RC_1) and Applicant Actions (0HR_PA_RC_2).
This InfoCube contains the general key figures Number of applicants (0APPL_CNT), Number of applications
(0APPLC_NUM), Number of applicant actions (0ACTION_CNT) and Age in years (0AGE_KYF). Restricted key
figures are also contained in the standard R/3 System. This InfoCube also includes numerous characteristics that
can be used for recruitment evaluation purposes (e.g. applicant groups, applicant ranges, advertisements, recruit-
ment instruments).
The following time dimensions are included in the InfoCube to help you in your evaluations: calendar day, calendar
year/month, calendar year/quarter, and calendar year.
Several templates/structures containing key figures or calculation rules for the InfoCube are provided in the stan-
dard R/3 System. These templates enable you to quickly and easily carry out frequently-required evaluations (such
as comparing the number of applications in the current and previous years, with absolute as well as percentage
differences).
For more information on the technical elements (characteristics, time characteristics, etc.), see Remarks on the
InfoCube.
InfoSource:
0HR_PA_RC_0: Applicants
0HR_PA_RC_1: Applications
0HR_PA_RC_2: Applicant Actions
Characteristics:
ExternaI hierarchy
avaiIabIe?
0AGE_RANGE Age range No No
0ADVERT Advertisement Yes No
0APPLICANT Applicant Yes No
0APPLICATION Applicant action types No No
0APPLSTREA Applicant status reason No No
0APPLSTATUS Applicant status (overall) No No
0CNTCTEMPL Contact employee No No
0AGE Age in years No Yes
0MEDIUM Medium No No
0APPLREFID Applicant reference indicator No No
0REFEMPL Reference employee No No
Page 145
0UNSAPPGRP Unsolicited application group No No
0CALMONTH Calendar year /month
0CALQUARTER Calendar year /quarter
Key Figures:
InfoObject Description InfoObject units Aggregation be-
havior
0APPL_CNT Number of applicants Last
0APPLC_NUM Number of applications Additive
0ACTION_CNT Number of applicant actions Additive
0AGE_KYF Age in years Last
0R_PARC_001 Number of applicants with status
To be hired
Key figure Number of applicants restricted
to applicants with overall status To be
hired
Contract offered
to applicants with overall status Contract
offered
Offer rejected
to applicants with overall status Offer re-
jected
0R_PARC_004 Number of unsolicited applications Key figure Number of applications re-
stricted to unsolicited applications (unsolic-
ited application groups 1-999)
0R_PARC_005 Number of applications in re-
sponse to advertisements
Key figure Number of applications re-
stricted to applications in response to ad-
vertisements (advertisement numbers 1-
999)
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year 1
(&0CYEAR&-1)
0QT_PARC_001 Compare previous year/current
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
calendar year
(&0CYEAR&)
Page 146
Difference Difference = Current
calendar year
Previous year
Difference in % Difference in % =
[Current calendar
year - previous year
/ previous year] *100
Number of appli-
cants
Number of applica-
tions
0C_PARC_001 Ratio of applications to applicants
Ratio of applications
to applicants
to applicants =
Number of appli-
cants / Number of
applications
Number of applica-
tions
0QT_PARC_002 Percentage breakdown of appli-
cations
Percentage break-
down of applications
Percentage break-
down of applications
= [Number of appli-
cations per charac-
teristic value / Total
number of applica-
tions] *100
Number of appli-
cants
0QT_PARC_003 Percentage breakdown of appli-
cants
Percentage break-
down of applicants
Number of appli-
cants = [Number of
applicants per char-
acteristic value /
Total number of
applicants] *100
Number of appli-
cants
Number of appli-
cants with status 'To
be hired'
0QT_PARC_004 Applicant hiring rate
Applicant Hiring
Rate
Applicant Hiring
Rate = [Number of
applicants with
status 'To be hired' /
Number of appli-
cants] *100
Number of appli-
cants with status
'Offer rejected'
0QT_PARC_005 Take Up Rate for Job Offers
Number of appli-
cants with status
'Contract offered'
Page 147
Ratio of offered
contracts to rejected
contracts
Ratio of offered
contracts to rejected
contracts = [Number
of applicants with
status Offer re-
jected / Number of
applicants with
status Contract
offered] *100
Number of appli-
cants
Age in years
0QT_PARC_006 Applicants average age
Applicants average
age
Applicants average
age = Age in years /
Number of appli-
cants
Number of appli-
cants
Number of applica-
tions
0QT_PARC_007 Ratio of applications to applicants
to applicants
to applicants =
Number of applica-
tions / Number of
applicants
Current quarter-4
(&0T_CQUAT&-4)
Current quarter-4
(&0CQUART&-4)
Current quarter-3
(&0T_CQUAT&-3)
Current quarter-3
(&0CQUART&-3)
Current quarter-2
(&0T_CQUAT&-2)
Current quarter-2
(&0CQUART&-2)
0QT_PARC_008 4 quarter comparison
Current quarter-1
(&0T_CQUAT&-1)
Current quarter-1
(&0CQUART&-1)
Current quarter-4
(&0T_CQUAT&-4)
Current quarter-4
(&0CQUART&-4)
Current quarter-3
(&0T_CQUAT&-3)
Current quarter-3
(&0CQUART&-3)
Current quarter-2
(&0T_CQUAT&-2)
Current quarter-2
(&0CQUART&-2)
Current quarter-1
(&0T_CQUAT&-1)
Current quarter-1
(&0CQUART&-1)
0QT_PARC_009 Average 4 quarters
Average 4 quarters quarterly value/ 4
Number of appli-
cants
0QT_PARC_010 Unsolicited application rate
Number of appli-
cants in response to
advertisement
Page 148
Number of unsolic-
ited applications
Unsolicited applica-
tion rate
tion rate = [Number
of unsolicited appli-
cations / Number of
applications] *100
General Remarks
Because of the way in which the InfoSources are structured in the standard R/3 System, it is only useful to carry
out some evaluations for certain InfoSources e.g. it makes sense to carry out application-related rather than appli-
cant-action-related evaluations in the InfoSource Applications (0HR_PA_RC_1).
Characteristics
Age Range (0AGE_RANGE) and Age in Years (0AGE) are calculated characteristics.
The Age Range characteristic contains an employees age, which is calculated from the date of birth and the
period in the relevant InfoSource. The ranges are specified by the update rules.
Note that you must manually maintain the master data for this characteristic as follows:
0 not available
1 < 20
2 20 - 29
3 30 - 39
4 40 - 49
5 50 - 59
6 60 - 69
7 70
The Age in Years characteristic contains an employees age at the end of the period. You can (depending on
your individual enterprise requirements) define a hierarchy for age and thereby depict the age profile in your
enterprise. You can also use the key figure Age in years (0AGE_KYF) to make calculations based on employ-
ees age in years.
The age characteristics are calculated at the end of the period using the update rules. The period is dependent on
the InfoSource from which it is transported. For example, the period end can fall either at the end of a calendar day
or a calendar month.
In the Applications and Applicant Actions (0PARC_C01) InfoCube, the characteristic Employee (0EMPLOYEE)
refers to internal applicants.
The characteristic Contact employee (0CNTCTEMPL) refers to the employee that accepts or passes on a job ap-
plication to the company or to an employee who is referred to in an application.
The characteristic Reference employee (0REFEMPL) refers to the employee in the enterprise who evaluates an
applicants suitability and subsequently recommends accepting or rejecting the applicant.
Page 149
Key Figures
Both the key figures Number of applicants (0APPL_CNT) and Number of applications (0APPLC_NUM) are avail-
able because an applicant can have made several applications.
Hierarchies
No hierarchies exist for age in the standard R/3 System, but you can define them yourself for the characteristic Age
in years (0AGE). This gives you flexibility in defining the ranges within the structure e.g. in five-year-intervals (25-
29 years, 30-34 years). Defining the age structure yourself has several advantages over using the pre-defined age
structure in the Age range characteristic (0AGE_RANGE).
For example, you can define the age structure of your enterprise as follows:
< 20 [ ] x < 20
20 - 24 [ ] 20 x 24
25 - 29 [ ] 25 x 29
30 - 34 [ ] 30 x 34
35 - 39 [ ] 35 x 39

The restricted key figures are derived from the InfoCubes key figures by means of a filter. The following restricted
key figures are determined in this way:
Number of applicants with status 'To be hired' (0R_PARC_001)
Number of applicants with status 'Contract offered' (0R_PARC_002)
Number of applicants with status 'Offered rejected' (0R_PARC_003)
Number of unsolicited applications (0R_PARC_004)
Number of applications in response to an advertisement (0R_PARC_005)
Update Rules
In the update rules, numerous fields are read from the master data tables to the period end (usually the last day of
the month) and are written to the InfoCube as characteristics. For this reason, it is necessary that the master data
is loaded and activated before the InfoSources.
Structures
In templates/structures in which time periods are taken into account, the periods are represented by text variables
(&0T_CYEAR&, &0T_CQUAT&), and the relevant values (calendar years, calendar quarters) are automatically
generated when the queries are executed.
Example:
In the "Compare previous year with current year" structure (0QT_PARC_001), the text variable &0T_CYEAR& is
used for "previous year" and "current year". When the query is executed, the text variable is replaced by the rele-
vant calendar year i.e. "previous year" is replaced by "1998" and "current year" by "1999".
Page 150
In the 4 Quarter Comparison (0QT_PARC_008) and Average 4 Quarters (0QT_PARC_009) structures, calculations
begin with the last quarter for which you have complete figures. For example, if a query compares 4 quarters and
begins in the second quarter of 1999, the following 4 quarters are compared: 1/99, 4/98, 3/98 and 2/98.
2.2.1.1 AppIications
2.2.1.1.1 Query: 0PARC_C01_Q002: Number of AppIications with Master Data
Purpose:
This query displays the number of job applications as an annual comparison (current year/previous year; with ab-
solute and percentage differences). In addition, you can display different data about applications (e.g. applicant,
applicants overall status, applicant group).
Structure:
Structure Description EIement FormuIa
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year 1
(&0CYEAR&-1)
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
Difference Difference =
Current calendar
Previous year
0QT_PARC_001 Compare previous year/current year
[Current year
previous year /
previous year] *
100
Key Figures:
TechnicaI name Key figure Remark
0APPLC_NUM Number of applications
0APPLGROUP Applicant group
0APPLICANT Applicant
0APPLSTATUS Applicant status (overall)
0APPLSGROUP Applicant range
Page 151
0AGE_RANGE Age range
0GENDER Gender
0NATION Nationality
0COUNTRY Country
Line Characteristic:
2.2.1.1.2 Query: 0PARC_C01_Q008: Percentage Breakdown of AppIications with Mas-
ter Data
Purpose:
The query displays job applications as a percentage of the total number of applications according to the selected
evaluation characteristics; it evaluates data for the current calendar year.
Structure:
Number of ap-
plications
0QT_PARC_002 Percentage breakdown of applica-
tions
Percentage
breakdown of
applications
Percentage
breakdown of
applications =
Number of ap-
plications per
characteristic
value / Total
number of appli-
cations * 100
Key Figures:
TechnicaI name Key Figure Remark
Percentage breakdown of applica-
tions
Key figure is calculated in structure
0QT_PARC_002
0APPLC_NUM Number of applications Key figure is calculated in structure
0QT_PARC_002
Page 152
0GENDER Gender
0NATION Nationality
0COUNTRY Country
CoIumn Characteristic:
0CYEAR Current calendar year
2.2.1.1.3 Query: 0PARC_C01_Q016: Average Number of AppIications
Purpose:
The query displays the average number of applications in relation to the last four quarters.
Structure:
Current quarter 4
(&0T_CQUAT&-4)
Current quarter 4
(&0CQUART&-4)
Current quarter 3
(&0T_CQUAT&-3)
Current quarter 3
(&0CQUART&-3)
Current quarter 2
(&0T_CQUAT&-2)
Current quarter 2
(&0CQUART&-2)
Current quarter 1
(&0T_CQUAT&-1)
Current quarter 1
(&0CQUART&-1)
Average 4 quarters of the quarterly
value / 4
Key Figures:
Page 153
0GENDER Gender
0NATION Nationality
0COUNTRY Country
2.2.1.1.4 Query: 0PARC_C01_Q006 Ratio AppIications to AppIicants
Purpose:
The query displays the number of applicants, applications and the ratio of job applications to applicants for the cur-
rent calendar year.
Structure:
Number of appli-
cants
Number of appli-
cations
0C_PARC_001 Ratio of applications to applicants
Ratio of applica-
tions to appli-
cants
Ratio of applica-
tions to appli-
cants = Number
of applications /
Number of appli-
cants
Key Figures:
TechnicaI name Key figures Remark
0APPL_CNT Number of applicants Key figure is calculated in structure
0C_PARC_001
0C_PARC_001
Ratio of applications to applicants Key figure is calculated in structure
0C_PARC_001
Page 154
0GENDER Gender
0NATION Nationality
0COUNTRY Country
2.2.1.2 AppIicants
2.2.1.2.1 Query: 0PARC_C01_Q003 Number of AppIicants with Master Data
Purpose:
The query displays the number of applicants with master data as an annual comparison (current year/previous
year; with absolute and percentage differences).
Structure:
Previous year
(&0T_CYEAR&)
Previous year =
Current calendar
year - 1
(&0CYEAR&-1)
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
Current calendar
year previous
year
0QT_PARC_001 Compare previous year/current year
[(Current year
previous year) /
previous year] *
100
Page 155
Key Figures:
0APPL_CNT Number of applicants
0GENDER Gender
0NATION Nationality
0COUNTRY Country
2.2.1.2.2 Query: 0PARC_C01_Q015: AppIicants' Average Age
Purpose:
The query displays the applicants average age. In addition you can display other data about the applicant (e.g.
applicants overall status, gender, nationality).
Structure:
Number of appli-
cants
Age in years
0QT_PARC_006 Applicants average age
Applicants aver-
age age
Applicants aver-
age age = Age in
years/Number of
applicants
Key Figures:
0QT_PARC_006
0AGE_KYF Age in years Key figure is calculated in structure
0QT_PARC_006
Page 156
Applicants average age Key figure is calculated in structure
0QT_PARC_006
0GENDER Gender
0NATION Nationality
0COUNTRY Country
2.2.1.2.3 Query: 0PARC_C01_Q007: Percentage Breakdown of AppIicants with Master
Data
Purpose:
The query displays the percentage breakdown of applicants with master data according to the selected evaluation
characteristics for the current calendar year.
Structure:
Number of appli-
cants
0QT_PARC_003 Percentage breakdown of applicants
Percentage
breakdown of
applicants
Percentage
breakdown of
applicants =
Number of appli-
cants per char-
acteristic
value/total num-
ber of applicants
* 100
Page 157
Key Figures
Percentage breakdown of applicants Key figure is calculated in structure
0QT_PARC_003
0QT_PARC_003
0GENDER Gender
0NATION Nationality
0COUNTRY Country
2.2.1.2.4 Query: 0PARC_C01_Q017: Average Number of AppIicants
Purpose:
The query displays the average number of applicants in relation to the last four quarters.
Structure:
Current quarter-4
(&0T_CQUAT&-4)
Current quarter-4
(&0CQUART&-4)
Current quarter-3
(&0T_CQUAT&-3)
Current quarter -3
(&0CQUART&-3)
Current quarter -2
(&0T_CQUAT&-2)
Current quarter -2
(&0CQUART&-2)
Page 158
Current quarter -1
(&0T_CQUAT&-1)
Current quarter -1
(&0CQUART&-1)
Average 4 quarters of quarterly value / 4
Key Figure:
0GENDER Gender
0NATION Nationality
0COUNTRY Country
2.2.1.3 Advertising
2.2.1.3.1 Query: 0PARC_C01_Q004: Number of AppIications in Response to Adver-
tising
Purpose:
The query displays the number of applications in response to advertising as an annual comparison (current
year/previous year; with absolute and percentage differences). The InfoObjects Advertising (0ADVERT), Medium
(0MEDIUM), and Recruitment Instrument (0RC_INSTR) are available for your evaluation.
Structure:
0QT_PARC_001 Compare previous year/current
year
Previous year
(&0T_CYEAR&)
Previous year =
Current calendar
year 1
(&0CYEAR&-1)
Page 159
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
Difference Difference = Cur-
rent calendar year
Previous year
[(Current year
Previous year) /
Previous year] *
100
Key Figure:
Free Characteristic:
0ADVERT Advertisement
0MEDIUM Medium
0RC_INSTR Recruitment instrument
0UNSAPPGRP Unsolicited application group
2.2.1.3.2 Query: 0PARC_C01_Q005: AppIications per Advertisement Showing Costs
Purpose:
The query displays the number of applications per advertisement along with the costs per advertisement.
Key Figure:
Page 160
2.2.1.3.3 Query: 0PARC_C01_Q009: Percentage Breakdown of AppIications
Purpose:
The query displays the percentage breakdown of applications in relation to the type of advertisement; in addition
this query includes the option of an evaluation by selecting unsolicited applications. There are additional evaluation
characteristics available for this query too (e.g. recruitment instrument, medium, unsolicited applications).
Structure:
Number of appli-
cations
0QT_PARC_002 Percentage breakdown of applica-
tions
Percentage
breakdown of
applications
Percentage
breakdown of
applications =
[Number of ap-
plications per
characteristic
value / Total
number of appli-
cations] * 100
Key Figures:
Percentage breakdown of applica-
tions
0QT_PARC_002
0QT_PARC_002
0MEDIUM Medium
0UNSAPPGRP Unsolicited applications group
Page 161
2.2.1.3.4 Query: 0PARC_C01_Q001: UnsoIicited AppIications and AppIications in Re-
sponse to Advertisements
Purpose:
The query displays the number of unsolicited applications and the number of applications in response to adver-
tisements for the current calendar year.
Key Figures:
0QT_PARC_002
TechnicaI name Key figures Condition
0R_PARC_004 Number of unsolicited applications Key figure Number of applications,
limited to unsolicited applications
(unsolicited application group 1 -
999)
0R_PARC_005 Number of applications in response
to advertisement
Key figure Number of applications,
limited to applications in response to
advertisement (advertisement num-
ber 1-99 999 999)
0GENDER Gender
0NATION Nationality
0COUNTRY Country
0RC_APPLGROUP Applicant group
CoIumn characteristic:
Page 162
2.2.1.3.5 Query: 0PARC_C01_Q010: UnsoIicited AppIications Rate
Purpose:
The query displays the number of applicants, the number of unsolicited applications, the number of applications in
response to an advertisement, and the unsolicited applications rate.
Structure:
Number of applicants
Number of applicants
responding to an ad-
vertisement
Number of unsolicited
applications
0QT_PARC_010 Unsolicited application rate
Unsolicited application
rate
tion rate = [Number
of unsolicited appli-
cations / Number of
applications] * 100
Key Figures:
Unsolicited applications rate Key figure is calculated in structure
0QT_PARC_010
0QT_PARC_002
0R_PARC_004 Number of unsolicited applications Key figure is calculated in structure
0QT_PARC_010
0R_PARC_005 Number of applications in response
to advertisement
0QT_PARC_010
Free Characteristic:
0GENDER Gender
0NATION Nationality
Page 163
0COUNTRY Country
0RC_APPLGROUP Applicant group
2.2.1.4 Hires/Contracts Offered
2.2.1.4.1 Query: 0PARC_C01_Q011: Hires/Offers/Rejected Contracts
Purpose:
The query displays the total number of all applicants, the number of applicants with the status To hire, the number
of applicants with the status Contract offered and the number of applicants with the status Offer rejected.
Key Figure:
TechnicaI name Key figures Condition
0R_PARC_001 Number of applicants with the status
To hire
Key figure Number of applicants,
limited by overall applicant status To
hire
0R_PARC_002 Number applicants with the status
Contract offered
limited by overall applicant status
Contract offered
Offer rejected
limited by applicants overall status
'Offered Rejected'
Page 164
0GENDER Gender
0NATION Nationality
0COUNTRY Country
2.2.1.4.2 Query: 0PARC_C01_Q012: AnnuaI Comparison of Hires/Offers/Rejected
Contracts
Purpose:
The query displays the total number of applicants, the number of applicants with the status To hire, the number of
applicants with the status Contract offered and the number of applicants with the status Offer rejected as an annual
comparison (current year/previous year; with absolute and percentage deviation).
Structure:
Previous year
(&T_CALYEA&)
Previous year = Cur-
rent calendar year
1
(&0CYEAR&-1)
Current calendar
year
(&T_CALYEA&)
Current calendar
year = variable cur-
rent calendar year
(&0CYEAR&)
Difference Difference = Current
calendar year Pre-
vious year
0QT_PARC_001 Compare previous/current year
[(Current year Pre-
vious year) / Previ-
ous year] * 100
Key Figure:
Page 165
To hire
'To hire'
'Contract offered'
Key figure 'Number of applicants',
'Contract offered'
'Offer rejected'
Key figure 'Number of applicants',
'Offer rejected'
0GENDER Gender
0NATION Nationality
0COUNTRY Country
2.2.1.4.3 Query: 0PARC_C01_Q013: AppIicant Hiring Rate
Purpose:
The query displays the number of applicants, the number of applicants with the status To hire as well as the appli-
cant hiring rate.
Structure:
Number of appli-
cants
Number of appli-
cants with the
status 'To hire'
0QT_PARC_004 Applicant hiring rate
Applicant hiring
rate
Applicant hiring
rate = [Number
of applicants with
the status 'To
hire' / Number of
applicants] * 100
Page 166
Key Figures:
TechnicaI name Key Figures Remark
Applicant hiring rate Key figure is calculated in structure
0QT_PARC_004
0QT_PARC_004
To hire
0QT_PARC_004
0GENDER Gender
0NATION Nationality
0COUNTRY Country
2.2.1.4.4 Query: 0PARC_C01_Q014: Take Up Rate for Job Offers
Purpose:
The query displays the number of applicants with the status Offer rejected, the number of applicants with the status
Contract offered and the take up rate for job offers.
Page 167
Structure:
Number of appli-
cants with the status
Offer rejected
Number of appli-
cants with the status
Contract offered
0QT_PARC_005 Take up rate for job
offers
Take up rate for job
offers
Take up rate for job offers =
[Number of applicants with
the status Offer rejected /
Number of applicants with
the status Contract offered]
* 100
Key Figure:
Take up rate for job offers Key figure is calculated in structure
0QT_PARC_005
Contract offered
0QT_PARC_005
Offer rejected
0QT_PARC_005
0GENDER Gender
0NATION Nationality
0COUNTRY Country
Page 168
Page 169
2.3 PT Time Management
2.3.1 InfoCube: 0PT_C01: EmpIoyee Times
Content:
This InfoCube represents the consolidated data basis used for reporting time data in the BUSINESS
INFORMATION WAREHOUSE that reflects non-cumulative values and not cumulative values such as time bal-
ances. In this way, a distinction is made in the time data of the OLTP according to the time types for reporting, re-
gardless of the source (database table, function module) from which the data is derived. Definitions for these time
types must be stored in OLTP Customizing. To provide queries and key figures in a business-related context, the
following time types have been predefined as follows in the standard SAP R/3 System:
Time Type Description
00000001 Leave
00000002 Illness
00000003 Planned time (work
schedule used for
time evaluation)
00000004 Overtime
00000005 Productive time
00000009 Planned time accord-
ing to personal work
schedule
Note:
For more information on the technical elements (characteristics, time characteristics, and so on) of the InfoCube,
see Remarks on the InfoCube.
InfoSources:
0HR_PT_1 Employee Planned Times
0HR_PT_2 Employee Actual Times
Characteristics:
Hierarchy avaiI-
abIe?
0CO_MST_AR Master controlling area No No
0HRPOSITION Position No No
0JOB Job No No
Page 170
0REPTT Time type for reporting No No
0TIME_STAT Time Management status No No
0ALP_POSTN Different position No No
0DEBT_ACTT Debited activity type No No
0DEBT_ACTVY Debited activity No No
0DEBT_BUSA Debited business area No No
0DEBT_CCTR Debited cost center No Yes
0DEBT_CMPC Debited company code No No
0DEBT_NETW Debited network No No
0DEBT_ORDER Debited order No No
0DEBT_WBS_E Debited work breakdown sched-
ule (WBS) element
No No
0RECV_ACTVY Receiver activity No No
0RECV_BUSA Receiver business area No No
0RECV_CCTR Receiver cost center No Yes
0RECV_CMPC Receiver company code No No
0RECV_NETW Receiver network No No
0RECV_ORDER Receiver order No No
0RECV_PROCS Receiver process No No
0RECV_WBS_E Receiver work breakdown sched-
ule (WBS) element
No No
0SEND_ACTT Sender activity type No No
0SEND_BUSA Sender business area No No
0SEND_CCTR Sender cost center No Yes
0SEND_CMPC Sender company code No No
0PERSON Person Yes No
0CALQUARTER Calendar year/quarter
Key Figures:
0ALP_AMOUNT Amount 0CURRENCY Additive
0DUR_ACTUAL Actual time 0UNIT Additive
Page 171
0DUR_VALUE Account-relevant time 0UNIT Additive
0PLHRS Planned time according to personal
work schedule
0UNIT Additive
0WRHRS Planned time excluding public holi-
days
0UNIT Additive
Key Figure Description Condition
0R_PLAN_HRS Planned hours 0PLHRS
0UNIT = STD
0R_PLAN_DAY Planned days 0PLHRS
0INIT = T
0R_PROD_HRS Productive hours 0DUR_ACTUAL
0UNIT = STD
0REPTT = 00000005
0R_OVER_HRS Overtime hours 0DUR_ACTUAL
0UNIT = STD
0REPTT = 00000005
0R_SICK_HRS Illness hours 0DUR_ACTUAL
0UNIT = STD
0REPTT = 00000005
0R_LEAV_HRS Leave hours 0DUR_ACTUAL
0UNIT = STD
0REPTT = 00000005
0R_LEAVE_DAY Leave days 0DUR_ACTUAL
0UNIT = STD
0REPTT = 00000005
0R_ACT_HRS Actual hours 0DUR_ACTUAL
0UNIT = STD
Units:
0CURRENCY Currency key
0UNIT Unit of measurement
0QT_PROD Productivity rate Productivity rate
Productive hours
Planned hours
Productivity rate =
Productive hours/
planned hours in %
Page 172
0QT_OVER Overtime rate Overtime rate
Overtime hours
Planned hours
Overtime rate =
Overtime hours/
planned hours in %
0QT_SICK Illness rate Illness rates
Illness hours
Planned hours
Illness rate =
Illness hours/
planned hours in %
0QT_LEAV Leave days per planned
days
Leave days per
planned days
Leave days
Planned days
Leave days per
planned days =
Leave days/
planned hours in %
0QT_ACTPL Compare actual with
planned
Actual/planned
Actual hours
Planned hours
Planned hours (dis-
play hidden)
Actual hours/
planned hours in %
0QT_TIMES Employee times Illness hours
Productive hours
Overtime hours
Planned hours
0QT_FTE Employee times in units for
effective full-time employee
(FTE)
Planned working time
for full-time worker
(FTE)
Productive time for
FTE
Overtime for FTE
Planned hours
Productive hours
Overtime hours
Planned
hours/Annual hours
for FTE
Productive
hours/Annual hours
for FTE
Overtime
hours/Annual hours
for FTE
0QT_LEAVE_DAYS Leave days per FTE Leave per effective
FTE
Leave hours
Planned hours
Effective FTE =
Leave days/Planned
days x Annual
working hours for
FTE
0QT_YEAR A_F Compare year with previ-
ous year
Current year
Previous year
Difference in %
(Current year - previ-
ous year)/previous
year in %
0QT_QUARTERLY Quarterly view Current, quarterly,
and 4 preceding
quarters
Time Types for Reporting
Page 173
Time type assignments for SAP Human Resources and SAP Time Management data, as well as additional cus-
tomer-specific time data, can be defined without restriction in the SAP HR System. Possible sources include time
management infotypes Absences (2001), Attendances (2002), and Employee Remuneration Info (2010), as well as
time evaluation results (DB PCL2 Cluster B2). These times are transferred to the BUSINESS INFORMATION
WAREHOUSE using the InfoSource 0HR_PT_2 Employee Actual Times.
On the one hand, assigning the OLTP subtypes to fewer time types in the BUSINESS INFORMATION
WAREHOUSE achieves a summarization of the OLTP, and thus, a reduction in the amount of data to be trans-
ferred. However, if the transferred time data is broken down into its most detailed level (subtype level), then multi-
level summarization rules with corresponding drilldown results appear in hierarchies reports in the BUSINESS
INFORMATION WAREHOUSE. These hierarchies must be created for time types in the BUSINESS
INFORMATION WAREHOUSE.
One exception is the time type 00000009 Planned time according to personal work schedule. The origin of the data
records with the time type value 00000009 Planned time according to personal work schedule is always the per-
sonal work schedule. This time type value does not have a corresponding database object in the SAP R/3 System,
however, the personal work schedule is always created dynamically at runtime. This also occurs during the extrac-
tion process during which the InfoSource 0HR_PT_1 Employee Planned Times is supplied with data. Thus, the
times in the personal work schedule are usually transferred to the InfoCube 0PT_C01 by the InfoSource
0HR_PT_1 under the time type 00000009 Planned time according to personal work schedule. The Employee
Planned Times and those Employee Actual Times listed above are represented separately by the various key fig-
ures in the InfoCube (see 0PLHRS, 0WRHRS, 0DUR_VALUE and 0DUR_ACTUAL above).
Time and Unit Breakdown
The InfoCube stores cumulated time data monthly in units of days and hours. Both hourly values (overtime) and
daily values (leave) are required for reporting. Required key figures are derived from the raw data stored in the
InfoCube. Standard derivations are available as restricted key figures (for example, Unit = Hour) and as templates
along with the InfoCube (see Restricted Key Figures).
Essentially, the extractor also permits daily totals to be transferred. This InfoCube is designed for key figure reports
where monthly totals are sufficient. An additional summarization based on quarterly and annual key figures occurs
automatically in the InfoCube.
If, within a particular month, an employees assignment changes in the SAP HR System (a change in master cost
center, for example), and the InfoCube contains the corresponding InfoObject as a characteristic, then the times
are distributed to the individual areas as of the key date and then presented separately in the report in the charac-
teristics section.
Account Assignment Objects
Based on the time data entered in the SAP HR System, cost assignment of related personnel costs takes place in
the payroll accounting process. If there is no explicit account assignment information accompanying the time data,
then the costs are distributed according to the employees master data in the Organizational Assignment (0001)
and Cost Distribution (0027) infotypes. Similarly, the account assignment object 0DEBT_xxxx to be posted is also
indicated as debited in the InfoCube.
If an activity assignment takes place in the SAP HR System, then the sender 0SEND_xxxx and receiver object
0RECV_xxxx are indicated accordingly. If not, then the corresponding fields are left blank.
"EmpIoyee" vs. "Person"
In the BUSINESS INFORMATION WAREHOUSE, the InfoObjects Employees 0EMPLOYEE and Persons
0PERSON differ in their attributes. The personal attributes of Gender 0GENDER, Nationality 0NATION, and Lan-
guage 0PERSLANGU are included in the InfoCube 0PT_C01 as navigation attributes. The most important attrib-
utes assigned to the employee as contract partner of the employer (these are the first twelve entries in the above
characteristics table) must be provided by the InfoSource, so that working times are distributed proportionally (pro-
rated) to the corresponding master data if the employees master data changes within the same month (a change
in cost center, for example).
Page 174
Key Figures
The amount 0ALP_AMOUNT is calculated from one of the valuation bases entered explicitly in the OLTP during
time data recording, which is then multiplied by the actual hours (0DUR_ACTUAL with 0UNIT = Hours). If an entry
in the valuation basis is missing, then this field is usually left blank in the OLTP. In addition, data in this field can be
entered or changed in the customer enhancement of the extractor in the InfoSource 0HR_PT_2.
The actual time 0DUR_ACTUAL represents a container for the attendance/absence hours or days in the Ab-
sences (2001) and Attendances (2002) infotypes. The extent to which hours from time wage types or time accounts
are subtotaled is specified in OLTP Customizing.
In actuality, an absence of two hours causes a time credit to be debited by a half day. As a result, a working day of
eight planned hours results in an account-relevant time of 4 hours. This derived key figure is available in reporting
by the InfoObject Account-relevant time 0DUR_VALUE. The extent to which hours from time wage types or time
accounts are subtotaled is specified in OLTP Customizing.
Restricted key figures are derived from the key figures of the InfoCube using a filter for one or several characteris-
tics of the InfoCube. Thus, the illness hours 0R_SICK_HRS result from the value of the key figure 0DUR_ACTUAL
in which the conditions Unit of measurement = Hours and the Time type = Illness are met. Otherwise, the result is
zero (0) illness hours. The formulation of the condition must be modified as necessary to match the InfoObject
characteristics and their definitions in the customer system. This is especially true if the filter values for the units
Hours and Days deviate from the standard filter values (where STD = Hours and T = Days). The queries can only
provide correct key figures when consistent conditions are formulated that conform to the InfoCube data provided.
Hierarchy:
If hierarchies exist for the Organizational unit 0ORGUNIT and Master cost center 0MAST_CCTR, then you can
activate one hierarchy for each column of the report by choosing the Properties option in the menu bar. In this way,
multi-level aggregation hierarchies can be represented. A hierarchy can also be activated for the InfoObject Time
type for reporting 0REPTT. However, the hierarchy cannot be supplied by the OLTP, but must be created manually
in the BUSINESS INFORMATION WAREHOUSE.
Remarks on TempIates/Structures:
Using Text VariabIes in Structures
Time periods in templates/structures that reference specific periods of time are displayed as text variables
(&0T_CYEAR& &0T_CQUAT&) in the structure and preview. The applicable values are automatically generated
when the queries (calendar year, calendar quarters) are performed.
ExampIe:
In the structure Compare previous year with actual year, the text variable &0T_CYEAR& is used for Previous
year and Current year. When the query is executed, the text variable is replaced by the applicable calendar year,
that is previous year is replaced with 1998, for example, and Current year with 1999.
2.3.1.1 EmpIoyee Times
2.3.1.1.1 Query: 0PT_C01_Q001: Productivity Rate
Purpose:
This query is used to compare the actual (productive) working times of employees with the planned working times
of a quarter.
Page 175
0QT_QUARTERLY Quarterly view Current, last, and 3
quarters preceding
the last quarter
0QT_PROD Productivity rate Productivity rate
Productive hours
Planned hours
Productivity rate =
Productive hours/
planned hours in %
Key Figures:
TechnicaI name Description Comments
Productivity rate Calculated in structure 0QT_PROD
0R_PROD_HRS Productive hours Display hidden
0R_PLAN_HRS Planned hours Display hidden
InfoObject Description Comments
0EMPLOYEE Employee None
0EMPLGROUP Employee group None
0EMPLSGROUP Employee subgroup None
0PERS_AREA Personnel area None
0PERS_SAREA Personnel subarea None
0MAST_CCTR Master cost center Hierarchy activated
0ORGUNIT Organizational unit Hierarchy activated
2.3.1.1.2 Query: 0PT_C01_Q002: IIIness Rate
Purpose:
This query is used to compare illness-related absence times of employees with the planned working times of a
quarter.
0QT_QUARTERLY Quarterly view Current, last, and
the 3 quarters pre-
ceding the last
quarter
Page 176
0QT_SICK Illness rate Illness rate
Illness hours
Planned hours
Illness rate =
Illness hours/
planned hours in %
Key Figures:
TechnicaI Name Description Comments
Illness rate Calculated in structure 0QT_SICK
0R_SICK_HRS Illness hours Display hidden
Line Characteristics: (see Query 0PT_C01_Q001)
2.3.1.1.3 Query: 0PT_C01_Q003: Leave Per PIanned
Purpose:
This query is used to compare absence times that result from leave taken by employees with the planned working
times of a quarter. The actual time is calculated from this basis, and not from the time that debits the leave account,
as it can deviate from actual time.
quarters preceding
the last quarter
0QT_LEAVE Leave per planned Leave per planned
Planned leave hours
Planned hours
Leave per planned =
Leave hours/
planned hours in %
Page 177
Key Figures:
Leave per planned Calculated in structure 0QT_OVER
0R_OVER_HRS Leave hours Display hidden
2.3.1.1.4 Query: 0PT_C01_Q004: Overtime Rate
Purpose:
This query is used to compare employees overtime with the planned working time of a quarter.
quarters preceding
the last quarter
0QT_OVER Overtime rate Overtime rate Over-
time hours Planned
hours
Overtime rate = Over-
time hours/ planned
hours in %
Key Figures:
Overtime rate Calculated in structure 0QT_OVER
0R_OVER_HRS Overtime hours Display hidden
Page 178
2.3.1.1.5 Query: 0PT_C01_Q005 Leave Taken for Effective FuII-Time EmpIoyees
Purpose:
This query is used to compare an employee leave days taken with planned working time in a quarter. The leave
days are based on planned time in full-time employee units (see formula), so that the leave taken result as a key
figure in the quarter for each organizational unit of an effective full-time employee (FTE). Actual time is not used to
calculate leave days, as is the case in Query 0PT_C01_Q003 (Leave per Planned), but based on account-relevant
time. This results in the efficiency of a full-time employee based on the relationship of planned hours in the quarter
to a quarter of the annual working time of a full-time employee. The annual working time of a full-time employee is
stored in the Business Information Warehouse as the formula variable 0P_HRYFT with a default value of 2000
hours.
0QT_QUARTERLY Quarterly view Current, last, and
three quarters pre-
ceding the last
quarter
0QT_LEAVE_DAYS Leave days per full-time em-
ployee (FTE)
Leave per effective
full-time employee
Leave hours
Planned hours
Effective FTE = Leave
days/Planned hours x
annual working
hours of a FTE
Key Figures:
Leave per effective FTE Calculated in structure
0R_LEAV_DAY Leave days Display hidden
Page 179
2.3.1.2 EmpIoyee Times Overview
2.3.1.2.1 Query: 0PT_C01_Q011: Comparing Overview of EmpIoyee Times to Previous
Year
Purpose:
This query is used to assign employee times from one year according to time types, and then based on a ratio of
planned working time, to compare times from the previous year.
0QT_YEAR A_F Compare current year with
previous year
Current year
Previous year
Difference in %
(Current year -
previous year)/
previous year in %
0QT_ACTPL Compare actual with planned Actual/planned
Actual hours
Planned hours
Planned hours (dis-
play hidden)
Actual hours/
planned hours in %
Page 180
Key Figures:
0R_ACT_HRS Actual hours
0R_PLAN_HRS Planned hours
2.3.1.2.2 Query: 0PT_C01_Q012: Comparing SeIected EmpIoyee Times and Debited
Cost Centers to Previous Year (AnnuaI Comparison)
Purpose:
This query is used to compare selected employee times from one year with times from the previous year. A hierar-
chy can be assigned as the only line characteristic to the cost center debited with the corresponding personnel
costs.
previous year
Current year
Previous year
Difference in %
(Current year -
previous year)/
previous year in
%
Key Figures:
0R_ACT_HRS Actual hours Used as filter value
Page 181
0REPTT Time type for reporting Only selected values
0DEBT_CCTR Debited cost center Hierarchy activated
additional display of attribute
0RESP_PERS, person responsible for
process
2.3.1.2.3 Query: 0PT_C01_Q013: MonthIy View of SeIected EmpIoyee Times
Purpose:
This query is used to present selected employee times of one year broken down into months. Quarterly and annual
summarizations can also be calculated by choosing the appropriate line characteristics. Personnel area and calen-
dar year/month are the selection variables available.
0QT_TIMES Employee times Illness hours
Productive hours
Overtime hours
Planned hours
Key Figures:
0R_SICK_HRS Illness hours Contained in structure 0QT_TIMES
0R_PROD_HRS Productive hours Contained in structure 0QT_TIMES
0R_OVER_HRS Overtime hours Contained in structure 0QT_TIMES
0R_PLAN_HRS Planned hours Contained in structure 0QT_TIMES
Page 182
0PERS_AREA Personnel area Selection variable
0T_CYEAR Calendar year
0CALMONTH Calendar year/month Selection variable
2.3.1.2.4 Query: 0PT_C01_Q021 EmpIoyee Times Represented in FuII-Time EmpIoyee
Units
Purpose:
This query is used to compare planned time, productive time, and overtime of a year with the values of the previous
year. The times are represented in full-time employee (FTE) units, in which the number of hours is based on the
annual working time of a full-time employee. The annual working time of an FTE is stored in the Business Informa-
tion Warehouse as the formula variable 0P_HRYFT with a default value of 2000 hours. For example, if an em-
ployees planned time is 1000 hours annually, then the value would be 0.5 FTE.
previous year
Current year
Previous year
Difference in %
(Current year - previ-
ous year)/
previous year in %
0QT_FTE Employee times in units for
effective full-time employee
(FTE)
Planned working time
for full-time worker
(FTE)
Productive time for
FTE
Overtime for FTE
Planned hours
Productive hours
Overtime hours
Planned hours/Annual
hours for FTE
Productive
hours/Annual hours for
FTE
Overtime hours/Annual
hours for FTE
Page 183
Key Figures:
0R_ACT_HRS Actual hours
0R_PLAN_HRS Planned hours
0PERS_AREA Personnel area Keine
0PERS_SAREA Personnel subarea Keine
Page 184
2.4 PY PayroII Accounting
2.4.1 InfoCube: 0PY_C02 PayroII Data
Contents:
This InfoCube summarizes data from the SAP HR systems payroll results. It mainly deals with all wage type
amounts from the results table RT. The data is made available in the InfoCube for each wage type on an employee
basis. The source of data is the OHR_PY_1 extractor. The time basis is monthly. Using its end date, each payroll
period is assigned exactly one month, whereby the payroll period used is the period for which the results were cal-
culated. For more information, see the remarks on the InfoCube.
The InfoCube contains additional organizational assignment information for the employee grouping. It does not,
however, use all the information provided by the extractor. The InfoCube can, if necessary, be used as a template
for cubes with different organizational assignment criteria.
For more information on the technical elements (characteristics, time characteristics and so on), refer to the Re-
marks on the InfoCube listed below.
InfoSource(s):
0HR_PY_1
Characteristics:
characteristics
avaiIabIe?
Hierarchy
avaiIabIe?
0CO_MST_AR Controlling area of master cost center No No
0PERSON Person Yes No
Key Figures:
InfoObject Description InfoObject unit Aggregation
behaviour
Page 185
Unit:
0CURRENCY Currency key
In templates/structures, where reference is made to periods, the periods are displayed in the structure and the pe-
riod preview using text variables (&0T_CYEAR&), &0T_CQUAT&). The corresponding values (calendar year, cal-
endar quarter) are automatically generated when executing the queries.
Example:
In the compare previous year with current year structure, the text variable &T_CALYEA& is used for previous
year and current year. On executing the query, the text variable is replaced with the corresponding calendar
year, for example, previous year is replaced with 1998 and current year with 1999.
Previous year
(&0T_CYEAR&)
year 1 (&0CYEAR&-1)
(&0T_CYEAR&)
(&0CYEAR&)
Difference Difference = current calendar
year-previous year
0QT_2YEARS_DIFF Compare previ-
ous year/ current
year
Difference in % Difference in % = (current year -
previous year)/previous year in %
Current quarter
(&0T_CQUAT&)
Current quarter
(&0CQUART&)
Current quarter-3
(&0T_CQUAT&-3)
Current quarter-3
(&0CQUART&-3)
Current quarter-2
(&0T_CQUAT&-2)
Current quarter-2
(&0CQUART&-2)
0QT_4QUARTER Compare current
quarter and the
last three quar-
ters
Current quarter-1
(&0T_CQUAT&-1)
Current quarter-1
(&0CQUART&-1)
Current quarter
(&0T_CQUAT&)
Current quarter
(&0CQUART&)
Current quarter-4
(&0T_CQUAT&-4)
Current quarter-4
(&0CQUART&-4)
Current quarter-3
(&0T_CQUAT&-3)
Current quarter-3
(&0CQUART&-3)
Current quarter-2
(&0T_CQUAT&-2)
Current quarter-2
(&0CQUART&-2)
0QT_45QUARTER Compare current
quarter and the
last four quarters
Current quarter-1
(&0T_CQUAT&-1)
Current quarter-1
(&0CQUART&-1)
Page 186
Wage Types for Reporting
This InfoCube contains all the payroll result wage types. In the SAP HR System, wage types sometimes have very
different meanings and their importance is valuated differently by users.
Wage types can be selected in a report based on this InfoCube by means of a filter. This selection can be made for
user wage types and technical wage types. The technical wage type /101 (Total Gross Amount) is, for example, of
significant size, therefore a corresponding example query is provided.
It is also possible to introduce a wage types hierarchy using the SAP Business Information Warehouse (BW) hier-
archy functions. This must, however, be explicitly created in the BW system since it is not provided by the source
system.
Time Breakdown
The payroll data is provided on a monthly basis by the extractor. Using update rules, this InfoCube can also calcu-
late quarterly and annual information from the payroll data (on a calendar basis in each case). Monthly assignment
is best explained using an example. The example assumes that payroll accounting is performed on a weekly basis.
(Monthly payroll runs are usually easy to assign).
Assume that the following payroll results are available for 1999:
For CW 1 in CW 1
For CW 1 in CW 2
For CW 2 in CW 2
For CW 3 in CW 3
For CW 4 in CW 4
For CW 4 in CW 5
For CW 5 in CW 5
The payment date for each week could be:
CW 1 : January 8
th
1999
CW 2 : January 15
th
1999
CW 3 : January 22
nd
1999
CW 4 : January 29
th
1999
CW 5 : February 5
th
1999
In this case, the data from the first six results is assigned to January and summarized. Only the last result is sum-
marized under February.
EmpIoyee versus Person
In the Business Information Warehouse (BW), the distinction is made between the info objects Employee
0EMPLOYEE and Person 0PERSON based on their attributes. The personal attributes, Gender 0GENDER, Na-
tionality 0NATION, and Language 0PERSLANGU are recorded as navigation attributes in the cube 0PY_C02.
Page 187
Remarks on the Restricted Key Figures
The wage types used in the restricted key figures are examples. Replace the examples with the wage types used
in your enterprise.
2.4.1.1 Query: 0PY_ C02_Q001: QuarterIy Wage Types Overview
Purpose:
This query provides a quarterly overview of any wage types. It is possible to navigate to employee level using vari-
ous organizational criteria.
Filter:
On calling up the query, a dialog box appears in which you can enter a wage type to restrict the dataset to be
evaluated. You can use individual values, wage type intervals or several individual wage types to enter the wage
type.
FiIter Description
0Y_WAGET Wage type
Structure:
Structure Description EIements FormuIa
0QT_4QUARTER Compare current quarter and
the last three quarters
Current quarter
(&0T_CQUAT&)
Current quarter
(&0CQUART&)
Current quarter-3
(&0T_CQUAT&-3)
Current quarter-3
(&0CQUART&-3)
Current quarter-2
(&0T_CQUAT&-2)
Current quarter-2
(&0CQUART&-2)
Current quarter-1
(&0T_CQUAT&-1)
Current quarter-1
(&0CQUART&-1)
Key Figure:
Key figure Remarks
Amount Information on the wage type
amount (for example, salary, al-
lowance, tax deductions)
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0PERSLANGU Employee language
Page 188
0CO_MST_AR Controlling area master cost center
0COUNTRY_ID Country grouping
Dimension Description
0QT_4QUARTER Quarterly comparison
0WAGETYPE Wage type
2.4.1.2 Query: 0PY_ C02_Q002: AnnuaI Wage Types Overview
Purpose:
This query provides an annual comparison (absolute and on a percentage basis) of any wage types. It is possible
to navigate to employee level using different/various organizational criteria.
FiIter:
On calling up the query, a dialog box appears in which you can restrict the amount of data to be evaluated using
the wage type. You can use individual values, wage type intervals or several individual wage types to enter the
wage type.
FiIter Description
0Y_WAGET Wage type
Structure:
0QT_2YEARS_DIFF Compare previous year/current
year
Previous year
(&0T_CYEAR&)
Previous year = current
calendar year-1
(&0CYEAR&-1)
Current calendar
year
(&0T_CYEAR&)
Current calendar year =
variable current calen-
dar year
(&0CYEAR&)
Difference Difference = current
calendar year -previous
year
Difference in % Difference in % = (cur-
rent year-previous
year) / previous year in
%
Page 189
Key Figure:
Key figure Remarks
amount (for example, salary,
allowance, tax deductions)
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0CO_MST_AR Controlling area master cost cen-
ter
0QT_2YEARS_DIFF Annual comparison
0WAGETYPE Wage type
2.4.1.3 Query: 0PY_ C02_Q003: Wage Types Overview for Ger-
many
Purpose:
This query provides a quarterly overview of various restricted, Germany specific wage types such as total gross
amount and others.
FiIter:
On calling up the query, a dialog box appears in which you can restrict the amount of data using the personnel
number, personnel area or personnel subarea. You can use individual values, intervals or several individual values
to enter the named values.
Page 190
FiIter Description
0Y_EMPLO Personnel number
0Y_PERSB Personnel area
0Y_PERSU Personnel subarea
Structure:
Struktur Description Elements Formula
0QT_5QUARTER Compare current quarter and the
last four quarters
Current quarter
(&0T_CQUAT&)
Current quarter
(&0CQUART&)
Current quarter-4
(&0T_CQUAT&-4)
Current quarter-4
(&0CQUART&-4)
Current quarter-3
(&0T_CQUAT&-3)
Current quarter-3
(&0CQUART&-3)
Current quarter-2
(&0T_CQUAT&-2)
Current quarter-2
(&0CQUART&-2)
Current quarter-1
(&0T_CQUAT&-1)
Current quarter-1
(&0CQUART&-1)
Key figure Remarks
OR_WT_BRUTTO Total gross amount
OR_WT_MA10 Standard pay
OR_WT_400 Employment tax
OR_WT_MM10 Overtime hours
OR_WT_269 Employer taxes
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
Page 191
Restricted key figures
2.4.1.4 Query: 0PY_ C02_Q004: Wage Types Overview USA
Purpose:
This query provides a quarterly overview of various restricted, USA specific wage types such as total gross amount
and others.
FiIter:
On calling up the query, a dialog box appears in which you can restrict the amount of data using the personnel
number, personnel area or personnel subarea. You can use individual values, intervals or several individual values
to enter the named values.
FiIter Description
0Y_EMPLO Personnel number
0Y_PERSB Personnel area
0Y_PERSU Personnel subarea
Structure:
0QT_5QUARTER Compare current quarter and
the last four quarters
Current quarter
(&0T_CQUAT&)
Current quarter
(&0CQUART&)
Current quarter-4
(&0T_CQUAT&-4)
Current quarter-4
(&0CQUART&-4)
Current quarter-3
(&0T_CQUAT&-3)
Current quarter-3
(&0CQUART&-3)
Current quarter-2
(&0T_CQUAT&-2)
Current quarter-2
(&0CQUART&-2)
Current quarter-1
(&0T_CQUAT&-1)
Current quarter-1
(&0CQUART&-1)
Restricted key figure Remarks
OR_WT_BRUTTO Total gross amount
OR_WT_401 TX withholding
OR_WT_MMXX Overtime
OR_WT_MQ10 Salary
Page 192
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0CO_MST_AR Controlling area master cost
center
Line characteristics:
Restricted key figures
CoIumn characteristics:
2.4.1.5 Query: 0PY_ C02_Q005: Wage Types Comparison for Per-
sonneI Areas
Purpose:
This query is used to compare wage types from different personnel areas/subareas. As for other organizational
criteria, the period is designed as a free characteristic.
On calling up the query, a dialog box appears in which you can enter a wage type to restrict the dataset to be
evaluated. You can use individual values, wage type intervals or several individual wage types to enter the wage
type.
FiIter Desciption
0Y_WAGET Wage type
Key Figure:
Key figure Remarks
amount
Page 193
0EMPLOYEE Employee
0GENDER Gender
0NATION Nationality
0CALMONTH Month
0QT_WAGETYPE Wage type
Page 194
2.5 PE Training and Event Management
2.5.1 InfoCube: 0PE_C01: Training and Event Management
Content:
The InfoCube Training and Event Management (0PE_C01) contains all transaction data relevant to business
events and bookings loaded from the connected source system(s). The data in the InfoCube is provided by the
InfoSources Attendance (OHR_PE_1) and Cancellation (OHR_PE_2).
The InfoCube contains the general key figures Number of cancellations (0CANCEL_NO), Number of attendances
(0BOOKING_NO), Cancellation fees (0CANCELFEE), Attendance fees (0BOOKINGFEE), Business event duration
in hours (0EVHOURS), Business event duration in days (0EVDAYS), and Business event costs (0EVENTCOSTS).
The standard system also provides calculated key figures (such as Average Cancellation Fees) and restricted key
figures. These are key figures that depend on certain characteristics (such as Billed attendance fees, Number of
internal attendances).
The following time dimensions are available for evaluations: calendar day, calendar year, calendar year/quarter
and calendar year/month.
A number of templates/structures are provided with the InfoCube in the standard system. These tem-
plates/structures contain the key figures in combination with certain calculation rules. The templates give you swift
and easy access to frequently used evaluations (such as Total bookings). The results are displayed as either ab-
solute or percentage values.
For more information on the technical elements (characteristics, time characteristics and so on) of the InfoCube,
see Remarks on the InfoCube.
InfoSources:
OHR_PE_1 Attendances
OHR_PE_2 Cancellations
Characteristics:
Hierarchy avaiI-
abIe?
0EVENTGROUP Business event group No Yes
0EVENTTYPE Business event type No No
0EVENT Business event Yes No
0ATTENDEETY Attendee type No No
0ATTENDEE Attendee No No
0EVCOSTINFO Fee indicator No No
0RECV_CCTR Receiving cost center Yes Yes
0CANC_DATE Cancellation date No No
0C_REASON Cancellation reason No No
0EMPLOYEE Employee Yes No
0PERSON Person No No
Page 195
0GENDER Gender No No
0NATION Nationality No No
0PERSLANGU Language No No
0AGE Age in years No Yes
0CO_MST_AR Controlling area of master cost
center
No No
0MAST_CCTR Master cost center Yes Yes
0JOB Job No No
0HRPOSITION Position Yes No
0CALQUARTER Calendar year /quarter
Key Figures:
InfoObject Description InfoObject units Aggregation
behavior
0BOOKING_NO Number of attendances None Additive
0BOOKINGFEE Attendance fee 0CURRENCY Additive
0CANCEL_NO Number of cancellations None Additive
0CANCELFEE Cancellation fee 0CURRENCY Additive
0EVDAYS Business event duration in days None Additive
0EVHOURS Business event duration in hours None Additive
0EVENTCOSTS Business event costs 0EVCURRCOST Additive
CaIcuIated Key Figures:
InfoObject Key figure Condition
0C_PE_001 Total bookings Key figure number of attendances +
key figure number of cancellations
0C_PE_002 Total fees Key figure attendance fees + key
figure cancellation fees
0C_PE_003 Average attendance fees Key figure attendance fees / key
figure number of attendances
0C_PE_004 Average cancellation fees Key figure cancellation fees / key
figure number of cancellations
0C_PE_005 Average total fees Total fees / total bookings
0C_PE_006 Revenue Total fees / business event costs
Page 196
InfoObject Key figure Condition
0R_PE_001 Billed attendance fees Key figure attendance fee, re-
stricted by characteristic fee indica-
tor
0R_PE_002 Allocated attendance fees Key figure attendance fee, re-
tor
0R_PE_003 Billed cancellation fees Key figure cancellation fee, re-
tor
0R_PE_004 Allocated cancellation fees Key figure cancellation fee, re-
tor
0R_PE_005 Number of internal attendees Key figure number of attendances,
restricted by characteristic attendee
type
0R_PE_006 Number of internal cancellations Key figure number of cancellations,
restricted by characteristic attendee
type
Units:
0EVCURRCOST Currency of business event costs Currency
Previous year
(&0T_CYEAR&)
Previous year = current
calendar year - 1
(&0CYEAR& - 1)
(&0T_CYEAR&)
Current calendar year =
variable current calen-
dar year
(&0CYEAR&)
Difference Difference = current
calendar year - previ-
ous year
0QT_PE_001 Compare previous
year with current year
Difference in % Difference in % = (cur-
rent calendar year -
previous year) / previ-
ous year in %
Current quarter - 4
(&0T_CQUAT& - 4)
Current quarter - 4
(&0CQUART& - 4)
Current quarter - 3
(&0T_CQUAT& - 3)
Current quarter - 3
(&0CQUART& - 3)
0QT_PE_002 4 quarters comparison
Current quarter - 2
(&0T_CQUAT& - 2)
Current quarter - 2
(&0CQUART& - 2)
Page 197
Current quarter - 1
(&0T_CQUAT& - 1)
Current quarter - 1
(&0CQUART& - 1)
Current quarter -4
(&0T_CQUAT& - 4)
Current quarter - 4
(&0CQUART& - 4)
Current quarter - 3
(&0T_CQUAT& - 3)
Current quarter - 3
(&0CQUART& - 3)
Current quarter - 2
(&0T_CQUAT& - 2)
Current quarter - 2
(&0CQUART& - 2)
Current quarter - 1
(&0T_CQUAT& - 1)
Current quarter - 1
(&0CQUART& - 1)
0QT_PE_003 Average 4 quarters
Average 4 quarters of quarter values / 4
Number of attendances
Number of bookings
0QT_PE_004 Total bookings
Total bookings Number of attendances
+ number of cancella-
tions
Number of cancellations
Total bookings Number of attendances
+ number of cancella-
tions
Attendances per can-
cellation (ratio)
/ number of cancella-
tions
0QT_PE_005 Attendance and can-
cellation rate
Cancellation rate: Can-
cellations per bookings
in percentage
Number of cancella-
tions / total bookings *
100
Attendance fees
Cancellation fees
0QT_PE_006 Total fees
Total fees Attendance fees + can-
cellation fees
Remarks:
Remarks on the Characteristics
You can display the available navigation characteristics by positioning the cursor on the characteristic in question
and using the right mouse button to call Characteristics.
The characteristic Age in years (0AGE) is a calculated characteristic: it calculates an employees age at the end of
a period.
The characteristic Attendee type (0ATTENDEETY) is used to differentiate and evaluate internal and external at-
tendees. This depends on what attendee types you have defined as internal and external. You must define atten-
dee types before you can evaluate employee data, for example.
Characteristic Employee vs. Person: A person can have multiple assignments as an employee. To be able to dis-
tinguish between work relationships (characteristic Employee 0EMPLOYEE) and real persons (characteristic Per-
son 0PERSON), a person is deemed an attribute of an employee.
Page 198
Remarks on the Time Characteristics
The time units used in the Infocube to calculate a time period are decimal minutes and decimal hours. In other
words, 100 minutes = 1 hour. So, for example, 1h 20 min = 1,30 decimal hours.
Remarks on the Restricted Key Figures
Restricted key figures are derived from the key figures of the InfoCubes using a filter of one or more characteristics
of the InfoCubes.
Remarks on the Units
The currency unit used to specify and calculate fees and costs in the InfoCube is the target currency US$. Totals
are rounded off to two places after the decimal point.
Remarks on the TempIates/Structures
The last completed quarter is taken as the calculation base in the structures 4 quarters comparison (0QT_PE_002)
and Average 4 quarters (0QT_PE_003), since there are complete values available for this quarter. So, for example,
in a query that compares 4 quarters, starting in the second quarter of 1999, the values of the last 4 completed
quarters are compared: 1/99, 4/98, 3/98 and 2/98.
In templates/structures where time periods are referenced, text variables (&0T_CYEAR&, &0T_CQUAT&) are used
to display the periods in the structure. When the query is executed, the corresponding values (calendar years, cal-
endar quarters) are generated automatically.
Example:
The text variable &0T_CYEAR& is used for Previous year and Current year in the structure Compare previous year
with current year. When the query is executed, the text variables are replaced by the relevant values: 1998 for
previous year and 1999 for current year.
Remarks on the Hierarchies
If hierarchies exist for the InfoObjects Business event group (0EVENTGROUP), organizational unit (0ORGUNIT)
and Master cost center (0MAST_CCTR), you can activate these with Characteristics. This enables the hierarchi-
cal representation of multi-layer aggregations.
In Training and Event Management, the hierarchical display feature is only available for business event groups that
have event dates for which bookings have actually been made.
SAP does not deliver hierarchies for Age in years. However, you can define your own hierarchies for the charac-
teristic Age in years (0AGE). The intervals in the structure are user-definable. You can, for example, define 5-year
intervals (25-30 years; 30-35 years and so on). This enables you to define hierarchies that suit company-specific
requirements and best reflect the age structure in your company.
You can switch the presentation hierarchy on and off as required using the Active switch under Presentation hier-
archy of the characteristic concerned.
Remarks on the Update RuIes
In the update rules, multiple fields from master data tables are read at the end of the period (usually on the last day
of the month) and these are written as characteristics to the InfoCube. This requires that the master data is loaded
and activated before the Infosources.
Page 199
2.5.1.1 Attendance and CanceIIation EvaIuations
2.5.1.1.1 Query: 0PE_C01_Q001: Number of Attendances and CanceIIations
Purpose:
This query displays the numbers of attendances and cancellations, the sum total of these, the total number of
bookings per business event group for the current year.
You can further differentiate the evaluation using the free characteristics by selecting line characteristics to suit
your requirements.
TempIates/Structures
Number of atten-
dances
Number of
bookings
Total bookings Number of atten-
dances + number
of cancellations
Key Figure:
TechnicaI name Key figure Remarks
0CANCEL_NO Number of cancellations
0BOOKING_NO Number of attendances
Total bookings Calculated in structure 0QT_PE_004
0EVENTTYPE Business event type
0EVENT Business event
0ATTENDEETY Attendee type
0ATTENDEE Attendee
0EVENTGROUP Business event group
Page 200
2.5.1.1.2 Query: 0PE_C01_Q002: AnnuaI Comparison of Bookings
Purpose:
This query compares the number of bookings for the current year with the total for the previous year, that is, the
sum total of attendances and cancellations. It also displays the absolute difference and the difference in percent-
age.
your requirements.
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year - 1
(&0CYEAR& - 1)
0QT_PE_001 Compare previous year with current
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
current calendar
year - previous
year
(current calendar
year - previous
year) / previous
year in %
Number of atten-
dances
Number of can-
cellations
Total Bookings Number of atten-
dances + number
of cancellations
Key Figures:
Key figure Remarks
Number of attendances Display hidden
Number of cancellations Display hidden
Remarks on the Key Figures:
You can hide the key figures used in a query if required. You do so by calling Characteristics with the right mouse
button and selecting Hide. You can display key figures that are hidden in the standard system by deactivating the
Hide option.
Page 201
0EVENTTYPE Business event group
0ATTENDEE Attendee
2.5.1.1.3 Query: 0PE_C01_Q003: Attendance and CanceIIation Rate
Purpose:
This query displays the attendance and cancellation rate from the previous year compared with that of the current
year. The key figure Attendance per cancellation displays the number of attendances per one cancellation, thus
indicating the ratio of cancellations to attendances. The key figure Attendance rate, on the other hand, indicates the
percentage of cancellations to total bookings.
your requirements
TempIates/Structures
Number of atten-
dances
Number of can-
cellations
dances + number
of cancellations
Attendances per
cancellation
(ratio)
Number of atten-
dances / number
of cancellations
0QT_PE_005 Attendance and cancellation rate
Cancellation rate:
cancellations per
bookings in per-
centage
Number of can-
cellations / total
bookings * 100
Key Figures:
TechnicaI name Key figure Remarks
0BOOKING_NO Number of attendances
0CANCEL_NO Number of cancellations
Attendances per cancellation Calculated in structure 0QT_PE_005
Cancellation rate Calculated in structure 0QT_PE_005
Page 202
0ATTENDEE Attendee
2.5.1.1.4 Query: 0PE_C01_Q004: Business Event Duration
Purpose:
This query serves to evaluate the duration of business events in days and hours for the current year. The query
also displays the business event duration in days and hours expressed as a percentage value of the total duration
of all business events. Reporting is done at the level of business event groups in the standard system.
your requirements.
Key Figures:
Key figure Remarks
Business event duration in days
Percentage distribution of days Business event duration in days per
characteristic value / Total business
event duration in days * 100
Business event duration in hours
Percentage distribution of hours Business event duration in hours per
characteristic value / Total business
event duration in hours * 100
0ATTENDEE Attendee
Page 203
2.5.1.2 EvaIuations of Business Event Fees
2.5.1.2.1 Query: 0PE_C01_Q005: Attendance and CanceIIation Fees
Purpose:
This query compares the fees incurred for business event attendance and cancellations per business event group
for the current year with those for the previous year. It also displays the difference expressed both as a percentage
and as an absolute value.
your requirements.
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year-1
(&0CYEAR&-1)
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
current calendar
year - previous
year
(current calendar
year - previous
year) / previous
year in %
Attendance fees
Cancellation fees
Total fees Attendance fees
+ cancellation
fees
Page 204
Key Figures:
Key figure Remarks
Total fees Calculated in structure 0QT_PE_006
Attendance fees Display hidden
Cancellation fees Display hidden
Hide option.
0ATTENDEE Attendee
Remarks on the Free Characteristics and FiIters:
You can evaluate training and education fees per employee, for example, using the drilldown function. You do so
by selecting the free characteristic Attendee as line characteristic and as filter the Attendee type you defined for
employees.
2.5.1.2.2 Query: 0PE_C01_Q006: Fee Distribution by InternaI and ExternaI Bookings
Purpose:
This query displays fee distribution by settlement type. The query compares attendance and cancellation fees for
the current year per business event group with those for the previous year, whereby internal and external fees are
taken separately.
your requirements.
year
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year-1
(&0CYEAR&-1)
Page 205
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
current calendar
year - previous
year
(current calendar
year - previous
year) / previous
year in %
Number of atten-
dances
Number of can-
cellations
Total bookings Attendance fees
+ number of can-
cellations
Attendance fees
Cancellation fees
+ cancellation
fees
Key Figures:
Key figure Remarks
Number of Attendances Display hidden
Number of Cancellations Display hidden
Hide option.
Page 206
0ATTENDEE Attendee
0EVCOSTINFO Fee indicator
Remarks on the Fee Indicators:
Indicator E stands for external billing, I for internal cost allocation.
2.5.1.2.3 Query: 0PE_C01_Q007: Fee Rates
Purpose:
This query compares the average business event fees incurred for the current year with the average fees for the
previous year. The query serves to evaluate the average cost of training measures per business event.
your requirements.
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year-1
(&0CYEAR&-1)
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
current calendar
year - previous
year
(current calendar
year - previous
year) / previous
year in %
Number of atten-
dances
Number of can-
cellations
dances + number
of cancellations
Attendance fees 0QT_PE_006 Total fees
Cancellation fees
Page 207
+ cancellation
fees
Key Figures:
Key figure Remarks
Average total fees Total fees / total bookings
Average attendance fees Attendance fees / number of atten-
dances; display hidden
Average cancellation fees Cancellation fees / number of can-
cellations; display hidden
Total bookings Number of attendances + number of
cancellations; display hidden
Total fees Attendance fees + cancellation fees;
display hidden
Remarks on Key Figures:
Hide option.
0ATTENDEE Attendee
2.5.1.3 EvaIuations of Organizer's SaIes and Costs
2.5.1.3.1 Query: 0PE_C01_Q008: AnnuaI Comparison of Revenues
Purpose:
This query compares the current years revenue received by the event organizer with that for the previous year.
The query evaluates revenue per business event group, where revenue is understood as business event fees mi-
nus business event costs. Total fees stand for business event sales here.
Page 208
your requirements.
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year-1
(&0CYEAR&-1)
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
current calendar
year - previous
year
(current calendar
year - previous
year) / previous
year in %
Attendance fees
Cancellation fees
+ cancellation
fees
Key Figures:
Key figure Remarks
Total revenue Total fees - Business event costs
Total fees Attendance fees + cancellation fees;
display hidden
Business event costs Display hidden
Hide option.
Page 209
0ATTENDEE Attendee
2.5.1.3.2 Query: 0PE_C01_Q009: AnnuaI Comparison of Business Event Costs
Purpose:
This query compares business event costs incurred for the current year with costs for the previous year. The query
also displays the increase in costs expressed as a percentage and as an absolute value.
your requirements.
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year-1
(&0CYEAR&-1)
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
current calendar
year - previous
year
(current calendar
year - previous
year) / previous
year in %
Key Figures:
Key figure Remarks
Business event costs
0ATTENDEE Attendee
Page 210
2.5.1.4 EvaIuations of EmpIoyees
2.5.1.4.1 Query: 0PE_C01_Q010: Training and Education Based on OrganizationaI
Assignment
Purpose:
This query compares event bookings per organizational unit for the current year with bookings per organizational
unit for the previous year.
your requirements.
FiIter:
The filter Attendee type is delivered empty in the standard system. Before you can use the filter in your evalua-
tions, you must assign the internal attendee types (e.g. Person) you want to use as values to the characteristic
Attendee type.
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year-1
(&0CYEAR&-1)
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
current calendar
year - previous
year
(current calendar
year - previous
year) / previous
year in %
Number of atten-
dances
Number of can-
cellations
Page 211
dances + number
of cancellations
Key Figures:
Key figure Remarks
Hide option.
0ATTENDEE Attendee
0PERSON Person
0EMPLOYEE Employee
0CO_MST_AR Controlling area of master cost center
0GENDER Gender
0AGE Age in years
2.5.1.4.2 Query: 0PE_C01_Q011: Training and Education Fees Based on Organiza-
tionaI Assignment
Purpose:
This query compares the costs incurred for training and education per organizational unit for the current year with
the costs for the previous year.
your requirements.
Page 212
FiIter:
Attendee type.
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year-1
(&0CYEAR&-1)
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
current calendar
year - previous
year
(current calendar
year - previous
year) / previous
year in %
Attendance fees
Cancellation fees
+ cancellation
fees
Key Figures:
Key figure Remarks
Hide option.
Page 213
0ATTENDEE Attendee
0PERSON Person
0EMPLOYEE Employee
2.5.1.4.3 Query: 0PE_C01_Q012: Training and Education by Target Audience
Purpose:
This query compares event bookings per job for the current year with bookings per job for the previous year.
your requirements.
FiIter:
Attendee type.
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year-1
(&0CYEAR&-1)
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
Current calendar
year - Previous
year
Page 214
(current calendar
year - previous
year) / previous
year in %
Number of atten-
dances
Number of can-
cellations
dances + number
of cancellations
Key Figures:
Key figure Remarks
Hide option.
0ATTENDEE Attendee
0PERSON Person
0EMPLOYEE Employee
0GENDER Gender
0AGE Age in years
0JOB Job
Page 215
2.5.1.4.4 Query: 0PE_C01_Q013: Training and Education Fees by Target Audience
Purpose:
This query displays the fees for training and education per job for the current year compared with the costs per job
for the previous year.
your requirements.
FiIter:
Attendee type.
Previous year
(&0T_CYEAR&)
Previous year =
current calendar
year-1
(&0CYEAR&-1)
year
Current calendar
year
(&0T_CYEAR&)
Current calendar
year = variable
current calendar
year
(&0CYEAR&)
current calendar
year - previous
year
(current calendar
year - previous
year) / previous
year in %
Attendance fees
Cancellation fees
+ cancellation
fees
Key Figures:
Key figure Remarks
Page 216
Hide option.
0ATTENDEE Attendee
0PERSON Person
0EMPLOYEE Employee
0GENDER Gender
0AGE Age in years
0JOB Job
2.5.2 Key figures
Number of CanceIIations
InfoObject: 0CANCEL_NO
Content: This key figure displays the number of cancellations. Please note that the number of cancel-
lations, which results from a cancellation transaction, can be greater than 1. This would be
the case with the cancellation of a group booking where the number of attendees is greater
than 1. Refer to the description of the key figure Number of Attendances.
Definition/Formula: None (The key figure corresponds to the value contained in the InfoObject.)
Prerequisites: None
Number of Attendances
InfoObject: 0BOOKING_NO
Content: This key figure displays the number of attendances. Please note that the number of atten-
dance bookings, which results from a booking transaction, can be greater than 1. This would
be the case for a group booking (for a company or an organizational unit) where the number
of attendees is greater than 1.
Page 217
Prerequisites: None
ExternaI event price
InfoObject: 0EVPRICEEXT
Content: The key figure contains the external event price.
Prerequisites: None
InternaI event price
InfoObject: 0EVPRICEINT
Content: The key figure contains the internal event price.
Prerequisites: None
Maximum event capacity
InfoObject: 0EVMAXCAP
Content: The key figure contains the maximum event capacity.
Prerequisites: None
Minimum event capacity
InfoObject: 0EVMINCAP
Content: The key figure contains the minimum event capacity.
Prerequisites: None
Optimum event capacity
InfoObject: 0EVOPTCAP
Content: The key figure contains the optimum event capacity.
CanceIIation fee
InfoObject: 0CANCELFEE
Content: The key figure contains the cancellation fee.
Attendance fee
InfoObject: 0BOOKINGFEE
Page 218
Content: The key figure contains the attendance fee.
Prerequisites: None
Business event duration in hours
InfoObject: 0EVHOURS
Content: The key figure contains the business event duration in hours.
Prerequisites: None
Business event duration in days
InfoObject: 0EVDAYS
Content: The key figure contains the business event duration in days.
Prerequisites: None
Business event costs
InfoObject: 0EVENTCOSTS
Content: The key figure contains the event costs.
Prerequisites: None
Page 219
3 Logistics
3.1 SD SaIes and Distribution
3.1.1 InfoCube: 0SD_C01: Customer
Content:
Key figures: Customer
InfoSource(s):
2LIS_01_S001: SD Customer
Characteristics:
ExternaI hierarchy
avaiIabIe?
0DISTR_CHAN Distribution channel No No
0DIVISION Division No No
0MATERIAL Material number Yes Yes
0SALESORG Sales organization Yes Yes
0SOLD_TO Sold-to party Yes Yes
0CALMONTH Calendar year / month
0CALWEEK Calendar year / week
Key figures:
behavior
0CRMEM_CST Credit memo cost 0STAT_CURR Cumulated data
Page 220
0CRMEM_QTY Credit memo quantity 0BASE_UOM Cumulated data
0CRMEM_VAL Net value of credit memos 0STAT_CURR Cumulated data
0INCORDCST Cost of incoming orders 0STAT_CURR Cumulated data
0INCORDQTY Quantity of incoming orders 0BASE_UOM Cumulated data
0INCORDVAL Net value of incoming orders 0STAT_CURR Cumulated data
0INVCD_CST Cost of invoiced sales 0STAT_CURR Cumulated data
0INVCD_QTY Invoiced quantity 0BASE_UOM Cumulated data
0INVCD_VAL Net value of invoiced sales 0STAT_CURR Cumulated data
0OPORDQTYBM Open orders quantity in base unit of
measure
0BASE_UOM Cumulated data
0OPORDVALSC Net value of open orders 0STAT_CURR Cumulated data
0ORD_ITEMS Number of order items Cumulated data
0RTNSCST Cost of incoming returns 0STAT_CURR Cumulated data
0RTNSQTY Returns quantity 0BASE_UOM Cumulated data
0RTNSVAL Net value of incoming returns 0STAT_CURR Cumulated data
0RTNS_ITEMS Number of returns items Cumulated data
Units:
0STAT_CURR Statistics currency Currency
0BASE_UOM Base unit of measure Unit of measure
In the standard system only the period is updated from the info structure.
3.1.1.1 Query: 0SD_C01_Q010 Returns
Purpose:
This query displays information about returns and their value in proportion to all orders.
Structure:
Key figure Comments
Number of return items Number of return items
Page 221
Number of order items Number of order items
Rate of returns Number of return items / Number of order items in %
Returns quantity Quantity of deliveries that have been returned
Quantity of incoming orders
in base unit of measure
Returns quantity in % Quantity of returns as a percentage of sales volume
Net value of returns Net value of deliveries that have been returned
Net value of incoming orders Net value of incoming orders
Returns value in % Value of returns as a percentage of sales volume value (net values)
0SALESORG Sales organization
0DISTR_CHAN Distribution channel
0DIVISION Division
3.1.1.2 Query: 0SD_C01_Q011 Incoming Orders
Purpose:
This query displays incoming order data.
Structure:
Key figure Comments
in base unit of measure
Incoming order cost Costs of incoming orders
Net value of incoming orders Net value of incoming orders
Number of order items Number of order items
Value per order item % Net value of incoming orders / Number of order items in percent
Page 222
0DIVISION Division
3.1.1.3 Query: 0SD_C01_Q012 Credit Memos
Purpose:
This query is used to display credit memos and their value in proportion to the sales volume.
Structure:
Key figure Comments
Credit memo quantity Quantity in credit memos
Credit memo cost Cost is net value minus costs for an order
Credit memo net value Credit memo in net value Gutschrift ber einen Nettowert
Credit memo quantity % Credit memo quantity / Sales volume quantity in percent
Credit memo value % Credit memo net value / Sales volume net value in percent
0DIVISION Division
Page 223
3.1.1.4 Query: 0SD_C01_Q013 SaIes VoIume
Purpose:
This query displays sales volume data.
Structure:
Key figure Comments
Sales volume quantity Total quantity of delivered items
Net sales volume value Total value of deliveries
Sales volume cost Total cost of deliveries
0DIVISION Division
3.1.1.5 Query: 0SD_C01_Q0001 - SaIes: PIan/actuaI/variance cur-
rent year/previous year
Purpose:
This query shows plan/actual values current year and previous year
Structure:
Key figures Comments
Plan sales cumulative year
Planed sales cumulative year
Actual sales cumulative year Actual sales cumulative year
Actual sales in previous year Actual sales in previous year
Plan variance Plan variance
Plan variance % Variance of sales in percent (current year)
Page 224
Variance previous year % Variance of sales in percent (previous year)
InfoObject Comments:
0CALMONTH CalYear/Month
0SOLD_TO_0INDUSTRY Industry
0SOLD_TO_0COUNTRY Country
0MATERIAL_0MATL_TYPE Material type
0MATERIAL Material
0MATERIAL_0PROD_HIER Product hierarchy
0DIVISION Division
3.1.1.6 Query: 0SD_C01_Q0002 - SD: Incoming orders/revenue:
Months of current year
Purpose:
This query shows incoming orders und revenues per month of current year
Structure:
Open IO net value
Open incoming orders net value
IO net value Incoming orders net value
IO cost value Incoming orders cost value
Material cost share Material cost share
Net value of invoices sales Net value of invoiced sales
Net value of credit memos Net value of credit memos
Corrected sales revenue Net value of invoices sales minus Net value of credit memos
Page 225
0DIVISION Division
0SOLD_TO Sold to party
3.1.1.7 Query: 0SD_C01_Q0003 - SD: Returns: Quantities + va-
Iues
Purpose:
Query shows returns quantities and values.
Structure:
Net value of incoming returns Net value of incoming returns
Returns quantity Returns quantity
0DIVISION Division
0SOLD_TO Sold to party
0MATERIAL Material
3.1.1.8 Query: 0SD_C01_Q021 Product AnaIysis
Purpose
List the Products of a company by incoming orders, sales and contribution margin.
Page 226
Structure
Incoming orders Net value of incoming orders
Incoming orders Qty. Quantity of incoming orders
Sales Net value of invoiced sales (sold products)
Inv. Qty Invoiced Quantity
Open orders Order, which has not been delivered yet
Open orders Qty Open orders quantity
Characteristics:
0MATERIAL_0MATL_GROUP Material group
0MATERIAL Material
3.1.1.9 0SD_C01_Q022 AnaIyses Product ProfitabiIity
Purpose:
This query analyses the product profitability.
Structure:
Key Figure Comments
Share of total (%) Percentage of Total Sales
Cost of Sales Stock value of Invoiced Sales (Stock value multiplied by the order/invoice
quantity)
Share of total (%) Percentage of Total Cost of Sales
Cont. Marg. Contribution Margin (Sales Cost of Sales)
Cont. Marg. (%) Contribution Margin in percent
Share of total (%) Percentage of Total Contribution Margin
Characteristics:
0MATERIAL Material
0SOLD_TO_0COUNTRY Country of the Sold-to party (customer)
0MATERIAL_0MATL_GROUP Material group
Page 227
3.1.1.10 Query: 0SD_C01_Q023 Top Customer
Purpose:
This query analyses the Sales of a Customer over a period of time.
Structure:
Key Figure Comments
quantity)
Characteristics:
0SOLD_TO Sold-to Party (Customer)
0DIVSION Division
0MATERIAL Material
3.1.1.11 Query: 0SD_C01_Q024 AnaIysis Incoming Orders
Purpose:
This query analyses the incoming orders in relation to the open orders.
Structure:
Key figure Comments
Incoming orders (IO) Net value of incoming orders
Open orders (OO) Order, which has not been delivered yet
OO % IO Percentage open orders of incoming orders
Delta IO/OO Incoming orders open orders
Characteristics:
0DISTR_CHAN Distribution Channel
0DIVISION Division
0SOLD_TO_0INDUSTRY Industry of the Sold-to party (customer)
0SOLD_TO Sold to party (customer)
Page 228
0MATERIAL Material
3.1.1.12 Query: 0SD_C01_Q025 AnaIysis SaIes/Cost
Purpose:
This Query compares the Sales with the Cost of Sales on a monthly basis.
Structure:
Key Figure Comment
quantity)
Cost of Sales (%) Cost of Sales as percentage of Sales
Characteristics:
0CALMONTH Calendar Year/Month
0SOLD_TO Sold-to Party (Customer)
0SALESORG Sales Organization
0DIVISION Division
3.1.1.13 Query: 0SD_C01_Q026 AnaIysis Distribution ChanneI
Purpose:
This Query analyses the Order Volume per Distribution Channel.
Structure:
Key Figure Comment
Share of total (%) Percentage of Total Sales
quantity)
Share of total (%) Percentage of Total Cost of Sales
Page 229
Share of total (%) Percentage of Total Contribution Margin
Characteristics:
0SOLD_TO_0INDUSTRY Industry of the Sold-to party (customer)
3.1.2 InfoCube: 0SD_C02 - DeIiveries
Content:
Key figures delivery
InfoSource(s):
2LIS_01_S005: Deliveries
Characteristics:
attribut avaiIabIe?
ExternaI hierarchie
avaiIabIe?
0FORWAGENT Carrier Yes Yes
0RECIPCNTRY Destination country No No
0ROUTE Route No No
0SHIP_POINT Shipping point No No
0CALDAY
Calendar day
Page 230
Key figures:
InfoObject Description Unit-InfoObject Aggregation-
behavior
0DEL_GR_WT Gross weight of deliveries 0UNIT_OF_WT Cumulated data
0DEL_NT_WT Net weight of deliveries 0UNIT_OF_WT Cumulated data
0DEL_VOL Volume of deliveries 0VOLUMEUNIT Cumulated data
0DEL_WRK Labor required for deliveries on hand Cumulated data
0RTNS_GR_WT Gross weight of returns deliveries 0UNIT_OF_WT Cumulated data
0RTNS_NT_WT Net weight of returns deliveries 0UNIT_OF_WT Cumulated data
0RTNS_VOL Volume of returns delivery 0VOLUMEUNIT Cumulated data
0RTNS_WRK Labor required for returns deliveries
on hand
Cumulated data
Units:
0UNIT_OF_WT Unit of weight Units of measure
0BASE_UOM Volume unit Units of measure
Comments on update ruIes:
3.1.2.1 Query: 0SD_C02_Q0001 - SaIes: weekIy deIiveries
Purpose:
Key figures deliveries per shipping point
Structures:
Gross weight of deliveries
Gross weight of deliveries
Labour required for deliveries
on hand
Labour required for deliveries on hand
Volume of deliveries Volume of deliveries
Gross weight of returns de-
liveries
Gross weight of returns deliveries
Labour required for returns
on hand
Labour required for returns on hand
Page 231
0ROUTE Route
0RECIPCNTRY Destination
0FORWAGENT Carrier
3.1.3 InfoCube: 0SD_C03 SaIes Overview
Contents:
This InfoCube contains all transaction data from sales orders, deliveries and billing documents/invoices.
InfoSource(s):
2LIS_01_S260: SD - Sales order
2LIS_01_S261: SD Delivery
2LIS_01_S262: SD - Billing document
2LIS_01_S263: SD - Sales order / delivery
Characteristics:
ExternaI hierarchy
avaiIabIe?
0BILLTOPRTY Bill-to party Yes Yes
0DOC_CATEG Sales document category No No
0PLANT Plant No No
0SALESORG Sales organization No Yes
0SALES_GRP Sales group No No
0SALES_OFF Sales office No No
0SHIP_TO Ship-to party Yes Yes
0SOLD_TO Sold-to party Yes Yes
Page 232
0SHIP_POINT Shipping point No No
0PAYER Payer Yes Yes
0DOC_CLASS Document class
Order/Delivery/Invoice
No No
0DEB_CRED Credit/debit postings (C/D) No No
Key figures:
behavior
0SUBTOT_1S Pricing subtotal 1 from pricing de-
termination procedure in statistics
currency
0STAT_CURR Cumulated data
currency
currency
currency
currency
currency
Page 233
0OPORDQTYBM Open order quantity in base unit of
measure
0OPORDVALSC Net open order value in statistics
currency
This Keyfigure is not updated by
SAP standard updating. If you want
this keyfigure to be updated, please
create your own update rules (see
note 136605 in OSS).
0DLV_QTY_BM Actual delivered quantity in base unit
of measure
0QUANT_B Quantity in base unit of measure 0BASE_UOM Cumulated data
0DOCUMENTS Number of documents Cumulated data
0DOC_ITEMS Number of document items Cumulated data
0NET_VAL_S Net value in statistics currency 0STAT_CURR Cumulated data
0COST_VAL_S Cost in statistics currency 0STAT_CURR Cumulated data
0GR_WT_KG Gross weight in kilograms Kilograms Cumulated data
0NT_WT_KG Net weight in kilograms Kilograms Cumulated data
0VOLUME_CDM Volumes in cubic decimeters Cubic decimeters Cumulated data
Units:
0STAT_CURR Statistics currency Currency
In the standard system, the month is updated from the info structure.
Page 234
Comments on SpeciaI InfoObjects
0DEB_CRED Credit/Debit Postings (C/D)
Differentiates between target and actual documents.
The following sales document categories (0DOC_CATEG = VBTYP)
generate target postings in the InfoCube:
- Sales order processing:
- - Credit memo request ............(VBTYP = K)
- - Returns ..................................(VBTYP = H)
- Delivery processing:
- - Return delivery ...................(VBTYP = T)
- Invoice processing:
- - Credit memo............................(VBTYP = O)
- - Cancelled invoice.....................(VBTYP = N)
- - Internal consumption (credit)(VBTYP = 6)
All other categories of sales documents generate actual postings in
the InfoCube.
- 0DOC_CLASS - Document classification: Order/Delivery/Invoice
- Classifies documents as order, delivery and invoicing (billing)
documents:
- - O = Order
- - D = Delivery
- - I = Invoice
- :
-
A combination of 0DOC_CLASS and 0DEB_CRED enables you to classify all sales documents simply.
For example:
Page 235
Key figure 0DOC_CLASS 0DEB_CRED Significance
Incoming orders O D Positive sales docu-
ments (orders, schedul-
ing agreements, etc.)
Returns O C Negative sales docu-
ments (returns, credit
memo requests, etc.)
0DIVISION The divison is updated from the document item.
0DOCUMENTS Number of documents (document counter)
We recommend that you only use the document counter along with
characteristics from the document header (header characteristics).
For example, 0SALES_ORG, 0DISTR_CHAN, 0BILLTOPRTY,
0SHIP_TO, 0SOLD_TO, 0PAYER, 0DOC_CATEG..
3.1.3.1 Query: 0SD_C03_Q003 Returns
Purpose:
This query is used to display the returns and their value in proportion to all incoming orders.
Structure:
Key figure Comments
No. returns items Number of returns items
Order items Number of order items
No_Items_% Number of return items / Number of order items in %
No. returns Number of returns (number of return documents)
No. orders Number of orders
Number_% Number or returns / Number of orders in %
Incoming returns qty Quantity of returns (quantity = total quantity of returned goods)
Incoming order qty Quantity in incoming orders
Quantity_% Percentage of incoming orders that are returns
Incoming returns net val. Net value of deliveries that have been returned
Incoming order value Net value of incoming orders
Page 236
Value_% Percentage value of net incoming order value that are returns
0DIVISION Division
3.1.3.2 Query: 0SD_C03_Q004 Incoming Orders
Purpose:
This query displays incoming order data.
Structure:
Key figure Comments
No. order items Number of order items
Incoming order qty Quantity of items in incoming orders
Incoming order val. Net value of incoming orders
Average value of order Value of incoming orders / Number of orders in %
0DIVISION Division
3.1.3.3 Query: 0SD_C03_Q005 Credit memos
Purpose:
This query displays credit memo values in proportion to the total billing document values.
Page 237
Structure:
Key figure Comments
No. credit memos items Number of credit memos items
No. billing documents items Number of billing documents items
Number_% Number of credit memos / Number of billing documents in %
Credit memo qty Quantity of credit memos (quantity of goods in credit memos)
Invoiced quantity Quantity of invoiced goods
Credit memo quantity_% Credit memo quantity / Invoiced quantity in %
Credit memo value Net value of credit memos
Invoiced sales net value Net value of invoiced sales
Value_% Credit memo value / Invoiced value in %
Credit memo: cost Credited cost * quantity
Invoiced sales: cost Invoiced cost * quantity
CostValue_% Credit value / Invoiced value in %
0DIVISION Division
3.1.3.4 Query: 0SD_C03_Q006 DeIiveries
Purpose:
This query displays delivery data.
Structure:
Key figure Comments
No. delivery items Number of delivery items
Delivery qty Quantity of delivered goods
Delivery gross weight Gross weight of deliveries
Delivery net weight Net weight of deliveries
Page 238
Delivery volume Volume of deliveries
0DIVISION Division
3.1.3.5 Query: 0SD_C03_Q007 BiIIing Documents
Purpose:
This query displays billing document data.
Structure:
Key figure Comments
No. invoiced items Number of invoiced items
Invoiced quantities Invoiced quantities
Invoiced sales net value Net value of all invoices
Invoiced sales: cost Invoiced cost * quantity
0DIVISION Division
3.1.3.6 Query: 0SD_C03_Q008 FuIfiIIment Rates
Purpose:
This query displays open sales orders data.
Page 239
Structure:
Open orders qty Quantity of order goods that have not yet been delivered
Incoming orders qty Quantity of goods in incoming orders
Fulfillment rate_quantity (Incoming order quantity open order quantity) / incoming order quantity
0DIVISION Division
3.1.3.7 Query: 0SD_C03_Q009 SaIes VaIues
Purpose:
This query displays information about order and sales values.
Structure:
Key figure Comments
Incoming orders (net val.) Net value of incoming orders
Incoming returns: net. Val. Net value of deliveries that have been returned
Invoiced sales net value Net value of invoiced sales
Credit memos net val. Net value of credit memos
0DIVISION Division
Page 240
3.1.3.8 Query: 0SD_C03_Q010 Order, DeIivery and SaIes Quanti-
ties
Purpose:
This query displays the order, delivery and sales quantities.
Structure:
Key figure Comments
Incoming orders qty. Quantity of incoming order goods in items
Incoming returns qty. Quantity of returns goods in items
Delivery qty. Quantity of delivered goods in items
Delivery returns qty. Quantity of return deliveries goods in items
Invoiced quantity Quantity of invoiced goods in items
Credit memos: qty Quantity of credit memos goods in items
0DIVISION Division
3.1.3.9 Query: 0SD_C03_Q011 FauItIess SaIes Order Processing
Purpose:
This query displays which sales orders were processed without problems.
Sales order processing is regarded as faultless if nothing has been returned.
Structure:
Key figure Comments
Orders items Number of orders items
No. returns items Number of returns items
Number_% (Number of orders items - number of returns items) / Number of orders
items in %
Number Number of orders - Number of returns
Page 241
Incoming orders qty. Quantity of goods in incoming orders
Incoming returns qty. Quantity of goods in returned deliveries
Quantity_% (Incoming order quantity returns quantity) / Incoming order quantity in %
Quantity Incoming order quantity returns quantity
Incoming order val Net value of incoming orders
Incoming returns: net.val Net value of deliveries that were returned
Value_% (Incoming order value returns value) / Incoming order value in %
Value Incoming order value - returns value
0DIVISION Division
Page 242
3.2 MateriaIs Management
3.2.1 MM-IC Inventory Management
3.2.1.1 Remarks on FiIIing Non-CumuIative InfoCubes
3.2.1.1.1 Reference Day for Non-CumuIative VaIues in the OLTP and in the BW Sys-
tem
The non-cumulatives for the non-cumulative InfoCube and those in the OLTP refer to the end-of-day non-
cumulatives:
When loading data, the non-cumulative data (see below) is uploaded as end-of-day non-cumulatives. When
running the delta initialization for the transaction data, all movements from the day after the non-cumulative key
date must be subsequently uploaded.
If OLTP evaluations and BW evaluations are compared, the values will be identical.
ExampIe:
OLTP Data:
Closing non-cum. for 1.1.99: 100 units
Inflow 1.1.99: 20 units
Inflow 2.1.99 10 units
Outflow 3.1.99 5 units
A non-cumulative overview in the OLTP results from this:
Key date Non-cum.
1.1.99 100
2.1.99 110
3.1.99 105
When uploading the non-cumulative data from 1.1.99, the non-cumulative 100 units is loaded. Since the inflow of
20 units is already contained in the (end-of-day) non-cumulative of 100 units on the OLTP side, only movements
after the 1.1.99 may then be uploaded when running the delta initialization.
A non-cumulative overview in BW subsequently shows:
Key date Non-cum. Delta
1.1.99 100 --
2.1.99 110 10
3.1.99 105 05
It is necessary to go through various steps to fill the non-cumulative InfoCube 0IC_C01, or. 0IC_C02:
3.2.1.1.2 Connecting PIant Non-CumuIatives to BW (InfoCube 0IC_C01)
InfoSources:
2LIS_03_S196 Goods movements
Page 243
2LIS_03_S198 Periodical plant non-cumulative
Activities in OLTP
a) Start program RMCBNEUA for InfoStructure S196, version 000
b) Start program RMCBNERP for InfoStructure S196, version 000
A company code must be entered here as a restriction criterion for the accounting documents. If the accounting
documents, that belong to the material documents, refer to more than one company code, the program must be
executed more than once with the corresponding restriction for the other company codes.
c) Start program RMCBNEUB for InfoStructure S032, version 000
d) Start program RMCBS198 for InfoStructure S198 (non-cumulative for the key date, key date must be included in
the analysis period)
The respective structures must be empty. They are delivered empty as standard. If filling the InfoCube proves un-
successful and all the activities have to be gone through once more, they can be emptied again using transaction
RMCVISCP.
Activities in BW
a) Start the initialization: InfoSource 2LIS_03_S198 for a chosen key date, for example, 1.1.1996.
Enter update parameter Initialization.
Note: You may only start the initialization one time. If the initialization is not started, no opening non-cumulative
is loaded, and the opening non-cumulative is, therefore, calculated as zero.
When initializing, restrictions can be set, for example, for particular material numbers or plants.
b) Initializing the goods movements: InfoSource 2LIS_03_S196; period 2.1.1996 current.
The day after the key date for the non-cumulative initialization must be entered here, since you can assume that
all movements have already previously influenced the calculation of the non-cumulative.
Update parameter: Initialization of the Delta Process. You can then only use the session Delta Update.
Note: Restrictions can also be set when initializing goods movements. With this, however, it is important to be
aware that all delta movements (therefore also ones that are not restricted) are uploaded when running a delta
upload. Thus, for previously excluded movements (for example, certain materials or plants), movements do also
exist, but without an initial non-cumulative or any initial movements. If evaluations for these originally excluded
materials or plants are then made, the non-cumulatives calculated here are incorrect since these initial values are
missing. Both the initialization of the non-cumulatives as well as the initialization of the transaction data should,
therefore, be made, provided that organizational measures do not prevent excluded elements from also influencing
evaluations.
SpeciaI features (ExampIes)
1. Connecting a new plant, creating a new material
Since no opening non-cumulatives exist here, the non-cumulative changes can be posted to BW via the delta
process using InfoSource 2LIS_03_S196.
2. Connecting plants or materials, that were already active in the source system and have opening non-
cumulatives:
The steps described above should be carried out in the OLTP system and in the BW system for the plant con-
cerned (materials).
Page 244
3.2.1.1.3 Connecting Warehouse Non-CumuIatives to BW (InfoCube 0IC_C02)
Activities in the OLTP
Start program RMCBNEUA for S195
Start program RMCBNEUB for S032, only if not yet carried out for plant non-cumulatives, i.e. optional
Start program RMCBS197
All remarks for plant non-cumulatives apply here in the same way.
Activities in BW
All the activities listed under plant non-cumulatives should be carried out for 2LIS_03_S195.
3.2.1.2 InfoCube: 0IC_C01 Goods Movements: PIant and Stocks
Content:
Stocks.
InfoSource(s):
2LIS_03_S196
2LIS_03_S198
Characteristics:
Characteristics
avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0REVERSEDOC Indicates that data should be can-
celled
No No
0MATERIAL Material number Yes, Material type,
Division, Material
group, Product Hi-
erarchy
No
0PLANT Plant No No
0FISCVARNT Fiscal Year Variants
Page 245
0FISCPER Fiscal Year / Period
0CALWEEK Calendar Year / Week
0CALMONTH Calendar Year / Month
0CALDAY Calendar Day
Key Figures:
0TOTUSVLAVG Average Total consumption value 0LOC_CURRCY Additive
0TOTUSQTAVG Average total consumption quantity 0BASE_UOM Additive
0CNSSTKQAVG Average Consignment stock quantity 0BASE_UOM Additive
0VALSTKQAVG Average Valuated stock quantity 0BASE_UOM Additive
0VALSTKVAVG Average Valuated stock value 0LOC_CURRCY Additive
0RECCNSSTCK Consignment stock receipts quantity 0BASE_UOM Additive
0NO_REVERSE Number of cancellations Additive
0NO_MATMOVE Number of times material move-
ments
Additive
0NO_UNPL_US Number of times an unplanned us-
age has been recorded
Additive
0NO_CNS_ISS Number of times consignment stock
has been issued
Additive
0NO_CNS_REC Number of times consignment stock
has been received
Additive
0NO_TOT_US Number of times the total usage has
been updated
Additive
0NO_VAL_REC Number of times valuated stock has
been received
Additive
0NO_VAL_ISS Number of times valuated stock has
been issued
Additive
0CNSSTCKQTY Quantity of consignment stock 0BASE_UOM Additive
0ISSCNSSTCK Quantity of consignment stock that
has been issued
0BASE_UOM Additive
0VALSTCKQTY Quantity of valuated stock 0BASE_UOM Additive
0ISSVALSTCK Quantity of valuated stock issues 0BASE_UOM Additive
0TOT_US_QTY Total consumption quantity 0BASE_UOM Additive
0TOT_US_VAL Total consumption value 0LOC_CURRCY Additive
Page 246
0UNP_US_QTY Unplanned usage quantity 0BASE_UOM Additive
0UNP_US_VAL Unplanned usage value 0LOC_CURRCY Additive
0RECVALSTCK Valuated stock receipts quantity 0BASE_UOM Additive
0RECVS_VAL Valuated stock receipts value 0LOC_CURRCY Additive
0VALSTCKVAL Value of calculated stock 0LOC_CURRCY Additive
0ISSVS_VAL Valuated outward movement 0LOC_CURRCY Additive
Units:
0BASE_UOM Basic unit of measure Unit
Data comes from the LIS
In some queries (for example, ranges of coverage), a predefined SAP material type is used as a filter. Check
whether your company also uses this material type. If not change it, and save the query and the same workbook.
3.2.1.2.1 Query: 0IC_C01_Q0001 Warehouse Inventory Turnover
Intended Purpose:
These key figures (KPIs) supply data, that illustrate the inventory turnover cycles for the analysis period.
Structure(s):
Key Figure Remarks
Warehouse Inventory Turn-
over of Total Stock
Specifies how often average total stock has been consumed. (Total con-
sumption quantity / Total stock- average quantity)
over of Consignment Stock
Specifies how often average valuated stock has been consumed. (Total
consumption quantity / Consignment stock average quantity)
over of Valuated Stock
Specifies how often average valuated stock has been consumed. (Total
consumption quantity / Valuated stock- average quantity)
Average Total Stock Ware-
house Inventory Turnover
Specifies how often average total stock has been consumed based upon
the average total usage. (Average total consumption quantity / Total stock
average quantity)
Average Warehouse Inven-
tory Turnover of Consign-
ment Stock
Specifies how often average consignment stock has been consumed
based upon the average total usage. (Average total consumption quantity /
Consignment stock average quantity)
Page 247
Average Warehouse Inven-
tory Turnover of Valuated
Stock
Specifies how often average valuated stock has been consumed based
upon the average total usage. (Average total consumption quantity / Valu-
ated stock- average quantity)
0MATERIAL_0MATL_TYP Material Type
0MATERIAL Material Number
0PLANT Plant
3.2.1.2.2 Query: 0IC_C01_Q0002 Inventory Days of SuppIy - Quantity
Purpose:
Indicates how many days the inventory can satisfy the demand based on quantity.
Structure(s):
Key Figure Remarks
Total DOS - Quantity Inventory days of supply of both, the consignment stock and valuated
stock, together.
Consignment Stock DOS -
Quantity
Inventory days of consignment stock
Valuated Stock DOS - Quan-
tity
Inventory days of supply of valuated stock.
InfoObjects Description
0PLANT Plant
Page 248
3.2.1.2.3 Query: 0IC_C01_Q0003 Inventory Days of SuppIy - VaIue
Purpose:
Indicates how many days the inventory can satisfy the demand based on value.
Structure(s):
Key Figure Remarks
Inventory DOS Value Inventory Days of Supply of valuated stock based on value
0PLANT Plant
3.2.1.2.4 Query: 0IC_C01_Q0004 Finished Goods Inventory Days of SuppIy - Quantity
Purpose:
Indicates how many days the inventory can satisfy the demand with finished goods based on quantity.
Structure(s):
Key Figure Remarks
stock, together.
Consignment Stock DOS -
Quantity
Valuated Stock DOS - Quan-
tity
Page 249
0PLANT Plant
3.2.1.2.5 Query: 0IC_C01_Q0005 Finished Goods Inventory Days of SuppIy - VaIue
Purpose:
Indicates how many days the inventory can satisfy the demand with finished goods based on value.
Structure(s):
Key Figure Remarks
0PLANT Plant
3.2.1.2.6 Query: 0IC_C01_Q0006 Raw MateriaI Days of SuppIy - Quantity
Purpose:
Indicates how many days the inventory can satisfy the demand of raw materials based on quantity.
Structure(s):
Key Figures Remarks
stock, together.
Consignment Stock DOS
Quantity
Valuated Stock DOS
Quantity
Page 250
0PLANT Plant
3.2.1.2.7 Query: 0IC_C01_Q0007 Raw MateriaI Days of SuppIy - VaIue
Purpose:
Indicates how many days the inventory can satisfy the demand of raw materials based on value
Structure(s):
Key Figure Remarks
0PLANT Plant
3.2.1.2.8 Query: 0IC_C01_Q0008 Inventory ObsoIete
Purpose:
The inventory obsolescence expressed as a percentage of inventory value. Inventory is obsolete when days of
supply value (DOS) is greater than the filter (90 days).
Structure(s):
Key Figure Remarks
Inventory Obsolete Days of
Supply - Value
The result is days of supply for the obsolete inventory or 0
Page 251
Inventory Obsolete Value The result is the value of the obsolete inventory or 0
Inventory Obsolete as a % of
Total Inventory
The inventory obsolescence expressed as a percentage of inventory value
0PLANT Plant
3.2.1.2.9 Query: 0IC_C01_Q0009 Inventory Aging
Purpose:
The percentage of total gross inventory (based on value) covered by expected demand within a specific time
bucket.
Structure(s):
Key Figure Remarks
Inventory Aging Time Bucket = 30 Days
0PLANT Plant
3.2.1.2.10 Query: 0IC_C01_Q0010 Stock VaIues
Purpose:
These key figures identify the value of the current inventory situation
Page 252
Structure(s):
Key Figure Remarks
Valuated Stock Value Stock value of a material held by a company which is part of the companys
current assets.
Average Valuated Stock
Value
The sum of the daily stock value for the time frame of the analysis divided
by the number of days.
0PLANT Plant
3.2.1.2.11 Query: 0IC_C01_Q0011 Stock Quantity
Purpose:
These key figures identify the quantity of the current inventory situation.
Structure(s):
Key Figure Remarks
Valuated Stock Value Stock quantity of a material held by a company which is part of the com-
panys current assets.
Average Valuated Stock
Value
The sum of the daily stock quantity for the time frame of the analysis di-
vided by the number of days.
Consignment Stock Quantity Stock quantity of a material held by a company which is part of the ven-
dors assets.
Average Consignment Stock
Quantity
The sum of the daily stock quantity for the time frame of the analysis di-
Total Stock Quantity Sum of the valuated stock quantity and consignment stock quantity.
Average Total Stock Quantity The sum of the daily stock quantity for the time frame of the analysis di-
Page 253
0PLANT Plant
3.2.1.2.12 Query: 0IC_C01_Q0012 MateriaI Consumption
Purpose:
These key figures provide data that illustrate the overall consumption patterns for a material.
Structure(s):
Key Figure Remarks
Total qnty of Mat.consumed Material taken from storage as a result of a reservation
Total val. of Mat. consumed Value of reserved material consumed
No. of total consumption Number of times a usage movement occurred
Unplanned Consumption
Quantity
Material taken from storage without a reservation
Value
Value of reserved material consumed
No. of unplanned consump-
tion
Number of times an unplanned usage movement occurred
Value (%)
Percentage (%) of total consumption that was unplanned
Unplanned Movements (%) Percentage (%) of total material movements that were unplanned
Page 254
0PLANT Plant
3.2.1.2.13 Query: 0IC_C01_Q0013 Process Performance Measure
Purpose:
These key figures provide data that can be utilized in identifying potential process flow bottlenecks
Structure(s):
Key Figure Remarks
No. of Valuated Stock Re-
ceipts
No. of Valuated Stock Receipts movements
No. of Valuated Stock Issues No. of Valuated Stock Issues movements
No. of Consignment Stock
Receipts
No. of Consignment Stock Receipts movements
No. of Consignment Stock
Issues
No. of Consignment Stock Issues movements
Number of Material Move-
ments
Number of Material Movements movements
No. of reversals/cancellations No. of reversals/cancellations movements
Total Receipts (%) % of total movements that are receipts
Total Issues (%) % of total movements that are issues
Total Reversals (%) % of total movements that are reversals
0PLANT Plant
Page 255
3.2.1.2.14 Query: 0IC_C01_Q0014 Consignment Stock Receipts vs Issues
Purpose:
This analysis provides a good comparison of the consignment material receipts vs issues. It can be used to identify
if vendor goods are being utilized or to analyze if vendor quantities are too high and potentially using excess space.
Structure(s):
Key Figure Remarks
Consignment Recpt Quantity Stock that is received into a location but still vendor material
Consignment Issue Quantity Stock that is issued from a location but still vendor material.
Quantity Variance Quality difference between receipts and issues
0PLANT Plant
3.2.1.2.15 Query: 0IC_C01_Q0015 VaIuated Stock Receipts vs Issues
Purpose:
This analysis provides comparison of the material receipts vs issues. It can be used to identify when the overall
inventory investment trend is too high or too low to meet stocks.
Structure(s):
Key Figure Remarks
Valuated Receipt Quantity Material received by a company which is part of the companys current
assets
Valuated Receipt Value Value of material received by a company which is part of the companys
current assets
Valuated Issue Quantity Material issued by a company which is part of the companys current as-
sets
Valuated Issue Value Value of material issued by a company which is part of the companys cur-
rent assets
Quantity Variance Difference between receipt quantity and issue quantity
Page 256
Value Variance Difference between receipt value and issue value
0PLANT Plant
3.2.1.3 InfoCube: 0IC_C02 Warehouse and Stocks
InfoSource(s):
2LIS_03_S195
2LIS_03_S197
Characteristics:
InfoObjects Description Navigation
Characteristics
avaiIabIe?
ExternaI Hierar-
chy avaiIabIe?
0REVERSEDOC Indicates that data should be can-
celled
No No
0STOR_LOC Storage location No No
0MATERIAL Material number Yes, Material
type, Division,
Material group,
Product Hierar-
chy
No
0PLANT Plant No No
0VTYPE Plant type for reporting No No
0FISCVARNT Fiscal Year Variants
Page 257
Key Figures:
InfoObjects Description Unit InfoObject Aggregation
0ISSVALSTCK Quantity of valuated stock issues 0BASE_UOM Additive
0ISSCNSSTCK Quantity of consignment stock that
has been issued
0BASE_UOM Additive
0NO_VAL_ISS Number of times valuated stock has
been issued
Additive
0NO_CNS_ISS Number of times consignment stock
has been issued
Additive
0NO_TOT_US Number of times the total usage has
been updated
Additive
0NO_MATMOVE Number of times material move-
ments
Additive
0NO_REVERSE Number of cancellations/reversals Additive
0NO_UNPL_US Number of times an unplanned us-
age has been recorded
Additive
0NO_VAL_REC Number of times valuated stock has
been received
Additive
0NO_CNS_REC Number of times consignment stock
has been received
Additive
0VALSTKQAVG Average valuated stock quantity 0BASE_UOM Additive
0TOT_US_QTY Total consumption quantity 0BASE_UOM Additive
0CNSSTKQAVG Average consignment stock quantity 0BASE_UOM Additive
0VALSTCKQTY Quantity of valuated stock 0BASE_UOM Additive
0CNSSTCKQTY Quantity of consignment stock 0BASE_UOM Additive
0UNP_US_QTY Unplanned usage quantity 0BASE_UOM Additive
0RECVALSTCK Valuated stock receipts quantity 0BASE_UOM Additive
0RECCNSSTCK Consignment stock receipts quantity 0BASE_UOM Additive
0TOTUSQTAVG Average total consumption quantity 0BASE_UOM Additive
Page 258
Unit:
InfoObjects Description Type
0BASE_UOM Base unit of measure Unit
In some queries (for example, ranges of coverage), a predefined SAP material type is used as a filter. Check
whether your company also uses this material type. If not change it, and save the query and the same workbook.
3.2.2 MM-PUR Purchasing
3.2.2.1 InfoCube: 0PUR_C01 Purchasing Data
InfoSource:
2LIS_02_S012 Purchasing
Characteristics:
InfoObjects Description Navigation
Characteristics
avaiIabIe?
ExternaI Hierar-
chy avaiIabIe?
0MATERIAL Material number Yes, Material
type
No
0MATL_GROUP Material group No No
0PLANT Plant No No
0PURCH_ORG Purchasing Organization No No
0REVERSEDOC Indicates that data must be can-
celled/reversed
No No
0VENDOR Vendor number No No
Page 259
0FISCVARNT Fiscal Year Variant
Key Figures:
InfoObjects Description Unit InfoObject Aggregation
0DEL_DT_VR1 Delivery date variance 1 Additive
0QTY_DEV_1 Delivery quantity variance 1 Additive
0ORDER_VAL Effective order value 0LOC_CURRCY Additive
0EFF_VAL_RE Effective order value returns 0LOC_CURRCY Additive
0GR_VAL_R_P GR- Returns value for post-
ing date
0LOC_CURRCY Additive
0GR_QTY_WDT Quantity of goods received in
base units of measure (for
calculating requested deliv-
ery time)
0BASE_UOM Additive
0GR_QTY_RET Quantity of goods received
returns
0BASE_UOM Additive
0GR_VAL_PD Value of goods received for
posting date
0IR_QTY_R_P IR: Quantity of returns for
posting date
0BASE_UOM Additive
Page 260
0IR_VAL_R_P IR: Value of returns for post-
ing date
0INV_RC_VAL Invoiced amount for posting
date
0IR_VAL_RET Invoiced amount returns 0LOC_CURRCY Additive
0INV_RC_QTY Invoice receipt quantity for
posting date
0BASE_UOM Additive
0IV_REC_QTY Invoice receipt quantity 0BASE_UOM Additive
0IR_QTY_RET Invoice receipt quantity re-
turns
0BASE_UOM Additive
0INVCD_AMNT Invoiced amount 0LOC_CURRCY Additive
0CONTR_ITEM Number of contract items Additive
0DELIVERIES Number of deliveries Additive
0DEL_SCHEDS Number of delivery sched-
ules
Additive
0PO_ITEMLNS Number of purchase order
item schedule lines
Additive
0PO_ITEMS Number of purchase order
items
Additive
0QUOT_ITEMS Number of quotation items Additive
0RFQ_ITEMS Number of RFQ items Additive
0SCH_AGR_IT Number of scheduling
agreement items
Additive
0PO_QTY_RET Purchase order quantity re-
turns
0BASE_UOM Additive
0PO_QTY Purchase order quantity 0BASE_UOM Additive
0GR_QTY Goods received quantity 0BASE_UOM Additive
0TAR_DL_QTY Required delivery quantity 0BASE_UOM Additive
0TOTDELTIME Total delivery time in days Additive
0GR_VAL Goods received value in local
currency
0WTDDELTIME Weighted total delivery time Additive
Unit:
Page 261
0BASE_UOM Basic unit of measure Unit
To calculate key figures (KPIs): on-time delivery performance in R/3-specific settings in the LIS: time buckets for
on-time delivery performance are required (transaction:MCFA)
In the query: Country comparison raw materials - goods receipt, a predefined SAP material type is used as a filter.
Check whether your company also uses this material type. If not change it, and save the query and the same
workbook.
3.2.2.1.1 Query: 0PUR_C01_Q0001 Average DeIivery Time -Vendor
Purpose:
The average time for a supplier to stage the required materials.
Structure(s):
Key Figure Remarks
Average Delivery Time The total delivery time (time difference between ordering and invoicing),
divided by the number of deliveries.
Average Weighted Delivery
Time
The total delivery time multiplied with the order quantity, divided by the
number of deliveries.
0PLANT Plant
0VENDOR Vendor
3.2.2.1.2 Query: 0PUR_C01_Q0002 Service LeveI Vendor
Purpose:
The percentage of orders that were completed either before or on the day originally requested.
To calculate the key figure (KPI): ): on-time delivery performance in R/3-specific settings in the LIS: time buckets for
on-time delivery performance are required (transaction:MCFA)
Page 262
Structure(s):
Key Figure Remarks
Service Level The number of orders that were delivered on time, divided by the total
number.
0VENDOR Vendor
Remarks:
SAP R/3: LIS Purchasing S012
Customizing R/3:
Transaction: MCFA
Change the time buckets for the on-time delivery performance
SeNo. Del.det.var
1 - Number
2 0
3 + Number
4 + Number
There must be a 0 in the second position. If there is a 0 in the third position, then the user must add the delivery
date variance 3 to the denominator in the formula.
3.2.2.1.3 Query: 0PUR_C01_Q0003 - FuIfiIment rate - DeIiveries
Purpose:
The percentage of orders that have been completed with the correct amount.
Structure(s):
Key Figures Remarks
Number of Deliveries The number of deliveries
Order Quantity The quantity ordered
Fulfilment Rate - Deliveries The number of deliveries (of the supplier), divided by the quantity ordered
Page 263
0PLANT Plant
0VENDOR Vendor
3.2.2.1.4 Query: 0PUR_C01_Q0005 Average DeIivery Time - MateriaI
Purpose:
Average time for materials procurement
Structure(s):
Key Figure Remarks
Average Delivery Time The total delivery time (time difference between ordering and invoicing),
divided by the number of deliveries.
Average Weighted Delivery
Time
The total delivery time multiplied with the order quantity, divided by the
number of deliveries.
0VENDOR Vendor
0PLANT Plant
3.2.2.1.5 Query: 0PUR_C01_Q0006 Purchasing vaIues according to purchasing org.
Remarks:
This query will not be delivered any more, but it has been rebuild in a more sophisitcated cersion in query
0PUR_C01_Q0013.
3.2.2.1.6 Query: 0PUR_C01_Q0008 DeIivery Quantity Variance
Purpose:
With this query, you can discover where the goods receipts (quantities) occur in a predefined delivery quantity vari-
ance.
Page 264
Structure(s):
Key Figure Remarks Info Objects / CaIcuIations
% Delivery Quantity Variance-
range 1
Percentage of all deviations
that fall within range 1
0QTY_DEV_1 /
0SUMQTYVARIANCE
range 2
0QTY_DEV_2/
0SUMQTYVARIANCE
range 3
0QTY_DEV_3/
0SUMQTYVARIANCE
range 4
0QTY_DEV_4/
0SUMQTYVARIANCE
range 5
0QTY_DEV_5/
0SUMQTYVARIANCE
Delivery Quantity Variance- range
1
Number of Delivery Quanti-
ties that deviated from Pur-
chase Order Qty. within in-
terval range 1
0QTY_DEV_1
2
terval range 2
0QTY_DEV_2
3
terval range 3
0QTY_DEV_3
4
terval range 4
0QTY_DEV_4
5
terval range 5
0QTY_DEV_5
0PLANT Plant
Page 265
3.2.2.1.7 Query: 0PUR_C01_Q0009 DeIivery Date Variance
Purpose:
To identify where in a predefined range do deliveries occur.
Structure(s):
Key Figure Remarks Info Objects / CaIcuIa-
tions
% Delivery Date Variance-
range 1
Percentage of all deviations that fall
within range 1
0DEL_DT_VR1/
0SUMDELIVERYVAR
range 2
within range 2
0DEL_DT_VR2/
0SUMDELIVERYVAR
range 3
within range 3
0DEL_DT_VR3/
0SUMDELIVERYVAR
range 4
within range 4
0DEL_DT_VR4/
0SUMDELIVERYVAR
range 5
within range 5
0DEL_DT_VR5/
0SUMDELIVERYVAR
Delivery Date Variance- range
1
Number of Deliveries within interval
range 1 that deviated from Purchase
Order due date
0DEL_DT_VR1
2
Order due date
0DEL_DT_VR2
3
Order due date
0DEL_DT_VR3
4
Order due date
0DEL_DT_VR4
5
Order due date
0DEL_DT_VR5
0PLANT Plant
Page 266
3.2.2.1.8 Query: 0PUR_C01_Q0011 Order Quantities
Purpose:
With this query, you can recognize discrepancies between ordered values and the values placed or contained in
the invoice.
Structure(s):
Key Figure Remarks
Order Quantities Quantity of the materials ordered in orders and deliveries
Invoice Receipt Quantity for
Posting Date
Quantity between invoicing and receipt of invoice
Quantity of Goods Received Quantity of goods that, according to the order, have come in
Percentage Invoice Receipt
Quantity to the Order Quantity
Percentage of the total order quantity, that was put in the invoice
Difference between Order Quan-
tity and Quantity of Goods Re-
ceived
Total order quantity of materials that did not come in
Percentage of Quantity of Goods
Received to Order Quantity
Percentage of the total order quantity that did come in
0VENDOR Vendor Number
0PLANT Plant
3.2.2.1.9 Query: 0PUR_C01_Q0012 Order Activities
Purpose:
With this query, you can differentiate between different purchasing activities for a given characteristic or for an or-
ganization.
Structure(s):
Key Figure Remarks
No. Order Items Number of order items
No. RFQ Items Number of order items
No. Quotation Items Number of quotation items
Page 267
No. Contract Items Number of contract items
No. Scheduling Agreement
Items
Number of scheduling agreement items
Total no. of items to deliver
Total number of items to deliver
No. deliveries
Total number of deliveries
Percentage of deliveries to
total no. of items
Percentage of deliveries to total number of items
0VENDOR Vendor Number
0PLANT Plant
3.2.2.1.10 Query: 0PUR_C01_Q0013 Vendor Comparison re: Purchasing VaIues
Purpose:
With this query, you can recognize discrepancies between ordered values and the values placed or contained in
the invoice.
Structure(s):
Key Figure Remarks
Order Quantity Quantity of the ordered materials in orders or scheduling agreements
Effective Order Value Value of the order, inclusive of discounts, surcharges, delivery costs and
cash discounts
Invoiced Amount Value is put in the invoice by the supplier
Value of Goods Received in
Local Currency
Value of the quantity, that, according to the order, has come in
Order Value, put in the In-
voice, as a Percentage
Percentage of the total order value that was put in the invoice
Open Order Value in the
Invoice
Total order value, that was not put in the invoice
Order Value Contained as a
Percentage
Percentage of the total order value, that has come in
Page 268
0PLANT Plant
0PURCH_ORG Purchasing Organization
0MATERIAL Material
0VENDOR Vendor
0MATL_GROUP Material Group
3.2.2.1.11 Query: 0PUR_C01_Q0014 Country Comparison Raw MateriaIs - Goods Re-
ceipt
Purpose:
Number of raw materials (goods purchased) by region
Structure(s):
Key Figure Remarks
Value of Goods Received in
Local Currency
Quantity of the material ordered in purchase orders or scheduling agree-
ments
0PLANT Plant
Remarks:
A predefined SAP material type is used as a filter here. Please check whether your company also uses this mate-
rial type. If not change it, and save the query and the same workbook.
3.2.2.2 InfoCube: 0PUR_C02 Vendor EvaIuation
Content:
This InfoCube contains all the uploaded data from the source system(s) for evaluating the vendor, with regard to
on-time delivery performance, quality audit, quantity reliability, shipping notification, shipping instructions, quality of
service, on-time delivery performance of the service, and the variance of the shipping notification for its deliveries.
InfoSource:
2LIS_02_S013
Page 269
Characteristics:
Attribute avaiI-
abIe?
ExternaI Hierarchy
avaiIabIe?
0MATERIAL Material number No No
0PURCH_ORG Purchasing organization No No
0REVERSEDOC Indicates that the data should be
cancelled/reversed
No No
0PLANT Plant No No
Key Figures:
0ONT_DEL_1 Points score 1 for on-time delivery
performance
Not additive
0ONT_DEL_2 Points score 2 for on-time delivery
performance
Not additive
0QA_SCORE_1 Points score 1 for quality audit Not additive
0QA_SCORE_2 Points score 2 for quality audit Not additive
0QTY_REL_1 Points score 1 for quantity reliability Not additive
0QTY_REL_2 Points score 2 for quantity reliability Not additive
0SHIP_NOT_1 Points score 1 for shipping notifica-
tion
Not additive
0SHIP_NOT_2 Points score 2 for shipping notifica-
tion
Not additive
Page 270
0SHP_INS_1 Points score 1 for shipping instruc-
tions
Not additive
0SHP_INS_2 Points score 2 for shipping instruc-
tions
Not additive
0SRV_QUAL_1 Points score 1 quality service Not additive
0SRV_QUAL_2 Points score 2 quality service Not additive
0SRV_TIME1 Points score 1 for scheduled time
service
Not additive
0SRV_TIME2 Points score 2 for scheduled time
service
Not additive
0VAR_SHP_1 Points score 1 variance shipping
notification
Not additive
0VAR_SHP_2 Points score 2 variance shipping
notification
Not additive
Units:
If point scores are aggregated, then the average is formed using the vendors as a basis. The exception aggrega-
tion does not, therefore, equal zero on the average.
3.2.2.2.1 Query: 0PUR_C02_Q0022 Vendor Comparison with the Vendor EvaIuation
Purpose:
The evaluation analysis displays the points scores from the vendor evaluation for the purchase. With the aid of this
analysis, you can, for example, follow whether a certain vendor delivers material on-time and in the correct quan-
tity.
Structure(s):
Key Figure Remarks
0QTY_REL_1 Point score 1 for quantity reliability in the last month
0QTY_REL_2 Point score 2 for quantity reliability cumulated from all periods
0ONT_DEL_1 Point score 1 for on-time delivery performance in the last month
0ONT_DEL_2 Point score 2 for on-time delivery performance cumulated from all periods
0SHP_INS_1 Point score 1 for the shipping instructions in the last month
0SHP_INS_2 Point score 2 for the shipping instructions cumulated from all periods
Page 271
0SRV_QUAL_1 Point score 1 quality service for the last month
0SRV_QUAL_2 Point score 2 quality service cumulated from all periods
0SRV_TIME1 Point score 1 for schedule time service for the last month
0SRV_TIME2 Point score 2 for schedule time service cumulated from all periods
0QA_SCORE_1 Point score 1 for quality audit in the last month
0QA_SCORE_2 Point score 2 for quality audit cumulated from all periods
0SHIP_NOT_1 Point score 1 Shipping notification for the last month
0SHIP_NOT_2 Point score 2 Shipping notification cumulated from all periods
0VAR_SHP_1 Point score 1 Variance shipping notification for the last month
0VAR_SHP_2 Point score 2 Variance shipping notification cumulated from all periods
0PLANT Plant
0PURCH_ORG Purchasing organization
0MATERIAL Material
0VENDOR Vendor
3.2.2.3 InfoCube: 0PUR_C03 Subsequent SettIement - EvaIuation
Content:
This InfoCube contains all the uploaded data from the source system(s), that are necessary for the settlement of
vendor arrangements (volume rebate processing).
InfoSource:
2LIS_02_S015
Characteristics:
Attribute avaiI-
abIe?
ExternaI Hierarchy
avaiIabIe?
0ACT_GI_DTE Actual goods issue date No No
0AGREEMENT Agreement (group of conditions) No No
0CND_GRANT Condition granter No No
Page 272
0CONDRECNO Condition record number No No
0MATL_GROUP Material group No No
0PROC_VEND Vendor No No
0PUR_GROUP Purchasing group No No
0REVERSEDOC Indicator No No
0PLANT Plant No No
Key Figures:
0CONDRECINC Income from the settlement of the
condition record
0ARR_CURR Additive
0DISS_PCI Dissolved provisioned condition
income
0ARR_CURR Additive
0POINTS Number of points (subsequent set-
tlement)
0POINTSUNIT Additive
0PROV_INC Provisioned condition income 0ARR_CURR Additive
0REBINC_FIS Income final settlement 0ARR_CURR Additive
0VBU_VOLUM Volume (subsequent settlement) 0COND_UNIT Additive
0VBV_A_CURR Vendor business volume (subse-
quent settlement)
0ARR_CURR Additive
0VBV_C_CURR Vendor business volume value in
condition currency relevant to set-
tlement
0COND_CURR Additive
Page 273
0VB_GROSSWT Vendor business volume gross
weight (subsequent settlement)
0UNIT_OF_WT Additive
0VB_NETWGT Vendor business volume net weight
(subsequent settlement)
0UNIT_OF_WT Additive
0VB_QTY Vendor business volume quantity
(subsequent settlement)
0COND_UNIT Additive
Units:
0UNIT_OF_WT Units of weight Units of measure
0ARR_CURR Arrangement currency Currency
0POINTSUNIT Points unit Units of measure
0COND_UNIT Condition unit of measure in the
document
Units of measure
0COND_CURR Condition unit (currency) Currency
3.2.2.4 InfoCube: 0PUR_C04 Purchasing Groups
Content:
This InfoCube contains all the uploaded data from the source system(s) for evaluating the purchaser on the basis
of his/her purchasing activities. To these belong the number of contracts and their items, the number of requests
for quotations and their items, the number of offers and their items, the number of scheduling agreements and their
items, the number of delivery schedules, the number of orders and their items, the number of purchase item order
schedule lines, as well as the effective order value and the invoiced amount.
InfoSource:
2LIS_02_S011
Characteristics:
Attribute avaiI-
abIe?
ExternaI Hierarchy
avaiIabIe?
0PUR_GROUP Purchasing group No No
Page 274
Key Figures:
0CONTRACTS Number of contracts Additive
0CONTR_ITEM Number of contract items Additive
0DELIVERIES Number of deliveries Additive
0DEL_SCHEDS Number of delivery schedules Additive
0INVCD_AMNT Invoiced amount 0LOC_CURRCY Additive
0NO_PUR_ORD Number of purchase orders Additive
0NO_REQ_QUT Number of request quotations Additive
0ORDER_VAL Effective order value 0LOC_CURRCY Additive
0PO_ITEMLNS Number of purchase order item
schedule lines
Additive
0PO_ITEMS Number of purchase order items Additive
0QUOT_ITEMS Number of quotation items Additive
0RFQ_ITEMS Number of request quotation items Additive
0SCHED_AGR Number of scheduled agreements Additive
0SCH_AGR_IT Number of scheduled agreement
items
Additive
Units:
Page 275
3.2.2.4.1 Query: 0MMPUR_C04_Q01 Purchasing Group AnaIysis
Purpose:
The purchasing group analysis shows the distribution of purchasing activities per purchasing group. Using this, the
following questions, for example, can be answered: Which order value did a purchasing group process? How many
order were given to a vendor, and what order value did they come to?
Structure(s):
Key Figure Remarks
0NO_REQ_QUT Number of request quotations
0RFQ_ITEMS Number of request quotation items
0QUOT_ITEMS Number of quotation items
0PO_ITEMLNS Number of purchase order item schedule lines
0PO_ITEMS Number of purchase order items
0NO_PUR_ORD Number of purchase orders
0CONTRACTS Number of contracts
0CONTR_ITEM Number of contract items
0SCHED_AGR Number of scheduled agreements
0DEL_SCHEDS Number of delivery schedules
0SCH_AGR_IT Number of scheduled agreement items
0DELIVERIES Number of deliveries
0ORDER_VAL Effective order value
0INVCD_AMNT Invoiced amount
0PURCH_ORG Purchasing Organization
0VENDOR Vendor
0PUR_GROUP Purchasing Group
Page 276
3.3 QM QuaIity Management
3.3.1 QuaIity Inspection
3.3.1.1 InfoCube: 0QM_C01 Inspection Iot and usage decision
Content:
This infoCube contains all of the transaction data uploaded from the source system(s) for inspection lots and usage
decisions.
InfoSource(s):
2LIS_05_S290: Transaction data for inspection lot / usage decision
Characteristics:
ExternaI hierarchy
avaiIabIe?
0INSP_LOT__0CUSTOMER Customer Yes No
0INSP_LOT__0INSPTYPE Inspection type Yes No
0INSP_LOT__0MATERIAL Material Yes No
0INSP_LOT__0PLANT Plant Yes No
0INSP_LOT__0PURCH_OR Purchasing organization Yes No
0INSP_LOT__0SALESORG Sales organization Yes No
0INSP_LOT__0SOLD_TO Sold-to party Yes No
0INSP_LOT__0STOR_LOC Storage location Yes No
0INSP_LOT__0VENDOR Vendor Yes No
0CALQUARTER Calendar year / quarter
Page 277
Key figures:
behavior
0ILOTS Number of inspection lots Sum
0ILOTS_ACC Number of accepted inspection lots Sum
0ILOTS_REJ Number of rejected inspection lots Sum
0ILOTS_SKIP Number of skipped lots Sum
0ILOT_QTY Actual lot quantity 0ILOT_UOM Sum
0DEF_QTY Defective quantity in sample 0SAMPLE_UOM Sum
0REJCT_QTY Rejected quantity 0ILOT_UOM Sum
0SKIP_QTY Skipped quantity 0ILOT_UOM Sum
0INSP_QTY Quantity actually inspected 0SAMPLE_UOM Sum
0ACCPT_QTY Accepted quantity 0ILOT_UOM Sum
0FRAC_NONCF Fraction of nonconforming units in
inspection lot
Sum
0QUAL_SCORE Quality score Sum
Units:
0ILOT_UOM Base unit of measure for the inspec-
tion lot quantity
0SAMPLE_UOM Base unit of measure for the sample
unit
To evaluate the cube, you need master data for the inspection lot/usage decision.
The individual lot sizes are not considered in the key figures "fraction of nonconforming units in inspection lot" and
"quality score."
3.3.1.1.1 Query: 0QM_C01/0QM_C01_Q001 MateriaI anaIysis - Inspection Iots
Purpose:
This query provides an overview of the number of inspections and lot quantities, as well as the confirmed quality.
Page 278
Structure(s):
Key figure Comments
Actual lot quantity
Rejected quantity
Number of lots
Number of rejected lots
Share of scrap in lot Total share of scrap. Key figure is hidden.
Share not OK [ppm] Total share of scrap / number of lots
Quality score Total of quality scores. Key figure is hidden.
Quality score Total of quality scores / number of lots
Characteristics:
Plant Plant for inspection lot
Inspection type Inspection type
Calendar year / month Period for lot creation
Material Inspected material
3.3.1.1.2 Query: 0QM_C01/0QM_C01_Q003 Vendor anaIysis - Inspection Iots
Purpose:
This query provides an overview of the number of inspections and the quality scores for the various vendors.
Structure(s):
Key figure Comments
Quality score Total of quality scores. Key figure is hidden.
Quality score Total of quality scores / number of lots
Share of scrap in lot Total share of scrap. Key figure is hidden.
Share not OK [ppm] Total share of scrap / number of lots
Number of lots
Number of rejected lots
Page 279
Characteristics:
Material Geprftes Material
Plant Werk des Prfloses
Purchasing organization Purchasing organization for inspection lot
Calendar year / month Period for lot creation
3.3.2 Notifications
3.3.2.1 InfoCube: 0QM_C02 Notifications
Content:
This infoCube contains all of the transaction data uploaded from the source system(s) for notifications.
InfoSource(s):
2LIS_05_S291: Transaction data for notification header
Characteristics:
ExternaI hierarchy
avaiIabIe?
0NOTIFICATN__0ASSEMB Assembly Yes No
0NOTIFICATN__0BATCH Batch Yes No
0NOTIFICATN__0CUSTOM Customer Yes No
0NOTIFICATN__0DISTR_ Distribution channel Yes No
0NOTIFICATN__0DIVISI Division Yes No
0NOTIFICATN__0EQUIPM Equipment number Yes No
0NOTIFICATN__0FUNCT_ Functional location Yes No
0NOTIFICATN__0MAINTL Location Yes No
0NOTIFICATN__0MAINTP Maintenance plant Yes No
0NOTIFICATN__0MAINTR Room Yes No
0NOTIFICATN__0MATERI Material Yes No
0NOTIFICATN__0NFCAT_ Coding Yes No
0NOTIFICATN__0NFCAT_ Code group Yes No
Page 280
0NOTIFICATN__0NFCAT_ Catalog type Yes No
0NOTIFICATN__0NOT_TY Notification type Yes No
0NOTIFICATN__0PLANPL Maintenance planning plant Yes No
0NOTIFICATN__0PLANT Plant Yes No
0NOTIFICATN__0PLANTS Plant section Yes No
0NOTIFICATN__0PMPLAN Maintenance planner group Yes No
0NOTIFICATN__0PRIORI Priority Yes No
0NOTIFICATN__0SALESO Sales organization Yes No
0NOTIFICATN__0VENDOR Vendor Yes No
Key figures:
behavior
0COMPL_QTY Complaint quantity 0ILOT_UOM Sum
0DEFQTY_EXT Defective quantity (external) 0ILOT_UOM Sum
0DEFQTY_INT Defective quantity (internal) 0ILOT_UOM Sum
0NOTIF_TOT Number of notifications Sum
0NTF_INTIME Number of notifications completed
within schedule
Sum
0RETURN_QTY Returned quantity 0ILOT_UOM Sum
0TASK_OUTST Number of tasks with status "out-
standing" or "released"
Sum
0TASK_SUCC Number of tasks with status "suc-
cessful"
Sum
0TASK_TOT Number of tasks Sum
Page 281
0NOTIFOUTST Number of tasks with status "out-
standing"
Sum
0NOTIF_PROC Notification processing time Sum
Units:
0BASE_UOM Base unit of measure
To evaluate the cube, you need master data for notifications.
The following characteristics are not available for quality notifications:
Equipment number
Functional location
Location
Maintenance plant
Room
Maintenance planning plant
Plant section
Maintenance planner group
This cube can contain data from the Quality Management and Plant Maintenance components. Be sure to consider
this when you define queries for this cube.
These queries should therefore contain a filter for the notification type, so you can analyze the key figures accord-
ing to different evaluation requirements (for example, the evaluation of technical objects or evaluations based on
customer or vendor requirements).
3.3.2.1.1 Query: 0QM_C02/0QM_C02_Q001 AnaIysis of notifications - QuaIity Man-
agement
Purpose:
This query provides an overview of the number of notifications and the affected objects.
Structure(s):
Key figure Comments
Notifications: total Number of existing notifications
Outstanding Number of outstanding notifications
In time Number of notifications completed on schedule
Page 282
Processing days: total Total of processing times
Average Total of processing times / number of notifications
Tasks: total Number of recorded tasks
Successful Number of successful tasks
Outstanding Number of outstanding tasks
Defective quantity (internal) Defective quantity of notifications (internally caused defects)
Defective quantity (external) Defective quantity of notifications (externally caused defects)
Characteristics:
Calendar year / material Period for notification date
Material Material specified in notification
Priority Priority of notification
Customer Customer specified in notification
Vendor Vendor specified in notification
Batch Batch number specified in notification
3.3.2.2 InfoCube: 0QM_C03 Notification items
Content:
This InfoCube contains all of the transaction data uploaded from the source system(s) for notification items.
InfoSource(s):
2LIS_05_S292: Transaction data for notification items
Characteristics:
ExternaI hierarchy
avaiIabIe?
Notification
Page 283
Defect type
0CATCODE_FE Problem No No
0CATGRP_FE Code group - problems No No
0CATTYPE_FE Catalog type - problems No No
Defect Iocation
0CATCODE_OT Object part No No
0CATGRP_OT Code group - object part No No
0CATTYPE_OT Catalog type - object part No No
Defect cIass
0DEFECTCLAS Defect class No No
AssembIy
0ASSEMBLY Item assembly No No
Page 284
Key figures:
behavior
0PROBL_FREQ Problem frequency
0DEFECT_VAL Sum of defect valuations
Units:
The following characteristics are not available for quality notifications:
Equipment number
Functional location
Location
Maintenance plant
Room
Plant section
Page 285
3.3.2.2.1 Query: 0QM_C03/0QM_C03_Q002 AnaIysis of nonconformities - Notifica-
tions
Purpose:
This query provides an overview and the frequency of the nonconformities (defect codes) recorded in the notifica-
tions and inspection lots.
Structure(s):
Key figure Comments
Problem frequency Confirmed number of nonconformities (including multiple occurrences)
Characteristics:
Problem Code for defect type
Object part Code for defect location
Calender year / week Period of notification date
Vendor Vendor specified in notification
Material Material specified in notification
Fehlerklasse Bedeutung des Fehlers
Page 286
3.4 PM PIant Maintenance and Service
3.4.1 Notifications
3.4.1.1 InfoCube: 0QM_C02 Notifications
Content:
This infoCube contains all of the transaction data uploaded from the source system(s) for notifications.
InfoSource(s):
Characteristics:
ExternaI hierarchy
avaiIabIe?
Page 287
Key figures:
behavior
0COMPL_QTY Complaint quantity 0ILOT_UOM Sum
0DEFQTY_EXT Defective quantity (external) 0ILOT_UOM Sum
0DEFQTY_INT Defective quantity (internal) 0ILOT_UOM Sum
0NOTIF_TOT Number of notifications Sum
0NTF_INTIME Number of notifications completed
within schedule
Sum
0RETURN_QTY Returned quantity 0ILOT_UOM Sum
0TASK_OUTST Number of tasks with status "out-
standing" or "released"
Sum
0TASK_SUCC Number of tasks with status "suc-
cessful"
Sum
0TASK_TOT Number of tasks Sum
0NOTIFOUTST Number of tasks with status "out-
standing"
Sum
0NOTIF_PROC Notification processing time Sum
Page 288
Units:
0BASE_UOM Base unit of measure
The following characteristics are not available for service and maintenance notifications:
Complaint quantity
Defective quantity (external)
Defective quantity (internal)
Returned quantity
3.4.1.1.1 Query: 0QM_C02/0QM_C02_Q002 AnaIysis of notifications - TechnicaI Ob-
jects
Purpose:
This query provides an overview of the number of notifications and the affected objects.
Structure(s):
Key figure Comments
Notifications: total Number of existing notifications
Outstanding Number of outstanding notifications
In time Number of notifications completed on schedule
Processing days: total Total of processing times
Average Total of processing times / number of notifications
Tasks: total Number of recorded tasks
Successful Number of successful tasks
Outstanding Number of outstanding tasks
Page 289
Characteristics:
Calendar year / month Period for notification date
Priority Priority of notification
Functional location Number or description of affected functional location
Equipment number Number or description of affected equipment
Maintenance plant
Location
Material Material der Meldung
3.4.1.2 InfoCube: 0QM_C03 Notification items
Content:
This infoCube contains all of the transaction data uploaded from the source system(s) for notification items.
InfoSource:
Characteristics:
ExternaI hierarchy
avaiIabIe?
Notification
Page 290
Defect type
0CATCODE_FE Problem No No
0CATGRP_FE Code group - problems No No
0CATTYPE_FE Catalog type - problems No No
Defect Iocation
0CATCODE_OT Object part No No
0CATGRP_OT Code group - object part No No
0CATTYPE_OT Catalog type - object part No No
Defect cIass
0DEFECTCLAS Defect class No No
AssembIy
0ASSEMBLY Item assembly No No
Page 291
Key figures:
behavior
0PROBL_FREQ Problem frequency
0DEFECT_VAL Sum of defect valuations
Units:
The following characteristics are not available for service and maintenance notifications:
Complaint quantity
Defective quantity (external)
Defective quantity (internal)
Returned quantity
3.4.1.2.1 Query: 0QM_C03/0QM_C03_Q001 AnaIysis of damage codes - Notifications
Purpose:
This query provides an overview and the frequencies of the damage codes recorded in notifications.
Page 292
Structure(s):
Key figure Comments
Problem frequency Confirmed damage codes (including multiple occurrences)
Characteristics:
Problem Damage code
Object part Code for affected object part
Calendar year / week Period for notification date
Plant section
Functional location Number or description of affected functional location
Equipment number Number or description of affected equipment
Item assembly
Maintenance plant
Location
3.5 Production PIanning and ControII
3.5.1 Process and Production Orders
In the following text, production orders are always talked of. The same, however, also always applies for process
orders: Production and process orders are merely differentiated in BW by order category in the master data, and
are otherwise always treated identically.
3.5.1.1 InfoCube: 0PP_C01 PIan/ActuaI Comparison Order/ Mate-
riaI View
Content:
This InfoCube contains all the transaction data of the production process related to the order header and item, that
is uploaded by the source system(s). The process is formed from the conversion of the plan order into a production
order using release, start and reply, up to the delivery. The data is mapped to the actual release date to enable a
plan/actual comparison. In addition, plan and actual data is only stored if actual data exists as otherwise the most
frequent comparisons plan/actual and target/actual will not produce good results.
Page 293
InfoSource:
2LIS_04_S280: Order header and item, BW
Characteristics:
ExternaI hierarchy
avaiIabIe?
0DOC_NUMBER Sales document No No
0ORDERITEM Number of the order item No No
0PLANT Plant No No
0PRODORDER Order number (Production order) Yes No
0P_PLANT Planning plant No No
0MAT_PLANT Material number with plant Yes No
0CALQUARTER Calendar Year / Quarter
Key figures:
behavior
0ACTDELDATK Actual delivery / finish date Additive
0ACTEXECTM Actual execution time 0WM_UOT Additive
0ACTFINISHK Returned order completion Additive
0ACTLEADTM Actual lead time 0WM_UOT Additive
0ACTRELDATK Actual release date Additive
0ACTSTARTDK Actual start date Additive
0ACTUALSRAP Actual scrap 0BASE_UOM Additive
0BASICSTARK Order start date Additive
0CAPREQMTS Target capacity requirement sum 0CAPA_UNIT Additive
Page 294
0FINISHDATK Order finish date Additive
0GR_QTY Quant. of goods received 0BASE_UOM Additive
0ITEMQTY Quant. of items 0BASE_UOM Additive
0ITEMSCRAP Scrap quantity 0BASE_UOM Additive
0PA_DELDEV Delivery date variation plan / actual 0WM_UOT Additive
0PA_DELDEVN Delivery date variation plan / actual
negative
0WM_UOT Additive
0PA_DELDEVP Delivery date variation plan / actual
positive
0WM_UOT Additive
0PA_RELDEV Release delivery date variation plan
/ actual
0WM_UOT Additive
0PA_RELDEVN Release delivery date variation plan
/ actual negative
0WM_UOT Additive
0PA_RELDEVP Release delivery date variation plan
/ actual positive
0WM_UOT Additive
0PA_STARDVN Start schedule variation plan / actual
negative
0WM_UOT Additive
0PA_STARDVP Start schedule variation plan / actual
positive
0WM_UOT Additive
0PA_STARTDV Start schedule variation plan / actual 0WM_UOT Additive
0PLANLEADTM Plan lead time 0WM_UOT Additive
0PLANORDQTY Order quantity 0BASE_UOM Additive
0PLDDELDATK Del. date plan Additive
0PLDOPENDTK Plan order opening date Additive
0PLDRELDATK Plan release date Additive
0PLDSTARTDK Plan order start date Additive
0PT_DELDEV Delivery date variation plan / target 0WM_UOT Additive
0PT_DELDEVN Delivery date variation plan / target
negative
0WM_UOT Additive
0PT_RELDEVP Release date variation plan / target
positive
0WM_UOT Additive
0PT_STARDVN Start date variation plan / target
negative
0WM_UOT Additive
0PT_STARDVP Start date variation plan / target
positive
0WM_UOT Additive
Page 295
0PT_STARTDV Start date variation plan / target 0WM_UOT Additive
0SCHEDFINDK scheduled finish Additive
0SCHEDRELDK scheduled release date Additive
0SCHEDSTARK scheduled start Additive
0SCRAPQTY Scrap quantity 0BASE_UOM Additive
0TA_DELDEV scheduled delivery date target / ac-
tual
0WM_UOT Additive
0TA_DELDEVN scheduled delivery date target / ac-
tual negative
0WM_UOT Additive
0TA_DELDEVP scheduled delivery date target / ac-
tual positive
0WM_UOT Additive
0TA_RELDEV Release date variation target / actual 0WM_UOT Additive
0TA_RELDEVN Release date variation target / actual
negative
0WM_UOT Additive
0TA_RELDEVP Release date variation target / actual
positive
0WM_UOT Additive
0TA_STARDVN Start date variation target / actual
negative
0WM_UOT Additive
0TA_STARDVP Start date variation target / actual
positive
0WM_UOT Additive
0TA_STARTDV Start date variation target / actual 0WM_UOT Additive
0TGTEXECTM Target execution time 0WM_UOT Additive
0TGTLEADTM Target lead time 0WM_UOT Additive
0NO_PRODORD No. of prod. orders Additive
Unit:
0WM_UOT WM time unit Units of measure
0BASE_UOM base unit of measure Units of measure
0CAPA_UNIT Capacity unit requirement Units of measure
The date key figures (for example, 0ACTSTARTDK actual start date) only make sense on the lowest level. They
are additive so that changes can be correctly updated.
Recommendation: Create an aggregate using the characteristics plant, material and month. The performance will
be significantly improved.
Page 296
0CALDAY Calendar day is filled in the update rules using the actual release date. The other time characteristics
are determined using an automatic time conversion.
Queries
All durations are displayed as average per order all quantities as sums.
3.5.1.1.1 Query: 0PP_C01_Q001 ScheduIe and Scrap Deviation Order View
Purpose:
This query compares target and actual schedule deviations of the order release, production start and delivery to
lead time deviation making it possible to determine which schedule deviation is most responsible for the lead time
deviation.
Structure(s):
Key Figure Remarks
T/A deviation in release date Target/actual deviation in scheduled release date
T/A deviation in start date Target/actual deviation in scheduled start date
T/A deviation in delivery date Target/actual deviation in scheduled delivery date
Target/actual lead time de-
viation
Target lead time
Actual lead time
0PLANT Plant, Variable &0S_PLANT&, First Line
0PRODORDER__0MRP_CO
NTRL
MRP Controller, Variable &0S_PDISP&
0MATERIAL Material Number, Variable &0S_MAT&
0PRODORDER Order Number (Production order)
0CALMONTH Calendar Year / Month, Variable &0I_CALMO&
Page 297
3.5.1.1.2 Query: 0PP_C01_Q002 ScheduIe/Scrap Deviation Order View
Purpose:
This query compares target and actual schedule deviations of order release, production start and delivery to the
scrap deviation making it possible to determine which schedule deviation is most responsible for the scrap devia-
tion.
Structure(s):
Key Figure Remarks
T/A deviation in release date Target/actual deviation in scheduled release date
T/A deviation in start date Target/actual deviation in scheduled start date
T/A deviation in delivery date Target/actual deviation in scheduled delivery date
Scrap deviation Scrap deviation
Scrap quantity Scrap item quantity
Actual scrap Actual scrap
See query 0PP_C01_Q001
3.5.1.1.3 Query: 0PP_C01_Q003 TotaI ScheduIe Deviation Order View
Purpose:
This query compares schedule deviations of order release, production start and delivery in order to determine how
well production was planned.
Structure(s):
Key Figure Remarks
Total release date deviation Maximum time between planned/target/actual deviation in release date
Total start date deviation Maximum time between planned/target/actual deviation in start date
Total delivery date deviation Maximum time between planned/target/actual deviation in delivery date
3.5.1.1.4 Query: 0PP_C01_Q004 DetaiIed Order ReIease Deviations
Purpose:
This query provides a detailed view of order release deviations.
Page 298
Structure(s):
Key Figure Remarks
Neg. P/T release date dev. Negative planned/target release date deviation
Pos. P/T release date dev. Positive planned/target release date deviation
Neg. T/A release date dev. Negative target/actual release date deviation
Pos. T/A release date dev. Positive target/actual release date deviation
Neg. P/A release date Negative planned/actual release date deviation
Pos. P/A release date Positive planned/actual release date deviation
3.5.1.1.5 Query: 0PP_C01_Q005 DetaiIed Order Start Date Deviations
Purpose:
This query provides a detailed view of order start date deviations.
Structure(s):
Key Figure Remarks
Neg. P/T start date dev. Negative planned/target start date deviation
Pos. P/T start date dev. Positive planned/target start date deviation
Neg. T/A start date dev. Negative target/actual start date deviation
Pos. T/A start date dev. Positive target/actual start date deviation
Neg. P/A start date Negative planned/actual start date deviation
Pos. P/A start date Positive planned/actual start date deviation
Page 299
3.5.1.1.6 Query: 0PP_C01_Q006 DetaiIed Order DeIivery Date Deviations
Purpose:
This query provides a detailed view of order delivery date deviations.
Structure(s):
Key Figure Remarks
Neg. P/T delivery date dev. Negative planned/target delivery date deviation
Pos. P/T delivery date dev. Positive planned/target delivery date deviation
Neg. T/A delivery date dev. Negative target/actual delivery date deviation
Pos. T/A delivery date dev. Positive target/actual delivery date deviation
Neg. P/A delivery date Negative planned/actual delivery date deviation
Pos. P/A delivery date Positive planned/actual delivery date deviation
3.5.1.1.7 Query: 0PP_C01_Q007 TotaI ScheduIe/Lead time Deviation Order View
Purpose:
This query compares schedule deviations of order release, start and delivery dates and determines which caused
the greatest lead time deviation. It also provides information on how well production is being planned.
Structure(s):
Key Figure Remarks
T/A lead time deviation Target/actual lead time deviation
Target lead time
Actual lead time
Page 300
3.5.1.1.8 Query: 0PP_C01_Q008 Quantity/Scrap/Lead time Deviation Order View
Purpose:
This query compares quantity, scrap and lead time deviations.
Structure(s):
Key Figure Remarks
Item quantity Item quantity order
Quantity of goods received Quantity of goods received
Scrap deviation Scrap deviation
T/A lead time dev. Target/actual lead time deviation
3.5.1.1.9 Query: 0PP_C01_Q009 Negative/Positive ScheduIe Deviation Order View
Purpose:
This query compares negative and positive schedule deviations of order release, start and delivery and provides
information on how well production is being planned.
Structure(s):
Key Figure Remarks
Neg. scheduled release dev. Negative share of scheduled release date deviation (%)
Pos. scheduled release dev. Positive share of scheduled release date deviation (%)
Neg. start dev. Negative share of scheduled start date deviation (%)
Pos. start dev. Positive share of scheduled start date deviation (%)
Neg. delivery dev. Negative share of scheduled delivery date deviation (%)
Pos. delivery dev. Positive share of scheduled delivery date deviation (%)
T/A lead time dev. Target/actual lead time deviation
Page 301
3.5.1.1.10 Query: 0PP_C01_Q010 Order Quantity
Purpose:
This query displays all quantity-related key figures.
Structure(s):
Key Figure Remarks
Order quantity Total planned order quantity
Order item Order item quantity
Goods received Quantity of goods received
Scrap quantity Fixed quantity of scrap
Scrap quantity Quantity of scrap from order item
Actual scrap Quantity of actual scrap
No. Prod. orders Number of production orders
3.5.1.1.11 Query: 0PP_C01_Q020 Production Lead Time
Purpose:
This query evaluates the production time frame of an order, taking the factory calendar into consideration.
Structure(s):
Key Figure Remarks
Actual lead time Actual lead time
Actual exec. time Actual execution time
% Exec/lead time Execution time / lead time %
Target lead time Target lead time
T/A lead time dev. % Target/actual lead time deviation %
3.5.1.1.12 Query: 0PP_C01_Q021 ScheduIed Achievement
Purpose:
This query compares the scheduled achievement of the production plan in terms of quantity.
Page 302
Structure(s):
Key Figure Remarks
Planned goods received Planned quantity of goods received minus scrap
Quantity reliability Quantity reliability in %: Quantity of goods received minus planned quantity
3.5.1.2 InfoCube: 0PP_C02 To-the-period order / materiaI view
Contents:
This InfoCube contains all of the production process transaction data related to order header and order item, up-
loaded from the source system(s). The process is mapped from the order start, via the reply, to the delivery. Only
actual data is displayed. However, as this should not be compared with plan data it can be mapped exactly to the
period, provided the OLTP allows this. The InfoCube is suitable for to-the-period quantity observations.
InfoSource:
2LIS_04_S280: Order header and item, BW
Characteristics:
ExternaI hierarchy
avaiIabIe?
0ORDERITEM Order item number No No
0PLANT Plant No No
0CALMONTH Calendar year / Month
0CALQUARTER Calendar year / Quarter
Page 303
0CALWEEK Calendar year / Week
Key figures:
behavior
0ACTUALSRAP Actual scrap quantity 0BASE_UOM Additive
0GR_QTY Quant. of goods received 0BASE_UOM Additive
Unit:
0WM_UOT WM-Time unit Units of measure
0BASE_UOM Base unit of measure Units of measure
The time characteristics 0CALMONTH, 0CALQUARTER and 0CALWEEK are determined via an automatic time
conversion.
3.5.1.2.1 Query: 0PP_C02_Q001 Quantity of Goods Received and Scrap
Purpose:
This query displays exact periods for quantity of goods received and actual scrap quantities.
Structure(s):
Key Figure Remarks
Actual scrap Quantity of actual scrap
Scrap % Actual scrap quantity /quantity of goods received
Page 304
3.5.1.3 InfoCube: 0PP_C03 PIan / actuaI comparison procedure /
work center
Contents:
This InfoCube contains all of the production process transaction data related to order operations, uploaded from
the source system(s). The process is mapped from the creation of a production order, via the release and start, to
the reply. The data is mapped to the actual release date to enable deadline comparisons. In addition, target dates
are only stored if replies exist as otherwise the comparisons will not provide good results.
The InfoCube also contains standard available capacities from the individual work centers. Capacity evaluation is,
therefore, enabled.
InfoSource:
2LIS_04_S281: order operation, BW
0PP_WCCP: PP(PI) Work center capacity
Characteristics:
ExternaI hierarchy
avaiIabIe?
0OPERATION Operation number No No
0PLANT Plant No No
0S_OPERAT Sub-operation No No
0WORKCENTER Work center Yes No
Page 305
Key figures:
behavior
0ACT_FIN_EK Actual finish time: Execute (date) Additive
0ACT_FIN_OK Actual finish time operation (date) Additive
0ACT_INPUTK Actual input (date) Additive
0ACT_STARTK Actual start time: Execute (date) Additive
0CONFRM_QTY Confirmed quantity 0OPER_UNIT Additive
0CONF_SCRAP Confirmed scrap 0OPER_UNIT Additive
0DEL_LOT_SZ Delivered lot size 0OPER_UNIT Additive
0EARLSCHDTK Earliest scheduled start time: Exe-
cute (date)
Additive
0EARL_FINK Earliest scheduled finish time: Exe-
cute (date)
Additive
0INPUTDEV Input schedule deviation 0WM_UOT Additive
0INPUTDEVN Input schedule deviation negative 0WM_UOT Additive
0INPUTDEVP Input schedule deviation positive 0WM_UOT Additive
0LATESTSTRK Latest scheduled start time: Execute
(date)
Additive
0LATEST_FIK Latest scheduled finish time: Exe-
cute (date)
Additive
0MOVE_TIME Transport time was moved 0MOVET_UNIT Additive
0OPER_QTY Operation quantity 0OPER_UNIT Additive
0OPER_STARK Actual operation start (date) Additive
0OUTPUTDEV Output schedule deviation 0WM_UOT Additive
0OUTPUTDEVN Output schedule deviation negative 0WM_UOT Additive
0OUTPUTDEVP Output schedule deviation positive 0WM_UOT Additive
0PROC_TIME Processing time 0PROC_UNIT Additive
0QUEUE_TIME Queue time scheduled 0QTIME_UNIT Additive
0RELSCHDEV Relative schedule deviation 0WM_UOT Additive
Page 306
0RELSCHDEVN Relative schedule deviation negative 0WM_UOT Additive
0RELSCHDEVP Relative schedule deviation positive 0WM_UOT Additive
0SETUP_TIME Set up time 0SETUP_UNIT Additive
0SRAP_QTY Scrap quantity 0OPER_UNIT Additive
0TEARDOWN Tear down 0TEARD_UNIT Additive
0TGTEXECTM Target execution time 0WM_UOT Additive
0TGTLEADTM Target lead time 0WM_UOT Additive
0TGTPROCCAP Process target capacity requirement
for operation segment
0CAPA_UNIT Additive
0TGTSETPCAP Set up target capacity requirement
0CAPA_UNIT Additive
0TGTTEARCAP Tear down target capacity require-
ment for operation segment
0CAPA_UNIT Additive
0TGT_INPUTK Latest target input (date) Additive
0WAIT_TIME Wait time scheduled 0QTIME_UNIT Additive
0STANDCAP Available capacity Additive
0USINGTIME Using time of the capacity Additive
0NO_PRODORD Number of prod. orders Additive
Unit:
0WM_UOT WM-Time unit Units of measure
0OPER_UNIT Operation units Units of measure
0MOVET_UNIT Move time unit Units of measure
0PROC_UNIT Processing time unit Units of measure
0QTIME_UNIT Queue time unit Units of measure
0SETUP_UNIT Set up time unit Units of measure
0TEARD_UNIT Tear down time unit Units of measure
0WAITT_UNIT Wait time unit Units of measure
Page 307
The date key figures (for example, 0ACT_INPUTK actual inflow) only make sense on the lowest level. They are
additive, so that changes are correctly updated.
When filling the InfoCube from InfoSource 0PP_WCCP you should note that, without the data on a time interval,
only the capacity data of the current day is loaded.
0CALDAY Calendar day is filled using the actual release date in the update rules. The other time characteristics
Queries:
All durations are displayed as average per order, all quantities as sums.
3.5.1.3.1 Query: 0PP_C03_Q001 Execution time and scrap variance: Work center view
Purpose:
This query compares the relative execution time and scrap variance. Therefore, you can check whether execution
time variances influence scrap.
Structure (s):
Key figure Comments
Execution time dev. % Execution time deviation in %
Scrap dev. % Scrap deviation in %
Target exec. Time Target execution time
Act. exec. time Actual execution time
Scrap quantity Scrap quantity operation
Conf. scrap Total confirmed scrap
0PLANT Plant, Variable &0S_PLANT&, first line
0WORKCENTER__0WRKCT
_RESP
Person responsible
0WORKCENTER Work center, Variable &0S_WORKC&
0MATERIAL Material number, Variable &0S_MAT&
Page 308
0OPERATION Operation number
0S_OPERAT Sub-operation number
0CALMONTH Calendar year / Month, Variable &0I_CALMO&
3.5.1.3.2 Query: 0PP_C03_Q002 Lead time and reIative scheduIe deviation: Work cen-
ter
Purpose:
This query compares lead time variances with schedule deviations.
Structure(s):
Key figure Comments
Target lead time Target lead time
Act. lead time Actual lead time
Lead. time dev. Lead time deviation
Rel. sched. dev. neg. Relative schedule deviation, negative proportion
Rel. sched. dev. pos. Relative schedule deviation, positive proportion
3.5.1.3.3 Query: 0PP_C03_Q003 Operation times detaiIed
Purpose:
This query displays the (target) operation segments. The operation quantities and the number of production orders
are also given for better arrangement.
Structure(s):
Key figure Comments
Queue time
Setup time
Processing time Processing time
Tear down
Page 309
Wait time
Move time
Operation quantity
Number of prod. orders Number of production orders
3.5.1.3.4 Query: 0PP_C03_Q004 Operation times
Purpose:
This query displays the (target) operation segments, summarized in hours and compares them with execution times
and lead times in days.
Structure(s):
Key figure Comments
Execution time segments Total of the individual execution time segments
Operation segments Total of the individual operation segments
Targ. exec. time Target execution time
Targ. Lead time Target lead time
Operation quantity
No. prod. orders Number of production orders
3.5.1.3.5 Query: 0PP_C03_Q005 ScheduIe deviations Work center view
Purpose:
This query examines to what extent schedule deviations with an inflow to a work center influence schedule devia-
tions with an outflow from this work center.
Structure(s):
Key figure Comments
Input schedule dev. Input schedule deviation
Input schedule dev. neg. Input schedule dev. negative proportion
Input schedule dev. pos. Input schedule dev. positive proportion
Page 310
Output sched. dev. Output schedule deviation
Output sched. dev. neg. Output schedule deviation negative proportion
Output sched. dev. pos. Output schedule deviation positive proportion
3.5.1.3.6 Query: 0PP_C03_Q006 ScheduIe and quantity deviations Work center view
Purpose:
This query examines to what extent schedule deviations influence quantity and scrap deviance in the work center.
Structure(s):
Key figure Comments
Input schedule dev. neg. Input schedule dev. negative proportion
Input schedule dev. pos. Input schedule dev. positive proportion
Output sched. dev. neg. Output schedule deviation negative proportion
Output sched. dev. pos. Output schedule deviation positive proportion
Rel. Sched. dev. Relative schedule deviation
Quantity dev. % Quantity deviation in %
Scrap dev. % Scrap deviation in %
3.5.1.3.7 Query: 0PP_C03_Q007 Capacity Ioad utiIization
Purpose:
This query displays the capacity load utilization of a work center. However, you should note that a capacity re-
quirement generated by an operation is not distributed across several days. Therefore, the query should be called
up for longer periods of time, as the edge of the selection period can contain inaccuracies.
The available capacity is available per work center. This should be noted when drilling down on orders and opera-
tions.
Contrary to query 0PP_C04_Q001 the actual release date is used as the date of the capacity requirement of an
operation instead of the date of the first reply. The query 0PP_C04_Q001 is normally the more suitable for evalua-
tion purposes, especially if the actual release date differs greatly form the reply date.
Page 311
Structure(s):
Key figure Comments
Capacity require. Capacity requirements
Available capacity Available capacity
Capacity load util. Capacity load utilization
3.5.1.3.8 Query: 0PP_C03_Q008 Operation quantities
Purpose:
This query displays all quantity key figures for an operation.
Structure(s):
Key figure Comments
Operation quantity
Del. lot size Entire lot size delivered
Confirm. quantity Entire lot size confirmed
Scrap quantity Scrap quantity operation
Confirm. scrap Entire scrap confirmed scrap
No. prod. orders Number of production orders
3.5.1.4 InfoCube: 0PP_C04 To-the-period operation / work center
view
Contents:
This InfoCube contains all of the transaction data of the production process uploaded from the source system,
based on order operations. The process is mapped from the order start to the reply. Only actual data is displayed.
However, as this should not be compared with target data, it can be mapped to-the-period if the OLTP system is
capable of this. The InfoCube is most suitable for to-the-period quantity evaluations.
InfoSource:
2LIS_04_S281: Order operation, BW
0PP_WCCP: PP(PI) Work center capacity
Page 312
Characteristics:
ExternaI hierarchy
avaiIabIe?
0PLANT Plant No No
0S_OPERAT Sub-operation No No
0WORKCENTER Work center Yes No
Key figures:
behavior
0CONFRM_QTY Confirmed quantity 0OPER_UNIT Additive
0CONF_SCRAP Confirmed scrap 0OPER_UNIT Additive
0DEL_LOT_SZ Delivered lot size 0OPER_UNIT Additive
0TGTPROCCAP Process target capacity require-
ments for operation segment
0CAPA_UNIT Additive
0TGTSETPCAP Set up target capacity requirements
0CAPA_UNIT Additive
0TGTTEARCAP Tear down target capacity require-
ments for operation segment
0CAPA_UNIT Additive
0STANDCAP Available capacity Additive
Page 313
0USINGTIME Using time of the capacity Additive
Unit:
0WM_UOT WM time unit Units of measure
0OPER_UNIT Operation units of measure Units of measure
Recommendation: Create an aggregate using the characteristics plant, material, work center and month. The per-
formance will be significantly improved.
When filling the InfoCube from InfoSource 0PP_WCCP you should note that, without data on a time interval, only
the capacity for the current day is loaded.
Time characteristics 0CALMONTH, 0CALQUARTER and 0CALWEEK are determined from an automatic time con-
version from 0CALDAY.
Queries:
All durations are displayed as average per order, all quantities as sums.
3.5.1.4.1 Query: 0PP_C04_Q001 Capacity Ioad utiIization
Purpose:
This query displays the capacity load utilization of a work center. However, you should note that a capacity re-
quirement generated by an operation is not distributed across several days. Therefore, the query should be called
up for longer periods of time, as the edge of the selection period can contain inaccuracies.
The available capacity is available per work center. This should be noted when drilling down on orders and opera-
tions.
Contrary to query 0PP_C03_Q007 the first reply date of an operation is used as the date of the capacity require-
ment of an operation instead of the actual release date.
Structure(s):
Key figure Comments
Capacity require. Capacity requirements
Available capacity Available capacity
Capacity load util. Capacity load utilization
Page 314
0WORKCENTER__0WRKCT
_RESP
Person responsible
0WORKCENTER Work center, Variable &0S_WORKC&
0OPERATION Operation number
0S_OPERAT Sub-operation number
3.5.2 ActuaI quantities in the work center
3.5.2.1.1 Query: 0PP_C04_Q002 ActuaI quantities in the work center
Purpose:
This query displays the delivered lot sizes, the returned quantities and the returned scrap, to the period.
Structure(s):
Key figure Comments
Del. lot size Delivered lot size
Confirm.quant. Confirmed quantity
Conf. scrap Total scrap confirmed
Scrap % Scrap in %
Page 315
3.5.2.2 InfoCube: 0PP_C05 PIan / actuaI comparison materiaI
consumption
Contents:
This InfoCube contains all of the material consumptions of the production process uploaded from the source sys-
tem. The data is mapped to the actual release to enable a plan / actual comparison. In addition, data is not stored
until a good issue, a reply or a goods receipt for a production order is posted.
InfoSource:
2LIS_04_S282: Order component, BW
Characteristics:
ExternaI hierarchy
avaiIabIe?
0COMPONENT BOM components Yes No
0PLANT Plant No No
Key figures:
behavior
0REQMTSQTY Required quantity 0BASE_UOM Additive
0WITHDRWQTY Withdrawn quantity 0BASE_UOM Additive
0WITHDRWVAL Withdrawn value 0CURRENCY Additive
Page 316
Unit:
Recommendation: Create an aggregate using the characteristics plant, material, component and month. The per-
0CALDAY Calendar day is filled in the update rules using the actual release date. The other time characteristics
3.5.2.2.1 Query: 0PP_C05_Q001 MateriaI consumption target / actuaI
Purpose:
This query displays the requirements and the withdrawn quantities including their values of the material compo-
nents.
Structure(s):
Key figure Comments
Requirement quantity
Withdrawn quantity
Withdrawn value
Quantity dev. Quantity deviation
Quantity dev. % Quantity deviation in %
0PRODORDER__0MRP_CO
NTRL
MRP controller, Variable &0S_PDISP&
0COMPONENT BOM components
Page 317
3.5.2.3 InfoCube: 0PP_C06 To-the-Period MateriaI Consumption
Contents:
This InfoCube contains all of the material consumptions of the production process uploaded from the source sys-
tem. Only actual data is displayed. However, as this should not be compared with target data, it can be mapped to-
the-period if the OLTP system is capable of this. The InfoCube is most suitable for to-the-period quantity evalua-
tions.
InfoSource:
2LIS_04_S282: Order components, BW
Characteristics:
ExternaI hierarchy
avaiIabIe?
0PLANT Plant No No
Key figures:
behavior
Page 318
Unit:
Recommendation: Create an aggregate using the characteristics plant, material, component and month. The per-
3.5.2.3.1 Query: 0PP_C06_Q001 MateriaI consumption
Purpose:
This query displays the withdrawn quantities and their values of the material components from production orders, to
the period.
Structure(s):
Key figure Comments
Withdrawn quantity
Withdrawn value
0PRODORDER__0MRP_CO
NTRL
MRP controller, Variable &0S_PDISP&
0COMPONENT BOM components
Page 319
3.5.3 Repetitive manufacturing
3.5.3.1 InfoCube: 0PP_C07 Repetitive manufacturing Goods re-
ceipts
Contents:
This InfoCube contains all of the transaction data on goods receipt and actual scrap from repetitive production up-
loaded from the source system.
InfoSource:
2LIS_04_S284: Goods receipts repetitive production, BW
Characteristics:
ExternaI hierarchy
avaiIabIe?
0PLANT Plant No No
0PRODVERS Production version Yes No
Key figures:
behavior
0ACTUALSRAP Actual scrap quantity 0BASE_UOM Additive
0GR_QTY Goods receipt quantity 0BASE_UOM Additive
Unit:
0BASE_UOM Base unit of measure Unit of meas-
urement
Page 320
Recommendation: Create an aggregate using the characteristics plant, material, material with plant, production
version and month. The performance will be significantly improved.
3.5.4 Goods receipts Repetitive manufacturing
3.5.4.1.1 Query: 0PP_C07_Q001 Goods receipts Repetitive manufacturing
Purpose:
This query displays the goods receipt quantities and actual scrap quantity for a production version per plant, you
can drilldown according to material and day.
Structure(s):
Key figure Comments
Goods receipt quantity
Actual scrap quantity
Scrap % Actual scrap quantity / Goods receipt quantity in %
0MAT_PLANT__0MRP_CON
TRL
MRP controller, Variable &0M_PDISP&
0PRODVERS Production version
0PRODVERS__0AGGRPV1 Planning ID 1
Page 321
3.5.4.2 InfoCube: 0PP_C08 Repetitive manufacturing MateriaI
consumption
Contents:
This InfoCube contains all of the transaction data on material consumption from repetitive production uploaded
from the source system.
InfoSource:
2LIS_04_S285: Material consumption repetitive prod., BW
Characteristics:
ExternaI hierarchy
avaiIabIe?
0PLANT Plant No No
0PRODVERS Production version Yes No
Key figures:
behavior
0REQMTSQTY Required quantity 0BASE_UOM Additive
Unit:
Page 322
Recommendation: Create an aggregate using the characteristics plant, material, material with plant, component,
production version and month. The performance will be significantly improved.
3.5.4.2.1 Query: 0PP_C08_Q001 MateriaI consumption Repetitive production
Purpose:
This query serves to compare the withdrawn quantities of a production version with the requirement quantities. In
addition, the absolute and relative variation of the quantities and values is calculated.
Structure(s):
Key figure Comments
Required quantity
Withdrawn quantity
Withdrawn value
Quantity dev. Quantity deviation
Quantity dev. in % Quantity deviation in %
0MAT_PLANT__0MRP_CON
TRL
MRP controller, Variable &0S_MDISP&
0COMPONENT Component
0PRODVERS Production version
Page 323
4 Customer ReIationship Management
4.1 MobiIe SaIes
4.1.1 Important Note
The workbooks for Mobile Sales show exemplary analysis options. They contain their own functions in the form of
Visual Basic Macros. The customer can transfer them into his/her enterprise-specific Content, or use parts of them
as a basis for his/her own workbooks. It is just these functions of the Visual Basic Macros that make it easier to use
the workbooks, with features such as navigation options and so on. With the demo workbooks, the process of
making information available to decision support can be speeded up, and Visual Basic functions can be used for
improving individual workbooks. The result is an acceleration in the implementation process and an increase in the
quality of the workbooks.
When activated, the demo workbooks then become the customers responsibility. This means that changes in the
Macro programming cannot be maintained by SAP. The workbooks demonstrate additional options for analysis and
presentation, but they are not meant for productive use.
4.1.2 Activities
4.1.2.1 InfoCube: 0MSA_C01 Activities (Customer/Product)
Content:
This InfoCube contains data of the activity reporting and customer order. Due to this fact it will be possible to an-
swer questions in regard to activities on the one hand and in regard to revenues on the other hand (but also in-
quiries etc.) E.g.: In which way did placed samples influence the revenue of last year?
InfoSource(s):
0MSA_GN_FCT Activity reporting
2LIS_01_S260 SD - Customer order
Characteristics:
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0MATERIAL Material number 0MATERIAL__0MA
TL_GRO
0MATERIAL__0MA
TL_TYP
No
Page 324
0CUSTOMER Customer number 0CUSTOMER__0C
OUNTRY
0CUSTOMER__0C
UST_CLA
0CUSTOMER__0C
UST_MKT
0CUSTOMER__0IN
DUSTRY
0CUSTOMER__0K
EYACCOU
0CUSTOMER__0NI
ELSEN_
0CUSTOMER__0O
UTL_TYP
0CUSTOMER__0R
EGION
No
0SALESORG Sales organization No No
0VTYPE Value type No No
0CALYEAR Calendar year/month
Key figures:
InfoObject Description Units-InfoObject Aggregation
conduct
0NET_VALUE Net value of order position in sales docu-
ment currency
0DOC_CURRCY SUM
0ORDER_QTY Order quantity of the customer in VME 0SALES_UNIT SUM
0NET_WT_AP Net weight of the position 0UNIT_OF_WT SUM
0ACTN_PRIC Action selling price 0CURRENCY SUM
0ORDERS Number of orders SUM
0ORD_ITEMS Number of order positions SUM
0COST Invoice value in sales documents cur-
rency
0DOC_CURRCY SUM
Page 325
0TARGET_QTY Target quantity in sales units 0SALES_UNIT SUM
0TARG_VALUE Target value of outline agreements in
sales document currency
0DOC_CURRCY SUM
0NO_SAMPLE Number of samples SUM
0REAL_PRIC Selling price realized 0CURRENCY SUM
Units:
0DOC_CURRCY Currency of Sales Document Currency
0SALES_UNIT Sales units Unit of measure
0UNIT_OF_WT Unit of weight Unit of weight
0TARGET_QU Unit of target quantity Unit of measure
Notes regarding InfoCube:
Notes regarding update ruIes:
4.1.2.1.1 Query: 0MSA_C01_Q0001 - SampIes according products
Purpose:
The query contains the number of samples which have been placed for each product. So you will be able to get an
overview regarding the distribution of samples.
Structure(s):
Key figure Notes
0NO_SAMPLE Number of samples
0CUSTOMER_0KEYACCOU
NT
Key Account
0CUSTOMER_0CUST_CLA
SS
Classification
0CUSTOMER_0REGION Region
0CUSTOMER_0COUNTRY Country
0CUSTOMER_0INDUSTRY Industry
Page 326
Notes:
4.1.2.1.2 Query: 0MSA_C01_Q0002 - SampIe reporting in detaiI
Purpose:
The query contains the number of samples, distributed for each product. Products will be grouped according types
and according country/region where the samples have been distributed so that you will get a detailed account.
Structure(s):
Key figure Description
0CUSTOMER_0KEYACCOU
NT
Key Account
0CUSTOMER_0CUST_CLA
SS
Classification
0CUSTOMER_0INDUSTRY Industry
Notes:
4.1.2.1.3 Query: 0MSA_C01_Q0003 - SampIes reporting according region
Purpose:
The query contains the number of samples distributed for each product. You will get a detailed account by a
grouping according countries and regions as well as by a subdivision according different months in which the sam-
ples have been distributed.
Structure(s)
Key figures Notes
0MATERIAL Material
Page 327
Note:
4.1.2.1.4 Query: 0MSA_C01_Q0004 - Order quantity for materiaI per month
Purpose:
The query provides an overview which products have been ordered in which quantity and in which month. Different
products will be grouped. You will be able to get an overview which products are mainly influencing the revenue of
different sales offices per month.
Structure(s):
Key figure Description
0ORDER_QTY Order quantity
0SALES_OFF Sales office
Notes:
4.1.2.1.5 Query: 0MSA_C01_Q0005 - Customer order quantity per month
Purpose:
The query provides an overview how many orders have been placed by the customers in which month. Different
customers will be grouped. You will be able to get an overview which customers are mainly influencing the revenue
in different sales offices per month.
Structure(s):
Key figure Note
0ORDERS Number of orders
Notes:
4.1.2.1.6 Query: 0MSA_C01_Q0006 - Action seIIing prices
Purpose:
The query provides an overview in which way the action selling prices has been changed for different products in
which month. So you will be able to get an overview of the development in different sales offices.
Page 328
Structure(s):
Key figures Notes
0ACTN_PRIC Action selling price
Notes:
4.1.2.1.7 Query: 0MSA_C01_Q0007 - Overview of orders per division
Purpose:
The query provides an overview in which way the order key figures are represented for the different divisions. The
divisions will be grouped. So you will get an overview of the development in different sales offices.
Structure(s):
Key figure Notes
0COST Invoice value in sales document currency
0ORDER_QTY Order quantity of the customer of VME
Notes:
4.1.2.1.8 Query: 0MSA_C01_Q0008 - Orders per saIes office
Purpose:
The query provides an overview about the number of orders distributed by the customers. The grouping is effected
by customers. You will be able to get an overview about the development of different sales offices.
Structure(s):
Figure Notes
0ORDERS Orders
Page 329
Notes:
4.1.2.2 InfoCube: 0MSA_C02 Activities (Customers)
Content:
That InfoCube contains data of the activity reporting, activity management and customer order. This way general
success control of activities will be guaranteed (not on product-level).
InfoSource(s):
0MSA_GN_ACT Activities
Characteristics:
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0SOLD_TO Sold-to party 0SOLD_TO__0ACC
NT_GRP
0SOLD_TO__0COU
NTRY
0SOLD_TO__0CUS
T_CLAS
0SOLD_TO__0CUS
T_MKT
0SOLD_TO__0IND
USTRY
0SOLD_TO__0KEY
ACCOUN
0SOLD_TO__0NIEL
SEN_I
0SOLD_TO__0OUT
L_TYPE
0SOLD_TO__0REG
ION
0SOLD_TO__0VISI
T_RYT
No
Page 330
Key Figures:
conduct
0NET_VALUE Net value of order position in sales docu-
ment currency
0DOC_CURRCY SUM
0NO_ACTIV Number of activities SUM
0COST Invoice value in sales document currency 0DOC_CURRCY SUM
Units:
0DOC_CURRCY Currency of the sales document Currency
0UNIT_OF_WT Unit of weight Unit of measure
Notes to InfoCube:
Notes to update ruIes:
4.1.2.2.1 Query: 0MSA_C02_Q0001 - RegionaI AnaIysis
Purpose:
The query provides an overview in which way the net values of order positions will be distributed per month and per
region. The grouping will be effected according regions.
Page 331
Structure(s):
Key figures Notes
0NET_VALUE Net value of order positions in sales document currency
Notes:
4.1.2.2.2 Query: 0MSA_C02_Q0002 - Customer-specific anaIysis
Purpose:
The query provides an overview of different key figures which are monthly distributed on the customers. The
grouping will be effected according customers. You will get an overview of the development regarding different
characteristics.
Structure(s):
Figure Notes
0NO_ACTIV Number of activities
0COST Invoice value of sales document currency
0SOLD_TO_0KEYACCOUNT Key Account
0SOLD_TO_0ACCNT_GRP Customer account group
0SOLD_TO_0CUST_CLASS Customer classification
0SOLD_TO_0CUST_MKT Market of the customer
0SOLD_TO_0OUTL_TYPE Outlet type
0SOLD_TO_0NIELSEN_ID Nielsen indicator
Page 332
0SOLD_TO_0REGION Region
0SOLD_TO_0VIST_RYT Pre-defined visit rhythm
Notes:
4.1.2.2.3 Query: 0MSA_C02_Q0003 - Activities of Key Accounts
Purpose:
The query provides an overview of all differently defined key figures which will be monthly distributed on the cus-
tomers. The grouping will be effected according customers. So you will get an overview of the development/phases
for the Key Account Management.
Structure(s):
Figure Notes
0NET_WT_AP Net weight of the position
0REAL_PRIC Selling price realized
Notes:
4.1.2.2.4 Query: 0MSA_C02_Q0004 - Activities according industries
Purpose:
The query provides an overview of the development of the net value - monthly distributed to the industries. The
grouping will be effected according industries.
Page 333
Structure(s):
Figure Notes
0NET_VALUE Net values of order positions in sales document currency
Notes:
4.1.2.2.5 Query: 0MSA_C02_Q0005 - Activities according customer cIasses
Purpose:
The query provides an overview of the development of the net value which will be monthly distributed to the cus-
tomer classification. The grouping will be effected according customer classes.
Structure(s):
Figure Notes
Notes:
4.1.2.2.6 Query: 0MSA_C02_Q0006 - Activities according NieIsen-indicators
Purpose:
The query provides an overview of the development of different key figures which will be monthly distributed to the
appropriate Nielsen-indicators. The grouping will be effected according Nielsen-indicators. Prices, activities and
orders will be compared periodically.
Structure(s):
Figure Notes
Page 334
0NET_VALUE Net value of order position in sales document currency
Notes:
4.1.2.2.7 Query: 0MSA_C02_Q0007 Activities according outIet type
Purpose:
The query provides an overview of the development of different key figures which will be monthly distributed to the
appropriate outlet types. The grouping will be effected according outlet types. Prices, activities and orders will be
compared periodically.
Structure(s):
Figures Notes
0NET_VALUE Net value of order positions ins sales document currency
Notes:
4.1.2.2.8 Query: 0MSA_C02_Q0008 - Visit rhythm - anaIysis
Purpose:
The query provides an overview of the development of different figures which will be monthly distributed on a visit
rhythm. The grouping will be effected according visit rhythm. Prices, activities and orders will be compared periodi-
cally.
Page 335
Structure(s):
Figure Notes
0NET_VALUE Net value of order positions of sales document currency
Notes:
4.1.2.3 InfoCube: 0MSA_C03 Revenues
Content:
That InfoCube contains data of the customer order. That data will be enhanced by CRM-Master Data - relations to
activities, opportunities, campaigns and promotions.
InfoSource(s):
Characteristics:
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
TL_GRO
0MATERIAL__0MA
TL_TYP
No
Page 336
0SOLD_TO Sold-to party 0SOLD_TO__0ACC
NT_GRP
0SOLD_TO__0COU
NTRY
0SOLD_TO__0CUS
T_CLAS
0SOLD_TO__0CUS
T_MKT
0SOLD_TO__0IND
USTRY
0SOLD_TO__0KEY
ACCOUN
0SOLD_TO__0NIEL
SEN_I
0SOLD_TO__0OUT
L_TYPE
0SOLD_TO__0REG
ION
0SOLD_TO__0VISI
T_RYT
No
0SALES_DIST Sales district No No
0SLS_ACTIV Activity No No
0SAL_PROM Promotion No No
0OPP_NUM Opportunity 0OPP_NUM__0OP
PRRESUL
0OPP_NUM__0OP
P_CLAS
0OPP_NUM__0OP
P_KIND
0OPP_NUM__0OP
P_PHASE
0OPP_NUM__0OP
P_REF
0OPP_NUM__0OP
P_RESUL
0OPP_NUM__0OP
P_TYPE
No
0ORD_REASON Reason for order (Reason for procedure) No No
0DOC_CATEG Sales document category No No
0DOC_TYPE Sales document type No No
Page 337
Key Figures:
InfoObject Description Units-InfoObject Aggregation-
conduct
0NET_VALUE Net value of order positions in sales
document currency
0DOC_CURRCY SUM
0ORDER_QTY Order quantity of the customer in VME 0SALES_UNIT SUM
0COST Invoice value in sales document currency 0DOC_CURRCY SUM
Units:
0DOC_CURRCY Currency of the sales document Currency
0SALES_UNIT Sales units Unit of measure
0UNIT_OF_WT Unit of weight Unit of measure
Notes to InfoCube:
Notes to update-ruIes:
Additional fields will be filled according to the update-rules. Therefore it is necessary that master data are already
loaded.
4.1.2.3.1 Query: 0MSA_C03_Q0001 - Order quantity
Purpose:
The query provides an overview of the development of the order quantity per product and sold-to party. The
grouping will be effected according material.
Structure(s):
Figure Notes
0ORDER_QTY Order quantity of the customer in VME
Page 338
Notes:
4.1.2.3.2 Query: 0MSA_C03_Q0002 - Net vaIue
Purpose:
The query provides an overview of the development of the net value per product and sold-to party. The grouping
will be effected according material.
Structure(s):
Figure Notes
0NET_VALUE Net value of order position in sales document currency
Notes:
4.1.2.3.3 Query: 0MSA_C03_Q0003 - Invoice vaIue
Purpose:
The query provides an overview of the development for the invoice value per product and sold-to party. The
grouping will be effected according sold-to party.
Structure(s):
Figure Notes
Page 339
Notes:
4.1.2.3.4 Query: 0MSA_C03_Q0004 - Coverage
Purpose:
The query provides an overview of the development of the coverage calculated per product and sold-to party. The
grouping will be effected according the material.
Structure(s):
Figure Notes
Coverage Coverage (0NET_VALUE ./. 0COST)
InfoObject Beschreibung:
Notes:
4.1.2.3.5 Query: 0MSA_C03_Q0005 - Opportunity / Revenue
Purpose:
The query provides an overview of the development of the net value per sales organization. The grouping will be
effected according the criteria promotion and promotion type.
Structure(s):
Figure Notes
0NET_VALUE Net value
Notes:
4.1.2.3.6 Query: 0MSA_C03_Q0006 - Promotion / Revenue
Purpose:
The query provides an overview of the development of the net value per region. The grouping will be effected ac-
cording the criterion promotion.
Page 340
Structure(s):
Figure Notes
Notes:
4.1.2.3.7 Query: 0MSA_C03_Q0007 - Revenues according Opportunity-CIassification
Purpose:
The query provides an overview of the development of the net value per month. The grouping will be effected ac-
cording the criterion Opportunity-Classification.
Structure(s):
Figure Notes
Notes:
4.1.2.3.8 Query: 0MSA_C03_Q0008 - Revenues according Opportunity-ResuIt Reason
Purpose:
cording the criterion Opportunity-Result Reason.
Structure(s):
Figure Notes
Page 341
Notes:
4.1.2.3.9 Query: 0MSA_C03_Q0009 - Revenues according kind of opportunity
Purpose:
cording the criterion kind of opportunity.
Structure(s):
Figure Notes
Notes:
4.1.2.3.10 Query: 0MSA_C03_Q0010 - Revenues according Opportunity type
Purpose:
cording the criterion Opportunity type.
Structure(s):
Figure Notes
Notes:
4.1.2.3.11 Query: 0MSA_C03_Q0011 - Order deveIopment
Purpose:
cording the criterion material.
Page 342
Structure(s):
Figure Notes
0DOC_TYPE Sales document type
0SLS_ACTIV_0SLS_ACTYP Activity type
0SAL_PROM_0PROM_TYPE Promotion type
0SAL_PROM Promotion
0OPP_NUM_0OPP_KIND Kind of opportunity
0OPP_NUM_0OPPRRESULT Opportunity result
0OPP_NUM_0OPP_CLAS Opportunity classification
Notes:
4.1.2.3.12 Query: 0MSA_C03_Q0012 - Promotion / VoIume
Purpose:
The query provides an overview of the development of the net weight per customer classification. The grouping will
be effected according the criterion promotion.
Structure(s):
Figure Notes
0NET_WT_AP Net weight
Notes:
4.1.2.4 InfoCube: 0MSA_C04 Activities
Content:
That InfoCube contains analysis and evaluations of the tables concerning activities activity reporting. It is principally
suitable for questioning, especially in regard to the number of activities and samples under certain criteria.
Page 343
InfoSource(s):
0MSA_GN_ACT Activities
Characteristics:
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0REGION Region (Federal State) No No
0INDUSTRY Industry key No No
0CUST_MKT Market of the customer No No
0CUST_CLASS Customer classification No No
0OUTL_TYPE Outlet type No No
0ACCNT_GRP Customer account group No No
0NIELSEN_ID Nielsen-indicator No No
0KEYACCOUNT Key Account No No
0TYPE_CP Customer (R/3) or prospect (Mobile Sales) No No
0SLS_ACTIV Activity 0SLS_ACTIV__0SL
S_ACSTAT
0SLS_ACTIV__0SL
S_ACTYP
No
Key Figures:
conduct
0NO_FACNG Number of facings SUM
Page 344
0NO_ACTIV Number of activities SUM
Units:
Notes to InfoCube:
Notes to the update ruIes:
4.1.2.4.1 Query: 0MSA_C04_Q0001 - Activities (Number of activities per prospect)
Purpose:
That query indicates the number of activities including prospects (only available in Mobile Sales) for one calendar
year. Furthermore the key figure is subdivided into customer classifications.
Structure(s):
Key Figure Notes
0COUNTRY Country key
0REGION Region (Federal State)
0SLS_ACTIV__0SLS_ACSTAT Activity status
Notes:
4.1.2.4.2 Query: 0MSA_C04_Q0002 - Activity status
Purpose:
That query indicates the number of activities for each activity type per calendar month. The key figure is subdivided
into the activity status.
Page 345
Structure(s):
Key figure Notes
0CUST_CLASS Customer classification
Notes:
4.1.2.4.3 Query: 0MSA_C04_Q0003 - Activities (Number of facings)
Purpose:
The query indicates the number of facings in a chronological development (on month-level) for the individual re-
gions.
Structure(s):
Figure Notes
0NO_FACNG Number of facings
0INDUSTRY Industry key
Notes:
4.1.2.4.4 Query: 0MSA_C04_Q0004 - RegionaI AnaIysis
Purpose:
That query indicates the number of activities and samples within their chronological development (on month-level)
for the individual regions and countries.
Page 346
Structure(s):
Key Figure Notes
0SLS_ACTIV__0SLS_ACTYP Activity type
Notes:
4.1.2.4.5 Query: 0MSA_C04_Q0005 - Activities Key Account
Purpose:
That query indicates the number of activities for Key Accounts within their chronological development (on month-
level) for the individual Nielson-indicators.
Structure(s):
Figure Notes
0SLS_ACTIV Activity
Notes:
4.1.2.4.6 Query: 0MSA_C04_Q0006 - Activity-types
Purpose:
That query provides an overview of the number of activities and samples within their chronological development
(on month-level) for activity types.
Structure(s):
Key Figure Notes
Page 347
0ACCNT_GRP Customer account group
Notes:
4.1.3 Opportunity
4.1.3.1 InfoCube: 0HTMSAC01 Opportunities (with reference to
materiaI)
Content:
That InfoCube contains material information regarding opportunities. A pipeline or a funnel analysis is not possible
as the characteristics of the opportunity are directly taken from the master data.
InfoSource(s):
0HT_MSA_OPP_1 Opportunities
Characteristics:
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0OPP_NUM Opportunity 0OPP_NUM__0OP
PRRESUL
0OPP_NUM__0OP
P_CLAS
0OPP_NUM__0OP
P_KIND
0OPP_NUM__0OP
P_PHASE
0OPP_NUM__0OP
P_REF
0OPP_NUM__0OP
P_RESUL
0OPP_NUM__0OP
P_TYPE
No
TL_GRO
0MATERIAL__0MA
TL_TYP
No
Page 348
0TYPE_CP Customer (R/3) or Prospect (Mobile Sales) No No
0SAL_PROM Promotion 0SAL_PROM__0PR
OM_STA
0SAL_PROM__0PR
OM_TYP
No
Figure:
conduct
0OPP_MQUNT Opportunity units (material) 0UNIT SUM
0OPP_MVOL Opportunity volume (material) 0CURRENCY SUM
0OPP_PROBM Opportunity probability (material) MIN
Units:
Page 349
Notes to InfoCube:
4.1.3.1.1 Query: 0HTMSAC01_Q0001 - Product AnaIysis
Purpose:
That query indicates the expected value in its chronological development (on month-level) for the different materi-
als.
Structure(s):
Figure Notes
Expected value
0OPP_KIND Kind of Opportunity
0OPP_PHASE Opportunity phase
0OPP_TYPE Opportunity type
0OPP_CLAS Opportunity classification
0OPPRRESULT Opportunity result reason
0OPP_RESULT Opportunity result
Notes:
4.1.3.1.2 Query: 0HTMSAC01_Q0002 - MateriaI-Group AnaIysis
Purpose:
That query indicates the expected value in its chronological development (on month-level) for the different material-
groups.
Page 350
Structure(s):
Figure Notes
Expected value
Notes:
4.1.3.2 InfoCube: 0HTMSAC02 Opportunities (PipeIine AnaIysis)
Content:
That InfoCube contains data regarding the pipeline or funnel analysis. It helps answering questions: How many
opportunities of type X are available in which phase? How many were available last year? How many opportunities
get lost due to which reason?
InfoSource(s):
0HT_MSA_OPP_2 Opportunities (historical view)
Characteristics:
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0OPP_FROM Start date of opportunity No No
0OPP_KIND Kind of opportunity No No
0OPP_PHASE Opportunity phase No No
0OPP_REF Reference project No No
0OPP_TO End opportunity No No
0OPP_TYPE Opportunity type No No
0OPP_CLAS Opportunity classification No No
0OPP_NUM Opportunity No No
0OPPRRESULT Opportunity reason result No No
0OPP_RESULT Opportunity result No No
Page 351
0CUSTOMER Customer number No No
0PROSPECT Prospect No No
0TYPE_CP Customer (R/3) or prospect (Mobile Sales) No No
0SAL_PROM Promotion 0SAL_PROM__0PR
OM_STA
0SAL_PROM__0PR
OM_TYP
No
Key figures:
conduct
0NO_OPPTNTY Number of opportunities SUM
0OPP_AGE Opportunity age (days) SUM
0OPP_PROB Opportunity probability MIN
0OPP_VOL Opportunity volume 0CURRENCY SUM
Units:
Page 352
Notes to InfoCube:
4.1.3.2.1 Query: 0HTMSAC02_Q0001 - RegionaI expected vaIue
Purpose:
That query indicates the expected value within its chronological development (on month-level) for the individual
regions.
Structure(s):
Figure Notes
Expected value
0OPP_KIND Kind of opportunity
0OPP_PHASE Opportunity phase
0OPPRRESULT Opportunity result reason
0OPP_RESULT Opportunity reason
Notes:
4.1.3.2.2 Query: 0HTMSAC02_Q0002 - PipeIine Customers
Purpose:
That query indicates the expected value and all key figures of the InfoCube for the individual customers of different
phases.
Structure(s):
Key figures Notes
0NO_OPPTNTY Number of opportunities
0OPP_AGE Opportunity age (days)
0OPP_PROB Opportunity probability
0OPP_VOL Opportunity volume
Expected value
Page 353
Notes:
4.1.3.2.3 Query: 0HTMSAC02_Q0003 - PipeIine PotentiaI customers
Purpose:
That query indicates the expected value and all figures of the InfoCube for the individual potential customers in
different phases.
Structure(s):
Key figure Notes
Expected value
Notes:
4.1.3.2.4 Query: 0HTMSAC02_Q0004 - PipeIine Customers (according phases)
Purpose:
That query indicates the expected value and all key figures of the InfoCube for the individual customers in different
phases (in columns).
Structure(s):
Key figure Notes
Page 354
Expected value
Notes:
4.1.3.2.5 Query: 0HTMSAC02_Q0005 - PipeIine cIassification
Purpose:
That query indicates the expected value for different classifications in different phases (in columns).
Structure(s):
Key figure Notes
Expected value
Notes:
4.1.3.2.6 Query: 0HTMSAC02_Q0006 - Kind of pipeIine
Purpose:
That query indicates the expected value for the different kinds in different phases (in columns).
Structure(s):
Key figure Notes
Expected value
Page 355
Notes:
4.1.3.2.7 Query: 0HTMSAC02_Q0007 - PipeIine ResuIt reason (Lost Order AnaIysis)
Purpose:
That query indicates the expected value for different result reasons in different phases (in columns).
Structure(s):
Key figure Notes
Expected value
Notes:
Page 356
5 ExternaI Data
5.1 IS-RetaiI
5.1.1 SAP CampbeII Integration
5.1.1.1 Important Note
The workbooks Job Productivity and Department Productivity for SAP Campbell show exemplary analysis op-
tions. They contain their own functions in the form of Visual Basic Macros. The customer can transfer them into
his/her enterprise-specific Content, or use parts of them as a basis for his/her own workbooks. It is just these func-
tions of the Visual Basic Macros that make it easier to use the workbooks, with features such as navigation options
and so on. With the demo workbooks, the process of making information available to decision support can be
speeded up, and Visual Basic functions can be used for improving individual workbooks. The result is an accelera-
tion in the implementation process and an increase in the quality of the workbooks.
When activated, the demo workbooks then become the customers responsibility. This means that changes in the
Macro programming cannot be maintained by SAP. The workbooks demonstrate additional options for analysis and
presentation, but they are not meant for productive use.
5.1.1.2 InfoCube: 0RC_C01 Labor Data
Content:
Labor is the single largest controllable expense in the retail environment. It is crucial for management to under-
stand how it is being spent across the chain and to use this knowledge to deploy it strategically and advance the
goals of the company . The labor InfoCube allows management to monitor store performance and to analyze actual
versus scheduled data. By fully understanding this distribution of labor, users can meet customer service and non-
sales requirements while still controlling labor costs and ensuring profitability.
This InfoCube contains the following labor-related information
- Actual and scheduled working hours (for example, regular working hours, overtime hours)
- Actual and scheduled payment (for example, regular pay, overtime pay)
- Workload: expected manpower demand. It is forecast by the SAP Campbell system but can also be adjusted
manually by the store manager. It is represented as working time hours at job level.
- Coverage statistics: reflects the staffing level (understaffing or overstaffing)
The information is presented at the following levels:
- Store
- Job: each employee can be assigned a number of different jobs, with one of them defined as his primary job.
All data stored within the SAP Campbell system is aggregated in BW at job level.
InfoSource:
0RC_CI_1 Labor
Page 357
Characteristics:
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0RC_STORE Store Yes No
0RC_JOB Job Yes No
0RC_DAYWK1 Day of week (Monday, Tuesday...) Yes No
0CALWEEK Calendar year and week
0FISCPER Fiscal year and period
Key figures:
InfoObject Description Unit InfoObject AggregationaI
behavior
0RC_TOT_WL Total workload: the total number of fore-
cast hours. This is the sum of flowed and
filler workload.
0UNIT cumulative
0RC_FLOW_WL Flowed workload: workload driven by
revenue, customer count or any other
variable flowed task defined in the SAP
Campbell system. Includes the static
workload.
0UNIT cumulative
0RC_FILL_WL Filler workload: the fixed and variable
filler hours allocated to the workload. In
contrast to static workload that has to be
scheduled for certain times (for example,
9 a.m. to 10 a.m.), filler workload refers to
non-selling tasks that can be scheduled
variably within certain time segments (for
example, in the morning). As a rule, filler
workload fills the gaps between workload
peaks.
0UNIT cumulative

1
Since BW, Release 1.2b, does not contain a time characteristic such as day of week, 0RC_DAYWK was imple-
mented as a standard characteristic. 0RC_DAYWK is calculated within the update rules using the function module
DATE_COMPUTE_DAY.
Page 358
0RC_STAT_WL Static workload: work manually defined
by the user. It is constant and independ-
ent of revenue, customer count or any
business indicator or task defined in the
SAP Campbell system (for example, the
person who unlocks the store).
0UNIT cumulative
0RC_OVRSTFF Overstaffing: the number of hours in which
the total workload is smaller than the
number of people scheduled and not on
an unpaid break
0UNIT cumulative
0RC_UNDSTFF Understaffing: the number of hours in
which the total workload is greater than
the number of people scheduled and not
on an unpaid break
0UNIT cumulative
0RC_EFFHRS Effective hours: the scheduled hours mi-
nus overstaffed hours minus breaks. The
values will be zero for events (for exam-
ple, training or meetings) because these
are not scheduled. From the perspective
of the SAP Campbell system, effective
hours are scheduled hours that match the
workload hours. They are a general
measure of schedule quality.
0UNIT cumulative
0RC_NEFFHRS Non-effective hours: the sum of over-
staffing and understaffing for the day.
The values will be zero for events (for
example, training or meetings), fixed shift
and temporary fixed shift job types, be-
cause these are not scheduled. Non-
effective hours could, for example, be
spent working on the shop floor and be
paid while the SAP Campbell system cal-
culated no corresponding demand.
0UNIT cumulative
0RC_COREAFT Core afternoon hours: the number of
hours of core coverage as part of the
workload for the afternoon segment. Core
coverage means that employees with a
particular job-specific minimum skill level
must be scheduled.
0UNIT cumulative
0RC_COREEVN Core evening hours: the number of hours
of core coverage as part of the workload
for the evening segment. Core coverage
means that employees with a particular
job-specific minimum skill level must be
scheduled.
0UNIT cumulative
0RC_COREMRN Core morning hours: the number of hours
for the morning segment. Core coverage
scheduled.
0UNIT cumulative
0RC_PAIDBR Paid breaks: the number of hours of
scheduled paid breaks
0UNIT cumulative
Page 359
0RC_NPAIDBR Unpaid breaks: the number of hours of
scheduled unpaid breaks
0UNIT cumulative
0RC_MANEDIT Manual edits: manual changes to the
system-generated staffing schedule. The
number of scheduled days (shifts) that
have been manually edited for every em-
ployee. Edits are attributed to each em-
ployees primary job.
cumulative
0RC_RULVIOL Number of employees with violations of
scheduling work rules assigned to the
primary job
cumulative
0RC_SCDHRS Scheduled hours: total number of sched-
uled hours that are not unpaid breaks.
This includes all hours scheduled (regu-
lar, overtime, vacation, and so on).
0UNIT cumulative
0RC_SCDEHRS Scheduled event hours: this key figure is
the sum of all hours that employees with
the selected job as their primary job spend
in events (for example, training or meet-
ings).
0UNIT cumulative
0RC_SCDOHRS Scheduled overtime hours: the number of
hours that will be paid at a higher rate (at
a multiple higher than one), regardless of
the reason.
0UNIT cumulative
0RC_SCDPAY Scheduled pay: The total payroll for the
scheduled hours. This includes regular,
overtime, vacation, and so on.
0CURRENCY cumulative
0RC_SCDEPAY Scheduled event pay: the total payroll for
the scheduled event hours, calculated
from scheduled event hours.
0RC_ACTRHRS Actual regular hours: actual (punched)
paid non-overtime hours.
0UNIT cumulative
0RC_ACTOHRS Actual overtime hours: actual paid over-
time hours.
0UNIT cumulative
0RC_ACTEHRS Actual event hours: actual hours spent in
an event. These hours are assigned to
the employees primary job.
0UNIT cumulative
0RC_ACTPHRS Actual productive hours: within the SAP
Campbell system, hours can be labeled
as productive (for example, regular
hours) or non-productive (for example,
hours spent on vacation). Typically, pro-
ductive hours are spent in direct support
of the stores operations
0UNIT cumulative
Page 360
0RC_ACTNHRS Actual non-productive hours: within the
SAP Campbell system, these are hours
that can be labeled as productive (for
example, regular hours) or non-
productive (for example, hours spent on
vacation). Typically, non-productive hours
are not spent in direct support of the
stores operations.
0UNIT cumulative
0RC_ACTRPAY Actual regular pay: total payroll for the
actual regular hours, as calculated by the
SAP Campbell system.
0RC_ACTOPAY Actual overtime pay: total payroll for the
actual overtime hours, as calculated by
the SAP Campbell system.
0RC_ACTEPAY Actual event pay: the pay for the actual
event hours.
0RC_RPFLG Reporting flag: auxiliary variable indicat-
ing whether actual figures are available
for the selected day and store.

0RC_LYRPFLG Last year reporting flag: auxiliary variable
indicating whether actual figures are
available for the selected day and store in
the previous year.

0RC_ADJHOUR Adjusted hours: auxiliary variable used
only to compute the calculated key fig-
ures net scheduled hours and projected
hours. It equals zero if actual hours exists
or it equals scheduled hours if no actual
hours exists.
0UNIT cumulative
0RC_ADJPAY Adjusted pay: this is an auxiliary variable
used only to compute the calculated key
figures net scheduled pay and projected
pay. It equals zero if actual pay figures
exists or it equals scheduled pay if no
actual pay exists.
Units:
0UNIT Unit of measurement UNIT
0CURRENCY Currency key CUKY
Contains information available in the current extraction file, that is, data delivered from the SAP Campbell system.
The SAP Campbell system uses the following terms when referring to labor and sales key figures:
- scheduled hours: labor representing shifts scheduled by the SAP Campbell system and/or edited by the man-
ager.
Page 361
- workload hours: labor representing the manpower demand for the work to be done. Scheduled hours are the
supply ideally placed to cover the workload demand.
- actual hours: labor representing shifts actually worked. In an ideal scenario, the actual hours should be placed
exactly where the workload demand is placed and the schedule was created to cover that demand.
- planned sales: budgeted sales figures supplied by the corporate headquarters
- system sales: sales forecast computed by algorithms from the SAP Campbell system
- manager sales: adjustments made by the user to the SAP Campbell systems forecast
- actual sales: sales actually reported on that day. Ideally, it should match the plan, system and manager fore-
cast.
In a subscreen users define a Daily Interval as the relevant selection period for each query of this InfoCube. They
do so by specifying a start date and an end date for the query selection.
In BW, if stores upload data twice for a specific day, the new data is not added to the existing values but the old
data is completely replaced by the newest data. For example, if store_1 uploaded $100 for July 10, 1999 and busi-
ness indicator_2 (dairy products), and if the same store then uploads $125 for the same date and business indica-
tor, the update rules for the SAP Campbell integration InfoCubes replace the value $100 by $125. BW standard
update rules would add both figures together to a total $225.
Comments on queries from InfoCube 0RC_C01:
Some key figures are marked as hidden because they are part of the query definition but are not displayed when
you execute the query.
When comparing actual with planned values it can happen that planned values but no corresponding actual figures
are available. This may cause problems for interpreting aggregated key figures that compare actual with sched-
uled data. To solve this problem, the following calculated key figures were introduced:
- Net Scheduled Hours: only scheduled hours for which corresponding actual hours are available. If no actual
hours are available, net scheduled hours equals zero. Net scheduled key figures describe the scheduled value
of only those stores that reported information for the particular time period. This will allow users to see only
scheduled vs. actual figures for stores that have both scheduled and actual figures. For example, if nine stores
reported 100 actual hours for the day and one store was missing, there would be 900 actual hours. If all ten
stores in the district had scheduled to work 100 hours, then the actual vs. scheduled figures would be 900 di-
vided by 1000 or 90 % of schedule. This indicates results that are below expectation. However, if you compare
the actual vs. the net plan (plan for reporting stores) figures, this would be 900/(1000-100) or 900/900 = 100 %
of plan. This indicates good performance. Whenever some stores do not report actual values, the comparison
of actual vs. planned figures will be misleading unless they have been cleaned using net plan or projected val-
ues.
- Projected Hours: it equals actual hours where actual hours exist. If no actual hours is available, projected hours
equals scheduled hours. Projected key figures are a projection of certain values under the assumption that all
stores reported that information for the particular time period. This will allow users to have a best estimate for
when a single store or group of stores does not report for a specific time period. Usually, the scheduled data is
used as a substitute for actual data to allow this projection. For example, if nine stores reported 100 hours each
for the day and one store did not report, the 75 scheduled hours may be substituted for the missing figure to
give us a total of 975 projected hours for the day.
The same logic as described for net scheduled hours is implemented for Net Last Year Hours. This includes only
those previous years hours for which corresponding actual hours exist for the current year.
Page 362
5.1.1.2.1 Query: 0RC_C01_Q0003 ActuaI vs. ScheduIed Overtime
Use:
This query enables users to identify stores that are poorly staffed and evaluate whether they are managing their
overtime situation properly. Stores that are poorly staffed or poorly managed often have serious overtime problems.
This means that workers are forced to work more hours than the standard working week. If stores are running a
high percentage of overtime compared to their peer group, the store may need to hire more people or borrow em-
ployees from neighboring stores.
Structure(s):
Key figure Remarks
Actual vs. Scheduled Over-
time Hours
Percentage of overtime hours actually worked in the store compared with
the number of overtime hours scheduled
Overtime Hours Total number of overtime hours worked
Scheduled Overtime Hours Number of scheduled overtime hours
Actual Overtime vs. Total
Hours
Percentage of overtime hours actually worked compared with the total
number of worked hours
0RC_GEOLEV2 Division
0RC_GEOLEV1 District
0RC_STORE Store
0RC_STORETY Store type
0RC_JOB Job
Comments:
Since overtime hours typically cost a retailer one and a half to two times as much as the basic payroll costs, these
hours quickly cause the labor budget to spiral out of control. No comparable store reporting is used in this report.
For this reason, the report should be viewed as an analysis report over a timeframe when all stores are known to
report.
Reporting is usually done on a weekly basis. Primary target group for this report: field management.
5.1.1.2.2 Query: 0RC_C01_Q0005 Customer Service
Use:
This report enables users to assess the level of customer service from a perspective of hours spent in front of the
customers. A well-run store is likely to run within company guidelines. Stores with a high percentage are maximiz-
ing their time in front of the customer and increasing the likelihood of increased sales or customer service. Stores
with percentages that are too high may be sacrificing other critical support tasks and may have poor stocking or
poor store appearance. Each client may have their own maximum based on the type of store. However, by com-
Page 363
paring stores across the chain, field managers and corporate executives can target stores that are not as efficient
in terms of customer service.
Structure(s):
Key figure Remarks
Selling Hours Percentage Percentage of selling hours compared with the total number of workload
hours
Selling Hours Equals the number of flowed workload hours minus static workload hours
Total Workload Total number of workload hours forecast by the SAP Campbell System
0RC_STORE Store
0RC_JOB Job
Comments:
Reporting is usually done on a weekly basis. Primary target groups for this report: business analysts, corporate
executives.
5.1.1.2.3 Query: 0RC_C01_Q0007 Department Productivity - DEMO
Use:
This query is very similar to the Store productivity query. Common measures of retail productivity include sales per
labor hour and payroll percent. This report allows users to see the variance between the actual productivity and the
schedule for these two very important metrics. This query enables users to review productivity across time and
across the departments within the store.
Structure(s):
Key figure Remarks
Projected Actual Hours Equals total hours where total hours exist. If no total hours figure is avail-
able, projected hours equals scheduled hours.
Scheduled Hours Number of hours scheduled that are not unpaid breaks. Includes all sched-
uled hours (regular, overtime, vacation, and so on).
Projected Pay Equals total pay where total pay exists. If no total pay is available, pro-
jected pay equals scheduled pay
Scheduled Pay Total amount of scheduled pay
Page 364
Projected Sales Equals sales where actual sales figures exist. If no actual sales is avail-
able, projected sales equals planned sales.
Managers Forecast Amount of sales forecast by the manager
Projected Scheduled Sales
per Hour
Difference between projected sales per hour and scheduled sales per hour
Projected Sales per Hour Projected sales divided by projected hours
Scheduled Sales per Hour Manager's forecast sales divided by scheduled hours
Projected Scheduled Labor
Percent
Difference between projected and scheduled labor percent
Projected Labor Percent Projected payroll divided by projected sales
Scheduled Labor Percent Scheduled payroll divided by planned sales
0RC_REGION Region
0RC_STORE Store
Comments:
The query yields complete results for sales per hour only when executed within the Department Productivity-DEMO
Excel workbook. This workbook also contains the Productivity Data Source query, which is a technical prerequisite
for calculating sales per hour.
Reporting is usually done on a weekly basis. Primary target groups for this report: store management, field man-
agement, corporate executives.
5.1.1.2.4 Query: 0RC_C01_ Q0008 Job Productivity - DEMO
Use:
This query is modeled in a similar way to the department productivity query. Common measures of retail productiv-
ity include sales per labor hour and payroll percent. This report allows users to see the variance between the actual
productivity and the schedule for these two very important metrics. This query enables users to review productivity
across time, across the jobs within the store.
Key figure Remarks
Projected Actual Hours Equal total actual hours where these hours exist. If no total actual hours is
available, projected hours equals scheduled hours.
Page 365
jected pay equals scheduled pay
Scheduled Pay Total amount of scheduled pay
per Hour
Difference between projected sales per hour and scheduled sales per hour
Percent
Scheduled Labor Percent Scheduled payroll divided by planned sales
0RC_REGION Region
0RC_STORE Store
Comments:
The query yields complete results for sales per hour only when executed within the Job Productivity-DEMO Excel
workbook. This workbook also contains the Productivity Data Source query, which is a technical prerequisite for
calculating sales per hour.
5.1.1.2.5 Query: 0RC_C01_Q0004 Labor Hour Distribution
Use:
This query demonstrates to a user exactly what percentage of labor hours is being targeted to specific areas within
the store. The report indicates deviations such as one store placing 5% of their hours in a high margin area while
Page 366
another is placing 25% of their hours in this same area. Often companies use certain percentages as standard
rules as to what figures signify a store being run correctly.
Structure(s):
Key figure Remarks
Percent Contribution Number of total hours compared with the number of aggregated hours
Total Hours Total number of hours actually worked, includes all types of hours (regular,
overtime, event hours)
Aggregated Hours Sum of total hours over the furthest right drilldown. In the standard drill-
down this will be total hours added together for all departments.
Scheduled Percent Contribu-
tion
Number of scheduled hours compared with the number of aggregated
scheduled hours
uled hours (regular, overtime, vacation, and so on). Equals the total work-
load plus the number of overstaffed hours minus the number of under-
staffed hours.
Aggregated Scheduled Hours Sum of scheduled hours over the furthest right drilldown. In the standard
drilldown this will be scheduled hours added together for all departments.
0RC_STORE Store
0RC_JOB Job
Comments:
Reporting is usually done on a weekly basis. Primary target groups for this report: field management, business
analysts.
5.1.1.2.6 Query: 0RC_C01_Q0001 ActuaI Labor vs. ScheduIe
Use:
As a rule, retail businesses are evaluated according to their labor performance. This report gives the user an over-
view of all the time ranges and organizational levels and enables them to monitor data at store level by job and by
department. The query compares actual hours and dollars extracted from a time evaluation system against the
schedule for a selected store. Thus, a field level manager can see which store has a labor problem as well as
which area in the store is causing the problem.
Page 367
Structure(s):
Key figure Remarks
Hours vs. Net Scheduled Percentage of total hours actually worked compared with the net scheduled
hours. Net scheduled hours includes only scheduled hours for which corre-
sponding total hours exist.
Pay vs. Net Scheduled Percentage of total pay compared with net scheduled pay. Net scheduled
pay will include only scheduled pay for which corresponding total pay exist.
Average Hourly Rate vs. Net
Scheduled AHR
Percentage of average hourly pay rate actually paid compared with the
scheduled average hourly pay rate. Net scheduled average hourly pay rate
is based on net scheduled hours and net scheduled pay.
Projected vs. Scheduled
Hours
Percentage of projected hours compared with the number of scheduled
hours. Projected hours equal total hours where total hours exist. If no total
hours are available, projected hours equal scheduled hours.
Projected vs. Scheduled Pay Percentage of projected pay compared with scheduled pay. Projected pay
equals total pay where total pay exists. If no total pay is available, pro-
jected pay equals scheduled pay.
Average Hourly Rate
Percentage of projected average hourly pay rate compared with the
scheduled average hourly pay rate. Projected average hourly pay rate is
based on projected hours and projected pay.
Projected Hours Equal total hours where total hours exist. If no total hours are available,
projected hours equal scheduled hours.
Projected Average Hourly
Rate
Projected pay divided by projected hours
Total Hours (hidden) Total number of hours actually worked. Includes all types of hours (regular,
overtime, event hours).
Total Pay (hidden) Total amount of wages actually paid. Includes all types of payment (regu-
lar, overtime, event pay).
Average Hourly Rate (hid-
den)
Total pay divided by total hours
Adjusted Hours (hidden) Auxiliary variable used only to compute the calculated key figures net
scheduled hours and projected hours. It equals zero if actual hours exist or
it equals scheduled hours if no actual hours exist.
Adjusted Pay (hidden) Auxiliary variable used only to compute the calculated key figures net
scheduled pay and projected pay. It equals zero if actual pay exists or it
equals scheduled pay if no actual pay exists.
Scheduled Hours (hidden) Number of hours scheduled that are not unpaid breaks. Includes all sched-
uled hours (regular, overtime, vacation, and so on). Equals the total work-
load plus the number of overstaffed hours minus the number of under-
staffed hours.
Scheduled Pay (hidden) Scheduled pay: the total payroll for the scheduled hours. This includes
regular, overtime, vacation, and so on.
Page 368
Scheduled Average Hourly
Rate (hidden)
Scheduled pay divided by scheduled hours
Net Scheduled Hours (hid-
den)
Scheduled hours minus adjusted hours
Net Scheduled Pay (hidden) Scheduled pay minus adjusted pay
Net Scheduled Average
Hourly Rate (hidden)
Net pay divided by net scheduled hours
0RC_STORE Store
0RC_JOB Job
Comments:
Reporting is usually done on a daily basis and thus gives users response time to correct labor issues without com-
promising customer service by cutting hours at the end of the reporting period. Primary target groups for this report:
store management, field management, corporate executives.
5.1.1.2.7 Query: 0RC_C01_Q0002 Manager's Forecasted Labor
Use:
This report is designed to identify how closely the store manager is adjusting the actual labor usage to the sched-
ule. If there are differences, the scheduling model must change or the manager must do a better job of making
employees work according to the schedule.
Structure(s):
Key figure Remarks
Scheduled vs. Workload
Hours
Percentage of scheduled hours compared with the number of total work-
load hours. Scheduled hours in excess of workload indicate staffing be-
yond budgeting requirements
Hours
Percentage of projected hours compared with the number of scheduled
hours are available, projected hours equal scheduled hours. Projected
hours in excess of scheduled hours may indicate poor schedule enforce-
ment when actual sales are in line with expectations.
Projected vs. Workload
Hours
Percentage of projected hours compared with the number of total workload
hours are available, projected hours equal scheduled hours.
Page 369
Total Workload Sum of filler and flowed workload
Total Hours Total number of hours actually worked. Includes all types of hours (regular,
overtime, event hours).
Projected Hours Projected hours equal total hours where total hours exist. If no total hours
are available, projected hours equal scheduled hours.
0RC_STORE Store
0RC_JOB Job
Comments:
Often the schedule is accurate, but employees punching in before and after their scheduled time cause the labor
budget to be exceeded, especially when this additional time pushes the user into an overtime situation. This
causes store management to build a buffer and schedule fewer hours than recommended by the forecasting algo-
rithm. As a result, customer service can suffer when fewer hours than needed are scheduled for shop floor work.
Reporting is usually done on a weekly basis. Primary target groups for this report: field management, system ad-
ministrators.
5.1.1.2.8 Query: 0RC_C01_Q0006 ScheduIe QuaIity
Use:
This query evaluates the labor schedule. It highlights areas that are seriously overstaffed or understaffed. Over-
staffing means that too many employees are scheduled compared to the expected activity load. Problems resulting
from overstaffing include high payroll costs, employee boredom and employee theft. Understaffing is the opposite
problem and means that a store has too few employees. Problems that result are poor customer service, poor store
appearance and higher customer theft. Since a number of these areas are difficult to measure individually, this
query can indicate where and when these problems are likely to arise.
This query is designed to identify how skilled the store user is in applying the SAP Campbell system or how well
modeled the store is for scheduling. The query shows the relative number of edits and rule violations that store
personnel are making with the software. Edits are manual overrides to the suggested schedule. High levels of edits
indicate the user has a poorly staffed store, it is incorrectly modeled by the SAP Campbell system administrator or
they are simply ignoring the suggestions. Stores with high numbers of edits typically stop using the software after a
while since it simply takes too long to evaluate the schedule and make changes, especially in a big store. These
stores should be provided with additional training, incentive or configuration services as soon as possible to enable
them to use the software correctly.
Page 370
Structure(s):
Key figure Remarks
Schedule Effectiveness The number of effective hours compared with the scheduled hours (minus
the scheduled event hours) plus understaffed hours. This value is used as
a general measure of schedule quality. A rating of zero would indicate the
worst possible schedule where all shifts were scheduled outside the work-
load. A rating of 100 would indicate a perfect schedule with all shifts
scheduled exactly within the workload.
Overstaffing Percentage Percentage of scheduled overstaffed hours compared with the total num-
ber of scheduled hours (minus event hours, for example, spent in training
or meetings). This will indicate whether the schedule effectiveness was
most affected by too many or too few hours.
Understaffing Percentage Percentage of scheduled hours understaffed compared with the total num-
ber of scheduled hours. This will indicate whether the schedule effective-
ness was most affected by too many or too few hours.
Edits per 100 Scheduled
Hours
Number of schedule days that have been manually edited per 100 sched-
uled hours
Rule Violations per 100
Scheduled Hours
Number of employees with rule violations counted towards the employees
primary job per 100 scheduled hours
0RC_STORE Store
0RC_JOB Job
Comments:
Stores with low levels of overstaffing and understaffing are often the best-run stores with the best management
team in charge. The report indicates proper staffing levels for all positions and expertise in using the SAP Campbell
system.
Rule violations occur when a rule set up by the SAP Campbell system administrator or the user is broken. High
numbers of rule violations indicate that the store needs more training, is poorly staffed or is not keeping up with the
weekly maintenance required to make the product work successfully. Stores with high rule violations are also more
likely to violate union or other legal rules set by the governing authority of the store. This can lead to financial pen-
alties as well as high employee turnover situations. In these stores employees contracts tend to be routinely bro-
ken and employees are more likely to leave the store or the company.
Reporting is usually done on a daily basis. Primary target groups for this report: field management, software ad-
ministration.
Page 371
5.1.1.3 InfoCube: 0RT_C02 SaIes Data
Content:
This InfoCube allows users to monitor sales information. This sales performance will directly indicate whether a
store is generating the sales dollars needed to meet the company profitability or market share goals. Data can be
reviewed down to a specific business indicator to identify whether the store is affected by the general business
climate or whether a single product line is showing signs of growth or decline. This InfoCube enables users to ana-
lyze current with previous years planned data. It contains the following sales related information:
- Actual sales
- Planned sales as expected by the corporate organization
- Managers forecasted sales
- System-forecast sales
- Last years sales
The information is presented at the following levels:
- Store
- Business indicator: a more detailed level of sales reporting. In a grocery store, a business indicator would be,
for example, meat sales, produce sales or dairy sales. In a department store, a business indicator would be, for
example, mens, womens or children's sales. With the SAP Campbell system, clients have the ability to set up
any type of business indicator they choose.
InfoSource:
0RC_CI_2 Sales
Characteristics:
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0RC_BUS_ID Business indicator Yes No
0RC_DAYWK
2
Day of week (Monday, Tuesday...) Yes No
0CALWEEK Calendar year and week

2
Since BW, Release 1.2b, does not contain a time characteristic such as 'day of week', 0RC_DAYWK was imple-
mented as a standard characteristic. 0RC_DAYWK is calculated within the update rules using the function module '
'DATE_COMPUTE_DAY'.
Page 372
0FISCPER Fiscal year and period
Key figures:
behavior
0RC_MNGFCST Sales forecast by the store manager 0CURRENCY cumulative
0RC_SYSFCST Sales forecast by the SAP Campbell sys-
tem
0RC_TYSALES Actual sales for the current year 0CURRENCY cumulative
0RC_LYSALES Actual sales for the previous year for the
corresponding fiscal day
0RC_PLSALES Planned sales, forecast by the company 0CURRENCY cumulative
0RC_RPFLG Reporting flag: auxiliary variable indicating
whether actual figures are available for
the selected day and store.

the previous year.

0RC_ADJLYSL Adjusted sales for the previous year: aux-
iliary variable used only to compute the
calculated key figure net last year sales. It
equals zero if actual sales figures exist or
it equals last year sales if no actual sales
exist for the current year.
0RC_ADJSALE Adjusted sales: auxiliary variable used
only to compute the calculated key figures
net plan sales and projected sales. It
it equals planned sales if no actual sales
exist.
Units:
ager
Page 373
cast.
Comments on queries from InfoCube 0RC_C02:
you execute the query.
- Net Plan Sales: includes only planned sales for which corresponding actual sales are available. If no actual
sales are available, net plan sales equals zero. Net plan key figures describe the planned value of only those
stores that reported information for the particular time period. This will allow users to see planned vs. actual
figures only for stores that have both planned and actual figures. For example, if nine stores reported $100 ac-
tual sales for the day and one store was missing, there would be $900 of actual sales. If all ten stores in the
district had planned to sell $100, then the actual vs. planned figures would be 900 divided by 1000 or 90 % of
plan. This indicates results that are below expectation. However, if you compare the actual figures vs. the net
plan (plan for reporting stores) figures, this would be 900/(1000-100) or 900/900 = 100 % of plan. This indicates
good performance. Whenever some stores do not report actual values, the comparison of actual vs. planned
figures will be misleading unless they have been cleaned using net plan or projected values.
- Projected Sales: equals sales where actual sales figures exist. If no actual sales figure is available, projected
sales equals planned sales. Projected key figures are a projection of certain values under the assumption that
all stores reported that information for the particular time period. This will allow users to have a best estimate
for when a single store or group of stores does not report for a specific time period. Usually, the planned or
scheduled data is used as a substitute for actual data to allow this projection. For example, if nine stores re-
ported $100 each for the day and one store did not report, the $75 planned sales may be substituted for the
missing figure to give us a total of $975 projected sales for the day.
The same logic as described for net scheduled hours is implemented for Net Last Year Hours. This includes only
those previous years hours for which corresponding actual hours exist for the current year.
Page 374
5.1.1.3.1 Query: 0RC_C02_Q0002 Key Business Driver
Use:
Clients use sales and non-sales data to forecast their business. The non-sales data is typically known as volume or
business drivers. In most cases, users of the SAP Campbell system define customer count as the key business
driver. This report captures how the business driver is performing against budget and against the previous year.
When scheduling it is very important to use a combination of sales and non-sales drivers. If it is known that a gro-
cery store is selling $ 300 in a quarter hour, this will give an indication of the staffing level. That same grocery store
would schedule the registers very differently if it had one customer buying $ 300 worth of food or 150 customers
buying a single cup of coffee at a price of one dollar.
The key configuration element required in the SAP Campbell system set-up is that this volume indicator must also
be imported as a business indicator and set up as a non-sales indicator in the store master data.
Structure(s):
Key figure Remarks
Sales vs. Net Plan Percentage of actual sales compared with net planned sales
Sales Net Plan Difference between actual sales and the net planned sales
Sales Amount of sales
Net Plan Sales Amount of net planned sales. Includes only planned sales for which corre-
sponding actual sales figures exist.
Adjusted Sales Adjusted sales of the previous year: auxiliary variable used only to compute
the calculated key figure net last year sales. It equals zero if actual sales
figures exist or it equals last year's sales if no actual sales exist for the
current year.
Projected Sales vs. Plan Percentage of projected sales compared with planned sales
Projected Sales Plan Difference between projected sales and planned sales. If no actual sales is
available, projected sales equals planned sales.
Planned Sales Amount of planned sales, forecast by the company
0RC_STORE Store
Page 375
Comments:
This report is crucial for business analysts as well as for the SAP Campbell implementation managers to make sure
the stores are properly modeled for staffing.
Reporting is usually done on a daily basis. Primary target groups for this report: all levels of management; software
administration; business analysts.
Despite the key figures listing data as sales, the key volume drivers may not necessarily be sales data. The term
sales is simply a remainder of the information being imported as a business indicator of the SAP Campbell sys-
tem. For example, although the name of the volume driver may refer to currency, it can still be a non-sales volume
driver.
5.1.1.3.2 Query: 0RC_C02_Q0004 Manager's Forecasted SaIes
Use:
This query is used to verify how the SAP Campbell system and the manager using this software are performing
their forecasting activity. To write an optimal schedule, the SAP Campbell system must receive as input an accu-
rate forecast of the business expected in the upcoming period. The software will provide a forecast and the man-
ager can change the forecast figure. This query allows upper management to review how the stores are modifying
the forecast and how the SAP Campbell system is forecasting. By reviewing this performance, corporate manage-
ment will be able to evaluate the managers understanding of store business properly and to provide additional
training to users making incorrect changes to the system.
Structure(s):
Key figure Remarks
Manager. vs. Projected Sales Percentage of sales forecast by the store manager compared with the
projected sales.
Manager. vs. Planned Sales Percentage of sales forecast by the store manager compared with the
projected sales
Manager. vs. System Sales Percentage of sales forecast by the store manager compared with the
sales forecast by the system.
System vs. Projected Sales Percentage of system-forecast sales compared with the planned sales
Manager's Forecast Sales forecast by the store manager
System Forecast System-generated sales forecast
Adjusted Sales (hidden) Adjusted sales of the previous year: auxiliary variable used only to compute
current year.
Page 376
0RC_STORE Store
Comments:
Since the software cannot have all the knowledge that a store manager has about local activities, the override ca-
pability is intended to make the system more accurate. For example, if the road in front of the store is being paved
this week, traffic and sales will be down. However, a forecasting algorithm based on trends could not forecast this
possibility and will tend to over-forecast for the week. A manager is expected to modify the forecast appropriately.
Reporting is usually done on a weekly basis. Primary target groups for this report: field management; software ad-
ministration.
5.1.1.3.3 Query: 0RC_C02_Q0005 Productivity Data Source
Use:
This query serves a technical purpose only. The query is not displayed in the SAP Business Explorer Browser and
is not intended for operational customer use.
Structure(s):
Key figure Remarks
0RC_REGION Region
0RC_STORE Store
Page 377
5.1.1.3.4 Query: 0RC_C02_Q0003 SaIes vs. Last Year
Use:
This year-by-year comparison is a key measurement of retail company performance measures. The same store or
comparable store reporting against the preceding year is a key figure closely watched by the stock market and is
widely reported in the financial media. BW reports on these figures by business indicator for all levels of the com-
pany.
Structure(s):
Key figure Remarks
Sales vs. Net Last Year Percentage of actual sales compared with net sales in the previous year
Net Last Year's Sales Amount of net sales in the previous year. Includes only these previous
year's sales for which corresponding actual sales for the current year exist.
current year.
Projected Sales vs. Last Year Percentage of projected sales compared with last year's sales
Last Year's Sales Amount of sales in the previous year
Adjusted Last Year's Sales
(hidden)
Adjusted sales of the previous year: auxiliary variable used only to com-
pute the calculated key figure net last year sales. It equals zero if actual
sales figures exist or it equals last year's sales if no actual sales exist for
the current year.
0RC_STORE Store
Comments:
Reporting is usually done on a weekly basis. Primary target groups for this report: store and field management,
corporate executives.
Page 378
5.1.1.3.5 Query: 0RC_C02_Q0001 SaIes vs. PIan
Use:
This query is designed to show how the retail store, district, region and company are performing according to the
predetermined sales plan by day. The query shows the raw figures, variance and percentage difference between
the key figures. It enables the user to analyze key figures at all levels of time reporting as well as at the business
indicator level.
Structure(s):
Key figure Remarks
Sales vs. Net Plan Percentage of actual sales compared with the net plan sales
Sales Net Plan Difference between actual sales and the net plan sales
Net Plan Sales Amount of net planned sales. Includes only planned sales for which corre-
sponding actual sales figures exist.
figures exist or it equals last years sales if no actual sales exist for the
current year.
Projected Sales vs. Plan Percentage of projected sales compared with the planned sales. If no ac-
tual sales is available, projected sales equals planned sales.
Projected Sales Plan Difference between projected sales and planned sales. If no actual sales is
available, projected sales equals planned sales.
0RC_STORE Store
Comments:
Reporting is usually done on a daily basis. Primary target groups for this report: store management; field manage-
ment; corporate executives.
Page 379
5.1.1.4 InfoCube: 0RC_C03 OperationaI InfoCube
Content:
This InfoCube combines sales and labor-related information. Based on this set of information it is possible to model
calculated key figures such as Sales per (Labor) Hour or Labor Percent (percentage of labor cost compared with
sales) which combine sales and labor information and which are key indicators in the retail industry.
Sales information is presented at the following level:
- Store
- Business indicator: a more detailed level of sales reporting. In a grocery store, a business indicator would be,
for example, meat sales, produce or dairy sales. In a department store, a business indicator would be, for ex-
ample, mens, womens or childrens sales. With the SAP Campbell system, clients can set up any type of
business indicator they choose.
Labor information is presented at the following level:
- Store
- Job: each employee can be assigned a number of different jobs, with one of them defined as his primary job.
All data stored within the SAP Campbell system is aggregated in BW at job level.
InfoSource:
0RT_RC: SAP Campbell Integration
Characteristics:
ute avaiIabIe?
ExternaI hierarchy
avaiIabIe?
0RC_BUS_ID Business indicator Yes No
0RC_JOB Job Yes No
0RC_ DAYWK
3
Day of week (Monday, Tuesday...) Yes No
0CALWEEK Calendar week
0FISCPER Fiscal period / year

3
Since BW, Release 1.2b, does not contain a time characteristic such as 'day of week', 0RC_DAYWK was imple-
mented as a standard characteristic. 0RC_DAYWK is calculated within the update rules using the function module '
'DATE_COMPUTE_DAY'.
Page 380
Key figures:
behavior
0RC_TOT_WL Total workload: the total number of fore-
cast hours. This is the sum of flowed and
filler workload.
0HOURS cumulative
0RC_FLOW_WL Flowed workload: workload dynamically
driven by revenue, customer count or any
other variable flowed task defined in the
SAP Campbell system. Includes the
static workload.
0HOURS cumulative
0RC_FILL_WL Filler workload: the fixed and variable
filler hours allocated to the workload. In
contrast to static workload that has to be
scheduled for certain times (for example,
9 a.m. to 10 a.m.), filler workload refers to
non-selling tasks that can be scheduled
variably within certain time segments (for
example, in the morning). As a rule, filler
workload fills the gaps between workload
peaks.
0HOURS cumulative
0RC_STAT_WL Static workload: work manually defined
by the user. It is constant and independ-
ent of revenue, customer count or any
business indicator or task defined in the
SAP Campbell system (for example, the
person who unlocks the store).
0HOURS cumulative
0RC_SYSFCST Sales forecast by the system 0CURRENCY cumulative
0RC_OVRSTFF Overstaffing: the number of hours in which
the total workload is smaller than the
number of people scheduled and not on
an unpaid break
0HOURS cumulative
0RC_UNDSTFF Understaffing: the number of hours in
which the total workload is greater than
the number of people scheduled and not
on an unpaid break
0HOURS cumulative
0RC_EFFHRS Effective hours: the scheduled hours mi-
nus overstaffed hours minus breaks. The
values will be zero for events (for exam-
ple, training or meetings) because these
are not scheduled. From the perspective
of the SAP Campbell system, effective
hours are scheduled hours that match the
workload hours. They are a general
measure of schedule quality.
0HOURS cumulative
Page 381
0RC_NEFFHRS Non-effective hours: the sum of over-
staffing and understaffing for the day.
The values will be zero for events (for
example, training or meetings), fixed shift
and temporary fixed shift job types, be-
cause these are not scheduled. Non-
effective hours could, for example, be
spent working on the shop floor and be
paid while the SAP Campbell system cal-
culated no corresponding demand.
0HOURS cumulative
0RC_COREAFT Core afternoon hours: the number of
hours of core coverage as part of the
workload for the afternoon segment. Core
coverage means that employees with a
particular job-specific minimum skill level
must be scheduled.
0HOURS cumulative
0RC_COREEVN Core evening hours: the number of hours
for the evening segment. Core coverage
scheduled.
0HOURS cumulative
0RC_COREMRN Core morning hours: the number of hours
for the morning segment. Core coverage
scheduled.
0HOURS cumulative
0RC_PAIDBR Paid breaks: the number of hours of
scheduled paid breaks.
0HOURS cumulative
0RC_NPAIDBR Unpaid breaks: the number of hours of
scheduled unpaid breaks.
0HOURS cumulative
0RC_MANEDIT Manual edits: manual changes to the
system-generated staffing schedule. The
number of scheduled days (shifts) that
have been manually edited for every em-
ployee. Edits are attributed to each em-
ployees primary job.
0HOURS cumulative
0RC_RULVIOL Number of employees with violations of
scheduling work rules assigned to the
primary job
cumulative
0RC_SCDHRS Scheduled hours: total number of sched-
uled hours that are not unpaid breaks.
This includes all hours scheduled (regular,
overtime, vacation, and so on).
0HOURS cumulative
0RC_SCDEHRS Scheduled event hours: this key figure is
the sum of all hours that employees with
the selected job as their primary job spend
in events (for example, training or meet-
ings).
0HOURS cumulative
Page 382
0RC_SCDOHRS Scheduled overtime hours: the number of
hours that will be paid at a higher rate (at
a multiple higher than one), regardless of
the reason.
0HOURS cumulative
0RC_SCDPAY Scheduled pay: the total payroll for the
scheduled hours. This includes regular,
overtime, vacation, and so on.
0HOURS cumulative
0RC_SCDEPAY Scheduled event pay: the total payroll for
the scheduled event hours, calculated
from scheduled event hours.
0HOURS cumulative
0RC_ACTRHRS Actual regular hours: actual (punched)
paid non-overtime hours.
0HOURS cumulative
0RC_ACTOHRS Actual overtime hours: actual paid over-
time hours.
0HOURS cumulative
0RC_ACTEHRS Actual event hours: actual hours spent in
an event. These hours are assigned to the
employees primary job.
0HOURS cumulative
0RC_ACTPHRS Actual productive hours: within the SAP
Campbell system, hours can be labeled as
productive (for example, regular hours) or
non-productive (for example, hours spent
on vacation). Typically productive hours
are spent in direct support of the stores
operations.
0HOURS cumulative
0RC_ACTNHRS Actual non-productive hours: within the
SAP Campbell system, these are hours
that can be labeled as productive (for
example, regular hours) or non-productive
(for example, hours spent on vacation).
Typically, non-productive hours are not
spent in direct support of the stores op-
erations.
0HOURS cumulative
0RC_ACTRPAY Actual regular pay: total payroll for the
actual regular hours as calculated by the
0HOURS cumulative
0RC_ACTOPAY Actual overtime pay: total payroll for the
actual overtime hours as calculated by the
0HOURS cumulative
0RC_ACTEPAY Actual event pay: the pay for the actual
event hours
0HOURS cumulative
0RC_TYSALES Actual sales of the current year 0CURRENCY cumulative
0RC_RPFLG Reporting flag: auxiliary variable indicat-
ing whether actual figures are available
for the selected day and store.

Page 383
the previous year.

0RC_ADJLYSL Adjusted sales of the previous year: aux-
iliary variable used only to compute the
calculated key figure net last year sales. It
it equals last years sales if no actual sales
exist for the current year.
0RC_ADJHOUR Adjusted hours: auxiliary variable used
net scheduled hours and projected hours.
It equals zero if actual hours exist or it
equals scheduled hours if no actual hours
exist.
0HOURS cumulative
0RC_ADJPAY Adjusted pay: auxiliary variable used only
to compute the calculated key figures net
scheduled pay and projected pay. It
equals zero if actual pay figures exists or
it equals scheduled pay if no actual pay
exists.
0RC_ADJSALE Adjusted sales: auxiliary variable used
net plan sales and projected sales. It
it equals planned sales if no actual sales
exist.
Units:
0UNIT Unit of measurement UNIT
ager
Page 384
cast.
The operational InfoCube does not allow you to drill down beyond the store level. All key figures are always dis-
played at store level due to a technical restriction.
Comments on queries from InfoCube 0RC_C03
you run the query.
- Net Plan or Net Scheduled key figures describe the planned value of only those stores that reported informa-
tion for the particular time period. This will allow users to see only planned vs. actual figures for stores that
have both planned and actual figures. For example, if nine stores reported $ 100 actual sales for the day and
one store was missing, there would be $ 900 of Actual Sales. If all ten stores in the district had planned to sell $
100, the actual vs. planned figures would be 900 divided by 1000 or 90 % of plan. This indicates results that
are below expectation. However, if you compare the actual figures vs. the net plan (plan for reporting stores)
this would be 900/(1000-100) or 900/900 = 100 % of plan. This indicates good performance. Whenever some
stores do not report actual values, the comparison of actual vs. planned numbers will be misleading unless
they have been cleaned by using net plan or projected values.
- Projected key figures are a projection of certain values under the assumption that all stores reported that infor-
mation for the particular time period. This will allow users to have a best estimate for when a single store or
group of stores does not report for a specific time period. Usually, the planned or scheduled data is used as a
substitute for actual data to allow this projection. For example, if nine stores reported $ 100 for the day and one
store did not report the $ 75 planned sales may be substituted for the missing figure to give us a total of $ 975
projected sales for the day.
5.1.1.4.1 Query: 0RC_C03_Q0005 Reporting Stores
Use:
It will be rare that all stores successfully deliver their daily information to the BW system every day. Transmission
problems, user errors and simple timing issues may prevent this. When users interpret the query results, they must
know how close to complete the data is that provided the basis for the results. For stores that did not upload their
data, this query shows the forecast sales values. This allows users to simply add the missing numbers to see what
a complete reporting would look like.
Page 385
Key figure Remarks
Planned Sales, Weighted
Average Reporting
This key figure will give the user an estimate of the percentage of stores
reporting, calculated not by number, but by total planned sales. This will
give you a weighted average of the amount of planned sales dollars of
stores that reported. For example, if you know your stores reported $
10000 yesterday and were told that 6 out of 10 reported, you would wonder
if your missing stores were large or small stores and how complete the $
10000 was. However, if 6/10 reported and that this was made up of stores
that were supposed to make up 99% of the planned sales, you would have
a much more accurate understanding of your final sales figures.
Number of Reporting Stores Number of stores that uploaded actual sales
Number of NonReporting
Stores
Number of stores that did not upload actual sales
Reporting Flag (hidden) Auxiliary variable indicating whether actual figures are available for the
selected day and store. This has to be considered especially for aggre-
gated key figures, since they vary considerably if one or more stores does
not upload actual figures.
0RC_REGION Region
0RC_BUS_ID Business Indicator
Comments:
Users will not be making critical business decisions if only 30% of the stores reported the previous night. Seeing
the number of stores specifically which stores did not transmit gives users the necessary degree of confidence
in reviewing the numbers.
Reporting is usually done on a daily basis. Primary target groups for this report: field management, corporate ex-
ecutives, system administrators.
5.1.1.4.2 Query: 0RC_C03_Q0001 Store Operations Summary
Use:
This query allows managers one-stop shopping for the key sales and labor metrics for a defined time period as it
shows the principle key figures at a glance. The goal of placing all these key figures in one report is to save the
user from having to look at five queries to find out whether everything is in order. Certain limitations require us to
keep the reporting at the total store level. If the user wants more detailed results, they can use the other sales and
labor reports to find out what is specifically causing the problem.
Page 386
Key figure Remarks
Total Store Projected Sales Equals sales where total store sales exist. If no total store sales is avail-
able, projected sales equals total store planned sales.
Projected Actual Hours Equal total hours where total actual hours exist. If no total hours is avail-
able, projected hours equals scheduled hours.
Rate
Projected Labor Percent Projected pay divided by projected sales
Projected Sales Per Hour Projected sales divided by projected hours
Total Store Sales Total amount of store sales
Total Hours Total number of hours actually worked, includes all types of hours (regular,
overtime, event hours)
Total Pay Total amount of wages
Average Hourly Rate Total amount of wages divided by the total number of worked hours
Store Labor Percent Payroll divided by total store sales
Store Sales Per Hour Total store sales divided by total hours
0RC_STORE Store
0RC_DEPART Department
0RC_JOB Job
Comments:
ecutives.
Page 387
5.1.1.4.3 Query: 0RC_C03_Q0002 Store Operations Summary vs. PIan
Use:
This query is designed for the same purpose as the store operations summary. It will not, however, just give the
user the raw numbers but, more importantly, will show how these numbers correspond to plan. Ideally all the num-
bers should be in one report. The sheer volume of information is not appealing to most users, however, and the
reports have therefore been split.
Key figure Remarks
Projected vs. Store Planned
Sales
Percentage of total store projected store sales compared with total store
planned sales. Projected sales equals sales where actual sales figures
exist. If no actual sales is available, projected sales equals planned sales.
Store Hours
Percentage of hours projected to be worked compared with scheduled
hours in the store
Store Pay
Percentage of wages projected to be paid in the store compared with
planned store wages
Average Hourly Rate
Percentage of projected average hourly pay rate actually paid in the store
compared with the scheduled average hourly pay rate
Total Store Projected Sales Projected sales for the business indicator marked as total business in the
BW master data
Total Store Planned Sales Amount of planned store sales, restricted key figure
Projected Actual Hours Equals total hours where total hours exists. If no total hours is available,
projected actual hours equals scheduled hours.
Scheduled Hours Total number of scheduled hours that are not unpaid breaks. This includes
all hours scheduled (regular, overtime, vacation, and so on).
Scheduled Pay Amount of scheduled wages
Rate
Rate
0RC_STORE Store
Page 388
0RC_JOB Job
Comments:
ecutives.
5.1.1.4.4 Query: 0RC_C03_Q0003 Store Operations Summary, Future Week
Use:
This report is also designed for one-stop shopping and provides all major key figures at one glance. However, it
adds the schedule information to the query. This allows upper management to see how next week will end, before
it begins. They now have a chance to be proactive in solving problems, not just reactive. By running this one report,
field management can essentially run the entire chain with significant impact on sales, labor, customer service,
employee morale, store appearance, labor contract violations, product usage of the SAP Campbell system, profit-
ability and loss prevention.
Key figure Remarks
Manager vs. Store Planned
Sales
Percentage of total store sales forecast by the store manager compared
with total store planned sales
Total Store Manager's Sales Amount of sales forecast by the store manager
Total Store Planned Sales Amount of planned store sales, forecast by the company
Scheduled Hours vs. Store
Workload
Percentage of scheduled hours compared with the workload
Scheduled Hours Total number of scheduled hours that are not unpaid breaks. This includes
all hours scheduled (regular, overtime, vacation, and so on).
Total Workload Total amount of workload
Scheduled Pay Amount of scheduled wages
Rate
Edits per 100 Scheduled
Hours
Ratio of manually editing the scheduling data generated by the SAP
Campbell system per one hundred scheduled hours
Rule Violations per 100
Scheduled Hours
Ratio of rule violations committed per one hundred scheduled hours
Page 389
0RC_STORE Store
0RC_JOB Job
Comments:
This may be the most powerful report in the system. Many clients have flash sales data and fewer have flash labor.
However, virtually no client has future week sales, labor and coverage information.
Reporting is usually done on a weekly basis. Primary target groups for this report: field management, corporate
executives.
5.1.1.4.5 Query: 0RC_C03_Q0004 Store Productivity
Use:
Common measures of retail productivity include sales per labor hour and payroll percent. This report allows users
to see the difference between the actual productivity and the plan for these two very important metrics. This query
enables users to review this across time, across the company and across jobs and departments within the store.
Structure(s):
Key figure Remarks
per Hour
Difference between projected store sales per hour and scheduled store
sales per hour
Percent
Scheduled Labor Percent Scheduled payroll divided by manager's forecast sales
Projected Sales (hidden) Equals sales where actual sales figures exist. If no actual sales is avail-
Projected Actual Hours (hid-
den)
Equals total hours where total hours exists. If no total hours is available,
projected actual hours equals scheduled hours.
Page 390
Projected Pay (hidden) Equals total pay where total pay exists. If no total pay is available, pro-
Total Store Managers Sales
(hidden)
Amount of managers forecast sales
Scheduled Hours (hidden) Total number of scheduled hours that are not unpaid breaks. This includes
all hours scheduled (regular, overtime, vacation, and so on). Restricted key
figure
Scheduled Pay (hidden) Total amount of scheduled wages, restricted key figure
Adjusted Sales (hidden) Auxiliary variable used only to compute the calculated key figures net plan
sales and projected sales. It equals zero if actual sales figures exist or it
equals planned sales if no actual sales exist. The sum of adjusted sales
allows you to determine the amount of dollars missing from the non-
reporting stores.
Adjusted Hours (hidden) Adjusted hours: auxiliary variable used only to compute the calculated key
figures net scheduled hours and projected hours. It equals zero if actual
hours exist or it equals scheduled hours if no actual sales exist.
Adjusted Pay (hidden) Adjusted pay: auxiliary variable used only to compute the calculated key
figures net scheduled pay and projected pay. It equals zero if actual pay
exists or it equals scheduled pay if no actual pay exists.
Total Store Sales (hidden) Amount of sales in the store, restricted key figure
Total Hours (hidden) Total number of hours actually worked, includes all types of hours (regular,
overtime, event hours), restricted key figure
Total Pay (hidden) Total amount of wages, restricted key figure
0RC_STORE Store
Comments:
If stores fall below the level of productivity, it often means that their largest controllable cost, labor, is out of control.
This could be the result of special circumstances at the store, but often is attributed to poor management. By giving
upper management an insight into which stores (which area) missed their numbers, they can quickly address the
problem before it spirals further out of control.
Page 391
5.2 ACNieIsen USA
5.2.1 InfoCube: 0DSLC_C1, SpeciaI Laundry Care (SLC) Market
Data
Content:
This InfoCube is a Remote InfoCube. It contains no real data. It is used to access Syndicated Data out of a demo
data base from ACNielsen US. When a query is executed, the Data Manager of SAP BW requests the data directly
from the Source System (ACNIELSEN) to retrieve the appropriate data. The demo database is a ACNielsen data-
base for special laundry care category. It contains standard key figures commonly used by consumer products
companies.
InfoSource:
This InfoCube is not updated with an InfoSource, it is connected with an external System.
Characteristics:
ExternaI hierarchy
avaiIabIe?
0DSLC_CT ACN-US SLC Category No No
0DSLC_BT ACN-US SLC Brand No No
0DSLC_IT ACN-US SLC Industry Subtotal No No
0DSLC_UT ACN-US SLC UPC / EAN No No
0DSLCMKT ACN-US SLC Market No Yes
0DSLCPER ACN-US SLC Period No No
0DSLCPRD ACN-US SLC Product Yes No
0CALYEAR Calendar Year (Dummy Period, see 0DSLCPER)
Key Figures:
InfoObject Description Type Aggregation
behavior
0DSLCSU SALES UNITS Integer non-additive
0DSLCSUE SALES UNITS EQU - OUNCE BASIS Float additive
0DSLCSD SALES DOLLARS Amount additive
0DSLCPACV %ACV (% STORES SELLING) Float non-additive
0DSLCSACV ACV SELLING $(000)/STR Amount non-additive
0DSLCACV MARKET ACV $(000)/STR Amount non-additive
Page 392
0DSLCSPMU SALES PER MILL/STR(UNITS) Integer non-additive
0DSLCSPME SALES PER MILL/STR(EQU) - OUNCE BASIS Float additive
0DSLCSPMD SALES PER MILL/STR($) Amount additive
0DSLCBU TOTAL BASELINE-UNITS Integer non-additive
0DSLCBE TOTAL BASELINE-EQU - OUNCE BASIS Float additive
0DSLCBD TOTAL BASELINE-DOLLARS Amount additive
0DSLCNPU NO PROMO UNITS Integer non-additive
0DSLCNPE NO PROMO EQU - OUNCE BASIS Float additive
0DSLCNPD NO PROMO $ Amount additive
0DSLCAPU ANY PROMO UNITS Integer non-additive
0DSLCAPE ANY PROMO EQU - OUNCE BASIS Float additive
0DSLCAPD ANY PROMO $ Amount additive
0DSLCFU ANY FEAT W/O DISP UNITS Integer non-additive
0DSLCFE ANY FEAT W/O DISP EQU - OUNCE BASIS Float additive
0DSLCFD ANY FEAT W/O DISP $ Amount additive
0DSLCDU ANY DISP W/O FEAT UNITS Integer non-additive
0DSLCDE ANY DISP W/O FEAT EQU - OUNCE BASIS Float additive
0DSLCDD ANY DISP W/O FEAT $ Amount additive
0DSLCFDU ANY FEAT AND DISP UNITS Integer non-additive
0DSLCFDE ANY FEAT AND DISP EQU - OUNCE BASIS Float additive
0DSLCFDD ANY FEAT AND DISP $ Amount additive
0DSLCPDU PRICE DECR UNITS Integer non-additive
0DSLCPDE PRICE DECR EQU - OUNCE BASIS Float additive
0DSLCPDD PRICE DECR $ Amount additive
0DSLCPDPA PRICE DECR %ACV/STR Float non-additive
0DSLCPDBU PRICE DECR BU Integer non-additive
0DSLCPDBE PRICE DECR BEQU - OUNCE BASIS Float additive
0DSLCPDBD PRICE DECR B$ Amount additive
Units:
Nielsen data are read into the BW as plain numbers without any dimension. The amounts are fixed to the US-
dollar.
5.2.1.1 Query: 0DSLC_C1_Q01: Market Performance
CoIumns: Structure:
Key figure Remarks
0DSLCSU Sales Dollar
0DSCLAPD Any Promo $
Page 393
0DSLCFDD Any Feature and Display
0DSLCPDD Price Descrease $
0DSLCPACV % ACV (Store Selling)
0DSLC_BT ACN-US SLC Brand
0DSLCPER ACN-US SLC Period
Row:
0DSLCMKT ACN-US SLC Market
5.2.1.2 Query: 0DSLC_C1_Q02: Category Performance
CoIumns: Structure:
Key figure Remarks
CoIumns: Characteristics:
Row:
Page 394
5.2.1.3 Query: 0DSLC_C1_Q04: PromotionaI Performance
CoIumns: Structure:
Key figure Remarks
0DSLCAPD Any Promo $
0DSLCPDD Price Decrease $
Row:
5.2.1.4 Query: 0DSLC_C1_Q05: Competitive Fact-Sheet
CoIumns: Structure:
Key figure Remarks
0DSCLAPD Any Promo $
0DSLCFDD Any Feature and Display
0DSLCPDD Price Descrease $
0DSLCPACV % ACV (Store Selling)
Page 395
Row:

Info Cubes

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Info Cubes

Загружено:

Авторское право:

Доступные форматы

Business Content

December previous year

December previous year

Restricted Key Figures

Вам также может понравиться