<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>Hi All, <BR>
<BR>
I hope you are fine<FONT face=Arial size=3 ><BR>
We are using the SRM 5.0 extended scenario with badi workflow, the task shown in the UWL are displaying a link that is <BR>
the business object therefore if we click on the attachment there is nothing shown and the screen displays a blank screen <BR>
This is causing confusion with our users.<BR>
The task we are using in the back end are standard from standard workflow<BR>
TS10008126 for shopping Cart workflow from WS14000134<BR>
TS14007970 for Local Purchase order workflow from WS14000146<BR>
<BR>
Of course we can still process the tasks by clicking directly on the title of the mail or on the Launch SAP task button<BR>
But apparently the users are really confused ...<BR>
<BR >Does anybody have a solution for this ?<BR>
<BR>
Cheers<BR>
Stephane<BR>
</FONT><BR ><BR ><BR ><BR ><BR > <BR>
<HR id=stopSpelling>
<BR>
> From: sap-wug-request@mit.edu<BR>> Subject: SAP-WUG Digest, Vol 19, Issue 37<BR>> To: sap-wug@mit.edu<BR>> Date: Thu, 15 Jun 2006 04:10:42 -0400<BR>> <BR>> Send SAP-WUG mailing list submissions to<BR>> sap-wug@mit.edu<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> or, via email, send a message with subject or body 'help' to<BR>> sap-wug-request@mit.edu<BR>> <BR>> You can reach the person managing the list at<BR>> sap-wug-owner@mit.edu<BR>> <BR>> When replying, please edit your Subject line so it is more specific<BR>> than "Re: Contents of SAP-WUG digest..."<BR>> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. instantiate an object and attach it to a workflow? - FICA<BR>> (Paul.Bakker@osr.treasury.qld.gov.au)<BR>> 2. Re: instantiate an object and attach it to a workflow? - FICA<BR>> (Mark Pyc)<BR>> 3. Re: instantiate an object and attach it to a workflow? - FICA<BR>> (Paul.Bakker@osr.treasury.qld.gov.au)<BR>> 4. Re: instantiate an object and attach it to a workflow? - FICA<BR>> (Mark Pyc)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Thu, 15 Jun 2006 15:00:08 +1000<BR>> From: Paul.Bakker@osr.treasury.qld.gov.au<BR>> Subject: instantiate an object and attach it to a workflow? - FICA<BR>> To: sap-wug@mit.edu<BR>> Message-ID:<BR>> <OF9706AED0.433198D8-ON4A25718E.001B1EBA-4A25718E.001B73F6@treasury.qld.gov.au><BR>> <BR>> Content-Type: text/plain; charset="us-ascii"<BR>> <BR>> Workflow Gurus,<BR>> <BR>> I have a custom workflow which, after seeking agent approval, creates an<BR>> object (a document of type CA_DOC).<BR>> <BR>> I would like to attach an instance of the created object to the workflow,<BR>> so that 'object services' can be used later.<BR>> <BR>> To do this, I added a custom step which calls the method<BR>> SYSTEM.GENERICINSTANTIATE. Apparently if you pass the object key (and<BR>> object type) to this method, it instantiates the object. This is then<BR>> passed back to the workflow container.<BR>> <BR>> At least, that's what I hoped it would do! In practice the workflow goes<BR>> into error with message OL808: "Object with runtime number '0' not defined"<BR>> <BR>> When I try to view the new CA_DOC object (via FPE3), it does not exist. I<BR>> suspect this is because the workflow went into error... it didn't get a<BR>> chance to save the document.<BR>> <BR>> And yet, if I run the workflow without the extra GENERECINSTANTIATE step,<BR>> it works fine.<BR>> <BR>> Does anyone have any idea what the problem is? Could it be that a 'COMMIT<BR>> WORK' needs to be done before trying to instantiate the new object? Is<BR>> there a workflow step for doing that?<BR>> <BR>> Or am I just being stupid. Is there a much easier way to attach an object<BR>> to a workflow via a background step?<BR>> <BR>> merci<BR>> Paul Bakker<BR>> Brisbane<BR>> <BR>> <BR>> ******************************************************************************************************************************************************<BR>> <BR>> Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments. Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.<BR>> <BR>> The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright. If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments. Queensland Treasury uses virus scanning software. However, it is not liable for viruses present in this e-mail or in any attachment. <BR>> <BR>> ******************************************************************************************************************************************************<BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 2<BR>> Date: Thu, 15 Jun 2006 08:42:04 +0100<BR>> From: "Mark Pyc" <mark.pyc@gmail.com><BR>> Subject: Re: instantiate an object and attach it to a workflow? - FICA<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <23f0a78a0606150042t35c63f9di9999d3204f6b36ec@mail.gmail.com><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> G'day Paul,<BR>> <BR>> You're on the right path. I don't seem to have an object type of CA_DOC in<BR>> my ECC system so I can't comment on specifics.<BR>> <BR>> Have you tried just testing the SYSTEM method from SWO1?? If you've got the<BR>> key right you should be get an object link back that you can double click<BR>> into to confirm that it's worked happily.<BR>> <BR>> Good luck,<BR>> Mark<BR>> <BR>> <BR>> On 6/15/06, Paul.Bakker@osr.treasury.qld.gov.au <<BR>> Paul.Bakker@osr.treasury.qld.gov.au> wrote:<BR>> ><BR>> > Workflow Gurus,<BR>> ><BR>> > I have a custom workflow which, after seeking agent approval, creates an<BR>> > object (a document of type CA_DOC).<BR>> ><BR>> > I would like to attach an instance of the created object to the workflow,<BR>> > so that 'object services' can be used later.<BR>> ><BR>> > To do this, I added a custom step which calls the method<BR>> > SYSTEM.GENERICINSTANTIATE. Apparently if you pass the object key (and<BR>> > object type) to this method, it instantiates the object. This is then<BR>> > passed back to the workflow container.<BR>> ><BR>> > At least, that's what I hoped it would do! In practice the workflow goes<BR>> > into error with message OL808: "Object with runtime number '0' not<BR>> > defined"<BR>> ><BR>> > When I try to view the new CA_DOC object (via FPE3), it does not exist. I<BR>> > suspect this is because the workflow went into error... it didn't get a<BR>> > chance to save the document.<BR>> ><BR>> > And yet, if I run the workflow without the extra GENERECINSTANTIATE step,<BR>> > it works fine.<BR>> ><BR>> > Does anyone have any idea what the problem is? Could it be that a 'COMMIT<BR>> > WORK' needs to be done before trying to instantiate the new object? Is<BR>> > there a workflow step for doing that?<BR>> ><BR>> > Or am I just being stupid. Is there a much easier way to attach an object<BR>> > to a workflow via a background step?<BR>> ><BR>> > merci<BR>> > Paul Bakker<BR>> > Brisbane<BR>> ><BR>> ><BR>> ><BR>> > ******************************************************************************************************************************************************<BR>> ><BR>> > Only an individual or entity who is intended to be a recipient of this<BR>> > e-mail may access or use the information contained in this e-mail or any of<BR>> > its attachments. Opinions contained in this e-mail or any of its<BR>> > attachments do not necessarily reflect the opinions of Queensland Treasury.<BR>> ><BR>> > The contents of this e-mail and any attachments are confidential and may<BR>> > be legally privileged and the subject of copyright. If you have received<BR>> > this e-mail in error, please notify Queensland Treasury immediately and<BR>> > erase all copies of the e-mail and the attachments. Queensland Treasury<BR>> > uses virus scanning software. However, it is not liable for viruses present<BR>> > in this e-mail or in any attachment.<BR>> ><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>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060615/55c699f8/attachment-0001.htm<BR>> <BR>> ------------------------------<BR>> <BR>> Message: 3<BR>> Date: Thu, 15 Jun 2006 17:54:20 +1000<BR>> From: Paul.Bakker@osr.treasury.qld.gov.au<BR>> Subject: Re: instantiate an object and attach it to a workflow? - FICA<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <OF986B5F4A.AC0486EB-ON4A25718E.002B2D30-4A25718E.002B66B3@treasury.qld.gov.au><BR>> <BR>> Content-Type: text/plain; charset=US-ASCII<BR>> <BR>> Mark,<BR>> <BR>> Thanks for that. I've solved the problem now, but in a fairly ugly way.. I<BR>> put a 'Requested Start' of "+1 minute" on the workitem that does the<BR>> instantiation. By the time ithe workitem executes, the CA_DOC has been<BR>> created and the instantation works.<BR>> <BR>> FYI: the object CA_DOC is specific to Contract Accounting (or PSCD)<BR>> <BR>> cheers - and thanks,<BR>> Paul B<BR>> <BR>> <BR>> <BR>> |---------+----------------------------><BR>> | | "Mark Pyc" |<BR>> | | <mark.pyc@gmail.c|<BR>> | | om> |<BR>> | | Sent by: |<BR>> | | sap-wug-bounces@m|<BR>> | | it.edu |<BR>> | | |<BR>> | | |<BR>> | | 15/06/2006 17:42 |<BR>> | | Please respond to|<BR>> | | "SAP Workflow |<BR>> | | Users' Group" |<BR>> | | |<BR>> |---------+----------------------------><BR>> >------------------------------------------------------------------------------------------------------------------------------|<BR>> | |<BR>> | To: "SAP Workflow Users' Group" <sap-wug@mit.edu> |<BR>> | cc: |<BR>> | Subject: Re: instantiate an object and attach it to a workflow? - FICA |<BR>> >------------------------------------------------------------------------------------------------------------------------------|<BR>> <BR>> <BR>> <BR>> <BR>> G'day Paul,<BR>> <BR>> You're on the right path. I don't seem to have an object type of CA_DOC in<BR>> my ECC system so I can't comment on specifics.<BR>> <BR>> Have you tried just testing the SYSTEM method from SWO1?? If you've got the<BR>> key right you should be get an object link back that you can double click<BR>> into to confirm that it's worked happily.<BR>> <BR>> Good luck,<BR>> Mark<BR>> <BR>> <BR>> On 6/15/06, Paul.Bakker@osr.treasury.qld.gov.au <<BR>> Paul.Bakker@osr.treasury.qld.gov.au> wrote:<BR>> Workflow Gurus,<BR>> <BR>> I have a custom workflow which, after seeking agent approval, creates an<BR>> object (a document of type CA_DOC).<BR>> <BR>> I would like to attach an instance of the created object to the workflow,<BR>> so that 'object services' can be used later.<BR>> <BR>> To do this, I added a custom step which calls the method<BR>> SYSTEM.GENERICINSTANTIATE . Apparently if you pass the object key (and<BR>> object type) to this method, it instantiates the object. This is then<BR>> passed back to the workflow container.<BR>> <BR>> At least, that's what I hoped it would do! In practice the workflow goes<BR>> into error with message OL808: "Object with runtime number '0' not defined"<BR>> <BR>> When I try to view the new CA_DOC object (via FPE3), it does not exist. I<BR>> suspect this is because the workflow went into error... it didn't get a<BR>> chance to save the document.<BR>> <BR>> And yet, if I run the workflow without the extra GENERECINSTANTIATE step,<BR>> it works fine.<BR>> <BR>> Does anyone have any idea what the problem is? Could it be that a 'COMMIT<BR>> WORK' needs to be done before trying to instantiate the new object? Is<BR>> there a workflow step for doing that?<BR>> <BR>> Or am I just being stupid. Is there a much easier way to attach an object<BR>> to a workflow via a background step?<BR>> <BR>> merci<BR>> Paul Bakker<BR>> Brisbane<BR>> <BR>> <BR>> ******************************************************************************************************************************************************<BR>> <BR>> <BR>> Only an individual or entity who is intended to be a recipient of this<BR>> e-mail may access or use the information contained in this e-mail or any of<BR>> its attachments. Opinions contained in this e-mail or any of its<BR>> attachments do not necessarily reflect the opinions of Queensland Treasury.<BR>> <BR>> The contents of this e-mail and any attachments are confidential and may be<BR>> legally privileged and the subject of copyright. If you have received this<BR>> e-mail in error, please notify Queensland Treasury immediately and erase<BR>> all copies of the e-mail and the attachments. Queensland Treasury uses<BR>> virus scanning software. However, it is not liable for viruses present in<BR>> this e-mail or in any attachment.<BR>> <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>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 4<BR>> Date: Thu, 15 Jun 2006 09:10:44 +0100<BR>> From: "Mark Pyc" <mark.pyc@gmail.com><BR>> Subject: Re: instantiate an object and attach it to a workflow? - FICA<BR>> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><BR>> Message-ID:<BR>> <23f0a78a0606150110i2eb2d1aaj3f27c3d2f5c9f47b@mail.gmail.com><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> There is always a sinking sense of failure when having to resort to good ol'<BR>> 1 minute delay. Unavoidable sometimes though...<BR>> <BR>> On 6/15/06, Paul.Bakker@osr.treasury.qld.gov.au <<BR>> Paul.Bakker@osr.treasury.qld.gov.au> wrote:<BR>> ><BR>> > Mark,<BR>> ><BR>> > Thanks for that. I've solved the problem now, but in a fairly ugly way.. I<BR>> > put a 'Requested Start' of "+1 minute" on the workitem that does the<BR>> > instantiation. By the time ithe workitem executes, the CA_DOC has been<BR>> > created and the instantation works.<BR>> ><BR>> > FYI: the object CA_DOC is specific to Contract Accounting (or PSCD)<BR>> ><BR>> > cheers - and thanks,<BR>> > Paul B<BR>> ><BR>> ><BR>> ><BR>> > |---------+----------------------------><BR>> > | | "Mark Pyc" |<BR>> > | | <mark.pyc@gmail.c|<BR>> > | | om> |<BR>> > | | Sent by: |<BR>> > | | sap-wug-bounces@m|<BR>> > | | it.edu |<BR>> > | | |<BR>> > | | |<BR>> > | | 15/06/2006 17:42 |<BR>> > | | Please respond to|<BR>> > | | "SAP Workflow |<BR>> > | | Users' Group" |<BR>> > | | |<BR>> > |---------+----------------------------><BR>> ><BR>> > >------------------------------------------------------------------------------------------------------------------------------|<BR>> ><BR>> > | |<BR>> > | To: "SAP Workflow Users' Group" <sap-wug@mit.edu<BR>> > > |<BR>> > |<BR>> > cc: |<BR>> > | Subject: Re: instantiate an object and attach it to a workflow? -<BR>> > FICA |<BR>> ><BR>> > >------------------------------------------------------------------------------------------------------------------------------|<BR>> ><BR>> ><BR>> ><BR>> ><BR>> > G'day Paul,<BR>> ><BR>> > You're on the right path. I don't seem to have an object type of CA_DOC in<BR>> > my ECC system so I can't comment on specifics.<BR>> ><BR>> > Have you tried just testing the SYSTEM method from SWO1?? If you've got<BR>> > the<BR>> > key right you should be get an object link back that you can double click<BR>> > into to confirm that it's worked happily.<BR>> ><BR>> > Good luck,<BR>> > Mark<BR>> ><BR>> ><BR>> > On 6/15/06, Paul.Bakker@osr.treasury.qld.gov.au <<BR>> > Paul.Bakker@osr.treasury.qld.gov.au> wrote:<BR>> > Workflow Gurus,<BR>> ><BR>> > I have a custom workflow which, after seeking agent approval, creates an<BR>> > object (a document of type CA_DOC).<BR>> ><BR>> > I would like to attach an instance of the created object to the workflow,<BR>> > so that 'object services' can be used later.<BR>> ><BR>> > To do this, I added a custom step which calls the method<BR>> > SYSTEM.GENERICINSTANTIATE . Apparently if you pass the object key (and<BR>> > object type) to this method, it instantiates the object. This is then<BR>> > passed back to the workflow container.<BR>> ><BR>> > At least, that's what I hoped it would do! In practice the workflow goes<BR>> > into error with message OL808: "Object with runtime number '0' not<BR>> > defined"<BR>> ><BR>> > When I try to view the new CA_DOC object (via FPE3), it does not exist. I<BR>> > suspect this is because the workflow went into error... it didn't get a<BR>> > chance to save the document.<BR>> ><BR>> > And yet, if I run the workflow without the extra GENERECINSTANTIATE step,<BR>> > it works fine.<BR>> ><BR>> > Does anyone have any idea what the problem is? Could it be that a 'COMMIT<BR>> > WORK' needs to be done before trying to instantiate the new object? Is<BR>> > there a workflow step for doing that?<BR>> ><BR>> > Or am I just being stupid. Is there a much easier way to attach an object<BR>> > to a workflow via a background step?<BR>> ><BR>> > merci<BR>> > Paul Bakker<BR>> > Brisbane<BR>> ><BR>> ><BR>> ><BR>> > ******************************************************************************************************************************************************<BR>> ><BR>> ><BR>> > Only an individual or entity who is intended to be a recipient of this<BR>> > e-mail may access or use the information contained in this e-mail or any<BR>> > of<BR>> > its attachments. Opinions contained in this e-mail or any of its<BR>> > attachments do not necessarily reflect the opinions of Queensland<BR>> > Treasury.<BR>> ><BR>> > The contents of this e-mail and any attachments are confidential and may<BR>> > be<BR>> > legally privileged and the subject of copyright. If you have received<BR>> > this<BR>> > e-mail in error, please notify Queensland Treasury immediately and erase<BR>> > all copies of the e-mail and the attachments. Queensland Treasury uses<BR>> > virus scanning software. However, it is not liable for viruses present in<BR>> > this e-mail or in any attachment.<BR>> ><BR>> ><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>> > 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>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060615/b225ca39/attachment.htm<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>> End of SAP-WUG Digest, Vol 19, Issue 37<BR>> ***************************************<BR><BR><br /><hr />À vous de rechercher : <a href='http://ideas.live.com/programpage.aspx?versionId=6e782662-5f2a-4161-a64a-7f63644e1f0a' target='_new'>Essayez Windows Live Search for Mobile Beta</a></body>
</html>