Integrating with Infor LN

Key Concepts

Infor LN is an advanced and easy-to-use ERP solution for manufacturers. By integrating Infor LN with PlanetTogether APS, users will be able to easily schedule and re-schedule their production based on up-to-date and accurate information found in their ERP system (LN).

The following document outlines the intended use cases and supported functionality between PlanetTogether and Infor LN via a SQL Database. 

Use Cases

1. Refresh Planning Data

  • The integration will allow users to update the planning data used by PlanetTogether by extracting data from LN. From here users will use the latest data from the ERP system to create optimized production schedules.
  • To do this, Exchange Schemas will extract the required information from various tables within LN and create a set of flat files. These files are then read by a SQL Server stored procedure which will insert the content of the files in the SQL Server Databases. This information can then be imported into PlanetTogether and used for scheduling.
  • The data that will be extracted from the LN ERP system includes:
    • Plants
    • Warehouses
    • Work Centers
    • Resources
    • Inventory
    • Items
    • Item Properties
    • Production Orders
    • Planned Orders
    • Routings
    • Bills-of-Material
    • Purchase Orders
    • Sales Orders
    • Forecasts

2. Update LN Planned and Firm Planned Orders

  • Information from PlanetTogether can also flow back to LN to update the status of Planned Orders. When the Scheduled Start Date, Scheduled End Date, or Order Quantity of a Planned/Firm Planned Order changes in PlanetTogether, the information is relayed back to LN to update the LN Planned Orders Quantity, Scheduled Start/End and set the order status as "Firm".
  • To do this, a flat file containing the required information is sent to the LN server which will read the file and update the following fields in the LN ERP:
    • Order Quantity
    • Scheduled Start Date
    • Scheduled End Date
    • Order Status (set to Firm)
  • File format for flat file: Order Number, Order Quantity, Start Date, End Date. 

3. Update LN Production Orders

  • Information from PlanetTogether can flow back to LN to update the status of Production Orders. When the Scheduled Start Date, Schedules End Dae, Due Date, or Order Quantity of a Production Order is changed in PlanetTogether, the information is relayed back to LN to update the LN Production Order Order's Quantity, Scheduled Start/End, and Production Order Requested Due Date.
  • To do this, a flat file containing the required information is sent to the LN server which will read the file and update the following fields in the LN ERP:
    • Order Quantity
    • Scheduled Start Date
    • Scheduled End Date
    • Requested Due Date
  • File format for flat file: Order Number, Order Quantity, Start Date, End Date, Due Date.

4. Change of Scheduled Resource

  • When a change of Scheduled Resource is planned in PlanetTogether, the LN Production Order table is updated. Note: This is not a change to the Standard Routing.
  • To do this a flat file is created from PlanetTogether and sent to the LN Server which will read and validate the records to update the "Scheduled Resource" field in the Production Order table.
  • File format for the flat file: Order Number, Scheduled Resource

5. Planned/Firm Planned Order Job Split

  • When a Planned or Firm Planned Order is split in PlanetTogether, the integration will update LN by:
    • 1) Reducing the original Planned Order Quantity (this order will also be set to "Firm").
    • 2) Create a new Firm Planned Order for the remaining quantity.
  • To do this, a flat file is created from PlanetTogether and sent to the LN Server which will read and validate the records to update the following fields:
    • Order Quantity
    • Scheduled Start Date
    • Scheduled End Date
    • Order Status (set to Firm)
  • A new Firm Planned Order is created with the same Start/End Dates for the remaining Order Quantity.
  • File format for the flat file: Order Number, Original Order Quantity, Start Date, End Date, New Order Number, New Order Quantity, New Scheduled Start Date, New Scheduled End Date.

6. Validation & Logging

  • With this integration, users will be notified of the result of the Import and Export from PlanetTogether and any data validation errors encountered.
  • After the information is processed in LN for updates, a report will be created showing the original record with that status. In case of success, the status will show "updated successfully". In the case of an error, the status will show the error along with the error message.
  • In addition, a log of the entire process will be created in a table in the SQL Server Database to provide a detailed Audit Trail of the integration. The table will include the integration Time and Date, Original Data Record, After Data Record, Transaction Type, Error (if any), and LN Error Message (if any). This log data will also be sent as an email to a specified user.
  • Report format for the flat file: Original Record, Updated Record, Status, Error Message Output (generated on the LN Default Report tool for reporting on the session).

Additional Information

  • All updates to LN will validate using standard (DAL - Data Access Layer) validations.
  • SQL Server stored procedures are used to call the LN web services and communicate with PlanetTogether.
  • Imports to PlanetTogether and Publishes to SQL Server can be initiated: 1) manually by users, 2) at a specified frequency, or 3) at scheduled days and times.
  • After every run of the scheduled integration program, the log information will be sent as an email to a specified user and logged into a table in the SQL Database.