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

Kathy Barthelt
/ Categories: Infor LN & Baan Tips

Infor LN & Baan Tip: Navigating the Complexities of Surcharges on Phantom Items in Manufacturing

Is it ok to define surcharges on phantom items?

It is advised not to use surcharges on phantom items for the following reasons:

  1. The usage of phantom surcharges makes it, in general, more difficult to understand, verify, and explain the result of the cost price calculation.
  2. Real phantom items do not exist in real life. It is only an efficient way to specify the BOM. It is therefore questionable if surcharges should be defined for these non-existing phantom items.
  3. The usage of phantom surcharges can lead to variances in production orders, depending on the actual usage of the phantom.
  4. When surcharges based on added costs are defined for both the main item and the phantom item, then the surcharge will be applied twice.

Alternatives are:

  • Define the required surcharges on the main item of the phantom.
  • Define the required surcharges on the sub-item of the phantom.
  • Define a (backflush) operation on the phantom to cover the handling costs (if any) of a phantom item.
Previous Article Infor LX & BPCS Tip: Mastering the Latest Infor LX Innovations for Manufacturing Excellence
Next Article Streamline Your Audit Process: How Crossroads RMC and Avalara Ensure Compliance and Confidence
Print
12773 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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

Compressing Integration Transactions

One way to save space in your general ledger is to compress integration transactions. The transactions are combined into one ledger account number. However, the detail is still available in the integration transactions sessions.

The compression is seen after the transactions are finalized. 

Compression is established in the mapping scheme by checking the box under the columns “Compression of Debit/Credit Transactions". This can only be done in a mapping scheme that is not activated. 

In the Credit Control Parameters, you can indicate if the same letter will be sent for reminding and action taken if amounts are zero or negative. The reminder letters work in conjunction with overdue sales invoices and the “Reminder Diary Margin.” When an invoice has passed its due date plus a certain margin of days, LN generates a reminder advice for the invoice. 

First7273747577798081Last

Theme picker

Categories