Professional Documents
Culture Documents
For
June 2021
ABOUT THIS MANUAL
This manual provides information and specific instructions on how to use the SAP S/4HANA MM
– Purchase Requisition (PR) module configured for the EEP. Using the manual, the user will be
able to apply the functions provided in the Purchase Requisition (PR) to conduct the activities
given to him/her.
Typographic Conventions
The standard used in this handbook is American English. The following typographic
conventions are also used.
Icons Used
The following icons are used.
Icon Meaning
Check Availability
Back
Caution
Save
Enter
Execute
ETHOPIAN ELECTRIC POWER
REVISION HISTORY
Document Revision History
OVERVIEW
Procurement in every organization starts with gathering requirements. SAP a purchase
requisition is a request that is made to the purchasing organization to procure a certain list of
materials or services. It is an internal document and remains within the organization. Purchase
requisition needs approval from the purchasing organization or requester department
supervisors.
Target Audience
This manual shall primarily be used by;
Pre-Requisites
Required Knowledge
Working knowledge of Microsoft Office and Internet browsers.
Familiarity with navigating the SAP.
Recommended Knowledge
Working knowledge of the PR business processes.
Objectives
Using this manual, you will be able to:
Able to create purchase requisition.
create Goods, Asset, Services Purchase Requisition.
Terms, Acronyms, Abbreviations Page 5 of 23 @2021 All rights reserved.
Created for EEP by ET
ETHOPIAN ELECTRIC POWER
Table of Contents
ABOUT THIS MANUAL..................................................................................................................................................ii
Typographic Conventions................................................................................................................................ii
Icons Used............................................................................................................................................................ii
REVISION HISTORY....................................................................................................................................................iv
OVERVIEW.................................................................................................................................................................... 5
Target Audience.................................................................................................................................................5
Pre-Requisites.....................................................................................................................................................5
Required Knowledge..........................................................................................................................................5
Recommended Knowledge................................................................................................................................5
Objectives.............................................................................................................................................................5
TERMS, ACRONYMS, ABBREVIATIONS......................................................................................................................6
Table of Contents.........................................................................................................................................................7
INTRODUCTION - PURCHASE REQUISITION...........................................................................................................8
I. Steps to Login to EEP SAP-HANA.................................................................................................................9
II. Steps to create Goods Purchase Requisition (PR)...............................................................................10
III. Service Purchase Requisition Creation...................................................................................................21
IV. Tables, Reports, and other T-codes.......................................................................................................23
ii. Subcontracting − Providing raw material to vendor and getting finished material.
iii. Consignment − Procuring material that is kept in company’s premises and paying to
vendor for that.
v. External service − Getting services like maintenance from third party vendor
A. Document type – define your purchasing type EEP Purchase type lists are below. For
our example lets choose EEP Goods PR
Header Note - You can insert details about the purchase Requisition.
Source Determination - to determine source we have to make sure that we have
source list and join for record for the particular material and vendor.
1. Account assignment(A),
Standards,
B - Limit,
K – Consignment, L - Subcontracting
S - Third-party, D – Service
3. Material code or Short texts - Material code will have its own description so in
case of material no need to insert description. Short Text- this field will be useful for
Service, Repair, works type PRs. So that you can describe your requirement in short
and precise key words. : 5000002001 – RED PEN
4. Quantity : 10
5. Unit of measure - Mostly SAP will take Master data Unit of measure. But you can
change it as per your requirement. Note that if the requirement is out of the given
measurements in Master data, - First you will be required to add the measurement in
the master data. Order unit for Pen is PAC – Pack: Optional field
6. Delivery date – 27.08.2021 The date you want the goods to in your office.
Optional field- SAP will take PR created date automatically
7. Material group – For material- it will automatically take form material. But in case of
Service or Work or repair PR , System will ask you to insert the Service group(Dept.
name created in SAP) or Material groups. E.g. 112 – General supplies
12. Vendor – if there is a source list or info record, or agreement or if your choose
direct vendor. You can insert the data then the vendor automatically come form the
fields(15,16,17) : Optional field
13. If there is a fixed vendor supplying this item. You can insert the vendor code.
14. Pur. Org. the Procurement Division that going to find source: STFP – Staff
procurement – Optional field
15. Agreement number: if there is an agreement between EEP Procurement Team
and supplier of this item. You can insert that agreement number created in SAP:
Optional field
16. Item number is line item in the Agreement: Optional field
17. Infor record - this field is master data that contains the combination of Material
and supplying vendor. Optional field
1. Line item number form PR overview: Each line item will have different
data views here. So, you have to switch up and down to get the details of each
line item.
2. Material Data- where you can change the material number if you want or you
can view the details of the material),
Example: Material number – 5000002001 - Red Pen – SAP
3. Quantities/Dates- Where you can change it also),
Example: 10 PAC
4. Valuation - where the material or service estimated price will be given here.
Example: One PAC PEN price: 252 ETB
Source supply- to discover the most suitable source of supply while creating a
purchase requisition, If there is in for record, known vendor, or agreement if you
have you can determine here.
6. Status is the place where you can view whether the PR have PO or not and
approved, blocked or not.)
8. Release Strategy – is where you can find approval status and level of
approvers (will appear when goods /Service needs approval
You can edit or see by expanding or collapsing or by clicking PR screen
details. For Cost center PRC1032 – Staff Procurement Division approval
looks like below.
Level 1: EEP Mgr. Staff Proc. For Request Approval
Level 2: EEP Mgr. FICO – For Budget stamp
Level 3: EEP Mgr. Warehouse – For the item is out of stock stamp
Note: Below can be changed as per the Approval Matrix.
G. SAVE.
8. Release strategy for Service PR will be different – As Mgr. Warehouse is not required for
Service approval.
Save.
Service PR is created