Version is BSCPPOCFF1 Format for Timestamp is yyyyMMddHHmmssSSS Example File Name: Test Environment: Production Environment: Each POC from BSCP will equate to a single flat file POC to the Supplier. Delimiters: The flat file formatting follows the below delimiter guidelines. 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 an 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) Optional records with all null values will not be included (see absence of RECORD_3) Example: RECORD_1|ELEMENT_1|ELEMENT_2|ELEMENT_3|LAST_ELEMENT| RECORD_2|ELEMENT_A||ELEMENT_C|LAST_ELEMENT| RECORD_4|ELEMENT_X|ELEMENT_Y|ELEMENT_Z|LAST_ELEMENT| - Example Transactions: The Boeing Business System Identifier will vary depending on the Boeing Business System (BBS) sending the data. The example(s) shown may not include all elements or records required or may contain some not required for all transactions. The use of a value such as "NOTE NAME, TERM OR CONDITION" is a generic placeholder for more specific but varied values. Please refer to the details for each record and element within this Implementation Guide. 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. BCA Purchase Order Change Example:
Version is BSCPPOCFF1 Format for Timestamp is yyyyMMddHHmmssSSS Example File Name: Test Environment: Production Environment: Each POC from BSCP will equate to a single flat file POC to the Supplier. Delimiters: The flat file formatting follows the below delimiter guidelines. 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 an 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) Optional records with all null values will not be included (see absence of RECORD_3) Example: RECORD_1|ELEMENT_1|ELEMENT_2|ELEMENT_3|LAST_ELEMENT| RECORD_2|ELEMENT_A||ELEMENT_C|LAST_ELEMENT| RECORD_4|ELEMENT_X|ELEMENT_Y|ELEMENT_Z|LAST_ELEMENT| - Example Transactions: The Boeing Business System Identifier will vary depending on the Boeing Business System (BBS) sending the data. The example(s) shown may not include all elements or records required or may contain some not required for all transactions. The use of a value such as "NOTE NAME, TERM OR CONDITION" is a generic placeholder for more specific but varied values. Please refer to the details for each record and element within this Implementation Guide. 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. BCA Purchase Order Change Example:
BSCP%20FF%20Purchase%20Order%20Change%20IG%20V1.3.docx