Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Versión

Fecha

Comentarios

Versión actual (v. 2)

25/09/2023

Juan Eduardo Sosa

v. 1

13/12/2021

Angel Javier Larrosa


Header

Attribute

Type

Description

system_id

string

Is the system identification. For Third Party integrations you must put 'third_party'

local_id

int|null

  • SIMA sends to ERP.

  • SIMA receives from Third Party. Is SIMA unique identification for work orders.

(Only one of local_id, local_code, external_id, external_code is used)

local_code

string|null

  • SIMA sends to ERP.

  • Not used in Third Party integrations.

(Only one of local_id, local_code, external_id, external_code is used)

external_id

int|null

  • SIMA receives from ERP.

  • Not used in Third Party integrations.

(Only one of local_id, local_code, external_id, external_code is used)

external_code

string|null

  • SIMA receives from ERP.

  • Not used in Third Party integrations.

(Only one of local_id, local_code, external_id, external_code is used)

date

datetime

  • Is the creation date.

  • ISO-8601 format, Ex: "2019-10-13T11:29:20-03:00"

voucher_date

datetime

  • Is the work order date.

  • ISO-8601 format, Ex: "2019-10-13T11:29:20-03:00"

name

string|null

  • Is the name to identify the work order.

is_read_only

bool

  • Indicates if the work order is editable in the external ERP.

  • In integrations, the value true will be returned/stored whenever the following conditions are met:

    StausId = 6 => ActivityStatus::OA_STATUS_EXTERNAL_SYSTEM

    Comes from Third Parties

concurrency_token

int|null

  • It is used to control the flow of an OT. It allows to avoid writing of unwanted OTs.

  • Third Party not implemented yet.

currency

Object

  • Object used by ERPs to define the currency

  • Not used in Third Party integrations.

(Only one of local_id, local_code, external_id, external_code is used)

observations

string|null

  • Work order observation.

state

Object

  • Object used to define the status of the work order.

  • Only one of pending, executed, confirmed can be true. The others mus be false.

  • For ThirdParty integrations there can be three cases.

  1. Pending true. When the work order is approved.

  2. Executed true: When the work order is approved and has confirmation dates.

  3. Confirmed true: When the work order is executed. This alos implies that all confirmations have execution dates.

extra_fields

Object

  • Object used to define other attributes necessary for integration between systems.

  • The object dimension and company are used by ERPs.

  • The object voucher_type is used to specify the work order type. In Third Party integrations local_id must match with one of the SIMA voucher type.

(Only one of local_id, local_code, external_id, external_code is used)

...