Problem (implicit commit) after calling POP UP in f-43 after pressing SAVE

Hi all ,
I have done an enhancement for F-43 after pressing SAVE a pop up will be given to enter amount after entering the amount the user will press enter then i check the amount entered if the value is incorrect then i through an error message so the document should not be posted.
But the issue is the document no is generated or fetched from number range before my enhancement but not commited in NRIV, and when the popup is called , the DOCUMENT no is commited as after the call screen a new LUW is started.
Iam thinking calling the popup before the DOCUMENT NO is generated or fetch from number range.
Any solution to resolve this .
Regards,
Madhukar Shetty

Hi Madhukar Shetty,
For your requirement you can use interface BTE 1020 which gets triggered just before save. Keep your condition based on SY-UCOMM as it will get triggered for Simulate & Save modes. At this point of time system will not have any document number and you can raise any error as well, coz system has not saved anything.
Thanks & Regards,
Faheem.

Similar Messages

Problem with mutiple BAPI calls during the commit

Hi all,
I am trying to create accounts for a given partner i the transaction F9K1 using the BAPI BAPI_BKK_ACCNT_CREATE. After calling the BAPI I am committing it too.
The problem is if I try to create multiple accounts like RCA, ACA, MCA, IOE and so on, the first time the BAPI is called to create RCA account it is successful an it is even committing. When I call the BAPI to create the the ACA account the return table from the BAPI shows success message but the commit fails. If I restart the program and try creation of accounts now the RCA will throw a error msg saying account already exist, ACA account will be created and then the MCA account creation fails in the same manner explained above.
I see the issue is with multiple BAPI calls and I tried using all sort of methods like clearing buffers, start new task in local and wait command and all. But none of them seems to be working for me.
Can anyone please guide me on how I can overcome this problem.
Thanks.

BAPI :
BAPI BAPI_BKK_ACCNT_CREATE
Functionality
Use this method to create an account in Bank Customer Accounts. This method returns the following values:
Identification details for the newly created account such as the internal and the external account number, and the bank area details
A table containing error messages
To create an account by using this method, you must specify values for the import parameters Bank Area (BANKAREA) and Product (PRODUCTNAME).
Note: You must also specify a value in the External Account Number (EXTERNALACCOUNTNR) parameter if you have defined an external number range for the bank .
REgards,
Jayan.

After call commit sql , data can not flush to disk

I use berkey db which support sql . It's version is db-5.1.19.
1, Open a database.
2. Create a table.
3. exec "begin;" sql
4. exec sql which is insert record into table
5. exec "commit;" sql
6. copy database file (SourceDB_912_1.db and SourceDB_912_1.db-journal) to Local Disk of D, then use a tool of dbsql to open the database.
7. use select sql to check data, there is no record in table.
1
sqlite3 * m_pDB;
int nRet = sqlite3_open_v2(strDBName.c_str(), & m_pDB,SQLITE_OPEN_READWRITE | SQLITE_OPEN_CREATE,NULL);
2
string strSQL="CREATE TABLE [TBLClientAccount] ( [ClientId] CHAR (36), [AccountId] CHAR (36) );";
char * errors;
nRet = sqlite3_exec(m_pDB, strSQL.c_str(), NULL, NULL, &errors);
3
nRet = sqlite3_exec(m_pDB, "begin;", NULL, NULL, &errors);
4
nRet = sqlite3_exec(m_pDB, "INSERT INTO TBLClientAccount (ClientId,AccountId) VALUES('dd','ddd'); ", NULL, NULL, &errors);
5
nRet = sqlite3_exec(m_pDB, "commit;", NULL, NULL, &errors);
Edited by: 887973 on Sep 27, 2011 11:15 PM

Hi,
Here is a simple test case program I used based on your description:
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include "sqlite3.h"
int error_handler(sqlite3*);
int main()
     sqlite3 *m_pDB;
     const char *strDBName = "C:/SRs/OTN Core 2290838 - after call commit sql , data can not flush to disk/SourceDB_912_1.db";
     char * errors;
     sqlite3_open_v2(strDBName, &m_pDB, SQLITE_OPEN_READWRITE | SQLITE_OPEN_CREATE, NULL);
     error_handler(m_pDB);
     sqlite3_exec(m_pDB, "CREATE TABLE [TBLClientAccount] ( [ClientId] CHAR (36), [AccountId] CHAR (36) );", NULL, NULL, &errors);
     error_handler(m_pDB);
     sqlite3_exec(m_pDB, "begin;", NULL, NULL, &errors);
     error_handler(m_pDB);
     sqlite3_exec(m_pDB, "INSERT INTO TBLClientAccount (ClientId,AccountId) VALUES('dd','ddd'); ", NULL, NULL, &errors);
     error_handler(m_pDB);
     sqlite3_exec(m_pDB, "commit;", NULL, NULL, &errors);
     error_handler(m_pDB);
     //sqlite3_close(m_pDB);
     //error_handler(m_pDB);
int error_handler(sqlite3 *db)
     int err_code = sqlite3_errcode(db);
     switch(err_code) {
     case SQLITE_OK:
     case SQLITE_DONE:
     case SQLITE_ROW:
          break;
     default:
          fprintf(stderr, "ERROR: %s. ERRCODE: %d.\n", sqlite3_errmsg(db), err_code);
          exit(err_code);
     return err_code;
}Than I copied the SourceDB_912_1.db database and the SourceDB_912_1.db-journal directory containing the environment files (region files, log files) to D:\, opened the database using the "dbsql" command line tool, and queried the table; the data is there:
D:\bdbsql-dir>ls -al
-rw-rw-rw-   1 acostach 0 32768 2011-10-12 12:51 SourceDB_912_1.db
drw-rw-rw-   2 acostach 0     0 2011-10-12 12:51 SourceDB_912_1.db-journal
D:\bdbsql-dir>C:\BerkeleyDB\db-5.1.19\build_windows\Win32\Debug\dbsql SourceDB_912_1.db
Berkeley DB 11g Release 2, library version 11.2.5.1.19: (August 27, 2010)
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
dbsql> .tables
TBLClientAccount
dbsql> .schema TBLClientAccount
CREATE TABLE [TBLClientAccount] ( [ClientId] CHAR (36), [AccountId] CHAR (36) );
dbsql> select * from TBLClientAccount;
dd|dddI do not see where the issue is. The data can be successfully retrieved, it is present in the database.
Could you try putting in the sqlite3_close() call and see if you still get the error?
Did you remove the __db.* files from the SourceDB_912_1.db-journal directory?
Did you use PRAGMA synchronous, and if so, what is the value you set?
If this is still an issue for you, please describe in more detail the exact steps needed to get this reproduced and provide a simple stand-alone test case program that reproduces it.
Regards,
Andrei

How to make the Commit after calling a BAPI from SE37 ?

Hi
When i use a BAPI for update some SAP table i always call the BAPI inside a program and then i call the BAPI_TRANSACTION_COMMIT for made the changes and validate them
Bot now i need to test the BAPI directly in SE37 , and the BAPI returns the sucess message but i can not see the changes in the SAP tables , i guess i need to make the Commit but how can i do this ?
by calling the BAPI_TRANSACTION_COMMIT directly in SE37 after the call to the other BAPI ?
Thanks
Frank

se37 > clear the field of the function module name
menu path: Function module > test > test sequence and give you FM's sequence you want to test

Retain the entityState and postState of entities even after calling commit

Dear all,
I am using view objects based on programmatic entity objects in my application for which data is populated from an array using populateRow().
I need to update the newly created/updated/deleted rows in this EO into the database using a stored procedure.
The stored procedure needs the input as an array of only those records that are created/updated/deleted with indicators of whether each row in the array is inserted/updated/deleted.
I have exposed a client interface method in the view object Impl class that calls the dbTransaction().commit() first and then calls the stored procedure.
In the doDML(), I am constructing the array and keeping the values in a page flow scope which is then accessed in the voImpl method.
In case if an exception occurs in the business logic inside the stored procedure, the data will not get posted in the database and the exception is displayed to the user in the UI.
After calling the stored procedure, I am clearing the page flow scope irrespective of whether the data has been posted to DB or not.
Consider the scenario,
I have updated 2 records. Of these, I've updated one of the records with wrong values. As per my logic, on calling the save method, doDML() will construct the data array for these two records.
Inside the stored procedure, the wrongly updated row is identified and exception is raised and the data will not get posted in the database.
Now, on getting the exception, I update the worngly updated record with proper value.
On calling the save method again, my doDML() is constucting the array with the currently updated record alone. But actually I need all the records (2 records in this case) that were modified.
My understanding is, since I've called the commit() action, all the records that make my transaction dirty gets updated as status_unmodified subsequently.
Hence, on calling commit the second time, only one record will be in modified state and that record alone is getting constructed in the array.
If I am correct,
1. Is there any way to make all those records with their status as they were before calling the commit.
2. Should I construct my array in some other method instead of doing it in doDML().
Thanks in advance.

You may want to try calling setClearCacheOnRollback(false) and rollback instead when you get the exception from the stored procedure. I still haven't understood where the commit is done...
You may want to consider using an Application Module variable to store your list if this helps.
Cheers,
Nick

I just had problems with a game called call of duty 4, modern warfare. I decided that if I deleted it, I could reinstall it, I could get it back to normal. After I deleted it,I went to to the appstore and went to purchases and accidentaly deleted it/help

I just had problems with a game called call of duty 4, modern warfare. I decided that if I deleted it, I could reinstall it, I could get it back to normal. After I deleted it,I went to to the appstore and went to purchases and accidentaly deleted it. please help me!

You have not deleted it from the purchases list, it is just hidden. To unhide an app, open the Mac App Store app, click the Account link in the Quick Links to the right of the pane and go to the iTunes in the Cloud section where you can manage hidden apps.

Why there is implicit commit before and after executing DDL Statements

Hi Guys,
Please let me know why there is implicit commit before and after executing DDL Statements ?
Regards,
sushmita

Helyos wrote:
This is because Oracle has design it like this.Come on Helyos, that's a bit of a weak answer. :)
The reason is that it makes no sense to update the structure of the database whilst there is outstanding data updates that have not been committed.
Imagine having a column that is VARCHAR2(50) that currently only has data that is up to 20 characters in size.
Someone (person A) decides that it would make sense to alter the table and reduce the size of the column to varchar2(20) instead.
Before they do that, someone else (person B) has inserted data that is 30 characters in size, but not yet committed it.
As far as person B is concerned that insert statement has been successful as they received no error, and they are continuing on with their process until they reach a suitable point to commit.
Person A then attempts to alter the database to make it varchar2(20).
If the database allowed that to happen then the column would be varchar2(20) and the uncommitted data would no longer fit, even though the insert was successful. When is Person B going to find out about this? It would be wrong to tell them when they try and commit, because all their transactions were successful, so why should a commit fail.
In this case, because it's two different people, then the database will recognise there is uncommitted transactions on that table and not let person B alter it.
If it was just one person doing both things in the same session, then the data would be automatically committed, the alter statement executed and the person informed that they can't alter the database because there is (now) data exceeding the size they want to set it to.
It makes perfect sense to have the database in a data consistent state before any alterations are made to it, hence why a commit is issued beforehand.
Here's something I wrote the other day on the subject...
DDL's issue a commit before carrying out the actual action
As long as the DDL is syntactically ok (i.e. the parser is happy with it) then the commit is issued, even if the actual DDL cannot be executed for another reason.
Example...
We have a table with some data in it...
SQL> create table xtest as select rownum rn from dual;
Table created.
SQL> select * from xtest;
        RN
         1We then delete the data but don't commit (demonstrated by the fact we can roll it back)
SQL> delete from xtest;
1 row deleted.
SQL> select * from xtest;
no rows selected
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
        RN
         1
SQL> delete from xtest;
1 row deleted.
SQL> select * from xtest;
no rows selectedSo now our data is deleted, but not committed, what if we issue a DDL that is syntactically incorrect...
SQL> alter tab xtest blah;
alter tab xtest blah
ERROR at line 1:
ORA-00940: invalid ALTER command
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
        RN
         1... the data can still be rolled back. This is because the parser was not happy with the syntax of the DDL statement.
So let's delete the data again, without committing it, and issue a DDL that is syntactically correct, but cannot execute for another reason (i.e. the database object it refers to doesn't exist)...
SQL> delete from xtest;
1 row deleted.
SQL> select * from xtest;
no rows selected
SQL> truncate table bob;
truncate table bob
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
no rows selectedSo, there we have it. Just because the statement was syntactically correct, the deletion of the data was committed, even though the DDL couldn't be performed.
This makes sense really, because if we are planning on altering the definition of the database where the data is stored, it can only really take place if the database is in a state where the data is where it should be rather than being in limbo. For example, imagine the confusion if you updated some data on a column and then altered that columns datatype to be a different size e.g. reducing a varchar2 column from 50 character down to 20 characters. If you had data that you'd just updated to larger than 20 characters whereas previously there wasn't, then the alter table command would not know about it, would alter the column size and then the data wouldn't be valid to fit whereas the update statement at the time didn't fail.
Example...
We have a table that only allows 20 characters in a column. If we try and insert more into that column we get an error for our insert statement as expected...
SQL> create table xtest (x varchar2(20));
Table created.
SQL> insert into xtest values ('012345678901234567890123456789');
insert into xtest values ('012345678901234567890123456789')
ERROR at line 1:
ORA-12899: value too large for column "SCOTT"."XTEST"."X" (actual: 30, maximum: 20)Now if our table allowed more characters our insert statement is successful. As far as our "application" goes we believe, nay, we have been told by the database, we have successfully inserted our data...
SQL> alter table xtest modify (x varchar2(50));
Table altered.
SQL> insert into xtest values ('012345678901234567890123456789');
1 row created.Now if we tried to alter our database column back to 20 characters and it didn't automatically commit the data beforehand then it would be happy to alter the column, but then when the data was committed it wouldn't fit. However the database has already told us that the data was inserted, so it can't go back on that now.
Instead we can see that the data is committed first because the alter command returns an error telling us that the data in the table is too big, and also we cannot rollback the insert after the attempted alter statement...
SQL> alter table xtest modify (x varchar2(20));
alter table xtest modify (x varchar2(20))
ERROR at line 1:
ORA-01441: cannot decrease column length because some value is too big
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
X
012345678901234567890123456789
SQL>Obviously, because a commit statement is for the existing session, if we had tried to alter the table column from another session we would have got
SQL> alter table xtest modify (x varchar2(20));
alter table xtest modify (x varchar2(20))
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified
SQL>... which is basically saying that we can't alter the table because someone else is using it and they haven't committed their data yet.
Once the other session has committed the data we get the expected error...
ORA-01441: cannot decrease column length because some value is too bigHope that explains it

Problem to download i called the support Adobe and after a while he said he had problem with his int

problem with his internetand shut down the contakt
After that I can not come in to my adobeconto on my other computer ?????

Once again
I can nor download my PHCC
The cod say no
When I phone Krishnan S on support he suddenly say he got problem with his internet and cannot go on phone later
After that talk I can not come in in the computer I tryid to download from and that computer I had contakt with Krishnan
What is the problem?

Problem with commit

Hi All,
I am using a COMMIT statement after update statement of a table in a transaction(say ZTRAN1),. When I am calling this transaction ZTRAN1 using CALL TRANSACTION ZTRAN1... statement from another transaction(say ZTRAN2) then the processing is coming out of the first transaction ZTRAN1 after comit statement. i.e no statement after comit stmt in ZTRAN1 is executing. Can any one pls give me reason.
All helpful answers will be awarded.
Thanks
Giridhar

Hi,
please do have a look at the following thread. Pay special attention to parameter RACOMMIT. i think that if you do a CALL TRANSACTION 'ZTRAN1' OPTIONS FROM w_ctu_params with w_ctu_params-RACOMMIT = 'X' your problem will be solved.
bdc
Best regards.

Implicit commit in ABAP Web Dynpro?

I wonder if ABAP Web Dynpro is executing an implicit commit. I have two buttons on the same view. The first one inserts an entry into a table, the second one executes a "rollback work" (and to be sure calls function "DB_ROLLBACK").
However, after first pressing the insert-button and secondly the rollback-button, the rollback had no effect, i.e. one dataset has been permanently inserted into the database table.
Is it possible that until the view is ready for new processing (i.e. finished any initializations) an implicit commit is executed by SAP?
I have not used any commit nor do I use debugger mode.
The same behavior happens when I split the insert and rollback things into two views. In the second view the rollback is possible before the inbound plug is processed to the end, but afterwards (e.g. when handling a button click by an assigned method) not.

