Solution : https://service.sap.com/sap/support/notes/1280623 (SAP Service marketplace login required)
Summary :
The SAP Note addresses an issue where a GUID generated by the database is being erroneously deleted, triggering a database lock. This occurs due to redundant deletion operations within the framework, causing errors. The identified root cause is a flaw within method /OSP/IF_INTERCEPTOR~PROCESS_REPORT of the class /OSP/CL_ALV_REPORTS. Previous additional code meant to delete the GUID has been removed to correct this. Applicable from SAP release 700 and above, as well as release 640. Users are instructed to apply the provided correction instructions to rectify this programming error.
Key words :
method /osp/if_interceptor~process_report, class /osp/cl_alv_reports, database generated guid, database lock, guid deletion, additional deletion, error situation, terms duet, program error, aditional code
Related Notes :
| 1303555 | Duet 1.5 Reporting Management: ERP 2004 |
| 1303554 | Duet 1.5 Reporting Management: ERP6.0 (2005) |
| 1287752 | Duet 1.5 SP1 ERP2004: Reporting Management Composite Note |
| 1287751 | Duet 1.5 SP1 ERP2005: Reporting Management Composite Note |
| 1280059 | Alloy 1.0: Release Information Note |
| 1149693 | Duet 1.5 SP01: Release Information Note |