cancel
Showing results for 
Search instead for 
Did you mean: 

Direct delta how to stop update to RSA7 delta queue when having plugin upgr

Former Member
0 Kudos

Hi,

I see that we don't really schedule a job for update mode direct delta.

Suppose we have a downtime in R/3 for new plugin or some other changes.How can we stop the LUWs coming to the DeltaQueue ?

(Since in normal Queued delta we can simply clear the LBWQ by running the V3 job and then remove it from schedule and clear the delta queue by running infopacakages.)

thanks,

rakesh

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member223744
Active Participant
0 Kudos

Hi.

Before the upgrade (import of a queue), all extraction queues and open update orders in all clients must be processed. The content of the setup tables must be deleted. To avoid this problem during the upgrade or to correct it, carry out the following steps:

1. Call transaction SMQ1 and check whether all queues in all clients (client = '', queue name 'MCEX') have been processed. To process the queues, start the collective run report for each application in the

displayed clients. If you no longer need the data in the BW system, deactivate the relevant extraction queues and DataSource in the LO cockpit (transaction LBWE) and delete the queue entries in ransaction SMQ1.

2. If you use the V3 update that is not serialized (usually only for application 03): Start collective run report RMBWV303. Then check the update orders in transaction SM13. If there are incorrect update orders in transaction SM13, correct the orders and then start the collective run report again. If you no longer require the update orders, you can delete them. There may be inconsistencies between tables VBMOD and VBHDR. For further information about this, see Notes 652310 and 67014.

3. Before the upgrade, delete the contents of the setup tables. Execute report RMCEX_SETUP_ENTRIES to find out which setup tables still contain entries. You can use transaction LBWG to delete the contents of the setup tables for all clients.

Unfortunately the check that the system carries out during the upgrade or when you import a Support Package does not display all affected applications. Therefore, Note 1083709 provides a check report that you can use to determine all affected applications and tables or queues.

More detailed information please check these following notes:

1083709-Error when you import Support Packages

1081287-Data extraction orders block the upgrade process

I hope I could be helpful.

Thanks,

Walter Oliveira.

Former Member
0 Kudos

Hi Rakesh,

In R/3 downtime, no body going to post any document or any changes in document, so if i am not wrong then no LUWs come to the delta queue in R/3 Down time. It is my opinion.

Regards,

Former Member
0 Kudos

So in the nutshell you are saying ...we don't have a way to control the direct delta like we have with queued delta????

Former Member
0 Kudos

Hi Rakesh,

In R/3 downtime, no body going to post any document or any changes in document, so if i am not wrong then no LUWs come to the delta queue in R/3 Down time.

Regards,

Former Member
0 Kudos

Hi ...

What I understand is probably the V3 jobs in the job control will be used to flush the delta of LBWQ in RSA7 and the structure will be made inactive?? right

Then clear the delta queue by infopackage.....please advise

Surprisingly i didn't find this topic till date in any threads, and also not mentioned in Roberto Negro's blogs.