The problem in using object = 0090 to create sales order in LSMW?

who can tell where is the problem "No logical path has been specified" when I doing "specify files"?
tks in advance.

Hi
There can be two ways -
1. Check if the file is present and with correct format.
2.The problem might be that when we execute "specify files",
sometimes, by default we get file name ..but not the entire path...
Try to browse thrugh the file entire path ...and then press enter .
Hope it helps
Reward if useful.
Regards
Megha Sharma

Similar Messages

Not using substitute material while creating sales order with function?

hi experts.
I use SD_SALESDOCUMENT_CREATE function to create a sales order.
Material A has a substitute material B with substitute reason 0005.
So if I use material A when creating sales order with SD_SALESDOCUMENT_CREATE, the order is created with material B.
I don't want to substitute the material automatically. I want to create the sales order with material A.
What should I do? Help me please.
Edited by: Ji Yeob Kim on Nov 19, 2009 11:34 AM

Hi Kim,
I also have same requirement. Please suggest how you resolved this?
Thanks
bvrnreddy

Not able to create sales order using BAPI - BAPI_SALESORDER_CREATEFROMDAT2

Hi Experts,
I am not able to create sales order . I am using BAPI - BAPI_SALESORDER_CREATEFROMDAT2
to create sales order .I am passing external sales order number to the parameter
SALESDOCUMENTIN.
I am getting following error.
"524 |Only quantity 1 EA is allowed (Item 00001"
Here EA is UOM(Unit of measurement).
Below is the sample program through which i am trying to create the sales order.
*& Report ZSDC_SALES_TEST
report zsdc_sales_test.
*DATA: wa_bapi_header TYPE bapisdhd1.
Include Name - ZSDC_SALES_ORD_UPLOAD_TOP
Program Name - ZSDC_SALES_ORD_UPLOAD_1393
Program Title - Include for Data Declaration and selection screen
Created by - Lalitha W
Created on - 18-Nov-2008
Object ID - SD_C_1393_SALES_ORDER_UPLOAD
Request Id - SD3K905579
Description - This is a common INCLUDE for data declarations and
*selection screen details.
 HISTORY
Date |Developer |Req by | Description |Reference ID
 | | | |
 | | | |
 TYPE-POOLS
*TYPE-POOLS: truxs, abap, slis.
 TABLES
*TABLES: t100.
 TYPES
types:begin of ty_header,
 auart(4) type c, " Sales Order Type
 vkorg(4) type c, " Sales Organization
 vtweg(2) type c, " Distrubution Channel
 spart(2) type c, " Division
 kunnr_1(10) type c, " Sold to Party
 kunnr_2(10) type c, " Ship to Party
 augru(3) type c, " Order Reason
 bstkd(35) type c, " PO Number
 bstdk(10) type c, " PO Date
 ketdat(10) type c, " Required Delivery Date
 zterm(4) type c, " Payment Terms
 inco1(3) type c, " Inco Terms -1
 inco2(28) type c, " Inco Terms -2
 prsdt(10) type c, " pricing date
 waerk(5) type c, " Document Currency
 vkbur(4) type c, " Sales Office
 vkgrp(3) type c, " Sales group
 pltyp(2) type c, " Price List type
 kdgrp(2) type c, " Customer Group
 bstkd_e(35) type c, " Ship-to-party PO number
 submi(10) type c, " Collective Number
 bname(35) type c, " Name
 ihrez(12) type c, " Your Reference
 kschl_1(4) type c, " Condition Type
 kbetr_1(11) type c, " Amount
 kschl_2(4) type c, " Condition Type
 kbetr_2(11) type c, " Amount
 kschl_3(4) type c, " Condition Type
 kbetr_3(11) type c, " Amount
 partner_1(25) TYPE c, " Partner(Bill To Party Number)
 partner_2(25) TYPE c, " Partner(Payer Number)
 partner_3(25) TYPE c, " Partner(Sales Responsible Number)
 partner_4(25) TYPE c, " Partner(Order admin)
 partner_5(25) TYPE c, " Partner(Contact person)
 partner_1(10) type c, " Partner(Bill To Party Number)
 partner_2(10) type c, " Partner(Payer Number)
 partner_3(10) type c, " Partner(Sales Responsible Number)
 partner_4(10) type c, " Partner(Order admin)
 partner_5(10) type c, " Partner(Contact person)
 tdspras_1(2) type c,
 text_1(500) type c, " Text Before Items Z012
 tdspras_2(2) type c,
 text_2(500) type c, " Invocie Up Z034
 tdspras_3(2) type c,
 text_3(500) type c, " Invocie Down Z035
 tdspras_4(2) type c,
 text_4(500) type c, " Customer Reference Continue Z018
 tdspras_5(2) type c,
 text_5(500) type c, " Dispatch Marks/ Order Z019
 tdspras_6(2) type c,
 text_6(500) type c, " Ordered By Z003
 tdspras_7(2) type c,
 text_7(500) type c, " Sales Parameters Z002
 kvgr1(3) type c, " Industry
 kvgr2(3) type c, " customer BU
end of ty_header.
types: begin of ty_item,
 bstkd(35) type c, " PO Number
 bstdk(10) type c, " PO Date
 bstkd_e(35) type c, " Ship-to-party PO number
 posnr(6) type c, " POSTION NUMBER
 matnr(18) type c, " Material Number
 kwmeng(18) type c, " Order Quantity
 pstyv(4) type c, " Sales doc. item categ
 kursk(18) type c, " EXCHANGE RATE****
 ffprf(8) type c, " DIP PROFILE
 werks(4) type c, " Delivering Plant
 vstel(4) type c, " SHIPPING POINT
 lgort(4) type c, " STORAGE LOCATION
 route(6) type c, " Route
 kurrf(18) type c, " EXCHANGE RATE-FI
 ntgew(18) type c, " Net Weight
 brgew(18) type c, " Gross Weight
 gewei(3) type c, " Weight Unit
 prctr(10) type c, " profit center
 abgrs(6) type c, " RESULT ANALYSIS KEY
 kalsm_k(4) type c, " COSTING SHEET
 kschl_1(4) type c, " Condition Type
 kbetr_1(11) type c, " Amount
 kschl_2(4) type c, " Condition Type
 kbetr_2(11) type c, " Amount
 kschl_3(4) type c, " Condition Type
 kbetr_3(11) type c, " Amount
 text_1(500) type c, " material Text 0001
 tdspras_1(1) type c,
 text_2(500) type c, " Pr Text 9001
 tdspras_2(1) type c,
 end of ty_item.
types: begin of ty_schedule_line,
 bstkd(35) type c, "PO number
 bstdk(10) type c, "PO date
 bstkd_e(35) type c, "Ship-to-party PO number
 posnr(6) type c, "sales doc.Item
 etdat(10) type c, "Schedule line date
 wmeng(2) type c, "Order Quantity
 end of ty_schedule_line.
types: begin of ty_err ,
 auart(4) type c, " Sales Order Type
 vkorg(4) type c, " Sales Organization
 vtweg(2) type c, " Distrubution Channel
 spart(2) type c, " Division
 kunnr_1(10) type c, " Sold to Party
 kunnr_2(10) type c, " Ship to Party
 augru(3) type c, " Order Reason
 bstkd(35) type c, " PO Number
 bstdk(10) type c, " PO Date
 ketdat(10) type c, " Required Delivery Date
 zterm(4) type c, " Payment Terms
 inco1(3) type c, " Inco Terms -1
 inco2(28) type c, " Inco Terms -2
 prsdt(10) type c, " pricing date
 waerk(5) type c, " Document Currency
 vkbur(2) type c, " Sales Office
 vkgrp(3) type c, " Sales group
 pltyp(2) type c, " Price List type
 kdgrp(2) type c, " Customer Group
 bstkd_e(35) type c, " Ship-to-party PO number
 submi(10) type c, " Collective Number
 bname(35) type c, " Name
 ihrez(12) type c, " Your Reference
 kschl_1(4) type c, " Condition Type
 kbetr_1(11) type c, " Amount
 kschl_2(4) type c, " Condition Type
 kbetr_2(11) type c, " Amount
 kschl_3(4) type c, " Condition Type
 kbetr_3(11) type c, " Amount
 partner_1(25) type c, " Partner(Bill To Party Number)
 partner_2(25) type c, " Partner(Payer Number)
 partner_3(25) type c, " Partner(Sales Responsible Number)
 partner_4(25) type c, " Partner(Order admin)
 partner_5(25) type c, " Partner(Contact person)
 tdspras_1(2) type c,
 text_1(500) type c, " Text Before Items Z012
 tdspras_2(2) type c,
 text_2(500) type c, " Invocie Up Z034
 tdspras_3(2) type c,
 text_3(500) type c, " Invocie Down Z035
 tdspras_4(2) type c,
 text_4(500) type c, " Customer Reference Continue Z018
 tdspras_5(2) type c,
 text_5(500) type c, " Dispatch Marks/ Order Z019
 tdspras_6(2) type c,
 text_6(500) type c, " Ordered By Z003
 tdspras_7(2) type c,
 text_7(500) type c, " Sales Parameters Z002
 kvgr1(3) type c, " Industry
 kvgr2(3) type c, " customer BU
 message(600) type c,
end of ty_err.
types: begin of ty_t685a,
 kschl type kschl,
 krech type krech,
 end of ty_t685a.
 INTERNAL TABLES
***header
data: g_krech_1(4) type c, " Calculation type for condition
 g_krech_2(4) type c, " Calculation type for condition
 g_krech_3(4) type c. " Calculation type for condition
 g_krech_4(4) TYPE c, " Calculation type for condition
 g_krech_5(4) TYPE c, " Calculation type for condition
 g_krech_6(4) TYPE c, " Calculation type for condition
 g_krech_7(4) TYPE c, " Calculation type for condition
 g_krech_8(4) TYPE c, " Calculation type for condition
 g_krech_9(4) TYPE c, " Calculation type for condition
 g_krech_10(4) TYPE c, " Calculation type for condition
 g_krech_11(4) TYPE c, " Calculation type for condition
 g_krech_12(4) TYPE c, " Calculation type for condition
 g_krech_13(4) TYPE c, " Calculation type for condition
 g_krech_14(4) TYPE c, " Calculation type for condition
 g_krech_15(4) TYPE c, " Calculation type for condition
 g_krech_16(4) TYPE c, " Calculation type for condition
 g_krech_17(4) TYPE c, " Calculation type for condition
 g_krech_18(4) TYPE c, " Calculation type for condition
 g_krech_19(4) TYPE c, " Calculation type for condition
 g_krech_20(4) TYPE c. " Calculation type for condition
Items
data: g_krech_item_1(4) type c, " Calculation type for condition
 g_krech_item_2(4) type c, " Calculation type for condition
 g_krech_item_3(4) type c. " Calculation type for condition
 g_krech_item_4(4) TYPE c, " Calculation type for condition
 g_krech_item_5(4) TYPE c, " Calculation type for condition
 g_krech_item_6(4) TYPE c, " Calculation type for condition
 g_krech_item_7(4) TYPE c, " Calculation type for condition
 g_krech_item_8(4) TYPE c, " Calculation type for condition
 g_krech_item_9(4) TYPE c, " Calculation type for condition
 g_krech_item_10(4) TYPE c, " Calculation type for condition
 g_krech_item_11(4) TYPE c, " Calculation type for condition
 g_krech_item_12(4) TYPE c, " Calculation type for condition
 g_krech_item_13(4) TYPE c, " Calculation type for condition
 g_krech_item_14(4) TYPE c, " Calculation type for condition
 g_krech_item_15(4) TYPE c, " Calculation type for condition
 g_krech_item_16(4) TYPE c. " Calculation type for condition
data: it_t685a type standard table of ty_t685a.
data: wa_bapi_header type bapisdhd1,
 wa_bapi_headerx TYPE bapisdhd1x,
 it_bapi_item type table of bapisditm,
 it_bapi_itemx TYPE TABLE OF bapisditmx,
 it_bapi_cond type table of bapicond,
 it_bapi_condx TYPE TABLE OF bapicondx,
 it_bapi_partner type table of bapiparnr,
 it_bapi_shdl type table of bapischdl,
 it_bapi_shdlx TYPE TABLE OF bapischdlx,
 it_bapi_order_text type TABLE OF BAPISDTEXT,
 it_bapireturn type table of bapiret2.
data: wa_bapi_item like line of it_bapi_item,
 wa_bapi_itemx LIKE LINE OF it_bapi_itemx,
 wa_bapi_cond like line of it_bapi_cond,
 wa_bapi_condx LIKE LINE OF it_bapi_condx,
 wa_bapi_partner like line of it_bapi_partner,
 wa_bapi_shdl like line of it_bapi_shdl,
 wa_bapi_shdlx LIKE LINE OF it_bapi_shdlx,
 wa_bapi_order_text like LINE OF it_bapi_order_text,
 wa_bapireturn like line of it_bapireturn.
*DATA: zmode(1) VALUE 'N'.
data: it_header type standard table of ty_header.
*DATA: it_temp_header TYPE STANDARD TABLE OF ty_header.
data: it_item type standard table of ty_item.
*DATA: it_temp_item TYPE STANDARD TABLE OF ty_item.
data: it_err type standard table of ty_err.
data: it_fline1 type standard table of tline,
 wa_fline1 type tline.
data: it_thead1 type thead.
data: it_fline2 type standard table of tline,
 wa_fline2 type tline.
data: it_thead2 type thead.
data: it_fline3 type standard table of tline,
 wa_fline3 type tline.
data: it_thead3 type thead.
data: it_fline4 type standard table of tline,
 wa_fline4 type tline.
data: it_thead4 type thead.
data: it_fline5 type standard table of tline,
 wa_fline5 type tline.
data: it_thead5 type thead.
data: wa_header like line of it_header,
 wa_item like line of it_item,
 wa_err type ty_err,
 wa_bill LIKE LINE OF it_bill,
 wa_bill1 LIKE LINE OF it_bill,
 wa_iterr like line of it_err,
 wa_t685a like line of it_t685a.
 wa_bill_item TYPE ty_bill_item.
data: it_schedule_line type standard table of ty_schedule_line,
 wa_schedule_line type ty_schedule_line.
data: sales_order_no type bapivbeln-vbeln.
data: ext_sales_order_no type bapivbeln-vbeln.
Variable to be used to separate the fields which are concatenated by a
runtime character
*DATA: g_tabchar(1) TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.
*DATA: wa_truxs_t_text_data TYPE truxs_t_text_data.
*DATA: g_filename TYPE string,
 g_path TYPE string,
 g_fullpath TYPE string,
 g_user_action TYPE i,
 g_file_encoding TYPE abap_encoding.
*DATA : g_text(8192),
data : g_mstring1(100) type c,
 g_mstring2(100) type c,
 g_mstring3(100) type c,
 g_mstring4(100) type c,
 g_mstring5(100) type c.
data: g_count1 type ebelp,
 g_str_count1(6) type c.
data: g_count type ebelp,
 g_str_count(6) type c.
*DATA: f_subrc LIKE sy-subrc,
 f_subrc1 LIKE sy-subrc,
 f_error(500) TYPE c,
 item1(27) TYPE c,
 item2(27) TYPE c,
 item3(27) TYPE c,
 item4(27) TYPE c,
 i TYPE ekpo-ebelp.
*DATA: g_billplan_header TYPE c,
 g_billplan_item TYPE c.
data : g_external_so type vbak-vbeln. "SO
 SELECTION-SCREEN
selection-screen begin of block frame1 with frame title text-001 .
parameters:p_file1 type rlgrap-filename, "OBLIGATORY, "Header data.
 p_file2 type rlgrap-filename, "OBLIGATORY, "Item Data.
 p_file3 type rlgrap-filename, "Schedule line.
 p_file4 type rlgrap-filename ."OBLIGATORY. "Error file.
selection-screen end of block frame1.
start-of-selection.
wa_bapi_header-doc_type = 'Z0MX'. "order type
wa_bapi_header-sales_org = '0130'."sales org
wa_bapi_header-distr_chan = '13'. "distr channel
wa_bapi_header-division = '13'. "division
Old code from copied program
wa_bapi_header-purch_no_s = wa_header-kunnr_2. " Ship to party
New code as required in Finland project
We are using to Header ->Order Tab -> Ship to Party -> Purchase order no (BSTKD_E) to store Old legacy SO number
wa_bapi_header-purch_no_s = 'MX100443'. "External SO i.e Old legacey SO number
wa_bapi_header-ref_1_s = '0000666666'. "Sold to party
wa_bapi_header-ord_reason = wa_header-augru.
wa_bapi_header-purch_no_c = 'ddr1234'. " PO number
wa_bapi_header-purch_date = sy-datum. " PO date
wa_bapi_header-req_date_h = sy-datum. " Required Delivery Date
wa_bapi_header-pmnttrms = '01'. " Payment Terms
wa_bapi_header-incoterms1 = wa_header-inco1.
wa_bapi_header-incoterms2 = wa_header-inco2.
wa_bapi_header-price_date = wa_header-prsdt. " Pricing date
wa_bapi_header-currency = wa_header-waerk. " Document Currency
wa_bapi_header-sales_grp = wa_header-vkgrp. " Sales group
wa_bapi_header-price_list = wa_header-pltyp. " Price list type
wa_bapi_header-cust_group = wa_header-kdgrp. " Cust Group
wa_bapi_header-ship_type = wa_header-vsart. " Shipping Type
wa_bapi_header-purch_no_s = wa_header-bstkd_e. " Ship-to-party po number
wa_bapi_header-collect_no = wa_header-submi. " Collective No.
wa_bapi_header-name = wa_header-bname. " Name
wa_bapi_header-ref_1 = wa_header-ihrez. " Your Reference
wa_bapi_header-cust_grp1 = wa_header-kvgr1. " Industry
wa_bapi_header-cust_grp2 = wa_header-kvgr2. " Customer BU
*ENDFORM. " f_header
IF wa_header-partner_1 IS NOT INITIAL.
 wa_bapi_partner-partn_role = 'AG'.
 wa_bapi_partner-partn_numb = '0000666666'.
 wa_bapi_partner-itm_number = '000000'.
 append wa_bapi_partner to it_bapi_partner.
 clear wa_bapi_partner.
ENDIF.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
 exporting
 input = wa_header-partner_2
 importing
 output = wa_header-partner_2.
IF wa_header-partner_2 IS NOT INITIAL.
 wa_bapi_partner-partn_role = 'WE'.
 wa_bapi_partner-partn_numb = '0000666666'.
 wa_bapi_partner-itm_number = '000000'.
 append wa_bapi_partner to it_bapi_partner.
 clear wa_bapi_partner.
ENDIF.
perform f_item.
data : order_items_inx type table of bapisditmx with header line.
order_items_inx-material = 'X'. "
order_items_inx-target_qty = 'X'. "
order_items_inx-comp_quant = 'X'. "
order_items_inx-trgqty_den = 'X'.
order_items_inx-rnddlv_qty = 'X'.
order_items_inx-updateflag = 'I'.
order_items_inx-target_qu = 'X'.
order_items_inx-plant = 'X'. "
append order_items_inx.
call function 'BAPI_SALESORDER_CREATEFROMDAT2'
 exporting
 salesdocumentin = 'MX11111152'
order_header_in = wa_bapi_header
 order_header_inx = wa_bapi_headerx
importing
salesdocument = sales_order_no
tables
return = it_bapireturn
order_items_in = it_bapi_item
order_items_inx = order_items_inx
order_partners = it_bapi_partner
 order_conditions_in = it_bapi_cond.
if sy-subrc is initial.
commit work.
endif.
*& Form f_item
 text
form f_item .
call function 'CONVERSION_EXIT_ALPHA_INPUT'
 exporting
 input = wa_item-posnr
 importing
 output = wa_item-posnr.
wa_item-posnr = '000010'.
IF sy-subrc EQ 0. "IS INITIAL.
move wa_item-posnr to g_str_count."commented out by shakti
ENDIF.
wa_bapi_item-itm_number = wa_item-posnr. " Line item
WA_BAPI_ITEM-PO_ITM_NO = WA_ITEM-EBELP.
wa_bapi_item-division = wa_item-spart.
wa_bapi_item-purch_no_c = 'ddr1234'. " po number
wa_bapi_item-purch_date = sy-datum. " po date
wa_bapi_item-purch_no_s = 'MX11111112'. " Ship-to-party po number
wa_item-matnr = 'MAXIMO_SERVICE'.
call function 'CONVERSION_EXIT_MATN1_INPUT'
 exporting
 input = wa_item-matnr
 importing
 output = wa_item-matnr
 exceptions
 length_error = 1
 others = 2.
if sy-subrc is initial.
 wa_bapi_item-material = wa_item-matnr. "material
endif.
wa_bapi_item-target_qty = '1'. " Order qty
wa_bapi_item-comp_quant = '1'.
wa_bapi_item-target_qu = 'EA'.
 wa_bapi_item-fixed_quan = '1'.
wa_bapi_item-comp_quant = wa_item-kwmeng.
wa_bapi_item-trgqty_den = '1'.
wa_bapi_item-rnddlv_qty = wa_item-kwmeng.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = wa_item-ps_psp_pnr
 IMPORTING
 output = wa_item-ps_psp_pnr.
IF sy-subrc = 0.
 wa_bapi_item-wbs_elem = wa_item-ps_psp_pnr.
ENDIF.
wa_bapi_item-item_categ = 'ZMAX'.
wa_bapi_item-ex_rate_fi = wa_item-kurrf.
wa_bapi_item-dli_profil = wa_item-ffprf. " Dynamic item processor profile
wa_bapi_item-route = wa_item-route. " route
wa_bapi_item-exchg_rate = wa_item-kursk.
wa_bapi_item-plant = '2090'. " Plant
wa_bapi_item-ship_point = 'FN11'. " Shipping point
wa_bapi_item-store_loc = wa_item-lgort. " stg loc
REPLACE ALL OCCURRENCES OF ',' IN wa_item-ntgew WITH '.'.
REPLACE ALL OCCURRENCES OF ',' IN wa_item-brgew WITH '.'.
wa_bapi_item-net_weight = wa_item-ntgew. "
wa_bapi_item-gross_wght = wa_item-brgew. "
call function 'CONVERSION_EXIT_CUNIT_INPUT'
 exporting
 input = wa_item-gewei
 language = sy-langu
 importing
 output = wa_item-gewei.
 EXCEPTIONS
 unit_not_found = 1
 OTHERS = 2.
IF sy-subrc <> 0.
ENDIF.
wa_bapi_item-untof_wght = 'KG'. " weight unit
replace all occurrences of ',' in wa_item-kursk with '.'.
replace all occurrences of ',' in wa_item-kurrf with '.'.
wa_bapi_item-profit_ctr = wa_item-prctr. " Profit center
wa_bapi_item-resanalkey = wa_item-abgrs. " RESULT ANALYSIS KEY
wa_bapi_item-cstg_sheet = wa_item-kalsm_k. " COSTING SHEET
append wa_bapi_item to it_bapi_item.
endform. " f_item
Thanks & regards,
Chetan

see the following to create sales order:-
*& Report ZSALESORDER
*&DEVELOPED BY JANI KRUPA 4.10.2008
REPORT ZSALESORDER.
Parameters
Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
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.
DATA: lt_schedules_ink TYPE STANDARD TABLE OF bapisdhead1
 WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
 header-COMPL_DLV = p_autlf.
 header-COMPL_DLV = 'X'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant = p_plant.
itemx-plant = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant = p_plant.
itemx-plant = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = '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.
Fill schedule lines
lt_schedules_in-itm_number = '000020'.
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 = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
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 the work.
 COMMIT WORK AND WAIT.
 WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.

Freight Carrier missing while creating sales order using BAPI

Hi All,
I am using BAPI BAPI_SALESORDER_CREATEFROMDAT2 to create sales order. At header level, I am passing sold-to-party,ship-to-party and Freight Carrier fields as partners.
When the sales order is created it is creating partners sold-to-party,ship-to-party but freight carrier is missing in the partners.
To partners inernal table, I am passing the partner role and partner number as following:
      int_partners-PARTN_ROLE = 'AG'.
      int_partners-PARTN_NUMB = int_order-kunnr.
      append int_partners.
      clear int_partners.
        int_partners-PARTN_ROLE = 'FC'. "Frieght carrier
        int_partners-PARTN_NUMB = int_order-kunnr2.
        append int_partners.
        clear int_partners.
      int_partners-PARTN_ROLE = 'WE'.
      int_partners-PARTN_NUMB = int_order-kunnr1.
      int_partners-NAME       = int_order-name1.
      int_partners-NAME_2     = int_order-name2.
      int_partners-STREET     = int_order-street.
      int_partners-POSTL_CODE = int_order-post_code1.
      int_partners-COUNTRY    = int_order-country.
      int_partners-CITY       = int_order-city1.
      int_partners-REGION     = int_order-region.
      int_partners-TRANSPZONE = int_order-transpzone.
      int_partners-TAXJURCODE = int_order-taxcode.
      int_partners-district   = int_order-city2.
      append int_partners.
      clear int_partners.
Freight Carrier is set up as a "Vendor" instead of Customer in our system.
If anyone has solution to pass "Freight Carrier" through BAPI, please let me know.
Thanks,
Sonali.

For Vendor (Freight carrier) , I checked the master data and it has partner function defined as VN (vendor).
I have another issue with the salesorder create BAPI:
I am getting error
"E - 000010 : Condition rate does not agree with init. indicator for condition PR00"
when I am updating the PR00 condition value with '0.0' .
Please advice if anyone has any idea.
Thanks,
Sonali.
Thanks,
Sonali.

Problem in creating Sales Order

Hi All,
We have 3 Document types ZS01,ZS02 and ZS03 for creating Sales Order. We have written one program to create Sales Order for document type 'ZS01'.
Our requirement is ,we should allow to create sales order of doc.type ZS01 thru that 'z' program only,we should not use ZS01 type to create sales order via VA01.So, we have restricted sales order creation using 'ZS01' thr' VA01 by authorisation profile.So in my 'z' program i couldn't call VA01 to create sales order.So I tried using BAPI,it is giving me the error "No maintenance authorization for document type ZS01".
Please guide or suggest me some alternative method to create sales order.
Thanks & Regards,
Sudipto.

Hi Sudipto,
There is no direct method of by passing a role, but u can try creating sales order thru FM BAPI_SALESORDER_CREATEFROMDAT2 with reference to a SO that is already created with ZSO1, or you might call the Z report program internally from ur program to create the SO.
Hope that helps
Anirban

How to create sales order using bapi( test purpose)

Hi all,
       while i was creating sales order using the BAPI_SALESORDER_CREATEFROMDAT1 it is giving some error,
version 0 is not defined for the fiscal year ****.
I have given the fallowing parameters as input
ORDER_HEADER_IN
     DOC_TYPE     OR
                SALES_ORG 1000
     DISTR_CHAN 10
                DIVISION         00
ORDER_PATNERS
     PARTN_ROLE     SP
     PARTN_NUMB     1000
ORDER_ITEMSIN
     MATERIAL     M-13
I need to create sample sales order . Please help me how to create sales order with an example( for test purpose).
Regards
Deviprasad.

Hi Prasad,
Try using BAPI_SALESORDER_CREATEFROMDAT2.
While creating sales order using FM: BAPI_SALESORDER_CREATEFROMDAT2, please make sure ORDER_ITEMS_IN, ORDER_ITEMS_INX, ORDER_SCHEDULES_IN, ORDER_SCHEDULES_INX.
Pricing Conditions will not be mandatory to create a sales order via BAPI.
As you were saying, you can create a sales order but not with items. Do populate the internal tables that i have specified above.
Also try to pass the item number internally, this will help you in identifying the schedule lines.
Regards,
Priyanka.

Avoid substitute material.., while creating sales order with BAPI?

Hi experts.
I use BAPI_SALESDOCU_CREATEFROMDATA1 function module to create a sales order.
Material A has a substitute material B with substitute reason 0005.
So if I use material A when creating sales order with above BAPI function, the order is created with material B.
I don't want to substitute the material automatically. I want to create the sales order with material A.
What should I do? Help me please.
Thanks in Advance.

Hi bvrn Reddy,
I know, your message is almost two years old, but, did you find a solution? I'm facing the same problem. The material A has B as substitute, but in va01 a popup appears (its customizing inside the substitution reason, strategy = A). Of course, we have no popup inside the bapi, but there must be a way to decide which material the bapi should use. At the moment I only get the substitute, never the old mat (even there is something in stock).
Maybe you've got a helpful hint for me, thanks!
Ben

Inbound Files Create Sales Order

Dear All,
I am working one Assignments For Sales Order Creation Through Inbound Files and Its working fine.
But I have one Issue during creation of Sales Order through inbound files ( Which Contains Quotation Number Which Already Exist in SAP ) and Quotation Number updated in PO Number (BSTKD) filed in Sales Order.
And My Problem is How we can update Quotation in Document Flow during creation of Sales Order through inbound files..
Any Help or Suggestion will very helpful for me.
Thanx in Advance.
Regards
Vijay Maurya

HI Vijay,
Could you please let me know, how are you processing the file to make sales order. In other words are you using BDC or something else for creating sales order.
If you are using a BDC to create sales order, you need to re-record it so that the sales order is created in reference to the quotation. In this way, the sales order will automatically get linked to sales order. And all the document flows will be updated, also the issues of pricing, delivery date will also be perfectly copied.
Also since the SAP will update the tables on its own, hence you will not need to direct update any table in SAP.
Hope this helps,
Abhishek
Edited by: Abhishek Purwar on Nov 20, 2008 9:11 PM

Free Goods Problem and User Exit if needed in Sales Order

Hello All,
The problem is related to Free Goods in Sales Order which is given with an example -
We have maintained Free Goods ( T Code - VBN1) in inclusive scenario which is as follows -
For 210 PAC (Pack) of Material A 18 PAC Free.
Where 1 PAC = 20 BT (Bottle) and 20 PAC = 1 CV (Case Pack)
In the material master of Material A the Base Unit Of Measurement (UOM) = PAC and Sales UOM = Blank so that we can use any conversion factor maintained for the material.
The conversion factors maintained for Material A are as follows -
1 BT = 1BT
1 PAC = 20 BT
1 CV = 20 PAC
Now when we are raising sales order for 11 CV the free goods are not generated in the Sale Order.
Again if we maintain the Sales UOM in CV and raise the sales order it is showing :
10 CV as main item and 1 CV as Free which is wrong because in the conversion factor we have already maintained 1CV = 20 PAC , Whereas in the inclusive scenario it is given 11CV = 210 PAC and 210 PAC = 18 PAC is free.So in any case it is taking into account 2 more PACs.
Please suggest what need to be done in this case in respect of User Exit or Source Code in ABAP if needed.
Thanks & Regards
Priyanka Mitra

Hello Priyanka Mitra,
We are facing a problem same as you.
How did you solve this problem?
We are very glad if you teach it concretely.
Please advise your solution to us.
Thanks.

Minimum mandatry fields for Creating Sales Order

Hi All,
I am going to create sales order using BAPI_SALESORDER_CREATEFROMDAT2 in the web dynpro for java,
I want to use minimum fields, so, what are the minimum fields for creating sales order ?.
if u have any documents or links realted to this please send me.
please help me out.
Thanks & regards,
Iqbal Ahmad

chk it
EXPORTING
SALESDOCUMENTIN =
ORDER_HEADER_IN = l_order_header
ORDER_HEADER_INX =
SENDER =
BINARY_RELATIONSHIPTYPE =
INT_NUMBER_ASSIGNMENT =
BEHAVE_WHEN_ERROR =
LOGIC_SWITCH =
TESTRUN =
CONVERT = ' '
IMPORTING
SALESDOCUMENT = l_salesdocument
TABLES
RETURN = it_return
ORDER_ITEMS_IN = it_order_items
ORDER_ITEMS_INX =
ORDER_PARTNERS = it_order_partners
ORDER_SCHEDULES_IN = it_order_schdl
ORDER_SCHEDULES_INX =
ORDER_CONDITIONS_IN = it_order_conditions
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
How to create sales order using bapi( test purpose)
Create Sales Order using BAPI
creating sales order using bapi

Create Sales Order for Repair

Hi All,
I want to create a Repair Sales Order using BAPI 'BAPI_SALESORDER_CREATEFROMDAT2'.
When I create the order using tcode VA01 it asks me to enter Material, Servicable Material and the Repair Information.
How can I pass the Servicable Material and the Repair Information to the above BAPI.
Any help will be appreciated.
Regards,
Shubham

Hi
Please refer to the following documentation.
Method
SalesOrder.CreateFromDat2
Sales order: Create Sales Order
Functionality
You can use this method to create sales orders.
You must enter at least sales order header data (via ORDER_HEADER_IN structure) and partner data (via the ORDER_PARTNERS table) as input parameters.
Enter the item data via the ORDER_ITEMS_IN table. You can allocate item numbers manually, by filling in the relevant fields, or the system does it, according to the settings for Customizing, by leaving the relevant fields blank.
If you have configurable items, you must enter the configuration data in the ORDER_CFGS_REF, ORDER_CFGS_INST, ORDER_CFGS_PART_OF and ORDER_CFGS_VALUE tables.
Credit cards can be transferred via the BAPICCARD structure, on the one hand, data for card identification, on the other, data for a transaction which has taken place in an external system.
Once you have created the sales order successfully, you will receive the document number (SALESDOCUMENT field). Any errors that may occur will be announced via the RETURN parameter.
If no sales area has been created in the sales order header, then the system creates the sales area from the sold-to party or ship-to party, who has been entered in the partner table. If a clear sales area cannot be created, you will receive a system message, and the sales order will not be created.
Notes
Mandatory entries:
ORDER_HEADER_IN : DOC_TYPE Sales document type
SALES_ORG Sales organization
DISTR_CHAN Distribution channel
DIVISION Division
ORDER_PARTNERS..: PARTN_ROLE Partner role, SP sold-to party
PARTN_NUMB Customer number
ORDER_ITEMS_IN..: MATERIAL Material number
Ship-to party:
If no ship-to party is entered, use the following: Ship-to party =
sold-to party.
Commit control:
The BAPI does not have a database commit. This means that the relevant application must leave the commit, in order that can be carried out on on the database. The BAPI BAPI_TRANSACTION_COMMIT is available for this.
German key words:
The following key words must be entered in German, independantly of
the logon language:
DOC_TYPE Sales document type, for example: TA for standard order
PARTN_ROLE Partner role, for example: WE for ship-to party
Further Information
You can find further information in the OSS. The note 93091 contains general information on the BAPIs in SD.
Regards
Inder

Sap Fiori - Create Sales Order in Offline

Hello,
It is possible to use SAP Fiori for creating Sales Order in Offline mode?
Thank you,

Hi Michely,
It is possible if you convert your Fiori web app to a hybrid app. You have to create a Cordova based hybrid app and use offline Kapsel plugins that comes with SAP Mobile Platform (Getting Started with Kapsel - Offline OData))
Out of the box Fiori doesn't have offline features, we are expecting it in the future.
Regards,Midhun
SAP Technology RIG

Creating sales order with reference to contracts

Hi Gurus,
I am creating a sales order with reference to a contract.I am making sales order sold-to-party as release order.
so my Contract sold-to-party and the sales order sold-to-party are different but both belong to same sales area. In the above case i am able to create sales order.
In other case though my Contract sold-to-party and the sales order sold-to-party are different but if they both belong to different sales area, i am unable to create a sales order.It says no contracts exits for sold-to-party.
i made both the customers as partners .
Any guidance on this is fully rewarded with points.

Each and everytime your both SOLD-TO should be in same sales area.
Enhance the Contract sold-to-party's customers sales area specific data in XD02 so, it could come in to sales area of the Order's Sold-to-party.
Regards,
Naimesh Patel

Creating a sales order via lsmw.

Hi,
I am creating sales orders via lsmw. Each of these sales orders may contain any number of line items, i.e. sales order 1 might have 3 line items and the next sales order may have 10.
How do I cater for this in lsmw. Is there a way of saying: when last line item, then start next sales order record?
Any help appreciated.
Regards,
Warren.

HI, I create LSMW for sales order. It is working fine for 9 line items. IF more than 9 line item, other item is not updating. Pls provide me a solution. Thanks in Advance.
my email is [email protected]

Creating sales order with BAPI_SALESORDER_CREATEFROMDAT2

Hi,
I´m creating sale orders with the function BAPI_SALESORDER_CREATEFROMDAT2. If you create sales order manually over the transaction, the system will find the right delivery date for you, if you are typing a date too early, for example.
The same I need to do the BAPI. But if I´m running the BAPI without a date, it is creating a sales order without a BAPI.
How can I get the date, SAP finds out automatically, when creating sales orders over the transaction?
Thank you!

Really no advices to that?

The problem in using object = 0090 to create sales order in LSMW?

Similar Messages

Maybe you are looking for