Requisitions {FPMO-1}

The creation and maintenance of Requisition are discussed in this manual.

Requistion Document Types

• Requisitions are  are not required by documents in the PM document hierarchy. 
• Can be used centralised and de-centralised. 
• The personnel throughout the institution who require goods or services or payment complete these documents. 
• Each document can handle any number of items irrespective if they are not defined, defined items or cheque requests. 
• Defined items are General,Stock or Library Items.
• The differences between R and I documents are that documents can only originate in the Finance i-Enabler while R documents originates from the standard ITS system {FPMO1-1} 
• Once budget control has been performed and a line on a document is sufficient or forced, funding for the expense is reserved by the Commitment generated.
• Commitments are cancelled on a request when a request results in a purchase order or stock issue or cheque issue or the request is cancelled or rejected.

Requistion Menu Option

• Update access to the document maintenance options {USERS-2,3}.  
• Document Security
• The first level is Access Restrictions on Document Type {FCSM-4}
• For process requistions the user must be linked to PM Access Restrictions.
• The Access restrictions for this option are:
  

• The area within which a user maintains and /or performs approval privileges is dependent on the permissions given to the user; refer the Finance Permissions Operational Manual.



• Set System Operational Definitions {FCSM-1b2}

• Account Type Definition {FCSC-21}
• The institution can create any number of new account types for PM as needed.
  

• Creditor Definitions {FPMM-2}
• Before a Creditor Code can be used in this option it must be defined on option {FPMM-2}.

• Store and item Definitions {FPMM-3, 22, 23}
• Before General and/or Stock Items can be used in this option it must be defined on option {FPMM-3, 22, 23}.
  

• Transaction Types for Request Events {FCSO-7}
• The users have no control over the Transaction type in this option, it is maintained by the program.  Transaction Types must be defined on option {FCSO-7} for the following events.
  

• Foreign Currencies {FCSO-21}
• Set the Type of exchange rate in Block 1.for the PM subsystem.
• Maintain the rates in Blocks 2 and 3.
• Process sequence 2 frequently.
  

• Change and Cancellation/Complete Reasons {FPMC-8}

• Create at least one reason code for Change, Cancel and Complete. This code will be used in Block 3 of this option.
  

• System Operational Definitions {FCSM-1b2}
  
• For Order System Operational Definitions, refer to the  System Operational Definitions manual.

• PM Subsystem Cycle. {FCSM-2}

• A user in this option must ALWAYS validate that the PM current cycle is correct before processing any documents.