RFC dump : 'Message type " " is unknown.'

Hi everyone,
I am calling an RFC from one system to another and i am getting a dump with error :
Message type " " is unknown.
When i debugged the program the found that nothing is returned for " MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. "
What should i do to rectify the problems? Please do help.
Thanks In Advance.
Regards,
Heera

ABAP runtime errors MESSAGE_TYPE_UNKNOWN
 Occurred on 03/05/2008 at 21:56:28
Message type " " is unknown.
What happened?
The current ABAP/4 program "Y_MM_C_CICS_MAT_RECON " h
because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 progra
What can you do?
Print out the error message (using the "Print" functi
and make a note of the actions and input that caused
error.
To resolve the problem, contact your
SAP system administrator.
You can print this message by choosing "Print".
Transaction ST22 allows you to display and manage sho
is especially useful if you want to keep a particular
Error analysis
Only message types A, E, I, W, S and X are allowed.
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_UNKNOWN"
"Y_MM_C_CICS_MAT_RECON " bzw. "Y_MM_C_CICS_MAT_RECON "
"START-OF-SELECTION"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
 To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
 To obtain this, call the system log with Transaction SM21
 and select the "Print" function to print out the relevant
 part.
3. If the programs are your own programs or modified SAP programs,
 supply the source code.
 To do this, you can either use the "PRINT" command in the editor or
 print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
 or which actions and input led to the error.
System environment
SAP Release.............. "46B"
Application server....... "fmsap591"
Network address.......... "10.19.196.114"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x IA64 Level 3"
Database server.......... "FMSAP591"
Database type............ "ORACLE"
Database name............ "AI0"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "46D"
Created on............... "Jul 30 2007 00:11:29"
Created in............... "NT 5.0 2195 Service Pack 2 x8
Database version......... "OCI_920_SHARE__OCI_7_API "
Patch level.............. "2335"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.0.5.., ORACLE 8.0.
8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 1
SAP database version..... "46D"
Operating system......... "Windows NT 4.0, Windows NT 5.
Windows NT 5.2, , System build information:,
 , LCHN : 921411"
User, transaction...
Client.............. 250
User................ "HPRAMANX"
Language key........ "E"
Transaction......... "SE38 "
Program............. "Y_MM_C_CICS_MAT_RECON "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP/4 program "Y_MM_C_CICS_MAT_RECON " in
"START-OF-SELECTION".
The main program was "Y_MM_C_CICS_MAT_RECON ".
The termination occurred in line 371
of the source code of program "Y_MM_C_CICS_MAT_RECON " (when calling the editor
3710).
Source code extract
003410 r_lgort-sign = 'I'.
003420 r_lgort-option = 'EQ'.
003430 r_lgort-low = x_storeloc_wa-ecc_st_locn.
003440 APPEND r_lgort.
003450 ENDLOOP.
003460
003470
003480 *CALL RFC TO GET MATERIAL DATA FROM F PIPE BY PASSING S_MATNR r_werks
003490 *r_lgort S_CHARG AND GETTING THE REQUIRED DATA BACK IN THE TABLE
003500 *I_MCHBF
003510
003520 CALL FUNCTION 'YCICS_MATERIALDATA'
003530 DESTINATION 'FI0250'
003540 TABLES
003550 i_matnr = s_matnr
003560 i_werks = r_werks
003570 i_lgort = r_lgort
003580 i_charg = s_charg
003590 i_mchb = i_mchbf
003600 EXCEPTIONS
003610 no_data_found = 1
003620 material_not_of_type_fert = 2
003630 invalid_plant_entry = 3
003640 invalid_stloc_entry = 4
003650 invalid_plnt_matnr_combi = 5
003660 invalid_plnt_matnr_batch_combi = 6
003670 invalid_plnt_matnr_batch_stloc = 7
003680 OTHERS = 8.
003690 IF sy-subrc <> 0.
003700 MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 > WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
003720 ENDIF.
003730
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 1 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 31
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
VARI
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40 ####00000000000000
 2222222222222222222200003333333333333322
 0000000000000000000000000000000000000000
... + 80 ####################################
 2222000000000000000000000000000000000000
 0000000000000000000000000000000000000000
... + 120 ########################################
 00000000
 0000000
SY-MSGV1
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40
 2222222222
 0000000000
SY-MSGV2
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40
 2222222222
 0000000000
Y-MSGV3
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
.. + 40
 2222222222
 0000000000
Y-MSGV4
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
.. + 40
 2222222222
 0000000000
_MCHB #######################################
 0000000000000000000000000000900000009000
 0000000000000000000000004000060000001000
.. + 40 ####0###0#######ÿÿÿÿ:###########è ####
 1000300030000000FFFF300000000000EA280000
 0000020001000000FFFFA000200043008D030000
.. + 80 x> ####################################
 7328000000000000000000000000000000000000
 8E03000000000000000000000000000000000000
.. + 120 ########################(#######
 00000000
 0000000
MCHBWA 000000000000895405CR01CRA10001 CR01TE
 3333333333333333334533454333332222453354
 0000000000008954053201321100010000320145
.. + 40 ST05####e#########
 553300006000000000
 3405000150C000000C
SCHARG_%_APP_% S_CHARG S_CHARG to
 5544454255444542222222222222222222222276
 3F3812703F38127000000000000000000000004F
.. + 40
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
.. + 80 @1FQMultiple selection@
 2224345547676766276666766642222222222222
 000016C1D5C490C5035C5349FE00000000000000
.. + 120
 222
 000
X_MCHBF_WA
 2222222222222222222222222222222222222222
 0000000000000000000000000000000000000000
... + 40 00000000 00000000
 3333333322222222222233333333222222222222
 0000000000000000000000000000000000000000
... + 80 000000 #################################
 3333332000000000000000000000000000000000
 0000000000000C000000C000000C000000C00000
... + 120 ########################################
 00000000
 0C00000
I_MCHBF ################@#######################
 0000000000000000400000000000100000000000
 1000400040004000080050004000080000000000
... + 40 ################ÿÿÿÿÓ###################
 1000000000000000FFFFD0000000000000000000
 0000000000000000FFFF30007000630000000000
... + 80 ########################################
 0000000000000000000000000000000000000000
 0000000000000000000000000000000000000000
... + 120 ########################8#######
 00000000
 0000000
SYST ########################################
 0000000000000000000000000000000000000000
 0000000010000000000000000000000000000000
... + 40 ####################ã###################
 10000000000000000000E0000000000000000000
 F00000001000000010003000000000000000F000
... + 80 ########################################
 0000000000000000000000000000000000000000
 0000000000001000800000000000000000000000
... + 120 #######################################
 00000000
 0000000
X_MKPFMSEG_WA-BKTXT
 2222222222222222222222222
 0000000000000000000000000
%_SPACE
 0
 0
X_OUTPUT_WA-BTEXT
 22222222222222222222
 00000000000000000000
X_MCHB_WA-MATNR 000000000000895405
 333333333333333333
 000000000000895405
X_MKPFMSEG_WA-WERKS
 2222
 0000
X_MCHB_WA-WERKSF CRA1
 4543
 3211
X_OUTPUT_WA-WERKS
 2222
 0000
X_MCHB_WA-LGORTF
 2222
 0000
X_MKPFMSEG_WA-LGORT
 2222
 0000
X_MCHB_WA-CHARG CR01TEST05
 4533545533
 3201453405
Active calls / events
No.... Type........ Name..........................
 Programm
 Include Line
 1 EVENT START-OF-SELECTION
 Y_MM_C_CICS_MAT_RECON
 Y_MM_C_CICS_MAT_RECON 371
Internal notes
The termination occurred in the function "ab_jmess" of the SAP
Basis System, specifically in line 1083 of the module
"//bas/46D/src/krn/runt/abdynpro.c#22".
The internal operation just processed is "MESS".
The internal session was started at 20080305215621.
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=24072)
When : 3/5/2008 21:56:28.0
Threads : 2
Computer Name : FMSAP591
User Name : ai0adm
Number of Processors: 2
Processor Type: ia64 Family 31 Model 1 Stepping 5
Windows Version : 5.2 Current Build: 3790
Stack Dump for Thread Id 56f4
FramePtr ReturnAd Param#1 Function Name
00000000083a0c00 0000000076eab530 00000000000024f4 kernel32!GetDateFormatW
00000000083a0bd8 000000000215a7c0 00000000000024f4 kernel32!GetDateFormatW
00000000083a0b88 000000000067fe80 0000000000000080 disp+work!
000000001c1b0040 0000000076ea7420 0000000000212e50 MSVCRT!tanhf
000000001c1b0000 0000000000000000 000006fb7eb36e88 kernel32!GetDateFormatW

Similar Messages

How to populate the RFC .Exception Message Type?

Hi All,
I am invoking an RFC synchronously from PI.
I am using the RFC.Exception message type to capture the exception raised from the RFC.
In the RFC, I have created a Non-class based exceptino anf raising it using the "Raise" command.
But it is only pupulating "Name" and "Text" of the Exception message. All other fileds are blank.
Is their a special way to raise the excpetion in rfc so as to populate the Exceptoin message type in PI completely?
thanks,
Piyush

But it is only pupulating "Name" and "Text" of the Exception message. All other fileds are blank.
Did you follow the steps as mentioned in this blog: /people/jin.shin/blog/2007/05/21/handling-web-service-soap-fault-responses-in-sap-netweaver-xi
Regards,
Abhishek.

Message type 1 unknown error occuring when clicked on IP workbook button

Hi,
I am working on authorization.
When i click on the save button in an IP workbook button, it throws the message "Message type 1 unknown" saying
that an error occured during communication with bw server, and its gets disconnected.
I have included authorization objects for the planning sequences, planning functions, process chains, also included tcodes for ADP ie rsanwb and tcodes
for ABAP programs. Still we are facing with the same problem.
Please suggest me the solution ASAP and points are awarded.
Thanks.

Hi Suresh,
I guess you have posted your question in the wrong forum.
This forum is exclusively for MDM related queries.Yours looks like a BW or ABAP related question.
Kindly repost your question under the respective forum to get immediate assistance.
Hope It Helps
Thanks & Regards
Simona Pinto

Message type " " is unknown

Hi Masters
When i try to cancel the subcontracting challan in T code J1IF13, it throws a run time error "Message type " " is unknown" .We discussed with the ABAPer regarding this error.He told that we have to maintain the message type in configuration. Where to maintain the message type for subcontracting challan?
Regards
Mohanraj.C

Use
The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
Requirements
Before you continue with this activity, work through the following activities:
Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Maintain Output Types.
Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Assign Forms and Programs.
Maintain the Program, FORM routine, and the form for the output type.
Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Printer Determination -> Printer Determination by Plant / Storage Location.
Enter the output device that you use.

HCM Processes & Forms - Message Type is unknown

Hi,
I have created an HCM process using HCM P&F framework. I can test the process from the ""Test Process" application on the ECC and it works fine. When I launch the process from the portal, I can see the adobe form correctly, the "Check and Send" also goes through fine, but when I click on send I get this error:
Error when processing your request
What has happened?
The URL http://xxxxxxxxxx:8000/sap/bc/webdynpro/sap/ASR_PROCESS_EXECUTE// was not called due to an error.
Note
The following error text was processed in the system SE1 : Message type is unknown.
The error occurred on the application server xxxxxxxx_SE1_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_POBJ_CASE~CREATE_CASE of program CL_POBJ_CASE==================CP
Method: CREATE_LEVEL_DB of program CL_POBJ_LEVEL=================CP
Method: FLUSH_LINKED_LEVEL of program CL_POBJ_LEVEL=================CP
Method: FLUSH_COMMON of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL1================CP
Method: IF_POBJ_PROCESS_OBJECT~FLUSH of program CL_POBJ_PROCESS_OBJECT========CP
Method: SAVE of program CL_HRASR00_PROCESS_RUNTIME====CP
Has anyone else encountered this issue?
Thanks & regards,
Manish

Hi,
I have created an HCM process using HCM P&F framework. I can test the process from the ""Test Process" application on the ECC and it works fine. When I launch the process from the portal, I can see the adobe form correctly, the "Check and Send" also goes through fine, but when I click on send I get this error:
Error when processing your request
What has happened?
The URL http://xxxxxxxxxx:8000/sap/bc/webdynpro/sap/ASR_PROCESS_EXECUTE// was not called due to an error.
Note
The following error text was processed in the system SE1 : Message type is unknown.
The error occurred on the application server xxxxxxxx_SE1_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_POBJ_CASE~CREATE_CASE of program CL_POBJ_CASE==================CP
Method: CREATE_LEVEL_DB of program CL_POBJ_LEVEL=================CP
Method: FLUSH_LINKED_LEVEL of program CL_POBJ_LEVEL=================CP
Method: FLUSH_COMMON of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL1================CP
Method: IF_POBJ_PROCESS_OBJECT~FLUSH of program CL_POBJ_PROCESS_OBJECT========CP
Method: SAVE of program CL_HRASR00_PROCESS_RUNTIME====CP
Has anyone else encountered this issue?
Thanks & regards,
Manish

Message type " " is unknown. Transaction J1IF13

Dear all,
When i am executing transaction J1IF13 for Subcontracting i am getting this error "Message type " " is unknown."
i want to cancel the transaction
Regards
Amey

Closed

Updates rules activation triggers dump message type X

Hi,
In an existing update rule, I am trying to add a field (key figure=> characteristic (source)
after I activated the update rules a shot dump is triggered
"Message type X"
message class RSAA
Number 108
trigger location
%_T005N1
Module Name Instantiate
called function :
RSAU_GET_CUBE_TIME
I have already done some consistency test about the infocube in RSRV, but don't dind a clue for the moment.
any help would be grateful
John

Hi
Try to run standard program RSAU_UPDR_REACTIVATE_ALL.
Thanks
lokeshM

Dump "Message X" when converting plan.order in APO (Operation classified)

Hello,
We are using master recipes. One operation is classified with work center class type 019 assigned. Operation is classified with two values so I get two alternative modes in APO PDS.
I can drag and drop between alternative modes in the Planning Board, and then save so I can see the mode change also in the order processing view for example.
However when I am triggering the conversion of planned to process in APO then order is never converted. An error queue appears in the qRFC inbound monitor in ERP stating that a short dump has occurred
Short dump "MESSAGE TYPE X" Information on where terminated
Termination occurred in the ABAP program "SAPMSSY0" - in "%_ORDER_FORM_LEVEL". The main program was "SAPMSSY1 ".
Thanks in advance
Carlos

Hello Carlos,
Have you updated alternative resources with the values in the user fields of the operation. ?
Also assign the work center class for the operation (same class which you have assigned for the work centers)
Best Regards,
Roopesh
Edited by: Roopesh Menon on Feb 17, 2011 9:55 AM

Distributing message type MATQM using ALE

Hi everybody!
I am using ALE to distribute material data. This already works. Now I also want to distribute material data for quality management.
When I try to distribute materials using BD10 I get this message:
Could not determine recipients for message type MATQM
So I tried to create a new distribution model for MATQM using BD64. Unfortunately I could not choose MATQM or MATQM01 as the message type. (Error: Message type MATQM01 unknown)
However, in transaction WE60 I can display message type MATQM01.
What is the problem?
best regards
Roland

Hi Roland,
BD10 only can be used with message type MATMAS.
If you want to send message type MATQM and IDoc type, please use this FM MASTERIDOC_CREATE_SMD_MATQM. You still need to maintain partner profile (WE20) and IDoc Port (WE21).
Other you can use Change Pointer (BD21) to send out and ensure you have activated the change pointer for message type MATQM (BD50).
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Want create dump message

hi experts,
I want give my own dump message in my report , in the dump i want give my own message in that dump error.
Is there any functional module.i

Execute this
report abc.
message 'This is a custom dump message' type 'X'.

SolMan configuration - Message type "e" is unknown

Hi all,
every time i select the step 6.6 (Connect Diagnostics Agents to Solution Manager) of the System Preparation in SolMan 7.1 SP11 i receive the following message (and related dump in ST22).
Message type "e" is unknown.
Same thing happens in two different Solution Manager (same version and SPS).
Looking for SAP Notes without help.
Any suggestions?
Regards.

Hello guys,
We have a similar issue.
Here is why we got to this error. When i setup the SLD in step 6.1 i used another system, and the Solution Manager was non existent in that SLD/LMDB.
I now configured a local SLD in 6.1 and created a local LMDB.
I am now running the synchronization again ( which as you know takes a while ).
Probably the easiest way would have been just to define the system in the first LMDB, but in our case it's a development system and i wanted to try this also.
I will let you know after the sync is finished.
Catalin

RFC destination for synchronous communication (message type SYNCH)

Hi experts,
I am trying to configuare ALE settings.waht i did is
My sending & receiving systems are one server with different clients.By using SALE transaction
1.crated logical systems.(LS_800 &LR_810)
2.Assigned those to clients.
3.Created RFC destination
4. Created modelview assign sending & receiving
systems and message type.saved it.
4.generated Partner profile.Here i am getting below problem
Target system LR_810
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LR_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Target system LS_800
RFC destination for synchronous communication (message
type SYNCH)
Partner profile LS_810 SYNCH does not exist
Generate partner profile or
specify outbound partner profiles for message type
SYNCH
Regards;
Upender.

Hi Shital;
Thanks for your replay;
Still am getting the Same Error;
Thanks;
Upender.

RFC to RFC - Error in the target RFC - Message type I

Dear all,
I am making a message using from RFC(ECC 6.0) to RFC(ECC 5.0).
It happens an error(System_Failure) because in the target RFC(source code), there is a message type I. I can't take off the message, so how can I create my message without error?
Best Regards,
Fernando

hi,
are you using a BAPI with direct commit fomr RFC adapter?
read info about parameter:
Commit Control for Individual BAPI Calls
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/content.htm
"I" should not affect the commit
if you have the commit inside then don't raise exception
or raise it inside another Function module that will serve as a wrapper
to the one you use)
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

JMS sender adapter : message type null is unknown, payload cannot be read

Hello,
We are building a scenario Weblogic -> PI through a JMS adapter, but we are getting the following error in the adapter :
2009-09-29 12:09:58 Information New JMS message with JMS message ID ID:P<450046.1254218997063.0> received. The XI message ID for this message is e705a65f-3cf6-472a-3675-b04e9862ce45.
2009-09-29 12:09:58 Warning JMS message ID:P<450046.1254218997063.0>: message type null is unknown, payload cannot be read and will be empty!
2009-09-29 12:09:58 Warning JMS message ID:P<450046.1254218997063.0>: Payload empty or cannot be read.
2009-09-29 12:09:58 Information JMS Message was converted to XI message succesfully.
Despite the fact that the message is not readable, PI creates a message anyway but the payload is empty. It is the same issue as described in this thread :
How to read Java Object message from JMS Queue using JMS Adapter .
But there have been no answer there.
We have read many notes but none are relevant, any ideas ????
Many thanks,
GL

Hallo,
Have you seen this note:
[Note 837501 - J2EE JMSAdapter: Empty payloads, unknown JMS message types|https://service.sap.com/sap/support/notes/837501]?
Seems it can be either message
a) does not contain any payload and/or
or
b) is not of type TextMessage or BytesMessage
/Jakub

RFC error "No authorization to send IDOCs with message type ..."

Hi all,
I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
Any suggestions?
Regards,
Liesel

Hi Liesel,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy Thomas

RFC dump : 'Message type " " is unknown.'

Similar Messages

Maybe you are looking for