Workitems for IDOC related activity

Tue Jun 29 09:01:02 EDT 2010

GT,
I just need the details, because the user itself is saying that there is no any idoc related activity done. In that case why the task is getting triggered and why the work item is triggered in his/her inbox. You have almost helped me in analyzing this issue. They just need the reason for this issue that’s it .

Thanks
PD

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Madgambler
Sent: Tuesday, June 29, 2010 5:55 PM
To: SAP Workflow Users' Group
Cc: SAP Workflow Users' Group
Subject: Re: Workitems for IDOC related activity

I couldn't possibly fathom why your particular IDocs are erroring. This is a Workflow forum after all.

Might I suggest you investigate the IDoc status history and go from there?

Mike GT

Sent from my iPhone

On 29 Jun 2010, at 12:28, "Patil, Priyank" <Priyank.Patil at keane.com<mailto:Priyank.Patil at keane.com>> wrote:
Hey sorry, . Just for knowledge purpose, why we get these kind of issues(as per my post). Any reason??

From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Gambier
Sent: Tuesday, June 29, 2010 4:42 PM
To: sap-wug at mit.edu<mailto:sap-wug at mit.edu>
Subject: RE: Workitems for IDOC related activity

Forgive me for saying so but that's a pretty fundamental Transaction if you're dealing with IDocs.

If you're not quite sure how to use this Transaction, and that's quite acceptable if you've not dealt with IDoc-based interfaces before, then maybe you should be asking someone who handles your interfaces on a daily basis to check this out for you.

Your post was about IDocs coming in to your system so you need to locate the Inbound Parameters for the specific Message Type in question and display the details.

WE20 allows you to drill down to lower levels by double-clicking key fields.

Mike GT

________________________________
From: Priyank.Patil at keane.com<mailto:Priyank.Patil at keane.com>
To: sap-wug at MIT.EDU<mailto:sap-wug at MIT.EDU>
Date: Tue, 29 Jun 2010 16:13:15 +0530
Subject: RE: Workitems for IDOC related activity
‘The IDoc Process Code defined in the Partner Profile settings’ –This settings I want to see in we20 that what kind of process code they have used in partner settings.

From: sap-wug-bounces at MIT.EDU<mailto:sap-wug-bounces at MIT.EDU> [mailto:sap-wug-bounces at MIT.EDU] On Behalf Of Mike Gambier
Sent: Tuesday, June 29, 2010 4:03 PM
To: sap-wug at MIT.EDU<mailto:sap-wug at MIT.EDU>
Subject: RE: Workitems for IDOC related activity

Hi,

Your question doesn't make sense, sorry.

The IDoc Process Code defined in the Partner Profile settings defines what BOR Object Event is raised (if any) for the specific Message Type that the IDoc definition is being used for when a processing error occurs.

In the case of the standard 'BAPI' Process Code that SAP provides out of the box, the setting will be to raise IDOCL.InputErrorOccured.

If you do NOT want any Work Items to be issued when this event is raised then deactivate the linkage in SWETYPV, that is all. Don't simply zap the event settings in the Process Code as that Process Code might be shared for lots of Message Types.

If you DO want Work Items to be raised but NOT issued to a particular agent then check the 'Post Processing: Permitted Agents' setting in Partner Profile. This will delimit who is supposed to receive any Work Items issued when the event is raised. Your user might be assigned incorrectly for example or your target audience for the Work Items might be too wide.

If you DO want Work Items to be issued AND you want to empower the particular Agent to be able to execute the Work Item as they cannot do so at the moment then look at their authorisations.

Mike GT

________________________________
From: Priyank.Patil at keane.com<mailto:Priyank.Patil at keane.com>
To: sap-wug at mit.edu<mailto:sap-wug at mit.edu>
Date: Tue, 29 Jun 2010 15:17:52 +0530
Subject: RE: Workitems for IDOC related activity
GT..I got struckup in WE20.Please let me know what kind of process code I need to search for it?

From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Patil, Priyank
Sent: Tuesday, June 29, 2010 2:41 PM
To: SAP Workflow Users' Group
Subject: RE: Workitems for IDOC related activity

 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.

From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Gambier
Sent: Tuesday, June 29, 2010 2:16 PM
To: sap-wug at mit.edu<mailto:sap-wug at mit.edu>
Subject: RE: Workitems for IDOC related activity

Hi,

This Work Item is typically based on the standard stand alone Task TS20000051.

The Method invoked is IDOCAPPL.InputForeground which calls standard FM IDOC_MANUAL_INPUT.

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

* Authoritycheck xlp 211197
  IF edidc-direct EQ '1'.              "Ausgang
    AUTHORITY-CHECK OBJECT 'S_IDOCMONI'                     "xlp211197
             ID 'ACTVT' FIELD c_display                     "xlp211197
             ID 'EDI_DIR' FIELD edidc-direct                "xlp211197
             ID 'EDI_MES' FIELD edidc-mestyp                "xlp211197
             ID 'EDI_PRN' FIELD edidc-rcvprn                "xlp211197
             ID 'EDI_PRT' FIELD edidc-rcvprt                "xlp211197
             ID 'EDI_TCD' DUMMY.                            "xlp211197
  ELSE.                                "Eingang
    AUTHORITY-CHECK OBJECT 'S_IDOCMONI'                     "xlp211197
             ID 'ACTVT' FIELD c_display                     "xlp211197
             ID 'EDI_DIR' FIELD edidc-direct                "xlp211197
             ID 'EDI_MES' FIELD edidc-mestyp                "xlp211197
             ID 'EDI_PRN' FIELD edidc-sndprn                "xlp211197
             ID 'EDI_PRT' FIELD edidc-sndprt                "xlp211197
             ID 'EDI_TCD' DUMMY.                            "xlp211197
  ENDIF.                                                    "xlp211197

Chances are if your agents can't work these Work Items they probably don't have the auths.

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.

This is usually the standard setting for BAPI (BD64/BDBG) Methods by the way.

To even receive these Work Items the Event Linkage must be active so go hunt in SWETYPV for IDOCAPPL.InputErrorOccurred.

Mike GT

> Date: Tue, 29 Jun 2010 16:09:12 +0800
> Subject: Re: Workitems for IDOC related activity
> From: rbakker at gmail.com<mailto:rbakker at gmail.com>
> To: sap-wug at MIT.EDU<mailto:sap-wug at MIT.EDU>
>
> Hello,
>
> In SWIA: 000007750945 for the workitem. You'll be able to see the
> workflow log, find out which workflow it is and hopefully be able to
> figure out how it was started by looking at the definition of the
> workflow in e.g. PFTC_DIS.
>
> regards
> Rick Bakker
> Hanabi Technology
>
> On Tue, Jun 29, 2010 at 4:01 PM, Patil, Priyank <Priyank.Patil at keane.com<mailto:Priyank.Patil at keane.com>> wrote:
> > 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.
> >
> > -----Original Message-----
> > From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Rick Bakker
> > Sent: Tuesday, June 29, 2010 1:20 PM
> > To: SAP Workflow Users' Group
> > Subject: Re: Workitems for IDOC related activity
> >
> > Hello,
> >
> > Look in SWIA to see which workflow it is and perhaps how it gets started.
> >
> > regards
> > Rick Bakker
> > Hanabi Technology
> >
> > On Tue, Jun 29, 2010 at 3:36 PM, Patil, Priyank <Priyank.Patil at keane.com<mailto:Priyank.Patil at keane.com>> wrote:
> >> Hi Wuggers,
> >>
> >>      One of our user is getting an IDOC error kind of workitem.I have
> >> checked in the business object(idocmsg) but there is no any event associated
> >> with it. Our user needs a clear details on this issue. We are into
> >> Ecc6.Since there is no any idoc related activity is done. How can I avoid
> >> this work item from triggering this into SBWP.
> >>
> >> Once the work item is executed, a pop up is displayed with -
> >>
> >> Work item 000007750945:object IDOCMSG method ERRORPROCESS cannot be
> >> executed.
> >>
> >> Pls find the enclosed document attached for details.
> >>
> >>
> >>
> >> From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> >> Patil, Priyank
> >> Sent: Tuesday, June 29, 2010 12:57 PM
> >> To: SAP Workflow Users' Group
> >> Subject: Workitems for IDOC related activity
> >>
> >>
> >>
> >> Hi Wuggers,
> >>
> >>      One of our user is getting this kind of workitem.I have checked in the
> >> business object(idocmsg) but there is not any event associated with it. Our
> >> user needs a clear details on this issue. We are into Ecc6.Since there is no
> >> any idoc related activity is done. How can I avoid this work item from
> >> triggering this into SBWP.
> >>
> >>
> >>
> >>
> >>
> >> ______________________________________________________________________
> >> 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.
> >>
> >> ______________________________________________________________________
> >> 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.
> >>
> >> _______________________________________________
> >> SAP-WUG mailing list
> >> SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug
> >>
> >>
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> > ______________________________________________________________________
> > 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.
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
________________________________
Get a free e-mail account with Hotmail. Sign-up now.<http://clk.atdmt.com/UKM/go/197222280/direct/01/>

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

______________________________________________________________________
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.
________________________________
Get a free e-mail account with Hotmail. Sign-up now.<http://clk.atdmt.com/UKM/go/197222280/direct/01/>

______________________________________________________________________
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.
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug

______________________________________________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100629/379c6725/attachment.htm