Task attributes not getting transported properly
Soady, Phil
phil.soady at sap.com
Wed Jun 14 08:48:01 EDT 2006
Jocelyn has helped enough, so to give her a break , some quick answers:
- Where is the setting to indicate I have to move the request from
client 200 to 300 ?
(A)The transport itself has a target. The target is defaulted and
controlled via STMS. Ask your adminstrator to send the request to the
clients required.
Which of the indicators to be selected?- Transport, delete objects,
replace person with user, with lock?
(A) Transport... needed if you want to send / select anything
Delete - deletes the matching objects. (VERY CAREFUL) in the
originating client as well.
LOCK, the transport marks the entries as locked. So further changes
are not possible until transport is released. I have not used it.
The online docu : Press F1 on the fields on selection screen for more.
Suggest you test with 1 object in DEV from client a to b before using
in bulk.
Cheers
Phil Soady
Solution Architect
Netweaver Consulting
SAP Australia
M +61 412 213 079
F +61 2 9957 7263
mailto:phil.soady at sap.com <mailto:phil.soady at sap.com>
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of akshay.bhagwat at wipro.com
Sent: Wednesday, 14 June 2006 4:30 PM
To: sap-wug at mit.edu
Subject: RE: Task attributes not getting transported properly
Hi Jocelyn,
Can you please help me out by elaborating it once again on following
fronts for this report:
- Where is the setting to indicate I have to move the request from
client 200 to 300?
- Which of the indicators to be selected?- Transport, delete objects,
replace person with user, with lock?
Tried to read report documentation, however I could not get the purpose
of delete objects , replace and lock options.
Thanks in advance.
Regards,
Akshay Bhagwat
SAP Practice
Wipro Technologies
': +91 20 2293 3700 x 3608
Fax: +91 20 2293 3756
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Tuesday, June 13, 2006 12:25 PM
To: SAP Workflow Users' Group
Subject: RE: Task attributes not getting transported properly
Yes. The settings are client dependent.
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 4:04 PM
To: sap-wug at mit.edu
Subject: RE: Task attributes not getting transported properly
Hi Jocelyn,
Thanks for the valuable inputs, however wanted to know is this procedure
also applicable if I want to move this data in same system , but in
different clients? e.g. from client 300 to client 400 of system TST.
Regards,
Akshay Bhagwat
SAP Practice
Wipro Technologies
': +91 20 2293 3700 x 3608
Fax: +91 20 2293 3756
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Tuesday, June 13, 2006 10:13 AM
To: SAP Workflow Users' Group
Subject: RE: Task attributes not getting transported properly
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,
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
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
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/20060614/e43c80dc/attachment.htm
More information about the SAP-WUG
mailing list