Alerts in case of XSLT Mapping failure without BPM

Dear All,
We are working on IDOC - SOAP Scenario and mapping is through XSLT Mapping.
when the Vendor number field in IDOC is coming blank/invalid, the mapping should fail and an email alert should go to business.
This IDOC-SOAP is Asynchronous and not using any BPM. So can we raise a alerts withut using BPM.
I have gone through some blogs but I can see the alerts in Inbox but where as I want the alert through EMAIL.
Any pointers are highly appreciated.
Regards,
Srini

Dear Srinivas,
When you want the Alert to be send through email,then you need to configure the required mentioned below.
1.In SU01 ,Assign the corresponding Email ID for the Recipient of the ALERT.
2. In , RWB>ALERT INBOX> PERSONALIZATION--> Go to Time Independent Delivery and check the Email option.
3. Go to the transaction code SCOT,INT->SMTP and mention the corresponding Mail Host and Port in SMTP Address.Then select the set in the Internet of supported Address Types and give mail address in the Address area.
Note: Check whether Node is use is checked.
You can find the mails which are pending/failed/success in the SOST Transaction code.
Check if you have access for this configuration.Otherwise get help from Basis team.
Regards
B.Dheepa

Similar Messages

Extracting more information from XI XSLT mapping failure

Hello
I am getting to grips with XI. When developing XSLT mappings I first run them on Stylus or XMLSpy, ensure they work, and then deploy them to XI.
Unfortunately they sometimes fail to work in XI, and the amount of information retrieved about the failure is very small.
I thought of a method to get more infomation in situations like this. I could write a Java method that sends messages to the XI console. This would involve seeing the javadoc API for GlobalContainer, Container and AbstractTrace. I would also need to have these objects in my classpath in order to compile the method. Then I could use the method in the XSL.
There are two small drawbacks to this plan: I cannot find the Javadoc or the Jar file holding the classes.
Perhaps one of you readers could either tell me where these things are, or suggest a better method of solving problems like this.
In either case I look forward to receiving a reply.
Thanks
Bill Logan

Thanks for the suggestion,
completely forgot about the simpler <xsl:message/> command. I tried this, and it worked fine in Stylus.....but not in XI.
I think the problem s when the file is being loaded. An alert box pops up. It says
"Transformer configuration exception occurred when loading XSLT GDS_to_DP.xsl (http://sap.com/xi/GDSConsole, 155fc320-f69f-11d8-97f7-c0140a114c15, -1)"
and the trace window says this
"10:00:13 Start of test
Creating XSLT mapping GDS_to_DP
URIResolver called with href = GDS_DP_Common.xsl and base = GDS_to_DP.xsl
Source resolved. System id = GDS_DP_Common.xsl
10:00:14 End of test"
It seems obvious (from deduction) that the problem lies in GDS_DP_Common.xsl. XI will not give me any information precisely where this occurs
Thanks for you earlier answer Alessandro

Alerts with variables from the messages payload without BPM?

Hi, experts:
Is it possible to define a alert category with variables from the messages payload(for example:order_id ) without BPM?
Regards
Yu Ming

Refer to
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1240902,00.html
initially this also talk about BPM but you can check whether you can use the container variable in you case.
How to define the container variable in ALRTCATDEF is mention in above link.
**Points if answers find useful.
Gaurav Jain

Don't want to trigger alert in mapping failure

Hi Experts,
I have defined one alert category and corresponding rule in RWB to trigger alert for any failure like Receiver determination error, mapping error etc for all interfaces like Create order, cost center, shipments etc.
I have done complete configuration and getting alerts email in mail box if any interface fails with any reason.
But, Now, I came up with requirement that for one particular interface the alert should not trigger for mapping failure only and other interface should also not affect.
Need your help to configure the same.
Thanks in advance for your help.
Regards,
Shele.

Thanks a lot for replies.
the solution achived by defining as suggested.
u2022 Created alert rule for interface specific with u201CNo Restrictionu201D to handle all types of error instead of one generic rule to handle all interfaces.
u2022 Created Multiple Rules ( Like Receiver determination error, IDOC Adapter errors etc) instead of "No Restriction" for required interface to handle errors excluding mapping error. It had sucessfully suppressed the alerts only if u201Cmapping Erroru201D occurs.
Thanks,
Shele.

Function in xslt mapping?

Hi guys,
I want to split the resultset containing many rows coming from database into a set fo individual rows using xslt mapping. I know we can acheive this using "split by value" node function in graphical mapping. But want is the name of the function used in this case present xslt mapping.
Regards,
Suresh.

HI,
XSLT supports java script as well, but XI has few restrictions that it could support particular versions of parsers, and limitations on XSLT capabilities.
Thus I will suggest you to use some of the string APIs to split the resultset by adding the contextChange in it.
You could use XSLT mapping with Java Enhancments
Refer below link
http://help.sap.com/saphelp_nw04/helpdata/en/73/f61eea1741453eb8f794e150067930/frameset.htm
(Observe the example given in above link)
Thanks
Swarup

JMS to IDOC xslt mapping

Hi,
We have a JMS to IDOC scenario. We are using PI7.1. We are currently using XSLT Mapping . This needs to be replaced by Graphical mapping as XSLT mapping is consuming more memory.
If we remove the XSLT Mapping between source and target would we need content conversion for the soruce file ?
Please advice.
Thanks,
Teresa

Hi Teresa,
File Content conversion(fcc) is used to convert Any format file to XML format, while sending the data into PI.
& XML format to Any required output format, while sending data out of PI.
B'cos, PI only understands XML language.
So, this has nothing to do with XSLT mapping in your case.
change XSLT mapping to Graphical mapping. that should accomplish your task.
-santosh.

PI 7.1 XSLT mapping without SAP XMLToolkit

Anyone successfully run an XSL map that uses a Java enhancement method in am Operation Mapping in PI 7.1 without the using the "SAP XML Toolkit" as the processor?
I have created an XSL mapping that is calling a Java enhancement. Both the xsl and class are contained in the same Imported Archive.
When executed as test in the ESR Operation Mapping with the "Use SAP XML Toolkit" selected the map competes without error (including the Java method call).
When executed with the u201CUse SAP XML Toolkitu201D not selected, a "javax.ejb.EJBException: nested exception is: java.lang.RuntimeException: java.lang.NoSuchMethodError:" error is generated.

@ Raja Sekhar,
But you have to adjust your XSLT Mapping accordingly.
Here, the issue is with the Java enhancements which cannot be solved by adjusting XSLT mapping. As suggested above by Neetesh, this can be resolved by installing updated Java APIs.
-- Abhi

Change Filename using XSLT mapping without variable subtitution

Hi,
My scenario is IDOC to file...i am using XSLT mapping, i want to change the filename format to OUT_<Purchase Number>_<DDMMYYYYhhmmss>_KKKK.txt, i cannot use UDF function as i do XSLT mapping i also i cannot use variable substitution as the target structure doesn't have PO and timestamp as tag elements. Can i acheive using writing a adapter module? I appreciate if anyone could help me with this..
Many thanks

>
Ravibabu Adari wrote:
> Hi,
> If i go with Option1: what changes i need to do in the file adapter to tell the adapter to pick the filename from XSLT ?
> If i go with Option2: To which element to the target structure should i map the filename using UDF ? do i have to add additional element to the target structure? what changes i need to do in the file adapter to tell the adapter to pick the filename from Message mapping ?
>
> Many thanks
Hi,
in both cases you need to enable file adapter specific properties and enable the file name...
for this you need to use the dynamic configuration properties for the same...
usage of this option using udf in message mapping is rather easy than to use in XSLT...for this you dont need to change the structure in the message mapping...message mapping is just needed for execution of the udf.. thats it..
HTH
Rajesh

Duplicate Message ID issue in case of Multi mapping (without BPM)

Hi Experts,
I am doing one sample Example for my requirement of converting the single source message data into the multiple Target messages.
for example, when sender system is sending the 5 sale order details into a single message in PI then my Inbound proxy class of ECC R/3 receiver system must get this sale orders separately, that means inbound proxy class method must be triggered separately for 5 sale orders from sender system. for achieving this, I have used the Multi mapping concept in ESR (without BPM).
This scenario is in Asynchronous mode.
The below screen shots give the details on what I have configures so far.
IN ESR
IN ID
IN SXMB_MONI of PI
IN SXMB_MONI of ECC R/3 Receiver system (Error in Processing)
due to this error, inbound Proxy class method is not being triggered for the single Sale order details as well,
please let me know how to tackle this duplicate message ID issue when we have multiple payloads to process in a single message.
please also let me know if is there any other workaround to fulfil this requirement.
Thank you,
Regards,
Jagesh

Hi Nunu,
Check the below blog for restrictions.
Multi-Mapping without BPM - Yes, it’s possible!
Restrictions
Messages that result from the split in a mapping-based message split are sent using one AE. So only adapters running on the AE are supported. In particular, this means that target IDOC message splits are not supported since the IDOC adapter is not part of the AE.
Regards,
Praveen.

How to trigger Alert from Mapping without BPM ?

Hi @ ,
I have to throw an alert in case of my mandatory source field is missing .
The requirement is to chk whether a particular field is present in the source structure if itisn't present then throw alert in alert inbox.I can throw exception but the reuirement is alert so ai m struck
urgent help is required
Regards,

Hi Bhavesh,
We had this similar discussion where the issue was to throw exception and it was resolved .
Now craeting alert is coming to be a different issue
Thanks again I ddnt chk the current blog of yrs
Regards

XSLT Mapping for creating Excel files

Hi ,
I am following the blog /people/michal.krawczyk2/blog/2005/12/10/xi-generating-excel-files-without-the-java-nor-the-conversion-agent-not-possible by Michal regarding conversion of Flat files to Excel file format.
My input xml format is
         <?xml version="1.0" encoding="utf-8"?>
         <FILE>
              <Record>
     <Name>Navin</Name>
                     <EmpID>123456</EmpID>
                     <Location>Bangalore</Location>
              </Record>
             <Record>
     <Name>Ravi</Name>
                     <EmpID>789456</EmpID>
                     <Location>Hyderabad</Location>
              </Record>
         </FILE>
i need to convert this file into an Excel format with each record in single rows with Column Header names as Name,EmpID,Location.
Could you please suggest how the XLST mapping should be done for this as i am very new to XSLT mapping concept.
Please suggest how we can attain the target structure(datatype) and steps to do this XSLT mapping.
Note:- We are not doing Adapter module for this conversion.
Thanks,
Navin

> i need to convert this file into an Excel format with each record in single rows with Column Header names as Name,EmpID,Location.
This can be done with file content convertion. Use delimiter ; for excel
> Could you please suggest how the XLST mapping should be done for this as i am very new to XSLT mapping concept.
If you do not understand XSLT, you you want to maintain your development, in case if an error?
http://w3schools.com/xsl/default.asp

Idoc with XSLT Mapping ALE service error

Hi all,
I have the same problem with "converting to an ALE logical system".
In this case I have a Business System without logical system name in the SLD. This information for the IDoc control record, like SNDPOR, I will map with a xslt mapping.
In weblogs from Michael are the properties for the directory described.
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
I selected in the comminication channel the last two check boxes, as described in SAP help.
"Take Sender from Payload
If you want to take the sender of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.
If you do not set the indicator, the information is taken from the configuration in the Integration Directory.
Take Receiver from Payload
If you want to take the receiver of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.
If you do not set the indicator, the information is taken from the configuration in the Integration Directory.
If you set both of the above indicators, you do not require a heading mapping and do not need to set the alternative identifiers.
However, you must ensure that the SNDPRN, SNDPRT, RCVPRN, and RCVPRT fields are set in the IDoc control record.
Setting the senders and receivers of a message from the payload simplifies configuration and speeds up processing.
If the sender and receiver are not set correctly in the payload, the resulting error is only visible in the receiving system. "
In my XSLT-Mapping I set the appropriate Idoc fields:
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
<xsl:preserve-space elements="*"/>
<xsl:template match="DATEN">
<_-XXX_-018_XXXXX_XIDATEN>
<IDOC>
<xsl:attribute name="BEGIN">1</xsl:attribute>
<EDI_DC40>
<xsl:attribute name="SEGMENT">1</xsl:attribute>
<TABNAM>EDI_DC40</TABNAM>
<DOCREL></DOCREL>
<DIRECT>2</DIRECT>
<IDOCTYP>_-XXX_-018_XXXXX_XIDATEN</IDOCTYP>
<MESTYP>_-XXX_-018_XXXXX_XIDATEN</MESTYP>
<SNDPOR></SNDPOR>
<SNDPRN>XXXXX01IN</SNDPRN>
<SNDPRT>LS</SNDPRT>
<RCVPOR>xxx</RCVPOR>
<RCVPRN>xxx</RCVPRN>
<RCVPRT>LS</RCVPRT>
</EDI_DC40>
<xsl:variable name="pid" select="substring(.,1,1)"/>
But in the sxmb_moni the message is red with the error message :" converting to an ALE logical system"
Have you any idea?
With another interface I used a graphic Mapping and the same properties in the directory and it works.
Bye
Stefan

Hi togehter,
it works now, after cpa_cache and sxi_cache.
and and ...
<IDOCTYP>/XXX/018_XXXXX_XIDATEN</IDOCTYP>
<MESTYP>/XXX/018_XXXXX_XIDATEN</MESTYP>
Without: _-...
I would write a blog.
Does know one how that goes here?
Thanks
SDN is great
Stefan

XI 3.0 Mapping Failure

Hello All,
We are experiencing mapping errors we cannot seem to resolve. Whether using straight Message Mapping or XSLT mapping imported as an archive, we receive the same error when processing a file. We also see the same issue when running Flight demos with mapping activities.
We are running XI 3.0 SP9.
When mapping a simple XML file with 4 fields, one to one mapping, all tests run via the testing tools are successful. This is true for Message Mapping and XSLT Mapping. As soon as we test with an external file, the mapping fails. The following lists the actual trace that is generated by our test:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/entry?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine/entry?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = h10:8000</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 208.242.95.16</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2005-03-02T22:06:09Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 482DBE308B6711D9C19800402B435B96</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = 482DBE308B6711D9C19800402B435B96</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0006</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0006</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 482DBE308B6711D9C19800402B435B96</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - Plant_Maintenance_Receiver</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) Plant_Maintenance_Receiver PlantIn_To_PlantOut_XSLT</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: PlantIn_To_PlantOut_XSLT</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- 
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- 
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTO3___0000</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = XID</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAFUSER</Trace>
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
- 
<Trace level="1" type="Timestamp">2005-03-02T22:06:10Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- 
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- 
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="1" type="T">Interface Mapping http://sap.com/demo/plantmaintenance PlantIn_To_PlantOut_XSLT</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping F783E251C7D43F268ED1A6DEC8DACF7D</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping E5D04F908A6311D9B6D7DB04D0F25F10</Trace>
<Trace level="3" type="T">Mapping Steps 1 XSLT PlantIn_to_PlantOut</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating XSLT mapping PlantIn_to_PlantOut.</Trace>
<Trace level="2" type="T">Call XSLT processor with stylsheet PlantIn_to_PlantOut.xsl.</Trace>
<Trace level="2" type="T">Returned form XSLT processor.</Trace>
<Trace level="3" type="T">XSLT transformation: PlantIn_to_PlantOut.xsl completed with 0 warning(s).</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
We are resolved to the fact that this is probably an environmental issue and any help in this matter would be greatly appreciated!
Thanks,
Mike

Paul,
We are running a very simple, File-To-File type interface using the File adapter on both ends.
We've downloaded the payload from the SXI_MONITOR transaction, and it is the same as expected. We are able to import that same file into the Message Mapping testing tool and run a successful test.
When we run the test transaction, SXI_SUPPORT, we run the mapping section of the pipeline and see an error about an "illegal reference".
Here is the exact error message that we see, notice the error description is unreadable.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""><SAP:Category>XIServer</SAP:Category><SAP:Code area="MAPPING"></SAP:Code><SAP:P1></SAP:P1
<SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>The exception occurred (program: CL_XMS_MAIN===================CP, include CL_XMS_MAIN===================CM00A, line: 535)
</SAP:Stack></SAP:Error>
Thanks,
Mike

Graphical Multi Mapping and then XSLT Mapping

Hi I have to do message Split. I'm doing this message split. Then I have use XSL Mapping where I'm basically sending the whole Source message into Target Node. Basically Graphical mapping splits one Source file into 2 target files and XSL Mapping should move these individual files to 2 target messages. How Can I refer the Individual messages in the Mapping ?.
Since Actual message split takes place in Adapter Engine does XSLT Mapping acts on a Single message out of Graphical Mapping ( in my case Graphical mapping produces 2 messages ) or It acts on both messages as no actaul split didn't took place yet in the Mapping runtime.
No Guess work please ..let me know if you actually did it.Appreciate all your help.

Message splits (1:n mappings) can be executed without BPMs. It will finally occur, as you said, at the Adapter Engine layer.
When you deal with multimappings with graphical mapping, XI will automatically create two new tags surrounding your root tag(s) (tag in case you have multiple occurrence of 1 interface; tags in case your target messages are from different interfaces).
But when creating multimappings with XSLT, ABAP or Java, you'll have to handle these two surrounding tags manually. So, in your xslt, your input will be like:
> <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
>   <ns0:Message1>
>     <ns1:Your_Message1 xmlns:ns1="http://your.namespace1">...</ns1:Your_Message1>
>   </ns0:Message1>
>   <ns0:Message2>
>     <ns2:Your_Message2 xmlns:ns1="http://your.namespace2">...</ns2:Your_Message2>
>   </ns0:Message2>
>   ...
> </ns0:Messages>
(in case your target message is just 1 interface with multiple occurrence, you'll have only <Message1> tag with multiple occurence).
So, the secret here is that you'll have to handle the <Messages> and <MessageX> tags in your xslt code.
Regards,
Henrique.

XSLT MAPPING

In which cases we will go for XSLT MAPPING?
What are different functions available in altova map force ? please provide me the helpful material regards this?

Hi,
Check this link..
http://help.sap.com/saphelp_nwpi711/helpdata/en/73/f61eea1741453eb8f794e150067930/frameset.htm
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/01a57f0b-0501-0010-3ca9-d2ea3bb983c1
STEPS.
1. Open the Alto MapForce, import the source .xml and .xsd file in it
2. Similarly import the target .xml and .xsd in MapForce.
3.These two data files should match with source and target data types in Integration Repository.
4.Complete the graphical mapping using extensive list of XSLT functions available there.
5. Save the mapping file.
6.Click the XSLT tab. You will have the entire xslt logic there.
7.Copy that content and save it as .xsl file.
8. Zip above .xsl file and import the same into IR under Imported Archives.
Thanks.

Alerts in case of XSLT Mapping failure without BPM

Similar Messages

Maybe you are looking for