> For the complete documentation index, see [llms.txt](https://help.besmart.software/erpc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/erpc/en-consultant-manual/imports/imports-of-entities/import-schedules.md).

# 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