TREX as an Technical System in the SLD

Via the sldreg my TREX instance is entering it's information into the SLD. But now I have to add my TREX instance to a technical system in the SLD.
Normally an ABAP or a Java system registers itself into the SLD with a technical system, but TREX doesn't do this
How do I add my TREX instance to a technical system in the SLD?

may be you can check whether the sld data supplier is updating the data or not
http://help.sap.com/saphelp_nw04s/helpdata/en/8a/361fb70681234fb7d3af841ec2383e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ea/cd2e807e0e45bf9da67354f452fc05/content.htm
and for ABAP, can be checked in RZ70
http://help.sap.com/saphelp_nw04/helpdata/en/ea/cd2e807e0e45bf9da67354f452fc05/frameset.htm
In system B's sld, check whether an sld is added towards the SLD server of C

Similar Messages

SAP XI 3.0 - Error while reading the ID of own business system from the SLD

Error while reading the ID of own business system from the SLD for system Quality (QOC) and Client 100.
I get this error in the SXMN_MONI. The business process is that the Interface to send master schedule and finished inventory from the legacy system to SAP to create planned orders in SAP for all Plants.
I could able to get "SUCCESSFULLY PROCESSED" in development and production. But only in Quality I getting this error. Could anyone help me to fix this issue.
thanks...

Probably, its due to incorrect RFC Adapter properties in config.
Go to Integration COnfiguration. Double Click on the Business System for your R/3 system. On the right hand screen, Click on Service-->Adapter Specific Parameters.
Check whether the Logical System Name comes up as SAP<SID> and whether R/3 system ID and Client are appropriate.
If these values are inappropriate, make changes to the corresponding Technical System defined in the SLD. After you have made the necessary corrections, come back to Integration COnfiguration, Double click on Business SYstem for R/3. Switch to Edit Mode. Click on Service-> Adapter Specific Parameters and then click on the Icon between Apply and Cancel buttons, inorder to compare with SLD and make those values reflect in config. Then click on Apply and Save the Business System.
After this, you can retry sending the message.
Rgds
R Chandrasekhar

Error while reading the ID of own business system from the SLD for system

Hello,
I try to send master material data from a 4.7 system via XI 3.0 to an autoID Infrastructure system 2.1. All Communication Channels, Receiver Agreements, Receiver and Interface Agreements are configured. The IDOC gets propper into the XI, Inbound Message is "green". Now, I get the following message:
<?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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>ZTA</SAP:P1>
<SAP:P2>013</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading the ID of own business system from the SLD for system ZTA and client 013</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anybody help me?

Probably, its due to incorrect RFC Adapter properties in config.
Go to Integration COnfiguration. Double Click on the Business System for your R/3 system. On the right hand screen, Click on Service-->Adapter Specific Parameters.
Check whether the Logical System Name comes up as SAP<SID> and whether R/3 system ID and Client are appropriate.
If these values are inappropriate, make changes to the corresponding Technical System defined in the SLD. After you have made the necessary corrections, come back to Integration COnfiguration, Double click on Business SYstem for R/3. Switch to Edit Mode. Click on Service-> Adapter Specific Parameters and then click on the Icon between Apply and Cancel buttons, inorder to compare with SLD and make those values reflect in config. Then click on Apply and Save the Business System.
After this, you can retry sending the message.
Rgds
R Chandrasekhar

Error while reading ID of own business system from the SLD

HI guys when trying to send Idoc from my R/3 system to SUS i am getting the following error in XI
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>DSM</SAP:P1>
<SAP:P2>900</SAP:P2>
<SAP:Stack>Error while reading ID of own business system from the SLD for system DSM and client 900</SAP:Stack>
I checked in sxmb_adm on both the ends on Xi as well as on my SUS server in Xi the role is the Integration server and on the SUS it is Application server also checked SLDAPICUST which is configured rite. Plz help me to come out of the problem.
Regards,
Anand

Hi Anand,
check the two thing's in XI.
1. First created technical system in XI to identify your XI server (Web as ABAP and Web AS Java)
2. Create the business system based on above technical system and select the role of business system is Integration server.
URL : http://<hostname>:<ICM Port>/sap/xi/engine?type=entry.
3. Create the technical system based on your SAP R/3 system.
4. Create the business system based on your SAP R/3 system.
here you need to select role of business system : Application system.
related integration server is : <XI System SID has to come>
and try to refresh the initical cache once ...
http://<hostname>:<j2ee stack port>/CPACache/refresh?mode=full
after all the things post what is the problem you are faceing.
Regards,
Venu.

Creating a Business system in the SLD

I am receiving an error message when trying to create a business system in the SLD. The error is "The selected client has an associated logical system nae that is already used for another business system. Select a different client."
Here is my issue. The business system that I am creating is for our R/3 4.6C production system. I currently have a business system for our R/3 4.6C quality system. Our prodution and quality R/3 systems do have the same logical system name and client number. This is because we recreate our qaulity R/3 system from our production system.
So, the question is, How do I create a business system in the SLD for my production R/3 system when the logical system name is used assoicated with and business system.
I should add that all my R/3 systems have been created as technical systems without any problems.
Thanks,
Jim

It is recommended to have all ALE names unique.
If it is not possible the following workaround can be used.
Create one system in SLD (business system/technical system) which contains the ALE name. Proposal: The production system
Create the other systems(dev/QA) without the ALE name
During configuration the production system will be configured as usual.
For Dev/QA systems: Define in the receiver agreement the header mapping and use The Receiver service to reference the production system. Because you reference the production system the ALE name of the production system will be used to fill the idoc.

Import technical system details into SLD

HI ,
I was looking for the way to import the technical system data for a SAP R/3 system into the SLD .
Is there a automated way of doing this or do we have to key in the details .
Thanks
Nikhil

Yes. It will import the all the details. The RZ70 has an option to run a batch job for every 720 minutes ( 12 hrs. you can change this). That means for every run, if there it will update all the components it has. No need of manual work.
Connection Between Web AS ABAP Systems and SLD
http://help.sap.com/saphelp_nw2004s/helpdata/en/21/84570b3ae14e77b3047c82218974b9/frameset.htm
If you do not see your Technical System in SLD, then troubleshoot with the following link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
Regards
Shravan
Message was edited by: Shravan Miryala

Error while reading ID of own business system from the SLD for system D18

Dear guru's,
I have almost completed a file2proxy scenario but I'm stuk on the following.
When sending a message the outbound adapter says:
<b>Error while reading ID of own business system from the SLD for system D18 and client 200</b>
What's the problem? I'm using a HTTP connection in the comm. channel. In this http connection a user with SAP_ALL is defined.
Any suggestions?
<?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="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>D18</SAP:P1>
<SAP:P2>200</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading ID of own business system from the SLD for system D18 and client 200</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Login to system D18 and client 200 and check the TC SLDCHECK and also as per my pervious message check the entries in the SLDAPICUST, it should point to the Server on which SLD is present usually XI server https.
Actually what happens in this error is when you are done with the configuration part in the ID, you are trying to eceute the scenario File to proxy, when it comes to identify the receiver system which is D18 clnt 200, it goes to SLD to check it and SLD is trying to ping to the machine D18 this connection is set from the TC SLDAPICUST on the machine D18.
here the problem is that either the D18 is not able to ping to the SLD and also try refreshing the SLD cache.
Hope you problem is fixed

Error while reading ID of own business system from the SLD for system DPI

Hi All,
My sceanrio is Proxy to JDBC. and its B2B. am sending the data from BI system and based on the country field from the source, table is decided and value is updated in the table.
In RWB->Component Monitoring->Adapter Engine->Test Message, I have given the Sender component,Receiver Party,Receiver component,Interface,Interface Namespace,userid and password,Quality of Service and pasted the payload.
Now I am getting the error :Error While Sending Message: Error stack from response: Error while reading ID of own business system from the SLD for system DPI and client 001 Internal error in Landscape Directory
Please help me out.
Thanks
Kiruthi
Edited by: kiruthiga balusamy on Nov 24, 2009 4:02 PM

Hi,
Check transaction SLDAPICUST for correct SLD configuration.
http://help.sap.com/saphelp_nw70/helpdata/EN/0b/8512417301ee6fe10000000a1550b0/content.htm
~Sanv...

Error when reading the ID of the business system from the SLD

Hi,
I am working on a scenario JDBC - XI - BW (ABAP Proxies). I configured all the steps required to connect XI & BW systems. The SLDCHECK transaction is all green. I was able to connect to SLD from BW using SXMB_IFR tcode too. I was able to look at all the XI Repository interfaces from SPROXY tcode in BW. Created a new ABAP proxy (class interface and method) for the message interface in XI from BW (SPROXY Tcode). Created all required config in XI Directory. Got the message from JDBC adapter, mapping done successfully, and the message failed in the CALL Adapter Step.
The error is "Error when reading the ID of the business system from the SLD for system BWS and client 100."
What could have gone wrong. Thanks in advance.
Srini

Hi,
:::::::One Should Have the Following Roles AS A XI Developer With Out Admin Rights ::::::
1) SAP_XI_Developer_ABAP +
2) SAP_XI_Developer_J2EE +
3) SAP_XI_MONITOR_ABAP +
4) SAP_XI_MONITOR_J2EE +
5) SAP_SLD_ADMINISTRATOR +
6) SAP_XI_BPE_MONITOR_ABAP +
7) SAP_XI_DEMOAPP
8) SAP_XI_DISPLAY_USER_ABAP +
9) SAP_XI_DISPLAY_USER_J2EE +
Regards
Sesh

SLD Error in IE:Error while reading ID of own business system from the SLD

Dear Champs,
Scenario : JDBC to Proxy(APO system)
We are getting below error in MONI UAT Box. All other interface are working fine but we are facing issue for a particular Bussiness System also logical system are maintained properly.the same interface is working fine in other UAT box.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SLD_NO_OWN_BS</SAP:Code>
<SAP:P1>R/3 Sys ID</SAP:P1>
<SAP:P2>"Client"</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading ID of own business system from the SLD for system "R/3 Sys ID"and client "Clnt no"</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards,
Manikandan

Hi Mani,
Solution 1:
Check if the techncal system has associated Business system. I think there is something wrong in your SLD configuration and try to correct it.
Solution 2:
Create a Business system in the ID, and create the communication channel do the respective changes in ID ( I.e Receiver agreement, Receiver determination & Interface).

How to delete replicated system in the SLD

Hi Experts.
How to delete the replicated systems in the SLD.As i m following note 1042815.
Regards
Ashok

Hi Ashok
I have to assume the system you are trying to delete is one that you manually added to SMSY which ended up in SLD due to the Write Back option
If however you do find the system re-appears do check that it is not registered directly in the SLD via RZ70
Best wishes
Stuart

Buisness system can not find the relevant technical system in xi sld

Hello,
I set up r3 business system and technical system landscape in xi SLD, somehow the business system cannot find the relevant system landscape, does anybody have any suggestions what's possiblly goes wrong in my sld setting or how should I debug?
Thanks,
Meg

Hey,
Well did you create the technical system or was it created or used before>? Unless it was done you can't create Business System for the specified technical system.
Cheers,
<b>*RAJ*
*REWARD POINTS IF FOUND HLEPFULL*</b>

No products installed while adding a Technical ABAP System in the SLD.

Hello,
I am trying to add Technical Systems in SLD. when I was at the point to select the software components, I am not seeing any installed products on the left side.
I already gave the ABAP system details in the previous screens, in this wizard.
Why is it that I am not seeing any installed products.
Thanks
Srinivas

