Changes in 2LIS_03_UM, impact on delta?

[Former Member]

We are going to add a field from the pool for 2LIS_03_UM Datasource. Not taking any downtime coz there will be no frequent postings in this datasource.

Now I know that there are separate queues for both BF an UM in SMQ1, also separate entries for datasources in RSA7 and also set up tables but the V3 job is common for both datasources, the whole application component 03.

Here we are using Unserialized V3 update for Inventory. My doubt is if I clear the queues and transport the UM datasource and in the mean while some posting are done in BF datasource, will I loose those delta records?

[RamanKorrapati · Accepted solution]

Hi ,

No, if you follow below 2 points.

Just take care all delta records and  move to bw side.

Check this points.

1. Clear SMQ1/SM13 by using V3 jobs

2. Clear RSA7 by running delta info pack 2 times.

if possible lock ecc respective t codes. Do the changes and move to prod.

Then there won't  be any problem regarding delta.

Thanks

[Former Member · Accepted solution]

Just take care all delta records and  move to bw side.

Check this points.

1. Clear SMQ1/SM13 by using V3 jobs

2. Clear RSA7 by running delta info pack 2 times.//

Say suppose I cleared the Queue(03) at 5:30 and transported the UM Datasource at 5:35, few postings for BF datasource will happen and there will entries in MCEX03. In that case will it give any transport error?

Or will there be any loss of records.

[RamanKorrapati · Accepted solution]

Hi dilip,

Transport won't give errors. delta may corrupt and have chance to miss delta records.

That's we always need to lock ecc respective transactions or better to move changes at weekends where there is no business.

thanks

[former_member182470 · Accepted solution]

There are chances to miss some postings in that 5 mins. Don't take chance, Lock for short time and move the transport. Hence no issues will raise. Hope u got my point.

[Former Member]

while ur transporting it is better to lock user and also stop background jobs which generates records or else there is a possibility to loss records.

Refer this threads :

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0709b9f-acbc-2c10-7a95-ab0ee18b9...

http://scn.sap.com/thread/1272702

[KamalMehta]

Hi Dilip,

Your Extract structures are getting changed so you need to make sure all the queues (including LBWQ/SMQ1, RSA7) corresponding to old structure  are cleared otherwise your V3 jobs would failed as it wont understand which extract structure is related to the data source.

Once queues are cleared it means all LBWQ's corresponding to old extract structure are gone and therefore you can transport. Make sure users are locked and no postings are done during this time.

Now you can fill the setup table which would contain historical records for new fields as well. This needs to be followed by init with data transfer in BW.

Hope you got the idea.

Thanks

[MGrob]

Hi

You just need to make sure your lbwq and your rsa7 for BF is empty otherwise you can't rebuild the setup tables. But it will not interfere with your BF delta. Transporting a datasource also doesn not affect your MCEX03

hope it helps

Martin

[anshu_lilhori]

Hi,

Best is while transporting  i would suggest to take the quick downtime and lock out the user related to this application to avoid all the troubles.

As it is inventory thats why i am asking you take all these precautions.

For more information refer this

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2050db8b-9d90-2c10-2980-b13a4b093...

Hope you understand.

Regards,

AL