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.

Similar Messages

File to Idoc with error in trfc

Hello,
I have a scenario like
File -> XI -> (idoc) R3
The scenario works fine but yesterday I had a problem with the user in the rfc destination(pwd wrong) which is used for the idoc-adapter. In the sxmb_Moni and the RWB the msg. got an success flag/info but it was not delivered to the r3 because the rfc-destintion could not work.
I know that the idoc-adapter is not part of the adapter-engine and my understanding was that the adapter send his status back to the integration engine. But in this cause I got no feedback from the adapter. I think this is not Ok or I am wrong ?
Regards Jami

Hi Jami,
The reason is simple.....the message is sent from the integration server to the adapter engine which was susessful.but what went wrong is the rfc destination being wrong in the receiver adapter which is not known to the integration server. So in simple words, if things work fine in your integration server then it will not throw an error in your sxmb_moni. So had there been a problem between the message transfer from the integration engine to the adapter engine then it would have surely given you an error in your sxmb_moni(for example you specify some wrong parameters while configuring your receiver IDOC adapter).
But in this case since we dont have an IDOC adapter in the component monitoring (it has adapters which are in the JAVA stack only but IDOC adapter is in the ABAP stack)we can see the error in SM58 only.
I hope this answers your question fully. If any other doubts regarding the same pls do ask me.
Regards,
Abhy
Message was edited by: Abhy Thomas

Runtime Error: How to Reprocess File-XI-IDoc scenario

Hi All,
I'm working a file adapter to XI to IDoc scenario. My XI message has about 2,000 records in it and one of those records contains an error (due to an invalid character in a description). My question is in a production environment would it be somehow possible for me to reprocess this erred message and post the remaining 1,999 records that do not have an invalid character? What are my options to progress?

Thanks Bhavesh,
Not sure what additional details you need but I'll give it a go. I've got an input file that contains lets say 100,000 rows of data and each row is a separate record. I use sender file adapter using file content conversion with fixed length definition. I send that through a simple mapping program that will generate 100,000 IDocs. I'll get 50 XI messages each containing 2,000 records (recordsets per message)
Because of an invalid character in the source file (an "escape" character) in SXMB_MONI I get a red flag. The error message is essentially "com.sap.engine.lib.xml.parser.ParserException: Invalid char #0x1b".
Since the XI message errors none of the IDocs for the 2,000 records in that message gets created even though 1,999 of them are OK.
So my question is basically is there a way for me to restart this message via SXMB_MONI (or another way) so the other 1,999 records will process OK leaving me with the error to deal with later?
Thanks again!

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

Error in file to idoc scenerio

hi
in file to idoc scenario
i got error in sxmb_moni
in status it is showing recording,
in Q.status it is showing stop symbol.
waiting for suggestions.

Hi Sandeep,
Have a look at queue problms here
/people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment
Some additional help
Q.Status is "Queue stopped"
queue status is stopped
Regards,
Prateek

File-to-Idoc error (using business sender service)

Hello,
My scenario is Flat file to IDoc. I am using a business service as my sender system. I did put in a logical system name in the business service and I have added the logical system in SALE.
The error I am getting is <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>MSGGUID 526719BA7E874E3906EEF45B43806D5C: Tag CULL_GR_RECORD found instead of tag IDOC BEGIN=</SAP:P1>
This is confusing to me because the CULL_GR_RECORD is the name of my data record of the file that is converted into an idoc within XI.
Can someone please help me with this? I would really appreciate it. I need to solve this tonight.
Thank you.

Hi,
>><i> I am using a business service as my sender system.</i>
This is fine as ur sender is file.
I suggest deleting the matadata in IDX2 and then rerun the entire interface.
Make sure ur IDoc is imported properly to the IR. If yes, test ur mapping locally once.
Regards,
Divija.

File to IDOC scenario-no messages in SXMB_MONI

Hi all,
   I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
I am doing a File to IDOC scenario through XI mapping.
I am not getting any messages in SXMB_MONI.
When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
Please help.
My scenario goes like this:
Sender : Business service(Some file location)
Used File adapter for sender communication channnel.
Receiver : Business system(SAP R/3)
Used IDOC Adapter for receiver communication channel.
One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
An inbound partner profile could not be found with the following key:
/LSDEMO/LS//DEBMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST    test flag
I already manitained following data and there is one record in EDP21.
SNDPRN = LSDEMO
SNDPRT = LS
SNDPFC = LS
MESTYP   = DEBMAS
MESCOD = space
MESFCT = space
TEST = space
EVCODE   = DEBM
SYNCHK = X
METHOD = space
USRTYP = space
USRLNG = space
INMOD = space
DCART = space
And please let me know whether I have to maintain outbound parameters also for my partner in XI system.I didn't see any difference even I maintained it.
And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
Edited by: Jaya on Feb 26, 2010 10:17 AM
Edited by: Jaya on Feb 26, 2010 10:27 AM

In file to idoc....EXCEPTION_DURING_EXECUTE Error

Hi XI Friends..
in my xml to idoc..scenario..
source datatype:
DT_Units
id
date
value
target idoc : IMEASR.IMEASR01
i did mapping between these
id----
>E1MEASR-POINT
date----
>E1MEASR-IDATE
value----
>E1MEASR-READC
and i assigned constants for readr,itime,mdtext of target idoc.
MT_Units------>IMEASR-IDOC
i tested in message mapping..and i cpoied the source from message mapping and given as source xml
<ns0:MT_Units xmlns:ns0="http://aaaa.com/xi/PROCESS/PPE/ERP_MES">
   <id>70013</id>
   <date>20060101</date>
   <value>3333</value>
</ns0:MT_WearUnits>
static test of interface mapping also Ok.
in ID, TestConfiguration i given source service and source interface and target service and the payload as source xml file and its a success.
the file is picking from source but it showing EXCEPTION_DURING_EXCECUTE OF MAPPING Catagory as error.
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_WearUnits_To_SAP_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
<SAP:P4></SAP:P4>
<SAP:AdditionalText></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage>
<SAP:Stack>During the application mapping com/sap/xi/tf/_MM_WearUnits_To_SAP_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and the payload is look like this..
Ã¯Â»Â¿<ns0:MT_Units xmlns:ns0="http://aaaaa.com/xi/PROCESS/PPE/ERP_MES">
   <id>70013</id>
   <date>20060101</date>
   <value>3333</value>
</ns0:MT_WearUnits>
and in file adaptermonitering ..in message content..
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'http://...
ï»¿<ns0:MT_Units xmlns:ns0="http://aaaaa.com/xi/PROCESS/PPE/ERP_MES">
^
please guide me..
regards
ram

Hi friends...
thanx for your quick responses..
As you suggested..
i put source xml as
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Units xmlns:ns0="http://aaaa.com/xi/PROCESS/PPE/ERP_MES">
   <id>70013</id>
   <date>20060101</date>
   <value>3333</value>
</ns0:MT_Units>
and i am getting same error in SXMB_MONI.
but payload as
Invalid at the top level of the document. Error processing resource 'file:///D:/Documents and Settings/ram/Local Se...
ï»¿<?xml version="1.0" encoding="UTF-8"?>
^
and in adaptermonitering ..file is picking and it showing the message content as
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'http://...
ï»¿<?xml version="1.0" encoding="UTF-8"?>
^
please help me...
regards
ram

File to IDOC scenario error...

Hi all,
we hhave created an File to Idoc scenario .
we are getting the following error in SXMB_MONI t-code.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BUS_SENDER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can any one plz say wat this error might be..
TIA
Regards,
Raj

Hi,
The problem occurs when sender and receiver business system or business service does not have a logical system name.
ID - Integration Directory
Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
If business system type = Third-Party, then add the logical system in business system level and Save.
If the business service does not have the logical system name in ID, it needs to be configured as follows.
Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
Apply and activate.
hope this will help you.
regards
Aashish Sinha
PS : reward points if helpful

No messsage in SXMB_MONI, although file has been picked up in file to idoc

Hi,
i m working on a file to idoc scenario using MATMAS.MATMAS02, once i got the scenario executed with error status 51 ,
"Messages have been issued: number 0000000000198012"
the datas to be posted were MATNR ,MAKTX,MBRSH , etc , in this MATNR is self generating and I by mistake issued a no to it for testing purpose and the above error came.
again when i tried to test the scenario without assigning any no to MATNR , I find no messsage in SXMB_MONI for this particular execution although file has been picked up from the source directory and it is also not found in the receiver R/3 system using we05 .
Pl help how to rectify the error and find out where the error has again occured and why .
ans will be rewrded
rgds
mojib

hi
go to SXMB_ADM-->manage queues. here desregister, register and active ALL the queues again.
see in SM58 if you have any error.
also in SXMB_ADM go to integration engine configuration and check you have this variabbles
RUNTIME--LOGGING--
0
RUNTIME--LOGGING_SYNC--
0
RUNTIME--TRACE_LEVEL--
3
Rgds
Rodrigo

File to idoc mapping error

Hi,
I am mapping a flat file to idoc in xi. If I execute the test data it works fine. But in actual run, it gave me the following mapping error:
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_MT_APPayment_to_FIDCCP02_: Runt
imeException in Message-Mapping transformatio~
Exception of class CX_XMS_SYSERR_MAPPING
Is it due to some mapping error or some basis config issue?
Thanks,
Jassi

Hi Jassi,
This may be a mapping issue, try this:
a)in interface mapping see if grids are formed at source and target after executing the test option,
b)also take the xml of the idoc from sxmb_moni , copy it and paste it at the source of the mapping ( use the src tab now) and execute the mapping, is your file structute formed?
Check the following link:
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Amaresh

File to idoc - IDX5 Error

Hi,
I am doing file to idoc scenario. I have done all required configuration in IR and ID. This Scenario is now executing properly and in SXMB_Moni it is also showing new generated IDOC number.
But when I tried to locate same IDOC in R/3 system i am not able to locate it. In IDX5 tcode is showing error msg like "No authorization to send IDocs with message type ZTESTMSG".
Please guide me on this.
Thanks,
Sunil

