BI 7.0 Bex Report Designer
Hello All
I would like to know if anyone has any insight into the features of the "Bex Report Designer" scheduled to come as part of BI 7.0
Regards
Rakesh
I suggest you look into the document that was released as part of upcoming features of BW7.0
The design seems exciting but till we have atleast a sneak peek or an eval version no one can say...
SAP any comments on when we can expect an Eval or a Sneak Peek other than PDFs ?
Arun
Similar Messages
-
Bex Report Designer is not previewing changes in QA
Hi All,
Please help... i am getting an unusual problem with bex report designer. I have created a bex report using report designer. This was then transported in to QA. In QA i opened my created report using report designer and clicked the print version button to preview the report in PDF format. This all worked correclty, however i noticed a spelling mistake in one of the custom text fields i am using.
So i put the report in a transport in dev, made the changes in dev and previewed in dev. Everything is ok here and i can see the change i made.
After this i transported the report to QA and when i open the report in report designer to preview the data i can see in design mode that the custom text field does HAVE the change i made so it is correct. The problem i am getting is though when i preview to see in PDF format the image i get is of the old preview with the spelling mistake.
SInce i have made more changes and i can see the changes in DEV and in QA in design mode but when i preview it shows me the old image from the 1st preview.
Please can anyone shed any light into this issue.
Kind regards
ForhadRefreshed the JAVA server resolved issue
-
Bex Report Designer - Large amount of data issue
Hi Experts,
I am trying to execute (on Portal) report made in BEx Report Designer, with about 30 000 pages, and the only thing I am getting is a blank page. Everything works fine at about 3000 pages. Do I need to set something to allow processing such large amount of data?
Regards
VladimirHi Sauro,
I have not seen this behavior, but it has been a while since I tried to send an input schedule that large. I think the last time was on a BPC NW 7.0 SP06 system and it worked OK. If you are on a recent support package, then you should search for relevant notes (none come to mind for me, but searching yourself is always a good idea) and if you don't find one then you should open a support message with SAP, with very specific instructions for recreating the problem from a clean input-schedule.
Good luck,
Ethan -
Error Message in BEx Report Designer 7.0
I am getting the following error message when I try to add a data provider (Query) to BEx Report Designer:
RSBOLAP 017 Java Communication Error: RFC destination NOT_CONFIGURED does not exist
Would anyone be able to provide feedback on what to do?Hi Selva Kumar,
Its a Basis Issue , report to a Basis asministrator about the configuration of Report Designer .
For info refer this link:
https://forums.sdn.sap.com/click.jspa?searchID=21289661&messageID=6734602
Cheers,
Tanish -
Using Report-to-Report Interface (RRI) in BEx Report Designer?
Dear experts,
I would like to know if it is possible to use Report-to-Report Interface in BEx Report Designer?
From what I read from this article
[(Creating Formatted reports using BEx Report Designer)|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00ae5173-6112-2d10-d78f-e7779d269f25?quicklink=index&overridelayout=true], the RRI capability of query is not supported in BEx report. So is it true? And are there any workarounds to enable/emulate RRI capability in BEx Report?
Thanks in advance.
Regards,
JoonHi Joon,
It is possible to make RRI in BEX Report Designer by using Transaction Code - RSBBS .
Here you need to give the Target Query and Source Query names and than you can easily connect two reports or two levels of same report.
For further step wise description please check the below SDN document :
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/607e63d5-b56f-2c10-718f-8e33a08baa89?quicklink=index&overridelayout=true
I hope this document helps to sort out the queries.
Regards,
Akanksha -
Bex Report Designer: Error while loading metadata
hi experts,
I am working with BI7 Bex Report Designer and we are using SP9. when i tried to load the Query in Report Designer its giving below error.
Error while loading metadata.
Check the Query and portal settings.(but the query is working fine in Analyzer).
and its giving message class RSBOLAP, message number 018 and Description is java system error: incoming call is not authorized.
when i double click the error its giving below error details.
Diagnosis
An error occurred in the BI components on the SAP J2EE Engine.
System Response
Procedure
Contact your system administrator to have the error analyzed in detail.
Procedure for System Administration
Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.
could you plz suggest me how to rectify the problem.
regards
vadlamudiHi vadlamudi
The error message RSBOLAP 018 means, that the ABAP stack can't communicate with the Java Stack.
1) Please ensure, that the user, used for the Report Designer, is valid in the Portal too. Depending on the user management setup this means that there either needs to be the same user or an assigned user in the Portal.
2) In case the user is valid, it means a basic misconfiguration according to note 937697. In this case please run the Support Desk Tool and ensure, that all checks are green. Please ensure, that the latest version of the Support Desk Tool is used.
Regards,
Janine -
In BEx Report Designer, I keep getting short dumps and timeouts when trying to design flashy reports.
I keep getting 2 errors when I time out:
1. 'Query (view) definition cannot be retrieved from Portal.
Please try again or check query and Portal Setup!
Time limit exceeded.
2. xxx Error when reading Query (via BICS)
Please check query and Portal setup!
Time limit exceeded.
We are running ECC 6.0, BI2004s, and SEM 6.0. All in Sandbox/Dev environment.
We are NOT running EP.
I am aware that we have some memory issues, and we're adding 4Gb more on Thursday....can the solution be that simple, or are these errors telling me we need Portals installed? I was under the impression that Portals were NOT required for 2004s, so long as you did not use WAD etc.
Any thoughts??You would need to install portals(EP) for the report designer to work. When you design your flashy report in designer and try it launch it... it would try to connect to EP to publish it. It bombs when it doesnt find the portal.
On a personal note: Report designer have a long way to go when you think the output would be something like crystal .. NO not yet ... But SAP just got started ... I think they would be there pretty soon. And they promise many enhancements as of SP 13.. so lets all wait. -
Unable to view report from Bex Report Designer
Hi,
When I log on to Bex Report Designer, I click execute button, it is giving a blank page. It is neither giving any error nor any message. We have recently installed NW2004s and BI Cont 703. Now my problem is how to make report visible in the BEX Report Designer.
Thanks,
SubhaniDear Prakash,
Thanks for the quick reply.
I have religiously followed your Blog. As far as I know any one who wanna setup BEx has to follow this. It is the one place where all the settings related to BEx front end were discussed and disclosed. Thanks a lot for your exemplary attempt.
Though you have mentioned about the .NET frame work I could not understand how it will effect the "insert" menu of BEx report designer. But i have checked that also and its matching with your recommendations.
My question is pretty simple. With sapgui6.40compilation5 with all the latest patches both for gui, BW and BI. Will i get the options of <i>"Report section", "Report section based on Querry"</i>in the <b>"insert"</b> menu of BEx report designer.
The mentioned options <i>"Report section", "Report section based on Querry"</i> were shown in the webnair of BEx report designer. Pls check the link:
(As per the SDN these menu items should be available in BEx report designer..Pls observe the Insert menu in the very first few seconds)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9c059b57-0701-0010-3283-e5e8669f827e
We have installed and upgraded the system to spstack 8 and done all the settings. Our front end is also updated with the service packs. But we could not get those options. If you can give me your mail id i can send you the screen shots.
Thanks & Regards,
Sridharb -
Hi,
When am trying open Query in BEx report designer it is getting below error plz help me to solve this issue.
error while loading query metadata check the wuery and portal settings
RSBOLAP 017 Java communication error : RFC destination NOT_CONFIGURD Does not exist
Thanks,
Medha.Hi Medha
this is due to two reaso
1 For the system IP there should be open a port
2 May be its a authorization problem check this object is added or not S_RFC
Shashi.. -
Bex Report designer is not working,
Hi all,
We have BI dual stack and we trying to activate Bex front end , i am able to execute Query designer but when i am opening report designer and trying to load any infocube i am getting Run time Java :.SS0 error.
SSO is configured and betweeb Java and ABAP and ABAP and JAVA....
Please suggest what i am missing...
Default trace Log is as below>.....
#1.5#0017A451D046001A0000000D0000A3A8000452DD2FB57056#1217009848502#com.sap.ip.bi.base.service.localization.impl.BIResourceAccessor#sap.com/irj#com.sap.ip.bi.base.service.localization.impl.BIResourceAccessor#J2EE_ADMIN#101##NBCDSSQLS10.corp_SBW_24896250#J2EE_ADMIN#cf85f8805a7511dd987b0017a451d046#SAPEngine_Application_Thread[impl:3]_25##0#0#Error#1#/Applications/BI#Plain###Missing resource: "com.sap.ip.bi.bics.exceptions.localization" "en" "InvalidVariableValues"#
#1.5#0017A451D046001A0000000E0000A3A8000452DD2FB5C854#1217009848522#com.sap.ip.bi.bics.exceptions.BicsBaseRuntimeException#sap.com/irj#com.sap.ip.bi.bics.exceptions.BicsBaseRuntimeException#J2EE_ADMIN#101##NBCDSSQLS10.corp_SBW_24896250#J2EE_ADMIN#cf85f8805a7511dd987b0017a451d046#SAPEngine_Application_Thread[impl:3]_25##0#0#Fatal#1#/Applications/BI/BI Consumer Services#Plain###Exception thrown: com.sap.ip.bi.bics.dataaccess.resource.impl.bi.exceptions.BicsResourceBwRuntimeException:
com.sap.ip.bi.bics.dataaccess.resource.impl.bi.exceptions.BicsResourceBwRuntimeException:
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.initializeState(ProviderSelectionObject.java:497)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.queryview.ProviderQueryView.initializeState(ProviderQueryView.java:95)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.hasDefaultView(ProviderSelectionObject.java:990)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.initializeState(SelectionObject.java:361)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView.initializeState(QueryView.java:169)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.getSelectionState(SelectionObject.java:532)
at com.sap.ip.bi.webapplications.ui.items.filteritems.dropdown.DropDownItem.unlinkDataprovider(DropDownItem.java:153)
at com.sap.ip.bi.webapplications.ui.items.dataprovider.SelectorReferenceItem.doUiItemDestroy(SelectorReferenceItem.java:91)
at com.sap.ip.bi.webapplications.ui.items.filteritems.dropdown.DropDownItem.doUiItemDestroy(DropDownItem.java:497)
at com.sap.ip.bi.webapplications.ui.items.UiItem.doDestroy(UiItem.java:233)
at com.sap.ip.bi.webapplications.runtime.base.PageObject.destroy(PageObject.java:390)
at com.sap.ip.bi.webapplications.runtime.base.Container.destroy(Container.java:53)
at com.sap.ip.bi.webapplications.runtime.impl.Page.destroyPageObject(Page.java:2734)
at com.sap.ip.bi.webapplications.runtime.impl.Page.doDestroyItemCommand(Page.java:3237)
at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:90)
at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:339)
at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:273)
at com.sap.ip.bi.webapplications.runtime.base.CommunicationProcessor.processCommand(CommunicationProcessor.java:144)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommand(Page.java:1207)
at com.sap.ip.bi.webapplications.runtime.template.TemplateAssembler.destroy(TemplateAssembler.java:655)
at com.sap.ip.bi.webapplications.runtime.base.Template.doDestroy(Template.java:162)
at com.sap.ip.bi.webapplications.runtime.base.PageObject.destroy(PageObject.java:390)
at com.sap.ip.bi.webapplications.runtime.base.Container.destroy(Container.java:53)
at com.sap.ip.bi.webapplications.runtime.impl.Page.destroyPageObject(Page.java:2734)
at com.sap.ip.bi.webapplications.runtime.impl.Page.destroy(Page.java:4217)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.destroyPage(Controller.java:603)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:320)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#0017A451D046001A000000110000A3A8000452DD2FB65C1C#1217009848562#com.sap.ip.bi.base.application.message.impl.MessageBase#sap.com/irj#com.sap.ip.bi.base.application.message.impl.MessageBase#J2EE_ADMIN#101##NBCDSSQLS10.corp_SBW_24896250#J2EE_ADMIN#cf85f8805a7511dd987b0017a451d046#SAPEngine_Application_Thread[impl:3]_25##0#0#Error#1#/Applications/BI#Plain###A message was generated:
ERROR
com.sap.ip.bi.bics.exceptions.BicsBaseRuntimeException InvalidVariableValues
Log ID: 0017A451D046001A0000000E0000A3A8000452DD2FB5C854
Message:
Stack trace: com.sap.ip.bi.bics.dataaccess.resource.impl.bi.exceptions.BicsResourceBwRuntimeException:
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.initializeState(ProviderSelectionObject.java:497)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.queryview.ProviderQueryView.initializeState(ProviderQueryView.java:95)
at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.hasDefaultView(ProviderSelectionObject.java:990)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.initializeState(SelectionObject.java:361)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView.initializeState(QueryView.java:169)
at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.getSelectionState(SelectionObject.java:532)
at com.sap.ip.bi.webapplications.ui.items.filteritems.dropdown.DropDownItem.unlinkDataprovider(DropDownItem.java:153)
at com.sap.ip.bi.webapplications.ui.items.dataprovider.SelectorReferenceItem.doUiItemDestroy(SelectorReferenceItem.java:91)
at com.sap.ip.bi.webapplications.ui.items.filteritems.dropdown.DropDownItem.doUiItemDestroy(DropDownItem.java:497)
at com.sap.ip.bi.webapplications.ui.items.UiItem.doDestroy(UiItem.java:233)
at com.sap.ip.bi.webapplications.runtime.base.PageObject.destroy(PageObject.java:390)
at com.sap.ip.bi.webapplications.runtime.base.Container.destroy(Container.java:53)
at com.sap.ip.bi.webapplications.runtime.impl.Page.destroyPageObject(Page.java:2734)
at com.sap.ip.bi.webapplications.runtime.impl.Page.doDestroyItemCommand(Page.java:3237)
at sun.reflect.GeneratedMethodAccessor260.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:90)
at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:339)
at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:273)
at com.sap.ip.bi.webapplications.runtime.base.CommunicationProcessor.processCommand(CommunicationProcessor.java:144)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommand(Page.java:1207)
at com.sap.ip.bi.webapplications.runtime.template.TemplateAssembler.destroy(TemplateAssembler.java:655)
at com.sap.ip.bi.webapplications.runtime.base.Template.doDestroy(Template.java:162)
at com.sap.ip.bi.webapplications.runtime.base.PageObject.destroy(PageObject.java:390)
at com.sap.ip.bi.webapplications.runtime.base.Container.destroy(Container.java:53)
at com.sap.ip.bi.webapplications.runtime.impl.Page.destroyPageObject(Page.java:2734)
at com.sap.ip.bi.webapplications.runtime.impl.Page.destroy(Page.java:4217)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.destroyPage(Controller.java:603)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:320)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
com.sap.ip.bi.bics.exceptions.BicsBaseRuntimeException InvalidVariableValues#
#1.5#0017A451D046001B000000000000A3A8000452DD308F89C6#1217009862791#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##SBW#XSGADDE #EA755ADDD4E4F19E947A0017A451D046#SAPEngine_Application_Thread[impl:3]_11##0#0#Error##Plain###com.sap.engine.services.security.exceptions.BaseLoginException: Authentication failed.#
#1.5#0017A451D046001B000000010000A3A8000452DD308F8B44#1217009862791#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##SBW#XSGADDE #EA755ADDD4E4F19E947A0017A451D046#SAPEngine_Application_Thread[impl:3]_11##0#0#Error##Plain###com.sap.engine.services.security.exceptions.BaseLoginException: Authentication failed.
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:170)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:177)
at com.sap.engine.system.SystemLoginModule.login(SystemLoginModule.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:675)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:129)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:610)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:607)
at javax.security.auth.login.LoginContext.login(LoginContext.java:534)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:70)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.security.core.server.jaas.DetailedLoginException: Authentication failed: Issuer of SAP Logon Ticket is not trusted. Authentication stack: evaluate_assertion_ticket
at com.sap.engine.services.security.login.ModulesProcessAction.run(ModulesProcessAction.java:167)
... 26 more
#1.5#0017A451D046001B000000030000A3A8000452DD308F952F#1217009862801#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##SBW#XSGADDE #EA755ADDD4E4F19E947A0017A451D046#SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#/System/Server#Plain###call FM BICS_CONS_GET_VIEW_DEF_J_PROXY to ProgId SBW_PORTAL on host NBCDSSQLS10 with SSO not authorized: Authentication failed.#
#1.5#0017A451D046001B000000040000A3A8000452DD308F996C#1217009862801#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##SBW#XSGADDE #EA755ADDD4E4F19E947A0017A451D046#SAPEngine_Application_Thread[impl:3]_11##0#0#Error##Plain###java.lang.RuntimeException: call FM BICS_CONS_GET_VIEW_DEF_J_PROXY to ProgId SBW_PORTAL on host NBCDSSQLS10 with SSO not authorized: Authentication failed.#
#1.5#0017A451D046001B000000050000A3A8000452DD308F9A9C#1217009862801#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##SBW#XSGADDE #EA755ADDD4E4F19E947A0017A451D046#SAPEngine_Application_Thread[impl:3]_11##0#0#Error##Plain###java.lang.RuntimeException: call FM BICS_CONS_GET_VIEW_DEF_J_PROXY to ProgId SBW_PORTAL on host NBCDSSQLS10 with SSO not authorized: Authentication failed.
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:79)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanks,
Subhash.GHi All,
We set the Tracelevel to 10 in VA at JCo and below is the trace info:
SYSTEMS: 0 row(s)
UCLASSSYS: 0 row(s)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:434]: [JAV-LAYER] Record() [>>> 375f1617]
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:434]: [JAV-LAYER] Record() [>>> 43a35c67]
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: [JAV-LAYER] setDsrPassport for connection with handle 1 [enter]
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: [JAV-LAYER] com.sap.mw.jco.JCO$Exception: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: [JAV-LAYER] JCO.Client.beginCall(): cannot get jDSR passport for call 'SUSR_GET_ADMIN_USER_LOGIN_INFO', because of com.sap.mw.jco.JCO$Exception: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: [JAV-LAYER] JCO.Client.execute (SUSR_GET_ADMIN_USER_LOGIN_INFO) on handle [1]
Input:
INPUT (uc)
ALIASNAME - CHAR 0 40 0 80 ioASU
AUTHORITY_CHECK - CHAR 40 1 80 2 ioA
USERID - CHAR 41 12 82 24 ioA
content:
00000000
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000020
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000040
0058004A003200450045 005F00410044004D0049 004E00200020
XJ2EE_ADMIN
Input tables: null
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Executing SUSR_GET_ADMIN_USER_LOGIN_INFO for handle 1
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Execute before RfcCall(1, SUSR_GET_ADMIN_USER_LOGIN_INFO, 2, null, null)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Sent Parameter AUTHORITY_CHECK
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Sent Parameter USERID
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Execute after RfcCall(1, SUSR_GET_ADMIN_USER_LOGIN_INFO, 2, null, null)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Execute before RfcReceive(1, SUSR_GET_ADMIN_USER_LOGIN_INFO, 4, null, null)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Expecting Parameter LAST_LOGON_DATE
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Expecting Parameter LOCK_STATUS
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Expecting Parameter PASSWORD_STATUS
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Expecting Parameter USER_ID
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Execute after RfcReceive(1, SUSR_GET_ADMIN_USER_LOGIN_INFO, 4, null, null)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: [JAV-LAYER] JCO.Client.execute (SUSR_GET_ADMIN_USER_LOGIN_INFO) on handle [1] returns after 0 ms
Output:
OUTPUT (uc)
LAST_LOGON_DATE - DATE 0 8 0 16 eA
LOCK_STATUS - INT1 8 1 16 1 eA
PASSWORD_STATUS - INT 9 2 17 4 eA
USER_ID - CHAR 11 12 21 24 eA
content:
00000000
00320030003000380030 0037003200370000FFFF FFFE004A003200450045 005F00410044004D0049
20080727...J2EE_ADMI
00000020
004E00200020
N
Output tables: null
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: [JAV-LAYER] JCO.Pool.releaseClient([1]) in pool com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy_1217213625244_1
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:444]: Reset before RfcCleanupContext(1)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:454]: Reset after RfcCleanupContext(1)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:454]: [JAV-LAYER] Record() [>>> 1a0790e2]
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:454]: [JAV-LAYER] Record() [>>> 66b8f2c7]
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:454]: [JAV-LAYER] JCO.Pool.getClient(false) from pool com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy_1217213625244_1 [enter]
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:454]: [JAV-LAYER] JCO.Pool.getClient(false) returns [1] [leave]
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:454]: [JAV-LAYER] setDsrPassport for connection with handle 1 [enter]
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:454]: [JAV-LAYER] com.sap.mw.jco.JCO$Exception: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:454]: [JAV-LAYER] JCO.Client.beginCall(): cannot get jDSR passport for call 'SUSR_CHECK_LOGON_DATA', because of com.sap.mw.jco.JCO$Exception: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:454]: [JAV-LAYER] JCO.Client.execute (SUSR_CHECK_LOGON_DATA) on handle [1]
Input:
INPUT (uc)
ALIASNAME - CHAR 0 40 0 80 ioASU
AUTH_DATA - STRING 40 0 80 8 ioASU
AUTH_METHOD - CHAR 40 1 88 2 iA
EXTID_TYPE - CHAR 41 2 90 4 ioASU
LANGUAGE - CHAR 43 2 94 4 ioASU
PASSWORD - CHAR 45 40 98 80 ioA
USERID - CHAR 85 12 178 24 ioA
USE_NEW_EXCEPTION - INT1 97 1 202 1 ioA
content:
00000000
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000020
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000040
00500020002000200020 00730031006400330044 00300030007200200020 00200020002000200020
P s1d3D00r
00000060
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000080
00200020002000200020 004A003200450045005F 00410044004D0049004E 002000200100
J2EE_ADMIN Ā
AUTH_DATA: null
Input tables: null
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Executing SUSR_CHECK_LOGON_DATA for handle 1
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Execute before RfcCall(1, SUSR_CHECK_LOGON_DATA, 4, null, null)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Sent Parameter AUTH_METHOD
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Sent Parameter PASSWORD
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Sent Parameter USERID
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Sent Parameter USE_NEW_EXCEPTION
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Execute after RfcCall(1, SUSR_CHECK_LOGON_DATA, 4, null, null)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Execute before RfcReceive(1, SUSR_CHECK_LOGON_DATA, 5, null, null)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Expecting Parameter ALLOW_PWD_DELETION
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Expecting Parameter PWDSTATE
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Expecting Parameter PWD_CHANGE_SSO
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Expecting Parameter TICKET
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:464]: Expecting Parameter USER_ID
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:474]: Execute after RfcReceive(1, SUSR_CHECK_LOGON_DATA, 5, null, null)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:474]: [JAV-LAYER] JCO.Client.execute (SUSR_CHECK_LOGON_DATA) on handle [1] returns after 20 ms
Output:
OUTPUT (uc)
ALLOW_PWD_DELETION - CHAR 0 1 0 2 eA
PWDSTATE - INT 1 2 2 4 eA
PWD_CHANGE_SSO - INT1 3 1 6 1 eA
TICKET - STRING 4 0 7 8 eA
USER_ID - CHAR 4 12 15 24 eA
content:
00000000
0020FFFFFFFE0100004A 003200450045005F0041 0044004D0049004E0020 0020
..ĀJ2EE_ADMIN
TICKET:
Output tables: null
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:474]: [JAV-LAYER] JCO.Pool.releaseClient([1]) in pool com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy_1217213625244_1
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:474]: Reset before RfcCleanupContext(1)
SAPEngine_Application_Thread[impl:3]_27 [20:10:48:474]: Reset after RfcCleanupContext(1)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:954]: [JAV-LAYER] Record() [>>> 31ebb3fb]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:954]: [JAV-LAYER] Record() [>>> 69753d57]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:954]: [JAV-LAYER] Record() [>>> 100e50d8]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:954]: [JAV-LAYER] JCO.Pool.getClient(false) from pool com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy_1217213625244_1 [enter]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:954]: [JAV-LAYER] JCO.Pool.getClient(false) returns [1] [leave]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:954]: [JAV-LAYER] setDsrPassport for connection with handle 1 [enter]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:954]: [JAV-LAYER] com.sap.mw.jco.JCO$Exception: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:964]: [JAV-LAYER] JCO.Client.beginCall(): cannot get jDSR passport for call 'BAPI_USER_EXISTENCE_CHECK', because of com.sap.mw.jco.JCO$Exception: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:964]: [JAV-LAYER] JCO.Client.execute (BAPI_USER_EXISTENCE_CHECK) on handle [1]
Input:
INPUT (uc)
USERNAME BAPIRET2 CHAR 0 12 0 24 iA
content:
00000000
004A003200450045005F 00410044004D0049004E 00200020
J2EE_ADMIN
Input tables: null
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:964]: Executing BAPI_USER_EXISTENCE_CHECK for handle 1
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:964]: Execute before RfcCall(1, BAPI_USER_EXISTENCE_CHECK, 1, null, null)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:964]: Sent Parameter USERNAME
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:964]: Execute after RfcCall(1, BAPI_USER_EXISTENCE_CHECK, 1, null, null)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:964]: Execute before RfcReceive(1, BAPI_USER_EXISTENCE_CHECK, 1, null, null)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:964]: Expecting Parameter RETURN
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:974]: Execute after RfcReceive(1, BAPI_USER_EXISTENCE_CHECK, 1, null, null)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:974]: [JAV-LAYER] JCO.Client.execute (BAPI_USER_EXISTENCE_CHECK) on handle [1] returns after 20 ms
Output:
OUTPUT (uc)
RETURN BAPIRET2 STRUCTURE 0 0 0 6 eA
BAPIRET2 (uc)
TYPE - CHAR 0 1 0 2 A
ID - CHAR 1 20 2 40 A
NUMBER - NUM 21 3 42 6 A
MESSAGE - CHAR 24 220 48 440 A
LOG_NO - CHAR 244 20 488 40 A
LOG_MSG_NO - NUM 264 6 528 12 A
MESSAGE_V1 - CHAR 270 50 540 100 A
MESSAGE_V2 - CHAR 320 50 640 100 A
MESSAGE_V3 - CHAR 370 50 740 100 A
MESSAGE_V4 - CHAR 420 50 840 100 A
PARAMETER - CHAR 470 32 940 64 A
ROW - INT 502 2 1004 4 A
FIELD - CHAR 504 30 1008 60 A
SYSTEM - CHAR 534 10 1068 20 A
RETURN:
00000000
00490030003100200020 00200020002000200020 00200020002000200020 00200020002000200020
I01
00000020
00200030003800380055 0073006500720020004A 003200450045005F0041 0044004D0049004E0020
088User J2EE_ADMIN
00000040
00650078006900730074 00730020002000200020 00200020002000200020 00200020002000200020
exists
00000060
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000080
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000100
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000120
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000140
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000160
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000180
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000200
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000220
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000240
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000260
00200020002000200030 00300030003000300030 004A003200450045005F 00410044004D0049004E
000000J2EE_ADMIN
00000280
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000300
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000320
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000340
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000360
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000380
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000400
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000420
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000440
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000460
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000480
00200020002000200020 00200020002000200020 00200020002000200020 00200020002000200020
00000500
00200020000000000020 00200020002000200020 00200020002000200020 00200020002000200020
00000520
00200020002000200020 00200020002000200020 00200020002000200053 004200570043004C004E
SBWCLN
00000540
0054003200300030
T200
Output tables: null
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:974]: [JAV-LAYER] JCO.Pool.releaseClient([1]) in pool com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy_1217213625244_1
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:974]: Reset before RfcCleanupContext(1)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:974]: Reset after RfcCleanupContext(1)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] Record() [>>> 44f54d22]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] Record() [>>> 449b168c]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] Record() [>>> 21e56484]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] Record() [>>> 5b2a277e]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] JCO.Pool.getClient(false) from pool com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy_1217213625244_1 [enter]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] JCO.Pool.getClient(false) returns [1] [leave]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] setDsrPassport for connection with handle 1 [enter]
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] com.sap.mw.jco.JCO$Exception: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] JCO.Client.beginCall(): cannot get jDSR passport for call 'PRGN_J2EE_USER_GET_ROLENAMES', because of com.sap.mw.jco.JCO$Exception: (152) JCO_ERROR_DSR_PASSPORT_NOT_VALID: Dsr passport is not valid.
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: [JAV-LAYER] JCO.Client.execute (PRGN_J2EE_USER_GET_ROLENAMES) on handle [1]
Input:
INPUT (uc)
IF_REPLACE_DERIVED - CHAR 0 1 0 2 iASU
IF_UNAME - CHAR 1 12 2 24 iA
content:
00000000
0020004A003200450045 005F00410044004D0049 004E00200020
J2EE_ADMIN
Input tables:
TABLES (uc)
ET_AGR J2EE_AGRNAME TABLE 0 0 0 6 AU
ET_RETURN BAPIRET2 TABLE 0 0 6 9 AU
J2EE_AGRNAME (uc)
AGR_NAME - CHAR 0 30 0 60 A
BAPIRET2 (uc)
TYPE - CHAR 0 1 0 2 A
ID - CHAR 1 20 2 40 A
NUMBER - NUM 21 3 42 6 A
MESSAGE - CHAR 24 220 48 440 A
LOG_NO - CHAR 244 20 488 40 A
LOG_MSG_NO - NUM 264 6 528 12 A
MESSAGE_V1 - CHAR 270 50 540 100 A
MESSAGE_V2 - CHAR 320 50 640 100 A
MESSAGE_V3 - CHAR 370 50 740 100 A
MESSAGE_V4 - CHAR 420 50 840 100 A
PARAMETER - CHAR 470 32 940 64 A
ROW - INT 502 2 1004 4 A
FIELD - CHAR 504 30 1008 60 A
SYSTEM - CHAR 534 10 1068 20 A
ET_AGR: 0 row(s)
ET_RETURN: 0 row(s)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: Executing PRGN_J2EE_USER_GET_ROLENAMES for handle 1
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: Execute before RfcCall(1, PRGN_J2EE_USER_GET_ROLENAMES, 1, null, 2)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: Sent Parameter IF_UNAME
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:984]: Sent Table ET_AGR
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:994]: Sent Table ET_RETURN
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:994]: Execute after RfcCall(1, PRGN_J2EE_USER_GET_ROLENAMES, 1, null, 2)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:994]: Execute before RfcReceive(1, PRGN_J2EE_USER_GET_ROLENAMES, null, null, 2)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:994]: Expecting Table ET_AGR
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:994]: Expecting Table ET_RETURN
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:994]: Execute after RfcReceive(1, PRGN_J2EE_USER_GET_ROLENAMES, null, null, 2)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:994]: [JAV-LAYER] JCO.Client.execute (PRGN_J2EE_USER_GET_ROLENAMES) on handle [1] returns after 10 ms
Output: null
Output tables:
TABLES (uc)
ET_AGR J2EE_AGRNAME TABLE 0 0 0 6 AU
ET_RETURN BAPIRET2 TABLE 0 0 6 9 AU
J2EE_AGRNAME (uc)
AGR_NAME - CHAR 0 30 0 60 A
BAPIRET2 (uc)
TYPE - CHAR 0 1 0 2 A
ID - CHAR 1 20 2 40 A
NUMBER - NUM 21 3 42 6 A
MESSAGE - CHAR 24 220 48 440 A
LOG_NO - CHAR 244 20 488 40 A
LOG_MSG_NO - NUM 264 6 528 12 A
MESSAGE_V1 - CHAR 270 50 540 100 A
MESSAGE_V2 - CHAR 320 50 640 100 A
MESSAGE_V3 - CHAR 370 50 740 100 A
MESSAGE_V4 - CHAR 420 50 840 100 A
PARAMETER - CHAR 470 32 940 64 A
ROW - INT 502 2 1004 4 A
FIELD - CHAR 504 30 1008 60 A
SYSTEM - CHAR 534 10 1068 20 A
ET_AGR: 4 row(s)
row 0
00000000
005300410050005F0042 0043005F004200410053 00490053005F00410044 004D0049004E00200020
SAP_BC_BASIS_ADMIN
00000020
00200020002000200020 00200020002000200020
row 1
00000000
005300410050005F0042 0043005F004200410053 00490053005F004D004F 004E00490054004F0052
SAP_BC_BASIS_MONITOR
00000020
0049004E004700200020 00200020002000200020
ING
row 2
00000000
005300410050005F0042 0043005F004A00530046 005F0043004F004D004D 0055004E004900430041
SAP_BC_JSF_COMMUNICA
00000020
00540049004F004E005F 0052004F002000200020
TION_RO
row 3
00000000
005300410050005F004A 003200450045005F0041 0044004D0049004E0020 00200020002000200020
SAP_J2EE_ADMIN
00000020
00200020002000200020 00200020002000200020
ET_RETURN: 0 row(s)
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:994]: [JAV-LAYER] JCO.Pool.releaseClient([1]) in pool com.sap.security.core.persistence.datasource.imp.r3persistence.R3JCo640Proxy_1217213625244_1
SAPEngine_Application_Thread[impl:3]_0 [20:10:48:994]: Reset before RfcCleanupContext(1)
SAPEngine_Application_Thread[impl:3]_0 [20:10:49:004]: Reset after RfcCleanupContext(1)
JCoRequestDispatcher [20:10:50:104]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:10:50:104]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:10:53:723]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:10:53:723]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:10:55:723]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:10:55:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:10:57:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:10:57:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:10:59:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:10:59:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:01:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:01:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:03:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:03:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:05:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:05:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:07:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:07:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:09:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:09:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:11:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:11:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:13:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:13:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:15:733]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:15:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:17:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:17:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:19:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:19:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:21:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:21:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:23:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:23:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
JCoRequestDispatcher [20:11:25:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) = RC_RETRY_LISTEN leave
JCoRequestDispatcher [20:11:25:743]: [JAV-LAYER] Dispatcher.waitForRequest(2000) enter
SAPEngine_Application_Thread[impl:3]_38 [20:11:26:593]: [JAV-LAYER] JCO.setProperty(jco.trace_level, 0)
at com.sap.mw.jco.JCO.setProperty(JCO.java:464)
at com.sap.mw.jco.JCO.setTraceLevel(JCO.java:633)
at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.setStaticProperties(RFCRuntimeInterfaceImpl.java:1354)
at com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.changeBundleConfiguration(RFCRuntimeInterfaceImpl.java:654)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Please suggest..
Thanks,
Subhash.G -
Which CTC template needs to be run for Bex Reporting Designer
Hi,
In our BW system I do not see any "Bex Web reporting Designer",.
Which CTC Template I do need to rung to in istall Bex Web Reporting Designer"
Thanks for help
sahmadHi,
To ensure BI Java is configured correctly and completely, please do the following:
1. Always use the CTC Template for BI Java for configuration (check SAP NetWeaver 2004s Masterguide available at http:/service.sap.com/instguides for details). Manual configuration or configuration via report RSPOR_SETUP should not be done for SAP NetWeaver 2004s.
2. To ensure a smooth configuration process, make sure that you have deployed the very latest patch from SAP Service Marketplace at http://service.sap.com/swdc for CTC Template for BI Java.
3. To avoid encountering already known issues within the area of BI Java itself, make sure to deploy the latest patches for SCAs BI-BASE-S and BIWEBAPP.
4. Read note 983156 ('BI configuration w. Template Installer') and ake sure the necessary prerequisites are given on the ABAP side. Ensure that you have installed the latest LM Tools.
5. After running the CTC Template for BI Java, run SAP NetWeaver BI Diagnostics & Support Desk Tool as described in note 937697 to verify your installation. In the "Advanced mode" of the tool, go to the "Configuration checks" tab and check for potential red traffic lights. To resolve the issues shown there, check the "Remedy" column and follow the instructions given there.
6. The overall process is described in more detail in note 917950 ('SAP NetWeaver 2004s: Setting up BEx Web'). Make sure to go through the note and also have a look at the document WDEBU7_Setting_up_BEx_Web.zip attached to that note, showing the overall process in a set of slides with screenshots.
Kind Regards,
Marcio -
Error message in BEx Report Designer
Hello,
I get an error message when I try to add a data provider in Report Designer
It says:
"Error when loading query metadata
Check the query and portal settings"
I can see no reason why my query should not appear in my report.
Has anyone seen a similar thing before?
With regards
KristianHi,
There is a reason for that. RD uses Java BICS service for getting the query meta data. This means that the request has to be processed in Java.
This error appears when Java server is not properly configured. The note 937697 will help you to check and correct the configuration of ABAP - Java connection.
With the note 989525 you can simply check the connection (it will be broken in your system). Points 4 - 7 are describing the check directly in ABAP.
Regards, Karol Kalisz
SAP NetWeaver BI Development -
when i try to insert a query i get this error:
This report desinger does not support this query dridown column axis may contain one structure only, remove any additional dimensions.
The report design is :
columns:
fiscal year/period
kf1
kf2
ck1
ck2
Rows:
Structure: liquidity items
Free charac:
sem_creation date
liqudity item
Note: The values of liqudity are used in the structure.
so i do have two structure. so due to the above error its allowing me to insert the query in report desinger.thanks a lot.
so what i udnerstand is that because we using a char. and key fig in columns we are not able of insert the query that being a drawback of the report desinger.
i need to insert space in the column:
Say i want the output to be
Receipts
SSfunds
ss payables
ss stands for sapce. so that the structure should like a hiearchy. -
Hi Experts,
There is a requirement for a report, where we need to show data for material sales from 2004 to 2014.
The report should contain
Material name, Material Type (FERT finished product) and Material Group with
sales keyfig. The data wanted to be displayed has to be from VBRP and VBRK table.
I want an assistance here to go step by step in creating this report.
As tables involved are VBRP standard datasources must be 2LIS_13_VDHDR
and for table VBRK standard Datasource must be 2LIS_13_VDITM
Now whats next. There are already many cubes and ODS and Zobjects as well built in the system and with different purpose.
Should it be wise to create a new flow with all new datastores and finally building the report. Please assist in step by step solutionHi Aparajit,
Let me share some design principles:
Do not create for every report a new data flow and new InfoProviders;
Look for existing InfoProviders and data flows (in the same business process area) which might cover the information requirements and enhance them if that makes sense;
Distinguish between Data Warehouse data flows and DataMart data flows, the first ones should be as generic and reusable as possible (no filtering, no aggregation and no business rules) - "extract once, deploy many";
If you have to create a new data flow, then always refer to the Business Content and take that as a starting point.
In your case check first if the DataSources 2LIS_13_VDHDR (sales header - main table is VBAK) and 2LIS_13_VDITM (sales item - main table is VBAP) are already available. If not, then I suggest to start with 2LIS_13_VDITM since this DataSource also contains information from other sales tables.
If you miss particular fields, then do not forget to look in the Logistic Cockpit (t/code LBWE). It is possible to extend the communication structure with the available fields.
Last remark on the required history of 10 years of data, is this really necessary? If yes, is the data still available in the ECC source system (i.e. no archiving took place yet)?
I hope that this will help you further.
Best regards,
Sander -
Hi all,
I have two questions when I run BEx Report Designer:
1. For InfoProvider or query with Chinese characters, I can't insert Data Provider into Report Designer. The error message is "Server does not return query metadata Check the query". For English-based InfoProvider or query it works.
2. When I insert a query into Report Designer and execute it, it pops up another error message as following:
<b>Version number of report is too high
This report Web item can display reports with version number 2.1 or lower. This report has version number 2.2
To display this report, use a newer version of the report Web item
Contact your system administrator. This error was recorded</i> </b>
The BW is version 7.0 with SP12 and the BEx is SP12 with Patch1. Please help on these issues if you have any idea. Thanks very much.Please check the deployment of BI Java.
The message corresponds to a Report Item of NW 2004s SPS 9.
Reports with Version 2.2 can be processed by Report Item SPS 10 and higher.
Report Designer checks the BI SP number (ABAP). You have to make sure
the BW server and the Portal are in sync regarding the SPS. I assume the BI SP was 10 or 11 when the Report was saved. However the Portal was not upgraded when the Report was run.
NW 2004s SPS 12 = BI Java SPS 12, BI ABAP SP 13/14
NW 2004s SPS 11 = BI Java SPS 11, BI ABAP SP 12
NW 2004s SPS 10 = BI Java SPS 10, BI ABAP SP 10/11
hope this helps, akrim
Maybe you are looking for
-
Enterprise Business Services and Oracle Service Bus
Hi, We are using AIA and we have developed a number of EBS'. These are composite applications containing a mediator and are deployed to the SOA Server. Am I right in saying that another option is to use the Oracle Service Bus and replace the composit
-
I can't open a file in OS 922 that was created in OS X.
The web-pages I downloaded while in OS X (and stored in the HD) appear blank, (white, no logo) when I am booted in OS 922. When I try to open them, I receive a message "Sorry, could not open because the application that created it could not be found"
-
String path = ""; path = "cmd /c start FCall.bat"; Runtime rt = Runtime.getRuntime(); Process proc = rt.exec(path); //proc.destroy() ; The code works fine, however, I need some help in exiting the command window. After executing the batch file the wi
-
Airport extreme status in menu
This does not seem to affect the connection but the status bar and the time connected slides back and forth in the menu when the time disappears for about one second. It is only disturbing because it catches my eye when this happens and causes me to
-
I have been trying to find who services my area for landline internet. Every time I try to type in my address into the website the data base has no idea where my address is but this is the same issue with all the other isp databases so I think the ad