IDOC ( WS-- XI -- R/3) Receiver Port

Hello i am having issues with IDOC post on R/3 via XI. The issue is with receiver port. I am populating values of Message variant and message function in Mapping and nothing else were populated.
As per SAP documentation RCVPOR variable will be populated from receiver adapter whether "Apply control record from payload is checked or not".
This value RCVPOR is being populated control record of idoc when "Apply control record from payload" is unchecked . when its checked its not . please comment

Hi Bujji,
did you see the RCVPOR in your payload?? if yes then select all the three check boxes in adapter refers to payload.
basically there are two ways to send Receiver and Sender details to R/3, one is from payload and the other is from configuration.
if you check the "Apply Control record from payload"
along with this you shd check "Take Sender from payload" and "Take Reciever from payload". then it should work.
if you uncheck Apply control record from payload then it will take these details from SLD. Make sure that these are given there.
Regards,
Sukarna

Similar Messages

Receiver port missing in inbound idoc

Hi All,
I am posting idocs from XI to R/3. All the ALE settings have been done correctly. Idocs were being posted to R/3 successfully, however suddenly the idocs started failing in R/3 with error: EDI: Partner profile inbound not available
When i checked the control record for the errored idocs i found that the receiver port is missing. I am not sure why this is happening as in the idoc adapter we have provided this and also the idocs were being posted successfully with the same setting.
Pls help to find the root cause for this problem.
Further what would be the best way to reprocess these failed idocs? The number is huge around - 30,000 hence manual processing through we19 is not possible. Also BD87 cannot be used as i need to edit the idoc to add the receiver port information before reprocessing.
Kindly suggest. Any help in this regards would be welcome.
Thanks
Anand Chavan

hi
Go thru the below blogs
check the partner profile settings
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/frameset.htm
Idocu2019s not posted in the receiver SAP Systemsu2026.
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
Troubleshooting File-to-IDOC Scenario in XI.
Troubleshooting File-to-IDOC Scenario in XI.
reward points if helpfull
regards
kummari

Problem with distribution model receiver ports

Hi,
I am facing a problem with distribution model.
I am using Distribution model for material classification data. I am sending my classification data using CLFMAS message type to one of the receiver. Again another person also sending classification data to another receiver.
But both objects will run at different times.
Problem is for every run and every change it is creating 2 idocs instead of 1 idoc.
I am able to create an IDOC with my changes for classifications. But it is creating 2 idocu2019s instead of creating 1 idoc. Because of there is another distribution model with same message type with different receiver port has been configured. I.e. reason it is creating 2 idocu2019s and sending to both the revivers.
When I run my changes It needs to create 1 idoc and send to my receiver port. If another person run his job it needs to create another idoc.
So how will I filter distribution model based on receiver port? it needs to create only 1 IDOC ..

Hi kotesh,
A similar issue.
check if this will help.
Do the following:
Go to TOOLS>ALE Development>IDoc Type Development> WE81 and create a new message type and give it a different name - say ORDERS2. Use WE82 to link it to an IDoc Type - say ORDERS05. So now you will have two message types linked to the same IDoc type. Each message type can now be referred in different logical systems without any clashes.
Now you can use BD64 to build your model using message types ORDERS and ORDERS2 without getting the multiple recepient error message.
Then use WE20 to set up each partner profile using your defined output conditions in message control to trigger the creation of the IDoc. Now you will beable to send the same Idoc type to different recepients.
source:http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/sap-distribution-model-3008763
Regards,
SuryaD.

"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

Inbound IDOC receiver port not getting filled in

Hi All,
I checked the WE20 configuration and it is fine. Just wanted to check if there is any other sap configuration which might be missing.
The IDOC is coming from a web server and they confirmed that they are filling the receiver port information while sending, but in the IDOC that we receive in SAP the receiver port is coming as blank.
Any pointers will be appreciated.
Thanks,
Anil

Hello Anil,
When they say they are filling receiver port that means they filling EDIDC-RCVPRT, please note with out receiver port you will not be able to receive the Idoc.
It means this value might be cleared somewhere in SAP. may be user exit or BADI or enhancement. what you can do is try to create inbound idocs by populating receiver port using WE19 and check whether the created idoc contains this value or not.By doing the you can get an idea where this value is disappered.

Idoc not found in the receiving system

Hi Experts,
In the sending system idoc status is 03 (Data passed to port OK), but in the receiving system the idoc is not there. How to rectify this error?
Thanks & Regards,
Soumya.

Hi Soumya,
Check the RFC connections, becoz in the sending system once the IDOC is sent the status becomes 03 it does not check whether the IDOC has sent to the received system, if there are any errors before sending the IDOC it will not send and the status will be 01, so check the RFC connections at sending and receiving systems.......
Reward points if this helps............
Regards,
Ravi G

Idoc in status 03 - not received by receiving system

Hello All,
I have researched a lot on this topic on the forum - but what I am facing is something peculiar - so posting the complete scenario.
I have three interfaces based on change pointers mechanism where change pointers have been activated for message type HRMD_A.
There are three distribution models which filter the same message type and send to receiving system GIS – for the logical systems:
FI
Concur
Russia
When IDoc is triggered using standard program RHALESMD (transaction RE_RHALESMD - HR: Evaluate ALE Change Pointers), there could be three or less IDocs produced depending on the filter criteria.
For example, you could have an IDoc each for all above three partners.
When the above program is triggered in the development system all three IDocs reach GIS.
All the custom code and configuration is transported from DEv to QA. When I trigger the above program in QA, not all IDoc reaches GIS. Others stay in the system in status 03.
If I check tRFC queue (transaction BD75), there are no IDocs in the queue.
If I use another program to change status from 03 to 12, the status changes, but IDoc still does not reach receiving system.
I have compared Dev and QA systems, deleted and generated partner profile, distribution model, port in QA – but nothing works.
Not all IDocs reach GIS.
I read on the forum that I need a commit work. But because I am using a standard program - RHALESMD - where do I commit work?
Your inputs will be helpful.

Hi Suneel,
Please go to transaction SM58 and check if the IDocs are stucked up on the t-rfc queue. If so, you can right click and choose Execute LUW to release them.
or
Execute the program RSARFCRD and get the corresponding Transaction id and then execute the program RSARFCSE for processing the entries in TRFC Queue.
Regards,
Ferry Lianto

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

BD64 - generate partner profile - outbound parameter; wrong receiver port

Hi all,
I'm using a distribution model (transaction BD64) for creating partner profiles in my system.
This works fine, exept for one thing.
The receiver port used in the outbound parameter is wrong.
It's using the tRFC port of the destination system instead of the tRFC port of the SAP XI/PI system.
If I send an Idoc it's now going directly to the destination system instead of going to XI/PI first.
I could modify this manually (which is a lot of work), but I would like to know how SAP determines which tRFC port is used when generating the partner profile and creating the outbound parameters.
Can anybody help me with this?
Reagrds,
Roy

Hi,
According to my knowledge, if you have a receiving logical system name is same as the RFC destination name, then the SAP will take the RFC destination properly and will generate the port automatically (for Ex: if you have a port A00..12 then it will create a port A..13). the generated port will be used in partner profile.
Or
Give a try by assign the RFC destination (The receiving logical system name and RFC destination name should be same) for a port and use it while generating the partner profile by using BD64 or SALE.
Regards,
Venu V

Overwrite Value from Payload for RCVPOR, Receiver Port

Dear All,
Can we overwrite value of receiver port (RCVPOR) from Payload?
The actual port value (For example SAP<SID>) will be specified in IDOC Receiver adapter.
If I want to replace this value with say ABC can I do it through mapping?
I tried using "apply control record from Payload" for IDOC Receiver communication channel but still the actual port value (SAP<SID>) is going to SAPR3 and not ABC.
I checked the help.sap.com link as well.
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/frameset.htm
As per my understandings, RCVPOR value will be picked up only from IDOC Receiver communication channel.
Can you please suggest?
Warm Regards,
Gouri

Thanks Prateek for replying.
Even my understanding is same that this value will not be overwritten. But I am not able to find any help.sap.com link or valid SAP Document which will clearly specify this.
I need to pass this ABC value into IDOC header Record. This value will be required by User as selection criteria while executing WE05 and WE09 reports on SAPR3.
This ABC value is nothing but the Application name and while executing above standard reports user will be able to differentiate application specific IDOCs if i provide this information in IDOC header .
Now I spoke to ABAP Team and he suggested to use RCVPOR filed for thsi purpose as it is present in selection screen of both WE05 and WE09 report.
So I wanted a confirmation through official document that we wont be able to use this field.

Biztalk Receive Port config (Routing Strings)

Dear Gurus:
I have set up BAPIs and RFCs and they are working correctly through the Send Port that is configured correctly for BTS 2004...
Moving onto Inbound IDOCS -0 the Connection settings in the BTS Receive Port:
We are using a routing string to connect (ICC). So in the correctly configured Send Port for the 'system' setting we have:
/H/LocalServer/H/xxx.xxx.xxx.xxx/S/3297/H/cpce601 (xxx.xxx.xxx.xxx = IP address)
The cpce601 is the application server and is appended to the regular routing string... It took Microsoft 2 days to help us get that set up originally (appending the application server to the routing string for a Send Port)...
Now on the Receive Port we have:
SAP Gateway Host and SAP Gateway Service as the required parameters:
Locally we have a server 'LocalServer' which then routes to the IP address then goes to the Application Server...
I can't seem to find a combination that works with our routing string and or application server in the receive port. I wish I could send a couple screen prints and this might make more sense (see link below for example)...
The root question is for SAP Gateway host I should put the routing string or some part of it. I thought the 'SAP Gateway Host' would be cpce601 (but not sure). I would think the SAP Gateway Service would have to be some or all of the Routing String.
Any help or pointing me in the right direction would be most appreciated!
Here is a link of the page I'm trying to get set up.
http://blogs.conchango.com/tamershaaban/archive/2005/01/24/873.aspx

Hello Gang:
The answer:
In the Transport Properties Box in the Receive Port, you use the entire Routing String (found in SAPLOGON.INI) and append the application server in the SAP Gateway Host field field (cpce601 in my case).
/H/LocalServer/H/XXX.XXX.XXX.XXX/S/3297/H/cpce601
In the SAP Gateway Service you use SAPGWXX (where XX is the System Number - sapgw13 for my example)
Also make sure your Program ID,Client, System ID, Username/Pass are in the other boxes.
I hope this helps someone else!
Message was edited by: Charles McGarvey

Error Propagation on a 2 way receive port

HI,
we have a 2 way receive port . The subscribing send port makes a web service call to a third party and the received response
goes back to the client via the received port.
All good if things are working! In case of any exception on the send port side, is it possible to propagate this exception to the client? any way to achieve this? Basically I want the client to be notified of any exception that occurs in the chain.
Please suggest.
thanks
MS

Hi MS,
All you need go do is enable "Propagate Fault Message".
Following the exact extract from MSDN on this context: "For the two-way send port, you can choose whether to forward SOAP fault messages on to the original caller
over a solicit-response send port by selecting Propagate fault message. If this option is not selected, BizTalk Server will generate a NACK first, and then suspend the message. If it is selected, BizTalk Server will treat
the message as a valid WCF response message from the external service and the response message will not be suspended because it is propagated."
If you need to handle this
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

Using XML String in the Scheduler Adapter in the Receive port

I have a requirement where I have to query the view in the Oracle database,and the View is like this
EmpNumber | Name | TermDate
E001 | ABC | (null)
E002 | DEF | 13-DEC-14
E003 | GHI | (null)
E004 | JKL | 11-NOV-14
E005 | MNO | (null)
E005 | PQR | 10-DEC-14
I am going to use the Scheduler adapter in the receive port.It should select the Records with the TermDate null and TermDate 7days ago from today. So here is how I want the selected records to be
EmpNumber | Name | TermDate
E001 | ABC | (null)
E002 | DEF | 13-DEC-14
E003 | GHI | (null)
E005 | MNO | (null)
In the other forum I found the sql command to do this is,
select * from EMP where TERMDATE is null or TERMDATE >= trunc(sysdate) - 7;
But I am not sure if the XML String in the Scheduler Adapter is correct
<ns0:Select xmlns:ns0="http://Microsoft.LobServices.OracleDB/2007/03/View/EMP"><ns0:COLUMN_NAMES>*</ns0:COLUMN_NAMES><ns0:FILTER>TERMDATE IN ('null','TERMDATE >= trunc(sysdate) - 7')</ns0:FILTER></ns0:Select>
Any help will be greatly appreciated. Thanks

Thanks Suleiman.
I am using the WCF-Custom Adapter to get the data from the Oracle database. And I am using the Scheduler adapter because to get data on a daily basis.In one of our other application we have used the query statement in the Scheduler adapter
Like,
<ns0:Select xmlns:ns0="http://Microsoft.LobServices.OracleDB/2007/03/View/VW_EMP_DEPT"><ns0:COLUMN_NAMES>*</ns0:COLUMN_NAMES><ns0:FILTER>PROCESS IN ('A','B','C')</ns0:FILTER></ns0:Select>
and it works really fine, it just select the records with the Process A or B or C. I dont know how can I select now with respect to data that is 7 days ago from today.Help me with it.

EREC: Multipal IDOC are getting created in receiver system for one IDOC

Hello Experts,
I ran in to one wearied issue in IDOC creation in Receiver system. I am running PFAL in sender system for only Person but 10 IDOC are getting created in receiver system. I don't know why is this happening.
This issue started popping up after we ran RBDAPP01-Inbound Processing of IDocs Ready for Transfer. We ran this to change IDOC to 53 status. Now I don't know what went wrong but Perner distribution is behaving
Appreciate your help.
Regards,
Krishna Bidwai
Losangeles USA.
818 527 0204.

Yes, employee is getting created after adding 0003 into the filter, but can u please answer my another question, i.e. PERNR in sender and receiver system should be same.
So in Receiver system (ECC) do i need to maintain external number range for PERNR?
Thanks

IDOC ( WS-- XI -- R/3) Receiver Port

Similar Messages

Maybe you are looking for