Interdependencies BI Delta Queue, activated change pointers and ROOSGEN

[former_member217320]

Hello all,

our basis administrator confronted me with a list of BDCPV entries for RSxxxx message types in the productive system that are aging, but haven't been processed. After analysing his list, it turned out that a few of the message types are for datasources which were initially requested per delta init, but in the meantime were adjusted to load per full.

We ran transaction BD22 to delete the items which were aged but never processed for specific datasources.

But why were the records created in the first place?

I examined the system reaction when requesting data per delta init and it seems to be that:

a) an message type entry is made in BD50 - activation of change pointers

b) the roosgen entry for the datasource is updated with the message type from BD50

c) the datasource is listed in the BI delta queue - RSA7

However, if I delete the delta init in the BI system (by deleting the entry in the scheduler of the infopackage - initialization options for source system), only the entry in RSA7 is deleted. The change pointer isn't deactivated and the system continues to create change pointer records. Am I doing something wrong? Is using transaction BD22 the only way to manage this?

It seems crazy to keep creating change pointer records for a datasource, that no longer runs in delta.

Any input or solutions are most welcome! We run BI 7.0 with ECC 6.0

Regards, Amber Morphis

[Former Member]

Hi,

See whenever a Master data source is activated and running for delta, it creates the change pointers in BDCPV table.

eg: for mat plant delta the message type is RS0026, after successful running of daily delta we can delete the processed change pointers periodically with a defined varinat as delte before 30days pointers.

There is a report to do this, we can run it daily with a defined variant for different message types..name of the report:

RBDCPCLR

You can chk the message types in ROOSGEN table with data source name.

As you are running full loads daily, I guess we can delete even obsolete pointers as well as processed chane pointers depends on your requirement... but be sure that this data is loaded to the targets thru daily full loads...

--

rgds,

Edited by: Krishna Rao on Mar 3, 2010 7:43 PM