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.

Similar Messages

  • Only since I started using Firefox, Hotmail has now 2 different senders for my e-mails, me and this new unknown : " **** ", that it insists on choosing as the sender , instead of me, and then gives me this message : invalid sender email address ... ??????

    I did not have any problems at all before I started using Firefox ( great !!! ) , that's why I assume it may be Microsoft making it hard for " other than IE users " to use Hotmail, as similar events have been proven true in the past, regarding Microsoft and its monopolistic policies , or is it a true technical incompability ???

    I moved the file formhistory.sqlite to another file folder. I then started Firefox up again to see if it worked or if I needed to start it in Safe Mode. No need for Safe Mode. It now works exactly as it should. Thank you so much!!

  • BAM. Track message payload inside dynamic send port

    Somehow Biztalk 2010 BAM fails to track message payload inside dynamic send port. Messaging properties and Context properties (from our own property schema) are tracked correctly.
    I'm using XMLTransmit with specified document schema property on the send port, but this does not help.
    Tracking the same properties on Receive port is successful.
    What could cause this kind of behavior?

    I do not use ESB. There are only simple send ports. I have been trying to track message payload either from static and from dynamic sen ports. In both cases it does not track anything (only null values).
    I've trying with simple solution: one send and one receive ports. No mapping or other stuff. Tracking profile had the same fields set, both with two ports mapped: one send, and one receive. Receive port line is filled with correct values from message, while
    send port line stays empty (null).
    What could cause such behavior?

  • How To use External Message To Send IDOC From XI To R/3

    we need to split one source message to several IDOC To
    R/3,But Standard Imported r/3 idoc contains only one idoc per message,so we export the standart idoc to a
    xsd file and change it to a  multi "IDOC" segment structure and import back to xi again,after that,we create a message interface use the imported
    message type and use it to send IDOC to r/3 via idoc adapter,but at the "call atapter" step it gernarate a
    error:"Unable to interpret IDoc interface MI_IDOC_IN".
    what we should pay attention to when use external message
    to send idoc to r/3?
    (when use the imported idoc message to send  single idoc per message,it is no probelm)
    thx

    The way this works is:
    1. In your Message Mapping use the External WSDL defintion that you loaded after tweaking the "IDOC" Occurance.
    2. Then in your INTERFACE MAPPING use the orginal IDOC Name that you imported from R/3.
    3. Use the original IDOC Name in Integration Builder too.
    This should work.
    Thanks
    Ashish

  • 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

  • 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

  • Send IDOC Messages to SAP

    I have a text file which contains lots of records. I have created a schema for that text file.Then I mapped this schema with IDOC (Acc_Document03)schema.Now I want to send this IDOC message to SAP.There is not shown any errors by BizTalk admin console.But
    the message is not reached to SAP.But when I  send this IDOC message to a location through File adapter instead of SAP adapter then it has reached there .Why this is happening ?
    Please also tell me how to send multiple IDOC message to SAP ?

    Hi Glenn.
    I got the following error:
    The adapter failed to transmit message going to send port "Interplx.SAP_SendPort" with URL "sap://CLIENT=130;LANG=EN;@A/10.151.97.51/00?RfcSdkTrace=False&AbapDebug=False&ListenerGwHost=10.151.97.51&ListenerGwServ=SAPGW00&ListenerProgramId=BTSIDOC_DEV-".
    It will be retransmitted after the retry interval specified for this Send Port. Details:"System.Xml.XmlException: Start element 'ITEMNO_ACC' from namespace 'http://Microsoft.LobServices.Sap/2007/03/Types/Idoc/3/ACC_DOCUMENT03//701' expected. Found element
    'ITEMNO_ACC' from namespace ''.
    Server stack trace: 
       at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)".
    Prakash

  • 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

  • Keep getting invalid destination port message every 30 sec in Console

    Hi, this is my first post so be easy on me. I have been checking up on a possible attack on my website and looking for things that may have caused visits/dowloads to blow out. 
    While do this I looked at my Console app on my iMac 2.4 Ghz Intel Core 2 Duo running 10.6.8 and notice that every 30 seconds there is a dual message:
    6/09/11 4:39:38 PM imagent[161] Unable to create APS daemon connection: (ipc/send) invalid destination port
    6/08/11 4;39:38 PM imagent[161] Unable to set enabled topics: (ipc/send) invalid destination port
    This action then repeats itself every 30 seconds non stop. Every now and then the odd "normal" error will appear with various apps but this is constant.
    The bottom of the Console window reads 4001 messages from 5/09/11 12:30:21 tp 6/09/11 4:57:08 PM
    I have looked on the web to try and find out what the 161 refers to and what meaning of the phrases are, but none address 161 specifically and most seem to be in foreign languages.
    Your help will be greatly appreciated
    Matt

    Thanks for that. I had a look at Facetime and had vitually forgottten about it having never used it. I tired about 8 months ago and coould never log in. All I ever got was the spinning wheel at log in, which is exactly what I have just got know as I tried to open it again.
    I am wondering if it has been going throogh this process ever since.
    Anyway I looked into the ~/Library/LaunchAgents and the nearest I can find are com.apple.apsd-ft.plist, com.apple.FTMonitor.plist, which may relate to Facetime and then there is com.apple.imagent.plist
    which is the one that seems to be causing the problem.
    Now when I read your reply and did the search using your parameters and the very first reply said that:
    "As you probably know, you can get FaceTime invitations even if you have quit FaceTime. That feature is provided by "imagent".
    Unless you have configured the FaceTime > Preferences... > FaceTimesetting to "OFF", you are still using "imagent" (and a couple of other support processes) even if you have "Quit" Facetime.
    Once you set the preference to "OFF", imagent will go away, but you will not be able to receive any incoming FaceTime invitations until it is turned ON again."
    Well as I can't log into Facetime I can't get to Preferences, to turn it off.  Now bear in mind I am new to this type of thing, but I have heard some people say that you can throw plist's in the trash and that the application regenerates a new problem free version.
    Is this what you suggest I do and if so which of the above three would be the one(s) to delete?
    And thank you very much for the very quick reply, much appreciated
    Matt

  • Sender Port in FILE to IDOC scenario

    Hi all,
    I am trying to do a File - SAP XI-IDOC scenario.
    The idoc which is getting created in XI is having senderport as SAPABC where ABC is my XI system id.
    i have not craeted this sender port and i am not able to find it in idx1 tx.code of XI.
    Can anyone please tell me how and where is this port is getting created. Will it get genarated automatically by the XI system for posting the idocs?
    thanks in adavance
    Jagruthi

    Hi Jagruti,
    Please refer to these blogs and threads:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
    /people/sravya.talanki2/blog/2006/12/25/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-i
    /people/sravya.talanki2/blog/2006/12/26/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-ii
    /people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
    /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
    Hope these blogs help you.
    Regards,
    Sarvesh Desai

  • Sender Port Error in SAP ECC for IDoc

    Hi,
    I am creating scenario IDOC -> XI -> JDBC with Customer Master IDoc.
    After sending it with we19 he said "IDoc sent to SAP system or external program".
    In we02 and we05 the IDOC it says "Data passed to port OK".
    But in SM58, the IDoc ends in error saying
    Transaction IDX1: Port SAPIDST100, client 600, RFC destination contains error.
    What I identified that the port SAPIDST100 is the sender port in the IDoc being send. However, for PI we do not need to maintain sender port.
    Business Systems:
    Sender : SAP ECC
    Receiver: SAPPID
    Kindly provide your inputs.
    Thanks
    Rahul

    Hi Rahul,
    thanks for the information that your scenario is working fine.
    But i want to clarify some points:
       - If you send out an IDoc from an ECC system, the senderport is filled with SAP+<system-id> by the SAP IDOC API,
         i.e.  if your system id is "ABC", the senderport is "SAPABC"
          => your senderport SAPIDST does not match this template, so i assume you entered the value for the senderport
         manually in the idoc test utility WE19
       - if you send out an idoc, only the receiver port must be created in transaction WE21, it is not necessary to create
         the senderport in WE21, this is not necessary and did not solve your problem
      - the idoc was send from ECC (application system with application IDoc metadata) to an XI/PI system (basis system      
        without application idoc metadata
       The IDoc adapter on the pi system must analyze the IDoc segments and must know the idoc application metadata,
       but this is not known. So the idoc adapter on PI side looks at the senderport to identify the sender.
       In transaction IDX1 an rfc-destination can be configured to point to the sendersystem with that senderport
       With this rfc-destination  the IDoc adapter tries to read the idoc aplication metadata from the ECC system and stores it on PI side.
       If there is no rfc-destination configured in transaction IDX1 on PI side you get the error mentioned in your request.
       I assume that in transaction IDX1 somebody configured the correct RFC-Destination.
    I hope this clarification helps you to understand the error and the solution.
    Kind regards,
    Andreas Dahl

  • Changing sender port in IDOC scenario

    Hi,
    i am trying to change the sender port in XI (name of the XI-System is CXE) to ZSAPCXE.
    I have successfully done the mapping of the IDOC header field (populating the field SNDPOR with ZSAPCXE).
    Now i have started my test scenario - sending an IDOC from source system...
    In transaction SXMB_MONI i can see, that the mapping was ok (<SNDPOR>ZSAPCXE</SNDPOR>).
    But if i start transaction WE02 in the target sytem the port of the incoming IDOC is SAPCXE. What is the problem?
    Thanks for any help!

    Thanks for your help.
    So you say, there is no chance to change the sender port?
    But why is in transaction WE02 in the target system the inbox port automatically set to SAPCXE?
    Is there a user exit for the function module MASTER_IDOC_DISTRIBUTE or anything else available?
    Is there a chance to change the sender port in the target system before processing begins automatically?
    Is there no option within XI to overwrite the default?
    I cant believe that...
    Thanks for any ideas

  • Sender port in an Outbound IDoc

    Hi
    Can someone please mention where is configuration for IDoc sendor port.
    We generally give Receiver port information in outbound parameters in partner profile(WE20). But there is no place where we give the Sender port information.
    When an outbound idoc gets created, in the control records you can find the Sender port. Can someone tell from where this port is picked up.
    In most of the cases I can find port name SAP<SYSID>. Is this something SAP standard. ?
    Thanks,
    J.

    Hi Brad,
    Can you tell me where its hard coded. which program/func module. ?
    Thanks,
    J.

  • 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

  • When and how does the message context get removed from the message when we use pass thru send port

    Friends,
    i have a doubt regarding message context.
    Assume i have used XMLRecieve pipeline in the receive side to receive the message so that the message context is created. I.e properties are promoted/written.
    now if we use pass thru transmit pipe line at send side, how and when does the message context get removed from the message?? Since pass thru does not have any stages/components, how does the message context removed and sent out a pure message to destination???
     i mean what exactly happens here to remove the context??
    Ravindar

    Thanks for the reply.
    "The Context is created by the Adapter, regardless of any Pipeline or Pipeline Component.  It has nothing to do with PassThrough vs. XmlReceive, although XmlReceive will write Promoted Properties to the existing Context,
    as can any other Component."
    yeah yeah, adapter does create some properties in context. You are right, i am aware of it. I just missed to explain it clearly. what i meant is addition of context properties will not happen if pass thru used. Thanks its clear.
    "No.  The Context already exists on the Message when it comes from the MessageBox and
    is equally available to any Component in any Stage.  The Context that hits the Pipeline is whatever was last Persisted, either by a Receive Port or Orchestration.  It is not created by the XmlAssembler (XmlTransmit)"
    You are right , the context already exists on the message while it leaves the receive port, and once it persists
    to message box the context and message context gets stored in messages in relative tables.
    Now as you said the components get the message from the last persistence, assume i have a send port(with passthru)
    subscriber and a orchestration subsrciber for this message.
    Orchestration gets the message with context right!!
    if the send sendport(with passthru) also gets message along with context, then where is this context removed/demoted
    while sending it out?.  i guess as per SAAkhlaq said,
    here sendport(with passthru) should get a pure message without context as passthru used. 
    or is it that ultimately send adapter removes the context completely?
    or is it something like biztalk run time load the context from database into cache and both orchestration and send port gets pure message, and if needed they use context from cache???
    sorry i may be troubling you, but i am confused. i hope i am not creating any nuisance with this
    post.
    Ravindar

Maybe you are looking for