Previous Topic: SUCCESSMSG Statement—Specify Success Message for ABAPNext Topic: TABLENAME Statement—Specify the Name of the Table to Monitor


TABLE_NAME Statement—Specify the Name of the Table to Monitor

The TABLE_NAME statement specifies the name of the database table to monitor for the changes specified in the Database Monitor or Database Trigger job.

Supported Job Types

This statement is required for the following job types:

Syntax

This statement has the following format:

TABLE_NAME table [CONTINUOUS(alertid)]
table

Specifies the name of the database table to monitor for changes.

Limits: Up to 100 characters; case-sensitive

CONTINUOUS(alertid)

(Optional) Specifies the identifier of an alert to be triggered when the specified database monitoring conditions occur. Defines the job as continuous. To end continuous monitoring, you must complete the job manually or cancel it. If you do not specify this operand, the job completes when the specified database monitoring conditions occur.

alertid

Specifies the alert identifier to be triggered.

Limits: 1-8 alphanumeric characters; the first character must be alphabetic

Note: The alert must have been previously defined to the scheduling manager. Not all scheduling managers support the CONTINUOUS operand.

Notes:

Example: Monitor a Table for an Update

In the following example, the table Inventory_List is monitored for an update. When an update occurs, the job completes.

AGENT CYBDB1
TABLE_NAME Inventory_List
TRIG_TYPE UPDATE

Example: Monitor a Table Continuously for the Insertion of Rows

In the following example, the table Inventory_List is continuously monitored for the insertion of table rows. When a row is inserted, the scheduling manager triggers the predefined alert INC. After the alert is triggered, monitoring resumes. To end the job, you must complete it manually.

AGENT CYBDB1
TABLE_NAME Inventory_List CONTINUOUS(INC)
TRIG_TYPE INSERT

Example: Monitor a Table Continuously for Updates

In the following example, the table Inventory_List is continuously monitored for updates. When an update occurs, if the number of units of product A has fallen below 100000, the scheduling manager triggers the predefined alert LOW. After the alert is triggered, monitoring resumes. To end the job, you must complete it manually.

AGENT CYBDB1
TABLE_NAME Inventory_List CONTINUOUS(LOW)
TRIG_TYPE UPDATE
TRIG_COND 'new.ProductA < 100000'