Project – SARTHI

UPPTCL SAP Implementation

Business Blueprint Design Document

Materials Management

Inter-store Stock Transfer

300.1.02.03.04

Version 0.4

BBP-300.1.02.03.04 Page 1 of 24 Project – SARTHI

Version 0.4
 Document History
Version Date Summary of Change Author Role
V 0.1 08.03.2021 Creation of document. Vibha Tripathi/Syed Functional
Ahmad Consultant - MM
Zeeshan/Himanshu
Rawat
V0.2 23.03.2021 Updates in document post Vibha Tripathi/Syed Functional
BBP workshop Ahmad Consultant - MM
Zeeshan/Himanshu
Rawat
V0.3 12.05.2021 Updates in document as per Vibha Tripathi/Syed Functional
changes suggested by PwC Ahmad Consultant - MM
Zeeshan/Himanshu
Rawat
V0.4 12.05.2021 Updates in the document as Vibha Tripathi/Syed Functional
per changes suggested in the Ahmad Consultant - MM
BBP Workshop Zeeshan/Himanshu
Rawat

Other Related Documents

Related Document Comments
As-Is Document 200.2.02.03.04
FRS Document

Review/ Approval Detail

Role Name Signature and Comments
Date
Review
Accenture Vibha Tripathi/Himanshu
Module Lead Rawat
Core Team Mr. Keshav Dev
Mr. Rajesh Kumar Rajan
Project Mr. Chandra Vishal
Manager
UPPTCL
Project Mr. Bibhudutta Panigrahi
Manager
Accenture
Approval

Core Team

BBP-300.1.02.03.04 Page 2 of 24 Project – SARTHI

Version 0.4
 Checklist

Business Event Description

Are the Business Considerations and “To-Be” process event descriptions complete?
Are the descriptions clearly written? (Free of jargon, logically organized etc.)
Has the Document History been continuously updated?
Has the Functional Requirement Specification spreadsheet been updated with the
BBP ID?

Business Process Flow

Have standard symbols been used?
Have all Steps in the proposed To-Be Business Process document been identified in
detail?
Do the process flows reference appropriate manual and system steps?
Are the flows at an appropriate level of detail?

Other
Have Configuration considerations been considered?
Have differences between current and To-Be processes been documented?
Have the To-Be Impacts been identified?
Have all the gaps been documented?
Have all reporting items been identified?
Have all high-level conversion considerations, including data and volume been
documented?
Has the application architecture been updated to reflect interfaces?
Have all referenced items been noted and attached where appropriate? (Other
Business Process Design Documents, Process Flows, Spreadsheets, etc.)
Have all exceptions and process variations/ scenarios been documented?
Have the Cutover and Transition Considerations been noted including the Action
Required?
Have the Key Assumptions been noted?
Have all software or business specific terminology been explained in the Glossary of
Terms?

BBP-300.1.02.03.04 Page 3 of 24 Project – SARTHI

Version 0.4
 Table of Content
1. Business Blueprint Design Document Overview: ............................................................................... 5
2. To Be Process – Inter-store Stock Transfer ......................................................................................... 7
2.1 Specific Definitions of the Terminologies Used.....................................................................................7
2.2 Business Scenario – Inter-store Stock Transfer ................................................................................... 9
2.2.1 Process Description ............................................................................................................................10
2.2.2 Key Design Decision...........................................................................................................................11
2.2.3 Process Flow .......................................................................................................................................12
2.2.3.1 Stock transfer between stores in the same plant: ..............................................................................12
2.2.3.2 Stock transfer between stores in different plants: ..............................................................................12
2.2.4 Process Steps......................................................................................................................................15
2.2.4.1 Stock transfer between stores in the same plant: ..............................................................................15
2.2.4.2 Stock transfer between stores in different plants: ..........................................................................17
2.2.5 Gap Analysis ........................................................................................................................................20
2.2.6 Business Process Variations .............................................................................................................20
2.2.7 Cross Functions Integration Requirements .....................................................................................21
3. Assumptions and Dependencies ......................................................................................................... 21
4. Organizations/Entities Impacted .......................................................................................................... 21
5. Existing IT Systems and Interface Requirements ............................................................................. 22
6. High-Level Data Migration / Cut Over Requirements ........................................................................ 22
7. Decision Points for Operations Committee ........................................................................................ 22
8. SAP Standard Reports ........................................................................................................................... 22
9. Change Management and Business Impact Assessment................................................................ 23
10. FRS Mapping ............................................................................................................................................ 23
11. Addition Details ....................................................................................................................................... 24

BBP-300.1.02.03.04 Page 4 of 24 Project – SARTHI

Version 0.4
1. Business Blueprint Design Document Overview:

A. What is Business Blueprint Document (BBP)?

The business blueprint document is the main deliverable of the business blueprint phase. The
purpose of this document is to verify understanding of UPPTCL’s To-Be business process and
reporting requirements which also finalizes the detailed scope of the project.

Business blueprint document primarily covers To-Be business processes, process variations, MIS
and reporting requirements, integration with cross functions, and high-level interface requirements
with existing systems/applications

B. Developing and Updating the Business Blueprint

The business blueprint will be created in the business blueprint phase. This deliverable is a central
grouping of various disciplines. Blueprint deliverables and strategies will be the fundamentals for
development and management in the ongoing phases of the project.

After sign-off has been obtained from the relevant parties involved, a copy of the business blueprint
will be stored for reference only.

C. Document Availability
This document is readily available to all staff on the project through read-only access to the
controlled environment or a hard copy. Please note that the master copy is held in an electronic
format under the document reference.

D. Document Sign Off

Process definition document will be submitted to core team members (CTMs) for final sign-off.
CTMs are requested to respond within three (3) business days from the date of submission, after
which a discussion on the changes required will be initiated. The document must be signed-off
within five (5) business days after the same is submitted to the CTMs for the first time. If no
response is received from the CTMs within five (5) business days, then the document will be
deemed signed.

BBP-300.1.02.03.04 Page 5 of 24 Project – SARTHI

Version 0.4
Visio Legend

Visio Legend
FlowChart
Flow Shapes
ChartShapes

BBP-300.1.02.03.04 Page 6 of 24 Project – SARTHI

Version 0.4
2. To Be Process – Inter-store Stock Transfer

This process describes the intra-division and inter-division store stock transfer. The stock transfer may be
divided into intra-division and inter-division stock transfers depending on whether the stock transfer is
between stores in the same plant or stores in different plants.

This document details the To-Be processes related to store stock transfer relevant for UPPTCL.

2.1 Specific Definitions of the Terminologies Used

Term Definition
AA Assistant Accountant
AAO Assistant Account Officer
ABT Availability Based Tariff
ACR Annual Confidential Report
AE/SDO Assistant Engineer / Sub-Divisional Officer / Sub Division-In-Charge
ALDC Area Load Despatch Centre
AMR Automated Meter Reading
AO Accounts Officer
AUC Asset Under Construction
BoD Board of Directors
BOQ Bill of Quantity
C&C Communication and Control
CE Chief Engineer / Zonal In-Charge / Zonal Chief
CEA Central Electricity Authority
CERC Central Electricity Regulatory Commission
CMUT Central Monitoring Unit Transmission
CoD Commercial Operation Date
CPF Contributory Provident Fund
CT Current Transformer
CTM Core Team Member
CWIP Capital Works In Progress
D&P Design & Procurement
DI Dispatch Instruction
DISCOM Distribution Company
DoP Delegation of Powers
DPR Detailed Project report
DSM Deviation Settlement Mechanism
EE Executive Engineer / Divisional Officer / Division In-Charge

BBP-300.1.02.03.04 Page 7 of 24 Project – SARTHI

Version 0.4
Term Definition
EHV Extra-High Voltage
ERP Enterprise Resource Planning
ETC Electricity Transmission Circle
ETD Electricity Transmission Division
ETF Energy Task Force
ETI Electrical Training Institute
F&A Finance & Accounts
FMU Fund Management Unit
FY Financial Year
Genco / GENCO Generation Company
GL General Ledger
GPF General Provident Fund
GTP Guaranteed Technical Particulars
HO/HQ Head Office / Head Quarter
HR Human Resources
ICT Information and Communication Technology
IT Information Technology
JE Junior Engineer
JE Junior Engineer
LoI/LoA Letter of Intent / Letter of Acceptance
MB Measurement Book
MD Managing Director
MIS Management Information System
MM Materials Management
MoM Minutes of Meeting
MRD Meter Reading Data
MTB Monthly Trial Balance
NIT Notice Inviting Tender
NRPC Northern Regional Power Committee
O&M Operations and Maintenance
OA Office Assistant
OCC Operations Coordination Committee
PERT Program Evaluation & Review Technique
PGCIL / Power Grid Corporation of India Limited
POWERGRID
PM&A Personnel Management & Administration
PMA/ PMC Project Management Agency/ Project Management Consultant
PO/ WO Purchase Order/ Work Order

BBP-300.1.02.03.04 Page 8 of 24 Project – SARTHI

Version 0.4
 Term Definition
PoC Point of Connection
PQR Pre-qualification Requirement
PT Potential Transformer
PTW Permit to Work / Work Permit
PwC PricewaterhouseCoopers Private Limited
RLDC Regional Load Dispatch Centre
SCADA Supervisory Control and Data Acquisition
SE Superintending Engineer / Circle In-Charge
SEM Special Energy Meter
SLDC State Load Dispatch Centre
SMP Standard Maintenance Procedures
SoR Schedule of Rate
SSO / SO Sub-Station Operator
T&C Testing & Commissioning
T&P Tools & Plants
TBU Transmission Billing Unit
TWC Transmission Works Committee
UI Unscheduled Interchange
UPERC Uttar Pradesh Electricity Regulatory Commission
UPJVNL Uttar Pradesh Jal Vidyut Nigam Limited
UPPCL Uttar Pradesh Power Corporation Limited
UPPTCL Uttar Pradesh Power Transmission Corporation Limited
UPRVUNL Uttar Pradesh Rajya Vidyut Utpandan Nigam Limited
UPSEB Uttar Pradesh State Electricity Board
UPSLDC Uttar Pradesh State Load Dispatch Centre
W&P Works & Projects
WCT Works Contract Tax
WWCR Work Management Credit Report
ZO Zonal Office

2.2 Business Scenario – Inter-store Stock Transfer

Transfer postings between storage locations is a routine process for inventory movement as storage
locations are created for departments and contractors, project sites in the system. The store stock
transfer can be broadly classified into two processes:

BBP-300.1.02.03.04 Page 9 of 24 Project – SARTHI

Version 0.4
 1. Intra-store stock transfer, i.e., stock transfer between stores in the same plant.
2. Inter-store stock transfer, i.e., stock transfer between stores in different plants.

In stock transfer between stores in the same plant, a 2-step transfer posting in transaction code
MIGO will be used.

In stock transfer between stores in different plants, a stock transport order will be used.

2.2.1 Process Description

2-Step transfer posting in stores in the same plant:

Transfer postings between storage locations is a routine process for inventory movement as
storage locations are created for sub-divisions, departments, etc.

Levels for Stock Transfers

In a company, goods movements not only occur in the form of goods receipts and goods issues but
also in the transfer posting process as well. Depending on the organization of the company (for
example, decentralized storage) and its sales policy, internal stock transfers might also be
necessary.
Stock transfers can occur at three different levels:
 Stock transfer from plant to plant
 From storage location to storage location (within the plant)

Stock Transfer from Plant to Plant

A stock transfer from plant to plant not only leads to a change in stock quantity in both plants; if both
plants are assigned to different valuation areas, an accounting document is also created.
This type of stock transfer should only be carried out from unrestricted-use stock of the issuing plant
to unrestricted-use stock of the receiving plant.

A stock transfer from plant to plant generally takes place within a company code. It can, however,
also take place between two company codes, if the plants are assigned to different valuation areas,
which belong to different company codes.
Unlike a stock transfer from a storage location to another storage location, a stock transfer from
plant to plant affects both accounting and materials planning, as follows:
 Accounting
Accounting is affected if both plants are assigned to different valuation areas. This means that a
stock transfer leads not only to a quantity update but also to a value update (stock value, G/L
accounts). Thus, parallel to the material document for stock transfer, an accounting document is
created.

From Storage Location to Storage Location (within the plant)

BBP-300.1.02.03.04 Page 10 of 24 Project – SARTHI

Version 0.4
 A stock transfer from a storage location to another storage location takes place within a plant. It is
usually posted without value since the transferred material is managed in the same plant and
therefore has the same valuation data as before. If the material is subject to split valuation, and the
valuation type of the material changes due to the stock transfer.
Users can enter this stock transfer using either the one-step procedure or the two-step procedure.

2.2.2 Key Design Decision

Number Range:

There will be a dedicated number range for goods issue material documents.

S.No. Document Type Description Number Range

1. ZSTR Stock Transfer Indent 1400000000 – 1409999999
2 UB Stock Transport Order 5600000000 – 5699999999
3. A07 Goods Issue 4900000000 – 4999999999
4. A08 Transfer Posting 4900000000 – 4999999999
5. A10 Place in Storage 4900000000 – 4999999999

Technical Details of MIGO:

Executable action in MIGO transaction Reference Document for MIGO transaction

A08 Transfer Posting R02 Material Document
R09 Reservation
R10 Other
A10 Place in Storage R02 Material Document
R10 Other
A07 Goods Issue R01 Purchase Order

BBP-300.1.02.03.04 Page 11 of 24 Project – SARTHI

Version 0.4
 2.2.3 Process Flow

2.2.3.1 Stock transfer between stores in the same plant:

1. A requirement for material is received at the receiving location.

2. The requisitioner will then identify the source in the same plant.
3. After identifying the source, the requisitioner will then create a reservation in transaction
code MB21 with movement type 313.
4. The requisitioner will then get the reservation approved via a custom program.
5. The section-holder at the issuing location will then post a transfer posting against the
approved reservation in transaction code MIGO. A transfer posting material document will
be generated.
6. The user will then check if a gate pass is required for the material.
7. In case a gate pass is required, the section-holder will generate a gate pass via a custom
program and will submit it physically to the gate security. If a gate pass is not required,
proceed to the other step.
8. Now the section-holder at the receiving location will place the stock in-store in MIGO
transaction code by using the place in-store functionality against the transfer posting
material document number. This movement will take place with movement type 315.

2.2.3.2 Stock transfer between stores in different plants:

1. A requirement for the material is received at the receiving plant location.

2. The requisitioner will then identify the source in different plants.
3. After identifying the source, the requisitioner will then create a stock transfer requisition /
Indent in transaction code ME51N.
4. The requisitioner will then get the stock transfer requisition / Indent approved in
transaction code ME54N/ME55.
5. The stock transfer requisition will then be converted into a stock transfer order in
transaction code ME21N.
6. The stock transfer order will then be approved by the concerned authority.
7. The requisitioner will then provide the STO details to the section-holder of the issuing
plant location.
8. The section-holder will then issue the goods against the stock transport order in
transaction code MIGO with movement type 351.
9. A delivery challan will be generated via a custom program.
10. The goods will then arrive at the receiving plant location and a gate entry document will
be generated via a custom program.
11. The section-holder in the receiving location will create a goods receipt document against
the STO. This movement will happen with movement type 101.

BBP-300.1.02.03.04 Page 12 of 24 Project – SARTHI

Version 0.4
 Stock transfer within plant (2 step) 300.1.02.03.04

30
J E /A E /S D O

20
Creation of
10 Identification of
START Requirement source JE/AE/
Reservation by
JE/AE/SDO
SDO
(T-Code : MB21)
C o n c e rn ed E E

40
Reservation Approval
by Concerned EE
(custom program)

50
Transfer of
Is s uin g S t or a ge S e c tio n H o lde r

60 goods from
Gate Pass issuing location
by section Holder
(T-Code: MIGO)
YES
NO

70
Generate Gate 80
Pass by Section Submit Gate
Holder Pass Physically
(custom by section holder
program)
R e c e iv in g S t o ra ge S e c t io n

90
Stock receiving in
Stock Register receiving Storage
update location by section
H old e r

holder
(T-Code : MIGO)

STOP

BBP-300.1.02.03.04 Page 13 of 24 Project – SARTHI

Version 0.4
Stock transfer between store in different Plant: 300.1.02.03.04
R e q u is i ti o n e r / J E / S D O
- R e c e iv in g l o c a tio n

30
20
10 Creation of stock
Identification of
Start Requirement by transfer requisition /
source by JE/AE/
JE/AE/SDO Indent by JE/AE/SDO
SDO
(T-Code: ME51N)

40
Approval of stock
transfer requisition /
S E /C E

Indent by SE/CE
(T-Code: ME55/
ME54N)
S e c t io n - h o ld e r Is s u in g P la n t / lo c a t io n /A E /

80 70 60
Delivery Challan Good Issue Stock Transport
Gate Pass by section against the STO Order Provided
holder, physically by Section by Requisitioner /
signed by AE/SDO Holder Section Holder of
(Custom Program ) (T-Code : MIGO) Source Plant
SDO

Stock Register
update
S e c t io n - h o l d er R e c e iv i n g P la n t /

Stock Register
update
50
Conversion of stock
transfer requisition/
lo c a t i o n

90 Indent to Stock
100
Gate Entry against Transport Order by
Goods Receipt by
STO by section STOP Section Holder
section holder
holder (T-Code: ME21N)
(T-Code : MIGO)
(Custom Program)

BBP-300.1.02.03.04 Page 14 of 24 Project – SARTHI

Version 0.4
 2.2.4 Process Steps

2.2.4.1 Stock transfer between stores in the same plant:

Following are the details about the process steps mentioned in process flow:

No. Process Process Flow steps Roles & SAP Fiori App
Flow Responsibilities T-Code
1. Requirement The requirement for Requisitioner Non - SAP
(10) material in the receiving
location is raised
2. Identification The requisitioner will Requisitioner Non-SAP/ App:
of source identify the source of MMBE Overview
(20) supply in the same plant. Inventory
(The location having the Management
requirement will run the
SAP system report to Device:
Desktop,
determine the store with smartphone.
the required material.) Tablet

App ID:
F2769
3. Creation of a User will create a manual MB21 App: Create
manual reservation in the system JE/AE/SDO a reservation
reservation with movement type 313
Device:
(30) Desktop

App ID:
MB21
4. Reservation Reservation will be Concerned EE Custom
Approval manually approved via a program
(40) custom program
5. Transfer The section-holder at Section Holder MIGO Application:
posting at the issuing location will Goods issue
issuing generate a transfer
Device:
location posting material
Desktop
(50) document.
(Section holder of the App Id:
store having the MIGO_GI
material will then
transfer the material to
the store with the
requirement in the SAP
system).

BBP-300.1.02.03.04 Page 15 of 24 Project – SARTHI

Version 0.4
6. Gate pass If a gate pass is Section-holder Custom
required or required, a gate pass program
not? will be generated at the
(60)(70)(80) issuing location and
physically signed by
AE/SDO and will be
physically submitted to
the gate security.(Gate
Pass (if applicable) will
be created by the
section-holder at the
source location
(location from where
the material is being
sent) in the SAP system.
A print form will then
be generated which will
be manually signed by
the source location
(location from where
the material is being
sent) AE/SDO. (custom
development and
custom print form))
7. Place in Place in storage Section-holder MIGO Application:
storage at functionality in MIGO Transfer
receiving will happen at the stock – in
plant
location receiving location (The
(90) goods will then be Device:
received at the receiving Desktop,
store location (location smartphone,
with the material tablet
requirement) in the SAP
system by the receiving App Id:
F1061
location’s section-
holder).

BBP-300.1.02.03.04 Page 16 of 24 Project – SARTHI

Version 0.4
 2.2.4.2 Stock transfer between stores in different plants:

No. Process Process Flow steps Roles & SAP Fiori App
Flow Responsibilities T-Code
1. Requirement The requirement for Non - SAP
(10) material in the JE/AE/SDO
receiving location is
raised
2. Identification The requisitioner will JE/AE/SDO Non- App:
of source identify the source of SAP/MMBE Overview
(20) supply in a different Inventory
Management
plant
Device:
Desktop,
smartphone.
Tablet

App ID:
F2769
3. Creation of a The requisitioner will JE/AE/SDO ME51N Application:
stock create a stock Create PR
transfer transfer requisition
Device:
requisition / (The source location
Desktop,
Indent (location from where tablet
(30) the material will be
App Id:
sent from) ME51N
determination for
the required material
in the SAP system
report at the
receiving location
(the location where
the material is
required) will be
done by the
JE/AE/SDO).
4. Stock Approve the stock The reservation will be ME54N/ME55 Application:
transfer transfer requisition/ approved by: Release PR
requisition Indent SE ( Division to Division
Device:
approval (The reservation will within Circle) Desktop,
(40) be approved by: CE ( Division to Division tablet
SE ( Division to within Zone, different
Division within Circle) circle)

BBP-300.1.02.03.04 Page 17 of 24 Project – SARTHI

Version 0.4
 CE (Division to Details of the approver App Id:
Division within Zone, in case of division to ME54N
different circle) division in different
Details of the zone scenario to be
approver in case of shared by UPPTCL.
division to division in
The transfer of stock for
different zone Materials that are
scenario to be procured centrally will
shared by UPPTCL.) be approved by the
Design circle at Shakti
Bhawan. The material
list with the concerned
purchaser / buyer will
be provided by the
UPPTCL team.
5. Conversion The requisitioner will ME21N Application:
of stock generate a transfer Section Holder Create PO
transfer posting material
Device:
requisition to document.
Desktop,
stock (The stock transport tablet
transport order Division to
order (STO) Division will be App Id:
(50) ME21N
created in the SAP
system by the
Section holder at
Receiving location
(location where the
material is required).
6. Stock Stock Transport Requisitioner/Section- Non – SAP
Transport Order provided to the holder (issuing location /
Order issuing plant by the Receiving Location)
provided to receiving plant
issuing plant
by receiving
plant
(70)
7. Goods Issue The section-holder at Section-holder (issuing MIGO Application:
at issuing the issuing location location) Goods issue
location will issue the goods
Device:
(80) against the STO
Desktop

App Id:
MIGO_GI

BBP-300.1.02.03.04 Page 18 of 24 Project – SARTHI

Version 0.4
8. Generation The section-holder Section-holder (issuing Custom
of delivery will generate a location) program
challan delivery challan
(90) E-way Bill

9. Gate pass If a gate pass is Section-holder (issuing Custom

required or required, a gate pass location) program
not? will be generated at
(90) the issuing location
and physically signed Physically signed by
by AE/SDO and will AE/SDO
be physically
submitted to the gate
security.
(Gate Pass (if
applicable) will be
created by the
section-holder at the
source location
(location where the
material will be sent
from) in the SAP
system. A print form
will then be
generated which will
be manually signed
by the source
location’s (location
where the material
will be sent from)
AE/SDO. (custom
development and
custom print form).
10. Gate entry A gate entry will be Section-holder Custom
at receiving generated at the (receiving location) program
location receiving location
(100) with reference to the
STO
11. Goods The section-holder at Section-holder MIGO Application:
receipt at the receiving location (receiving location) Goods
receiving will post a goods receipt
location receipt entry with
Device:
(110) Desktop,

BBP-300.1.02.03.04 Page 19 of 24 Project – SARTHI

Version 0.4
 reference to the smartphone,
STO. tablet
(The goods will then
App Id:
be received at the F0843
receiving store
location (location
where the material is
required) in the SAP
system by the
receiving location’s
(location where the
material is required)
section-holder).

Note - Actual transaction code may be different from mentioned above.

In case of inter-division transfer, approval for issuing material from the supplying plant will be
taken by the receiving location over FLM and DMS attachment for the same will be made in the
STO.

Awaiting DoP from the business team and the approval strategy is SAP system will be mapped
once we receive the final DoP from UPPTCL team.

2.2.5 Gap Analysis

GAP Analysis

No. Object Number Description (if reuse RICEFW – Object Organization (All or
(RICEFW item, include high-level Type (RICEFW) mention specific
Tracker) changes) name)
1 MM-FR-010 Stock Transfer order Print Form UPPTCL

2.2.6 Business Process Variations

Process Variations
Please provide information on known variations to the standard business process. Specify the
variation description, e.g. Standard process may branch out to two different sub-processes

BBP-300.1.02.03.04 Page 20 of 24 Project – SARTHI

Version 0.4
 depending on the satisfaction of criteria. Ensure that there is a cross-reference to the to-be
process step(s).
No. Variation Description Conditions Organization
Governing Variation
1. NA NA UPPTCL

2.2.7 Cross Functions Integration Requirements

Cross Function Integration Requirements

Please provide information on process steps which has an impact on other functions e.g. a
sub-process in procurement and stores may have an impact on Finance due to auto-posting of
accounting transactions
Process Step Integration Aspects Other processes
impacted
Purchase Requisition At the time of Purchase requisition PS
Creation creation budget will be consumed from
WBS element ( For CapEx Budget)
Purchase Requisition At the time of Purchase requisition FICO
Creation creation budget will be consumed from
Funds management (For OpEx Budget)
Goods Issue at issuing Accounting document FICO
location
Document Attachment in The Technical Specification sheet, SoR, DMS / FLM
Purchase Requisition cost estimation sheets and clearance
document from other departments like
NHAI, Forest, railways etc. will be attached
in Purchase requisition

3. Assumptions and Dependencies

Key Assumptions
Document key assumptions and dependencies related to the business process
No. Assumption Description
1. Finance Related configurations
2. MM related configurations.
3. DMS related configurations.
4. Master data should be created in System ( Material master, service master, Vendor master)

5. GL masters should be created in system.

7. Budget should be available / approved in system for initiating purchase.

4. Organizations/Entities Impacted
Organizations/Entities Impacted
UPPTCL Uttar Pradesh Power Transmission Corporation Limited

BBP-300.1.02.03.04 Page 21 of 24 Project – SARTHI

Version 0.4
5. Existing IT Systems and Interface Requirements
Existing IT Systems and Interface Requirements
Please provide information related to existing IT applications or
systems currently in use and provide the necessary details related to
the usage of the application and provide high-level interface
requirements, if applicable
S.No. IT System Usage Interface Requirements
1. No legacy IT system NA NA
exists

6. High-Level Data Migration / Cut Over Requirements

High-Level Data Considerations
Document conversion considerations corresponding to the business process. Specify the
priority (M = Mandatory, O = Optional) required. Please specify both Master and Transaction
data considerations.
No. Description Priority
1 NA

High-Level Cut-Over / Deployment Considerations

Document any Cut-over considerations (particularly dependencies with Third-party systems)
corresponding to the business process. Specify the action required.
No. Description Action Required
1. NA NA

7. Decision Points for Operations Committee

Decision Points referred to open points that need discussion with Operations Committee or
Steering Committee for closure
No. Description Action Required
1. NA NA

8. SAP Standard Reports

SAP Standard Reports
SAP Standard reports are the reports which are readily available as part of SAP offering and do
not involve additional customization. A customized report is captured as part of the GAP
Analysis requirement section
No. Report Name Transaction Code Description/Purpose
1. Purchase document by ME21N This report generates a list of purchase orders
number (STO) by document numbers.
2. Stock in transit MB5T This report generates a list of materials in
transit for the STO.
3. Stock Overview MMBE This transaction is for stock overview for a
material
4. Material Document List MB51 This report generates a list of material
documents.

BBP-300.1.02.03.04 Page 22 of 24 Project – SARTHI

Version 0.4
5. Stock in warehouse MB52 This is the list of stock of materials at the
plant/storage location level.

9. Change Management and Business Impact Assessment

Highlight Business Impact of Changes from Current Practices
Please provide a high-level summary (or list of) current practices related to this process.
Highlight/focus on practices that are no longer followed or changed because of the To-Be
process. The document identified impacts to the business. Specify impact category (OG =
Organization), the level of impact (H = High, M = Medium, L = Low), Process Change from
current practice (Deleted / Changed / Added)
No. Description Impact Level Deleted / Changed / Added
1 For stock transfers (inter- H Changed
division) as well the indent
must be created by the
Requester in the SAP system
2 The indent must approve by H Changed
the Source division in the SAP
system
3 A purchase order must be H Added
created in the SAP system
against the inter-division indent
4 While receiving the material at H Added
the target location, the Waybill
number will also be stored in
the SAP system by user input
5 IN the case of Intra division H Added
(one subdivision to another
within the same division)
transfers as well the request
must be approved by the
source subdivision
6 The print form of delivery H Changed
challan will be taken out from
the SAP system

10. FRS Mapping

Details of the Functional Requirement specification points mapped in the BBP document.
S.No. FRS ID FRS Description Status
1 PSM/F/SM/IST/001 Ability to support physical movement of Standard
stock between stores i.e. inter-store
transfers
2 PSM/F/SM/IST/002 Ability to record order for inter-store Standard
transfer by pre-configured authorized
entity in the system

BBP-300.1.02.03.04 Page 23 of 24 Project – SARTHI

Version 0.4
Details of the Functional Requirement specification points mapped in the BBP document.
S.No. FRS ID FRS Description Status
3 PSM/F/SM/IST/003 Ability to generate material issue request Standard
based on order for inter-store transfer from
the material requesting store to the
material issuing store

4 PSM/F/SM/IST/004 Availability of configurable approval Standard

workflow for material requisition request
for inter-store transfer
5 PSM/F/SM/IST/005 Ability to modify material requisition Standard
request based on approver update

6 PSM/F/SM/IST/011 Availability of the Rate Contracts for Inter Standard

Store Transfer and rationalize the linkage
through ATC, ATD etc. documents to
'Finance & Accounts Module'

7 FA/F/GL/MSAR/005 Ability to reflect the Goods in transit Standard

11. Addition Details

N/A

BBP-300.1.02.03.04 Page 24 of 24 Project – SARTHI

Version 0.4