Security Audit Log - Event AUY folder-path\file-name variable too short

[Former Member]

Hello Experts,

I am trying to fulfill an auditing requirement to log all opening of attachments from GOS in the SAP ABAP system.

We are using a combination of RAL and SAL to gather the data we require, however.....

With SAL we use the event AUY (Download &A Bytes to File &C) to log the file name which is opened from the GOS attachment list in the SAP ABAP system, but the record in the SAL log file and SM20 show the file path\name of the opened file as being truncated, (and thus we cannot actually identify the full file name which has been downloaded).

The output into the SAL logfile is similar to this:

C:\Users\User_Name\Document..1_20151022113509.101_X.pdf

so we get the folder path... and the timestamp... but not the actual distinguishing name of the file which was originally attached.

Does anyone know how to prevent SAL and event AUY from truncating the file path\name which is saved into the SAL logfile or extend the relevant field length.... or have ideas on an alternate solution?

Thanks in advance,

Kind regards,

Patrick.

[Former Member]

If you are lucky then it is just an ALV grid display width restraint. Double-click the record to see whether more is displayed?

If not, then the recording is truncated. Is the length 225?

Within the application you can also display the log of documents in tcode OA_LOG_VIEW_DOC. For the download option you might have to use the RAL (Read Access Logging) option - though mind you that might be truncated as well. Uploads also have a limit - the file path cannot be too long in the directory to reach it, otherwise the ABAP typing of the field might not reach it.

Cheers,

Julius

[Former Member]

Hi Julius,

Thank's for you response. Sadly its not the ALV grid display restraint as the data displayed is from the SAL *.AUD log file. Thus its the way which the log file is populated with data that would need to be changed.

You are correct that the record is truncated. The length is 64, as per doc describes, and from having a look in the data dictionary for RSAUENTR2 structure confirms this too.

For SAL to log the full length folder path and file name, I am guessing we will need one of our abappers to write an enhancement/mod to increase the field length.

You have mentioned that RAL could be used for recording downloads? So far I have not been able to find this option. Would you have any tips on how to log downloads/opening of attachments in RAL?

As an example, we are using a transaction like VL02N which then has an attachment list. The user opens the attachment list, and then double clicks an attachment to view it.

We are able to use RAL to record the viewing of the attachment list... but not able to record the action of actually opening one of the attachments.

Currently we are using the dynpro recording option for this... should I be looking in another area like RFC logging or?.... any tips on this would be helpful to be able to use RAL to log the opening of an attachment or downloading of data from the ABAP system. (Possibly I should create a new SCN question for this, as my original question is about SAL)

Regards,

Patrick

[Former Member]

Then it looks like you are not going to be able to influence the SAL in this regard. There are kernel functions behind the collection and you will not be able to enhance them.

RAL docs there are a few of them here on SCN. It was a customer development originally as far as I know, but then SAP decided to make a product out of it (so it has a price tag on it).

Personally I would recommend that you open an OSS message with SAP and request that the field type be changed to a longer one and that SAL also sends a longer path. 255 is the normal length for type FILE so they should have taken that in the first place.

Little tip: it being a Friday afternoon, use priority LOW. Those are like little snacks before going into the weekend. Other priorities will be dealt with next week...  🙂

Cheers,

Julius

[Former Member]

Hi Julius,

If you are referring to Read Access Loggin when talking about RAL, this is a functionality part of the SAP NetWeaver AS basis install and not a seperate product 😉

Maybe you mixed that with ETD, which is developped by the same team? Although this was not a customer development in the beginning either. There is still a custom development solution called UI logging available, however this is a completly different product.

Kind regards,

Patrick

[Former Member]

Ah, the plot thickens..  I did not realize there are 3 different flavours of it... 🙂

Perhaps you can comment then on what is best appropriate for what Patrick is looking for -> a log of which document in SAP was opened.

Cheers and enjoy the weekend

Julius

[Former Member]

Had a further look around and found SAP Note - http://service.sap.com/sap/support/notes/1819317

Looks like SAP have performed enhancements to other SAL events for the exact same purpose as the issue I am encountering (64 char field length not long enough).

I have logged a support request with them to perform the same enhancement for the AUY SAL event.

[Former Member]

Hi Patrick,

Thanks for the heads up regarding the other products (ETD and UI Logging).

Had a quick look at both, then found we are not licensed for either, and the client has a strong preference for me to implement a solution within the range of products they are currently licensed for.

Also found this  - http://service.sap.com/sap/support/notes/2082497

Talks about the deficiency of RAL for logging DMS activities, and that the solution is to just follow the standard SAP webpage for configuring RAL.... but I don't really see where there is any further instructions about configuring RAL for DMS activities there.... (unless I am blind, which I am happy to be labelled as such)

I will do some testing with ArchiveLink logging and see what I can find there.

Regards,

Patrick.

[Former Member]

Dear Patrick,

the solution is already available, note http://service.sap.com/sap/support/notes/2234569
I also did update your support request.

Regards,
Uwe

[Former Member]

I have implemented the SNOTE, given it a quick test and it looks to be working fine.

Thank's for the quick work!!

[Private_Member_69416]

Hi

SAL field size for "Variable message data" is 64.

AUY store there file size, mode (BIN),truncated path and separators.

Regards

Przemek