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

George Moroses
/ Categories: ERP News, Event / News, IDF

IDF News: Multi-Language Support

IDF capabilities have been enhanced to provide support for many description elements to be displayed in the user’s language. MLS address and description information has been added to Vendor/Customer/Item business objects. Users can add/remove information as needed. Those display icons that do not have MLS fields on them may have MLS objects already created that can be used to add MLS field to those display icons.

Scope: The following multi language description fields are now available in IDF. To show them, select the multi-language field for the desired IDF panel.

• Item Description

• Warehouse Description

• Customer Name

• Vendor Name

• Vendor Accounting Type

• Company Name

• Currency Description

• Country Description

• General Ledger Account Description

• General Ledger Segment Value Description

 

Impact: These IDF programs are new or were updated to support multi language functionality:

• Account Segment Value MLS Extension

• Bank Branch MLS Override

• Bank MLS Override

• Company MLS Override

• Country Extension MLS Override

• Country MLS Override

• Currency Extension MLS Override

• Currency MLS Override

• Customer MLS Address Override

• Customer MLS Note

• Customer Order Class MLS Override

• Customer Terms MLS Override

• Enterprise Item MLS Note

• Enterprise Item MLS Override

• Freight Term MLS Extension

• Note MLS Line

• Sales Representative MLS Address Override

• Vendor MLS Address Override

• Vendor MLS Note

• Warehouse MLS Address

Previous Article What problem is OTTO addressing?
Next Article Partner News: Are you up to date on all of the sales tax changes that have gone into effect this year?
Print
18721 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses

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.

12345678910Last

Theme picker

Tips: LN | Baan

If you do not wish to define a detailed mapping to various ledger accounts for specific integration transactions, you can map the corresponding integration document type to a default account. All the transactions of the integration document type for which an account cannot be determined based on the mapping scheme details, are posted to the default account.

 

The mapping of an integration document type to a default account is direct, without the need for element groups and mapping elements. No distinction is made on any of the transaction details.

 

Default accounts can be used in two ways:

  • Instead of a detailed mapping to various ledger accounts. All the transactions are posted to the same account. For example, all warehouse receipts are posted to the Inventory ledger account, without any distinction.
  • In addition to a detailed mapping. If a transaction cannot be mapped based on the detailed mapping scheme, it is posted to the default account.

A cluster is a group of one or more warehouses in a particular geographical area. You can plan an item by cluster (geographical area).

To enable this, you can set up multiple plan items for one item. You always define one plan item without a cluster indication and multiple plan items with a cluster indication. A plan item with a cluster is called a clustered plan item, and a plan item without cluster is called the non-clustered plan item.

The plan items in the clusters can be supplied not only by distribution, but also through purchase and production. In this way, you can, for example, plan local purchasing in a cluster (geographical area). You can also plan supply from multiple sources.

 

Optimize Your Manufacturing Today!

First9899100101103105106107Last

Theme picker

Categories