Redundant mapping of the discretely identified activities is required during an extended transition period to ensure interoperability in a mixed DLMS/legacy environment. AP2.10.3.1 Although identified in the transaction, the signal code in requisitions, including referral and passing orders, must also designate the role/placement of legacy fields containing the intended consignee (ship-to), and the activity to receive and effect payment of bills, when applicable. In the case of the MRP, the signal code designates the role/placement of fields containing the intended consignor (ship-from) and the activity to receive and process credits, when applicable. All requisitions/asset reports will contain the appropriate signal code. AP2.10.3.2 The coding structure and its meaning for requisition documents are shown in Table AP2.10.T3. Table AP2.10.T3. DLMS-Formatted Requisitioning Transaction Business Rules Code Ship to . . . Bill to . . . Notes A Requisitioner Requisitioner Supplemental data Requisitioner DoDAAC Requisitioner DoDAAC perpetuated to the bill perpetuated to the bill (LQ01/Code A9) and ship-to and ship-to (N101/Code BS) (N101/Code BS) B Requisitioner Addressee (other than Perpetuate bill-to DoDAAC to Requisitioner DoDAAC the requisitioner) the supplemental data perpetuated to the designated by the bill-to (LQ01/Code A9) (N101/Code BT) (N101/Code ST) C Requisitioner Addressee (other than Supplemental data Requisitioner DoDAAC the requisitioner or perpetuated to the ship-to) designated by (LQ01/Code A9) the bill-to (N101/Code ST) (N101/Code BT) Bill-to DoDAAC must be associated with the fund code in the Fund Code to Billed DoDAAC Conversion Table D Requisitioner No billing required (free Supplemental data Requisitioner DoDAAC issue) perpetuated to the (LQ01/Code A9) (N101/Code ST)
Redundant mapping of the discretely identified activities is required during an extended transition period to ensure interoperability in a mixed DLMS/legacy environment. AP2.10.3.1 Although identified in the transaction, the signal code in requisitions, including referral and passing orders, must also designate the role/placement of legacy fields containing the intended consignee (ship-to), and the activity to receive and effect payment of bills, when applicable. In the case of the MRP, the signal code designates the role/placement of fields containing the intended consignor (ship-from) and the activity to receive and process credits, when applicable. All requisitions/asset reports will contain the appropriate signal code. AP2.10.3.2 The coding structure and its meaning for requisition documents are shown in Table AP2.10.T3. Table AP2.10.T3. DLMS-Formatted Requisitioning Transaction Business Rules Code Ship to . . . Bill to . . . Notes A Requisitioner Requisitioner DoDAAC perpetuated to the bill and ship-to (N101/Code BS) Requisitioner Requisitioner DoDAAC perpetuated to the bill and ship-to (N101/Code BS) Supplemental data (LQ01/Code A9) B Requisitioner Requisitioner DoDAAC perpetuated to the (N101/Code ST) Addressee (other than the requisitioner) designated by the bill-to (N101/Code BT) Perpetuate bill-to DoDAAC to the supplemental data (LQ01/Code A9) C Requisitioner Requisitioner DoDAAC perpetuated to the (N101/Code ST) Addressee (other than the requisitioner or ship-to) designated by the bill-to (N101/Code BT) Supplemental data (LQ01/Code A9) Bill-to DoDAAC must be associated with the fund code in the Fund Code to Billed DoDAAC Conversion Table D Requisitioner Requisitioner DoDAAC perpetuated to the (N101/Code ST) No billing required (free issue) Supplemental data (LQ01/Code A9)
0210-AP2-10.docx