fim admin guide

5/28/2018 FIM Admin Guide

1/128

Financial Information Management 10 Administration Guide

SAP BusinessObjects Financial Information Management 10

2012-03-08


2/128

2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAPBusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as

Copyright

well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and

other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports,Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of BusinessObjects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere,Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAPcompany. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National productspecifications may vary.These materials are subject to change without notice. These materials areprovided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products and servicesare those that are set forth in the express warranty statements accompanying such products andservices, if any. Nothing herein should be construed as constituting an additional warranty.

2012-03-08


3/128

Contents

Document History...................................................................................................................7Chapter 1

Financial Information Management Architecture....................................................................9Chapter 2

Financial Information Management Architecture.......................................................................92.1

System Landscape with the Planning and Consolidation Application for Microsoft...................92.1.1

System Landscape with the Profitability and Cost Management Application...........................102.1.2

System Landscape with the Planning and Consolidation Application for NetWeaver..............112.1.3

System Landscape with the Strategy Management Application..............................................112.1.4

System Landscape with the Financial Consolidation Application ............................................122.1.5

Oracle Requirements............................................................................................................15Chapter 3

Oracle Database Requirements..............................................................................................153.1

Oracle Installation Requirements............................................................................................163.2

Additional Requirements When Using an Oracle Database.....................................................163.2.1

Maximum Connections on an Oracle Server..........................................................................173.3

User Roles.............................................................................................................................19Chapter 4

Specific Configuration..........................................................................................................21Chapter 5

Configuring SSL.....................................................................................................................215.1

Installing SSL on Tomcat........................................................................................................215.1.1

Preparing the Certificate Store...............................................................................................225.1.2

Configuring Tomcat HTTPS....................................................................................................235.1.3

Configuring SSL for the Data Services Application................................................................235.1.4

Configuring Reverse Proxy Servers for SAP BusinessObjects Financial InformationManagement..........................................................................................................................24

5.2

SAP BusinessObjects Financial Information Management Logs.............................................245.3

Configuring Tomcat for Production Environments...................................................................255.4

Configuring Server Groups....................................................................................................255.5

Configuring the Active Directory............................................................................................265.6

2012-03-083


4/128

Financial Information Management Application Parameters.................................................29Chapter 6

Configuring the Number of Lines in a Flat File Preview ..........................................................296.1

Configuring Time-out Parameters...........................................................................................296.2Increasing the Number of Lines Displayed in Job Run History................................................296.3

Custom Jobs.........................................................................................................................31Chapter 7

About Data Services Job Customization................................................................................317.1

Dataflows...............................................................................................................................317.1.1

Data Services Objects...........................................................................................................337.1.2

Global Variables.....................................................................................................................347.1.3

Repository Tables..................................................................................................................357.1.4

Customizing a Data Services Job...........................................................................................367.2

Publishing a Data Services Job to Web Services...................................................................367.2.1Connecting to a Data Services Job........................................................................................377.2.2

Modifying the Data Services Job...........................................................................................377.2.3

Importing a Custom Job.........................................................................................................387.3

Importing a Financial Information Management Job................................................................387.3.1

Batch Job Publishing..............................................................................................................397.4

Using the Financial Information Management Application with SAP NetWeaver BW..........41Chapter 8

Using the Financial Information Management Application with SAP NetWeaver Business

Warehouse............................................................................................................................41

8.1

Moving Data to and from SAP NetWeaver BW .....................................................................418.2

Overview: Setting Up the Connection Between SAP BW and the Financial Information Mangement

Application.............................................................................................................................42

8.3

Creating an RFC Connection.................................................................................................438.3.1

Creating a New RFC Server Interface....................................................................................448.3.2

Testing the RFC Connection..................................................................................................458.3.3

Creating the Open Hub Connection ......................................................................................468.3.4

Activating the Open Hub Connection.....................................................................................488.3.5

Creating the Transformation...................................................................................................488.3.6

Creating a Data Transfer Process..........................................................................................488.3.7

Creating a Datastore in the Financial Information Management Application............................498.3.8Creating a Process Chain.......................................................................................................508.3.9

Creating a Process Variant....................................................................................................508.3.10

Creating a Financial Information Management Job.................................................................508.4

Configuring Masterdata Browsing..........................................................................................528.5

2012-03-084

Contents


5/128


6/128

2012-03-086

Contents


7/128

Document History

The following table provides an overview of the most important changes to this document.

DescriptionDateVersion

Initial versionOctober 20101.0

Added information on configuring the Active DirectoryJune 20111.1

Added information on enriching the ECC datasource list

Added architecture diagrams

August 20111.2

Fixed bug to add proceduro on importing a financial informationmanagement job.

February 20121.3

2012-03-087

Document History


8/128

2012-03-088

Document History


9/128

Financial Information Management Architecture

2.1 Financial Information Management Architecture

The overall architecture resembles the following schematic:

Figure 2-1: SAP BusinessObjects Financial Information Management Architecture

2.1.1 System Landscape with the Planning and Consolidation Application for Microsoft

This schematic shows a detailed view of the financial information management architecture for theplanning and consolidation application for Microsoft:

2012-03-089



10/128


11/128

2.1.3 System Landscape with the Planning and Consolidation Application forNetWeaver

This schematic shows a detailed view of the financial information management architecture for theplanning and consolidation application for NetWeaver:

2.1.4 System Landscape with the Strategy Management Application

This schematic shows a detailed view of the financial information management architecture for thestrategy management application:

2012-03-0811



12/128

2.1.5 System Landscape with the Financial Consolidation Application

The following schematic shows a detailed view of the financial information management architecturefor the financial consolidation solution. Note that the web service interface in the financial consolidationapplication, leveraged by the financial information management application, is not installed by default.

2012-03-0812



13/128

2012-03-0813



14/128

2012-03-0814



15/128

Oracle Requirements

This section describes the requirements when using Oracle databases with SAP BusinessObjectsFinancial Information Management 10.0.

3.1 Oracle Database Requirements

Note the following Oracle database requirements:

The database must be configured in the decidated server mode. SAP BusinessObjects FinancialInformation Management does not support the shared server mode, formerly known as themulti-threaded server mode.

The character set recommended for an SAP BusinessObjects Financial Information Managementdatabase is AL32UTF8. The national character set recommended is UTF8.

When the database is configured inthe archive log mode, sufficient disk space is must be availablefor the archived redo logs. The system must be sized appropriately to support the system overheadassociated with archiving.

Oracle client settings must be changed on the on the SAP BusinessObjects Financial Information

Management application server. See the SAP BusinessObjects Financial Information ManagementInstallation Guide for information on configuring the Oracle elient. Identical settings can also beapplied to the Oracle server to avoid configuring the Oracle client on all the application servers.

SAP BusinessObjects Financial Information Management uses a single Oracle account to store all itsdatabase objects and to manage all its connections to the Oracle server. Multiple simultaneousconnections to the server are established with this single user account at any given time. Differentschemas to separate development and production environments can coexist in the same database.

The Oracle user account requires the following privileges:

CONNECT

RESOURCE

If your company's security policy prevents you from applying the above-mentioned privileges, you cangrant privileges as follows:

CREATE

CREATE TABLE

CREATE SEQUENCE

CREATE CLUSTER

CREATE TYPE

2012-03-0815

Oracle Requirements


16/128

For customization projects, the following additional privileges may be required:

CREATE PROCEDURE

CREATE TRIGGER

CREATE VIEWTip:SAP Technical Support can provide an Oracle Database Configuration Assistant template or a sampledatabase creation script and initialization parameter file customized for SAP BusinessObjects FinancialInformation Management, which can be edited to suit the requirements of your site.

Caution:You must not assign theSELECT ANY TABLEprivilege or assign a role including this privilege for

example, DBA, to the owner of the schema.

Note:Consult the Oracle Database Administrator's Guide for information on server mode configuration,archiving, and other database administration topics.

3.2 Oracle Installation Requirements

The following components are required when you install the Oracle database:

the Oracle server on the DBMS server

the Oracle client with the Oracle provider for OleDB on the application servers

All the other components are optional. The Oracle Corporation recommends that you upgrade yourclient software to match the current server software and use the latest patch releases.

Tip:We recommend that you install the client layer delivered with your database engine on the applicationserver.

Note:For more information on the operating systems supported, recommended patches, and installationprocedures, see the Oracle website at:http://www.oracle.com.

3.2.1 Additional Requirements When Using an Oracle Database

If your financial information management repository is an Oracle instance you need to add the path tothe location where the tnsnames.orafile is hosted. You add this information on the Java page of the

Apache Tomcat Properties dialog box under "Java options", for example,-Doracle.net.tns_admin=C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN

2012-03-0816

Oracle Requirements
http://www.oracle.com/http://www.oracle.com/


17/128

3.3 Maximum Connections on an Oracle Server

When using an Oracle server, you need to set the maximum number of connections in the OracleConsole under "Session":

altersystem set sessions =NbSession scope=spfile;

where NbSession must be equal to 8 x Number of jobs x maximum number of mapping tables in a injob.

2012-03-0817

Oracle Requirements


18/128

2012-03-0818

Oracle Requirements


19/128

User Roles

The user roles in the financial information management solution are the following:

Administrator, who creates and maintains databaseand application datastores. Administratorshaveaccess to all jobs defined in the platform.

The administrator may be, but is not required to be, the person who installsand manages the financialinformation management system.

Business user

Auditor

Executor

The principal user roles are summarized as follows:

AuditorBusiness UserExecutorAdministratorAction

XXXXView list of jobs

XXXXView job definition

XXCreate jobs

XXExport jobs

X (when owner ofjob)

XDelete jobs

XXXXView mapping tables

XXModify mapping tables

XXImport jobs

XXXExecute jobs

XXXSchedule jobs

2012-03-0819

User Roles


20/128

AuditorBusiness UserExecutorAdministratorAction

XX (who executed

the job)

XXView job results and audit

trail

X (who executedthe job)

XView extended data serviceslogs

XXXXDrill-to-origin

XCreate datastores to EPMapplications

X

Delete datastores

XView deleted jobs

Users and user groups are created in the CMS (Central Management Server) by the administrator whois responsible for installing and configuring the financial information management solution. Auditorsandadministratorssee all jobs. Business users andexecutors see jobs according to permissions grantedto them at the job level. Job results, audit trails, and extended data service logs can be viewed only bythe business user or executor who executed the job. If this person did not execute the job, he can viewonly the monitor log. A business user can delete only the jobs of which he is the owner.

2012-03-0820

User Roles


21/128

Specific Configuration

5.1 Configuring SSL

You use the Secure Sockets Layer (SSL) protocol for all network communication between clients andservers in your SAP BusinessObjects Financial Information Management deployment.

To set up SSL for all server communication you must perform the following steps:1. Install SSL on SAP BusinessObjects Enterprise XI

2. Configure CORBA SSL on SAP BusinessObjects Enterprise XI.

3. Install SSL on the SAP BusinessObjects EPM system to which you want the financial informationmanagement application to connect, for example, SAP BusinessObjects Financial Consolidation,SAP BusinessObjects Intercompany, or SAP BusinessObjects Planning and Consolidation.

4. Configure CORBA SSL communication on the financial consolidation server or on the intercompanyserver.

5. Configure the financial consolidation application web service HTTPS. If you are using SAPBusinessObjects Intercompany, configure the intercompany application to use HTTPS.

6. Install SSL on Tomcat.

7. Configure Tomcat HTTPS.

Note:Refer to the following guides for specific information on installing and configuring HTTPS:

The chapter on Securing SAP BusinessObjects Enterprisein theSAP BusinessObjects Administrator'sGuide

SAP BusinessObjects Financial Consolidation Installation Guide

SAP BusinessObjects Intercompany Installation Guide

5.1.1 Installing SSL on Tomcat

SSL on SAPBusinessObjects Financial InformationManagement requires a new installation of Tomcat.Do not use the Tomcat that is installed with SAP BusinessObjects Financial Information Management.

Before you begin installation and configuration of SSL on Tomcat, you need to do the following:

1. Create a folder %MYCERTFOLDER% (for example, D:\SSL) to store certificate files and keys.

2012-03-0821



22/128

2. Locate the following certificates and keys and paste them in the %MYCERTFOLDER% folder. Thecertificates and keys are:

server certificate %SERVERCERT%.der

CA certificate %CACERT%.der

server key %SERVER%.key

your passphrase %PASSPHRASE%.txt

When you have completed the above, you configure the CORBA SSL communication as follows:

1. Launch the Tomcat configuration tool.

2. SelectJava > Java options.

3. In Java options, add the following:

-Dbusinessobjects.orb.oci.protocol=ssl

-DcertDir=%MYCERTFOLDER%

-DtrustedCert=%CACERT%.der

-DsslCert=%CLIENTCERT%.der -DsslKey=%CLIENT%.key

-Dpassphrase=%PASSPHRASE%.txt

4. Close the Tomcat configuration tool.

5.1.2 Preparing the Certificate Store

The next step in configuring SSL for Tomcat is to prepare the certificate store.

1. Launch the command prompt.

2. Type the folllowing: %MYJDKBIN%keytool -genkey -alias tomcat -keyalg RSA -keysize

1024 -keystore %MYCERTFOLDER%\.keystore, which creates the keystore

Note:%MYKEYPASS% is the keystore password.

3. Type%MYJDKBIN%keytool -certreq -alias tomcat -file %MYTEMP%\tomcat.req -keystore %MYCERTFOLDER%\.keystore

4. Certify tomcat.req

5. Copy issued certificat %TOMCAT%.der to %MYCERTFOLCER%

6. In the command prompt, type%MYJDKBIN%keytool -import -alias tomcat -file %MYC

ERTFOLDER%\%TOMCAT%.der -trustcacerts -keystore %MYCERTFOLDER%\.keystore7. Copy the CA certificate used for the financial consolidation or intercompany application web service

HTTPS, %EPMCA%.der to %MYCERTFOLDER%

8. In the command prompt, type%MYJDKBIN%keytool -import -alias EPMCA -file %MYC

ERTFOLDER%\%EPMCA%.der -trustcacerts -keystore %MYCERTFOLDER%\.keystore

2012-03-0822



23/128

5.1.3 Configuring Tomcat HTTPS

To configure Tomcat proceed as follows:

1. Locate and open theserver.xmlfile in the Tomcat installation folder, %TOMCATDIR%\conf

2. Add the following:

3. Open the Tomcat configuration tool.

4. ClickJava> Java Options

5. Under Java Options add thefollowing: -Djavax.net.ssl.trustStore=%MYCERTFOLDER%\.key

store -Djavax.net.ssl.trustStorePassword=%MYKEYPASS%6. Restart Tomcat.

5.1.4 Configuring SSL for the Data Services Application

At runtime, you need to configure the folllowing file: axis2.xml which is located in the following directory

on the machine on which SAP BusinessObjects Data Services is installed:%DataServicesInstallDir%\ext\webservice-c\ .

You configure the file as follows:

1. Un-comment the https transport receiver and https transport sender section in theaxis2/cfile asshown in the following example:

6060false

HTTP/1.1

2. Type the SERVER_CERTpath as shown in the following example: /path/to/ca/SAPNETCA.der

2012-03-0823



24/128

5.2 Configuring Reverse Proxy Servers for SAP BusinessObjects Financial Information

Management

The SAP BusinessObjects Enterprise Performance Management applications use a Single Sign On(SSO) mechanism between web applications.

SSO allows a user to sign on to one EPM web application and then use other EPM web applicationswithout having to re-enter credentials. For example, a user enters credentials to connect to SAPBusinessObjects Financial Consolidation and receives an SAP BusinessObjects Enterprise XI sessioncookie. From SAP BusinessObjects Financial Consolidation, he goes to the SAP BusinessObjectsFinancial Information Management application with the same browser session, and does not need tore-enter credentials, because he is logged on automatically. The SAP BusinessObjects Enterprise XI

session cookie is reused automatically.A reverse proxyserver is mandatory if you want to use single sign-on (SSO)unless all server componentsare installed on the same machine (which is not recommended).

For SSO to work, follow this procedure:

Use the same URL domain name for all SAP BusinessObjects EPM applications web sites in thefollowing cases:

All EPM web servers must be installed on the same physical server

Each web application is installed on a separate servers and all URLs are published on the samereverse proxy server.

5.3 SAP BusinessObjects Financial Information Management Logs

The financial information management application provides the trace.inifile in which you set

parameters for the trace logs. Trace logs are located at the root of the C:\ directory as*.glf files.The file names begin withTraceLog

The trace.ini file is located in theWEB-INF folder in the financial information managementapplication.

It contains the following parameters, which can be modified:

active = true importance=,in which you set the logging levels in decreasing verbosity

Note:>>corresponds to DEBUG mode

log_dir = "C:"

2012-03-0824



25/128

The Tomcat logs are located in the Logssubdirectory of theTomcat server on the financial informationmanagement server with the file name stdout.logConsulting the Tomcat logs can help you in

troubleshooting the application.

5.4 Configuring Tomcat for Production Environments

If you are using SAP BusinessObjects Financial Information Management in a production environment,you should change the maximum memory of the Tomcat application.

1. SelectStart > All programs > Tomcat configurationand click theJavatab.

The following dialog box opens.

2. In theInitial memory poolfield, enter a number that is at least 64 MB and up to 100 MB.

3. In theMaximum memory poolfield, enter a number that represents up to 80% of your computer'sRAM. For example, if you have 512 MB of RAM, set the maximum memory to 400 MB.

4. ClickApplyandOK.

5.5 Configuring Server Groups

2012-03-0825



26/128

You can distribute the execution of a job or of part of a job across multiple job servers within a servergroup, which allows you to better balance resource-intensive job servers to the job server with thelightest load at runtime.

When using a group of servers, you need to install a complete version of the data services applicationon the financial information management server. You then configure theservergroup In theadministrationconsole under Data Services information as follows: ServerGroupName;inet:ServerDataServicesName:3500;inet:%SERVER2%:%PORT2%;...

Data services setup allows you to install client, server, and web tier components. In this diagram, nodata services job server is running on the financial information management server.

The financial information management server uses al_engine.exeto import the ATL job definitionto the data services repository. It uses al_RWJobLauncher.exeto fire the execution of the data

services job that will be processed by one of the job servers in the server group. Server group is a newparameter passed to al_RWJobLauncher.exeby financial information management.

For more detailed information on server groups, refer to the SAP BusinessObjects Data ServicesManagement Console: Administrator Guidefrom the SAP Help Portal athttps://help.sap.com

5.6 Configuring the Active Directory

If you are using an active directory, you need to perform the following configuration steps:

1. Create the following files and copy them toC:\Windowson the financial information managementserver:

bscLogin.confExample:

com.businessobjects.security.jgss.initiate {com.sun.security.auth.module.Krb5LoginModule required;};

krb5.ini

Note:You must configure the domains that you are using and put them in this file. It is important tomaintain consistent case sensitivity for the domainname throughout your setup. We recommendyou use CAPS implementation.

Example:

\[libdefaults\]default_realm = PNR2K8TEST01.COMdns_lookup_kdc = truedns_lookup_realm = trueforwardable = true\[realms\]PNR2K8TEST01.COM = {default_domain = PNR2K8TEST01.COMkdc = VANPGC8B2.PNR2K8TEST01.COMforwardable = true}

2012-03-0826

https://help.sap.com/https://help.sap.com/


27/128

2. In FIM Tomcat Config, add the paths to the configuration files:

bscLogin.conf

krb5.ini

-Djava.security.auth.login.config=C:\WINDOWS\bscLogin.conf

-Djava.security.krb5.conf=C:\WINDOWS\krb5.ini

2012-03-0827



28/128

2012-03-0828



29/128

Financial Information Management ApplicationParameters

6.1 Configuring the Number of Lines in a Flat File Preview

When uploading a flat file, by default only the first 100 lines are displayed when using the File Preview

option. You may change this default value. To change thedefault value of the maximum rows displayed:1. Open the server.xmlfile located inC:\Program Files\Business

Objects\Tomcat6\webapps\fim\WEB-INF .

2. In the section, locate the following line:

3. Increase the value of the maxPreviewRowNumberparameter (by default, it is set to 100 rows).

4. Save and close the file.

5. Restart the Apache Tomcat service.

6.2 Configuring Time-out Parameters

You can modify default time-out values for the financial information management server and client asfollows:

in server.xml

connectionTimeout: Timeout in milliseconds to connect to Data Services executionWebService. (Default120 000 milliseconds)

receiveTimeout: Timeout in milliseconds to receive result from Data Services execution Web Service.(Default 300 000 milliseconds)

6.3 Increasing the Number of Lines Displayed in Job Run History

2012-03-0829

Financial Information Management Application Parameters


30/128

You can increase the number of lines displayed in the job run history by modifying the maxRetrieveparameter on the jobExecutionbean in the server.xmlfile as shown here:

For example, if you want to increase the number of lines displayed to 400, set the maxRetrieve valueas follows:

The maxRetrieve value is valid for three tables on the Job Run History page. Each table returns thesame maximum number of lines:

Unmapped Lines

Rejected Lines

Imported Lines

Figure 6-1: Rows Limited to 200 Lines

2012-03-0830

Financial Information Management Application Parameters


31/128

Custom Jobs

7.1 About Data Services Job Customization

The financial information management solution is a business user interface on top of the data servicesapplication. The financial information management solution loads data into the EPM (EnterprisePerformance Management) applications. It generates data services jobs that business users launch

from the financial information management interface.

The data services jobs can be customized at the data services level to benefit from the features offeredby thedata services solution, such as broad connectivity to information systems and scripting language.

Note:Using this feature requires in-depth knowledge of SAP BusinessObjects Data Services, and therefore,is limited to technical users.

Related Topics

Customizing a Data Services Job

Data Services Objects

Global VariablesRepository Tables

7.1.1 Dataflows

The generated data services jobs is composed of a sequence of dataflows as follows:

An export dataflow, responsible for extracting the required data from the source of the financialinformation management job, and applying the runtime filters

A transform dataflow, responsible for applying the mapping rules, and identifying themapping errors

A load dataflow, responsible for loading the data to the target application of the financial informationmanagement job, and identifying the rejected rows by the target application.

On the left of the SAP BusinessObjects Data Services Designer window the following components ofa data services project are displayed:

Under "Project Area" the data services project generated by the financial information managementapplication, with the three dataflows

2012-03-0831

Custom Jobs


32/128

Note:The job that was created has the same name as the job name assigned in the financial informationmanagement application.

Under "Datastore", the various datastores including those created by the job

On the right side of the designer, a schematic of the dataflows is displayed.

For detailed information on dataflows, refer to the SAP BusinessObjects Data Services documentation.

7.1.1.1 The Export Dataflow

The export dataflow is dedicated to extracting data from a source.

The following image shows the export dataflow in the data services designer.

The database table is was selected in the financial information management application. The sourcetable in the schematic is a temporary table used to exchange data.

7.1.1.2 The Transform Dataflow

The transform dataflow takes the data and applies the mappings defined in the financial informationapplication.

The validation controls shown in the diagram make sure that every line in the table was translated usingat least one mapping rule. If this is not the case, the line has a null value and the data services applicationpushes the row in to the mapping error table in the financial information management repository.

The data is passed to the transaction table, which is used in the drill-to-origin function. The transactiontable contains the data with its definition before and after mappings.

2012-03-0832

Custom Jobs


33/128

7.1.1.3 The Load Dataflow

The load dataflow is dedicated to loading data into the target system. It take data from the transactiontable and prepares the data for the web services call. It then gathers the output from the web servicescall and ascertains if there is a problem. Rejected rows are stored in tables in the financial informationmanagement repository.

You can view the details generated by the load dataflow on the "Job Run History" page.

7.1.2 Data Services Objects

When you create a job using the financial information management interface, data services jobs aregenerated in the data services repository. In this table you need to replacejobNameby the name ofthe financial information management job that you created. The job name in financial informationmanagement is limited to 8 characters.

Data Services Object NameDescription

PROJECT_%jobName%DS Project Name

%jobName%DS Job Name

DF_EXPORT_%jobName%Export DS DataFlow

DF_TRANSFORM_%jobName%Transform DS Data Flow

DF_LOAD_%jobName%Load DS DataFlow

%jobName%_DSFinancial information management repository DBDS DataStore Name

%jobName%_FILE_EXPORT_DSFile Export DS DataStore Name

2012-03-0833

Custom Jobs


34/128

Data Services Object NameDescription

%jobName%_TABLE_EXPORT_DSTable Export DS DataStore Name

%jobName%_FC_LOAD_DSFC Load Web Service DS DataStore Name

%jobName%_PCM_LOAD_WS_DSPCM Load Web Service DS DataStore Name

%jobName%_FC_LOAD_TABLE_DSPCM Repository DS DataStore Name

7.1.3 Global Variables

Creating a financial information management job also creates, as part of the job definition, a list ofglobal variables. These variables are set at runtime when the business user launches the job throughthe financial information management interface.

Table 7-2: Global Variables

DS Global Variable NameDescription

$JOB_RUN_IDFinancial Information Management JobRun ID

$SerializedSessionBOE SSO logon token

$UserBOE user name

$PasswordBOE user password

$Filter_%SourceDimensionName%Filters on Source Dimensions

$aggregateAmounts, etc .Target Application Options

The following image shows the variables as they appear in thedata services application interface. Whenyou execute a job in the financial information management application, you set runtime parameters.

Their equivalent appears in the list of global variables in the data services application.

A generated data services job also contains the list of available filters found in the financial informationmanagement application.

The JOB_RUN_IDis an autogenerated number assigned to an instance of a job when it is run. Eachtime a job is run, a new ID is assigned to the instance.

2012-03-0834

Custom Jobs


35/128

7.1.4 Repository Tables

When you create a job using the financial information management interface, data services jobs aregenerated in the data services repository. In this table you need to replace jobName by the name ofthe financial information management job that you created. The job name in financial informationmanagement is limited to 8 characters.

Financial Information Management Repository Table NameDescription

SOURCE_%jobName%Source Table Name

TRANSACTION_%jobName%Transaction Table Name

SC_%DimName%Source Column in Transaction Table

FIM_%jobName%_%MappingTableName%Mapping Tables

MAPPING_ERRORS_%jobName%Mapping Errors Table

2012-03-0835

Custom Jobs


36/128

The source table is created in the financial information management repository to store the extractedrows from the source. This table is not mandatory. The generated data services job can be customizedto eliminate this staging area.

The transaction table is created in the financial information management repository to store the outputof every successfully-applied mapping. The transaction table contains mappings from every source setof data to every target set of data.

The transaction table is queried when you use the drill-to-origin feature from the target application todisplay the origin of data.

Note:The data services job is responsible for populating transaction tables. The financial informationmanagement application never writes to these tables directly.

Generated data services jobs use the following other financial information management repositorytables:

Financial Information Management RepositoryTable Name

Description

FIM_REJECTED_ROWRejected Rows Table Name

FIM_JOB_RUN_PACKAGE_STATUSJob Run Status

7.2 Customizing a Data Services Job

To customize a data services job, you must perform the following steps, which are explained in greaterdetail:

1. Create and execute a financial information management job.

The financial information management application generates a corresponding data services job.

2. Via the data services management console, publish the generated data services job to the webservices.

3. In the financial information management application, connect to the data services job.

4. In the data services application, modify the data services job to suit your requirements.

5. In the financial information management application, execute the job.

7.2.1 Publishing a Data Services Job to Web Services

2012-03-0836

Custom Jobs


37/128

1. From the Start menu clickSAP BusinessObjects XI 4.0 > BusinessObjects Data Services > DataServices Management Console, then log in.

2. Click "Administrator".

3. On the left side of the page under "Administrator", click "Web Services".4. On the right side of the page, click the "Web Services Configuration" tab.

A list of published web service operations appears on the page.

5. In the box, selectAdd Batch Job..., then clickApply.

6. In the next page, select the job, then clickAdd.

Below the "Web Services Configuration" tab, a message appears indicating that the web serviceprovider for the batch job was successfully added.

You have successfully published the data services job to web services. You can close the window.

7.2.2 Connecting to a Data Services Job

When you connect to an existing data services job, you tell the financial information managementapplication that this is an external job. Theapplicationdoes not modify or erase thecustomized version.

1. In the financial information management application, under "List of Jobs" select and open the jobthat you want to modify.

2. On the "Properties" page, select "Connect to an existing SAP BusinessObjects Data Services job".

3. Select the job that you want to modify from the list, which displays all the jobs that were publishedto web services.

By default, thenamesof the transaction table and thevalidation error table appear in theappropriateboxes.

4. ClickSave.

Note:Do not clickExecuteuntil after you have modified the job in the data services application.

7.2.3 Modifying the Data Services Job

After you haveconnected to the data services job from the financial informationmanagement application,you go to the data services application to customize the job.

1. In the data services designer, open the project.

2. In the main page, make the changes using the data services features such as creating a script tosend an email when a job has been completed.

3. Save your modified job.

2012-03-0837

Custom Jobs


38/128

Note:Once you have modified and saved the job, you must return to the financial information managementapplication to execute the job.

7.3 Importing a Custom Job

When you export a job, the underlying data services job is not exported. If you have created a customdata services job, you need to export the custom job and then import it as follows:

1. In "DataServices Designer" log in to the source data services repository.

2. Right click in the local object library>> Repository >> Export to file. Include the datastores usedthe first time the job is moved from the source data services repository to the target data services

repositoryExporting to file generates anATLfile.

3. Through "DataServices Designer "log in to the target data services repository and import the ATLfile.

Note: If this is the first time the custom job is moved to the target environment, you need to modifythe datastore properties to point to the correct environment. This is particularly true for the datastorepointing to the financial information management repository.

4. In the "Data Services Management Console", verify sure that the web services URL is correct.

After you have exported the custom job, import the job as explained in Importinga Financial InformationManagement Job

7.3.1 Importing a Financial Information Management Job

Before you attempt to import a job, note that flat files cannot be imported. If you are using a flat file asa source of data, you must copy the flat file located in the upload file folder of the server from whichyou are exporting the job to the upload file folder of the server to which you are importing the job. Theupload file folder is defined in the administration console.

To import a job:

1. On the Homepage under "List of Jobs" select the job you want to import, then clickImport.2. In the "Import Objects" screen clickBrowseto locate the xmlsource file of the import.

3. ClickNext.

The Select Objects screen lists the objects that you can import. If the object already exists, thisinformation is displayed in the "Already exist" column. If the object already exists in the financialinformation management environment and you select "Import", the existing object is overwritten bythe import.

2012-03-0838

Custom Jobs


39/128

4. ClickNext.

The financial information management job or jobs are imported and the underlying data servicesjobs are regenerated. The results are displayed in the "Import Result" screen.

Note:Press CTRL + Shift to select more than one job to export or import.

Note:When you import datastore that has the same name as an existing datastore, regardless of the case,the existing objects are updated. Therefore, we highly recommend that, when moving job definitionsfrom one environment to another, you use the same datastore name and that the connection namesbe written in the same case. When working with Oracle databases, datastore names must be writtenin upper case.

7.4 Batch Job Publishing

To execute custom, jobs for specific scenarios, use a web service that enables batch job publishing.Those batch jobs are executed by the SAP BusinessObjects Financial Information Management jobs.You select the Add Batch Job...option in the SAP BusinessObjects Data Services ManagementConsole as shown here:

Figure 7-1: Batch Job Publishing

2012-03-0839

Custom Jobs


40/128

Note:

Selecting theAdd Batch Job...option is necessary only for external jobs. If you are planning toexecute native jobs, you do not need to publish the web services.

For detailed information on creating batch jobs in the data services application consult the dataservices documentation available from the SAP BusinessObjects Solution Portfolio KnowledgeCenter athttp://help.sap.comSAP BusinessObjects > All Products

2012-03-0840

Custom Jobs
http://help.sap.com/http://help.sap.com/


41/128

Using the Financial Information Management Applicationwith SAP NetWeaver BW

8.1 Using the Financial Information Management Application with SAP NetWeaverBusiness Warehouse.

The financial information management application is the tool used to move data either from SAPNetWeaver Business Warehouse to an SAP EPM application, or from a SAP EPM application to SAPNetweaver Business Warehouse.

The business user selects SAP NetWeaver BW as either the source or target application in the financialinformation management application.

Before the user can select the source and target applications, however, certain preliminary steps mustbe performed by the administrator in the NetWeaver BW application as well as in the data servicesapplication. This section describes these mandatory steps.

8.2 Moving Data to and from SAP NetWeaver BW

The financial information management application lets you extract data from an SAP BusinessObjectsEPM application and import it into SAP Netweaver Business Warehouse specifically into the PersistentStorage Area. Data can also be extracted from SAP Netweaver BW and imported into one of the SAPEPM applications:

SAP BusinessObjects Financial Consolidation

SAP BusinessObjects Intercompany

Data is imported into the SAP Netweaver BW server using the BAPI interface, that is, the SAP-certified

interface leveraged by the data services application.

This diagram illustrates the application environment:

2012-03-0841

Using the Financial Information Management Application with SAP NetWeaver BW


42/128

Figure 8-1: SAP NetWeaver BW in the SAP BusinessObjects Enterprise Environment

Data is extracted from the SAP Netweaver BW server using the Netweaver Open Hub interface. Theopen hub service enables you to distribute data from an SAP BW system into external data marts,analytical applications, and other applications.

SAP BusinessObjects Data Services XI 4.0provides the functionnality to trigger an Open Hub extractionthat the financial informaition management application leverages to provide an end-to end solution.

To provide the end to end scenario this will require the following version of SAP Netweaver BW: in SAPBW 7.01 patch level 003 and above.

As a pre-requisite, the following SAP Notes must be implemented before using this feature:

SAP Note 1270828, 1294774: Resolves table import issues.

SAP Note 1330568 version 3: Resolves table reading issues.

For the latest information about Open Hub, refer to SAP Note 1343606 in the SAP Service Marketplace.The note can be accessed athttps://service.sap.com/sap/support/notes/1343606

8.3 Overview: Setting Up the Connection Between SAP BW and the FinancialInformation Mangement Application

Before you can begin extracting data from SAP Netweaver Business Warehouse, that is, using the

application as the source of your data, you need to set up a connection. The overall steps in creatingan SAP NetWeaver BW connection are as follows:

1. Create an RFC Connection on the SAP NW backend to the Data Services RFC server.

2. Create a new RFC Interface in the Data Services Management Console, and start the server.

3. Activate the RFC Connection.

4. Create and activate the open hub destination via the Data Warehousing Workbench.

5. Create a transformation.

6. Create a data transfer process.

2012-03-0842

https://service.sap.com/sap/support/notes/1343606https://service.sap.com/sap/support/notes/1343606


43/128

7. Create a datastore with SAP NetWeaver BW as source.

8. Create a process chain.

8.3.1 Creating an RFC Connection

First you create an RFC connection on the SAP NW back-end to the Data Services RFC server.

1. From the SAP client application, launch the transaction SM 59.

2. In the "RFC Destination" screen, in the "Connection Type" box, selectTCPIP Connection.

3. Under the "Technical Settings" tab, enter a program ID. The Program ID must match the one definedfor the RFC server interface of DataServices.

4. Click theSaveicon.

2012-03-0843



44/128

The next step is to launch the "Data Services Console" to create a new RFC server interface.

8.3.2 Creating a New RFC Server Interface

You create the RFC server interface from the "Data Services Management Console".

1. Under "SAP Connections", select "RFC Server Interface".

2. Click the "RFC Server Interface Configuration" tab.

3. ClickAdd.

A new tab opens that contains the RFC program ID that matches the ID defined on the BW back-end.At this point, you can modify the server configuration details, which are as follows:

RFC ProgramID

User name

Password

SAP Application Server name

Client number

System Number

SAP Gateway Host name

SAP Gateway Service name

Note:

The Application Server name and the Gateway host name must match. Leave the SAP GatewayServices name as default.

2012-03-0844



45/128

4. ClickApply.

5. Under the RFC Server Interface Status tab, select the server name, then clickStart.

You have created and started the RFC server interface on the Data Services server.

8.3.3 Testing the RFC Connection

Returning to the SM59 SAP transaction, open the connection.

Click Connection Test. Testing theconnectionsvalidatesyour configuration. The name of theconnectionand the type appear on the page along with the actions and results of the test.

2012-03-0845



46/128

Under "Configuration of RFC Connections", you can see the name of the server under "TCP/IPConnections"

8.3.4 Creating the Open Hub Connection

Make sure you have this version of SAP BW 7.01 patch level 003 or higher.

1. Launch transaction RSA1, which is the Data Warehousing Workbench.

2. Enter your login credentials where prompted.

3. Under "Modeling", select "Open Hub Destination".

4. Under "Open Hub Destination", right-click the info area in which you want to create the open hub,and select "Create Open Hub Destination" from the menu.

2012-03-0846



47/128

5. In the "Create Open Hub Destination" screen, select the Destination.

6. Enter the following information:

InfoArea

InfoCube

Name

The template you select is used to create the output structure of the extraction.

7. Click the check mark to validate.

A new screen opens.

8. Under the "Destination" tab, do the following:

Select "Third-Party Tool" as the "Destination Type"

In the" RFC Destination "box, type the name of the RFC connection that you created.

9. ClickSave.

2012-03-0847



48/128

8.3.5 Activating the Open Hub Connection

Once created, the open hub destination is inactive.

Check and save your work , and then click the Activate icon .

8.3.6 Creating the Transformation

You create the transformation in the "Open Hub Change: Overview "screen as follows:

1. Under "Open Hub Destination", select the name of the destination that you just created.

2. Right-click and select "Create Transformation..." from the menu.

3. In the Create Transformation screen select the following under Target of the Transformation:

Object Type

Name

4. Under Source of the Transformation select the following:

Object Type

Name

The InfoCube must be the same a s the source of the transformation.

5. Click the check mark to save the transformation.

Once created, the transformation is inactive, shown by the white icon. Click Activate. The icon turnsgreen. A message appears on the bottom of the screen: "Transformation activated successfully".

8.3.7 Creating a Data Transfer Process

The next step is to create the data transfer process, which embeds the transformation.

You create the Data Transfer Process in the Transformation Change screen.

1. Under "Open Hub Destination", select the cube and right-click.

2. Select "Create Data Transfer Process" from the menu.

The required data appears in the Creation of "Data Transfer Process" screen as folows:

Data Transfer Proc

DTP Type

2012-03-0848



49/128

Target of DTP Object Type

Target of DTP Name

Source of DTP Object Type

Source of DTP Name

3. Click the check mark to validate this information.

4. In the next screen, Change Data Transfer Process, on the right side, select one of two extractionmodes:

Delta

Full

5. Save and activate the DTP.

8.3.8 Creating a Datastore in the Financial Information Management Application

The next step is to create an SAP NetWeaver BW datastore in the financial information managementapplication.

8.3.8.1 Creating an SAP NetWeaver BW Datastore

You must be an administrator and be declared in the "Data Services Administrator Users" group in theCMC to create a datastore.

To create a datastore proceed as follows:

1. On the "Home" page, under "List of Datastores", clickNew.

2. Under "Datastore type" select "SAP NetWeaver BW".

3. ClickNext.

