Availability monitor

This time-triggered transaction monitors inventory availability. The Availability Monitor raises global alerts when the available inventory falls below the configured quantities on the current day, on subsequent days within the ATP time frame, and on subsequent days outside of the ATP time frame. The quantities for the days outside of the ATP time frame are determined by the maximum monitoring days. Unlike the schedule and release transactions, the Availability Monitor calculates the actual availability beyond the ATP horizon and does not assume infinite inventory.

Note: When the Promising server is being used, this transaction is not called on the Order server.

Attributes

The following are the attributes for this time-triggered transaction:

Table 1. Availability monitor attributes
Attribute Value
Base Transaction ID ATP_MONITOR
Base Document Type General
Base Process Type General
Abstract Transaction No
APIs Called None

Criteria parameters

The following are the criteria parameters for this monitor:

Table 2. Availability monitor criteria parameters
Parameter Description
Action Required. Triggers the transaction. If left blank, it defaults to Get, the only valid value.
MonitorOption Optional. Specifies how to monitor inventory. Valid values are:
  • 1 - current inventory
  • 0 - inventory within and outside of the ATP time frame. This is the default value.
Number of Records To Buffer Optional. Number of records to retrieve and process at one time. If left blank or specified as 0 (zero), it defaults to 5000.
InventoryOrganizationCode Optional. Valid owner inventory organization. Organization to process in this run. If not passed, all inventory organizations are processed.
CollectPendingJobs If this parameter is set to N, the agent does not collect information on the pending jobs for this monitor. This pending job information is used for monitoring the monitor in the System Management Console.
Status The negotiation status you are monitoring.
ColonyID Required in a multi schema deployment where a table may exist in multiple schemas. Runs the agent for the colony.

Statistics tracked

None.

Pending job count

None.

Events raised

No events are raised. Individual actions associated with the monitoring rule are run.

Data published to the actions is AVAILABILITY_MONITOR_dbd.txt.