DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 1 September 12, 2023

830 Planning Schedule with Release Capability

Functional Group=PS

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with

Release Capability Transaction Set (830) 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 practice relative to the transfer of forecasting/material

release information between organizations.The planning schedule transaction may be used in various ways or in a combination of

ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or

material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations,

period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in "buckets,"

such as weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders, as required,

because the order release capability eliminates the need for discrete generation of purchase orders.

DLMS Note:

1. Use a single occurrence of this transaction set to transmit Demand Data Exchange (DDE) Projected Supply Plan transactions to

one or more Inventory Control Points (ICPs)/Integrated Material Managers (IMMs). At this time, DDE Projected Supply Plans are

only submitted to the Defense Logistics Agency (DLA) ICP/IMM.” Use one occurrence of this transaction set to transmit a single or

multiple transactions. DoD logistics users should refer to the Defense Logistics Management Standards (DLMS) Implementation

Convention (IC) available at URL: www.dla.mil/does/DLMS. The DLMS IC provides specific business rules, conditions, and

authorized codes necessary for appropriate use of this IC within the DLMS.

2. The Demand Data Exchange Projected Supply Plan transaction is a DLMS enhancement. There is no corresponding DLSS

transaction; however this transaction encompasses functionality of non-DLSS DLA legacy Document Identifier Code (DIC) CDD.

See introductory DLMS note 4a.

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase

Unit Conversion Table which can be found on the Defense Enterprise Data Standards Office (DEDSO) Web site at

www.dla.mil/does/DLMS.

4. This DLMS Implementation Convention contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing

system. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be

received or understood by the recipient's automated processing system. Components must coordinate implementation with DEDSO

prior to use.

c. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support

transaction conversion in a mixed DLSS/DLMS environment. This data will be streamlined out once full DLMS implementation is

reached. Components may coordinate with DEDSO for early termination (or retention) of specific data requirements for users

operating in a full DLMS environment.

5. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDC) and Approved DLMS Changes (ADC) listed.

PDCs/ADCs are available from the DEDSO Web site at:

http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 278, Establish New DS 830D, Version 4030, for Demand Data Exchange (DDE) Projected Supply Plan, in Place of DS 830R,

Version 4030, Special Program Requirements (SPR)/DDE Forecast

- ADC 284, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock

Positioning (IMSP)

- ADC 284A, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock

Positioning (IMSP)

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes

and Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1082, Administrative Update to DLMS 830D, Demand Data Exchange (DDE) Projected Supply Plan

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on February 26, 2014.

- ADC 1105, Revise DLMS 830D Demand Data Exchange (DDE) Projected Supply Plan Requirements to Clarify Data and

Associated Procedures

- ADC 1138, Revise DLMS 830D Demand Data Exchange (DDE) Projected Supply Plan to provide an FST04 Date Representing

the Start Date of Forecast Bucket (Supply)

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 27, 2016

- ADC 1267, Revise DLMS 830D to Accommodate Navy Fleet Readiness Centers (FRC) Gross Demand Plan (GDP) for 

1. Use a single occurrence of this transaction set to transmit Demand Data Exchange (DDE) Projected Supply Plan transactions to

one or more Inventory Control Points (ICPs)/Integrated Material Managers (IMMs). At this time, DDE Projected Supply Plans are

only submitted to the Defense Logistics Agency (DLA) ICP/IMM.” Use one occurrence of this transaction set to transmit a single or

multiple transactions. DoD logistics users should refer to the Defense Logistics Management Standards (DLMS) Implementation

Convention (IC) available at URL: www.dla.mil/does/DLMS. The DLMS IC provides specific business rules, conditions, and

authorized codes necessary for appropriate use of this IC within the DLMS.

2. The Demand Data Exchange Projected Supply Plan transaction is a DLMS enhancement. There is no corresponding DLSS

transaction; however this transaction encompasses functionality of non-DLSS DLA legacy Document Identifier Code (DIC) CDD.

See introductory DLMS note 4a.

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase

Unit Conversion Table which can be found on the Defense Enterprise Data Standards Office (DEDSO) Web site at

www.dla.mil/does/DLMS.

4. This DLMS Implementation Convention contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing

system. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be

received or understood by the recipient's automated processing system. Components must coordinate implementation with DEDSO

prior to use.

c. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support

transaction conversion in a mixed DLSS/DLMS environment. This data will be streamlined out once full DLMS implementation is

reached. Components may coordinate with DEDSO for early termination (or retention) of specific data requirements for users

operating in a full DLMS environment.

5. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDC) and Approved DLMS Changes (ADC) listed.

PDCs/ADCs are available from the DEDSO Web site at:

http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 278, Establish New DS 830D, Version 4030, for Demand Data Exchange (DDE) Projected Supply Plan, in Place of DS 830R,

Version 4030, Special Program Requirements (SPR)/DDE Forecast

- ADC 284, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock

Positioning (IMSP)

- ADC 284A, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock

Positioning (IMSP)

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes

and Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1082, Administrative Update to DLMS 830D, Demand Data Exchange (DDE) Projected Supply Plan

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on February 26, 2014.

- ADC 1105, Revise DLMS 830D Demand Data Exchange (DDE) Projected Supply Plan Requirements to Clarify Data and

Associated Procedures

- ADC 1138, Revise DLMS 830D Demand Data Exchange (DDE) Projected Supply Plan to provide an FST04 Date Representing

the Start Date of Forecast Bucket (Supply)

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 27, 2016

- ADC 1267, Revise DLMS 830D to Accommodate Navy Fleet Readiness Centers (FRC) Gross Demand Plan (GDP) for 
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 2 September 12, 2023

Implementation by all DOD Components

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) -

Completed on 1/27/20

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data

Standards Office (DEDSO) - Completed on March 1, 202

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds

Transfer Indicator to Wide Area Workflow

- ADC 1454, Expand Use of Shop Service Center Codes in Defense Logistics Management Standards Transactions

Implementation by all DOD Components

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) -

Completed on 1/27/20

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data

Standards Office (DEDSO) - Completed on March 1, 202

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds

Transfer Indicator to Wide Area Workflow

- ADC 1454, Expand Use of Shop Service Center Codes in Defense Logistics Management Standards Transactions

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

0100 ST Transaction Set Header M 1 Must use

0200 BFR Beginning Segment for Planning

Schedule

M 1 Must use

* 0250 XPO Preassigned Purchase Order

Numbers

O >1 Not Used

* 0400 CUR Currency O 1 Not Used

* 0500 REF Reference Identification O 12 Not Used

* 0600 PER Administrative Communications

Contact

O 3 Not Used

* 0700 TAX Tax Reference O 3 Not Used

* 0800 FOB F.O.B. Related Instructions O 1 Not Used

* 0900 CTP Pricing Information O 25 Not Used

* 1000 SAC Service, Promotion, Allowance,

or Charge Information

O 25 Not Used

* 1100 CSH Sales Requirements O 1 Not Used

* 1200 ITD Terms of Sale/Deferred Terms

of Sale

O 2 Not Used

* 1300 DTM Date/Time Reference O 10 Not Used

* 1400 PID Product/Item Description O 200 Not Used

* 1500 MEA Measurements O 40 Not Used

* 1600 PWK Paperwork O 25 Not Used

* 1700 PKG Marking, Packaging, Loading O 25 Not Used

* 1800 TD1 Carrier Details (Quantity and

Weight)

O 2 Not Used

* 1900 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 12 Not Used

* 2000 TD3 Carrier Details (Equipment) O 12 Not Used

* 2100 TD4 Carrier Details (Special

Handling, or Hazardous

Materials, or Both)

O 5 Not Used

* 2200 MAN Marks and Numbers O 10 Not Used

LOOP ID - N1 LOOP ID - N1 200

2300 N1 Name O 1 Must use

* 2400 N2 Additional Name Information O 2 Not Used

* 2500 N3 Address Information O 2 Not Used

* 2600 N4 Geographic Location O 1 Not Used

* 2700 REF Reference Identification O 12 Not Used

* 2800 PER Administrative Communications

Contact

O 3 Not Used

* 2900 FOB F.O.B. Related Instructions O 1 Not Used

* LOOP ID - LM * LOOP ID - LM >1

* 3000 LM Code Source Information O 1 Not Used

3100 LQ Industry Code M 100 Must use
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F830D1DA10 3 September 12, 2023

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - LIN LOOP ID - LIN >1

0100 LIN Item Identification M 1 Must use

* 0200 UIT Unit Detail O 1 Not Used

* 0210 DTM Date/Time Reference O 10 Not Used

* 0300 CUR Currency O 1 Not Used

* 0600 PO3 Additional Item Detail O 25 Not Used

* 0700 CTP Pricing Information O 25 Not Used

* 0800 PID Product/Item Description O 1000 Not Used

* 0900 MEA Measurements O 40 Not Used

1000 PWK Paperwork O 25 Used

* 1100 PKG Marking, Packaging, Loading O 25 Not Used

* 1200 PO4 Item Physical Details O 1 Not Used

* 1300 PRS Part Release Status O 1 Not Used

1400 REF Reference Identification O 12 Must use

1500 PER Administrative Communications

Contact

O 3 Used

* 1700 SAC Service, Promotion, Allowance,

or Charge Information

O 25 Not Used

* 1800 ITD Terms of Sale/Deferred Terms

of Sale

O 2 Not Used

* 1900 TAX Tax Reference O 3 Not Used

* 2000 FOB F.O.B. Related Instructions O 1 Not Used

* 2100 LDT Lead Time O 12 Not Used

* 2200 QTY Quantity O >1 N2/2200 Not Used

* 2300 ATH Resource Authorization O 20 Not Used

* 2400 TD1 Carrier Details (Quantity and

Weight)

O 1 Not Used

* 2500 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 12 Not Used

* 2600 TD3 Carrier Details (Equipment) O 12 Not Used

* 2700 TD4 Carrier Details (Special

Handling, or Hazardous

Materials, or Both)

O 5 Not Used

* 2800 MAN Marks and Numbers O 10 Not Used

* 2900 DD Demand Detail O 10 Not Used

* LOOP ID - SLN * LOOP ID - SLN 100

* 3000 SLN Subline Item Detail O 1 Not Used

* 3100 PID Product/Item Description O 1000 Not Used

* 3150 NM1 Individual or Organizational

Name

O 10 Not Used

LOOP ID - N1 LOOP ID - N1 200

3200 N1 Name O 1 Must use

* 3300 N2 Additional Name Information O 2 Not Used

* 3400 N3 Address Information O 2 Not Used

* 3500 N4 Geographic Location O 1 Not Used

* 3600 REF Reference Identification O 12 Not Used

* 3700 PER Administrative Communications

Contact

O 3 Not Used
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F830D1DA10 4 September 12, 2023

* 3800 FOB F.O.B. Related Instructions O 1 Not Used

LOOP ID - LM LOOP ID - LM >1

3900 LM Code Source Information O 1 Used

4000 LQ Industry Code M 100 Must use

LOOP ID - FST LOOP ID - FST >1 N2/4100L N2/4100L

4100 FST Forecast Schedule O 1 N2/4100 Must use

* 4150 QTY Quantity O >1 Not Used

4200 SDQ Destination Quantity O 50 Used

* LOOP ID - LM * LOOP ID - LM >1

* 4300 LM Code Source Information O 1 Not Used

* 4400 LQ Industry Code M 100 Not Used

* LOOP ID - SDP * LOOP ID - SDP 260

* 4500 SDP Ship/Delivery Pattern O 1 Not Used

* 4600 FST Forecast Schedule O 260 Not Used

* LOOP ID - SHP * LOOP ID - SHP 25

* 4700 SHP Shipped/Received Information O 1 Not Used

* 4800 REF Reference Identification O 5 Not Used

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

* 0100 CTT Transaction Totals O 1 N3/0100 Not Used

0200 SE Transaction Set Trailer M 1 Must use

Notes: 

2/2200 QTY is used to specify supplemental quantities relevant to the forecast function. However, QTY is not related to the actual

forecast quantity in the FST segments.

2/4100L At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. These two loops are

mutually exclusive.

2/4100 At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. These two loops are

mutually exclusive.

3/0100 Number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash total (CTT02) is the sum

of the values of the quantities (FST01) for each FST segment.
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 5 September 12, 2023

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 3

User Option (Usage): Must use

Purpose: To indicate the start of a transaction set and to assign a control number

Semantics: 

1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate

transaction set definition (e.g., 810 selects the Invoice Transaction Set).

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use

Code Name

830 Planning Schedule with Release Capability

ST02 329 Transaction Set Control Number

Description: Identifying control number that

must be unique within the transaction set

functional group assigned by the originator for a

transaction set

DLMS Note: A unique number assigned by the

originator of the transaction set, or the

originator's application program.

M AN 4/9 Must use

ST03 1705 Implementation Convention Reference

Description: Reference assigned to identify

Implementation Convention

DLMS Note: Use to indicate this transmission

uses the 830D DLMS Implementation

Convention (IC). Enter the DLMS IC

004030F830D0DA00.

O AN 1/35 Used
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 6 September 12, 2023

BFR Beginning Segment for Planning

Schedule

Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 9

User Option (Usage): Must use

Purpose: To indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast; and related

forecast envelope dates

Syntax Rules: 

1. R0203 - At least one of BFR02 or BFR03 is required.

Semantics: 

1. If BFR01 contains the value "04" (Net Change), BFR09 is required.

2. BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.

3. BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins.

4. BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends.

5. BFR08 is the date forecast generated: The date the forecast data was generated.

6. BFR09 is the date forecast updated: The date the forecast was updated with "net change" data. (Used only when data element

353 in BFR01 contains the value "04", meaning net change.)

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

BFR01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

M ID 2/2 Must use

Code Name

00 Original

77 Simulation Exercise

DLMS Note:

Use to identify a simulated mobilization exercise transaction set. Activities initiating simulated

mobilization exercises must ensure complete coordination with all activities involved. All

transaction set recipients must use extreme caution to ensure that individual transactions do not

process as action documents which affect accountable records.

BFR02 127 Reference Identification

Description: Reference information as defined

for a particular Transaction Set or as specified by

the Reference Identification Qualifier

DLMS Note: Use code "Z" for this data element

to satisfy mandatory X12 syntax requirements.

X AN 1/50 Used

BFR04 675 Schedule Type Qualifier

Description: Code identifying the type of dates

used when defining a shipping or delivery time in

a schedule or forecast

M ID 2/2 Must use

Code Name

PR Planned Requirement Based

DLMS Note:

Use to indicate that data reflect DDE Projected Supply Plan requirements.

BFR05 676 Schedule Quantity Qualifier

Description: Code identifying the type of

M ID 1/1 Must use
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

Ref Id Element Name Req Type Min/Max Usage

004030F830D1DA10 7 September 12, 2023

quantities used when defining a schedule or

forecast

Code Name

A Actual Discrete Quantities

DLMS Note:

Use to indicate that quantities reflect discrete requirements.

BFR06 373 Date

Description: Date expressed as CCYYMMDD

DLMS Note: Must use to identify the projected

supply plan period start date for which all

identified materiel support should be available. 

This date represents the outside start date for all

table 2 iterations.

DLMS Note: Must use to identify the projected

supply plan period start date for which all

identified materiel support should be available. 

This date represents the outside start date for all

table 2 iterations.

M DT 8/8 Must use

BFR07 373 Date

Description: Date expressed as CCYYMMDD

DLMS Note: Must use to identify the projected

supply plan period end date for which all

identified materiel support should be available. 

This date represents the outside end date for all

table 2 iterations.

DLMS Note: Must use to identify the projected

supply plan period end date for which all

identified materiel support should be available. 

This date represents the outside end date for all

table 2 iterations.

O DT 8/8 Used

BFR08 373 Date

Description: Date expressed as CCYYMMDD

DLMS Note: Use to identify the transaction set

preparation date. This date corresponds to the

Universal Time Coordinate (UTC).

M DT 8/8 Must use

BFR12 783 Planning Schedule Type Code

Description: Code identifying type of planning

schedule used

O ID 2/2 Used

Code Name

AA Customized Ordering Forecast

DLMS Note:

Must use to indicate the transaction is a DDE Projected Supply Plan.

BFR13 306 Action Code

Description: Code indicating type of action

O ID 1/2 Used

Code Name

FI File

DLMS Note:

Authorized only for DAAS use to provide an information only image of the demand data

exchange projected supply plan transaction to DLA RIC-TO SMS when DLA is not the source of

supply.
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 8 September 12, 2023

N1 Name Pos: 2300 Max: 1

Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency

the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

Must use this 1/N1/2300 loop to identify the organization originating the transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N101 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an

individual

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

Code Name

41 Submitter

DLMS Note:

Must use to identify the submitter of the DDE requirement.

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Used

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

Use to identify the submitter.

N104 67 Identification Code

Description: Code identifying a party or other

code

X AN 2/80 Must use

N106 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an

individual

O ID 2/3 Used

Code Name

FR Message From

DLMS Note:
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

Code Name

004030F830D1DA10 9 September 12, 2023

Must use to indicate the organization cited in N104 is originating the transaction set.
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 10 September 12, 2023

LIN Item Identification Pos: 0100 Max: 1

Detail - Mandatory

Loop: LIN Elements: 3

User Option (Usage): Must use

Purpose: To specify basic item identification data

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 

1. LIN01 is the line item identification

Comments: 

1. See the Data Dictionary for a complete list of IDs.

2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No.,

U.P.C. No., ISBN No., Model No., or SKU.

DLMS Note:

Must use the 2/LIN/0100 loop to identify the type of transaction, materiel, transaction number, and information associated with the

projected requirement.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LIN01 350 Assigned Identification

Description: Alphanumeric characters assigned

for differentiation within a transaction set

DLMS Note: C - Cancellation of previously

submitted DDE Projected Supply Plan

transaction. Use indicates cancellation of the

entire open DDE transaction for the NIIN cited in

LIN02/03. This equates to DLA’s legacy DIC

CDD format with an ‘R’ in rp 952.

DLMS Note: C - Cancellation of previously

submitted DDE Projected Supply Plan

transaction. Use indicates cancellation of the

entire open DDE transaction for the NIIN cited in

LIN02/03. This equates to DLA’s legacy DIC

CDD format with an ‘R’ in rp 952.

H - DDE Projected Supply Plan transaction

submission for the NIIN cited in LIN02/03.

O AN 1/20 Used

LIN02 235 Product/Service ID Qualifier

Description: Code identifying the type/source of

the descriptive number used in Product/Service

ID (234)

M ID 2/2 Must use
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

Ref Id Element Name Req Type Min/Max Usage

004030F830D1DA10 11 September 12, 2023

DLMS Note: The following codes are authorized.

Code Name

FS National Stock Number

SW Stock Number

DLMS Note:

Use to identify a local stock number (LSN). 

ZZ Mutually Defined

DLMS Note:

Use to identify the National Item Identification Number (NIIN) for Demand Data Exchange

transactions. 

A data maintenance action was approved in version 5020. The approved code/name is "NN -

National Item Identification Number".

LIN03 234 Product/Service ID

Description: Identifying number for a product or

service

M AN 1/48 Must use
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 12 September 12, 2023

PWK Paperwork Pos: 1000 Max: 25

Detail - Optional

Loop: LIN Elements: 2

User Option (Usage): Used

Purpose: To identify the type or transmission or both of paperwork or supporting information

Syntax Rules: 

1. P0506 - If either PWK05 or PWK06 is present, then the other is required.

Comments: 

1. PWK05 and PWK06 may be used to identify the addressee by a code number.

2. PWK07 may be used to indicate special information to be shown on the specified report.

3. PWK08 may be used to indicate action pertaining to a report.

DLMS Note:

1. This segment contains free form text which the DDE submitter may use to provide information of value to the collaboration

participants. This field may also be used by the submitter to provide information deemed useful to their planners during

collaboration as it will be available for their viewing in the Collaborate tool. This segment is optional and informational in nature; the

information in this segment shall be perpetuated into the Collaborate tool and can be viewed by all participants in the collaboration

process. DLA will perpetuate the information in this segment and it will be visible in the online Collaborate tool as a drill down field.

2. On an interim basis, to accommodate DLA’s DIC CDD format in a mixed DLMS/non-DLMS CDD environment, the free form text

in the PWK segment is limited to a total of 110 characters which maps to DIC CDD Optional fields 1 through 4 in record positions

953-1062. To accommodate DLA DIC CDD fixed format, this requires restricting use of PWK segment to a maximum 4 iterations,

with maximum 20 characters each in 3 iterations and maximum of 50 characters in one iteration. This supports DLA DIC CDD

which has 3 optional fields of 20 characters and 1 optional field of 50 characters. 

3. When providing a Fund Identification Number (2/REF/1400 Code FG), the first occurrence of 2/PWK02/1000 cannot exceed 19

characters. Refer to ADC 1267. Use of PWK segment, other than as described in notes 2 and 3 is a DLMS enhancement. See

introductory DLMS note 4a.

1. This segment contains free form text which the DDE submitter may use to provide information of value to the collaboration

participants. This field may also be used by the submitter to provide information deemed useful to their planners during

collaboration as it will be available for their viewing in the Collaborate tool. This segment is optional and informational in nature; the

information in this segment shall be perpetuated into the Collaborate tool and can be viewed by all participants in the collaboration

process. DLA will perpetuate the information in this segment and it will be visible in the online Collaborate tool as a drill down field.

2. On an interim basis, to accommodate DLA’s DIC CDD format in a mixed DLMS/non-DLMS CDD environment, the free form text

in the PWK segment is limited to a total of 110 characters which maps to DIC CDD Optional fields 1 through 4 in record positions

953-1062. To accommodate DLA DIC CDD fixed format, this requires restricting use of PWK segment to a maximum 4 iterations,

with maximum 20 characters each in 3 iterations and maximum of 50 characters in one iteration. This supports DLA DIC CDD

which has 3 optional fields of 20 characters and 1 optional field of 50 characters. 

3. When providing a Fund Identification Number (2/REF/1400 Code FG), the first occurrence of 2/PWK02/1000 cannot exceed 19

characters. Refer to ADC 1267. Use of PWK segment, other than as described in notes 2 and 3 is a DLMS enhancement. See

introductory DLMS note 4a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

PWK01 755 Report Type Code

Description: Code indicating the title or contents

of a document, report or supporting item

DLMS Note: The following codes are authorized.

M ID 2/2 Must use

Code Name

R6 Miscellaneous Information

PWK07 352 Description

Description: A free-form description to clarify

the related data elements and their content

O AN 1/80 Used
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 13 September 12, 2023

REF Reference Identification Pos: 1400 Max: 12

Detail - Optional

Loop: LIN Elements: 2

User Option (Usage): Must use

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

DLMS Note:

Must use to identify the transaction document number associated with the DDE Projected Supply Plan.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

Code Name

FG Fund Identification Number

DLMS Note:

For Navy, this is a Program Funding Indicator associated to a Gross Demand Plan (GDP). See

ADC 1267

TN Transaction Reference Number

DLMS Note:

Use to identify the transaction document number.

REF02 127 Reference Identification

Description: Reference information as defined

for a particular Transaction Set or as specified by

the Reference Identification Qualifier

X AN 1/50 Used
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 14 September 12, 2023

PER Administrative Communications

Contact

Pos: 1500 Max: 3

Detail - Optional

Loop: LIN Elements: 9

User Option (Usage): Used

Purpose: To identify a person or office to whom administrative communications should be directed

Syntax Rules: 

1. P0304 - If either PER03 or PER04 is present, then the other is required.

2. P0506 - If either PER05 or PER06 is present, then the other is required.

3. P0708 - If either PER07 or PER08 is present, then the other is required.

DLMS Note:

1. Use to identify a contact to whom inquiries regarding this transaction can be directed.

2. Use multiple repetitions when needed to identify multiple points of contact or communication numbers. When using multiple

repetitions to identify different communication numbers for a single point of contact, repeat the name cited in PER02.

3. DLMS enhancement. See introductory DLMS note 4a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

PER01 366 Contact Function Code

Description: Code identifying the major duty or

responsibility of the person or group named

DLMS Note: The following codes are authorized.

M ID 2/2 Must use

Code Name

IC Information Contact

DLMS Note:

Use to identify the point of contact.

PER02 93 Name

Description: Free-form name

DLMS Note: Provide the last name, first name,

middle initial and rate/rank/title, as required, of

the individual named as point of contact. Include

blank spaces between name components and

periods after initials. Do not include NMN or NMI

when a middle initial is not available. 

DLMS Note: Provide the last name, first name,

middle initial and rate/rank/title, as required, of

the individual named as point of contact. Include

blank spaces between name components and

periods after initials. Do not include NMN or NMI

when a middle initial is not available. 

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: 1. The following codes are

authorized.

2. Do not include blank spaces, dashes, or

parentheses between numbers. 

O ID 2/2 Used

Code Name

AU Defense Switched Network

DLMS Note:

Use to identify the DSN telephone number.

EM Electronic Mail
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

Code Name

004030F830D1DA10 15 September 12, 2023

EX Telephone Extension

DLMS Note:

Use immediately following codes AU, IT or TE to identify a telephone extension.

FX Facsimile

DLMS Note:

Use to identify the commercial facsimile (FAX) telephone number. Include the area code and

number.

IT International Telephone

DLMS Note:

Include country and city code.

TE Telephone

DLMS Note:

Use to identify the commercial telephone number. Include the area code and number.

WF Work Facsimile Number

DLMS Note:

Use to identify the DSN FAX telephone number. 

PER04 364 Communication Number

Description: Complete communications number

including country or area code when applicable

O AN 1/256 Used

PER05 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: 1. Use to identify a second

communications number for the party cited in

PER02. For example, if PER03/04 cites a

commercial telephone number, PER05/06 can be

used to cite an Electronic Mail Address.

DLMS Note: 1. Use to identify a second

communications number for the party cited in

PER02. For example, if PER03/04 cites a

commercial telephone number, PER05/06 can be

used to cite an Electronic Mail Address.

2. Do not include blank spaces, dashes, or

parentheses between numbers.

3. The following codes are authorized.

O ID 2/2 Used

Code Name

AU Defense Switched Network

DLMS Note:

Use to identify the DSN telephone number.

EM Electronic Mail

EX Telephone Extension

DLMS Note:

Use immediately following codes AU, IT or TE to identify a telephone extension. 

FX Facsimile

DLMS Note:

Use to identify the commercial facsimile (FAX) telephone number. Include the area code and

number.

IT International Telephone

DLMS Note:

Include country and city code.

TE Telephone

DLMS Note:

Use to identify the commercial telephone number. Include the area code and number.
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

Code Name

004030F830D1DA10 16 September 12, 2023

WF Work Facsimile Number

DLMS Note:

Use to identify the DSN FAX telephone number. 

PER06 364 Communication Number

Description: Complete communications number

including country or area code when applicable

O AN 1/256 Used

PER07 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: 1. Use to identify a third

communications number for the party cited in

PER02.

2. Do not include blank spaces, dashes, or

parentheses between numbers.

3. The following codes are authorized. 

O ID 2/2 Used

Code Name

AU Defense Switched Network

DLMS Note:

Use to identify the DSN telephone number.

EM Electronic Mail

EX Telephone Extension

DLMS Note:

Use immediately following codes AU, IT or TE to identify a telephone extension.

FX Facsimile

DLMS Note:

Use to identify the commercial facsimile (FAX) telephone number. Include the area code and

number.

IT International Telephone

DLMS Note:

Include country and city code.

TE Telephone

DLMS Note:

Use to identify the commercial telephone number. Include the area code and number.

WF Work Facsimile Number

DLMS Note:

Use to identify the DSN FAX telephone number.

PER08 364 Communication Number

Description: Complete communications number

including country or area code when applicable

O AN 1/256 Used

PER09 443 Contact Inquiry Reference

Description: Additional reference number or

description to clarify a contact number

DLMS Note: Use to indicate the office symbol or

activity code for the identified party.

O AN 1/20 Used
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 17 September 12, 2023

N1 Name Pos: 3200 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency

the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

1. Must use one iteration of this 2/N1/3200 loop to identify the organization to receive the transaction.

2. Use additional iterations to identify other organizations associated with the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N101 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an

individual

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

Code Name

KA Item Manager

DLMS Note:

Must use to identify the ICP/IMM.

LW Customer

DLMS Note:

Use to identify the requisitioner (Sold-to) DoDAAC for DDE Projected Supply Plan transactions. 

This is the DoDAAC of the requisitioning (customer) organization. The requisitioner (Sold-to)

DoDAAC is found in the first six positions of a requisition document number. In many cases the

requisitioner (Sold-to) DoDAAC and the Ship-to DoDAAC will be the same in the transaction.

ST Ship To

DLMS Note:

Must use to identify the Ship-to DoDAAC. In many cases the requisitioner (Sold-to) DoDAAC

and Ship-to DoDAAC will be the same in the transaction.

XN Planning/Maintenance Organization

DLMS Note:

1. Used to identify a Shop Service Center/Shop Store.

2. Use in conjunction with N103 Identification Code Qualifier 92.

3. Refer to ADCs 284A, 381, and 1454 for known applications.

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

X ID 1/2 Used
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

Ref Id Element Name Req Type Min/Max Usage

004030F830D1DA10 18 September 12, 2023

Identification Code (67)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

Use with N101 codes LW and ST.

92 Assigned by Buyer or Buyer's Agent

DLMS Note:

Use with N101 Code XN to identify the user assigned Shop Service Center/Shop Store Identifier.

 Refer to ADCs 284A, 381, and 1454.

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to indicate the Security Assistance structured address data.

M4 Department of Defense Routing Identifier Code (RIC)

DLMS Note:

1. Use with existing code KA.

2. Use RIC-TO SGA when the item manager (source of supply) is unknown.

N104 67 Identification Code

Description: Code identifying a party or other

code

X AN 2/80 Used

N106 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an

individual

O ID 2/3 Used

Code Name

TO Message To

DLMS Note:

Must use with 2/N101/3200 code KA to identify the organization cited in N104 is receiving the

transaction.
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 19 September 12, 2023

LM Code Source Information Pos: 3900 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Use the 2/LM/3900 loop to identify coded information maintained in department or agency documentation.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LM01 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

M ID 2/2 Must use

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 20 September 12, 2023

LQ Industry Code Pos: 4000 Max: 100

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

DLMS Note:

Use to identify codes, as appropriate, consistent with management information requirements.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific industry

code list

DLMS Note: The following codes are authorized.

O ID 1/3 Used

Code Name

0 Document Identification Code

DLMS Note:

Use “CDD” to indicate the data reflects DDE Projected Supply Plan requirements. Continued

support of the DIC in a full DLMS environment will be assessed at a future date.

ZZ Mutually Defined

DLMS Note:

1. Use with DDE Projected Supply Plan transactions to identify the planning code.

2. Planning Code is optional data that the customer may use as they determine is needed.

Planning Code is an intra-Component, five-position code, which is under development by the

Services. Accordingly, although the data will be meaningful to the customer and will be visible to

customers in the Collaborate web tool, it won’t necessarily be meaningful to DLA or the other

Services.

A data maintenance action was approved in version 5030. The approved code/name is "PCL -

Planning Code Lookup".

1. Use with DDE Projected Supply Plan transactions to identify the planning code.

2. Planning Code is optional data that the customer may use as they determine is needed.

Planning Code is an intra-Component, five-position code, which is under development by the

Services. Accordingly, although the data will be meaningful to the customer and will be visible to

customers in the Collaborate web tool, it won’t necessarily be meaningful to DLA or the other

Services.

A data maintenance action was approved in version 5030. The approved code/name is "PCL -

Planning Code Lookup".

LQ02 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

X AN 1/30 Used
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 21 September 12, 2023

FST Forecast Schedule Pos: 4100 Max: 1

Detail - Optional

Loop: FST Elements: 4

User Option (Usage): Must use

Purpose: To specify the forecasted dates and quantities

Syntax Rules: 

1. P0607 - If either FST06 or FST07 is present, then the other is required.

2. P0809 - If either FST08 or FST09 is present, then the other is required.

Semantics: 

1. If FST03 equals "F" (indicating flexible interval), then FST04 and FST05 are required. FST04 would be used for the start date of

the flexible interval and FST05 would be used for the end date of the flexible interval.

Comments: 

1. As qualified by FST02 and FST03, FST04 represents either a discrete forecast date, the first date of a forecasted bucket

(weekly, monthly, quarterly, etc.) or the start date of a flexible interval.

2. FST06 qualifies the time in FST07. The purpose of the FST07 element is to express the specific time of day in a 24-hour clock

to satisfy "just-in-time" requirements. As an alternative, the ship/delivery pattern segment (SDP) may be used to define an

approximate time, such as a.m. or p.m.

3. FST11, FST12 and FST13 may be used only when FST02 contains code D (Planning).

DLMS Note:

Use one or multiple repetitions of the 2/FST/4100 segment for DDE Projected Supply Plan transactions.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

FST01 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. Use up to 60 repetitions in

Demand Data Exchange transactions to identify

the quantity for each interval/bucket.

2. Express quantity with two decimal places (e.g.,

1.50; 0.50; 0.00). 

M R 1/15 Must use

FST02 680 Forecast Qualifier

Description: Code specifying the sender's

confidence level of the forecast data or an action

associated with a forecast

DLMS Note: The following codes are authorized.

M ID 1/1 Must use

Code Name

D Planning

DLMS Note:

Use in conjunction with DDE Submission transactions (2/LIN01/0100 Code H- Submission)

W Cancellation

DLMS Note:

Use in conjunction with DDE Cancellation transactions (2/LIN01/0100 Code C - Cancelled)

FST03 681 Forecast Timing Qualifier

Description: Code specifying interval grouping

of the forecast

DLMS Note: The following codes are authorized.

M ID 1/1 Must use
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

Ref Id Element Name Req Type Min/Max Usage

004030F830D1DA10 22 September 12, 2023

Code Name

A Annually (Calendar Year)

DLMS Note:

Use to submit up to 5 years (5 annual periods) of projected supply plan data. (e.g., for a 5 year

projection, 5 annual periods will be submitted, to include zero entries for plan years with no data;

for a 4 year projection, 4 annual periods will be submitted, etc.). The beginning segment defines

the projected supply plan period start and end dates (BFR06 and BFR07 respectively). The

annual buckets must be provided in chronological sequence in the transaction and zero quantity

projections must be included. Use of “Annually” is a DLMS enhancement. See introductory

DLMS note 4a.

Use to submit up to 5 years (5 annual periods) of projected supply plan data. (e.g., for a 5 year

projection, 5 annual periods will be submitted, to include zero entries for plan years with no data;

for a 4 year projection, 4 annual periods will be submitted, etc.). The beginning segment defines

the projected supply plan period start and end dates (BFR06 and BFR07 respectively). The

annual buckets must be provided in chronological sequence in the transaction and zero quantity

projections must be included. Use of “Annually” is a DLMS enhancement. See introductory

DLMS note 4a.

M Monthly Bucket (Calendar Months)

DLMS Note:

1. Use to submit up to 5 years (60 months) of projected supply plan data. (e.g., for a 5 year

projection, 60 monthly buckets will be submitted, to include zero entries for plan months with no

data; for a 3 year projection, 36 monthly buckets will be submitted, to include zero entries, etc.). 

The beginning segment defines the projected supply plan period start and end dates (BFR06

and BFR07 respectively). The monthly buckets must be provided in chronological sequence in

the transaction and must include zero quantity projections.

2. While DDE projected supply plans can be as short as 12 months, DLA recommends that DDE

projected supply plans have 60 months plan periods, citing a 0 ( zero) for months with no plan.

1. Use to submit up to 5 years (60 months) of projected supply plan data. (e.g., for a 5 year

projection, 60 monthly buckets will be submitted, to include zero entries for plan months with no

data; for a 3 year projection, 36 monthly buckets will be submitted, to include zero entries, etc.). 

The beginning segment defines the projected supply plan period start and end dates (BFR06

and BFR07 respectively). The monthly buckets must be provided in chronological sequence in

the transaction and must include zero quantity projections.

2. While DDE projected supply plans can be as short as 12 months, DLA recommends that DDE

projected supply plans have 60 months plan periods, citing a 0 ( zero) for months with no plan.

Q Quarterly (Calendar Quarters)

DLMS Note:

Use to submit up to 5 years (20 quarters) of projected supply plan data. (e.g., for a 5 year

projection, 20 quarters will be submitted, to include zero entries for plan quarters with no data;

for a 4 year projection, 16 quarters will be submitted, etc.). The beginning segment defines the

projected supply plan period start and end dates (BFR06 and BFR07 respectively). The

quarterly buckets must be provided in chronological sequence in the transaction and zero

quantity projections must be included. Use of “Quarterly” is a DLMS enhancement. See

introductory DLMS note 4a.

Use to submit up to 5 years (20 quarters) of projected supply plan data. (e.g., for a 5 year

projection, 20 quarters will be submitted, to include zero entries for plan quarters with no data;

for a 4 year projection, 16 quarters will be submitted, etc.). The beginning segment defines the

projected supply plan period start and end dates (BFR06 and BFR07 respectively). The

quarterly buckets must be provided in chronological sequence in the transaction and zero

quantity projections must be included. Use of “Quarterly” is a DLMS enhancement. See

introductory DLMS note 4a.

S Semi-Annually (Calendar Year)

DLMS Note:

Use to submit up to 5 years (10 semi-annual periods) of projected supply plan data (e.g., for a 5

year projection, 10 semi-annual periods will be submitted, to include zero entries for semi-annual

plan periods with no plan data; for a 3 year projection, 6 semi-annual periods will be submitted,

etc.). The beginning segment defines the projected supply plan period start and end dates

(BFR06 and BFR07 respectively). The semi-annual buckets must be provided in chronological

sequence in the transaction and zero quantity projections must be included. Use of

“Semi-Annually” is a DLMS enhancement. See introductory DLMS note 4a.

Use to submit up to 5 years (10 semi-annual periods) of projected supply plan data (e.g., for a 5

year projection, 10 semi-annual periods will be submitted, to include zero entries for semi-annual

plan periods with no plan data; for a 3 year projection, 6 semi-annual periods will be submitted,

etc.). The beginning segment defines the projected supply plan period start and end dates

(BFR06 and BFR07 respectively). The semi-annual buckets must be provided in chronological

sequence in the transaction and zero quantity projections must be included. Use of

“Semi-Annually” is a DLMS enhancement. See introductory DLMS note 4a.

FST04 373 Date

Description: Date expressed as CCYYMMDD

DLMS Note: 1. Must use to identify the start date

for the forecast bucket (e.g., monthly) identified

in FST03 for the associated quantity in FST01.

Authorized DLMS migration enhancement. 

Refer to ADC 1138.

DLMS Note: 1. Must use to identify the start date

for the forecast bucket (e.g., monthly) identified

in FST03 for the associated quantity in FST01.

Authorized DLMS migration enhancement. 

Refer to ADC 1138.

2. Until such time as DLA implements DLMS

830D, the DLA legacy fixed format DIC CDD

cannot use this date and the forecast bucket

dates will not be mapped to the legacy

transaction. However, all DLMS implementations

must use the start date for the bucket to position

the input for DLA’s planned implementation of

DLMS 830D.

2. Until such time as DLA implements DLMS

830D, the DLA legacy fixed format DIC CDD

cannot use this date and the forecast bucket

dates will not be mapped to the legacy

transaction. However, all DLMS implementations

must use the start date for the bucket to position

the input for DLA’s planned implementation of

DLMS 830D.

M DT 8/8 Must use
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 23 September 12, 2023

SDQ Destination Quantity Pos: 4200 Max: 50

Detail - Optional

Loop: FST Elements: 3

User Option (Usage): Used

Purpose: To specify destination and quantity detail

Syntax Rules: 

1. P0506 - If either SDQ05 or SDQ06 is present, then the other is required.

2. P0708 - If either SDQ07 or SDQ08 is present, then the other is required.

3. P0910 - If either SDQ09 or SDQ10 is present, then the other is required.

4. P1112 - If either SDQ11 or SDQ12 is present, then the other is required.

5. P1314 - If either SDQ13 or SDQ14 is present, then the other is required.

6. P1516 - If either SDQ15 or SDQ16 is present, then the other is required.

7. P1718 - If either SDQ17 or SDQ18 is present, then the other is required.

8. P1920 - If either SDQ19 or SDQ20 is present, then the other is required.

9. P2122 - If either SDQ21 or SDQ22 is present, then the other is required.

Semantics: 

1. SDQ23 identifies the area within the location identified in SDQ03, SDQ05, SDQ07, SDQ09, SDQ11, SDQ13, SDQ15, SDQ17,

SDQ19, and SDQ21.

Comments: 

1. SDQ02 is used only if different than previously defined in the transaction set.

2. SDQ03 is the store number.

3. SDQ23 may be used to identify areas within a store, e.g., front room, back room, selling outpost, end aisle display, etc. The

value is agreed to by trading partners or industry conventions.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

SDQ01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which

a value is being expressed, or manner in which a

measurement has been taken

DLMS Note: 1. Use to identify the unit of issue

for the materiel.

2. DLMS users see the Unit of Issue and

Purchase Unit Conversion Table for applicable

codes.

M ID 2/2 Must use

SDQ03 67 Identification Code

Description: Code identifying a party or other

code

DLMS Note: Use "ZZ" for this data element to

satisfy mandatory X12 syntax requirements.

M AN 2/80 Must use

SDQ04 380 Quantity

Description: Numeric value of quantity

DLMS Note: Use “0” (zero) for this data element

to satisfy mandatory X12 syntax requirements.

M R 1/15 Must use
DLMS Implementation Convention (IC) 830D ADC 278, 284, 284A, 436, 1043C, 1082, 1105, 1138, 1267, 1367, 1412 and 1454 DLM 4000.25

 Demand Data Exchange (DDE) Projected Supply Plan

004030F830D1DA10 24 September 12, 2023

SE Transaction Set Trailer Pos: 0200 Max: 1

Summary - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST)

and ending (SE) segments)

Comments: 

1. SE is the last segment of each transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

SE01 96 Number of Included Segments

Description: Total number of segments included

in a transaction set including ST and SE

segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control number that

must be unique within the transaction set

functional group assigned by the originator for a

transaction set

DLMS Note: Cite the same number as the one

cited in ST02.

M AN 4/9 Must use