MMR Transaction Type

The Master Agreement Mod Request (MMR) Transaction Type is used to modify the Master Agreement (MA) transaction after it has reached a Phase of Final. Transactions of the MMR Transaction Type can be created from the Contract Catalog or by using the Copy Forward button on the Master Agreement (MA) transaction. Multiple draft MMR transactions against a single Master Agreement can exist simultaneously and users can independently workflow multiple modifications to the same agreement and apply approved modifications in the order of approval. The MMR transaction allows accepting the modifications expressed in the delta format and applying those deltas to produce new versions of the latest 'Final' version of an existing Master Agreement. Users can either directly modify the MA by clicking Edit and creating a new MA Modification or use the MMR to generate a MA Modification transaction. The MMR can only be created by using the Copy Forward action on a Final version of a MA transaction. These two methods can be used simultaneously together. Both transactions can be displayed from the Contract Catalog page or the Transaction Catalog page.

The MMR transaction contains the majority of Master Agreement fields with the most recently submitted values. All of the values for the previously submitted transaction ("existing" values) are protected and shown on the left side column for informational purposes only. Any modification/changes need be performed on the right hand side in the "new values" column. Only enter values in those fields you wish to change. If the field to be updated is a 'check box' in the 'existing' values, it displays with a drop-down box in the 'new values' column and is defaulted to No Change. If the check box for the existing value is blank, select Yes if you want it checked. If the check box for the existing value is checked, select No if you want to have it unchecked.

When the MMR transaction is saved or validated (or submitted to pending) the system refreshes the values for all existing left hand side fields based on the latest 'Final' version of the MA transaction. The data in the existing values column is not refreshed after the transaction has been submitted. On validate of the MMR, the system generates a MA Modification Draft from the latest final version of the MA and passes values from the MMR to the MA Modification Draft. The system them triggers the standard validations against this MA Modification Draft. If any validations fail, the system discards the MA Draft and displays errors to the MMR. If all validations pass, the MA Modification Draft is submitted or sent to workflow for approval. The MA modification submit phase is based on the Procurement Transaction Control (PRDOC) “Submit Phase for MA created from MMR” field. When this field is set to Final, the MMR will create a MA modified version with Phase set to Final irrespective of the Transaction Control (DCTRL) Submit phase setup. When set to Pending/Blank the MMR will create the MA modification version based on the DCTRL submit phase.

The MMR contains the following tabs:

• Header

• Renewal Period

• Authorized Department

• Authorized Unit

• Vendor

• Commodity

• Commodity T & C

• Sub Vendor

• Terms and Conditions

• Award Details

• Surety/Insurance

MMR Delivered Transaction Codes

Related Topic(s):

• MA Transaction Type

• The MMR Transaction Type belongs to the Award State.