Hello,
When I import the cimsap41510_0-10006428.zip file, I get the following errors.
Import finished with 72 erros.
Errors:
CIM_ERR_FAILED: CIM qualifier Alias is currently not supported by this implementation
QUALIFIER.DECLARATION Alias
CIM_ERR_FAILED: CIM qualifier BitMap is currently not supported by this implementation
QUALIFIER.DECLARATION BitMap
CIM_ERR_FAILED: CIM qualifier BitValues is currently not supported by this implementation
QUALIFIER.DECLARATION BitValues
CIM_ERR_FAILED: CIM qualifier Composition is currently not supported by this implementation
QUALIFIER.DECLARATION Composition
CIM_ERR_FAILED: CIM qualifier Counter is currently not supported by this implementation
QUALIFIER.DECLARATION Counter
CIM_ERR_FAILED: CIM qualifier Delete is currently not supported by this implementation
QUALIFIER.DECLARATION Delete
CIM_ERR_FAILED: CIM qualifier Deprecated is currently not supported by this implementation
QUALIFIER.DECLARATION Deprecated
CIM_ERR_FAILED: CIM qualifier DN is currently not supported by this implementation
QUALIFIER.DECLARATION DN
CIM_ERR_FAILED: CIM qualifier Expensive is currently not supported by this implementation
QUALIFIER.DECLARATION Expensive
CIM_ERR_FAILED: CIM qualifier Experimental is currently not supported by this implementation
QUALIFIER.DECLARATION Experimental
CIM_ERR_FAILED: CIM qualifier Gauge is currently not supported by this implementation
QUALIFIER.DECLARATION Gauge
CIM_ERR_FAILED: CIM qualifier Ifdeleted is currently not supported by this implementation
QUALIFIER.DECLARATION Ifdeleted
CIM_ERR_FAILED: CIM qualifier In is currently not supported by this implementation
QUALIFIER.DECLARATION In
CIM_ERR_FAILED: CIM qualifier Invisible is currently not supported by this implementation
QUALIFIER.DECLARATION Invisible
CIM_ERR_FAILED: CIM qualifier Large is currently not supported by this implementation
QUALIFIER.DECLARATION Large
CIM_ERR_FAILED: CIM qualifier MaxValue is currently not supported by this implementation
QUALIFIER.DECLARATION MaxValue
CIM_ERR_FAILED: CIM qualifier MinLen is currently not supported by this implementation
QUALIFIER.DECLARATION MinLen
CIM_ERR_FAILED: CIM qualifier MinValue is currently not supported by this implementation
QUALIFIER.DECLARATION MinValue
CIM_ERR_FAILED: CIM qualifier Nonlocal is currently not supported by this implementation
QUALIFIER.DECLARATION Nonlocal
CIM_ERR_FAILED: CIM qualifier NonlocalType is currently not supported by this implementation
QUALIFIER.DECLARATION NonlocalType
CIM_ERR_FAILED: CIM qualifier NullValue is currently not supported by this implementation
QUALIFIER.DECLARATION NullValue
CIM_ERR_FAILED: CIM qualifier Octetstring is currently not supported by this implementation
QUALIFIER.DECLARATION Octetstring
CIM_ERR_FAILED: CIM qualifier Out is currently not supported by this implementation
QUALIFIER.DECLARATION Out
CIM_ERR_FAILED: CIM qualifier PropertyUsage is currently not supported by this implementation
QUALIFIER.DECLARATION PropertyUsage
CIM_ERR_FAILED: CIM qualifier Provider is currently not supported by this implementation
QUALIFIER.DECLARATION Provider
CIM_ERR_FAILED: CIM qualifier Read is currently not supported by this implementation
QUALIFIER.DECLARATION Read
CIM_ERR_FAILED: CIM qualifier Schema is currently not supported by this implementation
QUALIFIER.DECLARATION Schema
CIM_ERR_FAILED: CIM qualifier Source is currently not supported by this implementation
QUALIFIER.DECLARATION Source
CIM_ERR_FAILED: CIM qualifier SourceType is currently not supported by this implementation
QUALIFIER.DECLARATION SourceType
CIM_ERR_FAILED: CIM qualifier Static is currently not supported by this implementation
QUALIFIER.DECLARATION Static
CIM_ERR_FAILED: CIM qualifier Syntax is currently not supported by this implementation
QUALIFIER.DECLARATION Syntax
CIM_ERR_FAILED: CIM qualifier SyntaxType is currently not supported by this implementation
QUALIFIER.DECLARATION SyntaxType
CIM_ERR_FAILED: CIM qualifier Terminal is currently not supported by this implementation
QUALIFIER.DECLARATION Terminal
CIM_ERR_FAILED: CIM qualifier TriggerType is currently not supported by this implementation
QUALIFIER.DECLARATION TriggerType
CIM_ERR_FAILED: CIM qualifier UnknownValues is currently not supported by this implementation
QUALIFIER.DECLARATION UnknownValues
CIM_ERR_FAILED: CIM qualifier UnsupportedValues is currently not supported by this implementation
QUALIFIER.DECLARATION UnsupportedValues
CIM_ERR_FAILED: CIM qualifier Write is currently not supported by this implementation
QUALIFIER.DECLARATION Write
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property ScheduledStartTime
CIM_Job
CIM_ERR_FAILED: Unknown qualifier Write found in property DeleteOnCompletion
CIM_JobSettingData
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_ConcreteJob: CIM_Job
CIM_ConcreteJob
CIM_ERR_FAILED: Unknown qualifier Write found in property EnabledDefault
CIM_EnabledLogicalElement
CIM_ERR_FAILED: Unknown qualifier Write found in property PrimaryOwnerName
CIM_System
CIM_ERR_FAILED: Unknown qualifier Write found in property PrimaryOwnerName
CIM_Service
CIM_ERR_FAILED: Unknown qualifier Gauge found in property AvailableSpace
CIM_FileSystem
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property array PowerManagementCapabilities
CIM_ComputerSystem
CIM_ERR_FAILED: Unknown qualifier Gauge found in property NumberOfUsers
CIM_OperatingSystem
CIM_ERR_FAILED: Unknown qualifier Gauge found in property FileSize
CIM_LogicalFile
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property PowerManagementSupported
CIM_LogicalDevice
CIM_ERR_FAILED: No such override property in superclass CIM_System: EnabledState
CIM_ApplicationSystem
CIM_ERR_FAILED: Unknown qualifier Gauge found in property WorkingSetSize
CIM_Process
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_LogicalPort: CIM_LogicalDevice
CIM_LogicalPort
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_Processor: CIM_LogicalDevice
CIM_Processor
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_NetworkAdapter: CIM_LogicalDevice
CIM_NetworkAdapter
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_NetworkPort: CIM_LogicalPort
CIM_NetworkPort
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_OSProcess
CIM_OSProcess
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_FRUIncludesProduct
CIM_FRUIncludesProduct
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_ProductParentChild
CIM_ProductParentChild
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_FileStorage
CIM_FileStorage
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class CIM_ProvidesServiceToElement
CIM_ProvidesServiceToElement
CIM_ERR_FAILED: Class CIM_OperatingSystem referenced by association CIM_RunningOS does not exist.
CIM_RunningOS
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_SystemDevice
CIM_SystemDevice
CIM_ERR_FAILED: Class CIM_OperatingSystem referenced by association CIM_BootOSFromFS does not exist.
CIM_BootOSFromFS
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property CompiledBits
SAP_BCApplicationServer
CIM_ERR_FAILED: Unknown qualifier STATIC found in property AccSldModelVersion2
SAP_ACEEngine
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class SAP_ACENetworkInterface: CIM_NetworkPort
SAP_ACENetworkInterface
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class SAP_JCODestination
SAP_JCODestination
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class SAP_MsgServJCODestination
SAP_MsgServJCODestination
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class SAP_AppServJCODestination
SAP_AppServJCODestination
CIM_ERR_FAILED: Class SAP_ACENetworkInterface referenced by association SAP_ACENetworkToNetworkInterface does not exist.
SAP_ACENetworkToNetworkInterface
CIM_ERR_FAILED: Class SAP_ACEEngine referenced by association SAP_ACEAssociatedVirtualizationManager does not exist.
SAP_ACEAssociatedVirtualizationManager
CIM_ERR_FAILED: Class SAP_ACEEngine referenced by association SAP_HostedACEEngine does not exist.
SAP_HostedACEEngine
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class SAP_ACENetworkInterfaceComponent: CIM_SystemDevice
SAP_ACENetworkInterfaceComponent

Technical system in client SLD is not updated in master SLD

Hi,
We are running on PI 7.0. We have 2 SLDs in (system A and system B) and both the SLD's are connected with additional SLD (system C). System C' SLD dont have system B's technical system for Web AS JAVA at all and Web AS ABAP only last updated on 03/05/2009. What and where I should check on the configurations if anything is missing. System A's techincal system are being updated daily to system C's SLD.
Thanks.
Regards,
Thava

may be you can check whether the sld data supplier is updating the data or not
http://help.sap.com/saphelp_nw04s/helpdata/en/8a/361fb70681234fb7d3af841ec2383e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ea/cd2e807e0e45bf9da67354f452fc05/content.htm
and for ABAP, can be checked in RZ70
http://help.sap.com/saphelp_nw04/helpdata/en/ea/cd2e807e0e45bf9da67354f452fc05/frameset.htm
In system B's sld, check whether an sld is added towards the SLD server of C

How PI uses technical system information in SLD

Hi Experts,
I know there are business system and technical system registered and associated in SLD.
Especially for those SAP systems, in our normal PI scenario, how PI uses the technical information which was registered under Technical System in SLD since we need again configure the host/port and credentials details in the sender/receiver channel in ID.
Or SLD is just one central place for collecting all the technical information together only for life cycle management?
There is nothing more to do with the Tech System (SLD), PI only needs the business system in scenario.
Please knidly share your opnion, thanks in advance.
Best Regards,

Hi Aditya,
Let me provide an example to describe the need fot technical systems.
Think of an outbound scenario : SAP ECC/CRM -> PI -> Third Party (ex: SOAP)
Now just think how PI will identify what the sender is (ECC/CRM or 3rd party) if the TS is not registered in SLD? The Business Systems are logical systems whcih points to Technical Systems (application systems that are installed in system landscape). TS hold the information about the actual systems, its host, IP, clients etc.
Now based on the source BS which points to TS, the target binding is done in Receiver Determination pipeline step. Now if there is no TS attached to the BS how can PI identify whether ECC or CRM is sending the data and hence will not be able to identify the relevant target for the source.
Think of Business Systems as sitting on top of Technical Systems, and when the landsape details are not known for third party systems we use Business Component/Business Service.
Cheers,
Souvik

TREX as an Technical System in the SLD

Similar Messages

Maybe you are looking for