Problem in Idoc scenario

Hi
Can anyone tell me how to determine the status of an iDoc in recieving system.
Please be specific

Hi,
enter WE05 transaction code in R/3 and hear u will c the status of IDOC wether it is posted succesfully.
1. Start with checking the status in sm58 of sender R/3
Follow the steps
No message in found in XI in IDOC to FILE scenario
2. Try deleating the IDoc from IDX2 and refiring the same.
3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).
In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system
4. Monitor the SM58 in R/3 for IDOC status.
5. Trouble shooting file to IDOC and IDOC to file
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario
Refer below links for indepth troubleshooting
File to IDOC, trouble shooting
Refer below steps
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOC to File steps to be followed please verify your scenario with it
R3 system.
1. Create SM 59 RFC destination to XI,.
2. We21 - Create port to XI.
3. We 20 -- Maintain Partner Profile for the outbound Idoc.
XI SLD
1. Create technical system for R3 system
2. Create Business System for the Client of the R3 system.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
These are the required steps for IDoc to File scenario...
In R3 (i.e., your IDES system)...
RFC dest to XI (sm59) - any name
Logical system (bd54) - any name
Port to XI (we21) - any name
Partner profile for the logical system (we20) - use Logical system name created in bd54
In XI...
RFC dest to R3 (sm59) -
Port to R3 (idx1) -
create metadata for the idoc (idx2)
In sld...
create business system for R3 with Logical system name as r3 sys.
In we19
and give in control record as
Sender : Port ; Partner
Receiver : Port = <Port created in WE21> ; Partner = <Partner created in we20>
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario

Similar Messages

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

Authorization problem for idoc scenario

HI,
Can some one tell me what are the authorizations required to post a custom idoc to R/3 from XI ? I have done a scenario like file->IDOC(custom).When i execute the scenario it is successful in MONI. When i execute the transaction IDX5 in XI, i am seeing the status as No authorization to send IDocs with message type ZMASEMPDETAILSMT....Any help on this will be appreciated.
Regards,
Sudheer.

Hi,
Please check SAP/ERP
WE20 navigate to logical system and check the INPUTPARAMETER (ZMASEMPDETAILSMT must be a value there)
ON XI check WE21 (define a port to your ERP)
On XI create CC IDOC receiver and point to this port
Helpful Link:
https://websmp202.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700003604082004E
Daniel

Problem with Sender service in File to IDOC scenario

Hello All,
Am doing a file to IDOC scenario.
I have configured the sending system as a party and added a business component, to the BC attached the service interface and also configured the sender Communication channel(CC) as file.
On the receiving end configured the R/3 system from SLD as the business system and configured the receiver CCl. Can see the R/3 logical system in the Adapter specific identifiers at business system.
Pushing the file get an error "Unable to convert the sender service to an ALE Logical System". But choosing "Take sender from Payload" in the receiver CC is resolving the problem, however the sender partner number remains the same as what I have mapped to the control record in message mapping (which is like hard coding).
My questions are:
1. Am I doing the correct config in terms of the scenario. (like using "Take sender from Payload")
2. I tried using identifiers at the party level to convert the sending system, but nothing seems to work. But sending system remains the same as the constant from mapping.
Suggestions would be very much helpful..
--Prashanth
PS: Have gone through many blogs and posts on the forums, but may be I did not see the correct thread. Apologies if I am asking this again.

Hi Prashanth,
refer the below discussion i think it will solve your problem.
File To Idoc scenario
Thanks

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

Problem in executing File to IDoc Scenario in XI

Hello,
I am Working in HR Payroll module and new to XI.We are implementing File to IDoc Scenario in XI.When I place the flat file in the application server the file is read but the contents of the flat file is not getting posted to the IDoc.The constant values defined for IDoc in Mapping program is getting posted .I am not able to trace the error.
kindly help me out in resolving this problem.IF there is any way of debugging the entire process please let me know.
Thanks & Regards,
Malathi V.

hi,
check this blog to test your mapping,
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Next, check your INBOUND MESSAGE in SXMB_MONI and check if the content conversion has been perfromed as expected.
these steps will help you reason out the cause of your problem.
Regards,
Bhavesh

File to idoc scenario problem

I am trying to do FILE TO IDOC scenario, i am getting error called, UNABLE TO CONVERT SENDER SERVICE TO AN ALE LOGICAL SYSTEM.?
could anybody solve this problem?

Murali,
You get this error when Adapter specific attributes are missing..
Maintain Adapter Specific Attributes for business system in Integration directory.
Select your business system...Then select Service-->Adpater Specific identifiers.
from right hand window..
Set Logical System ID(of R/3 system), R/3System ID and client.
Let us know if you need more details.
Nilesh

Problems in file to idoc scenario

hi all
I am doing file to IDOC Scenario. In that I am getting the successful message but the Fields which I mapped to the IDOC is not populated in the IDOC.
In message mapping also it was showing the same thing. when I entered the fields of the file manually it was coming into the idoc and if i gave any file then it was not populated.
Can any one help us.
Regards
Vasu

Hello
For that u will have to change the occurunces in messages tab in mappings and do a split by value in mappings to generate 4 different messages.
secondly i hope ur using BPM for the same. in that case u can use parForEach to post 4 IDocs at a time.
regards
rajeev

Error while executing a JDBC to Idoc scenario : No standard agreement found

Hello SAP PI Gurus,
I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration.
<SAP:AdditionalText>No standard agreement found for ,
BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SAP:AdditionalText>.
While i test the configuration...i get an error in reciever agreement as mentioned above.
Can you pls help me in resolving this issue.
Regards,
Ravi

Hi,
I think the problem is with namespace....for IDOC the namespace will be "urn:sap-com:document:sap:idoc:messages"...but in your case it is different.....i.e http:....etc.....please check whether you 've used the same IDOC withe above mentioned namespace in all the configuration objects like interface determination, receiveragreement etc.....
Thanks
Priyanka

Issue in IDOC-XI-IDOC scenario

Hi,
We are facing a strange issue in an IDOC-XI-IDOC scenario. We are using a SAX parser to parse the code here.
The error we are getting in 'sxmb_moni' is
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS</SAP:P1>
<SAP:P2>java.lang.RuntimeException</SAP:P2>
<SAP:P3>For input string: ""</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS a java.lang.RuntimeException was thrown: For input string: ""</SAP:Stack>
The strange thing is, when I restart the message, it gets processed successfully. Also, when I copy the payload, and test the same on a different environment, it gets processed successfully.
Would really appreciate some pointers here!
cheers,
Prashanth

Hi,
This related to mapping error check it once again.Check in Interface mapping Test tab.see the result.check the sxmb_moni and get the source of mapping come back to interfcae mapping and test .
See the below links
Hi I got EXCEPTION_DURING_EXECUTE in RWB->Message Monitoring
I am getting MAPPING EXCEPTION_DURING_EXECUTE
EXCEPTION_DURING_EXECUTE- Error in Mapping. Doubt about IE and AE
EXCEPTION_DURING_EXECUTE
Mapping problem - EXCEPTION_DURING_EXECUTE
ERR: EXCEPTION_DURING_EXECUTE while using FILE CONTENT CONVERSION
Regards
Chilla..

Error in IDOC-XI-IDOC scenario

Hi folks,
Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPMs involved. SAX parsing used to parse the IDOCs.
We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as Problems found during the EXPORT to specified keyin table.
When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying Function module does not exist or EXCEPTION raised.
I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is EXPORT_TABLE_UPDATE_CONFLICT.
In the what happened? part of the dump, it says Error in ABAP application program. The current ABAP program CL_XMS_PERSIST=============CP had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.
Even SXMB_MONI is not opening (for yesterdays date). When I try to open it, it hangs for a long time, and finally opens an ABAP Runtime Errors page with the runtime error titled as SNAP_NO_NEW_ENTRY and the error short text as Runtime error: Unable to write short dump
Please advise.Thanks a ton!
cheers,
Prashanth

Hello Prashanth,
First of all this is an XI issue and belongs in that forum.
The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
Function module does not exist or EXCEPTION raised- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
Good Luck (don't forget to award points)
Ofer

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

IDoc to JDBC and JDBC to IDoc Scenario

Dear All,
I am working on IDoc to JDBC and JDBC to IDoc Scenario.
I have to send Idoc from SAP to Non SAP system(.NET application) i almost configured in XI but still i don't know when my INTEGRATION will INVOKE how my data will proceed from IDOC to Oracle database(Through JDBC) and in case of revese how and when Data flow will start.
Does anyone have completed STEP by STEP scenario document for this?
How my Idoc will sent to XI?
How XI will pick up data from IDoc?
How XI will Convert data to JDBC and UPDATE in Oracle Database?
And i reverse case(JDBC to IDoc) when my INTEGRATION will INVOKE?
Where and When i can watch my process and data?
How can i test the whole integration?
I AM GETTING ERROR WHILE TESTING CONFIGURATION IN Integration Directory "Error while refreshing the XI runtime cache" and when i check this in SXI_CACHE it gives me error
"Unable to refresh cache "NO_BUSINESS_SYSTEM"
"Error during last refresh to cache"LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"
Please solve all the above problems i will reward u points
thanks,
RP

Hi,
While we working on IDOC to JDBC interface..
We have to deploy JDBC Drivers?
Go through this links,
/people/varadharajan.krishnasamy/blog/2007/02/27/configuring-jdbc-connector-service-to-perform-database-lookups
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1246926,00.html
To install JDBC driver follow the how to guide.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.pdf
Configuration of JDBC Adapter for SQL Server
JDBC Driver = com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection = jdbc:microsoft:sqlserver://hostname:<port>;DatabaseName=<DBName>
UserID and Password.
If the connection is not working find the correct port number.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b92770-db81-2a10-8e91-f747188d8033
JDBC- X I - R/3 Scenario
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Please check the driver path as mentioned below.
JDBC Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection:jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=//location of DB table.mdb;
No JDBC driver required.
Receiver JDBC scenario MS access - /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
follow this thread
Re: Problem when connecting to MS Access through JDBC Adapter.
SAP Note 850116 has details
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Configuring the Sender JDBC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/content.htm
Configuring the Receiver JDBC Adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm
Idoc Reveiver adapter..
http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
Thanks,
Satya Kumar
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
Edited by: SATYA KUMAR AKKARABOYANA on May 8, 2008 5:51 PM

File to IDOC scenario-no messages in SXMB_MONI

Hi all,
 I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
I am doing a File to IDOC scenario through XI mapping.
I am not getting any messages in SXMB_MONI.
When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
Please help.
My scenario goes like this:
Sender : Business service(Some file location)
Used File adapter for sender communication channnel.
Receiver : Business system(SAP R/3)
Used IDOC Adapter for receiver communication channel.
One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
An inbound partner profile could not be found with the following key:
/LSDEMO/LS//DEBMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST test flag
I already manitained following data and there is one record in EDP21.
SNDPRN = LSDEMO
SNDPRT = LS
SNDPFC = LS
MESTYP = DEBMAS
MESCOD = space
MESFCT = space
TEST = space
EVCODE = DEBM
SYNCHK = X
METHOD = space
USRTYP = space
USRLNG = space
INMOD = space
DCART = space
And please let me know whether I have to maintain outbound parameters also for my partner in XI system.I didn't see any difference even I maintained it.
And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
Edited by: Jaya on Feb 26, 2010 10:17 AM
Edited by: Jaya on Feb 26, 2010 10:27 AM

Reg:file to idoc scenario

In a file-xi-idoc scenario i created a business service for legacy
system and a business system for R/3 receiver system
i didn't assign logical system for the sender business service
and assigned a logical system for the reciver business system
so while maintaining partner profile in the R/3 system
i have to give partner no:
partner type:
here the problem is my sender business service i didn't assign any logical system,and it is not of LS type
so then what do i need to give in the above two fields?
answers required briefly

Hello,
you know this pdf:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c09b775e-e56e-2910-1187-d8eba09c7a4a
Could be helpful.
Regards
Patrick

Problem in Idoc scenario

Similar Messages

Maybe you are looking for