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: Work Center & Machine Locations

Anthony Etzel 0 47636 Article rating: No rating
For either file, you must specify a valid location code as defined in the Location Master File.

If the machine master locations are blank, then the work center locations are used. There are cases where you may want to do a combination between the two in defining the locations.

Let’s say the end item has one operation. The operation is at work center 510 and Machine A is in the work center. You have locations setup in both the Work center file and the Machine master File. You report 100 complete at the work center without specifying the machine.

In this case, the inventory will be processed based on the locations defined in the work center file. If the transaction included the machine number, then the locations in the machine file would be used.

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

Anthony Etzel 0 43021 Article rating: No rating

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.

RSS
First160161162163165167168169Last

Theme picker

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan 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 Baan/LN Tip of the Week: Getting a Handle on Downtime - Part 2
Next Article Baan/LN Tip of the Week: Ways to Prevent Scrap & Rework From Costing You
Print
40923 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories