cancel
Showing results for 
Search instead for 
Did you mean: 

Newbie: Creating a DataSource

Former Member
0 Kudos

I'm trying to create a basic DataSource and am encountering a strange error.

1) Right-click application component -> Create DataSource

2) Give name, pick source system, pick type of "Master Data Attributes", hit OK.

3) "Change DataSource" screen comes up

4) Enter descriptions on "General Info." tab

5) Switch to Extraction tab

6) Enter table name.

Then I hit the problems:

A) If I click the popup button next to the table name and click execute I get the error:

"Some table name(s)like: product are invalid

Removed from selection ->Long Text"

What does that mean?

B) Can the system auto-populate the input-fields? I can't get this to happen.

C) If I try to manually enter field definitions, I get a variety of strange errors (not worth posting)

What else can I do at this point to move forward? I want to import the attributes data from my external database into SAP.

Accepted Solutions (1)

Accepted Solutions (1)

former_member188975
Active Contributor
0 Kudos

Hi,

I'll move this to the BI area where you can get more attention on this problem.

Also, are you trying to pull from a table that is not in the same SAP system as where you are creating the datasource?

Former Member
0 Kudos

Thank you Bhanu.

Yes, I'm using an external MS SQL Server database that is running on a different server. I've setup the "Source System" entry and that seems to work.

If I type "product", which is the correct table name, I get the error that I described. If I type gibberish, I get a different error. This signals that SAP is correctly talking to the source database.

If I can create a dummy table with dummy data and get that to work, I can troubleshoot from there. But right now, I'm just stumped.

Is there a log somewhere that I can look at or anything that I can do?

Former Member
0 Kudos

The problem was that my table name was lowercase. The table name MUST be uppercase. My database is case-insensitive, but the uppercase requirement still holds.

If I create an uppercase view into the table, and reference that view, this error goes away.

Answers (0)