Sending IDOCs to R/3: Error in SXMB_MONI: Obligatory element missing

Hi,
after sending IDOCs to R/3 we saw that we forgot to maintain IDX2.
Know IDX2 is OK. But we get an error IDOC:Obligatory element xyz missing.
This cannot be, because we also send this IDOCs to another R/3 an everything works fine.
I already refreshed the cache.
Any ideas?
Thanks
Regards Mario

Hi Mario,
have you tried deleting the matadat in IDX2 and reloading it.
Regards
Kenny

Similar Messages

Import container contains errors (are any obligatory elements missing?)

Hi all,
i get this struggling error message when i try to start my work flow (WS10001004) out of the web ui from CRM 2007. I try to start this work flow via an action which is manually scheduled.
I already set the work flow and the task TS10008150 as "General Task".
Is there a possibility of debugging the work flow? Or how is it possible to get more details for this error message?
Thanks for hints!
Regards,
Christian

Hi venu,
I checked the slg1 which is empty or what did you mean with "work flow log"?
Which binding should I check exactly?
The note that was mentioned didn't solve my problem. I have a CRM 2007 System.
Are there any more possibilities to trace / debug a work flow besides the the slg1 and the swel?
Thanks for your answers!
Regards
Christian

Sending Idocs to R/3 Error when Business Service with a party is configured

Hi All,
I'm facing some issue when posting idocs (FINSTA) back to R/3 when Business Service with a party is configured in my Integration Directory. However, I do not have this problem, if the
Business System without Party is configured. It seems that 'adapter specific' setting doesn't
seem to work when you have a party.
I have read the same problem faced by other SDN members as well, some suggested to have the latest patch to solve the problem. FYI, I'm using latest patch SP 15, but the problem still exist. The error that I have in the sxmb_moni is "Unable to convert sender XI party http://sap.com/xi/XI / XIParty / GABXI100 to an IDoc partner".
Please assist. Thanks.

Hi Arun,
Thanks for reply.
What do you mean by XI Party must map to a party in the R3 in the partner profile?
For example, If my Party Name in Integration Directory is ABC01, I should create a partner profile of ABC01 in my R3? How if I have business service under the Party ABC001, what should I configure in my R3?
Currently My Partner Profile in R3 is type 'B' - Bank.
Thanks for helps.

Send Alerts(e-mail) for errors in SXMB_MONI(message mapping exceptions)

Good afternoon !
        I´m configuring SAP Netweaver PI 7.0(SP13) to use Alert Framework to send Alerts when errors occurs in the interfaces processing.
        I just achieved configure to send alerts when errors ocurrs in the Adapter Framework but, I can´t configure correctly to send alerts when errors ocurred only in SXMB_MONI(for example, message mapping exception in asyncronous interface).
        I just followed the instructions at Michal Krawczyk
weblog(/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step) and, initially, this was not sufficient to start to send alert when errors occurs only on SXMB_MONI, so, I researched and found some configurations to do in CCMS(started from here: http://help.sap.com/saphelp_nw70/helpdata/en/e3/bf3b7a8ccb8040b638ff732c551aeb/content.htm), jobs to start events collectors, etc, and after this, I could see a mail for an message mapping exception. BUT, this message, sent from CCMS to ALM, doesn´t carry out all the message parameters, like message Id, sender(service, interface), receiver(service, interface), that is very important to help to find the message with errors to be solved.
        There is somebody here that already done the Alert configuration to send messages for errors found only in SXMB_MONI(Monitor for processed XML Messages) ?
        There is a better way to achieve this ?
        Thank you for your attention,
        Wilson Rodrigo dos Santos
        SAP Netweaver XI/PI Consultant

Hi
Go through these links and follow it.
ALERTS CONFIG AND STUFF
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
XI: Alerts - Step by step
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
http://help.sap.com/saphelp_nw04s/helpdata/en/d0/d4b54020c6792ae10000000a155106/frameset.htm
Triggering by Calling a Function Module Directly.
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
Alerts with variables from the messages payload (XI) u2013 UPDATED
/people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
Simple Steps to Get Descriptive Alerts from BPM in XI
/people/community.user/blog/2006/10/16/simple-steps-to-get-descriptive-alerts-from-bpm-in-xi
Triggering XI Alerts from a User Defined Function
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
Throwing Smart Exceptions in XI Graphical Mapping
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
/people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/sravya.talanki2/blog/2006/11/22/error-handling-framework-xiout-of-the-box-episode-1
/people/ginger.gatling/blog/2005/06/16/integrating-alerts-into-uwl--its-no-problem
/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
/people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2
/people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1
http://help.sap.com/saphelp_nw2004s/helpdata/en/56/d5b54020c6792ae10000000a155106/content.ht
http://help.sap.com/saphelp_nw04/helpdata/en/2c/abb2e7ff6311d194c000a0c93033f7/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
check this links.
https://www.sdn.sap.com/irj/sdn/forums
Trouble shooting Alert configuration:
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Alert Inbox
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Alert Notification Step-by-Step
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Defining Alert Classifications
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Triggering Alerts
http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
Setting up alerts
Setting up alerts in RZ20
Alert Management
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e04141e8-0f11-2a10-adaa-9d97b062c2df
Alert Notification
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90f449a8-a6db-2910-a386-d2b5999f5751
/people/matt.kangas/blog/2006/06/27/personalized-alert-delivery
Thanks
Saiyog

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

Error during sending IDoc from XI to R/3

Hi,
I get following error (transaction: sxmb_moni), when I try to send a IDoc from XI to R/3.
Error: Transaction IDX1: Port SAPI14_921, client , RFC destination contain errors.
When I go to transaction sm 59 and start this rfc-destination so it works fine.
Can anybody help me please?
Thanks.
Regards
Stefan

Hi,
I dont now how you pushed the IDOC form R/3 to XI..
Follow this particular way ....
Go to WE19 and execute the IDOC which you want to send and clicl the tab startoutboundprocessing....
then it hits the XI after couple of minutes and then
Go to the XI in that IDX5 where you can see the IDOC messages....
Amaresh

Error : No authorization to send IDocs with message type MATMAS

Hi All,
My scenario is FILE-XI-IDOC.
I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
Do I need to give any authorizations on XI side or on R/3 side?
If so, what is the authorization required?
I could not find the note :837595.

You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
Solution
In transaction PFCG, extend the role of the logon user by adding the following authorizations:
Authorization object S_RFC
 Field name RFC_TYPE value FUGR
 Field name RFC_NAME value EDIMEXT, SDTX
 Field name ACTVT value 16
Authorization object S_IDOCDEFT
 Field name ACTVT value 03
 Field name EDI_CIM value ' '
 Field name EDI_DOC value TXTRAW01
 Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
 Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
 Field name ACTVT value 03
 Field name DICBERCLS value
from the note mentioned above.
Regards
Bhavesh

Getting error code 37 while sending IDOC via WE19

Hello experts,
I am facing a very unlikely error which is preventing me from testing my scenario.
I dont have XI quality server and hence I am using my development server as both dev and quality. Hence I need to connect both dev and quality SAP R/3 system to my XI dev system. While I have done all the configurations in my XI and both SAP R/3 systems, its giving me error when i am trying to send IDOC from quality system.
In quality R/3 i have done the following:
1) Created RFC for my XI dev server
2) Created port for this RFC
3) Created partner profile adding all required IDOCS in the outbound parameters
4) Created distribution channel for all the idocs
In XI dev system i have done the following:
1) Created RFC for both dev and quality of R/3
2) Created port for both the RFCs
3) Maintained the IDOC metadata for both the ports
Now when I am pusing IDOC via dev of r/3 (we19) is working fine but when I am doing the same from quality of r/3 its giving me status code of idoc as 37 that says "An error was identified in the control record while adding an IDoc. The sender port SAPQTY_510 is invalid."
But I have created this sender port SAPQTY_510 in my XI dev system and have also maintained the idoc metadata. I dont know why this error is coming.
Can anyone please point out what mistake i have done or if i missed sometig as I am trying to connect 2 r/3 systems to one XI system.
Its really urgent hence your help will be highly apreciated.
Thanks,
Yash

hi yash,
where you created SAPQTY_510 ,it should be created in R/3 Quality RFC destinations.
In XI DEV create port like SAPxxx WHERE xxx is SID of quality system.
actually we are getting confused.
i guess you used same name SAPQTY_510 in quality R/3 and XI DEV .
In error it says sender port SAPQTY_510 is invalid mean port of Source not XI DEV(receiver).
just try to use some other name say SAPXXX_QUA and confirm the error.
when IDOC is sent to XI DEV ,port of XIDEV SAPQTY_510 has nothing to play any role .
just check whether rfc destination of sender port (QUALITY R/3)you used is of type 3.
so please check at which port error is coming.
Thanks & Regards,
Rama Krishna
Edited by: rama krishna talluri on Mar 5, 2008 10:02 AM

IDOC to FTP File - Error : SAP:Stack No receiver agreement found for send

Hello Friends,
I need to configure a senario Idoc to FTP File, Í did required settings in R3 and in PI... , did mapping and configuratino in PI... and when I send my idoc I got error msg in monitor
<SAP:Stack>No receiver agreement found for sender ,BMG_ASN_File_Component to receiver ,GTN_224,http://adis-bmg.de/asn,SI_BMG_ASN</SAP:Stack>
I search the fourm but did not got my answer, me just a bit confused...
In my senario I have having followings:
1. Bussiness System ( RFT : sender R3 system). ( I have define a party and make a connection under Idoc Partner )
2. Bussiness Component ( ZTEST_COMP as on Reciever side is File Server, so I define the reciver as bussiness component )
3. Communicatin Channel
 File with protocol FTP having communicatin component as my Bussiness Component ( reciver ). there I defied the required info for FTP
4. Reciever Determination
 Sender:
 - RFT
 - Idoc-Interface
 - urn:sap-com:document:sap:idoc:messages
 Reciever
 communication party = space
 communicatin component = ZTEST_COMP
 Configure Reciever:
 There I again define the communication component as ( ZTEST_COMP)
5. Interface Determination
 -RFT
 - Idoc-Interface
 - urn:sap-com:document:sap:idoc:messages
 Reviever:
 ZTEST_COMP
and define the mapping which I did in design ( although I have seen some threads where mentioned we dont need maaping in this case ) ?
6. Reciver agrement
sender:
- RFT
Reviver:
- ZTEST_COMP
- SI interface ( SI_BMG_ASN )
- http://test-etc.de/asn
and included my CC for file .....
Now when I send Idoc I got error msg that Reciver is not found : am I dong something wrong ? do I have to defien a bussiness system instead of Bussiness Component ?
Pls suggest...

