BSP callable object failed to display

Hi, experts,
I created a simple gp process with one action, using BSP as the callable object,
the bsp CO will call a bsp application delivered by sap, but when i tried to execute it in runtime, it alway comeup with errors, could you pls help me?
this is our prototype for more GP process, we want to integrate bsp applications.
pls see attachment
1. simple gp process
http://www.saphrfans.com/forum/files/step5_193.jpg
2. all role assigned
http://www.saphrfans.com/forum/files/step7_188.jpg
3. failed to run
http://www.saphrfans.com/forum/files/step9_error_285.jpg

Hi rene,
the error message is on the last screenshot.
while trying to execute the process in runtime, i got the message:
bsp callable object could not be executed
it's quite a simple gp process with only one action item, and all the roles
has been set to myself
anything wrong here?
jun

Similar Messages

WHICH object failed to display?

I'm experiencing a tough, frustrating problem. I've used a SVG turbulence filter to create nice-looking Gullies on a boardgame map. There are dozens of them, and Illustrator reported no problems when they were being drawn. After drawing, I verified that they looked good at 300dpi, then changed my resolution back to 18dpi so that Illustrator wouldn't slow down displaying them while I was working on other things.
However, when I open the document, Illustrator gives me an error message to the effect of "An object failed to display". (Sorry, I don't have it in front of me - will get the exact error message later). All I can do is click OK. And immediately, the same error message pops up. Click OK. Same error message pops up. Dozens of times - I stopped counting when I hit 100.
I want to find out what objects are causing the problem. I suspect it's one of those Gullies that use SVG filters, but that's all I have - suspicions.
If anyone has tips on working with SVG turbulence filters, great, but what I really want to know is more basic - what do you people do when Illustrator reports a problem displaying an object, but it doesn't tell you which object? Particularly when there was no problem creating the object - it's not like I can say, "OK, that didn't work, try something else." Instead I'm saying, "Hmm. Something I did in my last drawing session is causing a problem. Now what?"
I'm not complaining (although yeah, this is a ridiculous situation). I'll give you the particulars of my system (Latest Illustrator CC, Win 7 Pro, 8 GB RAM, nice fast new machine with an i5 processor, document is roughly 70K in size and has maybe 30 layers and hundreds of objects), although that's not relevant to the question - what do you experienced people do when you need to know what object Illustrator is complaining about?
If I can't figure out which object (or set of objects) is causing the problem, I need to delete everything "suspicious" and start over. With no guarantee that it won't happen again. That's kinda... dumb.
Thanks,
Tom

Hi rene,
the error message is on the last screenshot.
while trying to execute the process in runtime, i got the message:
bsp callable object could not be executed
it's quite a simple gp process with only one action item, and all the roles
has been set to myself
anything wrong here?
jun

Difference between Callable Object for execution and Display

Hi,
I am new to Guided Procedures.When i am creating a callable object under an Action ,i find callable object for execution and callable object for display in the dropdown.What is the difference between the two types of callable objects.
Thanks,
Bala

Hi Bala,
GP comes with a set of registered callable object types that define which applications you can directly expose as callable objects and enable their handling in the context of GP processes.
So the different COs can handle your specific application requirements or process flow requirements appropriately at runtime.
You refer those COs in actions. To make the action functional, you attach at least one callable object to it. In addition to the object that is executed when the action is called, you can attach a callable object that is displayed after the execution. The first one is mandatory. You must attach a callable object for execution. It can be either a callable object with a visible part, such as a Web Dynpro or BSP callable object, or one for background execution.
Optionally, you can attach a callable object for display. It is required to have a visible part for example, you cannot select a callable object for background execution.
At runtime, this object is displayed if the processor wants to open the process step after it has been completed, or if a process contributor has view permissions on the action.
To make it easier, I will give you an example with submitting and approving a composite form. Say, the employee fills in an order for something, submits it and the manager then approves or rejects it.
First, in order for the employee to view the form, you can use a Form Display callable object as a display callable object for actions where the execution object is a form. It displays the name and description of the form and provides a link for download. If the user has view permissions on the step, he or she can view the display object and download the form itself. So, this CO is connected basically with the user experience and what he/she sees displayed on the screen, no matter what happens in the background (e.g. you can have a pre-filling service in the background that prefills some fields of the form, but what the user sees is only the form fields with certain info already prefilled in them).
Next, for the manager to approve or reject the form of the employee, you need a CO that is only for execution, for example a Process Control CO for File Approval For forms, you can use it in a process in which a form is sent by e-mail. As soon as the form is submitted back to the system, the receiver can view it, save a copy of the form, and depending on his or her decision, can approve or reject it.
This really is a very simplified example, but I hope it helped a little in some way or another
Here is a link to the Callable Objects in GP documenatation, hope it also clears up some questions:
http://help.sap.com/saphelp_nw70/helpdata/en/d2/d174413aff5458e10000000a1550b0/frameset.htm
Also, a link to the documentation for exposing COs:
http://help.sap.com/saphelp_nw70/helpdata/en/08/d88041a17e060de10000000a1550b0/frameset.htm
HTH:)
Greets,
Petra

Cannot display Adobe form as Callable object in GP

Hi all,
I'm trying to display an adobe form as an Interactive Form Callable object.
I've created a process -> block -> action -> callable object. But the form doesnt display. When I launch the GP runtime and initiate the process, I get the message "The next activity is not yet available: try again later using the "Refresh" button " nothing happens when I hit the refresh button.
Can someone advise me what I might be doing wrong? I've also tried things like consolidating parameters with other callable objects just to see if anything display, but no luck so far.
Thanks
TM

Hi Som,
I'm using NW04s, EP 7.0 SPS 10
OS is Unix(server) Windows 2000 Pro (client)
Browser version is IE 6.0.
I just realised the system is sending out an email to the initiator, and the initiator is able to open the Adobe form. But who does the initiator send the email back to? I'm quite a newbie to this stuff so please bear with me. Also another question is, if the form is offline, then how do we know which workflow (GP) it will tie to once the form is submitted back to the system? In other words, does the person who receives the email with a filled adobe form have to manually initiate the workflow or is there a mechanism to automate this?
Thanks in advance
TM

Re: Callable object for display

Hi all,
I would like to know how a can create a web dynpro component with GP interface so that i can set config (display mode or exceution mode) of CO in GP.
after deploy the WDPro component , I had tried to create a CO in GP, but i can not set the configuration properties of the CO.(It is default to callable object for execution)
And in the help of the NW Studio, it said some coding is needed.
So could anyone give me some guide in doing so.
Thanks In Advance
David
Edited by: David Tai on Jun 20, 2008 4:13 AM
Edited by: David Tai on Jun 20, 2008 4:55 AM

Thx for your reply first.
However I had already have a look on this tutorial, no hints about how to work on CO that is for display.
For example, in that tutorial when creating CO, there is a step for setting configuration initially, but after defining the input or output, that step disappear and the CO is automatically set as "callable object for execution"
In GP, there is an example Time Off Process, in which at each action we can see a CO for execution and CO for display.
So I would like to know how to implement it.
Regards,
David

Prevent auto display/assignment of next callable object

Hi everybody,
I have the following scenario for a GP process:
fist step: maintain data
second step: approve data
The callable objects are WD4J.
I need to route the workflow to a role/group of users. It may happen, that the processor of step 1 is also a member of the role, that is responsible for step 2. Because of SOX compliance, he is not allowed to approve his own data. But if GP identifies the current user as the processor of the next callable object, the callable object is displayed directly and assigned to the user.
This results to the following question:
1) How can I avoid, that the callable object is called directly and force the users to go always to the uwl first, even if several following steps are assigned to the same user
2) How can I prevent that a user is not able to take a task if he was the predecessor of the first step, evenif he belogs to the role that is responsible for the task
I would like to avoid a workaround based on custom code.
Any hints are welcome.
Best regards,
René

Hi Fahad,
I tried same as you said but its not worked.
public void execute( com.sap.caf.eu.gp.co.api.IGPExecutionContext executionContext )
    this.executionContext=executionContext;
public void Complete( )
IUser usr =UMFactory.getUserFactory().getUserByLogonID("logonid");
          IGPProcessRoleInstance role = executionContext.getProcessRoleInstance() ;
          role.addRuntimeDefinedUser(usr) ;
I changedthe roleInitiator of next action is runtime defined.
but its not worked.
Regards,
Naga

Problem in creating a callable object of type Business Logic

Hi SDN,
I am trying to create a callable object of type Business Logic in CE.
When I give all information and click Next, I get this error message.
Error while loading configuration dialog: Failed to create delegate for component com.sap.caf.eu.gp.ui.co.CExpConfig. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
Can anybody help me out with this problem.
Regards,
Sumangala

Hi.
I'm having the same problem as Senthil in NW2004s SP15 with my application service and methods not showing up in the Callable Object wizard for Composite Application Services after I choose the Endpoint. The only application name that shows up in the wizard is caf.tc, and the only service names that show up for it are LDDataAccessor, Metadata, and PropPermissionService.
My IDE is on one machine and the application server I deploy to is located on a different machine. My endpoint to the remote application server looks to be correctly configured. The Composite Application Service seems to be deployed properly as I'm able to see it and test that it works in the Web Services Navigator <http://remotehost:50000/wsnavigator/>
My deployed application service is a remote enabled service and is also web services enabled as well.
I'm not sure if this is relevant, but I noticed that the generated Java code does not create any remote EJB interfaces (only home and local interfaces were generated).
Something else I noticed is that when I proceed to the External Service Configuration -> Business Entities screen <http://remotehost:50000/webdynpro/dispatcher/sap.com/cafUIconfiguration>, I only see three business entities displayed, and the following error message is displayed: "Corrupt metadata has been detected. This may prevent some objects from being displayed. Check the server log for more details." I was unable to find anything in the instance log files. Is the error message indicative of the problem?
I am developing locally without a NetWeaver Development Infrastructure (NWDI) in place.
I'm wondering if the credentials specified in the endpoint require any special roles or privileges.
Senthil, do any of these additional descriptions apply to you as well?
Edited by: Ric Leeds on Jun 20, 2008 4:37 PM

Errot at creation of callable object (Web Dynpro Component (GP Interface))

Hi,
I have made a Web Dynpro component and it has been built and deployed without problems.
However, when I go to the Design Time in the portal to create the callable object, it dumps with this message:
500 Internal server error
The initial exception that caused the request to fail was:
java.lang.UnsupportedClassVersionError: bad version number in .class file
Any ideas to what this is about ?

Hi Peter,
Check this link.It may be helpful.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/java/netweaver%252bdeveloper%252bstudio%252b(NWDS)
Regards,
Sumangala

WebDynpro Application as callable object in GP?

Hello,
I have created a WebDynpro application in NetWeaver Studio.I have to create a callable object of this application in GP.
This application is available in GP.I create a callable object of it, with an action, block process for this single object.(Since i cant test this callable object).
Once i generate url and acess it, it generates an error in browser saying:
"The page builder required to display this application UI inside the portal environment is not available".
Kindly help me solve this issue.
Thanks,
Sharath

Andre,
Thanks a lot for your how to guide.. it's really good!.. I've followed all your steps and I've created my WD DC. Everything works fine, the build is correctly made, but when I deploy the application the following error is getting throw:
Deployment aborted
URL to deploy : file:/C:/DOCUME1/MARIAM1/LOCALS1/Temp/temp62306bcp.compa001de.ear
Result
=> deployment aborted : file:/C:/DOCUME1/MARIAM1/LOCALS1/Temp/temp62306bcp.compa001de.ear
Aborted: development component 'pa001de'/'bcp.com'/'local'/'20070606173629'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application bcp.com/pa001de.. Reason: Clusterwide exception: Failed to deploy application bcp.com/pa001de. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application bcp.com/pa001de. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
I think that the referenced components are not at the J2EE, but how can I check this or what do you think can be happening??
Regards and thanks a lot to all!
María Margarita Monteverde

Callable Object for Webdynpro Application

Hello,
I have a Webdynpro for Java Application where I am importing a model from R/3 and displaying certain records......and want to include it in GP Framework....so which is the Callable Object I should use.....i tried using Webdynpro application type but it gives me the error at runtime while execution as :
Application error occurred during request processing.
Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: Failed to start deployable object sap.com/home~<webdynpro component name>
Any help would be highly appreciated.
Regards,
Anil

Hi Anil,
I am also facing a similar problem . Can you please guide how to solve it.
Thanks and Regards,
Anurag

Error while creating a callable object - User Interface

Hello,
When i'm trying to create a callable object - User Interface in the guided procedure design time. i'm getting an error. An internal server error. This is happening while i'm trying to create a guided procedure with webdynpro's.
Is there any body who allready had somthing like this.
Greetings
Kurt

Hi Raja Akella,
I allready had the roles and my portal version is upgraded until SP8 and all the possible patches.
I get an internal server error when i want to create a callable object. specially when i want to create a webdynpro ( ABAP / JAVA).
In the visual administrator i get the following errors.
Error 1
Exception occured during processing of a Web Dynpro application: "com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.".
[EXCEPTION]
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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)
Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 2
Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:640)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponentInternal(IWDApplicationInfo.java:286)
 at com.sap.tc.webdynpro.progmodel.repository.IWDApplicationInfo$Implementation.getComponent(IWDApplicationInfo.java:270)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.addWdappsElement(COConfigWDApp.java:646)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readWebDynproApps(COConfigWDApp.java:631)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.COConfigWDApp.readApplications(COConfigWDApp.java:308)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalCOConfigWDApp.readApplications(InternalCOConfigWDApp.java:190)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.initCreate(VSelect.java:306)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.VSelect.onPlugFromDispatch(VSelect.java:174)
 at com.sap.caf.eu.gp.ui.co.config.wdapp.wdp.InternalVSelect.wdInvokeEventHandler(InternalVSelect.java:168)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)
 at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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)
Caused by: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:178)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLPersistence.doReadVMO(XMLPersistence.java:126)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.readVMO(RepositoryPersistence.java:356)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.doFindRepositoryObject(RepositoryPersistence.java:598)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.findRepositoryObject(RepositoryPersistence.java:170)
 at com.sap.tc.webdynpro.repository.model.Repository.findRepositoryObjectInternal(Repository.java:590)
 at com.sap.tc.webdynpro.repository.model.RepositoryObjectRelation$XMLGuidWrapper.getModelObject(RepositoryObjectRelation.java:462)
 at com.sap.tc.webdynpro.repository.persistence.RepositoryPersistence.getCurrentLayerObject(RepositoryPersistence.java:702)
 at com.sap.tc.webdynpro.repository.model.Repository.getCurrentLayerObject(Repository.java:1483)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.doMergeInheritedTarget(NonSharedRelationToOne.java:85)
 at com.sap.tc.webdynpro.repository.model.NonSharedRelationToOne.mergeInheritedTargets(NonSharedRelationToOne.java:49)
 at com.sap.tc.webdynpro.repository.model.RelationToOne.getTarget(RelationToOne.java:93)
 at com.sap.tc.webdynpro.repository.model.AbstractRepositoryModelClass.getRelatedModelObject(AbstractRepositoryModelClass.java:234)
 at com.sap.tc.webdynpro.repository.model.DelegatorRepositoryModelClass.getRelatedModelObject(DelegatorRepositoryModelClass.java:636)
 ... 39 more
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >: (:main:, row:1, col:491)(:main:, row=1, col=491) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:148)
 at com.sap.tc.webdynpro.repository.persistence.xml.XMLConfigurationParserWriter.startParsing(XMLConfigurationParserWriter.java:166)
 ... 52 more
Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Bad attribute list. Expected WhiteSpace, / or >:(:main:, row:1, col:491)
 at com.sap.engine.lib.xml.parser.XMLParser.scanAttList(XMLParser.java:1566)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1687)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 ... 53 more
error 3
Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to get Related Model Object for the object com.sap.caf.eu.gp.dt.comp.semanticbrowser.SemanticBrowserApp, relation Component.
Exception id: [00505691431B006F0000003E00000FE800041B45B87F7617]
thanks in advance
Kurt

Getting error while creating callable object

Hi,
I've created and deployed a DC using webdynpro.
Now I want to create a callable object from portal
I'm choosing the following options Guided Procedurers-->DesignTime>Create callable object-->userinterface>webdynprocomponent(GP interface)
On entering the required data on the displayed page, when I'm clicking 'next' option it is giving "500 internal server error".
Can somebody help how to resolve this.
Thanks
Piyush

your callable object component is missing. try to take preview of the iview and check.

Web Dynpro application callable object error: Page Builder Not available

Hi, SDN Fellow.
I created a callable object of Web Dynpro application. The callable object is atatched to an Action, and Action --> Block, and Block --> Process.
I initiate the process in GP Runtime, when it comes to the Action screen the Web Dynpro application atatched to, I got the following error:
The page builder required to display this application UI inside the portal environment is not available.
As aa comparison, another callable object that atatched to a Web Dynpro component (that implement GP interface) is working fine.
Please advise.
Thanks in advance,
KC

Hi KC,
When you start your process from GP Runtime, does the actual action/callable object open in a new window?
Have a look at this SAP Note:
[Error when executing a GP task - Page builder|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_gp/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393831353137%7d]
Although the error message you are getting is different, but if your callable object opens in a new window, then the problem (in most probability) is the same as mentioned in the SAP Note.
Also, try testing the Web Dynpro callable object in standalone mode. For more information on this, see:
[Testing Callable Objects|http://help.sap.com/saphelp_nw04s/helpdata/en/4c/588041a17e060de10000000a1550b0/frameset.htm]
Bye
Ankur

Problem to execute a Callable Object (SAP R/3 transaction) in UWL

Hi,
I have developed a callable object which calls a SAP R/3 transaction. It runs perfectly in design time , when I run it in UWL I am getting the Error "An error occurred while displaying the callable object, which uses the page builder. Check that the page builder is installed, and the transaction iView is available .
Please let me know your thoughts and suggestions.
Regards
Wesley Solomon

Hi Wesley
According to me, it is because of some missing package that this problem is encountered coz even i have faced this problem w.r.t the UWL and then i imported the required packages and it worked.
Regards
Navneet

Exception in executing External Service type Callable Object

Hi
I was trying to test a callable object of type external service. I have used the bapi BAPI_FLIGHT_GETDETAIL. But while executing I was getting exception like
java.lang.IndexOutOfBoundsException: Index: 5, Size: 3
at java.util.ArrayList.add(ArrayList.java:371)at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.addElementSilently(Node.java:1991)at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.addElement(Node.java:2003)at com.sap.tc.webdynpro.progmodel.context.Node.doAddElement(Node.java:676)at com.sap.tc.webdynpro.progmodel.context.Node.addElement(Node.java:644)
Anybody knows the reason?
Cheers
Sudip

Hii
I forgot to mention that if the RFC has a structure as output parameter it doesnt get displayed but if the parameter in RFC is string value it works fine.Please Help Urgently
Regards
Ishita

BSP callable object failed to display

Similar Messages

Maybe you are looking for