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..

Similar Messages

  • 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

  • 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

  • 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.  

  • 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

  • IDOC sender/receiver partner type LS?

    Hi,
    I am in need of advise if SAP 5.0 can be configured for ORDERS outbound (PO NEU) to pick up receiver (KU) partner type by standard config?
    I understand that there's exit available but would like to utilise standard application config method.
    Regards,
    Viv
    will definitely award points for the help!!

    if i understood u right this might help you
    1. /people/shabarish.vijayakumar/blog/2006/09/13/wanna-party
    2. https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660

  • 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

  • Idoc to File. Partner type as 'KU' and 'LI'.. Acheivable w/o using Party's?

    Hi all,
    Idoc to File scenario.
    I have the receiver partner type as 'KU' and sender partner type as 'LI'.
    I want to create the scenario without using party for these partner Types.
    Is it possible for me to create the B2B scenario without using party's?
    Is it mandatory that we need to use partys and Identifiers for these kind of scenarios?
    Kindly let me know if anyone has idea on this.
    Thanks
    -Seema

    Hi Seema,
    I appreciate that you chose to go with the parties
    That should be called a good design decision.......
    Now answering your query regarding the party identifiers
    Idoc to File :
    <SNDPOR>SAPDL1</SNDPOR>
    <SNDPRT>LI</SNDPRT>
    <SNDPRN>90000</SNDPRN>
    <RCVPOR>SAPXI</RCVPOR>
    <RCVPRT>KU</RCVPRT>
    <RCVPFC>SP</RCVPFC>
    <RCVPRN>36</RCVPRN>
    For Sender Party (say party INTERNAL)
    Agency : LD1_001
    Scheme: ALE#LI
    Name: 90000  (vendor number set in WE20 in the R/3)
    For Receiver Party (say party EXTERNAL)
    Agency: LDI_001 (SID_<client> BS as defined in SLD)
    Scheme: ALE#KU#AG  (AG for partner function SP)
    Name: 36  (customer number set in WE20 in the R/3
    This will resolve the IDoc header data into the following XI SOAP header information:
    Sender Party - INTERNAL
    Sender Service - LD1_001 (say this is the business system defined for logical system SAPLD1
    Receiver Party - EXTERNAL.
    Though, you can determine the receiver party alongwith the Receiver Service later at RCV DETERMINATION step, as I have said earlier.
    Yes, for outbound you have to maintain the identifiers for Sender Party type LI, but you can still skip the Receiver KU type and update the SOAP header at RCV DET step.
    File to Idoc:
    <SNDPOR>SAPXI</SNDPOR>
    <SNDPRT>KU</SNDPRT>
    <SNDPRN>36</SNDPRN>
    <SNDPFC>SP</SNDPFC>
    <RCVPOR>SAPDL1</RCVPOR>
    <RCVPRT>LS</RCVPRT>
    <RCVPRN>MAINSAP</RCVPRN>
    For Sender Party (say party INTERNAL)
    Agency: LD1_001 (SID_<client>)
    Scheme: ALE#KU#AG
    Name: 36
    For Receiver Party (say party EXTERNAL)
    Because the RCVPRT value is LS , no need to set the Receiver Party for that.
    But if you want to have some Receiver Party value for the same you can use Header Mapping in receiver agreement.
    Mandatory Setup in Receiver IDoc Adapter:
    Set the indicator -  Apply Control Record Values from Payload
    Remember to set the Identifiers in the Identifiers Tab in Idoc channel.
    Sender:
    Agency : LD1_001       Scehma : ALE#KU#AG
    Receiver:
    Agency: LD1_001        Schema : ALE#LS
    I am not sure why this ALE#LS entry is required, but according to my experience if we don't have that entry, the Idoc Adapter throws error while converting the Receiver Party (considering you use party in the ID configuration for both Sender and Receiver).
    Yes you are right, you can hard code the SNDPRN, RCVPRN values in the mapping and can take the values from payload...........for that set the following Indicators in Idoc channel:
    Take Sender from Payload
    Take Receiver from Payload
    Let me know if you have any concerns or any additional observation you make while configuring the scenarios. Thanks.
    Regards,
    Suddha

  • Mapping Control record?

    Hi all,
    iam doing File to idoc Senario and i need to map control record,How to map the control record.
    regards,
    phani

    Hi Venkatraman,
    if you want to control sender (and receiver) of an IDoc message by mapping, check "Take sender from payload" (and "Take receiver from payload") on. Map the fields of EDI_DC40:
    for the sender:
    SNDPRN (Sender Partner Name)
    SNDPRT (Sender Partner Type)
    and the receiver:
    RCVPRN (Receiver Partner Name)
    RCVPRT  (Receiver Partner Type)
    RCVPOR (Receiver Port)
    <a href="http://help.sap.com/saphelp_nw70/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm">Configuring the Receiver IDoc Adapter</a>
    Regards,
    Udo

  • ESS - SAP ECC 6.0/EP7 - Personal Info/Control Record

    Hi,
    During configuration for ESS on SAP ECC 6.0/EP7 , I received an error for 'Control Record XX not found' when selecting the Address and Personal Data services under Personal Information area on the portal side.  This occurred for one of our countries not on SAP Payroll.  I created a control record for that country and the error went away.
    Does anyone know why it is checking for a control record on version SAP ECC 6.0/EP7? We did not have this issue on SAP ECC5.0.
    Regards,
    Brian

    Thanks Siddharth - applied the note and issue resolved.
    Regards,
    Brian

  • 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

  • "Receiver port not valid in control record"...idoc error

    Hi,
    The new materials are sent to SAP via a text file which is placed in the application server which EDI uses to populate the Idoc segments and creates the material master.
    Recently we upgraded from SAP 4.6 C to ERP 5.0.
    After upgrading we are getting a message as Port(HPLED) invalid in control record.
    I get an error message as  "receiver port HPLED  not valid in control record"...
    It is not able to find  the receiver port & hence cannot create the MM.
    We checked all the config and compared with Test and production and we could not find any noticable change.
    Did anyone come across any infor on this?
    Your valubale reply is really very important for me.
    Pls reply.
    Regards,
    Pri

    Hey Ramesh,
    I've already done the WE57 setting.
    You see the WE57 setting is always done on the reciever side and not on the sender side (There is no harm but it is not what SAP recomends) The Linking on the sender side is done in the Partner Profile, where we give the extension name.
    For the reciever this Partner profile setting of extension is not there therefore we need to go to WE57 and do it.
    I've done all the config and have tried all the things in both the systems but somehow nothing is working.
    That is why I asked that in my Inbound FM which is IDOC_INPUT_HRMD do I need to popluate one of it Parameters or fields where I mention the Extension name and all.
    Yesterday however I found an SAP NOTE (105148) which tells me that my naming convention of the Extension is wrong. I have made ZHRMD_A07 extending standard IDOC tupe HRMD_A07, actually it should be ZRMD_A07. Again this is speculative I need to try this out. But I do know that SAP has various checks which checks all the naming convention and all. I'll try this out and hopefully it might work.
    In the meantime any other suggestions are most invited. I am using Message type HRMD_A and using IDOC type HRM_A07
    Regards
    Abhishek Sahi

  • Message "Wrong partner type LS" in message control

    Hi All,
    I am trying to send PO's out to a middleware system. I have configured the middleware system as a LS (logical system) done all the config required for Message control.
    But when I enter Output type = NEU and Medium = A (ALE) and Partner Function = LS and partner name and save the PO, I get the error "Wrong Partner type LS" in the processing log for that message. The details description says "The message record of the message control contains a partner role with a partner type LS that cannot be used here. Only the 'KU' and 'LI' partner types are allowed.". But i need to send it to partner type LS.
    Am I missing anything. Please Advise.
    Thanks in advance

    Hi!
    'By default' purchase orders can be send to vendors or plants - the two parties in the document. This is linked to the two different partner types KU and LI. Only partners of this type of a purchase order can be used to send data.
    Check, if you can create a partner definition (WE20) for KU (hopefully you have less plants then vendors).
    You also need a partner determination for the document - only out of this partners automatically a message output can be assigned.
    Regards,
    Christian

Maybe you are looking for