Auto commit in BAPI

Hi All,
How do we find the BAPI have auto commit or not, is it TEST RUN parameter, but all the BAPI doesn't have this parameters.
Thanks.

Typically you have parameters like TEST_RUN (as in BAPI_PO_CHANGE) or I_COMMIT (in ME_CCP_TPO_PRICE_CHANGE).
There is no general rule here and also many BAPIs WON'T have any COMMIT inside them. They need to be called and committed in wrapper function/program.

Similar Messages

Some BAPIs are auto commit and some are not. what is the reason?

Hi all,
currently i am working on BAPI.I found that some BAPIs are auto commit and some are not. can anybody tell me what is the reason.

hi,
one option to find the difference is you have to look for parameters like test run or commit .
If the function module doesn't have them, then it means you have to use BAPI_TRANSACTION_COMMIT or BAPI_TRANSACTION_ROLLBACK based on the success or failure.

Auto commit in BAPI_MATERIAL_SAVEDATA

hi
i want to know whether there is an auto commit in this method BAPI_MATERIAL_SAVEDATA or do we need to explicitly commit
Correct answer will be suitably rewarded

Hi Baldeep,
I dont think there is any parameter in this method which will let u know whether this method does an auto commit or not.
I normally execute the BAPI with the basic required data and check whether it is updating the database tables, and if the tables get updated then there is no need to explicitly commit or rollback, but if it does not update the database tables then I do an explicit commit.
I guess all this has got to do with the difference in creating master data and the transaction data. When ever u are using a bapi to create the master data u dont have to do an explicit commit. But when ur creating a transaction data in the database u have to do an explicit commit.
Thanks
Elan

Auto Commit in Oracle Document Capture

Hi,
I have recently installed and configured Oracle Document Capture 10g as a part of IPM installation. I have configured ODC to Scan, Index and commit to UCM 11g system. Scanning and indexing are going fine without and problem. However, I could not make the commit automatic. Please help me configure an auto-commit, so that I don't have to go to ODC every time and do a manual commit. Or is it possible to auto-commit at all ?
Thank you
Rama

In this case I think the problem is somewhere else. Normally, an indexed batch is committed immediately when you you confirm the message at the end of the last page. For that you don't even need the Commit server configured. Commit server with Indexing is used mainly in use cases, when you want to schedule committing (e.g. to a certain time). I guess the Commit Server is not activated, because the batch is not fully processed. AFAIK, recently released 11g is much better option for small batches.
I'd recommend you to try the Commit Server together with the Import/Recognition Server, which can be fully automated. Maybe this will enable you to understand what the problem with Indexing could be.

Problems with auto commit

Hi All,
I am having some trouble with the auto commit. In the sql work sheet i update a table and then disconnect. It seems to be auto commiting the changes i made.
i went in and unchecked 'Save all when deactivating or Exiting'
Do i need to turn this auto commit off somehere else?
Would it be possible to get prompted to commit when you disconnect?
Thanks
Chris

Yeah. You are up to date. That bug must still exist. Hopefully someone from Oracle is monitoring the thread from OOW and can let you know the status on this. Optionally, you can open a tar (or equiv support request) directly with Oracle.
Eric

BUG: Red Eye Removal on JPGs + Auto commit to XMP

There seems to be a bug in 1.3.1 when using the Red Eye Removal tool on JPGs and auto commit metadata to file option is selected:
Can anyone confirm?
This is what I've written to Adobe in a bug report:
******BUG******
Concise problem statement:
When using "Red Eye Removal Tool" on jpgs and in File->Catalog Settings->Metadata the option "Automatically write changes into XMP" is selected this will end up in a loop reading and writing metadata. The picture is always in status: "checking metadata". "Metadata Date" of file is changing from time to time because Lightroom is always saving metadata to file (modified date of the jpg file itself also changes, so something is written to file).
Steps to reproduce bug:
1. in File->Catalog Settings->Metadata check option "Automatically write changes into XMP"
2. select a JPG picture and go to Develop Module
3. use the Red Eye Removal Tool
Results:
Endless loop by Lightroom trying to save this change into Metadata of JPG file
Expected results:
Either it is not possible to store this change in metadata: then don't touch the file.
Or it is possible, then this needs to be fixed so it is written/read correctly from file.

The red eye tool works by selecting the whole eye not just the pupil. If it still does not work try lightening or darkening the image to gaiain some more colour. If that does not work you can clone form one of the eyes that has worked.
Hope this helps you out.........

Auto commit

I wrote an insert statement in a procedure and calling it by insert-statement in the programming unit. The problem is I want to show on the same form once the data is inserted, but due to some problem exception is comming. so can any one suggest how to auto commit once the data is inserted in the procedure
thanks in advance.

am getting the error no data found trigger failure exception.
i have a form, the trigger in that calls an insert procedure where i insert the values to data and again in the same trigger i pull the data from the table the inserted values in order to display in the same form where i took the input values.
so my problem occurs after inserting, its not fetching the values from the data and it causes the no data found exception
so that is the reason why i want to implement the commit and where to implement that.
thanks in advance

ADF view : auto commit delete operation

I have created a ADF table with add and delete operation. When I perform delete operation it is not committing automatically.
Can you please suggest the way to auto commit the delete operation.
Thanks,
Kiran

User,
please always tell us your jdev version as the solution might depend on it.
There is no auto commit in ADF. You can program it so that after an add or delete the data gets committed but there is nothing done automatically.
if you use a bounded task flow you can drag the operation from the data control onto the task flow and navigate to it after you have done the add or delete operation.
Timo

Oracle.xml.sql.OracleXMLSQLException:Cannot enable auto commit within JTS transaction

Hi All,
OracleXMLSave class in the Oracle XDK is being used to load XML data into an 8170 database. The Java code is running in IBM WebSphere with container-managed transactions. When JTA is enabled with the Merant JDBC driver for Oracle, we get the following error when the XML is loaded:
oracle.xml.sql.OracleXMLSQLException: Cannot enable auto commit within JTS
transaction
     at java.lang.Throwable.fillInStackTrace(Native Method)
     at oracle.xml.sql.dml.OracleXMLSave.saveXML(OracleXMLSave.java:2213)
     at oracle.xml.sql.dml.OracleXMLSave.insertXML(Compiled Code)
This suggests the OracleXMLSave class is not aware of the fact that it is now operating in a JTS transaction where control is managed elsewhere. i.e. should also not attempt to commit or rollback, as this is the responsibility of the container.
Is there a property which needs to set to prevent the above or does the XDK not work with J2EE (JTS) transactions?.
If you have any useful comments, let me know. Testing the above presents me with a number of problems so if this is easily explained , let me know.
Thanks,
Malcolm

Clearly , there does seem to be something a bit odd with the above stack.
<Bug:1917808> mentions OracleXMLSave in context of plsql equivalent : dbms_xmlsave . i.e dbms_xmlsave is a wrapper around OracleXMLSave class.
disabling autocommit on connection as follows should help:
conn = DriverManager.getConnection("connect string","scott","tiger");
conn.setAutoCommit(false);
to disble auto commit and see if this has an effect.
This issue might be <Bug:1497506>. If disabling autocommit does not work then it appears that it could be this issue .
Malcolm
Hi All,
OracleXMLSave class in the Oracle XDK is being used to load XML data into an 8170 database. The Java code is running in IBM WebSphere with container-managed transactions. When JTA is enabled with the Merant JDBC driver for Oracle, we get the following error when the XML is loaded:
oracle.xml.sql.OracleXMLSQLException: Cannot enable auto commit within JTS
transaction
     at java.lang.Throwable.fillInStackTrace(Native Method)
     at oracle.xml.sql.dml.OracleXMLSave.saveXML(OracleXMLSave.java:2213)
     at oracle.xml.sql.dml.OracleXMLSave.insertXML(Compiled Code)
This suggests the OracleXMLSave class is not aware of the fact that it is now operating in a JTS transaction where control is managed elsewhere. i.e. should also not attempt to commit or rollback, as this is the responsibility of the container.
Is there a property which needs to set to prevent the above or does the XDK not work with J2EE (JTS) transactions?.
If you have any useful comments, let me know. Testing the above presents me with a number of problems so if this is easily explained , let me know.
Thanks,
Malcolm

Auto commit in apex

Hello Sir,
how can i set auto commit on/off using apex in application builder, auto commit is there in sql command but not in application builder,it is possible to set auto commit using coding in apex processes or PL/SQL Block.
please help me.
Thanks in Advance,
Regards,
Jack R.

Hi Varad,
Thanks for your quick reply,
I want to manually handle commit and rollback on DML.
can you explain about a stateless transaction model and span requests in apex?
Thanks & Regards,
Jack R.

Cannot enable auto commit within JTS using websphere

i suddenly encountered some exceptions like this yet the process seems to be ok. i am pretty new to websphere, help please:
java.lang.IllegalStateException: Cannot enable auto commit within JTS transaction
     at com.ibm.ejs.cm.pool.ConnectO.setAutoCommit(ConnectO.java:2085)
     at com.ibm.ejs.cm.proxy.ConnectionProxy.setAutoCommit(ConnectionProxy.java:594)

I'm setting autoCommit to false in some of my code and it works. Here is the example:
//This code works for the Oracle Thin Driver
               conn.setAutoCommit(false); // <- required!
             // initialize LOB reference
             GDate curDate = new GDate();
             ps = conn.prepareStatement("insert into Calculated_Rate_Import values (empty_clob(), ?)");
             //conn.createStatement().executeUpdate("insert into Calculated_Rate_Import values (empty_clob(), TO_DATE('" + GDate.getSafeSqlDate(curDate) + "'))");
             ps.setTimestamp(1, GDate.getSafeTimestamp(curDate));
             ps.executeUpdate();
             ps = conn.prepareStatement("select Calculated_Rate_Import from Calculated_Rate_Import where Import_Date = ? for update");
             ps.setTimestamp(1, GDate.getSafeTimestamp(curDate));
               results = ps.executeQuery();
             results.next();
             // get lob reference from write lock
                 //oracle.sql.CLOB clob = ((oracle.jdbc.driver.OracleResultSet)results).getCLOB(1);
               oracle.sql.CLOB clob = (oracle.sql.CLOB)results.getClob("Calculated_Rate_Import");
             // create statement for update
             ps = conn.prepareStatement("update Calculated_Rate_Import set Calculated_Rate_Import = ? where Import_Date = ?");
             // stream data into lob
             java.io.OutputStream os = ((oracle.sql.CLOB)clob).getAsciiOutputStream();
             try{
                  os.write(fileContents.getBytes());
                       os.close();
             }catch(IOException e){
                  e.printStackTrace();
             // execute update
             //((oracle.jdbc.driver.OraclePreparedStatement)ps3).setCLOB(1, clob);
             ps.setClob(1, clob);
             ps.setTimestamp(2, GDate.getSafeTimestamp(curDate));
             ps.executeUpdate();
             // close lock
             results.close();
             conn.commit();
             //finished inserting CLOB
             //set the auto commit back to true, required!
               conn.setAutoCommit(true);

Auto-Commit and Pooled JDBC Connections

Forum Members,
If I am using Oracle Pooled JDBC Connections in the OC4J container is auto-commit set to "true" by default?
If I set auto-commit to "false" and then close the logical connection, when that connection is handed out again on a later call to getConnection(), is auto-commit automatically set back to "true"?
Thanks,
Richard

Richard,
Pardon me if I am stating the obvious, but you could test that in your code by invoking the getAutoCommit() method in interface java.sql.Connection.
My experience (with OC4J stand-alone versions up to -- and including -- 10.1.2) is that the behaviour depends on which data source you have configured. For example, if you have defined an "ejb-location" attribute in your "data-sources.xml" file, and you use that as your JNDI lookup for your data source, then OC4J handles transactions and you shouldn't deal with "auto-commit" at all. See the following post for more details:
Re: OC4J 10.1.3 Preview 4 - Global transaction active
But if you have defined a "location" attribute and use that, then you do need to handle transactions explicitly.
Hope this helps.
Good Luck,
Avi.

Could not turn on auto-commit in an active global transaction

Why and when does toplink throw this exception
09/09/28 17:50:58 Caused by: java.sql.SQLException: could not turn on auto-commit in an active global transaction
09/09/28 17:50:58 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
09/09/28 17:50:58 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
09/09/28 17:50:58 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
09/09/28 17:50:58 at oracle.jdbc.driver.PhysicalConnection.disallowGlobalTxnMode(PhysicalConnection.java:4045)
09/09/28 17:50:58 at oracle.jdbc.driver.PhysicalConnection.setAutoCommit(PhysicalConnection.java:1343)
09/09/28 17:50:58 at oracle.jdbc.OracleConnectionWrapper.setAutoCommit(OracleConnectionWrapper.java:107)
09/09/28 17:50:58 at oracle.oc4j.sql.spi.ManagedConnectionImpl.setAutoCommit(ManagedConnectionImpl.java:572)
09/09/28 17:50:58 at oracle.oc4j.sql.spi.ManagedConnectionImpl.initForUse(ManagedConnectionImpl.java:167)
09/09/28 17:50:58 at oracle.oc4j.sql.spi.ManagedConnectionImpl.<init>(ManagedConnectionImpl.java:106)
09/09/28 17:50:58 at oracle.oc4j.sql.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:171)
09/09/28 17:50:58 at com.evermind.server.connector.ApplicationConnectionManager.createManagedConnection(ApplicationConnectionManager.java:1398)
09/09/28 17:50:58 at oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnectionFromFactory(ConnectionPoolImpl.java:327)
09/09/28 17:50:58 at oracle.j2ee.connector.ConnectionPoolImpl.access$800(ConnectionPoolImpl.java:98)
09/09/28 17:50:58 at oracle.j2ee.connector.ConnectionPoolImpl$NonePoolingScheme.getManagedConnection(ConnectionPoolImpl.java:1211)
09/09/28 17:50:58 at oracle.j2ee.connector.ConnectionPoolImpl.getManagedConnection(ConnectionPoolImpl.java:785)
09/09/28 17:50:58 at oracle.oc4j.sql.ConnectionPoolImpl.getManagedConnection(ConnectionPoolImpl.java:45)
09/09/28 17:50:58 at com.evermind.server.connector.ApplicationConnectionManager.getConnectionFromPool(ApplicationConnectionManager.java:1596)
09/09/28 17:50:58 at com.evermind.server.connector.ApplicationConnectionManager.acquireConnectionContext(ApplicationConnectionManager.java:1541)
09/09/28 17:50:58 at com.evermind.server.connector.ApplicationConnectionManager.allocateConnection(ApplicationConnectionManager.java:1486)
09/09/28 17:50:58 at oracle.j2ee.connector.OracleConnectionManager.unprivileged_allocateConnection(OracleConnectionManager.java:238)
09/09/28 17:50:58 at oracle.j2ee.connector.OracleConnectionManager.allocateConnection(OracleConnectionManager.java:192)
09/09/28 17:50:58 at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:272)
09/09/28 17:50:58 at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:200)
09/09/28 17:50:58 at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:142)
09/09/28 17:50:58 at oracle.oc4j.sql.ManagedDataSource.getConnection(ManagedDataSource.java:127)
09/09/28 17:50:58 at oracle.toplink.essentials.jndi.JNDIConnector.connect(JNDIConnector.java:145)
Thanks,
ND

Hello,
As you can tell from the stack trace, TopLink is not throwing the exception, the connection is when TopLink is attempting to get a connection from the datasource. getConnection should not be throwing this exception, so it is likely a datasource configuration issue or a problem in the driver you are using. How is the datasource configured, what is the version of Oc4J and the driver you are using, and can you try using a different driver version?
Best Regards,
Chris

How to turn of auto commit for the jdeveloper worksheet?

Hi,
is it possible to turn off the auto commit for the jdeveloper worksheet?
thx, alex

Hi Alex,
No, this functionality is not available, there are some existing Enhancement Request which request this functionality.
Regards,
Lisa Sherriff
JDev QA

Auto-commit occurs even when preference disabled

In the menu under TOOLS > PREFERENCES > Database Connections, there is an option that says "Autocommit in SQL Worksheet". It seems that sometimes DML statements are committed immediately even if this option is turned off.
I am experiencing this problem on SQL Developer Version 1.0.0.15.57 running on Windows 2000 (5.00.2195 Service Pack 4). Not sure if it matters, but the database is 10.2.0.1 Enterprise Edition running on LINUX RHAS 3.0 Update 4.
Is this a known bug? Is it fixed in future releases?
Thanks,
Burt

Auto-commit preference for worksheet, if turned on, would issue commit immediately after you run DML from worksheet.
If it's turned off and you still see changes data being commit, I think it's possible only in another scenario where you have Auto-commit preference for worksheet turned off, issue DML from worksheet and subsequently do a commit in data grid.
Commit button is present in both data grid and in sql worksheet, and sql developer uses only one connection/session. So, a commit in grid is going to commit your worksheet issued DMLs.
Grid data is not commited that way unless you have grid's auto-commit preference on (that preference is in ObjectViewer preference node).
HTH
-Raghu

Auto commit in BAPI

Similar Messages

Maybe you are looking for