Creating Sales Order referring a contract using RFC_SDCONOIL_CREATEFROMDATA

Hi,
Which field is to be populated with the Contract number and the item number so as to get the same in the item details of the sales order created from the contract?

Hi,
Function module comes with adequate documentation..Please check.
Rgds,
Harikrishna

Similar Messages

Issue in creating sales order with ref contract(quantity)

hi friends,
I am creating sales order with reference contract using
"BAPI_SALESORDER_CREATEFROMDAT1"
my issue is with quantity field when i am entering quantity as 1 then it is taking as 0.001
i am also declaring its unit field too but there is no change.
in my program i am taking quantity as parameter.
field description is like this Order qty in sales units - 00009001 corresponds to 9.001
is there any chance of changing the quantity .
please help.

There is another similar post...look at those comments. Consider the data types in use...in true numeric fields with decimals, the decimal is implied, so look at how you're sending and/or converting any value.... For instance, if I were sending data to a quantity field described as curr 15, decimals 3, I would expect that I needed to send 1.000 (or perhaps 1000, depending on my testing) in the input to get a quantity of 1.

Creating Sales Order with credit card using Process Order API

Hi All,
When trying to create sales order with payment type as Credit card using Order data storing into staging tables and then calling Order Import Concurrent Program. The order is being created in ENTERED state.
While trying to passing the same details to Process Order API to create Sales Order, we are getting following error:
Unable to set up a Credit Card Bank Account for the Customer.
Credit Card information on the order is not valid.
Why getting this error while using Process Order API.
Regards,
KANN.

When using the API, are you trying to create the order as booked using the booked flag or the book action? I would recommend using the action if you are not. To troubleshoot, I would try the API without booking and then use the following article to determine the issue:
Unable To Setup A Credit Card Bank Account For The Customer. CC Information On The Order Is Not Valid (Doc ID 1450936.1)

Create Sales Order with type "return" using API

Dears ,
I tried to create a sales order with type Return using oe_order_pub.process_order but the order is not created .
There is no error msg returned .
Can anyone help me to solve this .?

Hi 2800842
Please use the following link for your issue;
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=539354996395765&parent=DOCUMENT&sourceId=746787.1&id=292…
or visit metalink: How to create an RMA via Process Order API ? (Doc ID 292743.1)
Thanks
Mirza Tanzeel

Creating Sales Orders from Quantity Contract - ORDERS05 IDOC

Hi,
I have created a Quantity Contract in ECC. Now I want sales orders to be created w.r.t to the Contract through ORDERS05.
Can anyone suggest which IDOC Segment and Qualf i have to populate to achive the same.
Also say once I am able to achive the creation of Release Orders from the Contract through ORDERS05. If I surpass the Qty of the Contract . The IDOC should be have a field for notifying the same.
REgards,
BInayak

Hello Binayak
You may use the following segment and fields for reference data:
Segment: E2EDK02
Fields:
QUALF : IDOC qualifier reference document - I think for contracts this is '001'.
BELNR : IDOC document number
POSNR : Item number
As per a flag to indicate that the contract quantity is surpassed, I doubt there will be anything like that becasue is an Idoc is before you created the order and how will the system know you have surpassed until an order is entered?
I think you need to use 'completion rule' and copy control 'update document flow' features to work on this.
Hope this helps.

Create Sales Order with Contract Accounts Receivable and Payable Set

I have successfully created a Sales Order using BAPI BAPI_SALESORDER_CREATEFROMDAT2. Then, I need to set value to Contract Accounts Receivable and Payable in the Sales Order Header Data (Goto -> Header -> Accounting).
How do I do that? Can I assign a value to Contract Accounts during creation of Sales Order using BAPI BAPI_SALESORDER_CREATEFROMDAT2?

Hi Andrew Tan,
iam trying to creats sales order but i cannot able to creats sales order.
I had used BAPI_SALESORDER_CREATEFROMDAT2 to create
iam getting an message as
SALES_HEADER_IN has been processed successfully
SALES_ITEM_IN has been processed successfully
Order receipt/delivery not possible, credit customer blocked
help me out of this problem
Pleases send me the code for this creation.
Waiting for your reply.
Thanks,
sayyed.

Create CRM sales Order based on contracts

Hi Experts,
Could you please guide me how to create sales order based on contract from CRM 5.0? What are customizing settings and coding to be in CRM to enable this?
The requirement is to display the list of sales contracts of type A&B from R3 to CRM system. If the customer selects contract type A, sales order X should be created from CRM. If the customers select contract type B, sales order Y should be created from CRM. Also, if the order is created based on Contract, will the document flow will be mapped to contract etc.
Regards,
Ronit

Start here with this SAP Help documentation.
[Contract processing in CRM Web Channel|http://help.sap.com/saphelp_crm52sp01/helpdata/EN/d2/650e26a21fe04bba5298afd089b9dd/content.htm] - link.
You can either create the contracts in CRM or download it from your ECC backend using middleware.
The scenario and especially the user interface is predefined in the application. Contract Item selection and transfer to basket is provided in the Catalog and not directly in the basket. Most customers want the contract item selection from the basket, and this will be an enhancement.
If you want the UI navigation to match what happens in SAPGUI will require custom development.

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.

Error in Creating Sales Order Using BAPI_SALESORDER_CREATEFROMDAT2

Hi Everyone,
We have a requirement to create sales order from flat file using BAPI. Everything was working well until we encounter a customer with credit control limit setup.
Using the partners table for BAPi, the sold to customer is enter at header level, and we have this requirement to add the payer at item level. This is where the error is occuring. Upon debugging, I found out that the customer has a credit limit setup at FD33, and has a record found in KNKK, which is giving the error "Credit limit customer differs from credit limit customer in header".
However, duting manual creation of sales order via VA01, this error is not encountered.
Any ideas or suggesstions on how we can move forward with SO creation using BAPI with customers where credit management is setup?
Thanks,
Louisse

If thats not working..
try BAPI_SALESORDER_CREATEFROMDAT2
If BAPI is not working. try creating a bdc for the same if there's not error on trying from VA01

Problem with BOM Quant while creating Sales order with reference using BAPI

Dear All,
I am facing problem with creating a slaes order with reference to other sales order by using BAPI_SALESORDER_CREATEFROMDAT2 .
Sales order is getting created but
1. It exploding the BOM means the line items which are not there in the reference SO also coming in the new SO ( all BOM items are coming )
2. Schedule line for BOM header item is getting copied to all sub items of BOM.
Can any one help me out to prevent the above deviations in creating Sales order with reference by using BAPI_SALESORDER_CREATEFROMDAT2.
Note: while passing the parameters to BAPI_SALESORDER_CREATEFROMDAT2
all the data related to items is exactly the same as in the original Sales Order.
Thanks in advnace.
Regards,
John

Hi All,
Can any one help me !!!!!!!!!!
please

Error while creating Sales Order Through BAPI

Hi Friends,
i am creating a RFC where i have to create sales order .
I am using bapi
BAPI_SALESORDER_CREATEFROMDAT2
for same and entering values to it.
I got the following return messages:
S V4                   233 SALES_HEADER_IN has been processed successfully
S V4                   233 SALES_ITEM_IN has been processed successfully
S V1                   311 BDN Order 3112800903 has been saved
But when I go to transaction VA03 and enter the number i get the following error:
SD document 3112800903 is not in the database or has been archived
Can any one know how to resolve this error.I am also using BAPI_TRANSACTION_COMMIT with wait = 'X'.
Regards,
Santosh Alle

Hi,
Try to check the return message once.
SD document 3112800903 is not in the database or has been archived
You will get this message if the sales document is deleted from the database .The BAPI   'BAPI_SALESORDER_CHANGE' is used to delete salesorder.Check whether anyone has deleted it
Also, sometimes it may take few seconds to update the sales order in the database when using BAPI. Check the transaction after some time.
Regards,
Lakshman.
Edited by: Lakshman N on May 14, 2010 7:43 AM

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

Sales order from Service Contract?

Dear SD Guru,
Can I created Sales Order from Service Contract? I would like to create a sales order from service contract (MV) and I need to generate billing from the sales order. MV-> OR-> F2. No Resource Related Billing involved.
Thanks,
Soo

Hi,
I think this can be achieved, if you do copy control from order to order in VTAA.
Thanks
Krishna.

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

Setting user specific contract data while creating sales order using BAPI

Hi all,
I am creating sales order using BAPI - BAPI_SALESORDER_CREATEFROMDAT2.
Now my problem is that there is no structure for contract data (i.e. VEDA), system automatically set contract data using customization values.
I am doing some validations on cotract data in MV45AFZZ which fails, because these validations are performed on standard values, user specific values r not set.
How to handle this issue, your small clue may help a lot.
Regards,
S@meer

HI
Pricing will be carried basing on the pricing
procedure.
Case1: Prices will be carried out automatically if
necessary condition records are maintained for the
condition type.
For this you can go to Sales Order-> Item Conditions
In the screen you can click on command button Analysis,
which gives you the list of condition types associated
to the pricing procedure. By clicking on the condition
type you can know the action that has taken place.
Case2: Manually forcing prices for Items.
To do this, you have to populate ORDER_CONDITIONS_IN &
ORDER_CONDITIONS_INX. Also note to identify the item
numbers, you manually pass the item number for each item
in the sales order, use the same item number for
populating conditions.
Parameters required:
ORDER_CONDITIONS_IN:
ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
ORDER_CONDITIONS_INX:
ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
Hope the above info helps you. Do revert back if you
need more info.
Kind Regards
Eswar

Creating Sales Order referring a contract using RFC_SDCONOIL_CREATEFROMDATA

Similar Messages

Maybe you are looking for