Standard Integration for Partners

Standard Integration Process for Partners

Integration Tools and Prerequisites:
  • The following article explains the PlanetTogether mapping wizard and how to use it in order to pull data from SQL: Interface Wizard
  • Instructions on how to set up an integration can be found here: Configuring PlanetTogether
  • The following article outlines how to publish data from PlanetTogether: Publish Options
  • Key terms:
    • ERP - Enterprise resource planning software
    • Customization - A custom add-in developed for PlanetTogether  to meet a customers need that may not be addressed by standard functionality



  Define the steps needed in order for a Partner to successfully create a Standard Integration.


In order to help with a successful implementation project, we suggest the following:


A Development Environment 

  -  The machine will need this configuration: IT Reference Guide

  -  We'll need SQL, possibly Excel, possibly FTP

  -  Remote access

  -  Read Access to a data source for Import only integration

  -  Additional access to the ERP for Import and Write-back integration.


A Goal

  -  What is the scope?

     Scheduling, Planning,Capable To Promise, Analytics, Supply Chain Distribution

  -  Is the data available?


we have ways of filling data gaps

we can help with the data validation

portals to suggest enhancements





  ERP Partners

  1. Setup the Environment

 -- Accessible by both the Partner and PT

 -- follow our server recommendations.

 -- include SQL & Excel


  1. Access the Data

 -- SQL DB desired

 -- test data either scrubbed or NDA approved.

 -- ERP client access is optional depending on who does the Validation and who does the Write-Back to the ERP.

 -- Install PlanetTogether server and client on the server

 -- Connect to the Data

 -- techniques of data validation and data manipulation


  1. Discovery

 - project scope

 - pros and cons of doing it quickly vs doing it thoroughly

 - team needed

 - PM framework


  1. Mapping

 - Resource Objects

Plant, Dept, Resource, Capability, Assignments

 - Inventory Objects

Item, Warehouse, Inventory

Inv: a record must exist even if the QOH is zero. Some ERPs would delete a zero QOH Inv record.

Inv: we don't allow negative QOH. Some ERPs use this to emulate allocations

 - Job Objects

Job, MO, Op, RR, RC, Product


  1. Mapping Next Level

 - Resource:

Product Rules

Attribute Tables

 - Inventory:

Purchase Orders, Sales Orders, Forecasts, Transfer Orders

 - Jobs:

Activity, Materials, Attributes, Alt Paths, SuccessorMOs

Mat: need to sum Qty Required for each Item. Some ERPs may list the same item multiple times.

If the items can't be summed, they need to either be made unique (ItemID + <config>) 

or required at a different parallel step (op10a: add strand 1, op10b: add strand 2, etc..)


  1. Mapping 3rd-Level: MRP, CTP, Analytics, Grids & Layouts, BPs & GMPs


  1. You now have accurate forward looking information.

How do you view it..

How do you use it..

What can it give you that you didn't expect..

looking up and down the supply chain

Forecast buckets as an unexpected and unnecessary strain on your suppliers