Please Wait a Moment
X

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

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

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

Subscribe to newsletter

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
70404 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

These programs are used to capture and post shop floor information. Labor reporting, machine time, etc. can be captured by either program. The key difference is that one will also capture the production receipt and backflush components. Based on your company information / transaction process, one of these programs will most likely be used daily to capture current shop floor data. You can use the shop packet labor ticket for the manual recording, and the keying of the data. Alternatively, you can incorporate an automated method like an MES solution to capture the data and streamline the process.

Read more

The bubble number is maintained at the component level for each component defined on the Bill of Material. It is an extra user-defined reference number that you can use to re-sequence the maintenance screen display or bills of material listings.

In Infor LX, the system displays the bubble number for the existing child items. Engineering drawings often use a bubble number at the component level on the drawing so that same bubble number can be used on the Bill of Material for a link of the component to the drawing. Alternatively, you may use it simply as a method to sequence the BOM.

Be careful of how you assign the number. It is a good idea to assign the number with a consecutive count by 10 leaving room to allow for component additions to the Bill of Material.

Read more
FirstLast

Tips: LN | Baan

Categories