Follow

Could not commit transaction -1116 on SAP 8.81 and 8.82 systems

Issue description

Error message: Data in Table COR_COR_MODULES not added: Could not commit transcation - 1116 occurs when trying to start the coresuite addon on 8.81 and 8.82 systems

 

Troubleshooting steps/tips

Check if field AchiveDate exists in any of the coresuite UDTs

 

Solution

The issue is caused by a new field (ArchiveDate) that SAP automatically added to "any" table (even "user defined tables") . This field is meant to be used for the build-in archiving functionality of SAP Business One.

According to Note 1630980 this field has already been removed again from some tables where it caused problems. For the 8.81 Version, the field is removed with PL09, but for 8.82 the field still exists. coresystems has already created a message with SAP to find out when the issue would also be resolved for 8.82. This issue will be resolved for the 8.82 Version with 8.82 PL3 (Status Update SAP 20/12/11).

To solve the issue in versions where SAP has not yet removed the field automatically, please proceed as below:

  1. backup database
  2. check which modules are currently set to active etc via:
    SELECT
      T0.U_ModuleGuid,
      T2.U_IsActive                                 AS 'Globale module configuration',
      T4.U_IsActive                                 AS 'User module configuration',
      t1.USER_CODE                                  AS 'User Code',
      t1.U_NAME                                     AS 'UserName',
      T2.U_LicCount                                 AS 'Total Available Licences',
      (SELECT
         COUNT(T3.U_ModuleGuid)
       FROM
         [dbo].[@COR_COR_LICENCE] T3
       WHERE  T3.U_IsLUsed = 'Y'
              AND T3.U_ModuleGuid = T0.U_ModuleGuid)AS 'Licences already assigned'
    FROM
      [dbo].[@COR_COR_LICENCE] T0
      LEFT JOIN OUSR t1
        ON T0.U_UserId = t1.INTERNAL_K
      LEFT JOIN [dbo].[@COR_COR_MODULES] T2
        ON T0.U_ModuleGuid = T2.U_ModuleGuid
      LEFT JOIN [dbo].[@COR_COR_MODULESUSER] T4
        ON T0.U_UserId = T4.U_UserId
           AND T0.U_ModuleGuid = T4.U_ModuleGuid
    WHERE  T0.U_IsLUsed = 'Y'
    ORDER  BY
      T0.U_ModuleGuid
  3. (In SBO:) Tools->customisation tools->User-Defined Tables-Setup
  4. remove the following table: COR_COR_MODULES and SWA_SWA_CONF via right-click (possibly other tables need to be removed also)
  5. restart SBO as (windows) admin with a SAP Business One Superuser

Remarks

CM106273_2011 open with SAP -> This issue will be resolved for the 8.82 Version with 8.82 PL3 (Status Update SAP 20/12/11).

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.