Error message in SAP Easy DMS

Hi there,
Is there anyone who has come across the error message "Classification data can only be maintained using a change number" in SAP Easy DMS. How can one resolve this issue?
Patrick

Dear Patrick,
please see my suggestion in thread http://forums.sdn.sap.com/thread.jspa?threadID=1911999&tstart=0.
Best regards,
Christoph

Similar Messages

SAP Easy DMS Error in Searching a Document.

Hello Guru,
A user can log in in SAP Easy DMS, but when doing the search on it he gots error pop-up message "The parameters is incorrect" how can we solve this he cannot search any document in his easy DMS.

Hi,
Refer below mentioned links to properly use search functionality in Easy DMS
https://help.sap.com/saphelp_edm71/helpdata/en/48/db51333aa369cae10000000a42189b/content.htm
https://help.sap.com/saphelp_edm71/helpdata/en/48/d8f373e5975430e10000000a42189b/content.htm
Regards,
Deepak Kori

Error Message from SAP GUI

Hi,
I have designed a Custom screen for one of my requirements. However when the screen is displayed, I am facing an error message from SAP Front End Server that says " Erroneous data received from server. Application may not work correctly".
What could be the reason ?
Thanks & Regards,
Venkatesh.

Hi,
Please check the belos SAP notes
1453114 Maximum string length
1161022 Dialog box "Erroneous data received from server"
1524462 - Erroneous Data received from server. Application may not work correctly.
Regards,
Naveen.

SAP Easy DMS / KPRO / Content Server

Dear Fiends,
We have a requirement to configure the SAP Easy DMS integrating with ECC 6.0 EhP6 application. I am trying to understand the base application components which are needed to set-up the landscape.
My questions are:
1 - Do we need SAP Content Server as part of the SAP Easy DMS configuration to store the attachments? (or) Can we use shared file system and link it to SAP Easy Document Management directly to store the attachments?
2 - Do we also need KPRO along with SAP Easy DMS?
Thank you,
Sri

Hello Tilak,
Thank you for the response.
Based on your comment, We have to use KPRO regardless whether we use Content Server or not with Easy DMS.
Is KPRO a additional installation or is it part of standard SAP application and available via transaction codes?
Thank you,
Sri

SR Log Error - | Message : com.sap.esi.uddi.sr.api.exceptions.SRException

Hi,
We are getting below errors in /nwa/logs. We have our PI (7.11) and Service Registry configured on the same server. And have out CE (7.2) system connected to this service registry. Does any one has similar experience? Please let me know if you have any solution for the same.
SR Log Error
| 11-Nov-11 14:10:45.568
| Method   : getClassificationSystems()
| Class    : com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean
| ThreadID : 146
| Message : com.sap.esi.uddi.sr.api.exceptions.SRException: No classification system found for ID 'QName: Namespace= http://uddi.sap.com/classification; Name= ConfigurationFlags'
|
|       com.sap.esi.uddi.sr.impl.common.Utility.cs2srException(Utility.java:122)
|       com.sap.esi.uddi.sr.impl.ejb.ServicesRegistryBean.getClassificationSystems(ServicesRegistryBean.java:242)
|       sun.reflect.GeneratedMethodAccessor1325.invoke(Unknown Source)
|       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|       java.lang.reflect.Method.invoke(Method.java:585)
|       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
|       $Proxy1087.getClassificationSystems(Unknown Source)
|       com.sap.esi.uddi.sr.api.ws.ServicesRegistrySiImplBean.getClassificationSystems(ServicesRegistrySiImplBean.java:456)
|       sun.reflect.GeneratedMethodAccessor1324.invoke(Unknown Source)
|       sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
|       java.lang.reflect.Method.invoke(Method.java:585)
|       com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_WS.invoke(Interceptors_WS.java:31)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
|       com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
|       com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
|       com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod(DefaultImplementationContainer.java:203)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:512)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:486)
|       com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:256)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:176)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:112)
|       com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:70)
|       SoapServlet.doPost(SoapServlet.java:51)
|       javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
|       javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
|       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
|       com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
|       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
|       com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
|       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
|       com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
|       com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:245)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
|       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
|       com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
|       com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
|       com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
|       com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
|       com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
|       com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
|       com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
|       com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
|       com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
|

Hi,
Refer Error:Service Registyr Configuration PI 7.11
and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8071b1b8-3c5c-2e10-e7af-8cadbc49d711?QuickLink=index&overridelayout=true
Thanks,
Chandra

Custom error message in SAP application log

Is there a way to add a custom error message to the SAP application log without passing the message variables MSGV1, MSGV2, MSGV3, MSGV4 and the Message class and number.
We want to pass a custom message from the BAPIRET2-MESSAGE without giving it a Message class and number. The reason for this is that we are using class based exceptions instead of the traditional message class with errors. When we catch the class based exception, we take the error text of the exception and put in in the BAPIRET2-message and set the BAPIRET2-TYPE as 'E'. Now we want to add this to the SAP application log.
The call to 'BAL_LOG_MSG_ADD' takes a structure BAL_S_MSG which is just like BAPIRET2. However this function builds the entry to the application log use the message variables MSGV1, MSGV2, MSGV3, MSGV4. There is no provision to pass in the BAPIRET2 message.
Add message to application log
CALL FUNCTION 'BAL_LOG_MSG_ADD'
 EXPORTING
 i_log_handle = app_log_handle
 i_s_msg = log_message
Thanks,
Jay

Hi Jay,
Did you see BAL_LOG_EXCEPTION_ADD?
This FM is represented by the structure BAL_S_EXC. This can have various versions as described below:
Data of BAL_S_EXC Structure / Use
EXCEPTION / Exception class from which an exception text
 is added to the log. This field must be filled.
MSGTY / Message type (MSGTY) of a T100 message.
 This field must also be filled for exceptions.
PROBCLASS,
DETLEVEL,
ALSORT, TIME_STMP / Message or exception attributes, such as
 problem class (PROBCLASS, for
 example, "very important"), level of detail
 (DETLEVEL, from 1 to 9), sort criterion
 (ALSORT, unrestricted) and timestamp
 (TIME_STMP). These fields can be displayed
 in the log (except TIME_STMP).
MSG_COUNT / This attribute is not used for exceptions.
Follow the link below for more details:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/d6/5d7f38f52f923ae10000009b38f8cf/frameset.htm">SAP Help DOc</a>
Hope this helps.
Thanks
Sanjeev

ICI - How to display custom error messages in SAP CRM

Hello,
we are working on a custom Contact Center which interfaces with SAP CRM Version 7 with Enhancement Package over ICI.
The basic call functions like accepting, hanging up, holding and retrieving are fully implemented and are working already.
Our goal is to display error messages in the CRM so that clients know there is something wrong, for example why he can't be log in successfully (e.g. the telephony server isn't reachable).
We already found the ICI Documentation file which provides us the CRM SOAP error codes and tried to send SOAP Fault messages, but never got
them to screen.
Please find an attached example screenshot what we mean exactly, reproduced by trying to make a call with CRM user while BCM CDT isn't
running in the background.
Regarding to this topic we've the following questions:
- Is it possible to display custom error messages on the CRM or is this functionality limited to SAP?
- Could you provide us some further information on how to use this feature exactly (implementation details?) and how the SOAP XML should look like to get it work?
Thank you in advance!
Best regards
René Holy

NewUser7 wrote:
Please correct me if I am wrong
I need to create an entity adapter and attach an error handler with the adapter? or can i handle that in the event handler itself. I coulnt find any api for handling errorsYou can do it both ways but since we are talking about event handler now, then in 9.x you need to extend com.thortech.xl.client.events.tcBaseEvent class for creating a event handler. In tcBaseEvent class there are various flavors of handleError method. So use that as per my note earlier and you should be good.
HTH

Automatic Error Message in SAP PI 7.1

My scenario in SAP PI 7.1 is like this:
1. If an XML message fails in validation of structure, that is the structure is not as per the message schema or any field contains data that is incorrect as per the business requirement, then SAP PI should not further process the message (i.e. reject the message or mark it as invalid)
2. As soon as the message is marked invalid (as described in point 1), PI will have to automatically generate a error or a failure message containing reasons why the original message falied. The structure of automatic error message should be predefined in PI (e.g. a schema)
My question is, how to achieve the above two scenarios in SAP PI 7.1
Thanks a lot for your immediate reply
Edited by: Chitrabhanu Raychowdhury on Aug 16, 2010 12:45 PM

>
> 1. If an XML message fails in validation of structure, that is the structure is not as per the message schema or any field contains data that is incorrect as per the business requirement, then SAP PI should not further process the message (i.e. reject the message or mark it as invalid)
>
implement XML Validation concept,we do have a oppurtunity to validate XML document before picking up,it will check against correct structure.if any the data wrong you can show error at adapter engine level only,we can do this one IE level and AE level.
search in sdn ,there are many documents.
> 2. As soon as the message is marked invalid (as described in point 1), PI will have to automatically generate a error or a failure message containing reasons why the original message falied. The structure of automatic error message should be predefined in PI (e.g. a schema)
>
we can't mark the file invalid using PI i think
> My question is, how to achieve the above two scenarios in SAP PI 7.1
>

Error message in SAP Travel Management

Hi alll,
I am trying to change an address in PRMD tx code
Error message: Enter a house number
Also it is not possible to change existing addresses as the same error comes up.
I also tried in other company codes and there it seem to work fine so the issue might only be for company code 0376
Could you please let me know if there is any restrictions from the field u201Cstreet and house numberu201D so that it can be entered and changed as free form text?
Thanks for your help!
It is SAP 6.0

Are you sure you mean PRMD? This is the T-code to update HR master data and is not related to travel management!
Did you mean PRAA perhaps if you were trying to update master data from HR to vendor as there are some known issues around the structure of the PRAA report and house number and address (see the notes 570023 and 663350)
cheers
Sally

Error message "com.sap.aii.af.ra.ms.api.DeliveryException: "

Hi Team,
Created a simple file2file scenarion successfully. Unable to pick the file from Sender directory to Receiver Directory.
Checked from monitoring the Communication Channel.
Error message shown for sender communication channel as below:
Communication Channel Status   Short Log                                Control Data   Party Service           Adapter Type Direction
sen_cc                 Red ball Processing Errors In the Last 30 Seconds Manually             kanchuf2f_sen_bs   File         Sender
Line 1 / 1
By selecting the sender communication channel "sen_cc", below is the node details given.
Processing Details for Cluster Node Server 0 1_54295
Type
Time Stamp         Message ID                           Explanation
12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Retry interval started. Length: 60.0 seconds
12/3/08 8:20:01 AM 45f841be-a421-43bd-235a-c7ad19b0aec8 Error: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:
By clicking on the first Message ID, The message says successful upto some point and give error says JCO COMMUNICATION FAILURE and RFC issue.
Below is the information provided in detail.
Audit Log for Message: 45f841be-a421-43bd-235a-c7ad19b0aec8
Time Stamp          Status Description
03.12.2008 08:20:00 Success Channel sen_cc: Send binary file "f:\xi_file\sender\f2fmap.xml". Size 210 with QoS BE
03.12.2008 08:20:00 Success Application attempting to send an XI message synchronously using connection AFW.
03.12.2008 08:20:00 Success Trying to put the message into the call queue.
03.12.2008 08:20:00 Success Message successfully put into the queue.
03.12.2008 08:20:00 Success The message was successfully retrieved from the call queue.
03.12.2008 08:20:00 Success The message status set to DLNG.
03.12.2008 08:20:01 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
03.12.2008 08:20:01 Error Transmitting the message using connection http://sitaserv33:8001/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:.
03.12.2008 08:20:01 Error The message status set to FAIL.
03.12.2008 08:20:01 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:JCO_COMMUNICATION_FAILURE:
Page 1 / 2
I think this could be the problem with some basis related settings, I am not sure what exactly the issue with.
Any idea what exactly the error is talking about please do help me in finding the solution to thresolve this error message.
Regards,
Venkat Ramana K

Hi Carlos,
Thank you for the quick information.
Followed all the steps and also basis person from onsite restarted the XI server.
Now, I am able to log onto XI with the login Id but, when I give Tr Code: SXMB_IFR, unable to open the browser that shows Integration Builder.
Getting the error message.
*500   Internal Server Error*
                                                                                *SAP J2EE Engine/7.00*
**Exception**
*An internal error occurred. Contact you XI administrator*
*Unable to read configuration data (ExchangeProfile/aii.properties)*
Error Details, Error History, Build Info, Generic Application Info
Regards,
Venkat Ramana K

Error message com.sap.aii.af.ra.ms.api.DeliveryException: error while proce

hello experts
I am sending a message WS2RFC and recieve an error message that return from the RFC.
<?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="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: error while processing the request to rfc-client: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Date '03042008' has a wrong format at field DATUM: Unparseable date: "03042008"</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
any ideas what it is and how to solve it?

Hi,
Looks like you have passed data in wrong format to RFC input parameter.
Your format: DDMMYYYY (03042008)
Expected: YYYYMMDD
I would use a graphical mapping function "DataTrans" to convert date format from DDMMYYYY to YYYYMMDD.
Regards,
Jakub

Forwarding FAX error message from SAP Connect to user outlook e-mail ID

Hello,
We have a few POs sent by FAX to vendors using top call .Some times FAX does not transmit the PO to vendor . The status of the message is updated as error in SAP connect( t-code SOST) . The user who released the PO or recreated the message is getting the mail to his/her SAP inbox with PO number XXXXXX is not trasmitted due to ............. .
The programs SX_OBJECT_STATUS_RECEIVE , SO_STATUS_DOC_SEND are getting the update from SAP connect , compiling the update message and sending mail to SAP inbox .
We ahve a requirement that the user be notifed to the outlook that the PO has not been transmitted to Vendor so that hey can take alternate action .
Is any one using this functionality or suggest a way to send only the FAX error messages to buyer/releaser to his/her outlook .
Thanks
Venkateswara Rao Yeleswaram

Hi Thareq,
I am also having the similar problem.
When ever a notification is created, Champion is receiving the messages daily to his outlook though reminder functionality doesn't exist in the workflow.
"Your Workflow inbox in the SAP system MEP, client 100, contains the following work item:"
Can you please let me know how this has resolved in your case. Your reply would really help me out to solve my issue.
thanks.

Re:SAP easy-DMS request for recovery path-location

Dear All,
I have a requirement of a recovery for an origin path or a location in easy-DMS for the Document.
Fact is that Document was deleted by mistake, then the deletion flag was reseted, and finally path-hierarchy or location has been somehow deleted.
Is this possible.
Please advice how to get this done if possible.
Regards,
Vivek

Hi,
In Easy DMS if a document is marked for deletion, It cannot be recovered. Process is same as SAP DMS.
For future course, you can have some configuraiton done in Easy DMS like "Originals deleted from EasyDMS can be moved to recycle bin by customizing easyDMS"
Hope this helps.
Regards,
Deepak Kori

Retrieve error message of SAP provided web service in web service response

Hi All,
We have a SAP provided web service that sometimes fails to process data it is called with. This is not a problem as the data sometimes is just plain wrong (i.e. date field contains text). However, the error is only logged in SAP and can only be queried using SRT_UTIL.
The problem is that the error is not reported back via the response. How can we set up the web service so that the error could be displayed by the calling party without logging into SAP?
Thanks for the help in advance.
Best Regards,
Daniel

Hi Calvin,
The WS is indeed synchronous. The problem is not whether the error is captured or not. It is captured indeed but it is logged inside SAP only and not returned via the Web Service response mechanism. The error message says that error message can be retrieved using SRT_UTIL.
This is a major problem as the users of the outside system calling SAP have no right to use SRT_UTIL to track down the error. They need to contact SAP basis in order to get to the end of it.
What we need to achieve is to get back the same error message that can be seen with SRT_UTIL via the web service.
Thanks.

Disable or Deactivate Delete Button in SAP Easy DMS.

Dear All,
My client is using Easy DMS and is working fine. Now the issue is as soon as files become more in Private or Public folder he is Deleting Documents using DELETE Button which is available on the Tool Bar. Whereas if he uses Delete Document from Context Menu it shows Authorization is not given to delete the Document.
Is there any way to overcome this by Disabling or Deactivating Delete Button on the Toolbar.
rgds,
Dayanand

Dear Anubhav,
I have already tried this option. It shows this can not be implemented.
Please let me know any other option is there to overcome this issue.
rgds,

Error message in SAP Easy DMS

Similar Messages

Maybe you are looking for