Using adapter specific parameters in a multiple receiver scenario.

Hi all,
I have a scenario in which I am sending a binary file from one folder to another using a file sender and file receiver adapter.
But, I have another file receiver to this message which expects the filename of the above binary file in the form of an XML file.
I want to know is this possible to receive an adapter specific value in the form of XML when we havent sent any xml from source side?
Please reply.
Sumit

Sumit,
I got ur sceario.
I'm sure u have designed the data type for the target file am I right.
Let say it looks like
DT_Filename
File 1..1
Filename 1..1
U might have created the message type for the same.
Please create the message mapping with the source and target as same(above structure).
Now create simple UDF with no input.
DynamicConfiguration conf = (DynamicConfiguration) container
.getTransformationParameters()
.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION );
DynamicConfigurationKey key = DynamicConfigurationKey.create(
"http://sap.com/xi/XI/System/File","FileName");
String name = conf.get(key);
return ""name"";
UDF mapping
UDF --> Filename[Target node, as per my data type designed above]
Hope it helps!!!
If not kindly revert back.
Best regards,
raj.

Similar Messages

SOAP Use Adapter-Specific Message Properties and Variable Transport Binding

Hi Friends,
   I am new to use to Soap Adapter. Please help me out bellow doubts.
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
   2. Where exactly we r using below parameters.
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Thanks&Regards
G.Bhanuprakash

Hi,
   1.When you use Use Adapter-Specific Message Properties and Variable Transport Binding .
SAP Help says both are needed to be checked when you want to process adapter attributes
Configuring the Receiver SOAP Adapter - SAP NetWeaver Exchange Infrastructure - SAP Library
These attributes can be get/set using dynamic configuration and their technical names are what you have pasted:
Remote User : (technical name: SRemoteUser )
Remote Host : (technical name: SRemoteHost )
SOAP Action (technical name: SHeaderSOAPACTION )
To transfer further header fields, set the relevant indicator. You can then store the following attributes and their values in the XI message header:
Variable Header : (technical name: XHeaderName1 )
Variable Header : (technical name: XHeaderName2 )
Variable Header : (technical name: XHeaderName3 )
Remote User - the username used to send a message to the adapter engine using SOAP
Remote Host - hostname which the remote user used
SOAP Action - SOAP Action of the XI webservice (sender) / SOAP Action of the receiver webservice
Variable Headers are additional key-value pairs in the HTTP Header that could be accessed in the XI Header using dynamic configuration. The limit is only three though.
Regards,
Mark

How does the adapter specific parameters gets filled up?

Hello,
How do I check adapter specific parameters?
like, I am making the Soap action parameter to dynamically fill in the receiver soap adapter.
I want to check if the correct (one of the 4 actions) action was filled in action field
how do I check?
thanks
nikhil.

Hi,
You need to test the scenario from RWB testing to get the proper results about the dynamic settings for adapter specific parameters.
Refer
Accessing Adapter-Specific Attributes through User Defined Function
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70c89607-e4d9-2910-7280-f6746e964516
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
/people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70c89607-e4d9-2910-7280-f6746e964516
Re: Adapter-Specific Message Attributes
setting adapter specific message attributes
Thanks
Swarup

Using adapter specific message attributes in SOAP adapter configuration

Hi,
Can you please let me know how to use adapter specific message attributes in receiver and sender SOAP adapter configuration. If possible , with example.

See here:
Adapter-Specific Message Attributes in the Message Header
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/frameset.htm
Sender Soap Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
Receiver Soap Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm

Using Adapter-specific attributes in Mail adapter

Hi,
I try to use adapter-specific attributes in my Mail adapter. I set the "Use Adapter-Specific Message Attributes" indicator, but I do not get a result in the mapping and also in the SXMB_MONI the attributes are not visible.
The documentation also refers to Variable Transport Binding indicator:<a href="http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm">http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm</a>
Could this be the problem? I cannot find this indiciator! Does anyone know where I can find this indicator?
Regards,
Torsten

Hi,
The values for the parameters, set using adapter specific message attributes are available at runtime in the path http://sap.com/xi/XI/System/Mail.
We need to write UDF's that can extract the values from this path.
For Ex:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters() .get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(
 http://sap.com/xi/XI/System/File,
 FileName);
String valueOld = conf.get(key);
if (valueOld != null) {
 String valueNew = valueOld.replaceAll(input,output);
 conf.put(key, valueNew);
If you check Dynamic configuration in sxmb_moni, you would be able to find the values for all the attributes that have been set in the adapter.
Regards,
Smitha.

Integrtion Scenario using BPM with two sender and multiple receiver

integrtion Scenario using BPM with two sender and multiple receiver
How many Application Components are required?

Hi Vinod,
1) In integration repository you can have one or many software components it depends on your landscape orchestration
2) In integration direcory you need at least one service for bpm and one or many for each system in your bpm
also each connection between systems and bpm must have receiver determination and so on.
Advice: Please treat BPM as a separate system.
best,
Wojciech

Any possiblity to use single Inbound Service Interface with multiple Receiver Agreements

Hi All,
Scenario: PROXY to FILE.
Requirement is to receive to two locations.
Is it possible to use single Inbound interface with multiple Receiver Agreements. I tried using two operation in the Inbound Service Interface, and Operation Specific in Determination. But couldnt proceed further. Do I need to use seperate Service Interface for two receiver locations?
Please suggest some solution.

Hi Naveen,
There is a possibility but in the case in the same server location with dynamic configuration: Placing file in two different directories using single receiver communication Channel
With different location you would need to develop a new adapter module as Amit Srivastava explains and develops here Send File to Two Different Locations using Adapter Module
Regards.

Error using XI HTTP adapter specific message attribute URL parameters

Hi XI gurus, in our XI 7.0 SPS11,
we have problem using URL parameters of plain HTTP receiver adapter.
If I set Adapter specific message Properties in communication channel and activate switch for Apply URL parameters (using Parameter 1 to 5) filling them using message mapping, we have no effect; instead we have error "Dynamic Header - Missing Message Attributes: Fields/Parameters".
We carried out this test:
1. not using adapter specific message attribute and setting
a static URL target with fixed parameters it runs correctly.
2. using adapter specific message attribute for target
URL and URL parameters both doesn't runs correctly.
3. using adapter specific message attribute only for target
URL doesn't run correctly.
These attribute key used for URL parameters:
URLParamOne
URLParamTwo
URLParamThree
URLParamFour
URLParamFive
Namespace: http://sap.com/xi/XI/System/HTTP
Can you solve this issue? Are there oss notes, corrections, ...
Thanks in advance.
Marco Tricase

Some other test done with TCP gateway.
Activated adapter specific message properties for
*URL
*HTTP Header fields (one header field named "lisca")
*URL Parameters (one param named "objectType")
The HTTP message catched by TCP Gateway
POST /csl/cslinker HTTP/1.0
content-type: text/xml; charset=UTF-8
content-length: 318
connection: close
accept: /
user-agent: SAP Web Application Server (1.0;700)
host: 10.10.43.94:54000
accept-encoding: gzip
<?xml version="1.0" encoding="UTF-8"?>
seems nothing has been generated, and obviusly URL and params have been set in message mapping.
Hope some guru has been solved the issue ...
Pasquale Rossiello

Need help for Adapter Specific Message Attributes in Receiver Email Adapter

We want to use Adapter Specifice Message Attributes(ASMA) in Receiver Email Adapter for sending the mails dynamically, and to set the CC and BCC. I have gone through the help give in <a href="http://help.sap.com/saphelp_nw04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/frameset.htm">SAP Help</a>
not clear how to use it. Please help to configure this.Any blogs?
with regards,
Ravi Siddam

Hi Kumar,
This blog explains about using 'Mail Package' option. We have already gone through this link and configured as explianed. 1.it dosen't support CC,BCC and 2. it is old way.
We are on PI 7.0. It is recommended to use ASMA and in this it is possible to use CC and BCC.
We don't know how to use ASMA. any help?
with regards,
Ravi Siddam

Adapter-Specific Message Attributes

Hello,
I have this configuration in a sender file adapter:
File adapter java class
classname=com.sap.aii.messaging.adapter.ModuleXMB2File
mode=XMB2FILE
##Adress for XMB endpoint
XMB.httpPort=8000 <- Para XI desarrollo
XMB.httpService=/tmp <- Directorio de XI
##File Adapter specific parameters
file.createDir=1
file.targetDir=/DATOS/INTERFACES/RRHH <- Directorio de R/3
file.targetFilename=XXXX0*.txt
#file.writeMode=addTimeStamp
##xml conversion properties if mode XMB2FILEWITHCONVERSION is specified
#xml.addHeaderLine=0
#xml.headerLine=
#xml.fieldFixedLengths=15,25
#xml.fieldSeparator=;
I just wanted to add the Adapter-Specific parameter but I do not how to do it, for keeping the Filename.
Can anyone help me?
Thanks in advanced,
Luis

Hi Moorthy,
I know I can do it like that, but for some reasons I can not use that way, so the only way for me for moving one file from R/3 to XI, was the one described above, and it works fien if I set a Filename in my file receiver channel in XI.
But if I set adapter specific options in the receiver I got an error, because there is no dynamic configuration in the xml message header...So I need to configure the sender adapter in the R/3 for setting that parameter up .
Michal in the help link that u give I couldnt find anything useful...
Thanks anyway,
Luis

Adapter specific attributes - SOAP Adapter

Hi,
I am trying to use the adapter specific attributes of the receiver SOAP adapter. But I am not able to view the Dynamic configurations in sxi_monitor corresponding to this message. Any clue why!?
I read through the SOAP adapter help on help.sap.com,
http://help.sap.com/saphelp_nw2004s/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
Here it says:
If you want to use header fields, set the relevant indicator for Variable Header. The technical names for the fields are XHeaderName1, XHeaderName2, XHeaderName3. The parameters are embedded in the HTTP request under the names you enter here.
But I donot find an option where I can enter the names. Am I missing something here?
Regards,
Smitha.

Hi Smitha,
I did not try to use adapter-specific attributes with SOAP-adapter, but with mail-adapter. The documentation is quite similar, so I excpect similar results...
So as far as I understood, the parameters XHeaderName1, ... etc are for dynamic extension of the set of adapter-specific attributes. For example, if you want to add some more information in the message header, you can program an adapter module and you have now a guide how to name the additional attributes.
Usually, the "standard" adapter-specific attributes are starting with "S" (Sender) or "T" (Receiver). You can find the names in the documentation of the SOAP-adapter.
In order to use the adapter-specific attributes, you have to check both indicators (adapter-specific attributes, variable transport binding). If this still doesn't work, you should use OSS. In my scenario (mail adapter) this didn't work, too. The reason was, that there was a bug in the adapter metadata (Integration Repository) of SAP BASIS. There was a SAP note, where I could download the correct adapter metadata. Maybe you can find a SAP note for the SOAP Adapter.
Although this is probably not the final solution, I hope this guides you a step further.
Regards,
Torsten

Multi-Message-split with ABAP mapping and adapter specific attributes

Hi all,
With ABAP-Mapping I split 1 message to n messages.
So many files are generated in file-Adapter.
Everything fine.
But now I want the file names different using adapter specific attributes.
It is not possible to use variable substitution and write the file name in payload because of receiver restrictions.
I tried this with following similar coding in ABAP-Mapping:
data: lt_records TYPE MPP_DYNAMIC_TAB.
 Loop.
 l_file_name = "payload-Inbound"-information
 ls_record-namespace = 'http://sap.com/xi/XI/System/File'.
 ls_record-name = 'FileName'.
 ls_record-value = l_file_name. "l_file_name comes from inbound-payload
 append ls_record to lt_records.
 Endloop.
CALL METHOD dynamic_configuration->set_all_records
 EXPORTING
 records = lt_records.
If I start the interface I see in the monitoring the dynamic configuration with many entries for file-name in the the SOAP-Header mapping of the request message (following extract):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:DynamicConfiguration xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">BPAADDRESS.XML</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">BPABROKERROLE.XML</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">BPACOMPANYSEGMENT.XML</SAP:Record>
<SAP:Record namespace="http://sap.com/xi/XI/System/File" name="FileName">BPACUSTOMERROLE.XML</SAP:Record>
The result is that all files have the same file name (last entry in dynamic configuration).
Is it possible to write the adapter specific configuration in ABAP-mapping for every single result message??
Thank you for your help,
Florian

Hi Florian,
I've a different idea...I dont think its a "right solution" but just another work around..it involves a BPM...
In your ABAP mapping..set the dynamic config with as many variables as number of different messages...i.e. use the variables like 'FileName1', 'FileName2'...'FileName6' instead of 'FileName'. But use the same namespace 'http://sap.com/xi/XI/System/File'
Call the above mapping in a BPM and capture the individual messages and set the attribute 'FileName' from the values of 'FileName1' to 'FileName6' accordingly using Message Mapping and then send the message using the 'Send' step.
before you try this, try using the variable names 'FileName1' ...'FileName6' in the receiver adapters...enable the ASMS. I know we need to select which variables from the dynamic config to be used by the adapter by specifically selecting 'FileName', 'Directory' etc...but just give it a try and see if it works..
Or..instead of using a BPM..you can combine Henrique's idea...use Adapter module to set the value for 'FileName' from variables 'FileName1'...'FileName6' accordingly.
hope I'm clear..lemme know if you have any questions..
cheers
praveen

JMS adapter: Adapter specific message attributes

Hi,
I have a synchronous SOAP to JMS (MQ series) scenario where Im using sync/async bridge (without BPM).
I need to correlate the message being put on JMS queue (JMS receiver adapter) and the response (JMS sender adapter).
The standard receiver JMS adapter only allows the JMS correlation ID to be set to one of three different values (excluding NULL). 2 of these (reference and conversation ID) will be empty in my scenario, leaving me with only the XI message ID. This ID however exceeds the length of ie. the JMS correlation ID and thus isnt suitable for correlating anything using the field JMS Correlation ID.
NB: it is of no use to try and set the conversation ID at mapping time (using container object) since the changed value only is available during mapping execution.
Surely one way of setting the conversation ID would be to use an adapter module in SOAP sender, but this is not an option. Also the sender system will not provide one either.
Now the problem isnt setting the JMS correlation ID dynamically at runtime (this is achieved without trouble using the dynamic configuration API with the key DCJMSCorreleationID). The problem is to actually have XI correlate the request with the response.
Since the JMS collelation ID is smaller than the XI message ID and the conversation and reference ID isnt available, what I figure is that I need to find a MQ message property to use and then use the Set MSProperty to part instead this property surely needs to be large enough to contain the XI message ID.
So what I did was I looked in http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqwak.doc/js50938.htm
where a list of fields in the message descriptor is available figuring I can just use one of these. Looking through the list I notice the field MDRQ (Name of reply queue, 48-byte character string) should be able to hold the XI message ID. So I add MDQR in the Specify additional JMS message properties and set the Java Type to String and also enter this field in the Correlation Setting of the receiver JMS adapter.
Runtime:
When looking in MDT I see:
New JMS message will be correlated with the XI message. Correlation rule: XI_MESSAGEID, correlated property: JMS property MDRM, correlation value: 36158680-5a0c-11dc-8c14-000f203cd3c8
I looks like a success! No data is however set in the field when looking at messages being put on MQ.
If I increase the trace level of the JMS adapter I can see (in defaultTrace) the following:
Cannot read the switch setting for property name DCJMSStringProperty0, switch name dynConfigDCJMSStringProperty0. It is switched off.
What does this error mean?
I have of course clicked Use adapter Specific Message-Attributes and also the Specify additional. In other words everything look ok in configuration.
Since Ive also put a check mark in Fail if adapter specific message attributes is missing I can see that I successfully put a value (using dynamic conf. at mapping time) in the field... but still something isnt right the value of the property never reached MQ.
Now Ive tried with a couple of fields in the message descriptor from the previous URL. XI complains all the time.
Anybody got some ideas?
Best Regards,
Daniel

Hi Vijay,
Thanks for your replay,as per your input i creted dynamic configuration method,
i taget structure luks like this
 <Data>
 <Mesage>
 <gl_update>
 <header>
 <ean1>
 <ean2>
 </header>
 <gl_update>
 <Message>
i written UDF and mapped to header element gl_update,
but i am getting below error message in MONI
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_ ffjms_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:MT_jms_ _a</SAP:P3>
<SAP:P4>sync_out/Data/Message/ GLUpdate. Values missi~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ ffjms_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_jms_ asyncout/Data/Message/ GLUpdate. Values missi~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
i want to know i mapped to UDF to GL_Update is is correct, to which element i have to map.
i think there is no prob with UDF,its executing ,giving warning messages
help me on this,
Regaards
Raj

Overwrite Adapter-Specific Message Attributes in MAIL adapter.

Hi guru.
I'm trying to use the SENDER MAIL Adapter.
My scenario is the following:
a remote system send an email with an XML file like attachment. The PI System read the mailbox and tries to map the payload.
When I try without the "Adapter-Specific Message Attributes" the flow work well, but I need to know the email of the sender.
When I try to enable the Adapter-Specific Message Attributes the system finds an error in the SOAP envelop, in the "SHeaderX-CR-HASHEDPUZZLE" Node.
This is a part of the ENVELOP.
<sap:DynamicConfiguration SOAP:mustUnderstand="1">
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTO">email</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SUser">testxi</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-ORIGINATING-IP">[XX.XXX.XX.XXX]</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SGreeting">
Lotus Notes POP3 server version X2.0 ready on xxx.</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderSUBJECT">GROUDWORK_REMOTE</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-MSG-REF">
server-10.XXXX.com!1224858537!24401109!1
</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderMESSAGE-ID"> 00a801c935e4$d4b4e3d0$7e1eab70$
</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-VIRUS-SCANNED">amavisd-new at xxx.com</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-ENV-SENDER">EMAIL</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-STARSCAN-VERSION">5.5.12.14.2; banners=-,-,xxx.it</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-SPAMWHITELISTED">domain whitelist</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-VIRUSCHECKED">Checked</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-MIMETRACK">
Itemize by SMTP Server on IXXX(Release 6.5.5|November30, 2005) at 10/24/2008 16:28:57,Serialize by POP3 Server on IXXX(Release 6.5.5FP2|October23, 2006) at 24/10/2008 16:38:51,Serialize complete at 24/10/2008 16:38:51
</sap:Record>
*THE ERROR IS IN THE FOLLOWING NODE*
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-CR-HASHEDPUZZLE">
7hY= AFac ANQ+ Ad/R ArpP BnYc C6X8 EpvL FLPB GGaw GaCt HKM+ I0Nu JIhk JdJ4 KIZZ;1;dABlAHMAdAB4AGkAQABwAHIAbwB0AG8AdABpAHAAbwAuAGkAdAA=;
Sosha1_v1;7;{CCB182EF-E812-44B6-9C48-85873A18C72};bQBhAG4AdQBlAGwALgBjAGgAaQBhAHIAZQBsAGwAaQBAAGkAbgBmAHIAYQBjAG8AbQAuAGkAdAA=;
Fri, 24 Oct 2008 14:28:46 GMT;RgBXADoAIABDAE8ATQBFAFIAXwBSAEUATQBPAFQARQA=
</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-CR-PUZZLEID">{CCB182EF-E812-44B6-9C48-B85873A18C72}</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">
Ack1vUKnx+miPqT4T22mKaVcKhgAvwAAEmwwAAGwdQAABvplAAAAK6sgAAARhjAAAGHCAAAAKwPAAABcPNA=
</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderRECEIVED">
from XXX.com ([xx.xxx.xxx.xx]) by mail3.XXX.com (Lotus Domino Release 6.5.5) with SMTP id 2008102416285733-32229 for EMAIL ; Fri, 24 Oct 2008 16:28:57 +0200
</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderDATE">Fri, 24 Oct 2008 16:28:48 +0200</sap:Record>
 <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SServerLocation">pop://popserver</sap:Record>
</sap:DynamicConfiguration>
My question is:
Can I overwrite in the adapter the <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-CR-HASHEDPUZZLE"> ?
<post_modified>
Edited by: Juan Reyes on Nov 3, 2008 7:22 PM

Hi
Check the details of the Email in Mail box are all the Adapter specific parameters are coming. If not then this will not read Adapter Specific parameters. Some Legacy system dont generate all parameters But you can add your using variable header.
Thanks
Gaurav

Adapter Specific Paramters for Integration Process in Configuration

I want to send the data from flat file to idoc through BPM
While doing configuration do I need to explicitly give Adapter specific parameters(Logical System Name) for BPM(Integration Process) or not?
Is it mandatory to give Adapter Specific Parameters for this scenario?
FILE-->BPM--->IDOC(R/3)
Thanks & Regards
Katta Mohan Reddy

Hi,
why would you require Adapter specific parameters (I assume you mean Adapter specific Attributes) - Logical System should be there through the routing (Receiver Determination). What exactly do you want to accomplish by that?
regards,
Peter

Using adapter specific parameters in a multiple receiver scenario.

Similar Messages

Maybe you are looking for