Country Reassignment Action

Hi all
I will have configure country reassignment action which I can define in simple words is combination of entry action with the new personnel number and the leaving action for the previous personnel number. While studying what more I came to know about this is in table (T529A) we have to set the 'Country reassignment' indicator on for this action
If I am correct then will anybody please let me know how to configure Country Reassignment action and what will be Info Types that I need to consider in country reassignment action.
Thanks
Subrat

Hi Paul
1st let me answer your question, yes we donu2019t have implemented Management of Global Employees (MGE) and itu2019s very new for me. Recently this requirement came to me and while studying I came to know about Country Reassignment as a solution. Currently we use to terminate employee from current company and then hire in new company code.
Further I have doubt in your line u201Cthere is no infotype group assigned to this action. But you do have to have a test individual with position available in the new countryu201D Can you please explain me in detail as I am new in MGE and as per my understanding InfoGroup is required for action.
I appreciate you early and details response on this.
Regards,
Subrat

Similar Messages

  • "Action does not exist error" during country transfer action

    Hello, everyone.
    We are on ECC5.0 with MGE.  Recently our users are getting an error - "Action does not exist on mm/dd/yyyy" when they perform a country transfer action (transfer from country A to country B).  Because this is a hard error, the action is stopped and our users have to re-execute it.  Surprisingly, the action works fine for the second time. 
    The error comes from message class PG no. 022 in the Include program MP000040.
    We raised this issue to SAP but all they told us to look into our user exits.  We were told to remove our exits entirely to see the error happens.  The problem is that this error does not happen each time.
    Has anyone experienced this error?  If so, does anyone know why this is happening and how to resolve it?
    We tried to debug the code step by step and came across CPREL is filled with "02" in OBJPS for infotype 0000 in the program FP50MF10.  We have no idea as to how the OBJPS is filled with a value.  Infotype 0000 is not supposed to have this field populated.  We think this is the root cause of the error.  But why does it happen?
    Any help will be greatly appreciated.
    Regards,
    Noriko

    Hi.
    We use both PBAS0001 and HRBAS00_CCHANGE.
    Noriko

  • Cross country's transfer

    There is no concurrent employment setup in SAP in my company.When transfer one employee from one country to another country,is it possible to keep the same personnel number and therefore keep all the history record of this employee ? the employee's payroll will be terminated in SAP after transfer since  another country just use HR module but doesn't use SAP to run payroll. Can sombody share your experience? Thanks.

    Setup Country Reassignment action to achieve this.
    http://help.sap.com/saphelp_erp2005/helpdata/en/0c/500638142d11d3965a00a0c9308b52/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/9b/f822b18418ec49a49604c9bb880d32/frameset.htm

  • How  to maintian Infotype 0302?

    Dear All,
    How  to maintian Infotype 0302, Additional Actions.
    Direct selection shows error- This Infotype cannot be maintianed directly.
    Is it maintained directly when we do two actions on the same day, if yes how to view both the actions?
    Regards,
    Saureb

    Hi
    Please see SPRO node "Set up personnel actions"
    You can use personnel actions to carry out complex personnel administration procedures. A personnel action displays, in the correct sequence, the infotypes that have to be maintained for a specific action.
    In this step
    you determine whether you want to use the Additional Actions infotype (0302).
    The Additional Actions infotype (0302) enables the automatic logging of all personnel actions types that you carry out for an employee on a key date.
    Note that in the Actions infoytype (0000), only one personnel action type is saved per day. In this infotype, you only store the personnel action types that change the status of the employee, such as the personnel action type Leaving.
    you define the personnel action types that represent the personnel processes in your enterprise. This means that within the personnel action Hiring, all the infotypes that must be maintained when hiring a new employee are displayed automatically to the personnel administrator for processing.
    define a priority list for the personnel action types that do not change status, and must therefore not be stored in the Actions infotype (0000), but which should nonetheless be logged in this infotype.
    If the personnel administrator performs no personnel action types that change status, but instead several that do change status on one day, the priority list controls which of these personnel action types is to be stored in the Actions infotype (000).
    Note that personnel action types that are only used to process several infotypes in an infogroup should not be stored in the Actions infotype (0000). SAP recommends that you log personnel action types such as these automatically using the Additional Actions infotype (0302).
    You only have to carry out this activity if you want to use the Additional Actions infotype (0302), and have activated this infotype.
    If you want to perform simplified employee organizational changes, you can also set up a 'Country reassignment' action type in this step, for which you set the Country reassignment indicator. For more information on country reassignments, refer to Personnel Administration documentation under Business Processes in Personnel Administration -> Country Reassignment.
    Requirements
    Familiarize yourself with the personnel processes that occur in your enterprise, such as entry or leaving.
    Standard settings
    In the standard system, the Additional Actions infotype (0302) is not activated. Furthermore, the SAP standard system contains several personnel action types.
    Recommendation
    Refer to the SAP sample entries for guidance when you are defining your own personnel actions.
    Activities
    1. If you want to use the Additional Actions infotype (0302), call up view Activate 'Additional Actions' for all existing personnel numbers.
    2. Call up the view Personnel Action Types.
    3. Check the SAP sample entries.
    4. Delete the entries you do not require.
    5. If required, define several personnel action types.
    a) Choose New entries.
    b) In the Action type field, enter a number, and in the Name of action type field, enter a name for the personnel action type.
    c) In the FC field, enter the function character for the personnel action type.
    You can distinguish the first entry actions from all the others. Choose the function character 1 for first entries, 7 for first entries with data transfer from recruitment and 0 for all other personnel action types.
    d) If required, define the status indicator STAT1 (customer specific).
    This status indicator is not used in the standard system. You can use this indicator individually.
    e) Define the status indicator STAT2 (recruitment) and STAT3 (Special payment).
    f) Decide whether you require standard decision rules to define plausibility rules for the sequence of personnel action types (check feature).
    Note: Never change the standard decision rules.
    g) Decide whether organizational assignment data may be changed whilst personnel actions are being carried out. When you set the indicator P, the position field in the Actions infotype (0000) is ready for entry.
    You can process the fields Personnel area, Employee group and Employee subgroup with the indicators PA, EG and ES.
    h) Assign an infotype group number to the IG field in the personnel action type.
    You can then process the the individual infotypes from the selected group in the personnel action type in the appropriate sequence.
    You defined the infotype groups in the " Define Infogroups" step.
    i) Specify whether the date entered on the initial screen of the Actions infotype (0000) is the start date for new infotype records or the end date for old infotype records. This is especially important in the case of leaving actions.
    j) Use the indicator U0000 to determine whether your personnel action type should create a new record for the Actions infotype (0000).
    k) Use the Country change indicator to determine whether the personnel action type is a country change.
    6. If you have activated the Additional Actions infotype (0302), determine whether your personnel action type should be logged in the Additional Actions infotype (0302) using the U0302 indicator. Call up the view Priority list for personnel action types.
    Specify a priority list for the personnel actions which do not change the status, and for which you have set the indicator to U0000.
    In the Priority field assign sequential numbers with a maximum of two digits to each of the personnel action types. The smaller the number, the higher the priority of the accompanying personnel action type.
    Further notes
    Do not define any new personnel action types if only the infotype group should be different for the personnel administrator. To achieve this, you can define the infogroups as user group dependent.
    The keys for personnel action types, which you carry out for an employee, for example, hiring, organizational change, leaving, are stored in the infotype Actions (0000).
    The existence of a personnel number is ruled out by the existence of a record in this infotype.  Only one record can exist for this infotype on the database at any one time.
    When an employee has left, there is also a record in the system for the personnel action Leaving. The most important information in this infotype is the employee's employment status: active, leave of absence, retired, left.
    Personnel actions that are only used to process several infotypes in an infogroup should not be saved in the infotpye Actions (0000). SAP recommends that you log personnel actions of this kind automatically using the Additional actions infotype (0302).
    Notes on the creation of batch-input sessions:
    If you want to carry out a batch-input for a personnel action, do not call up transaction PA40 (Actions menu). Instead, call up transaction PA30 (infotyp menu). In the actions menu place your cursor on the line containing the relevant action; this assumes you know the exact setup of the menu.
    Proceed as follows:
    1. Call up transaction PA30.
    2. Choose the Actions infotype (0000).
    3. Enter the personnel action type in the Type field.
    4. When processing entry actions, enter the function code '=INS', for other actions, enter the function code '=COP'.
    regards
    Pravin

  • "Reassign" and "Adhoc Route" Actions in human tasks

    Has anyone run into oddities when using either the "Reassign" or "Adhoc Route" actions from within a task in the BPM workspace?
    When I try to re-assign to a different participant, it seems the assignment gets lost altogether. The task history section on the task form shows the particpant went from the user I was logged in as and performed the reassign action to a "blank" participant on the next row. The Action column next to the blank participant shows "System Update" and the updated by column shows the participant from the previous row.
    When I attempt to Adhoc Route, I select the participant to send to (via the search and moving them from the LHS to RHS of the shuttle widget) and add my comment - but when I click OK it doesn't go anywhere. The screen updates and the task history shows a new row indicating a comment was added, but not the adhoc routing assignment. It just stays in the current assignment as if nothing changed except the comment.

    It also seems that the "Edit Routing Slip" option isn't functioning properly. If you go into a human task and click the "edit" pencil next to the "Task will go from starting to final participant" and check "Allow participants to edit new participants" then when you view the task within workspace the routing slip within the "History" section will appear with buttons to add/remove/edit rows in addition to an "Apply" and "Reset" button. However the add/remove/edit icons are always disabled. I tried with a participant within the routing slip, the Process Owner as well as an administrative user, but the results were the same. Am I doing this incorrectly?
    Are these bugs or have these features not yet been implemented?

  • Customize / Override BPM in-build actions like reassign

    We have a requirement to override the reassign action in BPM workspace to perform certain checks before allocate to person. Basically when a supervisor is reassigning a task, he can only reassign the task to a member who work under him and also has specific skill (these information maintained in a DB called agent profile) to be performed.
    If anyone knows about the steps or any documents, request you to please share with us. We are closing our UAT and this has came as a UAT feedback. We are at the edge of production now, hence the solution is urgent for us.
    Thanks in advance,
    Rati

    Sorry - don't know who wrote this code but hope it is the reassignment logic you are looking for:
    /* Copyright (c) 2004, 2009, Oracle and/or its affiliates.
    All rights reserved. */
       DESCRIPTION
        Sample that demonstrates how to programatically reassign human workflow task from one assignee to another
    import java.util.ArrayList;
    import java.util.HashMap;
    import java.util.List;
    import java.util.Map;
    import oracle.bpel.services.workflow.IWorkflowConstants;
    import oracle.bpel.services.workflow.WorkflowException;
    import oracle.bpel.services.workflow.client.IWorkflowServiceClient;
    import oracle.bpel.services.workflow.client.IWorkflowServiceClientConstants;
    import oracle.bpel.services.workflow.client.WorkflowServiceClientFactory;
    import oracle.bpel.services.workflow.query.ITaskQueryService;
    import oracle.bpel.services.workflow.task.ITaskAssignee;
    import oracle.bpel.services.workflow.task.ITaskService;
    import oracle.bpel.services.workflow.task.impl.TaskAssignee;
    import oracle.bpel.services.workflow.task.impl.TaskService;
    import oracle.bpel.services.workflow.task.impl.TaskUtil;
    import oracle.bpel.services.workflow.task.model.Task;
    import oracle.bpel.services.workflow.verification.IWorkflowContext;
    public class ReassignTask
        public static void main(String[] args) throws Exception {
            //command line input arguments validation
            if ( args.length != 6 ) {
                System.out.print("Usage: java ReassignTask protocol(SOAP/REMOTE) fromUser(jcooper) fromUserPassword(welcome1) taskId toUser(jstein) type(user/group/application_role)");
                return;
            String type = args[5];
            if (!((type.equals(IWorkflowConstants.IDENTITY_TYPE_USER)) ||
                  type.equals(IWorkflowConstants.IDENTITY_TYPE_GROUP) ||
                  type.equals(IWorkflowConstants.IDENTITY_TYPE_APPLICATION_ROLE))) {
                throw new Exception("Type has to be user or group or application_role");
            reassignTask(args[0], args[1], args[2], args[3], args[4], args[5]);
        public static void reassignTask(String protocol, String fromUser, String fromUserPassword, String taskId, String toUser, String type)
            throws Exception {
            System.out.println("Using the protocol " + protocol + " for reassigning the task " + taskId + " from " + fromUser + " with password " + fromUserPassword + " to " + toUser + " of type " + type + " ..... ");
            Map<IWorkflowServiceClientConstants.CONNECTION_PROPERTY, String> map =
                new HashMap<IWorkflowServiceClientConstants.CONNECTION_PROPERTY, String>();
            // get Human Workflow client
            IWorkflowServiceClient wfSvcClient = WorkflowServiceClientFactory.getWorkflowServiceClient(protocol, map, Util.getLogger());
            ITaskQueryService querySvc = wfSvcClient.getTaskQueryService();
            IWorkflowContext fromUserCtx = querySvc.authenticate(fromUser, fromUserPassword.toCharArray(), "jazn.com");
            Task task = querySvc.getTaskDetailsById(fromUserCtx, taskId);
            ITaskAssignee toUserAssignee = new TaskAssignee(toUser, type);
            List l = new ArrayList();
            l.add(toUserAssignee);
            ITaskService taskSvc = wfSvcClient.getTaskService();
            Task reassignedTask = taskSvc.reassignTask(fromUserCtx, taskId, l);
            System.out.println("Task was re-assigned successfully from " + fromUser + " to " + toUser);

  • Dynamic Actions in Custom Development

    I have a dynamic action running for an action.
    But when the same action is called through BDC or in the program this doesnot work.
    Can anyone suggest the reason as to why the dynamic actions are not getting called for the same process in the developments or BDC.
    Thanks

    Hi Manoj,
    I have a seperate BDC for Dynamic action but I cannot attach this in the BDC created to run the PA40 Country assignment action as the new employee number that is created during Reassignment action cannot be called in the BDC which is created for Dynamic action.
    In Dynamic action this is getting populated as it is present in the memory when the action is run in pa40.
    The option that you have told i troed the same to explore but this was not working.
    Some how I have to do this manually by getting the new employee number seperately and then collect the data of old number and pass it to the new number.
    Santoshi

  • Changes needed in OM while performing Actions in PA40

    Hi,
      I am new to SAP...I need to run an "Organizational change" action type. The action reason is "title change" . Can anyone let me know what are the changes need to be done in PA and OM to run this action?
    Best Regards,
    Satish

    Hi Satish
    Organization Reassignment Action is generally used when the employee gets transferred, gets promoted etc. This action allows changing IT0001 for the employee where you would be able to change his position, job, personnel subarea, payroll area etc. Along with IT0001 you are also allowed to change IT0007, IT0008 etc.
    When you execute this action in PA, the changes get reflected in OM as well provided your PA+OM integration switch (PLOGI + ORGA) is ON in table T77S0.You will not need to make any change in OM separately after executing this action if this intergration switch is on.

  • Cross Country Transfer

    Hi Gurus,
    Query relating to Cross Country Transfer. Can anyone enlighten how to perform Cross Country Transfer Action in Sap R/3? I am aware that a Central person Record needs to be created in HRP 1001 but how to go-ahead in-relation to performing Cross Country Transfer action in PA40 and assigning 2 personal numbers to an individual.
    Any assistance is highly appreciable and it will be suitably rewarded.
    Regards,
    Garima

    Hi Garima,
    Procedure for maintaining global employment is as follows :
    Creating Global Assignments
    In this step, you store all the key information with regard to a global assignment.
    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 employee’s 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.
    Or for further queries you may refer to following link, as it will help u a lot :
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/9b/f822b18418ec49a49604c9bb880d32/frameset.htm
    One more thing, in order to create person-ID (0709 INFTY) you have to maintain certain settings for your system, or else their is one function module, i don't remeber the exact name, once i get to recall will post you soon.
    Hope this sorts out your problem,
    In case need more help, plz do reply.
    Regards,
    Swapnil Mishra

  • Updation of Personnel Area for a position and an employee after hiring.

    Hi Experts,
    I have query regarding Personnel Area updation for an employee.
    Here is the scenario :-
    An employee was hired to a Position with personnel area  "A". In future, the Personnel area for this position is chnaged to "B". Now the PA for this person doesn't get updated automatically.
    Could you suggest how do we update the PA for an employee?
    Thanks
    Niharika

    Hi Niharika,
    If the personnel area of an employee is getting changed then that can be done by executing organisation re-assignment/ transfer action.
    Regards,
    Chetan
    Hi Niharika,
    In Set up personnel actions please mark the country reassignment indicator. Hope this will work.
    Regards,
    Chetan
    Edited by: Chetansw on Jun 23, 2009 12:48 PM

  • How to use standard workflows in my company?

    Hi Experts,
    I want to know how do i use standard workflows for my company. I have searched forum, but coudn't find proper answer. I have seen some standard workflow numbers(eg.WS12300111). But when i search for them it wont works. It will pop up "Choose Workflow Template" window. When i select the module there it opens up the empty folders.
    What is the meaning of this?
    Can i know what do i need to do for overcome this problem?
    Thanks,
    Rashika.

    Hello rashika ,
      To differentiate between standard and  custom workflows .
    All custom workflows would have first three digits lying betwee 900-999  ( called prefix number range )
    The number range 90000000 - 99999999  is reserved for customer developmen t and the range 00000000 - 89999999 is reserved for SAP.
    Or to  know precisely what exactly is the number range of  custom workflows in your system , check through tcode  OOW4.
    To help with your search in HR workflow , I am providing some -
    HR -OM
    WS01000014     Execute Designated Personnel Action
    WS01000038     Consolidate Headcount Planning
    WS01000039     Generate Headcount Planning
    WS01000040     Create Vacancy for Position
    WS01000041     Delimit Vacancy for Position
    WS01000043     Error in processing a vacancy
    WS01000077     Execute Designated Personnel Action
    WS01200136     Message New Employee in Department
    HR-PA
    WS00400077      Absence approval (asynchr. unlock)
    WS00400078     Handling of unapproved absence
    WS00400095      Display approved absence
    WS00400220      Preparations for start of work
    WS00400221      Choose letter
    WS00400222      Approve absence (sychr.unlock)
    WS01000015      ESS Plausibility check change of address
    WS01000036      ESS activities after hiring
    WS01200175      Entry due to country reassignment
    WS20000003      Pay increase approval with SAP forms
    WS20000015      Approve absence
    WS20000017      Determine basic pay items
    WS20000018      Resubmit postponed pay increase
    WS20000057      Find and Lock Employee
    HR-TM
    WS01000109     Cancel leave request
    WS01200003     Find and Lock Employee
    WS04200009     ESS Leave Request
    WS12300111     General Workflow for Documents
    WS12400004     ESS Leave Request Without Approval
    WS12400005     Cancel absence
    WS12400007     Cancel Absence Without Approval Step
    WS20000081     Leave Request with HTML
    HR-PY
    WS01000090      W-2 form reprint
    HR-BN
    WS01000001     Initial enrollment Benefits
    WS01000002     Create offer and inform employee
    WS01000003     Create adj. reason because of event
    WS01000009     Check if the employee is locked
    Thanks,
    sahiba

  • PERSON NOT VISIBLE IN OM IN STAFF ASSIGNMENTS DISPLAY

    hi all
    in OM
    First i uploaded org units through bdc
    next positons through bdc
    next jobs through bdc
    next s-o-c relationships
    in PA
    i uploaded employee master data (i.e. for IT0000, 0001 & 0002)
    while uploading 0001 i have assigned positions to the person and Org unit and Job it has taken bcause it is already assigned in the OM.
    NOW THE PROBLEM
    when i was seeing structure in OM for that positon i am able to see JOB and Org unit but not Person.
    what i have done and what i have to do
    Inputs plz.  it's urgent.
    regards

    PLOGI     EVCCC     2     Master data action: company code change
    PLOGI     EVCRE     X     Generate event with entry T77INT (action designat.
    PLOGI     EVEGC     2     Master data action: employee subgroup change
    PLOGI     EVENB          Enhanced integration (X= on, Space= off)
    PLOGI     EVPAC     2     Master data action for country reassignment
    PLOGI     ORGA     X     Integration Switch: Organizational Assignment
    PLOGI     PRELI     99999999     Integration: default position
    PLOGI     PRELU          Integration: PA update online or batch
    PLOGI     TEXTC          Integration: transfer short text of job
    PLOGI     TEXTO          Integration: transfer short text of org.unit
    PLOGI     TEXTS          Integration: transfer short text of position
    PPABT     PPABT     0     Switch: department
    PPINT     BTRTL          Default value for personnel subarea
    PPINT     PERSA          Default value for personnel area

  • OM-PA Integration

    Dear All
    I have a genuiene problem. When I hire a person for a particular position, that position is stored in the infotype 0001 of the employee. But when I go to tabble HRP1001 there is no person to position relationship visible for the particular position.
    Moreover in PO13 if I maintain a relationship between a position and a person it is visible.But not in case if I hire thru PA40.
    Please help me.I have checked all tables, but not able to find any error.

    hi..........
    PLOGI     EVCCC     U2     Master Data Action: Company Code change
    PLOGI     EVCRE     X     Generate event with entry T77INT (action designate)
    PLOGI     EVEGC     U2     Master Data Action: Employee subgroup change
    PLOGI     EVENB           Enhanced integration (X=on, Space=off)
    PLOGI     EVPAC          Master Data Action: Country reassignment
    PLOGI     ORGA     X     Integration Switch: Organizational Assignment
    PLOGI     PLOGI     01     Integration plan version / Active Plan Version
    PLOGI     PRELI     99999999     Integration: default position
    PLOGI     PRELU          Integration: PA update online or batch
    PLOGI     TEXTC          Integration: transfer short text of job
    PLOGI     TEXTO          Integration: transfer short text of org.unit
    PLOGI     TEXTS          Integration: transfer short text of position
    PPABT     PPABT     0     Switch: department
    PPINT     BTRTL          Default value for personnel subarea
    PPINT     PERSA          Default value for personnel area
    T77S0 table.............
    RHINTE00,10,20,30

  • What is PA40 in HR

    What is transaction PA40 in Human Resource module of SAP?

    hi Aruna,
    PA40 is the screen where you can enter all the onboarding (hire) employee data and also you can change the actions like...............
    Hire
    Hire Applicant
    Country reassignment
    ESS New Hire
    Family Status Change
    Employee Status Change
    Performance Appraisal
    Change of Position
    Change of Pay
    Transfer/Relocation
    Create New Assignment
    Tuition Reimbursement
    There are the some examples, we can define accordin to the requirements. before maintaing all these actions we should keep in mind about the date, means on which date these actions are perfromed which refelct in PA30 actions overview screen.
    i think this more than wahat you asked.
    reward me if this helps.
    Thanks,
    Vasu.

  • Problem on Assigning Person to a Position

    Hi SAP-HR folks,
    I would like to ask for your assistance on my problem below.
    I've hired a person using New Hire action type. During the hiring process, I've assign the person to a position which I've created also. Then, there is a need for this person to be re-assign to another vacant position. Re-assigning should be done using drag and drop in transaction PPOME.
    I've successfully done the re-assignment of this person to another vacant position using drag and drop. But according to the test scripts that we are following, the expected result should be that the system should refuse the re-assignment after filling in the dates. Re-assignment can only proceed after delimitation of the assignment of person to position.
    May I know if the action that I've done is a normal behavior of SAP? In the case the test scripts are right, may I know on how to successfully follow the scripts?
    Thanks in advance!

    whenever transfer employee from one positon to other position don't do this by drag and drop from ppome.
    just do this by PA40, Org Reassignment action.
    as ppome not support 100% for such change.
    and also if u do this from ppome, it0001 can't be updated for both positions.

Maybe you are looking for