Topmost Priority Issues

SA teams to always produce a Functional Specification for Demands and Projects. I know demands have DAD
document but that is not a FS. This can enforce and smoothen our way for getting the requirement early.

SAP MIC Issues

Excel File Having issues open since July. many errors in the SAPs (P20, BPP, GTS) resulting in wrong customs
declarations in the Netherlands and Italy.

The pdf invoices are as well wrong in several cases.

Examples are collected for all the different cases and shared with IT since weeks, sometimes months (attached here
as well).

CW22 44 TM Karakorum Project

EN400 IT System Infrastructure & Design

I got the below change request from NI that drives 3.5% increase in MN allocation.

Could you please confirm/validate if the new split is OK with the business?

GTS:

DAD is the part of Dema, Mandatory in which SA describes the basic information and analysis of that issue
or change.

For implementing Any New Change in Either Data flow, any change of Data Type

01. Minor Dema

Under the contract of HCL, For this if any new change Then SA will create DEMA first It has seven steps.
Collection-Qualify-BA-TA-Approval-Imp-Evaluation
DAD is the part of BA step.
Then Functional Specification Document should be created by SA.
If there is change which is integrated or supported by another system, then it comes under the umbrella of
Contractor HCL. Based on the nature and req support will be ask from SA to HCL.
Indicate days- Minor Demas –

Good Practice:
New Requirement – Change Request -
BA- Design by SA-
DAD- Write an FS Template float to ABAP Internal Team or (To validate the functional Specification
document)
Write an FS first from SA- Float via email to Technical Team for Review and Schedule a one o one
meeting to review with Technical Team.
Confirmation Email from SA with mutual concern from technical team that FS is Ready to Go.

For Timeline we need to look the requirement very vigilantly.

Timeline for FS to validate from Technical Team-
Schedule 05 Working Days- 15
Working Days. P1-05 P2-10 P3-15.
Urgent & Complex-?

Level of priority- -

How much time for design FS from Solution Architect based on Level of Priority-?
P1
P2
P3

Please propose Timeline- (We will discuss in detail with our Internal Meeting)

FS will float to HCL Team-

Acknowledgment of that FS from HCL Team. Schedule a call timeline – 3 Working days.

BA to TA conversion Phase- HCL will take 10 working Days.

If not reply with in that Timeline- Escalation Matrix flow---- HCL and Counterpart at Nokia
For Major DEMA- HCL not work. Other service providers like Accenture’s/Wipro/TCS.

TDR--- Technical Review Code Review Document- It should be on share point for your review-

TDR will create by HCL- and send it to Technical Team for Approval TDR when they do development in
any system and before transporting it to other system.

According to SA this TDR is not sufficient enough to understand the changes – development done so far in
system----at least it should be shared in SNOW or share point for review SA.
Quality of the Document need to be work.

Schedule a meeting with Internal ABAP Team & SA to improve the quality of TDR.
Either create a Hierarchy Folder for FS- Creation- Review- validate- Change- Approval

UAT--- UAT Sign Of.

If any major DEMA KT is handed over to HCL.

GO Live has two stages: According to good practice.

Bs Go Live
Technical Go Live

Support period- HCL

A project other than HCL- Other service providers Accenture’s or wipro- TCS-
Work Order- Agreement – Terms & Conditions that how support will be provided-
Based on that we generate PO- Mike – Shazia
Automatically go to supplier -notification – they provide confirmation of this PO.
 post go live support
Warranty – 3 Weeks

02. Major Dema

Main Problems:
We don’t have right ABAP support for all SA.