Datasource 9ARE snp issue

HI,
i have a data source in my apo system based on aggregation level 9ARE which pulls resource level data and total capacity in hours
it was extracting daily 1 million data everyday based on selections current cal day to 31/12/9999 and now suddenly it is only pulling 78000 records and looks like it is pulling data for resource relate to one particular plant only...
even have tried extraction in rsa3 it's same. and the strange thing is that if we give resource name in rsa3 which is not pulled now to bw... It show data for that resource even though it is not pulled in bw as well as rsa3 in apo also when we just check without any resource name .
no changes have happened in apo ...can someone give idea as to where the issue can be ?.
which tables I can look in apo to see where the issue is.
thanks
nilesh

Hi Nilesh,
Please check the Infopackage selections. Probably you could have an incorrect selection.
Regards
JB

Similar Messages

  • WSAD 5, xerces, datasource and classcastexception issue

    I am running into an issue trying to run my code once I upgraded from WDAD 5.0 to WSAD 5.01. I am getting the error below when I try and connect to my DataSource. This all was working fine before I upgraded. It looks like an issue with the xerces.jar file because if I take out the JAXP stuff in the xerces.jar file I work fine. But I need the JAXP stuff because I am doing messaging. Anyone have any ideas?
    [5/22/03 7:02:59:848 CDT] 2ec4c80 SystemOut O 2003.05.22 07:02:59.848--ServerSession(426724481)--Thread[asyncDelivery0,5,main]--Connection(47762586)--TopLink, version:TopLink - 9.0.3 (Build 423)
    2003.05.22 07:02:59.848--ServerSession(426724481)--Thread[asyncDelivery0,5,main]--Connection(47762586)--connecting(DatabaseLogin(
         platform => DB2Platform
         user name => "ou79ecm"
         datasource name => "jdbc/DB239DataSource"
    [5/22/03 7:03:00:118 CDT] 2ec4c80 ConnectionFac I J2CA0122I: Resource reference jdbc/DB239DataSource could not be located, so default values of the following are used: [Resource-ref settings]
         res-auth: 1 (APPLICATION)
         res-isolation-level: 0 (TRANSACTION_NONE)
         res-sharing-scope: true (SHAREABLE)
         res-resolution-control: 999 (undefined)
    [Other attributes]
    isCMP1_x: false (not CMP1.x)
    isJMS: false (not JMS)
    [5/22/03 7:03:01:160 CDT] 2ec4c80 ConnectionFac E J2CA0009E: An exception occurred while trying to instantiate the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jdbc/DB239DataSource : java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl
         at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
         at com.ibm.ejs.j2c.XMLReader.validate(XMLReader.java:673)
         at com.ibm.ejs.j2c.XMLReader.init(XMLReader.java:241)
         at com.ibm.ejs.j2c.XMLReader.<init>(XMLReader.java:165)
         at com.ibm.ejs.j2c.ConnectorRuntime.getJ2C_Properties(ConnectorRuntime.java:341)
         at com.ibm.ejs.j2c.poolmanager.PoolManager.<init>(PoolManager.java:541)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createCFD_Common(ConnectionFactoryBuilderImpl.java:699)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createConnectionFactoryDetails(ConnectionFactoryBuilderImpl.java:417)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1400)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1675)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1538)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1458)
         at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1130)
         at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:122)
         at javax.naming.InitialContext.lookup(InitialContext.java:363)
         at oracle.toplink.jndi.JNDIConnector.connect(Unknown Source)
         at oracle.toplink.sessions.DatabaseLogin.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.buildConnection(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.startUp(Unknown Source)
         at oracle.toplink.threetier.ServerSession.connect(Unknown Source)
         at oracle.toplink.publicinterface.DatabaseSession.login(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getSession(ToplinkServerSessionFactory.java:121)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getClientSession(ToplinkServerSessionFactory.java:56)
         at com.deere.jdc.component.rcts.dao.RCTSGateway.findDealerASMByDealerNumber(RCTSGateway.java:194)
         at com.deere.jdc.component.rcts.service.RCTSService.getRCTSDealerASM(RCTSService.java:159)
         at com.deere.jdc.component.rcts.adapter.SoapRCTSService.getRCTSDealerASM(SoapRCTSService.java:107)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.invokeServiceMethod(RCTSMessageHandler.java:103)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.processMessage(RCTSMessageHandler.java:62)
         at com.deere.jdc.mqseries.MQJMSMessageHandler.onMessage(MQJMSMessageHandler.java:122)
         at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java:861)
         at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:401)
         at java.lang.Thread.run(Thread.java:513)
    [5/22/03 7:03:01:310 CDT] 2ec4c80 ConnectionFac A J2CA0013I: An exception occurred while trying to create ManagedConnectionFactory for DB239DataSource : java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl
         at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
         at com.ibm.ejs.j2c.XMLReader.validate(XMLReader.java:673)
         at com.ibm.ejs.j2c.XMLReader.init(XMLReader.java:241)
         at com.ibm.ejs.j2c.XMLReader.<init>(XMLReader.java:165)
         at com.ibm.ejs.j2c.ConnectorRuntime.getJ2C_Properties(ConnectorRuntime.java:341)
         at com.ibm.ejs.j2c.poolmanager.PoolManager.<init>(PoolManager.java:541)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createCFD_Common(ConnectionFactoryBuilderImpl.java:699)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createConnectionFactoryDetails(ConnectionFactoryBuilderImpl.java:417)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1400)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1675)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1538)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1458)
         at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1130)
         at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:122)
         at javax.naming.InitialContext.lookup(InitialContext.java:363)
         at oracle.toplink.jndi.JNDIConnector.connect(Unknown Source)
         at oracle.toplink.sessions.DatabaseLogin.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.buildConnection(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.startUp(Unknown Source)
         at oracle.toplink.threetier.ServerSession.connect(Unknown Source)
         at oracle.toplink.publicinterface.DatabaseSession.login(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getSession(ToplinkServerSessionFactory.java:121)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getClientSession(ToplinkServerSessionFactory.java:56)
         at com.deere.jdc.component.rcts.dao.RCTSGateway.findDealerASMByDealerNumber(RCTSGateway.java:194)
         at com.deere.jdc.component.rcts.service.RCTSService.getRCTSDealerASM(RCTSService.java:159)
         at com.deere.jdc.component.rcts.adapter.SoapRCTSService.getRCTSDealerASM(SoapRCTSService.java:107)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.invokeServiceMethod(RCTSMessageHandler.java:103)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.processMessage(RCTSMessageHandler.java:62)
         at com.deere.jdc.mqseries.MQJMSMessageHandler.onMessage(MQJMSMessageHandler.java:122)
         at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java:861)
         at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:401)
         at java.lang.Thread.run(Thread.java:513)
    [5/22/03 7:03:01:340 CDT] 2ec4c80 Helpers W NMSV0605W: A Reference object looked up from the context "localhost/nodes/localhost/servers/server1" with the name "jdbc/DB239DataSource" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows:
    Reference Factory Class Name: com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl
    Reference Factory Class Location URLs: <null>
    Reference Class Name: DB239DataSource
    Type: connectorName
    Content: DB239DataSource
    Type: classpath
    Content: C:\Program Files\IBM\WebSphere Studio\runtimes\base_v5/lib/rsadapter.rar
    Type: FactoryJndiName
    Content: jdbc/DB239DataSource
    Address Type: dd
    AddressContents: ffffffac ffffffed 0 5 73 72 0 25 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 52 65 73 6f 75 72 63 65 ...
    Address Type: poolProps
    AddressContents: ffffffac ffffffed 0 5 73 72 0 27 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f ...
    Address Type: configProps
    AddressContents: ffffffac ffffffed 0 5 73 72 0 23 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f ...
    Address Type: dsProps
    AddressContents: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c 2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a ...
    Address Type: mcfProps
    AddressContents: ffffffac ffffffed 0 5 73 72 0 2d 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 4d 61 6e 61 67 65 64 43 ...
    Address Type: mbeanProps
    AddressContents: ffffffac ffffffed 0 5 73 72 0 1a 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 4d 42 65 61 6e 50 72 6f ...
    Exception data follows:
    java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl
         at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
         at com.ibm.ejs.j2c.XMLReader.validate(XMLReader.java:673)
         at com.ibm.ejs.j2c.XMLReader.init(XMLReader.java:241)
         at com.ibm.ejs.j2c.XMLReader.<init>(XMLReader.java:165)
         at com.ibm.ejs.j2c.ConnectorRuntime.getJ2C_Properties(ConnectorRuntime.java:341)
         at com.ibm.ejs.j2c.poolmanager.PoolManager.<init>(PoolManager.java:541)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createCFD_Common(ConnectionFactoryBuilderImpl.java:699)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createConnectionFactoryDetails(ConnectionFactoryBuilderImpl.java:417)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1400)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1675)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1538)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1458)
         at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1130)
         at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:122)
         at javax.naming.InitialContext.lookup(InitialContext.java:363)
         at oracle.toplink.jndi.JNDIConnector.connect(Unknown Source)
         at oracle.toplink.sessions.DatabaseLogin.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.buildConnection(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.startUp(Unknown Source)
         at oracle.toplink.threetier.ServerSession.connect(Unknown Source)
         at oracle.toplink.publicinterface.DatabaseSession.login(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getSession(ToplinkServerSessionFactory.java:121)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getClientSession(ToplinkServerSessionFactory.java:56)
         at com.deere.jdc.component.rcts.dao.RCTSGateway.findDealerASMByDealerNumber(RCTSGateway.java:194)
         at com.deere.jdc.component.rcts.service.RCTSService.getRCTSDealerASM(RCTSService.java:159)
         at com.deere.jdc.component.rcts.adapter.SoapRCTSService.getRCTSDealerASM(SoapRCTSService.java:107)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.invokeServiceMethod(RCTSMessageHandler.java:103)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.processMessage(RCTSMessageHandler.java:62)
         at com.deere.jdc.mqseries.MQJMSMessageHandler.onMessage(MQJMSMessageHandler.java:122)
         at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java:861)
         at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:401)
         at java.lang.Thread.run(Thread.java:513)
    [5/22/03 7:03:01:891 CDT] 2ec4c80 Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
    Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
    Context method: lookup
    Context name: localhost/nodes/localhost/servers/server1
    Target name: jdbc/DB239DataSource
    Other data:
    Exception stack trace: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl
         at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
         at com.ibm.ejs.j2c.XMLReader.validate(XMLReader.java:673)
         at com.ibm.ejs.j2c.XMLReader.init(XMLReader.java:241)
         at com.ibm.ejs.j2c.XMLReader.<init>(XMLReader.java:165)
         at com.ibm.ejs.j2c.ConnectorRuntime.getJ2C_Properties(ConnectorRuntime.java:341)
         at com.ibm.ejs.j2c.poolmanager.PoolManager.<init>(PoolManager.java:541)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createCFD_Common(ConnectionFactoryBuilderImpl.java:699)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createConnectionFactoryDetails(ConnectionFactoryBuilderImpl.java:417)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1400)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1675)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1538)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1458)
         at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1130)
         at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:122)
         at javax.naming.InitialContext.lookup(InitialContext.java:363)
         at oracle.toplink.jndi.JNDIConnector.connect(Unknown Source)
         at oracle.toplink.sessions.DatabaseLogin.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.buildConnection(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.startUp(Unknown Source)
         at oracle.toplink.threetier.ServerSession.connect(Unknown Source)
         at oracle.toplink.publicinterface.DatabaseSession.login(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getSession(ToplinkServerSessionFactory.java:121)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getClientSession(ToplinkServerSessionFactory.java:56)
         at com.deere.jdc.component.rcts.dao.RCTSGateway.findDealerASMByDealerNumber(RCTSGateway.java:194)
         at com.deere.jdc.component.rcts.service.RCTSService.getRCTSDealerASM(RCTSService.java:159)
         at com.deere.jdc.component.rcts.adapter.SoapRCTSService.getRCTSDealerASM(SoapRCTSService.java:107)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.invokeServiceMethod(RCTSMessageHandler.java:103)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.processMessage(RCTSMessageHandler.java:62)
         at com.deere.jdc.mqseries.MQJMSMessageHandler.onMessage(MQJMSMessageHandler.java:122)
         at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java:861)
         at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:401)
         at java.lang.Thread.run(Thread.java:513)
    2003.05.22 07:03:02.111--ServerSession(426724481)--Thread[asyncDelivery0,5,main]--EXCEPTION [TOPLINK-7060] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.ValidationException
    EXCEPTION DESCRIPTION: Cannot acquire data source [jdbc/DB239DataSource].
    INTERNAL EXCEPTION: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl]LOCAL EXCEPTION STACK:
    EXCEPTION [TOPLINK-7060] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.ValidationException
    EXCEPTION DESCRIPTION: Cannot acquire data source [jdbc/DB239DataSource].
    INTERNAL EXCEPTION: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. [Root exception is java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl]
         at oracle.toplink.exceptions.ValidationException.cannotAcquireDataSource(Unknown Source)
         at oracle.toplink.jndi.JNDIConnector.connect(Unknown Source)
         at oracle.toplink.sessions.DatabaseLogin.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.buildConnection(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.startUp(Unknown Source)
         at oracle.toplink.threetier.ServerSession.connect(Unknown Source)
         at oracle.toplink.publicinterface.DatabaseSession.login(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getSession(ToplinkServerSessionFactory.java:121)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getClientSession(ToplinkServerSessionFactory.java:56)
         at com.deere.jdc.component.rcts.dao.RCTSGateway.findDealerASMByDealerNumber(RCTSGateway.java:194)
         at com.deere.jdc.component.rcts.service.RCTSService.getRCTSDealerASM(RCTSService.java:159)
         at com.deere.jdc.component.rcts.adapter.SoapRCTSService.getRCTSDealerASM(SoapRCTSService.java:107)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.invokeServiceMethod(RCTSMessageHandler.java:103)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.processMessage(RCTSMessageHandler.java:62)
         at com.deere.jdc.mqseries.MQJMSMessageHandler.onMessage(MQJMSMessageHandler.java:122)
         at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java:861)
         at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:401)
         at java.lang.Thread.run(Thread.java:513)
    INTERNAL EXCEPTION STACK:
    com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl
         at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
         at com.ibm.ejs.j2c.XMLReader.validate(XMLReader.java:673)
         at com.ibm.ejs.j2c.XMLReader.init(XMLReader.java:241)
         at com.ibm.ejs.j2c.XMLReader.<init>(XMLReader.java:165)
         at com.ibm.ejs.j2c.ConnectorRuntime.getJ2C_Properties(ConnectorRuntime.java:341)
         at com.ibm.ejs.j2c.poolmanager.PoolManager.<init>(PoolManager.java:541)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createCFD_Common(ConnectionFactoryBuilderImpl.java:699)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createConnectionFactoryDetails(ConnectionFactoryBuilderImpl.java:417)
         at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1400)
         at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
         at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
         at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1675)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1538)
         at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1458)
         at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1130)
         at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:122)
         at javax.naming.InitialContext.lookup(InitialContext.java:363)
         at oracle.toplink.jndi.JNDIConnector.connect(Unknown Source)
         at oracle.toplink.sessions.DatabaseLogin.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.connect(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.buildConnection(Unknown Source)
         at oracle.toplink.threetier.ConnectionPool.startUp(Unknown Source)
         at oracle.toplink.threetier.ServerSession.connect(Unknown Source)
         at oracle.toplink.publicinterface.DatabaseSession.login(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(Unknown Source)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getSession(ToplinkServerSessionFactory.java:121)
         at com.deere.jdc.toplink.ToplinkServerSessionFactory.getClientSession(ToplinkServerSessionFactory.java:56)
         at com.deere.jdc.component.rcts.dao.RCTSGateway.findDealerASMByDealerNumber(RCTSGateway.java:194)
         at com.deere.jdc.component.rcts.service.RCTSService.getRCTSDealerASM(RCTSService.java:159)
         at com.deere.jdc.component.rcts.adapter.SoapRCTSService.getRCTSDealerASM(SoapRCTSService.java:107)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.invokeServiceMethod(RCTSMessageHandler.java:103)
         at com.deere.jdc.component.rcts.messaging.RCTSMessageHandler.processMessage(RCTSMessageHandler.java:62)
         at com.deere.jdc.mqseries.MQJMSMessageHandler.onMessage(MQJMSMessageHandler.java:122)
         at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java:861)
         at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:401)
         at java.lang.Thread.run(Thread.java:513)

    This looks like a classPath issue.check ur runtime
    class path and make sure xerces is before any other
    parser(xml4j /oracleParser)
    vasanth

  • Need help on datasource.plugin.DataSourceException issue

    Can any one help me on this issue.I can try to deploy the application succefully on weblogic.but when developers try to test this application they are receiving thsi error,is this a data source issue or anything else,
    com.xyz.tcc.apollo.webflow.process.flow.StateException: ; nested exception is com.xyz.tcc.apollo.common.datasource.plugin.DataSourceException: com.xyz.tcc.apollo.startup.service.ServiceCommunicationException: com.xyz.POSClient.POSException: org/apache/xpath/XPathAPI
                    at com.xyz.tcc.apollo.workflow.process.ProcessContext.handleException(ProcessContext.java:162)
                    at com.xyz.tcc.apollo.workflow.actions.common.LongOperationAction$3.run(LongOperationAction.java:79)
                    at java.awt.event.InvocationEvent.dispatch(Unknown Source)
                    at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
                    at java.awt.EventQueue.access$000(Unknown Source)
                    at java.awt.EventQueue$1.run(Unknown Source)
                    at java.awt.EventQueue$1.run(Unknown Source)
                    at java.security.AccessController.doPrivileged(Native Method)
                    at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
                    at java.awt.EventQueue.dispatchEvent(Unknown Source)
                    at com.xyz.tcc.apollo.core.error.ErrorHandlingEventProcessor.dispatchEvent(ErrorHandlingEventProcessor.java:55)
                    at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
                    at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
                    at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
                    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
                    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
                    at java.awt.EventDispatchThread.run(Unknown Source)
    Caused by: com.xyz.tcc.apollo.common.datasource.plugin.DataSourceException: com.xyz.tcc.apollo.startup.service.ServiceCommunicationException: com.xyz.POSClient.POSException: org/apache/xpath/XPathAPI
                    at com.xyz.tcc.apollo.common.datasource.plugin.extensionpoint.xml.pos.POSDataSourceDelegate.getResponse(POSDataSourceDelegate.java:51)
                    at com.xyz.tcc.apollo.common.datasource.plugin.extensionpoint.xml.serialization.impl.SerializedXMLDataSourceDelegateImpl.perform(SerializedXMLDataSourceDelegateImpl.java:51)
                    at com.xyz.tcc.apollo.common.datasource.plugin.extensionpoint.xml.serialization.impl.SerializedXMLDataSourceDelegateImpl.perform(SerializedXMLDataSourceDelegateImpl.java:47)
                    at com.xyz.tcc.apollo.common.datasource.plugin.extensionpoint.xml.serialization.impl.SerializedXMLDataSourceDelegateImpl.perform(SerializedXMLDataSourceDelegateImpl.java:38)
                    at com.xyz.tcc.apollo.common.datasource.plugin.extensionpoint.xml.serialization.impl.DefaultSerializedXMLDataSource.perform(DefaultSerializedXMLDataSource.java:22)
                    at com.xyz.tcc.apollo.workflow.actions.datasource.AbstractDataSourceOperationAction.submitDataSourceAction(AbstractDataSourceOperationAction.java:102)
                    at com.xyz.tcc.apollo.workflow.actions.datasource.AbstractDataSourceOperationAction.submitDataSourceAction(AbstractDataSourceOperationAction.java:96)
                    at com.xyz.tcc.apolloekgviewerplugin.actions.LoadMyProjectsIfExistsAction.addPOSResponse(LoadMyProjectsIfExistsAction.java:47)
                    at com.xyz.tcc.apolloekgviewerplugin.actions.LoadMyProjectsIfExistsAction.callOperation(LoadMyProjectsIfExistsAction.java:32)
                    at com.xyz.tcc.apollo.workflow.actions.common.LongOperationAction.executeOperationCall(LongOperationAction.java:55)
                    at com.xyz.tcc.apollo.workflow.actions.common.LongOperationAction.access$000(LongOperationAction.java:12)
                    at com.xyz.tcc.apollo.workflow.actions.common.LongOperationAction$1$1.run(LongOperationAction.java:41)
                    at java.lang.Thread.run(Unknown Source)
    Caused by: com.xyz.tcc.apollo.startup.service.ServiceCommunicationException: com.xyz.POSClient.POSException: org/apache/xpath/XPathAPI
                    at com.xyz.tcc.apollo.startup.service.POSClientServiceConsumer.getResponseAsStream(POSClientServiceConsumer.java:69)
                    at com.xyz.tcc.apollo.common.datasource.plugin.extensionpoint.xml.pos.POSDataSourceDelegate.getResponseImpl(POSDataSourceDelegate.java:60)
                    at com.xyz.tcc.apollo.common.datasource.plugin.extensionpoint.xml.pos.POSDataSourceDelegate.getResponse(POSDataSourceDelegate.java:49)
                    ... 12 more
    Caused by: com.xyz.POSClient.POSException: org/apache/xpath/XPathAPI
                    at com.xyz.POSClient.POSErrorContentHandler.getException(POSErrorContentHandler.java:77)
                    at com.xyz.POSClient.POSInputStream.checkForException(POSInputStream.java:69)
                    at com.xyz.POSClient.POSInputStream.checkIfStreamAnError(POSInputStream.java:114)
                    at com.xyz.POSClient.POSInputStream.<init>(POSInputStream.java:37)
                    at com.xyz.POSClient.InputStreamPOSResult.<init>(InputStreamPOSResult.java:21)
                    at com.xyz.POSClient.DefaultInputStreamPOSResultFactory.createResult(DefaultInputStreamPOSResultFactory.java:16)
                    at com.xyz.POSClient.XMLPOSConnection.callService(XMLPOSConnection.java:89)
                    at com.xyz.tcc.apollo.startup.service.POSClientServiceConsumer.getResponseAsStream(POSClientServiceConsumer.java:64)
                    ... 14 more

    Hi,
    This is not issue with Weblogic.
    It seems that your app is using direct provider directly.
    for this you u can include this driver under classpath and restart the server once and try to access your app whether they can able to access your DB or not.
    Regards,
    Kal

  • Generic Datasource Delta upload Issue

    Hi all,
    I have created a Generic Datasource for Solution Manager ODS 0crm_process_srv_h which contains the userstatus, transaction number, transaction desc and GUID of CRM Order Object (ods key field),only these fields.
      I have taken transaction number as delta field and it is as timestamp. But delta upload is not happening. If I give GUID or Status also delta upload is not happening . Please suggest which is the best way to give to delta upload.
    Thanks and Regards,
    SGK.

    Hi,
    in your case you need to create a function module as a extractor. Create a extract structure as well and add a timestamp field (lets call it zdeltahelp) to be used as the delta relevant field of the datasource. After successful init the last extraction timestamp will be passed to the fm and you can start selecting all resb entries for orders created and/or changed from that time on as well as the ones deleted (but therefore you need to read the change documents as well). For more information about generic extraction using fm search the forum or check out my business card. There you will find a link to a weblog about that issue.
    regards
    Siggi

  • Datasource Activation/replication issue

    Hi Experts
      Please update me what am i missing
      In R/3
    Development...i activated a Business Content data source and raised a Transport request and imported that transport in to R/3 Quality
    Check R/3 Quality i check RSA3 and datasource is extracting data
    In BW
    Development...I replicated that datasource and activated relevant BW Objects(Transfer rules,Update reules,Infosource,Cube ...etc) and extracted data and raised Transport request
    In BW Quality
    I replicated Same data source.....
    When i check the datasource in display mode it is not in active mode and showing me as in modified mode
    When i tried to import the transport request is raised BW Development itt failed because the datasource is not in active mode
    I checked Source system connection and everything is fine
    We care using BI 7.0
    Please update me how to proceed

    Hi,
          While transporting the transfer rules from Development system to Quality system please capture the datasource replica (object type R3TR ISFS) also in the transport request. This will automatically replicate the active version of your datasource in the BW quality system. Also, before importing the transport request. Please make sure that the source system definition in the BW system is active.
    Hope this helps you.
    Thanks,
    Nithin Reddy.

  • DataSource - FlashIsland concepts issue

    Hi everyone, I´m working with FlashIslands and I guess I have a concept issue here with the GACDATASOURCE ....I just can´t iterate the arraycollection in flex.
    in WD:
    I have a node called A, with 3 attributes, the node cardinality can be 0 .... to N.
    I have GACDataSource (Context Node) and three properties (Node Attributes) binded to the context
    in flex :
    I set a Bindable ArrayContainer object called "tableDataContainer"
    I set a Bindable attribute for each of the properties
    well, i cant get the attributes values,  the arraycontainer is properly created.... the arrayContainer size and the context node size are both of 3, then i guess I already have the values in flex. but i cant get data, only Objects...
    Try 1:
    var obj:Object = tableDataContainer.getIndexAt(0);
    Alert.show(obj["attr1"]);
    Try2 :
    var obj:Object = tableDataContainer.getIndexAt(0);
    Alert.show(obj.attr1);
    does everyone know how to iterate the plain content of the ArrayContainer ?
    thanks

    hi isaac,
    not sure this is what you are looking for. i am a flex developer, have limited amount of knowledge of SAP.
    the result of the following code:
    Object 0 => name = p
    Object 1 => name = m
    Object 2 => name = e
    completed code:
    <?xml version="1.0" encoding="utf-8"?>
    <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"
         initialize="initApp(event);"
         layout="absolute">
         <mx:Script>
              <![CDATA[
                   import mx.events.FlexEvent;
                   import mx.collections.ArrayCollection;
                   private function initApp(event:FlexEvent):void
                        var leng:int = tableContainer.length;
                        for(var i:int=0; i<leng; i++)
                             trace("Object " + i + " => name = " + tableContainer<i>.name);
              ]]>
         </mx:Script>
         <mx:ArrayCollection id="tableContainer">
              <mx:source>
                   <mx:Object id="p" name="p" />
                   <mx:Object id="m" name="m" />
                   <mx:Object id="e" name="e" />               
              </mx:source>
         </mx:ArrayCollection>
    </mx:Application>
    normally, when i get the set of data from the server into my flex app, i will put them into value objects(vo) individually and add each vo to the array collection which is binded to the data source.
    hopefully this helps.
    Mike

  • SNP - Issue with PDS as source of supply in low-level code run

    Hi All:
    I have a bunch of PDS that is giving me the following message when the SNP Low-level code is run:
    ''Invalid source 00000010382991380SLT1 S is not considered for low-level code calculation.  The source of suppy 00000010382991380SLT1   S is available actively in the Supply Chain Model. The location product for which the source of supply is intended, does not exist, however, or is no longer assigned to the model. The source of supply is therefore invalid. ''
    I tried all of the following but still did not get to work
    1. Made sure that FG and all the active component of one FG and the location and the PDS were in an active model.
    2.  Made sure that there was one production version and hence one PDS
    3.  Intialiazed the Planning area with the version
    But still would not generate the low level code for the product location.  Can some one throw share some insight and help pl?
    Thanks
    Ryan

    Could you please check whether in the Product Master, Procurement tab, the Procurement Type is set as "P - external procurement planning"? If yes, then that's the reason as the Low-Level Code is only calculated for Products that are to be planned in APO. In this case, change procurement type to X or E and it should work.
    Regards,
    Tiago

  • MS SQL Server JDBC 2.0 datasource creation issue using Visual Admin

    Hi,
    I need to create an MS SQL Server JDBC 2.0 DataSource using the Visual Admin (running on NetWeaver 2004 SP19). I'm using the Microsoft SQL Server 2005 JDBC driver. Have no problem creating a Version 1.x (no XA support) DataSource.
    The issue is that when I try to create a Version 2.0 (with XA support) datasource I get the following exception: java.sql.SQLException: Invalid DataSource reference
    This is the setup I used:
    JDBC Version "2.0 (with XA support)
    JDBC 2.0 Compliant:
      object factory:  com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory
      datasource type: XADataSource
      xads class name: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
    On the additional tab:
    databaseName=fldev_jj
    portNumber=1433
    serverName=dbsrv61
    user=fldev_jj
    password=******
    Even added the url, but that made no difference. Chose Vendor SQL,
    and have initial connections set to 1. This url worked when used
    with a version 1.x datasource.
    What can I try to do to resolve this?
    Full exception:
    java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "factorylogic.com/FactoryLogicBusinessDS". [id = StartupError]
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
         ... 42 more
    Caused by: java.sql.SQLException: Invalid DataSource reference.
         at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
         ... 43 more
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
         ... 31 more
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
         at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
         at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
         at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
         at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
         at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
         at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
         at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
         at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
         at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
         at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
         at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
         at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
         at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
         at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
         at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
         ... 42 more
    Caused by: java.sql.SQLException: Invalid DataSource reference.
         at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
         at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
         ... 43 more
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
         ... 33 more
         at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1016)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
         at javax.management.MBeanException.writeObject(MBeanException.java:126)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
         at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
         at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
         at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1309)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
         at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
         at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
         at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
         at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
         at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1272)
         at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1250)
         at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
         at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
         at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

    Leaving the object factory empty is absolutely part of the solution.
    I can now start the data source and it can get a connection.
    The remaining problem is that the moment I try to do anything with xa (inside of netweaver, using the datasource) I get an xa error... Found a way around that by changing the datasource type from "XADataSource" to a "ConnectionPoolDatasource".
    The problem with that is that I'm no longer sure it uses XA transactions...
    Will do more testing...
    Very helpful reply Yuri!
    Thanks

  • SNP planning Area Backup

    Hi All,
         Currently i am working on 5.0 SCM.I have one query.
    For Reporting perpose we required to take backup of SNP planning Area,so that i can save SNP planning Area data in Info cube.I would like to see data in Infocube according to Product,Location & Resource wise only. So that i can use this data for reporting perpose.
         Can we create whole data flow process for SNP Planning Area?
         We have lot of Product & resources in APO,so is it feasible to take backup of SNP planning Area?
         I want to take backup of SNP planning area only for reporting perpose,so that i can publish report according to my Product,Location & Resources.
        So kindly suggest proper solution to achive above requirement.
       Thanks in Advance!
    Regards
    Sujay

    Attaching note 428147
    Summary
    Symptom
    When extracting data from an SNP planning area, you must take account of some special features. These are explained in this note.
    Solution
          1. Data can be extracted only for existing SNP aggregates.
          Existing SNP aggregates are:
              o 9AAC (9AACTNAME)
              o 9AACPR (9AACTNAME, 9APPMNAME)
              o 9ALA (9ATRNAME)
              o 9ALO (9ALOCNO)
              o 9ALORE (9ALOCNO, 9ARNAME)
              o 9AMA (9AMATNR)
              o 9AMALA (9AMATNR, 9ATRNAME)
              o 9AMALARE (9AMATNR, 9ARNAME, 9ATRNAME)
              o 9AMALO (9ALOCNO, 9AMATNR)
              o 9AMALORE (9ALOCNO, 9AMATNR, 9ARNAME)
              o 9AMAPR (9AMATNR, 9APPMNAME)
              o 9AMARE (9AMATNR, 9ARNAME)
              o 9APR (9APPMNAME)
              o 9ARE (9ARNAME)
              o 9AREPR (9APPMNAME, 9ARNAME)
               Only the characteristic/characteristic combinations contained in these aggregates may be used in the InfoSource, transfer structure and transfer rules.The simplest way of doing this is by always generating Export-DataSources for SNP planning areas to one of the aggregates and not to the Basis planning object structure '9ASNPBAS'.A typical result of using the Basis planning object structure '9ASNPBAS' without correcting the transfer structure is that, while data is transferred to a RemoteCube, it cannot be extracted in a BasisCube.
    As of APO 3.0 Support Package 17 (or note 443613), only export DataSources for aggregates can be generated in SNP planning areas  they are no longer generated for the Basis planning object structure.
    Furthermore, note that the navigation attributes 9ATTYPE, 9ALOCTO, and 9ALOCFROM up to APO 3.0 Support Package 17 (or note 441653) must be deleted from the transfer structure for the SNP aggregates '9AMALA' (9AMATNR/9ATRNAME) and '9AMALARE' (9AMATNR/9ATRNAME/9ARNAME). These navigation attributes can be used from the specified correction.
    Due to technical restrictions the characteristics '9ATRNAME' and '9ATTYPE' can only be restricted with single values in the selection for the data extraction.The use of intervals and formatting characters (+/*) is not allowed for these characteristics.
          2. For an SNP aggregate, only the key figures assigned to it can be extracted. You can see which key figures are assigned to an aggregate in transaction /SAPAPO/MSDP_ADMIN on the Key figure assignment tab of the relevant planning area. As of APO 3.0 Support Package 17 (or note 439366), only the key figures assigned to this aggregate are taken into account when an export DataSource is being generated for aggregates.
          3. During the definition of queries, the following restrictions apply:
               In the case of queries for the aggregate '9AMALA', certain key figures can only ever be extracted with another key figure.The key figure combinations that can only be extracted together are:
              o (9AFSHIP, 9ADMDDF, 9ADMDDFVMI)
              o (9AFSHIPLP, 9ADMDDFLP)
              o (9AFSHIPVMI, 9ADMDDFVMI)
              o (9APSHIP, 9ADMDDI, 9ADMDDIVMI)
              o (9APSHIPLP, 9ADMDDILP)
              o (9APSHIPVMI, 9ADMDDIVMI)
              o (9ATSHIP, 9ADMDDT, 9ADMDDTVMI)
              o (9ATSHIPVMI, 9ADMDDTVMI)

  • 0hr_py_1 datasource extraction problem

    Friends,
    I am trying to extract data for 0hr_py_1 datasource and having issues.
    After activation, when i go in R3 to check in rsa3, it says 0 records.
    What i know is that HR extraction is simple and you just have to activate the datasource and replicate Metdata. I am not sure of any other steps...can anybody help. Are their any additional steps on R3 to be performed ????????

    Hi,
    Check if you are extracting in full mode in RSA3 and if you still don't get data, try to debug the extractor and see at which step it is not getting data.
    From this you will get to know which are the tables / FM involved in data selection.
    Regards,
    Durgesh.

  • Adding a Datasource to a running Server ?

    What is the best way to add a new data-source to a running Server ?
    Perviously, I was binding a new DataSource Object into the JNDI Tree from the context of an EJB, with an external process writing the new DataSource into the data-sources.xml file.
    But now I've kicked EJB's out of the application, replacing with POJO's accessed from the servlet tier and the binding of the datasource fails (unusual issue and all my other Objects bind perfectly, I'll continue investigating...)
    Now, I know that the admin.jar file can be used to manually add new data-sources to a server, but is this the best way to add data-sources to an already running server ?
    Could I in some way call into the appropriate Class to add a new data-source.
    e.g. A Server API like this: OC4JServer.addDataSource( Map params ); would be handy
    Cheers,
    Ro

    Hello,
    One way of doing that in OracleAS 10.1.3 will be to use JMX and MBeans.
    The getMBeanServer() returns you an MBean Server connection where you can invoke operations as follow:
    String appBeanName = "oc4j:j2eeType=J2EEApplication,name="+ j2eeAppName +",J2EEServer=standalone";
    ObjectName obj = new ObjectName(appBeanName);
    // invoke the create connection pool and create connection
    // values used to create the connection pool
    Object[] paramsPool = {
    connectionPoolName,
    dataSourceFactory,
    username,
    password,
    url};
    // signature used to create the connection pool
    String[] signaturePool = {
    "java.lang.String",
    "java.lang.String",
    "java.lang.String",
    "java.lang.String",
    "java.lang.String"};
    // Call the connection pool creation operation
    getMBeanServer().invoke(
    obj,
    "createJDBCConnectionPool", //operation
    paramsPool,
    signaturePool);
    // Values used to create the connection
    Object[] paramsConn = {
    connectionName,
    username,
    password,
    "jdbc/"+ connectionName,
    new Integer(30), // timeout
    connectionPoolName,
    "global",
    null};
    // Signature used for the Operation call
    String[] signatureConn = {
    "java.lang.String",
    "java.lang.String",
    "java.lang.String",
    "java.lang.String",
    "java.lang.Integer",
    "java.lang.String",
    "java.lang.String",
    "java.lang.String"
    getMBeanServer().invoke(
    obj,
    "createManagedDataSource",
    paramsConn,
    signatureConn
    Regards
    Tugdual Grall

  • Issue in Delivery document Status update

    Hi ,
    We are facing serious issue in delivery document delta extraction via Delivery item Datasource (2LIS_12_VCITM). This leads to incorrect Pending logistic figures in stock and dispatch report. Details for the issue are as follows.
    Datasource used : 2LIS_12_VCITM
    Issue Description :
    The goods movement status flag (WBSTA) field from the ECC table VBUP is not correctly extracted by the standard deliveries item datasource (2LIS_12_VCITM) during delta loads.
    Steps taken to rectify the issue
    -     We have removed the commit work statement and applied in parallel update task in ECC. Include : ZSD_INCL_DEL_SAVE_FINS
    -     Setup tables for Delivery were filled in ECC.
    -     Historic data was deleted from the Delivery cube in  BW
    -     Data was pulled into PSA (Info package u2013 Full Update)  from where it was loaded to DSO in overwrite mode  (Historic data was not deleted from DSO)
    -     Data from DSO to delivery cube was loaded with DTP setting as Full Update.
    -     After complete data was updated in Cube the DTP setting were changed to Delta.
    -     Delta info package was scheduled  for the capturing the document changes from next load.
    -     Goods Movement status for all the documents created till this point was exactly similar to the status in ECC.
    -     The goods movement status flag (WBSTA) field from the ECC table VBUP is not correctly extracted by the standard deliveries item datasource (2LIS_12_VCITM) during delta loads.
    Example              :
                                    Delivery document no:  2131260470 is pulled with goods movement status u201CAu201D in firstly load (here BW Delivery status matches
                                        With ECC )
                                   Before next delta load status in ECC (WBSTA) changes to u201CCu201D (PGI Complete) along with updated u201CGoods Issue Dateu201D
                                   Extractor fails to capture the change in document ,thus status in BW remains as u201CAu201D with no date updated in u201CGoods Issue Dateu201D
                                       field.
    Steps for Reconstruction :
    1)     Check the value of Goods movement status and actual goods issue date fields in the PSA for the datasource 
    2LIS_12_VCITM in BW for the sample delivery mentioned in the attached file
    2)     Compare these values with the ones in the ECC table VBUP.
    Kindly help at the earliest.
    Regards,

    Hi,
       Could anyone please reply as its quite critical.
    many thanks in advance,
    regards
    pramod.

  • Incorrect logical system name for datasources - entry not in TADIR

    Hi all,
    I currently can't replicate or edit any of my data sources because, after we applied some patches, the logical system name appears to be incorrect and a message is displayed saying the R3TR RSDS entry does not exist in table TADIR.
    For example:
    Object directory entry R3TR RSDS 0EMPLOYEE_0016_ATTR           R3DEV does not exist.
    That's correct, because all entries exist for my actual source system CD1CLNT175, not for SAP standard R3DEV.
    Does anybody have any idea how I can update my source system configuration/mapping? I've looked on the forum but couldn't
    find a clear cut answer.
    Thanks a lot!
    Markus

    Hi all,
    I think the solution lies in SAP note 1604726 "DataSources with package assignment cannot be activated"
    1. When you access the change transaction RSDS, the system issues error message TK 753 "Object directory entry R3TR ... does not exist" twice.
    2. When you try to activate the DataSource, the system issues error message TK 425 "Invalid call sequence for interfaces when recording changes".
    My message is TK753.. and before that I receive TK425, I guess we have to apply SP28... time for Mario and Luigi to apply some pizzas... ehmm patches...!
    I will let you know if that solved the problem, thanks for your help guys!
    Markus

  • Very urgent : Problem with field attributes in Datasource

    Hi
    I am getting a problem with field attributes in the datasource.
    The issue came up after i modified the extract structure-i modified one field and
    added one field to the structure.Now those two fields are not visible in BW.
    When i checked with transaction rsa2, i could find that for those two fields , the
    field attribute is <b>'A'</b> which is <b>'Field in OLTP and BW Hidden by SAP'</b>.
    I tried to modify the field attribute to make it visible.Now the issue is that it is not getting reflected after transport in the Q system.What can be the issue.In the Q system its still the old value 'A' ,which makes the fields invisible.
    Please let me know what can be the issue.
    Regards
    Leon

    Hi,
    did you change this attribute via RSA2?
    you need to change your datasource via postprocessing (RSA6); then transport your DS to your Q source system.
    Replicate your datasources in your BW.
    Finally modifiy your Transfer Structure by editing your TRules ( tab Datasource/Tran structure), move your new fields from the right frame to the left frame)
    Maintain your TRules
    Activate
    hope this helps...
    Olivier.

  • New Source System Issue

    Hi
    We are trying to connect new Source System to BW. It is ECC 5.0.
    When I try to activate the Source System, it generates the following error:
    <b>EDI: Partner profile not available
    Entry in inbound table not found
    Entry in outbound table not found
    Entry in outbound table not found</b>
    I checked WE20, it looks good. This is very similar to the current R/3 System (4.6). I was able to REPLICATE the DATASOURCE with no issues.
    Can you please let me know, how this could be resolved.
    Regards,
    GPK.

    Hi Guru's
    The OSS note mentioned was a good one. I did check that OSS to ensure we were on track. There was no loop hole i got in regards to this issue.
    I cannot say why it worked for me but I could tell what I did.
    1. Deleted the source system, I creted.
    2. Created the Source System back again.
    3. It worked, but the only difference I noted was that, the icon of the source system is like the BW and not like the r/3 icon. I don't know WHY??
    Thank you all for your support and advices.
    Regards,
    GPK.

Maybe you are looking for

  • Problem with mutiple photo gallery...

    Hello, I'm new to As3.0 (i'm a designer...) but I need to create a photo gallery, So I found a Tutorial On lynda.com. I'm using a code that works perfectly, and modified it (copy and paste it) to have 2 SAME photo gallery (using different images) dis

  • Cannot update Camera Raw from 6.7 to 7.1

    When I try to update Camera Raw from 6.7 to 7.1, from the 7.1 setup file I downloaded, I get the error: "Update failed Updates could not be applied This patch is not applicable for you. Please check for updates from the help menu in your product to s

  • Does web service support all the properties in the standalone BI console?

    Hi, Currently I am using BI web service API to get the report and its parameters and so on. But I find that the object definition in the web service can't be full defined to match the properties in the console UI. For exaple, ReportDefinition object

  • Java Developer's Journal Reader's Choice Award

    Sun Java System Application Server has been nominated for a Java Developer's Journal Reader's Choice Award; if you find it useful, please support us by voting. Vote for Sun Java System Application Server for Best Java Application Server. http://sys-c

  • Can't get Droplets to call 32 Bit Photoshop

    I'm trying to get my Droplets to call the 32 bit version of Photoshop CS5, but it will only call the 64 bit version. My Droplet runs a Plugin that currently only supports 32 bit version of CS5.  How do I configure which version of CS5 will get involk