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

10 Ways to Not Screw Up the OEE Project – It is More Important than You Think

Rich Grilli 0 42732 Article rating: 5.0


Is there a mandate in your company to increase OEE and it has landed on your plate? Ah yes, the OEE approach. You remember what that is right? The Overall Equipment Effectiveness  metric as developed in Japan during restoration made famous in crafting some serious efficiency. Well, someone in management has decided that this is the way to make his world better and now it’s up to you to make it happen.

But there are pitfalls along the way:

BPCS/LX Tip of the Week: Is Lot Control Necessary?

Anthony Etzel 0 81230 Article rating: No rating

Certain industries require lot control, where others may find it an option based on how they want to trace the material used in a product in the event of a defect, or recall.

LX provides tight lot controls and flexibility with lot number assignments. Shop orders can have a pre-assigned lot number, or a lot number can be automatically assigned when the item is produced. You can also assign a specific lot number for the entire shop order, or for each item/quantity reported against a shop order.

Baan/LN Tip of the Week: Default Order Frequency

Kathy Barthelt 0 89043 Article rating: No rating

In Baan IV, requirements for an MPS item with the order method lot-for-lot result in daily planned MPS orders. For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, an MPS planning run generates one planned MPS order of 200 pieces for each working day in the plan period.

In ERP LN, requirements for a planned item with the order method lot-for-lot result in one planned order per plan period. For example, if a plan period contains 10 working days and the net requirements for an item in that period is 2000 pieces, a master planning run will generate a single planned order of 2000 pieces for the first working day in that plan period. To influence the order quantity of the planned orders, enter appropriate values in the Maximum Order Quantity field and the Order Interval field in the Items – Ordering (tcibd2500m000) session or choose a fixed order quantity.

Crossroads RMC to Exhibit at COMMON Conference, April 26-29

Crossroads RMC 0 35764 Article rating: No rating

The Annual Meeting is COMMON’s largest educational event of the year, with four full days of in-depth IBM i, AIX, and Linux-related education that includes all-day pre-conference workshops, open labs and a wide variety of regular-length sessions. It is the annual meeting of the COMMON membership and the largest gathering of the Power Systems user community. Come see us in Booth 316.

BPCS/LX Tip of the Week: Batch Allocation

Anthony Etzel 0 75269 Article rating: 5.0

Thinking of moving from your old BPCS Version to LX?

There are numerous reasons to consider moving to Infor LX. It is a proven migration and it is easy to get there.

An area of interest may be allocations. Allocations can be difficult to manage, but with Infor LX, there is a new selection of ranges for Batch Allocations:

    • Sold To Customer
    • Ship To Number
    • Order Class
    • Order Number
    • Item Number
    • Request Date
    • Schedule Date

Baan/LN Tip of the Week: Safety Time

Kathy Barthelt 0 111027 Article rating: No rating

You can add safety time in the item master for the item. This will add the number of days safety time to the order lead time thus bringing the order in x number of days early. (x is the safety time).

The safety time is on form 4 of the item master in Baan IV and in Item Ordering Data – Generation I tab in Baan V and LN.

First127128129130132134135136Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

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 LN & Baan Finance Tip: How to clear balances on invoices that will be moved to a new company
Next Article Infor LN & Baan Manufacturing Tip: Performance Problems in Generate Order Planning (cprrp1210m000)
Print
80478 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories