Long Running VF11: Cancel Invoice

We have a table used for GL's that was converted from pooled to transaparent in 2003. There were tools and access keys used for creating this Z table related to the GL. The table has over 24,000,000 recs in it and causes VF11 to run for an hour to cancelk an invoice. I do not see any handy exits to put any code so certain bussineses can skip the logic. There are indexes but I do not think they are being utilized in the SAP R programs.
Bottom line: Either purge, or clean the table?
Anybody know any other ways to clean up this table or other suggestions?
Thank-You.

Use ST05 or ST04
ST05 has been explained earlier.
ST04 - You can find where the bottleneck is..whether its a connection problem or database problem etc. You will find data by Transaction.
Sri

Similar Messages

VF11 (cancel invoice) in background job

Hi,
Is there a way to schedule a job for x numbers of invoices we want to cancel? In VF11 (as far as I can see) there is no option to save a variant and then setup this job in SM36. Reason I want to run it as a job is that I don't want my name tag on all cancelled invoices. Any good suggestions?
Kind regards

Hi,
Check Note 1259505 - FAQ: New cancellation procedure in SD, surely it gives you some idea
Regards,
Eduardo

How to cancel invoice documents in Background Jobs ?

Dear sd Gurus
i want to cancel invoice documents in Background Jobs .
I Have checked this link also VF11 (cancel invoice) in background job
But i did find Exact Way
Thanks a lot

Hi Madhuri,
I suggest you to use LSMW for this activity. Just do the recording, test it for one billing doc. If successful then run it for all billing doc which you want to cancel.
MT

In forms how to cancel long running process or query in 10g

We have application which is hosted on 10g AS. Some forms has lot of processing to be done and sometimes user wants to cancel the processing in between maybe because he wants to change some value and refire processing.
Based on the search on net 'Esc' key was used in earlier version of forms to function as User requested Cancel operation. How can same be done in 10g. Do we have to do anything in fmrweb.res for this. Is there some setting to be done in forms or in AS for this functionality.
Does this matter on whether JInitiator is used or JPI is used for running the application?
Edited by: suresh_mathew on May 21, 2013 1:36 AM

Hi,
Exit can be used to cancel query mode i.e. in case you go into query mode by Exit you can cancel query mode. Suppose you went into query mode and you have fired query which will take some time to fetch how can I abort it.
In earlier version of form there was 'Cancel' facility wherein if triggered it used to fire an error message 'Ora--01013 user requested cancel of current operation"
With this facility you can abort any query which is executing or any long running process which forms is currently performing.
fmrweb.res would have entry like
27 : 0 : "Esc" : 1001 : "Cancel"
The above entry I picked from OPN
Java Function Numbers And Key Mappings For Forms Deployed Over Web [ID 66534.1]
Unfortunately this is not working for us even if I put this in frmweb.res of 10g AS
Basically I want ability to Abort/Cancel a long running process be it query execution or standard process triggered in the form.
Any advise or help is highly appreciated.
Suresh

SQL Developer Locking up/Unable to Cancel long Running tasks

I have had the same problem with a number of versions of SQL Developer (and version 3.2.09). It occurs when trying to cancel a long-running PL-SQL Function or procedure that has been started by 'Run' in SQL Developer.
Select Terminate in Run Manager does not stop the job. Nor does trying to exit SQLDeveloper; it asks whether I want to kill the job; then doesn't kill it and doesn't exit either.
Trying to save modifications to anything the process depends on results in SQL Developer locking for ~20 minutes.
I have to resort to getting a DBA to manually kill the process at the server.
Is there any possiblity of a workaround or a way of making the PL/SQL not lock so it can be terminated please?
Thanks

I have had the same problem with a number of versions of SQL Developer (and version 3.2.09). It occurs when trying to cancel a long-running PL-SQL Function or procedure that has been started by 'Run' in SQL Developer.
Select Terminate in Run Manager does not stop the job. Nor does trying to exit SQLDeveloper; it asks whether I want to kill the job; then doesn't kill it and doesn't exit either.
Trying to save modifications to anything the process depends on results in SQL Developer locking for ~20 minutes.
I have to resort to getting a DBA to manually kill the process at the server.
Is there any possiblity of a workaround or a way of making the PL/SQL not lock so it can be terminated please?
Thanks

Cancel long running statement in Oracle Lite (OLITE_10.3.0.3.0 olite40.jar)

On JDBC statement, there is the method 'cancel' to instruct the database to cancel an executing statement. This works fine on Oracle server database, but not on Oracle lite database. The method call 'cancel' just blocks and the running statement is never interrupted.
The example I tried is very simple. There is a thread started which executes a long running statement. I noticed, that when moving the cursor forward by calling rs.next(), it just blocks. That would be ok, if the statement could be canceled from within the main thread by stmt.cancel. But this call blocks as well with no implact on the running statement. Why is that? Do I miss something or is it not possible to cancel a long running statements in Oracle Lite?
In the following my code snipped:
public class CancelStatement {
     private static final String PATH_DB = "XX";
     private static final String PATH_LIB = "XX";
     private static final String CON_STRING = "jdbc:polite:whatever;DataDirectory=" + PATH_DB + ";Database=XX;IsolationLevel=Read Committed;Autocommit=Off;CursorType=Forward Only";
     private static final String USER = "XX";
     private static final String PASSWORD = "XX";
     public static void main(String args[]) throws Exception {
          System.setProperty("java.library.path", PATH_LIB);
          Class.forName("oracle.lite.poljdbc.POLJDBCDriver");
          Connection con = DriverManager.getConnection(CON_STRING, USER, PASSWORD);
          Statement stmt = con.createStatement();
          Thread thread = new Thread(new LongStatementRunnable(con, stmt));
          thread.start();
          Thread.sleep(3000);
          // stop long running statement
          System.out.println("cancel long running statement");
          stmt.cancel(); // XXX does not work, as call is blocked until out of memory
          System.out.println("statement canceled");
     private static class LongStatementRunnable implements Runnable {
          private Connection con;
          private Statement stmt;
          public LongStatementRunnable(Connection con, Statement stmt) {
               this.con = con;
               this.stmt = stmt;
          @Override
          public void run() {
               try {
                    System.out.println("start long running statement...");
                    // execute long running statement
                    ResultSet rs = stmt.executeQuery("SELECT * FROM PERSON P1, PERSON P2");
                    while (rs.next()) { // here the execution gets blocked
                         System.out.println("row"); // is never entered
                    rs.close();
                    stmt.close();
                    con.close();
                    System.out.println("long running statement finished...");
               } catch (Exception e) {
                    e.printStackTrace();
}I would be very glad if you could help me.
Thanks a lot
Daniel
Edited by: 861793 on 26.05.2011 14:29

Unfortunately Oracle Lite doesn't have this option. You can call your statement from a second thread as you have done, but you won't be able to kill or cancel this operation. The only way to get fix this is by rebooting. You can use process explorer to find the dll process that is executing the SQL, but the tables will be locked and sync would be locked as well until the process is finished running in shared memory.

To cancel invoice-VF11

Hi SAP Guru,
I have one question. To cancel invoice using VF11, I cannot do it if I logged in into SAP using normal user. The error log said "Document does not existed". (Actually, it is existed.) However, if I am log in using super user account, I can do it. The document is found. So, anybody can clarify me about this case. Thanks in advance. Reward point will be given to all whom provide contribution to my thread.

Hi Annop,
This could be because of some missing authorisation for that user id.
Try VF11 using the user id that gives error message.
Once you get the error message, goto the transaction <b>SU53</b>.
This will give you the missing authorizations for that user id for
executing the transaction VF11.
Get the missing authorisation objects & contact your basis people.
They can attach the necessary objects to the respective user id.
hope this will help!
best regards,
Thangesh

How can i cancel long running queries (red x doesnt work)

hi there
i am trying to work with some long running queries - it would be very nice to be able to cancel them (like toads cancel button)
I have tried the red X in the circle but it doesnt seem to work - it appears to have cancelled it (the cylon-eye style comfort bar stops ocillating) but if i try to use the connection again, or disconnect or open another connection it says:
"connection currently busy. Try again?"
i have tried this in the latest release vanilla & the latest release plus patch 2
thanks
Martin

Good news that this will be improved. Can't resist to post this Link: [plsql forum thread about start/stop.. | http://forums.oracle.com/forums/thread.jspa?forumID=75&threadID=927697]
I have experienced the same and also noted that it feels better to execute stored procedures in sqldeveloper
- by editing
- compiling (might hang if already busy)
- run from the same dialog just to get the the cylon's eye for emergency stops (which waits .... ) meanwhile jump to apex to fiddle with small table triggering exception to stop the procedure.
If stored procedure is executed from the list via 'right mouse click'-style then you see in the log-region "connecting to databse ... ." but no method to stop nor cancel or cylon's eye is well hidden.
When such "busy" is running I also noted that the database-connection right mouse click has greyed/inactivated the selections "connect/disconnect" so the next logical step for stopping via "disconnect" is out of the question.
I think this also boils down also to question whether the user has rights to see gv$session and be able to drop/stop busy/jamming sessions. E.g. public synonyms listing has small icons with mystic red :)
/paavo
Java(TM) Platform 1.6.0_14
Oracle IDE 1.5.4.59.40

Cancel long running queries

Hi Folks,
Is it possible to submit a SELECT statment using OraSqlStmt object and retrieve the data so generated?
I want to submit a long-running SELECT query against Oracle, and have the option to cancel the query.
I can submit the query asynchronously NONBLK option of OraSqlStmt and then be able to cancel it. However, I also want to display the dataset returned by the query. But I think it is not possible to create a dataset / recordset or dynaset using OraSqlStmt.
THe question is:
How can I submit a long running Select query, be able to cancel it and if the query is not cancelled then be able to display the records in a grid? I am using VB6.
Thanks

Good news that this will be improved. Can't resist to post this Link: [plsql forum thread about start/stop.. | http://forums.oracle.com/forums/thread.jspa?forumID=75&threadID=927697]
I have experienced the same and also noted that it feels better to execute stored procedures in sqldeveloper
- by editing
- compiling (might hang if already busy)
- run from the same dialog just to get the the cylon's eye for emergency stops (which waits .... ) meanwhile jump to apex to fiddle with small table triggering exception to stop the procedure.
If stored procedure is executed from the list via 'right mouse click'-style then you see in the log-region "connecting to databse ... ." but no method to stop nor cancel or cylon's eye is well hidden.
When such "busy" is running I also noted that the database-connection right mouse click has greyed/inactivated the selections "connect/disconnect" so the next logical step for stopping via "disconnect" is out of the question.
I think this also boils down also to question whether the user has rights to see gv$session and be able to drop/stop busy/jamming sessions. E.g. public synonyms listing has small icons with mystic red :)
/paavo
Java(TM) Platform 1.6.0_14
Oracle IDE 1.5.4.59.40

Cancelling of Long Running Queries feature for GRID data block

Hi,
Maybe someone knows solution-
we have custom form with Spreadtable (JTF_GRID object) block (similar as, for example, EBS form WMSCTLBD).
Is here any possibility to enable ‘Cancel Long Running Queries’ feature for it?
I have reviewed built-in JTF_GRID library (with hope to implement it by adding some custom timer) but I cannot find any API which could be used for cancelling already submitted queries.
I have created a SR but analyst suggested to ask for it in forums :)
Our Oracle Forms Version is 6.0.8.28.0
Thanks in advance.
BR,
Kristaps

Try CTRL-ALT-DELETE
:-)

How to Cancel Long Running Report

Hello
I'm looking for a way to cancel the printing of a long running report programatically? I'm using the CrystalDecisions.CrystalReports.Engine.ReportDocument() class.
Thanks for your help

Hi Syed,
The old viewer was COM based and the new viewer is .NET. CR has the ability if the DB server supports Async communication. Most DB's don't so it wasn't of much use. For those that did the functionality was through custom coding within the Designer only. Async would allow CR to send a stop processing command to the DB server. If the server did not have the ability then CR can only wait for the data to start coming back before stopping the viewer from updating.
In any event I don't believe the Windows Viewer in .NET has the ability but I will suggest it to the Product group to add the ability in some future version.
Thank you
Don

Canceling long running queries

This definitely occurs in 1.5.5 - in my particular case, and this is really strange, if one uses Task Manager to shut down SQLDeveloper because it is just taking forever to get a Data view (via the + expand sign on the side of a given admittedly big table, then clicking on the Data tab), SQLDeveloper freezes. Even if I start a new instance of SQLDeveloper, and ask for a Data view again, it freezes - I've waited as much as 1/2 hour, where as in prior days I'd get a response within say 1 min.
I've even uninstalled and re-installed. Same deal. This is what's the strangest by far. How can it be that SQLDeveloper remembers that a long running query was once canceled even after an uninstall / reinstall ? I could not find anything remotely related to this in the Registry after the uninstall either.
[By the way, if on the other hand, I say SELECT * FROM {table_name}, I get an instant response !]

How to Cancel the Cancel invoice? How to reverse the vf11 entry?

Hello Experts
Need suggestions on the following.
I have created wrongly the cancel doc in VF11. This was suppose to do for this year but did for last year.
How can I cancel/ reverse this doc which is generated in vf11.
Regards
RaviRaj

Hello
Please make search before putting up you specific query.
Refer following link:
- Cancel / reverse billing document cancellation document?
FYI - Based on standard config you can not cancel a "cancellation Invoice".
As if you check the Std Cancel. Invoice (S1), don't have Cancell.billing type.
Regards
JP

How to cancell Invoice by VF11

Salute Masters !!
I have created one new Sales Order Type PW00 Warranty Order for Plant P&YE (Port & Yard Equipment), Copied from Existing Sales Order Type EW00 Warranty Order Type for Plant BMHE (Bulk Material Handling Equipment) in which I have given separate No. Range From 3330000000 To 3339999999.
In PW00, I have given Delivery Document Type PY00 by No. Range from 3270000000 To 3279999999; Delivery Related Billing Type PY01 by No. Range 3290000000 To 3299999999 and have assigned to respected document.
Now, Sales Order has been created by 3330000000, subsequent Delivery has been done by 3270000001 and Invoice has been done by 3290000003, Released to Accounting and Excise Invoice done by 3290000003.
Now user wanted to get the same No. by which Accounting document generated internally which was created by FI side through FBN1, No. Range 3601000001 To 3791099999, for their Financial Accounting Document Type (OBA7), as it was given in my Billing Document type PY01, that is PB (Standard was EB), instead of 3290000003,
as his other plants Nos. are same as well as Invoice No. & Accounting Document No.
I have changed No. Range from 3290000000-32999999999 To 3601000001-3601999999 in VN01.
After wards user cancelled the excise invoice and tried to cancel Commercial Invoice by VF11, now system is giving error,
No Billing Document were generated
When check error log, its saying, Data inconsistency during processing of Document 3290000000
The Billing Document 3290000000 is already cleared
I have changed again the No. Range from 3601000001-3601999999 To 3290000000-32999999999
Still system is giving error,
No Billing Document were generated
When check error log, its saying, Data inconsistency during processing of Document 3290000000
The Billing Document 3290000000 is already cleared
Please suggest how to cancel invoice & give the same No. Range as per user requirement and we can do Excise Invoice.
Thanks & Regards
Srivastav
+91-9973504950

As I already mentioned, you need to remove Copying requirements in Cancellation section of Billing Doc type-PY01 (tcode VOFA).
As the routine is for cancelling an invoice that has been cleared in accounting. So, this copying requirements are FORM routines that check certain requirements as a precondition for the copying process. This requirement checks if a billing document has been paid in AR prior to permitting cancellation. For example, If an error has been made in invoicing, it is possible to create a cancellation invoice and then re-bill the customer for the correct amount. This process, however, should not be allowed if the invoice has already been forwarded to the customer and payment has been received and applied. This requirement can be assigned to the billing document to insure that no paid invoices are allowed to be canceled.
So, remove that and try.
And check you doc number 3290000003 with tcode FB03
Also, Doc type PB in tcode OBA7, check
- number range for doc type.
- Reversal Doc type and number range for reversal doc type.
Hope this can assist you.
Thanks & Regards
JP

Reason for canceling invoices - VF11 - SD

What is the procedure to capture reason for canceling invoices? The requirement is the users want to choose a reason from the given list of reasons (Like... Drop down option) when they cancel invoices.

Hi,
SAP dose not give you standard field for this use. The reason, I believe, that the system do not use billing cancel reason is the different processes followed. There for if you want to manage the reasons (though the process is the same), you can create different cancellation billing types.
I think otherwise you will break SAP Standard.
An alternative could be, if you also cancel the sales order, to manage the reasons there. In the sales order you will find appropriate fields for that.
Regards,
Ido
Please reward if it helps.

Long Running VF11: Cancel Invoice

Similar Messages

Maybe you are looking for