Defining ABAP BAPI Methods in the BOR

To represent the remote enabled function module as a BAPI, BAPI Wizard is used. The wizard generates some additional code to allow the BAPI to be called as a workflow method apart from being called by an outside program.
When creating a new object type in BOR (Business Object Repository), there can be two possibilities. Either it is created as a subtype of an existing business object or it is created as a new business object from scratch.

Create a business object using the T-Code SWO1


When create button is clicked, the following popup screen appears:

NOTE:
Enter any logical name in the Program that does not already exist. The program is generated by the wizard for the object type and not for the function module that we have already created.

Press enter and the new business object gets created. The business object gets created with the standard interface that contains an Interface IFSAP, an Attribute ObjectType, and two methods namely ExistenceCheck and Display. All these cannot be changed. It looks something like this:


Now we will add a method to the business object. For this, we will choose from the menu path, Utillities -> API methods -> Add method. The following window appears


Write the name of the function module in the dialog box and press enter.

The following dialog box will appear. This is the start screen of the BAPI wizard. Proceed with wizard by pressing the button.


The next screen that appears is given below:


Again press the button. A popup appears prompting to generate the template automatically. Click the Yes button in the screen as given below.


On completing the process in the wizard, you will find that the GetBillitems has been added to the business object:


To use the business object Object type status has to be set to Implemented.


The BAPI wizard adds a wrapper class for the function module which can be used as method in the business object. Click on the Program button or select Goto  Program from the menu. A code something like this can be seen.

***** Implementation of object type ZBILLITEMS *****
INCLUDE OBJECT.
BEGIN_DATA OBJECT. " Do not change.. DATA is generated
* only private members may be inserted into structure private
DATA:
" begin of private,
" to declare private attributes remove comments and
" insert private attributes here ...
" end of private,
KEY LIKE SWOTOBJID-OBJKEY.
END_DATA OBJECT. " Do not change.. DATA is generated

BEGIN_METHOD GETBILLITEMS CHANGING CONTAINER.
DATA:
IVBILLNO LIKE ZBAPI_BILL_ITEMS-VBELN,
RETURN LIKE BAPIRETURN,
ITVBRP LIKE ZBAPI_BILL_ITEMS OCCURS 0.

SWC_GET_ELEMENT CONTAINER 'IvBillno' IVBILLNO.
SWC_GET_TABLE CONTAINER 'ItVbrp' ITVBRP.

CALL FUNCTION 'ZBAPI_GET_BILL_ITEMS'
EXPORTING
IV_BILLNO = IVBILLNO
IMPORTING
RETURN = RETURN
TABLES
IT_VBRP = ITVBRP
EXCEPTIONS
OTHERS = 01.
CASE SY-SUBRC.
WHEN 0. " OK
WHEN OTHERS. " to be implemented
ENDCASE.

SWC_SET_ELEMENT CONTAINER 'Return' RETURN.
SWC_SET_TABLE CONTAINER 'ItVbrp' ITVBRP.
END_METHOD.



Generate & Release

After finishing the above steps, do the following:

Go to SE37 and release the API enabled Function module

In the Object created in the BOR, set the status of Object Type Component to Released


Set the status of Object Type to Implemented


You can now display the BAPI in the BAPI Explorer. Invoke the same using the T-code BAPI

EXAMPLE SHOWING HOW TO CREATE A BAPI

Programming a BAPI consists of some tasks like: •Defining BAPI Data structures ( using SE11 )
•Creating BAPI Function Modules (For each method)
•Defining BAPI Methods in the BOR
•Documentation of the BAPI
•Generate ALE interface for asynchronous BAPIs
•Generate and release

NOTE:
Here we will not be covering the two points – Documentation of BAPI and Generating ALE Interface for asynchronous BAPIs.

NOTE: You can use the BAPI explorer (T-code BAPI) to get a step-by-step instruction / checklist in how to create a BAPI. In the BAPI explorer select the Project tab.


EXAMPLE – HOW TO CREATE A BAPI
In the example we will create a BAPI that reads some information about the line items for a Sales Invoice from table VBRP based on the Invoice No. that is supplied to the import parameter of the BAPI Function Module.

BAPI Name ZGetInvoiceItems
Function group ZBAPIVIN
Function module: ZBAPI_GET_BILL_ITEMS
FM Import parameters : IV_BILLNO TYPE ZBAPI_BILL_ITEMS-VBELN
FM Tables :IT_VBRP LIKE ZBAPI_BILL_ITEMS
FM Export parameters : RETURN LIKE BAPIRETURN

Defining BAPI Structures

This is the basic step followed while creating BAPIs. All the relevant structures that are required for BAPI have to be created using T-Code SE11. The structures can be created for Import/Tables parameters. Use Data type -> Structure

In our case we do not have multiple inputs but just one input i.e. Sales Invoice No. and so we have not made use of any structure for the purpose. But if required, structure can be used for import parameter also.

The following are the components of structure ZBAPI_BILL_ITEMS:

Field Name Description
VBELN Invoice Number
POSNR Invoice Item Number
MATNR Material Number
FKIMG Quantity
VRKME Sales Units (Quantity)
NETWR Amount

Point of Caution
It is required to define a structure for every parameter in the BAPI and use of same structures which are used in existing applications cannot be done because BAPI structures are frozen when BAPIs are released and then there are restrictions on changing them.


Screenshot of Structure – ZBAPI_BILL_ITEMS



Creating BAPI Function Modules (For each method)
We must create new function group for each BAPI. If the BAPIs are related then the same can be grouped under the same FUNCTION GROUP to enable the sharing of global data amongst the related BAPIs

Screenshot of Attributes Tab in the FM ZBAPI_BILL_ITEMS


Screenshot of Import Parameters Tab in the FM ZBAPI_BILL_ITEMS


Screenshot of Export Parameters Tab in the FM ZBAPI_BILL_ITEMS


NOTE:
Since Remote Enabled module processing type is selected and the Import/Export parameters can only be BY VALUE for an RFC enabled function module, select the checkbox for Pass Value for each IMPORT/EXPORT parameter.

Screenshot of Tables Tab in the FM ZBAPI_BILL_ITEMS



Code in the Function Module ZBAPI_BILL_ITEMS &
related Includes in the Function Group

INCLUDE LZBAPISTATUSUXX
*****************************************************************
* THIS FILE IS GENERATED BY THE FUNCTION LIBRARY. *
* NEVER CHANGE IT MANUALLY, PLEASE! *
*****************************************************************
INCLUDE LZBAPIVINU01.
"ZBAPI_GET_BILL_ITEMS

INCLUDE LZBAPIVINTOP “ Global data
FUNCTION-POOL ZBAPIVIN. "MESSAGE-ID

TABLES: VBRK, VBRP.
DATA: T_VBRP LIKE ZBAPI_BILL_ITEMS OCCURS 0.

* STRUCTURE FOR RETURN MESSAGES BY BAPI FUNCTION MODULE
DATA:
BEGIN OF MESSAGE,
MSGTY LIKE SY-MSGTY,
MSGID LIKE SY-MSGID,
MSGNO LIKE SY-MSGNO,
MSGV1 LIKE SY-MSGV1,
MSGV2 LIKE SY-MSGV2,
MSGV3 LIKE SY-MSGV3,
MSGV4 LIKE SY-MSGV4,
END OF MESSAGE.

INCLUDE LZBAPIVINU01 - Subroutines
***INCLUDE LZBAPIVINU01.
FUNCTION ZBAPI_GET_BILL_ITEMS.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(IV_BILLNO) TYPE VBELN
*" EXPORTING
*" VALUE(RETURN) TYPE BAPIRETURN
*" TABLES
*" IT_VBRP STRUCTURE ZBAPI_BILL_ITEMS
*"----------------------------------------------------------------------
* Check if the Invoice exists
select single *
from vbrk
where vbeln eq iv_billno.
if sy-subrc ne 0.
* If not return the error message
clear message.
message-msgty = 'E'.
message-msgid = 'Z3'.
message-msgno = '001'.
message-msgv1 = iv_billno.
perform return_bapi_message using message
changing return.
exit.
endif.

* If the Invoice exists, get all the required item lines information
* in the table it_vbrp
refresh it_vbrp.
clear vbrp.

select vbeln posnr matnr fkimg vrkme netwr
into table it_vbrp
from vbrp
where vbeln eq iv_billno.

ENDFUNCTION.

*---------------------------------------------------------------------*
* FORM RETURN_BAPI_MESSAGE *
*---------------------------------------------------------------------*
* --> VALUE(IV_MESSAGE) *
* --> XV_RETURN *
*---------------------------------------------------------------------*
form return_bapi_message using value(iv_message) like message
changing xv_return like bapireturn.

