Locking user for LO Cookpit to transport changes with new field?

[Former Member]

We have loaded much LO Cookpit data to BW DSOs already. Now we added some new fields to this LO Cookpit application and we often hear that Before R/3 transports, we should Lock the users (transaction lock) and drain the delta queue into BW till we get 0 LUWs in RSA7 for that datasource in R/3 system.

Could some experts here tell us why it's necessary to lock user input and empty the extraction queue/delta queue in R3?

Really appreciate anyone's input!

[former_member181964 · Accepted solution]

Hi,

If you won't lock the users , the transactions will happen and then if you execute V3 the data will floe from SMQ1 to RSA7 and also once you changed the Structure you must activate all objects and then send to production.

Hi,

If your datasource is already in production, and you want to data only from today onwards for enhanced fields, i.e. historical data is not required for enhanced fields..

1. Fix ECC down time for 20 to 30 munities

2. Keep all objects on Qty system in ECC and BW.

3. Run Delta laods in BW for 2 to 3 times.So with this step you can clear SMQ1 and RSA7. Check the entries in RSA7, if it is ZERO then it is fine.

4. Move DS from ECC Qty to ECC PROD .

5. Replicate in BW.

6. Move all BW objects from BW Qty to BW Prod.

7. Delete Init load in InfoPackage level (Not in ODS/Cube).

8. Load Init without DataTransfer.

9. Then Run Delta.

10.Next day on wards deltas will come as usual.

If you need Historical data also.

1. Delete data in Cube.

2. Fix Down Time and load Init then Delta.

See the thread in SDN

Thanks

Surendra Reddy

[Former Member · Accepted solution]

hi Surendra,

Really appreciate your answer! We know that the system has to be shut down and users need to be locked and the extraction queue/Delta queue on R3 systems have to be empty and also know the steps you listed. But you did not get our points. Our question is whether it's necessary to lock user/system and empty the queues. If we don't lock users and don't empty the extraction queue/Delta queue and just let R3 transport to be moved to Production system, then what will happen?

Thanks and looking forward to hearing from you soon!

[Former Member · Accepted solution]

-If you don't flush the Queues and deletion of setup tables Transport will fail.

-If you plan setup tables properly I mean during weekend.. when the postings may not occur ... then you can create background job to run setuptables (to avoid locking users)

-If the volume of setup tables are more and more you have to inform the basis team for system downtime... they may take care of users for time being to avoid postings... during setup tables if any doc posting occurs that entry will not come from setup table neither from delta(because V3 job is stopped during setup table).

-if you don't need historical data for new fields .. avoid setup tables and it will be normal as you already knew!

Edited by: Srinivas on Jul 23, 2010 10:08 AM

[former_member181964 · Accepted solution]

Hi,

If you don't lock the users then they will post the transactions and the actual structure and previous structures are different so when you try to load the data it will go dump and error, so you must lock the users and do it.

See good blog

/people/jfrancisco.fernandes/blog/2010/05/21/customizing-cockpit-managing-delta-queues-when-structure-changes

Thanks

Reddy

[former_member202718]

Hi Kevin,

I agree with what Surendra Said.................

The transport will fail if you dont follow the procedure.............

Point 1-Why Lock the users ?

The users will have to be locked else they will keep creating the transactions and the queue in LBWQ will keep on filling up and as per our discussion we have keep LBWQ and RSA7 empty,so the very prpose wont be served.

Point 2 -Why Empty Extraction queue or Delta Queue ?

It is something like you have data in DSO and you want to change the DSO from Standard to Write Optimised or you want to change the Key fileds of the DSO...........so without deleting the data in DSO we cannot change these properties of DSO.

The structure will change and there will be mismatch and the Transport will fail.

Rgds

SVU123

[Former Member]

Only For Transports - Delete setup tables and flush all the queues.. that' enough .. you need not to lock the USERS!