Skip to Content
author's profile photo Former Member
Former Member

Newbie question on transaction integrity

I am calling an RFC which, during its execution, updates a Z_TABLE...but I cannot control the commit on the Z_TABLE. Every time I add a row, and do not commit from Jco, the row remains added.

Why is this ?

How do we workaround this problem ?

Must the RFC manually enqueue the data into a temp table until I commit ?

Thanks in advance !

Mark

Message was edited by: Mark Côté

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jun 23, 2004 at 06:12 PM

    Hi Mark,

    one possibility for this behaviour is, that the RFC or some function module called by the rfc does a commit work. If so you have no chance beside changing the "bad" fm.

    Hope that helps.

    Regards

    Stefan

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Stefan,

      This is the code that is in the RFC: It seems that

      as soon as the RFC is terminated, a commit is called

      on the table:ysyme001.

      FUNCTION YBAPI_BUPA_ADDRESS_ADD.

      .... some stuff, then

      tables: ysyme001.

      ysyme001-mandt = '350'.

      ysyme001-char1 = '1111111116'.

      ysyme001-char2 = '1111111117'.

      insert ysyme001.

      ENDFUNCTION.

      Thanks !

      Mark

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.