Outbound Q error ( conditions )

Hello Experts
Outbound Q which carries listings ( conditions ) from CRM -> R/3 was in failed with error " Processing terminated due to a fatal error " I tried to active the Q but no luck .
Please advise !!
Thanks
Pooja

Hi Pooja,
It is most likely that the BAPI function module dumped in R/3. Check ST22 in R/3 and find the real cause of the dump.

Similar Messages

The parsing engine has encountered a fatal error condition......

I am creating a new Entitilement Segment. When I sync, I get a parsing
exception. The error stack is described below. The same error message
is displayed while starting the server.
Any help is appreciated.
Kumar
URI : /contentselectors/GlobalContentSelectors.rls
Cause : Exception raised when executing create, please see the embedded
exception.
StackTrace :
Exception[com.bea.p13n.expression.internal.parser.ParseException: The
parsing engine has encountered a fatal error condition; see embedded
exception for details.]
at
com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
Caused by: org.xml.sax.SAXParseException: Valid documents must have a
<!DOCTYPE declaration.
at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at
com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
Resource key "Corrective Action" not found for class
com.bea.commerce.tools.server.SynchronizationProgress. null
==================================================================
URI : /entitlements/GlobalEntitlements.rls
Cause : Exception raised when executing create, please see the embedded
exception.
StackTrace :
Exception[com.bea.p13n.expression.internal.parser.ParseException: The
parsing engine has encountered a fatal error condition; see embedded
exception for details.]
at
com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
Caused by: org.xml.sax.SAXParseException: Valid documents must have a
<!DOCTYPE declaration.
at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at
com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
Resource key "Corrective Action" not found for class
com.bea.commerce.tools.server.SynchronizationProgress. null
==================================================================
URI : /segments/GlobalClassifications.rls
Cause : Exception raised when executing create, please see the embedded
exception.
StackTrace :
Exception[com.bea.p13n.expression.internal.parser.ParseException: The
parsing engine has encountered a fatal error condition; see embedded
exception for details.]
at
com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:175)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:257)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepository(AbstractDataRepository.java:706)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:658)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.notifyDataRepositories(AbstractDataRepository.java:606)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:994)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.dispatchMessage(DataSyncServlet.java:351)
at
com.bea.p13n.management.data.transport.servlets.DataSyncServlet.doPost(DataSyncServlet.java:276)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5412)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:744)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3086)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2544)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
Caused by: org.xml.sax.SAXParseException: Valid documents must have a
<!DOCTYPE declaration.
at org.apache.crimson.parser.Parser2.warning(Parser2.java:3074)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:491)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371)
at
com.bea.p13n.expression.internal.parser.ExpressionParserImpl.parse(ExpressionParserImpl.java:161)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createRuleSet(RuleSetPersistenceManager.java:489)
at
com.bea.p13n.rules.manager.internal.RuleSetPersistenceManager.createDataItem(RuleSetPersistenceManager.java:168)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.handleDataItemMessage(AbstractDataRepository.java:814)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onDataSyncMessage(AbstractDataRepository.java:990)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:252)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestResultMessage(AbstractDataRepository.java:1185)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.executeMessage(AbstractDataRepository.java:261)
at
com.bea.p13n.management.data.message.internal.JvmCommunicationPipe.sendMessage(JvmCommunicationPipe.java:116)
at
com.bea.p13n.management.data.repository.internal.AbstractDataRepository.onSyncRequestMessage(AbstractDataRepository.java:1086)
at
com.bea.p13n.management.data.reposit

Hi kumar,
did you find what was the resolution for this.
thanks

Outbound Idoc error handling through workflow

Hi,
I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
How this task can be triggered when outbound idoc error occurs in the system?
Kr,
Vithalprasad
Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

Hi,
Have a look
Outbound IDoc Error Handling via Workflow
Outbound idoc error handling through workflow

IDoc error - Condition type & tax code & does not exist

Hi,
I have the problem with CANADA tax codes. I have a few documents sent from external SAP to different SAP. In the source system documents were posted. In the target system i have error "Condition type & tax code & does not exist". I have compared the tables A003 and A053 in both systems and the settings are the same for specific Condition type and tax code... So where to find the reason Idocs are in error ? The only thing which is different is validity from (in the source system is earlier than in the target but the docs are created after both validation start)...
I would appreciate advice.
Tomek

Hi Tomasz,
Please go to T.code WE02 and check the reason for the error.
The failed IDocs will be in status "51" and will also give you the reason for errors.
Regards,
Shiv

Handling outbound IDOC errors through workflow TS00007989

Hi,
I want to sent an notification e-mail to external mail box when an outbound idoc has an error status. This needs to be achieved through a workflow template.
I noted that there is a standard task TS00007989 in WE40 which is used for handling outbound idoc errors.
Moreover i couldnt find any trigerring events for the above task.
Can any one help me with a step by step guide for achieving this.
Regards,
Krishnakumar

Hi,
the single step task TS00007989 that you see is NOT TRIGGERED thru' any BO's event. It is created by the std. pgm RSEWFERR. If you go to the wflow log of the witem generated by it, you will see the Creator.
And you can control the activation / deactivation of these single step tasks for various inbound and outbound Error IDOC's thru' Transaction WE46.
If you want, create a single step task of your own and maintain that task here. But, you will ahve to know the exact BO like IDOCORDERS or IDOCEMBMAS etc. or look for events triggered by General IDOC objects like IDOCAPPL.
Hope this helps.
venu

Cannot create error condition

Hello I am using IBM MQseries and jms to connect to the queues. Now what Im trying to do is catch linked exceptions on the read of a queue. I would start draining messages off a specific queue then in the middle close the channel, but it does not throw any exception it just halts. I am not sure if this is an error condition that is handled but i believe it should be. My class implements MessageListener
here is the bit of code that I want to handle this even
//more code
//more code
try{ //
System.out.println("Creating and starting a Connection");
connection = factory.createQueueConnection();
connection.start();
boolean transacted = false;
session = connection.createQueueSession( transacted,
Session.AUTO_ACKNOWLEDGE);
// Create a QueueReceiver and assign mesage listener
queueReceiver = session.createReceiver(queue);
queueReceiver.setMessageListener(this);
catch(JMSException e1)
if (e1.getLinkedException() == null)
e1.printStackTrace();
else
e1.printStackTrace();
System.out.println(e1.getLinkedException().getMessage());
catch(Exception ex) { ex.printStackTrace(); }
} // end of method
public void onMessage(Message msg)
String msgText = null;
counter++;
System.out.println("In onMessage fn ...");
try {
if (msg instanceof TextMessage) {
msgText = ((TextMessage)msg).getText();
System.out.println("Got TextMessage " + counter);
else if (msg instanceof ObjectMessage) {
ObjectMessage receivedMessage = (ObjectMessage) msg;
Object mess = receivedMessage.getObject();
System.out.println("Got ObjectMessage " + counter);
else { // If it is not a TextMessage...
System.out.println("Got Non-TextMessage and Non-ObjectMessage");
msgText = msg.toString();
if (msgText != null && msgText.equalsIgnoreCase("quit")) {
synchronized(this) {
quit = true;
this.notifyAll(); // Notify main thread to quit
} catch (JMSException jmse) {
if (jmse.getLinkedException() == null)
jmse.printStackTrace();
else
jmse.printStackTrace();
System.out.println(jmse.getLinkedException().getMessage());
} // end of class
Now if the channel was closed before i construct the class I would get the jms exception and the linked exception but not after. And if i open the channel up after I sptopped it nothing happens which tells me the listener is not listening
Any suggestions.
Thanks

but you start the connection before you associate the receiver and session to it.
if that doesn't work, maybe reboot the box. you might be running out of java virtual memory on the box. I had the same problem. It ended up being that.

QRFC Outbound queue errors

Hi All,
I have some "qRFC Outbound queue errors" in the production system of R/3 and the target system is CRM.
The status is "SYSFAIL " .
Can anybody tell me how to solve them.
Regards,
Anindya

HI Anindya,
It's a very simple error. You have to check with your Security System Administrator if the user has included in your profile the authorization object S_RFCACL. Before this you have to define RFC Trusted / Trusting Systems in your Landscape.
Reward Points if helpful
Cheers
Manohar

EDI Error : Condition EDI1 is not allowed as item condition

Hi EDI Gurus,
Right now I am getting the error while creating a Sales order through IDoc.
"Condition EDI1 is not allowed as item condition"
Clarify a few things to me:
1. Where to pass the Customer Expected Price on the IDoc.
2. How to maintain pricing Condition EDI1. (If it is necessary for processing of sales order)
Please clarify these two things.
Thanks,
Matt

I ran V/O8 transaction. There were a bunch of procedures listed in it.
I was not sure which procedure I should look for EDI1 pricing condition.
I checked RVAA01 (Standard) - there are two conditions EDI1 and EDI2.
I am not sure what I should do. Whether they are already configured or not I am not sure.
If they are already configured, why is it giving error in EDI process.
MxG,
Please enlighten me.
Thanks,
Matt

PO outbound message control - Condition record / PO IDOC outbound user exit

Guys,
I have a system with PO outbound message control sending PO idocs to a unique plant that is set up as a customer in the partner profile. I am using a custom message type and RSEOUT00 to send my idocs with custom message type to this plant. This interface works fine. Now my requirement has changed. I need to send PO's to varying plants (depending on the plant in PO item- all items on my POs belong to same plant).
I noticed that i cannot create condition tables with PO type and Plant combination. (SAP Note 457497 .Q-34).
So I have decided to populate all my PO idocs with a generic receiving partner number '9999' and planning to change this somewhere in a user exit. I found an user exit which looks helpful.
EXIT_SAPLEINM_001 . FM
MM06E001 - Enhancement.
But somehow this exit is not triggered in during PO creation ME21N or change Me22N/Me22.
Is this because I am using a custom message type instead of standard message type ? (I still use the process codes Me10/Me11). Would this matter ? When should this user exit trigger (during creation of idocs in status 30 or when i run RSEOUT00 to sweep these idocs in status 30 to status 03) ? Any tips will be useful.
THanks.
Edited by: Shareen Hegde on Jul 21, 2008 10:13 PM

I found a OSS note -Note 457497 (Q&A # 34), which talks about the same . This was my assumption too. I was just confused because I saw plant(WERKS) in the field catalag of the access sequence.
I don't know what header field I can use to map the plant (I agree its a good idea to do this). But I have decided to do it another way. I will change the receiving partner on the control record depending on the plant in an user exit
- EXIT_SAPLEINM_001.
Thanks for your answer , Mahesh.

Outbound delivery error.

Hi,
I have an outbound delivery and this delivery is processed from the EWM point.
From SCWM/PRDO I can see the status of Goods Issue everything is completed.
Now this delivery is not getting updated in ECC system, these deliveries are lying in SMQ2 queue with the error message saying.
Connection closed (No da ta)
Can anyone help on this
I ahave around 15 deliveries lying wit this error.

Hello,
This [SAP note|https://websmp230.sap-ag.de/sap(bD1ubCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=335162] describes your issue, but it doesn't really provide an answer because the error can have several different causes.
Did you check SLG1 for errors?
Regards,
Oliver

Outbound Proxy error when triggering from SPROXY

Hi Everyone,
I was working on outbound proxy from ECC to PI. I have generated the proxy and activated. When I am trying to test the proxy manually from SPROXY the message is not getting triggered to SXMB_MONI in ECC itself. But I didn't get any error message as well. When I am executing the proxy from SPROXY I was getting below message in the status bar. So can anyone help me with the possible solution why the message is not getting triggered.
Below is the options I have selected while executing the proxy.
This was the status message which was giving after execution of proxy from SPROXY. The same status was giving for all the Proxy interface which ever is executing from SPROXY.
Regards,
Kankipati.

Hi Kankipati
can you please try Commit work by navigating on test proxy screen .
Extra- Trigger Commit work .
Follow the below link .
SAP PI Reference: SAP PI ABAP Proxy Outbound settings, Triggering message to SAP PI(When many sap pi systems)
Best Regards
Srinivas

Outbound IDoc Error: Status Code 37 'Sender Port' is invalid

Hi
I have an Error when the Outbound IDoc is triggered.
It shows that 'Sender Port in Control Record is invalid'.
Status Code: 37.
I know that there are some issues with the Sender Port Definition.
Please help me out to solve this problem using some checkpoints at each and every step.
Reward Points Assured.
Regards,
Baburaj

Hi Baburaj Manickam
Good
Follow this simple procedure
1) Send an outbound IDOC data(MATMAS) to a flat file on client1(SENDER).
- Create File Port (WE21) for outbound file.
- Maintain Distribution Model (BD64) for sender ->receiver system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RBDSEMAT (t/code BD10) to generate IDoc MATMAS file(s).
_ Then you can FTP the file(s) to receiver system.
2) Upload the flat file as an IDOC on the inbound sytem
which is Client2(RECIEVER).
- Create File Port (WE21) for inbound file.
- Maintain Distribution Model (BD64) for receiver -> sender system.
- Create Partner Profile (WE20) for logical system.
- You can use this program RSEINB00 to upload IDoc MATMAS file(s).
INBOUND IDOC PROCESSING:
Firstly attach your idoc to a process code.
In the process cod you can tell the system that the specified program should be triggered whenever an idoc of that type comes to the system.
Then you want to have a Z-function module for your idoc processing, if I understand correctly.The steps should be:
1. Create a z function module for idoc inbound posting (copy from a function module idoc_input_*).
2. Set Function Modules as Inbound: - Transaction BD51
3. Assign Function Modules to Logical Messages and Idoc types:- Transaction WE57
4. Create process codes : Transaction WE42, and link the z-function module.
5. Create partner profile: transaction WE20 and attach the message type and process code.
6. In the Z- function module, extract data from the idoc segments, do whatever processing you want to do, and then call BAPI_CREATE_SALES_ORDER_FROMDAT2.
Try the Trasaction WE19 for testing your inbound and outbound IDOCs
Good Luck and Reward me for the same
Thanks
Ashok.N

EDI Outbound 855 Error Code:AIP-51505 Unable to create outbound file

Hi,
I am facing some issues while processing EDI Outbound 855.
I am getting error in B2B . I have checked ECS and XSD. There is no mismatch
Error description: Extra elements were found in the data file as part of Segment PO1 at guideline position 010.{br}{br}This error was detected at:{br}{tab}Segment Count: 3{br}{tab}Element Position: 5{br}{tab}Characters: 1388 through 1390
Can any one give me some resolution for this one.
Regards,
Rao

Hello Rao,
It appears from your previous post,
1. This issue is there only for one Trading Partner.
2. You have already validated document against XSD and also XSD is generated from the ecs which is getting used, transaction set ecs does not contain envelop details.
Please do the following.
1. Please make sure you have not overridden transaction set ecs as part of operational Capability.
2. Please send us the b2b.log in DEBUG mode along with ecs and payload(XML) which will help us to identify which segment is extra in it.
Rgds, Ramesh

XML Gateway Outbound transaction error

Hi,
We are trying to send a XML file to an outside vendor using XML gateway but facing issue in doing the HTTP post.
As per the XML Gateway user guide I have setup the Hub definition with protocol type as being HTTP. protocol address as the one provided by the vendor and created a hub user.
I have also setup a 'custom' outbound transaction type.
And then setup a 'Trading Partner' linked it to the transaction type and the hub. and loaded the DTD and Map file.
I am able to generate the XML file successfully but it does not get delivered or is being rejected by the vendor.
I am trying to narrow down to if the issue exists on our end and the file is not being sent correctly or it is being rejected once it reaches the http site.
I get the following error message on looking at the underlying log table:
Response: HTTP/1.1 500 Internal Server Error
Connection: close
Date: Tue, 26 Oct 2010 19:22:10 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Cache-Control: private
Content-Type: application/soap+xml; charset=utf-8
Content-Length: 1805
<?xml version="1.0" encoding="utf-8"?><soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><soap:Code><soap:Value>soap:Receiver</soap:Value></soap:Code><soap:Reason><soap:Text
xml:lang="en">System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.
any help will be much much appreciated.
Thanks
Amit

Yes i was able to go to the URL using my machine browser. Since Oracle is installed on a linux machine i do not think I will be able to install a browser and go to the site from the oracle machine. I also tried pinging www.google.com and that seemed to work so i am sure the server is able to connect properly.
Can you suggest any other way to verify that the file is being sent out and the issue is on the other end? I was hoping if i could send the file to any other outside link that will be a good enough test of file going out of the network.

Pricing error : condition k005 not allowed ...

hello
i had encountered an error while doing pricing. the details are as follows:
after completing entire process of pricing procedure step by step, when i had attempted to create a sales order based on the condition given, i got the exact results for PR00 and K004 condition types but calculations for k005 customer material discount did not appeared and after attempting to give a conditions in the conditions section of va01 ,
i had encountered an error saying :
" condition k005 is not allowed as a header condition"
please send adequate replies..
amar

You are trying to enter the condition type manually at the header level I believe. Thats the reason why the system is giving you that error.
Go to the item level meaning double click on any material that you entered in the sales order and go to the "conditions" tab and enter K005, the system will take it.
OR
Go to your pricing Procedure in T.Code:V/08 and to the condition type K005 and uncheck "Manual", it is manual entry there, that why it is not appearing like K004 and PR00.
Regards
AK
Reward points if helpful

Outbound Q error ( conditions )

Similar Messages

Maybe you are looking for