The Infor Distribution FACTS Version 9.3.2 incremental release provides the base framework for connecting to the Infor OS Cloud Enabled (CE). For further details, refer to the System Management section of this document and Infor Distribution FACTS Configuration Guide for Infor OS.
These versions are required for the integration:
When the user tries to access an SO document that is in use by another user, the user code was not displayed in all situations. An additional parameter was added to message code "SOFT_LOCK" to accept and display a user code. This change expanded the user code display for a record that is soft locked when another user attempts to lock the same record.
These scenarios are possible with file locking:
The content of the defect combined scenarios 2 and 3 where the Document in Use window displays the user name implemented at version 9.0.0, with the soft locking message, where that only displayed the key.
Custom column ordering and text-based list box column filtering are available for list boxes in Side Bars, three-level Entry programs, and Inquiry programs. When using list boxes you can right-click to display these options:
Use the My Column Order option to specify custom column ordering for the information displayed in the list box(stored in file: SMGPRF).
The default column options are displayed at the top of the screen. The default and current column orders are also displayed. In the New Column Order field, specify the codes to list the columns. Click Save.
You do not have to specify all codes. Partial entry is allowed. Any unspecified columns are appended to the grid in default column order.
For Inquiry and Side Bar list boxes, right click and select My Side Bar Filter or My Inquiry View Filter to display all the columns listed in default order in the list box, column code, and filter value, if set. Filtering values are not saved when you exit a program.
Check the Suspend Filtering check box to temporarily disable the filtering function.
Click Clear All to remove all filters values.
To specify a filter value, click a column line. On the edit screen, the current filter value is displayed. Specify a new value in the New Filter field and click Continue.
When you have specified the filter values click Continue to exit
Filter rules
In Side Bar areas, these filter rules apply:
In Inquiry views these filter rules apply:
Job Streams are now available as a background process. A new background process, job streams (BKC611), was created to spawn unique and individual background processes for each job stream that is able/scheduled to run. History is now available for job stream background processes.
Individual job streams that do not complete, either reporting an error in the background process or without completing the job stream result file, are not allowed to run in the background again until the error in the SMBKPR background processing record or the JSRSLT job stream result record are managed.
A new alert is available to notify a subscribed user of job stream progress as it runs in the background.
These programs were modified.
Job Stream Entry was enhanced to include Previous Record and Next Record buttons for record scrolling. A new Background Processing section was added and includes these fields:
Background - Indicate whether to run this job stream as a background process. Note the informational message indicating all lines should be set to 1) output to file and 2) perform no updates.
Months - Specify the 3-character abbreviation for each month to run the report.
Days - Specify the days this report will run. You can specify these options for the day of the month for the report. This table lists the options and when the report will run. When specified, the run report definition is displayed beside the Days field.
|
Option |
Run report definition |
|---|---|
| Number, 1-30 or 31 | Date of day of the month |
|
B |
First day of the month |
| B + M/T/W/H/F/S/U | First indicated day of the month |
| E | Last day of the month |
| E + M/T/W/H/F/S/U | Last indicated day of the month |
| M/T/W/H/F/S/U | Every indicated day in the month |
| 1/2/3/4/5 + M/T/W/H/F/S/U | Indicated day of the month in the week specified |
| A + number | Number of days after the last run of the report. |
The Background Scheduler Dashboard was updated to display the new job streams (BKC611) background process (JS).
The Background Process Results screen was updated to include all background job stream process results in order, job stream name, then within the name by date recent-to-oldest. A new Job Streams button in header displays all background process job stream results.
The new JobStreams window displays all background process job stream results in order, by job stream name, then within the name by date recent-to-oldest. You have these options:
Refresh - Redisplays with updated data in default/initial display order.
Delete - Deletes highlighted job stream result from the background processing file (SMBKPR) and refreshes the list box in default/initial display order.
A new JOBSTREAM (ALC150) alert was created to notify the subscribed user of job stream progress as it runs in the background. Access the Alert Control Center (ALE100) to view and optionally dismiss this alert. The alert is raised when the JS background process, job streams (BKC611), runs. The subscriber can manually delete their raised job stream alerts at any time from the Alert Control Center.
This information is available for the alert.
You can subscribe individually to any and all of these values.
Document Priority functionality was standardized throughout the Sales Orders, Purchase Orders, Inventory Control and Manufacturing Control modules.
These document priority indicators are available for transfers, purchase orders, BOM and formulation production tickets and purchase orders: Normal, Rush and Service Hold.
For purchase orders, PO Debit Hold processing is available. PO Debit Holds can be set by creating a debit limit for vendors in Vendor FM. An override password and security code are available for this function in PO Static Control FM. During PO document entry, accumulated currently open PO document totals for the specified vendor are checked against the vendor’s debit limit. When that vendor’s open PO document total exceeds a specified limit, the PO debit limit action is triggered for that vendor.
Previously, rush text was hard-coded in programs and print controls. New document priority functionality now allows custom rush text for each document type.
Priority drop box functionality was added to entry, print, inquiry, and report programs and documents and files throughout PO, IC and MC. Refer to the change table for program details. New document review programs have been added in the PO, IC, and MC modules. New alerts for Service Hold and PO debit hold actions and changes have been included for PO, IC, and MC modules.
Hold processing details
Service Hold and PO Debit Hold prevents both printing a ticket or an order and entry for confirmation. Changes to priority after confirmation have no restrictive effect on further processing of that ticket.
Buyers Control Center changes
This section lists the major changes for Buyers Control Center.
The corresponding Buyers Control Center detail screens were updated to include a Rush column for purchase orders, transfers and production tickets. The BCC now provides for a Rush bump value to be added to the indicated color-coded sort-priority. The Rush bump is set in PO Static Control F/M on the BCC tab. The bump value increases the defaulted sort color and value on the BCC detail screen. This allows for lower ranked and lower priority items to shift higher in the BCC Detail hierarchy of presented rows. In the BCC, when calculating non-special orders to be pulled in based on backorders from existing SO docs, the resulting single BCC detail line is the accumulated total needed across all relevant SO docs. The rush value is not set on that single accumulated detail line. The accumulated multiple docs may have a variety of priority settings.
Special Orders originating in SO then processed by the BCC, set the BCC Rush column to selected if the special order has a Rush priority and the special order is not already in the BCC.
Checking and un-checking the BCC Rush column check box does not change a tied special order SO document priority. When the BCC Rush column is checked and the PO, transfer, or production ticket id created from the BCC, the created document is set to Rush priority as the default.
To create a Rush priority purchase order or transfer from the BCC, all lines on the BCC detail screen that are set to Buy or Transfer must be set as Rush. A mixture of rush and non-rush lines results in the purchase order or transfer not having rush priority.
BOM or formulation production tickets created from the MC BOM and FML BCC Detail screens create unique documents corresponding to each BCC detail line. Rush and non-rush production tickets can be created at the same time since each line creates a unique document.
Special Order Entry programs and special-order creation changes
This section lists the major changes for document priority functionality in Special Order Entry programs and entry programs with special-order planning hot-key record creation.
When creating and adding lines to a purchase order or transfer from a menu-driven program or special-order planning record option, the priority value set in the header during initial document creation is used. A mixture for rush and non-rush lines may be pulled in on the resulting purchase order or transfer. During import of a special order, Priority information was added to look-ups and entry screens when SO document priority is Rush or Service Hold.
This section lists the major changes for reports and print processes.
Print programs were standardized to include options to print by document priority.
New fields on report program screens are not part of existing or saved user templates. Users must go to their saved templates and indicate the preferred values of any new fields to update their saved templates.
Sales Order Review (SOE230)
Existing Sales Order Review (SOE230) field layout has beenwas refactored so that all review programs have a similar layout. A Go To menu option allows quick navigation between all review programs.
New programs and alerts
This table lists the new document review programs for document priority standardization.
| Module | Program | Function |
| Purchase Orders | Purchase Order Review (POE230) | Display, place or release documents from debit or service hold. Documents may be displayed by warehouse, hold status, order type, order status, origin, priority, request date and buyer |
| Inventory Control | Transfer Ticket Review (ICE325) | Display, place or release documents from service hold. Documents may be displayed by warehouse, hold status, order type, order status, origin, priority, request date, and to warehouse |
| Manufacturing Control | BOM Ticket Review (MCE135) | Display, place or release BOM production tickets from service hold. Documents may be displayed by warehouse, hold status, order status, origin, priority, and entry date |
| Manufacturing Control | FML Ticket Review (MCE245) | Display, place or release FML production tickets from service hold. Documents may be displayed by warehouse, hold status, order status, origin, priority, and entry date |
Alerts
This section lists the new alerts for document priority standardization.
If you are subscribed to one of these alerts you can access the Alert Control Center (POE410) to view and optionally dismiss these alerts. The alerts are raised when S4 background program, BK610, checks the svc_alert_action field in the corresponding document header records, or the dbt_alert_action field for PO debit hold actions. When a debit hold or service hold alert action or release alert action is issued, the alert is raised and subscribed users are directed to corresponding Order Review program, based on the type of alert.
These alert types are available:
Hold Status = N – Document not on hold if alert is a release alert,
Hold Status = H – Document on hold if alert is a hold alert.
Note: New purchase orders, transfers or production tickets which are created with an initial Hold status, will not generate an alert.
This table lists the new alerts.
| Alert | Action | Available Information |
| 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. |
This information is available for the alert: Vendor Number Ship-From Number Action Creator (User) Hold Type 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. |
This information is available for the alert: From Warehouse To Warehouse Action Creator (User) Hold Type 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. |
This information is available for the alert: Finished Item Number Warehouse Action Creator (User) Hold Type 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. |
This information is available for the alert: Formula Warehouse Action Creator (User) Hold Type H: Placed on Svc Hold R: Release from Svc Hold |
| DebitHoldPO (ALC158) | Notifies the user when a purchase order is placed on debit hold or released from a debit hold. Any PO document placed on debit hold or released from debit hold generates the alert. |
This information is available for the alert: Vendor Number Ship-From Number Action Creator (User) Hold Type H: Placed on Dbt Hold R: Release from Dbt Hold |
Program changes
This table lists changes to existing programs.
| Module | Program | Change Summary |
| Accounts Payable | Vendor F/M (APF910) - Miscellaneous tab | PO Debit limit amount and Debit limit check action |
| Vendor AP Inquiry (API610) - General view | Debit limit and Debit Check | |
| Inventory Control | IC Static Control FM (ICF980) | Rush Header text |
| IC Print (ICP310) screens | Field additions and rearranged - Origin | |
| Planned Special Order Transfer Entry (ICE310) | Priority column | |
| Transfer Ticket entry (ICE320): Planned special order import function, Transfer Ticket Line F1 special order, F2 search on order | Priority column | |
| Manufacturing Control | MC Static Control FM (MCF980) | Rush Header text |
| MC Ticket Print (MCP110 and MCP210) | Screen additions - Origin, Priority | |
| MC Bill of Material Inquiry (MCI610), Production and Past Production views | Priority column | |
| MC Formulation Inquiry Production (MCI620), and Past Production views | Priority column | |
| Production Detail for the Selected Ticket (MCI624) | Priority column | |
| Production Detail for the Selected Ticket (MCI613) | Priority column | |
| MC BOM Ticket entry (MCE130) | Priority, Print now check box and window | |
| MC BOM Ticket Confirmation (MCE140) | Priority | |
| MC Production FML Ticket entry (MCE240) | Priority, Print now check box and window | |
| MC Production FML Confirmation (MCE250) | Priority | |
| Purchase Orders |
PO Static (POF980), General view Print Control view
BCC view
|
Rush Header text PO Debit limit password and security code Rush Order Bump
|
|
Vendor PO Inquiry (POI610), Codes view
Purchase Orders view |
hold column, Priority column, API column Debit limit and Debit Check |
|
| Purchase Order Detail Window | Priority column | |
| PO Print (POP110) | Cutoff Date, Origin, Doc Type, Priority screen additions | |
| F2 search on PO number | * in status column if PO is on Debit Hold | |
| PO Entry Options FM (POF915) | Priority | |
| PO Status report (POR710) | Priority | |
| PO Entry (POE120), Header Detail button F1 Special order entry, F2 lookup |
Priority, Special Order Import menu option, Hold/Rush label Priority column |
|
| PO Receipt Entry (POE210), Header Detail button | Priority | |
| Non-PO Receipt Entry (POE220), Header Detail button | Priority | |
| Buyers Control Center Detail screens (POE405 purchase orders and transfers, POE407 BOM tickets, POE408 formulation tickets) | Rush column and check box | |
| Sales Orders | SO Static Control FM (SOF980) | Rush Header text |
| Sales Order Review (SOE230) | screen rearranged, Go To menu expanded |
Cost discrepancy processing was expanded and updated in the Inventory Control and Sales Orders modules.
These programs were modified in the Inventory Control module.
These changes were implemented in Cost Discrepancy Entry.
Pre-register PO Receipts and Adjustments
For PO receipts that have been updated but not yet run through the PO Receipt Register, a message is displayed and cost discrepancy entry is not allowed.
Adjustment records are not displayed in Cost Discrepancy Entry browser if they have not been processed through the Adjustment Register.
Verifying Receipts
A new Verify Receipts button was added to check all cost discrepancy records currently on file for their matching receipt. If not found, the cost discrepancy record is removed. At least one cost discrepancy record is required to enable the button.
Cost factoring
When using cost factoring, the current and new unit costs are the same because the cost is factored across units. A new Factored Unit Cost column in the list box contains the factored cost that is applied during the register when no cost change is visible.
When a cost factoring value is specified, a new Update Cost button is available to calculate the unit factor value and display the value in the list box. If the entered cost factor value is not evenly distributable, you can choose to ignore the message or fix it. Specify Ignore to allow the uneven distribution to be saved and manually update individual lines to account for any unenven distribution. Specify Fix to allow entry of a new cost value. The Factored Unit Cost column is only populated when using cost factor.
A new Cost Overridden column was included. An asterisk, *, is displayed in the Cost Overridden column when the receipt cost was changed by the user.
When using the look-up button for on file cost discrepancy records, factored cost records are included in the look-up results. Cost discrepancy records, which are auto-created by an over-shipment being filled by a receipt, are not included in the look-up results.
These changes were implemented in the Cost Discrepancy Register.
IC receipt and disbursement files
GL account numbers are written to IC receipt and disbursement files during registers. Cost Discrepancy Entry is only allowed on receipts that are post-register processing. Running the Cost Discrepancy Entry Register for receipts which have ‘open’ disbursement documents that are not yet run through their own register does not show GL account information on the Cost Discrepancy Register output. Costs on ‘open’ disbursement documents can be updated by the cost discrepancy register, and, when the ‘open’ documents have their own register run, the associated docs, having already had their costs updated through the Cost Discrepancy Entry Register, update GL on their own register.
Outputs with no cost difference
Records can be written to the cost discrepancy file when an over-shipment is filled by an incoming receipt. Additionally, factored cost discrepancy entry may be involved. These are two types of output that show no cost difference on the first page of the Cost Discrepancy Register. Running the register clears such records.
When an overshipment (OS) receipt is resolved by an incoming receipt, the OS receipt record is removed and a Cost Discrepancy Entry record is written. Since the received cost did not exist at the time of the OS, now the cost is the same as the receipt that resolved that OS. Any change to the cost of that receipt (making the cost different than the disbursement document, such as the sales order) will have that disbursement document's cost updated with the receipt cost during the Cost Discrepancy Entry Register.
For example: A new item is entered, and before any receipts occur that new item is sold, an OS record is written. Then, once a receipt for that new item comes in, the OS record is removed and the sold quantity is accounted for from that incoming receipt. To handle potential cost changes, a Cost Discrepancy Entry record is written and “Created by Processing Overshipment” is displayed on the first page of the Cost Discrepancy Entry Register. The received cost has not changed. The sold item’s cost, if different from the receipt’s cost and not manually changed by the user at entry, would need to be updated with that incoming resolving receipt’s cost when the Cost Discrepancy Entry Register is run.
Update and report-only modes
The Cost Discrepancy Register runs in report-only mode by default. The Reports Only check box is checked by default. You must uncheck the Reports Only check box to run in update mode. If a locked distribution record is encountered during the report-only output, a message containing the document number and the cost discrepancy which will be skipped, is displayed. Make a note of any locked documents during report-only output allows for resolution before the Cost Discrepancy Register is run in update mode.
When output is report-only mode no files are updated in the system. The costs presented are the unchanged costs. When output is run updating costs, the values presented may be already updated values. The costs presented may be the changed cost instead of the pre-change cost. For example, if a receipt having disbursements associated has a cost change, then the disbursement summary page showing that receipt will show the original receipt cost in report-only mode, and show the changed, or updated, cost when run and updating costs.
When output is report-only mode, the register number displayed in the output header is 0000. If using Unform Document Archiving, all report-only mode output that is sent to Unform is stored under the 0000 register number.
Special Order temporary items
Special Order temporary items were included in cost discrepancy processing for the Cost Discrepancy Entry and Cost Discrepancy Register programs.
Cost Discrepancy Entry (ICE610) and Cost Discrepancy Register (ICR610)
If a temporary item is entered in Order Entry as a special order, then the temporary item is to be received on a tied special-order PO or transfer. During Order Confirmation, a tied disbursement record is created, against which any cost discrepancy entry can be successfully applied. Cost discrepancy entry and register for this type of special order temporary item updates cost for both the receipt and the disbursement of that special order temporary item.
Special Order Temporary item disbursement docs are now included and displayed.
This program was modified in the Sales Orders module.
All special order temporary items now create a disbursement.
This table lists descriptions for the defects that were included.
| Defect Number | Description |
| 700814 | Using Cost Factor in Cost Discrepancy Entry creates an endless loop |
| 660304 | Cost Discrepancy for Temporary Items not updated to past SO document |
| 660137 | Cost discrepancy update is not updating past invoice |
| 616216 | Cost Discrepancy Register not updating GL |
| 597979 | Cost Discrepancy Register has items with no cost discrepancy and prevents user from doing IC Month End |
| 510413 | CDR Currently only Post to current G/L Period |
| 501599 | Need ability for Cost Discrepancy Entry and Register, choose ALL warehouses |
| 500525 | Cost Discrepancy Report not removing orphaned records in ICCSDS |
| 496377 | Cost discrepancy register is ignoring the Cost Change Flag in SORSOL and SOPIND. |
| 474863 | Performing a Cost Discrepancy against a pre-register PO or Adjustment will not properly update cost |
| 468580 | Documentation for Cost Discrepancy records generated automatically by FACTS |
| 461047 | Cost Discrepancy Entry won't update thru Cost Discrepancy Register due to record locking failure |
| 430369 | Cost Discrepancy for Temp Items |
| 420734 | Cost is not updating with cost discrepancy when in POUPDL - if in POUPDH don't allow cost discrepancy |
The branch value was missing from the Transfer/Change Customer Codes program. A new field, Default Branch, was added.
When the Process Warehouse Item Records update program exported records from Warehouse Item FM (ICF920), an incorrect Date must be after today message was displayed. The spreadsheet generated from the update contained validations that Warehouse Item FM did not. The validations were removed from the spreadsheet and a new version was released in the FACTS 9.3.2 incremental.
The Side Bar feature was expanded to these IC transfer and confirmation programs: Transfer Entry, Shipment Confirmation, and Receipt Confirmation. Use the IC Side Bar to display additional quantity and item detail information for quick item selection and viewing. This provides information about items in the line-item section to facilitate efficient transfer.
Click Show/Hide to toggle the Side Bar display off and on. Select a view from the drop box. For views with drag and drop functionality, click and drag one or multiple lines at a time to the line-item section. Click Reload to refresh the contents displayed in the Side Bar area list box.
You can use the Side Bar for research and review after you specify an item. Limiting, scrolling and double click actions, when available, are also enabled during line entry. Drag and Drop during line entry is not allowed.
Refer to this table for the available Side Bar views:
| View | Description | Drag / Drop available | Functionality |
| F-From Warehouse Quantities | Displays the from warehouse quantities for that selected line. All from warehouse’s quantities for a selected item on the ticket are displayed. This is item-specific and contents change with items listed in Transfer Entry. | There is no further action in this view. | |
| T-To Warehouse Quantities | Displays the to warehouse quantities for that selected line. All to warehouse’s quantities for a selected item on the ticket are displayed. This is item-specific and contents change with items listed in Transfer Entry. | There is no further action in this view. | |
| A-Warehouse Quantities | Displays all warehouse quantities for that selected line. This is item-specific and contents change with items listed in Transfer Entry. | There is no further action in this view. | |
| R-Resources | Displays resources for the warehouse and item. Warehouse-specific as well as item-specific. The contents related to the warehouse will not change but content may change with item selection. | Select a line and double click to launch the Supplemental Resource Manager (SMC910). | |
| t-Timeline | Displays the selected item’s current timeline for that single item (and from warehouse). Temporary items are omitted. This is item-specific and contents change with items ordered. | Select a line and double click to launch the inquiry corresponding to the selected line type if the document is available. | |
| N-Notes | Displays notes based on warehouse and item. This is warehouse-specific and item-specific. The contents related to the warehouse will not change but content may change with item selection. | Select a note and double-click to launch the Note Entry (SME710) for the line and type (Document (header); Line or Item (line). | |
| I-Incoming | Displays where the item is coming into the “from” and “to” warehouses via Purchase Orders Transfers or Manufacturing entry programs. | Select a line and double click to launch the inquiry corresponding to the selected document type. | |
| O-Outgoing | Displays where the item is committed for the “from” and “to” warehouses via Sales Orders Transfers or Manufacturing entry programs. | Select a line and double click to launch the inquiry corresponding to the selected document type. | |
| L-Long Term Surplus | Displays items with long term surplus in the ticket’s From and To warehouses set in Warehouse/Item FM (ICF920). Alternate warehouses with long term surplus are included if the Use Surplus check box is selected in IC Static Control F/M and are valid for IC in Warehouse F/M (ICF970). | X | Double click a line to display the Change Long Term Surplus Quantity window to change the order quantity. Click Refresh to reset all quantities and values to their initial amounts. |
| s-Substitute Items | Displays substitute items for the selected item in the ticket’s From and To warehouses set in Warehouse/Item FM (ICF920). The item description, quantity and buying UM are also displayed. | X | Double click a substitute item to launch the Change Substitute Item Quantity window for the selected substitute item. |
The Side Bar feature was added to Manufacturing Control entry and confirmation programs. Use the MC Side Bars to display additional information for bill of materials items, production ticket entry and confirmation, formula entry, production and confirmation. The Side Bar information varies by program. It is tailored for quick item selection and viewing. This provides details about manufacturing habits for the specified BOM or formula item and information about items in the line item section of MC entry programs to facilitate efficient manufacturing choices. The MC Finished Item Entry (MCE231.F) Side Bar is also available from the FML BCC Detail (POE408) screen in the Buyers Control Center.
Click Show/Hide to toggle the Side Bar display off and on. Select a view from the drop box. For views with drag and drop functionality, click and drag one or multiple lines at a time to the line item section. Click Reload to refresh the contents displayed in the Side Bar area list box. Use the arrows in the lower right corner to scroll through the pages and go to the first and last pages. Scrolling moves through the items loaded into a particular drop box a page at a time.
During line entry, Side Bar research functionality is enabled after the Item field is entered. Limiting, scrolling and double click actions, when available, are also enabled. Drag and Drop during line entry is not allowed.
These MC Side Bars were added.
The Sales Orders Past Order Status Change Inquiry was expanded to include filtering options for code type, user code, document number and invoice number. The document number, invoice number filters have no mask and when entered, lines matching the exact typed value are displayed.
A new sequence number check box, Seq 0001, was added to the Background Process Log File Viewer. Check the Seq 0001 check box to indicate whether to display only records with a sequence number of 00001. This action displays only the first record of any possible record set, without showing all subsequent sequence number records for that first record.
You can double click a record in the list box to display all subsequent sequence number records and uncheck the check box by default.
The Entity Key field was also expanded as a text search for the entered value in the Entity key column. If the specified text exists anywhere in the entity key of a record, the record is displayed.
New functionality allows the raising of alerts to be set to inactive at the alert, company and system levels. When inactive, no Raise Alerts API XML is delivered to the API in directory.
A hookpoint was added to SMF009 allowing partners to specify to skip alerts if they set the skip_alerts flag to 1 (true).
3016 skip_alerts=0; perform "prog/SM/SMF00J;pre_record_alerts",err=*next ! hookpoint for other validation - if sets skip_alerts=1 then no alert raised.
These programs were modified.
A new Raise Alerts check box was added to each of these programs:
• Alert Metadata Entry (SMF009) - check if the alert is active
• Company Control F/M (SMF920) - check if the alert is active for the specified company
• System Control F/M (SMF950) - check if the alert is active for the system
System Alerts Dashboard (ALE100)
A new column, Active, was added to the System Alerts Dashboard to indicate if the specified alert is active or inactive.
System Alerts Dashboard (ALE100), Alerts Control Center / Exception Control Center (POE400)
The Alert Details button display the System Alerts Dashboard and the Alerts Control Center / Exception Control Center now display the Raise Alert status to indicate if any alert, company-level, or system-level check box is inactive.
These new alerts are included in version 9.3.2.
The SOCITEM alert was added 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/expiration date equals the subscribed "Issue the alert" number of days.
If you are subscribed to the alert, 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 was added 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/expiration date equals the subscribed "Issue the alert" number of days.
If you are subscribed to the alert, 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 was added to notify the user when a specific program is launched from the FACTS Program Launcher.
If you are subscribed to the alert, access the Alert Control Center (ALE100) to view and optionally dismiss this alert. This alert provides detailed information about user program access. 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 (ALC149) alert to audit value changes in validated fields. The 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.
You can subscribe to the SMPRMT field details, company, user code values and or evaluated 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.
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.
| 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.
These Process Type restrictions apply.
Refer to these scenarios for In-Line filter and SMGCTL filter methods of use.
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.
| 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.
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.
These key changes were implemented for the Infor OS integration.
These programs were created or modified to provide the base framework for connecting to the Infor OS Cloud Enabled (CE).
A new program, Infor OS Management FM, was created to manage all Infor OS-related settings and values. The SMOSFM file is used to store these values. The General tab contains global settings, such as the Tenant ID, Oagis release, and the connection type, Inbox/Outbox or REST/API. When modifying the connection method from Inbox/Outbox, a warning is displayed if there are any unprocessed records remaining in any database set up for use with Infor OS. Documents may be orphaned. The Inbox/Outbox and IMS tabs contain the necessary values for each integration connection type.
Note: To modify this program, you must check the Disable Background check box on the Settings tab of System Control FM (SMF950).
The ION tab was removed and the fields were relocated to Infor OS Management FM.
A new field, Type, was added to specify the database type: Microsoft SQL Server or PostgreSQL.
A new Database Type drop box was added for selecting SQL Server or PostgreSQL.
Stored procedure records, specific to PostgreSQL functionality, were added:
1) pgs_facts_clean_inbox, 2) pgs_facts_create_outbox, 3) pgs_facts_get_inbox
On the Modules Used tab, the ION check box was renamed to Infor OS.
These alerts were updated and created for the Infor OS integration.
The Delivery of XML to Infor OS failure, alert code: BK-I2 OUT, which is raised if an outbound BOD XML document was ready for delivery but something prevented it from being delivered, was expanded to communicate with Infor OS.
The Connection error to Infor OS, alert code: BK-I2 CERR, which is raised if the I2 background process attempted to connect but something prevented it from gaining a successful connection, was expanded to communicate with Infor OS.
New alert, 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.