Error in PBA7 & PA40

In our project we are implementing Recruitment with few customizations. The client does not require standard functionality in SAP i.e...generating the letters...so we have developed a Interface for letters and as and when the client wants he will select the applicant PERNRs and generate the relevant letters. For this we have deleted many operations from PACTV and we just used operations - INDIC and APACT for most of the statuses. Is this creating any problem for data transfer?
I have checked the configuration and activities minutely but Iam facing an error in data transfer i.e from Recruitment to PA which says run time error. Iam getting this error in PBA7 and in PA40 when running Hire Applicant action. When I run 'To be hired' action in PB40 - Hiring & Trannsfer Data activities are also created in PB60.........The overall status for the applicants are "2 -Prepare to Hire" and status reason is "90-To be hired only"

Hi rkm,
For an applicant to be transferred to employee database, there should be an activity with system function D- Transfer to employee databse should be defined on him.
Please make sure that following lines reside in PACTV feature:
2 &PACTV =INDIC A, NEXTR A
2 A &PACTV =APACT 014, NEXTR B
2 B &PACTV =INDIC A, NEXTR C
2 C &PACTV =APACT 015, NEXTR D
2 D &PACTV =RECTK X, NEXTR E
2 E &PACTV =REFID X,
Please also go to t-code SM31 - view T750J and make sure that system function for activity type 015 is D.
Regards,
Dilek

Similar Messages

Error while using pa40 for hiring an applicant

Hi
I am trying to hire an applicant using pa40 transaction code
But it gives me an error "NO ACTIVITIES FOUND". ( The applicant has overall status as "to be hired" and action type as "cleared interview" which is created)
However, when I go to Transaction code PB30 and change the applicant action type ( with overall status as" to be hired"), it works
Can someone explain to me why this is so?
Is there some connection between applicant action type and overall status and pa40?
Regards
Jean

Hi Jean,
Try the same thing through t code PBA7 and check what the exact error you are geting, but make sure that b4 running this tcode your applicant action status shud be 2 (to be hired).
If your are trying to do the same through tcode PA40 then make sure that in table T529A go through sm30 for the same action Function character should be 7.
Hope this helps you.
Regards,
Prashantkumar Tata

Run time error in PBA7

Dear Consultants,
When transferring Applicant data for one client using PBA7, system works properly & jumps to PA40 with action type 60 & the data is transferred to Employee data. Whereas in other system, PBA7 gives Run Time Error. I checked the customization but may I know which setting of these 2 systems need to be compared??
I get similar error while deleting applicant data using PB90
The error appears like :
SELECT * FROM (dbname) INTO
              CORRESPONDING FIELDS OF <infty_struc>
                       WHERE pernr EQ fps_pernr
                       AND   begda LE fps_endda
                       AND   endda GE fps_begda.
Regards
Bindumadhav

Dear Dilek,
Many thanks for your support.. I checked all tables suggested by you. All settings are identical. The Error stated as follows :
Missing RAISING Clause in Interface
    Program                                 SAPFP50P
    Include                                 FP50PF20
    Row                                     439
    Module type                             (FORM)
    Module Name                             READ_DATABASE
Trigger Location of Exception
    Program                                 SAPFP50P
    Include                                 FP50PF20
    Row                                     698
    Module type                             (FORM)
    Module Name                             READ_DATABASE
I compared the said rows in said Includes of said Programs on both the systems & also found them identical. The only difference was in working system the Applicant number range is external & SAP Patch level is 46. But in non working it is internal & SAP patch level is 27. Could that be the reason ???
Thanks again & Regards
Bindumadhav

Error while running PA40

Hi,
i'm getting an error while running my PA40,
after giving all hiring data at the time of saving i'm getting an
error at date of entry
its like
"no infotypes found,maintain infogroup modifier/user group"
Please help
Anish

Hi
Did you maintain the IGMOD feature?
Just check.
R K

Error in Running PA40 transaction

HI,
There are certain Joining & relieving Actions we made pertaining to a defined USer Group 42. A role was created authorising attached users to run PA40 transaction. The screen of PA40 & the corresponding Action MEnu is changed by the User Group PArameter.
When the transaction is run , the system shows an error saying "You are not authorised to run the Action Z3" (Z3 being the code of action).
Unable to understnad the issue why this is happening. PLs help.

Hi,
Please check in the Authorization data of the role under the object P_ORIGIN (HR: Master Data) whether for infotype "0000" in the subtype field the value is "*" and not " " or anything specific.
Subtype value would restrict action types as mentioned in the role.
Hope this helps.
Regards,
Shreyasi.

Error in pba7

hello,
i have started hiring a person iam stuckup in pba7 here it shows the applicant status as error in import .how do i rectify it? & what is the nxt step to complete hiring & wht other steps shld i complete to c tht particular perosn is hired & his name is displayed in ppom_old
Edited by: jagadish shimoga on Jun 30, 2009 12:49 PM

Hi Jagdish,
For executing the PBA7 transaction successfully, you have to execute it at one go. What I mean by this is, once u execute PBA7, all data in PA should be filled in one sequence.
If you miss filling any information for an employee, you should capture that data thro' PA30 and not by going back and forth while executing PA action in PBA7
You will get an error error in import if you are not completing filling the infotypes in PA as per the logical sequence as configured.
Hope this answers your query.
Let me know in case of any clarification
Rgeards,
Chetan W

Authorisation error with PA30/PA40 transaction

Hi Experts,
In our system, the transactions PA30/PA40 are giving some authorisation error
(No read/maintain authorisation for Personal Data) for all operations
create/change/display of data. (even though in su01 transaction,
we have given all authorisations SAP_ALL under profiles and also removed all roles)
Also checked the possibility of any custom BADI getting called, but none exists.
Any solutions / suggestions are appreciated.
Thanks in Advance,
Mirza.

Hi!
Right after you have the authority error, enter the following transaction code /NSU53.
SU53 trasnaction will collect the missing autority objects.
Regards
Tamá

Error in PA40 transaction - Management of Global Employees

Hi,
We are trying to implement Global Employment and have run into a serious error.
In PA40, I try an Expatriation Planning action and get the following error when I try to save the record.
Error Long Text
Grouped data for personnel number 91000074 does not match 01000035
Message no. PBAS_SERVICE042
Diagnosis
Personnel number 91000074 and 01000035 are supposed to be grouped with the grouping value 10 for infotype 0002. However, the number of data records of the infotype is not the same for these personnel numbers.
System Response
The system identifies all affected data records as inconsistent.
Procedure
Notify your system administrator.
Procedure for System Administration
The inconsistency described above can have several causes. The most likely causes are:
Customer-specific settings for grouping infotypes have been changed without the database being adjusted accordingly.
A customer program was used to add data to the database, without reference to the grouping values.
The infotype is not supposed to be grouped, but the grouping mechanism was activated inadvertently.
You must first identify the cause of the inconsistencies. You can use report RPUFIXDS to do this. ( I ran report, with no results for my
PERNRs)
We tried several other things from changing number ranges to turning Concurrent employment On. But the error was not fixed. We tried looking through OSS notes that could be related to Global Employment and CE but there was nothing relevant. We are on the latest patch levels for Basis and HR components.
Any help will be greatly appreciated.
Thank you
Amina

Yes the two pernrs belong to the same employee. Minimum set up on the infotypes you have mentioned has been performed. We are attempting to create the first step in the prepare for global assignment, which means setting up the assignment (copying infotypes from the original assignment). We can not get beyond the first IT0002 in the creation of the 2nd dialog, we never get to any IT's that are required for the concurrent employment infotypes.
Thanks
Amina

Error in PA40: missing secondary record for infotype 0001

Hi Experts,
while changing the job code of employee i am getting below error in the PA40 transaction for IT0001 .
Error : missing secondary record for infotype 0001 Key
could you please tell me why this message is coming.
Advance thanks,
Regards
Ram

Hi,
Please check out whether any user exits are maintained.
Check ZXPADU01/ZXPADU02 includes.
Please also check out whether there are dynamic actions configured for IT0000 and IT0001 via V_T588Z.
Regards,
Dilek
Edited by: Dilek Ersoz Adak on Dec 16, 2009 3:19 PM

Error: Organizational Assignment created via Orgnizational Management in HCM form

Hi All,
I am getting below error while moving an EE to certain position via HCM form.
I have cheked and found that if an org unit is to be assigned to another cost center in Organizational management from a certain date, this action generates a new record in infotype 0001 for integrated persons from the date of assignment to the new cost center and if we perform any action which would be deleting the new record (created from OM) in IT0001 then this error would populate.
Here is the the same case a new Cost Centre has been assigned with the orgunit and a new record is creaed in IT0001 from the OM but when I am performing the same action via PA40 then I not getting any error, the error is occuring from the form only.
Can you please help me to resove this error and provide me the reason why it is not occring when I am performing the same action from PA40.
Regards,
Mayank

Hi Mayank,
I think you will be triggering Job Salary Form for the action you have mentioned. Please check in the Tcode HRASR_DT for the form name as I have show below from my development system. In Back-End services - SAP_PA - Infotypes and Operations and for Infotype 0001 check what is the operation that you have maintained.. It should be "change" to avoid the error message.
For PA40 action you would have configured the same as "change" thats why you are not getting error message in PA40.
Thanks,
Sriram

Runtime error while executing New Hire action in PA40

Hi All,i am getting short dump while executing PA40 for new hire action typecan anyone look into this and guide as i am new to HCMNote: getting dump only for one user id for rest all other user id i am not getting dump.
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           /1PAPAXX/HDR_21000A
Application Component Not Assigned
Date and Time          21.08.2014 14:07:03
Short text
    Syntax error in program "/1PAPAXX/HDR_21000A ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in
    include "/1PAPAXX/HDR_21000AO01 " in
    line 52:
    ""LV_LENGTH" has already been declared"
    The include has been created and last changed by:
    Created by: "HCM04 "
    Last changed by: "HCM03 "
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "/1PAPAXX/HDR_21000A ".
    You can also perform the syntax check from the ABAP Editor.
    If the problem persists, proceed as follows:
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    The following syntax error was found in the program /1PAPAXX/HDR_21000A :
    ""LV_LENGTH" has already been declared"
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
System environment
    SAP Release..... 731
    SAP Basis Level. 0007
    Application server... "dc-ds-erp"
    Network address...... "172.16.23.111"
    Operating system..... "Linux"
    Release.............. "3.0.13-0.27-default"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "dc-ds-erp"
    Database type..... "ORACLE"
    Database name..... "ECD"
    Database user ID.. "SAPSR3"
    Terminal.......... "NLC-HP"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Sep 14 2013 06:16:24"
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"
    Database version. "OCI_112, 11.2.0.3.0, V1, default"
    Patch level. 500
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Linux 2.6, Linux 3"
    Memory consumption
    Roll.... 0
    EM...... 37708200
    Heap.... 0
    Page.... 106496
    MM Used. 4666776
    MM Free. 3709976
User and Transaction
    Client.............. 210
    User................ "HCM03"
    Language key........ "E"
    Transaction......... "PA40 "
    Transaction ID...... "53EF470299AB5D67E1000000AC10176F"
    EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPFP50M"
    Screen.............. "MP000000 1000"
    Screen Line......... 3
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPFP50M" - in
    "GET_HEADER_WITH_TCLAS".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 146
    of the (Include) program "FP50MDHD".
Source Code Extract
Line
SourceCde
116
CALL FUNCTION 'HR_HEADER_GET'
117
      EXPORTING
118
           DHDID                    = FHD_HID
119
           BEGDA                    = BEGDA
120
           TCLAS                    = TCLAS
121
* Es wird nur einer der folgenden 3 Parameter benutzt.
122
* Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.
123
* Der erste der nicht initial ist wird ausgewertet.
124
*           MOLGA                   =
125
           P0001                    = P0001
126
           PERNR                    = PSPAR-PERNR
127
      IMPORTING
128
           PROG                     = HEADER_PROG
129
           DNUM                     = HEADER_DYNNR
130
       EXCEPTIONS
131
            HEADER_DEACTIVATED          = 1
132
            HEADER_UNKNOWN              = 2
133
            HEADER_GENERATE_DEACTIVATED = 3
134
            HEADER_GENERATE_FAILED      = 4
135
            INTERNAL_ERROR              = 5
136
            OTHERS                      = 6.
137
138
IF NOT SY-SUBRC IS INITIAL.
139
* Bei Problemen gibt's eben ein leeres Dynpro.
140
    HEADER_PROG = 'SAPMP50A'.
141
    HEADER_DYNNR = '0090'.
142
ELSE. " NOT sy-subrc IS INITIAL.                                   "
143
* Dann setzen wir jetzt auch noch das Datum fest.
144
    PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.
145
* Und schalten auf Uebergabe der PERNR mit globalen Variablen.
>>>>>
    PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).
147
ENDIF. " (ELSE) NOT sy-subrc IS INITIAL.                           "
148
* Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.
149
* Wird mit Einfuehrung des Headerobjekts obsolet.
150
PERFORM REMEMBER_HEADER "                             "XYVPH4K015649
151
    USING HEADER_PROG HEADER_DYNNR 'S'. "               "XYVPH4K015649
152
ENDFORM.
153
154
*       FORM RE588I                                                   *
155
156
157
158
* --> T588I_DHDID                                                   *
159
* --> T588I_MOLGA                                                   *
160
* --> T588I_TCLAS

Implement SAP Note 1004280.. your issue if fixed
If your issue is resolved request you to close the thread or else free feel to touch base
BR
Anil

Error while hiring an employee in pa40

HI
This occurs while hiring an employee in PA40.
Runtime Errors         GETWA_NOT_ASSIGNED
Short text
     Field symbol has not yet been assigned.
     Error in the ABAP Application Program
     The current ABAP program "SAPLHRWF" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
    You attempted to access an unassigned field symbol
    (data segment 32770).
    Thanks in advance

Hi,
first tell me exactly where the error is coming?
is it coming as soon as you entered in PA40? or
is it coming in a particular infotype? if so what is that infotype and what value you are inputing in that screen?
please make sure the value you are giving in the screen is properly configured. also check the T588D & T529A with respect to UGR and IGMOD.
Gayathri N

Error with creating a new employee - PA40

When creating a new employee record using PA40, the PERNR gets generated as soon as Infotype 0000 is updated. How do we capture the new PERNR, if a BDC recording of PA40 fails midway during the process
I would appreciate and reward any valuable ideas!

create a session for error messages....and u can go to sm35 and check what has ahppened.....if not use format_message and display what has happened as report output....in case of BDC fail......!!!!!
it will be like....
call transaction 'PA40' using it_bdctab
mode 'N'
update 'S'
messages into it_bdcmsgcoll.
if sy-subrc <> 0.
*--store the pernr for which bdc failed......here!!!
call function 'bdc_open_group'
call function 'bdc_insert'
call function format_message
call function 'bdc_close_group'
*---check error and try to rectify it.....
Regards
Vasu

Runtime error in PA40

Hi all
i am working with PA40 transaction in HR. In that i am getting a runtime error like this, here u can find the detials.
<b>program name : SAPFP500
Include name : FP500EFW<u></b>
Eroor analysis:</u>
I am getting a error like this 'In a write src to dest+off [ ( len) ] [index i] statement, '"off" contains a target field offset (3) which is larger then the length of the target field "dest". (2).
this is not allowed.
Please guide me to get out of this problm..
Thanks in advance.

Hi,
Have you recently upgraded your system or applied upport packs. As this is a standard transaction you better search in OSS and you will find some note to fix it.
Regards,
Atish

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?

Error in PBA7 & PA40

Similar Messages

Maybe you are looking for