on 02-06-2007 4:16 PM
Hello All,
please help me for my problem on adapter in my system XI for a scenario idoc -> file an I have an message error.
<b>xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BS_ADONIX</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service BS_ADONIX to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error></b>
Please help if you have some idea BS_ADONIx is a business service.
Thanks for your reply
Hi,
Please refer my blog
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Regards,
Venu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I put a logical system XI and now I have a new error message.
<b><?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Response
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error></b>
Have you some idea for this message and i have a communication channel type receiver (file)
Hello,
please reply me for my question if you have some idea.
Hello,
I<b> put a logical system XI and now I have a new error message.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Response
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error></b> Have you some idea for this message and i have a communication channel type receiver (file) ?
Hi,
Your scenario is Idoc to File or is it File to Idoc?
If it is Idoc to File, are you able to trigger the Idoc from your SAP system and see the same in XI?
If it is File to Idoc, look into your Sender Business System --> Adapter Specific Identifers and see if there a Logical System Name assigned to your Busss System. If no, assign a Logical System name and try your scenario.
Or, create a Header Mapping for your Sender Service like pointed by Michal.
Regards
Bhavesh
In interface determination please select our inbound message interface you have created for output type of file i.e. you have data typefor output type then used in message type and then same is used in Message interface. you need to select this message interface as our inbound message interface in interface determination.
thanks
Sreeram
Hi,
Did you create any Inbound Message Interface for your File?
You will have to create a Inbound Asynch message Interface for your file and use it as your target message interface in your Interface Mapping .
Also, if you are using a receiver service as a business service, then you will need to manually assign the message interface to the Buss Service. If you are using a Buss System then delete the search criteria when selecting the inbound message interface in yoru interface determination and then you should see the message interface
Regards
Bhavesh
Steps IDOC to File.
IN IR
1. Import the IDOC in XI (input).
2. Create a Data type of (output) i.e. file.
3. Create a Message type of (output) i.e. file used the above data type.i.e.Step 2
4. Create a Message interface of(output) .i.e file used the above messagetype. i.e.Step3.
5. create Mappping select source as IDOC and target as Message type you created.
6, In Interface mapping select source as IDOC and Target Interface Message Interface of file i.e.Step 4.
In ID.
Select the recevier determination of .
1.select sender system as R/3 system recivr as File Bunisees system
2. create interface determination select sender system as R/3 Sender interface as IDOC . in interface determination select inbound message whihc createdin step 4
and message interface we created in step 5.
3. create recevier determination sender r/3 interface IDOC and reciver File business system . so create reciver file adapter and assign to file business system
Please reward points
Thanks
Sreeram.G.Reddy
There is an error.
<b><?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Response
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error></b>
It is possible that provide for the properties of my communication channel type file
for exemple directory user password an others parameters ?
Thanks
Hi,
Have you created the BS_TEST of type third party in SLD?
I think the File adapter(receiver) configuration must have some errors...
Follow this link for the receiver fiel adapter configuration:http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
Regards,
JE
Message was edited by:
Joslyn
Message was edited by:
Joslyn
<b><?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Response
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error></b>There is an error.From scenario idoc -> file what is a utility from receiver aggrement.I would like to create rece agree a system send a message there is exist and effectivly I see a (receiver agree) communication channel in my receiverdetermination ?
Thanks
Yes I put that in my interface determination i verify the differents points and I see
in my communication channeel receiver file ftp I put my structure DT_BBPIV in the fields 'Content conversion parameters'.It's correct ? because I see a difference with this forum /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Thanks
Hi Sreeram,
my scenario is idoc to file and my structure DT_BBPIV_ADONIX contains 10 fields
vendor occur0.1
value occur 0.1
amount_i occur 0.999
cost_ctr occur 0.999
and I put in my record structure in the differents parameters for example
DT_BBPIV_ADONIX .addHeaderLine value 0
DT_BBPIV_ADONIX .fieldSeparator value ,
It's correct and please explain me this part because it's not clear for me ?
i would like the diffrents names and values to put for a content conversion parameters.
Thanks
Before I try with this solution and that file is empty.
please give me the differents informations putting for name and value after recordset structure for exemple <b>Figure 7 Content conversion on receiver side in this topic</b>/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Thanks for your reply
Hi,
The Recorset structure DT_HEADER,DT_TRANSET etc has a Sub-elements
HEADER,TRANS etc....under which he has fields RECORD_IDENTIFIER,FILE_TYPE etc....
For better understanding of file content conversion follow these two blogs:
<a href="/people/michal.krawczyk2/blog/2004/12/15/how-to-send-a-flat-file-with-fixed-lengths-to-xi-30-using-a-central-file-adapter File adapter for a file with Fixed lengths</a>
<a href="/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30 File adapter content conversion</a>
Hi,
inside your receiver agreement you can use header mapping
and specify another sender (which has a logical system)
as described in:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
Regards,
michal
-
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.