Forwarding ABAP Proxy Application errors to CCMS of ECC
Hi All,
We are using fault messages for inbound ABAP proxy interfaces to capture application errors, and we can see the error in the monitoring of ECC. However, Is there a way, we can forward it to CCMS of ECC (and not XI), because we want to use an external tool linked to CCMS via SOLMAN to get alerted in case of application errors.
thanks,
Karthik
Solved on my own.
If you need information please contact [email protected]
Similar Messages
-
ABAP Proxy PARSE_APPLICATION_DATA ERROR
Hi Guys,
Can some one please help me to resolve this issue, XML --> ABAP proxy scenario. PI sent message successfully, but I am getting error on SNC target system.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1>Request Message</SAP:P1>
<SAP:P2>CX_ST_DESERIALIZATION_ERROR</SAP:P2>
<SAP:P3>/1SAI/TXSF8E9D07F84DB493AAA0A Line 3340</SAP:P3>
<SAP:P4>An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A (Data loss occurred when converting 00900012300355698 Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 529 XML Path: ns2:ProductActivityNotification(1)ProductActivity(2)Item(3)ShipToLocation(1)StandardID(2)</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion: Request Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/TXSF8E9D07F84DB493AAA0A Line 3340 An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A (Data loss occurred when converting 00900012300355698 Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 529 XML Path: ns2:ProductActivityNotification(1)P An error occurred when deserializing in the simple transformation program /1SAI/TXSF8E9D07F84DB493AAA0A Data loss occurred when converting 00900012300355698</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance
Regards
SanHi Folks,
I have got application error while doing in Inbound proxy scenario. This inbound message is ProductActivityNotification, this message has got fault message. This message is triggering for faults. How to control this fault message or how to divert this error as an alert to RWB. Please give me your ideas step by step. Error as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Inbound Proxy
-->
- <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="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SAPGlobal20/Global">ProductActivityNotificationFault</SAP:ApplicationFaultMessage>
<SAP:Stack>Application has thrown an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please find the fault message has got following values
<?xml version="1.0" encoding="utf-8" ?>
- <n0:ProductActivityNotificationFault xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:RAS:/1SAI/TAS653D9A9CCD9A8EF3AF9B:701:2009/02/10">
- <standard>
<faultText>Proxy Class (Generated)</faultText>
- <faultDetail>
<severity>information</severity>
<text>Start of inbound processing: ProductActivityNotification (ID )</text>
<id>000(/SCA/BIF_PROACT)</id>
</faultDetail>
- <faultDetail>
<severity>error</severity>
<text>Message ID is missing</text>
<id>032(/SCA/BIF_MI)</id>
</faultDetail>
</standard>
</n0:ProductActivityNotificationFault>
Will you please focus bit light on this error message please?
Regards
San -
Hi All,
I'm trying to create a synchronous ABAP proxy out of my outbound interface. When I do that I get an error saying that
<b>Cannot generate proxy (object <attributename="type"> missing in WSDL, see long text)</b>
Now when I remove the reponse message from the interface and make it asynchronous, I'm able to create it without any trouble. So the trouble lies in the reponse message which is a XSD file imported as an external definition. Request message is also an external definition.
The reponse WSDL is as follows:
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:ebay:api:PayPalAPI">
<wsdl:types>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:ebay:api:PayPalAPI" targetNamespace="urn:ebay:api:PayPalAPI" elementFormDefault="qualified">
<xsd:import namespace="http://schemas.xmlsoap.org/soap/envelope/" schemaLocation="DoDirectResponse.xsd" />
<xsd:import namespace="http://schemas.xmlsoap.org/ws/2002/12/secext" schemaLocation="wsse.xsd" />
<xsd:import namespace="http://www.w3.org/1999/XMLSchema-instance" schemaLocation="xsi.xsd" />
<xsd:import namespace="urn:ebay:apis:eBLBaseComponents" schemaLocation="ebl.xsd" />
<xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="RequesterCredentials">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="ebl:Credentials" />
</xsd:sequence>
<xsd:attribute ref="xsi:type" use="required" />
</xsd:complexType>
</xsd:element>
<xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="DoDirectPaymentResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="ebl:Timestamp" />
<xsd:element ref="ebl:Ack" />
<xsd:element ref="ebl:Version" />
<xsd:element ref="ebl:Build" />
<xsd:element ref="Amount" />
<xsd:element ref="AVSCode" />
<xsd:element ref="CVV2Code" />
<xsd:element ref="TransactionID" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="Amount">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:decimal">
<xsd:attribute name="currencyID" type="xsd:NCName" use="required" />
<xsd:attribute ref="xsi:type" use="required" />
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="AVSCode">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:NCName">
<xsd:attribute ref="xsi:type" use="required" />
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="CVV2Code">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:NCName">
<xsd:attribute ref="xsi:type" use="required" />
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:element xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" name="TransactionID" type="xsd:NMTOKEN" />
</xsd:schema>
</wsdl:types>
<wsdl:message name="RequesterCredentials">
<wsdl:part xmlns:generateduniqueprefix15="urn:ebay:api:PayPalAPI" name="RequesterCredentials" element="generateduniqueprefix15:RequesterCredentials" />
</wsdl:message>
<wsdl:message name="DoDirectPaymentResponse">
<wsdl:part xmlns:generateduniqueprefix16="urn:ebay:api:PayPalAPI" name="DoDirectPaymentResponse" element="generateduniqueprefix16:DoDirectPaymentResponse" />
</wsdl:message>
<wsdl:message name="Amount">
<wsdl:part xmlns:generateduniqueprefix17="urn:ebay:api:PayPalAPI" name="Amount" element="generateduniqueprefix17:Amount" />
</wsdl:message>
<wsdl:message name="AVSCode">
<wsdl:part xmlns:generateduniqueprefix18="urn:ebay:api:PayPalAPI" name="AVSCode" element="generateduniqueprefix18:AVSCode" />
</wsdl:message>
<wsdl:message name="CVV2Code">
<wsdl:part xmlns:generateduniqueprefix19="urn:ebay:api:PayPalAPI" name="CVV2Code" element="generateduniqueprefix19:CVV2Code" />
</wsdl:message>
<wsdl:message name="TransactionID">
<wsdl:part xmlns:generateduniqueprefix20="urn:ebay:api:PayPalAPI" name="TransactionID" element="generateduniqueprefix20:TransactionID" />
</wsdl:message>
</wsdl:definitions>
I would be really grateful if I could get a resolution as I'm badly stuck because of this issue.
Thanks
ArvindHi Arvind,
Check the following,
1. The tag <part name="" type=""> is not supported with ABAP Proxies.
Cannot generate proxy
2. Check for recursion - Cannot generate ABAP proxy
3. keep in mind tht ur application system is based on 6.40 or higher versions.
Regards,
Prateek -
ABAP Proxy PARSE_APPLICATION_DATA ERROR - Deserialisation error
Hi All,
Can some one please help me to resolve this issue, XML --> ABAP proxy scenario. PI sent message successfully, but I am getting error on SAP target system.
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1>Request Message</SAP:P1>
<SAP:P2>CX_ST_DESERIALIZATION_ERROR</SAP:P2>
<SAP:P3>/1SAI/SASF1B34BDF7BC867BECB1E Line 127</SAP:P3>
<SAP:P4>An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E (Data loss occurred when converting ON Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 6025 XML Path: ns1:MT_HCM092_EmpPersonalData(1)PersonalDataUpdation(34)GBDEP(6)</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion: Request Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SASF1B34BDF7BC867BECB1E Line 127 An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E (Data loss occurred when converting ON Kernel ErrorId: CONVT_DATA_LOSS) XML Bytepos.: 6025 XML Path: ns1:MT_HCM092_EmpPersonalData(1)PersonalDataUpdation(34)GBDEP(6) An error occurred when deserializing in the simple transformation program /1SAI/SASF1B34BDF7BC867BECB1E Data loss occurred when converting ON</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The error is shown for the field GBDEP. It is of type char(3) both in the source system and the target system.
Still i am getting this error.
Kindly help me in resolving the issue.
Regards,
Sridevi SHi Klaus,
Thanks for the t-code.
I couldn't figure out any issue in that program. Below is the line of code in the program for the field GBDEP which is same as for the other fields.
<tt:cond s-check="not-initial('ROOT.GBDEP')">
<tt:ref name="ROOT">
<GBDEP tt:ref="GBDEP">
<tt:deserialize>
<tt:assign to-var="_C_NIL" val="' '"/>
<tt:d-cond>
<tt:attribute name="xsi:nil">
<tt:read var="_C_NIL" map="xml('true', '1') > val(C('2'))"/>
</tt:attribute>
</tt:d-cond>
</tt:deserialize>
<tt:cond-var check="_C_NIL!='2'">
<tt:value maxLength="3"/>
</tt:cond-var>
</GBDEP>
kindly help. -
hello everybody,
i have the next scenario ABAP Proxy->XI->RFC, the problem is that in the sender system I'm getting the next error in SXMB_MONI of sender system:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Integration Server
-->
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1="401" p2="Unauthorized" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>
<SAP:Text language="EN">HTTP status code 401 : Unauthorized</SAP:Text>
</SAP:ErrorHeader>
the status is system error, can anyone help me with this error, cause messages are not aariving to Integration Server, thanks in advance.
Regards,
Julio CesarHi Julio
Check Following Steps:
1:Have you insterted the correct URL of your Integration Server?
XMB.TargetURL=http://<host>:<ICM_Port>/sap/xi/engine?type=entry
2: Is the user and password correct?
XMB.User=XIAPPLUSER
XMB.Password=*****
3: Are the read permissions in the source directory correct?
file.sourceDir=/usr/sap/...
4: Be sure you use the ICM Port in my case 8000, e.g.
XMB.TargetURL=http://server:8000/sap/xi/engine?type=entry
If you use SLD information also include
XMD.SLDConfiguration=SLDaccessor in the file.
Check also that the XI user has the right profiles in the XI ABAP instance.
Thanks
Abhishek Mahajan
***Reward points if helpful********* -
ABAP Proxy configuration Error (Not able to connect R/3 to IB )
Hello All...
I am trying to configure the connection from R/3 to XI using the ABAP proxy generation.For that I have followed the steps given in the below blog
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
We created all the credentials required for the XI and R/3 side configuration and its working fine individually when we have tested for the connection and also assigning this at SXMB_ADM,but in integration engine configuration,when I am trying with the URL <b>dest://<RFC destination(http</b>).Its giving error and in sproxy at R/3 its giving that no integration engine is connected to Business system.
Whats worng with my configuration.How can I resolve this.
I am having R/3 system WAS 6.40Hi,
<i>But when I am giving the path prefix as you have specified I am getting an Error Query String Not Allowed.</i>
I think thats the warning not error. Just press enter again and go to the logon detail Tab and give the userid password
<i>And how can give the SLD details using the SLDAPICUST.</i>
go to transaction SLDAPICUST and give the following details:
Alias name :any name u want
Prim: check this box
Hostanme: give the Hostname where your SLD (XI server name if you are using the XI SLD)
PORT: Java Port
UserId/Password: for XIAPPLUSER
I think you are missing on the configuration. I think its better if you go through the weblog again.
Regards
Vijaya -
FILE TO INBOUND ABAP PROXY - " LOOP_IN_MESSAGE_ROUTING ERROR "
Hi ,
Getting the following Error in *FILE TO INBOUND ABAP PROXY* which is updating a Database table in R/3.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">LOOP_IN_MESSAGE_ROUTING</SAP:Code>
<SAP:P1>is.01.lgscms</SAP:P1>
<SAP:P2>IS</SAP:P2>
<SAP:P3>XI</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XI protocol error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
How to rectify the Error..
Regards,
RaviHi Ravi !
Check if the url for the receiver is
http://<host>:<port>/sap/xi/engine?type=receiver
or
http://<host>:<port>/sap/xi/engine?type=entry
if using XI 3.0
Regards,
Matias.
Edited by: Matias Denker on Feb 25, 2008 2:12 PM -
Hi:
I am tryign to activate an ABAP Proxy in an ECC backend, and I get an error 'No Vendor Specified' with no further details, and the activation is terminated. Has anyone seen this, and what needs to be done to fix this.
BTW:I am using SAP PI 7.0(SP13) as the middleware and ECC6.0 (Basis SP16). I can see and generate my proxies and all objects. All my dictionary objects can be activated individually, and the Messages. However, its only the proxy that does not get activated.
ThanksHi,
check the connections in the ECC like
Regarding Proxy Scenario We need 3 connections
STEP1:
1.TCP\IP connections
1.1.LCRSAPRFC
1.2.SAPSLDAPI
2.Settings are to be done in SLDAPICUST transaction
3.Http Connection: -
3.1.PI_INTEGRATIONSERVER
Purpose of LCRSAPRFC:
In order to get the interface details in SPROXY transaction.
Purpose of SAPSLDAPI
To connect to SLD and get the respective business system name maintained in SLD,
Purpose Of SLDAPICUST
Next Execute transaction SLDAPICUST to maintain the SLD access data.
Purpose of PI_INTEGRATIONSERVER
Create a destination of type H in transaction SM59.This connection is used to send the message to the Integration server
Check all these connections are there or not in ECC.
Thanks. -
Outbound Client ABAP Proxy Timeout Error
Hello everybody we have the next scenario:
R/3 Client Synchronous ABAP Proxy->XI-> Synchronous RFC
and we are having problems cause the Sender R/3 is not waiting for the RFC in the Receiver system to process so XI is in log status fot this messages, is there a parameter to increase the time for R/3 Sender to wait for the Call method sentence to complete succesfully??????, thanks in advance.
Regards,
Raul AlvaradoHi,
do changes as below
In SXMB_ADM
go to Configure Integration server
in change specific identifiers Set Runtime parameter: HTTP_TIMEOUT and then restart XI server, changes will be updated.
Regards,
Sukarna. -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
<SAP:P1>DFBD3A3045C011DCACF800145ED17196</SAP:P1>
<SAP:P2>CENTRAL</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message-Id DFBD3A3045C011DCACF800145ED17196 ist im gerufenen System bereits vorhanden (Pipeline CENTRAL)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>Hi Jeong !
Check this thread:
Duplicate Message
Regards,
Matias. -
CCMS for application errors in SAP R/3
Hi Experts,
I am working on File->ABAP Proxy scenario.
My client has configured CCMS in solution manager system to receive alerts from PI as well as from SAP ECC system.
One thing which is not clear to me is how to capture the application errors raised in ABAP proxy (server proxy) in CCMS. I am not clear on below points.
1. Is it required to trigger SALERT_CREATE explicitly in ABAP proxy to trigger alerts in case of application errors?
2. Where to define the alerts using ALRTCATDEF? Is it in SAP ECC or in SAP PI?
3. Do I need to create alert rule in PI RWB for alerts related to application errors occurring in SAP ECC?
I have read the blogs and referred the threads related to CCMS but I could not get much on above mentioned points. Could you please help me in this regard?
Thanks a lot.
Regards,
PrasadCCMS alerting is different than the alerting available with SAP PI. Therefore when you already have a CCMS setup, there is no need for ALRTCATDEF, PI RWB setup.
Regards,
Prateek -
Error while invoking the ABAP Proxy via SOAP Adapter
Hi,
My scenario involves SOAP Client invoking a webservice hosted in PI which in turn invokes the ABAP Proxy asyncronously.
SOAP Client -> PI -> ECC (ABAP Proxy) . This works fine.
Next , I have exposed the ECC Service Interface as webservice using SOA Manager transaction. Now, once the service is created using SOAManager, i replaced the XI Adapter with SOAP Adapter and provided the target URL as the URL provided by the SOAManager.
SOAP Client -> PI -> ECC (ABAP Proxy via SOAP Adapter)
With this approach, i am encountering the below error message
2009-05-29 12:17:55 Error Adapter Framework caught exception: null
2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
Any ideas on the above errror message? Any pointers or inputs will be appreciated.
Thanks,
Vinayak Kamath> 2009-05-29 12:17:55 Error Adapter Framework caught exception: null
> 2009-05-29 12:17:55 Error Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.
This is a generic error message which does not have any information about the error which has occurred.
Do you see any error messages in the SOAP client?
Regards
Stefan -
ABAP proxy exception to SOAP fault and vice versa not getting mapped
Hi there,
I have these scenario's: ABAP proxy to SOAP (AXIS framework) and the other way around, synchronous, using AAE.
When declaring the Synchronous Service interfaces we also defined error message types in order to pass system and application exceptions back to the service consumers.
The behavior we are observing is as follows;
When an exception is generated on the ABAP proxy, the error message type is correct generated and filled with the corresponding values in the ABAP proxy runtime. However, when the response arrives at the service consumer, it only contains a SOAP fault filled with some kind of generic PI mapping exception information.
1. Why is the original ABAP proxy exception not mapped/passed into the SOAP response?
2. What can we do in order to change that situation?
3. Does it has to do with the use of the AAE - Advanced Adapter Engine or the AXIS framework?
PS: We have performed a test of the Operation Mapping - OM using the ABAP exception as input and it did work correctly, so the error structure seems to be Ok.
Many thanks for your replies.
Edited by: Roberto Viana on Jul 26, 2010 8:30 PMProblem was caused by some differences in namespaces between source and target.
-
Process a PDF File to an ABAP Proxy
Hello,
Does anyone know how to process a pdf file straight to an abap proxy.
With just a flat sender file adapter without conversion to a xsd:Base64Binary field straight to a Abap-proxy.
Error message :
SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1>Request Message</SAP:P1>
<SAP:P2>CX_ST_MATCH_ELEMENT</SAP:P2>
<SAP:P3>/1SAI/TXS00000000000000000543</SAP:P3>
<SAP:P4>XML Bytepos.: 0 XML Path: Error Text: Element 'mt_pdf' expected</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_MATCH_ELEMENT; (/1SAI/TXS00000000000000000543 XML Bytepos.: 0 XML Path: Error Text: Element 'mt_pdf' expected)) Element 'mt_pdf' expected</SAP:Stack>
I HAVE READ ALL the possibilities with java coding in the module tab etc. etc.
JUST is there "simple' way to solve this.
regards meinhartHi Meinhart,
I think you need to go with Conversion agent here.
Ref: http://www.saptechnical .com/Tutorials/XI/PDF/Index.htm
This would help you....
Thanks, -
ABAP proxy with Multiple PI system and Single SAP ECC
Hello Folks,
In my current project i have 2 SAP Pi system, PI7.0 and PI7.11. Currently 80% of the interfaces are on PI7.0 and we are planning to move interfaces to new PI7.11 next year. Old environment has lot of ABAP proxies ECC is configured to send data to it.
All the new developments will be done in new SAP and i need to use SAP PI7.11 for that. I have an interface where i need to use ABAP proxy.
How can i configure ECC so that it sends new ABAP proxy interface data to new PI7.11 and old proxies to old PI7.0.
As far as i know we can make ECC point to one integration server at one time. Any thoughts or suggestion ?
Regards
InderHi,
Multiple connection to ESR in sproxy can be done by switching host value in RFC destination SAP_ESR_PROXY and for maintaining multiple PI runtime you should use subparameter for parameter SXMB_ADM->Runtime->IS_URL (you can define combination of Sender/Receiver for subparameter in transaction SXMSIF).
This way for every sender/receiver combination you can use different integration server.
Regards,
Gourav
Maybe you are looking for
-
How do I save images in mail to photos on iPhone iOS 7
How do I save images in Mail to Photos on iPhone using iOS 7?
-
How to repair corrupt \windows\system32\config\system files?
T61 will not boot to Win XP - says the \windows\system32\config\system file is missing or corrupt. BIOS hardware test of disk drive passes. When I place a Microsoft Win XP disk to attempt a repair, the message says there is no disk drive detected.
-
Regarding advenced mode option at sender,reciever file adapters
hi. can any xi prof tell about the use of advanced mode at sender,reciever file adapters. and one more thing that i foung difference is at sender adapter advanced mode there are some options like msecs to wait before modification check and the othe
-
Is it possible to output PO to a FM instead of IDoc?
When setting up PO output conditions for a vendor, I noticed that, in addition to the standard "1-Print", "6-EDI" and other standard options, there was an option "8-Special Function". I was unable to find any documentation for this, so I figured I w
-
Where can i download drivers and view manuals????
Baught a 655 max-fisr refurb and it didnt come with any of the acessories and it didnt come with software or manuals what site have this information/software.