Skip to Content

SLG1 specific expire date for FIBL (FEB_BS)

Hello.

We have a lot of entries in SLG1 and want to start deleting them. A lot of entries results from object fica and therefor we can define an expire date in each transaction, so that we are able to ascertain the time to delete the log-entries.

But for our object fibl i do not know where i can set the expire date. Therefor in SAP standard the date 31.12.9999 (ddmmjjjj) is set. How is it possible to define an own expire date?

Thanks a lot,
Kind regards
Thomas

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Aug 08, 2017 at 12:27 PM

    Hi Thomas,

    Regarding deletion of logs (SLG1), a lot of useful information is given on Note:
    #195157 - Application log: Deletion of logs

    Expiration date can be seen ALDATE_DEL field from BALHDR table. This is set by the application that calls the application log tool. If the application does not set an expiration date, it's set expiration date DEC/31/9999, which means that logs will remain in the system.
    The expiration date does not mean that logs that have reached the expiration date are automatically deleted. It controls the deletion of logs when you call the deletion report SBAL_DELETE (transaction SLG2) and during archiving (archiving object BC_SBAL).


    The indicator DEL_BEFORE, a field also from BALHDR, determines whether or not a log is allowed to be deleted or archived before the expiration date is reached.
    DEL_BEFORE = SPACE means that the log is allowed to be deleted or archived before the expiration date is reached.
    DEL_BEFORE = X means that the log is only allowed to be deleted or archived once the expiration date has been reached.

    Regarding your query, the expiration date cannot be set by the end user; this is done from application perspective. When trying to delete logs you should also check not only expiration date but also del_before information, to check if the log is allowed to be deleted (even if expiration date has not yet been reached).

    Regards,
    Raquel

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Raquel,

      the informations are not correct. Here are two examples, first one (FPY1) the end user has an possibility to set an expiration date, second one (FF.5) you're right, there is no possibilty.

      Now I need an option to set a specific date for FF.5. In BALHDR is - as you say - ALDATE_DEL = DEC/31/9999 and DEL_BEFORE = blank. So for starting SBAL_DELETE there is no information which logs could be deleted and which not.

      In best case both examples would set an ALDATE_DEL and maybe a DEL_BEFORE and SBAL_DELETE could select for all entries in BALHDR which logs can be deleted and which not. For FPY1 it is working like that at the moment, but for FF.5 not.

      Kindly regards,
      Thomas

      fyp1.png (28.8 kB)
      ff5.png (37.0 kB)
  • Sep 07, 2017 at 08:38 AM

    Hi Thomas,

    As the expiration date is done from application perspective; in first case (FPY1) application allows end user to set manually and on second case (FF.5) application does not allow. This second opciton is the most common.

    In the case of FF.5 you mentioned that it has ALDATE_DEL = DEC/31/9999 and DEL_BEFORE = blank. This means that, even if expiration date is in year 9999, logs can be deleted (DEL_BEFORE = SPACE means that the log is allowed to be deleted or archived before the expiration date is reached).

    For transaction SLG2, used to delete logs, you can select based on Expiry date:
    - Only logs which hve reached thier expiry date
    - also add logs which can be deleted before the expiri dayte

    You can also delete them; or only calculate how many. This will show you how many logs cna be deleted.

    Regards,
    Raquel

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Thomas,

      Expiration date (field ALDATE_DEL) is decided by each application that calls the application log tool; as different objects have different dates. It's application decision to define it explicitly, or leave it by default to DEC/31/9999.

      Regards,
      Raquel