Use cases

Case

  • Case use cases sends BOM details to D365 FO on release of an Engineering Item at 3DX side. However, Case use cases works with/without change action. The in built use cases are mentioned in the below table.

Use case Event Category Event Processor Description

1. CreateProduct

Engineering Item

Created

CreateProduct

Generates the payload from the received newly created object ID of an Engineering item and sends the Engineering item details to D365 FO. For more information about payload structure please check Payload for create product use case.

2. Update Product

Engineering Item

Status Changed (RELEASED)

UpdateProduct

Generates the payload from the received released Engineering item object ID and sends the updated attributes details to D365 FO. For more information about payload structure please check Payload to update product attributes use case.

3. SendBOM

Engineering Item

Status Changed (RELEASED)

SendBOM

Generates the payload from the received released Engineering item object ID and sends the BOM details to D365 FO. For more information about payload structure please check Payload for send BOM use case.

4. ReleasedDocuments

Engineering Item

Status Changed (RELEASED)

ReleasedDocuments

Generates the payload from the received released Engineering item object ID and sends the document details attached to the engineering item to D365 FO. For more information about payload structure please check Payload for release documents use case.

5. ReviseProduct

Engineering Item

Versioned

ReviseProduct

Generates the payload from the received revised Engineering item object ID and Sends the version information of an engineering item to D365 FO. For more information about payload structure please check Payload for revise product use case.

6. CreateChange

Change Action

Created

CreateChange

Generates the payload from the received newly created change action object ID and sends the details of the Change Action to D365 FO. For more information about payload structure please check Payload for create change use case.

7. CreateChangeAssociation

Change Action

Status Changed (Complete)

CreateChangeAssociation

Generates the payload from the received released change action object ID and sends the details of the Change Action along with the associated BOM information to D365 FO. For more information about payload structure please check Payload for create ChangeAssociation use case.

8. Create Manufacturing Item

Manufacturing Item

Created

CreateManufacturingItem

Generates the payload from the received newly created object ID of a Manufacturing item and sends the Manufacturing item details to D365 FO. For more information about payload structure please check Payload to create MBOM use case.

9. Update MBOM

Manufacturing Item

Status Changed (RELEASED)

UpdateMBOM

Generates the payload from the received released Manufacturing item object ID and sends the updated attributes details to D365 FO. For more information about payload structure please check Payload to update MBOM attributes use case.

10. Send MBOM

Manufacturing Item

Status Changed (RELEASED)

SendMBOM

Generates the payload from the received released Manufacturing item object ID and sends the MBOM details to D365 FO. For more information about payload structure please check Payload for send MBOM use case.

  • Following is the list of processors which are available out of the box to send the information to D365 FO.

Processors Description

1. CreateProduct

Uses the Engineering item id to construct the payload for the Engineering item. This use-case uses 5 processors to send the information to the D365 FO. Following are the processors which will be executed in sequence.

Processors Description

ProductsV2

Create the number for global entity.

ReleasedProductsV2

Create entity for locale company.

ProductMasterStyles

Create entity for revision.

ReleasedProductVariantsV2

Create entity for variant management.

BillOfMaterialsHeadersV2

BOM Lines associated with BOM Header.

2. UpdateProduct

Uses the Engineering item id to construct the payload to update the attributes of an Engineering item. This use-case uses 2 processors to send the updated attribute information to the D365 FO. Following are the processors which will be executed in sequence.

Processors Description

UpdateProductsV2

Updates the Product Name and Product Description of existing entity.

UpdateReleasedProductsV2

Updates the Attributes of existing entity like (NetProductWeight, PurchaseUnitSymbol, InventoryUnitSymbol, SalesUnitSymbol).

3. CreateChange

Uses the Change Action id to construct the payload for the Change Action.

4. CreateChangeAssociation

Uses the Change Action id to construct the payload for the Change Action associated with the Engineering item.

5. SendBOM

Uses the engineering item id to construct the payload containing the BOM details.

6. ReleasedDocuments

Uses the engineering item id to construct the payload containing the document (specification) details associated with engineering item.

7. ReviseProduct

Uses the Engineering item id to construct the payload for the Engineering item. This use-case uses 3 processors to send the revised information to the D365 FO. Following are the processors which will be executed in sequence.

Processors

Description

ProductMasterStyles

Creates revise entity for revision.

ReleasedProductVariantsV2

Create revise entity for variant management.

BillOfMaterialsHeadersV2

Revise BOM Lines associated with revise BOM Header.

8. CreateManufacturingItem

Uses the Manufacturing item id to construct the payload for the Manufacturing item. This use-case uses 5 processors to send the information to the D365 FO. Following are the processors which will be executed in sequence.

Processors Description

MBOMProductsV2

Creates the number for global entity.

MBOMReleasedProductsV2

Creates entity for locale company.

MBOMProductMasterStyles

Creates entity for revision.

MBOMReleasedProductVariantsV2

Creates entity for variant management.

MBOMBillOfMaterialsHeadersV2

MBOM Lines associated with MBOM Header.

9. UpdateMBOM

Uses the manufacturing item id to construct the payload to update the attributes of a manufacturing item. This use-case uses 2 processors to send the updated attribute information to the D365 FO. Following are the processors which will be executed in sequence.

Processors Description

UpdateMBOMProductsV2

Updates the Product Name and Product Description of existing entity.

UpdateMBOMReleasedProductsV2

Updates the Attributes of existing entity like (NetProductWeight, PurchaseUnitSymbol, InventoryUnitSymbol, SalesUnitSymbol, UnitCost, PurchasePrice, SalesPrice).

10. SendMBOM

Uses the manufacturing item id to construct the payload containing the MBOM details.
Use cases like CreateProduct, UpdateProduct, ReviseProduct, CreateManufacturingItem, UpdateMBOM uses multiple processors internally to send the information to D365 FO in sequential manner. Once all the processor are successfully executed then the use case is completed otherwise status will be partially completed. Output file is also generated tx-log.json which holds the information of the executed processor. So when user resends the job it will start executing the processor which is failed or not yet executed.

ECM

  • Engineering Change Management (ECM) use cases sends the BOM details on completion of Change Action at 3DX side. The in built use cases are mentioned in the below table.

Use case Event Category Event Processor Description

1. CreateCA

Change Action

Created

CreateChangeOrder

Generates the payload from the received newly created object ID of a change action and sends the change action details to D365 FO. For more information about payload structure please check Payload for create change action use case.

2. CreateECMBOM

Change Action

Status Changed (Complete)

CreateECMBOM

Generates the payload from the received complete change action object ID and sends the information of BOM Head, change action and product mapping, product and BOM line details to D365 FO. For more information about payload structure please check Payload to create product/ product and CA mapping/ BOM head/ BOM Line use case.

  • Following is the list of processors which are available out of the box to send the information to D365 FO.

Processors Description

1. CreateChangeOrder

Uses the Change Action id to construct the payload to send details of the change action to D365 FO.

2. CreateECMBOM

Uses the change action id to construct the payload for BOM Head, change action and product mapping, product and BOM line. This use-case uses 4 processors to send the information to the D365 FO. Following are the processors which will be executed in sequence.

Processors Description

ReleasedEngineeringProductCreation

Sends the information of released engineering item.

EngineeringChangeOrderProductsV3

Sends the information of mapping between released engineering item and change action.

CreateBOMHeader

Sends the information of BOM Head.

CreateBOMLines

Sends the information of BOM Lines.

ChangeOrderStatus-Approve

Sends the approval information of BOM Lines.

ChangeOrderStatus-Process

Sends the process information of BOM Lines.
Use case CreateECMBOM uses multiple processors internally to send the information to D365 FO in sequential manner. Once all the processor are successfully executed then the use case is completed otherwise status will be partially completed. Output file is also generated tx-log.json which holds the information of the executed processor. So when user resends the job it will start executing the processor which is failed or not yet executed.

While using ECM use case Number Sequence configuration should be automatic in D365 FO.

  • Select Inventory Management Module

  • Select Setup → Inventory and warehouse management parameters.

  • Select Number Sequences.

  • Open number sequence for BOM.

  • In General → SETUP section uncheck the Manual.

While using ECM use case need to create template to support UOM in D365 FO.

1. Select Engineering change management from modules.
2. Then select Released product details.
3. Create New and fill hte mandatory details and click OK.
4. Select Engineering change management → Product release policies
5. Create new policy which refers the release product which is created in step 2 & 3.
6. Select Engineering change management → Product category details.
7. Create new product category and map it with the policy which is created in step 4 & 5.
8. Use this new created Product category details in the payload while creating the product.