Infotype Creation - FM HR_INFOTYPE_OPERATION

How do everyone,
I am using the FM HR_INFOTYPE_OPERATION to create a recurring payment infotype.
Everything is working fine. However, when the infotype is created it is created against the
master cost centre. This is ok for some people but not all.
If you create the infotype through PA30 you have the option to 'Maintain Cost Assignment'
which displays a pop up box and allows the user to enter a different cost centre.
Does anybody know how this can be replicated if possible using HR_INFOTYPE_OPERATION
or is there another FM to use???
Any help much appreciated.
Andy

try to record a batch input session and create the infotype with batch input instead of HR_INFOTYPE_OPERATION
otherwise you could maintain the tables for cost distribution,
view ASSOB_HR (tables ASSOB, ASSHR and PDSNR)

Similar Messages

Updating infotype 0041 using HR_INFOTYPE_OPERATION?

Hi All:
How do we update the dates in infotype 0041 using HR_INFOTYPE_OPERATION? lets say we have 6 dates populated in 41 and we another employee has 9 dates populated. We are reading these records and need to update the dates for all the employee records.
Thanks
Venkata

Hi Venkata,
What you can do is use the HR_INFOTYPE_OPERATION in Change or MOD(Modify) mode i.e.
pass 'MOD' in operation parameter.
Your recordnumber parameter should have the sequence number from infotype record you are updating (field SEQNR). All other parameters should be as it is had been for INS or insert operation.
Regards.

Pa custom infptype and org management infotype creation

hi experts,
pa custom infptype and org management infotype creation
steps are same or not.
If any difference b/w both plz give me step by step procedure.
Regards,
Sandeep

PA infotype will create in PM01 everything we need fill from PM01.
OM infotype
:- 1. we need to create HRI9XXX structure.
2. PPCJ t-code u can create from this t-code.
PA INFOTYPE CREATION
1) Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the `Employee Infotype' radio button.
4) Select the `PS Structure Infotype'.
5) Click on Create. A separate table maintenance window appears.
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on `All' push button. It takes a few moments.
10) Click on `Technical Characteristics' . Infotype list screen appears
11) Click on `Change'(pencil) button
12) Select your Infotype and click on `Detail' (magnifying glass) button
13) Give `T591A' as subtype table
14) Give `T591S' as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on `Infotype Characteristics' . Infotype list screen appears
18) Click on `Change' (pencil) button
19) Click on `New Entries'
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype's infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirement.
25) In the PM01 initial screen.Select `Screen' radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select `Layout Editor' and click `Change'.
27) Screen default layout appears.here you can design/modify the screen.. change the attributes of the fields. etc.
28) Save and activate. (Don't forget to `Activate at every level)
Edited by: sapabap229 on Aug 30, 2010 11:19 AM

Organization Management/ Personnel Development Infotype Creation

Hi Experts,
Like Personnel Administration Infotype 9xxx,
xxx- series.which are created using PM01 Transaction.
What is the approach to create Organization Management/ Personnel Development Infotype Creation.
Do they have series 9xxxx.
Please advice.
Thanks in Advance.
Regards,
IFF

Hi irfan,
Have u checked this thread?Have a look at the pdf mentioned in the thread.
how to create OM Infotype
Check ur gmail as well.
Regards,
Manoj.

PD Infotype creation

hello all,
can anyone guide me on PD infotype creation?
With all neccesary steps or links for the same,
Thanks in advance,
Yashvi

Hi,
This was posted by some one else. I do not remeber the link. The following is the procedure
Enter the transaction code PPCI
Enter a four digit infotype number (9nnn) and an infotype name.
Select Field Infotype
Choose Infotype Create.
Choose Check environment to maintain the required entry in table T777I (Infotypes per object type).
Choose the Entry 'T777I' under the list of 'Table Entries' (This list is produced when you choose 'Check' on the First screen of the Transaction PPCI.
Press the 'Change' button and you will be taken to the 'Maintain Table Views' Transaction (SM30).
Press the Maintain button.
From the list of Infotypes locate the custom infotype created and select the entry for that.
Click on the 'Time Constraint' folder appearing on the left hand corner of the screen.
The screen for Change View Time Constraint would appear.
In the object type field put in: O,P,S whatever is relevant to your requirement.Also add the time constraint.
Save it and double click on the 'Infotypes per object type' folder (on the left hand side again).
Create a new entry here for your infotype and save it.
Regards
Vick

Error while modifying HR infotype PA0105 using HR_INFOTYPE_OPERATION

Hello All,
I am not able to modifying the infotype PA0105.
Currently I am using the FM HR_INFOTYPE_OPERATION.
But I am not able to modify the record.
Has anyone faced any such situation...
Please help..!!
Useful pointers will be appreciated...
Thanks & Regards,
Tarun Gambhir

Hope this helps you out...
      C_INS   LIKE PSPAR-ACTIO VALUE 'INS',
      W_000-PERNR = T_SAIDA-PERNR.
      W_000-INFTY = C_0000.
      W_000-ENDDA = C_DATA.
      W_000-BEGDA = T_PA0000-BEGDA.
      W_000-AEDTM = SY-DATUM.
      W_000-UNAME = SY-UNAME.
      W_000-MASSN = C_16.
      W_000-MASSG = S_MASSG-LOW.
      W_000-STAT1 = SPACE.
      W_000-STAT2 = C_3.
      W_000-STAT3 = C_1.
      W_PSPAR-PERNR = T_SAIDA-PERNR.
      W_PSPAR-INFTY = C_0000.
      W_PSPAR-PLANS = T_P0001-PLANS.
      W_PSPAR-WERKS = T_P0001-WERKS.
      W_PSPAR-PERSG = T_P0001-PERSG.
      W_PSPAR-PERSK = T_P0001-PERSK.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          INFTY            = C_0000
          NUMBER           = T_SAIDA-PERNR
          LOCKINDICATOR    = SPACE
          VALIDITYEND      = C_DATA
          VALIDITYBEGIN    = V_BASE
          RECORD           = W_000
          OPERATION        = C_INS
          SECONDARY_RECORD = W_PSPAR
        IMPORTING
          RETURN           = T_RET_FUNC                     "#EC *
          KEY              = T_KEY.                         "#EC *
Greetings,
Blag.

Custom infotype creation issue

Hi Experts,
I have a requirement to create a custom infotype based on certain conditions. But there is a problem while saving data in the infotype. The infotype is populated from another infotype automatically through dynamic actions.
But while saving the data for the first time it happens as per the requirements and data gets saved properly.
But when the data is saved for the second time for the same pernr , the previous data is over written even though the new record starts with a different begin data.Also i have created the infotype with time constraint '1'.
can you please let me know if i am missing anything while creating or is this a logic issue .? all the logic has been coded in the flow logic part of the screen.
also if i dont save the data in the infotype it does not pop up any message like 'data not saved' which usually happens with every infotype. Please clarify me on this as well...
Thanks,
Raj Thilak.

Hi,
Check the logic how it is updating the custom infotype . I think it is nothing to do with creation of custom info type
Regards
Krishna

Check before an infotype operation (PA) / HR_INFOTYPE_OPERATION

Hi,
In my latest project there is a requirement to simulate the HR_INFOTYPE_OPERATION (or other possibilities to update the PA* infotypes). The main meaning of the project is in robust customer customization, which translates to dynamic abap webdynpro views with data from the infotypes. Person fills those forms and sends the "personal document" for processing (creating entries in customer Z* namespace). Just after that a different user can pick the "personal document" and can process it - that is the part where it comes to the infotypes filling (HR_INFOTYPE_OPERATION, batch-inputs, direct updates etc.).
Now requirement is to implement checks also in the creating of the "personal document" itself, before saving it into customer (Z*) tables. How could that be achieved? One way would be using HR_INFOTYPE_OPERATION with nocommit = 'X' and after all operations call of ROLLBACK WORK, initializing buffers etc. However whole concept of using HR_INFOTYPE_OPERATION is in locking the personal number before the call. User which only creates the "personal document" should not lock the personal number - as this part should be independent on other processes, taken in SAP standard HR tables / transactions themselfs.
I did not find any kind of checking mechanism ignoring the person-locking concept, but with full logic that the corresponding infotype expects. There should be are all kind of operations supported (insert, copy, delimit...).
I underline that the customer is at a low support package (< EH5) and the decoupling infotypes concept is useless here.
Thanks for any advice.

Hi Surya,
Enhancement project PBAS0001which contains those includes is obsolete in terms of detached infotype framework.
The following enhancements will work for a decoupled infotype:
BAdIs:
HRPAD00INFTYBL Enhancement of Business Logic of Standard Infotypes (this is the direct replacement for the enhancement project PBAS0001)
HRPAD00INFTYDB Performing actions after updating (this is the direct replacement for the BAdI HRPAD00INFTY)
HRPAD00INFTYUI BAdI: UI Logic Enhancement
More information you may find here:
IMG Personnel Management->Personnel Administration->Customizing Procedures->Infotypes->Infotypes in Detached Infotype Framework
Under the following IMG nodes:
Enhancements to Business Logic and Updating
Enhancements to UI Logic
Regarding to your questions:
1. If the infotype is decoupled, even the HR_INFOTYPE_OPERATION will call these business checks and time constraint checks. Right ? So, what is the major advantage of moving to HR_ECM_INSERT_INFOTYPE ?
I suppose it has been done to follow the same logic as SAP does in PA-EC component
For example to adjust a salary in ECM SAP uses FM HR_ECM_ACTIVATE_SAL_ADJUSTMENT meanwhile it uses FM HR_ECM_INSERT_INFOTYPE to update IT0008
2. Is there some trick to enable HR_ECM_INSERT_INFOTYPE call the user exits of the Infotype ?
I think there is no standard way to do so...
It is a good idea to follow the standard enhancement concept for decoupled infotypes, at least I see no problems in moving the old enhancement to a new one.
Kind regards,
Sergey

Updating hr infotype pa0305 with 'HR_INFOTYPE_OPERATION'

Hi everyone i'm trying to update hr infotype pa0305 using fm HR_INFOTYPE_OPERATION but it doesn't work maybe using in worng way.
Maybe someone knows how can i use the second structure q0305 passing trough the parameter called "secondary records".
Thanks in advance,

Sorry for the late, the problem was that the part structure of p305 is empty; the part of wage type and amount exactly.
CLEAR lv_return .
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        infty                  = '0305'
        number                 = wa_alvgrid2_error-pernr
        subtype                = ''
        OBJECTID               =
        LOCKINDICATOR          =
       validityend            = wa_alvgrid2_error-endda
       validitybegin          = wa_alvgrid2_error-begda
        RECORDNUMBER           =
        record                 = st_0305
        operation              = 'INS'
        tclas                  = 'A'
        dialog_mode            = '2'
         nocommit               = ' '
        view_identifier        = '15'
        secondary_record       = st_q0305
     IMPORTING
       return                 = lv_return
        KEY                    =.
maybe I am in wrong when I pass the secondary record.

How to Insert Infotype by FM HR_INFOTYPE_OPERATION

Hi,
I am using HR_INFOTYPE_OPERATION FM to insert and update the infotype.
I am able to update the data but unable to insert.
When I use MOD operation the data is updated successfully but for INS operation it is again rather than inserting record it is updated again.
Please see the following sample code .
REPORT ZHR_UPDATE_INFOTYP.
DATA: G_RETURN LIKE BAPIRETURN1,
      IT_P0003 LIKE P0003,
      G_SUBRC TYPE SY-SUBRC.
data: l_infty type prelp-infty value '0003',
      l_infty_tab type table of pa0003 with header line,
      wa_infty type pa0003.
PARAMETER: P_PERNR LIKE PA0003-PERNR,
          P_MODE TYPE CHAR1.
start-of-selection.
IT_P0003-INFTY = '0003'.
CALL FUNCTION 'HR_READ_INFOTYPE'
EXPORTING
TCLAS                 = 'A'
    pernr                 = p_pernr
    infty                 = l_infty
BEGDA                 = '20110905'
   ENDDA                 = '99991231'
BYPASS_BUFFER         = ' '
LEGACY_MODE           = ' '
IMPORTING
SUBRC                 = SUBRC
TABLES
    infty_tab             = l_infty_tab
EXCEPTIONS
INFTY_NOT_FOUND       = 1
read table l_infty_tab index 1 into wa_infty.
CLEAR:IT_P0003.
IT_P0003 = wa_infty.
IT_P0003-ABWD1 = sy-datum - 1.
PERFORM HR_INFOTYPE_OPERATION USING IT_P0003 P_MODE
                              CHANGING G_RETURN
                                       G_SUBRC.
WRITE:/ 'G_SUBRC',G_SUBRC.
*&      Form HR_INFOTYPE_OPERATION
      text
FORM HR_INFOTYPE_OPERATION USING   P_P0003 STRUCTURE P0003
                                    P_P_MODE
                            CHANGING P_P_RETURN
                                     P_P_SUBRC.
DATA: L_OPERATION TYPE PSPAR-ACTIO,
        L_KEY LIKE BAPIPAKEY.
CASE P_P_MODE.
    WHEN '1'.
      L_OPERATION = 'INS'.
    WHEN '2'.
      L_OPERATION = 'DEL'.
    WHEN '3'.
      L_OPERATION = 'MOD'.
    WHEN OTHERS.
ENDCASE.
*--Performing Infotype Operations Using FM
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
    EXPORTING
      NUMBER = P_P0003-PERNR.
   IMPORTING
     RETURN = P_P_RETURN.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
      INFTY                  = P_P0003-INFTY
      NUMBER                 = P_P0003-PERNR
      SUBTYPE                = P_P0003-SUBTY
OBJECTID               = OBJECTID
LOCKINDICATOR          = LOCKINDICATOR
   VALIDITYEND            = P_P0003-ENDDA
   VALIDITYBEGIN          = P_P0003-BEGDA
RECORDNUMBER           = RECORDNUMBER
      RECORD                 = P_P0003
      OPERATION              = 'INS'
   TCLAS                  = 'A'
    DIALOG_MODE            = '1'
NOCOMMIT               = NOCOMMIT
VIEW_IDENTIFIER        = VIEW_IDENTIFIER
SECONDARY_RECORD       = SECONDARY_RECORD
   IMPORTING
     RETURN                 = P_P_RETURN
     KEY                    = L_KEY .
P_P_SUBRC = SY-SUBRC.
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
    EXPORTING
      NUMBER = P_P0003-PERNR.
   IMPORTING
     RETURN = RETURN.
ENDFORM.                    " HR_INFOTYPE_OPERATION
Any help will be greatly appreciate

not solved ,closed sadly

Updating custom infotype with FM 'HR_INFOTYPE_OPERATION' dumps

Hi All,
While updating a custom infotype 9008 with FM 'HR_INFOTYPE_OPERATION', its giving adump.
Except. CX_HRPA_INVALID_PARAMETER.
I am using DIALOG_MODE as '1'. when I enter a valid field value to that particular field ( mandatory field) on that infotype, it gives dump.
Can you suggest something which will solve this?
Thanks.
Dipti.

Hi,
Here is the dump.
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_HRPA_INVALID_PARAMETER
Date and Time          12.11.2008 07:23:32
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_HRPA_INVALID_PARAMETER' 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_RESOLVE_EXCEPTION=====CP' has to be
terminated.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was not
caught in
procedure "RESOLVE_EXCEPTION" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Invalid parameter EXCEPTION, value
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_HRPA_VIOLATED_PRECONDITION", which was raised in the
program "CL_HRPA_MASTERDATA_FACTORY====CP",
specifically in line 6 of the (include) program
"CL_HRPA_MASTERDATA_FACTORY====CM004".
The cause of the exception was:
Precondition Violated
Missing RAISING Clause in Interface
Program                                 SAPFP50P
Include                                 FP50PE10
Row                                     2,152
Module type                             (FORM)
Module Name                             RESOLVE_EXCEPTION
Trigger Location of Exception
Program                                 CL_HRPA_RESOLVE_EXCEPTION=====CP
Include                                 CL_HRPA_RESOLVE_EXCEPTION=====CM001
Row                                     80
Module type                             (METHOD)
Module Name                             RESOLVE
Source Code Extract
Line
SourceCde
50
message_handler = message_handler.
51
return.
52
53
catch cx_sy_move_cast_error.
54
endtry.
55
END-OF-DEFINITION.
56
57
58
try_to resolve_missing_infty_data    cx_hrpa_missing_infty_data.
59
try_to resolve_missing_authorization cx_hrpa_missing_authorization.
60
try_to resolve_invalid_feature       cx_hrpa_invalid_feature.
61
try_to resolve_unexpected_message    cx_hrpa_unexpected_message.
62
try_to resolve_missing_personid      cx_hrpa_missing_personid.
63
try_to resolve_invalid_infotype_db   cx_hrpa_invalid_infotype_db.
64
try_to resolve_invalid_customization cx_hrpa_invalid_customization.
65
try_to resolve_inconsistent_database cx_hrpa_inconsistent_database.
66
67
68
Just to ensure the macro can be used nowhere else.
69
DEFINE try_to.
70
END-OF-DEFINITION.
71
72
If we can not remap we would like to just re-raise the
73
exception like below like "RAISE EXCEPTION exception.".
74
Unfortunately the kernel will then forget about the
75
original source position.
76
77
So this is the fallback strategy. Calling this method
78
is only allowed if the exception can be resolved. Since
79
this is not the case we indicate a parameter violation.
>>>>>
RAISE EXCEPTION TYPE cx_hrpa_invalid_parameter
81
EXPORTING
82
previous = exception
83
parameter = 'EXCEPTION'.
84
85
ENDMETHOD.
Regards,
Dipti.

Need to delimit infotype pa2006 record 'HR_INFOTYPE_OPERATION'

Hi
I need to delimit infotype record of infotype pa2006 in my own function module.
start date = 01.01.2009
delimit date = 01.01.2010
PA2006
SELECT * FROM PA2006 INTO IT_PA2006
                WHERE PERNR EQ PERNR
                  AND ENDDA LE '99991231'.
ENDSELECT.
IF SY-SUBRC = '0'.
    WA_TAB1-INFTY = '2006'.
    WA_TAB1-FNAME = 'P2006-PERNR'.
    WA_TAB1-FVAL = IT_PA2006-PERNR.
    APPEND WA_TAB1 TO IT_TAB1.
    WA_TAB1-INFTY = '2006'.
    WA_TAB1-FNAME = 'P2006-BEGDA'.
    WA_TAB1-FVAL = IT_PA2006-BEGDA.
    APPEND WA_TAB1 TO IT_TAB1.
    WA_TAB1-INFTY = '2006'.
    WA_TAB1-FNAME = 'P2006-ENDDA'.
    WA_TAB1-FVAL = IT_PA2006-ENDDA.
    APPEND WA_TAB1 TO IT_TAB1.
    WA_TAB1-INFTY = '2006'.
    WA_TAB1-FNAME = 'P2006-KTART'.
    WA_TAB1-FVAL = IT_PA2006-KTART.
    APPEND WA_TAB1 TO IT_TAB1.
    WA_TAB1-INFTY = '2006'.
    WA_TAB1-FNAME = 'P2006-BEGUZ'.
    WA_TAB1-FVAL = IT_PA2006-BEGUZ.
    APPEND WA_TAB1 TO IT_TAB1.
    WA_TAB1-INFTY = '2006'.
    WA_TAB1-FNAME = 'P2006-ENDUZ'.
    WA_TAB1-FVAL = IT_PA2006-ENDUZ.
    APPEND WA_TAB1 TO IT_TAB1.
    WA_TAB1-INFTY = '2006'.
    WA_TAB1-FNAME = 'P2006-ANZHL'.
    WA_TAB1-FVAL = IT_PA2006-ANZHL.
    APPEND WA_TAB1 TO IT_TAB1.
    WA_TAB1-INFTY = '2006'.
    WA_TAB1-FNAME = 'P2006-DESTA'.
    WA_TAB1-FVAL = IT_PA2006-DESTA.
    APPEND WA_TAB1 TO IT_TAB1.
    WA_TAB1-INFTY = '2006'.
    WA_TAB1-FNAME = 'P2006-DEEND'.
    WA_TAB1-FVAL = IT_PA2006-DEEND.
    APPEND WA_TAB1 TO IT_TAB1.
ENDIF.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
    INFTY                  = 2006
    NUMBER                 = PERNR
   SUBTYPE                = IT_PA2006-SUBTY
OBJECTID               =
LOCKINDICATOR          =
   VALIDITYEND            = DATE
   VALIDITYBEGIN          = IT_PA2006-BEGDA
RECORDNUMBER           =
    RECORD                 = IT_TAB1
    OPERATION              = 'MOD'
TCLAS                  = 'A'
DIALOG_MODE            = '0'
NOCOMMIT               =
VIEW_IDENTIFIER        =
SECONDARY_RECORD       =
IMPORTING
   RETURN                 = RETURN
KEY                    =
Why it is not delimit the infotype record. Let me know if any other way to do the same.

Hi friend please do this
"Need to lock the employee before delimiting
CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
    EXPORTING
      number        = px_infty_key-pernr
IMPORTING
       return       = px_bapireturn.
"in the 'HR_INFOTYPE_OPERATION' we need to specify all the details of the infotype what i have mentioned belo
CHECK px_bapireturn-type NA 'AEX'.
CLEAR: px_bapireturn.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'       " Updation of Employee Record
    EXPORTING
     infty                  = px_infty_key-infty
     number                 = px_infty_key-pernr
     subtype                = px_infty_key-subty
     objectid               = px_infty_key-objps
     lockindicator          = px_infty_key-sprps
     validityend            = px_infty_key-endda     "just give the date which you want to delimit with
     validitybegin          = px_infty_key-begda
     recordnumber           = px_infty_key-seqnr
     record                 = px_infty_data
     operation              = lc_mod
     tclas                  = 'A'
     dialog_mode            = '0'
     nocommit               = space
   IMPORTING
     return                 = px_bapireturn
     key                    = px_bapikey.
"Unlock the employee after the operation
CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'       " Unlock the Employee Record
    EXPORTING
      number        = px_infty_key-pernr.
I think will will solve your problem.
Just try it and let me know if you have any issues.
Thanks and Regards,
Sri Hari Anand Kumar

Infotype creation validation

Hi
I need to validate the creation of record in a custom infotype such that the record can be created or exists only when there is a record in another subtype of the same infotype. Please can you advise what would be the best way to achive this?
Regards
Rajeev

Hi Rajeev,
You will have to use USER EXITs for this purpose.
While saving this particular custom infotype of yours you can query the PA9XXX table for the other subtype.
If it exists then you can continue saving or else you can throw an error message.
Please contact your HR ABAP person to look into it.
Hope this helps
-Ajay

About Infotype Creation in ECC6.0

Hi All
Actually my requirement is create a custom infotype and use this infotype in pa30.Buy i am using ecc6.0 version.
I know in 4.7 version only. Try to send me steps about create infotype in ecc6.0 version.it is very urgent requirement.
Regards
hari

Steps to create a HR Infotype:
1) Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the 'Employee Infotype' radio button.
4) Select the 'PS Structure Infotype'.
5) Click on Create... A separate table maintenance window appears...
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on 'All' push button. It takes a few moments.
10) Click on 'Technical Characteristics'. Infotype list screen appears
11) Click on 'Change'(pencil) button
12) Select your Infotype and click on 'Detail' (magnifying glass) button
13) Give 'T591A' as subtype table
14) Give 'T591S' as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on 'Infotype Characteristics' ... Infotype list screen appears
18) Click on 'Change' (pencil) button
19) Click on 'New Entries'
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype's infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirement...
25) In the PM01 initial screen...Select 'Screen' radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select 'Layout Editor' and click 'Change'.
27) Screen default layout appears...here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Don't forget to 'Activate at every level)
Subtype Creation :
Transaction PM01 Goto Subtype Characteristics. Click on Append and then subtype. Enter the name and description of subtype on screen.
Then goto technical Characteristics and maintain the details of subtype there. I.e name of subtype i.e. component name defined in PSnnnn. Subtype table is T591A.
Subty.text tab is T591S and time const tab is T591A.
See:
http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
HR related site:
http://www.sapdevelopment.co.uk/hr/hrhome.htm
Enhancement of Infotype
Check the following
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_INFOTYP.pdf
Infotype Enhancement overview screen
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60a7586d-edd9-2910-68a8-8204303835a1
Regards.

About new infotype creation ?

Hi Experts,
I want to create new infotype in PD.
Will any one help me how to start with.
Before creating infotype whether we need to create structure.
How to create the structure HRI9xxx.
*Please give the step by step procedure and t-code to create theHRI9xxx structure,Pxxxx,any tables like T777 etc.
*Suggest some links to create these things.
*Give step by step procedure to create structure and Infotypes.
Helpfull answers are rewarded for sure.
Thanks,
Sakthi C

Steps to create a HR Infotype:
1) Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the 'Employee Infotype' radio button.
4) Select the 'PS Structure Infotype'.
5) Click on Create... A separate table maintenance window appears...
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on 'All' push button. It takes a few moments.
10) Click on 'Technical Characteristics'. Infotype list screen appears
11) Click on 'Change'(pencil) button
12) Select your Infotype and click on 'Detail' (magnifying glass) button
13) Give 'T591A' as subtype table
14) Give 'T591S' as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on 'Infotype Characteristics' ... Infotype list screen appears
18) Click on 'Change' (pencil) button
19) Click on 'New Entries'
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype's infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirement...
25) In the PM01 initial screen...Select 'Screen' radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select 'Layout Editor' and click 'Change'.
27) Screen default layout appears...here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Don't forget to 'Activate at every level)
Subtype Creation :
Transaction PM01 Goto Subtype Characteristics. Click on Append and then subtype. Enter the name and description of subtype on screen.
Then goto technical Characteristics and maintain the details of subtype there. I.e name of subtype i.e. component name defined in PSnnnn. Subtype table is T591A.
Subty.text tab is T591S and time const tab is T591A.
See:
http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
HR related site:
http://www.sapdevelopment.co.uk/hr/hrhome.htm
Enhancement of Infotype
Check the following
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAXX/PYINT_INFOTYP.pdf
Infotype Enhancement overview screen
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60a7586d-edd9-2910-68a8-8204303835a1
Reward points if uesful.

Infotype Creation - FM HR_INFOTYPE_OPERATION

Similar Messages

Maybe you are looking for