Hi Klaus,
I was wondering if you could do a ST05 trace? It will reveal the place where the commit happens. It will be quite interesting to see if it happens inside of the WD runtime. If yes, I would consider it a bug.
Best regards,
Thomas

Problem with ALV_GRID and CALL TRANSACTION.

Hi all, Could you please tell me
At SE38
Why REUSE_ALV_GRID_DISPLAY and CALL TRANSACTION after called then I click the back button to return to the calling program but it automatic return to the source code? (it hasn't saves the data in alv grid )
In another case of this program, after automatic return to the source code then I have to waiting for 5-10 mins for execute again cuz if immediately execute the program don't fill any data to the alv grid.
I have problem with a simple source code like this
REPORT ZFS_ALV_DEMO.
TYPE-POOLS: slis.
DATA: itab LIKE STANDARD TABLE OF aufk WITH HEADER LINE.
DATA: gs_selfield TYPE slis_selfield   "Information cursor position ALV
    , w_aufnr     LIKE aufk-aufnr.     "Order Number
SELECT * FROM aufk INTO TABLE itab WHERE autyp = 40.     "//Process Order
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
     EXPORTING
          i_structure_name        = 'aufk'
          i_callback_program      = sy-cprog
          i_callback_user_command = 'USER_COMMAND_COR3'
     TABLES
          t_outtab         = itab
     EXCEPTIONS
          program_error    = 1
          OTHERS           = 2.
FORM user_command_cor3 USING u_ucomm     LIKE sy-ucomm
                             us_selfield TYPE slis_selfield."#EC CALLED
CASE u_ucomm.
    WHEN '&IC1'.
      gs_selfield = us_selfield.
      IF gs_selfield-fieldname = 'AUFNR'.
        SET PARAMETER ID 'ANR' FIELD gs_selfield-value.
        CALL TRANSACTION 'COR3' AND SKIP FIRST SCREEN.
      ELSE.
        MESSAGE w208(00) WITH 'Select by Order only!'.
      ENDIF.
ENDCASE.
ENDFORM.

Hi all, Could you please tell me
At SE38
Why REUSE_ALV_GRID_DISPLAY and CALL TRANSACTION after called then I click the back button to return to the calling program but it automatic return to the source code? (it hasn't saves the data in alv grid )
In another case of this program, after automatic return to the source code then I have to waiting for 5-10 mins for execute again cuz if immediately execute the program don't fill any data to the alv grid.
I have problem with a simple source code like this
REPORT ZFS_ALV_DEMO.
TYPE-POOLS: slis.
DATA: itab LIKE STANDARD TABLE OF aufk WITH HEADER LINE.
DATA: gs_selfield TYPE slis_selfield   "Information cursor position ALV
    , w_aufnr     LIKE aufk-aufnr.     "Order Number
SELECT * FROM aufk INTO TABLE itab WHERE autyp = 40.     "//Process Order
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
     EXPORTING
          i_structure_name        = 'aufk'
          i_callback_program      = sy-cprog
          i_callback_user_command = 'USER_COMMAND_COR3'
     TABLES
          t_outtab         = itab
     EXCEPTIONS
          program_error    = 1
          OTHERS           = 2.
FORM user_command_cor3 USING u_ucomm     LIKE sy-ucomm
                             us_selfield TYPE slis_selfield."#EC CALLED
CASE u_ucomm.
    WHEN '&IC1'.
      gs_selfield = us_selfield.
      IF gs_selfield-fieldname = 'AUFNR'.
        SET PARAMETER ID 'ANR' FIELD gs_selfield-value.
        CALL TRANSACTION 'COR3' AND SKIP FIRST SCREEN.
      ELSE.
        MESSAGE w208(00) WITH 'Select by Order only!'.
      ENDIF.
ENDCASE.
ENDFORM.

VZW to VZW text messages have call back number in every message after Tango update

First of all I want to say how much I appreciate VZW rolling out the WP updates in a timely manner for once (is this the first time they've ever done so, for any phone?), even with the outdated technology (or just the one device), and I'm sure it'll keep us WP faithfulls happy for a little while longer. However I do have an issue with the latest update because it seems like VZW has been affected in such a way that now I have a "Call back at xxx-xxx-xxxx" after every text message received from a Verizon customer. At first I thought it was my friends and family telling me to call them back, and I did (to some degree of annoyance caused me and others) and now its just a plain nuisance. Some web perusing resulted in a few others having the same issue and only on verizon so far
I know who's texting me at any given time because their names are displayed on top and if I want to call them all I have to do is tap the name (and if no name then the number is so displayed), so displaying "call back at" so and so is just unnecessary and only serves to clutter up an otherwise clean nested message history/interface. So my question is there a way to disable this (which I have yet to find) or does VZW know about this error and plan to fix it, hopefully very soon? Or is this an issue with microsoft?

I found the answer to this problem. I think it depends on what kind of phone you have, but I was able to turn off the CB# in the messages. I have a Samsung Stratosphere. I was able to go into Messaging, then the menu icon, then choose Settings. Under the settings there was a choice called Callback enabled. I was able to to uncheck this choice and now my callback number no longer shows up. Hope this helps everyone!

Problem using RFC to call an adobe form to create pdf file........

Hi,
   I have an RFC that calls an adobe form to display the pdf output back in a bsp page...the RFC fails at the call to the adobe form (next call after after getting the form name) ...while debugging it looks like within this call it is trying to call fpcomp_job_open and failing on the call check_job_open ...
The code in my RFC looks like this....
DATA:
    gs_outputparams TYPE sfpoutputparams,
    fn_name           TYPE rs38l_fnam,
    fp_docparams      TYPE sfpdocparams,
    fp_formoutput     TYPE fpformoutput,
    frm_result        TYPE sfpjoboutput,
    lv_form           TYPE fpname.
DATA: l_pdf_xstring TYPE xstring,
       l_pdf_len      TYPE i.
lv_form = 'ZHR_ASSESSMENT_FORM'.
Start formrocessing - OPEN spool job to send to printer
gs_outputparams-getpdf = 'X'.
call function 'FP_JOB_OPEN'
    changing
      ie_outputparams = gs_outputparams
    exceptions
      others          = 1.
IF sy-subrc <> 0.
*//    RAISE FP Open Error.
      exit.
ENDIF.
Get name of the generated function module for the form
CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
    EXPORTING
      i_name     = lv_form
    IMPORTING
      e_funcname = fn_name.
IF sy-subrc <> 0.
*//    RAISE FP Get Form Module Name Error.
        exit.
ENDIF.
Call the Adobe Form
CALL FUNCTION fn_name
EXPORTING
      /1bcdwb/docparams = fp_docparams
      gv_appraisal_id = gv_appraisal_id
IMPORTING
     /1bcdwb/formoutput = fp_formoutput
    EXCEPTIONS
      usage_error        = 1
      system_error       = 2
      internal_error     = 3
      others             = 4.
IF sy-subrc <> 0.
*//    RAISE Call Form Module Error.
        perform f_build_message using 'E'
                                  'ZEXT'
                                  012
                            changing return.
       exit.
ENDIF.
End from processing - Close spool job
CALL FUNCTION 'FP_JOB_CLOSE'
    IMPORTING
      e_result       = frm_result
    EXCEPTIONS
      usage_error    = 1
      system_error   = 2
      internal_error = 3
      OTHERS         = 4.
IF sy-subrc <> 0.
*//    RAISE FP Close Error.
       exit.
ENDIF.
form = fp_formoutput-pdf.
Thanks,
Venkatesh

what is the solution for this problem? I have the same problem. I get sy-subrc = 1 after CALL FUNCTION 'FPCOMP_JOB_OPEN'.
If I look more in detail I see that "Perform check_job_open" is creating the problem:
FORM check_job_open.
IF fpstat-is_opened = c_true. (--> exactly here is the problem. This condition is true so the program is terminated.)
    PERFORM reset_status.
    MESSAGE ID 'FPRUNX' TYPE 'E' NUMBER '101' RAISING usage_error.
ENDIF.
fpstat-is_opened = c_true.
fpstat-is_started = c_false.
ENDFORM.
Does somebody know why my job is open and what is the solution to have the job closed at the beginning of my processing?
Thanks in advance.

Handle to error object after calling the statement execute - SQLDBC

Topic related to SQLDBC inteface to MaxDB
=======================
In C++ while i was executing the statement
rc = stmt->execute("SELECT 'Hello SAPDB' from DUAL");
i could get a handle to the error object by a call to
stmt->error().getErrorText()
Now while using SQLDBC_C i am using
rc = SQLDBC_Statement_execute(stmt,tempstr,strlen(tempstr),encodAsciiType);
Now how do i get the handle to the error object ??
Call like the above one
fprintf(stderr, "Executed SQLDBC_Statement %s",stmt->error().getErrorText());
gives me compilation error:
error: invalid use of undefined type `struct SQLDBC_Statement'
/opt/sdb/programs/sdk/sqldbc/incl/SQLDBC_C.h:125: error: forward declaration of `struct SQLDBC_Statement'
Please Help and feel free to ask me if the question is not clear.
Regards
Raja

Sorry. This question doesn't make sense. So, i withdraw the question.
Basically what I had confused with earlier and got clarified now is:
Just like when we make a call to SQLDBC_Connection_connect and after that use the SQLDBC_Connection_getError to get a handle to the SQLDBC_ErrorHndl.
I wanted to know how should we get a handle to the SQLDBC_ErrorHndl after we have made a call to the SQLDBC_Statement_<function call>.
I got the answer after looking through the SQLDBC_C.h file. It will be SQLDBC_Statement_getError and similarly SQLDBC_PreparedStatement_getError.
Wish i could award myself the 10 points for solving the problem
Regards
Raja

JNI - core dump - internal error on linux after calling Java method

I'm getting a core dump after calling athe main statric method using JNNI.
On linux.
I can get the class id correcttly but when I attempt to call the method it craches with an internal error , anyone know why it would crash instead of just not work.
if(cls)
    main_methodID = env->GetStaticMethodID(cls, "main", "([Ljava/lang/String;)V");
     printf("Class Found Successfully\n");
else
    printf ( "cls not found\n");
    return 0;
if(main_methodID)
          jstring first_str = env->NewStringUTF("The First String");//create string
          jobjectArray args = (jobjectArray)env->NewObjectArray(1,env->FindClass("java/lang/String"), first_str);//new array with 2 elements
               env->SetObjectArrayElement(args, 2, first_str);//insert the second string into index 1 of the array
          jstring second_str = env->NewStringUTF("The Second String");//create string
          env->SetObjectArrayElement(args, 1, second_str);//insert the second string into index 1 of the array
     env->CallStaticVoidMethod(cls, main_methodID, args);//pass the array to the Java main method
                              The JAVA method is
public static void main(String[] args) {
    System.out.println("Main method in Framework");
        Framework framework = new Framework();


I see yere points but what I see on linux is it makes it to the constructor of the Java object and somewhere afterwards it bails out, the Java app does work alone. It appears to have problems initializing the JFrame, could there be a problem with the Java inheritance when a JVM is invoked throurgh native invocation??
Here's some of the Java stuff
public class Framework extends WindowAdapter {
    public int numWindows = 0;
    private Point lastLocation = null;
    private int maxX = 500;
    private int maxY = 500;
    public Framework() {
        System.out.println("JAVA Framework cnst");//GETTING HERE
        makeNewWindow();
    public void makeNewWindow() {
        System.out.println("JAVA makeWindow"); //GETTING HERE
        JFrame frame = new MyFrame(this); //NOT GETTING HERE!!!!!!!!!
        numWindows++;
        System.out.println("Number of windows: " + numWindows);
        System.out.println("Frame location: " + lastLocation);
        frame.setVisible(true);
        System.out.println("Post Java set frame visible");
    public static void main(String[] args) {
    System.out.println("Main method in Framework");
        Framework framework = new Framework();//GETTING HERE
class MyFrame extends JFrame {
    protected Dimension defaultSize = new Dimension(200, 200);
    protected Framework framework = null;
    public MyFrame(Framework controller) {
        super("New Frame");
        System.out.println("MyFrame cnst ");//NOT GETTING HERE!!!!!!
        framework = controller;
        setDefaultCloseOperation(DISPOSE_ON_CLOSE);
        addWindowListener(framework);
        JMenu menu = new JMenu("Window");
        menu.setMnemonic(KeyEvent.VK_W);
       setSize(defaultSize);
}

Problem (implicit commit) after calling POP UP in f-43 after pressing SAVE

Similar Messages

Maybe you are looking for