cancel
Showing results for 
Search instead for 
Did you mean: 

ODS data mart error

Former Member
0 Kudos

Hi experts,

I created one ODS (I am using 3.5 version) copy from base level ODS and i activated my new ODS update rules by giving base level ODS prefix 8 and its activated fine. Now i ran load from Base level ODS to new ODS and i am getting the below error;

You do not have authorization to extract from DataSource 8Z_PODS, component DM

Message no. R8073

Diagnosis

You are not authorized to extract from DataSource 8Z_PODS in application component: DM .

System Response

The authorization check was performed with the following field values:

DataSource: 8Z_PODS

Application component: DM

Subobject: DATA

Activity: 03

Procedure

To be able to extract from the DataSource, you need authorization for authorization object S_RO_OSOA (authorizations SAPI-DataSource) with the field values specified above.

Procedure for System Administration

There is a role template S_RO_OSOA_TMPL (DataSource (OSOA) Display/Maintain/Extract) available that contains the authorizations to display, change and extract all DataSources.

can any one please help me out.

Thanks

David

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member182516
Active Contributor
0 Kudos

Let me ask you one question why are you again creating the same DSO and populating the data, can you explain the scenario.

Error message clearly tells us that its an authorization issue.

run su53 after trying to run the load step. you can find the missing authorization object, ask your basis to add that object to your id.

Check the below role S_RO_OSOA_TMPL weather you have this role in your profile or not to access the Data source.

Former Member
0 Kudos

Hi Prasanth,

Thanks for your sugession........., in my base level ODS i have 2 types of data like offered data and eligible data, as per my requirment i need to maintain eligible data separately, for this i created another ODS.

Thanks

David

former_member182516
Active Contributor
0 Kudos

first remove the red request if any in the DSO and try to re run the load from DSO - DSO again you will get the same error.

Now try running the transaction SU53 so that it will display any missing authorization objects for your ID.

If you find nothing over there run the Authorization trace and check if all the authorization objects that are displayed in the trace are in your used login id.

To run the Authorization trace use Tcode st01.

Instead of loading data from DSO you can extract data from DS as per your need.

In the second DSO select the eligible data and store init.