Sun Microsystems SAP BAPI manual SAP Version Support, Steps Required to Run the Sample Project

Chapter 6	Section 6.2
Reviewing the Sample Projects	SAP Version Support

6.1.1prjBapiOutbound.zip

The prjBapiOutbound.zip file contains the prjBAPIOutbound sample project, which demonstrates how to access flight ID and type by passing the airline code via an outbound BAPI.

In addition to the sample Project, the SAP_BAPI_eWay_Sample.zip file also contains the following files generated by running the prjBAPIOutbound sample Project:

ƒinputBAPIFlightGetList.txt—an input text file that contains the airline carrier code “BA”.

ƒoutputFlight1.dat—a sample output file received after running the sample Project.

6.1.2prjIDocInbound.zip

The prjIDocInbound.zip file contains the prjIDocInbound sample project, which demonstrates how to use an inbound RFC to receive IDocs.

In addition to the sample Project, the SAP_BAPI_eWay_Sample.zip file also contains the following files generated by running the prjIDocInbound sample Project:

ƒCREMASoutput1.dat—a sample output file containing CREMAS message type data.

ƒMATMASoutput1.dat—a sample output file containing MATMAS message type data.

6.2SAP Version Support

The sample Projects described within support SAP version 4.6x, 4.7, ECC 5.0 and ECC 6.0.

6.3Steps Required to Run the Sample Project

The following steps are required to run the sample projects contained in the SAPBAPIeWayDocs.sar file.

1Import the sample Project.

2Configure, build, deploy, and run the sample Projects.

You must do the following before you can run an imported sample Project:

ŠCreate an Environment

ŠConfigure the eWays

ŠCreate a Deployment Profile

ŠCreate and start a domain

eWay™ Adapter for SAP BAPI User’s Guide 70 Sun Microsystems, Inc.