BEAS Transaction Notification – Centralized Validation Mechanism for BEAS Transactions
Description
SAP Business One provides the SBO_SP_TransactionNotification, which allows customers to implement business rules and block transactions before they are committed to the database.
However, BEAS uses its own database tables (BEAS_*), which are created directly in the database and are not SAP Business One UDTs/UDOs. Therefore, operations performed on these tables do not go through the standard SAP Business One SBO_SP_TransactionNotification.
This creates an important limitation for customers who need to implement mandatory business rules on BEAS data.
Currently, BEAS User Events can be used for some customizations, but they do not provide the same guarantee as a centralized transactional notification mechanism. Depending on the process, screen, or internal BEAS workflow, a User Event may not be triggered in every possible scenario.
Using database triggers directly on BEAS tables is also not an appropriate solution, as this introduces unsupported database customizations and may create issues with maintenance, upgrades, or supportability.
Requested Functionality
We would like to request a native BEAS mechanism equivalent, in concept, to the SAP Business One SBO_SP_TransactionNotification.
This mechanism should be triggered for operations performed on internal BEAS tables and allow customers to implement custom validations before the transaction is committed.
Ideally, the mechanism should provide:
- Identification of the affected BEAS table or object;
- The type of operation being performed (
INSERT,UPDATE,DELETE, etc.); - Identification of the affected record;
- Access to the values involved in the operation;
- The ability to execute custom validation logic;
- The ability to return an error and prevent the transaction from being committed;
- The ability to provide a customized error message to the user;
- Execution within the same transaction context, so that a failed validation prevents the changes from being committed.
Conceptually:
BEAS Transaction
↓
BEAS Transaction Notification
↓
Custom Validation
↓
┌──────────────────┬
│ │
OK ERROR
│ │
↓ ↓
Continue Cancel / Rollback
transaction + Error Message
Example Use Case
For example, a customer may have a business rule stating that a specific BEAS operation must not be saved when a certain condition is not fulfilled.
In this scenario, the validation needs to occur before the transaction is committed, regardless of which BEAS screen, process, or internal workflow originated the change.
The objective is not simply to detect an invalid state after it has been created, but to ensure that the invalid state can never be persisted.
Benefits
Such a mechanism would allow customers to implement critical business rules in a centralized and reliable way, without having to:
- Create database triggers directly on BEAS tables;
- Depend on specific BEAS User Events;
- Implement the same validation separately for different screens or processes;
- Use unsupported methods to intercept database changes.
Question / Feature Request
Does BEAS currently provide any official mechanism equivalent to the SAP Business One SBO_SP_TransactionNotification for transactions involving internal BEAS tables and data?
If such a mechanism does not currently exist, we would like to submit this as a Feature Request.
The proposed functionality would provide BEAS with a centralized transaction notification and validation mechanism, allowing customers to implement business rules that can prevent a transaction from being committed when the required conditions are not met.
Comments
4 comments
I fully support this request, as it addresses an important need for centralized validation within BEAS. A native mechanism equivalent to SBO_SP_TransactionNotification would enable consistent enforcement of business rules, ensuring data integrity while avoiding unsupported database customizations or dependence on specific user events. This functionality would provide significant value to customers who require robust and reliable process controls.
This improvement would be extremely useful for several of my clients!!!
This feature, as a system default, adds value to the tool because it allows bringing guarantees to the client through a transaction process, which is crucial for processes that require verification and security locks in the activities performed.
What is possible can already be achieved via BEAS events?
Preventing a transaction—as one might in SAP—or intervening mid-process is sometimes impossible, because BEAS establishes its own database connection, and SAP transactions are executed in many areas. It is not possible to wrap an external transaction boundary around that.
For this reason, BEAS generally does not operate using transaction boundaries.
Of course, it would be great if SAP and BEAS behaved in the same way. But I cannot think of anything you could do with that which isn't already possible—it would simply be done in a different way.
Please sign in to leave a comment.