Professional Documents
Culture Documents
Contract Management
Packet Description
The Contract Management
packet describes the
process of creating
contracts from a Shopping
Cart, RFx, or Contract link.
MAGIC Flows
The individual MAGIC flows that are
included in this packet are:
Strategic Sourcing - RFx to
Award
Vendor Bidding Process
MAGIC Roles
The MAGIC Roles used in these flows are:
SRM- Manager Purchasing
SRM - Approver
SRM - Buyer Strategic Contract
SRM - Buyer Oversight
SRM - Buyer Strategic RFx
SRM Auditor
IM - Goods Receipt Processor Non
Nonstock
SRM - Buyer Operational
SRM Requisitioner
AP - Agency Invoice Processor
AP - Invoice Approver
A description of each role can be
found on the MMRS Website.
Contract Creation/Modification to
Release on Behalf of Agency
Contract Creation/Modification to
Release
R
l
Procure-to-Goods Receipt with
Contract and without Contract
Goods Receipt to Pay Paymode
Goods Receipt to Pay NonPaymode
Help or Questions
Click here to learn how to read a
MAGIC Business Flowchart.
If you have
h
a question,
ti
please
l
use
the MAGIC Feedback webpage to
submit your question.
Significant Changes
To create a contract, MAGIC will include the functionality of building on the
documents used in the bid invitation to create the contract.
Agencies will be able to customize reports according to their needs.
Agencies will be able to track what has been expended against the contract.
Agencies will be able to view procurement documents (PO, invoices, etc.) released
against the contract in one system.
Statewide contracts will be posted to a single website: ms.gov.
Agencies will no longer enter information into the award-contract interface.
Complete entry of
RFx information
Publish RFx in
SRM
Enter (Surrogate)/Bid
Response(s)
Create Contract
No
NO
Yes
Yes
Award(s)
Approval
RFx Publish
Approval
UWL
Vendors/Bidder
SRM Approver/Manager
Vendors
Submit/Resubmits
Bid Responses via
Supplier SelfService(SUS)
SUS Bidder
Vendor(s) Search
for appropriate
RFx
Complete entry of
RFx Response
information
Submit RFx
Response
Publish Intent to
Award
(Optional)
Bidding Process
Completed
No
Approve
Award(s)
Yes
Bidder
Completes entry of
RFx Response
information
Submit RFx
Response
Bid Opening
All bids have been
received (Paper) and
Electronically
SRM BuyerStrategic
SUS Bidder
Vendor(s) Search
for appropriate
RFx
Complete entry of
RFx Response
information
Submit RFx
Response
Bid Response
has been received
SUS Bidder
Vendor(s) Search
for appropriate
RFx
Submit RFx
Response
Bid Response
has been received
Buyer enters
Surrogate (Paper)
Response on behalf
of the supplier
SRM Requisitioner
SRM Approver /
SRM Manager
SRM Buyer
Operational
SRM Manager
Purchasing/SRM
Approver
Goods Receipt
Processor Non
Stock
Create
Order
Shopping Cart
Shopping Cart
Reject
Workflow
Shopping Cart
Approval
Rejection Alert/
Notification sent to
SC creator
No
Approve
Is Shopping
Cart to be
Sourced?
Yes
Assign Source
of Supply
(Contract /
Supplier)
Create / Edit
Purchase Order
Order Purchase
Order
Reject
Workflow
Purchase Order
Approval
Approve
Purchase Order
Submitted to Vendor
Goods Received
Post
Goods Receipt
with
Doc Type WE
MIGO
Invoice can be
created
Oversight Buyer
Contract Marked
as approved
(Oversight
Approval flag
updated)
Create Contract
with Buy on Behalf
flag checked on
Contract sent to
Agency for their
Review
Contract will be
reviewed by the
agency for approval
& modifications if
changes are
needed.
Contract
Successfully
Negotiated with
Awarded Vendor
Offline
Contract Released
Reassign Buyer on
Contract to
Agency Buyer
(Workload
Redistribution)
Create/Edit
Contract
SRM Approver/
Manager
Release Contract
for Approval
Reject
Workflow
Contract
Approval
Approve
Workflow
Is Oversite
Approval
required?
No
UWL
Oversight
Approver
Yes
Reject
Workflow
Contract
Approval
UWL
Approve
or
MIGO
AP Invoice
Processor
Goods Receipt
Processor Non-Stock
ML81N
MIRO
AP Invoice
Approver
Invoice is
attached via
open text
Reject
Workflow
LIV invoice
Approval
SBWP
Approve
Workflow
Determines if OFM
Approval Required
No
SBWP
DFA/OFM
Yes
Reject
Workflow
LIV invoice Approval
Invoice Document
Post
SBWP
F110
Payment is made
Paymode-X
Goods
Movement
Processor
Was PO
Automatically
Matched
?
Yes
NOTE: Invoice is Attached
via OPEN TEXT
AP Invoice Approver
AP Invoice Processor
No
Note: All non-PO Invoices and all
non-matched POs are on table.
Review the
ZFAP_PM_INV_ENT
ER-Paymode invoice
error reprocess table
Payment is made
MIGO
MIGO
Electronic
Invoice
Submission
Automatically Saves
Goods Receipt as
Complete
Process
Goods Receipt
No
Mark as no PO
required
FV60 (Direct)
Is PO missing?
Add PO reference
Yes
MIR7
Workflow
invoice Approval
Approve
SBWP
No
SBWP
Yes
Reject
DFA/OFM
Workflow
Determines if
OFM Approval
Required
Rejected documents
return to ID stored on
cost center for Paymode
processing for
corrections
Reject
Workflow
invoice Approval
Document
Post
Payment Process is
run (OFM)
SBWP
F110