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

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
18520 Rate this article:
5.0
George Moroses

George MorosesGeorge Moroses

Other posts by George Moroses
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

One common GRINYA issue would be incorrectly entered Integration Setups.

Check the Baan/LN manual for recommended Integration setups. If such a mistake were to occur, it is important to know for what period of time the Integration was in error. It is recommended that the Integrations Setup tables be audited either through Baan or Database Auditing. Corrections can be quickly calculated when an exact timeframe can be determined.
Read more

In LN, you can differentiate between items at various suppliers:

  • Locations (warehouses),
  • Purpose (planning, purchase)
  • Origin (supplier, warehouse)

Example

An item is supplied by two different suppliers. Supplier A ships in lots of 100 pieces due to how the item is packed. Supplier B ships the goods in units of 60 pieces.

You can define specific parameters for each supplier. The following sessions can be used to define these characteristics:
 
  • Items - Planning (cprpd1100m000)
  • Check Item Data by Warehouse (whwmd2210m000)
  • Item Supplier Plan (cpvmi0530m000)
These sessions define entities that have an n-to-1 relationship with the general item data.

 

Read more
First151152153154156158159160Last

Theme picker

Categories