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

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 LX & BPCS Finance Tip: 3-Way Match - A validation step when paying vendor invoices in ACP500
Next Article Infor LX & BPCS Materials Tip: Over-Receipts
Print
27735 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Exit Points is a new feature in Infor LX Version 8 that allows users to customize, without changing the original LX source code. Exit points provide a way for you to call an external program and pass a set of parameters to implement any needed custom logic. By using Exit Points, LX customers are able to modify the software, and still take advantage of new releases from Infor. Exit points are available in many LX programs. A complete list is available on the Infor support website.

Optimize Your Manufacturing Today!

Poor performance indicators make for poor outcomes.

Companies today continue to tolerate and accept how labor and production information is recorded, and the reliability on that information is questionable. In addition to collecting labor and production information, there are many other pieces of information manually recorded from the shop floor.

A critical element of information for productivity throughput would be to examine how much time the work center or machine was actually up and running. Downtime is another critical element of data that is usually manually recorded along with a reason identifying what caused production to stop. If this information is not provided on a timely and accurate basis, then what good is it anyway? Forms are filled out, data may or may not be keyed to a spreadsheet, the forms are sorted and filed, but is anybody really looking at the information that was recorded? Think about the amount of time it takes to manage the manual collection of information from your shop floor. 

What would real time access to data mean to your organization?
The benefits:

  1. Real Time Production Visibility
  2. Reduced Paperwork Load
  3. Downtime and Scrap Visibility
  4. WIP Inventory Visibility
  5. Improve Efficiency, Capacity Utilization

Optimize Your Manufacturing Today!

First101102103104106108109110Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

12345678910Last

Theme picker

Categories