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.

Similar Messages

Problem with comma and point

Hello,
I have a problem with comma and point in a double-digit.
I use a english driver for HM8142. When I get the values then I only get
int-digits. How can I change "Use comma as separator" . I tried to change
the option in LabVIEW.
I changed it, then I got the window. "To change, restart the programm". I
have done this. But when I have a look at the option, it is not changed.
What can I do?
I am not the admin on the computer.
Martin

Hi Martin,
you do not have to change any system settings neither in LabVIEW nor in your windows.
All instrument drivers should use a point as decimal separator. You can overwrite the decimal point handling in the string functions "Scan from string" and "Format into string".
Make a right click on the function and use "Edit Scan String". In the dialog open the ring under "Selected operation", the last entry allows you to set the character for the decimal separator. This separator will be used for all the following floating point numbers.
From your name and problem I think you are located in central europe. I do not have a german version of LV so I cannot tell you how the elements are named in german.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Problem with commas in user settings in 4.0, WS

There seems to be a problem returning user settings with GetUserSettings. The setting that contains a comma is being chopped.
Dim ptSettings, ptUserSettings
Set ptSettings = Server.CreateObject("GSServices.Settings")
Set ptUserSettings = ptSettings.GetUserSettings
Response.Write "<br>'" & ptUserSettings("strLastName") & "'"
For example this instead of 'Clayton, Jr', 'Clayto' is being displayed. The setting is correct in the PTMYPAGESPREFS table. Has anybody came across this problem, and maybe found a solution or a workaround? Thanks.
Dmitriy Karpov
[email protected]

I believe the problem is the following:
You have an app that calls directly into Plumtree.dll to set preferences. Those preferences may have non-alphanumeric characters, which are stored fine in the database.
You then want to retrieve these preferences through the EDK/GDK. The issue is, when EDK/GDK encounters non-alphanumeric characters, it encodes them using %u encoding before sending them over the wire to be stored in the DB. So, the data that's stored in DB is encoded, then it's sent back over the wire to EDK/GDK, which unencodes the prefs, and gives them to the calling app.
If the EDK/GDK encounters unencoded prefs sent over the wire, the behavior is undefined -- it's quite possible that's what you're seeing.
Basically, the trick is to store and retrieve preferences the same way -- either store them & retrieve them via direct calls to Plumtree API, or store them and retrieve them via EDK/GDK. If you have to store the prefs via the API and retrieve them in EDK/GDK, you HAVE to encode them the same way the EDK/GDK would encode them if it stored them.
BTW, what are the exact versions of the portal and EDK/GDK you are using?

Problem with Commit button When Backing bean is in Request Scope...

HI Everybody,
I have a Backing Bean in request scope having over 1000 lines of code, And in my JSPX page I have a table binding with a view object and At run time when user select the row in table and click the edit button so user will be able to edit that selected row in the same table at run time.. but the problem is : when the user enters some data in the Editable inputTexts and then clicks save(Commit), then the save button doesn't work..but when i delete any selected row and then press save then it is working fine..
And to test it in Session scope i made another sample page where every thing is working very fine..
Now i want to know What is the difference between Session scope and request scope bean...
And is there any solution to Save editable input text in Request scope?.
Also want to know that is it safe to set the scope of my main bean class to session scope without effecting the current running functionality? which is having over 1000 lines of code and lot of component has been placed...
Please help me to resolve this problem...
Thanks in Advance to all of you
Fizzz..

Hi Frank...
In my code i used almost same logic as Andrejus Baranovskis has explained in his Editable Table example...
You can refer that example to see what problem I'm facing...
http://andrejusb.blogspot.com/2007/04/create-edit-and-delete-operations-in.html
The Bean Scope in this Example is Session scope...Save button is working fine...
But as i Change the bean scope to Request scope then Save button is not working for Edit but it is working for Delete Action very well..
I want that save button should work also for Edit action in Request Scope..
Please Make me understand that why it is happened like that..
and help me to find the solution..
and Also if you have a better document to Explain the life cycle of Application in Different Bean Scope...So please provide me that Doc to me...
It would be a great help for me to understand the concept of session...
Thanks Frank
Fizzz...

Problem with COMMIT WORKS command

Hello all,
Ive a little problem. It seams that I dont understand how commit work command works. When Im calling transaction with USING parameter:
CALL TRANSACTION 'FPSA' USING itab_bdcdata.
When inside of that transaction Commit works occur, than commit is being executed and transaction is ending which is not good, because there is still code left that should be executed.
When I run transaction without USING
CALL TRANSACTION 'FPSA'
Everything works fine. Ive tried using UPDATE addition in CALL FUNCTION, but without result. Does anybody know what is the problem?

This is meant to work exactly as you described:
A transaction called with CALL TRANSACTION USING returns right after COMMIT occurs - if you don't provide any additional options.
There is a way to make such transaction continue with the code after the commit. You just have to use "OPTIONS FROM" addition of the "CALL TRANSACTION" statement - parameter RACOMMIT.
For more information put the cursor on CALL TRANSACTION statement in your abap code and press F1.
regards
good luck

Problems with 'COMMIT MISSING' - when using ABAP client proxies

Hi
We have a requirement - wherein while SAP std inbound IDOCs are being processed in the R/3 system- we need to monitor the processing of idocs - by sending relevant information out of the R3 system to a monitoring dashboard - outside of the R/3 environment.
Inorder to accomplish the above, we generated a async. client proxy class in the R3 system by pointing to a XI o/b message interface and that interface mapped on to DB calls - from which the dashboard was bringing up status of idocs being processed in R3
We made a call to the async class method from within the idoc user exit that lies within IDOC_INPUT_ORDERS FM . The user exit chosen to make the call was - after the salesorder processing for the inbound idoc was done in the above FM. We have not given any COMMIT WORK statement after the async client proxy method call within the user exit - since the call was being made from within user exit and we did not want to upset SAP std processing flow.
Now, when the inbound idoc processing is being done by using SAP std program rbdapp01 using parallel processing option of packets, the outbound message generated is in 'COMMIT MISSING' status - whereas - when rbdapp01 is executed in normal mode - the proxy message is sent out ok out of the R3 integration engine.
The program rbdapp01 has a COMMIT WORK statement after each IDOC packet is processed - but still with the parallel processing option - the proxy message stays in th R3 box - with the status 'COMMIT MISSING'
Any thoughts/ pointers on this is appreciated....

Hi Karthik,
I don't think you can get this to work using an asynchronous proxy - except perhaps by spawning an update task to send the data.
Perhaps you can re-cast this as a synchronous interface?
Regards,
Thorsten

Using Excel 14.3.7 to create a text file, for saving as a .csv file. Problems with commas.

I have created a text file in Excel, to be saved as a .csv file and uploaded to an online database. The file is rejected. When I open it in textedit I can see that the empty cells ( of which there are several in each row, all in the same columns) contain commas. It looked to me as though this could be the result of tabbing across empty cells. So I created a dummy file with a couple of lines where I tabbed across the whole row including the empty cells, and a couple of lines where I clicked in each individual cell in which I wanted to enter text. Opened in textedit there is no difference between the two type of entry. What can I do to stop Excel or .csv format entering commas in blank cells? Suggestions in simple English appreciated.

http://answers.microsoft.com/en-us/mac/forum/macexcel?tab=QnA

BAPI_REQUISITION_CREATE Problem with COMMIT WORK AND WAIT

I ran into an issue and wanted to get your opinions about what might be happening.
This is my original code that did not work correctly using COMMIT WORK AND WAIT. After the select statement, lv_count was zero even though there were PR items that had been created. I'm thinking that the database update was not complete, but why would that be?
    CALL FUNCTION 'BAPI_REQUISITION_CREATE'
      IMPORTING
        number            = lv_number
      TABLES
        requisition_items = gt_reqitem
        return            = gt_return.
*   Purchase requisition has been created
    IF lv_number IS NOT INITIAL.
      COMMIT WORK AND WAIT.
*     Get number of items in PR
      SELECT COUNT( DISTINCT bnfpo ) INTO lv_count
        FROM eban
        WHERE banfn = lv_number.
This is my corrected code that works. I removed the AND WAIT from the commit statement and added a separate wait statement. I now get the correct number of PR items that were created.
    CALL FUNCTION 'BAPI_REQUISITION_CREATE'
      IMPORTING
        number            = lv_number
      TABLES
        requisition_items = gt_reqitem
        return            = gt_return.
*   Purchase requisition has been created
    IF lv_number IS NOT INITIAL.
      COMMIT WORK.
      WAIT UP TO 1 SECONDS.
*     Get number of items in PR
      SELECT COUNT( DISTINCT bnfpo ) INTO lv_count
        FROM eban
        WHERE banfn = lv_number.
Any ideas?
Brenda

Brenda Bankert wrote:
Yes, I was able to see the message in RETURN and no, I am not calling the FM in a loop. My program calls it one time.
> Brenda
If you were able to see the message 'Purchase requisition number & created' it means that the macro macro_end is getting executed within which the COMMIT WORK statement is encapsulated.
I have quickly developed a dirty program to test the behaviour of 'SET UPDATE TASK LOCAL' and it seems to work as expected.
Everytime I executed the below program with 'SET UPDATE TASK LOCAL', I see the value of lv_count as 1000, however if I execute the below program with out the statement 'SET UPDATE TASK LOCAL' the value of count varies everytime, typically around 10 - 15, however the database is successfully updated with all the 1000 entries, this makes me believe that the 'SET UPDATE TASK LOCAL' statement will infact make the subsequent COMMIT synchronous.
REPORT zytest.
DATA:
ls_zytest    TYPE zytest,
ls_db_zytest TYPE zytest,
lv_numc04    TYPE numc4 VALUE 1001,
lv_count     TYPE i,
lv_index     TYPE i.
DO 1000 TIMES.
lv_index = sy-index.
CLEAR ls_zytest.
lv_numc04 = lv_numc04 + 1.
CONCATENATE 'KF00' lv_numc04 INTO ls_zytest-keyfield1.
CONCATENATE 'KF00' lv_numc04 INTO ls_zytest-keyfield2.
SET UPDATE TASK LOCAL.
CALL FUNCTION 'ZYTEST_BAPI'
    EXPORTING
      is_zytest = ls_zytest.
SELECT SINGLE * FROM zytest INTO ls_db_zytest WHERE keyfield1 = ls_zytest-keyfield1
                                                  AND keyfield2 = ls_zytest-keyfield2.
IF sy-subrc IS INITIAL.
    WRITE:/ lv_index, ls_db_zytest-keyfield1,ls_db_zytest-keyfield2.
    lv_count = lv_count + 1.
ENDIF.
ENDDO.
WRITE:/ lv_count.
FUNCTION zytest_bapi .
*"*"Local Interface:
*" IMPORTING
*"     REFERENCE(IS_ZYTEST) TYPE ZYTEST
DATA: transaction_id LIKE arfctid.
clear transaction_id.
macro_start.
CALL FUNCTION 'ZYTEST_UPDATE' IN UPDATE TASK
    EXPORTING
      is_zytest = is_zytest.
macro_end.
ENDFUNCTION.
FUNCTION ZYTEST_UPDATE.
*"*"Update Function Module:
*"*"Local Interface:
*" IMPORTING
*"     VALUE(IS_ZYTEST) TYPE ZYTEST
INSERT zytest from is_zytest.
ENDFUNCTION.
definition of the database table 'ZYTEST'
MANDT     MANDT
KEYFIELD1     CHAR20
KEYFIELD2     CHAR20
NONKEYFIELD     CHAR50
-Rajesh

"Problem" with COMMIT WORK AND WAIT

Hi everyone!
I'm facing the following situation:
I have a Z program that calls MIGO, via CALL TRANSACTION. The only thing I do when calling this is filling a few fields, so the user has to complete the operation before going back to Z program.
When someone executes MIGO in the normal way, I mean, without a CALL TRANSACTION command, there was a additional step, a modification made in the standard code for someone before. But this part of the code didn't execute when calling MIGO via CALL TRANSCATION.
What I have found out is that just before this code inserted, there was a COMMIT WORK AND WAIT command, and was exactly in this point that, when using the first aproach, it leaves MIGO.
Is there a way to execute the entire process in MIGO, I mean , do not leave it at COMMIT command? I've tried to pass at CALL TRANSACTION command diferent UPDATE parameters (i.e: 'S', 'A' and 'L'), but it didn´t work as well.
I hope you could get the point!
Thanks in advance!
Raphael

I've just found out something interesting about that.
When I make a CALL TRANSACTION, without passing a table bdcdata, the transaction doesn't leave at the COMMIT WORK command.
So, I think it won't work with the bdcdata!
Raphael

Mail-to-Mail scenario - Problem with comm. channel not reading message

