<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> Its quite valuable info. So how can I avoid this for a
particular user. And how should I check in WE20 for a process code.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Mike Gambier<br>
<b>Sent:</b> Tuesday, June 29, 2010 2:16 PM<br>
<b>To:</b> sap-wug@mit.edu<br>
<b>Subject:</b> RE: Workitems for IDOC related activity<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;
font-family:"Verdana","sans-serif"'>Hi,<br>
<br>
This Work Item is typically based on the standard stand alone Task
TS20000051.<br>
<br>
The Method invoked is IDOCAPPL.InputForeground which calls standard FM
IDOC_MANUAL_INPUT. <br>
<br>
Right at the start the user's Profile will be checked for Authorisation
Object S_IDOCMONI for the Direction, Message Type, Partner Number
(Sender/Recipient) and Port (Sender/Recipient):<br>
<br>
</span><span style='font-size:10.0pt;font-family:"Courier New"'>*
Authoritycheck xlp 211197<br>
IF edidc-direct EQ
'1'.
"Ausgang<br>
AUTHORITY-CHECK OBJECT
'S_IDOCMONI'
"xlp211197<br>
ID
'ACTVT' FIELD
c_display
"xlp211197<br>
ID
'EDI_DIR' FIELD
edidc-direct
"xlp211197<br>
ID
'EDI_MES' FIELD
edidc-mestyp
"xlp211197<br>
ID
'EDI_PRN' FIELD
edidc-rcvprn
"xlp211197<br>
ID
'EDI_PRT' FIELD
edidc-rcvprt
"xlp211197<br>
ID
'EDI_TCD'
DUMMY.
"xlp211197<br>
ELSE.
"Eingang<br>
AUTHORITY-CHECK OBJECT
'S_IDOCMONI'
"xlp211197<br>
ID
'ACTVT' FIELD
c_display
"xlp211197<br>
ID
'EDI_DIR' FIELD
edidc-direct
"xlp211197<br>
ID
'EDI_MES' FIELD
edidc-mestyp
"xlp211197<br>
ID
'EDI_PRN' FIELD
edidc-sndprn
"xlp211197<br>
ID
'EDI_PRT' FIELD
edidc-sndprt
"xlp211197<br>
ID
'EDI_TCD'
DUMMY.
"xlp211197<br>
ENDIF.
"xlp211197</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'><br>
<br>
Chances are if your agents can't work these Work Items they probably don't have
the auths.<br>
<br>
The event will only be raised if your IDoc Process Code defines that the event
should be raised. Go look in WE20 and dig down to the Process Code and you'll
see it.<br>
<br>
This is usually the standard setting for BAPI (BD64/BDBG) Methods by the way.<br>
<br>
To even receive these Work Items the Event Linkage must be active so go hunt in
SWETYPV for IDOCAPPL.InputErrorOccurred.<br>
<br>
Mike GT<br>
<br>
> Date: Tue, 29 Jun 2010 16:09:12 +0800<br>
> Subject: Re: Workitems for IDOC related activity<br>
> From: rbakker@gmail.com<br>
> To: sap-wug@MIT.EDU<br>
> <br>
> Hello,<br>
> <br>
> In SWIA: 000007750945 for the workitem. You'll be able to see the<br>
> workflow log, find out which workflow it is and hopefully be able to<br>
> figure out how it was started by looking at the definition of the<br>
> workflow in e.g. PFTC_DIS.<br>
> <br>
> regards<br>
> Rick Bakker<br>
> Hanabi Technology<br>
> <br>
> On Tue, Jun 29, 2010 at 4:01 PM, Patil, Priyank
<Priyank.Patil@keane.com> wrote:<br>
> > Rick, thanks for your immediate response. Could you please elaborate
in detail. Since there is no any event associated withit.So what should be my
input parameter in SWIA.<br>
> ><br>
> > -----Original Message-----<br>
> > From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On
Behalf Of Rick Bakker<br>
> > Sent: Tuesday, June 29, 2010 1:20 PM<br>
> > To: SAP Workflow Users' Group<br>
> > Subject: Re: Workitems for IDOC related activity<br>
> ><br>
> > Hello,<br>
> ><br>
> > Look in SWIA to see which workflow it is and perhaps how it gets
started.<br>
> ><br>
> > regards<br>
> > Rick Bakker<br>
> > Hanabi Technology<br>
> ><br>
> > On Tue, Jun 29, 2010 at 3:36 PM, Patil, Priyank
<Priyank.Patil@keane.com> wrote:<br>
> >> Hi Wuggers,<br>
> >><br>
> >> One of our user is getting an IDOC error
kind of workitem.I have<br>
> >> checked in the business object(idocmsg) but there is no any event
associated<br>
> >> with it. Our user needs a clear details on this issue. We are
into<br>
> >> Ecc6.Since there is no any idoc related activity is done. How can
I avoid<br>
> >> this work item from triggering this into SBWP.<br>
> >><br>
> >> Once the work item is executed, a pop up is displayed with -<br>
> >><br>
> >> Work item 000007750945:object IDOCMSG method ERRORPROCESS cannot
be<br>
> >> executed.<br>
> >><br>
> >> Pls find the enclosed document attached for details.<br>
> >><br>
> >><br>
> >><br>
> >> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On
Behalf Of<br>
> >> Patil, Priyank<br>
> >> Sent: Tuesday, June 29, 2010 12:57 PM<br>
> >> To: SAP Workflow Users' Group<br>
> >> Subject: Workitems for IDOC related activity<br>
> >><br>
> >><br>
> >><br>
> >> Hi Wuggers,<br>
> >><br>
> >> One of our user is getting this kind of
workitem.I have checked in the<br>
> >> business object(idocmsg) but there is not any event associated
with it. Our<br>
> >> user needs a clear details on this issue. We are into Ecc6.Since
there is no<br>
> >> any idoc related activity is done. How can I avoid this work item
from<br>
> >> triggering this into SBWP.<br>
> >><br>
> >><br>
> >><br>
> >><br>
> >><br>
> >>
______________________________________________________________________<br>
> >> Disclaimer: This email message and any attachments are for the
sole use of<br>
> >> the intended recipient(s) and may contain information that is
confidential,<br>
> >> legally privileged or otherwise exempt from disclosure under
applicable law.<br>
> >> If you are not the intended recipient(s) or have received this
message in<br>
> >> error, you are instructed to immediately notify the sender by
return email<br>
> >> and required to delete this message from your computer system.
This<br>
> >> communication does not form any contractual obligation on behalf
of the<br>
> >> sender, the sender's employer or such employer's parent company,
affiliates<br>
> >> or subsidiaries.<br>
> >><br>
> >>
______________________________________________________________________<br>
> >> Disclaimer: This email message and any attachments are for the
sole use of<br>
> >> the intended recipient(s) and may contain information that is
confidential,<br>
> >> legally privileged or otherwise exempt from disclosure under
applicable law.<br>
> >> If you are not the intended recipient(s) or have received this
message in<br>
> >> error, you are instructed to immediately notify the sender by
return email<br>
> >> and required to delete this message from your computer system.
This<br>
> >> communication does not form any contractual obligation on behalf
of the<br>
> >> sender, the sender's employer or such employer's parent company,
affiliates<br>
> >> or subsidiaries.<br>
> >><br>
> >> _______________________________________________<br>
> >> SAP-WUG mailing list<br>
> >> SAP-WUG@mit.edu<br>
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> >><br>
> >><br>
> ><br>
> > _______________________________________________<br>
> > SAP-WUG mailing list<br>
> > SAP-WUG@mit.edu<br>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> ><br>
> >
______________________________________________________________________<br>
> > Disclaimer: This email message and any attachments are for the
sole use of the intended recipient(s) and may contain information that is
confidential, legally privileged or otherwise exempt from disclosure under
applicable law. If you are not the intended recipient(s) or have received this
message in error, you are instructed to immediately notify the sender by return
email and required to delete this message from your computer system. This
communication does not form any contractual obligation on behalf of the sender,
the sender's employer or such employer's parent company, affiliates or
subsidiaries.<br>
> ><br>
> > _______________________________________________<br>
> > SAP-WUG mailing list<br>
> > SAP-WUG@mit.edu<br>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> ><br>
> <br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<o:p></o:p></span></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Verdana","sans-serif"'>Get
a free e-mail account with Hotmail. <a
href="http://clk.atdmt.com/UKM/go/197222280/direct/01/" target="_new">Sign-up
now.</a><o:p></o:p></span></p>
</div>
<BR>
______________________________________________________________________<BR>
Disclaimer: This email message and any attachments are for the sole use of the intended recipient(s) and may contain information that is confidential, legally privileged or otherwise exempt from disclosure under applicable law. If you are not the intended recipient(s) or have received this message in error, you are instructed to immediately notify the sender by return email and required to delete this message from your computer system. This communication does not form any contractual obligation on behalf of the sender, the sender's employer or such employer's parent company, affiliates or subsidiaries.<BR>
</body>
</html>