SA Administrator Options - System - General field descriptions

Contact and Activity Manager

Create CAM Activities (Instead of CM Activities)

Use this operation with Corporate Assistant. If you create Customer Marketing activities for Corporate Assistant events, select this option for Corporate Assistant to create activities in Contact and Activity Manager instead of Customer Marketing.

Interface to Customers from CM Prospects

Select this option to link a prospect record to a customer record. Sales Prospect Setup updates the customer address information in Customer Setup when changes are made to the corresponding prospect record. Each prospect record may contain a company number and customer number linking it directly to a customer. If a link is established, any changes to the prospect’s address or other fields automatically update the customer’s record and vice versa.

For example, if a change is made to the Prospect Name on the Sales Prospect Setup record, and no Lookup Name is defined in the associated Customer Setup record, the Lookup Name is updated with the first 15 characters of the Prospect Name.

Lookups

Disable Auto Wildcard Usage for Keyword Lookup Keys Field and Search Fields

Select this option to disable wildcard usage for all free-form filters and the keyword search fields. For example, select this option if you do not want to use automated wildcards in any keyword lookup. Automated wildcards are also called masking lookups. These are wildcard characters that are substituted for actual characters in a lookup on product records. You can also use an asterisk at the end of a lookup word. If you disable automated wildcards, asterisks that you specify in any key lookup fields are not modified.

For example, if this option is selected, when you specify ta ex in a Product field with a lookup, records are returned that begin with ta and ex, such as tap extension or tap brass extension.

Note:  In the Keyword field in a product look up, the order does not matter. You can specify ex ta and tap extension would be a valid value.

If you clear this option, the search is for an exact match.

Disable Auto Wildcard Usage for Keyword Lookup Search Fields With a Lookup Button

Keyword lookup functionality for the primary master data lookups uses wildcards on all search criteria filters. This occurs even when the filter should be an exact match. This is because the value is known value or there are lookup capabilities. Due to the wildcard usage, a query can take several seconds, instead of milliseconds, depending on the size of the database. Use this option to disable the automatic wild card creation for these lookups to improve performance. The option is selected by default.

Maximum Record Count for Keyword Lookups

Specify the number of records to return as a result of a keyword search. The higher the number of records, the longer the search may take.

Commerce Catalog / Storefront

Interface To Commerce Catalog

Select this option if you are integrating Distribution SX.e to Infor Storefront and are using the Commerce Catalog. This option indicates that recordsync records should be created for the data load.

Interface ICSC Records
Select this option to send existing catalog records from Product Catalog Setup to the Storefront Commerce Catalog during the data load.
Note: This option is available only in your first operating company in Distribution SX.e. This setting is applied to the same Administrator Option setting for all other companies.
URL

Specify the URL to your Storefront instance.

Dropbox

Interface To Dropbox

Select this option to enable users to send reports that are processed through Report Scheduler to Dropbox, a secure file hosting service that users install on their personal computers.

System

Use Advanced Polling Interface Logic for Designated Service Interface Calls

Select this option to implement batch call processing in functions that process large transaction sets. Batch call processing allows Service Interface calls to complete and return data outside of the 1-minute system constraint time frame.

As the batch process runs, a poller is initiated that tracks the status of the batch call using a database table that is updated as the batch process progresses. This status can be requested, in process,completed successfully, or completed with errors. If there are errors, a message is displayed to the screen with the specific error. When the status is completed successfully or completed with errors, the poller stops for that specific call and processing continues as normal.

After you select the Use Advanced Polling Interface Logic for Designated Service Interface Calls option, you can choose the service calls to activate for the advanced polling batch process in the Available Advanced Polling Calls list. Services calls are available for Customer Cash Receipt Entry, PD Mass Maintenance Entry, Sales Order Inquiry, Sales Order Entry, Purchase Receipt of Inventory Entry, Transfer Receipt of Inventory Entry, Transfer Shipping Entry, Vendor Inquiry, and GL Journal Inquiry.

If the Use Advanced Polling Interface Logic for Designated Service Interface Calls option is selected, and no calls are selected in the Available Advanced Polling Calls list, batch processing is enabled for all calls in the list. If the option is selected, and you select any calls in the list, batch processing is enabled for the selected calls only.

If the option is not selected, batch call processing is not enabled for any service calls. If you uncheck the option after selecting service calls in the list, those calls remain selected. This is useful for disabling advanced polling/batch processing temporarily. The selected calls remain selected if you enable the option at a later date.

Other functions' transaction processing Service Interface calls are being reviewed by Infor to determine where this batch call process can be enabled. We recommend you review the Available Advanced Polling Calls list periodically or as part of troubleshooting transaction set timeout errors.

The Rdclean utility reviews any orphaned batch process records that remain in the database more than two days after the process is completed. Log records are written to the rptsch.mmddyyy.log file as batchcallprocess records, and can be used for debugging, if necessary.

You can configure a business rule, RequestPollingInterval, in SA Business Rule Setup to override the 5-second interval between polling the batch process. You can set a shorter interval to require the poller to check the batch process sooner than 5 seconds. This is useful if a service call normally can complete in a short amount of time, under the 5-second polling time. If the business rule is enabled for a time under 5 seconds, and you run a process where a large set of data is processed, the batch process is run more frequently, but you do not experience timeout issues.

Use Client Time Zone to Load Date/Time on System Records

Select the option in the table according to your business requirements. This table shows possible values of Use Static Time Zone in Place of Client Time Zone For Report and System Generated Date/Time Fields list.

No Static Time Zone Static Time Zone
Select this option to create system records during report processing using the local date and time of the user's client system, rather than the server date and time.

When selected, the time zone is obtained from the user's Windows' session Time Zone. This Time Zone is stored as an offset of Universal Time Coordinated (UTC) time, and factors in Daylight Savings Time. For example, a user working in Denver, CO has a Windows Time Zone offset for Mountain Standard Time, or -7:00 hours. If UTC time is 17:00, MST time is 10:00. (You can select a setting in the Windows Date/Time Settings to automatically adjust for daylight savings time.)

Using the Windows Time Zone, the user’s SA Operator Setup record is updated with their Client Time Zone Offset. This is updated each time they sign in to their client system. If Daylight Savings Time (DST) applies in the user's locality, the DST offset is recorded on the user's SA Operator Setup record so that the correct date and time is used. When the user runs a report that creates transactions in Distribution SX.e that store a date and time, the Client Time Zone Offset is included on the transaction record.

Transactions created before you select the new option are not changed to reflect the client date and time zone.

Note: This time zone offset relies upon your Windows system time zone. TWL RF functions running on hand-held devices do not use a Windows-based client and always record the date and time as the server time.
Select this option to set one specific time zone that must be used for all system date/times and report date/times. This option allows you to select a static time zone for your company. Distribution SX.e uses this static time zone to run reports and perform other system processes such as record creation, GL posting, and invoicing. After a report start date and time is set by the operator and the report is picked up to run, Distribution SX.e adjusts the time of the report to the static time zone.

For example, If an operator creates an order at 10:00 AM Eastern time zone and the static time zone is Eastern Standard Time (-5:00), then the sale order’s enter date is stored as 10:00 AM Eastern time zone. The Pacific time zone warehouse must change their picking reports to run at 7:00 AM to pick up the orders created at 10:00 AM Eastern based on the static Eastern time zone setting. Any call centers in other time zones such as Central or Mountain, create the orders based on the Eastern Standard Time setting. Following are other examples:

  • Order is created at 7:00 AM Pacific - order has an Entered Time of 10:00 AM (EST).
  • Order is created at 7:00 AM Central - Order has an Entered Time of 8:00 AM (EST).
  • Order is created at 10:00 PM Pacific - Order has an Entered Time of 1:00 AM (EST) and the Entered Date is the next day.

You must review and adjust any stored reports’ start times to ensure that reports are scheduled to run at the appropriate time for all regions.

For example, if the Pacific location warehouse has a Sales Entry Invoice Processing Report set up to run at 11:00 PM PST on 11/01/21, then the Invoice Date on the orders processed is recorded as 11/02/21 at 2:00 AM EST. The GL Post Date is also updated for GL account entries made during invoice processing. If the Pacific locations need the invoice date of 11/01/21, then the stored report for Sales Entry Invoice Processing Report must be changed to run at 8:00 PM PST for end of day processing.

To understand the effect of Daylight Savings Time (DST), see the information about application and server times in Infor CloudSuite Distribution Configuration Guide (Cloud).
Include TWL in Time Zone Processing

Select this option to apply these time zone selections to all processing in TWL:

  • Static time zone in use companywide, or
  • Local date and time of the user's client system, or
  • TWL warehouse time zone

This field is available only when you select the Use Client Time Zone to Load Date/Time on System Records option.

When this option is selected, the operator or static time zone is used to update date fields in TWL, unless you also select the Time Zone Selection for TWL Warehouse option. In that case, the appropriate time zone assigned to each warehouse is used. See information about using time zone in a TWL warehouse in online documentation.

Note: 
  • Ensure that the End of Day (EOD) processes are complete before you start to use client or static time zone settings in TWL. Remaining EOD processes are updated the next day, after the settings are changed.
  • Change all Drop Rules start times to reflect client or static time zones when you start to use client or static time zone settings in TWL.
Time Zone Selection for TWL Warehouse

Select the time zone that applies to each live TWL warehouse. It is recommended that you set up the time zone for each TWL warehouse. This time zone is used for all TWL processing such as interfaces, EOD processing, and auto drop.

The Time Zone Selection for TWL Warehouse grid to select the time zone for each warehouse is available when you select these options:

  1. Use Client Time Zone to Load Date/Time on System Records
  2. No Static Time Zone option in the Use Static Time Zone in Place of Client Time Zone For Report and System Generated Date/Time Fields
  3. Include TWL in Time Zone Processing

This is the order in which the TWL warehouse time zone is determined :

  1. Static time zone
  2. Time zone per warehouse
  3. Client time zone
  4. Server date and time: TWL uses server date and time to record TWL processing when these options are not selected:
    • Include TWL in Time Zone Processing option
    • Use Client Time Zone to Load Date/Time on System Records

See information about using time zone in a TWL warehouse.