Treasury :: Financial Management Service

Enterprise Data Architecture

Treasury Account Symbol Business Message

Business Message Listing tas:TreasuryAccountSymbolRecords tas:TreasuryAccountSymbolRecord tas:BusinessEventTypeRecords tas:BusinessEventTypeRecord [1..unbounded] fms:BusinessEventType [1..1] tas:AdjustmentBusinessEventType [0..1] tas:BusinessTransactionType [0..3] tas:InternalClassification [0..1] Library Resource Documentation Data Dictionary and Change Log Data Dictionary Attribute DataDictionary Element DataDictionary tas:BusinessEventTypeRecord Data Documents Download the Mind Map Browse the Mind Map Help Basic Help Generic Help Downloads Published Releases Current Treasury Account Symbol Message Release Archived Releases Release 2.0 Release 2.1 Release 2.2 Expand All Collapse All

Element Information Name tas:BusinessEventTypeRecord Definition One to many BETCs corresponding to a particular TAS. Namespace urn:us:gov:treas:fms:TreasuryAccountSymbol:v2.3 Cardinality [1..unbounded] Content Model The <tas:BusinessEventTypeRecord> 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 <tas:BusinessEventTypeRecord> element has a particular order of elements that must be followed. Description Attribute Name Use DataType Definition AccountSuspendDate [0..1] YYYY-MM-DD Only populated if the TAS-BETC combination is suspended. AccountEffectiveDate [0..1] YYYY-MM-DD Indicates the date when the TAS-BETC became available for use. AccountEndDate [0..1] YYYY-MM-DD Indicates the date when the TAS-BETC became completely inactive. IsCredit [0..1] 1|0 Indicates if the item is a debit or credit, for example, a value of "1" would mean that it is a "credit". If the attribute is not populated or not present in the XML instance document, then the default value is understood to be "0".

For help, please contact the Treasury FMS Enterprise Data Architecture team.

Last Updated: 2011-06-22T14:05:29.592-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.