HR_MAINTAIN_MASTERDATA & PA40

Hi All,
I'm experiencing some issues with the usage of the Function Module HR_MAINTAIN_MASTERDATA.
The scenario im trying to test is a New Hire. When i perform new hire in T-Code PA40 i only populate Infotypes Organizational Assignment, Personal Data, Addresses, Bank Data and Communication im able to create the employee.
When I try to do the same within the FM it's returning me error and says Fill in all required entry fields. I've executed the FM in dialog mode and found out that Infotype Plan Working Time is throwing this message because the mandatory field is not populated.
Any idea why I am able to perform New Hire in PA40 with only populating a selected few infotypes but in FM these infotypes are not sufficient?
Thanks
John

Similar Messages

One action not creating from pa40 using HR_MAINTAIN_MASTERDATA

Hi Friends -
I am using FM HR_MAINTAIN_MASTERDATA for creating action 'Expatriation Planning ' in PA40
which covers 0000, 0001 ,00002 and few more but immid after filling 0001 data and save it gives me error 0003 is not created for this employees and come out
How i can correct it as 00003 infotype looks like some backend IT .
Regards
Meeta

k

Hiring new employee with HR_MAINTAIN_MASTERDATA

Hi,
I am trying to hire new employee with HR_MAINTAIN_MASTERDATA. For now, I only gives the mandatory values of the infotype 0002 in proposed_values and parameters to the FM.
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
     EXPORTING
       pernr                    = no_emp_int
       massn                    = '01'
       actio                    = 'INS'
       tclas                    = 'A'
       begda                    = sy-datum
       endda                    = '99991231'
*       OBJPS                    =
*       SEQNR                    =
*       SPRPS                    =
*       SUBTY                    =
       werks                    = '1000'
       persg                    = '1'
       persk                    = 'D9'
*       PLANS                    =
       dialog_mode              = '1'
*       LUW_MODE                 = '1'
       no_existence_check       = 'X'
*       NO_ENQUEUE               = ' '
      IMPORTING
        return                   = return
*       RETURN1                  =
*       HR_RETURN                =
      TABLES
        proposed_values          = it_prop_val
*       MODIFIED_KEYS            =
When it is executed, it gives me the error:
'No data available for A 00007787 0003' where 00007787 is the employee number. My guess is that 0003 is for the Payroll status (0003) infotype. I thought it would be automatically created with the FM.
When I change the dialog_mode parameter to '0', no error appears but, the employee data isn't saved i.e. I cannot access it with PA30 or PA40. It says 'Personnal number not yet assigned'.
So, I'd like to know how to save data correctly and why dialog_mode '1' or '2' failed everytime.
Thanks a lot for your answers, points will be awarded as it fits my needs!

Patrick
My guess is that this FM HR_MAINTAIN_MASTERDATA will not create all 4 infotypes (0, 1, 2 and 3 as I think all those 4 are mandatory for every employee). I would say that you need to specify data for each infotype separately. You can in fact create all those 4 infotypes in separate calls of FM. I was doing this some time ago (with calling FM 4 times) but I was using different FM - HR_INFOTYPE_OPERATION.
The obligatory fields for each infotype depends on the setting in you system so you need to find this out by your-self.
As per infotype 0003 do not forget to set properly field VIEKN - see feature IVWID otherwise maintenance of created employee may not be possible.
One last thing - you may try to use IDOC HRMD_A for employee creation. This way is much faster than using FM's. But be careful no data check/validation is done when you pass an IDOc to application (which maybe an advantage in your situation).
Andrzej

HR_MAINTAIN_MASTERDATA

hi,
can you plz explain me how to use this function module in detail.
any code snipet wil be of great help.
is it possible to generate a PERNR for a new hire using this function module?
regards,
Balaji

Here is the code..
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
    EXPORTING
      pernr                    = p_0735-pernr
    MASSN                    =
      actio                    = 'MOD'
      tclas                    = 'A'
      begda                    = p_0735-begda
      endda                    = p_0735-endda
      objps                    = p_0735-objps
      seqnr                    = p_0735-seqnr
      sprps                    = p_0735-sprps
      subty                    = p_0735-subty
*Put 0 here when everything is ok. 1 shows dialog on error.
      dialog_mode              = dialog_mode
      luw_mode                 = luw_mode
    NO_EXISTENCE_CHECK       = ' '
    NO_ENQUEUE               = ' '
    IMPORTING
      return                   = l_return
    RETURN1                  =
    HR_RETURN                =
    TABLES
      proposed_values          = l_value_tab
      modified_keys            = l_pskey.
I don't think we can generate PERNR using this. Use PA40 to create the PERNR

HR_MAINTAIN_MASTERDATA substitutions

Hi Gurus,
we are facing a problem using the FM HR_MAINTAIN_MASTERDATA to save substitutions. The problem is the FM doesn't delimit the substituion if we enter a new one.
For example, a substitution from 07.02.2011 to 13.02.2011, we try to book a new subtitution for the 09.02.2011. The FM delete the substitution from 07 to 13 and just matain the 09.02.2011.
I have tried with the operation LIS9, MOD and INS. INS works as I have described before, MOD and LIS9 doesn't work (error: Complex error ...)
This is very weird becuase sometime works, (10% of the times), but I didn't find anything different.
In addition, I have tried to use the FM HR_INFOTYPE_OPERATION, but I dind't find the proper values to make it works.
The same tests have been done for absences with op=INS, and they are delimited.
Do you know a way to delimit the IT2003?
Thank you and regards,
Rodolfo

A behaviour that has been observed was that, after infotype 0185 was saved, the function module throws me back to infotype 0000, citing, "No authorization to maintain XYZ exists". Data that I had populated to the screen, either via the FM or by manual input were cleared. If I skip the next 4 screens, I'll arrive at the Infotype after XYZ, with the data populated. Subsequent infotypes also have their data filled in.
Once I complete the sequence, the personnel record will be created. Upon examination, the frist 4 screens that were skipped in the 2nd pass contains data that were entered in the 1st pass.
My question, as posted in the original post, is why infotype XYZ is triggered by the function module, as the staffing account does not hae access for it. If I repeat the process using PA40, the infotype is skipped accordingly.
Any help would be appreciated.
Thank you,
James Wong,

Hr_maintain_masterdata showing an infotype that the user does not have auth

subject: hr_maintain_masterdata showing an infotype that the user does not have authorisation for
Hi all,
I've a user account that's meant to perform staffing, based on the actual HR role. The system is also set up with an infogroup that contains infotypes 0000, 0001, 0006, 0185, XYZ and other infotypes; XYZ representing an actual infotype. The HR role is not supposed to have this infotype XYZ.
When PA40 is used, infotype XYZ will be skipped, as the user account do not have authorisation for it. I could then proceed to create the record.
When the fm: hr_maintain_masterdata is used, I was prompted that I do not have authorisation for infotype XYZ.
I have setup my fm with the mininum amount of values, as indicated below.
I did not populate a table for "proposed_values" so the infotypes called were due to the actions of the infogroup.
fm: hr_maintain_masterdata
pernr = 01234567
massn = 01          (new staff)
actio = INS          (insert record)
tclas = A          (master record)
begda = 01.09.2010
endda = 31.12.9999
werks = myCompanyPlant
dialog_mode = 2     (online)
luw_mode = 1          (commit, if no errors encountered)
no_existance_check = X
Q. Is there any way to let the function module call the infotypes, with authorisation checks, as what PA40 is doing?
Your guidance would be appreciated.
Thank you,
James Wong

A behaviour that has been observed was that, after infotype 0185 was saved, the function module throws me back to infotype 0000, citing, "No authorization to maintain XYZ exists". Data that I had populated to the screen, either via the FM or by manual input were cleared. If I skip the next 4 screens, I'll arrive at the Infotype after XYZ, with the data populated. Subsequent infotypes also have their data filled in.
Once I complete the sequence, the personnel record will be created. Upon examination, the frist 4 screens that were skipped in the 2nd pass contains data that were entered in the 1st pass.
My question, as posted in the original post, is why infotype XYZ is triggered by the function module, as the staffing account does not hae access for it. If I repeat the process using PA40, the infotype is skipped accordingly.
Any help would be appreciated.
Thank you,
James Wong,

HR_MAINTAIN_MASTERDATA for hiring employees

Hi,
I am trying to use HR_MAINTAIN_MASTERDATA for hiring employees and creating a list of infotypes. I have tried with a number of infotypes as well as with just 0000, 0001 and 0002.
I am using 'DIALOG_MODE = 2' to see the steps as the function module progresses, I keep getting this error about Infotype 169. After creating IT0000, proceeds to IT0001 and then straight to IT0169 even though I do not have it on PROPOSEDVALUES. When it hits 169, I get the error saying the Infotype 171 cannot be read for Pernr xxxxxxxx on mm/dd/yyyy (begin date).
I do not face this problem when I manually go through PA40. I have tried various combinations and still get the same issue.
If you have any ideas, I would greatly appreciate those.
Thanks,
Jay Viswanathan

Hi Mr. A,
I have Action = 'INS' which is the default value (same as not sending any value).
Normal hiring process takes me through 0000, 0001, 0002 etc .. however the function module stops at 169 before going to 0002.
Thats whats confusing.
Thanks,
Jay

Unlock PERNR after excution of FM HR_MAINTAIN_MASTERDATA

Hi Experts,
Issue One:
I am using FM HR_MAINTAIN_MASTERDATA for Hire Action. In our Hiring action there are some Dynamic Action which will be triggered in background by save on other infotypes like infotype 0009 will be triggered by save on infotype 0006 and 210 by on save of infotype 0209. The record in these infotypes will be created based on dynamic action in background. Now I am facing the issue with these background dynamic actions. When I am using FM HR_MAINTAIN_MASTERDATA, these dynamic actions are not triggering. I suggested one solution to my Functional owner that to keep dynamic actions as it is but bring infotypes in foreground(I mean added them in the infogroup) instead of background so that the records can be created. But our client is not accepting to trigger the dynamic action in the foreground.
Issue Two:
I want to create records in these infotypes(0009 and 0210) after Hiring action complete by FM HR_MAINTAIN_MASTERDATA. But I am facing the issue with locking of pernr after execution of this FM. It is not unlocking the pernr until the completion of program i.e., until or unless we come to selection screen again. I tried to unlock the pernr with differnt FM and BAPI available but of no use.
Please suggest me solution for the above issues highly appreciated.
Thanks & Regards,
Suresh
Edited by: suresh kumar on Jun 13, 2010 7:20 AM
Edited by: suresh kumar on Jun 13, 2010 7:21 AM
Edited by: suresh kumar on Jun 13, 2010 7:21 AM

Hi Suresh,
Here is answers of your questions.
Answer 1--> Dynamic Action --> Dynamic action can't be executed by using FM HR_MAINTAIN_MASTERDATA. It only executes when you hire some person in PA30 or PA40 transaction. Now to solve your issue you have to write custom code which has been used in dynamic action. Say when IT0009 is created then through dynamic action you are filling IT0105 data and this is done in dynamic action. If you want to do the same in programming then please write custom code for that. I mean after creating IT0009 data call SAP function module to update IT0105 data.
Answer 2 --> Locking issue.
When an employee is hired then PERNR is generated. You have to catch the PERNR then use FM/BAPI to unlock the employee.
You can use BAPIEMPLOYEEENQUE* or many other function modules are there.
Thanks & Regards,
Sandip Biswas.

HR_MAINTAIN_MASTERDATA is it possible to perform same action as PA41

Hi All,
Is it possible to perform same action as PA 41 through HR_MAINTAIN_MASTERDATA ?
I have a scenario If employee is already left i.e. date of leaving is already in info type 0 and if after 2 days I want to change leaving date of employee is it possible through function module Z_PBHR_INPUT, is there any functionality of PA41 or PA40 in this IDOC?
If you give me your number I could discuss with you.
Thanks in advance!!
Thanks.
Kind Regards,
Manoj Shakya
Phone No. +44 012567 44337
Mobile No. +44 07903520822

action type 70 71
is nothing but tells nothig but about screen PA41
when there is a req to change the date of the employee so u can procedd
i am trying to call u

HR_MAINTAIN_MASTERDATA issue with PA0171 defaults

Greetings experts!
I'm using HR_MAINTAIN_MASTERDATA to create a participant. I'm running into trouble with PA0171. The defaults are not correct and even if I hard-code values into the proposed-values table it ignores them.
I thought I'd try just not sending over 171 at all and then, after HR_MAINTAIN_MASTERDATA finished, I'd use HR_INFOTYPE_OPERATION to create it. Curiously, however, HR_MAINTAIN_MASTERDATA still tries to populate 171 even though I'm not sending it (I'm setting the DIALOG_MODE parameter to 2 so I can see each screen as it's processed). Apparently, something else is "triggering" it.
When I run PA40 the values are defaulted correctly so I must be doing something out of order, perhaps? The best scenario would for 171 to be defaulted to the correct values automatically but I must be missing something for it to default to the wrong values.
Any suggestions?
Here's the order I'm sending in the proposed values:
0000
0001
0002
0006
0105
0008
0041
UPDATE
Also, a colleague of mine discovered that in
program MP017100
screen 2000 (infotype 171)
    module p0171
      FM 'HR_BEN_GET_FROM_FEATURE_BAREA'
        subroutine sap_get_emp_barea_from_feature
          subroutine fill_pme30
there is a call to "HR_READ_INFOTYPE" on line 1352 of "LHRBEN00FEATUREF01" and this always returns "8" meaning no records were found. Puzzled, we looked at infotype 0000 with the pernr in SE11 and sure enough there's no data there.
I thought changing to LUW_MODE param of HR_MAINTAIN_MASTERDATA to "0" might solve that issue but it doesn't seem to have any affect.
Many thanks!
Edited by: Steve King on Dec 30, 2008 10:09 PM

Steve,
The reason for incorrect default values in IT 0171 is, there is code in PBO module of MP017100 which defaults value from features BAREA, BENGR and BSTAT only if the mode is not batch.
To make it work, you can mimic the code that exist in "module p0171 output" in PBAS0001 user exit to default values.
regards
Sridhar

How to use HR_MAINTAIN_MASTERDATA to terminate an employee

Greetings experts:
I'm working on an inbound interface that, among other things, can terminate an employee. I'm new to ABAP and so it was recommended to me early on to record PA40 for this action. That seemed to be working great until they added a new action and the index position recorded by SHDB no longer was accurate. I tried reproducing the list in PA40 using some queries but that didn't work either.
So now I've been asked to use HR_MAINTAIN_MASTERDATA. I understand the basics of how this FM works but I'm not sure how to relate what the recording was doing to this function module. The recording touched 3 infotypes: 0000, 0001 and 0378. Some of the fields were defaulted on the screen so I didn't need to provide them in the BDC code, i.e., "PSPAR-WERKS", etc. Now that I'm having to "manually" setup these infotypes I don't know what values I can omit and which absolutely must provide.
Can I use the code from the recording as a guide? In other words, if I didn't record a field because it was being defaulted will it also be defaulted if I use HR_MAINTAIN_MASTERDATA?
Many thanks and Merry Christmas to all.

Yes, Steve, HR_MAINTAIN_MASTERDATA is basically a FM that reproduces PA40. I use this FM for all the interfaces that require measures and besides some bug or two, the FM works perfectly, be it for the hiring or firing measures. Like PA40, when you fill the MASSN field, the FM will go through every infotype that is specified in that infogroup and will fill each infotype with the default values unless you pass them in the PROPOSED_VALUES table. For the values to pass, it's pretty simple as well, all you need is the name of the field (in the PA structure and not the screen name like in Batch Input) and the value you want to pass. Here is a sample code for you ...
Also, you can even use the parameter DIALOG_MODE to make the input visible so you can see if some strange error occurs, you can see exactly what it is, just use DIALOG_MODE = '2' for visible.
data: return type bapiret1.
data: w_pernr type p0001-pernr,
        w_pnalt type p0032-pnalt,
        w_begda type p0001-begda,
        w_massg type p0000-massg,
        w_retcode type sy-subrc,
        w_dial type c.
clear : w_massg.
w_massg = '01'.
if NOT P_MASSG IS INITIAL.
    w_massg = p_massg.
endif.
LOOP AT P_TAB.
    clear : wa_proposed_values, proposed_values, t_output.
    free proposed_values.
* Caso o motivo não venha do ecran de seleccao entao fica 01
* Preencher os dados para cada infotipo usando a tabela "proposed_values"
*** Dados Infotipo 0000
    wa_proposed_values-infty = '0000'.
    wa_proposed_values-fname = 'P0000-MASSG'.
    wa_proposed_values-fval = w_massg.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0000'.
    wa_proposed_values-fname = 'PSPAR-PERSG'.
    wa_proposed_values-fval = P_TAB-PERSG.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0000'.
    wa_proposed_values-fname = 'PSPAR-PERSK'.
    wa_proposed_values-fval = P_TAB-PERSK.
    append wa_proposed_values to proposed_values.
*** Dados Infotipo 0016
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-CTTYP'.
    wa_proposed_values-fval = P_TAB-CTTYP.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-CTBEG'.
    wa_proposed_values-fval = P_TAB-CTBEG.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-CTEDT'.
    wa_proposed_values-fval = P_TAB-CTEDT.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-PRBZT'.
    wa_proposed_values-fval = P_TAB-PRBZT.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-PRBEH'.
    wa_proposed_values-fval = P_TAB-PRBEH.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0016'.
    wa_proposed_values-fname = 'P0016-EINDT'.
    wa_proposed_values-fval = P_TAB-EINDT.
    append wa_proposed_values to proposed_values.
*** Dados Infotipo 0001
    wa_proposed_values-infty = '0001'.
    wa_proposed_values-fname = 'P0001-BTRTL'.
    wa_proposed_values-fval = P_TAB-BTRTL.
    append wa_proposed_values to proposed_values.
*    wa_proposed_values-infty = '0001'.
*    wa_proposed_values-fname = 'P0001-PERSG'.
*    wa_proposed_values-fval = P_TAB-PERSG.
*    append wa_proposed_values to proposed_values.
*    wa_proposed_values-infty = '0001'.
*    wa_proposed_values-fname = 'P0001-PERSK'.
*    wa_proposed_values-fval = P_TAB-PERSK.
*    append wa_proposed_values to proposed_values.
*** Dados Infotipo 0002
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-ANRED'.
    wa_proposed_values-fval = P_TAB-ANRED.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-CNAME'.
    wa_proposed_values-fval = P_TAB-CNAME.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-VORNA'.
    wa_proposed_values-fval = P_TAB-VORNA.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-NACHN'.
    wa_proposed_values-fval = P_TAB-NACHN.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-GBDAT'.
    wa_proposed_values-fval = P_TAB-GBDAT.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-GBLND'.
    wa_proposed_values-fval = P_TAB-GBLND.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-GBORT'.
    wa_proposed_values-fval = P_TAB-GBORT.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0336-COUBI'.
    wa_proposed_values-fval = P_TAB-COUBI.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0336-PARBI'.
    wa_proposed_values-fval = P_TAB-PARBI.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-GESCH'.
    wa_proposed_values-fval = P_TAB-GESCH.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-NATIO'.
    wa_proposed_values-fval = P_TAB-NATIO.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-FAMST'.
    wa_proposed_values-fval = P_TAB-FAMST.
    append wa_proposed_values to proposed_values.
    wa_proposed_values-infty = '0002'.
    wa_proposed_values-fname = 'P0002-ANZKD'.
    wa_proposed_values-fval = P_TAB-ANZKD.
    append wa_proposed_values to proposed_values.
*** Função HR_MAINTAIN_MASTERDATA
* Perform PA40 via Maintain_masterdata
    clear w_dial.
    if p_modo = 'X'.
      w_dial = '2'.
    endif.
    call function 'HR_MAINTAIN_MASTERDATA'
      EXPORTING
        massn           = 'CD'
*        massg           = w_massg
        actio           = 'INS'
        begda           = P_TAB-EINDA
        werks           = P_TAB-WERKS
        plans           = P_TAB-PLANS
        dialog_mode     = w_dial
      IMPORTING
        return1         = return
      TABLES
        proposed_values = proposed_values.
    if not return is initial.
      CONCATENATE return-message_v1 return-message_v2 into t_output-mensagem.
    else.
      t_output-mensagem = 'Medida E1 criada com sucesso'.
    endif.
ENDLOOP.
Edited by: Pedro Guarita on Dec 22, 2008 5:10 PM

Problem with HR_MAINTAIN_MASTERDATA delimiting infotypes

hi,
I'm trying to delimit a register of the infotype 0017 using the FM
HR_MAINTAIN_MASTERDATA because i had to execute a infogroup (like the PA40
transaction) this is the call:
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
      EXPORTING
        pernr           = gwa_data-pernr
        massn           = 'A9'
        actio           = 'INSS'
        tclas           = 'A'
        begda           = gwa_data-begda
        endda           = gwa_data-endda
        werks           = gwa_data-persa
        persg           = gwa_data-persg
        persk           = gwa_data-persk
        plans           = gwa_data-plans
        dialog_mode     = '2'
       NO_EXISTENCE_CHECK = 'X'
      TABLES
        proposed_values = ltd_valprop.
The customizing of the T588D (Infogroups for Actions) table is:
ITYGR     ACTIO        INFTY
   A9     COP           0001
   A9     INS           0015
   A9     LIS9          0017
When I execute the FM first it creates the 0000 infotype, then the copy of the
001 and the new 0015, but when gets to the infotype 0017, it is not showed!
(i mean skips the infotype 0017, notice the 0017 register in the table has the LIS9 action), i thought this FM works like the PA40
transaction, reading the T588D table and appliaying the corresponding action
to each infotype, but this is not working. Any help will be very grateful.
Greetings,
Felipe.

Hi Felipe ,
can u tell me what fields+values u are passing to this FM , bcos when i try this FM it wll goes to infotype 17 without passing any screen fields to this FM.
And Better to Add Return tables to this FM , then u wll get some idea.
Regards
Peram

Call Transaction 'PA40' ALWAYS returns with error code

Hi,
I'm having issues with updating personnel actions using CALL TRANSACTION 'PA40'. The call always ends with an error code.
I checked the message table and there are no error messages, only warnings and status messages. Warning and information messages are usually skipped in the BDC...I've coded an 'ENTER' to past the warning but this does not work either as the subsequent infotype screen fields are then not filled correctly.
The following values for addition OPTIONS are used:
data: opt like ctu_params.
opt-dismode = 'N'.
opt-updmode = 'A'. ('S' makes no difference)
opt-defsize = 'X'.
opt-nobinpt = 'X'. ( ' ' makes no difference)
I've tried using 'PA30' for the same actions but I get the same problem. I've used call transaction 'PA30' in many programs and I've never come across this problem.
Is there perhaps a config setting somewhere to fix this? I've tried hiring employees using HR_MAINTAIN_MASTERDATA with the employee existance check off but there's a couple of problems there as well - sample code for hiring an employee would be very helpful...
I need your help urgently and would appreciate your assitance immensely. (I'm working on 4.6C.)
Thank you.
LM

The easiest way to resolve this is to set
opt-dismode = 'E'.
this way it will run in background and jump out when it hits an error, and it's much easier to see what the real issue is.
I'm assuming you used SHDB first to get the recording?

Issue regarding HR_MAINTAIN_MASTERDATA

Hi fellow Abap'ers.
I am using HR_MAINTAIN_MASTERDATA to hire employees nothing wrong with that. I gather the information for the different infotypes from excel files but i only have files for Infotypes 0000, 0001 and 0008. When i execute the FM with dialog_mode = '0' i get a return error saying to fill all fields. I then changed dialog_mode to '1' and i noticed it's stopping in infotype 0002. So, the question i have is the following, the measure i am using goes through several infotypes but i only have information for some of them, is there a way to bypass the infotypes for which i don't have files as you would do in PA40 ? If i execute in dialog_mode = '2', i can create the information, of course i have to pass the ones i don't have files but still i can create the employee with no problem with just those 3 infotypes.
Thanks in advance.

Hi Pedro,
You say you are hiring employees without IT0002-Personnel Data!?!? That is where the name and other personal information about an individual is stored. Thus, I do not know how you are seeing a name assigned to your employee.
Infotype 0002-Personal Data has a time constraint of "1". This means that it must exist for all periods the employee is in the system. The system is correct in stopping you as this is necessary information. There may be some data you do not have such as birth date for the employee, so you can make these optional fields. But you should have at least a first Name and Last Name entered in IT0002 for every employee. This is where you should also store your country's Person ID for identification.
Please rethink your process - PA40 is the recommended procedure. Loading from spreadsheets is possible (usually for initial go-live processing), but all the rules must be maintained - that includes having an IT0002.
Paul

Hr...bdc for pa40-salary increment

HI FRIENDS..
M NOT ABLE TO FETCH VALUES FOR TABLE CONTORL IN PA40 T.CODE FOR SALARY INCREMENT..
ACT D PROBLEM IS..
THE OLD SALARY SRTUCTURE IS DIFFERENG FROM CURRENT SALARY STRUCTURE IN EXCEL SHEET..
DOES ANY1 HAVE THE BDC FOR SALARY INCREMENT ..?
PLS HELP..
PTS REWRDED FOR SURE..

Hi,
We never write BDC for PA40.
Write it for PA30.
Goto SHDB tcode and record for the required infotype.
Or you can also use any of the following FM instead of BDc.
HR_INFOTYPE_OPERATION
HR_MAINTAIN_MASTERDATA.
Refer
https://forums.sdn.sap.com/click.jspa?searchID=4208189&messageID=3188548
https://forums.sdn.sap.com/click.jspa?searchID=4208189&messageID=1552901
Regards

HR_MAINTAIN_MASTERDATA & PA40

Similar Messages

Maybe you are looking for