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: Save Space in General Ledger

Kathy Barthelt 0 21585 Article rating: 5.0

One way to save space in your general ledger is to compress integration transactions. The transactions are combined into one ledger account number, and the detail is still available in the integration transactions sessions.

The compression is seen after the transactions are finalized. 

Compression is established in the mapping scheme by checking the box under the columns “Compression of Debit/Credit Transactions. This can only be done in a mapping scheme that is not activated. 

Infor LX & BPCS Tips: Purchase Order Print Security Validation

George Moroses 0 18539 Article rating: 5.0

This enhancement allows users to restrict access to purchase order print programs, providing additional security at the company and warehouse levels.

The purchase order print programs were updated to provide security validation for the user who selects the purchase orders to print. The security validation is controlled by the PO Print Security Validation flag on the Purchasing System Parameters screen, PUR820D-04.

Infor LX & BPCS Tip: Customer Tax Exempt Declarations, SYS160D1

George Moroses 0 16205 Article rating: 5.0

The Customer Tax Exemption Maintenance program, SYS160, allows you to specify customer declarations used by the Customer Order Entry (ORD) and Billing (BIL) applications to apply a tax rate code to specific order lines of an invoice.

With this program, Infor LX can invoice customers without value-added tax (VAT) if one of the following conditions occurs:

  • The cumulated...

Infor LN & Baan Tip: Important Porting Set Announcement (all versions of LN & Baan)

Kathy Barthelt 0 23936 Article rating: 5.0

There has been a recent porting set change due to Infor’s Product Life Cycle Policy.  

How to determine the maintenance stage of an Infor LN product version and release

Before a customer starts deploying Porting Set 9.4a or a later release, they must determine the actual maintenance stage of their Baan / Infor LN product. The definition of the maintenance stages for the product versions and releases of all versions of Baan and Infor LN are outlined in the Product Support schedule as published in the PLC policy. The maintenance stage of the ERP version is either “Mainstream Maintenance”, “Extended Maintenance” or “Sustaining Maintenance”.

How to manage Porting Set updates

The following conditions apply to customers who intend to upgrade to Porting Set 9.4a or later Porting Set releases:

Are You Running Your IT Department, or is IT Running You?

Crossroads RMC 0 19152 Article rating: 5.0

It's hard to efficiently manage your ERP system and support the users who rely on it every day when you are spending all your time running your manufacturing business. We get it and want you to know you are not alone. 

Are you able to answer any of these questions?

  1. How much available disk space is there on my ERP system box?
  2. What happens when users encounter an error in the ERP system?
  3. How are new employees being brought up to speed on ERP functionality?
  4. What needs to be done to ensure optimal performance of our ERP system?

If you don’t know all the answers that's because it's not easy to be the ERP guru of a company AND successfully stay on top of everything that is necessary to keep your business systems running efficiently and effectively. So, this begs the question…why do it? ....

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

Crossroads RMC 0 24393 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 21416 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 18662 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

RSS
First2021222325272829Last

Theme picker

Tips:  LX | BPCS | M3

Role-Based Security introduces Role type profiles and allows combining the use of Role profiles with the traditional LX User type security profile functionality. The new Role type profile can be defined to allow or deny access to All Products, Attention Key, Products, Programs, and Transaction Effects. Facility, Warehouse, and Company securities are still defined solely by the User profile settings and are not affected by the assignment of a Role. Where applicable, the Role authority is displayed alongside the User authority on the security profile maintenance screens making it easy to see where there are differences in authority between the User and the assigned Roles. 

When Users are assigned to Roles, security access in LX becomes a combination of authorities granted or denied by the Role, plus any User Exceptions. User Exceptions override authorities set by the Roles. A User can also be assigned to more than one Role.

12345678910Last

Theme picker

Tips: LN | Baan

Kathy Barthelt

Infor LN & Baan Tips & Tricks for EXECUTIVES:

OPERATIONS: Order Quantity Dependent Routings vs Default Routings
Order quantity-dependent routings
An automatically selected routing tailored to a specific production order quantity is useful. An example would be if the production order quantity is large, a routing with high production rates is used; If the order quantity is small, another routing is selected.

You can set up these quantity-dependent routings:

  • Select the Quantity-dependent Routing check box in the Item - Production (tiipd0101m000) session.

  • Enter the routing codes in the Item - Routings (tirou1101m000) session. Enter the maximum quantity for which a routing is valid in the Up to Quantity field.

Note: If multisite functionality is activated, the routings available may vary per site on the job shop bill of material selected. Differences in routings have an impact on the standard cost calculation.

Default routing

If the Quantity-dependent Routing check box is not selected, the default routing applies to an item. However, this default routing must also be linked to the item. To find out, LN checks the default routing code in the Default Routing field of the Job Shop Master Data Parameters (tirou0100m000) session. Next, LN checks whether the default routing code is linked to the item in the Item - Routings (tirou1101m000) session. If so, the default routing applies to the item. If the default routing is not linked to the item, no routing is used.


FINANCE: Integration Transactions - Compression
Integration transactions can be compressed before they are posted. For each integration document type, you can indicate whether the debit transactions and/or the credit transactions must be compressed.

Transactions can be compressed if the following transaction details have the same value:

  • The source financial company.

  • The destination financial company.

  • The transaction type and series.

  • The ledger account and dimensions.

  • The transaction currency.

  • The fiscal year and the financial period, the tax period, and the reporting period.

  • The integration document type and the Debit/Credit indicator.

  • If related gain and loss transactions are generated, the same compression criteria are used to compress these.

Note: Intergroup transactions are not compressed.

 
TECHNOLOGY: Infor LN Rest API

Frequently Asked Questions (KB2316174)

For Infor LN a framework has been developed to support REST API-based services for lean integrations. This framework is now made available for the LN application. This KB answers some common questions you may have and procedures that are needed for using the LN Rest APIs.

More details on these topics can be found in the Infor LN REST API Administration Guide.

Previous Article Infor LN & Baan Tips & Tricks for FINANCE: Integration Transactions - Compression
Next Article Infor LN & Baan Tips & Tricks for FINANCE: Ledger Account Blocked Error
Print
2796 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories