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. Imports
  2. Imports of entities

Import items

State change timing

original request: 2018-02, VíBa; reason:

  • minimizing uncleanable versions typically on an item i.e. write properties or BOMs on items before approval or after change to WIP

  • applying ACLs to associated item files when the state changes

Implementation

  • for each batch entity is loaded:

    • LfCycState_cur (current state)

    • LfCycState_trg (target/required state from erp)

  • as part of the import, a state change is made to either:

    • OnVaultEntityAvailable - i.e. immediately after getting the Vault entity instance or

    • OnBulkFinished - before the batch import is completed in the inverse order of batch decay (children first, top last)

  • logic for determining when to change the build:

    • OnVaultEntityAvailable for the state combination:

      • LfCycState_cur = Released AND LfCycState_trg <> Released

      • LfCycState_cur = Obsolete AND LfCycState_trg <> Released

    • OnBulkFinished in other cases

PreviousEntity identification by ERP systemNextImporting applications

Last updated 11 months ago

Was this helpful?