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

George MorosesGeorge Moroses

Other posts by George Moroses

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Item Facility Master has a new attribute to define the override inspection days lead time CICP.ICINSD.

  • When an item facility has a defined override inspection days lead time, that value will be used instead of the system parameter inspection days lead time.

MRP exception report, MRP200B
Purchase planning report, PUR285B
Purchase order / Requisition maintenance, PUR500D3
Purchase order consolidation / release, PUR640B1
Vendor splits, PUR653B

This enhancement improved the subfile utilized in MRP320D Master Schedule Detail Inquiry -SCR001 by expanding the subfile with data rather than clearing the subfile as user pages. This change provides full support for the WebTop 4.8 Grid decorator.

This enhancement updated the approach used to populate the subfile to allow a deployed Webtop Grid to function correctly. There is no visible or user-impacted change to the way the program functions.

This enhancement provides improved functionality and full support of a Webtop grid applied to the subfile.

Last

Tips: LN | Baan

Users can personalize sessions and apply special formatting to the data displayed in sessions. The personalizations and formatting settings that are specified by the users are stored on the LN server. Administrators can maintain these settings.

  • Session personalizations

    Users can personalize sessions in various ways. users can, for example, hide fields, change labels, customize the toolbar, and move fields to another tab. Administrators can maintain the personalizations defined by the users. For example, an administrator can export personalizations to an XML file, import personalizations from an XML file, and copy personalizations to another user, to a DEM role, or to a company number.

  • Report personalizations

    You can use the Report Designer (ttstppersrep) to personalize the layouts and style of reports, without modifying the standard reports or using an external reporting solution. The changes are stored as personalizations.

    You can also generate new reports that are based on a selection of fields from the application data model. These reports are generated in the extensibility package. You can personalize these reports in the Report Designer (ttstppersrep), or modify them in Infor LN Studio.

    For details, see the Infor LN Report Designer Development Guide
     
  • Conditional formatting

    users can define conditions to apply special formatting to the data displayed in LN sessions. The users can define multiple conditions per session and different types of formatting, such as a specific color for particular fields or rows, and a warning symbol for particular rows. Administrators can maintain the formatting settings specified by the users and can define system-wide formatting settings.

  • If Finances is implemented, we recommend that you do not delete order data in a fiscal year that has not yet been fully closed. This is because the GRINYA process uses information that would be deleted by this action. For best results, check whether the logistical balance for non-invoiced receipts matches the balance of the GRINYA accounts for the periods up to which you want to delete purchase order data.
  • When a purchase order is canceled, you can only delete the purchase order and the related tables. If only a purchase order line is canceled, the line can be deleted and archived.

You cannot delete a purchase order (line) if:

  • The linked warehouse order is closed but cannot be removed.
  • The purchase order is linked to a PCS project that is not yet archived. When the PCS project is archived, the purchase data is also archived and you can delete the purchase order.
  • A consignment replenishment order is not yet consumed completely.
  • The invoice is yet to be completely matched and approved.
  • The invoice amount is not yet inserted as turnover history.
  • The sales order or service order that is linked to the purchase order line, and for which an internal invoice must be sent from the purchase office to the sales office or service office, is not yet invoiced. In this case, you cannot delete the purchase order line before the sales order or service order is invoiced.

Categories