Quantcast
Channel: SCN: Message List - ABAP Connectivity
Viewing all articles
Browse latest Browse all 3125

Re: RFC can't set AUDITLEVEL for detail in rz15

$
0
0

Hi Ulrich,

 

I added a BAPI_TRANSACTION_COMMIT after the BAPI_XMI_SET_AUDITLEVEL, but it seemed to make no difference.  The WAIT argument should be a non-space to cause it to wait for the commit, right?   I used "X".

 

Thu Jan 21 17:04:45 2016 BAPI_XMI_SET_AUDITLEVEL > sles11sap_NPL_42 OK

Thu Jan 21 17:04:45 2016 IMPORT entries:

Thu Jan 21 17:04:45 2016 .AUDITLEVEL, RFCTYPE_NUM[1:1]:3

Thu Jan 21 17:04:45 2016 EXPORT entries:

Thu Jan 21 17:04:45 2016 .structure RETURN

Thu Jan 21 17:04:45 2016 ..TYPE RFCTYPE_CHAR[1:0]:

Thu Jan 21 17:04:45 2016 ..ID RFCTYPE_CHAR[20:0]:

Thu Jan 21 17:04:45 2016 ..NUMBER RFCTYPE_NUM[3:3]:000

Thu Jan 21 17:04:45 2016 ..MESSAGE RFCTYPE_CHAR[220:0]:

Thu Jan 21 17:04:45 2016 ..LOG_NO RFCTYPE_CHAR[20:0]:

Thu Jan 21 17:04:45 2016 ..LOG_MSG_NO RFCTYPE_NUM[6:6]:000000

Thu Jan 21 17:04:45 2016 ..MESSAGE_V1 RFCTYPE_CHAR[50:0]:

Thu Jan 21 17:04:45 2016 ..MESSAGE_V2 RFCTYPE_CHAR[50:0]:

Thu Jan 21 17:04:45 2016 ..MESSAGE_V3 RFCTYPE_CHAR[50:0]:

Thu Jan 21 17:04:45 2016 ..MESSAGE_V4 RFCTYPE_CHAR[50:0]:

Thu Jan 21 17:04:45 2016 ..PARAMETER RFCTYPE_CHAR[32:0]:

Thu Jan 21 17:04:45 2016 ..ROW RFCTYPE_INT[4:1]:0

Thu Jan 21 17:04:45 2016 ..FIELD RFCTYPE_CHAR[30:0]:

Thu Jan 21 17:04:45 2016 ..SYSTEM RFCTYPE_CHAR[10:0]:

 

Thu Jan 21 17:04:45 2016 BAPI_TRANSACTION_COMMIT > sles11sap_NPL_42 OK

Thu Jan 21 17:04:45 2016 IMPORT entries:

Thu Jan 21 17:04:45 2016 .WAIT, RFCTYPE_CHAR[1:1]:X

Thu Jan 21 17:04:45 2016 EXPORT entries:

Thu Jan 21 17:04:45 2016 .structure RETURN

Thu Jan 21 17:04:45 2016 ..TYPE RFCTYPE_CHAR[1:0]:

Thu Jan 21 17:04:45 2016 ..ID RFCTYPE_CHAR[20:0]:

Thu Jan 21 17:04:45 2016 ..NUMBER RFCTYPE_NUM[3:3]:000

Thu Jan 21 17:04:45 2016 ..MESSAGE RFCTYPE_CHAR[220:0]:

Thu Jan 21 17:04:45 2016 ..LOG_NO RFCTYPE_CHAR[20:0]:

Thu Jan 21 17:04:45 2016 ..LOG_MSG_NO RFCTYPE_NUM[6:6]:000000

Thu Jan 21 17:04:45 2016 ..MESSAGE_V1 RFCTYPE_CHAR[50:0]:

Thu Jan 21 17:04:45 2016 ..MESSAGE_V2 RFCTYPE_CHAR[50:0]:

Thu Jan 21 17:04:45 2016 ..MESSAGE_V3 RFCTYPE_CHAR[50:0]:

Thu Jan 21 17:04:45 2016 ..MESSAGE_V4 RFCTYPE_CHAR[50:0]:

Thu Jan 21 17:04:45 2016 ..PARAMETER RFCTYPE_CHAR[32:0]:

Thu Jan 21 17:04:45 2016 ..ROW RFCTYPE_INT[4:1]:0

Thu Jan 21 17:04:45 2016 ..FIELD RFCTYPE_CHAR[30:0]:

Thu Jan 21 17:04:46 2016 ..SYSTEM RFCTYPE_CHAR[10:0]:

 

However when I dug into my notes to see what the transaction was to let me see the description of a function (se37), I noticed that se16 was useful for setting XMILOGLEVEL in the TSPOPTIONS table to 2 for testing.  In the back of my head, there's been a feeling of a missed setting somewhere.  This is it.  Once I made the change and bounced SAP, the XMI log had the desired detail.

 

 

This satisfies my immediate need, but I'm left wondering why the audit level still cannot be set.  That's valuable in the field.   I think the question is still unsolved.

 

Thanks!

Rich

 

 




Viewing all articles
Browse latest Browse all 3125

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>