on 08-19-2006 5:47 AM
hello all,
i am reltively very much new to XI, a have some knowledge on BC. Thing is that i am able to identify different objects in integration repository, where as in integration builder if i get different messages from different servers wether R/3 or some third party, how does the XI identify to which Reciver determination it should pass the message 'where do we configure these things' and also any documentation about what sytem landscape does exactly.
it would be great if some one could help me regarding
thanks in advance.
raju N
Hi Raju,
<b>Receiver Determination</b> is a configuration object in SAP Exchange Infrastructure that
describes the assignment of a sender interface and an outbound interface to one or more receivers.
Within a receiver determination it is also possible to define conditions for forwarding a message to different receivers.
Logical routing is defined by both receiver determinations and interface determinations.
Kindly check the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
In the above link goto SAP Exchange Infrastructure -> Configuration -> System Landscape Directory in SAP Exchange Infrastructure
SDN elearnings link:
https://www.sdn.sap.com/irj/sdn/elearn?rid=/webcontent/uuid/a680445e-0501-0010-1c94-a8c4a60619f8 [original link is broken]
Check the following SDN thread:
Kindly reward points for useful answers!
Best Regards,
Thangesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raju,
<u><b>SLD:</b></u>
The System Landscape Directory of SAP NetWeaver (SLD) serves as a central information repository for your system landscape. A system landscape consists of a number of hardware and software components that depend on each other with regard to installation, software updates, and demands on interfaces.
- so talking about the working of an SLD, here if any information is required for the integration server regarding the systems(logical or physical) and the software (installed products) it refers to the SLD.
- to tell you about the other features it has....it captures the dimensions of the system landscape like solution dimension, transport dimension and technical dimension.
- putting it in short XI IS A CLIENT OF SLD
Also go thru this link and understand more about SLD <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/31/f0ff69551e4f259fdad799a229363e/frameset.htm">System Landscape Directory</a>
<u>
<b>SOFTWARE CATALOG:</b></u>
The SLD contains a Software Catalog of all installable SAP products and software components. The Software Catalog includes information about support packages and dependencies between the products and software components. This information is the basis for the description of the system landscape.
Also go thru this link and understand more about Software Catalog <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/a2/2999ef97ea2b4790165f9ca5c05c41/content.htm">Software Catalog</a>
<u><b>TECHNICAL SYSTEM, BUSINESS SYSTEMS, SOFTWARE PRODUCTS:</b></u>
Technical system correlates the software to the physical host on which it is installed
Or in other words Technical systems are application systems that are installed in your system landscape.
- they are actually the basis for defining the business systems.
- we assign a technical system to a business system to help the SLD make the appropriate association.
- the software products used by the business system are got from the technical system definition.
- to note 1 technical system can have more than one business system assigned to it....and as told the SLD make the appropriate association between them.
Also go thru this link and understand more about each of it:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm">Technical Systems</a>
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/42/c817d9d2296bb2e10000000a1553f6/content.htm">Business Systems</a>
<a href="/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation Preparation</a>
Regards,
Abhy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raju,
In the Configuration we create Sender Agrement, Receiver Determination,etc,etc.
Firstly senderAgreement gives information about the sender like sender interface, Communication Channel used.
In the receiver determination ...we specify the possible receivers based on the sender service & sender INterface.
So XI comes to knw of the receiver from the receiver agreement.
Cheers,
Sumit
hello thomas,
your views helped me a lot but the main thing is that, if i receive two different IDOCS from two different R/3 system. how do the xi system identify which document need to be send to which receiver determination. do we need to do any kind of routing in the integration server(i would like to know the exact process that works out there) and the other thing is that i have send a IDOC from R/3 systems.i didnt do anything in design time or configuration time just created RFC destination. created port in idoc adapter. where can i find the idoc i had sent.
thanks,
raju N
Hi ,
<i>i didnt do anything in design time or configuration time</i>
You have to import your IDocs from different R/3 systems into XI using Import Objects option under SWC in design time and also need to do nessessary mappings in design time...in IR.
<i>how do the xi system identify which document need to be send to which receiver determination</i>
You have to do the nessasary configuration like routing rules and reciever determinations....in ID
Check this thread for reference.....
sekhar
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.