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

BPCS/LX Tip of the Week: Notes Maintenance Enhancements

Anthony Etzel 0 25346 Article rating: No rating

The Notes Maintenance feature is made up note programs that are accessible from a central location. The Note Text Maintenance (SYS555), Note Type Maintenance (SYS553) and Multi Language Notes Maintenance (SYS556) programs are all available as menu options.

Instead of having to go into separate programs to maintain note settings, the user can set up print options, specify user documents and customize user security levels for specific notes.

The Notes Maintenance feature provides a way to create, revise, delete, and copy note text that are categorized by note types. The print options in Notes Maintenance permit a user to define documents for which the note is intended. This includes base LX documents and custom documents. 

Finally, the notes program provides a way to define notes by assigning document types. For example, a document type can be created named “Invoice.” A note can then be defined to print on all invoice programs without requiring individual entry.

Optimize Your Manufacturing Today!

Baan/LN Tip of the Week: Letter of Credit

Kathy Barthelt 0 40703 Article rating: No rating

In LN 10.6 you can now link Sales Order (lines), Purchase Order (lines) and Contract (lines) to a Letter of Credit and process the same in accordance with the conditions stated in the linked Letter of Credit.

In addition, LN can be setup in a way that enables employees, with sufficient authorization, to approve the different types of Letters of Credit and change its status.

Optimize Your Manufacturing Today!

BPCS/LX Tip of the Week: IDF - Enterprise Items Application

Anthony Etzel 0 25446 Article rating: No rating

The Enterprise Item application in the Infor Development Framework for Infor LX supports display of all information relevant to an item. This includes numerous aspects of Inventory, including facility, warehouse, location, lot, and container data.

With the Enterprise Items application, you can customize the data displayed to include more or less data than is currently displayed using the standard Infor LX programs. You can access this information through a single point of entry, so there is no need to switch from one program to another to see all the data you require. This ability to customize will help streamline your decisions by allowing you to display information that is specific to your needs.

The various Enterprise Item application cards provide listings, maintenance type information, and current information that you could previously only access by running multiple standard Infor LX programs, such as Material Status Inquiry (INV300), Bill of Material Inquiry (BOM300), and Routing Inquiry (SFC100).

Optimize Your Manufacturing Today!

RSS
First6768697072747576Last

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

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Theme picker

Contact author

x

Categories