FIORI Leave Approval Scenario Definition Error

Hi,
I have implemented a leave approval before. That was working fine. Now I'm implementing another leave approval on a different server (embedded deployment also). I followed the same configurations for scenario definition and system alias. But I'm still having this error.
Below are my configurations:
Hope someone can help. Thanks in advance.

Hi Melanie,
Are you implementing old UI? Please use new one..
Important Note: Please use new UI with new SAP Fiori launchpad
Only Approve Requests app uses scenario definition customizing. Other approval apps read workitems from backend application tables.
Regards, Masa
SAP Customer Experience Group - CEG

Similar Messages

Fiori Leave Approval App - Scenario Defenition Error

When I execute the Leave approval service in browser I get the below error, maintained the scenario definition settings as per the installation guide, my service pack level is Fiori SP03, so all the relevant, mandatory notes are applied.
Could you suggest anything else that I have missed out. attached the screenshot in scenario defn.
Check the URL parameters and the scenario definition. To check the scenario definition, go to customizing for SAP NetWeaver Gateway and choose SAP NetWeaver -> Gateway Service Enablement -> Content -> Task Gateway Service -> Scenario Definition.
Tags edited by: Michael Appleby

Hi Jegadesh,
The scenario ID should be LEAVEREQUESTAPPROVAL. Please double check the installation guide.
FYI.
I think you use old UI.
Important Note: Please use new SAP Fiori Launchpad
Regards,
Masa
SAP Customer Experience Group - CEG

Getting an Error while trying to Approve Requisition in SAP Fiori PR Approval App

Hi Experts,
We have followed all the instructions given in the installation/configuration of SAP Fiori PR APPROVAL APP. While approving the PR from Lunchpad we are getting the following error.
ERROR :"RFC Error : Internal program error; (SAPMSSY1 ZCL_IM_ME_PROCESS_REQ_CTSD====CP 1 CBRC_EXIT_47_PURREQ)"
2) I have put a debugger in the USER_EXIT : "CBRC_EXIT_47_PURREQ" and checked that the value of SY_UCOM is initial and when i store the value "MESAVE" and run through debugging i am able to approve the PR. I want to get rid of this Debugging mode and run the PR APP from Launchpad properly without error.
Attached are the three screenshots for more referenece.
Kindly help me with the same.
Thanks & Regards:
AZhar

Am i getting this Error for the below reason?..
Because i am also getting the Same Error as the error in the below post.
POST "Fiori - Approve Purchase Requisition Error"
Please find the attached error screenshot and confirm.
Thanks & Regards:
Azhar

Error in Leave Approval Workflow

Hello Experts,
I'm Using Standard Workflow WS0040077 for Leave Approval . I Activated the Event Linkage in SWEL .Did General Task in Agent Assignment . But when i run transaction PA30 . i get this error in SAP Inbox.
Following error occurred:
00 341
RFC_NO_AUTHORITY
Message text:
Runtime error RFC_NO_AUTHORITY has occurred
SAP System: EDV
Client: 100
Event container appended as attachment.
Event linkage not changed.
Event stored temporarily.
Events can be redelivered via event queue
administration (transaction SWEQADM).
so what should i do to solve this problem.

Hi,
Have you checked the workflow config in SWU3? It sounds like there may be a problem with the LOCAL RFC destination used by workflow. Click the 'Start Verification Workflow' button in SWU3 as a health check.
Also, are you testing this in the right client?
cheers
Paul Bakker

Approve Request App Error

Hi All,
i am working on Fiori Approve Request App & getting below Error on Launchpad.
Check the URL parameters and the scenario definition. To check the scenario definition, go to customizing for SAP NetWeaver Gateway and choose SAP NetWeaver -> Gateway Service Enablement -> Content -> Task Gateway Service -> Scenario Definition.
can you please help me.
I am following this document:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0ab2463-4e16-3110-b08e-d93918e513a1?QuickLink=index&overridelayout=true&59407987747630
Regards,
Naresh
Tags edited by: Michael Appleby

Hi Masa,
As per the troublshotting doc ,i have taken last URL from network tab which is "/sap/opu/odata/UI2/PAGE_BUILDER_PERS/$batch".
After excting the last url in /IWFND/GW_CLIENT we are getting error:
The server is refusing to process the request because the entity has a unsupported format
Regards,
Naresh

Missing IMG node for Scenario definition

We are currently configuring FIORI PR approval and the IMG node for Scenario Definition under Task Gateway Service is missing. Components installed as well as the IMG screenshot is below. Any thoughts on what would be missing is appreciated.
Tags edited by: Michael Appleby

FYI.
I see you use old UI components which were released in May 2013.
Important Note: Please use new UI with new SAP Fiori Launchpad
New UI components have UI extension points and work with new SAP Fiori Launchpad.
Please find correct components based on your Backend version.
SAP Fiori - Add-on quick reference for transactional apps
Regards, Masa
SAP Customer Experience Group - CEG

HR Leave Approval issues

hi everyone,
I have modified the standard HR Leave approval Workflow WS002000077. In that workflow user decision, Unlock step type, loop steps are available. I am getting user decision workitem in inbox. When i click approve option, i has to go to unlock step type. But it is not going for unlock step.
The same scenario is working good without loop, i can able to unlock it.
So, in this scenario with loop, I am getting following errors;
1. variables of the work item cannot be generated.
2. Error in the evaluation of expression '&EMPLOYEET<???>.NAME&' for item '10'
3. Error when determining attribute 'NAME' of object instance '[BO.EMPLOYEET.]'
4. Agent determination for step '0000000038' failed
5. Source (expression '&EMPLOYEET.ADMINISTRATOR.ADMINISTRATOR&') of binding assignment is not available
6. Source (expression '&EMPLOYEET.ADMINISTRATOR.ADMINISTRATORGROUP&') of binding assignment is not avaible
7. Error in the evaluation of expression '&EMPLOYEET<???>.ADMINISTRATOR.ADMINISTRATORGROUP&' for ite
8. Error in the evaluation of expression '&EMPLOYEET<???>.ADMINISTRATOR.ADMINISTRATOR&' for item '10
here item '10' refers to loop step. I am using custom rule. It is working fine without loop condition.
Thanks in advance!!

hi,
That one previous workflow and it solved. But now the same one with loop for Re-submission of Leave Request after change.
Actually the values from Employeet is not flowing in the Unlock step for agent determination. Because of that the agent determination is not possible for me. But it works well without loop scenario. Employeet is not instantiated.
Here i am using loop condition for re-submission of leave request.
Thanks,
Balaji.V
Edited by: Balajisap on Sep 19, 2011 3:56 PM
Edited by: Balajisap on Sep 19, 2011 6:22 PM

Fiori : Mass Approval

Hi,
Is Mass Approval possible for Approval apps in Fiori ?
I see we have Mass Action field in Scenario definition . If i check it, how can we enable Mass approval in Fiori ?
Any other solution, please highlight

Hi Tejas,
Mass approval is not released in UI side.
Users can use quick approval by side sliding in tablet.
From business process point of view, mass approval is not a best practice.
When user do mass approval, approves never check details and it means blind approval.
If it is the case, workflow engine can set approval based on business rules and send workitems which really need to be checked. It reduce workload for managers.
Regards,
Masa
SAP Rapid Innovation Group - RIG

Scenario manager error while starting server

can anyone please give the solution for the below error:
15:26:33,796 ERROR [ScenarioManager] Error while trying to complete pending oper
ation PendingDeletion[scenarioDeletion:3000001,/myscenario/custom.sdl,null,13457
91138625]
atg.process.ProcessException: Null value for property "subject" of repository it
em individualScenario:10000002
at atg.process.ProcessUtils.getNonNullPropertyValue(ProcessUtils.java:21
1)
at atg.process.ProcessManagerService.getSubject(ProcessManagerService.ja
va:3093)
at atg.process.ProcessManagerService.deleteIndividualInstance(ProcessMan
agerService.java:3288)
at atg.process.ProcessManagerService.deleteBatch(ProcessManagerService.j
ava:3330)
at atg.process.PendingDeletion.complete(PendingDeletion.java:340)
at atg.process.PendingWorkThread.run(ProcessManagerService.java:17169)
15:26:33,859 ERROR [ScenarioManager] Error while trying to complete pending oper
ation PendingDeletion[scenarioDeletion:4000001,/myscenario/custom.sdl,[Segment 1
],1345791144734]
atg.process.ProcessException: Null value for property "subject" of repository it
em individualScenario:12000008
at atg.process.ProcessUtils.getNonNullPropertyValue(ProcessUtils.java:21
1)
at atg.process.ProcessManagerService.getSubject(ProcessManagerService.ja
va:3093)
at atg.process.ProcessManagerService.deleteIndividualInstance(ProcessMan
agerService.java:3288)
at atg.process.ProcessManagerService.deleteBatch(ProcessManagerService.j
ava:3330)
at atg.process.PendingDeletion.complete(PendingDeletion.java:340)
at atg.process.PendingWorkThread.run(ProcessManagerService.java:17169)

atg.process.ProcessException: Null value for property "subject" of repository item individualScenario:This signifies that the subject property for your individual scenario is not referring to any user profile item which should not be the case. It could be because when your scenario is getting triggered there is no current user profile available. You will have to check your scenario definition segments that you have defined and the conditions when it is getting triggered.
ATG scenarios are based on the concept of state machines. Scenario manager maintains state information for every individual profile going through each of the scenario segment and each user's state is stored in the profile repository in "scenarioInstances" property. "scenarioInstances" contains a set of individual scenario instances (repository items of type "individualScenario") which are currently associated with that user. "individualScenario" item has a subject property which points back to the "user" repository item. And in your case some segment of your scenario is getting triggered when subject is not available.

Default "SAPInitial" View for Leave Approval in NWBC 4.0

Hello All,
We are using NWBC 4.0 for Desktop. Requirement of client is to default SAPInitial from dropdown list in View Field under Work Overview>Leave Approval. I am not able to find in R/3 where the configuration is done to default SAPInitial view for Leave Approval.
Any help on this will be highly appreciated
Regards,
Nishant Gaur

Hi Nishant,
just to clarify this from the NWBC team and to give some detailed background information:
With NWBC 4.0 the default is that the index page is pinned when you connect to a system the first time on your local machine.
The logic here is very easy. NWBC checks if there is a special *.tab file for the system in the following user directory - %APPDATA%\SAP\NWBC\Tabs. The files have the naming convention SYSID_NWBC.tabs. If the file does not exist, the pinned index page will be shown as default and the file is written and stored into the Tabs folder.
That means this logic is not dependent on the SAP system user, but on the OS/Windows user.
The next time you start NWBC and connect to the same system, the tabs are read from the *.tab file and you can then unpin and pin other tabs.
So your first question is somehow strange, as the default definitly is the pinned index page.
Best Regards,
Thomas

Custom Leave approval task problem

Dear All,
I have a problem with my custom leave approval webdynpro task.
Actually I was using standard task , TS12300097 for leave approval. It was working fine from SAP worklist from portal. If someone tries to approve from SAP R/3 it was providing an information like, this cannot be executed from SAP R/3.
I had a requirement to add certain custom fields information to the task description, so I copied and created a new task similar to that and added the containers and filled the description to that. Then i cofigured the new task in SWFVISU also. It working fine from enterprise portal sap worklist.
But some tries to approve from SAP Inbox in R/3 the workflow results in error. Its not providing the same information which was coming earlier with standard task.
The error is as follow :
Work item 000000885207: Object CL_PT_REQ_WF_ATTRIBS method DUMMY cannot be executed
Dereferencing of the NULL reference
Dereferencing of the NULL reference
Error handling for work item 000000885207
Let me how we can solve this issue.
regards,
Sabari Prabhu.

We are changing our Leave Request workflow, and I also came across this problem while testing.
In our situation, the problem is that we changed the approval task. We used to have it as a call to report RPTARQAPP, but then changed back to the standard method of calling CL_PT_REQ_WF_ATTRIBS DUMMY.
For us, it is only the old work items that go into error if the user tries to execute them in R/3. If the workflow is then re-started, the item is once again available and can be processed in the UWL. New work items come back with the pop-up message "The request cannot be started from the Business Workplace", like in the standard workflow.
I think we will just add some encouraging wording to the task so that people will (hopefully) not attempt to execute the work items in R/3, like this:
Please log on to ESS to approve this Leave Request through the Universal Worklist (UWL).
It is not possible to complete this work item from within R/3, DO NOT execute this work item here.
Once you have processed the request in ESS, this work item will automatically be completed.
Good luck

ESS Leave Approval: No authorization to start service

Hello,
User is not able to approve leave requests of sub-ordinates.
When user clicks on Approve or Reject button, nothing happens.
But when I checked in Default trace, I found below error:
You do not have the authorization to start service
sap.com/ess~lea/LeaveRequestApprover.
[EXCEPTION]
I checked portal content permissions for this user and found that those
are ok.
In ECC there is no dump (ST22) related to authorization.
Can you please suggest the solution.
Regards,
Vinod

Hello Karthik and Vivek,
Thanks for replies. But we have created ZMSS role in ECC which is assigned to all managers.
For all other managers the leave approval is working fine. The problem is with only 1 user.
So I dont think there is any issue in ECC authorizations.
Also there is no ABAP dump. Is there any other way like some trace from where we ll come to know about the missing authorization.
With Best Regards,
Vinod Patil

Leave Approval: Another superior in case present superior absent

Hi all,
I have a requirement with the Leave request ( WS2000081) . In the standard scenario, the leave request goes to Approver and he approves it.
My business requirement is that in case the Leave approver is absent it should go to the superior's superior(that will be decided) . Any idea how to go about it ? How should one go about modifying the workflow?
any help is appreciated.
Regards
PN

Substitution is a good option which was implemented.

Advanced search in ESS leave request scenario

Dear experts,
we want to use the leave request scenario for ESS. The employees should choose the ap-prover with the search help (or advanced search which pops up when the user clicked the symbol at the edge of the approver field). Is there any way to customize the advanced search so that the result only lists employees in a specific role and not all of them? Where can I see the code from the advanced search und where can I change this?
I am thankful for any hints and tips!
Many thanks
Diana Natanegara

Re: Advanced search in ESS leave request scenario

In ESS-Leave Request -A critical error has occured.

In ESS when tried to enter the Leave which is under Leave request the below error occured:
Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
     at com.sap.xss.hr.lea.blockcale.FcBlockCale.getBcData(FcBlockCale.java:232)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCale.getBcData(InternalFcBlockCale.java:250)
     at com.sap.xss.hr.lea.blockcale.FcBlockCaleInterface.getBcData(FcBlockCaleInterface.java:135)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface.getBcData(InternalFcBlockCaleInterface.java:224)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface$External.getBcData(InternalFcBlockCaleInterface.java:276)
     at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:261)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)
     at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)
     at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.java:220)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
     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:860)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
     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: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:175)
     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(AccessController.java:219)
     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.aii.proxy.framework.core.BaseProxyException: CREATE OBJECT: The class was not found., error key: RFC_ERROR_SYSTEM_FAILURE
     at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
     at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.pt_Arq_Eecale_Get(LeaveRequestAdaptiveModel.java:434)
     at com.sap.xss.hr.lea.model.Pt_Arq_Eecale_Get_Input.doExecute(Pt_Arq_Eecale_Get_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 60 more

I found out the solution and solved this issue.
Deleted the leave request which was created with error i.e: from the custom table zxx_vacr noted down the id initiater ( which had error) and in the Test Environment for Leave request (PTARQ) gave the PERNR and deleted the documents ( gave the id iniater in the document status ).
To check the error work flow go to SWIA and check for that Workflow (Leave) raised by the PERNR at that duration ( check in IT2001 for the duration) and give it here.
After deleting it check in the portal for the leave request.

FIORI Leave Approval Scenario Definition Error

Similar Messages

Maybe you are looking for