EDI: Sender partner number in control record is default

Hello!
Another problem... in SUS - MM, Plan Driven Procurement
I try to send PO from MM to SUS. But in the messages I get following
error: "EDI: Sender partner number in control record is default"
Message no. EA608
SAP Note Number: 111342 doesn't help
the logical systems are maintained!
Any idea about this problem?
Kind regards,
Barbara

If this is in regards to an ASN:  Check to see if this customer buys several divisions or is relevant for one division only.  In our instance of SAP, we found that it didn’t go to the Customer Master division setup relevant  to the division on the ASN to get the ACCT AT CUST field, it went to the first in the sequence of divisions and got that ACCT AT CUST field information.  That information was not filled out as it was a new division and that is what kept the output from happening.    For example:   we had divison 02, 04, 06 and 08.   We added division 03 and extended all customers to division 03.     Those customers that only bought division 04 just stopped sending ASNS.    The ASN was for division 04, but SAP logic was retrieving the ACCT AT CUST information (SALES tab, not CORRESPONDENCE tab) for divison 03, but we didn’t have that filled out. 
Hope that helps.  

Similar Messages

  • EA608 EDI: Sender partner number in control record is default

    We have created some KU partners in WE20 for sending billing documents to the SD bill-to partner but is running into an output error EA608 (EDI: Sender partner number in control record is default) on the billing document when trying to create IDOC's.
    Settings on partner:
    Partner: 12345
    Partner type: KU
    Partner function: BP
    Message type: INVOIC
    Application: V3 : Billing        
    Output type: ZEDI : US EDI Invoice
    Process code: SD09 : INVOIC: Invoic
    EDI Standard         X  
    Message type         810        
    Version              004010     
    Any idea to what the problem is?
    BR
    Joergen

    Hi Joergen,
    we also have similar problem to send out ordrsp. Could you tell me how to solve this problem as I saw tht this problem of yours has been answered.
    Thanks inadvance for your reply,
    Lily

  • Statusrecord 37:Sender partner number in control record is default

    Hi all
    I am sending MATMAS data from one R/3 to another R/3 in ALE.
    when i am testing it from we19..... I'm the data is not sent insted it is being saved in database.
    In WE05 I can see the following error.... and the lights are green.
    statusrecord 37:Sender partner number in control record is default
    Please help me
    Thankyou
    SIMON

    Hi Joergen,
    we also have similar problem to send out ordrsp. Could you tell me how to solve this problem as I saw tht this problem of yours has been answered.
    Thanks inadvance for your reply,
    Lily

  • 56 error,EDI: Receiver partner type in control record is default

    Hi all,
    When I trying to post the IDOC the 56 error is shown.
    I checked the partner profiles and found fine.Please clarify.
    Thanks,
    Srinivasa

    Hi,
    this means that your IDOC has some errors
    you can see it by clicking on the status in We02
    then you will know exactly where the error is located
    in inbound processing you should see status 53 - successful
    BTW
    to check IDOC errros with XI:
    /people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi
    Regards,
    michal

  • Receiver partner type in control record is default"

    Hi all,
    I am Getting 56 Error"Receiver partner type in control record is default".
    When I go to that perticular IDoc under control record under parter tab I am providing "PARTNER TYP" AND PORT.When I save these details th idoc is getting posted.
    The  port ifo is present in we21.I checked RFC Destination,It is fine.
    Now where to give this information centrally since I have to manually enter this every time.
    Thanks,
    SrinivasaP

    Hi,
    If error is 56.
    Check the partner profile is created or not, if not create partner profile, restart the process by TA.BD87.
    If partner profile is exist then check the control information in the IDoc file is incorrect. Correct the IDoc file and restart the process
    Please check receiver IDoc Adapter is configured with the said details are not.
    And if possible map the values in EDI_DC40 control record.then you need not to give these details every time.
    Regards
    Chilla..

  • IDOC control record mapping - Sender Partner number defaulted to log. sys.

    My PI scenario is file to IDOC scenario.
    I have ticked "apply values from payload" checkbox, so Sender Partner Number is being defaulted to logical system assigned to my business system.
    Logical system name has to be unique in PI. My understanding is that I can not have more than 1 business system with  the same logical system assigned to it.
    In SAP, I need to have idocs, coming from different businees systems through PI, set to have the same sender partner number,
    which is not possible when "apply values from payload = 'X' and messages are coming from different business systems.
    Calling all PI Gurus, have you got a workaround ?

    Hi,
    Idoc will be processed in SAP ECC based on the sender details (snprn,sndpor,sndpfc...) of idoc control record..
    instead of different partners name sending in the sender details of control record ...pass the value of the PI logical system name in SNDPRN.... (use only one and this is common for all partners...) any how data records of idoc will have the needed partner details...
    In SAP ECC you need to have this logical system ...to process the received idocs..
    thats it... Hope you got
    Regards
    Rajesh

  • ERROR:Receiver Partner record in the control record  is default

    Hi,
    When I am trying with WS t Idoc scenario the followinw error is getting
    "Receiver Partner record in the control record  is default" when I am checking in we05
    Please clarify.
    Thanks,
    Srinivas

    Hi,
    Check the partner profile settings in we20.
    Regards,
    Smitha.

  • Partner determination in control record for EDI

    Hi all,
        I have a custom EDI output which goes into the delivery.  However this EDI output is not picking the correct partner.
    The sales order with 2 plants would create 2 deliveries.   First delivery is created for plant A121 while second delivery is created for plant A710.   However, the vendor partner is not picked up correctly for plant A121 in the first delivery.  LIkewise the second delivery.  When the sales order has same plants, it create 1 delivery.  This comes out with correct partner.
      My question is:  How is the partner determined in EDI control record before the delivery is created ?
    In Partner Profile, WE20, there are 3 defined partners (100 LI, 200 LI, 300 LI).  For plant A121, the partner would be vendor 200.
    Thanks
    Joyce

    Hi Vinod,
       Thanks for your suggestion.  I have condiiton record for this EDI which is plant and it would list the partner.  Somehow, it seems the plant is not picked up correctly when there are a few plants in the sales order.   Becasue the partner is not picked up correctly, it seems to affect other output types that are plant-based.
        Initially the all output for EDI works fine.  There have been recent changes made to split delivery by plant which is fine  Output is one that are having issues.
       Have you any other suggestions ?  I will continue to look at the program  you suggested.
    thank you.\
    Joyce
    Edited by: Joyce Chan on Mar 17, 2010 8:31 PM

  • What is sender port in idoc control record!

    Dear all
    In idoc control records it is showing two ports  Receiver port and sender port.receiver port we cen configured in WE21.
    where we configured senderport!
    how it is updated in control records!
    Thanks & Regards
    raj

    When you generate the outbound idoc you provide info for Receipent
      "control record
      idoc_control-idoctp = 'ACC_GL_POSTING01'.
      idoc_control-doctyp = 'ACC_GL_POSTING01'.
      idoc_control-mestyp = 'ACC_GL_POSTING'.
      idoc_control-rcvprt = 'LS'.           "Partner Type of Receiver
      idoc_control-rcvprn = 'WCP100'.       "Partner Number of Recipient
      idoc_control-rcvpor = 'WCP100'.        "Partner Port of Recipient
      idoc_control-direct = '1'.             "outbound idoc
    When you receive and inbound idoc you nedd to provided similar info but for Sender
    Port for Sender is just like port for Receipent. Both you check in WE21.
    Edited by: Marcin Pciak on Oct 17, 2008 9:47 AM

  • Problem in modifying control record

    Hi All,
    My scenario is Purchase order to Sales order. Once PO is created IDOC will be created and that idoc will be taken as source and i will be modifying the idoc in abap mapping as per requirement.
    All the segements are being modified and getting updated in IDOC but when i am trying to change the control record its not getting reflected in the r/3 but when i check in moni before comming to r/3 the xml struture has changed as per my requirement even for control record also but while comming from XI control record is not getting changed.
    I would like to change senderpartner and sender partner type in control records.
    every configurattion steps has been done  correctly.
    Would request your experiences if you would have faced any this type of situation in your projects.
    Thanks in Advance.

    Apply Control Record Values from Payload
    If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.
    If you do not set the indicator, all combinations of communication parties and services are handled as services without party.
    If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values.
    http://help.sap.com/saphelp_nw04s/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm

  • Version of EDI standard in control record of an IDOC

    Hello All,
      I want to know from where the Version of EDI(in details tab of control record) is being picked from.
    Thanks,
    Rakesh.

    Hello Amit,
      I checkd in WE30.I think release version is different from EDI version because for a vendor in the system the release is 46C whereas EDI version is V11.
    Thanks,
    Rakesh.

  • XI3.0 IDOC control record - SNDPRN and SNDPRT setting from payload

    Hi,
    I have a source XML from which I wish to create IDOC-XML and forward to the IDOC adapter to post to an R/3 system.  I wish to create IDOCS with a sender partner type of 'KU' and a sender partner number which I wish to copy from the source XML document.  I have read the How to sample IDOC-XI scenarios but I still cannot get this to work.  Whenever the IDOC is created in the R/3 system is still has a sender partner type of 'LS' and a partner number taken from the sender business system. 
    To summarise - how do I map the customer number from the source XML-payload and use this to set the sender partner number and type for use by the IDOC adapter. 
    Many thanks
    Ian

    Sravya,
    Thanks for your blog & reply:
    I have changed my receiver agreement to map the sender party to /ORDERS05/IDOC/EDI_DC40/SNDPRN and set the schema to ALE#KU
    & for Receiver party to /ORDERS05/IDOC/EDI_DC40/RCVPRN.
    I'm receiving the following error message , can you please look into it :
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
      <SAP:P1>http://sap.com/xi/XI</SAP:P1>
      <SAP:P2>ALE#KU</SAP:P2>
      <SAP:P3>5229</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI/ALE#KU/5229 to an IDoc partner</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

  • EDI: Sender port in control record is invalid

    HI
    EDI: Sender port in control record is invalid,  this message i am getting in WE02 what is this pls tell me ASAP
    regards
    shekar

    Hi,
    Check the ALE setting...
    STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
    We need to do the following settings in XI
    1) Create an RFC Destination to the Sending System in transaction code (SM59)
    a) Choose create
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client user & Password details of Destination system
    h) Test the connection and remote logon.Both should be succesful
    2) Create Port Using Transaction Code IDX1
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client
    d) Enter the RFC Destination created in SAP R/3 towards other system
    e) Save
    3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1
    SETTINGS IN SAP R/3
    We need to do the following settings in R/3
    Logon to Sap R/3 System
    1) Create an RFC Destination to XI in transaction code (SM59)
    a) Choose create
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#
    e) Enter the Gateway host as same details above SID/URL
    f) Gateway service is 3300+system number#
    g) In the Logon /Security tab, enter the client user & Password details of Destination system
    h) Test the connection and remote logon.Both must be succesful
    2) Create communication Port for Idoc processing Using Transaction(We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile with Outbound Parameters (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang
    Then Save
    e) Select Partner no. and LS which were create above
    f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
    g) Select Message type
    h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
    I) save
    4) In Transaction SALE, Create Logical System
    a). Go to Basic Settings-> First Define logical systems
    and then assign logical systems
    b) Double click on Define the logical systems
    c) Give data for your Logicaal System and Name
    d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e) Assign the logical system name to the client
    5) Create Customer Distribution model in the transaction code BD64
    1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
    2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
    3) Save the Distribution model
    Generate Partner Profiles
    Click on Menu Item ‘Generate Partner Profiles’
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
    4) Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> ‘Distribute’ to the destination client
    Popup window appears ,press Enter
    You will be intimated about the the Modal View Distributed
    Regards,
    Phani

  • EDI: Field REFINT in control record

    I am trying to send orders.orders05 idoc from ecc to xi
    the message that I get in we02 in ECC is
    EDI: Field REFINT in control record with value 'T080902134731A ' is invalid
    Does somebody knows where this field is configured ?
    when I edited this idoc in we02 and erased this value the process was sucessfuly
    but when I try using we19 it assigns this value automatically
    thx
    Shai

    hi
    it depends on use
    As a reference, this field contains the number of the interchange file, as entered in the EDI standards.
    An interchange file can therefore only exist in the external EDI subsystem. Depending on the transmission direction, this number should:
    either inform the R/3 System via status confirmation: in this case, the last returned number is saved in the control record of the relevant outbound IDoc (from R/3).
    or in inbound processing (from R/3), write to the field in the control record of the inbound IDoc.
    cheers

  • Changing IDOC Control Record for EDI inbound Orders Creatiion

    Hi,
         When I try to process the Inbound orders Idocs file through the GENTRAN EDI System.IDOC's were errored out, because of the Partner function was not defined for the Customer ( Legacy ) ( Type KU ) in the SAP.
            Is there any user exit/badi/Configuration to change the Legacy Partner(Customer) to the SAP Partner(Customer) mapping and update the IDOC Control record with the SAP Partner. I am calling EDI_DATA_INCOMING Function module and IDOC_INPUT_ORDERS.IDOCs errored out with Message EO-332 ( Partner function not defined ). 
    Advance Thanks,
    Balaji.

    It's been a long time since I have done any IDOC processing. 
    Go to SE37 and enter the function module IDOC_INPUT_ORDERS.  Display the source code.  Search for "CALL CUSTOMER".  You should see several "CALL CUSTOMER-FUNCTION" lines.  These are enhancements where you can manipulate the IDOC data.  If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value.  Double-clicking on the number in quotes will bring you to an "EXIT_" function module.  A "ZX" INCLUDE program is referenced.  If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it.  The values passed into the function module are available in the INCLUDE.
    Ideally, you should create a project in transaction CMOD that references the chosen enhancement.  This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

Maybe you are looking for