Lock management error in bapi /SAPMP/BAPI_ROUTING_PROCESS of ECC 6.0 system

Hello Experts,
I am trying to use this bapi /SAPMP/BAPI_ROUTING_PROCESS for changing the routing. Am marking the change mode in import parameters of this bapi and filling the task, material allocation, sequence and operation tables with tasklist and group.
On executing this bapi, i am getting several errors like "Header cannot be locked(lock management error) in task table and "Operation cannot be locked(lock management error) in operation table.
Please help me out of this issue.
Regards,
Vijayalakshmi

You have to fill parameter WORKAREA with the value from tcode op77

Similar Messages

CA02 Routing change with /SAPMP/BAPI_ROUTING_PROCESS

Hello ,
I am using /SAPMP/BAPI_ROUTING_PROCESS BAPI to change Standard values VGW02 field , I m getting the below errors ,
Operation cannot be locked (lock management error)
Operation cannot be locked (lock management error)
Please advise about what am i missing in passing parameters to BAPI.
Thanks

Hi,
Are you uploading using program or lsmw.In some bapis there is an issue like locking.Please check using lsmw.
Regards,
Madhu.

An error occurred in lock management when attempting to set a lock on table

Hi All,
I am getting the error 'An error occurred in lock management when attempting to set a lock on table SWWWIHEAD.'
Sometimes the workitem is not created by the Workflow due to above error & this happens rarely but keeps coming.
cany anyone guide or help me how to correct this problem.Is it happening due to my custom code making locks on the above table?
Thanks in advance.
Pls do reply

I think you should not use any code to lock the table SWWWIHEAD. Please let us know why you are writing code to put lock on this table.
Thanks
Arghadip

Error in lock management

Hi
I am getting error in lock management when I am assiging role to user.
when i am saving user after assiging role to user...I am getting this error"error in lock mangement"
Regards
Tarun

Hi,
Please check SAP note https://service.sap.com/sap/support/notes/746138.
Use transaction SM12 (client specific)to obtain the raw information and the following selection data in particular:
Client: "#01"
User name: "#01_002"
Table: "#01_002"
Argument: "#01_002".
Check sm12 on regular basis. It may be due to a user using a Table which is causing lock. U need to forcefully log off that user id.
Check and let us know if any issue.
Regards
Aveek.

Intenal error in SAP lock management system

Hi All,
I got an error like this:
"An internal error was found in SAP lock management system when attempting to lock an object by calling an ENQUEUE functional module".
Can you provide me a solution as soon as possible..
Thanks in advance,
Sreepathi

Hi Sreepathi,
Usually this happen when the enque process is no longer accesible. I will schedule a system and db restart.
Regards
Juan
Please reward with points if helpful

System Error occured during lock management in activating BI Content.

In trying to activate BI content, 'InfoObject Actual for Netweaver Demo', on clicking install after selecting the grouping settings, i get the error message
"System error occurred during lock management"
What causes this problem and how do i successfully install BI content?. Please assist.

Hi,
The error indicates missing or inactive message/enqueue server or network problems.
Please follow the steps below to help troubleshoot the problem
1. Logon to each server separately and goto SM12->Extras->Diagnostics to test the connections for the enqueue server. This will test the access of each server.
2 Use SMGW and SM59 to test the RFC connections. See SAP Note 47682.
You may want to have your network administrator/Basis people test the connections & analyse the network.
Use the message server/logon group testing tool "lgtst" (Note 64015), & the "niping" program (Note 500235) to diagnose the network.
Have a look at attached note 124562 in order to check if you have a hostname resolution problem.
Check your DNS / network setting that this kind of problems can not lead to blocking situations of the dispatcher.
To avoid the blocking of the dispatcher you can set the parameter
rdisp/reverse_name_lookup = 0 to avoid such situations.
Best of luck.
Rgds,
Colum

ERROR - A system error has occured in lock management

Dear All ,
I have a major issue in my workflow in production client . In SWEL there are some workflows which
got started & then error occured as per the message " A system error has occured in lock management " and no workitem gets created .
This issue happened just 1 day back and still continues somtimes .
If any one have any idea on the issue , what is the root cause of the issue , please suggest how to solve the same .
Regards
Prabhu

No WF-BATCH is not locked . This issue does not happen every time , it happens some times .other wise workflow runs fine .
I will tell you when i checked abot the error message by clicking F1 help i got the below message details-
An error occurred in lock management when attempting to set a lock on table SWWWIHEAD.
The data cannot be processed at the moment. The data is displayed.
So i think there is some issue happens in updating the entry in the table which happens some times , and gets rectified automatically . But the workflow which gets affected by this error does not start .
so any idea on the same .
Regards
Prabhu

Transpot error" system error in lock managment"

Hi ,
When Iu2019m transporting infoobjects from BI DEV to BI Q while importing its showing u201Csystem error in lock managementu201D.
When I drill down the error its showing the following message.
Message no. AD025
Diagnosis
A system error has occurred in the lock management function.
The system was unable to determine whether a lock entry existed for the selected object.
System Response
The selected object could not be locked.
Only display mode can be used.
Procedure
Make a note of the error code and inform your system administrator
And In the error its not showing specific infoobjects ,when I searched forums I got one note 928044, but I skeptic that it works .
Please provide some inputs ASAP.
Thanks
chaitu

You didn't mention whether you are seeing this error message while building the transport/request or at the time of applying on BIQ....
Anyways, if you are seeing this message while trying to create a new transport for your infoobjects:
Please make sure all your infoobjects are not in any other *open" requests already? That is, if you have any other requests that are still open, try "releasing" them before trying to create the new transport/request.
Hope this helps.

An internal error was found in the SAP lock management system when opening

Hello SDN Experts ,
When i am trying to open any t-ocde in my productive system
it is displaying an error message "An internal error was found in the SAP lock management system " , not only for me but also for all the users .
Could please tell me what colud be the problem and solution for this??
it's very urgent .....
Thanks in Advance !
Siva reddy

Hi,
Check in SM12 if tht particular Tcode is being locked by some other person.
Else contact your basis team. There may be some auth issues.
Regards,
Lalit

System error occur during lock managment?

Hi all !
When I open the adminstrator workbench I am gettting the error " System lock occured during lock managment.
I can open other sessions such as RSPC, RRMX etc.
Can anyone help in this regard?
Regards
Durai

Hi,
I can suggest how to access administratoe workbench without using T.code:RSA1.
Go to T.code RSD1 then in Menu >Environment>Object Browser via AWB.
Try this for time being to access RSA1 and inform to BASIS guy he will solve the problem.
Assign points if helpful
Thanks & Regards,
Bala

Error during BAPI while uploading Material data through MM01

Hi all,
i am facing one problem when uploading Material data thorough BAPI in MM01.i am attaching the code below and the error given.
but in the debugger all the value is being stored.
REPORT ZFINISHED_MAT.
Data: Begin of legacy_data occurs 0,
     MATNR LIKE MARA-MATNR,
     MBRSH LIKE MARA-MBRSH,            "Industry Sector
     MTART LIKE MARA-MTART,            "Matl Type
     WERKS LIKE MARD-WERKS,            "Plant
     LGORT LIKE MARD-LGORT,            "Storage location
     VKORG LIKE MVKE-VKORG,
     VTWEG LIKE MVKE-VTWEG,
     MAKTX LIKE MAKT-MAKTX,             "Matl Desc.
     MEINS LIKE MARA-MEINS,             "Base UOM
     MATKL LIKE MARA-MATKL,             "Matl.Grp
*     BISMT LIKE MARA-BISMT,
     SPART LIKE MARA-SPART,             "Division
*     BRGEW LIKE MARA-BRGEW,             "Gross weight
     GROES LIKE MARA-GROES,
     FERTH LIKE MARA-FERTH,
     ZEINR LIKE MARA-ZEINR,
     TAXKM1 LIKE MLAN-TAXM1,
     TAXKM2 LIKE MLAN-TAXM2,
     TAXKM3 LIKE MLAN-TAXM3,
     TAXKM4 LIKE MLAN-TAXM4,
     KTGRM LIKE MVKE-KTGRM,
*     GEWEI LIKE MARA-GEWEI,             "Weight unit
*     NTGEW LIKE MARA-NTGEW,             "Net weight
*     KLART LIKE RMCLF-KLART,
     MTVFP LIKE MARC-MTVFP,             "Availibility Check
*     XGCHP LIKE MARA-XGCHP,
     XCHPF LIKE MARA-XCHPF,             "Batch Management
     TRAGR LIKE MARA-TRAGR,
     LADGR TYPE MARC-LADGR,
     VPRSV LIKE MBEW-VPRSV,            "Price Control
     VERPR LIKE MBEW-VERPR,
*     SPRAS LIKE MAKT-SPRAS,
END OF LEGACY_DATA.
DATA: BEGIN OF IT_MAKT OCCURS 0.
INCLUDE STRUCTURE BAPI_MAKT.
DATA: END OF IT_MAKT.
*--- BAPI structures
DATA: BAPI_HEAD LIKE BAPIMATHEAD, " Header Segment with Control Information
BAPI_MAKT LIKE BAPI_MAKT, " Material Description
BAPI_MARA1 LIKE BAPI_MARA, " Client Data
BAPI_MARAX LIKE BAPI_MARAX, " Checkbox Structure for BAPI_MARA
BAPI_MARD1 LIKE BAPI_MARD,
BAPI_MARDX1 LIKE BAPI_MARDX, " Checkbox Structure for BAPI_MARD
BAPI_MARC1 LIKE BAPI_MARC, " Plant View
BAPI_MARCX LIKE BAPI_MARCX, " Checkbox Structure for BAPI_MARC
BAPI_MVKE1 LIKE BAPI_MVKE,
BAPI_MVKEX1 LIKE BAPI_MVKEX, " Checkbox Structure for BAPI_MVKE
BAPI_MLAN1 LIKE BAPI_MLAN,
BAPI_MLANX1 LIKE bapi_mlan1, " Checkbox Structure for BAPI_MLAN
BAPI_MBEW1 LIKE BAPI_MBEW, " Accounting View
BAPI_MBEWX LIKE BAPI_MBEWX, " Checkbox Structure for BAPI_MBEW
BAPI_RETURN LIKE BAPIRET2. " Return Parameter
*              $PARAMETERS DECLARATION$
SELECTION-SCREEN BEGIN OF BLOCK B11
                          WITH FRAME TITLE TEXT-001.
PARAMETERS: P_FILE LIKE RLGRAP-FILENAME. " DEFAULT 'C:\TEST1.XLS'.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN ULINE.
SELECTION-SCREEN END OF BLOCK B11 .
*              $DATA DECLARATION$
*DATA : BDC_DATA LIKE STANDARD TABLE OF BDCDATA WITH HEADER LINE.
DATA : IT_EXCEL TYPE STANDARD TABLE OF ALSMEX_TABLINE INITIAL SIZE 0 WITH HEADER LINE,
        IT_EXCEL_DUMMY TYPE ALSMEX_TABLINE.
DATA : MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : L_MSTRING(480).
DATA :L_SUBRC LIKE SY-SUBRC.
DATA: V_FILE TYPE STRING.
*              $AT-SELECTON SCREEN DECLARATION$
AT SELECTION-SCREEN ON P_FILE.
IF P_FILE IS INITIAL.
    MESSAGE E398(00) WITH 'FILE NAME NEEDS TO BE SPECIFIED'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FILE.
CALL FUNCTION 'F4_FILENAME'
   EXPORTING
     PROGRAM_NAME        = SYST-CPROG
*   DYNPRO_NUMBER       = SYST-DYNNR
     FIELD_NAME          = 'P_FILE'
   IMPORTING
     FILE_NAME           = P_FILE
start-of-selection.
perform data_fetch_to_xls.
perform insertion.
*&      Form data_fetch_to_xls
*       text
* --> p1        text
* <-- p2        text
FORM data_fetch_to_xls .
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      FILENAME                = P_FILE
      I_BEGIN_COL             = 1
      I_BEGIN_ROW             = 2
      I_END_COL               = 25
      I_END_ROW               = 2
    TABLES
      INTERN                  = IT_EXCEL
    EXCEPTIONS
      INCONSISTENT_PARAMETERS = 1
      UPLOAD_OLE              = 2
      OTHERS                  = 3.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    WRITE: /'ERROR UPLOADING XLS FILE FROM PRESENTATION SERVER !' ,
           /'RETURN CODE : ', SY-SUBRC.
ELSE.
*************NOW FILL DATA FROM EXCEL INTO FINAL LEGACY DATA ITAB----LEGACY_DATA***************
    IF NOT IT_EXCEL[] IS INITIAL.
      CLEAR LEGACY_DATA.
      REFRESH LEGACY_DATA[].
      LOOP AT IT_EXCEL.
        IT_EXCEL_DUMMY = IT_EXCEL.
        AT NEW COL.
          CASE IT_EXCEL_DUMMY-COL.
            WHEN 1.
              LEGACY_DATA-MATNR = IT_EXCEL_DUMMY-VALUE(18).
            WHEN 2.
              LEGACY_DATA-MBRSH = IT_EXCEL_DUMMY-VALUE(1).
            WHEN 3.
              LEGACY_DATA-MTART = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 4.
              LEGACY_DATA-WERKS = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 5.
              LEGACY_DATA-LGORT = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 6.
              LEGACY_DATA-VKORG = IT_EXCEL_DUMMY-VALUE(4).
             WHEN 7.
              LEGACY_DATA-VTWEG = IT_EXCEL_DUMMY-VALUE(2).
            WHEN 8.
              LEGACY_DATA-MAKTX = IT_EXCEL_DUMMY-VALUE(40).
            WHEN 9.
              LEGACY_DATA-MEINS = IT_EXCEL_DUMMY-VALUE(3).
            WHEN 10.
              LEGACY_DATA-MATKL = IT_EXCEL_DUMMY-VALUE(9).
            WHEN 11.
              LEGACY_DATA-SPART = IT_EXCEL_DUMMY-VALUE(2).
            WHEN 12.
              LEGACY_DATA-GROES = IT_EXCEL_DUMMY-VALUE(32).
            WHEN 13.
              LEGACY_DATA-FERTH = IT_EXCEL_DUMMY-VALUE(18).
            WHEN 14.
              LEGACY_DATA-ZEINR = IT_EXCEL_DUMMY-VALUE(22).
             WHEN 15.
              LEGACY_DATA-TAXKM1 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 16.
              LEGACY_DATA-TAXKM2 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 17.
              LEGACY_DATA-TAXKM3 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 18.
              LEGACY_DATA-TAXKM4 = IT_EXCEL_DUMMY-VALUE(1).
             WHEN 19.
              LEGACY_DATA-KTGRM = IT_EXCEL_DUMMY-VALUE(2).
            WHEN 20.
              LEGACY_DATA-MTVFP = IT_EXCEL_DUMMY-VALUE(2).
             WHEN 21.
              LEGACY_DATA-XCHPF = IT_EXCEL_DUMMY-VALUE(1).
            WHEN 22.
              LEGACY_DATA-TRAGR = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 23.
              LEGACY_DATA-LADGR = IT_EXCEL_DUMMY-VALUE(4).
            WHEN 24.
              LEGACY_DATA-VPRSV = IT_EXCEL_DUMMY-VALUE(1).
            WHEN 25.
              LEGACY_DATA-VERPR = IT_EXCEL_DUMMY-VALUE(14).
              APPEND LEGACY_DATA.
              CLEAR LEGACY_DATA.
          ENDCASE.
        ENDAT.
        AT END OF ROW.
        ENDAT.
      ENDLOOP.
    ENDIF.
ENDIF.
ENDFORM.                    " data_fetch_to_xls
*&      Form insertion
*       text
* --> p1        text
* <-- p2        text
FORM insertion .
LOOP AT legacy_data.
* Header
BAPI_HEAD-MATERIAL = legacy_data-MATNR.
BAPI_HEAD-IND_SECTOR = legacy_data-MBRSH.
BAPI_HEAD-MATL_TYPE = legacy_data-MTART.
BAPI_HEAD-BASIC_VIEW = 'X'.
BAPI_HEAD-SALES_VIEW = 'X'.
BAPI_HEAD-STORAGE_VIEW = 'X'.
*BAPI_HEAD-PURCHASE_VIEW = 'X'.
BAPI_HEAD-ACCOUNT_VIEW = 'X'.
* Material Description
REFRESH IT_MAKT.
*IT_MAKT-LANGU = legacy_data-SPRAS.
IT_MAKT-MATL_DESC = legacy_data-MAKTX.
APPEND IT_MAKT.
BAPI_MARD1-PLANT = legacy_data-WERKS.
BAPI_MARD1-STGE_LOC = legacy_data-LGORT.
BAPI_MARDX1-PLANT = legacy_data-WERKS.
BAPI_MARDX1-STGE_LOC = legacy_data-LGORT.
** Client Data - Basic
BAPI_MARA1-MATL_GROUP = legacy_data-MATKL.
*bapi_mara1-OLD_MAT_NO = legacy_data-bismt.
BAPI_MARA1-BASE_UOM = legacy_data-MEINS.
BAPI_MARA1-PROD_MEMO = LEGACY_DATA-FERTH.
BAPI_MARA1-SIZE_DIM = LEGACY_DATA-GROES.
BAPI_MARA1-DOCUMENT = LEGACY_DATA-ZEINR.
BAPI_MARA1-BATCH_MGMT = LEGACY_DATA-XCHPF.
*BAPI_MARA1-UNIT_OF_WT = legacy_data-GEWEI.
BAPI_MARA1-TRANS_GRP = legacy_data-TRAGR.
BAPI_MARA1-DIVISION = legacy_data-SPART.
BAPI_MARAX-MATL_GROUP = 'X'.
*BAPI_MARAX-OLD_MAT_NO = 'X'.
BAPI_MARAX-BASE_UOM = 'X'.
BAPI_MARAX-PROD_MEMO = 'X'.
BAPI_MARAX-SIZE_DIM = 'X'.
BAPI_MARAX-DOCUMENT = 'X'.
BAPI_MARAX-BATCH_MGMT = 'X'.
*BAPI_MARAX-UNIT_OF_WT = 'X'.
BAPI_MARAX-TRANS_GRP = 'X'.
BAPI_MARAX-DIVISION = 'X'.
*SALES
BAPI_MVKE1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKE1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKE1-DELYG_PLNT = legacy_data-DWERK.
BAPI_MVKE1-ACCT_ASSGT = legacy_data-KTGRM.
BAPI_MVKEX1-SALES_ORG = legacy_data-VKORG.
BAPI_MVKEX1-DISTR_CHAN = legacy_data-VTWEG.
*BAPI_MVKEX1-DELYG_PLNT = 'X'.
BAPI_MVKEX1-ACCT_ASSGT = 'X'.
** Plant - Purchasing
BAPI_MARC1-PLANT = legacy_data-WERKS.
BAPI_MARC1-LOADINGGRP = legacy_data-LADGR.
BAPI_MARC1-AVAILCHECK = legacy_data-MTVFP.
*BAPI_MARC1-MRP_GROUP = legacy_data-disgr.
BAPI_MARCX-PLANT = legacy_data-WERKS.
BAPI_MARCX-LOADINGGRP = 'X'.
BAPI_MARCX-AVAILCHECK = 'X'.
*BAPI_MARCX-MRP_GROUP = 'X'.
* Accounting
BAPI_MBEW1-VAL_AREA = legacy_data-WERKS.
BAPI_MBEW1-PRICE_CTRL = legacy_data-VPRSV.
BAPI_MBEW1-STD_PRICE = legacy_data-VERPR.
*BAPI_MBEW1-VAL_CLASS = legacy_data-BKLAS.
*BAPI_MBEW1-STD_PRICE = legacy_data-STPRS.
*BAPI_MBEW1-PRICE_UNIT = legacy_data-PEINH.
BAPI_MBEWX-VAL_AREA = legacy_data-WERKS.
BAPI_MBEWX-PRICE_CTRL = 'X'.
BAPI_MBEWX-STD_PRICE = 'X'.
*BAPI_MBEWX-VAL_CLASS = 'X'.
* TAX JURISDICTION CODE
BAPI_MLAN1-TAXCLASS_1 = LEGACY_DATA-TAXKM1.
BAPI_MLAN1-TAXCLASS_2 = LEGACY_DATA-TAXKM2.
BAPI_MLAN1-TAXCLASS_3 = LEGACY_DATA-TAXKM3.
BAPI_MLAN1-TAXCLASS_4 = LEGACY_DATA-TAXKM4.
BAPI_MLAN1-TAXCLASS_1 = 'X'.
BAPI_MLAN1-TAXCLASS_2 = 'X'.
BAPI_MLAN1-TAXCLASS_3 = 'X'.
BAPI_MLAN1-TAXCLASS_4 = 'X'.
*--- BAPI to create material
call function 'BAPI_MATERIAL_SAVEDATA'
exporting
HEADDATA = BAPI_HEAD
CLIENTDATA = BAPI_MARA1
CLIENTDATAX = BAPI_MARAX
*PLANTDATA = BAPI_MARC1
*PLANTDATAX = BAPI_MARCX
* FORECASTPARAMETERS =
* FORECASTPARAMETERSX =
* PLANNINGDATA =
* PLANNINGDATAX =
* STORAGELOCATIONDATA =
* STORAGELOCATIONDATAX =
VALUATIONDATA = BAPI_MBEW1
VALUATIONDATAX = BAPI_MBEWX
* WAREHOUSENUMBERDATA =
* WAREHOUSENUMBERDATAX =
* SALESDATA = BAPI_MVKE1
* SALESDATAX = BAPI_MVKEX
* STORAGETYPEDATA =
* STORAGETYPEDATAX =
IMPORTING
RETURN = BAPI_RETURN
TABLES
MATERIALDESCRIPTION = IT_MAKT
* UNITSOFMEASURE =
* UNITSOFMEASUREX =
* INTERNATIONALARTNOS =
* MATERIALLONGTEXT =
* TAXCLASSIFICATIONS =
* RETURNMESSAGES =
* PRTDATA =
* PRTDATAX =
* EXTENSIONIN =
* EXTENSIONINX =
IF BAPI_RETURN-TYPE = 'E'.
WRITE:/ 'Error:' ,BAPI_RETURN-MESSAGE ,'for material:' ,legacy_data-maTNR.
ELSEIF BAPI_RETURN-TYPE = 'S'.
WRITE: 'Successfully created material' ,legacy_data-maTNR.
ENDIF.
ENDLOOP.
ENDFORM.                    " insertion
The error: The field MARC-MTVFP/BAPI_MARC-AVAILCHECK is defined as a required field; it does not contain an entr
suggestion will be vry helpful,
Kind Regards,
Edited by: Prasenjit Sengupta on Nov 16, 2009 9:11 AM

Hi Prasenjit,
Did you get any solution for this as I am getting same error from BAPI to update MRP controller in MARC table.
Regards,
Suruchi

EJB Primary Key not found in lock manager - Container BUG?

I have an EJB entity bean whose primary key class implementation is pretty simple, consisting of two strings. For the MOST part, it seems to work properly, but every so often I see the following message in my application server log.
####<Sep 17, 2008 10:03:27 AM EDT> <Warning> <JTA> <armantac22> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1221660207187> <BEA-110401> <Ignoring error in afterCompletion. Object=weblogic.ejb.container.internal.TxManager$TxListener@1906466, Exception=javax.ejb.EJBException: [EJB:010108]The EJB Lock Manager has received an unlock request from EJB:PortfolioMetaData with primary key:[ObjectPK: type: PortMetaData name: PortMetaData]. However, this primary key could not be found in the Lock Manager. This indicates either an EJB container bug, or the equals and hashCode methods for the primary key class:com.armanta.ejb.ObjectPK are implemented incorrectly. Please check the equals and hashCode implementations.
javax.ejb.EJBException: [EJB:010108]The EJB Lock Manager has received an unlock request from EJB:PortfolioMetaData with primary key:[ObjectPK: type: PortMetaData name: PortMetaData]. However, this primary key could not be found in the Lock Manager. This indicates either an EJB container bug, or the equals and hashCode methods for the primary key class:com.armanta.ejb.ObjectPK are implemented incorrectly. Please check the equals and hashCode implementations.
     at weblogic.ejb.container.locks.ExclusiveLockManager$LockBucket.unlock(ExclusiveLockManager.java:409)
     at weblogic.ejb.container.locks.ExclusiveLockManager.unlock(ExclusiveLockManager.java:170)
     at weblogic.ejb.container.manager.ExclusiveEntityManager.afterCompletion(ExclusiveEntityManager.java:723)
     at weblogic.ejb.container.manager.ExclusiveEntityManager.afterCompletion(ExclusiveEntityManager.java:667)
     at weblogic.ejb.container.internal.TxManager$TxListener.afterCompletion(TxManager.java:984)
     at weblogic.transaction.internal.ServerSCInfo.callAfterCompletions(ServerSCInfo.java:862)
     at weblogic.transaction.internal.ServerTransactionImpl.callAfterCompletions(ServerTransactionImpl.java:2913)
     at weblogic.transaction.internal.ServerTransactionImpl.afterCommittedStateHousekeeping(ServerTransactionImpl.java:2806)
     at weblogic.transaction.internal.ServerTransactionImpl.setCommitted(ServerTransactionImpl.java:2851)
     at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2650)
     at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2570)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:277)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:226)
     at weblogic.ejb.container.internal.BaseEJBHome.postHomeInvoke(BaseEJBHome.java:389)
     at weblogic.ejb.container.internal.EntityEJBHome.findByPrimaryKey(EntityEJBHome.java:408)
     at com.armanta.ejb.portfolio.PortfolioMetaData_a4zvzk_HomeImpl.findByPrimaryKey(PortfolioMetaData_a4zvzk_HomeImpl.java:64)
     at com.armanta.ejb.portfolio.PortfolioMasterBean.getPortfolioMetaData(PortfolioMasterBean.java:313)
     at com.armanta.ejb.portfolio.PortfolioMaster_fmk9e8_EOImpl.getPortfolioMetaData(PortfolioMaster_fmk9e8_EOImpl.java:64)
     at com.armanta.ejb.portfolio.PortfolioMaster_fmk9e8_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
     at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
     at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
     at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
I checked the equals and hashCode implementations and nothing pops out at me. Once this happens, the EJB seems to get messed up in the database and I lose information!
Here is the class implementation along with its superclass. I don't see anything blatant. Sorry for the lack of indentation, my original post was indented.
Thanks
Eric
public class ObjectPK extends ArmantaPK {
     private String type;
     private String name;
     private ObjectPK() {
          super();
     public ObjectPK(String type, String name) {
          super();
          this.type = type;
          this.name = name;
     public String getName() {
          return name;
     public String getType() {
          return type;
     public String toString() {
          StringBuffer buffer = new StringBuffer();
          buffer.append("[ObjectPK:");
          buffer.append(" type: ");
          buffer.append(type);
          buffer.append(" name: ");
          buffer.append(name);
          buffer.append("]");
          return buffer.toString();
     * Returns <code>true</code> if this <code>ObjectPK</code> is the same as the o argument.
     * @return <code>true</code> if this <code>ObjectPK</code> is the same as the o argument.
     public boolean equals(Object o) {
          if (this == o) {
               return true;
          if (!super.equals(o)) {
               return false;
          if (o == null) {
               return false;
          if (o.getClass() != getClass()) {
               return false;
          ObjectPK castedObj = (ObjectPK) o;
          return ((this.type == null ? castedObj.type == null : this.type
               .equals(castedObj.type)) && (this.name == null
               ? castedObj.name == null
               : this.name.equals(castedObj.name)));
     * Override hashCode.
     * @return the Objects hashcode.
     public int hashCode() {
          int hashCode = super.hashCode();
          hashCode = 31 * hashCode + (type == null ? 0 : type.hashCode());
          hashCode = 31 * hashCode + (name == null ? 0 : name.hashCode());
          return hashCode;
     public Object clone() {
          ObjectPK inst = new ObjectPK();
          inst.type = this.type == null ? null : new String(this.type);
          inst.name = this.name == null ? null : new String(this.name);
          return inst;
public abstract class ArmantaPK implements Serializable, Cloneable, Comparable {
     // Enforce compatability with future versions
     private static final long serialVersionUID = 1980721424128862564L;
     // Cache the hash code
     private transient int hash = 0;
     * Clones a primary key. Note that this is not a deep copy.
     * @return the cloned primary key
     public Object clone() throws CloneNotSupportedException {
          ArmantaPK newKey = (ArmantaPK) super.clone();
          newKey.hash = 0;
          return newKey;
     * Compare the specified object with this key for equality.
     * Implementations should return <tt>true</tt>
     * if and only if the specified object is also a key
     * of the same class and all corresponding attributes in the keys are
     * <i>equal</i>.
     * @param other the object to be compared for equality with this key.
     * @return <tt>true</tt> if the specified object is equal to this key.
     public boolean equals(Object other) {
          return other instanceof ArmantaPK;
     * This implementation only returns an empty String.
     * @return String
     public String toString() {
          return "";
     * Return the hash code value for this key. Implemented to call the
     * key's <code>computeHash</code> method and cache the result for
     * faster operation. Classes extending <code>ArmantaPK</code> should
     * only implement <code>computeHash</code>.
     * @return int
     public int hashCode() {
          if (hash == 0) {
               hash = computeHash();
          return hash;
     * @y.exclude
     * Compute a hash code for this key. This is the method that should
     * be overridden by sub-classes.
     * @return int
     protected int computeHash() {
          return 0;
     * @y.exclude
     * After called, will force the hash code to get recomputed.
     public void rehash() {
          hash = 0;
     * Compares this <tt>ArmantaPK</tt> to another object by comparing
     * their string representations.
     * @return an integer based upon comparing the <tt>ArmantaPK</tt>s string
     * representations
     public int compareTo(Object o) {
return toString().compareTo(o.toString());
}

We are experiencing a similar error after upgrading 9.2 to 9.2 MP3. We do not want to upgrade to 10g at this time. Is there a patch we can download with the fix?

Lock in lock manager could not be set - long text

Hi Experts,
We have a issue with the 124002 ID request for the ODS ZSDOD005 (request number REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX).
It has green status, but if you open the monitor, the status is red.
If you search for more detail, you can see the following message:
“Lock in lock manager could not be set -> long text”
The error refers to a lock in lock manager
Lock in lock manager could not be set -> long text
Message no. RSENQ009
Diagnosis
The lock in the lock manager could not be set.
An attempt is being made to set the lock in include LRSENQF00 in the form set_enqueue.
The lock table is table RSENQ_PROT_ENQ.
An attempt was made to lock the following object:
User/Object = BWREMOTE/ZSDOD005
Object_typ/Action = ODS/UPD_ODS
Subobject = REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX
SubSubObject = 000001
This problem affects subsequent loads.
The InfoPackage ZPAK_6K641H103XV0MTRBAV9Q788IS loads data to three ODS ZSDOD001, ZSDOD003 and ZSDOD005.
None of the other ODS generated InfoPackage for 09.25.2013.
Our BASIS support team couldn’t see locks that impact in the procedure.
The InfoPackage ZPAK_6K641H103XV0MTRBAV9Q788IS is part of the Process Chain ZCP01 - Ventas (SD) Transaccional
If we tried to repeat the step we had obtained the following message:
02.10.2013 16:44:04 Job started
02.10.2013 16:44:04 Step 001 started (program RSPROCESS, variant &0000000032648, user ID BWREMOTE)
02.10.2013 16:44:04 Start process LOADING ZPAK_6K641H103XV0MTRBAV9Q788IS in run 7PZGWSRZS6GJGB093B9W72U5H of chain ZCP01
02.10.2013 16:44:04 Delta request REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX is incorrect in the monitor
02.10.2013 16:44:04 A repeat needs to be requested
02.10.2013 16:44:04 Data target ZSDOD005 still includes delta request REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX
02.10.2013 16:44:04 If the repeat is now loaded, then after the load
02.10.2013 16:44:04 there could be duplicate data in the data targets
02.10.2013 16:44:04 Request the repeat?
02.10.2013 16:44:04 Last delta incorrect. A repeat must be requested. This is not possible.
02.10.2013 16:44:05 Performing check and potential update for status control table
02.10.2013 16:44:05 Could not set request REQU_6ROBVFEQ9SSOIJY5MDF2W9BTX in DTA ZSDOD005 to red; terminated with error 5
02.10.2013 16:44:05 Job finished
This issue prevents subsequent loads of data.
It is abnormal that there is a green external status and a red one internal.
Could you, please check why are we having this lock error?
What are the steps to follow to avoid losing information or having it duplicated in this case?
Thanks,
Kiran

Hi,
Make sure the DSO is not changed mode when u r trying perform your activity in production system.
if the DSO is in change mode..it will be locked for further activities to be happend on it unless again it comes back to active status.
if it locked..you can see all the locked Objects in SM12 Tcode and proceed accordingly.
hope this is clear for you.
Regards
Ramsunder.

Locking Problem while calling BAPI

Hi ,
I am calling a BAPI in my wd appln . if there is some problem while executing the bapi like posting period not open then i am displaying the error of the BAPI . but after that i see in the locked tables through SM12 some tables gets locked .
so when i call the BAPI again it gives me error like the following tables are locked by the user... so is there any way by which i can release the locks hold by the bapi if problems occurs.
Regards
Yash

Hi Yash,
Try the command ROLLBACK WORK if the error occurs.
This will remove all locks set by the BAPI.
Regards,
Jos

Can not refresh server manager Error:0x8007045b

OS: Windows 2012 R2 Core
Services: Hyper V
I was trying to remote reboot and the session hung. No worries I decided I could just reboot the next morning. So I rebooted the next day but when I go into server manager I get
an errror can not refresh server manager Error:0x8007045b. Did some research found suggestions to fix it using a DISM.exe /Online /Cleanup-image /Restorehealth.
But then I get an error 1115 A system Shutdown is in progress. I attempt to fix this issue using pskill winlogon but the issue pursistest. I have restarted the server several times now. Not sure how to fix this.
Thanks in advance,
Jake

Hi,
In addition to the above information,
Checkout the below thread for similar discussion,
http://social.technet.microsoft.com/forums/windowsserver/en-US/a700e9f6-4491-4c70-8bd0-d9d3111e2f70/windows-reboot-error
Regards,
Gopi
JiJi
Technologies

Lock management error in bapi /SAPMP/BAPI_ROUTING_PROCESS of ECC 6.0 system

Similar Messages

Maybe you are looking for