Doubt on IDOC TO IDOC communication

Hi Experts,
I have a doubt on IDOC to IDOC communication:
Plz clarify it
1. what is the need of passing same IDOC from one system to other system through XI while communicating between two systems,it can be done by using ABAP also ?
2.what is the advantage of passing like this through XI compared to ABAP?
                       Plz clarify good answers will be rewarded .
                                                                                Regards,
                                                                                Vinod.

Hi,
See when you are dealing with Only IDOC to IDOC Communication means there is no need of XI here.
You can go with ALE also here.
Situations to go to XI.
1) when you have the Different field mappings
2) When you are having the multiple receivers
3) when you are dealing with Bundling & Transformations
Reward Ponts If Helpful
Regards
Giri

Similar Messages

Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

Hello All,
One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
Is the (IDoc) Communication Channel from Sending system to XI required to configured?
Many thanks in advanced!
Jochen

Hi Jochen,
for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
Thanks,
Rajeev Gupta

Doubt on scenario involving idocs

Hi,
 Thankz for ur replies for my questions,i had some doubt in file to idoc scenario
plz give replies as briefly as possible best answers will be rewarded.
1.Once XI receives the File, the BAD records needs to put aside in a different file and only the good records needs to be sent to the Adapter.
Whether Module Processing is the Best Solution?
What would be Technical approach for the above scenario?
 Regards,
 Smitha.

If there is an error in the mapping if a sender sends wrong format, the complete processing will be stopped.
Once XI receives the File, the BAD records needs to put aside in a different file and only the good records needs to be sent to the Adapter.
U can go for enhanced interface and receiver determination. BCoz based on input data, u have to choose Idoc receiver or File Receiver
Whether Module Processing is the Best Solution?
Not the Best option. but could be used
Regards,
Prateek

Idoc to Idoc communication thru XI

Hi,
Any one can explain the step by step configuration details about IDOC to IDOC communication through XI not an ALE concept.
Thanks
Rao

There are some good IDOC How To guides here:
Exchange Infrastructure How-to Guides for SAP NetWeaver 2004 [original link is broken]
Nice step by step instructions.
I am configuring several IDOC to IDOC scenarios.
They are relatively staright foward.

Issue in IDOC-XI-IDOC scenario

Hi,
We are facing a strange issue in an IDOC-XI-IDOC scenario. We are using a SAX parser to parse the code here.
The error we are getting in 'sxmb_moni' is
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS</SAP:P1>
<SAP:P2>java.lang.RuntimeException</SAP:P2>
<SAP:P3>For input string: ""</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS a java.lang.RuntimeException was thrown: For input string: ""</SAP:Stack>
The strange thing is, when I restart the message, it gets processed successfully. Also, when I copy the payload, and test the same on a different environment, it gets processed successfully.
Would really appreciate some pointers here!
cheers,
Prashanth

Hi,
This related to mapping error check it once again.Check in Interface mapping Test tab.see the result.check the sxmb_moni and get the source of mapping come back to interfcae mapping and test .
See the below links
Hi I got EXCEPTION_DURING_EXECUTE in RWB->Message Monitoring
I am getting MAPPING EXCEPTION_DURING_EXECUTE
EXCEPTION_DURING_EXECUTE- Error in Mapping. Doubt about IE and AE
EXCEPTION_DURING_EXECUTE
Mapping problem - EXCEPTION_DURING_EXECUTE
ERR: EXCEPTION_DURING_EXECUTE while using FILE CONTENT CONVERSION
Regards
Chilla..

IDoc to IDoc scenario: distribute the model view

Hi!
I try currently to configure a IDoc to IDoc scenario for SAP ECC 6.0 system with following business 2 systems:
ERP:100 (Sender)
ERP:200 (Receiver)
and XIB:100 (XI system)
I successfuly created a message type and generated the model view in tcode BD64.
Question:
When I try to distribute the model view which system should I choose?
a) XI System or
b) Receiver system ERP:200
When I choose the receiver system ERP:200 and get the following error
Target system: ERP:200
Model view ECCCLNT100 has not been updated
Reason: Distribution model is currently being processed
When I try to choose my XI system I get the following error:
Target system: XIB:100
RFC destination for synchronous communication (message type SYNCH)
Partner profile LS PIBCLNT100 SYNCH does not exist
Generate partner profile
or specify outbound partner profiles for message type SYNCH
Is that an error? If yes, how can I fix them?
Thank you very much
Thom

Hi
Look my reply on this thread regarding SYNC Message Type.
Re: problem while distribute model view
When I try to distribute the model view which system should I choose?
a) XI System or
b) Receiver system ERP:200
You are sending IDoc to XI then R/3 so select XI system. because receiver of IDoc is XI then IDoc would be send from XI.

Idoc- XI- Idoc - still awaiting acknowledgement

Hi guys!
We send Idoc->XI->Idoc and in sxi monitor we have a green flag - still awaiting acknowledgment. What does it mean? How can we be sure, that Idoc is received bu target application?
Thanx olian!

Hi Olian,
One way is to logon to R/3 system and use tcode WE02 or WE05 and there give your idoc type and press F8. you can see your idoc here.
Also go through it.
/people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
Note: IDoc technology supports its own acknowledgment technology, namely the ALE Audit. Here there are no acknowledgment requests from the sender. Instead, the receiver decides whether an acknowledgment IDoc should be sent back to the sender based on the ALE configuration. These acknowledgment IDocs are only used for monitoring on the sender side.
IDoc technology is the only technology in which positive acknowledgments from the application contain data. This data is sent by the IDoc adapter in an acknowledgment IDoc if the sender is an IDoc system. Otherwise, the data is discarded.
For the inbound IDoc adapter to be able to send an acknowledgment IDoc to the sender, a communication channel with the interface ALEAUD.ALEAUD01 must be maintained for the sender.
Regards,
Sarvesh
Message was edited by:
Sarvesh Singh

B2B- IDOC 2 IDOC

Hi all,
We are building PI 7.1 from scratch. I have few doubts about it
My client has ECC 6.0 and installing PI 7.1 which able to receive and send IDOC's from it's customers (they also running ECC), so basically it is B2B IDOC 2 IDOC scenario. Can somebody tell me how to setup the Technical systems and Business Systems for this cross company scenario( I never worked on cross company scenario before).
Thanks in Advance,
Rishik.

SOURCE SIDE CONFIGURATION: Client ECC (SAP R/3)
1. Create RFC Destination: To create a RFC destination use transaction SM59.
2. Create Port: To create a port uses the transaction WE21
3. Now Go to Transaction Code SALE and create Logical System.
4.Creation of Partner Profile:
XI SIDE CONFIGURATION: Target SIde ECC (XI SYSTEM)
1. Create a RFC Destination with Target ECC(R/3 System) and select the connection type as 3(Connection to R/3 System).
2. Go to Transaction Code IDX1 and create an IDoc Port PORT_01 (Transactional RFC) and map it with the RFC destination
3. Go to Transaction Code IDX2, Click on Create and enter the details of IDoc Type and Source Port.
TARGET SIDE CONFIGURATION: CGNSAP01 (SAP R/3)
1. Go to SALE and create Logical System.
2. Create Partner Profile:

IDoc to IDoc through ALE

hello experts !! could u plz give me some idea or step by step help for creating IDoc to IDoc data transfer through ALE.
My scenarion is like the following:
there will be two client in two R/3 system..(Sending and receiving)....
in sending system i want to insert data in a particular table....
that data will be automatically updated in receiving system..
plz help meeeeeeee
thanks...
points will be rewarded.......

Hi Soumya,
Follow the process as below
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards,
Satish

Very simple and working IDoc to IDoc scenario

Hi!
I would like to implement for demo issues a working IDoc to IDoc scenario with SAP XI 7.0.
The IDocs sohuld be send from SAP ECC 6.0 system client 100 to SAP ECC 6.0 system client 200.
Questions:
- which material type should be used (e.g. MATMAS02,..)
- how should the message mapping (e.g. MATMAS02 to MATMAS02) look like
- what are the other settings in IB Repository and IB Configuration
- how should the test from WE19 look like?
Thank you very much!

Hi Holger,
No issues for that , U can use the MATMAS 02 or MATMAS 03.
Setting in R/3 system:
1) Create the RFC Destination(SM59).
2) Create the tRFC port(WE21)
3) Create the Partner profiles( WE20)
4) Create the Distribution Model(BD64)
Setting in XI:
1) Create the RFC Destination
2) Create the IDOC Port into IDOC Adapter(IDX1)
3) Load the Metadata into IDOC into IDOC Adapter(IDX2).
Same settings happened in Receiver IDOC also.
Directory : No need to create the Sender agreement & no need to create the Sender Communication Channel.
Repoistery: Import the Sender IDOC and Receiver IDOC from R/3 system.
In WE19 Testing tool we can test IDOC generated or not.
Regards,
Sateesh
D

Idoc-XI-Idoc Scenario

Dear All,
I am working on Idoc-XI-Idoc scenario in which I am getting ORDRSP Idoc in input. In one of its segment I am getting value as either A or B. If value is coming as A in input then in the output we want PORDCR101 Idoc but if we have B as value in the source idoc then we should have multiple PORDCR102 Idocs ie for each line item there will be different idocs.
Please guide me on how we can implement BPM in this scenario as required two MM i have created and they are working fine.
Regards,
NJ

