Hcm process as callable object in GP

Hi All,
I have an abap wd application named asr_process_execute ..which is used for executing certain processes using HCM processes and forms
And we have integrated it as one of the callable object in the guided procedure..
My requirement is when the user presses the complete button there should be a validation to check if the user has actually executed the processes in WD ABAP application or not .. if yes .. then complete button should go smooth ... if not .. then some error message should come..
Hope the above explanation is clear ...
Thanks in advance.
Best Regards,
Akshay..

Hey Bala,
Thanks for the response. You got it right you have a result state button where u can select the target.
But how do u get to know if the user has executed the process by pressing the send button on the form which is the embedded inside wd abap application ASR_PROCESS_EXECUTE which inturn is embedded in the callable object?
Only when u get this information .. we can use it to contol the processing of the Callable Object.
Best Regards,
Akshay

Similar Messages

  • Assign User for Process Role Callable Object

    Hi,
         I have a doubt in the Callable Object Assign User for Process Role.wat is the use of this callable object.This Callable Object is used to reterive any portal user information?can any one give description about this Callable Object.
    Regards,
    Satheshkumar

    Hi,
    Take a look at the following [wiki page |https://wiki.sdn.sap.com/wiki/display/BPX/GuidedProceduresCallable+Objects] and look for the callable object you need. There is a link to a tutorial.
    Dick

  • Launch Webdynpro Callable Object in Mobile?

    I am able to launch the normal Webdynpro Java application in Blackberry, but want to add it to GP Process using Callable Object, but no idea how can we get the URL for WD - Callable Object?
    Is it possible to launch web dynpro Callable Object in Mobile like in blackberry? I am trying to write a program for Approval Process for my project. If any one have done this please let me know what URL we need to use to launch the WD-Java Callable Object in Mobile?
    Please let me know if you have any suggestions.

    resolved myself

  • How to pass process instance id to callable object?

    Hello,
    using the SAP NetWeaver CE 7.1 EhP 1 SP 2 I have modeled a small approval workflow with Guided Procedures.
    At runtime, I want to pass the id of the running process instance to a callable object (WD4VC composite view). Is this possible and how?
    Alternatively, is there any way to fetch the id of the current process instance from withina WD4VC composite view?
    Kind regards
    Alexander

    Hi,
    I hope you have executionContext in callable object.
    You can get the ProcessID by calling function "executionContext.getProcessId()".
    Regards,
    Niraj

  • GP Process is Running even though Callable Object Encountered Error

    Hi Everyone,
    I am experiencing an interesting issue working with GP right now and it bothers me.
    I have created a process that includes a sequential block with a few actions including an action that sends out an Adobe form. I noticed during testing that even if the callable objects encountered technical exception (found in the logs), the process itself is not marked as erroneous. This bothers me because I'd like to see the process marked as erroneous if the callable object has errors.
    Has any one experienced this? Is this the "expected" behaviour? I am on SP18 ... is this fixed in a later support package stack?
    Thanks for any input.
    Robert

    Hi Everyone,
    I am experiencing an interesting issue working with GP right now and it bothers me.
    I have created a process that includes a sequential block with a few actions including an action that sends out an Adobe form. I noticed during testing that even if the callable objects encountered technical exception (found in the logs), the process itself is not marked as erroneous. This bothers me because I'd like to see the process marked as erroneous if the callable object has errors.
    Has any one experienced this? Is this the "expected" behaviour? I am on SP18 ... is this fixed in a later support package stack?
    Thanks for any input.
    Robert

  • 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.
    <b>Error 1</b>
    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
    <b>error 2</b>
    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
    <b>error 3</b>
    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

  • Web Dynpro as Callable object in GP using PDF Forms

    Hi All,
    I somehow want to integrate a user filling out a pdf form within a Guided Procedure. So far I have created a local web dynpro DC and I want to make it a Web Dynpro Callable Object (GP Interface). The problem is, I want the user to be able to see the PDF form when filling out the form. For example, if they had a role in the portal where they can invoke the Web Dynpro application with the pdf form, then when they click submit on the pdf they invoke the guided procedure...is this possible? This is so, I can use the web dynpro to do some data validation and call some bapis to get info, then submit this all to the GP. Is this achievable? I know how to do most things, I just want to know things like when is the "execute" and "getDescription" methods called? I want my execute( com.sap.caf.eu.gp.co.api.IGPExecutionContext executionContext ) method to call a bapi also. Is that possible? How do I automate a GP process when I click submit on the pdf form?
    Thanks in advanced
    TM

    Hi,
    You can integrate a PDF control in a Web Dynpro view. Refer the following links for that:
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/dc/f1783fe3263042e10000000a114084/frameset.htm">Example of the Use of an Interactive PDF Form (SAP Library - Web Dynpro for Java)</a>
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/60/6fc10c6748479392101e09c9e8d33a/frameset.htm">Interactive Forms in Web Dynpro for Java</a>
    Also you can create Web Dynpro Java callable object in GP by implementing the IGPWebDynproCO interface. Refer the following links for that:
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50d74ada-0c01-0010-07a8-8c118d408e59">Implementing a Web Dynpro Callable Object which Implements the GP Interface</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3f07a7a-0601-0010-ebbd-b9cfb445b814">Implementing a Web Dynpro Callable Object</a>
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/fd/afb4429027da11e10000000a155106/frameset.htm">Implementing a Web Dynpro Component</a>
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/de/8976417f2d5558e10000000a1550b0/frameset.htm">Implementing and Exposing a Web Dynpro as a Callable Object</a>
    You can start a GP process using the public API:
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/43/fcdf77fc6510b3e10000000a11466f/frameset.htm">Starting and Terminating Processes Using the GP API (SAP Library - Creating Composite Applications)</a><a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5f27e290-0201-0010-ff82-c21557572da1">Creating Interactive Forms in Web Dynpro for Java</a>
    Also you can start a GP process using Web Service:
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/44/44c59fd7c72e84e10000000a155369/frameset.htm">Starting a Process Using Web Services (SAP Library - Creating Composite Applications)</a>
    <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/93/27dc108cfc407fbf6c726151840001/frameset.htm">Starting and Terminating Processes Within a Composite</a>
    Refering the above links you'll get a fairly good idea how to integrate Adobe forms in WDP and how to start GP process programitically. My suggestion for your requirement would be if always you need to start the process after the user submits the Adobe form, then consider having the Adobe form as the first step for the process. In that case you don't need to start the process programitically. Whenever the user starts filling up the Adobe form the GP process will start. You can refer <a href="/people/dipankar.saha3/blog/2007/03/02/how-to-present-your-gp-processes-to-the-end-user">this blog</a> on how to start a GP process as an iview link in portal.
    Otherwise if based on certain conditions you need to start the process then you can either use the Java API or the web service to start the process from Web Dynpro. You should have the Adobe form embedded in Web Dynpro and on submit event you can check the conditions and start the process if required.
    Thanks,
    Dipankar

  • Callable Objects-Write to System Log,Offline Approval

    Hi,
    I am new to Guided Procedures and I am trying out examples in all callable objects.
    I have doubts in 2 callable object
    1. Can you guide me how to use the callable object under Miscellaneous Type - Write to system Log
    After we Enter the Log text where to go and view the text.    
    2.Callable object under  Process control type -  OfflineApproval           
    When I use this callable object I am not getting mail whether the action is approved or rejected.
    Regards,
    Bala Baskaran
    Edited by: Bala Baskaran on Feb 27, 2008 12:45 PM
    Edited by: Bala Baskaran on Feb 27, 2008 12:48 PM

    Hi,
    Which SRM version are you working??Always mention that in your post for appropriate solutions.
    Pls see the foll notes:
    <b>Note 928320 - RBBP_OFFLINE_EVAL: Local purchase orders not selected</b>
    Note 980963 - RBBP_OFFLINE_EVAL: Some users not found
    Note 1039869 - RBBP_OFFLINE_EVAL:Sometimes text contains no Object ID
    1035114 - RBBP_OFFLINE_EVAL: Wrong messages , missing values there
    BR,
    Disha.
    <b>Pls reward points for useful answers.</b>

  • Error while creating Callable object

    Hi,
       I had developed a form through Adobe Life Cycle Designer and now am creating a caalable object for a standalone interactive form.In the Set Configuration step i'am trying to Use the Process "Time of Process" which is a default process template available under Examples Foldr,but when am trying to use it is giving me an error "<b>Unable to check chosen process for default users: No active version of the given development object exists; contact your system administrator</b>".
    Please anybody help me in this issue.
    With Regards
    Pradeep.B

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

  • HCM Processes and Forms: Work Item is not opening

    Hi,
    We are implementaing HCM processes and forms using NWBC (EHP7 - HR Renewal 2.0 FP1) and after using configuration of POWL inbox for MSS and HR Admin, We are not able to launch the Work Item.
    1) In MSS Work Book, while launching, we are getting message  -
    Failed to resolve Object Based Navigation target ".MSS_WL.NAVIGATE_FORM_WD". Use transaction PFCG to define this OBN target in a role or contact your system administrator to assign a role with the relevant OBN entries to your user.
    2) For HR Admin, we are getting message - Work Item can only be open using Portal and UWL. and it is displaying back end transaction SWNWIEX.
    Detail configuration steps are shown as below -
    Workflow Task used in configurations -
    1) Entries in IBO_C_WF_TA_P_SC  (Assign Task ID’s to POWL Types)
    2) IBO_C_WF_ACC configuration - (Define Tasks and Actions)
    3) IBO_C_WF_APC configuration (Provide Details of navigation parameters)
    4) IBO_V_WF_TTAC (Assignment of Actions to the Tasks)
    5) IBO_C_WF_TAC (Specify Default Action)
    Error -
    1) MSS -
    2)HR Admin -

    Hi Guru,
    Any input..its urgent!.
    Regards,
    Vijay

  • 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

  • Error while Accessing the HCM process and forms

    Hi All,
    We have implemented HCm process and forms. Everything was working fine earlier but for past few days we are facing an issue after selecting an employee and clicks on the select process we are getting the following error. Kindly povide the solution.
    The following error text was processed in the system GOA : Component Usage OADP_USAGE Does Not Have an Active Component
    The error occurred on the application server sapgoa_GOA_37 and in the work process 4 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: ENSURE_ACTIVE_COMPONENT of program CL_WDR_COMPONENT_USAGE========CP
    Method: GET_INTF_CONTROLLER_INTERNAL of program CL_WDR_COMPONENT_USAGE========CP
    Method: IFWDR_INTERNAL_API~GET_INTERFACE_CTLR_DELEGATE of program SAPLWDR_RG_PROXY_FACTORY
    Thanks & Regards,
    Sreelatha Gullapalli.

    Hi,
    In EhP4, the employee search is created using OADP framework . And if the relevant configuration is not maintained , I mean there is a view cluster where the applications (PA/PD) and relevant object types are maintained.
    If this is not maintained, this creates a error. Please check .
    Hope this helps.
    Best Regards
    Saujanya

  • Error in creating Callable object of type Portal iView

    Hi People,
    I need to create a callable object of type Portal iView / Page,
    But whenever I try to create it gives me a RunTime Exception:
    <b>java.lang.ClassCastException
         at com.sap.caf.eu.gp.ui.co.portal.dt.VBrowse.appendChildren(VBrowse.java:523)</b>
    Please suggest some way out,
    Thanks in advance,
    Deepak

    Hi,
    How many actions  are there in your process?. Is it having only one action that is Web service?.
    I think, The process should at least contain one UI action.
    If your process is having multiple actions, there may problem with other actions. Test the web service action seperately to confirm this.
    Thanks

  • Workflow could not start in HCM process and Forms

    Hi All
    It would be really helpful if you can suggest possible solution regarding case management case in HCM forms and process.
    I have set up a simple custom HCM process and Form regarding Infotype 2 updation. I have checked the process and form consistency and it seems fine. Now when I run the process from HRASR_DT it generates a process number but it also gives an error workflow could not start.I get following error (SWIA log - Step history)
    Executing flow work item - Transaction brackets of the workflow has been damaged
    Exception occurred - Error when starting work item 000000007031
    PROCESS_NODE - Error when processing node '0000000014' (ParForEach index 000000)
    CREATE - Error when creating a component of type 'Step'
    CREATE_WIM_HANDLE - Error when creating a work item
    CREATE_VIA_WFM - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event CREATED and (target) status
    EVENT_RAISED - Error updating the process object
    Executing flow work item - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event STATE_CHG and (target) status READY->ERROR
    EVENT_RAISED - Error updating the process object
    Executing flow work item - Transaction brackets of the workflow has been damaged
    Executing flow work item - Work item 000000007031: Object FLOWITEM method EXECUTE cannot be executed
    Executing flow work item - Error when processing node '0000000014' (ParForEach index 000000)
    I have searched few SAP notes such as 1384961 which talks about same error but it is implemented in our system (EA-HR 604 , Patch 27, )
    Appreciate any help.
    Thanks
    Umang

    Hi Swati
    One of the similar (not exact) issues were resolved by correcting the event linkage....please refer thread:
    http://scn.sap.com/message/14848795#14848795
    Not sure of the details of the the resolution, maybe Ragavendran Kanagaraj can throw more light.
    Just some high level checks (if not done already):
    Check event linkage errors in SWEQADM if anything is related to your WF
    Check in SWEL if it's showing any more details (not sure if it will)
    Any warnings in syntax check of WF template (PFTC) or WF definition (SWDD)
    Any error sin binding
    regards,
    Modak

  • Adobe WebDynpro Callable Object

    Hi all
    I created Adobe WebDynpro application whihc worked well.
    After creating callable object with WebDynpro (GP instance), and  when i click complete button which is linked with complete method, following error occoured.
    Actually adobe form web dynpro works well independently.
    What do you think about that?
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.prepareSoapMessage(PDFObject.java:517)
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:351)
         at com.sap.tc.webdynpro.pdfobject.core.PDFObject.inputPDF(PDFObject.java:3643)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentInputPDFHandler.handle(PDFDocumentInputPDFHandler.java:145)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentProcessor.process(PDFDocumentProcessor.java:52)
         at com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentAccessibleContext.execute(PDFDocumentAccessibleContext.java:149)
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.AdobeFormHelper.updateDataContainer(AdobeFormHelper.java:161)
         at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.beforeTransportData(InteractiveForm.java:465)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.beforeTransportData(ClientApplication.java:1130)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:141)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:726)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:662)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:808)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:80)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1289)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:324)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:830)

    Hi Aliaksandr,
    I have the same issue and we desire the same. Also the button is placed outside the form....
    Have you found out what could be a possible solution?
    I couldn't find any note on this occurence.....
    Thanks in advance!

Maybe you are looking for