4.0 Mapping

This section contains an introduction to EDI transaction sets, guidance on how to read a transaction set, and the transaction set maps that Ginnie Mae will be using for its EDI Loan Level reporting. These include:

• Instructions for how to create the outer telecommunications envelope that carries a set of transaction sets - ISA and IEA segments referred to as the interchange envelope
• The electronic "paper clip" that holds related sets of transaction sets together-the GS and GE segments, referred to as the functional group
• The 203 Secondary Mortgage Market Investor Report and 997 Functional Acknowledgment transactions
• It is important to note that all segments are "Mandatory" within the 203 transaction set

4.3 Example Transaction Set

Note Number	Name	Explanation
1	Transaction Set Identifier	Uniquely identifies the transaction set. For ANSI ASC X12 transaction sets, this is a three-digit number assigned by the standards organization.
2	Transaction Set Title	The corresponding name of the transaction set.
3	Functional Group Identifier	Each transaction set is included in a specific collection of related transaction sets called a functional group. The functional group is identified using a two-letter identifier, which is assigned by X12.
4	Introduction	This describes the business purpose and scope of use of the transaction set. The words, "Draft Standard for Trial Use" simply means that the transaction set has been approved by the ASC X12 Subcommittee of ANSI, but has not yet been approved by ANSI. The ANSI approval process happens once every seven years.
5	Heading	This identifies the header information for the transaction set.
6	Page Number	This column indicates the page number in the transaction set map where the segment can be found.
7	Position Number	The Position Number indicates the position of the segment within the transaction set. Transaction set segments are ordered sequentially from top to bottom, beginning with "010."
8	Segment ID	Segment ID is an identifier of information in a transaction set. A transaction set is made up of segments; segments are made up of data elements. Each segment has a two-to-three-letter identifier, assigned by X12.
9	Name	This is the name of the segment corresponding to its identifier. The name describes the type of information the segment carries.
10	Requirement Designator	This is a one-character code indicating the need for the data segment to appear in the data stream of the transmission. The code "M" means that the segment is mandatory and the code "O" means that the segment is optional.
11	Maximum Use	The segments in a transaction set may be repeated. The Maximum Use number indicates the number of allowable occurrences for that segment.
12	Loop Repeat	In the transaction set maps, a bracket highlights the segments included in a loop. Within each bracket, the number of times the loop is permitted to occur is shown as the Loop Repeat number. If the terminology ">1" is used, it means that the loop may repeat an unlimited number of times.
13	Notes and Comments	For each transaction set, there may be specific information about the intended use of a segment. These instructions are very important for understanding how to use the transaction set, and are annotated within the transaction set and explained below it. For example, n1 refers to the first note in the Transaction Set Notes (See Note Number 18)
14	Detail	This identifies the detail information for the transaction set.
15	Loop ID	The Loop ID identifies the first segment appearing in the loop.
16	Loop Bracket	The segments included in a loop are enclosed in a bracket.
17	Nested Loop	A Nested Loop is a loop within a loop.
18	Transaction Set Notes	These are the footnotes containing specific information about how a particular segment should be used within the transaction set. (See Note Number 13)

Segment Notes

Note Number	Name	Explanation
19	Segment	A data segment is an intermediate unit of information in a transaction set. A transaction set is made up of segments; segments are made up of data elements. Each data segment has a two to three-letter identifier, assigned by X12, known as the Segment ID. The name of the segment corresponds to its identifier, and describes the type of information the segment carries. (See Note Numbers 8 and 9)
20	Position	This indicates the position of the segment within the transaction set. Transaction set segments are ordered sequentially from top to bottom, beginning with "010." (See Note Number 7)
21	Loop	Within the segment, this indicates whether this particular segment falls within a loop, and if so, provides the loop ID. (See Note Number 15)
22	Level	The level shows whether a particular segment is located in the Heading or Detail Section. (See Note Numbers 5 and 14)
23	Usage	This indicates whether the segment is mandatory or optional. (See Note Number 10)
24	Maximum Use	The segments in a transaction set may be repeated. When a segment is repeated, it may have a specified total allowable number of occurrences at a specific position within the transaction set. The Maximum Use number indicates the number of allowable occurrences. (See Note Number 11)
25	Purpose	This describes how a segment is generally used. If there are specific intentions for the use of a segment for a particular transaction set, the segment will be annotated, and this usage instruction will appear beneath the transaction set. (See Note Number 26)
26	Notes	This provides additional information about the segments in the transaction set and elements within the segment.
27	Data Element Summary	A segment is made up of a collection of related data elements. The data elements, and their descriptions, are listed under the heading, "Data Element Summary."
28	Reference Designator	Like the position number of a segment within a transaction set, the Reference Designator identifies the relative position of the data element within the segment. The data elements are numbered sequentially, beginning with 01, and take the segment ID as a prefix. (See Note Number 7)
29	Data Element	The Data Element is the smallest unit of information in the X12 standard. Each Data Element has a one-to-four-digit reference number assigned by X12.
30	Name	Each Data Element has a Name corresponding to its ID number. Below the name of the Data Element is the Data Element Definition, identifying the way this Data Element is used.
31	Attributes	Like data segments, Data Elements have specific characteristics, called attributes, which are presented as a set of three codes. The first attribute indicates whether the data element is mandatory or optional. The second attribute identifies the data element type: Numeric (N0) Decimal Number (R) Identifier (ID) String (AN) Date (DT) Time (TM) The third attribute indicates the minimum and maximum number of characters of the Data Element.
32	Data Element Code Value	Depending on the segment, there will be a list of the data element code values that can be used for a particular data element.
33	Code Value Description	The description of the code value is listed along with its identifier.
34	Additional Guidance	This is additional guidance about how you will make the connection between the current Ginnie Mae flat file format for loan information, and the 203 transaction set. This additional information may not be provided for all elements.

1                                                                                           2 203 Secondary Mortgage Market Investor Report 3                                                                Functional Group ID= MH 4 Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Secondary Mortgage Market Investor Report Transaction Set (203) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used for the transfer and reporting of mortgage servicing information between mortgage servicers, mortgage service bureaus, and secondary mortgage market organizations.   5 Heading:

6	7	8	9	10	11	12	13
Page No.	Pos. No.	Seg. ID	Name	Req. Des.	Max. Use	Loop Repeat	Notes and Comments
3	010	ST	Transaction Set Header	M	1
4	020	BGN	Beginning Segment	M	1
6	030	DTP	Date or Time or Period	M	1		n1
7	040	REF	Reference Identification	M	1		n2

14

Detail:

Page

Pos.

Seg.

Req.

Loop

Notes and

No.

No.

ID

Name

Des.

Max.Use

Repeat

Comments

16

15

LOOP ID - LX

>1

8

010

LX

Assigned Number

M

1

9

020

REF

Reference Identification

M

2

n3

LOOP ID - RLT

>1

10

050

RLT

Real Estate Loan Type

M

1

13

060

DTP

Date or Time or Period

M

1

n4

14

070

AMT

Monetary Amount

M

2

n5

16

090

INT

Interest

M

1

17

110

NX2

Real Estate Property ID Component

M

4

17

LOOP ID - N1

1

19

120

N1

Name

M

1

21

130

N2

Additional Name Information

M

1

22

140

DTP

Date or Time or Period

M

2

n6

23

150

AMT

Monetary Amount

M

2

n7

25

160

YNQ

Yes/No Question

M

1

n8

26

190

SE

Transaction Set Trailer

M

1

18 Transaction Set Notes 1. The DTP segment states the Reporting CycleDate. 2. The REF segment indicates the Servicer or Issuer Institution Number. 3. The REF segment is used to identify Sub-Servicer, Pool, Document Custodial Note Holder or Issuer. 4. The DTP segment is used to state the Last Paid Installment Date and Date of Last Payment Received. 5. The AMT segment is used to report amounts such as Actual or Scheduled Unpaid Principal Balance, Principal and Interest Due to Investor and Current Principal and Interest, Prepayment Penalties. 6. The DTP segment is used to identify the Original Maturity Date and the Date of First Payment. 7. The AMT segment is used to state the Original Principal Balance and the Tax & Insurance Escrow Fund Balance. 8. The YNQ segment determines whether or not Foreclosure proceedings have begun on the loan. A 'Y' indicates proceedings have begun.

19	Segment:	STTransaction Set Header
20	Position:	010
21	Loop:
22	Level:	Heading
23	Usage:	Mandatory
24	Max Use:	1
25	Purpose:	To indicate the start of a transaction set and to assign a control number
26	Notes:	One ST - SE loop is required for each issuer.

27 Data Element Summary

	28	29	30					31
	Ref. Des.	Data Element	Name					Attributes
	ST01	143	Transaction Set Identifier Code					M ID3/3
			Code uniquely identifying a Transaction Set
			32 203		33 X12.340 Secondary Mortgage Market Investor Report
	ST02	329	Transaction Set Control Number					M AN4/9
			Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
			34 This control number is assigned by your translation software. This element is not reported in the Monthly Loan Level Submission, but is required for the EDI Monthly Loan Level Submission.

Ginnie Mae Transaction Set Maps: Envelope (PDF) 203 Transaction Set (PDF) 997 Transaction Set (PDF)

If you have any questions about our EDI program, please e-mail Ginnie Mae's EDI Coordinator or call the Ginnie Mae EDI Hotline at 1-888-GINNIE4 Option 1.

Return to the Table of Contents