Treasury :: Financial Management Service

Enterprise Data Architecture

Transmission Business Message

Business Message Listing Transmission Batch BusinessTransaction FinancialTransaction FedwireDetail MessageSection [1..unbounded] DataElement [0..unbounded] Library Resource Documentation Data Dictionary and Change Log Data Dictionary Attribute DataDictionary Element DataDictionary MessageSection Data Documents Download the Mind Map Browse the Mind Map Data Listing Help Basic Help Generic Help Downloads Published Releases Current FMS Business Message Release Archived Releases Release 4.5 Release 4.4 Release 4.3 Release 4.2.1 Release 4.2 Release 4.1 Release 4.0 Release 3.0 Release 2.2 Release 2.1 Expand All Collapse All

Element Information Name MessageSection Definition Contains the grouping of name/value pairs Namespace urn:us:gov:treas:fms:BusinessTransaction:v4.6 Cardinality [1..unbounded] Content Model The <MessageSection> element contains 1 child element 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 <MessageSection> element has a particular order of elements that must be followed. Description The <MessageSection> element is a child element of the <FedwireDetail> element. The <MessageSection> element is the first element under the <FedwireDetail> element and is a required repeating (unbounded) element. Attribute Name Use DataType Definition SequenceNumber [0..1] String [0, 4] Provides a sequential order of items. SectionCode [1..1] String [0, unbounded] A brief description of what the Fedwire represents. SectionText [0..1] String [0, unbounded] The column name in CashlinkII that is used to store part of the Fedwire message. Count [0..1] 0,1,2,..n Indicates the number of items represented by this record.

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

Last Updated: 2011-05-31T21:19:17.33-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.