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

Don't laugh - the average lifespan of an ERP system is 7-10 years

Crossroads RMC 0 33478 Article rating: 5.0

Don’t laugh! I know, I know…many of our customers say that after 7-10 years they are finally settling in after the implementation! We have seen many a customer stretch out the lifespan of their ERP system to 20+ years. That sounds great for the company’s bank account, but is it good for the business?

An outdated ERP system hurts your business in many ways, not just with slow performance. The best-of-breed functionality is now 2 decades old, and obsolete technology can't leverage newer technology. Lack of integration leads to siloed data that hurts communication and your internal teams feel the pain, and your customers are noticing. Poor visibility into your operations makes it nearly impossible to achieve industry-based regulatory compliance and meet financial auditing requirements. Not to mention the sheer size of Big Data that is being collected today vs. 2 decades ago or the fact that your vendor is no longer supporting your ERP version.

Let’s scrap it all and start over!...

Infor LN & Baan Tip: Purchase Order Text

Kathy Barthelt 0 63631 Article rating: 5.0

Is the text linked to the purchase order just an information field? Could it be used for another purpose?

The text editor is just an information field when linked to the purchase order line and there is no other logic behind this functionality. The line text or the header text could be a part of the printed document. When you add text to a purchase order line you are creating a unique code that links the purchase order line (Baan - tdpur041/ LN - tdpur401) to the text (tttxt010).

Infor LX & BPCS Tip: Vendor Terms Maintenance, ACP160D1

George Moroses 0 33766 Article rating: 5.0

This program allows maintenance of vendor terms, which you individually assign to each vendor. Vendor terms designate the due date and the discount date as a number of days after the invoice date. You establish the discount percentage here. Vendor terms are stored in the AVT file. Rather than use the method specified above, you can override due dates and discount dates so those calendar days are used to age invoices.

Access: Menu ACP02

Infor LN & Baan: BIG DATA - Keeping Track of Key Metrics

Kathy Barthelt 0 65356 Article rating: 5.0

In order to communicate effectively as a team, everyone needs to speak the same language and operate off the same playbook. If decisions are made based on the data or the view of data that individuals are maintaining through their own spreadsheets or other data silos, then communication is negatively impacted.

Manufacturers need to review large amounts of data every day, making it difficult to keep track of key metrics within your department.

That’s where Crossroads RMC’s Analytics Dashboard solution comes in. Our Analytics Dashboard was developed to make tasks easier by putting all of the key information in one convenient location so you can view all of your crucial data in real-time. 

With powerful dashboards, you can...

Infor LX & BPCS: Waste in Manufacturing

George Moroses 0 28959 Article rating: 5.0

In manufacturing, waste is anything that doesn’t add value to or benefit the end customer. Reducing waste enables manufacturers to save money and increase productivity. Where is the waste happening in your processes?

How often is your department spending time and resources on the following tasks?...

Infor LX & BPCS Tip: Overhead Costs - CST120D1

George Moroses 0 27142 Article rating: 4.0

Use this program to enter period overhead expenses to distribute to various work centers. You can set up this overhead cost allocation on either a per-hour or a per-piece basis, depending on the overhead allocation type specified for each work center on the Work Center Maintenance screen, CAP100D2-01. The system spreads the amounts entered across all shop orders posted by Shop Floor Posting, SFC600, or Production Reporting, JIT600, when you run Overhead Cost Allocation, CST510. The system stores allocated overhead in the Labor Ticket file, FLT, and updates actual item cost when you run Shop Order Close and Post, CST900.

Access: Menu CST

Infor LX & BPCS: BIG DATA - Keeping Track of Key Metrics

George Moroses 0 32558 Article rating: 5.0

In order to communicate effectively as a team, everyone needs to speak the same language and operate off the same playbook. If decisions are made based on the data or the view of data that individuals are maintaining through their own spreadsheets or other data silos, then communication is negatively impacted.

Manufacturers need to review large amounts of data every day, making it difficult to keep track of key metrics within your department.

That’s where Crossroads RMC’s Analytics Dashboard solution comes in. Our Analytics Dashboard was developed to make tasks easier by putting all of the key information in one convenient location so you can view all of your crucial data in real-time. 

With powerful dashboards, you can...

First3334353638404142Last

Tips:  LX | BPCS | M3

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
37317 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories