System Lock Error while reset & reversing the cleared document - FBRA

Hi Experts,
Currently using t-code FBRA, when user trying to reset & reverse the cleared document , they are facing "System Lock Error". We have analyzed on this issue and found SAP note no. u201C487347 u2013FBRA: Overflow of the lock table in production systemu201D . After implementation of this note, SAP has created one new transaction code, FBRA_LOAC.
However, when we tried to reset & reverse the cleared document using t-code FBRA_LOAC, we face the same error.
Can you help me to resolve this issue ?
Thanks in advance.
Regards,
Manish

Hi:
      We once faced these issue and got it resolved by extending parameter after extending the profile-parameter "enque/table_size", as per note note 13907. Do not forget the restart the server after extension.
Regards

Similar Messages

  • Reversing the cleared document

    Hi experts,
    My client posted a wrong transaction in PRD system considering the Cheque Deposit Account instead of Cheque Payment Account while making a payment. After this the transaction became cleared item, now when he is trying to reverse the document system throwing up an error saying "Document is cleared, not possible to reverse".  Please could you suggest the way to reverse the cleared document.
    Nanda

    HI
    For reversal of cleared document we have to follow the below step
    1.Reset the cleared fi doucument in Transaction Code FBRA  
        Enter the Cleared document No ,Company code & Fiscal year then hit the clearing icon on the top press  the reset the cleared document then the document will be reset
    2. Check the status of the document in FBL1N  it should be uncleared
    3.Reverse the document in Transaction Code FB08
      Enter the UnCleared document No ,Company code & Fiscal year then reversal reason ,posting date & Posting period then hit the document icon on the top press  Post then the document  will be reversed
    Hope this will be usefull

  • How to  Reverse the clearing document & cancel the invoice

    Hi gurus,
    Can any body tell me how can i reverse the clearing document?
    what happen i had wrongly put up the customer invoice with the special GL indicator (Advance from customer) & i had clear the invoice & special gl balance.
    Steps which i follow:
    F-29 - Customer Down payment
    F-22 - Customer Invoice
    F-28 - Customer Incoming Payment
    F-39 - Clear customer down payment
    F-32 - Clear customer payments
    when i tried to reverse the document (T.Code FB08) which give me error that reverse the clear line item.
    Please help me to overcome this issue....
    Than'x,
    Dhananjay R.

    Hi amit,
    Than'x for given attention. actually i tried this T.code FBRA, what happen which reset the invoice & clearing document.& i see the customer / vendor invoice as open item in display. when i tried to reverse this entry which is wrongly inputed in the system which i want to reverse. while reversing this entry again i see the balance of clearing document in the customer / vendor balance display.
    i couldn't understand how to cancel this entry from the system?
    Pls suggest me to overcome this issue.
    Than'x
    Dhananjay R.

  • Reverse the Clearing Document Number

    ab01     1     50     1010810     UNVERFID DEP RECIPT 25,062.00-                              
    ab01     2     40     1012149     D A 10512634040103-S       686.00                              
    ab01     3     40     1012149     D A 10512634040103-S    2,500.00                         
    ab01     4     40     1012149     D A 10512634040103-S    2,556.00                         
    ab01     5     40     1012149     D A 10512634040103-S   16,000.00      1100016984     
    ab01     6     40     1012149     D A 10512634040103-S    2,700.00                              
    ab01     7     40     1012149     D A 10512634040103-S      620.00     
    Hi guys the  when i post the Document in the company Code Ab01 when i am try to Reverse the Document  i got the messageclearing Document number is there
    when i Try to reverse the Clearing Document Number in 2009  same number is avilable in the 2008 fiscal year. its not possible.we are not closed the fisacal year 2008
    please Solve this problem

    Dear Rao,
    It is not possible to reverse any clear documents with using of FB08. First we need to reset with FBRA and reverse the same transaction with FB08. or you can also do wih uing FBRA also to reverse the same.
    Best Rgds
    Mani

  • Call_fbra usage to reset multıple cleared documents(fbra)

    Hı experts
    I want to create z program to reset multıple cleared ıtems ,
    ıs there any snippet about his ı couldnt find any,
    ayn help will be appreciated..
    thanks

    Hi Kutay,
    Select all the valid documents(Company code, Document Number and Fiscal Year, and You may need to call the function modules with Company code, Document Number and Fiscal Year in a loop.
    for example
    u_mode = 'N'.
    Loop at IT_BELNR into WA_BELNR.
    u_bukrs = wa_belnr-bukrs.
    u_belnr = wa_belnr-belnr.
    u_gjahr = wa_belnr-gjahr.
    clear: wa_belnr, u_bukrs, u_belnr, u_gjahr.
    Endloop.
    Capture the error messages in a log and display it an ALV report.
    Hope this helps you out.
    Thanks,
    Rajesh Chowdary Velaga

  • Problems reversing a Clearing document

    Dear Frieds,
    User has cleared few documents with Transaction Code F-32 during monthend process and now he wants to reverse the clearing document.
    Trying to reverse through FBRA Tcode but it's giving error message as u201C Balance of the line items is not Zerou201D.
    Could you please help me with this to rectify this error.
    Thanks a lot for all your help.
    Regards,
    Hari.

    Hi Hari,
    Note 400530 - FBRA - F5136: Balance of line items not zero
    Summary
    Symptom
    A payment using a payment card fails, in other words, the payment is reversed using Transaction FBRC where the customer or vendor item is reopened.It is not possible to reset a payment document posted again for the open customer or vendor item by using Transaction FBRA, "Reset Cleared Items" and it responds with the error message "Balance of the line items is not zero".
    Other terms
    Error message F5136, FBRA, FBRC, payment cards
    Solution
    A solution is available in the Support Package for Release 4.0B and 4.6C. An advance correction is possible. The solution consists of a repair report, so that the current payment document can be reset by means of 'Reset Cleared Items', and of a correction.
    1. Repair-report ZREPAIR_BSEGC_FBRA:Create it temporarily as a test report using Transaction SE38. First the current payment/clearing document must be cleaned up of payment card data by means of the repair-report. Afterwards you can reset the payment document by means of 'Reset Cleared Items'. The report takes the current payment document as a parameter. In this case only changes are made to the database if the option "DO_UPD" is set.
    2. Advance correction:Supplement the interface for function module CREDIT_CARD_POST_REFUSAL with table parameter T_BSEG with reference type BSEG. The following describes the procedure in more detail.
    a) Transaction SE37: Enter function module CREDIT_CARD_POST_REFUSAL and choose "Change".
    b) On the "Tables" tab page, create parameter T_BSEG with reference to structure BSEG.
    c) Save and activate the function module.
    3. After you implemented the correction or the R/3 Support Packages valid for this note, read Note 450081 to avoid the unwanted deletion of payment card data.
    Regards
    udayakumar.k

  • SAP NAME FILE lock error while creating the TR in development system.

    Hi All,
    I am getting an error message while saving the changes in my SAP Script that 'SAP names file for <UserId> locked by another process'
    The name of the lock file is "/usr/sap/trans/tmp/<UserId>.LOS".
    Can any body help me, how to resolve this problem ?
    Thanks,

    Hi Kamlesh,
    did you find any solution? I'm getting the same error while a saving the changes in a Dynpro in the ABAP Development Workbench.
    Thanks,
    Viktor

  • Error while resetting a cleared document

    Hi everyone,
    I am getting an error while resetting a cleared invoicing document 'Document xxxxxxxxxxx with origin R4 can not be reversed'. Please guide me how can we reset the clearing of this document.
    Thanks and Regards

    Hi,
    You need to reset all clearing for the corresponding FICA document for the print document.
    Reset the clearing for the document no. mentioned in the output for EA13 execution.
    You need to reset all the clearing for the document, before reversing the same.
    To get all the clearing document, go to DFKKOP table, enter the FICA document no. (for the print document on FPL9). Get all AUGBL documents,
    Alternatively, you can go on to FPL9 screen, double click on the consumption document, in the basic data you will see the clearing date (if it is cleared), expand the view their (click on + sign), you will se the clearing document no,
    Pass the above clearing document no, to FP07, and once all the clearing is reset for the invoice, you can reverse the corresponding invoice through EA13.
    Regards,
    Rajesh Popat

  • Error while exporting/transporting the Business system from Dev to Quality

    Hi,
    We are getting the following error whil exporting/trsnporting the Business system from development(SLD) env to quality(SLD) environment. The error is
      404   Not Found
      The requested resource does not exist.
      Details:   Go to main page of this application!
    We have followed the following procedure to export :
    1. opened the business system.
    2. Clicked on export option
    3. tried to download
    then we got the above error message.
    Please provide your precious inputs to resove our problem.
    Thanks
    Ramesh

    Go through the following links for transporting XI objects.
    https://service.sap.com/~sapdownload/011000358700001684302005E/HowToSLDandXI.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0fa2c490-0201-0010-61b4-df12869c4753
    ere's a good link for what you are looking.
    Re: Transport design and configuration objects
    Here are some blogs.
    /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
    /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
    Pls reward if useful

  • FBRA: System lock error  inform system administrator

    While trying to reset a document transaction code FBRA, am getting the error message "System lock error  inform your system administrator" when I hit the save button.
    how do i solve this?
    You help is much obliged.
    ogutu

    Dear Ogutu,
    the F5288 error message (System lock error: inform system Administrator)                  
    appears to be caused by a table overflow as it takes place with a very                    
    large document ie. xxxx line items. As all the items must be locked when                  
    transaction FBRA is performed, there is not enough space in the lock                      
    table.                                                                               
    Please extend the profile-parameter "enque/table_size", as per note                       
    13907, 487347 which I have attached, in order to overcome this problem.                   
    You have to change a parameter.                                                                               
    Then please remember to restart the server after extend the                               
    profile-parameter "enque/table_size", as per note note 13907.                                                                               
    If you already did it and nothing changed, please increase the parameter                  
    again.                                                                               
    Please be aware that You have also to implement the solution described                    
    in note 487347. There is not only correction code, there is also some                     
    steps to do in order to solve the incident (manual changes have to be                     
    done in SE93):                                                                               
    1.  Implement the corrections. The corrections are not contained in the                  
         SAP Standard System. See Note 170183.                                                                               
    2.  Use Transaction SE93 to create the parameter transaction FBRA_LOAC                   
         referring to transaction FBRA. In addition to the descriptive text                   
         'Reset Cleared Items with Account Block', you have to enter the                      
         value FBRA in the 'Transaction' field.                                                                               
    3.  In problematic cases, use transaction FBRA_LOAC to reset cleared                     
         items. The transaction is not designed to replace the existing                       
         transaction FBRA. The transaction only provides the option to reset                  
         cleared items in case of an overflow of the lock table.         
    I hope this helps.
    Mauri

  • Unable to Log-in *SAP System Message : Error while reading a Dynpro*

    Hi,
    We are facing issues while logging-in through SAP logon 710.
    The system throws an error dialog box with the below message:
    SAP System Message : Error while reading a Dynpro
    At the OS level Java process  server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.

    Hi Please find the contents of std_server.out below.
    stdout/stderr redirect
    node name   : server0
    pid         : 4124
    system name : KEC
    system nr.  : 01
    started at  : Mon Jul 27 15:44:57 2009
    [Thr 5656] MtxInit: -2 0 0
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
    CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
    CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
    CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
    CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
    SAP J2EE Engine Version 7.00   PatchLevel 110760.44 is starting...
    Loading: LogManager ... 250 ms.
    Loading: PoolManager ... 0 ms.
    Loading: ApplicationThreadManager ... 47 ms.
    Loading: ThreadManager ... 16 ms.
    Loading: IpVerificationManager ... 0 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 93 ms.
    Loading: LockingManager ... 32 ms.
    Loading: ConfigurationManager ... 1032 ms.
    Loading: LicensingManager ... 0 ms.
    Loading: CacheManager ... 93 ms.
    Loading: ServiceManager ...
    Loading services.:
      Service runtimeinfo started. (16 ms).
      Service cross started. (31 ms).
      Service file started. (31 ms).
      Service memory started. (31 ms).
      Service timeout started. (16 ms).
      Service trex.service started. (32 ms).
      Service userstore started. (0 ms).
      Service jmx_notification started. (15 ms).
      Service p4 started. (62 ms).
      Service classpath_resolver started. (16 ms).
      Service deploy started. (3722 ms).
      Service MigrationService started. (31 ms).
      Service bimmrdeployer started. (0 ms).
      Service log_configurator started. (5177 ms).
      Service locking started. (0 ms).
      Service http started. (126 ms).
      Service naming started. (157 ms).
      Service failover started. (16 ms).
      Service appclient started. (31 ms).
      Service javamail started. (47 ms).
      Service ts started. (47 ms).
      Service jmsconnector started. (47 ms).
      Service licensing started. (15 ms).
      Service connector started. (93 ms).
      Service iiop started. (94 ms).
      Service configuration started. (16 ms).
      Service webservices started. (265 ms).
      Service dbpool started. (1204 ms).
      Service UT started. (0 ms).
    Jul 27, 2009 3:45:09 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "     Error while reading a dynpro                                        ". This message is critical if it appears during the startup of the AS Java.
    Jul 27, 2009 3:45:09 PM  ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] Fatal:
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro                                       
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro                                       
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
         ... 6 more
    com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro                                       
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro                                       
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
         at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
         ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Jul 27, 2009 3:45:09 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

  • Resetting and reversing a cleared document

    Hello
    I want to reset and reverse a customer clearing document. The clearing document which is 54203512 was posted and matched against the customer invoice in the previous period. When reversing and resetting the document in transaction code FBRA, a pop up screen u201CReversal Datau201D appears. The reversal reason is specified as 01 (Reversal for incorrect posting), posting date is todayu2019s date however the original clearing document 54203512 was posted in 05.09.2008 and in previous period. Click on continue.
    The document is not reset and reversed and I am getting the error message u201CReversal reason 01 only permits posting date 05.09.2008u201D. Not sure why the document is looking at the posting date of original document even though I specified the reversal date as 08.10.2008. Can a document be reset and reversed in different periods?? Or does this cause any issues or problems? Or is this a bug??
    Thanks in advance
    Evelyn

    Hi,
    There are only 2 controls allowed for Reversal reasons:
    1.  Negative posting
    2.  Alternative date for posting
    The symptom you have mentioned would be of a control from somewhere else, i.e. either a user exit or a validation.  An order reason can only restrict it to current date or allow any other date.  At least that is what I have experienced.
    Cheers...

  • F-04 Section code error while full Down Payment Clearing

    Hi,
    I am facing a situation wherein suppose I have given an advance of INR 10,000 to an employee as Travel advance but due to some reason his trip got cancelled and the employee is refunding me the full advance. I am trying to clear that down payment of INR 10,000 through transaction code F-04 but I am getting an error and the system is asking to input Section code to proceed further but the Section code field is greyed out; I can see only Business Place coming automatically but not Section code. In this case ofcourse no invoice will be raised on the employee.
    I am facing the same problem if try to clear through F-54 without any invoice reference. But when I try to do a partial/residual clearing the system allows me to enter Section code and proceed with the clearing. I have created a validation for making Section code mandatory and am using Sets (t-code GS01) in my validaiton but i have not inputted clearing transaction codes in there.
    What I am unable to understand is why I am getting this error only while doing full clearing and without invoice reference. If there is something wrong with the validation I should get the same error while doing partial/residual clearing.
    Please help me out on this one.
    Thanks

    Hi
    In validation , you have to give TCODs in which both the field required to make mandatory. Otherwise it is applicable for every transaction of vendor.
    Make necessary changes in prequisits in validation.
    Thannks
    GG

  • Only reseting the cleared documents with exchange rate differences in FBRA

    Hello,
    we want only reset the cleared documents . We dont want to reverse the cleard documents. But When we try to do it we get a message Exchage difference are posted do you want to reverse it. Want we want to reset are in Doc.. currency. postings for August.
    As i know when we have exchange rate difference we  dont get an option only resettng but we get reseting and reversing.
    May i know how to slove this situation.
    Thank you
    Chaithra

    HiI
    f you set this selection field then the settings in the ERD Setting column for this currency type are no longer relevant. The system calculates and posts exchange rate differences between order-related goods receipts and invoices not just for materials with standard price, but also for:
    Materials with moving average price
    Account-assigned transactions
    Planned delivery costs
    The valuation of the inventories or consumption is effectively done at the exchange rate for the goods receipt, and not at the exchange rate of the invoice. When you post the good receipts, the fixed exchange rate from the purchase order is not used, but the translation of the purchase order values to local currency is always done at the posting date of the goods receipt.
    If you are using the material ledger with actual costing, the system does not include the posted exchange rate differences at period-end closing in the actual prices of the materials.
    Regards
    Antony

  • System Lock error : Inform System administrator

    Dear all,
    One of the SAP user got this (System Lock error : Inform System administrator) error , while doing posting .
    Kindly advise

    Hi,
    Check for any lock entries in the TA SM12 and then have a look at the note 13907 System error in the block handler, overflow lock table.
    Hope this helps.
    _Varadhu...

Maybe you are looking for