Next Number Maintenance - Database inconsistency

Hi ,
I did basic configurations in SAP ME. I also did Next number maintenance as a part of configuration. I have created few shop orders and completed successfully with NC .
Recently we have upgraded to SAP ME 5.2.4.3 from 5.2.4.1
Now I have added some more materials to the same plant and trying to create inventory for those materials in Inventory Receipt.
I am getting the following message.
Database inconsistency: "Invalid Next Number return" (Message 1006)
I am able to create inventory for the old materials even now.But not for the newly added materials.
Did I miss something after patch upgrade? or is it configuration problem?
Regards,
Guru.

Hi,
it looks weird. Could you look at the default trace? What is the stack trace behind the exception you get?
What if you try just to copy old material under a new name? Does it work?
Regards,
Anton

Similar Messages

Next Number Maintenance - IncrementBy is used for what?

Hello everybody,
as I'm developing a webservice I've used the "IncrementBy" of my next number template as the value which is added to the current sequence of the number.
Let me provide an example:
The current sequence is 1
The IncrementBy value is 6
I order a new number and get 7 (current sequence + IncrementBy value)
My problem is now that the documentation states, that the "IncrementBy" value is used to "(...) increment the minimum and maximum sequence numbers."
Next Number Maintenance - SAP Manufacturing Execution (SAP ME) - SAP Library
This would differ from my current usage. However, I can't see any sense in providing a "incrementby" value to manipulate static data in a table. Furthermore the name of the column would be a fail, too. May there just be a mistake in the documentation?
If not, what's the sense behind the incrementby value then?
Thanks and regards,
Kai

Kai
The help is wrong. When you request a number from Next number, it returns the Current Sequence. It then adds the value of the Increment By to that number and stores it back to the Current Sequence, ready for the next request.
Stuart

Check next number (activity code)

Good day experts.
This is the issue we are currently importing a SFC into the system or using the supplier barcode for the SFC inside visprise. We unfortnately use two diferent product types from the same supplier where the two don't really have any differeneces. The products are hard drives one is 40 gig and the other is a 80 gig, but inside visprise we are having troubles keeping the product seperated.
We are wanting a way to check the barcode, because the part number is inside this barcode from the supplier to seperate the two inside visprise.
I thought about using check next number activity code, but unfortnately this isn't getting the job done. I was wondering if I was doing something wrong. As of right now I have the acitivity codes create SFC as Pre-start and check next number as a pre-validate start. I have tried changing the hook point, but nothing seems to work. I can force it to not work at all or work for everything.
I have a setup the next number maintenance and I can print out the correct barcode for this material, but I can't prevent us importing a incorrect barcode.

Basically this is what is happening. We are 'importing' Barcodes into the data base. Problem lies we have two materials that are very close to each other (both hard drives) they are getting mixed inside the test equipment causing us to much down time. I was reading up on the activity codes and was wondering how next number maintenance or mask valiation was working inside SAP ME. To try and prevent the confusion.
The biggest differences between the materials, that concerns SAP ME, is the barcode format. The two different part numbers are inside the the supplier barcode that is given to us, which we are currently using for our SFC in SAP ME.
It isn't a requirement for me to use SAP ME, but I was exploring every avenue. If it is true that these only work at the specific points that the help site is suggesting i will try a different avenue, this is looking very possible right now. I have tried using the activity codes with no luck in succeeding in the goal.

Next Number Activity Hook - Error on save

Hello all,
Running into a problem trying to create an Activity Hook for the Next Number Maintenance within NWDS.
I create the java class and deploy it to SAP ME 6.1 and create the activity in Activity Maintenance. When I add the Activity Hook to the Next Number Maintenance and try to save it generates the following error message:
Activity "MAT_NEXT_NUMBER" specifies a Java Class ("com.<vendorID>.nextnumber$MaterialNextNumber") that could not be found in the class path ("C:\usr\sap\ME0\J00\exe\jstart71.jar;C:\usr\sap\ME0\J00\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\ME0\J00\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\ME0\J00\exe\jre\lib\iqlib.jar;C:\usr\sap\ME0\J00\exe\sapjvm_6\lib\tools.jar;C:\usr\sap\ME0\J00\j2ee\cluster\bin\boot\sap.com~tc~bl~jkernel_boot~impl.jar;C:\usr\sap\ME0\J00\j2ee\cluster\bin\boot\jaas.jar;C:\usr\sap\ME0\J00\j2ee\cluster\bin\system\sap.com~tc~bl~bytecode~library.jar;C:\usr\sap\ME0\J00\j2ee\cluster\bin\boot\memoryanalyzer.jar") (Message 16018)
Was wondering what this means?
Did I forget to do something during the process? If so, what do I need to do?
Any help would be appreciated,
Mike Jewson

Hello,
I did set this up as any normal Activity Hook, so it is set as a Type: Service.
Here is the trace information after it is run:
#2.0 #2014 03 19 15:00:35:759#0-400#Error#com.sap.me.trace#
##sap.com/me~ear#C000C0A8CA89007B0000000100000EC4#4997050000000004#sap.com/me~ear#com.sap.me.trace.VM#SITE_ADMIN#34#JTA Transaction : 12004#8F1E85FCAF9811E3865E0000004C3FBA#bb314cc4af9811e3c16d0000004c3fba#bb314cc4af9811e3c16d0000004c3fba#0#Thread[HTTP Worker [@558364746],5,Dedicated_Application_Thread]#Plain##
Activity "MAT_NEXT_NUMBER" specifies a Java Class ("com.<vendorID>.nextnumber$MaterialNextNumber") that could not be found in the class path ("C:\\usr\\sap\\ME0\\J00\\exe\\jstart71.jar;C:\\usr\\sap\\ME0\\J00\\exe\\sapjvm_6\\lib\\jvmx.jar;C:\\usr\\sap\\ME0\\J00\\exe\\sapjvm_6\\lib\\jvmx_tools.jar;C:\\usr\\sap\\ME0\\J00\\exe\\jre\\lib\\iqlib.jar;C:\\usr\\sap\\ME0\\J00\\exe\\sapjvm_6\\lib\\tools.jar;C:\\usr\\sap\\ME0\\J00\\j2ee\\cluster\\bin\\boot\\sap.com~tc~bl~jkernel_boot~impl.jar;C:\\usr\\sap\\ME0\\J00\\j2ee\\cluster\\bin\\boot\\jaas.jar;C:\\usr\\sap\\ME0\\J00\\j2ee\\cluster\\bin\\system\\sap.com~tc~bl~bytecode~library.jar;C:\\usr\\sap\\ME0\\J00\\j2ee\\cluster\\bin\\boot\\memoryanalyzer.jar") (Message 16018)
at com.sap.me.frame.BaseDAO.abort(BaseDAO.java:2615)
at com.sap.me.frame.BasicBOBean.abort(BasicBOBean.java:2066)
at com.sap.me.activity.ActivityBOBean.execute(ActivityBOBean.java:499)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sun.proxy.$Proxy1166.execute(Unknown Source)
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:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1845.execute(Unknown Source)
at com.sap.me.numbering.NextNumberBOBean.formatNextValues(NextNumberBOBean.java:1125)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MethodRetry.invoke(Interceptors_MethodRetry.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sun.proxy.$Proxy268.formatNextValues(Unknown Source)
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:597)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at com.sun.proxy.$Proxy1865.formatNextValues(Unknown Source)
at com.sap.me.numbering.NextNumberApplicationBean.createSampleValue(NextNumberApplicationBean.java:405)
at com.sap.me.numbering.NextNumberApplicationBean.populateApplicationVO(NextNumberApplicationBean.java:470)
at com.sap.me.numbering.NextNumberApplicationBean.update(NextNumberApplicationBean.java:546)
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:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatefulTransactionAssociation.invoke(Interceptors_StatefulTransactionAssociation.java:45)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatefulSessionInstanceGetter.invoke(Interceptors_StatefulSessionInstanceGetter.java:37)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sun.proxy.$Proxy274.update(Unknown Source)
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:597)
at com.sap.me.coral.core.controller.EJBServiceProxy.invoke(EJBServiceProxy.java:110)
at com.sun.proxy.$Proxy1864.update(Unknown Source)
at com.sap.me.coral.core.command.DefaultSaveCommand.handleCmd(DefaultSaveCommand.java:77)
at com.sap.me.coral.core.command.AbstractCommand.execute(AbstractCommand.java:218)
at com.sap.me.coral.core.controller.ActivityServlet.processExistingApplicationRequest(ActivityServlet.java:502)
at com.sap.me.coral.core.controller.ActivityServlet.handleRequest(ActivityServlet.java:122)
at com.sap.me.coral.core.controller.BaseServlet.processRequest(BaseServlet.java:122)
at com.sap.me.coral.core.controller.BaseServlet.doPost(BaseServlet.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.me.frame.web.MeEntranceFilter.doFilter(MeEntranceFilter.java:36)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
As an experiment I took out all of the logic I originally had and just have it now writing to a text file and this Activity Hook works if I attach it to a Operation Activity Hook (POST_START) without any problems.
So I am wondering what the difference between that and an Activity Hook for Next Number Matinenance?
Thank you,
Mike Jewson

Next Number Generation Activity to use Base36 without I, O, Q

Hi all,
Need to have a Next Number Activity Hook to generate a sequence number similar to a base 36 with the exception of letters that could be confused with numbers: I, O, Q.
I have an activity hook created that generates the number I want to use without any problems at all.
Example:
16 = 000G
17 = 000H
18 = 000J <- Skips the letter I
19 = 000K
20 = 000L
But when putting the this into the inData object to be returned it is ignored.
inData.put("CURRENT_SEQUENCE", finalValue);
Any thoughts as a way I can get this to work?
Thanks,
Mike

Ok I finally had some time to work on this.
Within Next Number Maintenance if the Number Base is set to 34 it does exclude I and O (good), but stops at W (bad). No X, Y, or Z (bad). Plus it still includes Q (bad).
i.e.
TEST-000U
TEST-000V
TEST-000W
TEST-0010
TEST-0011
If the Number Base is set to 33, I, O, and Q are included (bad) and it also stops at W (bad).
Neither are acceptable solutions. So...
I have figured out an ugly workaround:
In Next Number Maintenance set Number Base to 36.
Then insert the invalid SFC numbers into the ID_USED table.
i.e.
INSERT INTO ID_USED (HANDLE, SITE, ID, ID_TYPE, CREATE_DATE, ARCHIVED) VALUES ('IDUsedBO:1000,TEST-000I,S', '1000', 'TEST-000I', 'S', TO_DATE('05/04/2010','MM/DD/YYYY'), 'false');
INSERT INTO ID_USED (HANDLE, SITE, ID, ID_TYPE, CREATE_DATE, ARCHIVED) VALUES ('IDUsedBO:1000,TEST-000O,S', '1000', 'TEST-000O', 'S', TO_DATE('05/04/2010','MM/DD/YYYY'), 'false');
INSERT INTO ID_USED (HANDLE, SITE, ID, ID_TYPE, CREATE_DATE, ARCHIVED) VALUES ('IDUsedBO:1000,TEST-000Q,S', '1000', 'TEST-000Q', 'S', TO_DATE('05/04/2010','MM/DD/YYYY'), 'false');
INSERT INTO ID_USED (HANDLE, SITE, ID, ID_TYPE, CREATE_DATE, ARCHIVED) VALUES ('IDUsedBO:1000,TEST-001I,S', '1000', 'TEST-001I', 'S', TO_DATE('05/04/2010','MM/DD/YYYY'), 'false');
INSERT INTO ID_USED (HANDLE, SITE, ID, ID_TYPE, CREATE_DATE, ARCHIVED) VALUES ('IDUsedBO:1000,TEST-001O,S', '1000', 'TEST-001O', 'S', TO_DATE('05/04/2010','MM/DD/YYYY'), 'false');
INSERT INTO ID_USED (HANDLE, SITE, ID, ID_TYPE, CREATE_DATE, ARCHIVED) VALUES ('IDUsedBO:1000,TEST-001Q,S', '1000', 'TEST-001Q', 'S', TO_DATE('05/04/2010','MM/DD/YYYY'), 'false');
Unfortunately this will need to be done for all of the potentially bad SFC's. I will defiantly need to write a small app for that.
Then when the Next Number is called for the SFC, the system would notice that that number is already used and jump to the next available number.
Also by using the ID_USED table should anyone want reports there would not be any bogus SFC data in the system.
This work exactly as I want on our test server.
So before I truly implement this on our Production server does anyone see any potential downfalls to this workaround? Questions and/or comments welcome.
Thanks,
Mike

Generating next number from the SQL database using java

Hi friends, I have a problem and need your help. I am working on a project about submitting claims form through the adobe PDF file and SQL database. I have problem working on a web service (written in java) that will generate the next Invoice Number from the SQL Database table. The field type for the column is text(var char). *Example: I first need to get into the table and search for the last Invoice number in the table and if the last invoice number in the table from the database is 3, i would want to generate the next number which is 4 and filled it up in the PDF file through web service that i am implementing. Can you all provide me some guidelines on how to implement this method in my web service?
Thanks a lot. I need it by today. Hope someone can reply this as soon as possible.
Lim89
Edited by: LIM89 on Apr 2, 2008 7:10 PM

far simpler to use a sequence generator, which most databases support.
Suggested method to get the max value in the column is NOT secure, unless you lock the entire table for update before you do so, which is a severe performance penalty.

How do I obtain the next number for a Primary Key using an ADF View Object?

I have two separate View Objects (A & B) for the same Entity Object. View Object A does a SELECT on all of the fields in the table. This View Object is where I execute my adds and updates. View Object B is only used to retrieve the next number for the primary key. This is done so that when I add a row to the database, I always get the max number of the primary key and add one to it. I accomplished this by setting the SQL mode to Expert and using the SQL: "SELECT MAX(NBR) AS MAX_NUMBER FROM TABLE_1". This may be overkill having a seperate View Object for this, but so far this is the only way I have found to obtain the next number. However, I have discovered that this way does not always work.
The problem I'm running into is when I try to add multiple records to View Object A without committing the transaction between each add. Because View Object B is disconnected from View Object A, the MAX_NUMBER of View Object B comes back with the same number for each add I do on View Object A. So I know I must retrieve the MAX_NUMBER from View Object A.
I've tried using the following code in my Table1ViewImpl class:
this.setQuery("SELECT MAX(Table1.NBR) AS MAX_NUMBER FROM TABLE_1 Table1");
this.executeQuery();
The view object now has what I want, but I have yet to figure a way to extract the MAX_NUMBER out of the View Object. I've also looked into using the method addDynamicAttribute() but I can't figure out any way to set the attribute with the MAX_NUMBER.
I can't be the only one trying to retrieve the next number from a database table using ADF. Can anyone help me with this? FYI - I'm using JDev 10.1.3 EA.

You missing the point.
On a multi-user db knowing the next highest number doesn't guarantee the number will be available when it comes time to commit the record. You can prove this to yourself by opening two instances of your app and do whatever you do to add a new record to your VO. Both will assume the same number, and when you commit an error will be generated
You must use sequences to avoid the possibility of duplicate keys. If you are trying to avoid gaps in your numbering then you need to convince yourself why this is necessary.

How to solve "Database inconsistent" error?

Hi,
when clicking on a task in my UWL i get this error. Why is that? How can i solve it?
TIA
Michael
500   Internal Server Error           SAP NetWeaver Application Server/Java AS
The initial exception that caused the request to fail, was:
com.sap.bpem.tm.exception.TechnicalTaskException: Database inconsistent, please contact your system administrator
    at com.sap.bpem.tm.impl.TaskManagerImpl.identifyNoSuchTaskExceptionFlavor(TaskManagerImpl.java:1567)
    at com.sap.bpem.tm.impl.TaskManagerImpl.getTaskInstanceObject(TaskManagerImpl.java:1524)
    at com.sap.bpem.tm.impl.TaskManagerImpl.getTask(TaskManagerImpl.java:1032)
    at com.sap.bpem.tm.impl.TaskManagerBean.getTask(TaskManagerBean.java:79)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    ... 91 more
See full exception chain for details.
Failed to process request. Please contact your system administrator.
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
System Environment
Client
Web Dynpro Client Type     HTML Client
User agent     Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7
Client Type     ns7
Client Type Profile     nn7
ActiveX     disabled
Java Applets     enabled
Accessibility mode     disabled
Rendering engine:     Lightspeed
Inline CSS:      enabled
Validate by rendering:      enabled
Server
Web Dynpro Runtime     vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.1101.20081121165726.0000', change number: '34307', codeline: NW711_01_REL
J2EE Engine     7.11.3710.34306.20081117170308
System ID (SID)     HNC
Server Node ID     |5055250|50552|Server 00 00_50552|saphnc/10.213.20.68|SERVER|RUNNING
Java VM     SAP Java 64-Bit Server VM, version:5.1.024, vendor: SAP AG
Operating system     Windows 2003, version: 5.2, architecture: amd64
Application
Java EE Application (deployable object)     sap.com/tcbpemwdui~taskinstance
Web Dynpro Application     ATaskExecution
Request URI     /webdynpro/dispatcher/sap.com/tcbpemwdui~taskinstance/ATaskExecution
Version     vendor: 'sap.com', name: 'tc/bpem/wdui/taskinstance', location: 'SAP AG', counter: '7.1101.20081107110357.0000', change number: '31'
Session & Other
Session Locale     de_DE
Session Timezone     Central European Time
Time of Failure     Tue Mar 24 12:18:45 CET 2009 (Java Time: 1237893525656)
Session User     ClientUser(id=USER.PRIVATE_DATASOURCE.un:neumann, name=neumann)
Client Session Id     p6E1GkmC7IqjpxmHR9bKm6ipRLUa3H83IAESI00A_SAP
Client Window Id     WIDx1237893542193
Application Session Id     pBsSrSGyXYyMkAL31ExbcA9YvaW5iZijHiiopfzm48oA
Web Dynpro Code Generation Infos
sap.com/tcbpemwdui~appcontainer
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapDictionaryGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:23+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapDictionaryGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:49+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapGenerationFrameworkCore     7.1101.20081107110357.0000
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapIdeWebDynproCheckLayer     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:35+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapMetamodelCommon     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:14:39+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapMetamodelCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:11:46+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapMetamodelDictionary     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:19:49+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapMetamodelWebDynpro     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:25:44+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapWebDynproGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:46+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapWebDynproGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:37:12+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapWebDynproRuntimeGen     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:34:49+0000, changelist=32183, host=pwdfm245, is-central=true)
sap.com/tcbpemwdui~attachments
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapDictionaryGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:23+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapDictionaryGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:49+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapGenerationFrameworkCore     7.1101.20081107110357.0000
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapIdeWebDynproCheckLayer     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:35+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapMetamodelCommon     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:14:39+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapMetamodelCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:11:46+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapMetamodelDictionary     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:19:49+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapMetamodelWebDynpro     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:25:44+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapWebDynproGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:46+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapWebDynproGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:37:12+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapWebDynproRuntimeGen     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:34:49+0000, changelist=32183, host=pwdfm245, is-central=true)
sap.com/tcbpemwdui~notes

WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapDictionaryGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:23+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapDictionaryGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:49+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapGenerationFrameworkCore     7.1101.20081107110357.0000
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapIdeWebDynproCheckLayer     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:35+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapMetamodelCommon     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:14:39+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapMetamodelCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:11:46+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapMetamodelDictionary     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:19:49+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapMetamodelWebDynpro     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:25:44+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapWebDynproGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:46+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapWebDynproGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:37:12+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapWebDynproRuntimeGen     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:34:49+0000, changelist=32183, host=pwdfm245, is-central=true)
sap.com/tcbpemwdui~taskinstance
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapDictionaryGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:23+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapDictionaryGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:49+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapGenerationFrameworkCore     7.1101.20081107110357.0000
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapIdeWebDynproCheckLayer     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:35+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapMetamodelCommon     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:14:39+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapMetamodelCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:11:46+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapMetamodelDictionary     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:19:49+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapMetamodelWebDynpro     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:25:44+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapWebDynproGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:46+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapWebDynproGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:37:12+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapWebDynproRuntimeGen     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:34:49+0000, changelist=32183, host=pwdfm245, is-central=true)
sap.com/tcwdapi
WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationCore     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:30:00+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationTemplates     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:30:16+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapGenerationFrameworkCore     7.1101.20081121165726.0000
WD web module webdynpro/resources/sap.com/tcwdapi: SapIdeWebDynproCheckLayer     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:43:48+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCommon     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:21:10+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCore     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:17:50+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelDictionary     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:25:15+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelWebDynpro     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:31:48+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationCore     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:43:58+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationTemplates     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:44:06+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproRuntimeGen     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:42:01+0000, changelist=32183, host=pwdfm245, is-central=true)
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(id=pBsSrSGyXYyMkAL31ExbcA9YvaW5iZijHiiopfzm48oA, name=com.sap.tc.bpem.wdui.taskinstance.ataskexecution.ATaskExecution). The causing exception is nested. RID=8a21d490186511de8a38000c2932868d
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:680)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:239)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

How to alter sequence next number

Can we alter sequence next number. I want to start it from minval.

To restart the sequence at a different number, you must drop and re-create it.
If you change the INCREMENT BY value before the first invocation of NEXTVAL, some sequence numbers will be skipped. Therefore, if you want to retain the original START WITH value, you must drop the sequence and re-create it with the original START WITH value and the new INCREMENT BY value.
Oracle Database performs some validations. For example, a new MAXVALUE cannot be imposed that is less than the current sequence number.

How to find next number range for project definition in tcode CJ20N

Hai Experts,
Please help me 'How to find next number range for project definition in tcode "CJ20N". I was trying in function module NUMBER_GET_NEXT. Is it right function module? If its right what input i need to give for this tcode and for the field project definition?
Note: I searched in forum before posting, but couldn't find the solution.
Thanks
Regards,
Prabu S.

Hi,
For project defination internal number is assigned by system.
When you saves's project then system allocate one number to project defination, you can view it,
SE11 >>> table PROJ >> Click on contents >>> execute,
here you will get your project defination & number is assigned to project defination.
kapil

How to Find the number of Databases in a server.

HI,
Please tell me how to find the number of Databases are in a server . when the DB is not up.
ps -ef | grep ora_
This i know whether our DB is up or not. But i want to know how many databases are in a server .If the database is down .
Cheers,
Gobi.

Hi,
[oracle@oralinux admin]$ lsnrctl status
LSNRCTL for Linux: Version 9.2.0.4.0 - Production on 01-DEC-2006 16:25:41
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
TNS-01169: The listener has not recognized the password
[oracle@oralinux admin]$
Plz give me the solution.
Cheers ,
Gobi.

Database Inconsistency Nightmare

As an avid user and supporter of Aperture since it's release, I now have an new issue. I am a pro photojournalist using Aperture every day for all my magazine assignment work and I feel like I know the program very well after 2+ years of heavy daily use.
I have never had any serious problems with the program at all, until one week ago.
The problems started when I launched aperture and got a database inconsistency dialog box. I was not too worried as I have had this once or twice in the past and I just relaunched the app with apple and option keys down and rebuilt the database. Everything seemed ok but then I noticed that 2,400 of my 12,000 referenced images were tagged as missing. I thought this was strange, and I used "Manage Referenced Files" to see what was going on and reconnect the missing files. I also noticed that 2 subjects had a second version not in a stack that contained the thumbnail for each image without metadata, while the normal version and stack with metadata had no thumbnail! On my FireWire drive 1 which holds a first copy of all referenced files in my library, each subject has a corresponding folder and I started to reconnect the offline and missing files. For most of the subjects everything went fine, but then there were 4 subjects where I encountered very unexpected problems. Firstly the names of the Master images for some subjects had been changed more that one year earlier, but the reconnect dialog box showed the original filename from the camera as the master filename. It did not want to "Reconnect All" so the only way is one by one!
Then I notice that the smart folders set to show "Offline" and "Missing" masters are inaccurate for some reason.
I even have a few "Managed" masters that will not export because the dialog box comes up to tell me that the image is "Offline" or "Unavailable". What? Ok so at this point I decide that since I have everything backed up on two separate Firewire drives and a server in California, that it may just be cleaner to reinstall Aperture and revert to a recent Vault. I did this and guess what, same problems plus a few more headaches reconnecting masters!
The biggest problem at this point is that for two subjects, the captions and adjustments are in a version that has no thumbnail, shows the "Missing" tag in the Metadata panel listing the original filename from the camera as the Master Filename, while there is a new mysterious version 2 which has a thumbnail, no caption, the offline tag and and shows the correct Master Filename. If I reconnect the masters for these images it still shows as missing for the normal version which has the captions, keywords and adjustments.
At this point I have decided that for two of the subjects One is Versailles 600 images and the other Cyprus 700 images, that I will probably end up having to just reimport these two subjects and manually move the caption for each image.
This is all starting to make me call into question the stability of this type of system for archiving large amounts of images. True that with all the backups and the normal robustness of Aperture you should not loose images. But if the Masters get unlinked in a corrupt way from the database you CAN loose a large part of your post processing work. And the worst seams to be that this can happen even if you DO know what you are doing.
This does not at all mean I am going to stop using Aperture, but it does make me feel a little more weary from an archival standpoint about keeping all metadata and adjustments separate from master images.

Thanks for all your replies. And yes the Project container is a fantastic way to back things up. It is especially useful for moving a project from one Library to another without risk of overwriting files.
Naturally if I could get my corrupt projects in order I would export the projects, including the masters and then reimport them. But Aperture is not going to let me do that with these corrupt Projects, as the masters are not be properly linked. I have tried everything I could think of.
There are still some really weird things going on with the database in my library. One really strange thing is that some referenced images that DO have the master linked and show the normal reference tag, but will not Consolidate as the dialog comes up "The selection does not contain any referenced files".
But then for the same image you can choose "Show in finder" and it goes straight to the master on it's external drive! How strange is that. For that matter it will also not "Relocate Master" for the image because it says that the master is "Offline or cannot be found". OK then here comes the weirdest part: It will export the image without a hitch! Managed referenced files shows these images as connected and black.
Then the other really bad thing is that some of the managed images will not export or relocate as the dialog comes up "Offline or cannot be found". I have rebuilt the library and everything else to no avail.
The thing that bothers me about this is that if this can happen to me, who spends untold hours on Aperture and on the computer in general and I believe I do know quite a lot about the program, what is going to happen to the many photographers who do not fully grasp the abstract file management of Aperture?
Maybe it is more stable to run your Library as Managed, but for working photographers who are usually laptop users it is almost essential to keep the masters on an external Ruggged drive. If you put the Library on the external drive the performance which is already sometimes sluggish when you need to work very quickly (even with the most powerful MacBook Pro) becomes too beach ball when on an external drive.
In any event I think that if I can ever get my Library back in order, in addition to the many backups of masters and vaults, I am going to export each project including masters and back that up too on a regular basis. Seems like a lot of work backing up to maintain the integrity of a database!
Cheers

Cannot Activate data type in ABAP Database Inconsistent

Hi,
can you please help me on this? We could not activate the data type abap proxy in SPROXY.
Here is the error:
Database inconsistent: TABL XYZ not found.
The object is inactive. Is there a way to delete the object in the backend?
Or do you know other way to solve this?

I already recreated the object in ESR, but we are still getting the error in SPROXY whether you regenerate, delete or activate proxy. If I checked the proxy name, it is in a form of a structure and is activated but the data type in SPROXY is still in inactive mode.
I could not remember how this error came up but it seems dependent objects for the data type are not generated properly that's why the error is TABL object is not found.
Do you have other way on how to delete the inactive proxy in ABAP?

Calling the next number in an array through a function?

ow do I request the next number in an array?
For example - currently being used for a loop:
for (i=0; i = levelSettings[0]; i++)
But when the function (named - NextLevel() ) is called I would like that loop to call the next number in that array.
Example:
(i=0; i = levelSettings[1]; i++) //Not the change in the levelSettings[x]
I would like this to work for all subsequent numbers in that particular array - so it can continue through to levelSettings[10] and so on.
Cheers!

in the outter for-loop, k is varying from 0 to the last index in levelSettings.
in the inner for-loop i varies from 0 to levelSettings[k].
ie,
0 to levelSettings[0]
0 to levelSettings[1]
0 to levelSettings[last_index]

SQ01 restricting the number of database accesses

Hi,
I created a report using SAP Query (SQ01). When I run the query a dialog box appears asking the maximum number of database accesses.
The value entered here directly affects the result of the report. The user has to change the value manually in order to see the complete set of results, set it 999999 for example.
I want to get rid of that dialog box. Is it possible?
If not can I change the default value '100' to anything I want?
Thanks...

That is true, it is a bit loaded report. It includes additional fields, selections and another select statement for each record. I tried to keep it as simple as possible but that is the only way that I could think of.
The joins are:
VBAK - VBAP
VBAP - VBUP
VBAP - MARD
VBAP - MARA
The report basicly brings the stock amounts of open sales order items. In addition the total consignment level for that item is also requested, so I wrote a select statement in record processing which finds the total consignment level from the MKOL table for that item. I could not simply add MKOL to my join list because it than divides each item to the number of vendors that exists in the MKOL table. The user is not interested in the amount for each vendor, only the total amount.
The performance is not that bad, but as I said before the result of the report is different for different limits of database accesses.
Is there a way to omit the limit?

Next Number Maintenance - Database inconsistency

Similar Messages

Maybe you are looking for