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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

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

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
Previous Article Tip of the Week: 8 Common-Sense Rules for Inventory Management
Next Article 6 Steps to Flawless Fulfillment
Print
27609 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

FINANCE: Default Billing Reason Code from User Order Class
This enhancement allows users to define a Default Billing Reason Code by User Order Class in addition to the Base Order Class. User Order Classes provide configurability for order processing events and the documents to be printed during those events. This enhancement allows users to configure different Billing Reason Codes for each User Order Class. If no specific code is defined, the system will default to the Billing Reason Code set up for the Base Order Class.

TECHNOLOGY:  Security Manager
New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves, but are only allowed to access regular LX programs if granted authority by an LX security officer.

OPERATIONS: Track all order holds added & released
Enhancement: Order Hold Audit Functionality
This enhancement introduces an audit file to track all holds added or released for customer orders. The audit file includes details for various types of holds: credit hold, margin hold, customer hold, user hold, and credit card hold. All applications that add or release a hold now write an audit record, capturing the user, date, time, and program associated with each hold action.

A new IDF Order Hold Audit Inquiry application allows users to review holds based on various criteria:

  • Hold type
  • User
  • Specific order
  • Transactions for a customer within a date range
  • Other combinations

Additionally, the selected data can be printed if desired.

New LX security type "M" for an LX Security Manager. Authority is similar to that of an LX Security Office (type "S"), but without the automatic authority to execute every LX program, and without the authority to change the authorizations of Security Officers and Security Managers. Users defined as LX security managers have authority to maintain security information for users other than themselves but are only allowed to access regular LX programs if granted authority by an LX security officer.

First2345791011Last

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:

1345678910Last

Theme picker

Categories