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

Infor LN & Baan Tips & Tricks for FINANCE: Interest Invoices

Kathy Barthelt 0 27116 Article rating: 5.0

You can generate interest invoices for paid invoices, partially paid invoices, and unpaid invoices. In addition, after you generate and send an interest invoice, you can generate a subsequent interest invoice for the next period.

Setting up interest invoicing: You can set up interest invoicing in Accounts Receivable and the General Ledger.
To set up interest invoicing, use these sessions:

  • Invoice-to Business Partner (tccom4112s000)

For invoice-to business partners...

Infor LX/BPCS Tips & Tricks for FINANCE: Creating Configurable Macros (CEA)

George Moroses 0 18694 Article rating: 5.0

You can create new macros in the Infor LX Configurable Enterprise Financials CEA107. 

On the Macro Definition window, you define the source file and the field in which you perform an arithmetic or special operation. For example, you can create a macro to accrue sales commission based on revenue. Your source file and field are the Invoice Line History (SIL) file and the G/L revenue (ILREV) field. 

Select Functions to access the Macro Functions window, on which you define the arithmetic, character, or special operation to process against the defined source field. In the previous example of accrued sales commission, you enter an arithmetic operation of multiply (*) and an operand value for the percentage, such as 0.05 for five percent. 

Note:  Previously created user defined macros will have to be updated to include any expanded field sizes in V84. 

Infor LX/BPCS Tips & Tricks for TECHNOLOGY: Setting Up User Groups (CEA)

George Moroses 0 15138 Article rating: 5.0

To utilize the Security Rules Optimization feature, a system administrator can assign security codes to 100 pre-defined user groups. User groups are created in the Group Security Maintenance (SYS603) program. All users assigned to this group possess the same level of security.   

A system administrator can assign security codes for up to 100 of the user groups. All user groups over 100 are still administered by all security reject/allow rules assigned to them but are not able to utilize the optimized process. 

Each of the security codes and access levels are assigned to user groups and are mapped to the account strings and stored in the Account Cross Reference (CEA106D1) file.   

Once security codes have been assigned, the system administrator must: 

  • Determine which level each group is allowed access.

  • Determine which segment values/account strings are assigned to which user groups.

  • Create security rules for specific segment values/account strings and assign these groups to the created rules.

  • Select the rules to be processed.  Processing can be done in either batch mode or interactively.

  • The Security Rules flag must be on in the CEA Control Parameters program before any rules are effective. 

Infor LX/BPCS Tips & Tricks for OPERATIONS: Lot Expiration Date

George Moroses 0 13340 Article rating: 5.0

This feature provides a parameter that allows the user to enter expiration dates on the Inventory Transaction Posting screen, INV500, and Purchase Order Receipts screen, PUR5505, when they have received a lot controlled item that is not QMS controlled. This new field allows an expiration date to be entered and not overridden. A system parameter was added to Advanced Process Industries Parameters, API820D. When the parameter is set to Yes, a new lot expiration date is available in the Inventory Transaction Posting, INV500D2, and Purchase Order Receipts, PUR550D2, screens.

Infor News You Can Use: LN NAUG Face-to-Face Annual Meeting 2025

May 13-15, 2024 | Chicago Marriott - Naperville IL

Kathy Barthelt 0 9366 Article rating: 5.0

We are delighted to invite you to the 2025 Annual LN NAUG Face-to-Face Event —a special premier event for Infor LN and Baan users of North America. This is your chance to connect with fellow users, share experiences, and shape the future.

  • Learn from the Best: Engage with industry leaders and experts through keynote sessions and panel discussions.
  • Increase your Skills: Participate in collaborative breakout sessions to explore available solutions.
  • Network & Connect: Build relationships with other customers, potential collaborators, and industry pioneers.


Register today to claim Early Bird pricing through March 31, 2025.
https://www.lnnaug.org/events/2025-f2f-annual-meeting 

 

First7891012141516Last

Tips:  LX | BPCS | M3

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX TIP OF THE WEEK: 6 POWERFUL STEPS TO WIN WITH AUTOMATION:

  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.
Previous Article BPCS/LX Tip of the Week: Vendor Maintenance Security Option for Company or Program
Next Article BPCS/LX Tip of the Week: Why Would You Buy a BMW, But Use a Scooter?
Print
32748 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories