This is the first time I am sharing my knowledge in SCN. I hope my document would be helpful.

Our client had a requirement that sensitive data cannot be a part of search criteria in HR transactions such as PA20/30, PPPM/D, PPOSE/ PPOME etc.

For our client, date of birth of employee is considered sensitive and they have requested us to remove/ hide date of birth and Start date when we are searching through Person. Employee’s Start date is pulled from IT0002 – Start date which is also the date of birth of an employee in the transaction code PPOME/ PPOSE.

For Ex: When we are searching for an employee through PPOSE/ PPOME by using PERSON Node, Valid From is retrieved from Person’s Date of Birth

/wp-content/uploads/2014/03/pic1_413985.png

Collective Search : PREMK

/wp-content/uploads/2014/03/pic2_413986.jpg

Though it is maintained in PREMK that begda and Endda information is retrieved from PA0001, but at the back end for collective search function module / program , the information is retrieved from PA0002.

/wp-content/uploads/2014/03/pic3_413996.jpg

Since this is SAP Standard program, we have come up with alternate solution by manipulating the display with config if required. We have raised it with SAP

We are using the column group NF_STP and that one includes the column ORG_BEGDA and ORG_ENDDA. To fill those columns we are using the generic function module OM_FILL_STANDARD_COLUMNS. The dates displayed for ‘validity’ are birthdate and high-date of IT0002.

We can’t change the way ORG_BEGDA and ORG_ENDDA are filled; you may create your own column group and attach that to the relevant search tool which is CL_HR_SEARCHTOOL_PREM in scenario OMEO00.”

We looked up the column group that is used to display the hitlist:

/wp-content/uploads/2014/03/pic4_413998.png

Then for this scenario we decided not to use the Valid from any more. So we removed it in config

SPRO > Personnel Management > Organizational Management > Hierarchy Framework > Column Framework

/wp-content/uploads/2014/03/pic25_414130.png

Searched for Column Group NF_STP and hidden the column ORG_BEGDA.

/wp-content/uploads/2014/03/pic5_413999.jpg

And it is no longer available

/wp-content/uploads/2014/03/pic6_414000.jpg

This will be applicable to PPOME, PPOCE and PPOSE.

The collective search help and the search term does not display the birth date as per the request but if you run a free search the value is displayed if the user select the field as part of the output.  See below;

/wp-content/uploads/2014/03/pic7_414011.jpg

/wp-content/uploads/2014/03/pic8_414120.jpg

To identify the Object manager in the search area of the HR transaction, set/get parameter OM_OBJM_SCEN_DISPLAY is set, you can see in the search areas which object manager scenario is active in an instance of the object manager.

SU01 for the User profile

/wp-content/uploads/2014/03/pic9_414121.png

Object Scenario: for Transaction code PPPM / PPPD

/wp-content/uploads/2014/03/pic10_414161.png

Object Scenario: for Transaction code PA20/PA30

/wp-content/uploads/2014/03/pic12_414163.png

     

Object Scenario: for Transaction code PPOME/PPOCE/PPOSE

/wp-content/uploads/2014/03/pic11_414162.png

As shown above, the object manager for PPOSE/ PPOSE/PPOCE is OMEOO0

SPRO > Personnel Management > Organizational Management > Hierarchy Framework > Object Manager

/wp-content/uploads/2014/03/pic26_414167.png

The search scenario for OME000

/wp-content/uploads/2014/03/pic13_414168.png

Search Node Key

/wp-content/uploads/2014/03/pic14_414169.png

P – Person

C- Job

O- Organisation Unit

US – User

S- Position

T – Task

For each Search Node Key, we have different search tool such as

/wp-content/uploads/2014/03/pic15_414174.pngbased on Position numbering.

/wp-content/uploads/2014/03/pic16_414175.png

The Free search node position 4 calls the Class CL_HR_ST_ADHOC_SELECTION

/wp-content/uploads/2014/03/pic17_414176.png

The search tool Class CL_HR_ST_ADHOC_SELECTION calls the table : T77OMAHQ_FUNCARS which gives mapping to ADHOC QUERIES.

/wp-content/uploads/2014/03/pic18_414177.png

SQ02

/wp-content/uploads/2014/03/pic19_414178.png

/wp-content/uploads/2014/03/pic20_414179.png

Proposed Solution

  1. We have copied the existing infoset /SAPQUERY/HR_XX_OM_P to ZHR_XX_OM_P under Global Area.
  2. Deleted the DATE OF BIRTH related fields from the custom Infoset ZHR_XX_OM_P. Generated the infoset
    1. /wp-content/uploads/2014/03/pic21_414180.jpg
    2. Fields  that are removed from Infoset are

               /wp-content/uploads/2014/03/pic22_414181.jpg

          3. Maintained the table T77OMAHQ_FUNCAR with the enteries

          /wp-content/uploads/2014/03/pic23_414182.jpg

  1. Tested PPOSE

/wp-content/uploads/2014/03/pic24_414183.jpg

Fields related to Date of Birth did not get dispalyed.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply