Académique Documents
Professionnel Documents
Culture Documents
SCM Reporting
SCM Reimagin
DRAFT Require
Dec-19
Requirements
agined
6 Spend based on customer groups:- Integration between SFDC & SAP for
customer data
1. Fetching of customer grps from SFDC to SAP & reporting thereon.
2. Ability to track the opportunity ID in SFDC till the PO in SAP and any
addtitional cost that would be linked with the same.
16 There should be seamless integration between different systems like SAP, Optimus, Ariba, Cramer, M6, Data Warehouse
17 Ability to automatically retrieve data from all systems into a Data Warehouse
18 Ability to process data in the Data Warehouse using ETL tools
19 Ability to feed in performance metrics into the system and to create automated workflows to populate the metrics/indic
20 Ability to display KPIs on pre-configured PowerBI dashboards
21 Ability to create different dashboards based on functions, heirarchy levels, or any other dimensions
22 Ability to restrict access to dashboards of other users
23 Ability to provide access to Data Warehouse to users as per DoA
24 Ability to create different dashboard views for different time durations - dashboards for viewing Daily, Weekly, Monthly,
25 Ability to add slicers to the KPIs and dashboards
26 Ability to modify/add KPIs in the system
27 Ability to add/modify SLAs for different KPIs
28 Customer related purchase: Ability to link transactions / data from upstream and downstream systems e.g SFDC Opport
29 Ability to integrate various SAP tables to analyze an entire transaction from Source to Procure to Pay (S2P2P). Ariba sour
30 Compliance and Non-compliance report to various Company's policy such as SCM policy, Travel policy, P-Card policy etc.
31 Ability to track inventory via a serial number and by customer, equiptment location, customer address, Customer local c
32 Ability to link external market intelligence data source with internal data warehouse.
33 Ability to analyze unit price (customer) and unit cost (vendor) analysis by a transaction and contribution profit margin.
34 Ability to overlay APIs to update the vendor's catalogue rate on a defined frequency, and monitor the rate change over a
35 Ability to monitor vendor performance management through a dashboard by various cuts / slicers
36 "Product Classification" and "Emergency Purchase" fields to be captured in PR PO process
37 Green category vendors, vendor diversity to be captured in Vendor on-boarding process
38 The solution should be able to handle multi currencies such as USD, AED, SAR, QAR, OMR and others. The reports shoul
39 The solution should be able to generate both PO and Non-PO report, linked with vendor payments and invoicing inform
40 The solution should be able to develop all existing custom PO reports: - PO report containing OLA consumption informa
41 The solution will provide end to end correlation of material/ services from catalogue to SAP masters, PO etc., for easier
42 Capturing time taken for sub-processes within any process, and represent TaTs in user defined bucket ranges
43 The solution will provide the ability to track and trace compliance measures and managing contract life management
45 The solution will provide the ability to link category information with complete contract, PO, vendor type, GL account , i
46 Maverick Spend details (Maverick spend type) should be captured in the PO process
47 Revenue related reports to monitor and compare SCM costs relative to revenue numbers
48 Report for average payment terms used, average credit period used for spend via PO & Non PO
Source System Dimensio Building block Leading/ Legal Audience/Ro
ns (Procure,Logistic Lagging le
( Refer s..etc) (Business
sample Analyst,
dimensio Business
Ariba & SAP n tab) Process
Owner, Line
function,Seni
or Manager
etc)
Procurement
Optimus & SAP
Procurement
Catalogue+Ariba+SAP
Procurement
Procurement
SAP
Finance/AOP
SFDC & SAP
SAP
SAP
SAP
SAP
SAP
SAP
SAP
SAP
Ariba & SAP
mer, M6, Data Warehouse (Tera Data / Galaxy), SFDC, Provisioning systems, etc
g Daily, Weekly, Monthly, Quarterly, Semi-Annually, Annually etc. (for different users)
systems e.g SFDC Opportunity ID and PR/PO should be linked, to track end-to-end customer to vendor transactions. Relationship between
to Pay (S2P2P). Ariba sourcing report, PR/PO report, GRN/SRN report, Invoice Report and Payment transaction report.
l policy, P-Card policy etc.,
address, Customer local contact etc.,
ntribution profit margin.
tor the rate change over a period across the catalogue.
others. The reports should provide single currency conversion into USD and INR for all currencies using the applicable Fx rate . Solution sho
ents and invoicing information
OLA consumption information, PO amendment reports, Open PO reports, PO report with all GST related fields
asters, PO etc., for easier reporting and tracking
bucket ranges
ntract life management
endor type, GL account , inventory etc.
Intention of the requirement/ if as per procurement Report to display
policy
To track end to end transaction via Optimus w.r.t To track end to end transaction via Optimus w.r.t
spend, payment & timelines. spend, payment & timelines
To minimise manual extraction of multiple reports Report will help to integrate spend, PO volume,
for different entities and ensure consolidation of various cuts by dept, users, buyers etc across these
spend, vendor payments & timelines. entities (as buyers/ PO releasers are common).
To track end to end transaction to help identify net To track end to end transaction to help identify net
revenue or loss against each transaction against a revenue or loss against each transaction against a
customer request. customer request.
A cash flow statement is a financial statement that A cash flow statement is a financial statement that
summarizes the amount of cash and cash summarizes the amount of cash and cash
equivalents entering and leaving a company. equivalents entering and leaving a company.
To track improvements in EBIT, ROC. To track improvements in EBIT, ROC.
Currently FAGLL03 doesn’t contain invoice # field Reporting of Non PO spend by teams, cost centre
which needs to be clubbed in one report only. owners etc.
Enable Service coding just like material codes for Monitor and track spend by OLA, its consumption,
better reporting and enable OLA creation therefrom. etc
To track spend on the basis of TCL products. This will To track spend on the basis of TCL products. This will
provide management a view product wise/ LOB wise. provide management a view product wise/ LOB wise.
As per Procurement Policy As per Procurement Policy
As per Procurement Policy As per Procurement Policy
omer to vendor transactions. Relationship between SFDC Opportunity ID and PR/PO: One to One, One to Many and Many to One.
nd Payment transaction report.
currencies using the applicable Fx rate . Solution should also help capture the currency exchange at the time of transaction.
Adhoc /Monthly
2 System Operational / Quarterly /
Annually
Adhoc /Monthly
2 System Operational / Quarterly /
Annually
Adhoc /Monthly
2 System Operational / Quarterly /
Annually
Adhoc /Monthly
2 System Strategic / Quarterly /
Annually
Adhoc /Monthly
2 System Operational / Quarterly /
Annually
As per calendar
2 System Operational SAP
run date
Key data elements required in the report
All Data Fields including Contractual ETC, Actual ETC, Vendor Details
Segment, Family, Class, Commodity, Inventory levels, Days of inventory, Inventory ageing, Type of
inventory - project stock / common stock, Lead time, Reorder levels
SAP report name, Column header, %filling in mandatory fields, adherence to data quality rules and
data dictionary (for attribute format, length, list of values, special character presence etc.)
Invoice#, Vendor Code, Date of receipt, Amount, Status – (Pending OCR, OCR, Pending queue
allocation), OCR Date, Queue allocation date
Invoice number, Invoice due date, Vendor, Business User, Currency, Amount, Entity, Mode of
Payment, House Bank, BPV Transfer Method
Invoice number, Invoice due date, Vendor, Business User, Currency, Amount, Entity, Payment
Processing Status (Passed/Failed), Payment reference no
Standard (S)/
Custom Report Comments
(C)?
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
See Comments
Tab: List of KPIs
Dimensions
Source
S # PIs Details (Derivation/Formula) Report Name1 Report Name2 ( Refer sample
System
dimension tab)
Purchasing1, MDM
TAT for material / service Team Personnel
# of days taken to service material/service Material/ Service
12 master record blocking Manual
master blocking Master Report
request service
Median contracting cycle # days taken from Contract Request Form Ariba Analytical Purchasing1,
53 ARIBA
time (CRF) to Contract Sign-off Report Purchasing2, Vendor1
Purchasing1,
Contractual spend as % Actual spend through contracts / Amount of Ariba Analytical Purchasing2
54 ARIBA
of total SCM PO spend SCM PO Spend Report
Purchasing1,
Date of final deal approval in Ariba - Date of Purchasing2, Vendor1,
55 Final Deal approval TAT ARIBA Ariba Sourcing Report Procurement Value
final deal approval raised
(USD)
Purchasing1,
(# of instances where (Date of final deal Purchasing2, Vendor1,
Adherence to
approval in Ariba - Date of final deal approval Ariba Analytical Procurement Value
56 Turnaround time of final ARIBA
raised) is within the SLA )/ Total no. of Report (USD)
deal approval
sourcing requests raised in a given period
Purchasing1,
Cost savings achieved Purchasing2, Vendor1
Cost savings from PO Line Item Data / SCM
61 as % of managed spend SAP PO Line Item Data
PO spend
(incl. cost avoidance)
Purchasing1, Logistics,
International freight Cost of inbound and outbound transportation PO Line Item Capex/Opex
92 SAP, ManualFreight Costs Report
costs of goods and materials (outside India) Data
Warehouse,
Reduction of Non- Actual Reduction to be measured against Purchasing1, Entity,
125 SAP Zstockageing
Moving Inventory last 31st Mar Non moving Inventory value Vendor
Warehouse,
Reduction of Slow- Actual Reduction to be measured against Purchasing1, Entity,
126 SAP Zstockageing
Moving Inventory last 31st Mar Slow moving Inventory value Vendor
Value of non-moving Warehouse,
Value of non-moving stock / value of total Purchasing1, Vendor
127 inventory as % of total SAP Zstockageing
inventory
inventory
Value of slow-moving Warehouse,
Value of slow-moving stock / value of total Purchasing1, Vendor
128 inventory as % of total SAP Zstockageing
inventory
inventory
Opening non-moving Warehouse,
129 #Stock units categorized as non-moving SAP Zstockageing
stock count Purchasing1, Vendor
Opening non-moving INR value of Stock units categorized as non- Warehouse,
130 SAP Zstockageing
stock value moving Purchasing1, Vendor
Opening slow-moving Warehouse,
131 #Stock units categorized as slow-moving SAP Zstockageing
stock count Purchasing1, Vendor
Opening slow-moving INR value of Stock units categorized as Warehouse,
132 SAP Zstockageing
stock value slow-moving Purchasing1, Vendor
Warehouse, Region,
Global Assets Transfer Entity, Function,
Time taken to transfer the materials from the Global Asset Transfer
136 TAT - End to End SAP CC_Owner, GMC
date of request Report
Delivery Management member
Logistics costs as % of Warehouse, Project
137 Logistics cost/ Total project cost SAP TBD
project cost Manager
% of SCN created by Total number of SCNs submitted by Project site, Project
138 ARIBA TBD
vendor vendors / Total number of SCNs Manager, Vendor1
Warehouse/Project site,
#GRNs completed within TAT/ Total # of Vendor, Purchasing1
139 Adherence to GRN TAT SAP ZMMGRNSRN
GRNs
Legend
Manual reports
Enablers
Enablers
Enablers
Enablers
Enablers
Enablers
Enablers
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
Sourcing
ASP
ASP
ASP
ASP
ASP
ASP
ASP
ASP
ASP
ASP
COP
COP
COP
COP
COP
COP
COP
COP
COP
COP
COP
COP
COP
COP
COP
COP
Logistics
Strategy and Planning
Segment
Family
Class
sub-class Purchasing1
Procurement Department
Procurement Vertical
Company Code
Buyer Name
Sponsor or CC_Department
CC_Owner
Purchasing2
CAPEX/Opex
G/L acct
Project Manager
Corp.Group
Corp.Group_Name
OEM Name Vendor1
Vendor No
Vendor Name
Warehouse
Entity
Logistics
Logistics
India / Int'l delivery
Delivery location (Warehouse/pr
PO Creator
MDM Team Personnel Operations
QR Team Personnel
Source-To-Procure-to
Ref.
IT Business Requirement Priority Vendor Response Module Name
No.
3.1 Strategic Sourcing
3.1.1 Analyze spend
The solution will provide the ability to
map, aggregate, report and analyses total S/4HANA Embedded Analytics
Mandatory Customisation
spend data. Dimensions of information SAP BW/4HANA system
are:
S/4HANA Embedded Analytics
- per product type / product group Mandatory Standard functionality
SAP BW/4HANA system
S/4HANA Embedded Analytics
- per product Mandatory Standard functionality
SAP BW/4HANA system
- usage (internal use or customer success
S/4HANA Embedded Analytics
based with the latter trackable by Customisation
SAP BW/4HANA system
customer name)
- possibility to link and cross all S/4HANA Embedded Analytics
Mandatory Customisation
dimensions mentioned above SAP BW/4HANA system
The solutions should be able to generate
both PO and Non-PO report, linked with
Mandatory Customisation S/4HANA - MM
vendor payments and invoicing
information
The solutions should be able to track PO
changes due to migration/merger of TC Mandatory Standard functionality S/4HANA - MM - Purchasing
units, etc.
3.1.2 Procurement planning
The solution will provide the ability to
Mandatory Customisation S/4HANA - FP&A - BP&C
develop procurement plans based on
SAP BW/4HANA system
- historical spend analysis by category Mandatory Customisation
S/4HANA - FP&A - BP&C
- driver based plans for direct material
categories (access, backhaul, CPE) Mandatory Customisation S/4HANA - FP&A - BP&C
based on pipeline and demand plans
- business division and cost center/
internal order / profit centre plans for
Mandatory Customisation S/4HANA - FP&A - BP&C
specific procurement categories like
services
-solution to have ability to adjust plans
based on short term plan change drivers Mandatory Customisation S/4HANA - FP&A - BP&C
from cross department inputs.
- system should factor in demand and
supply planning variables - Lead time, S/4HANA - FP&A - BP&C,
Mandatory Customisation
demand changes, ROP, ROQ and Stock S/4HANA - MM
levels at various locations
S/4HANA - MM - Purchasing,
Ability to form document repository for SAP DMS,
Mandatory Standard functionality
legal documents SAP PO,
MS Share Point Online
Ability to view audit trail of all the workflow S/4HANA - MM - Purchasing,
Mandatory Standard functionality
steps and user actions S/4HANA - Workflow
3.8 Payments
Ability to have a Cheque Master with
Mandatory Customisation S/4 HANA FI-AP/GL
tracking of cheque numbers
Ability to track Cheques bounced /
Mandatory Standard functionality S/4 HANA FI-AP/GL
represented account
Ability to allow processing of manual
cheques in case auto cheque processing Mandatory Standard functionality S/4 HANA FI-AP/GL
fails
3.9 Manage payables
Ability to provide reconciliation of
Mandatory Standard functionality S/4 HANA FI-AP/GL
subsidiary ledger to G/L
Customisation S/4 HANA FI-AP/GL
Ability to view total vendor spend across
Mandatory S/4HANA Embedded Analytics
legal entities and locations
SAP BW/4HANA system
Ability to support A/P aging report on
outstanding items , due date , invoice
Mandatory Standard functionality S/4 HANA FI-AP/GL
date, project based procurement vis-à-vis
non projects & supplier.
Ability to facilitate invoice inquiry
supporting search by amount, invoice
Mandatory Standard functionality S/4 HANA FI-AP/GL
number, vendor number, vendor name
etc.
Ability to create provision by IDs, accruals
by IDs/ suppliers, and manage their Mandatory Standard functionality S/4 HANA FI-AP/GL
closing
Source-To-Procure-to
Ref.
IT Business Requirement Priority Vendor Response Module Name
No.
Ability to provide creditors report showing
balances for:
- All creditors
- User defined range of creditors
Mandatory Standard functionality S/4 HANA FI-AP/GL
- Account balances aged over 1 month, 2
months, 3 months etc.
- Aged by transaction date
- Aged by due date
Ability of system to generate report on
year-to-date payments made to the Mandatory Standard functionality S/4 HANA FI-AP/GL
vendor
S/4HANA - MM
S/4HANA Finance
Ability to check if suppliers Sale Input is
SAP ASP Add-on Solution for GST
matching with our Purchase Input to claim Mandatory Standard functionality
(SAP DCS - Digital Compliance
Income Tax credit
Solution) & Third Party GSP
Services
S/4HANA - MM
The solution should be integrated with
Standard functionality SAP Ariba
SAP S4HANA
SAP PO
As confirmed by Tata Communications, Ariba Spend analysis has not been considered as part of engagement
scope.
A mix of standard SAP S/4HANA P2P standard reporting alongside custom reports will be leveraged to meet the
requirements
TCS recommends that in order to have flexibility and drive high level insights, SAP S/4HANA - optimized Business
Planning (add-on over SAP S/4HANA) can be leveraged.
Some of planning requirements for select items can be managed using reorder level planning
Historical data analysis (data not available in SAP S/4HANA system) can be made by developing the desired analytical
reporting in BW system. SAP S/4HANA system will not have historical data before system goes live.
SAP budgetary controls systems (fund management) can be used for monitoring the budgets and establishing
controls. (E.g., No PO can be raised by department if budget set of department is exceeded) for Opex. Internal Order /
WBS elements can be used for Capex.
TCS recommends that in order to have flexibility and drive high level insights, SAP S/4HANA - optimized Business
Planning (add-on over SAP S/4HANA) can be leveraged.
Procure-to-Pay
Some of planning requirements for select items can be managed using reorder level planning
To be filled by SI bidders
Historical data analysis (data not available in SAP S/4HANA system) can be made by developing the desired analytical
reporting in BW system. SAP S/4HANA system will not Remarks
have historical data before system goes live.
SAP budgetary controls systems (fund management) can be used for monitoring the budgets and establishing
controls. (E.g., No PO can be raised by department if budget set of department is exceeded) for Opex. Internal Order /
WBS elements can be used for Capex.
Any long term planning aspects can be managed using SAP BP component while analytics requirements can be
managed in existing SAP BW/4HANA system
SAP Ariba Catalog Management solution (also called as Ariba Procurement Content) integrated with SAP S/4HANA
Procurement will be enabled to meet employees’ self-purchasing requirements for goods and services.
The solution’s punch-out capability will drive improved user experience in terms of providing consumer like shopping
experience alongside driving greater contract compliance
Purchasing team will negotiate and mutually agree with suppliers for the select categories / products and their prices.
Catalogs can be structured based on business needs (E.g., Global / Local catalogs).
The user can select from internal catalogs maintained or can punch-out to specific supplier sites
The solution will also provide for cross-catalog search functionality among punch-out suppliers bringing the relevant
details and prices at one place.
Ariba catalog management is available as part of Ariba Buying and Invoicing module.
P2P process for select purchasing categories as discussed and agreed during business blueprinting stage
will be enabled in Ariba Buying and Invoicing. For most of core categories, it will be enabled in SAP S/4HANA
only.
Procure-to-Pay
To be filled by SI bidders
Remarks
As understood from TC team, users will be entering in the changed business requirements in system.
SAP Ariba / SAP S/4HANA standard / custom reporting / Analytical reporting can be leveraged for desired insights.
The templates for TC specific needs will be configured to drive end-to end sourcing processes. Any additional
templates to meet region / category specific needs can be additionally configured. However any sourcing "results" is a
subjective parameter and the same to manually done.
The desired approval workflows in line with requirements will be configured in solution for tracking and transparency
needs.
Ariba network drives suppliers collaboration wherein suppliers can raise their queries for clarifications over Ariba
platform itself.
Customer Order Procurement: COP process will be enabled as part of holistic procurement solution wherein requests
from SFDC system can be ported to SAP S/4HANA procurement and therefrom to SAP Ariba sourcing solution for
required sourcing needs.
The suppliers can register themselves with basic mandatory information during sourcing process to participate in the
sourcing events.
PR and RFQ will be created in SAP S/4HANA system which will be converted into a SAP Ariba sourcing project
request in SAP Ariba (through integration over SAP process Orchestration)
SAP Ariba Contract Lifecycle management solution is recommended for managing the contracting process including
collaborative authoring and sign-off. Any standard clauses can be maintained in libraries for reuse.
Ariba payables (discount management) solution is suggested for driving dynamic discounting needs. Supplier / TC can
create the proposals and once agreed by other party, the payments can be released by TC to supplier net of additional
adhoc discounts
The sourcing offered.for Project Specific needs will be managed using SAP Ariba Sourcing module. Requirements
processes
need to be specified clearly (say in RFP document) and a sourcing project needs to be created to manage the RFx /
Note:- Implementation
Auction processes. of SAP Ariba Payables / Discount Management Solution is not part of TCS Scope.
From SAP Ariba perspective, the process will be managed in similar fashion as for other TC sourcing needs. The
project specific sourcing templates for will be configured to meet process specific needs.
Supplier data can be maintained in self-service mode by suppliers themselves using Ariba SIPM. Or, the data can be
maintained by TC manually in SAP S/4HANA Procurement (business partner).
At time of creation of PR and PO, the requirement can be assigned to a WBS element (project) to account for project
specific tracking and capitalization needs of material procured.
The operational project specific requirements viz project start, execution and closure will be managed using SAP
S/4HANA project systems.
The country specific mandatory compliance details viz GST number / PAN number in India, W9 / W8 form for USA can
be managed as a standard feature in SAP Ariba. The necessary approval workflows can be configured and suppliers
can be classified into different categories viz Approved, Preferred etc.
Further, SAP S/4HANA system and Ariba SIPM will be synchronized with each other. The supplier details can be
created / updated in SAP S/4HANA system also which in turn will automatically update the Ariba system too.
TCS recommends to use Ariba Commerce Automation Module (subset of Ariba Supply Chain Collaboration) for
automatic exchange of key purchasing documents between Supplier and Tata Communications (TC).
The supplier also needs to be available over Ariba platform for same as a pre-requisite. TC needn’t share the
documents viz PO, Invoice etc. over e-mail / fax with suppliers however the solution will set-up the mechanism to auto-
exchange the select key documents on both sides and thus saving on time and bandwidth of associates. E.g.,
Purchase Order, Supplier acknowledgement, GRN, Invoice, Payment Remittance etc.
Supplier can attach necessary supporting documents too as needed during the process (sourcing process /
registration process / purchasing process)
Ariba Commerce Automation only has been considered for implementation as part of TCS Scope. Ariba
Supply
Contract authoring, Chain Collaboration
negotiating moduleversion
iteration and contract has not been considered
changes and sign-offfor
canimplementation
be managed in Ariba Contract
lifecycle management. The operational execution of contract will be managed in SAP S/4HANA system. Contract
compliance will also be driven using Ariba Catalog management solution.
For select functions / items. Custom developments in SAP S/4HANA solution otherwise.
SAP S/4 HANA standard Roles and Authorizations will be used with object level authorization if required
Procure-to-Pay
To be filled by SI bidders
Remarks
S/4 HANA standard reports will give the TAT in number of days from invoice posted to payment, however for time
based TAT, issue resolution the same needs development.
Contract life cycle will be handled both in SAP Ariba and also in S/4HANA purchasing, however for some of the Track
and trace compliance measures might involve customization.
SAP S/4 HANA and SAP Ariba Standard Roles & Authorizations.
SAP S/4 HANA standard workflows are available, however SLA milestones, contract usage notifications needs
customization
SAP S/4HANA - LD calculations can be done in purchasing as standard which can be passed to Special G/L for
invoice with customization
TC can utilize the existing Microsoft Share point online (or SAP Open Text ECM) for documentation management
system and integrate the same with SAP S/4 HANA system. SAP DMS will be required to the extent of Meta Data
preparation in SAP, however document will get repositorized in MS Share Point Online.
SAP S/4 HANA standard LE Shipping can be used to do shipment planning and execution, however for tracking
necessary interfaces and additionally tech capabilities are required like GPS, RFID etc., which is not in scope.
Procure-to-Pay
To be filled by SI bidders
Remarks
Statisical Vendor Sampleing may not be possible however selection of vendor invices may be possible with
customization
TC can utilize the existing Microsoft Share point online (or SAP Open Text ECM) for documentation management
system and integrate the same with SAP S/4 HANA system. SAP DMS will be required to the extent of Meta Data
preparation in SAP, however document will get repositorized in MS Share Point Online.
SAP Standard
Cheque register will be maintained based on the cheque lots which track the cheque numbers.
Cheque bounced can be traced through reason code identified for this Purpose. Based on the cheques voided due to
bouncing, the same can be represented with automatic functionality
Manual cheques can be Processed as standard functionality in case auto cheque processing fails
Reconciliation account through automatic account determination maintained in the vendor master
Total spend across legal entities will be consolidated. To be arrived through customization.
Ageing analysis
Based on the account balance with the document types overall payments can be extracted
Standard ageing report functionality to provide ageing report . Since it is defined by the user, the same needs to be
customized
Standard Reports can be leveraged. Customization might be needed based on detailed requirements
Credits based on the document type can be generated as Invoice report for a particular time frame. No separate
register In case it is required the same needs to be customized.
Payment report can be generated based on document type for a particular time frame. No separate register In case it
is required the same needs to be customized.
The Payroll journal entries will flow into SAP S/4 HANA FICO module for GL wise Tracking and clearing after
generation of DME File
TCS recommend TC to utilize the existing Microsoft Share point online for documentation management system and
integrate the same with SAP S/4 HANA system. SAP DMS will be required to the extent of Meta Data preparation in
SAP, however document will get repositorized in MS Share Point Online.
Reports can be built for same. SAP Vendor Evaluation functionality or SAP Ariba Supplier performance solution can
also be used
Asset Master and Eqpt Master to be in synch, warranty information's to be stored in Eqpt Master which will help the
purchase and maintenance team with warranty life cycle
Procure-to-Pay
To be filled by SI bidders
Remarks
The necessary fields to be captured will be made mandatory in system E.g., GST Number, PAN number etc.
SAP S/HANA system is GST compliant. Standard / custom reports can be leveraged to provide reporting insights to
TC users based on business needs.
SAP S/4HANA system will provide for purchase data however a third party or SAP's ASP solution will be needed for
reconciling if TC's purchase input is in line with suppliers' sales inputs for income tax credit. Any discrepancies can be
alerted to supplier over mails. Detailed clarifications between the buyer and supplier to happen offline.
It's suggested that suppliers are enabled over Ariba network and flip TC's Purchase order to create Invoice. Key
advantages:
a. The supplier is flipping the PO into an invoice resulting into auto-population of relevant data and minimization of
data entry errors. Supplier can use the same invoice into his system with formatting changes either through download /
upload or through direct integration
b. Select data validation related business rules can be configured on Ariba network side preventing wrong invoices to
come to TC, get into processing queue and then getting stuck for data errors, coordination with vendors for
rectifications. It will save processing time and improve STP % too.
c. After GST implementation, every supplier is creating a system based invoice for him to submit the details into GSTN
portal. The recommended system will also improve upon the successful reconciliation %age between TC’s purchasing
system data and suppliers’ sales data.
SAP ASP Add-on Solution for GST (SAP DCS - Digital Compliance Solution) & Third Party GSP Services are
not considered as part of scope here
Procure-to-Pay
To be filled by SI bidders
Remarks
Existing portal provides for basic functionalities for vendor to see his PO, Invoice status. The same can be integrated
using SAP PO with SAP S/4HANA system.
Otherwise, TCS suggests to use SAP Ariba Supply chain collaboration (inc Commerce automation) for collaboration
over operational purchasing transactions. The Ariba solution has standard integration with SAP S/4HANA too.
A mix of standard and custom reports can be leveraged for required reporting insights. Analytical reports can be
created in SAP S/4HANA embedded analytics or in SAP BW/4HANA system.
The alerts will be customized based on needs. E.g., contract expiry, contract usage etc.
For documents storage (received as part of P2P compliance), the metadata of digital documents can be maintained in
SAP S/4HANA DMS while scanned document can be stored in TC's SharePoint content management solution.
Documents versioning can be maintained
Rebates / discounts can be managed as part of standard PO pricing procedures or can be customized. Dynamic
discounts to be managed using Ariba payables (discount mgmt.) solution.
Related to Invoice Processing. TCS suggests to use SAP VIM for invoice processing
Standard analytical reports can be used to assist for contextual decision making at time of invoice payments. Any
business rules around same will need to be customized
System provides for multi-currency capabilities allowing for transaction with suppliers across geographies in respective
currencies.
As port of invoice processing, SAP's partner solution OpenText Vendor Invoice management (VIM) is suggested. the
solution wk ill allow for creation of queues for invoice processing to be done by associates. Further, the reports can be
leveraged to analyze the same.
Any access control will be managed using Roles and responsibilities to allow for segregation of duties.
Vendor desk integration with system can be enabled using SAP PO. Further SAP Fiori will be used for undertaking role
wise transactions and approvals using laptops / desktops / mobile / tabs providing a better user experience.
Procure-to-Pay
To be filled by SI bidders
Remarks
Vendor / business partners master data will reside in SAP S/4HANA (or master data will flow from TC's MDM system to
SAP S/4HANA).
The necessary vendor master data will be sent to SFDC for business process activities there
Vendor can also create their profile as part of registration as well as update the same on Ariba Supplier Lifecycle
Performance. The same will be synchronized with SAP S/4HANA business partner master data.
The sub-set vendor can be managed using partner function. System provides for standard duplication checks however
rest can be customized.
Any additional data validation checks or rules can be built into SAP S/4HANA system. Any BDC can be created to
upload the vendor details with necessary controls into system based on needs
Vendor can be blocked too. System will not allow for any transactions with blocked vendors. Vendor account groups
can be created inline with TC's needs
System provides for multiple standard reports which can be leveraged for desired reporting needs too.
Any FAQs / policies and links can be displayed over Ariba network to suppliers. A link can be made available from TC's
website (supplier section).
Procure-to-Pay
To be filled by SI bidders
Remarks
KPI design and analytics will need customization efforts in BW system. Cascading up / drilling down ability is usually a
standard feature in analytical reporting.
The necessary data points to design and monitor the KPIs should be available in SAP systems or in other third party
systems as a prerequisite.
SAP S/4HANA based solution will be integrated with Tata Communication's selected Tax solution wherever feasible.
Liability can be arrived at only for tax transactions posted in SAP. No Global tax intelligence will be possible
Source-To-Procure-to
Ref.
IT Business Requirement Priority Vendor Response Module Name
No.
3.1 Strategic Sourcing
3.1.1 Analyze spend
The solution will provide the ability to
map, aggregate, report and analyses total S/4HANA Embedded Analytics
Mandatory Customisation
spend data. Dimensions of information SAP BW/4HANA system
are:
S/4HANA Embedded Analytics
- per product category Mandatory Standard functionality
SAP BW/4HANA system
S/4HANA Embedded Analytics
- per product commodity Mandatory Customisation
SAP BW/4HANA system
S/4HANA Embedded Analytics
- per product type / product group Mandatory Standard functionality
SAP BW/4HANA system
S/4HANA Embedded Analytics
- per product Mandatory Standard functionality
SAP BW/4HANA system
S/4HANA Embedded Analytics
- per region Mandatory Standard functionality
SAP BW/4HANA system
S/4HANA Embedded Analytics
- per network location Mandatory Customisation
SAP BW/4HANA system
- per cost centre / Internal Order / Profit S/4HANA Embedded Analytics
Mandatory Standard functionality
Centre SAP BW/4HANA system
S/4HANA Embedded Analytics
- per month/Quarter/Year Mandatory Standard functionality
SAP BW/4HANA system
S/4HANA Embedded Analytics
- per subsidiary, entity, department Mandatory Customisation
SAP BW/4HANA system
S/4HANA Embedded Analytics
- per supplier Mandatory Standard functionality
SAP BW/4HANA system
S/4HANA Embedded Analytics
- per supplier location Mandatory Customisation
SAP BW/4HANA system
S/4HANA Embedded Analytics
- buyer Mandatory Standard functionality
SAP BW/4HANA system
- usage (internal use or customer success
S/4HANA Embedded Analytics
based with the latter trackable by Customisation
SAP BW/4HANA system
customer name)
- spend under contract by central S/4HANA Embedded Analytics
Mandatory Customisation
procurement team SAP BW/4HANA system
- spend under contract where
procurement is managed by business, S/4HANA Embedded Analytics
Mandatory Customisation
where central procurement primarily SAP BW/4HANA system
facilitating it as a business partner
- possibility to link and cross all S/4HANA Embedded Analytics
Mandatory Customisation
dimensions mentioned above SAP BW/4HANA system
The solutions should be able to generate
both PO and Non-PO report, linked with
Mandatory Customisation S/4HANA - MM
vendor payments and invoicing
information
The solution should be able to develop all
Mandatory Customisation S/4HANA - MM - Purchasing
existing custom PO reports:
- PO report containing all custom fields Mandatory Customisation S/4HANA - MM - Purchasing
Source-To-Procure-to
Ref.
IT Business Requirement Priority Vendor Response Module Name
No.
- PO report containing OLA consumption
Mandatory Customisation S/4HANA - MM - Purchasing
information
- PO amendment reports Mandatory Standard functionality S/4HANA - MM - Purchasing
- Open PO reports Mandatory Standard functionality S/4HANA - MM - Purchasing
- PO report with all GST related fields Mandatory Customisation S/4HANA - MM - Purchasing
The solutions should be able to track PO
changes due to migration/merger of TC Mandatory Standard functionality S/4HANA - MM - Purchasing
units, etc.
3.1.2 Procurement planning
The solution will provide the ability to
Mandatory Customisation S/4HANA - FP&A - BP&C
develop procurement plans based on
SAP BW/4HANA system
- historical spend analysis by category Mandatory Customisation
S/4HANA - FP&A - BP&C
- driver based plans for direct material
categories (access, backhaul, CPE) Mandatory Customisation S/4HANA - FP&A - BP&C
based on pipeline and demand plans
- business division and cost center/
internal order / profit centre plans for
Mandatory Customisation S/4HANA - FP&A - BP&C
specific procurement categories like
services
-solution to have ability to adjust plans
based on short term plan change drivers Mandatory Customisation S/4HANA - FP&A - BP&C
from cross department inputs.
- system should factor in demand and
supply planning variables - Lead time, S/4HANA - FP&A - BP&C,
Mandatory Customisation
demand changes, ROP, ROQ and Stock S/4HANA - MM
levels at various locations
S/4HANA - MM - Purchasing
The solution will provide quality check S/4HANA - MMIM - Quality
Good to haveStandard functionality
reports. Management,
S/4HANA - MMIM - Goods Receipt
S/4HANA - MM - Purchasing,
a. Report on volumes, conditions, and
SAP Ariba Contract Management,
quantity vs. contract agreement on item Mandatory Customisation
S/4HANA - Embedded Analtyics,
level
BW/4HANA
S/4HANA - MM - Purchasing,
SAP Ariba Contract Management,
b. Report on maverick spend Mandatory Customisation
S/4HANA - Embedded Analtyics,
BW/4HANA
S/4HANA - MM - Purchasing,
c. Report with contract status or message SAP Ariba Contract Management,
Mandatory Customisation
sent automatically S/4HANA - Embedded Analtyics,
BW/4HANA
Source-To-Procure-to
Ref.
IT Business Requirement Priority Vendor Response Module Name
No.
S/4HANA - MM - Purchasing,
SAP Ariba Contract Management,
d. Report on non-contracted spend Mandatory Customisation
S/4HANA - Embedded Analtyics,
BW/4HANA
S/4HANA - MM - Purchasing,
SAP Ariba Contract Management,
e. Report against contract compliance Mandatory Customisation
S/4HANA - Embedded Analtyics,
BW/4HANA
S/4HANA - MM - Purchasing,
SAP Ariba Contract Management,
f. Report on time taken at each step (TAT) Mandatory Customisation
S/4HANA - Embedded Analtyics,
BW/4HANA
S/4HANA - MM - Purchasing,
Ability to form document repository for SAP DMS,
Mandatory Standard functionality
legal documents SAP PO,
MS Share Point Online
Ability to view audit trail of all the workflow S/4HANA - MM - Purchasing,
Mandatory Standard functionality
steps and user actions S/4HANA - Workflow
3.8 Payments
Ability to have a Cheque Master with
Mandatory Customisation S/4 HANA FI-AP/GL
tracking of cheque numbers
Ability to track Cheques bounced /
Mandatory Standard functionality S/4 HANA FI-AP/GL
represented account
Ability to allow processing of manual
cheques in case auto cheque processing Mandatory Standard functionality S/4 HANA FI-AP/GL
fails
3.9 Manage payables
Ability to provide reconciliation of
Mandatory Standard functionality S/4 HANA FI-AP/GL
subsidiary ledger to G/L
Customisation S/4 HANA FI-AP/GL
Ability to view total vendor spend across
Mandatory S/4HANA Embedded Analytics
legal entities and locations
SAP BW/4HANA system
Ability to support A/P aging report on
outstanding items , due date , invoice
Mandatory Standard functionality S/4 HANA FI-AP/GL
date, project based procurement vis-à-vis
non projects & supplier.
Ability to facilitate invoice inquiry
supporting search by amount, invoice
Mandatory Standard functionality S/4 HANA FI-AP/GL
number, vendor number, vendor name
etc.
Ability to create provision by IDs, accruals
by IDs/ suppliers, and manage their Mandatory Standard functionality S/4 HANA FI-AP/GL
closing
Source-To-Procure-to
Ref.
IT Business Requirement Priority Vendor Response Module Name
No.
Ability to provide creditors report showing
balances for:
- All creditors
- User defined range of creditors
Mandatory Standard functionality S/4 HANA FI-AP/GL
- Account balances aged over 1 month, 2
months, 3 months etc.
- Aged by transaction date
- Aged by due date
Ability of system to generate report on
year-to-date payments made to the Mandatory Standard functionality S/4 HANA FI-AP/GL
vendor
S/4HANA - MM
S/4HANA Finance
Ability to check if suppliers Sale Input is
SAP ASP Add-on Solution for GST
matching with our Purchase Input to claim Mandatory Standard functionality
(SAP DCS - Digital Compliance
Income Tax credit
Solution) & Third Party GSP
Services
S/4HANA - MM
The solution should be integrated with
Standard functionality SAP Ariba
SAP S4HANA
SAP PO
As confirmed by Tata Communications, Ariba Spend analysis has not been considered as part of engagement
scope.
A mix of standard SAP S/4HANA P2P standard reporting alongside custom reports will be leveraged to meet the
requirements
Procure-to-Pay
To be filled by SI bidders
Remarks
A mix of standard SAP S/4HANA P2P standard reporting alongside custom reports will be leveraged to meet the
requirements
TCS recommends that in order to have flexibility and drive high level insights, SAP S/4HANA - optimized Business
Planning (add-on over SAP S/4HANA) can be leveraged.
Some of planning requirements for select items can be managed using reorder level planning
Historical data analysis (data not available in SAP S/4HANA system) can be made by developing the desired analytical
reporting in BW system. SAP S/4HANA system will not have historical data before system goes live.
SAP budgetary controls systems (fund management) can be used for monitoring the budgets and establishing
controls. (E.g., No PO can be raised by department if budget set of department is exceeded) for Opex. Internal Order /
WBS elements can be used for Capex.
Procure-to-Pay
To be filled by SI bidders
Remarks
Any long term planning aspects can be managed using SAP BP component while analytics requirements can be
managed in existing SAP BW/4HANA system
SAP Ariba Catalog Management solution (also called as Ariba Procurement Content) integrated with SAP S/4HANA
Procurement will be enabled to meet employees’ self-purchasing requirements for goods and services.
The solution’s punch-out capability will drive improved user experience in terms of providing consumer like shopping
experience alongside driving greater contract compliance
Purchasing team will negotiate and mutually agree with suppliers for the select categories / products and their prices.
Catalogs
Standard can be structured
functionality basedFree
to manage on business needs/ (E.g.,
of cost goods Global
samples / Local
in SAP catalogs).
S/4HANA procurement.
Users can run the reports to review the historical pricing of same material or material group items for comparison and
The user can
reference select from internal catalogs maintained or can punch-out to specific supplier sites
needs.
The solution will also provide for cross-catalog search functionality among punch-out suppliers bringing the relevant
details and prices at one place.
Ariba catalog management is available as part of Ariba Buying and Invoicing module.
P2P process for select purchasing categories as discussed and agreed during business blueprinting stage
will be enabled in Ariba Buying and Invoicing. For most of core categories, it will be enabled in SAP S/4HANA
only.
Procure-to-Pay
To be filled by SI bidders
Remarks
As understood from TC team, users will be entering in the changed business requirements in system.
SAP Ariba / SAP S/4HANA standard / custom reporting / Analytical reporting can be leveraged for desired insights.
The templates for TC specific needs will be configured to drive end-to end sourcing processes. Any additional
templates to meet region / category specific needs can be additionally configured. However any sourcing "results" is a
subjective parameter and the same to manually done.
The desired approval workflows in line with requirements will be configured in solution for tracking and transparency
needs.
Ariba network drives suppliers collaboration wherein suppliers can raise their queries for clarifications over Ariba
platform itself.
Customer Order Procurement: COP process will be enabled as part of holistic procurement solution wherein requests
from SFDC system can be ported to SAP S/4HANA procurement and therefrom to SAP Ariba sourcing solution for
required sourcing needs.
The suppliers can register themselves with basic mandatory information during sourcing process to participate in the
sourcing events.
PR and RFQ will be created in SAP S/4HANA system which will be converted into a SAP Ariba sourcing project
request in SAP Ariba (through integration over SAP process Orchestration)
SAP Ariba Contract Lifecycle management solution is recommended for managing the contracting process including
collaborative authoring and sign-off. Any standard clauses can be maintained in libraries for reuse.
Ariba payables (discount management) solution is suggested for driving dynamic discounting needs. Supplier / TC can
create the proposals and once agreed by other party, the payments can be released by TC to supplier net of additional
adhoc discounts offered.
Note:- Implementation of SAP Ariba Payables / Discount Management Solution is not part of TCS Scope.
The sourcing processes for Project Specific needs will be managed using SAP Ariba Sourcing module. Requirements
need to be specified clearly (say in RFP document) and a sourcing project needs to be created to manage the RFx /
Auction processes.
From SAP Ariba perspective, the process will be managed in similar fashion as for other TC sourcing needs. The
project specific sourcing templates for will be configured to meet process specific needs.
Supplier data can be maintained in self-service mode by suppliers themselves using Ariba SIPM. Or, the data can be
maintained by TC manually in SAP S/4HANA Procurement (business partner).
At time of creation of PR and PO, the requirement can be assigned to a WBS element (project) to account for project
specific tracking and capitalization needs of material procured.
The operational project specific requirements viz project start, execution and closure will be managed using SAP
S/4HANA project systems.
Procure-to-Pay
To be filled by SI bidders
Remarks
The country specific mandatory compliance details viz GST number / PAN number in India, W9 / W8 form for USA can
be managed as a standard feature in SAP Ariba. The necessary approval workflows can be configured and suppliers
can be classified into different categories viz Approved, Preferred etc.
Further, SAP S/4HANA system and Ariba SIPM will be synchronized with each other. The supplier details can be
created / updated in SAP S/4HANA system also which in turn will automatically update the Ariba system too.
TCS recommends to use Ariba Commerce Automation Module (subset of Ariba Supply Chain Collaboration) for
automatic exchange ofAriba
key purchasing documents
Supplier Information between
and Supplier
Performance and Tata Communications (TC).
Management
AribaThe supplier
solution also needs
provides to befunctionalities
for flexible available overtoAriba platform
assess for sameand
the suppliers as a pre-requisite.
thus TC continual
facilitates the needn’t share the of
monitoring
documents viz PO, Invoice etc. over e-mail / existing
fax with supply
suppliers however the
relationships. solution will set-up the mechanism to auto-
exchange the select key documents on both sides and thus saving on time and bandwidth of associates. E.g.,
Purchase can
Key stakeholders Order, Supplier
update theiracknowledgement, GRN,specified
feedback / ratings over Invoice, parameters
Payment Remittance
for each ofetc.
suppliers.
Supplier
The can will
templates attach
be necessary
defined for supporting
performance documents
which cantoo
beas needed
reused as during
part of the process (sourcing
performance process
evaluation /
projects.
registration process / purchasing process)
Workflows will be configured to drive transparency and efficiency. The feedback / scores can be shared with suppliers
Ariba Commerce Automationfor only hastobeen
them shareconsidered
their inputs for
andimplementation
comments too. as part of TCS Scope. Ariba
Supply Chain Collaboration module has not been considered for implementation
The solution provides for standard reporting / dashboards to assess the suppliers scores and derive insights for further
course of action.
SAP S/4HANA Procurement also provides for vendor evaluation functionality on specified parameters however SAP
Ariba solution is more flexible to account for qualitative parameters too. The usage of appropriate solution component
will be discussed and agreed during Solution Blueprinting phases
Procure-to-Pay
To be filled by SI bidders
Remarks
Contract authoring, negotiating iteration and contract version changes and sign-off can be managed in Ariba Contract
lifecycle management. The operational execution of contract will be managed in SAP S/4HANA system. Contract
compliance will also be driven using Ariba Catalog management solution.
For select functions / items. Custom developments in SAP S/4HANA solution otherwise.
SAP Business Partner Standard or classification can be used to identify / classify. Purchasing Info records with
conditions will help to classify the vendor and product combinations
S/4 HANA standard master data will provide various unit of measurements like Base Unit of Measure, Alternate Unit of
Measure with Conversions factors, Batch Unit of Measure etc., which can be used.
Procure-to-Pay
To be filled by SI bidders
Remarks
SAP – Serial Number management with Serial number profile can be used to identify and differentiate between
individual items of material. This component therefore ideally supplements the material master record, which may
contain all data for describing and managing a piece of material, but which in itself does not enable to differentiate
between individual items of that material.
Serial number management will be configured to capture the serial number of select networking equipment and CPE
items at time of GRN based on business requirements. A unique serial number assists with identifying the item
uniquely throughout the supply chain and can also be referred for any warranty claims.
The serial number information will be used to create the equipment master in SAP S/4HANA Plant Maintenance
module wherein Warranty information will be updated.
.
SAP S/4 HANA standard Roles and Authorizations will be used with object level authorization if required
S/4 HANA standard reports will give the TAT in number of days from invoice posted to payment, however for time
based TAT, issue resolution the same needs development.
SAP S/4 HANA Inventory Mgt. standard goods receipt process, e.g. Inbound Delivery, Quality Management will
address the same. SAP S/4HANA functionalities can be deployed for inspection of goods.
Invoicing tolerances is standard feature which can be used for invoices matching.
SAP S/4 HANA standard Purchasing will be used where either CPE / Customer Order Number or Circuit ID Number
can be tracked through out the supply chain for more visibility. Release orders can be issued against the specified
contract for reference.
Contract life cycle will be handled both in SAP Ariba and also in S/4HANA purchasing, however for some of the Track
and trace compliance measures might involve customization.
SAP S/4 HANA and SAP Ariba Standard Roles & Authorizations.
SAP S/4HANA - Embedded Analytics standard and custom HANA views will be used to address these requirements.
In addition S/4HANA will be integrated to Data warehouse system Terradata (EDW) for business analytics reporting
through BOBI tools.
Procure-to-Pay
SAP S/4HANA - Embedded Analytics standard and custom HANA views will be used to address these requirements.
In addition S/4HANA will be integrated to Data warehouse system Terradata (EDW) for business analytics reporting
To be filled by SI bidders
through BOBI tools.
Remarks
TCS understands category link is to associate a unique number through out the procurement supply chain, if so the
same be build.
SAP S/4 HANA standard workflows are available, however SLA milestones, contract usage notifications needs
customization
SAP S/4HANA - LD calculations can be done in purchasing as standard which can be passed to Special G/L for
invoice with customization
TC can utilize the existing Microsoft Share point online (or SAP Open Text ECM) for documentation management
system and integrate the same with SAP S/4 HANA system. SAP DMS will be required to the extent of Meta Data
preparation in SAP, however document will get repositorized in MS Share Point Online.
SAP S/4 HANA Standard capabilities in purchasing, inventory and Invoice Mgt.
S/4 HANA system is Unicode compliant and therefore it supports mutli language capabilities.
Procure-to-Pay
To be filled by SI bidders
Remarks
SAP Standard inventory data like Quantity, Inventory Valuation, Storage locations / Bin Locations, Port defined as
storage location, or vendor managed inventory
Physical inventory functionality in SAP S/4HANA will be used to update the inventory based on physical counts
SAP S/4 HANA standard LE Shipping can be used to do shipment planning and execution, however for tracking
necessary interfaces and additionally tech capabilities are required like GPS, RFID etc., which is not in scope.
The purchasing documents during P2P cycle can be exchanged with Suppliers enabled over Ariba network
automatically.
Procure-to-Pay
To be filled by SI bidders
Remarks
Statisical Vendor Sampleing may not be possible however selection of vendor invices may be possible with
customization
TC can utilize the existing Microsoft Share point online (or SAP Open Text ECM) for documentation management
system and integrate the same with SAP S/4 HANA system. SAP DMS will be required to the extent of Meta Data
preparation in SAP, however document will get repositorized in MS Share Point Online.
SAP Standard
Cheque register will be maintained based on the cheque lots which track the cheque numbers.
Cheque bounced can be traced through reason code identified for this Purpose. Based on the cheques voided due to
bouncing, the same can be represented with automatic functionality
Manual cheques can be Processed as standard functionality in case auto cheque processing fails
Reconciliation account through automatic account determination maintained in the vendor master
Total spend across legal entities will be consolidated. To be arrived through customization.
Ageing analysis
Based on the account balance with the document types overall payments can be extracted
Standard ageing report functionality to provide ageing report . Since it is defined by the user, the same needs to be
customized
Standard Reports can be leveraged. Customization might be needed based on detailed requirements
Credits based on the document type can be generated as Invoice report for a particular time frame. No separate
register In case it is required the same needs to be customized.
Payment report can be generated based on document type for a particular time frame. No separate register In case it
is required the same needs to be customized.
The Payroll journal entries will flow into SAP S/4 HANA FICO module for GL wise Tracking and clearing after
generation of DME File
TCS recommend TC to utilize the existing Microsoft Share point online for documentation management system and
integrate the same with SAP S/4 HANA system. SAP DMS will be required to the extent of Meta Data preparation in
SAP, however document will get repositorized in MS Share Point Online.
Reports can be built for same. SAP Vendor Evaluation functionality or SAP Ariba Supplier performance solution can
also be used
Asset Master and Eqpt Master to be in synch, warranty information's to be stored in Eqpt Master which will help the
purchase and maintenance team with warranty life cycle
Procure-to-Pay
To be filled by SI bidders
Remarks
The necessary fields to be captured will be made mandatory in system E.g., GST Number, PAN number etc.
SAP S/HANA system is GST compliant. Standard / custom reports can be leveraged to provide reporting insights to
TC users based on business needs.
SAP S/4HANA system will provide for purchase data however a third party or SAP's ASP solution will be needed for
reconciling if TC's purchase input is in line with suppliers' sales inputs for income tax credit. Any discrepancies can be
alerted to supplier over mails. Detailed clarifications between the buyer and supplier to happen offline.
It's suggested that suppliers are enabled over Ariba network and flip TC's Purchase order to create Invoice. Key
advantages:
a. The supplier is flipping the PO into an invoice resulting into auto-population of relevant data and minimization of
data entry errors. Supplier can use the same invoice into his system with formatting changes either through download /
upload or through direct integration
b. Select data validation related business rules can be configured on Ariba network side preventing wrong invoices to
come to TC, get into processing queue and then getting stuck for data errors, coordination with vendors for
rectifications. It will save processing time and improve STP % too.
c. After GST implementation, every supplier is creating a system based invoice for him to submit the details into GSTN
portal. The recommended system will also improve upon the successful reconciliation %age between TC’s purchasing
system data and suppliers’ sales data.
SAP ASP Add-on Solution for GST (SAP DCS - Digital Compliance Solution) & Third Party GSP Services are
not considered as part of scope here
Procure-to-Pay
To be filled by SI bidders
Remarks
Existing portal provides for basic functionalities for vendor to see his PO, Invoice status. The same can be integrated
using SAP PO with SAP S/4HANA system.
Otherwise, TCS suggests to use SAP Ariba Supply chain collaboration (inc Commerce automation) for collaboration
over operational purchasing transactions. The Ariba solution has standard integration with SAP S/4HANA too.
A mix of standard and custom reports can be leveraged for required reporting insights. Analytical reports can be
created in SAP S/4HANA embedded analytics or in SAP BW/4HANA system.
The alerts will be customized based on needs. E.g., contract expiry, contract usage etc.
For documents storage (received as part of P2P compliance), the metadata of digital documents can be maintained in
SAP S/4HANA DMS while scanned document can be stored in TC's SharePoint content management solution.
Documents versioning can be maintained
Rebates / discounts can be managed as part of standard PO pricing procedures or can be customized. Dynamic
discounts to be managed using Ariba payables (discount mgmt.) solution.
Related to Invoice Processing. TCS suggests to use SAP VIM for invoice processing
Standard analytical reports can be used to assist for contextual decision making at time of invoice payments. Any
business rules around same will need to be customized
System provides for multi-currency capabilities allowing for transaction with suppliers across geographies in respective
currencies.
As port of invoice processing, SAP's partner solution OpenText Vendor Invoice management (VIM) is suggested. the
solution wk ill allow for creation of queues for invoice processing to be done by associates. Further, the reports can be
leveraged to analyze the same.
Any access control will be managed using Roles and responsibilities to allow for segregation of duties.
Vendor desk integration with system can be enabled using SAP PO. Further SAP Fiori will be used for undertaking role
wise transactions and approvals using laptops / desktops / mobile / tabs providing a better user experience.
Procure-to-Pay
To be filled by SI bidders
Remarks
Vendor / business partners master data will reside in SAP S/4HANA (or master data will flow from TC's MDM system to
SAP S/4HANA).
The necessary vendor master data will be sent to SFDC for business process activities there
Vendor can also create their profile as part of registration as well as update the same on Ariba Supplier Lifecycle
Performance. The same will be synchronized with SAP S/4HANA business partner master data.
The sub-set vendor can be managed using partner function. System provides for standard duplication checks however
rest can be customized.
Any additional data validation checks or rules can be built into SAP S/4HANA system. Any BDC can be created to
upload the vendor details with necessary controls into system based on needs
Vendor can be blocked too. System will not allow for any transactions with blocked vendors. Vendor account groups
can be created inline with TC's needs
System provides for multiple standard reports which can be leveraged for desired reporting needs too.
Any FAQs / policies and links can be displayed over Ariba network to suppliers. A link can be made available from TC's
website (supplier section).
Procure-to-Pay
To be filled by SI bidders
Remarks
KPI design and analytics will need customization efforts in BW system. Cascading up / drilling down ability is usually a
standard feature in analytical reporting.
The necessary data points to design and monitor the KPIs should be available in SAP systems or in other third party
systems as a prerequisite.
SAP S/4HANA based solution will be integrated with Tata Communication's selected Tax solution wherever feasible.
Liability can be arrived at only for tax transactions posted in SAP. No Global tax intelligence will be possible