If you are using Access 97, you can download directly into an access
database from SAP. See program RIACCESS for details. You have to establish
an RFC destination PS_ACCESS_1 and 2.

There are then a couple of function modules. Go to SE37 and put in
*msaccess* and hit PF4.

The following is from the readme file: sapgui/ps/readme.sap

For the MS-Access interface SAP delivers 4 files:

WDPSASTR.EXE This is an RFC server program that is called by SAP R/3
(PS module).
This program creates a MS Access database. The structure
information
of the tables is transferred from R/3. In addition to
these tables
a table named DDIC is created. This table contains the
structure
information and should in no case be modified or deleted.

WDPSATAB.EXE This is an RFC server program that is called by SAP R/3
after WDPSASTR.
This program filles the tables of the database with data.
There must not be made any changes of the structure of
the tables
between the calls of WDPSASTR and WDPSATAB.

WDPSAZET.EXE This is an RFC client program that triggers work/time
confirmations in
the PS module of SAP R/3 (like transaction CN27 Collectiv
confirm).

WDPSAMAT.EXE This is an RFC client program that triggers material
confirmations in
the PS module of SAP R/3 (like transaction MB1A - Goods
Withdrawal).

All of these programs need the RFC DLLs

You need to go to the SAP install again and install the
RFCSDK. First, make sure you do a find on your PC to make sure it is not there

This procedure is not documented but here is how I got it to work.

I suggest you use RIACCESS instead. You will have to setup two RFC
destinations PS_ACCESS_1 and PS_ACCESS_2 and will have to get them to point
to wdpsastr.exe and wdpsatab.exe respectively. You will also have to
install the PS utilities, which are part of SAPGUI install CD.

Also, you should know that Access only supports tables with up 255 fields.

RIACCESS is a report and can be run from SE38. To setup RFC destinations you
have to go to SALE -> Communication -> Define RFC Destination. Then define the RFC
destinations. You will also have to install PS kit (part of SAP GUI install CD,
talk to your friendly BASIS person to install this).
Make sure you point the execution path in your RFC
Destinations to the directory where you install the wd files, so you might
want to do this first. Then execute RIACCESS and choose PS_ACCESS_1 to
generate access tables.

In SAP create two RFC Destinations:
ps_access_1 and ps_access_2.
These point to files wdpsastr.exe and wdpsatab.exe (on my pc).

I copied the ocx files to my local pc and ran
the programs aprxdist.exe, axdist.exe, and com32upd.exe. I assume these
programs install the ocx, vbx, tlb (etc) files.

Set Up RFC Destination
In this IMG activity, you set up the Remote Function Call destination in the R/3 System.

Activities
1. Creating RFC destinations
a) In the R/3 main menu, choose Tools -> Administration -> Administration -> Network -> RFC destinations (transaction SM59).
The "Display and Maintain RFC Destinations" screen appears.
b) Choose Edit -> Create.
The "RFC Destination" screen appears. Enter the following data:

RFC destination: Name of your RFC destination, WWI_WORD_START

Connection type: T
Connection type T stands for "TCP/IP connections".
c) Choose ENTER.
Additional pushbuttons are displayed.
d) Under Start on, choose the function Front-end workstation.
e) Enter wwiexe32.exe in the Program field.
f) Document the RFC destination and save your entries.

PS_ACCESS_1   c:\progra~1\sappc\sapgui\ps\access\wdpsas97.exe
PS_ACCESS_2   c:\progra~1\sappc\SAPGUI\PS\ACCESS\wdpsat97.exe
 

Beam Back -> ABAP Cafe for Abapers