When a new employee is hired, the system automatically creates the external person ID and

stores it in the Person ID infotype (0709). If another personnel assignment is created, the person
ID is transferred by the copy mechanism for infotypes.
You can store the generation rule for creating the external person ID in Customizing. For more
information, see the Implementation Guide (IMG) under Personnel Administration ® Customizing
Procedures  Settings for Concurrent Employment  Personnel Administration (Concurrent
Employment)  Activation of External Person ID.
So all infotypes which should be copied must have the copy flag set in table V_T582A. If they
have set or will set CCURE PC_UI to X then T582G is the relevant grouping table. Customer can
find more infor-
mation in note no. 1447867. There is also mentioned a correction in
note no. 570146 how the correct settings for IT0709 in V_T582G must be.
About the wrong PERNRS,
For the already existing records, you can execute the report RPUFIXDS.
This report will fix the inconsistencies for the infotype 0709 (you can filter on infotype level in the
selection-screen). Please read carefully the report's documentation:
infotype records can be deleted as infotype records are copied from a main pernr to other pernrs.
Therefore if the main pernr doesn't have any record, the records will be deleted for the other
pernrs too. This
is described in the report's documentation.
1538862  Create Reference Personnel Number: ENAME is not updated.

I have activated CE and turn on all the necessary switches and now it's time to generate IT0709
on all employees. For that, I use report HR_CE_GENERATE_PERSONID_EXT.

If I have an employee who go two assignments with two different employee number only the first
number will be generated and the second one will have an error message says: Personid_Ext
identical with employee number xxxxxx.
Why can't I generate IT0709 for the second employee number?

Check the following swithces in V_T77S0 table

CCURE PIDGN Generation Rule RESONID
CCURE PIDSL Selection with PERSONID

Person ID (IT0709)
 
You can add this infotype to the action menu in the Master Data Application
and it can also be used for processes in the FPM and roadmap forms.
If you want to use this infotype in processes, please see the Customizing
Activity   Personnel Management   Personnel & Organization   
Processes   Design Time for Processes and Forms  .
If you want to use this infotype in an action menu, please see the
Customizing Activity   Personnel Management   Personnel &
Organization   Role   Configure Launchpad for Actions  .
The Person ID infotype (IT0709) stores the data on an employee in
concurrent employment. Employees in concurrent employment are persons
who have more than one personnel assignment with one enterprise or
several affiliated enterprises.
An employee in concurrent employment is mapped by assigning multiple
personnel assignments to a central person (object CP). The system
determines the central person automatically through internal number
assignment. In addition, a unique external person ID is also determined.
The external person ID cannot change over time (time constraint A).
 
When a new employee is hired, the external person ID is created in the
system automatically and is stored in the Person ID infotype (0709). When
you enter an additional personnel assignment, the external person ID is
transferred using the copy mechanism for infotypes.
You can define the generation rule for creating the external person ID in
Customizing. For more detailed information on this, see Customizing and
choose   Personnel Administration   Customizing Procedures   Settings for
Concurrent Employment  Personnel Administration (Concurrent
Employment)   Activation of External Person ID  .
 Note
When you want to activate the external person ID in your system for the
first time, use report HR_CE_GENERATE_PERSONID_EXT to generate
the Person ID infotype (0709) for all of your employees.
SAP V_T588MFPROPS View fields within data Dictionary

Dat
length
a Check Descripti Conversio
Field Data Element (Decimal
Typ table on n Routine
s)
e
CHA
INFTY INFTY 4 T582A Infotype
R
ITVERS ITVERS CHA 2 T582ITVE ID for
R RS Infotype
 Versions
CHA
SUBTY SUBTY 4 Subtype
R
Name of
CHA
SNAME TYPENAME 30 Dictionary
R
Type
CHA
FNAME FIELDNAME 30 Field Name
R
HR:
MANDATO HRPAD_MANDATO CHA
1 Required
RY RY R
Entry Field
HR:
HRPAD_READONL CHA
READONLY 1 Output
Y R
Field
CHA HR: Not in
UNUSED HRPAD_UNUSED 1
R Use
CHA
FIXED HRPAD_FIXED 1 HR: Fixed
R

Check in V_T588MFPROPS table (for the original country-grouping for the app + 0185 subtype +
P0185 structure) the list of fields (and its config).
Copy this information to V_T588MFPROPC table (this is your custom table), by replacing
country-grouping for your country-grouping of application.

40 P0185 AUTH1
40 P0185 DOCN1
40 P0185 EXPID
40 P0185 FPDAT
40 P0185 ICCOL
40 P0185 ICOLD
40 P0185 ICTYP
40 P0185 IDCOT
40 P0185 ISCOT
40 P0185 ISSPL
40 P0185 OVCHK
& in table V_T588MFPROPC for infotype 185 there are no entries .
Please check if entries in the these tables are same as you have.

You will need to use PCL4 table to fetch the deleted records.
INCLUDE: rpc4sa00.
SELECT srtfd aedtm uname
FROM pcl4
INTO CORRESPONDING FIELDS OF TABLE it_pcl4
WHERE relid = 'SA'
AND aedtm IN s_period[]
AND srtfd IN r_srtfd[].
Here SA means Short Term documents, s_period[] will be the range in which you are looking for
data and r_srtfd is the PCL cluster key(here u may define it as a range). The key will be in the
form "A2001" if you are looking for deletions in IT-2001, "A2002" for IT-2002 etc.
After this, you can use this table to fetch data from cluster as:
LOOP AT it_pcl4 INTO wa_pcl4.
MOVE wa_pcl4-srtfd TO sh-key.
IMPORT header belege FROM DATABASE pcl4(sa) ID sh-key.
LOOP AT header WHERE opera EQ 'D'.
"Your Manipulations here
ENDLOOP.
ENDLOOP.
Opera indicates the operation (D=Deletion, I=Insertion, U=Updation)
Here, Header will contain begin and end date of the deleted record among other details. Also,
pcl4 table will itself contain the username of person who deleted the record.
Belege will contain the old and new data in the record.
You can use the report RPUAUD00 for more information. On using "Direct Output of Docs"
option, you will be able to see detail list, which will help you in your report development. Press F1
on any of the fields to know, whether it belongs to pcl4, header or belege. The documentation of
this report is also quite helpful.

Please let me know the t-code or procedure to see the data in PCL4 cluster.

you can use Report RPUP4D00 to display(and delete) records from PCL4 Cluster.

SAP HR ABAP programs

H99CWTR0 
Wage Type Reporter. Returns pay for particular wage types. To submit from new
report you will need to create copy and export value to memory. 

RHGRENZ0 
Delimit IT1000 and related 1001s. Program will delete any 1001 infotypes whose
start date is after the delimit date. 

RHGRENZ1 
Extend the end date on delimited records. Very useful when you delimit a bunch of
records incorrectly, and need to change the end date. 

RHGRENZ2 
Delimit infotypes (IT1001) 

RPCMPYG0 
Statutory Maternity Pay(SMP) 

RPCSSPG0_HIST 
Statutory Sickness History(SSP) 

RPDTRA00 
List all HR transactions and there uses 

RPTPSH10 
Personal work schedule, also accessed via PA20/PA30 infotype 2001 

RPUAUD00 
HR Report to list all logged changes in infotype data for an employee. Uses the PCL4
Audit Cluster. 

RPUAUDDL 
HR Report to delete audit data from the PCL4 Audit Cluster 

RPUDELPN 
Delete all info for an employee number, including cluster data and infotypes 

RPUP1D00 
View/Delete records from PCL1 Cluster 

RPUP2D00 
View/Delete records from PCL2 Cluster 

RPUP3D00 
View/Delete records from PCL3 Cluster 

RPUP4D00 
View/Delete records from PCL4 Cluster