PI 7.3 receiver AAE idoc scenario-No receiver comm channel found in ICO

Hi,
I am working in PI 7.3 receiver AAE idoc scenario.When I try to configure Integrated Configuration(ICO),I am not able to see the receiver comm channel in receiver agreement.
What is the reason for this??I have configured the communication channel,but still its not shown in reciver agreement dropdown.
Please help.
Regards,
Sriparna

Hi Sriparna,
In PI 7.3 there is are two separate IDoc adapters: "standard" IDoc adapter and one that is dedicated for AAE (ICO). Make sure that you have used the right one - most probably not, which is why you cannot see the channel in the dropdown list.
Hope this helps,
Grzegorz

Similar Messages

Receiver AAE IDoc adapter

Hi All,
I have a doubt regarding receiver AAE Idoc adapter. There are three options available in java IDoc adapter namely Default, Manual and From NWA. In Default option, we just need to configure a RFC Destination in NWA but in From NWA option, we need to configure RFC Destination as well as Resource Adapter(JCA Connection Factory). So, I just want to know what is the benefits of using From NWA option over Deafult and what is purpose of configuring Resource Adapter in NWA?

Hi,
see the below link.
http://help.sap.com/saphelp_nw73/helpdata/en/bc/0341dd385945d49eb809c084cf3dea/content.htm
as per this link i should check the checkbox.
Configuring Acknowledgements for a Sender IDoc Adapter (AAE) Locate this document in the navigation structure
Procedure
    Choose the sender communication channel on which you want to enable acknowledgement settings.
    Choose the Parameters tab and then, choose the Ack Settings tab.
    On the Acknowledgement Parameters area, enter the following settings:
        System Ack Ok Requested
        Choose this option to receive XI system acks.
        System Ack Error Requested
        Choose this option to receive XI system error acks.
        Application Ack Ok Requested
        Choose this option to receive XI application acks.
        Application Ack Error Requested
        Choose this option to receive XI application error acks.
        ALEAUD Special Handling Needed
        Choose this option to enable the sender Java IDoc adapter to apply special handling to the incoming ALEAUD message. The adapter replaces the IDoc number of the ALEAUD message with the original IDoc number.
        Initially, the receiver Java IDoc adapter generates a unique IDoc number, which replaces the original IDoc number of the outbound message. This IDoc unique number is referred by the ALEAUD message. However, the ALEAUD message is not converted to an XI Ack message in this case.

Web Service to IDoc scenario: No receiver could be determined error

Hi. I am working on a web service to IDoc scenario. I am receiving this error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I've taken the XML message being sent to me and tested the mapping and I've completed the test configuration in the IB. Both work fine. Any ideas? I've been looking into this for a couple of days, so I've been through all the previous posts I could find.
Thank you.
Nicole

hi,
This is not related to receiverdetermination ,whether you creaeted or not.
It is somthing related to receiver systemwhich was configured in Receier determination.
check the target BS is correct or not or the inbound interface.
Did you configured the proper receiver technical system..
OR
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong.

Mail-to-Mail scenario - Problem with comm. channel not reading message

Good day,
I am setting up a Mail-to-Mail scenario, where a received e-mail with an attachment is both processed into a file, as well as a monitoring e-mail needs to be send. The attachment processing is an existing process and is still working properly, but my e-mail isn't send. I am using Java mapping to create the destination e-mail based on the source e-mail. Everything is set up in the Directory as well, and through the Test Configuration feature I have tested my new addition to the existing process, I am seeing the result that I am expecting. I have sent a test message and XI picks it up just fine and processes it which is tested by both SXMB_MONI and the resulting file from the attachment.
However, the monitoring e-mail is not sent. Using the runtime workbench, there is an error in the receiver communication channel, being the following error from the Audit Log:
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.messaging.util.XMLScanException: java.lang.NullPointerException; nested exception caused by: java.io.IOException: Parsing an empty source. Root element expected!
Looking through the Message Content, I notice there is a SOAP document describing the source message and two payloads. The first payload being the source message in XML format, the second payload is entirely empty. I suspect this empty second payload is causing the NullPointerException, but I am at a loss as to why the payload is empty. The Test Configuration showed me that the message gets through just fine, so what is going wrong?
Here is a link to the configuration of the communication channel, maybe something is wrong here: [Config of communication channel|http://roald.hoolwerf.net/images/cc-config.png]
My question is: What can I do to find what is causing the communication channel to receive an empty payload, and how can I solve this?
Searching for this issue, or the given error on both Google as these forums hasn't given any related posts, if I did miss them in that case I am sorry for posting and please refer to the related topics.
Thank you in advance for taking time to look at this question.
Kind regards,
Roald Hoolwerf
Edited by: Roald Hoolwerf on Feb 1, 2010 3:57 PM

Try this.
Unchecked the configure use authentication.
and use mail package (base64)

PI AAE = IDOC control data to ECC

Hi All,
I am using the JAVA IDOC receiver adapter to send idoc's to CRM as a test to just send idocs
Need help on the control records.
Things done
1. Passing data manually.
2. Idoc begin =1 and all segments = 1
3. Created Logical system in WE20 in CRM and created partner profile with inbound parameters.
4. Checked business system in ID and it reflects the logical system ; albiet same as the one created in ECC.
5. Created a dummy partner profile in ECC to act as XI sender
Now, can tyou please guide me how to fill the fields in EDIDC_40?
<EDI_DC40 SEGMENT="1">
         <TABNAM>EDI_DC40</TABNAM>
         <MANDT>100</MANDT>
         <DOCNUM>Should i give?</DOCNUM>
         <DOCREL>1</DOCREL>
         <STATUS>1</STATUS>
         <DIRECT>2</DIRECT>
         <OUTMOD>1</OUTMOD>
         <EXPRSS>1</EXPRSS>
         <TEST>1</TEST>
         <IDOCTYP>CRMXIF_ORDER_SAVE_M01</IDOCTYP>
         <CIMTYP>1</CIMTYP>
         <MESTYP>CRMXIF_ORDER_SAVE_M</MESTYP>
         <MESCOD>1</MESCOD>
         <MESFCT>1</MESFCT>
         <STD>1</STD>
         <STDVRS>1</STDVRS>
         <STDMES>1</STDMES>
         <SNDPOR>SAPXX1 ( DOne as part of document available- XX1 SID of pi)</SNDPOR>
         <SNDPRT>LS</SNDPRT>
         <SNDPFC>1</SNDPFC>
         <SNDPRN>XX1CLNT001 ( dUMMY CREATED IN CRM</SNDPRN>
         <SNDSAD>1</SNDSAD>
         <SNDLAD>1</SNDLAD>
         <RCVPOR>SAPXX1_SBX ( Port created in CRM)</RCVPOR>
         <RCVPRT>LS</RCVPRT>
         <RCVPFC>1</RCVPFC>
         <RCVPRN>CX1CLNT100 ( Partner profile created and inbound parameter assigned; also reflecting in the business system)</RCVPRN>
         <RCVSAD>1</RCVSAD>
         <RCVLAD>1</RCVLAD>
         <CREDAT>20140303<CREDAT/>
         <CRETIM>191016<CRETIM/>
         <REFINT/>1<REFINT/>
         <REFGRP>1<REFGRP/>
         <REFMES><REFMES/>
         <ARCKEY>1<ARCKEY/>
         <SERIAL>1<SERIAL/>
      </EDI_DC40>
I ahve something urgent to be delivered and need your help very badly

Hi All,
Exception caught by adapter framework: Sender Partner Number is not available
This is the error i get when i try to process my idoc for the receiver AAE IDOC adapter
Which value do i put in here and here is the config i have made.
1. WE20 in ECC with inbound parameters.
2. Logical system field in SLD filled for the business system i am using.
3. ICO config with Sender and receiver business components checked with the respective business systems.
4. I have also noticed that the sender business system in ID , where you check for adapter specific attributes is blank even though i have provided a logical system in SLD for the BS.Tried Clear SLD cache but still not reflecting. COULD THIS BE THE PROBLEM?
Kindly help as even if it fails i have to send over an idoc as part of my POC and i am dead late .

Idoc - Idoc Scenario - Call User-Exit

Hi,
I have an Idoc - Idoc scenario and after receiving the Idoc in the receiver system, I have to call an user-exit, what is the best way to do this?
Or is it possible to do this?
-naveen.

Hi Naveen,
Nice to see here,I think you can do the above scenario by using BPM,i guess we can achieve by using the BPM.
Please proceed with BPM,If you have got stuck in the middle please update the issue so that I can help you out my level best.
Thanks in Advance.
Chandu

Receive acknowledgement in file-to-idoc scenario

Hello!
I'm using guide "How to handle acknowledgement for IDOC", and for the first time I want to see an acknowledgement status in sxmb_moni.
I have passed all steps:
In CRM I have logical system P1DFILE, this is the system that sends an idoc to CRM.
Also, I have logical system C2DCLNT100 - this is CRM system.
First, I go to BD64, create new model view XI_CRM. Then, add message type:
Sender system - C2DCLNT100
Receiver system - P1DFILE
Message type - ALEAUD.
Then I create RFC destination P1D_001 to my PI server.
Then I create port SAPP1D using WE21
Then I go to WE20, choose my Logical System - P1DFILE. I already have the inbound message types (CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M). I add new outbound message - ALEAUD with receiver port SAPP1D.
Then I go to RBDSTATE, create variant SAP_AUDIT_SEND and enter:
Confirmation to system: P1DFILE
Message type: CRMXIF_PARTNER_SAVE and CRMXIF_PARTNER_SAVE_M
Then, in SM36 I shedule SAP_AUDIT_SEND as a hourly job (does this mean, that I will receive confirmations only every hour?)
So, what should I do to see ack in sxmb_moni?

Dear All,
For file to idoc scenario is there any possibility to get line items details or xml details i.e the segments and its related field details using reference id, transaction id or interface name or message id in SAP PI 7.0. I know we need to click each and every message in sxi_monitor and look for details.
For SAP(R3 System) I can create a report and set the job for specific time period so automatically it throws the details(like reference no, document date, invoice no from) in ftp path as .csv file. The same ftp path is maintained in program.
I wanted to check FTP--->PI postings and I have set the job at r3 system it is working fine and Im monitoring it too.
Now the end to end scenario is FTP--->PI--->ECC(R3 system). Please help.Many Thanks.

IDoc to File scenario... Receiver Comm Channel Error...

Hi Guru,
On the scenario IDoc to file, I'm encountering the ff error on my receiver comm channel (File Adapter)...
ttempt to access the 1 requested objects on 1 failed.
Detailed information:
com.sap.aii.ib.core.roa.RoaObjectAccessException:
Attempt to read object Adapter Metadata File | http://sap.com/xi/XI/System,
type AdapterMetaData from application REPOSITORY on
system REPOSITORY failed. Object does not exist. Detailed
informatio n: SWCV ID: << removed >>
does not exist in Enterprise Service Repository and
System Landscape Directory (ROA_MOA_NOTCOMPLETED)
<< removed >>
Attempt to access the 1 requested objects on 1 failed.
Detailed information:
com.sap.aii.ib.core.roa.RoaObjectAccessException:
Attempt to read object Adapter Metadata File | http://sap.com/xi/XI/System,
type AdapterMetaData from application REPOSITORY on
system REPOSITORY failed. Object does not exist. Detailed
informatio n: SWCV ID: e5a519a0766111dca2e8e95d0a115642
does not exist in Enterprise Service Repository and
System Landscape Directory (ROA_MOA_NOTCOMPLETED)
Attempt to access the 1 requested objects on 1 failed.
Detailed information:
com.sap.aii.ib.core.roa.RoaObjectAccessException:
Attempt to read object Adapter Metadata File | http://sap.com/xi/XI/System,
type AdapterMetaData from application REPOSITORY on
system REPOSITORY failed. Object does not exist. Detailed
informatio n: SWCV ID: e5a519a0766111dca2e8e95d0a115642
does not exist in Enterprise Service Repository and
System Landscape Directory (ROA_MOA_NOTCOMPLETED)
Please advise what possible solution can we apply?
Thanks.
Edited by: Rob Burbank on Dec 17, 2010 10:43 AM
Edited by: Rob Burbank on Jan 3, 2011 12:03 PM

Hi,
You can check File adapter metadata under Basis SWCV -->namespace http://sap.com/xi/XI/System in IR.
-Rahul

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

IDOC as a receiver adapter in XI to 3rd party scenario

Hi All,
I have an requirement to connect sap xi and 3rd party. the scenario as given below:
sap ecc 6.0 --> sap xi --> 3rd party
Here ecc is sending an idoc to the 3rd party. The 3rd party is SAP certified and intelligent enough to receive and send idocs. Here I'm using a idoc adapter as a receiver adapter. In the receiver adapter I have to give a rfc destination and a port name.
My question is how to create a rfc destination for the 3rd party. and which port name we'll use in this case. Is the port name will be the 3rd party port name is yes then how I can create a port in the 3rd party system.
Please help.
Regards,
Santosh

A communication channel with a receiver IDoc adapter can be created automatically for business systems that are defined in the System Landscape Directory. refer this link
[http://help.sap.com/saphelp_nw04/helpdata/en/42/d1a4d665c5574fa6e19784358ec948/frameset.htm]
You need to configure the receiver IDoc adapter to convert Integration Server contents from IDoc-XML to native IDoc format and to forward the IDocs to an SAP system .
you create a port and the rfc destination pointing to receiver in PI system
use tcode sm59 for creating rfc destination and IDX1 to create port and map it to rfc destination.

Enhanced receiver determination - Idoc 2 Idoc scenario

Hi,
I am trying Enhanced receiver determination - in an Idoc 2 Idoc scenario.
But when I selected Enhanced receiver determination in ID, it is asking for interface mapping.As it is an Idoc 2 Idoc scenario, I did not create any mapping objects in IR.
Is there any round about for this.
reg,

Hi,
if you are planning to send the Idoc to two systems then you do not need Enhanced Recieevr Determination.
You can add multiple Receivers In the receiver Determination under Configured Receivers and now the same idoc will be sent to 2 receivers.
Like mentioned by moorhty, Enahnced Receievr Determination allows you to dynamically determine receivers using a mapping program.! I dont think that is needed in your case
Regards
Bhavesh

Not sure if IDoc was created or received in file to idoc scenario

Hi,
I configured a file to idoc scenario in my test client for idoc MATMAS.MATMAS02 , now after going thru all the phases of design and configuration and creating partner profile using we20 , when I m executing the scenario , I am not sure wht happened to the idoc becz i can't see in the R/3 system using we05/02 or BD87 in the XI system .
Pl help how to rectify the error and find out where the error has actually occured.
ans will be rewrded
rgds
mojib

Hi Mojib,
first check in SXMB_MONI whether you have a success chequered flag for the file messge.................if there is error here, then rectify your this error and re-run your scenario................if you cannnot see your file msg in SXMB_MONI, then go to RWB and in comm channel monitoring, see the error in sender file comm channel status and rectify the error in sender file comm channel in ID and save and activate it and then re-run your scenario............
then execute SM58 to see in there is anything in tRFC.........if there is not anything here, then it means your IDOC has reached R/3.................
then in R/3, execute WE05 for the relevant period, then you will see your IDOC there with some status..........
Regards,
Rajeev Gupta

File to IDoc scenario - IDoc received with Errors

Hi,
I tried to send send IDoc from a file to SAP R\3. The communication channels are working fine, and I get the IDocs in R\3 but with status 56. When I examine the received IDoc structure in transaction "WE19", I see that the receiver port(SAP + SID of sap server) is blank with no values. I tested the IDoc adding the receiver port, and the IDoc got successfully posted...
I wonder why the receiver port that I specified in payload file content, does not reflect during runtime. I'm using the downloaded MATMAS IDoc structure with sender and receiver details as the input from file....
Please help me out!
Thanks!!
-Ajitha

Rodrigo/Sarvesh/Ravi/Haseeb,
Thanks for the inputs!! I have checked in IDX1 and the port name is the same. Also "Apply control records values from payload" checkbox is selected. I guess there was some problem with cache. It started working fine, when I started a new session
Thanks for your time and inputs!!!

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

PI 7.3 receiver AAE idoc scenario-No receiver comm channel found in ICO

Similar Messages

Maybe you are looking for