Introduction

When we think of Engineering Design-driven business decisions being used to control a “Make/Buy” type of scenario, we have two different approaches to achieve this.

1. We can use some attributes on EBOM which will be responsible for Make/Buy decision at the time of MBOM structure creation.
2. Using "Manufacturing Responsibility” paradigm in XEN where the MBOM “placeholder” (single) objects are created up-front BEFORE the actual MBOM structure is created. These pre-existing placeholder objects become the basis of defining the required MBOM structure.

The below post follows the first approach mentioned above.

This post is intended to provide a detailed guide and example on how to edit the Business Rule for MFN widget to create MBOM structure based on Make/ Buy definition on attribute of Eng. item.

Version – On premise: 2022x FD03 (FP2223), 2023x FD04 (FP2333)

                 On Cloud    : 2022x HotFix 4.9

Pre-requisites

Licenses – In order to execute this script successfully, user must have below licenses assigned: 

Disclaimer:

Licenses mentioned above are as per 2022x documentation.

Example

In this example a dedicated attribute on Eng. item is used to take Make/Buy input from user for EBOM structure (you can use any other OOTB/ custom attribute) with the following values:

• MAKE: creates a Manufacturing Assembly.
• BUY: creates a Provided Part to implement the Product and stops the recursion.
• Not Manufactured: ignore (creates nothing).

Logical Flow

Example Business Rule

Below is the ready to use business logic for MBOM creation using Make/Buy value from Description attribute on Eng. item. User can create a Business Rule in Data Model Customization app in order to use this example business rule.

Detail Description

When we run ‘Create Mfg Items Structure’ command or drag and drop the Eng. Item on Mfg. item in MFN widget, according to the input value from the dedicated attribute the corresponding Mfg. item is created. It reuses the existing scoped Mfg. item if it exists.

First of all we check if we have any existing scoped items for the Eng. Item.

Logic to check if any scoped Mfg. Item exists

ScopeList = GetProcessScopesFromProduct(currentReference)

If the scoped Mfg. item exists then we can reuse that Mfg. item.

Logic to ‘reuse’ the existing Mfg. Item if scope link exists.

if(ScopeList.Size() <> 0)
{
      set instantiationAction = 2
      set reUseMfgItem = ScopeList.GetItem(1)
}

Here simply the first item in the scoped Mfg. items list is considered for reuse. We can select any particular item from the list which is matching a certain criterion according to the requirement.

If no scope links exist, ‘create a new Mfg. Assembly/ Provided Part or ignore’ based on the Make/Buy input. According to the Make/Buy value the MBOM structure will be generated.

Logic to create the MBOM structure based on Make/Buy value

if (  0 <= currentReference.V_description->Search("Not Manufactured") )
{       
     set instantiationAction = 0
}
else if(0 <= currentReference.V_description->Search("Make") )
{
      set instantiationAction = 1

      set instantiationType= "DELAsmAssemblyModelDisciplines/CreateAssembly"      

      set virtualID = "EKLVirtual" + currentReference.PLM_ExternalID

}
else if (0 <= currentReference.V_description->Search("Buy") )
{
      set instantiationAction = 1
      set instantiationType= "DELAsmAssemblyModelDisciplines/Provide"     
      set virtualID = "EKLVirtual" + currentReference.PLM_ExternalID
}

InstantiationAction:

1. 0 - If you want to ignore
2. 1 - If want to create new Mfg. item
3. 2 - If you want to reuse existing Mfg. item

Here Description attribute on Eng. Item is used to take Make/ Buy input. We can use any OOTB/ custom attribute as per the requirement.

Scenario

Consider an EBOM structure for Gearbox assembly as shown in below image.

Let’s create a MBOM structure for the Gearbox assembly.

In below image we can see a root Mfg. assembly is created and it is scoped with the root Eng. Item in EBOM structure.

Now let’s run the ‘Create Mfg Items Structure’ command from the Authoring section.

Here we can see the resulting MBOM structure in below image.

We can see that the ‘provide’ is created for ICGRBOX0001 because the Description attribute contains string ‘Buy’. For part ICGBHSG0001 the Description attribute contains string ‘Make’ hence Mfg. assembly is created for it.

Similarly depending on the Description attribute value the Mfg. items are created for corresponding Eng. Items and reused if scoped item exists.

Reuse:

If we detach the MBOM structure under the root MBOM and then re-run the ‘Create Mfg Items Structure’ command then the following structure will be created.

This MBOM structure reuses the Mfg. items created initially. We can see that the Name for Mfg. item ICGRBOX0001 is same as the Mfg. item created for ICGRBOX0001 initially. Please refer the below image.

In similar way the other existing Mfg. items (created initially) are reused here.

We can see that the Creation time differs from the current time. This means the existing scoped Mfg. item reference is reused here.

Here we decided the type of Mfg. item to be created for the corresponding Eng. Item using Make/Buy input from Description attribute of the Eng. Item.

Similarly we can utilize this Business Rule to put the required conditions for the MBOM creation in MFN widget depending on the particular requirement.

We can create the MBOM structure based on some input from Eng. Item attribute.

We can reuse certain Mfg. items according to any particular criterion. For example, we can filter the scoped Mfg. items based on plant and reuse only if the plant name is matching.

Business Rule Deployment

On Premise:

The below page can be referred for Business Rule deployment using Data Model Customization app (TXO).

Business Rule Deployment using Data Model Customization App

Resource Set and opening:

On Cloud:

The below page can be referred for Business Rule deployment using Data Setup app.

Business Rule Deployment using Data Setup App

Resource Set:

Opening:

When you create your Business Rule using the Data Setup App you must specify "Server-only" for the scope of this Business Rule.

We cannot change the scope of the business rule once it is created.

Important points to remember in creation/ deployment of this Business Rule (TBA)

Reference:

Documentation: As of now there is no documentation available on dsdoc for this business rule opening.

Author

Author: @JJ 

Person of Contact - @JJ ​​​​​​​@KA