VKMI Table - OSS Note 1042857
I'm looking to talk with someone who is currently using VKMI Table/ SD_VKMLOG_SHOW Report. This report logs entries that have updated S066(Open Orders) and S067(Open Deliveries) tables used in Credit Management. I am interested in system performance and also how the user parameter MCL was pushed out to the business users who could possible run transactions that would update this table?
Sheila,
I looked at the note, and I'm not sure that logging the S066 and 67 tables would be the best option. S066 is used by default for S&OP and should be updated for every order. So building another logging function for that table might add unnecessary overhead. S067, not entirely sure, but it MAY have to do with delivery due list indexing.
As for your needs about credit management updates, it might be better to try to find a way to use the change log on the orders. Even though the change history is a gigantic table, you might be able to index a few of the fields to get decent performance and then carefully build a query from that.
Either way, I'm not sure there is a really good answer. It really depends on what you are trying to do. And by the way, if you ever work with Jay Wolfarth (FI), tell him Bill says "hi."
Bill Wood
Similar Messages
-
Details of OSS Note in SAP tables
Hi Experts,
Do we have any standard report or a simple way by which I can get all the contents of a specific OSS note without going into SNOTE transaction. The reason why I am asking is for analysing a large volume of OSS notes. If I need to go through SNOTE and then find the objects it will be tedious. I know the table where in these details are there but I want to know if there is any report handy to use.
Kindly help
Regards,
Vijay VHello,
I'm afraid, but there is no such report in SAP using which you'll get the content os any SAP note.
Another option than SNOTE transaction is to use SAP marketpplace to findout the same.
Regards,
Nitin -
How to create a Attribute "Type standard table OF" to a OSS NOTE
Dear experts,
I need to add new attributes in a standard class as per one OSS note. I took access key to add new attributes. I have a question.
class name: CL_J_1BEFD
Attribute: MT_GROUP_C350
Level: Instance
Visibility: Private
Type STANDARD TABLE OF mty_result
How do i add the instance attribute because i do not want to give the typing and associated type, instead i have to declare data: MT_GROUP_C350 type standard table of mty_result in class builder private section code.
if you look at the pushbutton between Associated type and Description, for all instance attributes there's a green color lining below the arrow. I want my attribute also to be exactly same.
Though i have access key, in private section the display<->Change button is disabled.
Please suggest me how do i add code in private section of a standard class. i have required access key to change the class.
Thanks,
AlyssonHi Friend...
Thanks, but the question is...
When I went to transaction se24 or se80, I chose the class CL_J_1BEFD and second I swap to "CHANGE MODE".. after that the pushbutton is blocked... I can create the Attribute mt_group_c800 in the Class (using TYPE or LIKE option), but i can't change the code in the private session even using the assistant to modify it.
When I acess the Button "Detail View" the option "Direct Type Entry" is just unavaliable too, no matter what i do!
I coudn't find a way to create the Attibute like the note Describes (SAPNOTE NUMBER 1575772 - in the attachment of the note)
The changes are contained in the attachment
Follows the instructions retrieved from the file:
Add the following Attributes on the Class CL_J_1BEFD Private section
data:
mt_group_c800 TYPE STANDARD TABLE OF mty_result .
data:
mt_group_c850 TYPE STANDARD TABLE OF mty_result .
data:
mt_group_c860 TYPE STANDARD TABLE OF mty_result .
data:
mt_group_c890 TYPE STANDARD TABLE OF mty_result .
How can i make a way to creat this attributes using "TYPE STANDARD TABLE OF " Option? -
HI,
Can anyone plz tell me the table for OSS note where i get all implemented oss note with date . i want to filter that with date.
Regards
Anukool.Anukool,
go to snote transaction
click ctrl+f9(sap note browser)
execute
this will give you the data you are looking for.
K.Kiran. -
How to find out the list of implemented OSS Notes in a particular period.
Hi Friends,
Need help.
I need to find out the list of OSS Notes implemented in a period in a particular system.
Could you please suggest the table or program or any way to find out the OSS Notes Implemented date wise?
Thanks in Advance.
SreenivasHi Sreenivas.
How did you find the solution to this? Trying to do the same thing!
Cheers,
Tom -
SAP J2EE Engine JTA Transaction Xml for table TABLE could not be ana
I'm having a weird case. I created 3 entity bean. In my R/3 will call this JCO.Function to do the insert to database. But out of 3 entity bean, only 1 entity bean got error where it unable to insert to database and have this error in the log.
The case is quite weird where i created the same entity but only 1 entity is not working as expected. Wondering what cause this problem.
Thanks.
org.xml.sax.SAXException: Fatal Error: URI=:main: Line=1: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected: 0x20(:main:, row:1, col:218)#
at com.sap.dictionary.database.dbs.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)#
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)#
at com.sap.dictionary.database.dbs.XmlExtractor.map(XmlExtractor.java:130)#
at com.sap.dictionary.database.catalog.DbGeneralStructure.<init>(DbGeneralStructure.java:86)#
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:90)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)#
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)#
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)#
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)#
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)#
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)#
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)#
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)#
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)#
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)#
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)#
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)#
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)#
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)#
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)#
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)#
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)#
at java.lang.reflect.Method.invoke(Method.java:324)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)#
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)#
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
at java.security.AccessController.doPrivileged(Native Method)#
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
##0#0#Error##Java###{0}.commit(), Cannot commit due to unexpected exception in beforeCompletion():
[EXCEPTION]
{1}#2#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5 #001A6467CDF400590000004E000018D8000459BB785F496C#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Server#Java#ts_0004##Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).#1#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#
#1.5 #001A6467CDF400590000004F000018D8000459BB785F4BC5#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000050000018D8000459BB785F4E8F#1224561620123#com.sap.engine.services.ejb.entity.Container#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ejb.entity.Container#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###null
[EXCEPTION]
{0}#1#com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000051000018D8000459BB785F5FA9#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###RemoteException insertOk=false#
#1.5 #001A6467CDF4005900000052000018D8000459BB785F6094#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###Tue Oct 21 12:00:20 SGT 2008 java.rmi.RemoteException: com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
; nested exception is:
javax.transaction.RollbackException: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 moreHi Stefan and Everyone,
I have solved my problem. Just want to let everyone know if u have to install the SP's for WEB AS 6.30/6.40.
You start from the installation from CD 6.30/6.40. Everything will be working at this point. You can login to Visual Admin, Config tool and SDM.
Before you apply any SP's, do the following:
a) Create an emergency user with the Administrator rights: Ref OSS Note:669848
Try to follow this route for SP's:
From CD 6.30/6.40 -> SP04 -> SP07
Apply SP04 first before applying SP07 (Recommended Approach).
Refer the installation guide: SAP Web AS Support Package Guide 630SP2 to 640SP4.
Use JDK1.4.2_05 to install SP04. You must reference the following OSS Notes and apply to your system accordingly, this is the key to an error free installation:
a) OSS Note: 697535
b) OSS Note: 709140
c) OSS Note: 716604
d) OSS Note: 706378
You have to be really careful with SP04 installation, because it changes the version from 6.30 -> 6.40.
Once you are able to install SP04 without any problems, you can directly apply SP07 or the highest 6.40 SP.
Kind Regards,
Buddha. -
Remote Client copy: Table does not exist in Nametab
Hi!
We executed a client copy between 2 SAP EHP4 systems.
The both systems are SAP ERP EHP4 systems, but with different Support package.
After the client copy we get the following errors:
Table ADDRC_DELI_SERV does not exist in Nametab
Table ADDRC_DELI_SERVT does not exist in Nametab
Question
How can we solve these errors, maybe to transport the tables?
Thank you!Hi,
I would suggest to synchronize support pack levels between systems and copy it again. You could try to manually define those missing tables, but you need to create them under SAP namespace. later during upgrade you'll probably get some errors. Your issue is why it's not supported by SAP. Have a look at OSS note 70547 with detailed information about client transport.
Cheers -
ABAP dump in ECC 6.0 - Need OSS notes
ABAP dump is coming when retriving data between select-endselect.
Runtime Errors DBIF_RSQL_INVALID_CURSOR
Except. CX_SY_OPEN_SQL_DB
The problem cannot be resolved without correcting the application
program.
The statements MESSAGE, COMMIT WORK, ROLLBACK WORK, CALL SCREEN,
BREAK-POINT, WAIT, CALL FUNCTION ... DESTINATION, CALL FUNCTION ...
STARTING NEW TASK, RECEIVE RESULTS, CALL SELECTION-SCREEN, CALL
DIALOG, CALL TRANSACTION cannot be used within a database
loop.
You can collect the data needed for these statements together in an
internal table and process them
in a loop.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_INVALID_CURSOR" "CX_SY_OPEN_SQL_DB"
Can you please give the OSS notes no. if anything is available.Hi Sreedevi..
In the dump report, the piece of code where the dump occured will be shown
something with >>>>>> sign in the line...
Please copy and paste this peice of code..
Thanks and Best Regards,
Vikas Bittera.
**Reward if useful** -
OSS note 506603 What is it And where can I get it?
Hello,
I am trying to create my form with a SAP Table wizard connection, when I try to use the Table wizard I got the error: "No such interface supported". I can see in a lot of comments the solution is on OSS note 506603. I was trying to find this patch in the sdn site but I could not find it. I am not sure if it is a document, an exe file, a dll,,, and when I see the same question asking where to get the OSS note 506603 there is no answer, could somebody help me telling me what is this and where can I get the patch? I would really appreciate it.
Many thanks.Hi Eden,
How are you doing ?
OSS note is the older nomenclature for what is now SAP Notes.
They are available at :
http://service.sap.com/notes
you will need a service marketplace user id to log on.
alternatively, if you do not have access to service.marketplace.
send me an email [view my business card], i will reply with the patch. it is a few hundred kb.
with respect,
amit
the note number 506603 :-
Summary
Symptom
Additional information for SAP.Net Connector that was not included in the guide.
Other terms
SAP .NET Connector, Proxy Wizard
Solution
SAP.NET Connector Version 1.0 has been available since Nov 21, 2002. You can download the software from http://service.sap.com/connectors.
Version 2.0 is also available. Use only the new version for new developments.
Report any problems with the SAP.NET Connector under the components:
BC-MID-CON-DNW for problems with the .NET Proxy Wizard for Visual Studio.NET.
BC-MID-CON-DNC for problems with Communication Runtime.
Known problems
1. The Proxy Wizard terminates with the error message "Exception caught in method createFunction for DD_GET_UCLEN Reason: null".
This is caused by a missing function module, which can be installed as described in Note 580834.
2. Corrections for SAP.NET Connector 1.0
The updated version corrects various problems that have been noted during the interim period. You can download it from http://service.sap.com/connectors. To install this version, see the "Release Notes" file. For SAP.NET Connect 1.x, the newest patch-version is called "1.0.3".
3. Corrections for SAP.NET Connector 2.0
For Visual Studio Integration (Design Time) following problems have occurred:
For proxies with several functions, the following runtime error can occur under certain circumstances: "Method xyz can not be reflected." The cause is a combination of an error in the .NET framework and the way in which the proxy generator uses XML-attributes.
The SAP wizard table does not work. Existing tables are not recognized.
Both problems are solved by the patch attached to this note. Stop all instances of Visual Studio and unpack the ZIP file into the "%Program Files%\Microsoft Visual Studio .NET 2003/Common7/IDE" directory, whereby the "SAP.Connector.Design.DLL" file is replaced.
Header Data
Release Status: Released for Customer
Released on: 10.12.2004 16:40:26
Priority: Recommendations/additional info
Category: Installation information
Primary Component: BC-OP-NET-NCO SAP .Net Connector
Secondary Components: BC-OP-NET-VS Visual Studio .Net Connector Wizard
Message was edited by:
amit chawathe -
OSS Note for MIGO "Update terminate (SAPSQL_ARRAY_INSERT_DUPREC)"
Dear all
I am facing problem during MIGO GR reference Others, MVT 561.
Upon clicing Button: Save, I face 2 types of errors intermittently
1. Material document is saved and generated but when comes to displayed, it will say "Document 4900496xxx does not exist in calendar year 2009" And I check in Table: MKPF and it does not exist at all
2. I am not able to save it and face this termination error:
The ABAP/4 Open SQL array insert results in duplicate database record
What happened?
Error in ABAP application program.
The current ABAP program "SAPLGLIU" had to be terminated because one
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and adminis
termination messages, especially those beyond their normal deletion"
I have done my investigation and the number range uder FBN1 for this MVT 561 under this Company Code and Year has been maintained.
Can anyone advise me the OSS note to solve it? I cannot find a direct OSS note on it to solve this.
Thanks.
Edited by: Daimos on Oct 26, 2009 7:58 AMSorry Jurgen
I have posted so many material documents using MIGO to test it out and try to update my OMBT there so many times until I lost track what is the current number range when I wrote my question here.
I have read that thread you posted regarding the ST22 analysis [Solution from Jurgen|Document does not exist after creation of PO; . I exported them to HTML and did a detail checking, and I find out it is FI GL there did not update the number range properly which in turns cause my GR to have problems.
Below is my analysis and learning to share with others:
1. Ask the ABAPER to find out which record value the system trying to insert. Copy down this number.
2. Check the OMBT value of Current Number.
3. Then use the MFPK Table to search the latest Number Range.
4. Try to check if the record value trying to insert already exists in Current Number. Normally, it will exist and that is why
system prompt "insert duplication".
5. Then check if the record value trying to insert already exists in MFPK Number. Normally, it will exists it will exist and that is
why system prompt "insert duplication". (There can be situation that the Current Number is lower than the MFPK Number,
but it rarely happen).
6. Replace the Current Number to be the Next Number of MKPF largest Number. Save and it should work.
7. If it is not work, please create a material which is non valuated and perform GR, if GR can be done and we can display
material doc, it means the error is caused by the FI GL number range error.
8. There can be other issues such as activation of user exits and other.
Jurgen, I got one more question to ask you. I have tried to replace the current number with the largest number of MKPF without + 1. It can solve my problem.
But I wonder why SAP Notes and you suggest us to replace Current Number with largest MKPF value PLUS 1?
Please advise.
Thanks.
Edited by: Daimos on Nov 2, 2009 8:41 AM -
Problem while implementing OSS note 1077403
Hi,
I am trying to implement a OSS note ( 1077403) using SNOTE transaction. When I download the note, the status of this note is u201CCan be implementedu201D. It creates few standard programs which are utility programs related to Unicode conversion. While implementing this note, I am facing the issue "Objects can only be created in SAP package" and some of the objects in the note are not created. The note status becomes u2018Incompletely Implementedu2019.
Can you please suggest what could be the issue?HI,
For more efficence direct link to note Note 1077403 - Cluster table check using SDBI_CLUSTER_CHECK
Have you a basis release version >= 6.20 ?
you can use transaction SNOTE to implement the version for Basis Release 6.20 and higher.
Rgds
Edited by: stéphane mouraux on Mar 1, 2010 6:31 PM -
CDHDR and CDPOS tables are not updated
Hi,
When I am trying to change (or delete) Project definitions or WBS elements (changed all its related data which have change document ticked in its data element) those changes are not captured in CDHDR and CDPOS tables.
Here in our system PROJ object class exists in SCDO t-code and has all its generated programs, but still not able to find changes in CDHDR and CDPOS tables.
Can anybody plz let me know if I am missing anything or PROJ is not the appropriate object class or does BASIS team need to do any configuration to capture change documents in CDHDR or CDPOS tables because I do not see not even one record with PROJ object class in those tables.
Appriciated for quick response.
Regards,
M, ManoharHi Manohar,
Even we have project system in my project.We are able to see the changes and we did not done any settings for that.Just check with your basis people else raise an oss note.I did not see any sap notes also related to that.
Regards,
Madhu. -
Hi, I'm trying to review OSS Notes and I find a lot of notes that I feel don't have enough context to basically understand what the note is about. Basically I feel the Note Quality is poor. I found this one just today. Could someone look at it and let me know if they feel they understand this note or is it just me? Thanks!
[Note 1346134 - 0TCT_DS01 Deletion of statistical data|http://i34.tinypic.com/r0wa4h.png|Note 1346134 - 0TCT_DS01 Deletion of statistical data]Hi Kenneth,
I'm also there with you. This is something needs to be reported to SAP and they have review this OSS note as the description that they have given is not proper.
There is some more information is missing. They are talking about the deletion of Statistical data from the table: RSDDSTAT_OLAP .... but they did not mentioned about the actual issue for which the correction has been applied..
Onlyway to understand is that correction code that they have which will give some idea but this note needs more information to assist all users......
Me I used to work on serveral notes but I did not come across this kind of note..
Anyway have a nice day... -
TUB 166 and OSS Note 1422655 -- Michigan FUTA
We have applied TUB 166 and would like to get the Michigan taxes straightened out since the changes are retroactive to 1/1/2009. I found OSS note 1422655 and it says 'Before apply the instructions of this note, it is necessary to configure unemploymnet tax type 11 for Michigan state in your tax model'. Does that mean that I need to add a record to table V_T5UTD (Config step 'Maintain Tax Types per Tax Authority') and that is the only thing I need to do? Thanks.
Hi ,
You have to mantain the following config. :
1) Tax Model Tables T5UTE, T5UTM and T5UTY.
2) Also mandatory to maintain V_T5UTD (Maintain Tax Type 11 per Tax Auth - - Michigan in this case) and V_T5UTI (Mantain Tax Type per Tax Company Code per Tax Auth ).
3) Also ensure that tax type 11 is maintained at BSI Tax Factory's end for Michigan
FYI: Tax Type 11 is Employer Debt Repayment Tax
Thanks And Regards,
Somdeb.
Edited by: Sombed on Jan 27, 2010 4:08 PM -
SKB1 table is not populated - Bulgaria country version
Hi,
Our team is working on installation country version for Bulgaria.
We have ECC 6.0 and SAPK-11023INCCEE ECC Core Country versions for EEM Country (Romania country localization).
We followed the instructions of SAP note 856949 "Enhancements for mySAP R/3 46C and
higher for Bulgaria" and we face the following problem:
Table SKB1 for BG01 company code is not populated, but we have data in SKA1, SKAT tables (charts of accounts CABG).
Although we imported CT_BG_160108.zip , CT_SKB1_table_content.zip , still SKB1 table does not contain data for BG01 - company code.
Please help us to solve this problem.
Moderator: I'd suggest to open OSS message on this problem, if you are sure that you maintain the data for company codeHello,
Here are a few hints:
- In the operator, check the steps of your interface. Are rows inserted in I$ tables ?
- If you use Flow Control, does your E$ tables contains something ?
- Check the SQL code generated in the integration step, extract the Select from it and execute it using sqlplus, SQLDeveloper or whatever you want. Does it return something ? Maybe there is a wrong filter...
If you don't find the error, tell us which IKM you use and give us the generated code of the step which returns no data.
Hope it helps
Maybe you are looking for
-
Dear all, Here are the details: Operating system: Microsoft Windows XP Build 2600 Service Pack 2 Language: English Language for non-Unicode programs: English Locale: English Input language: English Nokia PC Suite: Version 6.83.14.1 Language: English
-
M500 120 GB mSATA hanging/crashing Windows 8.1 Ent after 1 year of use
Hi, I purchased a M500 120GB mSATA disk June '14 from Amazon, and installed it in my Sony Vaio T-Series laptop. I have been using it ever since and it has been fine and speedy. Since last week, I noticed my laptop started hanging applications and the
-
External Toshiba drive won't work on Mac after using on PC
My Toshiba External USB drive stopped working on my Mac air after I downloaded some files on a PC. It worked numerous times on the PC and then I brought it back home to use on Mac. Now, it won't show up on finder but can be found on Disk utility. I c
-
How to ignore 1st row form the file(csv) sender CC
Hi, I have a CSV File (File sender) that I need to load with PI.I want to Ignore 1st row from the file. For example the File contains 10 rows but PI need to read the data from 2nd row. because in the 1st row contains header data like name, number,
-
How do I add a grass texture to a selection in a photograph?
Usung Photoshop CS5 Extended in Windows 7 on a PC, I would like to make a selection and add a grass texture to a field I have painted. I went to Filter-TEXTURE-Texturizer-but do not see a grass texture I can add to the selction like I can Canvas etc.