*******DLM 4000.25, Volume 2, October 03, 2017*

*Change 9*

# C23. CHAPTER 23

# CATALOG DATA SUPPORT 

C23.1.  GENERAL

	C23.1.1.  Purpose.  This chapter provides general information regarding procedures and data exchange requirements for the communication of the DLMS Catalog Data Support.  

	C23.1.2.  Transactions.  This chapter addresses procedures applicable to the following Accredited Standards Committee (ASC) X12 transaction functions identified by the transaction set number and the beginning segment Transaction Purpose Code.  There are no legacy 80 record position (MILS) equivalent transactions.  See the Defense Enterprise Data Standards Website for available DLMS Supplement formats on the DLMS IC page.

		C23.1.2.1.  DLMS 832N, Catalog Data Support, is used for the following transaction functions identified by the beginning segment Catalog Purpose Code (1/BCT01/0200):

			C23.1.2.1.1.  CP – Use to identify catalog data support communicated between DLA Disposition Services, DLA Disposition Services Field Offices, and Distribution Depots supporting Reutilization Business Integration (RBI). These catalog data support transactions identified by BCT01=CP are referred to in this document as DLA Disposition Services Catalog Data Support.  See Chapter 16 for detailed procedures associated with this type of catalog data support.

			C23.1.2.1.2.  RC – Use to identify catalog data support communicated between DLA and maintenance/industrial activities (IAs) authorized by DLA IA support agreement supporting Supply, Storage, and Distribution (SS&D) for the Navy and Retail Storage and Distribution Interface (SDI) for the Marine Corps.  These catalog data support transactions are referred to as IA Catalog Data Support.

			C23.1.2.1.3.  SC – Use to identify catalog data support communicated between DLA Disposition Services and DLA Disposition Services Field Offices supporting Reutilization Business Integration (RBI). These catalog data support transactions are referred to as Sales Contract Catalog Data Support. Note: Only the following detail level functional data is applicable to this process: Generic Name Description, Sales Contract Number, Sales Contract Line Item Number, Remaining Authorized Quantity, and Unit of Measure.  See Chapter 16 for detailed procedures associated with this type of catalog data support.

		C23.1.2.2.  Reserved.  (This is a placeholder for other Catalog Data Support transactions that will be identified by different Transaction Purpose Codes.)

C23.2.  INDUSTRIAL ACTIVITY CATALOG DATA SUPPORT

	C23.2.1.  Navy Background.  As a result of the 2005 Base Realignment and Closure (BRAC) decision, retail supply, storage and distribution functions and associated infrastructure supporting the Navy industrial/maintenance sites transferred to DLA.  DLA is the material provider for all consumable items in support of the maintenance mission at these sites.  To effectively manage materiel at these sites, DLA will maintain materiel master records identifying the materiel identification and associated characteristics for all DLA managed, non-DLA managed, and local stock number materials that are used by the Navy.  Prior to the BRAC decision, Enterprise Business System (EBS) maintained materiel master records for all DLA managed items and some non-DLA Managed items; with this new requirement the DLA EBS will establish materiel master records for any non-DLA managed item requested by the Navy Fleet Readiness Centers (FRCs) and the Naval Shipyards (NSYs).

	C23.2.2.  Marine Corps Background.  As a result of the 2005 BRAC decision, operating materiel and supplies storage and distribution functions and associated infrastructure supporting the Marine Corps Maintenance Centers (MCMC) industrial/maintenance sites transferred to DLA.  DLA is the storage and distribution provider for most consumable items in support of the maintenance mission at these sites. To effectively manage materials at these sites, DLA Distribution Standard System (DSS) will maintain item data records containing the materiel identification and associated characteristics for all materiel used by the MCMC.  Prior to the BRAC decision, DSS maintained item data records for all DLA managed items and most non-DLA-managed items; with this new requirement the DLA DSS established item data records for any item assigned a local stock number (LSN) by the MCMC. 

	C23.2.3.  The catalog data exchange supports the following functions.  Specific implementation varies by Service:

		C23.2.3.1. Communication of Federal Logistics Information System (FLIS) and user unique data associated information for newly cataloged national stock number (NSN) materiel.

		C23.2.3.2.  Identification of non-NSN materiel by an LSN so that the LSN may be recognized for requisitioning, storage, and receipt processing.

		C23.2.3.3.  Communication of FLIS Catalog Change Notices to the Navy NSY and FRC sites.  DLA will send change notices whenever an active materiel master record is updated in the form of  DLMS 832N IA Catalog Data Support transactions.  EBS will send notices for changes resulting from manual/ programmatic updates (within EBS) and from systemic updates (from FLIS).  FLIS changes include communication of replacement, superseded, and discontinued NSNs.

		C23.2.3.4.  Identification of NSN materiel by an LSN so that the LSN may be used for storage and distribution of materiel identified at the unit of use (that is, a unit of measure that is less than the FLIS unit of issue).  

		C23.2.3.5.  Identification of MCMC LSNs to a unit of use LSN.

		C23.2.3.6.  Communication of a Service coordinated/approved substitute/ interchangeable item as a result of DLA or other Service provided supply status to associate the substitute NSN with the primary NSN. 

		C23.2.3.7.  Shipyard prepared queries to identify available DLA EBS materiel master matches on NSN, LSN, or CAGE/part number.  This action may trigger an EBS query against FLIS.  EBS responses will be returned in an DLMS 832N IA Catalog Data Support transaction.  

C23.3.  PROCEDURES – NAVY INTERFACE

	C23.3.1.  Upon data conversion, all the current LSNs and non-DLA managed materiel masters from the FRC and NSY systems will migrate to EBS.  DLA managed items will be identified and materiel master record will extended to each site as applicable.  This will provide a base line for the materiel currently used at the BRAC sites.  

	C23.3.2.  The catalog data will be applicable to new item inductions, FLIS change notices for DLA items and non-DLA managed items, as well as Navy-assigned LSNs.  Manual updates for user unique data elements will be included in the process.  Since DLA will purchase, store, and sell these items to industrial activities, DLA will have this data resident in EBS and will provide visibility and updates to the Navy systems via the DLMS 832N IA Catalog Data Support transaction. 

	C23.3.3.  EBS will also maintain site specific materiel master records for Depot Level Repairable, Nuclear Support Consumables, or Program Owned Material (even cognizance (COG)) items to provide updates pertaining to FLIS data or user unique data elements to the FRC or NSY sites. DLMS 832N IA Catalog Data Support change transactions will be provided to applicable sites based on FLIS updates or end user changes to user defined data elements for these items.

	C23.3.4.  Web-based Query.  When new items are needed by any of these sites, the capability is required to create new materiel masters or update user defined data elements to existing materiel masters directly into EBS through a user unique screen.  This application within EBS will prompt users for mandatory fields and user defined fields for new entries, that may be optional depending upon the site (FRC/NSY).  The screen will allow the user to query the current EBS data base and determine if an NSN or LSN already exists within EBS.  

	C23.3.5.  If an existing record is found, and EBS does not currently reflect the materiel master is extended to the user site, based on user response, the materiel will be extended to the user site and an DLMS 832N IA Catalog Data Support transaction will be sent to user site and identified as an ‘ADD’ record. 

	C23.3.6.  When no record is found within EBS, the system will query the FLIS reference master data environment (RMDE) to identify any associated NSN.  Once the materiel master is created in EBS, an DLMS 832N IA Catalog Data Support transaction will be sent to the applicable FRC or NSY site.  If found, the user will have the option to build a materiel master record created with FLIS data and any mandatory user unique data elements in EBS based on user response/input.  EBS will then format a DLMS 832N IA Catalog Data Support transaction.  This DLMS 832N IA Catalog Data Support transaction will be identified as an ‘ADD’ and will be sent to the appropriate NSY/FRC site via DAAS.  

	C23.3.7.  If no NSN is found in FLIS, the user will have the option to add a materiel master identified by an EBS assigned LSN.  EBS has logic that defaults specific mandatory FLIS data elements, and prompts the user for those for which a default cannot be determined.  EBS will then format an DLMS 832N IA Catalog Data Support transaction identified as an “ADD” and send it to the site identified by the user and also furnish a copy to the instance of DSS at the same site.  

	C23.3.8.  Materiel Identification.  Cataloging data will be categorized by two methods of materiel identification

		C23.3.8.1.  Items identified by NSN.  For these, DLA will relay FLIS catalog information in the absence of a Navy-FLIS interface.  DLA will also incorporate additional DLA/Navy unique content.

		C23.3.8.2.  Items identified by LSN.  There will be four configurations of LSN materiel numbers within EBS. 

			C23.3.8.2.1.  Items Cataloged with an NSN but issued to the Navy by Unit of Use.  EBS will assign a unique LSN using the existing data associated with the original NSN.  All transactions for this item will be recorded within EBS under the LSN.  There will be a cross-reference on the materiel master from the LSN to the NSN, and on the NSN to the LSN.  LSNs in this category will use the following construct: 5975-U0-000-1234.

			C23.3.8.2.2.  Items Identified within a Navy System (e.g., Materiel Access Technology (MAT) or Manufacturing Resource Planning II (MRP II)) by LSN. These LSNs will be migrated into EBS.  EBS will continue to process transactions against these numbers and modification will be done through user unique screen application by end users.  Updates will be sent to applicable sites based on these updates.  LSNs in this category will use the following construct: 5315-L*-00-9876.

			C23.3.8.2.3.  Items with no current LSN or NSN assigned to the Cage and Part Number combination within EBS or FLIS.  EBS will allow end users to create a materiel master for these items via the user unique screen application and systemically assign an LSN.  Updates will be sent to applicable sites based on the initial creation and any subsequent updates based on end user input.  These LSNs will be established based on Federal supply classification (FSC) with a serial number range of NL00000000001 through NL99999999999. 

			C23.3.8.2.4.  Hazardous Materiel under Hazardous Material Management System (HMMS)Control System (RHICS).  For items for which a materiel master is needed to identify hazardous materiel under HMMS, an LSN identifying the HMMS cataloged or created “LLN” numbers will be used if no NSN is assigned.  LSNs in this category will use the following construct:  6810-LL-N00-0001.

				C23.3.8.2.4.1.  EBS will determine if there is an existing materiel master record of the RHICS materiel beginning with LLN (first 3 digits).  When there is an existing materiel master, user will be prompted to enter user unique data elements to extend MMR and EBS will return a DLMS 832N Catalog Data Support transaction identified as an “ADD” record containing all agreed to data elements to build a record in MAT and pass a copy to DSS.

				C23.3.8.2.4.2.  If no materiel master exists for the HMMS hazardous materiel, the user will be prompted for mandatory fields and user defined fields for new entries using the HMMS data base elements.  The key is that only one HMMS LLN number will be used for like material, thereby having only one LLN number per hazardous materiel for all users. When the query is for an LLN, the DLMS 832N Catalog Data Support transaction will be an output transaction to MAT and a copy will be furnished to the applicable DSS site.  

			C23.3.8.2.5.  Navy Nuclear Material numbers will be created in EBS, via the user unique screen application and the user will assign an “LLR” material number.  These materials are unique and will only have one per material.  LSNs in this category will use the following construct:  LL-R**-****.

		C23.3.8.3.  New Records.  Upon creation of new materiel identification content applicable to this process, EBS will build the materiel master, apply the catalog data to the identified sites (extend to the user sites), and format an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code AA, New Catalog Record Added, that will be sent to the appropriate NSY/FRC site via Defense Automatic Addressing System (DAAS).  EBS will provide a copy of DLMS 832N IA Catalog Data Support transactions for items identified as LSNs to the applicable DSS site.

		C23.3.8.4.  Modified Records.  When the user entry modifies an existing record via the user unique screen application, ***the system will prompt***the user to save changes.  This will trigger EBS to generate a DLMS 832N Catalog Data Support transaction citing Catalog Purpose Code CC, Catalog Record Changed.  This record will contain all applicable data elements to build a record within Navy systems (allowing overlay, vice transmission of only the modified content).  If the change is to an existing LSN record previously provided to a DSS site, a copy of the change will also be furnished.  ***The system receiving a transaction identified by Catalog Purpose Code CC that is unmatched to an existing record in the database will accept the transaction and process it as a new record.[footnoteRef:1]***   [1:  Refer to ADC 1176. Staggered implementation applies.] 

		C23.3.8.5.  Transaction Query.  NSY sites will have the additional capability to inquire EBS materiel master records using an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code QU, Site Query for Catalog Record, to determine if NSN or LSN or CAGE Code and Part Number combination exists in the EBS data base when there is no existing record on the internal table within the NSY Navy system. 

			C23.3.8.5.1.  If there is an existing materiel master within EBS for the inquired NSN, EBS will extend the materiel master to the inquiry site and return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code AA,  New Catalog Record Added, containing all mandatory data elements to build a record in the MAT system. 

			C23.3.8.5.2.  If there is no materiel master within EBS for the inquired NSN, EBS will inquire FLIS.  When the response is positive, EBS will build a materiel master and return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code AA, New Catalog Record Added, containing all mandatory data elements to build a record in MAT system.

			C23.3.8.5.3.  If the response from FLIS for the inquired NSN is negative EBS will return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code NN,  No record exists for NSN query.  MAT will output for manual review.

			C23.3.8.5.4.  If there is an existing material master within EBS for the inquired LSN, EBS will extend the materiel master to the inquiry site and return an DLMS 832N IA Catalog Data  Support transaction citing Catalog Purpose Code AA, New Catalog Record Added, containing all mandatory data elements to build a record in MAT system. 

			C23.3.8.5.5.  If the response for the inquired LSN is negative EBS will return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code NL, No record exits for LSN query.  MAT will output for manual review.  The user may at this point enter data into the EBS user unique entry screen indicating the need to create a record.

			C23.3.8.5.6.  If there is an existing materiel master within EBS for the inquired ‘Part Number/CAGE’, EBS will extend the materiel master to the inquiry site and return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code AA,  New Catalog Record Added, containing all mandatory data elements to build a record in MAT system. 

			C23.3.8.5.7.  If there is NO existing materiel master within EBS for the inquired ‘part number/CAGE’, EBS will invoke a query to FLIS.  

				C23.3.8.5.7.1  When the FLIS response is positive and only one NSN is returned, EBS will build the materiel master to the inquiry site and return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code AA, New Catalog Record Added, containing all mandatory data elements to build a record in the MAT system. 

				C23.3.8.5.7.2.  When the FLIS response is positive and multiple NSNs are returned, EBS will return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code MN:  Multiple NSNs for Part Number/CAGE.  MAT will output record for manual review.  The user will determine which NSN is applicable for their use and will have the option to inquiry against the specific NSN or build the record through the EBS on-line input. 

				C23.3.8.5.7.3.  When the FLIS response is negative, EBS will return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code NP,  No NSN or LSN Found for Part Number/CAGE, to MAT for manual review.  

******C23.3.9  Special Processing at DAAS for Transactions to FRCs.  In order to compensate for data mapping inconsistencies between DLA and the FRC, DAAS is required to apply special mapping logic to 832N transactions addressed to FRC locations.  These transactions will be reviewed for drawing package information that must be re-used to create a unique part number/CAGE combination to be inserted in the outgoing transaction.  The new part number (REF01 Code MF) will be created using existing data from the reference drawing number (REF01 Code QZ) or, if not available, the drawing number (REF01 Code DG).  The associated manufacturer’s CAGE (REF04-W7) will be created using the drawing CAGE (REF01 Code ZM).

	C23.3.10.  Unit of Use.  Unique functionality to be added in support of the 2005 BRAC decision at the NSY and FRC sites is the ability to issue and store material at a quantity and unit of use less than the FLIS unit of issue.  In these instances EBS will apply unique logic to create a materiel master with an LSN.  This record will contain all applicable FLIS and user unique data elements copied from the original NSN.  The EBS materiel master records for both the LSN and NSN will reference each other.  

		C23.3.10.1.  EBS will create an LSN record for all NSN items identified with a unit of use upon data conversion as a base line.  After initial conversion, these records will be based on either a requisition alert or funded requisition from any NSY or FRC site identifying a unit of use requirement.  An DLMS 832N IA Catalog Data Support transaction record will NOT be generated to the NSY/FRC sites, but will be forwarded to the applicable DSS site.  

		C23.3.10.2.  The DLMS 832N IA Catalog Data Support record will reflect the assigned LSN and Unit of Use as well as the associated NSN and FLIS unit of issue.  DSS will build an internal table cross-referencing the NSN and the associated Unit of Use LSN, FLIS Unit of Issue and the Unit of Use.

	C23.3.11.  Substitute Cross Reference.  EBS will provide catalog data reflecting substitute reference during the status process.  This will occur for both DLA managed substitutions and for other Service managed substitutions.  

		C23.3.11.1.  When EBS processes a request from an NSY or FRC and determines the primary materiel identification number (e.g., NSN)  is not available but an approved substitute is available, EBS will provide ‘BH’ status and format an DLMS 832N IA Catalog Data Support identified as a substitute record reflecting the primary NSN and reference the substitute NSN. 

		C23.3.11.2.  When EBS receives a ‘BH’ indicating DLA will be sent an item previously identified as a Navy suitable substitute for a DLA funded requisition, the status will prompt EBS to format a DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code SN, NSN Substituted, reflecting the primary NSN and referencing the substitute NSN when a materiel master already exists in EBS. 

		C23.3.11.3.  When a materiel master for the substitute NSN does not exist in EBS, a materiel master record will be created.  Any user unique data elements will be copied from the primary NSN specific to that site.  A DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code SN, NSN Substituted, reflecting the primary NSN and referencing the substitute NSN will be forwarded to the applicable site for updating of Navy systems.

		C23.3.11.4.  EBS will not maintain a cross reference to other service managed NSNs pertaining to Substitution. 

	C23.3.12.  FLIS Change Notices.  EBS will be responsible for providing all change notices to the Navy BRAC 2005 SS&D sites.  These change notices will be generated as a result of FLIS data changes.  Anytime a FLIS recorded data element in EBS is modified, a DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code CC, Catalog Record Changed, will be sent to all FRC/NSY sites that the material has been extended to within EBS.  The changed data element will not be specifically identified.  Each FRC/NSY system will update internal records accordingly.  

		C23.3.12.1.  NSN Replacement.  When an NSN is specifically identified as a ‘REPLACED BY’ the DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code RN, NSN Replaced, and both the former and new NSN will be identified.  MAT and MRP II will update its systems as applicable for these records. 

		C23.3.12.2.  When an NSN is specifically identified as ‘DISCONTINUED’ the DLMS 832N IA Catalog Data Support transaction will cite Catalog Purpose Code DN, NSN Discontinued; no Replacement.  If a subsequent NSN is identified from the FLIS update, the DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code NS, NSN Superseded, will contain both the former and new NSN.  MAT and MRP II will update its systems as applicable for these records. 

		C23.3.12.3.  When an NSN is specifically identified as ‘When Exhausted use’ the DLMS 832N IA Catalog Data Support transaction will cite Catalog Purpose Code RS, Use NSN When Exhausted, and both the former and new NSN will be identified on the DLMS 832N IA Catalog Data Support transactions.  MAT and MRP II will update its systems as applicable for these records.

	C23.3.13.  Unanticipated Situations Impacting Catalog Transaction Exchange

		C23.3.13.1.  If the connection between DLA EBS and FLIS, via FLIS Portfolio Data Warehouse (FPDW) is down, EBS will initially respond with a ‘Response Delayed’ status and recycle the query until the FPDW connection resumes and then provide the appropriate status at that time.  This process is identified by a DLMS 832N IA Catalog Data Support transaction citing Catalog Transaction Purpose Code RD.

		C23.3.13.2.  If an unexpected error occurs that is not accounted for by existing response codes, a response of “Manual Action Required” will be provided by EBS and the transaction will output for manual review.  This process is identified by a DLMS 832N IA Catalog Data Support transaction citing Catalog Transaction Purpose Code AR.

C23.4.  PROCEDURES – MARINE CORPS INTERFACE.

	C23.4.1.  Upon data conversion, all the current local stock numbers and non-DLA managed materiel masters from the MCMC systems will be migrated to DSS.  This will provide a base line for the materiels currently used at all MCMC sites.  

	C23.4.2.  The catalog data will be applicable to MCMC-assigned LSNs.  Since DLA will be storing and distributing these items to industrial activities (IAs), DLA will have this data resident in the DSS and the MCMC will provide visibility and updates to these LSNs via the DLMS 832N IA Catalog Data Support transaction. 

	C23.4.3.  Web-based Query.  When new items are needed by any of these sites, the capability to create new material masters or update user defined data elements to existing material masters directly into MCMC systems through a user unique screen.  This application within the MCMC systems will prompt users for mandatory fields and user defined fields for new entries, which may be optional depending upon the site application. The screen will allow the user to query the current MCMC data base and determine if an NSN or LSN already exists.  

	C23.4.4.  If no NSN or LSN exists in the MCMC systems, the user will have the option to add a materiel master identified by a MCMC assigned LSN.  MCMC systems have logic that will default specific mandatory data elements, and prompt user for those for which a default cannot be determined.  MCMC systems will then format a DLMS 832N IA Catalog Data Support transaction and send to the site identified by the user.

	C23.4.5.  Materiel Identification.  Cataloging data will be categorized by items identified by LSN where no NSN is assigned.  

		C23.4.5.1.  Items currently identified within MCMC systems ((Industrial Logistics Support Management Information System), and MRP II) as an LSN will be migrated into DSS.  DSS will continue to process transactions against these LSNs and modification will be done through user unique screen application maintained by the MCMC systems.  Updates will be sent to applicable sites based on these updates.

		C23.4.5.2.  For items identified by contractor and Government entity (CAGE) and part number combination (with no LSN or NSN assigned) within MCMC systems,  MCMC systems will allow end users to create a materiel master for these items via the user unique screen application and systemically assign an LSN.  Updates will be sent to applicable sites based on the initial creation and any subsequent updates based on end user input.  These LSNs will be established based on the FSC with a sequentially assigned number in the LSN NIIN.

		C23.4.5.3.  A cataloging action is not required to establish unit of use LSNs for NSN materiel or for non-NSN materiel previously assigned an LSN.  A DLMS 846A  Asset Reclassification action will be used to re-identify the materiel and trigger the creation of an item data record under the new LSN within DSS.  

	C23.4.6.  New Records.  Upon creation of new materiel identification content applicable to this process, MCMC systems will build the materiel master, apply the catalog data to the identified sites (extend to the user sites), and format a DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code AA,  New Catalog Record Added, that will be sent to the DSS via DAAS. 

	C23.4.7.  Modified Records.  When the user entry modifies an existing record via the user unique screen application, ***the system will prompt*** the user to save changes.  This will trigger the MCMC system to generate a DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code CC, Catalog Record Changed.  This record will contain all applicable data elements to build a record within the DSS system (allowing overlay, vice transmission) of only the modified content.  ***The system receiving a transaction identified by Catalog Purpose Code CC that is unmatched to an existing record in the database will accept the transaction and process it as a new record.[footnoteRef:2]*** [2:  Refer to ADC 1176.  Staggered implementation applies.] 

	C23.4.8.  Deleted Records.  When the user entry deletes an existing record via the user unique screen application, the user will be prompted to save changes.  This will trigger the MCMC system to generate a DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code DD, Catalog Record Delete.  This record will contain all applicable data elements to delete a record within the DSS system 

	C23.4.9.  FLIS Change Notices.  DSS will be responsible for providing change notice information via catalog data support transactions to MCMC sites for changes related to the NSN itself.  MCMC systems will be updated as applicable for these records.  

		C23.4.9.1.  NSN Replacement.  When an NSN is specifically identified as a ‘REPLACED BY,’ the DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code RN, NSN Replaced, including the former and new NSN will be identified.

		C23.4.9.2.  When an NSN is specifically identified as ‘DISCONTINUED’ the DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code DN, NSN Discontinued; no Replacement, will be provided.  If a subsequent NSN is identified from the FLIS update, the DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code NS, NSN Superseded, will be provided containing both the former and new NSN.  

		C23.4.9.3.  When an NSN is specifically identified as ‘When Exhausted use’ the DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code RS, Use NSN When Exhausted, will be provided including both the former and new NSN.

