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?

Export

PreviousFunctionsNextItem breakdown

Last updated 2 years ago

Was this helpful?

processing is carried out in the following order:

  • DI entry - EcENTITY - basic (system) fields

  • DI entry - EcENTITY - custom field (Property)

  • DI entry - EcASSOC - basic (system) fields

  • DI entry - EcASSOC - custom field (Property)

  • writing to DI - EcLINK (it is executed depending on the PendingPublication setting - if it is true, the writes are performed by Publisher and further processing is part of the CadStudio.Export.PostProcess job)

  • regarding the job for FLC, change EcENTITY.comm_dir from 0 to 10

  • Create TrainJobs

  • Addon PostProcess

  • EcCore PostProcess

  • EcENTITY.comm_status = Pending

In the PendingPublication mode, the EcLINK Publisher plugin performs writes to the table and after the last write, the CadStudio.Export.PostProcess job is created. Processing of this job will provide postprocessing for the given job and set comm_status to Pending.

Item breakdown
Atypical requirements