*DoD 4000.25-M, Vol 1, August 2004*

*Change 2*

*DLM 4000.25, Volume 1, April 09, 2022*

*Change 10*

**C4. CHAPTER 4**

**FUNCTIONAL APPLICATION ERRORS**

C4.1.  INTRODUCTION

	C4.1.1.  Purpose.  DoD Components, Federal Agencies, contractors, and foreign governments may use a variety of application systems to exchange Electronic Data Interchange (EDI) data based on Defense Logistics Management Standards (DLMS) Implementation Conventions (IC).  The primary purpose of this manual is to establish standards through which these varied systems can interoperate technically and functionally.  This chapter describes use of the DLMS 824R, Reject Advice Transaction to exchange information about functional errors not covered by DLMS status transactions.  The DLMS 824R Reject Advice Transaction is not used to reject a transmission due to ASC X12 syntactical errors.  A ***DLMS*** IC 997, Functional Acknowledgment Transaction is used for that purpose (DLM 4000.25-4, “Defense Automatic Addressing System”).

	C4.1.2.  Error Reduction.  The primary means for reducing errors is for each DoD Component to ensure that outbound transactions are thoroughly edited to fully comply with the DLMS standards and any DoD Component-unique requirements.  Receiving applications will likely perform edits to preclude processing erroneous transactions that may cause incorrect actions, disrupt the integrity of other data, or disrupt the operation of the system as a whole.

	C4.1.3.  Error Reporting.  When receiving applications apply edit checks and discover functional errors, the errors may be reported back to the originating activity using DLMS 824R.

C4.2.  DLMS 824R REJECT ADVICE

	C4.2.1.  Implementation Convention Content.  The DLMS 824R, Reject Advice will convey the following information when reporting errors to the originator:

		C4.2.1.1.  Table 1 Data.  Identifies the originator of the DLMS 824R and the recipient, which is the originator of the erroneous transaction being rejected.

		C4.2.1.2.  Table 2 Data

			C4.2.1.2.1.  Identifies the erroneous transaction, specifically including the following data:

				C4.2.1.2.1.1.  Document number or procurement instrument identifier (PIID).[footnoteRef:1]  When a contract is authorized under a PIID call/order number (F in 9th position), provide the value in the PIID field. [1:  Use the legacy PIIN pending transition to the PIID.  ] 

				C4.2.1.2.1.2.  Transaction set control number.

				C4.2.1.2.1.3.  Transaction set identifier code.

				C4.2.1.2.1.4.  Beginning segment information as applicable (e.g., transaction set purpose code, transaction type code, report type code, action code).

				C4.2.1.2.1.5.  Identifying materiel number (e.g., National Stock Number (NSN), part number (PN)/CAGE)

				C4.2.1.2.1.6.  Transaction creation date.

			C4.2.1.2.2.  The application error condition code identifying error type.

			C4.2.1.2.3.  Copy of the bad data element (optional).

			C4.2.1.2.4.  Free-form text message describing the error (optional).

	C4.2.2.  Reject-Error Routing.  Routing of the reject is from the rejecting activity to the sending activity.  This will typically lead to one of three scenarios:

		C4.2.2.1.Defense Automatic Addressing System (DAAS) Transaction Reject.  DAAS uses the DLMS 824R, Reject Advice Transaction, to report the error back to the originating activity, which must correct and retransmit the transaction. 

			C4.2.2.1.1.  The Reject Advice Transaction reports the unique document number of the erroneous transaction and/or other pertinent information to identify the erroneous transaction including reject advice codes (when available) identifying one or more specific error conditions.

			C4.2.2.1.2.  Where specific reject advice codes are not established to identify the error condition causing the transaction to fail, DAAS uses the DLMS 824R to provide narrative message rejection of any DLMS transaction using procedures described in paragraph C4.2.4.2.

			C4.2.2.1.3.  A combination of reject advice codes and clarifying narrative may be used to facilitate interpretation of the error condition.

		C4.2.2.2.  Activity Transaction Reject to Sending Activity.  The activity receiving a transaction from DAAS uses the DLMS 824R to report an error back to the transaction originator.[footnoteRef:2],[footnoteRef:3]  DAAS will not compare the rejected information to an image of the transaction as they received it from the originating activity.  Instead, DAAS will route the DLMS 824R transaction to the identified Message-To addressee without further processing.  Action Code DR Direct in data element 1/BGN08/020 of the DLMS 824R Reject Advice Transaction identifies this rejection process. [2:  Not available for use without prior coordination.]  [3:  Authorized for use on an intra-Air Force basis for Government Furnished Property (GFP) accountability.  Refer to ADC 1226 for detailed procedures.] 

		C4.2.2.3.  Activity Transaction Reject to DAAS.  A potential future enhancement will allow an activity receiving a transaction from DAAS to report the error back to the transaction originator using DLMS 824R.[footnoteRef:4]  Under the planned enhancement, DAAS will compare the rejected information to an image of the transaction as they received it from the originating activity.  If DAAS determines it caused the error, DAAS will correct and retransmit the transaction.  If DAAS determines the originating activity caused the error, then DAAS will initiate another Reject Advice Transaction back to the originating activity, as in the first scenario.  Action Code 80 Reconcile in data element 1/BGN08/020 of the DLMS 824R Reject Advice Transaction identifies this planned enhancement.   [4:  Not available for use without prior coordination.] 

	C4.2.3.  Application Program Use of DLMS 824R, Reject Advice.  If a DoD Component application program cannot process a received transaction, it will send a DLMS 824R, Reject Advice Transaction back to the sending activity.  The Reject Advice Transaction reports the unique document number, and/or other pertinent information to identify the erroneous transaction, and codes identifying one or more specific error conditions

		C4.2.3.1.  Rejection by Specific Reject Advice Code.  

			C4.2.3.1.1.  Initially, DLMS 824R was developed to provide the functionality of legacy Military Standard Transaction Reporting and Accountability Procedures (MILSTRAP) Document Identifier Code (DIC) DZG, Transaction Reject.  As such it rejects the following DLMS transactions with legacy MILSTRAP functionality:  DLMS Transactions 527D, 527R, 536L, 830R, 830W, 846A, 846D, 846F, 846I, 846P, 846R, 846S, ***856S,*** 867D, 867I, 870L, 888I, and 947I, citing specific reject advice codes in the LQ segment.  

			C4.2.3.1.2.  Additionally, the DLMS 824R is authorized for use with DLMS supply (including MILSTRIP transactions), finance, and contract administration transactions that are not specifically identified in this chapter.  

		C4.2.3.2.  Use of DLMS 824R does not replace procedures for error identification addressed by DLMS 140A, Small Arms and Light Weapons (SA/LW) Reporting, DLMS 870S, Supply Status, or DLMS 842A/R, DoD Supply Discrepancy Report Reply.  DLMS 824R codes may be expanded in the future as requirements are identified and implemented.

	C4.2.4.  Characteristics of Use

		C4.2.4.1.  Application Identified Error Examples.  Even with stringent editing performed by the EDI translator, some error conditions will occur that only the more complex application program edits can identify.  These errors may include:

			C4.2.4.1.1.  Invalid item identification.

			C4.2.4.1.2.  Quantity of zero when a nonzero quantity is required.

			C4.2.4.1.3.  Invalid DLMS code received in the LQ02 Segment.  The DLMS 824R applies only when a received transaction fails to comply with the application-level rules/formats specified in the implementation convention.

		C4.2.4.2.  DAAS Receipt and Generation of DLMS 824R Reject Advice 

			C4.2.4.2.1.  Processing Data.  As DAAS receives DLMS interchange envelopes it will process the data through an EDI translator and then break the contents down to the transaction level.  DAAS will apply appropriate DLMS and DoD Component edit checks on received transactions.

				C4.2.4.2.1.1.  If DAAS software detects a nonbusiness process error, it will reject the transaction back to the sender using ***DLMS*** IC 997 or DLMS 824R, as applicable.

				C4.2.4.2.1.2.  If DAAS detects data errors preventing the correct routing or processing of the transaction, DAAS will reject the transaction back to the originator with a DLMS 824R containing a narrative message in the NTE segment identifying the error(s) that prevented the routing/processing.  DAAS will also use the enveloping information to identify the rejected transaction.

			C4.2.4.2.2.  Loading Transactions.  DAAS will load transactions that do not contain errors into the Logistics Online Tracking System (LOTS).

C6-4

CHAPTER 7

C4-4	CHAPTER 4