Webflow Future

Fri Oct 6 10:11:20 EDT 2006

I'm also happy to hear it's called "worflow" these days, the "work" bit
always put me off ;-)

On Fri, October 6, 2006 13:47, Josef Herwig wrote:
> Hello Jocelyn,
>
> many thanks for your quick answer!
>
> I'm happy to hear that it is called worflow again :-)
>
> Best Regards,
> Josef
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] Im Auftrag
> von sap-wug-request at mit.edu
> Gesendet: Freitag, 6. Oktober 2006 07:15
> An: sap-wug at mit.edu
> Betreff: SAP-WUG Digest, Vol 23, Issue 16
>
> 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. RE: Report on substitution (Dart, Jocelyn)
>    2. RE: Webflow Future (Dart, Jocelyn)
>    3. RE: Object Type Attributes (Dart, Jocelyn)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 6 Oct 2006 13:05:00 +0800
> From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
> Subject: RE: Report on substitution
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
> 	<F843AF000027394A9F3D3194109269F4984997 at sgsine11.sin.sap.corp>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Prasath,
>
> There is nothing that will give you this information if you are not
> capturing the original recipient.  The workflow log will show the actual
> agent of a work item, and work items that have been forwarded, but not
> when substitution was used.
>
> If you want to do this you need to ensure each of your workflows
> captures the original recipient of a work item into a suitable workflow
> container element - preferably giving the container element the same
> name across all workflows.   You could then compare the original
> recipient with the actual recipient.  Of course this does not mean a
> non-original actual recipient was a substitute - the work could have
> been forwarded to them manually or automatically as part of escalation.
>
> This is why its good to have a strategic approach to workflows and to
> ensure common patterns are used where possible across your workflows.
>
>
>
> Regards,
> Jocelyn Dart
> Senior Consultant
> SAP Australia Pty Ltd.
> Level 1/168 Walker St.
> North Sydney
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> http://www.sap.com <http://www.sap.com/>
>
> The information contained in or attached to this electronic transmission
> is confidential and may be legally privileged. It is intended only for
> the person or entity to which it is addressed. If you are not the
> intended recipient, you are hereby notified that any distribution,
> copying, review, retransmission, dissemination or other use of this
> electronic transmission or the information contained in it is strictly
> prohibited. If you have received this electronic transmission in error,
> please immediately contact the sender to arrange for the return of the
> original documents.
>
> Electronic transmission cannot be guaranteed to be secure and
> accordingly, the sender does not accept liability for any such data
> corruption, interception, unauthorized amendment, viruses, delays or the
> consequences thereof.
>
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the
> sender is authorized to state them to be the views of SAP AG or any of
> its subsidiaries. SAP AG, its subsidiaries, and their directors,
> officers and employees make no representation nor accept any liability
> for the accuracy or completeness of the views or information contained
> herein. Please be aware that the furnishing of any pricing information/
> business proposal herein is indicative only, is subject to change and
> shall not be construed as an offer or as constituting a binding
> agreement on the part of SAP AG or any of its subsidiaries to enter into
> any relationship, unless otherwise expressly stated.
>
>
>
> ________________________________
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of prasath natesan
> Sent: Thursday, 05 October 2006 10:04 PM
> To: SAP Workflow Users' Group
> Subject: Report on substitution
>
>
> Hi All,
> My client requires a report which needs to display details on
> substitution. The major requirement would be to display the "actual
> responsible agent" and "actual executor" of each workitem. For example
> we should be able to retrieve and display all the workitems that were
> executed by a substitute of one particular agent. I have checked with
> HRUS_D2 but this table just gives the information of substitution period
> and status. Is there a table (or any report) which gives the details of
> workitems executed by substitutes?
> We are at ECC 5.0 with EP 6.0.
>
> Thanks & Regards,
> Prasath N
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20061006/203f57e4/a
> ttachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Fri, 6 Oct 2006 13:11:54 +0800
> From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
> Subject: RE: Webflow Future
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
> 	<F843AF000027394A9F3D3194109269F4984999 at sgsine11.sin.sap.corp>
> Content-Type: text/plain;	charset="us-ascii"
>
> Hi Josef,
>
> Try looking under the BPM area (Business Process Management), and you
> may find more info on sdn.sap.com.
>
> 1. Webflow is now called Workflow again and yes it is here to stay.
>
> 2. Releases are announced when they are announced. ReleaseNotes for
> Netweaver 04s (7.0) you should find on help.sap.com or service.sap.com
> as this is the latest General Available version of Netweaver.   6.40 is
> now one release behind.
>
> 3. Upgrade from a lower release to a higher release is generally allowed
> for all development constructs of which workflows are just one of many -
> i.e. it doesn't depend on workflow it depends on the upgrade paths
> allowed from one release to another.  Going the other way isn't (no
> guarantees downgrades will work).
>
>
> Regards,
> Jocelyn Dart
> Senior Consultant
> SAP Australia Pty Ltd.
> Level 1/168 Walker St.
> North Sydney
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> http://www.sap.com
>
> The information contained in or attached to this electronic transmission
> is confidential and may be legally privileged. It is intended only for
> the person or entity to which it is addressed. If you are not the
> intended recipient, you are hereby notified that any distribution,
> copying, review, retransmission, dissemination or other use of this
> electronic transmission or the information contained in it is strictly
> prohibited. If you have received this electronic transmission in error,
> please immediately contact the sender to arrange for the return of the
> original documents.
> Electronic transmission cannot be guaranteed to be secure and
> accordingly, the sender does not accept liability for any such data
> corruption, interception, unauthorized amendment, viruses, delays or the
> consequences thereof.
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the
> sender is authorized to state them to be the views of SAP AG or any of
> its subsidiaries. SAP AG, its subsidiaries, and their directors,
> officers and employees make no representation nor accept any liability
> for the accuracy or completeness of the views or information contained
> herein. Please be aware that the furnishing of any pricing information/
> business proposal herein is indicative only, is subject to change and
> shall not be construed as an offer or as constituting a binding
> agreement on the part of SAP AG or any of its subsidiaries to enter into
> any relationship, unless otherwise expressly stated.
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Josef Herwig
> Sent: Friday, 06 October 2006 3:05 AM
> To: sap-wug at mit.edu
> Subject: Webflow Future
>
> Hello folks,
>
>
> maybe anybody of you has an answer to the following questions:
>
> 1. Will the SAP Webflow Engine bepart of the Netweaver Architecture in
> the future? Currently it is but i have no information regarding the
> future planning of SAP.
>
> 2. Which new features will SAP provide in the Webflow area for WAS
> greater than 6.40? I already checked www.service.sap.com/workflow but i
> didn't found
> the information which i was looking for. Maybe there are other links
> which could help or direct information.
>
> 3. Currently it is possible to move workflows from 4.6C to 4.7
> enterprise (my own experience) but will this also be possible for 4.6C
> to 6.40 or higher for the future? I can imagine that it must be possible
> for "simple"
> workflow definitions but maybe some "special" constructions could make
> trouble.
>
> Many thanks in advance for your help!
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 6 Oct 2006 13:15:11 +0800
> From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
> Subject: RE: Object Type Attributes
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
> 	<F843AF000027394A9F3D3194109269F498499C at sgsine11.sin.sap.corp>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Renier,
>
> Number of levels? In theory as many as you like until memory runs out.
> In practice most people limit it to about 3 levels as after that it
> starts getting tedious especially if any of the intermediate objects
> cannot be instantiated.
>
> In your object program use
>
> SWC_GET_PROPERTY SELF 'Propertyname' localvariable.
>
> Full syntax and explanations in The Book.
>
>
> Regards,
> Jocelyn Dart
> Senior Consultant
> SAP Australia Pty Ltd.
> Level 1/168 Walker St.
> North Sydney
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> http://www.sap.com <http://www.sap.com/>
>
> The information contained in or attached to this electronic transmission
> is confidential and may be legally privileged. It is intended only for
> the person or entity to which it is addressed. If you are not the
> intended recipient, you are hereby notified that any distribution,
> copying, review, retransmission, dissemination or other use of this
> electronic transmission or the information contained in it is strictly
> prohibited. If you have received this electronic transmission in error,
> please immediately contact the sender to arrange for the return of the
> original documents.
>
> Electronic transmission cannot be guaranteed to be secure and
> accordingly, the sender does not accept liability for any such data
> corruption, interception, unauthorized amendment, viruses, delays or the
> consequences thereof.
>
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the
> sender is authorized to state them to be the views of SAP AG or any of
> its subsidiaries. SAP AG, its subsidiaries, and their directors,
> officers and employees make no representation nor accept any liability
> for the accuracy or completeness of the views or information contained
> herein. Please be aware that the furnishing of any pricing information/
> business proposal herein is indicative only, is subject to change and
> shall not be construed as an offer or as constituting a binding
> agreement on the part of SAP AG or any of its subsidiaries to enter into
> any relationship, unless otherwise expressly stated.
>
>
>
> ________________________________
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Renier Walters
> Sent: Friday, 06 October 2006 9:32 AM
> To: sap-wug at mit.edu
> Subject: Object Type Attributes
>
>
> I have created ZVBAP object and delegated from VBAP object.  Within the
> ZVBAP object I have Object MATERIAL(BUS1001).  Now within the MATERIAL
> object exists a PURCHASEORDER(BUS2012) object.  Say for arguments sake I
> would like to grab the Vendor attribute within the PURCHASEORDER object.
>
>
> How many levels deep can I access these values in the imbedded objects
> and how do I access these values in any of the methods in my ZVBAP
> object?
>
> Do I use SWC_GET_ELEMENT CONTAINER or SWC_GET_PROPERTY SELF etc in my
> method.  I am not sure what the ABAP syntax should look like.
>
> Any help would be appreciated.
>
> Thanks in advance,
> Renier
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20061006/41105af8/a
> ttachment.htm
>
> ------------------------------
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> End of SAP-WUG Digest, Vol 23, Issue 16
> ***************************************
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>