Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Tip of the Week: The 3 Secrets to Improving Your MO (Manufacturing Optimization)

Kathy Barthelt 0 39074 Article rating: No rating
  1. Identify the key metrics. You need benchmark data so you know what realistic goals are, then track them and publish your performance along with a brief comment from time to time on how things are trending and how you compare with others, particularly your primary competitors. The best thing about this is that it is a system that develops a life of its own.
     
  2. Measure it. Automatically, people start to think about improving things. Then the fun part, stuff begins to improve by itself. Once in place, the system just hums along and the benefits appear, because it has motivated people to think about it, and figure out what they can do to make it better.
     
  3. Communicate it. Publish your numbers, and explain to people how what they do affects the company as a whole and its success/failure. Once they see the numbers, employees quite often start to modify their behavior for the better.

Optimize Your Manufacturing Today!

Read more

BPCS/LX Tip of the Week: CEA

Anthony Etzel 0 28819 Article rating: No rating

CEA Upload provides the capability to prepare both Budgets and Journal Entries in Excel. Once the spreadsheet is complete, it can be uploaded to CEA for posting as an entry to the GL Book of choice. Ease of use is achieved and a full audit trail is created. LX users can capitalize on their investment in both CEA and Excel to achieve a better accounting process. 

Optimize Your Manufacturing Today!

Read more
RSS
First100101102103105107108109Last

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.

Read more

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.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt
/ Categories: Infor LN & Baan Tips, Finance, Operations, Technology, Executive

Infor LN & Baan Tips & Tricks for EXECUTIVES:

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:

  • Select the Quantity-dependent Routing check box in the Item - Production (tiipd0101m000) session.

  • Enter the routing codes in the Item - Routings (tirou1101m000) session. Enter the maximum quantity for which a routing is valid in the Up to Quantity field.

Note: If multisite functionality is activated, the routings available may vary per site on the job shop bill of material selected. Differences in routings have an impact on the standard cost calculation.

Default routing

If the Quantity-dependent Routing check box is not selected, the default routing applies to an item. However, this default routing must also be linked to the item. To find out, LN checks the default routing code in the Default Routing field of the Job Shop Master Data Parameters (tirou0100m000) session. Next, LN checks whether the default routing code is linked to the item in the Item - Routings (tirou1101m000) session. If so, the default routing applies to the item. If the default routing is not linked to the item, no routing is used.


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.

  • The destination financial company.

  • The transaction type and series.

  • The ledger account and dimensions.

  • The transaction currency.

  • The fiscal year and the financial period, the tax period, and the reporting period.

  • The integration document type and the Debit/Credit indicator.

  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

 
TECHNOLOGY: Infor LN Rest API

Frequently Asked Questions (KB2316174)

For Infor LN a framework has been developed to support REST API-based services for lean integrations. This framework is now made available for the LN application. This KB answers some common questions you may have and procedures that are needed for using the LN Rest APIs.

More details on these topics can be found in the Infor LN REST API Administration Guide.

Previous Article Infor LN & Baan Tips & Tricks for FINANCE: Integration Transactions - Compression
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Ledger Account Blocked Error
Print
6910 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Theme picker

Contact author

x

Categories