Antwort: transports

Tue Aug 9 11:52:54 EDT 2005

Just some words of warning in using OOCR, this affects the PD side of HR.  When we changed the settings on OOCR, our HR analysts who were doing testing in DEV started seeing the transport requests popup.  We worked with them to come up with a solution that worked for Workflow Developers and our HR Analysts. One of our HR analysts summarized the issue and solution. I think you will find this very helpful:
Issue Summary
The automatic transport of PD objects is "Activated" in DV7 to assure proper transport of workflow objects (object types TS and WS).  This leaves us vulnerable to the inadvertent transport of other PD objects, e.g. Jobs, Organizational Units, or Positions, if they are accidentally incorporated in a transport.
Solutions
A partial solution is to deactivate transports for organizational units by setting the flag TRSP/ADMIN to 'X' in table T77S0 (see note 33582).  This turns off the transport window pop-up when performing Personnel Actions (transaction PA40).  However, this still leaves us open to updates of PD objects via other transactions.

A solution is offered via the "Transport Lock for Infotypes and Subtypes by Object" table, T77SR.  This table provides a means to prevent data from being updated in a target system via the transport process (see note 138411).  Inserting an entry in the table sets an import lock.  

For example, the entry:
* S, 1001, A002

Would prevent import of the "Reports to" relationship for a position.

Proposal
(1)	Set transport flags in T77S0 as follows (using transaction OOCR):
* TRSP COOR 		' '	- automatic transport of PD object ON
* TRSP ADMIN 	'X'	- transport of organizational units OFF

(2)	Lock transports for the following "High Risk" objects and infotypes (using transaction OOTR).  This provides a necessary safeguard against accidental update of the production system.  The proposed locks prevent not only creation of the specific objects, but also the naming of any relationships (infotype 1001) to the objects.  

Object	Infotype	Description
C	1000	JOB
O	1000	ORG UNIT
S	1000	POSITION
L	1000	BUSINESS EVENT GROUP
D	1000	BUSINESS EVENT TYPE
E	1000	BUSINESS EVENT
Q	1000	QUALIFICATION
QK	1000	QUALFICATION GROUP

Jane Simonetti
Sacramento Municipal Utility District 
916-732-5234

 -----Original Message-----
From: 	sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]  On Behalf Of Mike Pokraka
Sent:	Tuesday, August 09, 2005 8:36 AM
To:	SAP Workflow Users' Group
Subject:	RE: Antwort: transports

That'll be one for the FAQ :)

Cheers
Mike

robert.van.den.berg at accenture.com wrote:
> Finally, a mistery (for me anyway) is solved!!! Great transaction!
>
> Thank you very much Jane!!
>
> Regards,
> Robert
>
> ________________________________
>
> Van: sap-wug-bounces at mit.edu namens Jane Simonetti
> Verzonden: di 9-8-2005 16:17
> Aan: SAP Workflow Users' Group
> Onderwerp: RE: Antwort: transports
>
>
> You can use transaction OOCR and make sure the 'TSRP CORR' entry does NOT
> have an 'X' in the Value column. You will then be prompted for a transport
> request when you make your task a general task. This is a Customization
> transport that you will need to transport after your Workbench transports.
>
> Jane Simonetti
> Sacramento Municipal Utility District
> 916-732-5234
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf Of
> robert.van.den.berg at accenture.com
> Sent: Monday, August 08, 2005 5:26 AM
> To: sap-wug at mit.edu
> Subject: RE: Antwort: transports
>
> Nope, there is a setting which makes it possible to include it in the
> transports, but I can't remember where this setting is..
>
> What I found with google:
> To allow transport of agent assignments, the value of the semantic
> abbreviation CORR for the TRSP group name must be empty in table T77S0."
>
> "Transport lock for infotypes and subtypes per object (transaction OOTR
> Entry: S/1001/A008): this setting is
> made to prevent holders of positions being overwritten after transporting
> organizational plan changes from
> development tot production."
>
> There is also a program (RHMOVE30) in which you can make a transport
> request for the general task setting.
>
> ________________________________
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of U.Schroeder at westinvest.de
> Sent: maandag 8 augustus 2005 13:45
> To: SAP Workflow Users' Group
> Subject: Antwort: transports
>
> Hi Hohn,
>
> unfortunately the setting of the tasks as "general tasks" has to be done
> manually in every single system.
>
> Regards
>
> Ute
>
>
>
> John A Haworth <jhoworth at csc.com>
> Gesendet von: sap-wug-bounces at mit.edu
> 08.08.2005 13:31
> Bitte antworten an
> "SAP Workflow Users' Group" <sap-wug at mit.edu>
> An
> SAP-WUG at MITVMA.MIT.EDU
> Kopie
>
> Thema
> transports
>
>
>
>
>
>
>
>
>
>
> Hi all,
>
> I am transporting from Dev to Test, a workflow and number of tasks. Is
> there a way of also transporting the fact that the tasks have been set as
> 'General Tasks' as this doesn't seem to go with the workflow transports.
>
> Kind Regards
>
> John
>
>
> ----------------------------------------------------------------------------------------
>
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind CSC to any order or other contract unless pursuant to explicit
> written
> agreement or government initiative expressly permitting the use of e-mail
> for such purpose.
> ----------------------------------------------------------------------------------------
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 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.
>
>
> 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
>

Mike Pokraka
Senior Consultant
Workflow Connections Ltd.
Mobile: +44 (0)7786 910 855
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug