cancel
Showing results for 
Search instead for 
Did you mean: 

Help with Remodeling InfoCube and DSO

sap_cohort
Active Contributor
0 Kudos

Hi Team,

Here is my situation:

     I have a project to add a new Pricing Date field into a Staging DSO and a next level InfoCube.  The pricing date field is already configured in the billing extract, but has not been mapped to anything further upstream.  The user also needs history from the beginning of the year only.

My overall plan of attack is to:

1.  Write an ABAP on R3 to collect up the Document/Line/Pricing Date Information into a Table and port this over to BW somehow.

2.  Remodel the DSO to add the pricing field and populate new field with User Exit fetching the Pricing Date.

3.  Remodel the InfoCube to add the pricing field and populate new field with User Exit fecthing the Pricing Date.

4.  I am nervouse about remodeling a DSO with so many records.

DSO Issue: The documentation for Remodeling a DSO mentions having to delete entire change log.

       Question 1. What are the ramifications of deleting the entire change log since any deltas coming out of the DSO depend on this?

  

       Question 2. Should I only have to make sure any upstream deltas are collected before deleting the DSO Change Log?

InfoCube Issue: The documentation for Remodeling an InfoCube metions having to compress infocube first.

       Question 3. In InfoCube remodeling is it only required to compress if adding a Key Figure or is it required for any kind of change?
                     (The Documentation context for this is not very clear.  I am not adding a Key Figure, but a date field/characterstic)

                    http://help.sap.com/saphelp_nw73/helpdata/en/4a/40c3a397ea1d0fe10000000a42189c/frameset.htm

If you need to perform a key figure operation (Add, Replace or Delete) and the InfoCube contains compressed and uncompressed requests, you need to compress all of the requests before you can proceed. Remodeling cannot be performed on a partially compressed InfoCube

Backup Issue:  Older documentation for remodeling mentioned backing up the InfoProviders, but gave no context in how this should be approached.  The newer documentation does not mention backup probably due to the improved process using shadow tables etc

       Question 4. Should I have to backup by creating duplicate providers or have basis backup prior to the remodeling?

Thanks for any help with this challenge!

Accepted Solutions (1)

Accepted Solutions (1)

ranganath_korata
Contributor
0 Kudos

Hi Kenneth,

When you say that the Pricing date field is already configured in the billing extract, but it is not mapped upstream, do you mean that the field is available in the datasource in BW also, but it is not mapped to any data target? If so, why would you write ABAP on R3 to populate this field? Let me know if I misunderstood you.

Coming to the rest of your points.

1) Once all deltas from a DSO is updated to the upstream data targets and data is verified for accuracy, Change log has no value, so it can be deleted safely. Ramification of not updating DSO delta to the data targets upstream would be to delete the contents of the target objects, and doing a full load from the DSO with a subsequent DTP init.

2) Pretty much same as the point above. The source DSO should update its deltas to the upstream targets.

3) Since KF is mentioned specifically, I think it'd apply to KF only. I'd let others shed light on this though. It is always advisable to take a backup.

4) We would have to create duplicate providers.

Given that we would be creating duplicate providers as backing up is recommended, I prefer the conventional way of filling new IO's by transferring data to and fro to avoid complexities of remodeling. That's just me though.

Thanks,

Ranga

sap_cohort
Active Contributor
0 Kudos

Hi Ranga,

     Thanks for the reply back!  Yes I mean the pricing date field is available in the datasource in BW.  I need an abap to populate the history the users are requesting.  They want the pricing date for 1/1/2013 forward so I was considering the abap to populate this during the remodel.

I'm going to have to agree with you on backing up and to and fro.  On the return load I would access the pricing data from an ECC table containing the pricing date for billing items..

Thanks for your clear answers and suggestions.  Please feel free to pass on any more opinions you might have. 

Thanks!

ranganath_korata
Contributor
0 Kudos

Hi Kenneth,

As the pricing date field is available in the datasource in BW, may I know why you are considering coding to populate it ? Did you check if this field has data in PSA? and RSA3? Is it an enhanced field which was not coded when the datasource was appended ? If data is available in PSA, and you are planning on writing a routine to read this data for populating DSO/Cube during the to and fro data transfer, how much data do the data targets have ? Is it a lot to drop and reload from PSA if your PSA is retained and not deleted?

Thanks,

Ranga

sap_cohort
Active Contributor
0 Kudos

Hi Ranga,

     This is a standard field in the extractor.  The field is PRSDAY.  I am coding because we do not keep PSA from inception and user is only looking for this field to be populated beginning of year to current.  And I believe that time downtime needed to reload/initialize PSA would not be accepted by business.

So not I am thinking what you recommend. Duplicate providers and populate Pricing Date on reload.

Let me know if you see all of this now and thanks again for your help.

ranganath_korata
Contributor
0 Kudos

So how are you planning on populating this field using Duplicate providers when data for this field is not available in BW? Am I missing something here Kenneth?

sap_cohort
Active Contributor
0 Kudos

Thanks for keeping up with this thread!  Here is my thought.  I am extracting the pricing date from ECC into a table on BW.  This table will have Billing Doc/Item/Pricing Date.   when refilling the DSO and InfoCube I will have the transformation rule (abap) get the pricing date from this table.

Does this make sense?

ranganath_korata
Contributor
0 Kudos

When you say you'd extract to a table in BW, I hope you mean a DSO or an IO with attributes, basically a flat structure. Have you considered missing deltas when extracting data from base tables in a live ECC system ? I believe you are extracting data for the year 2013, i.e. current data which is changing in a live system.

Answers (0)