Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Resources Infor ERP Tips & News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Subscribe to newsletter

Kathy Barthelt
/ 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.

Previous Article Infor News You Can Use: Discover the Power of Advanced Planning & Scheduling with industry expert Greg Keating
Next Article Infor News You Can Use | Why Upgrade to Infor LX in the Cloud
Print
2833 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt
Contact author

Theme picker

Contact author

Please solve captcha
x

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.

Read more
12345678910Last

Theme picker

Tips: LN | Baan

How do I assign an unallocated payment to a purchase invoice when the document dates are not the same?

When trying to assign an unallocated payment, it is possible that the purchase invoice is not displayed in session Assign Unallocated / Advance Payments to Invoices (tfcmg2106s000), even though it is showing in the open entries. This can happen when the document date of the unallocated payment lies before the document date of the purchase invoice you want to assign it to. There are 2 ways to handle this...

Read more

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.

Read more
First1415161719212223Last

Theme picker

Categories