SF30_SPE30223R00090004.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NO.

See Block 14

4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)

6. ISSUED BY CODE SPE302 7. ADMINISTERED BY (If other than Item 6) CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

CODE FACILITY CODE

SPE30223R0009

X

2023 AUG 04

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of OffersX X is extended, is not extended.

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

12. ACCOUNTING AND APPROPRIATION DATA (If required)

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO.

IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc. ) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A NAME AND TITLE OF SIGNER (Type or print)

NSN 7540-01-152-8070

Previous edition unusable

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

16B. UNITED STATES OF AMERICA15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

(a) By completing Items 8 and 15, and returning

DLA TROOP SUPPORT INDO-PACIFIC

1025 QUINCY AVE, SUITE 1000

JBPHH HI 96860-3520

USA

15C. DATE SIGNED 16C. DATE SIGNED

D. OTHER (Specify type of modification and authority)

2023 AUG 31

3. EFFECTIVE DATE

Opening/Closing Date Changed to:

2023 AUG 04 / 2023 SEP 27

TIME 8:00 AM

See Attached Continuation Sheet(s).

(X)

CHECK ONE

9A. AMENDMENT OF SOLICITATION NO.

9B. DATED (SEE ITEM 11)

13. THIS APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED:

CONTINUED ON NEXT PAGE

PAGE 2 OF 3 PAGES

SPE30223R0009 - 0004

Amendment 0004 to Solicitation SPE302-23-R-0009 / Fresh Bread and Bakery Items for Troops and Ships, Guam

A. The purpose of this amendment to: 1) Correct Amendment 0003, Questions and Answers as shown below; 2) Extend the question period and solicitation closing date; 3) Clarify STATEMENT OF WORK – updated 8/11/2023, paragraph I.C. as stated below

B. Amendment 0003 is changed:

FROM:

Question 5: Page 4 of the SOW still requires the contractor to have EDI capability. Item I-D, Ordering System states that EDI capability is not a requirement of this contract but the offeror must be moving toward EDI functionality.

Answer 5: Acceptable for EDI or Non-EDI (via FAX or Email)

Question 5a: Is the contractor required to have EDI capability?

Answer 5a: It’s not mandatory

Question 5b: If not, what timeline is given to achieve full EDI functionality? Is any consideration given to offerors that have Full EDI functionality as part of their bid offer?

Answer 5b: There is no specific consideration available.

TO:

Question 5: Page 4 of the SOW still requires the contractor to have EDI capability. Item I-D, Ordering System states that EDI capability is not a requirement of this contract but the offeror must be moving toward EDI functionality.

Answer 5: Yes. In accordance with Solicitation Document, Page 4. The awardee will be required to have a computer system capable of accepting delivery orders and processing Electronic Data Interchange (EDI) transactions. This contract will require the contractor to have electronic commerce/electronic data interchange EC/EDI capabilities.

Question 5a: Is the contractor required to have EDI capability?

Answer 5a: Yes. Original Solicitation, page 4, The awardee will be required to have a computer system capable of accepting delivery orders and processing Electronic Data Interchange (EDI) transactions. This contract will require the contractor to have electronic commerce/electronic data interchange EC/EDI capabilities.

Question 5b: If not, what timeline is given to achieve full EDI functionality? Is any consideration given to offerors that have Full EDI functionality as part of their bid offer?

Answer 5b: After contract award, the Awardee (vendor)’s IT team works with the DLA STORES/IT Team, and go through a testing stage to try and eliminate the errors prior to the STORES catalog live date (performance start date).

C. Solicitation, Page 17: The questions period stated in ADDENDUM to 52.212-1 is extended from August 25, 2023 8 AM to September 6, 2023, 8 AM (Hawaii Standard Time).

D. The closing date of subject solicitation is extended from September 20, 2023, 10 AM to September 27, 2023, 8 AM (Hawaii Standard Time).

E. The following is added to Statement of Work – updated 8/11/2023 (SOW) paragraph I. INTRODUCTION C.: This acquisition is being solicited under the authority of FAR 13.5, "Simplified Procedures for Certain Commercial Items".

The purpose of this program is to vest contracting officers with additional procedural discretion and flexibility, so that commercial item acquisition greater than the simplified acquisition threshold but no exceeding $7.5 million may be solicited, offer, evaluated, and awarded in a simplified manner that maximizes efficiency and economy and minimizes burden and administrative costs for both the Government and industry.

F. All other terms and conditions of this solicitation remain the same.

CONTINUATION SHEET REFERENCE NO. OF DOCUMENT BEING CONTINUED: PAGE 3 OF 3 PAGES

SPE30223R0009 - 0004

Attachments

List of Attachments

Description File Name ATTACH_AMPS_Instructio ns AMPS Request_Vendor.pdf

ATTACH_EDI_Set_Up EDI Set-Up.pdf

STORES-AMPS

STORES Role Request Process for

Customers and Vendors May 2016

Introduction

• In order to gain access to the STORES system, new users must first create an account and request access through the Account Management and Provisioning System (AMPS) via https://amps.dla.mil

• Customers and vendors that are external to DLA will be issued a user id and will create a password that is used just for AMPS access.

• Once a customer/vendor submits a request for a STORES role via AMPS, the request will go directly to the DLA Representative assigned to their specified geographic area of responsibility.

• The DLA Representative approves the request and a notification from AMPS is sent to the STORES security administrators for their records.

https://amps.dla.mil/

AMPS Login

• As a STORES Customer/Vendor, this will be the first login to AMPS:

Select the link: ‘First Time In AMPS? Click Here to Register’

• AMPS User Registration

Please select: If you are external to DLA, select

‘Supplier/Vendor’ on the lower left hand table, first column.

DLA Privacy Act Statement and Rules of Use

1. Read the Privacy Act Statement

2. Select the ‘Rules of Use’ link to read and review.

3. Select ‘Accept’

AMPS First Time User Registration

1. Fill in the required fields. If you are a vendor, provide your CAGE code.

2. When finished, select ‘Next’ on the top right corner of the screen.

**The User Type will say VENDOR, even if you’re a supplier or customer. This is a standard AMPS designation**

AMPS User Registration - Set your Security Answers and Password

1. Select your security questions using the drop down box 2.Provide your answer to each question in the field directly beneath the question.

3. You must select three questions and provide answers for each.

4. Set your password using the composition rules on the right side.

5. When finished, select ‘Next’ on the upper right of the screen.

AMPS User Registration Summary

1. Review your information for accuracy.

2. Select the ‘Create Account’ button in the upper right hand corner of the screen to continue.

User Registration Confirmation (USER ID)

1. Take note of your ‘login name’

2. Select the ‘Login to AMPS’ link where you will use your issued login name and the password you just created to login to AMPS.

AMPS Access Page

1. You are now on the AMPS Gateway page.

Notice the User Guides and Job Aids Available on the right of the screen for future reference.

2. Select ‘Click HERE for access to AMPS’

DLA Warning Banner and User Agreement

1. Read the Warning Banner and select the ‘User Agreement’ link for review.

2. Select ‘OK’ to

Login to AMPS

1. Login to AMPS using the Login ID issued to you and password you created.

1. Select ‘Request Role’ from the menu on the left hand side of the screen.

1. Review the DLA Privacy Act Statement and select ‘Accept’ to continue.

1. Review your information, make any necessary corrections

2. Select ‘Next’ in the upper right corner of the screen to

In the ‘Browse Roles by Application’ area:

1. Select the arrow on the left of ‘DLA Enterprise Applications’

2. Select ‘STORES’

3. You will see that the box directly beneath is populated with STORES Roles

Selecting your STORES Role(s)

1. If you are a customer, scroll through the roles for STORES Prod – Customer – STATE/COUNTRY/ZONE and select the role for the PRIMARY geographic area that you are responsible for, this is typically the same as your business address.

2. If you are a vendor, scroll beyond the Customer roles until you see, STORES Prod – Vendor – STATE/COUNTRY/ZONE and select the role for the PRIMARY geographic area that you are responsible for, this is typically the same as your business address.

3. Select the right arrow between the two boxes to move your role(s) into the ‘Selected Roles’ area.

4. Scroll up to the top of the screen and select ‘Next’ to continue.

1. Provide a ‘Justification’ for your request, enter your supervisor’s contact information and select ‘Next’ when finished.

1. Review your Role Request Summary and if correct…

2. Select ‘Submit’ to complete your request.

1. Take note of your SAAR (System Authorization Access Request) number

2. Take note of the displayed AMPS Helpdesk contact information in the event you have questions or a technical issue.

3. Select ‘Ok’

4. You will receive an e-mail confirmation to the email address you supplied during account registration.

Next Steps

• You will receive an e-mail notification once your request is approved by your DLA Representative.

• If you have not already, please proceed to https://www.stores.dla.mil to request your STORES user account.

• If you have any questions about the process, please contact:

Your DLA Troop Support Representative https://www.stores.dla.mil/

Subsistence Total Ordering and Receipt Electronic System

(STORES)

EDI Implementation Guidelines

EDI Implementation Guidelines for Subsistence Prime Vendor (STORES)

Updated September 2017

SECTION 1.0 GENERAL INFORMATION

1.1 DLA TROOP SUPPORT EDI CONTACTS

1.2 EDI TESTING PROCESS

1.3 EDI TRANSACTION SETS

SECTION 2.0 PRODUCTION PROCEDURES

2.1 TRANSMISSION SCHEDULES

2.2 PROBLEM RECOVERY

SECTION 3.0 EDI Guidelines

3.1 (832) CATALOG REQUIREMENTS

3.2 (850) PURCHASE ORDER REQUIREMENTS

3.3 (810) INVOICE REQUIREMENTS

3.4 (864) RATIONS TEXT MESSAGE REQUIREMENTS……………………………………………….

3.5 (997) FUNCTIONAL ACKNOWLEDGEMENT REQUIREMENTS………………………………….

Section 1.0 General Information

1.1 DLA Troop Support EDI Test Contacts

1.2 Electronic Data Interchange (EDI) – Testing Process

DLA Troop Support points of contact for testing are listed at the beginning of this document. Vendors should contact these POCs several weeks prior to their contract go-live date to ensure there is sufficient time for testing. Each of the EDI transactions (832, 850, 810) must be tested successfully before the contract can move to production. Vendors should be prepared to work with the DLA Troop Support POCs for each transaction and provide notification about the success and failure of each transmission.

DLA Troop Support - Subsistence currently uses EDI communications to transmit catalogs (832s), purchase orders (850s) and receipts (810s) between STORES (Subsistence Total Order and Receipt System) and Vendor systems.

A typical EDI test process begins with an 832 (catalog) file being sent from a vendor to STORES. In this catalog file, vendors will provide stock item numbers, item descriptions, item prices and other item data included in the guidelines below. These stock items will be available for ordering by customers when the contract goes from testing to production. Once the 832 file is received, DLA Troop Support personnel will review the file to ensure all required fields are included and meet the proper requirements.

If edits are necessary, DLA will contact the vendor to discuss changes that need to be made to the file.

Contact For POC

EDI 832 (Catalog) Testing

Bob Thistle – robert.thistle@dla.mil

(215) 737-7558

Charles Benn – charles.benn@dla.mil

(215) 737-7318

Lou Milano – louis.milano@dla.mil

(215) 737-7315

EDI 850 (Purchase Order) Testing

Bob Thistle – robert.thistle@dla.mil

(215) 737-7558

Lou Milano – louis.milano@dla.mil

(215) 737-7315

Charles Benn – charles.benn@dla.mil

(215) 737-7318

EDI 810 (Invoice) Testing

Karen Conroy-Hegarty – karen.hegarty@dla.mil

(215) 737-7550

DLA Transaction Services

Edi@dla.mil (937) 656-3333 mailto:robert.thistle@dla.mil mailto:charles mailto:.benn@dla.mil mailto:louis.milano@dla.mil mailto:robert.thistle@dla.mil mailto:charles mailto:.benn@dla.mil mailto:karen.hegarty@dla.mil mailto:Edi@dla.mil

Catalog files are transmitted to STORES through an electronic mailbox at DLA Transaction Services.

Some vendors choose to use a Third Party VAN (VAN) to manage their catalogs. VANs are companies that specialize in the creation, maintenance and transmission of EDI files. When a VAN is used, vendors will provide stock item updates to the VAN, and that company will edit the catalog and transmit the file through DLA Transaction Services to STORES.

When vendors "go-live" and begin supplying items to customers, catalog updates are normally sent on a weekly basis for those items that have changed since the previous catalog submission.

Once catalogs have been approved, the next step in the test process is for a DLA Troop Support person to create and send a purchase order (850) using the stock items from the received catalog. Vendors will then notify DLA that the order was successfully received and will create and send back an invoice (810) file.

When DLA confirms that the 810 file was successfully received and processed, EDI Testing is deemed complete.

In production, orders are generated by customers either by manually keying the order directly into STORES or by uploading an order to STORES from one of the service systems. These orders are then translated into an 850 (purchase order) EDI file by STORES and sent through DLA Transaction Services to a vendor’s electronic mailbox. Vendors should keep in mind that there are times when a customer could place more than one order in the same day.

Once a vendor receives an order from a customer, the order is filled and the requested stock items are shipped to the customer's delivery location. These locations are determined by the customer and can be a dining facility, warehouse, depot, hospital, ship, child care center, or other facility. Note: Vendors should only deliver items that are on the order and should not substitute any similar items.

After the vendor has delivered the product, customers will verify shipment quantities and make any necessary adjustments to the receipt in STORES. Customers then send the receipt in STORES which generates an electronic validation of the receipt in the DLA Troop Support Financial System. This receipt is then matched to the vendor 810 (invoice) and all matching lines are paid. Any discrepancies between receipt and invoice must be researched before payment is made.

1.3 Transaction Sets

The EDI transaction sets listed below are described in detail in later sections of this guideline. Vendors must be able to support 832–Catalog, 850-Purchase Order and 810-Invoice file transmissions.

Section 2.0 Production Procedures

2.1 Transmission Schedules

Vendors should provide 832 catalog updates to DLA Troop Support before 12:00 Noon (EST) on Fridays each week so stock item changes may be reviewed prior to the update of all the weekly catalogs. Catalog updates sent after Noon on Friday will be reflected in the following weeks catalog update and may result in additional catalog pricing errors and erroneous payments.

As mentioned earlier, outbound 850 purchase orders can be generated anytime during the day seven days a week. Therefore, vendors should be prepared to retrieve order data throughout the day.

2.2 Problem Recovery During Production

After moving into production mode, delays, omissions, duplicates or any other type of error have to be addressed promptly. In the unlikely event that a delay lasts longer than one day, DLA Troop Support customers may contact the vendor regarding the option to fax or email a copy of orders.

If the Interchange Control Number (ISA13 element) is received more than once, the vendor should not process the duplicate transmission. Although the DLA Troop Support standard software has the constraints to prevent sending out duplicate purchase orders, the vendor may still need to consider checking for purchase order numbers that may have inadvertently sent more than once.

The STORES Help Desk or DLA Troop Support Subsistence Contract Specialist and/or Account Manager should be contacted promptly with operational concerns related to purchase order and catalog transactions.

Section 3.0 EDI Guidelines

This EDI Guideline is to be used for EDI partners of DLA Troop Support interfacing with STORES

For both testing and production, the following information is to be used:

3.1 832 Catalog (Vendor to DLA Troop Support) The 832 Catalog uses the standard EDI transaction set for the 832 Price/Sales Catalog. Please note:

Elements coded with an "M are mandatory and are required on all catalog submissions. Elements coded with a "C" are conditional and are required if certain conditions are met (see annotation at the bottom for each specific condition). Elements coded with an "O" are optional and are not required fields.

NOTE:

DLA is in the process of migrating current EDI X12 Maps from their current version to an upgraded 4010 version. The details of this migration are not yet defined, but will be provided when available.

All EDI capable vendors will be required to migrate to the new 4010 EDI X12 map version once it is made available.

ISA Qualifier ZZ ISA Id S39017 GS Id S39017 VAN DLA Transaction Services EDI Version 3040

Points of contact for 832 EDI Testing are:

Bob Thistle, robert.thistle@dla.mil, 215-737-7558 Charles Benn, charles.benn@dla.mil, 215-737-7318 Lou Milano, louis.milano@dla.mil, 215-737-7315

Guidelines for 832 – Catalog

Segment Element Definition and Value Size M/C/O ST Transaction ST01 Transaction Set Identifier Code

Definition: A Transaction Set Identifier Code that classifies the EDI file as an 832 catalog

Value: [“832”]

3 ID M

Set Header ST02 Transaction Set Control Number

Definition: The Transaction Set Control Number.

Value: [Transaction Set Control Number]

4-9 AN M

mailto:charles.benn@dla.mil mailto:louis.milano@dla.mil

BCT Beginning Element for Price/Sales Catalog

BCT01 Price Catalog Identifier Code

Definition: Indicates the beginning of the Price Catalog transaction set

Value: [“PC”]

2 ID M

BCT Beginning Element for Price/Sales Catalog

BCT02 Contract Number

Definition: Specifies catalog number information

Value: [Contract Number]

13 AN M

DTM Date/Time DTM01 Effective Date of Change

Definition: The code identifying the date and time of the catalog change

Value: [“152”]

DTM Date/Time DTM02 Update-date (YYMMDD)

Definition: The effective date of the catalog change

Value: [YYMMDD]

Date M

DTM Date/Time DTM03 Update-time (HHMMSS)

Definition: The effective time of the catalog change

Value: [HHMMSS]

Time M

LIN Item LIN01 Line number

Definition: Sequential Line numbers for the items on the catalog.

Value: [Line Number]

1-11 N M

LIN Item LIN02 Stock Number Identifier Code

Definition: Code identifying the type of descriptive number used in LIN03.

The code ‘SW’ indicates that LIN03 will hold the DLA Troop Support Stock Number for the item on the catalog.

Value: [“SW”]

LIN Item LIN03 Stock number

Definition: Identifying Code DLA Troop Support uses to identify an item on a catalog.

Value: [Stock Number]

13 AN M

LIN Item LIN04 Vendor Part Identifier Code

Definition: Code identifying the type of descriptive number used in LIN05.

The code ‘VP’ indicates that LIN05 will hold the Vendor’s Part Number for the item on the catalog.

Value: [“VP”]

LIN Item LIN05 Part Number

Definition: Identifying Code of the vendor’s product on the catalog

Value: [Part Number]

25 AN M

LIN Item LIN06 Mutually Defined Identifier Code

Definition: This is a constant ‘ZZ’ which indicates that the value in LIN07 is a mutually agreed upon code between the Vendor and

DLA.

Value: [“ZZ”]

LIN Item LIN07 update indicator

Definition: The update indicator for an item on the catalog. ‘C’ for a Change or Add, or ‘D’ for Delete

Value: [‘C’ or ‘D’]

1 AN M

LIN Item LIN08 Mutually Defined Identifier Code indicates that the value in the LIN09 is a mutually agreed upon code between the Vendor and DLA.

LIN Item LIN09 Economic Indicator

Definition: The Economic Indicator for the vendor providing the catalog stock items

Value: [One of the below codes – 00 to 08]

Economic Indicator options:

00 = Large business 01 = SB (Small business) 02 = SDB (Small disadvantaged business) 03 = WOSB (Women owned small business) 04 = VOSB (Veteran owned small business) 05 = SDVOSB (Service-disabled veteran owned small business) 06 = HZSB (Hub-Zone small business) 07 = Native Indian small business 08 = Native Hawaiian small business

2 AN M

LIN Item LIN10 GTIN Identifier Code

Definition : This is a constant ‘US’ value used to indicate Uniform Stock Symbol Code Number and that the next element will hold the Global Trade Item Number (GTIN)

Value: [“US”]

2 ID C

LIN Item LIN11 Global Trade Item Number (GTIN)

Definition: This is the Global Trade Item Number (GTIN) for the item on the catalog.

This element is required if LIN10 is provided.

1/40 AN C

REF Reference Numbers

REF01

Mutually Defined Identifier Code indicates that the value in the REF02 is a

REF02 Special Order Identifier Code 2 AN M

Definition: ‘SO’ is always entered in this element. ‘SO’ standing for ‘Special Order Item’. If the item is a special order one, additional information is entered in REF03.

Value: [“SO”]

REF03 Special Ordering Instructions

Definition: If the item is a Special Order one, the Special Ordering Instructions are entered in this element. If the item is not a Special Order one, then no value is entered.

Value: [Special Ordering Instructions or Null]

80 AN O

REF01 Mutually Defined Identifier Code indicates that the value in the REF02 is a

REF02 Foreign Source Identifier Code

Definition: Definition: This is a constant ‘FS which indicates a ‘Foreign Source (Non-US) Item’. If the item is from a foreign source, additional information is entered in REF03.

Value: [FS]

REF03 Foreign Source Indicator

Definition: This element designates either ‘Y’=Yes the item is from a foreign source or ‘N’=No, the item is not from a foreign source.

Value: [‘Y’ or ‘N’]

REF01 Mutually Defined Identifier Code indicates that the value in the REF02 is a

REF02 Manufacturer SKU Identifier Code

Definition: This is a constant ‘SK’ which indicates Manufacturer SKU code. If the item has an SKU code assigned, additional information is entered in REF03

Value: [“SK”]

REF03 Manufacturer SKU

Definition: If the item has an SKU assigned, the identifying code is entered. If the item does not have an SKU Code, then no value is entered.

Value: [Vendor SKU or Null]

20 AN M

REF01

Mutually Defined Identifier Code indicates that the value in REF02 is a mutually defined code between the Vendor and DLA.

2 ID

M

REF02 DLA Troop Support Unique Identifier Code

Definition: ‘DU’ is always entered in this element. ‘DU’ standing for a ‘DLA Troop Support Unique Item’. If the item is a DLA Troop Support Unique Item, additional information is entered in REF03.

Value: [“DU”]

REF03 DLA Troop Support Unique Indicator

‘Y’=Yes the item is DLA Troop Support Unique or ‘N’=No the item is not DLA Troop Support Unique

Value: [Either ‘Y’ or ‘N’]

CTB Restrictions/ Conditions

CTB01 Ordering Restrictions Identifier Code

Definition: This element specifies the conditions/restrictions (such as shipping.

ordering)

Value: [“OR”]

CTB02 Not Used 1/80 AN O

CTB03 Minimum Order Quantity Identifier Code

Definition: This is a constant ‘57’ which indicates that the value in the CTB04 is the minimum number of unit of measures for ordering this item.

Value: [“57”]

O

CTB04 Minimum Order Quantity

Definition: This element identifies the minimum number of unit of measures of the item that needs to be ordered; otherwise the vendor will not fill the order.

Value: [Quantity]

8 INT O

PID Product/Item Description

PID01 Free Form Identifier Code

Definition: This element identifies the ‘PID’ line as ‘F’ Free-form line where the vendor can enter item information.

Value: [“F”]

1 ID M

PID02 General Description Identifier Code

Definition: This code of ‘GEN’ (General Description) indicates that PID05 will provide a general description of the line item.

Value: [“GEN”]

PID03 Mutually Defined Identifier Code indicates that the value in PID07 is the Producer Price Index Categories

2 ID C5

PID04 Not Used PID05 DLA Troop Support Item Description

Definition: The vendor will enter a general

80 AN M

description of the line item in this element.

Value: [DLA Troop Support Item Description]

PID06 Not Used PID07 Producer Price Index Categories

Definition: Producer Price Index as defined by the bureau of labor statistics

Value [Producer Price Index Categories]

1/15 AN C5

PID08 DLA Troop Support Standards Acceptance Indicator

'Y'=Yes, the vendor accepts that their provided item does not deviate in any way from the DLA Standardized Item Description, or 'N'=No, the vendor does not provide this guarantee.

Value: [“Y” or “N”]

MEA Measurements MEA01 Waste Identifier Code

Definition: The code identifying the Tare Weight Value. For this element “WA” for Waste.

(Meaning the following MEA02, MEA03 and MEA04 elements will describe a measure of waste associated with the line item)

Value: [“WA”]

2 ID C1

MEA02 Tare Weight Identifier Code

Definition: The code identifying a specific product or process characteristic to which a measurement applies. In this case the value is “T” for Tare Weight. Tare Weight is the total weight of all packaging for an item.

Value: [“T”]

1 ID C1

MEA03 Tare Weight Value

Definition: The code identifying the Tare Weight Value

Value: [Tare Weight Value]

9,2 Decimal C1

MEA04 Tare Weight Unit of Measure

Definition: The Tare Weight Unit of Measure

Value: [Tare Weight Unit of Measure]

MEA01 Waste Identifier Code

Definition: The code identifying the broad category to which a measurement applies. In this case the value is “WA” for Waste.

(Meaning the following MEA02, MEA03 and

MEA02 Aluminum Identifier Code category to which a measurement applies. If the packaging is Aluminum a value of “ZAL” is entered. (Total weight of aluminum packaging for item)

Value: [“ZAL”]

3 ID C1

MEA03 Aluminum Weight Value

Definition: The Aluminum Weight Value

Value: [Aluminum Weight Value]

MEA04 Aluminum Weight Unit of Measure

Definition: The Aluminum Weight Unit of Measure

Value: [Aluminum Weight Unit of Measure]

MEA01

Waste Identifier Code category to which a measurement applies. In this case the value is “WA” for Waste.

(Meaning the following MEA02, MEA03 and

C1

MEA02 Tin Identifier Code category to which a measurement applies. If the packaging is Tin, a value of “ZSN” is entered.

(Total weight of tin packaging for item)

Value: [“ZSN”]

MEA03 Tin Weight Value

Definition: The Tin Weight Value

Value: [Tin Weight Value]

MEA04 Tin Weight Unit of Measure

Definition: The Tin Weight Unit of Measure

Value: [Tin Weight Unit of Measure]

MEA01 Waste Identifier Code category to which a measurement applies. In this case the value is “WA” for Waste.

(Meaning the following MEA02, MEA03 and

MEA02 Paper Identifier Code category to which a measurement applies. If the packaging is paper or cardboard, a value of “ZFL” is entered. (Total weight of paper and cardboard packaging for item)

Value: [“ZFL”]

MEA03 Paper Weight Value

Definition: The Paper Weight Value

Value: [Paper Weight Value]

MEA04 Paper Weight Unit of Measure

Definition: The Paper Weight Unit of Measure

Value: [Paper Weight Unit of Measure] category to which a measurement applies. In this case the value is “WA” for Waste.

(Meaning the following MEA02, MEA03 and

MEA02 Plastic Identifier Code category to which a measurement applies. If the packaging is Plastic, a value of “VIN” is entered. (Total weight of plastic packaging for item)

Value: [“VIN”]

MEA03 Plastic Weight Value

Definition: The Plastic Weight Value

Value: [Plastic Weight Value]

MEA04 Plastic Weight Unit of Measure

Definition: The Plastic Weight Unit of Measure

Value: [Plastic Weight Unit of Measure] category to which a measurement applies. In this case the value is “WA” for Waste.

(Meaning the following MEA02, MEA03 and

MEA02 Glass Identifier Code category to which a measurement applies. If the packaging is Glass, a value of “ZZZ” is entered.

(Total weight of glass packaging for item)

Value: [“ZZZ”]

MEA03 Glass Weight Value

Definition: The Glass Weight Value

Value: [Glass Weight Value]

MEA04 Glass Weight Unit of Measure

Definition: The Glass Weight Unit of Measure

Value: [Glass Weight Unit of Measure]

P04 Item Physical Detail

PO401 Units-per-purchase-pack

Definition: The number of inner pack units per outer pack unit

Value: [Units per purchase pack] Element Example: [24] Catalog Item Example: 24 -12 OZ CN

4 UI

PO402 Package-size

Definition: The size of supplier units in a pack

Value: [Package Size] Example: [12]

8 Explicit Decimal 2 “12345.78”

PO403 Package-unit-of-measure 2 AN M

Definition: The Unit of Measure

Value: [Package Unit of Measure] Example: [OZ] – Ounce

PO404 Packaging-code

Definition: The code identifying the type of packaging. (Note: must be “AVG” if item is catch weight)

Value: [Packaging Code] Example: [CAN] – Can

5 AN M

PO405 Not Used

PO406 Gross Weight/Pack

Definition: The numeric value of gross weight per pack

Value: [Gross Weight/Pack]

9,2 Decimal M

PO407 Gross Weight Unit

Definition: The Gross Weight Unit

Value: [Gross Weight Unit]

PO408 Gross Volume

Definition: The numeric value of gross volume per pack

Value: [Gross Volume]

9,2 Decimal M

PO409 Gross Volume Unit

Definition: The Gross Volume Unit in which a value is being expressed

Value: [Gross Volume Unit]

ITD Terms of Sale ITD01 Prompt Payment Act Identifier Code

Definition: The code identifying the type of payment terms. The value of 16 designates that the item is part of the Prompt Payment Act

Value: [“16”]

ITD02 Not Used ITD03 Not Used ITD04 Not Used ITD05 Not Used ITD06 Not Used ITD07 Not Used ITD08 Not Used ITD09 Not Used ITD10 Not Used ITD11 Not Used

ITD12 Brand Name

Definition: A description field that allows for entry of an 2 position State code for where the item was grown followed by a hyphen “-“ and the items Brand Name. The 2 position State Code is NOT mandatory for OCONUS Vendors. The hyphen is only required when State Code is present.

Value:[2 position State Code, “-“ (hyphen) and Brand Name] Example [PA-KC Mushrooms]

1-80 AN M

LDT Lead Time LDT01 Shelf Life Identifier Code

Definition: This code identifies the LDT line as dealing with Lead Time/Shelf Life for a stock item. It is a mutually defined Lead Time Code, where AU = Shelf Life

Value: [“AU”]

2 ID O

LDT02 Shelf Life

Definition: A numeric value designating the Shelf Life (the number of months or days) of the product.

Value: [Shelf Life]

3 Integer O

LDT03 Shelf life Unit

Definition: The unit of shelf life time – either months or days

Value: [Either “MO” – Month or “DY”- Day]

LDT Lead Time LDT01 Lead Time Identifier Code 2 ID O

Definition: A lead time code of “AF” indicates lead time from purchase order (PO) date to required delivery date (RDD)

Value: [“AF”]

LDT02 Required Lead Time in Days

Definition: The numeric quantity of the Required Lead Time Quantity in Days

Value: [Required lead time in days]

3 Integer O

LDT03 Calendar days

Definition: A code of ‘DA’ indicates the time period is in “Calendar Days”

Value: [“DA”]

DTM Date/Time Reference

DTM01 Voucher Date Identifier Code.

Definition: This code of ‘518’ indicates the Voucher Date of a manufacturing product purchased by the prime vendor

Value: [“518”]

3 ID C4

DTM02 MPA Purchase Date

Definition: This field allows entry of the MPA Purchase Date (required for OCONUS MPA items)

Value: [YYMMDD]

Date C4

SAC Service, Promotion, Allowance or Charge Information

SAC01 Allowance Identifier Code

Definition: This element is an allowance indicator

Value: [“A”]

1 ID C2

SAC02 NAPA Allowance Identifier Code

Definition: This allowance code of “C260” indicates a ‘Discount – Incentive (NAPA)

Value: [“C260”]

4 ID C2

SAC05 NAPA Allowance

Definition: The monetary amount of the NAPA Allowance. Must be prorated in accordance with the Unit of Measure of the Delivered Price of the item.

Value: [Napa Allowance $]

10,2 Decimal Explicit

C2

SAC02 Food Show Allowance Identifier Code

Definition: This allowance code of “C300” indicates a ‘Discount – Special (Food Show)

Value: [“C300”]

SAC05 Food Show Allowance

Definition: The monetary amount of the Food Show Allowance

Value: [Food Show Allowance $]

SAC02 Promotional Allowance Identifier Code

Definition: This allowance code of “C310” indicates a ‘Discount – Promotional’

Value: [“C310”]

SAC05 Promotional Allowance

Discount – Promotional Allowance

Value: [Promotional Allowance]

SAC01 Charge Identifier Code

Definition: This element is a charge indicator

Value: [“C”]

SAC02 Distribution Price Identifier Code

Definition: This charge code of “C330” indicates a ‘Distribution Price’

Definition (Fixed Unit Price): This charge code of “C330” indicates a ‘Distribution Price’ (storage and/or handling fee)

Value: [“C330”]

4 ID M

SAC03 Mutually Defined Identifier Code

Definition: The mutually agreed upon Agency Qualifier Code (between the Vendor and DLA)

SAC04 Distribution Price Category Code

Definition: The Agency maintained Distribution Price Category Code identifying the charge.

Definition (Fixed Unit Price): The Agency maintained Distribution Price (storage and/or handling fee) Category Code identifying the charge. For Fixed Unit Price (FUP) type contracts, where the item represents a Food Service Operating Supplies (FSOS) or a Producer Price Index (PPI) item, the value submitted should be “NA”

Value: [Distribution Price Category Code]

4 AN M

SAC05 Distribution Price for Unit of Measure

Distribution Price. If no Distribution Price is applicable, the value submitted should be 0.00.

Definition (Fixed Unit Price): The monetary amount of the Distribution Price (storage and/or handling fee). If no Distribution Price is applicable, the value submitted should be 0.00.

Value: [Distribution Price for Unit of Measure]

CTP Pricing Information

CTP01 Not used 2 ID O

CTP02 Standard Price Identifier Code

Definition: The standard price identifier code

Value: [STA]

CTP03 Unit price

Definition: The unit price per unit of product.

This price includes the distribution price per unit of measure, standard freight, and includes a reduction for all applicable allowances

Definition (Fixed Unit Price): The unit price per unit of product. This price contains all elements of price including the distribution price (storage and/or handling fee)

Value: [Unit Price]

CTP04 Catch weight multiple

Definition: The Catch Weight multiple number of units (in pounds (lbs.)) that must be ordered to purchase one case of product

Value: [Catch Weight Multiple Number of Units]

6 Integer (entered for catch weight items only) otherwise blank

C3

CTP05 Unit-of-measure

Definition: The standard Unit-of-Measure.

(Note: must be "LB" if item is catch weight) This is the unit that defines how the vendor sells the product, and represents the unit that the vendor price is based upon

Value: [Unit-of-Measure]

CTP06 Purchase Ratio Factor Identifier Code

Definition: The code identifying the Purchase Ratio Factor as ‘SEL’ – a selling multiplier

Value: [“SEL”]

CTP07 Ratio-numerator

Definition: The PRF is the ratio between the Unit of Issue (how DLA sells the item to the customer), and the Unit of Measure (how the vendor sells the product to the customer). It defines how many units of issue there are in one vendor unit of measure

Value: [Ratio-Numerator]

4 UI M

CTP08 Ratio-denominator

Definition: The PRF is the ratio between the Unit of Issue (how DLA sells the item to the customer), and the Unit of Measure (how the vendor sells the product to the customer). It defines how many units of issue there are in one vendor unit of measure.

Value: [Ratio-Denominator]

4 UI M

CTP01 Not Used CTP02 Product Price (Pertains to OCONUS contracts) / Delivered Price (Pertains to CONUS contracts) Identifier Code

Definition: The price identifier code.

Specifically the Manufacturer’s unit price (Price excluding distribution price but includes standard freight and a reduction for all applicable allowances per unit of measure)

Definition (Fixed Unit Price): The price identifier code. Specifically the unit price excluding distribution price (storage and/or handling fee) Value: [“PRO”]

CTP03 Product Price (Pertains to OCONUS contracts) / Delivered Price (Pertains to CONUS contracts)

Definition (Product Price): The Manufacturer unit price. This price excludes the distribution price but includes standard freight and a reduction for all applicable allowances per unit of measure

Definition (Delivered Price): The unit price excluding distribution price (storage and/or handling fee)

Value: [Product Price]

10 Explicit

R

CTP01 Not Used

CTP02 Additional Freight Charge Code

Definition: The Additional Freight Charge Code for the item being shipped/delivered.

This code indicates that CTP03 is additional freight charge.

Value: [“PPD”]

4 UI C6

CTP03 Additional Freight Charge Price

Definition: Additional Freight Charge fee for item being shipped /delivered

Value: [Additional Freight Price]

0 Explicit

R

C6

SE Transaction Set SE01 Number of included segments

Definition: The total number of elements included in a transaction set (including ST and SE elements)

1-10 AN M

Value: [Number of included elements]

Trailer SE02 Transaction Set Control Number

Definition: The identifying control number that must be unique within the transaction set functional group for a transaction set. *Note:

This is the final element in the 832 transaction set.

C1 = Conditional: Element is required if catalog is used for Navy standard core menu. C2 = Conditional: Item is required if allowance applies for this item C3 = Conditional: Element is required if item is a Catch-weight item.

C4 = Conditional : Element is mandatory for OCONUS contracts, while optional for others.

C5 = Conditional: Element is mandatory for CONUS Fixed Unit Price type contracts, while optional for others. C6 = Conditional: Element is mandatory for CONUS Alaska contracts, while optional for others.

832 Example File:

ISA~00~ ~00~ ~ZZ~ABC ~ZZ~S39017 ~120312~1234~U~

00200~000000593~0~P~^_

GS~SC~ABC~S39017~120312~1234~587~X~003040

ST~832~100535

BCT~PC~SPM30010DXXXX

DTM~152~120312~1234

LIN~1~SW~892501E19XXXX~VP~100068~ZZ~C~ZZ~00

REF~ZZ~SO

REF~ZZ~FS~N

REF~ZZ~SK~01232

REF~ZZ~DU~N

PID~F~GEN~~~CANDY, CHOC COV PEANUTS, PAN-COATED, ASST COLORS, 48/1.00 OZ PG~~~Y

PO4~48~1.00~OZ~PG~~1.00~CS~10.00~CS

ITD~16~~~~~~~~~~~MARS

LDT~AU~329~DY

LDT~AF~2~DA

SAC~A~C260

SAC~A~C300

SAC~A~C310

SAC~C~C330~ZZ~ 14~11.49

CTP~~STA~243.66~~CS~SEL~1~1

CTP~~PRO~100.00

LIN~2~SW~891501E09XXXX~VP~100041~ZZ~C~ZZ~03

REF~ZZ~SO

REF~ZZ~FS~N

REF~ZZ~SK~53181

REF~ZZ~DU~N

PID~F~GEN~~~RAISINS, SDLS, NAT, US GRA, 144/1.5 OZ PG~~~Y

PO4~144~1.00~OZ~PG~~10.00~CS~100.00~CS

ITD~16~~~~~~~~~~~REGENT

LDT~AU~546~DY

LDT~AF~2~DA

SAC~A~C260

SAC~A~C300

SAC~A~C310

SAC~C~C330~ZZ~ 14~11.49

CTP~~STA~10.00~~CS~SEL~1~1

CTP~~PRO~10.00

LIN~3~SW~892501E19XXXX~VP~181164~ZZ~C~ZZ~00

REF~ZZ~SO

REF~ZZ~FS~N

REF~ZZ~SK~65CLGF

REF~ZZ~DU~N

PID~F~GEN~~~HONEY, WHITE, US GRADE A, 5 LB CO, 6/CS~~~Y

PO4~6~1.00~LB~CO~~10.00~CS~100.00~CS

ITD~16~~~~~~~~~~~AMERICAN BOUNTY

LDT~AU~728~DY

LDT~AF~2~DA

SAC~A~C260

SAC~A~C300

SAC~A~C310

SAC~C~C330~ZZ~ 22~12.63

CTP~~STA~10.00~~CS~SEL~6~1

CTP~~PRO~10.00

CTT~3

SE~54~100535

GE~1~587

IEA~1~000000593

3.2 850 Purchase Order Version 3040 (Customer to Vendor) All STORES customer sites will use the 850 Purchase Order transaction set when ordering food. Multiple orders may be sent by customers to vendors at any time of the day.

ISA Id CHUCK1 GS Id CHUCK1

Points of contact for 850 EDI Testing are:

Lou Milano, louis.milano@dla.mil, 215-737-7315 Bill Saccone, charles.benn@dla.mil, 215-737-7318 Robert Thistle, robert.thistle@dla.mil 215-737-7558

Guidelines for 850 – Purchase Order

Segment Element Definition / Value Size ST Transaction Set Header

ST01 Transaction Set Identifier Code

Definition: Code uniquely identifying a transaction set.

Value: [“850”]

4/9 N

ST02 Transaction Set Control Number

Definition: This is the Transaction Set Control Number and holds the value of the unique identifying control number within the transaction set.

BEG Beginning Segment for Purchase Order

BEG01 Transaction Set Purpose Code

Purpose Code and the ‘00’ value indicates that this Purchase Order is the Original.

Value: [“00”]

2 AN

BEG02 Purchase Order Type Code

Definition: This is the Purchase Order Type Code and the value of ‘NE’ indicates that this is a new Order.

Value: [“NE”]

2 A mailto:louis.milano@dla.mil mailto:charles.benn@dla.mil

BEG03 Purchase Order Number

Definition: This is the purchase order number for the current order.

Value:[ Purchase Order Number]

14 AN

BEG04 Contract Order Number

Definition: Due to the PIID implementation, the Contract Order Number (Call Number) is no longer required.

Value: [NULL]

4 SPACES

BEG05 Contract Order Date

Definition: This is the Date the order was created.

Value: [Contract Order Date] date

BEG06 Contract Number

Definition: This is the contract number field and it holds the contract number for the contract that the customer will order from when placing orders.

Value [Contract Number]

13 AN

DTM Date/Time Reference

DTM01 Delivery Requested

Definition: This is a constant value of ‘002’ to indicate delivery requested.

Value: [“002”]

3 AN

DTM02 Required Delivery Date

Definition: This is the required delivery date for the items on the purchase order.

Value: [Required Delivery Date]

6 AN

N1 Name N101 Ship To

Definition: The constant value “ST” is required in this segment.

Value: [“ST”]

2 A

N102 Not Used N103 Department of Defense Activity Address

Code (DoDAAC)

Definition: The constant value “10” is required and indicates the next segment hold the DoDAAC.

Value: [“10”]

N104 Ship To Dodaac

Definition: This is the DoDAAC of the Ship To Address of the location to where the items will be shipped.

Value: [Ship To Dodaac]

6 AN

N2 Additional Name Information

N201 Ship To Facility Name or Number

Definition: This is the facility name or number of the location to where the items will be shipped.

Value: [Ship To Facility Name or Number]

35 AN

N202 Ship To Building Name Or Number

Definition: This is the building name or number of the location to where the items will be shipped.

Value: [Ship To Building Name Or Number]

N3 Address

N301 Ship To Address-1

Definition: This is the first line address of the ship to location to where the items will be shipped.

Value: [Ship To Address-1]

N302 Ship To Address-2

Definition: This is the second line address of the ship to location to where the items will be shipped.

Value: [Ship To Address-2]

N4 Geographic Location

N401 Ship To City

Definition: This is the City of the ship to location for the items that will be shipped.

Value: [Ship To City]

25 AN

N402 Ship To State

Definition: This is the State of the ship to location for the items that will be shipped.

Value: [Ship To State]

N403 Ship To Zip

Definition: This is the Zip Code of the ship to location for the items that will be shipped.

Value: [Ship To Zip]

9 UI

PO1 Baseline Item PO101 Line Item Number

Definition: This is the line item number for the item on the order. This is a sequential number for each new order.

Value: [Line Item Number]

PO102 Quantity

Definition: This is the quantity ordered for the item.

5 UI

Value: [Quantity]

PO103 Unit of Measure

Definition: The standard Unit of Measure

Value: [Unit of Measure]

PO104 Vendor Selling Price

Definition: This is the vendor’s selling price for the item

Value: [Vendor Selling Price]

10 explicit decimal 2 “1234567.90”

PO105 Not Used PO106 Vendor Part Number

“VP”. This value indicates that the next segment will hold the vendor’s part number.

Value: [“VP”]

PO107 Vendor Part Number

Definition: This is the vendor’s part number for the item being ordered.

Value: [Vendor Part Number]

25 AN

PO108 Stock-Number

“SW”. This value indicates that the next segment will contain the DLA stock number.

Value: [“SW”]

15 AN

PO109 Stock Number

Definition: This is the DLA stock number for the item being ordered.

15 AN

Value: [Stock Number]

PO110 Mutually Defined

Definition: This is a constant value of ‘ZZ’ and it means that the next element is mutually defined element between DLA Troop Support and the STORES EDI vendor.

PO111 FIC

Definition: This is the Food Identification Code (FIC). The FIC is used by Navy ordering sites only. It is the identification code used to identify an item on the catalog or order.

Value: [FIC]

PID

Production/Item Description

PID01 Free Form

Definition: The code indicating the format of the DLA Troop Support Item Description.

Value: [“F”]

PID02 Not Used PID03 Not Used PID04 Not Used

PID05 DLA Troop Support Item Description

Definition: This is the DLA Troop Support item description of the item that is on the order. The description is taken from the DLA Troop Support catalog.

Value: [DLA Troop Support Item Description]

80 AN

CTT Transaction Totals

CTT01 Line Item Number

Definition: This is the total number of line items in the purchase order.

Value: [Line Item Number]

CTT02 Total Purchase Order Dollar

Definition: This is the total dollar value for the purchase order.

Value:[Total Purchase Order Dollar]

12 Explicit Decimal 2

SE Segment Elements

SE01 Number Of Included Segments

Definition: This is the number of ST segments in the transaction

Value: [Number Of Included Segments]

1/10 N

SE02 Transaction Set Control Number

Control Number and holds the value of the unique identifying control number within the transaction set. It should match the Transaction Set Control Number used in the ST02 element.

4/9 AN

850 Example File:

ISA*00* *00* *ZZ* CHUCK1 *ZZ*STORES *120214*2103*U*00200*000001161*0*P*<~

GS*PO*CHUCK1*STORES*120214*2103*1161*X*003040

ST*850*000000001

BEG*00*NE* CHUCK120455695* *120214*SPM30011DXXXX

DTM*002*120221

N1*ST*SAM CAFE*10* CHUCK1

N2*SAM CAFE*BLDG# 335

N3*SAM CAFE*A1C REEDY

N4*Philadelphia*PA*19111

PO1*0086*88*LB*1.97**VP*11111*SW*891501E213585*ZZ*V03

PID*F****APPLES, EATING, RED, SWT, FRESH, BU

PO1*0087*88*LB*2.06**VP*2222*SW*891501E213586*ZZ*V04

PID*F****APPLES, EATING, YELLOW, FRESH, BULK

PO1*0088*81*LB*.8**VP*33333*SW*891501E213590*ZZ*V11

PID*F****BANANAS, FRESH, BULK, BUY IN 1 LB I

PO1*0089*108*LB*.83**VP*44444*SW*891501E211702

PID*F****BANANAS, FRESH, NMT, 4L, BULK, BUY

PO1*0090*4*CS*20.94**VP*55555*SW*891001E299881*ZZ*U47

PID*F****CHEESE, COTTAGE, CHL, ESL, SMALL CU

PO1*0091*11*LB*3.25**VP*66666*SW*891501E213599*

ZZ*V42

PID*F****CUCUMBERS, BULK, FRESH, US

NO. 1 GR

PO1*0092*36*LB*2.28**VP*77777*SW*891501

E213252

PID*F****GRAPES,FRESH,RED,GLOBE,BULK,US NO.

PO1*0093*54*LB*.99**VP*88888*SW*891501E213604*

ZZ*V61

PID*F****HONEYDEW MELONS, FRESH, BULK, US NO

PO1*0094*28*LB*3.33**VP*99999*SW*891501E213605*ZZ*V66

PID*F****KIWIFRUIT, FRESH, BULK, US GR NO. 1

PO1*0095*72*LB*2.37**VP*12222*SW*891501E213607*ZZ*V69

PID*F****LETTUCE, ICEBERG, FRESH, BULK, US N

PO1*0096*11*LB*2.95**VP*212222*SW*891501E213614*

ZZ*V87

PID*F****ONIONS, GREEN, FRESH, US NO. 1

GR,

PO1*0097*88*LB*.67**VP*323333*SW*891501

E310466

PID*F****ONIONS, YELLOW, LG, DRY, BUY IN 1 L

PO1*0098*22*LB*3.94**VP*434444*SW*891501E213620*Z

Z*W02

PID*F****PEPPERS, BELL, SWT, FRESH, US NO 1

PO1*0099*66*LB*1.07**VP*545555*SW*891501E213622*ZZ*W07

PID*F****PINEAPPLE, FRESH, BULK, US NO.

1 GR

PO1*0100*66*LB*.85**VP*656666*SW*891501

E211782

PID*F****POTATOES, FRESH, MAYQUEEN 2L, US#1

PO1*0101*44*LB*.82**VP*177777*SW*891501E213626*ZZ*W15

PID*F****POTATOES, WHITE, FRESH, FOR

BAKING,

PO1*0102*72*LB*3.08**VP*3288888*SW*891501

E211785

PID*F****TOMATOES, FRESH, LARGE, US#1 OR LOC

PO1*0103*18*CS*6.6**VP*888655*SW*891001E391626*

ZZ*U95

PID*F****YOGURT, REG, VARIETY, CHL, ESL, FRU

PO1*0104*34*LB*1.14**VP*655555*SW*891501E213601*

ZZ*V54

PID*F****GRAPEFRUIT, FRESH, US NO. 1 GRADE,

PO1*0105*190*LB*1.21**VP*867567676*SW*891501E213615*ZZ*V89

PID*F****ORANGES, FRESH, ANY VARIETY EXCEPT

PO1*0106*44*LB*1.37**VP*32323111*SW*891501E213633*Z

Z*W39

PID*F****TANGERINES, FRESH, BULK, US NO. 1 G

CTT*21*2038.4

SE*51*000000001

GE*1*1161

IEA*1*000001161

3.3 810 INVOICE - VERSION 4010

This standard contains the format and establishes the data contents of the Invoice. The transaction set is used for customary and established business and industry practice relative to the billing for goods and services provided.

Points of contact for 810 Invoice Testing are:

Karen Conroy-Hegarty, karen.hegarty@dla.mil, 215-737-7550

Guidelines for 810 – Invoices

Transaction Set Header (ST)

Definition: Code uniquely identifying…