Please Wait a Moment
X

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

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Anthony Etzel
/ Categories: ERP News, Event / News, IDF

Steps to undo an IDF modification and restore to the default

Changes are great, but if you want to undo an IDF modification and restore to the default, you need to follow these steps:

Reset to an Infor shipped view (“un-modify” it)

  1. Open the public node of an object you would like to reset to the shipped status. Notice that all of the standard views (i.e., those owned by Infor) are unmodified.
  2. Select the row with the Modified column = yes
  3. Select the Reset to default button on the toolbar
  4. Say Yes to the prompt
  5. The object is now back to the way it was shipped by Infor. Note that it now shows that it has not been modified. If you display the editor, you will see that the attribute you deleted has been restored. Note that only objects owned by Infor can be reset. If you change a standard definition, and later regret it, you can use this feature to restore it with a couple of clicks.
Previous Article How to Improve Customer Shipments With OTTO - A Case Study
Next Article Tax Law Changes by the Numbers - Infor LX & BPCS Integration to Avalara
Print
30811 Rate this article:
5.0
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

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.

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.

First34568101112Last

Theme picker

Tips: LN | Baan

Instead of sharing tables through logical linking, you can replicate table content between companies. This approach allows certain non-key attributes of a record to vary by company. For example, if you replicate bills of materials rather than sharing them, each company can associate a different warehouse with the same bill of material. This way, the bills of materials are consistent across companies, while the warehouses can differ.

Replication also enables selective availability of records in other companies. For instance, when replicating items, you might limit which items are available in a sales company based on their item group, only including end items. You can further refine replication to specific subsets, such as particular item groups.

Keep in mind that replication requires any referenced tables to be either replicated or shared as well.

123456810Last

Theme picker

Categories