IM106

download IM106

of 120

  • date post

    30-Aug-2014
  • Category

    Documents

  • view

    63
  • download

    2

Embed Size (px)

Transcript of IM106

IM106SAP Business Planning and Consolidation Data Manager: Now and the Future

Prakash Darji, SAP Business Objects

What Well Cover

1. Overview of Data Manager 2. Run-timeData Manager Packages Running & Scheduling Packages

3. Design-timeTransformation Files Conversion Files UI Script Security Large Files Delivered Objects

4. Future 5. Wrap-up

SAP 2008 / SAP TechEd 08 / IM106 Page 3

BPC Versions

Previously

BPC 5.x

MS Version SAP NetWeaverMigration Utility

Today

BPC 7

BPC 7 M

Future

BPC 7.5

BPC 7.5 MMicrosoft based SAP NW based

SAP 2008 / SAP TechEd 08 / IM106 Page 4

Data ManagerData Manager is an SAP Business Planning and Consolidation (BPC) module that helps you manage loading, transforming, and manipulating data The focus of this session is to discuss Data Manager capabilities in general, however, when examples are given, the details will be described for the NetWeaver version of the product As opposed to using typical ETL tools such as Microsoft SQL Server Integration Services (SSIS), or NetWeaver BI ETL (Process Chains, InfoPackages, DTPs, etc), the Data Manager provides basic ETL operations to an business user (end-user). This means that loading a flat file isnt an Administrator or IT function. The premise is such that the data is owned by the business. The BPC User has no idea that this underlying technology is being used when they are using the Data Manager Data Manager includes a delivered with a set of packages to import, copy, clear and move data within and across applications Data means transactional data as well as master data (no meta data) In addition, Data Manager supports mapping and complex transformations of transactional data files as well as master data files*

* Master Data loading is only supported in the NetWeaver version SAP 2008 / SAP TechEd 08 / IM106 Page 5

Data ManagerWithin the two platforms, there are two different underlying base technologies employedBPC 7.0 (M), uses SQL Server Integration Services (SSIS) as the base technology BPC 7.0 (NW), uses the SAP NetWeaver BI Process Chain Framework as the base technology

SAP 2008 / SAP TechEd 08 / IM106 Page 6

Data Manager Terminology

Object: Data Manager Package Task / Process Type

Acronym DM

Description The module to transform and load and manipulate data The operational unit that user can execute for a data process, like import, export, etc. The module to deal with specific functionality. E.g. load helps to transfer data from file to cube, from cube to cube, from cube to file. Package is built on Process Chains which include task(s).

Process Chain

PC

PC is a framework, which is provided by BW, that helps to schedule packages, maintain status of running packages, wrap tasks into packages and so on. PC is the foundation of a package. An SSIS package is roughly equivalent to a NW BI Process Chain. The Multi Dimensional Data Cube in BW. (ROLAP) Data Transfer Service or SQL Server Integration Services, provided by Microsoft. These are no longer relevant for BPC 7.0. Is a BI InfoObject that contains dimension members (Master Data) Is a BI Object that stores the value (Key Figure) This is an Excel Workbook that defines mappings for data transformations This is an Excel Workbook that defines conversions within data transformations.

InfoCube DTS (SQL 2000) SSIS (SQL 2005) Dimension Measure Transformation File Conversion File

DTS or SSIS

SAP 2008 / SAP TechEd 08 / IM106 Page 7

Accessing the Data Manager

From the Launch Page, click SAP Business Planning and Consolidation for Excel. From the Action Pane, click Manage Data.

SAP 2008 / SAP TechEd 08 / IM106 Page 8

What Well Cover

1. Overview of Data Manager 2. Run-timeData Manager Packages Running & Scheduling Packages

3. Design-timeTransformation Files Conversion Files UI Script Security Large Files Delivered Objects

4. Future 5. Wrap-up

SAP 2008 / SAP TechEd 08 / IM106 Page 9

What Well Cover

1. Overview of Data Manager 2. Run-timeData Manager Packages Running & Scheduling Packages

3. Design-timeTransformation Files Conversion Files UI Script Security Large Files Delivered Objects

4. Future 5. Wrap-up

SAP 2008 / SAP TechEd 08 / IM106 Page 10

Data Manager Packages

Data Manager packages are implemented allow you to do common data manipulation activities The packages that come with BPC 7.0 are designed to be dynamic so that you do not need to modify the packages in order for them to work with your applications and dimensions. You might want to modify packages to behave differently or to perform additional tasks. You can make modifications to the packages supplied with BPC (not best practice) or use those packages as templates to build packages as per your requirements

SAP 2008 / SAP TechEd 08 / IM106 Page 11

Uploading Data into BPC File ServiceA typical activity a user would do would be to load a flat file into a BPC application (cube) To do so, the user would first upload data to the BPC File Service as described below Choose Manage Data -> Upload Data File Enter your source and destination file

Within the BPC 7.0NW product, files are stored within the NetWeaver database, whereas within the BPC 7.0M product, files are stored on the .NET File Server (file system) NOTE: The following web admin parameters affect the behavior of file uploadALLOWEXTENSIONS: Defines allowed file extensions for upload ALLOW_FILE_SIZE: This is the maximum file size a user is allowed to upload. The default value is 100 MB. DEFAULT_EXTENSIONS: This is the list of default extensions that are allowed. This list includes: XLS,XLT,DOC,DOT,PPT,POT,XML,MHT,MHTML,HTM,HTML,XLSX,XLSM,XLSB,ZIP,PDF,PPTX,PPT M,POTX,POTM,DOCX,DOCM,DOTX,DOTM,CDM,TDM,PNG,GIF,JPG,CSS,MRC SAP 2008 / SAP TechEd 08 / IM106 Page 12

Download Data from BPC File ServiceIn some cases, a user may want to download a file from the BPC File Service To do so: Choose Manage Data -> Download Data File Enter your source and destination file The files for data manager have special storage within the NW BI Database

The files are stored in a special generated table, not as a compressed file within file service.

SAP 2008 / SAP TechEd 08 / IM106 Page 13

Data Preview

After uploading a file, it is a good idea for users to preview the data just to ensure that you havent made any mistakes with your file and the file is in the expected format Data Preview is accessed by clicking Preview data file from the Action Pane. It allows you to preview the first 200 lines of a data file.

SAP 2008 / SAP TechEd 08 / IM106 Page 14

ASCII Import File Formats

The source file for a data import can be a text file containing delimited strings.Each field represents the name of a dimension member.

The source file can be in either of three formats:Delimited

Fixed - requires a first row defining the name and position of all dimensions.

SAP 2008 / SAP TechEd 08 / IM106 Page 15

ASCII Import File Formats

The third file format:Variant - allows the user to define the name and position of the dimensions using multiple lines beginning with an asterisk (*). Can not be viewed in delimited data type only fixed width

While the above example is very simple, some extra features of the variable format can demonstrate its potential as a more useful tool.

SAP 2008 / SAP TechEd 08 / IM106 Page 16

Variable Format Example 1Repetitive field values can be moved into the header section. For example, the above file could also be read in the following format, where the value of the category (ACTUAL) and time (1999.Jan) are set in the header section and removed from the value rows *= specify the value of the dimension, this has the same effect with *NEWCOL command in mapping section. The line start with is the comment line which will be skipped during process.

SAP 2008 / SAP TechEd 08 / IM106 Page 17

Variable Format Example 2If one of the pre-defined values changes along the body of the file, a redefinition of the current member can be inserted anywhere in the file and as many times as desired, like in this example: If the * = header occurs in the middle of data file, all the records following this header are affected, but the records before the header will not.

The results of Example 2 is :

ACTUAL, 1999.Jan, UK, Sales, Sedan, 1234 ACTUAL, 1999.Jan, UK, Sales, Coupe, 2345 ACTUAL, 1999.Jan, FR, Sales, Sedan, 986 ACTUAL, 1999.Jan, FR, Sales, Coupe, 945

SAP 2008 / SAP TechEd 08 / IM106 Page 18

Variable Format Example 3A set of members of one or more dimension can span across multiple columns (Typically 12 months of budget values). The following example of header section will accept 12 value records: * =, has the similar effect with *MVAL command in mapping section, this type of header can only occurs in the beginning of the data file but not in the middle of data file.

Essentially, the variable format allows the user to specify which dimensions are in the page (CATEGORY=ACTUAL), which dimensions are in column (TIME=1999.Jan, 1999.Feb, etc.) and which dimensions are in row (ENTITY,ACCOUNT,PRODUCT,PERIODIC). Irrespective of the format of the source file, the output file will always be in the "fixed format" described for the input file, i.e: The first line will contain the delimited list of all dimension names with their corresponding positions for the data fields. All subsequent lines will define one data cell per line. For example, the above 12 periods variable format file will generate the following output (if we exclude any c