Regarding IDOC- XI3.0- IDOC scenario

Hi All,
Does anybody have IDOC->XI3.0->IDOC scenario.
I am new to XI. I am into ABAP mainly. Now i need to work on above scenario in XI 3.0.
I need to do the processing for IDOC->XI3.0->IDOC scenario using Sales order Idocs. Where Message type: ORDERS & Idoc type: ORDERS05.
My source and target systems are
Source systems: 1) BW , 2) APO
Target systems: SAP R/3
If anybody has done this scenario previously help me in this regard.
Can anybody send me the above scenario screen shots in XI 3.0 if done prviously.
My Mail ID: [email protected]
Thanks in advance.
Anyhelp in this regard is appreciated.
Thanks & Regards,
Deep.

Hi Deep,
Looking at your requirement, it looks like you are having two senders which means that you will have to use BPM to get the data from both of them simultaneously. In BPM, create two receivers for your two source systems. You will have to make sure that in the namespace, you enable import of RFCs and IDOCs by checking the box present at the scv level. Also you need to provide the details over there. the system is basically your <sid> and the clinet is the one you want to connect to to get the objects from. Then you will have to import the rfc/idoc in to the IR. In the namespace in which your integration process is, you will have to create two outbound interfaces and an inbound interface using the rfc/idoc you have imported. you will also need to create an abstract interface (it is sufficient if you just create 1 if you do not have any mapping in between and if your source and target structures remain intact). Even if you are having mapping, i feel that since you are going to send in a standard idoc, the strcuture remains constant. hence only 1 abstract interface should do. Now since you are having two sources, i assume that you are going to append the data from both the idocs in to 1 single idoc. In this case, you will need to create a message mapping and then in the messages, select both the source idocs. and also select the target one. Perform mapping. Create an interface mapping accordingly. use this in the BPM transformation. Finish the BPM.
Then in the configurations, i assume that you would be defining these two systems as business systems (as they will be in the SLD). you will have to provide the adapter specific identifiers. Finish the configuration as you would do for any BPM scenario.
That should do....there would be some other changes which you will have to do it for yourself. But in most cases, these seetings should work fine. also please keep in mind that you will have to import the meta data IDX2, and define ports in IDX1.
This is just teh XI part
Reward if hepful,
Sarath.

Similar Messages

Regarding receiver determination problem in IDOC-XI-XML file scenario

Dear All ,
In IDOC-XI-xml file scenario , I have configured SLD , IR . But in ID , after file adapter , reciever agreement configuration when I am doing receiver determination configuration I am not able to insert mapping program in configuration overview of receiver determination as I am not getting "New Specific" option in mapping .
Can anybody suggest what could be the reason behind this .
Thanks in Advance
Prabhat

Hi PRabhat,
In RCVR determination, you need to select the party & service (as appropriate) save the obeject
then refresh the configuration overview of recr det.
then you can see the partner/service
then you can open it & add the necessary objects.
Regards
Vishnu

Doubt regarding ALE SETTINGS in IDOC scenario.

Hi Friends,
        I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
                                                   --- TRFC PORT for sending IDOC to the XI system
                                                   --- CREATING LOGICAL SYSTEM
                                                   --- CREATING PARTNER PROFILE
               at the XI side is --- RFC Destination ( For SAP sender system)
                                       --- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
                                                                                FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.

hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
    R3 RFC destination points to Xi and
    XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
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)
     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 6)
     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.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
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

HTMLError in sxmb_moni, Idoc to ABAP Proxy Scenario

Hi Friends
I am trying to send data from R3 to SCMTM system(SAP System), via Idoc to ABAP Proxy Scenario ,I am getting the following under HTMLError in sxmb_moni
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED) (See attachment HTMLError for details)</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
Any ideas will be helpful.

Hi,
I faced similar problem. it was due to configuration problem in SXMB_ADM. corss check specific server confiration in SXMB_ADM.
/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
Regards,
Reyaz

IDoc to Flat file scenario - abap mapping

Hi All,
I have to do some IDOC to Flat file scenarios. In Order to generate the file in required format I will have to add all segments(Nodes) of Idoc in FCC receiver. We also have other option of doing it through ABAP Mapping which I found in one blog.
Now my question is : Is it better way of doing it through FCC or ABAP Mapping?
Ofcourse from development point of view ABAP Mapping looks easier as FCC is very time consuming task.
Is there and performance issues in either of the approach?
Thanks and Regards,
Atul

Hi VJ and Harald,
Thanks for your replies.
I am not having PI7.1 however the given blog was very informative.
I will try using file port approach as suggested.
Thanks and Regards,
Atul

IDoc to soap synchronous scenario with BPM

Hi,
I am working on IDoc to soap synchronous scenario using BPM. Here i am facing lot of soap exceptions in my production system. I handled the exceptions. The data getting excuted for the first time, the same data(just changed the description)is giving exceptions for the second time. Please let me know why the exceptions are getting, and different type of exceptions and solutions for the same.(Blog also is fine)
Thanks & Regards,
Pragathi.

The data getting excuted for the first time, the same data(just changed the description)is giving exceptions for the second
time.
Ideally you should not get an exception for the same data....can you tell is the description and where are you getting the exception...is it a part of the SOAP message or some object?
An exception might have occured because the description would be something unacceptable by the target application.
and different type of exceptions and solutions for the same
there would be many blogs....your thread would be spammed...better make a search on SDN with exception text that you are getting.
Regards,
Abhishek.

Multiple IDOC to Multiple IDOC scenario without BPM steps????

Hi
Could you please give me the solution for this ???
I want steps for sending all IDOCs at a time- ---"Multiple IDOC to Multiple IDOC scenario without using BPM".???
thanks
3nadh

Hello,
Refer the below, for certain details!
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi ALE configuration for pushing idocs from SAP to XI
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change XI: IDOC bundling - the "trick" with the occurance change
Regards,
Jilan

IDOC to XML SOAP Scenario

Hi All,
I want to implement IDOC to XML SOAP scenario for 3 different IDOC types.
Should i implement it under same namespace or use different namespace for each IDOC to XML scenario.
Thanks,
Vishal

Hi,
depends on your requirement and your XML SOAP receiver
there are no general rules
Regards,
Michal Krawczyk

IDOC to WS Synchronous Scenario Without BPM

Hi Experts,
I am dealing with Idoc to WS synchronous scenario. Can this be done without BPM??
ALEAUD can make IDOC to handle WS response??
Please suggest.
Regards,
Sushama

Please suggest since BPM involves performance issue
BPM surely has performance issue...only when there are a lot of steps/ logic implemented in it and when the processing load is too much for the XI/ PI server to handle.
The BPM design in your case will be just of following steps: Receive --> SyncSend --> AsyncSend .... excluding Transformation...and a BPM with these steps wont cause a big harm to processing of other messages.
Regards,
Abhishek.

IDOC to JDBC -- B2B scenario

Hi,
What are the Adaptors used for a B2B scenario to send an IDOC from R3 system to an Oracle database.
Thank You!

Hi San,
what Nikhil suggested is right
In Addition to above
Check this link for IDOC Configuration
Configuring IDOC
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
and this for Recieving JDBC adapter
http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
Reward if helpful
Regards
Sachin

ALE IDOC to XML IDOC scenario using XML port

Hi,
I am working on ALE IDOC to XML IDOC scenario using XML port . The requirement is to place a XML IDOC on the application server using ALE IDOC scenario ( output type is created in NACE which is ALE enabled ).
Can anybody help me on the steps.
Regards
Kumar
Moderator message: please search for available information/documentation.
Edited by: Thomas Zloch on Sep 8, 2011 6:01 PM

U can give a try as follows.
In the Partner Profile of Sender R/3 system,
Give the Receiver Party P_Party in the PartnerNo. Give the 'Business Partner' as logical System type.
In XI, Party Definition of P_Party
Give the following Alternative Identifier
Agency -   Sender R/3 Business System
Scheme -   ALE#GP
Value    -    P_Party

IDOC to websevice (SOAP) scenario

Hi Experts
I have a IDOC to SOAP scenario, i have searched for the step to step guide in SDN, but could not find it
Please let me know the step to step process for a IDOC to (webservice) SOAP scenario, like DT, MT etc.. and further steps
Regards
Lara

Hi Vijay
Thanks for the info shared.
below are the points observed from the links
My Scenario:
Source : IDOC
Target : SOAP
mode : Asynchronous
1. Import the IDOC which will be used in the message mapping at the source side
2. Create SOAP Datatype, Message Type, Service Interface.
3. Imoport the IDOC in message mapping and the SOAP message type that we have created in the above step
4. Operations Mapping and activate the scenario (same as normal idoc to file scenario)
5. Create Integration Scenario, SOAP Receiver Communication channel, Receiver Agreement, Receiver Determination, Interface Determination
Please let me know if anything else am I missing in this scenario
Regards
Lara

Idoc to web services scenario

Hi
Can any one send me material for idoc to web services scenario to my mail id [email protected] or any good links to download material
Regards
Pavan

How to Develop a Webservice Using NWDS and SAP XI.30
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5f3ee9d7-0901-0010-1096-f5b548ac1555
How to Set Up a Web Service-Related Scenario with SAP XI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/befdeb90-0201-0010-059b-f222711d10c0
How to Configure the IDoc Adapter
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
How to Sample IDoc Scenarios Within XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660

Regarding Creation of Custom IDOC

Hi,
This is Abdullah Shaik. I want to create an IDOC from the existing IDOC. Some times I need to add some segments to the existing IDOC. Can anybody plz let me know the process how to create the Customized IDOC from the Standard IDOC?
Thanks & Regards,
Abdullah shaik.

Hi Abdullah,
There are basically two types of IDOCs:-
Basic IDOCs and Extended IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDOC
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Go thro' this link:-
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
I hope this provides you a solution.
Regards.
Praveen

Doubt while importing idoc (file 2 idoc scenario)

hi,
In IR, Imported objects..>Idocs
while importing idoc there are two options to import
according to software componet version,
Overwrite sever info temporarily
which one i have to use ? what circumstances i have to each option?

Praba,
Also please check this SAP help for the difference between these two:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
Regards,
---Satish

Regarding IDOC- XI3.0- IDOC scenario

Similar Messages

Maybe you are looking for