Integration Scenario Specific Messages

Hi Experts,
I would like to display all the messages specific to each run of Integration Scenario.
For eg:
Scenario : ABC
Run 1 at 21/01/2009 11:31 PM
Messages : Msg1
Msg2
Run 2 at 21/01/2009 11:35 PM
Messages : Msg11
Msg12
Is there any way ,i can get the list of messages that was passed for a particular scenario for each run.
BestRegards
Dhanya

Hi Sachin,
Ofcourse we can provide Sender/Receiver interfaces/Party/Components etc.But not the scenario.A scenario can have many interfaces/systems involved. I am looking for messages relavent to each scenario.
Is there any Scenario ID or something that links all the messages of a IS.Or any table maintained?
Regards
Dhanya

Similar Messages

Multiple message mappings in one integration scenario

I am trying to send a message to a marketplace that uses a web service interface. First I have to map the SRM PO to OAGIS XML, then This must be embedded in the message of the web service which requires a further mapping. In the integration scenario in the repository it seems straight forward, however the configuration of the scenario in the directory seems a little strange. This becaue the middle step does not really have an eternal receiver, as it must stay in the integration engine until the final conversion. Is it actually possible to perform several mapping in series or must I use an integration process for the middle mapping?

Andrew,
I am addressing the same problem as follows.
If you need a canonical mapping (such as OAGIS in your example) you need 2 mappings for 3 messages A(source) to B(canonical) to C(target). If you try to use XI (without BPM) as an action between the source and the target need to configure a channel in and out which as far as I can see is not possible.
When setting multi-mapping you seem to only have the folowing options:
Multiple source and multiple targets but this seems to limit you to one mapping program.
Multiple mappings if I have only one source and one target.
I think this is designed to map one or many sources to one or many targets in one mapping program.
Also you can apply a series of mapping programs to a single source and target pair.
If I understand Michal's solution you would define A as the source and C as the target. You then use multi mapping to get to the final result, but I think this is still on a single source and target. A second solution is to include multiple mappings as additional modules in the channel adpator.
To take advantage of the canonical approach I am using a simple integration process with a receive and send step. All this realy does is get round the problem you highlight of having to have channels for the middle action in your integration scenario. This is an overhead but does allow you to add splitting and combining messages if needed in the future without much additional configuration.
I can't see an easy option without BPM. Maybe there is an alternative but I can't find it. Maybe a next release of XI could include an interface mapping configuration that allows a sequnce of mapping betweem multiple pairs of maps:
Seq Source -
Mapping Program   -
Target
1 -
Message A -
Mapping Program 1 -
    Message B
2 -
   Message B -
Mapping Program 2 -
    Message C
I hope this helps.
Regards
Antony

Customer specific codelists in integration scenario with CRM onPrem

Hi,
we are working on an integration scenario C4C <> CRM onPrem. The businesspartner masterdata should be editable in C4C and CRM.
We have several customer specific fields on the businesspartner in both systems.
In CRM we have implemented customizing for the values of these fields via customizingtables that can be maintained with TX:SM30.
We can also create finetuning-activities for the maintenance of the code lists for these fields in C4C.
As these customizingtables can have around 1.000 entries per table we are searching for a solution to maintain the values just in CRM instead of maintaining them twice.
Does anybody has an idea how to replicate customer specific codelist-values from CRM into C4C? Or maybe a valuehelp in C4C that retrieves the values via webservice from CRM?
Thanks
Danny

Hi Danny,
We have requirement like get all Oper Order based on Account from ECC to cloud and we have successfully achieved using External Web Service Integration.
We have consume ECC web service integration and retrieve all Open orders based on Account ID and display in the table.
So as per my knowledge you can read all value using web service call and maintained in custom OVS ( I have never tried ).
You need to check whether is it possible or not using custom OVS but if it is working for table than it may be work for custom OVS as well.
Please check this post below may be helpful to you
SAP Cloud SDK : Bi-directional Custom Web-service Integration with PI
Regards,
Mithun

Threshold for Messages in integration scenario?

Hi,
Can we set threshold (time) for Messages in integration scenario?
Thanks,
Nagarjuna.

