File to Idoc - Outbound Error

Hi,
I am doing File to IDOC scenario. I got error
in "Message has error status at outbound status" .. When
I opend that messeage then i got this ...
<SAP:IDOCTYP>ZIDOCIN</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>ZMTIDOCIN</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPX11</SAP:SNDPOR>
<SAP:SNDPRN>Logi_01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPA11</SAP:RCVPOR>
<SAP:RCVPRN>A11CLNT200</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
Can any one tell me what to do to solve this.
thx,
Ansar.

Hi,
There is somethig worng with your Partner Function while defining the the Partner Profile, please check it. The Partner function is optionla and see if you need it
Go thru the link,
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Thanks,
Prakash
Thanks,
Prakash

Similar Messages

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

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

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

IDoc outbound errors - mail send step in WF to send info-mail to enduser

Hello specialists
I searched quite a lot in the forums now. I found lot of info but nothing regarding my issue.
I need to send an info-mail to the end user creating purchase orders. But only if the idoc (outbound ORDERS) could not be sent (failing for some reason, i.e. if rfc connection fails). This is what I've done to achieve this:
- in WE40 I linked my WF to process code EDIO
- the WF-BATCH user has an email address assigned to it (in SU01)
- the mail sending step in my WF is configured like this:
recipient type = G (organizational object)
Expression = &_WORKITEM.CREATEDBYUSER.ID& (this contains the enduser id)
subject = Test for &WORKITEM.CREATEDBYUSER.ID&
When testing the mail can not be delivered (error SO23).
When setting recipient type to U (E-Mail address) and giving a valid e-mail address, then it works fine (SCOT, etc. is configured and mailing to external systems works). But setting the e-mail address hard coded style in the mail send step is not an option here!
It seems that the send mail step (SELFITEM.SENDTASKDESCRIPTION) always requires a valid e-mail address. Is it not able to handle SAP user id's ?
Thanks in advance for some guideance on this one.
Renaud
Edited by: Renaud Desarzens on Feb 11, 2010 3:00 PM

Hello and thanks for your help.
I was able to solve it like this:
- don't use mail send step
- instead, add new activity with a new task (SELFITEM.SENDTASKDESCRIPTION)
- in the bindings (workflow -> step) set:
B --> &TYPEID&
&_WORKITEM.CREATEDBYUSER.ID& --> &ADDRESSSTRINGS&
Seems that the mail send step doesn't allow TYPEID to be "B" because each time I tried to tweak the generated bindings that way it messed up the recipient type and expression I set before.
Regards
Renaud

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 ..error in sxmb_moni

Hi Xi Friends...
In my xml to idoc scenario...
file is picking..but in sxmb_moni it is showing as mapping error like
<b>No messages created from split mapping</b> ..
i copied the the payload from sxmb_moni and i tested in static message mapping..its converting successfully...
please guide me..
regards
ram

refer these links;
Split mapping created no messages - this has a solution, check if it can help you.
Message Split without BPM - Error

IDOC OutBound Error 29: Entry in outbound table not found?

Dear All,
        I configed the customized IDOC,and used BD64,WE20 Generate Partner Profile.the partner type is u2018LSu2019,In We20,I clicked the check button .There is no error in check.Other config also correct.
My outbound program main code is :
WA_IDOC_CONTROL_RECORD-MESTYP = 'ZMSGTYPE_WE81'.
WA_IDOC_CONTROL_RECORD-IDOCTP = 'ZIDOCTYPE_WE30'.
Receiver
WA_IDOC_CONTROL_RECORD-RCVPOR = 'A000000003'.           "Port
WA_IDOC_CONTROL_RECORD-RCVPRN = 'target100'.        "Partner number
WA_IDOC_CONTROL_RECORD-RCVPRT = 'LS'."Partner type
WA_IDOC_CONTROL_RECORD-RCVPFC = 'LS'."Partner function
Sender
wa_idoc_control_record-sndpor = 'A000000001'.           "Port
wa_idoc_control_record-sndprn = 'source500'.           "Partner number
wa_idoc_control_record-sndprt = 'LS'.             "Partner type
WA_IDOC_CONTROL_RECORD-SNDPFC = 'LS'."Partner function
DATA L_ITEM TYPE I.
LOOP AT GT_IDOC.
    L_ITEM = L_ITEM + 1.
    WA_EDIDD-SEGNAM = 'ZSEG_WE31'.
    WA_EDIDD-SEGNUM = L_ITEM.
    WA_EDIDD-SDATA = GT_IDOC.
    APPEND WA_EDIDD TO IT_EDIDD.
ENDLOOP.
CLEAR L_ITEM.
SORT IT_EDIDD BY SEGNUM.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
       EXPORTING
            MASTER_IDOC_CONTROL            = WA_IDOC_CONTROL_RECORD
          OBJ_TYPE                       = ''
          CHNUM                          = ''
       TABLES
          COMMUNICATION_IDOC_CONTROL     = IT_COMMUNICATION_IDOC_CONTROL
            MASTER_IDOC_DATA               = IT_EDIDD
       EXCEPTIONS
            ERROR_IN_IDOC_CONTROL          = 1
            ERROR_WRITING_IDOC_STATUS      = 2
            ERROR_IN_IDOC_DATA             = 3
            SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
            OTHERS                         = 5
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.

hi Sun,
The value 'X' means ABAP_TRUE, which means the outbound ALE settings for your message type are OK.
Did you check the sy-subrc value after the FM 'MASTER_IDOC_DISTRIBUTE' is called ? and if yes what is the value ?
Also did u check the IT_EDIDD table, whether is contains any values ?
If all of the above is fine then call the FM 'EDI_DOCUMENT_DEQUEUE_LATER' by passing the document number of the outbound IDoc created, this number you will from the 'communication_idoc_control' table which you need to pass to your FM MASTER_IDOC_DISTRIBUTE.
for your reference attached is code for it
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
      EXPORTING
        master_idoc_control            = wf_edidc
      TABLES
        communication_idoc_control     = int_comm_cntl
        master_idoc_data               = int_edidd
      EXCEPTIONS
        error_in_idoc_control          = 1
        error_writing_idoc_status      = 2
        error_in_idoc_data             = 3
        sending_logical_system_unknown = 4
        OTHERS                         = 5.
if sy-subrc = 0.
APPEND LINES OF lt_idoc_comm_control TO g_idoc_comm_control.
endif.
LOOP AT g_idoc_comm_control.
    CALL FUNCTION 'EDI_DOCUMENT_DEQUEUE_LATER'
      EXPORTING
        docnum = g_idoc_comm_control-docnum.
ENDLOOP.
{/code}
hope this will solve your problem
Edited by: Ashwinee on Dec 26, 2008 12:09 PM

ALE / IDOC Outbound Error Handling

Hi Experts,
I got an error in Outbound Process.
An IDOC gets the status 36 - Timed out.
Can anyone tell me how can i resolve this Error?.
Thanks in advance,
Sudhakar

Hi ,
Best option is to keep a sql trace on the outbound idoc which will tell you at which perform or functional module ,the performance is taking time to fetch .
all check with basis in terms of timed out ,they would have set a paramater for time out in terms of mins or hrs.

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

SAP to XI IDoc Outbound Error

Hi,
I am sending an IDoc from SAP R/3 to SAP XI . In WE02 IDoc showing Status as 03 (sucess) but in SM58 it showing as Error
*No service for system SAPTI2, client 030 in Integration Directory *
Any Info?
a®

Got answer from XI forum

File to IDoc scenario-CREMAS not getting posted

Hi Experts,
i am doing a file to idoc scenario in which i am giving the xml file from MDM ,consisting of Vendor Master data and posting the address and the general data into the ADRMAS and CREMAS idocs into the R/3 system.
The problem that i am facing is that the ARMAS is getting posted correctly but the CREMAS is getting posted with the red signal,status 51.It says "Not authorized to change the Vendor Centrally."
Can anyone please tell me what is the reason and the solution for this problem?
Is this a data error or XI error?
Thanks in advance,
Shweta.

Hi Shweta
Status 51, 52 means Posting error
Please check wheteher all the configuration has been done or not
SM59-rfc destination
IDX1-port
IDX2-load metadata
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
After That check the solution it is due to Authorization
File to idoc - IDX5 Error
Regards
Abhishek Mahajan
*Please reward points if helpful**

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

No suitable sender agreement error (File -- XI -- IDOC R/3)

Hi All,
I am completeing teh 'File --> XI -->IDOC to R/3' scenario.
Have manged to complete teh IR and ID config as per the various threads in SDN.
I am using FCC in the Sender File adapter (which I assume will read the file data and convert to XML data). When this channel is activated, it gives me the error 'No suitable sender agreement found'.
As per various posts in sdn, this scenaruio may not need sender agreement as XI is finally using IDOC adapter to send data to R/3.
Am I correct in assuming that ??
Could you help point any potential missing config.
For your reference:
The comm Channel used to read file data is using File adapter (marked as SENDER/NFS/FCC/Integration server)
Appreciate your feedback.
Thanks
Shirin

Hi,
chk for ALE settings....
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Step 6)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 7)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
reward points if helpful...
Prashant

File to Idoc - Outbound Error

Similar Messages

Maybe you are looking for