Error in Rush Order

Hi,
While doing billing in rush order i got an error that"No billing document was generated".
Plz help me

Hi Please check the log in edit what it says .
Check whether Picking happens properly in immediate delivery created and check whether GI is done or not .
Then try to create Invoice .
Hope it will work.

Similar Messages

Error in Rush Order type with BOM item!!

Hello,
I am facing a very strange error while creating a rush Order with BOM item.
System Error:
1. No item category available (Table T184 SO ERLA TAQ).
I except the error. I get next error as
2. Structure explosion for item 000010 is not possible.
After this BOM explodes with only first 2 Sub Items ( Item cat for main item is determind as TAQ and Sub Items as TAE) , where as the complete BOM has 7 Sub items.
I have made the required configs in item cat determination in T184 table for order type SO, as follows.
SO ERLA - TAQ for Main Item of the BOM
SO NORM TAQ TAE for the Sub Item of the BOM
The same item (BOM ) works very well in OR/BV kind of sales order types, by exploding the BOM to full level(i.e all the 7 sub items are determined).
Has any one come across such an issue. Please let me know what could be the solution?
Thanks in adv,
Shripad

Hi,
Thanks,
In vov7 for TAQ Item Cat. the structure scope is maintained as 'A'. And that's the reason for Standard order 'OR' , the BOM is exploding properly.
It is only with Rush Order , the BOM is not exploding correctly.
BR
Shripad

BOM error in Rush Order.

Hello,
I am facing a very strange error while creating a rush Order with BOM item.
System Error:
1. No item category available (Table T184 SO ERLA TAQ).
I except the error. I get next error as
2. Structure explosion for item 000010 is not possible.
After this BOM explodes with only first 2 Sub Items ( Item cat for main item is determind as TAQ and Sub Items as TAE) , where as the complete BOM has 7 Sub items.
I have made the required configs in item cat determination in T184 table for order type SO, as follows.
SO ERLA - TAQ for Main Item of the BOM
SO NORM TAQ TAE for the Sub Item of the BOM
The same item (BOM ) works very well in OR/BV kind of sales order types, by exploding the BOM to full level(i.e all the 7 sub items are determined).
Has any one come across such an issue. Please let me know what could be the solution.
Thanks in adv,
Shripad

Hi,
Thanks,
In vov7 for TAQ Item Cat. the structure scope is maintained as 'A'. And that's the reason for Standard order 'OR' , the BOM is exploding properly.
It is only with Rush Order , the BOM is not exploding correctly.
BR
Shripad

Error-cash/rush order problem

Dear all,
Apologies for bringing it up again as I am having constant problem on below transactions.
I thought my CASH/RUSH order u2018u2019immediate deliveryu2019u2019 problem was solved when I had discussed the same issue last week within the forum. Unfortunately last time there was some issue with material stock but after I had maintained the stock issue was resolved.
Now from last two days I am facing the same problem again and againu2026u2026u2026.........inspite of maintaining huge stock for the material.
Automatic shipping point determination is also happening in sales order but I am still having this error I.E no u2018u2019immediate deliveryu2019u2019
creation for above order.
Other config are also done as required like......
cs/ro doc type- immediated delivery is active
shipping condition is 10 ( immediate)
Can anybody think of any thing else ...which I am missing.
many thanks in advance.
Cheers!

Hi
How ever when today I have created CS/RO with different material e.g DEFG....then I was successful to create immediated delivery.
This clearly tells that there is no problem in configuration and there is problem with the master data of material e.g ABCD
Having said this there are some fields in master data that can influence configuration for example MRP type of the material can impact schedule line category which inturn affects availability check and requirements transfer
So check your master data tharoughly
Check where both the materials are are maintained in the same plant
If material e.g ABCD is in a different plant than that of material e.g DEFG you need to check the plant configuration too
In MMR delivering plant is proper or not? and also for that correct combination shipping pt determination is maintained or not
Check the schedule lines of the sales order
Regards
Raja

Error in cash sales / rush order process

Hi
i have created cash sales and rush order as delivery being created immediately but in my case its not creating i have done config i.e checked th box for immediate delivery but still getting error kindly help where am doing mistake .when am trying to do delivery separately in vl01n its giving error Copying is not poss.because an entry is missing in Table TVCPL: MSCS MVBV
Edited by: mukesh kumar on Mar 22, 2009 4:41 PM

