File Service to IDOC Scenario

HI ,
I am trying file service to IDOC scenario and iam getting following error "Unable to convert sender service FilesService_FILE2IDOC to an ALE logical system".
Here file has to be read and IDOC has to be posted in SAP system. Sender is not an SAP system / 3rd Party system ...itz an FILE sender service.
Settings i have done:
In Message Mapping in target IDOC structure i have disabled Control record
In integration directory IDOC Receiver Communication channel i have not selected "Apply Control Record values from Payload".
In receiver determination in header mapping i have put sender sevice "FilesService_FILE2IDOC ".
But still i receive the same error.
I do not want to send control record parameters in Message Mapping .
Pls throw some light on this ....
Regards
Sri

Hi Sridhar,
Regarding your error, below is the answer...
When you create the business system (in the SLD) you assign a "logical system name" or "ALE name". That is used as the ALE name for transporting IDOCs, and the sender system.
You have to also maintain this name in the R/3 System (tx. SALE, WE20), because IDOC will be noted as arriving from that system.
You also told that you dont want to pass the control records value....Do this, just deactivate the control records segments in your message mapping... let me not explain it further.... just check these blogs below for the same,
/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
And also go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
I hope this helps you solve your problem.
Regards,
Abhy

Similar Messages

File to Multiple Idocs scenario. Pls help

Hi All,
For Single File to Multiple Idocs scenario i am referring blog --
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
Suppose my source file is
AAA, BBB,CCC
111,222,333
ZZZ,ZZZ,ZZZ
I want to make 2 IDOCS for the first 2 records (AAA, BBB,CCC   and 111,222,333)
and do not want to make IDOC for the 3rd record -- how to achive this.
Regards

Hi,
If the condition is like, for 'AAA' and '111', IDocs to be generated, then do as follows.
If IDOCs are of same type.
1. Value
> Equals -
> createIf -
> IDOC
   Constant('AAA')
2. Value
> Equals -
> createIf -
> IDOC
   Constant('111')
3. Value
> Equals -
> not -
> createIf -
> IDOC
   Constant('ZZZ')
If 2 IDocs are of differnet types,
create different mapping programs with same logic.
If 2 IDocs are to be generated based on the record no in the file rather than the first field value, i think you can go for Global container.
Refer these,
[http://help.sap.com/saphelp_nw04/helpdata/en/ee/bf9640dc522f28e10000000a1550b0/frameset.htm]
[http://help.sap.com/saphelp_nw04/helpdata/EN/49/1ebc6111ea2f45a9946c702b685299/content.htm ]
[http://help.sap.com/saphelp_erp2004/helpdata/en/75/8e0f8f3b0c2e4ea5f8d8f9faa9461a/frameset.htm]
thanks.
Edited by: P.Ravi Varma on Apr 22, 2009 10:27 AM

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.

File-XI-multiple IDoc Scenario

Hi there -
I am working on single File-XI-multiple IDoc Scenario and have following questions:
(please keep in mind that there is already an existing multiple IDocs-XI-single File scenario between the same systems)
1. Please provide any detailed step by step documentation from end-to-end.
2. I am thinking it's compulsory to use BPM, is there any way to aviod?
3. Is it possible to update existing IDocs in R/3 directly from the data from XI?
Thanks everyone in advance...
Pat

HI,
Pls go thru following links-
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Single inbound file -> XI -> Multiple IDOCs in SAP
One file for multiple IDOCs
Hope this helps..
Regards,
Moorthy

Error Handling in File to Multiple IDOC Scenario?

Hello Experts,
My scenario is file with Multiple records and I want to send it to SAP system.If there will be 10 Records in my file I need to create 10 IDOC in Target system.
I can use below of the two options.
1) File to Multiple Idoc (1.N Mapping)
2) Using BPM
3)Directly place the file in SAP application server and process it via ABAP Program.
However I am not clear in which option error handling will be more effective.Please suggest.
Basically I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
Also I will be doing this scenrio for transaction data with huge size (1 Million Records).Which approach will be more effective in this case.
Thanks,
Pushkar

Hi Patel,
I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
when working on graphical mapping, the target structure is created when there are no errors in all records of source structure.
suppose if we have validation error in 9th and 10th record, then we can not process the first eight records and inturn we can not store the two error records in XI for further.
i suggest you the third option, you can directly place the file in SAP application server and process it via ABAP Program.
this is far better because you can do more customizations as you have to deal with millions of records.
Regards,
Pradeep A.

File- XI- Multiple IDOCs scenario

Hi,
I am working on File->XI->IDOC scenario. I have a single source file and I need to map it to two IDOCs and post them to ECC. The order of posting is not an issue since it is taken care of by ECC.
I need help (detailed) on achieving this in the best possible way (using/without using BPM).
Thanks,
Guru
PS: I went through the following blog:
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
But as per this blog, multi mapping is not possible with IDOC as the IDoc adapter is outside the Adapter Engine.

As Jaishankar suggested,
going for separate mapping is a better n simple options.
Source Message Interface Mapping 1> IDOC1
Source Message Interface Mapping 2> IDOC2
Since you are sending the IDocs to the same system,
One rcvr in rcvr determination, without any condition.
in interface determinations, you have 2 inbound interfaces, and corresponding Interface mappings.
Its a simple n straighforward approach.
Regards
Pushkar Anand

File to Multiple Idoc scenario using FCC

Hi All,
I am working in a file to idoc scenario. Here input is a fixed length file having Header and Item details which will repeat for many times.The number idoc in the target is based on the number of header in the input field. I have created a source structure with header as 1..unbounded and i have map the header with the target idoc.
In configuration part
Recordset Structure Header,9999,Item,9999
I am facing an error in communication channel as
"Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR consistency check in recordset structure validation in last recordset"
Please help me to resolve this issue. Thanks in advance.

Hi,
Source structure is
DATA         1...1
Record      0...unbounded
      Header 0...unbounded
      Item       0...unbounded
Here i am mapping Header to the target Idoc
In configuration
RecordSet Name: Record
RecordSet Structure:Header,9999,Item,9999
RecordSet Sequence:Varaible
Key Filed name : RecordType
Header.fieldFixedLength -
Header.fieldNames          -
Item.fieldFixedLength      -
Item.fieldNames               -
Header.keyFieldValue   : H
Item.KeyFieldValue         :I
Header.lastFieldOptional   YES
Item.lastFieldOptional         YES

Guarantee EOIO Processing in File-RFC-RFC-IDoc Scenario

Looking for some opinions on the following set up we've got. We're trying to build QoS EOIO on a scenario that goes File Sender->RFC and then RFC->IDoc. My question is basically have we effectively ensured that our scenario will be EOIO from file to IDoc. We want the first record in the file to always be the first created IDoc, the 10th record in the file to always be the 10th IDoc created etc..... We also want to make sure that if we encounter an error at any point that all subsequent processing stops and waits until the problem is resolved. We've successfully completed some steps but my biggest concern is in the area between where XI sends the data to SAP1 via RFC and the resulting return RFC from SAP1. I'm thinking we may not be quite there yet and would be interested to hear what others thought.
We're on SP15. The scenario goes like this (no BPM):
1) We have a legacy system LEG1 that we pick files up from using the Sender File adapter. This step will take the file from LEG1 into XI and map it to an SAP remote function on SAP system SAP1. We set QoS on the file adapter to EOIO. Our interface determination for the File to RFC component is set to QoS of "Maintain Order at Runtime".
2) XI makes the RFC call to SAP1 (6.20) using an RFC receiver adapter. The called function then processes the data and returns the data back to XI using another remote function call. This function call is of type tRFC where we call the function "in background task" and issue a commit after the RFC call.
3) We receive the data into XI from SAP1 using the RFC sender adapter. XI maps it to our IDoc layout and sends it onto another SAP system called SAP2. Again here our interface determination QoS is set to "Maintain Order at Runtime".
4) XI passes the IDoc onto SAP2 (7.00) using a receiver IDoc adapter. The paramter Queue Processing is turned on.

About EOIO in qRFCs, actually this is quite a polemic topic.
There is something you could do, allright, but it is controversial whether you could properly call it "EOIO" or not.
Refer to this thread for further discussion: use EOIO on Sender RFC and outbound ABAP proxy calls
Supposing you call the other RFC before you commit work in the receiver RFC, and supposing you could have EOIO at 2nd RFC (sender RFC), all these assumptions could mean that you would guarantee EOIO end-to-end. But they are just assumptions.
You have to try it and stress test the scenario to guarantee the validity of this design.
One other approach would be a BPM with all steps in one single transaction (check BPM transaction handling). The steps would be:
File -> sync RFC -> Idoc
where the response of RFC should be the necessary information for triggering the IDoc, and all send steps would be in EOIO mode (set queue name in Send steps). Also, file sender adapter QoS should be set to EOIO.
But I'm also not sure that this will guarantee EOIO end-to-end (possibly not...)
Good luck.
Regards,
Henrique.

File to multiple idoc scenarios depending on finput field value

Hi,
i have a file to idoc scenario.
depending on a particular field of the file i have to trigger a single idoc (with all the records in the file)or multiple idocs (for each record in the file ).
for example,
the file has 5 records-
2 records have field value A (create 1 idoc for all As)
3 records have field value B (create 1 idoc for each B)
so in this case 4 idocs (1 for all A, and 3x1 for B) are created
What is the best solution ?-
1. to have several outbound idoc interfaces and check each interface mapping for field value (A or B) ?
this solution seems like overwork to me
2. handle this in mapping ?
in that case will UDF be better or ABAP mapping
3. any other way ?
Thanks in advance

Hi,
if you have one IDOC type you can use ABAP mapping
this way you will handle everything in tables
and you will be able to post one IDOC (bundled)
with all IDOCs inside
also if you use ABAP mapping you will be able to incorporate changes
easily in the future I believe
for idoc bundling:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

File to multiple IDOCs scenario with the same receiver system

Hi guys,
I have to design and implement the following scenario:
I will receive one file with many lines (Records) with data for materials, quantities, operations etc..
Based on the values of some fields of each line, I will have to create an IDOC for each material.
For example:
if operation type = "INSERT", and Labor = 001 then create 3 Idocs of type MBGMCR with movement types=101, 261,311 that have to be posted one after the other to the same receiver system.
else if operation type = "INSERT", and Labor <> 001 then create an Idoc MBGMCR with movement type=311 and plant = 1001.
else if operation type = "Delete", and Labor = 001 the created 3 Idocs MBGMCR with movement type=312, 262 1002 and post them serially to the same receiver system.
else if operation type = "Delete", and Labor <> 001 the created 1 Idoc MBGMCR with movement type=312.
All IDOCS are posted to the same SAP R/3 system. We do not care about the sequence, except for the cases where 3 IDOCS are created.
I am trying to think of a good design in performance terms.
It is obvious that I will need BPM for sure.
I am thinking of creating a mapping program that will produce 4 message types for the different cases from the initial file and then create a different message mapping for each case from the message type to the IDOC.
I am asking you if I have to include everything (mappings) in BPM with a "fork" step?
Or shall I produce only the 4 message types and then post them to R/3 and execute the mappings in R/3?
Best Regards
Evaggelos

hi,
>>I am thinking of creating a mapping program that will produce 4 message types for the different cases from the initial file and then create a different message mapping for each case from the message type to the IDOC.
To me this seems to be the right solution.
here u will create different message mappings and write them sequentially in interface determination. the multi mapping will then be utilised in transformation step in BPM.
thus if this is the only requirement there is no need of using a fork step.
[reward if helpful]
regards,
latika.

Flat File to Delivery IDOC scenario

Dear All,
I am having one scenario in which I am having the flat file (.txt) of the Delivery Idoc and now I want to convert that flat file into a Delivery Idoc with the required data.
Kindly suggest me some good blogs which gives the step by step process for doing this scenario.
Warm Regards,
N.Jain

Hey Nishu,
You have to use File Content Conversion Paramters to acheive this.
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
You can Follow the following blogs
/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2
/people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
/people/jeyakumar.muthu2/blog/2005/11/29/file-content-conversion-for-unequal-number-of-columns
/people/shabarish.vijayakumar/blog/2006/02/27/content-conversion-the-key-field-problem
Or juz post your sender datatype structure some one might give u exact fcc params.
Hope itz Helpfull.
Cheers,
*Raj*
*REWARD POINTS IF FOUND USEFULL*

Web service to IDOC scenario

Hi,
I'm defining Web service (through the configuration builder) and the message interface that i'm using to publish is based on idoc.
when i'm trying to check the WSDL which was generated, in the wsnavigator i'm getting the following error:
"cannot download WSDL from http://<server.....filename.wsdl: cannot load java.class: typename = /wsdl:definition/wsdl:types/xsd:schema/xsd:elemen/xsd:complexType, elementName=TEST_BASIC_TYPE
please advise,
Pavel Sheynkman.

I think you have used the proposed url which was mentioned in defining the webservice in configuration. better to use this link:
http://hostname:port/XISOAPAdapter/MessageServlet?channel=:<service>:<sender channel name>.in that url. you have to mention the hostname of the server and the port number.

Mapping File to Multiple IDoc Scenario

I know how to do this, but when I load the IDoc's XML structure back into the IR, the EDI_DC40 field doesn't have anything in it's structure. I need to configure the sender parameters in this structure for this IDoc, so any help would be appreciated.

Schroeder,
If I understand your question correctly after you import the IDOC into IR you want the EDI_DC40 segment filled automatically.
Either you have to fill manually or if you automatically to be filled up then check this weblog:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
Regards,
---Satish

Problem in File to IDOC Scenario

Hi,
I am trying to test the demo example for Flight Booking using the "File Sender to IDoc" Scenario. I have done all the settings. As a last step after I copy the file in
[XI-hostname]\sapmnt\trans\tmp\fileadapter\group[XX] as per the Demo example guide and activate the changes for File_Sender communication channel, no action is triggered.
The file remains in the directory. When I want to see if my adapter is fine and I check the Adapter Lists in the Adapter Monitoring, it shows only JPR Adapter and that too in RED.
Then I check the tracefiles and find this error.
Date : 04/05/2006
Time : 16:44:52:264
Category : /Applications/ExchangeInfrastructure/Directory
Message ID : 00B0D03E9B4F005A0000000D000001F4000410AB0985C603
Severity : Error
Location : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler
Source Name : /Applications/ExchangeInfrastructure/Directory
Thread : SAPEngine_Application_Thread[impl:3]_3
Message : Failure at Cache-Refresh data consumption !!!
<?xml version="1.0" encoding="UTF-8"?>
<CacheRefreshError>
<EngineType>AE</EngineType>
<EngineName>af.aba.singdemo1</EngineName>
<RefreshMode>C</RefreshMode>
<Channel>
 <PartyName></PartyName>
 <ServiceName>XI_LEGACY_BS_00</ServiceName>
 <ChannelName>File_Sender</ChannelName>
 <ChannelObjectId>838401f3335236bbadd7086c6711b070</ChannelObjectId>
 <ChannelError>
 <Message>
 Could not parse Channel 'File_Sender'(ObjectId: 838401f3335236bbadd7086c6711b070) AdapterType: File|http://sap.com/xi/XI/System|3b787a8035c111d6bbe0efe50a1145a5:
 </Message>
 <Trace>
 com.sap.aii.af.service.cpa.CPAException: Schema not available for File|3b787a8035c111d6bbe0efe50a1145a5|http://sap.com/xi/XI/System.
 at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endElement(DirectoryDataSAXHandler.java:262)
 at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:154)
 at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1826)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1722)
 at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2298)
 at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1719)
 at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2701)
 at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:126)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:136)
 at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:209)
 at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:270)
 at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:331)
 at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
 at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
 at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
 at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:54)
 at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:713)
 at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:595)
 at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:440)
 at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
 at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
 at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
 </Trace>
 </ChannelError>
</Channel>
</CacheRefreshError>
Datasource : 48696150:E:\usr\sap\ABA\DVEBMGS04\j2ee\cluster\server0\log\applications.log
Application : sap.com/com.sap.xi.directory
Argument Objs :
Arguments :
Dsr Component : singdemo1_ABA_48696150
Dsr Transaction : 72d10590c48011da8a7100b0d03e9b4f
Dsr User : Guest
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler
Resource Bundlename :
Session : 3816
Source : /Applications/ExchangeInfrastructure/Directory
ThreadObject : SAPEngine_Application_Thread[impl:3]_3
Transaction : SAP J2EE Engine JTA Transaction : [2ffffffe7b5600a31]
User : XIAFUSER
Any help will be great.
Regards,
Shubham

Hi Manish,
I updated the same and now when I activate the changes in my File_Sender communication channel its still not working.
I checked the Message Monitoring and the message fails to get delivered.
Here is the Message Audit Log.
2006-04-11 13:21:51 Success Channel File_Sender: Send binary file "
singdemo1\sapmnt\trans\tmp\fileadapter\group00\Booking00.xml". Size 526 with QoS EO
2006-04-11 13:21:54 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-04-11 13:21:55 Success Trying to put the message into the send queue.
2006-04-11 13:21:56 Success Message successfully put into the queue.
2006-04-11 13:21:56 Success The application sent the message asynchronously using connection AFW. Returning to application.
2006-04-11 13:21:56 Success Confirmation mode test found. File will be resent next time
2006-04-11 13:21:56 Success The message was successfully retrieved from the send queue.
2006-04-11 13:21:57 Success The message status set to DLNG.
2006-04-11 13:23:01 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
2006-04-11 13:23:03 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:28:01 GMT+08:00 2006.
2006-04-11 13:23:06 Success The message status set to WAIT.
2006-04-11 13:28:02 Success Retrying to send message. Retry: 1
2006-04-11 13:28:02 Success The message was successfully retrieved from the send queue.
2006-04-11 13:28:02 Success The message status set to DLNG.
2006-04-11 13:29:04 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
2006-04-11 13:29:04 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:34:04 GMT+08:00 2006.
2006-04-11 13:29:04 Success The message status set to WAIT.
2006-04-11 13:34:12 Success Retrying to send message. Retry: 2
2006-04-11 13:34:12 Success The message was successfully retrieved from the send queue.
2006-04-11 13:34:12 Success The message status set to DLNG.
2006-04-11 13:35:15 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
2006-04-11 13:35:15 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:40:15 GMT+08:00 2006.
2006-04-11 13:35:15 Success The message status set to WAIT.
2006-04-11 13:40:15 Success Retrying to send message. Retry: 3
2006-04-11 13:40:15 Success The message was successfully retrieved from the send queue.
2006-04-11 13:40:15 Success The message status set to DLNG.
2006-04-11 13:41:17 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.
2006-04-11 13:41:17 Error The message status set to NDLV.
What can be the problems?
Regards,
Shubham

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

File Service to IDOC Scenario

Similar Messages

Maybe you are looking for