Shopping Cart Rejections

[Rick Bakker]

I assume you're talking about workflows that started after the transport?

On Fri, Jun 3, 2011 at 5:02 AM, BPT Consulting
<bptconsulting at sbcglobal.net>wrote:

>   Dale,
>
>
>
> Here are some other things I would check:
>
> Did you view the acceptance by contact person configuration in the new
> system – to see if transported correctly?
>
>
>
> Is it a fully rejected SC?  This configuration does not work for partial
> rejected SC.
>
>
>
> Did you have workbench transports as well as customizing (client dependant)
> transports – did they both move?
>
>
>
> Are task groups TG40000003 and TG40000007 set as general tasks?
>
>
>
> Did you transport normally or using BRF_TRANSPORT_SIMPLE?
>
>
>
>
>
> The events APPROVAL_PROCESS_DOC* are used by Alert Management to send
> notifications out and shouldn’t have anything to do with the process control
> Workflow.
>
>
>
> Regards,
>
> Thomas Maue
> --- On *Thu, 6/2/11, Ramki Maley <rmaley at erpworkflow.com>* wrote:
>
>
> From: Ramki Maley <rmaley at erpworkflow.com>
> Subject: Re: Shopping Cart Rejections
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Date: Thursday, June 2, 2011, 12:57 PM
>
>
> Hi Dale,
>
> Have you looked in the log (SLG1) and verified if your REJECTED event is
> being evaluated at all? I will be moving our BRF config  to a QA system soon
> and will have to see what happens.
>
> Regards,
> Ramki.
>
> On 6/2/11 11:38 AM, Dale Brown wrote:
>
>  We are running SRM 7.0 process controlled workflow.  We have configured
> the system in development to send work item back to orderer when shopping
> cart is rejected instead of having the workflow end as the system was doing.
>
> We did this by setting up a brf reject event calling an expression that
> checks current decision = REJECTED.  We then in the config for “acceptance
> by contact person” defined the new reject event for task 40007994.
>
> We also added SC to event schema for transaction type SHC .    This all
> works fine in development.    We have since transported up to a
> pre-production system and the rejections are back to ending the workflow.
>
> It looks like for WS40000015 in our development system the workflow goes to
> step SRM Document Owner interaction (WS0000026) , where in the system we
> transported to, the flow by-passes this step and eventually ends the
> workflow.
>
> Everything looks like it was transported correctly.  We have did swu_obuf,
> re-transported, etc.. but can not seem to get the workflow to behave like we
> want it (as it does in development).  We also notice in the system we
> transported to, that the
>
> email for the rejection is SAP’s standard email that shows it was started
> by event APPROVAL_PROCESS_DOC_REJECTED, sub cat
> APPROVAL_RESULT_NOTIFIC_NEW.  Does this need to be de-activated?  Is that
> causing the problem of not
>
> recognizing our config?  We don’t remember de-activating anything in
> development.
>
>
>
>
>
> *Dale R. Brown*
>
> *DUKE UNIVERSITY***
>
> *Sr. Analyst, IT
> OIT - Application and Database Services
> 919.684.5341*
>
>
>
>
> _______________________________________________
> SAP-WUG mailing listSAP-WUG at mit.edu <http://us.mc816.mail.yahoo.com/mc/compose?to=SAP-WUG@mit.edu>http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> -----Inline Attachment Follows-----
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu<http://us.mc816.mail.yahoo.com/mc/compose?to=SAP-WUG@mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110603/2c8f2f28/attachment.htm