Good day,
I am setting up a Mail-to-Mail scenario, where a received e-mail with an attachment is both processed into a file, as well as a monitoring e-mail needs to be send. The attachment processing is an existing process and is still working properly, but my e-mail isn't send. I am using Java mapping to create the destination e-mail based on the source e-mail. Everything is set up in the Directory as well, and through the Test Configuration feature I have tested my new addition to the existing process, I am seeing the result that I am expecting. I have sent a test message and XI picks it up just fine and processes it which is tested by both SXMB_MONI and the resulting file from the attachment.
However, the monitoring e-mail is not sent. Using the runtime workbench, there is an error in the receiver communication channel, being the following error from the Audit Log:
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.messaging.util.XMLScanException: java.lang.NullPointerException; nested exception caused by: java.io.IOException: Parsing an empty source. Root element expected!
Looking through the Message Content, I notice there is a SOAP document describing the source message and two payloads. The first payload being the source message in XML format, the second payload is entirely empty. I suspect this empty second payload is causing the NullPointerException, but I am at a loss as to why the payload is empty. The Test Configuration showed me that the message gets through just fine, so what is going wrong?
Here is a link to the configuration of the communication channel, maybe something is wrong here: [Config of communication channel|http://roald.hoolwerf.net/images/cc-config.png]
My question is: What can I do to find what is causing the communication channel to receive an empty payload, and how can I solve this?
Searching for this issue, or the given error on both Google as these forums hasn't given any related posts, if I did miss them in that case I am sorry for posting and please refer to the related topics.
Thank you in advance for taking time to look at this question.
Kind regards,
Roald Hoolwerf
Edited by: Roald Hoolwerf on Feb 1, 2010 3:57 PM

Try this.
Unchecked the configure use authentication.
and use mail package (base64)

Sql report on item - problem with commas in the string

I have a simple report that groups all the Job Titles entered on our database.
I pass the job title to an apex item and then on a second page list the records that match that job title using:
and ed.ede_job_title = :P35_JOB_TITLE
If there is a comma in the job title the report returns the records that match the string up to the point the comma appears not the full string.
So 'Project Manager, Operations' matches all the 'Project Manager' records.
Also when there is a leading space in the job title the report displays the jobtitle without the leading space.
Apologies if this is answered elsewhere, I did search.

Check the actual URL up in the location bar. Your comma may actually be dropping out there, because it isn't encoded such that in value commas can be differentiated from delimiters, so the fields aren't lining up in the URL properly.
When you go to a page that takes in parameters for assignment in the link, it has 2 fields. The first is the comma separated list of the item names on the page to assign, which wouldn't contain commas in their names. The other field in the URL is a comma separated list of values to be assigned to the previous list. Since these values aren't encoded, the comma in the value is picked up as delimiter and not a part of the value. I have an example I can load up to apex.oracle.com if you need.
-Richard
Edited by: rwendel on Aug 13, 2009 11:51 AM

PROBLEM WITH 'COMMIT' COMMAND IN FORM 4.5

During any process if I use COMMIT command after insert, update
or delete command in table which is not the base table of
current form a message appears on screen 'No changes to save'
and changes are saved in the table. How can I stop this message?
If I use Database trigger then I am not sure if I would be able
to use Rollback command.
null

If you are referencing standard.commit, it works for me. I
am using v4.5, I am assuming if is the same for 5.0 or 6.0 if 5.0
or 6.0 is your product.
Having said that all solutions mentioned are valid. I would
recommend next to try:
v_system_message_level := :system.message_level;
:system.message_level := '5';
commit;
:system.message_level := v_system_message_level;
If you modify the on-error/message trigger you may not
receive this error when it is raised when you really
do want to see it.
Faisal Shaikh (guest) wrote:
: No it didn't work any other ideas
: steve (guest) wrote:
: : Try using STANDARD.COMMIT;
: : Faisal Shaikh (guest) wrote:
: : : During any process if I use COMMIT command after insert,
: update
: : : or delete command in table which is not the base table of
: : : current form a message appears on screen 'No changes to
: save'
: : : and changes are saved in the table. How can I stop this
: : message?
: : : If I use Database trigger then I am not sure if I would be
: able
: : : to use Rollback command.
null

Problem with commit flag with RH_PNNNN_MAINTAIN

Hi,
i'm using RH_PNNNN_MAINTAIN in this way:
      call function 'RH_PNNNN_MAINTAIN'
        exporting
          act_fcode                   = 'INSE'
          act_otype                   = lw_plog-otype
          act_objid                   = lw_plog-objid
          act_infty                   = lw_plog-infty
          act_subty                   = lw_plog-subty
          act_begda                   = lw_plog-begda
          act_endda                   = lw_plog-endda
          act_pnnnn                   = lw_plog
          suppress_dialog             = '2'
          act_vtask                   = 'S'
          act_commit_flg              = space
        importing
          act_ok_code                 = lw_ok_code
          act_pnnnn_out               = lw_plog
          act_mess_info               = lw_msg
        tables
          act_hrtnnnn                 = <lf_1xxx>
        exceptions
          infty_not_valid             = 1
          no_plvar                    = 2
          object_not_defined          = 3
          otype_not_valid             = 4
          no_authority                = 5
          action_rejected             = 6
          no_gdate                    = 7
          fcode_not_supported         = 8
          others                      = 9 .
act_commit_flg is initial...however, the record is written to the database, why?
Regards,
Rocco

Hi Jozef,
I have find only a solution, use act_vtask = 'B' and act_commit_flg = space for test, when i want to write the change I'm using act_vtask = 'D' and act_commit_flg = 'X'.
Regards,
Rocco

Problems with PObject::destroy(void*) and commit after this

Hi there
I have some problem with delete garbage objects.
For example:
I create my object
MyObject * o = new (conn,"MY#TABLE") MyObject();
if (some_condition)
PObject::destroy(o);
delete o; //this work well
//but after this
conn->commit();
I have got the error
OCI-21710: argument is expecting a valid memory address of an object
help me anybody
can I delete/destroy object if one has been init over new (conn,table)
and absent problem with commit after this ?

Thank you for answer
but what you mean about this code ?
MyObject * o = new (conn,"MY#TABLE") MyObject();
if (some_condition)
o->markDelete();
PObject::destroy(o);
delete o;
//but after this
conn->commit();
This is work without error.
Message was edited by:
pavel

Problem with sqlldr and commit

Hi,
i have a problem with sqlldr and commit.
I have a simple table with one colum [ col_id number(6) not null ]. The column "col_id" is primary key in the table. I have one file with 100.000 records ( number from 0 to 99.999 ).
I want load the file in the table with sqlldr ( sql*loader ) but i want commit only if all records are loaded. If one record is discarded i want discarded all record of file.
The proble is that in coventional path the commit is on 64 row but if i want the same records of file isn't possible and in direct path sqlldr disable primary key :(
There are a solutions?
Thanks
I'm for the bad English

This is my table:
DROP TABLE TEST_SQLLOADER;
CREATE TABLE TEST_SQLLOADER
( COL_ID NUMBER NOT NULL,
CONSTRAINT TEST_SQLLOADER_PK PRIMARY KEY (COL_ID)
This is my ctlfile ( test_sql_loader.ctl )
OPTIONS
DIRECT=false
,DISCARDMAX=1
,ERRORS=0
,ROWS=100000
load data
infile './test_sql_loader.csv'
append
into table TEST_SQLLOADER
fields terminated by "," optionally enclosed by '"'
( col_id )
test_sql_loader.csv
0
1
2
3
99999
i run sqlloader
sqlldr xxx/yyy@orcl control=test_sql_loader.ctl log=test_sql_loader.log
output on the screen
Commit point reached - logical record count 92256
Commit point reached - logical record count 93248
Commit point reached - logical record count 94240
Commit point reached - logical record count 95232
Commit point reached - logical record count 96224
Commit point reached - logical record count 97216
Commit point reached - logical record count 98208
Commit point reached - logical record count 99200
Commit point reached - logical record count 100000
Logfile
SQL*Loader: Release 11.2.0.1.0 - Production on Sat Oct 3 14:50:17 2009
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Control File: test_sql_loader.ctl
Data File: ./test_sql_loader.csv
Bad File: test_sql_loader.bad
Discard File: none specified
(Allow all discards)
Number to load: ALL
Number to skip: 0
Errors allowed: 0
Bind array: 100000 rows, maximum of 256000 bytes
Continuation: none specified
Path used: Conventional
Table TEST_SQLLOADER, loaded from every logical record.
Insert option in effect for this table: APPEND
Column Name Position Len Term Encl Datatype
COL_ID FIRST * , O(") CHARACTER
value used for ROWS parameter changed from 100000 to 992
Table TEST_SQLLOADER:
100000 Rows successfully loaded.
0 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
Space allocated for bind array: 255936 bytes(992 rows)
Read buffer bytes: 1048576
Total logical records skipped: 0
Total logical records read: 100000
Total logical records rejected: 0
Total logical records discarded: 0
Run began on Sat Oct 03 14:50:17 2009
Run ended on Sat Oct 03 14:50:18 2009
Elapsed time was: 00:00:01.09
CPU time was: 00:00:00.06
The commit is on 992 row
if i have error on 993 record i have commit on first 992 row :(
Edited by: inter1908 on 3-ott-2009 15.00

Problem with commit

Similar Messages

Maybe you are looking for