FPM75 FI UserGuide en

SAP BusinessObjects Financial Information Management User Guide SAP BusinessObjects Financial Information Management 7.
2011-03-11
Copyright
2011 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 S.A. in the United States and in other countries. Business Objects 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. 2011-03-11
Contents
Chapter 1
Document History...................................................................................................................7
Chapter 2
SAP BusinessObjects Financial Information Management.....................................................9 About SAP BusinessObjects Financial Information Management..............................................9 Prerequisites............................................................................................................................9 Job Workflow...........................................................................................................................9 User Roles.............................................................................................................................10 Creating Connections...........................................................................................................13 Source and Target Database Connections.............................................................................13 Creating a Financial Consolidation Connection.......................................................................13 Creating a Profitability and Cost Management Connection ....................................................13 Creating a Planning and Consolidation Connection................................................................14 Creating an MS SQL Server Database Connection...............................................................14 Creating an Oracle Database Connection..............................................................................15 Creating Jobs........................................................................................................................17 About Jobs............................................................................................................................17 Creating a Job.......................................................................................................................17 Duplicating an Existing Job.....................................................................................................19 About Source Data................................................................................................................19 Defining the Target Properties................................................................................................21 About Mapping Tables...........................................................................................................22 Rules in mapping tables..........................................................................................................22 Creating Mapping Tables.......................................................................................................23 Error Checks in Creating a Mapping Table.............................................................................24 Populating Mapping Tables.....................................................................................................24 Patterns Used in Mapping Table Source Columns..................................................................25 Target Column Values............................................................................................................27 Populating Mapping Tables from Microsoft Excel...................................................................28 Populating Mapping Tables from Financial Consolidation DataLink Definitions........................28 Importing Data into the SAP Business Planning and Consolidation Application.......................29
2.1 2.1.1 2.1.2 2.1.3

Chapter 3
3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5

Chapter 4
4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.2 4.2.1 4.2.2 4.2.3 4.3 4.3.1 4.3.2 4.3.3 4.3.4 4.3.5
2011-03-11
Contents
4.3.6 4.3.7 4.4 4.4.1 4.4.2 4.4.3 4.5

Chapter 5
Importing Comments from the Business Planning and Consolidation Application into the Financial Consolidation Application.......................................................................................................30 Mapping Table History...........................................................................................................30 Moving Financial Information Management Job Definitions ....................................................30 Exporting a Financial Information Management Job................................................................31 Importing a Financial Information Management Job................................................................31 Importing a Custom Job.........................................................................................................32 Job Run History.....................................................................................................................33 Executing Jobs......................................................................................................................35 Executing a Financial Consolidation Job.................................................................................35 About Profitability and Cost Management Job Execution.......................................................36 Executing a Profitability and Cost Management Job...............................................................36 Selecting a Profitability and Cost Management Model at Runtime..........................................37 Exporting Data from the Business Planning and Consolidation Application.............................37 Importing Data into the SAP Business Planning and Consolidation Application.......................38 Launching a Job Via an External Scheduler............................................................................38 About the Drill-to-Origin Feature..........................................................................................41 Displaying the Origin of Data in Financial Consolidation..........................................................41 Displaying the Origin of Data in Profitability and Cost Management.......................................42 Example of the Drill-to-Origin Feature.....................................................................................42 Drill-to-origin: Open in Excel...................................................................................................44 Sharing Transaction Tables Among Several Jobs.................................................................45
5.1 5.2 5.2.1 5.2.2 5.3 5.3.1 5.4

Chapter 6
6.1 6.2 6.2.1 6.2.2

Chapter 7
Chapter 8
Example: Defining and Populating a Mapping Table.............................................................47 Defining a Mapping Table - Source Data................................................................................47 Linking Source to Target Definitions.......................................................................................48 Results...................................................................................................................................49 Example: Mapping Rule Behavior .........................................................................................51
8.1 8.2 8.3

Chapter 9
Chapter 10
Use Cases.............................................................................................................................55 Use Case 1............................................................................................................................55 Use Case 2............................................................................................................................56 Custom Jobs.........................................................................................................................59 About Data Services Job Customization................................................................................59
10.1 10.2
Chapter 11
11.1
2011-03-11
Contents
11.1.1 11.1.2 11.1.3 11.1.4 11.2 11.3 11.4 11.5 11.5.1 11.5.2 11.5.3
Appendix A Index
Dataflows...............................................................................................................................59 The Export Dataflow...............................................................................................................60 The Transform Dataflow.........................................................................................................60 The Load Dataflow.................................................................................................................61 Data Services Objects...........................................................................................................61 Global Variables.....................................................................................................................62 Repository Tables..................................................................................................................63 Customizing a Data Services Job...........................................................................................64 Publishing a Data Services Job to Web Services...................................................................64 Connecting to a Data Services Job........................................................................................65 Modifying the Data Services Job...........................................................................................65 More Information...................................................................................................................67 69
2011-03-11
Contents
2011-03-11
Document History
Document History
Caution: The following table provides an overview on the most important document changes: Version 7.5 Date January 2009 Description First version no changes The documentation contains the following changes: New features: In the Defining the Source Properties for Connection to a Flat File topic, the reference to a Browse button was changed to Upload. In the Duplicating an Existing Job, the new Save as feature is explained. In the new Rules in mapping tables section, new features for rules in mappings are defined. 7.5 Service Package 2 May 2009 Corrections to existing content: In the Example: Linking Source to Target Definitions topic, the mapping table for Account1, Minority Interests/Account, and Partner had the wrong concatenation. In the Creating Mapping Tables topic, a caution was added about selecting dimensions for mapping tables. In the Executing a Profitability and Cost Management Job topic, the step regarding Target Application Options has been removed as it is no longer in the interface. new topic Launching a Job Via an External Scheduler Requirement of upper case in Job Name when the Data Services repository is on an Oracle database
7.5 Support Pack 4 December 2009
2011-03-11
Document History
Version
Date
Description New parameters for execution with the performance and cost management application Exporting and importing financial information management job definitions Column headers in flat files New executor role support for the business planning and consolidation application
7.5 Support Pack 5
January 2010
7.5 Support Pack 6
March 2010
Related Topics Rules in mapping tables Example: Mapping Rule Behavior Duplicating an Existing Job Defining the Source Properties for Connection to a Flat File Linking Source to Target Definitions Creating Mapping Tables Executing a Profitability and Cost Management Job Launching a Job Via an External Scheduler Naming and Defining Core Job Properties
2011-03-11
SAP BusinessObjects Financial Information Management
2.1 About SAP BusinessObjects Financial Information Management

SAP BusinessObjects Financial Information Management is a web-based solution that allows a financial business user to do the following: Maintain complex mappings Launch processes using a single tool Import data into the financial consolidation and profitability and cost management applications The financial information management solution is a tool that combines an easy-to-use interface with the power of SAP BusinessObjects Data Services.
2.1.1 Prerequisites
For information on prerequisites for the financial information management client, refer to the SAP BusinessObjects Financial Information Management 7.5 Master Guide.
2.1.2 Job Workflow

The workflow in creating and executing a job is as follows: The administrator user creates a connection to the source data The business user does the following: Creates a new job. Defines mapping tables. Populates the mapping tables. Executes the job. The auditor views the execution logs.
2011-03-11
2.1.3 User Roles

The most common user roles the financial information management solution are the following: Administrator, who creates and maintains database and application connections. 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 X X X X X X X X X X X X X Business User X X X X X X X X X
Action View list of jobs View job definition Create jobs Modify jobs Delete jobs Create Mapping Table Structure View Mapping Table content Modify Mapping Table content Import Jobs Export Jobs Execute jobs Schedule jobs View job results and audit trail View extended data services logs Drill through
Auditor X X
10
2011-03-11
Action
Administrator Executor
Business User X
Auditor X
View connection to financial performance X management applications Create connection to financial performance management applications Update or delete connections 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. User roles have a fixed setting and cannot be customized. Note: Auditors and administrator users see all jobs. Business users see jobs according to permissions granted to them at the job level. A business user who has been granted rights and access to jobs can delete the jobs.
11
2011-03-11
12
2011-03-11
Creating Connections
3.1 Source and Target Database Connections

Before a business user can create or execute a job, an administrator must create connections to source databases and target applications. Connections are stored in the financial information management repository. The source data in a job is taken from the source database and mapped to the target database. If the source data is in a flat file, you do not need to create a connection. There are several possible target databases for financial information management: SAP BusinessObjects Financial Consolidation 7.5 SAP BusinessObjects Profitability and Cost Management 7.5 SAP Business Planning and Consolidation
3.1.1 Creating a Financial Consolidation Connection

You must be an administrator user to create a connection. 1. Log on to the application as an administrator. 2. Click List of Connections. 3. Click New. 4. Under "Select a Type" select "Financial Consolidation " 5. In the "Connection Name" box, type a unique name that you assign to that connection. 6. In the "Web Service URL" box, type the web service deployed in the financial consolidation application. You must end the web service URL with a slash. 7. Test the connection.
3.1.2 Creating a Profitability and Cost Management Connection

You must be an administrator to create a connection
13
2011-03-11
1. Log on to the application as an administrator. 2. Click List of Connections. 3. Select "Profitability and Cost Management" 4. In the "Connection Name" box, type a unique name that you assign to that connection. enter the web service URL to the profitability and cost management web service that is specific to the financial information management solution. 5. In the "Database Location" box, enter the location of the profitability and cost management location. 6. Enter the "Database Login" and "Password". 7. Test the connection. 8. Select a model type with one of the following extensions: .po .om .hy A list of available models is displayed. 9. Select the "Default Model Name" from the list of models.
3.1.3 Creating a Planning and Consolidation Connection

You must be an administrator user to create a connection. 1. Click Connections > New. 2. In the "Type of Connection" box select "SAP Business Planning and Consolidation." 3. In the "Connection Name" box, type the name you have selected for the connection. 4. In the "Web Service URL" box, type the URL of the web service of the machine where the business planning and consolidation application is installed for example, http://myBPCServer:8080/ Note: the URL must end with a forward slash / 5. In the "AppSet" box, select the AppSet from which you want to take data from the list of available AppSets. You see only the AppSets to which you have rights. 6. Test the connection, then click Save.
3.1.4 Creating an MS SQL Server Database Connection

You must be an administrator user to create a connection. 1. Log on to the application as an administrator. 2. Click List of Connections. 3. Click New. 4. Under "Select a Type" select Database.
14
2011-03-11
5. Enter the properties: "Connection Name": a unique name that you assign to the connection "Connection Type": database "Database Type: SQL Server" " Database Location": Server hosting the MS SQL Server. Can be followed by listener port number separated by a colon for example, SQLSRV:1433 "Database Name": MSSQL Server database name, for example, APAC_DW "Database Login": MS SQL Server login, for example, fim "Database Password": MS SQL Server password 6. Test the connection. 7. Save the connection.
3.1.5 Creating an Oracle Database Connection

1. Log on to the application as an administrator. 2. Click List of Connections. 3. Click New. 4. In the "Connection Type" box select "Database." 5. Enter the properties: "Connection Name": a unique name for the connection, for example, Oracle DB Cart "Connection Type": "Database". "Database Type": "Oracle". " Database Location": the name of the server hosting the Oracle database and server listener port number separated by a colon, for example ORASRV:1521 "Database Name": Oracle System Identifier (SID) or Service name, for example, CART "Database Login": Oracle schema, for example, fim_ref_75 "Database Password": password to connect to the Oracle schema. 6. Test the connection. 7. Save the connection. Note: To connect to an Oracle database with the financial information management application you need to use Oracle aliases that have the same name as the Oracle SID instance addressed in the financial information management/data services server TNSNAMES.ORA file For example # tnsnames.ora Network Configuration File: E:\oracle\product\10.2.0\client_1\network\ad min\tnsnames.ora # Generated by Oracle configuration tools.
15
2011-03-11
CART = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = SRV-ORA10G)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME =CART ) ) ) The following example does not work with the financial information management application : # tnsnames.ora Network Configuration File: E:\oracle\product\10.2.0\client_1\network\ad min\tnsnames.ora # Generated by Oracle configuration tools. APAC_SERVER = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = SRV-ORA10G)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = CART ) ) )
16
2011-03-11
Creating Jobs
Creating Jobs
4.1 About Jobs

A financial information management job allows you to load data from a source to a target. A financial information management job has the following components: Properties, describing the job Source page, on which you specify from where you want to take the source data Target page, on which you specify to which application you want to load the transformed data Mapping table definition page, where you specify the individual transformations that need to take place Mapping tables, which contain the actual transformation values, for example, translate account X to account Y.
When you execute a financial information management job, you automatically create an underlying data services job, which cannot be seen by an administrator or a business user. Note: A data services job can be modified by a person who has access to the data services application and who has the necessary advanced skill set required for customizing data services jobs. Related Topics Creating a Job Customizing a Data Services Job
4.1.1 Creating a Job

You create a job in a series of pages in the application. 1. 2. 3. 4. Name the job and define the core properties. Specify the location of the source data and its properties. Specify the target, the location to which you want to load the data, and its properties. Create and define a mapping table.
17
2011-03-11
Creating Jobs
5. Populate the mapping table with actual transformation values. Related Topics Naming and Defining Core Job Properties About Source Data About Mapping Tables Creating Mapping Tables
4.1.1.1 Naming and Defining Core Job Properties

The first step in creating a job is to define its core properties. 1. In the financial information management application, select List of Jobs then New. 2. On the "Properties" page, in the "Job Nickname" box, enter a name no longer than 8 characters. A job nickname is used for easy reference to the job. Note: The job nickname cannot be modified after the job has been created. The only way to modify the job nickname is to create a new job. If the data services repository is located on an Oracle database you must use upper-case, or capital, letters in the job nickname. The job nickname cannot contain a space; you must use an underscore.
3. In the "Description" box type a description of what the job does, no longer than 255 characters. 4. If you want to connect to an existing data services job, select "Connect with an existing Data Services Job", then select the job from the list, then type the following: "Transaction Table": defined in the data services application. The transaction table contains the mappings to each source row along with the set of target coordinates to which the row was mapped. Configuration of a transaction table is required in order to activate the drill-to-origin function "Validation Error Table ": the table to which mapping-related errors are written. The validation error table provides additional feedback for users when invalid data is caught by the data services job at runtime.
Note: You must be thoroughly familiar with the data services application to connect to a data services job. 5. Under "Available Users", select the users to whom you want to give rights to the job. 6. Click Next. Related Topics About Data Services Job Customization Customizing a Data Services Job
18
2011-03-11
Creating Jobs
4.1.2 Duplicating an Existing Job

