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: Support, Training & Workshops

We're excited to unveil our revamped BPCS/LX Technical Staff Augmentation Services

We're excited to share some updates about our BPCS/LX Technical Staff Augmentation Services. At Crossroads, we're refining our staff augmentation structures to better cater to specific job descriptions. This enhanced offering is designed to provide our clients with the opportunity to seamlessly maintain product-level support (BPCS/LX – RPG) and development assistance. What sets this program apart is its ability to offer significant cost savings compared to traditional time and material arrangements. We aim to make staff augmentation more accessible and customizable to meet varying budgetary needs.

As part of this agreement, Crossroads will allocate a dedicated BPCS/LX technical resource for a set number of hours per week. The exact hours will be mutually agreed upon during the sourcing requirements discussions, ensuring that the support arrangement aligns perfectly with your needs.

Key Features of the Technical Staff Augmentation Service:

  • Flexible Hours: Tailored to your specific needs, we'll collaborate with you to determine a fixed number of hours per week that best aligns with your requirements.

  • Duration Options: Choose from flexible prepaid agreement durations of 3, 6, 9, or 12 months.

  • Remote Accessibility: Our technical services are primarily remote, but onsite assistance can also be discussed and arranged during the project kickoff phase, ensuring comprehensive support regardless of location.

  • Expertise Spectrum: Our dedicated BPCS/LX technical resources boast a comprehensive skill set, including proficiency in RPG, thorough documentation practices, design capabilities, familiarity with IBMi system foundations, job scheduling expertise, SQL proficiency, CL development capabilities, and more.

  • Scope Clarification: While our agreement primarily focuses on technical support and development assistance, application support falls outside the defined scope and can be considered separately upon request.

This innovative approach to technical staff augmentation is designed to streamline your operations, enhance system reliability, and empower your team to maximize the full potential of your BPCS/LX environment. Let's embark on this journey together, customizing technical staff augmentation solutions that precisely align with your business objectives and budgetary constraints.

Request a phone consultation or Learn More

Previous Article Introducing VJES (Visual Job Execution Software)
Next Article Unlocking the Full Potential of Your LX/BPCS Investment - Embrace the Cloud for Enhanced Connectivity
Print
6172 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

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.
Read more

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!

Read more
First9899100101103105106107Last

Theme picker

Categories