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

Baan/LN Tip of the Week: Configuring Items in Infor LN

Kathy Barthelt 0 72750 Article rating: No rating

In Infor LN, the configuration of a generic item not always results into a customized item. Configured items can now be customized items as well as standard items. If users configure items without PCS projects, standard items are generated instead of customized items.

Baan/LN Tip of the Week: Optionally Include Tax Amounts In Order Balance

Kathy Barthelt 0 65385 Article rating: No rating
In Baan IV, the order balance amount always includes the tax amount. Consequently, the tax amount must be recalculated every time an order line is modified in order to update the balance correctly. If the tax provider is activated, this requires an API call for every re-calculation of tax.

In Infor LN, users can select or clear the new Include Tax in Order Balance check box in the COM Parameters (tccom0000s000) session to indicate whether users want to include tax amounts in the order balance amount. This parameter has an effect on various sessions in Order Management.

BPCS/LX Tip of the Week: Shop Order Status

Anthony Etzel 0 55182 Article rating: No rating

You can see the status of the Shop Order when using SFC300 Shop Order Inquiry. You want to be sure that your shop orders are at the correct status in order to report against them.

The following are the shop order status codes:

04 = The Shop order has been entered.

05 = The Shop order has been released and printed.

14 = The Shop order has been released, but not printed. If a shop order is at this status, you have released it and it is not printed due to a system failure, or the order has been put on hold.

XX = The Shop order is closed.

BPCS/LX Tip of the Week: Work Center & Machine Locations

Anthony Etzel 0 54393 Article rating: 4.0
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.

Baan/LN Tip of the Week: What could go wrong with GRINYA?

Kathy Barthelt 0 67153 Article rating: No rating
One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

Baan/LN Tip of the Week: Differentiating An Item By Supplier - LN

Kathy Barthelt 0 69444 Article rating: No rating

In LN, you can differentiate between items at various suppliers:

  • Locations (warehouses),
  • Purpose (planning, purchase)
  • Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:
 
  • Items - Planning (cprpd1100m000)
  • Check Item Data by Warehouse (whwmd2210m000)
  • Item Supplier Plan (cpvmi0530m000)
These sessions define entities that have an n-to-1 relationship with the general item data.

 

BPCS/LX Tip of the Week: Inventory Control

Anthony Etzel 0 54933 Article rating: No rating

In Infor LX you need to determine how inventory will be moved in and out of warehouse storage locations, and which of the following transactions to use for inventory control:


  • A transfer transaction can be used to move inventory from one warehouse location to another warehouse location.
  • A production receipt transaction is used to add inventory to a warehouse location.
  • A material issue or backflush is used to reduce inventory from a warehouse location.

New Definition of Insanity: Collect data the same old way

Anthony Etzel 0 83714 Article rating: 5.0

Just because you've always done it this way doesn't mean it's the best way. The old way of doing things may get the job done, but is the job being performed efficiently, accurately, and on a timely basis?

People resist change because there is an element of fear behind change and having to learn something new. Sometimes it’s just that you’re comfortable with how things are done, and you don’t see the need to make any changes. 


Are you stuck in manual?

RSS
First164165166167169171172173Last

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: The Key to Increasing Efficiency

Want to increase your efficiency across your organization?

Is access to real time data important to you?

Take a look at how and where your information is stored. Do you have employees keeping separate spreadsheets or databases outside of your ERP?

Separate data silos means that information is not being shared between departments. This can hamper growth, and cut down on overall efficiency. Take a look at why these silos exist. Can something be done within your ERP system to avoid having to store the information elsewhere? Can an integration be created to allow the ERP to have exposure to other databases, or allow updates to occur between systems?

Need help figuring out where to start? Contact us. We’d be happy to help.

Optimize Your Manufacturing Today!

Previous Article Baan/LN Tip of the Week: Month End Miscellaneous To-Do’s
Next Article Baan/LN Tip of the Week: Invest in Your Employees
Print
39110 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories