Part 5.3 CUR - Currency of 850 - Purchase Order

Currency

		Entity Identifier Code		US Dollars
CUR	*	BY	*	USD	~
Req.		M		M
Type		ID		ID
MIN/MAX		2/3		3/3

Entity Identifier Code
US Dollars

Part 5.2 BEG - Beginning Segment of 850 - Purchase Order

Beginning Segment for Shipping Schedule/ Production Sequence

Transaction Set Purpose Code - The code could be changed based on the requirement

• 00 - Original Order
• 01 - Change Order
• 02 - Cancellation Order

Others - Purchase Order Type. It will depend on the order type.

• SA - Standard Alone Order
• SO - Shipping Order

Purchase Order Number - It is Very important information for the business document or transaction set. Identifying number for Purchase Order Assigned by the ordered/purchaser. Without 856, The purchase order number will be mentioned in all the business document or transaction set between two trading partners.

Purchase Order Date - It is a mandatory element in the purchase order document. It’s format CC/YY/MM/DD 

Acknowledgment Type - Based on this information the receiver will send an Acknowledgment to the sender. 

Here, NA - No Acknowledgement Needed.

Part 5.1 Purchase Order - 850

Header level Information

Pos. No.	Segment ID	Name	Description	Reg.
010	ST	Transaction Set Header	Functional Group ID Maximum Uses - 1	M
020	BEG	Beginning Segment for Purchase Order	It will depend on the Business Document or transaction set. For Example: - 850 - BEG 855 - BAK Maximum Uses - 1	M
040	CUR	Currency	What kind of currency the trading partner is going to use in this Business Document or transaction set.	M

Header loop ID - N1

Address Related Information

Whom to whom, the business document is exchanging.

Pos. No.	Segment ID	Name	Description	Reg.
310	N1	Name	Whom to whom, the business document is exchanging.	M
330	N3	Address Information		O
340	N4	Geographical Location		O
360	PER	Administrative Contract		O
	DTM	Date and Time	Only a few customers are using this segment for date and time.	O

Item Level

Pos. No.	Segment ID	Name	Description	Reg.
010	PO1	Baseline Item Data	It holds the business logic. It holds all kind of information about Item, Qty, Price, and other order level information about the business documents or transaction set	M
100	REF	Reference Identification		M
295	SCH	Line Item Schedule	It is pcs of information about the business document. It will hold all kind of delivery related information (Qty, Date & Schedule Time)	M

Summary 

Pos. No.	Segment ID	Name	Description	Reg.
010	CTT	Transaction Totals		O
020	SE	Transaction Set Trailer		M

Part 2.2 SFG - Sterling file gateway

SFG - Sterling file gateway
Sterling File Gateway is an application for transferring files between trading partners by using different protocols, conventions for naming files, and file formats. Sterling File Gateway uses the Sterling B2B foundation, which includes IBM® Sterling B2B Integrator, Sterling Standards, and the Sterling platform. The capabilities that are delivered are like the features found in Advanced File Transfer and IBM Sterling Connect: Enterprise® for UNIX, plus new functionality.

SFG (Sterling file gateway) version - 2.2
Role of the partner in myFileGateway
Partners can be internal or external.

Partner users can: 

• Upload files to myFileGateway
• Download files from myFileGateway
• View the status of file transfers they participate in SFG
• Choose events to be notified about when the events occur
• Manage their own password 
• Generate reports

SFG - Sterling File Gateway

• Production -------- Sender file
• Consumer ---------- Receiver File
• Static Route ------ 
• Document Route ----

Part 4.9 Loop

What is a Loop?
Loops are a group of two or more related segments that repeat.

What are the types in Loops?

• Bounded explicit loops.
• Unbounded implicit loops.
• Hierarchical explicit nested loops.

What is a Bounded loop?

• Bounded or explicit loops are identified with segments that specify the beginning and end of looping structure in the data.

What is an Unbounded loop?

• Unbounded or implicit loops are identified by the first segment in the loop and have no special segments for loop definition. 

What do you know about HL segments?

• Hierarchical Level segments indicate parent-child relationships among occurrences.
• HL segments identify dependencies of hierarchical level data.
• HL segments identify explicit nested loops within a transaction.

Mention the elements in the HL segment.

• HL01 – ID Number (Usually “HL Counter”)
• HL02 - Parent ID (HL01)
• HL03 – Level Code (Identifies Level)
• HL04 – Child Code (0 = no children, 1 = children)

The requirement of valid EDI file (ANSI X12)

List of requirements -

• The first line will start with three letters: “ISA”.
• ISA 13th element should match with IEA 2nd element.
• ISA Segment’s length is 106 bytes with 16 Elements.
• The second line will start with "GS”.
• GS 6th element should match with GE 2nd element.
• GS Segment’s length is 24 bytes with 8 Elements.
• The third line will start with "ST”.
• ST 2nd element should match with SE 2nd element.
• The header and trailer controller number will be the same.
• The number of the segment between ST & SE, including ST, & SE will have to match with the SE 1st elements. 
• The number of the Functional Group (GS/GE) will have to match with IEA 1st Element.
• The number of Functional Groups can be maximum up to 99999 times with same Functional Group ID in an Interchange Envelope.
• The number of Transaction Sets can be maximum up to 99999 times with same Transaction Set ID in a Functional Group.

Part 4.8 IEA - Interchange Control trailer

IEA - Interchange Control trailer

• It has 2 elements with 21 bytes (varies).

List of IEA Element

1. Element 1 - A number of Functional Group Header.
2. Element 2 - Interchange Controller Number.
• It will have to match with ISA 13th Elements.

Part 4.7 GE - Functional Group Trailer

GE - Functional Group Trailer

• It has 2 elements with 20 bytes (varies).

List of GE Element

• Element 1 - A number of Transaction Sets.
• Element 2 - Functional Controller Number.
• It will have to match with GS 6th Elements.