SSIS packages on BPC v5

Helo Forum,
We encounter the following problem. Within an application we run a logic located in another application.
This usually works fine however in this particular instance the dimension names of the time and entity dimension is different. Hence the package ends in error as he can not find the time and entity dimension in the first application. My quetion is how can I modify the SSIS package so that the dimension name used in the logic is translated to the dimension name of the source application where I call the package.
Thanks for your help

Hi, Sanjaj,
U were right when saying that SAP BPC for NW version has SAP BW backend (not SQL Server) and that's why we don't use SSIS packages in Data Manager functionality. Instead of it we r using packages build on NetWeaver process chains (ABAP). U can get more information about BPC for NW packages at the official help page:
http://help.sap.com/saphelp_bpc70sp02/helpdata/en/af/36a94e9af0436c959b16baabb1a248/frameset.htm
The main idea is that u still have a list of standart packages that u can use (master data loading, transactional data loading, etc) and u can create your own packages build on your own process chains.
Hope that will help u,
Dzmitry

Similar Messages

*Error executing SSIS Package from BPC 5.1*

All -
I'm trying to execute a perfectly working SSIS package from BPC 5.1. When I execute the package it instantly completes executing (Failure) with nothin written to the Log file.
After doing further analysis, we have found the root cause to be "Sequence Containers" in SSIS Packages. We can execute the same package if we remove the sequence container.
When we try to edit the SSIS package via BPC, containing the Sequence Containers", we receive the following error:
[QuerytoServer] An error occurred while getting a package information. System.InvalidCastException: Unable to cast object of type 'Microsoft.SqlServer.Dts.Runtime.Sequence' to type 'Microsoft.SqlServer.Dts.Runtime.TaskHost' at Osoft.Services.Application.DataMgr.PackageExecute.DTSX.GetPackageInfor()
When we try to edit SSIS packages via BPC, containing NO Sequence Containers", everything is wonderful.
Does anyone have any suggestions, besides removing all of the Sequence Containers and moving the tasks to the base SSIS package level?
I trully appreciate any help you guys can provide.

Hi Lars,
Could you be more specific the step you did?
1. It works fine in Visual Studio,
2. It is not working with Excel Front-end. Call the package from Excel.
3. It worked few days ago, ==> Do you mean it was working with #2 step?
I think this might be caused by authentication,
1. could you check your athentication you have for #1 and #2?
2. Did you introduce BPC DM to call the package? BPC DM uses impersonated ID even you use ID which has restrictive to use system resource, there will be no problem for the authentication.
3. As you see the log, it points FLOW task and OLEDB SOURCE, check your connection string in OLEDB SOURCE also.
Hope this helps,
Regards,
YH Seo

Run SSIS Package (SQL Database on Different Server) from Data Manager.

Hi- How to run a SSIS package from BPC Data Manager -This package connects to another SQL Server Database and creates a text file. This text file is the source to BPC custom tasks CONERTTASK and DUMPLOAD task to load to BPC.
Here is the flow of the complete package- Dataflow (Create the text file from a SQL Database)
CONVERT TASK (Convert the file to BPC Format)
DUMPLOAD TASK (Load the converted file to BPC)
Any pointer will be a great help.

Hello Pam,
When you run SSIS package with BPC DM it runs on the application server. You don't really have to run a package on a different server in order to get data from a remote database and dump it to a file. That task can be done in your SSIS package using various data sources/destinations. If that's what you are trying to do. The only thing is, your BPC admin user (the one you used to install BPC) has to have an appropriate privileges on a remote server.
Hope that helps.
Regards,
Akim

BPC 7.0 MS upgrade - reinitiate SSIS packages required

Hello,
We have recently upgraded from BPC 5.1 to BPC 7.0 MS version.
We have SSIS package to load Accounts (as flat file), which load the flat file into a staging table and then moved to <mbraccount>.
This setup works very fine till in BPC 5.1, after upgrade to BPC 7.0 MS and noticed that the Account - member are loaded in jumbled order. Further investigating, we found that the SSIS packages loaded to staging table in the same jumbled order and then followed to copy the same in mbraccount table.
1. Should we required to re-initiate all the SSIS packages (custom built) after BPC 7.0 MS upgrade?
2. Have SSIS packages to load other MasterData, the same procedure as above but no issues in display order of dimension members. Why is it so?
Any clue..
Thanks in advance.
Warm Regards
Uma

Hi Tim,
Thanks for the reply.
No change in the versions SQL SERVER 2005 and EXCEL 2003 for both SAP 5.1 and 7.0.112
These DM packages are customised and flow of data is as below:
Flat File --> Clear the staging table (delete from stage) --> load the flatfile data into Staging table ( via Data Flow task, Table - Fast load option) --> clear the MBR tbl --> Copy Stage into MBRACCOUNT table
Not using the SSIS bulk insert.
This works well after gone live almost for 4-5 months in BPC 5.1 and as said recently upgraded in Mid June 2009, we have issues loading MasterData in jumbled order.
Account ids are all numeric. Flat file extracted from SAP R/3 is in correct sequential order and while loading into Stagingtable.. it sorting order varies and then copied the same into Mbr<dim> table.
Should this problem be with SSIS packages? Any clues.
Warm Regards
Uma

How to build SSIS package for SAP BPC 5.0

Is the above how paper apply to BPC 5.1?
I also have two questions:
1.As we know in the Data Manager 5.1 user guide indicate that we use DTS to manage SQL Server 2000 packages,and SSIS to manage SQL Server 2005 packages.
Also in the guide, when it discuss about the data manager package, it only reference DTS, is all the DTS package discussed in that guide apply to SSIS?
2. from BPC 7.0 NW, the BPC is part of NetWeaver , what role SSIS is play here, since we know that a lot of customer of not use SQL Server as their database.

Hi JW,
The answer to your question #2 is that we won't have SSIS packages in BPC7NW since all SQL server based functionality won't be there in Netweaver version. If you use migration tools to migrate from BPC5.x to BPC7NW, it can convert SSIS packages. However any custom SSIS code would have to be converted manually. For more information, please read Ryan's blog at SAP's definitive strategy for planning technologies moving forward: What's the word on BPC, BI-IP and SRC?
Regards
Pravin

SSIS Package resources

Hello, can someone please guide me to some resources on creating SSIS packages that read data from files, load data into SQL server tables and interface with BPC using the SAP provided extensions to SSIS.
Thanks.

Hey Zack -
This is pertaining to Version 5, but the same procedures translate to later versions...
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2027ebee-a928-2a10-4485-b88c926f5e24
Good luck!
Sean

Multiple Convert/Dump and Load tasks in a single SSIS package?

I'd appreciate some input. We have a single data file that has about 1,000,000 rows of data spanning 28 time periods in the columns across each row. The file is too large to import at one time, and so we have created 9 different transformation files to pull subsets of the timeperiods using MVAL. The end user does not want to have to break apart the file and/or schedule 9 separate imports to bring this file in each time. So, I've attempted to create a single SSIS package that runs each of the 9 required component imports, but I'm running into the following error any time that I try to run more than one import at once:
An error occurred while running a packageException of type 'System.OutOfMemoryException' was thrown.
I've tried using a ForEach loop to simply loop through each of the transformation files and run an import for each transformation file it finds. But, I understand that SSIS doesn't release memory until the end of the ForEach loop, which would explain an out of memory issue. I then broke it out and specified 9 distinct Convert task and 9 distinct Dump and Load tasks in the package with an order of Convert 1 --> Dump and Load 1 --> Convert 2 --> Dump and Load 2, etc. This results in the same out of memory issue any time I enable it to run more than 1 convert/dump & load task in the package - they are not running simultaneously, but rather sequentially. I don't understand this. In looking at the logs, it looks like it's creating the temp files for the first import and adding them into BPC, and then creating the temp files for the second import but then fails prior to the second load. This will work for a smaller data file, but shouldn't the memory be released after the task and allow subsequent tasks to complete? Any recommendations on how to address this and automate this load?

Quick update - I created unique ssis packages for the distinct imports and called those packages from within the initial package that is kicked off through Data Manager, and I ran into the same out of memory issue. Any ideas, suggestions, or help would be greatly appreciated.
Thanks!
Josh

Scheduling SSIS packages through SQL Server Agent

