- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We have installed the Surveyor and follow a parallel approach. First approach is transferring the metadata and transfer specific BW infoprovider transactional content afterwards.
We also have a second approach to select data directly using SQL. Is this possible?
We do not seem to have a correct statement.
The source system is BW on HANA.
Technical name of advanced DSO: CDDPOA02
We are trying statements like this:
LIBNAME SAPBW SASIOSR3 sysnr=10 ashost=asapbwci00.hosting.corp trace=0 destgroup="SAS1" BatchMode=1 language=EN
! Client=100 USER=TESTSAS PASSWORD=XXXXXXXXXXXX;
NOTE: Libref SAPBW was successfully assigned as follows:
Engine: R3
Physical Name: asapbwci00.hosting.corp
PROC SQL;
SELECT count(*)
FROM SAPBW.CDDPOA02;
And get errors like these:
ERROR: Exception while using RFC to SAP: TABLE_NOT_AVAILABLE
We also tried:
SELECT count(*)
FROM SAPBW./BIC/ACDDPOA022;
or some more statements. All to no luck.
Any idea which statement works?
Best Regards,
Eelco de Vries
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
We found the solution by using aliases in the PROC SQL FROM statement to the BW DSO tables.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
You could also add
Options sastrace=',,,d' sastraceloc = saslog nostsuffix msglevel=i;
to possible get out more info in the SAS log.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi LinusH,
Indeed we are also testing new BW authorizations, but this is not where the solution is expected.
Since when we try a normal metadata table in BW we get the authorization message:
SELECT count(*)
FROM SAPBW.RSDIOBJT;
ERROR: Exception while using RFC to SAP: NOT_AUTHORIZED
And not the TABLE_NOT_AVAILABLE message.
So it is purely how to access the BW advanced DSO object via a SQL statement.
Best Regards,
Eelco de Vries
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
We found the solution by using aliases in the PROC SQL FROM statement to the BW DSO tables.