Re: BAPI

Former Member · ‎2008 May 24

any body can help me to know what is bapi,how it works...?

Former Member · ‎2008 May 24

hi check this..

reagrds,

venkat

Former Member · ‎2008 May 24

BAPI (Business Application Programming Interface) is an API method of a business object which intern is a RFC enabled Function Module.

Business Objects are the Objects which has business sence associated to it. Ex. Sales Orders, Purchase Orders etc.

The Properties of BAPI are:

Every BAPI name should start with letters 'BAPI'.

It is an API method of a Business Object.

it does not contain a internal COMMIT statement in the Function Module.

It does not contain "CALL TRANSACTION" statements.

BAPI do not raise 'EXCEPTIONS'.

a RETURN structure is defined as an interface parameter of a BAPI which is used to log all the errors, warnings and the successful processes tha are triggered in the course of execution of a BAPI.

A successful execution of a BAPI requires the data to be commited and this process of performing a COMMIT is achieved by calling the BAPI_TRANSACTION_COMMIT' explicitly if there are no errors logged in the RETURN structure.

There are two types of BAPI's: Instance Dependent & Instance Independent.

BAPI provides an access to the SAP system for external applications to have the business data processed in the form of web services. When BAPI's are used to post the data in SAP system these are used as Function Modules.

for further information check following:

Go to the below link for BAPI.

http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm

BAPI

http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/5e114a4a1611d1894c0000e829fbbd/frameset.htm

http://www.sapgenie.com/abap/bapi/example.htm

http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm

http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html

http://techrepublic.com.com/5100-6329-1051160.html#

http://www.sap-img.com/bapi.htm

http://www.sap-img.com/abap/bapi-conventions.htm

http://www.sappoint.com/abap/bapiintro.pdf

http://www.sapgenie.com/abap/bapi/example.htm

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf

Programming a BAPI consists of two major tasks:

1. Defining BAPI Data structures in SE11

2. Program a RFC enabled BAPI function module for each method

3. Create a Business object for the BAPI in the BOR

4. Documentation the BAPI

5. Generate ALE interface for aynchronous BAPIs

6. Generate and release

Tip: You can use the BAPi explorer to get a step by step

instuction/checklist in how to create a BAPI. In the BAPI explorer

select the Project tab.

Methods

If the BAPI to be implemented is a standardized BAPI, use the generic names, for example, GetList, GetDetail.

The method name must be in English (maximum 30 characters).

The individual components of a BAPI name are separated by the use of upper and lower case.Example: GetList

Underscores ("_") are not allowed in BAPI names.

Each BAPI has a return parameter that is 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 as meaningful as possible. Poorly chosen names include abbreviations and technical names (e.g. "flag", table

names, etc.).

The parameter and field names must be in English with a maximum of 30 characters.

The components of a parameter name in the BOR are separated by upper and lower case letters to make them easier to read. Example:

CompanyCodeDetail

Values that belong to each other semantically should be grouped together in one structured parameter, instead of using several scalar

parameters.

For ISO-relevant fields (country, language, unit of measure, currency), additional fields for ISO codes are provided.

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.

The following standardized BAPIs are provided:

Reading instances of SAP business objects

GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.

The BAPI GetList() is a class method.

GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The

instance is identified via its key. The BAPI GetDetail() is an instance method.

BAPIs that can create, change or delete instances of a business object type

The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example,

if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the

consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.

Create( ) and

CreateFromData( ) The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order.

These BAPIs are class methods.

Change( ) The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is

an instance method.

Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.

The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.

Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the

database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.

Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object instance and the BAPI and

Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.

BAPIs for Mass Data Processing

The BAPIs listed above for creating and changing data can also be used for mass processing. For more information see BAPIs for Mass Data

Transfer Extern

BAPIs for Replicating Business Object Instances

Replicate( ) and SaveReplica( ) The BAPIs Replicate() and SaveReplica() are implemented as methods of replicable business object types. They

enable specific instances of an object type to be copied to one or more different systems. These BAPIs are used mainly to transfer data between

distributed systems within the context of Application Link Enabling (ALE). These BAPIs are class methods.

Other Less Used Standardized BAPIs

Programming GetStatus() BAPIs Extern

Programming ExistenceCheck() BAPIs Extern

Standardized Parameters

There are some parameters that can be created for various BAPIs because they contain the same or the equivalent data in all BAPIs. They should

be implemented the same in all BAPIs.

Address parameters Specific reference structures are defined for address parameters in BAPIs. You should copy these structures to use in your

BAPI, especially if the underlying object type uses the central address management (CAM).

Change Parameters In BAPIs that cause database changes (for example, Change() and Create() BAPIs) you must be able to distinguish between

parameter fields that contain modified values and parameter fields that have not been modified. This distinction is made through the use of

standardized parameters.

Extension parameters The parameters ExtensionIn and ExtensionOut provides customers with a mechanism that enables BAPIs to be enhanced

without modifications.

Return Parameters Each BAPI must have an export return parameter for returning messages to the calling application. To provide application

programmers with a consistent error handling process for BAPI calls, all return parameters must be implemented in the same, standardized way.

Selection Parameters Standardized selection parameters are used in BAPIs that can be used to search for specific instances of a business object

type (e.g. in GetList() ). These parameters enable the BAPI caller to specify the relevant selection criteria.

Test Run Parameters The parameter TestRun is used in write BAPIs (Create() and Change() ), to check the entries for the object instance in the

database before actually creating the object instance. The creation of the object instance is only simulated and data is not updated.

Text Transfer Parameters To transfer BAPI documentation texts (e.g. the documentation of a business object type), you have to create

standardized text transfer parameters.

Important things to remember..

It is important to follow the guidelines below when develop9ng BAPIs:

BAPIs must not contain CALL TRANSACTIO or SUBMIT REPORT

BAPIs must not invoke a COMMIT WORK. instead use the BAPI TransactionCommit to execute the commit after the BAPI has executed.

BAPI structures must not use includes.

There should be no functional dependecies between two BAPIs

BAPIs must perform there own authorization check

BAPIs should not use dialogs

BAPIs must not cause the program to abort or terminate. re4levant messages must be communicated through the return parameter.

BAPI/ALE Integration

When you use the BAPIs for asynchronous messagning, the application in the sendig systen calls the generated ALE IDoc interface isntead 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 trhe target system, crreates the BAPI data from the IDoc and calls the BAPI

An ALE interface for a BAPi is created in transaction BDBG

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

STEP 1 - Define a structures for the BAPI

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

STEP 2 - Write Function Module

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.

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.

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.

STEP 3 - Create the API Method Using the BAPI WIZARD

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:

*

o

+

#

Implementation of object type ZORDERSTAT *****

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 ZGETORDERSTATUS CHANGING CONTAINER.

DATA:

BAPIORDERSTATUSIMPORT LIKE ZBAPI_ORDER_STATUS_IMPORT,

RETURN LIKE BAPIRETURN,

TBAPISTAT LIKE ZBAPISTAT OCCURS 0.

SWC_GET_ELEMENT CONTAINER 'BapiOrderStatusImport'

BAPIORDERSTATUSIMPORT.

SWC_GET_TABLE CONTAINER 'TBapistat' TBAPISTAT.

CALL FUNCTION 'Z_BAPI_GET_ORDER_STATUS'

EXPORTING

BAPI_ORDER_STATUS_IMPORT = BAPIORDERSTATUSIMPORT

IMPORTING

RETURN = RETURN

TABLES

T_BAPISTAT = TBAPISTAT

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 'TBapistat' TBAPISTAT.

END_METHOD.

STEP 4 - Final steps

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:

Rewards if useful.

Former Member · ‎2008 May 24

Hi ,

BAPI stands for Business API(Application Program Interface).

A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..

You can make your function module remotely enabled in attributes of Function module but

A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).

BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call 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.

The following standardized BAPIs are provided:

Reading instances of SAP business objects

GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.

The BAPI GetList() is a class method.

GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type

The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.

Create( ) and CreateFromData! ( )

The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.

Change( )

The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.

Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.

The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.

Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.

Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.

Example Code

U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.

U can find these parameters for a particular condition type in table KONV.

&----

*& Form saveTransactionJOCR

&----

text

-

--> p1 text

<-- p2 text

-

FORM saveTransactionJOCR .

data: salesdocument like BAPIVBELN-VBELN,

order_header_inx like bapisdh1x,

order_header_in like bapisdh1,

return type standard table of bapiret2 with header line,

conditions_in type standard table of bapicond with header line,

conditions_inx type standard table of bapicondx with header line,

logic_switch like BAPISDLS,

step_nr like conditions_in-cond_st_no,

item_nr like conditions_in-itm_number,

cond_count like conditions_in-cond_count,

cond_type like conditions_in-cond_type.

salesdocument = wa_order_information-VBELN.

LOGIC_SWITCH-COND_HANDL = 'X'.

order_header_inx-updateflag = 'U'.

conditions

clear conditions_in[].

clear conditions_inx[].

clear: step_nr,

item_nr,

cond_count,

cond_type.

step_nr = '710'.

item_nr = '000000'.

cond_count = '01'.

cond_type = 'ZCP2'.

CONDITIONS_IN-ITM_NUMBER = item_nr.

conditions_in-cond_st_no = step_nr.

CONDITIONS_IN-COND_COUNT = cond_count.

CONDITIONS_IN-COND_TYPE = cond_type.

CONDITIONS_IN-COND_VALUE = 666.

CONDITIONS_IN-CURRENCY = 'EUR'.

append conditions_in.

CONDITIONS_INX-ITM_NUMBER = item_nr.

conditions_inx-cond_st_no = step_nr.

CONDITIONS_INX-COND_COUNT = cond_count.

CONDITIONS_INX-COND_TYPE = cond_type.

CONDITIONS_INX-UPDATEFLAG = 'U'.

CONDITIONS_INX-COND_VALUE = 'X'.

CONDITIONS_INX-CURRENCY = 'X'.

append conditions_inx.

CALL FUNCTION 'BAPI_SALESORDER_CHANGE'

EXPORTING

SALESDOCUMENT = salesdocument

ORDER_HEADER_IN = order_header_in

ORDER_HEADER_INX = order_header_inx

LOGIC_SWITCH = logic_switch

TABLES

RETURN = return

CONDITIONS_IN = conditions_in

CONDITIONS_INX = conditions_inx

.

if return-type ne 'E'.

commit work and wait.

endif.

ENDFORM. " saveTransactionJOCR

Bdc to Bapi

The steps to be followed are :

1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).

for VA01 use BAPI_SALESORDER_CREATEFROMDAT2

2. Create a Z program and call the BAPi (same as a Funtion module call).

2. Now, if you see this BAPi, it has

-> Importing structures.

eg: SALESDOCUMENT: this will take the Sales order header data as input.

-> Tables parameters:

eg: ORDER_ITEM_IN: this will take the line item data as input.

Note :

Only specify fields that should be changed

Select these fields by entering an X in the checkboxes

Enter a U in the UPDATEFLAG field

Always specify key fields when changing the data, including in the checkboxes

The configuration is an exception here. If this needs to be changed, you need to complete it again fully.

Maintain quantities and dates in the schedule line data

Possible UPDATEFLAGS:

U = change

D = delete

I = add

Example

1. Delete the whole order

2. Delete order items

3. Change the order

4. Change the configuration

Notes

1. Minimum entry:

You must enter the order number in the SALESDOCUMENT structure.

You must always enter key fields for changes.

You must always specify the update indicator in the ORDER_HEADER_INX.

2. Commit control:

The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.

For further details... refer to the Function Module documentation for the BAPi.

Bapi to VB(Visual Basic)

Long back I had used the following flow structure to acheive the same.

Report -> SM59 RFC destination -> COM4ABAP -> VB.exe

my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.

You need to have com4abap.exe

If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.

else refer OSS note 419822 for installation of com4abap

after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.

for setting up com4abap and rfc destination please refer to the documentation for com4abap.

Invoke NEW DCOM session

call function 'BEGIN_COM_SESSION'

exporting

service_dest = service_dest "(this will be a RFC destination created in SM59)

importing

worker_dest = worker_dest

exceptions

connect_to_dcom_service_failed = 1

connect_to_dcom_worker_failed = 2

others = 3.

call function 'create_com_instance' destination worker_dest