BW – Delta Queue Update Method

Following my last blog post on Unclogging Queue Entries.

We know that we need to trigger delta update by creating V3 job to push the data into Delta Queue.
For note, these process are running on ECC-Side.
There are 3 different update method for this delta:
1. Direct Delta
• In this update method, data is directly transferred to Delta Queue and application tables at same time,
with every document posting
• Here, 1 document = 1 LUW (Logistic Unit of Work)
• Suitable for a small datasource type

2. Queue Delta
• In this update method, the records are first sent to ‘Extraction Queue’ using V1 update
Note: This ‘Extraction Queue’ entries recorded in serialize way. That’s why the queue delta are suitable for serialization document number.
• From ‘Extraction Queue’, we need to send the records to ‘Delta Queue’ using collection
• In this update method, we can collect up to 10,000 documents in one LUW

3. Unserialized V3 Update
• Here, the extracted data of an application is written to update tables using V3 update
• We need to send the data from Update Tables (SM13) to Delta Queue (RSA7) using Collection Run
• In this, serialization of documents is not guaranteed

Image above showing the difference of three update methods.
> Direct Delta VS Queue & V3 Unserialize
Data from transaction updated directly into Delta Queue using V1.
Meanwhile, Queue & V3 Unserialize have temporary table( Extraction & Update Table).
> Queue VS V3 Unserialize
Extraction suitable for serialization & V3 Unserialize are not.
Queue Delta check with LBWQ.
V3 Unserialize check with SM13.

source: http://scn.sap.com/docs/DOC-33012

BW – Collection Run for Entries Delta Update

So we found this problem regarding Delta Update on BW server.
After BW running on production phase for a couple days we saw the update are not running as they should. They’re some extraction that remain on yellow light. It seems like there are no data coming through anymore from ECC to BW side.

It turned out there are a lot of entries Queue-ing on ECC side. Using transaction SMQ1, we could see some entries are waiting in line to be extracted.

It’s like a ‘Clogged Pipes’.
So how do we overcome the clogged pipes? we need to take out the plug.
But, where is the plug in terms of data flow from ECC to BW?

What we don’t know is, there is a difference process to update Full/Initial Datasource and Delta Datasource. Full/Initial data extracted are store in Setup-Table.
If initialization is successfully extracted into BW PSA, delta generated on ECC. From then on, data collection stored in Delta Queue (RSA7) before extracted by Infopackage.

And now for the best part, Unclogging.
It turned out we need to do the V3 job, releasing the entries data delta into queue delta before delta info package is triggered from BW-side.
Go to LBWE.
By clicking the job control and scheduling the job. Data Entries that stuck on SMQ1 are flowing into Delta Queue RSA7.

After setting up the background job process( I think I need to create a blog post on how I do this) for every time delta infopackage requested, the ‘Clogged Pipes’ never seen anymore.

© 2018 Rijdz

Theme by Anders NorenUp ↑