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 Week: Alternative Materials in BOMs:

Kathy Barthelt 0 29473 Article rating: No rating

Often, multiple items are interchangeable even when these are purchased from various vendors. You can use any of these items as material in a bill of material (BOM). If a shortage of a standard material is expected to delay a production order, LN can automatically select one of the alternative materials. You can define up to nine alternative materials for any material in a BOM.

The use of alternative materials has the following advantages:

  • LN can handle material shortages for some items without user intervention.
  • The use of alternative items can reduce the average inventory level.

BPCS/LX Tip of the Week: Purchase Order “In Use” Reset Feature 8.3.5

Anthony Etzel 0 23077 Article rating: No rating

 

This new feature provides the ability to resolve or reset a purchase order or requisition that is no longer being processed, but the system still indicates it is ‘in use’. We all remember those situations where we could never figure out how the order got hung up.

What we previously had to do was run a behind the scenes script to reset the flag so the order was again accessible. This enhancement provides the ability to resolve the issue and resume processes quickly.

This option is now on the PUR menu, and the user can select the Purchase Order/Requisition in Use Maintenance, PUR940D. The user then enters an order or requisition to remove the “In Use” status.

 

Optimize Your Manufacturing Today!

Baan/LN Tip of the Week: Advantages / Disadvantages of Virtualization

Kathy Barthelt 0 37235 Article rating: 5.0

I know a lot of our customers are considering virtualization projects. I came across this, and thought it might be useful:

The advantages of virtualization include the following:

• You get more out of your existing resources. Pool common infrastructure resources and break the legacy “one application to one server” model with server consolidation.

• You can reduce datacenter costs by reducing your physical infrastructure and improving your server to admin ratio. Fewer servers and related IT hardware means reduced real estate and reduced power and cooling requirements. With better management tools, you can improve your server to admin ratio so personnel requirements are reduced.

• You can increase the availability of hardware and applications for improved business continuity.

• Securely back up and migrate entire virtual environments with no service interruptions. Eliminate planned downtime and recover immediately from unplanned issues.

 

• Gain operational flexibility. Respond to market changes with dynamic resource management, faster server provisioning, and improved application deployment.

The disadvantages of virtualization include the following:

• Virtualization adds overhead to the CPU, memory, IO, and network.

• Virtualization adds an additional layer to the hardware and software stack. Therefore, additional complexity is introduced in the following circumstances:

  • When sizing the physical server.
  • When planning VM capacity.
  • When planning multiple VMs on the same physical server.
  • When investigating performance issues.

 

RSS
First91929394969899100Last

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories