Create a Generic Datasource based on monthly snapshot ?

[former_member182467]

Hi ,

We need data from one ecc table which will extract the stock data from ecc to bw. Its a monthly snapshot to get the plant and material data. Can anyone advise on the steps and the process for the same. I know there are many links and forums for generic datasource creation. But what logic to use and which generic datasource extraction to use is my question. Please advise how to do my inital requirement gathering.

Thank You

DR

[former_member186445]

is it really necessary to create a new datasource for this? Such data usually is already in BI. Create a cube that is loaded once a month from whatever target the data is in.

should do the trick.

BR,

M.

[former_member182467]

Tibollo,

Thanks for the reply. Yes we have a different requirement to get stock based on movement type from LQUA table in ECC. We cannot use the existing stock tables. Please advise based on my above screenshot.

Thanks

DR

[Former Member]

Hi Daniel,

If i understand this correctly, you would want to take end of month snapshots of stock quantities. For this, the steps that I think would work are

1. Build a generic datasource on the table with the fields required

2. Load the data into first level DSO on BW. This would have a timestamp of the load date. The dataload would have to be a full load.

3. In case you want to do comparison analysis of stock quantities, you could compare it based on the timestamps.

You can also consider non cumulative key figures as in the case of inventory datasources and build your dataflow in that regards

Snehith

[former_member182467]

Hi Raju,

2. Load the data into first level DSO on BW. This would have a timestamp of the load date. The dataload would have to be a full load.

I think full load in this scenario will not work as we need to keep track of the stock quantities regularly and we need a delta update, as it will be loaded into the infocube from DSO for reporting. If we have a full load we need to delete and reload the complete data,....which I think its not feasible.

How would you get a timestamp for the load ? I mean which field do we need to consider for the timestamp in the table. There is no timestamp field as such, we have the one's given below.

3. In case you want to do comparison analysis of stock quantities, you could compare it based on the timestamps.

Timestamp of what ? Which fields need to be considered for the timestamp ? I believe we can get the data to the write optimized dso as the 1st layer. But my question is how will it get the delta based on which field in the table ? Can you advise from the above screenshot ?

Thanks

[Former Member]

Hi Daniel,

I am not well versed with the Business process flow, but wouldn't the date to be determined for the delta be purely based on the requirement? I see that there are 5 date fields in this table

1. Last movement

2. Last Stock Placement

3. Last Stock Removal

4. Last Addition to stock

5. GR date

6. Last Inventory

You can consider any of these dates for your delta capability, or you can use a custom system date for delta, so that the pointer points to the time of extraction of the data.

Regards

Snehith

[former_member182467]

Raju

Your point makes sense. Thanks for the reply. Can you please explain how to use custom system date for delta ? Do we need to use a FM based generic extractor for the same ?

I will find out from business what date from these 6 date's should be used to consider the delta. Please advise, these are my points.

My approach will be

1) use the existing table to build the generic extractor.

2) need to create a Write optimzied DSO with the same key in the table.

3) Load it to the DSO to the 2nd level, use KF as summation.

4) create a cube with the KF summation property as these are Inventory KF.

5) Schedule a process chain to load the data.

Open questions:

1) what will be the delta and how to build the generic extractor .. I mean how to handle delta ?

2) what will be the delta for a month and will the DSO/extractor be able to handle the monthly snapshot data at once ?

Thank You

DR

[former_member182467]

Raju,

We need the summation of material per plant. But we have a different key in the LQUA table which is WH number and Quant. Is it mandatory to have the same key as in the table or we can get the summation even with the material & Plant as the semantic key in the write optimized dso ? Please advise how to get the summation from this table using generic datasource through table with the below key.

NOTE :we will have a standard dso on the write optimzied dso and cube /MP as the reporting layer.

Thanks

[former_member182467]

Raju, Did you get a chance to look into the below issue. Please advise if you need more details.

Thanks

[Loed]

Hi,

You will create your generic datasource in TCODE RSO2 in ECC side..Type your table then activate..

Afterwards, replicate your datasource in BW side..Then you may already extract data from ECC..For the monthly thing,  you may have an INFOPACKAGE routine so that your infopackage will extract LAST MONTH based on current month..

Regards,

Loed

[former_member182467]

Hi Loed,

We have a LQUA table in ECC, where Ware house number and Quant are the key in it. My question is do we need to use the same key as in the table to the view of the generic datasource as well ? Only then it will be able to extract the delta, right ? Please advise how to get a monthly snapshot delta in this case. Do we need to consider a timestamp delta for the generic datasource based on view ? or we need to go for a generice datasource using a FM. Main idea is to get the stock from this table in ECC.

[Loed]

Hi,

What do you mean by "monthly snapshot"?

If you will only be using one (1) table, no need to create a view..Just directly use the table in your generic datasource..Hence, same key field will be used since you only have one (1) table..

Do you have a date or time field in your table?

Regards,

Loed

[former_member182467]

Thanks Loed,

Monthly snapshot in the sense - we need to extract the inventory stock data monthly once from this table to BI. That is a good point which you said, no need to create a view if we have 1 table as source.

We have a last movement date and time but not the actual timestamp field in the table. Can we consider this. Bascially this table will have the stock added to a particular quant in the warehouse. So this Last movement date and time field's will tell you when was the stock added and there is another field which is Last placement date and time. I am not sure which one we can consider, and can we consider these fields first of all as there are not the actual date and time in the table where the record is getting added.

Now my questions are, can we just consider any date and time available in the table as a source for the timestamp field for the delta ?

2nd - Will this table work for the monthly delta option to bring all the inventory stock option ...monthly once.

Please advise. Given below is the structure of the table.

Thanks

DR

[KodandaPani_KV]

Hi,

create the generic data source  -> using table/view/FM.

come to BW side create the data soruce based on the generic data source.

create the cube/dso and design the process chain.

for process chain schedule schedule montly once.

when ever run the process chain you will get the data every month 1 day.

Thanks,

Phani.

[former_member182467]

Phani/Loed,

But how about getting a delta for a snapshot. for example if I choose timestamp as the delta option and set the safety interval for 1 hour and will I be able to get the snapshot of the monthly load in generic datasource using view option. Will it be a monthly load delta snapshot. or I should go for a full load snapshot monthly.

Thank You

[Loed]

Hi,

If you just need to get the data last month based on your current date, then just do it in INFOPACKAGE level..Just do a FULL EXTRACTION of whole previous month in INFOPACKAGE..Just do a routine if you need to include this infopackage in process chain..

Regards,

Loed