sre fde1002 eng am spm sv

FDE 1002Evolution Request File Projet SRE

Version 0.01 09/04/2014

Type de fiche / Type of request

Enhancement Request (before the project/lot) Amendment Request (during the project/lot)

Etat de la fiche / State of the File

Created Evaluated Determined

< Décision >: Change decision

Etape 1 : Identification de la demandeStep 1 : Request identification

Projet / Lot : SREProduct version / lot

R3.6

Date de la demande : 09/04/2014Date of the request

Numéro de Fiche : 1002File Id

Origine de la demandeRequest’s origin

Business Local IS team Business Analyst Technical Analyst

Other

Commentaire : Comment : to precise the origin

En charge de la demande / Request responsibleMétier

Business personConcepteur Fonctionnel

Business AnalystDéveloppeur

Developer

Nom Name Nom J. Rodriguez Nom P. Varatharajan

Intitulé de la demande / Request title

- GPRO impact and evolution of GPS Proto

- Adding Fields "references" in the business activitiesContexte général / Global context

In next release, SRE will transfer the data to GPRO project and supplying the project GPRO needs, SRE have to integrate new data.

There are new references for business activities to make proto reporting. These fields must be taken into account in the reporting.

Also there are old fields received from GPS for business activities who there are not in the target table in the SRE.

Description de la demande / Request Description

To supply the project GPRO needs, SRE have to integrate new fields in - SV (SAC_VALIDATION_SUPPORT)- SPM (SAC_BUSINESS_SUB_PROJECT) - AM (SAC_BUSINESS_ACTIVITY)

The new references to make proto reporting will be integrated in SAC_BUSINESS_ACTIVITY table.

The old fields that exist in tmp_activite_metier table will be integrated in SAC_BUSINESS_ACTIVITY table.

DSIR © RENAULT s.a.s. /15

ResponsableResponsableResponsable

Autre

Concepteur TechniqueConcepteur FonctionelleInformatique LocaleMétier

DécidéeImpacts évalués

Créée

Demande d'avenants (pendant projet/lot)Demande d'évolutions (avant projet/lot)


Version 0.01 09/04/2014

Périmètre de déploiement / Deployment perimeter

The affected users are proto users and GPRO users

Pièces jointes pour préciser la demande / Attached documents to clarify the request

PJ1 : PJ2 : PJ3 : PJ4 :Justification de la nécessité et l’urgence de l’évolution (gains métier, contraintes légales, informatiques, …)Justification for evolution and high priority (business stakes, legal constraints, IS/IT constraints, …)

This application determines the deployment GPRO whose pilot is planned for autumn 2014 SRE must have evolved by then according to the demands of the business

Criticité Functional priority

High Middle Low

Priorité de livraisonDelivery Priority

Délai souhaité / Expected date : Delivery in OPER R3.6 end June

Evénement métier associé :Related business event


Non Urgent

Urgent

MineurImportantCritique


Version 0.01 09/04/2014

Etape 2 : Analyse de la demande et de son impact – FaisabilitéStep 2: Evaluation of the request & of their impact – Feasibility

Analyse de la demande et éléments de solution (Concepteur fonctionnel)Evaluation result and solution elements (Business Analyst)

The new fields to supply the GPRO needs are:

"Type de fab", "Fab usine ?", "Ind MADC" and "Jalon MADC" in "export_SV.txt" to integrate in SAC_VALIDATION_SUPPORT table

"Ind MADC" in "export_SPM.txt" to integrate in SAC_BUSINESS_SUB_PROJECT.

"Début cible" and "Fin cible" in "activite_metier.txt" to integrate in SAC_BUSINESS_ACTIVITY.

The new references fields will be used in the proto reporting are:

Début calculé_REF1", "Début calculé_REF2", "Début calculé_REF3", "Fin calculé_REF1", "Fin calculé_REF2" et "Fin calculé_REF3" in activite_metier.txt to integrate in SAC_BUSINESS_ACTIVITY.

The old fields that exist in tmp_activite_metier table will be integrated in SAC_BUSINESS_ACTIVITY table are:

TEXT5, TEXT6, TEXT7, TEXT8, TEXT9, TEXT10, TEXT11, TEXT12, TEXT13, TEXT14, TEXT15, TEXT16, TEXT17, TEXT18, TEXT19.

Analyse de la demande et solution proposée (Concepteur Technique)Evaluation result and solution elements (Technical Analyst)

The jobs JS_CHG_TAB_TMP_METIER, JX_CHG_BUSINESSACTIVITY, JX_CHG_BUSINESSACTIVITY_1 , JX_CHG_BUSSUBPROJECT and JX_CHG_VALSUPPORT needs to be modified for adding the fields.

Below Scripts needs to be modified001_maj_bdd.sql- Needs to add the alter query003_CREATE_TABLES_TMP.SQL- Needs to add the create tmp table scriptBelow updated files needs to be overwritten to corresponding folderF_activite_metier.schemaF_export_SV.schemaF_export_SPM.schema

activite_metier.iniexport_SV.iniexport_SV.ini

Analyse d’impactResult =of impact analysis

Analyse Concepteur fonctionnelAnalysis by Business Analyst

Compléments apportés par le Concepteur TechniqueAnalysis complements by Technical Analyst

Impacts organisationnels (client, processus, …)Organizational impacts (users, processes, …)

Review GPS CLAReview “GPS-DE4922 Impact

GPRO Proto et évolution de GPS Proto” File

Changing the infrastructure associated


https://renault-workspace.share.renault.com/gna/proj3387/Projet%20GPS/GPS_V2.12/GPS-GPRO%20proto/GPS-DE4922%20Impact%20GPRO%20Proto%20et%20%C3%A9volution%20de%20GPS%20Proto.docx




Version 0.01 09/04/2014

Review “GPS-DE5024 - ajout de

champs dans les exports sur les activités métiers” file

Impacts techniques, développementsTechnical modifications and developments

Updating the loading process to tablesSAC_BUSINESS_ACTIVITYSAC_VALIDATION_SUPPORTSAC_BUSINESS_SUB_PROJECT

Technical and application architecture

Impacts documentaires (les plans et documents de test, documents de spécification, CLA, …)Impacts documentary (plans and documents of test, documents of specification, CLA, …)

MAPPING_R3.6.xls file was Updated

Associated treatments and nature Screens Reporting, states

Impacts sur les donnéesData evolution

8 new fields and 15 old fields to mapping in the table SAC_BUSINESS_ACTIVITY4 new fields in the table SAC_VALIDATION_SUPPORT1 new field in the table SAC_BUSINESS_SUB_PROJECT

we have to add the fields in TMP tables and target tables. Needs to change the TMP load jobs and target tables load jobs. We need to use the updated schema, format and sql files from updated Mapping Sheet.

Impacts Qualité : les revues, les validations et vérificationsQuality: reviews and validation activitiesImpacts industrialisationImpacts industrialization

NA

Autres points impactésOther impacted points

NA

Impacts Charges Estimated work

Analyst + writing docs + mapping +Re7

Jobs + Scripts + GESTION_CONFIG_SACRE.xlsx + Test

Impacts Coûts Estimated Costs

NA

Impacts DélaisEstimated Time for the change

NA

Etape 3 : Décision sur la demandeStep 3 : Decision on the request


https://renault-workspace.share.renault.com/gna/proj3387/Projet%20GPS/GPS_V2.12/GPS-DE5024%20-%20ajout%20de%20champs%20dans%20les%20exports%20sur%20les%20activit%C3%A9s%20m%C3%A9tiers.doc




Version 0.01 09/04/2014

Décision de réaliserRealization decision

Accepted Refused Postponed

Date de décision : dd/mm/yyyyDecision date

Instance de décision :Decision committee

Documents de référenceRelated documents


ReportéeRefuséeAcceptée


Version 0.01 09/04/2014

Etape 4 : ConceptionStep 4: Design Specification

En charge de la ConceptionDesign Responsible

Concepteur FonctionnelBusiness Analyst

J. RODRIGUEZ (ALTEN) Launch date 07/04/2014

Concepteur TechniqueTechnical Analyst

P. VARATHARAJAN (ISDC) Launch date / /

MOE en charge de la validationProject Manager in charge of the validation

F. SAIDANI Validation date: 11 /04 /2014

Summary1. Description détaillée du besoin................................................................................................................6

1.1. Functional Specification [BuA]..........................................................................................................................61.2. Technical Specification [TechA].......................................................................................................................6

Software components modified...................................................................................................................................6Description of the modifications..................................................................................................................................6

2. Description of interfaces [BuA]..............................................................................................................73. Description of data................................................................................................................................... 7

3.1. MCD - Conceptual Data Model [BuA]...............................................................................................................73.2. MPD – Physical Data Model [TechA]...............................................................................................................7

Document only the chapters necessary for describing and understanding the detailed description of the product modification.

[BuA] at the end of a chapter title means that the chapter has to be specified by the Business Analyst

[TechA] at the end of a chapter title means that the chapter has to be specified by the Technical Analyst



Version 0.01 09/04/2014

1. Description détaillée du besoin

1.1. Functional Specification [BuA]

Description of need:

COMP_SRE_FDE1002_01 The integration into the SRE of the new fields Début cible,Fin cible,Début calculé_REF1,Début calculé_REF2,Début calculé_REF3,Fin calculé_REF1,Fin calculé_REF2,Fin calculé_REF3from the activite_metier.txt file must respect the specifications in MAPPING_R3.6.xls

COMP_SRE_FDE1002_02 The mapping into the SRE of the fields TEXT5,TEXT6,TEXT7,TEXT8,TEXT9,TEXT10,TEXT11,TEXT12,TEXT13,TEXT14,TEXT15,TEXT16,TEXT17,TEXT18,TEXT19from tmp_activite_metier table must respect the specifications in MAPPING_R3.6.xls

COMP_SRE_FDE1002_03 The integration into the SRE of the new fields Type de fab,Fab usine ?,Indicateur MADC,Jalon MADCfrom the export_SV.txt file must respect the specifications in MAPPING_R3.6.xls

COMP_SRE_FDE1002_04 The integration into the SRE of the new fieldIndicateur MADCfrom the export_SPM.txt file must respect the specifications in MAPPING_R3.6.xls

For each impacted job, describe the modification

1.2. Technical Specification [TechA]

Software components modifiedBelow jobs needs to be modified

1) The Job JS_CHG_TAB_TMP_METIER– (job activity) will be updated in dStage_SRE->Jobs->SOCLE_R3.5->Phase0-> JS_CHG_TAB_TMP_METIER



Version 0.01 09/04/2014

Job Description: This job will load the data from updated flat file(activite_metier.txt)( to TMP table(tmp_ activite_metier)



Version 0.01 09/04/2014

2) The Job JX_CHG_BUSINESSACTIVITY and JX_CHG_BUSINESSACTIVITY_1will be updated in dStage_SRE->Jobs->SOCLE_R3.5->Phase7-> BUSINES_ACTIVITY

Description of Job Modification: This job will load the data from tmp table(tmp_ activite_metier)( to TARGET table(SAC_BUSINESS_ACTIVITY)



Version 0.01 09/04/2014

3) The Job JX_CHG_BUSSUBPROJECT will be updated in dStage_SRE->Jobs->SOCLE_R3.5->Phase8-> BUSINESS_SUB_PROJECT

Description of Job Modification: This job will load the data from tmp table(tmp_ export_SPM)( to TARGET table(SAC_BUSINESS_SUB_PROJECT)



Version 0.01 09/04/2014

4)The Job JX_CHG_VALSUPPORT will be updated in dStage_SRE->Jobs->SOCLE_R3.5->Phase8-> VALIDATION_SUPPORT

Description of Job Modification: This job will load the data from tmp table(tmp_ export_SV)( to TARGET table(SAC_VALIDATION_SUPPORT)



Version 0.01 09/04/2014

2. Description of interfaces [BuA]

NA

3. Description of data

3.1. MCD - Conceptual Data Model [BuA]Describe and highlight the data and relations that have been updated or added by the modification by recovering, whether fully or in part, the first level Conceptual Data Model (MCD) and the Physical Data Model (MPD). The requirements to be inserted here are the FCT (Functional) category and the DAT (Data description) sub-

category.

3.2. MPD – Physical Data Model [TechA]Describe the tables and columns impacted by the modification and describe the processes to be performed on the data (modifications, loading, cleaning, etc.) as well as the inspection procedures.Modify the resulting optimized MPD.

TMP table of the new fields:

FICHIER_SOURCE COLONNE_SOURCE LIBELLE_SOURCE FORMAT_SOURCE

POSITION_SOURCE

CLE_PRIMAIRE_SRC

NULL_SOURCE_ADMIS

activite_metier BEBUT_CIBLE Début cible Date(DD/MM/YYYY) 88 NON OUIactivite_metier FIN_CIBLE Fin cible Date(DD/MM/YYYY) 89 NON OUIactivite_metier

DEBUT_CALCULE_REF1

Début calculé_REF1 Date(DD/MM/YYYY) 90 NON OUI

activite_metier

DEBUT_CALCULE_REF2


activite_metier

DEBUT_CALCULE_REF3


activite_metier FIN_CALCULE_REF1 Fin calculé_REF1 Date(DD/MM/YYYY) 93 NON OUIactivite_metier FIN_CALCULE_REF2 Fin calculé_REF2 Date(DD/MM/YYYY) 94 NON OUIactivite_metier FIN_CALCULE_REF3 Fin calculé_REF3 Date(DD/MM/YYYY) 95 NON OUI

export_SV TYPE_FAB Type de fab Varchar2(5) 84 NON OUI

export_SV FAB_USINE Fab usine ? Varchar2(3) 85 NON OUI

export_SV INDICATEUR_MADC Indicateur MADC INTEGER(1) 86 NON OUI

export_SV JALON_MADC Jalon MADC Varchar2(1000) 87 NON OUI

export_SPM INDICATEUR_MADC Indicateur MADC INTEGER(1) 22 NON OUItref_ressources ESTUNRTX RTX ? Varchar2(3) 43 NON OUI

Mapping new fields:

TABLES_CIBLE COLONNES_CIBLEFORMAT_CIB

LETYPE_SOURCE

SOURCECOLONNE_SOURCE

FORMAT_SOURCE

TRANSFORMA

TIONSAC_BUSINESS_ACTIVITY CIBLE_BEGIN

DATE(DD/MM/YYYY) FICHIER activite_metier

BEBUT_CIBLE

DATE(DD/MM/YYYY)

SAC_BUSINESS_ACTIVITY CIBLE_END

DATE(DD/MM/YYYY) FICHIER activite_metier FIN_CIBLE

DATE(DD/MM/YYYY)

SAC_BUSINESS_ACTIVITY

CALCULATED_BEGIN_REF1


DEBUT_CALCULE_REF1

DATE(DD/MM/YYYY)

SAC_BUSINESS_AC CALCULATED_BEGIN DATE(DD/ FICHIER activite_metier DEBUT_C DATE(DD/



Version 0.01 09/04/2014

TIVITY _REF2 MM/YYYY)ALCULE_REF2 MM/YYYY)


CALCULATED_BEGIN_REF3


DEBUT_CALCULE_REF3

DATE(DD/MM/YYYY)


CALCULATED_END_REF1


FIN_CALCULE_REF1

DATE(DD/MM/YYYY)


CALCULATED_END_REF2


FIN_CALCULE_REF2

DATE(DD/MM/YYYY)


CALCULATED_END_REF3


FIN_CALCULE_REF3

DATE(DD/MM/YYYY)

SAC_VALIDATION_SUPPORT FABRICATION_TYPE Varchar2(5) FICHIER export_SV TYPE_FAB Varchar2(5) SAC_VALIDATION_SUPPORT IS_MADE_FACTORY INTEGER(1) FICHIER export_SV

FAB_USINE Varchar2(3)

OUI=1, sinon 0

SAC_VALIDATION_SUPPORT MADC_IND INTEGER(1) FICHIER export_SV

INDICATEUR_MADC

INTEGER(1)

SAC_VALIDATION_SUPPORT MADC_MILESTONE Varchar2(1000) FICHIER export_SV

JALON_MADC

Varchar2(1000)

SAC_BUSINESS_SUB_PROJECT MADC_IND INTEGER(1) FICHIER export_SPM

INDICATEUR_MADC

INTEGER(1)

Mapping old fields:

SAC_BUSINESS_ACTIVITY TEXT5

VARCHAR2(255) FICHIER

activite_metier TEXT5

Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)




Varchar2(255)

Cible table new fields:

TABLES_CIBLE COLONNES_CIBLE LIBELLE_CIBLE FORMAT_CIBLE

NULL_CIBLE_ADMI

S

CLE_PRIMAIRE_

CBL

SAC_BUSINESS_ACTIVITY CIBLE_BEGIN CIBLE_BEGIN DATE(DD/MM/YYYY) OUI NON

SAC_BUSINESS_ACTIVITY CIBLE_END CIBLE_END DATE(DD/MM/YYYY) OUI NON



Version 0.01 09/04/2014

SAC_BUSINESS_ACTIVITY CALCULATED_BEGIN_REF1 CALCULATED_BEGIN_REF1 DATE(DD/MM/YYYY) OUI NON



SAC_BUSINESS_ACTIVITY CALCULATED_END_REF1 CALCULATED_END_REF1 DATE(DD/MM/YYYY) OUI NON



SAC_VALIDATION_SUPPORT FABRICATION_TYPE FABRICATION_TYPE Varchar2(5) OUI NON

SAC_VALIDATION_SUPPORT IS_MADE_FACTORY IS_MADE_FACTORY INTEGER(1) OUI NON

SAC_VALIDATION_SUPPORT MADC_INDICATOR MADC_INDICATOR INTEGER(1) OUI NON

SAC_VALIDATION_SUPPORT MADC_MILESTONE MADC_MILESTONE Varchar2(1000) OUI NONSAC_BUSINESS_SUB_PROJECT MADC_IND MADC_IND INTEGER(1) OUI NON

Cible table new fields:

TABLES_CIBLECOLONNES_CIBL

ELIBELLE_CIBLE

FORMAT_CIBLE

NULL_CIBLE_ADMIS

CLE_PRIMAIRE_CBL

SAC_BUSINESS_ACTIVITY TEXT5 TEXT5 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT6 TEXT6 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT7 TEXT7 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT8 TEXT8 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT9 TEXT9 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT10 TEXT10 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT11 TEXT11 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT12 TEXT12 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT13 TEXT13 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT14 TEXT14 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT15 TEXT15 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT16 TEXT16 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT17 TEXT17 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT18 TEXT18 VARCHAR2(255) OUI NONSAC_BUSINESS_ACTIVITY TEXT19 TEXT19 VARCHAR2(255) OUI NON



Version 0.01 09/04/2014

Historique des évolutions du livrable du projet/application

VERSIONS DATEMODIFICATIONS

(NATURE ET CHAPITRES CONCERNES)AUTEUR

Historique des évolutions du template

VERSIONS DATEMODIFICATIONS

(NATURE ET CHAPITRES CONCERNES)AUTEUR

V1 07/04/2014

Initial version J. RODRIGUEZ


sre fde1002 eng am spm sv

Documents

demande request description

new fields

gpro project

new references fields

projectlotamendment

request pj1

fields references

dbut calcul