ods

[Former Member]

when ever we delete the request in ods,

it delets above requests also.

how to control this problem.

[raj_sharma]

Hi,

Can anyone please let me know what can be done to reload the data in DSO after deletion. For example:

I am loading data in DSO from past 10 days ( and all the requests are activated in DSO) and i got to know that there is some problem with data which i loaded on 4th day. Now, if i have to delete this data then, I will have to delete this 4th request which will autometically delete all the requests which are loaded after 4th day.

What should be my approach to reload the data for these 7 days?

Thanks in advance.

Regards,

RJ

[Former Member]

Hello Mahesh,

Wheneever we try to delete any request in a ODS which is activated, we have to delete all the recent ACTIVATED requests above it or the system will automatically delete it for us.

Its a property of a ODS and it has no solutions. This is set to maintain the changelog status of the ODS.

Regards,

Pankaj

[Former Member]

Hi mahesh,

Deleting Data from the ODS Object

Use

Deleting individual requests serves primarily to remove incorrect requests from the ODS object.

Like InfoCubes, you can also delete all data from the ODS object or even delete the entire ODS object. See also Deleting InfoCubes and InfoCube Contents.

Prerequisites

You have to differentiate between two situations:

...

1. The request(s), or the request(s) to be deleted, are not yet activated. In these cases, the requests are simply deleted from the activation queue during the deletion process. Because they were not yet activated, no adjustment occurs for the table of active data or the change log.

2. The request(s), or the request(s) to be deleted, are already activated.

A prerequisite for this would be that the requests to be deleted have not yet been updated or are no longer updated in the connected data targets. In this case, see also Deleting from Already Updated Data.

Since several requests can be activated in one activation run and you have the option of putting them together in a change log request, two cases have to be differentiated here:

- For each downloaded request (called a PSA request later on), there is exactly one change log request. In this case, the change log request is deleted from the change log and from the table of active data.

- Several PSA requests are assembled for a change log request in an activation run. In these situations, you have to delete all of the other PSA requests that are included in the same change log request when deleting a (PSA) request.

Functions

In both of the above-named cases, a rollback is executed during deletion. Rollback means that the status is restored that prevailed before posting the request to be deleted. As long as the request to be deleted is not the last one in the ODS object, all requests that were activated after the one to be deleted have to also be deleted from the ODS object.

In order to delete data from an ODS object, you have several different options. All of these options can be accomplished from the administration of the ODS object . The option you choose depends on your application scenario.

...

1. If you want to delete entire requests that are incorrect, then choose Delete by Request. With this, requests that are not activated can be deleted from the activation queue, or activated requests can be deleted from the active data table and the change log.

2. If you only want to delete individual fields instead of an entire request, choose Delete Selectively. With this, you can delete data, for example, from a time period that is no longer used. In doing so, only data from the table for active data is deleted, while the change log remains unchanged.

3. If you only want to delete data from the change log, choose Delete from the Change Log. With this, you can reduce the scope of the change log if several requests have already been loaded, and only a limited history needs to be retained. Thus, the data volume of the change log is reduced.

Delete by Request

Use

With this function, you can delete both inactive and active requests from ODS objects. This allows you to delete incorrect requests, since the system usually only recognizes errors in the data or in the update rules after the request has been activated. In doing so, the request is deleted from both the table for active data as well as the change log.

Integration

An error message appears if the request has already been updated into additional data targets. In this case, you have to delete the request to be deleted first from the data targets. See also Deleting from Already Updated Data.

Afterwards, you have to reset the data mart status manually in the ODS object. Then you can delete the request. You can load more deltas after this.

If you do not reset the data mart status, then the delta update is deactivated in the connected data target upon deletion.

Functions

You can only directly delete requests that have yet to be activated. The system uses the rollback for requests that have already been activated.

Rollback:

With the roll bck, the BW system returns to the status it had in the ODS object before you booked in the incorrect requests. This means that all requests that were updated after the incorrect request are also deleted. Afterwards, you can once again post available requests in the PSA.

If you posted three requests and want to delete the middle one, the last request is also deleted.

It might also be possible that three requests are grouped together in the ODS object when activating a request. In the source ODS object, it would also be possible that request 1, 2, and 3 would correspond to request 1 in the target ODS object. If you now want to delete request 3 from the source ODS object, you would have to delete request 1 from the target ODS object, because three requests are grouped together in this one. Subsequently, you would also have to delete all three requests from the source ODS object in order to remain consistent.

thanks'

shekar