2LIS_03_BX / BF Update Mode

[Former Member]

I'm looking at using the LO Extractors 2LIS_03_BX / BF Inventory Controlling. All the other LO Cockpit extractors we have use the Update Method Queued Delta but the default for 2LIS_03_BX / BF seems to be Unsereialized V3 Update. Is there any reason why this is the default and is there any reason why I shouldnt change this to Queued Delta.

[former_member202718 · Accepted solution]

Hi Joel,

In Unserialised V3 Update, there is no Sequencing of Data..i.e the way the data is stored.Say,the Movement type may change for the same Doc and material.And as most of the times we load the data to the cube,the data gets summed up.However if we go for DSO then we may have to think on Queued Delta as sequencing will matter due to overwrite.

And to know the basic difference there are many threads related to this.

rgds

SVU123

[former_member182343]

Dear Joel,

It is not mandatory to keep Un-serialised V3 update to Inventory datasources (2LIS_03_BF/UM). You can go ahead with queued delta also.

Benefits with Un-serialised v3 update exclusively for stocks(inventory):

- Posting are not to be in serialised through un-serialised v3 update. You will not find any data mismatch, even a day before posting get extracted to BW a day afterwords.

Generally inventory closing stk gets calculates at Bex level, through 0RECORDTYPE and 0CALDAY validity date.

Here even movements(mat. docs) posting get delayed(un-serialised), it wont effort data accuracy.

Best wishes, Vijay

[RamanKorrapati]

Hi,

Addition to Svu reply:

its default selected for Un-serialized(records will be updated to rsa7 from base tables which are saved and no sequence). but we can change to queue delta. No issues.

I think you may be know the advantages of queued delta and why sap suggested.

thanks