on 02-16-2010 7:14 AM
Hi folks,
Can anyone explain why to import RFC and IDOC objects from the R/3 system to which we are communicating. Is the reason is only due to its complex datatype structure.? Then why do they have different NAMESPACE, and how/when it is generated.?
Correct me if i am wrong.
Thanks,
Srinivas Reddy.
R/3 & PI both systems works on ABAP Stack during these communications.
We need interface for R/3, so we can use structure of IDoc & RFC, exists on R/3 system.
If you will create your own structure, it is difficult.
Also you will define that structure on R/3 also, as at that time R/3 does not know your structure.
So it is easy to use existing structures of RFC & IDoc.
Namespaces are system generated. These depends on object & its version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For RFC: urn:sap-com:document:sap:rfc:functions
For IDOC: urn:sap-com:document:sap:idoc:messages
The namespaces are standard and fixed for RFC and IDOC respectively and are related to the formats in the SAP ECC system, nothing is done for this in XI/ PI.
If you have an ABAP counterpart working with you, then you can actually get the process known from him/ her.
Regards,
Abhishek.
Hi Srinivas,
>>Can anyone explain why to import RFC and IDOC objects from the R/3 system to which we are communicating. Is the reason is only due to its complex datatype structure.? Then why do they have different NAMESPACE, and how/when it is generated.?
Because they have
1. SAP specific namespace.
2. complex structure
3. Easily available (and hence to import rather than re-create)
Regards
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
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.