You might want to check /USI/BAL_DEMO and its subpackages. At the moment two demos exits.

Simple demo report

Report: /USI/BAL_DEMO_01
Transaction: /USI/BAL_DEMO_01

Includes a very simple example that covers all the steps from the creation of a logger to its destruction.

Complex demo report

Report: /USI/BAL_DEMO_02
Transaction: /USI/BAL_DEMO_02

A more complex report that mimics a ToDo list.

The demo consists of a report, that implements a "stupid" UI without any business logic and the global class /USI/CL_BAL_DEMO_TO_DO_LIST that is acting as the business logic layer of the application.

The custom user commands of the ALV grid will execute the use cases of this demo:

• Refresh
• Add task
• Edit task
• Delete task(s)

They will be handled by method lcl_main_screen->on_user_command (Local class of the report). If you want to analyze the log writer integration this method is a good place to start.

Depending on the flag "Start log in main program" the main program will open or not open a log before delegating the call to the global class, that will try to open a log in any case.

The different use cases are using different subobjects for their logs.