Sun Microsystems eWay SAP BAPI - Manual (Page 70)

Chapter 6 Section 6.2
Reviewing the Sample Projects SAP Version Support
eWay™ Adapter for SAP BAPI User’s Guide 70 Sun Microsystems, Inc.
6.1.1
prjBapiOutbound.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.2
prjIDocInbound.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.2
SAP Version Support
The sample Projects described within support SAP version 4.6x, 4.7, ECC 5.0 and ECC
6.0.
6.3
Steps Required to Run the Sample Project
The following steps are required to run the sample projects contained in the
SAPBAPIeWayDocs.sar
file.
1 Import the sample Project.
2 Configure, 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