( I have define a party and make a connection under Idoc Partner
Do you really need a party in your communication? Should it not be a partly-less communication.
In the receiver agreement ensure that you have included the inbound message interface.
communication party = space
No need to give any space.
In the Interface Determination i hope that you have included the receiver meessage interface and then the corresponding Interface Mapping.
If still not works then make some dummy changes and again activate....correspondingly check the cache status of the ID-objects
Regards,
Abhishek.

File-XI-IDOC : error in sxmb_moni because of empty idoc

Hi !
I'm converting a CSV file to IDOC segments (CREMAS04).
XI uses a lookup table to convert CSV records to IDOC segments. It is normal that some records could not be converted. When I process a CSV file that has ALL non-convertable records, I get an error in sxmb_moni :
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID 99889D40A4D811DBAD4A0017A4510466: Tag found instead of tag IDOC BEGIN=</SAP:P1>
And the final payload is:
<?xml version="1.0" encoding="UTF-8" ?>
<CREMAS04 />
In the integration repository, the occurance of the complex type CREMAS04 is "1..1", I modified the xsd to minOccurs=0 , maxOccurs=1 , and imported it, but it keeps showing me "1..1"...
How do I deal with these case ?? I don't want error red flags in monitor because of empty idocs...
Thanks.

Hi Bhavesh !
Thanks !
The problem is that because of mapping rules, the value of my target fields is SUPPRESS, not "empty".
For example, I have a file with this records:
A
A
B
A
"B" records should fill an IDOC segment, "A" not.
If I receive a file with only "A" records, for example 48 "A" records...then the IDOC segment, now, is receiving 48 SUPPRESS values...then the mapWithDefault doesn't work because they are SUPPRESS and not EMPTY.
Any ideas?
Thanks,
Matias.

Error in Sending IDoc to XI

Hi Gurus,
We are not being able to send Idocs from one of our Back-end SAP system. The Idoc status in we05 is successful but it doesn't reach XI. So we checked in SM58 in the Back-end R/3 system and there it shows the error:
No Service For System SAP*** , Client *** in Integration Directory
We tried almost every possible setup
-The System is defined in SLD and has the logical system name.
-The Adapter Specific Identifiers are correct for the corresponding business system in ID
-The RFC destination in R/3 system is defined.
- Read through other similar threads in SDN about the similar problem.
Do anyone have a more definite solution for this particular problem? The other R/3 systems are connected to XI system and all IDocs from those systems are arriving at XI.
Waiting for your valuable advices!
Regards,
Suddha

Hi All,
We had eventually found the solution to this problem we were facing in sending IDoc, though I couldn't manage to update the thread with the solution. I think this would be a very helpful information for those who face similar problems.
Let me describe the scenario first briefly,
We are sending an IDoc (Idoc extension), from SAP system to XI and then send the XML payload as mail attachment to the receiver via receiver mail adapter. Since this is a cross company transaction, hence we have configured the scenario as a B2B in ID, which means we use Parties for both the sender and receiver.
Now in the ID we had done all necessary configurations and used parties and services under Party. For the sender SAP system we assigned a Business System to Sender Partner, configured the Party Alternative Identifiers correctly. The ports were created in IDX1.
On the other hand the SAP system was also configured successfully - including Partner Profile, Distribution List, RFC destinations and ports.
In SLD we created Business System for the SAP system and in ID the Business System under party had the correct logical system name as Adapter Specific Identifiers.
But after all these, the IDoc was not arriving at XI, though in R/3 the status of the IDoc was 03 in we02. When we checked in sm58 in R/3, it showed us the error message that "No Service For System SAP*** , Client *** in Integration Directory".
The cause to this problem was:
We created (assigned from SLD) Business System only under Party (Sender), as this was a B2B scenario, and didn't create (assign) a Business System without Party, as we didn't need one at all in the scenario configuration. And this the reason behind this error. When an Idoc arrives at XI, before the Inbound IDoc adapter converts the IDoc to IDoc XML using IDoc metadata............it checks in Configuarion to see if any Service without Party (Busniess System) is defined for the Sender SAP System and Client (The SNDPOR and MANDT field values from IDoc Control header are taken as the SAP SID and Client). If it finds one it accepts the IDoc and starts the Normalization (Sender Party, Service......in the message header) and IDoc to XML conversion. If it cannot find an Service without Party in ID for sender system, it rejects the Idoc with the error message that we saw in sm58 in backend R/3 system.
In this step the Service under Party doesn't help, because at this point the Inbound IDoc adapter can not deterimine the sender party.
Hence for sending an IDoc from an SAP system to XI, we need to have an Service Without Party in ID, whether or not we require it in our actual Scenario Configuration, which is ofcourse not a case for the Reverse Scenario, ie Sending an IDoc into SAP system from XI.
This is the similar with BC adapter as well. I was already aware about this behaviour of BC adapter from my past experience and this actually helped to troubleshoot this IDoc adapter problem.
This was ofcourse a useful and new learning for me and hope would be helpful to others as well. Let me know if anyone has any doubts on this.
Regards,
Suddha
Edited by: Suddhasatta Guha on Aug 28, 2008 1:03 PM

Idoc- can we sent already sended idoc if status is showing error message

hi
Idoc- can we sent already sended idoc if status is showing error message
without making any changes.
Thanks in advance.

Hi raja,
IN BD87.
give the idoc number,its status,messagetype and partner system and resend it.
Regards,
nagaraj

Error in sending Idoc :: Urgent

HI
we are trying to send Idoc DELINS and ORDERS to SUS system. when sending the idoc the following error occurs in SUS
StandaredMessageFault
An error occured within XI interface: An exception with the type CX_GDT_CONVERSION occured but was neithered handled locally nor declared in a RAISING clause Program: SAPLBBP_BD_MAPPING_SAPXML1; Include : ; Line
How ever the same works fine in Dev and QAS servers
Regards,
Anand

Hi
Please provide SRM-SUS and XI Version details.
Please go through the SAP OSS Notes, which will help ->
Note 782755 - Control indicator is not transferred from MM to SUS
Related Notes
Note 1062864 - Control indicator is not transferred from MM to SUS
Note 313925 - Example exit for EDI outbound processing (e.g. purchase order
Other OSS Notes ->
Note 885825 XML inbound: Dump in QuoteItemReferenceVersionID
Note 825169 XML: Bid currency in bid invitation
Note 819953 SRM 4.0 of SAP XML output of partner address data
Note 723680 Corrections in the mapping of SAP XML messages
Note 723594 - SRM 4.0 XML confirmation mapping error
Do let me know.
Regards
- Atul

Error in SXMB_MONI as"Copy Sender from Payload: Sender Is Missing in Payloa

Hi Folks,
I am working on file to IDOC scenario. If I am testing in ESR and ID my interface is working fine. But when I am testing end to end I am getting below error. Please find the below error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Copy Sender from Payload: Sender Is Missing in Payload</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: Copy Sender from Payload: Sender Is Missing in Payload</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can u ppl please suggest me how to resolve this error.Ur help is highly appreciated.
Thanks,
Swathi

You need to have a S-userid for that....check with senior members within your company....they would be having this S-userid
Some portion from the note:
You are using the Exchange Infrastructure and you use the IDoc adapter to send IDocs. A setting in the IDoc channel
defines that the IDoc sender agreement is to be determined from the payload. The payload is stored in the XI message in the
IDoc tunnel format. If the message has been created, for example, using a Business Process Engine (BPE) process, the IDoc
inbound property may no longer be available in the XI message. This results in the error described above.
TIll you get access to the SAP Note:
In mapping enable the EDI_DC40 segment in your IDOC...fill SEGMENT, SNDPOR, SNDPRT, SNDPRN ....map them as constant
then in IDOC channel check take Apply Control record from payload (or take sender from payload)
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 24, 2010 4:51 PM

Sending IDOC from R/3 to MII error

Hi,
We are trying to send IDOC from R/3 4.7 to MII 12.1 (SP8 patch 9 on NW CE 7.11).
We followed the guide below:
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3861e693-0e01-0010-e791-9b44d2693e6c
Connection of message listener to R/3 works fine.
RFC connection test from R/3 to message listener was successful.
But when we try to do model distribution we get this error " - Communication error occured. Server repository could not create function template for 'MODEL_VIEW_REPLICATE'.
Maybe someone encountered this error and can help to resolve it.
Thanks in advance.

Hi Michael,
What do you mean by "manually registered the ProgID"? The message listener configuration property is as below:
ProgramID: MII_IDOC_CONNECT_5
MaxReaderThreadCount: 1
SAPClient: 800
UserName: GAOMX
Password: xxxxxxxx
Language: EN
ServerName: blade01a.memc.com
PortNumber: 00
BindingKey: XMIIIDOC
And also, following is error message found from LOG VIEWER of the MII server:
here is one
Message: not supported FunctionModule MODEL_VIEW_REPLICATE for IDocActivationSpec
Date: 2011-07-21
Time: 15:30:18:060
Category: /System/Server/Connector/Rfc
Location: com.sap.mw.jco.jra
Application: sap.com/sapjra~xMIIIDOC05
Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
Data Source: j2ee/cluster/server0/log/system/server_00.log
and another one
Message: Server repository could not create function template for 'MODEL_VIEW_REPLICATE' caused by: java.lang.RuntimeException: not supported FunctionModule MODEL_VIEW_REPLICATE used with IDocActivationSpec registered for MII_IDOC_CONNECT_5 on system blade04a_MIT_00
Date: 2011-07-21
Time: 15:30:18:061
Category: /System/Server/Connector/Rfc
Location: com.sap.conn.jco
Application: sap.com/sapjra~xMIIIDOC05
Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
Data Source: j2ee/cluster/server0/log/system/server_00.log
Thanks,
Mike

Sending IDOCs to R/3: Error in SXMB_MONI: Obligatory element missing

Similar Messages

Maybe you are looking for