Is it Possible to send IDOCs from one system to itself?

Hi,
Is it possible for the R/3 system to send IDocs to itself?? If yes can you guys guide me on how to configure the system to do the same.
The requirement is for learning purpose only.
Regards,
VJ

dear vijayendra,
you can do it by creating two clients on your system jus talk to any basis person for creation of clients after that you will make the configration on both client by just login through that.
after proper configration you can send the idoc.
first create the client after that u can talk to me in more details.
i have around 2 year hands on experiance in ale idoc.
by
vijay dwivedi
rewards if answer is helpfull for you.

Similar Messages

IDOC from One System to another

Hi All,
I am sending idocs from one system to another For Eg System A to System B .
Now suppose 2 idocs are generated 1 and 2.
Now how to determine , for idoc 1 in system A, what is the corresponding Inbound Idoc in System B because the data which is coming in System B might be different than in System A for the same Idoc?
Thanks in Advance.

Hi,
direction 1 for outbound idoc,
              2 for inbound idoc,
goto tcode WE02
enter direction - 2.
creation date
and basic type i.e. idoc type
double click on an idoc num.
on L.H.S u have 'Control REc' double click on it..
it contains all the sender details and to what outbound idoc it corressponds to -> basic type, message type
    -> Partner details like partner num, port, partner type
    -> date & time of creation
    -> and the other details
Regards,
Neelima.

Send idoc from one version of R/3 to different version

Hi All,
I have a scenario to send idocs from one R/3 system to another (both have different versions) .Can anyone tell me the step by step way to configure. Do I need to program anywhere to send or receive idocs Any help is really appreciated
Thanks
Michael

Hi michael,
The version change technique allows you to exchange idocs with systems using the older version of idocs.
For this v have to configure the sending system to generate back level idoc for receiving system using the partner profile. configuring the partner profile is enough to send idocs in this scenario.
Regards....
Arun.
Reward pts if useful.

Is it possible to send varient from one client 800 to another client 810

hi
is it possible to send varient from one client 800 to another client 810,
could u plz explain clearly,

Hi,
You can use the transport mechanism to transport variant.
Go to SE38, type in the report name and choose "Variants". Then select the variant and choose the menu Utilities -> Transport request. Add the variant to an existing transport.
Then use the standard procedures to move the transport request from client to client.
Hope this helps (please reward me if it does).
regards, Joerg

Send PO from one system and create a SO in another system

Hello Gurus
ii am learning ALE IDOC and would like to do a complete hands on practice. I have been doing some basic scenarios and so far i am progressing well.
What i am planning to do:
Now i would like to do an end to end scenairo of sending a PO idoc from one system and this should create a SO in the other system.
Steps i am planning to do:
1). Configure the sending system for a outbound PO idoc
2). Configure the receiving system for a Inbound SO idoc
3). Maintain VOE2(EDPAR) and VOE4(EDSDC) tables for partner information and organization information respectively.
Questions:
1). Am i missing any steps?
2). I am confused on what to maintain in VOE2 and VOE4. Which information of PO should i maintin in VOE2 and VOE4 in the receiving system?
~Suresh

Hi Suresh,
this might be of some help.
ALE IDOC
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 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view
This is Receiving system Settings
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
Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors
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
1) System Name : ERP000
Description : Sending System
2) 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
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
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)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
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
I know 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
kindly reward if helpful.
cheers,
Hema.

Transfer Idocs from one system to other

Hi,
Please check below scenario regarding Idoc transfer from Source to Receiver system:
I have source system SRC and receiver system REC.
I want to send Idocs from SRC to REC based on some data checks in REC system.
For ex, I am sending Sales order Idocs from SRC to REC, but should send the Idocs only when corresponding Sales area customizing is maintained in REC to avoid creating error IDocs in REC.
Is there a way to check on REC customizing data before sending Idocs from SRC system?
Thanks,
Yogita

As you said "I would probably have a program running every x minutes to check for required changes in REC system"
But the required changes in REC system is the customizing data which I need to check against the Idocs in SRC system. So how will I link it with the Idocs in SRC?
Also do you think it is possible with RFC call from SRC system to check customizing data in REC system which is releated to SRC Idocs ?
What I was thinking is:
1 Collect SRC Idocs to be sent to REC
2 RFC call from SRC to check customizing data related to collected IDocs
3 If Customizing exists, do outbound(RSEOUT00)
else
dont post Idocs from SRC
Do you think this is achievable?
Thanks,
Yogita

Send IDoc from External System to SAP system

Hi Folks,
I have a requirement to send IDocs from an external system to the SAp system. Basically the external system is a subsystem which is able to send & receive idocs. The external system is currently able to send idocs to SAP system through the ALE layer but now we have to replace it by PI. Now the external system has to send teh IDocs to the SAP ECC system through the SAP PI 7.0.
Kindly let me knowq how I can achieve it.
Regards,
Santosh

Hi Satish,
You can achieve this requirement
1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel to send IDoc.
or
2)Use proxy program ,implement the same ALE logic in PI.
or
3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
Regards,
raj

Send IDOC from SAP system to IX but can't see any message in SXI_MONITOR

Hi all,
I have built up an XI system and configured an IDOC to IDOC scenario between two SAP Systems. After completed all configuration necessary:
1. Configuration on Source Side (SAP System that send IDOC) and on Target Side (SAP System that receive IDOC) is OK.
2. SLD is OK: Technical System and Business System are correct for these two SAP System.
3. Integration Repository: all designed Object is OK.
4. Integration Directory: all configuration is OK. "Test Configuration" Function is OK.
5. Runtime WorkBench: is OK. "Test Message" Function of "Integration Server" is OK.
In general, it is all OK.
But when i send an IDOC from SAP System Sour Side (Outbound IDOC from Source Side is OK), on the XI server i can't see any message in Tcode SXI_MONITOR. In this case, my XI server didn't receive any IDOC Message from this Source Side, and so that my XI server can't process and exchange any IDOC sent from Source Side.
Anyone can please help me to explain this problem: why my XI server can't receive any IDOC message from SAP System Source Side when all configuration is OK? Do anyone see the same case as this case?
Thanks a lot for all in advance,
Best regards,
Vinh vo

Hi,
Possible checks
At R/3 side
1) Check in SMQ1 and SM58
At XI Side
1) Check in SMQ2 and IDX5
Check this
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Regards
Seshagiri

Sending idoc from one r3 system to another r3 system

Hi
I want to send the idoc from system A to system B only (not from B to A). Then is it need ports in both the systems or only in one system ?? If it is on one system..... on which system port is needed ?? (A or B) ?? similarly RFC destinations also......whether it needs one or two ??
thanks
kumar

Hi seshu,
thanks for your reply !! once you create the rfc destination and after that if you create the port for that rfc destination............whether port will be created for the source system side or target system side. ??
thanks
kumar

Sending IDoc from external system to XI system

Hi All,
I want to send an IDoc from a subsytem (External System) to the SAP PI system. how to achieve the same ?
Regards,
Santosh

hi,
>>>Do you mean to say the port I am creating for the external system should actually refer to a SAP system
not the port - port's name should be a new one but the RFC should point to an SAP system
>>>and the IDoc you want to transmit should be imported to that port using the tcode IDX2.
this will be transported then from SAP application system
>>>>In fact I have already done the same step but its still not working the IDoc is not reaching the XI system.
then you should see the error in your sending tool - I worked with JCO IDOC client and the error was always
very explanatory (like BS in SLD missing etc.) so it was pretty easy to debug
Regards,
Michal Krawczyk

QRFC/TRFC for sending idocs from SAP system to XI

Hi experts,
The standard program RFFOEDI1 generates payment orders - first PEXR2002 and then EUPEXR idocs. These idocs are to be sent to the bank from SAP through XI. Bank partner profile is maintained. But these idocs because of TRFC are not getting sent in the order in which they are generated by the SAP system. So I changed the bank partner profile settings from TRFC to QRFC and gave the rule name as first 16 of mes type. But the idocs are struck in the SAP system. Is there any standard program to be run to send the idocs out from SAP system or is it automatic.
Please suggest a standard method which is to be followed to send the idocs in the same order in which they are getting generated for the scenairo above.
Regards,
Asha

Hi Asha,
As you said Idocs are stucking,
To send Idocs to XI, you must have maintain some settings in XI to receive Idocs. Once they are done properly .in R3 side standard way to send idocs to XI is Maintaining Change Pointers and shedule the programe to trigger that most of Standard idocs will have standard programs to catch change pointers and send them to external system.
and to maintain the same order of idocs there is a setting called Quality Of Service in XI side ,that option should be set to Exactly Once In Order .
Regards,
Ramesh.

Using remote enabled rfcs can we send data from one system to other..

or do can we do this only b/w twp sap systems.
why do we use bapis then.
wat is its difference b/w rfc and bapi.

Hi Jaya Krishna,
RFC's can be accessed from non SAP systems also.
Technically BAPIs are RFcs Function modules only.
The only differenece is the business utility of them. The BAPIs have a standard Business functionality attached to them, like creation of an Order, Changing a Purchase document etc, Where as normal RFC function modules may or may not have a specific business functionality attached to them.
Regards,
Ravi

Send IDOC from Business Connector to SAP faster

Hi Developer!
I need to send a very lot of IDOC converted from XML files from the Business Connector to SAP. The XML files are in different directories pro business partner, but they have a same type (ISU_MSCONS).
My problem, that the import take a lot of time. Only in every 3 seconds (IDOC creation time) gets (or works up?) the SAP one IDOC. I start diferent services pro partner at the same time to import the IDOCs, but I couldnt short the 3 second work time in the SAP. So you can count it easy, that in 1 minute I can import 20, in 1 hour 1200, in 1 day 28800 IDOCs instead of 100.000.
It is really parallel import? Have anybody any idea to make the import more faster. I know (asked the SAP Administrator) so, one BC - SAP connection (Program_ID) has more pools (= threads) in the SAP at the same time.
Thanks any help,
Charlie

Hi Satish,
You can achieve this requirement
1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel to send IDoc.
or
2)Use proxy program ,implement the same ALE logic in PI.
or
3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
Regards,
raj

Sending IDoc from ERP to PI

Hi all,
I am trying to sent IDoc's from the ERP (SAP ECC) side to PI. But the IDocs are not arriving at the PI side. In ECC tc:we05 they seem to be successfully sent.
The Partner Type in we20 is "LI". I added the IDoc to the Outbound parameters and set the PORT to the Port we use for PI. But unfortunately it is not working.
Any idea why?

When sending IDoc from ECC System to PI.
some settings needed on ECC System & PI System
On ECC System
Create Port in WE21 type LS (Logical System) use RFC Destination TYPE ABAP in that port.
Create Partner Profile using PORT in WE20.
Add the Idoc as Outbound in that Partner Profile.
Now on PI System
PI System does not have structure / matadata of IDoc.
Create Port in IDX1.
Import IDoc Matadata in IDX2 use Port created in IDX1.
Create complete scenario & send IDoc from ECC, it will reach at PI System, if successful at ECC.

IDOC from external system

Hi,
I have scenarion in that we will receive IDOC from external system (SAP system) in XI i.e. IDOC- XI -IDOC scenrio. from my Understanding ,to configure the scenario I have to do ALE from sender side and IDOC receiver channel in receiving side.
External system (SAP) -(ALE)-> XI -(IDOC rcv)--> Our System (SAP)
Please can anyone provide me steps to do ALE from external system.
Edited by: tapan singh on Feb 28, 2011 11:51 AM
Edited by: tapan singh on Feb 28, 2011 11:52 AM

Hi,
We can have alternate ways to send IDocs from external system to SAP system. One way is in below link
http://help.sap.com/saphelp_46b/helpdata/en/52/16abf6543311d1891c0000e8322f96/content.htm.
http://help.sap.com/saphelp_40b/helpdata/ru/52/16abcf543311d1891c0000e8322f96/content.htm
I can think of few more, like In external system after generating Idoc, save it as a tex and send it to SAP system using Http post or using web service.
Look out to below discussion.
Send IDoc from External System to SAP system
Regards
Aashish Sinha
Edited by: Aashish Sinha on Feb 28, 2011 1:16 PM

Is it Possible to send IDOCs from one system to itself?

Similar Messages

Maybe you are looking for