Ar01 Transaction  Runing Problem

Hi All,
   AR01 transaction to raise the "Fiscal year change not yet made for company code XXXX" , because i did not open the new asst year.
If is possible to view the last year asset balance details.
Thanks
Saravanan

Hi,
just do ARJW to get a new year for the assets.
But be aware, that changes on asstes then will affect also the the year before. 
You can close the fiscal year and do AJAB later after your last depreciation.    
kind regards sibylle

Similar Messages

  • MDB Transaction Management Problem

    Hi,
    I am implementing a container managed MDB. The process involves implementing the retry queue and a dead letter queue in case the message is not processed properly.
    In one of the scenarios, an exception gets thrown during the message processing and the message is sent to the retry queue. But somehow it is not being delivered to this queue also and an exception gets thrown. I can see the stacktrace in the logs but somehow This exception is not causing my transaction to rollback in the original MDB and hence the message is getting lost.
    I am using WSAD 5.1 with websphere app server.
    Can someone help please.

    Hi,
              Thanks for your reply.
              Unfortunatelly, I didn't find any information about that issue in Release Notes of Service Pack 5.
              Could you show me any source of information about this problem as it is known issue ?

  • JDBC, JMS and EJB transactions - possible problem?

    Hello,
              I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
              XDoclet.
              In my current project I have the following piece of code
              in one of my message driven beans (code cited as pseudocode
              without unnecessary details):
              * @ejb.bean name="MyMessageProcessor"
              * display-name="Display name for a MyMessageProcessor"
              * jndi-name="ejb/MyMessageProcessor"
              * description="Bean MyMessageProcessor"
              * destination-type="javax.jms.Queue"
              * transaction-type="Container"
              * acknowledge-mode="Auto-acknowledge"
              * subscription-durability="Durable"
              * generate="false"
              * @ejb.transaction type="Required"
              public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
              public void onMessage(Message msg) {
                   try {
                        //obtaining connections to two different databases via JNDi
                        java.sql.Connection connOne =
                        ((DataSource)ctx.lookup("DataSourceOne")).getConnection();          
                        java.sql.Connection connTwo =
                             ((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
                        // performing some UPDATEs and INSERTs on connOne and connTwo
                        // calling some other methods of this bean
                        //creating the reply JMS message and sending it to another JMS queue
                        Message msgTwo = this.createReplyMessage(msg)
                        this.queueSender.send(msgTwo);
                        //commiting everything
                        this.queueSession.commit();          
                   } catch (Exception ex) {
                   try {
                        if (this.queueSession!=null) this.queueSession.rollback();
                   } catch (JMSException JMSEx) {};     
                   this.context.setRollbackOnly();
              Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
              connection pool with non-XA jdbc driver. Everything worked fine
              including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
              to database and the incomming message was thrown back to the my bean's
              queue).
              When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
              participate in a global transaction. When I changed both datasources
              to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
              EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
              and the JMS message wasn't resent to the JMS queue.
              So here are my questions:
                   1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
                   Are there any global server configurations, which may influence this situation?
                   2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
                   (of course, if necessary)?
                   3. Are there any JMS Queue settings, which would disable the container to send message back to the
                   queue in case of setRollbackOnly()? How should be the Queue configurated?
              As I am new to the topic and the deadline for the project seems to be too close I would be grateful
              for any help.
              This message was sent to EJB list and JDBC list.
              Sincerely yours,
              Marcin Zakidalski

    Hi,
              I found these information extremely useful and helpful.
              The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
              Anyway, I still have some problems. I have made some changes to the
              code cited in my previous mail. These changes included changing QueueSessions
              to non-transactional. I also set the "Honorate global transactions" to true.
              I am using XA JDBC driver. After setting "Enable local transactions" to false
              (I did it, because I assume that JDBC transactions should be part on the global
              EJB transaction) I got the following error:
              java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
              driver supports performing SQL operations with no global transaction, explicitly allow it by setting
              "SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
              transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
              complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
              I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
              the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
              My questions are as follows:
              1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
              thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
              from doing that? Can using setAutocommit(true/false) change the situation for better?
              2. How to encourage the JDBC driver to be a part of EJB transaction?
              3. As I have noticed each of ejb method has its own transactions (transactions have different
              Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
              way that if already started transaction exists it is used by the called method?
              4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
              impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
              enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
              solved programmically?
              Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
              I am loosing the ability to perform all actions in one transaction.
              Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
              Marcin

  • Toplink transaction-type problem

    we have web application ear file, inside ear file persistence.xml is looking like
    <persistence-unit name="TCA" transaction-type="JTA">
    <provider>oracle.toplink.essentials.PersistenceProvider</provider>
    <jta-data-source>jdbc/TcaConnDS</jta-data-source>
    We have deployed same ear file to 4 different oc4j instances and 2 oc4j instances application working without problem. Another 2 oc4j instances application does not work and we have to modify transaction-type="JTA" to transaction-type="RESOURCE_LOCAL" to make it work.
    Since we have deployed same ear to all oc4j instances, 2 oc4j only work with transaction-type="JTA" and the other 2 only work with transaction-type="RESOURCE_LOCAL".
    I think it is OC4J configuration to affect toplink behavior. Which oc4j configuration can affect toplink transaction-type setting?
    Thanks for the help.

    Very odd. What does not work, what error do you get?
    Are the OC4J servers that same version, what is different about them?
    James : http://www.eclipselink.org

  • EJB Entity transaction rollback problem

              Hello,
              I have created 2 beans one is a Stateless Session and the other a Bean Managed Entity Bean. The SS Bean has methods to retrieve an Oracle Connection from a DataSource defined connection pool, and to close a connection. The entity bean I have created is responsible for insterting a new record into one of the tables in my database.
              I have a client app that calls the ejbCreate method on the entity bean at which point the Entity EJB takes control, gets a valid connection from the SS EJB, runs a simple working SQL SELECT statement (obtaining correct values), and then attempts to perform an insert into a table using a prepared statement. My problem is that the application runs fine without any errors and all calls are made and all calls seem to be working fine. I have checked to make sure that the Datasource I am using is AutoCommit= false and it is and there are no exceptions being thrown in my EJB's but yet it appears as though the SQL statements executeUpdate() command is not being committed as their is no rows created in the database. Does anyone know what I may be doing wrong. I have all ACL parameters set up correctly and as I stated before the entire app runs without errors and I do have a SELECT statment that is working properly within the same method as the INSERT statement which is not!!! Please send any suggestions!!
              Justin
              

              I am using CMT, it is activated by default on Entity Beans I believe. The bean itself is marked as TX_REQUIRED so I believe all the methods automatically are all TX_REQUIRED.
              Here is my Bean ejbCreate Method, My PK class, and my ejb-jar.xml file-- I've pasted them below for convenience.
              ejbCreate:
                   public CustomerPK ejbCreate(String aUserName, String aPassword, String aFirstName,
                        String aMiddleInit, String aLastName, String aEmailAddr)
                        throws javax.ejb.CreateException {
                   Connection conn=null;
                   long nextPrsnID;
                   long nextCustID;
                   if (verifyParams(aUserName, aPassword, aFirstName, aMiddleInit,
                        aLastName, aEmailAddr)) {
                   if (isUniqueUserName(aUserName)) {
                   try {
                        conn=getConnection();
                        conn.setAutoCommit(false);
                        nextPrsnID=addPerson(conn,aFirstName,aMiddleInit,aLastName); // adds a person to the person table consists of just simple SQL
                        nextCustID=addCustomer(conn,nextPrsnID, aUserName,aPassword, aEmailAddr); //adds a customer to the customer table
                        // SET THE BEAN MANAGED PUBLIC VARIABLES
                        this.userName=aUserName;
                        this.password=aPassword;
                        this.firstName=aFirstName;
                        this.middleInit=aMiddleInit;
                        this.lastName=aLastName;
                        this.emailAddr=aEmailAddr;
                        this.personID=nextPrsnID;
                        this.custID=nextCustID;
                        conn.commit(); // with this statement here the transaction goes through otherwise the DB will not be updated
                   catch (Exception e){
                        throw new javax.ejb.CreateException("Experiencing Database Problems-- Unrecoverable Error"); // rollback transaction
                   finally{
                        cleanup(conn,null); // close the connection
                   else {           // UserName already exists
                   throw new javax.ejb.CreateException("Sorry username already exists please choose another one");
                   else {          // Registration parameters were not verifiable
                   throw new javax.ejb.CreateException("Registration paramater rules were violated");
                   CustomerPK custPK=new CustomerPK(nextCustID);
                   return custPK;
              EJB CUSTOMER PRIMARY KEY CLASS:
              public class CustomerPK implements java.io.Serializable {
              // PRIMARY KEY VARIABLES
              public long CustomerID;
              public CustomerPK(long aCustomerID) {
              this.CustomerID=aCustomerID;
              public CustomerPK() {
              public String toString(){
              return ((new Long(CustomerID)).toString());
              public boolean equals(Object aComparePK){
              if (this.CustomerID==((CustomerPK)aComparePK).CustomerID){
                   return true;
              return false;
              public int hashCode(){
              return ((new Long(CustomerID).toString()).hashCode());
              } // END-CLASS
              CUSTOMER ejb-jar.xml
              <?xml version="1.0"?>
              <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
              <ejb-jar>
              <enterprise-beans>
              <entity>
                   <ejb-name>Customer</ejb-name>
                   <home>CustomerHome</home>
                   <remote>Customer</remote>
                   <ejb-class>CustomerBean</ejb-class>
                   <persistence-type>Bean</persistence-type>
                   <prim-key-class>CustomerPK</prim-key-class>
                   <reentrant>False</reentrant>
                   <resource-ref>
              <res-ref-name>jdbc/DeveloperPool</res-ref-name>
              <res-type>javax.sql.DataSource</res-type>
              <res-auth>Container</res-auth>
              </resource-ref>
              </entity>
              </enterprise-beans>
              <assembly-descriptor>
              <container-transaction>
                   <method>
                   <ejb-name>Customer</ejb-name>
                   <method-intf>Remote</method-intf>
                   <method-name>*</method-name>
                   </method>
                   <trans-attribute>Required</trans-attribute>
              </container-transaction>
              </assembly-descriptor>
              </ejb-jar>
              "Cameron Purdy" <[email protected]> wrote:
              >Are you using CMT? Have you marked the methods as REQUIRED?
              >
              >Peace,
              >
              >--
              >Cameron Purdy
              >Tangosol, Inc.
              >http://www.tangosol.com
              >+1.617.623.5782
              >WebLogic Consulting Available
              >
              >
              >"Justin Jose" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >> Hello,
              >>
              >> I have created 2 beans one is a Stateless Session and the other a Bean
              >Managed Entity Bean. The SS Bean has methods to retrieve an Oracle
              >Connection from a DataSource defined connection pool, and to close a
              >connection. The entity bean I have created is responsible for insterting a
              >new record into one of the tables in my database.
              >> I have a client app that calls the ejbCreate method on the entity bean at
              >which point the Entity EJB takes control, gets a valid connection from the
              >SS EJB, runs a simple working SQL SELECT statement (obtaining correct
              >values), and then attempts to perform an insert into a table using a
              >prepared statement. My problem is that the application runs fine without
              >any errors and all calls are made and all calls seem to be working fine. I
              >have checked to make sure that the Datasource I am using is AutoCommit=
              >false and it is and there are no exceptions being thrown in my EJB's but yet
              >it appears as though the SQL statements executeUpdate() command is not being
              >committed as their is no rows created in the database. Does anyone know
              >what I may be doing wrong. I have all ACL parameters set up correctly and
              >as I stated before the entire app runs without errors and I do have a SELECT
              >statment that is working properly within the same method as the INSERT
              >statement which is not!!! Please send any suggestions!!
              >>
              >> Justin
              >
              >
              

  • Distributed transactions/jdbc problem WL60

    Hi
              Our company has aworking application running on WLS5.1sp9.
              Im in the process of migrating it to WL6.0sp2.
              Our domain has 2 clusters each running 2 servers:
              1) servlet engines (handling http requests from clients, running servlets
              and jsp's)
              2) ejb containers (runnigour entities and session beans, working with Oracle
              8i database using connection pool and TxDataSource)
              The scenario:
              - a client request invokes a servlet on one of the servlet engines.
              - the servlet opens a jndi context to one of the ejb containers
              - the servlet open a transaction on a UserTransaction stub on that ejb.
              - then the servlet calls an entity bean using a home interface looked up
              using the same context.
              - the entity bean uses DataSource lookup in its own servers jndi to rerieve
              a connection.
              and then i get the following exception:
              java.sql.SQLException: No default driver for database type:
              jdbc:weblogic:jts
              at
              weblogic.jdbcbase.t3.Driver.seeIfWeNeedToInferDriverNameAndUrlFrom(Driver.ja
              va:456)
              at weblogic.jdbcbase.t3.Driver.getAllPropsFrom(Driver.java:255)
              at weblogic.jdbcbase.t3.Driver.connect(Driver.java:75)
              at weblogic.jdbcbase.jts.Driver.createRemoteConnection(Driver.java:199)
              at weblogic.jdbcbase.jts.Driver.connect(Driver.java:134)
              at
              weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java
              :44)
              at com.unisfair.util.DBHelper.getConnection(DBHelper.java:43)
              the transaction toString() gives:
              transaction=(IdHash=7541556,Name = [EJB
              UserBeanImpl.generateSessionSuffix()],Xid=2:b53da78d3c1badbb,Status=Active,n
              umRepliesOwedMe=0,numRepliesOwedOthers=1,seconds since begin=0,seconds
              left=30,activeThread=Thread[ExecuteThread: '8' for queue: 'default',5,Thread
              Group for Queue:
              'default'],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=new,assig
              ned=none),SCInfo[ejb2]=(state=active),SCInfo[servlet2]=(state=active),SCInfo
              [ejb1]=(state=active),properties=({weblogic.transaction.name=[EJB
              UserBeanImpl.generateSessionSuffix()], weblogic.jdbc=t3://10.0.0.31:7007}))
              However the error happens on the other ejb server 10.0.0.33:7007
              It seems that the jts driver tries to get a remote connection on the server
              that coordinates the transaction but uses the deprecated t3 driver.
              I hope someone can help us since this problem is a good enough reason for us
              not moving on to WL6.0 we also looked at WL6.1 Beta and theres nothing new
              about it either.
              thanks
              Dror Last
              Senior Software Engineer
              Unisfair Inc.
              12 Yad Haruzim St. Tel Aviv 67778 Israel
              Tel: +972-3-5373738 Ext. 243
              Fax: +972-3-5373731
              GSM: +972-55-723710
              mailto:[email protected]
              http://www.unisfair.com/
              

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by JDBC_TX ():
    In the readme file of Oracle JDBC drivers 8.1.6.0.1 (http://technet.oracle.com/software/tech/java/sqlj_jdbc/files/Readme_01.txt)
    it mentioned that it supports "distributed transactions".
    As I understand, JDBC transaction is connection based and uses Oracle internal transaction manager. In order to do "distributed transactions", I must have at least two connections open at the same time each to its own database instance. How does the two connections coordinate the transactions? I thought in order to support "distributed transactions", one has to build a higher layer to encapsulate the two connections and therefore coordinate the distributed transactions. Any examples will be welcome.<HR></BLOCKQUOTE>
    The two branches of the transaction are coordinated using 2-phase commit.
    For samples look under
    $ORACLE_HOME/jdbc/demo/samples/oci8/jdbc20-samples/
    null

  • F-32 Transaction BDC Problem

    Hi All,
           I am following the below procedure to populate the transaction F-32 using BDC but I have a small doubt:
    1) I go to F-32 Transaction code populate the required fields on that and press F5
    2) It takes to second screen which has three fields as Field in which I am populating BELNR, second field is Lower Limit field which has a value combination of year document type document number, third field is left blank.
           Now I need to Clear Only part of the second field say for example year part.
          How can I do that? Has anyone faced this kind of problem if so Please reply back.
    Thanks & Regards,
    Joseph Reddy.
    Message was edited by: Joseph Reddy Yeruva

    Hi Rob,
           This is how the code is written
          PERFORM bdc_dynpro      USING 'SAPMF05A' '0131'.
          PERFORM bdc_field       USING:
                               'BDC_CURSOR'  'BKPF-WAERS',
                               'BDC_OKCODE'  '=SLB',
                               'RF05A-AGKON' p_kunnr,
                               'BKPF-BUDAT'  lv_date,
                               'BKPF-MONAT'  '11',
                               'BKPF-BUKRS'  p_bukrs,
                               'BKPF-WAERS'  gv_waers.
                               'RF05A-XNOPS' c_x.
          perform bdc_dynpro      using 'SAPMF05A' '0733'.
          perform bdc_field       using 'BDC_CURSOR' 'RF05A-                                     SEL01(01)'.
          perform bdc_field       using 'BDC_OKCODE'
                                        '=PA'.
          perform bdc_field       using 'RF05A-FELDN(01)'
                                          'BELNR'.
          perform bdc_field       using 'RF05A-FELDN(02)'
                                        record-FELDN_02_008.
          perform bdc_field       using 'RF05A-FELDN(03)'
                                        record-FELDN_03_009.
          perform bdc_field       using 'RF05A-FELDN(04)'
                                        record-FELDN_04_010.
          perform bdc_field       using 'RF05A-SEL01(01)'
                                         lv_belnr.
          perform bdc_field       using 'RF05A-SEL01(02)'
                                        record-SEL01_02_012.
          perform bdc_field       using 'RF05A-SEL01(03)'
                                        record-SEL01_03_013.
          perform bdc_field       using 'RF05A-SEL01(04)'
                                        record-SEL01_04_014.
          perform bdc_dynpro      using 'SAPDF05X' '3100'.
          perform bdc_field       using 'BDC_OKCODE'
                                        '=OMX'.
          perform bdc_field       using 'BDC_CURSOR'
                                        'DF05B-PSSKT(01)'.
          perform bdc_field       using 'RF05A-ABPOS'
                                          '001'.
          perform bdc_dynpro      using 'SAPDF05X' '3100'.
          perform bdc_field       using 'BDC_OKCODE'
                                        '=Z+'.
          perform bdc_field       using 'BDC_CURSOR'
                                        'DF05B-PSSKT(01)'.
          perform bdc_field       using 'RF05A-ABPOS'
                                         '001'.
          perform bdc_dynpro      using 'SAPDF05X' '3100'.
          perform bdc_field       using 'BDC_OKCODE'
                                        '=BU'.
          perform bdc_field       using 'BDC_CURSOR'
                                        'DF05B-PSSKT(01)'.
          perform bdc_field       using 'RF05A-ABPOS'
                                         '001'.
         CALL TRANSACTION 'F-32' USING gt_BDCDATA
                                 MODE   'A' "gv_mode
                                 UPDATE gv_updat.
    Rgds,
    Joseph

  • DB2 Transaction log Problem after set db manuell to Rollforward

    Hello,
    I have a problem when set the db2 manuell in rollforward mode. After I set the command db2rfpen ON E35 my database (E35) is in rollforward mode.
    Now I can see with command "db2 rollforward db E35 query status" the Last committed transaction
    but the timestamp of the Last committed transaction is 2106-02-07-06.28.15.000000 UTC
    but we do not have year 2106!!
    did someone have similar issue or a solution for my problem??
    Is it possible to manuell update the table via SQL? But I dont know which table i should update..
    Thanks in advanced.
    Robin

    Hi,
    following output of db2 get snapshot for all databases because db2 get snapshot for database E35 does not work..
    there I think the timestamp is also ok. Thanks for your help!
    regards
    Robin
                  Database Snapshot
    Database name                              = E35
    Database path                              = /db2/E35/db2e35/NODE0000/SQL00001/MEMBER0000/
    Input database alias                       =
    Database status                            = Active
    Catalog database partition number          = 0
    Catalog network node name                  = srvnetapp07
    Operating system running at database server= LINUXAMD64
    Location of the database                   = Local
    First database connect timestamp           = 08/11/2014 12:16:58.594371
    Last reset timestamp                       =
    Last backup timestamp                      = 08/08/2014 09:57:42.000000
    Snapshot timestamp                         = 08/11/2014 12:17:46.494342
    Number of automatic storage paths          = 4
    Automatic storage path                     = /db2/E35/sapdata1
          Node number                          = 0
          State                                = In Use
          File system ID                       = 64782
          Storage path free space (bytes)      = 23376351232
          File system used space (bytes)       = 3045990400
          File system total space (bytes)      = 26422341632
    Automatic storage path                     = /db2/E35/sapdata2
          Node number                          = 0
          State                                = In Use
          File system ID                       = 64783
          Storage path free space (bytes)      = 23376351232
          File system used space (bytes)       = 3045990400
          File system total space (bytes)      = 26422341632
    Automatic storage path                     = /db2/E35/sapdata3
          Node number                          = 0
          State                                = In Use
          File system ID                       = 64784
          Storage path free space (bytes)      = 23376351232
          File system used space (bytes)       = 3045990400
          File system total space (bytes)      = 26422341632
    Automatic storage path                     = /db2/E35/sapdata4
          Node number                          = 0
          State                                = In Use
          File system ID                       = 64785
          Storage path free space (bytes)      = 23376351232
          File system used space (bytes)       = 3045990400
          File system total space (bytes)      = 26422341632
    High water mark for connections            = 13
    Application connects                       = 9
    Secondary connects total                   = 11
    Applications connected currently           = 1
    Appls. executing in db manager currently   = 0
    Agents associated with applications        = 11
    Maximum agents associated with applications= 13
    Maximum coordinating agents                = 13
    Number of Threshold Violations             = 0
    Locks held currently                       = 29
    Lock waits                                 = 2
    Time database waited on locks (ms)         = 56
    Lock list memory in use (Bytes)            = 77568
    Deadlocks detected                         = 0
    Lock escalations                           = 0
    Exclusive lock escalations                 = 0
    Agents currently waiting on locks          = 0
    Lock Timeouts                              = 0
    Number of indoubt transactions             = 0
    Total Private Sort heap allocated          = 0
    Total Shared Sort heap allocated           = 6
    Shared Sort heap high water mark           = 245
    Post threshold sorts (shared memory)       = 0
    Total sorts                                = 2
    Total sort time (ms)                       = 2
    Sort overflows                             = 0
    Active sorts                               = 0
    Buffer pool data logical reads             = 68507
    Buffer pool data physical reads            = 1312
    Buffer pool temporary data logical reads   = 0
    Buffer pool temporary data physical reads  = 0
    Asynchronous pool data page reads          = 899
    Buffer pool data writes                    = 0
    Asynchronous pool data page writes         = 0
    Buffer pool index logical reads            = 52871
    Buffer pool index physical reads           = 449
    Buffer pool temporary index logical reads  = 0
    Buffer pool temporary index physical reads = 0
    Asynchronous pool index page reads         = 0
    Buffer pool index writes                   = 0
    Asynchronous pool index page writes        = 0
    Buffer pool xda logical reads              = 0
    Buffer pool xda physical reads             = 0
    Buffer pool temporary xda logical reads    = 0
    Buffer pool temporary xda physical reads   = 0
    Buffer pool xda writes                     = 0
    Asynchronous pool xda page reads           = 0
    Asynchronous pool xda page writes          = 0
    Total buffer pool read time (milliseconds) = 4912
    Total buffer pool write time (milliseconds)= 0
    Total elapsed asynchronous read time       = 3219
    Total elapsed asynchronous write time      = 0
    Asynchronous data read requests            = 454
    Asynchronous index read requests           = 0
    Asynchronous xda read requests             = 0
    No victim buffers available                = 0
    LSN Gap cleaner triggers                   = 0
    Dirty page steal cleaner triggers          = 0
    Dirty page threshold cleaner triggers      = 0
    Time waited for prefetch (ms)              = 982
    Unread prefetch pages                      = 0
    Direct reads                               = 986
    Direct writes                              = 2
    Direct read requests                       = 77
    Direct write requests                      = 1
    Direct reads elapsed time (ms)             = 243
    Direct write elapsed time (ms)             = 0
    Database files closed                      = 0
    Host execution elapsed time                = 5.785568
    Commit statements attempted                = 16
    Rollback statements attempted              = 2
    Dynamic statements attempted               = 6950
    Static statements attempted                = 23
    Failed statement operations                = 0
    Select SQL statements executed             = 6936
    Xquery statements executed                 = 0
    Update/Insert/Delete statements executed   = 6
    DDL statements executed                    = 0
    Inactive stmt history memory usage (bytes) = 0
    Internal automatic rebinds                 = 0
    Internal rows deleted                      = 0
    Internal rows inserted                     = 0
    Internal rows updated                      = 0
    Internal commits                           = 21
    Internal rollbacks                         = 0
    Internal rollbacks due to deadlock         = 0
    Number of MDC table blocks pending cleanup = 0
    Rows deleted                               = 0
    Rows inserted                              = 0
    Rows updated                               = 13838
    Rows selected                              = 13897
    Rows read                                  = 141752
    Binds/precompiles attempted                = 0
    Log space available to the database (Bytes)= 333797877
    Log space used by the database (Bytes)     = 26523
    Maximum secondary log space used (Bytes)   = 0
    Maximum total log space used (Bytes)       = 37070
    Secondary logs allocated currently         = 0
    Log pages read                             = 0
    Log read time (sec.ns)                     = 0.000000000
    Log pages written                          = 13
    Log write time (sec.ns)                    = 0.006250000
    Number write log IOs                       = 9
    Number read log IOs                        = 0
    Number partial page log IOs                = 7
    Number log buffer full                     = 0
    Log data found in buffer                   = 0
    Log to be redone for recovery (Bytes)      = 26523
    Log accounted for by dirty pages (Bytes)   = 26523
    Node number                                = 0
    File number of first active log            = 90
    File number of last active log             = 94
    File number of current active log          = 90
    File number of log being archived          = Not applicable
    Package cache lookups                      = 6955
    Package cache inserts                      = 20
    Package cache overflows                    = 0
    Package cache high water mark (Bytes)      = 1026593
    Application section lookups                = 20824
    Application section inserts                = 29
    Catalog cache lookups                      = 740
    Catalog cache inserts                      = 55
    Catalog cache overflows                    = 0
    Catalog cache high water mark              = 429098
    Catalog cache statistics size              = 0
    Workspace Information
    Number of hash joins                       = 4
    Number of hash loops                       = 0
    Number of hash join overflows              = 0
    Number of small hash join overflows        = 0
    Post threshold hash joins (shared memory)  = 0
    Active hash joins                          = 0
    Number of OLAP functions                   = 0
    Number of OLAP function overflows          = 0
    Active OLAP functions                      = 0
    Statistic fabrications                          = 0
    Synchronous runstats                            = 0
    Asynchronous runstats                           = 0
    Total statistic fabrication time (milliseconds) = 0
    Total synchronous runstats time (milliseconds)  = 0
    Memory usage for database:
      Node number                                  = 0
        Memory Pool Type                           = Backup/Restore/Util Heap
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 204800000
      Node number                                  = 0
        Memory Pool Type                           = Package Cache Heap
           Current size (bytes)                    = 1179648
           High water mark (bytes)                 = 1179648
           Configured size (bytes)                 = 472317952
      Node number                                  = 0
        Memory Pool Type                           = Other Memory
           Current size (bytes)                    = 196608
           High water mark (bytes)                 = 196608
           Configured size (bytes)                 = 20971520
      Node number                                  = 0
        Memory Pool Type                           = Catalog Cache Heap
           Current size (bytes)                    = 524288
           High water mark (bytes)                 = 524288
           Configured size (bytes)                 = 10485760
      Node number                                  = 0
        Memory Pool Type                           = Buffer Pool Heap
           Secondary ID                            = 1
           Current size (bytes)                    = 494010368
           High water mark (bytes)                 = 494010368
           Configured size (bytes)                 = 494010368
      Node number                                  = 0
        Memory Pool Type                           = Buffer Pool Heap
           Secondary ID                            = System 32k buffer pool
           Current size (bytes)                    = 1835008
           High water mark (bytes)                 = 1835008
           Configured size (bytes)                 = 1835008
      Node number                                  = 0
        Memory Pool Type                           = Buffer Pool Heap
           Secondary ID                            = System 16k buffer pool
           Current size (bytes)                    = 1572864
           High water mark (bytes)                 = 1572864
           Configured size (bytes)                 = 1572864
      Node number                                  = 0
        Memory Pool Type                           = Buffer Pool Heap
           Secondary ID                            = System 8k buffer pool
           Current size (bytes)                    = 1441792
           High water mark (bytes)                 = 1441792
           Configured size (bytes)                 = 1441792
      Node number                                  = 0
        Memory Pool Type                           = Buffer Pool Heap
           Secondary ID                            = System 4k buffer pool
           Current size (bytes)                    = 1376256
           High water mark (bytes)                 = 1376256
           Configured size (bytes)                 = 1376256
      Node number                                  = 0
        Memory Pool Type                           = Shared Sort Heap
           Current size (bytes)                    = 2359296
           High water mark (bytes)                 = 3932160
           Configured size (bytes)                 = 40435712
      Node number                                  = 0
        Memory Pool Type                           = Lock Manager Heap
           Current size (bytes)                    = 159645696
           High water mark (bytes)                 = 159645696
           Configured size (bytes)                 = 159711232
      Node number                                  = 0
        Memory Pool Type                           = Database Heap
           Current size (bytes)                    = 87687168
           High water mark (bytes)                 = 87687168
           Configured size (bytes)                 = 119472128
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 107
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 106
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 105
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 104
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 103
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 102
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 101
           Current size (bytes)                    = 196608
           High water mark (bytes)                 = 196608
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 100
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 99
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 98
           Current size (bytes)                    = 65536
           High water mark (bytes)                 = 65536
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Application Heap
           Secondary ID                            = 97
           Current size (bytes)                    = 131072
           High water mark (bytes)                 = 131072
           Configured size (bytes)                 = 1048576
      Node number                                  = 0
        Memory Pool Type                           = Applications Shared Heap
           Current size (bytes)                    = 458752
           High water mark (bytes)                 = 458752
           Configured size (bytes)                 = 81920000

  • Local Class Transaction Code Problem

    Hi friends,
            I have created report program using local class. I have also used selection screen to get input from user. I have created oops transaction code (using se93) for that program.
    Problem is selection screen is not displayed when program is executed using tcode.
    I think logically it not possibel to display the selection screen. Is it true?. OR
    What Should I do?.
    Next Question is, I have also created  global class from my report program. But i cant able to find my class in se24.
    I have done following things.
      1) imported a local class from my report prg. ( In pop up screen that class icon(circle shaped icon) shown in gray colour)
      2) Assigend New class name starting with 'Z'.
      3) Selected overwrite existing class checkbok.
      4) selected import icon.
          'Import Completed Succesfully' message appeared. Still i am not able to find my class.
         Kindly provide answers.
    Thanks In Advance,
    S.Senthil

    Hi senthil kumar ,
    u can display the selection screen and secondly try to create your report in module pool type,
    and when also check if the class is activated or not and then check in se24,
    if still the issue remains
    let me know...
    thanks
    ravi

  • RRI report transfer to ERP transaction VA03  problem

    Hi all,
    I have following problem when I tried to jump to VA03 transaction from Query Designer report.
    I created sender/receiver assignment with following options
    Sender : Query Designer report
    Receiver : VA03 transaction
    When i click on go to VA03 it's displaying error " Java communication error: Error when opening an RFC connection" after it's displaying below error.
    Is it related to EP and R/3 connnection problem or else?
    Error:
    SAP Web Application Server window is displaying and asking for logon details.
    The URL http://ttcsap04:8001/sap/bc/gui/sap/its/webgui was not called due to an error.
    Note
    The following error text was processed in the system TCQ : System error
    The error occurred on the application server ttcsap04_TCQ_01 and in the work process 0 .
    The termination type was: ABORT_MESSAGE_STATE
    The ABAP call stack was:
    SYSTEM-EXIT of program SAPLRSRR_WEB
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system TCQ in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server ttcsap04_TCQ_01 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server ttcsap04_TCQ_01 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 500 -u: USER -l: E -s: TCQ -i: ttcsap04_TCQ_01 -w: 0 -d: 20090107 -t: 041216 -v: ABORT_MESSAGE_STATE -e: System error
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Thanks in Advance,
    Venky

    Hi
    You need to establish the connection between EP/ERP/BI-BEx.
    More of a network / Basis/ EP Issue Raise a ticket with them for the help.

  • IDOC's in TRFC ("Transaction recorded") Problem

    Dear Gurus,
    BW System = SAP NetWeaver 7.40 , Sap_Basis = 7.40 - 007 , Database = Hana , 1.00.80.00.391861 , Kernel = 741 , Sup.Pck.Lvl = 31
    ERP System = ERP 6 EHP 4 , Sap_Basis = 701 - 0011 , Database = Oracle , 11.2.0.4.0 , Kernel = 721 , Sup.Pck.Lvl = 401
    The IDOCs we send are sitting in TRFC queues, they are not sent to the target system. I checked all the ALE settings, they are fine. The processing mode is "Immediate".
    When I go to SM58 I will find the entry for the transaction with status "Transaction Recorded". If I select the entry and press F6 (Execute LUW) the IDOC is sent to the target system and the queue becomes empty.
    Also " 530997 - tRFC calls are not processed in transaction SM58" job is scheduled for 2 min period but same result !
    What is the problem ? It should be goes automatically.
    Best Regards

    Dear Kumar,
    We have enough DIALOG WP defined, now we will check 1280898 note and see what happens.
    Best Regards

  • Transaction Launcher problems: Significance of IC_LTX

    Hi all,
    We are on CRM 5.0 and ECC 6.0.
    I am facing some problems using the transaction launcher when I use the Webgui service.
    I looked into the note 888931 which asks us to use the Webgui service and the below URLs for the logical system.
    http://<host>:<port>/scripts/wgate/webgui/!?transaction=IC_LTX&okcode=ICEXECUTE
    OR
    http://<host>:<port>/sap/bc/gui/sap/its/webgui/!?transaction=IC_LTX&okcode=ICEXECUTE
    The first one does not work in our system and 2nd one returns a grid kind of blank screen although I configured the transaction launcher to pull the transaction 'BP'.
    Can anyone please let me know what could be the problem? and also what is the significance/use of the Transaction/function group IC_LTX ?
    Best Regards,
    Nag

    Hello Glenn,
    Thanks for your reply.
    I've tried with passing the parameters also but still that does not work.
    But if I change the URL to use the CRM_CIC_RABOX it works fine. But we have some display issues with this.
    So we are trying with WEBGUI service as per the note 888931.
    Regards,
    Nag

  • ITS webgui transaction width problem

    we are getting no splash screen and the webgui (HTML) launched from portal -
    we have problem when we launch a transaction from portal.
    we see the transaction inside the webgui is shorten (reduced width) but when I click on the transaction directly in webgui - transaction displayed properly
    any ideas

    Hi Weatboy,
    I would like to know the SAP_BASIS package level (SAPKBxxxxx format) and the kernel release/patch level.
    Anyway, you can check if SAP note 1411321 helps.
    Regards,
    Cristiano

  • Delivery challan print preview for transaction j1if01 problem

    hi , i have problem with print preview of delivery challan. after creating it from j1if01 im unable to get a print preview of it
    as i dont find any tab or button for print preview .
    plz guide me how can i  get an output . also plz give form name for it . thanks !!

    In u2022     SPRO > Logistics - General > Tax on Goods Movements > India > Business Transactions > Subcontracting > Subcontracting Attributes maintain the Output type. Other attributes are as under fyi
    Excise Group         XX
    Excise TT            57FC
    Subtransaction Type  01
    Subtran Type Text   57FC CHALLAN
    Subc. Period        180
    Rate-subcontracting
    Mvt Grp Issues      0001
    Mvt Grp Receipt     0002
    Filter Non exise    X
    EI Items            10
    No. range no.       01
    ***. Val. /Exc Inv
    Subcon Output Type  J1IF

  • Transactional Messaging Problem

    Hi,
    The problem I am facing is, I have multiple publishers that can send the same type of messages to the topics and mutiple subscribers are receiving the messages (many-to-many). Suppose the publisher makes changes to a database row, and then send a message to the topic reflecting that change. At the same time, another publisher makes changes to the same database row and then send a message to the topic. If there is no transaction involved on the publisher side, it is possible that the second publisher's message arrives at subscriber side first. This could potentially cause trouble on the subscriber side. How can I guarantee the order of the messages published into the topic? In a situation where message service is down and my publisher has the ability to resend the message after service is back alive, the message it is sending will obviously out of order. So what is the best approach to this kind of problem? How can I ensure the right order delivered to the other end of message pipe? Thanks.

    Hi,
    You are right by saying that updating your database and publishing your messages within the scope of a transaction will solve your problem. But however, you need to use the right database transactional model. The best one to go for is the strict serialisation model that will guarantee you that write operations are strictly done sequentially and then that your messages are published in the right order. Note that this model has a certain degree of overhead that you may be able to relax so that to improve performance.
    On the messaging side you will need to use a XA compliant JMS provider as well as a transaction manager. You can achieve that by using an app server or you can use a MDS (message driven service) container. For example, Arjuna provides such a container (http://www.arjuna.com/products/arjunams/tutorials/mds/index.html) that is roughly speaking a light weight MDB container that provides you with concurrent message processing as well as container managed transactions. The MDS container comes with a full JTA compliant transaction manager.
    Note that in the event of a database or a JMS bus failure you will rollback your transaction and take the necessary action that could simply be re-trying later or waiting for the faulty resource to reboot.
    Hope this helps,
    Arnaud
    www.arjuna.com

Maybe you are looking for