Technical Receiver Determination API 
The ABAP stack of SAP NetWeaver offers an API for technical receiver determination (TRD-API), which allows developers of web service consumer applications to dynamically instantiate consumer proxies at runtime.
Note
Technical receiver determination is only relevant for communication scenarios that are either based on the Web Service protocol or the XI 3.0 protocol and where the consumer application uses Service Groups.
To instantiate consumer proxies, the TDR-API can use:
Service Groups
Developers can use Service Groups to find the recipients of a Web service call. If there is support for routing, a Service Group can be configured for multiple provider applications.
Business Application IDs
A provider application can use the unique Business Application ID of a consumer application to identify that application and to instantiate a consumer proxy with a logical port that points to the calling consumer application.
Consumer proxies that are instantiated using the TRD-API can be configured for the Web Service Runtime and for XI Runtime. If the consumer- and the provider application do not use features that are not supported by both runtime environments, the consumer has the option to choose which one to use.
Activities
Developers and system administrators typically work with the technical receiver determination API as follows.
Developer of a Consumer Application
Create a new outbound proxy (or reuse an existing one) to consume the inbound interfaces.
Create Service Groups that contain the proxies.
At runtime, use the Service Group API to instantiate the consumer proxies.
To transfer your own Business Application ID to a provider application to receive an asynchronous response, use the provider ID API.
Developer of a Provider Application
If a provider application supports the asynchronous request response pattern, you can use the Service Group API to instantiate consumer proxies using the Business Application ID of the consumer application.
Administrator of a Consumer Application
Configure a system connection containing the data needed to access the provider system.
The configuration framework automatically attempts to retrieve the Business Application Name and the Business Application ID of the provider application from the Services Registry. If this attempt fails, you need to configure the connection manually.
Next, you can assign Service Groups to the applications in the provider system.
You can use the XI protocol or the Web Service protocol. The configuration framework automatically attempts to create the required logical ports. If this attempt fails, you need to configure the missing logical ports manually.
Administrator of a Provider Application
Set up the Business System Name of your system. (The Business System Name can be retrieved from the System Landscape Directory if one is available.) You can also maintain the organization name to make it easier for consumer application administrators to select your provider application.
Next, maintain the service binding, either on its own or as part of business scenario communication. When the service definitions are published, they are automatically classified.