Skip to main content

​
Tango PO Outbound

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

​
Overview

SFTP file-based outbound integration. Tango writes approved Purchase Orders (header + detail rows) as a pipe-delimited text file to its SFTP server. The client reads the file and processes the data in its target system. Owner: Tango Analytics Spec version: 0.5 Status: Draft (auto-generated from design doc — needs review)

​
Transport

Existing files are moved to Processed/ with a timestamp before each new write.

​
Integration logic

  • All POs with status Approved are exported.
  • Zero-dollar lines are excluded.
  • After successful export, POs are flagged Exported.
  • PO_ID is the reconciliation key.
  • The file always contains Header + Detail.
  • If there are no approved POs, no file is generated.

​
Data fields

​
Validations

​
Open Questions / Assumptions

  • No “Required?” column in the source — every field is left optional in the schema.
  • Numeric fields typed as VARCHAR (PO_AMOUNT, RETAINAGE_PCT, QTY, RATE, LINE_AMOUNT): mapping table says VARCHAR; the spec mirrors that. Confirm whether numeric typing is intended.
  • SFTP credentials are blank in source.
  • Timing/frequency is <TBD>.
  • Lookup values for PO_TYPE, PAYMENT_TERMS, CURRENCY, UOM, C_EXT_LOV1 are <TBD> in Appendix.
  • Header / Trailer formats not separately defined.
  • Test Scenario #2 is missing from the source (numbering jumps from 1 to 3 in the doc).

​
Changelog