Error saving purchase order data decimal values in SAP R/3

sir,
PO was created with currency japanese YEN using Tcode ME21N . The net price was showing 142502300 (in JPY).
when checked in EKPO table , it saved with a value 1425023.00 instead of 142502300 .
what can be done to correct this.
In PO Print out , it showing values as 1425023.00 which is wrong.
SPRO>> NET WEAVER >> GENERAL SETTINGS >> CURRENCY>> SET DECIMAL values FOR CURRENCY CODES is showing 0 decimals against JPY (Japanese YEN)
I want to know where else the Decimal values could have been set to 2 decimal places.
FOr other currencies like US Dollars there is no error.
Regards,
Srinivasa Murthy

Hello Srinivasa
Please check the forum Rules of Engagement - https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement.
Cross posting is not permitted. This issue is already raised in the application area forum which is probably correct. This does not look like a PI technical issue.
Regards
Mark Smyth
XI/PI Moderator

Similar Messages

Error saving purchase order data decimal values

sir,
PO was created with currency japanese YEN using Tcode ME21N . The net price was showing 142502300 (in JPY).
when checked in EKPO table , it saved with a value 1425023.00 instead of 142502300 .
what can be done to correct this.
In PO Print out , it showing values as 1425023.00 which is wrong.
SPRO>> NET WEAVER >> GENERAL SETTINGS >> CURRENCY>> SET DECIMAL values FOR CURRENCY CODES is showing 0 decimals against JPY (Japanese YEN)
I want to know where else the Decimal values could have been set to 2 decimal places.
FOr other currencies like US Dollars there is no error.
Regards,
Srinivasa Murthy

Hi Srinivasa,
Use T. code OY01 and you can try 3rd option of decimal format that is 1234567, 89 for the same.
Regards,
Shailesh Verma

Purchase order with decimal values in held status.

Hello, i have a SC. The quantity is decimal for the line item.When it was approved, the PO got a 'held' status.How do i release the PO and what can i do in order to accept decimal values in my SC ?

Hello,
Are you sure this is not a workflow issue? If it is held, someone either placed it in hold status or something like that. Since, there was nothing to suspect an application error, I don't think the decimals is your issue. If you feel that it is, have you checked OSS.
More information would be helpful....
Regards, Dean.

Error while saving purchase order

Hi all,
While saving purchase order i am getting the following error.
Syntax error in program SAPLV61A
in include RV64A932
in line 10
Statement"*&"is not defined.check your spelling.
Thanks& Regards,
Hari.

Hi Hari,
I've just encountered the same problem as you have now in your latest post.
Normally the include that you mentioned is a formula condition value include which you can modify but you probably have
to register this object first on the SAP OSS pages to get an Access key to modify it.
After you've obtained a key launch transaction VOFM and comment out the line "TABLES: VBRK, VBAK".
As you see below SAP did exactly the same thing in several other includes.
Include FV64A582
-> is a formula condition value
    tx VOFM
            -> Formulas
     -> Condition Value
     -> Routine number 582
At line 37 I commented out "TABLES: VBRK, VBAK." which is not used
anyway in this include.
On top of that SAP commented out these definitions in several other
includes: eg. FOICH002, FOICH002, OI_LV61ATOI.
If other persons have comments on this topic please respond/advise.
Hari, inform us if this resolved your problem.
Also reward points if my post aided you in resolving your issue.
Thank you for feedback.
Best regards,
Tom Cockaert.

Error in : Purchase order Creation using BAPI_PO_CREATE1

Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
 i_create_order,
 i_cycle TYPE cycle,
 i_qty_acpt TYPE dzmeng,
 i_dly_date TYPE vbak-vdatu,
 i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
 i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
 i_vbap TYPE vbap,
 i_ekko TYPE ekko,
 i_ekpo TYPE ekpo,
 i_bsoh TYPE bapisdhd1,
 i_bsohx TYPE bapisdhd1x,
 i_bpoh TYPE bapimepoheader,
 i_bpohx TYPE bapimepoheaderx,
 i_vbeln TYPE vbeln_va,
 i_posnr TYPE posnr_va,
 i_contr TYPE vbeln_va,
 i_conit TYPE posnr_va,
 i_ebeln TYPE ebeln,
 i_ebelp TYPE ebelp,
 i_pargr TYPE pargr,
 i_thead TYPE thead,
 i_line TYPE tline,
 i_note TYPE txw_note,
 i_new_vbeln TYPE vbeln_va,
 i_new_ebeln TYPE ebeln,
 i_wa_bsoi TYPE bapisditm,
 i_wa_bsoix TYPE bapisditmx,
 i_wa_bsop TYPE bapiparnr,
 i_wa_bsos TYPE bapischdl,
 i_wa_bsosx TYPE bapischdlx,
 i_wa_vbpa TYPE vbpa,
 i_wa_vbkd TYPE vbkd,
 i_wa_bpoi TYPE bapimepoitem,
 i_wa_bpoix TYPE bapimepoitemx,
 i_wa_bpos TYPE bapimeposchedule,
 i_wa_bposx TYPE bapimeposchedulx,
 i_wa_bpop TYPE bapiekkop,
 i_wa_ekpa TYPE ekpa,
 i_message TYPE char72,
 i_bapiretn TYPE bapiret2,
 i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
 i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
 i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
 i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
 i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
 i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
 i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
 i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
 i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
 i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
 i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
 i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
 i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
 i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
 i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
 i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
 c_char_e VALUE 'E',
 c_char_p VALUE 'P',
 c_char_g VALUE 'G',
 c_char_i VALUE 'I',
 c_char_s VALUE 'S',
 c_char_x VALUE 'X',
 c_zsw(3) VALUE 'ZSW',
 c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
 IF NOT i_create_order IS INITIAL .
 CLEAR: i_create_order .
 MOVE: wa_order_split_create-docnr TO i_ebeln,
 wa_order_split_create-docitm TO i_ebelp .
 CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 IMPORTING
 po_ekko = i_ekko
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
 ENDIF .
* Fill PO Header
 i_bpoh-comp_code = i_ekko-bukrs .
 i_bpoh-doc_type = i_ekko-bsart .
 i_bpoh-vendor = i_ekko-lifnr .
 i_bpoh-langu = i_ekko-spras .
 i_bpoh-pmnttrms = i_ekko-zterm .
 i_bpoh-purch_org = i_ekko-ekorg .
 i_bpoh-pur_group = i_ekko-ekgrp .
 i_bpoh-currency = i_ekko-waers .
 i_bpoh-agreement = i_ekko-konnr .
 i_bpoh-incoterms1 = i_ekko-inco1 .
 i_bpoh-incoterms2 = i_ekko-inco2 .
* Fill PO update indicator 'X'
 i_bpohx-comp_code = c_char_x .
 i_bpohx-doc_type = c_char_x .
 i_bpohx-vendor = c_char_x .
 i_bpohx-langu = c_char_x .
 i_bpohx-pmnttrms = c_char_x .
 i_bpohx-purch_org = c_char_x .
 i_bpohx-pur_group = c_char_x .
 i_bpohx-currency = c_char_x .
 i_bpohx-agreement = c_char_x .
 i_bpohx-incoterms1 = c_char_x .
 i_bpohx-incoterms2 = c_char_x .
 CALL FUNCTION 'ME_EKPO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 pi_ebelp = i_ebelp
 IMPORTING
 po_ekpo = i_ekpo
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF .
* Fill PO Item
 i_wa_bpoi-po_item = i_ekpo-ebelp .
 i_wa_bpoi-material = i_ekpo-matnr .
 i_wa_bpoi-plant = i_ekpo-werks .
 i_wa_bpoi-stge_loc = i_ekpo-lgort .
 i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
 i_wa_bpoi-po_unit = i_ekpo-meins .
 i_wa_bpoi-tax_code = i_ekpo-mwskz .
 i_wa_bpoi-val_type = i_ekpo-bwtar .
 i_wa_bpoi-item_cat = i_ekpo-pstyp .
 i_wa_bpoi-acctasscat = i_ekpo-knttp .
 i_wa_bpoi-agreement = i_ekpo-konnr .
 i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
 APPEND i_wa_bpoi TO i_bpoi .
* Fill PO Item update indicator 'X'
 i_wa_bpoix-po_item = i_ekpo-ebelp .
 i_wa_bpoix-po_itemx = c_char_x .
 i_wa_bpoix-material = c_char_x .
 i_wa_bpoix-plant = c_char_x .
 i_wa_bpoix-stge_loc = c_char_x .
 i_wa_bpoix-quantity = c_char_x .
 i_wa_bpoix-po_unit = c_char_x .
 i_wa_bpoix-tax_code = c_char_x .
 i_wa_bpoix-val_type = c_char_x .
 i_wa_bpoix-item_cat = c_char_x .
 i_wa_bpoix-acctasscat = c_char_x .
 i_wa_bpoix-agreement = c_char_x .
 i_wa_bpoix-agmt_item = c_char_x .
 APPEND i_wa_bpoix TO i_bpoix .
* Fill PO Item Schedule
 i_wa_bpos-po_item = i_ekpo-ebelp .
 i_wa_bpos-sched_line = '0001' .
 i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
 i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
 APPEND i_wa_bpos TO i_bpos .
* Fill PO Item schedule update indicator 'X'
 i_wa_bposx-po_item = i_ekpo-ebelp .
 i_wa_bposx-sched_line = '0001' .
 i_wa_bposx-delivery_date = c_char_x .
 i_wa_bposx-quantity = c_char_x .
 APPEND i_wa_bposx TO i_bposx .
 CLEAR: i_pargr .
 SELECT SINGLE pargr
 INTO i_pargr
 FROM t161
 WHERE bstyp = i_ekko-bstyp
 AND bsart = i_ekko-bsart .
 CLEAR i_ekpa[].
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa[].
 LOOP AT i_ekpa INTO i_wa_ekpa .
 i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
 i_wa_bpop-langu = sy-langu .
 IF NOT i_wa_ekpa-lifn2 IS INITIAL .
 i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
 ELSE .
 i_wa_bpop-buspartno = i_wa_ekpa-parnr .
 ENDIF .
 APPEND i_wa_bpop TO i_bpop .
 CLEAR: i_wa_ekpa, i_wa_bpop .
 ENDLOOP .
 CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
 CALL FUNCTION 'BAPI_PO_CREATE1'
 EXPORTING
 poheader = i_bpoh
 poheaderx = i_bpohx
 IMPORTING
 exppurchaseorder = i_new_ebeln
 TABLES
 return = i_bapiret2
 poitem = i_bpoi[]
 poitemx = i_bpoix[]
 poschedule = i_bpos[]
 poschedulex = i_bposx[].
 i_order = i_new_ebeln .
 SHIFT i_order LEFT DELETING LEADING '0' .
 i_return-errortype = c_char_i .
 i_return-workarea = c_zsw .
 i_return-message = '064' .
 i_return-variable1 = i_order .
 loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
 append i_bapiretn to t_bapi_return .
 endloop .
 if t_bapi_return[] is initial .
 i_create_order = c_char_x .
 CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
 EXPORTING
 act_return = i_return. "Popup with new PO no.
 ENDCASE . " Docind
 ENDIF .
ENDLOOP.

Hi Shareen,
I think in the following parts of the code,
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa[].
Error in : Purchase order Creation using BAPI_PO_CREATE1
Posted: Mar 20, 2006 7:39 PM Reply E-mail this post
Hell guys,
I am trying to create a PO using a BAPI - BAPI_PO_CREATE1
I want the new PO to have all the characteristics of an existing PO. whose PO # is stored in wa_order_split_create-docnr and for the new PO, i want the quantity from wa_order_split_create-qty_acptd and the delivery data to be wa_order_split_create-dly_date. But this process and code below gives a short dump in the std FM - MEPO_DOC_ITEM_GET . It raises an exception of failure. I am trying to create many new PO's in the loop below. If there is just one row, sometimes, it creates the PO even with the exception failure ( which is pretty weird).
Am i making any mistake while filling the header or item or schedule lines for the BAPI_PO_CREATE1 ? Any tips or clues why I am getting a dump ?
DATA: i_insert,
 i_create_order,
 i_cycle TYPE cycle,
 i_qty_acpt TYPE dzmeng,
 i_dly_date TYPE vbak-vdatu,
 i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
 i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
 i_vbap TYPE vbap,
 i_ekko TYPE ekko,
 i_ekpo TYPE ekpo,
 i_bsoh TYPE bapisdhd1,
 i_bsohx TYPE bapisdhd1x,
 i_bpoh TYPE bapimepoheader,
 i_bpohx TYPE bapimepoheaderx,
 i_vbeln TYPE vbeln_va,
 i_posnr TYPE posnr_va,
 i_contr TYPE vbeln_va,
 i_conit TYPE posnr_va,
 i_ebeln TYPE ebeln,
 i_ebelp TYPE ebelp,
 i_pargr TYPE pargr,
 i_thead TYPE thead,
 i_line TYPE tline,
 i_note TYPE txw_note,
 i_new_vbeln TYPE vbeln_va,
 i_new_ebeln TYPE ebeln,
 i_wa_bsoi TYPE bapisditm,
 i_wa_bsoix TYPE bapisditmx,
 i_wa_bsop TYPE bapiparnr,
 i_wa_bsos TYPE bapischdl,
 i_wa_bsosx TYPE bapischdlx,
 i_wa_vbpa TYPE vbpa,
 i_wa_vbkd TYPE vbkd,
 i_wa_bpoi TYPE bapimepoitem,
 i_wa_bpoix TYPE bapimepoitemx,
 i_wa_bpos TYPE bapimeposchedule,
 i_wa_bposx TYPE bapimeposchedulx,
 i_wa_bpop TYPE bapiekkop,
 i_wa_ekpa TYPE ekpa,
 i_message TYPE char72,
 i_bapiretn TYPE bapiret2,
 i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
 i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
 i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
 i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
 i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
 i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
 i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
 i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
 i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
 i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
 i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
 i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
 i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
 i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
 i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
 i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
 c_char_e VALUE 'E',
 c_char_p VALUE 'P',
 c_char_g VALUE 'G',
 c_char_i VALUE 'I',
 c_char_s VALUE 'S',
 c_char_x VALUE 'X',
 c_zsw(3) VALUE 'ZSW',
 c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
 IF NOT i_create_order IS INITIAL .
 CLEAR: i_create_order .
 MOVE: wa_order_split_create-docnr TO i_ebeln,
 wa_order_split_create-docitm TO i_ebelp .
 CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 IMPORTING
 po_ekko = i_ekko
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
 ENDIF .
Fill PO Header
 i_bpoh-comp_code = i_ekko-bukrs .
 i_bpoh-doc_type = i_ekko-bsart .
 i_bpoh-vendor = i_ekko-lifnr .
 i_bpoh-langu = i_ekko-spras .
 i_bpoh-pmnttrms = i_ekko-zterm .
 i_bpoh-purch_org = i_ekko-ekorg .
 i_bpoh-pur_group = i_ekko-ekgrp .
 i_bpoh-currency = i_ekko-waers .
 i_bpoh-agreement = i_ekko-konnr .
 i_bpoh-incoterms1 = i_ekko-inco1 .
 i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
 i_bpohx-comp_code = c_char_x .
 i_bpohx-doc_type = c_char_x .
 i_bpohx-vendor = c_char_x .
 i_bpohx-langu = c_char_x .
 i_bpohx-pmnttrms = c_char_x .
 i_bpohx-purch_org = c_char_x .
 i_bpohx-pur_group = c_char_x .
 i_bpohx-currency = c_char_x .
 i_bpohx-agreement = c_char_x .
 i_bpohx-incoterms1 = c_char_x .
 i_bpohx-incoterms2 = c_char_x .
 CALL FUNCTION 'ME_EKPO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 pi_ebelp = i_ebelp
 IMPORTING
 po_ekpo = i_ekpo
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF .
Fill PO Item
 i_wa_bpoi-po_item = i_ekpo-ebelp .
 i_wa_bpoi-material = i_ekpo-matnr .
 i_wa_bpoi-plant = i_ekpo-werks .
 i_wa_bpoi-stge_loc = i_ekpo-lgort .
 i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
 i_wa_bpoi-po_unit = i_ekpo-meins .
 i_wa_bpoi-tax_code = i_ekpo-mwskz .
 i_wa_bpoi-val_type = i_ekpo-bwtar .
 i_wa_bpoi-item_cat = i_ekpo-pstyp .
 i_wa_bpoi-acctasscat = i_ekpo-knttp .
 i_wa_bpoi-agreement = i_ekpo-konnr .
 i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
 APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
 i_wa_bpoix-po_item = i_ekpo-ebelp .
 i_wa_bpoix-po_itemx = c_char_x .
 i_wa_bpoix-material = c_char_x .
 i_wa_bpoix-plant = c_char_x .
 i_wa_bpoix-stge_loc = c_char_x .
 i_wa_bpoix-quantity = c_char_x .
 i_wa_bpoix-po_unit = c_char_x .
 i_wa_bpoix-tax_code = c_char_x .
 i_wa_bpoix-val_type = c_char_x .
 i_wa_bpoix-item_cat = c_char_x .
 i_wa_bpoix-acctasscat = c_char_x .
 i_wa_bpoix-agreement = c_char_x .
 i_wa_bpoix-agmt_item = c_char_x .
 APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
 i_wa_bpos-po_item = i_ekpo-ebelp .
 i_wa_bpos-sched_line = '0001' .
 i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
 i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
 APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
 i_wa_bposx-po_item = i_ekpo-ebelp .
 i_wa_bposx-sched_line = '0001' .
 i_wa_bposx-delivery_date = c_char_x .
 i_wa_bposx-quantity = c_char_x .
 APPEND i_wa_bposx TO i_bposx .
 CLEAR: i_pargr .
 SELECT SINGLE pargr
 INTO i_pargr
 FROM t161
 WHERE bstyp = i_ekko-bstyp
 AND bsart = i_ekko-bsart .
 CLEAR i_ekpa[].
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa[].
 LOOP AT i_ekpa INTO i_wa_ekpa .
 i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
 i_wa_bpop-langu = sy-langu .
 IF NOT i_wa_ekpa-lifn2 IS INITIAL .
 i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
 ELSE .
 i_wa_bpop-buspartno = i_wa_ekpa-parnr .
 ENDIF .
 APPEND i_wa_bpop TO i_bpop .
 CLEAR: i_wa_ekpa, i_wa_bpop .
 ENDLOOP .
 CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
 CALL FUNCTION 'BAPI_PO_CREATE1'
 EXPORTING
 poheader = i_bpoh
 poheaderx = i_bpohx
 IMPORTING
 exppurchaseorder = i_new_ebeln
 TABLES
 return = i_bapiret2
 poitem = i_bpoi[]
 poitemx = i_bpoix[]
 poschedule = i_bpos[]
 poschedulex = i_bposx[].
it should be only i_bpoi, i_bpoix, i_bpos, i_bposx but not i_bpoi[], i_bpoix[], i_bpos[], i_bposx[].
CHange the code as follows:
DATA: i_insert,
 i_create_order,
 i_cycle TYPE cycle,
 i_qty_acpt TYPE dzmeng,
 i_dly_date TYPE vbak-vdatu,
 i_item TYPE roijnomiio .
DATA: i_order TYPE symsgv,
 i_return TYPE swd_return .
DATA: i_vbak TYPE vbak,
 i_vbap TYPE vbap,
 i_ekko TYPE ekko,
 i_ekpo TYPE ekpo,
 i_bsoh TYPE bapisdhd1,
 i_bsohx TYPE bapisdhd1x,
 i_bpoh TYPE bapimepoheader,
 i_bpohx TYPE bapimepoheaderx,
 i_vbeln TYPE vbeln_va,
 i_posnr TYPE posnr_va,
 i_contr TYPE vbeln_va,
 i_conit TYPE posnr_va,
 i_ebeln TYPE ebeln,
 i_ebelp TYPE ebelp,
 i_pargr TYPE pargr,
 i_thead TYPE thead,
 i_line TYPE tline,
 i_note TYPE txw_note,
 i_new_vbeln TYPE vbeln_va,
 i_new_ebeln TYPE ebeln,
 i_wa_bsoi TYPE bapisditm,
 i_wa_bsoix TYPE bapisditmx,
 i_wa_bsop TYPE bapiparnr,
 i_wa_bsos TYPE bapischdl,
 i_wa_bsosx TYPE bapischdlx,
 i_wa_vbpa TYPE vbpa,
 i_wa_vbkd TYPE vbkd,
 i_wa_bpoi TYPE bapimepoitem,
 i_wa_bpoix TYPE bapimepoitemx,
 i_wa_bpos TYPE bapimeposchedule,
 i_wa_bposx TYPE bapimeposchedulx,
 i_wa_bpop TYPE bapiekkop,
 i_wa_ekpa TYPE ekpa,
 i_message TYPE char72,
 i_bapiretn TYPE bapiret2,
 i_bapiret2 TYPE TABLE OF bapiret2 INITIAL SIZE 1,
 i_vbpa TYPE TABLE OF vbpa INITIAL SIZE 1,
 i_vbkd TYPE TABLE OF vbkd INITIAL SIZE 1,
 i_ekpa TYPE TABLE OF ekpa INITIAL SIZE 1,
 i_bsoi TYPE TABLE OF bapisditm INITIAL SIZE 1,
 i_bsoix TYPE TABLE OF bapisditmx INITIAL SIZE 1,
 i_bsos TYPE TABLE OF bapischdl INITIAL SIZE 1,
 i_bsosx TYPE TABLE OF bapischdlx INITIAL SIZE 1,
 i_bsop TYPE TABLE OF bapiparnr INITIAL SIZE 1,
 i_bpoi TYPE TABLE OF bapimepoitem INITIAL SIZE 1,
 i_bpoix TYPE TABLE OF bapimepoitemx INITIAL SIZE 1,
 i_bpos TYPE TABLE OF bapimeposchedule INITIAL SIZE 1,
 i_bposx TYPE TABLE OF bapimeposchedulx INITIAL SIZE 1,
 i_bpop TYPE TABLE OF bapiekkop INITIAL SIZE 1,
 i_text_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_line_tab TYPE TABLE OF tline INITIAL SIZE 1,
 i_txw_note TYPE TABLE OF txw_note INITIAL SIZE 1,
 i_oij_el_doc_mot TYPE oij_el_doc_mot .
CONSTANTS: c_char_c VALUE 'C',
 c_char_e VALUE 'E',
 c_char_p VALUE 'P',
 c_char_g VALUE 'G',
 c_char_i VALUE 'I',
 c_char_s VALUE 'S',
 c_char_x VALUE 'X',
 c_zsw(3) VALUE 'ZSW',
 c_nomit_stat(4) VALUE 'ZDNY' .
DATA : lv_nomtk_split TYPE oij_nomtk.
DATA : i_order_split_create TYPE TABLE OF zsws_order_split.
DATA : wa_order_split_create TYPE zsws_order_split.
LOOP AT i_order_split_create INTO wa_order_split_create.
 IF NOT i_create_order IS INITIAL .
 CLEAR: i_create_order .
 MOVE: wa_order_split_create-docnr TO i_ebeln,
 wa_order_split_create-docitm TO i_ebelp .
 CALL FUNCTION 'ME_EKKO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 IMPORTING
 po_ekko = i_ekko
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
 ENDIF .
Fill PO Header
 i_bpoh-comp_code = i_ekko-bukrs .
 i_bpoh-doc_type = i_ekko-bsart .
 i_bpoh-vendor = i_ekko-lifnr .
 i_bpoh-langu = i_ekko-spras .
 i_bpoh-pmnttrms = i_ekko-zterm .
 i_bpoh-purch_org = i_ekko-ekorg .
 i_bpoh-pur_group = i_ekko-ekgrp .
 i_bpoh-currency = i_ekko-waers .
 i_bpoh-agreement = i_ekko-konnr .
 i_bpoh-incoterms1 = i_ekko-inco1 .
 i_bpoh-incoterms2 = i_ekko-inco2 .
Fill PO update indicator 'X'
 i_bpohx-comp_code = c_char_x .
 i_bpohx-doc_type = c_char_x .
 i_bpohx-vendor = c_char_x .
 i_bpohx-langu = c_char_x .
 i_bpohx-pmnttrms = c_char_x .
 i_bpohx-purch_org = c_char_x .
 i_bpohx-pur_group = c_char_x .
 i_bpohx-currency = c_char_x .
 i_bpohx-agreement = c_char_x .
 i_bpohx-incoterms1 = c_char_x .
 i_bpohx-incoterms2 = c_char_x .
 CALL FUNCTION 'ME_EKPO_SINGLE_READ'
 EXPORTING
 pi_ebeln = i_ebeln
 pi_ebelp = i_ebelp
 IMPORTING
 po_ekpo = i_ekpo
 EXCEPTIONS
 no_records_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0 .
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF .
Fill PO Item
 i_wa_bpoi-po_item = i_ekpo-ebelp .
 i_wa_bpoi-material = i_ekpo-matnr .
 i_wa_bpoi-plant = i_ekpo-werks .
 i_wa_bpoi-stge_loc = i_ekpo-lgort .
 i_wa_bpoi-quantity = wa_order_split_create-qty_acptd .
 i_wa_bpoi-po_unit = i_ekpo-meins .
 i_wa_bpoi-tax_code = i_ekpo-mwskz .
 i_wa_bpoi-val_type = i_ekpo-bwtar .
 i_wa_bpoi-item_cat = i_ekpo-pstyp .
 i_wa_bpoi-acctasscat = i_ekpo-knttp .
 i_wa_bpoi-agreement = i_ekpo-konnr .
 i_wa_bpoi-agmt_item = i_ekpo-ktpnr .
 APPEND i_wa_bpoi TO i_bpoi .
Fill PO Item update indicator 'X'
 i_wa_bpoix-po_item = i_ekpo-ebelp .
 i_wa_bpoix-po_itemx = c_char_x .
 i_wa_bpoix-material = c_char_x .
 i_wa_bpoix-plant = c_char_x .
 i_wa_bpoix-stge_loc = c_char_x .
 i_wa_bpoix-quantity = c_char_x .
 i_wa_bpoix-po_unit = c_char_x .
 i_wa_bpoix-tax_code = c_char_x .
 i_wa_bpoix-val_type = c_char_x .
 i_wa_bpoix-item_cat = c_char_x .
 i_wa_bpoix-acctasscat = c_char_x .
 i_wa_bpoix-agreement = c_char_x .
 i_wa_bpoix-agmt_item = c_char_x .
 APPEND i_wa_bpoix TO i_bpoix .
Fill PO Item Schedule
 i_wa_bpos-po_item = i_ekpo-ebelp .
 i_wa_bpos-sched_line = '0001' .
 i_wa_bpos-delivery_date = wa_order_split_create-dly_date .
 i_wa_bpos-quantity = wa_order_split_create-qty_acptd .
 APPEND i_wa_bpos TO i_bpos .
Fill PO Item schedule update indicator 'X'
 i_wa_bposx-po_item = i_ekpo-ebelp .
 i_wa_bposx-sched_line = '0001' .
 i_wa_bposx-delivery_date = c_char_x .
 i_wa_bposx-quantity = c_char_x .
 APPEND i_wa_bposx TO i_bposx .
 CLEAR: i_pargr .
 SELECT SINGLE pargr
 INTO i_pargr
 FROM t161
 WHERE bstyp = i_ekko-bstyp
 AND bsart = i_ekko-bsart .
 CLEAR i_ekpa[].
 CALL FUNCTION 'MM_READ_PARTNERS'
 EXPORTING
 application = c_char_p
 ebeln = i_ebeln
 bstyp = i_ekko-bstyp
 pargr = i_pargr
 TABLES
 x_ekpa = i_ekpa.
 LOOP AT i_ekpa INTO i_wa_ekpa .
 i_wa_bpop-partnerdesc = i_wa_ekpa-parvw .
 i_wa_bpop-langu = sy-langu .
 IF NOT i_wa_ekpa-lifn2 IS INITIAL .
 i_wa_bpop-buspartno = i_wa_ekpa-lifn2 .
 ELSE .
 i_wa_bpop-buspartno = i_wa_ekpa-parnr .
 ENDIF .
 APPEND i_wa_bpop TO i_bpop .
 CLEAR: i_wa_ekpa, i_wa_bpop .
 ENDLOOP .
 CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
 CALL FUNCTION 'BAPI_PO_CREATE1'
 EXPORTING
 poheader = i_bpoh
 poheaderx = i_bpohx
 IMPORTING
 exppurchaseorder = i_new_ebeln
 TABLES
 return = i_bapiret2
 poitem = i_bpoi
 poitemx = i_bpoix
 poschedule = i_bpos
 poschedulex = i_bposx.
 i_order = i_new_ebeln .
 SHIFT i_order LEFT DELETING LEADING '0' .
 i_return-errortype = c_char_i .
 i_return-workarea = c_zsw .
 i_return-message = '064' .
 i_return-variable1 = i_order .
 loop at i_bapiret2 into i_bapiretn where type ca 'EAX' .
 append i_bapiretn to t_bapi_return .
 endloop .
 if t_bapi_return[] is initial .
 i_create_order = c_char_x .
 CALL FUNCTION 'SWD_POPUP_MESSAGE_SEND'
 EXPORTING
 act_return = i_return. "Popup with new PO no.
 ENDCASE . " Docind
 ENDIF .
ENDLOOP.

Open Purchase Orders at Retail Value

Hi
I need to show Open Purchase Orders at Retail Value in one of my reports and I am using the key figure - "Open Purchase Orders (Retail Price) - 0RTOPDVSV".
I am using this KF in the cube ZRT_STWK which is part of a multiprovider. Data to this cube is being pulled from 2LIS_03_BF. I couldn't find a probable field in ECC to which I can map the field 0RTOPDVSV in the cube.
Any idea what the likely field could be in ECC which I can map to the key figure 0RTOPDVSV?
Any help is appreicated.
Thank you.
Pavan.

Hi,
To prepare the Open PO report:
Take all the purchase order details from EKKO and EKPO tables by writing a JOIN based on the selection screen paramters:(into ITAB)
Then fetch the related GR and GI data from the table MSEG for each PO Item (using for all entries of ITAB passing EBELn and EBELP to MSEG).
Here based on the movement type you have to consider the GR or GI.
generally for 101 movement types it is fresh GR(goods receipt).
so in this table MSEG you have many entries with different movement types for each PO items, so summing up the correct quanitities(ERFMG) for GR and other s is importants.So from ITAB you know the PO qty for a particular PO and from MSEG you know the qty received(GR QTY), if the both qty's are equal then that order is closed, if bothe qty's are not equal then that order is OPEN.
Fetch the invoice related data from EKBE or RSEG tablse passing EBELN and EBELP fields for them.
GR dat is in MSEG
and Invoice data is in EKBE or RSEG.
Hope this is useful.
regards,
Anji

Purchase order date posting problems

Hi all,
I have done an interface to post purchase/ sales order into sap. ive populated fields correctly into the segments and executed the fm. its posting all the data except the purchase order date in the header. i dont know why its doing dat. the field is populated into the segments and i can see it. but its not getting reflected in the order created .. can somebody help me with this. ive used date segment e1edk03 qualifier 22 field is iddat.
thanks,
kishore.

Hi,
Im using orders 05.. FM idoc_input_orders
Create Document header date segment - E1EDK03
*. I.e. set header level required delivery date
e1edk03-iddat = c_edi_iddat_002.
e1edk03-datum = date_required. "Set the date required
PERFORM add_segment USING c_segnam_e1edk03 e1edk03.
Header Level Customer purchase order date
e1edk03-iddat = c_edi_iddat_022. " default value 22.
e1edk03-datum = cust_po_date.
PERFORM add_segment USING c_segnam_e1edk03 e1edk03.
Header Level Pricing Date
e1edk03-iddat = c_edi_iddat_023.
e1edk03-datum = pricing_date.
PERFORM add_segment USING c_segnam_e1edk03 e1edk03.
Wat i could observe from fm idoc_input_orders fm , fm is not posting in the purchase order date for identifier 22.. u can have a look at it if u want.. include LVEDAF5W
is there any way to post this date plz
thanks

Regarding LSMW -- Purchase Order Data

Hi Friends,
I have one requirement i.e purchase order data need to be upload through LSMW via Direct input method.
=============
pls find the belwo flat file structure
old_PO           material            price            qty
P123              M111                  10               1
P123              M222                  10                1
P123              M333                  20               1
===============
Normally if I upload same data into SAP, it will create three purchase orders with different SAP numbers.
I want if old_PO number is matches with the previous record all the materials should be in single transaction and single Purchase order should be created.
Can any body help how to resolve this issue. This is very urgent.
pls explain in detail. I am using LSMW. I don't have no other option.
=====
please don't post any junk amswers.
=====
Thanks in advance

Hi Raghunath,
Don't think that this reply is junk one.I cannot explain you in detail but try like this.
In the fifth step of LSMW,You can find Global data definitions & Processing times.
In any of these you can just fetch the values from database with reference to flat file data like..
select PO from ...where PO = source-PO.
if sy-subrc EQ 0.
skip_transaction. Using this function you can skip this record
endif.
Award points if useful.
Thanks,
Ravee..

'How to restrict change in Quantity/Price in saved Purchase Order in SAP B1'

Dear All,
How can I restrict a user from changing Quantity or Price in a saved Purchase Order in SAP B1 8.81 PL 0?
Regards.

Try This TN SP
If @object_type='22' and @transaction_type='U'
BEGIN
If Exists (SELECT T0.docnum FROM [dbo].[OPOR] T0
INNER JOIN [dbo].[POR1] T1 ON T1.DOCENTRY = T0.docENTRY
WHERE T0.DOCENTRY = @list_of_cols_val_tab_del)
BEGIN
Select @error = -1,
@error_message = 'Update not possible'
End
End
Regards
Kennedy

What is the BADI while SAVING purchase order using me22n?

what is the BADI while SAVING purchase order using me22n?
while i will save purchase order through me22n, badi should be fire what is badi for that?
regards,
dushyant.

Dushyant,
Hopefully you know how to implement the BADI ME_PROCESS_PO_CUST now.
The following are the codes that you can put in the method "Post".
DATA: LW_HEADER TYPE MEPOHEADER,
 LW_POSTED_HEADER TYPE MEPOHEADER,
 LW_VALID TYPE MMPUR_BOOL,
 ITAB_ITEM TYPE PURCHASE_ORDER_ITEMS,
 LW_ITEM TYPE MEPOITEM,
 ITEM_INTERFACE TYPE PURCHASE_ORDER_ITEM,
 ITAB_ACCT TYPE PURCHASE_ORDER_ACCOUNTINGS,
 ACCT_INTERFACE TYPE PURCHASE_ORDER_ACCOUNTING,
 LW_ACCT TYPE MEPOACCOUNTING,
 LW_POSTED_ACCT TYPE MEPOACCOUNTING,
 W_ACCT_CHANGED TYPE C,
 W_GRANT_AMT TYPE EKPO-NETWR,
 W_FINANCE_AMT TYPE EKPO-NETWR,
 W_FLAG TYPE C.
Check if PO header data is valid
CLEAR LW_VALID.
CALL METHOD IM_HEADER->IS_VALID
 RECEIVING
 RE_VALID = LW_VALID.
CHECK LW_VALID = 'X'.
PO header data is valid
Get the newly updated PO header data
CLEAR LW_HEADER.
CALL METHOD IM_HEADER->GET_DATA
 RECEIVING
 RE_DATA = LW_HEADER.
Get the posted PO header data
CLEAR LW_POSTED_HEADER.
CALL METHOD IM_HEADER->GET_PERSISTENT_DATA
 IMPORTING
 EX_DATA = LW_POSTED_HEADER
 EXCEPTIONS
 NO_DATA = 1.
IF SY-SUBRC <> 0.
 CLEAR LW_POSTED_HEADER.
ENDIF.
Get PO line items
REFRESH ITAB_ITEM.
CALL METHOD IM_HEADER->GET_ITEMS
 RECEIVING
 RE_ITEMS = ITAB_ITEM.
LOOP AT ITAB_ITEM INTO ITEM_INTERFACE.
Check if PO line item is valid
 CLEAR LW_VALID.
 CALL METHOD ITEM_INTERFACE-ITEM->IS_VALID
 RECEIVING
 RE_VALID = LW_VALID.
 IF LW_VALID <> 'X'.
This PO line item is not valid
 CLEAR W_ACCT_CHANGED.
 EXIT.
 ENDIF.
 CLEAR LW_ITEM.
 CALL METHOD ITEM_INTERFACE-ITEM->GET_DATA
 RECEIVING
 RE_DATA = LW_ITEM.
Get the account interface
 REFRESH ITAB_ACCT.
 CALL METHOD ITEM_INTERFACE-ITEM->GET_ACCOUNTINGS
 RECEIVING
 RE_ACCOUNTINGS = ITAB_ACCT.
 LOOP AT ITAB_ACCT INTO ACCT_INTERFACE.
 CLEAR LW_ACCT.
Get the newly updated PO item data
 CALL METHOD ACCT_INTERFACE-ACCOUNTING->GET_DATA
 RECEIVING
 RE_DATA = LW_ACCT.
 CLEAR LW_POSTED_ACCT.
Get the posted PO item data
 CALL METHOD ACCT_INTERFACE-ACCOUNTING->GET_PERSISTENT_DATA
 IMPORTING
 EX_DATA = LW_POSTED_ACCT
 EXCEPTIONS
 NO_DATA = 1.
 IF SY-SUBRC > 0.
 CLEAR LW_POSTED_ACCT.
 ENDIF.
 IF LW_ACCT-LOEKZ <> LW_POSTED_ACCT-LOEKZ OR
 LW_ACCT-KOSTL <> LW_POSTED_ACCT-KOSTL OR
 LW_ACCT-PRCTR <> LW_POSTED_ACCT-PRCTR OR
 LW_ACCT-PS_PSP_PNR <> LW_POSTED_ACCT-PS_PSP_PNR.
Account assignment was changed
We will force this PO to go through workflow
 W_ACCT_CHANGED = 'Y'.
 ENDIF.
 ENDLOOP.
ENDLOOP.

Purchase order data for ATP category BH and BI not retrieved

Hi Experts,
I have a requirement where I need to extract purchase orders data from the bapi BAPI_POSRVAPS_GETLIST3. I am passing the locations, products and ATP categories AG,EF,BF,BI and BH. However, my bapi works correctly for AG,EF and BF, but it does not retrieve the data for BI and BH categories.
I have debugged the bapi and found that it is unable to retrieve data from the live cache.
Can anybody please help me out and let me know the exact reason for this issue? I have checked the return table of the bapi and it does not give any error message as well.
Looking forward to your reply.
Thanks in advance.
--Warm Regards,
Prajakta K.

Hi,
BI (stock transport order) and BH (PreqRel) are demand elements for which there exist corresponding receipt element as BF (Purchase order) and AG (Preq) respectively. BAPI will give data for these categories.Thus you can get data for BI and BH from corresponding BF and AG.
Similarly EF (Dep:Preq) is receipt element and you will not get data for corresponding demand element which is available in the system as EG (Dep:ConRel).
I think BAPI is working fine.
Regards,
~Vaibhav

Output error in purchase order 3000000002 for output medium PRN

Hello,
I got this error message:
'Output error in purchase order 3000000002 for output medium PRN'
Regards,
Lina

Hi
Please go through this ->
To set Output type,check the foll path:
SPRO->supplier relationship management-> SRM Server->Cross application basic setting->set output action and output format
See the foll link for more details:
http://help.sap.com/saphelp_srm50/helpdata/en/91/41faf2c220e84c9002a4ae4cc1906a/frameset.htm
Look for BADI "BBP_SEND_MEDIUM_MODE ".
Related notes:
Note 1028388 - User settings for output medium is not saved.
Note 885593 - SRM 5.0 SP02: Incorrect output medium and change impossible
Do let me know.
Regards
- Atul

Customer purchase order date allow 01.01.0511 in sales order ??

Hello All,
In sales order,Customer purchase order date (filed name BSTDK) 01.01.0511 was maintained.
the date format 01.01.0511 will allowing in this field in SAP in teh slaes order.
or this is typo error.??
VBKD-BSTDK is having DATS data type.
rec
if we use same date 01.01.0511 on the POs, system will give error message
"Delivery date outside period covered by factory calender DE (DE-germany) with message no:ME078".
so how to cor

Hello All,
In sales order,Customer purchase order date (filed name BSTDK) 01.01.0511 was maintained.
the date format 01.01.0511 will allowing in this field in SAP in teh slaes order.
or this is typo error.??
VBKD-BSTDK is having DATS data type.
if we use same date 01.01.0511 on the POs, system will give error message
"Delivery date outside period covered by factory calender DE (DE-germany) with message no:ME078".
so how to correct the date 01.01.0511 in VBKD-BSTDK ??

Purchase order data

Hi Can anyone tell me how to download purchase order data of material master data? Which table?

Hi
The Purchaser Order Text of the Material Master data can be downloaded ans saved to the local file using the 'Save to File' Icon in the Material Master data.
Goto MM03, for the material and select the Purchase order text view and in the small window where the Text is written, you can see the icon 'Save to File'.
Regards
Siva

Doubt in uploading purchase order data using BDC

Hi friends,
how to upload purchase order data.
1) In both BDC and BAPI which one is preferable?
2) for suppose if it is through BDC, how to use? what are the transactions that we can use(SHDB, ME21N,ME21)?
3) To execute the job in background, is it possible for both call transaction and session method.
Thanks in advance
Sreenivas k

It really depends on the number of records you have. Still for a set of 5,000 records my answer to your questions will be:
1) In both BDC and BAPI which one is preferable? - Go with BDC
2) for suppose if it is through BDC, how to use? what are the transactions that we can use(SHDB, ME21N,ME21)? - Yes, its SHDB for recording, SE38 for abap program and ME21 for PO. Avoid SAP Enjoy transactions for recording as you may end up having problems wiht it.
3) To execute the job in background, is it possible for both call transaction and session method. - If you use call transaction method then you have to schedule the job to run in background or simply run it through F9 instead of F8. In case of session method you can chose to process the session in background. However I would suggest you go with BDC Session method for this.
- Guru
Reward points for helpful answers

Error saving purchase order data decimal values in SAP R/3

Similar Messages

Maybe you are looking for