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

Don't laugh - the average lifespan of an ERP system is 7-10 years

Crossroads RMC 0 33741 Article rating: 5.0

Don’t laugh! I know, I know…many of our customers say that after 7-10 years they are finally settling in after the implementation! We have seen many a customer stretch out the lifespan of their ERP system to 20+ years. That sounds great for the company’s bank account, but is it good for the business?

An outdated ERP system hurts your business in many ways, not just with slow performance. The best-of-breed functionality is now 2 decades old, and obsolete technology can't leverage newer technology. Lack of integration leads to siloed data that hurts communication and your internal teams feel the pain, and your customers are noticing. Poor visibility into your operations makes it nearly impossible to achieve industry-based regulatory compliance and meet financial auditing requirements. Not to mention the sheer size of Big Data that is being collected today vs. 2 decades ago or the fact that your vendor is no longer supporting your ERP version.

Let’s scrap it all and start over!...

Infor LN & Baan Tip: Purchase Order Text

Kathy Barthelt 0 64171 Article rating: 5.0

Is the text linked to the purchase order just an information field? Could it be used for another purpose?

The text editor is just an information field when linked to the purchase order line and there is no other logic behind this functionality. The line text or the header text could be a part of the printed document. When you add text to a purchase order line you are creating a unique code that links the purchase order line (Baan - tdpur041/ LN - tdpur401) to the text (tttxt010).

Infor LX & BPCS Tip: Vendor Terms Maintenance, ACP160D1

George Moroses 0 34235 Article rating: 5.0

This program allows maintenance of vendor terms, which you individually assign to each vendor. Vendor terms designate the due date and the discount date as a number of days after the invoice date. You establish the discount percentage here. Vendor terms are stored in the AVT file. Rather than use the method specified above, you can override due dates and discount dates so those calendar days are used to age invoices.

Access: Menu ACP02

Infor LN & Baan: BIG DATA - Keeping Track of Key Metrics

Kathy Barthelt 0 66346 Article rating: 5.0

In order to communicate effectively as a team, everyone needs to speak the same language and operate off the same playbook. If decisions are made based on the data or the view of data that individuals are maintaining through their own spreadsheets or other data silos, then communication is negatively impacted.

Manufacturers need to review large amounts of data every day, making it difficult to keep track of key metrics within your department.

That’s where Crossroads RMC’s Analytics Dashboard solution comes in. Our Analytics Dashboard was developed to make tasks easier by putting all of the key information in one convenient location so you can view all of your crucial data in real-time. 

With powerful dashboards, you can...

Infor LX & BPCS: Waste in Manufacturing

George Moroses 0 29427 Article rating: 5.0

In manufacturing, waste is anything that doesn’t add value to or benefit the end customer. Reducing waste enables manufacturers to save money and increase productivity. Where is the waste happening in your processes?

How often is your department spending time and resources on the following tasks?...

Infor LX & BPCS Tip: Overhead Costs - CST120D1

George Moroses 0 27602 Article rating: 4.0

Use this program to enter period overhead expenses to distribute to various work centers. You can set up this overhead cost allocation on either a per-hour or a per-piece basis, depending on the overhead allocation type specified for each work center on the Work Center Maintenance screen, CAP100D2-01. The system spreads the amounts entered across all shop orders posted by Shop Floor Posting, SFC600, or Production Reporting, JIT600, when you run Overhead Cost Allocation, CST510. The system stores allocated overhead in the Labor Ticket file, FLT, and updates actual item cost when you run Shop Order Close and Post, CST900.

Access: Menu CST

Infor LX & BPCS: BIG DATA - Keeping Track of Key Metrics

George Moroses 0 33075 Article rating: 5.0

In order to communicate effectively as a team, everyone needs to speak the same language and operate off the same playbook. If decisions are made based on the data or the view of data that individuals are maintaining through their own spreadsheets or other data silos, then communication is negatively impacted.

Manufacturers need to review large amounts of data every day, making it difficult to keep track of key metrics within your department.

That’s where Crossroads RMC’s Analytics Dashboard solution comes in. Our Analytics Dashboard was developed to make tasks easier by putting all of the key information in one convenient location so you can view all of your crucial data in real-time. 

With powerful dashboards, you can...

First3334353638404142Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip of the Week: Limitations of Customer Defined Fields (CDFs)

Customer Defined fields are fields that can be added to tables, screens, reports, and BODs. Validation and calculation logic can be defined around those fields. This gives you great added capability and flexibility… however, are you aware of the limitations of using CDFs?

  • You cannot define customer-defined fields for tables within Tools (the tl and tt packages).
  • External integrations, such as Infor Integration, EDI, Office Integration, and SOA-based integration, do not support customer-defined fields.
  • You can use customer-defined fields within 4GL reports if editing the 4GL report layouts is still supported in your environment or by using the report personalization features of Infor LN Report Designer. For external reporting, only Infor Reporting and Microsoft Reporting (SSRS) support customer-defined fields.
  • Customer-defined fields cannot store application data in multiple data languages.
  • There is no direct limitation on the number of CDFs in a table. The actual number of fields in a table and the total length of all fields may be limited by the RDBMS you use.
  • Only superusers can run the Convert to Runtime Data Dictionary (ttadv5215m000) session to convert the customer-defined fields and the related domains to the runtime data dictionary.

Note: The full functionality of customer-defined fields is only available within Web UI and LN UI. Customer-defined fields are not displayed in the classic Infor LN BW UI.

If you have questions or need assistance with the use of CDFs, or Infor LN or Baan modifications in general, please contact us for assistance. We’d be happy to help. 800.762.2077 or kbarthelt@crossroadsrmc.com

Previous Article Infor LN & Baan Finance Tip: How to clear balances on invoices that will be moved to a new company
Next Article Infor LN & Baan Manufacturing Tip: Performance Problems in Generate Order Planning (cprrp1210m000)
Print
71420 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories