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

Similar Messages

  • EDI: Receiver port in control record is invalid

    Yesterday, we got refreshed out quality system with the production SAP system.
    I am trying to process IDoc # QXXXXXXX  in quality but I am getting the following error message:
    EDI: Receiver port in control record is invalid.
    To create this IDoc, I copied IDoc # PXXXXXXX using WE19 and modified certain fields so that it would change the clearance status. The IDoc I used to copy from was from production server and a part of the recent refresh of Production serveru2026
    could that be the reason that the EDI Receiver port is invalid or is there another reason?
    THANKS IN ADVANCE.

    Hi sam kumar 
    Ports and Partner Profile  may be Same or Different in Quality and Production  systems.- it is Client dependent
    U can cross check Ports using WE21 with Quality system and production systems
    U can cross check Partner Profile using WE20  with Quality system and production systems
    if both are not same u need maintain port and partner profiel before creating idoc using we19...
    Note: Keep a note on Logical system also..
    I hope this help for all when system refreshs,.
    Ramesh

  • Sender port in control record

    Hey guys
    i m trying to test my IDOC to FIle scenario and in WE19 i m getting an error with status 37 saying that sender port in control records is invalid.
    i have created the Sender port correctly in WE21,what might the problem be?
    thanx
    ahmad

    HI,
    As you said you have created the port with WE21.
    Did you checked , RFC destination which was configured in Port creation , what was the user ,pwd you used,does that user has the proper authorization , did you checked remote login for RFC destination,generally SAPxxx for port name, did you selected the version which was selected.
    let me know what is the correct error.
    Regards
    Chilla..

  • 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

  • Sender Information in control record of IDOC adapter

    Hello All,
    I am sending data from JMS to R/3 (IDOC). I need to populate the SNDPRT with LI and SNDPRN with 42980.
    I have mapped SNDPRT with LI and SNDPRN with 42980 in the control record. I have checked the <b>Apply Control recrod values from check box</b> in the IDOC adapter communication channel.
    Also checked the Sender Party in the Receiver aggrement. I have selected <b>the context object as the SNDPRN of IDOC control record</b>
    But it is failing. I am getting an error Unable to convert sender XI party ........to  an IDOC party
    I need to resolve thsi problem
    Please help me.

    Hi Abinash,
    In addition to the document Mike suggested, SAP has many How-to Guides at the following link
    http://service.sap.com/nw-howtoguides
    https://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
    Mike: Thanks a lot for spending your valuable time helping the forum even on Weekends. SAP really appreciates your help on this.
    Regards,
    Sam Raju

  • Sender Port Invalid.

    Hi Experts,
    We have pre-prod system(MR0) and Production System(MP0). recently our MR0 is refreshed and copy MP0 to MR0.
    Now when i am trying to process any IDOC it is giving me the error like 'EDI: Sender port in control record is invalid'.
    So if i want to change the sender port how can i change it?
    Thanks in Advance,
    Abhishek.

    >
    abhishek ingole wrote:
    > Hi Experts,
    >
    > We have pre-prod system(MR0) and Production System(MP0). recently our MR0 is refreshed and copy MP0 to MR0.
    > Now when i am trying to process any IDOC it is giving me the error like 'EDI: Sender port in control record is invalid'.
    > So if i want to change the sender port how can i change it?
    >
    > Thanks in Advance,
    > Abhishek.
    I think you are trying process a IDoc in system MR0 which was created in system MP0.
    Sender port for outbound Idoc should be SAP<sys-id>, in your case in system MRO it should be SAPMR0 but it is SAPMP0. If this is the case then you can process those Idocs by changing port to SAPMR0 using transaction WE19.
    Edited by: Pawan Kesari on Dec 23, 2009 9:50 PM

  • IDoc Message: Invalid Sender Port in FM IDOC_INBOUND_SINGLE

    Hi experts
    For inbounding IDocs I use the FM IDOC_INBOUND_SINGLE.
    My problem is, the IDocs always gets the status 56 with error message <Sender port in control record is invalid>.
    I don't understand the message, because all ports are maintained in WE21.
    When I execute BD84 for created IDocs everything is OK.
    But my problem is, that I don't want to execute BD84 after every IDoc which will be created by the FM IDOC_INBOUND_SINGLE.
    So could anyone help with the error message <Sender port in control record is invalid>.
    Thx for every help

    Hello Sachin
    Thx for fast help.
    However, a few minutes ago I solved the problem (debugged SAP-FM).
    Problem had been, that direction was 1 instead of 2.

  • Outbound IDoc Error: Status Code 37  'Sender Port' is invalid

    Hi
    I have an Error when the Outbound IDoc is triggered.
    It shows that 'Sender Port in Control Record is invalid'.
    Status Code: 37.
    I know that there are some issues with the Sender Port Definition.
    Please help me out to solve this problem using some checkpoints at each and every step.
    Reward Points Assured.
    Regards,
    Baburaj

    Hi Baburaj Manickam
    Good
    Follow this simple procedure
    1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
    -  Create File Port (WE21) for outbound file.
    -  Maintain Distribution Model (BD64) for sender ->receiver system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s). 
    _  Then you can FTP the file(s) to receiver system.
    2) Upload the flat file as an IDOC on the inbound sytem
    which is Client2(RECIEVER).
    -  Create File Port (WE21) for inbound file.
    -  Maintain Distribution Model (BD64) for receiver -> sender system.
    -  Create Partner Profile (WE20) for logical system.
    -  You can use this program RSEINB00 to upload IDoc MATMAS file(s). 
    INBOUND IDOC PROCESSING:
    Firstly attach your idoc to a process code.
    In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
    Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
    1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
    2. Set Function Modules as Inbound: - Transaction BD51
    3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
    4. Create process codes : Transaction WE42, and link the z-function module.
    5. Create partner profile: transaction WE20 and attach the message type and process code.
    6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
    Try the Trasaction WE19 for testing your inbound and outbound IDOCs
    Good Luck and Reward me for the same
    Thanks
    Ashok.N

  • 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

  • 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

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

  • 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

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

  • Reciever port blank in control record of idoc.

    Hi,
    I am sending IDOC from  client 110 to 220 in R/3.
    In Client 220 reciever port is blank in control record of
    Idoc.Do I need to do some kind of settings for this.
    Any help appericiated.
    Thanx.
    Rekha.

    Hi Rekha;
       Are the ports properly populated on the outbound IDoc (from client 110)?
    Cheers,
    John

  • Port field is blank in Control record

    Hi Experts,
    I am sending the idoc from R3 to XI to R3, the idoc successfully came to R3 to XI and XI to R3, but in reciever r3 system when i check idoc control reocrd, the port field is blank.
    Can you please help me why it is blank.
    Kind Regards,
    Praveen.

    Hi,
       If you have chosen the "Apply control records from Payload" check box in Receiver IDOC adapter configuration, then you have to look at what value did you map the RCVPRT field in your message mapping.
    If "Apply Control recrds from payload" is not checked, then you have to re-check if your port configuration is properly done in IDX1 transaction in your XI box.
    Regards,
    Ravi

Maybe you are looking for

  • SSRS Execution Service Render Method stopped working

    Hello SSRS Profis! I'm having the following Problem: I was trying to integrate SSRS in my Company-Software, and until today it went quite good: Its an ASPMVC 5 project with WCF-Services, and in these i had methods to render reports with the help of t

  • I am unable to install the CSXS Infrastructure 4.0.2 update

    Every day I can see the adobe cc update icon, it makes me feel very bad, but always be updated each time an update fails, which is why this road is not? There are pictures and the truth: No matter how retry, the result is the same: Update failed! Ple

  • Usb video

    I am looking at a couple of devices for Powerpoint presentations and have come to the realization that I will not be able to do composite video out from my macbook pro with the mini-display port. So I found a couple of pico/led projectors that have u

  • Why Do I Get "Unknown" Publisher?

    I am wondering why I always get an "unknown publisher" every time that I try to install the Java EE 6 SDK on my Windows 7 64-bit system?? I always get "Oracle" as the pubisher when I first install the Java Standard Edition SDK. What goes wrong in the

  • Cannot execute sql

    Hi All; Cannot execute sql inquiry? Exception Details: org.apache.jasper.JasperException java.sql.SQLException: [sunm][SQLServer JDBC Driver][SQLServer]Line 6: Incorrect syntax near '%'. Object selName = textField1.getText(); try{ getSessionBean1().g