SAP Workflows (Vimal Soni)

Thu Nov 16 09:07:22 EST 2006

Welcome to the WUGers Vimal,
I would strongly recommend purchasing THE book of workflow "Practical
Workflow for SAP" by our esteemed WUG members Alan Rickayzen and Jocelyn
Dart.  
Cheers,
Sherie 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of shireesh.mitragotri at accenture.com
Sent: Thursday, November 16, 2006 2:18 AM
To: sap-wug at mit.edu
Subject: SAP Workflows (Vimal Soni)

Hi Vimal - On R/3 Enterprise I did not see an out-of-the-box Material
Master Task provided by SAP so you can create a Workflow template,
listen to the BOR/Event of Material create and use the step type of Send
mail to send the info. 

________________________________

From: sap-wug-bounces at mit.edu on behalf of sap-wug-request at mit.edu
Sent: Thu 11/16/2006 10:17 AM
To: sap-wug at mit.edu
Subject: SAP-WUG Digest, Vol 24, Issue 43

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. Specifying Interface as Importing parameter (Alon Raskin)
   2. RE: Creating Excel sheets in background [slightly OT]
      (Soady, Phil)
   3. RE: Specifying Interface as Importing parameter (Dart, Jocelyn)
   4. SAP Workflows (Vimal Soni)

----------------------------------------------------------------------

Message: 1
Date: Wed, 15 Nov 2006 16:12:51 -0500
From: "Alon Raskin" <araskin at 3i-consulting.com>
Subject: Specifying Interface as Importing parameter
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
        <CEF21C1C5BF2FA42A42CEC87B91BBCDED61836 at ms07.mse2.exchange.ms>
Content-Type: text/plain; charset="iso-8859-1"

Well this Workflow-OO stuff just gets better and better.

It seems that I can not declare a container element of type interface.
The workflow editor requires a concrete type and will not allow me to
specify an element whose type is an interface. The way I see it, this
basically blows away any polymorphic behaviour within Workflow and
greatly reduces the benefits of using OO in SAP Workflow (feel free to
let me know that I am over reacting). To make things worse I can achieve
this using the old BOR by simply not specifying a type.

Before you ask, here is what I am trying to achieve, I am creating a
workflow which should be able to accept any instance of a class which
implements the BI_PERSISTENT interface. However, when I define my
importing container element I am given an error that tells me that I can
not specify a container element of type BI_PERSISTENT and must specify a
concrete type.

Am I going crazy or is this a big 'hole' in the OO - Workflow
implementation?

Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
p: +1 207 523 3489
c: +1 207 409 4983
f:  +1 806 403 4983

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 4712 bytes
Desc: not available
Url :
http://mailman.mit.edu/pipermail/sap-wug/attachments/20061115/2e48cb34/a
ttachment-0001.bin

------------------------------

Message: 2
Date: Thu, 16 Nov 2006 07:31:09 +0800
From: "Soady, Phil" <phil.soady at sap.com>
Subject: RE: Creating Excel sheets in background [slightly OT]
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
        <F843AF000027394A9F3D3194109269F4B3C871 at sgsine11.sin.sap.corp>
Content-Type: text/plain;       charset="us-ascii"

did you use XSLT to generate the XML file ?

Phil Soady
Solution Architect
Netweaver Consulting
SAP Australia
M  +61 412 213 079
F  +61 2 9957 7263
mailto:phil.soady at sap.com

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Thursday, 16 November 2006 3:29 AM
To: SAP Workflow Users' Group
Subject: Re: Creating Excel sheets in background [slightly OT]

Short update on this:
Excel supports an XML format where you can generate almost anything you
like from pretty colours to pivot tables in an XML file which you can
attach to an email as a proper Excel file. Small word of warning: though
not very difficult, it can be quite laborious and a lot of coding.

Thanks all for your help - especially David for all the code.
Cheers,
Mike

