Kathy Barthelt / Thursday, August 8, 2024

/ Categories: Infor LN & Baan Tips, Finance, Operations, Technology, Executive

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.

6734 Rate this article:

5.0

Kathy BartheltKathy Barthelt

Theme picker

Contact author

Name:

Email:

Subject:

Company:

City:

Region:

Country:

Telephone:

Mobile:

Message:

Please solve captcha

Tips: LX | BPCS | M3

28Nov2017

BPCS/LX Tip of the Week: Understanding What Goes On – Out on the Factory Floor

Tuesday, November 28, 2017

Ok… so you want to know the status of a specific shop order that was released two days ago.

What do you do?

It’s a sure bet that you have a manager, supervisor, or planner who can walk the floor and find the order at whatever work center it happens to be at. He/she can then answer “what operations have been completed and how many were completed?” All this requires leg work, and of course, a fair amount of time.

Now, if you have setup your BPCS master files properly, and you report transaction activity, you should be able to get those shop order statuses much faster using the SFC300 Shop Order Inquiry Screen.

At your fingertips you can see:

Release date & due date
How many hours remain in total and at each operation
The quantity required, what was finished and the remaining quantity
What components (materials) have been issued

Pretty basic information, right? Are you getting what you need to know? If not, then you may want to reexamine how your BPCS files are setup and what transactions along with their frequency are captured.

Optimize Your Manufacturing Today!

14Nov2017

BPCS/LX Tip of the Week: Role-Based Security

Tuesday, November 14, 2017

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, 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.

Optimize Your Manufacturing Today!

First Previous 83 84 85 86 87 88 89 90 91 92 Next Last

Theme picker

Tips: LN | Baan

13Nov2024

Infor LN & Baan Tips & Tricks for FINANCE: Use of Electronic Bank Statements

Wednesday, November 13, 2024

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

Bank Statement Workbench (tfcmg5610m100)
Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

16Oct2024