Modify table vbuk

Hi all.
I need modify the field vbuk-cmgst in the program SAPMV45A.
To do it I wrote the code below:
vbuk-cmgst = iv_cmgst.
I hope it be committed in the standard commit of the program.
Is there a rule to modify standard fields in standard programs ?
thansk.

Hi Renato Alves,
Whenever you try modifying a tabel , to avoidd deadlocks, you can use the Enqueue and Dequeue functions.
Incase if u need more clarification , reply back
Reward If useful.
Regards,|
Chitra.

Similar Messages

  • Another user-modified table (VPM1)

    Dear Experts,
    I faced the above error when trying to add outgoing payment.
    Firstly, I saved the outgoing payment as a draft. Then, I open the outgoing payment draft through payment draft report.
    Before I add the outgoing payment draft into valid outgoing payment document, I have to confirm and update the check number in payment mean.
    Finally I save the outgoing payment. However, system doesn't allow to save this draft into valid document and display error "Another user-modified table (VPM1) (ODBC-2039) [Message 131-183]". Please help!

    Dear Teng,
    It seems to be a database corruption issue.
    We would like to suggest you to open a message for SAP Support.
    Regards,
    Rakesh Pati
    SAP Business One Forum Team.

  • Error: Another User Modified Table in Service Call in SAP B1 8.8 PL9

    Hi Experts,
    We are facing an issue in SAP B1 8.8 Patch 9 in Service Call.  When taking service calls continuosly, when we try to update every 3rd Service Call the following error is coming
    "Another user or another operation modified data; to continue, open the window again  'Service Calls' (OSCL) (ODBC -2039)  [Message 131-183]".
    Only 1 user is using the service call.. Several times we logged out and logged in, still the same error is coming,
    Kindly help to solve this.
    Regards
    Sundaram

    Hi
    You may check this thread. It might be a bug.
    Re: another user modify table error on Service call
    Thanks,
    Gordon

  • Programme SDV03V02 changes Overall status of credit check in table VBUK

    Dear All,
    I happened to go through the previous threads pertaining to this program on rescheduling  the sales orders. Adding to that too
    i have an important aspect which needs the suggestion of you legends. As in my support this jobs runs every day night and reschedules all the open / back orders and it is found to change one key field "CMGST" (overall credit status)  from parameter
    B-Credit check was executed, document not OK     to     A-  Credit check was executed, document OK.        in the table VBUK.
    Due to which the blocked sales orders for delivery against credit checks  were being released and hence getting the goods issue and billing done. Users are panic on this and it created a lot of mess. Can any one suggest how to get rid of this please so that the program should not change the delivery block while it runs the batch job.
    An earlier solution might be definitely of great help for me.
    Thanks & Regards
    Krishna.K

    Dear Krishna,
    The backorder rescheduling program SDV03V02 can change confirmed quantities. The system uses confirmed quantities to calculate the credit value of the sales order. This change of the credit value can lead to a credit block or in your case a credit check where the document is ok.
    To stop SDV03V02 triggering a new credit check you could implement your own 'no credit check' routine 901 in transaction OVA8. Notes 895630 and 502930 provides more information on this.
    I hope this information helps.
    Best regards,
    Ian Kehoe

  • Another user modified table rdr3

    Hi
    I got error "Another user modified table rdr3" when try to update additional expenses on sales order form.
    Case: Update Add. expences through my code based on condition and document updated well with add. expenses
    but after that if i update add. expenses through system functionality <b>means By pass my code</b> based on some condition, SBO throws this error.
    Help needed!???

    In what event are you performing your update?  I was getting the same message when I did my update in the in "item clicked" (for the update button) and this is evidently before the form does the update.  It saw the changes I made to the record and therefore aborted the update.
    I moved my update to item-pressed and that solved the problem.  But it's been a little more complicated than that for me.
    As far as I can tell, SBO updates the object on the form AFTER the BeforeAction event is triggered from item pressed.  But the way my debugging suggests it happens is that if there are no errors from that update, while item pressed does get it's AfterAction triggered, the form is no longer in update mode - it's in OK mode. So it seems that the update really needs to happen from OK mode but there's one more complication.
    At least for the item master form, button 1 can be in OK mode after doing an Update (which will work), but will also be in OK mode after a find (where the user types, for instance, an item number and presses enter, rather than the find button).  So what I am doing is setting a flag on item pressed/update mode/before action that let's me know that update is requested.  then in item pressed/find mode/after mode I test for update requested, then update the object and turn off my flag:
      Case Is = SAPbouiCOM.BoEventTypes.et_ITEM_PRESSED
        If pVal.ItemUID = "1" Then
           Select Case pVal.FormMode
                Case Is = SAPbouiCOM.BoFormMode.fm_UPDATE_MODE
                         If pVal.BeforeAction Then
                            g_UpdateModeStarted = True
                         End If
               Case Is = SAPbouiCOM.BoFormMode.fm_OK_MODE
                          If g_UpdateModeStarted Then
                               If pVal.Action_Success Then
                                  UpdateItem()
                                  g_UpdateModeStarted = False
                               End If
                          End If
    WARNING:  I am very new to SBO programming and haven't even taken the class yet.  This works for me but I imagine that others in this forum might say I'm going about it all wrong.  But since no one else has offered a solution to this yet, I thought I'd let you know how I got around the problem.
    Good Luck!

  • Another user modify table error on Service call

    Dear All,
    i am getting error while updating the service call.
    As this is SAP2007B PL 16 i have created a service call when i am updating this service call i am getting the error like-another user is modify table-service call .
    Kindly help me out.
    Regard,
    Divya Singh

    Dear Divya,
    In most cases, the error messages " Another user modified table XXX (XXXX) (ODBC -2039)." comes because after opening the form at your side, another user opened the same form and applied some changes. You can close the form, open it again, apply your changes and then update it to avoid this error message.
    But in some cases, even if you close all the clients and login again, the problem still exists. In that case, this error might be caused by Database Corruption which need DB fix.  If this is the case, Kindly log a message to SAP Support.
    Regards,
    Varun
    SAP Business One Forum Team

  • Error: Another user -modified table (ODBC -2039)

    I receive an error when trying to post data through to the SapbobsCom6.7 business object reading "Another user -modified table (ODBC -2039)"
    Could anyone please assist me regarding this!
    Thank you!
    Etienne

    Hi Etienne et al,
    I don't know if this helps you, as your last post in this topic was quite a while ago, but never the less I found one reason for the -2039 error which may be of help to other Business One developers in the future.
    I was getting the -2039 error every time I tried to update a record in one of my user defined forms, yet the error wouldn't happen with most of the other records in the table.
    Looking at the record I found that there was a column related to a Date field on the which had an incorrectly entered value from a previous data import.
    What should have been '2004-06-23 00:00:00.000' in the table was actually '1899-12-30 23:06:04.000' and would appear as 30/12/99 in the form field. Once I corrected the format of the data the addon form was happy to update the record.
    I hope this helps anyone else out there.
    Nick Jacka

  • [OACT], Another user-modified table 'G/L Accounts' (ODBC-2039)

    Dear All,
    When AP dept user attempting to add outgoing payment, the error message ""[OACT], Another user-modified table 'G/L Accounts' (ODBC-2039)" appears, what could the causes of the problem be ? I have restarted server many times but still unsolved yet.
    TIA
    Rgds,

    Steve,
    One reason why this happens ("Another User Modifed table") is if the SQL database has been updated while the document is open. When trying to add the document, the information in the document will be inconsistent with the values in the database itself.
    It can also be because someone tried to Run one of the Restore Balances Procedure.
    Please contact SAP Support by logging a message at http://service.sap.com
    Suda

  • Another user-modified table... Errors

    Dear Experts,
    Two of our clients are experiencing same error message but different Table name and scenario.
    First: Customer1 change the password of Manager account and it became successful. But when they change the password again, they encounter the u201CAnother user-modified table 'Users'(OUSR)...u201D error message.
    Second: Customer2 can't change the Item description in Item Master Data. When they try to update the description, the "Another user-modified table 'Items'(OITM)(ODBC-2039)[Message 131-183]"  error message appears.
    I've read some of the preferred solutions but the same issue occurs.
    Are these considered as bugs?
    Please help us.
    Thank you so much.
    Regards,
    Doriza Cortez

    Dear Doriza Cortez,
    All those errors are caused by table locks. Users have at least to exit from B1 for all their sessions. If the problem still persist, restart server is the last cure. Before that, you can try to kill certain hidden session from SQL Studio.
    Thanks,
    Gordon

  • Another user-modified table  '' (POR1) (ODBC -2039)  [Message 131-183]

    I have updated the purcahse order form.I have added a combo excisable.Also I have defined excisable and non-excisable warehouses.I have added a condition as,
    If I select Yes from the combo then the warehouse of the item should be excisable.And,if I select No then the item should be from non-excisable warehouse.
    When I change the warehouse as per the above condition it gives error as,
    Another user-modified table  '' (POR1) (ODBC -2039)  [Message 131-183]
    I am using SAP Business One 2007 B.
    PL:11
    The errors occurs when I click on update button.The error does not occur if I don't update purchase order.
                                                                                    Regards,
                                                                                    Dilip Kumbhar

    Dilip Kumbhar,
    You may check these threads first:
    Updating a PO
    In Purchase Order
    Thanks,
    Gordon

  • Another user-modified table 'Items' (ITEM) (ODBC - 2039) [Message 131-183]

    Hi All,
    Just had an issue reported by a customer. They tried to amend a UDF on an Item Master record and they can change data such as the Item description, remarks etc and update the item successfully... However, when they tried to amend the contents of the UDF's attached to the Item  the system issue the message:
    Another user-modified table 'Items' (ITEM) (ODBC - 2039) [Message 131-183]
    Any thoughts?
    Best regards
    Earl

    I figured it out
    We had a UDF name U_Discount that was set to only allow Y or N.
    In the database I had a space after the Y or N value for some of the records. I discovered it by running
    SELECT distinct [U_Discount], COUNT(*)  FROM [OITM]  group by  [U_Discount]
    No idea how the space got there, but I ran
      update OITM set U_Discount = 'N' where LEFT(U_Discount,1) = 'N'
      update OITM set U_Discount = 'Y' where LEFT(U_Discount,1) = 'Y'
    and it fixed it

  • Another User modified Table (ODBC -2039) - Sales order

    Via a button on sales order form I delete some of the order lines with oMatrix.DeleteRow(rowNr).
    It works fine but the DocTotal is not updated as it will be if I delete the row manually with the right-click Delete Row command.
    When saving the order via Update button it refuses with the error "Another User modified Table (ODBC -2039)".
    Do you have any ideas for workarounds for this?
    I've tried to set the price to 0 before deleting the row (the DocTotal will be updated) but the error is the same when saving.
    I don't manipulate the FormMode in the code.
    Regards
    Lars

    HI,
    SAP has answered with notes 720076.
    They suggest to use
    oMatrix.Columns.Item("1").Cells.Item(i).Click()
    SBO_Application.ActivateMenuItem("1293")
    instead of
    oMatrix.DeleteRow(i)
    It works for me.
    Best regards,
    Paolo.

  • Another user-modified table 'Activities' (OCLG) (ODBC-2039) [Message 131-18

    Hello,
    Iu2019m having problems re-assigning some activities. When i make a slight alteration to an existing activity I added my note and reassigned the activity to another user to raise collection but it is coming up with the red message when I click on update which reads as follows:
    'Another user-modified table 'Activities' (OCLG) (ODBC-2039) [Message 131-18]'
    Could you please assist.
    Regards,
    Juan

    Gordon,
    I have tried disconnecting the AddOns to no avail. There are a few stored procedures but none that I can see attribute to the actitivity screen.
    I have tried this on a test company and there is no issue. I have ensured no one else is logged into SAP but the same message appears. Having investigated further it is now only happening for one activity in particular. Other 'Open' activities are fine. Newly created Activities can also be edited.
    Any other ideas?
    Regards,
    Juan

  • Another user-modified table  'Items' (ODBC -2039)

    I have a problem with the Items object. I have a folder on the Item MasterData  form and a extra table that stores the info from that tab.
    When I try to update an item i get this error message :
    Another user-modified table  'Items' (OITM or OITW) (ODBC -2039)
    I can update items normally if my addon is stopped. I have read something about a similar message about PO, but I get the error on all items( even newly added ones) so I don't think it's about them being involved in PO.
    Any ideas on this matter ?

    Hi,
    I faced a similar error once, i also modified the Item Master screen and added a tab with an extra table, then i was modifing the FORM MODE explicitly.
    If ur are modifing the FORM MODE explicitly we may get this error.
    Vasu Natari.

  • Another user-modified table ODBC -2039 [Message 131-183]

    Hi!
    I created a matrix that it is linked to a ChooseFromList, that has multiselection = true.
    The thing is that if i'm trying to update the record selecting multiple values, this error is displayed "Another user-modified table ODBC -2039 [Message 131-183]".
    If i try doing it with just one record, the UDO works perfectly.
    Also, it works fine if i'm creating for the first time the record and adding the multiple selection lines.
    Greetings!
    Reynaldo!

    HI,
    I think you have some transactions in the background.
    Close all stuffs, delete SM_OBS_DLL directory from your TEMP directory, and start the work again.
    Regards,
    J.

Maybe you are looking for