How to check that Delta is not captured?

[Former Member]

Dear Experts,

I am using 2LIS_02_ITM datasource.

PO is created using a program.

The next step in the program, it can change a field in the PO depending on logic, using a abap command 'update'.

Sometimes, this change is not captured in the delta queue, it seems.

why i say this is the PO shows the field value but BI delta load does not.

It is using Queued Delta now.

Initially, the program uses a command 'update' to update the field in PO.

Now, we decided to use ME22N program to ensure delta will be created.

The problem is happening to some records and not all delta records.

Its very difficult to tell what is the cause.

What is the standard method to check that Application table data is not captured in Delta Queue by the extractor?

Or

If PO can show the field value, is there a possibility that Delta may not capture this field change?

regards

Pascal

[former_member186445 · Accepted solution]

it's always possible that a change is not captured by the delta...however there always needs to be reason.

first of all, you can check on OSS if it's a known bug. if you are lucky you get a note to implement. issue solved.

next, you need to know that not all changes will lead to records in delta queue. not all changes lead to change pointers set.

if you change custem added fields, this is often the case.

next, you need to know that not all po types are extracted. you can find on the net the info about this.

so, first thing, you need to find a pattern in the doc you are not getting in the delta queue

[Former Member · Accepted solution]

Dear Tibollo,

The field is a standard field in PO , vendor material.

regards

Pascal

[Former Member · Accepted solution]

Well just throwing few possibilities:

1 - Basically PO creation, change in values/quantities etc are Business transactions and they generate evens known as BTEs.

Now we have to explicitly inform SAP ECC that which applications can use BTEs and we do this by tcode BF11.

Check if the software component creating and changing POs is properly linked to BTEs and if BW is set as active in BF11 tcode.

2 - If point 1 is checked and nothing is found to be incorrect, please check if Industry sector is correctly chosen (SBIW). Industry sector generates a set of Transaction keys (BWVORG) without which the values are not updated in BW.

Also rightly pointed by Tbollo, you need to ensure that there's a pattern in the missing docs to identify the rootcause.

Debanshu