Skip to Content
avatar image
Former Member

Implicit Commits and SAP LUW

I am looking at a practice question for the ABAP certification exam. It asks:

Which statements would conclude a SAP LUW?

a. MESSAGE S101.

b. CALL TRANSACTION

c. ROLLBACK WORK

d. COMMIT WORK.

The answer key says c and d are correct. But I also said a, since the MESSAGE statement will cause an implicit commit.

Any comments?

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    Apr 21, 2006 at 03:22 PM

    Hi Jerry,

    answer a) says Success message ie <b>S101</b>.Success messages are not implicit commit.

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 21, 2006 at 03:22 PM

    An error message may rollback a LUW but not a success message.

    Hence 'a' is not an answer.

    Regards,

    Ravi

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 21, 2006 at 03:25 PM

    hi,

    Look it this link for interview question

    SAP, ABAP interview question and answers

    http://www.geocities.com/sap_interviewquestions/

    D is th correct answers

    Regards

    Manoj

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 21, 2006 at 03:28 PM

    Hi Jerry,

    Please go through the following link.

    SAP" target="_blank">http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4bfa79e11d1950f0000e82de14a/content.htm">SAP LUW

    Mark helpful answers.

    Regards,

    Amit Mishra

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 16, 2006 at 11:48 AM

    Not all messages type ends the LUW. Only the dialog message will do it. The key is whenever the system has to wait; it trigger implicit commit.

    Example1 ...

    INSERT sbook FROM TABLE it_sbook[].

    MESSAGE s836(sd) WITH 'Test Message'. "Message type S

    ROLLBACK WORK.

    You DONT GET data from it_sbook in the table sbook at the end. (because the program run through message type S and do the rollback first)

    Example2 ...

    INSERT sbook FROM TABLE it_sbook[].

    MESSAGE i836(sd) WITH 'Test Message'. "Message type I

    ROLLBACK WORK.

    You GET data from it_sbook in the table sbook at the end.

    (message type i trigger implicit commit before you process the statement ROLLBACK WORK)

    Example3 ...

    INSERT sbook FROM TABLE it_sbook[].

    MESSAGE e836(sd) WITH 'Test Message'. "Message type E

    ROLLBACK WORK.

    You still GET data from it_sbook in the table sbook at the end.(even message type E also trigger implicit commit because once it comes to message E statement it shows the error message immediately. so, its the interruption)

    Example4 ...

    INSERT sbook FROM TABLE it_sbook[].

    WAIT UP TO 2 SECONDS.

    ROLLBACK WORK.

    In this case, you also GET data from it_sbook in the table sbook at the end. And that the conclusion... Everytime program has to wait, implicit commited is inititated..

    -


    However, i also have a question about the implicit commit.

    According to SAP standard training course. (BC414: Database Update Col.2003/Q2)

    Implicit Commit happened in 4 cases.

    1. display a screen <-- That's true for sure

    2. send a DIALOG message <-- Yes. see above examples

    3. sync/async RFC <-- Yes. I have tried that.

    4. CALL TRANSACTION or SUBMIT <-- ??? I dont think so!

    I have created the program to test the CALL TRANSACTION / SUBMIT and it never really trigger an implicit commit !!

    If anybody have any idea about this, pls kindly share. Thank you in advance

    P.S. its the first time i posted the messsage here ... :P

    Add comment
    10|10000 characters needed characters exceeded