Day-0 Explorer
General enterprise visibility, with access to the enterprise's general document spaces. No HR or payroll compartment access.Viewing as Enterprise Reader

Trace · LOC-000009

Canonical entityLocationNashik DepotOpen the canonical record

Source — ERP Warehouse

Derived chronology · 5 stages · technical time
  1. Source

    ERP Warehouse WH-NASHIK · Nashik Depot · status A

  2. Connector

    Incremental sync · extract version ERP_NATIVE_V1

    Open the ERP Warehouse connector
  3. Landed

    13 Sep 2026, 18:18 IST · recorded

    source updated 13 Sep 2026, 18:18 IST · recorded

    Raw payload as it landed (8 fields)
    created_at
    2026-09-13T12:48:24.05918+00:00
    legal_entity_id
    f8f9105d-ec9f-47d6-a2ff-f92eaa14abea
    operating_unit_id
    91506faf-4b05-4ada-920d-5fff01794546
    status_code
    A
    updated_at
    2026-09-13T12:48:24.05918+00:00
    warehouse_code
    WH-NASHIK
    warehouse_id
    e0005ced-31e4-412f-8b67-b8e3eca7fb5e
    warehouse_name
    Nashik Depot

    payload sha256 6a46af709351a6dcb8a78130344f54cc0e7a5f3e414004c351385d1afaa78a72

  4. Mapping
  5. Resolution

    Exact business identifier match · confidence 1.00000 · RES-LOC-ERP-WAREHOUSE v1

This is a view over the records, not a second source of truth. The landed time is technical time — when the payload arrived — not the business time of the record, which its own dates carry.

Field lineage

Canonical fieldCanonical valueSourceFromContributionMapping · survivorship
display_nameNashik DepotERP Warehouse WH-NASHIKwarehouse_name= Nashik DepotDirectMAP-LOC-ERP-WAREHOUSE
location_typeWarehouseERP Warehouse WH-NASHIK← constant WAREHOUSEConstantMAP-LOC-ERP-WAREHOUSE

Entity resolution

Open entity resolution
  • ERP Warehouse WH-NASHIK · Exact business identifier match · confidence 1.00000 · RESOLVED · RES-LOC-ERP-WAREHOUSE v1

Resolution says records represent the same enterprise thing. It is not an operational integration link.