System information

The Debug-window has the following functions:

- Display table and column name of current column

- Display form name / window name

- Display executed Beas - scripts

- Display local and global initialized Beas - variables

- Display SAP Business One events

- Execute Beas - scripts

Overview Debug Functions

Send Debug Log to Support

Display field names

debug_fieldnames

The system information is displayed in the first row of the debug window if a Beas-window is currently opened.

Information on the current field is displayed (where the mouse cursor is)

1. Form-Number (dw_1, dw_2, .. dw_6)

2. "item" - as note, if it is an item of a form

3. Field name

4. Field type

5. "Table:" + Table name, linked to the field

6. Form name. Generally a PSR-File + folder name

In the Debug window you can view and edit all current events, SQL statements or scripts. Events are displayed in separate rows and in different colors.

Events on Level 1 are displayed with a yellow border around the window (see image below) which changes to red once having switched to Level 2 and 3.

The color codes of the events are as follows:

Green: reading settings

Violet: calling functions

Orange: customized function

Red: error

Grey: window-specific event

PATH: View > System information or Ctrl+Shift+i

Click open a row to view the source code in an editor:

debug_window

Window beasgui_sbo.psr

The tabs of the System Information window

The tabs of the Debug Information are located vertically on the left side of the window.

Vertical tabs on the left	Meaning
Protocol	Protocol of all events
Script	Enter scripts
Item	Press Ctrl and move mouse on the object to see more details
Variable	Display global and local variables
Events	Enter events
Settings	Settings for Debug-window

Columns	Meaning
Area	Area of the event: window event, SAP-event, SQL statement ...
Command	Executed statement
CPU	Duration in milliseconds between this and the preceding entry
Windowname	Displays the name of the latest opened window

Protocol

The debug log can log every executed SQL command, Script line, Setting Read/Changes and many more

The line of buttons located on the bottom of the window in the Protocol tab + their meaning:

Button below	Meaning
	Show details for current line
	Start debug log
	Stop debug log
	Create Printscreen of the current window
	Insert comment in debug log
	Delete current row
	Upload and create URL string to clipboard. You can insert This URL string in your ticket or send it as a link in email and other messaging systems. See Debug log HTML string
	Show as formatted HTML string. See Debug log HTML string
	Reset Protocol
Level 1/2/3 switch	Filters which events to be displayed: Level 1 – only events, SQL-Statements and other colored rows Level 2 – additionally, beas-script without Resize, Timer and various system scripts Level 3 – everything
Search field with two blue arrows	Enter search term and use the arrows to search in both directions.
	Product news and general info
	Questions and answers
	Open Beas feature request and sharing ideas in Boyum Helpcenter

Script

Create small scripts and execute this directly in the current window

In Tab Settings you can define the font size

Button below	Meaning
Execute in system window	The currently entered script is executed in displayed window
Exec SQL	Marked section is transferred to SQL window and executed there
Editor	Open extended editor
Blue question mark	Link to Beas script Documentation
Arrows	Switch between up to 10 different sources. These sources are saved by Station
Dropdown beas script / macro	Execute the script as "Beas script" (empty / default = Beas script) or macro script

Item

Press Ctrl and move mouse over the object for more details

Variable

Display all variables from current window:

Button below	Meaning
Local	All active variables in the current window
Global	All global variables
Timer on / off	Activate timer to update the list of local variables continuously
Gui-Window	Only in SAP B1 environment: all active windows are displayed

Events

Display all declared functions and events:

Button below	Meaning
Refresh	Update the list
Log other event	Check box option if you need the log of other events

Settings

Debug_Window_2020_06

Window beasgui_sbo.psr

Define Debug settings and Filter

Buttons / Fields

Meaning

Full text filter

Enter to log only entries containing the entered word.

DB Protocol

Used to view log in case of program crash:
1. Activate DB Protocol and click "View".
2. Open a Beas form and click "View".

Information is saved in table BEAS_SYS_DEBUG with the following fields.

Field	Description
nr	continuous number
windowname	name of current window
Info	debug text
sqlinfo	current SQL info
modulobject	function

To view the log, execute SQL-statement:

select * from "BEAS_SYS_DEBUG"

Note: Open transactions are closed after each entry . This can change the program behavior.

Only current window

Log only current window

Show Windowevents, SQL, Window focus, Setup

Here you can select filters which type of information are to be displayed in the protocol: Window events, SQL, Window focus and Setup information.

DB Reset

Delete protocol.

View

View protocol.

Transparent Protocol %

Window is displayed transparently, if it loses the focus. Enter percentage for active tab "protocol".

Transparent Script %

Window is displayed transparently, if it loses the focus. Enter percentage for active tab "protocol".

Font Size

Define the font size for scripting in tab "Script".

Stop beasgui

If Beas is started in terminal mode, it can be stopped here.

Start Record Macro

Generate a macro script in background.

Stop Macro (save into clipboard)

Stop the macro recorder and save the script in debug window.

Debug to File

If active, the right point is red and you can close the debug window. The debug2log is complete outside of the debug window.

Beas 2020.05

Load Debug File

You can choose a BeasDebug.log file. The default location is the current temp folder.

If you want to load the log file of a service, you must choose the protocol directory of this service.

This function loads the debug log in the debug window (tab Protocol).

You can select the Level (1-3) which you want to load. You can load the debug log more than once.

After loading, you can export it to HTML or upload it to Boyum Support.

Beas 2020.05

Delete Debug File

Delete the debug file selected in "Load Debug File" 2020.05

Using the Debug window outside SAP B1

It is possible to use the debug window when Beas entries are collected within a separate menu point in the Modules tab of the SAP B1 Main menu.

In this way you can get an HTML view of the debug log with images and get a clear understanding of the process.

To access debug information of a window, proceed as follows:
1. Click on the Printscreen button in the Protocol tab.
2. Mark a line and Shift + double-click on certain information you wish to edit.
3. A red rectangle appears (see image below) which can be moved with the mouse.
4. Click the Printscreen button again to access the HTML view.

systeminfo_OUTsideB1_wb

Window fert_fthaupt_browse.psr

Example:
1. Open work orders and follow the procedure above.
2. Double-click on a work order, change some of the information in the WO window, then click on the Printscreen button.
3. Repeat changing information in the WO data and click Printscreen after each change.
4. Click on to see the formatted HTML string of the process.

In this way you get a clearly understandable picture or description of an entire process in an HTML view.

Debug_log_html

The different colors help support agents to quickly analyze every click and setting performed in a chronological order in the log.

In case you need support, you can simply copy the URL address of the Debug log to the clipboard and paste it in the Boyum help page to submit a request.
The email address, the subject and a clear, detailed description of the issue are mandatory to add. First, paste the URL string of the Debug log and describe the issue in a simple way. Then, send your request to support.

Boyum_helpc_Submit_Req

Help URL: https://help.beascloud.com/beas202102/index.html?debugfenster.htm