September 2021 Production Update

Product improvements

This section provides information about the enhancements in this release:

• Infor Expense Management can now be integrated with Infor Governance, Risk and Compliance (GRC) Authorizations Insight (AI) to monitor the automated business processes continuously. The GRC application automatically identifies exceptions and controls system failure in the key application. Organizations can reduce potential business risk and increase operational efficiency by locating and correcting issues immediately. GRC can automate audit processes and reduce the cost of compliance. When the applications are integrated, security BODs are sent from Infor Expense Management and Infor Federation Services (IFS) component of Infor Ming.le™ to the Data Lake through ION. Data from these BODs is extracted and analyzed by GRC. Security assignment violations generated in the GRC application are sent to IFS through ION.
• Infor Expense Management customers can now benefit from Infor Smart Help. Smart Help is an Infor Ming.le context application which can provide end users with in-context access to product knowledge including Infor product documentation, Knowledge Base articles, Training materials, and your own organization’s documentation.
• The Financial Code Block Validation business rule now supports Travel Plans. The business rule validates Cost Center or Project Codes with the Cloud Suite Financial (CSF) backend data.
  Note: For details, see KB 2175132
• The Expense Management application provides the ability to highlight the View/Add Itemization option when you require to itemize an expense type. You must configure the expense type and the business rule to mandate the itemization before submitting the expense.
  Note: For details, see KB 2095958
• A new Check Invoice Date business rule is introduced to validate the Payment Request (PR) invoice date. The business rule confirms that the PR invoice creation date does not exceed the number of days specified in the System Administration Tool (SAT) application.
  Note: For details, see KB 1853658
• The Parallel Charge Code Routing Rule business rule is enhanced to include the ‘Zero Amount Expense Lines Included' and the 'Personal Expense Lines included' check boxes on the BR Parameters tab. When the check boxes are selected, the business rule enables the Charge Code Manager to approve the expense reports that have zero $ or 'Do Not Reimburse (Personal)' expense line items.
  Note: For details, see KB 2195525
• The Expense Management application provides the ability to hide or display the flat cost center segments in the application or in the expense document that is printed.
  Note: For details, see KB 2193533
• The Sync.CodeDefinition BOD (Expense Management to FSM) now includes the modified name of the Expense type instead of creating a duplicate entry with the modified name.
  Note: For details, see KB 2192092
• The Expense Management application is enhanced to support Additional Data Capture (ADC) fields on allocations. For example, the ADC fields can be used for moving unit information to the International Federation of Accounts (IFAC) program for S3 account validation.
  Note: For details, see KB 2191250
• The Cumulative Mileage functionality can now be configured to track cumulative miles based on the expense type.
  Note: For details, see KB 2190855
• The ‘Consider check between non-itemization and itemization line item’ check box is added to the Duplicate Expense Check business rule. You can select the check box to consider the duplicate expenses between the non-itemized and itemized line items.
  Note: For details, see KB 2189146
• The Expense Management application is enhanced to include the ‘Receipt Receiver’ information in the document history table or on the Document History page.
  Note: For details, see KB 2185878
• The Expense Management application now provides the ability to import public or statutory holidays using the staging tables.
  Note: For details, see KB 2171309
• The Java and the HTML SAT screens now display the tenant name on the screen title.
  Note: For details, see KB 2137857
• The Expense Management application now provides the ability to consider specific expense types in an Expense Report when a complete expense document or expense line items are copied to create a new expense report.
  Note: For details, see KB 2192073
• The Expense Management application provides an option to restrict users from using only administrator defined mileage route related to Mileage expenses. As a result, mileage is consistent between two defined locations.
  Note: For details, see KB 2200134
• The Expense Management application is enhanced to list the expenses that are rejected (zero approved amount) in a printed expense report. The rejected expenses can be resubmitted in a new expense report.
  Note: For details, see KB 2198986
• The default value in the Billable field of the expense line allocations is now set to False. The Charge Code Reviewers now do not require to reset the default value.
  Note: For details, see KB 2198754
• The Expense Management application provides the ability to specify a default cost center value for Payment Requests, using the Field Default Definition functionality.
  Note: For details, see KB 2197121
• The Force Approver to look Receipts business rule is introduced that compels approvers to open each receipt attached to a document before approving the document.
  Note: For details, see KB 2180390
• You can now enable the print.hideCloseButtonOnProcessingError application parameter to hide the Close option on the Approval screen. This enhancement is applicable when a transaction error is encountered while approving a document.
  Note: For details, see KB 2179711
• A tooltip is now added to the Bulk Change functionality.
  Note: For details, see KB 2172517
• The Search functionality is enhanced to search documents based on Document Owner ID, Vendor Name, and Invoice Number.
  Note: For details, see KB 2133345
• The Positive Only Expense business rule is enhanced to consider few expenses instead of one specific expense or all expenses in an Expense Report. The business rule confirms that expenses contain only positive amounts.
  Note: For details, see KB 1647421
• Auditors can now copy or paste an expense report number without opening the expense report document.
  Note: For details, see KB 1639649
• The ‘All proxy Creators’ address type is added to the Email Notification screen of the Corporate Data menu in the SAT application. When the address type is selected, system generated emails are sent to all proxy creators of a document.
  Note: For details, see KB 1537238
• You can now define the process of calculating the expense report summary values.
  Note: For details, see KB 2195667
• The Expense Management application can now be configured to send a single consolidated email notification to each manager at the end of the day for reviewing documents. The email notification is sent only if the manager is required to review documents. The enhancement reduces the number of emails sent to approvers for approving expense reports.
  Note: For details, see KB 2180388
• The auditscore.showAuditScoreElementonScreen application parameter can be configured to control the visibility of the Audit Score and User Score on the Manager Review and the Auditor Review screen respectively.

  Users can be removed or added to the audit list based on the threshold value specified for the User Score. Users are added to the audit list when the User Score is less than the specified threshold value. However, when the user score exceeds the specified threshold value, the users are automatically indicated as inactive in the audit list.

  Note: For details, see KB 2205378
• The Expense Management application now supports the new Google Maps API key. You must set the value of the googleMaps.url application parameter to //maps.googleapis.com/maps/api/js?callback=initMap&key=AIzaSyDKxxMEuVmBPkCnjF_HZC0WZS_3TFtgccE to use the Google maps functionality with the new API.
  Note: For details, see KB 2217202
• This table is added to the Reporting Database schema:

  CREATE TABLE ALLOCATION_ADC (
  ALLOCATION_ID	int	NOT NULL
  DOCUMENT_ID	int	NOT NULL
  ADC_STRING_1	nvarchar(510)
  ADC_STRING_2	nvarchar(510)
  ADC_STRING_3	nvarchar(510)
  ADC_STRING_4	nvarchar(510)
  ADC_STRING_5	nvarchar(510)
  ADC_STRING_6	nvarchar(510)
  ADC_STRING_7	nvarchar(510)
  ADC_STRING_8	nvarchar(510)
  ADC_STRING_9	nvarchar(510)
  ADC_STRING_10	nvarchar(510)
  ADC_DATE_1	datetime
  ADC_DATE_2	datetime
  ADC_DATE_3	datetime
  ADC_DATE_4	datetime
  ADC_DATE_5	datetime
  ADC_INTEGER_1	int
  ADC_INTEGER_2	int
  ADC_INTEGER_3	int
  ADC_AMOUNT_1	numeric(28,10)
  ADC_AMOUNT_1_CURRENCY	nchar(3)
  ADC_AMOUNT_2	numeric(28,10)
  ADC_AMOUNT_2_CURRENCY	nchar(3)
  ADC_AMOUNT_3	numeric(28,10)
  ADC_AMOUNT_3_CURRENCY	nchar(3)
  CHANGE_TIMESTAMP	datetime
  CONSTRAINT PK_ALLOC_ADC PRIMARY KEY CLUSTERED ( ALLOCATION_ID )
  )

• These tables are modified in the Reporting Database schema:

  CREATE TABLE CUMULATIVE_MILES (
  CUMULATIVE_MILEAGE_ID	int	NOT NULL
  USER_ID	int
  PERIOD_START_DATE	datetime
  PERIOD_END_DATE	datetime
  CUMULATIVE_MILES	numeric(15,5)
  CHANGE_TIMESTAMP	datetime
  EXPENSE_TYPE_ID	int
  CONSTRAINT PK115_1 PRIMARY KEY CLUSTERED ( CUMULATIVE_MILEAGE_ID )
  )

  CREATE TABLE ORGANIZATION (
  COST_CENTER_ID	int	NOT NULL
  COMPANY_ID	int
  COMPANY_NAME	nvarchar(255)
  COMPANY_CODE	nchar( 60 )
  DIVISION_ID	int
  DIVISION_NAME	nvarchar(255)
  DIVISION_CODE	nchar( 60 )
  DEPARTMENT_ID	int
  DEPARTMENT_NAME	nvarchar(255)
  DEPARTMENT_CODE	nchar( 60 )
  USER_ID	int
  COST_CENTER_NAME	nvarchar(255)
  COST_CENTER_CODE	nchar(60)
  COST_CENTER_DESCRIPTION	nvarchar(255)
  DEFAULT_REVIEWER_ID	int
  ALTERNATE_REVIEWER_ID	int
  CHANGE_TIMESTAMP	datetime
  COST_CENTER_ACTIVE_STATUS	smallint
  CONSTRAINT PK10 PRIMARY KEY CLUSTERED ( COST_CENTER_ID )
  )