cancel
Showing results for 
Search instead for 
Did you mean: 

How to populate historical data into a newly added field in an infoprovider

Former Member
0 Kudos

Hi,

I have currently activated the purchasing datasources 2LIS_02_ITM etc. in the LO Cockpit.

Data has been loaded into the infoproviders and delta is activated.

We need to add in 3 new fields into one of the datasources and into one of the info providers.

For the 3 new fields, the previous and historical data will not have values if we just load in the delta data.

Is there anyway to update the previous and historical data with values for the 3 new fields without reloading all the data starting from day 1?

Thanks.

Shunhui.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi

Just to elaborate on the previous reply to your question.

You should make a generic datasource on the R/3 system that delivers document number and item (the key fields) and the 3 new fields. This datasource can be updated directly into the target on the BW side given that the target is an ODS and that it is overwriteable fields that we are talking about. If the target is a cube then you must write the data from the generic DS into an ODS and then make a "feedback" update rule on the cube which reads the extra fields from the ODS (given that you have the key fields in the cube). Tricky? Yes the first and second time you do it, then it becomes part of your toolbox.

Have a nice weekend

Kristian

Former Member
0 Kudos

Hi Kristian,

Thanks for the help.

I am not sure what you mean by "feedback" update rule.

Do you simply mean that I need to create an update rule for the infocube based on the ODS? Example: the ODS is call 0ABC_O01, infocube is 0ABB_C01, update rule to infocube 0ABB_C01 is called 80ABC_O01?

Thanks.

Shunhui.

Former Member
0 Kudos

Hi

If you have Purchasing ODS before Infocube then follow this quick procedure :-

(I had already implemented this for Delivery extractor 2LIS_12_VCITM)

Create the generic data source in R/3 side with these 3 fields plus key fields (Purchasing document , purchase order item etc) .

Replicate on BW side and then assign it to BW info source . Create the update rules to ODS.

Alternatively you can map the generic data source to Info source 2LIS_02_ITM .

Load the full data using Infopackage option - Repail FULL request and activate the ODS and update this request to Info cube.

Let me know if you are not clear on this procedure.

Hope this helps

Regards

Pradip

Message was edited by: Matthew Billingham

Former Member
0 Kudos

Hi Pradip,

I am clear with your suggestions. Thanks.

Below is what I was thinking of doing. Hope to hear your inputs.

Can I enhance the current extract structure of a datasource (for example 2LIS_02_ITM) with the new user created customized fields? I can only see the standard SAP fields being listed for appending to the extract structures but not the new user customized fields when clicking on the "Maintenance" link for structure.

And then add new customized infoobjects to the infosource 2LIS_02_ITM and map it to the new fields in the R/3 datasource? Is my way a good or recommended way?

Thanks.

Shunhui.

Former Member
0 Kudos

Hi Shunhui

Yes . you need to enhance the extract structure and write ABAP code in user exit to populate the data foe newly added 3 fields in datasource .

If the required fields (to be added) are not available in Maintenance link for structure then you need to go for enhancing the extract structure as explained above.

You have mentioned that delta is already active for datasource 2LIS_02_ITM . I believe you mean to say that delta is active in Production system . Then you need to be careful when you will transport enhanced extract structure+User exit for new code. You need to transport them in a single request and then replicate & activate the transfer rules .

If you think that you may face some problems while implementing this solution in Production system then let me know .

Hope this helps

Regards

Pradip

Former Member
0 Kudos

Hi Pradip,

If the required fields are not available in the Maintenance link, does it mean that I have to goto SE11 and create an append structure for the extract structure MC02M_0ITM which belongs to the datasource 2LIS_02_ITM?

Then I have to write codes in the user exit for transactional datasources in RSAP0001?

Are you able to provide some information on the errors that might arise during transports with the delta being active in the production system? Will data be corrupted? Will I need to clear the delta queue before the transport goes over?

Thanks for all the information.

You've been very helpful.

Shunhui.

(Just a thot: how do I award the points?)

Former Member
0 Kudos

Hi Shunhui

Answers :-

If the required fields are not available in the Maintenance link, does it mean that I have to goto SE11 and create an append structure for the extract structure MC02M_0ITM which belongs to the datasource 2LIS_02_ITM?

Then I have to write codes in the user exit for transactional datasources in RSAP0001?

Ans : That's correct . Once you have done this on R/3 side, replicate the data source in BW side. Activate the transfer rules with appropriate mapping for 3 new fields and also adjust the update rules so that these 3 new fields are availble in Info providers.

Are you able to provide some information on the errors that might arise during transports with the delta being active in the production system? Will data be corrupted? Will I need to clear the delta queue before the transport goes over?

Ans : I assume that deltas are active in Production system . There is risk to your active delta into BW .

Before your R/3 transports reach Production system , you need to clear the delta queue that means bring the number of LUWs for 2LIS_02_ITM to zero . Also stop the delta collector job in R/3 for Application 02(purchasing). Make sure that there are no postings (transactions /users are locked) so that there will be change in purchsing base tables.

Then send your R/3 transport into Production system (Append structure , new fields + user exit code) .Replicate on BW side. Now send the BW transports to BW production system .

I had done this earlier for 2LIS_12_VCITM and had a step by step proceduew written with me ....will have to search for that document . Let me know your email ID , will try to send it once I find the document

Regards

Pradip

(when you edit the questions , there are option buttons with which you can assign points for that you need to do log on to SDN )

Former Member
0 Kudos

Hi Pradip,

I now have a better understanding and clearer picture of what I'll need to do for such cases in the future.

I would still appreciate very much if you could send me your step by step procedure document.

My email is <removed>

Thanks for all the help.

Shunhui.

Message was edited by: Matthew Billingham

Former Member
0 Kudos

Hi Pradip/Shunhui,

Could you please forward this procedure to my e-mail id also.

Regards,

<removed>

Message was edited by: Matthew Billingham

Former Member
0 Kudos

Can I have the document you mentioned.you can mail me at <removed>

Message was edited by: Matthew Billingham

Former Member
0 Kudos

Hi ShyamKumar

Please refer to my weblog on enhance existing LO extractor (read comments on this weblog also)

/people/pradip.patil/blog/2006/06/07/how-to-retain-deltas-when-you-change-lo-extractor-in-production-system

Hope this helps.

Regards

Pradip

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

Hi,

refer the web log of Dinesh -

/people/dinesh.lalchand/blog/2006/02/07/loopback-process--follow-up

regards

Vikash