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 LN & Baan Tip: Separate item codes for incoming & outgoing subassemblies

Kathy Barthelt 0 63573 Article rating: 5.0

You may be wondering if it's necessary to have separate item codes for incoming and outgoing subassemblies.

No, it is not necessary to have separate item codes for incoming and outgoing subassemblies, but it is recommended. In theory, you could have only one item code with the description subassembly and use the same item code for the outgoing subassembly and for the incoming subassembly. However, when monitoring inventory movements and financial integration transactions, it will be difficult to understand the process. Also, the costing logic is much clearer when different item codes for the incoming and outgoing subassemblies are used. Because of this, it is advised to use a different item code for the outgoing subassembly and a different item code for the incoming subassembly.

Infor LX & BPCS Tip: Changing an item to non-inventory

George Moroses 0 24919 Article rating: 5.0

When an attempt is made to change an item’s type to a non-inventory item from any other value, a new validation is performed to determine if the item has any inventory on hand and, if so, prevents changing the item’s type.

This enhancement available in LX 8.4 prevents LX from showing an on-hand inventory balance for a non-inventory item.

The programs or areas impacted include:

  • Facility/Planning Data Maintenance, MRP140D2
  • IDF Enterprise Item

To get this enhancement, request and apply MR 80120.

Top 10 Things (you might not know) About Crossroads RMC

Crossroads RMC 0 16238 Article rating: 5.0


10.  Crossroads RMC has been in business since 1984 & has been an  partner since 1991
 

 9. Crossroads RMC offers functional & technical training on all versions of Infor LX, BPCS, Infor LN, and Baan and will completely tailor the training to your specific needs. 🤝🏽

 8.  Our consultants have over 1,000 years of combined experience working with manufacturers just like you! 🤓

 7.

 6.

 5.

 4.

 3.

 2.

 1.

DATA: See it. Understand it. Discuss it.

Crossroads RMC 0 16374 Article rating: 5.0

We’ve all heard author and management consultant Peter Drucker’s famous quote “If you can’t measure it, you can’t manage it.”  

What’s the right way to manage “It” though? Is it enough to put the data in the hands of the responsible manager and wait for change to occur? Does the manager have a pulse on everything that went into those numbers?

Your numbers tell a story, but there is a lot of...

Infor LX & BPCS Tip: Tracking Financial Journal Entries

George Moroses 0 22211 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:

First2930313234363738Last

Tips:  LX | BPCS | M3

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES

FINANCE: Clear Rounding Differences for Documents with Period Change (tccri7214m000)

Use this session to adjust the rounding difference transactions, calculated during the internal conversion, for inter-period postings.

Inter-period postings are the postings made to the ledger accounts defined in the Finance Company Parameters (tfgld0503m000) session for fiscal and reporting period changes.

If inter-period postings exist, very big rounding differences are calculated . If you run this session, those rounding differences are replaced with values that properly deal with an observed period change.

If inter-period postings exist, during the internal conversion rounding differences can be calculated for the wrong period. If you run this session, those rounding differences are deleted and the rounding differences are created for the correct period.



OPERATIONS: Sales Contract Linked Documents (tdsls3506m000)

Use this session to view the documents linked to a sales contract. You can view these documents only when a sales order line or a sales schedule line is linked to a sales contract line.

Note: 

  • You can view this session only if the Contracts check box is selected in the Sales Parameters (tdsls0100s000) session.
  • You can use the Linked Document option from the References menu to view the details of a specific linked document.


Field Information

Contract: The code of the sales contract.

Description: The description of the sales contract

Line: The sequence number of the sales contract line.

Sales Office: The code of the sales office.

Description: The description of the Sales Office

Linked Document: The document type that is linked to the sales contract line.

Note: This field can be set to Sales Order Line or Sales Schedule Line only.

Linked Document Company: The company in which the document is linked to the sales contract line.

Linked Document: The code of the document that is linked to the sales contract line.

Note: 

  • The code of the sales order is defaulted from the Order Line field in Sales Order Lines (tdsls4101m000) session.
  • The code of the sales schedule is defaulted from the Schedule field in the Sales Schedule Lines (tdsls3107m000) session.

Linked Document Reference: The reference number of the linked document.

Note: 

  • The line number of the sales order line is defaulted from the Line field in the Sales Order Lines (tdsls4101m000) session.
  • The line number of the sales schedule line is defaulted from the Line field in the Sales Schedule Lines (tdsls3107m000) session.

Link Sequence: The sequence number of the linked document.


TECHNOLOGY: Audit Fields by Table (ttaud3125m000)

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.
     

Previous Article Infor LN & Baan Tips & Tricks for TECHNOLOGY: Load Audit Tables for Profile (ttaud3220s000)
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Clear Rounding Differences for Documents with Period Change (tccri7214m000)
Print
574 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

x

Categories