Configuring The Purchase Order Release Strategy
Configuring The Purchase Order Release Strategy
The aim of the sap purchase order release procedure is to replace the manual written authorization
procedures. An electronic signatures is used instead, maintaining the dual control principle. The
person responsible for the processes of the requisition or other purchasing document in the system
have to approve by marking an "electronic signature" which can give the document legal force for
further processing.
Briefly, this is how the purchase order release strategy works :The release code is a two character ID allowing a person to release (clear, or approve) a requisition
or an external purchasing document. The release codes is basically controlled via a system of
authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
An example of configuring a Purchase Order Release Strategy :If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the
Purchase Order. There is only one characteristic created in this example. For controlling the Purchase
Order type, create characteristic for CEKKO-BSTYP and the value NB.
Steps for configuring the Purchase Order release strategy :1.
2.
3.
4.
e.g. NETVALUE
information message :Format data taken from Data Dictionary (press enter)
(for currency dependent field, you are prompt to enter the currency which the system then
converts the currency of the Purchasing document into this currency)
Mutliple values
Interval values
In the Value data, in the Char. value column, type >=10000 (equal or greater than
In the Char. (characteristic) tabstrips, type NETVALUE to assign your characteristics to the
class
Save your data and this message will appear :Class type 032: Class REL_PUR created