Problem in file to database scenario
Hi friends,
I have done file to database(oracle) scenario. I have tried to push the data to database.but it is not reached to database.
I have tested my scenario in Integration Directory.I didn't get any error msg under test configuration.
Pls verify the main and sub table levels in oracle database.
ORDERSDEMO -
> ORDERSTEST -
> ORDERSTABLE
Data base connection In ID:
JDBC Driver -
com.oracle.jdbc.Driver
Connection -
jdbc:oracle://aljs047:1521\ORDERSTABLE
Kindly guide me if I have done mistake in the connection.
Your valuable cooperation is greatly appreciated.
Points will be awarded.
Thanks in advance.
Best Regards,
Naresh.
You have given the Connection like this right?
Connection: jdbc:oracle://aljs047:1521\ORDERSTABLE
But the right one is
Connection: jdbc:oracle://aljs047:1521/ORDERSTABLE
(Just check that forword slash & Backword Slash)
Where:-
aljs047: is the host name
1521: is your port
ORDERSTABLE : is your Database Table Name
Similar Messages
-
Simple File to Database Scenario
Dear Experts
I am working on a File to Database scenario. My requirement is to update the database with latest information. For example
1. First day i got a file of 100 records...Insert all the 100 records.
2. Second day i will get 110 records (here 100 records is old data and 10 records is the delta). Now PI needs to lookup with DB and insert the updates of 100 records and insert the delta 10 records...
3. Third day i got 125 records file (here 110 is previous days data and 15 is todays delta). I need to update the changes of all the 110 and insert 15 delta records
ThanksHi,
Since you want to update the existing records and insert the delta, the 'update_insert' option of JDBC receiver should fulfill your requirements.
Refer the following links for more help on this
Re: jdbc update_insert
Jdbc Reaciver UPDATE_INSERT
Regards -
Facing Problems in File to JDBC scenario
Hi Folks,
I am trying to configure a file to jdbc scenario where I'm getting the below error.
Error during database connection to the database URL 'jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=D:\usr\sap\PRD\SYS\global\Receive\Student.mdb' using the JDBC driver 'sun.jdbc.odbc.JdbcOdbcDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:odbc:Driver={Microsoft Access Driver (.mdb)};DBQ=D:\usr\sap\PRD\SYS\global\Receive\Student.mdb'*: SQLException: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified'
I Have done the below configuration for the receiver JDBC adapter
Driver : sun.jdbc.odbc.JdbcOdbcDriver
Connection : jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=D:\usr\sap\PRD\SYS\global\Receive\Student.mdb
tried to provide the user id & password as well as the password and also tried with with keep them blank. My Ms access 2007 database table is in the application server itself.
I've also checked with the below blogs & forums:
MS ACCESS 2007 to PI 7.01
/people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
http://www.riyaz.net/blog/jdbc-adapter-configuration/technology/1200/
Thanks Experts.Hi Santosh,
If also could be possible that, you have not added proper JDBC dirver and hence i think you are getting following error:
Data source name not found and no default driver specified'
So first add the JDBC driver( .jar) to the SAP PI JDBC library and redeploy the .sda file and then retest your scenario. Here is a link to PDF which explain how to add external drivers to use new DB drivers in the JDBC adapter.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f?quicklink=index&overridelayout=true
Regards,
RK -
File to database scenario in JCAPS513
Hi ,
I ma trying to do File to database scenarion in Jcaps513. here i am using Oracle 9i as database . I m using prepare statement for it .
I m trying to fetch data from databse and write into simple text file . But after deployment i am getting following error.
please suggest me solution for the same.
[#|2009-06-18T17:32:34.085+0530|SEVERE|IS5.1.3|prj_Database_File.cm_database_jcd_Database_File_1.jcd_Database_File_Runtime_Handler|_ThreadID=14; ThreadName=Worker: 4; Context=project=prj_Database_File,deployment=dp_databse,collab=cm_database_jcd_Database_File 1,external=File1;stacktrace-id=1;|com.stc.codegen.framework.runtime.ServiceInitializationException: Error in allocating a connection. Cause: Connection could not be allocated because: invalid arguments in call
com.stc.codegen.framework.runtime.ServiceInitializationException: Error in allocating a connection. Cause: Connection could not be allocated because: invalid arguments in call
at com.stc.oracle.runtime.ejb.OracleEWayRuntimeHandler.initializeService(OracleEWayRuntimeHandler.java:262)
at prj_Database_File.cm_database_jcd_Database_File_1.jcd_Database_File_Runtime_Handler.handleRequest(prj_Database_File.cm_database_jcd_Database_File_1.jcd_Database_File_Runtime_Handler:355)
at sun.reflect.GeneratedMethodAccessor185.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:140)
at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:135)
at $Proxy39.handleRequest(Unknown Source)
at com.stc.connector.codegen.fileadapter.AbstractFileAdapterMDB.sendMessage(AbstractFileAdapterMDB.java:153)
at com.stc.connector.codegen.fileadapter.AbstractFileAdapterMDB.onContents(AbstractFileAdapterMDB.java:104)
at sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:940)
at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)
at com.sun.ejb.containers.MessageBeanContainer.deliverMessage(MessageBeanContainer.java:948)
at com.sun.ejb.containers.MessageBeanListenerImpl.deliverMessage(MessageBeanListenerImpl.java:42)
at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:136)
at $Proxy43.onContents(Unknown Source)
at sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.stc.connector.framework.eway.EndpointProxy.invoke(EndpointProxy.java:175)
at $Proxy42.onContents(Unknown Source)
at sun.reflect.GeneratedMethodAccessor184.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.stc.connector.framework.eway.MessageResourceManager$MessageSender.run(MessageResourceManager.java:245)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:54)
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:382)The message: "Error in allocating a connection. Cause: Connection could not be allocated because: invalid arguments in call" could be a sign that you should double-check configurations in your Environment.
Regards -
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
VasuHello
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 -
Problem with FILE TO EMAIL Scenario
Hello ALL,
I am working on FILE--->XI--> Email scenario, done with designing and configuration part.I try to post a sample test file, File adapter is not picking up the file from the directory and throwing exception in Adpater Framework Window. I see following exception in Adapter monitoring window.. I am not able to figure it out where it went wrong..Any suggestions are gretly helpful.
Last message processing started 14:38:34 2005-08-08, Error: Module exception com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.DeliveryException: Failed to call the endpoint found
last retry interval started 14:38:34 2005-08-08
length 30,000 secs
Thanks ,
Prakash.Hi,
There is feature to test the Configuration settings in Integration Directory.
Tools--> Test Configuration.
Here you need to specifry the Sender and Receiver details.
In Payload, --> copy it from RWB or SXMB_MONI with sender payload,
execute the scenario( Downward arrow Icon).
It will give you all details and log if there is anything missing in the scenario.
Thanks
Swarup -
Problem in file to rfc scenario without using BPM concept
hi ,
I have configured the file to rfc scenatio and in that i have created a synchronous message interface .i have even aaded modules to my sender adapter .
I have one sender aggrement , 2 receiver aggrement , 1 interface determination , and 1 receiver determination .
the problem that i am facing is that i am able to perform the operations on r3 side succesfully but i am not getting the response back in xi .
can any one pls help me in getting out of this problem .
with regards
Bhawarlal ChoudharyHi Amit ,
My scenario is for creating the notification ( in plant maintenance) . every time i transmit a file a new notification nos is generated and even i am able to see it in SAP . in RWB when i check my communication channel i am not getting any response . The synchronous process seems to be working fine according to me do i need to even create a FRC communiation channel for sender as i have not done that .
with regards
Bhawarlal Choudhary -
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,
ShubhamHi 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 -
Output XML file problem (in FILE to RFC scenario)
hi,
my problem is that in the export parameter i have 3 variables but my output xml file shows only 2 parameters . I have checked my mapping all 3 parameters are mapped properly in output mapping .
Initially when i started the scenario there were only 2 parameters in my export list .
i completed this suuccesfully and then as per new requirement one more parameter was needed to be added i added a new parameter and reimported my rfc .
the response tab of the reimported RFC shows me the newly added parameter but my final xml file only shows me the previous 2 it doesnt show me the newly added one is there any seeting which i need to change like in idoc where we have to readd the idoc in IDX2
With regards
Bhawarlal ChoudharyHi,
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
The Client must be the client number of the backend SAP system.
Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
Double-click on the business system in the Integration Directory.
Switch to Edit mode.
Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
The RFC Destination is from step 3.1.
The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
If find helpful plz award points -
Problem with File to IDOC scenario
Hello,
I try to implement our first scenario to IDOC.
In TOC SXMB_MONI I have to errors
1. <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
2. <SAP:Stack>Unable to convert sender service aaa_Sender_Service to an ALE logical system</SAP:Stack>
Any idea how I can solve this problems?
EladHI,
I think u have not done the configuration at the R3 end....
Just go through the below step by step process of FILE to IDOC. and check whether u have done the same configuration for ur scenario....I dont know what all configuration u have done....
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
Thnx
Chirag -
Getting problem in File to IDOC scenario
Hi,
In SXMB_MONI, I am getting an error "Message has error status on outbound side". file is being picked by XI and it is not appearing in the R/3 system as IDOC. I am getting black & white chequered flag at left side and red flag at right side in the SXMB_MONI. Plz help me in this regard.
Thanks
Raghavesh.Hi Divija,
Thanks for ur reply.Mapping is done correctly. I have tested it and executed successfully.
The error message is "Message has error status on outbound side". I checked the Message ID about error, but i couldn't found any error in that.Plz check the following payload below.----
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Response
-->
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>087E57E0-25F3-11DB-AB31-001143D6B120</SAP:MessageId>
<SAP:TimeSent>2006-08-07T08:59:28Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>FILE_TO_IDOC_BS</SAP:Service>
<SAP:Interface namespace="http://filetoidoc/xi">ZEP_TO_IDES_MI</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SAPIDES</SAP:Service>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS03</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS03</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2006-08-07T08:59:28Z" wasRead="false">
<SAP:Engine type="AE">af.xi2.igatesap09</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>087E57E0-25F3-11DB-AB31-001143D6B120</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2006-08-07T08:59:28Z" wasRead="false">
<SAP:Engine type="IS">is.00.igatesap09</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>087E57E0-25F3-11DB-AB31-001143D6B120</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2006-08-07T08:59:29Z" wasRead="false">
<SAP:Engine type="IS">is.00.igatesap09</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">IDoc</SAP:Adapter>
<SAP:MessageId>087E57E0-25F3-11DB-AB31-001143D6B120</SAP:MessageId>
<SAP:Info>0000000000045522;</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000045522</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>DEBMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>DEBMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPXI2</SAP:SNDPOR>
<SAP:SNDPRN>FILETOIDOC</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPDES</SAP:RCVPOR>
<SAP:RCVPRN>IGATE_800</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2006-08-07</SAP:CREDAT>
<SAP:CRETIM>04:59:29</SAP:CRETIM>
<SAP:ARCKEY>087E57E025F311DBAB31001143D6B120</SAP:ARCKEY>
</SAP:IDocOutbound>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20060807</SAP:Date>
<SAP:Time>045928</SAP:Time>
<SAP:Host>iGateSAP09</SAP:Host>
<SAP:SystemId>XI2</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>003</SAP:ProcStatus>
<SAP:AdapterStatus>001</SAP:AdapterStatus>
<SAP:User>XIAFUSER</SAP:User>
<SAP:TraceLevel>3</SAP:TraceLevel>
<SAP:Logging>1</SAP:Logging>
<SAP:LogSeqNbr>008</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId />
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService />
<SAP:QIdInternal>XBTO3___0000</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="100">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">C0A84641121044D700F02DB4</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID">C0A84641121044D700F12DB5</SAP:EOReferenceOutbound>
<SAP:MessageSizePayload>752</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>3020</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>752</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>1124</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>XIRA</SAP:AdapterInbound>
<SAP:AdapterOutbound>IDOC</SAP:AdapterOutbound>
<SAP:RandomNumber>81</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.765</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085928.781</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.781</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085928.781</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.781</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085928.859</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.875</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085928.875</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.89</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085928.89</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.906</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085928.906</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085928.906</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085928.984</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085929.0</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085929.015</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085929.015</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085929.031</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="iGateSAP09">20060807085929.046</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="end" host="iGateSAP09">20060807085929.062</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SAP:OutboundBindingEntry version="30">
<SAP:OutboundBindingObjectId>7E9DD53BBCC334B78F5D7E5373481745</SAP:OutboundBindingObjectId>
<SAP:FromPartyName />
<SAP:FromServiceName>FILE_TO_IDOC_BS</SAP:FromServiceName>
<SAP:ToPartyName />
<SAP:ToServiceName>SAPIDES</SAP:ToServiceName>
<SAP:ToInterfaceName>DEBMAS.DEBMAS03</SAP:ToInterfaceName>
<SAP:ToInterfaceNamespace>urn:sap-com:document:sap:idoc:messages</SAP:ToInterfaceNamespace>
- <SAP:OutboundBindingAttributes>
<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:OutboundBindingAttributes>
- <SAP:HeaderMapping>
<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
</SAP:HeaderMapping>
- <SAP:ChannelEntry version="30">
<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">SAPIDES</SAP:ServiceName>
<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">ZEP_TO_IDES_RCC</SAP:ChannelName>
<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:AdapterName>
<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">IS</SAP:AdapterEngineType>
<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:MessageProtocol>
<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">IDoc</SAP:TransportProtocol>
<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
<SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30" />
<SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30" />
- <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:Attribute>
<SAP:Name>interfaceVersion</SAP:Name>
<SAP:Value>3</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>passControlSetValues</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>port</SAP:Name>
<SAP:Value>SAPDES</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>queueing</SAP:Name>
<SAP:Value>0</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>rfcDestination</SAP:Name>
<SAP:Value>IGATE_800</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>sapRelease</SAP:Name>
<SAP:Value>640</SAP:Value>
</SAP:Attribute>
- <SAP:Attribute>
<SAP:Name>segmentVersion</SAP:Name>
<SAP:Value />
</SAP:Attribute>
</SAP:AdapterTypeData>
</SAP:ChannelAttributes>
</SAP:ChannelEntry>
</SAP:OutboundBindingEntry>
</SAP:OutboundBinding>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = 192.168.70.65:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 192.168.70.65</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = XI2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = 087E57E025F311DBAB31001143D6B120</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 087E57E025F311DBAB31001143D6B120</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 087E57E025F311DBAB31001143D6B120</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XI2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - SAPIDES</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) SAPIDES DEBMAS.DEBMAS03</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: DEBMAS.DEBMAS03</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO3___0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XI2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-08-07T08:59:28Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="1" type="T">Interface Mapping http://filetoidoc/xi ZEP_TO_IDES_IM</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 15340465420C3DA1A9475DA6856A09C7</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping D9FF93C122D711DBA80DE4DEC0A84641</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_ZEP_TO_IDES_MM_</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_ZEP_TO_IDES_MM_.</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._ZEP_TO_IDES_MM_</Trace>
<Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
<Trace level="3" type="T">Document start</Trace>
<Trace level="3" type="T">Start tag [DEBMAS03]</Trace>
<Trace level="3" type="T">Start tag [IDOC]</Trace>
<Trace level="3" type="T">Add attribute: [BEGIN]=[1]</Trace>
<Trace level="3" type="T">Start tag [EDI_DC40]</Trace>
<Trace level="3" type="T">Add attribute: [SEGMENT]=[99]</Trace>
<Trace level="3" type="T">Start tag [TABNAM]</Trace>
<Trace level="3" type="T">Put value [EDI_DC40]</Trace>
<Trace level="3" type="T">Close tag [TABNAM]</Trace>
<Trace level="3" type="T">Start tag [DOCREL]</Trace>
<Trace level="3" type="T">Put value [640]</Trace>
<Trace level="3" type="T">Close tag [DOCREL]</Trace>
<Trace level="3" type="T">Start tag [DIRECT]</Trace>
<Trace level="3" type="T">Put value [2]</Trace>
<Trace level="3" type="T">Close tag [DIRECT]</Trace>
<Trace level="3" type="T">Start tag [IDOCTYP]</Trace>
<Trace level="3" type="T">Put value [DEBMAS03]</Trace>
<Trace level="3" type="T">Close tag [IDOCTYP]</Trace>
<Trace level="3" type="T">Start tag [MESTYP]</Trace>
<Trace level="3" type="T">Put value [DEBMAS]</Trace>
<Trace level="3" type="T">Close tag [MESTYP]</Trace>
<Trace level="3" type="T">Start tag [SNDPOR]</Trace>
<Trace level="3" type="T">Put value [SAPXI2]</Trace>
<Trace level="3" type="T">Close tag [SNDPOR]</Trace>
<Trace level="3" type="T">Start tag [SNDPRT]</Trace>
<Trace level="3" type="T">Put value [LS]</Trace>
<Trace level="3" type="T">Close tag [SNDPRT]</Trace>
<Trace level="3" type="T">Start tag [SNDPRN]</Trace>
<Trace level="3" type="T">Put value [XI2CLNT100]</Trace>
<Trace level="3" type="T">Close tag [SNDPRN]</Trace>
<Trace level="3" type="T">Start tag [RCVPOR]</Trace>
<Trace level="3" type="T">Put value [SAPDES]</Trace>
<Trace level="3" type="T">Close tag [RCVPOR]</Trace>
<Trace level="3" type="T">Start tag [RCVPRT]</Trace>
<Trace level="3" type="T">Put value [LS]</Trace>
<Trace level="3" type="T">Close tag [RCVPRT]</Trace>
<Trace level="3" type="T">Start tag [RCVPRN]</Trace>
<Trace level="3" type="T">Put value [IGATE_800]</Trace>
<Trace level="3" type="T">Close tag [RCVPRN]</Trace>
<Trace level="3" type="T">Close tag [EDI_DC40]</Trace>
<Trace level="3" type="T">Start tag [E1KNA1M]</Trace>
<Trace level="3" type="T">Add attribute: [SEGMENT]=[1]</Trace>
<Trace level="3" type="T">Start tag [MSGFN]</Trace>
<Trace level="3" type="T">Put value [005]</Trace>
<Trace level="3" type="T">Close tag [MSGFN]</Trace>
<Trace level="3" type="T">Start tag [KUNNR]</Trace>
<Trace level="3" type="T">Put value [000000I236]</Trace>
<Trace level="3" type="T">Close tag [KUNNR]</Trace>
<Trace level="3" type="T">Start tag [KTOKD]</Trace>
<Trace level="3" type="T">Put value [0001]</Trace>
<Trace level="1" type="T">*** APPLICATION TRACE TRUNCATED (for more details see LogViewer)***</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_ZEP_TO_IDES_MM_ completed. (executeStep() of com.sap.xi.tf._ZEP_TO_IDES_MM_</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="1" type="T">processing the outbound binding</Trace>
<Trace level="1" type="T">search outbound bindings</Trace>
<Trace level="2" type="T">search outbound binding for:</Trace>
<Trace level="2" type="T">... sender party =</Trace>
<Trace level="2" type="T">... sender service = FILE_TO_IDOC_BS</Trace>
<Trace level="2" type="T">... receiver party =</Trace>
<Trace level="2" type="T">... receiver service = SAPIDES</Trace>
<Trace level="2" type="T">... receiver interface namespace = urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="2" type="T">... receiver interface name = DEBMAS.DEBMAS03</Trace>
<Trace level="2" type="T">outbound binding found</Trace>
<Trace level="2" type="T">outbound channel is:</Trace>
<Trace level="2" type="T">... party =</Trace>
<Trace level="2" type="T">... service = SAPIDES</Trace>
<Trace level="2" type="T">... name = ZEP_TO_IDES_RCC</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
<Trace level="1" type="T">outbound bindings found</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2006-08-07T08:59:29Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Channel for IDOC adapter: IDoc</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = IDOC</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_IDX_IDOC_SERVICE</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Outbound IDoc-Adapter -
</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
<Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
<Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="2" type="T">IDoc-Endpoint Channel :</Trace>
<Trace level="2" type="T">RFCDEST : IGATE_800</Trace>
<Trace level="2" type="T">Port : SAPDES</Trace>
<Trace level="2" type="T">Docrel :</Trace>
<Trace level="2" type="T">Version : 3</Trace>
<Trace level="2" type="T">Saprel : 640</Trace>
<Trace level="2" type="T">Queue-ID:</Trace>
<Trace level="2" type="T">----
</Trace>
<Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>
- <Trace level="1" type="B" name="IDX_XML_TO_IDOC">
<Trace level="1" type="T">Parse XML-BODY</Trace>
<Trace level="1" type="T">Get the Metadata for port SAPDES</Trace>
<Trace level="2" type="T">----
</Trace&g -
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 -
Regarding RFC connection in File to IDOC Scenario
Hi everyone,
I was configuring file to Idoc Scenario, i have made all the required configurations in SLD, IR and ID, in XI system and in R/3 System. i have created RFC connection from XI to R/3 system, and its working fine. i have created an Partner profile in WE20 with sender file system name with inbound parameters. <i>But still i am getting error as EDI Partner Profile not defined in WE05- iDOC ADDED WITH ERRORS. </i><b>Do we need to create an RFC connection from R/3 system to XI for file to Idoc Scenario</b>
<b>!!! Note: RFC connection from R/3 system to XI is not working, will this be a problem for file to idoc scenario. !!!</b>
Regards,
Varun Reddy.KHi Varun
Follow these steps
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
Regards,
Santosh -
File content to database scenario
Hi All,
I am doing file content conversion to database scenario.
In this scenario i got the following problem.
Error during database connection to the database URL 'jdbc:mysql://ibxi:3306/javatest' using the JDBC driver 'org.gjt.mm.mysql.Driver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:mysql://ibxi:3306/javatest': SAPClassNotFoundException: org.gjt.mm.mysql.Driver'
In this i am connecting to mysql database.at that time in receiver side i got the problem.
please do the need ful.
Thanks & Regards,
Kakshayini.Sorry for the above post..
First check whether the required drivers has installed on your J2EE Engine or not. If it is not installed, please follow the bellow steps,
1.Get the existing <b>aii_af_jmsproviderlib.sda</b> file from your SAP XI installation (if you already have JDBC or JMS drivers deployed).
2. Unzip the file, add the required .jar files (each database has it's own .jar file that has
to be deployed on your J2EE Engine ).
For example if it is SQL server db -mssqlserver.jar
3. Again zip the flies including all .jars with the name "aii_af_jmsproviderlib" and it has
to be deployed in to the J2EE Engine.
4. Start the SDM (Software Deployment Manager) and select the
aii_af_jmsproviderlib.zip file and start the deployment.
I hope once you have done this thing, the problem will be solved.
Regards,
Velan
<b></b><b></b> -
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
Maybe you are looking for
-
Calendar app crashes when going to march 2013
Does anyone else experience the same problem? I can recreate it on at least two iPads (the original iPad1 [iOS 5.1.1] and the latest Retina iPad [iOS 6.0.1]) While browsing the calendar in month view and going from febraury 2013 or april 2013 to marc
-
Entire image turns black when using the type tool in Photoshop CC
When I create a text layer, the whole image turns black. If I enter the text blindly, I will see the expected results when I finish and click on another tool. If I try to edit the text layer, everything turns black again. I am not using the type m
-
I've created a horizontal menubar with the Spry features. In FireFox, the submenu bars drop into the correct place and function properly. Pull up the page in IE 7 and the submenus appear off to the right of where I want them to be. Here's a link to t
-
Data service returning an empty object
Hi I am trying to call a data service from the flex to load my data grid. In the debug, i saw that the arrraycollection in the fill method is being returned empty. here are the details.... My .java file has the same names with the set and get functio
-
Tracking information for individual item quantities...any suggestions?
Hello Experts! At my current client, they use tag numbers for some of the materials they order, specifically for capital-related procurement. For example, an order of 10 quantity, each material will have a tag number for a total of 10 unique tag numb