Distribute IDoc via BAPI_SALESORDER_CREATEFROMDAT2

Hello,
I am successfully creating a sales order with the BAPI BAPI_SALESORDER_CREATEFROMDAT2 from an external system via the SAP .Net Connector. 
I would like to generate an IDoc to send an order confirmation to the partner via message type ORDERSP. I have all of the output message type customized within my system and I am able to send the IDoc manually via the Output message control.
Is there something special that I have to call in the BAPI to generate the output message in NAST? Do I need to call a second RFC/BAPI? If so, any suggestions?
Thanks for the help

hi Stefan,
I think that you are forgetting the bind method call
wdContext.node<ModelNodeName>().bind( input1 ) ;
after this line
Bapi_Salesorder_Createfromdat2_Input input1 = new Bapi_Salesorder_Createfromdat2_Input();
Regards,
Ignacio.

Similar Messages

  • Getting error code 37 while sending IDOC via WE19

    Hello experts,
    I am facing a very unlikely error which is preventing me from testing my scenario.
    I dont have XI quality server and hence I am using my development server as both dev and quality. Hence I need to connect both dev and quality SAP R/3 system to my XI dev system. While I have done all the configurations in my XI and both SAP R/3 systems, its giving me error when i am trying to send IDOC from quality system.
    In quality R/3 i have done the following:
    1) Created RFC for my XI dev server
    2) Created port for this RFC
    3) Created partner profile adding all required IDOCS in the outbound parameters
    4) Created distribution channel for all the idocs
    In XI dev system i have done the following:
    1) Created RFC for both dev and quality of R/3
    2) Created port for both the RFCs
    3) Maintained the IDOC metadata for both the ports
    Now when I am pusing IDOC via dev of r/3 (we19) is working fine but when I am doing the same from quality of r/3 its giving me status code of idoc as 37 that says "An error was identified in the control record while adding an IDoc. The sender port SAPQTY_510 is invalid."
    But I have created this sender port SAPQTY_510 in my XI dev system and have also maintained the idoc metadata. I dont know why this error is coming.
    Can anyone please point out what mistake i have done or if i missed sometig as I am trying to connect 2 r/3 systems to one XI system.
    Its really urgent hence your help will be highly apreciated.
    Thanks,
    Yash

    hi yash,
    where you created SAPQTY_510 ,it should be created in R/3 Quality RFC destinations.
    In XI DEV create port like SAPxxx WHERE xxx is SID of quality system.
    actually we are getting confused.
    i guess you used same name SAPQTY_510 in quality R/3 and XI DEV .
    In error it says sender port SAPQTY_510  is invalid mean port of Source not XI DEV(receiver).
    just try to use some other name say SAPXXX_QUA and confirm the error.
    when IDOC is sent to XI DEV  ,port of  XIDEV  SAPQTY_510 has nothing to play any role .
    just check whether rfc destination of sender port (QUALITY R/3)you used is of type 3.
    so please check at which port error is coming.
    Thanks & Regards,
    Rama Krishna
    Edited by: rama krishna talluri on Mar 5, 2008 10:02 AM

  • Error in number range while testing inbound idoc via we19

    hi all,
    i have done all configurations but while testing the inbound idoc via we19 i am getting an error 'error in assigning number to idoc'..i checked and found that the number range object for idoc is edidoc in it number interval is defined from 1 to 99
    i dont think that anything is wrong with the number object..
    Can u tell me how dow i eliminate this error?

    Increase Higher limit the reason is when you look at current idoc number ( This idoc number already exists ) ,it will not create new idoc number.
    System will get the number from SNRO Based on IDOC Object.
    Just look at EDIDC and see the current idoc number.
    Simple example :
    I have one number - 100 ,it is already exists in database,if i insert same record to the database ,did system will accept ?
    Thanks
    Seshu

  • Sending IDocs via RFC Adapter

    Hello!
    In an itegration scenario, we need to send (non XML) IDocs via RFC to a remote R/3 system (4.6C). As we don't want to get these IDocs persisted on the target system, it's intended to address the remote functions directly.
    Now the problem:
    - RFC Adapter only works with XML IDocs (so we cannot transfrom back to native IDoc)
    - IDoc-Adapter sends native IDocs, but only to IDOC_INBOUND_ASYNCHRONOUS on target system (and the Idocs will be persisted)
    In a next step, we also tried to implement a workaround with a local ABAP proxy on the XI system. But it seems, that it's not allowed to call a abap proxy locally on the integration engine.
    Has anybody any idea to solve this problem? Maybe I'm thinking too complicated Help is highly appreciated!
    Cheers,
    Matthias

    Hi,
    what kind of document you want to post?
    most (many) IDOCs use BAPIs so you can
    just call the BAPI (RFC) from XI
    >>>But it seems, that it's not allowed to call a abap proxy locally on the integration engine.
    you can call it on another client on the XI
    (which is set as application system in SXMB_ADM)
    Regards,
    michal

  • Flat-Idocs via the IDOC-adapter

    Hi All,
    I want to send a flat-IDOC via the IDOC Adapter to a SAP R/3 system. The IDOC adapter does not accept flat-IDOC, but wants xml-IDOC. Does anyone know how to send this flat-IDOC to the SAP R/3 via ALE, but without XML-lizing the IDOC?
    I am looking in to the principle of tunneling, but that will involve some ABAP coding.
    Cheers,
    Frank

    Hi Bhavesh,
    I tried, but the IDOC adapter wants XML. The receiver IDOC adapter checks the type of the payload and determines if IDOC tunneling is used or not. I don't know yet how to change the type of the payload:
    <i>method CL_IDX_IDOC_SERVICE-GET_PAYLOAD, part of package SIDOC_ADAPTER
    test if idoc is in tunnel-payload-format
        l_content_type = l_payload->getcontenttype( ).
        IF l_content_type = if_xms_resource=>mimetype_idoc.
          l_idoc_resource ?= l_payload->getdata( ).
          l_tunnel_flag    = 'X'.
        ELSE.</i>
    and with tunneling the idoc must be stored in certain tables where the receiver idoc adapter will get the IDOC instead of the payload. And our flat-idoc is in the actual payload. So the direction I am looking into is an abap mapping, which will change the payload type and stores the flat idoc in these tables, so the idoc adapter is "fooled" to believe it is IDOC tunneling.
    Cheers,
    Frank

  • Sending MATMAS05 IDOC via XML-HTTP Interface (without XI)

    Dear all,
    I have to send the MATMAS05 IDOC via XML-SOAP-HTTP Interface to a subsystem. Sending works (the sub-system receives the SOAP-Request with the MATMAS05 as Body). So far so good. Now the SAP System is waiting for an answer (synchronous communication). How should this answer look like?
    We receive the Error EA390 "Problem with SOAP Class" - execute_processing: entry result table
    Can anybody give me a hint how the response should look like.
    Many thanks and best regards
    Roman

    Hello Sven,
    we find a solution. As far as I remember, there is a flag to send without waiting for answer (or technical better to not rely on SOAP standard).
    Look in WE21 and the XML_HTTP Port you use. Uncheck the "SOAP Protocol" flag. Then it should work.
    HTH and Best regards
    Roman

  • Problems with sending IDOC via RFC from Unicode to NonUnic

    Hello
    I have following problem, sending an IDOC via RFC from Unicode to Non Unicode System. IDoc is not sent with error: codepage of receiver system cant determined. receiver destination was: Message no. B1999
    I have tried different options in sm59, but it didnt help.
    Any ideas? The recipient system is rather old, version 4.0

    hey,
    I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and  RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

  • Testing Inbound IDoc via WE19...

    Hi,
    I am trying to learn IDOCs via WE19.
    I just took a sample IDOC from WE02 and tried to test in WE19.
    I am trying to understand what do we mean by following:
    1) Process Inbound IDOC via file ?
    2) Process Inbound IDOC via function module ?
    Regards,
    Rajesh,

    Rajesh,
    Go thru this link
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

  • IDOC Via Reprot program ( conversion)

    Dear All,
    I have to develop a conversion through IDOC Via Reprot program
    Can any one please give a little idea how to do this.
    Cheers,
    Raadha.

    Reviving an old thread...
    I'm getting a similar error making RFC calls from a stand-alone program to an ABAP server using JCo:
    RFC_GET4, GET_ID-3c05 LINE 990
    Any ideas?
    Thanks.
    Tim

  • Distributed rendering via wifi

    Could I setup distributed rendering via wifi: combining a 3.4 iMac 27inch and a Mac Pro 2.26 8-core?

    Tom Wolsky wrote:
    No, counterproductive. You would slow the process down, wasting time sending and receiving frames between the machines.
    I'll second that.  I've tried over WiFi and wired, (not gigabit) and it doesn't speed it up.  Too much time wasted sending and receiving data.  I do better setting up a quickcluster in Compressor, using the multi-cores to do the final rendering to the desired format.

  • MIGO - Distribute quantities via an interface.

    Hi All,
    We currently use subcontracting to record the consumption of components in a BOM via a goods receipt.  Where a component of a BOM is batch managed, we can use the distribute quantities button against a line item to allocate more than 1 batch to the component.  For example we want to GR 10kg for a component, and 5kg comes from batch A and 5kg from batch B.
    The above scenario works well using MIGO (no similar distribute quantities functionality appears to exist in MB01).  We are attempting to do the same via an interface.  WE are currently investigating the use of basic type MBGMCR02 (BAPI_GOODSMVT_CREATE) and WMMBID02 (function L_IDOC_INPUT_WMMBXY) but have had no luck.  Before we delve into these IDOCs deeper, I wanted to check to find out if anyone else had done something similar via an interface?
    Our other option, as we cannot record a MIGO session, is to build our own wrapper around function module MB_CREATE_GOODS_MOVEMENT but  I want to avoid this development if we can use a standard interface.
    I'd appreciate any help or guidance in dealing with the above scenario.
    Many thanks,
    James.

    It is enough if you:
    1. Distribute the stub and skeleton.
    2. Make sure you know the proper string throught which the server was bound to the registry.
    3. Make sure you call the appropriate objects and the proper method names on those objects.

  • HCM = FI: Posting an IDOC via Workflow

    Hello,
    I hope I'm right here in this part of the forum. In addition I hope my explanations will be good enough to understand.
    Every month the HCM-System send IDOCs (payment of salary) to the FI-System. Everything works well (in partner profile (WE20) we used message types ACC_EMPLOYEE_EXP, ACC_EMPLOYEE_PAY, ACC_EMPLOYEE_REC, PDTCO_POSTPRIMARY und PLANDATATRANSFERCO_POSTKEYFIGU (all inbound parameters) and process code BAPI is attached). Every payment is automatically and fully posted in FI.
    Latter the FI accounting clerks do not want. They do want to decide when the IDOCs are posted into the FI. What we've done so far ist that we've changed the process code BAPI at the above mentioned message types into ED00. ED00 uses the standard task TS30200088 for generating a workitem in the BWP of a or some users. That's exactly what we want, no instant posting but self-decided action through the clerk. The only problem is that the standard task only displays the IDOC as seen in BD87. The process then can be terminated via the menu and the status of the IDOC changes to 53, but no FI posting has been processed what's not very amazing 'cause the standard task only displays the IDOC. Now my questions:
    1. Is there any process code which comes with an appropriate SAP-Standard-Workflow to fulfil the request of the FI users (keeping the IDOC in Workflow status until the user executes the workitem  which leads to posting of the IDOC)?
    2. If not, do I have to create a new process code and do I have to create an own Workflow?
    3. If all that would not help what else can I do?
    In advance many thanks for your help.
    Kind regards,
    Frank
    Edited by: Frank Zieger on Oct 21, 2011 11:40 AM

    Hi,
    U have to use the lookup.
    1) pass the customer no to R3 system as input to function module.
    2) IN function module check whether that customer no present or not?
    3) Based on that u send a result back to Xi and go ahead.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70d90a91-3cf4-2a10-d189-bfd37d9c3231
    chirag

  • Sending Outbound FI Documents IDOC via ALE

    Hi all,
    We would like to send FI documents via IDOC. However, the message types we found, (FIDCC1,FIDCC2,FIDCMT) do not have outbound function. In addition to that how can we trigger IDOC, after posting FI documents .
    Thank you for your help...
    Best Regards,
    Didem GUNDOGDU
    mail: [email protected]

    hi, the outbound function for FIDCC1 FIDCC2 is list as followinig:
    FIDCC1     FI_IDOC_CREATE_FIDCC1
    FIDCC2     FI_IDOC_CREATE_FIDCC2
    But still can't find the FIDCMT, maybe you can create a customize function reference to two others.
    About trigger the IDOC sending, you can add the call function into a proper user-exits.
    Help it can be helpful

  • Loading flat idoc via report RSEINB00 into integration server fails

    Hi,
    we have PI/700.
    We get idocs (in flat format NOT XML) via filesystem from an external partner.
    Now I try to load these idocs with the report RSEINB00 into my integration server.
    My problem is, that the report says that the sender port + client(of the idoc control segment) is not a service in the integration directory.
    E.g.: SAPWR3 and client 550 (this WR3 is the system + client of the external partner who exports the idocs to filesystem).
    For testing I changed the idoc control segment and inserted an existing business system + a correct client (of our SAP-System) instead of the SAP-port used by the external partner.
    --> It worked!!!
    Do I have to enter the SAP-System of the external partner in my SLD?
    If yes - as a SAP-System (including client,...) or a third party system or...?
    Any ideas?
    Thanks for your help!
    Regards
    Wolfgang

    HI,
    Regd. Party config etc , you can refer this-
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    /people/sravya.talanki2/blog/2005/08/17/outbound-idocs--work-around-using-party
    More -
    http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
    <i>When I enter the sender-system of the external idocs into my SLD, do I have do insert it as a third party system or a SAP System?</i>
    >>SAP system.
    Hope this helps,
    Regards,
    Moorthy

  • Status 29 when creating and distributing IDocs

    Hi all!
    I try to create IDocs for distribution via MASTER_IDOC_DISTRIBUTE without providing a specific receiver.
    The distribution model contains for my message type a distrubution and generated partner agreements. In one example this is a bapi for a message type, in another example this is a message type directly.
    I get in BD87 the status 29 but i have no idea why the receiver could not be determined, as explained in the3 belonging message B1 003.
    Thanks for any hint.

    Hi Ferry, hi Nilesh,
    the partner agreements are ok.
    We were sure yesterday, that there was no difference for the bapi example and for the message type example. Today we found a result for the message type example what was our example to compare with.
    The example in focus is a bapi with the message type VCUI_SAVEM coming from business object BUS1401. I do not understand the difference between directly assigned message types in BD64 and indirectly assigned message types belonging to a assigned bapi when reading the documentation.
    When debugging the suggested modules i found out, that with bapis the message type is not contained in table TBD05 and nothing else is considered there.
    So the question is, what is the difference between bapi and message type assignement in this case and what is to do to use the distribution model with a bapi without providing the receivers by the caller.
    Thank you so far.

Maybe you are looking for