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

Infor LX & BPCS Tip: Tracking Financial Journal Entries

George Moroses 0 21736 Article rating: 5.0

An 8.4.1 EGL audit enhancement now provides visibility to who and when a financial journal was last maintained and to who and when the journal was approved. The enhancement provides audit attributes for last maintain user, date, time and approval user, date time on the Financial Journal Entry and Financial Journal Entry Lines.  

The programs or areas impacted include:

Is Your ERP System Hurting Your Business?

The Importance of an Integrated System

Kathy Barthelt 0 16922 Article rating: 5.0

It could be if your ERP system isn't integrated with other systems that contain mission-critical business data.

Having data in two (or more) systems that don’t talk to one another is like baking a pizza crust in one oven and the toppings in another. Once baked, you may have food to snack on, but it sure isn’t pizza! Pizza requires the cheese, sauce and spices to bake with the crust, so all the flavors meld together when you take that first delicious bite. 

That’s the value of an integrated ERP system. When you...

Optimize with Infor Development Framework: IDF

Infor LX | BPCS | M3

George Moroses 0 19224 Article rating: 5.0

Why You Need IDF

The Infor Development Framework (IDF) not only helps you modernize the look and feel of your LX software but also the interactions of the IBM i software with other applications in your business.

“The IDF is a multi-user interface, single codebase architecture that’s metadata-driven (and) provides a lot of flexibility to adapt the software for their processes.” says Infor. This is the direction that Infor is going starting...

First2829303133353637Last

Tips:  LX | BPCS | 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 3

Understanding: The quantities required, finished and remaining at the operation and in total for the Shop Order

The shop order may require 1,000 pieces but only 950 are reported as finished in total for the shop order. The quantity required is what is planned on the SO and it may be a higher number than what is finished, factoring in that there can be scrap. If a 1,000 pieces are required to be produced, and there is always is scrap of 10 pieces, then plan for scheduling a quantity of 1,010.

The quantity finished for the end item is what is reported in the inventory application with a production order receipt transaction. At the operation level, if the quantity is reported at the operation, there will be a value in the PCS Complete field on the operation detail screen showing the pieces completed through that operation.

If you want to get a handle on the difference between the required quantity and the finished quantity, you may want to look into reporting quantities at the operation level as well as examining how scrap is controlled and reported.

Previous Article BPCS/LX Tip of the Week: Getting the Most Out of the Shop Order Inquiry Program – Part 2
Next Article BPCS/LX Tip of the Week: Understanding What Goes On Out On The Factory Floor – Part 4
Print
57318 Rate this article:
No rating

Contact

Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

Contact author

x

Tips: LN | Baan

Use this session to to define which fields must be audited, and when they must be audited.

Note: 

  • It is not required to define the fields that must be audited. Only if not all fields in a table must be audited, you must specify the fields that must be audited. You can only specify fields for a table for which you selected Specified in the Field Selection field of the Audit Tables by Profile (ttaud3120m000) session. If you selected All in that field, all fields in the table are audited, and no fields can be specified.

  • For a detailed explanation of the relation between audit type and field specification, refer to the section How to determine the net result of the audit configuration in the Audit Configuration Management topic.

  • The audit functionality uses the positive approach, which means that you can only specify which tables and fields must be audited, but not which tables and fields must not be audited. Therefore, through the appropriate menu, commands are available to load all (key) fields. You can then delete the fields you do not require.

Categories