Global Employee Number

Hi All,
Where can we mantain the gloabl emoplyee number if its in 4.6c or other version also.
ASAP help woule be apprecaited
Thanks and Regards

Hi,
These are the switches.
CCURE     ADDCO          Further Pers.Assignmnt or Processing of Info Group
CCURE     CPAUT
CCURE     GEMAN     PERSCM2     MGE: Evaluation Path for Manager of Organization
CCURE     GLEMP     X     Management of Global Employees
CCURE     GLOPY     X     Payroll: Global Employee
CCURE     MAINS     X     Concurrent Employment Main Switch
CCURE     MPSDS          Start Date for Wage Type Generation
CCURE     PAUIX          CE Master Data User Interface Enhancements
CCURE     PAY99     X     Country Grouping 99: Start Date CE Payroll
CCURE     PAYCA          Canada: Start Date CE Payroll
CCURE     PAYSE
CCURE     PAYUS          USA: Start Date CE Payroll
CCURE     PC_UI          PC UI Main Switch
CCURE     PIDGN          Generation Rule PERSONID
CCURE     PIDSL          Selection with PERSONID
CCURE     PYAAU
CCURE     SEARC          X=New Employee Search Screen
CCURE     TMEVL          Start Date for Time Evaluation
CCURE     WTGEN          Start Date for Wage Type Generation
Warm Regards,
Kapil Kaushal

Similar Messages

Reference Employee Number

I have a scenario where an employee working in country A is being transfered to country B within a global company. While in country B, the employee history from country A needs to be tracked. If I use Reference Employee Number functionality, will running a report with the employee number in country B include the histroy in country A?

Depends on the report, if it's standard only if it uses the PNPCE logical database will that possible.

Global Employee Programming

Hi,
Which LDB should be used for global employment PNP or PNPCE. Does anyone has examples of using PNPCE. i am fully aware of using PNP but not PNPCE keeping in ming global employees.
Concurrent employment is different from Global employment.
How do i handle PU12 interface for global employment ? We outsource payroll and export master data to the vendor.
Help will be approciated.
Amandeep.

Hi
The Difference is only with in an SAP R/3 system in which Concurrent Employment is active, reports are executed by the PNPCE logical database. The general logic of the PNPCE logical database corresponds to the PNP logical database. The PNPCE logical database can also process the concept of Concurrent Employment.
HR Logical Databases
In Human Resources (HR), the following logical databases can be used as a data source for HR InfoSets:
PNP (PNPCE)
PAP
PCH
By selecting a logical database, you determine the HR data that can be reported on using an InfoSet.
Logical Database PCH
This logical database generally enables you to report on all HR infotypes. However, you are advised not to use this logical database unless you want to report on Personnel Planning data.
Logical Database PNP (or PNPCE)
Use logical database PNP to report on HR master data. It is possible to use logical database PCH to access this data, but PNP meets such reporting requirements more quickly because it is best suited to the task of selecting persons.
Logical database PNP enables you to access HR master data and infotypes from Personnel Planning. For example, you have the following options:
Reporting on the costs, number of attendees booked, and instructor for a business event on which an employee is booked
Reporting on working time and planned compensation for a position that an employee occupies
Reporting on the validity and proficiency of a qualification that an employee fulfils
From a technical perspective, this means you can use PNP to report on all of the infotypes that exist for objects (infotype 1000) that have a direct relationship (infotype 1001) with the Person object.
The ability to access infotypes from Personnel Planning using logical database PNP is a special feature that you can only use in the context of SAP Query and Ad Hoc Query. You cannot use this functionality for ABAP reports you programmed yourself.
You can also use logical database PNP to report on data from Personnel Time Management (infotypes 2000 to 2999) and Payroll (special payroll infotypes for the USA and customer infotypes; for more information, access Customizing for the Human Resources Information System and see Payroll Results).
Logical Database PAP
Logical database PAP enables you to access data from Recruitment.
The PNP and PNPCE are basically the same, with the exception of the concurrent employment / global employment concept.
If you activate the Management Global Employee functionality or the Concurrent Employment functionality, you have introduced a new ID concept called PERSON ID. This allow a person to have more than one PERNR (personnel number) and linked together through PERSON ID. Which is created, stored, and track via infotype 0709.
PNPCE has one extra field in there for PERSON ID and allow you to write code to query upon it.
Manoj Shakya

HCM Process and Forms & Global employee management

Hi all,
I would to know if anyone of you experience in implementing HCM Process and forms for Global employee management(GEM).
I would like to know the difficulties or challeges .
How the forms will work.
Means if i have created a form using Personnel number without GEM.
Later if i Implement GEM.do i have to Change the form ?
Does P&F has any option choose the employee based on personnel id anywhere or we have to use personnel number and process as existing.
what could be stuctures for each infotype which are country specific .
Please share your experience on this.
Regards,
Nachy

Forms and processes are enabled for CE/GE.
what process you would lile to do ?
refer HR_PA_US_ADDL_CONTRACT sample process and note 1366872
1) The central person id of the existing (reference) pernr should be
   read with the help of a generic service and this should be made
   available for the SAP_PA service so that a new central person is not
   created. This should be set in the field CENTRAL_PERSON in the
   form scenario.
2) An explicit operation on IT0709 should not be defined in the
   infotypes and operations of the design time tool. This is
   automatically handled by the infotype framework through the data
   sharing mechanism (table T582G). Kindly ensure that IT0709 is
   enabled for data sharing and please remove it from the process.
3) The reference pernr data and the shared infotypes must be read with
   the generic service only (refer to note 1366782), these should not
   be read with the SAP_PA service as this may lead to a clash in the
   record keys and can lead to undesired results.

Employment of Global Employees / Concurrent Employment Model

Hello all,
We are working with SAP R/3 4.6C and our organization has global employees. For example: an employee is on the payroll for country 'X' but is working in country 'Y'.
I know the solutions to these employees are in the 'Management of Global Employees' (MGE) but this functionality is only available as of SAP R/3 Enterprise - HR extension 1.1.
We are wondering what the solution is for MGE within 4.6C? What are the possibilities within SAP or perhaps other topics I can look for to solve this problem?
Kind regards,
Michael

Hi,
regarding your current release, the functionalities around infotype 0031 could be suitable for you.
The Reference Personnel Number (0031) infotype is used to assign several personnel numbers to one employee, if the employee has different employment relationships in your company. In this case, the personnel number associated with the employee is known as a reference personnel number. This infotype establishes links between all of an employees reference personnel numbers.
Regards
Michael

Org Assignment of global employees in Compensation Management

I have a problem with Compensation Management but it also relates the Org Assignment of global employees
In Comp when I try to submit an employee using transaction HRCMP001, I have an error saying no org assignment exist on 01. 01 .2008.
The business scenario is as follows. EE is hired on 01012008 in UK for e.g. he gets terminated on 31.05.2008 and then gets re-hired in another country using the Global Employee Personnel actions on 01.06.2008. In this county, he becomes eligible to receive the increase but when I try to submit, the error comes up that no org assignment exist for 01.01.2008. I have changed the settings in T582A to u2018copy infotypeu2019, it tries to reference the previous org assign infotype from 01.01.2008(which is correct but the system rejects it and will only accept the new date of the new hire 01.06.2008) thereby not referencing the old org assignment in the new personnel number.? I tried the propose infotype option but it did not do anything. Does any one have any suggestions? Thanks ever so much for your anticipated help.

You create the compensation packages using info type 0706. This info type has
Two subtypes; one for home country and one for host country
Check this link
http://help.sap.com/erp2005_ehp_04/helpdata/EN/32/79c73c0c52085be10000000a114084/content.htm

Doubts in Management of global employees

Dear Experts,
im trying to configure Global employment in my system.
Here im having some doubts in the execution of Global employment.
the doubts are...1.Shall we need to configure seperate actions for the management of global employees and what are the specific infotypes for the actions.
2.How to activate the global employment in the system.
Kindly share your valuable advices.
Regards,
V Sai.

Hope it helps
Payroll for Global Employees This component is not released for all customers. For more information, read SAP note 518503.
You use this component to run payroll for your global employees.
Implementation Considerations:
To implement this component you must activate it in your system. Access Customizing for Payroll and choose Payroll International --> Payroll for Global Employees, and perform the IMG activity Activate Payroll for Global Employees. You make other settings for this component in the same section.
Integration:
You can implement Payroll for Global Employees irrespective of whether you administer your global employees with the component Management of Global Employees or in some other way in the system.
Features:
For Payroll for Global Employees payroll is usually run in two countries. There is data exchange between two payroll systems. Data is exchanged in the form of wage types.
u2022 The sending payroll creates the wage types and stores them in table RT_GP (Results Table: Payroll for Global Employees).
u2022 The receiving payroll imports the wage types from the sending payroll and processes them further.
Use function XGP (Payroll for Global Employees) to transfer wage types from the sending payroll to the receiving payroll and to process them within the receiving payroll.
All features that are included in the appropriate Payroll country version are available in sending and receiving payroll. For more information, see Payroll country versions in the SAP Library under Human Resources --> Payroll --> Payroll <Country>.
Constraints:
At present you can only transfer wage types from the sending to the receiving payroll. Data exchange in two directions is not possible.
Example
Employees in your German firm are usually seconded to your subsidiary company in the USA for three to five years. The remuneration of these global employees is calculated in the Payroll of the US company. Payment is also effected in the USA. However, the employee also pays social insurance contributions in Germany during his overseas assignment. These social insurance contributions are calculated in the German payroll system, and transferred to the American payroll system. They are settled there with the remuneration of the employee. In this case the German payroll is the sending payroll system, and the American payroll is the receiving payroll system.
Execute the relevant personnel action or choose Human Resources > Personnel Management > Administration > HR Master Data > Maintain.
2. If you have chosen to maintain the infotype manually, enter the global employeeu2019s personnel number and choose infotype Global Assignment Details (0710).
3. Click Create.
4. Enter the data with regard to the global assignment and check their consistency. Note that the system automatically determines the end date of the assignment on the basis of the duration you have entered.
5. Enter the applicable employment percentage in the host country.
6. Enter the current personnel number the global employee is assigned to in the host country. For more information on how to use these fields, see the F1 documentation.
7. Click Save.
Maintaining the Global Assignment Status
In this step, you maintain the current status of the global assignment according to HR processor.
Procedure
1. Execute the relevant personnel action or choose Human Resources > Personnel Management > Administration > HR Master Data > Maintain.
2. If you have chosen to maintain the infotype manually, enter the global employeeu2019s personnel number and choose infotype Global Assignment Status (0715).
3. Click Create.
4. Select the applicable assignment status.
5. Click Save.
Copied from the previous Threads

Management of Global Employees (MGE) query

Hello all,
We are implementing MGE (Management of Global Employees) functionality for Personnel Administration for a global company. I have activated all Global Employment (GE) switches in table T77S0 after consultation with SAP. We don't plan to implement Global Payroll, but only the concept of Person ID which will be unique even the employee is transferred from one country to other. I have set up Generation and Selection Rule for Person ID. I would like to know if Person Id can be used for Master Data maintenance and can it be used in Reports as a primary query criteria (instead of PERNR). Also want to know how to set up Personnel Actions related to country transfer within MGE.
I would like to know experiences from the real-time implementations. Anyone worked on Global Employment and Person ID implementation?
Thanks.

Hi,
1. How to do use PNPCE logical database for Std and custom reports? Do we need to activate LDB PNPCE?
If you have activated MGE, PNPCE gets activated with it. For custom reports, the developers need to include the LDB in their code. But it should be available in all standard reports and queries. Although, you will have to be careful if you are converting any custom reports as the u201Cget pernr/perasu201D statements differ. Iu2019m not technical but I saw some interesting threads on that topic here. You might want to check those.
2. The use of Person Id for master data maintenance (instead of PERNR), would it be a problem for other HR modules implementation in future e.g. Benefits.
I think for other modules, you should stick to personnel number.
3. Instead of using std. SAP MGE actions- 81, 82, 83, can I create custom personnel actions and custom infogroups (with std HR infotypes). The std MGE actions look complicated for the business users.
Yes, this is possible. You need to modify feature ACTCE accordingly for the following logical keys:
EXPATPLANNING=81
EXPATACTHOST=82
EXPATACTHOME=83
EXPATCHANGE=84
The logical keys come predefined. Simply equate them to the custom action types. You can read the documentation for this feature for more information.
4. Is it ok if I don't use the Infotypes related to MGE e.g. IT 706, 707, 710, 715 (except IT709 which gets created by the system) since we want to use the basic level of MGE and not implementing global payroll.
I believe you need IT0710 and IT0715 to track assignment details and statuses if it is in line with the client business process. You can ignore IT0706 and IT0707 as you are not implementing the payroll piece of MGE.
Hope this helps.
Donnie

Management of Global Employee w/out Concurrent Employment

Hi All,
Good evening. Can MGE be deployed w/out CE?
Please advise.
Kind Regards,
Daniel A. LA Mendola

Thank you Wilfred, I understand this is part of it and I appreciate your aid. I keep on getting this error message
Grouped data for personnel # (original PERNR) does not match personnel # (new PERNR).
Personnel number 91000074 and 01000035 are supposed to be grouped with the grouping value 10 for infotype 0002. However, the number of data records of the infotype is not the same for these personnel numbers.
It appears as if the infotypes are grouped in some fashion akin to how CE works- you can share data in a common infotype between assignments, or create new copies of infotypes.
I have executed the program rpufixds and this did not display the cause of the inconsistencies.
This is despite the fact that the new assignment copies IT0002 data from the originating assignment. Is there some cross-over in functionality between CE and MGE that could be causing this? I can't find any MGE configuration that address the configuration of grouping data. ( I'm assuming the grouping value of "10" that the detailed error report mentions has to do with the US=10.) That doesn't make sense to me either, because in the case of MGE, it is the norm that the new assignment would be a foreign country so there wouldn't be any common groupings of the infotypes under "10", if that refers to the US.
I have also reviewed and implemented a couple of the OSS notes that refer to Global Employees, but to no avail.
Kind Regards,
Daniel A. La Mendola

Skipping of Employee Number using Self Service Hire Process

Dear All,
We are using 11.5.10.2
We have enable Global Employee Numbering.
Employee Numbers are generated properly using Core HR.
But in Self Service Hire Process using Manager Self Service skips employee numbers.
Suppose last number is 12. Instead of generating 13, self service hire process generates 14.
Has anyone encounterd such issue?
Is there any solution to this issue?
Regards,
Ashish Shah

PTO accrual plans let you define all kind of rules via fast formulas.

Update Employee Number

Hi to All
I have a question regarding employee number updating. Situation is some thing like this:
I introduced a new employee in a system assigning him employee number e.g. *0001*. I haven't defined any assignment yet. Now after a week I required to change employee number from *0001* to *0100*. Is it possible if this employee number haven't referenced any forward.
Regards
Majid

You can change the employee number, never change the person_id. Apply the same logic that we use for Business group transfers or Global deployment.

How to Customize Employee Number Generation?

m trying to generate a custom employee,applicant numbers through a dummy business group.
I've created on Application: Oracle E-Business 11.5.10.2 the work structure and am now on the step of customizing the employee generating number.
I followed the link steps:
Below steps already done:
Technical Side:
1- Create New Sequence in DB.
-----Sequence Code----------
DROP SEQUENCE APPS.APPSLEAD_CUST_NUMB;
CREATE SEQUENCE APPS.APPSLEAD_CUST_NUMB
START WITH 1
MAXVALUE 999999999999999999999999999
MINVALUE 0
NOCYCLE
NOCACHE
NOORDER;
2- Create New Package for issuing the numbers.
----------Package Code--------------
Create or replace package appslead_package as
Function get_emp_custom_number (
p_business_group_id IN number
,p_legislation_code IN varchar2
,p_person_type IN varchar2
,p_person_number IN varchar2
,p_party_id IN number
,p_person_id IN number
,p_national_id IN varchar2
,p_date_of_birth IN date
) return varchar2;
end appslead_package;
Create or replace package body APPSLEAD_PACKAGE as
Function GET_EMP_CUSTOM_NUMBER (
p_business_group_id IN number
,p_legislation_code IN varchar2
,p_person_type IN varchar2
,p_person_number IN varchar2
,p_party_id IN number
,p_person_id IN number
,p_national_id IN varchar2
,p_date_of_birth IN date
) return varchar2 as
/*Check if the person id is exists on the system or not*/
cursor person_exists is
select employee_number,applicant_number,npw_number
from per_all_people_f
where party_id = p_party_id;
--and p_effective_date between effective_start_date and effective_end_date;
lseq_num number;
l_next varchar2(30);
l_emp_num varchar2(30);
l_apl_num varchar2(30);
l_npw_num varchar2(30);
begin
open person_exists;
fetch person_exists into l_emp_num,l_apl_num,l_npw_num;
if person_exists%notfound then
Select to_char(Appslead_Cust_Numb.Nextval) Into lseq_num From Dual;
l_next := 'AppsLead-'||lseq_num;
return l_next;
Else
If p_person_type = 'EMP' then
l_next := l_emp_num;
Elsif p_person_type = 'APL' then
l_next := l_apl_num;
Elsif p_person_type = 'CWK' then
l_next := l_apl_num;
End if;
End if;
Close person_exists;
return l_next;
end get_emp_custom_number;
End appslead_package;
Functional Side:
1- Create or Modify Business Group Employee numbering method to Manual.
2- Create New Formula Function.
3- Create New Formula EMP_NUMBER_GENERATION with Type "Person Number Generation"
------Formula Script--------
EMP_NUMBER_GENERATION
Create Custome formula for generation employee number*/
DEFAULT FOR Person_Number IS ' '
DEFAULT FOR Party_ID IS 0
DEFAULT FOR Person_ID IS 0
DEFAULT FOR National_ID IS ' '
DEFAULT FOR DATE_OF_BIRTH IS '1900/01/01 00:00:00' (date)
DEFAULT FOR Hire_Date IS '1900/01/01 00:00:00' (date)
INPUTS ARE
Legislation_Code (text),
Person_Type (text),
Person_number (text),
Party_id,
Person_id,
Date_of_birth (date),
Hire_date (date),
National_ID (text)
Next_Number = '0'
Invalid_msg = ' '
IF Person_Type = 'EMP' then
Next_Number = TO_CHAR(Get_Emp_Custom_Number(Legislation_Code,Person_Type,Person_Number,Party_Id,Person_Id,National_ID,Date_Of_Birth))
Else
Invalid_msg = 'This is not an person_type of Employee!'
Return Next_Number
Now, when I create a new employee I need the employee number to appear as
"AppsLead-Emp-00001"
But its not, and the screen of employee master is not allow to create an employee without filling the number.
How to do the same?
What should be the Employee Number Generation ?
1- Automatic generation with Global Sequencing
2- Manual
If your answer is manual, in the employee master screen, the employee id is required and when you create the employee the id should be entered.

there are some fast formula you can use.
Please check metalink

Structural authorization - creation of employee number

Hello Experts,
We are facing an issue with strutural authorization in creation of employee number,
I have tested without assigning stuctural authorization and it process the hiring action and generates the employee number
(Hiring action is carried through the adobe form which inturn calls the ABAP Function module),
for the same user if i assign Strctural profile with Function module RH_GET_MANAGER_ASSIGNMENT ( User is assigned to an employee who is Chief ) the hiring action which has to happen through adobe form is not happening and when we check in the program it is throwing an error as Failed strutural authorizations.
I checked whether the employee which has to generate lies within the organization unit of the manager ( who is chief) and it does lies with in the same org unit.
can you please help me in analysing why the employee is not getting gereating though the user is having proper HR authorizations and Strutural authorization assigned.

Hi.
After 2½ days of frustration I finally nailed this.
Function group RHAC, that handles the authority checks, initially buffers a table called VIEW containing all objects available for the user. As stated earlier in this conversation, SAP handles creation of relations in HRP1001 (links PA and OM). At this point the new employee number is appended to buffered table VIEW in function group RHAC.
When execution the PA40 activity through CALL TRANSACTION, the creation of the relations are not handled - and the same goes for updating the buffered table VIEW. The table can be updated using the function module RH_VIEW_ENTRY_INSERT from the same fundtion group:
This example might be useful
data: ls_view_entry type hrview,
        ls_related_object type hrobject.
ls_view_entry-plvar = '01'.
ls_view_entry-otype = 'P'.
ls_view_entry-objid = lv_pernr.
ls_view_entry-begda = '18000101'.
ls_view_entry-endda = '99991231'.
ls_view_entry-maint = 'X'.
ls_related_object-plvar = '01'.
ls_related_object-otype = 'S'.
ls_related_object-objid = lv_ny_objid.
call function 'RH_VIEW_ENTRY_INSERT'
    exporting
      view_entry     = ls_view_entry
      related_object = ls_related_object.
Best regards
Poul Steen Hansen
Senior Technical Consultant
EDB Consulting Group A/S, Denmark

Structural authorization - creation of employee number in webdynpro or abap

Hello Experts,
We are facing some problems with the combination of structural authorizations and the creation of a new employee.
When we use PA40 to create a new employee this does not give any problem.
In the webdynpro we first execute a call transaction PA40 to apply infotype 0000 and 0001. This works well.
Except that the call transaction does not set the connection between PA and OM. (so we did program this ourselves)
In PO13 and the table HRP1001 the same relations are made as when we use PA40 in the sap gui.
After this we do call transactions PA30 for the next infotypes.
When we check the SU53 it gives a message: problems with structural authorizations object P (with the employeenumber) starting at 01.01.1800, enddate is empty.
The employee is manager and connected with his userid in infotype 0105.
We use in the structural profile the function module RH_GET_MANAGER_ASSIGNMENT
We checked with transaction HRHAUTH.
User has been adjusted to the tables T77UA etc.
We do not use workflow in this webdynpro
We used the trace function when this was executed, but it did not give more information about missing structural authorizations.
This issue was before on SDN (Structural authorization - creation of employee number) but unfortunally there was no solution there for the issue!
Hope one of you can help me to find the solution!
With kind regards,
Rita Mensink

Hi.
After 2½ days of frustration I finally nailed this.
Function group RHAC, that handles the authority checks, initially buffers a table called VIEW containing all objects available for the user. As stated earlier in this conversation, SAP handles creation of relations in HRP1001 (links PA and OM). At this point the new employee number is appended to buffered table VIEW in function group RHAC.
When execution the PA40 activity through CALL TRANSACTION, the creation of the relations are not handled - and the same goes for updating the buffered table VIEW. The table can be updated using the function module RH_VIEW_ENTRY_INSERT from the same fundtion group:
This example might be useful
data: ls_view_entry type hrview,
        ls_related_object type hrobject.
ls_view_entry-plvar = '01'.
ls_view_entry-otype = 'P'.
ls_view_entry-objid = lv_pernr.
ls_view_entry-begda = '18000101'.
ls_view_entry-endda = '99991231'.
ls_view_entry-maint = 'X'.
ls_related_object-plvar = '01'.
ls_related_object-otype = 'S'.
ls_related_object-objid = lv_ny_objid.
call function 'RH_VIEW_ENTRY_INSERT'
    exporting
      view_entry     = ls_view_entry
      related_object = ls_related_object.
Best regards
Poul Steen Hansen
Senior Technical Consultant
EDB Consulting Group A/S, Denmark

Same Employee Number two Vendor Codes

Hi All
I created an employee as vendor by linking his personnel number in FK01 but when I tried to create the another vendor with same employee number the system is allowing me to do so. Am i missing any config or is it a standard process in SAP to allow to vendor codes for one employee number.
Expecting your replies.
Regards
Rajaram

Hi,
yes why should this be not possible? Normally you cretae the "employee" vendors e.g. for the travel management with TC: PRAA, so just think the case one employee is working in company code A (assigned to personell area A) he gets paid his travel expenses through the vendor account in cc A, then the employee moves to another company e.g B in assigned to Personell Area B then he gets paid on his vendor account cretaed in cc b but stil has the same employee number.
I hope this help a little bit to explaing why it should be possible to allow this,
Regards,

Global Employee Number

Similar Messages

Maybe you are looking for