Overall Release of Purchase Requisitions using Workflow Templ ate WS20000077

[Nobles, Diane]

Thanks for the information.  Even though we are not in 4.6, and do not have
a delegation function, I believe that to be the same as Release in 3.1H.
But I did get it working.  It turns out my client had just been copied and I
needed to rerun the WF configuration settings. You did help me though.  The
information about SAP triggering from the application is very interesting.
Several days ago one of my workflows was being triggered twice.  The
solution was to delete the change doc, entry for that object/event.  Then
the workflow only triggered once.  We knew that SAP was doing something, but
what I didn't know.  You have shed some light on this subject.  Is there a
way to check for the applications this is applied to and if this will always
be the case, i.e., SAP standard operations.    I am concerned with using a
trigger that I do not know anything about.  From this it appears that the
only time we need a forced event, i.e., change doc., etc., is for
particulars.  I find that each day I learn a little more about workflow.
Nothing like real experience heh!!!!
 
Since you have been so helpful, can you tell me how to use status management
to trigger a workflow?  How do you actually link it to the workflow??  Also
one other thing where does the method container reside and how can you see
it?
 
Diane H. Nobles
SDE PM Team
(757)380-7250
::::::::::::::::::::::::::::::::::::::
Now the Lord is the Spirit; and where
the Spirit of the Lord is, there is
Liberty. II Corinthians 3:17
 
 
 
-----Original Message-----
From: Svanikier, Helena [mailto:helena.svanikier at sap.com]
Sent: Friday, June 22, 2001 2:23 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Overall Release of Purchase Requisitions using Workflow
Templ ate WS20000077
 
 
Hi Diane
 
Events get triggered by the application regardless of whether there is an
entry in the event linkage table or not.
If the event is a standard event, it will always be fired with the original
business object and not with the related subtypes.
 
What you have to do is set up a delegation between the original business
object (BUS2078) and your subtype (ZBUS2078).
Having done this, you can always refer to the original business object
BUS2078 but you will also see all the additional methods, attributes and
events defined for your subtype.
 
For delegation goto the business object builder (SWo1), then chose settings
--> delegation --> systemwide.
 
Hope this helps
Regards
 
Helena Svanikier
SAP Switzerland
 
-----Original Message-----
From: Nobles, Diane [mailto:nobles_dh at naptheon.com]
Sent: Donnerstag, 21. Juni 2001 22:31
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Overall Release of Purchase Requisitions using Workf
Templ ate WS20000077
 
 
I am having a similar problem that Paul is having but with object type
ZBUS2078.  I created this object type because I wanted to make changes to
the attributes.  During testing both the workflow and the event
trigger/linkage works great.  But when I create the notification, it will
not create an event using my object type.  Also the system seems to be
generating events on object types not even in the event linkage table,i.e.,
an event is still being created for BUS2078 even though I have deleted and
deactivated everything I know that can trigger this event.  Can anybody
offer any suggestions.
 
 
 
Diane H. Nobles
SDE PM Team
(757)380-7250
::::::::::::::::::::::::::::::::::::::
Now the Lord is the Spirit; and where
the Spirit of the Lord is, there is
Liberty. II Corinthians 3:17
 
 
 
-----Original Message-----
From: Susan R. Keohan [mailto:skeohan at MIT.EDU]
Sent: Thursday, June 21, 2001 10:13 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Overall Release of Purchase Requisitions using Workflow
Template WS20000077
 
 
Hi Paul,
 
First off, I would check that the event linkage is activated.  Use
transaction SWETYPV to check that there is an entry in this table for your
business object BUS2015, RELEASESTEPCREATED, and that the 'enabled' switch
is ticked.  Once this is done, your workflow should be triggered when you
create the requisition.
 
Also, with this switch enable, it could solve the problem of the req not
going to the next level (but I plead ignorance here, as I am not familiar
with this template.
 
Good Luck
Sue
 
At 02:55 PM 6/21/01 +0100, you wrote:
>Hello Everybody,
>
>My name is Paul Blackford and I work for MCT (McCann Erickson) based in
London.
>My role is senior MM Implementor using SAP version 4.6C.
>
>I am currently experiencing a problem with Workflow in SAP 4.6C.
>
>I am attempting to use the above workflow template to release purchase
>requisitions using a release strategy with classification. I have created
an org
>structure with assignments and activated the workflow. However, when I
create a
>purchase req the workflow is not activated. But if I start the workflow
from the
>test environment the template is triggered, although when the purchase req
is
>released it does not appear in the SAP Inbox of the next person in the org
>structure.
>
>Can anybody help?
>
>thanks
>Paul.
>
>
>The information transmitted is intended only for the person or entity to
which
>it is addressed and may contain confidential and/or privileged material.
Any
>review, re-transmission, dissemination or other use of, or taking of any
action
>in reliance upon, this information by persons or entities other than the
>intended recipient is prohibited.  If you receive this in error, please
contact
>the sender and delete the material from any computer.
>