Validation Configuration

By using the Validation Configuration, an action can be triggered based on a condition.

The Validation Configuration can be opened in the following ways:

- Right-click, Usability Package Icon > "Setup Overview" > "New Validation".

Administration > Add-Ons > B1 Usability Package > Module Configuration > Beas customizing Administration.

A validation configuration is always window-related. Therefore, the corresponding window must be open.

Options for Validation Configuration:

- Actions while loading, saving, adding, or deleting data, e.g. checking whether an entry is correct.

- Actions while editing a field e.g. checking content.

- Actions by mouse-clicks (Left, right, and double-click with Shift, Ctrl, or a combination of both).

- Actions by key stroke, also in combination with Shift, Ctrl, or both.

Furthermore, non-window related processes are customizable.

- Customization of processes e.g. creating work orders or time receipts in work orders.

- Determination of accounts, cost types for WIP (Work In Progress) bookings etc.

Window Structure

A validation consists of 3 areas:

1. Description of the validation (describe the validation),

2. Description of the event to be monitored (define the event),

3. Description of the activity that has to be executed (define the action).

Validation_config_Expl

How Is A Validation Created?

1. Create a new validation by right-clicking, then click on the Usability Package Icon via "Setup Overview" and then "New Validation".

2. Select the window that is related to this validation.

3. Enter a name that describes the valuation configuration.

4. Select the event.

5. Select the the remaining fields according to event type.

6. Define the action that has to be executed.

For more information go to: Form, Datawindow, Items.

Validation Definition

Field

Description

Unique ID for for the validation – Definition.

If an ID is not set manually, the system assigns one automatically.

Window ID

ID of the window for which the defined validation should apply.

Tip: The window specified here must be open in order to change its properties.

Go to Form, Datawindow, Items.

Description

Text field where the validation can be described in further detail.

User (empty=All)

You can indicate the validity of the definition / users in the Item Placement Tool, function buttons, and validation configuration.

The following rule applies:

Field is empty: There is no check

Incl. User: The definition is only valid for the specified users

Excl. User: The definition applies to all users except for the users specified here

A user can be:

- SAP User

- SAP user group

- Personnel (Menu: Human Resources > Personnel)

In the selection window the corresponding user can be defined and taken over by the ("transfer button")

User_personnel
Window bde_personal_browse.psr

Category

Defines the related category.

Trigger

Field

During event

Description

DataWindow

Item Event, DW Event

Standard is dw_1, can be dw_2.... dw_7

For buttons, right click popup menu or toolbar: always "dw_master"

Element

Item Event

See event "click" and basic introduction Form, Datawindow, Items.

Buttons, right click popup menu, tool bar

For Buttons use object name from the Button. You can see the object name in debug window

Insert in DataWindow always "dw_master" and in Element the object name of the Button / Function, example "edit:" for open entry

Window Mode

Item Event, DW Event, Key Down

Determines in which window modes this event should be checked: ADD, OK, UPDATE, or valid for more than one window mode e.g. ADD/OK/UPDATE. Standard setting is "All".

Event

All

Item Events

Event

Description

Click [left mouse click down]

Choose the DataWindow and the item that has to be clicked on in order to trigger the validation.

If an element which is not an input field is checked, the input field can be selected and the corresponding extension for the corresponding field e.g. -t for the corresponding text field or _p for the Dropdown Icon or _pp for the golden arrow.

fieldname

For more information see: Form, Datawindow, Items.

right-click (right mouse click down)

Right-click on an item.

Double Click

Double-click on an item.

Item changed

The field content of an item was changed.

Got Focus

Item gets in focus .

Key Down

When a key or a combination of keys was pressed.

DW Events

Event	Description
DW Load	DataWindow has been loaded.
DW Insert	A line has been added in the DataWindow.
DW Deleted	A line has been deleted in the DataWindow.
DW Row Changed	There has been a row change in the DataWindow.

Form Events

Event	Description
Form Load	The form is being loaded.
Form Closing	The form is being closed.
Form Add	The "Add" – process is running in the form.
Form Update	The "Update" – process is running in the form.
Form Delete	The "Delete" – process is running in the form.

Special Events

Event	Description
Work order management	Event in the module Work order management.
Stock management	Event in the module Stock management.
MRP	Event in the module Material Resource Planning.
QC Management	Event in the module Quality Control Management.
FDC	Event in the module time Factory Data Capture, time recording.
beas menu	Event in the module "load menu" (Gets triggered when the Beas menu is loading).
SAP B1 Sales	Event in the module SAP B1 Sales.
SAP B1 Purchase	Event in the module SAP B1 Purchase.

Sub event

Special Events

This field is only visible when a "Special Event" has been selected, such as:

Work order management

Stock management

MRP

QC management

FDC

beas menu

SAP B1 Sales

SAP B1 Purchase

These events are not window-related and should not be assigned to a user.

Here the corresponding sub event can be selected.

Key

Key Down

Only visible during the event "KeyDown".

The key can be selected here. The additional key should also be selected.

Modifier

Key Down, Item Event, DW Event

Determines which additional key must be pressed in order to carry out the action, e.g. just a combination with Shift or Crtl, or a combination of both.

Block Event

All

When active, all subsequent systems are blocked. This has different effects depending on the event.

Condition

Field

Description

No condition, just execute function

With this setting the Universal Function that should be executed can be directly selected. Both a Beas function and a B1UP Universal Function can be selected.

Script

The Beas script defined here will be run directly.

validation_bscript

This is the easiest way to respond to events: beas script.

As soon as the event occurs, the code stored there is executed directly.

Various wizards facilitate the creation of the script.

Return:

If the script ends with "return failure", then the subsequent processes in the event is not executed and the entire event is aborted (e.g. Delete, Update, Close)

Principle: by returning an SQL statement, it is determined which universal function should be called.

1. First the universal function has to be defined.

2. An SQL statement is defined, which returns a value depending on the condition. Using the "Magic Wand" function makes the SQL statement easy to create.

3. The table below defines which universal function should be executed.

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