Hi Mukesh
In t code VTLA copy control keys are missing to create delivery
Hence the error
Cash sale order type BV (if ECC 6.0) or CS if previous versions the delivery type is BV and the item category is BVN
In VTLA between BV order type to BV delivery type heder level controls have to be defined
At item level for the item category BVN controls have to be defined
Rush order type ROand the delivery type is LFand the item category is TAN
In VTLA between RO order type to LF delivery type heder level controls have to be defined
At item level for the item category TAN controls have to be defined
Then check your OVL2 settings also whether shipping point determination are properly maintained
Normally for cash sales order type SHIPPING CONDITIONS are maintained at order type in VOV8
For this SHIPPING CONDITIONS combination have you maintained proper shipping point determination in OVL2
This also please check
Normally in most of the cases SHIPPING CONDITIONS are maintained in Customer Master not in order types
But for Cash sale SHIPPING CONDITIONS are maintained in its order type in VOV8
If SHIPPING CONDITIONS are maintained order type in VOV8 then it has preference over what is maintained in customer master
Regards
Raja

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.

Error while creating order

hello all,
i got a error while creating order please help me in resolving the issue,
Service/maintenance order type AD02 not completely maintained in plant 1000
Thanks & regards,
Balaji

Hi,
A work order type has specific parameters per plant, when you create a new order type is easier to copy from existing the all the parameters will be copied too; these are some:
Plant Maintenance and Customer Service>Maintenance and Service Processing>Maintenance and Service Orders>Functions and Settings for Order Types>Assign Order Types to Maintenance Plants
Plant Maintenance and Customer Service>Maintenance and Service Processing>Maintenance and Service Orders>Functions and Settings for Order Types>Control Key-->Maintain Default Values for Control Keys for Order Types
Plant Maintenance and Customer Service>Maintenance and Service Processing>Maintenance and Service Orders>Functions and Settings for Order Types>Costing Data for Maintenance and Service Orders-->Assign Costing Parameters and Results Analysis Keys
Plant Maintenance and Customer Service>Maintenance and Service Processing>Maintenance and Service Orders>Functions and Settings for Order Types>Availability Check for Material, PRTs, and Capacities-->Define Inspection Control
Plant Maintenance and Customer Service>Maintenance and Service Processing>Maintenance and Service Orders>Completion Confirmations> Define Control Parameters for Completion Confirmations
Regards,
Carlos

There is an error in the order submission.

Hi,
While placing order in iStore(11.5.7 vis) i got the following error."Error messages from Order Management. The item specified is invalid or does not exist in the warehouse you specified. Please Enter a valid item- warehouse combination. Invalid unit of measure for this item. There is an error in the order submission."
The item was created only in the master inv org (V1) and not in M1.The error appeared only when placing order in istore and not in OM since warehouse was explicitly chosen. After assigning the item to M1 the order was placed without any error in istore.
Would like to know why istore picks up item particularly from M1.Is there any profile option or setting?
Thanks & Regards,
Nithya

symptom: The item specified is invalid or does not exist in the warehouse
you specified.
Please enter a valid item-warehouse combination
change: Note Role : Navigation -> Order management -> Order return -&
gt; Import order -> Correction.
cause: Internal ordered enabled flag not checked for the item
fix:
Check the internal order Enabled flag for the Item
Thanks
Naveen

Error in Sales order - Consumption account not found

Hi Gurus,
I am facing an error in Sales order - 'Consumption account not found'. The scenario is third party. In sales order, it says 'Consumption account not found'. the item category is TAS and scedule line category has general modification key 'VKA'. And as it is third party, thr is no movement type for the schedule line category. The valuation class of the material is 3334 (software services). I was thinking In OBYC, under GBB key, this combination of my val. grping code+ 3334 + VKA and relevant GLs shud exist.
But in my development client, i dont get any error for the same material. And in thr also, thr is no mention of entry like above combination in OBYC. So its making me think that its not config error. But its an issue of master data or GL data.
Please help me . This is critical.
-Prashant

Hi,
Your observation is perfectly write, the possible errors are
1. Check the combination of Account modifier of Purchase order account assignmnet or PR. Based on the modifier and check the relevent combination in OBYC
Valuation ClassAccount ModifierIf Groups is there + Transaction Event Key + Gl Accounts
2. If GL Account is available then check the GL Master through FS00 for validation of mandatory consumption is required and i feel there is no issue with material master.
Rewards if it helps
Regards
Goutham

Error in sales order when selecting a warranty item in configurator 'Please enter required information - Service Reference Type Code'

Error in sales order when selecting a warranty item in configurator 'Please enter required information - Service Reference Type Code'
Not able to book the sales order because of this issue

