Working with logs

Details

Category: ABAP

Published on Monday, 23 February 2009 20:02

Written by Anon.

Hits: 6626

• APPL_LOG_DELETE With this function module you delete logs in the database according to specified selection conditions
• APPL_LOG_DISPLAY_INTERN With this function module you can analyze logs in local memory, e.g. when you have only collected log records at runtime and do not want to write to the database.
• APPL_LOG_INIT This function module checks whether the specified object or sub-object exists and deletes all existing associated data in local memory.
• APPL_LOG_READ_INTERN With this function module you read all log data whose log class has at least the specified value, from local memory, for the specified object or sub-object.
• APPL_LOG_SET_OBJECT With this function module, you create a new object or sub-object for writing in local memory. With a flag you can control whether the APPL_LOG_WRITE_... messages are written in local memory or are output on the screen.
• APPL_LOG_WRITE_DB With this function module you write all data for the specified object or sub-object in local memory to the database. If the log for the object or sub-object in question is new, the log number is returned to the calling program.
• APPL_LOG_WRITE_HEADER With this function module, you write the log header data in local memory.
• APPL_LOG_WRITE_LOG_PARAMETERS With this function module, you write the name of the log parameters and the associated values for the specified object or sub-object in local memory. If this function module is called repeatedly for the same object or sub-object, the existing parameters are updated accordingly. If you do not specify an object or sub-object with the call, the most recently used is assumed.
• APPL_LOG_WRITE_MESSAGE_PARAMS With this function module you write a single message, with parameters, in local memory. Otherwise the function module works like
• APPL_LOG_WRITE_MESSAGES With this function module you write one or more messages, without parameters, in local memory.
• APPL_LOG_WRITE_SINGLE_MESSAGE With this function module you write a single message, without parameters, in local memory. If no header entry has yet been written for the object or sub-object, it is created. If you do not specify an object or sub-object with the call, the most recently used is assumed.

• BAL_CNTL_CREATE Create Control for log display
• BAL_CNTL_FREE Release Control
• BAL_CNTL_REFRESH Put new data in log display
• BAL_DB_DELETE Delete logs from the database
• BAL_DB_DEQUEUE Unlock log
• BAL_DB_ENQUEUE Lock log
• BAL_DB_LOAD Load logs from the database
• BAL_DB_LOAD Load log(s)
• BAL_DB_SAVE Save logs in the database
• BAL_DB_SAVE Save log(s)
• BAL_DB_SAVE_PREPARE Prepare save
• BAL_DB_SEARCH Find logs in the database
• BAL_DSP_LOG_DISPLAY Display messages in memory
• BAL_DSP_LOG_DISPLAY Display Log
• BAL_DSP_LOG_PARAMETERS Either output extended long text or call a callback routine (based on the data in BAL_S_LOG-PARAMS)
• BAL_DSP_LOG_TECHNICAL_DATA Output all log header data
• BAL_DSP_MSG_LONGTEXT Display message long text
• BAL_DSP_MSG_PARAMETERS Either output extended long text or call a callback routine (based on the data in BAL_S_MSG-PARAMS)
• BAL_DSP_MSG_TECHNICAL_DATA Output technical data of a message such as work area, error number, etc.
• BAL_DSP_OUTPUT_FREE End output
• BAL_DSP_OUTPUT_INIT Initialize output
• BAL_DSP_OUTPUT_SET_DATA Set dataset to be displayed
• BAL_DSP_PROFILE_DETLEVEL_GET Message hierarchy in DETLEVEL
• BAL_DSP_PROFILE_NO_TREE_GET Display without tree (fullscreen)
• BAL_DSP_PROFILE_POPUP_GET Display without tree (popup)
• BAL_DSP_PROFILE_SINGLE_LOG_GET Standard profile (SLG1) for one log

• < Prev
• Next >