Inbound proxy failed in ECC

Hi All,
Inbound proxy failed in ECC with below error Please help.
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
<SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
<SAP:P2>ZCL_P2F_IS_AGILE_TO_SAP</SAP:P2>
<SAP:P3>P2F_IS_AGILE_TO_SAP</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during proxy processing An exception with the type CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor declared in a RAISING clause The database returned a value containing an error</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Chaitanya Naru

Hi Chaitanya,
Looks like the ABAP code failed during a call to DB. You would have to sit with ABAPer fot this to debug and see where exactly the exception is being raised. Set a debug point in Proxy code and debug the message. You can use sproxy to test this.
Regards,
Sanjeev.

Similar Messages

Inbound proxy message serialization

hi, i have an inbound proxy on SAP (ECC) which receives batch data. i need to serialize this i/b flow of data on SAP which come here through XI from one legacy system. appreatiate earliest response.
best regards
neeraj

Yeah, thats fine, but what is the format in which the validation system sending data to XI ?. You might have configured a sender adapter in XI for that system to send the data to XI right ? So in the Sender communication channel, you specify EOIO as quality of service and give a queue name ( can be any anything )
example
Validation system-->Sender CC>XI(IE)---->ECC
( with EOIO n queue name QUEUE1)
Once you do this, the same queue will be used to transfer data from XI to ECC as well thus ensuring that data is received in the same order as it was sent.
I hope this helps you.
regards,
Advait

Managedavailability error about inbound proxy probe failing

getting a managedavailability error about inbound proxy probe failing.
what does the inbound proxy probe do, and why does this error reference forefront, when I do not have MS forefront installed?
below are the details:
The inbound proxy probe failed 3 times over 15 minutes.
The inbound proxy probe failed 3 times over 15 minutes. No connection could be made because the target machine actively refused it 127.0.0.1:25 Probe Exception: 'System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target
machine actively refused it 127.0.0.1:25 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SimpleSmtpClient.Connect(String server, Int32 port, Boolean disconnectIfConnected) at
Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.MeasureLatency(String reason, ActionWithReturn`1 cmd) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.MeasureLatency(String reason, ActionWithReturn`1
cmd, ConnectionLostPoint connectionLostPoint) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection() at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken) at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.b__0() at System.Threading.Tasks.Task.Execute()' Failure Context: 'No connection
could be made because the target machine actively refused it 127.0.0.1:25' Execution Context: '' Probe Result Name: 'OnPremisesInboundProxy' Probe Result Type: 'Failed' Monitor Total Value: '3' Monitor Total Sample Count: '3' Monitor Total Failed Count: '0'
Monitor Poisoned Count: '0' Monitor First Alert Observed Time: '1/27/2015 4:46:45 PM

Hi,
Please use the Get-ServerHealth and Get-HealthReport commands to check result.
Here is a related blog for your reference.
http://blogs.technet.com/b/exchange/archive/2013/06/26/managed-availability-and-server-health.aspx
Best regards,
Belinda Ma
TechNet Community Support

Outbound proxy in Inbound proxy

Hi Experts,
I am doing two way interface. JDBC asyn - proxy-JDBC asyn
I am calling outbound proxy in inbound proxy here.
While i am calling it is giving HTTP connection error.
So can i call outbound proxy in inbound proxy ????
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>

Outbound proxy inside inbound proxy scenario usually works fine. But few suggestions,
1. Check if the message is failing in request side of asynchronous scenario. If this is the case then I think the error which you are getting is probably due to improper channel configuration.
2. If problem is not the one mentioned in point 1 above then, test the proxy in transaction SPROXY of ECC as to whether outbound proxy is called while inbound proxy is executed manually in transaction SPROXY . Once you execute the inbound proxy then go to transaction "SXMB_MONI" of ECC to check whether a message which outbound proxy is required to send to PI appears over there, if it appears there that means there is no issue on programming of proxy.
Hope it might help in finding resolution.
Thanks,
Amit

Issue while inserting a BDC program in Inbound Proxy.JDBC-- PI-- SAP.

The scenerio is jdbcsender-sappi-inboundproxy(ECC6.0).
The issue is related to SAP Plant Maintenance Module where We have a requirement for creating Maintenance item
programmatically from (SQLDatabase)Legacy Data for one of the interface.
since there are no standard BAPIS/Idocs or function modules available from SAP side for creating the maintenance item. So I
have written BDC program and with the help of submit statement in inbound proxy program, I am calling BDC program for
creation of the maintenance item.
When I tested the program independently on proxy side the Maintenance Item is getting created successfully but when I
executed from end-to-end ie. SQLDATABASE->SAP PI-->SAP. The message is getting strucked into the queue and queue got stopped on SAP.
ECC side and the status of the message is scheduled state on SXMB_MONI transaction of SAP ECC.
As the message is in scheduled state multiple number of Maintenance Items are getting created with the same values.
Has any one of our SAP friends, encountered this type of issue while inserting a BDC program in inbound proxy, please help
in fixing this issue. FYI... I am using sap pi7.0 with service pack 24 and ecc6.0
Waiting for your kind expert guidance...
cheers,
Ram

Raj,
Thanks for the reply. I have tried registering the queues but still the same problem. the message got stuck in the queue of ECC and showing below message in queue.
function module StatusText
SXMS_ASYNC_EXEC connection closed (no data)
I have checked in the forums especially for this issue but no one has provided the answer for this.
Thanks and Regards
Ram

Special character " (quote) in inbound proxy

Hi folks,
We have a scenario in which inbound proxy is implemented on SAP side. I am getting following error:-
Error during XML => ABAP conversion (Request Message; error ID: CX_ST_DESERIALIZATION_ERROR; (/1SAI/TXS9457077FA0DEC03F30D0 XML Bytepos.: 988 XML Path: MT_SLM_INT30_LUPReviewFromLUPS(1)Title(16) Error Text: Data loss occurred when converting PROPOSED 8" U/G HRDH & ROUTE Kernel ErrorId: CONVT_DATA_LOSS)) An error occurred when deserializing in the simple transformation program /1SAI/TXS9457077FA0DEC03F30D0 Data loss occurred when converting PROPOSED 8" U/G HRDH. KHUFF GAS WELL-1050 & COMMUNICATION ROUTE FOC TO HRDH RH-K6}
Could you please suggest me what is wrong in the data PROPOSED 8" U/G HRDH & ROUTE. I guess it is due to the use of " in the data. Could you please help me in this?
Regards,
Sami.

Hi,
The problem was with the length of that field. That field was created in XI with max length 80. During proxy generation, corresponding abap field was created with 80 char. In the message, data for that field was 81 characters At runtime, when proxy runtime tried to map the xml to corresponding abap object, it failed.
While testing in Sproxy transaction when tried to execute after removing quote(") it was successful, as length was reduced to 80. So i went under impression that it is not working because of quote(").
Thanks for your rersponses.

Urgent: Error in Inbound Proxy in SCM system

Hi All
Please give your inputs to solve following problem I am facing. I am working on XI first time so please help me out to solve the following problem. Please let me know if you need any more info.
Thanks a lot for your help guys.
I am sending ORDERS.ORDER05 from R/3(ECC6.0) to SCM (5.0) through XI. I am using standard message interface ReplenishmentOrderNotification_In to send data to ICH configured on SAP SCM System.
I am using XI adapter at receiver end. My message successfully going to SCM. SXMB_MONI, its giving error. After clicking on error flag it displays a table with 3 entries, please find them below.
1. Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202027) 032(/SCMB/ORDER)
2. TST 20080429202851 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
3. Partner key(s) not found 042(/SCMB/MDL_BASIC)
Please find the XML message from ERROR node from Inbound Proxy
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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/SCMBasis/Global">ReplenishmentOrderNotificationFault</SAP:ApplicationFaultMessage>
<SAP:Stack>Application has thrown an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please find contents of Trace XML message from Inbound proxy
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<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/?type=receiver</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="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<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="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-04-30T01:31:18Z 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 = 48165647672B03B5E10080000A0C640C</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler 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="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ReplenishmentOrderNotification_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SCMBasis/Global</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-04-30T16:19:34Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 000</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-04-30T20:52:28Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 002</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RAJARANGA</Trace>
<Trace level="1" type="Timestamp">2008-04-30T22:34:19Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 004</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RAJARANGA</Trace>
<Trace level="1" type="Timestamp">2008-04-30T22:35:19Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 006</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RAJARANGA</Trace>
<Trace level="1" type="Timestamp">2008-04-30T22:41:24Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 008</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T00:07:18Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 010</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T00:30:07Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" 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="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 012</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T00:53:39Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 014</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<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="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T01:04:22Z 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 RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
Regards
Amol

Hi All
Thanks for your inputs, we are a step ahead now. We applied few notes I will be posting details soon. At the moment we stuck at one poin, its giving a configuration related error. Please find the process log from SXMB_MONI from SCM system. It is saying Buyer missing in fact we have configured BP01 in SCM system and same we are getting from ECC system.
Hope to hear from you soon. Thanks a lot for your inputs.
ReplenishmentOrderNotificationFault
Proxy Class (Generated)
Detailed Information
Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202043) 032(/SCMB/ORDER)
The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'BEFORE_CONVERSION' has been run 080(/SCMB/BIF_COMMON)
TST 20080508141414 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
The active implementation of BAdI '/SCMB/BIF_MI_PARTYID' 'BEFORE_MASTER_DATA_ACCESS' has been run 080(/SCMB/BIF_COMMON)
Start generic process type determination 000(/SCMB/BIF_CU)
Process type could not be determined - search for standard process type 002(/SCMB/BIF_CU)
Standard process type (ICH) determined successfully 013(/SCMB/BIF_CU)
Start action determination for addresses 070(/SCMB/BIF_CU)
No Customizing found; standard action is 'map all addresses' 072(/SCMB/BIF_CU)
End of action determination for addresses 071(/SCMB/BIF_CU)
Start partner role determination 060(/SCMB/BIF_CU)
Partner role is 'buyer (sold-to party)' 063(/SCMB/BIF_CU)
Partner role determination completed successfully 061(/SCMB/BIF_CU)
TST 20080508000000 (type CreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
The active implementation of BAdI '/SCMB/BIF_MI_ITMBPRT' 'BEFORE_MASTER_DATA_ACCESS' has been run 080(/SCMB/BIF_COMMON)
The active implementation of BAdI '/SCMB/BIF_MI_PRODID' 'BEFORE_MASTER_DATA_ACCESS' has been run 080(/SCMB/BIF_COMMON)
TST 20081027000000 (type DeliveryPeriodStartDateTime, item 00010, sched. line 1) is local, interpret. as UTC 024(/SCMB/BIF_MI)
Order 4500000105 item 00010: 'DeliveryPeriodEndDateTime' missing in schedule line 1 090(/SCMB/ORDER)
The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'AFTER_CONVERSION' has been run 080(/SCMB/BIF_COMMON)
BOL processing started for object /SCA/CL_SVORDER process name REPLORDER 006(/SCMB/DM_BOL)
Start: read ODM order 250(/SCMB/ORDER)
End: read ODM order 251(/SCMB/ORDER)
Start: validation framework 254(/SCMB/ORDER)
Validation started for validation profile POC1 (ICH - REPLORDER - HEADER) 606(/SCMB/DM_BOL)
Business partner 'buyer' is missing in order 4500000105 021(/SCMB/ORDER)
Validation for val. prof. POC1 (ICH, REPLORDER, HEADER) ended with errors and warnings 608(/SCMB/DM_BOL)
End: validation framework 255(/SCMB/ORDER)
Start alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 504(/SCMB/ANOT)
End of alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 525(/SCMB/ANOT)
Start: write ODM order 252(/SCMB/ORDER)
End: write ODM order 253(/SCMB/ORDER)
BOL processing ended for object /SCA/CL_SVORDER process name REPLORDER 007(/SCMB/DM_BOL)
End inb. proc.: ReplenishmentOrderNotification (ReplenishmentOrder ID ) 033(/SCMB/ORDER)

Error/Exception handling in PI (Inbound Proxy)

Dear All,
I need some help in PI Error handling.
If PI sends data to an ABAP inbound proxy and an error occurs in PI because of type mismatch (e.g. Unable to convert date).
This error is persistent in the PI monitor, but how do I let the Sender know that an error has occured?
regards,
Piyush

Hi,
I understand that you have a doubt, if PI sends data to ABAP inbound proxy and an alert reaised due to type mismatch. Now, you would like to know how to acknowledge that sender to know about the alert?
First of all, get the payload and test in the message mapping, you will get know where exactly you got the error or check in the trace in Moni. You need to identify the issue and let the user know why exactly it failed.

Can I supress BPM for Asyn outbound and syn inbound proxy interface

Hi all,
Is there any other alternate to remove the BPM at asyn outbound and syn inbound proxy interface. Reason because I can create another outbound proxy interface at the receiver. But at receiver side we already invested huge code to develop the sync server proxy. So the intension is, with out disturbing the code Can I make the message flow with out BPM?
Because the reason of removing BPM is for a simple interface like this I don't want to use BPM. souce is JDBC and receiver is ECC 6.0. I know with out BPM it can not be achieved but in PI 7.1 EHP 1 by any chance can we do?
I mean during response mapping from server proxy shall we use look up function to achieve?

This bean I have to use at sender channel right?
Yes
I mean is it is limited to JMS adapter?
No
You can find more information in the Wiki which deals with FILE to RFC synchronous...using the above Module

Sync Async using proxies ( Calling Outbound proxy from Inbound proxy )

I'm trying to generate Asynchronous Outbound message from the Synchronous Inbound message message due to a requirement. My question is : is it really possible to develop such a scenario?. I'm getting weird error such as Kernal exception etc. Please let me know if you have developed such scenario and what should we do dfifferently in such scenarios?. Thank you for any suggestions.

Hi,
This error has has nothing to do with Calling Outbound Proxy from from Inbound Proxy. The scenario which you are telling is very much possible.
It looks like there is some problem in your proxy code while calling RFC from within there or something like that. Try catching the exception and see what is the exact error or put in debug mode and see the step where exactly your code is failing.
Use the following links for Catching Exception in Proxy
Inbound ABAP Proxy Trace and error handling
Handling Exceptions
ABAP Server Proxies - Fault Handling
Exception handling in integration processes
ABAP Proxy and fault messages
/people/bhanu.thirumala/blog/2006/02/07/abap-proxy--xml-to-abap-transformation
Thanks
Amit
Reward point if answer is helpful

Generated Class is not called by Inbound Proxy

Uploading data to Ztable of ECC by using inbound proxy.
The messages are tranfered to SAP ECC from SAP XI.
Monitoring in SXMB_MONI in SAP XI DEV can see Success flag
Monitoring in SXMB_MONI in SAP ECC can see inbound message stored in QUEUES only.
I configured the Application Integration Engine as per the help document.
In Reciever XI Adapter set the addressing type URL.
Coding is correct in the method of the generated class.
Let me know if any configurations yet to be done.
Let me know how to proceed furthur.
ThankYou in Advance.

hi
Go to SMQR of the ECC and register and activate the queues again.
Also ensure that u are implementing the correct methods of the proxy
EXECUTE-SYNCHRONOUS / EXECUTE-ASYNCHRONOUS
rgds
Arun

PI inbound proxy

Dear All,
We are planning build one proxy to recieve the file from thirdy party to SAP though PI system . So I have couple of questions in this regard.
1) How is this proxy in ABAP side trigger to run ? Do we need to schedule any background job run this in ECC side or PI will trigger the program to run ?
2) Can we put the files in apllication server using ABAP inbound proxy ?
3) Can we include selection screens to the inbound ABAP proxy program ?
4) Is there any options in proxy to handle DATA errors in the file ( Like in IDoc we can see 51 status if any failure and we can reprocess )
5) Can emails sent from proxy for any processing errors and data mismatch ( send and receive ) .
6) How can we monitor and reprocess the proxy ( sxmb_mony ? any )
Thanks all,
Vinay.

