Adapter-Specific Identifiers 
In certain message formats, the sender or receiver is replaced by special adapter-specific identifiers. These identifiers must be mapped to the names of the relevant services in the Integration Directory so that the message can be processed.
Example
When communicating with IDocs, you can use the logical system for addressing a business partner. The name of the logical system is then mapped to the name of the relevant service in the Integration Directory.
To display adapter-specific identifiers for a service, in the object editor menu bar, choose 
Service 
Adapter-Specific Identifiers 
.
The following adapter-specific identifiers exist:
Adapter Type |
Identifier |
Note |
|---|---|---|
Logical System |
For business system services, the adapter-specific identifiers are defined in the System Landscape Directory (SLD) (as attributes of the relevant business system) and therefore cannot be changed. If the adapter-specific identifiers for a business system change in the SLD, this information is not automatically updated in the Integration Directory. To synchronize the information in the Integration Directory with the SLD, choose Comparing with System Landscape Directory in the window for Editing Adapter-Specific Identifiers. This function is only available for business system services. |
|
SAP system ID Client |
||
DDID label |
Marketplaces based on the MML (MarketSet Markup Language) message format use a DDID (Document Destination ID) to address senders and receivers. If you enter the DDID for the marketplace adapter for your communication party and service, the system checks that it is unique. |
Note
To edit adapter-specific identifiers, you must first switch to change mode in the Edit Service editor and then choose Service Adapter-Specific Identifiers .