Update Infotype 24 with Qualification

Hi Friends,
I have to update infotype 24(qualifications).  I am using function module Rh_insert_infty_1001_ext to update but this function only creates a record in hrp1001(i.e. OM side) but does not create any record in PA side i.e.  infotype 24.
Is there a different way to update infotype 24?
Thanks
Nazish

Hello Nazish,
check this  HR_INFOTYPE_OPERATION with operation = 'COP'
For PD tables,FM - BAPI_HRMASTER-SAVE_REPL_MULT is used and after PD tables are updated , for PA Tables use
FM - HR_INFOTYPE_OPERATION
Check FM - RH_INSERT_INFTY_1001_EXT  and also FM - BAPI_HRMASTER-SAVE_REPL_MULT
regards

Similar Messages

  • Updating infotype screen with screen fields

    Hello everyone,
    I am working on a RFC to update infotype 0077. Infotype 77 has veteran status as screen fields from Q0077 structure. I am using HR_INFOTYPE_OPERATION to update 77. Could anyone please tell me how to update the screen and database table pa0077.
    Thanks for your time and answers.
    Rush

    Thank you Balaji. I tried updating with HR_INFOTYPE_OPERATION but no luck. Could you please suggest any other way of updating field in info type screen (Q0077 structure) as well as in PA0077 table??
    Thanks
    Rush

  • While updating infotype i was throughen with an error

    Hi Experts,
    while I am updating the infotype 0170 with the hr_infotype_operation. i was given an error stating 'EPG                  009No data stored for 0170 in the selected period'.  How to resolve this. Please help me.
    My code is as follows
    ls_0170 like p0170.
        CALL FUNCTION 'HR_READ_INFOTYPE'
             EXPORTING
                  pernr           = ls_pernr-pernr
                  infty           = '0170'
                 begda           = '20070101'
                 endda           = '20071130'
             IMPORTING
                  subrc           = l_subrc
             TABLES
                  infty_tab       = p0170
             EXCEPTIONS
                  infty_not_found = 1
                  OTHERS          = 2.
        IF l_subrc = 0.
          IF p0170-endda = '20071130' AND p0170-begda = '20070101'.
    locking the pernr ********************
            CALL FUNCTION 'BAPI_EMPLOYEET_ENQUEUE'
                 EXPORTING
                      number        = p0170-pernr
                      validitybegin = p0170-begda
                 IMPORTING
                      return        = l_return.
    change the end date to 12/31/2007*************
            IF l_return IS INITIAL.
              p0170-endda = '20071231'.
             MODIFY p0170 INDEX 1  TRANSPORTING endda.
              ls_p0170 = p0170.
              CALL FUNCTION 'HR_INFOTYPE_OPERATION'
                   EXPORTING
                        infty     = '0170'
                        number    = p0170-pernr
                        record    = ls_p0170
                        operation = 'MOD'
                   IMPORTING
                        return    = l_return.
            ENDIF.
    unlocking the pernr ********************
            IF l_return IS INITIAL.
              CALL FUNCTION 'BAPI_EMPLOYEET_DEQUEUE'
                   EXPORTING
                        number        = p0170-pernr
                        validitybegin = p0170-begda
                   IMPORTING
                        return        = l_return.
            ENDIF.
          ENDIF.
          IF p0170-endda = '99991231' AND p0170-begda = '20071201'.
    locking the pernr ********************
            CALL FUNCTION 'BAPI_EMPLOYEET_ENQUEUE'
                 EXPORTING
                      number        = p0170-pernr
                      validitybegin = p0170-begda
                 IMPORTING
                      return        = l_return.
    ***modify a record with begin date 1/01/2008 and end date
    ***12/31/9999
            IF l_return IS INITIAL.
              p0170-begda = '20080101'.
             MODIFY p0170 INDEX 1  TRANSPORTING  begda.
              ls_p0170 = p0170.
              CALL FUNCTION 'HR_INFOTYPE_OPERATION'
                   EXPORTING
                        infty     = '0170'
                        number    = p0170-pernr
                        record    = ls_p0170
                        operation = 'MOD'
                   IMPORTING
                        return    = l_return.
            ENDIF.
    unlocking the pernr ********************
            IF l_return IS INITIAL.
              CALL FUNCTION 'BAPI_EMPLOYEET_DEQUEUE'
                   EXPORTING
                        number        = p0170-pernr
                        validitybegin = p0170-begda
                   IMPORTING
                        return        = l_return.
            ENDIF.
          ENDIF.
        ENDIF.

    Hi,
    I think if you use this code, it migth work
    ***modify a record with begin date 1/01/2008 and end date
    ***12/31/9999
    IF l_return IS INITIAL.
    ls_p0170 = p0170.
    ls_p0170-begda = '20080101'.
    MODIFY p0170 INDEX 1 TRANSPORTING begda.
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
    infty = '0170'
    number = p0170-pernr
    VALIDITYEND = p0170-endda
    VALIDITYBEGIN = p0170-begda
    record = ls_p0170
    operation = 'MOD'
    IMPORTING
    return = l_return.
    ENDIF.
    I have no idea because if that infotype could have more than one register at time perhaps you must use RECORDNUMBER. But this is not that case
    Best regards
    Jaime

  • HRMD_A07 Idoc to update InfoType 0014 does not delimit existing PA0014 rec

    In ECC 6.0, we are using HRMD_A07 Idoc to update infotype 0014 using update data received from a third party application. In XI, I am creating the Idoc with Update Code "U" with E1PLOGI, E1PITYP and E1P0014 segments. E1P0014 holds the data for the latest record.
    If I directly pass the Idoc thru ALE layer, It creates records for the new date range on E1P0014 segment, but does not delimit the previous record by changing its end date. This results in two records in PA0014 with end date of 12/31/9999 - which is wrong.
    I also tried using a wrapper FM to create additional segments in the Idoc representing the existing record in PA0014, with the end date being delimited to incoming record's beg. date minus 1.
    This also results in just creating two additional records in PA0014 corresponding to the two segments in Idoc while existing record in PA0014 stays intact resulting in two records with end date 12/31/9999.
    I also experimented with setting the lock indicator (PA0014-SPRPS) but that also does not result in delimiting the existing record.
    Am I missing something? Is there a piece of config that controls this?
    Regards,
    The time constraint on 0014 is "2"

    Hi Jon and Ashish,
    I too am facing the same issue that the new IDOC is not delimiting the previous record.
    Can you explain how did u get over you issue.
    I'm maintaining the same dates in E1PITYP and in E1P0014.
    Thanks,
    Jilly

  • Updating InfoType 0001 in ABAP

    Our parent company is passing different begin and end dates from Infotype 0001 to our HR system. In our system an employee would have a start date of 3/1/2005 but our parent company has the same employee in there system as a start date of 1/1/2008. I was looking at using user exit EXIT_SAPLRHA0_003 to capture these and add the parent companies dates into our Infotype 0001 so that there feed doesnt overwrite our original dates. I have attempted to use HR_INFOTYPE_OPERATION with no luck. Any one have a possible way to update InfoType 0001 without using a BDC?

    What exactly is the issue? In any case HR_INFOTYPE_OPERATION in turn calls HR_MAINTAIN_MASTERDATA so you might end up with the same issue with either function call.
    ~Suresh

  • Standard programs to update infotypes

    Please provide updates for this question:
    What are the standard SAP programs to update infotypes ( Ex: 001 / 002 / 003 ) .
    I will be uploading data from legacy system ( Excel / Text file ) and would like to use standard programs
    before going ahead with BDC .
    Thanks
    Rohan

    Hi,
    I checked out the program you stating.......
    In that program itself if you check the documentation its given how to add in fields.......
    You can use report RPUSTD00 to transfer master data from your old HR system.
    The dataset to be transferred must be stored in a sequential file. The file is stored under the name specified in the "logical file name" field (for more information on logical file names, read the IMG section entitled Additional client-dependent file name maintenance).
    The report reads this dataset and creates a batch input session for transaction PA30.
    The data description of your old record is defined according to the structure HRDATASET. If this structure does not meet your requirements, create the structure CI_HRDATAS in the ABAP Dictionary. In this structure, you can store the infotype fields to which data should be transferred. Make the necessary changes in RPUSTD00.
    Example
    If the include CI_HRADATAS contains the field F1 which is to be assigned to the infotype nnnn, add the following ABAP statements to FORM Dnnnn:
      CLEAR BDCDATA.
      BDCDATA-FNAM = 'Pnnnn-F1'.
      BDCDATA-FVAL =   SATZ-F1.
      APPEND BDCDATA.
    If the FORM Dnnnn does not exist for your infotype nnnn, copy FORM D0008 to FORM Dnnnn. Replace the 0008 by your infotype number:
    FORM Dnnnn.
      CLEAR BDCDATA.
      BDCDATA-PROGRAM  = 'MPnnnn00'.
      BDCDATA-DYNPRO   = '2000'.
      BDCDATA-DYNBEGIN = 'X'.
      APPEND BDCDATA.
      CLEAR BDCDATA.
      BDCDATA-FNAM = 'Pnnnn-F1'
      BDCDATA-FVAL = SATZ-F1
      APPEND BDCDATA.
      CLEAR BDCDATA.
      BDCDATA-FNAM = 'BDC_OKCODE'.
      BDCDATA-FVAL = '=UPD'.
      APPEND BDCDATA.
    ENDFORM.
    The FORM Dnnnn is called directly after FORM D0008; see the ABAP statement indicated as "<------ INSERT in the following (starting at line 1730 in the standard system):
      LOOP AT INFTAB.
        CASE INFTAB.
    Include all infotypes in your action *
         WHEN '0002'. PERFORM D0002.
         WHEN '0001'. PERFORM D0001.
         WHEN '0006'. PERFORM D0006.
         WHEN '0007'. PERFORM D0007.
         WHEN '0008'. PERFORM D0008.
         WHEN 'nnnn'. PERFORM Dnnnn.         "<------ INSERT
         WHEN OTHERS. WRITE: / 'Infotype not included:' (008), INFTAB.
                       STOP.
       ENDCASE.
    ENDLOOP.
    Parameter DSLOGNAM
    Logical file name
    Parameter MAPNAME
    Session name
    Definition
    Enter any name for the session to be created.

  • Standard programs to upload / update infotypes

    Please provide updates for this question:
    What are the standard SAP programs to update infotypes ( Ex: 001 / 002 / 003 ) .
    I will be uploading data from legacy system ( Excel / Text file ) and would like to use standard programs
    before going ahead with BDC .
    Thanks
    Rohan

    Please provide updates for this question:
    What are the standard SAP programs to update infotypes ( Ex: 001 / 002 / 003 ) .
    I will be uploading data from legacy system ( Excel / Text file ) and would like to use standard programs
    before going ahead with BDC .
    Thanks
    Rohan
    Hi Rohan ,
         you can update you infotype using 'HR_INFOTYPE_OPERATION' function module .
    1)   transfer all your excel data  into internal table .
    2)   loop at internal table
    3)  fill all the required field of that infotype .
    4) lock table
    5) call that functuion module .
    6) unlock table
    for this fallow the below code...
    DATA: it_p0169 TYPE STANDARD TABLE OF pa0169 WITH HEADER LINE.  (make internal table according to your requirment)
    DATA: wa_p0169  TYPE p0169.
    LOOP AT it_file
          v_eeamt = it_file-pct_gross.
    *Pre-Tax Contribution Percentage
          v_eepct = v_eeamt / 10.
          v_begda = it_file-datchngd .
    *Appending into header (these all are the required filed in my case )
         it_p0169-eeamt =  v_eeamt.
          it_p0169-begda =  v_begda.
          it_p0169-eepct =  v_eepct.
          it_p0169-bplan =  v_bplan .
          CLEAR wa_p0169.
          MOVE-CORRESPONDING it_p0169 TO wa_p0169.
          wa_p0169-INFTY = '0169'.    (not forget to pass infotype no in the header )
    CONSTANTS: c_action_ins  TYPE pspar-actio VALUE 'MOD',   (it can be also COP for Copy , DEL for Delete , DIS for Display , MOD to Change , LIS9 to  Delimit , INS to Create )
               c_infty_0169  TYPE prelp-infty VALUE '0169'.
    DATA: it_return  TYPE bapireturn1. (as it is )
    DATA: it_return  TYPE bapireturn1.
      CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
        EXPORTING
          number = p_pernr
        EXCEPTIONS
          OTHERS = 1.
      IF sy-subrc <> 0.
         RAISE enqueue_FAILED.
      ENDIF.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
      EXPORTING
        infty                  = c_infty_0169
        number                 = p_wa_0169-pernr
        SUBTYPE                = '401K'
        OBJECTID               =
        LOCKINDICATOR          =
        validityend            = p_wa_0169-endda
        validitybegin          = v_begda1
        RECORDNUMBER           =
        record                 = p_wa_0169
        operation              = c_action_ins
        TCLAS                  = 'A'
        DIALOG_MODE            = '0'
        NOCOMMIT               =
        VIEW_IDENTIFIER        =
        SECONDARY_RECORD       =
      IMPORTING
        return                 = it_return.
       if it_return-MESSAGE is not initial .
         delete it_file .
       endif.
    commit work .
      CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
        EXPORTING
          number = p_pernr
        EXCEPTIONS
          OTHERS = 1.
      IF sy-subrc <> 0.
         RAISE DEQUEUE_FAILED.
      ENDIF.
    Enjoy
    Priyank

  • Problem updating Infotype 1208 subtype ALUM

    Hi,
    My requirement is to update the infotype 1208 subtype ALUM with the Value "YES" when I terminate a employee in PA40.   ( immediately).
    I am using the FM - HR_INFOTYPE_OPERATION which doesn't seem to work.
    I tried running a BDC for PA30 , but it is not allowing me to edit the employee and says that i am processing him.
    I feel this is an issue with locks. But not sure about how to go with.
    Are there any standard classes available or any other method to use to update this infotype while terminating.
    Regards,
    Karan.

    1) as suggested by Suresh first check the return table to know exaclty the error mesage.
    2) u can update a IT with same values i don think it wil have a problem
    3) to me it looks that it is due to PERNR locked ,as when u r updating it first time the pernr is locked and when u r trying to update it again in the same session it must be failing due to pernr looked..
    so before using FM to update IT ,use Fm -
    CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
      EXPORTING
        NUMBER        = number .
    IMPORTING
      RETURN        =          .
    and after tht call FM to update IT and then call below FM to unlock employee-
    CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
      EXPORTING
        NUMBER        = number.
    IMPORTING
      RETURN        =          .
    this will solve ur probelm .
    amit

  • Function to update Infotype 0003

    Hi,
    I want to update 'Run payroll up to' field of infotype 0003 based on some conditions .
    Is there any function module to update Infotype 0003 fields ?
    Thanks

    I have calle the FM with action 'EDQ'  .
    It did not uloack the pernr .
    I am using this code :
    SELECT SINGLE STAT2
      INTO LV_STAT2
      FROM  PA0000
      WHERE PERNR =  INNNN-PERNR AND
            ENDDA >= INNNN-BEGDA AND
            BEGDA <= INNNN-ENDDA .
      IF SY-SUBRC = 0 AND
        LV_STAT2 <> '3'  .
        CALL FUNCTION 'HR_READ_INFOTYPE'
          EXPORTING
            PERNR           = INNNN-PERNR
            INFTY           = '0003'
          IMPORTING
            SUBRC           = LV_SUBRC_1
          TABLES
            INFTY_TAB       = IT_PA0003
          EXCEPTIONS
            INFTY_NOT_FOUND = 1
            OTHERS          = 2.
        IF LV_SUBRC_1 = 0 .
          READ TABLE IT_PA0003 INDEX 1  .
          CHECK SY-SUBRC = 0 .
          WA_PA0003 = IT_PA0003 .
          IF INNNN-BEGDA >  IT_PA0003-ABWD1  .
         Reset the  "Run payroll for pers.no. up to" date
            WA_PA0003-ABWD1 = INNNN-BEGDA  .
            CALL FUNCTION 'HR_INFOTYPE_OPERATION'
              EXPORTING
                INFTY                  = '0003'
                NUMBER                 = INNNN-PERNR
                RECORD                 =  WA_PA0003
                OPERATION              = 'EDQ'
             IMPORTING
               RETURN                 =  LV_SUBRC_2          .
            CALL FUNCTION 'HR_INFOTYPE_OPERATION'
              EXPORTING
                INFTY                  = '0003'
                NUMBER                 = INNNN-PERNR
                VALIDITYEND            = WA_PA0003-ENDDA
                VALIDITYBEGIN          = WA_PA0003-BEGDA
                RECORD                 =  WA_PA0003
                OPERATION              = 'MOD'
                NOCOMMIT               =  'X'
             IMPORTING
               RETURN                 =  LV_SUBRC_2

  • Update Infotype 1016

    Hi,
    I have to update Infotype 1016 using the BAPI FM "BAPI_HRMASTER_SAVE_REPL_MULT".
    Two tables need to get updated, HRP1016 & HRT1016.
    The Data in the HRT 1016 is a Table Data for Record in HRP1016.
    Say: Orgunit O 10000001 has two standrd Profiles..
    IF I go to PP01 and create the two standard profiles,
    I will have a single record in HRP1016 which has a TABNR field value generated.
    Now for this TABNR, I have two record in HRT1016 each corresponding to one Profile.
    I need to create these three ( 1 + 2 ) entries using the FM. The FM has Input structure BAPIHR1016 which allows only one profile per structure. Also it asks for the TABNR field, which I donot know until the actual creation.
    If I send one profile & TAB_SEQNR as 00001, its working fine, generating a TABNR for me.
    But when I send two records in the FM, one with TAB_SEQNR 00001 & other with TAB_SEQNR 00002, the second one is overwriting the first one, and I have only the second profile assigned.
    Please help solve this issue.
    Thanks in Advance.
    Suryakiran D.

    For updating the IT 1011, we have 6 fields in the BAPI.
    But when I go to PP01, i have only one field in input mode, rest all are disabled for input.
    Even if I fill the values in all the fields, only one is considered for update, and rest all are recalculated using this.
    Can someone please let me know how we can decide this.
    Thanks,
    Surya

  • UPDATING INFOTYPE

    Hi Experts
    I have one problem in updating infotype using
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
    EXPORTING
    INFTY = '2001'
    NUMBER = pernr
    SUBTYPE = subtype
    VALIDITYBEGIN = validitybegin
    VALIDITYEND = validityend
    RECORD = wa_inf_2001
    OPERATION = action "INS,MOD
    IMPORTING
    RETURN = return
    KEY = key
    EXCEPTIONS
    OTHERS = 3.
    This is working fine for first time operation but when i want to overwrite it .
    Is is displaying as page can not be displayed .
    i.e if updating infotype with same veluse for two times
    i.e duplicationg the values then it is showing error .How to solve it
    Thanks
    Prasad

    1) as suggested by Suresh first check the return table to know exaclty the error mesage.
    2) u can update a IT with same values i don think it wil have a problem
    3) to me it looks that it is due to PERNR locked ,as when u r updating it first time the pernr is locked and when u r trying to update it again in the same session it must be failing due to pernr looked..
    so before using FM to update IT ,use Fm -
    CALL FUNCTION 'BAPI_EMPLOYEE_ENQUEUE'
      EXPORTING
        NUMBER        = number .
    IMPORTING
      RETURN        =          .
    and after tht call FM to update IT and then call below FM to unlock employee-
    CALL FUNCTION 'BAPI_EMPLOYEE_DEQUEUE'
      EXPORTING
        NUMBER        = number.
    IMPORTING
      RETURN        =          .
    this will solve ur probelm .
    amit

  • Class to update infotype

    Hi friends,
    Can you please give the details of class(not HR_INFOTYPE_OPERATION) for updating infotypes?
    Thanks in advance,
    Anu

    Hi Anu,
    If "Class " mentioned by you related to time constrins,
    A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:
    1: An infotype record must be available at all times. This record may have no time gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.
    2: Only one record may be available at one time, but time gaps are permitted.
    3: Any number of records may be valid at one time, and time gaps are permitted.
    Other possible time constraint indicators are as follows:
    A: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
    View V_T582B Infotypes Which are Created Automically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action.
    Infotypes with time constraint A may not be deleted.
    B: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
    Infotypes with time constraint B may be deleted.
    T: The time constraint varies depending on the subtype.
    Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y Time Constraint Reaction.

  • Update infotype 7407

    Hi,
    I need to do a program to update infotype 7407(Career Goal).
    However, I have difficulties in updating fields COMMENT_CLASS and COMMENT_ID.
    These 2 fields are the fields that will be updated if I edit the Career Goal from the portal with notes.
    How do I update notes to this infotype 7407?
    Thanks

    I found the solution for this.
    Use class cl_hrtmc_ac_career_goals to update Career goals.
    To modify the text, use method modify_comment
    At last, to save the infotype, call method SAVE from class cl_hrtmc_ac_tb

  • Updating infotype 1007

    Hello experts,
    I need to update the IT 1007 marking a position as Vacant.
    Is this can be done using a Function Module? like the one that updates infotype in the PA30 (HR_INFOTYPE_OPERATION) ?
    Thanks in advance for your help,
    ArepaKing

    Dear King,
    Not much sure but kindly have a look at function module :-
    RH_UPDATE_INFTY
    Short Text
    Change infotype records
    Functionality
    With this function module you can change multiple infotype records for OM objects from Personnel Planning database tables (HRPnnnn). The infotype tables of the table parameter INNNN must all have the structure Pnnnn (logical structure for the infotype nnnn). The records you want to change must exist in the Personnel Planning database tables. If not, this triggers the exception ERROR_DURING_UPDATE.
    Might be other members can have some more better ideas as well.
    Hope this helps.
    Kindly reward in case useful.
    Regards & Thanks,
    Darshan Mulmule

  • Updating infotypes

    Hi Experts
    I have one problem in updating infotype using
    CALL FUNCTION 'HR_INFOTYPE_OPERATION'
            EXPORTING
              INFTY                  = '2001'
              NUMBER                 = pernr
              SUBTYPE                = subtype
              VALIDITYBEGIN          = validitybegin
              VALIDITYEND            = validityend
              RECORD                 = wa_inf_2001
              OPERATION              = action  "INS,MOD
          IMPORTING
             RETURN                  = return
             KEY                     = key
          EXCEPTIONS
             OTHERS           = 3.
    This is working  fine for first time operation but when i want to overwrite it .
    Is is displaying as page can not be displayed .
    i.e if  updating infotype with same veluse for two times
    i.e duplicationg the values then it is showing error .How to solve it
    Thanks
    Prasad

    <i>This is working fine for first time operation but when i want to overwrite it .
    </i>
    To Insert, you need to pass the action 'INS'
    To Modify action needs to be 'MOD'
    <i>ts is displaying as page can not be displayed .</i>
    To get the exact error message, please do the following settings in IE Browser:
    Tools -->Internet option--> Advanced(Tab) uncheck the "Show Friendly HTTP error messages".
    Raja T

Maybe you are looking for

  • How do I find available available storage on Macbook Pro OS X?

    I have looked in About this Mac under the Apple symbol but the More Information does not give storage information as advised at the Apple Shop. Would welcome help. Thanks

  • Regarding oracle ERP

    Hi, We are using oracle financials 1.we need to know the base tables for the following modules Cash management Account payables Account Receivables General Ledger Purchase 2.We need to know the API's used in these modules. Waiting for ur valuable rep

  • Experience on new V125?

    Hello, I'm wondering about some hardware details of the new V125s. According to sun.com website it ships with 1.0 Ghz UltraSPARC IIIi, will that one be approx. comparable to an older V210 with 1GHz UltraSPARC IIIi or are there more things to think ab

  • How do I access my photos in Elements 10 by using Revel which does recognise albums by name?

    How do I access my photos in Elements 10 from Revel which does not recognised named albums?

  • Wl-plugin sp4: ap_proxy deadlock warning

    Running weblogic 8.1 SP4 & Apache 2.0.54 on Solaris 8. Following the upgrade of the WL-plugin mod_wl_20.so to SP4 version we are getting intermittent warnings in the apache error log: [warn] (45)Deadlock situation detected/avoided: ap_proxy: couldn't