Hi Vinay,
1) How is this proxy in ABAP side trigger to run ? Do we need to schedule any background job run this in ECC side or PI will trigger the program to run ?
Ans: When your File Communication channel picks a file, a process will start and once the message has been transformed in PI, PI will automaticall trigger the inbound Proxy.
2) Can we put the files in apllication server using ABAP inbound proxy ?
Ans: What do you mean by this? Are asking if the ABAP inbound proxy can save the message as a file in the application server? If yes, it is possible. You just need to modify the implemented class of your Inbound proxy to save a file in the app server.
3) Can we include selection screens to the inbound ABAP proxy program ?
Ans: Yes, you may add codes in your implemented class to call and use a selection screen.
4) Is there any options in proxy to handle DATA errors in the file ( Like in IDoc we can see 51 status if any failure and we can reprocess )
Ans: Yes, you may validate the incoming message of your inbound proxy and apply exception handling if error occured.
5) Can emails sent from proxy for any processing errors and data mismatch ( send and receive ) .
Ans: I think this is possible in ABAP coding. But if you wanted to send notification emails when transformation error occurs during mapping, you can do it using Alert Configuration.
6) How can we monitor and reprocess the proxy ( sxmb_mony ? any )
Ans: Since your scenario is File to ABAP proxy, the only way to reprocess is to send/place another file on the source directory to trigger the inbound proxy.
Let me know if this helps.
Regards,
Jenny

Inbound proxy with system error.

Hi Experts,
                I desighned an inbound proxy scenario which is file to ECC.
               I test the proxy from 'SPROXY" t.code.
               Because of wrong data, it throws an exception as below.
       - <cls:CX_XMS_SYSERR_PROXY id="o125">
- <CX_ROOT>
<TEXTID>8BB7CA726FE56F43BC4A06197ABFE5FD</TEXTID>
<PREVIOUS href="#o117" />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>242</PROGID>
<CONTID>668</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_XMS_SYSTEM_ERROR>
<ID>PARSE_APPLICATION_DATA</ID>
<P1>Request Message</P1>
<P2>CX_ST_DESERIALIZATION_ERROR</P2>
from above, we can tell this is a system error because this exception caught by class'CX_XMS_SYSTEM_ERROR'.
If this is a system error, it has to show a system log in 'SM21'.
but, it's not appearing.
if my understanding was wrong,let me know where it will display these logs.
please let me know your opinion on this.
regards
mahesh.

hai
you can check the below link to debug the application
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3dfac358-0d01-0010-5598-d4900e81a30c
check the t.code sxmb_moni in the receiver SAP
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Inbound proxy debug

Hi Gurus,
I am sending the XML message from PI to SAP ECC system using inbound proxy.
I have to debug the inbound proxy at runtime.
I mean when the message is sent to SAP ECC system I want to debug the proxy code.
Is there any transaction to debug the proxy code.
Any help appreciated.
Thanks,
Jay

Hi,
Follow this abstracts taken from one of the thread
go to TCode: SPROXY in SAP system and find your Inbound Message interface from ur software component.
double click on the ABAP interface and get into the execute_asynchrounous method. place a break point there or place a break point in the program which is used to update the table
come back to the Inbound interface and press F8 or execute the interface. take the payload from SXMB_MONI in SAP system and paste the payalod. now investigate..
regds
Ramesh

Inbound proxy by HTTPS

Hi All,
i have to call from PI inbound proxy on ecc using https(and xi adapter) . how to configure it ? where to import certificate ? nwa or strust ?
Regards
Maciej

for ABAP proxy security, refer - vhttp://help.sap.com/saphelp_nwpi711/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm

Inbound proxy failed in ECC

Similar Messages

Maybe you are looking for