teeeeee
-
Upload
tejas-sanghavi -
Category
Documents
-
view
221 -
download
0
Transcript of teeeeee
-
7/31/2019 teeeeee
1/4
BAT Data QualityData Quality Request Specification Form
Ver. 1.1Printed on: August 01, 2012 4:26:16 PM
1. Document History
1.1. Revision HistoryAuthor/Changed by Version Date Status/CommentsDonna Foreman 1.0 19/01/2012
1.2. Approvals (alphabetical order)Name Signature Title Date Version
1.3. DistributionName Title Date Version
1. PURPOSE OF DOCUMENTThe purpose of this document is to ensure that a request for a data quality service is carried out in a consistent and standardised manner.
It allows the requestor to provide a complete set of data quality specificationsthat the service provider can then use to deliver the required Data Quality reports.
-
7/31/2019 teeeeee
2/4
The document also provides the requestor with visibility of the timelines pertaining to their request,2. REQUESTOR INFORMATIONThis section is to be completed by the requestor.* denotes a mandatory field
No. Information Required Response Comments1* Name of Requestor Donna Foreman2* Business Function Operations2.1* Business Priority High3* Date of Request(Date this request is submitted to the service provider) 19/01/20124* Name of Data Object to be checked(Name which will identify the data object to be checked) GS_NPI_SKU on the following Classes: GS_FG_CIGAR, GS_FG_SNUS, GS_FGFINECUT, GS_FG_PIPE, GS_FG_CP
_FINECUT, GS_FG_TUBES5* Name and accessibility (User-Id and Password) of the source system the data is to be extracted from N/a6* Name/Structure of the table the data is to be extracted from in each source system The following are the various sources, which will be used for the data extraction for given .
Sr No. Source System Name Source File Name Update Cycle
1 Fortnightly
7* Columns that needs to be extracted/considered for change
Sr No. Source File Name Source Column
8 Filter Conditions/Derived Columns to be added/modified/Removed
Source File Name Filter to be added Derived Column name with transformation rule
9* Source system Contact/Owner Bob Davies10 Reference File to be used
< Name of the reference file used, frequency of receiving them,storage location >< Reference File Format attached >
11 Description of Business Rules to be Added/Modified/Removed
Information DetailsSubjectArea TextOrganisation
-
7/31/2019 teeeeee
3/4
RuleNameShortRuleNameLongRule_LogicRuleTypeBusinessFunctionRuleStartDateRequestedByForProjectRuleOwnerRuleStatusRuleReasonRuleEndDate
12* Name of the Data Object Owner N/a13* Textual description of the business rule to be applied)Description of the circumstances when the data object will fail the data quality check) Business rules added to this latest file:
14* Date rule to become effective from (dd/mm/yyy) Immediate15* Date rule become effective to (dd/mm/yyy)(Set to On-going if no expiry date) Ad hoc16 Name and brief overview of project (if applicable) linked to this reques
t OTDP17* Business impact caused by poor data quality of this Data Object(Description of the issues caused by poor data quality) Inaccurate reporting inBI18* Name of the Rule Owner(Person authorising the implementation of the data quality rule) Donna Foreman19* DQ Report Recipients(List of the people who need to receive the DQ report associated to this data object) SAP BI19 Mock up of the DQ Report required Usual SAP BI reports20* Frequency DQ Report should be run - (e.g. weekly, monthly, quarterly)Usual SAP BI reports
21* Should it be a part of SAP BI? Yes
3. SERVICE PROVIDER INFORMATIONTo be completed by the Service ProviderAll fields are mandatory
Request Ref.(Unique ref. number assigned by Service Provider) 0001
No Information Required Expected Date Actual Date Comments1 Date request received
2 Date acknowledgement of request sent to Requestor(SLA: Within 2working days of receiving request)3 Date estimate (time/cost) sent to Requestor(SLA: Within 6 working days of receiving request)4 Date confirmation toproceed received5 Date development begun6 Date development complete7 Date rule put into Production8 Rule Active date
-
7/31/2019 teeeeee
4/4
9 English logic description of the business rule logic to be applied