cancel
Showing results for 
Search instead for 
Did you mean: 

ODS Activation Problem

Former Member
0 Kudos

Hi,

I have a Delivery ODS which has 2lis_12_vcitm as the data source. I have initialized the delta with data transfer and loaded successfully. Then I loaded a delta which was successful. But when I tried to activate the ODS data it says "Req XXX has not or not correctly been updated, please edit."

The performance window reads..

Diagnosis

Request REQU_41BBBOJAOR0TQA3AKZ7TROGUR (40,726) for DataSource 2LIS_12_VCITM from source system DEV_030 has the status (green) and a smaller SID (is thus older) than the request that you currently want to update into the ODS object.

System response

This is not possible since the sequence of the requests must be kept when wanting to update them into an ODS object. Delta- and init. requests must be updated into the ODS in the request sequence.

Procedure

First update request REQU_41BBBOJAOR0TQA3AKZ7TROGUR(40,726) for DataSource 2LIS_12_VCITM from source system DEV_030 from the PSA into ODS object.

If you do not need the data in request REQU_41BBBOJAOR0TQA3AKZ7TROGUR (40,726) in the ODS object, you can also set the total status for this request to (red) in the Monitor, on theStatus tab page. When checking for completeness, the system then ignores the request.

I tried to find that request but I couldnt find it in the ODS->manage->requests.

Any input on this will be appreciated.

Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hi ajax,

goto t-code RSRQ and give the request name REQU_41BBBOJAOR0TQA3AKZ7TROGUR and see weather this request is in green red or yellow and try to find weather this is in data target. if not try reconstructing this request ( only if its through PSA, then u can do this ). Once this request is in, then u can probably activate the target.

Sriram

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Ajax,

See whether you are able to find the specified request in Reconstruct tab.

Menupath: ODS -> Right Click Manage -> Last Tab Reconstruct.

Hope this helps.

Cheers!

Bhuvana.

Former Member
0 Kudos

Click monitor directly on the ODS object.

Change the time duration filter and set it as (date of request number slightly lower than 40726) and to current date.

You can find the data load of a request having number slightly lower than 40726 by going to ODS->manage screen and observing the sequence of the requests.

Once you go to monitor,click on each of the requests displayed there.If 40726 is a yellow request and is stil not updated to data target,it will not show in the ODS.

Any request which is yellow might turn to RED when clicked and gives message like 'Trigger follow on events ?'.

Check the request number in monitor by double clicking on the 'REQU_' number in the 1st tab of the monitor details on the right of the screen.Try to find 40726 there.

If it is a valid request then somehow update it to ODS or the new request will never activate.

If its invalid and isnt required,force a QM status change and change it to RED.

Then activation program will not count it and the new request will get activated..

cheers,

Vishvesh

0 Kudos

hi Ajax,

take a look oss note 521522 453833 905922

521522

Symptom

A PSA request cannot be updated to an ODS (with the scheduler in the PSA tree) even though the request does not yet exist in the ODS and all prerequisistes (active update rules ...) have been fulfilled.

(The ODS is not even offered as a possible updating data target in the scheduler in the PSA tree).

This happens if the request SID of the new request to be updated is smaller than the largest activation SID in the ODS which was already updated to the data targets behind.

This check is incorrect and should be checked against the largest request SID of this activation request, which was already updated, rather than the activation request SID.

Other terms

Updating the request from PSA to ODS; activation request SID;

DMEXIST; PROCESSED_ONE; RSM1529; RSM1 529

Solution

Depending on your BW system release, this problem is eliminated as follows:

You can book the request beforehand as well by running through the following procedure:

1. Turn off the automatic update (or an update started some other way) on the ODS! - No-one may extract data from the ODS or otherwise change, reset etc. the delta administration.

2. Note the contents of the field Processed_one in the table rsbodslogstate (se16) and replace the contents by those in the field Processed_all for the ODS object into which you want to update the request. This must make the value smaller than the SID of the request you want to update in the ODS. You get these SIDs by double-clicking on the request number for this request in the monitor.

3. Start the workbench again and call the ODS administrator, the last request now no longer seems to be updated.

4. Subsequently post the request from the PSA into the ODS.

5. Set the contents of the processed_one field back to its previous value again.

6. Activate the request.

7. It is VITAL that you bear in mind that no data should be extracted from this ODS during this action, as otherwise the resetting of the delta administration (table rsbodslogstate) will cause incorrect or already extracted data to be extracted again, or the delta administration might be destroyed.

Using the patches below, you can then book the PSA requests without changing the rsbodslogstate table.

Former Member
0 Kudos

A.H.P,

I dont find the Processed_one field in the RSBODSLOGSTATE table as suggested by the note ??

Any thoughts ?

Thanks.

Former Member
0 Kudos

Ajax

Another way of finding request number is

In RSA1> ODS>Right clickManageChoose Content-->change log. In the next Data Browser screen give your request number and execute "REQU_41BBBOJAOR0TQA3AKZ7TROGUR". see if you find any requests.

Also try in the similar way for new and active Data tabs.

Hope this helps

Thnaks

Sat