Hi,
If value is coming as A in input then in the output we want PORDCR101 Idoc but if we
have B as value in the source idoc then we should have multiple PORDCR102 Idocs ie for
each line item there will be different idocs.
For Source = A:
SourceField----
-----equalS ----ifwithoutElse ----then Constant(blank) ---> PORDCR101
Constant(A)---
Assuming that A in input then in the output we want PORDCR101 Idoc means that you need only one occurence of the IDOC
For Source = B:
SourceField----
-----equalS ----ifwithoutElse ----then LineItem ---> PORDCR102
Constant(B)---
Regards,
ABhishek.

IDOC-Xi-IDOC: CRM - XI -R/3 (No service for system SAPOCC, client ** in ID)

Hi all
I am doing a scenario IDOC - Xi - IDOC where CRM sends an IDOC to R/3 via PI.
I have configured everything in OCC (CRM system), PI and BSC (R/3 system) but when I test it with the transaction WE19 in OCC nothing happens in PI or BSC.
All i can see if a message in SM58 transaction in OCC.
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - XI.
Status Text - No service for system SAPOCC, client *** in Integration Directory.
Could anyone tell me what is the problem.
Your help will be very much appreciated
Regards
Naina

Error message: No service for system SAPCRD client 201 in the integration directory
Cause: There is no service without party in PI server that represents OCC server with client details.
Solution:
We send IDocs from system OCC to PI. In the control record (Segment EDIDC40) of the IDoc, the SNDPOR (SenderPort) field contains the value "SAPCRD". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service)
In System Landscape Directory (SLD) create a technical system for OCC system and assign a client for the same. Don't forget to assign an "ALE logical system" to the technical system created. Create a business system for this technical system. Then Business System can be imported under service without party/update the details existing in PI.
Edited by: Rodrigo Alejandro Pertierra on Jun 23, 2010 10:28 AM

Error in IDOC-XI-IDOC scenario

Hi folks,
Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPMs involved. SAX parsing used to parse the IDOCs.
We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as Problems found during the EXPORT to specified keyin table.
When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying Function module does not exist or EXCEPTION raised.
I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is EXPORT_TABLE_UPDATE_CONFLICT.
In the what happened? part of the dump, it says Error in ABAP application program. The current ABAP program CL_XMS_PERSIST=============CP had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.
Even SXMB_MONI is not opening (for yesterdays date). When I try to open it, it hangs for a long time, and finally opens an ABAP Runtime Errors page with the runtime error titled as SNAP_NO_NEW_ENTRY and the error short text as Runtime error: Unable to write short dump
Please advise.Thanks a ton!
cheers,
Prashanth

Hello Prashanth,
First of all this is an XI issue and belongs in that forum.
The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
Function module does not exist or EXCEPTION raised- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
Good Luck (don't forget to award points)
Ofer

IDoc missing in IDoc - XI - IDoc scenario

Hello!
The integration scenario is R/3 4.6C (IDoc) -> XI -> (IDoc) R/3 4.6C for DELFOR, ORDERS, ORDCHG, DESADV and ORDRSP.
Now we switched to a new XI development system and the flow is working for all message types besides DELFOR.
WE20 -> New XI Logical System Name -> DELFOR points to the new receiver port which referenced to the correct SM59 destination that is used by all other message types as well.
There is also no error in SM58 in the sending R/3 system and the DELFOR IDocs are in status 12 in WE02 but when I search the IDoc number in IDX5 on XI the IDocs are not there.
Does anybody have an idea where to find the DELFOR IDocs?
Regards, Tanja

Hello!
> IDOC staus if it is sent out from R/3 should be 03 or
> 12?
First it was 03 but as I was not able to find it anywhere I ran a report and the status changed to 12 afterwards.
> if IDOC is coming out of R/3 without any errors( sm58
> no errors) then it should come in the SXMB_MONI in XI
> as it usess th TRFC Port........
Yes, this is also my understanding but it is not in SXMB_MONI nor in IDX5.
> if it is not check the SMQ2 and SMQ! in both XI and
> R/3...it cannot go anywere else (-:
I have checked SMQ2 and SMQ1, the queues are empty in XI and R/3.
Regards, Tanja

Sender port is not picking in PI for idoc to idoc scenario

Hi Guru's,
i am doing idoc to idoc scenario passing through sap pi ,while executing this idoc from client1 is successfully coming to PI, but while going from PI to client2 , i am getting error 51 (company code is defined for LS(logical system) for 1000 (vendor),i checked the configurations for sender idoc from pi ,it is taking a port value which is not present neither in xi nor in r/3 it is MDM interface port value i tried makking the port value constant in PI mapping ,but still same error is comming.
idoc created with partner type LI in source system.i am posting it as LS in receiver system.
Please help me in resolving this error.
Regards,
reddy

Hi,
The error mentioned by you is not related to the port..but its related to the Application ...
IDoc 51 means idoc has been received in R/3 client and when it tries to process it ended in error..
Check with the functional consultant for the error you have received..
HTH
Rajesh

Doubt on IDOC TO IDOC communication

Similar Messages

Maybe you are looking for