On Thu, November 2, 2006 18:01, Mike Pokraka wrote:
> Hi all,
>
> We have a requirement where a mail is sent out to a user with some
info.
> Basic stuff, however the twist here is that they require this as an
Excel
> spreadsheet.
>
> Easy enough to do in dialog, but does anyonw know how to create an
Excel
> spreadsheet attachment in background? All methods we've lookied at
come
> back to the use of OLE functions which require a GUI session of a user

> with Excel installed. This must be completely in background.
>
> I know this is on the far-flung borders of the workflow realm, but
seeing
> as we have some very knowledgeable people on this list I figured I
might
> throw the question out here.
>
> Any input appreciated.
> Cheers,
> Mike
>
>
> _______________________________________________
> 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: 3
Date: Thu, 16 Nov 2006 11:15:31 +0800
From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
Subject: RE: Specifying Interface as Importing parameter
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Cc: "Janetz, Frank" <frank.janetz at sap.com>
Message-ID:
        <F843AF000027394A9F3D3194109269F4B3C993 at sgsine11.sin.sap.corp>
Content-Type: text/plain; charset="us-ascii"

Hi Alon,

One of the basic rules is you have to obey is that your class must
support interface IF_WORKFLOW.

BI_PERSISTENT does not support IF_WORKFLOW.  Also as BI_PERSISTENT is
part of the IF_WORKFLOW interface you could run into recursive scenarios
so best to create something completely separate.

Perhaps what you are looking for is a container element that is an
object type of category ABAP Class but without the class name
specified???   This is ok to do and lets you pass in any workflow
capable class at runtime.

Widening and narrowing bindings are possible - make sure you use the
arrowhead button to refine the binding rules, e.g. when narrowing cast
you might want to use "handle error as warning".

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 Alon Raskin
Sent: Thursday, 16 November 2006 8:13 AM
To: SAP Workflow Users' Group
Subject: Specifying Interface as Importing parameter

Well this Workflow-OO stuff just gets better and better.

It seems that I can not declare a container element of type interface.
The workflow editor requires a concrete type and will not allow me to
specify an element whose type is an interface. The way I see it, this
basically blows away any polymorphic behaviour within Workflow and
greatly reduces the benefits of using OO in SAP Workflow (feel free to
let me know that I am over reacting). To make things worse I can achieve
this using the old BOR by simply not specifying a type.

Before you ask, here is what I am trying to achieve, I am creating a
workflow which should be able to accept any instance of a class which
implements the BI_PERSISTENT interface. However, when I define my
importing container element I am given an error that tells me that I can
not specify a container element of type BI_PERSISTENT and must specify a
concrete type.

Am I going crazy or is this a big 'hole' in the OO - Workflow
implementation?

Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
p: +1 207 523 3489
c: +1 207 409 4983
f:  +1 806 403 4983

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20061116/b2126eda/a
ttachment-0001.htm

------------------------------

Message: 4
Date: Thu, 16 Nov 2006 10:16:56 +0530
From: "Vimal Soni" <sonivimalkishore at gmail.com>
Subject: SAP Workflows
To: sap-wug at mit.edu
Message-ID:
        <2ed37fb20611152046t68273753u747c89458884a3a0 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hello

We are on SAP R/3 Enterprise 4.7x1.10.

I am responsible for SAP management of two indian chemical units of
Aditya Birla Group.

I am from FICO and have good domain knowledge of MM and SD too but have
no ABAP knowledge.

We would like to implement standard workflows without ABAP development
and would like to start with MM workflows.

To start with, we would like to implement a workflow whereby our users
would be sent an e-mail (Tran SBWP) whenever a material master is
created through
MM01 transaction code.

I would appreciate your help with detailed screen shots.

Regards.

Vimal Soni, India
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20061116/8495dcc2/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 24, Issue 43
***************************************

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete
the original.  Any other use of the email by you is prohibited.

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug