Giter VIP home page Giter VIP logo

mbom-export's Introduction

MBOM Export for Aras MPP

This project adds an export action to the Process Plan item provided by the Aras Manufacturing Process Planning application. Resolve the Process Plan's MBOM by location and produced part, then export the result to Excel or PDF.

History

Release Notes
v1.2.0 Updated Newtonsoft reference to work with recent service packs.
v1.1.0 Includes an optional report to allow users to export the MBOM from the Reports menu instead of the actions menu. Requested in Issue #6.
v1.0.0 First release. Tested on Aras 11 SP15 with MPP 11.0 R3 installed.

Supported Aras Versions

Project Aras
v1.2.0 12.0 SP9 w/ MPP 12.0 R1
v1.1.0 11.0 SP15 w/ MPP 11.0 R3
v1.0.0 11.0 SP15 w/ MPP 11.0 R3

Installation

Important!

Always back up your code tree and database before applying an import package or code tree patch!

Pre-requisites

  1. Aras Innovator installed
  2. Aras Manufacturing Process Planning (MPP) installed
  3. Aras Package Import Utility
  4. aras.labs.mbom_export package

Install Steps

  1. Backup your database and store the BAK file in a safe place.
  2. Open up the Aras Package Import tool.
  3. Enter your login credentials and click Login
    • Note: You must login as root for the package import to succeed!
  4. Enter the package name in the TargetRelease field.
    • Optional: Enter a description in the Description field.
  5. Enter the path to your local ..\mbom-export\Import\imports.mf file in the Manifest File field.
  6. Select the following in the Available for Import field.
    • aras.labs.mbom_export
  7. Select Type = Merge and Mode = Thorough Mode.
  8. Click Import in the top left corner.
  9. Close the Aras Package Import tool.

You are now ready to login to Aras and start exporting.

Optional: Use Report instead of an Action

By default, this project adds an Action to the mpp_ProcessPlan ItemType called Export MBOM. If your users would rather access this feature from the Reports menu instead of the Actions menu, you can remove the Export MBOM Action from the mpp_ProcessPlan ItemType and instead attach the included labs_ExportMBOM Report.

  1. Login to Innovator as admin.
  2. Open the mpp_ProcessPlan ItemType for editing.
  3. Remove the labs_ExportMBOM Action from the Actions tab.
  4. Add the labs_ExportMBOM Report to the Reports tab.
  5. Save, unlock, and close the mpp_ProcessPlan ItemType.

The usage steps documented below still apply. Just access the Export MBOM feature from the Reports menu instead of the Actions menu where applicable.

Usage

Note: The steps below for both use cases start from the Process Plan item window, but the Export MBOM action can also be run from the main grid. You don't have to open the Process Plan or MBOM view to use the Export MBOM action.

Export to PDF

Export to PDF

  1. From the Process Plan, select Actions > Export MBOM from the main menu.
  2. In the Export Options dialog, select the Location and Produced Part you want to use to resolve the MBOM.
    • These dialog fields are populated from the Locations and Produced Parts relationships on the Process Plan.
  3. Select PDF from the Export Type dropdown list.
  4. Click the Export MBOM button to begin the export.
  5. In the new browser window that opens, enter CRTL+P or manually open the browser's print options.
  6. Select Microsoft Print to PDF as the printer.
    • Note: You may need to enable the browser's background image/graphics settings in order to see the alternating table row colors.
  7. Click Ok/Print.
  8. When prompted by the file system, choose a location and file name for your exported PDF file.

Click here to see an example of a MBOM exported to PDF.

Export to Excel

Export to Excel

  1. From the Process Plan, select Actions > Export MBOM from the main menu.
  2. In the Export Options dialog, select the Location and Produced Part you want to use to resolve the MBOM.
    • These dialog fields are populated from the Locations and Produced Parts relationships on the Process Plan.
  3. Select Excel from the Export Type dropdown list.
  4. Click the Export MBOM button to begin the export.
  5. In the browser prompt that appears, confirm whether you want to open or save the Excel file.
  6. Open the file for viewing or editing as needed.

Click here to see an example of a MBOM exported to Excel.

Note: When you open the Excel file, you may receive a warning about the file type. This is a known issue but does not affect the usability of the file. As a workaround, run Save As on the file to avoid seeing the message next time you open workbook.

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request

For more information on contributing to this project, another Aras Labs project, or any Aras Community project, shoot us an email at [email protected].

Credits

Created by Eli Donahue for Aras Labs. @EliJDonahue

License

Aras Labs projects are published to Github under the MIT license. See the LICENSE file for license rights and limitations.)

mbom-export's People

Contributors

ajsebastian avatar asebastian-aras avatar elijdonahue avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar

mbom-export's Issues

Allow export of MBOM without manufacturing location

Location is not a required field in MPP. Especially in companies where different production locations work with the same ProcessPlan, it´s likely that this property is empty.
The mbom-export expects this value to be set. But if no location is available, it´s a lot of clicking to close the dialog.

Avoid use of keyed_name, use id instead

Hi Eli,

this one is a real excellent project! It´s highly reusable and does many things just right! But I run into an conceptional issue. I am sorry for the following question, because it´s probably hard to answer. I acutally planned to ask about this since months, but didn´t know where to place the request.

I was forced to change the following in the code to get the project working:
labs_GetMBOMData - around line 27:
image
In my case, I use the item_number in the MBOM, but the Part keyed_name contains item_number and revision information. Of course using the item_number like I did above is not a solution, as the MBOM export will deliver wrong results when exporting MBOMs that use previous part revisions.
But from my POV, neither the item_number nor keyed_name are unique indentifiers. Both are not the best choice to select a destinctive part.

I noticed that Aras increasingly uses the keyed_name property as item selector instead of the id. But the increasing use of keyed_name instead of id is a real problem. I already had corrupted data caused by this one. I right now use many addtional code for handling the keyed_name on various events (copy item, version item, ...). This amount of work wasn´t necessary in the past. Previous concepts used standard ids in combination with keyed_name attribute as display value. I do not fully understand why Aras changed that proven approach.

Many of the newer Aras features solely rely on the keyed_name. This forces users to use more precise keyed_name for items. But guaranteeing uniqueness of an item is not the job of the keyed_name. Is this really how it´s intended to be?

To break down my long text to simple questions.

  • How can we solve this on ein the project?
  • What is Aras masterplan regarding the keyed_name?

Many thanks for the project! Sorry for this question!
Angela

Add option to add thumbnails for building a pick list

Similar to the Elis idea to add MPP icons to the export, it would also be helpful to add thumbnail images.
If manufacturing prepares to build a product, someone have to pick the various components from the storage area. A pick list that contains images of the needed products helps to collect stuff faster.

This use case is probably better solved in an additional one level report which is mainly intended to be used as picklist. For this use case, a multilevel bom would be contraproductive.

Fix Excel format error message

When an exported Excel file is opened in Excel, an error message occurs about an invalid format. This error doesn't prevent use of the project, but it isn't ideal. I think the XML content of the xls file is missing something for Excel to recognize the file as valid xls. Not 100% sure what it's missing though.

Labs: When we find this fix we should submit an Innovator bug fix, as the same error occurs when exporting anything from Aras to Excel.

Use Report instead of Action to trigger MBOM Export

The current version uses an additional Action to trigger the MBOM Export.
But users are used to creating reports via the report menu. The action menu is inteded for other things.

Solution:
Use an additional report item to start the method to improve user experience:
image

Include MBOM metadata in exported Excel file

PDF export includes the process plan number, location name, and part number used to resolve the MBOM. Not currently included in the Excel export XSLT, but likely an easy fix.

Include icons in the exported content

The code that retrieves the MBOM content also gets the urls for the icons used in the grid. It would be possible to update the method and report XSLT to include the icons in the exported content.

Error Number CS0103

Hi Eli,

on recommendation of Rolf (Laudenbach) I've installed the mbom-export solution. When trying to run the export I get the error CS0103. How can I fix this issue?
mbom_export_error_cs0103.pdf

Best regards,
Jochen

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.