Unable to create sales Order/Inquiry object using SAP JCo

Hi All,
Pls can you help me.
I am using BAPI_INQUIRY_CREATEFROMDATA2 and BAPI_Trancation_commit to create Inquiry object.From my Client JCo code there is no error.I debugged the BAPI_Trasaction_commit, there is no error, return code is 0. But th system is not creating Inquiry object. When I try the same from SAP GUI client with exactly the same input parameters it works.
Do I need to set any option/value to commit the Inquiry to the SAP database? How to maintain the same session between the different BAPI's. Is there any issue with Session maintainance? I would appreciate if you can provide me any sample SAP JCo code for creating a Sales Order/Inquiry.
Thanks
mars

Can you put the part of your code that fill the ORDER_PARTNERS table, also you could compare your coding with [Sales order creation using BAPI|http://wiki.sdn.sap.com/wiki/display/Snippets/SalesordercreationusingBAPI] in [Community Code Gallery |http://wiki.sdn.sap.com/wiki/display/Snippets/CommunityCodeGallery] (don't forget that there is a conversion exit on the partner role, so use internal codes "AG" and "WE")
Regards,
Raymond

Similar Messages

Error while creating sales order with ref using SD_SALESDOCUMENT_CREATE

Hi
I am creating sales order with reference using function module SD_SALESDOCUMENT_CREATE , while creating i am getting error
Document doesn't have document category even thougth i am passing document category in header as well as item lavel.
In VBUK table there is no value for VGTYP.
Can you please help me how to resolve it.
Thanks & regards
kiran

Problem resolved by passing REFDOC_CAT in the FM along with SD_DOC_CAT.
Thanks

ERROR IN CREATING SALES ORDER INQUIRY

Hi,
I am getting the error "Schedule line Category AT is not defined" while creating Item level details in Sales order Inquiry. Please Help....

Hi Sudhanshu
                       Please make sure these settings are done.
The schedule line category controls whether schedule lines in delivery schedules are relevant for planning and/or delivery. The system determines this category on the basis of the planning indicator in the forecast delivery schedule, then in the just-in-time (JIT) delivery schedule.
To configure schedule line categories for scheduling agreements, choose Sales ® Sales Documents Schedule lines Define or Assign schedule line categories in Customizing for Sales and Distribution.
For scheduling agreements with delivery schedules, you must assign at least four schedule line categories to combinations of item category and requirement planning type:
·        The basic schedule line category (field SchLC) is relevant for planning and delivery
·        The alternative schedule line category (field 1 MSLCa) is relevant for planning, not delivery
·        The alternative schedule line category (field 2 MSLCa) is relevant for delivery, but not planning
·        The alternative schedule line category (field 3 MSLCa) is not relevant for planning or delivery
When you have made these assignments, all possible combinations are covered during automatic determination. If any are missing, the system will not be able find the appropriate schedule line category and will generate an error message.
The SAP System contains the following schedule line categories for component suppliers:
·        L1, BN, L2, and CN for item category LZN
·        E4, E0, E5, and BN for item category LKN
·        L2 for item category LZMA (standard for delivery order processing)
Although the availability check is switched off in the standard system for these categories, the system may carry out a transfer of requirements for some of them. Even when the availability check is switched off, you must use an availability check group for all materials in scheduling agreements with delivery schedules. Otherwise, the system will not transfer requirements.
If the availability check is switched on and the transfer of requirements switched off for a schedule line type, the system will not take it into account!
Usefull: Please Reward Points
Thanks and Kind Regards
Mohan

Creating Sales order texts while using BDC session method is not working

Hi All,
I have an existing program which creates sales order using BDC session method.( Actual program uses BAPI to create sales order and in case if any error occurs during creation of sales order BDC session is generated so that user can process it later and i am facing issues in this part of code where it uses BDC)
I wanted to modify this BDC sesion to update the sales order text also. I tried recording VA01 for creationg sales order text unfortunatly it is not capturing the data i am entering in the text fields.
Please suggest if there is any way to create sales order using BDC.
Regards
Sheeba

Hi Madhu,
'=TP_CREATE' is the OK code i am getting for creating TEXTS. But the text entered are not captured in BDC.
Part of BDC program generated for cretaing sales order texts.
perform bdc_dynpro      using 'SAPMV45A' '4003'.
perform bdc_field       using 'BDC_OKCODE'
                              '=%_GC 128 22'.
perform bdc_field       using 'LV70T-SPRAS'
                              'EN'.
perform bdc_dynpro      using 'SAPMV45A' '4003'.
perform bdc_field       using 'BDC_OKCODE'
                              '=TP_CREATE'.
perform bdc_field       using 'LV70T-SPRAS'
                              'EN'.
perform bdc_dynpro      using 'SAPMV45A' '4003'.
perform bdc_field       using 'BDC_OKCODE'
                              '=%_GC 128 22'.
perform bdc_field       using 'LV70T-SPRAS'
                              'EN'.
perform bdc_dynpro      using 'SAPMV45A' '4003'.
perform bdc_field       using 'BDC_OKCODE'
                              '=TP_CREATE'.
perform bdc_field       using 'LV70T-SPRAS'
                              'EN'.
perform bdc_dynpro      using 'SAPMV45A' '4003'.
perform bdc_field       using 'BDC_OKCODE'
                              '/EBACK'.
perform bdc_field       using 'LV70T-SPRAS'
                              'EN'.
perform bdc_dynpro      using 'SAPMV45A' '4001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=SICH'.
Regards,
Sheeba

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

Unable to create Sales order from "BAPI_SALESORDER_CREATEFROMDAT2" for Free Goods

Hi Experts,
I am facing the issue while creating the Sales order through "BAPI_SALESORDER_CREATEFROMDAT2" , all is going well in normal cases but when I process the contract with FREE GOODS line items for which free goods condition record is maintained it fails to create the Sales order. Is there any special treatment for this Free goods case. Is there any Flag to be passed from BAPI?
Regards,

Hi Paaavan
You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module SD_SALESDOCUMENT_CREATE to create sales documents with.
Regards,
Marius

How to create sales order using BAPI.

Hi all,
I am trying to create sales order using standard BAPI
"BAPI_SALESORDER_CREATEFROMDAT2". But, even I had entered all mandatory fields, I am unable to create sales order sucessfully.
I had gone through the documentaion of this BAPI and entered these fields.
These are the mandatory fields that which I had tried to create,
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
Do we have anymore fields to give as inputs? I am getting this error message as below :
Msg: Personal number 00007176 does not exit.
But, I am not giving any personal number manually. This personal number was having connection with partner role field,
I had reffered this from the VBPA (Sales Document: Partner Table). Now, please suggest me how to solve this?
Can anyone tell me how to solve this problem and create sales order sucessfully.
Thanks in advance,
Surender Batlanki.

hi surendra ,
chech with below code.
REPORT z_bapi_salesorder_create.
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 OBLIGATORY.
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.
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'.
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'.
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'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI 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.
let us know if you have any qauistions.
~linganna

Condion Type "VPRS" should not appear in Sales Order, Inquiry, Contract

Hi Gurus,
Normally when you create Sales Order/Inquiry/Contract, in the Condition Tab VPRS Condition Type will appear and show the cost price of Materail from the Material Master.
My Client requirement is, VPRS Condition type has to be calculated as "Statistical" Contion but IT SHOULD NOT APPEAR IN THE CONDITIONS TAB IN THE SALES ORDER/INQUIRY/CONTRACT.
Thanks,
Bala

hello, friend.
try sapnote 105621. this is about restricting view of condition types (i.e. vprs) in sales orders by creating anauthorization object for cond types..
i wish to discuss our experience with this, as we had the same business requirement.
first, we simply deleted vprs from the PP. this did not affect financial accounting, until the client decided to implement std cost estimates. we had to bring back vprs.
now, we did the sapnote, which required joint efforts among SD, ABAP and BASIS. although we were able to restrict view of vprs in the cond tabs at itm level, this was still visible at header level. also, a resourceful data encoder can always find ways to view the same in, for example, the document flow or materials movement data.
however, try this and maybe you will get it right.
regards.

Issue in creating Sales Order in CRM 7.0 IC WEB

Hello Experts,
I am working on CRM7 and ECC 6 integration. I have configured Sales Order ( transaction type ZOR) in CRM. Using GUI the sales order is properly created in CRM and getting replicated to ECC without any issues.
I started configuring IC web UI, systematically followed C04 and C78 and completed all the steps including IC_BT transaction profile customization but inspite of this I am unable to create sales order in IC web.
I am geting error "No transaction type available for creating transactions" and if I go into details of this error it shows a page as follows
Diagnosis
No transaction type is available when creating a transaction. This can be due to the following reasons:
u2022     No transaction type is available according to Customizing
u2022     The user has no authorization for the transaction type
System Response
It is not possible to create the transaction.
Procedure
Make sure that:
u2022     The transaction type is set up in Customizing
u2022     The user has authorization for the transaction type
I have checked everything , nothing seems to be wrong. Can anyone advice how to resolve this issue
Thanks and Regards
Ambar

goto IMG where you defined the ZOR. Select the ZOR and choose Channel on the left, is ICW Interaction Center Webclient a choice? or add it.
We noticed that once any transaction was set to an option, we had to set these for all transactions in the ICWC, ISA, Gui, etc.

Problem while creating SALES ORDER (OR)

Hi All,
I am unable to create sales order (OR)
Error : Material is not defined for sales areaI have created MMR and CMR Properly.
Please help.
Thanks In Advance
Regards
Abhi

Hi Abhi,
I face similar issue as faced by you.
I went to additional data and changed the description and added the description in which I wanted it to be added but does not help. Am I missing the right place where to make the change?
I am pretty sure that it is a language issue.
I created a sales order, added a product, it worked fine.
Now, I copied this product to a new product, changed description and added it in same sales order it does not work.
Best Regards,
Neha

Creating sale order by using BAPI

Hi,
My requirement is to create a inquiry(VA11), By using the Inquiry no as a input in report, i should create a salesorder using BAPI in which the datas should be flowed from inquiry to sale order. i did almost everything except the Pricing Condition.
I am fetching the pricing condition values from table KONV-KSCHL and passing the value via BAPI_SALESORDER_CREATEFROMDAT2 it creates saleorder. In the created salesorder, there are two same pricing conditions but different rate 1.) the price of the MATNR which is maintained 2.) the changed MATNR price in inquiry level,
i need the value which is changed in inquiry level that is 2nd value.
can anyone help me in this...

REPORT ZSALESORDER.
<< Cut and paste without attribution from
create sales order using BAPI
removed >>
Edited by: Rob Burbank on Feb 24, 2009 10:43 AM

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.

Unable to Configure Sales Order using SALESORDER_CREATEFROMDAT2

I am using the basic type SALESORDER_CREATEFROMDAT2 02 idoc, created via LSMW, in order to create sales orders. Everything works fine, except for the fact that I cannot set configuration characteristics. The sales order is saved, but when i look at it the value of my characteristic is not set. Can you help me please? Currently I do not know how to generate an idoc of this basic type from an existing order. Knowing how to do this would be a great help.
For my test data, I am only attempting to create one line item (line 10) and configure one characteristic.
Below is a list of the segments being used. I have provided the fields with code for those fields I believe are relevant.   I have attempted to process idocs with and without segment E1BPCUPRT. I have also processed idocs with and without the fields E1BPSDITM1-CONFIG_ID, E1BPSDITM1-INST_ID and E1BPSDITM1-MAT_EXT.   When these three fields are populated, the order is created but the order line items are dropped. When these three fields are not populated, the order lines created but the characteristic value is not passed to the line item.
Target Structures Used
E1SALESORDER_CREATEFROMDAT2 - Header Segment
    E1BPSDHD1 - Communication Fields: Sales and Distribution Document Header
    E1BPSDHD1X - Checkbox Fields for Sales and Distribution Document Header
    E1BPSDITM - Communication Fields: Sales and Distribution Document Item
      E1BPSDITM1 - Communication Fields: Sales and Distribution Document Item
E1BPSDITM1-CONFIG_ID
Rule Type: Constant
    E1BPSDITM1-CONFIG_ID = '000001'.
E1BPSDITM1-INST_ID
Rule Type: Constant
    E1BPSDITM1-INST_ID = '00000001'.
E1BPSDITM1-MAT_EXT
Rule Type: ABAP Code
        concatenate '0000000000000000000000' E1BPSDITM-MATERIAL into
     E1BPSDITM1-MAT_EXT.
    E1BPSDITMX - Communication Fields: Sales and Distribution Document Item
    E1BPPARNR - Communications Fields: SD Document Partner: WWW
    E1BPSCHDL - Communication Fields for Maintaining SD Doc. Schedule Lines
    E1BPSCHDLX - Checkbox List for Maintaining SD Document Schedule Line
    E1BPCOND - Communication Fields for Maintaining Conditions in the Order
    E1BPCONDX - Communication Fields for Maintaining Conditions in the Order
    E1BPCUCFG - CU: Configuration Data
E1BPCUCFG-POSEX <=== ORDER_ITEM-POSNR
Rule Type: Transfer (MOVE)
    E1BPCUCFG-POSEX = ORDER_ITEM-POSNR.
E1BPCUCFG-CONFIG_ID
Rule Type: Constant
    E1BPCUCFG-CONFIG_ID = '000001'.
E1BPCUCFG-ROOT_ID
Rule Type: Constant
    E1BPCUCFG-ROOT_ID = '00000001'.
E1BPCUCFG-COMPLETE
Rule Type: Constant
    E1BPCUCFG-COMPLETE = 'T'.
E1BPCUCFG-CONSISTENT
Rule Type: Constant
    E1BPCUCFG-CONSISTENT = 'T'.
    E1BPCUINS - Instances of Several Configurations
E1BPCUINS-CONFIG_ID
Rule Type: Constant
    E1BPCUINS-CONFIG_ID = '000001'.
E1BPCUINS-INST_ID
Rule Type: Constant
    E1BPCUINS-INST_ID = '00000001'.
E1BPCUINS-OBJ_TYPE
Rule Type: Constant
    E1BPCUINS-OBJ_TYPE = 'MARA'.
E1BPCUINS-CLASS_TYPE
Rule Type: Constant
    E1BPCUINS-CLASS_TYPE = '300'.
E1BPCUINS-OBJ_KEY
Rule Type: ABAP Code
    * Target Field: E1BPCUINS-OBJ_KEY Object key
    Select single SATNR from MARA into E1BPCUINS-OBJ_KEY
      where BISMT = ORDER_ITEM-BISMT.
E1BPCUINS-QUANTITY <=== ORDER_ITEM-KWMENG
Rule Type: Transfer (MOVE)
    E1BPCUINS-QUANTITY = ORDER_ITEM-KWMENG.
    E1BPCUPRT - Part_of Entries of Several Configurations (Have tried with and without this segment)
E1BPCUPRT-CONFIG_ID
Rule Type: Constant
    E1BPCUPRT-CONFIG_ID = '000001'.
E1BPCUPRT-PARENT_ID
Rule Type: Constant
    E1BPCUPRT-PARENT_ID = '00000001'.
E1BPCUPRT-INST_ID
Rule Type: Constant
    E1BPCUPRT-INST_ID = '00000001'.
E1BPCUPRT-PART_OF_NO
Rule Type: Constant
    E1BPCUPRT-PART_OF_NO = '0010'.
E1BPCUPRT-OBJ_TYPE
Rule Type: Constant
    E1BPCUPRT-OBJ_TYPE = 'MARA'.
E1BPCUPRT-CLASS_TYPE
Rule Type: Constant
    E1BPCUPRT-CLASS_TYPE = '300'.
E1BPCUPRT-OBJ_KEY
Rule Type: ABAP Code
    E1BPCUPRT-OBJ_KEY = E1BPCUINS-OBJ_KEY.
    E1BPCUVAL - Characteristic Values of Several Configurations
E1BPCUVAL-CONFIG_ID
Rule Type: Constant
    E1BPCUVAL-CONFIG_ID = '000001'.
E1BPCUVAL-INST_ID
Rule Type: Constant
    E1BPCUVAL-INST_ID = '00000001'.
E1BPCUVAL-CHARC
Rule Type: ABAP Code
    E1BPCUVAL-CHARC = 'PRG_METRIC'.
E1BPCUVAL-VALUE <=== ORDER_ITEM-ATWRT8
Rule Type: Transfer (MOVE)
    E1BPCUVAL-VALUE = ORDER_ITEM-ATWRT8.
    E1BPCUREF - CU: Reference Order Item / Instance in Configuration
E1BPCUREF-POSEX <=== ORDER_ITEM-POSNR
Rule Type: Transfer (MOVE)
    E1BPCUREF-POSEX = ORDER_ITEM-POSNR.
E1BPCUREF-CONFIG_ID
Rule Type: Constant
    E1BPCUREF-CONFIG_ID = '000001'.
E1BPCUREF-INST_ID
Rule Type: Constant
    E1BPCUREF-INST_ID = '00000001'.
    E1BPSDTEXT - Communication Fields: SD Texts

Hi Paaavan
You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module SD_SALESDOCUMENT_CREATE to create sales documents with.
Regards,
Marius

Error: Object type '' could not be generated when creating sales order

Hello Friends,
I am using a SAP standard ITS service to create sales order.
When I am creatin SO, it gives me error Object type '' could not be generated.
Can you plz suggest me what is that issue & how I can reslove it.
Regards,
Narendra

any inputs around this plz??

Create Sales Order With Reference to Billing Document Using BAPI_SALESORDER

Hi,
How can i create a sales order With Reference to Billing Document Using BAPI_SALESORDER_CREATEFROMDAT2?
Thanks in advance,
Alejandro.

I have to create sales order with reference to existing billing document. I have tried to following bapis.
1. BAPI_SALESORDER_CREATEed
I have successfully created document with following details.
-->ORDER_HEADER_IN:
DOC_TYPE =                  ZRK
SALES_ORG =              3000
DISTR_CHAN   =            00
DIVISION =                    00
ORD_REASON =            100
SD_DOC_CAT   =          L
CURRENCY       =         EUR
REF_DOC          =         100000028
REF_DOC_CA    =         M
-->ORDER_ITEMS_IN:
ITM_NUMBER    =           000010
MATERIAL          =          701791
TARGET_QTY     =          0000000001000
CURRENCY        =          EUR
REF_DOC           =          100000028
REF_DOC_CA     =          M
-->ORDER_PARTNERS:
PARTN_ROLE      =          SP
PARTN_NUMB      =         W12001
COUNTRY             =         NL
by providing this input i am able to create the document but it is not picking up the net value. so i have passed some extra paramters in ORDER_ITEMS_IN
COND_TYPE          =        PNET
COND_VALUE        =        14,56
COND_D_UNT        =         PC.
folowing error is occured: Condition PNET is missing in pricing procedure A V Z0000.
is it something related to configuration problem?
2.BAPI_SALESORDER_CREATEFROMDAT1 or BAPI_SALESORDER_CREATEFROMDAT2
I have used same test data that is used for BAPI_SALESORDER_CREATEFROMDATA (where in i coudl succefully create doc). but here i encounterd following error.
Unpermitted combination of business object BUS2032 and sales doc. category L.

Unable to create sales Order/Inquiry object using SAP JCo

Similar Messages

Maybe you are looking for