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

Seems obvious – you want real time data and you want it to be accurate. Do you have the systems in place to allow for this?

Here are 4 reasons you need a data collection system:

  1. See the differences between actuals and standards
  2. Determine the source of project overruns
  3. Prevent mis-shipments to customers
  4. Avoid unnecessary reordering of parts

An automated data collection system will analyze your current data, allowing you to efficiently optimize your manufacturing and the benefits will be huge and far reaching.

Optimize Your Manufacturing Today!

Do you have a strong relationship with your suppliers? Do they know your every need/want? No? Well, why not?  

The key to any good relationship is communication. Have you established clear and consistent communication with your suppliers? Consider establishing a way for both of you to share information with each other electronically.

A portal is a good way to achieve this. Documents can be shared, updates on deliveries can be communicated with ease, and changes that can affect both your operations and theirs can be communicated efficiently and effectively.

Optimize Your Manufacturing Today!

First105106107108110112113114Last

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