Error in File to Idoc

Hey guys i m doin a asynchronous file to IDoc scenario and getting the followin error in MONI
Error:IDoc XML data record:In segment attribute occured instead of SEGMENT.
i copied the payload from MONI and its workin fine in message mapping.
is there a way i can monitor IDOC adapter(i cant do it in RWB).
any idea where the error might be?
thanx
ahmad

Hey the payload i m getting is as follows
<?xml version="1.0" encoding="UTF-8" ?>
- <ns:MT_Idoc_sender xmlns:ns="http://Thoughtbyte.com">
- <Record>
- <Row>
<Name>Mark</Name>
<Address />
</Row>
</Record>
</ns:MT_Idoc_sender>
and the error is
<?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_IDOC_RUNTIME</SAP:Code>
<SAP:P1>IDoc XML data record: In segment attribute occurred instead of SEGMENT</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: IDoc XML data record: In segment attribute occurred instead of SEGMENT</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
thanx
ahmad

Similar Messages

Error in File to IDOC Scenario

Hi,
I have File to IDOC scenario.
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Despite of this error in sender channel I am receiving the message in XI.
But in XI also it throws error :
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
Any help on this ?
Thanks,
Vikas

Hello Vikas,
I am getting error in sender file channel.
"Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found "
Although I have used this parameter in content conversion 'xml.keyfieldName' (for each sub structure and defined a key field).
Check your flat file structure whether the key field you have chosen is appropriate and also recheck the FCC details whether you have assigned the value for the key field i.e. keyFieldValue.
"Unable to convert the sender service PG_TOM_CEEMEA_RU_SFA to an ALE logical system"
regarding the above error refer this
https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
Regards,
Prasanna

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

Error in File 2 Idoc

Getting following error while doing Simple File to Idoc scnerio
Leaf node with min occurence>0 and with out mapping.
please Help

Hello,
You try to send an idoc that require a filled node without filling it.
For example, the node B must to be fill :
<A><B>toto</B></A>
If you don't fill it you have an error.
Regards,
Chris

Error in File-PI-Idoc scenario

Dear All,
While working on File-PI-Idoc scenario, I am getting the error as
<?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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have checked various other posts on the same error but still I am not able to resolve this.
Please help me in resolving this error.
reg,
nj

Nishu,
Please check whether you have assigned the following roles to the particular user you are using for data communication.
Roles:
SAP_XI_IS_SERV_USER,
SAP_XI_APPL_SERV_USER
Regards,
Sugata

IDOC is posting with Errors in File to IDOC scenario

Hi,
I did the File to IDOC scenario for CREMAS . IDOC is posting with Errors .. i.e. in the status record it was showing 56- EDI: Partner profile inbound not available ..
If I manually process that IDOC in WE19 , then it was processing successfully.. and in the we19 it was showing Inbound Processing : Port Not Maintained but even though manually it was posting fine...
any ideas regarding this will be appriciated.....
Regards
Babu

Please check whether you had done the following assuming your doing File to Idoc
Settings in your Business service for the receiving system
Please specify the RFC detination, SAP System and Client of the Receiving System in the adapter specific detials.
Settings in R/3
WE20 - Add the partner profile for the particular message type cremas and process code.
Your statement
" and that same logical system name had given as Message Specific Attributes in the Sender Business Sevice parameters in I.D "
Please do mention R/3 Details in the receiver business service or system.
Thnz

How to catch Posting error in File to IDoc Scenario?

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

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

Error Records-File-To-Idoc

Hi all,
In processing of File-To-Idocs, if we get any error in particular record by the follwoing situations how XI will handle,
1) Wrong value in record.
2) Due to strcuture change happend to the particular record
3) value range is different than expected
Is the total process stops or the correct record posts and error records will not post in the system.
Regards,
venu

