IDoc from SAP R/3 to SAP XI

Hi All,
I am passing an IDoc to SAP XI. I have had to amend a bespoke segment on the IDoc. I have imported the new strucutre into XI. When I send an IDoc to XI the payload is not showing the new fields, even though they are populated correctly.
Any ideas??
Thanks
Martin

Hi Martin,
delete the IDoc meta data in XI transaction IDX2 and try it again.
Regards,
udo

Similar Messages

Steps of EDI is used to transfer IDOC from R3 system to non sap system

Hi Experts,
Can you provide me Steps to configure EDI is used to transfer IDOC from R3 system to non sap system?
Full points will be assigned.
Thanks in advance!
Sapna

Hello,
 The EDI Configuration required to be done for Transfering IDoc to non SAP System is.
1. First of all, we need to identify the Transaction Data which is required to be Transfered to external System.(Ex: Sales Order Data or Shipment Data or Delivery Related Data).
2. Secondly, Identify the IDoc Type & Message Type. IDoc Type can be found in Transaction WE30 & Message Type Can be explored in Transaction WE81.
3. After that, assign the IDoc Type to Message Type in WE82.
4. Identify the Selection Program (Outbound) which is generally a Function Module in the Form of IDOC_OUTPUT_<Message Type>. Example, if the Message Type is ORDERS, the FM will be IDOC_OUTPUT_ORDERS.
5. Assign the Function Module to a Process Code in WE41 (Process Code for Outbound).
6. Configure Port Definitions in WE21 for which the RFC destinations are to be maintained in Transaction SM59.
7. Maintain Partner Profiles for the Outbound Message Processing in WE20.
8. Last, but not the Least, we need to Focus Mainly on Message Control Configuration which is nothing but maintaining the Output Type for the Outbound IDoc to be Triggered for the Sales Order Application or Delivery Application.
 i. In Message Control Configuration, we'll maintain
 a. Condition Tables
 b. Access Sequences
 c. Output Types
 ii. To Create the above elements, we can go to SPRO Transaction and do the same depending on the Application Area such as Sales / Shipping / Logistics Execution etc.
 iii. For Output Types & Access Sequences, we can go to the Transaction NACE or VK01 in which we'll maintain the Output Types / Access Sequences & Condition Records.
 Please note that all the above steps may not be needed if we are using some of the Standard Elements provided by SAP such as Message Type, Process Code, IDoc Type & Selection Program as many of the Standard SAP Applications have their own Elements for different Application Areas.
 For example, if you want to send an Order Confirmation IDoc when the Sales Order is saved, you can use the Message Type ORDRSP, IDoc Type ORDERS05 & Selection Program as IDOC_OUTPUT_ORDRSP.
 However, Message Control Configuration is the Key Factor and is required for all the Applications as per the Customer's / Client's Requirements.
Hope the above procedure was clear.
Thanks and Regards,
Venkat Phani Prasad Konduri

Urgent: Sending order05 IDOC from R/3 to ICH (SAP SCM) through SAP XI

Hi All
I have requirement where I have to send Order05 IDOC from SAP R/3 (ECC 6) to ICH (SAP SCM 5) through SAP XI (PI 7).
I came to know that there is one standard scenario in SAP SCM Basis content in integration repository.
I never done any XI development, please guide me with the useful links or whole step by step process. I will be very thankful for your inputs.
Please reply asap.
Regards,
Amol

Hi !
Check this note:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d383336323030%7d
Regards,
Matias.

Error sending IDOC from external Java application to Sap ERP system

Hi Experts!
When I try to send Idoc from Java application to XI an error occurs : no service for system CLNTJAVA, client in Integration Server.
My question is: What value the setSenderPort() is excepting?The Java third party business system's logical name or the ERP business system's logical name where the JCO can be found?I tried both of them, but still have the problem.
Please help. I read all threads about this error, but non of those can help me.
My relevant java sourcecode:
doc.setSenderPort("CLNTJAVA");
The XI documentation says that:In the case of non-SAP senders, the entry in the SNDPOR field is interpreted as a logical system name, and the corresponding business system is searched for in the runtime cache.
Both case(third party business sytem and erp business system) I have configured the ID i think correctly. I made a business systems,I configured the adapter specific identifies,I made the IDX1 port,I made the RFC destination,I polled the IDOC type with IDX2 transaction, I have made full cache refresh,I configured the INTEGRATION_DIRECTORY_HMI rfc destination,but I do not made any communication channels, receiver determinations, receiver agreement.
My configurations if it can help for you.
Hostname:sapsp5
System name: NE2
Clients:
000 ERP
001 Integration Server
SLD configurations:
Third Party Technical system name: Java_sytem
Business System:CLNTJAVA
Logical system name: CLNTJAVA
ID configurations:
Business System:CLNTJAVA
adapter-specific identifiers:logical system:CLNTJAVA, the rest is initial,because I cant change it.
IDX1 port name: CLNTJAVA the client is 001. the rfc destination is client_001.
I think the IDX1 port and the adapter specific identifiers are wrong. is it?
my java source if the sender is the JCO
doc.setSenderPort("INTSERV");
My configurations if the sender is the JCO.
SLD configurations:
Technical system name: NE2
Business System:INTEGRATION_SERVER_NE2
Logical system name: INTSERV
ID configurations:
Business System:INTEGRATION_SERVER_NE2
adapter-specific identifiers:logical system:INTSERV,system NE2,client 001.
IDX1 port name: INTSERV the client is 001. the rfc destination is client_001.
Could this error be an autorization error?I tired to connect to the xi from the Java, with the user PIISUSER extended with PISUPER roles.
Thank very much.

