DMT Bill of Operations with OpStds defined

Thank you for your reply,  we ran into the same gotcha on PO and Sales Orders.  The DMT tool is perfect but our data is not. 




On May 3, 2015, at 3:04 PM, bruce.d.ordway@... [vantage] <vantage@yahoogroups.com> wrote:

 

<div id="ygrps-yiv-1829051039ygrp-text">
  
  
  <p>&gt;&gt;I figured out the process to change<br>Sounds good.<br>I know it took me a while to start using multiple passes. <br>Since the DMT is using the business logic to update records and not writing directly to the tables.<br>And it might simply ignore some values instead of showing an error.<br><br><br>Reminds me of another &quot;gotcha&quot; I ran into on job sub-assembly imports<br>Some jobs had been edited so there were gaps in the numbering the subs, i.e. 1, 2, 4, 6.....<br>The DMT  import ignored the numbering and used business logic to renumbered them in sequence as new jobs. So 1,2,3,4 instead of 1,2,4,6. It was driving me crazy until I finally realized what was going on.</p>

</div>

I am in the process of DMT Bill of Operations from one plant to another.   We have 5 Standard Ops, which we don't use but can't delete because the StdOps have been used in the past, when we DMT the operation the system retrieves the SetHoursPerMach and EstProdHours from the OpStd and not the DMT template.  I thought I could re-run the operation and update the SetHoursPerMach and EstProdHours but apparently not.   I understand why on the first run the OpStd is retrieved but Epicor allows the Engineer to overide the standard so we should be able to override via DMT.   Does anyone have a work around besides manual intervention? 
 
 
If I understand what you're saying...
You'll DMT the JobOper fields on the first run.
Then you can run a second run to set the JobOpDtl# fields.

It's was kind of a pain to figure out the way the business logic does it.
Like you are saying...
the first run the OpStd is retrieved but Epicor allows the Engineer to overide the standard
I figured out the process to change SetHoursPerMach and EstProdHours. Need to change the template and remove all fields except required fields and SetHoursPerMach, EstProdHours, Machines,  ProdStandard and StdFormat on the second DMT.  

On May 1, 2015, at 11:58 AM, Brinda Whitaker bkw_symmetry@... [vantage] <vantage@yahoogroups.com> wrote:

 

<div id="ygrps-yiv-1963233535ygrp-text">
  
  
  <p></p><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"><div id="ygrps-yiv-1963233535yui_3_16_0_1_1430494436683_9843" dir="ltr"><br>I am in the process of DMT Bill of Operations from one plant to another.&nbsp;&nbsp; We have 5 Standard Ops, which we don&#39;t use but can&#39;t delete because the StdOps have been used in the past, when we DMT the operation the system&nbsp;retrieves the SetHoursPerMach and EstProdHours from the OpStd and not the DMT template.&nbsp; I thought I could re-run the operation and update the SetHoursPerMach and EstProdHours but apparently not.&nbsp;&nbsp; I understand why on the first run the OpStd is retrieved but Epicor allows the Engineer to overide the standard so we should be able to override via DMT.&nbsp;&nbsp; Does anyone have a work around besides manual intervention?&nbsp;</div><div id="ygrps-yiv-1963233535yui_3_16_0_1_1430494436683_10056" dir="ltr">&nbsp;</div><div id="ygrps-yiv-1963233535yui_3_16_0_1_1430494436683_10055" dir="ltr">&nbsp;</div></div><p></p>

</div>
>>I figured out the process to change
Sounds good.
I know it took me a while to start using multiple passes.
Since the DMT is using the business logic to update records and not writing directly to the tables.
And it might simply ignore some values instead of showing an error.


Reminds me of another "gotcha" I ran into on job sub-assembly imports
Some jobs had been edited so there were gaps in the numbering the subs, i.e. 1, 2, 4, 6.....
The DMT import ignored the numbering and used business logic to renumbered them in sequence as new jobs. So 1,2,3,4 instead of 1,2,4,6. It was driving me crazy until I finally realized what was going on.