IDoc scenario monitoring,,,

Hi,
I have some scnerio's in whic data flows from SAP (using idoc's) - XI - POS system (File system) and vice versa.
Indeed there are some heavy data transfer involved.
NOw I have some queries and would appreciate if anyone can help me in solving them:
1. Is there any way like creating a custom/ standard report to monitor the idoc's sent sucessfully/ unsuccessfully end to end from R/3 and XI perspective.
I understand that this can be done using certain tools in XI but this report is helpful for end user, who actually triggers the scenario from SAP and POS system.
2. At times, it happens that 1-2 messages out of 5-6 messages in SXMB_MONI have green flag ( Scheduled for outbound processing) and then I have to manually go in SMQ1/SMQ2 and execute the LUW. Is there any way to avoid such occurences.
I would really apreciate if in addition to links/blogs, anyone can provide some explaination to these issue.
Thanks....

Hi,
2. At times, it happens that 1-2 messages out of 5-6 messages in SXMB_MONI have green flag ( Scheduled for outbound processing) and then I have to manually go in SMQ1/SMQ2 and execute the LUW. Is there any way to avoid such occurences.
For this goto SMQ2--Then Delete or release that Locks and now
goto SMQR Select All QueuesSay Delete
Now goto SXMB_ADMManage Queues-Say Register Queues
Regards
Seshagiri

Similar Messages

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

Alert Configuration for File to IDoc scenario

I have followed Alerts : Step-by-Step /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
and configured Alerts for file to IDoc scenario.
But the problem is, I did not notice any alerts being generated. I could notice the IDocs being posted to destination system. So I was going through Alerts-Troubleshoute Guide. In intension to maintain monitoring level, I clicked Configuration tab. But I did not notice my sender and receiver system there to maintain.
Can any body help me to detail out the procedure to add sender and receiver systems to maintain the monitoring level?
Regards,
Suraj Kumar

hi Suraj,
WHich SP version are you on??
If you are on Sp14 or above, then unfortunately, Michal's Trouble Shooting for Alerts will not help.
From SP14 onwards, activation of end to end monitoring is not needed for Alerting. Refer to this note 870232 for this info.
Next, to test if your Alerts have been defined correctly, go to SE38. In the program , type RSALERTTEST and then click on EXECUTE button ( F8 ). In the next window, it will ask you for your ALERTCATEGORY. Just give the name of your ALERT CATEGORY and click EXECUTE.
If you have configured your alerts correctly, you will receive a message that tells ALERT IS GENERATED and will give the ALERT ID.
Now, go to your Run TIme workbench and then select ALERT INBOX and see if you have got the ALERT message in your ALERT INBOX.
If this is working fine, then the last step, implement the note 913858.
Regards,
Bhavesh

Transactions used in simple file-idoc scenario

hi all,
what are the transactions used in idoc scenario...(Ex: idx1 for creating new idco)
let me know what is the transaction code to find the clients available...
Is it 'SCC4'
Please provide me required info
Thanks
Narasimha
Edited by: Narasimha bommela on Jan 23, 2008 9:17 PM

Try this guide:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Covers everything from setting partner profiles to monitoring Idocs
I can also recommend this book: http://www.sap-press.com/product.cfm?account=&product=H1935

IDocs not created in file to IDoc scenario

Hi all
I am trying this file to IDoc scenario.
File picked up successfully and sent to R/3 BackendBut Idoc is not postedthe status records
In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
I created/tested all basics like RFC dest, port etc.
File service that I am using is a business service hence I am specifying a Logical system name in
Adapter specific Identifiers of the file service.
I disabled EDI_DC40 control tag record as IDoc adapter
takes care of it.
So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
But SXMB monitor gave an error regarding this control record tagI guess as we have disabled it so there wont be any values
for control record in payload (correct me if I am wrong).
So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
But in the backend I am getting this error regarding partner profile.
I also tried to use an existing profile (LS type) by modifying its inbound parameters to accept CREMAS Idoc.
But the error is as persistent as me
Pls help
Sudhir

Hi
Sender --> LEGACY, maintained in SLD (Logical system).
Receiver--> ENI maintained in SLD with logical sys name M700.
Partner Profile LEGACY maintained in R3.
Following is the IDocOutbound in SXMB monitor in XI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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>0000000000001013</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
<SAP:SNDPRN>LEGACY</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPENI</SAP:RCVPOR>
<SAP:RCVPRN>M700</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
</SAP:IDocOutbound>
Control record of IDoc in R3
Tab: Typeinfo
 Basic type-->CREMAS03
 Message Type-->CREMAS
Tab: Partner
 Recipient
 Port -->SAPENI
 Partner Number--> M700
 Partner Type-->LS
 Sender
 Port -->SAPAXI
 Partner Number--> LEGACY
 Partner Type-->LS
Pls help
Regards
Sudhir

Receive acknowledgement in file-to-idoc scenario

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

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

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

System Level Acknowledgement in File to IDOC Scenario

Hi All,
I have the File-> IDOC Scenario. Once the IDOC is successfully sent to R/3, PI should send a acknowlement file back to the sender system.
Could someone suggest how to design this scenario?
Should I use IDOC Acknowledgement. As it is a existing scenario, I dont want much change in r/3 side.

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

How to catch Posting error in File to IDoc Scenario?

I have successfully completed File to IDoc Scenario. Now I am interested in catching posting error. i.e., if mapping goes well and when IDoc is being sent to Recipient system then if any posting error is encountered, then a mail should go to a recipient.
Can anybody suggest the solution.
Regards,
Suraj Kumar

Hi Suraj,
this can be done by triggerring an alert to the recipient.chk out these links to trigger a alert
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
/people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
regards
jithesh

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

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

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

IDOC Scenario - User has no RFC authorization for function group EDIN

Hi all,
I'm trying to configure an IDOC scenario from ECC to XI.
RFC's, ports and destinations already configured. On WE19 I'm creating an IDOC for testing the scenario. The IDOC is sent successfully, and it stops on TRFC Monitor with error "User PIRFCUSER has no RFC authorization for function group EDIN." .
Some of you knows what authorization is needed? Basis team said the roles are the same at DEV environment, and there this scenario works fine.
Thanks for your help.
regards.
Roberti

Hi,
Check with PIRFCUSER user , that is having the right authorization or not ..
And make sure that this user is present in the system & it should not locked.
to check that user is present or not-----goto su01 of the system & check
Regards
Seshagiri

XI unable to post IDOC to ECC the interface is FILE-to-IDOC scenario

Hi All,
The XI interface is a FILE-2-IDOC scenario and some times IDOC's in the receiver system are not posted. I did see successfully message for that particular messages but the IDOC's were not created in the ECC. If the messages is reprocessed then IDOC's are posted successfully to the ECC system. The message has checkered flag in the SXMB_MONI tcode.
This issue is occurring intermittently so could some point me in the right direction how to trouble shoot the issue.
Thanks,
Sarvesh

Hi,
Interesting problem...since its intermittant..
You cannot use any of the traditional RWB or message monitoring or cc chanel monitoring here as the error is in the ecc system, so from an XI standpoint it has left XI succssfully..that explains all the chequered flags..indicating success.
we19, we12, we14(process all idocs) test out the whole process with a load..use transaction we46..this can tell you why it is failing....in r/3
from the ecc system to check inbound queue monitoring.
from there you can select the IDocs or queues which you want to monitor, using the specified selection parameters available.
Look at the status record for the idoc that should give you more information, processing status of the idoc...that should tell you the status code assigned to it..
There is one other option here....if you can figure out what sequence they need to be posted in...that might be the reason for the failure..you can specify the sequence to post the idocs in, use qRfc ..
Hope that helps
Regards
Ravi Raman

File to IDOC scenario not working

I have configured a file to idoc scenario and kept the XMl file in a shared location on XI server.
I have also created and checked the communication channels correctly.
Once Everything is done my xml file does not get picked up at all. Also the SXMB_MONI does not show any messages for my service.
How do I find out what is the error ??

Hi Kapil,
Just check the File path that was in shared location once and the file name is properly mentioned or not..
And also one thing after activating all IR and ID just goto SXI_CACHE and press F6 to update cache refresh
And also in RWB --> Message Monitoring --> Adapter monitoring --> check the status of the sender
Regards,
Sridhar

File to IDOC scenario using FTP server

Dear Experts,
I'm getting IDOCs in the form of .TXT file from sender side and at reciever end we have IDOC. We are using FTP connection at sender.
I want to know:
1. Is FCC the only solution to integrate with PI or do we have any other option also?
2. What all the things I need to care in designing and configuration?
Thanks a lot.

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

SOAP to IDOC scenario: java.lang.NullPointerException

Our trading partners currently post their xml files directly to our Integration Engine, where they are converted to idocs and posted to ECC. I am now trying to change this scenario to a SOAP to IDoc scenario so that we can process the files through the Adapter Engine using HTTPS. But I am running into an error when trying to post an xml file and I'm wondering what I am missing.
My SOAP communication channel is configured as follows:
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter engine: Integration Server
HTTP Security Level: HTTP
Do Not Use Soap Envelope: *Checked*
Default interface and namespace have been specified
QoS: Exactly Once
If I post an xml file to this channel using the RWB test tool, I receive message java.lang.NullPointerException. However, I can find the message via the Message Monitoring in the RWB, with versions for both the AE and IE, each with status Successful. The idoc is created and successfully posted to ECC.
If I post this same file to the same URL using a third-party tool, I get the same error message along with more details (listed below). Futhermore, a message does *not* show up in the RWB and thus does not get converted to an idoc and posted to ECC.
Any ideas??? Thank you.
<?xml version="1.0" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Body>
- <SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
- <detail>
- <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
<context>XIAdapter</context>
<code>ADAPTER.JAVA_EXCEPTION</code>
- <text>
- <![CDATA[
java.lang.NullPointerException
 at com.sap.aii.messaging.net.MIMEInputSource.decodeContentType(MIMEInputSource.java:425)
 at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:323)
 at com.sap.aii.messaging.net.MIMEServletInputSource.parse(MIMEServletInputSource.java:58)
 at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:381)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
]]>
</text>
</s:SystemError>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>

Here's the message log found in End-to-End monitoring from RWB test post (different from third-party tool message):
java.lang.NullPointerException
 at com.sap.plaf.frog.FrogScrollPaneUI$1.propertyChange(FrogScrollPaneUI.java:113)
 at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
 at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)
 at java.awt.Component.firePropertyChange(Unknown Source)
 at javax.swing.JScrollPane.setHorizontalScrollBar(Unknown Source)
 at javax.swing.plaf.basic.BasicComboPopup.createScroller(Unknown Source)
 at javax.swing.plaf.basic.BasicComboPopup.<init>(Unknown Source)
 at com.sap.plaf.frog.FrogComboPopup.<init>(FrogComboPopup.java:21)
 at com.sap.plaf.frog.FrogComboBoxUI.createPopup(FrogComboBoxUI.java:410)
 at com.sap.plaf.frog.FrogComboBoxUI.installUI(FrogComboBoxUI.java:178)
 at javax.swing.JComponent.setUI(Unknown Source)
 at javax.swing.JComboBox.setUI(Unknown Source)
 at javax.swing.JComboBox.updateUI(Unknown Source)
 at javax.swing.JComboBox.init(Unknown Source)
 at javax.swing.JComboBox.<init>(Unknown Source)
 at com.sap.jnet.clib.JNcToolBar$ComboBox.<init>(JNcToolBar.java:64)
 at com.sap.jnet.clib.JNcToolBar.addComboBox(JNcToolBar.java:192)
 at com.sap.jnet.clib.JNcAppWindow.newUI(JNcAppWindow.java:607)
 at com.sap.jnet.clib.JNcAppWindow.newData(JNcAppWindow.java:1097)
 at com.sap.jnet.JNetData.createGraphFromDOM(JNetData.java:512)
 at com.sap.jnet.JNetData.load(JNetData.java:709)
 at com.sap.jnet.JNetApplet.initJNetApplet(JNetApplet.java:524)
 at com.sap.jnet.JNetApplet.access$000(JNetApplet.java:40)
 at com.sap.jnet.JNetApplet$1.run(JNetApplet.java:265)
 at java.awt.event.InvocationEvent.dispatch(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
 at java.awt.EventDispatchThread.run(Unknown Source)

IDoc scenario monitoring,,,

Similar Messages

Maybe you are looking for