Transporting Org Management Data from Dev to QA

Fri Mar 26 05:14:31 EST 2004

Hi Swami and Jocelyn,

Thanks for your answers. We also maintain the organization structure except the holders of positions on
development ans transport this to the other target systems/clients.

>From the previous messages I (wrongly) concluded that Swami maintained the whole orgnaization structure on
production, not only the holders of positions.

It's also clear to me now that if you maintain the whole organization structure (thus not only the assignment of
holders to positions) the assignment of responsible/excluded agents to the steps in the workflow definition is
also maintained on production.

Regards,

Fred Kouw

Swami Bala wrote:

> Hello Fred,
>
> We Maintained the org structure including the position in Dev transporting
> all the way across to PRD (except the holders ) .The workflow definition
> also has the same org assignment (including position) all the way from
> DEV.Then PPOMW can be used  in PRD to assign holders to this position (
> which was transported from DEV alongwith Org structure). This holder
> assignment then gets reflected in the workflow definition. Not sure we were
> doing the right thing but it was temoporary thing until we integrated HR
> Hope this helps..
>
> Swami Bala
>
> >From: "Kouw, FA - SPLXE" <fa.kouw at td.klm.com>
> >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Re: Transporting Org Management Data from Dev to QA
> >Date: Tue, 23 Mar 2004 11:03:40 +0100
> >MIME-Version: 1.0
> >Received: from mc5-f18.hotmail.com ([65.54.252.25]) by mc5-s2.hotmail.com
> >with Microsoft SMTPSVC(5.0.2195.6824); Tue, 23 Mar 2004 02:06:31 -0800
> >Received: from cherry.ease.lsoft.com ([209.119.0.109]) by
> >mc5-f18.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Tue, 23 Mar 2004
> >02:04:34 -0800
> >Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com
> >(LSMTP for Digital Unix v1.1b) with SMTP id
> ><2.00D3772B at cherry.ease.lsoft.com>; Tue, 23 Mar 2004 5:04:31 -0500
> >Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release
> >1.8e)          with spool id 9287 for SAP-WUG at MITVMA.MIT.EDU; Tue, 23 Mar
> >2004          05:04:10 -0500
> >Received: from MITVMA (NJE origin SMTP at MITVMA) by MITVMA.MIT.EDU (LMail
> >      V1.2d/1.8d) with BSMTP id 8161; Tue, 23 Mar 2004 05:03:39 -0500
> >Received: from mail7.messagelabs.com [194.151.197.68] by mitvma.mit.edu
> >(IBM VM          SMTP Level 430) via TCP with SMTP ; Tue, 23 Mar 2004
> >05:03:37 EST
> >Received: (qmail 20764 invoked from network); 23 Mar 2004 10:03:42 -0000
> >Received: from unknown (HELO splu0029.td.klm.nl) (213.31.197.133) by
> >   server-9.tower-7.messagelabs.com with SMTP; 23 Mar 2004 10:03:42 -0000
> >Received: from td.klm.com ([171.21.7.30]) by splu0029.td.klm.nl (Netscape
> >        Messaging Server 4.15 splu0029 Mar 21 2002 16:03:55) with ESMTP id
> >         HV0XA400.1IA for <SAP-WUG at MITVMA.MIT.EDU>; Tue, 23 Mar 2004
> >11:03:41          +0100
> >X-Message-Info: TSNaxu8CDoc9hJ4AgzwuyYZbJT2D4M3IPw0HowWg+Dc=
> >X-Comment: mitvma.mit.edu: Mail was sent by mail7.messagelabs.com
> >X-VirusChecked: Checked
> >X-Env-Sender: fa.kouw at td.klm.com
> >X-Msg-Ref: server-9.tower-7.messagelabs.com!1080036222!7009235
> >X-StarScan-Version: 5.1.15; banners=td.klm.com,-,-
> >X-Mailer: Mozilla 4.79 [en] (WinNT; U)
> >X-Accept-Language: nl,en
> >References: <C516DE3977D4D44D91DA0F47E176E28A643CA7
> >@miwimx10.tdscorp.tdsgroup.net>
> ><BAY2-DAV448KShPdHfK000008b7 at hotmail.com>
> ><405ECA7D.14DB818F at td.klm.com>
> ><BAY2-DAV26gDx23l3Ix00005dcd at hotmail.com>
> >Approved-By:  "Kouw, FA - SPLXE" <fa.kouw at TD.KLM.COM>
> >Message-ID:  <40600B7B.467CB0B4 at td.klm.com>
> >Organization: KLM Engineering and Maintenance
> >Precedence: list
> >Return-Path: owner-sap-wug at MITVMA.MIT.EDU
> >X-OriginalArrivalTime: 23 Mar 2004 10:04:35.0903 (UTC)
> >FILETIME=[3EF104F0:01C410BE]
> >
> >Hi Swami,
> >
> >I don't have any problem, I'm only curious how you assign a responsible
> >agent to a step in the workflow
> >definition (what object, f.i. job, position etc.) when you maintain the
> >org. plan on production (the object is
> >not available on development when maintaining it on production).
> >
> >Regards,
> >
> >Fred Kouw
> >
> >Hotmail wrote:
> >
> > > Hello Fred,
> > >
> > > You can use tcode PPOMW to assign holders to Position in Org structure.
> >Let
> > > me know
> > > if you still have problems..
> > >
> > > Swami Bala
> > >
> > > ----- Original Message -----
> > > From: "Kouw, FA - SPLXE" <fa.kouw at td.klm.com>
> > > To: <SAP-WUG at MITVMA.MIT.EDU>
> > > Sent: Monday, March 22, 2004 3:14 AM
> > > Subject: Re: Transporting Org Management Data from Dev to QA
> > >
> > > > Hi Swami,
> > > >
> > > > Can you tell me how you assign agents to steps when you maintain the
> > > organization structure directly on
> > > > production? F.i. the positions cannot be assigned to the steps on
> > > development (when modelling the workflow),
> > > > because they are maintained on production.
> > > >
> > > > Regards,
> > > >
> > > > Fred Kouw
> > > >
> > > > Hotmail wrote:
> > > >
> > > > > Hello Brad,
> > > > >
> > > > > If it is a simple org structure can you not maintain it directly in
> >PRD
> > > ? We
> > > > > did maintain the org structure for workflows
> > > > > using PPOMW before we switched over to SAP HR. One other option
> >could be
> > > > > using ALE to transport Org structure if source and target systems
> >are
> > > > > mainatined in ALE Distribution.
> > > > > One other I would check is if the holder ( USERID - If you are
> > > transporting
> > > > > the user id's too) is existing in the client where you are able to
> >see
> > > the
> > > > > org structure but not holders.
> > > > > Swami Bala
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Tisch, Brad" <brad.tisch at teldta.com>
> > > > > To: <SAP-WUG at MITVMA.MIT.EDU>
> > > > > Sent: Friday, March 19, 2004 6:43 AM
> > > > > Subject: Re: Transporting Org Management Data from Dev to QA
> > > > >
> > > > > Hi Werner,
> > > > >
> > > > > I used the manual transport option. I did get the data over to the
> >test
> > > > > system, but wasn't able to display or change it. I finally ended up
> > > > > transporting some structural authorizations that existed in
> >Development
> > > but
> > > > > not in test. I can know view the org structure, but cannot assign
> > > different
> > > > > holders to various positions. Any thoughts? I want to be able to
> > > maintain
> > > > > the org structure in production - at least the holders of positions.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Daucher Werner [mailto:Werner.Daucher at hrforce.at]
> > > > > Sent: Friday, March 19, 2004 3:29 AM
> > > > > To: SAP-WUG at MITVMA.MIT.EDU
> > > > > Subject: AW: Transporting Org Management Data from Dev to QA
> > > > >
> > > > > Hi Bradley,
> > > > >
> > > > > do you use RHMOVE30 ?
> > > > > if yes, which evaluation path do you use ?
> > > > >
> > > > > it is also possible that you have to wait some time, because of
> > > buffering.
> > > > >
> > > > > Werner
> > > > >
> > > > > -----Urspr|ngliche Nachricht-----
> > > > > Von: Tisch, Bradley [mailto:Bradley.Tisch at kraft.com]
> > > > > Gesendet: Donnerstag, 18. Mdrz 2004 22:18
> > > > > An: SAP-WUG at MITVMA.MIT.EDU
> > > > > Betreff: Transporting Org Management Data from Dev to QA
> > > > >
> > > > > Hi,
> > > > >
> > > > > I'm working with a client who is not currently using any form of org
> > > > > management. However they want to start using workflow and we decided
> >to
> > > > > create a simple org chart using the expert mode simple maintenance
> >of
> > > org
> > > > > management. All works fine in Development, however I'm having issues
> > > view
> > > > > the org chart in our QA system after transporting the org data.
> >There
> > > was no
> > > > > errors in the transport and I can see the data in the underlying
> >table,
> > > but
> > > > > I cannot access via the org management transactions. Help Please!!!!
> > > > >
> > > > >
> > >
> >____________________________________________________________________________
> > > _____________
> > > > > This inbound message from KPN has been checked for all known viruses
> >by
> > > KPN IV-Scan, powered by MessageLabs.
> > > > > For further information visit: http://www.veiliginternet.nl
> > > > >
> > >
> >____________________________________________________________________________
> > > _________________
> > > >
> > > >
> > > > **********************************************************************
> > > > This e-mail and any attachment may contain confidential and privileged
> > > > material intended for the addressee only. If you are not the
> >addressee,
> > > you
> > > > are notified that no part of the e-mail or any attachment may be
> > > disclosed,
> > > > copied or distributed, and that any other action related to this
> >e-mail or
> > > > attachment is strictly prohibited, and may be unlawful. If you have
> > > received
> > > > this e-mail by error, please notify the sender immediately by return
> > > e-mail,
> > > > and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM),
> >its
> > > > subsidiaries and/or its employees shall not be liable for the
> >incorrect or
> > > > incomplete transmission of this e-mail or any attachments, nor
> >responsible
> > > > for any delay in receipt.
> > > > **********************************************************************
> > > >
> > > >
> > >
> >____________________________________________________________________________
> > > _________________
> > > > This outbound message from KPN has been checked for all known viruses
> >by
> > > KPN IV-Scan, powered by MessageLabs.
> > > > For further information visit: http://www.veiliginternet.nl
> > > >
> > >
> >____________________________________________________________________________
> > > _________________
> > > > Please visit http://www.klm-em.com for information about KLM
> >Engineering &
> > > Maintenance products and services.
> > > >
> > >
> > >
> >_________________________________________________________________________________________
> > > This inbound message from KPN has been checked for all known viruses by
> >KPN IV-Scan, powered by MessageLabs.
> > > For further information visit: http://www.veiliginternet.nl
> > >
> >_____________________________________________________________________________________________
> >
> >
> >**********************************************************************
> >This e-mail and any attachment may contain confidential and privileged
> >material intended for the addressee only. If you are not the addressee, you
> >are notified that no part of the e-mail or any attachment may be disclosed,
> >copied or distributed, and that any other action related to this e-mail or
> >attachment is strictly prohibited, and may be unlawful. If you have
> >received
> >this e-mail by error, please notify the sender immediately by return
> >e-mail,
> >and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
> >subsidiaries and/or its employees shall not be liable for the incorrect or
> >incomplete transmission of this e-mail or any attachments, nor responsible
> >for any delay in receipt.
> >**********************************************************************
> >
> >_____________________________________________________________________________________________
> >This outbound message from KPN has been checked for all known viruses by
> >KPN IV-Scan, powered by MessageLabs.
> >For further information visit: http://www.veiliginternet.nl
> >_____________________________________________________________________________________________
> >Please visit http://www.klm-em.com for information about KLM Engineering &
> >Maintenance products and services.
>
> _________________________________________________________________
> MSN Toolbar provides one-click access to Hotmail from any Web page   FREE
> download! http://toolbar.msn.com/go/onm00200413ave/direct/01/
>
> _________________________________________________________________________________________
> This inbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl
> _____________________________________________________________________________________________

**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee, you
are notified that no part of the e-mail or any attachment may be disclosed,
copied or distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have received
this e-mail by error, please notify the sender immediately by return e-mail,
and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its
subsidiaries and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor responsible
for any delay in receipt.
**********************************************************************

_____________________________________________________________________________________________
This outbound message from KPN has been checked for all known viruses by KPN IV-Scan, powered by MessageLabs.
For further information visit: http://www.veiliginternet.nl
_____________________________________________________________________________________________
Please visit http://www.klm-em.com for information about KLM Engineering & Maintenance products and services.