AC620 - Exexutive information system - Setting up the sysytem.pdf

8/12/2019 AC620 - Exexutive information system - Setting up the sysytem.pdf

http://slidepdf.com/reader/full/ac620-exexutive-information-system-setting-up-the-sysytempdf 1/138

© SAP AG

R

© SAP AG

A C 620 A C 620

Executive Info rm ation Sys tem(EIS) 2 - Setti ng u p th e Sys temExecut iveExecut ive Info rm at ion SystemInfo rm at ion System(EIS) 2 -(EIS) 2 - Set t ingSett ing u pu p thethe SystemSystem

R/3 Release 4.0A Date: October 1998 Materialnummer: 5002 4434



© SAP AG

R

Copyr igh t

Copy right 1999 SAP AG. All r ights reserved.

Neither this t ra ining m anual nor any p art thereof m aybe copied or reprodu ced in any form or b y any means ,or t ranslated into another langu age, witho ut the pr ior cons ent of SAP AG. The inform ation c onta ined in th i sdocu ment i s sub jec t to ch ange and supp lementwi thout p r ior no t ice.

A ll r ig h ts res er v ed .

Trademarks SAP and the SAP logo are registered trademarks of SAP AG. MS-DOS and EXCEL are registered trademarks of Microsoft. OS/2, CICS, MVS, ACF/VTAM, VSE, AIX, OS/400 and AS/400 are registered trademarks of IBM. X Window System is a registered trademark of MIT University. SINIX, UTM and BS2000 are registered trademarks of Siemens. UNIX is a registered trademark of AT&T. HP-UX is a registered trademark of Hewlett Packard. DECnet, DECstation, DECsystem, VAXstation and VMS are registered trademarks of DEC. Ethernet is a registered trademark of the Xerox Corporation.

ORACLE SQL*net, SQL*+ PRO*C are registered trademarks of the ORACLE Corporation. INFORMIX-OnLine and INFORMIX-ESQL/C are registered trademarks of the INFORMIX

Corporation.



© SAP AG

R

R/3 Int egratio n Mo del

R/3R/3Client/Server

A B A PClient/Server

A B A P

COContro l l ing

COContro l l ing

A A A s se t

A c co u nt in g

A A A s se t

A c co u nt in g

PSProjec tSystem

PSProjectSystem

WFWorkf low

WFWorkf low

ISIndus t ry

Solu t ions

ISIndus t ry

Solu t ions

MMMaterials

Mgmt

MMMaterials

M g m t

HRHuman

Resources

HRHuman

Resources

SDSales &

Dis t r ibut ion

SDSales &

Dis t r ibut ion

PPProduct ion

Planning

PPProduct ion

Planning

QMQualityMgmt

QMQualityMgmt

FIFinancial

A c co un ti n g

FIFinancial

A c co un ti n g

PMPlant

Maintenance

PMPlant

Maintenance

• The SAP R/3 System continues to set new standards for universal standard software. Based on progressive development techniques, the SAP R/3 System allows comprehensive integration of business administration and data processing.

• The SAP R/3 System components are characterized by comprehensive business functions with themost modern technology. The integration of the applications ensures that all the functions aredirectly available in the system and thus in the enterprise.



© SAP AG

R

Enterpr ise Con trol l ing

Financial AccountingEnterprise C ontrollingControlling

Level 1Level 2

A C660 5 daysConsolidationFunctions

A C615 2 daysReporting EIS 1

E C - E I S: Execut ive Informat ion System

E C - C S: Consolid ation

E C - P C A: Prof i t Center Accou nt ing

A C620 2 daysSetting up the SystemEIS 2

Level 3

A C665 3 daysIntegratedConsolidation

A C610 2 daysProfit Center

Ac coun ting

A C0 10 5 daysOverview of Financial

Accountig & Report ing

A C060 3 daysEnterprise C ontrolling

A C205 2 daysIntegrated closing

A C040 5 daysCost Management andControlling

A C220 5 daysFI - SL

A C670 2 daysConsolidations of Investments



© SAP AG

R

Prerequisi tes

Part ic ipants mu st h ave at tended ei ther a Level 1 or Level 2 course on an SAP com ponent

Recommended:

Technical understanding of database structures



© SAP AG

R

Target Au dience

A u d ienc e:Mem bers of a project team

Ad ministrators

Durat ion: 2 days

Notes to the user The training materials are not teach-yourself programs. They complement the course instructor's

explanations. On the sheets, there is space for you to write down additional information.



© SAP AG

R

In t rod uct io n: Con tents

Cours e object ivesGoals

Course content

Cours e overview diagram

Main bu siness sc enario



© SAP AG

R

Cou rse Object ives

This cours e wi l l enable you to :

Understand th e various p oss ible uses of EC-EIS

Set up and cus tom ize the Execut ive Inform ationSystem



© SAP AG

R

Goals

A t the en d o f the co u rs e yo u sh ou ld b e ab le to :

Structure th e database of y our EIS System

Fil l the EIS with d ata thro ugh data t ransfers o f many d i fferen t types and o r ig ins

Create autho rizat ions for yo ur s ystem



© SAP AG

R

Course Content

Unit 1 In t roduct ionUnit 2 Data basisUnit 3 Data trans fer Unit 4 A u th o riza tio ns

Preface

Exercises

Solu t ions

A p p en d ix



© SAP AG

R

Cou rse Overview DiagramUnit 4

Au th oriza t io ns- EIS auth orizationobjec ts

- Definin g EISauthorizations

Unit 3Data transfer - EIS data prov ision- Data transfer pro gram- Transfer proc edures

Unit 2Data basis- Asp ect- Characterist ics- Key figures- Data co llectio n- Plannin g



© SAP AG

R

Main B usin ess Scenar io

Define a con sis tent data basis in yo ur EC-Execut ive Inform ation System

Provide the database tables in you r sys tem withda ta f rom both SAP Sys tems and non-SAPSystems

Create authorizat ions for u sers

You are a member of a project team whose task it is to provide the decision-makers of your companywith up-to-date information on the development of critical success factors. The aim of this project is to construct an information system, that is consistent throughout your

company from both a technical and business point of view. You will use EC-EIS. Your project must take account of the requirements of a wide range of departments:

• A uniform data basis should be used for company reporting.• The reporting process should be supported at all levels.• The information system should supply directors and managers at all levels of your company with the

information they need to manage their area of responsibility.• You should be able to supply the database with data from the operative applications without

requiring extensive programming. You should also be able to include external data in theinformation system and if necessary link it with internal data.



© SAP AG

R

Data Basis - Contents

Structure and definition of aspectsCharacteristics

Master data

Basic key figures

Data entry

Key figures

Basic planning functions



© SAP AG

R

Data Basis: Unit Objectives

In this unit you will learn abou tThe data basis

The structure of an aspect and its datastructures

Different definition options and special typesof aspects

Characteristics, master data and basic keyfigures

Data entry and maintenance of key figures

Basic planning functions



© SAP AG

R

Unit 3Data transfer - EIS data provision- Data transfer programs- Transfer procedures

Data BasisUnit 4

Authorizations- EIS au thorizationobjects

- Defining EISauthorizations

UnitUnit 22Data basisData basis-- AspectAspect-- CharacteristicsCharacteristics -- Key figuresKey figures-- Data entryData entry-- PlanningPlanning



© SAP AG

R

Data Basis: Business Scenario

Define aspects

Create key figures, characteristics andcharacteristic attributes

Maintain m aster data for characteristics

Enter data on aspects

Plan your aspects

Optimize your system performance

Your project team has the task of constructing an executive information system for your companyusing the SAP EC-Executive Information System. When your project team has determined from which data sources or systems future users would like to

have their information requirements met, you can start structuring your data basis. You have to define the database tables which will later include the data and form the basis for reports

which will be called up within EIS. You have several ways of designing your database so that later the information will be used optimally. For data that cannot be collected using standard methods, you can create various types of entry

layouts. From the point of view of business planning you define planning layouts and if necessary, have the

system generate plan data. You use specific techniques to make your future reporting more effective.



© SAP AG

R

EISdatabase

Data Basis

Reportportfolio Reporting

FinancesFinances HumanHuman ResourcesResources StockStock priceprice

Envir.Envir Envir ..

Datacollection/summarization

Operativedata

- - -- - - - - -- - -

CritCrit ..success factorssuccess factors

DB tab.DBDB tabtab .. - - -- - -

Aspects

I-IV I-IV

Drilldownreporting

The data basis forms the basis of the EC-Executive Information System. The EIS data basis is subdivided into various aspects. An aspect encompasses a set of data that is related from a business point of view and a database point

of view. From a technical point of view, an aspect is a database table. The data basis contains both the standard aspects delivered by SAP and the individual aspects you

define to reflect a company’s individual structure. The data structure for an aspect can be created,modified and deleted online in EIS. The description objects in the ABAP Dictionary are created withgeneration techniques.

A significant advantage of the data basis lies in the fact that it can be extended by the addition ofdatabase tables.



© SAP AG

R

Database

TableTable

ScreensScreens

ProgramsPrograms

Aspe

ct

Repository

Structure of an Aspect (Table) - Objects

DictionaryDictionary ListList ofofaspectsaspects

EnvironmentEnvironment

Su bSu b --groupgroup CompanyCompany SalesSales

An aspect is an individual subsection of the summarized business information of a company. Itsubdivides the databasis into independent evaluation areas. An aspect consists of the following objects:

• An SAP table description (ABAP Dictionary definition),• A relational database table for receiving transaction data,• An aspect environment for entering and displaying data,• Routines and modules for master data management.

The data structure of the aspect is defined online by the user. The environment can be derived fromthe structure description and generated automatically.



© SAP AG

R

ChemicalsChemicalsSteelSteel

AspectsAspects

Finances

Personnel

Stock price

Field attributes

Comp.

Subgrp

Pcost

Sales

Field catalogField catalog Master dataMaster data

Sub-group

XY ZXY Z Oil IncOil Inc ..Plastics CorpPlastics Corp ..

Comp-any

AromaticsAromaticsinstall.install.

ToolToolconstructionconstruction

Profitcenter

Relationship: Aspect - Field Catalog - M aster Data

When an aspect is generated, the newly defined fields are updated to a field catalog, which thereforealways contains all the fields from all the aspect data structures. If a field is stored in the field catalog,it can be used in further aspects but no longer changed. In other words, it has the same meaningthroughout EIS. The field catalog is therefore aspect-independent.

The field catalog identifies a field as an independent object in EIS with a unique use in all aspects. Itcontains attributes for the fields which determine how the fields are used in reporting. These attributesare given default values when the aspect is generated and can be maintained by the user inmaintenance views. The field catalog aids integration since it is aspect-independent.

The characteristics of an aspect data structure refer to master data tables, which contain the permittedvalues, texts and possible characteristic attributes for the characteristic. The values can be enteredmanually or via data transfer if they have not already been transferred from feeder systems.



© SAP AG

R

- - -- - - - - -- - - - - -- - - - - -- - -

CharacteristicsCharacteristicsBasicBasic ke yke y

figuresfigures

Aspect s pecificAspect spec ific

Fixed chars

Plan/Plan/ ac tac t .. indicindic ..Fiscal year Fiscal year PeriodPeriodVersionVersion

Aspect spec ificAspect s pecific

Structure of the Aspect - Data Structure

F/year:Value Description1995 F/year 19951996 F/year 1996

Version:Version:VrsVr s .. De scriptionDescription0101 Actual versionActual version02 Plan02 Plan versionversion 1103 Plan03 Plan versionversion 22

Period:Fiscal year variant DescriptionK1 Cal. year, 1 special period

The aspect-data structure consists of fixed characteristics, aspect-specific characteristics and basic keyfigures, which are entered online. Characteristics are keys or classifications (for example, company, customer group, organizational

unit), to which the basic key figures (for example, sales, number of employees, machine hours) refer.The number of characteristics within an aspect is limited only by the confines of the database in termsof the total number of fields.

Each aspect contains the fixed characteristics version, fiscal year, period, and plan/actual indicators,which are automatically included in the aspect when you save the data structure.• The plan/actual indicator separates the planning data from the actual data in the database.• You set the years you require with the fiscal year.• You set the number of possible periods per fiscal year using a fiscal year variant.• The version allows different datasets to be held in parallel. For planning it acts as a planning version

but actual data can also be kept in different versions. In the reports, planning and actual data fromdifferent versions can be compared.

• The characteristic values for the fixed characteristics are maintained in Customizing with theexception of the planned/actual indicators: the characteristic values for these are delivered and donot have to be maintained.



© SAP AG

R

DivisionDivisionMaterialMaterial::

CharacteristicsCharacteristics

RevenueRevenueCM 1CM 1::

BasicBasic key figureskey figures

Fixed charctrsFixed charctrs

- - -

- - -

- - -

- - -

- -

-

- - -

- -

-

- -

-

Field catalogField catalog Master dataMaster data

Insert

ne w fields

Data structureData structure

Create checkCreate check andan d text tablestext tables

Dictionary

Generation of repository objects(generation technique)

Defining an Aspect

VersionPlan/act. indic.Fiscal yearsPeriods

Maintaining the data structure of an aspect is the main task when creating an aspect. The data structureis defined as a table in the ABAP Dictionary. The components of the data structure (or table) areindividual fields which are subdivided into fixed characteristics and aspect-specific characteristics or

basic key figures. You enter characteristics and basic key figures online in a table. You can also use existing fields from

the field catalog. The field catalog contains, in total, the fields of all aspects that have already been defined. The data structure of the aspect and all the objects involved is created or modified in the ABAP

Dictionary using the ‘save’ function. This includes the aspect table itself, required data elements,check and text tables. The new fields are added to the field catalog.

All dictionary objects are activated using the ‘activate’ function. The tables corresponding to theABAP Dictionary description are set up or modified in the database. Only when it is in the ‘active’status can the aspect receive data and be used in the information system.



© SAP AG

R

"View aspect"

M1 ... ... K1 K2M1 ... ... K1 K2

Sales analysis

”Physical aspects"

Finances

M1 M2 ... K1 ... ...

Personnel

M1 M2 ... ... ... K3

Sales

M1 ...M1 ... M3 ...M3 ... K2 ...K2 ...

Special Case: View Aspect

K3K3

A view aspect enables you to evaluate data in more than one table. You can select characteristics and basic key figures from the fields of the aspects concerned. Views of two or more existing aspects cantherefore be defined, without a new database table being created. The data records are handled by thesystem as if they had been read from a single aspect. In other words, the data records are read from allthe aspects involved and combined in a join-operation.

The following prerequisites should be taken into account when designing view aspects:• The aspects concerned must have the same fiscal year variants.• If a key figure has not been selected from the “physical” aspect when the report is being defined, a

database query is not generated.• If a characteristic that has been selected from a report is not available in a “physical” aspect, a

database query will not be generated for this aspect if the characteristic has been committed to acharacteristic value for the whole report. If the characteristic has not been restricted, a databasequery will be generated. The transaction data then appears in the report as “not assigned”, if youdrill down using this characteristic.

• If a basic key figure occurs in several “physical” aspects, it is read from each aspect. This can leadto the key figures being totaled and should be avoided.

• Calculated key figures can be created for view aspects. View aspects should be defined for aspects which contain several similar characteristics and differing basic key figures.



© SAP AG

R

Defining Characteristics/Dictionary References

Activity+

Parameter

Objects:

Ne wNe w definitiondefinition(( typetype ,, lengthlength ,, textstexts ))

D. elem.

Domain

Check tab.

< D.< D. elemelem . >. >

<< DomainDomain >>

<Check<Check tabtab .>.>

DomainDomain(( textstexts ))

<< DomainDomain >>

<Check<Check ta btab .>.>

Tab.Tab. fieldfield

< D.< D. elemelem . >. >

<< DomainDomain >>

< Check< Check tabtab ..>>

Transfer Transfer fromfromfield catalogfield catalog

<----><---->

<< Fixed domain valuesFixed domain values alsoalso possible insteadpossible instead of Checkof Check ta btab .>.>

- - -- - - - - -- - -1. 2. 3. 4. 5.

<----><---->

<----><---->

D. elem.

<< ReferenceReference >>

New object

T27xx

R e f e r e nR e f e r e n cece

D.D. elemelem ..

You define the characteristics of an aspect online in table form when you define the data structure.Each characteristic is clearly identified by its field name. The attributes for the characteristic(description, type and length) can be either entered directly or by assigning a data element or domain.

A data element establishes the business meaning of a field using texts and a reference to a domain. Adomain describes the technical attributes of a field (type and length) and, depending on the definition,limits the permitted values for the characteristic (using a reference to a check table or fixed domainvalues).

Normally, the data element and domain assignment serve as a reference to an existing check table (forexample, the domain COCDE has a reference to the company code table T001).

You define a characteristic in any of the following ways:• Enter field name, description, type and length. A new data element, domain and check table (T27xx)

are generated for the characteristic.• Enter a field name and an assign a data element (the data element determines the domain and

description).• Enter a field name and description and assign a domain (the domain determines the type, length and,

where necessary, value restrictions). A data element is generated by the system.• Copy a characteristic from any ABAP Dictionary table. The data element of the table field is

automatically assigned.• Copy an exiting characteristic from the field catalog.



© SAP AG

R

Properties of Characteristics

Time ref.

Conversion routine

Time ConvR '0001' MATNRMARA

Constant

Original table and field

Field hasa time

dimension

How thecharacteristic

is to bedisplayed

in reporting

Pres.

Presentation

Alpha conv.

for CHAR typecharacteristicsOrigin of thecharacteristic

A constant is assignedto the characteristic

and thus is no longerrelevant for report

A field, which has a time dimension = “X”can be used as a reference field for a basic key figure fortime-based aggregation. The field designates the characteristic as a time dimension (for example, posting date, calendar week).

With “ConvR” the characteristic is assigned the Alpha conversion. The Alpha conversion for fieldswith data type 'CHAR' converts an entry such as ' 01 ' to '0001'.

In the “Presentation” field you enter how the characteristic should be displayed in reporting. By assigning a constant, a characteristic contains the same value in all data records. It is, therefore, no

longer relevant in reporting. It may, however, be required for a compound characteristic. The original table and field specify from which dictionary table or field the characteristic has been

transferred.



© SAP AG

R

Characteristic Attributes

ProductProduct

Absolute basisCM I DB I

group

Productgroup

Distributionchannel

Plant

Customer Customer Customer

groupCustomer

group

The characteristics generated in EIS can be assigned characteristic attributes similar to their properties.There are two types of characteristic attributes: Display attributes:

• Some characteristics serve only to form the hierarchy or to combine and group other characteristicsfor reporting purposes. If the characteristics are generated in EIS, they can be stored as attributesfor other EIS-generated characteristics.

• The advantage of characteristic attributes is that the assignments are stored in the master data insteadof in the transaction data. Any reorganization of the assignments takes effect immediately withoutthe database having to be converted.

• In reporting, characteristic attributes are treated in exactly the same way as the normal aspectcharacteristics.

Attributes for currency/unit fields• These attributes serve as a reference field (specific to the characteristic) for the currency or quantity

unit of a key figure and are stored in the check table of the characteristic. These attributes arealways the same and cannot be maintained. They cannot be evaluated in reporting.



© SAP AG

R

Compound Characteristics 1

400000 Usage o f r aw ma te ria ls410000 Usage o f t rading goods420000 Loan

:410000 Bonds420000 Loan430000 Prepayment s r eceived:

- - -- - - - - -- - -Chart of Chart of acctsaccts G/LG/L accountaccount

GKRGKRGKR

:IKRIKRIKR:

Chart of accounts/

G/L account

Chart of accounts

Some characteristics are dependent on other characteristics, meaning that their values can only beinterpreted in combination with the values of other characteristics. These characteristics are known ascompound characteristics.

From a technical point of view, a compound characteristic is a multilevel key in check and text tables. If, in the example, you choose a G/L account for a report, the chart of accounts must also be a report

characteristic.



© SAP AG

R

Compound Characteristics 2

CountryCountry

Characteristic Compound

RegionRegion

CountryCountry

CountryCountry

CountryCountry

CityCity

RegionRegion

CityCity

RegionRegion

If you have assigned a data element or domain, the compound characteristics are derived from the keyfields of the referenced check table. If you have defined a brand new characteristic, you can define thecompound characteristics yourself.

In the example above, the new characteristic ‘City’ is to be created and compounded with the‘Region’. The characteristic ‘Country’, that is compounded with the ‘Region’, is then automaticallyincluded.

The compound characteristic is transitive (the cities table must also contain the country because theregion is compounded with the country).



© SAP AG

R

Considerations When Designing an Aspect DataStructure

Interplay be tweencharacteristics andbasic key figures

> More data records

> Longer data records

- - -- - -Male/Male/ femalefemale1

Personnel costsPersonnel costsmalemale - - -- - -

11222

- - -- - -

+ +

+

Definition of keyfigures/key figuretrees for basic keyfigures, identical usein reporting

/

Personnel costsPersonnel costsfemalefemale

Personnel costsPersonnel costs

To cover specific information requirements, various possibilities are available when designing aspects. In the above example, the personnel costs in a report are to be broken down by employee gender. Both possibilities (gender as a characteristic or included in key figures) offer the same in terms ofinformation content. The difference lies in the fact that if you include gender in the aspect as acharacteristic, you will have more data records in your database table. You can navigate using thischaracteristic. If you include gender in your key figures, you will have longer data records and youcan use these key figures to calculate further key figures.



© SAP AG

R

Master Data

Product

The master data contains the permitted characteristics and the description texts. When entering ortransferring transaction data, a check is later carried out against this master data. Master data must be maintained manually in EIS if it has not already been transferred from reference

tables or imported into EIS by data transfer. The master data constitutes the values of the characteristics. Appropriate modules are needed for those characteristics created in EC-EIS when transferring the

master data (reading texts for characteristic values using a view). These modules are automaticallygenerated when the characteristics are activated from the system.

Master data hierarchies can be maintained for all characteristics in EIS. The creation of master datahierarchies or reference hierarchies is described in Course AC615.



© SAP AG

R

Option

ActivityAmountAmount

< Currency >

QuantityQuantity

< Unit >

ReferenceReferenceTable fieldTable field

<C>/<U>

Transfer fr.Transfer fr.field catalogfield catalog

<---->

- - -- - - - - -- - -

Defining the Basic Key Figures of an Aspect

SelectionSelection

A basic key figure is a value, for example sales, fixed costs, number of employees. The data on the basic key figures is held in the database of the aspect, differentiated according to the characteristic(sales in fiscal year 1995, period 1, country GER).

Basic key figures are defined by selecting the field (amount or quantity), or copied from a referencetable.

Each basic key figure is identified clearly by the field name. If you select the basic key figures for your aspect later, you can choose any of the basic key figures

from the field catalog. The following are possible when creating basic key figures:

1. Assign a fixed currency or quantity unit to a basic key figure. This value is included in each datarecord.

2. Assignment to an aspect currency or no automatic assignment to a quantity unit (the amounts are posted in the aspect currency, the quantity units have to be assigned per data record.)

3. Create a reference to a table with a currency/unit field.4. Basic key figures of the type “number” are stored without a unit.



© SAP AG

R

Currencies

Am.1Aspect Co.cde

‚001‘ '0004'

Three possible assignmentsof a currency to a basickey figure in SAP-EIS

*1

*2

*3

'*' = Priority

Am.3Am.2

Field catalogAmount 1 > 'DEM'

Company codes'0004' > 'LIT'Aspects

‘001’ > 'SFR'

There are three possible ways of determining in which currency SAP-EIS data is to be stored:• If no other stipulations are laid down for the currency of a basic key figure, the aspect currency

determines in which currency the basic key figure is stored in the aspect.• For each basic key figure you can define in which currency the data is to be saved, regardless of the

aspect. When creating a key figure you define the currency. This has priority over the aspectcurrency.

• It is possible to store values in a certain currency depending on the characteristic value (for example,cost accounting data in controlling area currency). To do this, with a basic key figure you referencethe currency assigned to the characteristic. The currency is then determined from the characteristicvalue. This also has priority over the default currency of the version.



© SAP AG

R

Quantity Units

Qty1... ... Act.type

'0004'

Three possibilities for theassignment of a quantityunit to a basic key figure

Qty2 Qty3 Unit3

'TO'

*1 *3

*2

'*' = Priority

Field catalogQty1 > ‘PCE'

Activity types'FST' > 'H'

A quantity unit can be assigned to a basic key figure in the following ways:• Define the quantity unit for each data record

For each data record, the basic key figure can be posted in any unit.

• Specify quantity unit for basic key figureFor each basic key figure you can specify in which quantity unit the data should be stored. Thequantity unit is specified when the basic key figure is created. This entry applies to all aspects.

• Linking a quantity unit to a characteristic value.As with the currency translation, the quantity units can also come from the values of a referencedcharacteristic. A basic key figure amount is then interpreted with the quantity unit, that isdetermined by the quantity unit of a characteristic.



© SAP AG

R

Further Attributes of a Basic Key Figure

Currency translation Display factor

Decimal places

Key figure group

Aggregation

When maintaining basic key figures you can specify further optional properties:• You can maintain currency translation types, which appear in drilldown reporting as a default value

if “currency conversion” is selected for the basic key figure.• You can assign the basic key figure to a key figure group. When creating reports, the group provides

an overview.• With the “decimal places” property, you set the number of decimal places.• The “display factor” field enables you to display the value of the basic key figure in a different

scale.• The aggregation properties determine how the basic key figures are aggregated in the report with

regard to the characteristics.



© SAP AG

R

Comment tables

Aspects Comment tables Characteristics

When entering data and executing reports, it is possible to enter and display comments on transactiondata. These comments can be stored in SAPScript or be called up from any application on a local PC.Such applications might be the Microsoft Office products, for example.

The comments are saved using a comment table which contains the selected fields of the aspectstructure. It is possible to assign a comment table to one or several aspects. Initially a comment table iscreated and the relevant characteristics selected. An aspect structure has to be defined at the same time.Comments on transaction data, which contain these characteristics for a special key figure, can becreated later.



© SAP AG

R

Maintain/display

Environment

ProgramsPrograms

Master data modules

UpdateUpdate

Read textRead text

ManualManualmaintenancemaintenance

1 North2 West

DictionaryDictionary

Aspect desc ription in

Dictionary

Automatic

generation

Automatic

generation

Entry transaction+

raw data display

Generation of Aspect Environment and Master Data Modules

The aspect environment is derived from the aspect description in the Dictionary and is generatedautomatically. The generation takes place without further interaction by the user. When the aspect environment has been generated, you can start maintaining the master and transaction

data. Certain modules are required to maintain the master data and read texts. These can also be generated

automatically from the description of the fields in the Dictionary.





© SAP AG

R

Data Entry Layout (w/o Lead Columns)

Div. Revenue Unit Sales volume Unit Production var. UnitMotor bikes 2,000.00 DEM 20 pc 100.00 DEMPaints 200,000.00 DEM 30 pc 200.00 DEMLightbulbs 200,000.00 DEM 200 pc 240.00 DEMFood 40,000.00 DEM 70 pc 530.00 DEMElevators 450,000.00 DEM 60 pc 410.00 DEMHigh tech 1,000.00 DEM 10 pc 650.00 DEMService 100,000.00 DEM 100 pc 320.00 DEM

Ac cessories 60 ,000 .00 DE M 10 pc 270.00 DE MVehicles 70,100.00 DEM 20 pc 170.00 DEM

Au to spare s 640,00 0.0 0 DE M 300 pc 36 0.00 DE M Ac cessories 20 0,000.0 0 DE M 200 pc 240.00 DE M AU TO MO BILE S 300,000.0 0 DE M 14 pc 10 3.00 DE M

Total 2,263,100.00 1034 3,593.00

Value type 1 Plan dataFiscal year 1996 F/year 1995Period 1 to 12Company code 1000 IDES AG

Data entry layouts are created with the Report Painter in Customizing. By double-clicking on the field row 1, a row is defined (similar to a form). Then, you create a layout

without lead columns. The key figures are in either the rows or the columns. A unit column is created automatically for each column. For rows or columns, the number format can be determined both in Customizing and in data entry.

Furthermore, rows and columns can be switched to ‘not ready for input’. In data entry with a layout without lead columns, only key figure values and (where necessary) units

are entered. No characteristic values can be entered or changed. With amount key figures the units are not ready for input. However, you can determine an entry

currency for the entire data entry.

With quantity key figures, whose unit is not fixed, the unit must be entered. With quantity key figureswith a fixed unit or a reference unit, the display unit can be converted to the database unit.



© SAP AG

R

Data Entry Layout (with Lead Columns)

Div Region Revenue Unit. Sales volume Unit01 Motor bikes 000001 2,000.00 DEM 20 pc02 Paints 000002 200,000.00 DEM 30 pc03 Lightbulbs 000003 200,000.00 D EM 200 pc04 Food 000004 40,000.00 DEM 70 pc05 E levators 000005 450,000.00 DEM 60 pc06 High Tech 000001 1,000.00 DEM 10 pc07 S ervice 000002 100,000.00 DEM 100 pc08 A ccessories 000003 60,000.00 DEM 10 pc09 Vehicles 000004 70,100.00 DEM 20 pc

10 Auto spares 000005 640,000.00 D EM 300 pc11 Accessories 000001 200,000.00 D EM 200 pc

Total 1,963,100.00 1020

Value type 1 Plan. dataFiscal year 1997 F/year 1996Period 1 to 12Company code 1000 IDES AG

You create a layout with lead columns by double-clicking on the field lead column in the first screenof the Report Painter and establishing a characteristic for this column. In this case, there are no fixedrows - they are established by the characteristic values that the user enters. The key figures appear hereautomatically in the columns.

Up to nine lead columns can be created. Data records can also be deleted in a layout with leadcolumns. At first, deletion is only internal and then during posting, deletions also take place from thedatabase.

Variables can be used for all characteristic values (in rows, columns and general selections). Thisapplies for both types of layout.

If you have selected an interval in your head, you can scroll through all combinations of headercharacteristics, for which transaction data exists.



© SAP AG

R

Derivation

Aspect structure (not derived)

Aspect structure (derived)

Division 01 - 05 'DE'

Sales district Country 000001

Convertsender field

05

05 000001 DE

Set constants

DerivationDerivation rulesrules (( toolboxtoolbox ))

Data entry Data transfer

From Release 3.0D it is possible to define derivations in EIS. Derivation makes it possible to supplement missing characteristic values during manual data entry and

data transfer. The derivation rules are maintained in the same way as the transfer rules of characteristics (set

constants, convert sender fields, transfer sender fields, and so on.) The receiver field is thecharacteristic that is derived (from the values of the sender fields).

The derivation rules are aspect-independent. Entering the aspect during maintenance only serves torestrict the displayed characteristics (as in the master data maintenance).

It is also possible to derive across several levels, for example the product determines the product groupand this in turn determines the division.

An existing value of a characteristic is not overwritten with the derivation. Only those fields thatcontain the initial value are derived.

In the data entry, use ‘Choose characteristics’ to display all characteristics of a data record, includingthose which are derived.



© SAP AG

R

Validation (Plausibility Check in Data Entry andTransfer)

Div Region Revenue Unit Sales volume Unit01 Motor bikes 000001 -2,000.00 D EM 20 pc02 Pumps 000002 200,000.00 DEM 30 pc03 Lightbulbs 000003 10,000,000.00 DEM 200 p c04 V ehicles 000004 2,350,224.00 DEM 70 pc

T Message textE Division 1: revenue must be greater than 0E Combination of div.4 and region 4 invalid

Message output

Layout entry

I Average sales volume smaller than 100W Revenue from cars varies by more than

double that of mo tor bikes

LogsLogs

Singlerecord

validation

Matrixvalidation

Validations serve to filter out obvious errors in the data entry and data transfer. The validations consist of several steps and each step consists of a prerequisite, a check and a message.

The message is given precisely when the prerequisite is fulfilled and the check is not fulfilled. Up to999 steps, which are processed one after the other, are possible per validation.

The following messages are given, depending on the level of seriousness:

• If a message is of type A (Abort) or (E) (Error), nothing can be saved in the data entry, or the datatransfer reports an error and no records are updated.

• If only messages of type W (Warning) or I (Information) appear, records are updated but a log withthe messages of the validation is written.

There are two types of validations:

• Single record validations check each new data record. (for example, the sales revenue must behigher than the costs in each data record)

• Matrix validations check the entire quantity of the records. (for example, the sum of the salesrevenues over all data records is not allowed to fall below a certain value)



© SAP AG

R

Objects for Validation: Relationships

Aspect

Boolean classSingle record

validation

Boolean classMatrix validation

Rule

Validation step

Sing. rec. validation

Matrix validation

Entry layout

Booleanprint out

Prerequisite

Check

Message

Sender program Contains one (maximum)

Contains one or more

Procedure when creating a validation:• Call up transaction. Two Boolean classes are automatically generated for the entered aspect (single

record and matrix validation).• Create validations, each with several steps: Each step consists of a prerequisite (optional), a check

and a message.• Where necessary, create rules: rules contain reusable Boolean statements, and can therefore be

compared with includes in coding. Rules can be used in the prerequisite and in the check of thevalidation, as well as in further rules.

• Activate the validations, in other words assign a matrix and/or single record validations to data entrylayouts and sender programs/structures.

Others:• Validations are aspect-specific, but can be copied between aspects.



© SAP AG

R

Key figure

Description

Key figure formula

Key figure FormulaREV_EMP = SALES / EMPLOYEE

REV_EMP

Revenue per employee

Key Figures

Key figures:• Are formed from the basic key figures of the aspect, predefined key figures and constants.• Are uniquely defined for all aspects.• Can be combined into groups.• Are treated in the same way as basic key figures in reporting.

Unlike basic key figures, the value of a calculated key figure is not saved on the database. A keyfigure is calculated by the system when a report containing this key figure is executed.

Every calculated key figure has a unique name, valid for all aspects. However, each calculated keyfigure is assigned to a specific aspect since it can be broken down into the key figures of an aspect. Ifthe detailed key figures are also available in another aspect, the calculated key figure can also be made

visible in this aspect. You can create derived key figures for a view aspect and use the basic key figures from the relevant

aspects in the formula. The aggregation and display of key figures in reporting can be chosen just as with basic key figures.



© SAP AG

R

Key Figure Aggregation

Product AVG SUM Sales = P * QPrice Quantity

Machine A 10 000 1 10 000

Machine B 11 000 10 110 000

10 500 11 120 000

Hamburg 2 000 000 10 200 000

Munich 520 000 2 260 000

2 520 000 12 210 000Revenue/Employee

Non-aggregation flag = X = Row calculation

Non-aggregation flag = = Column calculation Total sales

Subsidiary Sales Employees Revenue/Employee

The aggregation process of the individual key figures is important for the use of the key figures inreporting. The non-aggregation flag shows how the key figure in the result row of the report should be

calculated. It must be set when the key figure cannot logically be aggregated from the existing lineitems in the report.

Time-based aggregation shows how the key figure should be summarized with respect to time. Fortime-based aggregation, a reference field must be entered (the smallest time unit of the aspect).

Non time-based aggregation shows how a key figure should be summarized over a characteristicwithout a time reference.

A time-based and a non time-based aggregation rule can be maintained for each key figure. !!!Note: Key figures in a report cannot have different time-reference fields.



© SAP AG

R

SAP-EIS: Key Figures

Profit as% of invest.

capital

Profit as% of sales

Turnover ofcapital

SalesSales

Contributionmargin

FixedFixedcostscosts

Net

sales

VariableVariablesales costssales costs

Gross salesGross sales

SalesSalesdeductionsdeductions

SalesSales

Investedcapital

ReceivablesReceivables

InventoriesInventories

CashCash

Currentassets

FixedFixedassetsassets

Profit

You can build up whole key figure trees by reusing existing key figures in other key figure formulas. You can form key figure groups and assign key figures to a key figure group. This key figure group

can then be used when defining a report in order to simplify key figure selection. The grouping of keyfigures into areas such as ‘liquidity’ and ‘cost effectiveness’, and so on, allows a better overview ofkey figure maintenance and reporting.



© SAP AG

R

Planning in the Executive Information System

EISEISEIS

100100

00 100100

Quantity planQuantityQuantity planplan

OrdersOrdersInventoriesInventoriesCapacityCapacity

R1

:

:-

:

R4

........

-------

--------------

ROIROIProfit/Profit/costscosts

EmployeesEmployees / /qualificationsqualifications

Zeit

NonNon --SAP-SAP-

systemssystems R/2R/2Externaldata

Financial budgetFinancial budgetFinancial budget Personnel planPersonnelPersonnel planplan

PullPull

Profitcenter

Equity costs ROI EVA

Yea r Version European Subsidiary

Distrib.key

PCTR1PCTR2PCTR3

10.00 10,000100,000 1

Business master Business master planplan

Planning functionsPlanning functions in EISin EIS

OperationalOperationalbranchesbranches

PlanPlan data sourcesdata sources

From Release 4.0a you can plan directly in EC-EIS. There are both interactive planning functionsonline and automatic functions in the background processing. Using these functions, you can process plan data for any characteristics and key figures of an aspect.

EIS enables you to process plans on an aggregated level. Because of the generic functions in EIS, you can freely choose the planning object. Thus you can

combine cross-application business relationships in one or more plan sections, for example sales plans,aggregated personnel plans, finance plans etc..

You can process these plans further in EIS using planning functions such as seasonal distribution andrevaluation.

EIS supports the transfer of planning data from operational R/3 Systems and non-SAP Systems.





© SAP AG

R

Defining a Planning Layout (1)

Planning Layout

Lead column Key figure columns Attributes

Header - general data selection

© SAP AG

By defining a customized planning layout you can adapt the screen output to the specific requirementsof your company. The exact information which the planner needs for the current planning session isavailable. Layouts, which have been defined for the entry of actual data, can also be used for planning.

The planning layout determines the structure of the screen where you enter the plan data. This coversthe positioning of the fields and their description. The user determines which characteristics and keyfigures are to be planned for which timeframe, by assigning the characteristics and key figures to therows and columns of the layout or the general data selection (header).

Characteristics, which are the same for all planning objects, are defined in the general selections(header block).

The ‘version’ and ‘plan/actual indicator‘ fields are treated as normal characteristics when you definethe layout. Thus you can display a second plan version or actual data, or plan more than one version.

You can enter fixed values or variables for the characteristics in the planning layout. If you entervariables, you will get a system message when planning requesting you to replace the variables.





© SAP AG

R

Planning Online

Copying plan and actual data

Revaluation, seasonal distribution, formula calculation

Flexible currency hand ling

Bottom-up planning

Comm ents on plan data (W ord, Powerpoint, etc.)

R

In EIS the following functions are available for a planning session: You can copy plan or actual data from reference data sets, you can also use several versions together

in a layout. Values can be entered as totals for the selected planning period and be allocated to periods using predefined seasonal distributions.

Formulas for key figures can be evaluated both upstream and downstream. You can revaluate the values following entry of a revaluation percentage (sales + 5% ). By using characteristic value-based currencies, with the planning layout you can plan key figures in

various currencies for a single planning layout. Example: group planning is done in the subsidiary companies in the company code currency. After

this decentralized planning, the individual plan versions are incorporated into the group plan that usesthe group currency. You can supplement additional information to your plan data by using the comment function (for

example, in the MS Word, MS Powerpoint, and SAPscript formats).



© SAP AG

R

Bottom-Up PlanningSB U Cost of

sales

AutoAir

105 + 5 50 + 10

Company Productgroup

01

01

.

10

15

.

Cost ofsales

03

03

5

10

Company

02

02

02

20

5

10

10 + 50

Productgroup

Cost ofsales

30 + 20

Productgroup

35 + 10

Productgroup

Cost ofsales

ProductgroupCompanyCost of

sales

Cost of sales

Cost ofsales

Productgroup

3rd3rd planning stepplanning step :: strategic business unitstrategic business unit

2nd planning step: product group 1 -3

1st planning step: compan y 1-3 for product groups 1-3

At each level of planning you can use interactive online planning and/or automatic planning. Thesystem ensures that the data is consistent on all levels since the data are transferred from the lowerlevels to the upper levels.Example: you wish to plan a P&L account “cost of sales” for companies and product groups. Becauseof the large number of companies, only the most important are planned at the lowest level. Planningfor all other companies will be at the level of the product groups or the strategic business units.

In the first step you plan product groups 1, 2 and 3 for companies 01, 02 and 03. In the second step you plan the cost of sales for all other companies on the product group level by

entering data directly for groups 1, 2 and 3. The system then displays the cost of sales planned in thefirst step that have been added for all groups, and the quantities planned at product group level in steptwo.

In the third step, you reconcile the plan at the level of the strategic business unit. The data is then aggregated automatically.



© SAP AG

R

Plan data

Plan 1998Version 1Division A

Plan data

CopyChange

(Forecast)

Automatic Planning

Plan 1997Version 1Division A

Actual 1997Division ADivision B

Actual data

Automatic planning functions serve to process large volumes of data in a planning run. Thus, at the beginning of a planning period, for example, you can copy the entire previous year’s plan data or theactual data, and then process it further online. You can use these functions either directly or in the

background. The following planning functions are available:• Copying• Seasonal distribution• Revaluation

Additional planning functions such as currency conversion, aggregation and restructuring can becarried out using the standard EC-EIS transfer tools.

Selections and parameters for automatic planning runs can be saved using variants and then scheduledfor background processing.



© SAP AG

R

Automatic Plan Processing (e.g. Copying)

CurrentCurrentsalessales planplan

Businessunit Revenue Sales

quantity

010203

10,00015,00020,000

100,000225,000240,000

Source

Target

or

RR


Businessunit

Revenue Salesquantity

010203

10,00015,00020,000

100,000225,000240,000


Businessunit

Revenue Salesquantity

010203

10,00015,00020,000

100,000225,000240,000

Distribution k eyRevaluationCopy values

Basicsettings:

characteristicskey figuresfunctions

Yea r 1 997Actual data

Year 1997Version 2 plan data

Ye ar 19 98Version 1

For automatic planning, choose a view for reference data by selecting a specification forcharacteristics and key figures. This can be both plan and actual data. Using the planning functions, operations affect the selected dataset. In the simplest case, this might

consist of copying the data into another version or another time period, but could also involve arevaluation or a seasonal distribution.



© SAP AG

R

Update Plan Data: Directly or with Rules

Cust. *

Cust. groupBicycles

Transfer rulesCustomer BikeshopBikeworld

Cust. groupBicycles 100Bicycles 200

Target data

Cust.

*

Cust. group

Bicycles

Customer

--

Cust. group

Bicycles 300

Cust. *

Cust. groupBicycles

Reference dataReference data

Customer BikeshopBikeworld

Customer groupBicyclesBicycles

Revenue100200

Customer BikeshopBikeworld

Cust. groupCycles 100Cycles 200

No transfer rules

Convert (“group”)

Convert (“reassign”)

Selection rulesSelection rules

With automatic planning you can update the generated plan data either directly in the same aspect or,using the transfer rules, you can update it in the same or a different aspect. Using the transfer rules you can execute extensive additional functions. You can carry out currency

translations, restructuring, summarize the data further, or calculate formulas. The diagram above illustrates the following possibilities:

• Direct updating of the data, without changes to the structure.• Grouping data: for example, all customers of the customer group bicycles are aggregated and

assigned to the customer group bicycles .• Reassigning the data: for example, all customers are assigned to another customer group ( cycles ).



© SAP AG

R

Performance

Summ arization levels

Report-reportinterface

Split report

Saved data

Aspect design

VV ??

When a report is executed, transaction data records are read and summarized so that you can navigateusing the characteristics selected when you defined the report. This data is stored in the main memoryand can result in a long response time. There are various way in which you can optimize the responsetime in reporting:

Execute background report and save data: the data in the main memory is saved. Youautomatically receive the data from the last save. It is a good idea to use saved data with large reports.

Report-report interface: with the report-report interface, several reports can be linked to one anotheras modules.

Split report: using the function “split report”, large, complex reports can be split into several smallunits which can call each other up using variables.

Aspect design: the order of the characteristics created in an aspect can lead to variations in performance.

Summarization levels: a summarization level saves the transaction data of an aspect passively in acompressed form by leaving out certain selected characteristics.

The report is looked at in more detail in course AC615.



© SAP AG

R

Region

Division

C u s

t o m e r g r o u p

C u s

t o m e r g r o u p

110 0RT-0001

NorthPlastics

Retail trade

SalesHours worked

4,000,0001,300,000 Key figures

Charact-eristics

n Charact er is tic s и n-dimensional data cube

1 Element cube 1 data record in the aspect

Number of dimensions is the degree of detail/summarization level of dataset

Considerations when Modelling Data

You can compile the aspects according to your information requirements and your volume of data. In this respect, only related business data should be combined. With data modeling the degree of detail of the data should be taken into account. A high level of detail

increases the navigation possibilities in drilldown reporting, but also adversely affects the performancedue to the large volume of data. Here it is important to weigh up to what extent the data from theoperative systems is to be aggregated.







© SAP AG

R

Unit Summary (1)

The SAP-EIS data basis is divided into variousaspects.

The data structure of an aspect con sists of fixedcharacteristics, aspect-specific characteristics,and basic key figures.

The view aspect as a special case enables across-table evaluation of the data from severalaspects.

To supplement transaction data manually in thesystem, you can use single record m aintenanceand m aintenance with a layout.



© SAP AG

R

Unit Summary (2)

The key figures are formed from the basic keyfigures of the aspect, and existing key figuresand con stants, and are uniquely defined for allaspects.

EC-EIS planning enables you to create amultidimensional plan for a company at a highlevel of aggregation.



© SAP AG

R

Data Transfer - Contents

Data collectionTransfer rules

Transfer procedure

Currency translation

Standard data collection reports

Flexible Excel upload

Aspect summarization

Data transfer between systems

Currency translation



© SAP AG

R

Data Transfer: Unit Objectives (1)

In this unit you will learn about

Steps in data collection

Alternatives for data supply in the SAP EISSystem

Currency translations with data transfer

Definitions of sender structures and rules for data transfer.



© SAP AG

R

Data Transfer: Unit Objectives (2)

In this unit you will learn about

Various standard data collection reports

The flexible Excel upload,

Summarization aspects

Types of communication between systems



© SAP AG

R

Data Transfer

Unit 2Data basis- Aspect- Characteristics- Key figures- Data entry- Planning

Unit 4Authorizations- EIS authorization

objects- Defining EIS

authorizations

Unit 3Unit 3Data transfer Data transfer - EIS data provision- EIS data provision- Data transfer program- Data transfer program- Transfer procedures- Transfer procedures





© SAP AG

R

HOST

SelectSelect

Sender structureConvertConvert

SummarizeSummarize

Receiver structureUpdateUpdate

K

e e p

l o g

Steps in Data Collection

EIS DatabaseEIS Database

NO NNO NSA PSA P

SA PSA PR/2R/2

SA PSA PR/3R/3

FILEFILE

Data collection covers functions which enable you to fill the database tables (aspects) with data. Thisdata can come from both the SAP environment and other applications. Sender programs in R/2 or R/3 select a data extract from R/2 or R/3 databases using the pre-defined

sender structure. The technical communication takes place using CPI-C, RFC or a file transfer. In R/3 the data extract is modeled to the receiver structure using transfer rules, and updated in the EIS

database.





© SAP AG

R

Sender structure

Sender structure

Source system

Target system

Transport using CPI-Cor file (1:1)

Sender Structure

aspect structure

Receiver structure or

Transfer rules

The principal classification term in the data transfer area is the sender structure. A sender structure describes the structure of the data which is to be transferred to an aspect in EIS. If

you are transferring data between different systems, the sender structure must be described identicallyin both the source system and the target system.

If you transfer data from an SAP system, the sender structure must have the same name as the datacollection program in order to link the collection program and the sender structure.

If you use standard collection reports, the sender structures already exist or are generatedautomatically.

To import files the name of the sender structure can be freely assigned. A sender structure consists of one or more dictionary structures; each DDIC structure describes the

structure of reports expected to be imported. The transfer rules for the sender structure must be maintained in the target system. You instruct a sender structure as to which aspect of the sender program the data should be transferred

to, and which transfer method to use (this determines the type of data transfer). If you would like towork with validation during the data transfer, enter the validation name. By checking the “double key”field you can allow records with double keys during the data transfer.





© SAP AG

R

Transfer Rules for Characteristics

Setconstants

Receiver structure

Senderstruktur Fiscal year Period Customer Division Material Sales ...

...

...

...

1998 001

1998

1998

002

003

Mь ller

Mь ller

Mь ller

Pumps

Pumps

Colors

AX B

AX C

Lack 12

4350

4985

854

Senderstruktur Fiscal year P er io d S ale s d is tric t Country Sales ...Area

...1998 013 North district DE ? 10189

Setvariables

Sender structure

Senderrecords

Transfer rules

Receiver records

Transfersender field

Reassignsender fields

The transfer rules help to define how sender structure fields should be modeled to fields of a receiverstructure (aspect structure). Rules when maintaining transfer rules for characteristics:

• Transfer sender field: the sender field values are assigned to the receiver field. You can restrict thevalue area and set conditions so that the transfer takes place only if the data record containsspecific values.

• Reassign sender fields: specific sender field values are assigned to a receiver field value. You canreassign the sender fields, using an Offset assign only parts of the sender field, and set conditions.By applying this rule, you can, for example, summarize characteristics (from periods to quarters),or use sender structure characteristics to fill different characteristic in the receiver structure.

• Set constants: you can assign a fixed value to the receiver field.• Set variables: you can assign a variable to the receiver field. This allows you to make an enter in

the field only when the data transfer is being executed.• Apply general rules: you can set rules to be used for several transfers.

During the transfers for characteristics you can determine whether the receiver record fields should beverified against the master data tables.

You can decide what happens if, contrary to the rules, a characteristic value does not receive a value(set to initial value, classify as an error, set constants, transfer sender field).

Special features with transfer rules for compound characteristics: the rules must be maintained for eachfield. The data transfer, however, executes a complete verification for compound characteristics.



© SAP AG

R

Transfer Rules for Key Figures

Receiver structure

Sales CM 1Capacity QuantityF/year ... Sender structure

Senderrecords

Transfer rules

Receiverrecords

Mkt share

Sales Max.Cap. No. empCM1 MinF/year ... M/share 2

Emp. Age

M/share 1

...

Senderstruktur ...Senderstruktur ...

Senderstruktur ...

1998

1998

1998

1998

4350

4985

854

10189

SU M

81

96

89

96

MAX

150

89

10-

10-

MIN

158

679

473

35

61

42

3

COUNT

20

35

33

FIRST

20

LAST

33

In the transfer rules on key figures, enter in the formula how the key figure is calculated. It is possible,for example, to use two key figures to calculate a third one.

You can determine a currency translation type (for the sender structure) or a target unit for key figures. You can determine whether an existing key figure in the database should be overwritten during the

data transfer. If the value is not overwritten, it will be read from the database and taken as the initialvalue during the entire operation.

Via the total operation field you determine what happens if several records are to be modeled to thesame receiver. Depending on the total operation different values are written to the database• With SUM the sum of the results is added.•

With MAX the largest,• With MIN the smallest,• With FIRST the first and• With LAST the last result is taken.• With ‘count’ the number of records is counted.

Using conditions, you can determine that a key figure is filled only if a sender field accepts certainvalues.









© SAP AG

R

Data Collection Reports from CO-PA

CO-PACO-PA


Data collection from CO-PA (Profitability Analysis):• Data from CO-PA can be transferred to SAP-EIS using basic reports.• A corresponding sender structure is generated automatically.

When executing the function, a program for transferring the report data to the EIS System is generatedfrom the CO-PA drilldown report. The program also requires the aspect into which the data is to beimported. The EIS System automatically generates a sender structure using the characteristics and keyfigures used in the report.

After executing the function, the transfer of data from CO-PA can be started from within EIS. Whenstarting the data transfer you can decide if, with repeated data transfer, you wish to transfer only thedifferences from the previous run, or all the data again.

A prerequisite for generating a data transfer report from CO-PA is a basic drilldown report.



© SAP AG

R

Data Collection Reports by Report Writer

CO-OMCO-OMEC-PCAEC-PCAFI-SLFI-SL


With Report Writer or Report Painter reports, data from CO-OM (Overhead Cost Controlling), EC-PCA (Profit Center Accounting) and the FI-SL (Special Ledger) can be transferred to EIS.



© SAP AG

R

Summ arization in the Set hierarchy

Cost center hierarchy

H1H1

H1000H1000 H2000H2000

H1100H1100 H1200H1200 H1300H1300 H2100H2100 H2200H2200

1

2

3

S ele ctio n S ets O utp ut p aram eters

Cost ctr grpCost ctr grp : H1: H1 OutputOutput mediummedium : 5: 5

Characteristic: from to single value

Cost centerCost center 0202 0202

OutputOutput parametersparameters

VariationVariation

Example: Report Writer

General requirements for Report Writer reports for transferring data to SAP-EIS: Prerequisites:

• The columns may contain key figures only.• The evaluation characteristics are to be entered in the report rows.• The characteristics in the rows are to be broken down in the Report Painter or must have detail level

0, 1 or 2 in the Report Writer.• If the values in Set hierarchies (for example, cost center hierarchy) are to be summarized and

transferred at a summarized level, you can use the selection variation. When starting the datatransfer, the ‘from’ level must be the same as the ‘to’ level, otherwise data records will betransferred more than once.

• Each report can contain only one row block (the same characteristics have to be transferred for allrows).

• A newly created report should be assigned to a report group which itself may only contain onereport.



© SAP AG

R

Data Collection Reports Using ABAP Query

ABAPABAPQueryQuery


SAP-EIS is linked to the ABAP Query which means that all data that can be displayed by means of asingle-line ABAP Query can be transferred to aspects. The ABAP Query is suitable for data collectionwhenever the sender database is transparent and does not require any additional external information(for example, LIS info-structures).

The query can be used for transferring both master data and transaction data. The transfer rules must be maintained in the target aspect.



© SAP AG

R

Standard Data Collection Reports from R/2

R/2R/2 RFRK-ERK-SRK-PABAP Query


Below is a list of R/2 collection programs:Application Collection program Sender structureRF RFBILA00, RFSERG00 Balance sheet item, account, company code,

business area, report year, from-report month,to-report month, currency, amount.

RK-E TK75 is generatedRK-S SAPK021V KIDS

RKCKSTKS RKCKSTSP for generating the sender structureRL-P RXSEIPSA EIPS (DDIC)Misc. ABAP Query is generated

Setting up the data collection from R/2 begins in R/2. The sender structure (T242S) has to be createdfor the delivered R/2 collection reports or reports produced in-house. In R/3, the sender structurecreated in R/2 can be transferred automatically.

A more extensive description of the R/2 collection programs is stored in R/2 as report documentationand parameter documentation. See also the corresponding chapter in the R/3 IMG.



© SAP AG

R

Importing Files

RKCFILE0

Aspect CF xxx

You use this function to import data from a file. To import larger data volumes on a periodic basis, you can schedule report RKCFILE0 in the background processing.

To do this, you must have maintained the sender structure and transfer rules. The files can be read both from the presentation server and from the database server. Different file types can be imported:

• TXT format (the fields in the rows must be separated by tabulator characters)• CSV format (the fields are separated by semicolons)• MC format (the file to be imported is split into two parts: rows at the beginning with characteristic

values, which hold for the remaining records, and single records. The fields in these single records

are separated by either a comma or a semicolon)• Binary files (with binary files the system requires the SAP binary format). Binary files cannot be

imported from the presentation server).









© SAP AG

R

R/2R/2

Target system Source systemTransfer methods:Destination e.g.: S11ClientUser Password

Use inFinding destinationLogs

Transfer methods:Destination e.g.: S12ClientUser PasswordQueueDriver program

Use inFinding destinationLogs

Communication

Buffer

Sender structure

Transfer rules

EIS - DBEIS - DB

Sender structure

To set up the communication between a sending system and SAP-EIS, you need to maintain thetransfer method. There are three ways of starting the sender program:

• Starting the sender program from the target system with the program RKCSUB00• Starting the sender program in the source system online• Scheduling the sender program in the background processing in the source system

Depending on where you want to start the transfer, the transfer methods must be maintaineddifferently.

In the source system the transfer method has to be completely maintained (logon in the target system,Queue and driver program RKCDRIVE).

In the target system a transfer method should be created and have the same name as the transfermethod in the source system (if the sender program is to be started in the source system, it is enough tocreate a transfer method in the target system. There is no need to make specifications for the targetsystem and QUEUE.)

If the sender program is to be started from the target system with the program RKCSUB00, you mustspecify for the transfer method in the RKCSUB00 selection screen in the target system, how the targetsystem logs onto the source system.



© SAP AG

R

Source system 3

Target system 1

Source system 2

Client 2

Client 3

Source system 1

Transfer Logs

L o g

L o g

L o g

L o g

Since the data transfer does not usually take place online, a log is written for each data transfer. The log display for a sender structure includes information on errors and on the timing details of the

data transfer. Using various selection criteria you can display lists of the available logs. In the detail screens of the individual logs you can reprocess non-posted sender records or incorrect

receiver records, for example. It is possible to display or delete sender and receiver records, or to display the required structures. You

can import the sender and receiver records again. To avoid having a large volume of data it is advisable to regularly delete existing logs that are no

longer required.





© SAP AG

R

Job definieren

StepsKlicken Sie, um Text hinzuzuf ь

gen

Job nameJob classStatusTarget host

D-Transfer CPlanned

Start date

Define jobDefine job

Transfer Procedure

Klicken Sie, um Text hinzuzuf ь gen

StepStep 11

User ABCD

Program detailsABAP programName RKCSUB00Variant ...External program

Klicken Sie, um Text hinzuzuf ь gen

DateTime

no w

21.02.199420:00:00

After job

Date/time

After event

Start dateStart date

In order to start programs in the source system background from within the target system, you mustcreate variants for the program RKCSUB00, in which the sender program to be started in the sourcesystem is specified. The transfer method delivers the necessary information to the source system.

Procedure:• Program RKCSUB00 starts a sender program in the source system.• RKCSUB00 must be scheduled as a job.• Transfer methods for R/3 must be maintained.• Transfer methods for R/2 must be maintained (Table T2420).



© SAP AG

R

Data Transfer: Unit Summ ary (1)

There are different ways o f transferring data fromSAP and non-SAP sources into SAP-EIS. Withinan R/3 System the data transfer occurs viastandard interfaces or user-defined programs,via CPI-C (other R/3 or R/2 Systems) and CPI-C/RFC or a file (non-SAP Systems).

The transfer rules help define how sender structure fields are to be modeled on the fields of a receiver structure, although the supply of datato the characteristics is d ifferentiated from thesupply to the key figures.



© SAP AG

R

Data Transfer: Unit Summ ary (2)

Various R/2 and R/3 standard data collectionreports are delivered together with the system.

Using aspect sum marization you can reorganizetransaction data and combine data from differentaspects in a summarization aspect.





© SAP AG

R

A u th o r izatio n s : Un i t Ob jec t ives

In this uni t you wil l learn abou t

The SAP-EIS authorizat ion c onc ept .



© SAP AG

R

A u th o r izatio n s

Unit 3Data transfer - EIS data pro vision- Data transfer program s- Transfer pro cedures

Unit 2Data basis- Asp ect- Characteristics- Key figures- Data entry- Plannin g

Unit 4Unit 4 A u tho riza tions A u th oriza tio ns- EIS authorization- EIS auth orizatio n

objec ts objec ts- Defini ng EIS- Definin g EIS

authorizations authorizations



© SAP AG

R

User

Profi le

A u th o r iza tio n

Value

Object

Field

The Au thor izat ion Con cept

Can co nta in m ore than oneelement

The authorization concept determines which functions users are allowed to execute in the SAPSystem. You need to define authorizations for these functions, and assign them to your users using profiles.

Authorizations refer to authorization objects, which are pre-defined by SAP.



© SAP AG

R

A u th o r izatio n Ob jec ts

Data entry layout/data entry A c t iv ity ; as p ec t ; fo rm

Funct ion code A c t iv ity

Structures and key figures A pp lic at ion c las s ; as p ec t ; fu nc t io n code; t r an sac t ion cod e

Presentat ion objects A c t iv ity ; as p ec t

Presentat ion form A c t iv ity ; as p ec t ; fo rm

Data basi s

A sp ec t; func t ion c od e; f is cal yea r ; per io d ;t ransact ion code

Data struct ure maintenance A s pec t ; fun c t io n c ode; key f igu re g ro up ; tr an sac t io n cod e

Presentat ionUser group; repor t name; s torage locat ion; funct ion ; t ransact ion;num ber of the h ierarchy node

Hierarchies A c t iv ity ; ap p l icat ion c las s ; f iel d nam e; h ier ar ch y v ar ia n t

The graphic shows the pre-defined standard authorization objects and the fields contained in them.



© SAP AG

R

Divis ion:Rev.: 1000 TDMCMI: 80 TDM

Rev.: 200 TDMCMI: XXXX


Office supplies

Product group

Rev.: 1000 TDMCMI: 80 TDM



Computers

Divis ion:

Rev .: 1000 TDMCMI: 80 TDM

Rev .: 200 TDMCMI: XXXXRev .: 300 TDMCMI: XXXX

Toys

A u th o r izat io n Ob jec ts fo r Co m b in ation s o f Character is t ics and K ey Figu res

For any aspect you can create authorization objects for combinations of characteristics and keyfigures. The new authorization objects are used within the aspect to ensure authorization protection for

combinations of characteristics. Each authorization object consists of up to 10 selected fields which you can determine. Fields can be both characteristics of an aspect and place holders for key figures.

All the characteristics and key figures that are not specified in the authorization object are allowed. Before executing a report, the user’s authorizations are checked. If the user does not have an

authorization for one of the selected objects, the request is rejected. The authorizations are also checked for data collection and planning.

Possible authorizations for an object:• Normal characteristic values and key figures• '*’ : authorization for all the values of a characteristic• ':’ : the user can sum using this characteristic• ’#’ : the user is authorized for the initial characteristic value.



© SAP AG

R

A u th o r izatio n s : Un i t Su m m ary

The au thor izat ion con cept cont ro ls whichfun ct ion s cer tain users are al lowed toexecute in the SAP System.





Unit: Data basis

Topic: Characteristics

• Create characteristics

Characteristics classify the dataset. They are part of the aspect structureand can be seen as data records keys that are stored in the database tableof the aspect.

1-1 Characteristics

1-1-1 Creating characteristics

Create an EIS-generated characteristic 'Customer group XX' with the fieldname 'CGXX', whereby 'XX' stands for your group number (the number onyour screen).

Enter data type 'NUMC' and length '2'. Under Display, select 'Text plus Key'.

Check your entry.

Save your entry and select 'Automatic generation' of the characteristic checktable.

Generate the master data routines exclusively for the new characteristics.

What is the name of the generated check table?



1-1-2 Maintaining master data

Maintain the characteristic values for your characteristic 'CGXX'.

Since the characteristics have not yet been assigned to an aspect, you must begin maintaining them using Transaction '/nsm30' (in the input field). Enterthe name of the check table and maintain the following characteristic values:

Customer group XX Description Long text

10 Industry Industry

20 Services Services

1-1-3 Creating characteristic attributes

Create another EIS-generated characteristic 'Customer XX' with the fieldname 'CUXX', where 'XX' stands for your group number (the number on yourscreen).

The characteristic 'CUXX' should have the same data type as thecharacteristic 'CGXX' from the last exercise.

Before saving and activating the new characteristic, click on 'Attributes'.Select your characteristic 'CGXX' as a characteristic attribute for 'CUXX'from the field catalog.

Save and activate the new characteristic, have the characteristic tablegenerated automatically again, and generate the master data modules. Havethe view maintenance modules generated only for new characteristics.

Using Transaction '/nsm30', enter the following values in the master datatable of characteristic 'CUXX':

Customer Description Long text ... Customer group

10 Hagmanns Hagmanns Inc. 10

20 HTC Hills Training Center 20

1-1-4 Displaying characteristic attributes

Display the structure of aspect '665'. This aspect contains only characteristic'CU00' (customer group 00) and a basic key figure (contribution margin). Thecharacteristic customer group also has an attribute (customer group), as inthe last exercise.

Start the report 'Attributes' in aspect '665'.

What you see now are the two navigation characteristics, customer group andcustomer. The characteristic attribute appears in the drilldown report as anormal characteristic that you can use for navigation purposes.



Unit: Data basis

Topic: Key figures

• Create basic key figures

Whereas the characteristics classify the dataset, the key figures are the

transaction data, which is found in the database under a certaincombination of characteristic values.

2-1 Key figures

2-1-1 Creating key figures

Create the basic key figure 'EVAXX' (Economic Value AddedXX), and enteryour group number or the number on your screen for 'XX'. The currencyshould refer to the company code currency (COCDE1).

Which aggregation types are set as standard with time-based and non-time- based aggregation?

___________________________________________________________

Save and activate the basic key figure. What is the name of the data elementof the basic key figure?

___________________________________________________________

Display the basic key figure 'HB1_FI'. In how many aspects is this basic keyfigure used?

___________________________________________________________



Unit: Data basis

Topic: Aspect

• Create an aspect

Aspects classify the EIS dataset. Aspects are database tables that acquiretheir structure by including characteristics and key figures. Since the

ensuing reports are produced from the aspects, the characteristics and keyfigures set in an aspect should be related from a business point of view.

3-1 Aspect

3-1-1 Creating and maintaining an aspect

Create the aspect '8XX' (description 'Economic Value Added') where 'XX' isyour group number. The fiscal year variant 'K4' and the aspect currency 'UNI'should be assigned to the aspect.

Select the following characteristics and key figures:

Type Field name Description

Characteristic SBUN Strategic business unit

Characteristic CMPN Company

Key figure CAPIR Capital Return

Key figure COSTS Capital Costs

Key figure DBCOS Debt Costs

Key figure EQCO Equity Costs

After selecting the correct characteristics and key figures from the fieldcatalog, check, save and activate the aspect and generate the aspectenvironment.



Display the aspect list and check if everything has worked. Maintain theaspect '8XX'. Which are the technical fields of the aspect?

_________ __________ __________ __________

How many bytes are still available in this aspect for additional characteristicsand key figures?

_________



Unit: Data basis

Topic: Data entry

• Create a data entry layout

There are two different ways of manually checking actual data into thedatabase: single data record entry where in fact only individual data

records are saved/changed in the aspect, and data entry using layouts withwhich several data records can be processed simultaneously.

4-1 Entry layout

4-1-1 Data entry with layout

Starting from the configuration menu, create entry layout 'LayoutXX' (groupnumber) for aspect '8XX'). You can find this function under Data basisData entry layout Create .

In the general selections define the validity of the layout:

Version '2' (test version),

Planned/actual KF '0' (actual data) and

Fiscal year '1998'.

Set a variable for the periods

Put the characteristics 'Strategic business unit' and 'Company' in the leadcolumn. Copy the asterisk as a characteristic value to allow any entry for thecharacteristics.

Put the four basic key figures of the aspect in the columns of the layout, bydouble clicking in the relevant places. Do not select any more characteristicshere. For each column a unit column is automatically created.

Save your layout.

You enter data records with your layout by choosing either EnvironmentData entry or from the application menu Transaction data Data entryMaintain with layout .

By clicking on 'Overview screen' you access the data entry.

Enter some data records in any combination of characteristics.



Save the data and create a basic report for the aspect to display the data.



Unit: Data transfer

Topic: Sender structure

• Create a complex sender structure

Sender structures describe the data that is to be imported into aspects bydata transfer.

1-1 Sender structure

1-1-1 Creating a complex sender structure

Call up MS Excel and open the file ‘complex.xls’.

The instructor will tell you which directory to use. A simple example of acomplex data structure will appear on-screen for aspect '8XX' that you usedin the data basis unit exercise.

There are two data records of different lengths and content. The type 1 datarecords are general settings for type 2 data records.

A type 1 data record is recognizable by type number 1, offset 0, and datarecord type 2 is recognizable by type number 2 and offset 0.

Create sender structure ‘COMXX’, where XX is again the number of yourgroup.

To link the complex sender structure to aspect ‘8XX’, you have to assign twodictionary structures to the sender structure (one per data record type).

Create the first dictionary structure ‘RKCTAXX’, where XX is your groupnumber. Enter the correct offset, the correct sender field length and the fieldvalue, so that the correct dictionary structure can be assigned to the detaileddata records.



Double click on the row and enter the necessary fields to describe data recordtype 1.

Note: look at the Excel sheet and the help tables below to describe the senderstructure and both its dictionary structures correctly.

Further help information

(Characteristics and key figures of data record types 1 and 2 )

Characteristic/key figure Type Length Decimal

TYPE N 1 0

YEARB N 4 0COMPANY N 2 0

PERIOD N 3 0

RETURN P 8 2

COSTS P 8 2

DBCO P 8 2

EQUITY P 8 2

Save your dictionary structure.

Now you have to create another dictionary structure for data record type 2.

Name the dictionary structure for type 2 ‘RKCTBXX’, where XX is yourgroup number, and enter the necessary fields to describe the data record typecorrectly.

Save your sender structure, and then close your Excel file.



Unit: Data transfer

Topic: Transfer rules

• Create transfer rules for your sender structure.

Whereas the sender structures describe the data that is to be imported into

aspects by data transfer, you determine in the transfer rules how theimported data is to be saved in the database.

2-1 Transfer rules

2-1-1 Creating transfer rules

Maintain the transfer rule 'COMXX' for your sender structure 'COMXX',where XX is your group number.

Create a rule proposal by clicking on the relevant button.

Assign a constant value '1' to the version and the value '0' to the plan/actualindicator.

Define the correct rules for the remaining characteristics and key figures withthe exception of the characteristic 'SBUN'.

Save the transfer rules.

Switch to the Application menu and select Transaction data ∫ Transfers ∫ Import file .

Select the sender structure 'COMXX', where XX is again your group number.



Fill in the remaining fields:

Field name: Input data:Physical file name Given by the instructor

File system Presentation server

Data transfer Activated

Display file Activated

Display sender record-field assignment Activated

File type TXT format

Type P stored in double length Deactivated

Nimber format Decimal point

2-1-2 Import data

Start by importing the data from the Excel file. Check the log after the import procedure and look at the data records received.





Here you describe the structure of the Excel files to be imported.

From the configuration menu, go to the configuration of a flexible Excelupload: Data transfer File name Def. Excel upload .

Name the file description ‘FLEXIBLEXX’ where XX stands for your group

number.Configure the example file ‘SBU.TXT’ (your instructor will tell you which

path to use) so as to determine the grid structure and assign the correct fieldto the sender structure ‘UPLOADXX’.

First you must maintain the key figure areas:

You define these areas by double clicking on the relevant key figures. Forexample, first double click on the key figure ‘Return’ under 1996 ‘Plan’ andsecond double click on the key figure ‘Return’ under 1996 ‘Actual’. Now

select the button ‘Value area. Enter the sender structure (UPLOADXX) andthe sender field (CAPIT) which belongs to this area.

For each key figure and fiscal year, you have to maintain an individual keyfigure area.

Proceed similarly with the other key figure combinations.

In the next step you must maintain the header area.

Header areas are the SBU and the years.

Example: double click on SBU and select the header area button. Since theSBU applies to the whole form, you can enter an asterisk here.

For the fiscal years you must specify more precisely for which data area thisheader area is valid.

Finally, you must maintain the key area. In our example, the key area is the plan/actual indicator. Double click on the Plan 1. column and double click onActual 4. column.

Now select the ‘lead column’ button and enter value area ‘*’ and thecorresponding field (PLACTI).

Now maintain the generic file name ‘sbu*0.txt’. The asterisk means that allthe files that begin with ‘sbu’ and end with ‘0.txt’ are imported from a

predefined directory. In the example, these are the files ‘sbu10.txt’ and‘sbu20.txt’.

Check and save your file description.

Maintain the transfer rules ‘UPLOADXX’ for the relevant sender structure‘UPLOADXX’.





Unit: Data transfer

Topic: Planning – additional exercise

• Plan your aspect

The planning function allows a company-wide view of plan data.

4-1 Planning

4-1-1 Defining a planning layout

In this exercise you will learn how to define an individual planning layoutwith which you can plan the capital costs of decentralized companies for theyear 1998 on the basis of the actual data for 1997.

Create a planning layout 'CAPCOS' for the aspect '8XX'. Use the followingstructure as a basis:

Rows/columns Value

Row 1: Company Oil (10)

Row 2: Company Natural (20)

Column 1: Capital costs Actual 1997 (12 periods)

Column 2: Capital costs Plan 1998 (12 periods)

Column 3: Variance Variance between plan and actual

Add the attributes 'Unit' and 'Distribution key' to the first two columns. Thecurrency unit and the distribution key will then be displayed in the planninglayout.

In the general selections, set the version to value '1' – IDES Version.

Make sure that the calculated third column is not ready for input.

Check, save and quit the planning layout definition.



4-1-2 Interactive planning

Plan the capital costs for the companies that you have set up in your planninglayout.

Use the planning layout 'CAPCOS' for the aspect '8XX'.

Select and copy the actual data from 1997 and place this in the plan datacolumn.

Select the plan data column and click on 'Change values'. Enter –5(%) andclick on ‘Revaluate’.

Check the entry by displaying the variance column.

Change the distribution key of the 'Oil' company to 'Uniform distribution'.Switch to the period screen of the 'Oil' company and check the values.

4-1-3 Automatic planning with revaluation

Create the revaluation 'EXX' for aspect '8XX', where XX is your groupnumber.

Assign factor ‘-10’ (%) to the key figure 'Capital costs'. Save and terminatethe revaluation definition.

Switch to automatic planning and enter the following values:

Field Value

Plan aspect 8XX

Plan version 1

Plan period 001.1998 to 012.1998

Source data aspect 8XX

Source data plan/act. indic. Actual

Source data version 1

Source data period 001.1997 to 012.1997

Revaluation key function EXXExtras test run Off

Extras log On

Extras backgr. processing Off

Updating Without transfer rules, overwriting

Click on 'Select characteristics' and select the characteristic 'Company'. Clickon 'Continue'. Select the key figure 'Capital costs' ('Continue') and set thevalue area '10 – 20' for the company ('Continue').

Save the settings as variant 'AutoXX' .





© SAP AG

R

S o l u t i o n s



Unit: Data basis

Topic: Characteristics

• Create characteristics

Characteristics classify the dataset. They are part of the aspect structureand can be seen as data record keys that are stored in the database table ofthe aspect.

1-1 Characteristics

1-1-1 Creating characteristics

Create an EIS generated characteristic 'Customer group XX' with the fieldname 'CGXX', where 'XX' stands for your group number (the number on yourmonitor) .

Configuration menu: Data basis ∫ Characteristics ∫ Edit .

Enter the Characteristic field name and click on 'Create/change'

Enter a name for the characteristic, activate 'Creating with new data elementand check table' and click on 'Create' .

Enter a description , short text and heading

Enter data type ' NUMC' and length '2' (data type/length). For format, select‘Text and Key’.

Check your Entry .

Save your entry and select 'Automatic' generation of the characteristic checktable.

Activate the characteristic and generate the master data routines for the newcharacteristics only .

What is the name of the generated check table?

_______T27XX_______



1-1-2 Maintaining master data

Maintain the characteristic values of your characteristic 'CGXX'.

Since the characteristics have not yet been assigned to an aspect, you have tostart maintaining the characteristics using transaction ‘/nsm30’ (in the input

field). Enter the name of the check table and maintain the followingcharacteristic values:

In transaction ‘sm30’ under ‘Table/view' enter your table 'T27##' and click on'Maintain'. Click on 'New entries', enter the customer groups and save yourentries.

Customer group XX Description Long text

10 Industry Industry

20 Services Services

1-1-3 Creating characteristic attributes

Create another EIS-generated characteristic 'Customer XX' with the fieldname 'CUXX', where 'XX' stands for your group number (the number on yourscreen).

The characteristic 'CUXX' should have the same data type as thecharacteristic 'CGXX' from the last exercise.

Before saving and activating the new characteristic, click on 'Attribute'.Select your characteristic 'CGXX' as the characteristic attribute for 'CUXX'

from the field catalog.

If you are in the input screen for the attributes , you have to switch to the'Create' icon.

Save and activate the new characteristic, have the characteristic tablegenerated automatically, and generate the master data modules. Generate the

view maintenance modules only for new characteristics.Using transaction '/ nsm30' , enter the following values for the master datatable of characteristic 'CUXX':

Customer Description Long text ... Customer group

10 Hagmanns Hagmanns Inc. 10

20 HTC Hills Training Center 20



1-1-4 Displaying characteristic attributes

Display the structure of aspect '665'. This aspect contains only characteristic'CU00' (Customer group 00) and a basic key figure (contribution margin).The characteristic customer group has also, as in the last exercise, anattribute (customer group).

Configuration menu: Data basis Aspect Edit . Enter aspect number andclick 'Display'.

Start the report 'Attributes' in aspect '665' .

Application menu: Information system Report Execute

You can now see both the customer group and the customer navigationcharacteristics . The characteristic attribute appears in the drilldown report asa normal characteristic that you can use for navigation purposes.



Unit: Data basis

Topic: Key figures

• Create basic key figures

Whereas the characteristics classify the dataset, the key figures are the

transaction data, which is found in the database under a certaincombination of characteristic values.

2-1 Key figures

2-1-1 Creating key figures

Create the basic key figure 'EVAXX' (Economic Value AddedXX), where XXis your group number or the number on your monitor. The currency shouldrefer to the company code currency (COCDE1) .

Configuration menu: Data basis Basic key figures Edit .Enter the Field names of the basic key figure and click 'Create/change'.

Enter a description and a short text. Under 'Amount', click on 'Referencecurrency' and select 'COCDE1' for the 'Reference characteristic'.

Which aggregation types are set as a standard with relevant and time-dependent aggregation?

Set both aggregation and time-based aggregation (Agg.(time)) to 'SUM'.

Save and activate the basic key figure. What is the name of the data elementof the basic key figure?

___RKCG_EVAXX___________________________________________

Display the basic key figure 'HB1_FI'. In which aspects is this basic key figure used?

Configuration menu: Data basis Basic key figures Edit

Enter the name of the basic key figure and click 'Display'.

You can find the where-used list under:Edit Use in class/object .



Unit: Data basis

Topic: Aspect

• Create an aspect

Aspects classify the EIS dataset. Aspects are database tables that acquiretheir structure by including characteristics and key figures. Since the

ensuing reports are produced from the aspects, the characteristics and keyfigures set in an aspect should be related from a business point of view.

3-1 Aspect

3-1-1 Creating and maintaining an aspect

Create the aspect '8XX' (description 'Economic Value Added') where XX is your group number. The fiscal year variant 'K4' and the aspect currency'UNI' should be assigned to the aspect.

Configuration menu: Data basis Aspect Edit Enter the aspect number and click on the 'Edit aspect' icon. Click on 'Create'.

Enter the aspect name. For aspect type, select 'Transparent table' and enter theaspect attributes Fisc.year var., 'K4' and currency 'UNI'. Click the 'Edit datastructure' icon.

Select the following characteristics and key figures

Type Field name Description

Characteristic SBUN Strategic business unitCharacteristic CMPN Company

Key figure CAPIR Capital Return

Key figure COSTS Capital Costs

Key figure DBCOS Debt Costs

Key figure EQCO Equity Costs





Unit: Data basis

Topic: Data entry

• Create a data entry layout

There are two different ways of manually checking actual data into thedatabase. Single data record entry with which in fact only individual datarecords are saved/changed in the aspect, and the data entry using layoutswith which several data records can be processed simultaneously.

4-1 Entry layout

4-1-1 Data entry with layout

From the configuration menu, create the entry layout for aspect '8XX''LayoutXX' (group number). You can find this function under Data basisData entry layout Create .

In the general selections, define the validity of the layouts:Version ‘2’ (test version),

Plan/actual indicator '0' (actual data), and

Fiscal year '1998'

Set a variable for the periods.

You can find the general selections in the menu under Edit Gen. Dataselection Display/change.

Put the characteristics 'Strategic business unit' and 'Company' in the leadcolumn ( double click on the lead column). Copy the asterisk as acharacteristic value to allow any entry for the characteristics.

Put the four basic key figures of the aspect in the columns of the layout bydouble clicking in the relevant places. Do not select any more characteristics.For each column a unit column is created automatically.

Save your layout.



Enter data records with your layout by choosing either Environment Dataentry or from the application menu Transaction data Data entryMaintain with layout .

By clicking on 'Overview screen' you access the data entry.

Enter some data records in any combination of characteristics.

Save the data and create a basic report for the aspect so as to display the data.

You create reports through the Application menu under Information system ∫ Report ∫ Create . Enter the aspect and a name for the report, and select the

basic report. Now you can select the characteristics and key figures whichyou want to report on. Save and execute the report.



Unit: Data transfer

Topic: Sender structure

• Create a complex sender structure

Sender structures describe the data that is to be imported into aspects bydata transfer.

1-1 Sender structure

1-1-1 Creating a complex sender structure

Call up MS Excel and open the file ‘complex.xls’.

The instructor will tell you which directory to use. A simple example of acomplex data structure will appear on-screen for aspect '8XX’ from the data

basis exercise.There are two data records of different lengths and content. Type 1 datarecords are general settings for type 2 data records.

A type 1 data record is recognizable by type number 1, offset 0, and datarecord type 2 is recognizable by type number 2 and offset 0.

Create sender structure ‘COMXX’, where XX is again the number of yourgroup.

Configuration menu:Data transfer Transaction data Sender structure

.Click on 'New entries’.

Maintain the name of the sender structure (COMXX), create the aspect with(8XX) and check the field ‘Double key’.

Enter item number 1. To link the complex sender structure to aspect ‘8XX’,you have to assign the sender structure two Dictionary structures (one perdata record type).

Create the first Dictionary structure ‘RKCTAXX’, whereby XX is your groupnumber. Enter the correct offset (‘0’), the correct sender field length (‘1’) andfield value (‘1’), so that the data records are assigned the correct Dictionarystructure.





Entries in the sender structure:

Sender field Table Description Type Length Decimal

Type Type N 1 0Period Period N 3 0

Return Capital return P 8 2

Costs Capital costs P 8 2

DBCO Debt costs P 8 2

Equity Equity costs P 8 2

Save your sender structure, and then close your Excel file.



Unit: Data transfer

Topic: Transfer rules

• Create transfer rules for your sender structure.

Whereas the sender structures describe the data that is to imported into

aspects by data transfer, you determine in the transfer rules how theimported data is to be saved to the database.

2-1 Transfer rules

2-1-1 Creating transfer rules

Maintain the transfer rule ‘COMXX’ for your sender structure ‘COMXX’,where XX is your group number.

Configuration menu: Data transfer ∫ Transaction data ∫ Transfer rules

Enter the sender structure (‘COMXX’) and click on ‘Maintain’.Click on 'Create proposal for rule'.

Assign a constant value ‘1’ to the version and the value ‘0’ to the plan/actualindicator. Double click on the relevant characteristic, click on 'Set constant"and select the corresponding characteristic.

Define the correct rules for the remaining characteristics and key figures withthe exception of the characteristic ‘SBUN’:

YEARB has sender field FYEAR

PERDE has sender field PERIOD

CMPN has sender field COMPANY

CAPIR has the complete operation Sum and the formula RETURN

COSTS has the complete operation Sum and the formula COSTS

DBCOS has the complete operation Sum and the formula DBCO

EQCO has the complete operation Sum and the formula EQUITY

Save the transfer rules.



Switch to the Application menu and select Transaction data TransfersImport file .

Select the sender structure ‘COMXX’, where XX is again your group

number.Fill in the remaining fields:

Field name: Input data:

Physical file name Given by the instructor

File system Presentation server

Data transfer Activated

Display file Activated

Display sender record-field assignment Activated

File type TXT format

Type P stored in double length Deactivated

Number format Decimal point

2-1-2 Import data

Start importing the data from the Excel file. Check the log after the import procedure and look at the data records received.



Unit: Data transfer

Topic: Flexible Excel upload

• Define a flexible Excel upload

The flexible Excel upload is a user-friendly function with which the datafrom an Excel sheet can be transferred to EC-EIS aspects. The advantageover the ‘Import file’ function is that, with a flexible Excel upload, theExcel sheet does not need to have a uniform structure.

3-1 Flexible Excel upload

3-1-1 Executing a flexible Excel upload

Create a sender structure ‘UPLOADXX’ in aspect ‘8XX’, which you havecreated already in a previous exercise. Configuration menu: Data transferTransaction data Sender structure .

Assign a Dictionary structure ‘RKCTUXX’, where XX is your group number.Check the field ‘Double key’. Maintain the DDIC structure, and complete thetable as follows:

Sender field Description Type Length Decimal

VERSION Version C 3 0

PLACTI Plan/act. indic. C 1 0

YEARB Fiscal year N 4 0

PERDE Period N 3 0

SBUN Strateg. bus. unit N 2 0

CAPIT Capital return P 8 2

COSTS Capital costs P 8 2

DBCO Debt costs P 8 2

EQCO Equity costs P 8 2

Save your entries.



In the next step you must define an Excel file description.

Here you describe the structure of the Excel files to be imported.

From the Configuration menu define a flexible Excel upload: Data transferFile name Def. Excel upload .

Name the file description ‘FLEXIBLEXX’ where XX stands for your groupnumber.

Configure the file containing the example ‘SBU.TXT’ (your instructor willtell you which path to use) so as to set the grid structure and assign thecorrect field to the sender structure ‘UPLOADXX’.

First you must maintain the key figure areas:

You define these areas by double clicking on the corresponding key figures.For example, first double click on the key figure ‘Return’ under 1996‘Planned’ (coordinate 2/8). Second double click on the key figure ‘Return’under 1996 ‘Actual’ (coordinate 3/8). Now select "Value area". Enter thesender structure (UPLOADXX) and the sender field (CAPIT), which belongsto this area. Click on ‘Back’.

Follow this sequence to define all key figures for 1996 and then define thekey figures for 1997.

For each key figure and fiscal year, you have to maintain an individual keyfigure area.

In the next stage you have to maintain the header area:

The header areas are the SBU and the years.

Example: double click on the SBU value (’10) and select the header area button. Since the SBU applies to the whole form, you can enter an asterisk.Click on ‘Back’.

With the fiscal years you must state more precisely for which data area thisheader area is valid.

Example: double click on '1996' and on the button 'Header area'. Using F4

access the value area field - here you can see the coordinates for thecorresponding value areas. Select the correct value areas one after the other.

Finally, you must maintain the key area. In our example, the key area is the plan/actual indicator. Double click on the Plan 1. column and double click onthe Actual 4. column.

Now select 'lead column’ and enter value block ‘*’ and the correspondingfield (PLACTI).



Now maintain the generic data names 'sbu*0.txt'. The asterisk means that allthe files that begin with ‘sbu’ and end with ‘0.txt’ are imported from a

previous directory. In the example, they are the files ‘sbu10.txt’ and

‘sbu20.txt’.

Check and save your file description.

Maintain the transfer rules ‘UPLOADXX’ for the relevant sender structure‘UPLOADXX’.

Configuration menu: Data transfer ∫ Transaction data ∫ Transfer rules

Generate the rule proposals.

Set the constant version to value ‘1’. Enter also a constant for a period (for

example, period 1) and save your transfer rules.Entries:

VERSIO constant to ‘1’

PLACTI with sender field PLACTI

YEARB with sender field YEARB

PERDE constant to, for example, ‘1’

SBUN with sender field SBUN

CAPIR, complete operation ‘SUM’, ‘Overwrite’ field active, and the formulaCAPIT

COSTS, complete operation ‘SUM’, ‘Overwrite’ field active, and the formulaCOSTS

DBCOS, complete operation ‘SUM’, 'Overwrite' field active, and the formulaDBCO

EQCO, complete operation ‘SUM’, ‘Overwrite’ field active, and the formulaEQCO

Start the flexible upload from the Application menu:Transaction data Transfers Flexible Upload .

Select here 'Import single file' and select the file 'sbu10.txt' (your trainer willtell you which directory to use).

Start the flexible upload and check the transfer log.

Repeat the upload process for file ‘sbu20.txt’.



Unit: Data transfer

Topic: Planning – additional exercise

• Plan your aspect

Planning enables a company-wide view of plan data.

4-1 Planning

4-1-1 Define a planning layout

In this exercise you will learn how to define an individual planning layoutwith which you can plan the capital costs of decentralized companies for the

year 1998 on the basis of the actual data for 1997.

Create a planning layout ‘CAPCOS’ for aspect ‘8XX’.

Configuration menu: Planning ∫ Planning layouts ∫ Create

Use the following structure as the basis:

Rows/columns Value

Row 1: Company Oil (10)

Row 2: Company Natural (20)

Column 1: Capital costs Actual, 1997 (12 periods)

Column 2: Capital costs Plan 1998 (12 periods)

Column 2: Variance Variance between plan and actual

Add the attributes 'Unit' and 'Distribution key' to the first two columns. Thsmeans that the currency unit and the distribution key will be displayed in the

planing layout.

In the general selections, set the version to value '1' - IDES version.

Menu: Edit Gen. data selection Display/change

Make sure that the calculated third column is not ready for input.



Menu : Formatting Ready for input y/n

Check, save and quit the planning layout definition.

4-1-2 Interactive planning

Plan the capital costs for the companies that you have set up in your planninglayout.

Application menu: Planning Interactive planning Change plan data

Use the planning layout ‘CAPCOS’ for aspect ‘8XX’.

Select and copy the actual data from 1997 and place it in the plan datacolumn.

Select the plan data column and click on ‘Change values’. Enter –5(%) andclick on 'Revaluate'.

Check the entry by displaying the variance column.

Change the distribution key of the ‘Oil’ company to ‘Uniform distribution’.Switch to the period screen of the ‘Oil’ company and check the values.

4-1-3 Automatic planning with revaluation

Create the revaluation 'EXX' for aspect ‘8XX’, where XX is your groupnumber.

Configuration menu: Planning Revaluation Change

Enter aspect, (with 'New entries') enter a number and a name for therevaluation key; select and click on 'Assign factors': also here with ‘Newentries’.

Assign factor ‘-10’ (%) to the key figure 'Capital costs'. Save and thenterminate the revaluation definition.

Switch to automatic planning and enter the following values:

Application menu: Planning Automatic planning



Field Value

Plan aspect 8XX

Plan version 1Plan period 001.1998 to 012.1998

Source data aspect 8XX

Source data plan/act. indic. Actual

Source data version 1

Source data period 001.1997 to 012.1997

Revaluation factor EXX

Extras test run Off

Extras log On

Extras backgr. processing Off

Update Without transfer rules, Overwrite

Click on ‘Choose characteristics’ and select the characteristic ‘Company’.Click on ‘Continue’. Select the key figure ‘Capital costs’ (‘Continue’) and setthe value block '10 – 20' for the company (‘Continue’).

Save the settings as variant ‘AutoXX’ .

Execute the automatic planning and check the log.



© SAP AG

R

A p p en d ix

This sect ion con tains supplem entary mater ialto b e used as reference

This m ater ial is no t par t of the s tandardcour se

Therefore, the instruc tor mig ht no t cover thisdur ing the cou rse presentat ion



Menu Paths AC620 EIS2 – Executive Information SystemData RetentionBelow the most important menu paths relevant to course AC620 are given in the order in which they appear in thecourse material.

The menu paths start from the EIS Application menu or the EIS Configuration menu.

You can find the Application menu under:

Accounting Enterprise controlling Executive information system

You can find the Configuration menu under:

Accounting Enterprise controlling Executive information system EnvironmentConfiguration menu

Data basis :

Create/change fixed characteristics:

Configuration menu: Data basis Fix. characteristics

Create/display/change aspects:

Configuration menu: Data basis Aspect Edit

Create/display/change characteristics:

Configuration menu: Data basis Characteristics Edit

Create master data for characteristics:

Application menu: Master data Characteristic values Maintain

Create/display/change basic key figures

Configuration menu: Data basis Basic key figures Edit

Edit comment table:

Configuration menu: Data basis Edit comment table

Create/change/display data on single record entry:

Application menu: Transaction data Data entry Maintain record

Create/change/display data entry layout:

Configuration menu: Data basis Data entry layout Create



Create derivations:

Configuration menu: Data basis Derivation

Maintain validations:

Configuration menu: Data basis Validations Maintain

Create calculated key figures:

Configuration menu: Data basis Key figures Maintain

Create planning layout:

Configuration menu: Planning Planning layouts Create

Create distribution key for planning:

Configuration menu: Planning Distribution key Create

Create revaluations for planning:

Configuration menu: Planning Revaluation Change

Interactive planning – change plan data:

Application menu: Planning Interactive planning Change plan data

Automatic planning:

Application menu: Planning Automatic planning

Execute summarization levels, data base statistics:

Data basis Summarization levels Database statistics

Define summarization levels:

Data basis Summarization levels Define levels

Structure summarization levels:

Data basis Summarization levels Structure levels



Data transfer

Standard data collection program:

Configuration menu: Data transfer Transaction data Data collection pr.

Create sender structure:

Configuration menu: Data transfer Transaction data Sender structure

Create transfer rules:

Configuration menu: Data transfer Transaction data Transfer rules

Maintain currency translation types for data transfers:

Configuration menu: Data transfer Transaction data Currency transl. type

Display data records:

Application menu: Transaction data Data entry Display data

Import files:

Application menu: Transaction data Transfers Import file

Define flexible Excel upload:

Configuration menu: Data transfer File name Def. Excel upload

Import data on flexible upload:

Application menu: Transaction data Transfers Flexible Upload

Execute aspect summarizations:

Configuration menu: Tools Data transfer Define aspect summ.

Application menu: Transaction data Transfers Summarize aspect

Maintain transfer methods:

Configuration menu: Data transfer External systems Transfer method

Display data transfer logs:

Application menu: Transaction data Transfers Transfer log



Maintain variants of data transfer procedures:

Configuration menu: Data transfer Transfer procedure Maintain variants

Define jobs:

Configuration menu: Data transfer Transfer procedure Define job

Au th or izat ion s:

Display/create authorizations:

Configuration menu: Tools User maintenance Authorizations

Maintain authorization profiles :

Configuration menu: Tools User maintenance Profiles

Documents

AC620 - Exexutive information system - Setting up the sysytem.pdf