Sun Adapter for SAP BAPI

Searching Java CAPS

Table of Contents

Description:

The Sun Adapter for SAP BAPI provides OTD wizard for building BAPI and RFC OTDs by connecting to an SAP R/3 System and a JCA connector, which provides ability to execute BAP/RFC and send IDOCs from Java CAPS to a SAP R/3 System and also to receive BAPI/RFC calls or IDOCs from a SAP R/3 System into Java CAPS.

Adapter Features:

  • Supports both a Non-Unicode and Unicode SAP R/3 Installations
  • Supports Non-Transactional and Transactional-RFC mode of communication with SAP R/3
  • Allows file based TID Management for Transactional-RFC mode
  • Automatic and manual mode of client connection.
  • Ability to create multiple inbound RFC servers.
  • Encoding support for marshal and unmarshal operations when using OTD for IDOC.
  • Inbound and outbound communication with SAP R/3
  • Supports send and receive of any IDOC message type in a generic manner.
  • Support for COMMIT and ROLLBACKS using BAPIs
  • Support for changing paramaters, table types and nested structures
  • Support for relaunchable OTD for BAPIs and RFCs.
  • Support to read configuration parameters from LDAP at runtime.

External System Support/Dependencies:

  • Wizard and runtime need JCO libraries version 2.1.8
  • Supports SAP R/3 version - 4.5B, 4.6B, 4.6C, 4.6D, 4.7(Unicode and Non-Unicode), SAP ECC 5.0 (Unicode and Non-Unicode) and SAP ECC 6.0
  • Supports the SAP R/3 version - 4.6C, 4.6D and 4.7 for Japanese and Korean.

SAP Support Matrix:

SAP Adapter SAP R/3 4.6C Non-Unicode ECC 5.0 Non-Unicode ECC 5.0 Unicode ECC 6.0 Non-Unicode ECC 6.0 Unicode
SAP ALE Adapter Yes Yes Yes Yes Yes
SAP BAPI Adapter Yes Yes Yes Yes Yes

Upgrade Considerations:

  • Any BAPI/RFC OTDs built with SAP BAPI eWay version 5.0.x when imported into Release 6 must be rebuild using BAPI Adapter 6

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact