Military Interdepartmental Purchase Requests (MIPR)

Creating and using MIPRs

Overview

A Military Interdepartmental Purchase Request (MIPR) is used when one department within the DoD (or any non-DoD department) requests for goods or services that can be provided by another site / department (through an existing contract, for example). The MIPR provides funding information and a description of the goods and services required. The MIPR is created by the requesting agency, it is generated on the DD-448 standard form and send to the assisting agency.

When the MIPR is received, the assisting agency must formally accept or reject MIPR by completing DD448-2 form, Acceptance of MIPR form. Primarily the Acceptance of MIPR form has funding information, Reimbursement Order (Category I) or Direct Citation (Category II) based on which receiving/invoicing/payment processes are determined. The MIPR acceptance form is sent to the requesting agency.

The assisting agency determines whether to use the Reimbursement Order (Category I) or the Direct Citation (Category II) method of funding. With the Reimbursement Order (Category I), the assisting agency pay for the items up front and is then reimbursed by the requesting agency. With Direct Citation (Category II), the requesting agency provides the funds up front.

An example of where a MIPR might be used is when an enhancement/fix needs to be applied to a software/system that is implemented at multiple government agencies. While one agency may be overseeing the contracting services that are responsible for developing the fix, the agencies that will benefit from the enhancement provide a certain percentage of the funds to pay for the software enhancement. These funds are recorded in the form of a MIPR and sent to the overseeing agency. The overseeing agency then receives the MIPR in the contracting system.

Funding Methods

There are two funding methods for a MIPR:

Shopping Cart

MIPRs can be created using any appropriate CLM iProcurement responsibility. MIPRs are created in a manner similar to purchase requisitions.

MIPRs can be created for both catalog as well as non-catalog items. Add items to your shopping cart in the same way you would do for regular purchase requisitions and click Checkout. In the Shopping Cart page, below the line details region, you will see a checkbox – Military Interdepartmental Purchase Request. If you select this checkbox, you are indicating to the system that this purchase requisition is a MIPR. This checkbox is not enabled by default. When you select this checkbox, the MIPR Type list of values displays with 2 values: Military Interdepartmental Purchase Request – Others and Military Interdepartmental Purchase Request – Own (the same agency can play the role of requesting agency as well as assisting agency). Select Military Interdepartmental Purchase Request – Own when you wish to create a MIPR for your own agency (your agency is the requesting agency as well as the assisting agency). Select Military Interdepartmental Purchase Request – Others for incoming MIPRs from requesting agencies, for which your agency is the assisting agency. If either of these values are selected (Military Interdepartmental Purchase Request – Own is the default value), the relevant MIPR information is displayed in the Requisition Information page and related pages.

MIPR Assisting Agency is a business classification for suppliers or supplier sites, using which a MIPR Assisting Office can be defined as a supplier. A MIPR Assisting Agency displays it's contact and location details (as a supplier) when a MIPR-Own is created.

MIPR Requesting Agency is a business classification for suppliers or supplier sites, using which a MIPR Requesting Office can be defined as a supplier. This supplier (MIPR Requesting Agency) displays their contact and location details when a MIPR-Others is created. For MIPR-Others, the requesting office is an external agency, so the MIPR-Others is defined and set up outside of the HR locations (HR Extra Information Types form).

For information about setting up the Assisting Agency, and Requesting Agency, see: Oracle Contract Lifecycle Management for Public Sector Implementation Guide.

The Checkout: Requisition Information page displays the MIPR related fields along with the purchase requisition information. After you have entered the Requisition Name and Date Prepared (the MIPR Type you selected in the Shopping Cart page displays in this page too), navigate to the Addresses region. You need to enter the addresses, including the MIPR related addresses, Invoice Office and Assisting Office. Enter a Location, an Address Code and a Contact for the Invoice Office and Assisting Office addresses and save your work.

The MIPR Information region enables you to enter MIPR specific details. Enter relevant data in the fields provided.

FSC/PSC: The Federal Supply Classification (FSC) is a set of codes designed to help the federal government in supplying operations.

Use the field Reimbursable Agreement to enter the value for Reimbursable Agreement Number or Contract Number for the MIPR. This will flow down to award as well.

Control Symbol Number: optional text field.

Transportation Allotment: optional text field.

Signature: The values for this dropdown are: None, Proxy Signature, Signature.

Authorizing Officer: Use the LOV to select a person who will sign the DD-448 form.

Statutory Authority: This is a mandatory field. Enter the specific authority that is cited for making the acquisition.

The MIPR Acceptance region displays for all MIPR type MIPR – Others; however for the MIPR type MIPR – Own, the MIPR Acceptance region displays only if you have selected the MIPR Acceptance checkbox in the Setup: Purchasing Options page > CLM Options region.

Enter the relevant field values in the MIPR Acceptance Information region. The fields marked with an asterisk (*) are required fields.

Click Edit Lines to open the Requisition Information: Edit Lines page. Click the Accounts tab and then click the Update button. The distribution details for the line display on the page. Click the Split Cost Allocation icon at the end of the line to view the ACRN details in the Charge Accounts tab or click the Charge Account link to view the ACRN details. You can enter an ACRN (Accounting Classification Reference Number). The ACRN along with the Appropriation and Limit/Subhead information gets printed in the DD-448 form. The ACRN can be entered by you or it can be system generated. Whether the ACRN is entered by you or is generated by the system, it should begin with AA and follow the numbering scheme cited in DFARS 204.7107 to include starting with A1-A9, B1-B9, etc., after ZZ. The letters I and O cannot be used in the ACRN number.

Each distribution (charge account) can be assigned one ACRN only. Each ACRN represents a given charge account within a single contract. For example, if the system assigns ACRN AA to charge account 112300023234YXZ, and if 112300023234YXZ happens to appear on multiple CLINs within the same contract, it will always be assigned to ACRN AA.

The Regenerate ACRN button enables you to allow the system to generate the ACRN across lines, even if you have entered the ACRN manually. If you click Regenerate ACRN, the changes you entered to the ACRN field are lost. This button is displayed only when the checkbox Enable MIPR is selected in the Setup: Purchasing Options page > CLM Controls region.

In addition, the Accounts tab also has a field called MIPR Obligation Type for each line of account. If the value of the MIPR Obligation Type field in the Checkout: Requisition Information page is Both, then you need to enter the MIPR Obligation Type value for each line.

Save your work and return to the Checkout: Requisition Information page by clicking Apply.

If all the remaining information (approvals etc) is entered in the MIPR, you can submit the MIPR for approval. MIPR–Own and MIPR–Others follow the same approval process as purchase requisitions.

For MIPRs that are of type MIPR-Own, click Submit to get the document approved by various approvers. Notifications are sent to the various approvers to inform them that they need to approve / reject the MIPR document. The MIPR Number is in the notification, making it easier for approvers to refer to. When all the approvers approve the document, the approval Status changes to Approved.

However this approved MIPR will not be available in Demand Workbench (thus you cannot create an award ). The approved MIPR-Own should have a status Approved, Acknowledged, which would make it eligible to show up in the Demand Workbench. In order to reach this status, (Approved, Acknowledged), the MIPR-Own needs to go through the MIPR acceptance acknowledgement action. The following sections describe how the MIPR-Own is accepted and acknowledged.

For MIPRs that are of type MIPR-Others, click Submit to get the document approved by various approvers. Notifications are sent to the various approvers to inform them that they need to approve / reject the MIPR document. The MIPR Number is in the notification, making it easier for approvers to refer to. When all the approvers approve the document, the approval status changes to Approved, Accepted. Other statuses can be Approved, Rejected; Approved, Rejected with Changes. These statuses are based on the MIPR Acceptance information. The approval status shows as Approved, Accepted only when MIPR Others with MIPR Acceptance status Accepted is selected.

Only MIPR-Others with a status of Approved, Accepted are eligible to be in displayed in the Demand Workbench. Thus you can also create an award from a MIPR-Others with a status Approved, Accepted.

Requisitions page

The Requisitions page enables you to search for and view MIPRs of both types – MIPR-Own and MIPR-Others – along with other requisitions. Use the search criteria to search for MIPRs. The search results display a column called Requisition Type that shows you whether the purchase request is a MIPR-Own, MIPR-Others or a purchase requisition.

The Requisitions page also enables you to perform various actions, depending on which MIPR Type you select. The Actions list of values changes it's values according to which requisition type you select using the Select radio button.

If you select a MIPR-Own, the following actions are available for you to use:

Receiving DD-448 by the assisting agency

The assisting agency receives the DD-448 as an email attachment /fax/print from the requesting agency contact. As the assisting agency contact, you need to check your email / fax / print to verify receipt of the DD-448 form from the requesting agency. To configure email to receive the DD-448, you need to perform some setup steps, the details of which are in the Oracle Contract Lifecycle Management for Public Sector Implementation Guide.

The Requisitions page also enables you to perform various actions, depending on which MIPR Type you select. The Actions list of values changes it's values according to which requisition type you select using the Select radio button.

If you select a MIPR-Others, the following actions are available for you to use:

The MIPRs thus completed are eligible to be available in the Demand Workbench of Buyer Work Center. Please note that the MIPR-Own should have a status of Approved, Acknowledged to be eligible for the Demand Workbench and the MIPR-Others should have a status of Approved, Accepted to be eligible for the Demand Workbench. In the Demand Workbench, if you click the MIPR number hyperlink, the MIPR information displays in read-only mode in a new page. For more information on autocreating MIPR lines to awards, please refer to the Buyer Work Center chapter of the Oracle Contract Lifecycle Management for Public Sector Purchasing User Guide.

Purchase Request Data Standard (PRDS) Inbound

CLM for Public Sector can receive purchase requisitions in a standard format from an external requisition system. This ability helps agencies achieve traceability and transparency of contract expenditures, by properly linking requirements, as found in purchase requests. It also helps agencies comply with the regulations for creating requisitions.

Requisitions are created using requisition web services. An XML file is imported from external federal systems, that the CLM requisition web service uses as a source file. When you invoke the requisition web service, the transformed XML is used to create a requisition in the CLM system. Note that the PRDS file is received with additional information when a MIPR (such as a DD-448 or DD-448-2 form) is imported. Use web services to validate the imported PRDS XML, and update the requisition tables.

For more information on setting up PRDS Inbound, see: Oracle Contract Lifecycle Management for Public Sector Implementation Guide.

Purchase Request Data Standard (PRDS) Outbound

The Purchase Request Data Standard (PRDS) schema is a way for the Department of Defence to standardize the Purchase Requisition data. This ensures that the right data is provided in order to establish Awards. PRDS is built to be compatible with the PDS for Awards. PRDS XML Generation establishes standard and accurate data that is in compliance with Department of Defense standards. The purchase requisition is also the source for critical data used in contract awards, and thus accurate PRDS XML generation is more important than ever before.

The system has the ability to send CLM iProcurement purchase requisitions outbound in the PRDS format. CLM generates PRDS compliant XML files. The PRDS files contain specific purchase request data elements. In order to ensure that CLM purchase requisition documents are compliant with DoD standards, the system capture all data elements as required by PRDS and also provides the ability to produce an XML file in accordance with the PRDS Schema. However, CLM currently does not support sending PRDS XML files to other agencies.

You can generate the PRDS XML file manually by running the concurrent program called Generate PRDS XML.

The PRDS XML file is auto-generated when the purchase requisition is approved. The Requisition Approval Workflow initiates the PRDS XML generation process if PRDS flag is enabled at office level depending on the requisition type.

In order to generate the PRDS XML file automatically for a purchase requisition, the following criteria must be met:

The Requisitions Details page has an Action History for PRDS. The PRDS field shows the value Yes with a link when the PRDS XML file is generated successfully. Click the link to open the PRDS Action History page. The concurrent request details, along with the posting information, is displayed in this page. The View XML link enables you to open or download the PRDS XML file.

The system notifies the final approver of the purchase requisition document when the PRDS XML file is successfully generated. This FYI notification is sent to the approver only when PRDS XML file has been successfully generated. The notification contains the details of the outbound directory path that contains the generated PRDS XML file.

The requester needs to go to the Action History page (View XML link) in order to view or download the PRDS XML file.