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

Sathish Venkatesan sathish at smartsoftus.com
Wed May 5 18:15:12 EDT 2010


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 - *Works to Your Advantage*
>
> [image: Graybar® 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100505/a4a80537/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1548 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100505/a4a80537/attachment.gif


More information about the SAP-WUG mailing list