ABR delta extractor and entries written to the delta queue

[Former Member]

Hello Everyone,

We have an ABR extractor and it's behaving like this:

For example fields: PM Order Number, Post Goods Issue Date, Start Date, Work Qty, Projected Qty

Create the PM order the entry is written perfect to the delta queue:

10019987, blank, 04/29/2009, 100 PC, 90 PC

Now, if we perform a confirmation on the PM order we see the following:

10019987, 04/29/2009, blank, 0 PC, 90 PC

Now if we change something on the PM order header we see the following:

10019987, blank, blank, 100 PC, 0 PC

When this comes over to BW we don't get good results in our ODS.

Basically we don't get our Post Goods Issue date and Work Qty gets blanked out. Basically, the last change to the order gets written to the ODS and isn't correct.

Shouldn't it do the following:

10019987, blank, 100 PC, 90 PC

10019987, 04/29/2009, 100 PC, 90 PC

10019987, 04/29/2009, 100 PC, 90 PC

10019987, 04/29/2009, 04/29/2009, 100 PC, 90 PC------this gets sent as last record with all fields updated. We choose all these fields in the extract structure.

Thanks

[Former Member]

Hi.buddy:

The most important effect of the ABR mark is to decide which record will be extracted.

Can you show us all the record with ROCANCEL or RECORD_MODE?

Best Regards

Martin Xie

[Former Member]

Hello Martin,

Below is a snapshot of the delta queue (you can see the Cancel). Question: How do you control what record is updated and what others are not? We thought the cancel won't update and the others will in order they were updated to the delta queue (and that appears how it's behaving):

Scenerio #1 (sorry, can't remember sequence of steps done in system, but thought I'd mention)

Cancel, Order Number, Release Date, Posting Date, Material, Plan Qty, Confirmed Qty

blank, 10019987, 04/29/2009, blank, , 4415, 100, 0

blank, 10019987, 04/29/2009, 04/30/2009, 4415, 0, 100

blank, 10019987, 04/29/2009, blank, 4415, 100, 100

X, 10019987, 04/29/2009, blank, 4415, 100, 100

Scenerio #2

cancel, order, release date, posting date, material, plan qty, confirm qty

blank, 100019989, 04/29/2009, blank, 4415, 50, 0

then we perform a confirmation for 50 pieces and this is how the delta queue looks like

cancel, order, release date, posting date, material, plan qty, confirm qty

blank, 100019989, 04/29/2009, blank, 4415, 50, 0

blank, 100019989, 04/29/2009, 04/30/2009, 4415, 0, 50 <----

---

second line

Notice the second line now has plan qty at 0 and confirm at 50. Plan should always show 50 (or whatever the plan amount is. Something doesn't seem correct here??

Now, if we change something on the order header, we get the correct plan qty of 50 (and confirmed still 50), but then the posting date is blank. So when this comes over to BW we get correct plan and confirmed qty, but posting date is blank. This really makes no sense because if you have confirmed qty populated with a quantity then you have a posting date.

Thanks!

[Former Member]

Can someone let us know of this behavior?

Shouldn't every before have an after?

Shouldn't the after have the populated fields of the before and after?

Thanks

[Former Member]

CM,

Please provide datasource name.

ABR --> Complete Delta with Deletion Flag Via Delta Queue(Cube-Comp)

and what is the update mode...? Queued Delta or Unserialized or serialized V3 updates...??

[Former Member]

Hi Srinivas,

It's 2lis-17-ioitem and it's queued.

After order creation a run immediate LBWE job to push to delta.

Then perform confirmation and run LBWE job to push to delta queue.

Above is how it looks in RSA7 and how it comes over to BW.

Shouldn't every upate have fields populated from the previous delta change?

Meaning after a confirmation is done posting date is populated, after any change to the order shouldn't the next delta change have the changed fields and all previous populated fields populated from previous delta?

We are stuck????

Thanks!