Problem In IDX5

Hi Experts,
There is an error Message in IDX5 when i double click on IDOC Number.
File to IDOC scenario, If we double click on IDOC number it will be connecting to ECC system, but it is showing the error message on the status bar
"Error for the remote call of method RSEIDOC2_CALL_VIA_RFC_DOCNUM in system ZM1CLNT100 message control FrameWork Fatal error - GUI cannot be rea"
Can any body help on this issue
Regards
Sankar

Hi,
Can check what error it is showing in sxi_monitor for that message?? Have you defined rfc destination of type R3 in your XI system to your target (SAP R/3) system?? Test if the RFC destination is working fine from your XI to R/3 system.
Thanks!!

Similar Messages

IDOC-XI scenario problem

I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?

Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k

FILE-RFC ADAPTER problem

Hi all,
I am trying file->xi->rfc adapter scenario.
My scenario is employee information is written to flat file n will be kept on ftp server.THe file adapter will pickup the file and sends it to rfc adapter through pipeline service.
This is going well. The problem is the data is not being updated into receiving sap system.
in SXMB_MONI transaction the messages are successully processed . But there are no messges in rfc adapter when i gone through idx5 transaction???
Any one have idea??
Thanks in advance.
Rgds,
Ram Sri

sxmb_moni only shows the status of the integration engine's processing, not the result of what happened in the rfc call. First, you can check if the adapter framework successfully passed the message to the destination system (not on moni, thru RWB)
as far as did the rfc succeed - it's as difficult as always with internal processing. We did a lot of testing by debugging modules on the destination side (manually putting in the data as the adapter would've to step thru & see where the message is "lost") - have not yet found a better way, sorry. It's not so much a problem with XI, just in general the difficulty to debug rfc's

Problem With Seeing Message in Adapter Engine

Hello Everyone,
We are facing a strange problem while running an Integration Process, BPM in PI. In the process, we are trying to read a .CSV File and convert it into a .XML File via FCC. The .CSV file is placed in the XI box itself, under a certain directory. We have configured the process such that whenever the .CSV file is read, its attributes are set to 'read only'. After configuring the process, the required XML file did not show up. So we checked that whether the .CSV file was read and it showed up attributes of 'read only'.We cross checked
 -First by going to SXMB_MONI; here it said 'No messages available for selection'
 -Then by examining the 'channel monitoring' in AE; where we found both the sender and receiver channel are showing green. The sender channel first shows up that 'Processing started' and then 'Processing Completed Successfully'. The receiver channel does not show up any messages.
 -we checked for the XML messages that are in the Adapter in IDX5; it shows 'no messages selected'.
 -We anticipated that it may be a cache problem and cleared all the caches; but when we tried to clear the Adapter Framework Cache, it popped up an authorization error and the problem persisted.
We are using NW2004s with SP6 at the ABAP and BASIS stack and SP 9 at the Java Stack. Also, all the required connections made in SM59 are in order.
Now, What can be the problem? Is it the difference in SP level that is causing the problem? Or is it something else? What have we missed? Guys, please help us solve this problem.
Need Help. Pleae Reply. Points will be awarded.
Thanking in anticipation.
Amitabha

Hi Shabarish,
1.Document name is indeed the name of message type in our case.
2. We did not use delete mode; but once the file was read- we manually changed its attributes from 'RA' to 'A'..and it became 'RA' again after 2 seconds; which is our polling interval.
3. And we have discovered that the file is being read properly..because we can see the XML payload of it and it contains the correct data.But still it does neither show up in SXMB_MONI..nor in IDX5.
Can you please tell us what are the necessary roles for the User PIAFUSER? We suspect that somewhere's an authorization error we are getting; because the AF cache refresh attempt shows "Forbidden" and we are getting an error in Tcode SXI_SHOW_MESSAGE as:
AE_DETAILS_GET_ERROR: no_adapter_engine_found: Unable to find Adapter Engine:; Stack trace shows:Error while reading access data (URL, user, password) for the Adapter Engine

Problem in IDOC

Hi,
I am working on IDOC to Mutiple target systems..and the IDOC is extended at the ECC side..and my IDoc extension looks is like this.
ZX/AFS/DELVRY03.
i have imported the idoc succesfully in PI and dragged it to the source message of message mapping after which it looks like this.Z_-AFS_-DELVRY03.
Now When i do my end to end testing, i am getting the weird error as
"<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem evaluating a condition: An exception has occurred.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: An exception has occurred. Problem evaluating a condition: An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. Problem extracting values from the Payload: Check line 1 column 42 of the XML document</SAP:Stack>
When i changed the idoc name in Inbound payload from ZX/AFS/DELVRY03 to Z_-AFS_-DELVRY03.it executes succcesfully in message mapping and even in RWB.
I am not able to do my end to end testing just because of this reason..can someone help me with this?
regards
Edited by: ayrahcaanilan on Jan 13, 2011 4:59 AM

Hi Prakash,
Yes..You are right."In XI '/' will be represented by _- . So Payload shoudl have _-.".
and this happens automatically..
but why is that failing for my interface..every idoc which come in IDX5 shows the same error.and the other thing is even the inbound message payload gives this error.
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
The character '>' was expected. Error processing resource 'file:///C:/Documents and Settings/9toufe5/Local Settings/Tempora...
<?xml version="1.0" encoding="UTF-8" ?><ZX/AFS/DELVRY03><IDOC BEGIN="1"><EDI_DC40 SEGMENT="1"><TA....
i cant edit my Source idoc since its coming directly from ECC.i tried reimporting the idoc and testing.but it still sgives the same error.
Regards

Time limit Exceeded problem

Hi ,
I have a file to idoc scenario .
I have a file which generates many idocs (size atmost 5 mb)
I am aware sap recommends to limit the message the file size to atmost 5mb.
Do they mean file size of the payload ...because size increases in xi also .
I just want to process such a file quickly .
For that I am employing queue priortization at both sender and reciever .
and would idoc packaging help at the receiver .
Besides I am getting 'time limit exceeded in sm58' although I am seeing my idocs in idx5.
Here are some of the things I have checked ..
1) Parameters in SXMB_ADM - Integration Eningine configuration ---Specific configuration ...tried various tuning parameters ...but it didn't work..
2) In partner profile in recieving CRM system made chagend the setting from trigger immediately ..to background Task ...
(I am not certain how far that is relevant .
If it is a problem with CRM system's ability to accept mass idocs (because a small number is acceptible ...under 1mb file size ) then seetings should in crm so that large number idocs get succesfully posted .
I have posted this issue several times ...Kindlyhelp
KIndly what parameters i should tweak in xi or that matter recieving crm system to take care of this problem.
Kindly help

HI,
Large size of file processing
In general, an extra sizing for XI memory consumption is not required. The total memory of the SAP Web Application Server
should be sufficient except in the case of large messages (>1MB).
To determine the memory consumption for processing large messages, you can use the following rules of thumb:
Allocate 3 MB per process (for example, the number of parallel messages per second may be an indicator)
Allocate 4 kB per 1kB of message size in the asynchronous case or 9 kB per 1kB message size in the synchronous case
Example: asynchronous concurrent processing of 10 messages with a size of 1MB requires 70 MB of memory
(3MB + 4 * 1MB) * 10 = 70 MB With mapping or content-based routing where an internal representation of the message payload
may be necessary, the memory requirements can be much higher (possibly exceeding 20 kBytes per 1kByte
message, depending on the type of mapping).
The size of the largest message thus depends mainly on the size of the available main memory. On a normal 32Bit operating system, there is an upper boundary of approximately 1.5 to 2 GByte per process, limiting the respective largest message size.
please check these links..
/community [original link is broken]:///people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
Input Flat File Size Determination
/people/shabarish.vijayakumar/blog/2006/04/03/xi-in-the-role-of-a-ftp
data packet size - load from flat file
How to upload a file of very huge size on to server.
Regards
Chilla

File-to-Idoc - field population problem.

Hi All,
Im getting the following problem.
My scenario is Filetoidoc.
Problem:
In the interface mapping Im able to see all the values are populated correctly for Idoc.but when I see in IDX5 or SXMB_MONI one value instead of populating correctly replacing , in that field.
Im using Java mapping program also to convert the file in to desired structure.
Thanks in advance.
Venu.

Hi All,
The out put from the above java program is.
<?xml version='1.0' encoding='UTF-8'?><ns0:MT_MeterReading_IntermediateForm xmlns:ns0="urn://MVP_SR3_01/MVP/MeterReading"><Recordset><H1><Recordid>H1</Recordid><RouteNumber>10151G</RouteNumber><MetReaderId>002</MetReaderId><TotRead>000015</TotRead><TotDevUploaded>000016</TotDevUploaded></H1></Recordset><Recordset><H1><Recordid>H1</Recordid><RouteNumber>10151G</RouteNumber><MetReaderId>SYSADMIN</MetReaderId><TotRead>000000</TotRead><TotDevUploaded>000000</TotDevUploaded></H1><Item><D1><HMetReaderId>SYSADMIN</HMetReaderId><HTotDevicesUploaded>000000</HTotDevicesUploaded><AccountNumber>6205</AccountNumber><MeterReadCode>0000001495</MeterReadCode><ReadDate>20060819</ReadDate><TroubleCode></TroubleCode></D1><D2><ChgdSplInstr>IN FOOTPATH DOG BITES information for service order</ChgdSplInstr></D2><U2><Data>33333300100451</Data></U2><UC><Data>SKIP TEST COMMENTS FROM METER READER FOR 4000734 MRo with RR '09' </Data></UC></Item></Recordset></ns0:MT_MeterReading_IntermediateForm>
In abobe result last Data field value is populated correctly . the above result is from interface mapping.
but when the idoc is generated in XI. I'm unable to see the value.
Thanks,
venu.

Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller: PIAFUSER
FM: IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server; and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

Problem with IDOC : caracter shifted in RWB

Hi experts,
I am having a slight problem while sending my messages from Idoc to JDBC.
In the Idoc, I fill the fields right, the problem is that when I go to the RWB to check the message I sent, in the XML, the caracters are all shifted. In example, in the field <KUNNR> am supposed to get <KUNNR>1234567890<\KUNNR> (ten caracters). Instead, in the RWB I get <KUNNR>123456789<\KUNNR> and the last caracter is shifted in the next field and so on.
Does anyone knows where this might come from?
Thanks a lot, any help would be appreciated
Regards,
Jamal
Edited by: ba_da_boom on Aug 5, 2008 12:07 PM

Hi,
The problem is because of the Meta Data.
Delete the IDoc meta data from IDX2 and reload it.
Whenever there is a change in the IDoc structure you have to delete and load the metadata in IDX5.
1. Go to IDX2.
2. Expand the R3 Port.
3. Choose the IDoc type and delete.
4. Import the Metadata again by clicking on the button new and giving the IDoc message type and the source port detail.
Thanks
SaNv...

IDOC to xi problem IDOC not reaching xi

Dear all,
this is a case of IDOC scenario in development server.
we are sending a IDOC form R/3 system to xi system,and when we are checking it with Tcode sm58 ,it is coming as status 12 .
but when we try ti view this IDOC in xi system with Tcode IDX5 nothing is coming. we check every thing like port configuration in IDX1 and IDX 2.
we checked the code also which is used to trigger Idoc from R/3 System. every thing is fine thete also.
please give some input regarding this problem.
thanks and regards,
Navneet Sumit

HI,
Check whether u have done the proper configuration at the R3 end.
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Thnx
Chirag

Queue problem ?

I am working on IDOC-XI-FIle scenario.
I see IDOC in IDX5 but file is not created.
SXMB_MONI has a status of 'Scheduled for outbound status'. When I dbl-click the message to view the message, I get empty screens (no message details are seen). But If I go to RWB and click on message details,
(status is waiting), I do see the message XML details (for the same message ID).
Queue status on sxmb_moni line has status of 'Stopped'.
SMQ2 shows status of 'SYSFAIL' for XBT0___000.
SMQR has scheduler status of 'INACTIV' and all queue have type field eq 'R'.(so all of them are registered).
Though I do not see XBTO* in the list !!!!
ANy ideas what is happening ?
-Thanks
Bhaven

They were active and registered.
But I am still having problem to create the file.
It is a very simple mapping and sxmb_moni is giving error in the mapping step. I copied the XML data and map works perfect in IR.
If I remove the map from interface determination, file is created.
I also did a IDOC-IDOC map and it still gives the error. Any ideas ?
Error in sxmb_moni is :
Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

IDX5 - System is not a central XI; cannot start program

hi all -
Did anyone come across this error message - "System is not a central XI; cannot start program" when trying to execute the tcode - IDX5 on the XI box?
I pushed an IDOC - MATMAS05 from IDOC to XI. It doesn't come into XI.
1. I checked the SM58 on the R/3 side. No Messages.
2. I checked the IDX5 transaction on the XI side, that's when i get the above error message.
3. I checked the IDX2 transaction on the XI side, i get this error "I:000" - Anyone knows what it means?
4. SXMB_MONI doesn't show up anything.
5. R/3 - pushed idocs shows a status of 3.
Any ideas where to look for and how to solve the problem -IDX5 and IDX2.
Environment:
1. We are using SAP NW 2004s
2. SAP BASIS Component - SAP_BASIS - Release 7.00
Thanks in advance,
Tirumal

Hi,
I think port configuration in IDX1 may be not correct,
Anyway check out this SAP note- 940313
Also refer this analysis:
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Regards,
Moorthy

Problem with XI simple scinario

Hi Friends,
I am new in XI, I am working on simple xi scenario. whn i create sales order i wan to send order confirmation . for that i am using ORDRSP. I had done all the ale settings and able to generaet idoc and send it to XI . Now the problem is that,once the idoc is sent from R/3 system, on the XI system I am not able to see it in transaction SXMB_MONI. I am able to c that idoc in transaction WE02,with error in XI system.
So please let me knw,how to solve this.
Regards,
Brij.....

hi,
plz once check in idx5 in xi server..
if u r able to see u r idoc in that then u can confirm u er IDOC reached to XI server..
if IDOC is not there in IDX5, plz do check in RFC destination remote connection, if u get the EASY ACCESS MENU of the XI system, then RFC destination is fine.
and once check port and partner profile also....
if u check all these things.. hope u r problem will be solved.
Thanks,
Madhav
Note:Points if useful

Idoc to file problem.......... IDOC lost

i have a idoc to file problem,
the idoc is sent from R/3 to XI,
the problem is IDOC is sent from R/3,
it didnt reach to XI.....
i have checked.......we05 in R/3, it gives a status 3,
then i checked SM58 in R/3, it shows nothing,
when i check in idx5 in XI, theres no trace of that idoc....and no trace of the scenario run in SXMB_MONI
pls help, where can i trace the idoc.....
pls help

Hi sudeer,
Did You Check It In WE19.(Test Tool For Idoc Processing)
If Not Do The Following Steps:
Step1:
>> Give Your Existing Idoc Number.
Step 2:
>> Basic Type is Your Message type.
 Ex: MATMAS05 or CREMAS05.
Step 3:
>> In Your Existing MATMAS05 or CREMAS05 Structure say EDIDC,
>> You Should Fill Your Mapped Entries In Data Structure of EDIDC.
>> So that Those Fields Gets Framed as Segments.
Step 4:
>> After Doing It goto Menu Bar and Click Idoc And Goto Edit Control Record.
Step 5:
>> Now You Give Your Sender And Receiver Port Number Along With Your
 Logical System And Message Type again its Your MATMAS05 or
 CREMAS05 .
Step 6:
>> After Doing It Click Standard Outbound Processing.
Step 7:
>> It Will Say what Happened To your Idoc.
Step 8:
>> It Is For Sure That if This Processing Fails It Wont Go To XI..
Regards,
Dhayanandh .S
Dont forget To Provide Points If Found Helpful...
Message was edited by:
 DHAYANANDH SIVASANKARAN

Lock table overflow problem in transaction sm58

Hi ,
I have a file to idoc scenario.I am on xi 7.0 sp09.
I am posting about 10000 records at one time in a 1 mb file.
In idx5 i am able to idocs .
However in transaction SM58 I am seeing Lock table overflow error .
Regards ,
Deepak

Deepak,
Here you can solve the problem in two ways
1) increase the size of the lock table via parameter
enque/table_size
2) or increase the enque work processes from 1 to 2 or 3
via parameter rdisp/wp_no_enq
Please have a look on SAP Note: 928044.
---Satish

Problem In IDX5

Similar Messages

Maybe you are looking for