Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News, Crossroads Connection

Compression

Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

• The source financial company.
• The destination financial company.
• The transaction type and series.
• The ledger account and dimensions.
• The transaction currency.
• The fiscal year and the financial period, the tax period, and the reporting period.
• The integration document type and the Debit/Credit indicator.
• If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

Order quantity-dependent routings

An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:

Enhancement: Order Hold Audit Functionality

This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

• Hold type
• User
• Specific order
• Transactions for a customer within a date range
• Other combinations

Additionally, the selected data can be printed if desired.

Frequently Asked Questions (KB2316174)

For Infor LN a framework has been developed to support REST API-based services for lean integrations. This framework is now made available for the LN application. This KB answers some common questions you may have and procedures that are needed for using the LN Rest APIs.

More details on these topics can be found in the Infor LN REST API Administration Guide.