Intercompany Work Orders

Create and work on work orders across companies

Introduction

In standard Asset management, work orders created in a company can be worked on and completed in the same company.

We've added a functionality that allows you to create work orders in one company and carry out the maintenance work and complete the work order in another company. This is done by using the procurement functionality in D365FO.

Example: In company A (source company), a maintenance request exists, and a work order has been created from that request. The maintenance work will be performed by workers in company B (target company). Intercompany work order functionality handles the automatic creation of a related work order in company B, based on the 'original' work order in company A.

Audience
Maintenance Manager

License Configuration

This setup is required in the source company and the target company.

The Intercompany work orders functionality in Asset management requires specific setup regarding license configuration.

  1. Select System administration > Setup > License configuration.
  2. Select Advanced Asset Management.
  3. Ensure that the Intercompany Work Orders check box is selected.

Security Configuration

This setup is required in the source company and the target company.

Data entities for Intercompany work orders have been extended in the D365FO Data management framework.

In D365FO, the Maintenance manager role must include the following setup.

  1. Select System administration > Security > Security configuration.
  2. Select role: Maintenance manager.
  3. Select duty: Maintain Asset management Intercompany work order entities.
  4. The privileges Maintain Asset management Intercompany assets entity and Maintain Asset management Intercompany work orders setup entity must be added.

Refer to Microsoft documentation to learn more about security configuration in D365FO: Security architecture.

Source Company Setup

Before you can start using intercompany work orders, specific setup is required in the source company as well as the target company.

In the source company - where you create the work order to be used as basis for an intercompany work order in the target company - required setup includes

  • Work order type
  • Work order lifecycle state
  • Procurement type setup on an item forecast line in maintenance job type default

If required, you can set up several companies (legal entities) as source companies to automatically create related work orders in the same target company.

Work Order Type

Create a work order type to be used on the work order that you want to create an intercompany work order from.

  1. Refer to Microsoft documentation for information on how to create a work order type.
  2. On the work order type, select a Vendor (for which procurement will be created).
  3. On the work order type, select a Vendor company (the target company for intercompany work orders).

Work order type for intercompany work orders
Work order type for intercompany work orders

Work Order Lifecycle State

Create a work order lifecycle state to specify at which lifecycle state an intercompany work order will be created.

  1. Select Asset management > Setup > Work orders > Lifecycle states.
  2. Select New.
  3. Enter an ID in the Lifecycle state field.
  4. Enter a name in the Name field.
  5. On the General FastTab
    1. In the Work order section, activate the Active toggle button.
    2. In the Project section, select "In process" in the Stage drop-down.
    3. In the Intercompany work orders section, activate the Create intercompany work orders toggle button.

Note

When you've created the lifecycle state, as described above, go to Lifecycle models and add the lifecycle state to the Lifecycle states selected section on your standard lifecycle model. Remember to also go to Lifecycle state updates on the lifecycle model to include update to the new lifecycle state, for example, in the first lifecycle state used in your company setup. Refer to Microsoft documentation for more information on Lifecycle models in Asset management.

The screen below shows an example of the lifecycle state setup.

Work order lifecycle state for creating intercompany work orders
Work order lifecycle state for creating intercompany work orders

Procurement Setup on Item Forecast Line

Intercompany work orders use procurement functionality in D365FO to create a procurement setup for item forecasts on maintenance job type defaults. In this setup, the target company (where related work orders will automatically be created) is treated as a contractor that receives work orders.

This setup means that a work order (created in the source company) with a maintenance job type, which includes a maintenance job type default setup with an "Intercompany" procurement type on an item forecast line, automatically generates a related work order in the target company.

The following setup is required on maintenance job types in the source company:

  1. Create a maintenance job type for the target company. If you have several companies in your organization, which should work with related work orders, create a maintenance job type for each company.
    1. Refer to standard Microsoft documentation for Asset management: Create a maintenance job type
  2. On the maintenance job type described in step 1, create a maintenance job type default line dedicated to procurement setup.
    1. For the maintenance job type default line, create an item forecast forecast line on which you select "Intercompany" in the Procurement type field.
    2. Refer to standard Microsoft documentation for Asset management: Create maintenance job type default lines and related forecasts

The three screenshots below show an example of a procurement setup on a maintenance job type.

Maintenance job type on the source company - for the target company (USSI) to receive related work orders
Maintenance job type on the source company - for the target company (USSI) to receive related work orders
Maintenance job type default line on the maintenance job type - used for item forecast setup
Maintenance job type default line on the maintenance job type - used for item forecast setup
Item forecast setup on the maintenance job type default line
Item forecast setup on the maintenance job type default line

Target Company Setup

When you've completed setup in the source company, next step is to set up intercompany functionality in the target company (where related work orders will be automatically created based on work orders in the source company). Here, you define which setup from the source company should be changed to a similar value in the target company when you create intercompany work orders.

Five options for mapping values (value types) are available:

  • Work order type
  • Service level
  • Maintenance job type
  • Maintenance job type variant
  • Trade

In the screenshot below > Setup FastTab > Value type field, you see a setup with all options used for mapping values.

In the screenshot below > Intercompany assets FastTab, assets From legal entity (source company) with asset type "Air Compressor" are mapped to assets in the current legal entity (target company).

  1. In D365FO, change company to the target company.
  2. Select Asset management > Setup > Work orders > Intercompany work orders.
  3. On the Setup FastTab, add the lines required to reflect different values used in the source company (From legal entity) and in the current legal entity.
    1. We recommend that you create at least one setup line for each value type, to prevent errors when you create intercompany work orders.
    2. Depending on your setup in the source company and target company, multiple lines for the same value type may be required.
  4. On the Intercompany assets FastTab, add one or more lines to map assets in the source company (From legal entity) to the assets in the current legal entity.
    1. The number of selections available in the From legal entity drop-down (source companies) depends on the number of companies for which you've created intercompany work order setup.
    2. Depending on how you want to divide assets from the source company into asset 'categories' in the target company, multiple lines for mapping assets from the same source company may be required. Assets can be mapped one-to-one (which would require many lines), or you can create assets in the target company for the purpose of grouping intercompany assets. Example: "Asset - laptop Dell", "Asset - laptop Lenovo", "Asset - printer", and "Asset - keyboard" if you maintain office equipment.
    3. The number of assets included in a setup line depends on how specific your setup is. Making selections in the From asset type, From manufacturer, From model, From asset fields on a line makes your setup more specific, meaning you decrease the number of assets included in that setup line.

Example of intercompany work orders setup in target company
Example of intercompany work orders setup in target company

Create an Intercompany Work Order

When a work order with intercompany setup is created in the source company and updated to the lifecycle state you have set up for intercompany work orders, then:

  • Intercompany procurement is created in the source company.
  • A similar work order is created in the target company, based on the setup.

Refer to the test case below for a step-by-step procedure on how to create an intercompany work order.

Refer to Microsoft documentation regarding how to create work orders in Asset management:

When an intercompany work order is created, and if a field defined as a Value type field in the target company setup (Work order type, Service level, Maintenance job type, Maintenance job type variant, Trade) is blank on a work order job line, it means that no setup matches that field.

When an intercompany work order is created, and if a field defined as a Value type field is mandatory on a work order job line, but that field (for example maintenance job type) has no mapping and is left blank, then an error message is shown on the work order.

When work order lines are created for an intercompany work order, any attachments from the original work order lines are applied automatically to the intercompany work order lines.

Update Customer Requisition on Project Contract

When a purchase order is created during the creation of an intercompany work order, the purchase identifier will be stored in the customer requisition field on the project contract. The project contract should be created automatically with project related to the maintenance job. If it's not created automatically, it might be because the project type you're using is not suitable for intercompany work orders.

You can see the field 'Customer requisition' in the 'General' tab in the 'Projects' page. See screenshot 01.

You will see a warning notification if there is a related project group setup which isn't suitable for the project contract.

01.
01.

Creating an Intercompany Work Order

Data Requirements

  1. A Work order type for intercompany exists in the source company.
  2. A work order lifecycle state for creating intercompany work orders exists in the source company.
  3. Procurement setup in Asset Management > Jobs > Maintenance job type defaults > Forecasts in source company exists in the source company.
  4. Parameter setup in Asset Management > Setup > Work Orders > Intercompany Work Orders exists in the target company.

Steps 2

  1. In the source company, create a work order with the relevant 'intercompany' work order type.

  2. Update the work order lifecycle state to the lifecycle state used for intercompany work orders.

Expected

Information about creation of an intercompany work order is displayed in 'Message details' in the source company.

A purchase order is created for each work order job in the source company.

If there is no hour forecast line on the work order, or if multiple hour forecast lines are created for the same work order job, a warning is displayed.

A work order is created in the target company, according to intercompany setup.

The work order in the target company contains the same number of jobs as the source work order.

Copyright Dynaway A/S

Privacy Policy