WL - 006 Error occured

Gavin Mooney gavinmooney at gmail.com
Tue Apr 25 11:54:43 EDT 2006


Thank Eddie,

With the entry removed from SWEC it's all working fine now.

 - Gavin

2006/4/25, Morris, Eddie <eddie.morris at sap.com>:
> Hi Gavin,
>
> This FM was introduced via note:
>
> * 764521 - Change pointer processing R/3 order outbound
>
> If you do NOT use Forecasting & Replenishment then the entry in SWEC
> can be removed. ie. remove the function module FRE_ORD_EVENT_PO_DB
> as I assume you use the entry in SWEC to raise event in any case.
> Please look at note 797775 on how to remove the entry.
>
> * 797775 - Entry in Transaction SWEC hinders workflow
>
>
>
> Regards,
> Eddie
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Gavin Mooney
> Sent: 25 April 25, 2006 16:01
> To: SAP Workflow Users' Group
> Subject: Re: WL - 006 Error occured
>
> Ok Bala,
>
> I don't know if our problems are identical but I found the problem here:
>
> Upon creation of a purchase order in ME21N, two events were being
> raised. One contained the Release Code parameter and was starting the
> workflow fine (when the linkage hadn't been set to error status) and
> the other didn't contain the Release Code and was erroring.
>
> There was an entry in SWEC to raise one of the events. The event
> container should have been filled by function module
> FRE_ORD_EVENT_PO_DB but a bit of debugging of the update task showed
> that this FM was exiting at line 38 because there wasn't an entry in
> table FRE_SEND_OPTION (in fact it bombs out so early you don't even
> need to debug to see why). Hence the event container wasn't being
> filled.
>
> I don't know if anyone knows much about that table...?... but it
> belongs to SCM and we here aren't using it. So I took the entry out of
> SWEC and now only one event is raised (I assume it's raised directly
> by the ME21N code), which contains the Release Code and kicks off the
> workflow without any problems.
>
> As I said - I don't know if that's any use to you. I'd be interested
> to know if other projects have that SWEC entry to raise
> BUS2012.ReleaseStepCreated...
>
> Regards,
> Gavin
>
>
> 2006/4/25, Gavin Mooney <gavinmooney at gmail.com>:
> > Funnily enough we have what appears to be exactly the same problem on
> > my project (620) with this workflow, the Release Code isn't present in
> > the event container so the linkage errors.
> >
> > The MM guys who set up the release strategy say the config is the same
> > as the config for WS20000079 (Release of contract),  which is working
> > fine.
> >
> > There was a SAP consultant on site last week who took a look and told
> > us to raise it to OSS but I'd like to do some more digging first. I'll
> > let you know if I find anything.
> >
> >  - Gavin
> >
> > 2006/4/25, Hill, Anna <anna.hill at sap.com>:
> > > Hi Bala
> > >
> > > The workflow you refer to has 2 mandatory import parameters, the
> > > Purchase order object instance (BUS2012) and the release code that
> has
> > > been applied to the PO. You must ensure that when you trigger the
> > > workflow (how are you testing it?), that both bits of data are
> passed.
> > >
> > >
> > > Anna Hill
> > > SAP Netweaver Technology
> > >
> > > SAP (UK) Ltd
> > > Clockhouse Place, Bedfont Road,
> > > Feltham, Middlesex TW14 8HD
> > >
> > > T   +44 (0)20 8917 6125
> > > F   +44 (0)20 8917 6461
> > > M  +44 (0)7966 975125
> > > E  anna.hill at sap.com
> > >
> > >
> > > -----Original Message-----
> > > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf
> > > Of Mike Pokraka
> > > Sent: 17 April 2006 13:41
> > > To: SAP Workflow Users' Group
> > > Subject: Re: WL - 006 Error occured
> > >
> > > Hello,
> > > Looks like you're not passing the input parameters. Check your
> event->WF
> > > binding. You say PO number is mandatory, but that's not what's being
> > > passed - only a PO Object.
> > >
> > > Cheers
> > > Mike
> > >
> > > Balasubramanian wrote:
> > > > Hi All,
> > > >
> > > >   I am getting the following error message below in a custom built
> > > > workflow template
> > > > from the standard workflow template ws20000075. We're using SAP
> ver.
> > > > 4.7. I am using BUS2012, where the mandatory params are the PO
> number
> > > > and the Release code, which I'm passing them.
> > > >
> > > > The system sends this mssage to the WF admin saying WL 006
> message.
> > > >
> > > >   I am sure there is something wrong with the input param, which I
> am
> > > > not able to figure out.
> > > >
> > > >   It will be of great help, if anyone of you can spare your
> valuable
> > > > time to have look at this and share your thoughts on this. How to
> find
> > >
> > > > the list of workflow errors.
> > > >
> > > > Thanks
> > > > Bala
> > > >
> > > >   Error processing following event linkage:
> > > > BUS2012 RELEASESTEPCREATED WS90000002
> > > > Following error occurred:
> > > > WL 006
> > > > Message text:
> > > > The mandatory input parameters of the workflow must be set
> > > > Event container appended as attachment.
> > > > Event linkage not changed.
> > > > Event stored temporarily.
> > > > Events can be redelivered via event queue
> > > > administration (transaction SWEQADM)
> > > >
> > > >     <?xml version="1.0" ?>
> > > >     - <CONTAINER>
> > > >       - <PROPERTIES>
> > > >       - <OWN_ID>
> > > >         <INSTID>B592F6FC289EBB43AC717C57E4B2D20D</INSTID>
> > > >       <TYPEID>CL_SWF_EVT_CONT_PERSISTENCE</TYPEID>
> > > >       <CATID>CL</CATID>
> > > >     </OWN_ID>
> > > >
> > > >     - <DEFEXTENSN>
> > > >         <INSTID>79F0DF5D6B4A5F47BCA4A6C572455758</INSTID>
> > > >       <TYPEID>CL_SWF_CNT_PERSISTENCE_XML</TYPEID>
> > > >       <CATID>CL</CATID>
> > > >     </DEFEXTENSN>
> > > >
> > > >       <PROPSTRING>21</PROPSTRING>
> > > >       <XMLVERSION>0001</XMLVERSION>
> > > >     </PROPERTIES>
> > > >
> > > >     - <ELEMENTS>
> > > >       - <_EVT_OBJECT NAME="_EVT_OBJECT:" TYPE="BUS2012:BO::u:0:0"
> > > > PROPS="2C92009">
> > > >         <INSTID>4500000577</INSTID>
> > > >       <TYPEID>BUS2012</TYPEID>
> > > >       <CATID>BO</CATID>
> > > >     </_EVT_OBJECT>
> > > >
> > > >       <_EVT_OBJTYPE NAME="_EVT_OBJTYPE:"
> TYPE="::SIBFTYPEID:C:32:0"
> > > > PROPS="2C00001">BUS2012</_EVT_OBJTYPE>
> > > >       <_EVT_NAME NAME="_EVT_NAME:" TYPE="::SWO_EVENT:C:32:0"
> > > > PROPS="2C00001">RELEASESTEPCREATED</_EVT_NAME>
> > > >       <_EVT_OBJKEY NAME="_EVT_OBJKEY:" TYPE="::SWO_TYPEID:C:70:0"
> > > > PROPS="2C00001">4500000577</_EVT_OBJKEY>
> > > >     - <_EVT_CREATOR NAME="_EVT_CREATOR:" TYPE="::SWHACTOR:u:0:0"
> > > > PROPS="2C00009">
> > > >         <OTYPE>US</OTYPE>
> > > >       <OBJID>LUKRAFKAW</OBJID>
> > > >     </_EVT_CREATOR>
> > > >
> > > >       <_EVT_CREATION_DATE NAME="_EVT_CREATION_DATE:"
> > > > TYPE="::SYDATUM:D:8:0"
> PROPS="2C00001">2006-04-12</_EVT_CREATION_DATE>
> > > >       <_EVT_CREATION_TIME NAME="_EVT_CREATION_TIME:"
> > > > TYPE="::SYUZEIT:T:6:0"
> PROPS="2C00001">15:00:24</_EVT_CREATION_TIME>
> > > >       <_EVT_CREATION_TIMESTAMP NAME="_EVT_CREATION_TIMESTAMP:"
> > > > TYPE="::TZNTSTMPS:P:8:0"
> > > > PROPS="2C00001">20060412200024</_EVT_CREATION_TIMESTAMP>
> > > >       <_EVT_LANGUAGE NAME="_EVT_LANGUAGE:" TYPE="::SYLANGU:C:1:0"
> > > > PROPS="0C00001">E</_EVT_LANGUAGE>
> > > >       <_EVT_ID NAME="_EVT_ID:" TYPE="::SWE_EVTID:N:20:0"
> > > > PROPS="2C00001">00000000000000336165</_EVT_ID>
> > > >       <_EVT_LOG_UPDATE NAME="_EVT_LOG_UPDATE:"
> TYPE="::XFELD:C:1:0"
> > > > PROPS="2C00001">X</_EVT_LOG_UPDATE>
> > > >       <RELEASECODE NAME="RELEASECODE:ReleaseCode"
> > > > TYPE="::T16FC-FRGCO:C:2:0" PROPS="0C003A01" />
> > > >       <CD_OBJECTCLAS NAME="CD_OBJECTCLAS:"
> TYPE="::CDOBJECTCL:C:15:0"
> > > > PROPS="2C">EINKBELEG</CD_OBJECTCLAS>
> > > >       <CD_OBJECTID NAME="CD_OBJECTID:" TYPE="::CDOBJECTV:C:90:0"
> > > > PROPS="2C">4500000577</CD_OBJECTID>
> > > >       <CD_CHANGENR NAME="CD_CHANGENR:" TYPE="::CDCHANGENR:C:10:0"
> > > > PROPS="2C">0000051986</CD_CHANGENR>
> > > >     </ELEMENTS>
> > > >
> > > >     </CONTAINER>
> > > >
> > >
> ------------------------------------------------------------------------
> > > -------------------------------------------------
> > > >
> > > >
> > > >
> > >
> ------------------------------------------------------------------------
> > > > Yahoo! Messenger with Voice.
> > > >
> > >
> <http://us.rd.yahoo.com/mail_us/taglines/postman3/*http://us.rd.yahoo.co
> > > m/evt=39666/*http://beta.messenger.yahoo.com>
> > > > PC-to-Phone calls for ridiculously low rates.
> > > >
> > > >
> > > >
> > >
> ------------------------------------------------------------------------
> > > >
> > > > _______________________________________________
> > > > 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
> > >
> > > _______________________________________________
> > > 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
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>




More information about the SAP-WUG mailing list