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.

Similar Messages

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 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.

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.

Process controlled workflow - Reject SC approval

Experts,
I configured process controlled workflow in SRM 7. My approval process is working fine but i need to send a notification e-mail when the approver rejects the SC approval. The requisitioner will receive this email saying that the SC was rejected.
Is there any chance to do this with configuration? Do you have to use a new expression linked to an event to perform this ?
Thanks for your help,
Best regards,
Mário

Hello Mario,
See IMG path below:
SAP Implementation Guide -> SAP Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Business Workflow -> Process-Controlled Workflow -> Business Process Configuration -> Define Recipient of Notifications
For scenario "Approve Shopping Cart", you can define user role which will receive notification in the event of "Rejection".
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.

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

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 Process Controlled Workflow

Hi Exports,
I have created a Process schema for SC object type (BUS2121)..
Looks like my process levels are trigged before the shopping cart is actually ordered by the user..
Is this a normal behavior? or I am missing any configuration? or I need to have a additional process level initially to check whether the SC completed?..
Please advice..
Thanks in advance
Bharath

HI,
Yes. That is correct task ID.
FYI. Task ID List for Process-Controlled Workflow
SRM Contract     BUS2000113               No Completion Task
          40007980     SRM_CT_APPR1     SRM Contract Approval
          40008003     SRM_CTR_Acc     Accept Decision / Adjust Document
          40007997     SRM_CTR_Revi     Revise Document
          40107926     SRM_CTR_RW     review document
SRM Shopping Cart     BUS2121
                                           40007952     SRM_SC_COMP1     SRM Shopping Cart Completion
          40007953     SRM_SC_APPR1     SRM Shopping Cart Approval (1)
          40007954     SRM_SC_APPR2     SRM Shopping Cart Approval (2)
          40007994     SRM_SC_Acc     Accept Decision / Adjust Document
          40007936     SRM_SC_Revi     Revise Document
          40007945     SRM_SC_RW     Review Document
SRM RFx     BUS2200     40107917     SRM_BI_COMP1     SRM RFx Completion
          40007982     SRM_BI_APPR1     SRM RFx Approval
          40107922     SRM_RFx_Acc     Accept Decision / Adjust Document
          40007998     SRM_RFQ_Revi     Revise Document
          40107927     SRM_RFQ_RW     Review Document
SRM Purchase Order     BUS2201
                                           40007973     SRM_PO_COMP1     SRM Purchase Order Completion
          40007974     SRM_PO_APPR1     SRM Purchase Order Approval
          40007995     SRM_PO_Acc     Accept Decision / Adjust Document
          40007996     SRM_PO_Revi     Revise Document
          40107924     SRM_PO_RW     Review Document
SRM Supplier Quote     BUS2202               No Completion Task
          40007981     SRM_QT_APPR1     SRM RFx Response/Bid Approval
                    No Adjust task
          40007999     SRM_QTE_Revi     Revise Document
          40107928     SRM_QTE_RW     Review Document
                    No Completion Task
          40008000     SRM_QT_APPR2     SRM Bid Approval
                    No Adjust task
          40107934     srm_bid_revi     Revise Bid
          40107935     srm_bid_rw     Review Bid
SRM Confirmation of Goods/Service     BUS2203               No Completion Task
          40007987     SRM_CF_APPR1     SRM Confirmation Approval
                    No Adjust task
          40008004     SRM_CF_Revi     Revise Document
          40107929     SRM_CF_RW     review confirmation
SRM Incoming Invoice     BUS2205               No Completion Task
          40008005     SRM_IV_APPR1     SRM Invoice Approval
                    No Adjust task
          40008006     SRM_IV_Revi     Revise Document
          40107925     SRM_IV_RW     Review Document
Auto          40007988     SRM_AUTOAPP     Automatic Approval
Auto          40007989     SRM_AUTOREJ     Automatic Rejection
Regards,
Masa

SRM Process Controlled Workflow - Re-start using FM BBP_PD_SC_UPDATE

Hi All,
We are upgrading from SRM4.0 to SRM7.0 SP07 in classic scenario. We switched to Process Controlled Workflow.
We have a CUSTOM application where the requisition items are entered and a Shopping Cart is created in SRM through Function Module BBP_PD_SC_CREATE. When the Shopping Cart is created in SRM , the Process Controlled Worflow is triggered successfully.
In the custom application , we allow users to do changes to the requisition that are awaiting approval.The changes are updated in SRM Shopping Cart through function module BBP_PD_SC_UPDATE. It is noticed that the workflow process levels are not re-started after the shopping cart is updated through FM BBP_PD_SC_UPDATE.
However , the process levels are re-started when the change is directly done to the Shopping Cart in SRM POWL. We want the process levels to be re-started even when the changes are done through BBP_PD_SC_UPDATE. The users are used do changes to the requisition through the custom application. We also noticed that system does not go through BAdI /SAPSRM/BD_WF_PROCESS_RESTART when changes are done to the SC through BBP_PD_SC_UPDATE.
Is there any way that we can trigger process level re-start when SC is changed through FM BBP_PD_SC_UPDATE
Thanks
Sukumar

HI ,
       This is not the correct way of updating the SC. please check the below process...
       first you try to get the SC document in Edit mode and this can be done only SY-UNAME should requester of the SC or( user who are changing the SC should be in the Org structure ). ( This point why i mentioned is you mentioned that your editing through custom application ).
note : use try and endtry and catch the exception when u get the SC document in Edit mode.
DATA: lo_pdo_sc             TYPE REF TO /sapsrm/cl_pdo_bo_sc_adv.
      "Instance SC PDO Layer
      lo_pdo_sc ?= /sapsrm/cl_pdo_factory_sc_adv=>get_instance( iv_header_guid   = p_guid "ps_shopping_cart-guid
                                                                iv_mode          = /sapsrm/if_pdo_constants_gen_c=>gc_mode_edit ).
   now you do what ever changes to the document. I mentioned points below.
        "Get Item Details
      lo_pdo_sc->/sapsrm/if_pdo_bo_sc~get_item_detail
do changes to the items of the SC.
       "Update SC Items
      lo_pdo_sc->/sapsrm/if_pdo_bo_sc~update_items
       "Submit Update
      lo_pdo_sc->/sapsrm/if_pdo_base~submit_update
       "Save SC
      lo_pdo_sc->/sapsrm/if_pdo_base~save
      or order the SC again.
      COMMIT WORK AND WAIT.
regards,
Devi

Complexity of using N-step BADI in SRM 7using Process controlled Workflow.

Hi,
Just as a big thought,
I have a Shopping Cart requirement, Here i am asked to develop a Custom workflow for SRM 7.0.
And the client is looking for us to use Process Control Workflows i.e(BRF integrated one).
I need to understand the complexity of using a N-step BADI.
How would be the complexity level if I use a N step BADI( ie Multiple approval levels on Line Item Based).
Kindly tell me the complexity of Using it and if any one has come across some requirement like this, then explain me that how did you face the situation.
Expecting an Earliest Response.
Thanks,
Shanky

Hi,
Is your project SRM 7.0 implementation project then you have to go for Process Controlled Workflow and if your project is upgrade then you can still go with Application Controlled Workflow but down line this has to switch to Process Controlled Workflow.
Best Regards,
Saravanan

SRM 7.0 Process-controlled Workflow 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

Hi..
what do you see in SLG1? .. i think your process level Eval.id result is false, that is the reason workflow is not kicking of
1- level approval.. check your process level configure and try to use 0ev000 as a Eval.Id instead your custom Eval.Id and test..
Saravanan

Error during approval Process flow in Process controlled workflow

Hello Experts,
We are in SRM 7.0 classic scenario using Process controlled workflow.WE recently connected a new backend R/3 system to our SRM system i.e we now have 2 R/3 backend system connected to SRM system
It is regarding the two new additional account assignment categories that came into picture when we connected the new R/3 backend system to our SRM system, i.e. Asset and Network.
There seems to be some problem with the approval workflow for those SHC, that have such Acc *** Cats.
Please find below my obeservations:
- if you have just one line item in the SHC, and this item is either booked on Asset or on Network, than everything goes fine. After the Acc *** approval, the PR is created in R/3
- if you have SC with a mix between an "old" Acc *** Cat (Cost Centre, WBS and Order) and one of the "new" Acc *** Cats, than the workflow is not working as required --- the manager, that is responsible for the accounting approval of the two positions (e.g Cost Centre and Asset) gets only one work item in his approval overview --- in that work item, the two positions are there, but the Asset one is grayed out --- so, the Manager approves only the Cost Centre positions and than the SC is no longer with the approver --- if you observe the SC now from the requisitioner point of view, the status of the line items in the approval process overview of both(!) lines is "approved", but the overall status of the SC is still "in approval"
Can you all experts plz let us know why this is happening and how this can be resolved?
Any pointers will be highly appreciated.
Thanks & Regards,
RKS

Hi,
What is Resp. Resolver Name and Decision Type in your Process Level Definition? Did you create custom agent BADI implementation?
Regards,
Masa

Dump on screen when configuring Process controlled workflow

Hi Experts,
I am facing 1 problem in SAP SRM 7 ehp1. I am configuring Process controlled workflow. Previous workflow settings was Application controlled workflow as its been upgraded from SRM 5. If i run a RFX (BUS2200) cycle in application controlled workflow environment, it works flawlessly.
But when i change my workflow framework to process controlled workflow for all Business Objects. I face a dump when I am creating an RFX. The dump on the portal is:
http://dl3803.ltisap.com:8040/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif
DATREF_NOT_ASSIGNED
No access possible via the 'NULL' data reference
Method: PARTICIPATING_IN_ACTIVE_WF of program /SAPSRM/CL_PDO_DYN_MDA_WF_ADJ=CP
Method: EDIT_DURING_WORKFLOW of program /SAPSRM/CL_PDO_DYN_MDA_WF_ADJ=CP
Method: /SAPSRM/IF_PDO_META_CONF_BO~GET_BO_HDR_ACTION_METADATA of program /SAPSRM/CL_PDO_META_CONF_PROV=CP
Method: /SAPSRM/IF_PDO_META_CONSUMER~GET_ACTION_METADATA of program /SAPSRM/CL_PDO_META_BO_RFQ====CP
Method: /SAPSRM/IF_PDO_META_CONSUMER~GET_ACTION_METADATA of program /SAPSRM/CL_PDO_META_BO_RFQ_ADVCP
Method: /SAPSRM/IF_PDO_META_CONSUMER~GET_ACTION_METADATA of program /SAPSRM/CL_PDO_META_HANDLER===CP
Method: UPDATE_ACTIONS of program /SAPSRM/CL_CH_WD_MAP_IDENT====CP
Method: /SAPSRM/IF_CLL_MAPPER~REFRESH of program /SAPSRM/CL_CH_WD_MAP_IDENT====CP
Method: /SAPSRM/IF_CLL_MAPPER~REFRESH of program /SAPSRM/CL_CH_WD_IDEN_MAP_RFQ=CP
Method: OVERRIDE_LEAVE_INIT_SCREEN of program /SAPSRM/CL_FPM_OVRIDE_OIF=====CP
& when i check in st22. I get the dump as:
Category               ABAP Programming Error
Runtime Errors         DATREF_NOT_ASSIGNED
ABAP Program           /SAPSRM/CL_PDO_DYN_MDA_WF_ADJ=CP
Application Component SRM-EBP-PD
Date and Time          17.12.2011 15:46:56
and get dump at:
1 method PARTICIPATING_IN_ACTIVE_WF.
2   " this method returns ABAP_TRUE if the logon user has an active work item,
3   " i.e. he participates in an active approval workflow process.
4
5   DATA lv_curr_workitem_id    TYPE /sapsrm/wf_workitem_id.
6   DATA lr_process_info        TYPE ref to /SAPSRM/S_PDO_WF_PROCESS_INFO.
7
8   " the default:
9   rv_participates_in_active_wf = abap_false.
10
11   " The scenario is not valid for application-controlled workflow:
12   " Any agents who may edit the document (approver and requester)
13   " enter "Edit" mode right-away. No special handling possible.
14   lr_process_info = io_apf_md_context->get_process_info_ref( ).
>>>   IF lr_process_info->wf_version NE /sapsrm/if_wf_process_c=>GC_APF_VERSION_0200.
16     return.
17   endif.
18
19   " check if a valid workitem exists
20   lv_curr_workitem_id = io_apf_md_context->get_workitem_id( ).
21   IF lv_curr_workitem_id IS INITIAL.
22     RETURN.
23   ENDIF.
the only configuration I change in the system is I changed the workflow framework to process controlled workflow.
Kindly help.
Thanks
Anand

Hello Anand,
As per standard SAP recommendations the application-controlled workflow framework is only intended to be used if you are upgrading from SAP SRM 5.0 or earlier and you need to continue using your existing work-flows.
The default workflow framework setting is the process-controlled workflow from SRM 6.0 on-wards and the user will be provided a option to switch to the application-controlled workflow framework. The option to switch to process-controlled workflows is available only after you have once switched to application-controlled work flows but there will be a big caution that " If you switch from the application-controlled workflow framework to the process-controlled workflow framework; once a process-controlled workflow has been run, it is not supported that you switch back to application-controlled work-flows".
As per the details given i got a feel that we have tried executing the scenario by switching between application and process controlled workflow and hence the system have become inconsistent and its dumping.
I suggest you to raise a OSS ticket to SAP to resolve the issue.
Best Regards,
Rahul

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

Similar Messages

Maybe you are looking for