PREQ WF: Release code R0 does not exist in T161E

[hari.bommaraju@accenture.com]

Dear Rick,

Thanks for the response!

This problem has been reported only for a single plant. It happens to be working fine for the remaining plants. So we thought that it might be some configuration related issue.

But then - I will do as suggested and revert back with the result!

Br,
Hari

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Rick Bakker
Sent: Tuesday, June 07, 2011 5:50 PM
To: SAP Workflow Users' Group
Subject: Re: PREQ WF: Release code R0 does not exist in T161E

Hello,

I assume you've googled the error, but just in case:
Please see if this helps:
http://forums.sdn.sap.com/thread.jspa?threadID=1041692
"The reason why this is throwing error is the WF container release
code has been defined with the type RM06B-FRGAB and this field has
check table from T161E. Change the data type and it should be fine."

regards
Rick Bakker
hanabi technology

On Tue, Jun 7, 2011 at 8:46 PM,  <hari.bommaraju at accenture.com> wrote:
> Hi All,
>
>
>
> I am facing a serious problem with the PREQ Item level approval workflow.
>
>
>
> Release strategy R0 is getting triggered and a workflow gets called - but
> the agent determination fails.
>
>
>
> I checked the rule and it has been found OK upon simulation.
>
>
>
> I tried to restart the workflow that went in to error because of failed
> agent determination - but it never came in to "In Process".
>
>
>
> I then decided to logically delete the existing workflow and start a new one
> using transaction SWUE.
>
>
>
> Surprisingly - I am unable to pass the mandatory parameter 'release code'
> with value R0. When I do an F4 - I find only one release code value "01" and
> there is no R0 value.
>
>
>
> What I did is - triggered the workflow with release code "01" and then from
> the workflow log tried to change the release code to R0.
>
>
>
> I get the following error message - "Entry R0 does not exist in T161E (check
> entry)"
>
>
>
> Did any body experience similar error? Is this a config issue?
>
>
>
> Please help!
>
>
>
> Br,
>
> Hari
>
>
>
> ________________________________
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the email by you is prohibited.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at 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


This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.