|
|
The Requisition document is designed to be a simple vehicle that enables you to enter onto the system all your goods and/or service requirements whilst maintaining control over expenditure. This document forms the basis for the creation of an Order and the eventual placement of this Order with a Supplier.
Requisitions are created in response to a number of demands. Their purpose can be summarised as follows:
The system has been designed to allow you to create a Requisition Header and Lines with the minimum of information. This facility is achieved by having a number of default values attached to a particular entry. For example, each CP User will have default values attached that cover all mandatory Header and Control information and each 'Item-coded' line will default supplier and price information.
The diagram illustrates the impact of Requisition creation within the Requisition Business Cycle.
Diagram pm440
The creation of a Requisition is the initial process in the Requisition Business Cycle.
Each Requisition created is assigned a unique reference. The reference can be assigned by one of three different methods determined via the PM Controls:
As the PM Company Controls allow for the customisation of the creation process then a number of factors have the potential to affect the creation of a Requisition:
The diagram illustrates the sequence of screens accessed during the creation of a Requisition.
Diagram pm490
If authorisation by GL responsibility/Value within GL responsibility/Level within GL Responsibility is being used then instead of screen MDB7 being shown screens MDB8 and MDBU will be shown.
See also
Purchasing Management Home Page