814 General Request, Response or Confirmation

Functional Group ID=GE

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the General Request, Response or Confirmation Transaction Set (814) for use within the context of an Electronic Data Interchange (EDI) environment. This standard can be used to request actions to be performed, to respond to a request for actions to be performed or to confirm information related to actions performed.

Notes:

This Implementation Convention is used to transmit Line of Accounting (LOA) and Transportation Account Code (TAC) information from the Transportation Global Edit Table (TGET) to the DoD Third Party Payment System - Transportation (TPPS-T).  LOA/TACs populate the Chart of Accounts in TPPS-T, which is U.S. Bank's Syncada system.	

Heading:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
M	010	ST	Transaction Set Header	M	1									
M	020	BGN	Beginning Segment	M	1									
Not Used	030	CUR	Currency	O	1									
			LOOP ID - FA1			>1								
Not Used	035	FA1	Type of Financial Accounting Data	O	1									
Not Used	036	FA2	Accounting Data	M	>1									
														
			LOOP ID - N1			>1								
Not Used	040	N1	Name	O	1		n1							
Not Used	050	N2	Additional Name Information	O	2									
Not Used	060	N3	Address Information	O	2									
Not Used	070	N4	Geographic Location	O	1									
Not Used	080	PER	Administrative Communications Contact	O	>1									
Not Used	090	REF	Reference Identification	O	>1									
Not Used	100	DTM	Date/Time Reference	O	>1									

Detail:

	Pos.	Seg.		Req.		Loop	Notes and
	No.	ID	Name	Des.	Max.Use	Repeat	Comments	
			LOOP ID - LIN			>1								
	010	LIN	Item Identification	O	1									
Not Used	020	ASI	Action or Status Indicator	O	1									
Not Used	030	REF	Reference Identification	O	>1									
	040	DTM	Date/Time Reference	O	>1									
Not Used	050	CUR	Currency	O	1									
Not Used	060	AMT	Monetary Amount	O	>1									
Not Used	070	PM	Electronic Funds Transfer Information	O	1									
			LOOP ID - FA1			>1								
Must Use	075	FA1	Type of Financial Accounting Data	O	1									
M	076	FA2	Accounting Data	M	>1									
														
			LOOP ID - NM1			>1								
Not Used	080	NM1	Individual or Organizational Name	O	1		n2							
Not Used	090	N2	Additional Name Information	O	2									
Not Used	100	N3	Address Information	O	2									
Not Used	110	N4	Geographic Location	O	1									
Not Used	120	PER	Administrative Communications Contact	O	>1									
Not Used	130	REF	Reference Identification	O	>1									
Not Used	140	DTM	Date/Time Reference	O	>1									
														
M	150	SE	Transaction Set Trailer	M	1									

Transaction Set Notes

1.	The N1 loop is used to identify the transaction sender and receiver.
2.	The NM1 loop is used to identify the parties associated with the individual line item (LIN), such as an individual consumer in a consolidated third party Consumer Service Provider transaction.

	Segment:	ST Transaction Set Header
	Position:	010
	Loop:
	Level:	Heading
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the start of a transaction set and to assign a control number
	Syntax Notes:
	Semantic Notes:	1	The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
	Comments:
	   Business Rules:	Variable Name: STST

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	ST01	143	Transaction Set Identifier Code	M		ID 3/3	
	Code uniquely identifying a Transaction Set	
 	814		General Request, Response or Confirmation	
M	ST02	329	Transaction Set Control Number	M		AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set	

	Segment:	BGN Beginning Segment
	Position:	020
	Loop:
	Level:	Heading
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the beginning of a transaction set
	Syntax Notes:	1	If BGN05 is present, then BGN04 is required.
	Semantic Notes:	1	BGN02 is the transaction set reference number.
		2	BGN03 is the transaction set date.
		3	BGN04 is the transaction set time.
		4	BGN05 is the transaction set time qualifier.
		5	BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	BGN01	353	Transaction Set Purpose Code	M		ID 2/2	
	Code identifying purpose of transaction set	
 	00		Original	
 	04		Change	
M	BGN02	127	Reference Identification	M		AN 1/30	
	Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier	
	Use 'GLCHARTID'	
M	BGN03	373	Date	M		DT 8/8	
	Date expressed as CCYYMMDD	
	System Date	
X	BGN04	337	Time	X		TM 4/8	
X	BGN05	623	Time Code	O		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	BGN06	127	Reference Identification	O		AN 1/30	
X	BGN07	640	Transaction Type Code	O		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	BGN08	306	Action Code	O		ID 1/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	BGN09	786	Security Level Code	O		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	

	Segment:	LIN Item Identification
	Position:	010
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	1
	Purpose:	To specify basic item identification data
	Syntax Notes:	1	If either LIN04 or LIN05 is present, then the other is required.
		2	If either LIN06 or LIN07 is present, then the other is required.
		3	If either LIN08 or LIN09 is present, then the other is required.
		4	If either LIN10 or LIN11 is present, then the other is required.
		5	If either LIN12 or LIN13 is present, then the other is required.
		6	If either LIN14 or LIN15 is present, then the other is required.
		7	If either LIN16 or LIN17 is present, then the other is required.
		8	If either LIN18 or LIN19 is present, then the other is required.
		9	If either LIN20 or LIN21 is present, then the other is required.
		10	If either LIN22 or LIN23 is present, then the other is required.
		11	If either LIN24 or LIN25 is present, then the other is required.
		12	If either LIN26 or LIN27 is present, then the other is required.
		13	If either LIN28 or LIN29 is present, then the other is required.
		14	If either LIN30 or LIN31 is present, then the other is required.
	Semantic Notes:	1	LIN01 is the line item identification
	Comments:	1	See the Data Dictionary for a complete list of IDs.
		2	LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
>>	LIN01	350	Assigned Identification	O		AN 1/20	
	Alphanumeric characters assigned for differentiation within a transaction set	
	Use '1' for the first LOA/TAC, and increment by one for each additional LOA/TAC	
M	LIN02	235	Product/Service ID Qualifier	M		ID 2/2	
	Code identifying the type/source of the descriptive number used in Product/Service ID (234)	
 	GE		Generic Name Description	
M	LIN03	234	Product/Service ID	M		AN 1/48	
	Identifying number for a product or service	
	Accounting Code Name	
X	LIN04	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN05	234	Product/Service ID	X		AN 1/48	
X	LIN06	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN07	234	Product/Service ID	X		AN 1/48	
X	LIN08	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN09	234	Product/Service ID	X		AN 1/48	
X	LIN10	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN11	234	Product/Service ID	X		AN 1/48	
X	LIN12	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN13	234	Product/Service ID	X		AN 1/48	
X	LIN14	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN15	234	Product/Service ID	X		AN 1/48	
X	LIN16	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN17	234	Product/Service ID	X		AN 1/48	
X	LIN18	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN19	234	Product/Service ID	X		AN 1/48	
X	LIN20	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN21	234	Product/Service ID	X		AN 1/48	
X	LIN22	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN23	234	Product/Service ID	X		AN 1/48	
X	LIN24	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN25	234	Product/Service ID	X		AN 1/48	
X	LIN26	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN27	234	Product/Service ID	X		AN 1/48	
X	LIN28	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN29	234	Product/Service ID	X		AN 1/48	
X	LIN30	235	Product/Service ID Qualifier	X		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	LIN31	234	Product/Service ID	X		AN 1/48	

	Segment:	DTM Date/Time Reference
	Position:	040
	Loop:	LIN        Optional
	Level:	Detail
	Usage:	Optional
	Max Use:	>1
	Purpose:	To specify pertinent dates and times
	Syntax Notes:	1	At least one of DTM02 DTM03 or DTM05 is required.
		2	If DTM04 is present, then DTM03 is required.
		3	If either DTM05 or DTM06 is present, then the other is required.
	Semantic Notes:
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	DTM01	374	Date/Time Qualifier	M		ID 3/3	
	Code specifying type of date or time, or both date and time	
 	150		Service Period Start	
	Use for LOA Effective Date	
 	151		Service Period End	
	1. Use for LOA Expiration Date
2. If the LOA status is 'U' (Unexpired) and no end date is provided, use the current FY end date.
3. If the LOA status is 'E' (Expired) and the end date is greater than the current date, or if no end date is provided, use the current date plus 2 days. 	
 	154		Adjustment Period Start	
	Use for TAC Begin Use Date	
 	155		Adjustment Period End	
	1. Use for TAC End Use Date
2. If the TAC status is 'A' (Active) and no end date is provided, use the current FY end date.
3. If the TAC status is 'I' (Inactive), or no end date is provided, use the current date plus 2 days.	
>>	DTM02	373	Date	X		DT 8/8	
	Date expressed as CCYYMMDD	
X	DTM03	337	Time	X		TM 4/8	
X	DTM04	623	Time Code	O		ID 2/2	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	DTM05	1250	Date Time Period Format Qualifier	X		ID 2/3	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	DTM06	1251	Date Time Period	X		AN 1/35	

	Segment:	FA1 Type of Financial Accounting Data
	Position:	075
	Loop:	FA1        Optional (Must Use)
	Level:	Detail
	Usage:	Optional (Must Use)
	Max Use:	1
	Purpose:	To specify the organization controlling the content of the accounting citation, and the purpose associated with the accounting citation
	Syntax Notes:
	Semantic Notes:	1	FA101 Identifies the organization controlling the assignment of financial accounting information.
		2	FA102 Identifies the purpose of the accounting allowance or charge information.
	Comments:

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	FA101	559	Agency Qualifier Code	M		ID 2/2	
	Code identifying the agency assigning the code values	
 	ZZ		Mutually Defined	
	Transportation Service Code	
X	FA102	1300	Service, Promotion, Allowance, or Charge Code	O		ID 4/4	
	Refer to 004010 Data Element Dictionary for acceptable code values.	
X	FA103	248	Allowance or Charge Indicator	O		ID 1/1	
	Refer to 004010 Data Element Dictionary for acceptable code values.	

	Segment:	FA2 Accounting Data
	Position:	076
	Loop:	FA1        Optional (Must Use)
	Level:	Detail
	Usage:	Mandatory
	Max Use:	>1
	Purpose:	To specify the detailed accounting data
	Syntax Notes:
	Semantic Notes:
	Comments:
Notes:		Use this segment to identify the various components of the line of accounting.   If TA - Transportation Account Code (TAC) is provided, no line of accounting is needed.

1.  Use codes from the following list when providing a segmented DoD Standard Line of Accounting (SLOA):

15     Interdivisional Work Authorization
89     Budget Line Item Identification
90     Project/Task
A1    Department Indicator
A2    Transfer From Department
A4    Basic Symbol Number
A7    Subhead or Limit
AI    Activity Identifier
BE    Business Event Type Code
C3    Budget Restriction
CC    Cost Center Identifier
F1     Object Class
FA    Functional Area
FC    Funding Center Identifier
FT    Funding Type
H1    Cost Code
IA     Security Cooperation Implementing Agency
L1     Accounting Installation Number
N1    Transaction Type
P1     Disbursing Station Number
P5     Foreign Military Sales (FMS) Line Item Number
S1     Security Cooperation Customer Code
S2     Security Cooperation Case Designator
WO   Work Order Number
YB    Beginning Period of Availability
YE    Ending Period of Availability

Additional information may be found on the Under Secretary of Defense (Comptroller)/Office of the Deputy Chief Financial Officer (ODCFO) website (https://comptroller.defense.gov/odcfo/) under Standard Financial Information Structure (SFIS).

2.  Use codes from the following list when providing a segmented DoD legacy Line of Accounting (LOA):

A1     Department Indicator
A2     Transfer From Department
A3     Fiscal Year Indicator
A4     Basic Symbol Number
A5     Sub-Class
A6     Sub-Account Symbol
B1     Budget Activity Number
B2     Budget Sub-activity Number
B3     Budget Program Activity
B4     Program Year Indicator
C1     Program Element
C2     Project Task or Budget Subline
D1     Defense Agency Allocation Recipient
D4     Component Sub-allocation Recipient
D6     Sub-allotment Recipient
D7     Work Center Recipient
E1     Major Reimbursement Source Code
E2     Detail Reimbursement Source Code
E3     Customer Indicator
F1     Object Class
F3     Government or Public Sector Identifier
F4     Country Code
G1     Program or Planning Code
G2     Special Interest Code or Special Program Cost Code
H1     Cost Code
H3     Cost Allocation Code
H4     Classification Code
I1      Abbreviated DoD Budget and Accounting Classification Code
J1      Document or Record Reference
L1      Accounting Installation Number
M1     Local Installation Data
N1     Transaction Type
P5      Foreign Military Sales (FMS) Line Item Number
P6      Contract Payment Notice (CPN) Recipient Indicator	

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	FA201	1196	Breakdown Structure Detail Code	M		ID 2/2	
	Codes identifying details relating to a reporting breakdown structure tree	
 	15		Interdivisional Work Authorization	
	Work to be performed within the same company, but at a different division. Coding allows tracking of the costs associated with the other division (because indirect costs may be different, etc.)	
	For a SLOA, use to indicate the three position Sub Account (SFIS A4).  Indicates the relationship to the Main Account (SFIS A3).  Example:  002.	
 	89		Budget Line Item Identification	
	For a SLOA, use to indicate the one to sixteen position Budget Line Item (SFIS B4).  For MilPers, value will be Budget Sub-Activity (BSA) plus Budget Line Item (BLI).  Further sub-divides the Treasury Account Fund Symbol below sub-activity.  Example:  111.	
 	90		Project/Task	
	For a SLOA, use to indicate the one to twenty-five position Project Identifier (SFIS CA4).	
 	A1		Department Indicator	
	1.  For a legacy LOA, use to indicate the two position department code.

2.  For a SLOA, use to indicate the three position Department Regular (SFIS A1).  Example: "021" for Army, "017" for Navy, "057" for Air Force, "097" for ODOs.	
 	A2		Transfer from Department	
	1.  For a legacy LOA, use to indicate the two position transfer from department.

2.  For a SLOA, use to indicate the three position Department Transfer (SFIS A2).  A transfer of obligation authority from DoE; aka Allocation Transfer Agency Identifier (ATA).  Example:  089.	
 	A3		Fiscal Year Indicator	
	For a legacy LOA, use to indicate the eight position fiscal year.  The first four positions represent the first year the funds are available and the last four positions represent the last year the funds are available.  Example:  Year one 1999, year two 2000 would be cited as "19992000".	
 	A4		Basic Symbol Number	
	1. For a legacy LOA, use to indicate the four position code assigned by the Treasury that indicates the type of funds for the appropriation.

2. For a SLOA, use to indicate the four position Main Account (SFIS A3).  Synonymous with Basic Symbol and Appropriation Symbol.  Example:  4930.	
 	A5		Sub-class	
	For a legacy LOA, use to indicate the four position numeric suffix that identifies the subdivision of funds that restricts the amount or use of funds.	
 	A6		Sub-Account Symbol	
	For a legacy LOA, use to indicate the two position Fund Code or Material Category Code.	
 	A7		Subhead or Limit	
	For a SLOA, use to indicate the four position Sub-Allocation (SFIS B12).  Use of this data element is exclusive to the sub-allocation purposes, useful for Financial Reporting.  Example:  2504.	
 	AI		Activity Identifier	
	For a SLOA, use to indicate the one to sixteen position Activity Identifier (SFIS CA5).	
 	B1		Budget Activity Number	
	For a legacy LOA, use to indicate the two position Operation Agency Code that indicates the issuing organization.	
 	B2		Budget Sub-activity Number	
	For a legacy LOA, use to indicate the Allotment Serial Number that indicates the distribution of funds.	
 	B3		Budget Program Activity	
	For a legacy LOA, use to indicate the six position activity address code of the card holder.	
 	B4		Program Year Indicator	
	For a legacy LOA, use to indicate the one position Program Year.	
 	BE		Business Event Type Code	
	For a SLOA, use to indicate the four to eight position Business Event Type Code (SFIS T20).  Replaces Transaction Codes. Example: "DISB" for disbursement.	
 	C1		Program Element	
	For a legacy LOA, use to indicate the program element code.	
 	C2		Project Task or Budget Subline	
 	C3		Budget Restriction	
	For a SLOA, use to indicate the one position Availability Type (SFIS A24).  Example:  "X" for no-year TAS.	
 	CC		Cost Center Identifier	
	For a SLOA, use to indicate the one to sixteen position Cost Center Identifier (SFIS CA3).	
 	D1		Defense Agency Allocation Recipient	
 	D4		Component Sub-allocation Recipient	
	For a legacy LOA, use to indicate the Job Order/Work Center Order Number for assigning cost to a specific project.	
 	D6		Sub-allotment Recipient	
	For a legacy LOA, use to indicate the one position Sub-allotment Recipient.	
 	D7		Work Center Recipient	
	For a legacy LOA, use to indicate the six position Work Center Recipient.	
 	E1		Major Reimbursement Source Code	
 	E2		Detail Reimbursement Source Code	
 	E3		Customer Indicator	
	For a legacy LOA, use to indicate the six position customer identifier who has requested the goods or services.	
 	F1		Object Class	
	1. For a legacy LOA, use to indicate the Object Class, Element of Resource or the Element of Expense.

2. For a SLOA, use to indicate the three to six position Object Class (SFIS B6).  Example:  252.	
 	F3		Government or Public Sector Identifier	
	For a legacy LOA, use to indicate the government or public source providing the goods or services.	
 	F4		Country Code	
 	FA		Functional Area	
	For a SLOA, use to indicate the one to sixteen position Functional Area (SFIS CA15).	
 	FC		Funding Center Identifier	
	For a SLOA, use to indicate the one to sixteen position Funding Center Identifier (SFIS CA1).	
 	FT		Funding Type	
	For a SLOA, use to indicate the one position Reimbursable Flag (SFIS A9). Example:  "D" for direct; "R" for reimbursable.	
 	G1		Program or Planning Code	
 	G2		Special Interest Code or Special Program Cost Code	
 	H1		Cost Code	
	1. For a legacy LOA, use to indicate the Cost Code.

2. For a SLOA, use to indicate the one to fifteen position Cost Element Code (SFIS CA6).	
 	H3		Cost Allocation Code	
 	H4		Classification Code	
 	I1		Abbreviated Department of Defense (DoD) Budget and Accounting Classification Code (BACC)	
	For a legacy LOA, use to indicate the shorthand elements of the accounting classification.	
 	IA		Security Cooperation Implementing Agency Code	
	For a SLOA, use to indicate the one position Security Cooperation Implementing Agency (IA) Code (SFIS T27).  Identifies the U.S. MILDEP or agency which is executing the FMS sale on behalf of the U.S. Government.  Example:  "B" for Army, "P" for Navy, "D" for Air Force.	
 	J1		Document or Record Reference Number	
	For a legacy LOA, use to indicate the Standard Document Number.	
 	K6		Accounting Classification Reference Code	
 	L1		Accounting Installation Number	
	1. For a legacy LOA, use to indicate the Accountable Station Number. The Accountable Station Code is the Fiscal Station Number (FSN) of both the Army and the Office of the Secretary of Defense (OSD), the Authorization Accounting Authority (AAA) of the Navy, or the Accounting and Disbursing Station Number (ADSN) used by the Air Force.  This code is used whether or not the application can generate the individual components of the LOA.

2. For a SLOA, use to indicate the six position Agency Accounting Identifier (SFIS O3). Defined by the Comptroller and identifies the accounting system responsible for the accounting event. Example: "021001" for DFAS Indianapolis (GFEBS).	
 	M1		Local Installation Data	
	Use to indicate the Installation Facilities System Number.	
 	N1		Transaction Type	
	1.  For a legacy LOA, use to indicate the transaction type code.

2.   For a SLOA, use to indicate the two position Sub Class (SFIS A7).  Grouping of a transaction type aka Sub-level Prefix (SP).  Example:  "46" for Payments from Current Appropriations for Obligations of Closed Accounts.	
 	P1		Disbursing Station Number	
	For a SLOA, use to indicate the four to eight position Agency Disbursing Identifier Code (SFIS O2).  Synonymous with Treasury DSSN definitions for each disbursing office.  Example:  1700.	
 	P5		Security Cooperation Case Line Item Identifier	
	1. For a legacy LOA, use to indicate the FMS Case Number, Country Code, and FMS line number.

2. For a SLOA, use to indicate the three position Security Cooperation Case Line Item Identifier (SFIS T23).  Identifies a detailed line-item requirement.  Example:  001.	
 	P6		Contract Payment Notice (CPN) Recipient Indicator	
	Use to indicate the 8 position CPN Recipient, Organization Code.	
 	S1		Security Cooperation Customer Code	
	For a SLOA, use to indicate the two to three position Security Cooperation Customer Code (SFIS T21).  The country, customer, or U.S. program receiving the product/service.  Example:  "EI" for Ireland, "F1" for F-16 Co-production, "B4" for Section 1206.	
 	S2		Security Cooperation Case Designator	
	For a SLOA, use to indicate the three to four position Security Cooperation Case Identifier (SFIS T22).  Identifies the FMS or Security Cooperation contractual sales agreement between countries.  Example:  UAK.	
 	TA		Transportation Account Code (TAC)	
	Identifies a financial instrument used to charge the cost of transporting a SHIPMENT-UNIT.  It is the specific code that represents the appropriate Service, Agency, or contractor account to be charged for the cost of transportation.	
 	WO		Work Order Number	
	For a SLOA, use to indicate the one to sixteen position Work Order Number (SFIS CA7).	
 	YB		Beginning Period of Availability Fiscal Year Date	
	For a SLOA, use to indicate the four position Beginning Period of Availability Fiscal Year Date (SFIS A27).  Example:  2012.	
 	YE		Ending Period of Availability Fiscal Year Date	
	For a SLOA, use to indicate the four position Ending Period of Availability Fiscal Year Date (SFIS A28).  Example:  2012.	
 	ZZ		Mutually Defined	
	Use this code in conjunction with code L1 when the individual components of the legacy LOA cannot be generated by the application.  When used, provide the legacy Line of Accounting (LOA) as cited on the contract, which should include the Accountable Station Number, identified by the use of code L1 in another iteration of this segment.	
M	FA202	1195	Financial Information Code	M		AN 1/80	
	Code representing financial accounting information	

	Segment:	SE Transaction Set Trailer
	Position:	150
	Loop:
	Level:	Detail
	Usage:	Mandatory
	Max Use:	1
	Purpose:	To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
	Syntax Notes:
	Semantic Notes:
	Comments:	1	SE is the last segment of each transaction set.

Data Element Summary
	Ref.	Data	
	Des.	Element	Name	Attributes
M	SE01	96	Number of Included Segments	M		N0 1/10	
	Total number of segments included in a transaction set including ST and SE segments	
M	SE02	329	Transaction Set Control Number	M		AN 4/9	
	Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set	
	Use the same Control Number cited in ST02