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

Kathy Barthelt
/ Categories: Infor

Infor News You Can Use: Discover the Power of Advanced Planning & Scheduling with industry expert Greg Keating

CloudSuite® Industrial APS - Effective Planning & Scheduling

Learn what it is, how it works, and how it can transform your manufacturing operations.

Logo

Presented by

Greg Keating, Senior Solution Consultant, Infor

About this talk

Bring the future into closer focus If you are like most manufacturers today, managing your planning and scheduling resources has become a major challenge. The disrupted supply chain, workforce availability, equipment capacity, sporadic market demand, and changing customer expectations all contribute to the complexities of planning. Having the right resources available is essential for keeping production flowing and ensuring customers receive orders on time. In this session we will focus on Advanced Planning and Scheduling (APS) capabilities within CloudSuite Industrial. Our Infor expert will share: - What APS is, how it varies from traditional Manufacturing Resource Planning and the difference between Planning and Scheduling within CSI. - The basic configuration requirements needed to effectively utilize APS and available-to-promise/capable-to-promise (ATP/CTP) functionality. We'll also look at the key differences between these solutions - Examples of advanced applications that help identify accurate and reliable commitment dates.

Watch now On-Demand >

Infor On-Demand: 67min talk

Previous Article Bring New Life to Your Infor LN & Baan ERP System
Next Article Infor LN & Baan Tips & Tricks for EXECUTIVES:
Print
2217 Rate this article:
5.0
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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

In Baan IV, users define series and numbers in the Maintain First Free Numbers (tcmcs0147m000) session. In the Type of Number field, users must select the type of documents for which the series will be used. The generated document numbers are always numeric and can consist of up to six characters.

 

In LN, users must define number groups in the Number Groups (tcmcs0151m000) session and then in the First Free Numbers (tcmcs0150m000) session, define the series and numbers of each number group. Users assign the number groups to various purposes in the corresponding sessions. For example, in the Sales Order Parameters (tdsls0100s400) session, users can select the number group for sales orders and sales schedules. In the Sales Offices (tdsls0512m000) session, users can then select a series of that number group for the sales orders generated by a specific sales office. As the series codes can be alphanumeric, the generated document numbers can be alphanumeric and they can consist of up to nine characters.

The Infor LN database must be created with the appropriate size. For example, if at least 150 GB is required for a year, create the database with the required size from the beginning. Do not let the size increase to the required size and cause additional fragmentation in the database and the NTFS volume.  Set the autogrowth to a minimum of 10 percent or 1 GB (for each extent) to avoid fragmentation on file system level. Never use the default extent size of 1 MB.
First139140141142144146147148Last

Theme picker

Categories