Documentos de Académico
Documentos de Profesional
Documentos de Cultura
SAP Business Planning and Consolidation Data Manager: Now and the Future
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
BPC Versions
Previously
BPC 5.x
Today
BPC 7
BPC 7 M
Future
BPC 7.5
BPC 7.5 M
Microsoft based SAP NW based
Data Manager
Data 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*
Data Manager
Within the two platforms, there are two different underlying base technologies employed
BPC 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
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
From the Launch Page, click SAP Business Planning and Consolidation for Excel. From the Action Pane, click Manage Data.
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
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
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 upload
ALLOWEXTENSIONS: 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
The files are stored in a special generated table, not as a compressed file within file service.
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.
The source file for a data import can be a text file containing delimited strings.
Each field represents the name of a dimension member.
Fixed - requires a first row defining the name and position of all dimensions.
While the above example is very simple, some extra features of the variable format can demonstrate its potential as a more useful tool.
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
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 conversion of the members labels):
For users who dont like the action pane or menu, BPC also has a Data Manager toolbar
Icon Task Run Package View Status New Transformation File Manage Transformation File Validate and Process Transformation File Copy Transformation File New Conversion File Manage Conversion File Validate and Process Conversion File Copy Conversion File Add Conversion Sheet <Selected Dimension> Description Opens the Run Package dialog box, where you can run a package for a team and application. Opens the View Status dialog box, where you can see the status of currently running or previously run packages. Creates a new Transformation File Excel workbook. Sub menus allow you to edit, save, copy, and validate transformation files. Checks the structure and syntax of transformation files and reports any potential problems. Creates new transformation files based on existing ones that you can then modify for your needs. Creates new conversion files. Sub menus allow you to edit, save, copy, and validate conversion files. Checks the structure and syntax of conversion files and reports any potential problems. Creates new conversion files based on existing one that you can then modify for your needs. Adds a sheet to an existing conversion file. You can have multiple sheets in one conversion file in order to use different sheets depending on the context of the transformation. Works with the Show Member List button to show the Data Manager member selector for the selected dimension.
Show Member List button Clicking this button shows the Data Manager member selector.
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
Icon
Task View Status New Automation Edit Automation Run Automation Data Upload Data Download Refresh Package List Exit
Description View the status of all scheduled and finished packages Allows you to create an automation for reuse of scheduling packages Edits an existing automation Run an automation Upload a file to file service Download a file from file service Refresh the list of packages (discards all changes that havent been saved) Exits the scheduling package functionality.
NOTE: To refresh the view, you can choose Refresh status every and specify the polling time to refresh the job list.
The detailed log will give you detailed information for success or failed jobs: The runtimes for each process type within the process chain The successful and failed records and package status
All user input for data management prompts are automatically saved This improves usability for repetitive DM tasks A user can clear the saved prompts by selecting the appropriate menu item
DEMO
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
Organizing Packages
Packages are arranged for the convenience of the customer and their end-users. All packages in company are visible and available to all users with Data Manager task access Packages can also be organized by defined security teams. In the image below, admin is a team of users. The list is NOT a reflection of available packages, it is a reflection of what packages are available to the users of an application. These packages are copied from an application when you create a new application and are delivered by default for all applications
Organize Package
Organize package is controlled by administrators and team leaders (only for their teams) Package options Add - allows authorized users to select from available packages on the server Modify allows authorized users to change the variables or behavior of a package, it is best practice to first copy a pre-delivered package prior to modification to ensure the original package remains as shipped with the product. Copy creates a duplicate package with a new package ID Move moves a package between teams and/or package groups, it is common to remove rarely used or potentially damaging packages from the company team to the admin team Remove remove the package from the selection screen Package groups equivalent to folders unique to each team Add creates a new grouping Modify allows for a change in the grouping name Remove removes the group
You can assign your package to a Group. This is the folder to which the package will be added. You can add a new group by typing a new group name. This is just used for organization and categorization. The group field has no functional impact. You can populate a description as well to describe your package
If you flag Admin Package, this will take precedence, and ignore that User Package is flagged
If the task type is flagged as Admin Package only users who are BPC Administrators will be able to run this package. This package can still be saved to any team (even non-Admin) teams, but only Administrators can run this package
A BPC Administrator is defined by a user who has access all the DM Tasks assigned see the list below
User Package can be seen by all BPC Users that are assigned Execute Data Management task security Packages can be assigned to teams using the menu Manage team user package access by a team leader or as part of organize packages if an administrator The primary purpose is to restrict a user from running a package that could damage to the data like clearing all data (zero values) by accident. NOTE: BPC 7.0M has two additional package types that are not used in BPC 7.0NW for special actions or packages that process the fact or cube
Modify Package
BPC 7.0 allows for the modification of a package via the BPC Excel eData interface Package type Name of the process chain or SSIS package Package name Location Descriptive name to display Task type
User Admin
Only packages that are flagged as Task Type = User Package and not flagged with Task Type = Admin Package will be allowed to be executed by BPC Users that have the Execute You will not see any packages within this list that have been flagged as Admin Package
Icon
Task Add Package Modify Package Copy Package Move Package Remove Package Add Package Group Modify Package Group Remove Package Group Save Package List Refresh Package List Exit
Description Used to add a new data manager package (choose the Process Chain to assign) Allows you to update package definition Gives you the ability to copy packages between teams and package groups Allows you to move packages between teams and package groups Delete a pacakge Create new package groups (folders) for organizing your packages Allows you to rename package groups (folders) Delete package groups (folders) Saves all changes made to packages. None of the changes are committed to NW until this button is clicked Refresh the list of packages (discards all changes that havent been saved) Exits the organize package functionality.
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
Transformation Files
Transformation file is selected during the run time of the import package. Transformation definition are in Excel files that contain one worksheet named Instructions. The file is divided into 3 parts (*OPTIONS; *MAPPING, *CONVERSION) The transformation file references conversion files that may contain multiple worksheets.
Transformation Files
SAP 2008 / SAP TechEd 08 / <Session ID> Page 44 IM106 Page 44
DEMO
Transformation Files allow application administrators or team leaders to set up the rules for reading data from a source and putting it in the proper form within your SAP BPC 7.0 target application. To create a new Transformation file,
select eData > New Transformation File. To edit an existing Transformation file, select eData > Manage Transformation Files, choose a team in the left column of the dialog box, choose a folder, and then double-click an existing Transformation file name. Fill out or define the options, mapping, and conversion file sections.
*OPTIONS: Set up Mapping Options *MAPPING: Map Dimensions to source *CONVERSION: Setup Conversion Files for dimensions
HEADER = YES | NO Required Parameter If YES, then your input file contains one header row that defines the fields. If you do have a header row, you can refer to a field by name in the MAPPING section. Default: YES MAXREJECTCOUNT = <empty_string> | -1 | positive number Required Parameter If validating records, the number of rejected records at which to stop processing. A value of -1 implies that DM should keep processing no matter how many rejected records exist. The default value is 500, which can be represented by an empty string. Default: <empty_string> SUPPRESSCHARACTER = <text> This option is used to remove certain text in records, the text is specified by <text>, for example
SUPPRESSCHARACTER = abc will remove all abc occurs in the data records.
Default: <empty>
VALIDATERECORDS = No | Yes Required Parameter Default: No If YES, validate the mapping and that members exist, and map data in the proper order for Business Planning and Consolidation. For example, the Amount field is always moved to the end of the records even though it might be written in the first line of the mapping section. If NO, will not validate. In this case, if the mapping section is out of order or just wrong, fields will be skipped.
SAP 2008 / SAP TechEd 08 / IM106 Page 48
While this is supported, it will just cause confusion by setting this to yes This is there for legacy reasons
*IIf() Example 1
Example 1: Given this data:
Entity, SEntity U1000000, US01 Z2000A01, CA03 K3430000, JP04 Entity=*IF(*col(1,1:1)=U then SEntity;*col(1,1:1)=Z then *col(1,3:6); *STR(ERR)) Entity, SEntity US01, US01 A01, CA03 ERR, JP04
*IIf() Example 2
Example 2: Given this data:
ENTITY 52 EF KL
Product=*IF (product+ID+Entity=*Str(148552) then *str(MHarn);ID(1:1) = *str(C) then *str(XX) ; *str(YY)) PRODUCT, MHarn, AB, YY, ID, 85, XX, IJ, ENTITY 52 EF KL
Besides the simple header(the header with only one line), the data file can also contain variant header, the header can have several lines, each line must start with *(star), here is four cases for variant header Case 1 This case is same as the simple header.
*CATEGORY, TIME *ENTITY, ACCOUNT, PRODUCT *PERIODIC 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
Case 2--*<DIMENSION>=<VALUE> 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.
*CATEGORY=ACTUAL *TIME=1999.Jan *ENTITY, ACCOUNT, PRODUCT *PERIODIC '----------------------------------this is the comment line, will be skipped when processing UK, Sales, Sedan, 1234 UK, Sales, Coupe, 2345 FR, Sales, Sedan, 986 FR, Sales, Coupe, 945
Case 3If the *<Dimension> =<value> header occurs in the middle of data file, all the records following this header are affected, but the records before the header will not.
*CATEGORY, TIME *ENTITY=UK *ACCOUNT, PRODUCT, PERIODIC ACTUAL, 1999.Jan, Sales, Sedan, 1234 ACTUAL, 1999.Jan, Sales, Coupe, 2345 *ENTITY=FR ACTUAL, 1999.Jan, Sales, Sedan, 986 ACTUAL, 1999.Jan, Sales, Coupe, 945 The results of Case 3 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
Case 4--*<Dimension> =<value1>,<value2> 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.
*CATEGORY=ACTUAL *TIME=1999.Jan, 1999.Feb, 1999.Mar, 1999.Apr, 1999.Jun, 1999.Jul, 1999.Aug, 1999.Sep, 1999.Oct, 1999.Nov, 1999.Dec *ENTITY, ACCOUNT, PRODUCT *PERIODIC UK, Sales, Sedan, 100, 200,320,450,600,700,850,900,230,200,340,560 UK, Sales, Coupe, 1120, 1230,1220,470,1600,7900,1850,1900,1230,3200,3340,2560
If you are an application administrator, select eData > Validate & Process Transformation File.
When you choose to validate, you can choose the type of transformation file youd like to validate against: Transaction data
Loading a flat file into a BPC Cube
Master Data
Loading a BPC InfoObject Master data and attributes
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
*Conversion
Conversion files define the mappings by Dimension Define the mapping from external to internal member names (source to target) Provide the ability to perform arithmetic and rounding on data. Can contain one or more worksheets for different types of data transformations. * Skip Ignore external data Wildcards: You can use the asterisk (*) and question mark (?) wildcards in the External and/or Internal columns. asterisk (*) stands for ANY character, while question mark (?) stand for any SINGLE character.
Within BPC 7.0NW, Data Manager Supports Javascript in Conversion Files Within BPC 7.0M, Data Manager Supports VBScript in Conversion Files
Conversion Files
SAP 2008 / SAP TechEd 08 / <Session ID> Page 70 IM106 Page 70
DEMO
the input member names of dimension Account will be converted according to the conversion rules defined in the conversion file AccountConv.xls. It will use the sheet CONVERSION. Use the keyword Amount and the transformation option ConvertAmountWDim to get formula
Amount = AccountConv.xls!Calculus
This conversion file should be in the company folder This conversion file should be located in the corresponding folder of AdminTeam
Account = [AdminTeam]AccountConv.xls!newaccount
Refers to the source value since CONVERT_INTERNAL = NO You can use wildcards to match source values
Refers to the target dimension member you want to load into the application (since CONVERT_INTERNAL = NO) You can use formulas within this column Use %EXTERNAL% in your formula to refer to the source value for derivation of the target value You can use wildcards to replace target values
You can use the keyword VALUE to refer to the signeddata value in the source file
Special Options:
*SKIP: You can ignore some data records and just skip them without loading them into the target cube.
The below example means that all the data records will be skipped and not be loaded into target cube, if the
Wildcards: You can use the asterisk (*) and question mark (?) wildcards in the External and/or Internal columns. asterisk (*) stands for ANY character, while question mark (?) stand for any SINGLE character. You also can use colon mark (:) for a specified range.
For example, if you want to reference all members, use the asterisk (*). This would be useful to apply a formula to
Using Wildcards
Wildcards can be used within both the external and internal columns! This will allow for very dynamic replacements (convert_internal = NO, the input member name will be compared with External column)
Correct examples:
Case 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Input member name abcdef abcdef abcdef abcdef abcdef abcdef abcdef abcdef abcdef abcdef abcdef abcdef 23 abs c100 Wrong examples: Input member name abcdef abcdef abcdef External a*f abc* *f a*f abc* *f a*c*f a*f a*c?*f a*c?? abcdef abc??? 1:100 aba:abz c001:c999 External a*c*f a*d*f abc??? Internal c*g c*g c*g cg* cg* *cg cg c*g* cg c*g c*g ???cg abc def def Internal *cg *c*g ????g Result cbcdeg cdefg cabcdeg cgbcde cgdef abcdecg cg cbcdegbcde cg cbg cg defcg abc edf def Result Error, the meaning of asterisk (*) for replacement is vague. Error, the meaning of asterisk (*) for replacement is vague. Error, the number of ? is not consistent
17 18 19
To write a formula for dimensions, you will write this formula within the INTERNAL column
This formula will do the following: If the value for category in the source file begins with act, then it will map this
value to Actual. Otherwise, it will check if the value for category in the source is 4 characters long. If it is, it will write the value Budget. If not, it will write the value Actual
To write a formula to update SIGNEDDATA, you will write this formula with the FORMULA column
This formula will take multiple the value of signeddata in the source by 100 and round it to two places for all time
VALUE This can only be used in the formula column of a conversion file It refers to the signeddata in the source file you are trying to load from. The Keyword VALUE is treated as a formula variable in a conversion file AMOUNT The keyword AMOUNT can only be used in the conversion section in transformation files;
Return a Long containing the number of characters in a string Return the length of the string contained in external. Return a string in which a specified substring has been replaced with another substring a specified number of times.
js: %external%.length
Currently, we do not allow creating custom javascript includes (This is being evaluated for a feature pack)
SAP 2008 / SAP TechEd 08 / IM106 Page 79
formula
Formulas Example 2
Example 2: The input member names are Acc123 and bcdef. The rules in AccountConv.xls are:
formula
Formulas Example 3
Example 3: ConvertAmountWDim = Account The input member names of Account are Acc123 and bcdef with values 100 and 200 respectively. The converted member names of Account are Accpay and Accrec. The rules in the sheet Calculus of conversion file AccountConv.xls are:
To validate a conversion file, choose Validate & Process Conversion File within the eData menu The validate process performs only one thing: Check if the excel sheet format (the header line should be External, Internal, Formula) is correct. It will not perform: check formulas --- this will be checked at runtime. check dimension names --- dimension name will not appear in conversion file, so it will not be checked. check valid dimension members --- dimension members will be checked at runtime if the value of the transformation option VALIDATERECORDS is yes.
To copy Conversion files Choose Manager Data -> Manager Existing Conversion Definition Open a Conversion File Choose Copy Conversion Click Save
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
DEMO
UI Script
SAP 2008 / SAP TechEd 08 / <Session ID> Page 94 IM106 Page 94
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
Loading Large Files from AppServer Instead of Database (SAP NetWeaver Version Only)
When the user wants to execute this package (i.e. package runtime), he will be asked to select the file they want to use in their Data Manager package. The user will be given a dialog box containing an F4/Value Help function, to select from a list of files. Instead of choosing a file, the user can specify a NetWeaver application server file system location to import a file from the NW Application Server. This may be useful for any files that are already being stored on the NW Application Server from 3rd party applications For example: /uscikp1_KP1_77/tmp/FINANCE2250000.txt
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
These process chain templates can be displayed and edited in ABAP transaction RSPC
This package allows you to load dimension member texts directly into a /CPMB/IMPORT_DESCRIPT EVDESCRIPTION (BW InfoObject's text table) BPC: Import Transaction Data This package imports one or more ASCII files into the current application. /CPMB/IMPORT You are prompted for one or more import file and associated transformation files. The signs of the amounts are reversed based on the Account type. You can use the import.xls transformation file with this package. BPC: Load Transaction Data from Other Cube This package allows you to load data from one BI Cube (EDW or BPC) /CPMB/LOAD_INFOPROVIDER into a BPC Application. You can associate a tranformation file to do the mapping. BPC: Move Transaction Data in one cube This package lets you move any selection of data within an application. /CPMB/MOVE You are prompted for source and destination data selections for all dimensions. The destination selection's fact table records are cleared before the source's records are moved. The source's fact table records are cleared after they are moved to the destination. BPC: Clear Transaction Data in One Cube This package clears the data in the BPC Application by importing zero /CPMB/CLEAR values. The optimize process removes the zero values, which clears all values from the table. Running this package also clears comments from the comments table. You can use the import.xls transformation file with this package. You must select at least one dimension in order to run this package. If you select [All], the package will not run. BPC: Copy Transaction Data in One Cube This package copies data between dimensions within BPC application. /CPMB/COPY BPC: Append Transaction Data This package imports data into the application by appending the data to /CPMB/APPEND the fact table, and then runs default logic against the imported data set. You can use the import.xls transformation file with this package.
If your GL only provided a new export for actual and May on its entirety, you would not be able to determine accounts that have been reclassified, changed or remain the same Replace lets the user reset that region of the cube similar reloading the file as if it was a new data set It is really an option for what the import file represents
The merge option (alternative to replace) changes only like data between source and database
Supposewewereloadinganewfilewiththesecontents:
ACCOUNT FRINGEBENEFIT DIRECTLABOR CATEGORY ACTUAL ACTUAL DATASRC INPUT INPUT ENTITY SALESITALY SALESITALY INTERCO NON_INTERCO NON_INTERCO RPTCURRENCY LC LC TIME 2006.JAN 2006.JAN SIGNEDDATA 1600 160
InBPC7.0,usingtheMerge option,theoutputwouldbeasfollows:
ACCOUNT FRINGEBENEFIT OTHEREXP SALARIES.CAT1 DIRECTLABOR FRINGEBENEFIT OTHEREXP SALARIES.CAT1 CATEGORY ACTUAL ACTUAL ACTUAL ACTUAL BUDGET BUDGET BUDGET DATASRC INPUT INPUT INPUT INPUT INPUT INPUT INPUT ENTITY SALESITALY SALESITALY SALESITALY SALESITALY SALESITALY SALESITALY SALESITALY INTERCO NON_INTERCO NON_INTERCO NON_INTERCO NON_INTERCO NON_INTERCO NON_INTERCO NON_INTERCO RPTCURRENCY LC LC LC LC LC LC LC TIME 2006.JAN 2006.JAN 2006.JAN 2006.JAN 2006.JAN 2006.JAN 2006.JAN SIGNEDDATA 1600 500 250 160 15 20 30
Standard Data Management Packages BPC: Load Transaction Data from Other Cube
BPC: Load Transaction Data from Other Cube
This package allows you to load data from one BI Cube (EDW or BPC) into a BPC Application You are prompted for one or more source and associated transformation files The signs of the amounts are reversed based on the Account type Security is required to be granted to the BPC service users to allow NW BI access to any source EDW cube if an EDW cube is used
SALESITALY SALESITALY
RPTCURRENCY LC LC
In BPC 7.0, using the Append capabilities, the result would be as follows:
ACCOUNT FRINGEBENEFIT OTHEREXP SALARIES.CAT1 DIRECTLABOR FRINGEBENEFIT OTHEREXP SALARIES.CAT1 CATEGORY ACTUAL ACTUAL ACTUAL ACTUAL BUDGET BUDGET BUDGET DATASRC INPUT INPUT INPUT INPUT INPUT INPUT INPUT ENTITY INTERCO NON_INTERCO NON_INTERCO NON_INTERCO NON_INTERCO NON_INTERCO NON_INTERCO NON_INTERCO
RPTCURRENCY LC LC LC LC LC LC LC
In the underlying table, EVDESCRIPTION isnt stored in the member table A foreign key relationship to this language specific table Logon will read the dimension member table, and join to this language specific table Text returned based on end-user setting Users member sheet will only show this text Updating EVDescription will update this language specific table. The user can maintain there language view My Settings using BPC Web
Process Chain Template BPC: Default Formulas Logical BPC: Allocation BPC: Calculate Ownership BPC: FX Restatement
Description This package executes default formulas stored in your default.xls file. The package runs the Allocation logic. The package runs the CalcOwnership logic. This package is used for currency translation. The package runs the FXTrans logic. BPC: IC Elimination This package is used to Perform Inter-Company eliminations. The Package runs the ICElim logic. BPC: ICBooking The Package runs the ICBooking logic. BPC: ICData The Package runs the ICData logic. BPC: Legal Consolidation The Package runs the LegalConsolidation logic. BPC: Opening Balances The Package runs the OpeningBalances logic. BPC: Run CalcAccount The Package runs the CalcAccount logic. BPC: Clear the Journal Clears Journal tables and creates an output file. Tables BPC: Export the Journal Exports Journal tables to an output file Tables BPC: Restore Journal Allows you to load Journal tables from a File Tables
TechName /CPMB/DEFAULT_FORMULAS /CPMB/ALLOCATION /CPMB/OWNERSHIPCALC /CPMB/FX_RESTATMENT /CPMB/IC_ELIMINATION /CPMB/ICBOOKING /CPMB/ICDATA /CPMB/LEGAL_CONSOLIDATION /CPMB/OPENING_BALANCES /CPMB/RUNCALCACCOUNT /CPMB/CLEAR_JOURNALS /CPMB/EXPORT_JOURNAL /CPMB/RESTORE_JOURNALS
Take the system offline. Can only be run by administrators with the appropriate task security.
Description Creates dimension members using a SQL table and schedules the processing of dimension members. For example, if a new member ID is added, this process updates the fac2 table with the updated list. See Scheduling dimension member processing
TechName /CPMB/ADMINTASK_MAKEDIM
BPC: Admin Task Validate Validates the logic file. BPC: Validate Transformation Validates the Transformation Files for Data Manager File BPC: Validations Runs BPC Validation of Business Rules Table BPC: Archive Activity Archives Audit Activity BPC: Archive Data Archives Audit Data BPC: Clear Comments Clears comments from the comments table. BPC: Full Optimization Runs the BPC Admin Full Optimization Process - this chain can be run from Admin Console BPC: Light Optimize Cube Runs the BPC Admin Light Optimization Process - this chain can be run from Admin Console
Process Chain Template BPC: Import and Send Mail BPC: Import Using FTP
Description TechName Import an ASCII file and send the result to specific user. /CPMB/IMPORT_A_SEND_EMAIL This package allows you to import an ASCII file to download from an FTP /CPMB/IMPORT_USING_FTP site into the current application. You can use modify the server name within the package. After you modify the server name, you can run this sample package at any time.
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
Today, there is a how-to guide available for the MSFT version already Use Data Manager packages to natively transform NW BI data to BPC format data Possibly via Data Integrator/BICS/UD Connect
Tighter integration to NW BI
In the future:
Enhanced parallelization and performance enhancements Enhanced user experience and even simpler user interface
This slide outlines our general product direction and should not be relied on in making a purchase decision. This slide is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this slide or to develop or release any functionality mentioned in this slide. This slide and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This slide is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this slide, except if such damages were caused by SAP intentionally or grossly negligent.
SAP 2008 / SAP TechEd 08 / IM106 Page 117
3. Design-time
Transformation Files Conversion Files UI Script Security Large Files Delivered Objects
4. Future 5. Wrap-up
Further Information
SAP SDN/BPX Community:
EPM Page: www.sdn.sap.com/irj/sdn/bpx-epm EPM Blogs: www.sdn.sap.com/irj/sdn/weblogs?blog=/weblogs/topic/82 EPM Forums: www.sdn.sap.com/irj/sdn/forum?forumID=270
Thank you!
SAP 2008 / SAP TechEd 08 / <Session ID> Page 120 IM106 Page 120
Thank You !
SAP 2008 / SAP TechEd 08 / IM106 Page 121