***C23.5. AIR FORCE GOVERNMENT FURNISHED PROPERTY ACCOUNTABILITY***

***C23.5.1. Air Force Background: The Air Force chartered the Government Furnished Property-Accountability (GFP-A) Capability Initiative to provide property accountability/control of Air Force-owned, contractor-managed and possessed property by implementing standard and integrated processes. This capability establishes and maintains accountable inventory records for GFP assets managed by the Air Force contractor inventory control points (CICPs), and makes them visible in the Air Force accountable property system of record (APSR).***

***C23.5.1.1. Air Force CICPs will use their own inventory management systems to send catalog data for local stock number (LSN) items to the Air Force APSR. The contractor is the source of this information, which is similar to standard catalog data. The Air Force APSR maintains the data fields used to track the contractor-provided catalog data. As the item manager, the Air Force CICP is responsible for identifying the appropriate values to be provided to the Air Force APSR. The Air Force APSR’s asset master record must mirror the asset information in the CICP’s IMS at all times.***

***C23.5.1.1.1. The Air Force CICPs will send catalog data when a new LSN is added to its contractual requirements, or when information for a previously assigned LSN changes. The Air Force CICP will transmit a DLMS 832N to the Air Force APSR after processing the update to reconcile the information between the two systems. The Air Force APSR will process the DLMS 832N and update its master record for the affected asset(s).***

	C23-11	CHAPTER 23