Skip to main content

​
Tango CO Outbound

Generated from Tango CO Outbound Integration Design Specification V0.5.docx in SharePoint folder 04 Projects Integrations. OAS spec: co-outbound.yaml

​
Overview

One-way SFTP file-based outbound integration. Tango writes a pipe-delimited text file containing approved Change Order (CO) header and line-item rows to its SFTP server; the client reads the file from that location and loads it into their target system. Owner: Tango Analytics (Solution / Technical / Functional Lead roles listed as TANGO; client roles unfilled in source). Spec version: 0.5 Status: Draft (auto-generated from design doc — needs review)

​
Transport

Before each write, Tango moves the prior file to a Processed subfolder with a timestamp suffix. No file is written when there is no data.

​
Authentication

SFTP user + password, provisioned per environment. Concrete values not in the design doc — request from the Tango integration team before testing.

​
Integration logic

  • Tango selects all Change Orders with status Approved and produces the outbound file.
  • Zero-dollar lines are excluded from the file.
  • Negative COs are included.
  • CO_NUMBER is the unique reconciliation key — the client must round-trip it back via CO Inbound.
  • The file has both Header and Detail rows.
  • After file generation, all exported COs are flagged with status Exported in Tango.
  • If no approved COs exist, no file is produced.

​
Data fields

​
Validations

  • Zero-dollar COs are NOT exported (negative COs ARE).
  • Only Status = Approved COs are exported.
  • The file always contains Header, Detail, and Trailer information.

​
Open Questions / Assumptions

Each item below was either unstated, ambiguous, or <TBD> in the source document.
  • Required-field annotation is missing for every column. The source doc’s “Required?” column was empty for all 22 fields; the spec leaves required[] empty rather than guess. Confirm which fields a downstream system must always receive.
  • SFTP credentials are <TBD> in the doc — confirm user/password (and whether key-based auth is in fact the standard).
  • Timing and Frequency section is <TBD> — confirm the cron/schedule.
  • Sample data column is empty for every field — capture at least one realistic example row in the next revision.
  • Header / Trailer row formats not defined in the source — assumed the data mapping table describes Detail rows only.
  • No Glossary entries — verify the meaning of fields that share names with PO/AP integrations (e.g. LINE_AMOUNT, SEGMENT1..6) actually match.

​
Changelog (from source doc)