Professional Documents
Culture Documents
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
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
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
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
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
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
January 2010
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
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.
2011-03-11
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
Creating Connections
13
2011-03-11
Creating Connections
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.
14
2011-03-11
Creating Connections
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.
15
2011-03-11
Creating Connections
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
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
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
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
19
2011-03-11
Creating Jobs
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
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.
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.
23
2011-03-11
Creating Jobs
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.
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
Pattern
Matches
Example
period .
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"
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.
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
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.
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.
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
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.
32
2011-03-11
Creating Jobs
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
35
2011-03-11
Executing Jobs
The financial information management application executes the job and posts the results on the "Job Run History" page.
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.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.
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
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.
Example: CURRENCY=EUR
41
2011-03-11
PERIOD
ACCOUNT
INTERCO
PA
P_AMOUNT
USA1 CAN1
R0010 R0120
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.
42
2011-03-11
CostCentre
Geography
AC
RU
FL
Amount
ExpenseType Geography
Year
AC
RU
FL
Amount
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
NA CA NA USA
58588.00 194500.00
43
2011-03-11
ExpenseType
Geography
Year
Amount
44
2011-03-11
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
PART3
2000
47
2011-03-11
"Company "
Account1 6* 41* 7*
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
P1 P2 P1
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
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
51
2011-03-11
Company_Code 5 6
RU 'IEFO002-T-' 'RTDF001-Y-'
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'
52
2011-03-11
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-
AC E1110
PA USDR001-T
FL F99
A2460
F00
E1110
F00
A2460
F99
E1110
F99
54
2011-03-11
Use Cases
Use Cases
* 1*
[Account] '10'
1* *
* *
[Amount] * -1 [Amount]
123
1000
10
-1000
55
2011-03-11
Use Cases
Account
Amount
ACCOUNT
AMOUNT
2000
2000
.*
[Partner] Rule 1
Note: .* prevents matching empty partners. These lines are imported by job TOTAL.
1 1 1
1 2 1
56
2011-03-11
Use Cases
1 2 1
Val1
3000
Val2 Val3
3000 4000
Table 10-7: Warning: if source mix total and detailed line , result can be inconsistent
Dim1 Partner Amount DIM1 AMOUNT
3000 4000
Val2 Val3
5000
57
2011-03-11
Use Cases
58
2011-03-11
Custom Jobs
Custom Jobs
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.
60
2011-03-11
Custom Jobs
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
61
2011-03-11
Custom Jobs
Description
Table Export DS DataStore Name FC Load Web Service DS DataStore Name PCM Load Web Service DS DataStore Name PCM Repository DS DataStore Name
Financial Information Management Job Run ID BOE SSO logon token BOE user name BOE user password Filters on Source Dimensions Target Application Options
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
Source Table Name Transaction Table Name Source Column in Transaction Table Mapping Tables Mapping Errors Table
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
FIM_REJECTED_ROW FIM_JOB_RUN_PACKAGE_STATUS
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.
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
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
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/
67
2011-03-11
More Information
Information Resource
Location
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