If you need to learn more about BAPI (Business Application Programming Interface), then please read and use the SAP BAPI Learning Resources presented here. BAPI is a set of interfaces to object-oriented programming methods that help developers integrate 3rd party applications into SAP's R/3 software. To initiate and perform tasks such as uploading transactional data, BAPIs are implemented and stored in the R/3 system as remote function call (RFC) modules. The following BAPI tutorials and learning documents will describe what a BAPI is, how it is used, and where it fits into an integrated software environment. Examples, tips, tools, and expert advice are also included here to further your understanding on using BAPIs.
BAPI Quick Start
BAPI (Business Application Programming Interface)
A great resources to start learning about BAPI is is Sappoint.com's Introduction to BAPIs.
In addition, SAP offers a detailed BAPI User Guide that will explain and help you understand all of the fundamentals, including terminology, rules for usage and prerequisites. SAP also offers a BAPI Programming Guide that will help you learn much of the technical aspects of BAPI.
Here are definitions for some acronyms related to BAPI:
Finding BAPIs
If you need to find a specific BAPI, here are several lists of BAPIs by version, you may want to bookmark them for the future:
In addition, here is a information-packed article from SAP.info that explains how to find a BAPI.
Understanding BAPI development
This section will help you to understand BAPI conventions and to learn the rules and tools for BAPI programming. The following describe BAOI methods, standardized conventions and development tools.
BAPIs, RFC and IDOCs
Learn more about BAPIs, RFCs and IDOCs and how they work together. This section will help you to understand how RFCs relate to BAPIs.
A BAPI is a business object. An RFC is functional code. IDOCs OR intermediate documents are standard data structures for electronic data interchange (EDI) between application programs. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Included here is expert advice from SearchSAP.com:
- Clarifying BAPIs, IDocs and Partners
- BAPIs vs. IDocs
- BAPIs vs. IDocs tip
- Difference between BAPI and RFC
- Will the BAPI function names change?
BAPIs, Java and JCo
If you're a Java programmer you'll need to understand how to call BAPIs using JCo. This section explains how to use the SAP Java Connector.
- Calling BAPIs through JCo
- Why build a custom JCo repository?(tip)
- Developing Applications with the "SAP Java Connector"(PDF)
- Introduction to SAP Java Connector (JCo) Client Programming (webcast)
- A Brief Introduction to the JCo Server
- How can I get a JCo list of supported BAPIs?
- Talk to SAP with JCo
BAPI Errors
Learn about some common BAPI errors and their solutions.
BAPI chat
Here are answers to frequentl BAPI questions, along with an interview with a BAPI expert.
- BAPI return code
- Transforming BAPI XML output into HTML using XSL
- BAPI_ENTRYSHEET_RELEASE
- BAPI_GOODSMVT_CREATE
- BAPI_MATERIAL_SAVEDATA
- BAPI or RFC for payment posting
- Uploading Appraisals into SAP using BAPI
BAPI Quick tips
Use these techniques and tips from BAPI programmers to fix and handle some of your difficult BAPI problems. Understand what is meant by asynchronous and synchronous BAPIs, learn about BAPI COMMIT and messaging.
No comments:
Post a Comment