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
28658 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

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

1. Eliminate paper shop packet and distribution of the paperwork to the shop floor.     

2. Eliminate manual (paper-based) recording activities and the need to key in the transactions.

3. Easy electronic scheduling by sequence and changing job priorities.

4. Evaluate differences using actual times compared to standards.

5. Improve data accuracy and eliminate the need to chase and fix errors.

6. Practice Real-Time data reporting to monitor efficiencies and identify problems as they occur.

In Baan IV, if a link with Financials exists for commissions and rebates, invoices are created directly in the Commission Control System (CMS) module and posted to Financials. As a result, users must specify the ledger accounts that are used for posting commissions and rebates in the Maintain Commission/Rebate Transaction Accounts (tdcms2101m000) session.

In LN, the Maintain Commission/Rebate Transaction Accounts (tdcms2101m000) session is removed from the Commission Control System (CMS) module, because invoices are no longer created directly in the Commission Control System module.

First119120121122124126127128Last

Theme picker

Categories