Hi!
My SNDPOR already set to my source business system's logical name if you check my configurations(JAVACLNT), so there is another problem unfortunately. I set SNDPRN to JAVA, but it still does not work.
Check this configuration please(posted here:
No service for system ... in Integration Directory)
doc.setMessageType("ACC_DOCUMENT");
doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set
doc.setRecipientPartnerType("LS");
doc.setRecipientPartnerNumber("SE1CLNT500");
doc.setSenderPort("SAP3MA");
doc.setSenderPartnerType("LS");
doc.setSenderPartnerNumber("TREMACLNT");
doc.setClient("100");
Inside XI configuration integration builder
Business Service: Service: TREMACLNT
Under the menu Service - Adapter specific identifiers
Idoc Adapter Logical system: TAPPMAN (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA
Client: 100
In IDX1 trans
Port: SAP3MA (Note that the 3MA here is matched against the IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA)
(a not so well documented feature)
Client: 100
RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
I guess that your idx1 port name is the same as the SNDPOR value. I think it should be, because the XI is whatching the IDOC traffic in the idoc adapter port, so you should send the IDOC from external system to the adapter port. Is it right?
My idx1 port is the same as my SNDPOR value in Java,but still came the error.

How to Trigger an IDOC from SAP R/3 to two systems at a time

Hi experts,
Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
My current production R/3 system sends a DELVRY03 IDOC to Production XI system ( Name : XIP) .
I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
Problem is production R/3 system triggers an IDOC once. We need to write a logic to route the same to two different systems
Can any one tell me how can we do that ?
Regards
Ram.

Hello Ram,
Do you have connectivity between your production & XIQ?
What does "connectivity" mean?
1. RFC destination is maintained.
2. Port defined for the RFC destination.
If no, create these. (Search in SDN for details).
If yes, proceed:
1. Define the logical system for XIQ.(BD54)
2. Define the same as your partner profile. (WE20). Add the message type SYNCH with the port for XIQ.(This is imp)
3. Create a distribution model view with sender as "your production" & receiver as XIQ.
3.1. Add the messages which you want to distribute.
3.2 Generate Partner profiles.
No coding is reqd. for this.
BR,
Suhas

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
Target system XIDEV Communication error occurred
User is locked. Please notify the person responsible
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 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

IDOC settings from sap r/3 to sap pi7.3

Hi Guru,
actual problem when i am triggering the idoc from ERP,it is trigeering to the abap stack in sap pi.but i am using idoc_aae adapter at sender side,the message is flowing from sap ERP to file but the message is seen in sxmb_moni,but actually it is not seen in moni .
Please if any one have the idoc setting from sap erp to sap pi7.3. and iam using ICO configuration.
Please help me
Regards
Reddy

Hi,
Please go through the below link :
http://wiki.sdn.sap.com/wiki/display/XI/ALE-Idocconfiguration-+%28R3XIFile%29
Also in your software component version please check whether import of IDocs and RFCs are allowed
from your respective ECC system, and check the ECC system parameters are correctlt maintained or not.
Try out once.

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

How to Trigger an IDOC from SAP R/3 to two XI systems

Hi experts,
Can any one please tell me How to Trigger an IDOC from SAP R/3 to two XI systems at a time.
My current production R/3 system sends a DELCERY01 IDOC to Production XI system ( Name : XIP) .
I would like to route the same IDOC from production R/3 system to my Quality XI System ( Name XIQ) .
Problem is production R/3 system triggers an IDOC once.
Regards
Ram.

Hi Ravi,
Thank you very much for your answer.
As I am not completely aware of R/3 side,I am getting little problem in understanding your answer.
Could you please explain the same in some what beter way.. Thank you ..

IDOC import from CRM 7.0 to SAP PI 7.0 fails: unable to read segments

Hello,
We want to import an Idoc from a CRM 7.0 system to SAP PI 7.0.
The import fails with the message ""unable to read segments".
The issue is related to ALL Idocs, standard and customer defined.
The result of any import is that we can see the object in the import folder, but the structure is missing.
Importing any RFC from the same CRM system is no problem.
Any ideas?
Your help is appreciated.
Regards
Dirk

Hi Peter,
Thank you for your answer.
But we need to find out what the reason for this import error is.
Our customer will not be very pleased to see that all IDocs from CRM system cannot be found in the IDOC folder.
IDX2 import of metadata is no issue.
We were successful for standard and customer Idocs here.
Additional information:
We are already importing Idocs from a SAP ECC 6.0 system into PI in another SWCV
successfully. So this is a CRM system specific issue in our environment.
Regards
Dirk
Edited by: Meinhard Dirk on Aug 27, 2010 10:30 AM

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 ?

Import IDoc from SAP R/3 3.1I to ESR

Hi experts
For the import of RFC and IDoc structures the SAP Backend needs SAP Release 4.0 and higher.
But I have the requirement to import an Z-IDoc from an SAP R/3 3.1I to the PI-ESR.
Is there any way to do this?
Thx
Tobias

As there any other R/3 system in your landscape to transport the RFC or IDOC to and upload from there?
The interface needs not to be uploaded from the same system as processed later.
But you cannot use PI for this, as the target system for RFC or IDoc and the system to upload the metadata must be both unicode or both non-unicode.

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

IDoc from SAP R/3 to SAP XI

Similar Messages

Maybe you are looking for