Naming of Datasources
Hello,
Need some guidance here. I hope to find out why FI-SL DataSource is sometimes named as 3FI_SL_L1 and sometimes 3FI_SL_L1_TT? Or is it due to different naming convention for different releases?
thanks!
adette
Level names can be reused across dimensions. This is common. For example, detail level data is very often shared across levels. When is comes to summary levels, you need decide whether this makes sense. Consider two hierarchies:
Shipping Hierarchy, with levels:
Total Product
Region Shipments
Country Shipments
Warehouse
Item
Product Type hierarchy, with levels:
Total Product
Brand
Group
Item
In the above case, Total Product in each hierarchy should yield the same values because it is the aggregation of all items. So, you might decide that is ok. A different case might not be ok. Consider:
Shipping Hierarchy, with levels:
Total Product
Region Shipments
Country Shipments
Warehouse
Items shipped
Product Type hierarchy, with levels:
Total Product
Brand
Group
Items sold
Since Items Shipped and Items Sold are likely to have different values, the aggregation of each level will yield a different value. In this case, Total Product as the top of each hierarchy doesn't make sense.
A different twist would be (note the display names):
Shipping Hierarchy, with levels:
Total Shipments with 'Total Product' as display name
Region Shipments
Country Shipments
Warehouse
Items shipped
Product Type hierarchy, with levels:
Total Product Types with 'Total Product' as display name
Brand
Group
Items sold
In this case there will be different levels with different values, but the user will see each as 'Total Product'. Only your user community can tell you if this is want they want.
Similar Messages
-
Problem in datasource in embedded oc4j 10.1.3
Hi,
I have created a data source with following details.
Connection Pool Name: jdbc/pool/xyz and enter all details in the connection Factory.
Then am trying to create a connection as follows
javax.naming.InitialContext ic = new javax.naming.InitialContext();
DataSource dd= (javax.sql.DataSource)ic.lookup("jdbc/pool/xyz");
But it is not creating any connection getting following error.
javax.naming.NoInitialContextException:
This is am trying from stand alone program..even tried in the web application by placing (<resource-ref>
<res-ref-name>jdbc/OracleDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>) then also
also same problem...
please help me how to setup in data srouce and access it.
Regards,
PhaniHello,
A connection pool is only the start, once you created a pool you need to create a datasource which uses this pool.
This datasource will have a JNDI name, this is the name you want in your code:
DataSource dd= (javax.sql.DataSource)ic.lookup("jdbc/<yourdatasourcejndiname>");The pool bame, is only a name. Its about the JNDI name for the datasource.
Hope this helps
-Anton -
Invalid Structure Template KNKK of DataSource KNKK_DataSource
Hello,
I am trying to create a Generic DataSource in R3 for BW. My goal is to create a Generic DataSource for table KNKK in R3. I am following some Generic DataSource instructions which appear to be very straightforward. I have named the DataSource "KNKK_DataSource". I follow the steps, but when I try to save the DataSource, I get this error message, "Invalid Structure Template KNKK of DataSource KNKK_DataSource". I can see a field on this page that is called "ExtractStruct", but I am not able to enter anything into this field, and even if I could, I do not know what to enter.
Can anyone provide some guidance?
Thanks!hi Jim,
yes, seems no infoproviders for 0fi_ar_9.
take a look oss note 688859. however, there is ODS 0FIAR_O09 - oss 656687, please check if it's suitable,
i have no access to system now.
hope this helps.
688859-Business Content for 0FI_AR_9 (Credit Management DataSource)
Symptom
There are no InfoProviders shipped by SAP for DataSource 0FI_AR_9
(Credit Management: Control Area Data with Delta Extraction).
You want to understand the reasons for this, and
you are looking for guidance on possible usage scenarios for 0FI_AR_9.
Other terms
KNKK 0FI_AR_9 BWFI3D_GET_FIAR_CM_CAD DTFIAR_9
Reason and Prerequisites
This is a consulting note.
Solution
By standard, SAP does not offer any queries for 0FI_AR_9. The main reason for this is the following one: SAP R/3 ERP allows multiple n:m relationships between Customer, Credit Control Area, and Company Code. (For example, one customer could be allocated to many credit control areas, and one company code could have relations to many credit control areas, or vice versa). Moreover, those foreign key (n:m) relationships vary by customer installation. This makes it difficult to develop business content applicable to a wide variety of installations.
There are multiple ways, however, how the information contained in 0FI_AR_9 could be made available e.g. for A/R reports. Some of those options include:
- MultiProviders.
- Reading of 0FI_AR_9 (from ODS) via update rules.
- Central consolidated ODS layer.
- Inclusion of relevant fields as attributes, e.g. for 0CUSTOMER.
When doing so, make sure to pay particular attention to the following:
- Potential implications of n:m relationships, as pointed out above.
- Implications for delta behavior of 0FI_AR_9.
- Possibly required mapping of calendar month to fiscal period. -
See my code for geting the datasource that give me error
sir i use under blow code for geting datasource
no error in datasource but when use datasource object that give me errr
Connection conn = null ;
// the following should be in a try-catch...
javax.naming.Context ctx = new javax.naming.InitialContext() ;
DataSource ds = (DataSource)ctx.lookup("java:comp/env/jdbc/Travel") ;
conn = ds.getConnection() ;
JasperReport jasperReport = JasperCompileManager.compileReport ("f:\ireport\fahim.jrxml","G",conn); ?(this line give me error )
JasperPrint jasperPrint = JasperFillManager.fillReport(jasperReport,new HashMap(),obj);
please give me idea how i get ireport JasperReport viewer
thank's
aamirI found and easier way to do it and wrote it up here: http://developers.sun.com/jscreator/learning/tutorials/2/reports.html
-
Please see my problem and give me idea
sir i use sun java studio creater with oracle 10g an i flow your code and use this code on button press event
Connection conn = null ;
log("*********** connecting");
try {
javax.naming.Context ctx = new javax.naming.InitialContext() ;
DataSource ds = (DataSource)ctx.lookup(" java:comp/env/jdbc/datasource1" ) ;
conn = ds.getConnection() ;
} catch (Exception ex) {
error(" Error counting rows: " + ex.getMessage() );
log(" Error counting rows: " + ex.getMessage() );
JasperReport jasperReport;
JasperPrint jasperPrint;
log("compiling report");
try {
jasperReport = JasperCompileManager.compileReport("C:/mfa.jasper");
} catch (Exception ex) {
log(" ********* Error compiling report: " + ex.getMessage() );
return null;
but system not give me result
then i see in view server log then i found this error
main error
[#|2007-07-04T10:06:03.159+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042tatus of dynamic reconfiguration event processing:[runtime_error]|#]
[#|2007-07-04T10:06:03.222+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1041ent the event to instance:[ApplicationDeployEvent -- reference-removed WebApplication17]|#]
[#|2007-07-04T10:06:03.284+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1042tatus of dynamic reconfiguration event processing:[success]|#]
[#|2007-07-04T10:06:04.472+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|DPL5109: EJBC - START of EJBC for [WebApplication17]|#]
[#|2007-07-04T10:06:04.487+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|Processing beans ...|#]
[#|2007-07-04T10:06:04.487+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|DPL5110: EJBC - END of EJBC for [WebApplication17]|#]
[#|2007-07-04T10:06:06.378+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|Total Deployment Time: 2891 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 1%
Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2007-07-04T10:06:06.472+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|deployed with moduleid = WebApplication17|#]
[#|2007-07-04T10:06:06.644+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=14;|ADM1041ent the event to instance:[ApplicationDeployEvent -- reference-added WebApplication17]|#]
[#|2007-07-04T10:06:06.706+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=14;|ADM1042tatus of dynamic reconfiguration event processing:[success]|#]
[#|2007-07-04T10:06:06.722+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041ent the event to instance:[ModuleDeployEvent -- deploy web/WebApplication17]|#]
[#|2007-07-04T10:06:06.753+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [WebApplication17] in virtual server [server] at [WebApplication17]|#]
[#|2007-07-04T10:06:06.769+0500|SEVERE|sun-appserver- pe8.2|org.apache.catalina.core.StandardContext|_ThreadID=11;|error stopping
LifecycleException: Manager has not yet been started
full server log file
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:242)
at sun.security.provider.PolicyFile.addPermissions(PolicyFile.java:1403)
at sun.security.provider.PolicyFile.getPermissions(PolicyFile.java:1307)
at sun.security.provider.PolicyFile.getPermissions(PolicyFile.java:1270)
at sun.security.provider.PolicyFile.getPermissions(PolicyFile.java:1211)
at sun.security.provider.PolicyFile.implies(PolicyFile.java:1166)
at com.sun.enterprise.security.provider.PolicyWrapper.implies(PolicyWrapper.java:135)
at java.security.ProtectionDomain.implies(ProtectionDomain.java:195)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:249)
at java.security.AccessController.checkPermission(AccessController.java:427)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
at java.io.File.exists(File.java:700)
at com.sun.enterprise.admin.server.core.channel.RMIClient.checkServerStatus(RMIClient.java:373)
at com.sun.enterprise.admin.server.core.channel.RMIClient.setRestartNeeded(RMIClient.java:354)
at com.sun.enterprise.admin.event.RRPersistenceHelper.setRestartRequired(RRPersistenceHelper.java:98)
at com.sun.enterprise.admin.event.RRPersistenceHelper.setRestartRequiredForServer(RRPersistenceHelper.j ava:75)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:152)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificat ionHelper.java:288)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.j ava:155)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStopEvent(ServerDeploymentTarget.ja va:283)
at com.sun.enterprise.deployment.phasing.StopPhase.runPhase(StopPhase.java:126)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java: 639)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.stop(PEDeploymentService.java:409)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.stop(PEDeploymentService.java:444)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.stop(ApplicationsConfigMBean.java:725)
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:585)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:305)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:360)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:272)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:38)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandle r.java:92)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJm xConnectorServlet.java:69)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnect orServlet.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:189)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:371)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:264)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:281)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83)
|#]
[#|2007-07-04T10:06:03.159+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042tatus of dynamic reconfiguration event processing:[runtime_error]|#]
[#|2007-07-04T10:06:03.222+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1041ent the event to instance:[ApplicationDeployEvent -- reference-removed WebApplication17]|#]
[#|2007-07-04T10:06:03.284+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1042tatus of dynamic reconfiguration event processing:[success]|#]
[#|2007-07-04T10:06:04.472+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|DPL5109: EJBC - START of EJBC for [WebApplication17]|#]
[#|2007-07-04T10:06:04.487+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|Processing beans ...|#]
[#|2007-07-04T10:06:04.487+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|DPL5110: EJBC - END of EJBC for [WebApplication17]|#]
[#|2007-07-04T10:06:06.378+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|Total Deployment Time: 2891 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 1%
Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2007-07-04T10:06:06.472+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=13;|deployed with moduleid = WebApplication17|#]
[#|2007-07-04T10:06:06.644+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=14;|ADM1041ent the event to instance:[ApplicationDeployEvent -- reference-added WebApplication17]|#]
[#|2007-07-04T10:06:06.706+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=14;|ADM1042tatus of dynamic reconfiguration event processing:[success]|#]
[#|2007-07-04T10:06:06.722+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041ent the event to instance:[ModuleDeployEvent -- deploy web/WebApplication17]|#]
[#|2007-07-04T10:06:06.753+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [WebApplication17] in virtual server [server] at [WebApplication17]|#]
[#|2007-07-04T10:06:06.769+0500|SEVERE|sun-appserver- pe8.2|org.apache.catalina.core.StandardContext|_ThreadID=11;|error stopping
LifecycleException: Manager has not yet been started
at org.apache.catalina.session.StandardManager.stop(StandardManager.java:704)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4675)
at org.apache.catalina.core.StandardContext.preDeregister(StandardContext.java:5643)
at org.apache.commons.modeler.BaseModelMBean.preDeregister(BaseModelMBean.java:1418)
at com.sun.jmx.mbeanserver.BaseMetaDataImpl.preDeregisterInvoker(BaseMetaDataImpl.java:122)
at com.sun.jmx.mbeanserver.MetaDataImpl.preDeregisterInvoker(MetaDataImpl.java:251)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor. java:377)
at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:527)
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:585)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.unregisterMBean(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.unregisterMBean(SunoneInterceptor.java: 324)
at org.apache.commons.modeler.Registry.unregisterComponent(Registry.java:643)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4228)
at com.sun.enterprise.web.WebModule.start(WebModule.java:241)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:827)
at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:125)
at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:147)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:809)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:646)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1331)
at com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1040)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.j ava:160)
at com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.j ava:246)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulti caster.java:918)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.j ava:905)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:427)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:139)
at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificat ionHelper.java:288)
at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.j ava:155)
at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.j ava:258)
at com.sun.enterprise.deployment.phasing.StartPhase.runPhase(StartPhase.java:87)
at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:71)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java: 639)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:361)
at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:396)
at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:702)
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:585)
at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:305)
at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:360)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:54)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:272)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:38)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandle r.java:92)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJm xConnectorServlet.java:69)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnect orServlet.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:767)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:189)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doProcess(ProcessorTask.java:604)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:475)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:371)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:264)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:281)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:83)
|#]
[#|2007-07-04T10:06:07.987+0500|WARNING|sun-appserver- pe8.2|org.apache.commons.digester.Digester|_ThreadID=11;|[ComponentRule]{faces-config/component} Merge(com.sun.rave.web.ui.Time)|#]
[#|2007-07-04T10:06:08.019+0500|WARNING|sun-appserver- pe8.2|org.apache.commons.digester.Digester|_ThreadID=11;|[ConverterRule]{faces-config/converter} Merge(null,java.math.BigDecimal)|#]
[#|2007-07-04T10:06:08.019+0500|WARNING|sun-appserver- pe8.2|org.apache.commons.digester.Digester|_ThreadID=11;|[ConverterRule]{faces-config/converter} Merge(null,java.math.BigInteger)|#]
[#|2007-07-04T10:06:09.222+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042tatus of dynamic reconfiguration event processing:[success]|#]
[#|2007-07-04T10:06:47.427+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.container.web|_ThreadID=15;|WebModule[/WebApplication17]*********** connecting|#]
[#|2007-07-04T10:06:47.442+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.container.web|_ThreadID=15;|WebModule[/WebApplication17] Error counting rows: null|#]
[#|2007-07-04T10:06:47.442+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.container.web|_ThreadID=15;|WebModule[/WebApplication17]compiling report|#]
[#|2007-07-04T10:06:48.114+0500|INFO|sun-appserver- pe8.2|javax.enterprise.system.container.web|_ThreadID=15;|WebModule[/WebApplication17] ********* Error compiling report: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.|#]
sir what means of this error
Status of dynamic reconfiguration event processing:[runtime_error]
Total Deployment Time: 2891 msec, Total EJB Compiler Module Time: 31 msec, Portion spent EJB Compiling: 1%
Breakdown of EJBC Module Time: Total Time for EJBC: 31 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
please give me idea how i create pdf fileAamir, you asked this same question in the thread below, and I provided an answer.
how use F2-key -
I want to bring the sale order table to BI. What are the activities required to be done in r/3 as well as in bi.
Hi.........
It depends which fields u want to extract..............If there are any Standard Datasource then u can use it...............otherwise u can go for Generic datasource.............since SD belongs to LO Extraction...........U hav to follow the below Steps........
The following section describes the steps that are necessary to configure a data
flow for logistics data extraction.
1. Transfer the logistics DataSource for transaction data from Business Content
With the transfer of the DataSource, the associated extraction structure is
also delivered, but the extraction structure is based on LIS communication
structures. Furthermore, based on the extraction structure for the DataSource,
a restructuring table that is used for the initialization and full update to BI
is generated.
Naming convention:
DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
optional
Examples:
2LIS_11_VAITM: 11 = SD Sales VA = sales order, delivery schedule ITM
(u2192 ITEM) = document position
Extraction structure MC<Application><Event/group of
events>0<Suffix>; where MC is derived from the associated communication
structures and <Suffix> is optional
Examples:
MC11VA0ITM: Extraction structure for the DataSource 2LIS_11_VAITM
MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
where M_ indicates the group for the events MA (order), MD (delivery
schedule), ME (contact) and MF (request).
Restructuring table (= setup table) <Extraction structure>SETUP
Example:
Extraction structure: MC11VA0IT u21D2 Restructuring table:
MC11VA0ITSETUP
2. Maintain extraction structure (transaction LBWE)
This means that fields can be added to the extraction structure that is
delivered with the DataSource without modifying anything. On the one
hand, fields from the LIS communication structures that are assigned to the
extraction structure can be used, that means standard fields that SAP has
not selected, and on the other hand, customer fields that were attached to
the LIS communication structures with the append technique can be used.
After the extraction structure is created, it is generated automatically and the
associated restructuring table is adapted.
3. Maintain/generate DataSource
In the DataSource maintenance, you can assign the properties Selection,
Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
the fields of the extraction structure. After enhancing the extraction structure,
the DataSource always has to be generated again!
4. Replicate and activate DataSource in SAP BI (=metadata upload)
5. Maintain Data Target (Data Store Object, InfoCube)
6. Maintain Transformations between DataSource and Data Target
7. Create a Data Transfer Process
the Data Transfer Process will be used later to update the data from the PSA
table into the Data Target.
8. Set extraction structure for updating to active (transaction LBWE)
In this way, data can be written to the restructuring table or the delta queue
from then on using the extraction structure (see following steps).
9. Filling the restructuring table/restructure (OLI*BW)
During this process, no documents should be created or changed in the
system! In some applications, it is possible to fill the restructuring table
beforehand in simulation mode. These results are listed in a log (transaction
LBWF). Before filling the restructuring table, you must ensure that the
content of the tables is deleted (transaction LBWG), preventing the table
from being filled multiple times. Once the restructuring tables are filled,
document editing can resume as long as Unserialized V3 Update or Queued
Delta is selected in the next step. Be absolutely sure that no V3 collection
run is started until the next successful posting of an InfoPackage for delta
initialization (see step 11).
10. Select update method
Unserialized V3 update
Queued delta
Direct delta
11. Create an InfoPackage for the DataSource and schedule the Delta
Initialization in the Scheduler
This updates the BI-relevant data from the restructuring table to the
PSA table. Since the restructuring table is no longer needed after delta
initialization, the content can be deleted (transaction LBWG).
Use the Data Transfer Process created in step 7 to update the data from
the PSA table into the Data Targets. After successful delta initialization,
document editing can resume, as long as the direct delta update method
was selected in step 13. This means that BI-relevant delta data is written
directly to the delta queue.
Note:
If the DataSource supports early-delta initialization, the delta data can
be written to the delta queue during delta initialization. This feature is
controlled with an indicator in the Scheduler.
12. Start V3 collection run (transaction LBWE)
This step is only necessary when the update method unserialized V3 Update
or Queued Delta was selected in step 10. By starting a corresponding job for
an application, the BI-relevant delta data is read from the update tables or
extraction queue and written to the delta queue.
13. Create an InfoPackage for the DataSource in BI and schedule the Delta
Update in the Scheduler
The BI-relevant delta data from the delta queue for the DataSource is updated
to the PSA table. Use the Data Transfer Process created in step 7 to update
the data from the PSA table into the Data Targets.
And if u want to create a Generic datasource............use tcode RSO2.................if u r Extracting data from a single table...........then create the datasource based on the condition table.................if u r extracting from two or three tables go for View...............and if u r extracting data from many tables...........its better to go for function module...........If u don't know how to create generic datasource.........U can search in Forum.............u will get good documents..........
Hope this helps.........
Regards,
Debjani............... -
I have oc4j (9,0.4.0.1) and oracle database 9i. I 'm trying to call to a stored procedure and the next error appear
06/06/27 09:40:33 Oracle Application Server Containers for J2EE 10g (9.0.4.0.1)
initialized
06/06/27 09:40:59 The driver is 10.1.0.1.1
06/06/27 09:40:59 java.sql.SQLException: Bigger type length than maximum
06/06/27 09:40:59 at oracle.jdbc.driver.DatabaseError.throwSqlException(Da
tabaseError.java:137)
06/06/27 09:40:59 at oracle.jdbc.driver.DatabaseError.throwSqlException(Da
tabaseError.java:174)
06/06/27 09:40:59 at oracle.jdbc.driver.DatabaseError.check_error(Database
Error.java:897)
I write a jsp to test, I know the code is not the best
<%@ page import="java.sql.CallableStatement" %>
<%@ page import="java.sql.Connection" %>
<%@ page import="java.sql.DriverManager" %>
<%@ page import="java.sql.ResultSet" %>
<%@ page import="java.sql.ResultSetMetaData" %>
<%@ page import="java.sql.SQLException" %>
<%@ page import="java.sql.Statement" %>
<%@ page import="java.util.Hashtable" %>
<%@ page import="java.util.Vector" %>
<%@ page import="javax.naming.InitialContext" %>
<%@ page import="javax.sql.DataSource" %>
<%@ page import="oracle.jdbc.driver.OracleTypes" %>
<%
CallableStatement call = null;
Connection _conn = null;
Hashtable[] ahtListResults = null;
ResultSet resul = null;
String mes="2";
String anio="2006";
String suministrador = "ARL";
String aeropuerto = "AUH";
String[] asParameter = {mes, anio,suministrador, aeropuerto};
try {
InitialContext ctx = new javax.naming.InitialContext();
DataSource ds = (DataSource) ctx.lookup("jdbc/gescom");
_conn = ds.getConnection();
System.out.println("The driver is " + _conn.getMetaData().getDriverVersion() );
// Prepare a PL/SQL call
call = _conn.prepareCall("{ ? = call inf_cargas.porFlotaMesYSuministrador (?,?,?,?)}");
call.registerOutParameter(1, OracleTypes.CURSOR);
for (int i=0; i<asParameter.length; i++) {
call.setString(i + 2, asParameter);
call.execute();
//resul = (ResultSet) call.getObject(1);
call.close();
_conn.close();
System.out.println("correcto");
} catch (Throwable e) {
call.close();
_conn.close();
call=null;
_conn = null;
e.printStackTrace();
I've checked this jsp in a Tomcat and runs ok. The difference is message of the driver is
The driver is 9.2.0.5.0
I think the problem is the driver and I'm using ojdb14.jar in Tomcat but in Oc4j I don't know how to change it.
Any idea to solve the problem????
Thanks in advancepueblopaleta,
You cannot change the JDBC driver in OC4J stand-alone 9.0.4.0.1 -- but you can in OC4J stand-alone 10.1.3.0.0
Good Luck,
Avi. -
Help Connecting A Stateless Session Bean To MySQL Database
Hi, I'm trying to connect a simple stateless session bean that has been
deployed using the admin console to a MySQL database that has been
set up and pinged using the JDBC Resources/Connection Pools part of the
admin console.
When I attempt to connect to the database using the session bean I get the
following error message:
Exception in thread "main" java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: ; nested exception is:
java.sql.SQLException: No database selected
at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:161)
at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:142)
at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(Unknown Source)
at DBDynamicStub.testDatabase(_DB_DynamicStub.java)
at DBClient.main(DBClient.java:9)
Caused by: java.rmi.RemoteException: ; nested exception is:
java.sql.SQLException: No database selected
at com.sun.ejb.containers.InvocationHandlerUtil.throwRemoteException(InvocationHandlerUtil.java:96)
at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:141)
at $Proxy26.testDatabase(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:585)
at com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:123)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:648)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:192)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1709)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1569)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:951)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:181)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:721)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:469)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1258)
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:409)
Caused by: java.sql.SQLException: No database selected
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2851)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1531)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1622)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2379)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2306)
at com.mysql.jdbc.Statement.executeQuery(Statement.java:1192)
at DBBean.testDatabase(DBBean.java:45)
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:585)
at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:950)
at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:158)
Obviously this means that the bean can't connect to the database but I am
unsure why this is. When I set up the database using the admin console
I set the the jndi name to jdbc/test and I've tried using the following look up
code to find the database that is referenced by the JNDI name:
Context context = new javax.naming.InitialContext();
DataSource ds = (DataSource) context.lookup("jdbc/test");
and also
Context context = new javax.naming.InitialContext();
DataSource ds = (DataSource)context.lookup("java:comp/env/jdbc/test");
Neither of these methods work.
When I look at the JNDI Tree Browsing window which is available from the
admin console there is no mention of the database at all, there are four
items in the three, they are:
UserTransaction
->jdbc
->ejb
DBBean
Do I need to add a JNDI reference somewhere in order for the bean to locate
the database? I thought that when I created the database in the admin
console and specified a JNDI name this would be all that's required in order
for beans to locate the database, obviously not.
If anyone can offer any advice at all I would be very very grateful.
Ianstmt.execute("use YOUR_DATABASE_NAME");
// then your db queries.This approach works for me.
It also works to specify the database in the query like this:
InitialContext initCtx = new InitialContext();
Context envCtx = (Context) initCtx.lookup("java:comp/env");
DataSource ds = (DataSource) envCtx.lookup("jdbc/myDB");
Connection conn = ds.getConnection();
try {
Statement statement = conn.createStatement();
ResultSet rs = statement.executeQuery("select * from myDB.news");
...As you can see I added myDB. to the query.
But why is this necessary?
If I use DriverManager instead, this is NOT necessary. Like this:
Connection connection = null;
try {
Class.forName("com.mysql.jdbc.Driver");
connection = DriverManager.getConnection("jdbc:mysql://localhost:3306/myDB", "username", "password");
Statement statement = connection.createStatement();
ResultSet rs = statement.executeQuery("select * from news");
...Why do I not have to run the query statement.execute("use YOUR_DATABASE_NAME"); or specify the database name in the query statement.executeQuery("select * from myDB.news"); when I use DriverManager to obtain a Connection when I have to do that when using a DataSource?
It don't seem very efficient to have to run the extra query ( use db-name ) before I run any other query in my application. -
My code not give error nut not give pdf report output
hi master
sir see my code not give error nut not give pdf report output
String reportSource = "./WEB-INF/reports/mfa.jasper";
String reportDest = "./reports/mfa1.html";
Connection conn = null ;
Statement msqlStatement = null ;
ResultSet mrs = null ;
Connection mconn = null ;
ExternalContext econtext = getExternalContext();
InputStream stream = econtext.getResourceAsStream(reportSource);
if (stream == null) {
throw new IllegalArgumentException("Unknown report name '" + reportSource
+ "' requested");
try {
String mfat = ac_categoryDataProvider.getCachedRowSet().getDataSourceName();
javax.naming.Context mctx = new javax.naming.InitialContext() ;
DataSource mds = (DataSource)mctx.lookup(mfat);
Connection mcon= mds.getConnection();
mcon.setAutoCommit(false) ;
JasperPrint jasperPrint = null;
//getSessionBean1().getTripRowSet(),
//getSessionBean1().getAc_categoryRowSet(), mfat getSessionBean1().getAc_categoryRowSet()
jasperPrint = JasperFillManager.fillReport(stream, null,mcon);
JRExporter exporter = null;
HttpServletResponse response = (HttpServletResponse)econtext.getResponse();
FacesContext fcontext = FacesContext.getCurrentInstance();
exporter = new JRPdfExporter();
exporter.setParameter(JRExporterParameter.JASPER_PRINT, jasperPrint);
exporter.setParameter(JRExporterParameter.OUTPUT_STREAM,
response.getOutputStream());
exporter.exportReport();
fcontext.responseComplete();
} catch (Exception ex) {
log(" Error Description" , ex);
error("Error counting rows: " + ex.getMessage() );
error("Error counting rows: " + ex );
please give me idea
thank's
aamirThanks Sven.
The query works but the other way. The output is for all the targets, not for the respective target which we select from :p1_target.
select target_name,target_type, column_label,
warning_threshold,critical_threshold,occurrence_count
from sysman.MGMT$TARGET_METRIC_SETTINGS@crmodem
where target_name in (select MEMBER_TARGET_NAME from MGMT$TARGET_FLAT_MEMBERS@crmodem
where upper(AGGREGATE_TARGET_NAME) like '%X' || :P1_TARGET || '%')
Thanks again. -
<Moderator Message: Please search before posting. You can find a lot of information related to this issue searching the forums, the blogs and of course the online help.>
Hi friends,
I want do purchase extraction using LO cockpit extraction before doing this i want to know about R/3 steps & setting if any in R/3 system.
I know about LO extraction steps apart from that if we have any steps in R/3 setting kindly forward to me.
thanks
Siri
Edited by: Siegfried Szameitat on Jan 26, 2009 12:31 PMHi Siri........
U want to extract Logistic data........
The following section describes the steps that are necessary to configure a data
flow for logistics data extraction.
1. Transfer the logistics DataSource for transaction data from Business Content
With the transfer of the DataSource, the associated extraction structure is
also delivered, but the extraction structure is based on LIS communication
structures. Furthermore, based on the extraction structure for the DataSource,
a restructuring table that is used for the initialization and full update to BI
is generated.
Naming convention:
DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
optional
Examples:
2LIS_11_VAITM: 11 = SD Sales VA = sales order, delivery schedule ITM
(u2192 ITEM) = document position
2LIS_02_HDR: 02 = MM purchasing HDR (u2192 HEADER ) = Document
header
Extraction structure MC<Application><Event/group of
events>0<Suffix>; where MC is derived from the associated communication
structures and <Suffix> is optional
Examples:
MC11VA0ITM: Extraction structure for the DataSource 2LIS_11_VAITM
MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
where M_ indicates the group for the events MA (order), MD (delivery
schedule), ME (contact) and MF (request).
Restructuring table (= setup table) <Extraction structure>SETUP
Example:
Extraction structure: MC11VA0IT u21D2 Restructuring table:
MC11VA0ITSETUP
2. Maintain extraction structure (transaction LBWE)
This means that fields can be added to the extraction structure that is
delivered with the DataSource without modifying anything. On the one
hand, fields from the LIS communication structures that are assigned to the
extraction structure can be used, that means standard fields that SAP has
not selected, and on the other hand, customer fields that were attached to
the LIS communication structures with the append technique can be used.
After the extraction structure is created, it is generated automatically and the
associated restructuring table is adapted.
3. Maintain/generate DataSource
In the DataSource maintenance, you can assign the properties Selection,
Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
the fields of the extraction structure. After enhancing the extraction structure,
the DataSource always has to be generated again!
4. Replicate and activate DataSource in SAP BI (=metadata upload)
5. Maintain Data Target (Data Store Object, InfoCube)
6. Maintain Transformations between DataSource and Data Target
7. Create a Data Transfer Process
the Data Transfer Process will be used later to update the data from the PSA
table into the Data Target.
8. Set extraction structure for updating to active (transaction LBWE)
In this way, data can be written to the restructuring table or the delta queue
from then on using the extraction structure (see following steps).
9. Filling the restructuring table/restructure (OLI*BW)
During this process, no documents should be created or changed in the
system! In some applications, it is possible to fill the restructuring table
beforehand in simulation mode. These results are listed in a log (transaction
LBWF). Before filling the restructuring table, you must ensure that the
content of the tables is deleted (transaction LBWG), preventing the table
from being filled multiple times. Once the restructuring tables are filled,
document editing can resume as long as Unserialized V3 Update or Queued
Delta is selected in the next step. Be absolutely sure that no V3 collection
run is started until the next successful posting of an InfoPackage for delta
initialization (see step 11).
10. Select update method
Unserialized V3 update
Queued delta
Direct delta
11. Create an InfoPackage for the DataSource and schedule the Delta
Initialization in the Scheduler
This updates the BI-relevant data from the restructuring table to the
PSA table. Since the restructuring table is no longer needed after delta
initialization, the content can be deleted (transaction LBWG).
Use the Data Transfer Process created in step 7 to update the data from
the PSA table into the Data Targets. After successful delta initialization,
document editing can resume, as long as the direct delta update method
was selected in step 13. This means that BI-relevant delta data is written
directly to the delta queue.
Note:
If the DataSource supports early-delta initialization, the delta data can
be written to the delta queue during delta initialization. This feature is
controlled with an indicator in the Scheduler.
12. Start V3 collection run (transaction LBWE)
This step is only necessary when the update method unserialized V3 Update
or Queued Delta was selected in step 10. By starting a corresponding job for
an application, the BI-relevant delta data is read from the update tables or
extraction queue and written to the delta queue.
13. Create an InfoPackage for the DataSource in BI and schedule the Delta
Update in the Scheduler
The BI-relevant delta data from the delta queue for the DataSource is updated
to the PSA table. Use the Data Transfer Process created in step 7 to update
the data from the PSA table into the Data Targets.
Hope this helps.......
Regards,
Debjani...... -
Purchasing Data Not Tying Up between BW and R/3.
Hi,
As a part of our project, we reloaded the all the data related to Purchasing through the extractors
2LIS_02_SCL
2LIS_02_ITM
2LIS_02_HDR
As these were corrupted due to patch application.
We took all the possible care during reloading of all the data from R/3 like locking the user from making any transactions, Deleting the setup tables etc in a step by step process etc.
But however, after the extraction the data is not tying up between R/3 and BW Purchasing ODS.
Is there some thing wrong did we do or How can we get that missing records into BW again.
Appreciate your help.
Thanks.Hi......
Did u fill the set up table with any selection...........?.....Previously no of records picked was larger than this time........right?..........Hav u checked RSA3 in the source system..........is it showing correct no of records........? if yes............then check the selection tab of the IP..whether u hav maintained any selection there.........
If no..........then......first check the selection in the set up table..............then the function module....which is extracting the data..........u will get the function module in RSA2.........there just double click on the Extractor.........u will get the function module name........
Anyways.........did u know which records r missed.........then just fill the set up table for those values only.........then do full load......
Anyways,............I think u know the steps in LO Extraction...........still for ur reference..........
1. Transfer the logistics DataSource for transaction data from Business Content
With the transfer of the DataSource, the associated extraction structure is
also delivered, but the extraction structure is based on LIS communication
structures. Furthermore, based on the extraction structure for the DataSource,
a restructuring table that is used for the initialization and full update to BI
is generated.
Naming convention:
DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
optional
Examples:
2LIS_02_HDR: 02 = MM purchasing HDR (u2192 HEADER ) = Document
header...
Extraction structure MC<Application><Event/group of
events>0<Suffix>; where MC is derived from the associated communication
structures and <Suffix> is optional
Examples:
MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
where M_ indicates the group for the events MA (order), MD (delivery
schedule), ME (contact) and MF (request).
Restructuring table (= setup table) <Extraction structure>SETUP
Example:
Extraction structure: MC11VA0IT u21D2 Restructuring table:
MC11VA0ITSETUP
2. Maintain extraction structure (transaction LBWE)
This means that fields can be added to the extraction structure that is
delivered with the DataSource without modifying anything. On the one
hand, fields from the LIS communication structures that are assigned to the
extraction structure can be used, that means standard fields that SAP has
not selected, and on the other hand, customer fields that were attached to
the LIS communication structures with the append technique can be used.
After the extraction structure is created, it is generated automatically and the
associated restructuring table is adapted.
3. Maintain/generate DataSource
In the DataSource maintenance, you can assign the properties Selection,
Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
the fields of the extraction structure. After enhancing the extraction structure,
the DataSource always has to be generated again!
4. Replicate and activate DataSource in SAP BI (=metadata upload)
5. Maintain Data Target (Data Store Object, InfoCube)
6. Maintain Transformations between DataSource and Data Target
7. Create a Data Transfer Process
the Data Transfer Process will be used later to update the data from the PSA
table into the Data Target.
8. Set extraction structure for updating to active (transaction LBWE)
In this way, data can be written to the restructuring table or the delta queue
from then on using the extraction structure (see following steps).
9. Filling the restructuring table/restructure (OLI*BW)
During this process, no documents should be created or changed in the
system! In some applications, it is possible to fill the restructuring table
beforehand in simulation mode. These results are listed in a log (transaction
LBWF). Before filling the restructuring table, you must ensure that the
content of the tables is deleted (transaction LBWG), preventing the table
from being filled multiple times. Once the restructuring tables are filled,
document editing can resume as long as Unserialized V3 Update or Queued
Delta is selected in the next step. Be absolutely sure that no V3 collection
run is started until the next successful posting of an InfoPackage for delta
initialization (see step 11).
10. Select update method
Unserialized V3 update
Queued delta
Direct delta
11. Create an InfoPackage for the DataSource and schedule the Delta
Initialization in the Scheduler
This updates the BI-relevant data from the restructuring table to the
PSA table. Since the restructuring table is no longer needed after delta
initialization, the content can be deleted (transaction LBWG).
Use the Data Transfer Process created in step 7 to update the data from
the PSA table into the Data Targets. After successful delta initialization,
document editing can resume, as long as the direct delta update method
was selected in step 13. This means that BI-relevant delta data is written
directly to the delta queue.
Note:
If the DataSource supports early-delta initialization, the delta data can
be written to the delta queue during delta initialization. This feature is
controlled with an indicator in the Scheduler.
12. Start V3 collection run (transaction LBWE)
This step is only necessary when the update method unserialized V3 Update
or Queued Delta was selected in step 10. By starting a corresponding job for
an application, the BI-relevant delta data is read from the update tables or
extraction queue and written to the delta queue.
13. Create an InfoPackage for the DataSource in BI and schedule the Delta
Update in the Scheduler
The BI-relevant delta data from the delta queue for the DataSource is updated
to the PSA table. Use the Data Transfer Process created in step 7 to update
the data from the PSA table into the Data Targets.
Hope this helps.......
Regards,
Debjani... -
Startup error in Java Web Tomcat 7 Container in PersistenceDataSourceFactory
Hi,
I tried to deploy a webapp in the Java Web Tomcat 7 container in my trial account. In my web.xml I have the following resource-ref:
<resource-ref>
<res-ref-name>jdbc/ccocs</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
</resource-ref>
When I start the container, I get the following error in the log: #+00#ERROR#com.sap.cloud.runtime.kotyo.persistence.client.PersistenceDataSourceFactory##anonymous#localhost-startStop-1##dXXXXXXtrial#cs2#web##An exception occurred during rest communication with local config service: java.io.FileNotFoundException: http://localhost:20002/config/v1/services/persistence/jdbc/ccocs
What could be the reason for that error?
Regards
MarcoSorry my fault. After some try and error I realised I named the DataSource in the binding "ccocs", but it has to be "jdbc/ccocs".
-
Implementing Database codes FAIL /error in parsing data into jsp page
Hi there,
I have this problem trying to build a portal application. I am using the JSPDynPage, jsp page and a bean to build a page.
I have this problem parsing data from JSPDynPage to the beans and to the jsp page.
I tested out the connection between the beans and the jsp page. There is no error parsing information from the beans to the jsp page.
So i tried to test out the codes for the database from the beans.
Will this work? Because it does not display the results i want.
I need an Solution asap to find out wad is wrong also also the correct codes to the database.
public String db(){
try {
InitialContext iC = new InitialContext();
DataSource dataSource = (DataSource)iC.lookup("java:env/jdbc/mySQL");
java.sql.Connection connection = dataSource.getConnection();
PreparedStatement st = connection.prepareStatement("SELECT name FROM test WHERE id='123'");
ResultSet resultSet = st.executeQuery();
while (resultSet.next()){
name = resultSet.getString("name");
name = name.toString();
connection.close();
return name;
} catch(Exception n){
e = "Exception";
return e;
This is the method i put in the beans to test out the database connection.
Thanks Loads
QuatreHi there,
Thanks for the reply, i thought that no one is going to reply me anymore. Thanks loads.
Bean Class name: Bean1
Bean Packeage name: Beans1
Bean id : myBean1
Jsp Codes
<%@ taglib uri="tagLib" prefix="hbj" %>
<jsp:useBean id="myBean1" scope="application" class="Beans1.Bean1" />
<hbj:content id="myContext" >
<hbj:page title="PageTitle">
<hbj:form id="myFormId" >
<hbj:textView id = "ll" text="lalalalalalalalalasasa" />
<%--
<hbj:textView id = "l">
<% l.setName(myBean1.getName());%>
</hbj:textView>
--%>
<hbj:textView
id="appraisal_yr_label"
text="Apprasial Year:">
</hbj:textView>
<hbj:textView id = "la" >
<% la.setText(myBean1.getName());%>
</hbj:textView>
</hbj:form>
</hbj:page>
</hbj:content>
Beans1.java
package Beans1;
import java.io.Serializable;
public class Bean1 implements Serializable{
private String name = new String();
private String e = new String();
private String year = new String();
public void setName(String name){
this.name = name;
public String getName(){
return name;
JSPDynPage
import Beans1.Bean1;
import com.sapportals.htmlb.*;
import com.sapportals.htmlb.enum.*;
import com.sapportals.htmlb.event.*;
import com.sapportals.htmlb.page.*;
import com.sapportals.portal.htmlb.page.*;
import com.sapportals.portal.prt.component.*;
public class testDBv5 extends PageProcessorComponent {
import Beans1.Bean1;
import com.sapportals.htmlb.*;
import com.sapportals.htmlb.enum.*;
import com.sapportals.htmlb.event.*;
import com.sapportals.htmlb.page.*;
import com.sapportals.portal.htmlb.page.*;
import com.sapportals.portal.prt.component.*;
public class testDBv5 extends PageProcessorComponent {
public DynPage getPage(){
return new testDBv5DynPage();
public static class testDBv5DynPage extends JSPDynPage{
private Bean1 myBean1= null;
private String name = new String();
public void doInitialization(){
try{
IntitialContext context = new javax.naming.InitialContext();
DataSource dataSource = (DataSource)context.lookup("java:env/jdbc/appDB");
Connection connection = dataSource.getConnection();
Statement stmt = connection.createStatement();
ResultSet rs = stmt.executeQuery("Select AppraisalYear From tblAppraisal Where AppraisalYear='2007'");
while(rs.next()){
year = rs.getString("AppraisalYear");
rs.close();
stmt.close();
connection.close();
return year;
}catch (Exception n){
n.printStackTrace();
IPortalComponentProfile profile = ((IPortalComponentRequest)getRequest()).getComponentContext().getProfile();
Object o = profile.getValue("myBean1");
if(o==null || !(o instanceof Bean1)){
myBean1 = new Bean1();
profile.putValue("myBean1",myBean1);
} else {
myBean1 = (Bean1) o;
Object value = request.getSession().getValue("myBeans1");
if (value==null || (value instanceof Bean1)){
myBean1 = new Bean1();
request.getSession().putValue("myBean1", Object value);
DataBase cn = new DataBase();
name = cn.dataBaseConnection();
myBean1.setName(name);
//name = "gir";
//myBean1.setName(name);
// IPortalComponentRequest request = (IPortalComponentRequest) this.getRequest();
//IPortalComponentContext myContext = request.getComponentContext();
//Bean1 myNameContainer = (Bean1) myContext.getValue("myBean1");
//myNameContainer.setName(name);
// fill your bean with data here...
public void doProcessAfterInput() throws PageException {
public void doProcessBeforeOutput() throws PageException {
this.setJspName("testDBv5.jsp");
//testing purpose
public static void main (String[] arg){
testDBv5DynPage ef = new testDBv5DynPage();
ef.doInitialization();
Thanks Loads
Quatre -
Websphere 6 connection pooling
Hi,
Just a quick one (I hope).
I'm setting up an application to run on websphere. To get the connection pooling to work, is it as simple as setting up the connection in the server config as a db2ConnectionPoolDataSource. eg dataSource provider name = prov1, type = db2ConnectionPoolDataSource. DataSource name = ds1, jndi name=jdbc/ds1.
Then whenever I need to obtain a connection, I simply reference this jndi name and websphere takes care of the pooling. e.g.
javax.naming.InitialContext ctx = new javax.naming.InitialContext();
dataSource = (javax.sql.DataSource) ctx.lookup("jdbc/ds1);
connection = dataSource.getConnection(userName,password);
Am I on the right track wih this or have I missed the point (again)?
Thanks
Message was edited by:
spidermonkey
spelling errorI guess you have to make an entry into your app's web.xml. I made an entry and it worked...
<resource-ref>
<description>Oracle XE Datasource connection</description>
<res-ref-name>jdbc/oraclexe</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
and also the ojdbc14.jar should be in tomcat's lib and not your app's lib.
These were the mistakes i made , hope this helps -
HI,
what all are the disadvantages of generic over LO.\
Regards,
Sunny.Sunny
Generic extractor :
with which you can extract more data from the SAP source system and transfer it into BW. Only when you call up the generic extractor by naming the DataSource does it know which data is to be extracted, and from which tables it should read it from and in which structure. This is how it fills different extract structures and DataSources.
LO Extractor: LO extraction is used for Logistics applications. Check this link for more details
Hope this helps
Thanks
Sat
http://help.sap.com/saphelp_nw04/helpdata/en/28/4c553c42360a40e10000000a114084/frameset.htm
Maybe you are looking for
-
Lecture Poster Large/Not printing correctly
I selected Lecture Poster Large. I replaced all the photos using Aperture. The large photo at the bottom was also replaced by dragging in a photo from Aperture. I was very happy with the result. The photo preview looks exactly like the project. But w
-
Hi there I bought an iPhone 4S unlock. 1st time after I putted the SIM card in, it works for 10minute and then rejected. It showed: Invalid SIM card or :No SIM cared instatalled". How do I fix it? Thanks Chi
-
Hi gurus, does anybody know how to use KPRO infrastructure with SAP EP 6.0? To be more explicit I would like to know how to leverage the cache server delivered with KPRO and use caching infrastructure to retrieve documents through KM from sites with
-
SSP PO & Confirmation document no.
HI Is there anyway to pull the SSP PO & confirmation no created in a specific period or year. Please let me know if any table or report is there to pull the same. Regards Pratap J
-
How to Install Drivers for Win XP without the CD?
I have a 15-inch Mac Book Pro older version. I have installed the Windows XP, but my superdriver is with some kind of problem. When I insert the CD from Mac OS X, as instructed on the Boot Camp Manual, the CD is not recognized. So it is ejected after