When you duplicate an existing job, the following information is included in the new job: the external job setting and data source job name the job description the list of business users source and target properties mapping table definitions and content To duplicate an existing job: 1. In the financial information management application, click List of Jobs. 2. On the List of Jobs page, select the job you want to duplicate. 3. On the job's Properties page, click Save as. 4. Enter a Job nickname. Note: The name of the mapping table cannot contain spaces or non-alphabetic or non-numeric characters. 5. Click OK.
4.1.3 About Source Data

Source data is the data that you want to transform and load into a target application. The source data can come from: The connection that you defined, for example, a database An SAP ERP (Enterprise Resource Planning) application A flat file You define the source data on the "Source Properties" page. Related Topics Defining Source Properties for a Connection to a Data Source Defining the Source Properties for a Connection to an SAP ERP Defining the Source Properties for Connection to a Flat File
19
2011-03-11
Creating Jobs
4.1.3.1 Defining Source Properties for a Connection to a Data Source

1. In the "Source Properties" page, select the "Connection" to the source data from the list. 2. Depending on the type of connection to the source data, select as follows: the "Consolidation" for the financial consolidation application the "Measure" for the profitability and cost management application the "Application" for the business planning and consolidation application 3. Click Next. The Target Properties page, in which you specify the target data for your connection, opens. Note: It is not possible to specify a database view or synonym with this version of the product.
4.1.3.2 Defining the Source Properties for a Connection to an SAP ERP

You can connect to an SAP ERP only if you have installed specific templates. 1. On the "Source Properties" page select "SAP ERP" 2. Select the SAP ERP data source to which you want to connect from the list. Note: This list is empty if you have not installed the templates. For more information on these templates, consult the SAP Developer Network (SDN).
4.1.3.3 Defining the Source Properties for Connection to a Flat File

The number format in flat files must match regional settings of the account that is running data services and must not contain a thousand separator such as a space or a dot, for example: US regional setting: 1000.00 FR regional setting: 1000,00 1. On the "Source Properties" page select "Flat File" 2. Click Upload to browse to a file.
20
2011-03-11
Creating Jobs
Caution: If the file already exists with the same name for the job, an error message appears to ask if you want to overwrite the file on the server. Note: Once you have uploaded the file, the name of the file appears next to the Upload button that allows you to view the first hundred lines of the file. 3. To see the header, select First line contains header. If the first line does not contain a header, column numbers are designated by default as dimension names. Note: Column headers cannot contain spaces. You need to insert an underscore, for example, Transaction Currency to Transaction_Currency. 4. Select the value delimiter: Semicolon Comma Space Tabulation
Restriction: Fixed-width flat files are not supported. 5. Click Next.
4.1.3.3.1 Changing Column Headers in Flat Files

You have defined a mapping table using a flat file. After you have defined a mapping table using a flat file, if you change a column name in the flat file, you must reopen the job and resave the mapping table definition in order to save the changes. The procedure is as follows: 1. 2. 3. 4. 5. Open the job Click "Source Properties" and select the file whose name you changed. Click . Click "Mapping Table Definition" and select the new column name source. Click Save
4.1.4 Defining the Target Properties

After you define the source data, you define the target properties for that connection. 1. On the "Target Properties" page, proceed as follows: If your target is the financial consolidation application, select the name of your target server.
21
2011-03-11
Creating Jobs
If your target is the profitability and cost management application select the name of the connection to the server, then select the "Measure" from the list. Note: Most of the Measures proposed mirror those already defined for use by SAP BusinessObjects Data Bridge. For details, refer to the SAP BusinessObjects Profitability and Cost Management Data Bridge User Guide.
If your target is the business planning and consolidation application, select the "Application" from the list. The applications contained in the AppSet that you selected when you created the connection.
2. Click Next. You proceed to the "Mapping Table Definition" page in which you create a mapping table.
4.2 About Mapping Tables

A mapping table contains the rules to be applied to the source dimensions in order to produce the target dimensions. When you create a job, you must create at least one mapping table in which you specify the individual transformations that need to occur. A mapping table usually consists of source and target dimensions. When defining a mapping table, you can define up to five source columns and five target columns. At mapping time, you can select from a list of values that are retrieved from the associated source column table. Each target column must be associated with a dimension in the target application, for example, Flow or Account. Related Topics Rules in mapping tables Creating Mapping Tables Populating Mapping Tables
4.2.1 Rules in mapping tables

When you populate a mapping table you define a set of rules, and when you run the job, the financial information management application processes the rules either by the using the highest priority rules or all matching rules. You want to match all rules when you want to, for example:
22
2011-03-11
Creating Jobs
Include aggregate amounts For example; you want to leave a calculated amount row for all accounts.
Load more than one amount for a line For example; you want to load both opening and closing balance from each input line.
4.2.2 Creating Mapping Tables

1. On the "Mapping Table Definition" page, click Create Mapping Table. 2. On the tab, type a name for the new mapping table. Each tab on the "Mapping Table Definition" page contains one mapping table in the financial information management repository. The name of the mapping table may not contain spaces or non-alphabetic or non-numeric characters. 3. Under "Source", select the column from the source table or flat file from which you want to load data. 4. Under "Target", select the target to which you want to map data. Depending on the application to which you map data, the target may be a: Financial consolidation dimension Profitability and cost management dimension Business planning and consolidation dimension 5. Click the green "Add" icon to add columns to the mapping table. 6. Select the mapping table behavior you want to apply: Select Highest Priority Matching Rule applies to run only the first matching rule. By default, the priority is set to 10, 20, 30 and so on. Select All Matching Rules apply to have all rules applied. To view the "Priority" column, click the "Show/Hide" button in the upper right corner of the table. 7. Click Finish. You return to the "List of Jobs" page. The new job name and description appear in the appropriate columns. Example: You select the financial consolidation application as the target application. From a source database you select the table column "GL_ACCOUNT" and the target dimensions AC and FL. Caution: You must ensure that all mandatory dimensions for the target application are correctly mapped, otherwise the job fails. Most performance and cost management dimensions are compulsory. In the financial consolidation application the mandatory dimensions are as follows: Reporting Unit
23
2011-03-11
Creating Jobs
Data Entry Period Category
We recommend that you select the source dimension from the list boxes. If you manually modify the selection, your job may no longer work. Manually modifying the source dimensions is advised only when building complex jobs where the underlying data services job accesses a modified source for which the user interface does not provide metadata browsing.
4.2.3 Error Checks in Creating a Mapping Table

Financial information management does not allow you to save a job if you attempt to enter incorrect information. In order to avoid issues for saving a mapping table definition, please note the following items: Do not create two mapping tables that calculate the same target dimensions. Do not use a space or non-alphabetic or non-numeric characters in the source or target dimension names. Do not create a mapping table that does not calculate a target AMOUNT financial consolidation dimension or a profitability and cost management measure value.
Related Topics About Mapping Tables
4.3 Populating Mapping Tables

Once you have created and defined a mapping table, you need to define the transformation rules. Defining the transformation rules is called populating a mapping table. You populate a mapping table in one of the following ways: Manually entering values, patterns and expressions into the cells Selecting from lists of pre-defined values. This option is available if specific columns from a source table were associated with specific columns in the mapping table when it was defined. Copying and pasting values from a Microsoft Excel worksheet Pasting from financial consolidation DataLink definitions.
1. In the financial information management application click List of Jobs. 2. On the "List of Jobs" page, select the job for which you want to populate the mapping table.
24
2011-03-11
Creating Jobs
3. On the "Properties" page, click Mapping Tables and select the mapping table that you want to populate. 4. On the "Mapping Tables" page, select the mapping table that you want to populate. In mapping tables, source cells are white and target cells are grey. 5. In the mapping table, click inside each source cell from which you want to map data and do one of the following: Type a value. Select a value from the list. Type a pattern. 6. Click inside each target cell to which you want to map data and do one of the following: Type the value to which you want to map the source data. Select a value to which you want to map the source data from the list. Type an expression. 7. When you have finished entering the data, click Save. Related Topics Patterns Used in Mapping Table Source Columns Target Column Values
4.3.1 Patterns Used in Mapping Table Source Columns
Pattern
Matches
Example
period .
any single character
6. returns all character strings beginning with 6 and followed by one single character 6# returns all character strings beginning with 6 and followed by a single letter of the alphabet .*
hash or pound any single alphabetic letter sign # asterisk * dollar sign $ (blank) any character zero or more times
any alphabetic character ze- 6$ returns all character strings starting with 6 followed ro or more times by letters of the alphabet any string If the pattern is empty, then it matches all the data.
[no1...no2] any number between no1 and no2 {empty} {EMPTY} empty strings Predefined patterns that match empty data
25
2011-03-11
Creating Jobs
Pattern
Matches
Example
{null} {NULL} plus sign + preceding character one or more times OR - enclose list in {} NOT escape character
Predefined patterns that match NULL data a+ returns the character strings made up of one or more "a"s - ab+1 returns character strings starting with a , followed by b and finishing in 1 {ABC+;XYZ*} - If the data matches either ABC+ or XYZ* then the result is true. <> pattern - The data is considered as matching if the pattern does not match the data. Used in a pattern before a non-alphabetic or non-numeric character to indicate to the engine that the character cannot be used to build the pattern Example: your source data reads # Trips. You need to put a backslash in front of the pound sign '\# Trips' to display # Trips under Target. used to run other options such as "run as separate process"
semi-colon ; <> backslash \
tilde ~
new operator
Note: for users of the profitability and cost management application: certain non-alphabetic and non-numeric characters such as the pound sign, are used as special characters in the financial information management application. To ensure that the data is loaded corrected in the financial information management application, it is necessary to prefix the non-alphabetic or non-numeric character by the backslash, for example \# PCs in the source column to yield'# PCs' in the target column.
4.3.1.1 Example of a Profitability and Cost Management Mapping

The source file contains a combination of values and item names such as Resource Driver Values, which are dimensioned by the following: Version Period Responsability Center Resource Driver name Resource Driver Value Resource Driver Delta Value Resource Driver Target Value
26
2011-03-11
Creating Jobs
The resource driver name contains a character # noted as a special non-alphabetic, non-numeric character by the financial information management application but not by the profitability and cost management application. The following image shows dimensions in row 1 and the first line of data in row 2.
The first line of data shows the following: Version = Actual Period = Q1 Responsibility Center (RC) = Finance Resource Driver Name (RD) = #Trips Resource Driver Value (Rdvalue) = 40 This example shows the two areas of note for profitability and cost management users: the # character and the combination of values and item names. The first row is typical of the remaining rows in the source file. To make sure the data is loaded correctly via the financial information management application, we recommend that you do the following: Use one mapping table per dimension. Prefix the source # Trips with the financial information management escape character, the backslash: \# Trips Use the asterisk * to select all from the source Rdvalue column in the source file. Use the [columnheader] function as shown below, to map the data into the RDValue column in the target table
4.3.2 Target Column Values

All types of expressions recognized by the data services application may be used to display target column values. Some examples of these expressions are as follows: Constants, inside single quotes, such as 'ABC' expression : everything is evaluated as an expression.
27
2011-03-11
Creating Jobs
Input parameters referred to as the source column name, for example, the mapping table has a source column called GL_ACCOUNT. The string [GL_ACCOUNT] would refer to the current value of this input column.
Within the expression operands are used and string functions or numeric functions nested inside string functions. Some examples are as follows: Substring(input_string, start_pos, length) Ltrim_blanks(inputstring) Rtrim_blanks(inputstring) Ltrim(input_string, char_to_trim) Rtrim(inputstring, char_to_trim) Length(inputstring) Index(inputstring, start_pos, char_to_be_found) Lpad(inputstring, char_to_pad, length) Rpad(inputstring, char_to_pad, length) Tip: A full list of available data services functions can be found in the SAP BusinessObjects Data Services documentation Note: You cannot use target dimensions to calculate another target dimension in the financial information management interface. This type of calculation could be performed by a power user by modifying the underlying data services job created by the financial information application.
4.3.3 Populating Mapping Tables from Microsoft Excel

You can populate a mapping table by copying and pasting an individual cell, an entire column or row, or a range of cells from a Microsoft Excel spreadsheet and paste it into the mapping table. 1. In Microsoft Excel select the cell, column, or row and select Edit > Copy. 2. In the mapping table, select the cell in which you want to start pasting data, right-click the cell, and select Paste from the menu. Remember: Make sure that the source and target values from Microsoft Excel are correctly aligned in the financial information management application.
4.3.4 Populating Mapping Tables from Financial Consolidation DataLink Definitions
28
2011-03-11
Creating Jobs
You can populate a mapping table by copying and pasting from a datalink definition stored in a Microsoft Excel spreadsheet for instance. This feature differ from the standard Paste functionality as it replaces double quotes used for defining constant in DataLink by single quotes used by financial information management for defining constants. 1. In Microsoft Excel select the cell, column, or row and select Edit > Copy 2. In the mapping table, select the cell in which you want to start pasting data, right-click, and select Paste From DataLink from the menu. Note: This feature differs from the standard paste functionality because it replaces the double quotes used for defining constants in Datalink by single quotes, used by financial information management for defining constants.
4.3.5 Importing Data into the SAP Business Planning and Consolidation Application
When you import data, that is, when the business planning and consolidation application is your target, there is no loading option. Loading data in the financial information management application is equivalent to using Data Bridge in the business planning and consolidation application. You cannot clear existing data; you replace existing data. You need to use the Clear function in the SAP Business Planning and Consolidation Data Manager. When you export data from the financial consolidation application to the business planning and consolidation application, you load data at the package level and export data at the consolidation level. You export only the consolidated amounts.
4.3.5.1 Amounts
Some amounts need to be mapped with a negative sign. In order to avoid any rounding performred automatically by the financial information management application, the following syntax should be used: to_decimal([Amount],'.','',10)*-1 The number 10 indicates the number of digits after the decimal. For more information, refer to the SAP BusinessObjects Data Services documentation.
29
2011-03-11
Creating Jobs
4.3.6 Importing Comments from the Business Planning and Consolidation Application into the Financial Consolidation Application
Your source is the business planning and consolidation application. You can add comments when importing data from the business planning and consolidation application to the financial consolidation application. You do so when you define the mapping table. 1. On the "Mapping Table Definition" page, create the mapping table defining the source and target data. 2. Under "Target", click the green "Add" icon to add a column in the mapping table, and select "Comment" from the list. 3. Save the mapping table definition. 4. Click Mapping Table, to open the "Mapping Table" page 5. In the "Mapping Table" page, type the comment you want to add in the "Comment" column. 6. When you have finished populating the mapping table, click Execute. The job is executed and the comment is generated with the data. Your comment appears in the financial consolidation application. To view the comment, right-click inside the cell that corresponds to the mapping table and select Comment. The comment appears in the "Information on Data" dialog box.
4.3.7 Mapping Table History

