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

BPCS/LX Tip of the Week: Ways to Prevent Scrap & Rework From Costing You

Anthony Etzel 0 35262 Article rating: No rating

Scrap and rework costs are a manufacturing reality impacting organizations across all industries and product lines.

Scrap and rework costs are caused by many things—when the wrong parts are ordered, when engineering changes aren’t effectively communicated or when designs aren’t properly executed on the manufacturing line.

No matter why scrap and rework occurs, its impact on an organization is always the same—wasted time and money. And while no one, especially an operations manager, wants to admit it, these expenses add up quickly and negatively impact the bottom line...

Read Full Article

Baan/LN Tip of the Week: Ways to Prevent Scrap & Rework From Costing You

Kathy Barthelt 0 61434 Article rating: No rating

Scrap and rework costs are a manufacturing reality impacting organizations across all industries and product lines.

Scrap and rework costs are caused by many things—when the wrong parts are ordered, when engineering changes aren’t effectively communicated or when designs aren’t properly executed on the manufacturing line.

No matter why scrap and rework occurs, its impact on an organization is always the same—wasted time and money. And while no one, especially an operations manager, wants to admit it, these expenses add up quickly and negatively impact the bottom line...

Read Full Article

Tip of the Week: 8 Common-Sense Rules for Inventory Management

Anthony Etzel 0 35476 Article rating: No rating

Common sense rules. We may not like them, but generally, they stand the test of time and should be followed. Here are 8 common sense rules related to inventory management published by Inbound Logistics back in 2007. They still hold true today. 

1. If you don' t know where you are going, no road will take you there. Enterprise resource management systems are designed to tell you about today' s inventory. With some work, you can also access information about past inventory. To manage inventory proactively, however, you must know projected inventory levels for the future.

2. Make what you can sell. An integrated Sales and Operations Plan will naturally take into account expected demand in its production plan. Inventory is not an independent variable - it is the direct result of demand and supply.

3. Sell what you can make. Too often, a disconnect exists between sales and marketing desires and the reality of production capabilities.

4. If you can' t sell it, stop making it. If demand for your product does not materialize, you need to identify that gap quickly to avoid a buildup of non-moving inventory. Numerous mechanisms can be put in place to identify such trends.

For tips 5 through 8 and more details into the other tips, click the button below to read the full article.

Read Full Article

Tip of the Week: 8 Common-Sense Rules for Inventory Management

Kathy Barthelt 0 60493 Article rating: No rating

Common sense rules. We may not like them, but generally, they stand the test of time and should be followed. Here are 8 common sense rules related to inventory management published by Inbound Logistics back in 2007. They still hold true today. 

1. If you don' t know where you are going, no road will take you there. Enterprise resource management systems are designed to tell you about today' s inventory. With some work, you can also access information about past inventory. To manage inventory proactively, however, you must know projected inventory levels for the future.

2. Make what you can sell. An integrated Sales and Operations Plan will naturally take into account expected demand in its production plan. Inventory is not an independent variable - it is the direct result of demand and supply.

3. Sell what you can make. Too often, a disconnect exists between sales and marketing desires and the reality of production capabilities.

4. If you can' t sell it, stop making it. If demand for your product does not materialize, you need to identify that gap quickly to avoid a buildup of non-moving inventory. Numerous mechanisms can be put in place to identify such trends.

For tips 5 through 8 and more details into the other tips, click the button below to read the full article.

Read Full Article

Crossroads RMC to Exhibit at Inforum 2016

Crossroads RMC 0 26495 Article rating: No rating

Inforum 2016  returns as a three and a half-day event of educational seminars and workshops focused on the future of enterprise software and your business. This event is Infor’s premier event for 2016, and Crossroads RMC is excited to sponsor the event! Come see us in Booth 173 to learn about Crossroads MES and Analytics Dashboard solutions for the shop floor, our Services for Baan/LN and BPCS/LX, and see a demo of our latest solution, Analytics Dashboard, which can be connected to any ERP to provide up to the minute sales analysis data.

    
 

If ERP is plumbing for the Enterprise - How do we unplug it and keep it from making a huge mess?

David Dickson 0 34066 Article rating: 5.0

I have been working with ERP in various roles for over 30 years, directly involved in over a hundred implementations, while my company has been involved with over 400 more. Of course, in many ways the systems we use today are completely different from what we used in the ‘80s – back then it was green screens, simple transaction entry forms, and cumbersome updates (at best) to link what one department did with all the other areas that needed access to that information. Then there were those planning programs that took all the information along with various parameters the users needed to set and told us what to do.

The More Things Change, the More They Stay the Same

First96979899101103104105Last

Tips:  LX | BPCS | M3

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

BPCS/LX Tip of the Week: The Item Master Requirements Code

In the Item Master File, the requirements code is used to specify the type of demand for the item. Planned order requirements are determined from the type of demand. If the requirements code is left blank, the planning systems treat the item as a sum code (3).


Other options for the field are:

1 = Dependent demand that is indirectly generated from the parent item requirements.

2 = Independent demand generated from customer orders and forecasts.

3 = The Sum of both independent and dependent demand.
Previous Article BPCS/LX Tip of the Week: How To Capture Re-Work Time (Part 1)
Next Article BPCS/LX Tip of the Week: Work Center & Machine Locations
Print
65672 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

Users can personalize sessions and apply special formatting to the data displayed in sessions. The personalizations and formatting settings that are specified by the users are stored on the LN server. Administrators can maintain these settings.

  • Session personalizations

    Users can personalize sessions in various ways. users can, for example, hide fields, change labels, customize the toolbar, and move fields to another tab. Administrators can maintain the personalizations defined by the users. For example, an administrator can export personalizations to an XML file, import personalizations from an XML file, and copy personalizations to another user, to a DEM role, or to a company number.

  • Report personalizations

    You can use the Report Designer (ttstppersrep) to personalize the layouts and style of reports, without modifying the standard reports or using an external reporting solution. The changes are stored as personalizations.

    You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer (ttstppersrep), or modify them in Infor LN Studio.

    For details, see the Infor LN Report Designer Development Guide
     
  • Conditional formatting

    users can define conditions to apply special formatting to the data displayed in LN sessions. The users can define multiple conditions per session and different types of formatting, such as a specific color for particular fields or rows, and a warning symbol for particular rows. Administrators can maintain the formatting settings specified by the users and can define system-wide formatting settings.

  • If Finances is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.

You cannot delete a purchase order (line) if:

  • The linked warehouse order is closed but cannot be removed.
  • The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
  • A consignment replenishment order is not yet consumed completely.
  • The invoice is yet to be completely matched and approved.
  • The invoice amount is not yet inserted as turnover history.
  • The sales order or service order that is linked to the purchase order line, and for which an internal invoice must be sent from the purchase office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.

Categories