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

Similar Messages

File to IDOC scenario : Error with mapping due to Context handling

Hi Experts.
I have a file to IDOC scenario which need your advice.
Source File structure as follows:
Control_Header <1:1>
Invoice_Header <1:unbounded)
Invoice_Line <1:unbounded)
Trailer <1:1>
Payload as follows capture from SXMB_MONI
- <Control_Header>
 <Key>999</Key>
 <TransactionID>RCTV</TransactionID>
</Control_Header>
- <Invoice_Header>
 <Key>000</Key>
 <BusinessUnit>HDB05</BusinessUnit>
 <InvoiceNo>64471</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>7.00000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>0.49</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>8.00000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>0.56</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Header>
 <Key>000</Key>
 <BusinessUnit>HDB21</BusinessUnit>
 <InvoiceNo>6Y0575</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>49.50000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>3.47</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Trailer>
 <Key>TRL</Key>
 <TransactionID>RCTV</TransactionID>
 <TotalFeedLine>96</TotalFeedLine>
 <HashTotalValue>212.00</HashTotalValue>
</Trailer>
</ns:MT_EINVOICE>
Mapping as follow:
 IDOC
<Control_Header> -> <Control_Header>
<Invoice_Header> --> <Header_Invoice>
<Invoice_Line> ---> removeContext --> <Line_Invoice> this is the child node of <Header_Invoice>
<Trailer> -
> <Trailer>
The result of the using the above Payload get the following result which not wht I seek
<Control_Header>
<Header_Invoice>
 <Line_Invoice>
 <Line_Invoice>
 <Line_Invoice> *** This belong to the Invoice_Line of the second <Header_Invoice> at the payload
<Header_Invoice>
 <Line_Invoice> *** THis segment is empty
<Trailer>
I required the Line_Invoice to belong to the child of the second <Header_Invoice>, I have tried using
removecontext with splitVaue and collaspeContext but to no avail.
May I know what is my mistake on the mapping of the Invoice_Line to Line_Invoice>
Rgds
FNG

Hello,
There should be something that could correlate the Invoice_Header/Key and Invoice_Line/Key. In your example, both are the same for the first and data set. If the sample looks like the one below, it is possible to sort things by correlating the Invoice_Header key and Invoice_Line key
<Invoice_Header>
<Key>000<Key>
</Invoice_Header>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Header>
<Key>001<Key>
</Invoice_Header>
<Invoice_Line>
<Key>001<Key>
</Invoice_Line>
An example mapping could look like this
For Header
Invoice_Header --> Header_Invoice
For Line
/InvoiceLine/Key --> removeContext --> splitByValue:valueChanged --> Invoice_Line
The subfields of the invoice line would also follow a similar logic, you just need to use formatByExample --> splitByValue:eachValue so that the context levels are the same.
Hope this helps,
Mark

File to idoc scenario error - not working yet :(

Hello! I'm trying to make changes in business partner record in CRM using idoc CRMXIF_PARTNER_SAVE_M01
I have an error 56 EDI: Partner profile not available.
In Control record in we02 transaction, I have right Partner number for Recipient information - logical system name like CRM has in SLD. But there is no Port.
In Sender information I have right Partner number, like my filesystem business system has in SLD and have a port SAPP1D - but I have nowhere entered it!
And one more little question. In we20 transaction am entering inbound parameters for partner:
CRMXIF_PARTNER_SAVE
CRMXIF_PARTNER_SAVE_M
1) Is this right inbound parameters for my idoc?
2) What Process code should I use ?

Hi,
in XI in IDX1 transaction, maintain a port for CRM system specifying the CRM port and the client and the RFC destination from XI to CRM system.......moreover if you are using apply control record values from payload option in reciver IDOC comm channel, then in the IDOC control record in msg mapping map the sender port to CRM port, partner number as logical system of CRM ie C2DCLNT100 and partner type as LS..........then when you will re-run your scenario, your IDOC will have CRM port also in the control record..........
in CRM system your WE20 for LS for XI should have as an inbound parameter your IDOC - which i think you have already done.........
One more thing - put everything in uppercase letters everywhere in msg mapping in control record data, in we20 setting etc.
Regards,
Rajeev Gupta

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 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-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

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

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: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.

File to IDoc scenario( Bypass)-- Error ( Segment is missing) -- urgent pls.

Hi All,
I am doing File to IDoc scenario( Bypass) for Orders05.
File is picking succesfully and not posting the idoc in the SAP..
My source file(idoc-xml) consists of all the required data to post the idoc including the segment 'E1EDK01'.
but the error it is showing is " Obligatory node 'E1EDK01' missing in the structure ORDERS05 "
Please suggest me ASAP what is going wrong .
Thanks in Advance.
Regards
Seema.

The source File is not the idoc XML. It is invalid. You might need to ask the source to change the XML or use a Mapping to do this.
This is how it should look, ( check the parts in bold),
<?xml version="1.0"?>
<ORDERS05>
<IDOC BEGIN ="1">
<EDI_DC40 SEGMENT="EDI_DC40">
<DOCNUM>1</DOCNUM>
<DIRECT>2</DIRECT>
<IDOCTYP>ORDERS05</IDOCTYP>
<CIMTYP></CIMTYP>
<MESTYP>ORDERS</MESTYP>
<SNDPOR>XXXXXXXXX</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPFC></SNDPFC>
<SNDPRN>XXXXXXXX</SNDPRN>
<RCVPOR>XXXXXX</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPFC></RCVPFC>
<RCVPRN>XXXXXXXX</RCVPRN>
<CREDAT>20070511</CREDAT>
<CRETIM>152803</CRETIM>
</EDI_DC40>
<E1EDK01 SEGMENT = "1"><BELNR>AAAAAAAAA123</BELNR>
</E1EDK01SEGMENT = "1">
<E1EDKA1 ><PARVW>EK</PARVW> <ILNNR>231654845121</ILNNR>
</E1EDKA1>
<E1EDKA1 SEGMENT = "1"><PARVW>LF</PARVW>
<NAME1>international</NAME1>
<NAME2>Delhi</NAME2>
<ILNNR>2121211545</ILNNR>
</E1EDKA1><E1EDK02 SEGMENT = "1"><QUALF>001</QUALF>
<BELNR>AAAAAAAAA123</BELNR>
</E1EDK02><E1EDK02 SEGMENT = "1"><QUALF>002</QUALF>
<BELNR>AAAAAAAAA123</BELNR>
</E1EDK02><E1EDP01><POSEX>45</POSEX>
<E1EDP19 SEGMENT = "1"><QUALF>001</QUALF>
<IDTNR>00000000002150059</IDTNR>
<KTEXT>Reddy</KTEXT>
</E1EDP19><E1EDP19>
<QUALF>003</QUALF>
<IDTNR>5484218521214</IDTNR>
</E1EDP19></E1EDP01>
</IDOC></ORDERS05>
Regards
Bhavesh
PS : You need to add SEGMENT = "1" for every segment. Please do add it if I have missed in the XML above.

Error while doing a File to IDOC scenario

Hi Experts,
I have created a File to IDOC scenario where in i have sent a file which has to pass data to ABSEN1 IDOC.I could see the IDOC reaching R/3 ,but with the status 56: "EDI: Partner profile inbound not available"
I have checked with all the configurations and couldnt find where it went wrong.
Kindly help me in this regard.
Thanks.

Hi
Check the inbound parameter and the process code.
To find Process code for IDoc use Tcode WE42.
ALE idoc trouble shooting use
Troubleshooting of ALE Process
look also this configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6bd6f69a-0701-0010-a88b-adbb6ee89b34

Error values in Idoc Control Records in File to Idoc Scenarios

Hi All,
I am posting 2 different types of Idocs in 2 different File-to-Idoc Scenarios. In many cases both these files may get picked at the same time. One is an Orders Idoc and the other one is Shipment Idoc. The Orders Idoc has a control record value in the Sender Partner Fn as 'ZC' while as for Shipment Idoc that value is not passed. The other Sender parameters are passed and are different for both these idocs. But when the files are processed, the value 'ZC' get populated for the Shipment Idoc also. When 100 files are sent with 90 orders and 10 shipments, the shipments get created with 'ZC' partner fn. This is visible in the Call Adapter Pipeline Step under the node IDocOutbound. . I have 2 different Idoc receiver adapters.Can anybody help me out here?
Thanks,
Geetha

Hey,
>'ZC' while as for Shipment Idoc that value is not passed
Check whether the Source/ Mapping populates the 'ZC' , Did you checked Apply Control record in Receiver Adapter for Shipment, What is the name you have mentioned for the in the SLD -Logical system for Sender system
Cheers
Agasthuri

Problem with Sender service in File to IDOC scenario

Hello All,
Am doing a file to IDOC scenario.
I have configured the sending system as a party and added a business component, to the BC attached the service interface and also configured the sender Communication channel(CC) as file.
On the receiving end configured the R/3 system from SLD as the business system and configured the receiver CCl. Can see the R/3 logical system in the Adapter specific identifiers at business system.
Pushing the file get an error "Unable to convert the sender service to an ALE Logical System". But choosing "Take sender from Payload" in the receiver CC is resolving the problem, however the sender partner number remains the same as what I have mapped to the control record in message mapping (which is like hard coding).
My questions are:
1. Am I doing the correct config in terms of the scenario. (like using "Take sender from Payload")
2. I tried using identifiers at the party level to convert the sending system, but nothing seems to work. But sending system remains the same as the constant from mapping.
Suggestions would be very much helpful..
--Prashanth
PS: Have gone through many blogs and posts on the forums, but may be I did not see the correct thread. Apologies if I am asking this again.

Hi Prashanth,
refer the below discussion i think it will solve your problem.
File To Idoc scenario
Thanks

File to IDOC scenario error...

Similar Messages

Maybe you are looking for