How to find out marker updated or not for any request ?

[Former Member]

Dear Experts

Some requests are loaded with Marker update. Some not.

The decision is relative to the BX init.

So, while all requests have been compressed in inventory cube, how to tell which request is compressed with and without markers given that both types can exist?

Thanks for reading.

Best regards

Pascal

[Former Member]

Dear Experts

Thank you for your responses.

While it is clear When to update the marker, what is missing information is How to See if a past request in the cube was compressed, with or was it done without marker update.

Thanks for reading.

Regards

Pascal

[anshu_lilhori]

Hi,

Check out this thread

https://scn.sap.com/thread/1462358

Regds.

AL

[former_member182343]

Dear Pascal,

Once compressed you cant get request information.

But you can able to see that data with selective filters while viewing data on 0IC_C03.

Filter data with 0RECORDTP -1 , those records are from BX load request , which compressed with marker update.

2LIS_03_BX with Marker Update (No Tick):

These are historical records having 0RECORDTP - 1 and 0CALDAY(Stock date) will be
31.12.9999.

- Vijay

[Former Member]

Dear Vijay

Just to confirm,

here is the understanding :

0. It is not possible to see was marker updated for a request existing in cube because compression removes the request ID.

Only at record level can we find out via 0recordtp value.

1. BX load contains historical records.

2. BF init also contains historical records.

3. Both of these records have 0calday = 31.12.9999 and 0recordtp for BX is -1 and 0recordtp for BF init is 0.

If I do a selective record deletion from the compressed inventory cube, say 1 material document number, and reload from the source R/3, this record is considered a historical record and as it is after the BX date, it is to be compressed with marker update once loaded?

Thank you for reading.

Best regards

Pascal

[anshu_lilhori]

Hi,

Just thought of throwing some light on your queries.

BX init doesn't contain the historical data.This just gives you the stock of the day when you initialized.

You can check the same ECC side once you fill the set up table..Run the RSA3 for that datasource and in posting date you will see the current system date and the same when loaded to BI side the date becomes 31.12.9999.

In order to get the historical data and movements data BF datasource comes into the picture which indeed gives you historical data as well as further movements data.

Inventory Management is a vast topic and it has lot of significance and importance as well from companys perspective.

I appreciate your continuous efforts to drill down more on functional and technical part of it by opening new thread with different subject lines which obviously shows your keen interest and research on the same.

I would suggest to draw the bottom line by reading all the threads and pdfs which i and other gyus gave you in your previous threads.

Also would request you to try the same on your sandbox system,practical knowledge helps to register the things easily and for longer period.

Regards,

AL

Message was edited by: Anshu Lilhori

[former_member182343]

HI,

1. BX load contains historical records:

Yes historical records before the day you made BF init and capturing closing stock.

2.BF init also contains historical records:

No , it doesn't contain historical records.

Init of BF captures closing stock of that material/plant on the day you made it init.

BF Deltas  captures all material movements with respect to movement types.

3.Both of these records have 0calday = 31.12.9999 and 0recordtp for BX is -1 and 0recordtp for BF init is 0.

Not both of the requests doesn't have 0calday = 31.12.9999.

Only BX will have 0calday = 31.12.9999.

BF init will get date on which you are capturing closing stk.

BF deltas will have date as-usually on which date movements are happening. 

I suggest you to do reversal posting , instead of selective deletion for mismatch Material doc.

If you want clarification on this ask me.

It is better to avoid selective deletion in Non cumulative cube.

- Vijay

[RamanKorrapati]

Hi Pascal,

Below docs maintained where we want to tick or not.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e...

Pls make note on this.. total inventory flow form r/3 to BI. it will be more useful..

Regards

[former_member182343]

Hi Pascal,

Before excplanation find the flow.

INITIAlIZATION

      2LIS_03_BX with Marker Update (No Tick)

      2LIS_03_BF with No Marker Update (Tick)

      2LIS_03_UM with No Marker Update (Tick)

FULL (Historic)

      2LIS_03_BF with No Marker Update (Tick)

      2LIS_03_UM with No Marker Update (Tick)

DELTA

      2LIS_03_BF with Marker Update (No Tick)

      2LIS_03_UM with Marker Update (No Tick)

  2LIS_03_BX with Marker Update (No Tick):

These are historical records having 0RECORDTP - 1 and 0CALDAY(Stock date) will be
31.12.9999.

This doc helps you:

http://sapedw.blogspot.in/2012/01/trouble-shooting-in-inventory.html#!/2012/01/trouble-shooting-in-i...

- Vijay

[former_member182343]

I will give you an idea about how stocks(material) deal at BW level and how  2LIS_03_BX datasource differentiates.

MM Enterprice structure:

Company code - Plant - Storage location - Batch - Material.

See MM03 for  material Master.

MB5B for validating stocks on specific date.

MC.9 for movements - Reports follow same hierarchy.

Lets I explain example with one material (Bolt).

Your EC went go live 2 yers back. Today your BI Stocks are going go live.

Check MB5B till yersterday closing stock of Bolt is 500 units.

You can simply load BF data-source with full load then you will get record with Closing stock 500. here 0RECORDTP is 0 and stock date will be 31.12.9999.

Here this Material(Bold) have may movements in 2 years since ECC system went go live.

Here user want to see those historical records also.

Then you have to go for BX data-source(called historical movements , i.e., movements before you done initialization of BF i.e, closing stock.

These BX records will have 0RECORDTP - 1.

0RECORDTP concept is only for Not-cumulative KF / Stocks.

- Vijay