Create Sales order through PO by output type NEU

Hi friends,
I want to create Sales order out of a PO. I used the output type NEU of PO and was successfully get ourbound IDOC posted. But my inbound failed.
Two erros message:
1.The material number for item 000010 could not be identified
2. Partner number XX01 for customer XX01 , partner function WE does not exist
Although I can manually create the sales order with exact same info.
I used message type ORDERS04 for both partners and use ALE as a transmition.
Thanks in advance!

hi ,
Can you please tell me it for the same company code or different company code.
maintain the customer material info record , if it is a different company code. the system is checking the qualifier.
thanks
Kuntla

Similar Messages

  • Creating sales order through Bapi

    Hi all,
    I am trying to create sales order through bapi.
    Now my problem is mapping sales order fields with bapi structure fields.
    1.'Overall Order status' field in the 'Status' tab of the header in VA02.
    2.'Tax'feild in the 'conditions' tab of the header in VA02.
    Please help me to map these fields into Bapi structure.
    Thanks in advance.
    Regards,
    Shalem.

    HI
    GOOD
    GO THROUGH THIS LINK,I HOPE THIS WILL GIVE YOU THE COMPLETE IDETA OF CREATING A SALES ORDER THROUGH BAPI,
    http://help.sap.com/saphelp_nw04/helpdata/en/4c/fd7ebb515911d395f900a0c94260a5/content.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    THANKS
    MRUTYUN

  • Create Sales Order through OE_ORDER_PUB  API and get credit card authorizat

    Hi,
    I was trying to know if there is some way to get credit card authorization (when payment type is CREDIT CARD) creating a Sales Order through de OE_ORDER_PUB API.
    I need to reproduce the manual process where you get this authorization, through the Action Button, in the Sales Order Window.
    Thanks in Advance.
    Nicolas.

    Hi Nagamohan,
    Thanks for the reply..It was Vision Instance that i was working on..
    There was some problem in setups. I had run the same script on other instance and it is working.
    Before signing off i have one more doubt...
    The script which i used is creating a sales order with booked_flag='Y' but flow_status_code is still 'ENTERED'
    how can i change it to 'BOOKED' using API...
    Thanks for the help...

  • Problem In Creating Sales Order Through DI API

    Hi
    I am Creating The Sales Order Through DI API.
    the Error Is Coming - " [OACT] , 'No matching records found (ODBC -2028)'"
    anyone  can help me solving it.

    Hi vivek,
    Have you tried adding the same document with the client ?
    OACT is the accounts table and this error message typically indicates that there is an account parameter missing somewhere in the system.
    Possible causes include:
    - you are using a tax group or warehouse which does not have all the required accounts set
    - There is a price rounding and the rounding price account has not been set in the account settings
    - etc.
    The first things I would check include the tax group settings and the G/L Account determination settings.
    Henry

  • ITem category  error while creating sales order through

    Hi,
    I am trying to create a sales order through Bapi  and in between im getting the below error.
    ' Item category TAM is not defined for non material items'.
    Can anybody pls provide the solution for this.
    Thanks

    speak to your SD functional person.  The Error is pretty self explanatory; SAP is telling you that the item category for that order item is not permitted by your SD configuration.

  • Create Sales Order through VB

    Hi Experts
              I am new to BAPI, my requirement is to create sales order in SAP through VB.
              Please provide me the BAPI coding part which are needed and also suggest me the steps to be followed in SAP and VB.
             Thanks in advance.
    Regards
    Rajaram

    Hi Vinodh
      I tried this coding as part of your link, but it contains Run-time error as Object Required.
          Anything needs to be added in my VB Project, i have already added the BAPI ActiveX contol in my project.
    Pls sugges me.
    Dim boOrder As Object 'Business object SalesOrder
    Dim oPartners As Object 'Parameter OrderPartners of BAPI method
    Dim oHeader As Object 'Parameter OrderHeaderIn of BAPI method
    Dim oItemsIn As Object 'Parameter OrderItemsIn of BAPI method
    Dim oReturn As Object 'Parameter Return of BAPI method
    Private Sub Form_Load()
    'Connect to business object SalesOrder
    '(this creates an anonymous object with an empty key field):
    Set boOrder = oBAPICtrl.GetSAPObject("SalesOrder")
    'Get structure/table objects:
    Set oPartners = oBAPICtrl.DimAs(boOrder, "CreateFromData", "OrderPartners")
    Set oHeader = oBAPICtrl.DimAs(boOrder, "CreateFromData", "OrderHeaderIn")
    Set oItemsIn = oBAPICtrl.DimAs(boOrder, "CreateFromData", "OrderItemsIn")
    'Fill header:
    oHeader.Value("DOC_TYPE") = "TA" 'Standard order
    oHeader.Value("SALES_ORG") = "0001" 'Sales organization
    oHeader.Value("DISTR_CHAN") = "01" 'Sales channel
    oHeader.Value("DIVISION") = "01" 'Division
    oHeader.Value("PO_NUMBER") = "" 'Customer purchase orderNumber
    oHeader.Value("PRICE_DATE") = Now 'Date
    'Fill partners:
    oPartners.Rows.Add
    oPartners.Value(1, "PARTN_ROLE") = "AG" 'PartnerRoll: Person posting the order
    oPartners.Value(1, "PARTN_NUMB") = "0000010096" 'Customer number
    'Fill items:
    oItemsIn.Rows.Add
    oItemsIn.Value(1, "REQ_QTY") = "0000000010000" 'Quantity
    oItemsIn.Value(1, "MATERIAL") = "BERLINER" 'Product ID
    oItemsIn.Value(1, "COND_VALUE") = "1432" 'Rate
    'Call the method:
    boOrder.CreateFromData OrderHeaderIn:=oHeader, _
    OrderPartners:=oPartners, _
    OrderItemsIn:=oItemsIn, _
    Return:=oReturn
    'Free the business objects:
    Set boOrder = Nothing
    End Sub
    Regards
    Rajaram

  • 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

  • Creating sales order through BAPI - do not want to send idoc confirmation

    Hi guys!
    I'm creating a sales order using BAPI BAPI_SALESORDER_CREATEFROMDAT1. The system was cuztomized to send an idoc through an output type, so whenever this BAPI is executed an idoc is sent.
    My problem is that I do not want the Idoc to be created when using this BAPI.
    Is there a way not to use an output type when using the BAPI?
    Thanks in advance for your help!

    Use an output requirement that stops the proposal of the output.  You'll want to make sure that it works in both immediate and delayed modes, e.g., you can't use a field-symbol (or the KOMKBV1 user exit) for access to T180-TCODE or to the CALL_BAPI value in memory.   You might want to try the VBAK-ERNAM value, since you probably use a specific (non-dialog) user for the call.  Otherwise, use another field to identify a BAPI call and check that field in the requirement.

  • How to created sales order through xi in CRM...?

    Hi
    My scenario is like this
    I have one purchase order web application. when i click submit request will go to xi throgh http request. After it receiving the request xi will take the purchase order and based on the purchase order it will create a sales order in CRM through IDOC adpater and send the purchase order reference no back to customer.
    How to do this scenario can any one please help me.
    Best Regards
    Deepika
    null

    You could use BPM to do this.
    Try these how to guides :
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40697f5e-088d-2910-6592-cefedf19860e
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e7bc3a5a-0501-0010-1095-eb47159e169c
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/59ef6011-0d01-0010-bfb0-b51381e00509

  • Creating Sales Order through SAP-EDI after PO

    Hi, Experts.
    Please help me to design business flow using SAP-EDI.
    How can I design business among 2 affiliate companies and HQ.
    are many company around the world, and they want to use SAP-EDI to realize intercompany process,
    such as below.
    1, Company A create Puchase Order from B
    2, Sales Order is created automatically at Company B
    I know it is possible If this is only among 2 companies.
    But my client want to put HQ in this flow by plan as below.
    1, Company A create Puchase Order. and in Puchase Order,
    Vender is HQ and Invoicing Party is HQ
    Goods supplier is Company B
    2, Sales Order is created automatically at Company B, and in Sales Order,
    Sold-to party is HQ and Bill-to party is HQ
    Ship-to party is Company A
    Be careful that A doesn't always purchase from B, so user should select where to purchase at each time.
    Is it possible to realize customizing or user-exit? If so, please tell me.

    wazukanahikari
    With regard to margins, you should be able to manage them using pricing conditions, you have the following in the standard any way:
    PI01 Intercompany: fixed amount per material unit
    PI02 Intercompany: percentage of the net invoice amount
    If the above don't work, you can create your own condition types to add the margin.
    I don't think you need to add on anything special, if you have an EDI specialist work with him/her. This is an ALE/EDI process that one company sends a PO Idoc and another company uses that Idoc to create a Sales order. Only difference is that both companies are in the same SAP client/instance.

  • Error while creating sales order in ECC 6.0

    Hi All,
    I am creating sales order through VA01.
    Error comes As "Repairs processing with cost management only for the main item"
    The material which i am using is finished goods.

    Dear Akilesh,
         Just check whether the material - in MM - material type whether the Qty and value update has been ticked.
    What order type you are using and what is the item category you are using?
    Kindly let me know that also
    Regards,
    Sudhir

  • Create Sales order with reference to purchase order - Help needed

    Hi Gurus
    Purchase order is being created in Oracle system. SAP system will receive the purchase order and creates the sales order for the corresponding purchase order.
    Hoe to create sales order, Through BAPI or through IDOC. Please suggest and give some pointers of existing interface
    Thanks
    Andy.

    Hi,
        If you are working on ECC6.0 check for the BAPI BAPI_SALESORDER_CREATEFROMDAT1 .You can also pass the purchase order number .
    Check the sample 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'.
    *Purchase order number
    header-PURCH_NO_C =  '4000006'.
    headerx-PURCH_NO_C = '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.
    Reward points if it worked.
    Regards,
    Abhishek
    Edited by: Abhishek Raj on May 14, 2008 9:57 AM

  • Sales order through QM02

    Dear All,
    We are creating credit memos against QM notification (type q1) and it is working also.
    The requirement is that through VA01 t code either credit note sales doc type
    should not allow or without notification no sales order should not save.
    To handle this I have added VBAK-QMNUM in incompletion procedure for credit note sales doc type and it
    is also working. But while creating sale order through QM02 order it is showing incomplete for
    notification no but in sales tab field of notification is not showing.
    As per logic if I create sale order through QM02 notification no should should copy but it
    is not working. plz advice what can I do.
    regards,
    sp shukla

    Dear Divya Singh,
    I don't think that is logical to DTW document with approval. You probably better to DTW drafts and then going through approval procedure.
    Thanks,
    Gordon

  • Creation of Sales orders through EDI

    Hello,
    We have a problem when creating sales orders through EDI.
    We are getting IDOCs with a delay of 1 second.Before  
    creating sales orders through the posting function
    module IDOC_INPUT_ORDERS, we need to validate for
    reference Purchase order number in the IDOC. If there is
    any sales order in the database with the Purchase order
    number in the current IDOC that sales order should be 
    blocked.
    We already put a validation in the User-Exit of the
    posting function module. Because of the frequency of
    IDOCs we receive, this validation is getting failed.
    Can anybody tell me, how to process only 1 IDOC at any
    given point of time before the Posting process.
    Thanks,
    Madhusudan.

    Hi Sanjeev,
      Thank you very much for helping me out in this problem.Still I haven't got the solution.
    I tested the above mentioned configuration option by putting the Check Purchase Order Number field to 'A' in the transaction VOV8. But while creating sales orders, it is giving only information message. Is there any other way, to restrict the Duplicate PO value through configuration setup.
      can you also explain how to use Enqueue and Dequeue FMs in the inbound posting function module.
    Regards,
    Madhusudan.
    Message was edited by: Madhusudan Budati
    Message was edited by: Madhusudan Budati

  • Creating Sales Order trhough PS-WBS

    Dear Experts,
    I have two question;
    1. I need to create sales order through WBS according to client's requirement. Can anyone explain how to create sales order from WBS.
    2. Client wants to create sales order through WBS and trigger milestone billing plan from that sales order. but client wants to delivery according to normal sales order. My question, is it necessary to create two sales order for same material? I want to delivery from that sales order which is created through WBS. is it right decision?
    I am waiting for your valuable suggestion.Thanks in advance.

    Sorry about the below the site is acting up again. Anyways according to process it depends on how the configuration is setup.
    In my experience I have seen that deliveries are done thru PS. One creates a Project Sales Order and assigns the WBS element number inside the item line for that material. If PS config is properly set the Billing Plan dates also get fetched and populated. Once it is assigned you can create invoices relating to the billing plan dates in order related billing. Note: You can create deliveries from PS or SD. I have no idea why you would create 2 sales order you did not quite explain why you would want to do that for?
    Best of Luck
    Ali Lozada

Maybe you are looking for