Order Management does not support the inclusion of optional service items in a configured Model BOM (see Support article #1296751.1 for more detail). Allowing for such would therefore require customization.
As you've found, there's no modeling restriction that prevents you from creating a Model BOM that includes optional service items, nor is there any problem with creating a Configurator Model for it. And required service items (such as a warranty item that is a required child of an optional BOM component) do not present a problem; they have nothing to do with Configurator, and would never appear as sub-lines in OM. The problem arises in OM, which requires that any service item be "associated" to the item it's "servicing". OM does not automatically make such an association with service sub-lines, even though it might be argued that an association may be inferred by the BOM structure (i.e., OM does not assume that an optional service sub-line is necessarily associated, from a service standpoint, with its BOM parent). OM customization is therefore required in order to hook any service item up to its corresponding product item. Many customers who configure service along with product have implemented such a customization.
(Another gap in such a solution that may be relevant to you is that for an included optional service item requiring recurring billing, Order Management does not create the requisite Service Contract. Customers have likewise developed customizations to address this, as well.)
As this is not specifically a Configurator matter (you could have created your order without using Configurator at all, and you would have experienced the exact same behavior), please do not take my explanation as being either authoritative or comprehensive (I am a Configurator expert, and only knowledgeable enough about Order Management to be dangerous). It would be advisable for you to seek more detailed information/recommendations from the Order Management forum.
Eogan

Trying to purchase trial period in different email address - error message "Error in Your Order The account was registered for a different country. Please sign out and sign in using an existing account for this country. Ok"

Trying to purchase trial period in different email address - error message "Error in Your Order The account was registered for a different country. Please sign out and sign in using an existing account for this country. Ok"@

Hi boags2014,
Please refer this link and know the work-arounds for the same:
How do I complete a purchase when I get an incorrect "country" error?
Regards,
Anubha

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

GR/IR Posting Error CKMLGRIR025 - Purchase Order History Inconsistent

Hi Everyone.
We currently have a posting in our GRIR for a Feright Condition Value against a Purchase Order which gets the above error when trying to post in MR11.
The Diagnosis of the error reads:
"The purchase order history contains differences between the goods receipt and invoice receipts/Account maintenance for the order item in the field Difference Quantitiy (= 43.804 TO) and Difference Value (= -342.77)
The purchase order history for this tiem is inconsistent"
When looking at this Freight Condition information in the Purchase Order I can not see why this item has resulted in this error in MR11.
Has anyone else seen this error come through in their system, and do you have any ideas on how to fix this.
Thanks
Hayley

We are experiencing the same issue with the GRIR Posting Error CKMLGRIR025 - puchase order history inconsistent. The actual message that we receive is Puchase Order history already inconsistent -->Quantity 1.00 EA Value 0.65-USD.
We reviewed SAP Note 708649 which also recommends using transaction MIRO with the corresponding default quantity and value o. However, we are not able to enter an Invoice for the "default qty & value 0", as SAP gives me error message M8278 "You are not allowed to have zero lines" (just like Haley commented). In reviewing this thread, I did not find the solution to the error message M8278 "You are not allowed to have zero lines" . Could someone help me understand?
Thank you!

Sales order stock error in Process order confirmation

Hello SAP Gurus,
In Make To order scnario while I do COR6 order confirmation it gives me Error that Sales order stock does not exist.
Can anyone suggest me which way I can remove the error?
What is the Transaction and movement to transfer stock to SALES ORDER?
Please reply...
Thanks & Regards,
Bhavik Dangi.

Hi,
As per your mail, you can move the stock from normal stock to sales order stock through transaction MB1B with movement type 412 E. This route is generally follow if want to assign stocks manually to sales order stock otherwise if follow the PP route then system generates the stock against the sales order line item at the time of produciton confirmation and requirement type use in this are KSL, KE.
Rewards if it helps.
Regards
Goutham

Rush Order & RLT

Hi All, am currently using RLT, i would like to control the rush orders from consuming the stock reserved by the sales orders available in the system already.
note : i cannot exclude the sales requirements from delivery scope of availability check, because i see an inconsistency that when the sales orders requirement is twice more than the available stock, ( say order 1 - 50, order 2 - 70, stock came in for 60, availability check re - ran ), sales order 1 cannot be delivered even after the confirmation is available.
thanks & regards
Ilango

Hi Shiva,
i think i did not explain it better, when i check the include sales requirements in the delivery level scope of check, i have issues on the regular standard order scenarios, as explained with 2 sales orders & less stock scenario in the problem statement above.
i already have include deliveries.
The problem now i have is if i include sales requirements from delivery scope of check, i have issues with standard order, explained above. if i remove this requirement (exclude sales requirements), my standard orders reserved stocks are being utilized by rush orders.
how to come out of both these scenarios.?

Error in Rush Order

Similar Messages

Maybe you are looking for