Be.Smart ERP Connector
(EN) Consultant Manual
(EN) Consultant Manual
  • Be.Smart ERP Connector Consultant Manual
  • Abbreviations used
  • Home
  • Purpose of the product
  • Technical solution
    • Data Interface
    • Autodesk Vault
    • Basic types of jobs and their origin
  • Configuration
    • EC configuration (central)
      • Main Card
      • Property Values tab
        • Tab < entity>
    • EC local configuration
    • Logging in
      • Logging to the local station
      • Logging in DI
    • Reverse logging
      • Description of the reverse logging process
    • FLAGs (additional flags in std Vault configuration)
      • List of symptoms
  • Commands and Features in Vault Explorer
    • Attach to already existing purchased item
    • Apply item security to files
    • Create Raw material BOM rows
    • Send to DI (Send to Data interface)
    • Data interface browser
      • Functions
  • Export
    • Item breakdown
      • BOM loading method
      • Transfer MJ
    • Atypical requirements
  • Imports
    • Processing of external requests for transfer to Vault (from version 2019 inclusive)
      • The procedure for processing the Arkance.Import initialization job:
    • PreProcess sample
    • Imports of entities
      • Entity identification by ERP system
      • Import items
      • Importing applications
      • Import folder
      • Importing a change command
      • Import schedules
  • Recommended commissioning procedure
    • DI commissioning
    • Mapping fields
  • Castomization (ec addons)
  • Attachments
    • Job types - complete list
    • Configuration type Global/Workgroup
Powered by GitBook
On this page

Was this helpful?

  1. Commands and Features in Vault Explorer

Attach to already existing purchased item

context of the file(s)

purpose: a way to bind, update and secure the file(s) for the next model of an existing item

verifies for each file:

  • the file must be in a category with |PURCH| in the definition description

  • the file must have a valid property value that is mapped to the item number

  • an item with this number must already exist and have an associated non-empty life cycle

  • the item must already have a primarily associated file

  • the item must already be in a category with |PURCH| in the definition description

executes for each file:

work/development:

  • Move processing (write properties to the model and assign) to VaultExplorer (under the current account)

  • add a new job for Visualization (e.g. check if the Vault settings show the need to update the visualization)

PreviousCommands and Features in Vault ExplorerNextApply item security to files

Last updated 2 years ago

Was this helpful?