Concurrent Employment in SRM 5

[Dave Weston]

Hi Jerry,

We had only one user id that could be switched between different
personnel numbers.

We created a new workflow rule based on a copy of the      
function module SWX_GET_MANAGER so that the rule finds the CP (VARYF)   
relationship in table HRP1001 for the employee and then finds all       
the associated relationships again in table HRP1001 where field OTJID   
matches the CP entry. If any of these entries have a 0105 subtype 0001  
user id assigned then we have found our agent.   

Hope this helps. I'd send u the code but I don't have access to that
system anymore.

Cheers
Dave
                        

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of jerry martinek
Sent: Tuesday, January 17, 2006 2:15 PM
To: SAP Workflow Users' Group
Subject: Re: RE: Concurrent Employment in SRM 5

Hi Dave,

Thanks for the reply. I've searched the help documentation on this
subject and haven't been able to find much. At the momment I'm waiting
for the HR group responsible for this functionality in the ERP system to
return from training.

Can you please expand on the multiple 105 relationships? Does the person
actually have mutliple logon ids (st 0001), one per each position? 

I will also have to perform similar things in the ERP system that you
had to do in your system so I was wonderring if you could provide some
additional information on how or what you did with respect to rule 168
and 157?

Regards,
Jerry  

----- Original Message -----
From: Dave Weston <Dave.Weston at clockwork.ca>
Date: Tuesday, January 17, 2006 10:41 am
Subject: RE: Concurrent Employment in SRM 5

> Hi folks,
> 
> I have had experience with concurrent employment in a 4.7 enterprise 
> system but only from the viewpoint of the workflow rules 168 and
> 157 not
> supporting the 105 relationship between the multiple person id's. 
> We had
> to create our own version of the SWX_GET_MANAGER function to find the 
> right person from the 105 infotype relationship. We created an OSS 
> message for this problem but worked around the issue.
> 
> But no experience in replicating org units with concurrent employment 
> I am afraid.
> 
> Cheers
> Dave
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [sap-wug-bounces at mit.edu] On Behalf Of 
> jerry martinek
> Sent: Tuesday, January 17, 2006 12:00 PM
> To: sap-wug at mit.edu
> Subject: Concurrent Employment in SRM 5
> 
> Hi,
> 
> Has anyone had the opportunity to implement shopping cart approvals in

> an SRM 5 system that is tied to an ERP 2005 system that supports 
> concurrent employment? If yes how did you implement it with respect to

> shopping cart approvals? If no but have some insight or know of some 
> useful documentation, would you be willing to share your information?
> 
> I'm working in a new ERP 2005 and SRM 5 implementation where we need 
> to implement approvals based of the org unit where the shopper could 
> be shopping for any one of their other assigned positions. We haven't 
> beenable to find any useful information on this subject so I'm 
> wondering if anyone has any experience or suggestions as to how to 
> proceed with implementing his requirement in SRM.
> 
> Concurrent employment is when a person can be actively assigned to 
> multiple positions but they only have the one user/logon id. I believe

> that our SAP consultant tried replicating  an org unit that included 
> concurrent employment from the ERP system but only the single position

> was replicated to the SRM system.
> 
> Regards,
> Jerry
> 
> 
> _______________________________________________
> 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