Edit a BPC Standard Package with SSIS

Hi,
I need to edit a BPC standard package ("Convert Task" for example) with SSIS.
I have an Error message of Microsoft Visual Studio :
The task with the name "Admin Task" and the creation name "Osoft.Services.Application.DataMgr.Task.SSISAdmin, OsoftTaskAdmin, Version=4.2.0.400, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648" is not registered for use on this computer. Contact Information:Admin Task
I copied files .dll from "u2026\websrvr\bin" to "u2026\90\DTS\Tasks"
Thank you for your help
Regards,
Morgann

Hi James,
I always have the same issue.
For my customer, BPC is installed E:\ in Citrix environment
In first, I followed the guide "How to...Build SSIS Package for SAP 5.0".
I copied my "osofttask.dll" files in E:\BPC\websvr\Web\Installation\OsoftSSIS_client\Bin to E:\MSSQL\MSSQL2005-0\90\DTS\Tasks
Then, I copied these files in GAC (C:\Windows\Assembly) like your procedure.
But I always had the same error message in SSIS...
Have you another idea ?
Files are copied betwween E and C, is it an impact ?
Thanks,
Morgann

Similar Messages

Running a SSIS package with SQL Job and Linked Server

I have a SSIS 2008 package. In one of the Script task I am calling a stored procedure which is using Openquery using linked server. I deployed this package with protection level as "EncryptWithPassword" and gave a password to the package.
Created a SQL job and edited its command line to include the password. If I login to SQL Server Mgmt Studio with Windows Authentication and run the job manually it runs fine. But when I schedule it then I get an error that "The Communication link to Linked
server failed".
Please help

Hi Vivek.B,
The issue should occur because the SQL Server Agent Service Account or SQL Agent Proxy account under which the job step runs doesn’t have sufficient permissions on the linked server.
If the job owner is the sysadmin fixed server role, the job can be run under the SQL Server Agent Service Account or a proxy account, then please make sure the SQL Agent Service Account or the proxy account has corresponding login on the linked server. If
the job owner is not a sysadmin fixed server role, the job must run under a proxy account. In this case, make sure the proxy account has a corresponding login on the linked server.
Reference:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/10/13/who-owns-my-job-and-who-runs-it.aspx
Regards,
Mike Yin
TechNet Community Support

Has anyone else had problem with the STANDARD package?

Hi Oracle gurus, has anyone here had the same problem with the STANDARD package? Or do I have to reinstall Oracle to make it work?
Thanks.
Ben

missesboggs wrote:
I literally just called AT&T and Apple about this today. I was having issues with iMessage and texting my husband. His texts back to me would show up as my name. Turns out it's because we share the same AppleID. So, I'm currently trying to change mine, but it hasn't worked so far. I'm on hold with Apple right now to see if I can get it fixed.
Both of you have registered the same email address for iMessage. If you were using a shared Apple ID and you updated your phones to iOS5, the default will be the Apple ID. Go into settings and change it.

Error while processing with XML but not with SSIS Package

Hi All,
In the project that I am currently working we are using SQL Server 2005 and its components. We recently upgraded SSRS 2005 to 2008. Now we are in the process of upgrading SSAS from 2005 to 2008.
To process the cubes in 2005 version, we were using 2 methods. One is using XML and the other is SSIS packages. We upgraded one of our cubes to 2008 and we are unable to process the cube using XML but its processing fine when we are using SSIS package.
I Suspect it is something to do with the "Ignore Dimension Key Errors". There are some dimension keys that are missing. It was working fine in 2005 version and also in 2008 version with SSIS.
Please help me with this and let me know the reasons why this happens.
Thanks
Vineesh
vineesh1701

Hi Thomas,
Below are the things you have asked for.
1.
We are running XMLA Scripts as jobs Under SQL Server Agent. The job fails. But cube is processed and the key errors are logged in the specified path.
2.
The same script runs fine in Management Studio.
Executed as user: XXXX. <return xmlns="urn:schemas-microsoft-com:xml-analysis"><results xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults"><root
xmlns="urn:schemas-microsoft-com:xml-analysis:empty"><Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception"><Warning WarningCode="1092354050" Description="Server: Operation completed with 17 problems logged." Source="Microsoft SQL Server
2008 R2 Analysis Services" HelpFile="" /></Messages></root></results></return>. The step failed.
Thanks
Vineesh
vineesh1701

Deploying standard changes to SSIS packages

A couple glitches were discovered in our SSIS template. Approximately 100 packages were built from the template. Is there a mechanism to update all packages with the changes? Or do I have to open each one and manually change?

I'm into the xml and notice a lot of difference between packages for DTS:DTSID I searched the net trying to find what DTS:DTSID is and if I should be replacing this text.
Hi Hawk73ku,
Each package object has a GUID, and the GUID is marked as the DTSID element in the XML code of the .dtsx file. Generally, it doesn’t matter to change the GUID of a package object only if the GUID is unique. However, when we try to modify certain XML code
snippet of a package, there is no need to modify the DTSID element actually.
You can first make the changes to a package, and compare and find out the modified code snippet. Then, you can open the code of any one package, and then perform text replace in the project or entire solution scope.
Regards,
Mike Yin
TechNet Community Support

Good afternoon! I purchased a few months the basics of adobe photoshop package with the CC and Lightroom, but has expired, and was made the annual package. What can I do to solve this problem. I have two weddings being edited and now I can not finish the

Good afternoon! I purchased a few months the basics of adobe photoshop package with the CC and Lightroom, but has expired, and was made the annual package. What can I do to solve this problem. I have two weddings being edited and now I can not finish the work. I thank you.

Renew the subscription?

How to edit in Standard def with 1920x1080 24fps clips

I have Jpegs of digital images 1920 x 1080 24fps which I have used shake to make them into quicktime files in Standard definition (which I understand you can use Uncompresses 8 bit 422, I am then putting them into FCP and I want to edit them in standard def. What settings should I use for my sequence settings and video set up?

Look in your EASY SETUPS...there is one in there called UNCOMPRESSED 8-BIT...
Shane

Can i use the SAP standard package for lock object creation ?

Dear Guru ,
I want to create a new lock ojbect for my abap program .
When i completed the creation , SAP required a new request and it said the object only can be imported to SAP standard package .
But i saw the help from SAP said :
>* Package begins with A-S or U-X:
>These packages are for SAP standard objects. Customer objects cannot be created in them. Changes to objects of these packages are recorded by the Transport Organizer (Request management) and can be transported (see field transport layer.
In this case , Can i use one of the SAP standard package for this creation ? Does it will affect the SAP system ( such as the system upgrade ) ?
Thanks .
Best Regards,
Carlos Zhang
Moderator message - Please do not use code tags to format text - it should only be used for code
Edited by: Rob Burbank on May 25, 2010 11:12 AM

Hi Carlos...
First , You will never be able to use any standard SAP Package for your custom programs. So don't go for it.
So in your case what you need to do is , when you save your Lock object ,
- if you want Transport request to be created , then
in the screen shown you need to enter the Z package name (the same package as that of your ABAP Program)
or
-if you want it to be stored as local object , then
specify package as $tmp
Regards,
Uma

BPC Export data with filter

Hello.
It is necessary to export BPC transactional data by means of a standard export chain.
How can I to customize filter use for export?
Order my actions:
1.Run the Export package with Data Manager.
2.Choose a file name.
3. Choose the dimension. I save a filter by one of attributes. Manage filter name (Button "Manage Filter"-
MYFILTER - Save). Refresh.
Button "Copy all Members". In window with dimension name I see the text [FILTER: MYFILTER].
4. I execute the export package. But csv-file contains only a string with names of dimensions, no transactional data.
How can I solve this problem?
P.S. SAP BPC 7.0 for Netweaver, Support Packages CPMBPC level - 04.
Thanks!
Best Regards,
Svetlana

Hi Andrea,
I don't think you have to support many version of ABAP code - one for each variable.
If your OLAP variable has type Customer Exit you can call SAP function RRS_VAR_VALUES_EXIT_FILL which has variable value as a parameter. You can save that value as a variant of ABAP process type. This way you'll have just one program to support, but as many variants as many variables you need.
Hope this helps,
Gersh

Associate a dtsx package with Visual Studio

when i double click a dtsx package created via import /export wizard, it opens it in Word. what can i do to get it to open in Visual Studio.?
sukai

Hi sukai,
By default, if we’ve ever used Word program open this .dtsx format file, then it always opens .dtsx file in Word.
If we want to directly open the .dtsx file with Visual Studio, we can change the program. For more detail steps, please see:
Right-click file to select “Open with” option.
Expand “+” next to Other Programs.
Click Browser to navigate to “C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE”, then select devenv.exe application.
Click OK. In this way, the .dtsx file would be always opened with Visual Studio. We can design the package, but cannot execute it.
Besides, as Arthur said, by default, the .dtsx file is opened with SSIS Package Execution Utility (DTEXECUI.EXE Utility). I strongly recommend that we should create a SSIS project, then add the package with “Add existing package” option from File System. At
this time, we can edit, execute and deploy it in SQL Server Data Tools.
Reference:
https://www.blackbaud.com/files/support/guides/infinitydevguide/Subsystems/bbdw-developer-help/content/tkaddpackagefromexisting.htm
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Unable to connect to oracle source with SSIS connection manager

I have oracle drivers installed and I am trying to connect to oracle database by using SSIS with oracle provider
Oledb but receiving error as:
Test connection failed because of an error in initializing provider. No error message available, result code: E_UNEXPECTED(0x8000FFFF).Any suggestions
Thanks..

http://sqlblog.com/blogs/jorg_klein/archive/2011/06/09/ssis-connect-to-oracle-on-a-64-bit-machine.aspx
Solution
Download the Oracle 11G full client.
Install the 32 AND the 64 bit version of the
11G full client (Installation Type: Administrator) and reboot the server afterwards. The 32 bit version is needed for development from BIDS with is 32 bit, the 64 bit version is needed for production with the SQLAgent, which is 64 bit.
Configure the Oracle clients (both 32 and 64 bits) by editing the files
tnsnames.ora and
sqlnet.ora. Try to do this with an Oracle DBA or, even better, let him/her do this.
Use the "Oracle provider for OLE DB" from SSIS, don't use the "Microsoft Provider for Oracle" because a 64 bit version of it does not exist.
Schedule your packages with the SQLAgent.
Arthur
MyBlog
Twitter

String literal too long error while invoking a package with clob variable

I have a package.One of the input variables of the procedure in packae is clob.
I want to invoke this package with a huge clob as input.
when i invoke this package like that i am getting following error
PLS-00172 string literal too long
can't we pass clob(huge clob) as input .is there any solution for that ?
Thanks
Pramod Garre

842802 wrote:
If insert this data into a table , from sql prompt still i get the same error.Do you mean SQL*Plus? Then there is buffer limitation and it is better to split literal into, let say 1000 character chunks:
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Mar 29 16:17:26 2011
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
2 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
3 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
4 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
5 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'
6 from dual;
from dual
ERROR at line 6:
ORA-01489: result of string concatenation is too long
SQL> select to_clob('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA') ||
2 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
3 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
4 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' ||
5 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA'
6 from dual;
TO_CLOB('AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
SQL> SY.

Edit font size standard report

Hello community,
I try to edit the font size of a standard report but I can't find any menu within APEX to edit this reports.
I also tried to edit it within the SQL with '< f o n t s i z e=130%">' || ... || '</ f o n t >' but this did not work.
Can anybody help me? Is there a menu which lists all the standard reports and where is the chance to edit this?
Or is there any other chance?
Thank you so much,
Lisa :-)

Hi Lisa,
The font is defined in the style sheet (css file) that is referenced in the Page Template. You can override the style by adding your own style (with the same name as used by the columns in the report - you can check that using Firefox+Firebug or the Developer Tools in Chrome) after the APEX standard CSS. You can also put this CSS in your Report Template or in your Page (if it's only for one specific page).
A good practice is not to include CSS or HTML in your SQL query. Because SQL is logic and HTML/CSS is presentation and these two shouldn't be mixed up.
Roel

Standard Report with IDOC Number and PR number

Hi
My client need the Standard report with the combination fields of " Purchasing Number , Requirements tracking number in PR,
IDOC number , IDOC Processing status. "
(Our PR will generates through IDOC from other system via XI interface)

Hi Nagendra,
for Purchasing Number , Requirements tracking number in PR you can use -ME5A
Purchasing Number-EBAN-BANFN
Tracking number goto- MELB.
table name-EKPO
for IDOC number , IDOC Processing status -we09
For IDOC number -EDID4-DOCNUM
IDOC Processing status-EDIDC-STATUS
Regards,
Krishna.
Edited by: kris_hna on Sep 8, 2011 1:14 PM
Edited by: kris_hna on Sep 8, 2011 1:19 PM

Run package with different user - SUSER does not work in DM Package

Hi,
we need to be able to start a DM package for which the username needs to be changed from your own to a fixed username ...
So in the BPC DM package we enter a fix value for variable SUSER (instead of %USER). However the DM package is still being executed with the user launicn the DM package ... We can see this for example the SQE BADI .. In the DM log the fixed username is being mentioned but it is being executed with your own username ...
The reason why we have this requirement, is to bypass the lacking functionality of a decent security model and to allow a certain (automated) data posting by means of a seperate DM package ...The user only has access to one specific profit center. However for one specific data posting, it needs to be able to have access to all profit centers. We want to achieve this by letting him execute a certain DM package with a fix user, having all the necessary security rights ...
Apperantly the parameter SUSER in the task prompt has no relevance ...

Hi,
I came up with a different solution to this in the end.
You need to set WRITE = OFF in your script logic and handle the write back in your code - see below.
The following steps need to happen after you've completed all of your data manipulation in the BAdI and you are ready to do the write back.
Set Up
Step 1: Set up the impersonation 'domain\name' in BPC Administration -> Set Application Parameters
BAdI code
Step 2: Retrieve this parameter in the BAdI using method GET_PARAM_VALUE of class CL_UJA_APPLICATION
Step 3: Call cl_uj_context=>get_cur_context to get the current context
Step 4: Replace the user id in the context with the value retrieved in Step 2
Step 5: Call cl_uj_context=>set_cur_context to set the context with the new user id
Step 6: Call method write_back_int of cl_ujr_write_back to do the write back
Step 7: Reset the context back to the original user
Here is the code we used - it refers to some internal parameters and variables we have created here so can't be lifted 'as is' but should give sufficent information to replicate this functionality:
****Step 1: Get the application parameter*
TRY.
    create object lo_application exporting i_appset_id       = i_appset_id
                                           i_application_id = i_appl_id .
    lo_application->GET_PARAM_VALUE( EXPORTING I_PARAM_NAME = i_param_name
                                     RECEIVING R_VALUE      = e_param_value ).
    CATCH CX_UJA_ADMIN_ERROR .
*   RAISE ERROR HERE
      exit.
ENDTRY.
****Step 2: Change the user**
* Grab Current Context
lo_context = cl_uj_context=>get_cur_context( ).
ls_user = lo_context->ds_user.
ls_original_user = ls_user.
concatenate l_impersonate_domain '\' l_impersonate_name into ls_user-user_id.
try.
*     Change user so that the data can be written back
      call method cl_uj_context=>set_cur_context
        EXPORTING
          i_appset_id   = i_appset_id
          is_user       = ls_user
          i_appl_id     = i_appl_id
          i_module_name = lo_context->d_calling_module.
    catch cx_uj_obj_not_found.
*   RAISE ERROR HERE
       exit.
endtry.
****Step 3: Perform the write back*
create data lo_error like it_data.
assign lo_error->* to <fs_t_error_records>.
ls_work_status-module_id = cl_ujk_model=>g_module_id.
try.
      create object lo_write_back.
      call method lo_write_back->write_back_int
        EXPORTING
          is_work_status     = ls_work_status
          i_default_logic    = abap_false
          i_update_audit     = abap_true
          i_duplicate        = abap_true
          i_mdata_check      = abap_true
          i_sign_trans       = ' '
          it_array           = it_data
          i_measures_formula = ' '
        IMPORTING
          et_message         = lt_message
          es_status_records = l_status
          et_error_records   = <fs_t_error_records>.
    catch cx_ujr_write_back cx_uj_db_error cx_uja_admin_error cx_uj_static_check into lo_exp.
*   RAISE ERROR HERE
    exit.
endtry.
if l_status-nr_fail > 0.
*   RAISE ERROR HERE
    exit.
endif.
**** Step 4: Change the context back to original*
try.
      call method cl_uj_context=>set_cur_context
        EXPORTING
          i_appset_id   = i_appset_id
          is_user       = ls_original_user
          i_appl_id     = i_appl_id
          i_module_name = lo_context->d_calling_module.
    catch cx_uj_obj_not_found.
*   RAISE ERROR HERE
      exit.
endtry.

Edit a BPC Standard Package with SSIS

Similar Messages

Maybe you are looking for