check not message is initial.

call function 'BALW_BAPIRETURN_GET'
exporting
type = iv_message-msgty
cl = iv_message-msgid
number = iv_message-msgno
par1 = iv_message-msgv1
par2 = iv_message-msgv2
par3 = iv_message-msgv3
par4 = iv_message-msgv4
importing
bapireturn = xv_return
exceptions
others = 1.

endform.

HOW TO CREATE OWN BAPI’S

Topics covered under this are:

•What is BAPI?
•Some Conventions about BAPI
•Example showing How to Create a BAPI

What is BAPI?
BAPI is an abbreviation used for Business Application Programming Interface. These are interfaces within the business framework to link SAP components to one another and SAP components with third-party components.

The SAP Business Objects are an essential part of the Business Framework and the prerequisites for interoperability. SAP Business Objects cover a broad range of R/3 business data and processes and can be accessed using BAPIs. The SAP Business Objects and their BAPIs thus provide an object-oriented view of R/3 business functionality.

The SAP Business Object types are defined by the following:

Object type
The object type describes the features common to all instances of that object type. This includes information such as the unique name of the object type, its classification, and the data model.

Key fields
The key fields determine the structure of an identifying key, which allows an application to access a specific instance of the object type. The object type "Employee" and the key field "Employee.Number" are examples of an object type and a corresponding key field.

Attributes
An attribute contains data about a Business Object, thus describing a particular object property. For example, "EMPLOYEE.NAME" is an attribute of the "EMPLOYEE" object type.

Events
An event indicates the occurrence of a status change of a Business Object.

Interfaces
Interfaces are groups of related methods associated with an object type.

SOME CONVENTIONS ABOUT BAPI
•Methods
•Parameters
•Standardized BAPIs
•Standardized Parameters
•Guidelines for BAPI development
•BAPI/ALE Integration

Methods
A method is an operation that can be performed on a Business Object and that provides access to the object data. A method is defined by a name and a set of parameters and exceptions, which can or must be provided by the calling program in order to use the method. BAPIs are examples of such methods.
•If the BAPI to be implemented is a standardized BAPI then make use of generic names Like CheckExistence, GetList etc.
•The method name can be of maximum 30 characters and should be in English.
•Underscores are not allowed in BAPIs so to separate the words make used of a combination of upper and lower case characters for e.g. GetDetail
•BAPIs have return parameter that can be either an export parameter or an export table.
•So that customers can enhance BAPIs, each BAPI must have an ExtensionIn and an ExtensionOut parameter.

Parameters
•If standardized parameters are used, you have to use the names specified for standardized parameters.
•BAPI parameter names should be meaningful. A parameter name can be of maximum 30 characters. For example if some BAPI is related to some customer where in customer code is to be input, the parameter name can be CUSTOMERCODE or CUSTOMERNO.
The components of a parameter name in the Business Object Repository (BOR) are separated by upper and lower case letters to make them easier to read. Example: CustomerCode
•Unit of measure fields must accompany all quantity fields and currency identifiers must accompany currency amount fields.

Standardized BAPIs
Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
For details use the link http://www.sap-img.com/abap/bapi-conventions.htm
BAPIs are actually created by and maintained with other BAPIs. The BAPI that creates BAPIs is in the BOR, and is called Create. (There’s also a variation, CreateFromData, that is sometimes useful.) Objects that have already been created, and need to be modified, may be manipulated with the BAPI Change, also found in the BOR.

Other BAPI utilities for object manipulation include Delete and UnDelete, Replicate and SaveReplicate, GetStatus, GetDetail, and ExistenceCheck, all of which are self-explanatory. These handy utilities exist alongside the workhorse BAPIs in the BOR. There is also a convenience in SAP called the subobject—objects attached to a greater object, such as line items on a purchase order. The BOR provides you with Add(subobject) and Remove(subobject) to facilitate these.

Typical of an object-oriented system, BAPIs must be treated as objects. Some are instance-dependent (a specific occurrence of an object); some are instance-independent (requiring class methods). When creating a BAPI, you must obviously be clear about which applies. As an example, if you’re working with a class-method BAPI (e.g., the SalesOrder class), GetDetail isn’t useful, because it returns data items from a specific sales order. Instead, you would use GetList, which would return a list of all instantiations of SalesOrder.

Guidelines for BAPI development
•BAPI structures must not use includes.
•There should be no functional dependencies between two BAPIs
•BAPIs must perform there own authorization check
•BAPIs should not use dialogs
•CALL TRANSACTION or SUBMIT REPORT must not be invoked in a BAPI
•Instead of COMMIT WORK a BAPI must make use of the BAPI TransactionCommit to execute the commit after the BAPI has executed.
•Program should not get terminated due to BAPIs but instead the BAPI must communicate relevant messages through the return parameter.

BAPI/ALE Integration
When you use the BAPIs for asynchronous messaging, the application in the sending system calls the generated ALE IDoc interface instead of the BAPI. Asynchronous BAPIs use the ALE interface this way:
•Creates an IDOC from the BAPI data
•Sends the IDOC to the target system
•Receives the IDOC in the target system, creates the BAPI data from the IDoc and calls the BAPI

An ALE interface for a BAPI is created in transaction BDBG.

Free Download BAPI User Guide (CA-BFA)

Download ----> http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf Tutorial

Create BAPI step by step procedure (by Dinesh deshmukh)

About the Example
STEP 1 - Define a structures for the BAPI
STEP 2 - Write Function Module
STEP 3 - Create the API Method Using the BAPI 5 WIZARD
STEP 4 - Final steps

This BAPI reads system status for a production order from table JEST and system status
text fro table TJ02T



Name ZGetOrderStatus
Function group ZBAPISTATUS
Function module: Z_BAPI_GET_ORDER_STATUS
Import parameters: ORDER_STATUS_IMPORT type
ZBAPI_ORDER_STATUS_IMPORT: AUFNR Order number (Keyfield)
SPRAS Language ExcludeInactive - Checkbox -
Exclude inactive status

Tables T_BAPISTAT type ZBAPISTAT:
OBJNR like JEST-OBJNR
STAT like JEST-STAT
INACT like JEST-INACT
TXT04 like TJ02T-TXT04
TXT30 likeTJ02T-TXT30

Export parameters RETURN like BAPIRETURN



In this step structures for the parameters and tables of the function module used for
the BAPI are defined.

Use Data type -> Structure

Define the following structures:

ZBAPI_ORDER_STATUS_IMPORT which contains the following fields:

ORDERID Order number (Keyfield)
SPRAS Language
ExcludeInactive - Checkbox - Exclude inactive status


ZBAPISTAT:

OBJNR like JEST-OBJNR

STAT like JEST-STAT
INACT like JEST-INACT
TXT04 like TJ02T-TXT04
TXT30 likeTJ02T-TXT30


Important note:

You will have to define a structure for every parameter in the BAPI. You cannot use
the same structures used in existing applications because BAPI structures are frozen
when BAPIs are released and then there are restrictions on changing them.

ZBAPI_ORDER_STATUS_IMPORT

ZBAPI_ORDER_S
TATUS_IMPORT

ZBAPISTAT

Important notes:

Each BAPI must have its own function group.
Under the attrbutes tab remember to select Processing Type Remote Enabled
module, otherwise the function module cannot be invoked via RFC and used as a
BAPI
Import/Export parameters can only be BY VALUE for an RFC enabled function
module
We are only creating one BAPI in this example, but you can create related BAPIs
in the same function pool, so they will be able to share global data.

attributes

Import Parameters

Export Parameters

Tables

Code
Notes:

The subroutine SET_RETURN_MESSAGE is a standard routine used for BAPIs that use the BAPIRETURN structure
In form Z_BAPI_GET_ORDER_SYSTEM_STATUS there is a test IF 1 = 2. If the test is true a mesage is displayed. The condition will obviously never be true, and we will never want to display a message in a BAPI. The reason why it
is included is, that it create a reference for the message, so that the WHERE USED funstionallity can be used for the message. This is the SAP standard way to handle it, copied from the Company Code GetList BAPI.


INCLUDE LZBAPISTATUSUXX

*****************************************************************
* THIS FILE IS GENERATED BY THE FUNCTION LIBRARY. *
* NEVER CHANGE IT MANUALLY, PLEASE! *
*****************************************************************
INCLUDE LZBAPISTATUSU02.
"Z_BAPI_GET_ORDER_SYSTEM_STATUS


INCLUDE LZBAPISTATUSTOP - Global data

FUNCTION-POOL ZBAPISTATUS. "MESSAGE-ID Z3
Types:
begin of Type_tj02t,
istat like tj02t-istat,
txt04 like tj02t-txt04,
txt30 like tj02t-txt30,
end of type_tj02t.



DATA:
* Declarations for TABLE parameter
T_BAPISTAT like ZBAPISTAT occurs 0,
G_BAPISTAT like ZBAPISTAT,
* Table for object texts
t_tj02t type type_tj02t occurs 0,
g_tj02t type type_tj02t.

* Structure for return messages
DATA:
BEGIN OF MESSAGE,
MSGTY LIKE SY-MSGTY,
MSGID LIKE SY-MSGID,
MSGNO LIKE SY-MSGNO,
MSGV1 LIKE SY-MSGV1,
MSGV2 LIKE SY-MSGV2,
MSGV3 LIKE SY-MSGV3,
MSGV4 LIKE SY-MSGV4,
END OF MESSAGE.


INCLUDE LZBAPISTATUSF01 - Subroutines


***INCLUDE LZBAPISTATUSF01 .
*----------------------------------------------------------------------*

*&---------------------------------------------------------------------*
*& Form SET_RETURN_MESSAGE
*&---------------------------------------------------------------------*
* This routine is used for setting the BAPI return message.
*
* The routine is a standard routine for BAPIs that handles the message
* structure for the BAPIRETURN structure. It has been copied from the
* BAPI Company Code Getlist
*----------------------------------------------------------------------*
* -->P_MESSAGE text
* <--P_RETURN text
*----------------------------------------------------------------------*
form SET_RETURN_MESSAGE USING VALUE(P_MESSAGE) LIKE MESSAGE
CHANGING P_RETURN LIKE BAPIRETURN.

CHECK NOT MESSAGE IS INITIAL.

CALL FUNCTION 'BALW_BAPIRETURN_GET'
EXPORTING
TYPE = P_MESSAGE-MSGTY
CL = P_MESSAGE-MSGID
NUMBER = P_MESSAGE-MSGNO
PAR1 = P_MESSAGE-MSGV1
PAR2 = P_MESSAGE-MSGV2
PAR3 = P_MESSAGE-MSGV3
PAR4 = P_MESSAGE-MSGV4
* LOG_NO = ' '
* LOG_MSG_NO = ' '
IMPORTING
BAPIRETURN = P_RETURN
EXCEPTIONS
OTHERS = 1.


endform. " SET_RETURN_MESSAGE
FUNCTION Z_BAPI_GET_ORDER_STATUS

FUNCTION z_bapi_get_order_system_status.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(I_AUFNR) TYPE AUFNR
*" VALUE(I_SPRAS) TYPE SPRAS DEFAULT SY-LANGU
*" VALUE(I_EXCLUDEINACTIVE) TYPE CHAR1 OPTIONAL
*" EXPORTING
*" VALUE(RETURN) TYPE BAPIRETURN
*" TABLES
*" T_BAPISTAT STRUCTURE ZBAPISTAT
*"----------------------------------------------------------------------
**
*"Local interface:
*" IMPORTING
*" VALUE(I_AUFNR) TYPE AUFNR
*" VALUE(I_SPRAS) TYPE SPRAS DEFAULT SY-LANGU
*" VALUE(I_EXCLUDEINACTIVE) TYPE CHAR1 OPTIONAL
*" EXPORTING
*" VALUE(RETURN) TYPE BAPIRET2
*" TABLES
*" T_BAPISTAT STRUCTURE ZBAPISTAT
*"----------------------------------------------------------------------
DATA:
l_aufnr LIKE afko-aufnr,
l_objnr LIKE jest-objnr.


********************************************
* Check if order exists
********************************************
SELECT SINGLE aufnr
FROM afko
INTO l_aufnr
WHERE aufnr = BAPI_ORDER_STATUS_IMPORT-orderid.

IF sy-subrc NE 0.
CLEAR message.
message-msgty = 'E'.
message-msgid = 'Z3'.
message-msgno = '000'.
message-msgv1 = BAPI_ORDER_STATUS_IMPORT-orderid.
PERFORM set_return_message USING message
CHANGING return.
IF 1 = 2.
* The only reason to include this statement, that will obviously
* never execute, is that it will create a referecence so that you
* can find out where a particular message is being used. This
* functionality is used by the BAPIs programmed by SAP
MESSAGE e000(z3).
ENDIF.
ENDIF.
CHECK return IS INITIAL.

********************************************
* Read order status
********************************************
CONCATENATE 'OR' BAPI_ORDER_STATUS_IMPORT-orderid INTO l_objnr.

IF BAPI_ORDER_STATUS_IMPORT-i_excludeinactive = 'X'.
SELECT objnr stat inact
FROM jest
INTO TABLE t_bapistat
WHERE objnr = l_objnr AND
inact <> 'X'.
ELSE.
SELECT objnr stat inact
FROM jest
INTO TABLE t_bapistat
WHERE objnr = l_objnr.

ENDIF.
IF sy-subrc <> 0.
* No object status found
CLEAR message.
message-msgty = 'E'.
message-msgid = 'Z3'.
message-msgno = '001'.
message-msgv1 = BAPI_ORDER_STATUS_IMPORT-orderid.
PERFORM set_return_message USING message
CHANGING return.
IF 1 = 2.
MESSAGE e001(z3).
ENDIF.
ENDIF.
CHECK return IS INITIAL.


********************************************
* Read order status texts
********************************************
SELECT istat txt04 txt30
FROM tj02t
INTO TABLE t_tj02t
FOR ALL ENTRIES IN t_bapistat
WHERE istat = t_bapistat-stat AND
spras = BAPI_ORDER_STATUS_IMPORT-i_spras.

SORT t_tj02t BY istat.

LOOP AT t_bapistat INTO g_bapistat.
READ TABLE t_tj02t
WITH KEY istat = g_bapistat-stat BINARY SEARCH
INTO g_tj02t.
IF sy-subrc = 0.
MOVE:
g_tj02t-txt04 TO g_bapistat-txt04,
g_tj02t-txt30 TO g_bapistat-txt30.
MODIFY t_bapistat FROM g_bapistat TRANSPORTING txt04 txt30.
ENDIF.


ENDLOOP.


ENDFUNCTION.

The BAPI wizard is used toTo expose the remote function module as a BAPI. The wizard will generate some additional code, so the
function module is a valid method of the BOR. This allows the BAPi to be called as a workflow method in addition to be called by an
outside program.

Note: Each functionmodule corresponds to a method in the BOR

Go to the Busines Object Builder SWO1.

You can either create the new Object type as a subtype of an existing business object or create a new business object from scratch. In
this example it would be obvious to create the Object type as a subtype of BUS2005 Production order. However, to illustrate how to
create a new Object type from scratch, we will do this.

In the Object/Interface type field write the name of the new Business Object: ZORDERSTAT. Press enter and fill in the additional fields
necessary to create the object type.

Supertype: Not relevant because we are creating our object from scratch

Program. This is the name of the program where the wizard generates code for the Object type, NOT the function module we craeted
earlier. The program name must not be the name of an existinbg program.

Press enter and create the new business object. Note that when you create the business object a standard interface, an attribute
ObjectType and the methods ExistenceCheck and Display are automatically generated. These cannot be changed!


The next step is to add the Z_BAPI_GET_ORDER_STATUS method to the business object. Select Utillities -> API methods -> Add method and
write the name of the functionmodule in the dialogbox. Next the dialogbox show below will be shown. This is the start screen of the BAPI wizard.
Proceed with wizard by pressing the button.





After you have finished the wizard, tyou will notice that the ZGetOrderStatus has been added to
the business object:


You can doubleclick on the method to see its properties. To use the business object you must change the Object type status to Implemented. Use menu Edit->Change releases
status->Object type->To implemented. No you can test thge object (Press F8).

Note that the BAPI wizard has added a wrapper class for the function module so it can be sued as method in the business object. Choose menu Goto->Program to display the
program:

***** Implementation of object type ZORDERSTAT *****
INCLUDE When the Business object has been checked and the documentation created, the follwing steps must be carried out:

Release the BAPI function module (in the Function Builder).
Release the business object type (in the BOR ObjectType -> Change release status to -> Implemented ).
Release the BAPI as a method in the BOR (Release the methods you has created - Set the cursor on the method then
Edit -> Change release status -> Object type component -> To released )
For potential write BAPIs: Release the IDoc and its segments


You can now display the BAPI in the BAPI Explorer:

Difference Between SAP BADI and User Exits

Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.

As with customer exits two different views are available:

In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.

In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.

In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.

SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.

The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).

All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.

The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.

What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?

I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.

What is the system landscape?

1) Difference between BADI and USER-EXIT.
i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
ii) BADI's are oops based.

2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
Ex:- 'Development server'-->'Quality server'---> 'Production server'......