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

For years, repetitive manufacturing industries have been applying many of the principles in Just-in-Time philosophy. They have established balanced production lines that depend on a steady flow of material to each work station. They schedule production in daily or weekly rates rather than in discrete shop order lots. They track finished inventory by work center rather than by job. They typically backflush stock balances (decrement stock balances upon completion of specific manufacturing steps rather than issued at the beginning of each production run).

 

Costing is typically based upon a daily rate or hourly rate rather than being associated with specific shop orders. 

 

Repetitive manufacturers use MRP II software adaptable to their environments

in the following key areas:


â–ª Product definition

â–ª Inventory tracking

â–ª MRP/Master Scheduling

â–ª Shop Floor Control

â–ª Purchasing

â–ª Costing

Just-in-Time (JIT) is a management philosophy that focuses on minimizing the resources necessary to add value to your products and to operate your factory in ways that eliminate waste. Resources are labor, materials, equipment, space, and time. Waste is anything that does not add value to your products. Moving work-in-process from place to place, stacking and sorting, investing capital in large work-in-process and raw material inventories, inspecting materials at your vendors' sites, and tying up warehouse space with finished goods are all activities that add cost, not value, to your products. 

JIT is a process that reduces lead time. JIT does not replace an MRP, an inventory program, a scheduling technique to bypass your Master Schedule, or a materials management project. JIT is the never-ending commitment of everyone, from top management to your workers on the floor, to maximize your effectiveness through continuous, incremental improvements.

First134135136137139141142143Last

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