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
12516 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

The Infor Development Framework (IDF) re-architects the way a user interacts with the application. IDF provides an efficient, task-oriented process to view application information that is contained within Infor LX. IDF enables users to configure their view of the application data without modifying the core application and its supportability.

The examples below describe how users can configure their display of data and maximize overall productivity:

  • Arrange application information into multiple groupings and sequences that make sense for the job.
  • Hide information that does not apply to a particular job or task.
  • Filter records to show only the information that applies to the job or task that the user is performing.
  • Customize the information for an individual user, for a group of users, or for all users.
     

Did you know?  Product interface list, SYS635D

This program creates a report that contains all interface program call records that were created for the Infor LX programs specified in the range on this screen. The report contains a line for each record found. The line displays the following information:

  • The name of an Infor LX program that contains a user exit to an add-on program
  • The interface point in the Infor LX program, that is, an identifier of the point in the program code where the user exit is requested
  • The execution sequence number of the record, because more than one add-on program can exist that can run from the same interface point
  • The add-on program to call at the interface point. The Add-on Product Interface file, ZXI, stores the records.

Access: Menu SYS

First3637383941434445Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

1345678910Last

Theme picker

Categories