Issue in Process Level Workflow

Dear SRM Workflow Experts,
I have following issue for workflow in SAP SRM 7.0
We have configured item level shopping cart approval workflow using process level configuration. Total four process Levels are configured for Audit/Deman Challenge/Tax and Financial approval.
Process Level Config Details
Level. Apr.Type Evval.Id                              Description                               Resp.Resover                            Decision Type
100     Approval ZEV_SC_DMCH_LEVEL1   Demand Challenge Workflow ZRR_DEMAND_CHALLENGE       4
200     Approval ZEV_SC_AUDT_LEVEL1   Audit Approval Workflow        ZRR_AUDIT                           4
300     Approval ZEV_SC_ITAX_LEVEL1    Tax Approval Workflow           ZRR_TAX                           4
400     Approval ZEV_SC_LEVEL3              Financial approval                    ZRR_COSTCENTER_APPROVE      4
We have a issue for the shopping cart with multiple items, once process level is applicable for first item it becomes mandatory for another items even though BRF expression rule for process level is not valid. It looks like my BRF event is executing only once for Shopping Cart and it's not getting trigerred for each line item.
Please suggest how I can resolve this issue.
Thanks & Best Regards,
Navnath Bondarde

Thanks for quick response,
Actually I am using GET_AREA_TO_ITEM_MAP method in the /SAPSRM/BD_WF_RESP_RESOLDER BADI.
I am not creating the Responsibility Area for the items for which Approver not needed.
Please refer following code, please note AREA_ID field will be empty for the items for which approver not needed. For these items workflow is getting triggered with error "Strategy ZRR_AUDIT' did not determine any approver.
LOOP AT lt_item_to_area_map REFERENCE INTO lr_item_to_area_map.
    AT NEW area_id.
    For each area id a new responsibility area is created, this instance can
    later be retrieved in
    method GET_APPROVERS_BY_AREA_GUID to return the list of responsible
    agents
      IF not lr_item_to_area_map->area_id is initial.
        lo_area = /sapsrm/cl_wf_area=>/sapsrm/if_wf_area~create_instance(
          iv_area_type         = /sapsrm/if_wf_process_c=>GC_AREA_TYPE_ADHOC
          iv_leading_object_id = lr_item_to_area_map->area_id
        ls_area_to_item_map-area_guid = lo_area->get_guid( ).
      ELSE.
        ls_area_to_item_map-area_guid = /sapsrm/if_wf_process_c=>gc_nil_guid.
      ENDIF.
    ENDAT.
    IF NOT ls_area_to_item_map-area_guid EQ /sapsrm/if_wf_process_c=>gc_nil_guid.
        ls_area_to_item_map-item_guid = lr_item_to_area_map->item_guid.
        APPEND ls_area_to_item_map TO rt_item_to_area_map.
    ENDIF.
ENDLOOP.
Thanks & Best Regards,
Navnath Bondarde

Similar Messages

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.

Issue in N level workflow of shopping cart

Hi all,
SRM5.0 and ECC5, using ECS scenario
We are using the N level workflow ( SC approval workflow and not item level workflow) with the BADI for determining the approvers of the shopping cart.
The following are issues faced during rejection:
1. When the 1st approver rejects some of the line items and approves others, The SC is sent back to the requester or. the requester accepts the changes, the SC instead of going to the next level of approvers gets approved.
I have debugged and found that the actual index is set to 2 and the next level of approvers are determined correctly in the BADI, once it is out of the BADI, something happens and the SC is approved and it doesn't go for approval.
2. When the 1st approver approves all the line items and the 2nd approver does a partial rejection, the SC is sent back to the requester and once the requester accepts the changes, the workflow restarts and the approvers are redetermined again.
For the 2nd issue, if its a standard process, Can onyone provide me with a document or a OSS note which can be used for substantiating it. Does this behavior correspond to the back and forth process of N level workflow?
Thanks and Regards
Kishan

Hi Munna,
The code just determines the approvers for each level, this works fine when I debug but it changes after the control comes out of the N level BADI.
Is there any other check which I need to do?
Regards
Kishan

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.

Approval Level in Process Controlled workflows

Hi Sap Gurus,
How can i find the number of approval levels in process controlled workflows for Shopping Cart, Purchase Order....
Thanks in advance

Hello,
IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Business Workflow > Process-Controlled Workflow > Business Process Configuration > Define Process Levels
For concerned object type, select "Process Schema Definition" directory.
Then, select correct process level schema to display "Process Level Configuration" directory: here are the process levels defined.
Regards.
Laurent.

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.

Process Level Config in SRM 7.0 workflow

Hi,
I am implementing Process-controlled workflow in SRM 7.0 for the first time. We have identified some 5 levels of approver depending on the total shopping Cart value.
1. >= $XXX; Product Category manager (based on UNSPSC code at item level)
2. >= $x,xxx: Line manager
3. >= $xx,xxx; Cost Center manager (based on cost center)
and so on ..
As per my understanding,
First we need to create following Filter values for RESP_RESOLVER_NAME:
ZSC_PRODUCTCAT_MANAGER
RR_MANAGER
ZSC_COSTCTR_MANAGER
Then, based on these filter the following BAdi implementations will be called to get responsible approver list:
ZSRE_BD_SC_PRO_MGR
/SAPSRM/BD_WF_SC_RR_MANAGER
ZSRE_BD_SC_CCR_MGR
and the process level may have the following entries for BUS2121, Zevalution ID & Zprocess schema:
Level #     Level Type     Evaluation ID     Responsibility Resolver Name                     Task ID     Decision Type
100     Approval     ZEV_SC_001     ZSC_PRODUCTCAT_MANAGER     40007953     4
150     Approval     ZEV_SC_002     RR_MANAGER     40007953     4
200     Approval     ZEV_SC_003     ZSC_COSTCTR_MANAGER     40007953     4
999 automatic
Create the custom events & expressions:
Evaluation ID                          Expression                          SAP formula builder
ZEV_SC_001     ZE_SC_LEVEL_001     Total Shopping Cart value exceeds $ XXX
ZEV_SC_002     ZE_SC_LEVEL_002     Total Shopping Cart value exceeds $ X,XXX
ZEV_SC_003     ZE_SC_LEVEL_003     Total Shopping Cart value exceeds $ XX,XXX
Question:
Am I going in the correct way..or
Can we do it using SAP standard events, expressions or spending limit approver badi implementation with only one process level for RR_SPENDING_LIMIT_APPROVER, using some custom tables for Product Cat manger/Cost Center manager list.
Regards,
Bijaya

Hi all,
I have a client requirement like below,
A PO is in ordered status and if some one chages the PO value and if the changed value is more than 1000 Euros then the PO has to go through the approval process else it should go for an automatic approval.
Can any of you please guide me how to acheive this functionality.
Just for reference I am giving some details :
I have created an Eval Id (ZEVAL, this is the event), and this event linked to a expression(ZDET_SCHEMA: Function module for determining the schema), and I have 2 process levels for the schema
1 Level will have folowing details:
Level # Level Type Evaluation ID Responsibility Resolver Name Task ID Decision Type
100        Approval       ZE_PO_EXE                      ZE_PO_APP 40007953 4
and the evalutio id ZE_PO_EXE points to an expression(ZDET_PO_CALC Function module) ZDET_PO_CALC Function module will have the actual manipulation for calculating the price change and passes a result 'X' or space , if 'X' level 100 will get excecuted else level 2 will be executed.
2 Level will have an automatic approval
But some how this is not working as per the requirement.
Any info will be highly apreciated.
Thanks in advance
Krishna

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

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

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

Ddeleting duplicate approvers from each process level

Hi,
We are on SRM 7.1 ECS.
We have configured n step approval workflow(PCW) header level for shopping carts:
THe issue we are facing is deleting duplicate approvers so that only one work item is sent to unique approvers.AS the process levels are independant of each other,the approvers determined in one Process level are not know in other process levels which get triggered for a cart.
We have around 5 Process levels configred but sometimes the same approver(e.g.BUYER) ets fetched for each of the process levels which get triggered(We fetch approvers based on data in custom tables and SRM Org structure).
IN SRM 5,in n step badi,we could easily delete same approvres/duplocate approevsr from the table APPORVAL_TABLE.But in SRM 7,due to the process level config how can I determines or fetch in the current process level the approvers from previous process levels?The main idea is to delete duplicate approvers and just create one work item even thogh they could be approvers for multiple process levels.
Please advise.
Thanks in advance fior your time.

Hello
will you pls tel me how did you solve this ?
Even i am working on SRM 7 and need to know about this
Regards
sahil p

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

SRM 7.0 Process Controlled Workflow - Shopping Cart customising

Hi
I am trying to use my own task (copied from TS 40007953) in the shopping cart approval workflow. I have made my task a general task and I have added it to task grouo TG 40000003.
I also put my task number in the task id column in the process level customising.
When the shopping cart is ordered, the workflow is started correctly AND my task is used in the workflow log.
The workitem goes to the correct approver (portal UWL) but the task does not behave correctly. The approve/reject buttons are missing and it does not open.
Is there something I have missed?
Appreciate any ideas:)

Hi..
Any reason that you have customized task use to approve / reject the SC?..
Saravanan

Process Controlled workflow

Hello experts,
We are trying to use process controlled work flow for SC approval. Approval process will be multiple based on the amount of shopping cart. Somebody has already activated BC set for one step approval in the system. If i want to have my own process schema ( multiple approval ),what i supposed to do? Do i delete the existing schema attached to BUS2121 or create my own schema ?
How system will determine which schema needs to be picked up after creation of SC?
Regards,
Sagar

Hello Bharat,
Thanx for reply.
I have below cases for process controlled workflow.
1. No approval
2. One step approval
3.Multi level approval.
All the above scenario will be decided based on the Z field which we have added to SC header. My understanding in this case is to have three process schema for above cases. Name of schema will be decided by Evaluation ID.
Once the schema is decided then i need to define process level for each process schema.
Please let me know if i am on the right track??
Regards,
Sagar

Issue in Process Level Workflow

Similar Messages

Maybe you are looking for