Académique Documents
Professionnel Documents
Culture Documents
BSR 14-788-01
<Project Short
Name>
<Project Version>
<Application Code>
Date :
15/09/2014
Responsibilities
Written by
Authorized by
Name Function
Grgoire COUSIN
BI Runmode Coordinator
Gaetan FALLETTA
Head of CTOIOIM HIB
Department Company
TIM HIB
Date
Signature
15/09/2014
TIM HIB
<Project Version>
<Application Code>
Date :
15/09/2014
Contents
1
Introduction............................................................................................................................3
1.1 Purpose of the document........................................................................3
1.2 Scope of the document...........................................................................3
1.3 Terminology...........................................................................................3
AS IS Description...............................................................................................................4
2.1 Current IS situation analysis...................................................................4
2.2 Risks in case of status quo......................................................................4
TO BE Description..............................................................................................................5
<Project Version>
<Application Code>
Date :
15/09/2014
1 INTRODUCTION
1.1
The BRD documents all the requirements expressed by the business both functional & non functional (security,
performance), highlights impacts & changes on the business process & defines the users population in scope.
This key deliverable is validated by BPL & business key stakeholders. It is the major business deliverable for the
Concept phase ending at M5. During Technical and Functional Acceptance and for Go ahead of Deployment (M11),
this document is the reference to validate the solution by the business.
Through iteration, this document will evolve to a realistic set of requirements from which the project or relevant
organization will be able to define, develop, and deliver a solution that addresses customer and business' needs.
1.2
This Business Requirement Dossier documents the overall requirements in order to be able to specify the IS
solution to be deployed.
1.3
Terminology
GPP
BRD
IS
Information System
TBD
To be confirmed
CR
Change Request
<Project Version>
<Application Code>
Issue:
1.0
Date :
15/09/2014
2 AS IS DESCRIPTION
2.1
Since SAP HR Renewal 1.0 feature pack 4, a new business function has been introduced on ECC side called
Framework for Tracking Infotype Changes (FND_HRICP_1 on help.sap.com).
This framework allows to track all modifications done on PA & PD infotypes. Then it allows BW extractors to send
only DELTA to BW system, instead of extraction the full content of the infotype table.
It has been noticed that modification done by PHA interface are not tracked by this framework. After investigation,
its a SAP standard behavior, according to following OSS Call:
call_oss.pdf
Installation_Procedur
e.docx
2.2
No possibility to use this framework, as it does not track all modification done on infotypes.
This issue has a huge impact on Annual Interview project, as lot of PA/OM modification have to be tracked on a
daily basis.
<Project Version>
<Application Code>
Issue:
1.0
Date :
15/09/2014
3 TO BE DESCRIPTION
According to the solution suggested by SAP in the OSS Call, all modification done by an IN interfaces, on PA/PD
infotypes which are customized to be tracked by the framework, need to be registered in HRICP_D_CH_PTR table
on xHM side.
ID
IITC_01
IITC_02
Short Name
Description
Source
Priority
Coverage
Interface scope
GCO
High
Mandatory
Interface status
GCO
High
Mandatory
GCO
High
Mandatory
Tracking results
IITC_04
Performance impact
GCO
High
Mandatory
IITC_05
Data Modification
GCO
High
Mandatory
IITC_06
Out Interfaces
GCO
High
Mandatory
<Project Version>
<Application Code>
Issue:
1.0
Date :
15/09/2014
REFERENCE DOCUMENTS
Index
Title
Reference
Issue
Date
Please indicate the list of reference documents used by this template. Note that only documents that are
applicable or referred to in the text should be listed.
List also documents to be used to cover/express legal requirements : EADS agreements, Laws, legal forms,
In the column Index, please enter the reference to be used in the text (ex: [RD1]).
<Project Version>
<Application Code>
Date :
15/09/2014
REVIEWERS
Department -
Name - Function
Company
Grgoire COUSIN
CTOIOIM HIB
Date
15/09/2014
<Project Version>
Issue:
1.0
<Application Code>
Date :
15/09/2014
APPROVAL
Name - Function
Department -
Date
Signature
Company
In this section, list only the relevant approvers (Business key stakeholders + eHR core team members + eHR
Quality). All others should be on the distribution or review lists only.
As signature please put the link to documents included their approval (Validation mails received, MoM, scan of
document physically signed)
Issue:
1.0
<Application Code>
<Project Version>
Date :
15/09/2014
DISTRIBUTION LIST
Name - Function
Department -
Date
Signature
Company
Issue:
1.0
<Application Code>
<Project Version>
Date :
15/09/2014
TABLE OF REVISIONS
Issue
1.0
Date
15/09/2014
Modified by
Modified
sections
Grgoire COUSIN
All
Observations
Creation of the document
10