Solution : https://service.sap.com/sap/support/notes/376750 (SAP Service marketplace login required)
Summary :
Deadlocks may occur in the LIS when multiple update groups are utilized, often due to improper sorting of PROG_TAB. To resolve these issues, specific source code adjustments referenced in SAP Notes need implementation. For versions 3.1I, 4.0, and 4.5A, preliminary corrections from notes 120003, 138987, 139018, 419149, and 419236 must be applied. Post these corrections, additional fixes from notes 401432 and 417562 are necessary. Modifications in the inbound interface of LIS require regeneration of specific function groups or updating source code per the indicated routines to ensure stability and correctness of data updates.
Key words :
'environment' --> 'lis interface' --> 'delete lis interface', 'environment' --> 'lis interface' --> 'create lis interface', lis inbound interface display, lis inbound interface change, lis inbound interface, symptom deadlocks occur, form routine update_from_int, main program saplznnn, sample report rmcmev0u, snnn information structure
Related Notes :
| 544787 | PP-IS: Deadlocks during mass processing in R/3 or from APO |
| 449086 | TIS: Deadlocks due to unsorted PROGTAB |
| 419236 | LIS inbound interface: Error M2789 during generation |
| 419149 | SIS: Dump in LMCS1F10/5F10/6F10 after impl of Note 376750 |
| 417562 | Addition to Note 401432 - LMCF4F10 |
| 401432 | Performance & update problems after implementing Note 376750 |
| 390918 | IS-M/AM: LIS deadlock in update / dump with order |
| 385372 | LIS: Collective note - DEADLOCKS |
| 204130 | SIS update: Collective note |
| 188368 | Deadlocks in the LIS |