Problem with Confirmation (BUS2203) Process Controlled Workflow SRM 7.0

Hi gurus,
I'm having a bit of trouble with the Process-Controlled approval workflow for the business object "BUS2203" (Confirmation) in SRM 7.0.
Basically, I've configured it to determine N-process levels, and for each level to retrieve the corresponding agents/approvers. When I am creating the confirmation, I go to the "Approval" tab and I can see all of my approvers there. Nevertheless, the moment I confirm an item (ie, put a confirmed quantity and press the confirm button) first I get the status "Awaiting Approval" and then when I close/or click the refresh button I get the status "Release Rejected".
Has anyone had this problem before with this workflow? Do you know if this is a standard error, or might I be doing something wrong? I tried to look through the OSS notes, but unfortunately couldn't find anything..
Please feel free to provide any idea that may be useful!
Many thanks...
Adi

Hi,
Can you paste your process definition? BRF event and expressions.
Does it work with SAP sample 1 step approval process definition?
Regards,
Masa

Similar Messages

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

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

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

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

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

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.

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

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.

Process Controlled Workflows VS Applicaiton Enabled Workflows-What to chose

G'Day All,
We are upgrading from SRM5.0 to SRM7.0
There are these bespoke shopping cart approval workflows developed previously. I have to do some sort of assessment to include
1) Why would we go for PCWs instead of just migrating the old ones in SRM 7.0 as business is pretty happy with the functionality they have got and are not interested in revising the workflow processes. Answer : Application enabled workflows are in maintainence mode so newer functionality would be delivered using PCWs.( is there any other justification ? )
2) Would we be able to map the existing workflow process to PCWs, here i need some pointers. I understand the PCWs are based on BRF though i don't know much about BRF( updating myself ). The key question i have is, whatever is there in bespoke workflow templates would i be able to replicate that using this i.e. a different technology. Since my exposure to either PCWs or BRF is not great so as a general rule i am asking, is it possible or are there any sort of technical limitations on what you can and what you can't do using PCWs which you could design using a normal workflow template?
I am sure this would be a common analysis which many of you might have done or are doing if you are involved in an upgrade.
An Interesting Fact : There is no documentation available on existing SRM 5.0 workflows as what differently they have done to standard. The only thing i know at this stage is they have a bespoke level 1 template which call different standard templates for n level approval process. The apporval process( agent determination ) is based purely on custom logic. I am not that worried about the agent determination as i know i could get that as rule evaluation in BRF. The crux for me is to understand how BRFcontrols or connects to workflow templates in this particular case and what permutation conbinations are possible.
So, i want to have a discussion on this and if possible some insight on all this new PCWs.
Hope to see some valuable comments.
Regards
Praveen

Hi everyone:
My question is the following.
We will implement SRM 7.01 with Process Controlled Workflow.
However in the manual is the following note:
Note: Even if you decide to use Process-Controlled Workflow in general,
there are a few workflows still on the old technology:
WS10400022 . Contract Alert Workflow
WS10000192 - Approval Workflow for Internal Users
WS10000209 - Approval workflow for new bidder/supplier
WS10000093/WS10000100 -Procurement Card Approval
Probably We will required some of this.
My question is if we are planning to configure process and application the correct strategy will be:
1.     Start the configuration with the application controlled workflow and then
2.     Follow with the change of the configuration application to process controlled workflow
3.     And configure the workflowu2019s in process.
u2022     Is there any problem when if we change the check application to process? Are there any chance that we loss the configuration?
u2022     Is there any problem in the functionality that both kinds of workflow (application-process) work at the same time?
u2022     If is possible to make change or maintenance of the application workflow?
Thanksu2019 a lot for all the help
Best Regards

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

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

Problem with Confirmation (BUS2203) Process Controlled Workflow SRM 7.0

Similar Messages

Maybe you are looking for