Hello All! I have an SSIS question for BPC 7.5 installations across multiple servers. I have been rebuilding all my DTS packages over to SSIS and trying to learn this more dynamic environment. Currently I have saved a copy of all my rebuilt packages from BIDS (on web server) to the MSDB located on the SQL server. I can manually run packages from Integration Services and load data successfully. When I try to schedule packages based on the packages stored in MSDB, I get failures. The errors initially suggested I was passing over a NULL password, so I adjusted the protection level of the package to ServerStorage, as opposed to the default setting.
Now I have the following error when I schedule and run it:
Message
Executed as user: AMERICREDIT\svcbpc_ssis_dev. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:48:00 AM Error: 2011-02-28 11:48:02.05 Code: 0xC0010018 Source: Convert Task 2008 Description: Failed to load task "Convert Task 2008", type "OSoft.Services.Application.DataMgr.Task.SSISConvert, OSoftTaskConvert2008, Version=7.0.112.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648". The contact information for this task is "". End Error Error: 2011-02-28 11:48:02.06 Code: 0xC0010018 Source: DumpLoad Task 2008 Description: Failed to load task "DumpLoad Task 2008", type "OSoft.Services.Application.DataMgr.Task.SSISTaskDumpLoad, OSoftTaskDumpLoad2008, Version=7.0.112.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648". The contact information for this task is "". End Error Error: 2011-02-28 11:48:02.13 Code: 0xC0010026 Source: Convert Task 2008 Description: The task has failed to load. The contact information for this task is "". End Error Error: 2011-02-28 11:48:02.13 Code: 0xC0024107 Source: Convert Task 2008 Description: There were errors during task validation. End Error Error: 2011-02-28 11:48:02.13 Code: 0xC0010025 Source: Z6_VW_STAT_APLN_CURR Description: The package cannot execute because it contains tasks that failed to load. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:48:00 AM Finished: 11:48:02 AM Elapsed: 1.406 seconds. The package execution failed. The step failed.
It appears I cannot execute any of the BPC custom tasks in the SSIS packages. Any recommendations?

Thanks, James, your point is well taken. Originally we were importing packages into the file system, but had the same results when scheduling.
Below is the message received when I schedule a package located in the stored package file system from my web server:
Executed as user: AMERICREDIT\svcbpc_ssis_dev. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:36:00 AM Error: 2011-03-01 10:36:02.56 Code: 0xC0010018 Source: Convert Task 2008 Description: Failed to load task "Convert Task 2008", type "OSoft.Services.Application.DataMgr.Task.SSISConvert, OSoftTaskConvert2008, Version=7.0.112.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648". The contact information for this task is "". End Error Error: 2011-03-01 10:36:02.58 Code: 0xC0010018 Source: DumpLoad Task 2008 Description: Failed to load task "DumpLoad Task 2008", type "OSoft.Services.Application.DataMgr.Task.SSISTaskDumpLoad, OSoftTaskDumpLoad2008, Version=7.0.112.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648". The contact information for this task is "". End Error Error: 2011-03-01 10:36:02.62 Code: 0xC0010026 Source: Convert Task 2008 Description: The task has failed to load. The contact information for this task is "". End Error Error: 2011-03-01 10:36:02.62 Code: 0xC0024107 Source: Convert Task 2008 Description: There were errors during task validation. End Error Error: 2011-03-01 10:36:02.62 Code: 0xC0010025 Source: Z6_VW_STAT_APLN_CURR Description: The package cannot execute because it contains tasks that failed to load. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:36:00 AM Finished: 10:36:02 AM Elapsed: 1.954 seconds. The package execution failed. The step failed.
Could this be a security thing? If so, what would my security need to be set up from the package level?

SSIS packages to update dimensions

We are having a technical problem with dimension members refreshing after an insert of a new member into the mbr table through an SSIS package
When a new record is inserted into the mbr table, using a sql insert statement and a full process of the application occurs, that member is viewable in Current view BPC Excel after the dimension members are refreshed. However, the new member is not viewable on the Current View of BPC Web, until an individual process of the dimension occurs via BPC Administration (i.e. not a full process of the application).
Do you now of a way to process dimensions rather than applications from ssis tasks
and do you know what SQL layer process is required to get the web POV updated

Wrong forum. Refer thread - SAP Business Planning and Consolidation Topics (BPC)

How to insert CLEAR SSIS Package in another SSIS Package

Hi All,
We have a requirement to run CLEAR SSIS Package in another SSIS Package whish extracts data from Oracle database system. Needed to run CLEAR SSIS Package if data exists in BPC application else run extract to Oracle system. Basically continue with SSIS Package and extract to Oracle system.
In Outlooksoft 4.2 we didn't have any issue, since all evModify is going to be in DTS Package and we didn't have any issues in placing a condition connection to CLEAR Package. Basically we were running CLEAR Package inside anther DTS Package twice successfully.
When we tried to create same functionality in SAP BPC 5.1, the code from EVMODIFY not doing correctly in executing the CLEAR inside another SSIS Package.
If any body knows how to create SSIS Package with a combination of 2 or more SSIS Packages by taking above scenario, please let me know.
The basic requirement is, how do we include a SSIS Package in another SSIS Package and use EVMODIFY to run this meta package in SAP BPC 5.1 environment.
Any information would be appreciated.
Regards,
Sreekanth.

Yes, I have the job , and tried running this, Looks like it started executing. Will update in next 5 mins if it runs fine.
Looking at the command it generated, it looks like it is setting few more parameters like LoggingLevel, Synchronized , callerInfo etc.. I believe these should be optional right?
Also now I have to set two Parameters out of 10 parameters the project takes, If I add additional /Par Project.starttime , will the package pick the values passed from this prompt?
/ISSERVER "\"\SSISDB\FFF\PPP\Xpackage2.dtsx\"" /SERVER "\".\"" /Par "\"$ServerOption::LOGGING_LEVEL(Int16)\"";1 /Par "\"$ServerOption::SYNCHRONIZED(Boolean)\"";True /CALLERINFO SQLAGENT /REPORTING E

Parsing PROMPT values to custom SSIS package

Hi,
I need to extract data from our customers ERP system. I have created a SSIS package doing this. I'm using two SSIS variables 'STARTDATE' and 'ENDDATE' to specify the range in transactions I want to extract. I have tested the SSIS package with the variables pre-filled (in SSIS) from SAP BPC 7.5 and the package is working as expected.
Now i want to change the pre-filled values with values from my PROMPTs in my BPC package. I have created two PROMPTs called BEGIN and END. I have tried to parse the values in different ways, but havn't found the solution. Can anyone guide me in the right direction?
Here the script on my BPC package:
DEBUG(ON)
GLOBAL(STARTDATE,%BEGIN%)
GLOBAL(ENDDATE,%END%)
PROMPT(TEXT,%BEGIN%,"Enter start date:",,"")
PROMPT(TEXT,%END%,"Enter end date:",,"")
INFO(%TEMPFILE%,%TEMPPATH%%RANDOMFILE%)
TASK(CONVERT data,INPUTFILE,%FILE%)
TASK(CONVERT data,OUTPUTFILE,%TEMPFILE%)
TASK(CONVERT data,CONVERSIONFILE,%TRANSFORMATION%)
TASK(CONVERT data,STRAPPSET,%APPSET%)
TASK(CONVERT data,STRAPP,%APP%)
TASK(CONVERT data,STRUSERNAME,%USER%)
TASK(LOAD AND PROCESS,APPSET,%APPSET%)
TASK(LOAD AND PROCESS,APP,%APP%)
TASK(LOAD AND PROCESS,USER,%USER%)
TASK(LOAD AND PROCESS,DATATRANSFERMODE,4)
TASK(LOAD AND PROCESS,CLEARDATA,%CLEARDATA%)
TASK(LOAD AND PROCESS,FILE,%TEMPFILE%)
TASK(LOAD AND PROCESS,RUNTHELOGIC,%RUNLOGIC%)
TASK(LOAD AND PROCESS,CHECKLCK,%CHECKLCK%)
Regards,
Lars

This is confusing, I can't understand why you are getting this error, it seems to me that BPC is trying to look for your stored procedure in your APPSET DB (Source Server) . If your connection object, which is defined in the package is pointing to the correct destination server, then it should work, unless you have modified te connection using Dynamic Script (which it appears not to be the case)
You can try to create the stored procedure in the source system, but I suspect you will get the error message "Object not found, etc... ", becuase your source server doesnt know about your database in your query.
You can try add the following dynamic script, which implicitly tells BPC to override the connection object with the settings you have provided.
DEBUG(ON)
INFO(%DBName%,YourSourcedBName)
INFO(%DSTSrv%,YourDestinationServerName/IP)
PROMPT(TEXT,%BEGINDATE%,"Enter start date:",,"")
PROMPT(TEXT,%ENDDATE%,"Enter end date:",,"")
CONNECTION(SQLconn,ConnectionString,Data Source=%DSTSrv%;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;)
CONNECTION(SQLconn,InitialCatalog,%DBName%)
CONNECTION(SQLconn,ServerName,%DSTSrv%)
OLEDBCONN(Source - LEDGERTRANS,SqlCommand,"EXEC dbo.AXdata '%BEGINDATE%', '%ENDDATE%'")
OLEDBCONN(Source - LEDGERTRANS,OpenRowSet,"EXEC dbo.AXdata '%BEGINDATE%', '%ENDDATE%'")
Make sure you amend the following
YourSourcedBName - Your Destination Server Database Name (The name of the database where you are extracting data from)
DSTSrv - The destination server ne or IP Address
SQLConn - This is the name of your OLE DB connection object defined in the package. This should be the same connection object in which your OLEDB Source is using..
And try to fully qualify your SQL code, meaning try to put the full path, for example
EXEC DBName.dbo.AXdata '%BEGINDATE%', '%ENDDATE%'"
I hope this helps and resolves your error..
Kind Regards
Daniel

Scheduled Packages Hanging (BPC ver 5.0)

Hello,
We are having a problem "scheduling" standard SSIS packages for e.g. import package. When we schedule a package, the package runs successfully for 3 or 4 days (i.e. 3 to 4 cycles) but the package hangs after that. When this happens event though the "Package Schedule Status" shows the status "Running" and the package itself is not executed ("View Package Status" does not show any activity on the package).
Has anyone encountered this issue? If so how can we solve this? (This is a significant issue for us since we cannot reliably schedule any packages)
FYI, we are still on BPC ver 5.0.
Thank you & regards
Raja

Iwould venture a guess that if you are seeing the issue in version 5.0 SP (ANY), that the issue was subsequently solved and fixed in either 5.1 SP(X) or 7.0SP(X). The best chance of determining this is to log a ticket with SAP support for clarification on timing of the issue and resolution. Otherwise, you would need to search the Release Notes from version 5.1 forward to see if and when the problem was resolved.
My immediate advice is to plan accordingly for an upgrade to the newest BPC version on either the MIcrosoft or Netweaver platform. As it relates to the issue at hand; You may want to try to truncate the log table every 2 days and see if that impacts the locking, otherwise, check for any proceses that run on the server or take it offline in the middle of you running the package. I would imagine any MS updates or backup processes will "kill" the process mid stream.
Hope this helps.

How to import SSiS file to BPC 7.5

HI.
I am new to the BPC world and am having trouble learning how to import a master data file from ECC to BPC 7.5. I also need to be able map the property names and add "CC_" to the beginning of each Cost Center. Help would be greatly appreciated.
Thanks.

Hi Christopher
You could read through the thread [Create BPC - Dimension with SSIS Admin Task; to get an idea.
But in essence it might be easier to modify the AdminMakeDim SSIS package and use a DataFlow task which imports the flat file into a SQL table and then in your BPC Dynamic script you pass the name of the table to the task.
Just a few points to note: make sure that the source, or where the table is is in the same database as the Appset database. For example: if you have a staging database even if you qualify the name of the object (DBName.dbo.tblName) it doesn't work, it needs to be in the appset database.
The structure of the table needs to be the same structure as the mbrDimension table. I have tried various methods (additional or less columns), but I have found that if you mirror the structure of the mbrDimension table, it gives less issues.
If you want to apply any logic to you master data, you can use Execute SQL task to execute a SQL procedure which applies your defined checks.
Hope this helps.,
Kind Regards
Daniel

Updating Dimension Members using SSIS packages

Hi!
We use BPC 7.0 MS version. We has developed SQL Integration Service package which load XML file from ftp server and update table mbrEntity in our Application Set Database, when in Administration Console our bpc administrator clicks Export dimension in Maintain dimension property and after that Process dimension.
How can we automatize manually process Export dimension and Process Dimension using SSIS package?
Thank you for attention.
Best regards, Iaroslav

Absolutely yes, you can mix & match the standard SQL tasks with the BPC tasks. This allows for customized interfaces to, for instance, connect to a remote DB (or flat file that you FTP to the BPC app server), stage the data in the BPC appset database (in custom tables that you create there), cleanse it, and then process it into the standard dimension table using the BPC task.
Similarly, you can program anything else you'd like in the SSIS package - interact with the file system on the app server (drop a data export file into the user's PrivatePublications\DataManagement\DataFiles folder, where they can then download to their PC), or Excel (load in the data which users maintain in a BPC conversion file from Excel into a custom DB table, to manage your mappings on the DB), etc. -- and then allow users to execute these packages from eData -> Run Package.

SSIS Package Fails Immediately in Data Manager

Hey all!
I have an SSIS Package that works perfectly in my Production system. I'm currently trying to test the exact same package in my Test System. The only change I've made to the package was to change the server name to point to our Test Server.
Now, within SSIS, this Test package runs completely fine. However, when I try to run the exact same package through the Data Manager. The package Errors out immediately. Of course, BPC gives no error message at all to help troubleshoot.
Does anyone have any idea why this package would work on our Production system, but not our Test Server? Any hints on what to look for would be extremely welcome!
Thanks much!
Sean

For clarity, you have an SSIS package in production, in the DM file folders, that you are copying over to a file location in the TEST environment. Then you are adding the package via the DM interface. The saving the view. Then trying to execute the package?
-If you edit the package via the DM interface, does everything look correct, regarding settings for the package?
-Does the package have more SSIS tasks than just standard BPC tasks? Do they need to be modified for the new servers.
- WHat does the package do? Is it supposed to run logic? B/c it may need the logic statements to be validated and saved?
Please Let us know.

SSIS packages on BPC v5

Similar Messages

Maybe you are looking for