Identify ODS change log request from Cube update rules init routine

Hello all.
I need to use a logic in the Start routine of a cube, whcih change log request are move from an ODS when doing a delta.
Anyone knows if this is possible???
Thnaks and best regards,
Alofnso.

Hello Oscar.
Basically my requirement is to do a selective deletion of the cube, before I load the new data, but the selective deletion has to be done according to some fields of the data that is going to be load to the cube.
That´s why I need this.
Best Regards,
Alfonso.

Similar Messages

Activation of ODS fails: Change-Log Request ODSR_... does not exist in ODS

Hello Experts,
I have a problem loading in an ODS object in Release BW 3.5. This load is in parallel to loading in a Cube and InfoObjects from 10 different SAP sources monthly.
Everytime, I load data, Activation fails. The Error message is "Change-Log Request ODSR_... does not exist in ODS ..." These Requests (30 requests) are very old starting with the Go-Live date of the application in 2005. If I search for the first Request in Reconstruct, a request without a InfoPackage-Name is found and if I reconstruct the request, all other new loaded Request are activated and everything is fine. The next month, the same error appears, but without the one old request in the list reconstructed the month before of course.
A few months before I had to repair loading and deleted also requests in the ODS. Then I realized my mistake, that reconstruction is not possible, because the request was gone in the reconstruction list. So I searched for the PSA Request in the ODS reconstruction list, found the requests and reconstructed these. Could this be the reason for my current problem?
But how can I stop this error? Reconstructing all of the requests did not work, because one request says, no active update rules exist for this request. So I stopped reconstructing every request of the long list.
Please help me, I could not find any helpful information until now ...
Many thanks in advance,
Hannes

Hi,
For the old requests that you don't want and that are not valid, goto the monitor for those and mark them red. After that you won't face any problems while activating the new requests.
The reason this is happening is that during activation BW thinks that these old requests are valid as they are green and tries to activate them as they are in squence. When it dosen't find them then it gives the error. If you mark them red, they are ignored and the next request is taken into consideration.
Cheers,
Kedar

Duplicate records in ODS change log

Hi Experts,
I have loaded records from R/3 to ODS (psa and then data target).
Records looks good in ODS active data.
Then I did a delta load from ODS to InfoCube and I have recevied are the changed entries to Cube.
Then, I checked the ODS and the Datamart status was Checked.
But, when I did a delta load again after couple of days from ODS to InfoCube, I received some duplicate records. I have checked the Change Log of ODS and the duplicate records were there.
I am not sure why my ODS is transporting entries from the ODS request for which there was a datamart status already checked.
( I cannot do selective deletion because there are about 1000 duplicate entries and in random order..).
I beleive my best bet would be to:
1. Delete both the delta load requests (the request with correct records and the request with duplicate records) from InfoCube.
2. Remove datamart status from ODS
3. Delta load from ODS to InfoCube
Please let me know if this will solve the issue or I will still get the duplicate records in InfoCube?
Also, do I need to Delete Change log data?

Hi Ramesh,
The entries in Active Data of ODS looks good. No duplicates.
When i checked Change log,
I had entries in ODS change log from two differnent requests.
Request1 (Full repair request via PSA) in ODS (ODSR_xxxx1) has records the same as in R/3
(eg., entry for DocumentA has keyfigure as value +$1000)
Request2 (Delta Load via PSA) in ODS (ODSR_xxxx2) has two records with posive and negative keyfigues
(eg, entries for DocumentA has keyfugure as value +$1000 and DocumentA has keyfugure as value -$1000)
So, not sure if I should call these records as 'duplicates'.
But, I see 3 entries in InfoCube for DocumentA with keyfigure values as +$1000, -$1000 and +$1000.
I beleive the ODS change log should actually cancel the earlier +$1000 and load the new +$1000 entry.
But, it seems to be not replacing the old one.
I hope i am clear.

Regarding the generation of the change log request

Hi,
While going through the BW310 document,i came across the below notes..
The user can choose whether the changes called up from the different load requests are to be combined in a change log request, or whether a change log request is to be generated for each loaded request.
How can i make the above settings.Where should i go inorder to get the screen where i can mention 'A change log request is to be generated for each loaded request'.By default the setting is like that.But i would like to know where to make these settings.
Please help me.
Regards,
Rajesh janardanan

Hi rajesh,
If you select do not condense request into one request when activation takes places, ur generating one change log request for each loaded request. i.e while activation, each request is activated seperately and for each activation, one change log request is created. The advantage of this is you can delete individual request at the time of deletion from the ODS ( if at all u want to ). Suppose you club request and activate, and in the one request u want to delete later, then ull endup deleting all the request which are activated together.
Process request serially when activation takes place has nothing to do with the change log requests. It sees to it that the activation process is serial instead pf parellel.
Please post for more
Sriram

After deletion ODS change log, Delta upload OK?

Hi all,
Now I am reducing data from BW server. For this purpose, I will delete ODS change log. Both of data "from ODS" and "to ODS" are uploaded by Delta Upload.
If I delete change log after last delta initialization, is there any problem to next delta upload?
For example, the last delta initializing was done April 1. And I delete the change log up to April 30. After this operation, can be expected any problem to Delta upload?
Bamboo Shampoo

I dont think it will cause any issue with next delta loads.
Data goes from ODS to its targets from change log table.
But I think better have strategy like..'delete change log data only for requests older than say...1 month or 2 months..'
so that if u have problems with recent data loads..u can reload easily..
u can also try cleaning up old requests from the PSA tables in the system..
cheers,
Vishvesh

Process Chains and Process Types for ODS Change logs

We have created and used process chains to manage a large amount of our batch processing. I am looking to convert our batch process of deleting data from ODS change logs into a process chain. I have been unable to find a process type that will allow us to do this.
Any thoughts?

Hi Lisa,
You can use Process "Deleting Requests from the PSA" for deleting PSA and change log data.
Since the change log is also stored as a PSA table, you can also use this function to delete change log
records. You can find additional information under Deleting from the Change Log.
More info:
Deleting Requests from the PSA
http://help.sap.com/saphelp_nw04/helpdata/en/b0/078f3b0e8d4762e10000000a11402f/content.htm
Deleting from the Change Log
http://help.sap.com/saphelp_nw04/helpdata/en/6d/1fd53be617d524e10000000a11402f/content.htm
Hope it Helps
Srini

Delete overlapping requests from cube not working in processchain.

In a process chain, 'deletion of overlapping requests from the cube ' step is used.
Before this step a DTP step runs with a full update to load the cube. This process chain is scheduled every day.
Issue is, the process chain failed at the DTP step and after correcting and repeating, the step got executed.
However, the next step after the DTP,'delete overlapping requests from the cube'
gets executed but without deleting the previous day's request.
In the step details a message that 'No request for deletion were found' can be seen.
Then next day when the DTPstep is executed without any problem the 'delete overlapping requests from cube' step is successful
and the previous requests from cube are deleted.
the deletion selections in the step ' delete overlapping request from infocube' is
Delete existing requests
Conditions:
only delete requests from same DTP
Selections
Same or more comprehensive
Because of this issue on a particular day because of the presence of 2 days requests the data is getting aggregated and shown as double in the reports.
Please help.

Hi Archana,
When you delete the bad request from target and before repeating your DTP in PC, make sure the bad request deleted from table RSBKREQUEST also.
If you find the same request in table, first delete the request from table and repeat the DTP in PC.
Now Delete overlapping step should work.
As this is not the permanent solution, please raise an OSS for SAP
Regards,
Venkatesh

Deleting requests from Cube with code using infopackage with two targets

hi experts,
Working on BW 3.5.
I am creating a process chain to load from a table in a source system to two Infocubes.
In the start routines of the update rules depending on the date of load, if it is not the last day of month InfoCube A will be loaded with data and InfoCube B will have Datapackage deleted but a request will still load but will contain no data.
And vice versa if it is the last day of month.
In InfoCube A I only want to retain a rolling 15 days of data and have entered a "Delete Overlapping Request from Cube" step.
In the "Deletion-selections" of this step I have added a "Request Selection through Routine" and put in the following code;
del_date = sy-datum - 15.
loop at l_t_request_to_delete.
    if l_t_request_to_delete-timestamp+0(8) GT del_date.
      delete l_t_request_to_delete.
    endif.
endloop.
My question is, how can I ensure this delete code will only work for InfoCube A, as I only want the rollings 15 days of data in here, in Infocube B I want to store all the requests that are loaded here for the end of month.

Hi
Try in some sql browser with outer joins and you will see the problem.
select *
from (select nvl(leverklant.klant_code,'-1') fk_cube_abonnementen_kla_code,
     nvl(factuurklant.klant_code,'-1') fk_cube_abonnementen_kl2_code
     from ods_titsub
     left outer join dim_klant leverklant on (leverklant.klant_code = ods_titsub.cust)
     left outer join dim_klant factuurklant on (factuurklant.klant_code = ods_titsub.sta_cust)
     where (case substr(ods_titsub.isbn,1,8) when 'FBVISTAQ' then 'J' else 'N' end) = 'N'
     and ods_titsub.rec_sta <> 'X'
     and ods_titsub.curr_start >= to_date('01011999', 'DDMMYYYY')
     and ods_titsub.curr_start <= to_date('01022008', 'DDMMYYYY')
     and (leverklant.klant_sk is null or leverklant.klant_sk = leverklant.dimension_key)
     and (factuurklant.klant_sk is null or factuurklant.klant_sk = factuurklant.dimension_key)) a
left outer join dim_klant b on
     b.klant_code = a.fk_cube_abonnementen_kla_code and
     b.dimension_key = b.klant_sk and b.klant_sk is not null
left outer join dim_klant c on
     c.klant_code = a.fk_cube_abonnementen_kl2_code and
     c.dimension_key = c.klant_sk and c.klant_sk is not null
Regards
Result will be like:
FACT_TABLE DIM1 NULL
FACT_TABLE NULL DIM2
but never like:
FACT_TABLE DIM1 DIM2
Message was edited by:
Armands

How do you add an entry in the monitor log from the update rules?

How do you add an entry in the monitor log from the update rules?

Check this link for relevant SAP recommended implementation.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0c22e690-0201-0010-9581-832abdb5d50d
Sample Code (Routine) available on the last page of the document.
award points if useful

Reporting on ODS (Change log Table)

Hi,
Can we do Reporting on ODS (Change log Table) that can give me the detailed transactions (invoices, cancellation etc) that is stored in the change log table.
If we can do reporting on the change log table, how can that be done? Please Help!
Thanks,

Hi Bharath,
See here:
http://help.sap.com/saphelp_nw04/helpdata/en/49/7e960481916448b20134d471d36a6b/content.htm
You can use a database table as the source of data:
http://help.sap.com/saphelp_nw04/helpdata/en/02/cd0b405bacdd5fe10000000a155106/content.htm
And store in an ODS:
http://help.sap.com/saphelp_nw04/helpdata/en/30/1d09407448c442e10000000a1550b0/content.htm
Hope this helps...

Ods change log

hi all
i wish to schedule the change log deletion for my ods zods1 . however , I am not sure how i can find the ODS change log table name . please guide .
thanks
oops

Follow this menu path right click on ODS -> Manage -> menu environment -> delete change log data. once you go to the screen of delete change log you will see different option to delete right away or schedule for montly deletion.
Hope it is helpful to you.
York

Is there a reviewable change log for Creative Cloud updates

This morning I received a Creative Cloud notification: "A new version of Creative Cloud is available. Update now?". Is there a log that tells us what has been modified so we know what is being installed? I prefer to know whats going on with my machine than just accepting any and all action buttons.
Thanks in advance for your help.
MJ

Thank you Jeff. Have a great day!
Re: Is there a reviewable change log for Creative Cloud updates <http://lycos.com> *Michael
Jordan<[email protected]>
| Designer**
<Removed by Moderator>

How to find all the cubes update rules transfer rules ,programms ,ds,ect

HI SDN
Is there any tables for finding update rules,cubes,multiproviders in the system.
can any body tells me the tables for the objects all the objects
thx

Hi Rubane,
These the tables which gives relevant info,
Here are few of those -
Thought it may be of some use if we make a list of useful BW tables
for instance
v_rszglobv = variables
/bic/f (cubename) is the fact table of a content cube
/bic/D (cubename) P is the package dimension of a content cube
/bic/D(cubename) U is the unit dimension of a content cube
/bic/D(cubename) T is the time dimension of a content cube
/bic/D(cubename) I is the userdefined dimension of a content cube
/bic/m (object name) master data of object
/bic/t (object name) text data of object
/bic/H (object name) hierarchy data of object
you can replace the BIC with BI0 for business content object and cubes
RSDIOBJ - index of all InfoObjects
RSSELDONE - Monitor: Selections for executed request
RSREQDONE - Monitor: Saving of the QM entries, state of the uploads, all info about the upload via request number, field: RNR
ODS Table names
1.New data: /BIC/A (ODS NAME)40
2.Active data: /BIC/A (ODS NAME)00
3.Change log: /BIC/B ( NUMBERS)
RSRREPDIR which is the table containing all your reports.
RSTSODS - table that contain relation between "ODS Name" and PSA Table.
TBDLS - Logical system customization, when you run TA: BDLS
EDP21 - Partner Profile, when you run TA: WE20
RSBASIDOC - Assignment of source systems to BIW systems incl. IDoc type
In V_COMPDIR_COMPIC you can also see all your reports. The advantage is that you can see the name/text of the query, not only the technical id.
RSDCUBEIOBJ Objects per InfoCube (where-used list)
RSDODSOATRNAV InfoObject in ODS (navigational attributes)
RSDODSOIOBJ InfoObject in ODS
RSDIOBJT InfoObject texts
RSDIOBJ Directory of all InfoObjects
RSDKYF Key figures
RSDBCHATR Master data attributes
RSBBSQUERYDIR BW: Directory of the Query Sender
RSBBSQUERY BW: Query Receiver
RSBBSQUERYT BW: Texts for Query Receiver
TQOP Compare Operators for View Maintenance Query
TQOPT Compare operators for view maintenance query (texts)
TQLOT Logical operators for view maintenance query (texts)
ROMSDIOBJ BIW: Assignment of master data attributes to InfoObjects
RODCHA BIW: InfoObjects / characteristics
RODIOBJCMP BIW: InfoObjects / compounding
RODKYF BIW: Key figures
ROAPPLT BIW: Name of the application components
RSUICDONE BIW: Selection table for user-selection update ICs
RODTIM BIW: Time characteristics
RODUNI BIW: Units
RSIST InfoSource texts
RSIS InfoSource (transaction data)
RSISOSMAP Mapping Between InfoSources and OLTP Sources
RSOSFIELDMAP Mapping Between OLTP Source Fields and InfoObjects
RSUPDDAT Update rules key figures
RSUPDKEY Update rule: Key per key figure
RSUPDROUT Update rules - ABAP routine - check table
RSRWBINDEXT Titles of binary objects (Excel workbooks) in InfoCatalog
RSRWORKBOOK 'Where-used list' for reports in workbooks
RSDDIME Dimensions directory
RSDDIMEIOBJ InfoObjects per dimension (where-used list)
RSDDIMET Dimension Texts
RSZCOMPDIR Directory of reporting components
RSZELTATTR Attribute selection per dimension element
RSZELTDIR Directory of the reporting component elements
RSZELTTXT Texts of reporting component elements
RSZELTXREF Directory of query element references
RSZGLOBV Global Variables in Reporting
RSDCUBET Texts for the InfoCubes
SMEN_BUFFC-Table for Storing Favorites.
tables which hold the list of BEx Queries, Web Reports, and Workbooks,
RSRREPDIR
RSZCALC
RSZCEL
RSZCHANGES
RSZCOMPDIR
RSZCOMPIC
RSRWORKBOOK
RSZCOMPDIR - Directory of reporting components
RSZELTDIR - Reporting Component Details
RSBCT_NAVKEY_T
RSBCT_NAVKEYDET
check it in the following table
RSDDAGGL
RSDDAGGLF
RSDDAGGRDIR
RSDDAGGRDIR_M
RSAABAP - Routines
Thanks,
Sudhakar.

Cube update rules transport failing-urgent

Hello All,
We had a set of TPs created for our project. All went well to the QA system. But when we tried to move these transports to the PROD, first we had a set of TPs failed, all related to the activation of the update rules of the cube we have. We found that this happened ( I think so) because we missed sending changes of a few display attributes, changed to Navigational attributes, to PROD. These navigational attributes are used in the cube. Even after sending the changes of display attributes to NAV attributes, still the TPs are failing. We tried activating the cube update rules by creating new TP and transporting to PROD. But the TP failed. As nobody in us have the authorization for activating the update rules directly in PROD, we are facing the problem. We are in doubt even if we create another new TP for activation of the UR, we may still fail to activate the UR.
Can anybody help me with this.
Many Thanks in advance
Vinay

Hello Dinesh,
When I recreated transports, I included the cube and its update rules in 2 transports. All other object, like the infoobjects changed/created, Navigational attributes are already in production box. When I sent the TPs with cube activation and update rules activation, the TP with the UR activation failed again.
Hi Siggi,
When I try to open the update rules in PROD, I am unable to open and I get a message that there is error in UR coming from the data mart infosource to the cube.
Could you please suggest me something more.
Thanks a lot
Regards
Vinay

DSO - Cube : Update Rule Error

When trying to push data from an DSO to a ube, the request stays amber until finally short dumping.
The update rule is activated and all key figures, characteristics and time characteristics are filled correctly from the DSO.
The error message in the monitor of the request is:
<i>Update Rules (15199 => 0 records) : Errors Occurred</i>
How do I see the exact error description of what caused the update rule not to transfer any records? I can't seem to find much information in the monitor of what went wrong.
Thanks in advance,
Matt

There is a characteristic called 'Reporting Week' that uses some routine to convert the a document 'created on' date in the week/year format (e.g 01.2008).
Code of this routine is below. All other characteristics or key figures in this update rule are matched with source fields.
fill the internal table "MONITOR", to make monitor ent *ries
result value of the routine
DATA: i_per(3) type n,
i_year(4) type n.
CALL FUNCTION 'DATE_TO_PERIOD_CONVERT'
EXPORTING
I_DATE = COMM_STRUCTURE-createdon
I_PERIV = 'ZW'
IMPORTING
E_BUPER = i_per
E_GJAHR = i_year
EXCEPTIONS
INPUT_FALSE = 1
T009_NOTFOUND = 2
T009B_NOTFOUND = 3
OTHERS = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
concatenate i_year i_per+1(2) into RESULT.
if the returncode is not equal zero, the result will not be updated
RETURNCODE = 0.
if abort is not equal zero, the update process will be canceled
ABORT = 0.

Identify ODS change log request from Cube update rules init routine

Similar Messages

Maybe you are looking for