SRM 5.0 and my Concurrent Employment Issues

[Dave Weston]

In a 4.7 Enterprise R/3 system last year, I worked at a client with
concurrent employment. I found problems with the 157 and 168 rules. The
function SWX_GET_MANAGER didn't read the HRP1001 table correctly. So I
had to create my own version of this FM. Think I posted the answer last
year to the group.
 
I put in an OSS message but all SAP said was that they would investigate
for a future release as I had my work around Z function in a rule.
 
Cheers
Dave 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Adao-Cruz, Miguel
Sent: Tuesday, May 16, 2006 4:15 AM
To: SAP Workflow Users' Group
Subject: RE: SRM 5.0 and my Concurrent Employment Issues


Hello,
 
Try debugging function SWX_GET_MANAGER and see which links in HRP1001 it
is following to find the manager.
In a past project, debugging this function, I realised that the workflow
was not finding the correct manager (sometimes a manager miles from the
user branch!) because of inconsistencies in the HR tables.
 
Cheers
 
________________________________________________________________________
___
Miguel Adao-Cruz | Capgemini | London
Technology Services
SAP Application Architect

T.+44-870-238-2927 | Int.700 2927 | www.capgemini.com
<file:///C:\Documents%20and%20Settings\madaocru\Application%20Data\Micro
soft\Signatures\www.capgemini.com,DanaInfo=OWA.UKI.CAPGEMINI.COM+> 

Join the Collaborative Business Experience
________________________________________________________________________
___

________________________________

From: sap-wug-bounces at mit.edu on behalf of jerry martinek
Sent: Mon 15/05/2006 18:23
To: sap-wug at mit.edu
Subject: SRM 5.0 and my Concurrent Employment Issues



Hi All,

 

I need some help understanding how the current concurrent employment
(CE) implemented in SRM is supposed to work or help me explaining to OSS
that the CE SRM implementation is not correct for workflow approvals.

 

We're a NW2004S / SRM5.0 ramp up site. We're also unfortunately
implementing concurrent employment which seems to be the source of a lot
of my challenges. 

 

In a CE scenario, a single person can concurrently hold multiple
employment contracts. For each contract they will have a distinct P, S
and US (logon id).

 

This means that they will have multiple Ps, one per contract. Each P
will be assigned to a single S. Each P will also have one distinct US
(PA0105-0001). The different Ps will be grouped by a person id (CP).

 

Example:

In the ERP HRP1001 table, P1 and P2 are linked/joined by a CP1. US1 is
linked to P1 and US2 is linked to P2. P1 is assigned to S1 and P2 is
assigned to S2. S1 is linked to O1 and S2 is linked to O2.

 

The same scenario replicated into the SRM HRP1001 table, a new CP1 is
created from P1. P2 is not replicated into SRM. All references to P2 are
replaced by CP1. Only one BP is created for the CP1. CP1 is linked to
both S1 and S2. US1 and US2 are both linked to CP1. S1 is linked to O1
and S2 is linked to O2.

 

In PPOSA_BBP, the display shows both ids assigned to each position, and
the same CP and BP are also assigned to the different positions.

 

When I logon in with any of the two USs in ERP, I get the correct
superior of results. When I logon in with any of the two USs in SRM, I
always get the same result which is not correct.

 

In the current SRM CE implementation, I don't see how you can figure out
the correct position assignment in order to figure out your correct
approver.

 

There are other issues as well but this one is my most pressing one.
Another example of an issue is in the area of authorizations. 

 

What am I missing? OSS keeps telling me that there are no problems.

 

Regards,

Jerry Martinek

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060516/f8a9e3d4/attachment.htm