Deleting MCEX02 enteries in table trfcqout.....

[Former Member]

Hi,

During setup table filling and subsequent initialization of purchasing datasources in LO-Cockpit, we had almost 0.5 million records in trfcqout table for MCEX02 queue. We had innitialized the queue in silent period so we know the delta timestamp after which we would need records to up updated in BW Delta Queue.

The option of deleting the queue through LBWQ gives no parameters for deletion of records. Is it possible to delete the queue MCEX02 at database level? I was just curious because we can run the query with selection conditions, though I am worried about inconsistencies this activity may cause. Also, it is not recommended to delete records at database level but if we could do it our initialization activity would be successful. I would appreciate if someone could reply with a solution.

Thanks,

Regards,

GVB

Message was edited by: Govind Bajaj

[Former Member]

I am refering to LBWQ. I do not have any enteries in RSA7 as collection job is not scheduled yet.

Thank you

GVB

[Former Member]

Hi Govind,

Just as what I have said, If you are willing to start over again the INIT Procedure, destroy your INIT Request using the Info Package and schedule the collective job now. It will delete entries in LBWQ.

If you wanted to preserve the INIT, delete the Queue using LBWQ delete option. Ask BASIS if theres a way to schedule that in Back Ground.

--Jkyle

[Former Member]

Definitely you will get reward points but once I know how to do so!!!

One last question - is there any program which runs in the background to delete MCEX02 queue content? The source system for my BW project is pretty huge and loading is pretty high so it would take 20 hrs atleast.

Thank you,

GVB

[Former Member]

Hi,

Wow, that means I have to wait till you learn before I got at least 2 points... Not good..he he.

I know a technique to delete this. But it will break your current INIT request. Unless you are willing to start over again.

By this time, you should schedule the hourly collective job in LBWE. When you delete the INIT Request and that job (collective run) triggers and detects no INIT Request present in RSA7, it will delete all entries in LBWQ.

Which entries are you referring for Deletion? LBWQ or RSA7?

--Jkyle

[Former Member]

Thanks for your wonderful clarifications!

If I am not wrong, records for a particular period which has been laoded in full update method are not transfered to BW during delta extraction even if they are present in BW delta queue in RSA7?

Is there any program which can run in backround for MCEX02 record deletion? Because it would take atleast 20-24 hrs for me to clear the queue.

Thanks,

GVB

[Former Member]

Hi Govind,

Thats pretty hefty, 20 to 24 hours? How did you arrive on that conclusion?

Anyway, I think you failed to assign points. Its a way to say Thank You...We had a pretty long conversion hmmm?? And I bet I have helped you a lot...He heh...

I'd say you practice more with this things to prove them yourself. The learning will definitely stick to your brain if you experience this on your own...Do these things in DEV.

Regards,

--Jkyle

[Former Member]

Thanks!

I have not scheduled an infopackage with delta update mode.

This is what I am getting from your reply -

1. Delete the MCEX02 queue

2. Setup the table for Purchasing from 01.05.2005 to 06.05.2005

3. Load the data in fullload update method for this period

4. Reinitialise the delta with zero transfer of records

5. Setup the collection run in LBWE for purcahsing.

This will require that there are no records in MCEX02 and all posting is stopped during steps 4 and 5.

Please correct me if I am wrong...

Thank you

GVB

[Former Member]

Hi Govind,

Steps 1 to 3 are correct.

Step 4 is wrong. You dont need to Reinitialize the Delta w/o Data Transfer. You already have an INIT DELTA. You dont need

to REINIT again. You must not destroy the old INIT Request.

Step 5 must be done ahead of this all because it does not matter since it runs only in background. Remember to make it periodic and run on Hourly Basis.

No stopping of postings are required.

Follow my suggestions in my previous post. Thats the correct order. Just clarify each step from me...

--Jkyle

[Former Member]

Thanks!!!

I have already initialized the delta and data is there in my ODS. The next activity I was thinking of was to start collection job and then go ahead with delta extraction.

In case I delete the MCEX02 queue how will I get delta from 02.05.2005 onwards. If this in not happening my initialization is as good as failure. Please let me know.

Thank you once again!

GVB

[Former Member]

Hi Govind,

Now, you are already in that scenario I advice you to try this method of correction.

1.) Today is 06.05.2005. If you delete the Queue, you will loose 02.05.2005 onwards right? It does not matter anymore. Just delete it.

2.) Now, you can collect Deltas Daily.

3.) After you collected your first DELTA for this day, it is half baked since you loose half day transactions since you deleted the DELTA Queue.

4.) Tomorrow, 07.05.2005, setup your P.O. SETUP tables but limit it only to dates 01.05.2005 to 06.05.2005. You must do this tomorrow to ensure all the P.O. transactions for 06.05.2005 are posted already.

5.) Perform a Selective Deletion on your ODS. Limit the deletion with 01.05.2005 to 06.05.2005.

6.) Perform FULL Update and convert to Repair Request.

I think if followed carefully, your problem will be solved...

--Jkyle

[Former Member]

Thanks again for a quick reply!

Following are the sequences of activities we did for data extraction for LO Cockpit purchasing datasources -

1. Set up table was filled with records from last six months on 01.05.2005

2. Purchasing datasources were activated on 19.04.2005

3. No transactions were posted in source system from 01.05.2005 to 02.05.2005

4. Before setup table fill there were half million records already present in MCEX02 queue(I guess records started flowing after we activated the datasources)

5. We initialized the datasources on 02.05.2005

Since records would have been there in setup table as well as in MCEX02 for the period 20.04.2005 to

01.05.2005, these would be duplicated in BW when delta is loaded into it. This will make my keyfigures give wrong values.

Now if we could delete records in MCEX02 for the period 20.04.2005 to 01.05.2005 no duplicate records would go into BW and records from there onwards could be extracted using delta call.

Hope you are getting me.

Thank you,

GVB

[Former Member]

Hi Govind,

Now its clear. What update mode are you using? If you are using Queued Delta, when you activated <b>Purchasing Datasources</b> last 19.04.2005, the DELTA Collective Job must also be started and set to run every hour.

It clears the LBWQ Delta Queue every time it runs when there is no active INIT DELTA Request for P.O.. This may have prevented your Queue to bloat to 0.5 million records.

The correct practice is to DELETE the Queue first before INIT in case it contains data.

If we delete the entire Queue, your worry are the DELTAs from 02.05.2005 onwards, right? Worry about this later. This can be repaired. Just delete the Queue. Have you transfered the content of Setup tables to the ODS already?

--Jkyle

[Former Member]

Thanks for reply!

Actually during initialization of purchasing datasoucrces, there were around 0.5 million records in queue MCEX02. Now if I update this queue into BW delta queue and load data in delta mode in BW (ODS is data target) there will be duplicate records and so updation process will fail.

My query is whether we can delete records of MCEX02 based on date parameter? To my understanding, through transaction LBWQ you can delete all the records of the queue.

But I want to delete the records based on date, from this queue, so that overlapping records in setup table and queue are deleted. This can only be done if a query is written in the database to delete the records from certain date to certain date. Can this be done? If yes, what are the consequences?

Hope things are clear now.

Thank you,

GVB

[Former Member]

Hi Govind,

I am just curious as to why you need to delete this 0.5 million records in the Queue and as to why they will cause duplication in your ODS? On a day to day DELTA process, these DELTA Updates should be updated to BW am I right?

And why did it accumulate to 0.5 million? Is your Delta Queue Collector Job running every our?

--Jkyle

[Former Member]

Hi Govind,

I'd like to help you. But can you please explain more on what do you need to do? It does not sink in to me...

Thanks...

--Jkyle