When running a BI session, what is "detailed/extended log" for?

Question

Hello all,
I couldn't find any information about "detailed log" checkbox (forum, notes, online help, sap library, google).
It is displayed in a popup when we run a BI session from SM35 transaction. It's also the LOGALL parameter ("extended log") of RSBDCSUB program.
By debugging the system, I noticed that it was used only with All-screen and Error-only display modes. In No-screen mode, the BI session is run with detailed log on.
In All-screen and Error-only modes, the message 00355 "Transaction was processed successfully" is not stored in the log if the detailed log option is off.
Are there any other differences?
Thx a lot

Answer 1

Thx Harald, I missed it.
But unfortunately, it doesn't work as described, or there is something I don't understand. You can try with the following code which changes FR 1234567890 bank name to sy-uzeit using FI02 transaction (please create the bank before running the program), and produces both S and W messages, whatever extended log is on or off. The only difference is about the message number 00355 as I stated previously.
REPORT  zzysro_test6.
PARAMETERS p_logall TYPE flag AS CHECKBOX.
DATA ls_bdcdata TYPE bdcdata.
DATA lt_bdcdata TYPE TABLE OF bdcdata.
DEFINE d.
  clear ls_bdcdata.
  ls_bdcdata-program = '&1'.
  ls_bdcdata-dynpro  = '&2'.
  ls_bdcdata-dynbegin = '&3'.
  append ls_bdcdata to lt_bdcdata.
END-OF-DEFINITION.
DEFINE f.
  clear ls_bdcdata.
  ls_bdcdata-fnam = '&1'.
  ls_bdcdata-fval = '&2'.
  append ls_bdcdata to lt_bdcdata.
END-OF-DEFINITION.
DEFINE f2.
  clear ls_bdcdata.
  ls_bdcdata-fnam = '&1'.
  ls_bdcdata-fval = &2.
  append ls_bdcdata to lt_bdcdata.
END-OF-DEFINITION.
d sapmf02b  0100  x.
f bdc_cursor  bnka-banks.
f bdc_okcode  /00.
f bnka-banks  fr.
f bnka-bankl  1234567890.
d sapmf02b  0110  x.
f bdc_cursor  bnka-banka.
f2 bnka-banka sy-uzeit.
f bdc_okcode  =upda.
DATA l_bi_qid TYPE apqi-qid.
DATA l_group TYPE apqi-groupid VALUE 'ZSRO'.
CALL FUNCTION 'BDC_OPEN_GROUP'
  EXPORTING
    group = l_group
    keep  = 'X'
    user  = sy-uname
  IMPORTING
    qid   = l_bi_qid.
CALL FUNCTION 'BDC_INSERT'
  EXPORTING
    tcode      = 'FI02'
  TABLES
    dynprotab  = lt_bdcdata.
CALL FUNCTION 'BDC_CLOSE_GROUP'.
* now go to SM35 to start the session in A, E or N display mode
* (N mode always use extended log on, whatever checkbox is ticked or not)
* There are 2 messages issued by FI02: W210(BF00) (as the bank has been
* flagged for deletion) and S207(BF00) ("bank modified")
Edited by: Sandra Rossi on Jun 15, 2010 10:06 AM
> In sample code above, I removed call to RSBDCSUB program so that we can choose the display mode in SM35 when we execute the BI session