BIll of Materials with Unreleased Items

[richard.valdez]

there shoould be some built-in system validation created so you cannot release a Bill of Materials with unreleased Child Components or at least gives you a warning. this causes a lot of problems with our Jitterbit / Netsuite integration.

here are a couple of examples:

if I release a BOM that had one unreleased child component then the BOM will not push into Netsuite through Jitterbit. forcing us to create another CO to correct this problem.

if I have a BOM with two Child Components and one is unreleased it will push into Netsuite through Jitterbit with only the one component (the released one) and there is no error/ warning/ or indication that one items didn't make it or that the BOM is not correct. 

these type of things can be process controlled internally by the company but can be missed and the system will still let you do it. even a warning like "You are about to submit a Bill of Materials with Child Components that are not yet Released" would be very helpful! 

[tony.mandatori]

Richard,

Validation before sending to ERP makes a lot of sense.

Have you tried doing this with a Validation or PreCondition Script in the Change Order?  On BOMs, you would only have to check one level deep, since the other children would be checked on their Change Orders.

I think you need to add a check to ensure that the child is either on the same Change Order or is released.  If both fail, then veto the transition.

Thanks,

Tony

[richard.valdez]

I think validation script or pre condition is needed I'm not savy at scripting so this will need to be created, mostlikely by our consultant until I get some Java training. 

this seems to be something that I would say is not standard practice to release a BOM with Unreleased Items this is why I suggest a Built- in warning

[tony.mandatori]

The scripting isn't so bad...

Here is a little script I tested:

var messages = [];
var bomSize = 0;
var latestversion;
var currentparent;
var currentchild;

var wfItemSize = item.workflowItems.length;
println("Item Size is: " + wfItemSize);

if (wfItemSize > 0){
  println('Got Affected Items');
 
  for (var i = 0; i < wfItemSize; i++) {
      currentparent = item.workflowItems[i].item.descriptor.descriptor;
      println ("Checking item: " + i + currentparent);
     
      bomSize = item.workflowItems[i].item.boms.length;
      // Look for BOM
      println("bomSize is: " + bomSize);

             
      if (bomSize > 0){
          for (var j = 0; j < bomSize; j++) {
              currentchild=item.workflowItems[i].item.boms[j].item.descriptor.descriptor;
              println ("... checking child: " + j + currentchild);
              latestversion = item.workflowItems[i].item.boms[j].item.descriptor.dvi.release;
              println("latest version is: " + latestversion);
             
              if (latestversion === null) {
                  messages.push (currentparent + " calls " + currentchild + " which is unreleased.");
              }

          }
      }
  }
}

println(messages);

returnValue (messages);

It creates the following debug output:

Item Size is: 3
Got Affected Items
Checking item: 0 - 100-1000-01 [REV:w]
bomSize is: 1
... checking child: 0015-000002 - Sample Part [REV:w]
latest version is: null
Checking item: 1015-000001 -  [REV:w]
bomSize is: 0
Checking item: 2699-2000-002 - SBOM FINISHED ASSY GT 220 [REV:w]
bomSize is: 2
... checking child: 0690-0001-000 - SBOM PCBA p681 GT220 [REV:A]
latest version is: A
... checking child: 1680-2003-000 - SBOM THERMAL p681        [REV:A]
latest version is: A
[ - 100-1000-01 [REV:w] calls 015-000002 - Sample Part [REV:w] which is unreleased.]

And the message returned is:

 - 100-1000-01 [REV:w] calls 015-000002 - Sample Part [REV:w] which is unreleased.

[nguyentru]

Hi Richard,

We will add this to our feature list, and hope to get this idea in our future release.

Thank you,

Trung

[benderk]

Since this topic is over 6 months old, and we would like to review it in more detail internally in the context of Modern before potentially moving into a development backlog.

Sincerely,

Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management

[benderk]

Thank you for submitting your idea. Have you tried the Modern Interface lately? We request that you review your idea in the context of the Modern interface. If your idea is not addressed, we invite you to create a new Idea in the context of Modern so that it can be addressed accordingly. Sincerely, Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management