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

  • Sit down with your IT team. Decide how the information will be captured and where it will be stored so that employees have access to it. What software tools need to be used to capture the information? How does it need to be organized? Create a repeatable process to make this easy for your staff.
     
  • Interview the person. Have them talk you through his/her job. What are the things they do every day? What are their biggest challenges? How do they overcome them? 
     
  • Have someone shadow the person for a week. Watch what they do and how they do it. Ask questions. Who does he/she interact with in their department? Outside of their department? Why?
     
  • Find out what tools he/she uses to perform their job? Are there spreadsheets?  Reports within your ERP / outside of your ERP? Separate stand-alone databases? Drawings? Websites? Why does he/she use them?
     
  • Video record how the person does their job. Is their technique critical to “doing it right” the first time and not ending up with a bunch of scrap that you can’t reuse?
     
  • Figure out if the person does anything special on a monthly, quarterly, or annual basis that might not come up during the observation period or interview. 
     
  • Map how he/she uses your business system and how that impacts the rest of the company. Understand both the “what” and the “why”. Without this, new employees may end up figuring out what they need to do, but never understand why they need to do it.

Optimize Your Manufacturing Today!

  • Are you tracking downtime? Is it done manually, or with some type of automation or application that gathers information in real-time, or is it based upon history?
  • If you are measuring team effectiveness by shift, you know there are significant differences between them. Have you figured out why?

One of our automotive customers was experiencing significant inefficiencies and difficulties with their receiving operations. After analyzing their operation, we discovered a disconnect between how they were tracking their incoming goods and what their ERP system thought was on hand.

This disconnect created time-consuming steps to process incoming material and determine where the material was needed. The manual process slowed production, caused additional staffing needs and hindered their ability to effectively get needed material to the assembly line. They chose to implement our data collection solution to automate the process.

Since implementing the solution, receiving and moving material was quicker, more accurate and efficient. This enabled the addition of another assembly line, increasing production volume – without adding staff.

Optimize Your Manufacturing Today!

First111112113114116118119120Last

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