This document is intended to provide a detailed guide and examples on how to customize a Business Rule for opening id DELMIA_GetMfgItemReferenceToUseFromScopingItems_ID to reuse the existing Mfg. item reference in the same plant/organization.

Introduction

When we want to reuse the existing Mfg. item reference which is present in the database and satisfies some custom condition, it’s possible by customizing this BL.

The Mfg. Engineer prepares the Mfg. planning for some Eng. Part or Assembly for his plant/ organization and saves it in the database.

In case some other Mfg. Engineer from the same plant/ organization has the existing Eng. items in EBOM which are already getting manufactured in his plant/organization. When he wants to use the same Mfg. planning already available in the database for the same plant/ organization then he can reuse it using this example Business Rule.

Version – 2022x FD01 (FP2205) & 2023x FD04 (FP2333)

Pre-requisites:

Licenses –

• PPL(Process Engineer): required to create Mfg. Assembly object.

Disclaimer: Licenses mentioned above are as per 2022x & 2023x documentation.

Example: Reusing Mfg. items within same Plant/ Organization

This example shows how we can reuse one of the existing Mfg. items from the database if it is present in the same organization.

Detail Description:

Following preference setting (use same item reference to implement multi-instantiated parts) is required to check for this BL to get invoked. If it is unchecked, the BL won’t get invoked.

No Reuse:

When the “Use same manufactured item reference to implement multi- instantiated parts” is NOT checked, a NEW Mfg. Item Reference gets created to implement an Eng. Item and no already scoped items are reused. The Business Rule is not invoked in this case.

Reuse:

The existing Mfg. Item Reference object is used for each Instance you create.

It’s possible to add some custom conditions to select the item to reuse from the list of available scoped items. Please refer below code snippet for the customization example.

Here, a check for ‘organization’ is added. Among the list of existing scoped items the Mfg. item with organization matching the current organization will be reused. 

set NbOfScopingItems = iListOfScopingMfgItems.Size()

/* Determine the current Org from our Security Context */
set UserOrganization = Parameters->GetAttributeString("Organization")

if (NbOfScopingItems > 0)
{
   index = 1

   for index while index <= NbOfScopingItems
   {
       set ItemReference = iListOfScopingMfgItems.GetItem(index)
       if (ItemReference <> NULL)
      {
         /* Compare Org of scoped item with current Org... use it if there is a match */
         set scopedObjectOrg = ItemReference->GetAttributeString("organization")

         if (scopedObjectOrg == UserOrganization) // Orgs match ! 
         {
            set oMfgItemReference = ItemReference
                                    break
         }
      }
   }
}

We can add few more custom conditions to filter the Mfg. item reference to reuse from the list of scoped items available in the database.

Scenarios

Consider an EBOM structure for Gearbox as shown below.

Let’s change the current organization to Pune.

Now let’s create a MBOM structure for bearing assembly in above EBOM structure. A manufacturing assembly ‘ICGBBEA A’ implementing the bearing assembly is created in ‘Pune’ organization.

Scenario 1

Now in ‘Pune’ organization let’s try to create another MBOM structure implementing the same bearing assembly. Let’s drag and drop the bearing assembly on the new MBOM root node.

In default case (without reuse) it should create a new Provided part on drag and drop of any product.

We can see that the earlier created Manufacturing assembly scoped with Bearing Assembly is reused here. Note that both the current organization and organization of existing scoped Manufacturing assembly is same and that is Pune here.

Scenario 2

Now let’s change the organization to Bengaluru.

Now in ‘Bangaluru’ organization let’s try to create another MBOM structure implementing the same bearing assembly. Let’s drag and drop the bearing assembly on the new MBOM root node.

We can see that a new provided part is created to implement the bearing assembly. This is default OOTB behavior.

 Note that the current organization (Pune) and organization of existing scoped Manufacturing assembly (Bangaluru) are different here. This does not allow the reuse in the above Business Rule.

Business Rule Deployment

The below page can be referred for Business Rule deployment.

How to Deploy Business Rule

For deployment using Data Setup app following Resource set and Opening needs to be used
Resource Set:

Opening:

Reference

Documentation: Get Item Reference to Use from Scoping Items (DELMIA_GetMfgItemReferenceToUseFromScopingItems_ID)

Author

Author - @JJ 

Person of Contact - @JJ & @KA