Process control workflow issue with Approvers

Hello Experts
In PCW, after creating a shopping cart i dont see the work item in the approvers work list. Can you please tell me how where to check out this / debug this problem.
Thanks in Advance.

hi,
check if you can see the work item in the approver's inbox in tcode SBWP (business workplace).
if you can find the work item there, then check the approver's authorization as advised by SG.
regards.

Similar Messages

SRM Process Controlled Workflow Issue - Process Level Agent not shown up

System: SRM 7.0 (SP09)
Implemented BADI to determine agents at process level - BADI Definition /SAPSRM/BD_WF_PROCESS_CONFIG
Configuration: 1 Process Level (Seq 100, Lvl Type A, Resp. Resolver Name: Z_XXXXXX, Task ID 40007954, Decision Type 1)
When creating the Shopping cart based on the cart value, the agents are determined correctly and process level GUID is created with Agent ID associated.
something like
GUID1 - APPR1
GUID2 - APPR2
GUID3 - APPR3
GUID4 - APPR4
Before "Order" when we do preview of Approval Process, it shows all the approvers in the sequence as expected. As soon as the cart is ordered, the first process level GUID lost its agent thus throwing error saying "Strategy Z_XXXXXX did not determine any approver"
But when we look at the table /SAPSRM/D_WF_016, the corresponding entires of GUID1 has the agent ID as APPR1.
The task 40007954 has been GENERALIZED so as the master workflow template 40000014. The same is working in our Dev system but throwing error "Strategy Z_XXXXXX did not determine any approver" in QA system.
Any input is highly appreciated.

See the thing is the agents were picked up & saved in the table /SAPSRM/D_WF_016 in the process level BADI. The first process level guid doesn't get processed in the RESP_RESOLVER BADI. I put the break point and can see the agents were picked up & saved in Process Level BADI.
The funny part is it is working just fine in the Dev system. Secondly, when we do BOB for the same user (requester), it picks up the first level approver without the error.
Meaning, If USER1 shops for himself (Creator & Requester are same), we encounter this error. If USER2 shops for USER1, then the corresponding approvers were picked up correctly without the error. USER1 & USER2 have same authorizations in SU01D (USER2 is copy of USER1, so no authorization issues). Approvers determination is based on the requester.
Somewhere, we miss the settings. Don't know where though.

Issue in Process Controlled workflow for Shopping cart in Quality system.

Hello All,
I ahve configured a Process controlled workflow in SRM 7.0 with custom resolver, and I am facing an issue taht the Workflow works well in Development but in Quality the approvers are dropped after SC is ordered in Quality system.
The SC Workflow drops the approvers picked up from the Interface method /SAPSRM/IF_EX_WF_RESP_RESOLVERGET_AREA_TO_ITEM_MAP and IF_EX_WF_RESP_RESOLVERGET_APPROVERS_BY_AREA_GUID of BADI /SAPSRM/BD_WF_RESP_RESOLVER. The approvers can be seen in the shopping cart Approval preview Tab until the SC is ordered.
I have compared the OSS notes relevant for Workflow, all of them have been transported, Also I compared and checked general Workflow settings, BRF Config and Process level settings in Dev and Quality, everything is same.
Also while debugging; the approvers can be seen in the decision set table in the create_process_forecast method of class /SAPSRM/CL_WF_PROCESS_MANAGER.
Kindly let me know what else i can check to find the root cause.
Thank you in advance for help!
Regards
Prasuna.

Hello Vinita;
Thanks for the input and sorry for the not so "ASAP" reply;
From what I'm seeing in from your 2 screenshot, i strongly believe that the problem is even before the Z implementation /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID (in which the FM i ZSRM_GET_USER_FROM_PGRP is called. I think the problem could be in the process level determination ZSRM_WF_BRF_0EXP000_SC_APP100. Let me explain:
In your cases where not buyer is determined, in the approval tab there is not even a process level for buyer approval. If the problem were indeed in the implementation /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID then the process level would be there, but the system will display, instead of the name of the buyer(if the buyer determination fails) a red label with the message: "With the strategy "Buyer determination" an approver could not be determined (or something like that..please check the image at the end of the text)".
I can propose a way to discard this: Implement the method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS of class ZCL_BADI_SC_WC (in case you didn't know, in this method you can specify an "default" approver in case that the determination of approver in GET_APPROVERS_BY_AREA_GUID fails). The idea is to specify an default approval and see how it behaves:
If the user you indicated in the method GET_FALLBACK_AGENTS appears as approver, then yes, the problem is arises from implementation GET_APPROVERS_BY_AREA_GUID, in which case it could be a data problem (peharps in pposa_bbp?). You could also check in TX SU53 with the users with this problem to see if there's a missing authorization objetc.
If, in the other hand, the "default" approver is not shown, it means that the process level buyer determination is not even called, so you should check in more detail ZSRM_WF_BRF_0EXP000_SC_APP100 and /SAPSRM/CL_WF_PROCESS_MANAGER > Determine process restart –method ----- (i have never used this method, so i could not tell if it could be the source of the problem).
Also, you could implement the method GET_FALLBACK_AGENTS in this way so the default approver would be the WF administrator indicated in the customizing (or you could just append directly any user you want):
METHOD /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_FALLBACK_AGENTS.
   DATA: lv_admin_expr TYPE swd_shead-admin_expr,
         lv_admin      TYPE swd_shead-wfi_admin,
         lv_admin_type TYPE sy-input,
         ls_agent      TYPE /sapsrm/s_wf_approver.
   CALL FUNCTION 'SWD_WF_DEFINITION_ADMIN_GET'
     IMPORTING
       default_admin_expr = lv_admin_expr
       default_admin      = lv_admin
       default_admin_type = lv_admin_type.
   ls_agent-approver_id = lv_admin.
   APPEND ls_agent TO rt_agent.
ENDMETHOD.
Error of agent determination:
Please let me know the result of the test with the implementation of method GET_FALLBACK_AGENT. By doing this we could ensure if really the problem is in method GET_APPROVERS_BY_AREA_GUID or before. I just made the test in our system and I'm almost sure that you wont get the default approver, but i could be wrong.
Any question please let me know.
Best regards
Cristian R.

SRM 7.0 - Process controlled workflow

Hi,
Landscape - SRM 7.0 SP05
Workflow - Porcess controlled
Scenario - Self service procurement
Problem:
1. We have mulitple level approval workflow for the shopping cart. I am using standard workflow task- 40007953 and using /SAPSRM/BD_WF_RESP_RESOLVER badi to determine agents.
2. All the potential approvers (managers) are determined correctly by this badi but the issue is work-item is sent to all the approvers at the same time where as the requirement is to sent the work-item to each approver in series i.e. only when the work-item is approved by the lower level manager, it should go to the higher level manager. Currently, this workflow task sends the work-item to all potential approvers at one go who can start working on parallely which is not desired.
Could anyone please help me to resolve this?
Please note that adding additional process steps in the process-level configuration was the option but we could not opt for that at this point of development as we have gone too far in terms badi development for agent derterminiation
Thanks & regards,
Amit

Amit,
It is not possible to send the work item to people in sequence by configuring only one process level. If you have only one process level, the agent determination will only be applicable to that process level. If you are trying to assign multiple agents to that step, then all will get the work item at the same time.
I recommend doing one thing, Create multiple process levels(= no of approval levels you want). For each process level you keep same event and expressions. But your agent determination badi implementation need to be tweaked. Here is how you can do that
Use Parameters along with agent determnation badi implementation. In other words derive Agents based on the value of parameter using your badi implementation. This parameter can be configured in Process Controlled Workflow Configuration.
Example,
Process step 1 - WF_BADI - Parameter1
Process step 2 - WF_BADI - parameter2
Now write some code in the WF_BADI to pick up particular agent if parameter value is Parameter1 , pick another agent if parameter value is parameter2. Doing this way you wont ve to redesign your BADI implementation as you are able to break up the Agent logic based on parameter values.
Virender Singh

How to trigger standard task manually in Process controlled workflow?

Hi All,
I would like to trigger a task mannually in BRF, process controlled workflow. My requirement is to send an approval notification to the approvers at the current approval level, at any instance by the requestor of the shopping cart. In that case, will it be possible to trigger the standard task 40007953 (SRM Shopping Cart Approval (1)) with the workitem of Shopping cart under consideration?
I have tried searching for the same in SDN and other forums but most of the information was regarding application controlled workflows. None of those function modules seems to be working in PCW.
Any pointers on how to trigger a standard task (using FM or code) in BRF(process controlled workflow) environment is also highly appreciated.
Thanks,
S.H@ri

Hi,
Use this FM [SAP_WAPI_START_WORKFLOW|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/bb9100f8-0c01-0010-ac8e-e017351f3fc1].
Regards,
Surjith

SRM 7.0 Process Controlled Workflow-Level Type in Process level config

Hello Experts,
In SRM 7.0 for Process controlled workflow,for Level Type in Process Level configuration we have 3 different options
1) Approval with Completion
2) Approval
3) Automatic(System User)
Can you plz explain what is the difference between these 3 diffrent potion for Level Type in Process Level configuration.
Your help will be highly appreciated,
Thanks & Regards,
RKS

1. Approval with completion : This allows approvers to make any changes to document while approving. Generally you define this type for buyer in SC approval.
2. Approval : above minus change
3. Automatic (system approval) : If no process level is determined, you need to set up a process level with automatic approval to approve the document by system.

Inconstancy in Approval Workflow- Process Controlled Workflow

Hello Experts,
We are in SRM 7.0 classic scenario using process controlled workflow and facing an issue as described below:-
During the approval workflow, we are observing that in
Case 1: When approver3 is forwarding the work item to approver10, the approver10 in not getting the work item in his Inbox. However, when we see the log detail in SWI6 the status is shown as u201CREADYu201D
Case 2: We created a shopping cart with identical details as in Case 1 and followed the same approval process i.e.Approver3 forwarding the work item to approver10, however in this case approver10 is getting the work item in his Inbox and when we see the log details in SWI6 the status is shown as u201CCOMPLETED"
We tried this scenario for 10 times and we found that in 2 cases the approval status is showing as u201CREADYu201D while in other 7 cases the approval workflow got completed.
Can you all experts please help us understand why this is happening and how can be find the root cause i.e why Case 1 is in u201CREADYu201D status for last 2 days.
We seek your help in understandingroot cause so that we can eliminate any inconsistency in future.
Any pointers to resolve this issue will be highly appreciated.
Thank you in advance.
Regards,
RKS

Use class /SAPSRM/CL_WF_APV_FACADE. This is used by standard SAP WF Analysis.
Methods - RETRIEVE_PROCESS_HISTORY, GET_CURRENT_PROCESS_STATE, CREATE_PROCESS_FORECAST.
To analyze more, check the program /SAPSRM/WF_CFG_ANALYSIS_002. Check lines 209...216 (These Lines pull Previous Approved Steps, Current Process Step & Gets the approval forecast). However the REJECTED Items (Accept Decision) work little different (which is not captured by this report).
To Identify the current approval process awaiting decision by the requester of the cart, use method GET_CURRENT_PROCESS_STATE, return parameter structure /SAPSRM/S_WF_PROCESS-PROCESS_LEVEL_LIST-DECISIONSET_LIST-ITEM_STATUS_LIST gets you the current status of the item (ACCEPTED, REJECTED, OPEN, INQUIRED). If ITEM_STATUS_LIST-ITEM_STATUS EQ 'REJECTED', then the WF is waiting for acceptance/resubmission from the requester.
To your specific need, pass DOCUMENT_GUID to the class /SAPSRM/CL_WF_APV_FACADE=>GET_CURRENT_PROCESS_STATE get the return parameter /SAPSRM/S_WF_PROCESS. It will give you PROCESS_LEVEL_LIST. Then loop through DECISIONSET_LIST. It contains Table Types of AGENTS_LIST, ITEM_STATUS_LIST, WORKITEM_LIST. At /SAPSRM/S_WF_PROCESS level, you can get all the details of the current process level details
Thanks,
SC

Shopping Cart - Process Controlled Workflow - replace standard task

Hallo,
I am on SRM 7.0 SAPKIBKV09 using NWBC.
I use Process Controlled Workflow for Shopping Cart, and in the process schema definition,
I replaced the standard workflow task 40007952,
(with name - SRM Shopping Cart Completion),
with a copy of task 40007952, task 90000010
(with name - SRM Shopping Cart BUYER Completion)
I did that for the following Reason: to ensure that in the Shopping Cart Approval Log, I can distinguish between diffrent approval level, all of type completion.
Issue is that now when approver is executing the task from NWBC, I get the following error:
´No default action found for task TS90000010´
Any idea?
tried to apply Note 1409276 - Not all tasks have default action in inbox config, (as this applies to SAPKIBKV06)
but no success.
Thank you
Marco

Hi,
I wanted to add that there is standard report /SAPSRM/IBO_FILL_TABLES in SRM 7.0 that updates these tables for all standard tasks:
IBO_C_WF_ACS
IBO_C_WF_APS
IBO_C_WF_CAS
IBO_C_WF_TAS
IBO_C_WF_TTAS
Use these views in SM30 to create entries for customer specific tasks:
IBO_V_WF_ACC
IBO_V_WF_APC
IBO_V_WF_CAC
IBO_V_WF_IRA
IBO_V_WF_TAC
IBO_V_WF_TTAC
Best Regards,
Marcus
Edited by: Marcus Mock on Jun 6, 2011 11:56 AM
Edited by: Marcus Mock on Jun 6, 2011 11:59 AM

Process Control Workflow Configuration error on portal

Hi Experts,
We are using process controlled workflow for BUS2121 and activated a BC Set "/SAPSRM/C_SC_600_000_SP04" Shopping cart without approval.
For this We have created a Event and a Expression in BRF as constant for Process schema evaluation. No approval is required as of now. But when try to shop from the portal it shows a dump as:
The following error text was processed in system SRD : Dynamic type conflict when assigning references
The error occurred on the application server dl3803_SRD_40 and in the work process 2 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: INIT_BRF_TRACE of program /SAPSRM/CL_WF_BRF_MSG=========CP
Method: CONSTRUCTOR of program /SAPSRM/CL_WF_BRF_MSG=========CP
Method: INITIALIZE_BRF_MSG of program /SAPSRM/CL_WF_BRF_MSG=========CP
Method: /SAPSRM/IF_WF_RULE_CONNECTOR~EVALUATE of program /SAPSRM/CL_WF_BRF_CONNECTOR===CP
Method: /SAPSRM/IF_WF_RULE_CONNECTOR~EVALUATE of program /SAPSRM/CL_WF_SCHEME_PROVIDER=CP
Method: GET_SCHEME of program /SAPSRM/CL_WF_SCHEME_PROVIDER=CP
Method: GET_PROCESS_SCHEME of program /SAPSRM/CL_WF_CONFIGURATION===CP
Method: CREATE_PROCESS_LEVEL_SEQUENCE of program /SAPSRM/CL_WF_CONFIGURATION===CP
Method: CREATE_PROCESS_INSTANCE of program /SAPSRM/CL_WF_PROCESS_MANAGER=CP
Method: CREATE_PROCESS_FORECAST of program /SAPSRM/CL_WF_APV_FACADE======CP
Kindly help to solve this problem.

Hi Anand,
I am facing the same problem. Were you able to resolve that issue? if so, what is the solution? I don't find any relevant note for this.
Probelm: BRF is activated and when you do save/check on SC, throws short dump with error message as
"Dynamic type conflict when assigning references".
"MOVE_CAST_ERROR" "CX_SY_MOVE_CAST_ERROR"
Thanks
Akbar

Advantage of Process-Controlled Workflow

Good Morning!
What are the advantage of Process-Controlled Workflow? (and/or what are the advantage of Business-Rule-Framework?)

I am looking at a SRM 5.5 upgrade to SRM 7 and moving to PCW represents issues and risk to me.
The SAP Migration program /sapsrm/pr_wf_migration_cfg does not deal with the N Step Badi Wf's.
SAP's recommendation is to complete all active Wf's are restart with PCW which means finalising all approvals restarting Approvals using PCW from the start,
SAP recommend ALL processes should be moved to PCW from ACW in a production environment.
If your trying to implement a ACW N Step Badi in PCW then you will probably be looking at Resp Resolvers that refer to a Badi implementation where you will need abap code.
Not sure about a flexible set of approval levels, but think that's another Badi implementation, with abap code.
Not over impressed, I'm afraid. Better structured abap program code in the N Step BADI could be an improvement

Process controlled workflows- basic questions

Hi,
I am new to SRM 7 process controlled workflows.
I need some help designing the process controlled worlflow for n step approval of shopping cart.
If there are n conditions to be checked for a cart before deetrminig the no of approvers,then does that mean for a BO(in my case Shopping cart),there will be n process schemas or just one process schemas with n process levels?
Also under each process schema,I see multiple expressions/process levels.Does the column "level sequence no" determine the sequqnce of the task in the whole approval process?
Please advise.

Hi Saravanan,
Thanks for the prompt response!
Based on your inputs,I think I need to go with option 2 as based on the data in shopping cart e.g. product category,spend limit,total value and a/c assignment catgeory,the no of approvers are determined.
The flow is like:
cond 1: check the prod category,if true,add 1st approver.
cond 2: check reqeuseter spending limit with total value fo cart,if true,add further approver or approvers
cond 3: check a/c assgt category,if true for a particular catgeory,add new approver or approvers using RFC call.
cond 4: check ship-to-address,if a local address,add buyer as last approver.
For a given cart,one or multiple conditions from the above may be true.But the sequence for the cosnidtions is as defined above.
As per my understanding,I need to create only one process schema for "Shopping cart" and then create different BRF expressions for each of the above conditions right?E.g. cond1>level1,cond2>level2 etc...Please advise.
Also under process schema,process level configuration,I see one column for "resp resolvername".What do I need to enter here?My understanding was that this entry will be responsible for determining the approver values...Pls confirm.
Also if I go with option 2,you said BADI SAPSRM/BD_WF_RESP_RESOLVER' will have to be implemented for determining approvers.So the logic for determining the approvers for each of the above conditions will be implemented in this single badi?
Pls advise.
Also in the event linkage,I need to actiavte only the two entries /SAPSRM/CL_WF_PDO/SRM_PROCESS_START and /SAPSRM/CL_WF_PDO/WS40000014 right?
Also regarding the workflow template,is WS40000014 the only template for all business objects i.e. Shopping cart and PO?
Thanks again for your time and inputs.

Approver not determined process controlled workflow in SAP SRM 7.0

Hello all,
I have setup process controlled workflow in SAP SRM 7.0 EHP3 for shopping cart approval.
I have 4 approval levels.
I have used item-based Decision for entire document because for some items i want system approval.
In implementation of BADI /SAPSRM/BD_WF_RESP_RESOLVER, in the method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_AREA_TO_ITEM_MAP, i am skipping the items for which i want system approval.
Also in method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_APPROVERS_BY_AREA_GUID of BADI implementation class, i am keeping the approver table empty for the step which i want system approval.
For example i have 1 item in shopping cart and for 1st step, based on some accouting criteria, i want system approval for 1st level and the workitem should go directly to 2 approval step when shopping cart is ordered. This is not happening.
But if i have multiple items, and one item should have system approval based on some criteria and the 1st approval level should be system approval and other item should go to the 1st approver. This is happening and showing 'system' approver for item1 and 'appr_xyz' for item 2.
For shopping cart having only 1 item, If i approve the shopping cart in this state only, it doesn't go to any approver and is not usable.
am i missing anything in BADI /SAPSRM/BD_WF_RESP_RESOLVER??
Please let me know.
Regards,
Yayati Ekbote

Hi Adrian,
Yes it is possible to display custom workflows in the Universal Worklist, However, I am not sure what you are trying to do with a routing table. If the workitems are of type decision, you can use UserDecisionHandler (action handler) configured in the XML file to use the Approve/Reject functionality - we are talking about webflow connector here correct? R/3 connector?
Regards,
Beth Maben
EP - Senior Support Consultant II
SAP Active Global Support
Global Support Centre Ireland
**SDN Forum Moderator:
SAP Enterprise Portal: Application Integration
**SDN Universal Worklist Wiki:
http://wiki.sdn.sap.com/wiki/x/ehU

Process controlled workflow - SC process schema evaluation

Hi experts,
at the moment I'm using the n-step item level approval in SRM 5.0.
We are implementing SRM 7.0. With the new process controlled workflow I'm not sure how to
implement the logic of our "old" system.
Depending on category and item value the SC item has to be approved by 0 - 7 users.
I've created an event which finds a Z-process schema via FM.
In the FM I've tried to change the process schema (debugger) for one SC item.
But the schema has been changed for all items.
Is it possible to use different process schemas for items?
When yes how can I set the schema e.g.
item 10 schema1
item 20 schema1
item 30 schema2
item 40 schema1
Thanks in advance for your inputs!
Regards
Stefan

Hi,
Schema Evaluation is document header level.
There are 2 ways for implementation.
1. Schema Evaluation returns Schema name. For example, 1 step approval, ... 7 step approval
2. 1 Fixed Schema and 7 level evaluations. 1 Schema has 7 approval steps and each evaluation returns true or false.
You have to implement GET_AREA_TO_ITEM_MAP method of Agent BADI to exclude/include items.
BTW. If you set workflow framework as Application-Controlled Workflow, your old workflow logic works without any change.
Regards,
Masa

Process controlled Workflow is not starting

Hi,
I have problems with implementing an own process-controlled workflow. The "Sample BC Set for Process Level Definition" /SAPSRM/C_SC_600_001_SP04 is working fine. However I do not succeed in triggering a customer Process Schema for BUS2121.
The (first?) problem can be duplicated as following:
1. BC-Set /SAPSRM/C_SC_600_001_SP04 is activated
1.1 When creating a shopping card (Web Portal) a approver ("Head of organizational unit" in OrgManagement) is displayed in the Details (Approval-Workitem is created when saving the shopping cart)
--> OK
2. Deactivation of Process Schema 3C_SC_600_001 (replace Eval.IDs with customer Eval.ID which contains always false expression)
--> When creating a shopping card (Web Portal) no approval data is displayed in the Details
--> OK
3. Copy Process Schema 3C_SC_600_001 into ZC_SC_600_001; replace customer Eval.ID with original Eval.IDs (Boole; no process schema in expression (Eval-ID 3EV_SC_600_001_100; Expression 3B_SC_600_001_100: "Execute always"))
--> When creating a shopping card (Web Portal) no approval data is displayed in the Details
--> NOT OK; the same result as with 1.1 is expected
Why is 3. not working? Any ideas would be very welcome.
Best regards

In most cases, this means that the 'Start Process' is not configured correctly. Take a look at the following:
1. make sure that the Wf assigned to your start process is active
2. make sure that reference numbers are configured and assigned to your process
3. assign a user to receive error messages when an error occurs
Thanks,
Derrick Banks

Process Controlled Workflow - 1-step approval for shopping cart approval

Hi,
I have configured a one-level approval for SC (Process Controlled Workflow):
Object Type: BUS2121
Additional 1 level under schema: 3C_SC_600_000 (the last level is the automatic approval)
Level Type: Approval with completion
Eval ID: 0EV_SC_SL1
RR Name: RR_SPENDING_LIMIT_APPROVER
RR Param: USTONY.Y (I hardcoded it using my user ID, for the moment)
Task ID: 40007953 (I have checked, it's generalized as well)
Decision Type: Item-based decision for entire document
For PPOMA_BBP:
Under my org unit (Position):
Approval Limit: 1000
Output Limit: 1000
I didn't do any BADI implementations yet.
During creation of SC by other user, before "Order" the SC, the approval preview can show correctly that the Processor is as indicated in the config.
Once the SC is ordered, the whole step is gone and the event linkage becoming delinked (because there is error, and according to the config in SWEQADM).
However, I cannot find the workitem (no workitem generated) and SLG1 does not give any clue whatsoever.
I tried debugging method APPROVAL_LIMIT, and it seems fine as well.
Please help, what did I do wrong here?
Thanks,
Tony Y

Hi Sahil,
I even changed to first process level to:
Level Type: Approval
Eval ID: 0EV000
RR Name: RR_MANAGER
RR Param: (Blank)
Task ID: 40007953 (I have checked, it's generalized as well)
Decision Type: Decision for entire document
Under PPOMA_BBP:
I made myself as a head of the org unit with the role manager.
The requester is "Exclude" the role manager.
The agent can be determined now.
But the workitem ID is still cannot be generated. It's always no workitem generated.
Please everyone, any help?
Thanks in advance,
Tony

Process control workflow issue with Approvers

Similar Messages

Maybe you are looking for