Support Project (AMS Project)

SLA(Service Level Agreement)

SLA is mutual agreement between IT company and business
SLA contains as below

1 It contains Financial terms

Contract Period===> 5years
Contract value ===>5Cr

2 Service Related Terms

Scope of the Project, scope of Modules and which Co
Support Times ( 24 Hr or 16Hr or 8hrs) and how man
Resource Skill set (Senior / Middle /Junior level Consu
Penalty Clause
3 Other Terms
Severity / Priority / Category of Tickets (P1/P2/P3/P4
Times lines to resolve the issue for each category of ti
What is the targets to be achived for each category o
90% of tickets to be resolved for P1 tickets
95% of tickets to be resolved for P4 Tickets(Lo
Strategy of escalations/ penalities if target is not achi

Status Of Tickets
Time Count 1 Create Status ===> Business user w
Time Count 2 Accept / Reject status ===> Project team w
===>

Time Count 3 In progress or On Going Status ==> Consultant will

No Time Count 4 Onhold (waiting for inputs) ===> Ticket having i
Time Count 5 In progress or On Going Status =====> Received rep
No Time Count 6 Resolved ===> Consultant sen
 7 Confirmed / Closed ===> User accepted
Priority of tickets
Tickets = Incident
1 P1 Very High Priority Tickets
2 P2 High Priority
3 P3 Medium Priority
4 P4 Low Priority

1 P1 Very High Priority Tickets

Ticket Accept /reject
Temporary Solution / Intial Solution /
Final Solution
2 P2 High Priority
Ticket Accept /reject
Temporary Solution / Intial Solution/
Final Solution

3 P3 Medium Priority
Ticket Accept /reject
Temporary Solution / Intial Solution
Final Solution
4 P4 Low Priority
Ticket Accept /reject
Temporary Solution / Intial Solution
Final Solution

SAP Supporting Tools

1 SAP Solution Manager ( SAP Product)

2 Service Now
3 Remedy
 4 Jira
5 Mercury
6 Ctrix
7 Tivoli
8 Outlook
9 HPQIC

Ticket Process

Ticket Tool
Ticket with Create Status===> Project Monitoring Team===>
 Consultant===> Change status to Onoing===> Consultant wi
Consultant will change status to OnHold till get reply
Consultant need to work on issues===> Provide soluti
User will checkthe solution===> If results not ok===>
User accepted solution===> User will send confirma

Note :
User not replying or Not confirming to close the incident

Every company having stratey ===> 3Strike rule

3Strike Rule===> send 3reminders day by day(every 2 or 3da

How to resolve the Issue :

1 Read the issue which is specified in the ticket, check any atta
2 Try to understand the issue
3 Propose the solution if you know
4 Unknown issue then replicate issue in Quality System
Find the rootcause for issue
Then Propose the solution
Solution Might be
1 Master data updation
or
2 Configuration Chan====> Propose configurati
or
3 Modfication of Pr ====> Propose Program c
or
4 SAP Std Error ===> We will raise ticket t
SAP may Propose solution
1
 5 If unable to replicate the issue in quality system
1 Better to ask the user to share screen through the M

Need to ensure beow contents while proposing solution to the user

1 Overview the issue :
1 Write briefly about the issue

2 Analysis of the issue

3 Propose the solution

4 Prepare and attach the supporting document

100 Consultants====>80% working on AMS Support Projects +20% working on

 ompany and business

Modules and which Company codes covered

or 8hrs) and how many days supported (only working days or All Seven Days)
dle /Junior level Consultants )=====> Every Project having Mixing of Consultants

Tickets (P1/P2/P3/P4) P1-Very High Priority P2-High Priority P3-Medium Priorit

for each category of tickets 4hrs 1day 2 to 3 days
ed for each category of tickets 90% 90% 95%
olved for P1 tickets
olved for P4 Tickets(Low Priority)
ties if target is not achieved

===> Business user will create ticket in Ticket Tool====> Reaches to iT support team with stat
===> Project team will monitor ticket Q then change the status either to accept or Reject and
We can reject ticket in below cases ==>1. relevant module not in project scope 2. Ticke
In suce cases , we will reject tickets with comments

==> Consultant will change the status to ongoing===> That means consultant working on the
===> Ticket having insufficient information , you asked business for inputs====> Consultant w
=====> Received reply from Business along with required inputs
===> Consultant sent or provided solution to the Business and waiting for confirmation to acce
 ===> User accepted solution and confirmed to close ticket

Stoping the Business process ( Unable to create billing /Print , Posting Wrong Financia
Deprecial error ,Month end closing process errors , Funcial area not filled In internal O
Reporting Issues /Clarification Issues etc
Reporting Issues , New requirements / Modification of Requirements /Clarifications et
Target to be Achieved
Resolution time between 2hr to 4 Hrs
30 Minutes 95%
ntial Solution / 2 Hrs 90%
4hrs 90%
Resolution time 8 Hrs
1 hr 95%
ntial Solution/ 4 hr 90%
8 hr 90%

Resolution time 3working Days

1 hr 95%
ntial Solution 2 Days 90%
3 Days 95%
Resolution time 7working Days
1 hr 95%
ntial Solution 3 Days 92%
7 Days 95%
Monitoring Team===> Change status to Accept /Reject===> Assigne ticket to Relevant Consulta
ng===> Consultant will check ticket details ===> Ask the user to provide furtherdetails if any ins
o OnHold till get reply from the User ====> Change status to ongoing once received reply from
ues===> Provide solution====> send mail to the user ====> Conultant need to change staus to
> If results not ok===> User will send mail along with queries to the Consultant===> Consultant
ser will send confirmaton mail to close the incident to the consuultant===> Consult will close th

close the incident

by day(every 2 or 3days once) and closed the incident with final remainder if no replay

ticket, check any attachments

Quality System

=> Propose configuration changesto be done===> with reference to these analysis===> We will

=> Propose Program changes to be done===> with reference to these analysis===> We will crea

> We will raise ticket to SAP in SAP Support site, We will resolve the issue as per SAP Reply
may Propose solution:
SAP OSS note
1 It contains technical Code ( To be implemented By Basis team)
 or
2 Configuration changes ( taken care by Functional consultant)

y system
screen through the Meeting tool ( Invite meeting , ask the user screen and replicate issue in pro

o the user

ects +20% working on Implementation Projects

 P3-Medium Priority P4-Low Priority
2 to 3 days 7days
95%

port team with status create

ccept or Reject and assigned ticket to relvant consultant
oject scope 2. Ticket not belongs to SAP system ( 3rd party system),3. Create ticket for vendor m

ant working on the issue=====> In progress of the ticket

====> Consultant waiting for user inputs and reply

onfirmation to accept or reject solution from the business

ting Wrong Financial data etc)
t filled In internal Order Master, Profit center wrongly filled in Internal Order Master

nts /Clarifications etc

Relevant Consultant
herdetails if any insufficient information
eceived reply from the users
to change staus to Resolved
ant===> Consultant actually need to change the status from Resolved to ongoining===> Then co
Consult will close the incident by change status from Resolved to Closed or Confirmed

f no replay

alysis===> We will create change CR(Change Request)==> Config changes routed through CR

is===> We will create change CR==> Program changes routed through CR

per SAP Reply

eplicate issue in production system)
e ticket for vendor master cretion ( Master data) not project scope
oining===> Then consltant need to work on queries===> Once fix the issue===> Send / update
onfirmed

uted through CR
==> Send / update mail to the user====>Change status to Resolved
1 Internal Order created Through CRM service Orders/Contracts
Issue : Funcial area not filled in the Internal Order Master
Default profit center assigned in the Internal Order mast
Internal Order Settelement rules having Wrong COPA Re

Analysis :
Funcial area not filled in the Internal Order Master
Functional area need to fill Order based on Functi

Next Step : Raised ticket to SAP about standard Func

Proposed Work Around Solution :

Execute KOK4 along with substitution rule

How to set up Substitution Rules :

 Save

Create variant
Front end :
Execute KOK4
Remove Test run then execute
KO03 Check Order Master data field updation
Final Solution : Waiting for SAP Reply
 Issue2 Default profit center assigned in the Internal Order mas

Default Profit center Y01

Profit center Logic

CRM Service Order -----------------------

Profit center derived base
Profit center derived Corre

Issue3 Internal Order Settelement rules having Wrong COPA Reporting Dime

Analysis
CRM service Order--------------> Creating Internal Order---

Auto Release of In

CRM service Order

User Defined Fields ( Part of COPA Reporti
Product Group
Service Line
Profit center
/Contracts
Order Master
nternal Order master ( Profit center should copy from CRM service orders)
ng Wrong COPA Reporting Dimensions

Order Master
der based on Functional area assignement in the Internal Order Type but not working as per sta

bout standard Functionality Not Working

ith substitution rule to update some field in asset Master and save then functional derived corr
ata field updation
Internal Order master ( Profit center should copy from CRM service orders)

-----------------------------------------------------------------------> Internal Order

enter derived based on Sales Distric Field
enter derived Correctly : Y200 Profit center ====>Y200 (
Issue is that Profit
Expected to be Pro
Profit rederiving C
Temporary Solutio
Final Solution :

PA Reporting Dimensions

ng Internal Order-----------> automatic Settelement Rules ( standard configuration settings )====

Auto Release of Internal Orders===> Settelement rules creates Automatically while releasing In

==========> Internal Order

Part of COPA Reporting Dimensions) Master data ( User define
The enhancement COOPA002

What is actual Issue==> Internal Order cr

SAP Product limitation, But it setteles cor
FI settelement document level getting rig
As Functional area and profit center not fi
Proposed Solution :
Option1: Waiting for SAP solution
OR
Option2 KOK4 ====> Update Internal orde
OR
Option3 Use BDC to rederive PSG through
OR
Option4 Use enhancement along with func
COOM0003 User-Exit for developing user-

EXIT_SAPLKOBS_001
t working as per standard functionality

ctional derived correctly in the order Master

 enter ====>Y200 (Expectation)
Issue is that Profit center intially filled with Default Profit center with Y01 so not filled profit ce
Expected to be Profit center Y200 should derive from CRM service Order
Profit rederiving Correctly when go KO02 save then it filling Correct Profit center
Temporary Solution : KOK4 update some text field then it deriving correctly Profit center base
Final Solution : Waiting for SAP Reply

ation settings )======>Receiver PSG

ly while releasing Internal Order

data ( User defined fields by using Master data user exist)

The enhancement COOPA002 affects order master data saving only and the function module EXIT_SAPLKAUF_001 is called with parameter I_FUNC = 'SAV

> Internal Order creating parally and settelement Rules creating parally these user defined field
n, But it setteles correctly to right reporing dimensions i.e rederiving COPA reporting dimensions
ent level getting right reporting dimensions eventhough Settelement rule having wrong Reporti
d profit center not filled correctly while creating Internal order but subsequently updating these
P solution

pdate Internal order but settelement rules not deriving

derive PSG through daily scheduled jobs

ent along with functional modules to update or rederive Settelement rules ( More Complex dev
User-Exit for developing user-defined strategies
o not filled profit center Correctly

y Profit center based CRM Order

with parameter I_FUNC = 'SAVE'

e user defined fields unable to fill Settelement Rules

porting dimensions while posting Documents
ving wrong Reporting dimensions
ntly updating these fields by using KOK4 but settelement rules still continuing Old Reporting dim
More Complex development)
g Old Reporting dimensions
1 Issue :
Transacion type is not updated to FAGLFLEXT but updated BSEG

Overview of the issue : Asset transaction type not updating to th

Analysis :
We observe that the transacton types corr
Its impacting the BW reports and used trns
The reason for issue is that missing of confi

Proposed Solution :
Need to include below configuration to fix
need to add the scenarios and custom field
FIN_CONS updates the fields of Trad
 The above changes can be address through CR proces

Payment proposal for foreign vendors

Please be informed that I have a problem to creat
Ticket Contents Could you please be so kind and let us know how

Note1:
Collect insufficient data from the user that is Vend

Analysis :
Try to replicate issue in Quality system and find th
or
Check vendor master bank details and also payme

The reason for issue I that IBAN details not mainta

Proposed Solution :
 Recommend to maintain IBAN details in the vend
Run the new payment proposal
Issue
Inventory data is inconsistency for material FGX during MIGO
Company having ML Actual costing

Analysis :
As per SAP OSS Note NO :2917042 .The reason for issue is that d
Proposed Solution :
Perform the FAGLGVTR program to carry forward balance from
Then perform MIGO

Issue
Asset transaction 100 showing as external acquisation but wron
Analysis :
The issue might be SAP product error hence raised the ticket to
Issue
1.Balancing field “Profit Centre” in line 01 not filled Error in

Analyis :
The reasn for missing cost center in the asset mas
Need to identify the assets which missing cost cen

Proposed Solution :
Need to assign missing cost center in the asset ma
Issue
2.Transaction key XXX YY chart of accounts ZZZZ not defined in t
Solution
A) Invoice and the tax code has not been maintained in Configu
Issue:
3."No clearing accounts specified for company codes A001/A000- "dur
A)OBYA Configuration

Issue
Functional area wrongly updated to the old functional area instead of

Analysis :
As per SAP standard functionality , it post to the old funtional area for
Proposed Solution :
Use the program : ZFCORRFA_FAGL
 We can correct or change the functional area man

Se38

Prerequest :
Need to implement SAP OSS note : 677630 to ena
Then possible use the above program

Issue: FI-AA - New Depreciation Smoothing config is not taking end of useful l

Analysis: As the Smoothing flag is activated for these company c

The periodic depreciation to be posted by distribu
so as per the user request we are deselection the
Proposed Solution
Need to create CR
Provide what is impact analysis if deselecting sm
 Then need to set confguration====> Testing====>

Issue: Assets got successfully transferred but there is a variance between Dep

Analysis :
We have found in the deprecation key “ZSL1" Multilevel Metho
so we have created new depreciation key “ZSL3” and new multi

The reason for variation is that sender and receiver asset having

Issue: certain assets on disposal order being rejected

Few assets not deactivated while disposing assets
Analysis :
The user can post asset acquisition value of ZERO $ with transcti
if there will not updated in asset master data field "Deactivation
User need to set deactivation indicator Manually

Issue: GL Mapping update due to Bank account change

Analysis :
The user wants to changes the GL account for Bank whic is migr
Need to change Bank GL account in FBZP and EBS
We need to change Bank GL account after approv

Issue: Blocked billing from postings in VFX3

 Analysis :
Found Billing document is blocked with Account determination
Need to check the AAG for Customer and AAG for material weth
Will check the Configuration and will convert this incident into s

Issue: depreciation key ZA10 is incorrect error.

Analyis
User is getting the above error because Useful life is maintained
User need to maintain useful life in the asset master to resolve

Issue :STO error. Unable to post asset in fiscal year 2021.

Analysis
You have not closed your Asset Fiscal Year for 2020, see below i

Proposed Solution :
Need to close Asst FY for 2019
Then you can able to post transactions

Issue : Duplicate transaction found in FEBN. Account ID# BO04 Doc# 10361

Analysis:
Its not a duplicate posting and it is a reversal of the document s
 Proposed Solution :
Need to give explanation to the business

Issue : Assets Not Depreciating

Analysis
Which user provided assets it is selected “Asset shutdown flag”

Proposed Solution
Run the dep after deactivating Shutdown Indicator if user want
ut updated BSEG table while posting asset transactions like F-90

ot updating to the FAGLELEXT but update to the BSEG table whie posting FI asset acc

acton types correctly updated in BSEG but entries missing in FAGLFLEXT

rts and used trnsaction type field in the report
t missing of configuration

nfiguration to fix the issue

and custom fields i.e FIN_CONS to the ledgers as below
the fields of Trading partner and asset tansaction type in general ledger view ( FAGLF
problem to create the proposal payment for foreign vendors
et us know how to prepare the proposal payment for foreign vendors

user that is Vendorcode , Payment proposal run , which payment method using'

ystem and find the root cause

s and also payment method prequest===> then identify missing data in the vendor m

etails not maintained in the vendor master as per payment method.

tails in the vendor master

for issue is that due to Balance C/F ( FAGLGVTR) not performed in quality system

ard balance from previous years to current years

isation but wrongly showing description as opening balance in fi document line item

ised the ticket to SAP and waitng for reply

ot filled Error in ASKB.

in the asset master.

missing cost centers

er in the asset master

Z not defined in table T030K

ained in Configuration.--OB40

A001/A000- "during the intercompany transaction.

area instead of the new functional area while settelement of order for fi ducument

ntional area for existing orders

SAP predelevered Program

nctional area manually for already posted fI documents

e : 677630 to enable the program

ng end of useful life into account

these company codes at the config level.

osted by distributing the remaining depreciation posted equally throughout the fisca
e deselection the smoothing flag for consolidated company codes and converted this

f deselecting smoting indicator====> Is there any impact on existing assets / Historic

==> Testing====>UAT====> Approvals====> TR====> Prd client

nce between Deprecation

Multilevel Method (Z02) updated Base value “24” ( Net book value) because there is v
3” and new multilevel method “Z03” with Base value “01” Acquisition value.

iver asset having different Dep key and Dep Method

RO $ with transction code. ABCO and there will not be create accounting entry,
eld "Deactivation on" than the user need to entry by manually

Bank whic is migrated from Royal Bank for AR transactions.

in FBZP and EBS settings
unt after approvals=====> This can be handled through CR Process
t determination error.
for material wether assigned or not in the customer master and material master. If it
is incident into service request to maintain the missing configuration if any.

life is maintained as zero in Asset 209888

aster to resolve the issue

020, see below in OAAQ you still have Asset Fiscal Year 2019 as the last closed fiscal

04 Doc# 103612625 post on Oct 28 for Chno00019576 $303.88; Doc# 100681679

f the document show and system

t shutdown flag” in asset master data so this assets deprecation not calculated, user

ator if user want to run depreciation

osting FI asset accuations trough F-90

dger view ( FAGLFLEXT)

ethod using'

a in the vendor master

uality system

cument line item

for fi ducument
oughout the fiscal year,
nd converted this incident to a change request and communicated same to the user..

g assets / Historical Assets

because there is variance depreciation calculation
n value.

ting entry,
terial master. If it is perfect then need to look maping of GL accounts inVKOA
n if any.

last closed fiscal year.

Doc# 100681679-Duplicate post again on Oct 31st

calculated, user let us know if any more details required to closure of the incident.
ame to the user..
s inVKOA
of the incident.
 RCA ( Root Cause Analysis)
Need to be prepared in the below cases
1 Very High Priority Issues
2 Recurring nature of similar type of issues
3 Any abnormal instance happened

Contents of Root Cause Analysis

Issue :

Business Impact :

Root Cause

Corrective Action

Preventive Action

ExamplMissing company codes in derivation rules (KEDR)

Issue :
Product(mat code) missing in KE24 report for record Type A(in C

Business impact:
Impact on MEC closing and MIS report and Miss match the data w
Root Causes:
Missing the company codes RI1 & RI2 in derivation rules (KEDR)
Corrective action:
 •Identified the sales orders which are missing product in the KE
•We have reversed / cancel all the documents which are poste
•Maintain company cde in the relevant derivation rules and r
•Matching the product quantity in the report and sales order.
Preventive action :
Updated the missing company codes in derivation rules.
Need tobe very careful while working through KEDR

Example2
Issue:
Received a high inflow of tickets in FICO area during the Jan2020 MEC/Y
Business impact:
Delay in business activities due to the organizational changes in terms o
Root Causes:
Organizational changes done during the year end which resulted in crea
Corrective action:
All errors were solved based on the incidents received like maintaining th
Preventive action :
All organizational changes leads to new requirements for updating variou
The users identify the master data that is to be modified and accordin
Status- Closed.
Example3
Issue: Open items are not available for manual clearing

Buiness Impact :
Unable to clear open items
Root Cause:
Business users will create payment proposal (F110) and o
Lack of knowledge and Training
 This is because of payment proposal and not done payme

Preventive action :
Since they have created the payment proposal, the open
If they want to make the payment entries manually, dele

Recomndation:
Provide training to the users

Example4
Issue 1 : Repeated incidents for incorrect POC/revenue calculations & p
Business impact:
Incorrect calculation resulting in incorrect postings of revenues.
Root Causes:
The negative costs postings are occurred when the material prices are
POC(Enhancement Program ) is calculated incorrectly in case of correcti
These business cases are not considered in the current program logic.
Corrective action:
Manual correction of material prices and reposting of POC.
Preventive action :
Logic has been included for these business cases in the POC program th
Status- Closed.

Example5
Issue
Multiple jobs scheduled at the same time due to MEC(month end Closing
Business impact:
Due to parallel jobs run for the same order, the POC program generates
Root Causes:
 1)Time difference ( gap ) in executing the jobs.
2) Explored the option of locking the entries while jobs are executed. Ho
3) Explored the other options to schedule the 2nd job after completing ste
Note: Option 2 and 3 are mentioned to avoid further explore on the same in future instances

Corrective action:
Reversal of the document is performed on duplicate entries.
Preventive action :
While changing the scheduled jobs, with sufficient time gaps between bo
Technically not feasible for option1 and option2
Status- Closed.

Issue:
The revenues are not calculated for those contracts whose end date has
Business impact:
Revenues are not posted.
Root Causes:
The issue arises due to change in the contract end date.
Changing of the Contract end date to previous period effects POC prog

Corrective action:
POC program is executed again for these Contracts.
Preventive action :
1)IT support team suggested to make changes for ‘POC program’ and
2)Alternately, a proactive measure to address such cases , AMS Supp
Solution 2 is accepted by Business
Status- Closed.
Note: A word document with the step by step procedure will be prepared and given
Issue:
Revenues are not recognized correctly.
Business impact:
Due to this, the revenues and cost of sales are not booked.
Root Causes:
Due to contract period changes, contract value changes, credit block of s
Corrective action:
Whenever an incident is reported, AMS team does in depth analysis and
Preventive action :
In progress
As the analysis is time consuming, AMS Team is proposing to develop a
Status- In progress

Issue
Unable to create long term contracts with quarterly billing (Billing plan typ
Business impact:
Business is unable to create long term contracts with quarterly billing in S
Root Causes:
Bug in the standard SAP program pertaining to VA41.
Corrective action:
Contract was created with alternate solution by using yearly billing (Z3- Y
Preventive action :
CR has been created to handle this issue and raised with SAP to provide
Status- Closed.
es (KEDR)

cord Type A(in COPA document) for few sales orders for company code RI1 and RI2

match the data with BW

ion rules (KEDR) in few derivation steps.

 product in the KE24 report.
s which are posted without product and rederive the PSG by using KE4S.
tion rules and rederive the PSG by using KE4S.
nd sales order.

on rules.

e Jan2020 MEC/YEC.

hanges in terms of master data creation/changes and related subsequent changes.

h resulted in creation/changes to the master data records , updation of derivation tables

ike maintaining the master data, fixing the errors due to the master data changes.

or updating various tables and related master data . The changes to the master data are
fied and accordingly tickets are raised and Consultant makes the changes accordin

l clearing

osal (F110) and open items will include in the payment proposal are now locked for
d not done payment run and it will block the open items certain vendors which are th

oposal, the open items that are included in the payment proposal are now locked fo
es manually, delete the payment proposal by selecting Go To - Proposal - Delete. The

e calculations & postings.

evenues.

aterial prices are changed at time of goods issue and goods returns.
n case of correction invoices, ie, the POC considers the original invoice and not the cor
t program logic.

e POC program through CR 58323

month end Closing) schedule Changes which results in duplication of POC postings ( Wr

ogram generates revenues twice for the order.

 are executed. However, if we lock the table in program level, the next parallel job will ge
ter completing step 2 of the first job, but could not proceed further as the job frequency

gaps between both the jobs. This is already taken care by Support team.

ose end date has been changed from current to previous period

effects POC program as it does not consider the Contract for POC calculation.

POC program’ and provide additional logic to schedule a batch job for a period of last 6
cases , AMS Support team would provide a list of the contracts at the period end for all

prepared and given to user for future reference.

s, credit block of sales order, the revenue is not recognized correctly. Each case is uniqu

epth analysis and proposes a solution

sing to develop a query/custom program which provides inputs for easy analysis to redu

ng (Billing plan type Z4- 3 months ) for few contracts as the amount exceeds internal SA

uarterly billing in SAP.

early billing (Z3- Yearly Invoice) and later changing the billing plan to Z4( Quartely billing

ith SAP to provide permanent solution. Need to incorporate the program changes a sug
de RI1 and RI2
uent changes.

f derivation tables ( Maintaince tables).

ta changes.

he master data are dynamic and hence are to be handled as they occur.
changes accordingly. Hence no preventive action.

e now locked for mannual payment.

dors which are there in Proposal.

re now locked for manual payment.

osal - Delete. Then you will be able to make payment manually

e and not the correction invoice for POC calculation & postings.

OC postings ( Wrong revenue postings). .

parallel job will get abended instead of waiting for the first job to be completed.
he job frequency of both the jobs is not in same interval ( one being a daily job and the

alculation.

a period of last 6 months. This will run for all changed Contracts ! But business rejected
period end for all the contracts where the contract end date has been changed to the pr
Each case is unique and requires in-depth analysis and propose solutions to correct the

y analysis to reduce the time consumption

ceeds internal SAP limits resulting in dump error in the standard transaction VA41.

4( Quartely billing)

am changes a suggested by SAP. Investigation in progress for implementing the change

ompleted.
daily job and the other being a monthly job). And also there is no step level control on th

business rejected this proposal, as they would want to post for selective contracts.
changed to the previous period, so that the business can take the decision to post the re
ons to correct the errors.

action VA41.

enting the changes. Changes suggested by SAP not implemented.

level control on the job.

e contracts.
sion to post the revenues for the required contracts.
Contract
Validity from 01.04.2019 till 31.03.2025
Contract value===> 6crores for 6 years

Current period : 2.2020 May ( Period2)

Contrct end date has been changed from 31.03.2025 to 30.04.2

POC Program considers for those programs end date is current

in this case the above contract not considered in the result ana

So We need to execute program manally by giving contract man

POC program calculates revenues based on comparing between

POC % = ( Actual cost / Plan cost )X100

Calculated Revenue =Pln revenue X POC%

 May ( Period2)

3.2025 to 30.04.2020

d date is current month or future month

in the result analysis program (POC)

ving contract manually in the selection parameters of the poc program

mparing between plan cost and actual cost

Support Projects -Roles and Responsabilitis

1 Resolving Tickets
2 RCA ( Root cause Analysis for recurring incidents , Very H
3 Value additions to the Business
Automation in few specific areas
Example :
Payment Automatation
EBS Automation
GR/IR automation

4 CR( Change request process)

Preparation of Functional Specification
Testing, Documentation , Training

5 Users Training
6 Weekly meeting with the Business
Discussing about open issues , any difficulties / ri
We are discussing about ticket status
7 Project internal daily meetings
Discussing within project team
Discussing about open issues , any difficu
We are discussing about ticket status

8 Upgrading versions/ Patches---> Basis

Consultants will do testing
g incidents , Very High Prioity Incidents)

nt Automatation
tomation
automation

cification

, any difficulties / risk to resolve the issues/ Any inputs required

issues , any difficulties / risk to resolve the issues/ Any inputs required
ut ticket status