Hi Sunil,
Please can you check the RFC in IDX1 (RFC destination given in PORT)which is used for sending the IDOC.
Does it have all the authorizations.
Also you can try this using xiappluser in the RFC destination.
Regards
Vijaya

Error:IDOC_ADAPTER" ATTRIBUTE_INV_SND_PARTY : File to IDOC scenario .

Dear XI experts ,
Issue : Error to a new implementated SAP ERP SYSTEM . File to IDOC Scenario
Business Scenario : Exchange Rates from Thomas REuters (XML) - > XI-> SAP 1 , SAP 2 ERP Systems ( 2 diff SAP ERP systems)
SAP 2 is a new system set up for a new plant of our Organization.
The Excahnge rate is gettiong updated by IDOC: EXCHANGERATE.EXCHANGE_RATE01 in two SAP Systems
Each one is configured with diffrent IDOC receiver .
The Error is : for the SAP 2 system . The MEssage gets branched and one message is successfully sent to SAP1 , and turns an error : in SXMB_MONI for SAP2 system
I had been thropugh few blogs have performed the below steps:
-IDOC metadata : IDX2 have configured in XI
-checked the port of EGP , Partner Profile in SAP 2 ERP system
-Checked IDX1 , IDX2 of SAPEGP in XI .
-Refreshed business system .
-Tried to send the xml data from the start point through File Zilla(FTP)
Could somehow help as this is Production issue ans this is affecting the business.
Error from SXMB_MONI:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_PARTY</SAP:Code>
<SAP:P1>http://sap.com/xi/XI</SAP:P1>
<SAP:P2>XIParty</SAP:P2>
<SAP:P3>Reuters</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender XI party http://sap.com/xi/XI / XIParty / Reuters to an IDoc partner</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Reuters : is the Sender Party of Exchange Rates. I have seen in blogs to craete agency / schema , but since thsi scenario is 2 seperate SAP ERP systems , my question is do i need to create agency , schema for sender party .
Appreciate your Input
Thank you,
Vara
Edited by: Varalakshmi SB on Oct 26, 2011 12:14 PM
Edited by: Varalakshmi SB on Oct 26, 2011 12:16 PM

agency and scheme are used when your doing B2B scenarios.

Java heap space error occured during message mapping of FILE to IDOC

hello Friends,
I am trying to do the message mapping for File to Idoc scenario.
Idoc which I am using is HRMD_A.HRMD_A06 and infotype which I want to update is 14. I am trying to map the message type which I hav created for infotype 14 with the IDOC
Its very simple scenerio but every time I try to save the mapping before activating it I get an error:
Java heap space
Internal problem occurred (INTERNAL_PROBLEM)
Java heap space.
I am not able to figure out what possibly is the problem wheather its from my end or the BASIS end.
Kindly help.
Regards,
Lokesh

As the server probably survives (you restart your Integration Builder and can probably connect immediately), the problem will be on your side (client). Did you add one or more large xml-test-instances to the mapping ? If yes, delete them, because they lower the performance and can make problems. If not, then this is a strange problem. Even if the Idoc structure is complex, the mapping object itself cannot be that large.Is this problem only with this one mapping ?
CSY
Edited by: Christian Sy on Mar 9, 2010 6:26 AM

ATTRIBUTE_IDOC_METADEATA Error: File to IDOC Java Mapping

I have done a Java Mapping from File to Idoc and I get the following error in sxmb_moni:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>I::000</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Fehler: I::000</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The Idoc structure that I generate in my mapping makes no fullfil of the IDOC tags.
For example:
<IDOC BEGIN="1">
               <EDI_DC40 SEGMENT="1">
                    <TABNAM/>
                    <MANDT/>
                    <DOCNUM/>
                    <DOCREL/>
                    <STATUS/>
                    <DIRECT/>
                    <OUTMOD/>
                    <EXPRSS/>
                    <TEST/>
                    <IDCOTYP/>
                    <CIMTYP/>
                    <MESTYP/>
                    <MESCOD/>
                    <MESFCT/>
                    <STD/>
                    <STDVRS/>
                    <STDMES/>
                    <SNDPOR/>
                    <SNDPRT/>
                    <SNDPFC/>
                    <SNDPRN/>
                    <SNDSAD/>
                    <SNDLAD/>
                    <RCVPOR/>
                    <RCVPRT/>
                    <RCVPFC/>
                    <RCVPRN/>
                    <RCVSAD/>
                    <RCVLAD/>
                    <CREDAT/>
                    <CRETIM/>
                    <REFINT/>
                    <REFGRP/>
                    <REFMES/>
                    <ARCKEY/>
                    <SERIAL/>
               </EDI_DC40>
Should I complete these values in my mapping program?
Which values should I complete?
Thank You.

Antonio,
you can ignore whole EDIDC Segement make disabled in our mapping still it works . but the problem is not with this is our meta data chekc in IDX2 t/c code of XI box.
      it has some problem the strcuture you generate and R/3 accepts are not same their is mismatch in structure
Regards
Sreeram.G.Reddy
Message was edited by:
        Sreeram Reddy

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

Similar Messages

Maybe you are looking for