For these defined scenarios, the system will generate an alert for handling in the Alert Control Center (ACC) program.
Background Process Time Out, alert code: API-TIME, allows you to subscribe to any or all API requests. If the API request has timed out, then you are notified by email for the API that has timed out. You can access the Alert Control Center to view and optionally dismiss this alert.
The Request ID is available in the alert. It allows for filtering / reviewing to determine if the issue of API Timeout is related to a single API request or system wide. Can be subscribed to by users.
Delivery of XML to Infor OS failure, slert code: BK-I2 OUT, is raised if an outbound BOD XML document was ready for delivery to Infor OS, but something prevented it from being delivered.
You can access the Alert Control Center to view and optionally dismiss this alert. This information is available in the alert:
You can subscribe to the API name.
Build XML Fail, alert code: ERR XMLGEN, is called/recorded if SMC600 is unable to build the outgoing XML. It is raised by the I1 background process. You can access the Alert Control Center to view and optionally dismiss this alert.
This information is available in the alert.
You can subscribe to the API name.
Connection error to Infor OS, alert code: BK-I2 CERR, is raised if the I2 background process attempted to connect Infor OS to but something prevented it from gaining a successful connection. You can access the Alert Control Center to view and optionally dismiss this alert. The ID for the database is available in the alert. You can subscribe to this value.
Imported G/L Transactions, alert code: GL-IMPORT, is called/recorded when a G/L Transaction is imported using the API. You can access the Alert Control Center to view and optionally dismiss this alert. The Imported G/L Transactions alert is sent to provide visibility that the import occurred and the transaction can be viewed in G/L Journal Inquiry, provided the user has security to access this program.
This information is available in the alert.
The Error alert is called/recorded when an error occurs in FACTS. You can access the Alert Control Center to view and optionally dismiss this alert. The Error alert is sent to provide visibility that an error occurred and the error can be viewed in System Error Inquiry, provided the user has security to access this program.
This information is available in the alert.
Auto Re-Auth of a Pre-Auth Failed, alert code: ReAuthFail, is called/raised when a pre-authorization transaction qualified for automatic re-authorization based on the customer’s settings and the # days old prompt in Credit Card Control F/M, but the attempt to re-authorize the transaction failed. You can access the Alert Control Center to view and optionally dismiss this alert, or click Respond to Exception for the option to access Order/Invoice Entry or Payment Entry. In Payment Entry, only pre-auth transactions can be manipulated.
This information is available in the alert.
Pre-auth Credit Card Transaction is Expiring, alert code: PreAuthExp, is called when a pre-authorization transaction that does not qualify for automatic re-authorization based on the customer’s settings is soon to expire. You can access the Alert Control Center to view and optionally dismiss this alert or click Respond to Exception for the option to access Order/Invoice Entry or Payment Entry. In Payment Entry, only pre-auth transactions can be manipulated..
This information is available in the alert.
ServiceHold (ALC138) notifies the user when an SO document is placed on service hold or released from a service hold. Any SO document placed on service hold or released from service hold generates the alert.
You can access the Alert Control Center (POE410) to view and optionally dismiss this alert. The alert is raised when an S4 background program, BK610, checks the svc_alert_action field in SORSOH. When a service hold alert action or service hold release alert action is issued, the alert is raised and users are directed to Sales Order Review (SOE230), based on the type of alert.
Note: New orders, which are created with an initial Hold status, will not generate an alert.
These alert types are available:
This information is available for the alert:
H: Placed on Svc Hold
R: Release from Svc Hold
CreditHold (ALC139) is used to notify the user when a sales order is placed on credit hold or released from a credit hold. Any SO document placed on credit hold or released from credit hold generates the alert.
You can access the Alert Control Center to view and optionally dismiss this alert. The alert is raised when the S4 background program, BK610, checks the crd_alert_action field in SORSOH. When a credit hold alert action or credit hold release alert action is issued, the alert is raised and users are directed to Sales Order Review (SOE230) based on the type of alert.
Note: New orders, which are created with an initial hold status, will not generate an alert.
These alert types are available:
This information is available for the alert:
H: Placed on Svc Hold
R: Release from Svc Hold
The OrderInAPI alert is raised as a notification that a sales order, meeting the subscription criteria, has arrived in FACTS via the API:OrderLoad. You can access the Alert Control Center to view and optionally dismiss this alert, or click Respond to Exception for the option to access Document Inquiry (SOI620) with the proper filters (Doc Type and Doc Number) appropriately filled in for the alert in question.
This information is available for the alert. You can subscribe to these values.
The QuoteInAPI alert is raised as a notification that a quote, meeting the subscription criteria, has arrived in FACTS via the API:QuoteLoad. You can access the Alert Control Center to view and optionally dismiss this alert, or click Respond to Exception for the option to access Document Inquiry (SOI620) with the proper filters (Doc Type and Customer/Doc Number) appropriately filled in for the alert in question.
This information is available for the alert. You can subscribe to these values.
The LTSRP-EXC alert is used to notify the user of an item's available quantity exceeding the long-term surplus quantity.
You can access the Alert Control Center (ALE100) to view and optionally dismiss this alert. When background process R3 (BKC603) runs and updates the Long- and Short-Term surplus points, each item’s available inventory is checked against the quantity of inventory tagged as “long term surplus”. If the available quantity exceeds the long-term surplus quantity, the alert is raised/generated. Users are directed to Item Inquiry (ICI610) with the appropriate item number and warehouse values.
This applies only if the Surplus Stock parameters, Long-Term Surplus, Seasonal and Long-Term Surplus, Non-Seasonal are set in Replenishment Parameter Maintenance (ICF990).
This information is available for the alert.
You can subscribe to the warehouse code and item number values.
The STSRP-EXC alert is used to notify the user of an item's available quantity exceeding the short-term surplus quantity.
You can access the Alert Control Center (ALE100) to view and optionally dismiss this alert. When background process R3 (BKC603) runs and updates the Long- and Short-Term surplus points, each item’s available inventory is checked against the quantity of inventory tagged as “short term surplus”. If the available quantity exceeds the short-term surplus quantity, the alert is raised/generated. Users are directed to Item Inquiry (ICI610) with the appropriate item number and warehouse values.
This applies only if the Surplus Stock parameters, Short-Term Surplus, Seasonal and Short-Term Surplus, Non-Seasonal are set in Replenishment Parameter Maintenance (ICF990).
This information is available for the alert.
You can subscribe to the warehouse code and item number values.
The APIERROR alert is used to notify the user when an API containing a customer number fails with a completion code of "E". It provides notification when a Storefront shopper places a shopping cart order that fails. You can access the Alert Control Center (ALE100) to view and optionally dismiss this alert.
This alert applies under these conditions.
This information is available for the alert.
You can subscribe to the API request, company and customer number values. The trigger value is the API Request ID + Response Log File Name. This ensures the trigger is unique.
The SOCITEM alert is used to notify the user that a SO companion item has an upcoming effective or expiration date where the number of days between today and the effective or expiration date equals the subscribed "Issue the alert" number of days.
You can access the Alert Control Center (ALE100) to view and optionally dismiss this alert. When background process A1 Data Miner (BKC100) runs, if the expiration and effective dates of the SO Companion item is greater than or equal to today’s date, the alert is raised. Users are directed to SO Companion Item Entry (SOE150) with the parent item and the proper companion item displayed for viewing or editing of that companion item’s effective/expiration date.
This information is available for the alert:
You can subscribe to the parent and companion item number values, parent item status and subscription type.
The POCITEM alert is used to notify the user that a PO companion item has an upcoming effective or expiration date where the number of days between today and the effective or expiration date equals the subscribed "Issue the alert" number of days.
You can access the Alert Control Center (ALE100) to view and optionally dismiss this alert. When background process A1 Data Miner (BKC100) runs, if the expiration and effective dates of the PO Companion item is greater than or equal to today’s date, the alert is raised. Users are directed to PO Companion Item Entry (POE150) with the parent item and the proper companion item displayed for viewing or editing of that companion item’s effective/expiration date.
This information is available for the alert:
You can subscribe to the parent and companion item number values, parent item status and subscription type.
The PGMLAUNCH alert is triggered by programs launched from the FACTS Launcher.
You can access the Alert Control Center (ALE100) to view and optionally dismiss this alert. When viewing launched alerts you can export the list to Excel and perform these analysis tasks:
Programs launched from within other programs via Go To or View menu options or direct code-based launching are not part of this alert.
You can subscribe to the program name, company and user code values.
The FLDCHANGE alert is triggered by a user change in program fields that have validation procedures.
You can access the Alert Control Center (ALE100) to view and optionally dismiss this alert.
These fields are available for subscription for the alert:
Changes to character-based or GUI program fields without validation or from within code, via direct code-based change to relevant variables, are not part of this alert.
The JOBSTREAM (ALC150) alert is triggered by Job Stream processing to notify the subscribed user that a job stream has run the background. Access the Alert Control Center (ALE100) to view and optionally dismiss this alert. The alert is raised when background process, Jobstreams (BKC611), runs. The alert remains in the subscriber’s control. The subscriber can manually delete the alert at any time from the Alert Control Center.
This information is available for the alert.
You can subscribe by these status values.
You can subscribe by these processing types.
You can subscribe to the all of these values.
The ALERT-3LE (ALC151) alert is triggered when a specified header or line process occurs in a three-level entry program controlled by SME999 and SME997 driver programs. Processes and record changes to that are outside three-level entry driver control do not raise an alert. Alert subscribers can manually close or clear the alert at any time from the Alert Control Center (POE410).
This information is available for the alert.
If this optional entry is made, it must be a valid 3LE program followed by ^ , followed by runtime condition. For example: SOE510^ORDER
The selected SMENTY values must have either a Header file entry, a Line file entry, or both to use the Data Filter field for this alert. Some three-level entry programs may have name changes during program runtime. To pick up program runtime changes, you can specify values with a description of “Not on file”. Refer to these scenarios for In-Line filter and SMGCTL filter methods of use for the Data Filter field.
This table shows the available Header and Line process options.
| DB Value | Text Value |
| L | Launched/started (entering program) |
| O | Opened/pulled (loading doc) |
| C | Created/updated (header saved/updated) |
| d | Deleted (deleted doc) |
| S | Saved/closed (end of doc) |
| F | finished/exited (leaving program) |
| A | Added line |
| R | Removed line |
| E | Edited line |
Line options are specified including the text, Line.
All options are recorded post occurrence, after the indicated event is completed.
This optional advanced filter requires a working knowledge of proper PxPlus syntax. It can be used only when a 3LE Selection value is specified.
These Process Type restrictions apply.
Refer to these scenarios for In-Line filter and SMGCTL filter methods of use.
This optional text value is displayed in the Notice column of the Alert Control Center (POE410). You can specify specific notes or text of the corresponding alert. There is a 30-character max.
Except the for Notice/Memo, you can subscribe to all of these values.
The ALERT-FM (ALC152) alert is triggered when a file maintenance process occurs via the SME999 driver program. Processes and record changes to files that are outside SME999 driver control do not raise an alert. Alert subscribers can manually close or clear the alert at any time from the Alert Control Center (POE410).
This information is available for the alert.
Optionally specify a valid file maintenance program. For example: SOF930.
This table shows the process type options available.
| DB Value | Text Value |
| l | Launched/started (entering program) |
| o | Opened/pulled (loading doc) |
| c | Created/updated (header saved/updated) |
| d | Deleted (deleted doc) |
| S | Saved/closed (end of doc) |
| f | finished/exited (leaving program) |
| a | Audit: added record |
| r | Audit: removed record |
| e | Audit: edited record/field |
The audit options, a, r, and e, are only applicable for file maintenance programs with the Audit settings turned on for the indicated file. Use the Audit>Change Audit Settings For This File FM menu option to activate file auditing. Audit-based alerts indicate that an audit record has been recorded for the indicated situation. If File Auditing is not turned on for the file impacted by the file maintenance, an alert is not raised for the audit Process Types.
All options are recorded post occurrence, after the indicated event is completed.
This optional advanced filter requires a working knowledge of proper PxPlus syntax. It can be used only when a FM Selection value is specified.
These Process Type restrictions apply:
Refer to these scenarios for using the In-Line filter and SMGCTL filter methods.
This optional text value is displayed in the Notice column of the Alert Control Center (POE410). You can specify specific notes or text of the corresponding alert. There is a 30-character max
Except the for Notice/Memo, you can subscribe to all of these values.
DebitHoldPO (ALC158) is used to notify the user when a purchase order is placed on debit hold or released from a debit hold. Any PO document placed on credit hold or released from credit hold generates the alert.
You can access the Alert Control Center to view and optionally dismiss this alert. The alert is raised when the S4 background program, BK610, checks the crd_alert_action field in PORPOH. When a credit hold alert action or credit hold release alert action is issued, the alert is raised and users are directed to Purchase Order Review (POE230) based on the type of alert.
Note: New orders, which are created with an initial hold status, will not generate an alert.
These alert types are available:
This information is available for the alert:
H: Placed on Svc Hold
R: Release from Svc Hold
ServiceHoldPO (ALC154) notifies the user when a PO document is placed on service hold or released from a service hold. Any PO document placed on service hold or released from service hold generates the alert.
You can access the Alert Control Center (POE410) to view and optionally dismiss this alert. The alert is raised when an S4 background program, BK610, checks the svc_alert_action field in PORPOH. When a service hold alert action or service hold release alert action is issued, the alert is raised and users are directed to Purchase Order Review (POE230), based on the type of alert.
Note: New purchase orders, which are created with an initial Hold status, will not generate an alert.
These alert types are available:
This information is available for the alert:
H: Placed on Svc Hold
R: Release from Svc Hold
ServiceHoldTR (ALC155) notifies the user when a transfer is placed on service hold or released from a service hold. Any transfer placed on service hold or released from service hold generates the alert.
You can access the Alert Control Center (POE410) to view and optionally dismiss this alert. The alert is raised when an S4 background program, BK610, checks the svc_alert_action field inICTRNH. When a service hold alert action or service hold release alert action is issued, the alert is raised and users are directed to Transfer Ticket Review (ICE235), based on the type of alert.
Note: New orders, which are created with an initial Hold status, will not generate an alert.
These alert types are available:
This information is available for the alert:
H: Placed on Svc Hold
R: Release from Svc Hold
ServiceHoldMCB (ALC156) notifies the user when an BOM production ticket is placed on service hold or released from a service hold. Any BOM production ticket placed on service hold or released from service hold generates the alert.
You can access the Alert Control Center (POE410) to view and optionally dismiss this alert. The alert is raised when an S4 background program, BK610, checks the svc_alert_action field in MCBPDH. When a service hold alert action or service hold release alert action is issued, the alert is raised and users are directed to MC BOM Ticket Review (MCE135), based on the type of alert.
Note: New tickets, which are created with an initial Hold status, will not generate an alert.
These alert types are available:
This information is available for the alert:
H: Placed on Svc Hold
R: Release from Svc Hold
ServiceHoldMCF (ALC157) notifies the user when a formulation production ticket is placed on service hold or released from a service hold. Any formulation ticket placed on service hold or released from service hold generates the alert.
You can access the Alert Control Center (POE410) to view and optionally dismiss this alert. The alert is raised when an S4 background program, BK610, checks the svc_alert_action field in MCFPDH. When a service hold alert action or service hold release alert action is issued, the alert is raised and users are directed to MC FML Ticket Review (MCE245), based on the type of alert.
Note: New tickets, which are created with an initial Hold status, will not generate an alert.
These alert types are available:
Hold Status = N – Documents not on hold if alert is a release alert,
Hold Status = H – All documents on hold if alert is a hold alert.
This information is available for the alert:
Formula
Warehouse
Action Creator (User)
Hold Type
H: Placed on Svc Hold
R: Release from Svc Hold
IMS Connection error, alert code BK-IMS CERR, is raised if the current IMS settings cannot connect to Infor OS. You can access the Alert Control Center to view and optionally dismiss this alert. You must resolve the connection setting issue in Infor OS Management. The logical ID is displayed in the alert. You can subscribe to this value.