topic bapi_commit in Application Development and Automation Discussions

bapi_commit

Former Member — Sat, 28 Jul 2007 10:27:01 GMT

hi all

1.i want the details about bapi_commit

2.how do we create bapi

Re: bapi_commit

Former Member — Sat, 28 Jul 2007 10:38:34 GMT

BAPI_COMMIT is used to commit the changes to the Database tables

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.

BAPI-step by step

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

list of all bapis

http://www.planetsap.com/LIST_ALL_BAPIs.htm

for BAPI's

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

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

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

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

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

http://service.sap.com/ale

http://service.sap.com/bapi

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://www.planetsap.com/Bapi_main_page.htm

http://www.topxml.com/sap/sap_idoc_xml.asp

http://www.sapdevelopment.co.uk/

http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf

Also refer to the following links..

www.sap-img.com/bapi.htm

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

www.planetsap.com/Bapi_main_page.htm

www.sapgenie.com/abap/bapi/index.htm

Checkout !!

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

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

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

exporting

clsid = g_c_clsid

typelib = g_c_typelib

importing

instid = g_f_oid

exceptions

communication_failure = 1 message g_f_msg

system_failure = 2 message g_f_msg

invalid_instance_id = 3

others = 4.

call function 'com_invoke' destination worker_dest

exporting

%instid = g_f_oid

%method = 'UpdatePDF'

sntemp = g_v_const_filent

snsysid = sy-sysid

snflag = 'N'

tables

rssaptable = g_t_pdfdetail1

%return = g_t_pdfdetail1 "t_test

exceptions

communication_failure = 1 message g_f_msg

system_failure = 2 message g_f_msg

invalid_instance_id = 3

others = 4.

then close the com session , using

FM delete_com_instance

FM END_COM_SESSION

see the sample code for BAPI

************SALES ORDER INPUT CREATION.

PARAMETERS: p_auart TYPE auart OBLIGATORY.

PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.

PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.

PARAMETERS: p_spart TYPE vtweg OBLIGATORY.

PARAMETERS: p_sold TYPE kunnr OBLIGATORY.

PARAMETERS: p_ship TYPE kunnr OBLIGATORY.

*ITEM

PARAMETERS: p_matnr TYPE matnr OBLIGATORY.

PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.

PARAMETERS: p_plant TYPE werks_d OBLIGATORY.

PARAMETERS: p_itcat TYPE pstyv OBLIGATORY.

DATA DECLARATIONS.

DATA: v_vbeln LIKE vbak-vbeln.

DATA: header LIKE bapisdhead1.

DATA: headerx LIKE bapisdhead1x.

DATA: item LIKE bapisditem OCCURS 0 WITH HEADER LINE.

DATA: itemx LIKE bapisditemx OCCURS 0 WITH HEADER LINE.

DATA: partner LIKE bapipartnr OCCURS 0 WITH HEADER LINE.

DATA: return LIKE bapiret2 OCCURS 0 WITH HEADER LINE.

DATA: lt_schedules_inx TYPE STANDARD TABLE OF bapischdlx

WITH HEADER LINE.

DATA: lt_schedules_in TYPE STANDARD TABLE OF bapischdl

WITH HEADER LINE.

HEADER DATA

header-doc_type = p_auart.

headerx-doc_type = 'X'.

header-sales_org = p_vkorg.

headerx-sales_org = 'X'.

header-distr_chan = p_vtweg.

headerx-distr_chan = 'X'.

header-division = p_spart.

headerx-division = 'X'.

headerx-updateflag = 'I'.

PARTNER DATA

partner-partn_role = 'AG'.

partner-partn_numb = p_sold.

APPEND partner.

partner-partn_role = 'WE'.

partner-partn_numb = p_ship.

APPEND partner.

ITEM DATA

itemx-updateflag = 'I'.

item-itm_number = '000010'.

itemx-itm_number = 'X'.

item-material = p_matnr.

itemx-material = 'X'.

item-plant = p_plant.

itemx-plant = 'X'.

item-target_qty = p_menge.

itemx-target_qty = 'X'.

item-target_qu = 'EA'.

itemx-target_qu = 'X'.

item-item_categ = p_itcat.

itemx-item_categ = 'X'.

APPEND item.

APPEND itemx.

Fill schedule lines

lt_schedules_in-itm_number = '000010'.

lt_schedules_in-sched_line = '0001'.

lt_schedules_in-req_qty = p_menge.

APPEND lt_schedules_in.

Fill schedule line flags

lt_schedules_inx-itm_number = '000010'.

lt_schedules_inx-sched_line = '0001'.

lt_schedules_inx-updateflag = 'X'.

lt_schedules_inx-req_qty = 'X'.

APPEND lt_schedules_inx.

Call the BAPI

CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'

EXPORTING

sales_header_in = header

sales_header_inx = headerx

IMPORTING

salesdocument_ex = v_vbeln

TABLES

return = return

sales_items_in = item

sales_items_inx = itemx

sales_schedules_in = lt_schedules_in

sales_schedules_inx = lt_schedules_inx

sales_partners = partner.

Check the return table.

LOOP AT return WHERE type = 'E' OR type = 'A'.

EXIT.

ENDLOOP.

IF sy-subrc = 0.

WRITE: / 'Error in creating document'.

ELSE.

COMMIT WORK AND WAIT.

WRITE: / 'Document ', v_vbeln, ' created'.

ENDIF.

<b>Reward points for useful Answers</b>

Regards

Anji

Re: bapi_commit

Former Member — Sat, 28 Jul 2007 10:46:20 GMT

realy good explanation

i need one more thing i.e. how to create dynamic internal tables?

Re: bapi_commit

Former Member — Sat, 28 Jul 2007 11:06:25 GMT

If you want to be able to commit or rollback database modifications as a unity they must be in the same logical unit of work. Two SAP transactions (CALL TRANSACTION aaa followed by CALL TRANSACTION bbb) have their own LUW because they are part of separate sessions. However, two BAPI's can be part of the same LUW, so one BAPI_COMMIT can refer to more than one CALL FUNCTION BAPI_...

example program

REPORT ZBAPI_SALESORDER_CREATE LINE-SIZE 132 MESSAGE-ID ZMMBAPI .

----

Internal table definition *

----

****<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>>>

DATA: GT_ORDER_HEADER_IN LIKE BAPISDHD1,

*******<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>

GT_ORDER_HEADER_INX LIKE BAPISDHD1X,

*****<<<<<Return Parameter>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

GT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE, " Return Messages

*********<<<Communication Fields: Sales and Distribution Document Item<>>>>>

GT_ORDER_ITEMS_IN LIKE BAPISDITM OCCURS 0 WITH HEADER LINE, " Item Data

*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>

GT_ORDER_ITEMS_INX LIKE BAPISDITMX OCCURS 0 WITH HEADER LINE, "Item Data Checkbox

*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>

GT_SALESDOCUMENT LIKE BAPIVBELN-VBELN , "Number of Generated Document

*********<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>

GT_ORDER_PARTNERS LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE, "Document Partner

********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>

GT_ORDER_SCHEDULES_IN LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE, "Schedule Line Data

****<<<<<<<<Checkbox List for Maintaining Sales Document Schedule Line>>>>>>>>

GT_ORDER_SCHEDULES_INX LIKE BAPISCHDLX OCCURS 0 WITH HEADER LINE, " Checkbox Schedule Line Data

*******Communication Fields for Maintaining Conditions in the Order

GT_ORDER_CONDITIONS_IN LIKE BAPICOND OCCURS 0 WITH HEADER LINE,

******Communication Fields for Maintaining Conditions in the Order

GT_ORDER_CONDITIONS_INX LIKE BAPICONDX OCCURS 0 WITH HEADER LINE.

----

Data definition *

----

DATA: BEGIN OF GT_FT_SALES OCCURS 0,

DOC_TYPE(4) , "Sales Document Type

SALES_ORG(4) , "Sales Organization

DISTR_CHAN(2) , "Distribution Channel

DIVISION(2) , "DIVISION(2)

SALES_DIST(6) , "Sales district

INCOTERMS1(3) , "Incoterms (part 1)

INCOTERMS2(28) , "Incoterms (part 2)

PMNTTRMS(4) , "Terms of payment key

PRICE_DATE(8) , "Date for pricing and exchange rate

PURCH_NO_C(35) , "Customer purchase order number

PURCH_NO_S(35) , "Ship-to Party's Purchase Order Number

EXCHG_RATE(8) , "Directly quoted exchange rate for pricing and statistics

CURRENCY(5) , "SD document currency

MATERIAL(18), "MATERIAL

TARGET_QTY(13) , "Target quantity in sales units

ITEM_CATEG(4) , "Sales document item category

MATL_GROUP(8) , "Material Group

PURCH_NO_C1(35), "Customer purchase order number

SALES_DIST1(6) , "Sales district

INCOTERMS11(3) , "Incoterms (part 1)

INCOTERMS21(28), "Incoterms (part 2)

PMNTTRMS1(4) , "Terms of payment key

EXCHG_RATE1(8) , "Directly quoted exchange rate for pricing and statistics

PRICE_DATE1(8) , "Date for pricing and exchange rate

TRG_QTY_NO(5) , "Factor for converting sales units to base units (target qty)

DIVISION1(2) , "DIVISION1

SALQTYNUM(5) , "Numerator (factor) for conversion of sales quantity into SKU

GROSS_WGHT(3) , "Gross Weight of the Item

NET_WEIGHT(15) , "Net Weight of the Item

UNTOF_WGHT(3) ,"Weight Unit

PARTN_ROLE(2) ,"Partner function

PARTN_NUMB(10) ,"Customer Number 1

********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>

ITM_NUMBER(6) ,"Item number of the SD document

REQ_QTY(8) , "Schedule line date

DLV_DATE(8) , "Schedule line date

MS_DATE(8) , "Material availability date

LOAD_DATE(8) , "Loading time (local time with reference to a shipping point)

GI_DATE(8), "Time of goods issue (local DATE, with reference to a plant)

TP_DATE(8) , "Transportation planning -time (local w/ref. to shipping pnt)

ITM_NUMBER2(6) , "Condition item number

END OF GT_FT_SALES,

MSG(240) TYPE C, " Return Message

E_REC(8) TYPE C, " Error Records Counter

REC_NO(8) TYPE C, " Records Number Indicator

S_REC(8) TYPE C, " Successful Records Counter

T_REC(8) TYPE C. " Total Records Counter

selection block for EXCEL UPLOAD FILE>>>>>>>>>>>>>>>>>>>>>>>>

SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.

PARAMETERS FILE TYPE IBIPPARMS-PATH OBLIGATORY.

SELECTION-SCREEN END OF BLOCK B1.

*<<<<AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .>>>>>>>>>>>>

AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .

CALL FUNCTION 'F4_FILENAME'

EXPORTING

PROGRAM_NAME = SYST-CPROG

DYNPRO_NUMBER = SYST-DYNNR

IMPORTING

FILE_NAME = FILE.

**<<<<<<<<<<<<<<<<<START-OF-SELECTION.>>>>>>>>>>>>>>>>>>>>>>>>>>>

START-OF-SELECTION.

CALL FUNCTION 'WS_UPLOAD' "#EC *

EXPORTING

FILENAME = FILE

FILETYPE = 'DAT'

TABLES

DATA_TAB = GT_FT_SALES

EXCEPTIONS

CONVERSION_ERROR = 1

FILE_OPEN_ERROR = 2

FILE_READ_ERROR = 3

INVALID_TYPE = 4

NO_BATCH = 5

UNKNOWN_ERROR = 6

INVALID_TABLE_WIDTH = 7

GUI_REFUSE_FILETRANSFER = 8

CUSTOMER_ERROR = 9

NO_AUTHORITY = 10

OTHERS = 11.

IF SY-SUBRC <> 0 .

MESSAGE E000.

ENDIF.

SKIP 3.

FORMAT COLOR COL_HEADING INVERSE ON.

WRITE 40 TEXT-001.

FORMAT COLOR COL_HEADING INVERSE OFF.

SKIP 1.

FORMAT COLOR COL_NEGATIVE INVERSE ON.

WRITE 😕 TEXT-002, 13 SY-MANDT , 104 TEXT-003, 111 SY-UNAME,

/ TEXT-004, 13 SY-DATUM , 104 TEXT-005, 111 SY-UZEIT.

FORMAT COLOR COL_NEGATIVE INVERSE OFF.

SKIP 3.

LOOP AT GT_FT_SALES.

PERFORM SLALE_UPLOAD_DATA.

ENDLOOP.

T_REC = E_REC + S_REC.

SKIP 3.

FORMAT COLOR COL_TOTAL INVERSE ON.

WRITE: /38 TEXT-007, T_REC.

FORMAT COLOR COL_TOTAL INVERSE OFF.

FORMAT COLOR COL_NEGATIVE INVERSE ON.

WRITE: /38 TEXT-008, E_REC.

FORMAT COLOR COL_NEGATIVE INVERSE OFF.

FORMAT COLOR COL_TOTAL INVERSE ON.

WRITE: /38 TEXT-009, S_REC.

FORMAT COLOR COL_TOTAL INVERSE OFF.

&----

*& Form SLALE_UPLOAD_DATA

&----

text

----

--> p1 text
<-- p2 text

----

FORM SLALE_UPLOAD_DATA .

*******<<<<<<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>

GT_ORDER_HEADER_IN-DOC_TYPE = 'TA'.

GT_ORDER_HEADER_IN-SALES_ORG = GT_FT_SALES-SALES_ORG . "'0001'

GT_ORDER_HEADER_IN-DISTR_CHAN = GT_FT_SALES-DISTR_CHAN. "'01'

GT_ORDER_HEADER_IN-DIVISION = GT_FT_SALES-DIVISION. " '01'

GT_ORDER_HEADER_IN-SALES_DIST = GT_FT_SALES-SALES_DIST ."'000001'

GT_ORDER_HEADER_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1. "'CFR'

GT_ORDER_HEADER_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'

GT_ORDER_HEADER_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS . "'0001'

GT_ORDER_HEADER_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE ."'20060818'

GT_ORDER_HEADER_IN-PURCH_NO_C = '32'.

GT_ORDER_HEADER_IN-PURCH_NO_S = '32'.

GT_ORDER_HEADER_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE ."'1.00000'

GT_ORDER_HEADER_IN-CURRENCY = GT_FT_SALES-CURRENCY . " 'EUR'

********<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>

GT_ORDER_HEADER_INX-DOC_TYPE = 'X'.

GT_ORDER_HEADER_INX-SALES_ORG = 'X'.

GT_ORDER_HEADER_INX-DISTR_CHAN = 'X'.

GT_ORDER_HEADER_INX-DIVISION = 'X'.

GT_ORDER_HEADER_INX-SALES_DIST = 'X'.

GT_ORDER_HEADER_INX-INCOTERMS1 = 'X'.

GT_ORDER_HEADER_INX-INCOTERMS2 = 'X'.

GT_ORDER_HEADER_INX-PMNTTRMS = 'X'.

GT_ORDER_HEADER_INX-PRICE_DATE = 'X'.

GT_ORDER_HEADER_INX-PURCH_NO_C = 'X'.

GT_ORDER_HEADER_INX-PURCH_NO_S = 'X'.

GT_ORDER_HEADER_INX-EXCHG_RATE = 'X'.

GT_ORDER_HEADER_INX-CURRENCY = 'X'.

*****<<<<<<Communication Fields: Sales and Distribution Document Item>>>

GT_ORDER_ITEMS_IN-ITM_NUMBER = '000010'.

GT_ORDER_ITEMS_IN-MATERIAL = GT_FT_SALES-MATERIAL .

GT_ORDER_ITEMS_IN-PO_ITM_NO = '32'.

GT_ORDER_ITEMS_IN-CUST_MAT22 = 'AGNI-IV'.

GT_ORDER_ITEMS_IN-BILL_DATE = '20060808'.

GT_ORDER_ITEMS_IN-PLANT = '0001'.

*GT_ORDER_ITEMS_IN-STORE_LOC = '0001'.

GT_ORDER_ITEMS_IN-TARGET_QTY = GT_FT_SALES-TARGET_QTY . "'1000'

GT_ORDER_ITEMS_IN-ITEM_CATEG = GT_FT_SALES-ITEM_CATEG . "'TAN'

GT_ORDER_ITEMS_IN-MATL_GROUP = GT_FT_SALES-MATL_GROUP . "'01'

GT_ORDER_ITEMS_IN-PURCH_NO_C = GT_FT_SALES-PURCH_NO_C . "'32'

GT_ORDER_ITEMS_IN-SALES_DIST = GT_FT_SALES-SALES_DIST . "'000001'

GT_ORDER_ITEMS_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1 . "'CFR'

GT_ORDER_ITEMS_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'

GT_ORDER_ITEMS_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS . "'0001'.

GT_ORDER_ITEMS_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE . "'1.00000'

GT_ORDER_ITEMS_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE . "'20060808'

*GT_ORDER_ITEMS_IN-SALES_UNIT = 'DZ'.

GT_ORDER_ITEMS_IN-TRG_QTY_NO = GT_FT_SALES-TRG_QTY_NO . "'23'

GT_ORDER_ITEMS_IN-DIVISION = GT_FT_SALES-DIVISION . "'01'

GT_ORDER_ITEMS_IN-SALQTYNUM = GT_FT_SALES-SALQTYNUM . "'32'

GT_ORDER_ITEMS_IN-GROSS_WGHT = GT_FT_SALES-GROSS_WGHT. " ' 25272000'

GT_ORDER_ITEMS_IN-NET_WEIGHT = GT_FT_SALES-NET_WEIGHT. "'24464000'

GT_ORDER_ITEMS_IN-UNTOF_WGHT = GT_FT_SALES-UNTOF_WGHT . " 'KG'

*GT_ORDER_ITEMS_IN-CURRENCY = 'EUR'.

APPEND GT_ORDER_ITEMS_IN.

****<<<<<<Communication Fields: Sales and Distribution Document Item>>>

GT_ORDER_ITEMS_INX-ITM_NUMBER = '000010'.

GT_ORDER_ITEMS_INX-MATERIAL = 'X'.

*GT_ORDER_ITEMS_INX-PO_ITM_NO = 'X'.

GT_ORDER_ITEMS_INX-CUST_MAT22 = 'X'.

GT_ORDER_ITEMS_INX-BILL_DATE = 'X'.

GT_ORDER_ITEMS_INX-PLANT = 'X'.

*GT_ORDER_ITEMS_INX-STORE_LOC = 'X'.

GT_ORDER_ITEMS_INX-TARGET_QTY = 'X'.

GT_ORDER_ITEMS_INX-ITEM_CATEG = 'X'.

GT_ORDER_ITEMS_INX-MATL_GROUP = 'X'.

GT_ORDER_ITEMS_INX-PURCH_NO_C = 'X'.

GT_ORDER_ITEMS_INX-SALES_DIST = 'X'.

GT_ORDER_ITEMS_INX-INCOTERMS1 = 'X'.

GT_ORDER_ITEMS_INX-INCOTERMS2 = 'X'.

GT_ORDER_ITEMS_INX-PMNTTRMS = 'X'.

GT_ORDER_ITEMS_INX-EXCHG_RATE = 'X'.

GT_ORDER_ITEMS_INX-PRICE_DATE = 'X'.

*GT_ORDER_ITEMS_INX-SALES_UNIT = 'X'.

GT_ORDER_ITEMS_INX-TRG_QTY_NO = 'X'.

GT_ORDER_ITEMS_INX-DIVISION = 'X'.

GT_ORDER_ITEMS_INX-SALQTYNUM = 'X'.

GT_ORDER_ITEMS_INX-GROSS_WGHT = 'X'.

GT_ORDER_ITEMS_INX-NET_WEIGHT = 'X'.

GT_ORDER_ITEMS_INX-UNTOF_WGHT = 'X'.

*GT_ORDER_ITEMS_IN-CURRENCY = 'x'.

APPEND GT_ORDER_ITEMS_INX.

*****<<<<<<Communications Fields: SD Document Partner: WWW

GT_ORDER_PARTNERS-PARTN_ROLE = 'WE'.

GT_ORDER_PARTNERS-PARTN_NUMB = '0000000057'.

***GT_ORDER_PARTNERS-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER . " '000010'.

APPEND GT_ORDER_PARTNERS.

*********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>

GT_ORDER_SCHEDULES_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER." '000010'

GT_ORDER_SCHEDULES_IN-REQ_QTY = GT_FT_SALES-REQ_QTY . "'234'

GT_ORDER_SCHEDULES_IN-DLV_DATE = GT_FT_SALES-DLV_DATE ." '20060824'.

GT_ORDER_SCHEDULES_IN-MS_DATE = GT_FT_SALES-MS_DATE . "'20060808'

GT_ORDER_SCHEDULES_IN-LOAD_DATE = GT_FT_SALES-LOAD_DATE. " '20060822'

GT_ORDER_SCHEDULES_IN-GI_DATE = GT_FT_SALES-GI_DATE . " '20060823'

GT_ORDER_SCHEDULES_IN-TP_DATE = GT_FT_SALES-TP_DATE . "'20060821'

APPEND gt_ORDER_SCHEDULES_IN.

*********<<<<Communications Fields: SD Document Partner: WWW FLAG>>>>>>>>>>>>>>>>>>

GT_ORDER_SCHEDULES_INX-ITM_NUMBER = '000010'.

GT_ORDER_SCHEDULES_INX-REQ_QTY = 'X'.

GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.

GT_ORDER_SCHEDULES_INX-MS_DATE = 'X'.

GT_ORDER_SCHEDULES_INX-LOAD_DATE = 'X'.

GT_ORDER_SCHEDULES_INX-GI_DATE = 'X'.

GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.

APPEND gt_ORDER_SCHEDULES_INX.

********Communication Fields for Maintaining Conditions in the Order

GT_ORDER_CONDITIONS_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER ." '000010'

APPEND GT_ORDER_CONDITIONS_IN.

***Communication Fields for Maintaining Conditions in the Order

GT_ORDER_CONDITIONS_INX-ITM_NUMBER = '000010'.

APPEND GT_ORDER_CONDITIONS_INX.

CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'

EXPORTING

SALESDOCUMENTIN =

ORDER_HEADER_IN = GT_ORDER_HEADER_IN

ORDER_HEADER_INX = GT_ORDER_HEADER_INX

SENDER =
BINARY_RELATIONSHIPTYPE =
INT_NUMBER_ASSIGNMENT =
BEHAVE_WHEN_ERROR =
LOGIC_SWITCH =
TESTRUN =
CONVERT = ' '

IMPORTING

SALESDOCUMENT = GT_SALESDOCUMENT

TABLES

RETURN = GT_RETURN

ORDER_ITEMS_IN = GT_ORDER_ITEMS_IN

ORDER_ITEMS_INX = GT_ORDER_ITEMS_INX

ORDER_PARTNERS = GT_ORDER_PARTNERS

ORDER_SCHEDULES_IN = GT_ORDER_SCHEDULES_IN

ORDER_SCHEDULES_INX = GT_ORDER_SCHEDULES_INX

ORDER_CONDITIONS_IN = GT_ORDER_CONDITIONS_IN

ORDER_CONDITIONS_INX = GT_ORDER_CONDITIONS_INX

ORDER_CFGS_REF =
ORDER_CFGS_INST =
ORDER_CFGS_PART_OF =
ORDER_CFGS_VALUE =
ORDER_CFGS_BLOB =
ORDER_CFGS_VK =
ORDER_CFGS_REFINST =
ORDER_CCARD =
ORDER_TEXT =
ORDER_KEYS =
EXTENSIONIN =
PARTNERADDRESSES =

IF GT_RETURN-TYPE EQ 'E' .

E_REC = E_REC + 1.

READ TABLE GT_RETURN WITH KEY ID = 'V1'.

FORMAT COLOR COL_NEGATIVE INVERSE ON.

REC_NO = E_REC + S_REC.

CONCATENATE TEXT-006 REC_NO ':'

GT_RETURN-MESSAGE INTO MSG SEPARATED BY SPACE .

CONDENSE MSG.

WRITE: / MSG.

FORMAT COLOR COL_NEGATIVE INVERSE OFF.

ELSEIF GT_RETURN-TYPE EQ 'S'.

S_REC = S_REC + 1.

FORMAT COLOR COL_POSITIVE INVERSE ON.

MSG = GT_RETURN-MESSAGE.

CONDENSE MSG.

WRITE: / MSG .

FORMAT COLOR COL_POSITIVE INVERSE OFF.

PERFORM COMMIT_MM.

ENDIF.

CLEAR: GT_RETURN[], MSG.

ENDFORM. " SLALE_UPLOAD_DATA

&----

*& Form COMMIT_MM

&----

text

----

--> p1 text
<-- p2 text

----

FORM COMMIT_MM .

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

WAIT = 'X'

IMPORTING

RETURN = GT_RETURN.

clear: GT_ORDER_ITEMS_IN[],GT_ORDER_CONDITIONS_IN[].

ENDFORM. " COMMIT_MM