Treasury :: Bureau of the Fiscal Service
Enterprise Data Architecture
Transmission Response Data Exchange


Data Exchange Listing
TrnsmRsp [1..1]
Sucses [0..1]
Wrns [0..1]
Errs [0..1]
Tot [0..2]

Element Information
NameTrnsmRsp
DefinitionUsed to identify an application error by either text, code, or by an online description and also to give the status, tag, and/or identification of the record that may have caused the error.
DataTypeContainer
Attribute Information
Attribute NameUseDataTypeDefinition
EchoIDrequired String [0, 80]Identifies the unique original Transmission message level identifier.
IDrequired String [0, 80]An identifier for the record. For a receiving system, this value can be used to reconcile updates to an existing record and qualify new records. For a sending system, this value can be used to reconcile acknowledgements for the submitted records.
TrnsmTsrequiredYYYY-MM-DDTHH:MM:SS or may end in 'Z' to reflect UTC (Coordinated Universal Time)Indicates the date and time of a transmission.
AcctbBusLnCdoptionalCollections [Collections], DebtCollection [Debt Collection], Payments [Payments], Intragovernmental [Intragovernmental], Securities [Securities], Investments [Investments], Miscellaneous [Miscellaneous]The business line of a transaction's content (as opposed to the business line of the program that processes the transaction, which is not always the same).
IptSysTxtoptional String [0, 40]Identifies the sending trading partner.
SeqNroptional [0-9]{4}|0[0-9]{3}|00[0-9]{2}|000[0-9]|[1-9][0-9]*Provides a sequential order of items.
Technical Information
Schema versionurn:us:gov:treasury
Cardinality[1..1]
Content ModelThe <TrnsmRsp> element contains 4 children elements and has a sequence content model. The sequence content model means that there is a particular order to the children elements of the parent element - in this case, the <TrnsmRsp> element has a particular order of elements that must be followed.


For help, please contact the Treasury Bureau of the Fiscal Service Data Registry team.
Last Updated: 2017-05-02T13:23:37.587-04:00

This web site is informative only and may contain publishing errors/inconsistencies - please carefully review the appropriate XML Schema documents in the Download section.