Termination Actions Infotype in Personnel Administration

Hi Cronies,
My Client requirement was It shouldnt perform Termination Action Until and unless employee deposits company belongings So what I did was I have created a custom Infotype as Assets Handover Infotype (9001) and I have added in Termination action
While performing Termination Action Action Infotype is displaying first I dont want to display action infotype first I want to display assets handover Infotype first so that User can complete Assets Handover activities and then it should delimit action infotype How can I achieve this I have added In Infogroup as assets handover first after that action infotype still I can see Acton Infotype first  please let me know how can i do that???? I want assets handover infotype to be displayed first and after that It should display action infotype
Edited by: My SAP Cronies on Jan 16, 2012 6:56 PM

I want Custom Infotype to be displayed first before action infotype. See I dont want to delimit the position.    Action Infotype is appearing first,  when we delimit it will take next infotype in Termination.
Instead of action infotype to be displayed first I want Custom Infotype to be displayed first so that User can check that Infotype for employee belongings to be deposited before terminating How can I do that? please let me know about this how can i do that
Edited by: My SAP Cronies on Jan 16, 2012 8:22 PM
Edited by: My SAP Cronies on Jan 16, 2012 8:23 PM

Similar Messages

  • Table entries for Personnel administration and organisation management

    Hi ,
    For a functional consultant do we need to remember the table entries where the employee infotypes saved or where the table entries is useful as far as Personnel administration and organisation management is concerned.....
    and one more thing how to create a custom Infotype (employee) detail documentation required ...
    keep me posted
    Thanks

    hi,
    it is really helpful if you rember the table name which holds the information about the infotypes
    table starting with <b>PA</b> contains all the personnel information data
    like <b>PA0001</b> holds the information of<b> infoty0001</b>
    similary you can check for other info types
    and hr haster table like<b> HRP1000</b> or<b> HRP1001</b> hold all the other hr objects including your personnel objects as well as organizational related objects
    <b>infotype numbers</b>
    Four digit number nnnn
    Unique identification
    <b>9000 to 9999 reserved for customer infotypes</b>
    <b>naming convention
    0000 to 0999 – HR Master data  / Applicant data
    1000 to 1999 – Organizational Management
    2000 to 2999 – Time data                     
    4000 to 4999 – Applicant data           
    9000 to 9999 – Customer defined</b>
    defination of infotypes
    <b>Each infotype nnnn requires at least two structures and one table</b>:
    <b>Structure PSnnnn</b>
         Structure PSnnnn contains all of the infotype data fields.
    <b>Structure Pnnnn</b>
         Structure Pnnnn contains infotype key fields and all of the data fields
    from structure PSnnnn .
    <b>Transparent table</b> PAnnnn and/or transparent table PBnnnn
    <b>infotype module pool</b>
    A module pool should be used with each infotype. This module pool is the main program for the maintenance interface for the info type.
    The name of the program is MPnnnn00. Where P stands for Human Resources (personnel) and nnnn is the four-digit info type number.
    Transparent table PAnnnn is required if you want to use an infotype within Personnel Administration.
         If you want to use an infotype within Recruitment, transparent table PBnnnn is required.
    In accordance with the distribution of infotype name ranges, objects P9nnn , PS9nnn , PA9nnn and PB9nnn are assigned to the customer name range.
    <b>infotype screen</b>
    An initial screen
    A single screen
    A list screen
    <b>Initial screen</b> is used as technical interface
    Screen 1000 is used for all info types
    Processed in background and not displayed
    Performs general initialization procedures
    <b>A single screen</b>
    Its an interface between the system and the user.
    It enables to create, display or maintain data records.
    Screen 2000 is used for single screen.
    <b>list screen</b>
    Unable to list all records in info type
    Screen 3000 is used for list screen
    <b>infotype time constrains</b>
    A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:
    A    Only one record may exist, valid  from 01/01/1800 to 12/31/9999. Splitting and deletion is not permissible.
    B    Only one record may exist, valid  from 01/01/1800 to 12/31/9999. Splitting is not permissible, but may be deleted.
    T    The time constraint varies depending on the subtype.
    Z    Refers to time management infotypes.
    <b>
    to create infotype</b>
    Transaction code
    <b>‘PM01’.</b>
    <b>enhancing PA infotype</b>
    Start the Personnel Administration info type copier (PM01)
    Enter the info type number.
    Choose Enhance info type.
    Start transaction PM01
    You access the Create Info type screen:
    Choose Enhance Info types.
    In the Info type no. field, enter the four-digit number of the info type you want to create. When you specify the info type number, please remember to enter any leading zeros.
    In the Sub-Objects group box, flag CI Include.
    Choose Create. The Dictionary: Initial Screen is displayed.
    Create the Cl include.
    Choose Activate.
    Return to the Create Info type screen.
    Choose Create All.
    hope this information will help you..
    and don't forget to reward points

  • How to restrict change/creation of Infotype record after termination action

    Hi All,
    Based on my client requirement, we have to restrict any change or creation of certain infotypes after performing termination action.
    For Ex:- Suppose termination date is 01.01.2008. End user should not able to change or create any new record for infotype 0001, 0008 and 0016 after 01.01.2008.
    This is very critical. Request your valid input ASAP.
    Thanks in advance.
    Regards,
    Purnima

    Hi Sreenu,
    Thanks for your valid input.
    I tried by giving "EDQ". Then I got below mentioned error while performing termination action.
    Error:- "Status EDQ of the user interface MP000100 missing"
    Can you help please?
    Regards,
    Purnima

  • Adding Personnel Name to Actions Infotype

    Hi,
    I am trying to add Peronnel Name beside the Pers. No. on the screen of Actions Infotype for PA30.
    Any help and advise would be greatly appreciated.
    Thanks.
    John

    As per your answer
    Infotype 0000, Screen Header 00
    Infotype 0001, Screen Header 03
    Now check V_582A_B whether these entries are
    0000     Actions                                     00
    0001     Organizational Assignment     03
    If yes
    Now check V_T588I whether these entries are
    00     A     00
    00     B     00
    03     A     03
    03     B     03

  • How to perform TERMINATION action

    Hello experts....
    I am new to SAP... can anybody please let me know how to configure termination action and what type of infortype we will configure for Termination.Thanks in advance...........

    Hi,
    Follow the below mentuion steps:-
    1. Create an action say 'TM' at the img path mention below:-
    Personnel Management->Personnel Administration->Actions->Set up personnel actions
    2. Create action reasons also at the link below:-
    Personnel Management->Personnel Administration->Actions->Create reasons for personnel actions
    3. Add the termintaion action in the Action menu of your country:-
    Personnel Management->Personnel Administration->Actions->Change action menu
    4. Define infogroup for your termination action below:-
    Personnel Management->Personnel Administration->Actions->Define infogroups
    Usually, IT0001, IT0002, IT0014, IT0015, IT0041 are set up in the infogroup action. Also, get the requirements from your customer like which all infotype he will like to delimit.
    5. Most important is to set the Inactive status for the employee
    Go to table T529A and set the status as '0' in the employment field 'STAT2'.
    Thanks & Regards, Swapnil Mishra

  • Dump error while running termination action

    I'm facing a dump error while running termination action, please, if some one wud help me out of this error. here when im termination action the system is opening action infotype when given the date of termination and try to save, system shows a warning message that "Record valid from 08.08.1995 to 31.12.9999 delimited at end" then I press enter and system is asking me to save. when I do so, rather than it taking me to another screen its throwing a dump error.
    Runtime Errors         SYNTAX_ERROR
    Date and Time          21.10.2008 18:54:05
    Short dump has not been completely stored (too big)
    Short text
         Syntax error in program "SAPLCACS_BU_PARTNER ".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLBUD_CHECK" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
         The following syntax error occurred in program "SAPLCACS_BU_PARTNER " in
          include "LCACS_BU_PARTNERU44 " in
         line 19:
         "The key of internal table "LT_BUT0BK" contains components of type "X" "
         "or "XSTRING". The "READ TABLE LT_BUT0BK" statement is not permitted fo"
         "r such tables in a Unicode context."
         The include has been created and last changed by:
         Created by: "SAP "
         Last changed by: "SAP "
         Error in the ABAP Application Program
         The current ABAP program "SAPLBUD_CHECK" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         The following syntax error was found in the program SAPLCACS_BU_PARTNER :
         "The key of internal table "LT_BUT0BK" contains components of type "X" "
         "or "XSTRING". The "READ TABLE LT_BUT0BK" statement is not permitted for
    "r such tables in a Unicode context."
    ger Location of Runtime Error
    Program                                 SAPLBUD_CHECK
    Include                                 LBUD_CHECKF01
    Row                                     1.129
    Module type                             (FORM)
    Module Name                             RLDEL_CHECK
    ce Code Extract
      SourceCde
    9
    0 *------ ... Funktionsbausteine ermitteln -
    1   CALL FUNCTION 'BDT_TBZ1F_GET'
    2     EXPORTING
    3       iv_objcn  = gc_objcn_bupa
    4       iv_objap  = gc_objap_bupa
    5     TABLES
    6       et_tbz1f  = lt_tbz1f
    7     EXCEPTIONS
    8       not_found = 1
    9       OTHERS    = 2.
    0   READ TABLE lt_tbz1f INDEX 1.
    1   IF sy-subrc = 0.
    2     CALL FUNCTION 'BUP_PARTNER_GET'
    3       EXPORTING
    4         i_partner    = is_but100-partner
    5         i_cp_exclude = gc_x
    i_is_exclude = gc_x
    PORTING
    e_but000_int = ls_but000_int
    CEPTIONS
    OTHERS       = 1.
    ... Funktionsbausteine aufrufen -
    T lt_tbz1f WHERE     ztpkt =  'RLDEL'
                 AND NOT fname IS INITIAL.
    Datümer alt = neu = SPACE => Löschung, sonst Update -
    (Einschränkung der Gültigkeit)
    FUNCTION lt_tbz1f-fname
    PORTING
    i_partner        = is_but100-partner
    i_partnerguid    = ls_but000_int-partner_guid
    i_role           = is_but100-rltyp
    i_dfval          = is_but100-dfval
    i_calltp         = iv_calltp
    i_valid_from     = is_but100-valid_from_dats
    i_valid_from_old = iv_valid_from_old
    i_valid_to       = is_but100-valid_to_dats
    i_valid_to_old   = iv_valid_to_old
    PORTING
    e_result         = lv_result.
    ... Ergebnis merken, wenn höher als bisheriges Zwischenergebnis-
    v_result > gv_wu_result.                          "#EC PORTABLE
    wuresult = lv_result.
    F.
    ... Ergebnis ist 'Nicht löschen': Zeitpunkt abbrechen -

    HI Mallik,
    for termination action the operation that i've set is
    lis9  0001
    cop  0002
    lis9  0007
    cop  0008
    lis9  0014
    lis9  0015
    lis9  0587
    so just want to know if the set format for termination action is right
    and other option is that if there is some change to settings of infotype charateristics in table v_t582A this may cause change in the date that is cause of error.
    can u please suggest the above alignment of operations and infotype is right and provide me the idle settings for infotype characteristics which may solve my query.
    thanks mallik.

  • Issue with Dynamic Actions - Infotype 0041 Updation

    Hi All,
    Requirement :
    I have to update the Date type-13 ( Resignation Date - DAR11 ) without Date ( DAT11 as Blank value - User will fill through Infogroup ) while performing the Termination action through PA40.
    Added below code in V_T588z (0000):
    I have added 186,188 Lines.Other lines are standard thing.
                  04     180     P     PSPAR-MASSN='10'/X  **Termination
                  04     181     P     PSPAR-MASSN='ZB'/X **Termination
                  04     182     P     PSPAR-MASSN='14'/X  **Termination
                  04     185     I     COP,41,,,(PSPAR-BEGDA),(PSPAR-ENDDA)/D
                  04     186     W     P0041-DAR11='13' **BEGIN & END OF CRA01670 CODE ***
                  04     188     W     P0041-DAR11='' **BEGIN & END OF CRA01670 CODE ***
    Issue :
    1. The above logic is not working for Finland ,other countries. For only India it is working.
    2. Some times Date type-13 is coming twice while through the Infogroup-0041 screen twice,which is incorrect. The infotype-0041 should call only once.I have checked the User parameters,MOLGA,USR. But it is not working.
    2. The standard configuration Date type -09-Last day of work - is working fine . But i could not be able to find ,from where it is coming.I have checked the Dynamic actions,but no use.
    Need your inputs to solve the issue.
    Thanks,
    N.L.Narayana

    P     P0000-MASSN='01'    Action type
    P                   P0000-MASSG="01"   Action Reaosn
    P     T001P-MOLGA='40'
    F                   here u will keep the Call Routine
    I     INS,2001,,,(P0000-BEGDA),(P0000-ENDDA)/D  (here u have pass the date of Call routine )
    W     P2001-IAWRT='01'
    But here Infotype 2001 we will give Absence type this IT is used for Booking Absence Types i did not get the Wage type 8001
    thru which IT are u processing it
    for more info Checjk Tabvke V_T588Z  here iam pasteing the sample call routine which i got from earlier thread
    Create a Program (Subroutine) using SE38. Save and activate it.
    ZZSY_DYA_TEST2
    REPORT ZZSY_DYA_TEST2.
    tables : p0000,p0001,rp50d.
    FORM getdate.
    rp50d-date1 = p0000-begda + 90.
    ENDFORM.
    FORM get_date.
    rp50d-date2 = p0000-begda + 180.
    ENDFORM.

  • Making Employment status field editable in Actions infotype

    Hi All,
    Can we make the Employment status or Customer specific status editable in Actions Infotype 0000?
    I tried doing that in 'Change Screen modification' in IMG, but it isn't working.
    Please provide your inputs.
    Thanks!

    Hi,<br>
    It is not possile to do it.
    Each action is assigned the three status indicators STAT1 (customer defined), STAT2 (employment), STAT3 (special payment) in the customizing system.
    When a personnel action record is created, the system automatically fills the Customer defined, Employment and Special payment fields if the action affects the employee's status.
    The first record of the Actions infotype is assigned the status specified in the customizing system. All other records
    have the same status indicator as the new personnel action if this is not BLANK in the customizing system.
    have the same status indicator as the previous record if this is BLANK in the customizing system.
    This applies to all three indicators.
    Can you let  us know the business need or requirement to do it??
    Good luck<br><br>
    Thanks,
    Amosha
    <br><br>"Known is a drop & unknown is an OCEAN!"

  • Personnel administrator

    Hello friends.
    I am working on a workflow for HR module. my issue is to trigger a mail to the personnel administrator, on an event. Plaese can anyone tell me how will i find the personnel administrator, on infotype 0001, ie
    P0001-SACHP. Is there any rule to find this.
    Thanks in advance.
    Vishal VH

    Hi
    Check this rule from PFAC_DIS transaction Code
    21300138 RCPersAdmin  Personnel Administrator
    50000135 HR Adm.Recr. Personnel administrator
    01000012 pdPosPersAdm Position of personnel administrator
    Thanks
    Arghadip

  • Integration between organizational management and personnel administration

    Dear Sirs/Madams,
    I am trying to integrate organizational management and personnel administration to have see positions, jobs, and units which are assigned in PPOME. I made some configuration in T77SO and correct the needed integration in PLOGI position and especially for ORGA.
    Nevertheless, the integration problems did not solve. Now, I was wondering if you would mind helping me in this case.
    Thanks for your considerations,
    Kind Regards,
    Mohammad Hassan Salmani.

    To set up/fix full integration between PA and PD, run below reports in this sequence:
    1. RHINTE00 – Transfer PA records into PD positions –batch
    2. RHINTE20 – Create OM objects in PA tables – Online
    3. RHINTE30 – Bulk update of infotype 0001
    4. RHINTECHECK – Program to check PA to PD
    5. RHCHECKV - Checks all inverse relationships
    Also,It is important to realize that in PA, there are tables that contain objects from OM, i.e. for those items displayed on infotype 0001 Organizational Assignment. Sometimes the tables can get ‘out of step’ with those in PD – table HRP1000. Check those as well. The tables are:
    T513,T513S  Object type C (Job)
    T528B,T528T Object types S (Position) and A (Work center)
    T527X Object type O (Organizational unit)
    Regards,
    Mukesh

  • Resignation / Reliving deletion log data in actions infotype 0000

    Dear all,
    When we delete resignation/relieving entry in Pa30 in actions infotype 0000 no log is maintained.
    where i can see the deletion log please help.
    Regards,
    Gaurav sood

    You have set the indicator in Table:  T529A. for the field U0000 for the leaving action.
    If you set the indicator U0000, the personnel action type is stored in the Actions infotype (0000).

  • Workflow related to personnel administration.

    Hi Everyone,
                         I m in sap-hr and wanted to know that is there  any workflow related to personnel administration.Also how can I create a workflow for filling the personnel data of employees.I had created workflow for leave.
                           I want the detailed steps.
                                                             Regards,
                                                             Pratighya Jain.

    Check this documentaion on SAP Business Workflow, which is built in HR:
    http://help.sap.com/saphelp_46c/helpdata/en/a1/172437130e0d09e10000009b38f839/frameset.htm
    Things that can be done are eg:
    Application forms and everything for handling them
    Absence approvals, travel requests, expenses
    Time
    Pls don't forget to reward points and close the question if you find the answers useful.

  • SAP Query to join action infotype with additional action infotype

    We have created SAP Query on PA0000 which shows all actions that are executed for an employee.
    The problem is that if two actions are exceuted on the same day then it shows only one action instead of showing both the actions.
    As two actions are executed on the same day it will be stored in additional action infotype(0302).We tried to join PA0000(Action infotype) with PA0302(additional action infotype) in SAP Query by using joins(inner join/outer join) but it shows duplicate records.
    Is there any way to get additional action along with records of action infotype without any duplication in SAP Query.

    All entries that are in PA0000 will be in PA0302, but not vice-versa so you just have to reverse what you are currently doing, i.e.: create a Query on PA0302 and join to PA0000, and then make sure your selection criteria is from PA0302 and not PA0000.

  • How to add an customized HR infotype in personnel information on ESS

    Dear Experts,
    I am trying to add a customized HR infotype in personnel information on ESS.  Could you pls provide me some solution or references document. Thanks
    Daniel

    Daniel,
    check this(may give some hint)
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/profile/essPersonalInformationUIenhancementwithoutmodification
    Changing an input field's appearance to Optional in an ESS WD Java scenario
    you need to modify the HomePage framework to include link in ESS for custom infotype.search for chris solomon's blogs in sdn
    Thanks
    Bala Duvvuri

  • HELPP Changes in OM done directly should update in Personnel Administration

    Hello Gurus,
    My client guy did changes in OM by directly moving persons into different positions and work flow doesnt work now. So is there any report i have to run so as to update the changes from OM to PA.
    Thanks,
    Raj..

    Hi Soniya,
    Please check if the OM to PA integration is set in the table T77s0. You can check this through the transaction sm30.
    Or you can use the img node Organizational Management -> Integration -> Integration with Personnel Administration -> Set Up Integration with Personnel Administration.
    Also try using the report RHINTE10  and RHINTE30 to correct the entries in PA.
    You can execute these from transaction se38.
    Regards,
    Santosh

Maybe you are looking for