Purchase Order Change Response IMPLEMENTATION · PDF filePurchase Order Change Response Flat File 5/04/2017 BSCP Flat File Purchase Order Change Response Implementation Guide V1.0

Purchase Order Change Response –

IMPLEMENTATION GUIDE BSCPPOCRFF1

BOEING (BSCP)

EXOSTAR LLC +1.703.561.0500 phone www.exostar.com 2325 Dulles Corner Boulevard +1.703.793.1763 fax Suite 600 Herndon, VA 20171

http://www.exostar.com/

Purchase Order Change Response Flat File 5/04/2017

BSCP Flat File Purchase Order Change Response Implementation Guide V1.0

i Exostar LLC

Document Status

Document Name Exostar Implementation Guide for BSCP – Flat File Purchase Order Change Response

Version 1.0

Issue Date May 4, 2017

Author Ann Lamica

Description An Implementation Guide for Aerospace and Defense industry Suppliers who want to deliver Purchase Order Change Responses in an Exostar Flat File Format.

Document Revision History

Version # Date Author’s Name Records Revised

Revisions Made

1.0 draft 04/25/2017 Ann Lamica New First Published Version - draft

3700 maximum characters in Supplier Message

1.0 05/04/2017 Ann Lamica Minor note/usage clarifications

First Published Version (no substantive changes from draft of 4/25/17). There is an update to the table with the data links to other documents to include use of the Supplier Code from the POC.



ii Exostar LLC

Introduction

This Guide is designed for Suppliers who want to send Purchase Order Change Responses (POCRs) in the Flat File format for the Boeing Supply Chain Platform (BSCP). The Purchase Order Change Response is sent by a Boeing Supplier to Exostar in response to a Boeing Purchase Order Change (POC). The POCR will be posted to BSCP and forwarded to the appropriate Boeing Business System (BBS).

Requirements may vary by each Boeing Business System utilizing the POCR and the Supplier will need to meet the requirements of any BBS with which the Supplier is integrated via Exostar. Since the POCR is not utilized by every Boeing Business System, the Supplier should not create or send the POCR in response to any POC’s generated by a non-participating BBS. As a result, the Supplier will need an internal method of identifying which Boeing POC’s need responses.

The first response/status required by some Boeing Business Systems is an in process notification. That can be followed by an “as is” acceptance or an acceptance with amendment. The key status responses are located at the line/schedule line level and any proposed changes by the Supplier for the header, line or schedule line must be identified in a Supplier Message at the header level.

The Supplier is not permitted to update order data, however, line/schedule level data must be returned at the detail level from the POC and all lines/schedule lines must be accounted for and responded to in order to set the overall status. It is expected that the Supplier will promptly issue the POCR. Additional information on properly populating a POCR is included within the details of this Implementation Guide.

The overall structure of the Flat File Purchase Order Change Response (POCR) is defined after the Table of Contents. Examples of a typical BSCP Flat File are included and subsequent pages of this Guide define the usage or technical requirements for each Flat File record and the data elements used within the transaction. Notes may be present explaining Boeing’s usage or identifying special requirements by BBS. Differences in data format, field size or content is noted by BBS where appropriate and may be accompanied by examples to assist the Supplier in mapping the POCR transaction properly for each element/record.

Some Flat File elements will have specific code values indicated in the Guide. 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 for Exostar or Boeing to properly apply the POCR.

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.



iii Exostar LLC

Table of Contents

Document Status ..................................................................................................................................................... i

Document Revision History ..................................................................................................................................... i

Introduction ........................................................................................................................................................... ii

Purchase Order Change Response ........................................................................................................................ 4

Transaction Control ............................................................................................................................................... 8

POCR Header ........................................................................................................................................................10

Reference Information – Header ..........................................................................................................................14

Reference Description – Header ..........................................................................................................................16

POCR Detail ..........................................................................................................................................................17



4 Exostar LLC

POCR Purchase Order Change Response

Purpose: This document contains the format and establishes the data contents of the Purchase Order Change Response as a Flat File format to be used within Exostar BSCP (Boeing Supply Chain Platform). The transaction set can be used to convey acceptance of or exception to a previously submitted Purchase Order Change (POC) by the Buyer. The POCR should only be generated against the most current POC on Exostar BSCP, earlier versions will be rejected.

Heading:

LOOP ID – RFH 1000*

DSH Reference Description - Header M 1

Detail: Record ID Record Name Req Max Use Repeat

LOOP ID – DTL 4000

DTL POCR Detail M 1

* Total characters contained in all DSH records containing the Supplier Message may not exceed 3700

Boeing POR and POCR Usage Requirements:

The following Boeing Business Systems require the POR and POCR transactions.

BGS SAP CAS MS: Requires the POR and POCR including the “In Process” status for all orders and changes

BDS: May use the integrated the POR and POCR in the future

Boeing Business Systems not noted above 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.

Record ID Record Name Req Max Use Repeat

CTL Transaction Control M 1

HDR POCR Header M 1

RFH Reference Information - Header O 1



5 Exostar LLC

FLAT FILE NAME:

The Flat File naming is dependent on environment. Test Environment: fromDuns_BSCPTEST_dataType_version_timestamp.txt Production Environment: fromDuns_BSCPPROD_dataType_version_timestamp.txt

BSCPTEST or BSCPPROD is a fixed value that will occur dependent on the Exostar environment the document is being transmitting to.

fromDuns is same as Supplier MPID

Datatype is POCR

Version is BSCPPOCRFF1

Format for Timestamp is yyyyMMddHHmmssSSS

Example File Name: Test Environment: b1bccb95-d87e-4d4e-b6c0-

3ca849993f9a_BSCPTEST_POCR_BSCPPOCRFF1_20151025131026199.txt Production Environment: b1bccb95-d87e-4d4e-b6c0-

3ca849993f9a_BSCPPROD_POCR_BSCPPOCRFF1_20151025131026199.txt

Number of Transactions Per File: A maximum of 300 POCRs can be combined into a single flat file. Each POCR must contain Control (CTL), Header (HDR) and at least one (1) Detail (DTL) record as described in this Implementation Guide. Additonal record types may be required as noted in this document.

Delimiters: The flat file formatting follows the below delimiter guidelines.

Exostar Delimiters Record Identifier Element Separator Record Terminator

Production First value before the | (pipe) I (pipe) CRLF

Test First value before the | (pipe) I (pipe) CRLF

Rules: The first value in each record will be the Record ID. The first data element is preceded by the first element separator. The last element is followed by a element separator. The record is terminated with a Carriage Return Line Feed (CRLF) Elements with null values will be indicated by back to back element separators (see RECORD_2,

ELEMENT_B)

Example: RECORD_1|ELEMENT_1|ELEMENT_2|ELEMENT_3|LAST_ELEMENT| RECORD_2|ELEMENT_A||ELEMENT_C|LAST_ELEMENT|



6 Exostar LLC

Flat File POCR Examples:

Accepted With Amendment (Acknowledged with Exceptions): In the example below we are showing mixed values. Lines 10 & 30 have been Accepted With Amendment for which there are notes in the Supplier Message explaining the reason for the exceptions. Line 20 has been Accepted “as is” for which no note in Supplier Message is needed.

CTL|POCR|444444500212345678902016120122011220|b1bccb95-d87e-4d4e-b6c0-3ca849993f9a|e78ab758-

78a0-1000-b1a4-0a1c0c090001|BSCPPOCRFF1|CASSAPBGS|20161201|22011220||||||

HDR|Response|AC|50021234567890|00000001|20160801|SupOrdNumber|20161201|20161130|CP|KH|e78ab758-78a0-1000-b1a4-0a1c0c090001|b1bccb95-d87e-4d4e-b6c0-3ca849993f9a|Smith, John|[email protected]|||||||||||| RFH|L1|Supplier Message|| DSH|Line 10 Schedule Line 1 incorrect price should be $102 EA, cannot deliver until 20170428| DSH|Line 30 Schedule Line 1 request reschedule to 07/31/17| DTL|10|IC|1|10|EA||||||||||| DTL|10|IC|2|10|EA||||||||||| DTL|20|IA|1|50|EA|||||||||||

DTL|30|IC|1|25|EA|||||||||||

In Process: Note there is no Supplier Message as this is an “In Process” POCR and none is needed.



HDR|Response|AH|50021234567890|00000001|20160801|SupOrdNumber|20161201|20161130|CP|KH|e78ab758-78a0-1000-b1a4-0a1c0c090001|b1bccb95-d87e-4d4e-b6c0-3ca849993f9a|Smith, John|[email protected]|||||||||||| DTL|10|IH|1|10|EA||||||||||| DTL|10|IH|2|10|EA||||||||||| DTL|20|IH|1|50|EA|||||||||||

DTL|30|IH|1|25|EA|||||||||||

Accepted: Note there is no Supplier Message as this is an “Accepted” POCR. All header and detail line/schedules have been accepted “as is”.



HDR|Response|AT|50021234567890|00000001|20160801|SupOrdNumber|20161201|20161130|CP|KH|e78ab758-78a0-1000-b1a4-0a1c0c090001|b1bccb95-d87e-4d4e-b6c0-3ca849993f9a|Smith, John|[email protected]|||||||||||| DTL|10|IA|1|10|EA||||||||||| DTL|10|IA|2|10|EA||||||||||| DTL|20|IA|1|50|EA|||||||||||

DTL|30|IA|1|25|EA|||||||||||



7 Exostar LLC

POCR Data Links To Other Documents: This table identifies the Exostar Data Source from which an POCR element may originate. All elements may not be present on all POCRs or used by all Boeing Business Systems (BBS).

Exostar Data Source

POC Flat File (BSCPPOCFF1)

Shared Elements POCR Flat File (BSCPPOCRFF1)

NMH05 – Supplier Code (Identification Code) CTL02 – Transaction Control Number (contains the

Supplier Code from NMH05 and PO Number from

HDR04)

CTL04 – Receiver Identification (Seller MPID) CTL03 – Sender Identification (Seller MPID)

CTL03 – Sender Identification (Buyer MPID) CTL04 – Receiver Identification (Buyer MPID)

CTL06 – Boeing Business System Identification (BBS) CTL06 – Boeing Business System Identification (BBS)

HDR04 – Order Number HDR03 – Purchase Order Number

HDR06 – Change Order Sequence Number HDR04 – Change Order Sequence Number

HDR07 – Order Date HDR05 – PO Date

HDR08 – Change Order Date HDR08 – POC Date

NMH05 – Buyer MPID (Identification Code) HDR11 – Buyer MPID

NMH05 – Seller MPID (Identification Code) HDR12 – Seller MPID

DTL01 – Line ID DTL01 – POC Line ID

SCH01 – Schedule ID DTL03 – Schedule ID

SCH02 – Requested Schedule Qty DTL04 – Requested Schedule Quantity

SCH03 – UOM DTL05 – Schedule UOM

Transaction Set Notes: The following is a terminology cross-reference to various transactions within the Exostar Order Management Suite. The most common usage in our Implementation Guides will be the Doc Type.

Doc Type Name FF Functional Identifier Code (CTL01)

PO Purchase Order PO

POC Purchase Order Change POC

ASN Advance Ship Notice ASN

FA Functional Acknowledgment FA

POR Purchase Order Response POR

POCR Purchase Order Change Response POCR



8 Exostar LLC

CTL Transaction Control Elements: 13 Max: 1

Heading - Mandatory

Loop: N/A Repeat: N/A

Purpose: To indicate the beginning of an Purchase Order Change Response (POCR) and to identify the sender, receiver, dates and transaction control information. Please note throughout the document that an “Id” is present in the left column within the Element Summary. This field is used internally within Exostar and contains no information of value to the Supplier.

Element Summary:

ID Ref Element Name Req Type Min/Max

CTL01 Functional Identifier Code

M Code 2/4

Code Name

POCR Purchase Order Change Response

CTL02 Transaction Control Number

Exostar: Supplier’s system generates a unique identifier per transaction, based on the following scheme: Supplier Code + PO Number + Timestamp [CCYYMMDDHHmmssSS]

M varChar 18/144

5 CTL03 Sender Identification

Exostar: Assigned MPID

M varChar 36/40

8 CTL04 Receiver Identification

Exostar: Assigned MPID

M varChar 36/40

CTL05 FF Version Control Number

Exostar: FF POCR Version Control Number: BSCPPOCRFF1

M varChar 1/12

CTL06 Boeing Business System Identifier

BCA ERPLN: POR/POCR not used

BGS SAP CAS MS: Uses “CASSAPBGS”

BDS: Uses “BDSNWP”

O varChar 1/10

CTL07 Transaction Date

Exostar: Format CCYYMMDD

M Date 8/8



9 Exostar LLC

CTL08 Transaction Time

Exostar: Format HHmmssSS

M Time 8/8

CTL09 Reserved for future O varChar 1/128




CTL13 Reserved for future

O varChar 1/128

Example Transaction Control Record:



Boeing Business System Identifier:

The Boeing Business System Identifier will vary depending on the Boeing Business System (BBS) for which the data is intended.

Boeing Business System (BBS) Identifiers BGS SAP BDS NWP

Production & Test CASSAPBGS BDSNWP



10 Exostar LLC

HDR POCR Header Elements: 25 Max: 1

Heading - Mandatory

Loop: N/A Repeat: N/A

Purpose: To transmit identifying numbers, dates, and other basic data relating to the Purchase Order Change Response (POCR) transaction. Please note throughout the document that an “Id” is present in the left column within the Element Summary. This field is used internally within Exostar and contains no information of value to the Supplier.

Element Summary:

ID Ref Element Name Req Type Min/Max

HDR01 Purpose

Exostar: All PORs or POCRs will have the same Purpose Code.

M Code 6/12

Purpose

Response

3 HDR02 Acknowledgment Type

Exostar: Please refer to the segment notes shown at the end of the HDR segment for information on setting the value in the HDR02 Acknowledgment Type element and understanding its relationship to the DTL02 values at the line item level.

Code Name

AC Acknowledge - With Detail and Change (Exostar: Accepted With Amendment)

AH Acknowledge - Hold Status (Exostar: In Process)

AT Accepted

M Code 2/2

1 HDR03 Purchase Order Number

Boeing: The PO Number varies in length and format by Boeing Business System (BBS) and comes from the POC.

M varChar 1/24

5 HDR04 Change Order Sequence Number

Exostar: POC Sequence Number from the POC.

Boeing: Length varies by BBS. BGS SAP CAS MS: Length is 8 characters. Example: 00000008

M Integer 1/10



11 Exostar LLC

2 HDR05 PO Date

Exostar: Date of the original PO from the POC. Format: CCYYMMDD

M Date 8/8

7 HDR06 Reference Identification

Exostar: Seller's internal order number

Boeing: Optional unless noted below as required for a specific BBS.

BGS SAP CAS MS: Required by CAS

O varChar 1/64

HDR07 POCR Issue Date

Exostar: Supplier POCR issue date. Format: CCYYMMDD

M Date 8/8

HDR08 POC Date

Exostar: Issue date of the POC Sequence Number located in HDR04 above from the POC. Format: CCYYMMDD

M Date 8/8

HDR09 Purchase Order Type Code

Exostar: Order Type Code

Code Name

CP Change to Purchase Order

O

Code 2/2

HDR10 Transaction Type Code

Exostar: Type of document for which the Response was generated

Code Name

KH Change Order

O Code 2/2

8 HDR11 Buyer MPID

Exostar: Identifies the unique 36 character integrated Exostar Test or Production MPID assigned to the Buyer and received on the POC.

Boeing: See "Boeing (Buyer) MPIDs" below for reference.

M varChar 36/40

Boeing (Buyer) MPIDs:

Production: a1d8e6d8-7802-1000-bfb4-ac16042a0001



12 Exostar LLC

Test: e78ab758-78a0-1000-b1a4-0a1c0c090001

42 HDR12 Seller MPID

Exostar: Identifies the unique 36 character integrated Exostar Test or Production MPID assigned to the Seller/Supplier. The Seller/Supplier integrated MPID used in the POCR comes from the POC.

M varChar 36/40

500 HDR13 Supplier Contact Name

Exostar: Name of Supplier Point of Contact for the POCR in the event that the Buyer has questions relating to the Response.

O varChar 1/64

49 HDR14 Supplier Contact Email

Exostar: Email Address for Supplier Point of Contact for the POCR in the event that the Buyer has questions relating to the Response. Exostar: Elements HDR15-25 are currently not used by Boeing on the POCR. Each null element should be represented by back to back element separators. Example: |||

O varChar 1/64

HDR15 Reserved for future O varChar 1/64

HDR16 Reserved for future O var Char 1/64









HDR25 Reserved for future

O varChar 1/128

Example POCR Header Record: HDR|Response|AC|50021234567890|00000001|20160801|SupOrdNumber|20161201|20161130|CP|KH|e78a

b758-78a0-1000-b1a4-0a1c0c090001|b1bccb95-d87e-4d4e-b6c0-3ca849993f9a|Smith,

John|[email protected]||||||||||||



13 Exostar LLC

Segment Notes: Follow these guidelines in setting the value in the HDR02 Acknowledgment Type:

HDR02 Description DTL02

value

Conditions To Set

HDR02 Notes on Usage

AH In Process IH If the DTL02 on

any line in the order =

"IH" then HDR02 =

"AH"

Acknowledges the Supplier has received the POC 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" POCR is optional unless identified as

required for a specific BBS.

AT Accepted IA If the DTL02

on ALL lines in the

order = "IA" then

HDR02 = "AT"

The entire change order, including the header

information, has been Accepted 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 the current

Purchase Order Change Sequence Number.

AC Accepted With

Amendment /

Acknowledged

with

Exceptions

IC If the DTL02 on

any line in the order =

"IC" and no lines =

"IH" then HDR02 =

"AC".

All open lines must

contain either "IC" or

"IA" in the DTL02.

For any line that a Supplier has Acknowledged with

Exceptions then a Supplier Message must be provided

at the Header Level in the RFH "L1" that identifies by

line/schedule the details of all exceptions. No changes

are to be made to the actual content of the lines by the

Supplier.

If a change is agreed upon by the Buyer then Boeing

will issue a new POC. The Supplier can also modify

the status on a line(s) from Accepted With Amendment

to Accepted as long as the Purchase Order Change

Sequence Number is the current POC on BSCP.

If a BBS requires the POCR then It is mandatory that Suppliers send one or more POCRs to Accept all open lines or Accept some open lines and set the remainder of the lines to Accepted With Amendment (Acknowledged with Exceptions). Exostar uses the individual values in the DTL02 to determine the current Order status on BSCP, not the HDR02 Acknowledgment Type. Once a new POC has been issued, responses can no longer be made against an earlier POC Sequence Number. An email alert will be generated by Exostar upon receipt of any POCR for a previous POC Sequence Number that cannot be applied indicating the reason for the error. Code AC (Accepted With Amendment) used in the integration is equivalent to Acknowledged with Exceptions on the BSCP User Interface. If any header level data within the POC cannot be accepted, those notes must also be placed in the “Supplier Message” and the entire POC should be Accepted With Amendment/Acknowledged with Exceptions.

BGS SAP CAS MS:

The "In Process" POCR is required by CAS as the first POCR after receipt of a POC. The POCR should not be confused with a Functional Acknowledgment which acknowledges a document has been received and indicates whether it passed syntax checks.



14 Exostar LLC

RFH Reference Information – Header

Elements: 3 Max: 1

Heading - Optional

Loop: RFH Repeat: 1

Purpose: To transmit identifying information as specified by the Ref Code in the RFH01. One “Reference Information – Header” record is allowed to identify notes to the Buyer about the supplier response to a POC. Only one RFH loop is permitted containing one header record (RFH) and one or more detail (DSH) records containing the actual message from the supplier which must clearly identify all exceptions to the POC header or detail level. A maximum of 3700 characters is permitted in a POCR to explain supplier exceptions which may be comprised of one or multiple DSH records. A Supplier Message is required if the supplier notes any exceptions taken to the header or line/schedule lines.

Element Summary:

Id Ref Element Name Req Type Min/Max

RFH01 Ref Code

Exostar: A message is required if the supplier notes any exceptions taken to the header or line/schedule lines. Use the following code value to identify the loop:

M Code 2/3

Code: Name:

L1 Letters or Notes

RFH02 Ref Title

Exostar: There will be a maximum of one RFH "L1" loops at the header which may include one or more DSH Records. Value of the RFH02 = “Supplier Message”. Note that there is no value in RFH03.

Ref Code (RFH01)

Ref Title Values (RFH02) Additional Ref

Title Values (RFH03)

L1 Supplier Message

O varChar 1/64

RFH03 Additional Ref Title

Exostar: Not used

O varChar 1/128



15 Exostar LLC

Example RFH Loop:

RFH|L1|Supplier Message||

DSH|Line 1 Schedule Line 1 incorrect price should be $102 EA, cannot deliver until 20170428|

DSH|Line 3 Schedule Line 1 request reschedule to 07/31/17|

The RFH "L1" "Supplier Message" loop is required whenever the Supplier needs to report an exception to the POC header, any line item or schedule line item. The text within the Supplier Message is free form; however, if it relates to item detail level information then it should contain the line number, the schedule line number (for date, quantity or UOM changes) and the specific change being requested by the Supplier. Only one RFH "L1" loop can be present within a POCR and all messages from the Supplier must be conveyed within one or more DSH records. Exostar can accept a maximum of 3700 characters within the one RFH/DSH loop. A supplier can choose to send 1 DSH record containing up to 3700 characters or may elect to send multiple DSH records each containing smaller messages. In either event, the maximum allowed is 3700 characters. The RFH "L1" loop need not be created under the following conditions which need no additional explanation:

1. Supplier Accepts the entire POC "as is"

2. The POCR is an "In Process" only POCR



16 Exostar LLC

DSH Reference Description – Header

Elements: 1 Max: 1000

Heading – Mandatory

Loop: RFH Repeat: N/A

Purpose: To provide a free form format that allows the transmission of text information about the POCR. The DSH record contains the text content of the Supplier Message to the Buyer about the POC. It is mandatory if an RFH record is present.

Element Summary:

Id Ref Element Name Req Type Min/Max

82 DSH01 Reference Description

Exostar: One or more DSH records may contain information about the previous RFH record. The content is a Supplier Message to the Buyer explaining any exceptions that caused the supplier to be unable to Accept the POC “as is”. If exceptions are at the line or schedule line then it is necessary to identify them along with the specific change requested. Header exceptions, if any, also need to be identified in the Supplier Message.

BGS SAP CAS MS: Used

BDS: Used

M varChar 1/3700

Example DSH Record:

DSH|Line 3 Schedule Line 1 request reschedule to 07/31/17|

Segment Notes:

The DSH01 should contain the Supplier's specific reason(s) for requesting an amendment to the POC including identification of each POC line position and schedule line for which a change is requested. Multiple DSH records may be included in the one RFH Loop, however, the total number of characters in all DSH records combined may not exceed 3700 characters.



17 Exostar LLC

DTL POCR Detail Elements: 15 Max: 1

Detail – Mandatory

Loop: DTL Repeat: 4000

Purpose: Identifies item level information pertaining to the contents of the POCR including the relationship of the item to a POC. A new POCR Detail (DTL) Record should be created for every POC Line/Schedule Line that is included in the Purchase Order Change. Please note throughout the document that an “Id” is present in the left column within the Element Summary. This field is used internally within Exostar and contains no information of value to the Supplier.

Element Summary: ID Ref Element Name Req Type Min/Max

531 DTL01 POC Line ID

Exostar: Assigned Line/Position/Item Identifier from the Buyer’s POC. The value and format must match the originating document.

Boeing: The format of the POC Line/Position/Item varies with the Boeing Business System (BBS) and the POCR must match the POC. In general, a Boeing POC Line/Position/Item Identifier could include:

A number with a fixed length, including leading zeroes. Example: 0010 (always 4 characters)

A number with a maximum length without leading zeroes. Example: 10 (1 to 5 digits, no leading zeroes)

An identifier with a combination of alpha, numeric and special characters. Example: 3-Shipment 1 (combination of character types)

BGS SAP CAS MS: The POC Line/Position/Item format is a maximum of five digits without leading zeroes. Examples: 1,10, 20.

BDS: The POC Line/Position format is four characters with leading zeroes padding the number to four positions. Example: 0001, 0010.

M varChar 1/20

328 DTL02 Line Item Status Code

Exostar: Line Item/Schedule Line Item status code. See Notes at the end of the record which contains the criteria for setting the status.

Code Name

IA Item Accepted (As is - no changes)

IC Item Accepted - Changes Made (Accepted With Amendment/Acknowledged with Exceptions)

M Code 2/2



18 Exostar LLC

IH Item on Hold (In Process)

85 DTL03 Schedule ID

Exostar: Schedule Line Number from the SCH01 in the POC

M varChar 1/64

126 DTL04 Requested Schedule Quantity

Exostar: Quantity from the POC for the Schedule Line Number referenced in SCH02. Supplier requested quantity changes should not be reflected in the "SCH02" quantity provided by the Supplier on the POCR. Supplier originated change requests are to be made via the RFH "L1" "Supplier Message" loop located at the header level. If the Buyer agrees to the revisions, a POC will be issued by the Buyer with the revised quantity so that the Supplier can accept the line.

M Float 1/20

DTL05 Schedule UOM

Exostar:

Unit of Measurement from the POC for the quantity specified in the SCH03 for the POC Line/Schedule Line.

Exostar: Elements DTL06 - 15 are currently not used by Boeing on the POCR. Each null element should be represented by back to back element separators. Example: |||

M Code 2/2

DTL06 Reserved for future O Float 1/20

DTL07 Reserved for future O varChar 1/64








DTL15 Reserved for future

O varChar 1/256



19 Exostar LLC

Example POCR Detail Record:

DTL|10|IA|1|10|EA|||||||||||

DTL|10|IA|2|10|EA|||||||||||

DTL|20|IH|1|50|EA|||||||||||

DTL|30|IC|1|25|EA|||||||||||

Segment Notes:

The DTL02 Line Item Status Code represents the Supplier status for the POC line number referenced in the DTL01. This status must be in sync with the HDR02 (Acknowledgment Type). Whenever the DTL02 = "IC" then a note must be provided by the Supplier in the RFH "L1" "Supplier Message" loop located at the Header indicating the exceptions from the lines/schedule lines. Refer to the RFH record for additional information. The DTL02 is considered a line item level status, however, the line status automatically applies to all schedule lines contained within the line. The following rules apply:

1. All schedule lines within the line are considered "Accepted" if the item is Accepted "IA". If any schedule line cannot be Accepted "as is", set the line item status to "IC" Accepted With Amendment (Acknowledged with Exceptions) and provide a "Supplier Message" specifying the Line Number, Schedule Line Number and the exception;

2. All terms, conditions, notes, etc. contained in the header of the POC are deemed to be Accepted if any

line is Accepted. In the event that a Supplier cannot Accept the POC header "as is", set the line item status for all lines to "IC" and create a "Supplier Message" defining the header level exception(s);

3. If an exception exists at either/both the header and line item/schedule levels, the RFH "L1" "Supplier

Message" should include all exceptions. Only one "RFH" "L1" loop may be contained within a Purchase Order Change Response.

4. No RFH loop containing an “L1” "Supplier Message" is needed if all lines = "IA" (Accepted) or "IH" (In

Process). If the Buyer is agreeable to the proposed changes, then a POC will be issued to update the order. If, however, a POC is received without the requested changes then it will be necessary to repeat the exceptions and comments. Once a new POC been issued on the order, any responses to the previous POC will not be posted nor passed to the Buyer as it no longer is the current version of the document.