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

BPCS/LX Tip of the Week: Work Center - Cells

Anthony Etzel 0 57693 Article rating: No rating
The LMP module (Lean Manufacturing Process) uses work centers but refers to them as production cells.

A cell is one or more work centers that produces an end item. So when a company decides to adopt the lean manufacturing philosophy, the concept of work centers takes on a new meaning.

In lean terms, the work center, or group of work centers, becomes a production cell. In other words, a mini-factory producing end items with similar characteristics.

Baan/LN Tip of the Week: Closed, Final Closed, Provisional Close – What’s The Difference?

Kathy Barthelt 0 73110 Article rating: No rating

Fiscal, Reporting and Tax Periods can have status Open, Closed or Final Closed. If a period is Closed or Final Closed, you cannot post entries to those periods. If a period is Closed, you can re-set it to Open and post entries. If a period is Final Closed, you cannot post and you cannot set it back to Closed or Open.

A Provisional Close is run at year-end to bring the balances forward for the new year without having to close the previous year. A Provisional Close can be run as many times as you like. After a Final Close, a Provisional Close cannot be run.

The Provisional Close allows you to continue into the new year with all financial reporting and not have to rush with the Final Close until all adjusting entries are made and any final signoffs have been completed.

Baan/LN Tip of the Week: Product Families

Kathy Barthelt 0 73673 Article rating: No rating

In Baan IVC, plan items on the lowest plan level were automatically actual items (not product families). All plan items on higher plan levels were product families.

The relationship between a product family and items on lower plan levels was defined in a planning bill of material.

In Infor LN, every family item must be defined in the Item Base Data module. A family item can exist on any plan level. The relationship between a family item and items on lower plan levels is defined in aggregation relationships.

Aggregation relationships in Infor LN are much more flexible than the planning bills of material in Baan IV. For example, users can define aggregation relationships between items on the same plan level.

BPCS/LX Tip of the Week: Create the Master Schedule

Anthony Etzel 0 70679 Article rating: No rating

In the master schedule creation, you have the flexibility to enter a planning start date, or default to the facility planning start date. Infor LX uses the planning date to plan both orders with forecasts and customer orders as demand.You can create your master schedule from the Master Production Scheduling module (MPS).

No one cares how hard you work! How you can do more, while doing less – know your MO.

David Dickson 0 53731 Article rating: 5.0

Would you like me to tell you a dirty, little secret?

No one cares how hard you work. Sure, some people will notice if you seem to be working hard. Your spouse or companion might note that you seem tired, stressed, not as much fun, or just aren’t around much, but they care about the consequences, not how hard you work. Your boss might note happily that his staff seems busy, things are humming along, but you can be sure that when it is review time she gets no credit for “keeps staff very busy.” Nor will the boss give you extra points for being busy. It is about results.

People outside your personal life, beyond your coworkers, might notice that you are hard to contact, perhaps because you are so busy. But trust me, customers do not care why they can’t get hold of you, and they will not see it as a positive.

Infor and Crossroads RMC are proud to offer a joint webinar on Taking Your Shop Floor Paperless - August 28th, 2014.

Anthony Etzel 0 43363 Article rating: No rating

Taking Your Shop Floor Paperless - Webinar, August 28th, 2014.

During this webinar, you will learn about the Crossroads MES Shop Floor Solution which gives you the ability to do all the following and more:

  • Collect production data
  • Provide real time feedback to your workers and your management team
  • Integrate to machines on your shop floor to pull counts directly
  • Provide up-to-date electronic versions of shop floor paperwork at the work center
  • Monitor your production against your key performance indicators
     

Join us on Thursday, August 28th at 12:00 p.m. Eastern to learn more.

TO REGISTER:

linked removed...

Baan/LN Tip of the Week: Company Calendar

Kathy Barthelt 0 70831 Article rating: No rating

Baan uses the company calendar in the following modules to determine the start and end dates for planned orders:

  • Master Production Scheduling
  • Material Requirements Planning
  • Capacity Requirements Planning (All three combined in a single planning module for Baan V and LN)
  • Shop Floor Control

The calendar provides the valid working days, number of shifts per day and the number of hours in a day.

Baan allows for a single calendar for the whole company or for a calendar for each work center.

BPCS/LX Tip of the Week: SFC600 & SFC650

Anthony Etzel 0 79132 Article rating: No rating

These programs are used to capture and post shop floor information. Labor reporting, machine time, etc. can be captured by either program. The key difference is that one will also capture the production receipt and backflush components. Based on your company information / transaction process, one of these programs will most likely be used daily to capture current shop floor data. You can use the shop packet labor ticket for the manual recording, and the keying of the data. Alternatively, you can incorporate an automated method like an MES solution to capture the data and streamline the process.

First119120121122123125127128

Tips:  LX | BPCS | M3

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

  • When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

This enhancement improved the subfile utilized in MRP320D Master Schedule Detail Inquiry -SCR001 by expanding the subfile with data rather than clearing the subfile as user pages. This change provides full support for the WebTop 4.8 Grid decorator.

This enhancement updated the approach used to populate the subfile to allow a deployed Webtop Grid to function correctly. There is no visible or user-impacted change to the way the program functions.

This enhancement provides improved functionality and full support of a Webtop grid applied to the subfile.

Last

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE Tip: Remap Posted Integration Transactions (tfgld4282m100)

Use this session to remap Posted transactions that were mapped incorrectly.

To remap integration transactions successfully, several conditions must be fulfilled. For details, refer to To remap integration transactions.

Enter the ranges of selection criteria for the integration transaction or range of integration transactions to be remapped. You can select the integration transactions of a range of business objects or of a specific business object.

You must select a specific integration document type or an integration document type group.

To evaluate the remapping before you perform the actual remapping, you can select the Simulate check box and the Error Report check box. After you solve the errors, you can run the session again and clear the Simulate check box.

After remapping the integration transactions, you can use the Post Integration Transactions (tfgld4282m000) session to create the postings in the General Ledger.

OPERATIONS Tip: Using Country of Origin for Purchase Orders

For purchase orders, information about the COO allows you to track the related import duties, tariffs, and compliance with sourcing requirements. You can maintain the COO of an item when creating an order or the release level of a purchase order.

When you create a purchase order line in the Purchase Order Lines (tdpur4101m000) session, the COO related details are defaulted based on the item-purchase data defined in the Items - Purchase (tdipu0101m000) session. To view this data, you can use the Country of Origin option from the References menu in the Purchase Order Lines (tdpur4101m000) session.

After the order line is released to Warehousing, an inbound line is created in the Inbound Order Lines (whinh2110m000) session with the COO information. A receipt line is created in the Warehouse Receipt Lines (whinh3512m100) session when the inbound order line is received. To view the actual COO for the item specified on the receipt line, you can use the Country of Origin option from the References menu in this session.

You can view the country of origin (COO) data for the inventory received in a warehouse in the Item - Country of Origin Inventory (tcitu6600m000) session based on the data specified in the header section such as, warehouse, item, and so on.

In the Inventory Tracking Receipt (tcitu2610m000) session, you can view the information related to the purchase order, inventory quantity, and actual COO of the item. You can use the Intrastat Transactions (tccom7171m000) session to view the COO that is reported for an order line and is used for the Intrastat declaration.

TECHNOLOGY Tip: Impact of Configuration Changes on Audit Trails:

Impact of Configuration Changes on Audit Trails

The impact of changes in the audit settings varies depending on the specific circumstances. The issues typically arise when changes made to audit settings are implemented at runtime without requiring all users to exit the system (LN). As a result, some users may continue to generate audit trails using the old configuration, while those who log in after the changes take effect will create audit trails based on the new configuration.

Changes in User Profiles

Below is a summary table that illustrates the effects of these changes for a specific table within a company:

Change Description Impact
Add a table Users that still use the old settings do not audit some transactions.
Remove a table Some transactions that must not be audited with the new settings are still audited by users that use the old settings.
Change the audit type for a table or field Some transactions are audited according to the old settings, and other transactions are audited according to the new settings.
Add or remove a field After you audit transactions in the table with the new settings, users that use the old settings can no longer perform transactions on this table. Therefore, users with the old settings can be forced to restart LN.

Note on Changes in Field-Specific Auditing:
When you toggle field-specific auditing on or off for a table, which alters the number of fields being audited, the effect is analogous to adding or removing a field. However, not every modification to the audit settings impacts the runtime settings. Converting the new settings to runtime might result in no net change for the entire configuration if the overall effect of the adjustments neutralizes each other.

Previous Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Impact of Configuration Changes on Audit Trails
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES
Print
28124 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories