Approved DLMS Change 60A, Revision to DLMS Supplement 180M, Material Returns Reporting

Transcription

1

2 Approved DLMS Change 60A, Revision to DLMS Supplement 180M, Material Returns Reporting 1. ORIGINATOR: Supply Process Review Committee, Ellen Hilert, Co-Chair, DLA J-673, Defense Logistics Management Standards Office (DLMSO), (DSN 427), 2. FUNCTIONAL AREA: Supply 3. REFERENCE: DLMSO memorandum, Approved DLMS Change 60, Revision to DLMS Supplement: 180M, Material Returns Reporting (Supply) February 20, REQUESTED CHANGE: a. Title: Addendum for Revision to DS 180M, Material Returns Reporting b. Description of Change: This change provides numerous administrative corrections, clarifications, and updates but does not alter the functionality of the DS 180M. c. Procedures: Revise DS 180M, Material Returns Reporting as follows: # Location Revision Reason Federal IC 1 Introductory Federal Notes (Cover page) Revise notes 1 and 2. Add new note Organizations use this transaction set to report the availability of material to the wholesale distribution system, to report the automatic shipment of material to storage or repair facilities, to request cancellation of previously submitted report, and to inquire about the status of previously submitted transactions. 2. Use a single occurrence of this transaction set to transmit single or multiple material returns information transactions to one or more Inventory Control Points (ICPs or Integrated Material Managers (IMMs). Correction. (Notes are being returned to original content; removes information not applicable to this IC which was inadvertently added during a previous update.) Requires Federal IC change prior to DS update. 3. A single transaction set may contain a combination of transactions for standard and nonstandard material. 4. DoD logistics users should refer to the Defense Logistics Management System (DLMS) Supplement to the Federal Implementation Convention (IC) available at URL: The DLMS Supplement provides specific business rules, conditions, and authorized codes necessary for appropriate use of this IC within the DLMS.

3 2 Introductory DLMS Notes (Cover page) Administrative Change 1. Users operating under the Defense Logistics Management System (DLMS) must reference the Unit of Issue and Purchase Unit Conversion Table, Transportation Mode of Shipment Conversion Table, and the Accounting Classification Appendix which can be found on the Defense Logistics Management Standards Office (DLMSO) web site at Correction and update. Adds new clarification restricting use of ANSI functionality for data repetition. 2. This DLMS Supplement to the Federal 180M implementation convention contains: a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system. DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DLMSO 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 DLMSO 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 DLMSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment. d. Data elements which have an expanded files size above existing DLSS capability which may not be supported by the recipient's automated processing system. Components must coordinate implementation with DLMSO prior to use. e. Repetition of data (using multiple iterations or loops) which is not compatible with existing DLSS capability. Although supported by the use of the ANSI X12 standard, such data is not compatible with DLSS/DLMS conversion and may not be supported by the recipient s automated processing system. Components must coordinate implementation of enhanced capability with DLMSO prior to use. 3. This revision to the DLMS Supplement (DS) incorporates Approved DLMS Change (ADC) 60. ADCs are available from the DLMSO website: 4. This DS supercedes and cancels all previous DLMS Supplements to the Federal IC 180M, Version 4010, Rev 0. Throughout Supplement When referring to a DLMS Introductory note ensure correct numbered note is referenced

4 3 1/BGN07/020 Revise DLMS note for qualifier FT to read: FT Material Returns DLMS Note: Use to indicate the transaction set contains material returns program transactions. No action code when used for initial asset report (DLSS DI Code FTE/FTG). 4 1/BGN08/020 Revise DLMS notes for the following qualifiers: C Cancelled DLMS Note: Use to indicate a request to cancel a previously submitted report of material availability (DLSS DI Code FTC). T RF Status Query DLMS Note: Use to indicate an inquiry to the ICP/IMM requesting a reply to a previously submitted report of material availability (DLSS DI Code FTF). Returned to Shipper's Facility (Other Than Original Shipping Location) DLMS Note: Use to indicate a notification of an automatic return shipment (DLSS DI Code FTA). RS Report Status DLMS Note: Use for customer followup indicating a request to provide receipt status for material previously reported as shipped (DLSS DI Code FTT). 5 2/BLI01/010 Add qualifier ZZ to Data Element DLMS note 235. Revise qualifier ZZ DLMS note to state: ZZ 6 2/BLI05/010 Add DLMS note 2: Mutually Defined DLMS Note: Use to identify nonstandard material when all other authorized codes do not apply or cannot be determined (includes management control numbers and locally assigned control numbers). May be used for DLSS-to-DLMS conversion when the translator cannot determine a more appropriate code. DLMS enhancement; see introductory note 2a. 7 2/N901/011 Revise DLMS note for qualifier TG TG 8 2/N907/011 Delete qualifiers 43 and 72 Transportation Control Number (TCN) DLMS Note: 1. Enter the shipment unit TCN on customer follow up due to nonreceipt of receipt acknowledgment. 2. Future streamlined data; see introductory DLMS note 2c. 43 Supporting Document Number (used for SPR number) 72 Schedule Reference Number (used for excess plant property number) Deleted codes are not applicable to this IC (inadvertently added during previous IC update). Requires Federal IC change prior to DS update

5 9 2/LQ01/058 Revise DLMS notes for qualifier A9 to read: A9 Supplemental Data DLMS Note: 1. Use to identify supplemental address/data. 2. During the DLSS/DLMS transition, this field will be used to perpetuate/populate the DLSS Supplemented Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see introductory note 2d. 3. Expanded use of this field for supplemental data without field size restriction is a DLMS enhancement; see introductory note 2a. 4. Under full DLMS, the requirement to pass activity address information within the supplemental data field will be streamlined. Activity address data previously contained in the SUPAAD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 2c. 10 2/N101/060 Revise DLMS note for the following qualifiers: 77 Service Location DLMS Note: Use for material availability reports and automatic shipment notifications to identify the party to receive packing, crating, and handling credit when different from the party to receive credit for material. Data maintenance action to add qualifier CRP for this purpose has been approved for a future version Clarification/update. SF ZB ZZ 2. DLMS enhancement; see introductory note 2a. Ship From DLMS Note: Use in material availability reports and automatic shipment notifications to identify the organization from which the material is shipped if different from the organization originating the transaction set. Party to Receive Credit DLMS Note: Use as needed for material availability reports and automatic shipment notifications to identify the organization to receive credit if different from the organization originating the transaction set. Mutually Defined DLMS Note: 1. Use for material availability reports and automatic shipment notifications to identify the party to receive transportation credit when different from the party to receive credit for material. Data maintenance action to add qualifier CRT for this purpose has been approved for a future version Simplifies business rules. Simplifies business rules. 2. DLMS enhancement; see introductory note 2a. 11 2/DTM01/130 Add new DLMS note 2 to the following qualifiers: 036 Expiration 2. Supports AMCL 5 (MILSTRAP) & 13 (MILSTRIP); see introductory DLMS note 2b. 510 Date Packed 2. Supports AMCL 5(MILSTRAP) & 13 (MILSTRIP); see introductory DLMS note 2b.

6 12 2/LX/170 Add new segment DLMS note 2: 2. UIT information is provided as a DLMS enhancement; see introductory note 2a. 13 2/FA102/225 Add Data Element 1300 DLMS note: DLMS Note: All qualifiers listed below are associated with a DLMS enhancement; see DLMS introductory note 2a. 14 2/FA2/226 Add new segment DLMS note: DLMS Note: All qualifiers listed below - with exception of B5, Fund Code are associated with a DLMS enhancement; see DLMS introductory note 2a. *15 2/LM02/57 Mark LM02 as Not Used. Correction. There is no requirement for this data element. Revision is consistent wit h other DLMS transactions Requires Federal IC update d. Alternatives: None identified. 5. REASON FOR CHANGE: These administrative changes support DLMS implementation and desired functionality. 6. ADVANTAGES AND DISADVANTAGES: a. Advantages: Supports DLMS implementation b. Disadvantages: None identified 7. IMPACT: a. Publications. Federal Implementation Conventions 180M and corresponding DoD M DLMS Supplement. The DS revision requires prior change to the Federal Implementation Convention (IC). All applicable revisions will submitted to the Federal IC. b. DAAS DLMS/DLSS conversion map has been modified to incorporate above revision. * Corrected Page, June 20, 2002