Purchase Order
Acknowledgment –
IMPLEMENTATION GUIDE
BSCP EDI 855 POA (POR) – X12 Version 4010
BOEING
Document Status
Document Name / Exostar Implementation Guide for BSCP – EDI 855 Purchase Order AcknowledgmentVersion / 1.4
Issue Date / May 3, 2017
Author / Ann Lamica
Description / An Implementation Guide for Aerospace and Defense industry Suppliers who want to deliver Purchase Order Acknowledgments in an Exostar EDI 855 Format.
Document Revision History
Version # / Date / Author’s Name / Segments Revised / Revisions Made1.0 / 11/27/2013 / Ann Lamica / New Guide / First publication of the Boeing BSCP - EDI 855 POA IG (POR)
1.1 / 4/30/2014 / Ann Lamica / GS & examples / Individual GS IDs have been assigned to each BBS. FA added to the Order Management Suite transaction list.
1.2 / 5/22/2015 / Ann Lamica / N9 / N902 documentation changed from Used to Must Use.
1.3 / 3/30/2017 / Ann Lamica / General Update Draft / Draft for the CAS 2017 implementation. Distributed to CAS suppliers to use for planning and design.
1.4 / 5/03/2017 / Ann Lamica / MSG segment, other Notes and examples / Final version for the CAS 2017 Implementation. Only substantive change from draft is a change to the maximum Supplier Message length in the N9 MSG segment from 3900 to 3700 characters. Other changes primarily for clarity for some notes and full transaction examples changed GS ID and PO numbers to be more representative of CAS only, previously some were for BDS.
Introduction
This Guide is designed for Suppliers who want to send Purchase Order Acknowledgments (known within Exostar as Purchase Order Responses) in the EDI X12 format to the Boeing Supply Chain Platform (BSCP). The Purchase Order Response (POR) is sent by a Boeing Supplier to Exostar in response to a Boeing Purchase Order. The POR will be posted to BSCP and forwarded to the appropriate Boeing Business System (BBS).
The EDI formats outlined in this Guide adhere to the Accredited Standards Committee (ASC) X12 standards for EDI, Version 4010. The overall structure of the EDI Purchase Order Acknowledgment (855 Transaction Set) is defined on the pages immediately after the Table of Contents. Following the Transaction Set are examples of a typical POR for every POR status covered by this Implementation Guide.
The subsequent pages of this Guide define the usage for each EDI segment and element used within the 855 Transaction Set. In addition to the EDI technical requirements, there are notes explaining Boeing’s usage and identifying any special requirements.
Although the one POR format is used by all Boeing Business Systems (BBS) which elect to receive integrated PORs from Suppliers, not all BBS want PORs and it will be a Supplier requirement that PORs are returned only when appropriate to the BBS. This may mean that a Supplier which is integrated with multiple BBS, may send PORs to one BBS but not another. Integrated PORs should also only be sent in response to integrated Purchase Orders received via Exostar.
The “User Option (Usage)” identifies Boeing specific requirements regarding a segment. When the segment is Mandatory within the standard then it will be marked as “Must Use”. If, however, the segment is Optional within the standard but it is required by Boeing then it is marked “Must Use” and Exostar considers it to be mandatory. If marked “Used” then it is considered optional or conditional based upon the type of response and the decision to send a POR will be dependent on the notes contained within this document. Treatment of the elements is similar and is denoted by the “Usage” column within the respective segment.
Some EDI elements will have specific EDI code values indicated in the Guide. If an element comes from an EDI code list and there is a small subset of the codes accepted by Exostar then those codes have been identified and defined by BBS. The Unit of Measurement (UOM) and several other values must be returned from the applicable Purchase Order. When so specified it is necessary that the values match in order for Exostar or Boeing to properly apply the POR.
For additional information about the usage of this Guide or contents, please contact Exostar. Exostar strongly recommends that the Supplier not undertake any mapping or development activities until the Supplier and Exostar have reviewed the Guide together.
Table of Contents
855Purchase Order Acknowledgment
ISAInterchange Control Header
GSFunctional Group Header
STTransaction Set Header
BAKBeginning Segment for Purchase Order Acknowledgment
PERAdministrative Communications Contact
N9Reference Identification
MSGMessage Text
N1Name
N1Name
PO1Baseline Item Data
ACKLine Item Acknowledgment
SCHLine Item Schedule
CTTTransaction Totals
SETransaction Set Trailer
GEFunctional Group Trailer
IEAInterchange Control Trailer
855 /Purchase Order Acknowledgment
Functional Group=PRPurpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.
Not Defined:
Pos / Id / Segment Name / Req / Max Use / Repeat / Notes / UsageISA / Interchange Control Header / M / 1 / Must use
GS / Functional Group Header / M / 1 / Must use
Heading:
Pos / Id / Segment Name / Req / Max Use / Repeat / Notes / Usage010 / ST / Transaction Set Header / M / 1 / Must use
020 / BAK / Beginning Segment for Purchase Order Acknowledgment / M / 1 / Must use
060 / PER / Administrative Communications Contact / O / 1 / Used
LOOP ID - N9 / 1
280 / N9 / Reference Identification / O / 1 / Used
290 / MSG / Message Text / O / 1000 / Used
LOOP ID - N1 / 1
300 / N1 / Name / O / 1 / Must use
LOOP ID - N1 / 1
300 / N1 / Name / O / 1 / Must use
Detail:
Pos / Id / Segment Name / Req / Max Use / Repeat / Notes / UsageLOOP ID - PO1 / 100000 / N2/010L
010 / PO1 / Baseline Item Data / O / 1 / N2/010 / Must use
LOOP ID - ACK / 1
270 / ACK / Line Item Acknowledgment / O / 1 / Must use
LOOP ID - SCH / 200 / N2/310L
310 / SCH / Line Item Schedule / O / 1 / N2/310 / Must use
Summary:
Pos / Id / Segment Name / Req / Max Use / Repeat / Notes / UsageLOOP ID - CTT / 1 / N3/010L
010 / CTT / Transaction Totals / O / 1 / N3/010 / Must use
030 / SE / Transaction Set Trailer / M / 1 / Must use
Not Defined:
Pos / Id / Segment Name / Req / Max Use / Repeat / Notes / UsageGE / Functional Group Trailer / M / 1 / Must use
IEA / Interchange Control Trailer / M / 1 / Must use
Boeing POR And POCR Usage Requirements:
Boeing Business Systems not notedbelow as actively using the integrated POR or POCR should not receive any integrated POR or POCR transactions from the Supplier in response to a PO or POC issued by those business systems. It will be necessary for the Supplier to be able to distinguish which Boeing PO’s and POC’s should receive an integrated response.
Responses will only be accepted for the current version of the order on BSCP, once an order has been updated responses referencing earlier versions of the document will be rejected and an email alert sent to the Supplier.
BCA ERPLN:
Not used by BCA ERPLN.
BGS SAP CAS MS:
The POR and POCR is required by CAS including the In Process status.
BDS:
BDS mayuse the integrated POR and POCR in the future
Example "Accepted" Purchase Order Response:
The BAK02 (AT) at the header and all lines in the ACK01(IA)are set to Accepted. No Supplier Message is needed as there are no exceptions.
ISA~00~ ~00~ ~01~599599599 ~ZZ~LIAEXOBOEINGT ~130629~0001~U~00401~000000381~0~T~^|
GS~PR~599599599~CASSAPBGS~20130629~0001~381~X~004010|
ST~855~0001|
BAK~11~AT~50021234567890~20130626~~~~788Z14A~20130629~OR|
PER~SU~Sally Supplier~EM~|
N1~BY~~92~e78ab758-78a0-1000-b1a4-0a1c0c090001|
N1~SE~~92~99ff9999-7960-1000-819c-0a1c0c099991|
PO1~10|
ACK~IA|
SCH~6~EA~~~ZZZ~20130710~~~~~~1|
PO1~20|
ACK~IA|
SCH~3~EA~~~ZZZ~20131015~~~~~~1|
SCH~4~EA~~~ZZZ~20131115~~~~~~2|
CTT~2~13|
SE~14~0001|
GE~1~381|
IEA~1~000000381|
Example "Accepted With Amendment" Purchase Order Response:
The following example contains one line (30) that is Accepted (ACK01 = IA)and two lines with Exceptions (ACK01 = IC). Please note that there is an N9 loop containing a Supplier Message which is required when one or more exceptions are present. The content of the "Supplier Message" only refers to the line(s) with exceptions. Because there is an exception the header levelBAK02 = AC (Accepted With Amendment is equivalent to Acknowledged with Exceptions onBSCP).
ISA~00~ ~00~ ~01~599599599 ~ZZ~LIAEXOBOEINGT ~130629~0001~U~00401~000000381~0~T~^|
GS~PR~599599599~CASSAPBGS~20130629~0001~381~X~004010|
ST~855~0001|
BAK~11~AC~50020123456789~20130626~~~~788Z14A~20130629~OR|
PER~SU~Sally Supplier~EM~|
N9~L1~Supplier Message|
MSG~Line10 Schedule Line 1 price should be $102 EA|
MSG~Line20 Schedule Line 2 reschedule to 121513|
N1~BY~~92~e78ab758-78a0-1000-b1a4-0a1c0c090001|
N1~SE~~92~99ff9999-7960-1000-819c-0a1c0c099991|
PO1~10|
ACK~IC|
SCH~6~EA~~~ZZZ~20130710~~~~~~1|
PO1~20|
ACK~IC|
SCH~3~EA~~~ZZZ~20131015~~~~~~1|
SCH~4~EA~~~ZZZ~20131115~~~~~~2|
PO1~30|
ACK~IA|
SCH~3~EA~~~ZZZ~20131015~~~~~~1|
SCH~4~EA~~~ZZZ~20131115~~~~~~2|
CTT~3~20|
SE~21~0001|
GE~1~381|
IEA~1~000000381|
Example "In Process" Purchase Order Response:
The BAK02 is marked as In Process (AH) at the Header and the ACK01 (IH) at each line is set to In Process. No Supplier Message is needed for this example as there are no exceptions.
ISA~00~ ~00~ ~01~599599599 ~ZZ~LIAEXOBOEINGT ~130629~0001~U~00401~000000381~0~T~^|
GS~PR~599599599~CASSAPBGS~20130629~0001~381~X~004010|
ST~855~0001|
BAK~11~AH~50022345678901~20130626~~~~788Z14A~20130629~OR|
PER~SU~Sally Supplier~EM~|
N1~BY~~92~e78ab758-78a0-1000-b1a4-0a1c0c090001|
N1~SE~~92~99ff9999-7960-1000-819c-0a1c0c099991|
PO1~1|
ACK~IH|
SCH~6~EA~~~ZZZ~20130710~~~~~~1|
PO1~2|
ACK~IH|
SCH~3~EA~~~ZZZ~20131015~~~~~~1|
SCH~4~EA~~~ZZZ~20131115~~~~~~2|
CTT~2~13|
SE~14~0001|
GE~1~381|
IEA~1~000000381|
POR Data Links to Other Documents:
This tableidentifies the Exostar Data Source from whicha POR elementmay originate. All elements may not be present on all PORs orused by all Boeing Business Systems (BBS).
Exostar Data Source
EDI 850 PO – X12 Version 4010 / Shared Elements
EDI 855 POA – X12 Version 4010
ISA07 – Interchange ID Qualifier (Receiver/Seller) / ISA05 – Interchange ID Qualifier (Sender/Seller)
ISA08 – Interchange Sender ID (Seller) / ISA06 – Interchange Sender ID (Seller)
ISA05 – Interchange ID Qualifier (Sender/Buyer) / ISA07 – Interchange ID Qualifier (Receiver/Buyer)
ISA06 – Interchange Receiver ID (Buyer) / ISA08 – Interchange Receiver ID (Buyer)
GS03 – Application Receiver’s Code (Seller) / GS02 – Application Sender’s Code (Seller)
GS02 – Application Sender’s Code (Boeing Business System Identification) / GS03 – Application Receiver’s Code (Boeing Business System Identification)
BEG03 – Purchase Order Number / BAK03 – Purchase Order Number
BEG05– Date (PO Date) / BAK04 – Date (PO Date)
N104 – BY Identification Code (Buyer MPID) / N104 – BY Identification Code (Buyer MPID)
N104 – SE Identification Code (Seller MPID) / N104 – SE Identification Code (Seller MPID)
PO101 – Assigned Identification (PO Line ID) / PO101 – Assigned Identification (PO Line ID)
SCH01 – Quantity / SCH01 – Quantity
SCH02 – UOM / SCH02 – UOM
SCH06 – Date (Requested Delivery Date) / SCH06 – Date (Requested Delivery Date)
SCH12 – Assigned Identification (Schedule Line Number) / SCH12 – Assigned Identification (Schedule Line Number)
Notes - Example Transactions:
The Boeing GS Receiver ID will vary depending on the Boeing Business System (BBS) for which the data is intended. The example(s) shown may not include all elements or segments required or may contain some not required for all transactions. Please refer to the details for each segment and element within this Implementation Guide.
Transaction Set Notes:
The following is a terminologycross-referencetovarious transactions within theExostar Order ManagementSuite. The most common usage in our Implementation Guides will be the Doc Type.
Doc Type / Name / EDI Transaction Set Identifier Code (ST01) / EDI Functional Identifier Code (GS01)
PO / Purchase Order / 850 / PO
POR / Purchase Order Response / 855 / PR
POC / Purchase Order Change / 860 / PC
POCR / Purchase Order Change Response / 865 / CA
ASN / Advanced Ship Notice / 856 / SH
INV / Invoice / 810 / IN
FA / Functional Acknowledgment / 997 / FA
BSCP EDI 855 Purchase Order Acknowledgment IG V1.4.ecs / 1 / Exostar LLC
Purchase Order Acknowledgment - 855 / X12V4010 / 5/3/2017
ISA /
Interchange Control Header
/ Pos: / Max: 1Not Defined - Mandatory
Loop: N/A / Elements: 16
User Option (Usage): Must use
Purpose: To start and identify an interchange of zero or more functional groups and interchange-related control segments
Element Summary:
Ref / Id / Element Name / Req / Type / Min/Max / UsageISA01 / I01 / Authorization Information Qualifier / M / ID / 2/2 / Must use
Code / Name
00 / No Authorization Information Present (No Meaningful Information in I02)
ISA02 / I02 / Authorization Information
Exostar:
Blank
/ M / AN / 10/10 / Must use
ISA03 / I03 / Security Information Qualifier / M / ID / 2/2 / Must use
Code / Name
00 / No Security Information Present (No Meaningful Information in I04)
ISA04 / I04 / Security Information
Exostar:
Blank
/ M / AN / 10/10 / Must use
ISA05 / I05 / Interchange ID Qualifier / M / ID / 2/2 / Must use
Code / Name
01 / Duns (Dun & Bradstreet)
12 / Phone (Telephone Companies)
14 / Duns Plus Suffix
ZZ / Mutually Defined
ISA06 / I06 / Interchange Sender ID
Exostar:
Supplier assigned Sender ID
/ M / AN / 15/15 / Must use
ISA07 / I05 / Interchange ID Qualifier / M / ID / 2/2 / Must use
Code / Name
ZZ / Mutually Defined
ISA08 / I07 / Interchange Receiver ID
Exostar:
Boeing's Receiver ID
/ M / AN / 15/15 / Must use
ISA09 / I08 / Interchange Date
Exostar:
Format YYMMDD
/ M / DT / 6/6 / Must use
ISA10 / I09 / Interchange Time
Exostar:
Format HHMM
/ M / TM / 4/4 / Must use
ISA11 / I10 / Interchange Control Standards Identifier / M / ID / 1/1 / Must use
Code / Name
U / U.S. EDI Community of ASC X12, TDCC, and UCS
ISA12 / I11 / Interchange Control Version Number / M / ID / 5/5 / Must use
Code / Name
00401 / Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA13 / I12 / Interchange Control Number
Exostar:
Unique interchange control number assigned by the Sender
/ M / N0 / 9/9 / Must use
ISA14 / I13 / Acknowledgment Requested / M / ID / 1/1 / Must use
Code / Name
0 / No Acknowledgment Requested
ISA15 / I14 / Usage Indicator / M / ID / 1/1 / Must use
Code / Name
P / Production Data
T / Test Data
ISA16 / I15 / Component Element Separator
Exostar:
^
/ M / 1/1 / Must use
Example Segment:
ISA~00~ ~00~ ~01~599599599 ~ZZ~LIAEXOBOEINGP ~130326~0001~U~00401~000000381~0~P~^|
Segment Notes:
Exostarcan accepta maximum number of 300 EDI transactions within a single file. This includes all transactions sent at the ISA, GS or ST levels.
Boeing Receiver IDs and Qualifiers:
Usage / ISA Qualifier / ISAReceiver ID
Production / ZZ / LIAEXOBOEINGP
Test / ZZ / LIAEXOBOEINGT
Delimiters:
Suppliers are requested to use the following EDI delimiters:
Exostar Delimiters / Segment Terminator / Element Separator / Sub-Element/Component Separator
Production / |(pipe) / ~ / ^
Test / | (pipe) / ~ / ^
BSCP EDI 855 Purchase Order Acknowledgment IG V1.4.ecs / 1 / Exostar LLC
Purchase Order Acknowledgment - 855 / X12V4010 / 5/3/2017
GS /
Functional Group Header
/ Pos: / Max: 1Not Defined - Mandatory
Loop: N/A / Elements: 8
User Option (Usage): Must use
Purpose: To indicate the beginning of a functional group and to provide control information
Element Summary:
Ref / Id / Element Name / Req / Type / Min/Max / UsageGS01 / 479 / Functional Identifier Code / M / ID / 2/2 / Must use
Code / Name
PR / Purchase Order Acknowledgement (855)
GS02 / 142 / Application Sender's Code
Exostar:
Supplier assigned Sender ID
/ M / AN / 2/15 / Must use
GS03 / 124 / Application Receiver's Code
Boeing:
Boeing's Receiver ID
/ M / AN / 2/15 / Must use
GS04 / 373 / Date
Exostar:
Format CCYYMMDD
/ M / DT / 8/8 / Must use
GS05 / 337 / Time
Exostar:
Format HHMM
/ M / TM / 4/8 / Must use
GS06 / 28 / Group Control Number
Exostar:
Unique group control number assigned by the Sender
/ M / N0 / 1/9 / Must use
GS07 / 455 / Responsible Agency Code / M / ID / 1/2 / Must use
Code / Name
X / Accredited Standards Committee X12
GS08 / 480 / Version / Release / Industry Identifier Code / M / AN / 1/12 / Must use
Code / Name
004010 / Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Example Segment:
GS~PR~599599599~CASSAPBGS~20130326~0001~381~X~004010|
GS~PR~599599599~BDSNWP~20130326~0001~381~X~004010|
Segment Notes:
The Boeing GS Receiver ID will vary depending on the Boeing Business System (BBS) for which the data is intended.
Boeing Receiver IDs and Qualifiers:
GS Usage / BGSSAP / BDS NWP
Production & Test / CASSAPBGS / BDSNWP
BSCP EDI 855 Purchase Order Acknowledgment IG V1.4.ecs / 1 / Exostar LLC
Purchase Order Acknowledgment - 855 / X12V4010 / 5/3/2017
ST /
Transaction Set Header
/ Pos: 010 / Max: 1Heading - Mandatory
Loop: N/A / Elements: 2
User Option (Usage): Must use
Purpose: To indicate the start of a transaction set and to assign a control number
Element Summary:
Ref / Id / Element Name / Req / Type / Min/Max / UsageST01 / 143 / Transaction Set Identifier Code / M / ID / 3/3 / Must use
Code / Name
855 / Purchase Order Acknowledgment
ST02 / 329 / Transaction Set Control Number
Exostar:
Unique transaction set control number assigned by the Sender
/ M / AN / 4/9 / Must use
Example Segment:
ST~855~0001|
BSCP EDI 855 Purchase Order Acknowledgment IG V1.4.ecs / 1 / Exostar LLC
Purchase Order Acknowledgment - 855 / X12V4010 / 5/3/2017
BAK /
Beginning Segment for Purchase Order Acknowledgment
/ Pos: 020 / Max: 1Heading - Mandatory
Loop: N/A / Elements: 7
User Option (Usage): Must use
Purpose: To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
Element Summary:
Ref / Id / Element Name / Req / Type / Min/Max / UsageBAK01 / 353 / Transaction Set Purpose Code / M / ID / 2/2 / Must use
Code / Name
11 / Response
BAK02 / 587 / Acknowledgment Type
Exostar:
Please refer to the segment notes shown at the end of the BAK segment for information on setting the value in the BAK02 Acknowledgment Type and understanding its relationship to the ACK01 values at the line item level.
/ M / ID / 2/2 / Must use
Code / Name
AC / Acknowledge - With Detail and Change (Exostar: Accepted With Amendment)
AH / Acknowledge - Hold Status (Exostar: In Process)
AT / Accepted
BAK03 / 324 / Purchase Order Number
Boeing:
POnumber varies in length and format by Boeing Business System (BBS)
/ M / AN / 1/22 / Must use
BAK04 / 373 / Date
Exostar:
Date of the PO. Format: CCYYMMDD
/ M / DT / 8/8 / Must use
BAK08 / 127 / Reference Identification
Exostar:
Seller's internal order number
Boeing:
Optional unless noted belowas required for a specific BBS.
BGS SAP CAS MS:
Required by CAS.
/ O / AN / 1/30 / Used
BAK09 / 373 / Date
Exostar:
Date of thePOR. Format:CCYYMMDD
/ O / DT / 8/8 / Must use
BAK10 / 640 / Transaction Type Code
Exostar:
Type of documentfor whichthe Response was generated
/ O / ID / 2/2 / Used
Code / Name
OR / Order
Example Segment:
BAK~11~AC~50021234567890~20130325~~~~788Z14A~20130326~OR|
Segment Notes:
Follow these guidelines in setting the valuein theBAK02:
BAK02 / Description / ACK01 value / Conditions To Set BAK02 / Notes on Usage
AH / In Process / IH / If the ACK01 on anylinein the order= "IH" then BAK02 = "AH" / Acknowledgesthe Supplier has received the PO and is reviewing it. Any individual line can be maintained in an "IH" status until the Supplier is ready to Accept the line or to Acknowledge the line with Exceptions. The "In Process" POR is optional unless identified as required for a specific BBS.
AT / Accepted / IA / If the ACK01 onALLlines in the order= "IA" then BAK02 = "AT" / The entire orderhas beenAccepted by the Supplier "as is" if all lines are set to "IA". Once all lines have been Accepted, the status of the lines/header cannot be changed for thePurchase Order.
AC / Accepted With Amendment /
Acknowledged with Exceptions / IC / If the ACK01 on anyline in the order= "IC" and no lines = "IH"then BAK02 = "AC". All openlines must contain either "IC" or "IA" in the ACK01. / For any line that a Supplier has Acknowledged with Exceptions then a Supplier Message must be provided at the Header Level in the N9 "L1" that identifies by line and schedulethe details of all exceptions.
No changes are to be made to thelines by the Supplier. If a change is to be made the Buyer will issue a POC. The Supplier can change a line(s) from Accepted With Amendment to Accepted as long asno Purchase Order Change has been issued.
If a BBS requires the POR (855 POA) thenit is mandatory that Suppliers sendone or morePORs (855 Purchase OrderAcknowledgments) toAccept all openlines or Accept some openlines and set the remainder of the linestoAccepted With Amendment (Acknowledged with Exceptions).Exostaruses the individual ACK segments todetermine the current Order status on BSCP, not the BAK02 Acknowledgment Type. Once aPOC has been issued, responses can no longer be made against the original PO.
Code AC (Accepted With Amendment) used in the integrationis equivalent to Acknowledged with Exceptions on the BSCP User Interface.
BGS SAP CAS MS:
The "In Process" POR is required by CAS as the first POR after receipt of a PO.The PORshould not be confused with a 997 Functional Acknowledgment which acknowledges a document has been received and whether it passed syntax checks.
BSCP EDI 855 Purchase Order Acknowledgment IG V1.4.ecs / 1 / Exostar LLC
Purchase Order Acknowledgment - 855 / X12V4010 / 5/3/2017
PER /
Administrative Communications Contact
/ Pos: 060 / Max: 1Heading - Optional
Loop: N/A / Elements: 4
User Option (Usage): Used