Purchase Order Question

Tue Jun 13 09:31:23 EDT 2006

Dan,

It shouldn't have happen. 
However please note that you might front a problem: each PO item can
have a different cost center. In such case release strategy will not be
assigned.

As for you issue, try using the "releaseStepCreated" event.

You should also verify workflow customization in PO release strategy.

Good luck.

Regards,
Shai Eyal

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of sap-wug-request at mit.edu
Sent: Tuesday, June 13, 2006 6:44 AM
To: sap-wug at mit.edu
Subject: SAP-WUG Digest, Vol 19, Issue 31

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. BBP_WFL_SECUR_BADI_S  (Susan R. Keohan)
   2. Purchase Order Question (Stoicof, Dan)
   3. RE: Guided Procedures and Workflow (Dart, Jocelyn)
   4. Task attributes not getting transported properly
      (akshay.bhagwat at wipro.com)
   5. RE: Task attributes not getting transported properly
      (Dart, Jocelyn)

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

Message: 1
Date: Mon, 12 Jun 2006 14:23:57 -0400
From: "Susan R. Keohan" <keohan at ll.mit.edu>
Subject: BBP_WFL_SECUR_BADI_S
To: "SAP Workflow Users' Group" <SAP-WUG at MIT.EDU>
Message-ID: <448DB13D.4080002 at ll.mit.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed

SRM 5.0

All,

This is not a specific question, just trying to gather some info...

We know that this BADI can be used to set the security level to
allow/disallow changes during the WF 
approval process.   We've also tested and found that if the BADI sets
the Security Authorization to 
4 (highest) then a substitute who has 1 (lowest) is able to change the
SC through the inbox.

It doesn't seem that this BADI allows you to allow/disallow changes to
the Cart depending on the level of approval...

For example: the same approver may be required to change carts when they
are seeking 'level 1' 
approval, but we need to prevent that approver from changing the cart
when it needs 'level 2' 
approval.

Similarly, we want to prevent Shoppers from changing carts while they
are involved in a workflow process, and yet there is a business
requirement that these shoppers should be able to delete the cart.

I would be interested in hearing about your implementations of
BBP_WFL_SECUR_BADI_S.

Regards,
Sue
--
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu

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

Message: 2
Date: Mon, 12 Jun 2006 15:08:18 -0600
From: "Stoicof, Dan" <dan.stoicof at gwl.com>
Subject: Purchase Order Question
To: <sap-wug at mit.edu>
Message-ID:

<FD1944EFCA4BFE46886FCC05B0D4D01101D0F2BC at ITS-EXMBX3.its.corp.gwl.com>
Content-Type: text/plain;  charset="iso-8859-1"

Greetings,

We have a need to change the release strategy for PO's, by adding a
characteristic.  I have added a new table element  (KOSTL - cost center)
to table cekkozz, activated the exit M06E004, created the
characteristic, added it to the class, and to the release strategy (phew
. . .!).

My problem?  Now FREBUS2012.CREATED is being triggered, instead of
BUS2012.CREATED.  Is this what's supposed to happen?

Thanks!

Dan Stoicof

GREAT-WEST LIFE and ANNUITY

The information contained in this message and any accompanying
attachments may contain privileged, private and/or confidential
information protected by state and federal law. Penalties may be
assessed for unauthorized use and/or disclosure. This message and any
attachments are intended for the designated recipient only. If you have
received this information in error, please notify the sender immediately
and return or destroy the information.

This e-mail transmission and any attachments are believed to have been
sent free of any virus or other defect that might affect any computer
system into which it is received and opened. It is, however, the
recipient's responsibility to ensure that the e-mail transmission and
any attachments are virus free, and the sender accepts no responsibility
for any damage that may in any way arise from their use.

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

Message: 3
Date: Tue, 13 Jun 2006 08:18:00 +0800
From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
Subject: RE: Guided Procedures and Workflow
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
	<F843AF000027394A9F3D3194109269F453BD25 at sgsine11.sin.sap.corp>
Content-Type: text/plain;	charset="iso-8859-1"

Hi Jerry, 

Yes that's a pain... try the
great-idea-but-too-risky-right-now-let's-do-it-properly-and-run-a-pilot-
afterwards approach if you haven't already.  Roll on Enterprise SOA... 

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 jerry.martinek
Sent: Friday, 09 June 2006 11:52 PM
To: 'SAP Workflow Users' Group'
Subject: RE: Guided Procedures and Workflow

Hi Jocelyn,

We haven't tried a lot of the things you're suggesting for various
different
reasons as well as not being aware of some of the product features.

At this point in the development stage of our project, introducing new
unknown technology to write our own travel request and expense
application
is not the correct decision. 

Your answer confirmed my suspicion that there is more to it than you're
led
to believe. So when a non IT person reads that article, they get the
impression that the IT guys are holding back. They can't understand why
we're telling them that it's not that straight forward in 'our' case.

Thanks,
Jerry   

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of
Dart, Jocelyn
Sent: June 9, 2006 12:18 AM
To: SAP Workflow Users' Group
Subject: RE: Guided Procedures and Workflow

Hey Jerry, 

The standard SAP trip allows you to split up the  travel request items
to
different accounts. We use the same one at SAP and it works fine. 

Possibly its a missing customization issue?  Or it's just the EP views
that
are a problem
in which case yes you are better off adjusting the iviews.   You could
try
calling the original app via SAPGUI for HTML as well. 

Have you checked to see if there is an Adobe or WebDynpro version that
you
can use?  This will probably depend on the backend release you are
running
ESS on, as with NW04s portal you have the lot in terms of capability.
Both
would let you do attachments or easily extend to do attachments. 

Also remember that in NW04s the UWL has the attachment manager which may
give you some further options, e.g. start form, send work item "do you
have
any attachments" (make it processing rejectable), then go forward to
approval. 

GP will let you do attachments but:

1. Remember its still relatively new - e.g. agent determination and
asynchronous/terminating event functionality is not approaching the
standard
of SAP Workflow as yet.

2. You still need an underlying application to call from GP - similar to
workflow.  You can use Adobe or a WebDynpro for instance as an
alternative
to iviews.  It does provide a number of helper applications but for
something as complex as a travel request you will probably end up doing
your
own app or an adjusted version of SAP's standard app anyway. 

GP is great if you want to run a step by step process that your business
analyst maintains and that may run against multiple backend systems -
i.e.
if you want process integration driven by the business rather than IT.
But
it's still early days and you should not expect the depth of features
you
find in SAP Workflow currently.  

If your management is super keen you might want to do a proof-of-concept
to
explain the differences.  Given the trip request is fully in one system,
and
given the relative maturity of Workflow vs GP, I would suggest SAP
Workflow
is probably going to meet your needs better, even if you have to do some
work on the web app for the original travel request entry. 

Don't discourage them from using GP - it's going to be a case by case
basis
for a while yet.  For the moment think - multi-system/frequent business
changes -> GP, single system/stable process/deep integration ->
Workflow. 

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
Mikko M?ki-Rahkola
Sent: Friday, 09 June 2006 4:39 PM
To: sap-wug at mit.edu
Subject: Re: Guided Procedures and Workflow

Hi Jerry,

Alan will probably give you a more 'official' view on GP himself but
here are my comments...

First, I didn't quite understand one of the requirements you stated.
What did you mean by travel request itemization? Do you have a
requirement to split up the travel request advance amount?

Writing the travel doc entry applications from scratch is I think a
huge task, not only do you need to get all the view logic there but
also connect to the backend to get help values, transfer the data etc.
So I think the business case might not be that good counting in the
maintenance cost in addition to the development cost.

Couldn't you just modify the current travel request/expense report Web
Dynpro apps directly and then use them as is? SAP delivers the source
code for these so putting in some logic of your own (like attachment
entry or itemization) shouldn't take that long from a skilled WD
developer.

In my current project we have implemented Web Dynpro-enabled travel
request and expense report approval workflows (running on ECC5.0 &
EP6.0). We have had some smaller changes done to the entry
applications and created a custom approval/checking application (I
believe ECC6.0 has a standard app for this), too. All this works well
together, workflow as the backbone glueing all the WD pieces into a
fully web-enabled workflow.

Regarding Guided Procedures, I think you can't directly include the
standard travel WD apps there because of missing WD interfaces. Using
GP would thus basically require you to develop your own GP-supported
Web Dynpro application or a plain form, which brings me back to the
business case point I raised at first. SAP's view on GP's usage also
seems to be against this, I believe they recommend GP only for
departmental processes, not company-wide like a travel request or
expense report approval process.

So in conclusion, I believe GP might not be the best choice here. You
have quite a lot of existing functionality exposed as Web Dynpros
which you can use by doing small modifications and tying them up with
workflow. The other GP way would require a lot of SAP standard
overwriting and would leave you out on your own regarding support.

If you are interested in our project details, please contact me
directly and I'll be happy to share any helpful information.

Best regards,
Mikko
_______________________________________________
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

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

Message: 4
Date: Tue, 13 Jun 2006 09:56:51 +0530
From: <akshay.bhagwat at wipro.com>
Subject: Task attributes not getting transported properly
To: <sap-wug at mit.edu>
Message-ID:
	<0F35D2C4458E9B4A9891BE2D4E0C8390F84DD9 at PNE-HJN-MBX01.wipro.com>
Content-Type: text/plain; charset="us-ascii"

Hello,

Point no 1.:
For a particular scenario, I had assigned task property as general task
for one of the tasks used in workflow.
As we need to move this to testing client, using transaction SCC1, I
moved the same config to testing client.
This happened successfully and I could see task as general task in
testing client.
However, later I changed the task properties as General forwarding not
allowed, and assigned specific Positions to this task.

Now when I am trying to move this to testing client, the changes are not
getting reflected in testing client.
Could you pls suggest, what might be the reason?

point no.2

Instead of assigning many positions in Org structure, I tried to assign
the Root org unit to this task, however at run time I got error in WF
saying object type A not allowed. So wanted to know that can we not
assign Root org units to tasks?

Thanks in Advance.
Regards,

Akshay Bhagwat

SAP Practice

Wipro Technologies

The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If
you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of viruses.
The company accepts no liability for any damage caused by any virus
transmitted by this email.

www.wipro.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20060613/14bbea66/a
ttachment-0001.htm

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

Message: 5
Date: Tue, 13 Jun 2006 12:43:27 +0800
From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
Subject: RE: Task attributes not getting transported properly
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
	<F843AF000027394A9F3D3194109269F453BE83 at sgsine11.sin.sap.corp>
Content-Type: text/plain; charset="us-ascii"

Ok .. I really think its time this one was on the FAQ - Mike P. can you
assist?

Task attributes are client dependent so they are not transferred by
change requests. 
Task attributes are not customizing so they are not transferred by
customizing requests. 
Task attributes are HR data.  
To transport HR data you must use an HR transport program such as
RHMOVE30. 

Nominate your task, list of tasks, or task group. 
Use evaluation path TASKHIER.
Nominate a transport request.
On the results list, select all tasks for transport and then include
them in the transport request. 

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 akshay.bhagwat at wipro.com
Sent: Tuesday, 13 June 2006 2:27 PM
To: sap-wug at mit.edu
Subject: Task attributes not getting transported properly

Hello,