4. In the "Application server" box, select the application server to which you want to connect. The listof available application servers corresponds to the RFC connections that were created in the dataservices application during configuration.

5. In the "Routing string" box, enter a value as follows:

the default value, /H/if no SAP router is required

/H/hostname/s/portif a simple router string is required.

The port is 3300 plus the SAP system number.

6. Enter the User name and "Password" required to access the SAP NetWeaver BW system.

7. Test the connection.

2012-03-0849



50/128

8. ClickFinish.

8.3.9 Creating a Process Chain

It is not possible to execute a Data Transfer Process (DTP) remotely, via BAPIs, so you need to createa process chain. Often the process chain is used only to start the DTP.

1. In the modeling view of the Data Warehousing Workbench, click Process Chains.

2. In the Process Chain Display Pl screen, clickCreate.

3. In theNew Process Chainscreen enter a name and a description:

4. Click the check mark to validate.

5. In the Insert Start Process screen, clickCreatethen validate.

6. In the "Maintain Start Process" screen, set the "Scheduling Option" to "Start Using Meta Chain orAPI"

This is not the default value.

7. Click theSaveicon.

Note:The next step is to call the execution of the data process chain.

8.3.10 Creating a Process Variant

The process variant is the starting point of the process chain.

1. Under "Insert Start Process", clickCreate.

2. Under "Start Process", enter a name and a long description for the process variant, then click thecheck mark.

3. Under "Maintain Start Process" set the scheduling option to "Start Using Meta Chain or API", whichis not the default value.

4. Click the check mark.

The process chain is created.

The next step is to call the execution of the Data Transfer Process.

8.4 Creating a Financial Information Management Job

2012-03-0850



51/128

1. Under List of Jobs, selectNew.

2. Enter a name for the job and a description.

3. From the list of available users, select the users then clickNext.

4. Select the following to the source data: Datastore

Open Hub Destination

Process Chain

Then clickNext.

5. Select the target datastore.

6.

Select the source and target dimensions, which create the mapping table.

7. ClickFinish.

2012-03-0851



52/128

The job you created appears in the List of Jobs in the financial information management application.The next step is to populate the mapping table. Refer to the online help in the application for informationon populating the mapping table.

8.5 Configuring Masterdata Browsing

To permit masterdata browsing in SAP BusinessObjects Financial Information Management you needto meet the following criteria:

the Open Hub destination structure references InfoObject templates. The application then browsesthe characteristics declared as InfoObject templates.

Figure 8-2: The Open Hub Desination Display

The Characteristic is declared as InfoProvider

2012-03-0852



53/128

Figure 8-3: Characteristic Declared as InfoProvider

2012-03-0853



54/128

2012-03-0854



55/128

Using the Financial Information Management Applicationwith SAP ERP

9.1 Accessing SAP ERP Central Component (ECC Data)

Thereareseveral methods of accessingSAPECCdata using SAPBusinessObjects Financial Information

Management. Each method is explained in this chapter.

The methods are listed in order of recommendation as follows:

Accessing SAP ECC data through SAP NetWeaver BW

Direct access to SAP ECC using financial information management native jobs

Direct access to SAP ECC using Data Services connectors

9.1.1 Accessing SAP ECC Data Through SAP NetWeaver BW

We recommed that you access SAP ECC data through SAP NetWeaver BW when possible. Thisscenario implies that you have SAP NetWeaver BW installed:

Figure 9-1: Acessing SAP ECC Data Through SAP NetWeaver BW

Accessing ECC data through NetWeaver BW leverages the tight SAP ECC / SAP NetWeaver BWintegration. This integration leverages the SAPECC datasources, or Business Suite content extractors,and their delta extraction capabilities when they exist.

2012-03-0855

Using the Financial Information Management Application with SAP ERP


56/128

We use the recommended BW interface, the NetWeaver Open Hub interface, to extract mass data fromBW.

9.1.2 Direct Access to SAP ECC Using the Financial Information Management NativeJobs

When SAP NetWeaver BW is not present in the landscape, it is possible for the financial informationmanagement application to access SAP ECC data directly.

Figure 9-2: Direct Access to SAP ECC Using Financial Information Management Native Jobs

This approach also leverages the SAP ECC datasources, or SAP Business Suite content extractors,but is not able to leverage their delta extraction capabilities when they exist.

This scenario implies that you have SAP ECC 5.0 or higher.

9.1.3 Direct Access to SAP ECC Using Financial Information Management CustomJobs

It is also possible to use DataServices direct connectors to SAP ECC.

2012-03-0856



57/128

Figure 9-3: Direct Access to SAP ECC Using Financial Information Management Custom Jobs

Note:For further information regarding this method, see the SAP BusinessObjects Data Services Supplementfor SAP.

9.1.4 Data Services / SAP ECC Integration Basics

The integration process is as follows:

1. At runtime all ABAP programs are generated and saved as files in the generated ABAP directoryon the data services job server.

2. When the data services data flow starts the ABAP, a call is made to theRFC_ABAP_INSTALL_AND_RUN function on the ECC end.

3. The ABAP creates a file containing the results in the working directory on the SAP server.

4. The data services job server does one of the following:

Downloads the file from the working directory either via FTP or custom transport

Tries to access the file via shared directory

The process described above is generally valid only in SAP ECC development environments. Forother environments, the ABAP code executed but not published.

You must use the SAP transport system to move the ABAP code from the development environmentto another environment, which is standard practice in SAP environments.

Data Services / SAP ECC Integration Basics

2012-03-0857



58/128

9.1.5 Transport Methods

The result file is transported back to the data services server in one of the following ways:

FTP

Shared Directory

Direct Download

Custom Program

FTP or Shared Directory are the recommended transport methods

Direct Download is not recommended as performance is not good, however direct download does notrequire any configuration so it can be used as an initial transport method.

The custom program is for very specific cases. Consult the data services documentation for moreinformation.

9.1.5.1 SAP GUI on the Financial Information Management Server

In order to use SAP ECC as a source with direct download, you need to install the SAP GUI for Windows,which is available from the SAP Community Network. http://www.sdn.sap.com/irj/sdn/sap-gui#section6on the financial information management server.

After you have installed the SAP GUI , you must perform the following additional steps:

1. Add the following registry key:

2012-03-0858

http://www.sdn.sap.com/irj/sdn/sap-gui#section6http://www.sdn.sap.com/irj/sdn/sap-gui#section6


59/128

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP\SAPGUI Front\SAP Frontend

Server\Security]

"DefaultAction"=dword:00000000

2. In the "SAP GUI Options" dialog box, underSecurity > Security Settings, change the "DefaultAction" to "Allow".

Figure 9-4: SAP GUI Security Settings

9.1.5.2 Creating an SAP ECC Datastore

You create an ECC datastore in the financial information management application.

1. On the "Home" page, under "List of Datastores", clickNew.

2. Under "Datastore type" select "SAP ECC".

3. ClickNext.

4. In the "Application server" box type the name of the application server to which you want to connect.

5. Enter the following:

User

Password

Client number

System number

6. Select the "data transfer method" as follows:

2012-03-0859



60/128

Enter the following information:If the "data transfer method"is:

the working directory on the SAP server, for example,D:\DataServices

the application path to the shared directory, for example,

\\bsw6529.wdf.sap.corp\DataServices

"Shared directory "


the local directory

FTP path relative to the working folder

FTP host name

FTP login

FTP password

"FTP"


the application path to the shared directory, for example,\\bsw6529.wdf.sap.corp\DataServices

"Direct download"


the local directory

the transfer program to be invoked during job execution

additional arguments used by the transfer program such as

security, compression, or data services system variables. Thearguments are optional.

the username and password

"Custom transfer"

7. If you want to enable drill-to-source, select this option, then enter the drill-to-source root URL, whichconnects to the SAP web GUI.

Note: the drill-to-source root URL must match the following syntax: http://:/sap/bc/gui/sap/its/webgui?

8. ClickTestto test the datastore connection.

9. ClickFinish.

9.1.6 About Drill to Source

2012-03-0860



61/128

When the source of your data is an SAP ECC, you can drill back to the source of data from the targetapplication. From the target application, first you drill to the origin of data, and from there, you view thesource of the data.

9.1.6.1 Configuring Drill to Source

Financial information management drill to source leverages SAP Internet Transaction Server (ITS) toaccess SAP ECC via a web browser.

When drill to source is enabled, the user enters the drill to source root URL, which connects to the SAPWeb GUI.

Example:

http://:/sap/bc/gui/sap/its/webgui?

The following is an example of a financial information job with drill to source enabled.

Figure 9-5: Drill to Source Enabled in a Financial Information Management Job

2012-03-0861



62/128

For detailed information on activating the WebGUI back end refer to the following article on the SAPDeveloper Network http://wiki.sdn.sap.com/wiki/display/EP/12+ITS+WebGUI+-+Activation+(Back+End)

9.1.6.1.1 Example Drill to SourceThe following image shows an example of drill to source:

The drill to source process is as follows:

1. Data is loaded from SAP ECC to SAP BusinessObjects Financial Consolidation

2. From the financial consolidation application the user clicksDrill to originand the origin of data isdisplayed in financial information management.

3. From the financial information management application, the user clicks View Source.

2012-03-0862

http://wiki.sdn.sap.com/wiki/display/EP/12+ITS+WebGUI+-+Activation+(Back+End)http://wiki.sdn.sap.com/wiki/display/EP/12+ITS+WebGUI+-+Activation+(Back+End)


63/128

4. The data is displayed in the original ECC application.

9.2 About SAP ECC Datasources

9.2.1 ECC Datasources Supported by the Financial Information ManagementApplication

You can extract data from SAP ECC using the SAP datasources, that is, the Business Content Extractors.A datasource contains a number of logically-related fields that are arranged in a flat structure.

Before you can use the SAP ECC datasources, they need to be activated on the SAP ECC end usingthe transaction RSA5.

The datasources supported by the financial information management application are as follows:

0FI_GL_10 - Interface to New General Ledger, data from Leading Ledger

0FI_GL_20 - Interface to New General Ledger, data from all ledgers

0FI_AP_4 - Interface to Accounts Payable

0FI_AP_30 - Interface to Accounts Payable

0FI_AR_4 - Interface to Accounts Receivable

0FI_AR_30 - Interface to Accounts Receivable

0EC_PCA_1 - Interface to Profit Center Accounting

0CO_OM_CCA_3 - Interface to Cost Center Accounting



0CO_OM_ABC_2 - Interface to Activity Based Costing

0CO_PA_1 - Interface to Profitability Analysis

Note:The datasource to CO-PA does not appear in the list of available datasources by default. You mustadd this datasource.

Related Topics

Activating a Datasource

Adding an ECC Datasource for the CO-PA Module

2012-03-0863



64/128

9.2.1.1 Activating a Datasource

To activate a datasource proceed as follows:

1. Connect to SAP ECC and run transaction RSA5.

2. Validate any message that appears.

3. Expand NODESNOTCONNECTED and locate your datasource .

4. Place your cursor on the selection and clickSet Selection.

2012-03-0864



65/128

5. With your cursor still on the datasource, clickActivate Data Sources.

6. In the next screen clickLocal Objectthen validate any message that appears.

The datasource is indicated as Aor active.

2012-03-0865



66/128

9.2.1.2 Checking an Activated a Datasource

You can confirm that you have activated a datasource by running transaction RSA2.

In the DataSource Repository screen click the Browseicon.

The next screen displays the active datasources.

9.2.1.3 Testing a Datasource

To test a datasource run transaction RSA3.

1. Select an activated datasource/extractor.

2. In the next screen enter any filters in the "From Value / To Value" columns.

3. ClickExtraction.

4. ClickDisplay Listto view the list of results.

5. Double-click the name of the data package that interests you.

The results are displayed in a table.

9.2.1.4 ECC Datasources in the Financial Information Management Application

When you select SAP ECC as a source of data in the financial information management application,you see the list of activated datastores from which you select one.

2012-03-0866



67/128

Figure 9-6: Activated ECC Datasources in the Financial Information Management Application

Fordetailed information on creating jobs, consult the online help in the financial information managementapplication.

9.2.2 About the 0FI_GL_10 / 0FI_GL_20 Datasources

The 0FI_GL_10 datasource contains data from the Leading Ledger.

The 0FI_GL_20 datasource contains data from all ledgers. It is available only with a minimal version ofECC (ECC 6.0 EhP4)

Generally used fields are as follows:

FISCPER : Fiscal Period

CURTYPE=10 Local Currency

CURTYPE=00 Transaction Currency

RBUKRS: Company Code

RACCT: Account, formatted using 10 digits, including leading zeroes

RASS: Trading Partner

RCNTR: Cost Center PRCTR: Profit Center

Dates are expressed in the format YYYYMMM

The number of fiscal periods per year is configurable

Period 00 is for Carry Forward from prior year

2012-03-0867



68/128

9.2.2.1 Modifying the 0FI_GL_20 Extractor

When using the 0FI_GL_20 datasource you need to modify the extractor as follows:

1. Run transaction RSA6.

2. In the "Datasource Edit" screen uncheck "Hide field" for all field names selected as shown:

2012-03-0868



69/128

9.2.3 About the 0FI_AP_4 / 0FI_AP_30 Datasources

Output line items are from Account Payables (AP) and there is one output line per line item.

Generally-used fields are as follows:

FISCPER: Fiscal Period

BUKRS: Company Code

BELNR: Document number (under SAP ECC)

REBZG: Invoice Reference

SAKN : G/L Account, formatted using 10 digits, including leading zeroes

WAERS: Transaction Currency

LCURR: Local Currency WRSHB: Debit/Credit Amount in Transaction Currency

DMSHB: Debit/Credit Amount in Local Currency

LIFNR: Account Number of Vendor or Creditor

STATUSPS: Status of the item ( Opened or Closed : O/C )

0FI_AP_30 allows you to filter opened/closed items

9.2.4 About the 0FI_AR_4 / 0FI_AR_30 Datasource

Output line items are from Account Receivables (AR) and there is one output line per item.

Generally-used fields are as follows:

FISCPER: Fiscal Period

BUKRS: Company Code

BELN : Document number (under SAP ECC)

REBZG: Invoice Reference

SAKN : G/L Account, formatted using 10 digits including leading zeroes

WAERS: Transaction Currency

LCURR: Local Currency

WRSHB: Debit/Credit Amount in Transaction Currency DMSH : Debit/Credit Amount in Local Currency

KUNNR: Customer

STATUSPS: Status of the item ( Opened or Closed : O/C )

Dates are expressed in the format YYYYMMM

In ERP the number of fiscal periods per year is configurable

2012-03-0869



70/128


71/128

9.2.7 About the 0CO_OM_CCA_4 Datasource

The 0CO_OM_CCA_4 datasource does the following:

Interfaces to the Cost Center Accounting module

Provides information about the quantities posted for each cost center for the statistical key figures

Outputs both actual and planned quantities

VTYPE=10, Actual

VTYPE=20, Plan

The generally used fields are as follows:

FISCPER Fiscal Period

KOKRS Controlling Area

KOSTL Cost Center

STAGR Statistical Key Figure, for example, Employees or Square Meters

LSTAR Activity Type, for example, IT Services, Machine Hours or Quality Control

MEINH Unit of measure, for example, Hour or Square meters

SSME Quantity

Dates are expressed in the format YYYYMMM, with the month in three digits, for example, 2010011

The number of fiscal periods per year is configurable



9.2.8 About the 0CO_OM_CCA_9 Datasource

The 0CO_OM_CCA_9 datasource interfaces to the Cost Center Accounting module. It providesinformation on the actual costs that were posted to cost centers. These costs may have been postedto the cost centers as primary costs or internal allocations.

Amounts expressed by currency use the Currency type column (CURTYP) CURTYP=10 Local Currency, Company Code

CURTYP=00 Transaction Currency

CURTYP=20 Controlling Area Currency

The generally-used fields are as follows:

FISCPER Fiscal Period


2012-03-0871



72/128

KOSTL Cost Center

KSTAR Cost Element

VERSN Version

LSTAR Activity Type

MEINH Unit of Measure

MEINH Unit of Measure

SWG Amount

9.2.9 About the 0CO_OM_ABC_2 Datasource

The 0CO_OM_ABC_2 DataSource provides information on the activity quantities of the business

processes.

The generally used fields are as follows:

FISCPER : Fiscal Period


VKSTA Allocation Cost Element

VERSN Plan Version

LEINH Activity Unit

SLST Activity Quantity

Dates are expressed in the format YYYYMMM.

The number of fiscal period per year is configurable.Period 00 is for Carry Forward from prior year.

9.2.10 Configuration of the New General Ledger

The "New General Ledger" is configurable, therefore, not all extractor columns return values.

Any data that you load into the financial consolidation application requires details on the amount:

Trading Partner either Cost Center or Profit Center

Due to the configuration of the New General Ledger, you need a Leading Ledger to which the followingscenarios have been assigned :

FIN_CONS,,Preparation for Consolidation'' that gives you the Trading Partner information inFAGLFLEXT, therefore in0FI_GL_10

Either

2012-03-0872



73/128

"FIN_CCA ,,Cost Center Update"" for the Cost Center detail, or

FIN_PCA ,,Profit Center Update" for the profit center detail

Additional Notes :

Amounts extracted by the extractor are the following:

BALANCE

DEBIT

CREDIT

TURNOVER

QUANTITY

All amounts are extracted using different currencies such as transaction, and accounting, therefore,in most cases, you need to put a filter on the CURTYPEcolumn of the extractor

Note:CURTYPE=00 means transaction currency.

TheFISCPER column extracts the fiscal period generally under the format YYYYMMM, therefore,if you need data from January 2009, filterFISCPERon 2009001

9.2.10.1 Fields of Origin in the Extraction Structure - General Ledger

The following table describes the business content extractor structure.

2012-03-0873



74/128

Field in Table ofOrigin

Table of OriginFilterableDescription ofField in the Extrac-tion Structure

Field in ExtractionStructure

Same name asthe field in the ex-traction structure.

If you useyour own totals ta-ble, these fieldsare only availableon thedatasourceif your table con-tains them. If yourtable contains

your own fields(Y* or Z*) as well,such fields are al-so available in theDatasource (seethe section "Fea-tures of the Extrac-tor").

FAGLFLEXT (orother GeneralLedger totals ta-ble for leadingledger)

YFiscal yearRYEAR

YGeneral Ledger:Transaction At-tributes

ACTIV

YTransaction typeRMVCT

YCurrency keyRTCUR

YBase unit of mea-surement

RUNIT

NLedgers in Gener-alLedgerAccount-ing

RLDNR

YRecord typeRRCTY

YVersionRVERS

YLogical systemLOGSYS

YAccount numberRACCT

YCompany codeRBUKRS

YCost centerRCNTR

2012-03-0874



75/128




YProfit centerPRCTR

YFunctional areaRFAREA

YBusiness areaRBUSA

YControlling areaKOKRS

YSegment for seg-ment reporting

SEGMENT

YSender cost cen-ter

SCNTR

YPartnerprofit cen-ter

PPRCTR

YPartner functionalarea

SFAREA

YBusiness area ofthebusiness part-ner

SBUSA

YCompany ID oftrading partner

RASSC

YPartner segmentforsegment report-ing

PSEGMENT

RUNITNUnit of measureQUANUNIT

2012-03-0875



76/128




From RRCTY:The characteristicRecord TypeinFI-SL is displayedon the InfoObjectValue Type:

The record types0 and 2 are con-verted to valuetype 10: Recordtype 0 = ActualRecord type 2 =

Actual assess-ment The recordtypes 1 and 3 areconverted to valuetype 20: Recordtype 1 = PlanRecord type 3 =Plan assessment

YReporting valuetype

VALUETYPE

Ledger masterdata

YCurrency typeCURTYPE

RYEAR and RP-

MAXYFiscal year/periodFISCPER

Master data of theledgerand organi-zational unit

NFiscal year variantFISCVAR

NChart of accountsCHARTACCTS

Always empty(SPACE) due toafter image deltaprocess.

NBW delta proce-dure: Updateses-sion

UPMOD

Ledger masterdata

NValuation viewVALUTYP

RTCURor masterdata of the ledgerandorganizationalunit

NCurrency keyCURRUNIT

2012-03-0876



77/128




xSLnn andxSLVTThe field fromwhich the data istaken depends onthe ledger masterdata, the charac-teristics of the In-foObject OCUR-TYPE, and theposting period.Here, x stands forT, H, K or O. The

suffix nn portraysa two-digit offset,which, togetherwith the key fieldRPMAX, de-scribes the post-ing period (gener-ally, the postingperiod = RPMAX+ nn -16). Thefield xSLVT con-tains the balance

carryforward.

NCumulated bal-anceBALANCE

xSLnnNTotal debit post-ings

DEBIT

xSLnnNTotal credit post-ings

CREDIT

xSLnnNSales of the peri-od

TURNOVER

MSLnnNConsumptionquantity

QUANTITY

Caution:Note the following limitation of the extractor: not all the fields of the extractor can be used for filteringpurposes. If you attempt to filter one of those fields, for example CHARTACCTS then your job willextract 0 rows from SAP ECC.

2012-03-0877



78/128

9.2.11 Configuration of Profit Center Accounting

Profit Center Accounting is configurable therefore not all extractor columns return values.

The following types of amounts are extracted by the extractor:

DEBIT

CREDIT

BALANCE

QUANTITY

All amounts are extracted using different currencies for example, transaction currency, companycurrency, and profit Center Local Currency, therefore, in most cases, you need to put a filter on the

CURTYPEcolumn of the extractor (CURTYPE=00 means transaction currency)

TheFISCPERcolumn extracts the fiscal period generally under the format YYYYMMM. For example,

you need data from January 2009 filterFISCPERon 2009001

9.2.11.1 Fields of Origin in the Extraction Structure - Profit Center Accounting

SourceFilterableDescription of Fieldin the ExtractionStructure


GLPCT-KORKSYControlling areaKORKS

GLPCT-RBUKRSYCompany codeRBUKRS

GLPCT-RFAREAYFunctional areaRFAREA

GLPCT-RPRCTRYProfit centerRPRCTR

CLPCT-RHOARTYOrigin object type inProfit Center Account-

ing

RHOART

derived from the controllingarea (GLPCT-KORKS)

NFiscal year variantFISCVAR

derived from the controllingarea (GLPCT-KORKS)

NChart of AccountsCHARTACCTS

2012-03-0878



79/128

SourceFilterableDescription of Fieldin the ExtractionStructure


GLPCT-RACCTYAccount numberRACCT

conversion or record type(GLPCT-RRCTY) Record types 0 and 2 are

converted int value type 10

Record types 1 and 3 areconverted into value type20.

YValue type for reportingVALUETYPE

Customizing settingsNValuation ViewVALUTYP

from customizing settings inProfit Center Accounting andname of the value field used.

YCurrency TypeCURTYPE

with value field TSL, curren-cy type 0 is set

with HSL, currency type 10is set

with KSL, currency type20,30, or 90 is set

YVersionRVERS

GLPCT-VERSNYResults analysis ver-

sionVERSA

GLPCT-VERSAYDepreciation areaRASSC

GLPCT-RASSCYPartner company codeAFABE

GLPCT-SUKRSYPartner functional areaSBUKRS

GLPCT-SFAREAYPartner profit centerSFAREA

GLPCT-SPRCTRYPartner profit center forelimination of internalbusiness volume

SPRCTR

GLPCT-EPRCTRNPartner origin objecttype in Profit CenterAccounting

EPRCTR

GLPCT-SHOARTYPartner origin objecttype in Profit CenterA

fim admin guide

Documents