on 04-19-2008 8:40 AM
Hello,
Could you give me clarity whe ever we are sending the Idoc at sender system to reciever system, how can we identify the DT and MT and MI for this as sender system. Because we dont create it.
Thank you
Hi
IDOC structure we can directly import from R3 using the import tool available in IR .
The imported structure is eqivalent to MI, you can see the wsdl after import.
So you are importing IDOC structure
(as MI) so no need to create DT, MT & MI
Arun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey
IDOC itself is a message interface,hence there is no need to creating DT,MT or MI for and IDOC.
Every IDOC has an underlying Message type encapsulated within itself.
lets take for example ORDERS IDOC.
The IDOC name(Message interface) is ORDERS.ORDERS05 and the message type is ORDERS.
since you are getting all this information by importing IDOC itself hence there is no need of creating DT,MT or MI.
But in case you need to use IDOC in a BPM,then you need to create a abstract MI for the IDOC.
Thanx
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jyotsna,
IDOC is a structure itself and you use the mapping that tells the types that has to be mapped with target structure. XI will directly taken care of the type and its message transformation.
Regards
Vinod V
*
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For IDoc, we get the Message Type in repository. So we can skip creation of DT and MT. As these are taken from R/3.
We build Message Interfaces from those Types ( IDoc or RFC ) which will be actually imported from R/3 end.
and with this Message Interface mapping and transformations are done.
hope you understood.
nikhiL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
since we are not specififing the direction like in MI, how will the system know that idoc is used for outbound or inbound.
regards
raghu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Here we will use the IDOC name Directly in case of Mapping and Interface Mapping.
When you fired the IDOC from SAP R/3 means it will pass through Partner Profile--Port---RFC Destination and reach XI.
Then the corresponding Interface will be triggered and executed.
This is the flow
Regards
Seshagiri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
When u do message mapping u directly use the IDOC strucutre. so no need to define the DT,MT,MI for IDOC.
For IDOC interface we have to perfom certain configuration on R3 as well as on XI side.
configuration like:
RFC destination which points to XI if ur scenario is R3 to XI.
port
reverse case XI to R3.
RFC destination pointing to R3
port using IDX1 tcode.
just refer the below link which will give u more idea.
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)&
chirag
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.