Solution : https://service.sap.com/sap/support/notes/769414 (SAP Service marketplace login required)
Summary :
Since the introduction of Support Package 23 for BW 3.0 and subsequent releases, SAP has utilized the RSBATCH_WRITE_PROT_TO_APPLLOG report to manage Lock Manager log entries efficiently. This report is programmed to execute every 5 minutes, addressing a previous program error whereby direct log writes could prevent rollbacks for ungranted lock requests due to premature commits in the primary connection. This solution is applicable only in a live BW environment, necessitating that the scheduling be maintained continuously except during system downtimes (such as Support Package imports). Alterations to the job under different users are permissible following job deallocation and rescheduling through SM37, utilizing the specific job name "BI_WRITE_PROT_TO_APPLLOG." The job's interval setting is flexible, extendable up to one hour. Multiple active jobs in SM37 should be consolidated to maintain system integrity.
Key words :
active sm37 job running periodically, report rsbatch_write_prot_to_appllog/job bi_write_prot_to_appllog runs, write application log entries, sm37 job log, current job bi_write_prot_to_appllog, pure erp systems, 5-minute execution interval, terms lock manager, lock manager log, separate batch process
Related Notes :
| 763335 | SAPBWNews BW Support Package 09 NW'04 Stack 09 RIN |
| 752052 | P23:ENQUE:Commits when RSENQ_ENQUEUE locks are requested |
| 723260 | SAPBWNews BW 3.1 Content Support Package 18 |
| 723259 | SAPBWNews BW 3.1 Content Support Package 17 |
| 723193 | SAPBWNews BW 3.0B Support Package 24 |
| 723192 | SAPBWNews 3.0B Support Package 23 |
| 693495 | SAPBWNews BW Support Package 05 NW'04 Stack 05 RIN |