Poland Infotype 0002 - standard screen

Hi,
In infotype 0002 there are many standard screens for countries for example Japan has screen 2022. Is there a standard screen for Poland for infotype 0002 or should I use 2000 or 2044?
Regards,
Warren.

you can use one of these 2 or copy into some new screen and use

Similar Messages

  • Adding a custom field in a sap standard screen in pa30 for an infotype.

    Hi to all..
    i'm in a requirement to add a custom field in a standard screen of pa30. for the infotype 0442.
    I googled up.. but i was not getting proper solution for it.. can any one provide a solution for it..
    With regards.
    Aahbha.

    Hello Sirs,
    Step by step instructions on:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/4f/d52552575e11d189270000e8322f96/frameset.htm
    The below thread provide more info on how to create an infotype from scratch, but this is just for the reference:
    add custom fields to standard infotype
    Regards,
    Bentow.

  • Sending the enhanced Infotype 0002 outside SAP via an IDOC

    Hello Friends,
    We have added couple of Z fields to the standard 0002 Iinfotype table PA0002.
    I can see the custom fields in the trans : PA30 screen for infotype 002.
    Now, we want to send these custom fields value outside SAP via an IDOC.
    Here are the steps I followed :
    I created a Z Segment in an extended idoc with the structure PA0002.
    I went in transaction PM01 for Infotype 0002 and added the above created Z segment as a 2nd IDOC segment.
    In transaction PA30 for 002, I made changes to the custom field value for a person 12039.
    Created an idoc via BD21.
    IDOC generated with the Z Segment but it doesn't contain any  Z  custom fields.
    Which step am I missing here? Do I have to have a user-exit or BADI to achieve this OR can it be done without writing any code?
    Basically I
    I will really appreciate your help.
    Regards,
    Pooja Pandey

    Pooja,
    you need to fill each field manually.
    check this code i am filling ZHCMS_PI_SEMENT
    data: sgmnt_e1pityp type e1pityp.
      field-symbols: <wplog> type any.
      field-symbols: <wplog1> type any.
      data: ixxxx type e1pityp, iyyyy type e1plogi,sgmnt_hcms_pi type zhcms_pi_segment,wa_idoc_data_x type edidd, ls_idoc_data type edidd.
      data: lv_p0001 type standard table of p0001 ,lv_p0002 type standard table of p0002 ,lv_p0007 type standard table of p0007 .
      data: lv_p0521 type standard table of p0521 ,lv_p0710 type  standard table of p0710 ,lv_p2001 type  standard table of p2001 .
      data: ls_p0001 type  p0001,ls_p0002 type p0002,ls_p0007 type p0007 ,ls_p0521 type  p0521 ,ls_p0710 type  p0710 ,ls_p2001 type p2001 .
      data: row_index type sy-tabix,del_index type sy-tabix.
      data: lcx_root type ref to cx_root.
    fILL THE E1PITYP
    try.
    Keep the segments which have changed date greater than last run date in update mode
        read table idoc_data into wa_idoc_data_x with  key segnam = 'E1PITYP'.
        assign wa_idoc_data_x-sdata to <wplog> casting type e1pityp.
        ixxxx = <wplog>.
        loop at idoc_data into wa_idoc_data_x where segnam = 'E1PLOGI'.
          row_index = sy-tabix + 1.
          assign wa_idoc_data_x-sdata to <wplog1> casting type e1plogi.
          iyyyy = <wplog1>.
          sgmnt_e1pityp-plvar = ixxxx-plvar.
          sgmnt_e1pityp-otype = ixxxx-otype.
          sgmnt_e1pityp-objid = iyyyy-objid.
          sgmnt_e1pityp-infty = '0001'.
          sgmnt_e1pityp-begda = ixxxx-begda.
          sgmnt_e1pityp-endda = ixxxx-endda.
          clear ls_idoc_data.
          ls_idoc_data-segnam = 'E1PITYP'.
          ls_idoc_data-sdata = sgmnt_e1pityp.
          insert ls_idoc_data into idoc_data index row_index.
    APPEND t_idoc_data .
    Get the ZZSWISSREID
          sort lv_p0001 by begda descending.
          read table lv_p0001 into ls_p0001 index 1.
          sgmnt_hcms_pi-zzswissreid = ls_p0001-zzswissreid.
    Get the custom data from IT0002
          sort lv_p0002 by begda descending.
          read table lv_p0002 into ls_p0002 index 1.
          sgmnt_hcms_pi-zzglobalid = ls_p0002-zzglobalid.
          sgmnt_hcms_pi-zzsource_id = ls_p0002-zzsource_id.
          sgmnt_hcms_pi-zzlegacy_emp_id = ls_p0002-zzlegacy_emp_id.
          ls_idoc_data-segnam = 'ZHCMS_PI_SEGMENT' .
          ls_idoc_data-sdata = sgmnt_hcms_pi.
          row_index = row_index + 1.
          insert ls_idoc_data into idoc_data[] index row_index.
          clear : lv_p2001[] , lv_p0001[] , lv_p0002[] , lv_p0710[] ,lv_p0007[], lv_p0521[], ls_p2001 , ls_p0001 , ls_p0002 , ls_p0710 ,ls_p0007, ls_p0521 .
    APPEND t_idoc_data.
        endloop.
    Thanks
    Bala Duvvuri

  • Missing of Gender field in infotype 0002

    Hi All,
    Recently we have upgraded the patch level from 0026 to 0037.  The problem is I am unable to see the Gender field(GESCH)  in Infotype 0002. I have checked in Std screen of P0002 there also i am unable to find the field. But in the database table the field is available.Previously it was available in infotype 2.
    Due to the missing of  standard field Gender (GESCH) in Infotype 0002 I am unable to upload the data and also unable to take the std copies of PF form 5 and form 10 where system is automatically taking the Gender column as F(female) instead of M(Male).As per the standard code it checks this field GESCH for "1" and outputs gender as "M" if "1" and "F" otherwise.
    Any help in this regard will be highly appreciated.
    Regards,
    Anjenaya Prasad

    Hi,
    Activate the field in the table T588M Q0002-GESCH to standard.
    Path: PM->PA->Customizing user interfaces-> Change screen Modifications
    Regards
    Devi

  • Calling infotype 0002 in ALV  report for showing employee photo

    Hi all,
    The requirment from business side is a report in which employees personal data shuold be shown with employee photo, I had tried for employee photo in ALV report but it didnt sucessed, then I went for other solution like calling transaction in ALV report.
    In this case I am calling Infotype 0002 but the issue is that the transaction PA20 is coming with PERNR but I am not able to go directlly to infotype which shows employee Photo,please suggest any solution.
    Thaks.
    JAY

    Hi Jay,
    It is possible. Please refer the syntax for the CALL TRANSACTION
    CALL TRANSACTION ta { [AND SKIP FIRST SCREEN]
                        | [USING bdc_tab [bdc_options]] }.
    You can do a recording till the required page comes & call the transaction accordingly. Hope, you are aware about the same.
    For example, I just had a solution to go to the roles tab in the user profile and I did as below:
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPLSUU5'.
        wa_bdcdata-dynpro   = '0050'.
        wa_bdcdata-dynbegin = k_ok.
        APPEND wa_bdcdata TO it_bdcdata.
        CLEAR wa_bdcdata.
        wa_bdcdata-fnam  = 'BDC_CURSOR'.
        wa_bdcdata-fval   = 'USR02-BNAME'.
        APPEND wa_bdcdata TO it_bdcdata.
        CLEAR wa_bdcdata.
        wa_bdcdata-fnam  = 'USR02-BNAME'.
        wa_bdcdata-fval   = g_value.
        APPEND wa_bdcdata TO it_bdcdata.
        CLEAR wa_bdcdata.
        wa_bdcdata-fnam  = 'BDC_OKCODE'.
        wa_bdcdata-fval   = 'SHOW'.
        APPEND wa_bdcdata TO it_bdcdata.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPLSUU5'.
        wa_bdcdata-dynpro   = '0100'.
        wa_bdcdata-dynbegin = k_ok.
        APPEND wa_bdcdata TO it_bdcdata.
        CLEAR wa_bdcdata.
        wa_bdcdata-fnam  = 'BDC_OKCODE'.
        wa_bdcdata-fval   = '=ACTG'.
        APPEND wa_bdcdata TO it_bdcdata.
        g_opt-dismode = 'E'.
        g_opt-defsize = k_ok.
    *** if user click on the User Name, call SU01
        CALL TRANSACTION 'SU01' USING it_bdcdata
                    OPTIONS FROM g_opt.
    Regards,
    Selva K.

  • Need some help in creating Search Help for standard screen/field

    I need some help in adding a search-help to a standard screen-field.
    Transaction Code - PP01,
    Plan Version - Current Plan (PLVAR = '01'),
    Object Type - Position ( OTYPE = 'S'),
    Click on Infotype Name - Object ( Infotype 1000) and Create.
    I need to add search help to fields Object Abbr (P1000-SHORT) / Object Name (P1000-STEXT).
    I want to create one custom table with fields, Position Abb, Position Name, Job. Position Abb should be Primary Key. And when object type is Position (S), I should be able to press F4 for Object Abb/Object Name fields and should return Position Abbr and Position Name.
    I specify again, I have to add a new search help to standard screen/field and not to enhance it.
    This is HR specific transaction. If someone has done similar thing with some other transation, please let me know.
    There is no existing search help for these fields. If sm1 ever tried or has an idea how to add new search help to a standard screen/field.
    It's urgent.
    Thanks in advace. Suitable answers will be rewarded

    Hi Pradeep,
    Please have a look into the below site which might be useful
    Enhancing a Standard Search Help
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/daeda0d7-0701-0010-8caa-
    edc983384237
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee93446011d189700000e8322d00/frameset.htm
    A search help exit is a function module for making the input help process described by the search help more flexible than possible with the standard version.
    This function module must have the same interface as function module F4IF_SHLP_EXIT_EXAMPLE. The search help exit may also have further optional parameters (in particular any EXPORTING parameters).
    A search help exit is called at certain timepoints in the input help process.
    Note: The source text and long documentation of the above-specified function module (including the long documentation about the parameters) contain information about using search help exits.
    Function modules are provided in the function library for operations that are frequently executed in search help exits. The names of these function modules begin with the prefix F4UT_. These function modules can either be used directly as search help exits or used within other search help exits. You can find precise instructions for use in the long documentation for the corresponding function module.
    During the input help process, a number of timepoints are defined that each define the beginning of an important operation of the input help process.
    If the input help process is defined with a search help having a search help exit, this search help exit is called at each of these timepoints. If required, the search help exit can also influence the process and even determine that the process should be continued at a different timepoint.
    timepoints
    The following timepoints are defined:
    1. SELONE
    Call before selecting an elementary search help. The possible elementary search helps are already in SHLP_TAB. This timepoint can be used in a search help exit of a collective search help to restrict the selection possibilities for the elementary search helps.
    Entries that are deleted from SHLP_TAB in this step are not offered in the elementary search help selection. If there is only one entry remaining in SHLP_TAB, the dialog box for selecting elementary search helps is skipped. You may not change the next timepoint.
    The timepoint is not accessed again if another elementary search help is to be selected during the dialog.
    2. PRESEL1
    After selecting an elementary search help. Table INTERFACE has not yet been copied to table SELOPT at this timepoint in the definition of the search help (type SHLP_DESCR_T). This means that you can still influence the attachment of the search help to the screen here. (Table INTERFACE contains the information about how the search help parameters are related to the screen fields).
    3. PRESEL
    Before sending the dialog box for restricting values. This timepoint is suitable for predefining the value restriction or for completely suppressing or copying the dialog.
    4. SELECT
    Before selecting the values. If you do not want the default selection, you should copy this timepoint with a search help exit. DISP should be set as the next timepoint.
    5. DISP
    Before displaying the hit list. This timepoint is suitable for restricting the values to be displayed, e.g. depending on authorizations.
    6. RETURN (usually as return value for the next timepoint)
    The RETURN timepoint should be returned as the next step if a single hit was selected in a search help exit.
    It can make sense to change the F4 flow at this timepoint if control of the process sequence of the Transaction should depend on the selected value (typical example: setting SET/GET parameters). However, you should note that the process will then depend on whether a value was entered manually or with an input help.
    7. RETTOP
    You only go to this timepoint if the input help is controlled by a collective search help. It directly follows the timepoint RETURN. The search help exit of the collective search help, however, is called at timepoint RETTOP.
    8. EXIT (only for return as next timepoint)
    The EXIT timepoint should be returned as the next step if the user had the opportunity to terminate the dialog within the search help exit.
    9. CREATE
    The CREATE timepoint is only accessed if the user selects the function "Create new values". This function is only available if field CUSTTAB of the control string CALLCONTROL was given a value not equal to SPACE earlier on.
    The name of the (customizing) table to be maintained is normally entered there. The next step returned after CREATE should be SELECT so that the newly entered value can be selected and then displayed.
    10. APP1, APP2, APP3
    If further pushbuttons are introduced in the hit list with function module F4UT_LIST_EXIT, these timepoints are introduced. They are accessed when the user presses the corresponding pushbutton.
    Note: If the F4 help is controlled by a collective search help, the search help exit of the collective search help is called at timepoints SELONE and RETTOP. (RETTOP only if the user selects a value.) At all other timepoints the search help exit of the selected elementary search help is called.
    If the F4 help is controlled by an elementary search help, timepoint RETTOP is not executed. The search help exit of the elementary search help is called at timepoint SELONE (at the
    F4IF_SHLP_EXIT_EXAMPLE
    This module has been created as an example for the interface and design of Search help exits in Search help.
    All the interface parameters defined here are mandatory for a function module to be used as a search help exit, because the calling program does not know which parameters are actually used internally.
    A search help exit is called repeatedly in connection with several
    events during the F4 process. The relevant step of the process is passed on in the CALLCONTROL step. If the module is intended to perform only a few modifications before the step, CALLCONTROL-STEP should remain unchanged.
    However, if the step is performed completely by the module, the following step must be returned in CALLCONTROL-STEP.
    The module must react with an immediate EXIT to all steps that it does not know or does not want to handle.
    Hope this info will help you.
    ***Reward points if found useful
    Regards,
    Naresh

  • Employee photo upload in portal and to be saved in infotype 0002

    Hi Everyone,
           I got an requirement where in ESS Portal, through "Change Own Data" link, employee is uploading his photo and it has to be saved in infotype 0002. Below are the doubts i have,
    1. There is no field for photo in infotype 0002, so how it will be saved in 0002.
    2. After uploading and clicking preview button, error was raising saying 'Error when archiving the photo'.
    3. I seen in many forums that the employee photo is visible from PA30. how it will be visible in that tcode ?

    Hi  Chris McNarney,
          Sorry for long delay for replying.. According to you,
    1. I checked the service under /default_host/sap/bc/conentserver/ it was activated and moreover below is the logon data,
            Client           500
         User             XXXXXX
         Language
         Password Status  Set
    and what is the use of this logon data..
    2. According to your link [https://wiki.sdn.sap.com/wiki/display/ERPHCM/Add%20Employee%20Photo%20on%20Infotype%200002?showChildren=false|https://wiki.sdn.sap.com/wiki/display/ERPHCM/Add%20Employee%20Photo%20on%20Infotype%200002?showChildren=false],
    there it has  4.7 version in that they told to create A2 repository with Tcode: OAC0 with details,,
         While creating the repository, keep the Document Area blank, Storage type as R/3 database, Rep. Sub-type will appear as Normal by default, Version No. as 0046 and in Contents table put 'SDOKCONT1' as the table name.
        With that screen im am not able to find table name field to put 'SDOKCONT1' as input and moreover SAP system database is there instead of getting R/3 database for storage type. Screen detilas below,
    Content Rep.    A2                               Active
    Description
    Document Area
    Storage type
    Version no.     0046   Content Server version 4.6 as the table name.

  • PNP standard screen Reporting period

    Hi All,
    The PNP standard screen has a parameter Reporting period.
    Could anyone please explain that if I select a Key date then what will this date be matched against in the database? Will it be the begda of an infotype?
    Also, same with selecting "other period" what would this range be checked against?
    I would appreciate your help.
    Regards,
    ~Mark

    Hi,
    When you select Key Date, all the employee records fetched which valid as on the Key date (i.e. All the records with BEGDA < KEYDATE < ENDDATE).
    Similarly for other field, employee records are fetched as on valid on the range given in the 'other period'.
    Hope this helps,
    Shrinivas

  • Creating / updating Custom infotype with different screen

    Hi All,
    I have created custom infotype having different screen for different subtype(1,2).
    From Subtype 1, indotype is automatically updated as it is a standard program. But for subtype 2 i am using HR_INFOTYPE_OPERATION for updating the record which is ending with error, as employee which i am trying to update is already locked by me only through PA30. So this function module ends with Complex error. Please suggest how to update the infotype with subtype 2.
    Thanking you..
    Best regards
    Akshay

    Hi All,
    I have created custom infotype having different screen for different subtype(1,2).
    From Subtype 1, indotype is automatically updated as it is a standard program. But for subtype 2 i am using HR_INFOTYPE_OPERATION for updating the record which is ending with error, as employee which i am trying to update is already locked by me only through PA30. So this function module ends with Complex error. Please suggest how to update the infotype with subtype 2.
    Thanking you..
    Best regards
    Akshay

  • Infotype 0002 issue

    hi,
    i have added one field in infotype 0002 , by pm01 . it is not getting displayed in pa30 transaction . i have already activate module pool  and layout editor plz tell me what to do .

    Please check the screen number of the module pool. In which screen you have added the new field? Is the same scrren is being used by PA30 screen. I am sure there is some mismatch in screen.
    Regards,
    Sandip

  • Abap hr standard screen question

    Hi,
    I want to learn if it is possible to create a screen at which we can get datas as we get from standard screens at hr.
    I mean can we get data directly as we get by using 'get pernr' without using where condition at a infotype which we created.
    Edited by: Begum Al on Aug 11, 2008 3:50 PM

    Yes, you just need to link your program to the logical database PNP. Look at [Reporting in Human Resource Management|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/HRREPORTING/HRREPORTING.pdf] and [Report Programming in HR|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_PROGRAMM.pdf] and [Programming Utilities for the Logical Databases PNP and PAP|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_RMAC.pdf], also do some [search at sdn.sap.com|https://www.sdn.sap.com/irj/sdn/advancedsearch?query=hr+report&cat=sdn_all]
    Regards

  • Issue adding records to Infotype 0002

    Hi All,
    I am trying to insert records into Infotype 0002. I am using HR_INFOTYPE_OPERATION to do this. It works fine for all the employees but fot the ones who have Reference Personnel numbers. The system lets me to add the record to those employees through PA30 online or through BDC program with a warning message "No record with the same key for personnel number xxxxxxx",  but if I use the FM HR_INFOTYPE_OPERATION or HR_MAINTAIN_MASTERDATA, it sometimes gives me hard error message " The Social Insurance number already assigned to another employee" in the foreground and when executed in background I get a short dump with exception " CX_HRPA_INVALID_BUFFER_ACCESS".
    I debuged the standard code and the exception occurs in Include UP50RU02 in method IF_HRPA_MASTERDATA_BUFFER~INSERT.
    Short dump:
    The exception 'CX_HRPA_INVALID_BUFFER_ACCESS' was raised, but it was not caught
      anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
      'CL_HRPA_MASTERDATA_BUFFER=====CP' has to be
    terminated.
    Please let me know if I am doing something wrong.
    Thanks,
    Danny.

    Hi Daniel,
    I would not worry about using FM 'HR_INFOTYPE_OPERATION' or 'HR_MAINTAIN_MASTERDATA' for the purpose of inserting PA infotype records for employees. I had developed a generic module last year to insert any PA infotype record which will use the standard PA business logic framework i.e. include all standard checks and validation, calls all Exits/BAdIs before inserting the record as it would when you are saving the infotype record via PA30. I basically created a wrapper FM to simplify the calling of some other standard FMs. Use it if you like (and if it works in your system keeping in mind config is different in every system) but please do handle all the Exceptions after the call (by reading the Message Handler Interface IF_HRPA_MESSAGE_HANDLER) to confirm there was no data inconsistency or other problems at the time of the update. Below is the sample code:
    The generic customer Function Module
    FUNCTION zpa_insert_any_infty_record.
    *"*"Local Interface:
    *"  IMPORTING
    *"     VALUE(IS_PNNNN) TYPE  ANY
    *"     REFERENCE(IT_TEXT_TAB) TYPE  HRPAD_TEXT_TAB OPTIONAL
    *"     REFERENCE(IV_NO_AUTH_CHECK) TYPE  BOOLE_D DEFAULT SPACE
    *"     REFERENCE(IV_LOCK) TYPE  SPRPS DEFAULT TRUE
    *"  EXPORTING
    *"     REFERENCE(EIF_MESSAGE_HANDLER) TYPE REF TO
    *"        IF_HRPA_MESSAGE_HANDLER
    *"     REFERENCE(EV_OK) TYPE  BOOLE_D
    *"  EXCEPTIONS
    *"      EX_PERNR_LOCKED
    * FUNCTION...... ZPA_INSERT_ANY_INFTY_RECORD                           *
    * FUNCTION GROUP.ZPA_FG_EMP_LEAVE_BOOKING                              *
    * TITLE......... Insert any PA infotype record for an employee         *
    * AUTHOR........ Sougata Chatterjee                                    *
    * DATE WRITTEN.. 23/08/2010                                            *
    * SAP RELEASE... ECC 6.0                                               *
    * SPECIFICATION. N/A - Reuseable Object                                *
    * =====================================================================*
    * DESCRIPTION... This function is a generic module that will insert    *
    *                a PA infotype record into the employee master data as *
    *                per the import structure IS_PNNNN. This module wil be *
    *                particularly useful when requirement is to create     *
    *                other infotype records for the same employee within a *
    *                User-Exit or a BAdI.                                  *
    * ASSUMPTIONS... Infotype record to be updated is a PA Infotype.       *
    * =====================================================================*
    * MODIFICATION HISTORY                                                 *
    * Date       Userid       Change No & Description                      *
      DATA:
        lif_msg_handler  TYPE REF TO if_hrpa_message_handler,
        lo_msg_handler   TYPE REF TO cl_hrpa_message_list.
    * instantiate the message handler object
      CREATE OBJECT lo_msg_handler.
    * assign a reference to a rereference variable using the CAST operation
      lif_msg_handler ?= lo_msg_handler.
    * insert the infotype record into the employee master data
      PERFORM insert_infotype USING    is_pnnnn
                                       it_text_tab
                                       iv_no_auth_check
                                       iv_lock
                                       lif_msg_handler
                              CHANGING ev_ok.
    * pass back the message handler to the calling program if it was requested
      CHECK eif_message_handler IS REQUESTED.
      eif_message_handler = lif_msg_handler.
    ENDFUNCTION.
    For some reason I couldn't format the subroutine code here in SDN as it is scrambling the whole page but you could use the link here to find the [subroutine code|http://www.mediafire.com/file/9923qui7dm4xqpg/Form%20Insert_Infotype.html] and an [example code|http://www.mediafire.com/file/ihg83agkf0mbc9k/z_calling_program.html] for the program calling this FM including exception handling etc.
    Let me know if the links are not working...I'm happy to email them to you if you want.
    Hope this helps.
    Cheers,
    Sougata.

  • Infotype 0002 Amendment

    How do everyone
    We have just created a new client 333 on our dev machine. We are currently
    using the existing 010 client.
    When I look at infotype 0002 via PA20 on the new client 333 I can see that
    there are certain customised ZZ fields missing.
    I created a dummy transport in 010 to include the table definition CI_P0002,
    the report source code and the screen.
    I then imported this transport via SCC1 into the new client 333.
    It ran successfully, but the fields are still missing from PA20.
    Does anybody know if I am doing anything wrong????
    Cheers
    Andy

    Hi again,
    1. The procedure is a little tricky.
    2. To confirm, just goto se09, and check your request objects.
       The MP000200 entries must be there.
      (If the procecudure was done 100% correct)
    3. Just make sure, in PM01,
        u press the BUTTON in app toolbar
       "INCLUDE IN REQUEST"
        and then save button.
       (Only when we do this step, the etnries get included in request)
    regards,
    amit m.

  • Infotype 0002 problem

    Hi All,
    I have couple of problems in infotype 0002.
    1. field ANZKD(number of children) is missing in infotype.
    2. marital status key in structure P0002 and in dynamic actions is FAMST but in Infotype marital status key is FATXT.
    I am using country grouping 10 for USA. Is there different screens available? If yes how to change screen.
    We have done no screen exits so far!!
    Thanks in Advance.
    Vivek.

    Hi,
    You should work on view T588M via t-code sm30.
    You can either change screen or control the screen fields there.
    1. ANZKD is alreay there in 2010, just choose the entry to set it to the value other than hide.
    MP000200     2000               10     2010     0
    2. Just go ahead with FAMST, FATXT is the text display on screen. But FAMST stored in database.
    Hope helps,
    Chen Jian

  • Need to upload employee photos against infotype 0002

    Hi,
    We have an urgent reqirement to load the photos of all the employees agianst the infotype 0002 which need to be accesed by the employees and managers via enterprise portal.
    Can anybody help me....
    Thanks in advance
    Krishna

    The steps provided you are very appropiate , but you can also check the following settings incase you dnt achieve your requirements.
    Q. How to attached the Photo in IT0002
    1.Create a number range for SAP Archive Link :
    IMG>Basis Components>Basis Services>SAP Archive Link>Basic Settings>Maintain number ranges.
    Tcode OANR. Create range 01 from 0000000001 to 9999999999 without the external number flag.
    2.Document type HRICOLFOTO must exist with document class JPG.
    IMG>Basis Components>Basis Services>SAP Archive Link>System Settings>Maintain document types.
    Table TOAVE, Tcode OAC2.
    3.Document type HRICOLFOTO must be linked to object type PREL and IT0002.
    IMG>Personnel Management>Personnel Administration>Tools>Optical Archiving>Set up Optical Archiving in HR.
    View V_T585O, no Tcode. In all three columns there ara minuses, don’t put a flag in the check box.
    4.Check which content repository (Archive) is linked to document type HRICOLFOTO and object type PREL.
    IMG>Basis Components>Basis Services>SAP Archive Link>Basic Settings>Maintain Links.
    Table TOAOM_C, Tcode OAC3
    5.Create this content repository with storage type FILE archive.
    IMG>Basis Components>Basis Services>SAP Archive Link>Basic Settings>Maintain content repositories.
    Tcode OAC0
    Storage type FILE archive can be attained by clicking on the field Storage type and clicking somewhere else in the screen with the right mouse button. Choose Possible entries and only then you get a list of all values. FILE Archive is entry number 08. Choose Version no. 0031 and Archive path something (e.g. C:\).
    6.Link photo to personnel number.
    Menu>Tools>Business Documents>Miscellaneous>Stored Documents. Tcode OAAD.
    Click on the Create button. Business object PREL and Docyment type HRICOLFOTO. Click on create (fill in the right personnel number in the pop up and click Continue). Choose the photo (as a JPG file) from the place where it is saved (e.g. hard disk). SAP will notify that the Stored Document was created succesfully. Photo is visible via PA10, PA20, PA30, PA40. Double-click to magnify photo.
    To delete archived document :
    Tcode OAAD, click Find. In docyment type field select HRICOLFOTO and after execute you get a list of all documents. Select appropriate document and click on delete icon.
    thnkx
    bhanu

Maybe you are looking for