Creation of a new member in 2 different Planning Budgeting Applications
Hi,
I have a query.
We have 2 planning applications with the same number of dimensions. One application is created just to store the historical data and the actual data month to month.
The other application is where the budgets are created and 1 or 2 years of actual data is loaded.Many times in the year we need to add some new account members (new accounts get created) or new cost centers gets added. In this case we need to add the member in the 2 different applications. This creates maintenance issues at times . The users who keep adding at times forget to add in both applications.
Is it possible by using any method that we can add the member at one time to both the applications?
We are using Planning version - 11.1.1.3.
Thanks in advance.
Not if they are being manually added, you could look at automating the process usIng the outlineload utility or ODI if they are classic applications.
Cheers
John
http://john-goodwin.blogspot.com/
Similar Messages
-
Creation Of A Single Purchase Requisition From Different Planned Orders
Hi,
After MRP run i get different Planned Orders for different raw materials . My requirement is that can i combine all the Planned Orders for diiferent materials into a single Purchase Requisition.This is a urgent requirement.
If useful i will award points.
Regards
JimmyHi,
it is not possible to combine with planned orders for different materials into single PR but differet PR can combine into a single Purchase Order.
pls let me know any clarification.
thanks
mohan
Message was edited by:
Mohan Ramalingam -
Switch phone numbers with a family member on a different plan
Hello!
I have a Verizon cell phone plan and my mother has a separate plan. A few years ago my mother got a phone that she absolutely hated so I agreed to take her phone and she took mine. What ended up happening is that she has a phone that I technically pay for each month under my plan and I have a phone that she pays for under her plan. We are both at the end of our contracts now but I want to switch the phone numbers to the proper plans so we pay for our own phones. This is especially important since she wants to cancel her account and go to a different carrier but I want to stay with Verizon.
How do I go about doing this? If she cancels her plan is there a way I can keep the number but bring it to my account and how will this affect my upgrade? I think my mother would also like to bring her current number (the phone under my account) to her new carrier.
Thank you very much for any help you can give me!Hi irishpat87,
Let's explore options to complete the number swap! As indicated by others (thanks!), doing an Assumption of Liability is a way to accomplish what you want to do and since you are at the end of your contracts (as per your original post), contract length carries over as is. I trust that this will answer your questions fully. Please visit this link http://vz.to/187wQRK for details on the Assumption of Liability process.
AntonioC_VZW
Follow us on Twitter at www.twitter.com/VZWSupport -
Creation of new task in a different TR
Hi All,
I have a modification to be made to a User exit. When I'm trying to change to editable mode, a new task in the default TR (already associated with the user exit) is being created. but I want to create the new task in a different TR.
is there any possibility of changing the TR (charm already associated with the user exit) associated with the user exit to a new TR (new charm)?
Please help...
Thanks & Regards,
SriLalithaHi Sri Latha,
There is option to create the TR for same modification.If you are changing the same modification it will create one sub task under main TR.
SO you can change your modification and under old old TR only.Before going to release the TR,
You can create one empty TR include those modifications in new TR.
Thanks for understanding.
BR,
Veeru -
Ann: SuperScheduler: a new member of Super 1.80
Announcement: Super 1.8 - an EJB/J2EE monitoring/admin tool with
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperReport
SuperStress
has got a new member: SuperScheduler
You can anomyously down load it free from:
http://www.acelet.com.
Super is a component based administration tool for EJB/J2ee.
It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A full-featured logging/tracing tool for centralized, chronological logging.
* A PeekPoke tool to read/write attributes from EJBs.
* A Stress test tool.
* A global environment tool.
* A report tool.
* A Scheduler tool.
It is written in pure Java.
The current version support:
* Universal servers.
* Weblogic 5.1, 6.0
* Weblogic 6.1 with EJB 2.
What is new:
Version 1.80 March 2002
Enhancement:
1. Add new component: SuperScheduler
Bug fix:
1. SuperLogging: Verbose should ignore class registration.
2. SuperLogging-tracing: an exception was thrown if the java class without package
name.
Version 1.70 January 2002
Enhancement:
1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
weblogic 6.1, need download an application).
2. Add alias names for log threshold as new Java suggests.
3. New component: SuperReport.
Change:
1. SuperLogging: Log database parameters are specified in a properties file, instead
of EJB's deployment descriptor. It is more convenient and it avoids some potential
problems. No change for development, easier for administration.
Bug fix:
1. Add Source Path Panel now accepts both directory and jar file.
2. Bug in SuperEnvironment example (for version 1.60 only).
Version 1.60 December 2001
Enhancement:
1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
2. Add timeout parameter to logging access.
3. New installation program with A). Easy install. B). Remote command line install.
4. Support EJB 2.0 for Weblogic 6.1.
5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
was supported since version 1.5).
Change:
1. Poke: argument list is set at define time, not invoke time.
2. Default log database change to server mode from web server mode, booting performance
to 10-20 times.
Bug fix:
1. If the returned object is null, Peek did not handle it correctly.
2. If the value was too big, TimeSeries chart did not handle it correctly. Now
it can handle up to 1.0E300.
3. Help message was difficult to access in installation program.
4. Source code panel now both highlights and marks the line in question (before
it was only highlight using JDK 1.2, not JDK 1.3).
5. Delete an item on PeekPoke and add a new one generated an error.
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
Changes:
1. The structure of log database changed. You need delete old installation and
install everything new.
2. The format of time stamp of SuperLogging changed. It is not locale dependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clustering environment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, it is treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods will not try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put log database
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on<font size=+0> the Source Code
Panel (as a work-a-round for JDK 1.3).</font>
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
Changes:
1. All changes are backward compatible, but you may need to recompile monitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message will not show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: press F1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.Not if they are being manually added, you could look at automating the process usIng the outlineload utility or ODI if they are classic applications.
Cheers
John
http://john-goodwin.blogspot.com/ -
Ann: SuperReport - a new member from Super 1.7
Announcement: Super 1.7 - an EJB/J2EE monitoring tool with
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperStress
has got a new member: SuperReport
You can anomyously down load it free from:
http://www.acelet.com.
Super is a component based administration tool for EJB/J2ee.
It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A PeekPoke tool to read/write attributes from EJBs.
* A full-featured logging/tracing tool for centralized, chronological logging.
* A Stress test tool.
* A global environment tool.
* A report tool.
It is written in pure Java.
The current version support:
* Universal servers.
* Weblogic 5.1, 6.0
* Weblogic 6.1 with EJB 2.
What is new:
Version 1.70 January 2002
Enhancement:
1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
weblogic 6.1, need download an application).
2. Add alias names for log threshold as new Java suggests.
3. New component: SuperReport.
Change:
1. SuperLogging: Log database parameters are specified in a properties file, instead
of EJB's deployment descriptor. It is more convenient and it avoids some potential
problems. No change for development, easier for administration.
Bug fix:
1. Add Source Path Panel now accepts both directory and jar file.
2. Bug in SuperEnvironment example (for version 1.60 only).
Version 1.60 December 2001
Enhancement:
1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
2. Add timeout parameter to logging access.
3. New installation program with A). Easy install. B). Remote command line install.
4. Support EJB 2.0 for Weblogic 6.1.
5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
was supported since version 1.5).
Change:
1. Poke: argument list is set at define time, not invoke time.
2. Default log database change to server mode from web server mode, booting performance
to 10-20 times.
Bug fix:
1. If the returned object is null, Peek did not handle it correctly.
2. If the value was too big, TimeSeries chart did not handle it correctly. Now
it can handle up to 1.0E300.
3. Help message was difficult to access in installation program.
4. Source code panel now both highlights and marks the line in question (before
it was only highlight using JDK 1.2, not JDK 1.3).
5. Delete an item on PeekPoke and add a new one generated an error.
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
Changes:
1. The structure of log database changed. You need delete old installation and
install everything new.
2. The format of time stamp of SuperLogging changed. It is not locale dependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clustering environment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, it is treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods will not try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put log database
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on<font size=+0> the Source Code
Panel (as a work-a-round for JDK 1.3).</font>
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
Changes:
1. All changes are backward compatible, but you may need to recompile monitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message will not show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: press F1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.Announcement: Super 1.7 - an EJB/J2EE monitoring tool with
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperStress
has got a new member: SuperReport
You can anomyously down load it free from:
http://www.acelet.com.
Super is a component based administration tool for EJB/J2ee.
It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE/EJB monitor.
* A gateway to EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A PeekPoke tool to read/write attributes from EJBs.
* A full-featured logging/tracing tool for centralized, chronological logging.
* A Stress test tool.
* A global environment tool.
* A report tool.
It is written in pure Java.
The current version support:
* Universal servers.
* Weblogic 5.1, 6.0
* Weblogic 6.1 with EJB 2.
What is new:
Version 1.70 January 2002
Enhancement:
1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
weblogic 6.1, need download an application).
2. Add alias names for log threshold as new Java suggests.
3. New component: SuperReport.
Change:
1. SuperLogging: Log database parameters are specified in a properties file, instead
of EJB's deployment descriptor. It is more convenient and it avoids some potential
problems. No change for development, easier for administration.
Bug fix:
1. Add Source Path Panel now accepts both directory and jar file.
2. Bug in SuperEnvironment example (for version 1.60 only).
Version 1.60 December 2001
Enhancement:
1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
2. Add timeout parameter to logging access.
3. New installation program with A). Easy install. B). Remote command line install.
4. Support EJB 2.0 for Weblogic 6.1.
5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
was supported since version 1.5).
Change:
1. Poke: argument list is set at define time, not invoke time.
2. Default log database change to server mode from web server mode, booting performance
to 10-20 times.
Bug fix:
1. If the returned object is null, Peek did not handle it correctly.
2. If the value was too big, TimeSeries chart did not handle it correctly. Now
it can handle up to 1.0E300.
3. Help message was difficult to access in installation program.
4. Source code panel now both highlights and marks the line in question (before
it was only highlight using JDK 1.2, not JDK 1.3).
5. Delete an item on PeekPoke and add a new one generated an error.
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
Changes:
1. The structure of log database changed. You need delete old installation and
install everything new.
2. The format of time stamp of SuperLogging changed. It is not locale dependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clustering environment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, it is treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods will not try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put log database
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on<font size=+0> the Source Code
Panel (as a work-a-round for JDK 1.3).</font>
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
Changes:
1. All changes are backward compatible, but you may need to recompile monitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message will not show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: press F1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks. -
Function of HOLD DATA in the settings for creation of a new screen.
Hi,
Since i'm new to ABAP and still learning my way through, i would really appreciate if somebody can help me out with the exact functioning of selecting the check box 'HOLD DATA' under the settings option while creation of a new screen.
Thanks for any help extended.Take simple scenario of SE38. The Screen for the transaction has the Flag "HOLD DATA" as Ticked.
Now enter some program name on the field and Click - Utilities-> User Profile -> Hold data.
Now come out of the transaction, go back to the same transaction. The name of the Program that you entered earlier will appear on the input field.
So if the screen doesn't have "Hold Data" set the functions of HOLD data, SET DATA, DELETE data will not work.
Also try using SET DATA For the Program input field.
SAP Help :
If you activate this option, the following functions are supported for the screen at runtime:
System -> User profile -> Hold data
-> Set data
-> Delete data
The Hold data function allows you to hold onto any entries you have made on the screen. When the screen is next processed (even in a different mode), the system then automatically redisplays the data in the input fields.
If the option is not activated, these functions are ineffective at screen runtime. -
Step By Step Creation Of A new Business Object
hi,
Please Give Me Details Of A Business Object,like step by step creation of a new business object and it's utilization.Create a business object (SWO1).
Give the business object name prefixed with Z_.
Enter the following fields with values:
Object type: Z_TESTXX
This is the internal technical key. Page: 1
Object type can have maximum 10 characters. This must be unique across all object type. Objects are specific instances of object types at runtime.
Object name: Object_Name_for_XX
The object type is addressed with this name by external applications. This is a descriptive English name and can be up to 32 characters. This also must be unique across all object type.
Name: Object Name: XX
This is a meaningful name of the business object.
Description: Object Description: XX
Page: 1
Object description, can be up to 40 characters.
Program: Z_TESTXX
Each object type has an ABAP/4 program in which methods of the object are implemented. This program is generated automatically when you create or revise an object type.
Application: indicates cross application.
3: Create an event.
Open the Object type in change mode. When you change your subtype the first step is to create a new event, this is done by selecting the Event node and clicking the create button. Give the event a name and a description. Next set the status of this object type component to implemented.
Event: Z_EVENT_XX
Name: Event name: XX
Description: Event Description: XX
Click on the new event andu2026
Edit - Change Release Status- Object Type Component - Implemented
(A small box sign vanishes from the right side of the event, indicating that it is implemented)
There can be multiple triggering events for a standard/customer task.
In R/3 4.0 the release strategy for new Object Types and Object Type Components (methods, attributes, events, etc.) was enhanced. Now when an object type and/or components are created, there are different statuses to select, based on its required purpose. The statuses are:
u2022 Modeled - objects cannot be accessed at runtime. This is the status that is automatically set when an object type or component is created. Items with a modeled status cannot be referenced in any type of workflow task.
u2022 Implemented - objects can be used internally in a test environment. They are accessible, but may not be stable (especially if no delegation has been defined).
u2022 Released - objects are ready for production. Note: Local objects cannot be released.
u2022 Obsolete - objects are typically replaced by new functionality or incompatible with previous versions. This status is optional.
4: Create a method.
Next a method must be created without using any function module template. When creating the method ensure that the method call is synchronous - this means that the method doesn't require a terminating event.
A method can be synchronous or asynchronous. Synchronous Method
Method that, for the duration of its execution, assumes the process control and, after its execution, reports to the calling component (work item manager, in this case).
Synchronous methods can return the following data, if defined: Return parameters, one result and Exceptions.
Terminating events can also be defined for a single-step task described with a synchronous method. At runtime, the relevant work item is then terminated either when the synchronous method is successfully executed or when one of the defined terminating events occurs.
Asynchronous Method
Method that, after its execution, does not report directly to the calling component (work item manager, in this case).
Asynchronous object methods do not return results, parameters or exceptions.
At least one terminating event must be defined for a single-step task described with an asynchronous object method.
At runtime, the relevant work item is only terminated if one of the defined terminating events occurs.
Next set the status of this object type component to implemented. The methods are not implemented unless you once open their program. Select the method and open its program. It gives a message u201CDo you want to generate a template automatically for the missing sectionu201D. Click u201CYesu201D. Inside the program insert the code u201CCALL TRANSACTION u2018FB03u2019. Display Financial Document.
Method: Z_METHODXX
Name: Method name: XX
Description: Method Description: XX
Edit - Change Release Status - Object Type Component - Implemented
5. Create Key fields.
Create key fields with ABAP dictionary field proposal.
It is the identifying key, via which the system can access a specific object, that is, an instance of the object type. The key fields of an object type are usually also the key fields in the table containing the header data for the object type. Only character-based data types are allowed as key fields. The total length allowed for all key fields is 70 characters. Each key field refers to a field in the ABAP Dictionary.
Enter u2018BKPFu2019 in table name field and select all the key fields. Press Continue button. Next set the status of these key fields to implemented.
Edit - Change Release Status -Object Type Component - Implemented
6:Implement business object.
The whole business object needs to be implemented so click on the business object title andu2026
Edit - Change Release Status - Object Type - Implemented
Now you can check the syntax, generate the Business Object and then test it. Execute the custom method you created and give the Company code, Document number and Year. -
Can not add a new member to the existing log group.
Dear all,
I just want to multiplex the online redo log to different devices for security reason. I just have one member for each group. So I want to use this command to add a new member.
alter database add logfile member '/u02/oracle/oradata/TEST/redo01.log' to ('/u01/app/oracle/oradata/TEST/redo01.log')
or
alter database add logfile member '/u02/oracle/oradata/TEST/redo01.log' to group 1.
But both commands failed with error pasted below:
ERROR at line 1:
ORA-19510: failed to set size of 102400 blocks for file "/u02/oracle/oradata/TEST/redo01.log" (block size=512)
ORA-27045: unable to close the file
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
Do you know what caused this problem?
Thanks,
RickyI just want to multiplex the online redo log to different devices for security reason. I just have one member for each group. So I want to use this command to add a new member.Not a BAD idea.. :)
ERROR at line 1:
ORA-19510: failed to set size of 102400 blocks for file "/u02/oracle/oradata/TEST/redo01.log" (block size=512)
ORA-27045: unable to close the file
Linux-x86_64 Error: 5: Input/output error
Additional information: 4It is running out of space. check the required space on mount point /u02 , if not you can create in another mount point as per your requirement.
THanks -
Move Exchange 2010 Server from AD Server to a new Member Server
Hi All,
I would like to get some suggestion on a particular task which i have presently , In my organisation i have a Exchange Server 2010 installed on Win2008 R2 DC (FSMO role Holder), also i got a ADC on Win2003 R2 Server for the same Domain , My
task is to move Exchange 2010 from DC to a new Member server without loosing mail boxes and present configuration ,Kindly guide me with the steps to achieve this task easly
Thanks & Regards
SameerHi Sameer and thanks for posting. Its good that you are moving exchange server from DC, because installing exchange server on DC its not recommended. To get the job done: 1.Install exchange server on the new Member server. (You can spread the roles on
the different servers if you are in the enterprise level organization.) 2.Create MailBox Databases according to your management style. 3.Move the mailboxes from DC server to the new Exchange server. 4.Move System Mailboxes to New server. 5.I would move FSMOs
to the ADC and shut down the old exchange for a week. 6.If everything was alright uninstall old exchange and move FSMOs back. I hope this helps. Farhad -
New member-internet readings low
HI, as a new member I chose the high internet for $29.95...when I check on my speed at the speed test site, i get 2.78-2.84 Mbps download and 583 kbs uploading...is that the maxium verizon high speed ? The double reading of downloading were done a different times of the day. I have XP SP2, 1024MB ram, 2.60 mghtz. I just left road runner and there I was getting close to 5 mb of downloading at times. Did I make a mistake in dropping RR? Maybe verizon is giving me the lighter version unknowingly?
Your download is right on the money. Your upload looks just a little under what you should get.
-
Hello I am a new member here and I want to introduce myself. I am known as Sakasa and what I do is graphics wallpapers designs. Most of the wallpapers are done for the Linux community and I will want to share some of these works in the near future with you all. I do not really get involve in OS development of graphics wallpapers desktops, themes or anything else.. Hopefully that my art can help this great community through the offering of the art. Here is my latest Arch Linux wallpapers.
http://bestfreewallpapers.net/tiki-brow … lleryId=12
Hope you like these.
Best Regards,
Last edited by sakasa (2010-05-15 17:25:46)Allan wrote:So... you are not making any wallpapers specifically for Arch, but rather rehashing wallpapers by changing the distro name on them to Arch. Combine that with joining the forums just to post a link to your website and I start hearing warning bells. Are you actually using Arch Linux at all or just here to "spam"?
I have done wallpapers for the linux community for a long time. Arch Linux is a great and known distro. Linux needs a push and this has always been my intention to go ahead and do what I must do and it is to help societies that offer their work for free and can express freely through. I do not need to spam or ever will. I want to make it strickly clear. Many distros have use my wallpapers in their different distro version and I am well known. Antix Linux, PCLinuxOS, and a few others have use my art in others OS, I do not recall right now. I do not care if this society, members or others uses my wallpapers for their distros or for their desktop looks as long as they can benefit from these then I a m doing my duty. Google sakasa and you will see. You comment: you are not making any wallpapers specifically for Arch, but rather rehashing wallpapers by changing the distro name on them to Arch my re: I make a nice wallpaper and after I go ahead and add up the different OS names like all artist do but not how you specify it above.. My art is original and I hold 100's of licenses It would not be fair for the linux society and other distros not to be able to obtain the same type of wallpapers. I do not think it would be correct that I as an artist will take only one side or a specific distro and leave the rest like they do not exist. Linux is for all and I am a truly belief that we must work together to encourage all the distros so we can grow as a bigger community in this world, which it is needed. I thought by offering that I will get an opposite of the response that I am getting from you. The warning bells you maybe hearing it from someone else. You have put me into in a interrogative situation without knowing me, only because I came here to offer to your OS an extra service in a noble way. This is shocking to me I do not judge or interrogate until I am really and truly sure to know completely a person intentions with time before I can judge or asking them a question and even if I do judge them it does not mean I am right, still I could be wrong. So I am very sensitive before I open my mouth to interrogate or ask questions to anyone like the ones you have make me here..
I do not need to spam. I take this very seriously and if you belief from your part that this is my intention then go ahead and erase me from your members list.
I hope that you can understand my message and I ask to excuse my English because it is not the best.
One more thing I am not here to work in the development of your distro or any distro as I mentioned in the above post. I feel exciting when others are doing their work too because this help greatly the Linux community and we most expand linux within unlimited ways if we want it to succeed even more.. This is my belief..
Sincerely, Sakasa
Last edited by sakasa (2010-05-16 06:38:48) -
Doubt in creation of a new object
Hi All,
I have one doubt in creation of a new object.If a new object is to be created and it is not a subtype
of any existing object, then what should we enter in the Program field for creating the object?
I hope I am clear with my question.
Thanks in Advance,
Saket.Hi Saket,
Following will be required for created a custom business object.
1. Object Type - ZTEST (Internal Techincal Key)
2. Object Name - ZTESTNAME (Technical Key Name)
3. Name - TEST (Name of BO, it is used while selecting the object type)
4. Description - (Short Description of BO)
5. Program - ZTESTPROGRAM (ABAP program in which the methods of the object type are implemented)
6. Application - A or B.. etc (Area to which your BO is related)
Please remember that you can learn these basic things by giving F1 help on those fields and in HELP.SAP.COM.
Regards,
Gautham Paspala -
How to Create a new column from two different result sets
How to Create a new column from two different result sets, both the result set uses the different date dimensions.
i got solutions for this is apply filters in column formula it self, based on the requirement.
-
I got a brand new iPod and wanted to put the music files on my old iPod to the new one. In addition to this I would like to know how to sync my new iPod to a different computer from that of the old one. Is it possible for me to accomplish all this with music rescue?
Put everything on one computer and sync to that computer.
Maybe you are looking for
-
Hey, Class: package import flash.display.MovieClip; import flash.events.Event; public class Main extends MovieClip public var enemyA:Array = []; public var birdA:Array = []; public var rowNum:int = 2; priva
-
Call WDA from ABAP via function module
Hi WDA experts, is there any possibility to call a WDA within a ABAP report AND include it in the process. The best would be to call a WDA via a function module - make some inputs on the WDA side - press submit and the function module gives me the da
-
Is laptop's outer body covered under warranty
hi afternoon i have a pavillion p15 077tx it is six months old and have cooling fan replaced after three months now problem start arising , the base is cracking under graphic card area . but i m cleaning vent every weak and no signs of overheatin
-
When Scaling Image, Cannot See All Of Image
I want to allow the user to zoom into an image. Using drawImage(Image img, int x, int y, int width, int height, ImageObserver observer) achieves this, however it displays the scaledImage on background that is of the same size as the original image. i
-
How do I selectively blur one edge of a selection in PS CC? I have merged two photos together using layers (there was a big gap between two subjects) but the bottom edge of the upper layer is a bit obvious. I blurred the whole image and the bottom lo