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

BPCS/LX Tip of the Week: Getting the Most Out of the Shop Order Inquiry Program – Part 1

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 these fields will have an impact on how you report transactions and what is seen on the SO inquiry screen.

Previous Article Baan/LN Tip of the Week: ERP Setup - Pros & Cons
Next Article Crossroads RMC Maintains Preferred Partner Status With Honeywell / Intermec for 2016
Print
36936 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

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

In general, you can enter a different series in the order field if you have an available series. To add a new series, find the appropriate group in the First Free Number session, and add a new series and first free number (usually 1).

In Baan IV, go to the Maintain First Free Numbers Session (under Common, Tables, Maintain Logistics Tables, Maintenance 1). Groups are easily identified (e.g., Purchase Order, Sales Order, etc.).

In Baan V, go to the First Free Number Session (under Common Data, Tables, Logistics). There are number groups (e.g., 570 may be for Purchase Orders, 650 may be for Sales Orders, etc.).

In LN, go to the First Free Number Session (tcmcs0150m000 – it is in different places in the menu under different Feature Packs). There are number groups (e.g., 210 may be for Purchase Orders, 310 may be for Sales Orders, etc.).

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan or 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.

To ensure, it’s recommended that the Integrations Setup tables should be audited either through Baan/LN or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.

First124125126127129131132133Last

Theme picker

Categories