Vous êtes sur la page 1sur 128

Financial Information Management 10 Administration Guide SAP BusinessObjects Financial Information Management 10

2012-03-08

Copyright

2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 2012-03-08

Contents

Chapter 1

Document History...................................................................................................................7

Chapter 2

Financial Information Management Architecture....................................................................9 Financial Information Management Architecture.......................................................................9 System Landscape with the Planning and Consolidation Application for Microsoft...................9 System Landscape with the Profitability and Cost Management Application...........................10 System Landscape with the Planning and Consolidation Application for NetWeaver..............11 System Landscape with the Strategy Management Application..............................................11 System Landscape with the Financial Consolidation Application ............................................12 Oracle Requirements............................................................................................................15 Oracle Database Requirements..............................................................................................15 Oracle Installation Requirements............................................................................................16 Additional Requirements When Using an Oracle Database.....................................................16 Maximum Connections on an Oracle Server..........................................................................17 User Roles.............................................................................................................................19

2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5


Chapter 3

3.1 3.2 3.2.1 3.3


Chapter 4

Chapter 5

Specific Configuration..........................................................................................................21 Configuring SSL.....................................................................................................................21 Installing SSL on Tomcat........................................................................................................21 Preparing the Certificate Store...............................................................................................22 Configuring Tomcat HTTPS....................................................................................................23 Configuring SSL for the Data Services Application................................................................23 Configuring Reverse Proxy Servers for SAP BusinessObjects Financial Information Management..........................................................................................................................24 SAP BusinessObjects Financial Information Management Logs.............................................24 Configuring Tomcat for Production Environments...................................................................25 Configuring Server Groups....................................................................................................25 Configuring the Active Directory............................................................................................26

5.1 5.1.1 5.1.2 5.1.3 5.1.4 5.2 5.3 5.4 5.5 5.6

2012-03-08

Contents

Chapter 6

Financial Information Management Application Parameters.................................................29 Configuring the Number of Lines in a Flat File Preview ..........................................................29 Configuring Time-out Parameters...........................................................................................29 Increasing the Number of Lines Displayed in Job Run History................................................29 Custom Jobs.........................................................................................................................31 About Data Services Job Customization................................................................................31 Dataflows...............................................................................................................................31 Data Services Objects...........................................................................................................33 Global Variables.....................................................................................................................34 Repository Tables..................................................................................................................35 Customizing a Data Services Job...........................................................................................36 Publishing a Data Services Job to Web Services...................................................................36 Connecting to a Data Services Job........................................................................................37 Modifying the Data Services Job...........................................................................................37 Importing a Custom Job.........................................................................................................38 Importing a Financial Information Management Job................................................................38 Batch Job Publishing..............................................................................................................39 Using the Financial Information Management Application with SAP NetWeaver BW..........41 Using the Financial Information Management Application with SAP NetWeaver Business Warehouse............................................................................................................................41 Moving Data to and from SAP NetWeaver BW .....................................................................41 Overview: Setting Up the Connection Between SAP BW and the Financial Information Mangement Application.............................................................................................................................42 Creating an RFC Connection.................................................................................................43 Creating a New RFC Server Interface....................................................................................44 Testing the RFC Connection..................................................................................................45 Creating the Open Hub Connection ......................................................................................46 Activating the Open Hub Connection.....................................................................................48 Creating the Transformation...................................................................................................48 Creating a Data Transfer Process..........................................................................................48 Creating a Datastore in the Financial Information Management Application............................49 Creating a Process Chain.......................................................................................................50 Creating a Process Variant....................................................................................................50 Creating a Financial Information Management Job.................................................................50 Configuring Masterdata Browsing..........................................................................................52

6.1 6.2 6.3


Chapter 7

7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.2 7.2.1 7.2.2 7.2.3 7.3 7.3.1 7.4
Chapter 8

8.1 8.2 8.3 8.3.1 8.3.2 8.3.3 8.3.4 8.3.5 8.3.6 8.3.7 8.3.8 8.3.9 8.3.10 8.4 8.5

2012-03-08

Contents

Chapter 9

Using the Financial Information Management Application with SAP ERP............................55 Accessing SAP ERP Central Component (ECC Data)............................................................55 Accessing SAP ECC Data Through SAP NetWeaver BW .....................................................55 Direct Access to SAP ECC Using the Financial Information Management Native Jobs..........56 Direct Access to SAP ECC Using Financial Information Management Custom Jobs .............56 Data Services / SAP ECC Integration Basics ........................................................................57 Transport Methods.................................................................................................................58 About Drill to Source.............................................................................................................60 About SAP ECC Datasources................................................................................................63 ECC Datasources Supported by the Financial Information Management Application..............63 About the 0FI_GL_10 / 0FI_GL_20 Datasources...................................................................67 About the 0FI_AP_4 / 0FI_AP_30 Datasources......................................................................69 About the 0FI_AR_4 / 0FI_AR_30 Datasource.......................................................................69 About the 0EC_PCA_1 Datasource.......................................................................................70 About the 0CO_OM_CCA_3 Datasource..............................................................................70 About the 0CO_OM_CCA_4 Datasource..............................................................................71 About the 0CO_OM_CCA_9 Datasource..............................................................................71 About the 0CO_OM_ABC_2 Datasource...............................................................................72 Configuration of the New General Ledger..............................................................................72 Configuration of Profit Center Accounting..............................................................................78 Configuration of Accounts Payable and Accounts Receivable................................................81 Configuration of Cost Center Accounting ..............................................................................92 Configuration of Activity Based Costing ..............................................................................105 Enriching the ECC Datasource List......................................................................................107 Enriching the ECC Datasource List......................................................................................107 Configuring Drill-to-Source...................................................................................................111 Configuring Drill-to-Source for an ECC Datasource..............................................................111 Configuring Drill-to-Source for the 0CO_OM_CCA_3 Datasource, Part 1............................117 Configuring Drill-to-Source for the 0CO_OM_CCA_4 Datasource.......................................119 Troubleshooting..................................................................................................................123 Errors Returned with SAP NetWeaver BW in Target............................................................123 Could Not Send Message ...................................................................................................123 More Information.................................................................................................................125 127

9.1 9.1.1 9.1.2 9.1.3 9.1.4 9.1.5 9.1.6 9.2 9.2.1 9.2.2 9.2.3 9.2.4 9.2.5 9.2.6 9.2.7 9.2.8 9.2.9 9.2.10 9.2.11 9.2.12 9.2.13 9.2.14 9.3 9.3.1 9.4 9.4.1 9.4.2 9.4.3
Chapter 10

10.1 10.2
Appendix A Index

2012-03-08

Contents

2012-03-08

Document History

Document History

The following table provides an overview of the most important changes to this document. Version 1.0 1.1 1.2 Date October 2010 June 2011 August 2011 Description Initial version Added information on configuring the Active Directory Added information on enriching the ECC datasource list Added architecture diagrams 1.3 February 2012 Fixed bug to add proceduro on importing a financial information management job.

2012-03-08

Document History

2012-03-08

Financial Information Management Architecture

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 the planning and consolidation application for Microsoft:

2012-03-08

Financial Information Management Architecture

2.1.2 System Landscape with the Profitability and Cost Management Application
This schematic shows a detailed view of the financial information management architecture for the profitability and cost management solution:

10

2012-03-08

Financial Information Management Architecture

2.1.3 System Landscape with the Planning and Consolidation Application for NetWeaver
This schematic shows a detailed view of the financial information management architecture for the planning 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 the strategy management application:

11

2012-03-08

Financial Information Management Architecture

2.1.5 System Landscape with the Financial Consolidation Application


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

12

2012-03-08

Financial Information Management Architecture

13

2012-03-08

Financial Information Management Architecture

14

2012-03-08

Oracle Requirements

Oracle Requirements

This section describes the requirements when using Oracle databases with SAP BusinessObjects Financial 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 Financial Information Management does not support the shared server mode, formerly known as the multi-threaded server mode. The character set recommended for an SAP BusinessObjects Financial Information Management database is AL32UTF8. The national character set recommended is UTF8. When the database is configured inthe archive log mode, sufficient disk space is must be available for the archived redo logs. The system must be sized appropriately to support the system overhead associated 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 Management Installation Guide for information on configuring the Oracle elient. Identical settings can also be applied 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 its database objects and to manage all its connections to the Oracle server. Multiple simultaneous connections to the server are established with this single user account at any given time. Different schemas 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 can grant privileges as follows: CREATE CREATE CREATE CREATE CREATE TABLE SEQUENCE CLUSTER TYPE

15

2012-03-08

Oracle Requirements

For customization projects, the following additional privileges may be required: CREATE PROCEDURE CREATE TRIGGER CREATE VIEW

Tip: SAP Technical Support can provide an Oracle Database Configuration Assistant template or a sample database creation script and initialization parameter file customized for SAP BusinessObjects Financial Information Management, which can be edited to suit the requirements of your site. Caution: You must not assign the SELECT ANY TABLE privilege 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 your client 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 application server. Note: For more information on the operating systems supported, recommended patches, and installation procedures, 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 to the location where the tnsnames.ora file 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_ad min=C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN

16

2012-03-08

Oracle Requirements

3.3 Maximum Connections on an Oracle Server


When using an Oracle server, you need to set the maximum number of connections in the Oracle Console under "Session": alter system set sessions =NbSession scope=spfile; where NbSession must be equal to 8 x Number of jobs x maximum number of mapping tables in a in job.

17

2012-03-08

Oracle Requirements

18

2012-03-08

User Roles

User Roles

The user roles in the financial information management solution are the following: Administrator, who creates and maintains database and application datastores. Administrators have access to all jobs defined in the platform. The administrator may be, but is not required to be, the person who installs and manages the financial information management system. Business user Auditor Executor

The principal user roles are summarized as follows: Administrator Executor X X X X X X X X X X X X X X X Business User X X X X X (when owner of job) X X X X X X Auditor X X

Action

View list of jobs View job definition Create jobs Export jobs Delete jobs View mapping tables Modify mapping tables Import jobs Execute jobs Schedule jobs

19

2012-03-08

User Roles

Action

Administrator Executor X X

Business User X (who executed the job) X (who executed the job)

Auditor X

View job results and audit trail View extended data services logs Drill-to-origin Create datastores to EPM applications Delete datastores View deleted jobs

X X

X X

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

20

2012-03-08

Specific Configuration

Specific Configuration

5.1 Configuring SSL


You use the Secure Sockets Layer (SSL) protocol for all network communication between clients and servers 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 information management 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 intercompany server. 5. Configure the financial consolidation application web service HTTPS. If you are using SAP BusinessObjects 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 Enterprise in the SAP BusinessObjects Administrator's Guide SAP BusinessObjects Financial Consolidation Installation Guide SAP BusinessObjects Intercompany Installation Guide

5.1.1 Installing SSL on Tomcat


SSL on SAP BusinessObjects Financial Information Management 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.

21

2012-03-08

Specific Configuration

2. Locate the following certificates and keys and paste them in the %MYCERTFOLDER% folder. The certificates 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. Select Java > 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%\.keystore 7. 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

22

2012-03-08

Specific Configuration

5.1.3 Configuring Tomcat HTTPS


To configure Tomcat proceed as follows: 1. Locate and open the server.xml file in the Tomcat installation folder, %TOMCATDIR%\conf 2. Add the following: <Connector port="%MYSSLPORT%" protocol="HTTP/1.1" SSLEn abled="true" maxThreads="150" scheme="https" secure="true" keyAlias="tom cat" clientAuth="false" sslProtocol="TLS" keystoreFile="%MYCERTFOLDER%\.key store" keypass="%MYKEYPASS" % pares MYKEYPASS=% /> 3. Open the Tomcat configuration tool. 4. Click Java> Java Options 5. Under Java Options add the following: -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: %DataServicesIn stallDir%\ext\webservice-c\. You configure the file as follows: 1. Un-comment the https transport receiver and https transport sender section in the axis2/c file as shown in the following example:
<!-- ================================================= --> <!-- Transport Ins --> <!-- ================================================= --> <transportReceiver name="https" class="axis2_http_receiver"> <parameter name="port" locked="false">6060</parameter> <parameter name="exposeHeaders" locked="true">false</parameter> </transportReceiver> <!-- ================================================= --> <!-- Transport Outs --> <!-- ================================================= --> <!-- Uncomment the following with appropriate parameters to enable the SSL transport sender. Also make sure that the appropriate transport receiver is enabled above.--> <transportSender name="https" class="axis2_http_sender"> <parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter> <parameter name="xml-declaration" insert="false"/> </transportSender>

2. Type the SERVER_CERT path as shown in the following example: <parameter name="SERV ER_CERT">/path/to/ca/SAPNETCA.der</parameter>

23

2012-03-08

Specific Configuration

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 applications without having to re-enter credentials. For example, a user enters credentials to connect to SAP BusinessObjects Financial Consolidation and receives an SAP BusinessObjects Enterprise XI session cookie. From SAP BusinessObjects Financial Consolidation, he goes to the SAP BusinessObjects Financial Information Management application with the same browser session, and does not need to re-enter credentials, because he is logged on automatically. The SAP BusinessObjects Enterprise XI session cookie is reused automatically. A reverse proxy server is mandatory if you want to use single sign-on (SSO) unless all server components are 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 the following 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 same reverse proxy server.

5.3 SAP BusinessObjects Financial Information Management Logs


The financial information management application provides the trace.ini file 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 with TraceLog The trace.ini file is located in the WEB-INF folder in the financial information management application. 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:"

24

2012-03-08

Specific Configuration

The Tomcat logs are located in the Logs subdirectory of theTomcat server on the financial information management server with the file name stdout.log Consulting 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. Select Start > All programs > Tomcat configuration and click the Java tab. The following dialog box opens.

2. In the Initial memory pool field, enter a number that is at least 64 MB and up to 100 MB. 3. In the Maximum memory pool field, enter a number that represents up to 80% of your computer's RAM. For example, if you have 512 MB of RAM, set the maximum memory to 400 MB. 4. Click Apply and OK.

5.5 Configuring Server Groups

25

2012-03-08

Specific Configuration

You can distribute the execution of a job or of part of a job across multiple job servers within a server group, which allows you to better balance resource-intensive job servers to the job server with the lightest load at runtime. When using a group of servers, you need to install a complete version of the data services application on the financial information management server. You then configure the server group In the administration console under Data Services information as follows: ServerGroupName;inet:ServerDataServices Name:3500;inet:%SERVER2%:%PORT2%;... Data services setup allows you to install client, server, and web tier components. In this diagram, no data services job server is running on the financial information management server. The financial information management server uses al_engine.exe to import the ATL job definition to the data services repository. It uses al_RWJobLauncher.exe to 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 new parameter passed to al_RWJobLauncher.exe by financial information management. For more detailed information on server groups, refer to the SAP BusinessObjects Data Services Management Console: Administrator Guide from the SAP Help Portal at https://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 to C:\Windows on the financial information management server: bscLogin.conf Example:
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 to maintain consistent case sensitivity for the domain name throughout your setup. We recommend you use CAPS implementation. Example:
\[libdefaults\] default_realm = PNR2K8TEST01.COM dns_lookup_kdc = true dns_lookup_realm = true forwardable = true \[realms\] PNR2K8TEST01.COM = { default_domain = PNR2K8TEST01.COM kdc = VANPGC8B2.PNR2K8TEST01.COM forwardable = true }

26

2012-03-08

Specific Configuration

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

27

2012-03-08

Specific Configuration

28

2012-03-08

Financial Information Management Application Parameters

Financial Information Management Application Parameters

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 the default value of the maximum rows displayed: 1. Open the server.xml file located in C:\Program Files\Business Objects\Tomcat6\webapps\fim\WEB-INF. 2. In the <bean id="fileManager" class="com.sap.fpm.fim.server.webservice.im pl.FileManagerImpl"> section, locate the following line: <property name="maxPreviewRowNumber" value="100"/> 3. Increase the value of the maxPreviewRowNumber parameter (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 as follows: in server.xml

connectionTimeout: Timeout in milliseconds to connect to Data Services execution Web Service. (Default 120 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

29

2012-03-08

Financial Information Management Application Parameters

You can increase the number of lines displayed in the job run history by modifying the maxRetrieve parameter on the jobExecution bean in the server.xml file as shown here: <bean id="jobExecution" class="com.sap.fpm.fim.server.webservice.impl.JobEx ecutionImpl" init-method="init"> <property name="maxRetrieve" value="200"/> </bean > For example, if you want to increase the number of lines displayed to 400, set the maxRetrieve value as follows: <property name="maxRetrieve" value="400"/> </bean > The maxRetrieve value is valid for three tables on the Job Run History page. Each table returns the same maximum number of lines: Unmapped Lines Rejected Lines Imported Lines

Figure 6-1: Rows Limited to 200 Lines

30

2012-03-08

Custom Jobs

Custom Jobs

7.1 About Data Services Job Customization


The financial information management solution is a business user interface on top of the data services application. The financial information management solution loads data into the EPM (Enterprise Performance 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 offered by the data 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 Variables Repository 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 financial information management job, and applying the runtime filters A transform dataflow, responsible for applying the mapping rules, and identifying the mapping errors A load dataflow, responsible for loading the data to the target application of the financial information management job, and identifying the rejected rows by the target application. On the left of the SAP BusinessObjects Data Services Designer window the following components of a data services project are displayed: Under "Project Area" the data services project generated by the financial information management application, with the three dataflows

31

2012-03-08

Custom Jobs

Note: The job that was created has the same name as the job name assigned in the financial information management 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 source table 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 information application. The validation controls shown in the diagram make sure that every line in the table was translated using at least one mapping rule. If this is not the case, the line has a null value and the data services application pushes 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 transaction table contains the data with its definition before and after mappings.

32

2012-03-08

Custom Jobs

7.1.1.3 The Load Dataflow


The load dataflow is dedicated to loading data into the target system. It take data from the transaction table and prepares the data for the web services call. It then gathers the output from the web services call and ascertains if there is a problem. Rejected rows are stored in tables in the financial information management 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 are generated in the data services repository. In this table you need to replace jobName by the name of the financial information management job that you created. The job name in financial information management is limited to 8 characters.
Description Data Services Object Name

DS Project Name DS Job Name Export DS DataFlow Transform DS Data Flow Load DS DataFlow Financial information management repository DB DS DataStore Name File Export DS DataStore Name

PROJECT_%jobName% %jobName% DF_EXPORT_%jobName% DF_TRANSFORM_%jobName% DF_LOAD_%jobName% %jobName%_DS %jobName%_FILE_EXPORT_DS

33

2012-03-08

Custom Jobs

Description

Data Services Object Name

Table Export DS DataStore Name FC Load Web Service DS DataStore Name PCM Load Web Service DS DataStore Name PCM Repository DS DataStore Name

%jobName%_TABLE_EXPORT_DS %jobName%_FC_LOAD_DS %jobName%_PCM_LOAD_WS_DS %jobName%_FC_LOAD_TABLE_DS

7.1.3 Global Variables


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

Table 7-2: Global Variables


Description DS Global Variable Name

Financial Information Management Job Run ID BOE SSO logon token BOE user name BOE user password Filters on Source Dimensions Target Application Options

$JOB_RUN_ID $SerializedSession $User $Password $Filter_%SourceDimensionName% $aggregateAmounts, etc .

The following image shows the variables as they appear in the data services application interface. When you 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 information management application. The JOB_RUN_ID is an autogenerated number assigned to an instance of a job when it is run. Each time a job is run, a new ID is assigned to the instance.

34

2012-03-08

Custom Jobs

7.1.4 Repository Tables


When you create a job using the financial information management interface, data services jobs are generated in the data services repository. In this table you need to replace jobName by the name of the financial information management job that you created. The job name in financial information management is limited to 8 characters.
Description Financial Information Management Repository Table Name

Source Table Name Transaction Table Name Source Column in Transaction Table Mapping Tables Mapping Errors Table

SOURCE_%jobName% TRANSACTION_%jobName% SC_%DimName% FIM_%jobName%_%MappingTableName% MAPPING_ERRORS_%jobName%

35

2012-03-08

Custom Jobs

The source table is created in the financial information management repository to store the extracted rows from the source. This table is not mandatory. The generated data services job can be customized to eliminate this staging area. The transaction table is created in the financial information management repository to store the output of every successfully-applied mapping. The transaction table contains mappings from every source set of data to every target set of data. The transaction table is queried when you use the drill-to-origin feature from the target application to display the origin of data. Note: The data services job is responsible for populating transaction tables. The financial information management application never writes to these tables directly. Generated data services jobs use the following other financial information management repository tables:
Description Financial Information Management Repository Table Name

Rejected Rows Table Name Job Run Status

FIM_REJECTED_ROW FIM_JOB_RUN_PACKAGE_STATUS

7.2 Customizing a Data Services Job


To customize a data services job, you must perform the following steps, which are explained in greater detail: 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 web services. 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

36

2012-03-08

Custom Jobs

1. From the Start menu clickSAP BusinessObjects XI 4.0 > BusinessObjects Data Services > Data Services 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, select Add Batch Job..., then click Apply. 6. In the next page, select the job, then click Add. Below the "Web Services Configuration" tab, a message appears indicating that the web service provider 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 management application that this is an external job. The application does not modify or erase the customized version. 1. In the financial information management application, under "List of Jobs" select and open the job that 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 published to web services. By default, the names of the transaction table and the validation error table appear in the appropriate boxes. 4. Click Save. Note: Do not click Execute until after you have modified the job in the data services application.

7.2.3 Modifying the Data Services Job


After you have connected to the data services job from the financial information management 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 to send an email when a job has been completed. 3. Save your modified job.

37

2012-03-08

Custom Jobs

Note: Once you have modified and saved the job, you must return to the financial information management application 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 custom data 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 used the first time the job is moved from the source data services repository to the target data services repository Exporting to file generates an ATL file. 3. Through "DataServices Designer "log in to the target data services repository and import the ATL file. Note: If this is the first time the custom job is moved to the target environment, you need to modify the datastore properties to point to the correct environment. This is particularly true for the datastore pointing 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 Importing a Financial Information Management 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 as a source of data, you must copy the flat file located in the upload file folder of the server from which you are exporting the job to the upload file folder of the server to which you are importing the job. The upload file folder is defined in the administration console. To import a job: 1. On the Home page under "List of Jobs" select the job you want to import, then click Import. 2. In the "Import Objects" screen click Browse to locate the xml source file of the import. 3. Click Next. The Select Objects screen lists the objects that you can import. If the object already exists, this information is displayed in the "Already exist" column. If the object already exists in the financial information management environment and you select "Import", the existing object is overwritten by the import.

38

2012-03-08

Custom Jobs

4. Click Next. The financial information management job or jobs are imported and the underlying data services jobs 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 definitions from one environment to another, you use the same datastore name and that the connection names be written in the same case. When working with Oracle databases, datastore names must be written in 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 Management Console as shown here:

Figure 7-1: Batch Job Publishing

39

2012-03-08

Custom Jobs

Note: Selecting the Add Batch Job... option is necessary only for external jobs. If you are planning to execute 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 data services documentation available from the SAP BusinessObjects Solution Portfolio Knowledge Center at http://help.sap.comSAP BusinessObjects > All Products

40

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

Using the Financial Information Management Application with SAP NetWeaver BW

8.1 Using the Financial Information Management Application with SAP NetWeaver Business Warehouse.
The financial information management application is the tool used to move data either from SAP NetWeaver Business Warehouse to an SAP EPM application, or from a SAP EPM application to SAP Netweaver Business Warehouse. The business user selects SAP NetWeaver BW as either the source or target application in the financial information management application. Before the user can select the source and target applications, however, certain preliminary steps must be performed by the administrator in the NetWeaver BW application as well as in the data services application. 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 BusinessObjects EPM application and import it into SAP Netweaver Business Warehouse specifically into the Persistent Storage Area. Data can also be extracted from SAP Netweaver BW and imported into one of the SAP EPM 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:

41

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

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. The open 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.0 provides the functionnality to trigger an Open Hub extraction that 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 SAP BW 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 at https://service.sap.com/sap/support/notes/1343606

8.3 Overview: Setting Up the Connection Between SAP BW and the Financial Information 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 creating an 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.

42

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

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, select TCPIP Connection.

3. Under the "Technical Settings" tab, enter a program ID. The Program ID must match the one defined for the RFC server interface of DataServices. 4. Click the Save icon.

43

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

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. Click Add. 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 Gateway Services name as default.

44

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

4. Click Apply. 5. Under the RFC Server Interface Status tab, select the server name, then click Start. 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 the connections validates your configuration. The name of the connection and the type appear on the page along with the actions and results of the test.

45

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

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

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.

46

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

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. Click Save.

47

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

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 turns green. 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

48

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

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 extraction modes: 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 management application.

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 the CMC to create a datastore. To create a datastore proceed as follows: 1. On the "Home" page, under "List of Datastores", click New. 2. Under "Datastore type" select "SAP NetWeaver BW". 3. Click Next. 4. In the "Application server" box, select the application server to which you want to connect. The list of available application servers corresponds to the RFC connections that were created in the data services 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/port if 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.

49

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

8. Click Finish.

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 create a 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, click Create. 3. In the New Process Chain screen enter a name and a description: 4. Click the check mark to validate. 5. In the Insert Start Process screen, click Create then validate. 6. In the "Maintain Start Process" screen, set the "Scheduling Option" to "Start Using Meta Chain or API" This is not the default value. 7. Click the Save icon. 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", click Create. 2. Under "Start Process", enter a name and a long description for the process variant, then click the check mark. 3. Under "Maintain Start Process" set the scheduling option to "Start Using Meta Chain or API", which is 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

50

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

1. Under List of Jobs, select New. 2. Enter a name for the job and a description. 3. From the list of available users, select the users then click Next. 4. Select the following to the source data: Datastore Open Hub Destination Process Chain Then click Next.

5. Select the target datastore. 6.

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

51

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

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 information on populating the mapping table.

8.5 Configuring Masterdata Browsing


To permit masterdata browsing in SAP BusinessObjects Financial Information Management you need to meet the following criteria: the Open Hub destination structure references InfoObject templates. The application then browses the characteristics declared as InfoObject templates.

Figure 8-2: The Open Hub Desination Display

The Characteristic is declared as InfoProvider

52

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

Figure 8-3: Characteristic Declared as InfoProvider

53

2012-03-08

Using the Financial Information Management Application with SAP NetWeaver BW

54

2012-03-08

Using the Financial Information Management Application with SAP ERP

Using the Financial Information Management Application with SAP ERP

9.1 Accessing SAP ERP Central Component (ECC Data)


There are several methods of accessing SAP ECC data using SAP BusinessObjects 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. This scenario 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 BW integration. This integration leverages the SAP ECC datasources, or Business Suite content extractors, and their delta extraction capabilities when they exist.

55

2012-03-08

Using the Financial Information Management Application with SAP ERP

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

9.1.2 Direct Access to SAP ECC Using the Financial Information Management Native Jobs
When SAP NetWeaver BW is not present in the landscape, it is possible for the financial information management 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 Custom Jobs
It is also possible to use DataServices direct connectors to SAP ECC.

56

2012-03-08

Using the Financial Information Management Application with SAP ERP

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 Supplement for 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 directory on the data services job server. 2. When the data services data flow starts the ABAP, a call is made to the RFC_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. For other environments, the ABAP code executed but not published. You must use the SAP transport system to move the ABAP code from the development environment to another environment, which is standard practice in SAP environments. Data Services / SAP ECC Integration Basics

57

2012-03-08

Using the Financial Information Management Application with SAP ERP

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 not require 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 more information.

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#section6 on 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:

58

2012-03-08

Using the Financial Information Management Application with SAP ERP

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP\SAPGUI Front\SAP Frontend Server\Security] "DefaultAction"=dword:00000000 2. In the "SAP GUI Options" dialog box, under Security > Security Settings, change the "Default Action" 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", click New. 2. Under "Datastore type" select "SAP ECC". 3. Click Next. 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:

59

2012-03-08

Using the Financial Information Management Application with SAP ERP

If the "data transfer method" is: Enter the following information: "Shared directory " 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 the working directory on the SAP server, for example, D:\DataServices the local directory FTP path relative to the working folder FTP host name FTP login FTP password 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 the working directory on the SAP server, for example, D:\DataServices 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. The arguments are optional. the username and password

"FTP"

"Direct download"

"Custom transfer"

7. If you want to enable drill-to-source, select this option, then enter the drill-to-source root URL, which connects to the SAP web GUI. Note: the drill-to-source root URL must match the following syntax: http://<servername>:<port number>/sap/bc/gui/sap/its/webgui? 8. Click Test to test the datastore connection. 9. Click Finish.

9.1.6 About Drill to Source

60

2012-03-08

Using the Financial Information Management Application with SAP ERP

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

9.1.6.1 Configuring Drill to Source


Financial information management drill to source leverages SAP Internet Transaction Server (ITS) to access 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 SAP Web GUI. Example: http://<servername>:<portnumber>/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

61

2012-03-08

Using the Financial Information Management Application with SAP ERP

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

9.1.6.1.1 Example Drill to Source


The 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 clicks Drill to origin and the origin of data is displayed in financial information management. 3. From the financial information management application, the user clicks View Source.

62

2012-03-08

Using the Financial Information Management Application with SAP ERP

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 Management Application


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 using the 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_CCA_4 - Interface to Cost Center Accounting 0CO_OM_CCA_9 - 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 must add this datasource. Related Topics Activating a Datasource Adding an ECC Datasource for the CO-PA Module

63

2012-03-08

Using the Financial Information Management Application with SAP ERP

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 click Set Selection.

64

2012-03-08

Using the Financial Information Management Application with SAP ERP

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

6. In the next screen click Local Object then validate any message that appears.

The datasource is indicated as A or active.

65

2012-03-08

Using the Financial Information Management Application with SAP ERP

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 Browse icon. 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. Click Extraction. 4. Click Display List to 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.

66

2012-03-08

Using the Financial Information Management Application with SAP ERP

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

For detailed information on creating jobs, consult the online help in the financial information management application.

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 of ECC (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

67

2012-03-08

Using the Financial Information Management Application with SAP ERP

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:

68

2012-03-08

Using the Financial Information Management Application with SAP ERP

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

69

2012-03-08

Using the Financial Information Management Application with SAP ERP

Period 00 is for Carry Forward from prior year

9.2.5 About the 0EC_PCA_1 Datasource


The output is from Profit Center Accounting (PCA) Amounts expressed by currency using Currency type column (CURTYPE) CURTYPE=10 Local Currency CURTYPE=00 Transaction Currency Dates are expressed in the format YYYYMMM In ERP the number of fiscal periods per year is configurable Period 00 is for Carry Forward from prior year

9.2.6 About the 0CO_OM_CCA_3 Datasource


The 0CO_OM_CCA_3 datasource does the following: Interfaces to the Cost Center Accounting module Provides information on the activity quantities of cost centers and activity types 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 VKSTA Allocation Cost Element VERSN Plan Version LSTAR Activity Type (ex:IT Services, Machine Hours, Quality Control, etc..) LEINH Activity Unit ( Hour, etc ) SLST Activity 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 Period 00 is for Carry Forward from prior year

70

2012-03-08

Using the Financial Information Management Application with SAP ERP

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 Period 00 is for Carry Forward from prior year Period 00 is for Carry Forward from prior year

9.2.8 About the 0CO_OM_CCA_9 Datasource


The 0CO_OM_CCA_9 datasource interfaces to the Cost Center Accounting module. It provides information on the actual costs that were posted to cost centers. These costs may have been posted to 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 KOKRS Controlling Area

71

2012-03-08

Using the Financial Information Management Application with SAP ERP

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 KOKRS Controlling Area 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 following scenarios have been assigned : FIN_CONS,,Preparation for Consolidation'' that gives you the Trading Partner information in FAGLFLEXT, therefore in 0FI_GL_10 Either

72

2012-03-08

Using the Financial Information Management Application with SAP ERP

"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 CURTYPE column of the extractor Note: CURTYPE=00 means transaction currency. The FISCPER column extracts the fiscal period generally under the format YYYYMMM, therefore, if you need data from January 2009, filter FISCPER on 2009001

9.2.10.1 Fields of Origin in the Extraction Structure - General Ledger


The following table describes the business content extractor structure.

73

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extraction Structure

Description of Field in the Extraction Structure

Filterable

Table of Origin

Field in Table of Origin

Same name as the field in the extraction structure. If you use your own totals table, these fields are only available on the datasource if your table contains them. If your table contains your own fields (Y* or Z*) as well, such fields are also available in the Datasource (see the section "Features of the Extractor").

RYEAR

Fiscal year

FAGLFLEXT (or other General Ledger totals table for leading ledger)

ACTIV RMVCT RTCUR RUNIT

General Ledger: Transaction Attributes Transaction type Currency key Base unit of measurement Ledgers in General Ledger Accounting Record type Version Logical system Account number Company code Cost center

Y Y Y Y

RLDNR RRCTY RVERS LOGSYS RACCT RBUKRS RCNTR

N Y Y Y Y Y Y

74

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extraction Structure

Description of Field in the Extraction Structure

Filterable

Table of Origin

Field in Table of Origin

PRCTR RFAREA RBUSA KOKRS SEGMENT SCNTR PPRCTR SFAREA

Profit center Functional area Business area Controlling area Segment for segment reporting Sender cost center Partner profit center Partner functional area Business area of the business partner Company ID of trading partner Partner segment for segment reporting Unit of measure

Y Y Y Y Y Y Y Y

SBUSA

RASSC

PSEGMENT QUANUNIT

Y N RUNIT

75

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extraction Structure

Description of Field in the Extraction Structure

Filterable

Table of Origin

Field in Table of Origin

VALUETYPE

Reporting value type

From RRCTY: The characteristic Record Type in FI-SL is displayed on the InfoObject Value Type : The record types 0 and 2 are converted to value type 10: Record type 0 = Actual Record type 2 = Actual assessment The record types 1 and 3 are converted to value type 20: Record type 1 = Plan Record type 3 = Plan assessment Ledger master data RYEAR and RPMAX Master data of the ledger and organizational unit

CURTYPE FISCPER

Currency type Fiscal year/period

Y Y

FISCVAR CHARTACCTS

Fiscal year variant Chart of accounts BW delta procedure: Update session Valuation view

N N

UPMOD

Always empty (SPACE) due to after image delta process. Ledger master data RTCUR or master data of the ledger and organizational unit

VALUTYP

CURRUNIT

Currency key

76

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extraction Structure

Description of Field in the Extraction Structure

Filterable

Table of Origin

Field in Table of Origin

BALANCE

Cumulated balance

xSLnn and xSLVT The field from which the data is taken depends on the ledger master data, the characteristics of the InfoObject OCURTYPE, and the posting period. Here, x stands for T, H, K or O. The suffix nn portrays a two-digit offset, which, together with the key field RPMAX, describes the posting period (generally, the posting period = RPMAX + nn -16). The field xSLVT contains the balance carryforward. xSLnn xSLnn xSLnn MSLnn

DEBIT CREDIT TURNOVER QUANTITY

Total debit postings Total credit postings Sales of the period Consumption quantity

N N N N

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

77

2012-03-08

Using the Financial Information Management Application with SAP ERP

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, company currency, and profit Center Local Currency, therefore, in most cases, you need to put a filter on the CURTYPE column of the extractor (CURTYPE=00 means transaction currency) The FISCPER column extracts the fiscal period generally under the format YYYYMMM. For example, you need data from January 2009 filter FISCPER on 2009001

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

Field in Extraction Structure KORKS RBUKRS RFAREA RPRCTR RHOART

Description of Field in the Extraction Structure Controlling area Company code Functional area Profit center Origin object type in Profit Center Accounting Fiscal year variant Chart of Accounts

Filterable

Source

Y Y Y Y Y

GLPCT-KORKS GLPCT-RBUKRS GLPCT-RFAREA GLPCT-RPRCTR CLPCT-RHOART derived from the controlling area (GLPCT-KORKS) derived from the controlling area (GLPCT-KORKS)

FISCVAR CHARTACCTS

N N

78

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extraction Structure RACCT

Description of Field in the Extraction Structure Account number

Filterable

Source

GLPCT-RACCT conversion or record type (GLPCT-RRCTY) Record types 0 and 2 are converted int value type 10 Record types 1 and 3 are converted into value type 20. Customizing settings from customizing settings in Profit Center Accounting and name of the value field used. with value field TSL, currency type 0 is set with HSL, currency type 10 is set with KSL, currency type 20,30, or 90 is set

VALUETYPE

Value type for reporting

VALUTYP CURTYPE

Valuation View Currency Type

N Y

RVERS

Version

VERSA RASSC AFABE SBUKRS SFAREA SPRCTR

Results analysis version Depreciation area Partner company code Partner functional area Partner profit center Partner profit center for elimination of internal business volume Partner origin object type in Profit Center Accounting Partner origin object type in Profit Center Accounting

Y Y Y Y Y Y

GLPCT-VERSN GLPCT-VERSA GLPCT-RASSC GLPCT-SUKRS GLPCT-SFAREA GLPCT-SPRCTR

EPRCTR

GLPCT-EPRCTR

SHOART

GLPCT-SHOART

79

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extraction Structure WERK REP_MATNR RSCOPE FISCPER

Description of Field in the Extraction Structure Plant Representative material Object class Fiscal year/period

Filterable

Source

Y Y Y Y

GLPCT--WERK GLPCT-REP_MATNR GLPCT-RSCOPE from fiscal year (GLPCTRYEAR) and name of the value field used dependent on the currency type from the currency key (GLPCTRTCUR) for transaction currency or customizing settings GLPCT-RUNIT from value fields (GLPCTTSLxx,GLPCT-HSLxx, GLPCTKSPxx) and debit/credit indicator (GLPCT-DRCRK) dependent on period and currency type. from value fields (GLPCTTSLxx,GLPCT-HSLxx, GLPCTKSPxx) and debit/credit indicator (GLPCT-DRCRK) dependent on period and currency type. from value fields (GLPCTTSLxx,GLPCT-HSLxx, GLPCTKSPxx) and debit/credit indicator (GLPCT-DRCRK) dependent on period and currency type. from value fields (GLPCTMALLxx, dependent on the period.

CURRUNIT

Currency Key

QUANUNIT

Unit of measure

DEBIT

Total debit postings

CREDIT

Total credit postings

BALANCE

Accumulated balance

QUANTITY

Quantity

80

2012-03-08

Using the Financial Information Management Application with SAP ERP

Caution: Note the following limitation of the extractor: Not all the fields of the extractor can be used for filtering purposes. If you attempt to filter one of those fields, for example, CHARTACCTS, your job will extract 0 rows from SAP ECC

9.2.12 Configuration of Accounts Payable and Accounts Receivable


This datasource extracts Accounts Payable Accounting line items from tables BSIK (open items) and BSAK (cleared items) in the R/3 source system. This datasource replaces the 0FI_AP_3, Accounts Payable: Line Items, datasource and uses the same extraction structure. Generally-used fields are as follows: BUKRS : Company Code BELNR : Document number (under SAP ECC) REBZG : Invoice Reference SAKNR : 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 The FISCPER column extracts the fiscal period generally under the format YYYYMMM, therefore, if you need data from January 2009, filter FISCPER on 2009001

9.2.12.1 Fields of Origin in the Extraction Structure - Accounts Payable: Line Items
In the following table only the fields BIUKRS and FISCPER are filterable: Field in Extract Structure BUKRS Description of Field in Extract Structure Company code Field in Table of Origin BSIK-BUKRS

Table of Origin

BSIK, BSAK

81

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in Extract Structure

Table of Origin

Field in Table of Origin BSIK-GJAHR

FISCPER

Fiscal year/period

BSIK, BSAK BSIK-MONAT

BELNR

Accounting document number Account document posting line Subitem number

BSIK, BSAK

BSIK-BELNR

BUZEI

BSIK, BSAK

BSIK-BUZEI

UPOSZ

= 0001 BSIK-BSTAT, BSIK, BSAK BSIK-AUGDT

STATUSPS

Status of the FI item (O = open, C = cleared)

LIFNR

Account number of the vendor or creditor

BSIK, BSAK

BSIK-LIFNR

KKBER

Credit control area

BSIK, BSAK, T001

BSIK-KKBER or T001KKBER BSIK-MABER =K

MABER KOART UMSKZ BLART BSCHL FISCVAR

Dunning area Account type Special G/L indicator Document type Posting key Fiscal year variant Document date in document

BSIK, BSAK

BSIK, BSAK BSIK, BSAK BSIK, BSAK T001

BSIK-UMSKZ BSIK-BLART BSIK-BSCHL T001-PERIV

BLDAT

BSIK, BSAK

BSIK-BLDAT

82

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in Extract Structure Posting date in the document Day on which accounting document was created Clearing date Last dunning date Due date for net payment Due date according to cash discount terms 1 Due date according to cash discount terms 2 Baseline date for due date calculation Cash discount days 1 Cash discount days 2 Net payment terms period Cash discount percentage 1 Cash discount percentage 2

Table of Origin

Field in Table of Origin

BUDAT

BSIK, BSAK

BSIK-BUDAT

CPUDT

BSIK, BSAK

BSIK-CPUDT

AUGDT MADAT

BSIK, BSAK BSIK, BSAK

BSIK-AUGDT BSIK-MADAT

NETDT

BSIK, BSAK

Calculated

SK1DT

BSIK, BSAK

Calculated

SK2DT

BSIK, BSAK

Calculated

ZFBDT

BSIK, BSAK

BSIK-ZFBDT

ZBD1T ZBD2T

BSIK, BSAK BSIK, BSAK

BSIK-ZBD1T BSIK-ZBD2T

ZBD3T

BSIK, BSAK

BSIK-ZBD3T

ZBD1P

BSIK, BSAK

BSIK-ZBD1P

ZBD2P

BSIK, BSAK

BSIK-ZBD2P

83

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure LAND1 ZLSCH ZTERM ZLSPR

Description of Field in Extract Structure Country key Payment method Terms of payment key Payment block key Reason code for payments Dunning block Dunning key Dunning level Currency key of the local currency

Table of Origin

Field in Table of Origin T001-LAND1 BSIK-ZLSCH BSIK-ZTERM BSIK-ZLSPR

T001 BSIK, BSAK BSIK, BSAK BSIK, BSAK

RSTGR

BSIK, BSAK

BSIK-RSTGR

MANSP MSCHL MANST

BSIK, BSAK BSIK, BSAK BSIK, BSAK

BSIK-MANSP BSIK-MSCHL BSIK-MANST

LCURR

T001

T001-WAERS

DMSOL

Debit amount in local currency

BSIK-SHKZG, BSIK, BSAK BSIK-DMBTR BSIK-SHKZG, BSIK, BSAK BSIK-DMBTR BSIK-SHKZG, BSIK, BSAK BSIK-DMBTR

DMHAB

Credit amount in local currency

DMSHB

Local currency amount (+/-)

SKNTO

Cash discount amount in local currency Currency key

BSIK, BSAK

BSIK- SKNTO

WAERS

BSIK, BSAK

BSIK-WAERS

84

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in Extract Structure

Table of Origin

Field in Table of Origin BSIK-SHKZG,

WRSOL

Debit amount in foreign currency

BSIK, BSAK BSIK-WRBTR BSIK-SHKZG, BSIK, BSAK BSIK-WRBTR BSIK-SHKZG, BSIK, BSAK BSIK-WRBTR

WRHAB

Credit amount in foreign currency

WRSHB

Foreign currency amount (+/-)

SKFBT

Amount eligible for cash discount in document currency Cash discount amount in document currency Chart of accounts General ledger account in G/L accounting. G/L account number Branch account number Clearing document number Reference document number Invoice document number

BSIK, BSAK

BSIK-SKFBT

WSKTO

BSIK, BSAK

BSIK-WSKTO

KTOPL

T001

T001-KTOPL

HKONT

BSIK, BSAK

BSIK-HKONT

SAKNR

BSIK, BSAK

BSIK-SAKNR

FILKD

BSIK, BSAK

BSIK-FILKD

AUGBL

BSIK, BSAK

BSIK-AUGBL

XBLNR

BSIK, BSAK

BSIK-XBLNR

REBZG

BSIK, BSAK

BSIK-REBZG

85

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in Extract Structure Fiscal year of the relevant invoice Posting item in the relevant invoice Sales document number Reference key of the business partner Reference key of the business partner Reference key for the document items Item text Flag: Negative Posting Indicator: amount already in archive Transaction class Special Ledger BW delta process: Update mode Assignment number

Table of Origin

Field in Table of Origin

REBZJ

BSIK, BSAK

BSIK-REBZJ

REBZZ

BSIK, BSAK

BSIK-REBZZ

VBELN

XREF1

BSIK, BSAK

BSIK-XREF1

XREF2

BSIK, BSAK

BSIK-XREF2

XREF3

BSIK, BSAK

BSIK-XREF3

SGTXT XNEGP

BSIK, BSAK BSIK, BSAK

BSIK-SGTXT BSIK-XNEGP

XARCH

BSIK, BSAK

BSIK-XARCH

UMSKS

BSIK, BSAK

BSIK-UMSKS

UPDMOD

ZUONR .INCLUDE DTFIAP-WF

86

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in Extract Structure Customer exits for extract structure DTFIAP_3

Table of Origin

Field in Table of Origin

.INCLUDE CI_BSIK

Calculated

9.2.12.2 Fields of Origin in the Extraction Structure - Accounts Receivable: Line Items
In the following table only the fields BIUKRS and FISCPER are filterable: Field in Extract Structure BUKRS Description of Field in Extract Structuree Company code Field in Table of Origin BSID-BUKRS BSID-GJAHR, FISCPER Fiscal year/period BSID, BSAD BSID-MONAT Accounting document number Account document posting line Subitem number

Table of Origin

BSID, BSAD

BELNR

BSID, BSAD

BSID-BELNR

BUZEI

BSID, BSAD

BSID-BUZEI

UPOSZ

= 0001 BSID-BSTAT, BSID, BSAD BSID- AUGDT BSID, BSAD BSID-KUNNR

STATUSPS

Status of the FI item (O = open, C = cleared)

KUNNR

Customer number

87

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in Extract Structuree

Table of Origin

Field in Table of Origin BSID-KKBER or T001KKBER BSID-MABER =D

KKBER

Credit control area

BSID, BSAD, T001

MABER KOART UMSKZ BLART BSCHL FISCVAR

Dunning area Account type Special G/L indicator Document type Posting key Fiscal year variant Document date in document Posting date in the document Day on which accounting document was created Clearing date Last dunning date Due date for net payment Due date according to cash discount terms 1

BSID, BSAD

BSID, BSAD BSID, BSAD BSID, BSAD T001

BSID-UMSKZ BSID-BLART BSID-BSCHL T001-PERIV

BLDAT

BSID, BSAD

BSID-BLDAT

BUDAT

BSID, BSAD

BSID-BUDAT

CPUDT

BSID, BSAD

BSID-CPUDT

AUGDT MADAT

BSID, BSAD BSID, BSAD

BSID- AUGDT BSID-MADAT

NETDT

BSID, BSAD

See below 1)

SK1DT

BSID, BSAD

See below 1)

88

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in Extract Structuree Due date according to cash discount terms 2 Baseline date for due date calculation Cash discount days 1 Cash discount days 2 Net payment terms period Cash discount percentage 1 Cash discount percentage 2 Country key Payment method Terms of payment key Payment block key Reason code for payments Dunning block Dunning key

Table of Origin

Field in Table of Origin

SK2DT

BSID, BSAD

See below 1)

ZFBDT

BSID, BSAD

BSID-ZFBDT

ZBD1T ZBD2T

BSID, BSAD BSID, BSAD

BSID-ZBD1T BSID-ZBD2T

ZBD3T

BSID, BSAD

BSID-ZBD3T

ZBD1P

BSID, BSAD

BSID-ZBD1P

ZBD2P

BSID, BSAD

BSID-ZBD2P

LAND1 ZLSCH ZTERM ZLSPR

T001 BSID, BSAD BSID, BSAD BSID, BSAD

T001-LAND1 BSID-ZLSCH BSID-ZTERM BSID-ZLSPR

RSTGR

BSID, BSAD

BSID-RSTGR

MANSP MSCHL

BSID, BSAD BSID, BSAD

BSID-MANSP BSID-MSCHL

89

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure MANST

Description of Field in Extract Structuree Dunning level Currency key of the local currency

Table of Origin

Field in Table of Origin BSID-MANST

BSID, BSAD

LCURR

T001

T001-WAERS

DMSOL

Debit amount in local currency

BSID-SHKZG, BSID, BSAD BSID-DMBTR BSID-SHKZG, BSID, BSAD BSID-DMBTR BSID-SHKZG, BSID, BSAD BSID-DMBTR

DMHAB

Credit amount in local currency

DMSHB

Local currency amount (+/-)

SKNTO

Cash discount amount in local currency Currency key

BSID, BSAD

BSID- SKNTO

WAERS

BSID, BSAD

BSID-WAERS BSID-SHKZG,

WRSOL

Debit amount in foreign currency

BSID, BSAD BSID-WRBTR BSID-SHKZG, BSID, BSAD BSID-WRBTR BSID-SHKZG, BSID, BSAD BSID-WRBTR

WRHAB

Credit amount in foreign currency

WRSHB

Foreign currency amount (+/-)

SKFBT

Amount eligible for cash discount in document currency

BSID, BSAD

BSID- SKFBT

90

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in Extract Structuree Cash discount amount in document currency Chart of accounts General ledger account in G/L accounting. G/L account number Branch account number Clearing document number Reference document number Invoice document number Fiscal year of the relevant invoice Posting item in the relevant invoice Sales document number Reference key of the business partner Reference key of the business partner

Table of Origin

Field in Table of Origin

WSKTO

BSID, BSAD

BSID- WSKTO

KTOPL

T001

T001-KTOPL

HKONT

BSID, BSAD

BSID-HKONT

SAKNR

BSID, BSAD

BSID-SAKNR

FILKD

BSID, BSAD

BSID-FILKD

AUGBL

BSID, BSAD

BSID-AUGBL

XBLNR

BSID, BSAD

BSID-XBLNR

REBZG

BSID, BSAD

BSID-REBZG

REBZJ

BSID, BSAD

BSID-REBZJ

REBZZ

BSID, BSAD

BSID-REBZZ

VBELN

BSID, BSAD

BSID-VBELN

XREF1

BSID, BSAD

BSID-XREF1

XREF2

BSID, BSAD

BSID-XREF2

91

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in Extract Structuree Reference key for the document items Item text Flag: Negative Posting Indicator: amount already in archive Transaction class Special Ledger BW delta process: Update mode Assignment number Customer exits for extract structure DTFIAR_3

Table of Origin

Field in Table of Origin

XREF3

BSID, BSAD

BSID-XREF3

SGTXT XNGEP

BSID, BSAD BSID, BSAD

BSID-SGTXT BSID- XNGEP

XARCH

BSID, BSAD

BSID-XARCH

UMSKS

BSID, BSAD

BSID-UMSKS

UPDMOD

ZUONR

.INCLUDE CI_BSID

9.2.13 Configuration of Cost Center Accounting


Cost Center Accounting is configurable therefore not all extractor columns return values. The FISCPER column extracts the fiscal period generally under the format YYYYMMM. For example,if you need data from January 2009 filter FISCPER on 2009001.

9.2.13.1 Fields of Origin in the Extraction Structure of 0CO_OM_CCA_3

92

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Ex- Description of Field tract Struc- in the Extract StrucTable of ture ture Filterable Origin MEASTYPE VTSTAT Key Figure Category Statistics Indicator for Value Type Value Type for Reporting Version Fiscal Year/Period X COSL COSL

Field in Table of Origin /Remarks

VTYPE

COSL

VERSN FISCPER

X X

COSL COSL GJAHR of the totals record + period of the value field For the controlling area from table TKA01 From the OBJNR of the totals record (places 3-6 of the object number) From the OBJNR of the totals record (places 7-16 of the object number) From the OBJNR of the totals record (places 17-24 of the object number) AUSEH MEINH AUS001-AUS016 DIS001-DIS016

FISCVAR

Fiscal Year Variant

COSL

KOKRS

Controlling Area

COSL

KOSTL

Cost Center

COSL

LSTAR

Activity Type

COSL

AUSEH LEINH SAUS SDIS

Output Unit Activity Unit Output Scheduled Activity Quantity

COSL COSL COSL COSL

93

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Ex- Description of Field tract Struc- in the Extract StrucTable of ture ture Filterable Origin SKAP SLST VKSTA Capacity Activity Quantity Allocation Cost Element COSL COSL COKL

Field in Table of Origin /Remarks KAP001-KAP016 LST001-LST016 VKSTA

9.2.13.2 Fields of Origin in the Extraction Structure of 0CO_OM_CCA_4

Field in Ex- Description of Field tract Struc- in the Extract Filterture Structure able MEASTYPE Key figure category VTSTAT Statistics indicator for value type Value type for report- X ing Version Fiscal year/period X X

Table of Origin COSR COSR

Field in Table of Origin/ Remarks

VTYPE

COSR

VERSN FISCPER

COSR COSR GJAHR of the totals record + period of the value field For the controlling area from table TKA01 From the OBJNR of the totals record (places 3-6 of the object number)

FISCVAR KOKRS

Fiscal year variant Controlling area X

COSR COSR

94

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Ex- Description of Field tract Struc- in the Extract Filterture Structure able KOSTL Cost center X

Table of Origin COSR

Field in Table of Origin/ Remarks From the OBJNR of the totals record (places 7-16 of the object number) From the OBJNR of the totals record (places 17-24 of the object number) MEINH of the totals record

LSTAR

Activity type

COSR

MEINH SSME SSMED

Unit of measure Quantity Inventory quantity

COSR COSR

SME001- Whether SSME or SSMED is filled depends SME016 on the category of the statistical key figure. STAGR

STAGR

Statistical key figure X

9.2.13.3 Fields of Origin in the Extraction Structure of 0CO_OM_CCA_9


All amounts are extracted using different currencies for example, transaction currency, company code, currency, and controlling area currency, therefore, in most cases, you must put a filter on the CURTYP column of the extractor (CURTYP=00 means transaction currency.) Description of Field in the Extract Structure

Field in Extract Structure

Filterable

Table of Origin

Field in Table of Origin /Remarks

CURTYP

Currency Type

COVP (COEP and COBK)

See Mapping the Currency Type and Currency Key

95

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in the Extract Structure

Filterable

Table of Origin

Field in Table of Origin /Remarks

SMEF

Fixed Consumption Quantity

Value fields MEF* of the totals record. See Mapping the Currency Type and Currency Key and SAP Note 175624 Value fields MEG* of the totals record. See Mapping the Currency Type and Currency Key. = SMEG - SMEF See Mapping the Currency Type and Currency Key. Value fields WKF*, WOF* and WTF* of the totals record. See Mapping the Currency Type and Currency Key. Value fields WKG*, WOG* and WTG* of the totals record. See Mapping the Currency Type and Currency Key. = SWG - SWF. See Mapping the Currency Type and Currency Key.

SMEG

Consumption Quantity

SMEV

Variable consumption quantity

SWF

Fixed Amount

SWG

Amount

SWV

Variable Amount

MEASTYPE

Key Figure Category

96

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in the Extract Structure Detailing the Value Type Statistics Indicator for Value Type Value Type for Reporting Specification of a partner InfoObject Partner InfoObject (4-characters)

Filterable

Table of Origin

Field in Table of Origin /Remarks

VTDETAIL

VTSTAT

VTYPE

RSPAROBVAL

See Mapping the Partner Object and Partner Object Type

RSPOBART

SEKNZ

Sender/Receiver Indicator

See Mapping the Currency Type and Currency Key. See Mapping the Version and Transfer Price Valuation

VALUTYP

Valuation View

VERSN

Version See Mapping the Currency Type and Currency Key GJAHR of the totals record + period of the value field

WAERS

Currency Key

FISCPER

Fiscal Year/Period

97

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in the Extract Structure

Filterable

Table of Origin

Field in Table of Origin /Remarks

FISCVAR

Fiscal Year Variant

For the controlling area from table TKA01 From the OBJNR of the totals record (places 3-6 of the object number) From the OBJNR of the totals record (places 7-16 of the object number) KSTAR of the totals record From the OBJNR of the totals record (places 17-24 of the object number) MEINH of the totals record From the value type WRTTP (CORRTYPE = X , if WRTTP = 8 or 9 ) Depends on transaction (BEKNZ) from USPOB possibly PAROB

KOKRS

Controlling Area

KOSTL

Cost Center

KSTAR

Cost Element

LSTAR

Activity Type

MEINH

Unit of Measure

CORRTYPE

Correction Type (BW)

COSP

CCTR_IBV

Cost centers for elimination of internal business volume (BW) Document Number

COST, COEJ, COEP

BELNR

COVP

BELNR

98

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in the Extract Structure Document Date Posting Date Company Code Posting Row Functional Area Funds: Funds & Function Grant: Funds & Function Business Area Chart of Accounts Customer Number Account Number of Vendor or Creditor Material Number Company Code of Partner

Filterable

Table of Origin

Field in Table of Origin /Remarks

BLDAT BUDAT BUKRS BUZEI FKBER

BLDAT BUDAT BUKRS BUZEI FKBER

GEBER

GEBER

GRANT_NBR

GRANT_NBR

GSBER

GSBER

KTOPL

T001

KTOPL

KUNNR

COVP

Converted from GKONT

LIFNR

MATNR

MATNR

PBUKRS

PBUKRS

99

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in the Extract Structure Personnel Number Partner Functional Area Partner Funds: Funds & Function Partner Grant: Funds & Function Notification Number Company Code of FI Document Reference Document Number Document Type of Reference Document Posting Row of Reference Document Fiscal Year of Reference Document

Filterable

Table of Origin

Field in Table of Origin /Remarks

PERNR

PERNR

PFKBER

PFKBER

PGEBER

PGEBER

PGRANT_NBR

PGRANT_NBR

QMNUM

QMNUM

REFBK

REFBK

REFBN

REFBN

REFBT

REFBT

REFBZ

REFBZ

REFGJ

REFGJ

100

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in the Extract Structure Object Type for Auxiliary Account Assignment Auxiliary Account Assignment Object G/L Account Number

Filterable

Table of Origin

Field in Table of Origin /Remarks

RSAUXACC TYPE

Calculation from information on partner object for BUE

RSAUXACCVAL

SAKNR

Converted from GKONT COVP SGTXT

SGTXT

Segment Text BW Delta Process: Update Mode Plant COVP

UPDMODE

User Input

WERKS

WERKS

9.2.13.3.1 Mapping the Currency Type and Currency Key


In contrast to R/3, the values of the individual posting periods and currency types that is, transaction currency, object currency, and controlling area currency, are extracted to SAP BW in individual data records rather than as a single block. The currency type (0CURTYPE) then indicates the fields of the R/3 totals records from which the values were read. Currency Type 00 Description Transaction currency Currency of company code (object currency) Controlling area currency Fields in R/3 Totals Record WTG*

10

WOG*

20

WKG*

101

2012-03-08

Using the Financial Information Management Application with SAP ERP

Currency Type 70

Description Object currency

Fields in R/3 Totals Record WOG*

Extraction results in a maximum multiplication of the selected R/3 totals records by a factor of 48 = 3 * 16 = number of currency types * number of periods (12 + 4 special periods). Zero values -- both the cost amount and the quantity are zero -- are not transferred. The quantities are transferred with each currency type. When defining queries, you must also specify a restriction for quantity columns on a currency type. We recommend adding the currency type as a filter parameter for the entire query. Restricting the currency type to the values required in BW significantly improves performance during extraction. Costs in object currency are transferred with currency type 10 as a default, regardless of whether selection in the InfoPackage is on currency type 70 or 10. If necessary, this default setting can be changed from 10 to 70 in the control table BWOM_SETTINGS (parameter OBJCURTYPE). The currency key 0CURRENCY is determined based on the currency type: Currency Type Determination of Currency Key Taken directly from the data record read (COSPTWAER, COSS-TWAER etc.) Determined from the object number of the record from the master data. The controlling area is determined from the object number of the record read. The currency of the controlling area is then determined. See currency type 10

00

10

20

70

9.2.13.3.2 Mapping the Partner Object and Partner Object Type


0PIOVALUE and 0PIOBJSV are determined from the Partner Object field of the COSS records for the following partner object types:

102

2012-03-08

Using the Financial Information Management Application with SAP ERP

R/3 Object Type

Description

BW Partner Object Type 0PIOBJSV 0CCT 0ATY 0COR 0ABC 0POS 0SDP

KS KL OR BP PR VB

Cost center Cost center/activity type Order Business process WBS element Sales order

For all other R/3 object types, the BW partner object is determined generically as follows: The first place of the values of 0PIOBJSV is always 0. The first value is followed by the English 3-character short name of the object type from table tbo01, field OBART_LD.

9.2.13.3.3 Mapping the Debit/Credit Indicator (0DB_CR_IND)


The debit/credit indicator represents the sender/receiver relationships from the Controlling perspective. It is therefore not a 1:1 mapping of the debit/credit indicator BEKNZ which distinguishes between debits and credits with primary cost postings and is updated in the CO totals record tables (for more information on this, see Note 65075). The following conversions are made for the transfer into BW: For the following transactions, SEKNZ is always S (debit) if the value in the field BEKNZ of the totals record is not A (settlement) or L (delivery to stock): COIN (CO through-postings from Financial Accounting) RKU1 (repost costs) RKU2 (repost revenue) RKU3 (repost CO line items) KZRI (interest calculation - actual) (see Note 314540) KZRP (interest calculation - plan) (see Note 314540) KSI1 (split actual primary) (see Note 314540) KSP1 (split plan primary) (see Note 314540) RKIB (actual periodic repostings) RKPB (planned periodic repostings) COIE (CO sales order/project stock) (see Note 314540)

103

2012-03-08

Using the Financial Information Management Application with SAP ERP

RRIB (segment adjustment periodic reposting - actual) (in R/3 from Release 4.0, see Note 314540)

For the values L (delivery to stock) and A (settlement) in the field BEKNZ of the selected totals records, SEKNZ is always H (credit). In all other cases, SEKNZ = BEKNZ

Note: The debit/credit indicator SEKNZ transferred to BW is not the same as the characteristic BELKZ, the debit/credit indicator CO, of the Report Writer report table CCSS in R/3. In this table, the values A and L are no longer replaced with H from Release 4.0 onward.

9.2.13.3.4 Mapping the Version and Transfer Price Valuation


The values transferred to BW for the InfoObjects 0VERSION and 0VALUATION depend on the following parameters in R/3: Controlling area of the object: COSP-OBJNR, COSS-OBJNR Version field of the records read: COSP-VERSN, COSS-VERSN Settings for the transfer price valuations in R/3 Customizing

Extraction into BW is based on the delta version logic of R/3. That is, only records with complete amounts are transferred. For example, for a valuation that is updated in R/3 in a delta version, the amounts of the version belonging to the base valuation are added automatically. Delta versions of activity-based costing are not supported. Initializing the Extraction: ROMU_GET_VERSN_FOR_VALUATION or ROMU40_GET_VERSN_FOR_VALUATION: If selection criteria were entered for 0VERSION and 0VALUATION (valuation), the extractor maps the version required for this valuation as well as the base version, and adds them to the selection criteria for 0VERSION. (Module K_VERSN_VALUATION in ROMU_GET_VERSN_FOR_VALUATION or ROMU40_GET_VERSN_FOR_VALUATION). If no selection criteria were entered for 0VERSION, all versions (and therefore all valuation versions) are always selected. Processing of the imported totals records/line items: ROMU_ENHANCE_VERSN_IN_DATA or ROMU40_ENHANCE_VERSN_IN_DATA: The system determines whether the version of the imported record is an operational version or a delta version. If it is an operational version, the record is copied for all delta versions belonging to that operational version. The delta version is entered into the new, copied records. The new, copied records then run through the complete mapping logic of the extractor for all other fields as well. ROMU_GET_VALUTYP_FROM_VERSN or ROMU40_GET_VALUTYP_FROM_VERSN: For the version of the record read, the valuation in Customizing of the versions is determined and entered in 0VALUATION. ROMU_RESET_CO_VERSN or ROMU40_RESET_CO_VERSN:

104

2012-03-08

Using the Financial Information Management Application with SAP ERP

For versions that do not belong to the basic valuation, the version is set to 000.

9.2.14 Configuration of Activity Based Costing


Activity Based Costing is configurable therefore not all extractor columns return values. The FISCPER column extracts the fiscal period generally under the format YYYYMMM. For example, if you want data from January 2009, filter FISCPER on 2009001.

9.2.14.1 Fields of Origin in the Extraction Structure of 0CO_OM_ABC_2

Field in Extract Structure

Description of Field in the Extract Structure Key Figure Type Statistics Indicator for Value Type Value Type for Reporting Version

Filter able

Table of Origin

Field in Table of Origin / Remarks

MEASTYPE

COSL

VTSTAT

COSL

VTYPE

COSL

VERSN

COSL GJAHR of the totals record + period of the value field For the controlling area from table TKA01 From the OBJNR of the totals record (places 3-6 of the object number)

FISCPER

Fiscal Year/Period

COSL

FISCVAR

Fiscal Year Variant

COSL

KOKRS

Controlling Area

COSL

105

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in the Extract Structure

Filter able

Table of Origin

Field in Table of Origin / Remarks

AUSEH AUSEH Output Unit COSL Check table T006 Business Process Attribute: Category External Value Added Ranking (CO-ABC) Internal Value Added Ranking (CO-ABC) Business Process Attribute: Allocation Category (CO-ABC)

CBART

CBPR

CBART

CBRKE

CBPR

CBRKE

CBRKI

CBPR

CBRKI

DRVTP

CBPR

DRVTP

LEINH LEINH Activity Unit CBPR Check table T006 PRZNR Business Process X PRZNR Calculated from AUS001AUS016 (in SAPLBWOM/ RESOLVE_PERIODS_ACT). Calculated from DIS001DIS016 (in SAPLBWOM/ RESOLVE_PERIODS_ACT). Calculated from KAP001KAP016 (in SAPLBWOM/ RESOLVE_PERIODS_ACT).

SAUS

Output

COSL

SDIS

Scheduled Activity Quantity

COSL

SKAP

Capacity

COSL

106

2012-03-08

Using the Financial Information Management Application with SAP ERP

Field in Extract Structure

Description of Field in the Extract Structure

Filter able

Table of Origin

Field in Table of Origin / Remarks

SLST

Activity Quantity

COSL

Calculated from LST001LST016 (in SAPLBWOM/ RESOLVE_PERIODS_AC.

VKSTA

Allocation Cost Element

CBPR

VKSTA

9.3 Enriching the ECC Datasource List

9.3.1 Enriching the ECC Datasource List


When creating a job using SAP ECC as a source connection to an EPM target application, you select a datasource from a default list. Although this list is limited, you can enhance it by modifying the FIM server configuration file. The available ECC datasources and their drill-to-source definitions are declared in the sap-eccmetadata.csv file located in the following folder: <fim install directory>\WEB-INF\. The datasource, transaction type, and parameters are shown in the following format: <ECC datasource name>,~transaction=*<transaction code>,<parameter 1>=<value 1>&<parameter 2>=<value 2>&..&<parameter n>=<value n>& DYNP_OKCODE=<okcode>. The sap-ecc-metadata.csv file is as follows: 0FI_GL_10,~transaction=*FAGLB03,RBUKRS-LOW=%SC_RBUKRS%&RACCT-LOW=%SC_RAC CT%&RYEAR=%SC_FISCPER{0:4}%&DYNP_OKCODE=OKCODE 0FI_GL_20,~transaction=*FAGLB03,RBUKRS-LOW=%SC_RBUKRS%&RACCT-LOW=%SC_RAC CT%&RYEAR=%SC_FISCPER{0:4}%&DYNP_OKCODE=OKCODE 0EC_PCA_1,~transaction=*KE5Z,RRCTY-LOW=0&RVERS-LOW=%SC_RVERS%&KOKRSLOW=%SC_KOKRS%&BUKRS-LOW=%SC_RBUKRS%&POPER-LOW=%SC_FISCPER{4:3}%&PRCTRLOW=%SC_RPRCTR%&RFAREA-LOW=%SC_RFAREA%&RACCT-LOW=%SC_RACCT%&RYEARLOW=%SC_FISCPER{0:4}%&DYNP_OKCODE=OKCODE

107

2012-03-08

Using the Financial Information Management Application with SAP ERP

0FI_AP_4,~transaction=*FB03,RF05L-BUKRS=%SC_BUKRS%&RF05L-BELNR=%SC_BEL NR%&RF05L-GJAHR=%SC_FISCPER{0:4}%&DYNP_OKCODE=/00 0FI_AR_4,~transaction=*FB03,RF05L-BUKRS=%SC_BUKRS%&RF05L-BELNR=%SC_BEL NR%&RF05L-GJAHR=%SC_FISCPER{0:4}%&DYNP_OKCODE=/00 0FI_AP_30,~transaction=*FB03,RF05L-BUKRS=%SC_BUKRS%&RF05L-BELNR=%SC_BEL NR%&RF05L-GJAHR=%SC_FISCPER{0:4}%&DYNP_OKCODE=/00 0FI_AR_30,~transaction=*FB03,RF05L-BUKRS=%SC_BUKRS%&RF05L-BELNR=%SC_BEL NR%&RF05L-GJAHR=%SC_FISCPER{0:4}%&DYNP_OKCODE=/00 0FI_GL_20,~transaction=*FAGLB03,RBUKRS-LOW=%SC_RBUKRS%&RACCT-LOW=%SC_RAC CT%&RYEAR=%SC_FISCPER{0:4}%&DYNP_OKCODE=OKCODE 0CO_OM_CCA_3,, 0CO_OM_CCA_4,, 0CO_OM_CCA_9,, 0CO_OM_ABC_2,, Each line corresponds to an ECC datasource. The first element of each line corresponds to the extractor name and the following parameters correspond to drill-to-source redirection, if applicable. If you want to add an ECC datasource without drill-to-source redirection, you add a line with the ECC datasource name followed by two commas. Once you have added a datasource, you must activite it to make it available in the financial information management application. A good example of adding a datasource is the addition of an ECC datasource for the CO-PA module. Related Topics Activating a Datasource

9.3.1.1 Adding an ECC Datasource for the CO-PA Module


The CO-PA module is a highly-configurable module. You create datasources using the SBIW transaction as follows: 1. Create your datasource, then name the datasource using the following syntax: 1_CO_PA<client><Operating concern>. Example: client 004 for the operating concern S_GO is named as follows: 1_CO_PA004S_GO 2. Run the SBIW transaction.

108

2012-03-08

Using the Financial Information Management Application with SAP ERP

3. Expand the structure, then select CreateTransaction Data DataSource 4. Under "Function", select "Create", and in the "Operating concern" box, type the name of the operating concern for which you want to create the datasource for example, S_GO.

5. Click the Execute icon. 6. In the next screen, in the appropriate fields, enter the following names for the datasource: "Short text" "Medium-length text" "Long text"

109

2012-03-08

Using the Financial Information Management Application with SAP ERP

7. Select the characteristics you want to use. 8. Click the green check icon when you have finished.

The CO_PA datasource is created. 9. In the FIM server directory, open the sap-ecc-metadata.csv file and add the following line : 1_CO_PA005S_GO,, Restart the Tomcat 6 server to allow the modification of the sap-ecc-metadata.csv file to be taken into account.

110

2012-03-08

Using the Financial Information Management Application with SAP ERP

9.4 Configuring Drill-to-Source

9.4.1 Configuring Drill-to-Source for an ECC Datasource


Once you have added an ECC datasource to the sap-ecc-metadata.csv file, you can configure the drill to source link that is used from the drill-to-origin page. The drill-to-source mechanism is specific to a given SAP ECC datasource; it leverages the web ITS GUI. The format of the sap-ecc-metadata.csv file is as follows: <ECC datasource name>,~trans action=*<transaction code>,<parameter 1>=<value 1>&<parameter 2>=<value 2>&..&<parameter n>=<value n>& DYNP_OKCODE=<okcode> Proceed as follows: 1. Associate the datasource to the SAP transaction that you want to use to interpret the output of the datasource by replacing <ECC datasource name> and <transaction code> with the proper values. 2. Define the following: the parameters that you want to pass to that transaction the name of the OKCODE used to acknowledge the search screen of the transaction Example: The datasource 0FI_AP_4 extracts line items from the Account Payable (AP) module. Therefore, it is associated with the FB03 transaction that displays Accounts Payable documents. The datasource reads as follows: 0FI_AP_4,~transaction=*FB03,RF05LBUKRS=%SC_BUKRS%&RF05L-BELNR=%SC_BELNR%&RF05L-GJAHR=%SC_FIS CPER{0:4}%&DYNP_OKCODE=/00 The parameters are: BELNR: Document Number BUKRS: Company Code FISCPER: FIscal Period When launched, the FB03 transaction asks for the following information: Document Number Company Code Fiscal Year as shown in the following screen:

111

2012-03-08

Using the Financial Information Management Application with SAP ERP

9.4.1.1 Setting the Name of the Parameters


After associating the datasource to the transaction you need to set the name of the parameters. Proceed as follows for each of the "Keys for Entry View". The values are the names of the parameters you use in the datasource. 1. In the SAP GUI, click inside the field, then press F1.

The "Performance Assistant" opens. 2. Click the Technical Information button.

The Technical Information screen displays the technical information relating to that particular field. For example, the field name BELNR refers to the document number.

112

2012-03-08

Using the Financial Information Management Application with SAP ERP

3. In the "Technical Information" screen, locate the value for the "Screen Field". This is the name of the parameter.

4. Repeat the operation for all fields from the search screen for which you want names.

9.4.1.2 Values for the Parameters


When providing values for the parameters in the datasource, you must place the SC_ prefix on the datasource colum and enclose the datasource by the percentage symbol for example,. Example: In the 0FI_AP_4 datasource, the document number is output to the BELNR column, therefore, the value reads %SC_BELNR% and the parameter/value pair reads RF05L-BELNR=%SC_BELNR% Note: You can apply a substring calculation over datasource columns using the following syntax: %SC_COLUMN{starting position:number of characters}% The starting position is set to 0, therefore, if you need only the first two characters of a column the syntax is %SC_COLUMN{0:2}%

113

2012-03-08

Using the Financial Information Management Application with SAP ERP

Example: The transaction FB03 expects the fiscal year as a parameter (RF05L-GJAHR) however the 0FI_AP_4 datastore has a field, FISCPER, that has a column that contains two parameters, the fiscal year and the period. For this reason, we use only the four first characters from the FISCPER column: RF05LGJAHR=%SC_FISCPER{0:4}

9.4.1.3 OKCODE
In most cases you can use /00 as the parameter for the OKCODE, however if you need a different OKCODE, proceed as follows: 1. From the main menu of the initial screen select System > Status.

2. In the "System:Status" page, double-click inside the "GUI status" box.

114

2012-03-08

Using the Financial Information Management Application with SAP ERP

3. In the next screen, "Display Status", expand the application toolbar.

115

2012-03-08

Using the Financial Information Management Application with SAP ERP

OKCODE is located in the table under "Application Toolbar", for example, "SRCH". For the datastore 0FI_AP_4 the line reads : 0FI_AP_4,~transaction=*FB03,RF05LBUKRS=%SC_BUKRS%&RF05L-BELNR=%SC_BELNR%&RF05L-GJAHR=%SC_FISCPER{0:4}%&DYNP_OK CODE=/00. Note: Not all SAP transactions can be used with this procedure because it allows you to pass only one series of parameters at a time: only one OKCODE; these codes are not cascadable. Most transactions associated with the CO module prompt you for a Controlling Area before entering the transaction main search screen, and SAP transactions that leverage START_REPORT do not work in this context becauses parameters are passed to START_REPORT initially. You can, however, create your own custom transaction that will address directly the report. For example, the following transactions can be used in the context of using 0CO_OM_CCA_3 and 0CO_OM_CCA_4: S_ALR_87013611 - Cost Centers Actual-Plan-Variance can be used for 0CO_OM_CCA_3 S_ALR_87013645 - Statistical Key Figures: Period Breakdown can be used for 0CO_OM_CCA_4

116

2012-03-08

Using the Financial Information Management Application with SAP ERP

9.4.2 Configuring Drill-to-Source for the 0CO_OM_CCA_3 Datasource, Part 1


First you determine which program is associated with the transaction, then you create a custom transaction, and finally you configure the drill-to-source link definition. To locate the program number proceed as follows: 1. Run the transaction.

2. Right-click and locate "Program" in the menu. 3. Copy the program number. You need this information when creating the custom transaction.

9.4.2.1 Configuring Drill-to-Source for the 0CO_OM_CCA_3 Datasource, Part 2


In this procedure you create the custom transaction. Before you begin, make sure that you have located the number of the program. 1. Launch transaction SE93 to begin creating the custom transaction. 2. In the Transaction code box, type a transaction code, for example, Z_FIM_3.

117

2012-03-08

Using the Financial Information Management Application with SAP ERP

3. Click Create. 4. In the "Create Transaction" screen, type a short text. 5. Select "Program and selection screen", then click the green check icon.

6. In the next screen in the Package box, assign the transaction to a package. 7. In the "Program" box, type the number of the program, which is the information you located previously. 8. Select the "SAPGUI" check boxes. The custom transaction is created. Next, you create the drill-to-source link definition as explained previously.

118

2012-03-08

Using the Financial Information Management Application with SAP ERP

Example: 0CO_OM_CCA_3,~transaction=*Z_FIM_3,$1KOKRE=%SC_KOKRS%&$1GJAHR=%SC_FIS CPER{0:4}%&$1PERIB=%SC_FISCPER{5:2}%&$1PERIK=%SC_FISCPER{5:2}%&_1KOSETLOW=%SC_KOSTL%&_1KSTAR-LOW=%SC_VKSTA%&DYNP_OKCODE=/00 Related Topics Configuring Drill-to-Source for an ECC Datasource Configuring Drill-to-Source for the 0CO_OM_CCA_3 Datasource, Part 1

9.4.3 Configuring Drill-to-Source for the 0CO_OM_CCA_4 Datasource


The procedure for configuring drill-to-source for the 0CO_OM_CCA_4 datasource is similar to that used to configure the 0CO_OM_CCA_3 datasource: first you determine which program is associated with the transaction, then you create a custom transaction, and finally you configure the drill-to-source link definition. Before you begin, locate the number of the program as you did with the 0CO_OM_CCA_3 datasource , then proceed as follows: 1. Launch transaction SE93. 2. In the Transaction code box, type a transaction code, for example, Z_FIM_4.

3. Click Create. 4. In the "Create Transaction" screen, type a short text.

119

2012-03-08

Using the Financial Information Management Application with SAP ERP

5. Select "Program and selection screen", then click the green check icon. 6. In the next screen, in the Package box, assign the transaction to a package. 7. In the "Program" box, type the number of the program, which is the information you located previously. 8. Select the "SAPGUI" check boxes.

Next, you create the drill-to-source link definition as explained previously. Example: 0CO_OM_CCA_4,~transaction=*Z_FIM_4,$1KOKRE=%SC_KOKRS%&$1GJAHR=%SC_FIS CPER{0:4}%&$1PERIB=%SC_FISCPER{5:2}%&$1PERIK=%SC_FISCPER{5:2}%&_1KOSETLOW=%SC_KOSTL%&_1KSTAR-LOW=%SC_VKSTA%&DYNP_OKCODE=/00

120

2012-03-08

Using the Financial Information Management Application with SAP ERP

Related Topics Configuring Drill-to-Source for an ECC Datasource

121

2012-03-08

Using the Financial Information Management Application with SAP ERP

122

2012-03-08

Troubleshooting

Troubleshooting

10.1 Errors Returned with SAP NetWeaver BW in Target


The following errors are returned is returned when SAP NetWeaver BW is the target application in the error log: Error opening BW datastore <name_of_datastore> for loading. Check your connection. in the trace log : Job <jobname> is terminated due to error <error_ID> The errors are caused by an incorrect routing string.

10.2 Could Not Send Message


If, in the error pane, you receive the following message: "Could not sent message" you need to manually modify a file as follows: 1. If you: are not using data services server groups, open the server.properties and leave the parameter dataServices.serverGroup blank. are using server groups, open the <Data Services Install Location>\bin\DSCon fig.txt file. 2. Locate the parameter Native_Webservice_Call_Timeout_Miliseconds. 3. Modify the parameter to increase the value from the default 30000 to 300000. 4. Save the file.

123

2012-03-08

Troubleshooting

124

2012-03-08

More Information

More Information

Information Resource

Location

SAP BusinessObjects product information

http://www.sap.com Navigate to http://help.sap.com/businessobjects and on the "SAP BusinessObjects Overview" side panel click All Products. You can access the most up-to-date documentation covering all SAP BusinessObjects products and their deployment at the SAP Help Portal. You can download PDF versions or installable HTML libraries. Certain guides are stored on the SAP Service Marketplace and are not available from the SAP Help Portal. These guides are listed on the Help Portal accompanied by a link to the SAP Service Marketplace. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative. http://service.sap.com/bosap-support > Documentation Installation guides: https://service.sap.com/bosap-instguides Release notes: http://service.sap.com/releasenotes

SAP Help Portal

SAP Service Marketplace

The SAP Service Marketplace stores certain installation guides, upgrade and migration guides, deployment guides, release notes and Supported Platforms documents. Customers with a maintenance agreement have an authorized user ID to access this site. Contact your customer support representative to obtain an ID. If you are redirected to the SAP Service Marketplace from the SAP Help Portal, use the menu in the navigation pane on the left to locate the category containing the documentation you want to access. https://cw.sdn.sap.com/cw/community/docupedia

Docupedia

Docupedia provides additional documentation resources, a collaborative authoring environment, and an interactive feedback channel. https://boc.sdn.sap.com/

Developer resources https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary

125

2012-03-08

More Information

Information Resource

Location

SAP BusinessObjects articles on the SAP Community Network

https://www.sdn.sap.com/irj/boc/businessobjects-articles These articles were formerly known as technical papers. https://service.sap.com/notes

Notes These notes were formerly known as Knowledge Base articles. Forums on the SAP Community Network https://www.sdn.sap.com/irj/scn/forums http://www.sap.com/services/education Training From traditional classroom learning to targeted e-learning seminars, we can offer a training package to suit your learning needs and preferred learning style. http://service.sap.com/bosap-support Online customer support The SAP Support Portal contains information about Customer Support programs and services. It also has links to a wide range of technical information and downloads. Customers with a maintenance agreement have an authorized user ID to access this site. To obtain an ID, contact your customer support representative. http://www.sap.com/services/bysubject/businessobjectsconsulting Consulting Consultants can accompany you from the initial analysis stage to the delivery of your deployment project. Expertise is available in topics such as relational and multidimensional databases, connectivity, database design tools, and customized embedding technology.

126

2012-03-08

Index
0EC_PCA_1 70 0FI_AP_30 69 0FI_AP_4 69 0FI_AR_30 69 0FI_AR_4 69 0FI_GL_10 67 0FI_GL_20 67 Oracle 15, 16, 38

E
ECC 55, 63 executor 19 export dataflow 32

P
process chain 50 process variant 50

A
administrator 19 architecture 9

F
flat file, importing 38 flat files 29

R
rejected rows 33 repository 35 Reverse proxy 24 RFC 42, 43 rows of data 29

B
BAPI 41, 50 batch jobs 39 business user 19

J
jobs, importing 38 jobs, moving 37

S
SAP ERP 55 SAP GUI 58 server groups 25 SSL 21

L
load dataflow 33 logs 24

C
connectors 56

D
Data Services 31 data services, repository 35 data transfer process 48 dataflows 31 DataServices connectors 56 datasources 63 datastore 33 drill to source 60, 61, 62 DTP 48, 50

M
masterdata browsing 52 maximum connections 17

T
time out 29 Tomcat logs 24 trace logs 24 Transformation 48

N
native jobs 56 NetWeaver BW 41

V
variables 34

O
objects 33 Open Hub 46, 48, 52

W
web services 36

127

2012-03-08

Index

128

2012-03-08