How do we permanently stop MASS_CRM_* and R3AD_* locks from being applied??

[Former Member]

Good afternoon Experts,

How do we permanently stop MASS_CRM_* and R3AD_* locks from being applied in CRM? We have several jobs that run weekly to download information from R/3 to CRM. The information only takes a few minutes to download into CRM, however the blocks are applied during the middle of the night, and cause backups within our system.

Queue name R3AD_SCE also becomes blocked as well during these downloads.

How do we stop these from being applied, without manually having to go into R/3 to remove during the middle of the night?

We currently are on CRM 4.0. The only notes that I found regarding this problem was for 3.0 - 3.5.

Thank you for your help!

Jami

Edited by: Jami Shircel on May 27, 2009 8:00 PM

[Former Member]

Hi

Run report RSTRFCQI0 in t code se38 and give R3AD* as input to release all the cues starting with R3AD. This is to release the lock in mass. This might not help you resolve this issue permanently but it will reduce your efforts to unlock the cues.

Hope this will help

Rgds

Mallikarjun

[Former Member]

Hello jami,

What jobs you are running? Are you putting the lock manually in the code of these jobs?

Initial load would automatically put lock on R3AD* for consistency purpose.

You can refer note:1097651 for more info on mass queue.

My question is when you manually delete the lock ,job would continue to run.In that case why you need to set the lock?Is it getting set automatically?

So in your system..setting the locks on these table would trigger a back up?Why is this?

Regards,

Shatnhala.

[Former Member]

Thank you very much for your reply.

We are running a job created to download all materials from R/3 into CRM, using SAP program SMOF_DOWNLOAD with variant of material. I believe the locks are coming on as this is a load. However, the job only takes about 15 seconds to run and take the information from R/3. CRM takes longer to process that information. However, the lock does not come off when the job is complete. We have to manually remove the lock the next time someone from the team logs into CRM. This causes problems as nothing from R/3 to CRM is passing through while the locks are on. As soon as the lock is removed, the systems begin communicating again. The job is not impacted as it takes less than 15 seconds to run.

How do we either stop the lock from coming on, or have it automatically come off when the job is complete?

I reviewed the note suggested, but it was for account life cycles. Perhaps the wrong number was written?