Issue: Error in generating export datasource / DSO cannot be activated

 After system copy of Production to development system, there are many issues related to Basis team. One of the issues is DSO not getting activated and throwing error while creating new ones or activating the already existing ones.

If this happens, contact basis team as it is a source system RFC issue. This happened in our case. You might get the same error in many other scenarios but here I am discussing the error due to source system RFC issue.

In every BW system, we have a self system. Suppose your BW system id is BWD100. This will be shown in the source system list.

When the issue comes, do not try to restore or activate any datasources in the self system. Immediately contact your basis team. This is especially important if the system is a client system and any changes in it can have all eyes on you. Restoring the source system has a system wide effect as the process tries to activate all the export datasources present in the source system.

Export datasource is like a backend object which is generated by default whenever you create any DSO. The name of the export datasource will be 8<your DSO technical name>.

In my case, when I checked the self source system by right clicking it, it had shown a green status. But still the issue was persistent.

When Basis team checked it by right clicking on the source system and selecting "Connection Parameter", it was found that the target host was incorrect.

This was corrected and the issue was resolved.

Symptom:

Suddenly, DSOs cannot be activated in the system. Mostly after system refresh/copy.

Error message:

error1

Resolution:

[should be done by basis team]

Go to RSA13, right click on the own system, selected "Connection Parameter"

error2

Correct the host server name in the "Target Host" field

error3

 

 

Comments

Post a Comment

Popular posts from this blog

Domains and Data Elements

  Domains A domain provided Technical attributes (type, length and possible values) for a field. The definition of domain in ABAP is same as that in Mathematics. In the world of Mathematics, a domain is defined as the set of input values that are valid for a given function. The same holds true for domains in ABAP. To understand this, let us first see what is the role of domains in ABAP data dictionary. Domains -> Data Elements -> (Structures, DB tables, program references etc.)
Read more

How to update exchange rates via process chain in BW

Image
 The exchange rate in the BW system may not be updated one. Also the business wants to see the amounts according to the exchange rates in the source. In such cases, you have to update the exchange rate in the BW system via process chain. Include the step ‘Execute ABAP Program’ in the process chain. Give the program name as ‘RSIMPCURR’. Create a variant for the program.
Read more

Sample ABAP program for Updating notepad file data to Internal table and Sending it to Application server

 *--Structure type TYPES: BEGIN OF TY_STD, RONO TYPE C LENGTH 4, NAME1 TYPE C LENGTH 20, GEN TYPE C LENGTH 6, FEES TYPE C LENGTH 10. END OF TY_STD. *--Header line and internal table DATA WKA TYPE TY_STD. DATA INT_TAB TYPE TABLE OF TY_STD. *--Application server files are known as "Datasets" *--here "fname" is the Dataset DATA FNAME TYPE C LENGTH 40 VALUE "StudentsInfo.txt". *--Convert notepad file data into internal table CALL FUNCTION 'GUI_UPLOAD' EXPORTING FILENAME = 'C:Documents and SettingsAdministratorDesktopstudents.txt' HAS FIELD_SEPARATOR = 'X' TABLES DATA_TAB = INT_TAB. *--Sending data to Application Server OPEN DATASET FNAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT. LOOP AT INT_TAB INTO WKA. TRANSFER WKA TO FNAME. ENDLOOP. CLOSE DATASET FNAME.
Read more