Introduction

A powerful ERP solution from Microsoft Dynamics 365 (F&O) is simple, easy to use, and quick to prove ROI after implementation. Core ERP capabilities include financial management, human capital management, business intelligence, production, supply chain management, procurement and sourcing, project management and accounting, sales and marketing, and service management.


The Goal of this connector is to integrate Tulip with Microsoft Dynamics (F&O) using HTTP Connectors & provide our customers with an out-of-box connector that can be imported into their instance & perform a complete set of end to end operations.

Purpose

We are going to highlight different connector functions that can be built by doing HTTP calls to Microsoft Dynamics API to interact with the data & perform basic CRUD operations on Dynamics. The connector functions used for the connector let you pull a list of Batch Orders, Update Batch Orders, Update route operations & filter the list of operations by Status.

API Doc

Microsoft Graph API Documentation

Pre-Requisites

  1. Configuring the OAuth 2.0 credentials in Azure Active Directory.

2. Register API with the required scopes in the Azure Active Directory Portal

Tulip Connection Details

The following information would need to be configured on Tulip’s

Connectors.

  1. Running On: Cloud Connector Host

  2. Host: <your_dynamic_instance_host>.cloudax.dynamics.com

  3. Port:443

  4. TLS: Yes

OAuth 2: Authentication will be carried forward to all

the Connector Functions

Connector Functions

Get a list of all Batch Orders

Purpose

This connector gets a list of all available Batch Orders in Dynamics.

Endpoint

HTTP GET call to the endpoint: https://<host_url>:443/data/BatchOrderHeaders

Required Input

  1. Legal Entity ID (Query Parameter passed as an OData filter)

Output Extractor

There are various fields that are returned by Dynamics, based on each use case you can parse multiple fields. Naming a few that are being parsed into the connector:

  1. Batch Order Number

  2. Scheduled Quantity

  3. Item Number

  4. ScheduledStartDate

  5. ProductName

  6. WorkOrderStatus

  7. Inventory Lot ID

Get a list of all Batch Orders by status

Purpose

This connector gets a list of all available Batch Orders in Dynamics by specifying a specific status.

Endpoint

HTTP GET call to the endpoint: https://<host_url>:443/data/BatchOrderHeaders

Required Input

  1. Legal Entity ID (Query Parameter passed as an OData filter)

  2. Batch Order Status (Query Parameter passed as an OData filter)

Output Extractor

There are various fields that are returned by Dynamics, based on each use case you can parse multiple fields. Naming a few that are being parsed into the connector:

  1. Batch Order Number

  2. Scheduled Quantity

  3. Item Number

  4. ScheduledStartDate

  5. ProductName

  6. WorkOrderStatus

  7. Inventory Lot ID

Get specific batch order details

Purpose

This connector gets a list of specific Batch Orders in Dynamics by specifying batch order number.

Endpoint

HTTP GET call to the endpoint: https://<host_url>:443/data/BatchOrderHeaders

Required Input

  1. Legal Entity ID (Query Parameter passed as an OData filter)

  2. Batch Order Number (Query Parameter passed as an OData filter)

Output Extractor

There are various fields that are returned by Dynamics, based on each use case you can parse multiple fields. Naming a few that are being parsed into the connector:

  1. Batch Order Number

  2. Scheduled Quantity

  3. Item Number

  4. ScheduledStartDate

  5. ProductName

  6. WorkOrderStatus

  7. Inventory Lot ID

Update batch order status

Purpose

This connector updates the status of a pulled batch order.

Endpoint

HTTP POST call to the endpoint: https://<host_url>:443/data/TPProdTableStatusUpdates

Required Input

  1. Legal Entity ID (Query Parameter passed as an OData filter)

  2. Batch Order Number (Query Parameter passed as an OData filter)

  3. Production Status (Request Body)

Get batch order formula/BOM

Purpose

This connector gets a list of BOM or a formula for a batch order.

Endpoint

HTTP GET call to the endpoint: https://<host_url>:443/data/BatchOrderFormulaLines

Required Input

  1. Legal Entity ID (Query Parameter passed as an OData filter)

  2. Batch Order Number (Query Parameter passed as an OData filter)

Output

There are various fields that are returned by Dynamics, based on each use case you can parse multiple fields. Naming a few that are being parsed into the connector:

  1. Material Number

  2. Material Name

  3. Inventory Lot ID

  4. UOM

  5. Route Operation Number

  6. Line Number

Gets a list of operations for a batch order

Purpose

This connector gets a list of all operations that batch order needs to be processed across.

Endpoint

HTTP GET call to the endpoint - https://<host_url>:443/data/TBProductionOrderRouteOperations

Required Input

The following are the parameters that are sent as the Request Body

  1. Legal Entity ID (Query Parameter passed as an OData filter)

  2. Batch Order Number (Query Parameter passed as an OData filter)

Output

There are various fields that are returned by Dynamics, based on each use case you can parse multiple fields. Naming a few that are being parsed into the connector:

  1. Operation Number

  2. Operation Priority

  3. Next Operation Number

  4. Operation Name

Did this answer your question?