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

Baan/LN Tip of the Day: Chart of Accounts

Kathy Barthelt 0 55767 Article rating: No rating

Zero sublevel accounts are posting level accounts. All others are parent accounts. Once the balances have been updated in the child ledger accounts, the parents are automatically updated.

Inquiries and reports can be printed or displayed either by child accounts or by parent accounts. On line drill-down is possible from either child or parent.

BPCS/LX Tip of the Day: Cycle Counting Part 2

Anthony Etzel 0 42283 Article rating: No rating

Understanding: The Cycle Count Alternative

The best way to cycle count is to count the same number of items each day and at the same time each day. The goal is to count your “A” items 4 times a year. The “A” items should be those item that are about 80% of the total inventory value and 20% of the total items. Consider creating your own cycle count schedule then instead of using the cycle count transaction, use the inventory adjustment transaction. The item balance is changed at the time the transaction is keyed. The transaction list can be used for the reconciliation process.

Baan/LN Tip of the Day: Company Calendar

Kathy Barthelt 0 53076 Article rating: 5.0

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.

RSS
First156157158159161163164165Last

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories