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: Getting the Most Out of the Shop Order Inquiry Program – Part 1

Anthony Etzel 0 36881 Article rating: No rating

Understanding: How many hours remain in total and at each operation?

First let’s look at some key BPCS Master File data starting with the routing file.

How many routing steps (operations) are set up that reflect how the product is produced in the factory? If you take a short cut and set up only one operation for the entire process, then you will limit the information seen on the SO inquiry program. Set up the operation steps to reflect what you want to report back to from the factory floor.

Will each of the routing steps run in one work center, or in different work centers? To keep it simple you may want to set up work centers as departments. For example:

  • Assembly
  • Machine
  • Paint
  • Etc.

For each operation setup consider how you have set up the following:

  • Load Codes – for example a code 5 is used if reporting both setup time and run labor time. These codes are maintained in the work center file
  • Basis Code – typical codes are P for pieces per hour,  3 is used for hours per 1,000 pieces
  • Setup hours – if you set them up, you also want to report them
  • Run hours – Direct Labor
  • Machine hours

How you set up th

Baan/LN Tip of the Week: ERP Setup - Pros & Cons

Kathy Barthelt 0 48241 Article rating: No rating

You may have started your setup of your ERP system one way, and have discovered over time that maybe it no longer fits how you need to do business. Over the next few weeks, I’ll be providing some pros/cons to consider for different company setups.

Pros/Cons of Single Finance / Single Logistic Company Set-Up

Pros
Easy to implement and to maintain.
No risk of processing data for another company.
Data not visible across companies – pro if you do not want users to see other company’s data.
Cost Prices can be different for the same item in the different logistics companies.
Easy to add or remove companies when companies are bought or sold.
Accounting functions are all separate by company. – Pro if each finance company is managed separately.
 

 

Cons
Decentralized operations – purchasing, sales, manufacturing, planning, warehousing, etc.
User must go in and out of companies if there is a need to view or create transactions in more than one company.

It’s NOT All About the Money, Money, Money… Motivating Employees in the New Year!

Kathy Barthelt 0 33452 Article rating: 5.0

Have you ever thought about what really motivates your employees?

It’s not about the almighty dollar, you know. Ok, ok…..money doesn’t hurt, but money alone doesn’t keep most people in their jobs. You actually need to motivate your employees to keep them showing up, mentally, and physically. Employees that don’t feel motivated are probably underperforming, and that means you’re losing money.

Ask yourself these questions about your employees:

  • Are they happy…..YES….HAPPY! Do they enjoy coming to work every day?
  • Do they feel challenged, or do they feel demeaned?
  • Are they sinking, or are they swimming?
  • Do they have the right tools in their arsenal to battle the giants?
  • Where’s the reward?

Happiness - I’ve worked with manufacturers for almost 20 years now...

RSS
First129130131132134136137138Last

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

Infor LN & Baan Tip & Tricks for OPERATIONS: Best Practices for Purchase Order Archiving / Deleting

 Here are some best practices to follow if you are considering archiving or deleting purchase order data:

  • If Financials 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.
  • Purchase contracts must be archived before purchase orders can be 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's linked to the purchase order line, and for which an internal invoice must be sent from the purchas 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.

Previous Article Infor LN & Baan Tip & Tricks for TECHNOLOGY: Using Table Boosters to Speed Up Sessions & Processes
Next Article Infor LN / Baan Tips & Tricks for EXECUTIVES
Print
9420 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories