Post Idoc from SAP to Thirdparty using XI

Dear Friends,
My requirement is sending the Idoc from SAP to Thirdparty system,but Thirdparty system also receive the Idoc format only.
so IDoc to Idoc scenario but SAP to Thirdparty system it is possible or not.
please tell me how ?
Regards,
Shalini Shah

You can use SAP Business Connector(BC) to convert IDOC to IDOC-XML at the third party legacy system.
With Business Connector see the below links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://www.erpgenie.com/mysap/bus_connector.htm
WAS - Business Connector
business connector documentation
SAP Business Connector
Business connector
Will Business Connector 4.6 be affected by new Daylight savings changes
Business connector
More info on XI can be found at https://service.sap.com/xi
and webAS on http://help.sap.com/saphelp_nw04/helpdata/en/f3/e20f3adfd0a706e10000000a114084/frameset.htm
Check this also-
http://help.sap.com/saphelp_nw2004s/helpdata/en/6f/1bd5c2a85b11d6b28500508b5d5211/frameset.htm

Similar Messages

"An IdocException occurred" while posting Idocs from SAP ECC to SAP PI AEX

Hi all,
While sending Idocs from SAP ECC to SAP PI 7.4 AEX, we are experiencing this issue at SAP ECC-SM58
Only a particular Idoc type is having this issue.
Below are the checks done before posting this query:
1. Pushed other Idocs from the SAP ECC to PI and all were getting exchanged successfully.
2. Reloaded the meta data in PI for the particular Idoc type in issue.
3. Checked the RFC destinations in SAP ECC, RFC connection test is also working fine.
4. Unicode option enabled in the SAP ECC RFC destination pointing to PI-AEX
5. Restarted the inboundRA service in PI AEX.
Is there anything still missing. What could be root cause of this issue.
If anyone has encountered it before, pleases share the resolution.
Thank you
Younus

Hi Amit,
Thanks for the reply. Log viewer doesn't provide much help on the error.
The error desc says
"JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_SID, Managed_Application_Thread_58, connectionId=5-ip address|sapgw20|XI_IDOC_DEFAULT_SID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: An IDocException occurred"
regards,
Younus

Unable to send an idoc from SAP R/3 to XI

Hi,
We are trying to send Z_CREMAS_SUSMM.CREMAS03 idoc from R/3 system to XI using IDOC adapter.
We have done the following steps.
On SAP R/3 system:
1.created a RFc Destination which points to the XI system using transaction SM59
2.created a port in which we have selected this RFC Destination using tansaction WE21
3.logical system for R/3 with transacion BD54
4.In WE20 transaction,we have configured the PartnerProfile by adding the IDOC message type to the outbound Parameters of XI Logical system.
On XI Sytem:
1.Created RFC destination
2.Created a Port
3.Loaded metadata
While trying to Post IDOc from SAP R/3,it is throwing an error"External segment name E2LFA1M001 cannot be interpreted"
and "Basic type CREMAS03 does not exist" on XI side.
Can anyone please provide a solution to this?

HI Jagruthi,
Have you loaded the metadata into the XI system by using IDX2?
If it is done then try to delete once and do once again.
And also delete the IDoc from IR and reimport the IDoc and activate it once again.
Regards
Goli Sridhar

Error while pushing idocs from SAP to XI

Dear All,
For doing ALE configurations for pushing IDOC's from SAP to XI, I am following the following blog posted on SDN:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I am able to create the model view distribution successfully but when I am clicking on EDIT --> MODEL VIEW --> DISTRIBUTE (which is one of the steps mentioned in the blog), I am getting an error tht
<b>Target system XIDEV Communication error occurred
User is locked. Please notify the person responsible</b>
please tell me what is the error ie which user is locked and how should i proceed now.
Waiting for your reply.
Warm regards,
N.Jain

hi krishnamoorthy,
i hve created one RFC in my R/3 system which is pointing to Xi-DEV. So, in the RFC I have used my XI user id & password for loging and the RFC is wrking fine when I am testing tht. I have used my id "XISUPER" in that RFC and it is not locked in XI-DEV. I have not used user id "XI_APPLUSER" anywhere.
Please suggest.
Warm Regards,
N.Jain

Help Required to post IDOC from R/3 to XI

Hello,
I need help to post IDOC from R/3 to XI
My XI System --- E11 on client 001
My R/3 System -- IXS on client 812
In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 )
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS )
While Posting data from R/3
Recipient Port --- A00020
Recipient Partner No -- RECE
Recipient Partner Type --- LS
Sender Port --- SAPB6M
Sender Partner Number -- B6MTEST
Sender Partner Type --- LS
I am getting error " Could not post IDOC to R/3".
Please let me know where are my setting are incorrect
Regards

In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 ) ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS ) ( Not require in SAP XI)
chenage the PORT NAME IN R/3 it should work.

What authorization required to post idoc from XI via RFC?

Hi all,
I need to post idoc to SAP R/3 system from XI. I have done all the steps correctly. While creating RFC in XI system to connect to the R/3 system, intially I gave my R/3 username and password and tested teh connection. Everything was working fine but when I actually ran the scenario, IDOC was not getting posted in the R/3. But there was no error anywhere.
fianlly after debugging I fould it might be the issue of authorization the the R/3 user i used in the RFC. I then assigned SAP_ALL authorization to my user and posted the iodc again and it started working fine.
Can anyone please tell me what are th exact authorizations/role i need to assign to the r/3 used to use it in RFC and successfully posting the idoc? I dont want to use SAP_ALL authorization in my production environemnt.
Please help.
Regards,
Yash

Hi,
Even i had faced this problem. Whenever I tried to send IDOCs, i used to get an error in SM58, " No authorization to send IDOC of type DEBMDM".
When i got SAP_ALL it worked. However I raised a note with SAP asking for an alternative and this is the reply gave me.
You can get good information on this topic in your online help files.
The following is taken from the document "General Security Measures
(ALE)":
Use the transaction SALE to maintain the ALE configuration, to include setting up the distribution model and setting up ALE user authorizations and profiles. Note the following:
- Be restrictive when assigning the ALE authorizations.
The authorization profile B_ALE_ALL contains the following
authorization objects that are needed for ALE:
Authorizations for ALE
Authorization Description
B_ALE_CGRP ALE Customizing Distribution: Group Activities
B_ALE_LSYS ALE/EDI: Maintaining logical systems
B_ALE_MAST ALE/EDI: Distributing master data
B_ALE_MODL ALE/EDI: Maintaining customer distribution model
B_ALE_RECV ALE/EDI: Receiving IDocs via RFC
B_ALE_REDU ALE/EDI: Generating messages (ex. reduction)
S_PROGRAM ABAP: Program run checks
S_TABU_DIS Table Maintenance (using standard tools such as SM30)
Protect external users and passwords.
For example, for a non-SAP system to send IDocs to a SAP System using transactional RFC, it must also send a SAP user ID and password.
In most cases, the user and password are stored outside of the SAP System. Make sure that this information is not accessible to external systems or programs. (How you can do this is dependent on the system that you have; therefore, you need to refer to the documentation for the system where the information is stored.)
However, I feel assigining the profile S_IDOC_ALL should also be enough. Just try and see.
Regards,
Merrilly

Help needed in transferring IDoc from SAP CRM to XI

Hi All,
We are facing an issue in sending an IDoc from SAP CRM to XI system. The IDoc is triggered and the status is showing as 03 in SAP CRM system(WE05 is used) but it is not getting replicated in XI System. This is verified by logging into XI System and cross checked the records retrieved by executing the transaction IDX5. No entry is found for this IDoc.
In SM58 transaction, it is giving the status text as EDISDEF:Port SAPRIO segment defn E201CRMXIF_BILLI.
Any pointers on this issues will be very helpful. We are able to send information from XI to CRM.
The project is an upgrade one and the IDocs are developed earlier and were working fine one week back and no changes were made recently.
Thanks,
Udaya

Hi Kapil,
Thanks a lot for your help. We need to delete and recreate Metadata. This is a typical problem that is encountered during upgrade projects.
Thanks,
Udaya

Message SR 053 when i send idoc from SAp R/3 4.6C to PI 7

Hi,
I try to send idoc from SAP r/3 4.6C to PI 7. I had made ALE configuration in my sender system ( SAP 4.6C) but idocs are not sent to PI. In SM58 i have message "Name or password is incorrect (repeat logon)". Yet i'm sure that user and password are correct because if i test RFC destination using SM59 , test is OK.
Is somebody can help me ?

Hi,
In R/3 :
my RFC destination is type 3 and point to XI. The port in the partner profile point to this RFC destination. ( all seems good !).
In Xi : i created a port and i load manually idoc in idx2 to be sure that RFC destination was OK. Nothing in IDX5.
When i send idoc MATMAS using BD10 from R3 to Xi i have something very strange: first the message B1 038 "1 master IDocs set up for message type MATMAS" and just after
the XI logon screen appears !! Then message "1 communication IDoc(s) generated for message type MATMAS" and this idoc stay in SM58 with message "Name or password is incorrect (repeat logon)".
Somebody can give me requires caracteristics for XI user used in R/3 RFC destination ?

Is it possible to read Idocs from SAP R/3 System?

Is it possible to read Idocs from SAP R/3 System? Instead of the aRFC

Unless Hydra emulates ECC sending IDOCS, then you just might want to use the WSMessageListener (http://help.sap.com/saphelp_xmii120/helpdata/en/45/6a86ac88130dece10000000a11466f/frameset.htm) and configure your message processing rules accordingly.

Problem in Outbound IDOC from SAP R/3

Hi,
I am working on to send an IDOC from SAP R/3 to XI.
I configured all necessary things as follows:
1. Created for XI in sender system -- RFC dest, PORT and a partner profile with an outbound parameters and reciever port as XI port.
2. created for sender system in XI -- RFC dest, PORT(as SAP<SID>) in IDX1 and assigned an idoc type(coming from sender system) to the port.
Now I am trying to push the IDOC from sender system using Test IDOC transaction and gets success message as data is passed to port.
My problem is I am not able to see any message in SM58 of XI server.
Could anyone help me out?
Thanks In Advance.
Yaseen.

Yasseen,
you hardly see the idocs in Xi in sm58. Try sxmb_moni.
If you see anything there try sm58 on the sending R/3. There you see if you have connection problems (eg authorization in XI or missing receiver determinitions).
Hope it hellps,
helge

Problem when pushing IDOC from SAP to XI

Hi,
I am trying to push an IDOC from SAP R/3 system to XI. When I processed the IDOC using test tool(WE19), it's showing message that IDOC sent succesfully to R/3 or External system. But in SM58 Transaction it gave error message that in Trabsaction IDX1: some RFC connection error. Then I opened the Transaction IDX1 on XI server, in that IDOC Adapter configuration I gave RFC destination, Logical system name of R/3 and saved it. Now When I tried again to push IDOC from R/3 to it's not giving any error message(in SM58), but I am not able to see any thing in SXMB_MONI. Can anybody guess what's happening? And also I am using fresh newly installed XI server. DO I need to configure something else? All RFC connections are well defined and working fine.

Hi,
It is not required to create Sender Agreement for the Idoc to XI scenario. Because it is implicitly exists.
Can u check Receiver Determination created in the XI once again. And also check for RFC destinations created in the R/3.
Hope it helps ..
-Moorthy

Missing IDOCS from SAP to BODI

I have an issue of missing idocs from sap going to BODI.
Idocs are received by BODI trough adapter, but there are idocs that are missing but are successfully sent by SAP. When trying to resend the idocs it was successfully received by BODI.
We thought that it is an intermittent connection issue, so we try to send idoc from SAP while the adapter was down. The idoc was successfully sent from SAP. Then we try to start again the adapter and it was loaded after sometime.
Iu2019m now out of idea on why does the idocs went missing. Can someone help me?
Thanks in advance.

Hi Parida,
IDoc Status 03...Green Status... wills not guarantee you that IDoc reached EDI subsystem...
Run the Program RBDMOIND in SE38...
Changed on :<Date>
IDocs/Commit Work :100
Display IDoc not sent- Check the Check Box.
Now you will get list of un posted IDocs
Ramesh

Limit send of IDoc from SAP-ERP to SAP-XI or a Non-SAP

Hi guys,
I send the following IDocs from SAP-ERP over SAP-XI to Non-SAP for an initialload: Artmas, Bommat, Infrec, Cond_a, Mmaddi, Cremas
Example: Artmas with TA: BD10.
Problem: SAP-ERP send all 25'000 IDoc to SAP-XI. The effect is that the qRFC and tRFC in SAP-XI is full, because the Non-SAP is not fast enough to takeover the Idocs. From then other systems can't send out or get in Idocs.
I tried to limit in WE20, but it didnt work. TA: RSEOUT00 ist not so useful, because of the quantity of the IDocs.
Is in SAP-ERP a possibility to limit the sending of IDocs to SAP-XI or Non-SAP?
Example: Automatic sending of 200 Idocs every 2 Minute.
Thanks

may be u can write a wrapper above BD10 this way
report zaRs message-id b1.
select-options: matsel for marav-matnr matchcode object mat1.
parameters: receiver like tbdlst-logsys no-display.
start-of-selection.
select * from mara into i_mara where matnr in matsel.
refresh : matsel.
v_no = 0.
loop at i_mara.
    move i_mara-matnr to matsel-low
* fill up sign option etc.
    append matsel
do.
   move mara
   if v_no = 200.
    submit rbdsemat " Program behind BD10
          with logsys eq receiver
          with matsel in matsel
          with mestypat eq 'ARTMAS'
          and return.
          wait 20 seconds
    exit.
    clear v_no.
   endif.
enddo.
a®

While Posting IDOC from XI to R/3 Message Type needs to be changed

We are doing mapping IN XI. For one condition we want Message Type to be ORDERS and for one condition we want Message Type to be ORDERSCHG
when posting IDOC from XI to R/3.
Pls revert anybody asap.
Regards

Hi,
>>>>It means I need to create two Interface Mappings for the same message mapping and then I can use the Interface Determination . Am I right.
no, you need two message mapping
and two interface mappings
file - orders.orders05
file - ordrchg.order05
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Sending IDOC from SAP ECC to SAP MII

Hello,
Issue while configuring.
I have configured the RFC Destination in the Netweaver message listener and when i check the connection in SM59 I got error as timeout during allocate of registered program and I have attached the screenshot of the error page.
I would request a reply asap.
Thanks,
Praveen

Hi Praveen,
First, I would suggest that you identify what version, and SP, of MII and ECC. Also the NW version and SP if applicable.
Second, use this custom Google search and terms MII, IDoc Listener, and perhaps SM59. There are many discussions on IDoc Listeners going back a number of years. Many of the issues with IDoc Listeners have not changed in most of that time, so look at the older ones as well. I presume that you found and are using my How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener (MII 12.1 to ECC 6.0) to set up your Listener? If not, you should review your configuration and setup procedure against it.
I have not looked at MII 14.0 or 15.0, but understand that the configuration of Listeners really has not changed since MII 12.1. So the document is still applicable.
Third, roughly 90% of the problems experienced with IDoc Listeners involve multiple uses of the self registering ProgID. Deleting it in one place, generally does not work. Use it in one place only. Create a new ProgID for each separate Listener (either type) on each separate MII instance for each ECC instance. Save yourself a lot of headaches. Never, ever reuse ProgIDs!!!
Fourth, most of the other issues involve a PI/XI system in the middle. Those are a bit more complicated since they rely on getting the connection configuration set up properly in PI. Since I am not that familiar with PI systems (most times it is not involved with the Listeners), I generally have to get other experts involved. Sometimes a CSS ticket is required.
Regards, Mike
SAP P&I Technology RIG

Post Idoc from SAP to Thirdparty using XI

Similar Messages

Maybe you are looking for