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