on 11-05-2007 5:23 AM
Hi
Have some doubts about adapter specific identifiers.
What is the use of adapter specific identifiers in xi scenarios.
In what cases, its mandatory to specify adapter specific identifiers?
Thanks for your responses.
Actually i asked about Adapter Specific Identifiers. But even the other responses about Adapter Specific Message attributes are something useful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mesage deleted
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everybody,
I think we are moving into wrong direction Aarthi was having doubt about "
Adapter specific identifiers
" not about "Adapter specific message attributes
"...Aarthi, Please correct me i am wrong .
Use of 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.
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-Specific Identifiers
Adapter Type : IDoc Adapter , RFC Adapter ,Marketplace Adapter respectively
Identifier : Logical system , SAP system ID , DDID respectively
aarthi, kindly go through this Link : http://help.sap.com/saphelp_nw04/helpdata/en/7d/6b82cd0d1aef48ab5953524c9cc5b2/frameset.htm
this will clear all your doubts..:
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aarthi ,
These r the details regarding Use of adapter specific identifiers :
The sender service within the message header is identified by adapter-specific identifiers.
For, business systems that are maintained in the System Landscape Directory(SLD) , the relevnt properties are replicated into the Integration Directory. For SAP systems, the sender service is determined by the system ID of the sender port and by the client. For non-SAP systems, it is identified by the logical system name.
Adapter-Specific Identifiers
http://help.sap.com/saphelp_nw04/helpdata/en/7d/6b82cd0d1aef48ab5953524c9cc5b2/frameset.htm
Adapter-Specific Message Attributes in the Message Header
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
Parts of an XI Message
http://help.sap.com/saphelp_nw04/helpdata/en/17/50d440e14f8431e10000000a1550b0/content.htm
Maintaining the Integration Server
http://help.sap.com/saphelp_nw04/helpdata/en/0e/d8fa40badbf56fe10000000a1550b0/content.htm
Java Mapping of Adapter-Specific Message Attributes
http://help.sap.com/saphelp_nw04/helpdata/en/43/09b16006526e72e10000000a422035/frameset.htm
how to apply adapter-specific identifiers, alternative identifiers, and header mapping in order to configure various Intermediate Document (IDoc) and Exchange Infrastructure (XI) scenarios
cheers!
gyanaraj
***Pls reward points if u find this useful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aarthi ,
These r the details regarding Use of adapter specific identifiers :
The sender service within the message header is identified by adapter-specific identifiers.
For, business systems that are maintained in the System Landscape Directory(SLD) , the relevnt properties are replicated into the Integration Directory. For SAP systems, the sender service is determined by the system ID of the sender port and by the client. For non-SAP systems, it is identified by the logical system name.
Adapter-Specific Identifiers
http://help.sap.com/saphelp_nw04/helpdata/en/7d/6b82cd0d1aef48ab5953524c9cc5b2/frameset.htm
Adapter-Specific Message Attributes in the Message Header
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
Parts of an XI Message
http://help.sap.com/saphelp_nw04/helpdata/en/17/50d440e14f8431e10000000a1550b0/content.htm
Maintaining the Integration Server
http://help.sap.com/saphelp_nw04/helpdata/en/0e/d8fa40badbf56fe10000000a1550b0/content.htm
Java Mapping of Adapter-Specific Message Attributes
http://help.sap.com/saphelp_nw04/helpdata/en/43/09b16006526e72e10000000a422035/frameset.htm
how to apply adapter-specific identifiers, alternative identifiers, and header mapping in order to configure various Intermediate Document (IDoc) and Exchange Infrastructure (XI) scenarios
cheers!
gyanaraj
***Pls reward points if u find this useful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wrongly posted..
Regards,
Sudharshan N A
Message was edited by:
Sudharshan Aravamudan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aarthi,
>>What is the use of adapter specific identifiers in xi scenarios.
Adapter Specific message attributes can hold the informations such as
1.File Name
2. File Type
3. Directory
4. File Size .
These informtions can be found in the Dynamic configuration payload.
>>In what cases, its mandatory to specify adapter specific identifiers?
Scenarios where u need to store the filename/filedirectory in an Table or
passed to the target system.. etc...
Eg Scenario:
Regards
San
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
If you want to get the sender file name and directory from source system.
so how i can get the source file name and directory from 3rd party?
Use Adapter specific message attributes
In Adapter Specific Message Attribute of File CC Select the Check Boxes File name & Directory.
You can also use this Blog
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
it is mand to use in cases like above where you want to sedn the source filename adn driectory to the receiver....this is one such example where you need this attributes....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The best blog on this
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
<b>Cheers,
*RAJ*</b>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
refer this on Adapter-Specific Identifiers http://help.sap.com/saphelp_nw04/helpdata/en/42/f3d027074e1bcae10000000a11466f/frameset.htm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
8 | |
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.