Professional Documents
Culture Documents
SAP Order Structure 1.0
SAP Order Structure 1.0
I. Objective
The objective this document is to define the standards for creating purchase/work order to
ensure:
1) that all orders will have uniform structure
2) Adequacy and completeness of the purchase/work order document.
II. Order Structure
The following will be integral part of any purchase or work order. When order is printed, by
default system would link / print annexures 1, 2 and 3. Annexure 4 will be maintained in
DMS (Document Management System – SAP repository) for reference purpose and can be
printed separately as the case may be.
1. SAP Order
2. Annexure 1 (SCC)
3. Annexure 2 (GCC)
4. Annexure 3 (Scope, Specifications, BoQ)
5. Annexure 4 (Vendor Communications)
A. SAP Order
SAP order will consist of the following:
1. Reference to enquiry, offers and communications
2. Material details as per PR including HSN codes. For service orders, service codes and SAC
will apply.
3. Price (Basic Price, Freight Cost, Insurance Cost, any other charges, GST)
4. Bank Guarantee
5. Buyer and Seller details
6. Delivery schedule
7. Inco‐terms
8. Payment terms
9. Liquidated Damages for Delayed delivery / Performance
10. Documents & Certificates (e.g. MOC, IBR Certificates, Fitment & Interchangeability
Guarantee, Warrantee etc)
11. Enclosures to be mentioned in SAP Order – SCC, GCC, BoQ, Scope, Technical Documents
B. Annexure 1 (SCC)
1) It will be a MS Word prepared document and final copy will be converted to PDF file.
2) SCC will have two sections.
• Part‐1: This is the initial section of SCC and to contain clauses of SCC ‐ which are
applicable to all orders. If there is any clause NOT relevant to order, ‘Not Applicable’
SAP Order Structure REL/22‐07‐2018/1.0 Page 1 of 7
to be put against that clause. In addition SCC to specify order of precedence, Scope
and deliverables, SLA, BG Formats, Contract closure documents like NDC and Letter
of Indemnity.
• Part‐2: Addendum – any additional specific clauses of order will be put here.
3) The final PDF converted file shall be maintained in DMS.
C. Annexure 2 (GCC)
1) A standard GCC document in PDF format.
2) The signed off copy by the vendor will be maintained in DMS and shall form an integral
part of the order.
3) It will be linked to order at the time of printing.
4) As this is a PDF file, it will retain all formatting.
D. Annexure 3 (Scope, Specifications, BoQ)
1) This section contains technical documents relevant to order. Detailed Scope,
Specifications and BoQ obtained and agreed with vendor will be maintained in this
section.
2) These documents should be PDF files to a have uniform printing.
E. Annexure 4 (Vendor Communications)
1) This section contains all correspondence with the vendor.
2) It will be maintained in Vendor Correspondence section in DMS.
The final Order shall be after incorporating enquiry, offer and all vendor communications.
SAP Order Structure REL/22‐07‐2018/1.0 Page 2 of 7
Need Validation Template
Date:
S. No Description Details Remarks
Name of the Company
1 Business Plant
Department
2 User Details: Name, Contact
No, Email ID
Supply
3 Category of Requirement Service
Supply and Service
4 Description of requirement
(Title)
CAPEX
5 Budgetary provision OPEX
Others (Specify)
Yes
6 Budget allocated/ approved
No
Total Budget for Financial Year
Budget available as on date
7 Budget Status (with Taxes) Budget Consumed in this requirement
Balance Budget after allocating for this
requirement
Up to 50 Lac
>50 Lac to 1 Crore
8 Category as per DOP (in INR)
>1 Crore to 3 Crore
>3 Crore
9 Approving Authority as per
DOP
Last Purchase Price/PO Reference No
Vendor’s offer
10 Basis of Budgeted Value
CPG inputs
Others ( Pl specify)
One Time
Regular
11 Type of Requirement
Renewal of existing contract
New Requirement
Normal
12 Priority of requirement Critical
Emergency
Operational/Maintenance/Overhauling
Efficiency/ process improvement
Statutory/ Regulatory requirement
Corporate Social Responsibility(CSR)
13 Requirement basis Related to Environmental/ Safety/
Occupational hazard requirement
New Business initiative
New technology adoption
Pilot project/ Proof of Concept
SAP Order Structure REL/22‐07‐2018/1.0 Page 3 of 7
Need Validation Template
Date:
S. No Description Details Remarks
Customer value enhancement
Expected benefit to the organisation
Alternate product/technology
analysed
Change in requirement w.r.t to
previous year
Usage/application of Product/Service
Technology Road Map/obsolesence
Justification for the Material Timeline
14
/ Service required Past 3 years utilization trend
Review of similar requirement for
other Business
Life cycle cost/ ROI/ Break‐ Applicable
15
even analysis as applicable Not applicable
Critical
16 Inventory Position
Non‐Critical
OEM
17 Supplier Type
Non‐OEM
18 Lead Time for Procurement In number of Weeks
19 Required at Site for Supply /
Start and End Date for
Service
Scope of Work ( As per enclosed
format)
BOQ with Specifications
20 Document enclosed Drawings
Stock level and Stock availability in
number of days
Any other documents ( if any)
Vendor Panel
Justification in case of proposal on
Single Vendor Basis
Past performance report of vendors if
21 Vendor details available
PQ evaluation matrix along with
marking system and minimum
qualification criteria
MIS/ Progress report formats
Proposing officer
Validating officer
Budget allocating authority
22 Proposal Sign‐off Approving authority
Technical offer evaluator
Project/ Engineer‐in‐Charge
Overall co‐ordinator
SAP Order Structure REL/22‐07‐2018/1.0 Page 4 of 7
Checklist for Scope of Work
Reference No: Date:
S No. Description Details Remarks
Supply Yes/No
1 Category of Requirement Service Yes/No
Supply and Service Yes/No
2 Description of requirement
Design Yes/No
Manufacture Yes/No
/Assembly
Testing Yes/No
Drawings, Data and Yes/No
inspection Manuals
Tools and Tackles Yes/No
Spare Parts for support Yes/No
Startup and Yes/No
3 Scope of Work
Commission of spares
Mandatory spares Yes/No
Transportation, Yes/No
Loading, unloading ,
storage and stacking
requirements
Admin and Overhead Yes/No
List of documents Yes/No
required from vendor
Others (Specify) Yes/No
Supervision, Erection, Yes/No
Commissioning, Trial
run and handing over
4 Scope of Work ‐ Service
Only Supervision of Yes/No
Erection,
Commissioning
BOQ covering item
description, Qty makes
and model,
5 Supply Deliverables specification
Spares, after sales
service & warrantee
requirement
Deliverables
Responsibility Matrix
6 Service Required Exclusions/Inclusions
Free issue Material ( if
any)
Details of location(s)
for which
7 Location
supply/service
required.
Required at site date
8 Delivery Schedules
(RAS) for supplies
SAP Order Structure REL/22‐07‐2018/1.0 Page 5 of 7
Checklist for Scope of Work
Reference No: Date:
S No. Description Details Remarks
Time Period From and
Start dates for services
Type of resource Yes/No
Required
Skilled Number………
Semi Skilled Number………
Unskilled Number………
Type of wages (state or
central minimum
wages)
Working pattern (26
days or 30 days)
Profile/Experience of Yes/No
the Manpower
required with count of
each type
9 Manpower Required Manpower CV Yes/No
required or not
Reliever/Backup Yes/No
Manpower required to
be specified
Tools and Plants (T&P) Yes/No
Required
Manpower based / KPI
based / BOQ Based
Comprehensive /Non
Comprehensive
Consumables Details ‐
included/excluded
T&P included/excluded
OEM/Non OEM
10 AMC Details
Support
BOQ ‐ list of
equipment, OEM Serial
Number, Makes and
model, Current
AMC/Warranty
dates/Location of
equipment
Specify SLA and
11 Service Level Required
Associated Penalties
Quality Assurace plan
(QAP), Inspection &
Quality Testing and Inspection
12 Testing requirements
Requiement
FAT & SAT details
Field quality plan
13 Document enclosed BOQ covering item
SAP Order Structure REL/22‐07‐2018/1.0 Page 6 of 7
Checklist for Scope of Work
Reference No: Date:
S No. Description Details Remarks
description, Qty makes
and model in excel
format
Technical
Specifications
Tender Drawings
To be provided by
Facilities to be provided for
Vendor
14 Storage,Watch & Ward, Electricity or
To be provided by
any other facility
Buyer
Statutory and Regulatory approvals Scope of Vendor
15
Required Scope of Buyer
Vendor
16 Vendor Prequalification Prequalification
Requirements
Evaluation Matrix
17 Technical Evaluation Process Technical Approval
Criterion
SOW Document Reference number and Document Number Yes/No
18
version release history and Version
Created By
Approved By
Technical Evaluator
SOW Release approval
19 Project/ Engineer‐in‐
(Name, Sign and Date)
Charge
Overall co‐ordinator
Consultant
SAP Order Structure REL/22‐07‐2018/1.0 Page 7 of 7