Receiver Business System Connot find Inbound Interface - IDoc to File

Hi Everyone,
I am doing IDoc to File Scenario.....Idoc got triggered from SAP system and successfully posted to SAP PI.
Now when I check in T-Code IDX5 in PI, I got one message. When I double click that I am getting following error:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also When I am selecting Receiving Inbound interface for Receiver system, I am not getting any interface by default.
Please help me out.
Thanks & Regards,
Sudheer

Hi everyone,
Thanks for your quick responses.
Actually I am doing IDoc to File Scenario from blog which consists of Conditional Receiver Determination
"SNDPFC"
Here is the Explanation given in that blog:
In most instances, a new Receiver Determination would be created. However, given that in this scenario the combination of the sender service (i.e. u201CGL1u201D) and interface (i.e. u201CMATMAS.MATMAS04u201D) will be used by every student, each student will instead be adding their receiver service to an existing Receiver Determination
11. In the Condition column on that same line, left click on the question mark help icon
12. In the following Condition Editor pop-up window, left click on the help icon in the u201CLeft Operandu201D field
13. In the following Expression Editor pop-up window, select the u201CContext Objectu201D radio button
14. Use the drop drown to locate and select the u201CSNDPFCu201D field and u201COKu201D
15. Back in the Expression Editor, leave the u201C=u201D Operand as is
16. Enter your group number in the u201CRight Operandu201D and u201COKu201D
17. u201CSaveu201D and validate your u201CConfigured Receiversu201D as seen below:
I did not understood this Conditional RD.
Apart from this all configuration are correct.
Thanks,
Sudheer

Similar Messages

Dynamically change Receiver Business system in message mapping

Dear all,
I would like to change the receiver business system in the message mapping that is used in the interface determination. I do understand there is an enhanced receiver determination where I can use a mapping but that is not what I am looking for.
I think this should be possible if we can change the appropriate value in the SOAP(message) header.
Possible candidates I can think of by looking at the SOAP header in SXMB_MONI are
1. SOAP:Header- SAP:Main- SAP:Receiver- SAP:Service
2. SOAP:Header- SAP:OutboundBinding - SAP:OutboundBindingEntry - SAP:ToServiceName
Q1. Which one of the above is relevant while identifying the receiver agreement ?
Q2. What is the best way to access them from the mapping(preferably from a UDF) ?
Thanks in advance.
Cheers
danus
PS: I have tried to set "http://sap.com/xi/XI/System","ReceiverService" in Dynamic config & ReceiverService, BusinessSystemReceiver and ReceiverSystem in the Containers Transformation Parameters, but didn't get the expected result.

Chidambaram,
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
Go through the following link:
[Receiver Determination enhancement|http://www.****************/Tutorials/XI/RecvDetermination/Enhancement.htm]
Hope your problem gets resolved.
Regards,
Kiran Bobbala
Edited by: kiran Bobbala on May 7, 2008 5:47 PM

"Unable to find inbound interface"

Hi all,
I have an error in sxmb_moni. Everytime I click on the red flag, I get the error, "Unable to find inbound interface". I already checked namespaces and SCV in IR. I also checked Interface Determination in ID. They are all correct. I have already tested my config in QAS, and everything went well. I'm having problems right now in PRD. Can somebody help me? thanks.
When I run Test Tool Config, I get the following error:
Interface Determination
Thanks.
Regards,
IX

Error when determining the inbound interface: Problem evaluating a condition: Exception
CX_SWF_RLS_RULE occurred (program: CL_SWF_RLS_CONDITION==========CP, include:
CL_SWF_RLS_CONDITION==========CM00Q, line: 160).
Payload problem check these solved threads:
Error
Error in Receiver Determination
regards,
Abhishek

FILE TO IDOC SCENARIO-Receiver Business system ECC showing Red

HI
     In File-idoc scenario Business system showing red status in RWB .And i have given the role for the business system as application server and configure related integrated server . But the error in a RWB for the ping and self-test is as follows
     Unable to log on to system buss_ecc_200 in language en with user PIRWBUSER .
I thing from XI side every thing is ok. But for bussiness system side ECC might miss some configuration .
       could any help in this issue:
regards..

Hi
Please try one of the followings:
1) In Configuration --> Business service --> Service --> Adapter specific identifiers. Give logical system name for the sender system (e.g XI_00_800)
2) In Design --> mapping objects. Give all information of sender n receiver in EDIDC40 segment and
   In configuration --> receiver communication channel in that enable the checkbox take sender from payload.
3) In configuration --> Receiver Agreement --> Header mapping --> Sender Service (Give XI1 i.e ur sender system).
Also check the RFC destination that is the major problem with idoc...

Business service is not working in sender side but business system is working soap to idoc but why like that

i have scenario SOAP to IDOC
when i'm using business service in sender side it is getting an error as follows
sender message can not convert to ALE Logical system
in this i'm using altova spy as testing tool
my sender interface is asynchronous
but when i'm using business system everything is working fine
In sender side i'm using soap adapter,i checked the logical system everything is fine
mainly the problem is why it is working when i'm using business system rather than business service
my pi version is pi 7.0
thanks in advance
regards
satish

Hi Satish,
You are sending IDOC's to SAP system right. we should create Business system not business service.
so we should create the business system as web AS ABAP in SLD and import the same in ID.
When we create the business system in SLD the logical system name is assigned for the business system. like SAPCLNT100...It plays a key role in IDOC scenarios.
sender message can not convert to ALE Logical system
Reasons for this issue is
1) logical system name is unable to read from SLD for that corresponding business system.
Goto business system click on Adapter specific identifiers from the menu --> read from SLD.
it will automatically fetch the logical system name from the SLD.
2) Sometimes the logical system name will be deleted from the business system in SLD.
Delete the business system and re-create it, and follow the above procedure.it will resolve your issue.
Regards
Bhargava Krishna

[Forum FAQ] Cannot perform a backup schedule via Windows Server Backup and receive "The system cannot find the path specified." Error

Symptom One
You attempt to
schedule a backup every day via Windows Server Backup on Windows Server 2008 R2. At the beginning, the backup works without issue. But after a few days it failed and you receive the error “Windows Server Backup:
The system cannot find the path specified.”
Cause
The issue may occur if there is
no shadow copy storage space available on the backup volume.
Verify
You can use the List ShadowStorage command to check if you have enough storage space to store the newly created shadow copy. If you've reviewed the size of the backup snapshot and discovered
that there is no allocated space for the storage association, you need to resize shadowstorage.
Solution
You could run the command below to create shadow copy storage space on the backup volume:
vssadmin resize
shadowstorage /for=<ForVolumeSpec> /on=<OnVolumeSpec> [/maxsize=<MaxSizeSpec>]
More Information
Vssadmin resize shadowstorage
http://technet.microsoft.com/en-us/library/cc788050.aspx
Symptom Two
When you add
another external hard drive to backup schedule via Windows Server Backup on Windows Server 2012, it fails and you receive the error “The System cannot find the path specified.”
Cause
The issue is due to the
Original Destination Disk was not attached to the server.
Verify
You could check the disk status in Disk Management to see if the Original Destination Disk is offline or removed.
Solution
You need to attach
Original Destination Disk to the Server then choose another external hard drive as backup target. After that, you could remove the Original Destination Disk.
Workaround
To work around this issue, please use the WBADMIN command line tool to add disk.
WBADMIN ENABLE BACKUP -addtarget :{ DiskID}
The AddTarget parameter takes disk ID as parameter. It can be retrieved by running "WBADMIN GET DISKS" command.
Example:
WBADMIN ENABLE BACKUP
-addtarget :{ aa123d14-bba0-1dd9-0d93-80aaaa6bbb63}
More Information
Wbadmin enable backup
http://technet.microsoft.com/en-us/library/cc742130.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

good

Error in IDOC ststus , for interface IDOC to File

Hi All,
iI am doing IDOC to file interface , in which i am using IDOC Orders05, we are using the same IDOC for other interface to connect with DOTNET connectors , when i trigger the IDOC ORDERS05 for my interface when i check the ststus , in which it is pointing the to partner No and Port to that dontnet, not to my Iterface for SAP XI , anyone there to help me in this isssue
Thanking you
Sridhar

Hello,
While sending Idoc you will be providing the Port which in turn needs RFC Destination and this is one which takes the document to External system configured in RFC.
If you need to send the idoc to External Systems other than R/3 then you need to use T type connection which uses JCO for estblishing session. if it is R/3 then requires logon credentails and type 3 for configuring RFC.
HTH
Rajesh

SLD - Export Business System: 404 Not found while downloading ZIP-File

Hi, well we did a complete export of SLD to another XI-System. This worked fine so far except that one business System was not properly "installed" in SLD.
Therefore we want to export this single business system via option "Export" but we receive an 404 Error: The requested resource does not exist. when trying to download the given zip-file!
I read in OSS that this error occurs in XI-systems with SP <12 and SAP suggest to upgrade to 12
Well that's not an appropriate solution!
Does somebody can help how we can download this zip-file with the business system in it?!
Or is there some workaround i am not familiar with?!
Thx in advance!

Ok Prateek,
we had two same Technical Systems with two differnet hosts given in the SLD of DEV & PROD System.
After decision to devide both systems, means to seperate SLDs we copied the whole SLD from DEV to PROD. So there were some conflict with this two technical systems because during import of CIM-Data the business systems got switched up.
Therefore we thought we have to export the business system given in DEV SLD to import this business system in PROD SLD. But the workaround is that we simply assign the wrong imported business system to the right technical system (in PROD SLD)
That's it! br

Content Based Routing, but same receiver Business System

Hello experts,
I'm working with SAP PI 7.11 and I need to process different incoming EDI messages.
These EDI messages have the same name (except for the timestamp), so I really need to read the files.
Based on 2 fields in the message, a different ABAP mapping must be chosen. The final receiver is always the same, the SAP backend system.
So I checked the Receiver Determination, but adding receiver rules doesn't make any sense because the sender is always the same and only 1 interface determination can be created in that case. Thus only 1 ABAP mapping can be referenced.
Please advice.
Thanks a lot
Dimitri

Thanks for the tip!
I moved my xpath expression from my receiver determination to my interface determination because there I cannot should the source structure.
Did a quick test and it looks fine. I my trace I see different ABAP mappings are being taken.
Thanks again.
Dimitri

No service for system ECC R/3 , for IDOC to file interface in SM58

Hi all,
I am geting a error No service for system XXXXX, client 100 iIntegration Directory,
when i go to IIDX2 and Updating the IDOC type , i am not able to add it is give me a error 100
please help me in this
thanking you

Hi,
Check the threads Idoc adapter - No service for a system in Integration directory
No service for system ... in Integration Directory
Thanks!

Logical system and business system

Hi experts, please help me with the below questions---
1) What is the diff between logical system and business system?
2)what is the difference between logical system(defined in R/3) and business system (defined in SLD) in idoc to file scenario.
3) Is it require to give the logical system name of the xi server(Which we define in idx1 port) to the 3rd party system(Application system at the FTP side) to carry out file to idoc scerario?

Hi,
Business System :
1. Business systems are logical systems, which function as senders or receivers within XI. Business systems can be SAP systems or third-party systems. Depending on the associated technical system.
2. Business Systems should be mandatory used when dealing with Idoc's and Proxies .
Business Service:
1. Business Service requires manual adding on Inbound and Outbound Interfaces, Business Systems do not.
2. Business Services are maintained across environments and so, their names cannot be changed. Business Systems names can be changed across environments by providing SLD level transport targets.
3.In the Business Services we cannot maintain the Group and Targets in SLD. For Ease in transporting your ID/Configuration objects Groups and Targets are used in SLD for Business Systems.
4.Business Service has no SLD Entries and No Assigned Products and SWCV's
Regards
Sangeetha

Integration directory : select IDOC interface for WAS business system

Hi,
While adding a receiver determination for an WAS business system, I do not get any IDOC based message interface from the design repository proposed for my business system in the popup dialog.
The only interfaces that appear are for the non SAP standard SWCV that we added to the business system. But no interface for the APPL 5.0 SWCV ( or BASIS 7.0 ) appears.
In the SLD this component is correctly listed for that WAS .
If I remove all the default search criteria , eventually, the in terface appears but after selecting it I get a message saying :
"Message Interface does not exist in any software components installed on this business system "
Since everything looks ok in the SLD I'm puzzled. How does this look on other systems ?
Any ideas
( The business system was updated from APPL 4.70 / BASIS 6.40 to APPL 5.0 / BASIS 7.00 some time ago but I don't know how it look before the upgrade of the business system )
rgds
Dirk

Hi Bavesh,
Yes, It's correctly listed. I did not manually link these components to the technical/business system. This happened automatically by the SLD data collector service. I also cleared the SLD cache several times,
rgds
Dirk

Business system for idoc reciver communication channel.

hi gurus,
iam doing one file to idoc scenerio.
for defining reciver idoc adapter ,which type of businees system i required that is configured in SLD.
pls guide me .
warm regards.

Hi
You can use th Buiness system as a receiver for IDOC.
Making sure
1. the LS of the system(R/3) is same in the SLD and it is also reflecting in the adapter specific attributes in the ID.
2. Use the same LS name for the BS pointng to FIle in the SLD.
Complete the IDOC configuration from XI
1. Create the RFC dest from XI to ECC
2. Create the Trfc port and call this RFC dest created..
3. Use this Trfc port in the IDOC receiver
On ECC:
Make sure the Partner Profiles is created properly.
it is suggested to use always the business systems when you deal with IDOC and Proxies.
Edited by: Nisar Khan on Feb 27, 2008 1:31 PM

Idoc not visible in Business system

Hello Experts,
I am trying to configure a scenario where in I am trying to use the IDoc ZCNOSE_PRICAT.PRICAT02.ZPRICAT1.
However, this IDoc is not reflected in the business system in which I am using.
I have already released the extension from the backend SAP system.
Can you please suggest what I am missing such that the extension is visible in the Business system.

Hi,
You imported the idoc structure into the ESR, under a specific SWCV.
Make sure that SWCV is linked to your Business System in the SLD.
Kind regards,
Dimitri

Failure in retrieving business system with Idocs

We implemented a B2B scenario (SAP R/3 4.7 ->XI->XI->SAP R/3 4.7 ) in which each SAP R/3 + XI act as a Business Party with a business service assigned to internal business system.
Trying to send IDoc from one Business Party to the other
The IDoc got through from the source system to the target system OK, The target R/3 sent the ALEAUD ack back but the ALEAUD sent from the target R/3 contains the internal business systems names and the XI did
not convert it back to address the services that sent it from the source system.
The message gets to the source system with the internal names of the target system so it falls due to unrecognized systems.
the error at the source target for the returning ALEAUD is OUTBOUND_BINDING_NOT_FOUND
SAP dev support claim that the source is the header mapping from XI1 to XI2.
Any work around for this?
Thanks,
Udi

I have an idea.
call me : 0526116713
Nimrod

Receiver Business System Connot find Inbound Interface - IDoc to File

Similar Messages

Maybe you are looking for