on 10-22-2008 5:33 AM
Hi,
I am testing file to proxy scenario in SPROXY tcode,by giving the xml payload,I am getting the following error "APPLICATION_ERROR".Can you please tell me why did error is occuring
<?xml version="1.0" encoding="utf-8" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<ERROR href="#o76" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_XMS_SYSERR_APPLICATION id="o76">
- <CX_ROOT>
<TEXTID>4349F3B101039A42A05904CB12F7FA0E</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>203</PROGID>
<CONTID>2508</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_XMS_SYSTEM_ERROR>
<ID>APPLICATION_ERROR</ID>
<P1 />
<P2 />
<P3 />
<P4 />
<INFO />
<CATEGORY />
<AREA />
<RETRY />
</CX_XMS_SYSTEM_ERROR>
- <CX_XMS_SYSERR_APPLICATION>
<RETRY_MODE>M</RETRY_MODE>
- <FAULT_MSG>
<NAME>***********_MT</NAME>
<NAMESPACE>urn:***************</NAMESPACE>
</FAULT_MSG>
</CX_XMS_SYSERR_APPLICATION>
</cls:CX_XMS_SYSERR_APPLICATION>
</asx:heap>
</asx:abap>
Thanks
Hello,
I think there is problem with the XML file....
Download the xml file from SXMB_MONI and use the same in SPROXY transaction..
Regards,
Sreeni
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI!
I just want to tell this that not to miss this information while configuring the PROXY Scenario...
. PRE-REQUISITES to be take while doign PROXY Scenario..:
The prerequisites to configure ABAP Proxies are as follows:
Configurations required at the ECC System:
1 CREATE RFC DESTINATION OF TYPE HTTP IN THE ECC SYSTEM FOR CONNECTING ECC SYSTEM TO SAP XI:
Configuration Details:
Following Inputs are required for technical settings
RFC Destination: GIVE YOUR RFC DEST NAME (EX: RFC DEST XXXX)
Connection Type: Http
Target Host: XI System Name (*******)
Service Number: HTTP Port name (5*****) (available in Tcode SICF)
Path Prefix: /sap/XI/engine
2 CONFIGURING APPLICATION SYSTEMS LOCAL INTEGRATION ENGINE: Go to Transaction SXMB_ADM
Choose Edit u2192 Change Global Configuration Data.
Select Role of Business System: Application system
Corresponding Integration Server: dest: // RFC DEST XXXX (Created in step 1) Under Specific Configuration Data you can specify additional configuration data.
Select the relevant category under Specific Configuration Data. Choose Change Specific Configuration Data. Add the following configuration:
Category: RUNTIME
Parameters: IS_URL
Current Value: dest:// RFC DEST XXXX.
3 CONFIGURATION OF THE INTEGRATION ENGINE:
Connection between Business System and System Landscape Directory:
Create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection.
While creating RFC Destination of type TCP/IP we need to give the Program IDu2019s as LCRSAPRFC_SystemID and SAPSLDAPI_SystemID. Here SystemID is the system id of XI System. Here it is LCRSAPRFC_P7R and SAPSLDAPI_P7R.
These program IDs must be registered in the SAP J2EE Engine of the Integration Server host.
Maintain SLD access details in Transaction SLDAPICUST.
Note:
If there is a HTTP error during connection, first run transaction SLDCHECK in the Business system. Also check whether the HTTP connection is working fine.
Also please check once go to
4. Also please go to RWB-->Communication monitoring and check your Communication Channel Status
whether it was green or RED...and also check the AUDIT LOG..
5. Suppose if any errors are there or not even though once go to RWB--MEssage Monitoring and check on
which basis and on which part it was strucked I mean whether the partiular message fails at Integration
Engine level or else ADapter Engine level... and finally Check AUdit log..
I hope it will be useful to you in final case...Suppose if it is useful to you please close this and award points to the repective contributors if it is useful to you..
Regards:
Amar Srinivas ELi
I found the following error in SAP R/3-SXMB_MONI in call inbound proxy.Can anyone tell me why this error is comes.
*Error* tab in call inbound proxy
<?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="urn:***************MT</SAP:ApplicationFaultMessage>
<SAP:Stack>The application triggered an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Payload Tab in call inbound proxy in SXMB_MONI
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:****************MT xmlns:nr1="urn:****************">
- <standard>
<faultText>Error Records in the Input File</faultText>
- <faultDetail>
<text>Following are the Errors in input records where Division is SA and Record ID is ER</text>
</faultDetail>
- <faultDetail>
<text>Error in document: BKPFF $ R31</text>
</faultDetail>
- <faultDetail>
<text>Balance in transaction currency</text>
</faultDetail>
</standard>
</nr1:************_MT>
Thanks
Edited by: guest xi on Oct 28, 2008 12:49 PM
Hi,
Go through this sap note for solution.
SAP Note Number: 1064346
Regards,
Sarvesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Guest,
"Application Error" it means the Data problem.
This error shows "System Error" also. So u can check is their communication connection between XI to R/3
1) Check ur HTTP Destination
2) Check RFC Destination between XI & R/3 system
3)Check your test Message Mapping, Its successful or not
Regards,
Sateesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.