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

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
7383 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

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

12345678910Last

Theme picker

Tips: LN | Baan

Baan/LN Tip: New Mapping Scheme

After a new mapping scheme is copied from an existing one, it is possible to check transactions in a simulation mode, before activating the new scheme. However, before the simulation can take place, the new mapping scheme needs to have completed the “Check Mapping Scheme” step. When the check is completed, a transaction can be simulated by highlighting it and from the Specific menu, selecting “Map with Specific Mapping Scheme.” Any errors can be corrected without having to activate the new mapping scheme.

This has come up as an issue during various stages of warehouse material movements – transfers, outbounds, shipments. We have seen it right up to 10.4. The inventory structure table (whinr150) becomes a problem. The error points to that table, but users are lost as to how to fix it.

In the session Units by Unit Set many companies let the field Storage default to Yes. If the UOM is not intended to be used in inventory then that setting should be No. 

If an item is purchased in UOM different from the inventory unit and the setting is Yes then LN adds a record in that UOM to the inventory structure table. It is that record that causes problem later.

The session has an option to change the value of the storage field. Specific > Convert Use for Storage. This option works both ways and will correct all inventory in the UOM range. 

Should a user receive an error that references inventory structure table then the solution is to check that session to see if an odd UOM exists in it. If so use the Convert Use for Storage to correct the problem.

First7374757678808182Last

Theme picker

Categories