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. Configuration
  2. Reverse logging

Description of the reverse logging process

reverse logging can be enabled in the central EC configuration;

after it's turned on:

  • the scheduled job CadStudio.Ec.Service is created

  • The processing of the CadStudio.Ec.Service job instance from the point of view of reporting back is as follows:

    • for each batch that contains a record in DI.EcENTITY that has a comm_stat status of Error (9) or ErrorReportRequest (90) a new job CadStudio.Error is created with a reference to the batch number (bulk_id) and the parameters of this job contain the error description read from DI.EcLOG

    • then the CadStudio.Error job is processed and its processing ALWAYS ends with an error and the error description is read from the job parameters and used to log the job error

  • for jobs (batches) of the CadStudio.Export or Import type that end with an error, the transfer status ErrorReported is written (DI.EcENTITY.comm_status = 91)

PreviousReverse loggingNextFLAGs (additional flags in std Vault configuration)

Last updated 2 years ago

Was this helpful?