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 schedules

Vault line origin flag

  • an association property called "ERP" is used to distinguish the origin of the breakdown line

  • this property does not need to be configured , it is created automatically when you first import the spreadsheet as follows:

    • Boolean type

    • mapping of the "Breakdown row"

  • it is not necessary to write this flag to the EcASSOC table as an external field and map it to a property in Vault (unless Vault=>ERP export is required)

  • the logic is based on the flag "ERP = True" on the piecewise binding this flag is necessary because of the repeated import of the schedule into Vault

  • if a breakdown line does NOT have this "ERP" flag set, import processing considers CAD, manual creation, EPLAN, etc. as the source of this line.

  • imported BOM rows are marked ERP=True

Rules and restrictions

  • import is done only in one level (one "step")

  • for the breakdown line is transferred from the exchange interface (EcASSOC) field:

    • position => Position number

    • qty_total => Quantity

    • qty_occ => Quantity of items

    • row_number => Row order (negative number can be used, decimal number cannot be used)

    • user attributes on the binding (Association property)

  • in Vault, the "bulb" attribute of the spread line (Turn on/off the spread line) is always set to On by the import

  • it is not possible to transfer suppressed lines of the schedule to the Vault (in the Vault with the light bulb off)

up to and including version 25.0.5: the occurrence of lower fields must be unique , i.e. the breakdown cannot contain multiple identical numbers of lower items

PreviousImporting a change commandNextRecommended commissioning procedure

Last updated 2 years ago

Was this helpful?