Working with Compounding infobjects in BEx

The customer wants to be able to drill down on infoobject LOCATION (Madrid etc)
without the SUBDIVISION on Location(A111 etc). SUBDIVISION is a compounding object of LOCATION.
I will try to explain with an (dummy) example:
Current situation:
Country         Location             Headcount
SP                A111/Madrid           10
SP                A112/Barcelona        20
SP                A114/Madrid           4
Requested situation:
Country         Location             Headcount
SP                Madrid               14
SP                Barcelona            20
Is it possible to summarize the data on LOCATION without SUBDIVISION in BEX?Or do we have to add a new characteristic with a different key having only LOCATION?
Thanks
KT

Hello Pradeep,
I can remove the infoobject SUBDIVISION but i still have LOCATION with the values A111/Madrid etc.I only want "Madrid" to be displayed under LOCATION.
Thanks
KT

Similar Messages

How can i work with variables of the BEx-Query in WAD ???

Hi Experts !
In my Web Template i want to work with the value of a BEx-Variable like this :
</td>
<td class="SAPBEXTbsTab" id="head_TAB4"><A href="javascript:if (V_TEST != '1') {goto_tab('TAB4')}">Summenblatt 3</A>
</td>
V_TEST is a variable in my BEx-Query. Does someone know how i can get the value from this variable ???
Thx Andreas

to get the query variable value into javascript variable you can do like below
<script>
var period_val = '<object>
         <param name="OWNER" value="SAP_BW"/>
         <param name="CMD" value="GET_ITEM"/>
         <param name="NAME" value="TEXTELEMENTS_PERIOD"/>
         <param name="ITEM_CLASS" value="CL_RSR_WWW_ITEM_TEXT_ELEMENTS"/>
         <param name="DATA_PROVIDER" value="DP"/>
         <param name="GENERATE_CAPTION" value=""/>
         <param name="ELEMENT_TYPE_1" value="VARIABLE"/>
         <param name="ELEMENT_NAME_1" value="0P_FPER"/>
         <param name="ONLY_VALUES" value="X"/>
         ITEM:            TEXTELEMENTS_PERIOD
</object>';
</script>
Raja

Filter Web Template with URL Cmd: doesn't work with compound infoobject ?

Hello all,
I've to filter the query contained on a web template with URL command, but it doesn't work.
The web template contains only one query, and on the free chars I have 0PLANT.
I call the web template adding to the normal url the following command:
&FILTER_IOBJNM=0PLANT&FILTER_VALUE=33
where 33 is the code of the plant I want to filter.
The command is executed, I think, because the result is "NO APPLICABLE DATA FOUND". The fact is that when I execute this query on the Bex filtering 0PLANT by value 33 the data exists.
May be because 0PLANT on our system is in compound with 0SOURSYSTEM ? In this case, what's the value I can use as filter ?
Thank's in advance,
Max

Hi,
please see http://help.sap.com/saphelp_nw04/helpdata/en/59/edfe395dd76846e10000000a114084/frameset.htm
especially:
If the variant with ending 'EXT' is selected, the fully compounded value has to be entered in the external format, for example, 24.12.2000.
If the ending 'EXT' is not used, the fully compounded value has to be entered in the internal format, for example, 20001224 for 24.12.2000.
and
In the internal display (see table below) you can easily determine the name of the characteristic and the filter value using the URL parameter &snippet_operations=%20 (see also Object Tag for the Properties of Web Templates). Call the Web application with this URL parameter. If you filter using the context menu, the parameters FILTER_IOBJNM and FILTER_VALUE are automatically added to the URL in the Web browser. You can then use the desired values with Command URLs in hyperlinks.
Heike

Issue with Compounded infoobjects in BEx

Hey Everyone,
I have a small issue when running a report in BEx. I want to be able to run a report against different Profit Centers, and have all values on the same line. But, in some cases, I have the same Profit Center on different lines, because the Controlling Area is different (compounded with Profit Center).
Example:
Profit Center           Site            Value
1000-103                1000           $100
1000-103                1000           $200
I want to see:
Profit Center           Site            Value
1000-103                1000          $300
I have set Controlling Area to NO DISPLAY in the query properties, and it doesn't display it, but still puts the same Profit Center on two separate lines, because it's compounded and because it does actually have a different Controlling Area.
Is there anyway to not have the Controlling Area influence my result, and have the same Profit Center aggregated with the other, so they end up on the same line?
Thanks,
John

Hi ,
try this:
steps:
1. Remove the Profit center from your report .
2. Drag it again in rows where u want the profit center be.
When u r draging the profit center to rows "Controlling area" will also come along with it as that was compounded.
3. Drag "Controlling area" info-object to "Filter section" of query designer.
4. make the Display properties setting of "Profit Center " as "Standard text".
That will solve the problem .
Thanks
Mukesh

Working with documents via BEx Analyzer not using the portal

Hello,
i read that we are able to create (work) with documents (comments) via
BEx Analyzer. When i want to add a comment how it is described in the
help we get connected to the portal. We dont want to use the portal for
that. Therefore we searched a way to skip the portal. We read that in
BW Versions before 7.0 the portal was not connected but since 7.0 we
have the portal connectivity, but it should also possible to not use
the portal and to access directly the BI Server. I searched for the
Customizing to do so but i could not find it where to switch to the old
logic.
And another question is when we use the Portal with the knowledge base . The documents are stored in the document framework (SKWF). Is it the same as the Datawarehousing Workbench --> documents. This storage we want to use.
Can anyone give me a hint?
Kind regards,
Murat

Hi Murat,
We are also facing the same issue of when trying to create/access the documents from BEx analyzer it is connecting portal , we need to bypass portal and directly access the document browser in BW server.
In your thread you mentioned it is done. So can you please let me know how did you enable the old configuration?. It will be very much helpful to us.
Awaiting for your reply.
Thanks,
V.Senthilkumar

How to work with BI using Visual Composer....?

Hi
I want to work with BI report and BEx analyzer etc using Visual Composer.
I am using Visual Composer 7.1. I have configured BI system connection using the following link
http://help.sap.com/saphelp_nwce10/helpdata/en/7e/6dbcea3700452195e3bddaa47c5906/frameset.htm.
In the above document i didnt understand the following para....
Creating BI Users in the Portal
Ensure that the BI back-end users also exist in the J2EE Engine. You can use the BI back end as the user store for the J2EE Engine or you can create the users manually. If you create the users manually, you should ensure that they have the same names as in the BI back-end; this avoids the need to configure user assignment.
How to check BI back end user also exist in J2EE engine ?
How to use BI kit in Visual composer. From where can i download BI kit for Visual Composer.
What is the difference between developing application in VC using the above method and using BI kit.
Please help me....
Regards
Sowmya....

Hi,
Without the BI kit you cannot do a lot of things in VC 7.1.
This kit is not available with 7.1.
The part that you did not understand meant that if you opening VC using a certain id in portal for eg "user" then the same id should be present in your backend system in this case BW system.
Without this it wont be able to connect to the system.
Hope this helps
Regards
Nikhil.
Reward points if you find the answer helpful

RRMXP does not work with GUI 7.20

Hi Experts,
I have the following problem. RRMXP does not work with GUI 7.20, BEX 7.0 launches and I have to enter proper user and password. (I get SAP Logon screen with listed systems)
It works properly with GUI 7.10 and I have not to log into BEX.
Did anyone encounter such problem? Does anyone know what causes the problem?
Regards&thanks
Marek

Hi,
RRMXP uses OLE to launch Microsoft Excel together with the SAP BEx add-in. Then it use a macro within BEx to open the workbook. check whether BEx is not installed properly (run SAPBEXC.XLA under C:Program FilesSAPFrontendBW) or the Excel macro security settings prevent execution of the macros.
Also Check the below link it has some note to follow
RRMX and RRMXP does not open the query and workbook
Regards,
Satya

SAP documentation for working with BExRepositorySheet?

Can someone point me to where I can find some documentation for programmatically working with the BExRepositorySheet, in particular reading from and writing to the embedded XML script within that sheet.
As I wrote in an earlier thread (BEx 7.0 -- SAPBEXqueries hidden sheet gone -- where is the data stored now?), what I'm trying to do is re-program a very elaborate Excel VBA solution we built for BEx 3.5 to automate the processing of BEx reports by reading the stored variable values in the SAPBEXqueries sheet, but with that sheet gone in BEx 7.0 now, and all that meta-data being stored in BExRepositorySheet XML script instead, I need to be pointed in the right direction as to how to work with the BExRepositorySheet in BEx 7.0.
Thank you kindly for any information.

Hi Stephan,
please see link [http://wiki.sdn.sap.com/wiki/display/VC/WhatisWebAPI|http://wiki.sdn.sap.com/wiki/display/VC/WhatisWebAPI] that contains a reference to a 300+ pages PDF document describing the Web API commands. It is describing the ABAP Web Runtime for BW 3.5 which also exists in BW 7.0.
Best regards
Matthias

SAP BW Bex 7.3 Queries not working with Enterprise Portal (EP) 7.3 ABAP stack only

SAP BW Bex 7.3 Queries not working with Enterprise Portal (EP) 7.3 ABAP Stack
Dear Portal Gurus,
we want to integrate SAP BW Bex Queries 7.3 into an Enterprise Portal 7.3 EP ABAP Stack only installation.
1) We have Done SSO between EP And BI System
2) System Object is Created
3) When we trying to create Iview of BEX 7.3 report, its executing that report on BI server, we don't have java stack on BI System
4) We have updated the required table in Bi system for executing the report on EP
5) RFC is OK, System Object Test is OK, Report is working independently from Business Explorer, but not working from EP
There no irj services available on BI system, as it is only ABAP stack.
Can anybody help us in achieving our requirement
Thanks in advance
Michael Wecker

Hi Michael,
To integrate portal with BI you need to perform BI Portal integration steps.
Refer to a document link below for guidance purpose.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0a5216a-349c-2a10-9baf-9d4797349f6a?overridelayout=t…
Ensure that you have performed all these relevant steps.
Hope this helps.
Regards,
Deepak Kori

Work with cumulative KF in the BEx

Hi all,
I have created a cumulative KF in a query. Now, I would like to work with "conditions" (or even "exceptions") on this cumulative KF.
The problem is that "conditions" consider the actual ("internal") value of my KF and not the cumulative ("displayed") one...
Does somebody know how to resolve this issue?
Regards

I have created a CKF based on the Cumulated one. The showed results for this CKF are the non-cumulated values.
So I'm still not able to make any condition or exception on the "cumulated" value.
Maybe there is something I did wrong...?

Crystal Report with Compound Key

Hi,
I have Characteristic with Compound Key in SAP BW 7.0. This Characteristic use to store the Purchase Order Item Line. The Compound Key is the Purchase Order Document.
So I will have the following fields created for this Characteristic:
Compound Key (Purchase Order Document) 5600001982, Purchase Order Item Line 10
I created a Query for this Characteristic and I have the following as result:
10 ...
20 ...
30 ...
All works fine.
Now I created the Crystal Report from this Query. When I display this Characteristic in Crystal Report, I have the following:
5600001982/10
5600001982/20
5600001982/30
Is this a bug or Crystal not support the Compound Key?
Please advise, thank you.

Hello,
Did you get this resolved.
Were you able to display characteristics in Crystal without the compounding characteristic.
Thanks.

Crystal Report and InfoObject with Compound Key

Hi,
I have Characteristic with Compound Key in SAP BW 7.0. This Characteristic use to store the Purchase Order Item Line. The Compound Key is the Purchase Order Document.
So I will have the following fields created for this Characteristic:
Compound Key (Purchase Order Document) 5600001982, Purchase Order Item Line 10
I created a Query for this Characteristic and I have the following as result:
10 ...
20 ...
30 ...
All works fine.
Now I created the Crystal Report from this Query. When I display this Characteristic in Crystal Report, I have the following:
5600001982/10
5600001982/20
5600001982/30
Is this a bug or Crystal not support the Compound Key?
Please advise, thank you.

a

How to working with BI in Visual Composer 7.1

Hi.
I want to work with BeX Query using Visual Composer 7.1
I created BI system in EP System configuration.
http://help.sap.com/saphelp_nwce10/helpdata/en/7e/6dbcea3700452195e3bddaa47c5906/frameset.htm
http://help.sap.com/saphelp_nwce10/helpdata/en/46/081ed5f8685875e10000000a11466f/frameset.htm
But I can only see Web service destination and RFC destination. What shall I do to solve it?
And Why /nwa -> destination is only see in VC?
Help me^^

Hi Kang Min Shim ,
In order to search for BI destinations in VC you must have the BI Kit for VC installed on your machine.
If you have that BI Kit installed you need to [define a BI destination|http://help.sap.com/saphelp_nwce10/helpdata/en/45/c21540edc547f5e10000000a114a6b/content.htm].
I hope it helps,
Udi

Query Designer not working with Aggregation Levels on BW 7.30

Hi,
Every time I try to create a query on top of an Aggregation Level that I created with the new ABAP based RSPLAN transaction.
If somebody can help me out I'd appreciate it.
By the way, we don't have the Java stack, but we are currently using BO4's JVM as we're on ramp up.
This is the error that I get when trying to create the query:
QD Revision 667
ERROR ID: E-ONGUIUNHANDLEDEXCEPTION
And this is the error log:
1:42:13 p.m..319: Info: Query Designer Start. Revision: 667
QDbCommandBase::Execute - Standard View
QDbCommandBase::Execute - Table View
QDbCommandBase::Execute - Rows/Columns
QDbCommandBase::Execute - Cells
QDbCommandBase::Execute - Conditions
QDbCommandBase::Execute - Exceptions
QDbCommandBase::Execute - InfoProvider
QDbCommandBase::Execute - Filter
QDbCommandBase::Execute - Documents
QDbCommandBase::Execute - Where-Used List
QDbCommandBase::Execute - Properties
QDbCommandBase::Execute - Properties
QDbCommandBase::Execute - Messages
QDbCommandManager::ItemClickedHandler - Bar clicked: NewQuery
QDbCommandBase::Execute - New...
QDbCommandBase::Execute - Table View
QDbCommandBase::Execute - Rows/Columns
QDbCommandBase::Execute - Cells
QDbCommandBase::Execute - Conditions
QDbCommandBase::Execute - Exceptions
QDbCommandBase::Execute - InfoProvider
QDbCommandBase::Execute - Filter
QDbCommandBase::Execute - Documents
QDbCommandBase::Execute - Where-Used List
QDbCommandBase::Execute - Messages
QDbCommandBase::Execute - Table View
QDbCommandBase::Execute - Cells
QDbCommandBase::Execute - Conditions
QDbCommandBase::Execute - Exceptions
QDbCommandBase::Execute - Rows/Columns
QDbCommandBase::Execute - Filter
QDbCommandBase::Execute - InfoProvider
QDbCommandBase::Execute - Properties
-EXCEPTION-START- 1:42:52 p.m..416: TRACE EXCEPTION ---
Exception Name: TargetInvocationException
Exception Message: Exception has been thrown by the target of an invocation.
Exception    at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
   at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.PropertyGet(Object iPropertySource, String iPropertyName)
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.ValueGetDefault(Object iPropertySource)
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.pValueDefault()
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.ValueDefault()
   at com.sap.bi.et.QueryDesigner.QDpPropertyBase.ValueResolved()
   at com.sap.bi.et.QueryDesigner.QDpPropertyMulti.SetFirstProperty(QDpPropertyBase iProperty)
   at com.sap.bi.et.QueryDesigner.QDpPropertyMulti.Add(QDpPropertyBase iProperty)
   at com.sap.bi.et.QueryDesigner.QDuPropPageQuery.ToDialog()
   at com.sap.bi.et.QueryDesigner.QDuPropPageBase.ToDialogCore()
   at com.sap.bi.et.QueryDesigner.QDuPropPageBase.set_CommandContext(QDbCommandContext Value)
   at com.sap.bi.et.QueryDesigner.QDuPropPages.EnablePage()
   at com.sap.bi.et.QueryDesigner.QDuPropPages.ContextChangedHandler(Object iSender, QDbCommandContext iCommandContext)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.ContextChangedEventHandler.Invoke(Object iSender, QDbCommandContext iCommandContext)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.OnContextChanged(QDbCommandContext iCommandContext)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CalculateContext(QDcView iViews, QDeAreaType iAreaType)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CalculateContext(QDbElement iElement)
   at com.sap.bi.et.QueryDesigner.QDbCommandPropertiesQuery.ExecuteCommand()
   at com.sap.bi.et.QueryDesigner.QDbCommandBase.Execute()
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.CommandExecute(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.InitialCommandExecute(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.DoExecuteCommandInternal()
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.DoExecuteCommand(QDbCommandBase iCommand)
   at com.sap.bi.et.QueryDesigner.QDbCommandManager.ItemClickedHandler(Object sender, BarItemClickedEventArgs args)
   at com.sap.bi.et.QueryDesigner.QDdEventDispatcher.MenuItemClickedHandler(Object iSender, BarItemClickedEventArgs iE)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarManager.OnItemClicked(BarItemClickedEventArgs args)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarItem.OnItemClicked(EventArgs args)
   at com.sap.bi.et.QueryDesigner.QDiBarItem.OnItemClicked(EventArgs args)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarItem.PerformClick()
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarRenderer.OnMouseUp(MouseEventArgs e)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarControlInternal.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at Syncfusion.Windows.Forms.Tools.XPMenus.BarControlInternal.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Full Stack:   at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
   at com.sap.bi.et.common.appl.Log.Trace.Exception(Exception ex, String iAdditionalInformation)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.OnGuiUnhandledException(Object iSender, ThreadExceptionEventArgs iEventArgs)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDbQueryDesigner.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDStarter.QDStartup.Main()
-EXCEPTION-END----
-CALLING-FROM- 1:42:52 p.m..416: TRACE EXCEPTION ---
   at com.sap.bi.et.common.appl.Log.Debug.WriteTraceToFile(Level lLevel, String lString, Exception ex)
   at com.sap.bi.et.common.appl.Log.Trace.Exception(Exception ex, String iAdditionalInformation)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.OnGuiUnhandledException(Object iSender, ThreadExceptionEventArgs iEventArgs)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)
   at com.sap.bi.et.QueryDesigner.QDbApplicationData.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDbQueryDesigner.Run(Boolean iAsApplication)
   at com.sap.bi.et.QueryDesigner.QDStarter.QDStartup.Main()

Hi,
it seems that you are already using the most recent query designer version. Is your SAPGUI also the most recent version? If yes, open a OSS ticket. If not reinstall the SAPGUI and the BEx tools. I am also working with this query desinger version and I don't have this kind of problem.
Regards,
Gregor

What actions should be taken while working with the quality system

Hi all,
The development phase has been completed, I would like to know what are the steps we need to follow when we are working with the quality system.
I have some doubts regarding this could any one give the inputs please.
1. Where should we create any Roles and Authorizations.Dev/QA/Prd
2. Where should we craete process Chains. Dev/QA/Prd.
3. Can I transport the queries without using Bex transport. What will happen If i dont use the Bex transport.
Thanks in Advance
Regards
Kumar

Hi Kumar,
your BW quality system will be connected to your R/3 Production system from where you'll extract the real time data and do testing which includes estimation of downtime in case of filling up of the set up tables and so on...
the most general procedure is to create the Roles and Authorizations in teh development system and then transport it across to production through your quality system...
Process chains you afford to create it directly in your production system itself... that's no big deal...
And of course, you'll have to transport the queries only using the BEx transport.. there's no other go for this as its the standard procedure given by SAP...
Hope it helps..
Regards
Manick

Working with Compounding infobjects in BEx

Similar Messages

Maybe you are looking for