Deprecated feature: Inventory monitor

Deprecated: The inventory monitor time-triggered transaction is deprecated.

This time-triggered transaction monitors inventory availability at ship node level. It raises alerts at the ship node level when the available inventory exceeds or drops below the configured quantities.

This monitor uses the OPEN_ORDER demand type to calculate available inventory at a given node. All supplies assigned to a supply type that is considered by the OPEN_ORDER demand type are considered. For more information about configuring inventory supply and demand considerations, refer to the Configuring Sterling Global Inventory Visibility topic.

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. Inventory monitor attributes
Attribute	Value
Base Transaction ID	INVENTORY_MONITOR
Base Document Type	General
Base Process Type	General
Abstract Transaction	No
APIs Called	`checkAvailability()`

Criteria parameters

The following are the criteria parameters for this monitor:

Table 2. Inventory monitor criteria parameters
Parameter	Description
Action	Required. Triggers the transaction. If left blank, it defaults to Get, the only valid 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.
InventoryOrgCode	Optional. Valid inventory owner organization. Organization to process in this run. If not passed, all inventory organizations are processed.
Collect Pending Jobs	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.
AllowedOverriddenCriteria	If this parameter is set to Y, the overriding value for the agent criteria parameters can be provided in the command line in the following format when triggering the agent: `<AgentCriteriaAttribute> <OverriddenValue>`
ShipNodes	Optional. Comma-separated list of valid ship nodes that should be processed in this run. If not passed, all the ship nodes are processed.
Colony Id	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 <INSTALL_DIR>/xapidocs/api_javadocs/dbd/INVENTORY_MONITOR_dbd.txt.