SWEHR1/2/3 - Adding REQUESTED event to PERSDATA on ESS Name Change

Fri May 7 09:53:50 EDT 2010

Rick,

Here's how HR Symmetrical Double Verification works.

It's all based on authorizations using authorization object P_ORGIN
and/or P_PERNR.

If you're doing this through ESS, the employee will need access to their
infotype 0006 but NOT full Write access only Enqueue access as follows:

If you're allowing this in R/3 using transaction PA30, it would be
similar but it would be authorization object P_ORGIN instead.  The
manager (or HRAdvisor) would need D for Dequeue or W for Write.

When an employee changes their address it locks the record and can be
seen in PA20/PA30 as a padlock.

The padlock icon goes away when the Manager and/or HR advisor unlocks
it.

In SWEHR3 it would look like this.

You would then simply create a workflow that is triggered by the event
ADDRESSEMP.REQUESTED to allow an HR Advisor or Manager to approve.

This can be used in Payroll for IT0008 where you have a "junior" data
entry person (with Enqueue authorization only) changes salaries. The
"old" salary continues until a payroll supervisor unlocks (or dequeues)
the new record.

Hope that helps.

Claude
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sample, Rick
Sent: May 06, 2010 11:09 AM
To: SAP Workflow Users' Group
Subject: RE: SWEHR1/2/3 - Adding REQUESTED event to PERSDATA on ESS Name
Change

Hi Sathish,

I added to SWEHR1 and appears to work. 

Locks?
Are you referring to "SAP HR Symmetrical Double Verification"? 
http://help.sap.com/saphelp_47x200/helpdata/en/ab/4bba3b3bf00152e1000000
0a114084/frameset.htm
If you are using this (and it actually works) I would really be
interested in knowing how it is "supposed" to work.
Because we tried, but got nowhere! So, we ditched that idea and added
simple ABAP code to lock.

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sathish Venkatesan
Sent: Wednesday, May 05, 2010 5:15 PM
To: SAP Workflow Users' Group
Subject: Re: SWEHR1/2/3 - Adding REQUESTED event to PERSDATA on ESS Name
Change

Rick

I would say add a new record for PERSDATA and leave the other one there.
We have similar HR workflows in our syatem and I always added new
entries. No issues so far after 2 major upgrades.

Just a thought - Instead of using BADI\Exit to lock the record, you can
control it through ESS role authorization value such that when they
change that particular infotype, it will always create a locked record.
I think the value is 'S' and "D' for creation and deletion of locked
record.

Regards,
Sathish

On Wed, May 5, 2010 at 4:14 PM, Sample, Rick <Rick.Sample at graybar.com>
wrote:
Good day wuggers!

Quick question / chat to confirm what I am doing won't cause issues.
And, 
by all means, if someone has a better idea, please feel free to throw
rocks. 

We currently allow our employees to change their name via ESS without
checks. 
This currently works fine. We also have a simple send msgs wf to inform
Security, LAN, etc. 
All this is on PERSDATA object, events, etc. 

Now, we want to lock any change and route to HR folks to verify. 
Social Security Admin (Big Brother) recommends using old name until
changed name is verified. Fine!

We now lock the record when user creates a change via ESS. 
Changes in a BADI and User EXIT. Setting field sprps = 'X'.

On change, I got a locked record but then the CHANGED event did not
trigger. After some head scratching, I figured out that I need to add
REQUESTED event. So, I added REQUESTED event to my zPERSDATA. When I
went to add the event ( as REQ type) to SWEHR3 (customer changes), it
would not allow me. Complaining about no entry in SWEHR1's table. 

<questions>
In SWEHR1, I see an entry for PERSDATINT. I assume this stands for
International? 
We don't use PERSDATINT as far as I can see. We have been using PERSDATA
(and zPERSDATA) since inception, so I would rather not change it unless
I must. 

So, do I ADD a new record for PERSDATA and leave PERSDATINT in this
table? 
- or -
Add PERSDATA and delete PERSDATINT? 

Thanks much,

Rick Sample | Workflow Analyst/Developer
11885 Lackland Road | Maryland Heights, MO 63146 | Office (314) 573-5822
| Mobile (314) 952-2273 | rick.sample at graybar.com 
www.graybar.com <http://www.graybar.com/>  - Works to Your Advantage 

  <http://www.graybar.com/> 

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

====================================================================================

La version française suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential information, and the Bank of
Canada does not waive any related rights. Any distribution, use, or copying of this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately from
your system and notify the sender promptly by email that you have done so. 

------------------------------------------------------------------------------------

Le présent courriel peut contenir de l'information privilégiée ou confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre
ordinateur toute copie du courriel reçu.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100507/3e2140f8/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/bmp
Size: 120474 bytes
Desc: Outlook.bmp
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100507/3e2140f8/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1548 bytes
Desc: image001.gif
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100507/3e2140f8/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/bmp
Size: 387926 bytes
Desc: Outlook.bmp
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100507/3e2140f8/attachment-0001.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/bmp
Size: 184950 bytes
Desc: Outlook.bmp
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100507/3e2140f8/attachment-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/bmp
Size: 73482 bytes
Desc: Outlook.bmp
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100507/3e2140f8/attachment-0003.bin