BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
air_dedman
Calcite | Level 5

I have my SAP R3 info:

authdomain=

client=

language=

ashost=

sysnr=

...and obviously my usrnm and psswd, but for some reason I'm getting a connection fail, does any one know have a sample LIB statement to connect SAS EG to SAP R3?

1 ACCEPTED SOLUTION

Accepted Solutions
jakarman
Barite | Level 11

No r3 sas/access license present no surprise the engine is failing SAS/ACCESS(R) 9.4 Interface to R/3: User's Guide, Second Edition

---->-- ja karman --<-----

View solution in original post

5 REPLIES 5
SASKiwi
PROC Star

It would be helpful if you could supply your LIBNAME statement too. Also what SAS/ACCESS product are you using to connect to R3? If you are not sure use check in EG SAS Server Properties or PROC SETINIT or PROC PRODUCT_STATUS statement to confirm.

air_dedman
Calcite | Level 5

OK  so my SAS/ACCESS types are:

---SAS/ACCESS Interface to PC Files

---SAS/ACCESS Interface to ODBC


the libname statement i think i should be using is...


libname example r3 user=Test password=pwd client=100 language=EN

    ashost=host.biz.server.com sysnr=01;

-------------------------------------------------------

Error I Get, It can't find my R3 engine....

NOTE: Writing TAGSETS.SASREPORT13(EGSR) Body file: EGSR

   

22         GOPTIONS ACCESSIBLE;

23         /*authdomain= biz.server.com

24         client= 100

25         language= EN

26         ashost= host.biz.server.com

27         sysnr= 01 */

28       

29         libname Q31 r3 user=TEST password=XXXXXXXXXX client=100 language=EN

30       

31             ashost=host.biz.server.com  sysnr=01;

ERROR: The R3 engine cannot be found.

ERROR: Error in the LIBNAME statement.

32       

33       

34         GOPTIONS NOACCESSIBLE;

35         %LET _CLIENTTASKLABEL=;

36         %LET _CLIENTPROJECTPATH=;

37         %LET _CLIENTPROJECTNAME=;

38         %LET _SASPROGRAMFILE=;

39       

40         ;*';*";*/;quit;run;

41         ODS _ALL_ CLOSE;

42       

43       

44         QUIT; RUN;

jakarman
Barite | Level 11

No r3 sas/access license present no surprise the engine is failing SAS/ACCESS(R) 9.4 Interface to R/3: User's Guide, Second Edition

---->-- ja karman --<-----
air_dedman
Calcite | Level 5

Thank you, I'll see what my IT department can do about enabling the correct SAS/ACCESS or at the very least setting up an ODBC. That link you sent me, doesn't explain a whole lot to me, if I were to write an ODBC LIBNAME,  what would that code look like?

Thanks for the help Smiley Happy

jakarman
Barite | Level 11

This is the ODB part. It is just basic RDBMS SAS/ACCESS(R) 9.4 for Relational Databases: Reference, Fifth Edition you won't be happy with that as all metadata objects of SAP will be missing.

It that low level access of accessing basic tables.  Having the r3 interface you can hope for more information. Still Sap is a complex environment.

---->-- ja karman --<-----

hackathon24-white-horiz.png

The 2025 SAS Hackathon Kicks Off on June 11!

Watch the live Hackathon Kickoff to get all the essential information about the SAS Hackathon—including how to join, how to participate, and expert tips for success.

YouTube LinkedIn

Creating Custom Steps in SAS Studio

Check out this tutorial series to learn how to build your own steps in SAS Studio.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 5 replies
  • 2240 views
  • 3 likes
  • 3 in conversation