You are on page 1of 1

TECHNICAL REQUIREMENTS FOR DMS

Sr. No.Requirement

1
2
3
4

10

SAP DMS
Implementation
and
configuration
Server and
Storage Sizing

Description
SAP DMS Implementation and
configuration along with easy DMS are in
the scope of vendor.

Vendor
Confirmati
on YES/NO Vendor Comments

Yes

Vendor has to provide the Server and


Storage sizing for 5 years

SAP DMS
Installation of SAP DMS on HINCOL HP
Installation on
UNIX Server are in the scope of vendor
HP Unix Platform
All documents uploaded from SAP ECC
Content Server
should get stored only in the Content
Server
Operating
All work of Operating System, SAP
System, SAP
Application, Basis and ABAP related to DMS
Application,
Installation/configiration are in the scope
Basis and ABAP
of vendor.
Activities
Vendor has to download all the required
Software
software/media from SAP Support Portal
Download from
which is required for DMS
SAP
Implementation/configuration
Any Support Pack and SAP Note required
for DMS implementation/configuration and
any time during the
SAP Support
implemantion/confiuration period needs to
Pack , SAP Note,
be applied by the vendor. Support Pack
and SAP Note related to DMS requirement
are in the scope of vendor.
Number of DMS System to be Installed.
Number of DMS
1. Development
Instance
2. Production
Number of DMS System to be linked with
Number of DMS
ECC
Instance to be
1. Development
linked with ECC
2. Production

Yes
Yes

Yes

Assuming BASIS & ABAP is in scope


of Diligent

Yes

Assuming BASIS & ABAP is in scope of Diligent

Yes

Assuming BASIS & ABAP is in scope of Diligent

Yes

Yes

1.Asset Master AS02 Configuration to make the provision to upload


(ANLA)
document in change mode in content server and to
2.Equipment Master view the same in display mode for all the mentioned
IE02 (EQUI)
T- codes are in the scope of vendor.
3.Customer Master
XD02 (KNA1)
4.Vendor Master
XK02 (LFA1)
5.Material Master
MM02 (MARA
MARC)
6.Purchase Order
ME22N
7.Create Notification
QM02 (QMEL)
8.Purchase
Requisition ME52N
9.Inspection
Methods QS32
10.BOM- CS02(STKO)
11.Sales Order VA02
(VBAP)

Yes

11

12

13

14

15

16

17

18
19

1.MIGO - Create
Mode
2.FB01 /FB50L
Create and Change
Mode
3.MIRO / FB60
Create Mode
4.FB75 Credit note
Create and Change
Mode
5.ME51N Create
Mode

Enhancement to be done to make the provision to


upload document in content server in the mode
specified and to view the same in display mode for all
the mentioned t codes are in the scope of vendor.

Yes

User should be able to upload and view the uploaded


Documents in the
documents in content server as per their authorization
DMS will have the
of ECC are in the scope of vendor.
authorizations of the
SAP object it is
Yes
attached with.

FILE NOTE
WORKFLOW: A
separate customized
process to be
developed for
creation of the File
Note. This file note
will route based on
the originator(user)
and amount
specified in this file
note (the amounts
should be entered in
a separate filed).

Three separate
document types to
be created for
Knowledge
Repository.

1. Provision to attached multiple documents in the file


note to be provided.
2. Provision to attached the file note document in the
LPR-ME51N and ME52N
3. Before configuring the same Vendor has to provide
complete document
and detail understanding to HINCOL about the
configuration and the actual configuration to be done
based on the mutual discussion between HINCOL
and vendor

Need More clarity


These documents will be used for knowledge
repository and will be directly
created and uploaded in the content server through
CV01N
Access to these documents should be thorugh
controled authorization

Yes
The DMS requires configuration changes in
ECC EHP7 however the vendor has to
ensure that the existing functionality
should work the same way even after DMS
configuration. The Vendor has to do the
necessary testing using SAP Tools or any
Yes
other tool to ensure the same.
Vendor has to take the backup of both
devlopment and production system of DMS
and ECC servers peridoncally during the
Backup and
period of DMS installation/configuration
Restoration of ECC
and incase if the backup needs to be
and DMS
restored it has to be done by the vendor.
All backup and restoration are in the scope
Yes
of vendor.
Vendor has to ensure that their is business
Business
continuity during DMS
Continuity
implementation/configuration.
Yes
Minimum Down There should be minimum down time when
Yes
Time
we GO LIVE with DMS.
Existing
Functionality of
ECC

20

Downtime

21

System
Prerequiste

22

Implementation
Methodolgy

23
Offisite

Planned downtime to be provided by the


vendor. Vendor may review the infrastructure
to provide realistic downtime.

Yes

The vendor has to provide the implementation


methodology

Yes

System Prerequiste like RAM, Mount Points,


media etc needs to be provided by the
vendor
Vendor can do all the work from offsite
from their office, vendor has to visit
HINCOL ERP center for the meetings and
the cost for the same have to be born by
the vendor.

24

Internal
Connectivity
between the
systems

Transport Route and all other internal RFC


connections to be working as it is are in the
scope of vendor.

25

External
Connectivity

Connectivity to other systems such as BI, PI to


be working as it is are in the scope of vendor.

26

System Testing
Content Server
and Fine Tunning
after Upgrade

Load Testing, Performance Testing, fine tunning


of database, application, content server and os
parameters are in the scope of work of vendor Yes

27

Functional Testing will be done by HINCOL, the


vendor has to resolve all the issue reported by
Functional Testing the HINCOL Team.

28

Documentation

Deliverables:

29

30

ABAP Development required

User should be able to upload any number of


documents for the above t codes even for the t codes
No capping on the
where enhanement is done and for the t codes where
number of
documents uploads, the function is already avaliable are in the scope of
users should be able vendor.
to attached N
number of
documents to any
sap object.

Post Go Live
Support

Installation and Configuration Documentation


of DMS needs to be provided by the vendor.

Making and submititng the Installation


Document that should consists of all
installation steps and parameters details
and content server details are in the scope
1.Functional
of vendor. Knowledge Transfer :- Vendor
have to provide the document and a 23days training session in HINCOL Turbhe
Office to do the knowledge transfer of all
the functional configuration settings done
during DMS configuration.
2.Technical Knowledge Transfer :- Vendor
have to provide the document and a 2-3
days training session in HINCOL Turbhe
Office to do the knowledge transfer of all
the technical installation settings done
during DMS configuration.
After go live support for 15 days

Yes

DMS config. Will not effect any other


SAP module functioning.

Assuming BASIS is in scope of Diligent

Assuming BASIS & ABAP & Interface


is in scope of Diligent

Assuming BASIS is in scope of Diligent

Yes
Yes

Config document will be


responsibility of Diligent