Hi Earlence,
> 1. Is it possible to search for messages sent to PI (7.1) via TREX and monitor their status?
Status I am not aware, but we can search the messages based on the content.
Its external search engine for SAP, we can buy this and install in the XI server.
ex : Suppose we have an order number, we don't no in which scenario it is used then we give
this number to the TREX then it searches and gives that scenarion name.
> 2. Search should be possible based on various criteria like Sender/Receiver Component/Interface, Business system name etc.
TREX is based on a client/server architecture. The client component is integrated into the application that uses the TREX functions, and allows communication with the TREX servers.The server component processes the requests; it indexes and classifies documents and answers search queries.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/78df2a46-0a01-0010-ef81-a6
be60cc5cfd
> 3. Is there a Java API so that this can be done programmatically?
May be available but this is not easy.
> 4. Some resources for the same?
/people/prasad.illapani/blog/2005/11/14/payload-based-message-search-in-xi30-using-trex-engine
http://help.sap.com/saphelp_nw04/helpdata/en/70/0837ced133304eba452c45b6047c74/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/78df2a46-0a01-0010-ef81-a6be60cc5cfd
Regards
Ramesh

PayPal integration using SOAP messages

Hello,
for a integration scenario we want to call a PayPal SOAP API as described in https://www.x.com/docs/DOC-1244.
The PayPal safety requirements are fullfilled by giving a Username, Password and Signature in the SOAP Header:
<SOAP-ENV:Header>
<RequesterCredentials xmlns=u201Durn:ebay:api:PayPalAPIu201D xsi:type=u201Debl:CustomSecurityHeaderTypeu201D>
   <Credentials xmlns=u201Durn:ebay:apis:eBLBaseComponentsu201D xsi:type=u201Debl:UserIdPasswordTypeu201D>
    <Username>api_username</Username>
    <Password>api_password</Password>
    <Signature>api_signature</Signature>
    <Subject>authorizing_account_emailaddress</Subject>
   </Credentials>
</RequesterCredentials>
</SOAP-ENV:Header>
I have given the three values as Adapter-Specific Message Attributes filled by UDF in Message Mapping.
The filled values are also visible in monitoring in section DynamicConfiguration.
SOAP Adapter: http://s3.directupload.net/file/d/2127/r8y4aywt_jpg.htm
Monitoring: http://s5.directupload.net/file/d/2127/cqvfds35_jpg.htm
But PayPal responded:
Authentication/Authorization Failed
You do not have permissions to make this API call
My credentials are ok. I have tested it within the PayPal NVP API Tester: http://www.shopsandbox.de/PayPal/Refund/ .
How do I have to manipulate the SOAP header for a successful SOAP API call?
Is it necessary also to insert the nodes ?
If yes, how?
Thanks in advance,
André

Hi,
I´ve created the whole SOAP message in Message Mapping and changed the SOAP receiver adapter sending the message without envelope. But the response is:
ADAPTER.HTTP_EXCEPTION
HTTP 500 Internal Server Error
<?xml version="1.0" encoding="UTF-8"?>
<Envelope>
<Header>
<RequesterCredentials>
   <Credentials>
     <Username>xxxxx</Username>
     <Password>xxxx</Password>
     <Signature>xxxxxx</Signature>
     </Credentials>
   </RequesterCredentials>
</Header>
<Body>
   <RefundTransactionReq>
    <RefundTransactionRequest>
     <Version>54.0</Version>
     <TransactionID>xxxxxxxxx</TransactionID>
     <InvoiceID>222222</InvoiceID>
     <RefundType>Partial</RefundType>
    <Amount>1</Amount>
    <Memo>memotext</Memo>
   </RefundTransactionRequest>
</RefundTransactionReq>
</Body>
</Envelope>
Have I missed sth?
Thanks,
André

Building an Integration scenario with the Foundation Pack

From what I can see most people use AIA so they can make use of the available PIPS.
Has anybody used just the AIA Foundation pack to build integration scenarios?
We are experiencing many problems just trying to develope a simple end to end process and wondered if anyone had a simple Do's and DOn'ts, or Step by step guide to developing a scenario.
There is a lot of documentation and its very difficult to find the relevant information as it seems to be spread across multiple docs.
Stuart

We have made some small progress using the Foundation Pack 2.3.
I thought i'd share some of my experiences for others who are having problems and finding it difficult to get info.
We used the Artifcat Generater which creates the ABCS (BPEL process).
We found several issue:
1. In ABCS Requester (which calls an EBS implemented as an ESB process) - Partner Links did not work. We were getting Invalid Port Type errors (i will post the error message when i'm back in the office), but on close inspection everything looked ok but just did not work. The simple work around was to delete the Partner Link and re-enter it manually. I wasted days investigating this problem and ended up creating my own test BPEL process calling the EBS to prove it was configured correctly.
2. The XSL stylesheets could not be tested in JDEV. We ended up commenting out many of the generated XSL templates (generated by the Artifact Generater), the main culprit seems to be GetSenderNode template, haven't got to the bottom of the issue but ended up commenting out much of the code, specifically the aia.Getxxxxxx functions. Once I get time and find more information i'll post my findings.
Good luck.

Adding a new reciever to an existing integration scenario of conf in PI7.0

Hi SapAll.
here i have got a requirement to add one more reciever to an existing integration scenario in Integration Directory(Configuration).
this Integration scenario is for sending the idoc MATMAS.MATMAS05 From 5 Different SAP-R/3 Systems to 2 Recievers.
here iam using 5 different business systems with idoc communication channels for sending idocs and 2 business systems for recieving idocs in file format with file adapters.
so when iam trying to create new reciever detarmination or Interface Determination, it says object already exists.
but i can created reciever agreement without any error.
so can anybody guide me on how to create the Interface,Reciever Determinations without any error.
regards.
Varma

now i just created a new business system with file communication channel
Why have a Business System for a FILE channel? We normaly use Business Component/ Service.
You mentioned IDOC SENDER channels....why? For IDOC we just create Receiver channels...unless you want to specify IDOC packaging.
when iam trying to create a reciever detarmination from one of the existing sender system say like BUS_SENDER2 to new
reciver system ex:NEW_BUS_RECIEVER it says object already exists.
Receiver Determination can have the same BUS_SENDER2 system/ service as sender....but it should not have the same Interface Name....this is where PI is throwing the error.
There already exists a Receiver Detremination with BUS_SENDER2 as source system and the same message interface.
You can reuse the same RD by just entering one more receiver system/ service below the already existing one (in the RD)
In short just search your ID and you will see a RD created with the source details which you are trying to use.
If you want to see a difference, then create a new sender service/ system and then use this to create the RD!
Regards,
Abhishek.

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

Read Filename form Adapter-Specific Message Attributes in Java Mapping

Hi,
I have scenario File to Mail adapter. How can i read filename from Adapter-Specific Message Attributes
in java mapping.
Thank you and Best regards
Fernand

Hello Fernand,
Are u using DOM or SAX parser?
In any case just put the Dynamic config code in the execute function or the other option is to define it as a private functionand call it in the execute,My personal advice would be the former.
Just put this code in ur java mapping
As fellow sdn ers have mentioned there is no need of the container method,just initialise the set param method and use it in the dynamice config code as follows
public class YourClass implements StreamTransformation
     private Map map;
public void setParameter(Map param)
     map = param;
public void execute(InputStream in, OutputStream out) throws StreamTransformationException
               DynamicConfiguration conf =(DynamicConfiguration) map.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
               DynamicConfigurationKey KEY_FILENAME =DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
// read value
File = conf.get(KEY_FILENAME);
Now just call File in the mapping program,
Should help u out
Regards,
Tauseef

Change Adapter Specific Message Attributes with ABAP Mapping

Hi everyone,
I have an IDOC -> PI -> File scenario and I need the file name to be a combination of several fields of the file so variable substitution is quite complicated. I have been reading about Adapter Specific Message Attributes and since the File name is one of those attributes I think maybe I can use it. The only thing is that I'm using ABAP mapping. Can I set the file name in that way? Has anyone done it?
Thank you for your help.
Regards,
Pablo

I found it myself:
DATA: l_dyn_record      TYPE mpp_dynamic.
      l_dyn_record-namespace = 'http://sap.com/xi/XI/System/File'.
      l_dyn_record-name = 'FileName'.
      l_dyn_record-value = w_nombrearch.
      dynamic_configuration->add_record( l_dyn_record ).
Thanks anyway.

Cannot see PI receiver(Proxy) adapter - advanced adapter specific message

Hello Friends,
I cannot see adapter specific message attributes in receiver adapter XI (abap proxy) for enabling. I want to use these properties for getting a file name dynamically in a receiver structure.
I had seen a blog by Mr.Michal but that gives details for file to file. Here my target is abap proxy so I cannot see advance tab properties in XI adapter used communication channel.
Clearly my interface is file to ecc (using proxy), where i will have to read a file name which my interface picks and has to update in ecc.
I have enabled the sender side File adapter - ASMessage attributes but am not able to find the attributes in receiver side. Does it make any diffrence if am not enable the attributes at receiver adapter.
Thanks very much.

Swarna,
in your scenario in order to have the file name updated on ecc, you must:
1. Set the ASMA properties on sender channel
2. Read the property in mapping and put the value in a custom field on the proxy structure. Create an UD like this:
UD
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String onixdataset = conf.get(key);
--- END UD
3. Manage the filename in the proxy class with your requirements
Regards,
Andrea

How to set values in JMS Adapter using Adanced specific Message Attributes

Hi Frnds,
in my scenarios i have to add extra header information MQ Message,
using Adanced specific Message Attributes i defined 7 parameters(Transaction,Environment,shema......) all are type Interger.But i have to set values ( Transaction type,Enviroment,shema....).
Where i can set values ??
help me on this...
Regards,
Raja Sekhar

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

XI 3.0 SP 20 - Problem with adapter-specific message attributes

Hi everyone,
I am using XI 3.0 SP 20, in SP 17 i read who SOAP adapter and mail adapter have additional adapter-specific message attributes in the message header
But in my XI SP20 dont have that function.
There arent problem in installation of SP20 (no show errors).
Can anybody tell me what is happening? Why dont have "adapter-specific message attributes" ?
Thanks

Hi,
you have to import the SAP XI content, SAP BASIS 6.40 have to be updated. Because the new attributes for adapters are saved in the Adapter Metadata located in the Integration Repository. If you have not update the content, you will not be able to find new options.
Start IR and navigate to the SAP BASIS 6.40, double click on this SWCV and click on the Details tab, you should be able see which Support Package the SAP BASIS has at moment. Update it to SP20 if it is still SP17. You will be able to see the required new attributes in Mail Adapter.
regards,
Hai

Where can I find Adapter Specific Message Attributes ASMA Schema Definition

Hi all,
I'm on PI 7.1 and want to use the Mail adapter in XIPAYLOAD mode.
I want to map to the ASMA schema definition in the Enterprise Service Builder.
I'm wondering where I can get this "new" schema?
For example the "old" mail adapter xml schema could be found in Note 748024.
REgards,
John
Note 748024 - XI Mail Adapter XML Schema "Old"
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=748024
SAP Help Configuring the Receiver mail adapter
http://help.sap.com/saphelp_nwpi71/helpdata/en/43/96cb0fb9335b77e10000000a11466f/frameset.htm
Note 856599
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856599
Should I use MailPackage or ASMA?
A: SP14 introuced the Adapter Specific Message Attributes (ASMA) that can be used to import and export adapter/transport specific headers into and out of XI. This is a generic mechanism for all adapters and other components such as mapping and routing can directly access or manipulate these values. The functionality provided by MailPackage is available in ASMA. Therefore, it is recommended that new scenarios use ASMA instead of MailPackage.

John,
the idea behind ASMA is exactly not to depend on modifying the payload to be able to map data that is just relevant to the communication layer, not the application.
Instead of having a target XSD that you need to map your source message to, filling the communication details, instead you create XI specific message headers (the so called "adapter specific message attributes") that go in the message within the SOAP Header, hence not requiring any modification of the payload whatsoever.
Notice that not having to modify the payload doesn't mean not having a mapping program, since the mapping can modify both the payload and the header, and sometimes it's a good approach to fill the ASMAs in a mapping, just bypassing the payload to the output unmodified.
BR,
Henrique.

Integration Scenario Specific Messages

Similar Messages

Maybe you are looking for