One role of the business user is to maintain mapping tables. Each modification that you make to a mapping table is recorded on the "Mapping Table History " page. You have access to the history, or audit, of the mapping tables to which you have rights. The audit user has access to the Mapping Table History page for all mapping tables. The "Mapping Table History" page displays the following: "Modification Date" and the number of changes on that date "User" who made the modifications The modifications in their respective columns
4.4 Moving Financial Information Management Job Definitions
30
2011-03-11
Creating Jobs
Once you have created a financial information management job you may want to move it to a different environment, for example, from a development environment to a test environment, or from a test environment to a production environment. To move a job definition to a different environment you first export the job, which generates a flat file. You then transfer the flat file to the target environment for import. You move job definitions from the "List of Jobs " page
4.4.1 Exporting a Financial Information Management Job

To export a job: 1. On the" List of Jobs" page, select the job you want to export. 2. Click Export.. 3. In the "Export Jobs" dialog box, select the directory on the client machine. The file name is the job nickname with the .xml extension. You cannot change the extension. 4. Click Export. The following parameters are exported: Job properties Source properties Target properties Mapping table definition Mapping table content Source connection (if any) Target connection The following parameters are not exported: Mapping table audit trail Job run history Source file (if any) Last run parameters (filters and target application properties Underlying data services job
4.4.2 Importing a Financial Information Management Job

To import a job: 1. On the "List of Jobs" page, click Import. 2. In the "Import Objects" dialog box, click Load then select the job you want to import.
31
2011-03-11
Creating Jobs
The screen lists the financial information management job and connection to be imported. 3. Under "Import", select the objects you want to import. If the object already exists, the "Already exist "box is checked. If the object already exists in the financial information management environment and you select Import, the existing object is overwritten by the import. 4. Click Import. The financial information management job or jobs are imported and the underlying data services jobs are regenerated. Note: Use CTRL + Shift to select more than one job to export or import. You can have up to two connections per job. If a flat file as used as the source file, it is not imported. You must copy and paste the flat file to your new environment. Note: When a connection that bears the same name as an existing connection is imported, regardless of the case, the existing connection is updated. Therefore, we highly recommend that, when moving job definitions from one environment to another, you use one connection name and that you consistently use the same case for the connection name. When working with Oracle databases, connection names must be written in upper case.
4.4.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 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
32
2011-03-11
Creating Jobs
4.5 Job Run History

The "Job Run History" page provides important details on the execution of a job. When you click "View Job Run Details" you view the following: "Job Name" "Start Time" "End Time" "Status": succeeded or error "User Name" Note: "Succeeded" status means that the call to the web services was successful. It does not mean that all the input data rows were successfully imported into the target application . When you click "View Job Run Details", the "Job Run Details" page displays tabs for the following: "Job Run Status Feedback Table": displays the results of the web service call to the target application (for importing data). If there is an error when the job is run, an error message is returned. When the job is run successfully, the detail of the rows rejected by the target application is displayed in the table, for example, "Code XXXX not defined in ACCOUNT dimension" for the financial consolidation application "Responsibility Center name does not exist "for the profitability and cost management application.
When you load data into the financial consolidation application, one line is returned per package. "Validation Error Table": gives a list of mapping errors: the rows where no mapping rule could be applied "Error Log": shows the data services error log, which is of interest to technical users. "Trace log": shows the data services trace log, which is of interest to technical users. "Monitor Log": shows the data services monitor log, which is of interest to technical users.
33
2011-03-11
Creating Jobs
34
2011-03-11
Executing Jobs
Executing Jobs
5.1 Executing a Financial Consolidation Job

When you have finished populating the mapping tables, you are ready to execute the financial information management job. 1. From the "List of Jobs", select the job you want to execute and click Open. 2. On the "Properties" page click Execute. The "Runtime Parameters" dialog box opens. This page displays the filtering and target application options. 3. Under "Filtering Options", click inside the cell below "Dimension or Parameter" and select the filter you want to use on your source data from the list. 4. Under "Value" click Browse to locate the value or values that you want to enter, or directly type the value or values, separating values with commas. 5. Under "Target Application Options", select the possible parameters to use. The options are as follows: Delete before execution: if checked, all existing data in the financial consolidation application relating to the Reporting ID is deleted before importing new data. Aggregate Amounts: if checked, new data loaded by the job is added to existing data, subject to the same dimensionality. Replace Amounts: if checked, the matched existing data is replaced by the imported data. Data that does not correspond to the imported data in the same package remains unchanged. Do not create operation objects: if unchecked, this parameter triggers the creation of undefined packages on the fly. Run Package Rules: if checked, this parameter triggers the package's rules after import completion. Package rules automatically create journal entries. Run Controls: if checked, this parameter triggers the controls of the package after import completion. Controls are a set of data checks that are predefined by the reporting administrator. Results of the running of financial consolidation controls are visible only under the financial consolidation application. Publish Package: if checked, this parameter triggers the package's publishing process after import completion. You certify that the content of the package is valid, and make it available for the publication site. Integrate: if checked, this parameter triggers the integration process of the package after import completion. 6. Click Run Now.
35
2011-03-11
Executing Jobs
The financial information management application executes the job and posts the results on the "Job Run History" page.
5.2 About Profitability and Cost Management Job Execution

Profitability and cost management jobs are executed by a profitability and cost management model builder or a financial information management administrator. The financial information management application uses the profitability and cost management data loader utility to load data into the application. Therefore, the following restrictions of the profitability and cost management application apply: When loading data, you must either ensure that no users are logged into the profitability and cost management application and that no models are open. Failure to do so causes a conflict between the application server cache and the data held in the database, and therefore, could result in data corruption. The Data Loader utility bypasses the profitability and cost management application and, therefore, the application server has no indication that data is being inserted into the database. For more information on the profitability and cost management data loader see the SAP BusinessObjects Profitability and Cost Management Database Guide for Microsoft SQL Server or the SAP BusinessObjects Profitability and Cost Management Database Guide for Oracle. Related Topics Executing a Profitability and Cost Management Job
5.2.1 Executing a Profitability and Cost Management Job

1. From the "List of Jobs", select the job you want to execute and click Open. 2. On the "Properties" page click Execute. The "Runtime Parameters" dialog box opens. This page displays the filtering options. 3. Under "Filtering Options", click inside the cell below "Dimension or Parameter" and select the filter you want to use on your source data from the list. 4. Under "Target Application Options SAP BusinessObjects Profitability and Cost Management" select: Target Model One of the following: No deletion before execution; replace existing data .(default value) No deletion before execution; aggregate. Delete matching version/period before execution. Delete all before execution.
36
2011-03-11
Executing Jobs
5. Under "Value" click Browse to locate the value or values that you want to enter, or directly type the value or values, separating values with commas. 6. Click Run Now.
5.2.2 Selecting a Profitability and Cost Management Model at Runtime

The profitability and cost management internal model ID and model name are passed to the drill-to-origin URL. The financial information management application filters results based on the internal model ID or the model name The internal model ID is stored in the job transaction table; the model name is stored in the financial information management connection table.
5.3 Exporting Data from the Business Planning and Consolidation Application
The financial information management application lets your import and export data to and from the following applications: SAP BusinessObjects Financial Consolidation SAP BusinessObjects Profitability and Cost Management SAP Business Planning and Consolidation When exporting from the business planning and consolidation application, only base member values are exported. Note: Hierarchies, aggregations, and dimension member formulas are not exported When you browse to define a mapping table or to set filter options when you execute a job, only base member values are available. You can export date values as follows: Periodic Year-to-date Quarter-to-date Custom measures To select the value you want to use, you set a filter on the "Measures" dimension in the Job Execution dialog box. Note: If you do not set a filter on the "Measures" dimension, the default value, "Periodic", is used.
37
2011-03-11
Executing Jobs
5.3.1 Importing Data into the SAP Business Planning and Consolidation Application
When you import data, that is, when the business planning and consolidation application is your target, there is no loading option. Loading data in the financial information management application is equivalent to using Data Bridge in the business planning and consolidation application. You cannot clear existing data; you replace existing data. You need to use the Clear function in the SAP Business Planning and Consolidation Data Manager. When you export data from the financial consolidation application to the business planning and consolidation application, you load data at the package level and export data at the consolidation level. You export only the consolidated amounts.
5.4 Launching a Job Via an External Scheduler

You can launch a financial information management job via an external scheduling tool such as Windows task scheduler. The financial information management application generates a scheduling file that contains a command line to launch Internet Explorer on a given URL, which gives information on the selected job, the execution parameters and user credentials. 1. From the "List of Jobs", select the job you want to execute and click Open. 2. On the "Properties" page click Execute. The "Runtime Parameters" dialog box opens. 3. Enter the filter parameters for your job. 4. In the lower part of the page click Save As Scheduling File... 5. If you: have been automatically logged in to the financial information management application via Single Sign On (SSO), a dialog box opens in which you must first re-enter your password and indicate the authentication mode have entered credentials to log in to the financial information management application, you go directly to the next step. 6. Enter the path to the location in which you want to save the generated script file, or browse to its location, then click OK. The financial information management application generates the script and stores it in the location that you indicated. When the job is launched, the result is sent to a log file.
38
2011-03-11
Executing Jobs
Note: The length of the generated URL may not be longer than 2000 characters. Setting a large number of complex filters on a job may generate a URL longer than 2000 characters, in which case job execution fails and a warning message is displayed.
39
2011-03-11
Executing Jobs
40
2011-03-11
About the Drill-to-Origin Feature
The drill-to-origin feature allows you to view the origin of data from the target application. It must be configured in the financial consolidation and/or profitability and cost management application by an administrator prior to the installation of the financial information management application. Refer to the SAP BusinessObjects Financial Information Management Installation Guide for details on enabling the drill-to-origin feature. Note: Administrators need to remember the following: The user account must be defined on the CMS. The user account must be associated with one of the three security groups in the CMS for the financial information management application. External authentication with BOE must be enabled in the CtAdmin in the financial consolidation application. The account must be declared in the financial consolidation application with external authentication.
6.1 Displaying the Origin of Data in Financial Consolidation

In the financial consolidation application, open your report or schedule. 1. Select the cell for which you want to view the origin of data, right-click, and select Drill-to-Origin from the menu. The "Drill-to-Origin" dialog box opens. Values are displayed for each of the finance dimensions. 2. Verify that these values are correct, then click Continue. The Drill-to-Origin page displays information from the transaction table, including: job_run_ID Row number, which corresponds to the row number in the transaction table Amount other target and source values
Example: CURRENCY=EUR
41
2011-03-11
ROW NUMjob_run_ID BER ENTITY
PERIOD
ACCOUNT
INTERCO
PA
P_AMOUNT
628203207 82 628203207 83 628203207 84
ITA1 ITA1 ITA1
06-12 06-12 06-12
R100I R100I R100I
USA1 CAN1
R0010 R0120
15000.00 5000.00 20000.00
Note: You can export the content of the table as a .csv, .xls or .xml file by clicking on the appropriate button in the "Export Options "below the table. When you export to Excel the results of more that one financial information job are displayed.
6.2 Displaying the Origin of Data in Profitability and Cost Management

You use the drill-to-origin function to look at the source of any one value. The function returns two source lines that have been loaded for a value. The function returns two source lines that have been loaded for a particular data point. 1. In the profitability and cost management application click inside the cell for which you want to view the origin of data. 2. Right-click and select Drill-to-Origin from the menu. The financial information management application opens and displays a table containing the origin of the data. Note: You can export the contents of the table as a .csv, .xls, or.xml file by clicking the appropriate button in the Export Options below the table. When you export to Excel, the results of more than one financial information management job are displayed.
6.2.1 Example of the Drill-to-Origin Feature

The following example illustrates how the display-origin feature works. The following transaction tables have been populated for Job1 and Job2. Job1 Transaction Table:
42
2011-03-11
CostCentre
Geography
AC
RU
FL
Amount
Office Office Travel
NA CA NA CA EU FR Job2 Transaction Table
Rent Rent Travel
Canada USA France
F22 F22 F22
58588.00 194500.00 96800.00
ExpenseType Geography
Year
AC
RU
FL
Amount
Overhead Overhead Overhead
USA INTL CA INTL FR
2007 2007 2007
Rent Rent Rent
USA Canada France
F22 F22 F22
286300.00 36000.00 127000.00
A call back to the financial information management application http://myserver:8080/fim/drill ToOrigin/drillToOrigin.jsp?AC=Rent&RU=Canada&FL=F22 results in the following being displayed on the "Drill-to-Origin "page: The requested cell {AC=Rent,RU=Canada,FL=22} was traced to the following cells: Job1
CostCentre Geography Amount
Office Job2
ExpenseType
NA CA
58588.00
Geography
Year
Amount
Overhead
INTL CA
2007
36000.00
In the case of partial coordinates, a longer response resembles this: The requested cell {AC=Rent, FL=22} was traced to the following cells: Job1
CostCentre Geography Amount
Office Office Job2
NA CA NA USA
58588.00 194500.00
43
2011-03-11
ExpenseType
Geography
Year
Amount
Overhead Overhead Overhead
USA INTL CA INTL FR
2007 2007 2007
286300.00 36000.00 127000.00
6.2.2 Drill-to-origin: Open in Excel

When defining financial information management drill-to-origin in the profitability and cost management application through the profitability and cost management configuration tool, you can use the drill ToOriginExcel.jsp file instead of the the drillToOrigin.jsp to allow the Drill-to-Origin results open directly in Excel. All available source and target columns from all jobs are displayed.
44
2011-03-11
Sharing Transaction Tables Among Several Jobs
Each financial information management job has its own transaction table that is used to display results from drill-to-origin results. This table may be completely or partially cleaned-up at job runtime depending on the target application loading options. To ensure that the correct data is used in the case of multiple financial information management jobs loading the same: profitability and cost management measure financial consolidation datasource it is possible to share the transaction table among several jobs. On the"Job Properties" page, you can select "Connect with an existing data services job", and then select the name of the job from the list. In this case, both the transaction table and the validation error table become up-datable. You can also select "Transaction Table" which allows the transaction table to be updated. When you execute a job the job nickname is added to the transaction table in order to differentiate the drill-to-origin results when a transaction table is shared by more than one job.
45
2011-03-11
46
2011-03-11
Example: Defining and Populating a Mapping Table
8.1 Defining a Mapping Table - Source Data

In this example data is taken from a flat file. The first line contains headers, and the columns are separated by a semicolon. The source columns are: Company Account1 Minority_Interests Debit Credit Data in a Flat File Company;Account1;Minority_Interests;Debit;Credit SOC1;601100;PART1;10000; SOC1;601200;PART2;15000; SOC1;701100;PART1;;50000 SOC1;710000;;;20000 SOC1;411100;PART3;2000;
Below is the same data in table format:

Company Account1 Minority Interests Debit Credit
SOC1 SOC1 SOC1 SOC1 SOC1
601100 601200 701100 710000 411100
PART1 PART2 PART1
10000 15000 50000 20000
PART3
2000
47
2011-03-11
8.2 Linking Source to Target Definitions

In a rule, the source dimension values are selected in order to generate the value of the target dimension, and the option Highest Priority Matching Rule applies mapping rule is used for this example.
Table 8-3: Mapping Table1: Company/Reporting Unit

In this example, everything under Company is transferred to Reporting Unit.
Source dimension Target dimension
"Company "
"Reporting unit " [Company]
Table 8-4: Mapping Table 2: Account1, Minority Interests/Account, Partner

For all accounts that begin with a 6 or a 7, the Account target dimension will be filled in with an R followed by the account number. The Minority Interests column is reclassified: PART1 becomes P1, PART2 becomes P2 and the "empty" cell remains so.
Source Dimension Source Dimension Target Dimensions Target Dimensions
Account1 [6..7]* [6..7]* [6..7]*
Minority_Interests 'PART1' 'PART2' {empty}
Account 'R'||[Account1] 'R'||[Account1] 'R'||[Account1]
Partner 'P1' 'P1'
Table 8-5: Mapping Table 3: Account1, Debit, Credit/Amount

For expense accounts, the Amount target dimension will be filled in with the opposite of the Debit source column. For client accounts, the Debit source dimension is transferred to the Amount target dimension and remains unchanged. Similarly, for product accounts, the Credit source dimension is transferred to the Amount target dimension and remains unchanged.
Source Dimension Source Dimension Source Dimension Target Dimension
Account1 6* 41* 7*
Debit
Credit
Amount [Debit]*-1 [Debit] [Credit]
48
2011-03-11
Explanation:[Debit]*-1 means that you need to multiply the debit amount by -1 to return a negative value
8.3 Results
The data produced as a result of the job is as follows:
Reporting unit Account Partner Amount
SOC1 SOC1 SOC1 SOC1
R601100 R601200 R701100 R710000
P1 P2 P1
-10000 -15000 50000 20000
The production report shows that the row corresponding to account 411100 has not been processed since no rule was defined for it in Mapping Table 2: Account1, Minority Interests/Account, Partner.
49
2011-03-11
50
2011-03-11
Example: Mapping Rule Behavior
A mapping table uses one or more rules to generate the value of the target dimension. The data in the example is taken from a database table. The source columns are: Company code Posting period Fiscal year Currency Account number Trading partner Opening balance Total debit Total credit Ending balance Your mapping rules for each mapping table are set to either Highest Priority Matching Rule applies or All Matching Rules apply. Note: For option Highest Priority Matching Rule applies, when no priority column is added in the mapping the first mapping has the priority. The source sample data is: Compa ny _Code 5 5 5 Post ing _Peri od 4 4 4 Fis cal _year 2008 2008 2008 Ac count _Num ber 144000 144000 145000 Trad ing _Part ner 1000 1100 6 Open ing _Bal ance 0 0 4651.16 Total _Deb it 520000 45000 0 Total _cred it 0 0 0 End ing _Bal ance 520000 45000 4651.16
Cur rency EUR EUR EUR
Table 9-2: Mapping Table: Company Code/Reporting Unit

When the Highest Priority Matching Rule applies rule is used to match the source data in the Com pany_Code column to the target RU (Reporting Unit) column, company code 5 is mapped to IEFO002T- and company code 6 is mapped to RTDF001-Y-.
51
2011-03-11
Company_Code 5 6
RU 'IEFO002-T-' 'RTDF001-Y-'
Table 9-3: Mapping Table: Currency

The currency is left as is. Currency * CU [Currency]
Table 9-4: Mapping Table: Posting Period & Fiscal Year/Data Entry Period (DP) & Period (PE)
When the Highest Priority Matching Rule applies rule is used to match the source data in the Posting_Period and Fiscal_Year columns to the target DP and PE columns, the posting period 1 and the fiscal year 2008 are mapped to 2008.01 in the target DP and PE columns. Posting_Period 1 2 3 4 Fiscal_year 2008 2008 2008 2008 DP '2008.01' '2008.02' '2008.03' '2008.04' PE '2008.01' '2008.02' '2008.03' '2008.04'
Table 9-5: Mapping Table: Account Number/Account (AC)

When the Highest Priority Matching Rule applies is used to match the source data in the Ac count_Number column to the target AC column, account 144000 is mapped to A2460 in the target AC column: Account_Number 144000 145000 AC 'A2460' 'E1110'
Table 9-6: Mapping Table: Trading Partner/Partner (PA)

The All Matching rules apply rule is used to match the source data in the Trading_Partner column to the target PA column. The last line in the rule (*) generates for each row an additional row that will roll-up to calculate the aggregated value:
52
2011-03-11
Trading_Partner 1000 1100 6 *
PA 'FRDR005-T' 'NLFO001-T' 'USDR001-T'
Table 9-7: Mapping Table: Opening Balance & Ending Balance/Flow (FL) & Amount
The All Matching Rules apply rule instructs the target file to take the opening and ending balances for specific accounts and aggregate these balances per fiscal year: Account _Number 144000 144000 145000 145000 Opening _Balance * * * * Ending _Bal ance * * * * FL 'F00' 'F99' 'F00' 'F99' AMOUNT [Opening_Balance] [Ending_Balance] [Opening_Balance]*-1 [Ending_Balance]*-1
The flow (FL) enables you to differentiate between amounts at opening and closing during the data entry period. Example results The data produced as a result of the job is as follows: RU IEFO002TIEFO002TIEFO002TIEFO002TIEFO002TDP 2008.04 2008.04 2008.04 2008.04 2008.04 PE 2008.04 2008.04 2008.04 2008.04 2008.04 CU EUR EUR EUR EUR EUR AC A2460 PA FRDR005-T FL F00 AMOUNT 0 0 -4651,16 520000 45000
A2460
NLFO001-T
F00
E1110
USDR001-T
F00
A2460
FRDR005-T
F99
A2460
NLFO001-T
F99
53
2011-03-11
RU IEFO002TIEFO002TIEFO002TIEFO002TIEFO002T-
DP 2008.04 2008.04 2008.04 2008.04 2008.04
PE 2008.04 2008.04 2008.04 2008.04 2008.04
CU EUR EUR EUR EUR EUR
AC E1110
PA USDR001-T
FL F99
AMOUNT -4651,16 0 -4651,16 565000 -4651,16
A2460
F00
E1110
F00
A2460
F99
E1110
F99
54
2011-03-11
Use Cases
Use Cases
10.1 Use Case 1

This use case Transform amounts of a debit account into negative amount while importing to a specific account of the target system. Debit account starts with 1 and matches to account 10 in the target system . Source file columns are Account, ., Amount. Target system dimensions are ACCOUNT, AMOUNT Rule 1a: If an account starts with 1 then the target account is 10. Rule 1b: Default rule: Target account equals source account
Table 10-1: Mapping table for transformation of account

Account ACCOUNT
* 1*
[Account] '10'
Table 10-2: Mapping table for transformation of amount

Rule 2a: If an account starts with 1 then target amount is "source amount" * -1 Rule 2b: Default rule - Target amount equals source amount
Account Amount AMOUNT
1* *
* *
[Amount] * -1 [Amount]
Table 10-3: Example

Account Amount ACCOUNT AMOUNT
123
1000
>> because of rules 1a and 2a
10
-1000
55
2011-03-11
Use Cases
Account
Amount
ACCOUNT
AMOUNT
2000
>> because of rules 1b and 2b
2000
10.2 Use Case 2

Import data detailed by partner and import also total (Aggregation of partners) into source system The source file columns are Partner, Dim1. The target system dimensions are PARTNER, DIM1. Create 2 jobs: DETAIL to imported data detailed by partner and TOTAL to import total line - TOTAL will not have a mapping for transformation of partner. This allows lines to be aggregated ignoring partner dimension
Table 10-4: DETAIL will have a mapping for transformation of partner

Partner PARTNER
.*
[Partner] Rule 1
Note: .* prevents matching empty partners. These lines are imported by job TOTAL.
Table 10-5: Job DETAIL transforms data

Dim1 Partner Amount DIM1 PARTNER AMOUNT
Val1 Val2 Val2 Val3
1 1 1
1000 2000 3000 4000
>> >> >> >>
Val1 Val1 Val2
1 2 1
1000 2000 3000 Line is not processed because of Rule 1
56
2011-03-11
Use Cases
Table 10-6: Job TOTAL transforms data l

Dim1 Partner Amount DIM1 AMOUNT
Val1 Val1 Val2 Val3
1 2 1
1000 2000 3000 4000
>> >> >> >>
Val1
3000
Partner is ignored. Lines are aggregated
Val2 Val3
3000 4000
Table 10-7: Warning: if source mix total and detailed line , result can be inconsistent
Dim1 Partner Amount DIM1 AMOUNT
Val2 Val3 Val3
3000 4000
Val2 Val3
3000 9000 - Unexpected amount value
5000
57
2011-03-11
Use Cases
58
2011-03-11
Custom Jobs
Custom Jobs
11.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
11.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
59
2011-03-11
Custom Jobs
Note: The job that was created has the same name as the job nickname 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.
11.1.2 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.
11.1.3 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.
60
2011-03-11
Custom Jobs
11.1.4 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 in the "Job Run Details" page of the financial information management application.
11.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
61
2011-03-11
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
11.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 11-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.
62
2011-03-11
Custom Jobs
11.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%
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.
63
2011-03-11
Custom Jobs
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
11.5 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.
11.5.1 Publishing a Data Services Job to Web Services

1. From the Start menu click BusinessObjects XI 3.1 > 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".
64
2011-03-11
Custom Jobs
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.
11.5.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, click List of jobs and, on the "List of Jobs" page, open the job that you want to modify. 2. On the Properties page, select "Connect with an existing 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.
11.5.3 Modifying the Data Services Job

After you have connected to the data services job from the financial information management application, you return 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. Note: Once you have modified and saved the job, you return to the financial information management application to execute the job.
65
2011-03-11
Custom Jobs
Related Topics Executing a Financial Consolidation Job Executing a Profitability and Cost Management Job
66
2011-03-11
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
67
2011-03-11
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.
68
2011-03-11
Index
A
administrator 10 amounts 29 audit user 10 export dataflow 60
F
flat file 20, 21
P
profitability and cost management 36, 42
B
backslash 25 BPC 30 business user 10
H
history 30, 33
R
rejected rows 61 repository 63 rules matching 22
J
job 17 job execution 35, 36 job run history 33 jobs 17 jobs, importing 31
C
column headers 21 comments, importing 30 connections 13, 14, 31
S
SAP ERP 20 source columns 25 source data 19, 47 source properties 20 syntax 25
D
Data Services 59 database 20 dataflows 59 datalink 28 datastore 61 display origin 42 drill-to-origin 9, 41, 42
L
load dataflow 61
T M
mapping table 47 mapping table history 30 mapping tables 22, 23, 28 rules 22 target columns 27 target definitions 48 target properties 21 transaction table 9, 18, 45
E
error checks 24 errors 24 escape character 25 Excel 28 executing jobs 36 executor 10
V O
objects 61 Oracle 15 origin of data 9, 41, 42 validation error table 18, 33 variables 62
W
web services 64
69
2011-03-11
Index
70
2011-03-11

FPM75 FI UserGuide en

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

FPM75 FI UserGuide en

Încărcat de

Drepturi de autor:

Formate disponibile

SAP BusinessObjects Financial Information Management User Guide SAP BusinessObjects Financial Information Management 7.

2.1 2.1.1 2.1.2 2.1.3

3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5

4.3.6 4.3.7 4.4 4.4.1 4.4.2 4.4.3 4.5

5.1 5.2 5.2.1 5.2.2 5.3 5.3.1 5.4

6.1 6.2 6.2.1 6.2.2

8.1 8.2 8.3

7.5 Support Pack 4 December 2009

7.5 Support Pack 5

7.5 Support Pack 6

SAP BusinessObjects Financial Information Management

SAP BusinessObjects Financial Information Management

2.1 About SAP BusinessObjects Financial Information Management

2.1.2 Job Workflow

SAP BusinessObjects Financial Information Management

2.1.3 User Roles

SAP BusinessObjects Financial Information Management

SAP BusinessObjects Financial Information Management

3.1 Source and Target Database Connections

3.1.1 Creating a Financial Consolidation Connection

3.1.2 Creating a Profitability and Cost Management Connection

3.1.3 Creating a Planning and Consolidation Connection

3.1.4 Creating an MS SQL Server Database Connection

3.1.5 Creating an Oracle Database Connection

4.1 About Jobs

4.1.1 Creating a Job

4.1.1.1 Naming and Defining Core Job Properties

4.1.2 Duplicating an Existing Job

4.1.3 About Source Data

4.1.3.1 Defining Source Properties for a Connection to a Data Source

4.1.3.2 Defining the Source Properties for a Connection to an SAP ERP

4.1.3.3 Defining the Source Properties for Connection to a Flat File

Restriction: Fixed-width flat files are not supported. 5. Click Next.

4.1.3.3.1 Changing Column Headers in Flat Files

4.1.4 Defining the Target Properties

4.2 About Mapping Tables

4.2.1 Rules in mapping tables

4.2.2 Creating Mapping Tables

Data Entry Period Category

4.2.3 Error Checks in Creating a Mapping Table

Related Topics About Mapping Tables

4.3 Populating Mapping Tables

4.3.1 Patterns Used in Mapping Table Source Columns

any single character

semi-colon ; <> backslash \

4.3.1.1 Example of a Profitability and Cost Management Mapping

4.3.2 Target Column Values

4.3.3 Populating Mapping Tables from Microsoft Excel

4.3.4 Populating Mapping Tables from Financial Consolidation DataLink Definitions

4.3.7 Mapping Table History

4.4 Moving Financial Information Management Job Definitions

4.4.1 Exporting a Financial Information Management Job

4.4.2 Importing a Financial Information Management Job

4.4.3 Importing a Custom Job

4.5 Job Run History

5.1 Executing a Financial Consolidation Job

5.2 About Profitability and Cost Management Job Execution

5.2.1 Executing a Profitability and Cost Management Job

5.2.2 Selecting a Profitability and Cost Management Model at Runtime

5.4 Launching a Job Via an External Scheduler

About the Drill-to-Origin Feature

About the Drill-to-Origin Feature