Hi Sravya,
What my main concern is If I'm using Message Mapping tool for mapping (value mapping/structure mapping)
Some records are might processed correctly and relavent Idocs are created some are not went fine not created any idocs In this case what happence?(Assuming each record will be an Idoc)
What I have a plan is error messages anyhow will be shown in RWB, I'll search for relavent table and send those messages to relavent person.
There might be another ways, but I'm using XI just now, I don't know how to use the Java code which u suggested to read.means where exactly i should insert this code to work on file and generates XML message and will be inout to target.
Expecting an easy solution for me.
Regards,
venu.

Error in file-ro-idoc scenario

Hi! I'm trying this scenario https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
And and have an error "Unable to convert the sender service MDM_to_CRM_BC to an ALE logical system". What maybe wrong in my scenario ?

Vishnu, I'm very sorry, but:
I've opened we02 ---> Inbound idocs ---> CRMXIF_PARTNER_SAVE_M ---> Status 56
Then I've opened my idoc and see:
Control Rec
Data records - idoc fields
Status records --> 56 --> EDI: Partner profile not available
Message no. E0332
Diagnosis
A partner profile could not be found with the following key:
/ls_p1d /LS/
This involves the key fields of the table EDPP1:
-PARNUM partner number
-PARTYP partner type
Procedure
Please check the EDI partner profiles.
What should I do now?

Catch Mapping Error in File to IDoc scenario

Configured BPM and now learning Error Handling. I know that through BPM we can handle system Errors, but I doubt whether Mapping error is a system error.
I am interested to know the classification of errors with examples, preferably listing out all types of errors.
Please provide some weblogs or explain briefly how to handle system and application errors through BPM.
Thanks,
Raja

Hi Raja,
You will need CCMS if you want to send the Alerts to external system or you want to access the ALerts from the transaction. You can capture your alerts without this also.
When you go to Alert Configuration in the Runtime Workbench you can see Create Alert Rules. These rules are pertaining to the error generated in your AF,AE or IE.
Once you have completed the whole config. The error happening in the AE, IE or AF would trigger the alert. you can see this in your Alert Inbox.
The best would be if you go through the URL I have mentioned below.
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
You have to use BPM only if you want to do an activity after the alerts are raised.
Regards
Vijaya
Message was edited by: vijaya kumari

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

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 error

i am testing File to idoc scenario..
everything went smooth in XI...51 status error at ECC.
when i went into details..it says..Fill in all required entry fields
i tried checking those ..but its fine
what should be the error

Hey
When you execute the function module in foreground,you will see errors(if any) in red color along with the field which is giving this error(with explanation).fix that error and try to post IDOC's again.
to me it looks like the configuration is not in place to receive your IDOC,you might be passing some value which is not valid for proper configuration.
Like in my case i was giving wrong ship to party,this ship to party was not configured in R/3 hence IDOC was not posted correctly.
Thanx
Aamir

Regarding error in XI File to IDoc scenario

Hi,
when i was doing file 2 idoc scenario i got this error "Unable to convert sender service to an ALE logical system". please resolve my issue as early as possible.

Uday,
Please go through these threads:
Unable to convert the sender service to an ALE logical system
How to convert Sender Party/Service to a Logical System?
Unable to convert the sender service to an ALE logical system
BR,
Alok
Edited by: Alok Sharma on Jan 31, 2008 12:39 PM

Idocs with errors added status-56 in file to idoc scenario- how to rectify

hi ,
in file to idoc scenario when i m sending the file from ftp server to IS Retail, file is successfully getting processed but the idoc is showing error ,when we see using WE05 tcode or BD87 , pl sugggest how to rectify it to make the status 53

Hi,
Have you configured the partner profile details? check these steps..
1. In the receiver system you must configure the partner profile for your sender system in WE20.
2. Add the IDoc message type to inbound parameters of the partner profile and configure the appropriate process code.
2. Fill the Logical system name for your senderservice-->Adapter Specific identifiers in ID.
<a href="/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi File-to-IDOC Scenario</a> By Venugopalarao
<a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> By Ravikumar Allampalam
Regards
San

Error in File to Idoc

Similar Messages

Maybe you are looking for