Java-enabling an SAP application without a BAPI

Java-enabling an SAP application without a BAPI

I am using JCO to interact with SAP. In that I need to create one Sevice Contract from Java application by calling a BAPI. But the SAP system doesn't have the related BAPI to create the contract. Is it necessary to create a BAPI? If so, how should I go about it? Any suggestions are welcome.


    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Using JCo, you are not limited solely to calling R/3 BAPIs. The power of JCo allows you to call ANY RFC-enabled ABAP application within SAP.

You can import your ABAP application into SAP's Function Builder, describe the required set of input/output parameters, and call your new RFC using JCo. However, a major caveat here is that SAP does not allow you to directly call existing R/3 function modules even from within an ABAP application. The purpose of the BAPI interface is to provide prescribed methods for calling SAP function modules from outside SAP. Calling these modules directly, even if a BAPI doesn't exist, is done so at your own risk.


This was first published in July 2002