Exception in method

Hi Friends,
The method which posts FI document throws an exception. Its shows an application error. Doc is still in parked status though the w/f is completed.
How can we handle such error ? Please advice.
Regards,
Vittalprasad

Hi
In this special case I would suggest that you either restart the workflow in question, or post the document manually.
For future reference, you should design your workflow so it handles these exceptions. If the methods are implemented correctly each exception will give you a possible outcome, on the outcome tab, in task implementation. You should activate all of these outcomes (unless your sure that they would never occur).
By doing this you have the opportunity to model your exception handling in the workflow, and thus avoiding these kind of problems.
Regards
Morten Nielsen

Similar Messages

Xi 3.0: Mail adapter fails with "exception in method process"

Hi.
I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.
Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".
I tried both async and sync case with the same result. In the sync case, the response contains:

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea???

Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.
Anyway, in my server i get a 404 for the link you suggested.
In the async case i don't get any error on the SXMB_MONI but only on the A.F.
I attach the audit log for the async case:
Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc
Time Stamp Status Thread ID Sequence No. Description
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV.
Total: 33 Entries 1020304050 messages displayed per page; this is page 1 of 1 page(s)

Java Proxy error: Exception in method methodExists

Hello all!
We are doing the following synchronous scenario: CRM->XI->JavaProxy--->Third party....
Here is the process we are following to deploy our Proxy:
1.Created EJB Module Project in NWDS
2.Import the files generated by XI into ejbModule folder from ZIP file.
3.Renamed *PortTypeImpl.template to *PortTypeImpl.java
4.Compiled all code (no errors)
5.Added all the references to the SAP libraries required (taken from our XI server):
com.sap.aii.proxy.xiruntime
com.sap.xi.util.misc
com.sap.aii.messaging.runtime
com.sap.guid
6.Codified Java Proxy codified the method <interfacename> in the <intefacename>_PortTypeImpl class.
7.Edited ejb_jar.xml to add EJBs.
8.Provided a JNDI name in the file ejb-j2ee-engine.xml.
9.Built EJB archive (no errors).
10.Created a new Enterprise Application Project and pointed build path to our EJB Project.
11.Added our EJB to the Enterprise Application project.
12.Created the references to the SAP libraries in the Enterprise Application Project in the application-j2ee-engine.xml file:
com.sap.aii.proxy.xiruntime
com.sap.xi.util.misc
com.sap.aii.messaging.runtime
com.sap.guid
13.Within the Enterprise Application Project we built an EAR file.
14.We deployed our .ear file to the J2EE Engine via Visual Admin (no errors).
15.We registered our Java Proxy on the ProxyServer, using
/register?ns=<interface_namespace>&interface=<XI_Interface_Name>&bean=<EJB_JNDI_name> &method=<name of the method implemented by you on the _PortTypeImpl>
Actually, we did the following:
url for registering the EJB:
http://ithpsrq0:50200/ProxyServer/register?ns=http://banco.popular.com.pr/xi/crm&interface=mi_AccountInfo_is&bean=popularinc.com/MiAccountInfoIs_Default&method=miAccountInfoIs
Message displayed when listing interfaces (http://ithpsrq0:50200/ProxyServer/listAll)
http://banco.popular.com.pr/xi/crm#mi_AccountInfo_is = popularinc.com/MiAccountInfoIs_Default:miAccountInfoIs
1 interfaces found
When running the interface we get the following error:
com.sap.aii.af.ra.ms.api.DeliveryException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.: com.sap.aii.proxy.xiruntime.core.XmlInboundException: Error checking method name miAccountInfoIs of remote inbound proxy bean $Proxy250: Exception in method methodExists.
Does anyone have any suggestions?
What causes a "methodExists" Exception?
Please help us,
Thanks a lot!!!

Hi,
Is this a runtime of "com.sap.aii.proxy.xiruntime.core"
please check the jars used, adding this jars will solve this i guess.
aii_utilxi_misc.jar
ejb20.jar
exception.jar
jARM.jar
sapj2eeclient.jar
sapxmltoolkit.jar
aii_msg_runtime.jar
aii_proxy_xirt.jar
Also check, application-j2ee-engine.xml and see if,
com.sap.aii.proxy.xiruntime
com.sap.aii.messaging.runtime
com.sap.xi.util.misc
com.sap.guid
You wil get the jars in XI servers, you can ftp and get the jars, but you may need to search them.
Anotherthing, always take the jars from the xi servers to be sure you are compatible with the upgrades .
Hope this solves your problem.
Anirban.

Exception in method process

Hi all,
I am configuring a scenario RFC -> XI -> Webservice. In my SOAP adapter trace, i found an error :
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can any body please suggest me the possible reasons?
Thanks and best regards,
Kulwant

try this too
com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process
and this
com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process ?
Edited by: Lawrence on Apr 22, 2008 8:17 AM

SOAP Adapter: Exception in method process

Hello Experts,
We are getting from time to time on the Receiver SOAP Communication Channels the folowing error:
Delivery of the message to the application using connection AFW failed, due to: Exception in method process.
We are getting this error on both types of messages - sync and async.
I did a search on SDN and Notes, but didn't found any description or solution for this error.
Can someone please help with this error?
Thanks in advance!

Here are some details extracted from the log:
Date : 07/30/2008
Time : 8:44:15:783
Message : Error during processing local bean: localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Severity : Error
Category :
Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)
Application : sap.com/com.sap.aii.af.app
Thread : output
Datasource : 1217412862462:/usr/sap/xxx/xxx/j2ee/cluster/server1/log/defaultTrace.trc
Message ID : 001CC4B7988E00A5000268B100000CB3000453381549AFAE
Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean
Argument Objs :
Arguments :
Dsr Component : xxx
Dsr Transaction : 989219405e0211ddc88b001cc4b7988e
Dsr User : Guest
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean
ThreadObject : output
Transaction : SAP J2EE Engine JTA Transaction : [2dffffff91ffffffbdffffffe3040ffffffb0]
User : J2EE_GUEST
Hope this will help somebody to get the clue what is causing this error.

Getting Inbound Java Proxy Exception in method "onMessage"

I have built an Inbound Java proxy, deployed the EJB, viewed it in the J2EE admin tool, registered the JPR settings (also listAll, reviewed results, looks OK), configure the XI scenario. When I run the XI scenario using the Runtime workbench I get the following error in the BPM Synchronous Send step (calling the Java Proxy)
"com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method onMessage".
Does anyone have any suggestions?
What causes an "onMessage" Exception?

Thanks Sudhir Here is the process I am following to deploy my Proxy, would you please validate it. Created EJB Project in NWDS, unziped XI gened proxies into ejbModule folder, renamed *PortTypeImpl.template to *PortTypeImpl.java (will add real code later), compiled all code (no errors), edited ejb_jar.xml to match your suggested format, can view EJB Candidates (and see my Proxy Bean), built EJB.JAR file (via Wizard), created new Enterprise Application Project and pointed build path to my EJB Project, within the Enterprise Application Project I built an EAR file (which includes the "EJB Project JAR File", Deployed Enterprise Application Project to the XI J2EE Engine. I can log into XI J2EE Admin and see my EJB Project and the Proxy Bean I am trying to execute. Is this the process you used to deploy the proxy bean?
Also you you turn on JPR Tracing to see what parameters are passed into the JPR engine?

Session bean "Exception in method create()"

Hello,
I have a session bean which is consuming entity bean and session bean is published as webService now when I call create method of entity bean from session bean it says "Exception in method com.syntel.exam_tool.entityBeans.tabExamTable.TabExamLocalHomeImpl0.create()."
But my create method of entity bean is blank I am not getting from where this exceptions is being thrown.
below is the code from session bean wehre I am calling entity bean
javax.naming.Context ctx;
ctx = new InitialContext();
TabExamLocalHome tabExamLocalHome = (TabExamLocalHome) ctx.lookup("java:comp/env/ejb/TabExamBean1");
TabExamLocal tabExam = tabExamLocalHome.create();
Please help me ins this problem.
Thanks

Hi Janeth,
below is the stack trace
com.syntel.exam_tool.entityBeans.tabExamTable.TabExamLocalHomeImpl0_0.create(TabExamLocalHomeImpl0_0.java:343)
com.syntel.exam_tool.sessionBeans.examTool.ExamToolBean.findByPassingScore(ExamToolBean.java:126)
com.syntel.exam_tool.sessionBeans.examTool.ExamToolLocalLocalObjectImpl0_0.findByPassingScore(ExamToolLocalLocalObjectImpl0_0.java:247)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke(Method.java:324)
com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
SoapServlet.doPost(SoapServlet.java:51)
javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged(Native Method)
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
please help me in this as I am not getting where the problem is
Edited by: new to netweaver on Sep 9, 2009 11:15 AM

Exception in method when trigger PDFObject WS

Hi,
wonder anyone do before the PDFObject Tutorial.
as i try to create a new Web Services the concept is about the same but different types...
but somehow i encounter errors...
as the WS has 4 methods
createPdf (test.types.p1.CreatePdf parameters)
extractData (test.types.p1.ExtractData parameters)
getData (test.types.p1.GetData parameters)
getItemValue (test.types.p1.GetItemValue parameters)
but then when i trigger the createPDF methods i get this error
Exception in method com.sap.tut.ejb.pdfobjectservices.PdfObjectLocalLocalObjectImpl0_0.createPdf(java.lang.String,java.lang.String,java.lang.String,java.lang.String).
extractData
Exception in method com.sap.tut.ejb.pdfobjectservices.PdfObjectLocalLocalObjectImpl0_0.extractData(java.lang.String).
getData
Exception in method com.sap.tut.ejb.pdfobjectservices.PdfObjectLocalLocalObjectImpl0_0.getData(java.lang.String).
so wonder how to overcome it.. is there any mistake i have done or errors i have make so have this results
Regards
Jia Jun

now is i alway have exception on Exception in method createPDF.
so what should i do?

Java system error: Exception in method processFunction in BEX Broadcaster

Hi All,
We are trying to broadcast a BI7 Webtemplate with our enterprise portal. While clicking on "Create New setting " iam getting the error " Java system error: Exception in method processFunction ".
Detailed error description is
*Diagnosis
An error occurred in the BI components on the SAP J2EE Engine.
System Response
Procedure
Contact your system administrator to have the error analyzed in detail.
Procedure for System Administration
Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.
Notification Number RSBOLAP 018 *
Please let us know how to proceed

Hi,
This is a configuration issue. All components on the J2EE stack have to
be on the same SPS level. Please make sure of this as a first step.
For special requirements of BI with regards SPS levels please see SAP
Notes 873996 and 1013369.
Please run the latest version of the support desk tool as per SAP note
937697 and ensure that there is no error and then check for the issue
again.
Otherwise, I suggest you open a BW-BEX-ET-BC msg with SAP.
Rgds,
Colum

Webservice returned with exception in method 'isConnectionLoopbackAlive'

Hello,
during monitoring of last 24 hours logs i found message:
<b>Webservice returned with exception in method 'isConnectionLoopbackAlive'
category: /Applications/CAF/KM
Application: sap.com/irj
Location:com.sap.portal.prt.cafkm.com.sap.caf.km.service.ConnectionTestService.isConnectionLookupAlive(String)
</b>
can anybody help me? what does it mean?
Denis
ip
Edited by: Denis Yugay on Mar 18, 2008 5:10 AM

Hello, Vincent.
Situation is same after rebooting server.
Denis
Edited by: Denis Yugay on Mar 20, 2008 5:17 AM

Looks like some Exceptions' getMessage() methods return null

Looks like some Exceptions' getMessage() methods return null instead of the message.
-Andrew

snidely_whiplash wrote:
Looks like some Exceptions' getMessage() methods return null instead of the message.
-AndrewDoes it return a null object, or does it return "null" as a String? The latter may be a case of using the message from a wrapped exception, which in case of a NullPointerException is frequently null (if the NPE was not constructed intentionally with a message).
BR,
Robert

SOAP Runtime exception: 1023 method IF_SOAP_TRANSPORT_BINDING~receive

SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: HTTP COMMUNICATION FAILURE")
SOAP Runtime exception: 1023 occured in method IF_SOAP_TRANSPORT_BINDING~receive of class CL_SOAP11_HTTP_TPBND at position 1
Getting the error above when making a web service call to external web service. Used to work all the time. Getting the error all the time now.

Hi.
Check the response. Sometimes this error occurs due to an empty response.
Regards.
Rafael Rojas.

Adding throws exception to methods

I using spring hibernate orm.SO I have Service layer which internally calls dao and this service layer is called by web.
for example
     @Override
     public List<StgAuditGeneral> findAuditsByStatus(StgAuditSearchDTO stgAuditSearchDTO) {
          return ((StgAuditGeneralDAO)(GenericDAO)(entityDao)).findStgAuditsByStatus(stgAuditSearchDTO);
     }now this method does not throw any checked exceptions it might throw unchecked exceptions like hibernate unchecked exceptions if something is wrong with query etc, Is it a good practice to add throws MyCustomException to all my service methods ?

miro_connect wrote:
I using spring hibernate orm.SO I have Service layer which internally calls dao and this service layer is called by web.
for example
     @Override
     public List<StgAuditGeneral> findAuditsByStatus(StgAuditSearchDTO stgAuditSearchDTO) {
          return ((StgAuditGeneralDAO)(GenericDAO)(entityDao)).findStgAuditsByStatus(stgAuditSearchDTO);
     }now this method does not throw any checked exceptions it might throw unchecked exceptions like hibernate unchecked exceptions if something is wrong with query etc, Is it a good practice to add throws MyCustomException to all my service methods ?If there is risk involved in using you server layer class then yes... but only if you expect that the next layer can do something useful with it.

MDM ABAP API exception using method invoke_matching

Hi,
I am using below calss in MDM ABAP API. If i can use small records
source (1000) target (1000) it is working fine. If i can use source (1000)
Target ( 40, 000) i am getting exception ( kernal exception ).
Please could you advise do i have to set any parameter.
CALL METHOD lr_api->mo_core_service->invoke_matching
EXPORTING
iv_object_type_code = 'MDM_BUSINESS_PARTNERS'
iv_strategy_id = ls_matching_strategy-strategy_id
is_matching_filter = ls_matching_filter
iv_wait_for_invocation = 'X'
IMPORTING
ev_matching_task_id = lv_matching_task_id
ev_matched_record_count = lv_matched_record_count.
Thanks,
Anil

Thank you Andreas its working fine. I am getting new issue
if i can filter result vs result or result vs selected or sleeted vs result.
I am passing the values in is_matching_filter.
matching_scope = 1 or 2.
selected_records = ( query record ids)
query_records = ( i am not passing anything).
1. If i can select source and target values same 2. Filter 2 vs 2
its working fine. Remaining scenarios its not working. Please
help me.
CALL METHOD lr_api->mo_core_service->invoke_matching
EXPORTING
iv_object_type_code = 'MDM_BUSINESS_PARTNERS'
iv_strategy_id = ls_matching_strategy-strategy_id
is_matching_filter = ls_matching_filter
iv_wait_for_invocation = 'X'
IMPORTING
ev_matching_task_id = lv_matching_task_id
ev_matched_record_count = lv_matched_record_count.
Thanks,
Anil

To Raise an Exception: which method is more appropriate

Hi Friends,
I am using method report_error_message to raise exception but it is not stopping the execution sequence of the application.
I need to show the exception for mandatory check for the UI field when we click on any action buttons in the screen.
Please suggest me which method is suitable and explain the parameters in that method.
Regards,
Lakshmi Prasad.

Hello Lakshmi,
you can use REPORT_FATAL_ERROR_MESSAGE method to stop the further processing.
BR, Saravanan

Exception in method

Similar Messages

Maybe you are looking for