Person Reponsible feature
Kjetil Kilhavn
KJETILK at statoil.com
Thu Jan 24 01:51:42 EST 2002
You can create a work centre in development and transport it to production, then
populate it differently in development and production. Works for me :-)
--
Kjetil Kilhavn
|--------+------------------------------>
| | "Martinek, Jerry" |
| | <Jerry.Martinek at icbc|
| | .com> |
| | Sent by: SAP |
| | Workflow |
| | <Owner-SAP-WUG at MITVM|
| | A.MIT.EDU> |
| | |
| | |
| | 23.01.2002 18:20 |
| | Please respond to |
| | "SAP Workflow Users'|
| | Group" |
| | |
|--------+------------------------------>
>----------------------------------------------------------------------------|
| |
| To: SAP-WUG at MITVMA.MIT.EDU |
| cc: (bcc: Kjetil Kilhavn) |
| Subject: Re: Person Reponsible feature |
>----------------------------------------------------------------------------|
Hi Stephan and Michael and thank you for the advice.
The process you described works as long as the desired 'user' who will be
the responsible for the workflow in the PROD environment exists in the
development environment where the actual workflow change is being made. If
they don't, the field validation edit fails thus preventing you from making
the change. It seems that in order for me to complete this change, I need to
define this production user in our development environment. Is this correct
or am I missing something?
Our development environment only contains the ids (usr01) of the people who
can access that environment.
Also, how does the 'Person Responsible' function in the 'Additional Data'
sub menu of the base 'Workflow Template: Add' work?
Thanking In Advance,
Jerry Martinek
-----Original Message-----
From: michael.klika at de.pwcglobal.com
[mailto:michael.klika at de.pwcglobal.com]
Sent: Wednesday, January 23, 2002 1:35 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Antwort: Person Reponsible feature
hi jerry!
not quite sure what you did exactly. try the following:
pftc_chg (in dev of course), open the wf-builder, menue:
GOTO->BASIC DATA
now you find on tab RESPONSIB. a field for a local sysadmin.
give the
desired name or better an organisational unit, position or
role.
now: save, activate, test, transport
hope this helps,
michael
>Hi, I need some help with the 'Person Responsible' feature.
My goal is to
override the workflow
> administrator definition for a custom workflow and
redirect any problems
with this workflow to a different person.
>
>I made what I thought were the required settings using the
'user' option
of the relationship definition.
> I ran a test but it didn't work, the specified person
didn't receive any
notice about the workflow failure. I
> forced a role resolution problem in one of the tasks
within the workflow.
>
>At this point I'm not sure if I don't understand the usage
of the feature
or if it's the way I made the change.
>I used PFTC_DIS in PROD to make the desired feature
setting. This sort of
seems strange that one
>is able to make the change using this technique.
>
>Any help would be greatly appreciated.
>
>We are currently on the latest 46c functional and 46d basis
versions.
>
>Thanking in advance,
>Jerry Martinek
----------------------------------------------------------------
Diese Information ist ausschliesslich fuer die adressierte
Person oder
Organisation bestimmt und koennte vertrauliches und/oder
privilegiertes
Material enthalten. Personen oder Organisationen, fuer die
diese
Information nicht bestimmt ist, ist es nicht gestattet,
diese zu lesen,
erneut zu uebertragen, zu verbreiten, anderweitig zu
verwenden oder sich
durch sie veranlasst zu sehen, Massnahmen irgendeiner Art zu
ergreifen.
Sollten Sie diese Nachricht irrtuemlich erhalten haben,
bitten wir Sie,
sich mit dem Absender in Verbindung zu setzen und das
Material von Ihrem
Computer zu loeschen.
Sie haben uns gebeten, mit Ihnen ueber das Internet per
E-Mail zu
korrespondieren. Unbeschadet dessen ist allein die von uns
unterzeichnete
schriftliche Fassung verbindlich.
Wir weisen darauf hin, dass derartige Nachrichten mit und
ohne Zutun von
Dritten verloren gehen, veraendert oder verfaelscht werden
koennen.Herkoemmliche E-Mails sind nicht gegen den Zugriff
von Dritten
geschuetzt und deshalb ist auch die Vertraulichkeit unter
Umstaenden nicht
gewahrt Wir haften deshalb nicht fuer die Unversehrtheit von
E-Mails
nachdem sie unseren Herrschaftsbereich verlassen haben und
koennen Ihnen
hieraus entstehende Schaeden nicht ersetzen. Sollte trotz
der von uns
verwendeten Virus-Schutz-Programmen durch die Zusendung von
E-Mails ein
Virus in Ihre Systeme gelangen, haften wir nicht fuer
eventuell hieraus
entstehende Schaeden. Dieser Haftungsausschluss gilt nur
soweit gesetzlich
zulaessig.
English:
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, retransmission, 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 received
this in error, please contact the sender and delete the
material from any
computer.
You have asked us to correspond with you via the Internet
per e-mail.
However, the written version signed by us is the only
authoritative
version. We draw your attention to the fact that such
messages can be
lost, changed or falsified, with or without any interference
by third
persons. Normal e-mails are not protected against access by
third persons
and, therefore, their confidentiality may not be assured in
certain
circumstances. We cannot be responsible for the integrity of
emails after
they have left our sphere of control. We shall not,
therefore, indemnify
you for any damages resulting out of these circumstances.
If, despite our
use of anti-virus software, a virus enters your systems in
connection with
the sending of the e-mail, you may not hold us liable for
any damages that
may possibly arise in that connection. We will accept
liability which by
law we cannot exclude.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20020124/32ff4280/attachment.htm
-------------- next part --------------
-------------------------------------------------------------------
Statoil: The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete this
message.
Thank you.
More information about the SAP-WUG
mailing list